Wednesday, January 05, 2011

Find MGCP gateway associated with CUCM NumberOfRegisteredGatewaysDecreased alert

After configuring RTMT NumberOfRegisteredGatewaysDecreased alert to deliver information via email, found associated gateway details are not included in the email. This can be a real problem on larger scale deployments with multiple gateways and no other reporting tools available.

To find the gateway in question:
  1. Freak out when receiving [RTMT-ALERT-StandAloneCluster] NumberOfRegisteredGatewaysDecreased alert.
  2. Hope the traces have been enabled in CUCM. The default Error level on CallManager should be sufficient.
  3. Go to RTMT | Trace & Log Central | Collect Files
  4. Choose Cisco CallManager
  5. Choose Cisco Database Layer Monitor
  6. Set the date and time as close to the alert times as reasonably possible.
  7. Download the files somewhere you can find them.
  8. Search SDL file for DMRemoteDeviceRegisterUnRegister
  9. The last column indicates gateway in question (i.e. S0/SU0@MyRouter:
  10. Fix something.
Of course, your results may vary.


  1. Anonymous1:15 AM

    THANK YOU!!!
    BTW, for the benefit of my fellow Googlers, it is probably worth having the search term MGCP on this page, since it is in regards to MGCP gateways after all. There, I said it twice.

  2. You're welcome. As my little gift to the Googles, I added MGCP to the title.

  3. Anonymous4:54 PM

    It's unbelievable that we're still in the same situation where there is no way of modifying an alert to tell you which gateway is having the issue. From recent interaction with Cisco support here's what they told me:
    **Checked the RTMT as you were getting the alerts of gateway increased/decreased.
    **You wanted to set the tool to have the information which gateway is producing this alert to which gateway, which is not possible in the RTMT.
    **Collected the Sys and Application logs to check the errors (there are the Event Viewer-Application Log and System Log).
    Then the engineer told me one can't possibly decypher them, so I have to send them in so they can read them for me.
    Really Cisco?

  4. For what it's worth, I've suggested a feature enhancement through Cisco's Communities CallManager User Group. Cross your fingers. Do NOT hold your breathe.

  5. Anonymous6:45 PM

    This does not seem to output the desired results on CUCM 9.x