Outbound from your platform
Your PBX or dialler sends calls to OBSID over the same SIP connection it receives them on. OBSID selects a route with a carrier partner and connects the call.
Send calls from your PBX, dialler or platform to OBSID and let us select the carrier route. Present a number you hold, keep spend inside your prepaid wallet, and see every call in your log.
Four things, in order: authorise the source, check the account and caller ID, choose a route, connect and bill.
Your PBX or dialler sends calls to OBSID over the same SIP connection it receives them on. OBSID selects a route with a carrier partner and connects the call.
Present a fixed number you hold, or rotate through a pool of your numbers per endpoint. Presented numbers must be yours to use and must follow the destination country's rules.
Every call is checked against your wallet balance and the concurrent-call limit on the endpoint before it is routed, so spend and load stay where you set them.
Calls are rated per minute by destination and deducted from your prepaid wallet. Each call appears in your log with duration, result and the number presented.
Send the call to OBSID over your SIP endpoint, with the destination in international format.
Source IP, wallet balance, channel limit and the caller ID to present — all in the moment the call arrives.
The call is handed to a carrier partner for the destination; the caller ID is stamped as configured.
The far end rings and answers. Duration, result and cost appear in your activity and usage.
Caller ID is configured per endpoint, not per call, so your dial plan stays simple. OBSID stamps the configured number as the call leaves and records what was presented against each call.
Numbers you buy from OBSID are routed inbound as well, so a called party who rings back reaches your team rather than a dead line.
| Connection | The same SIP endpoint used for inbound: your system sends INVITEs to the OBSID SBC from an allow-listed IP. |
|---|---|
| Dialling format | E.164 international format (e.g. +1 …, +44 …). National formats can be normalised for a default country on request. |
| Caller ID | Fixed number or CLI pool per endpoint. Numbers must be held with OBSID or registered as authorised. |
| Concurrency | Channel limit per endpoint; attempts above it are declined with a busy response. |
| Credit control | Balance checked per call; new calls declined when the wallet is empty. |
| Records | Per-call log with time, destination, presented CLI, duration and result; usage totals on the billing page. |
A dialler sends campaign calls through OBSID and presents a number your customers can call back. Channel limits match your seat count.
Route your office system's external calls through OBSID and present your main number, with UK, US and Canadian destinations the common case.
Send your customers' outbound traffic over one interconnect and bill them yourself, using the per-call detail from OBSID.
Your application originates calls over SIP; OBSID handles carrier selection and the caller-ID checks the destination expects.
Share your monthly minutes by country and how you present caller ID. We come back with rates and the setup for your endpoint.