Sentinel Mini SBC
A compact SBC for a branch or a dedicated SIP edge.
- Selection criterion
- Required sessions, network ports, power supply and license.
Use Case
Microsoft Teams Migration
Move enterprise voice to Teams while preserving carriers, PBXs, analog systems and operational control.
Products to compare
A starting point for your project. Review the model data sheet before ordering.
Sentinel 400 SBC & Gateway
A modular voice edge for sites with mixed telephony interfaces.
- Selection criterion
- Interface modules, session license, power and resilience requirements.
Sentinel CS Virtual SBC
An SBC deployed on your virtual infrastructure.
- Selection criterion
- Supported hosting environment, CPU resources and licensed capacity.
CALL-PATH SCHEMATIC
Trace the microsoft teams migration path end to end.
Every device and service is part of a live operating workflow. The diagram makes the translation point, trust boundary and acceptance target visible.
NO PUBLIC INTERNET REQUIRED
Private LAN / isolated IP network
The on-premises PBX, Mediatrix gateways and local endpoints can retain an internal call path. This local path does not become dependent on the public Internet simply because Teams is added.
REQUIRED FOR TEAMS & PUBLIC CALLING
Microsoft 365 and SIP carrier connection
Teams Phone, Direct Routing and calls to the public telephone network require working connectivity to the applicable Microsoft and carrier services. The diagram shows that external path separately.
PRIVATE CUSTOMER NETWORK
Existing PBX
Can coexist during a phased Teams migration.
Mediatrix gateway
Preserves approved analog phones, fax, modems and legacy trunks.
Teams & legacy users
Users communicate across one engineered dial plan during transition.
PRIVATE IP NETWORK / LANLocal SIP signaling + RTP media
INTERNALIndependent local pathLocal PBX, gateways and extensions can keep communicating even though the cloud route is shown separately.
CONTROLLED EDGE
DIRECT ROUTING
Certified Sentinel SBC
Translates Teams requirements into controlled SIP signaling, media and routing.
EXTERNAL SERVICE NETWORK
Microsoft Teams Phone
Hosts users and calling features in Microsoft 365.
SIP carrier
Provides numbers and public telephone access.
SIP over TLSSRTP mediaE.164 routingCoexistence
READING THE DIAGRAM
Follow one call from the cloud to the telephone network
- Cloud voice platform
- Hosts communications services such as Microsoft Teams Phone or CCaaS outside the customer site.
- Sentinel SBC
- Secures and normalizes SIP between voice domains, controls media and routing, and hides the internal network.
- SIP carrier
- Connects the organization to the public telephone network and supplies telephone numbers and external call routes.
- PBX or call server
- Controls extensions, features and call routing. It may run on-site, in a data center or as a hosted service.
Use-case model — field validation remains mandatory for endpoints, carriers and safety-related workflows.
VALIDATION MATRIX
The checks that prevent a silent failure after cutover.
A microsoft teams migration design should answer each question before rollout, not after the first incident.
Safety, emergency, alarm and regulated services require approval from the responsible authority and service provider for the actual deployment.| Validation layer | Question to answer | Evidence to collect | Owner |
|---|---|---|---|
| Endpoint | Does the real device behave correctly over the new path? | Dialing, media and feature test | Customer / integrator |
| Network | Are latency, jitter, NAT and QoS controlled? | Capture and quality baseline | Network team |
| Service | Does the carrier support the required call or data behavior? | Carrier-accepted test result | Carrier / service owner |
| Failure | What happens during power, WAN or platform loss? | Failover and recovery test | Operations |
| Lifecycle | Who owns updates, certificates, backups and escalation? | Approved runbook and entitlement | Service owner |
FREQUENTLY ASKED
What to know before the next step.
The most common risk is assuming endpoint, carrier or network behavior instead of validating it in the actual call path.
Use a repeatable reference architecture, but confirm site-specific power, WAN, interfaces, endpoints, local routing and operational constraints.
The pilot should prove real workflows, not only dial tone: features, media quality, exceptional routes, failover, monitoring and recovery.
READY FOR THE NEXT STEP?Request a free review
Build the right voice architecture.
Share the product, deployment and target outcome. M5 will identify the right technical and commercial path.