Overview
A Teler-powered AI calling setup where your Retell AI agent answers inbound calls on your Teler virtual number and places outbound calls through your Teler SIP trunk.
Your Teler SIP trunk connects directly to Retell AI over SIP — calls flow between the two platforms without a bridge or media server to host.
Key Features
- Direct SIP connection — Calls go straight from your Teler trunk to Retell AI, with no bridge or media server to host.
- Full control over your configuration — Update your SIP settings directly in both dashboards anytime, without needing any intervention from the FreJun team.
- Same trunk, both directions — One Teler trunk handles inbound and outbound calls to the same Retell AI agent.
- Standard credential authentication — Reuse the same username and password across both the Teler trunk and Retell AI, no separate credential system to manage.
How to Integrate
Prerequisite: Creating a SIP Trunk in Teler
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 from the Teler dashboard under SIP Trunks.
The Create SIP Trunk wizard has three parts: basic trunk configuration, outbound authentication, and inbound routing.
Step 1: Basic trunk configuration
| Field | Required | Description |
|---|---|---|
| SIP trunk name | Yes | Internal label shown in the dashboard, e.g. “Production Trunk.” |
| Domain name | Yes | Unique subdomain assigned to the trunk (resolves as your-custom-domain.sip.frejun.ai). This is the Termination URL that all outbound calls route to. Alphanumeric and hyphens only. |
| Call status URL | No | HTTPS endpoint that receives call lifecycle webhooks. |
| Secret | No | Signing secret used for HMAC signatures on webhooks. Rotatable without downtime. |
| Channel limit | No | Maximum concurrent calls on the trunk. Defaults to 0 – increase as needed. |
| Recording | No | When enabled, all call audio is recorded and delivered via recording events. |
| Transport type | No | Selects the protocol used for SIP signaling and media – see below. |
Transport type
Select the protocol used for SIP signaling and media between your platform and Teler:
| Option | Port | Encryption |
|---|---|---|
| TLS/SRTP | 5061 | Encrypted signaling (TLS) and media (SRTP) |
| TCP | 5060 | Unencrypted |
| UDP | 5060 | Unencrypted |
Recommended order:
- TLS/SRTP (default, recommended). Use this whenever your platform supports it.
- TCP. Use this if TLS is unavailable. It is more reliable than UDP for larger SIP messages.
- UDP. Use this only if your platform strictly requires it.
Note for UDP: UDP supports credential-based authentication only. You must also share your platform’s origination IP address with the Teler team so it can be allowlisted. Calls from IPs that are not allowlisted will be rejected.
Step 2: Choose outbound authentication
Every trunk authenticates outbound calls one of two ways — pick whichever matches how your downstream SIP system identifies itself; you only need to configure one:
| Method | Best for | Description |
|---|---|---|
| IP authentication | Fixed, static source IPs | Create an IP ACL (Access Control List) – a list of source IPs allowed to send SIP INVITEs – and attach it to the trunk. Calls from an IP in the ACL are authenticated without credentials; anything outside it is rejected. |
| Credential authentication | Dynamic or cloud-based environments where the egress IP can change | Set a username and password on the trunk. Your SIP client presents them on every INVITE. |
IP authentication isn’t suitable for dynamic or cloud-based environments where your SIP client’s egress IP may change; prefer credential authentication in those cases.
- Option A — Create an IP ACL: Name the ACL so it’s identifiable later (e.g., “Test” or “Production Carrier”), add each source IP or CIDR block with Add IP address/CIDR, and label each entry for reference. Once saved, the ACL is reusable across multiple trunks — no need to re-enter the same IPs each time.
- Option B — Set up credential authentication: Set the username and password your SIP client will present on each INVITE. This integration uses credential authentication, reusing the same username and password on the Retell AI side.
Step 3: Configure inbound routing
Tells Teler where to deliver calls that arrive on the trunk:
| Field | Required | Description |
|---|---|---|
| Inbound routing name | Yes | Internal label for the route. |
| SIP URL | Yes | The SIP URL Teler forwards inbound calls to (the Origination URL). Set the value to: sip:sip.retellai.com |
| SIP user | No | SIP username to present to the destination, only if your downstream platform requires one. |
Step 4: Create the trunk
Review the details across all screens and click Create. The trunk is live immediately — outbound calls authenticate using the method chosen in Step 2, and inbound SIP INVITEs route per the configuration in Step 3.
Step 5: Assign a virtual number to the trunk
A trunk isn’t usable until at least one virtual number is assigned to it — this is a separate step, done from the Virtual numbers section rather than the trunk wizard itself.
- Go to Virtual numbers in the left nav and select the number(s) assigned to your account. If no number is assigned yet, contact the support team to get one provisioned.
- Click Actions → Assign.
- In the Assign virtual numbers dialog, set Assign to as Trunk, use Select trunk to find the trunk you created, and click Assign.
- Back in SIP trunks, open the trunk and check the Numbers tab — the assigned number should appear there, confirming the assignment worked.
Full field reference and API details: Teler Docs – SIP Trunking
To test before going live, create the trunk in sandbox mode and assign the sandbox reference number to it here.
Prerequisites
- A Teler SIP trunk that is Active, with the domain name and Transport type already configured
- Outbound authentication on the Teler trunk set to credential authentication, with a username and password you’ll reuse on the Retell AI side
- Inbound SIP URL set to
sip:sip.retellai.com - A virtual number already assigned to the Teler trunk
- A Retell AI account and an agent already created
Step 1: Head to the Phone Numbers section in the Retell AI dashboard
Step 2: Click “Connect to your number via SIP Trunking”
Step 3: Enter the Teler number
In E.164 format.
To test before going live, enter the sandbox reference number here instead of a live number. Sandbox calls go only to and from verified numbers.
Step 4: Enter the termination URI
Your trunk’s domain name, e.g. your_domain.sip.frejun.ai.
Step 5: Enter the trunk’s outbound authentication credentials
The same username and password set on the Teler trunk.
Step 6: Select the Outbound transport
Match the Transport type set on the Teler SIP trunk.
Step 7: Save and assign an agent
Assign your agent to the number for inbound and outbound calls. Your setup is complete.
Test the setup in sandbox
Create the trunk in sandbox mode and use the sandbox reference number in step 3. To test an outbound call, call a verified number from Retell AI. To test an inbound call, dial the sandbox virtual number from a verified number and enter the 4-digit PIN of the trunk.
Integration at a Glance
| Requirements | An active Teler SIP trunk with domain name, Transport type, and credential authentication configured; a virtual number assigned to the trunk; a Retell AI account with an agent already created |
| Setup type | Dashboard-configured on both sides – no code or hosting required |
| Support | support@frejun.com |