I have a Call Manager 5.1 trying to establish a MGCP connection with a Cisco 2801. I think that I perform all the steps correctly, but the following message appears: Rejected. Unknown MGCP Gateway. NotEntryinDatabase. It seems that the Gateway configuration doesn?t save correctly in the Call Manager.
One common reason for this to happen is the Name defined on the CallManager is the Hostname of the router and on the Router you have an IP Domain Name configured. The way you need to define the name of CM should be hostname.+domainname.
Router Hostname is 2800
Domain Name is router.local
On CallManager you need to define this as router.local
If this is already done, can you collect the following and attach it here
I made the mistake of changing the CCM servernames to actual names, instead of leaving them as IP addresses. When you change the servers to the hostnames, rather than IP address, MGCP goes and registers it on the MGCP gateway, but then will change the MGCP parameters to the CCM hostname, rather than the IP address you specified in the router config. Unless you have defined DNS everywhere, (including the router) stay away from changing the names of the CCM servers. (forgot which page it was on, something like System/Servers or something like that)
It's funny because I had the router all setup with the correct config. MGCP would register it, then all of sudden deny it. I go into the config and see that the MGCP was changed from IP address of CCM pub and Sub to their actual hostnames. Well, the router does not resolve hostnames that great.
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...