Hi Aakash,
According to the current RFC, UAs can not start another negotiation of
the session timer during the early dialog.
Regards,
Shinji
On 2020/12/05 1:03, akashdeep vishnoi wrote:
Hi,
I have a little confusion in this :
--------------------------------
Errata ID: 4744
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Chao Wang
Date Reported: 2016-07-19
Section 3 says:
A UAC starts by sending an INVITE. This includes a Supported header field
with the option tag 'timer', indicating support for this extension
It should say:
A UAC starts by sending an INVITE. This includes a Supported header field
with the option tag 'timer', indicating support for this extension.If UAC
or UAS knows one negotiation of session timer is ongoing, it SHALL not
start a new one.
-------------------------------------------------------------------------------
As per above explanation, I want to know if* Session Expire timer value can
be changed by UAS/UAC by sending early UPDATE* before Call is established
when INVITE request already has one timer value.
Thanks,
Aakash
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
