14 · Coexistence and CCaaS

CUCM and CUBE

Most Teams migrations in a Cisco estate are a dual-run, not a weekend miracle.

Room HTMLAll downloads

Learn it in 5 minutes

A calling search space is closest to a voice routing policy’s ordered usages, and it is not a one-to-one object. A translation pattern is closest to a dial-plan rule. A route pattern is closest to a voice route. There is no partition object in Teams. Pick one system to normalize numbers.

Calls from people still on CUCM to people now on Teams trombone through CUBE. That is normal during dual-running and expensive as a steady state. Move groups that call each other in the same wave. Keep the old route until rollback is boring.

Translate CUCM ideas carefully, normalize in one place, and keep the old route until the new path is quiet.

Room HTML

Visual

SIP over TLS toward the carrierUsersip3SBCINVITEINVITE180200ACK
Signaling for CUCM and CUBE. Teams keeps the dialog. A 488 is codecs, not a greeting.
CUCM ideas, looselyCSS · Policy plus usagesTranslation · Dial planRoute pattern · Voice routePartition · No Teams object
Not one-to-one. The lab says the gap. Counts in this drawing are teaching order, not customers.

SVGPNGHTML

Worked example

One normalization owner. Tromboning is temporary. Rollback keeps the old trunk.

  1. Map CSS to policy, translation to dial plan
  2. One owner Normalization
  3. Dual-run Trombone expected
  4. Rollback Old route still there

If it fails: Both systems add +44, or the old trunk is deleted on Friday.

Checklist HTML

Quiz

Which description of Teams Phone extensibility is accurate?

A colleague reports: Two phone systems ring the same person. Where do you start?

Which description of CUBE as a bridge is accurate?

Flashcards

Ecosystem

Glossary

  • Connect model A certified contact center attaches to Teams through certified SBCs and Direct Routing. Config: Confirm the vendor’s current certification, then design the SBC and the transfer target’s license. Fault: Transfers to experts fail because the expert has no Teams Phone number.
  • Extend model The contact center uses the Teams client, Graph, and Cloud Communications APIs. Teams Phone is the calling system and the agent works in Teams. Config: Read the Extend section of the contact-center article before you license agents. Fault: The design buys a Connect SBC for an Extend product.
  • Unify model The model Microsoft Learn names, as of 14 October 2026, for a native experience. Partner material describes it as ACS-based applications on Teams calling infrastructure. Older decks say Power. Ask which current model a vendor holds. Config: Get the vendor’s certification letter and match it to Connect, Extend, or Unify. Fault: A proposal says Power and nobody can find the media path.
  • Teams Phone extensibility A way for a contact center, including Dynamics 365 Contact Center, to use a customer’s existing Teams Phone for the agent’s telephony. Config: Use a solution that has finished the certification if you want the supported experience. The API existing is not the same as a finished certification. Fault: Two phone systems ring the same person.

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

Both systems add +44, or the old trunk is deleted on Friday.

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