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

FreePBX Misc Destination reaches the wrong number or fails

Trace one selecting module from its saved destination ID through the generated Misc Destination handoff, exact digits, loaded match, route or feature owner and final result before editing labels or routes.

Reviewed 2026-10-12Sangoma Misc Destinations overview and PBX GUI 13 user guide, FreePBX Misc Destinations release/17.0 repository metadata and generated-dialplan source, current Sangoma outbound-route documentation, and current Asterisk dialplan documentation reviewed October 12, 2026; the Sangoma screen guide is explicitly version 13, repository state does not prove an installed module or generated configuration, and no PBX, module, destination, consumer, route, trunk, dialplan, endpoint or call was inspected or testedIntermediateDocumentation based · not lab tested

Freeze one selecting branch and one symptom

Record one authorized occurrence with timestamp and timezone, source DID or internal caller, matched inbound route or application, IVR digit or condition branch, selected Misc Destination, intended dial string and observed outcome. Classify the first symptom: wrong saved object, wrong digits, no loaded target, invalid extension, blocked feature, wrong outbound route, trunk failure, no answer or media failure.

Do not begin by renaming duplicate objects or changing every outbound pattern. Preserve the installed FreePBX and Misc Destinations versions, saved configuration, generated files and relevant call evidence.

Prove which saved object the consumer references

Inspect the selecting IVR, inbound route, time condition, announcement, callback or other module and capture its destination type and stable identifier. Then resolve that identifier to the current Misc Destination description and exact dial string. A matching label is insufficient when objects were copied, renamed or recreated.

If the consumer references another destination type, stay with that owner. Misc Applications create dialable internal codes, while Custom Destinations publish custom dialplan targets; neither should be rewritten to make a Misc Destination trace appear correct.

Compare saved, generated and loaded state

After a supported Apply Config, locate the installed module's generated ext-miscdests entry for the selected record and compare its target digits with the saved value. Then inspect the loaded Asterisk dialplan for the same record. Keep a stale generated file, rejected reload and stale loaded context as separate failures.

Do not edit generated FreePBX files as a durable repair. Correct the owning record or apply-config failure, regenerate, reload and recheck the exact target.

Follow the configured digits into the first real owner

The release/17.0 source hands the stored digits into internal dialing logic. Trace the first loaded match for those exact digits and caller context: extension, feature code, queue, voicemail, DISA, outbound route or invalid extension. Preserve prefixes and transformations at every boundary.

A valid ext-miscdests entry can still reach the wrong owner because the stored digits are wrong or because another pattern wins later. Conversely, an expected external number that matches no permitted outbound route is not repaired by recreating the wrapper.

Separate outbound policy and carrier outcome

For an external target, prove the matched outbound route, transformed digits, caller-ID owner, selected trunk, provider response, answer and media in order. A route match does not prove carrier acceptance, and carrier acceptance does not prove the intended person answered or heard audio.

For a feature or privileged target, prove the source caller is authorized. An inbound IVR branch does not inherit trust simply because the generated handoff enters from-internal; add explicit authentication or redesign the call flow when the target requires it.

Correct the first divergence and retest every consumer

Change only the first demonstrated fault: consumer ID, saved dial string, apply-config result, loaded target, route pattern, restriction, caller identity or downstream owner. Retest the original branch, each additional recorded consumer, one neighboring selection and an unauthorized boundary.

Confirm the intended destination without widening unrelated dialing permissions or emergency reach. Roll back the record and consumer selections if any unaffected path changes. This workflow is documentation-derived and was not reproduced on an installed or laboratory FreePBX system.

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 · Sangoma Misc Destinations overview and PBX GUI 13 user guide, FreePBX Misc Destinations release/17.0 repository metadata and generated-dialplan source, current Sangoma outbound-route documentation, and current Asterisk dialplan documentation reviewed October 12, 2026; the Sangoma screen guide is explicitly version 13, repository state does not prove an installed module or generated configuration, and no PBX, module, destination, consumer, route, trunk, dialplan, endpoint or call was inspected or tested

FreePBX Misc Destinations: selectable handoffs and dial-string ownership

Publish an already understood dialable target for another FreePBX module while keeping the selecting module, stored dial string, generated handoff, outbound policy and final call result independently provable.

Read guide →
Guide · Sangoma Misc Applications and Misc Destinations guidance, FreePBX Misc Applications 17.0.3 release/17.0 metadata and current dialplan source, and current Asterisk dialplan documentation reviewed October 11, 2026; Sangoma screen guidance may reflect older PBX GUI releases, and no PBX, module, application, feature code, destination, extension, generated or loaded dialplan, endpoint, permission boundary or call was inspected or tested

FreePBX Misc Applications: dialable feature codes and destination boundaries

Publish a unique internal code for a managed PBX destination while keeping Misc Applications, Misc Destinations, Custom Destinations and ordinary extensions distinct.

Read guide →
Guide · Sangoma Custom Destinations, Misc Applications and Misc Destinations guidance; FreePBX Custom Applications 17.0.1 and Misc Applications 17.0.3 release/17.0 metadata and current dialplan sources; and current Asterisk Goto, Gosub, Return and dialplan documentation reviewed October 11, 2026; older screen guides establish concepts rather than an exact FreePBX 17 field map, and no installed module, code, application, destination, generated or loaded dialplan, caller path or call was inspected or tested

FreePBX Custom Destinations: publish custom dialplan without losing ownership

Register a reviewed context, extension and priority as a managed destination, choose transfer or subroutine behavior deliberately, and keep source, generated state and call results separate.

Read guide →
Troubleshooting · Current Sangoma IVR guide and FreePBX 17 IVR module metadata plus current Asterisk 22 PJSIP DTMF, logging, Background, WaitExten and special-extension documentation reviewed September 28, 2026; no PBX, module, endpoint, trunk, generated dialplan, prompt, destination, RTP event, SIP INFO request, in-band tone, digit or live call was tested

FreePBX IVR keypress is ignored or reaches the wrong destination

Trace one caller digit from the ingress call leg through Asterisk reception, IVR matching, retry policy and the generated destination before changing DTMF or menu settings.

Read guide →
Troubleshooting · FreePBX outbound-route module, user-guide and configuration-example documentation plus the current Asterisk Dial reference reviewed October 5, 2026; exact FreePBX 17 module fields, generated dialplan, permissions and provider numbering require runtime verification

FreePBX outbound route mismatch: digits, order, trunk attempts and response proof

Trace the digits received by FreePBX through route precedence and transformations to each attempted trunk and remote response.

Read guide →
Diagnostic · Current Sangoma fwconsole and Asterisk CLI, dialplan and PJSIP troubleshooting documentation reviewed September 27, 2026; no FreePBX, Asterisk or call path lab tested

FreePBX Apply Config failed: isolate generation from reload

Preserve the failed change, capture the supported fwconsole reload error and prove which generated object reached Asterisk before attempting repair.

Read guide →
Troubleshooting · FreePBX DISA release/17.0 repository and dialplan-generation source plus current Asterisk 23-generated DISA application documentation reviewed October 10, 2026; no PBX, installed module, signature, database, generated or loaded dialplan, inbound route, PIN, DTMF event, caller identity, context, outbound route, trunk, provider response or call was inspected or tested

FreePBX DISA access or outbound call fails: route, PIN, context and trunk proof

Trace one external attempt from the inbound destination through authentication and post-authentication digits to the selected outbound route and remote result.

Read guide →