Cross platform
Bridges and future hooks
These are the paths that already exist. The hooks at the bottom are design seams, not features this lab turns on in your network.
| From | To | Bridge | Proof |
|---|---|---|---|
| CUCM | PSTN | SIP trunk to CUBE or a gateway | Both dial-peers and both SDPs |
| CUCM | Webex Calling | Local gateway, or a migration of the number | The location's PSTN choice and one test call |
| CUCM | UCCE | Route point, dialed number, JTAPI | Call type in the script, phone rings |
| Teams | PSTN | Calling Plan, Operator Connect, or Direct Routing | The user's connectivity type, then OPTIONS if it is an SBC |
| Teams | A contact center | Connect, Extend, or Unify, as Microsoft documents them | The certified model, not a guessed port |
| Webex Contact Center | Teams | The published Webex Contact Center app for Teams | A consult between agent and a Teams user, with an interaction id |
Hooks to leave in a design
- SIPREC on the SBC, so a future recorder has a defined leg. RFC 7866.
- CTI or the platform's webhook with a stable interaction id, so CRM and WFM can subscribe later.
- A test number that is not 911, routed like production, so each bridge has a canary.
- +E.164 on every boundary, so the next system does not invent its own habit.
None of these hooks place a call by themselves. They are names of interfaces you can write into a design review.