Your service. A considered network layer.
Connect the origination and termination behind your retail VoIP product.
Your customer experience
Defined carrier handoff
Inbound / outbound voice
Keep the network boundary behind your customer experience.
The operating model
Your subscribers see a number, a dial tone and an application. Behind that experience, inbound number assignment, outbound calling and customer billing need to stay aligned. Define which system owns each stage of the lifecycle so adding customers does not create a manual reconciliation problem.
Use test accounts that represent the service you sell. Include forwarded calls, transfers, DTMF and number changes where applicable. Confirm how the receiving platform distinguishes customer environments and how your team will find the underlying call record when a subscriber reports a problem.
Where VirPhone fits
You own customer provisioning, support and packaging. Define the wholesale trunk boundary so customer-facing changes do not require a network redesign.
Define the handoff
Your platform and SBC connect to wholesale voice. Document how numbers map to tenants and where call records enter billing.
- 01Your applications
- 02Your voice infrastructure
- 03VirPhone service
- 04PSTN connectivity
Plan around your operation
Review provisioning, inbound formats and export needs. Test transfers, DTMF and representative customer flows before a wider rollout.
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 |
|---|---|
| Customer lifecycle | Number assignment; trunk mapping; service activation and release. |
| Support handoff | Customer reference; call timestamp; platform and carrier ownership. |
| Next step | Share the proposed architecture, traffic profile and required service boundary. |
Before the next step
What should our technical team prepare?
Number assignment; trunk mapping; service activation and release. Include known application dependencies and the people responsible for testing.
A carrier layer for the service your subscribers use
A VoIP provider owns the customer experience even when multiple networks carry the call. Keep the subscriber platform, numbering inventory and external routes clearly separated in the design. This makes it easier to identify whether a fault affects one extension, one trunk, one destination or the whole service.
Map inbound numbers to the correct subscriber before testing outbound identity. For a migration, use a small representative group that includes forwarding, voicemail and the customer’s normal calling destinations. Record what changes for the subscriber and what remains within the provider’s operating team.
Provisioning and support ownership
Define which system is the source of truth for number assignments. A number that exists in inventory but has no valid receiving route is not ready for a customer. Give support staff a consistent way to correlate the subscriber, number and call record without exposing account credentials.
Start with design inbound delivery. 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
Who owns subscriber features?
Your subscriber platform controls its application features. Establish where provisioning and carrier delivery begin so support can identify the responsible system.