<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: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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
/* 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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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">The thing I would say is it all depends on your level of comfort with the Carrier and with SIP. I generally don’t have a problem with the quality of the service
when it works, the problem has been troubleshooting and making it work in the first place. I understand how to debug and troubleshoot a T-1 or PRI and can set one up H.323 or MGCP no problem. SIP just doesn’t process for me, Everybody says it’s simple, plain
text and all that but I don’t get it. <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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">My point, If you are going with it make sure you or someone you have understands it.<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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">If you have a smaller install one thing you can do is have the provider put in an IAD and hand off as PRI. Make them responsible and make your side something
you understand. Obviously in a large campus environment that may not be feasible and defeats some of the consolidation benefits but in a smaller setup it can make life much easier.<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Matthew Loraditch, CCVP, CCNA, CCDA</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><br>
1965 Greenspring Drive<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Timonium, MD 21093
<br>
<a href="mailto:support@heliontechnologies.com"><span style="color:black">support@heliontechnologies.com</span></a><br>
(p) (410) 252-8830<br>
(F) (443) 541-1593<br>
<br>
Visit us at <a href="http://www.heliontechnologies.com/"><span style="color:black">www.heliontechnologies.com</span></a>
<br>
Support Issue? Email <a href="mailto:support@heliontechnologies.com"><span style="color:black">support@heliontechnologies.com</span></a> for fast assistance!</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</div>
<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 #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-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net]
<b>On Behalf Of </b>David Eco<br>
<b>Sent:</b> Tuesday, February 08, 2011 2:47 PM<br>
<b>To:</b> matthew@ciscovoiceguru.com; notariannil1@scranton.edu<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] Verizon SIP vs. PRI?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">with SIP, you may get more capacity of the channel. But in our case, we have to setup IPSEC VPN with Verizon to utilize their SIP Trunk. Network has to be reliable.<br>
<br>
David<br>
<br>
<br>
<br>
<br>
> From: <a href="mailto:matthew@ciscovoiceguru.com">matthew@ciscovoiceguru.com</a><br>
> Date: Tue, 8 Feb 2011 13:43:34 -0600<br>
> To: <a href="mailto:notariannil1@scranton.edu">notariannil1@scranton.edu</a><br>
> CC: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Subject: Re: [cisco-voip] Verizon SIP vs. PRI?<br>
> <br>
> One of my biggest questions right now regarding SIP trunks has been data circuit issues and usability in SRST mode. If your branch office loses it's network connection, will your SIP trunk go down too? If so, then you're up the creek without a paddle.<br>
> <br>
> Sent from my iPhone<br>
> <br>
> On Feb 8, 2011, at 1:13 PM, Lisa Notarianni <<a href="mailto:notariannil1@scranton.edu">notariannil1@scranton.edu</a>> wrote:<br>
> <br>
> > We currently utilize PRI trunks as fail over and backup. They connect to our 6509's.<br>
> > <br>
> > Can anyone share their thoughts on SIP vs. PRI services. <br>
> > <br>
> > Thanks,<br>
> > <br>
> > Lisa<br>
> > -- <br>
> > <LNsignature.jpg><br>
> > _______________________________________________<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><br>
> <br>
> _______________________________________________<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></span></p>
</div>
</body>
</html>