Resources

Setup guides and answers.

How to buy your first number, connect a PBX to OBSID, and stay on the right side of caller-ID and verification rules. The exact hosts and IPs for your account are on your endpoint page in the dashboard.

Getting startedFreePBX / Asterisk3CXCaller ID and verification
01Setup guides

Connect your system.

Each guide lists prerequisites, numbered steps, the configuration values you will be asked for, the expected result and common fixes.

Link to this guide

Prerequisites

  • An OBSID account with company details completed
  • A funded wallet — setup and rental are charged from it
  • A PBX or platform reachable over SIP from the internet, with a fixed public IP

Steps

  1. In the dashboard, add your system as a SIP endpoint: public host or IP, port, transport, and the source IPs to allow-list.
  2. Search the inventory, reserve a number, then buy it. Upload any documents the country requires against the order.
  3. Point the number at your endpoint, add a backup destination if you have one, and set a channel limit.
  4. Create the matching inbound route in your PBX for the number in +E.164 format.
  5. Place an inbound test call from a mobile and an outbound test call through the trunk.

Configuration values

Endpoint hostYour PBX's public host or IP and SIP port (5060 unless you changed it).
TransportUDP, TCP or TLS — match what your PBX trunk uses.
Allow-listed IPsThe public IPs your system sends SIP from.
Channel limitConcurrent calls you want the number or endpoint to accept.

Expected result

Both test calls appear in the dashboard activity log with the endpoint used; the inbound call rings the destination you set in your PBX.

Troubleshooting

Inbound call is logged as “Endpoint did not answer”
Your PBX did not respond to OBSID. Check the firewall accepts SIP from the OBSID signalling IPs shown on your endpoint page, and that the inbound route matches the +E.164 number.
Outbound call is logged as rejected
The log shows the reason: an IP that is not allow-listed, an empty wallet, or a channel limit. Fix the item named in the log entry.

Using a system not listed here? Any SIP platform that can send from a fixed public IP can connect. Send us your setup

02Reference

Values every guide relies on.

SIP host and IPsShown on your endpoint page in the dashboard. Allow-list the signalling addresses in your firewall and trunk.
AuthenticationSource-IP allow-list. No registration credentials are used.
Number formatNumbers are delivered and should be dialled in international (+E.164) format.
TransportUDP, TCP or TLS, as configured on your endpoint.
Caller IDA number held with OBSID, or one registered with us as authorised — fixed or pooled, configured per endpoint.
Where to look when something failsThe activity log in the dashboard shows each routing decision and the reason for any rejection.
03FAQ

Common questions.

One place to run production voice: buy numbers, point them at your SIP endpoints with a backup destination, send outbound calls through our routing layer to carrier partners, and handle billing and verification — without stitching together several carrier portals.
Ready when you are

Stuck on a trunk?

Send us your PBX or dialler, the error you see and the time of the call. We check the routing log on our side and come back with the fix.

Routing log on every callGuides for common systemsReal people replying