10-06-2013 08:30 AM - edited 03-16-2019 07:44 PM
what is the advantage of using mgcp instead of h323 gw?
i think mgcp supports srtp but h323 not
Solved! Go to Solution.
10-06-2013 09:13 AM
Hi
H.323
-Uses Abstract Syntax Notation 1 (ASN.1) for call control messages
-Uses a peer-to-peer model
-Scales well in an enterprise
-Fractional PRI support
-CallerID support on analog FXO
-Many more TDM interface types and signaling
-Gateway-resident applications like TCL and VXML
-CAC network design with H.323 Gatekeepers
-No release dependencies between GWs and CCM
-Call preservation for SRST on PRIs
MGCP
-Not as mature as H.323
-Uses clear text for call control
-Uses a client-server model
-Ideally positioned for service providers (centrally located call agents)
-Centralized management and control (Dial plan, etc.)
-Enhanced call survivability
-Better feature interaction with capabilities like CallerID
-Support of QSIG supplementary services with CCM
Thank you
please rate all useful information
10-06-2013 08:48 AM
Hi PC,
In case of MGCP, it is like a Client server relationship, which involved doing most of the configuration on Call manager and avoiding configuration of dial peers on routers. doing min. config on VG router.
In H.323 , u need to configure the VG fully.
regds,
aman
10-06-2013 09:05 AM
Hi PC,
SRTP is supported on both MGCP and H.323 .
I was just referring the link
for SRTP on H.323
http://www.cisco.com/en/US/docs/ios/12_4t/12_4t11/htsecure.html
for SRTP on MGCP
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/security/4_2_3/secumgcp.html
regds,
aman
regds,
aman
09-01-2015 09:44 PM
All,
09-02-2015 08:01 AM
I agree with the first point on your list, but the remaining 3 are unfortunately false, both SIP and H323 support all 3 of them.
09-03-2015 07:05 PM
Thanks for the Correction Chris.
10-06-2013 09:12 AM
Hi
Please also find the below links:-
http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note09186a00806fedbe.shtml
http://www.packetizer.com/ipmc/h323_vs_sip/ataglance.html
Thank you
please rate all useful information
10-06-2013 09:13 AM
Hi
H.323
-Uses Abstract Syntax Notation 1 (ASN.1) for call control messages
-Uses a peer-to-peer model
-Scales well in an enterprise
-Fractional PRI support
-CallerID support on analog FXO
-Many more TDM interface types and signaling
-Gateway-resident applications like TCL and VXML
-CAC network design with H.323 Gatekeepers
-No release dependencies between GWs and CCM
-Call preservation for SRST on PRIs
MGCP
-Not as mature as H.323
-Uses clear text for call control
-Uses a client-server model
-Ideally positioned for service providers (centrally located call agents)
-Centralized management and control (Dial plan, etc.)
-Enhanced call survivability
-Better feature interaction with capabilities like CallerID
-Support of QSIG supplementary services with CCM
Thank you
please rate all useful information
10-06-2013 11:46 AM
The only advantage of MGCP is really the configuration simplicity for the admin as you control the GW in CUCM. With that said I would and never did recommend MGCP for any deployments as it is very prone to many unexplained issues. Go with SIP for voice gateway control for all deployments. H323 would be a second option.
HTH,
Chris
10-06-2013 05:25 PM
I go with you on that one Chris!
also I would like to add, and this is my personal opinion, that H323 and especially SIP is much easier to diagnose than MGCP.
=============================
Please remember to rate useful posts, by clicking on the stars below.
=============================
10-07-2013 12:08 AM
For ease of configuration, MGCP is best.
For doing clever stuff (or ensuring CUCM doesn't play with your IOS configuration), H.323 or SIP are best.
GTG
Please rate all helpful posts.
10-07-2013 01:48 AM
+5 to All...
This is the classic interview question In addition to all that has been said...MGCP is a dying protocol. I dont see any reason why anyone wants to use it apart from Qsig functionality. Cant even remember last time I deployed it. H323 is in similar territory. No further development on it. Still much better than MGCP due to the flexibility you have in terms of call routing etc. SIP is the present and the future, go with it.
Please rate all useful posts
"opportunity is a haughty goddess who waste no time with those who are unprepared"
10-07-2013 05:00 AM
HI ALL,
Amanso@ I would like to tell MGCP is a Call manager centric.
If we use MGCP each and every instruction will be provided by Call manger.
H323: It has its own brain (Dial peer and all......)
Can any one share a link of SIP Protocol.
10-07-2013 11:47 AM
Hi,
there is an advantage for MGCP over SIP and H323. MGCP can preserve the active call and keep it up when the call manager goes down and the phone register to the subscriber.
I prefer H323 and SIP due to the troubleshooting capabilities
HTH
Anas
please
10-07-2013 11:51 AM
H323 and SIP can do call preservation as well. In fact does it a lot better than MGCP for PRI circuits as the D-channel is not back-hauled, so a call can be preserved even when falling into SRST and not just when a server fails.
HTH,
Chris
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: