CSCec54778: Dialer port is not registering to the Active CM
Given that Vikram is using 7.2(3), I would suggest that this bug is non-impacting.
Generally speaking, you should register the two dialler port pools across 2 subscribers.
For example, at a recent customer we have a very similar setup to yours, with 2 diallers, with 96 ports per dialler. We have configured all of the odd numbered ports (from both diallers) to be on subscriber 1, and all even numbered ports to be on subscriber 2. This ensures that load is evenly distributed across the CM cluster.
When you say "not registering", do you mean they are not showing up in CM as registering, or not showing up on the ICM side? Have you restarted the dialler and MR PG components after completing the CM config?
I was able to figure out the problem.It was typo error in computername of dialer under outbound in AW machine.But I liked the way you have load balanced your dialer ports to two subscriber.THanks again for this suggestion.
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...