VoIP.infoThe independent guide to business communications.
VoIP.info Troubleshooting

Asterisk VALID_EXTEN is missing after upgrade or DIALPLAN_EXISTS is wrong

Freeze the upgrade boundary, prove the registered function and loaded target, then distinguish omitted arguments, labels, priorities and pattern selection.

Reviewed 2026-10-19Asterisk 22 VALID_EXTEN deprecation documentation, the current Asterisk 23 DIALPLAN_EXISTS reference and function index, upstream func_dialplan implementation, function-availability, CLI help, dialplan reload and pattern-matching documentation were reviewed October 19, 2026. The older page reports branch 22 and the current pages report branch 23; installed branch, module selection, generated and loaded dialplan, context includes, patterns, labels, caller identity and route outcomes remain deployment specific. No PBX, module, package, generated configuration, dialplan, channel, lookup or live call was inspected or testedAdvancedDocumentation based · not lab tested

Freeze the upgrade and first failing lookup

Record timestamp and timezone, node, old and new Asterisk versions, package source, module inventory, configuration generator, reload or restart event, exact expression, supplied context, extension and priority or label, channel context and caller identity, expected target, returned value, warning or error, and next observed priority.

Classify the symptom: unknown VALID_EXTEN, unknown DIALPLAN_EXISTS, invalid arguments, unexpected zero, unexpected one, correct existence result but wrong normal route, generated configuration overwrite, or a later application failure.

Prove what the running process registered

Run core show functions and request help for both names on the affected node. Asterisk 22 documentation marks VALID_EXTEN() deprecated, while the Asterisk 23 index and current upstream func_dialplan surface DIALPLAN_EXISTS() instead. Treat the running CLI as deployment evidence.

If DIALPLAN_EXISTS() is missing too, inspect the build and module state before rewriting more dialplan. A package label or online branch page is not a loaded-function inventory.

Map every old call site and its omitted defaults

Search the authoritative dialplan source, supported custom includes and generator inputs for VALID_EXTEN. Record whether each call omits context or priority. Do not rely on one rendered file or replace an unrelated string in generated output.

For each call site, state the intended question in full: context present, extension at priority 1, exact numeric priority or named label. Then write DIALPLAN_EXISTS() with explicit arguments matching that contract.

Validate numeric priority, label and argument parsing

The current implementation treats a positive numeric third argument as a priority check and a non-empty nonnumeric value as a label lookup. With no priority, an extension check uses priority 1; with context only, the function checks for that context.

Preserve commas, variable expansion and quoting at the call site. An empty field, zero, negative value, malformed expansion and missing label are different evidence and should not be collapsed into a generic missing extension.

Compare existence with actual pattern selection

Inspect the loaded context using dialplan show extension@context, including matched patterns, includes and switches. Asterisk documents that several patterns can match and are ordered by specificity; auto-fallthrough can also reach another matching pattern at a later priority.

A 1 from DIALPLAN_EXISTS() does not prove that the live call selected that exact entry. Preserve the executed context, extension and priority from the channel trace before changing routing.

Correct the earliest demonstrated boundary and retest

Correct only the first proven divergence: obsolete function name, missing running function, wrong context, omitted argument, numeric priority, label, stale loaded dialplan, generator overwrite or mistaken pattern expectation. Reload through the configuration owner and verify the loaded result.

Repeat exact, pattern, missing-context, missing-extension, missing-priority or label and known-good call controls. Confirm later routing and call outcome separately, then remove temporary logging. No PBX, module, package, generated configuration, dialplan, channel, lookup or live call was inspected or tested.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.

Continue your research

Guide · Asterisk 22 VALID_EXTEN deprecation documentation, the current Asterisk 23 DIALPLAN_EXISTS reference and function index, upstream func_dialplan implementation, function-availability, CLI help, dialplan reload and pattern-matching documentation were reviewed October 19, 2026. The older page reports branch 22 and the current pages report branch 23; installed branch, module selection, generated and loaded dialplan, context includes, patterns, labels, caller identity and route outcomes remain deployment specific. No PBX, module, package, generated configuration, dialplan, channel, lookup or live call was inspected or tested

Asterisk VALID_EXTEN migration to DIALPLAN_EXISTS

Replace a deprecated extension check with explicit context, extension and priority evidence without changing routing semantics during an Asterisk upgrade.

Read guide →
Diagnostic · Asterisk's lifecycle table, official release feed, update and upgrade guidance, Asterisk 23 upgrade notes, module-loader guidance and main configuration file reference were reviewed October 10, 2026; Asterisk 24 was still pre-release and no host, package, source archive, build, module, configuration, database, certificate, API, registration, call, media path, rollback or upgrade was inspected or tested

Asterisk changed or broke after an update or upgrade

Find the first changed boundary between the last-good and current Asterisk builds before editing modules, configuration, state or dependencies.

Read guide →
Troubleshooting · Current first-party Asterisk lifecycle, release-policy, download, platform, branch-documentation, upgrade, module-loader, module-loading and CLI-help evidence reviewed October 18, 2026. A displayed lifecycle status label and its scheduled transition date remain separate observations when the source has not reconciled them. Documentation presence, source inclusion, dependency resolution, build selection, installed module file, load state, running state and registered capability remain separate evidence. No host, artifact, signature, source tree, dependency, package, build, module file, configuration, running process, API, endpoint, packet, audio or call was inspected or tested

Asterisk feature or module is missing after a version or build change

Find the first divergence among branch documentation, source, dependencies, build selection, installed files, load policy, running module state and registered capability.

Read guide →
Troubleshooting · Asterisk branch-23-generated and branch-22-generated ModuleCheck, ModuleLoad and Reload action references plus official module-loader, module-type, AMI-permission and network-security documentation reviewed October 16, 2026; installed branch, package contents, module directory, dependencies, modules.conf policy, active use counts, reload support, registered capabilities, parsed configuration, runtime objects, manager privileges and service outcome remain deployment specific; no PBX, module, package, manager session, configuration file, channel, packet, media stream or live call was inspected or tested

Asterisk module is loaded but its capability is missing

Trace one missing application, function, driver, action or runtime object through package inventory, load response, registration, configuration, dependencies and behavior.

Read guide →
Guide · Asterisk 22 LTS

Asterisk dialplan: contexts, patterns and loaded-call evidence

Build a restricted Asterisk 22 call path, then prove its context, match, priorities and runtime behavior separately.

Read guide →
Guide · Current Asterisk CLI, logging, PJSIP troubleshooting and call-identifier documentation reviewed September 30, 2026; CLI commands are not shell commands; no PBX, trace, call or media tested

Asterisk CLI and PJSIP logging for one failed call

Bind one failed call to the loaded PJSIP objects, dialplan decision and short signaling trace, then prove diagnostic cleanup.

Read guide →