BYEs are sequential (in-dialog) requests that go to the RURI that is the Contact returned in the final 2xx reply.
CANCELs are sent to the proximate endpoint - same RURI as initial INVITE request. They are not sequential requests, are not loose- routed, etc. So, the behaviour you are seeing is normal. -- Sent from mobile device On Jan 22, 2010, at 12:55 PM, Olivier Détour <chino540off+kamai...@gmail.co m> wrote: > Hi, > > I would like to break a SIP communication during a call or a > proceeding SIP session... > > If the call is in progress (Caller can speak to Callee), I can send a > BYE to caller and callee each with send_request function; > Here is my Wireshark trace: > > BYE sip:s...@1.1.12.3 SIP/2.0 > Via: SIP/2.0/UDP 2.2.22.2;branch=z9hG4bKda73.5742b3a7.0 > From: <sip:1...@2.2.22.2>;tag=934c0604001f8a49c065a1707fbb682d-59cf > To: <sip:2...@1.1.12.3>;tag=B2B.333.0.1264181639 > CSeq: 4 BYE > Call-ID: B2B.269.0.1264181639 > Content-Length: 0 > User-Agent: OpenSIPS (1.6.1-notls (i386/linux)) > Contact: <sip:s...@2.2.22.2> > > If the sip session is proceeding (Caller send INVITE but he hasn't > receive 200 OK yet), I send a CANCEL > like I sent the BYE (send_request); > But here is my Wireshark trace: > > CANCEL sip:2...@1.1.12.3 SIP/2.0 > Via: SIP/2.0/UDP 2.2.22.2;branch=z9hG4bK5161.0ab21263.0 > From: <sip:1...@2.2.22.2>;tag=934c0604001f8a49c065a1707fbb682d-ac1f > To: sip:2...@1.1.12.3 > CSeq: 2 CANCEL > Call-ID: B2B.134.0.1264181129 > User-Agent: OpenSIPS (1.6.1-notls (i386/linux)) > Contact: <sip:s...@2.2.22.2> > > Why is the Request Line not for sip:s...@1.1.12.3 as for the BYE? > > Regards, > > -- > Olivier Détour > Sent from Paris, Île-de-France, France > > _______________________________________________ > Devel mailing list > Devel@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/devel _______________________________________________ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel