I believe it should transition the state to 'Terminated'. That's what happens in case of a transport error in all other states - Calling & Completed.
See corresponding figure (Figure 6) for non-INVITE client transaction. Same is the case for INVITE server transaction. I believe this behavior should be same across INVITE & Non-INVITE client transactions. FYI, Transport Error handling in case of non-INVITE transactions for un-reliable transports is highlighted in RFC 4321. Regards, Gaurav > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:sip-implementors- > [EMAIL PROTECTED] On Behalf Of Nasir Khan > Sent: Friday, May 04, 2007 8:24 AM > To: [email protected] > Subject: [Sip-implementors] Invite Client Transaction State > Machineommission? > > With respect to Invite Client Transaction (ICT) state machine diagram > 17.1.1.2 RFC 3261 Figure 5. - > > > > In the "Proceeding" state there is no transition on transport error. The > ICT sends an ACK on 300-699 response but the treatment on transport > error is not specified, while it is specified for "Calling" and > "Completed" states where the machine transitions to "Terminated". > > > > What should be the right behavior on transport error in "Proceeding" > state? > > > > 1. No state change? OR > > 2. Silently transition to Completed? OR > > 3. Transition to Terminated? OR > > > > Also there is this implicit initial state before the INVITE is sent out, > so what happens to the Txn if sending of INVITE results in transport > error. > > > > Thanks > > Nasir > > > > Discuss SIP Servlets at http://groups.google.com/group/sipservlets/ > <http://groups.google.com/group/sipservlets/> > > > > > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the individual > or entity named in this message. If you are not the intended recipient, > and have received this message in error, please immediately return this by > email and then delete it. > _______________________________________________ > 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
