SIP Trunking
A SIP Trunk connects Teler to your own SIP infrastructure (a PBX, SBC, softswitch, or an AI voice platform) over SIP. It defines how Teler authenticates and routes SIP calls to and from that infrastructure, in both directions: inbound origination and outbound termination.
Trunks are created and managed in the Teler dashboard, or programmatically using the SIP Trunk API, the Python SDK, or the Node SDK
Configure a trunk
Section titled “Configure a trunk”Click Create Trunk in the dashboard and fill in these fields:
| Field | Required | Description |
|---|---|---|
| Name | yes | Internal label shown in the dashboard. Example: Production Trunk. |
| Domain Name | yes | Unique subdomain assigned to the trunk. All outbound calls route to this domain (a.k.a. the Termination URL). Alphanumeric and hyphens only. |
| Call Status URL | no | HTTPS endpoint that receives webhook events. |
| Secret | no | Signing secret used for HMAC signatures on webhooks. Rotatable without downtime. |
| Channel Limit | no | Maximum concurrent calls. Defaults to null; purchase more as needed. If channel_limit is null, the account-level channel limit applies instead. |
| Recording | no | When enabled, all call audio is recorded and delivered via recording events. |
| Transport Type | yes | Controls transport encryption. See below. |
| Webhook API version | no | Pin the webhook payload shape to 2025-08-01 or 2026-06-01. See API versioning. |
Transport Type
Section titled “Transport Type”Controls the protocol used for SIP signaling and media:
| Transport | Port | Signaling | Media |
|---|---|---|---|
| TLS/SRTP | 5061 | SIP over TLS (encrypted) | SRTP (encrypted) |
| TCP | 5060 | SIP over TCP (unencrypted) | RTP (unencrypted) |
| UDP | 5060 | SIP over UDP (unencrypted) | RTP (unencrypted) |
TLS + SRTP is recommended for any trunk carrying customer PII.
Outbound authentication
Section titled “Outbound authentication”Every trunk authenticates outbound calls one of two ways:
| Method | Use when | How it’s configured |
|---|---|---|
| IP | Calls originate from fixed, static IP addresses. | Create an IP ACL (Access Control List) once, then assign it to multiple trunks. Calls from IPs in the ACL are accepted without credentials. |
| Credential | Your SIP system authenticates via username and password. | Set the username and password in the SIP trunk; your SIP client presents them on each INVITE. |
Inbound routing
Section titled “Inbound routing”Inbound routing tells Teler where to deliver calls that arrive on the trunk. Configure a route with:
| Field | Required | Description |
|---|---|---|
| Name | yes | Internal label for the route. |
| SIP URL | yes | The SIP URL where Teler should forward inbound calls (a.k.a. the Origination URL). Provided by your downstream platform (AI provider, PBX, SBC, or softswitch). Example: sip:sip.rtc.elevenlabs.io:5061. |
| SIP User | no | SIP username to present to the destination, if your downstream platform requires one. The complete inbound SIP URL will become sip:<sip_user>@<sip_url>:<port> |
Testing in sandbox mode
Section titled “Testing in sandbox mode”To test a trunk in sandbox mode, assign your sandbox reference number to it, and import that same reference number into your AI agent platform or SIP system. Each trunk also gets a 4-digit sandbox PIN when it’s created; callers enter it after dialing your sandbox virtual number to reach this trunk. See Testing calls.