Business platforms

Give your product a voice your users can call.

Connect 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.

Your SIP gateway as the endpointNumbers routed to your productOutbound with configured caller ID
Your application · “Bookly” (example)

Today · example customers

09:30 · A. ExampleReminder sent · call back requested
10:15 · B. SampleConfirmed
Call area · demonstrationNo call in progressPress “Call customer” to see the states your app shows.Demo only — nothing is dialled.
SIP gateway · the component that talks SIP to OBSID
Host
sip.bookly.example
Public IP
203.0.113.9
Transport
TLS · 5061
OBSIDnumbers · calling · caller ID
Number service+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.
Calling serviceCaller ID is set per endpoint: a fixed number or a poolCredit and channel checks on every callOutbound calls present the number configured on the gateway’s endpoint — one fixed number, or a number from a pool of numbers you hold.
01The operational problem

Connect your application to the phone network.

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.

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 connectivity

Numbers for your users

Buy and route local or toll-free numbers as your users need them, with the country's verification handled on the order.

Global numbers

Outbound calling

Calls from your platform are routed to carrier partners, presenting a fixed number or a pool of your numbers per endpoint.

Voice termination

A log for reconciliation

Every call and routing decision is in the activity log, so usage can be matched to your own records.

Activity log
Illustrative deployment

Example: a scheduling platform.

Example 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.

02Responsibilities

What your application handles, and what OBSID handles.

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 gatewayOBSID
IdentityWhich tenant a called number belongs to; which user placed a callWhich endpoint a number rings; which caller ID the endpoint presents
NumbersRequesting a number per tenant in the dashboardInventory, verification and per-number routing to the gateway
CallsOriginating outbound INVITEs from an allow-listed IP; media handlingSource-IP authentication, credit and channel checks, carrier route selection
Caller IDDeciding which calls go through which endpointStamping the endpoint's configured caller ID — a fixed number, or a number from your pool — on each outbound call
RecordsYour own usage view for tenantsThe activity log and per-call detail you reconcile against
03Prerequisites

What you need in place.

1

SIP gateway

A SIP-capable component of your platform with a fixed public IP — OBSID connects to it, not to your web app directly.

2

Business account

Company details for the account; documents for any regulated numbers.

3

Tenant mapping

A way for your gateway to map each called number to the right customer.

4

Funded wallet

Number rental and minutes are charged to the prepaid balance.

04Questions

Asked by teams like yours.

Not as a public product today. Numbers and routing are managed in the dashboard; talk to us about your volume if you need programmatic provisioning.
Ready when you are

Describe your platform, we'll map the connection.

Send us how your product handles SIP today and the countries your users are in.

Prepaid walletPer-call logVerification per order