This document describes the configuration of the Cisco Unified Communications Manager (CUCM) SPA Interface Processor (SIP) Trunk with the Domain Name System Server (DNS SRV) record of the IM & Presence.
For High Availability purposes, multiple IM & Presence server node destinations are configured in the IM & Presence Publish trunk of CUCM. A maximum of 16 destination IP addresses can be added in the SIP Trunk configuration. However, administrators prefer the use of SRV records instead of IP addresses, as SRV records are easier to manage. SRV records are populated in the DNS server, and thus centralized management is achieved when you point the SIP trunk destination to the DNS SRV record.
Cisco recommends that you have knowledge of these topics:
The information in this document is based on these software and hardware versions:
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Complete these steps in order to configure the DNS server:
In this example, the CUCM and IM & Presence sub-domains were created in the test lab for demonstration.
In the test lab, the domains are:
In order to verify SRV lookup from a Microsoft Windows command prompt, enter the nslookup command.
nslookup
set type=srv
sip._tcp.cup.domain.com
For example, refer to this code example:
Complete these steps in order to configure the CUCM server:
Complete these steps in order to configure the IM & Presence server:
From the IM & Presence server administration page, select Presence > Presence Gateway. Configure a CUCM PRESENCE gateway as shown here.
This configuration specifies the servers from where Phone presence is accepted.
This section provides information in regards to signalling between the different components involved in this configuration.
There is currently no verification procedure available for this configuration.
There is currently no specific troubleshooting information available for this configuration.
Revision | Publish Date | Comments |
---|---|---|
1.0 |
20-Nov-2014 |
Initial Release |