Skip to main content
An Inbound (origination) trunk is the path Vobiz uses to deliver incoming PSTN calls to your SIP endpoint - typically a PBX, soft‑switch, or AI agent. Each trunk has its own Primary URI (the destination Vobiz forwards to), its own recording settings, and its own webhook.
URL

​
The Inbound Trunks list

Inbound Trunks page with a searchable list of trunks (qwertyu, piyush video sdk, vapi new kush, inbound, vobiz inbound) showing ID, Primary URI, Status Enabled, and a Trunk Details panel on the right with Trunk Name (qwertyu), Trunk ID UUID, Status toggle on, Call Recording on, AI Transcription on, PII Redaction off, Recording Webhook off, a Webhook section with POST URL, and a URI Configuration section showing Primary URI (qwerty.asfg.com)

Inbound Trunks - list, details, and toggles

Same three‑column layout as outbound trunks - search + create on top, list on the left, details on the right.

​
The trunk details panel

​
Recording & Transcription toggles

Identical to outbound trunks: Call Recording, AI Transcription, PII Redaction, Recording Webhook. Each obeys the same prerequisite chain - transcription needs recording, redaction needs transcription.

​
Webhook

A general‑purpose webhook URL Vobiz POSTs inbound‑call events to (incoming.ringing, incoming.answered, incoming.ended). Use it to track who’s calling, drive a live CRM update, or log to your data warehouse.

​
URI Configuration

Click the copy icon (⧉) next to the URI to copy it to your clipboard.

​
Linked Numbers

Below the URI Configuration card, the Linked Numbers (N) section lists every DID currently routing to this trunk. Click Link Numbers in the top‑right of the section to attach more numbers or detach existing ones.

​
Create an Inbound Trunk

Click + Create New Trunk to open the side panel.
Create Inbound Trunk side panel with Trunk Name required field, Recording and Transcription section with toggles for Call Recording, Recording Webhook, AI Transcription, and PII Redaction (each with Enable recording first or Enable transcription first prerequisite hints), Primary URI (optional) dropdown with Select Primary URI and an Add New URI link, and a Webhook Configuration Optional section with POST method dropdown and URL placeholder https://your-domain.com/webhook/calls plus the hint Receive real-time call events via HTTP to this endpoint

Create Inbound Trunk form

Click Create Trunk.

​
Linking numbers

After the trunk exists:
  1. Open the trunk details.
  2. Scroll to Linked Numbers and click Link Numbers.
  3. Pick existing numbers from your account or buy new ones inline - same flow as the Voice Applications attach‑number modal.
From the moment a number is linked, every call to that number forwards to the trunk’s Primary URI.

​
Tips

  • Use Origination URIs as named destinations. Even if you only have one PBX, give the URI a name like primary-pbx-mumbai - it’s clearer than a raw 1.2.3.4:5060.
  • Webhook before recording. If you only want call state for analytics, the webhook is enough - no need to enable recording.
  • Status toggle for maintenance windows. Disable the trunk to fail‑fast on inbound (carrier returns “all circuits busy”) instead of timing out on a dead PBX.

​
What’s next

Origination URI

Add or edit the SIP destinations Vobiz forwards to.

Phone Numbers

Buy or port the DIDs that ring this trunk.