[reSIProcate] [resiprocate] Fails to send BYE to WS, WSS clients [DNS failure for the address <random>.invalid]

Abdul Rehman abdulrehman272 at live.com
Mon Jan 28 10:01:02 CST 2019


Hi Diego Carvalho Domingos,

Here is the solution, in my case browser is initiating a call.

          // Participant is inherited from InviteSessionHandler
          // resip::Tuple m_destination;

void Participant::onNewSession(ServerInviteSessionHandle sish, InviteSession::OfferAnswerType, const SipMessage &msg)
{
  ...
  m_destination = msg.getSource();
  ...
 }
void Participant::onReadyToSend(resip::InviteSessionHandle ish, resip::SipMessage &msg)
{
  msg.setDestination(m_destination);
}

Please let me know your thoughts and if you find a better solution please share.

Thanks,
Kind Regards,
Abdul Rehman

________________________________
From: Diego Carvalho Domingos <ddomingos at daitan.com>
Sent: Tuesday, November 13, 2018 11:05 PM
To: Scott Godin; 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]


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<mailto: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<mailto: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/20190128/ec836630/attachment.htm>


More information about the resiprocate-devel mailing list