Voice LabTeams Phone

09 · Devices and media

SIP Gateway and analog

Elevators, door phones, and fax machines do not run the Teams client.

Room HTMLAll downloads

Learn it in 5 minutes

Leave analog on a certified SBC or on SIP Gateway when the device is supported. Direct Routing is the usual way to keep those devices when the humans move to Teams. A Calling Plan user license does not create an elevator phone.

Test the emergency path from the analog device, including during a WAN cut if the device must keep working. An elevator that depends on a cloud sign-in is a bad surprise.

Keep analog devices on an SBC or SIP Gateway, and test their emergency path.

Room HTML

Visual

OPTIONS health12345678SIP OPTIONS
Repeated misses take a trunk out of service. The campus does not invent Microsoft's internal counter.
Where analog sitsSBC · UsualSIP Gateway · Listed devicesTeams client · Not for elevators
Not on a user client. Counts in this drawing are teaching order, not customers.

SVGPNGHTML

Worked example

Analog stays on the SBC or SIP Gateway, with an emergency test from that device.

  1. Device Analog
  2. Front SBC or SIP Gateway
  3. Number Service number
  4. Emergency Tested from that device

If it fails: The elevator is migrated to a Teams user and fails when the WAN fails.

Checklist HTML

Quiz

Which description of SIP Gateway is accurate?

A colleague reports: A generic analog adapter is plugged in and never registers. Where do you start?

Which description of Teams-certified phone is accurate?

Flashcards

Ecosystem

Glossary

  • Teams Rooms license Rooms use their own SKU family, not a borrowed user Calling Plan. Names such as Basic and Pro change. Check the current name. Config: Assign the current room license to the room account and keep Conditional Access from blocking the device. Fault: The room account has a user E5 stack and still fails sign-in policy.
  • Media bypass Media can flow between the Teams client and the SBC, skipping Microsoft’s media processors. Signaling still goes through Teams. Config: Enable it on the gateway only when the client can reach the SBC and LBR does not forbid the path. Fault: Bypass is on for a VPN user and audio is worse than the processor path.
  • Local media optimization A Direct Routing pattern with internal and external SBC interfaces so a branch user stays on the local media path. Config: Use the current media optimization article and the SBC vendor’s build. Fault: Internal users hairpin out to the internet and back to the SBC on the same LAN.
  • SIP Gateway Microsoft’s front end for certain compatible analog and SIP devices that are not Teams phones. Config: Check the current supported device list before you buy handsets. Fault: A generic analog adapter is plugged in and never registers.

Sister technologies

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.

Config and troubleshooting

The elevator is migrated to a Teams user and fails when the WAN fails.

Cross-platform bridges

CUCM

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.

Webex

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.

UCCE

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.

Future hooks

Copilot Studio, Azure Communication Services, and Graph are later tracks in this lab. Treat any uncited limit as confirm before relying.

BridgesEcosystem

Sources and go deeper

Opened 2026-10. A row marked confirm did not open. Wikipedia is background. The Teams blog row is the community index.

  • SIP Gateway — Microsoft Learn — last checked 2026-10.
  • Survivable Branch Appliance — Microsoft Learn — last checked 2026-10.
  • RFC 3550 — RFC — last checked 2026-10.
  • RFC 3711 — RFC — last checked 2026-10.
  • Session Initiation Protocol — Wikipedia — last checked 2026-10. Wikipedia fallback for background. Confirm the vendor page before you change a tenant
  • Microsoft Teams blog index — Community — last checked 2026-10. Community index for the Microsoft Teams blog. This is the index, not a claim that a post discusses this room

sources.json