# Platform guides

What to enter at ElevenLabs, LiveKit, Vapi, Retell, Ultravox, OpenAI and other SIP targets so calls to your number reach your agent.

> Early access: the dashboard, CLI, MCP server and REST API are available. We are happy to help you set them up for your voice stack.

Source: https://trunkbeam.com/en/docs/platforms

In TrunkBeam you only set **where calls should go** for each number: the address at your provider (SIP URI). Everything else is configured at the provider. This page shows where to find what on the common platforms.

The ElevenLabs guide is tested in production. The others follow the providers' documentation (as of September 2026). Field names there may change.

## How it works

| Direction | What happens | Where you set it |
|---|---|---|
| Inbound | TrunkBeam delivers calls to your number to the provider's SIP URI. | Dashboard → Rufnummern → number → **Verbindung** |
| Outbound and transfers | Your agent calls out or transfers through TrunkBeam. The provider signs in with your SIP access. | Dashboard → Konto → **SIP-Zugang** |

Outbound settings are the same for every provider:

| Field | Value |
|---|---|
| Server / Address | `sip.trunkbeam.com` |
| Port | `5061` |
| Transport | TLS |
| Username / Password | from Konto → SIP-Zugang (the password is shown only when generated) |

### The SIP target on a number

- **Address at the provider**: number or identifier, server and transport (TLS, TCP or UDP). You do not need to enter a port: 5061 applies for TLS, otherwise 5060. Only for a non-standard port, append it to the server, for example `pbx.example.com:5080`. If you have a complete SIP URI such as `sip:+4930123456@sip.provider.example;transport=tls`, paste it into one of the upper fields; the dashboard splits it across the fields. The SIP URIs further down are meant the same way.
- **Encrypt audio (SRTP)**: on by default. The provider must allow encrypted audio, otherwise calls fail. The call log then shows "encryption mismatch (SIP 488)".
- **Username and password**: only turn this on if the provider requires credentials for inbound calls. Most providers recognise TrunkBeam by its IP address, which the dashboard shows next to the SIP target.

After saving, call the number. If the agent does not answer, the reason is listed under **Anrufe** (calls) in the dashboard.

### Headers TrunkBeam sends

| SIP header | Content |
|---|---|
| `X-TrunkBeam-Called` | the TrunkBeam number that was called |
| `X-TrunkBeam-Transfer` | only when a call returns after a transfer: the reason (`no-answer`, `busy`, `unavailable`, `not-allowed`, `limit`) |
| `X-TrunkBeam-Transfer-Target` | only on return: the number that did not answer |

The agent transfers with **SIP REFER** to `tel:+49…` or `sip:+49…@sip.trunkbeam.com`. See [Blind transfer, availability check and hold music](/en/docs/transfer).

## ElevenLabs Agents

**SIP URI in TrunkBeam:** `sip:+49…@sip.rtc.elevenlabs.io;transport=tls` with your TrunkBeam number. Encrypt audio on, username and password as in ElevenLabs.

1. **Import the number**: ElevenLabs → Agents → Phone Numbers → Import number → From SIP trunk.
   - Label: `TrunkBeam`
   - Phone Number: your TrunkBeam number with +, exactly as in the SIP URI
2. **Inbound Configuration**
   - Media Encryption: **Allowed** or **Required**. With "Disabled", calls do not get through.
   - Authentication: **on**. Choose a username and password and enter the same values on the SIP target in TrunkBeam. Without authentication, ElevenLabs accepts calls from anyone.
   - Leave all other switches off. An IP allowlist (Allowed Addresses) and Remote Domains are not needed. If you want to set Remote Domains anyway: `sip.trunkbeam.com`.
3. **Outbound Configuration** for outbound calls and transfers
   - Address: `sip.trunkbeam.com`
   - Transport Type: TLS
   - Media Encryption: Required
   - Username / Password: from Konto → SIP-Zugang
4. **Assign the agent** to the imported number and call it.

**Transfers:** system tool "Transfer to number" with transfer type **SIP REFER**. Without REFER ("Conference"), ElevenLabs places a second call through TrunkBeam.

- The called number is available to the agent as `{{sip_trunkbeam_called}}`.
- When TrunkBeam calls the agent back after an unsuccessful transfer, the reason and number are in `{{sip_trunkbeam_transfer}}` and `{{sip_trunkbeam_transfer_target}}`. Handle them in the prompt, for example by taking a message, instead of greeting the caller again.
- ElevenLabs waits only about 10 to 15 seconds for a transfer result. With an availability check, the target therefore rings for at most 12 seconds.

ElevenLabs documentation: [SIP trunking](https://elevenlabs.io/docs/eleven-agents/phone-numbers/sip-trunking), [Transfer to number](https://elevenlabs.io/docs/agents-platform/customization/tools/system-tools/transfer-to-number)

## LiveKit Cloud

**SIP URI in TrunkBeam:** `sip:+49…@<subdomain>.eu.sip.livekit.cloud;transport=tls`. The address is under Settings → Project. Turn on username and password, with the same values as in the inbound trunk.

1. **Inbound trunk**: LiveKit Cloud → Telephony → SIP trunks → Create inbound trunk, or with the CLI:

   ```bash
   lk sip inbound create --name trunkbeam --numbers "+49…" \
     --auth-user "<username>" --auth-pass "<password>"
   ```

   Set `include_headers: SIP_X_HEADERS` to receive the TrunkBeam headers as attributes `sip.h.x-trunkbeam-called` and `sip.h.x-trunkbeam-transfer`.
2. **Dispatch rule**: Telephony → Dispatch rules, route calls on this trunk to your agent.
3. **Outbound trunk** for outbound calls and transfers:

   ```bash
   lk sip outbound create --name trunkbeam --address sip.trunkbeam.com --transport tls \
     --numbers "+49…" --auth-user "<SIP access username>" --auth-pass "<SIP access password>"
   ```

**Transfers:** `TransferSIPParticipant` sends a SIP REFER, with `transfer_to` as `tel:+49…` or `sip:…`.

LiveKit Cloud offers IP allowlisting only through support. Username and password are enough.

LiveKit documentation: [SIP trunk setup](https://docs.livekit.io/telephony/start/sip-trunk-setup/), [SIP API](https://docs.livekit.io/reference/telephony/sip-api/), [Transfer](https://docs.livekit.io/sip/transfer-cold/)

## Self-hosted LiveKit

Same as LiveKit Cloud, with the [livekit/sip](https://github.com/livekit/sip) service on your own server.

- **SIP URI in TrunkBeam:** `sip:+49…@sip.your-domain.example;transport=tls`. The certificate must match the host name.
- Configure the public IP and TLS in the SIP service. In the firewall, open SIP (5060/5061) and the RTP ports (default 10000–20000) for the TrunkBeam IP.
- Inbound trunk with username and password or with an IP allowlist (`--allowed-addresses <IP>/32`). With an IP allowlist, leave credentials off in TrunkBeam.
- Outbound trunk as for LiveKit Cloud.

## Vapi

**SIP URI in TrunkBeam:** `sip:+49…@<credentialId>.sip.eu.vapi.ai` for EU accounts, otherwise `<credentialId>.sip.vapi.ai`. No credentials, Vapi recognises TrunkBeam by its IP.

1. **Create a credential** via the API, EU accounts through `api.eu.vapi.ai`:

   ```json
   POST /credential
   {
     "provider": "byo-sip-trunk",
     "name": "TrunkBeam",
     "gateways": [{ "ip": "<TrunkBeam IP>", "port": 5061, "inboundEnabled": true,
                    "outboundEnabled": true, "outboundProtocol": "tls" }],
     "outboundAuthenticationPlan": { "authUsername": "<SIP access username>",
                                     "authPassword": "<SIP access password>" }
   }
   ```

2. **Create the phone number**:

   ```json
   POST /phone-number
   { "provider": "byo-phone-number", "number": "+49…", "credentialId": "<credentialId>",
     "numberE164CheckEnabled": true }
   ```

**Transfers:** tool `transferCall` with `destination { "type": "sip", "sipUri": "sip:+49…@sip.trunkbeam.com" }`. Vapi uses REFER by default.

Vapi documentation: [SIP trunk](https://docs.vapi.ai/advanced/sip/sip-trunk), [Networking](https://docs.vapi.ai/advanced/sip/sip-networking)

## Retell AI

**SIP URI in TrunkBeam:** `sip:+49…@sip.retellai.com;transport=tcp`. No credentials.

In Retell under Phone Numbers → Connect via SIP trunking:

| Field | Value |
|---|---|
| Phone Number | your TrunkBeam number in E.164 format |
| Termination URI | `sip.trunkbeam.com` |
| Transport | TLS |
| SIP Trunk User Name / Password | from Konto → SIP-Zugang |
| Inbound Agent | the agent you want |

To change these values later, delete the number in Retell and import it again.

**Transfers:** by default Retell transfers with a new call and stays on the line. With the "SIP REFER" option, Retell hands the call to TrunkBeam.

Retell documentation: [Custom telephony](https://docs.retellai.com/deploy/custom-telephony), [Transfer](https://docs.retellai.com/build/single-multi-prompt/transfer-call)

## Ultravox

**SIP URI in TrunkBeam:** `sip:agent_<agentId>@<your account's SIP domain>`. `GET /api/sip` returns the domain. No credentials.

1. **Allow TrunkBeam**: `PATCH /api/sip` with `{ "allowedCidrRanges": ["<TrunkBeam IP>/32"] }`.
2. **Outbound**: create a call with `medium` `sip.outgoing`:

   ```json
   { "sip": { "outgoing": { "to": "sip:+49…@sip.trunkbeam.com;transport=tls", "from": "+49…",
     "username": "<SIP access username>", "password": "<SIP access password>" } } }
   ```

**Transfers:** the built-in `coldTransfer` sends a SIP REFER to `sip:+49…@sip.trunkbeam.com`.

Ultravox documentation: [SIP](https://docs.ultravox.ai/telephony/sip), [Transfers](https://docs.ultravox.ai/telephony/call-transfers)

## OpenAI Realtime

Inbound only. **SIP URI in TrunkBeam:** `sip:proj_…@sip.api.openai.com;transport=tls`, in the EU `sip-eu.api.openai.com`. Encrypt audio on, OpenAI requires it. No credentials.

1. OpenAI → project → Webhooks: send the `realtime.call.incoming` event to your backend.
2. Your backend accepts each call with `POST /v1/realtime/calls/{call_id}/accept`, including model, instructions and voice. The TrunkBeam SIP headers are in the webhook under `data.sip_headers`.

**Transfers:** `POST /v1/realtime/calls/{call_id}/refer` with `target_uri` `tel:+49…`.

OpenAI documentation: [Realtime SIP](https://developers.openai.com/api/docs/guides/realtime-sip)

## Deepgram Voice Agent

Deepgram has no SIP interface. Build the agent with LiveKit Agents and the Deepgram plugins and connect it like [LiveKit](#livekit-cloud). Alternatively use Pipecat with the Daily or LiveKit transport.

Deepgram documentation: [Deepgram with LiveKit](https://developers.deepgram.com/docs/livekit-integration)

## Other SIP targets

For your own PBX, Asterisk, FreeSWITCH, Synthflow or any other SIP server:

- **SIP URI** with the target's host, port and transport, for example `sip:reception@pbx.example.com:5061;transport=tls`.
- Allow calls from TrunkBeam: username and password (digest) or allowlist the TrunkBeam IP.
- Codecs: G.722 and G.711 (PCMA/PCMU).
- Outbound: server `sip.trunkbeam.com`, port 5061, TLS, with your SIP access.

**Pipecat** has no SIP endpoint of its own. Dial-in through Daily requires the carrier to hand the live call over via API to an address that Daily issues for each call; TrunkBeam delivers to one fixed address per number. Two routes work: run Pipecat with the LiveKit transport and connect the number as described for LiveKit above, or use your own Asterisk or FreeSWITCH as the SIP target and pass the audio on to Pipecat.

Not yet supported: targets that can only use an IP allowlist instead of a password for outbound calls, for example Daily dial-out, and targets that require Opus.
