[+] On the Server Info Tab
For each SIP Server instance in the cluster node, you must configure listening ports for the T-Controller and Interaction Proxy modules:
- Create a new port for T-Controller. Click Add Port and assign the following information:
- ID — TCPort
- Listening Port — Enter an available port number.
- Connection Protocol — Enter TController as the protocol.
- Create a new port for Interaction Proxy.
- ID — IPport
- Listening Port — Enter an available port number.
- Connection Protocol — Enter IProxy as the protocol.
Note: All names are case-sensitive.
[+] On the Options Tab
For each SIP Server instance in the cluster node, configure the following options:
- 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.
- sip-link-type — Set this option to 3.
- server-role — Set this option to 5.
- msml-support — Set this option to true. This enables msml for integration with GVP media services.
- dial-plan — Set this option to the name of the Dial Plan DN (Voice over IP Server DN with service-type set to dial-plan to be used by this SIP Server application.
