> > 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." _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
