Track 15
Call Automation is a server-side call with events. Speech and Copilot Studio can sit in the recognize step. Foundry is where you evaluate a model, not a second phone system.
You can sketch answer, play, recognize, and transfer, with a human escape.
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: T15-R01-calling-sdk-versus-call-automation T15-R02-teams-interop-from-acs T15-R03-an-ivr-as-events T15-R04-azure-ai-speech T15-R05-copilot-studio-voice T15-R06-foundry-and-what-not-to-invent
