Vobiz SIP trunking skill

Use this when the user is provisioning their own SIP infrastructure - connecting an on-prem PBX, a BYOC carrier, or restricting trunk access by IP.

Base URL: https://api.vobiz.ai/api/v1. Auth on every request: X-Auth-ID and X-Auth-Token headers. JSON bodies use Content-Type: application/json.

Resources

• Trunks - the parent SIP container. POST /Account/{auth_id}/trunks, GET, PUT, DELETE. Creating a trunk auto-generates a SIP domain {trunk_id}.sip.vobiz.ai.
• Credentials - username/password for SIP digest auth. POST /Account/{auth_id}/credentials, list at GET /Account/{auth_id}/trunks/credentials.
• IP ACL - IP/CIDR allowlist for inbound SIP traffic. POST /Account/{auth_id}/ip-acl, list at GET /Account/{auth_id}/trunks/ip-acl.
• Origination URIs - outbound SIP routing destinations with priority/weight failover. POST /Account/{auth_id}/origination-uris, list at GET /Account/{auth_id}/trunks/origination-uris.
• Number assignment - route a DID to a trunk. POST /Account/{auth_id}/numbers/{phone_number}/assign with body { "trunk_group_id": "<trunk_id>" }.

The four auth/routing layers

A trunk can combine four independent controls. Know which one the user needs before reaching for an endpoint: