In your case UAS should send 500 to the second INVITE and continue with the first one as usual. Sec 14.2 says
A UAS that receives a second INVITE before it sends the final response to a first INVITE with a lower CSeq sequence number on the same dialog MUST return a 500 (Server Internal Error) response to the second INVITE and MUST include a Retry-After header field with a randomly chosen value of between 0 and 10 seconds. Am I missing any thing ? -Sp.Raja -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Medhavi Bhatia Sent: Wednesday, 31 July 2002 2:32 AM To: [EMAIL PROTECTED] Subject: [Sip-implementors] re-invite In section 14.2 of rfc 3261, the spec doesnt seem to talk about the following scenario: A UAS hasnt responded yet to an INVITE or a re-INVITE on the dialog (or early dialog), and it receives a new re-INVITE, which is different from what was pending (ie., higher CSeq no). The spec forbids the UAC (dialog peer) from sending a new INVITE before the UAS has responded to the old one, but in cases of a misbehaving UAC, what response should be sent to the second INVITE ? Maybe I am missing some detail. Can someone clarify this ? _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
