04-13-2011 10:18 AM - edited 03-16-2019 04:30 AM
Hi,
In the process of converting our branch offices from H323 to MGCP and have hit a road block. It seems that incomming calls on my FXO port are hitting an h323 dial-peer rather than the MGCP dial-peer. If you dial the number it just rings continuosly(possibly in a loop?) Any help with this would be greatly appreciated.
Please see the attached config and debug.
Don
Solved! Go to Solution.
04-13-2011 11:53 AM
seems like matching the H323 dial-peers. Removed these dial-peers and move them to the end of the
config. ie: Brought the MGCP dial-peers ahead.
Advised best practice is to first get all the MGCP config on the router (so dial-peers are
created by CCM, or we do it manually), and then only add other dial-peers.
http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a008010fed1.shtml#to
pic1
cts_Command_Reference_Chapter.html
04-13-2011 10:26 AM
can you please attach
Show ccm-manager
Show mgcp endpoint
debug mgcp pack
debug voice ccapi inout
for a failed call ?
04-13-2011 11:16 AM
04-13-2011 11:53 AM
seems like matching the H323 dial-peers. Removed these dial-peers and move them to the end of the
config. ie: Brought the MGCP dial-peers ahead.
Advised best practice is to first get all the MGCP config on the router (so dial-peers are
created by CCM, or we do it manually), and then only add other dial-peers.
http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a008010fed1.shtml#to
pic1
cts_Command_Reference_Chapter.html
04-13-2011 12:31 PM
Thank you, Yogesh! Call is now hitting the correct peer. I was under the impression that since the interface was MGCP, it would ignore the h323 peers unless in srst mode. Excellent information!
04-13-2011 12:37 PM
Glad it worked .
Thanks for the rating !
Yogesh
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide