Setting 200 OK’s Session-Expire: value

The session timer is based on the negotiation between each side’s session expires value. The final value on the ingress leg is returned by the Oracle Communications Session Border Controller to the UAC, unless there is an error.

The Oracle Communications Session Border Controller can always reduce the session expires value it returns to the UAC. It checks that the Session-Expires: header is larger than the SIP Interface’s min-se value. The Oracle Communications Session Border Controller then compares the received Session-Expires: header to the configured session-expires configuration element and uses the lower value for the 200 OK’s Session-Expires: header. If this outbound Session-Expires: value is lower than the received Min-SE: header, it will be bumped up to the Min-SE: header’s value.

If the Oracle Communications Session Border Controller’s Min-SE value is larger than the Session-Expires: header, a 422 (Session Interval Too Small) message is returned to the UAC containing the Oracle Communications Session Border Controller’s configured Min-SE value.

When the UAC supports (but does not require) Session Timers and the Oracle Communications Session Border Controller does not support session timers, a 200 OK is returned to the UAC with no indication of session timer support.