In any SIP call scenario, two entities are involoved in the call flow: UAC and UAS. In this exercise, PSTN makes a call to the Lync client over the Sonus SBC 1000/2000, where the Sonus SBC 1000/2000 acts as a UAC and the Lync/SBA acts as a UAS. In our example we are assuming that a Sonus SBC 1000/2000 is integrated in the topology shown below.
This article describes the steps necessary to configure a Sonus SBC 1000/2000 to employ the SIP Timer Functionality in the depicted topology:
Topology |
---|
The configuration process comprises of two overall steps:
Configure the Session Timer as shown in the figure below.
Important: The Offered Session Timer value must be equal to or greater than the Minimum Acceptable Value.
Click Apply
After having applied the configuration changes, in the call flow, the Sonus SBC 1000/2000 supports the UPDATE and INVITE methods for changing the media capabilities. Session Timer (RFC 4028) uses the INVITE or UPDATE as a mechanism for a periodic refresh of SIP sessions.
Currently the Sonus SBC 1000/2000 supports RTCP-based dead call detection. Session timers provide an alternate methodology for the detection of dead calls using SIP Signaling. If the SIP peer fails to respond to an UPDATE or INVITE message, this enhancement cleans up the call by sending a BYE which will enable the call stateful SIP proxies (Lync/SBA in this example) to clean up the resources associated with the call. Additionally, the relevant DISCONNECT is sent to the PSTN link by the Sonus SBC 1000/2000.
You can verify this using the Log Exchange utility — the following diagram depicts a Sonus SBC 1000/2000 to Lync/SBA call with the Session Timer enabled and in effect: