Hello, That's exactly the point.They shouldn't be the same. Please check scenario 3.1 of RFC3665. Best regards, Ben.
________________________________ From: Aurelien Grimaud [mailto:[email protected]] Sent: vrijdag 23 januari 2009 15:10 To: BONNAERENS Ben Cc: Iñaki Baz Castillo; [email protected] Subject: Re: [Sip-implementors] reply 481 Call/Transaction Does Not Exist toBYE BONNAERENS Ben a écrit : Hello, No, the BYE's R-URI is ok ("Callee" side is releasing). Probably it's the From and To header of the BYE that are incorrect. Best regards, Ben. Well, From and To header fields are exactly the same in all requests and replies. (ezxcept To for INVITE and 100 provisional which does not have tag) Aurelien -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Iñaki Baz Castillo Sent: vrijdag 23 januari 2009 14:49 Cc: [email protected] Subject: Re: [Sip-implementors] reply 481 Call/Transaction Does Not Exist toBYE 2009/1/23 Aurelien Grimaud <[email protected]> <mailto:[email protected]> : Hi, I try to setup tests with sipp, openser and resiprocate. resiprocate (192.168.160.23:6091) initiate the calls sip routeur is 192.168.160.141:5060 uas is sipp 192.168.160.141:5061 sipp initiates a BYE which is routed correctly by openser but rejected by resiprocate. Request Uri, from and to looks ok. I am obviously missing something.... If someone could point me what ... I am struggling with RFC but not finding any answer. How should be constructed the via in BYE ? The Via branch should not be any of previous one, this is a new transaction right ? The BYE is a different transaction so the Via MUST NOT match. Your problem is the Request URI in the BYE which is wrong: ACK is correct: ACK sip:192.168.160.141:5061 BYE is totally wrong: BYE sip:[email protected]:6091 BYE RURI should be the same as the ACK RURI. -- Iñaki Baz Castillo <[email protected]> <mailto:[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
