Note that there really isn't any need for UAC or UAS to request session
timer for their own benefit. (Since they can do a reinvite any time they
want to test the session.) It is really for the benefit of proxies in
the path. If the S-E header is omitted from the reinvite, and there is a
proxy on the path that needs session timer, it will presumably add a S-E
header. If the reinvite reaches the other UA without an S-E present then
presumably nobody needs it any longer, so there is no reason for it to
insert an S-E value.
Paul
Brett Tate wrote:
> For clarity, your example is using UAC as "session originator" instead of
> the RFC 3261 definition.
>
>
>
>>UAS send re-INVITE without session-expires header to modify
>>session attribute. (This request has supported header field
>>with the option tag 'timer')
>>When UAC receives this request, how does UAC behave?
>
>
> If it wants to keep Session-Expires active, it adds Session-Expires when
> sending the 200 response.
>
> If the 200 response does not contain Session-Expires, the devices have
> negotiated to no longer use the session timer mechanism on the dialog.
>
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
