Trace a VICIdial call through the Asterisk dialplan

1. Identify the call's server and route

1. In Admin, open the campaign used for the test and note Dial Prefix and Manual Dial Prefix; record the synthetic lead's phone code and number.
2. Identify the dialer server assigned to this call and connect to that server over SSH. Do not assume the web server processes the call.
3. Join the Asterisk console with the command below.

asterisk -rvvv

You should seeThe CLI connects to the Asterisk instance on the selected server.

2. Find the loaded context

1. From the Asterisk prompt run `core show channels concise` during a supervised test to identify the relevant channel and context.
2. Run `dialplan show <context>` with that observed context, replacing the placeholder. Find the extension or pattern matching the complete digits, including any prefix.
3. Follow the next application and context rather than assuming every Local channel is the carrier leg.

You should seeThe loaded dialplan reveals the matching extension and next application. A channel listing is a snapshot and may be empty after the call ends.

3. Compare the carrier route

1. In Admin → Carriers → Show Carriers open the test carrier on the assigned server. Find Dialplan Entry and Account Entry; do not copy credentials or real provider addresses into a shared ticket.
2. Compare Dial Prefix and Manual Dial Prefix from the campaign with the lead’s Phone Code and Phone Number. The official PJSIP example _91NXXNXXXXXX matches prefix 9 + phone code 1 + a ten-digit NANP number.
3. For an uncalled illustration, 9 + 1 + 2025550123 gives 912025550123. In the official route ${EXTEN:1} removes the leading 9; this example does not establish that any provider accepts the remaining digits.
4. If your actual built digits do not match the route, record the prior values and ask the carrier and campaign administrators to review the precise field; re-open the record after an approved correction.

Enter a carrier example

Open to enlarge

You should seeThe blank Add Carrier screenshot shows where the dialplan field is located, not a saved carrier or successful call.

Official PJSIP example →

4. Verify a correction

1. Record the old field value and change only the agreed test route in the managed Admin record.
2. After the installation's normal configuration generation, inspect the loaded context again and run one authorized test.
3. If the intended route is still absent or another route is affected, restore the recorded field value using the same managed path and escalate.

You should seeThe loaded route matches the approved record; call completion must be checked independently.