Direct Routing
Your own carrier, connected to Teams through a session border controller (SBC) that we build and look after.
- Any carrier with SIP trunks
- SBC on Azure, AWS or on site
Enterprise Voice
Calling in Teams. Your numbers kept.
Microsoft Teams calling that replaces desk phones, at every site. We plan it country by country, build the connections and look after it.
- One phone system inside Teams, at every site
- Your numbers kept, with no gap in service
- Call quality you can measure every month
Three ways in
How calls reach Teams.
Each country has its own telecom rules, so we choose the connection site by site and check the local rules first.
Operator Connect
A carrier connects its network straight to Teams, and numbers are assigned in the Teams admin center. There is no SBC for you to run.
- Connection run by the carrier
- Numbers managed in Teams
Calling Plans
Microsoft is the phone company, and your numbers come from Microsoft. Calling Plans aren't sold in India, so Indian sites use one of the other two.
- Where Microsoft sells them
Four lanes
Everything voice, in one team.
Take one service or the whole move. Open a lane to see each service, what you get and how long it usually takes.
Lane 01
Enterprise Voice
Calling in Microsoft Teams that replaces desk phones and keeps your numbers.
- One phone system inside Teams, at every site
- Your numbers kept, with no gap in service
- Call quality you can measure every month
Works withTeams Phone, Direct Routing, Operator Connect, Calling Plans, Poly, Yealink, AudioCodes
All 13 services
| Stage | Service | What we do | You get | Typical time |
|---|---|---|---|---|
| Assess | Voice assessment | Numbers, call flows, carriers, network and licences reviewed against your plans. | A costed plan with the right connection for each country. | 1 to 2 weeks |
| Design | Connection design | Direct Routing, Operator Connect or Calling Plans chosen per country, with local rules checked. | A signed-off design for every site. | 1 to 2 weeks |
| Design | Number plan and dial plans | Number ranges, extensions, normalisation rules, voice routes and routing policies. | A number plan and dial plan workbook. | 3 to 5 days |
| Build | Direct Routing build | SBC pairing, PSTN usages, voice routes, policies and test calls on your own carrier. | Working Direct Routing with a signed test record. | 1 to 2 weeks |
| Build | Operator Connect setup | Carrier onboarding in the Teams admin center, numbers assigned and test calls made. | Operator Connect live, with numbers in Teams. | 3 to 5 days |
| Build | Auto attendants and call queues | Menus, business hours, holidays, queues, resource accounts and voicemail. | Call flows that match how your teams work. | 1 to 3 days |
| Build | Phones and shared devices | Certified desk phones, common area phones and headsets set up with the right policies. | Devices ready on every desk and in every lobby. | 2 to 3 days |
| Build | Emergency calling | Emergency addresses, network sites, policies and routing, as each country requires. | Tested emergency calling at each site. | 2 to 5 days |
| Build | Call recording | A certified recording partner connected to Teams, with retention rules set. | Recorded calls stored under your policy. | 2 to 4 weeks |
| Build | Survivable branch | Local Media Optimization and Survivable Branch Appliance for sites with weak links. | Calling that keeps working if a link fails. | 1 to 2 weeks |
| Build | User rollout | Users moved in waves, with number cutover, training and floor support. | Users live, with a report for each wave. | 1 to 2 weeks |
| Run | Call quality review | Teams call quality data and network checks, with a ranked list of fixes. | A quality report and fix plan. | 3 to 5 days |
| Run | Managed voice | Moves, adds and changes, carrier tickets, monitoring and a monthly review. | One team looking after your calling. | Ongoing |
Lane 02
Session Border Controllers & SIP
The secure gateway between your voice platform and the outside world.
- A voice edge that stays up and stays secure
- Clean connections to every carrier and PBX
- Faults traced to the packet, then fixed
Works withAudioCodes, Oracle, Cisco CUBE, Avaya SBCE, Azure, AWS, VMware
All 15 services
| Stage | Service | What we do | You get | Typical time |
|---|---|---|---|---|
| Design | SBC design and sizing | Session counts, transcoding, high availability, licences and where each SBC sits. | A design document and bill of materials. | 1 week |
| Build | Virtual SBC deployment | SBC built on Azure, AWS or VMware, with networks, certificates and base settings. | A working SBC, ready to pair. | 3 to 5 days |
| Build | Appliance SBC deployment | Hardware SBC racked, cabled, licensed and set up, on site or remotely. | A working SBC with its build sheet. | 3 to 5 days |
| Build | High availability pair | Active and standby SBCs, with failover tested before go-live. | A failover test record. | 2 to 3 days |
| Build | Teams Direct Routing connection | SBC paired to Teams, with TLS, SRTP, SIP options and media settings checked. | Teams calls running over your SBC. | 2 to 4 days |
| Build | SIP trunk integration | Carrier connection tested end to end: number formats, codecs, header rules and calls. | A tested trunk with an interop record. | 3 to 5 days |
| Build | PBX integration | Old PBX connected over SIP or a gateway, so both systems work during a move. | Calls flowing between the PBX and the new platform. | 3 to 5 days |
| Build | Analog and fax gateways | Gateways for analog lines, fax, lifts and door phones. | Analog devices kept working. | 1 to 2 days |
| Build | Routing and number rules | Routing tables, number and header manipulation, load sharing and failover routes. | Documented routing rules. | 1 to 3 days |
| Build | Security hardening | TLS, SRTP, certificates, access lists, topology hiding and call fraud limits. | A hardened SBC with a security checklist. | 2 days |
| Build | Upgrades and licences | Firmware upgrades, licence changes and config backups, with a rollback plan. | An upgraded SBC, tested after the change. | 1 day |
| Build | SBC vendor migration | Config translated to the new vendor, run in parallel and cut over route by route. | A move your callers never notice. | 2 to 3 weeks |
| Run | Troubleshooting | SIP traces and packet captures to find call drops, one-way audio and failed calls. | Root cause and fix, in writing. | 1 to 3 days |
| Run | Monitoring and alerts | SNMP, syslog and voice quality alerts into your monitoring tools. | Alerts and a monthly quality report. | 2 days to set up |
| Run | Managed SBC | Patching, certificate renewals, alerts and change control. | Your voice edge looked after under an agreed SLA. | Ongoing |
Lane 03
Telephony
Business phone systems, numbers and carriers, planned properly and looked after.
- Lower phone bills, with every line accounted for
- A phone system your people find easy
- One contact for carriers, numbers and faults
Works withCisco, Avaya, Mitel, Asterisk, 3CX, Twilio, Azure Communication Services
All 15 services
| Stage | Service | What we do | You get | Typical time |
|---|---|---|---|---|
| Assess | Telephony assessment | PBX, numbers, carriers, bills and contract dates reviewed in one place. | A report with costs and options. | 1 week |
| Assess | Bill and line audit | Carrier bills checked for unused lines, wrong tariffs and old contracts. | A list of savings, ranked by value. | 1 week |
| Assess | Network readiness for voice | Bandwidth, QoS, VLANs, PoE and test calls for jitter and packet loss. | A readiness report and fix list. | 2 to 3 days |
| Build | IP PBX deployment | Cloud or on-site PBX with extensions, hunt groups, voicemail and reports. | A working phone system, with user guides. | 1 to 3 weeks |
| Build | SIP trunks and carriers | Carrier comparison, order support and trunk setup, in line with local telecom rules. | A live trunk and a carrier contact list. | 1 to 3 weeks |
| Build | Numbers and porting | Number ranges, direct numbers and toll-free numbers ordered, ported and tested. | Numbers live, with a porting record. | 2 to 6 weeks |
| Build | IVR and call flows | Menus, time-of-day rules, voice prompts, overflow and after-hours handling. | Call flow diagrams and live menus. | 1 to 3 days |
| Build | Call recording | Recording for all or selected lines, with search and retention rules. | Recordings you can find and control. | 1 week |
| Build | Voicemail and fax | Voicemail to email and fax to digital, with old fax lines retired. | Messages delivered to the inbox. | 2 to 3 days |
| Build | Desk phones and DECT | IP phones and cordless handsets provisioned, with firmware and directory set. | Phones ready on every desk. | 2 to 3 days |
| Build | Multi-site dialling | Extension dialling between sites, least-cost routing and on-net calls. | One dial plan across your sites. | 2 to 3 days |
| Build | Programmable voice | Calling built into your own apps with Twilio or Azure Communication Services. | Voice features inside your product. | 2 to 6 weeks |
| Run | Legacy PBX support | An older PBX kept running until you are ready to move. | Time to migrate on your terms. | Ongoing |
| Run | Voice security | Toll fraud controls, screening of spoofed and unwanted calls, and call limits. | Fewer fraud calls and lower risk. | 1 to 2 weeks |
| Run | Managed telephony | Moves, adds and changes, carrier tickets and fault handling. | One contact for your whole phone estate. | Ongoing |
Lane 04
Migration to Teams
From any platform to Microsoft Teams, in planned waves, with your numbers intact.
- A move planned wave by wave, with a way back
- Numbers, call flows and rooms carried across
- Old contracts and licences closed down
Works withCisco, Avaya, Mitel, Skype for Business, Zoom, Webex, Google Meet, Slack, any PBX
All 15 services
| Stage | Service | What we do | You get | Typical time |
|---|---|---|---|---|
| Assess | Migration assessment | Users, numbers, devices, call flows, rooms and integrations listed for every site. | An inventory and a wave plan. | 1 to 3 weeks |
| Assess | Business case and licences | Cost today against cost on Teams, with the licences each user needs. | A business case you can take to finance. | 1 week |
| Assess | Network readiness | Bandwidth, QoS, firewall and Teams network tests at each site. | A readiness report and fix list. | 2 to 3 days |
| Build | Pilot | A small group moved first, with their feedback used to adjust the plan. | A pilot report and go-ahead. | 2 to 3 weeks |
| Build | PBX to Teams Phone | Cisco, Avaya, Mitel or any other PBX moved to Teams calling, site by site. | Users calling in Teams, and a shrinking PBX. | 1 to 2 weeks |
| Build | Skype for Business to Teams | Coexistence, upgrade modes, user moves and server removal. | Skype for Business retired. | 1 week |
| Build | Zoom to Teams | Zoom Meetings, Phone and Rooms moved, with scheduled meetings rebuilt. | One platform and one licence bill. | 1 week |
| Build | Webex to Teams | Webex Meetings, Calling and devices moved in planned waves. | One platform and one licence bill. | 1 week |
| Build | Slack to Teams | Channels, messages and files moved with a migration tool, and apps remapped. | Your history carried across. | 2 to 4 weeks |
| Build | Google Meet to Teams | Calendars, meetings and rooms moved, often alongside mail (see Lane 11). | Everyone meeting in Teams. | 1 week |
| Build | Numbers and call flows | Numbers ported or re-pointed, and hunt groups rebuilt as queues and attendants. | Callers notice nothing. | 1 to 4 weeks |
| Build | Devices and rooms | Desk phones, headsets and meeting rooms moved or replaced (see Lane 08). | Rooms and phones ready on day one. | 1 week |
| Build | User adoption | Champions, short guides, live sessions and floor walkers. | People using Teams with confidence. | With each wave |
| Run | Cutover and hypercare | Cutover weekends, a rollback plan and two weeks of close support. | Stable service, then a clean handover. | 1 to 2 weeks |
| Run | Decommissioning | Final data export, licences stopped, and old systems and contracts closed. | Old platform gone, and its costs stopped. | 1 to 2 weeks |
Before we start
What we'll ask, and what we'll need.
Questions we'll ask
- How many users need calling, and in which countries and sites?
- Which phone system and carrier do you use today, and when do the contracts end?
- How many numbers do you have, and which must stay?
- How many call flows, hunt groups and receptionists do you have?
- Which Microsoft 365 licences do your users have today?
- Do you need call recording?
- Which analog, fax or door phone lines must stay?
What we'll need from you
- A Teams admin contact
- Recent carrier bills and a full number list
- Network diagrams and a firewall contact
- A named owner at each site
Start with a voice assessment.
We review your numbers, call flows, carriers, network and licences against your plans, then send a costed plan with the right connection for each country.
Brand and product names belong to their owners and are shown as examples only. We choose platforms and carriers site by site and are not tied to any maker. You can also write to contact@whitelanes.in.