Session Border Controllers Tested with Exchange Online UM
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 how you set them up can be different depending on other equipment on your network. 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 |
Net-Net 3820 or 4500 |
Dedicated SBC |
||
Mediant 1000B MSBG |
Dedicated SBC |
||
Mediant 1000B MSBG |
MSBG Gateway and Session Border Controller (SBC) with Legacy PBX |
SBC and IP gateway |
|
SIParator |
Dedicated SBC |
||
VX 1200 & VX1800 |
SBC option for a VoIP gateway product |
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, it can cause configuration problems.
Warning
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. For example, if you specify the FQDN address sbcexternal.contoso.com 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. However, this name that you use is case-sensitive, so 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 IP gateway’s FQDN, the call will be rejected with a 403 error.