Connect the PSTN beneath your platform.
Carrier connectivity for providers operating hosted communications services.
Users, features & identity
Separate operational ownership
Market-specific requirements
A PSTN layer designed around your platform boundary.
The operating model
A multi-tenant UCaaS platform manages users, features and customer policies. Carrier connectivity carries the inbound and outbound traffic at the SBC boundary. Keep those layers separate in the design so a seat change, tenant migration or application upgrade has an understood effect on voice delivery.
Model both tenant demand and aggregate bursts. A large set of individually modest customers can produce a busy-hour setup peak. Validate caller identity and number mapping across representative tenants. Confirm which provisioning and reporting operations are available before committing to an automation design.
Where VirPhone fits
This is for UCaaS operators needing a PSTN layer beneath their platform. Teams buying a phone system should use Business Communications.
Define the handoff
Your multi-tenant platform handles seats and features. The SBC boundary carries inbound and outbound voice to the carrier network.
- 01Your applications
- 02Your voice infrastructure
- 03VirPhone service
- 04PSTN connectivity
Plan around your operation
Define number assignment, tenant isolation, busy-hour demand and aggregate CPS. Confirm available operations before designing automation.
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 OnboardingExplore hosted business calling
Hosted PBX plans, devices and team features are in Business Communications.
Business CommunicationsWhat to review with your team
| Review area | What to establish |
|---|---|
| Tenant design | Number ownership; caller identity; routing assignment and isolation. |
| Platform acceptance | Transfers; forwarding; media; peak aggregate call setup. |
| Next step | Share the proposed architecture, traffic profile and required service boundary. |
Before the next step
What should our technical team prepare?
Number ownership; caller identity; routing assignment and isolation. Include known application dependencies and the people responsible for testing.
Keep platform features and carrier delivery aligned
UCaaS customers see an application; operations teams see several dependencies. Authentication, endpoint registration, application call control and PSTN connectivity should have separate owners and observable boundaries. A carrier handoff can be healthy while an application routing rule still sends the call to the wrong destination.
Test the features your subscribers actually use: transfer, forwarding, simultaneous ringing and voicemail. Confirm how those flows affect caller identity and duration records. Use separate tests for inbound number delivery and outbound termination rather than treating one successful call as a complete acceptance.
Expand by market, not by assumption
For each market, confirm the required number types, service capabilities, provisioning prerequisites and support process. A voice number does not establish messaging capability. Keep customer launch dates dependent on confirmed availability and successful application testing.
Start with plan a numbering footprint. 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
What should we test beyond a basic call?
Use the application’s forwarding, transfer, voicemail and simultaneous-ringing scenarios. Check identity and records for those flows, not only direct calls.