Sponsored By

5 Reasons SIP Trunking is Alive and Well5 Reasons SIP Trunking is Alive and Well

The SIP trunking market continues to thrive, even as organizations move to the cloud.

Irwin Lazar

August 25, 2019

3 Min Read
Tech concept

A funny thing happened on the way to cloud communications and contact centers – SIP trunking adoption grew.

 

Nemertes’ recently published “Workplace Collaboration: 2019-20 Research Study” shows that more than 18% of the 645 participating companies are using SIP trunking, while an additional 34% plan to deploy it in the next two years. Adoption is highest in North America with 58% of PSTN trunks converted to SIP, opposed to 37% in APAC and 21% in EMEA. More startling, organizations are continuing to leverage SIP trunking even when adopting UCaaS. For example, nearly 89% of those using Microsoft Teams for calling are bringing their own SIP trunking services using Microsoft Direct Routing rather than buying PSTN access through Microsoft’s Calling Plan.

 

It seems counter-intuitive that SIP trunking adoption would increase given many UCaaS offerings include local and long-distance calling plans. If PSTN access is part of a UCaaS license, why would organizations still need to purchase SIP trunks? Yet most, UCaaS providers allow customers to bring their SIP trunks with them as they migrate to the cloud. Our research shows several reasons for the continued and growing adoption of SIP trunking:

 

  1. Cost – Organizations, especially large multi-nationals, are likely to find that PSTN access services that they purchase on their own, or through a managed services provider, offer superior economics. Most large organizations (greater than 2,500 employees) use self-managed SIP trunking services, either from a single provider or from a variety of best-in-region providers, coupled with policy-based routing to minimize toll charges. For a small company operating solely within the U.S., bundled PSTN minutes with a UCaaS service makes financial sense; for large multi-nationals, the economics often point to self-management as delivering superior TCO

  2. Control – Using a UCaaS or CCaaS provider’s PSTN access services means transferring your phone numbers to their domain. Again, this approach might attract small companies, but for large ones, with tens of thousands of phone numbers, the complexity of transferring phone numbers and avoiding disruption/downtime may make it more advantageous to maintain phone number control.

  3. Flexibility – Moving phone numbers to a UCaaS or CCaaS provider not only means loss of control of those numbers, but it also means that customers are locked into those service providers. After going through the pain of transferring numbers to a cloud provider, it may be exceedingly difficult to transfer those numbers to a different provider. Alternatively, maintaining one’s own SIP trunks and control of PSTN numbers means that not only can organizations easily move from one cloud provider to another, but that they also have the flexibility to utilize multiple cloud providers. For example, a large organization might leverage Microsoft Teams or Cisco Webex Calling for its business phone services and want to use a different provider for its contact center. Or, they may want to pilot services from a few different cloud providers before making a final purchase decision. Bring-your-own-SIP models provide for the flexibility to avoid single-vendor lock-in.

  4. Contracts – Larger organizations may have long-term contracts with SIP trunking providers that don’t allow for easy breakage. Again, it may be more costly to get out of existing three-or-more year SIP service contracts to migrate PSTN access to the cloud provider.

  5. Features – Many SIP trunking providers offer additional features not available from UCaaS providers. These may include APIs for phone number provisioning, global emergency services (911, 112) call routing, SMS/MMS in-bound and out-bound services, virtual phone numbers to establish local presence in remote markets, and more.

Bottom Line

SIP trunking services continue to grow and thrive, even as the march to cloud communications and contact center accelerates. IT leaders should carefully consider whether it makes sense to maintain their SIP trunking services, and with them, control over their phone numbers and the flexibility to avoid service lock-in and obtain access to advanced features potentially not available from their UCaaS partners.

About the Author

Irwin Lazar

As president and principal analyst at Metrigy, Irwin Lazar develops and manages research projects, conducts and analyzes primary research, and advises enterprise and vendor clients on technology strategy, adoption and business metrics, Mr. Lazar is responsible for benchmarking the adoption and use of emerging technologies in the digital workplace, covering enterprise communications and collaboration as an industry analyst for over 20 years.

 

A Certified Information Systems Security Professional (CISSP) and sought-after speaker and author, Mr. Lazar is a blogger for NoJitter.com and contributor for SearchUnifiedCommunications.com writing on topics including team collaboration, UC, cloud, adoption, SD-WAN, CPaaS, WebRTC, and more. He is a frequent resource for the business and trade press and is a regular speaker at events such as Enterprise Connect, InfoComm, and FutureIT. In 2017 he was recognized as an Emerging Technologies Fellow by the IMCCA and InfoComm.

 

Mr. Lazar’s earlier background was in IP network and security architecture, design, and operations where he advised global organizations and held direct operational responsibility for worldwide voice and data networks.

 

Mr. Lazar holds an MBA from George Mason University and a Bachelor of Business Administration in Management Information Systems from Radford University where he received a commission as a Second Lieutenant in the U.S. Army Reserve, Ordnance Corps. He is a Certified Information Systems Security Professional (CISSP). Outside of Metrigy, Mr. Lazar has been active in Scouting for over ten years as a Scouting leader with Troop 1882 in Haymarket VA.