The Architect’s Notebooks · Edition 03

Secure the voice, protect what works: the role of the SBC in a Mitel and Microsoft Teams migration

How to modernise telephony and contact centres step by step, without putting customer relationships at risk.

ARCA CX Solutions · Telecom architecture · November 2026

SIP securityPhased migrationBusiness continuityMicrosoft TeamsMitel CX

Why voice deserves a dedicated architecture

Telephony remains a business-critical service. A customer calling about an order, an emergency or a support request expects to reach the right person, whatever technical changes are under way.

Yet voice traffic often relies on security equipment run to the constraints of the IT network. A firewall update, a routing change or a new security policy can disrupt SIP signalling and audio streams.

The point is not to set IT and telecom teams against each other, but to build shared governance with expertise specific to real-time communications. That is the role of the Session Border Controller, or SBC.

A voice-dedicated SBC does more than protect calls. It keeps telephony changes under control, secures interconnections and prepares migrations without interrupting customer relationships.

Seven reasons

What a voice-dedicated SBC brings

01Governance

Voice 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
02Migration

Migrate 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 Teams

Teams 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

04Mitel

MiVoice 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 continuity

Continuity 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
06Interoperability

Fewer 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 channels

A 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.

Common objections

What we are often asked

QuestionOur answer
“Our firewall already handles SIP.”A SIP ALG is not an SBC: no SIP normalisation, limited media handling, no Teams certification, and updates follow network security priorities.
“Teams Phone is enough.”Teams provides auto attendants and call queues, which cover many needs. Demanding contact centres need skills-based routing, supervision, history and business integration: that is the role of Mitel CX.
“It is one more box to maintain.”It is virtualised and maintained under the voice contract by the integrator, not by the security team.
“What if the SBC fails?”Depending on licences and architecture: redundancy, alternative paths and automatic failover, validated through acceptance testing.

The ARCA LAB

Test before you migrate

Our integration lab combines MiVoice 5000 R8.4, Mitel CX 3.0 and CX Ignite, OpenScape SBC, Microsoft Teams, CRM applications and automation. It lets us study realistic scenarios before proposing them.

ScenarioStatus
Carrier call to MiVoice then Teams, with caller ID displayedValidated
Teams call queue overflowing to a Mitel extensionValidated
Calls delivered to CX Ignite with number, queue and IDValidated
Forwarding to Teams voicemailValidated
WhatsApp Business calls over SIP through the SBCUnder qualification
High availability and chosen virtualisation platformPending vendor validation

The LAB also showed how much SIP session sizing matters: a forward or an overflow can use several resources on the PBX. We size this from the scoping phase.

Method

The ARCIA™ method applied to telephony migration

  1. AAuditEquipment, licences, call flows, network constraints and risks
  2. RRedesignTarget architecture, migration pathways, continuity scenarios
  3. CConnectionsTelephony, Teams, contact centre and business applications
  4. IIntelligenceAutomation and AI features that help the teams
  5. AAccompanimentPilot, acceptance, cut-over and operations

Modernise without weakening

A company does not need to replace everything to modernise its communications. It needs to understand its existing estate, secure its interconnections, control its dependencies and choose a pathway that fits how people work. The SBC is an important part of this, when it is integrated into a well-designed, well-run architecture.

Preparing a migration?

Keep your Mitel telephony, integrate Microsoft Teams, modernise your contact centre or strengthen business continuity: start with a 30-minute conversation.

+33 1 85 46 01 79 · contact@arcacx.com

Product capabilities depend on the release, licences and architecture chosen. LAB results are not vendor certifications.