Voice termination

Outbound calls, connected through one relationship.

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.

UK · US · Canada routes on every accountFixed or pooled caller IDPrepaid, per-minute
OUTBOUND · YOUR PLATFORM → DESTINATIONYour platformPBX or diallerOBSIDchecks · routingCarrier partnerselected routeDestination+1 8•• ••• ••••AnsweredCredit · channels · caller ID
Demonstration · masked numbers
01Capabilities

What happens to a call you send us.

Four things, in order: authorise the source, check the account and caller ID, choose a route, connect and bill.

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.

Caller ID you control

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.

Credit and channel checks

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.

Per-minute billing you can audit

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.

02How it works

From your dial plan to the far end.

1

Your system dials

Send the call to OBSID over your SIP endpoint, with the destination in international format.

2

OBSID checks

Source IP, wallet balance, channel limit and the caller ID to present — all in the moment the call arrives.

3

A route is selected

The call is handed to a carrier partner for the destination; the caller ID is stamped as configured.

4

Connected and logged

The far end rings and answers. Duration, result and cost appear in your activity and usage.

Caller ID

Present a number people can call back.

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.

Fixed CLIOne number presented on every call from an endpoint — your main business number, held with OBSID.
CLI poolA set of your numbers rotated across calls, with cooldowns and daily caps per number, and local presence where the pool covers the destination's area.
RegulationDestination countries increasingly verify caller ID. Presenting numbers you hold, in the format the destination expects, is what keeps calls connecting.
03Interconnection

What your engineer needs to know.

ConnectionThe same SIP endpoint used for inbound: your system sends INVITEs to the OBSID SBC from an allow-listed IP.
Dialling formatE.164 international format (e.g. +1 …, +44 …). National formats can be normalised for a default country on request.
Caller IDFixed number or CLI pool per endpoint. Numbers must be held with OBSID or registered as authorised.
ConcurrencyChannel limit per endpoint; attempts above it are declined with a busy response.
Credit controlBalance checked per call; new calls declined when the wallet is empty.
RecordsPer-call log with time, destination, presented CLI, duration and result; usage totals on the billing page.
04Who uses it

Termination in practice.

01

Contact-centre campaigns

A dialler sends campaign calls through OBSID and presents a number your customers can call back. Channel limits match your seat count.

  • CLI pools with rotation and daily caps
  • Recordings and dispositions in the optional portal
02

Outbound from a business PBX

Route your office system's external calls through OBSID and present your main number, with UK, US and Canadian destinations the common case.

  • One trunk for inbound and outbound
  • Usage on the same invoice as your numbers
03

Termination for service providers

Send your customers' outbound traffic over one interconnect and bill them yourself, using the per-call detail from OBSID.

  • Wholesale rates by volume — quoted
  • Endpoint per customer or shared
04

A platform placing calls

Your application originates calls over SIP; OBSID handles carrier selection and the caller-ID checks the destination expects.

  • Fixed or pooled CLI per endpoint
  • Call log for reconciliation
05Questions

Commercial and operational.

Routes to the United Kingdom, United States and Canada are the common case and are available on every account. Other destinations are opened on request as part of a quote, with rates by destination. Ask us for the list that matches your traffic.
Ready when you are

Tell us your destinations, we'll quote the routes.

Share your monthly minutes by country and how you present caller ID. We come back with rates and the setup for your endpoint.

Prepaid walletPer-call logCaller ID controls