Extend your carrier interconnect strategy.
Evaluate wholesale voice as part of a broader supplier and routing strategy.
Your switching estate
Commercial + technical boundary
Measured comparison
Add a supplier without losing operational control.
The operating model
A new wholesale relationship should fit the carrier process already used by your commercial and network teams. Maintain a comparable destination profile, a controlled test allocation and a clear reason for promoting or withdrawing traffic. Supplier diversity is useful only when the alternate path can be operated and evaluated.
Keep settlement and quality review connected. Agree how rate changes enter the routing process, how disputed records are identified and who is responsible for an urgent route change. Use destination-level evidence when discussing a performance issue; a network-wide average can hide the affected traffic.
Where VirPhone fits
Your team retains control of ingress policy and supplier selection. Scope VirPhone around the destinations, capacity and commercial terms you need to add or diversify.
Define the handoff
Your softswitch connects through a supplier trunk to the destination network. Keep rate ownership and acceptance within your existing carrier process.
- 01Your applications
- 02Your voice infrastructure
- 03VirPhone service
- 04PSTN connectivity
Plan around your operation
Bring destination mix, monthly minutes, a quality baseline and peak setup rate. Compare destination-level tests before promoting traffic.
Continue the technical review
Voice service
Explore the relevant connection.
Explore Voice serviceInterconnect
Review signaling and media.
Explore InterconnectOnboarding
Prepare a commercial and technical inquiry.
Explore OnboardingWhat to review with your team
| Review area | What to establish |
|---|---|
| Supplier evaluation | Prefix-level cost and quality comparison; versioned rates; test traffic allocation. |
| Operational acceptance | Escalation ownership; route-change process; CDR reconciliation. |
| Next step | Share the proposed architecture, traffic profile and required service boundary. |
Before the next step
What should our technical team prepare?
Prefix-level cost and quality comparison; versioned rates; test traffic allocation. Include known application dependencies and the people responsible for testing.
Traffic exchange without losing operational control
A carrier adding a supplier needs to decide where that supplier belongs in its routing policy. Begin with the destination groups, commercial objective and interconnect boundary. A new route may serve a primary allocation, a quality comparison or a defined contingency; those roles require different acceptance criteria.
For an initial exchange, keep a versioned rate deck alongside the test allocation. Compare like-for-like destination traffic and examine rejection patterns before increasing volume. Separate network failures from customer behavior so that a low answer ratio does not become an unsupported quality claim.
Commercial reconciliation
Match records across the handoff using agreed timestamps, timezone and identifiers. Sample answered calls, short-duration calls and failed attempts separately. Establish how deck changes and disputes are handled before the volume makes manual investigation expensive.
Start with compare termination requirements. Describe the service you operate, the part of the call path you want to change and the person responsible for technical acceptance. That gives the first discussion a concrete scope.
A practical question
How do we compare a new supplier fairly?
Hold the destination and traffic mix steady, retain the same measurement window and record the applicable deck. Compare call-level exceptions as well as the aggregate result.