Session Border Controllers certified for Direct Routing

Microsoft partners with selected Session Border Controllers (SBC) vendors to certify that their SBCs work with Direct Routing.

Microsoft works with each vendor to:

  • Jointly work on the SIP interconnection protocols.

  • Perform intense tests using a third-party lab. Only devices that pass the tests are certified.

  • Run daily tests with all certified devices in production and pre-production environments. Validating the devices in pre-production environments guarantees that new versions of Direct Routing code in the cloud will work with certified SBCs.

  • Establish a joint support process with the SBC vendors.

    Note

    Microsoft only supports Phone System with Direct Routing when used with certified devices. In case of issues, you must contact your SBC vendor's customer support first. If needed, the SBC vendor will escalate the issue to Microsoft via internal channels. Microsoft reserves the right to reject support cases where a non-certified device is connected to Phone System through Direct Routing. If Microsoft determines that a customer's Direct Routing issue is with a vendor's SBC device, the customer will need to re-engage the SBC vendor for support.

    The certification is granted to specific SBC firmware versions. Any SBC firmware version documented below is both certified and supported. Firmware versions that are higher than what is documented are supported as long as the major.minor version is the same.

    Example:

    • Supported 6.10.258 - In this case, Microsoft supports firmware versions 6.10.(258 or higher).
    • Recommended 6.20.100 - In this case, Microsoft recommends firmware versions 6.20.(100 or higher).
    • For supportability questions about specific version, reach out to your SBC vendor.

The tables that follow list devices certified for Direct Routing. (For information about which SBC vendors support Local Media Optimization, see Configure Local Media Optimization for Direct Routing.)

Learn more about Direct Routing.

Note that we are not accepting new nominations for certification until further notice.

Certified SBC vendors

Vendor Product Non-media bypass Media bypass Software version 911 Service Provider Capable* ELIN capable
AudioCodes Mediant 500 SBC Supported 7.20A.258 (Recommended 7.40A.100 or 7.40A.250)
Mediant 800 SBC Supported 7.20A.258 (Recommended 7.40A.100 or 7.40A.250)
Mediant 2600 SBC Supported 7.20A.258 (Recommended 7.40A.100 or 7.40A.250)
Mediant 4000 SBC Supported 7.20A.258 (Recommended 7.40A.100 or 7.40A.250)
Mediant 1000B SBC Supported 7.20A.250 (Recommended 7.40A.100 or 7.40A.250)
Mediant 9000 SBC Supported 7.20A.258 (Recommended 7.40A.100 or 7.40A.250)
Virtual Edition SBC Supported 7.20A.258 (Recommended 7.40A.100 or 7.40A.250)
Mediant Cloud Edition SBC Supported 7.20A.258 (Recommended 7.40A.100 or 7.40A.250)
Ribbon Communications SBC 5100/5110 Supported on all versions of 10.1, 9.2, 8.2 and 7.2 (Recommend latest version of 10.1)
SBC 5200/5210 Supported on all versions of 10.1, 9.2, 8.2 and 7.2 (Recommend latest version of 10.1)
SBC 5400 Supported on all versions of 10.1, 9.2, 8.2 and 7.2 (Recommend latest version of 10.1))
SBC 7000 Supported on all versions of 10.1, 9.2, 8.2 and 7.2 (Recommend latest version of 10.1)
All SBC SWe variants, including hosted offers Supported on all versions of 10.1, 9.2, 8.2 and 7.2 (Recommend latest version of 10.1)
SBC 1000 8.x or 9.x
SBC 2000 8.x or 9.x
SBC SWe Lite 8.x or 9.x
EdgeMarc Series 16.3.2
Thinktel Think 365 SBC 1.4
Oracle AP 1100 Supported 8.3.0.0.1 & Recommended 8.4.x & 9.x
AP 3900 Supported 8.3.0.0.1 & Recommended 8.4.x & 9.x
AP 4600 Supported 8.3.0.0.1 & Recommended 8.4.x & 9.x
AP 6300 Supported 8.3.0.0.1 & Recommended 8.4.x & 9.x
AP 6350 Supported 8.3.0.0.1 & Recommended 8.4.x & 9.x
VME Supported 8.3.0.0.1 & Recommended 8.4.x & 9.x
AP 3950 Supported 9.x
AP 4900 Supported 9.x
TE-SYSTEMS anynode Supported 3.20 (Recommended 4.0)
Metaswitch Perimeta SBC 4.7 (4.9 for Media Bypass)
Cisco Cisco Unified Border Element (CUBE) for 1000 Series Integrated Services Routers Supported IOS XE Amsterdam 17.2.1r (Recommended 17.6.1a)
Cisco Unified Border Element (CUBE) for 4000 Series Integrated Services Routers Supported IOS XE Amsterdam 17.2.1r (Recommended 17.6.1a)
Cisco Unified Border Element (CUBE) for 1000V Series Cloud Services Router Supported IOS XE Amsterdam 17.2.1r (Recommended 17.3.3)
Cisco Unified Border Element (CUBE) for 1000 Series Aggregation Services Routers Supported IOS XE Amsterdam 17.2.1r (Recommended 17.6.1a)
Cisco Unified Border Element (CUBE) for Catalyst 8000 Edge Platforms Supported IOS XE Amsterdam 17.3.2 (Recommended 17.6.1a)
Avaya Avaya Session Border Controller for Enterprise (ASBCE) Release 8.1.1 (8.1.2 for Media Bypass)
Nokia Nokia Session Border Controller 22.0
Italtel NetMatch-S CI Supported 5.0, 5.1 (Recommended 5.3)
Ericsson vSBC 2.16
Cataleya Orchid Link 3.1
ULTATEL Teams SBC 1.6
Atos Atos Unify OpenScape Session Border Controller V10R2.2.0
Sansay Inc. vmVSXi 10.5.1.354-vm-S-x64
Enghouse Networks Dialogic BorderNet SBC 3.9.0-786
Patton Electronics Co. Patton SmartNode eSBC 3.19.x
M5 Technologies (previously known as Media5 Corporation) Mediatrix Sentinel Series DGW 48.0.2340 (Recommended DGW 48.1.2503)
Ekinops Ekinops Session Border Controller (ONeSBC) Supported 6.6.1m5ha1 (Recommended 6.8.x)
Ekinops Virtual Session Border Controller (ONEvSBC) Supported 6.6.1m5ha1 (Recommended 6.8.x)
46 Labs LLC Peeredge Orchestrator 1.0.6
Frafos ABC SBC 4.6

* 911 service providers

Support for Local Media Optimization

The following table describes which SBC vendors support Local Media Optimization.

Vendor Product Software version
Audiocodes Mediant 500 SBC 7.20A.256
Mediant 800 SBC Supported 7.20A.258 (Recommended 7.40A.100)
Mediant 2600 SBC Supported 7.20A.258 (Recommended 7.40A.100)
Mediant 4000 SBC Supported 7.20A.258 (Recommended 7.40A.100)
Mediant 1000B SBC Supported 7.20A.258 (Recommended 7.40A.100)
Mediant 9000 SBC Supported 7.20A.258 (Recommended 7.40A.100)
Mediant Virtual Edition SBC Supported 7.20A.258 (Recommended 7.40A.100)
Mediant Cloud Edition SBC Supported 7.20A.258 (Recommended 7.40A.100)
Ribbon SBC Core SBC 5110 8.2
SBC 5210 8.2
SBC 5400 8.2
SBC 7000 8.2
SBC SWe 8.2
Ribbon SBC Edge SBC SWe Lite 8.1.5
SBC 1000 8.1.5
SBC 2000 8.1.5
TE-SYSTEMS anynode 4.0.1+
Oracle AP 1100 8.4.0.0.0
AP 3900 8.4.0.0.1 & 9.x
AP 4600 8.4.0.0.1 & 9.x
AP 6300 8.4.0.0.1 & 9.x
AP 6350 8.4.0.0.1 & 9.x
VME 8.4.0.0.1 & 9.x
AP 3950 9.x
AP 4900 9.x
Avaya Avaya Session Border Controller for Enterprise (ASBCE) 10.1.2

Direct Routing and analog devices interoperability

The following table lists devices that are verified for interoperability between Direct Routing and Analog Devices.

Vendor Product Verified
AudioCodes ATA-1
AudioCodes ATA-2
Cisco ATA 191 Multiplatform Analog Telephone Adapter
Oracle AP 1100 Software Version Supported 8.3.0.1.2 & Recommended 8.4.x or 9.x
Oracle AP 3900 Software Version Supported 8.3.0.1.2 & Recommended 8.4.x or 9.x
Oracle AP 4600 Software Version Supported 8.3.0.1.2 & Recommended 8.4.x or 9.x
Oracle AP 6300 Software Version Supported 8.3.0.1.2 & Recommended 8.4.x or 9.x
Oracle AP 6350 Software Version Supported 8.3.0.1.2 & Recommended 8.4.x or 9.x
Oracle VME Software Version Supported 8.3.0.1.2 & Recommended 8.4.x or 9.x
Oracle AP 3950 Software Version Supported 9.x
Oracle AP 4900 Software Version Supported 9.x
Ribbon SBC 1000. Software version: 8.1.1 (build 527)
Ribbon SBC 2000. Software version: 8.1.1 (build 527)
Ribbon EdgeMarc 302. Software version: 16.1.1
Ribbon EdgeMarc 304. Software version: 16.1.1
Ribbon EdgeMarc 2900A. Software version: 16.1.1
Ribbon EdgeMarc 4806. Software version: 16.1.1
Ribbon EdgeMarc 4808. Software version: 16.1.1
Ribbon EdgeMarc 6000. Software version: 16.1.1
TE-SYSTEMS anynode with Grandstream GXW42xx (V1.0.7.10)

Note the certification granted to a major version. That means that firmware with any number in the SBC firmware following the major version is supported.

To provide feedback about Teams, such as ideas for new features, see the Microsoft feedback portal.

Note

Media re-targeting is not supported. During a Direct Routing call, if the SBC sends a new media IP to Teams Direct Routing, although it's negotiated in the SIP signaling, the media is never sent to the new IP address from Teams Direct Routing.