[cisco-voip] TDM to IP VG's SIP, H323, MGCP

[Eric Pedersen]

SIP works very well in CM 9.1. I don't know of any reason to use H.323 between CM and PRI gateways anymore.  MGCP still provides the simplest configuration but you lose all the PRI calls if the connection between the gateway and the CM it's registered to drops for some reason.

I suggest using the same protocol for all your gateways to reduce the likelihood of problems with things like DTMF relay and faxes.

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Candese Perez
Sent: 25 July 2013 8:07 AM
To: cisco-voip at puck.nether.net VOIP
Subject: [cisco-voip] TDM to IP VG's SIP, H323, MGCP

Hello All,
I am working on a new CUCM 9.1 deployment with several branch offices using PRI's.
Reading through the SRND and a few messages on this board, I am still not sure which protocol to use for these gateways.
I know SIP is really prevalent now, and is much easier to troubleshoot, but not sure if there are any issues in terms of features.

Additionally, this deployment will involve several VG 224's for fax, and analog IVR components.
Does anyone have any suggestions either way SIP, H323, or MGCP or particular features that work better/worse using a particular protocol?
Thanks!


The contents of this message may contain confidential and/or privileged
subject matter. If this message has been received in error, please contact
the sender and delete all copies. Like other forms of communication,
e-mail communications may be vulnerable to interception by unauthorized
parties. If you do not wish us to communicate with you by e-mail, please
notify us at your earliest convenience. In the absence of such
notification, your consent is assumed. Should you choose to allow us to
communicate by e-mail, we will not take any additional security measures
(such as encryption) unless specifically requested.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130726/6e9834e5/attachment.html>