El Tuesday 04 September 2007 15:37:46 Iñaki Baz Castillo escribió: > El Tuesday 04 September 2007 15:03:25 Dan escribió: > > Full ngrep log attached. > > In the INVITE OpenSEr sends to your provider is appears: > > > ## U 78.45.146.34:5060 -> 212.34.169.220:5060 > INVITE sip:[EMAIL PROTECTED]:5060 SIP/2.0. > Record-Route: <sip:78.45.146.34;ftag=6613ce14;lr>. > To: <sip:[EMAIL PROTECTED]>. > From: 58.68.96.11<sip:[EMAIL PROTECTED]>;tag=6613ce14. > Call-ID: 757a270529254e41. > ... > Contact: <sip:[EMAIL PROTECTED]:5060> <---- **1** > > > But in the BYE from your provider it appears: > > > ## U 212.34.169.220:5060 -> 78.45.146.34:5060 > BYE sip:[EMAIL PROTECTED] SIP/2.0. <---- **2** > Route: <sip:78.45.146.34;ftag=6613ce14;lr>. > From: <sip:[EMAIL PROTECTED]>;tag=04093807084639921117967993. > Call-ID: 757a270529254e41. > To: 58.68.96.11<sip:[EMAIL PROTECTED]>;tag=6613ce14. > ... > > That is wrong, the **2** field should be the same as **1** in order to > OpenSer route the BYE to EyeBeam. Because the URI is 78.45.146.34 > (OpenSer's IP) then the BYE arrives to OpenSer, it reads "Route: > 78.45.146.34" so it deletes the "Route" header and sends again the BYE to > himself. But this time there is not a "Route" header so the message is NOT > in dialog.
I'd like to insist on this. The problem is there: the provider SHOULD send the BYE (in-dialog BYE containing "Route" header) to the URI indicated in the "Contact" header that OpenSer sent to provider. But instead of that, the provider sens the BYE to a wrong URI (sip:[EMAIL PROTECTED]). Could you do a ngrep when a call from PAP2 to other PAP2? ngrep -d any -P ' ' -W byline -T -t "$*" udp port 5060 -- Iñaki Baz Castillo [EMAIL PROTECTED] _______________________________________________ Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users