One- I assumed that the IP address CUCM was seeing for the port on the gateway was reflective of connectivity to that IP address. Troubleshooting finally revealed I had made two very bad assumptions.
#Cisco cucm 8.6 srnd registration
On this particular brain-dead day, I had managed not to make either of these mistakes but was still getting a Registration Rejected error. Here’s an example of what you will be looking at, be sure to confirm part number and location with your router output: With CUCM however, you will likely be greeted with a Registration Rejected message and a raspberry blown in your general direction should you err in your selection. And in that example, the results may be fatal. Extending the previous analogy, saying your girlfriend has blue eyes when they are really green, will not help your cause. If your card is a VIC3-4FXS, selecting a VIC-4FXS in CUCM is not the same thing. This will show you the part number and slot you should be picking. The best way to ensure you are picking the right module, card type, and slot for your gateway from the CUCM drop-down menus is to do a #show diag on the router. The other most common mistake is to pick the wrong module, card type, and/or slot for your gateway in CUCM. This needs to be precise in CUCM or the gateway won’t register – it would be like calling your new girlfriend by your old girlfriend’s name. Your device name will look like if the domain name is set. Go ahead and copy and paste this into CUCM to be sure you have it correct. One, and by far the most common, is to get the device name wrong.Įasiest way to check this is to do a #show ccm-manager on the gateway and see what is listed as the device name in the output.
There are (at least) two common errors when it comes to MGCP port configuration. So once you’ve checked the gateway configuration and everything looks kosher, you can move onto checking the CUCM piece of the puzzle. The above configuration allows not only for port 0/2/0 to be controlled via MGCP, but also allows the port to failover to h323 when in SRST mode. Mgcp call-agent 192.168.1.10 service-type mgcp version 0.1
In this particular case, I was configuring a single port on an otherwise h323 gateway as an MGCP port, so my configuration looked something like this: Is MGCP configured and running on your gateway? Sounds simple enough, but easy to miss the actual “turning it on” step. So what makes MGCP ports unhappy enough to reject all caring efforts of devoted voice engineers? We left off the last episode with one registered conference bridge and one snarky MGCP port touting its Registration Rejected message as a badge of honor.
0 kommentar(er)
