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
- In the dashboard, add your system as a SIP endpoint: public host or IP, port, transport, and the source IPs to allow-list.
- Search the inventory, reserve a number, then buy it. Upload any documents the country requires against the order.
- Point the number at your endpoint, add a backup destination if you have one, and set a channel limit.
- Create the matching inbound route in your PBX for the number in +E.164 format.
- Place an inbound test call from a mobile and an outbound test call through the trunk.
Configuration values
| Endpoint host | Your PBX's public host or IP and SIP port (5060 unless you changed it). |
|---|---|
| Transport | UDP, TCP or TLS — match what your PBX trunk uses. |
| Allow-listed IPs | The public IPs your system sends SIP from. |
| Channel limit | Concurrent 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.