Dynamic Routes is a “decision layer” in FreePBX. It takes a call, optionally collects digits, optionally looks up a value (from an internal/external source), and then routes the call to different destinations based on a match table.

Use it when you want routing rules that are easy to maintain in one place—without rewriting IVRs, inbound routes, or custom dialplan every time your routing logic changes.

What Dynamic Routes is good for

• Single menu → multiple targets: map input like 1/2/3 to IVR, queue, extension, announcement, conference, etc.
• Central routing table: update routing decisions in one screen (instead of editing multiple IVRs).
• Variable-based routing: route using a value stored in a channel variable (when your flow sets one).
• Integration routing: if another app sets a value (AGI/ARI/VoiceBridge), Dynamic Routes can map that value to destinations.

What Dynamic Routes is NOT

• It does not replace Inbound Routes (DID matching still starts there).
• It does not replace IVR/Queues/Ring Groups—those are destinations; Dynamic Routes decides which destination to use.

Where Dynamic Routes Fits in Real Call Flow

Most common placement patterns:

Trunk
  → Inbound Route (DID match)
     → (optional) Announcement / IVR / Time Condition
        → Dynamic Route (decision layer)
           → Final Destination (Queue / IVR / Extension / Conference / Voicemail)

Extension / Feature Code
  → IVR / Custom Destination
     → Dynamic Route
        → Final Destination

Rule of thumb: put Dynamic Routes where you want centralized routing decisions. Keep your DID handling in Inbound Routes and your “customer experience” in IVR/Queue modules.

Dynamic Routes vs Misc Destination vs Misc Application

Dynamic Routes

• Purpose: decision-based routing using a match table
• Input: digits and/or variables
• Output: routes to a chosen destination (queue/extension/ivr/etc.)
• Best for: “If X then go to A else go to B” logic maintained in GUI

Misc Destination

• Purpose: create a destination that points to a custom Asterisk dialplan target
• Input: none (it’s just a pointer)
• Output: jumps to a dialplan context/extension/priority
• Best for: linking FreePBX modules to custom dialplan you wrote

Misc Application

• Purpose: run a specific Asterisk application with custom arguments
• Input: the application + arguments you configure
• Output: executes the app (Playback, AGI, System, etc.)
• Best for: advanced custom actions; use carefully in production

If you need routing decisions, use Dynamic Routes. If you need to jump into your own dialplan, use Misc Destination. If you need to execute an Asterisk app, use Misc Application.

Where to Find Dynamic Routes

Applications → Dynamic Routes

Screenshot 1 — Dynamic Routes List (Overview)

This page is your overview. Each row represents one Dynamic Route definition (a routing rule set). Click the edit icon to change routing rules, or Add Dynamic Route to create a new one.

Screenshot 2 — Create/Edit a Dynamic Route (Fields Explained)

Real Example: How to Use It With an IVR

Clean approach:

Inbound Route (DID)
  → IVR (plays menu + collects digit)
     → Dynamic Route (routes based on digit)
        → Queue / Ring Group / Extension

Why this is useful: you can change the routing table (Sales → Queue A, Support → Queue B) without editing the IVR every time. The IVR stays stable; the Dynamic Route becomes your decision table.

Common Mistakes (And Exact Fix)

1) Everything goes to Default Destination

• Cause: no input/variable is being provided for matching
• Fix: enable DTMF input here, or ensure the upstream IVR/app provides the expected value

2) Match values don’t trigger

• Cause: mismatch like leading zeros, spaces, or different expected digits
• Fix: make match values exactly what callers will enter (or what your upstream app sets)

3) No invalid destination set

• Cause: invalid input has nowhere safe to go
• Fix: set Invalid Destination + Default Destination to something safe (IVR repeat or operator)

MYLINEHUB / VoiceBridge Note (Practical)

If your VoiceBridge / ARI app sets a channel variable (example: intent, language, customer type), Dynamic Routes can map that value to a FreePBX destination. Example mapping ideas:

• MLH_INTENT=SALES → Sales queue
• MLH_INTENT=SUPPORT → Support queue
• MLH_LANG=HI → Hindi IVR

This keeps your AI logic and your PBX routing clean: AI decides the tag/value, FreePBX decides the destination.

Next Steps

1. FreePBX Inbound Routes (DID mapping)
2. FreePBX IVR (menus and digit collection)
3. FreePBX Queues (agent routing strategy)
4. FreePBX Time Conditions (open/closed)