Brett,
Your response and the section from the draft confirm my previous
point. With session expires successfully negotiated and with the UAC as
the refresher (even if it is not) if it sends a refresh, reINVITE |
UPDATE, without the Session-Expires from it's point of view it is negotiating the
expires feature off. What the Proxy
is capable and willing to do and what the UAS is willing to do is up to
them.
Regards - Wayne D.
> > Sending a re-INVITE or UPDATE without
> > a session-expires does not deactivate
> > the session timer. It only indicates
> > that the uac prefers not to keep it
> > active. Proxies and/or the uas can
> > still add the session-expires to keep
> > the functionality active.
>
> Acknowledged that if proxies in the path
> support and want to negotiate the timer
> they can. But, if none do, then performing
> such a refresh turns off the feature
> 'no expiration' and no subsequent refreshes
> will be performed. In this case I do not
> distinguish "uac prefers not to
> keep it active" to "turns the feature off".
The distinction is clearly indicated by draft-ietf-sip-session-timer-15.
Section 9 of draft-ietf-sip-session-timer-15 clearly indicates that the
uas
can still choose to keep the timer functionality active even if the uac
and
proxies did not include session-expires within the re-INVITE/UPDATE.
"If the incoming request contains a Supported header field with a value
'timer' but does not contain a Session-Expires header, the UAC indicated
support for timers, but did not request one. The UAS may request a
session
timer in the 2XX response by including a Session-Expires header field."
******************************************************************************
- NOTICE FROM DIMENSION DATA AUSTRALIA
This message is confidential, and may contain proprietary or legally privileged
information. If you have received this email in error, please notify the sender and
delete it immediately.
Internet communications are not secure. You should scan this message and any
attachments for viruses. Under no circumstances do we accept liability for any loss
or damage which may result from your receipt of this message or any attachments.
******************************************************************************
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
