Configuring SIP Cluster Switch and DNs

Step 1: Configuring the SIP Cluster Switch

1. Create a single Switch object of type SIP Switch for the entire cluster. When configuring this switch, keep the following rules in mind:

• Do not configure Extension or ACD Position DNs in the switch. Endpoint DNs are configured in SIP Feature Server instead. ?
• Do not configure Agent Logins in the switch. Agent configuration is also handled in SIP Feature Server.
• ACD Queue DNs are not supported in the cluster.
• Other DNs are still configured in the switch. For example, Trunk, Trunk Group, Voice over IP Service, Virtual Queue, Routing Point DNs.
• All SIP Server applications running in the cluster must use the same switch.

For details about configuring a SIP Server Switch object, see the Framework 8.1 SIP Server Deployment Guide.

Step 2: Configuring the Cluster Node DN

The cluster switch must contain one Cluster Node DN. All SIP Server and SIP Proxy applications in the cluster use the parameters configured in this DN.

1. Create a DN of type Voice over IP Service named, for example, sip-cluster-nodes.
2. In the Options > TServer section, configure the following mandatory options:

Name	Value	Notes
addp-trace	full
addp-remote-timeout	11?	T-Controller link ADDP protocol setting.
addp-timeout	7?	T-Controller link ADDP protocol setting.
applications	A comma-separated list of primary SIP Server application names in the cluster.	All SIP Server instances for all data centers.
dn-owner-applications (dn-ownership-termination-timeout?)	A comma-separated list of application names that can take DN ownership for a node.	The application name is sent to SIP Server as AttributeApplicationName in TRegisterClient.
sipproxy-applications	A comma-separated list of all SIP Proxy application names in the cluster.	All SIP Proxy instances for all data centers.
service-type	sip-cluster-nodes
node-startup-delay ?

Step 3: Configuring the SIP Outbound Proxy DN

The cluster switch must contain one SIP Outbound Proxy DN. All SIP Server and SIP Proxy applications in the cluster use the parameters configured in this DN.

1. Create a DN of type Voice over IP Service named, for example, sip-outbound-proxy.
2. In the Options > TServer section, configure the following mandatory options:

Name	Value	Notes
contact	FQDN of SIP Proxy resolved to SRV list	Set this option to the Fully Qualified Domain Name (FQDN) that resolves to the SRV list of the SIP Proxy addresses. SIP Server uses this list to load-balance the traffic across all SIP Proxy instances. If there are multiple data centers within the cluster, or to localize outgoing SIP traffic inside one data center for SIP Servers from different data centers, this FQDN must be resolved to different sets of SIP Proxy addresses based on their geographical location. In other words, SIP Server should be aware only of those SIP Proxy instances installed in the same data center where SIP Server resides. It is the responsibility of the DNS to make this differentiation.
external-contact	FQDN of SIP Proxy resolved to A-record (host:port)	Set this option to the FQDN used by SIP phones to access the SIP Proxy instances in the cluster. Use the following format:  host:port where: host is the FQDN that can be resolved using DNS to a list of SIP Proxy IP addresses (DNS A records). port is the TCP/IP port that SIP Proxy uses to listen for SIP messages from SIP phones (all SIP Proxy instances listen on the same port). For example,  anyproxy.DnsServer.com:7018
oos-check	3	These two options enable active out-of-service detection. In this specific example, SIP Server is checking for SIP Proxies (by using the value of the contact option) every 3 seconds and sets them in the out-of-service state 5 seconds after the last check for which a response was not received.
oos-force	5
service-type	sip-outbound-proxy

Step 4: Configuring dial-plan DNs

The cluster switch might contain one or more dial plan DNs. A typical cluster deployment will have one dial plan DN configured for each data center.

1. Create a DN of type Voice over IP Service named dial-plan.
2. In the Options > TServer section, configure the following mandatory options:

Name	Value	Notes
service-type	feature-server
url	URL of a local SIP Feature Server	Set this option to the URL for the local SIP Feature Server in this data center. For example,    http://myhost:8800 If there is more than one SIP Feature Server in the data center, create as many url options as needed to accommodate all of their addresses in one DN. The first option must always be named url. All consecutive options must be named url-<n>. For example,    url=http://myhost:8800    url-1=http://myhost1:8800    url-2=http://myhost2:8800
geo-location	Data center	Enter a string identifying the data center to which this DN belongs.

Step 5: Configuring Voicemail DNs

1. Create a DN of type Voice over IP Service with DN names the same as the DIDs configured. Create one DN for each Resource Manager (RM) instance.
2. In the Options > TServer section, configure the following options:

Name	Value	Notes
contact	::msml
service-type	voicemail
geo-location

Step 6: Configuring MSML DNs

1. Create a DN of type Voice over IP Service named, for example, msml, for each data center containing contacts of all RMs in the environment, by completing the following steps:
2. In the Options > TServer section, configure the following configuration options:

Name	Value	Notes
service-type	msml
contact	sip:<IP address of RM>:<port>	For a single RM, set this option to the contact information of the RM in the specified format.
contact-list	sip:<IP address of RM1>:<port>;sip:<IP address of RM2>:<port>	For multiple RMs, set this option to the contact information of all RMs in the specifed format.
geo-location

Step 7: Configuring Device Profile DNs

The cluster switch can support multiple device-profile DNs. These DNs are used to configure the DN-level parameters that SIP Server dynamically assigns to the device participating in a call.

1. Create a DN of type Voice over IP Service named, for example, device-profile.
2. In the Options > TServer section, configure the following options:

Name	Value	Notes
service-type	device-profile
profile-id	Enter a value to identify this profile	SIP Server assigns the profile to a device by matching this value to the content of the User-Agent header in the SIP message. If no device profile is found, then a default device is created (in other words, all device parameters will have default values). The value of the profile-id option must either match the value of the User-Agent header or it can be defined as a substring which can be found in the User-Agent header.

Notes:

• The string is case-sensitive.
• There is no default value.
• Changes take effect for the next call.
• You can set profile-id to the special value of default-profile. SIP Server uses this profile to handle any device that includes the User-Agent header in its SIP messages (and so cannot be used to match a specific device profile).

A Device Profile DN, set to the default-profile

Step 8: Configuring other DNs

Configure Trunk, Trunk Group, and Media Service (Voice over IP Service) DNs as follows:

• Set the contact option to a valid URI of the device (Trunk, Trunk Group, or Media Service).

Note: For additional configuration options that might be configured for a particular device, see the Framework 8.1 SIP Server Deployment Guide.