Track 17
Glossary, mind map, sister technologies, integration maps, bridges, and future hooks.
You can draw the mind map, configure a compliance-recording gate, and say which identifier joins the logs.
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.
Chapter list. Each room keeps its own sources.json.
Room files: T17-R01-voice-is-not-a-closed-box T17-R02-how-to-use-the-glossary T17-R03-the-mind-map T17-R04-compliance-recording-and-quality-management T17-R05-workforce-management T17-R06-e911-as-a-system-of-record T17-R07-analytics-and-power-bi T17-R08-crm-and-screen-pop T17-R09-ai-agents-beside-the-queue T17-R10-integration-maps T17-R11-cross-platform-bridges T17-R12-future-integration-hooks T17-R13-configuring-an-ecosystem-change T17-R14-troubleshooting-across-a-vendor-boundary
