27.5.7 Re-using TCP Connections
You can enable the SAS application to re-use the same TCP connection for sessions
(multiple SIP requests / responses) with the same SIP UA. The benefits of this feature
include less CPU and memory usage because fewer TCP connections are open and
reduced network congestion. For example, assume User A sends a REGISTER message
to SAS with transport=TCP, and User B sends an INVITE message to A using SAS. In this
scenario, the SAS application forwards the INVITE request using the same TCP
connection that User A initially opened with the REGISTER message.
To re-use TCP connection sessions in SAS
1. Open the SAS Configuration page (Configuration tab > VoIP menu > SAS > Stand
Alone Survivability).
2. From the ‘SAS Connection Reuse' drop-down list, select Enable.
3. Click Submit to apply your changes.
27.5.8 Replacing Contact Header for SIP Messages
You can configure SAS to change the SIP Contact header so that it points to the SAS host.
This ensures that in the message, the top-most SIP Via header and the Contact header
point to the same host.
Notes:
• This feature is applicable only to the SAS Outbound mode.
• The device may become overloaded if this feature is enabled, as all
incoming SIP dialog requests traverse the SAS application.
Currently, this feature can be configured only by the ini file parameter,
SASEnableContactReplace:
[0] (Default): Disable - when relaying requests, SAS adds a new Via header (with the
IP address of the SAS application) as the top-most Via header and retains the original
Contact header. Thus, the top-most Via header and the Contact header point to
different hosts.
To Next Page
Loading...
Need help?
General
