Issue with CUCME and Exchange 2013 Unified Messaging
We have had an issue where we could only reach our Exchange UM server if we pointed the dial-peer directly to the mailbox listening port rather than the call router port.
Exchange 2010 and 2013 should both accept a SIP connection to a CAS running Unified Messaging on either port 5060 or 5061 by default. The CAS which runs the UM call routing service will then send a SIP redirect to CUCME or the SIP phone with the IP and port of the mailbox server.
This was not working correctly in our installation due to CUCME's max-redirect having a default of 1 for any dial-peer unless the value is changed. Exchange was sending the redirect correctly but the lack of "max-redirects X" was causing the redirect to fail.
We set ours to 10, which fixes the issue. We have submitted a question to TAC to explore the ramifications of setting it so high. Since we were unable to find a solution when searching for a solution, we wanted to post this so that others may not have to spend as much time as us. It may have been a "rookie mistake" but I'm sure others will make it.
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...