Re: [Opalvoip-user] BYE not received at end point

[Robert J. <ro...@vo...>]

Sorry, that is incorrect and will make it non compliant to the RFC. 
There are very strict rules for how the target URI is updated via a dialog.

There are also strict rules for how a request (e.g. BYE) is sent and how 
to determine where to send it. In particular, the Contact field is 
overridden by the receive= field of the Via header. If you are behind a 
NAT, then that should have been triggered, setting 
m_fixedTransportAddress in the SIPDialogContext.

Can you send me a trace log exhibiting the problem?

*Robert Jongbloed*
/OPAL/OpenH323/PTLib Architect and Co-founder./
Commercial support at http://www.voxlucida.com.au

On 3/09/2014 4:10 PM, Ashok Kumar wrote:
> Hi Robert,
>
> I was making an incoming sip call to my application (which uses opal). 
> Endpoint was behind NAT and my application is in public domain.
>
> I am seeing that the INVITE transation initiated from EP is completed 
> successfully and media is also flowing both way. But later when I 
> disconnect the call from my end then OPAL trying to send the BYE to 
> the private IP received in Contact header of initial INVITE, hence it 
> is failing to create the TCP connection itself.
>
> To make it work I have replaced the "m_requestURI" with the public 
> transport address.
>
> I am attaching the changes I have done. Pease let me know if you agree 
> with the fix?
>
>
> Thanks,
> Ashok
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
>
>
> _______________________________________________
> Opalvoip-user mailing list
> Opa...@li...
> https://lists.sourceforge.net/lists/listinfo/opalvoip-user