>> I think a UAS is forbidden to include a Session-Expires header field
>> in the UPDATE request and a UAC should reject it.
>> In that case, the value of session refresher in 200 OK of INVITE MUST
>> be uac.
>
> I'm not sure why you think that it is forbidden.
>
> RFC 4024 table 1 shows that Session-Expires is optional for UPDATE.
> Section
> 13 also shows Session-Expires within an UPDATE.
>
> RFC 4024 section 7.2 indicates the following:
>
> "Similarly, a re-INVITE or UPDATE request sent within a dialog for
> purposes other than session refreshes will also have the effect of
> refreshing the session, and its processing will follow the procedures
> defined in this specification."
>A consequence of this is that if you do a re-INVITE or UPDATE, and fail to
>include Session-Expires, then you are *cancelling* the session timer.
Hi All,
Thanks for your inputs!
However, now I have two queries regarding a similar scenario :
UAC (Caller) UAS(Callee)
------------------- INVITE ---------------------->
(Session-Expires:3600;refresher=uac)
<------------183 Session Progress------------
-----------------PRACK ------------------------>
<------------200 OK (PRACK) ------------------
<-------------------UPDATE--------------------
(Session-Expires:3600;refresher=uac)
----------------200 OK ------------------------>
(Session-Expires:3600;refresher=???)
<--------------- 200 OK (INVITE)----------------
(Session-Expires:3600;refresher= ???)
1. Can the refresher value be changed in the SE header of the above
mentioned UPDATE by Callee ?
2. What are the values that can be sent in 200 Ok( UPDATE) by the caller ?
3. What Callee should send in 200 Ok (INVITE) in the above scenario ?
Best Regards,
Mayank
Aricent
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for
the use of the individual to whom it is addressed. It may contain privileged or
confidential information and should not be circulated or used for any purpose
other than for what it is intended. If you have received this message in error,
please notify the originator immediately. If you are not the intended
recipient, you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message. Aricent accepts
no responsibility for loss or damage arising from the use of the information
transmitted by this email including damage from virus."
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
