Skip to main content
An Origination URI is a SIP destination address - host:port plus transport - that Vobiz forwards inbound PSTN calls to. Each inbound trunk picks one URI as its Primary, and you can keep multiple URIs on hand for primary/backup routing or per‑region delivery.
URL

​
The Origination URI list

Origination URI page with a search field, Add Origination URI button, a list of URIs (qwerty.asfg.com, ZJGB2STD4WCD.sip.videosdk.li, 2f51fa9d-c783-47ae-ab24-299..., 8ebd23dc-b86b-4fea-bc41-96..., asd.exmaple.sip.com) each showing No description, Transport UDP, and Status Active, and a URI Details panel on the right with URI (qwerty.asfg.com), URI ID, Description, Status Active, Transport UDP, Trunk, and Metadata Created and Last Updated timestamps

Origination URI - list and details

Click any card to load its details on the right.

​
Details panel

​
Create an Origination URI

Click + Add Origination URI to open the side panel.
Create Origination URI modal with URI required field (placeholder example.com:5060) and hint Examples example.com:5060 sip.example.com:5060 34.73.214.124:5060, Description field with placeholder Optional description and hint Primary origination URI backup route etc., Transport dropdown set to UDP, Active toggle on, and Cancel and orange Create URI buttons

Create Origination URI form

Click Create URI. Once the URI exists:
  1. Open an Inbound Trunk.
  2. Edit the trunk and pick this URI from the Primary URI dropdown.
  3. Save.
Vobiz immediately starts forwarding inbound calls on the trunk’s linked numbers to this URI.

​
Multiple URIs - primary / backup

A URI created here can be reused across many trunks, or you can keep several URIs on standby for fast failover:
  1. Primary URI stays linked to the production inbound trunk.
  2. Backup URI stays Active but unlinked.
  3. When the primary PBX goes down, switch the trunk’s Primary URI to the backup - propagation is instant.
For automatic failover at the carrier level, contact support@vobiz.ai - multi‑URI fallback is a per‑account configuration.

​
Tips

  • Always include the port. example.com:5060 is clearer than relying on a default - and several common firewalls reject SIP without an explicit port.
  • Use TLS for cloud PBXes. UDP over the open internet is fine for fixed‑IP deployments, but TLS prevents eavesdropping and SIP fingerprinting for cloud setups.
  • Name the URI well. The list grows fast; “Primary Mumbai PBX” beats 34.73.214.124:5060 when you’re staring at 28 entries.

​
What’s next

Inbound Trunks

Link this URI to a trunk and start receiving calls.

SIP Call Logs

Verify inbound traffic landed on the right URI.