Microsoft Teams Phone · Powered by Centra IP
Your team already lives in Teams. Put the phone system there too.
Microsoft secures it. Centra IP connects and manages it. One app for calls, chat, and meetings — on the same identity, the same compliance policies, and the same device your people already use.
No second phone app. No separate bill to chase. No PBX in the closet.
30 minutes · We check your licensing and numbers · Call 844-534-1240
The caller
PSTN • Mobile
Landline
Centra IP voice network
Certified operator
Numbers + carrier
Microsoft Teams Phone
Entra ID • Compliance
Desktop • Mobile • Desk
The caller
PSTN • Mobile
Landline
Centra IP voice network
Carrier + numbers
Redundant routing
Managed SBC
Session border ctrl
Encryption • Failover
Microsoft Teams Phone
Entra ID • Compliance
Desktop • Mobile • Desk
1 app
Calls, chat & meetings
2 paths
Operator Connect or Direct Routing
Keep
Your existing numbers
1 partner
Voice, network & support
Microsoft + Centra IP
Microsoft builds the platform. We make it a phone system.
Teams Phone is excellent software and a terrible do-it-yourself project. The gap between “we have licenses” and “every call routes correctly on day one” is where we live.
Secure by inheritance
Calls run on the same Microsoft 365 identity your email does — Entra ID sign-in, conditional access, MFA, and your existing retention and compliance policies. Voice stops being the one system outside your security perimeter.
Reliable by design
Carrier-grade voice on redundant routing, with failover paths that send calls to mobiles or an alternate number if something upstream breaks. Two decades of running business phone systems sits behind the configuration.
Easy because nothing is new
Your staff already know Teams. There's no new app to install, no training curve, and no "which one do I answer?" moment. The dial pad simply appears in an interface they open every morning.
Two ways to connect
Operator Connect or Direct Routing.
Teams Phone is excellent software and a terrible do-it-yourself project. The gap between “we have licenses” and “every call routes correctly on day one” is where we live.
- Simplest path
Operator Connect
Provisioned inside Teams admin cent
You select Centra IP as your operator from within the Microsoft Teams admin center, and numbers flow into your tenant. There’s no session border controller to purchase, host, or maintain that infrastructure sits on our side and peers directly with Microsoft.
- No SBC to own. Nothing to buy, rack, patch, or fail over.
- Fast to stand up.Numbers assigned in the admin center rather than through a build project.
- Direct peering with Microsoft. Fewer hops between the carrier network and your tenant.
- One place to manage users.. Assign and change numbers where you already manage licenses.
Best fit
Cloud-first organizations that want dial tone in Teams quickly, don’t have analog devices to preserve, and would rather not run voice infrastructure.
- Most flexibl
Direct Routing
Connected through a managed SBC
A session border controller sits between our voice network and your Microsoft tenant, giving you control over how calls are routed, translated, and failed over. We host and manage the SBC, so you get the flexibility without the hardware.
- Keeps analog alive..Elevator phones, fax lines, overhead paging, door intercoms, alarm dialers.
- Runs alongside your old PBX.Migrate department by department instead of flipping everything in one night
- Custom routing rules..Least-cost routing, per-site call paths, number manipulation, third-party contact center integration.
- Carrier flexibility. Regional coverage and existing carrier contracts can stay in play.
Best fit
Multi-site operations, businesses with analog or legacy equipment that isn’t going away, phased migrations, and anyone with routing requirements that don’t fit a template.
| Consideration | Operator Connect | Direct Routing |
|---|---|---|
|
Session border controller |
Not required
|
Managed by us
|
|
Typical time to deploy |
Faster |
Longer |
|
Setup complexity |
Low |
Moderate |
|
Analog & legacy devices |
Limited |
Supported |
|
Coexist with existing PBX |
Limited |
Supported |
|
Custom call routing rules |
Standard |
Granular |
|
Keep your existing numbers |
yes |
yes |
|
Managed end to end by Centra IP |
yes |
yes |
Still not sure which one fits?
Tell us how many sites you have and what’s plugged into the old phone system. That conversation usually answers it in ten minutes.
Included either way
Everything a business phone system has to do.
Configured for how your organization actually answers calls — not left at defaults.
Auto attendants
Menu trees, business-hours routing, and holiday schedules that don’t need a ticket to change.
Call queues
Ring groups, hunt patterns, overflow and timeout handling for sales, support, and the front desk.
Voicemail transcription
Messages arrive as readable text in Teams and email, so nobody sits through a two-minute ramble.
Emergency calling
Dynamic location handling configured per site so a 911 call reaches the right dispatcher with the right address.
Call recording
Retained under your existing Microsoft 365 compliance and retention policies, not a separate silo.
Analytics & reporting
Call volumes, answer rates, missed calls by queue, and per-user activity from the Teams admin center.
Desk phones & headsets
Teams-certified handsets, conference room phones, and common-area devices — sourced and provisioned by us.
Mobile & remote
The same extension rings the desktop, the phone, and the browser. Remote staff are just extensions.
Migration
Nobody loses dial tone.
The old system stays live until the new one is proven. Porting happens on a scheduled window you approve.
STEP 01
Readiness review
We audit your Microsoft licensing, network readiness, current carrier contracts, and every device on the old system.
STEP 02
Design & build
Connection method, call flows, queues, auto attendants, and emergency addressing get built and tested in your tenant.
STEP 03
Pilot group
A small group runs live on Teams while the old system still answers. We fix what surfaces before it reaches everyone.
STEP 04
Port & support
Numbers port on an approved window, then ongoing changes, adds, and troubleshooting run through our help desk.
Free readiness call
Find out what your Teams tenant can already do.
Thirty minutes. We look at your licensing, your numbers, and what’s plugged into the old system, then tell you which connection method fits and roughly what it costs. If Teams Phone isn’t right for you, we’ll say so.
calendly.com/patrickb-centraip/30min · No obligation
Common questions
What IT managers ask first.
Teams Phone requires a Teams Phone license per calling user, which some Microsoft 365 plans include and others add on. Part of the readiness call is checking exactly what your tenant already carries — organizations are frequently paying for entitlement they haven’t turned on.
Yes. Numbers port over on a scheduled window you approve, and the old system stays live until the port completes. Main lines, direct dials, and toll-free all come along.
This is usually the deciding factor between the two connection methods. Direct Routing handles legacy analog equipment cleanly through the SBC. If you have elevator lines, alarm dialers, or overhead paging, bring the list to the readiness call.
Yes, and with Direct Routing it’s straightforward — Teams can run alongside your existing PBX while you move department by department. We always pilot a small group first regardless of method.
Us. That’s the point of running it through Centra IP rather than assembling it yourself — you get one number for the carrier side, the Teams configuration, and the network underneath, instead of three vendors pointing at each other.
It is when the network underneath is right, which is why the readiness review looks at bandwidth, QoS, and firewall configuration before anything gets deployed. Teams call quality problems are almost always network problems wearing a costume.