I have two clusters of CCM, Cluster A and Cluster B connected using ICT (non-gatekeeper controlled). In cluster A, there is an IPIVR using G.711 codec, configured in the same "region" as CCM-A.
A remote branch IP Phone at Cluster B registers to the Cluster B CCM-B. This remote branch uses G.729. When the remote branch IP Phone tries to reach the IPIVR at cluster A (via ICT), a fast busy tone is heard.
If i change the remote branch "region" to be the same as CCM-B, then the call gets through, so it has something to do with codecs.
I undo the above "region" changes. When i check the "MTP required" checkbox when configuring the ICT, the call gets through, but it uses up hardware transcoder at the gateway.
Can someone help me to understand why is there a need to check the "MTP required" check box ? If i dun check the "MTP required" check box, can i still get it to work ?
You definitely need a transcoder in this case, because IP-IVR most likely supports only g711 codec and your phones at branch use g729 to talk to rest of the world. When you use MTP checkbox, since your phone is negotiating g729, and IVR supports only g711, the trunk will look in its MRGL for an available MTP. MTP can be software based (g711 only) in Callmanager or MTP can be a trancoder (hardware device, which can do any codec). In this case
a. either you have no MRGL configured on the Trunk or device pool level and your hardware transcoders are not in a MRG, because of which Callmanager selects the first available hardware MTP resource
b. Or you have a MRGL configured under the trunk (or device pool level) which has a hardware transcoder in the list (group).
So you definitely need a transcoder to make this call to work or use g711 for just the calls between the phone and IPIVR.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.