SIP trunks can be a blessing or a burden. Things that become important with SIP trunking:<br><br>-All of your versions and VOIP applications become points of interoperability. With PRI's, your interop stopped at the PRI. This means contact center applications, voicemail, call control, etc. This even extends out into the provider cloud - sometimes you'll have interop issues with only certain DIDs or companies on the other side of their network. SIP is open and flexible, which is good and bad. Sometimes the fixes to these problems are complex and require for people like the SIP provider to take action, which you can't control. You may find your contact center software, call control software, border element software, and provider have differing levels of interoperability flexibility. <br>
<br>-Sometimes it is a wash. If you're worried about survivability at the branch, you can take the money you may save by centralizing the PRIs and use it to get another circuit and router at the site. Now you've got higher branch survivability and more bandwidth as well. And if you lose two routers and/or two circuits at the site - you've probably got bigger problems. The easy generalization is that you inherit the flexibility of IP networks and get to work with the equipment you've invested into the network rather than 20+ year old telephony technology. Since you've got increased flexibility, it may be worth it to just flip the calls from the failed site somewhere else until they've recovered.<br>
<br>-Faxing/911/Modems. Now that your VOIP domain is extended to the SIP cloud, you have to take care to make sure you're standards based and compliant with the provider. It's common for people to leave a small percentage of TDM at the branch sites for 911, faxing, and survivability. Expect trouble here.<br>
<br>-Many choose to co-reside their SIP provider with their MPLS provider. This prevents having a 'dumb pipe' for your SIP traffic with the capability to distort the traffic without a disincentive. Imagine calling your cable modem provider at home and telling them "you're causing 20% jitter and a 1% loss on my high priority EF traffic". That being said - the internet is quite significantly more reliable than many expect for carrying SIP traffic. Skype, google voice, and a number of others are prime examples.<br>
<br>That being said - it's really cool. There are a couple places where it's just awesome. If you've got a remote branch and the only voice offering is a dusty T1 CAS circuit? Forget about that. If you have highly seasonal or even unpredictably bursty traffic, it can be great. If you have a lot of offices where you've overprovisioned the phone lines, SIP is a big cost saver. It's portable, and you are no longer tied down to a single smart jack where your T1 comes in on. When I travel, I register a SIP agent on my cell phone to a HTTP PBX, which registers to a SIP trunk. It's the exact same concept and architecture that SIP trunking for enterprises build on, but cool-ified.<br>
<br>If SIP is confusing, just think about how an H.323 gateway works. Your CUCM points to an IP address in your network. Now move your gateway out onto the internet. H.323 and SIP are incredibly similar, so just switch the protocol from H.323 to SIP. The last step is to place a Session Border Controller (SBC) or in Cisco's terms a Cisco Unified Border Element (CUBE). This is basically a voice firewall, and makes sure your signaling and voice stays secure and is manageable. What really happens is that is takes the call, terminates it, and then re-originiates it going outbound. From your CUCM's perspective - it wouldn't know whether a PRI or another SIP leg was on the other side. <br>
<br>In my opinion, once you get the hang of how SIP works, the troubleshooting can be simpler too. Call quality problems and resolution can be a pain on TDM circuits - who is to say where the distortion is coming from. With IP, you can easily prove where the distortion is coming from with a sniffer. Ever have to troubleshoot ISDN Q.921 messages? No thank you. It's a stronger protocol than H.323 - the odd TCP handshake isn't a problem, it isn't inhibited by a large specification, and it's a whole ton easier to read and troubleshoot.<br>
<br>Signaling interoperability problems can be solved by going through the RFCs, which can be muddy and fruitless - Vendor A allows only strictly formed messages and Vendor B refuses to implement such details. Vendor A knowingly doesn't follow SIP RFC #17, while Vendor B expects compliance. Vendor A is written by a guy in Russia who quit 3 months ago, and Vendor B doesn't like the way it was written, but Vendor B thinks it's correct. This was all solved by TDM PRI's which are essentially the lowest common denominator of voice termination.<br>
<br>Hopefully this gives you an idea. I suppose I'm just full of opinion on this one.<br><br>-nick<br><br><br><div class="gmail_quote">On Tue, Feb 8, 2011 at 7:08 PM, Paul <span dir="ltr"><<a href="mailto:asobihoudai@yahoo.com">asobihoudai@yahoo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div style="font-family: 'times new roman','new york',times,serif; font-size: 12pt;">
<div><font size="3" face="'times new roman', 'new york', times, serif">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 </font><font face="'times new roman', 'new york', times, serif">curiosity since I've never heard of anyone using session management edition....yet.</font></div>
<div><font size="3" face="'times new roman', 'new york', times, serif"><br></font></div><div><font face="'times new roman', 'new york', times, serif"></font><font size="3" face="'times new roman', 'new york', times, serif"> </font></div>
<div style="font-family: 'times new roman','new york',times,serif; font-size: 12pt; color: black;"><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font size="2" face="Tahoma"><hr size="1">
<b><span style="font-weight: bold;">From:</span></b><span> Bob Zanett (US) <<a href="mailto:bob.zanett@us.didata.com" target="_blank">bob.zanett@us.didata.com</a>></span><br><b><span style="font-weight: bold;">To:</span></b><span> 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>></span><br>
<b><span style="font-weight: bold;">Cc:</span></b><span> "<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>></span><br>
<b><span style="font-weight: bold;">Sent:</span></b> Tue, February 8, 2011 1:08:13 PM<div><div></div><div class="h5"><br><b><span style="font-weight: bold;">Subject:</span></b> Re: [cisco-voip] Verizon SIP vs. PRI?<br></div>
</div></font><div><div></div><div class="h5"><br>
<div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">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></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">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></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">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></p>
<p><span style="font-size: 11pt; font-family: Symbol; color: rgb(31, 73, 125);"><span>·<span style="font: 7pt "Times New Roman";">
</span></span></span><span style="font-size: 11pt; color: rgb(31, 73, 125);">Centralized dial plan management</span></p>
<p><span style="font-size: 11pt; font-family: Symbol; color: rgb(31, 73, 125);"><span>·<span style="font: 7pt "Times New Roman";">
</span></span></span><span style="font-size: 11pt; color: rgb(31, 73, 125);">Centralized DID control and management</span></p>
<p><span style="font-size: 11pt; font-family: Symbol; color: rgb(31, 73, 125);"><span>·<span style="font: 7pt "Times New Roman";">
</span></span></span><span style="font-size: 11pt; color: rgb(31, 73, 125);">On-the-fly call volume adjustment – it is now bandwidth
not copper in the ground</span></p>
<p><span style="font-size: 11pt; font-family: Symbol; color: rgb(31, 73, 125);"><span>·<span style="font: 7pt "Times New Roman";">
</span></span></span><span style="font-size: 11pt; color: rgb(31, 73, 125);">Economy of scale</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"><a rel="nofollow" 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></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Cheers,</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Bob </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Solutions Architect</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Customer Interactive Solutions</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Dimension Data</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
</div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<div>
<div style="border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"><span>
<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> </span><b>On
Behalf Of </b>Matthew Loraditch<br>
<b>Sent:</b> Tuesday, February 08, 2011 2:29 PM<br>
<b>To:</b><span> 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><br>
<b>Cc:</b><span> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a></span><br>
<b>Subject:</b> Re: [cisco-voip] Verizon SIP vs. PRI?</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">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></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">My point, If you are going with it make sure you or someone you
have understands it.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">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></p>
<div>
<p class="MsoNormal"><span style="font-size: 10pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><b><span style="font-size: 11pt; color: black;">Matthew Loraditch, CCVP, CCNA, CCDA</span></b><span style="font-size: 11pt; color: black;"><br>
1965 Greenspring Drive</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: black;">Timonium, MD 21093 <br>
<a rel="nofollow" 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 rel="nofollow" href="http://www.heliontechnologies.com/" target="_blank"><span style="color: black;">www.heliontechnologies.com</span></a> <br>
Support Issue? Email <a rel="nofollow" href="mailto:support@heliontechnologies.com" target="_blank"><span style="color: black;">support@heliontechnologies.com</span></a> for fast
assistance!</span><span style="font-size: 11pt; color: rgb(31, 73, 125);"></span></p>
</div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<div>
<div style="border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"><span>
<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> </span><b>On
Behalf Of </b>David Eco<br>
<b>Sent:</b> Tuesday, February 08, 2011 2:47 PM<br>
<b>To:</b><span> <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><br>
<b>Cc:</b><span> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a></span><br>
<b>Subject:</b> Re: [cisco-voip] Verizon SIP vs. PRI?</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="font-size: 10pt;">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 rel="nofollow" href="mailto:matthew@ciscovoiceguru.com" target="_blank">matthew@ciscovoiceguru.com</a><br>
> Date: Tue, 8 Feb 2011 13:43:34 -0600<br>
> To: <a rel="nofollow" href="mailto:notariannil1@scranton.edu" target="_blank">notariannil1@scranton.edu</a><br>
> CC: <a rel="nofollow" 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 rel="nofollow" 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 rel="nofollow" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
> > <a rel="nofollow" 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 rel="nofollow" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
> <a rel="nofollow" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span></p>
</div>
<p></p><hr size="1"><p></p>
<a rel="nofollow" href="http://dimensiondata.stream57.com/04141pm/" target="_blank"><span style="color: blue; text-decoration: none;"><img src="" alt="DDIPT" border="0"></span></a>
<p><b>
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.
</b></p></div></div></div></div><div style="color: black; font-family: 'times new roman','new york',times,serif; font-size: 12pt;"></div>
</div><br>
<hr size="1">
Don't get soaked. Take a<a href="http://tools.search.yahoo.com/shortcuts/?fr=oni_on_mail&#news" target="_blank"> quick peak at the forecast </a><br> with the<a href="http://tools.search.yahoo.com/shortcuts/?fr=oni_on_mail&#news" target="_blank">Yahoo! Search weather shortcut.</a></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>