Asterisk Call Center: Queuing Strategies (Latest Versions)

Call queues are powerful only when calls are distributed correctly. If distribution is unfair, some agents stay overloaded while others remain idle, leading to slow responses and poor customer experience.

This is why queue strategies are one of the most important configuration areas in Asterisk call centers.

In this guide, you will learn how queue distribution works in modern Asterisk with PJSIP, the meaning of each strategy, and when businesses should use them.

What Is a Queue Strategy?

A queue strategy defines:

• Which agent receives the next call
• How workload is balanced between agents
• How long agents stay idle between calls

Without the right strategy, call centers suffer from uneven performance and agent burnout.

Where Queue Strategies Are Configured

Queue strategies are defined inside:

/etc/asterisk/queues.conf

Example queue:

[support]
strategy=ringall
timeout=20
retry=5

member => PJSIP/1001
member => PJSIP/1002
member => PJSIP/1003

Main Queue Strategies in Asterisk

1. ringall

All agents ring at the same time. The first person to answer gets the call.

• Fastest answer time
• Best for small teams
• Not fair for large teams

2. leastrecent

Sends the next call to the agent who answered the longest time ago.

• Balanced workload
• Very common in support centers

3. fewestcalls

Chooses the agent who handled the lowest number of calls.

• Fair distribution over long periods
• Useful for performance tracking environments

4. random

Picks a random available agent.

• Simple but unpredictable
• Rarely used in professional setups

5. rrmemory (Round Robin with Memory)

Cycles through agents sequentially and remembers last used agent.

• Even distribution
• Popular in sales teams

6. linear

Calls agents in a fixed priority order.

• Manager-first or tiered escalation
• Not suitable for equal teams

Example — Changing Queue Strategy

[support]
musicclass=default
strategy=leastrecent
timeout=20
retry=5

member => PJSIP/1001
member => PJSIP/1002
member => PJSIP/1003

Reload queues after change:

asterisk -rx "queue reload all"

How to Choose the Right Strategy

Small Team (2–5 agents)

• Use ringall
• Fastest pickup time

Customer Support Desk

• Use leastrecent or fewestcalls
• Ensures fairness and prevents burnout

Sales Team

• Use rrmemory
• Balanced lead distribution

Escalation / Priority Handling

• Use linear
• Senior agent first, then juniors

Common Problems Related to Queue Strategies

Same Agent Gets All Calls

• Using ringall in large teams
• Other agents not available/registered

Calls Take Too Long to Answer

• Wrong timeout or retry values
• Strategy mismatch with team size

Agents Feel Distribution Is Unfair

• Switch to fewestcalls or leastrecent

Real-World Optimization Tips

• Combine queue strategy with agent pause/unpause
• Use dynamic login/logout for shift control
• Monitor statistics for fairness
• Adjust timeout and retry based on call duration

Strategy tuning is an ongoing operational task, not a one-time configuration.

What Comes Next?

After understanding queue strategies, the next important topic is:

• Dynamic queue members (agent login/logout)
• Music on Hold configuration
• Advanced queue reporting

Key Takeaway

Queue strategy determines how fair, fast, and efficient your call center feels.

Choosing the correct strategy — ringall, leastrecent, fewestcalls, rrmemory, or linear — directly impacts customer satisfaction and agent productivity.