SIP connectivity

Connect your phone system to your numbers.

Add your PBX, dialler or platform as a SIP endpoint, point numbers at it, and keep a backup destination ready for new calls when the primary is unavailable.

Source-IP authenticationUDP · TCP · TLSBackup destination per number
Incoming callto your OBSID numberfrom a carrierOBSIDsession border controllernumber → endpoint lookup01 · PRIMARYYour PBX / platformsip:pbx.example.comAuthorising…02 · BACKUPBackup destinationsip:backup.example.comStandbyEndpoint IP added to allow-listPrimary not answeringNext call attempt → backup
Demonstration · example hosts
01Capabilities

Routing you configure, not a ticket you raise.

Endpoints, routes, backups and limits are all yours to change in the dashboard, and take effect on the next call.

Endpoints you define

Add your PBX, dialler or platform as a SIP endpoint: host or IP, port and transport. Calls are authenticated by a source-IP allow-list you control.

Per-number routing

Point each number at the endpoint that should ring it. Move numbers between endpoints from the dashboard; changes apply to the next call.

Backup destination

Configure a second destination per number. When the primary is unavailable, new call attempts can be routed to the backup instead of failing.

Channel limits

Set how many concurrent calls a number or endpoint accepts. Attempts above the limit are declined cleanly rather than overloading your system.

02Architecture

Where your system sits.

Your endpoints talk to the OBSID session border controller. It looks up the number, applies your limits and caller-ID rules, and passes signalling to or from our carrier partners.

  1. Your side

    • PBX or diallerSIP · source-IP auth
    • Your platformSIP gateway
    • Browser agentsvia the call-centre portal

    ↕ Inbound and outbound SIP, authenticated by source IP

  2. OBSID

    • Session border controllersignalling · caller ID · limits
    • OBSID platformnumbers · routing · billing · logs

    ↕ Signalling, caller ID and limits; lookups and call records

  3. Carrier partners

    • Carrier Anumbers · termination
    • Carrier Btermination routes
    • Further partnersadded per market

    Interconnects per market

YOUR SIDEOBSIDCARRIER PARTNERSPBX or diallerSIP · source-IP authYour platformSIP gatewayBrowser agentsvia the call-centre portalSession bordercontrollersignalling · caller ID · limitsOBSID platformnumbers · routing · billing · logsCarrier Anumbers · terminationCarrier Btermination routesFurther partnersadded per marketlookups · CDRsinbound and outbound SIPinterconnects per market
03Setup

Connected in four steps.

1

Add an endpoint

Enter your host or IP, port and transport, and allow-list the public IPs your system sends from.

2

Create the trunk on your side

Follow the guide for your system to accept calls from OBSID and send calls to it.

3

Route numbers to it

Point each number at the endpoint, add a backup destination and set a channel limit.

4

Test and go live

Place an inbound and an outbound test call; both appear in your activity log with their result.

Technical details

What the connection looks like.

The details you and your PBX administrator need before creating the trunk. Anything not listed here can be confirmed with our team before you go live.

  • Signalling to and from our SBC
  • Your endpoint host must be reachable from the internet
  • Changes to routing apply to new calls immediately
ProtocolSIP, with signalling handled by the OBSID session border controller.
TransportUDP, TCP or TLS — chosen per endpoint.
AuthenticationSource-IP allow-list. Your system must send from, and be reachable at, a fixed public address.
Number formatNumbers are delivered in E.164 (international) format, e.g. +44 20 …Configure your inbound routes to match.
ConcurrencyChannel limit per number or endpoint; attempts above it receive a busy response.
Caller IDInbound: the caller's number as received from the carrier. Outbound: a number you hold, fixed or from a pool.
Backup destinationOptional second endpoint per number for new call attempts when the primary is unavailable.
LogsEvery routing decision and call appears in the dashboard activity log.
04Deployments

Systems that connect to OBSID.

01

An on-premise or hosted PBX

FreePBX, 3CX, Asterisk and similar systems connect by IP authentication: allow-list your public address, create the trunk, and point numbers at it.

  • Guides for FreePBX / Asterisk and 3CX
  • UDP, TCP or TLS transport
02

A contact-centre dialler

VICIdial and GoAutoDial receive inbound calls on your OBSID numbers and send outbound campaigns back through the same connection.

  • Inbound and outbound on one endpoint
  • Channel limits sized to your agents
03

Your own platform

If your product speaks SIP, it becomes an endpoint like any other. Numbers your users buy are routed to it; calls it makes leave through OBSID.

  • IP allow-list per environment
  • Call logs available in the dashboard
04

A second site as backup

Give numbers a backup destination at a second PBX or a different site, so new calls have somewhere to go while the primary is being restored.

  • Backup per number
  • Primary and backup can be different systems
05Questions

For the person configuring the trunk.

Source-IP allow-listing: you register the public IP addresses of your system, OBSID accepts calls from them and delivers calls to your configured host. If your system cannot present a fixed public IP, talk to us before you commit — we will confirm what is possible for your deployment.
Ready when you are

Connect your system this week.

Create an account and add your first endpoint, or send us your setup and we will confirm the details before you begin.

Source-IP authenticationBackup destination per numberChannel limits you control