Hi, On Mon, Nov 29, 2010 at 9:49 PM, Felix Lechner <[email protected]> wrote: > > Ian & Eugen, > Thank you for your responses. I would be happy to create a bug report, > although I require some clarification: > 1. Should I file one bug report covering the PUBLISH and the BYE issues > together, or just one a report for the BYE issue alone?
I already filed a bug report for the BYE issue: https://bugzilla.gnome.org/show_bug.cgi?id=636121 > 2. With respect to the BYE issue, the offending message in case of a timeout > is > (1) 32 35.745194 192.168.11.177 192.168.11.1 SIP > Request: BYE sip:[email protected]:24000 > Instead, it should look like > (2) 32 35.745194 192.168.11.177 192.168.11.1 SIP > Request: BYE sip:[email protected]:24000 > if the record-route field has been set to ensure the proxy stays in the path > AND loose routing has not been specified, or > (3) 32 35.745194 192.168.11.177 192.168.11.1 SIP > Request: BYE sip:[email protected]:24000 > if the record-route field has been set and loose routing has been specified, > or > (4) 32 35.745194 192.168.11.177 198.65.166.131 SIP > Request: BYE sip:[email protected]:24000 > if the record-route field has not been set even if an outbound proxy has > been specified (please note destination IP), but never > (5) 32 35.745194 192.168.11.177 192.168.11.1 SIP > Request: BYE sip:[email protected]:24000 > Right? > I am particularly unsure if I properly understand the IP routing vs. SIP > routing mechanism. > Message (4) would fail in my circumstances, but 'siproxd' hopefully sets the > record-route field. If not, then it probably should. The request line is actually good, but it has wrong route set. From RFC 3261 Section 12.2.1.1: "If the route set is not empty, and the first URI in the route set contains the lr parameter (see Section 19.1.1), the UAC MUST place the remote target URI into the Request-URI and MUST include a Route header field containing the route set values in order, including all parameters." So the BYE should have the request line: BYE sip:[email protected]:24000 SIP/2.0 and the following Route headers: Route: <sip:[email protected]:5060;lr> Route: <sip:198.65.166.131;lr;ftag=1370489315> Route: <sip:198.65.166.131;lr;ftag=1370489315> Route: <sip:74.125.46.80:24000;lr=on> -- Ian _______________________________________________ ekiga-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list
