________________________________
From: praveen dandin [mailto:[EMAIL PROTECTED]
Sent: Friday, January 25, 2008 11:31 AM
To: Brett Tate; [email protected]
Subject: RE: [Sip-implementors] Should 200 OK be sent to UPDATE
received withSession-Expires in early dialog?
Thanks Brett for the information.
I have few more doubts on this:).
1) UAS restarts the session timer on receiving the
UPDATE/reINVITE as a session-refresh request once the call is
established.
[Brett] For clarity, it restarts based on sending the 200
response instead of receiving the request.
However in case of early dialog there is no session-timer
running but a request has arrived at UAS through UAC. In such a case
(with SDP & 100rel & Session-Expires) is it valid for UAS to honour the
Session-Expires in the early UPDATE ( i.e., should UAS renegotiate
Session-timer)?
[Brett] Concerning UPDATE and rfc4028, the rules which apply to
a confirmed dialog also apply to the early dialog. The receiver of
UPDATE can renegotiate session-timer per the receiver's desire and
rfc4028's constraints. The contents of UPDATE 200 is honored.
Can it just not ignore the Session-Expires in early UPDATE and
send 200 OK for UPDATE without the including the Session-Expires header?
[ I am still confused for this particular case. Please reconfirm
even if answered in previous mails. Actually the doubt is regarding
inclusion of SE header in 200 OK for early UPDATE]
[Brett] The lack of Session-Expires within the UPDATE 200
indicates that Session-Expires is disabled. However it might be
subsequently enabled based upon INVITE 200 response.
2) In case of confirmed dialog if UAS gets UPDATE (but not, one
more reINVITE) with SE header while the UAS is processing reINVITE
refresh request, then should UAS send the 4xx-5xx response to such an
UPDATE? [ As per the discussion so far the answer to this question is
NO. If it is otherwise please let me know].
[Brett] The UAS can reject whatever it desires unless an RFC
mandates otherwise. It is the receiver's prerogative to reject the
UPDATE if it does not want to allow the UPDATE to be successfully
processed while there is an outstanding re-INVITE. However depending
upon the importance of the UPDATE, such a rejection might subsequently
cause the dialog to be released or cause poor interoperability.
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
