[cisco-voip] H.323 vs. MGCP Gateway Protocol Selection

[Voll, Scott]

I comes down to what kinds of things you want and don't want to do.  

 

MGCP is easy to manage and use.

 

H323 has more configuration and management, but since it's older,
supports more options.

 

Both can get you redundancy that your looking for.  both through RL and
RG's 

 

As far as the Nortel, I have not used it so you might get a more
definitive answer that way.  Most PBX integrations are Qsig PRI that
I've seen.

 

Scott 

 

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Neil Barnett
Sent: Thursday, February 02, 2006 9:17 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] H.323 vs. MGCP Gateway Protocol Selection

 

Just curious, would like to determine from the Group which Protocol
(H.323 vs. MGCP) represents 

An optimal gateway protocol selection in a basic centralized CallManager
Setup (1 Small Cluster) with 4 2801's (1 PRI, Per 2801) 

Communicating to the PSTN. No IP WAN Voice Connectivity will exist
within this network in the near future, However there 

Will be an IPCC Express Deployment soon.  

 

It seems to be better documentation concerning utilization of MGCP as a
primary gateway protocol and H.323 as a backup, existing 

PBX is a Nortel. Also what are the options available, on a telephony
signaling level to achieve redundancy across multiple PRI's. (Other than
HSRP) 

 

Thanks, New to the list. 

 

Neil J. Barnett 

Chief Technical Officer 

Internetwork Archetype Incorporated 

600 W. Van Buren Ave. 

Suite 908 

Chicago, Illinois 60607 

Office: 312.831.4651

Fax:312.831.1580

Mobile: 630.639.0194 

 

IMPORTANT NOTICE: This message is intended only for the use of the
individual or entity to which it is addressed. The message may contain
information that is privileged, confidential and exempt from disclosure
under applicable law. If the reader of this message is not the intended
recipient, or the employee or agent responsible for delivering the
message to the intended recipient, you are notified that any
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please
notify Internetwork Archetype immediately by email at
postmaster at i-archetype.com.com. 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060203/35ca4962/attachment-0001.html