Updating queues via FOP2 vs Trixbox Admin Panel
We are running Trixbox v2.8.0.3 and had been administering the queues via that interface for the last few years until I found they could be administered via the FOP2 interface.
After the queue has been updated via FOP2, the queue members box when viewed through Trixbox is empty. I can see via FOP2 that the queues are still working correctly, but would like to know where the configuration is stored with each queue update, and whether we can only use one method or the alternate between the 2 without breaking the queues in some way.
Cheers,
Jordan
After the queue has been updated via FOP2, the queue members box when viewed through Trixbox is empty. I can see via FOP2 that the queues are still working correctly, but would like to know where the configuration is stored with each queue update, and whether we can only use one method or the alternate between the 2 without breaking the queues in some way.
Cheers,
Jordan
Comments
In Asterisk queues you can have static memebers (the ones defined in queues.conf), and dynamic members (the ones added via dialplan, ami or agi via "addqueuemember").
If you have the options persistenmembers=yes in queues.conf, any dynamic member that is added to a queue will be "remembered" by asterisk when it is restarted, so you do not have to ask the agent to log again if asterisk crashes or is restarted for whatever reason. The data is stored in the astdb (hint: use "database show" in the asterisk cli to see the contents of the whole astdb).
You can use both types. FOP2 will work only on dynamic members, that means that you cannot REMOVE a static member from fop2 (but you can pause/unpause it).
Trixbox is dated in that regard, more recent FreePBX versions include in the queues config page a way to define static *and* dynamic members and even set restrictions on what extensions can be added dynamically or not. FOP2 will honor those freepbx settings.
Best regards,