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

FreePBX queue priority is not applied or callers answer in the wrong order

Trace one caller from its selecting route through the generated priority target, inherited QUEUE_PRIO value, queue admission, comparable waiters, member offers and queue outcome before changing weights or penalties.

Reviewed 2026-10-12Sangoma Queue Priorities overview and PBX GUI 13 user guide, FreePBX Queue Priorities release/17.0 repository metadata and Queueprio.class.php dialplan source, and current Asterisk QUEUE_PRIO and Queue application documentation reviewed October 12, 2026; the Sangoma screen guide is explicitly version 13, repository state does not prove an installed module or loaded channel state, and no PBX, module, priority object, route, queue, caller, member, channel variable, queue log, SLA result or call was inspected or testedAdvancedDocumentation based · not lab tested

Freeze one ordering claim with comparable callers

Record the queue, caller channels, arrival times, source routes, expected priority classes, member availability and first observed divergence. Classify the symptom: priority object not selected, wrong value, value lost on a new leg, queue not entered, caller rejected or exited, or admitted callers apparently offered out of order.

Do not use answer time alone. Preserve queue-entry, offer, answer, abandon and exit events for every compared caller, plus the installed FreePBX, Queue Priorities, Queues and Asterisk versions.

Prove the intended priority object executed

Resolve the inbound route, IVR key, time condition or other source to the stable Queue Priorities destination ID. Compare its saved value and next destination with the generated and loaded app-queueprio target. A familiar description or correct GUI value does not prove the live call executed that record.

If Apply Config failed or the loaded target is stale, repair that boundary through supported controls before changing the numeric priority.

Follow QUEUE_PRIO on the exact queue-entering channel

Capture the value immediately after the priority target and again on the channel that invokes Queue. The release/17.0 source uses inherited _QUEUE_PRIO, but Local channels, transfers, callbacks and custom dialplan can create or optimize legs or replace variables. Map channel names and unique identifiers instead of relying on a shared linked identifier.

A value on the original leg is not proof that the admitted queue channel retained it. Find the first creation or handoff where the value diverges.

Separate queue admission from ordering

Confirm that each compared call entered the same queue and was accepted into its waiting population. Join-empty rules, maximum callers, timeouts, leave-empty behavior, failover destinations and caller abandonment can remove a call before priority ordering is relevant.

Keep queue priority separate from member penalty, member pause or device state, ring strategy and queue weight. Changing an agent-side control to fix a missing caller variable can reorder unrelated calls.

Reconstruct offers, not just answers

Use queue-log and channel evidence to order arrivals, effective priorities, member offers, ringing intervals, answers and exits. A lower-priority call may appear to answer first because it was already offered, the higher-priority call had not been admitted, different members were eligible, or the first offer was not accepted.

Do not claim strict SLA compliance from a small test. Preserve simultaneous-event resolution, clock sources and logging gaps as limitations.

Correct one owner and retest the class matrix

Correct the first proven divergence: source selection, saved value, Apply Config, loaded target, variable inheritance, queue destination or a separate member-policy defect. Retest one lower, equal and higher class under controlled availability, plus an unauthorized source path.

Accept only the intended ordering without starving ordinary callers or changing unrelated queues. Roll back the value or path if evidence diverges. 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 Queue Priorities overview and PBX GUI 13 user guide, FreePBX Queue Priorities release/17.0 repository metadata and Queueprio.class.php dialplan source, and current Asterisk QUEUE_PRIO and Queue application documentation reviewed October 12, 2026; the Sangoma screen guide is explicitly version 13, repository state does not prove an installed module or loaded channel state, and no PBX, module, priority object, route, queue, caller, member, channel variable, queue log, SLA result or call was inspected or tested

FreePBX Queue Priorities: caller weight, channel scope and queue order

Assign a documented queue priority to the intended caller path, preserve it across the configured destination chain and distinguish caller ordering from agent penalty, staffing, service level and answer outcome.

Read guide →
Guide · FreePBX 17 operational guidance using Sangoma's version-13-scoped field reference plus current Asterisk 23 Queue, queue-variable and queue-log documentation reviewed October 10, 2026; no PBX, module, queue, route, caller, member, endpoint, prompt, music, report, destination, staffing level, capacity or call was inspected or tested

FreePBX queues and agent operations

Design and verify caller admission, agent eligibility, offer strategy, overflow and queue evidence as separate controls.

Read guide →
Diagnostic · Current Sangoma FreePBX Queues and Music on Hold documentation plus Asterisk 23 Queue application, queue-variable and queue-log references reviewed October 10, 2026; the detailed Sangoma queue screen guide remains scoped to PBX GUI 13, and no PBX, module, route, queue, caller, member, prompt, music stream, report, destination, capacity, staffing level or call was inspected or tested

FreePBX queue caller waits, exits or hears the wrong treatment

Trace one queued caller through admission, waiting media and announcements, live eligibility, exit reason and failover before changing staffing or queue-wide settings.

Read guide →
Troubleshooting · Current Sangoma queue documentation and Asterisk queue interfaces reviewed September 27, 2026; installed module and Asterisk behavior remain version-sensitive, and no queue, agent, endpoint or call was tested

FreePBX queue agent does not ring: prove eligibility before changing strategy

Trace one queued call through membership, login, pause, device state, wrap-up and queue policy before changing agent or capacity settings.

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 →
Guide · Current Asterisk logging, runtime command, logger.conf, debug-collection, call-identifier and console-verbosity documentation reviewed September 30, 2026; no process, logger, trace, storage path or call tested

Asterisk logging without permanent debug overload

Map configured destinations, console levels, call identifiers and a bounded protocol trace without leaving sensitive debug collection active.

Read guide →
Troubleshooting · Current Asterisk queue-log, logging-configuration and main-configuration documentation plus Asterisk 22 Queue, QueueLog and QUEUE_VARIABLES references and the Certified Asterisk 22.8 QueueLog AMI reference reviewed October 11, 2026; installed version, module state, effective configuration, log directory, file or realtime backend, permissions, rotation, clock, queue, call, custom event and consumer require local evidence, and no PBX, logger, queue, file, realtime backend, database, importer, report, packet, audio or live call was inspected or tested

Asterisk queue log is missing, incomplete or attributed to the wrong call

Trace one queued call from Queue entry through logger policy, file or realtime storage, event identity, rotation and downstream import before changing queue behavior.

Read guide →