[reSIProcate] [resiprocate] Fails to send BYE to WS, WSS clients [DNS failure for the address <random>.invalid]
Scott Godin
sgodin at sipspectrum.com
Tue Nov 13 12:39:42 CST 2018
The point is, to get this to work, you need to use the same TCP connection
that the Websocket client formed for all SIP messaging to/from that client,
you shouldn't be using the contact header for any routing. RFC5626 is an
implementation of this logic for registrars/proxies. This is what repro
implements to get that behaviour.
Scott
On Tue, Nov 13, 2018 at 1:05 PM Diego Carvalho Domingos <
ddomingos at daitan.com> wrote:
> I would be glad to share but I still did not find a solution for this. I
> thought it would be easy to just get the IP from the connection object and
> avoid dns but still couldn’t figure it out. Also, I didn’t understand how
> RFC5626 would help on this. If you find a solution, Abdul, please let me
> know. Thanks
>
>
>
> Diego
>
>
>
> *From:* Scott Godin <sgodin at sipspectrum.com>
> *Sent:* Tuesday, November 13, 2018 1:26 PM
> *To:* abdulrehman272 at live.com
> *Cc:* resiprocate-devel at resiprocate.org
> *Subject:* Re: [reSIProcate] [resiprocate] Fails to send BYE to WS, WSS
> clients [DNS failure for the address <random>.invalid]
>
>
>
> https://list.resiprocate.org/archive/resiprocate-devel/msg08919.html
>
>
>
> You could setup repro between the browser and your application and ensure
> record-routing is enabled.
>
>
>
> Implementing flow routing in a DUM app is possible, but not trivial, if
> Diego got it working, perhaps he'll share.
>
>
>
> Scott
>
>
>
> On Tue, Nov 13, 2018 at 2:56 AM Abdul Rehman <abdulrehman272 at live.com>
> wrote:
>
> Hi,
>
>
>
> I am using resiprocate-1.10.2 and have the exact same issue as mentioned
> in the following thread posted by Diego Carvalho Domingos:
>
>
> https://list.resiprocate.org/archive/resiprocate-devel/msg08916.html
>
>
> I would like to know its solution. I have tried message decorator so far
> but it didn't help.
>
>
>
> Thanks.
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20181113/260be372/attachment.htm>
More information about the resiprocate-devel
mailing list