MGCP vs H323

Unanswered Question
Jul 2nd, 2008

What are the advantages/Disvantages of having MGCP configured compared to H323. How difficult would it be to convert?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Jaime Valencia Wed, 07/02/2008 - 10:27

we already have a doc on that:

MGCP and H.323 Voice Gateway Protocol Comparison

MGCP is easier to configure but has limitations because CCM takes all decisions and only works on DNIS.

H323 requires more configuration because of dial-peers but work with ANI, DNIS and redirect number. you have a lot more control.

it's really not that hard to convert between them, a GW can have both at the same time if you want to handle a PRI with MGCP and other with H323



if this helps, please rate

jcsmith96 Wed, 07/02/2008 - 10:32

If MGCP is configured on the CM what function does the publisher have in the operation. Also, where can I find information on how to configure H323 on the gw?

Jaime Valencia Wed, 07/02/2008 - 10:35

CM takes all decisions of routing, MGCP is master-slave, H323 is peer to peer. have you gone thru the link? that is explained there

Cisco IOS H.323 Gateway Configuration for Use with Cisco CallManager

Cisco IOS H.323 Configuration Guide

Dial Peer Configuration on Voice Gateway Routers

more links are available if you search H323 on CCO.



if this helps, please rate

kalbasha0 Wed, 05/11/2011 - 10:40

Q is this a correct statement

The main reason I would use MGCP over h.323 is for failover.  If you are using a h.323 gateway and your primary callmanager goes down the calls will be dropped.  With mgcp the gateway calls will be failed over to the secondary callmanager and the calls will stay up.

According to H.323 gateway confg

There is 2 VOIP statements apply with a

Session target ipv4: Primary Call manager IP address

And Subscriber IP address

Can you explain?



This Discussion