Configuring SIP Server

A single SIP Server HA pair in the cluster is called a SIP Server Node. You must configure each SIP Server application by completing the following steps:

Configuring SIP Server

Configuring Server Info

For each SIP Server instance in the cluster node, you must configure listening ports for the T-Controller and Interaction Proxy modules:

1. Create a new port for T-Controller. Click Add Port and assign the following information:
   • ID—Enter TCport.
   • Listening Port—Enter an available port number.
   • Connection Protocol—Enter TController.
2. Create a new port for Interaction Proxy.
   • ID—Enter IPport.
   • Listening Port—Enter an available port number.
   • Connection Protocol—Enter IProxy.

Note: All names are case-sensitive.

Configuring SIP Server options

For each SIP Server instance in the cluster node, in the Options >TServer section, configure the following options:

• server-role—Set this option to 5 for SIP Server to run in cluster mode.
• sip-link-type—Set this option to 3 for SIP Server to run in multi-threaded mode.
• geo-location—Enter a string identifying the Data Center to which this SIP Server instance belongs.
  Important: This parameter must be defined for SIP Server to work properly in cluster mode. All applications deployed in the same data center use the same value for this geo-location parameter.
• sip-address—This existing SIP Server option is mandatory in cluster mode. SIP Server uses this parameter to build the Via and Contact headers in SIP messages.
• sip-outbound-proxy—Set this option to true.
• sip-enable-gdns—Set this option to true.
• sip-enable-rfc3263—Set this option to true.
• gdns-verbose-level—In the Log section, set this option to 4 to enable GDNS logs. This is an optional parameter, used to troubleshoot DNS-related scenarios.
• dial-plan—Set this option to the name of the Dial Plan DN (VoIP Service DN with service-type set to extended) to be used by this SIP Server application.

For each SIP Server instance in the cluster node, in the Options > extrouter section, configure the following option:

• cluster-role—Set this mandatory option to one of the following values:
  • iscc-node—For each SIP Server instance that does not act as a proxy in a SIP cluster environment.
  • iscc-proxy—For each SIP Server instance that acts as a proxy in a SIP cluster environment.
    

Note: The cluster-role option must be never set to off (the default) in a SIP cluster environment.

Configuring multi-site call handling

The following configuration options support multi-site call handling:

1. SIP Server Application > extrouter section:

• cluster-role—Ensure this mandatory option is set to one of the following values:
  • iscc-node—For each SIP Server instance that does not act as a proxy in a SIP cluster environment.
  • iscc-proxy—For each SIP Server instance that acts as a proxy in a SIP cluster environment.
    

Note: The cluster-role option must be never set to off (the default) in a SIP cluster environment.

• proxy-name—Specify the name of the primary SIP Server application. Mandatory option for SIP Servers with the cluster-role set to iscc-proxy.
• pct-ci-req-tout—Specify the time interval during which SIP Server waits for call data requested for a call that originated at another site.
• pct-rci-tout—Specify the time interval that SIP Server waits for call data from other SIP Server transactions.

2. SIP Cluster Switch > DN of type External Routing Point > TServer section:

• proxy-name—Specify the name of the primary SIP Server application that is used for association of External Routing Point resources.

Mandatory configuration steps:

• SIP Server that is acting as ISCC proxy (cluster-role=iscc-proxy) must have configured the ISCC connection to all SIP Server instances in the cluster and to external T-Servers/SIP Servers that it serves. And vice versa, all SIP Server instances must have configured the ISCC connection to each SIP Server acting as ISCC proxy.

• To provide the ISCC functionality between external T-Servers/SIP Servers and SIP Servers in the cluster, the external T-Servers/SIP Servers must have configured the ISCC connection to the SIP Server which serves them (acting as ISCC proxy).

Note: If SIP Server has the cluster-role option set to a value of iscc-proxy and the proxy-name option has a default value (an empty string), SIP Server prints an error message to the SIP Server log and immediately triggers application shutdown.