Hi David, In RFC 2543, INVITE and CANCEL transactions were intermingled, but in RFC 3261 they are separated. When a user sends an INVITE and then a CANCEL, UAS needs to send 200 for cancel and then needs to respond to the original INVITE request with a 487 response.
Rgds, Gururaj K. David Cutullic <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 04/10/2006 02:40 PM To [email protected] cc Subject [Sip-implementors] Should a cancel generate a new server transaction ? Hi, When a cancel is received from the network, should it be matched with a new server transaction or with the server transaction of the initial invite request ? When i read the chapter 17 of the rfc 3261, in understand than all the request must create a transaction. But I use the java NIST SIP implementation that don't match the cancel request with a transaction. Is it an error of the implementation ? Thanks for your attention _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors *********************** FSS-Unclassified *********************** _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
