Track 12

Troubleshooting

Call Analytics is one call. CQD is a building. The SBC trace is the ladder. Mixing them up wastes the hour.

Track sheetPNGPDF

Learn it in 5 minutes

You can pick the tool that matches the scope of the fault and name one hypothesis.

Visual

Scope the evidenceOne call · Call AnalyticsBuilding · CQDTrunk · OPTIONSLadder · SBC trace
Which tool, not a made-up rate. Counts in this drawing are teaching order, not customers.

Rooms

  1. One hypothesis 6 min
  2. Reading a ladder 8 min
  3. Call Analytics 6 min
  4. Call Quality Dashboard 8 min
  5. Trunk health 6 min
  6. A fault catalog 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: T12-R01-one-hypothesis T12-R02-reading-a-ladder T12-R03-call-analytics T12-R04-call-quality-dashboard T12-R05-trunk-health T12-R06-a-fault-catalog