A new era for enterprise communications: BYOC

Join our info session on February 16 : Register here

We’ve all experienced rapidly changing work styles in the past two years, and businesses have had to adapt accordingly. Many have been faced with the challenge to quickly enable and support digital efforts in the areas of remote work, employee productivity, communications and collaboration, mobility, and enterprise security. While these digital objectives are nothing new, the speed and scale at which they are trying to deliver them are unprecedented. Moreover, as enterprises embrace remote working, their networks are becoming even larger. Almost overnight, corporate networks have ended up in the homes of every single employee, making threat vectors and the places where businesses could be exposed increasingly wider.

Undoubtedly, all of this has a considerable impact on enterprise communications.  As the market is continuing to move towards cloud-based contact centers, collaboration, and communications services, organizations must continue to maintain their on-premises infrastructure for operational staff and the potential return to normalcy. Supporting all these use cases is a significant undertaking, both functionally and financially. Thus, combining some of these functionalities is not only convenient but also necessary. For instance, adding inbound and outbound calling to Microsoft Teams and Zoom enhances productivity and lowers costs. For contact centers with heavily customized architectures, changing dial plans and porting numbers are not viable options. This has given rise to “Bring Your Own Carrier (BYOC)” or “Bring Your Own SIP Trunk”— an architectural network model that makes it possible to leverage current PSTN connectivity and dial plans with a cloud-based communications provider.

As enterprises move to the cloud, however, bridging the gap between the new and the old ways of implementing communications and collaborations services is an emerging challenge with security being a chief concern. There are two areas of interest to leveraging the cloud for real-time communications, namely:

  1. 1. Unified Communications (UC), including enterprise telephony, conferencing, and messaging.
  2. 2. Contact Centers, including inbound, and outbound calling, account management, customer experience, and support.

Each of these areas has challenges in common and on their own. Firstly, organizations are realizing that they are not going to have a single provider for all their cloud-based communications, just as their on-premises network solutions are very diverse. They need to integrate those disparate cloud services along with their on-premises enterprise telephony and the PSTN. Not only do organizations want the best of what cloud can offer them, but they want the best of what other technologies can offer as well.

Security is one of the highest concerns with all cloud adoption, but real-time communications have their own set of security requirements. For instance, there is a greater expectation of privacy with regards to telephony that you don’t have with messaging and email. There are also regulatory challenges and additional requirements for resiliency, emergency calling, and compliance to name a few.

SBC is the key to enterprise adoption of BYOC

Another challenge for enterprises is reckoning with the existing systems and hardware in place as they look to embrace BYOC. Often when it comes to mid- to large enterprises, there are contractual carrier agreements and physical trunks already in place. Assuming the company and carrier have already negotiated the best agreement for services, there may be hesitation around adopting new communications technologies.

Zoom has presented BYOC options structured specifically to build cloud-based telephony into the enterprise, allowing users to communicate from headquarters to branches through Zoom Phone, a feature license in addition to a Zoom account. Rolled out to approximately 2M users in the last 18 months, Zoom Phone enables enterprises to remain with their preferred carriers, existing trunks, and the same phone numbers – it just drives all applications into the cloud.

How are all these technologies possibly connected? The Session Border Controller (SBC) is the enabler to a successful migration from existing carrier agreements to cloud-based communications. The device sits on the edge, acting as a bridge to the SIP trunking, applications, contact center, and unified communications applications. As security devices deployed at the enterprise edge or in the cloud, SBCs also facilitate direct connections to new and innovative cloud services and provide access to the remote workforce. Once an SBC and session management layer are deployed, legacy platforms can be swapped out or new services can be introduced at the pace that fits the business’ needs with minimal disruption. Outdated and underused services and systems can be decommissioned over time and newer resources like UCaaS, CCaaS, video conferencing, or SMS messaging to existing platforms, can be delivered rapidly.

Protect critical, real-time communications for collaboration, unified communications (UC), and contact centers. Oracle Enterprise Session Border Controller (E-SBC) lets you interconnect SIP trunks, on-premises enterprise telephony, UCaaS, CCaaS, and any other SIP service with security, reliability, quality, and scalability and can be deployed in your own network, as well as in major public clouds.

While enterprises are evolving towards next generation communications solutions there are certainly many paths to get there and it is no “one size fits all” situation. However, what is clear is that enterprises cannot sacrifice reliability, security, or service quality in their transformation to cloud journey. 

Want to know more about these challenges and potential solutions to address them based on your organization’s communications strategy?


A new era for enterprise communications: BYOC SBC is the path to BYOC: Three keys to a successful cloud migration Shirin Esfandiari, Product Marketing Director, Oracle Communications.