Track 14

Coexistence and CCaaS

Connect, Extend, and Unify are different media paths. CUCM, Webex, UCCE, Genesys, and Amazon Connect each need a named bridge, not a slogan.

Track sheetPNGPDF

Learn it in 5 minutes

You can say which model a design is, and where CUBE sits between CUCM and Teams.

Visual

Three models on LearnConnect · SBCExtend · Graph and clientUnify · ACS-native
Current names as of 14 October 2026. Counts in this drawing are teaching order, not customers.

Rooms

  1. Connect, Extend, and Unify 8 min
  2. Teams Phone extensibility 6 min
  3. CUCM and CUBE 8 min
  4. Webex calling interop 6 min
  5. UCCE during a move 6 min
  6. Genesys and Amazon Connect 7 min

Ecosystem

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.

Sources and go deeper

Chapter list. Each room keeps its own sources.json.

Room files: T14-R01-connect-extend-and-unify T14-R02-teams-phone-extensibility T14-R03-cucm-and-cube T14-R04-webex-calling-interop T14-R05-ucce-during-a-move T14-R06-genesys-and-amazon-connect