ConfOutboundProxyDN

Configuring the Outbound Proxy DN

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

Configure the following mandatory options in the Annex (Options) tab, in the TServer section:

Name	Value	Notes
oos-check	3	These two options 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.
oos-force	5
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. 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 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