SBC integration into an existing VoIP/PBX environment
In our UC projects, we are often asked to leverage existing PBX or to ensure a smooth transition to a new UC environment. In fact, these scenarios are standard, and “big bang” migrations or greenfield installations are rare. So how do we implement SBC with minimal disruption to end-user services? At the beginning, there is a traditional PBX connection—let’s say via an ISDN line—to a PSTN -based operator:
We would install SBC between PBX and Operator:
Note that no configuration changes are required for PBX or Operator. This is quite useful if you have limited hardware available for a very old PBX or if maintenance support is too extensive or simply unavailable. Once you complete this step, you’re free to proceed: you can smoothly introduce a new UC system such as Skype for Business, two systems will coexist, and users access users from the other system:
Or change the uplink to the operator from legacy ISDN to modern SIP trunk:
If you have fully migrated to Skype for Business, you can disconnect and phase out PBX:
Please visit our website to learn more about SBC from our partners—Sonus Networks and Audiocodes.
What an article Can't Know
An article describes what applies to everyone. What varies from one organization to another is the inventory: which applications, which accounts, and which pieces of equipment are actually involved in your organization. The inventory determines the scope of the effort, and it cannot be summarized on a single page.
You'll be speaking directly with the engineers who will be doing the work, not with a middleman. We'll respond within 24 business hours.
Check what is still true
Announced dates are sometimes postponed, products are renamed, and conditions change. The blog tracks these topics over time: when a rule changes, a new post announces it.
Search for a topic in the blogIn the same issue
Three articles on the same topic. The blog has 139 articles, all of which are freely available.