Hi All,
Thanks all for the Response.
Is it necessary to send a 500 with Retry-After if an Update without SDP is
received when a previous UPDATE has not been yet sent a final response?
Cant we simply send 200 OK in the above case because second UPDATE do not
really pose a conflict.
I was going through PJSIP Open Source code where it mentions below:
/* If UPDATE doesn't contain SDP, just respond with 200/OK.
* This is a valid scenario according to session-timer draft.
*/
Best Regards
Deepak
On Wed, Jan 16, 2013 at 9:11 PM, Pranab Bohra <[email protected]>wrote:
>
> The same applies to re-INVITEs as well.
> 491 is applicable in glare situations, i.e. when UPDATE/re-INVITE sent by
> both the UAs cross each other.
>
> In this case however, UAS MUST respond to the 2nd UPDATE with 500 and may
> respond to the 1st one with 200 OK.
>
> Thanks,
> Pranab
>
> ________________________________________
> From: [email protected] [
> [email protected]] On Behalf Of Brett Tate [
> [email protected]]
> Sent: Wednesday, January 16, 2013 6:39 PM
> To: deepak bansal; sip-implementors
> Subject: Re: [Sip-implementors] Processing Update without SDP when an
> Update is pending
>
> RFC 3311 section 5.2:
>
> A UAS that receives an UPDATE before it has generated a final
> response to a previous UPDATE on the same dialog MUST return a 500
> response to the new UPDATE, and MUST include a Retry-After header
> field with a randomly chosen value between 0 and 10 seconds.
>
>
> > -----Original Message-----
> > From: [email protected] [mailto:sip-
> > [email protected]] On Behalf Of deepak bansal
> > Sent: Wednesday, January 16, 2013 6:16 AM
> > To: sip-implementors
> > Subject: [Sip-implementors] Processing Update without SDP when an
> > Update is pending
> >
> > Hi All,
> >
> > Could you please help me in below Scenario:
> >
> > How UAS should Process an Update received without SDP when an Update is
> > pending i.e. (Previous update has not been yet sent a Final Response)
> >
> > Secondly, How UAS should Process an Update received with SDP when an
> > Update
> > is pending i.e. (Previous update has not been yet sent a Final
> > Response)
>
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
> SASKEN BUSINESS DISCLAIMER: This message may contain confidential,
> proprietary or legally privileged information. In case you are not the
> original intended Recipient of the message, you must not, directly or
> indirectly, use, disclose, distribute, print, or copy any part of this
> message and you are requested to delete it and inform the sender. Any views
> expressed in this message are those of the individual sender unless
> otherwise stated. Nothing contained in this message shall be construed as
> an offer or acceptance of any offer by Sasken Communication Technologies
> Limited ("Sasken") unless sent with that express intent and with due
> authority of Sasken. Sasken has taken enough precautions to prevent the
> spread of viruses. However the company accepts no liability for any damage
> caused by any virus transmitted by this email.
> Read Disclaimer at http://www.sasken.com/extras/mail_disclaimer.html
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
