Skip to content

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

Click Create Trunk in the dashboard and fill in these fields:

FieldRequiredDescription
NameyesInternal label shown in the dashboard. Example: Production Trunk.
Domain NameyesUnique subdomain assigned to the trunk. All outbound calls route to this domain (a.k.a. the Termination URL). Alphanumeric and hyphens only.
Call Status URLnoHTTPS endpoint that receives webhook events.
SecretnoSigning secret used for HMAC signatures on webhooks. Rotatable without downtime.
Channel LimitnoMaximum concurrent calls. Defaults to null; purchase more as needed. If channel_limit is null, the account-level channel limit applies instead.
RecordingnoWhen enabled, all call audio is recorded and delivered via recording events.
Transport TypeyesControls transport encryption. See below.
Webhook API versionnoPin the webhook payload shape to 2025-08-01 or 2026-06-01. See API versioning.

Controls the protocol used for SIP signaling and media:

TransportPortSignalingMedia
TLS/SRTP5061SIP over TLS (encrypted)SRTP (encrypted)
TCP5060SIP over TCP (unencrypted)RTP (unencrypted)
UDP5060SIP over UDP (unencrypted)RTP (unencrypted)

TLS + SRTP is recommended for any trunk carrying customer PII.

Every trunk authenticates outbound calls one of two ways:

MethodUse whenHow it’s configured
IPCalls 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.
CredentialYour 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 tells Teler where to deliver calls that arrive on the trunk. Configure a route with:

FieldRequiredDescription
NameyesInternal label for the route.
SIP URLyesThe 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 UsernoSIP 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>