CMM 1 unregistered this morning, but calls did use CMM2??
I have (2) CMM's modules in different 6500s. Each CMM has (2) PRIs in it. The PRI's in CMM1 unregistered with CCM this morning. I figured no big deal, calls should go out CMM2 with the (2) other PRIs. Calls did not.
In my route Priority list, I have
So I changed the order of priority, and it still would not route calls out CMM2, still forcing CMM1.
Is there a flaw here? If the CMM1 unregistered and CMM2 is regestered, wouldnt CCM route calls to the CMM2? Did I miss a config somewhere in my cluster why this did not failover?
Re: CMM 1 unregistered this morning, but calls did use CMM2??
Not sure what was the status for the GW, the unregistration was due to an MGCP failure or the T1 circuit itself?
CCM should be aware of that and depending the status in a module called DeviceManager it should take a decision when doing the following process:
RouteListCdrc::selectDevices -- mTemporaryDeviceInfoList.entries = X
Where X is the number of Gateways available.
Could be that that entry contains 2 (CMM1 and CMM2) . Not sure, if u have the detailed CCM trace for the moment we can find out what happened. Also I would change the Stop Routing on Unallocated Number Flag* to False.
I did a test in the lab with an MGCP GW Unregistered (no T1 cable) and a second and worked fine the hunting. (CCM 4.1.2sr1 2 CMMs)
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
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...