I want to used the Cisco 7960G ip phone to run MGCP,but I can't get the dial tone in the 7960G ip phone.Now I have a Cisco Call Manager(call agent),Cisco 3745(MGCP Gateway) and four Cisco 7960G ip phone.How can I config ? Thanks a lot.
MGCP is a protocol used between Call Manager and Gateways (routers, etc).
The IP phone will register with Call Manager directly in this scenario, so Call Manager needs to have this IP phones MAC address configured or auto-registration enabled. If the phone is on a different subnet then routing needs to be in place/working. A DHCP server is also needed so IP Phone can get a IP, unless you staticly configured the network settings on the IP phone. TFTP server as well so phone can get a config file, etc.
The IP phones will run MGCP. But, Call Manager does not support using MGCP to communicate with IP phones. THe main reason why there are SIP and MGCP loads for the IP phones is to allow you to use the phone on almost any call agent. If you want to use MGCP and a Cisco IP phone you will need to get another Call Aganet (like Call Manager) that only supports MGCP on phones. Just like if you wanted to use SIP on your IP phones you will need to use the Cisco SIP Proxy server because, Call Manager does not support SIP at all on 3.3.
So the long answer is you need to use Skinny on your IP phones and MGCP or H.323 on your gateways. Since that is how Call Manager is currently setup.
Thanks your answer a lot.Does this mean that Cisco IP phone load MGCP Firmware(like 7960G) can be used with third-party call agent,but not with Cisco Call Manager ? Does the MGCP gateway(like router) need if I do this ? Thanks a lot.
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.