<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>SCCP doesn’t do Standards Based T.38, thus MGCP does.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> Kenneth Hayes [mailto:kennethwhayes@gmail.com] <br><b>Sent:</b> Friday, July 26, 2013 5:47 PM<br><b>To:</b> Jason Aarons (AM)<br><b>Cc:</b> Eric Pedersen; cisco-voip@puck.nether.net VOIP<br><b>Subject:</b> Re: [cisco-voip] TDM to IP VG's SIP, H323, MGCP<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>With the VG224's instead of MGCP wouldn't it be easier to do it SCCP vs MGCP because of T.38 issues with SIP?<o:p></o:p></p></div><div><p class=MsoNormal><br><br>Sent from my iPad<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>On Jul 26, 2013, at 4:36 PM, "Jason Aarons (AM)" <<a href="mailto:jason.aarons@dimensiondata.com">jason.aarons@dimensiondata.com</a>> wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I would agree SIP where possible end to end creates the least amount of issues. You might have some VG224s that want Shared Lines with SIP Phones requiring MGCP on the VG224.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Kenneth Hayes<br><b>Sent:</b> Friday, July 26, 2013 3:14 PM<br><b>To:</b> Eric Pedersen<br><b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a> VOIP<br><b>Subject:</b> Re: [cisco-voip] TDM to IP VG's SIP, H323, MGCP</span><o:p></o:p></p></div></div><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'> <o:p></o:p></p><div><p class=MsoNormal>I agree. SIP between your UC apps, and gateways is what I recommend. In some cases you might need to use SCCP protocol but for the major stuff SIP is what I recommend.<br><br>Sent from my iPad<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>On Jul 26, 2013, at 9:22 AM, Eric Pedersen <<a href="mailto:PedersenE@bennettjones.com">PedersenE@bennettjones.com</a>> wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>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.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I suggest using the same protocol for all your gateways to reduce the likelihood of problems with things like DTMF relay and faxes.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Candese Perez<br><b>Sent:</b> 25 July 2013 8:07 AM<br><b>To:</b> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a> VOIP<br><b>Subject:</b> [cisco-voip] TDM to IP VG's SIP, H323, MGCP</span><o:p></o:p></p></div><p class=MsoNormal> <o:p></o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Hello All, <br>I am working on a new CUCM 9.1 deployment with several branch offices using PRI's. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Reading through the SRND and a few messages on this board, I am still not sure which protocol to use for these gateways. <o:p></o:p></p></div><div><p class=MsoNormal>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. <o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Additionally, this deployment will involve several VG 224's for fax, and analog IVR components. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Does anyone have any suggestions either way SIP, H323, or MGCP or particular features that work better/worse using a particular protocol?<o:p></o:p></p></div><div><p class=MsoNormal>Thanks!<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div></div><pre>The contents of this message may contain confidential and/or privileged<o:p></o:p></pre><pre>subject matter. If this message has been received in error, please contact<o:p></o:p></pre><pre>the sender and delete all copies. Like other forms of communication,<o:p></o:p></pre><pre>e-mail communications may be vulnerable to interception by unauthorized<o:p></o:p></pre><pre>parties. If you do not wish us to communicate with you by e-mail, please<o:p></o:p></pre><pre>notify us at your earliest convenience. In the absence of such<o:p></o:p></pre><pre>notification, your consent is assumed. Should you choose to allow us to<o:p></o:p></pre><pre>communicate by e-mail, we will not take any additional security measures<o:p></o:p></pre><pre>(such as encryption) unless specifically requested.<o:p></o:p></pre><pre> <o:p></o:p></pre></div></blockquote><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p></div></blockquote><p class=MsoNormal><br><br><span style='color:white'>itevomcid</span> <o:p></o:p></p></div></blockquote></div></body></html>