咨询：适配MongoDB与Asterisk的queue.conf集成方案选型

Great question! Moving your Asterisk queue config from queue.conf to MongoDB is a smart move for scalability and dynamic management—here are the most practical, battle-tested approaches I’ve used or recommended:

1. Use Asterisk’s Native res_config_mongodb Module (Simplest Approach) #

Asterisk has built-in support for pulling configs from MongoDB via the res_config_mongodb module. This is the easiest way to replace queue.conf without writing custom code.

How to set it up: #

• First, install the res_config_mongodb module (it might be included with your Asterisk package, or you’ll need to compile Asterisk with --with-res-config-mongodb).
• Configure extconfig.conf to tell Asterisk to load queue configs from MongoDB:

  ; Format: <config-type> => mongodb,<database-name>,<collection-name>
  queues => mongodb,asterisk,queues
  

• Create a queues collection in your asterisk MongoDB database, and store queue documents matching the structure of queue.conf parameters. For example:

  {
    "name": "support_queue",
    "musiconhold": "default",
    "context": "support_inbound",
    "extension": "1000",
    "maxlen": "20",
    "strategy": "ringall",
    "member": ["SIP/agent1", "SIP/agent2"]
  }
  

• Restart or reload Asterisk with asterisk -rx 'module reload res_config_mongodb'—it will start pulling queue configs directly from MongoDB.

Pros: #

• Native Asterisk support, no custom code needed
• Changes to MongoDB take effect in real-time (no full Asterisk restart required)
• Follows standard Asterisk queue parameter conventions

Things to watch out for: #

• Make sure your MongoDB document fields exactly match the queue.conf parameter names (case-sensitive in some versions)
• Keep the res_config_mongodb module updated to match your Asterisk version

2. Build a Custom ARI Application (For Full Control) #

If you need advanced logic—like dynamic queue creation based on business events, or integrating queue data with other systems—Asterisk REST Interface (ARI) is the way to go. This lets you build a custom service that manages queues via MongoDB.

How to set it up: #

• Enable ARI in ari.conf and create an application user with permissions to manage queues.
• Write a service (Python, Node.js, etc.) that connects to MongoDB. When your system needs to create/update a queue:
  1. Fetch the queue configuration from MongoDB
  2. Use the ARI API to send commands to Asterisk (e.g., queues.create to spin up a new queue, queues.addMember to add agents)
• You can also listen to ARI events to sync queue status (like agent availability, call waiting counts) back to MongoDB for reporting.

Example snippet (Python with ari-py): #

import ari
import pymongo

# Connect to MongoDB
client = pymongo.MongoClient("mongodb://localhost:27017/")
db = client["asterisk"]
queues_coll = db["queues"]

# Connect to ARI
ari_client = ari.connect('http://localhost:8088', 'my_ari_user', 'my_ari_pass')

# Load and create a queue from MongoDB
queue_doc = queues_coll.find_one({"name": "support_queue"})
ari_client.queues.create(
    queueName=queue_doc["name"],
    musicOnHold=queue_doc["musiconhold"],
    context=queue_doc["context"],
    extension=queue_doc["extension"],
    maxlen=queue_doc["maxlen"]
)

Pros: #

• Full control over queue lifecycle and logic
• Easy to integrate with your existing business systems
• Supports complex workflows (e.g., auto-scaling queues based on call volume)

Things to watch out for: #

• You’ll need to handle error recovery (e.g., restarting queues if Asterisk reboots)
• Requires writing and maintaining custom code

3. Hybrid Sync Mode (Smooth Transition) #

If you’re not ready to fully abandon queue.conf, you can set up a sync between the file and MongoDB. This lets you gradually migrate while keeping your existing workflow.

How to set it up: #

• Option 1: Write a script that parses queue.conf (using a config parser library) and syncs the data to MongoDB at regular intervals. Then switch Asterisk to use res_config_mongodb once you’re confident.
• Option 2: Use MongoDB triggers or a watcher script to detect changes in the queues collection, generate a new queue.conf file, and reload Asterisk with asterisk -rx 'queue reload'.

Pros: #

• Low-risk transition from traditional config files
• Compatible with existing tooling that relies on queue.conf

Things to watch out for: #

• Sync delays can cause inconsistencies between MongoDB and Asterisk
• Need to handle conflicts if someone edits both queue.conf and MongoDB directly

Quick Recommendations #

• For most use cases, start with Option 1 (native res_config_mongodb)—it’s the fastest and least error-prone.
• If you need custom logic or integration, go for Option 2 (ARI).
• Use Option 3 only if you need a gradual migration path.

内容的提问来源于stack exchange，提问作者Onur Durmuş