The cluster switch must contain one Outbound Proxy DN. All SIP Server and SIP Proxy applications in the cluster use the parameters configured under this DN.
In the Annex tab, TServer section, configure the following (mandatory options):
| Name | Value | Key Info |
|---|---|---|
| oos-check | 3 | |
| oos-force | 5 | These two options (oos-check and oos-force) enable active out-of-service detection. In this specific example, SIP Server is checking for proxies (by using value of the contact option) every 3 seconds and sets them in the out-of-service state 5 seconds after the last check that was not responded. |
| service-type | sip-outbound-proxy | |
| contact | FQDN of SIP Proxy resolved to SRV list | Set this option to the Fully Qualified Domain Name (FQDN), which 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. To localize SIP traffic inside one data center, this FQDN must be resolved to different sets of SIP Proxies based on geo-location: in other words, SIP Server should be aware only about those SIP Proxy instances installed in the same data center where SIP Server resides. |
| external-contact | FQDN of SIP Proxy resolved to A-record (host:port) | Set this option to the FQDN used by the SIP phones to access the SIP Proxy instances in the cluster. Use the following format: host:port Where host is an 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. |