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.
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.
Endpoints, routes, backups and limits are all yours to change in the dashboard, and take effect on the next call.
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.
Point each number at the endpoint that should ring it. Move numbers between endpoints from the dashboard; changes apply to the next call.
Configure a second destination per number. When the primary is unavailable, new call attempts can be routed to the backup instead of failing.
Set how many concurrent calls a number or endpoint accepts. Attempts above the limit are declined cleanly rather than overloading your system.
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.
Your side
↕ Inbound and outbound SIP, authenticated by source IP
OBSID
↕ Signalling, caller ID and limits; lookups and call records
Carrier partners
Interconnects per market
Enter your host or IP, port and transport, and allow-list the public IPs your system sends from.
Follow the guide for your system to accept calls from OBSID and send calls to it.
Point each number at the endpoint, add a backup destination and set a channel limit.
Place an inbound and an outbound test call; both appear in your activity log with their result.
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.
| Protocol | SIP, with signalling handled by the OBSID session border controller. |
|---|---|
| Transport | UDP, TCP or TLS — chosen per endpoint. |
| Authentication | Source-IP allow-list. Your system must send from, and be reachable at, a fixed public address. |
| Number format | Numbers are delivered in E.164 (international) format, e.g. +44 20 …Configure your inbound routes to match. |
| Concurrency | Channel limit per number or endpoint; attempts above it receive a busy response. |
| Caller ID | Inbound: the caller's number as received from the carrier. Outbound: a number you hold, fixed or from a pool. |
| Backup destination | Optional second endpoint per number for new call attempts when the primary is unavailable. |
| Logs | Every routing decision and call appears in the dashboard activity log. |
FreePBX, 3CX, Asterisk and similar systems connect by IP authentication: allow-list your public address, create the trunk, and point numbers at it.
VICIdial and GoAutoDial receive inbound calls on your OBSID numbers and send outbound campaigns back through the same connection.
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.
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.
Create an account and add your first endpoint, or send us your setup and we will confirm the details before you begin.