Voice Gateway's not registering across VPN

Unanswered Question
Mar 26th, 2008

Does anyone know of any issues that could prevent a Voice Gateway router from registering with a Call Manager across a VPN tunnel? All of our Gateway's that are across Tunnels are failing to register.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Brandon Buffin Wed, 03/26/2008 - 11:31

I'm assuming these are MGCP gateways? Try using the following commands to specify the source address for TFTP (if you're using ccm-manager config download) and MGCP.

ip tftp source-interface

mgcp bind control source-interface

mgcp bind media source-interface

Also be sure that the domain name configured in CCM matches the hostname of the router. Also, if you're using a domain name on the router such as domain.com, you will need hostname.domain.com for the domain name in CCM config.

Hope this helps. If so, please rate the post.


spangdahlemcco Mon, 03/31/2008 - 02:09

Well this issue has been solved. I feel kind of retarded about it though. It is simply because the line to the end point wasn't connected. My thinking was that the gateway should be able to register with the CCM even though the e1 to the avaya wasn't online yet. Apparently if you do a "show ccm" it was registered but it won't show up as registered in the call manager until the e1/t1 is operational.

Maybe this explanation will help people in the future.


This Discussion