Direct Routing SBC
Session Border Controller configuration and TLS certificate setup, including failover.
Microsoft Cloud · Teams Phone
Teams Phone + Direct Routing
Replace your legacy PBX with Microsoft Teams Phone. Complete SBC configuration, number porting, call queues, and auto-attendants.
✓SBC and direct routing✓Number porting✓E911 configured
Capabilities
Everything you need for cloud telephony
The session border controller, the numbers and the call flows are all part of the scope.
Number porting
Seamless migration of existing numbers to Teams with LOA preparation and carrier coordination.
Call queues
Intelligent call distribution with overflow and timeout handling, music on hold and agent assignment.
Auto attendants
Interactive voice menus with business hours, holiday schedules and voice prompts.
Emergency calling
E911 configuration with location services and emergency routing.
User training
Comprehensive training for end users and administrators, plus documentation.
Business impact
What changes after cutover
One phone system inside the collaboration tool your team already uses.
PBX retiredcalls in Teams on desktop and mobile
Onenumber plan and directory
E911configured before go-live
Managedmoves, adds and changes included
Porting timelines depend on the losing carrier; the schedule is agreed in the statement of work.
Where it lands
Common use cases
Typical Teams Phone projects.
PBX replacement
Move off an ageing on-premises phone system without losing numbers.
Contact centre queues
Route sales and support queues with overflow and business-hours menus.
Multi-site organisations
One number plan across offices with E911 per site.
Hybrid work
Calling on desktop and mobile without a desk phone.
Technical specifications
How it is deployed
What you need for Teams Phone Direct Routing.
| Microsoft licensing | Microsoft 365 E3/E5 or Business Premium; Teams Phone System licence; Teams Phone add-on |
|---|---|
| Network requirements | Dedicated internet bandwidth, QoS configuration, firewall rules, public IP address |
| SBC requirements | Supported session border controller, TLS certificate from a trusted CA, domain registered in Microsoft 365, SIP trunk from the carrier |
| Deployment time | 4–6 weeks typical; porting scheduled with the carrier |
| Pricing | Quoted per engagement; no invented per-user rates |
Engagement options
Teams Phone packages
Scope by user count and redundancy; every package is quoted per engagement.
Starter
Best for: Up to 50 users
- SBC configuration
- One trunk
- Number porting (up to 10 numbers)
- Basic call routing
- 2 auto attendants
- User training
Timeline4–6 weeks
Quoted per engagementProfessional
Best for: Up to 200 users
- Everything in Starter
- Redundant SBC setup
- Multiple trunks
- Porting up to 50 numbers
- 5 call queues
- 5 auto attendants
- E911 configuration
- Advanced call routing
Timeline6–8 weeks
Quoted per engagementEnterprise
Best for: Unlimited users
- Everything in Professional
- Multi-site deployment
- Unlimited number porting
- Unlimited queues and attendants
- Custom integrations
- Dedicated project manager
- 24/7 support
TimelineCustom
Quoted per engagementUser bands are scope indicators, not prices. Porting volume and redundancy drive the final quote.
Modernise your phone system
Schedule a consultation to discuss your Teams Phone deployment and the porting plan for your numbers.
Existing partner? Sign in to the partner portal for contract pricing, order status and invoices.
Keep going