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 th
The registration deadline for SIPit 30 is February 4, just over two
weeks away.
If you plan to attend, but have not yet registered, please do so today.
Note that we will be testing against RTCWeb implementations during
Tuesdays multiparty test.
See www.sipit.net for more info.
RJS
On 11/26/12
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
___
Hi Deepak,
If the UPDATE contains neither SDP nor session refress parameter(timer). I
guess you can respond with 200 OK.
What is the harm in replying with 200 Ok in this case?
Thanks.
On Wed, Jan 16, 2013 at 6:39 PM, Brett Tate wrote:
> RFC 3311 section 5.2:
>
> A UAS that receives an UPDATE
Hi,
Concerning stateless proxy branch generation, the following RFC 3261 bugs
discuss a potential fix.
http://bugs.sipit.net/show_bug.cgi?id=680
http://bugs.sipit.net/show_bug.cgi?id=755
Is copying the topmost Via's branch (which may be missing) into the new Via
still the current recommendati
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 Me
The update message if sent without SDP means that the session parameters
are going to remain same and just the session timers are refreshed. You
need not reject the update if it comes without SDP. But, even in that
case, if the UE receives another Update before it sends a final response
for the f
Hi,
Please see detailed Scenario below:
UAS UAC
<> (Call is established)
< (UPDATE without SDP)
<
Hi Deepak,
You may want to reject the second UPDATE with "491 Request Pending".
Thanks,
Somesh
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of ext
deepak bansal
Sent: Wednesday, January 16, 2013
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
10 matches
Mail list logo
