In the lab I have a CUCM 7.x system successfully integrated with E2K7SP1.
The SIP Trunk is using TCP (not TLS) and works if I code the IP or the FQDN of the E2K7 UM node.
If I create a SRV record in MS DNS with a priority/weight of 0/0, a port of 5060, and point it at the same A record FQDN as used above I cannot get CUCM to successfully use the SRV.
A nslookup from another client using the same DNS server returns the right results.
"A" record exchange.lab.local = 192.168.2.100
SRV record _sipe2k7._tcp.lab.local is given a weight of 0, a priority of 0, a port of 5060, and is associated to the "A" record of exchange.lab.local.
On the SIP trunk that is working using an IP of 192.168.2.100 or a DNS name of exchange.lab.local, I enter the SRV record of _sipe2k7._tcp.lab.local, check the checkbox for SRV, watch the port automatically change to 0, save, apply, and reset the trunk, and the trunk is no longer usable.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...