09 · Devices and media
A branch SBC with one public interface can still hairpin local users out and back.
Local media optimization uses internal and external SBC interfaces so a user inside the branch stays on the local media path. It is more specific than a single bypass checkbox. Use the current article and the SBC vendor’s build.
If internal users hairpin to the public address of an SBC sitting on their own LAN, you have not finished the design. Draw the interfaces before you enable the feature.
Local media optimization keeps branch media on the internal SBC interface. Draw the interfaces.
Local media optimization is about which SBC interface the media uses. I will draw both.
If it fails: Users on the LAN hairpin through the public internet to reach an SBC in the same rack.
Which description of Media bypass flag is accurate?
The gateway setting that allows media to skip Microsoft’s processors. It is not implied by a short ping. Leave it off until the path is drawn. Source: https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan accessed 2026-10-14.
A colleague reports: It is enabled tenant-wide in someone’s notes and only one site can route to the SBC. Where do you start?
It is enabled tenant-wide in someone’s notes and only one site can route to the SBC. Set it on the paired gateway, then test from the real subnet. Source: https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan accessed 2026-10-14.
Which description of Processor path is accurate?
The default media path through Microsoft media processors in the region closest to the call. Use it when bypass is unsafe. Source: https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan accessed 2026-10-14.
Around the call: compliance recording, workforce management, emergency location, analytics, CRM screen pop, and an agent with a human escape. Each one has its own failure.
Users on the LAN hairpin through the public internet to reach an SBC in the same rack.
Cisco CUBE is one of the SBC families named in this lab’s certification lesson. A certified release can be the Direct Routing SBC between Unified CM and Teams.
The tenant still needs a verified domain on the SBC FQDN, and the user still needs Teams Phone. The studio translator does not open a live AXL session. Confirm the current certified release before you build.
Teams Phone and Webex Calling are separate clouds. This lab does not describe a feature that registers a Webex Calling user into a Teams tenant.
A number move is usually a carrier port, a certified SBC, or a meetings interop product. Confirm before relying.
Unified CCE stays the ACD until you migrate it. Microsoft’s contact-center articles name Connect, Extend, and Unify. They do not name a UCCE connector in the notes this lab cites.
Voice into Teams is still Direct Routing or Operator Connect. The routing script stays on the contact-center product you bought. Confirm the vendor’s current model. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-contact-center.
Copilot Studio, Azure Communication Services, and Graph are later tracks in this lab. Treat any uncited limit as confirm before relying.
Opened 2026-10. A row marked confirm did not open. Wikipedia is background. The Teams blog row is the community index.
