To configure the Session Timer feature, you should understand the following concepts:
Interoperability and Compatibility
-
Interoperability--This feature provides a periodic refresh of SIP sessions. The periodic refresh allows user agents and proxies
to monitor the status of a SIP session, preventing hung network resources from pausing indefinitely when network failures
occur.
-
Compatibility--Only one of the two user agent or proxy participants in a call needs to implemented the SIP Session Timer Support
feature. This feature is easily compatible with older SIP networks. The SIP Session Timer Support feature also adds two new
general headers that are used to negotiate the value of the refresh interval.
Role of the User Agents
The initial INVITE request establishes the duration of the session and may include a Session-Expires header and a Min-SE header.
These headers indicate the session timer value required by the user agent client (UAC). A receiving user agent server (UAS)
or proxy can lower the session timer value, but not lower than the value of the Min-SE header. If the session timer duration
is lower than the configured minimum, the proxy or UAS can also send out a 422 response message. If the UAS or proxy finds
that the session timer value is acceptable, it copies the Session-Expires header into the 2xx
class response.
A UAS or proxy can insert a Session-Expires header in the INVITE if the UAC did not include one. Thus a UAC can receive a
Session-Expires header in a response even if none was present in the request.
In the 2xx
response, the refresher parameter in the Session-Expires header indicates who performs the re-INVITES. For example, if the parameter contains the
value UAC
, the UAC performs the refreshes. For compatibility issues, only one of the two user agents needs to support the session timer
feature, and in that case, the UA that supports the feature performs the refreshes. The other UA interprets the refreshes
as repetitive INVITEs and ignores them.
Re-INVITEs are processed identically to INVITE requests, but go out in predetermined session intervals. Re-INVITEs carry the
new session expiration time. The UA responsible for generating re-INVITE requests sends a re-INVITE out before the session
expires. If there is no response, the UA sends a BYE request to terminate the call before session expiration. If a re-INVITE
is not sent before the session expiration, either the UAC or the UAS can send a BYE.
If the 2xx
response does not contain a Session-Expires header, there is no session expiration and re-INVITES do not need to be sent.
Session-Expires Header
The Session-Expires header conveys the session interval for a SIP call. It is placed in an INVITE request and is allowed in
any 2xx
class response to an INVITE. Its presence indicates that the UAC wants to use the session timer for this call. Unlike the
SIP-Expires header, it can contain only a delta-time, which is the current time, plus the session interval from the response.
For example, if a UAS generates a 200 OK response to a re-INVITE that contained a Session-Expires header with a value of 1800
seconds (30 minutes), the UAS computes the session expiration as 30 minutes after the time when the 200 OK response was sent.
For each proxy, the session expiration is 30 minutes after the time when the 2xx
was received or sent. For the UAC, the expiration time is 30 minutes after the receipt of the final response.
The recommended value for the Session-Expires header is 1800 seconds.
The syntax of the Session-Expires header is:
Session-Expires = ("Session-Expires" |
"x"
) ":" delta-seconds
[refresher]
refresher = ";" "refresher" "=" "UAS"|"UAC"
The refresher parameter is optional in the initial INVITE, although the UAC can set it to UAC
to indicate that it will do the refreshes. The 200 OK response must have the refresher parameter set.
Min-SE Header
Because of the processing load of INVITE requests you can configure a minimum timer value that the proxy, UAC, and UAS can
accept. The proxy, UAC, and UAS. The min-se command sets the minimum timer, and it is conveyed in the Min-SE header in the initial INVITE request.
When making a call, the presence of the Min-SE header informs the UAS and any proxies of the minimum value that the UAC accepts
for the session timer duration, in seconds. The default value is 1800 seconds (30 minutes). By not reducing the session timer
below the value set, the UAS and proxies prevent the UAC from having to reject a call with a 422 error. Once set, the min-se command value affects all calls originated by the router. If the Min-SE header is not present, the UA accepts any value.
The syntax of the Min-SE header is:
Min-SE = "Min-SE" ":" delta-seconds
422 Response Message
If the value of the Session-Expires header is too small, the UAS or proxy rejects the call with a 422 Session Timer Too Small
response message. With the 422 response message, the proxy or UAS includes a Min-SE header indicating the minimum session
value it can accept. The UAC may then retry the call with a larger session timer value.
If a 422 response message is received after an INVITE request, the UAC can retry the INVITE.
Supported and Require Headers
The presence of the timer argument in the Supported header indicates that the UA supports the SIP session timer. The presence of the timer argument in the Require header indicates that the opposite UA must support the SIP session timer for the call to be successful.
Feedback