Carriers & SIP · Telnyx · choose your SIP driver

Telnyx with VICIdial: IP-auth PJSIP and chan_sip dialplans

Telnyx carrier examples with separate PJSIP and chan_sip Account Entry and Dialplan Entry blocks, authentication choices, worked prefix conversion and read-only checks. No provider call is claimed.

Start the guide

By Vicigeek Editorial DeskStep-by-step guide8 minute readUpdated November 8, 2026

Before you start

An installed VICIdial dialer with the selected SIP driver enabled and authorized Admin/shell access; use the native carrier guide before creating the Telnyx record.
A Telnyx account/trunk with known authentication, network settings, caller ID and a separately approved test destination.
An inactive isolated campaign, unused carrier ID and unused prefix 8. Record previous values before the Telnyx change.

Finish when: Choose the correct Telnyx driver syntax, fill the native carrier fields, verify the constructed destination and loaded route, then document a bounded test without inventing an audio or registration pass.

The Telnyx templates are not live-tested provider configurations. Do not save placeholders, expose secrets, enable traffic to a fictional number or change a shared listening port. No real calls are placed by this webpage.

01 / 13

Choose one driver, one carrier and one number format

This Telnyx guide separates the carrier Account Entry from the Dialplan Entry and shows PJSIP and chan_sip alternatives. PJSIP is the current Asterisk driver. Use chan_sip only when your installed older build actually loads it; upstream Asterisk removed it in version 21.

These are outbound configuration worksheets, not captured working Telnyx trunks. No provider login, registration or call was performed for this update. The existing native screenshot identifies VICIdial fields; it does not establish provider acceptance.

Telnyx example contract: check these before copyingScroll sideways to compare columns
Item	This guide uses	Why it matters
Authentication	IP-authenticated connection with no Tech Prefix; no outbound credentials or REGISTER.	Use the connection type actually configured on your account.
Dial prefix	8 — an isolated NANP route	For Telnyx, confirm this prefix is unused in the target dialplan context.
Fictional input	812025550123	Remove only the leading 8; the remaining 1 is the country code.
Provider destination	+12025550123	A formatting illustration only; never dial the fictional example.
Branch choice	PJSIP OR SIP (chan_sip)	Keep one Telnyx branch active; do not paste both definitions for the same route.

02 / 13

1. Check which SIP driver your server actually has

On the Telnyx target server, run these read-only CLI checks before changing carrier records. A module name in this list establishes installation/loading only; it does not establish registration, NAT or audio.

Before you use it: Use an authorized shell on the actual Telnyx dialer. These commands inspect the running Asterisk instance and make no call.

sudo asterisk -rx 'core show version'sudo asterisk -rx 'module show like chan_pjsip.so'sudo asterisk -rx 'module show like chan_sip.so'

Reader-run example · not executed for this guide

This example has no recorded result here. Follow its preparation, expected result and stop conditions before using it.

Success looks like: For Telnyx, choose PJSIP when chan_pjsip is loaded. Choose the SIP branch only when chan_sip is loaded on your supported installed build.
Stop if: If the Telnyx target has neither driver, stop. Do not compile a retired module or move listening ports to make this worksheet fit.

Sources for this section

Asterisk: chan_sip lifecycle and PJSIPAsterisk · Checked November 8, 2026

03 / 13

2. Prepare the Telnyx account settings

In Telnyx Mission Control Portal, create or select an IP-authenticated SIP Connection. Add the actual approved outbound public IP used by this dialer.
Associate the connection with the intended Outbound Voice Profile and review destinations, caller-ID policy and the account-specific call limits.
This recipe assumes the connection has no Tech Prefix. If a Tech Prefix is configured, stop and adapt the destination deliberately; do not use either dial string below unchanged. Credential/FQDN connections are different recipes.

You should seeYou have the Telnyx host, selected authentication path, allowed caller ID and agreed destination format. A dashboard-ready label alone is insufficient.

Sources for this section

Telnyx: configure an Asterisk IP trunkTelnyx · Checked November 8, 2026
Telnyx: call completion, IP authentication and number formatTelnyx · Checked November 8, 2026
Telnyx credential connections are a different authentication pathTelnyx · Checked November 8, 2026

04 / 13

3. Put each value in the correct VICIdial field

For Telnyx, use Admin → Carriers → Add A New Carrier and select an unused ID. Select the actual dialer under Server IP. PJSIP requires an installed VICIdial build with PJSIP enabled; the SIP protocol corresponds to chan_sip.

Keep Account Entry and Dialplan Entry separate. On the captured Add form there is no Active control; after an approved save, reopen Modify Carrier and check Active before permitting Telnyx test traffic. Do not overwrite the original carrier.

Carrier ID: vg_telnyxUse a new, unused ID for the isolated Telnyx configuration.
Protocol: PJSIP for branch A; SIP for branch B
Account Entry: Driver configuration onlyPaste the selected Telnyx account block after substituting its placeholders.
Dialplan Entry: The three matching exten lines onlyUse the Telnyx dialplan for the SAME selected driver.
Registration String: Empty for this no-registration trunkTelnyx authentication in this example occurs without SIP REGISTER.
Campaign Dial Prefix / Manual Dial Prefix: 8Review both values and the Phone Code/Phone Number combination; Omit Phone Code changes the digits Telnyx receives.

Actual unsaved VICIdial Add Carrier form showing Account Entry and Dialplan Entry, with a fictional PJSIP example. — Native VICIdial form captured November 4, 2026, Admin 2.14-969a build 261102-0125.
Capture details
It contains an unsaved fictional IP-auth worksheet and an unselected Server IP. Use it to locate the fields only: its values are not a Twilio, Telnyx or Vonage configuration. No carrier, registration or call was created. The complete original capture remains available through Enlarge.

You should seeThe Telnyx record names the right server and one driver; the campaign remains inactive while the generated route is reviewed.

Native carrier setup and saved-value checks

05 / 13

4A. PJSIP: Account Entry

For Telnyx, replace <EXISTING_PJSIP_UDP_TRANSPORT> with the transport name from pjsip show transports; it is not a new transport definition. This narrow worksheet uses UDP and ulaw, not a TLS/SRTP setup. Match your actual network, codec and security requirements before activation.

The context vg-telnyx-inbound-disabled is intentionally left undefined for this outbound-only exercise. Check it is absent and do not create an outbound-capable context under that name. It rejects incoming calls instead of silently routing them into an outbound dialplan.

This single-caller-ID worksheet fixes from_user in PJSIP and fromuser in chan_sip to one permitted number. For Telnyx campaigns using changing list/lead caller IDs, review the effective From and identity-header behavior separately; the fixed example must not be assumed to preserve dynamic caller-ID selection.

Before you use it: Review this Telnyx configuration worksheet, replace every angle-bracket placeholder and select only one channel-driver branch. It has not been loaded into Asterisk.

[vg_telnyx]type=aorcontact=sip:sip.telnyx.comqualify_frequency=60 [vg_telnyx]type=endpointtransport=<EXISTING_PJSIP_UDP_TRANSPORT>aors=vg_telnyxcontext=vg-telnyx-inbound-disableddisallow=allallow=ulawdtmf_mode=rfc4733direct_media=nofrom_domain=sip.telnyx.comfrom_user=<APPROVED_TELNYX_CALLER_ID_E164>

Not executed · worksheet or reference text

This sample is a template or reading aid, not a terminal command. There is no output to show.

Success looks like: The Telnyx field contents match the chosen driver, actual trunk host and agreed number format. This is a configuration check, not a completed call.
Stop if: Stop the Telnyx setup if any placeholder remains, the transport does not exist, or the provider/account contract differs. Do not activate the campaign.

Sources for this section

Asterisk PJSIP outbound trunk configurationAsterisk · Checked November 8, 2026
Telnyx: call completion, IP authentication and number formatTelnyx · Checked November 8, 2026
VICIdial PJSIP carrier fields and dial stringVICIdial · Checked November 8, 2026

06 / 13

4A. PJSIP: Dialplan Entry

Use this Telnyx dialplan only with the PJSIP endpoint named vg_telnyx. The number is before @ in the PJSIP dial string. Keep the VICIdial call_log AGI and campaign timeout; do not paste a raw Asterisk-only test route over the managed campaign route.

Before you use it: Review this Telnyx configuration worksheet, replace every angle-bracket placeholder and select only one channel-driver branch. It has not been loaded into Asterisk.

exten => _81NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)exten => _81NXXNXXXXXX,n,Dial(PJSIP/+${EXTEN:1}@vg_telnyx,${CAMPDTO},To)exten => _81NXXNXXXXXX,n,Hangup()

Not executed · worksheet or reference text

This sample is a template or reading aid, not a terminal command. There is no output to show.

Success looks like: The Telnyx field contents match the chosen driver, actual trunk host and agreed number format. This is a configuration check, not a completed call.
Stop if: Stop the Telnyx setup if any placeholder remains, the transport does not exist, or the provider/account contract differs. Do not activate the campaign.

You should seeFictional 812025550123 matches _81NXXNXXXXXX; the PJSIP Request-URI user becomes +12025550123. This arithmetic check does not send an INVITE.

07 / 13

4B. chan_sip: Account Entry

Choose this Telnyx alternative only if the driver check found chan_sip. VICIdial Protocol is SIP, and the equivalent configuration belongs to the chan_sip generator, not pjsip.conf. Never paste type=endpoint, aors or outbound_auth into this branch.

Before you use it: Review this Telnyx configuration worksheet, replace every angle-bracket placeholder and select only one channel-driver branch. It has not been loaded into Asterisk.

[vg_telnyx]type=peerhost=sip.telnyx.comtransport=udpcontext=vg-telnyx-inbound-disableddisallow=allallow=ulawdtmfmode=rfc2833directmedia=noqualify=yesqualifyfreq=60fromdomain=sip.telnyx.comfromuser=<APPROVED_TELNYX_CALLER_ID_E164>

Not executed · worksheet or reference text

This sample is a template or reading aid, not a terminal command. There is no output to show.

Success looks like: The Telnyx field contents match the chosen driver, actual trunk host and agreed number format. This is a configuration check, not a completed call.
Stop if: Stop the Telnyx setup if any placeholder remains, the transport does not exist, or the provider/account contract differs. Do not activate the campaign.

Sources for this section

Asterisk: chan_sip lifecycle and PJSIPAsterisk · Checked November 8, 2026
Telnyx: configure an Asterisk IP trunkTelnyx · Checked November 8, 2026

08 / 13

4B. chan_sip: Dialplan Entry

The Telnyx chan_sip dial string puts the peer name immediately after SIP/ and the destination after the next slash. PJSIP/+${EXTEN:1}@vg_telnyx and SIP/vg_telnyx/+${EXTEN:1} are alternatives, not interchangeable spellings.

Before you use it: Review this Telnyx configuration worksheet, replace every angle-bracket placeholder and select only one channel-driver branch. It has not been loaded into Asterisk.

exten => _81NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)exten => _81NXXNXXXXXX,n,Dial(SIP/vg_telnyx/+${EXTEN:1},${CAMPDTO},To)exten => _81NXXNXXXXXX,n,Hangup()

Not executed · worksheet or reference text

This sample is a template or reading aid, not a terminal command. There is no output to show.

Success looks like: The Telnyx field contents match the chosen driver, actual trunk host and agreed number format. This is a configuration check, not a completed call.
Stop if: Stop the Telnyx setup if any placeholder remains, the transport does not exist, or the provider/account contract differs. Do not activate the campaign.

You should seeFor the same fictional 812025550123, the chan_sip destination is +12025550123. Only the channel syntax changes between the two Telnyx branches.

09 / 13

5. Check saved values, then the loaded route

After an approved save and normal managed generation, reopen the Telnyx carrier and compare its saved fields. On the selected server inspect the chosen driver only; a missing sip command on a PJSIP-only build is not a provider outage.

Use the actual campaign dialplan context shown by your installed VICIdial configuration. The illustrative 812025550123 is used for a read-only lookup, never a dial attempt. A loaded route may still have unresolved placeholders; inspect the full Dial line.

Before you use it: Review this Telnyx configuration worksheet, replace every angle-bracket placeholder and select only one channel-driver branch. It has not been loaded into Asterisk.

# Run only the branch selected for Telnyx.# PJSIP branch:sudo asterisk -rx 'pjsip show endpoint vg_telnyx'sudo asterisk -rx 'pjsip show aor vg_telnyx'# chan_sip branch instead:sudo asterisk -rx 'sip show peer vg_telnyx'# Both branches: replace the context with the actual generated campaign context.sudo asterisk -rx 'dialplan show 812025550123@<ACTUAL_CAMPAIGN_CONTEXT>'sudo asterisk -rx 'dialplan show vg-telnyx-inbound-disabled'

Reader-run example · not executed for this guide

This example has no recorded result here. Follow its preparation, expected result and stop conditions before using it.

Success looks like: The selected Telnyx object has the expected host, transport and caller ID. The campaign lookup has exactly the chosen prefix and channel syntax. The vg-telnyx-inbound-disabled lookup reports that no such context exists.
Stop if: For Telnyx, stop on duplicate extensions, unknown context, missing endpoint, stale saved values or any angle-bracket placeholder. An OPTIONS result cannot establish a PSTN call.

You should seeThe Telnyx configuration is loaded as intended. Only a later, separately approved call can establish signaling and media.

10 / 13

Incoming calls need their own routing

The Telnyx blocks above deliberately reject inbound calls. Do not remove that boundary until you have the current provider signaling ranges, restricted inbound matching, reviewed trunkinbound context and a specific DID route. Incoming provider IPs are not necessarily the IP your outbound hostname currently resolves to.

For Telnyx, assign the owned DID to this exact SIP Connection and set its inbound destination from the actual network plan.
After the Telnyx inbound source matching and network rules have been reviewed, configure a real inbound context and the exact delivered DID in VICIdial. Verify the intended in-group or destination independently.

You should seeAn outgoing Telnyx call pass does not establish incoming delivery. An inbound setting screenshot does not establish agent audio.

Route one inbound DID to the intended agent destination

11 / 13

6. Test one approved destination and record the result

Keep Telnyx traffic isolated. Have a bounded test window, owned/consenting destination and recorded caller ID before enabling the new carrier and campaign. Do not dial the fictional 555 example or run a bulk campaign as a test.

Place one approved Telnyx call through the actual VICIdial agent workflow so the campaign prefix, caller ID and call logging are included.
Record the constructed digits, sent Request-URI user, selected Telnyx peer/endpoint, final SIP result and provider call identifier privately.
Check ringing/answer, two-way audio, DTMF, hangup from each side and the VICIdial report row separately. Mark each Telnyx observation pass, fail or not tested.
For Telnyx, pause/log out the test agent and disable the test route when the approved window ends; preserve the exact observed outcome rather than inferring it from a saved form.

12 / 13

If it fails, follow the first broken boundary

Telnyx failure → next concrete checkScroll sideways to compare columns
Observation	Check next	Do not infer
No matching route	Compare prefix 8, Phone Code, Omit Phone Code and the exact dialplan context.	Do not loosen the pattern to _X. to make it match.
Endpoint/peer missing	Inspect the selected Telnyx Protocol, server and generated driver configuration.	A saved web form is not loaded Asterisk state.
Unexpected 401/407 challenge	For this Telnyx IP-auth recipe, verify the actual source IP and that the call reaches the intended IP-authenticated connection.	This branch has no SIP auth user. Do not add an arbitrary password to hide a connection-mode mismatch.
403 / provider rejection	Inspect this Telnyx account’s source-IP/ACL, destination permission and effective caller ID.	Do not rotate passwords before reading the actual rejection.
Answered but one-way audio	Compare Telnyx SDP, NAT path, actual media ranges and codecs in an authorized bounded capture.	A 200 OK or OPTIONS response is not an audio-quality pass.

13 / 13

Rollback and continue

For Telnyx, pause test traffic, restore the previous campaign Dial Prefix and Manual Dial Prefix, and disable only the new carrier in its Modify screen. Restore the recorded fields and use the installation’s normal configuration generation procedure.

Confirm the previous route is loaded again. Leave unrelated Telnyx trunks and other providers unchanged. Rotate only an exposed secret, and record which provider and PBX settings were restored.

Twilio: both driver examples

Telnyx: IP-authenticated driver examples

Vonage: current trunk and driver boundaries

Check the actual PJSIP implementation first

Checks and sources

What was checked

Telnyx primary documentation and Asterisk/VICIdial syntax were source-reviewed on November 8, 2026. The NANP prefix transformation was checked offline; no provider authentication, registration or call was performed.
The PJSIP and chan_sip Telnyx Account Entry and Dialplan Entry blocks are configuration worksheets. Native field media is a historical unsaved reference, not this provider’s console or a saved working trunk.
For Telnyx, registration state, outbound signaling, incoming routing, two-way audio, DTMF, hangup and report evidence remain separate acceptance checks.

Primary references

Sources

Telnyx: configure an Asterisk IP trunkTelnyx · accessed November 8, 2026
Telnyx: call completion, IP authentication and number formatTelnyx · accessed November 8, 2026
Telnyx credential connections are a different authentication pathTelnyx · accessed November 8, 2026
Asterisk: chan_sip lifecycle and PJSIPAsterisk · accessed November 8, 2026
Asterisk PJSIP outbound trunk configurationAsterisk · accessed November 8, 2026
VICIdial PJSIP carrier fields and dial stringVICIdial · accessed November 8, 2026