The UAC and UAS would start timers of different durations based on the call-id ownership. (see section 5.2 of rfc3311 and sec 14.1 of rfc3261 about error code 491)
Since client and server would be running different timers the request would be rejected with either 491 or 500 depending on the scenario..... Thanks & Regards, Nataraju A.B. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, November 29, 2005 2:53 PM To: [email protected] Subject: [Sip-implementors] UPDATE handling Hi All, In scenario like: * UAC sends UPDATE with offer to UAS. * UAC receives 491 response for UPDATE * UAC starts a timer. When this timer will fire, UAC again attempt to send UPDATE. * When timer is running, UAC receives UPDATE with offer from UAS. What treatment should be given to UPDATE received from UAS while timer is running? [ABN] if the UAS has not generated an offer or no answers to be sent out, it can accept the UPDATE request.... Thanks, Rajpal Confidentiality Notice 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 confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. _______________________________________________ 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
