As we are experiencing MOH tracking issues in Asterisk 20.8 Queue and later, the CALLERONHOLD and CALLEROFFHOLD UniqueID columns in the queue_log have a colon [:] symbol in front of the value. We’re not sure if this is an issue or something lacking from our configuration. I’ve attached the queue_log file.
The first glaring thing that may or may not matter as the queues setup changed majorly at some point and wasn’t documented well (actually it’s the agent side that changed not the queue creation); is it should be musicclass=default and not music=default.
I’m also not sure what you mean by MOH tracking. If you’re trying to see if the queue member gets dumped to MOH like in normal dialplan; I’m not sure if the logging says that.
I can’t see any significance of the colon in the UniqueID. Nothing in the documentation that I can find.
As I’ve already changed the queues.conf file with musicclass=default.
I track the queue calls using the Queuemetrics CRM tool. For each call, we should monitor/track the Music on Hold (MOH).
However, while checking the queue logs for Hold events [CALLERONHOLD & CALLEROFFHOLD], the UniqueID column in the queue_log file has the colon[:] symbol. If I delete the colon from the UniqueID column, we may obtain the MOH data.
It should be noted that in other events, UniqueID data was updated without a colon, however data for the CALLERONHOLD and CALLEROFFHOLD events had a colon symbol.
Our PBX Details are,
Operating System: Red Hat 9.4
Asterisk Version: 20.8.1
Are these from a patch to Asterisk?:- No, we installed the Asterisk from the source code.
Are they generated using something else (QueueLog dialplan application, or the AMI action)?:- Not using AMI and QueueLog dialplan application.
We are using a simple queue setup; if a call enters in that queue, it will be routed to an agent using rrmemory. Please find the dialplan we used. Also, find the Queue configuration [queues.conf].
Accoridng to docs.loway.ch :: Loway Documentation Center Asterisk itself is not generating CALLERONHOLD and CALLEROFFHOLD, but an application outside of it is. It would be responsible for putting the correct uniqueid value in.
This would also explain why I can find no mention of those in the Asterisk source code.
