Voice LabTeams Phone

17 · Ecosystem

Troubleshooting across a vendor boundary

The fault is usually on one side of a boundary. The argument is usually on both.

Room HTMLAll downloads

Learn it in 5 minutes

Name the boundary: Teams and SBC, SBC and carrier, Teams and recorder, queue and WFM, number and CRM. Collect the join key on both sides before anyone changes anything. Call-ID for SIP. E.164 for the CRM. Interval timestamp for WFM. Subnet for E911 and CQD.

One change, on the side the evidence names. Vendor-first if it is the SBC. Partner-first if it is the recorder. Do not restart a carrier trunk because a Copilot answer was wrong. Write the pack down so next month does not start from zero.

Across vendors, name the boundary and match the identifier. Then change one thing.

Room HTML

Visual

Survivable branch timelineBranch clientsSBA and SBCMicrosoft 365WAN down. Local PSTN only.Meetings and presence are not the survivable set.
What remains when the path to Microsoft 365 drops. Lesson: Troubleshooting across a vendor boundary.
Join keysSIP · Call-IDCRM · E.164 plus Call-IDWFM · IntervalQuality · Subnet
Use the key that matches the boundary. Counts in this drawing are teaching order, not customers.

SVGPNGHTML

Worked example

I name the boundary and the join key before I ask a vendor to change anything.

  1. Boundary Name it
  2. Key The same id both sides
  3. Side Where the evidence points
  4. Change One

If it fails: Three vendors change three boxes because nobody wrote down the Call-ID.

Checklist HTML

Quiz

A colleague reports: The carrier is asked for a recording they never made. Where do you start?

Which description of Retention of recordings is accurate?

A colleague reports: A regulator asks for a call and the partner’s bucket expired. Where do you start?

Flashcards

Ecosystem

Glossary

  • Convenience recording A user starts a recording of a call, meeting, or event. Policy can allow it. The user can stop it. Storage follows meeting rules. Config: Set the meeting, calling, and events policies on purpose. Fault: A regulated desk is told to ‘just hit record.’
  • Compliance recording A third-party recorder is invited by policy into new calls, meetings, and events. The user does not start it and participant consent is not the control. Notification is enforced. Config: Create the application instance, enable the policy, grant it, and test a new call. Fault: The policy is granted and nothing records because the bot instance was never created.
  • Compliance recording application The bot instance of a certified recorder. The policy references it. Without it, granting the policy does not record. Config: New-CsTeamsComplianceRecordingApplication attaches it to the policy. Fault: Recording works in the vendor’s cloud and never joins the Teams call.
  • Existing calls are unaffected When you grant a compliance recording policy, calls and meetings already up are not swept in. Test with a new call. Config: Place a fresh call after the grant and confirm the bot joined. Fault: The pilot says recording failed because they watched an old meeting.

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

Three vendors change three boxes because nobody wrote down the Call-ID.

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.

sources.json