Multi-country UC rollouts (Microsoft Teams Phone, Zoom Phone, Webex Calling, RingCentral) depend on a specialist voice and PSTN layer that Ecosmob, NUWAVE, Babelforce, BT Wholesale, Tata Communications, and regional SIP trunk providers deliver.
This layer handles direct routing, SBC deployment, SIP trunk provisioning per country, number porting, and emergency calling compliance, the parts of the rollout that global system integrators (AVI-SPL, NTT, Insight, CDW) almost always subcontract because the work requires deep telecom engineering rather than IT deployment skills.
If you’re planning a UC rollout across 5 or more countries, the voice layer is where most of the unexpected delays and budget overruns come from. The platform itself goes live in weeks; the per-country voice connectivity takes months.
This is the layer most asker questions undervalue and most rollouts underestimate. Below is what the voice layer actually involves, who delivers each piece of it, and how to keep it from breaking your timeline.
Why the voice layer takes 4x longer than the platform layer
Microsoft Teams Phone, Zoom Phone, and Webex Calling all work the same way once you have voice in. Getting voice in is where time disappears.
Number porting in the United States takes 5 to 10 business days on average. In Germany, France, and the UK, expect 15 to 30 days. In Brazil, India, and Indonesia, 45 to 90+ days, sometimes longer when the losing carrier has a contractual incentive to slow things down. Multiply that across 12 countries and the rollout calendar suddenly has six-month dependencies the program manager didn’t see coming.
Emergency calling is the second time sink. Ray Baum’s Act and Kari’s Law in the US require dispatchable location and direct 911 access from every endpoint. The EU has 112 obligations that vary by country. Australia, Japan, India, and most APAC countries each have their own emergency calling rules. Getting this wrong is not a configuration error; it’s a regulatory liability. A specialist partner that has shipped emergency calling for Teams or Zoom in your specific countries is worth more than one that hasn’t, regardless of price.
Direct routing is the third. Microsoft Teams supports Operator Connect (carrier-provided), Direct Routing (your own SBC), or Microsoft Calling Plans (Microsoft-provided). Each path has different country availability, different cost structures, and different operational complexity. A real partner walks you through the choice for each country individually rather than recommending the same path everywhere.
What the specialist voice layer actually delivers
Five things, none of which the global SI doing your office rollout will do internally:
SBC deployment and direct routing configuration. For Teams Direct Routing or equivalent in Webex Calling, the SBC sits between the platform and your SIP trunks. Production-grade deployments use redundant SBCs (AudioCodes, Ribbon, or Oracle ACME) in each region with failover patterns. NUWAVE’s iPILOT and Synthesis platforms automate parts of this for Teams, Zoom, and Webex specifically. Ecosmob designs and deploys the SBC layer for custom requirements and for platforms where the off-the-shelf automations don’t fit.
SIP trunk procurement and management, country by country. Each country has different incumbent carriers, different regulatory rules on who can sell SIP trunks, and different pricing. Tata Communications, BT Wholesale, and Babelforce cover global footprints. Smaller regional carriers are sometimes cheaper but require local expertise to manage. The work is part procurement and part engineering: negotiate the contracts, then configure the trunks to actually work with the UC platform’s expectations.
Number porting orchestration. Submit port-out requests to losing carriers, manage the timeline, handle the inevitable rejections (wrong CSR, mismatched billing address, account holder doesn’t match), and coordinate the actual cutover. This is mostly project management with a deep technical layer. Specialist firms have the legal templates and the carrier relationships to move things along.
Emergency calling implementation per country. For each location in scope, this means setting up dispatchable location data, ensuring emergency calls route to local PSAPs (Public Safety Answering Points) correctly, and testing the path. The testing piece is non-negotiable. Most failures here go undetected until someone actually dials emergency services, which is the worst time to find out.
Long-term voice operations and monitoring. After the rollout, someone has to monitor SIP transaction success rates, RTP packet loss, MOS scores, and SBC capacity across all the regions you went live in. Tools like Homer SIP capture and RTPEngine analytics are standard. The specialist that ran the rollout often stays on for the operations layer because the institutional knowledge is theirs.
How to structure the engagement
The cleanest model is to have a direct contractual relationship with the voice specialist, not have them subcontracted under the global SI doing your office rollouts. Three reasons. First, the voice layer has the longest lead times, so you need visibility into it independently of the SI’s project plan. Second, the SI’s incentives push them to mark up the voice work and treat it as a black box. Third, when something goes wrong in production six months after launch, you want to be calling the voice specialist directly, not opening a ticket with the SI that then forwards it.
The global SI still owns the program. They run the office surveys, manage meeting room hardware, coordinate change management, and handle the platform-level work. The voice specialist (Ecosmob, NUWAVE, or one of the regional firms) sits in parallel, with a direct line to your team and a defined scope around the voice layer specifically.
Two workstreams round out the rollout. Program management and on-site deployment is handled by AVI-SPL, NTT, Insight, or CDW depending on your geographic footprint. Adoption and change management often goes to Avanade, Modality Systems, or the SI’s own adoption practice. These are real categories but they’re not the part of the project that breaks. The voice layer is.
What to look for in a voice specialist
A serious voice specialist walks into the first conversation with country-specific numbers ready: porting timelines by jurisdiction, SIP trunk pricing per minute or per channel by carrier, emergency calling certification status for the countries in scope. They name the SBC vendor they prefer and explain why. They show you a sample dashboard from a prior rollout with SIP transaction success rates and per-country MOS scores. They have an opinion on Operator Connect vs Direct Routing vs Calling Plans for each country in your footprint.
