Session Border Controllers certified for Direct Routing - Microsoft Teams

Publisher

Microsoft

URL

https://learn.microsoft.com/en-us/microsoftteams/direct-routing-border-controllers

Published

2026-05-27

Updated

unknown

Accessed

2026-09-14

HTTP status

200

License

Microsoft Learn terms of use (content copyright Microsoft); open licence for this page not verified; no-redistribution; short excerpts and locators only

Source notes citing this source

• Microsoft's certified-SBC table names 7.40A firmware for AudioCodes, not 7.60A, and its major.minor rule does not on its own extend certification to 7.6; whether 7.6 is certified is unresolved on this evidence. inferred in context
• For most AudioCodes models, Microsoft's certified-SBC table lists firmware 'Supported 7.40A.600 (Recommended 7.40A.500)'; Mediant 500 Li is listed as Supported 7.2x.xxx (Recommended 7.40A.400) and Mediant 7000 as Recommended 7.40A.600. in context
• Microsoft supports certified SBC firmware versions higher than the documented one as long as the major.minor version is the same. in context
• Microsoft's certified Direct Routing SBC table lists AudioCodes Mediant 500, 500 Li, 800, 1000B, 2600, 3100, 4000, 7000 and 9000 SBCs plus Virtual Edition and Mediant Cloud Edition, all certified for both non-media-bypass and media bypass. in context
• Microsoft lists AudioCodes Mediant 500, 800, 1000B, 2600, 4000, 9000, Virtual Edition and Cloud Edition SBCs as supporting Local Media Optimization; for most models the table shows Supported 7.20A.258 (Recommended 7.40A.100), and for Mediant 500 it shows 7.20A.256. in context
• Microsoft states it is not accepting new nominations for Direct Routing SBC certification until further notice. in context
• For Direct Routing issues, the customer must contact the certified SBC vendor's support first, and escalations to Microsoft need the vendor's investigation report. in context
• Microsoft lists AudioCodes Mediant 500, 800, 1000B, 2600, 3100, 4000, 7000 and 9000 SBCs, Virtual Edition SBC and Mediant Cloud Edition SBC as certified for both non-media-bypass and media bypass, with supported firmware 7.40A.600. in context
• Because Microsoft's list shows AudioCodes firmware 7.40A and supports higher builds only within the same major.minor, a Mediant running a 7.6 release may fall outside the documented certified line and should be confirmed with AudioCodes before production. inferred in context
• Direct Routing certification is granted to specific SBC firmware versions, and firmware higher than the documented version is supported as long as the major.minor version is the same. in context
• Microsoft does not support media re-targeting during an active Direct Routing call: if the SBC signals a new media IP mid-call, Direct Routing never sends media to it. in context
• Avaya Session Border Controller for Enterprise is certified for Direct Routing at Release 8.1.1 or higher, 8.1.2 or higher for media bypass, and 10.2.0.2 for ELIN. in context
• Microsoft lists Avaya SBCE 10.1.2 or higher as supporting Local Media Optimization for Direct Routing. in context
• Direct Routing certification applies to specific SBC firmware versions, and higher firmware is supported as long as the major.minor version is the same. in context
• Microsoft states it is not accepting new nominations for Direct Routing SBC certification until further notice. in context
• Direct Routing does not support media re-targeting: if the SBC signals a new media IP mid-call, Teams never sends media to it. in context
• Microsoft lists Avaya Session Border Controller for Enterprise (ASBCE) as certified for Direct Routing at release 8.1.1 or higher, with 8.1.2 or higher for media bypass and 10.2.0.2 for ELIN. in context
• Microsoft lists Avaya ASBCE release 10.1.2 or higher as supporting Local Media Optimization for Direct Routing. in context
• Direct Routing does not support media re-targeting: if the SBC sends a new media IP mid-call, Teams never sends media to the new address. in context
• Direct Routing SBC certification is granted to specific firmware versions, and higher firmware versions are supported as long as the major.minor version is the same. in context
• Microsoft states it is not accepting new nominations for Direct Routing SBC certification until further notice. in context
• AudioCodes Mediant Cloud Edition SBC is listed as certified for Direct Routing with and without media bypass, supported from 7.40A.600 with 7.40A.500 recommended. in context
• AudioCodes Virtual Edition SBC is listed as certified for Direct Routing with and without media bypass, supported from 7.40A.600 with 7.40A.500 recommended. in context
• Microsoft lists Cisco CUBE for Catalyst 8000 Edge Platforms as certified for Direct Routing, supported from IOS XE 17.3.2 with 17.6.1a recommended. in context
• Microsoft lists Cisco CUBE for 1000V Series Cloud Services Router as certified for Direct Routing, supported from IOS XE 17.2.1r with 17.3.3 recommended. in context
• Direct Routing certification covers documented SBC firmware versions, and higher firmware is supported as long as the major.minor version is the same. in context
• Microsoft states it is not accepting new nominations for Direct Routing SBC certification until further notice. in context
• Oracle VME is listed as certified for Direct Routing with and without media bypass on software 9.x and 10.x. in context
• Microsoft's certified list covers all Ribbon SBC SWe variants including hosted offers, with and without media bypass, on 11.1 and later, 10.1, 9.2 and 7.2. in context
• Microsoft does not support media re-targeting during an active Direct Routing call: a new media IP sent by the SBC mid-call is negotiated in SIP but Teams never sends media to it. in context
• Microsoft's certified list does not explicitly name Catalyst 8000V, so whether CUBE on a cloud-hosted Catalyst 8000V falls under the Catalyst 8000 Edge Platforms certification needs confirmation from Cisco. inferred in context
• A cloud SBC HA design whose failover changes the media IP address mid-call is unlikely to preserve Teams Direct Routing media on in-progress calls, because Teams does not follow mid-call media re-targeting. inferred in context
• Microsoft certifies specific SBC firmware versions and supports higher firmware versions as long as the major.minor version is the same as a documented version. in context
• Microsoft lists Cisco Unified Border Element as certified for Direct Routing, both non-media bypass and media bypass, on 1000 Series ISR, 4000 Series ISR, CSR 1000V, ASR 1000 and Catalyst 8000 Edge platforms. in context
• In Microsoft's certified SBC list the CUBE rows are marked 911 Service Provider capable but not ELIN capable, and Cisco does not appear in the Local Media Optimization support table. in context
• Microsoft lists CUBE as supported from IOS XE Amsterdam 17.2.1r (17.3.2 for Catalyst 8000 Edge) with 17.6.1a recommended (17.3.3 recommended for CSR 1000V). in context
• Direct Routing does not support media re-targeting: if the SBC signals a new media IP mid-call, Direct Routing never sends media to the new address. in context
• To escalate an SBC-related Direct Routing issue to Microsoft, the customer must first contact the SBC vendor and present the vendor's investigation report with its ticket reference. in context
• Direct Routing certification is granted to specific SBC firmware versions; higher firmware is supported as long as the major.minor version is the same. in context
• CUBE for Catalyst 8000 Edge Platforms is listed as certified for Direct Routing, supported from IOS XE 17.3.2 with 17.6.1a recommended. in context
• Cisco Unified Border Element for 4000 Series ISRs is listed as certified for Direct Routing (non-media-bypass and media bypass), supported from IOS XE Amsterdam 17.2.1r with 17.6.1a recommended. in context
• In Microsoft's certified SBC table the Cisco CUBE rows are marked 911 Service Provider Capable but not ELIN capable. in context
• Microsoft states it is not accepting new nominations for Direct Routing SBC certification until further notice. in context
• Microsoft certifies and supports Bandwidth Dynamic Location Routing, Intrado Emergency Routing Service and Inteliquent as 911 service providers for Direct Routing, and may reject support cases that use a non-certified provider. in context
• Microsoft lists Cisco Unified Border Element as certified for Direct Routing, with and without media bypass, on ISR 1000, ISR 4000, CSR 1000V, ASR 1000 and Catalyst 8000 Edge platforms, supported from IOS XE 17.2.1r (17.3.2 on Catalyst 8000) with 17.6.1a recommended (17.3.3 on CSR 1000V). in context
• Direct Routing certification applies to specific SBC firmware versions; firmware higher than the documented version is supported only while the major.minor version stays the same. in context
• Cisco ATA 191 Multiplatform Analog Telephone Adapter is verified for interoperability between Direct Routing and analog devices, alongside AudioCodes, Oracle and Ribbon adapters and gateways. in context
• Microsoft's table marks Cisco CUBE as certified for both non-media bypass and media bypass, and leaves the 'ELIN capable' column blank for Cisco CUBE while marking the 911 service provider capable column as satisfied. in context
• Cisco Unified Border Element (CUBE) is certified for Direct Routing on ISR 1000 Series, ISR 4000 Series, CSR 1000V, ASR 1000 Series and Catalyst 8000 Edge Platforms. in context
• The Cisco CUBE rows are certified at IOS XE Amsterdam 17.2.1r (recommended 17.6.1a; 17.3.3 for CSR 1000V; Catalyst 8000 Edge supported from 17.3.2), and the table notes that firmware higher than documented is supported as long as the major.minor version is unchanged. in context
• Cisco does not appear in the Microsoft page's 'Support for Local Media Optimization' vendor table, which lists AudioCodes, Ribbon, TE-SYSTEMS, Oracle, Avaya, Italtel and Enghouse Networks. inferred in context
• Microsoft certifies and supports three emergency services providers for Direct Routing - Bandwidth Dynamic Location Routing, Intrado Emergency Routing Service and Inteliquent - and may reject support cases if a non-certified provider is used. in context
• The certified SBC page repeats that media re-targeting isn't supported: if the SBC sends a new media IP during a Direct Routing call it is negotiated in signalling but Teams never sends media to the new address. in context
• The certified SBC page states that Microsoft is not accepting new nominations for SBC certification until further notice. in context
• Microsoft lists Intrado Emergency Routing Service (ERS) as a certified and supported 911 service provider for Teams Direct Routing, together with Bandwidth Dynamic Location Routing and Inteliquent. in context
• Microsoft says it may reject support cases if a non-certified emergency services provider is used with Direct Routing. in context
• Microsoft's certified SBC table marks each SBC as '911 Service Provider Capable' and/or 'ELIN capable' separately; for example, Cisco CUBE is marked 911 Service Provider Capable but not ELIN capable, and several certified SBCs are marked as neither. in context
• Direct Routing certification is granted to specific SBC firmware versions; higher firmware is supported as long as the major.minor version is the same. in context
• The AudioCodes Mediant 1000B SBC is on Microsoft's certified list for Direct Routing, with media bypass support and software 7.40A.600 listed as supported. in context
• Microsoft states it is not accepting new nominations for Direct Routing SBC certification until further notice. in context
• Microsoft lists Bandwidth Dynamic Location Routing, Intrado Emergency Routing Service and Inteliquent as the emergency services providers it certifies and supports for Direct Routing, and may reject support cases that use a non-certified provider. in context
• Cisco Unified Border Element is certified for Direct Routing, including media bypass, on ISR 1000, ISR 4000, CSR 1000V, ASR 1000 (supported from IOS XE Amsterdam 17.2.1r) and Catalyst 8000 Edge (supported from IOS XE 17.3.2). in context
• Cisco does not appear in the certified-SBC page's 'Support for Local Media Optimization' vendor table. in context
• The certified-SBC page states that SBC firmware versions higher than the documented one are supported as long as the major.minor version is the same. disputed in context
• The certified-SBC page also states that certification is granted to a major version, so firmware with any number following the major version is supported. disputed in context
• Media re-targeting isn't supported: if the SBC signals a new media IP mid-call, Direct Routing never sends media to the new address even though it is negotiated in SIP. in context
• As of the 2026-09-28 revision of the certified-SBC page, Microsoft states it is not accepting new nominations for Direct Routing SBC certification until further notice. in context
• For Direct Routing issues the customer must contact the certified SBC vendor first; the vendor escalates to Microsoft if needed, and a Microsoft support case must include the SBC vendor's investigation report. in context
• Microsoft's Direct Routing certified SBC list includes AudioCodes Mediant SBC models, including Virtual Edition and Cloud Edition, supported at 7.40A.600 with 7.40A.500 recommended for most models. in context
• Microsoft's Direct Routing certified SBC list includes Cisco Unified Border Element on Catalyst 8000 Edge Platforms, supported from IOS XE 17.3.2 with 17.6.1a recommended. in context
• Cisco CUBE and AudioCodes Mediant appear on the Teams certified list, the Zoom certified list and the Webex LGW material, but at different versions, so a shared SBC's firmware must fall within every platform's listed range at once. inferred in context
• The Microsoft certified SBC page says firmware versions higher than those documented are supported as long as the major.minor version is the same. disputed in context
• The Microsoft certified SBC page's closing note says certification is granted to a major version, so firmware with any number after the major version is supported. disputed in context
• As of the page update on 2026-09-28, Microsoft states it is not accepting new nominations for Direct Routing SBC certification until further notice. in context
• Microsoft grants Direct Routing certification to specific SBC firmware versions and supports firmware higher than the documented version only while the major.minor version stays the same. in context
• Microsoft's certified-SBC list for Direct Routing includes the Oracle AP 1100, AP 3900, AP 4600, AP 6300, AP 6350, VME, AP 3950, AP 4900 and AP 6400, each marked as certified for both non-media-bypass and media bypass and as 911 service provider and ELIN capable. in context
• Microsoft lists Oracle SBC software 9.x and 10.x as supported for Direct Routing on most Oracle platforms, with the AP 6300 listed for 9.x only and the AP 6400 for 10.x only, and recommends the latest version. in context
• Microsoft's certified 911 service providers for Direct Routing are Bandwidth Dynamic Location Routing, Intrado Emergency Routing Service and Inteliquent; RedSky is not on that list. in context
• Using RedSky as the emergency routing provider behind Teams Direct Routing would put it outside Microsoft's certified ERS list, so Microsoft may reject related support cases. inferred in context
• An AudioCodes Mediant SBC at 7.40A.600 or later appears to meet both the Microsoft Direct Routing supported version and the Webex Calling certificate-based minimum of 7.40A.250.440. inferred in context
• Microsoft lists TE-SYSTEMS anynode as Direct Routing certified with media bypass, at Supported 3.20 (Recommended 4.0). in context
• In Microsoft's Direct Routing certified list most AudioCodes Mediant SBC rows (500, 800, 2600, 4000, 1000B, 9000, 3100, Virtual Edition and Cloud Edition) show 'Supported 7.40A.600 (Recommended 7.40A.500)'. in context
• Microsoft lists Avaya ASBCE as Direct Routing certified at release 8.1.1 or higher, 8.1.2 or higher for media bypass, and 10.2.0.2 for ELIN. in context
• Direct Routing certification is granted to specific SBC firmware versions, and higher firmware versions are supported as long as the major.minor version is the same as the documented one. in context
• Microsoft certifies Direct Routing SBCs by having them tested in a third-party lab, and only devices that pass are certified. in context
• Microsoft certifies and supports three emergency services providers for Direct Routing: Bandwidth Dynamic Location Routing, Intrado Emergency Routing Service and Inteliquent. It may reject support cases if a non-certified provider is used. in context
• Microsoft lists Cisco CUBE on ISR 1000, ISR 4000, ASR 1000 and CSR 1000V as Direct Routing certified from IOS XE Amsterdam 17.2.1r. in context
• In Microsoft's Direct Routing certified list none of the Cisco CUBE rows is marked ELIN capable, although all of them are marked 911 Service Provider Capable. in context
• Microsoft lists the Italtel NetMatch-S CI as Direct Routing certified with media bypass, at Supported 5.8 (Recommended latest version). in context
• Microsoft lists TE-SYSTEMS anynode as supporting Direct Routing Local Media Optimization at version 4.0.1 or later. in context
• Microsoft lists the Italtel NetMatch-S CI as supporting Direct Routing Local Media Optimization at version 5.7 or higher. in context
• Direct Routing does not support media re-targeting: if the SBC signals a new media IP mid-call, Teams Direct Routing never sends media to the new address. in context
• Microsoft states it is not accepting new nominations for Direct Routing SBC certification until further notice. in context
• Several products on Microsoft's certified list have no media bypass mark, including Thinktel Think 365 SBC, Oracle Cloud Native SBC, Ericsson vSBC, Cataleya Orchid Link, Patton SmartNode eSBC, Mediatrix Sentinel, Frafos ABC SBC, Vodia PBX and Brekeke PBX. in context
• Microsoft reserves the right to reject support cases in which a non-certified device is connected to Phone System through Direct Routing. in context
• Microsoft lists Oracle AP 1100, AP 3900, AP 4600, AP 6350, AP 3950, AP 4900 and VME as Direct Routing certified on 9.x and 10.x, AP 6300 on 9.x only, and AP 6400 on 10.x only. in context
• Microsoft lists the Oracle Cloud Native SBC for Direct Routing as non-media-bypass only, at 1.26.0.1.0 or higher, with 911 provider and ELIN capability shown as TBC. in context
• Microsoft lists Ribbon SBC 5400, SBC 7000 and all SBC SWe variants (including hosted offers) as Direct Routing certified on available versions of 11.1 and later, 10.1, 9.2 and 7.2, with media bypass. in context
• Microsoft lists Ribbon SBC 1000, SBC 2000 and SBC SWe Edge (formerly SWe Lite) as Direct Routing certified on available versions of 12.x and later, 11.x or 9.x, and marks them ELIN capable. in context
• Microsoft supports Phone System with Direct Routing only when it is used with certified SBC devices. in context
• For Direct Routing issues the customer must contact the SBC vendor's support first, and the SBC vendor escalates to Microsoft through internal channels if needed. in context
• To escalate an SBC-related Direct Routing issue to Microsoft support, the customer must present an SBC vendor investigation report that contains the vendor's ticket reference number. in context
• Microsoft only supports Phone System with Direct Routing when it is used with certified SBC devices, and reserves the right to reject support cases involving non-certified devices. in context
• Microsoft states it is not accepting new nominations for Direct Routing SBC certification until further notice. in context
• Inference: a contact center topology that relies on a non-certified Direct Routing SBC (Connect) or a non-certified third-party voice agent (Unify) can leave the affected user cohort outside Microsoft's support boundary, because Microsoft says it may reject support cases in both situations. inferred in context
• Microsoft lists Bandwidth Dynamic Location Routing, Intrado Emergency Routing Service and Inteliquent as the certified 911 service providers for Direct Routing, and may reject support cases that use a non-certified provider. in context
• Direct Routing does not support media re-targeting. If the SBC signals a new media IP during a call, Teams never sends media to the new address. in context
• As of the page's last update, Microsoft states it is not accepting new nominations for Direct Routing SBC certification until further notice. in context
• Because certification nominations are closed, an SBC product not already in the certified table is unlikely to gain Direct Routing certification in the near term, so SBC selection is effectively limited to the listed vendors and products. inferred in context
• Microsoft reserves the right to reject support cases where a non-certified device is connected to Teams Phone through Direct Routing. in context
• AudioCodes Mediant 500, 800, 1000B, 2600, 3100, 4000, 9000, Virtual Edition and Cloud Edition SBCs are listed as certified for both non-bypass and media bypass with supported firmware 7.40A.600 and recommended 7.40A.500. in context
• The certified SBC table marks non-media-bypass and media-bypass certification separately per product, and some certified products, including Thinktel Think 365 SBC, Patton SmartNode eSBC, Frafos ABC SBC and Vodia PBX, are listed without media bypass. in context
• Cisco Unified Border Element on ISR 1000, ISR 4000, CSR 1000V and ASR 1000 is listed as supported from IOS XE Amsterdam 17.2.1r and on Catalyst 8000 Edge from 17.3.2, certified for media bypass, with 17.6.1a recommended except 17.3.3 on CSR 1000V. in context
• Direct Routing certification is granted to specific SBC firmware versions, and firmware higher than the documented version is supported as long as the major.minor version is the same. in context
• Oracle AP 1100, AP 3900, AP 3950, AP 4600, AP 4900, AP 6350 and VME are listed as supported on 9.x and 10.x, AP 6300 on 9.x and AP 6400 on 10.x, all certified for media bypass. in context
• Ribbon SBC 5400, SBC 7000 and SBC SWe variants are listed as supported on 11.1 and later, 10.1, 9.2 and 7.2, and Ribbon SBC 1000, SBC 2000 and SBC SWe Edge on 12.x and later, 11.x or 9.x, all certified for media bypass. in context
• For a Direct Routing issue the customer contacts the SBC vendor first, and escalating an SBC-related issue to Microsoft requires an SBC vendor investigation report carrying the vendor ticket reference. in context
• Microsoft lists Bandwidth Dynamic Location Routing, Intrado Emergency Routing Service and Inteliquent as the certified and supported 911 service providers for Direct Routing, and may reject support cases that involve a non-certified provider. in context
• Microsoft's certified SBC list marks non-media-bypass and media-bypass certification separately, and some certified products (for example Thinktel Think 365 SBC, Patton SmartNode eSBC and Frafos ABC SBC) are certified for non-media bypass only. in context
• Local Media Optimization support is listed in a separate table with its own minimum software versions (for example Ribbon SBC Core 8.2 or higher, anynode 4.0.1+, Avaya ASBCE 10.1.2 or higher), distinct from the media bypass certification versions. in context
• Media re-targeting is not supported: if the SBC signals a new media IP during a Direct Routing call, Teams Direct Routing never sends media to the new address even though it was negotiated in SIP. in context

Cite this source record

APA

WarmTransfer. (2026, May 27). Session Border Controllers certified for Direct Routing - Microsoft Teams. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-direct-routing-certified-sbcs

BibTeX

@misc{warmtransfer-ms-learn-direct-routing-certified-sbcs,
  title  = {Session Border Controllers certified for Direct Routing - Microsoft Teams},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/ms-learn-direct-routing-certified-sbcs},
  note   = {Microsoft, accessed 2026-09-14}
}