Numbers for your customers
Buy from one inventory and route each number to the relevant customer's PBX or platform. Release and re-route as customers change.
Global numbersHold numbers in one account, route each customer's numbers to that customer's system, send their outbound traffic through one interconnect and bill them yourself from OBSID's per-call detail.
A service provider needs to provision numbers and trunks for many end customers quickly, keep each customer's traffic separate, and reconcile costs against what it charges — without maintaining a dozen carrier relationships.
Buy from one inventory and route each number to the relevant customer's PBX or platform. Release and re-route as customers change.
Global numbersEach customer system is its own SIP endpoint with its own allow-listed IPs, channel limit and caller-ID policy.
SIP connectivityOutbound routes quoted for your traffic mix; per-call logs show the destination, duration and presented CLI you need for your own invoices.
Voice terminationAll customers' numbers and minutes are charged to your prepaid wallet with itemised usage.
Billing on the platformAn IT services company providing phone numbers and trunks to twenty small-business clients on hosted 3CX instances — each instance registered as its own endpoint (see the comparison below). The deployment-specific details:
| Scale | Twenty endpoints, one per hosted 3CX instance, each with its own public IP and a channel limit sized to that client. |
|---|---|
| Verification | UK geographic numbers per client; documents collected once per client and uploaded against that client's order. |
| Provider billing | The provider's wallet carries every charge; call logs filtered by endpoint feed the provider's own client invoices. |
Separation is done at the endpoint. Everything that matters per customer — routing, limits, caller ID and the call log — is attached to that customer's endpoint.
| Per customer endpoint | Shared across your account | |
|---|---|---|
| Connectivity | Their PBX host and allow-listed IPs | The OBSID SIP hosts and signalling IPs |
| Numbers | Routed to that endpoint only; re-routed when the customer changes | Bought from one inventory |
| Capacity | Channel limit sized to that customer | — |
| Caller ID | Fixed number or pool for that customer | — |
| Records | Call log filtered by endpoint for their invoice | One wallet, one OBSID invoice, itemised usage |
Your company details on the OBSID account; the dashboard and wallet are yours.
For each client, a SIP system with a fixed public IP to register as its own endpoint.
A way to collect the documents a client's numbers require in regulated countries.
Your own invoicing to clients, built from the per-call detail OBSID provides.
Tell us how many endpoints and which countries. We set up the account and confirm pricing for your mix.