Hello Uri , You should actually do nothing if the timer B fires in the proceeding state , This is because u have already received a provisional response for the INVITE if you are in proceeding state , Once u r in proceeding state u can do one of the following 1>Stop Timer B 2>Or just let it run and fire but don't take any action.
SIP does not define any "ring timeout" , depending on your application you can define it yourself if u want. HTH , Sayan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Baniel Uri-CUB001 Sent: Tuesday, August 08, 2006 10:28 PM To: [email protected] Subject: [Sip-implementors] Timer B for INVITE transaction RFC 3261 section 17.1.1.2 does not seem to define what to do when the client transaction is still in the "proceeding" state when timer B fires... I'd think the client should go to the "Terminated" state just as if timer B had expired while in the "calling" state, otherwise the client can get hung there forever... Agree? -uri _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
