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

FreeSWITCH XML dialplan: evaluation and execution

Understand contexts, conditions and queued applications before building a routing rule.

Reviewed 2026-10-24FreeSWITCH 1.11.3 release reference; verify installed modules and package supportIntermediateDocumentation based · not lab tested

Read the evaluation model

The XML dialplan groups extensions and conditions within contexts. Conditions determine which actions are selected, and actions normally execute after dialplan evaluation. This differs from assuming each action immediately changes the values used by the very next condition during the same evaluation pass. Supported inline actions are an explicit exception. Not every application can run inline. Keep preprocessor variables, runtime channel variables and regex captures distinguishable when reading an example.

FreeSWITCH configuration has distinct responsibilities
A SIP profile defines a listener and transport behavior, the directory supplies user identity, and the dialplan selects actions. Media modules execute the application path. FusionPBX manages configuration above FreeSWITCH.

Conceptual responsibilities, not a file-loading sequence. FusionPBX is an administration layer; edits to generated configuration can be replaced by its management workflow.

Keep untrusted entry points narrow

Identify the context selected for an incoming call and the source of that assignment. A public inbound context should reach only the destinations intended for untrusted callers. A broad route into privileged outbound logic can turn a working PBX into an unauthorized transit service. Create one explicit test destination and an intentional unmatched-number result. Verify which condition matched and which application executed. When transferring back into the dialplan, inspect the new destination and context rather than assuming the original route continues unchanged.

Test both matches and misses

Use valid local numbers, invalid numbers and destinations the caller is not permitted to reach. Include a busy or unavailable destination and confirm the fallback. For a variable-dependent route, log a non-sensitive value at the relevant stage so the evaluation order is observable. If a management interface owns the dialplan, use its supported editing mechanisms. Retain the previous rule and a recovery path. A syntactically valid XML file can still implement the wrong permissions or route every unmatched call into the wrong tenant.

Keep XML source, fetch, parse and execution distinct

The FreeSWITCH comparison compares static or dynamic XML with Asterisk configuration without claiming identical semantics.

Keep the selected gateway and media leg in the dialplan proof

Use the SIP profile and gateway guide and gateway-down diagnostic after the XML dialplan selects an outbound bridge.

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 · Current SignalWire-maintained SIP-profile, gateway, registration, call-setup, diagnostic, trace and CLI documentation was reviewed October 24, 2026. Shipped profile names and defaults are configuration examples, not security guarantees or proof of an installed listener. No profile, socket, certificate, gateway, credential, provider account, registration, dialplan, packet, call, media stream, price, availability, compatibility or support response was inspected or tested.

FreeSWITCH SIP profiles and gateways: listeners, trust and trunk state

Keep Sofia profile listeners, directory identities, gateway definitions, registration, dialplan authority and observed call behavior as separate evidence.

Read guide →
Guide · Current SignalWire-maintained SIP-profile, TLS, Event Socket, CLI, diagnostic, registration and trace documentation was reviewed October 24, 2026. Shipped bindings, credentials and verification defaults are documentation values, not a secure deployment baseline. No host, firewall, ACL, listener, certificate, private key, credential, module, Event Socket, endpoint, provider account, packet, backup, restore, penetration test, price, compatibility or call was inspected or tested.

FreeSWITCH security: bound listeners, trust, control and recovery

Secure Sofia, dialplan, TLS, Event Socket, modules and restore paths as separate control boundaries with runtime evidence.

Read guide →
Guide · Wireshark 4.x / current upstream tool documentation; inspect installed versions

Correlating SIP call legs with PBX events

Follow transfers and bridges without assuming one Call-ID represents the entire business call.

Read guide →
Guide · FreePBX 17 installation guidance, current release/17.0 framework documentation and Sangoma custom-extension guidance, together with current Asterisk architecture, module, channel and dialplan documentation, were reviewed October 24, 2026. FreePBX is treated as a management and generation layer for Asterisk, not as a competing signaling engine. Repository support ranges, installer defaults, documentation examples and feature availability do not prove the installed framework, Asterisk branch, module set, license, platform health, custom-code compatibility or accepted call behavior. No host, installer, PBX, module, database, generated file, custom dialplan, endpoint, trunk, packet, media stream, backup, restore, upgrade, price, availability, compatibility, support entitlement or call was inspected or tested

FreePBX vs Asterisk: choose the management and configuration boundary

Compare a FreePBX-managed Asterisk system with direct Asterisk administration by ownership, generated configuration, custom logic, lifecycle, recovery and acceptance evidence.

Read guide →
Guide · Current SignalWire-maintained FreeSWITCH manual sections for architecture, installation, modules, Event Socket and XML Curl, together with current Asterisk architecture, module, channel, dialplan, AMI and ARI documentation, were reviewed October 24, 2026. Product vocabulary, configuration domains, control interfaces and installation paths are compared as operating models, not as benchmark results or proof of identical capabilities. Documentation and packaged defaults do not prove installed versions, enabled modules, scale, latency, media quality, security posture, compatibility, staffing cost, support terms or suitability for a workload. No host, switch, PBX, module, XML document, configuration file, event socket, API, endpoint, trunk, packet, media stream, benchmark, failover event, price, availability, support response or call was inspected or tested

FreeSWITCH vs Asterisk: compare configuration and control models

Compare FreeSWITCH and Asterisk by channel model, configuration authority, dialplan, external control, module lifecycle, installation and a reversible workload proof.

Read guide →
Guide · Current SignalWire-maintained installation, module, CLI, SIP-profile and diagnostic documentation was reviewed October 24, 2026. The documented package and source paths, vanilla configuration and command examples do not prove a supported operating-system combination, installed build, enabled module, secured listener, capacity, recoverability or accepted call. No host, repository account, token, package, compiler, module, configuration, endpoint, packet, media stream, backup, restore, price, support entitlement or call was inspected or tested.

FreeSWITCH installation: packages, source, modules and first-call proof

Choose one reproducible installation path, record the effective module and configuration baseline, and prove a restricted first call before exposing service.

Read guide →
Guide · Current SignalWire-maintained codec, media-handling, channel-variable, SIP-profile, trace and audio-troubleshooting documentation was reviewed October 24, 2026. Codec and media-mode capabilities do not prove module load, negotiation, transcoding, NAT reachability, SRTP protection, audio quality or capacity. No host, module, endpoint, SDP, packet, capture, recording, conference, benchmark, media stream, price, compatibility or call was inspected or tested.

FreeSWITCH media and codecs: prove each negotiated RTP path

Compare full media, proxy media and bypass media while retaining per-leg codec, SDP, address, security and packet evidence.

Read guide →
Troubleshooting · Current SignalWire-maintained gateway, Sofia-profile, diagnostic, call-setup, trace and events documentation was reviewed October 24, 2026. Gateway state names and command examples require verification on the installed build and profile. No switch, profile, gateway, credential, provider account, DNS answer, firewall, registration, OPTIONS exchange, packet, call, media stream, failover event, price, availability, compatibility or support response was inspected or tested.

FreeSWITCH gateway down: registration, ping, route or upstream failure

Separate Sofia gateway lifecycle, OPTIONS reachability, dialplan selection, SIP response, hangup cause and media evidence before changing a trunk.

Read guide →