RFC 3261 section 12.2.1.2 addresses your questions. However the usage of SHOULD instead of MUST within the text allows some leeway by the implementer/service/deployment to choose not to perform the SHOULD. (RFC 2119 defines SHOULD and MUST.)
"If the response for a request within a dialog is a 481 (Call/Transaction Does Not Exist) or a 408 (Request Timeout), the UAC SHOULD terminate the dialog. A UAC SHOULD also terminate a dialog if no response at all is received for the request (the client transaction would inform the TU about the timeout.) For INVITE initiated dialogs, terminating the dialog consists of sending a BYE." > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Atul Edlabadkar > Sent: Wednesday, July 20, 2005 8: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
