Microsoft announced support for Session Border Controller in Exchange Online Unified Messaging’s Discontinuation. This article is meant to explain why it’s such a big deal and what this means. UPDATES: Choice 3 is a Microsoft choice. On Apr 24th Microsoft extended the date to eliminate SBC from Office 365 according to user feedback. This is only an extension. They’ve no intention of encouraging SBCs. Session Border Controllers are utilized to route SIP traffic. They act as two legged goal firewalls, utilized for SIP traffic. SBCs are deployed in the DMZ, where one port faces the other and the network faces the world wide web.
They’re required for Skype for Company and all PBXs except Server to join to Office 365 for voice email or cloud PBX. Two SBCs are required for this communication and another Microsoft possessed SBC in Office 365. This is what’s being retired. When A legacy TDM based PBX doesn’t talk SIP, VOIP gateways are required. They translate TDM to SIP. A SIP trunk and the SBC in DMZ connect the VOIP gateway. Clients have more than one! An Office 365 customer has to make an IP Gateway from the renter for SBC connectivity. This creates a public Domain Name System entry that looks like .um.outlook. Com that maps into the SBC in Office 365.
There’ll be one for each client, But all on prem SBCs join to the exact same IP Gateway address, so the actual number of SBCs is truly unknown. The number of clients utilizing SBCs to join to Office 365 can Be small based on Microsoft, but these are typically very large clients with lots of SBCs. Once clients settle on a connectivity solution they continue into invest and expand on it. That is why it is such a big deal, specifically for these customers. According into today’s announcement, the Office 365 SBCs are planned to be decommissioned in July 2018.
As the article states, you’ve Four choices: Option 1: Complete migration from third party on premises PBX into Office 365 Cloud PBX. Option 2: Complete migration from third party on premises PBX to Skype with Company Server Enterprise Voice on premises. Option 3: For clients with a mixed deployment of third party PBX and Skype for Company, connect the PBX to Skype for Company Server utilizing A connector from a Microsoft partner, and keep with Exchange Online UM through that connector. For instance, TE SYSTEMS anynode UM connector may be used for that purpose. Option 4: For clients With no Skype for Business Server installation or for which the solutions above aren’t appropriate, implement a third party voice mail system. Options 1, 2, and 4 are quite well understood, but not trivial.