01GovernanceVoice governed by those accountable for it
A dedicated SBC gives clear ownership of SIP security and routing, configuration changes and rollback procedures. It complements existing firewalls; it does not replace them.
- Change windows owned by the voice and contact centre teams
- SIP-aware security: source validation, signalling and media inspection, dynamic media pinholes
- Diagnostics suited to telephony incidents
02MigrationMigrate by user population, no big bang
The SBC can orchestrate coexistence between the PBX, Teams and the contact centre. Users move by department, site or job role, with acceptance tests and rollback paths prepared in advance.
- Agents stay on Mitel CX while knowledge workers move to Teams
- Numbers and call journeys preserved where the numbering plan, carriers, routing and portability allow
03Microsoft TeamsTeams Direct Routing with a certified SBC
Microsoft publishes the list of SBCs certified for Direct Routing. It includes Mitel’s OpenScape SBC (V10R2.2.0 or later) and the Mitel Session Border Controller, with and without media bypass. Certification applies to a given product and release.
Microsoft Learn · SBCs certified for Direct Routing
04MitelMiVoice 5000, Teams and Mitel CX: each with its role
Mitel documents the integration of MiVoice 5000 with Teams through OpenScape SBC. The SBC handles SIP interconnections, Mitel CX keeps call distribution and supervision, and CRM and automation enrich interactions. Presence, recording and phone control are validated separately.
Mitel · MiVoice 5000 and Microsoft Teams through OpenScape SBC
05Business continuityContinuity is designed from day one
Depending on products and licences, an architecture can include redundant SBCs, alternative paths and failover policies. But continuity never rests on a single device: it spans carriers, the PBX, inter-site links and the contact centre, and is proven through acceptance testing, never by a failover time promised upfront.
- Loss of an SBC or a carrier
- Failure of a telephony server or a link
- A failed update
06InteroperabilityFewer interfaces, controlled interoperability
An SBC acts as the boundary between carriers, PBXs and collaboration platforms where SIP behaviour, codecs or encryption differ. Some incompatibilities are handled at the interconnection instead of changing every system. Responsibilities remain shared between vendors, carrier and the integrator, who coordinates the whole.
07New channelsA reliable foundation for AI and new channels
Voice agents, automatic qualification, calls from messaging apps: these services need a reliable communications foundation. The SBC secures the relevant SIP voice flows; APIs, messages and application data are handled by other components. AI does not replace security, availability and audio quality requirements.