>> 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 tha
On 3/10/16 6:52 AM, Brett Tate wrote:
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 t
yeah agree with Brett .It should not be forbidden rather should be replied
with SE and refresher parameter.
I think user A should have sent refresher role as UAS instead of UAC in
200ok of UPDATE to clearly say User A is acting as refresher as how he
intended to be refresher in INVITE by putting U
> 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-Expir
Hi,
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.
Regards,
Shinji
>Hello,
>
>I have some queries in the below scenario :
> UAC
