SIP TRUNKING

    SIP trunking in India for AI voice agents

    Vobiz is a SIP trunk provider in India for AI voice agents, PBXs and contact centers. Bring your own carrier, use ours, or run both. INR billing, KYC built into signup, and 140 and 1600-series numbers on Indian carriers, all configured by API.

    Works with Vapi, Retell AI, Bolna, LiveKit, ElevenLabs, OpenAI Realtime and 3CX.

    Talk to an engineer
    cURLBASH
    1# Create a trunk: returns trunk_id and its SIP domain2curl -X POST https://api.vobiz.ai/api/v1/Account/$AUTH_ID/trunks \3  -H "X-Auth-ID: $AUTH_ID" -H "X-Auth-Token: $AUTH_TOKEN" \4  -H "Content-Type: application/json" \5  -d '{"name":"voice-agent-prod","trunk_type":"OUTBOUND","max_concurrent_calls":50}'
    POST /trunks201 Created
    {  "trunk_id": "aabbccdd-1234-…",  "trunk_domain": "aabbccdd-1234-….sip.vobiz.ai"}

    10min

    to first call

    Sub-80ms

    one-way latency

    43

    fields on every call record

    15M+

    calls a day

    How it works

    From signup to a live SIP trunk
    in India in five steps

    No ticket, no provisioning window. Everything below is available in the console or over the REST API.

    Signup12345Live SIP trunk
    01Complete KYCConsole
    PANVerified
    GSTVerified
    CINVerified
    Aadhaarvia DigiLockerVerified
    02Create a trunkPOST /trunksBASH
    1# Create a trunk: returns trunk_id and its SIP domain2curl -X POST https://api.vobiz.ai/api/v1/Account/$AUTH_ID/trunks \3  -H "X-Auth-ID: $AUTH_ID" -H "X-Auth-Token: $AUTH_TOKEN" \4  -H "Content-Type: application/json" \5  -d '{"name":"voice-agent-prod","trunk_type":"OUTBOUND","max_concurrent_calls":50}'
    Response 201 Created{  "trunk_id": "aabbccdd-1234-…",  "trunk_domain": "aabbccdd-1234-….sip.vobiz.ai",  "trunk_status": "active",  "concurrent_calls_limit": 50}
    Full SIP trunking quickstart

    Built for voice AI

    Low-latency SIP trunking for real-time voice AI

    A conversational turn has roughly 500ms end to end before a pause feels unnatural, and it has to cover speech-to-text, the model, text-to-speech and the network.
    On Vobiz, media crosses exactly one internal relay, in India for calls in India.

    Shown at 1/8 speed
    Carrier / BYOCPSTN · SIPMedia Engine1 HOPYour agentSTT · LLM · TTS
    Conversational turn500ms
    NetworkSpeech-to-text · model · text-to-speechNetworkPause feels unnatural
    0100200300400500 ms
    One-way latency
    Sub-80ms
    Speech onset
    50ms
    PESQ MOS
    4.2+
    Signal-to-noise
    38.4dB
    Vobiz internal measurements.How the single-hop architecture works

    Your carrier, ours, or both

    Keep your Airtel, Jio or Tata trunk, or use ours

    Vobiz works as your only route, a second route, or the layer your existing carrier plugs into.

    Use the Vobiz network

    Indian numbers, termination and routing across multiple Indian carriers from one account. The fastest path from signup to a live call.

    Bring your own carrier (BYOC)

    Keep your existing PRI or SIP trunk contract and rates.

    See a BYOC setup

    Run both side by side

    Start Vobiz as a second route. Shift traffic gradually with priority and weight, and keep your existing route as fallback while you compare.

    On-prem interconnect

    Connect Vobiz directly to the PBX, SBC or contact center you run on your own premises.

    Routing and failover

    Configurable SIP trunk failover

    On the Vobiz network, calls fall back across multiple carriers automatically, per leg, while the call is being set up.

    voice-agent-prodOrigination URIs
    Origination URIPriorityShare of calls
    URI A1If priority 1 fails
    URI B2

    Higher priority URI is tried first; if it fails, the next one takes the call. URIs at the same priority split traffic by weight, so a URI at 20 carries twice the calls of one at 10.

    Security and access control

    Control exactly who can call through each SIP trunk

    Sub-accounts and the partner API

    Digest credentials

    — username and password auth for AI agents, softphones and anything behind NAT. Passwords are write-only and never returned by the API.

    Digest
    username••••••••
    passwordwrite-only

    IP and CIDR allowlists

    — accept traffic only from your SBC, PBX or carrier ranges.

    SBC
    PBX
    carrier ranges

    Both at once

    — require an allowlisted IP and valid credentials for defense in depth.

    allowlisted IP
    valid credentials

    Tenant isolation with per-customer KYC

    — Ask each end customer to complete their own KYC, so platforms serving many businesses stay compliant per customer.

    Integrations

    A SIP trunk for Vapi, Retell AI, Bolna and every platform you run

    Connect over standard SIP. Nothing on the platform side changes. Keep the orchestration you chose and bring the carrier underneath it.

    See all integrations
    PlatformHow it connectsSetup guide
    VapiSIP trunk, inbound and outbound/integrations/vapi/↗
    Retell AISIP trunk, inbound and outbound/integrations/retell-ai/↗
    LiveKitSIP trunk, inbound and outbound/integrations/↗
    ElevenLabsAgentsSIP trunk, inbound and outbound/integrations/↗
    OpenAIRealtimeSIP trunk/integrations/↗
    3CXand other PBXsStandard SIP trunk/integrations/↗
    Pipecat·DograhDograh·custom pipelinesWebSocket audio streams, not SIPAudio Streams docs↗

    India compliance

    SIP trunking in India, with DoT and TRAI compliance handled

    Business VoIP in India runs on licensing, KYC and registered calling. Vobiz builds each into the account, so you don't run them separately.

    DoT and TRAI compliance

    KYC per account and per sub-account

    — verification runs in the console at signup, and again for each end customer where you need it.

    140

    140 series for promotional calls

    — DLT-registered, with NDNC scrubbing and calling limited to 9 AM–9 PM.

    1600

    1600 series for service calls

    — the TRAI-designated series for service and transactional calls from regulated entities such as banks, NBFCs and insurers.

    Observability

    Know whether a bad call was the trunk, the carrier or the model

    Every call detail record carries 43 fields — MOS, jitter, packet loss, negotiated codec, which side hung up and why. Fetch by call_id, filter per sub-account, or export to CSV. Trunk webhooks report each call’s start and hangup, including billed seconds and MOS.

    Call detail records
    Trunk webhooks
    1. CallInitiated
    2. Negotiated codec
    3. MOSJitterPacket loss
    4. Which side hung upWhy they hung up
    5. Hangup"Billsec"3"MOS"4.5
    Call detail record43 fields
    GET/api/v1/Account/{auth_id}/cdr/{call_id}
    {  "data": {    "mos": 4.5,    "jitter": 0,    "packet_loss": 0,    "codec": "PCMU",    "hangup_source": "Caller",    "hangup_cause": "NORMAL_CLEARING",    …  }}
    ⚲ Fetch by call_id▽ Filter per sub-account↓ Export to CSV

    Related

    Get started

    Your first SIP trunk
    in 10 minutes

    Create a trunk, point your agent at it, place a call.
    No ticket, no sales call, no commitment.

    Book a demo

    FAQ

    SIP trunking questions