H323 vs. MGCP

Unanswered Question
Oct 23rd, 2008

Currently have 4.x CM with multiple MGCP and H323 Gw's. Will be moving to 6.x probably within a year.

Will be installing 4 more remote GW's in next few months.

Looking for opinions on wheter to use H323, or MGCP. (Outside of the H323 SRST benefits)

Thanks

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
allan.thomas Thu, 10/23/2008 - 06:06

Take an opportunity to look at the following document, it describes and compares both protocols:-

http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note09186a00806fedbe.shtml

The fundamental difference between each protocol is the management. Compared to MGCP, H.323 requires more configuration on the gateway since the gateway must maintain the dial plan and route patterns.

This will be required across all H.323 gateway, whereas with MGCP it will be more centralised.

HTH

Allan.

allan.thomas Thu, 10/23/2008 - 06:21

Further to my previous post, one other consideration that I did not mentioned, and that was the fact that MGCP does not offer incoming call blocking.

With H323 you can configure the Dial-peer to match using the ANI. This option is not available with MGCP as the call control with the CallManager. As is stands it is not possible to route calls based on Calling Party Number.

HTH

Allan.

Actions

This Discussion