Session Border Controllers Tested with Exchange Online UM

 

Topic Last Modified: 2014-01-20

The following session border controllers (SBCs) have been successfully tested for interoperability with Exchange Online. Note that the capabilities and compatibilities of SBCs can vary, and the required configurations can also vary depending on other equipment in your environment. Consult with the SBC manufacturer to see whether there are specific configuration notes for Unified Messaging in Office 365.

For information about how to set up Unified Messaging in Office 365 to work with an SBC, see Configuration Checklist: Configure Office 365 Unified Messaging to Work with a Session Border Controller.

 

Vendor

Model

Configuration notes

Comments

Acme Packet

Net-Net 3820 or 4500

Acme Packet SBC in Microsoft Office 365 Unified Messaging

Dedicated SBC

AudioCodes

Mediant 1000B MSBG

MSBG Session Border Controller (SBC) with IP PBX

Dedicated SBC

AudioCodes

Mediant 1000B MSBG

MSBG Gateway and Session Border Controller (SBC) with Legacy PBX

SBC and IP gateway

Ingate

SIParator

Ingate SIParator Configuration Notes

Dedicated SBC

NET

VX1200 & VX1800

NET VX SESSION BORDER CONTROLLER CONFIGURATION NOTES FOR OFFICE 365 UNIFIED MESSAGING (UM)

SBC option for a VoIP gateway product

Sonus

SBC 1000/2000 2.2.1 or later

Configuring Sonus SBC 1000/2000 with Microsoft Office 365 Application Notes

Dedicated SBC

Note   Because SBCs are designed to sit on the network edge, they function as a firewall already. If you set up an SBC behind your organization’s firewall, this can cause configuration problems.

warningWarning:
The subject common name in the certificate must match the fully qualified domain name (FQDN) value in the Address field on the UM IP gateway that you create for Exchange Online. In Exchange Online UM, a UM IP gateway represents an SBC. If you specify an FQDN address on your UM IP gateway, make sure that the subject name and subject alternative name in the certificate contain the same value (for example, sbcexternal.contoso.com). Note that the name that you use is case-sensitive. Therefore, make sure the case is the same on both the certificate and the IP gateway object. If you’re using an Acme Packet SBC, and the common name doesn’t match the FQDN of the IP gateway, the call will be rejected, and you’ll receive a 403 error.
 
Related help topics
Loading...
No resources were found.