• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2542
  • Last Modified:

MGCP Registration Problems with Cisco ISR2851 and CCM4.3

I am having problems getting a Cisco router to register with a CallManager.  I am using MGCP for my protocol, and here is my configuration to tie in to the CallManager:

ccm-manager mgcp
ccm-manager music-on-hold
ccm-manager config server 172.31.0.4  
ccm-manager config
!
mgcp
mgcp call-agent UCMPUB01 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp rtp unreachable timeout 1000 action notify
mgcp modem passthrough voip mode nse
mgcp package-capability rtp-package
no mgcp package-capability res-package
mgcp package-capability sst-package
no mgcp package-capability fxr-package
mgcp package-capability pre-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp rtp payload-type g726r16 static
!
mgcp profile default

I understand that the MGCP call-agent should be an IP address for best practices, but as long as it can resolve (which it can), the system can work, it just relies on DNS resolution (which I have hard-coded into the router anyway and in the CallManager).

These are the same configs that Cisco recommends to use (referenced from the Cisco Voice Gateways and Gatekeepers book).  The problem is that it never fully registers with the CallManager.  This is the status I get from the router:

T_2851_01#sho ccm hosts
MGCP Domain Name: T_2851_01.XXXXX.local
Priority        Status                   Host
============================================================
Primary         Registering with CM      UCMPUB01 (172.31.0.4)
First Backup    None                    
Second Backup   None

Has anyone ran across this problem before?  I have looked at Cisco documentation and they have a page for problems like this:  http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00805a316c.shtml

However, my problem is not a domain name problem (they match up between the CallManager and the router.  I have even gone in and removed the domain name association from the router and the CallManager, restarted MGCP and still have the same problem.
0
Husker411
Asked:
Husker411
  • 4
  • 4
1 Solution
 
bfasonCommented:
Check that you have the Gateway named exactly the same on the call manager. I've found this to be the most common cause for this problem. Be sure to check upper/lower case as well.

I've also found it to be a good practice to define the host address on the router in case there is a dns problem. From the config prompt

Router(config)#Ip host UCMPUB01 xxx.xxx.xxx.xxx

Hope this helps
B
0
 
Husker411Author Commented:
Done and done.  I was having domain name unresolvable issues originally on the 2851 when the CCM was sending down the mgcp config with the hostname inside of it.  So the host is already configured in the 2851.

As for the naming convention on the router, I can always try a different name (maybe the underscores are having issues with the registration).  I don't think that's the problem, but hey, at this point anything is worth a try.
0
 
bfasonCommented:
When you named the gateway on the callmanager did you include the xxxx.local in the name?
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
Husker411Author Commented:
No I didn't.  It was just ip host ucmpub01 172.31.0.4.  It's all right, though, my registration problems are taken care of.  I had a Cisco tech connect in and make some changes to the system.

In the end, the configuration was the same pretty much as before (I'm still using hostnames instead of IP address but the system works and that's what is important).  Here's what it looks like:

ip domain name XXXX.com
ip host UCMPUB01 172.31.0.4

ccm-manager mgcp
ccm-manager music-on-hold
ccm-manager config server 172.31.0.4  
ccm-manager config
!
mgcp
mgcp call-agent UCMPUB01 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp rtp unreachable timeout 1000 action notify
mgcp modem passthrough voip mode nse
mgcp package-capability rtp-package
no mgcp package-capability res-package
mgcp package-capability sst-package
no mgcp package-capability fxr-package
mgcp package-capability pre-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp rtp payload-type g726r16 static
mgcp bind control source-interface GigabitEthernet0/0.2
mgcp bind media source-interface GigabitEthernet0/0.2
!        
mgcp profile default

And here's what I was trying to get all along...

routername#sho ccm hosts
MGCP Domain Name: routername.XXXX.com
Priority        Status                   Host
============================================================
Primary         Registered               UCMPUB01 (172.31.0.4)
First Backup    None                    
Second Backup   None                    

In the end, what I believe tripped the registration was a combination of going in and configuring a T1 port for PRI and the removal and re-addition of the "ccm-manager config" command.  This triggered another download of the config from the CallManager.

Incidentally, another place to look for problems on this issue are...in the CallManager!  Yes, I know, Captain Obvious, right?  Anyway, check the event logs and I get an event id 3 saying "a transient device is attempting to connect".  Which is Cisco's safeguard against rogue MGCP gateways and a good thing to have, but since the config wasn't re-initialized, the server didn't know it should actually be talking to it.
0
 
bfasonCommented:
Great, glad this is working for you.
0
 
bfasonCommented:
Since I'm the only one that responded I'm giving my ok to paq with a full refund on points.
0
 
Husker411Author Commented:
bfason, thanks for your help in this matter.  Since you were the only one to attempt to give a solution to this matter (which I think should have been possible for many Cisco VoIP experts in this forum to at least attempt), I bump the points up and award you all of them.
0
 
Husker411Author Commented:
I didn't read your question correctly before.  Yes, I did use the xxx.domainname in the CallManager configuration.  I thought you were referring to the router config when I first read it.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now