CM 3.3 Intercluster trunks and Called Name Display
I have 2 CallManager clusters connected via intercluster trunk. One cluster is running CM 3.3.3, the other is on 3.3.2. When a call is initiated from a phone on the 3.3.2 side to a phone on the 3.3.3 side, the Called name displays on the calling phone as soon as the phone starts ringing.
If a phone on the 3.3.3 side calls a phone on the 3.3.2 side, the Called name does not display on the calling phone until the call is answered.
I have checked the settings on the trunks and they are identical. Anyone have any idea why the called-name display behaviors are different?
Re: CM 3.3 Intercluster trunks and Called Name Display
Similar scenerio for me except my CallManager cluster release is different. If a phone on the 3.3.3 side calls a phone on the 3.2.(2c) side, the Called name does not display on the calling phone at all. Also, the party calling from 3.3.3 to 3.2(2c) never gets the called name display. However, Calling name display does work between the two clusters if the call is originated in 3.2(2c).
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...