Atul, RFC 3261, p.14.1:
If a UA receives a non-2xx final response to a re-INVITE, the session parameters MUST remain unchanged, as if no re-INVITE had been issued. Note that, as stated in Section 12.2.1.2, if the non-2xx final response is a 481 (Call/Transaction Does Not Exist), or a 408 (Request Timeout), or no response at all is received for the re- INVITE (that is, a timeout is returned by the INVITE client transaction), the UAC will terminate the dialog. The dialog is considered terminated. Anyway, ask Slava Sayko first :). Alexander. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Atul Edlabadkar Sent: Wednesday, July 20, 2005 5:14 PM To: [email protected] Subject: [Sip-implementors] How ReInvite timeout should be handled... I would appreciate if somebody can comment on following callflow: UAS UAC <----------------INVITE-------------------- -----------------100-------------------------> -----------------180--------------------------> -----------------200--------------------------> <----------------ACK------------------------ <----------------reINVITE-------------------- ------------------No Response------------- 1) Isn't the UAC supposed to send BYE in this case? 2) The SIP Stack used by UAC removes the dialog when it timesout sending reINVITE and post 408 timeout event to application. Is this correct behaviour? Thanks, Atul _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
