{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/voice-calling.sip-trunk-to-platform/",
    "json": "https://www.anchorterminal.com/niches/voice-calling.sip-trunk-to-platform/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/voice-calling.sip-trunk-to-platform/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/voice-calling.sip-trunk-to-platform/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 10 | 28 | 14 | 7 |\n\n## What counts as done\n\nDocs give a step-by-step trunk setup for the named platform pair, inbound calls reach the platform and are dispatched to the agent, outbound calls through the trunk carry two-way audio, the negotiated codecs are listed (including a wideband option), and DTMF passes as RFC 4733 events.\n\nMeasured, for our own tests: an inbound test call reaches the agent and both parties hear each other for 2 minutes, with audio quality on a blind listen equal to the platform's WebRTC path.\n\nHow agents ask for it: connect my Twilio number to LiveKit; set up a SIP trunk for my voice agent; route calls from my carrier into my own PBX or agent; use my existing numbers with this voice platform\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **46elks Voice API (46elks AB)**: The connect action takes a sip: URI, and ElevenLabs, Retell, OpenAI, Twilio, Vapi, LiveKit, Voximplant and jambonz trunks are allowed by default; others need support approval. No codec list or RFC 4733 statement in the pages read.\n- **Bandwidth Voice API + MCP (Bandwidth Inc.)**: Step-by-step guides for ElevenLabs, Vapi, Bland and OpenAI SIP cover inbound and outbound with TLS and digest credentials, but the ElevenLabs guide enables PCMU only, so no wideband codec, and RFC 4733 is not stated.\n- **didlogic Voice API (DID Logic PTE. LTD.)**: Step-by-step guides for ElevenLabs, LiveKit, Retell and Vapi; the FAQ lists PCMU, PCMA, GSM and G.729 and RFC 2833/4733 DTMF, but says G.722 availability is limited and often not passed end to end.\n- **DIDWW Voice and Number Management API (DIDWW Ireland Limited)**: Step-by-step guides for LiveKit, ElevenLabs, Retell, Vapi, OpenAI, Ultravox and others cover inbound and outbound trunks, but the LiveKit guide keeps only PCMA and PCMU (no wideband) and outbound needs approved Outbound Trunk access.\n- **jambonz (FirstFive8, Inc.)**: jambonz is the SIP platform: the interoperability spec lists UDP, TCP and TLS with PCMU, PCMA, G722 and Opus, and carrier and inbound routing guides exist. The DTMF mode (RFC 4733) is not stated in the pages read, and carrier guides are generic rather than per carrier.\n- **LiveKit Telephony (LiveKit Incorporated)**: Per-carrier trunk guides, UDP, TCP and TLS, RFC 2833/4733 DTMF and G722 or AMR-WB wideband are documented. Open interop issues: tel: URIs match no trunk (acc-24, sip 960) and IPv6 calls drop (sip 988); acc-21 found SIP audio grainier than WebRTC.\n- **Plivo Voice API (Plivo Inc.)**: Step-by-step SIP trunk guides for LiveKit, ElevenLabs, Retell and Vapi, plus India media anchoring; acc-19 followed the Plivo-LiveKit guide and the call rang with no agent dispatched. Codec list not read.\n- **SignalWire Voice API (SignalWire, Inc.)**: connect has PCMU, PCMA, Opus, G722, G729 and AMR-WB to SIP destinations with custom headers, but no named-platform trunk guide (LiveKit, Vapi and the like) or RFC 4733 statement was found in the pages read.\n- **Telnyx Voice API + MCP (Telnyx LLC)**: acc-38 runs Telnyx SIP into LiveKit Cloud, but acc-21 found the same pairing grainy against WebRTC on every TTS provider; trunk codec and DTMF pages were not read.\n- **Twilio Programmable Voice API + MCP (Twilio Inc.)**: Elastic SIP Trunking is a common LiveKit pairing, but accounts show the path failing: acc-20 heard silence after the greeting, acc-22 lost parts of words outbound, and acc-23 measured added latency. Trunk codec pages were not read.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **Exotel Voice API + MCP (Exotel Techcom Private Limited)**: SIP trunking pages are in the docs menu but were not read; no codec or DTMF evidence gathered.\n- **Infobip Calls API + MCP (Infobip Ltd)**: SIP trunking is listed as a Calls API feature, but no trunk setup guide for a named voice platform, codec list or DTMF mode was found in the pages read.\n- **Sinch Voice API + MCP (Sinch AB (publ))**: SIP trunking and an ElevenLabs SIP tutorial are indexed, but codec lists and DTMF mode were not read.\n- **Vonage Voice API + MCP (Vonage Holdings Corp.)**: SIP connect endpoints exist in the NCCO reference, but no trunk guide for a named voice platform, codec list or DTMF mode was read.\n- **Voximplant (Voximplant, Inc.)**: A SIP and SIP trunking page is indexed but codecs and DTMF mode were not read.\n\n## What stops agents finishing\n\n- carrier sends headers the platform does not parse, so the call matches no trunk (acc-24)\n- inbound trunk set up but no dispatch rule, so the call rings out (acc-19)\n- outbound trunks need an approved business application with a VAT or tax id (DIDWW)\n- LiveKit Phone Numbers are US and inbound only\n\n## Around it\n\nBefore: voice-calling.get-number-in-country. After: voice-agents.inbound-receptionist, voice-agents.outbound-campaign.\n\n## Where this comes from\n\nWeight 14 of 100 in Phone calling \u0026 voice transport: 7 of 49 accounts: LiveKit inbound trunks from Plivo, Twilio and Telnyx that ring with nothing answering, go silent after the greeting or sound grainy, a carrier tel: URI that matches no trunk, a Telnyx SIP plus LiveKit personal setup, and RFC 4733 DTMF over Twilio SIP\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/voice-calling.sip-trunk-to-platform.json, or the MCP tool get_use_case with id voice-calling.sip-trunk-to-platform. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Bring carrier numbers into a voice platform over a SIP trunk",
        "url": ""
      }
    ],
    "description": "Bring carrier numbers into a voice platform over a SIP trunk: 0 companies fully do it, 10 with a limit, 28 carry the tag. Every listing in Phone calling \u0026 voice transport with the reason and a source.",
    "facts": null,
    "h1": "Bring carrier numbers into a voice platform over a SIP trunk",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/voice-calling.sip-trunk-to-platform/",
    "published": "",
    "section": "agents",
    "title": "Bring carrier numbers into a voice platform over a SIP trunk | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/voice-calling.sip-trunk-to-platform/"
  },
  "tokens": {
    "markdown": 1600,
    "slim": 380
  },
  "version": 1
}
