Hi Youg, I think it is ok.. that time limit is depends upon the design of the application.. If your application wants to wait for more than 180 seconds or if you are going to integrate ur application with some other SIP entities which will take more than 180 sec to respond .. then it will lead to some other issues..
Regds, Balaji Murlitharan.C Aricent "Yong Xin" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 01/09/2007 01:16 AM Please respond to [EMAIL PROTECTED] To Balaji Murlitharan/CHE/[EMAIL PROTECTED] cc [EMAIL PROTECTED], [email protected] Subject Re: [Sip-implementors] SIP question about "INVITE clienttransaction"in RFC3261 Thanks Balaji, this helps. Since it is user agent's choice when to hangup if no final response is received, it makes sense some kind of timer should be implemented by application to avoid the transaction stay in Proceeding state forever. Once this bug is resolved, I think the spec will just include some clarification and still leave no timer defined for this state (since it is implementation dependent). Our implementation currently chooses to include a "Expires" header in outbound INVITE message with a value of 180 seconds (minimum of Timer C value) and generate a CANCEL request if no final response is received once it is expired, any comments? Regards, Yong _____ From: Balaji Murlitharan [mailto:[EMAIL PROTECTED] Sent: Monday, January 08, 2007 3:52 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [email protected] Subject: Re: [Sip-implementors] SIP question about "INVITE client transaction"in RFC3261 Hi, It is already reported bug... check the below links, http://bugs.sipit.net/show_bug.cgi?id=706 https://lists.cs.columbia.edu/pipermail/sip-implementors/2003-December/00578 5.html ... Since it is not resolved yet ,the application should handle that. We have to run a specific application timer for this .. any thoughts???? Regds, Balaji Murlitharan.C Aricent "Yong Xin" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 01/06/2007 04:55 AM Please respond to [EMAIL PROTECTED] To <[email protected]> cc [EMAIL PROTECTED] Subject [Sip-implementors] SIP question about "INVITE client transaction"in RFC3261 Hi, I have a SIP question about Figure 5 "INVITE client transaction" in RFC3216 http://www.ietf.org/rfc/rfc3261.txt. It looks to me when the transaction is at "Proceeding" state (i.e.: after client receiving the 1xx response), the only way to move the transaction to next state is to receive final response (200-699). Then what happen if final response is lost, would the client transaction be stuck in this state forever and never terminated? By looking at the text description in section 17.1.1.2, I could not find any clear statement say Timer B should continue at this state or not. How it works if there's no timer? If someone can help me, much appreciated. Thanks, Yong _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors *********************** Aricent-Private *********************** "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors *********************** Aricent-Private *********************** "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
