Exchange Online Unified Messaging

August 30th, 2017

On July 18th, Microsoft announced a discontinuation of support for session border controllers (SBCs) to connect 3rd party PBXs to Exchange Online Unified Messaging.

In their announcement, Microsoft provided four options for those affected. Still, we had a lot of our customers and partners asking for more specifics. Their questions ranged from topology to configuration to licensing. There are a lot of different topologies consisting of many disparate vendors that help route a call from the PSTN to a local PBX through an SBC to Exchange Online Unified Messaging. Every time you start to think one through, more questions come up.

“How does this change affect the message waiting indicator?”

“Can I fork incoming calls to my local PBX and Skype for Business and forward to Exchange Online Unified Messaging if there is no answer?”

“Can one use E3 or E1 with Skype for Business Cloud Connector Edition connected voicemail to Exchange Online out of a 3rd party PBX? Or is E5 always needed?”

Brad Chapin

Brad Chapin, Director of Strategic Alliances at Sonus has regular conversations with Microsoft and understands how all of this works today as well as how it will work after the announced change takes effect. Brad took the time to go over all of the options laid out by Microsoft, with diagrams showing how calls are routed today and how they will be routed after the announced change.

Click here to view Brad’s webinar presenting these options.

Ask Us Anything!

Ribbon's team of professionals are ready to answer your questions, guide you to the right solution or help you with your network design.