Cross-platform bridges

Learn it in 5 minutes

The bridge is a certified SBC, often CUBE, with one normalization owner, a written number range, and a rollback that still has the old route. Identity is not shared automatically between CUCM and Entra. Presence is not a call route. Chat interop is not voice.

Genesys needs a named Connect, Extend, or Unify certification. Amazon Connect needs a drawn SIP path. UCCE agents stay put until the contact-center migration is its own project. Tromboning during dual-running is expected and should not become the steady state.

Bridge other platforms with a certified SBC, one place that normalizes, and a rollback you still have.

Room HTML

Visual

SVGPNGHTML

Worked example

A cross-platform voice bridge is an SBC, one normalizer, written ranges, and a rollback.

1. SBC The bridge
2. Ranges Written
3. Normalize One owner
4. Rollback Old route remains

If it fails: Both systems transform numbers, or the old trunk is deleted the same night.

Checklist HTML

Quiz

Flashcards

Ecosystem

Glossary

• Convenience recording A user starts a recording of a call, meeting, or event. Policy can allow it. The user can stop it. Storage follows meeting rules. Config: Set the meeting, calling, and events policies on purpose. Fault: A regulated desk is told to ‘just hit record.’
• Compliance recording A third-party recorder is invited by policy into new calls, meetings, and events. The user does not start it and participant consent is not the control. Notification is enforced. Config: Create the application instance, enable the policy, grant it, and test a new call. Fault: The policy is granted and nothing records because the bot instance was never created.
• Compliance recording application The bot instance of a certified recorder. The policy references it. Without it, granting the policy does not record. Config: New-CsTeamsComplianceRecordingApplication attaches it to the policy. Fault: Recording works in the vendor’s cloud and never joins the Teams call.
• Existing calls are unaffected When you grant a compliance recording policy, calls and meetings already up are not swept in. Test with a new call. Config: Place a fresh call after the grant and confirm the bot joined. Fault: The pilot says recording failed because they watched an old meeting.

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 transform numbers, or the old trunk is deleted the same night.

Cross-platform bridges

Future hooks

Copilot Studio, Azure Communication Services, and Graph are later tracks in this lab. Treat any uncited limit as confirm before relying.

BridgesEcosystem