Lately about 50% of my customers age going with SIP trunks to carriers. <div>The latest one I just finished up had 2 geographically separated SIP trunks terminating on 2 separate CUBE's with failover both from the CUCM side and the carrier side.</div>
<div>This one customer had about 18 offices spread throughout the US. We took care of disaster scenarios using local analog trunks at each site for SRST purposes only.</div><div>The carrier could handle E911 using the SIP trunks and not needing to use the local GW's for this. </div>
<div>Previous to this customer we also implemented another one that had about 110 sites, same scenario as above. </div><div><br></div><div>I have one customer that has several dozen PRI's and a handful of DS3's terminating on MUX's. They are looking to combine all those circuits and going the SIP route. </div>
<div>For all of the above customers the amount of equipment needed plus the annual cost of having so many different carriers servicing so many different circuits will be reduced significantly.</div><div>They especially liked that just one carrier would be responsible for not only the billing for calls but also for their circuits.</div>
<div><br></div><div>My prediction is that SIP will eventually take over using local PRI's at the GW level where possible.</div><div><br></div><div>Joel P</div><div><br><br><div class="gmail_quote">On Wed, Feb 9, 2011 at 2:31 PM, Jason Aarons (US) <span dir="ltr"><<a href="mailto:jason.aarons@us.didata.com">jason.aarons@us.didata.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I still see a lot of PRI(s) on 3945 with SIP/vxml to CVP 8x (versus H323) and UCCE. But the amount of SIP work is growing every month….if you don’t know it I would start learning it with some small stuff first. I’ve seen some very large branch projects with centralized Verizon SIP trunks/Acme SBC which mirrored what Nick stated earlier…</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I recall in 1985 my team at Sprint griped about having to go to BGP for the Internet backbone from OSPF…….next will be IPv6 grumbling and more SIP….I bet in 10 years SIP will be 95% of new trunks sold.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </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">From:</span></b><span style="font-size:10.0pt"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Bob Zanett (US)<br>
<b>Sent:</b> Wednesday, February 09, 2011 9:55 AM<br><b>To:</b> Paul; Matthew Loraditch; David Eco; <a href="mailto:matthew@ciscovoiceguru.com" target="_blank">matthew@ciscovoiceguru.com</a>; <a href="mailto:notariannil1@scranton.edu" target="_blank">notariannil1@scranton.edu</a></span></p>
<div><div></div><div class="h5"><br><b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><b>Subject:</b> Re: [cisco-voip] Verizon SIP vs. PRI?</div></div><p></p></div></div>
<div><div></div><div class="h5"><p class="MsoNormal"> </p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Paul,</span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">It is not. SME seems to only fit into a specific silo of very large customers. I do see CUSP and CUBE being deployed, especially in the contact center area and many of our large customers – we are talking very large BHCA customers are migrating or have migrated to SIP internally already. I am working with a large service provider that we will be migrating from H323 centric to SIP centric towards the end of this year for their contact center.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Cheers,</span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Bob </span></p></div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </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">From:</span></b><span style="font-size:10.0pt"> Paul [mailto:<a href="mailto:asobihoudai@yahoo.com" target="_blank">asobihoudai@yahoo.com</a>] <br><b>Sent:</b> Tuesday, February 08, 2011 6:09 PM<br>
<b>To:</b> Bob Zanett (US); Matthew Loraditch; David Eco; <a href="mailto:matthew@ciscovoiceguru.com" target="_blank">matthew@ciscovoiceguru.com</a>; <a href="mailto:notariannil1@scranton.edu" target="_blank">notariannil1@scranton.edu</a><br>
<b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><b>Subject:</b> Re: [cisco-voip] Verizon SIP vs. PRI?</span></p></div></div><p class="MsoNormal"> </p><div><div><p class="MsoNormal">
Are you using CCM session management edition for that customer or is it just one cluster with a lot of centralized SIP trunks? I'm just asking out of curiosity since I've never heard of anyone using session management edition....yet.</p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"><span style="color:black"> </span></p><div><div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:10.0pt;color:black"><hr size="1" width="100%" align="center">
</span></div><p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:10.0pt;color:black">From:</span></b><span style="font-size:10.0pt;color:black"> Bob Zanett (US) <<a href="mailto:bob.zanett@us.didata.com" target="_blank">bob.zanett@us.didata.com</a>><br>
<b>To:</b> Matthew Loraditch <<a href="mailto:MLoraditch@heliontechnologies.com" target="_blank">MLoraditch@heliontechnologies.com</a>>; David Eco <<a href="mailto:david.eco@msn.com" target="_blank">david.eco@msn.com</a>>; "<a href="mailto:matthew@ciscovoiceguru.com" target="_blank">matthew@ciscovoiceguru.com</a>" <<a href="mailto:matthew@ciscovoiceguru.com" target="_blank">matthew@ciscovoiceguru.com</a>>; "<a href="mailto:notariannil1@scranton.edu" target="_blank">notariannil1@scranton.edu</a>" <<a href="mailto:notariannil1@scranton.edu" target="_blank">notariannil1@scranton.edu</a>><br>
<b>Cc:</b> "<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>" <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br><b>Sent:</b> Tue, February 8, 2011 1:08:13 PM<br>
<b>Subject:</b> Re: [cisco-voip] Verizon SIP vs. PRI?<br><br></span><span style="color:black"></span></p><div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I have helped to design, architect and deploy multiple customers with SIP, including SIP trunks carrying contact center calls and also business user calls. I helped to build out the initial infrastructure of a global medical device firm that almost has all of their US remote offices – literally 100s – migrated onto their centralized SIP trunks. </span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:black"></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Are there interoperability issues? Yes, as each vendor can speak a slightly different dialect. However, with the onset of some very nice Border Gateways – it is making this a non-issue. However, as Matthew states below – you need to work with someone who knows what they are doing.</span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:black"></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">For instance, ROI can be a grey area. Many times, it is simply a wash and at other times can save a tremendous amount. Like the example above, each of the remote sites had a least a PRI. However, many of the offices hardly used 12 b-channels. By centralizing, they are seeing a very nice savings and they get:</span><span style="color:black"></span></p>
<p><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D">·</span><span style="font-size:7.0pt;color:#1F497D"> </span><span style="font-size:11.0pt;color:#1F497D">Centralized dial plan management</span><span style="color:black"></span></p>
<p><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D">·</span><span style="font-size:7.0pt;color:#1F497D"> </span><span style="font-size:11.0pt;color:#1F497D">Centralized DID control and management</span><span style="color:black"></span></p>
<p><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D">·</span><span style="font-size:7.0pt;color:#1F497D"> </span><span style="font-size:11.0pt;color:#1F497D">On-the-fly call volume adjustment – it is now bandwidth not copper in the ground</span><span style="color:black"></span></p>
<p><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D">·</span><span style="font-size:7.0pt;color:#1F497D"> </span><span style="font-size:11.0pt;color:#1F497D">Economy of scale</span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:black"></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><a href="http://www.callcentertimes.com/LatestNews/tabid/59/ctl/NewsArticle/mid/407/CategoryID/1/NewsID/173/Default.aspx" target="_blank">http://www.callcentertimes.com/LatestNews/tabid/59/ctl/NewsArticle/mid/407/CategoryID/1/NewsID/173/Default.aspx</a> </span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:black"></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Cheers,</span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:black"></span></p><div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Bob </span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:black"></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Solutions Architect</span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Customer Interactive Solutions</span><span style="color:black"></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Dimension Data</span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:black"></span></p></div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:black"></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;color:black">From:</span></b><span style="font-size:10.0pt;color:black"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [<a href="mailto:mailto:cisco-voip-bounces@puck.nether.net]" target="_blank">mailto:cisco-voip-bounces@puck.nether.net]</a> <b>On Behalf Of </b>Matthew Loraditch<br>
<b>Sent:</b> Tuesday, February 08, 2011 2:29 PM<br><b>To:</b> David Eco; <a href="mailto:matthew@ciscovoiceguru.com;" target="_blank">matthew@ciscovoiceguru.com;</a> <a href="mailto:notariannil1@scranton.edu" target="_blank">notariannil1@scranton.edu</a><br>
<b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><b>Subject:</b> Re: [cisco-voip] Verizon SIP vs. PRI?</span><span style="color:black"></span></p></div></div><p class="MsoNormal">
<span style="color:black"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;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. </span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:black"></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">My point, If you are going with it make sure you or someone you have understands it.</span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:black"></span></p><p class="MsoNormal"><span style="font-size:11.0pt;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.</span><span style="color:black"></span></p>
<div><p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D"> </span><span style="color:black"></span></p><p class="MsoNormal"><b><span style="font-size:11.0pt;color:black">Matthew Loraditch, CCVP, CCNA, CCDA</span></b><span style="font-size:11.0pt;color:black"><br>
1965 Greenspring Drive</span><span style="color:black"></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:black">Timonium, MD 21093 <br><a href="mailto:support@heliontechnologies.com" target="_blank"><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/" target="_blank"><span style="color:black">www.heliontechnologies.com</span></a> <br>Support Issue? Email <a href="mailto:support@heliontechnologies.com" target="_blank"><span style="color:black">support@heliontechnologies.com</span></a> for fast assistance!</span><span style="color:black"></span></p>
</div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:black"></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;color:black">From:</span></b><span style="font-size:10.0pt;color:black"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [<a href="mailto:mailto:cisco-voip-bounces@puck.nether.net]" target="_blank">mailto:cisco-voip-bounces@puck.nether.net]</a> <b>On Behalf Of </b>David Eco<br>
<b>Sent:</b> Tuesday, February 08, 2011 2:47 PM<br><b>To:</b> <a href="mailto:matthew@ciscovoiceguru.com;" target="_blank">matthew@ciscovoiceguru.com;</a> <a href="mailto:notariannil1@scranton.edu" target="_blank">notariannil1@scranton.edu</a><br>
<b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><b>Subject:</b> Re: [cisco-voip] Verizon SIP vs. PRI?</span><span style="color:black"></span></p></div></div><p class="MsoNormal">
<span style="color:black"> </span></p><p class="MsoNormal"><span style="font-size:10.0pt;color:black">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" target="_blank">matthew@ciscovoiceguru.com</a><br>> Date: Tue, 8 Feb 2011 13:43:34 -0600<br>> To: <a href="mailto:notariannil1@scranton.edu" target="_blank">notariannil1@scranton.edu</a><br>
> CC: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">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" target="_blank">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" target="_blank">cisco-voip@puck.nether.net</a><br>> > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">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" target="_blank">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><span style="color:black"></span></p>
</div><div class="MsoNormal" align="center" style="text-align:center"><span style="color:black"><hr size="1" width="100%" align="center"></span></div><p class="MsoNormal"><span style="color:black"><a href="http://dimensiondata.stream57.com/04141pm/" target="_blank"><b><span style="text-decoration:none">Error! Filename not specified.</span></b></a></span></p>
<p><strong><span style="color:black">Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. </span></strong><span style="color:black"></span></p>
</div></div></div><p class="MsoNormal"> </p><div class="MsoNormal" align="center" style="text-align:center"><hr size="1" width="100%" align="center"></div><p class="MsoNormal">Don't get soaked. Take a<a> quick peak at the forecast </a><br>
with the<a>Yahoo! Search weather shortcut.</a></p><div class="MsoNormal" align="center" style="text-align:center"><hr size="1" width="100%" align="center"></div><p class="MsoNormal"><a href="http://dimensiondata.stream57.com/04141pm/" target="_blank"><span style="text-decoration:none"><img border="0" alt="DDIPT"></span></a></p>
<p><strong>Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. </strong></p>
</div></div></div></div><div><div></div><div class="h5"><div><p></p><hr size="1"><p></p>
<a href="http://dimensiondata.stream57.com/04141pm/" target="_blank"><span style="color:blue;text-decoration:none"><img border="0" alt="DDIPT"></span></a>
<p><strong>
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</strong></p></div></div></div><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" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>