Your gateway as an endpoint
Register your platform's SIP gateway — host and public IPs — once. Every number you buy can be routed to it; every call it originates is authenticated by source IP.
SIP connectivityConnect your application's SIP gateway to OBSID. Numbers your users need are routed to it; calls it places leave through OBSID with the caller ID you configure. You keep the customer relationship.
Today · example customers
sip.bookly.example203.0.113.9TLS · 5061+1 437 ••• •••• → sip.bookly.example+44 20 •••• •••• → sip.bookly.exampleNumbers per customer, all routed to the gateway; the gateway maps the called number to the tenant.A software platform that needs telephony wants numbers and calling without building carrier relationships, handling verification paperwork in every country, or exposing its users to a second vendor. The one thing it must bring is a SIP-capable component — a gateway or media server — that OBSID can reach.
Register your platform's SIP gateway — host and public IPs — once. Every number you buy can be routed to it; every call it originates is authenticated by source IP.
SIP connectivityBuy and route local or toll-free numbers as your users need them, with the country's verification handled on the order.
Global numbersCalls from your platform are routed to carrier partners, presenting a fixed number or a pool of your numbers per endpoint.
Voice terminationEvery call and routing decision is in the activity log, so usage can be matched to your own records.
Activity logExample values, not a customer case study.
A scheduling product gives each business customer a local number for appointment reminders and lets staff call customers back from the app. Its SIP gateway sits in one cloud region and is registered with OBSID as an endpoint: public IP allow-listed, TLS transport, channel limit set for that environment.
Inbound, each customer's number is bought in the dashboard and routed to the gateway; because every number is routed individually, the gateway reads the called number and hands the call to the right tenant. Outbound, calls leave through the same endpoint and present the caller ID configured on it — a fixed number or one from a pool of the product's numbers — and each call appears in the activity log, which the team exports for usage reconciliation.
OBSID connects to the SIP gateway, not to your web application. The gateway is the boundary: your product logic stays on your side of it.
| Your application and gateway | OBSID | |
|---|---|---|
| Identity | Which tenant a called number belongs to; which user placed a call | Which endpoint a number rings; which caller ID the endpoint presents |
| Numbers | Requesting a number per tenant in the dashboard | Inventory, verification and per-number routing to the gateway |
| Calls | Originating outbound INVITEs from an allow-listed IP; media handling | Source-IP authentication, credit and channel checks, carrier route selection |
| Caller ID | Deciding which calls go through which endpoint | Stamping the endpoint's configured caller ID — a fixed number, or a number from your pool — on each outbound call |
| Records | Your own usage view for tenants | The activity log and per-call detail you reconcile against |
A SIP-capable component of your platform with a fixed public IP — OBSID connects to it, not to your web app directly.
Company details for the account; documents for any regulated numbers.
A way for your gateway to map each called number to the right customer.
Number rental and minutes are charged to the prepaid balance.
Send us how your product handles SIP today and the countries your users are in.