What you’ll learn at VoiceCon OrlandoPart 2:

SIP Trunking from All Angles

…from the Services & Equipment perspective:LISA PIERCE, STRATEGIC NETWORKS GROUPwith panelists from AT&T, Verizon, Sprint; Acme Packet, AudioCodes, NET, Sonus

…from the Technology perspectiveSORELL SLAYMAKER, UNIFIED IT SYSTEMSwith Jim Allen, Medtronic

…from the End User perspectivespeakers from UPENN, RIVERSIDE BANK, ALPINE ACCESS

VoiceCon Orlando 2010

SIP Trunking benefits

• Conversion to IP has:

• Reduced PSTN connectivity costs by approximately 40%• 6x increase in trunk capacity improving scalability• Eliminated business disruption due to legacy system

failures for converted lines• Eliminated costs associated with maintenance and sparing

of legacy equipment and services• Eliminated support process inefficiencies by converging

on IP.• Allowed for greater architectural flexibility thereby

enabling new feature and service development

VoiceCon Orlando 2010

Major technical challenges with SIP Trunking

The greatest challenge was integrating SIP trunks with our legacy and VoIP based PennNet Phone service

•Technical •Availability of products•Signaling (addressing)•Time required for Interop testing with ITSPs

•Business process •Billing (Clear & consistent customer bills)•Contract terms (features, capacity, cost)

Summary• 3 Internet T1 connections into two Cisco routers, total 135

concurrent calls; both inbound and outbound, using SIP/H.323 signaling via port 5060. We chose the G.729 codec with a 30 ms sample rate so each internet T1 can support 45 concurrent calls as opposed to a T1 that can support 24 concurrent calls or a PRI that can support 23 concurrent calls. The default sampling rate from our vendor is 20 ms, giving you 33 concurrent calls over the internet T1.

• We can control the amount of calls going to ATT Long Distance at any time using the outbound route preference in the NEC PBX. Currently, we are keeping the ATT LD T1 as a fail safe, but will be migrating away very shortly, using the Local PRI’s as the analog fail safe.

• We removed 1 PRI and 4 T1 circuits. Each circuit was roughly $550.00 per month. So far we are saving roughly $180,000 per year for inbound 800 calling. Now we are adding outbound calling through Qwest and expecting another $2000.00/month savings, factoring in the cancellation of 1 T1 and Qwest pricing.

Summary Cont.

• The initial investment was just under $20,000, and my time for research and programming, the ROI was within three months.

• Expect challenges!

• Carrier availability: sales team’s reality, vs. actual reality.

• We are still using TDM lines for faxing, but will be reviewing our options in the near future.

• We are now beginning a new phase to add more SIP capabilities at both the OPS Center and branches for even more savings, currently estimated at $7000 per month. More info on this topic in the future!

Copyright © Alpine Access, Inc. Proprietary and confidential.

What drives enterprise deployment of SIP trunks?

> For us, the key driver was inbound traffic costs> We needed a low-cost NPA-NXX presence

throughout the country (along with a low-cost toll-free presence where local numbers were not available)

> Scaleability of SIP (both for growth and seasonality) was a bonus

> Reducing our data center footprint is a plus> Last but not least, we are beginning to get

requests from our clients for VoIP handoff to us (instead of TDM)

Copyright © Alpine Access, Inc. Proprietary and confidential.

Carrier availability, pricing, SLAs and contracting/procurement

> Upstart carriers seem to be ahead of the big name brands in their SIP offerings and understanding

> Pricing:– Denver’s local calling area is huge but that is not

always honored by SIP providers– Different vendors have different pricing structures:

• Generally pay per minute for inbound / outbound • Often no free outbound local calling or free inbound DID• Some carriers allow bursting but other don’t

– Intrastate toll still expensive on SIP> Since TDM still has some pricing benefits for us,

we have kept it for that reason (and for backup)

Copyright © Alpine Access, Inc. Proprietary and confidential.

Copyright © Alpine Access, Inc. Proprietary and confidential.

Technical challenges

> Multiple carrier-side outages on a single circuit (although other SIP circuits have never had an outage)

> Ensuring successful end user transmission of DTMF to all terminating equipment (RFC 2833)

> Timeouts affecting long calls or slowly-answered calls (e.g., caused by Redirect on No Answer)

> Heat in data center affecting SBCs

Copyright © Alpine Access, Inc. Proprietary and confidential.

Conclusions

> Migrating trunking from TDM to SIP is a lot less painful than migrating hundreds or thousands of telephones from TDM to SIP!

> Now’s a good time for any enterprise to investigate SIP, determine ROI and implement it while avoiding a lot of the early adopter pitfalls

> Since small SIP pipes will not have the same economies of scale as large ones, the biggest benefits of SIP are likely to be seen in enterprises that already have or plan to flatten, consolidate, and extend their voice infrastructure

“SIP Trunking: Who’s Offering What?”Presenter: Lisa Pierce, Strategic Networks Group

Monday, March 22, 9:00 – 10:45 AM

“Implementing SIP Trunking”Presenter, Sorell Slaymaker, Unified IT Systems (with Jim Allen, Medtronic)

Monday, March 22, 2:00 – 3:00 PM

“SIP Trunking Case Studies”Panel: Steve Blair, UPenn; Todd Vinciguerra, Riverside Bank; Larry Riba, Alpine

Access Wednesday, March 24, 2:00 – 3:00 PM

Check out the entire program at www.voicecon.com/orlando/program

REGISTER NOW FOR TO ATTEND VOICECON ORLANDO 2010!

CLICK HERE TO REGISTER