QueueMetrics > Running QueueMetrics

Agents not getting proper penalty on queue

(1/1)

cursor:
We upgraded to Queuemetrics 12.10.1 last week and we just notices that agent priorities on queues are no longer working.  When an agent has a WRAP o SPILL priority on the queue configuration they are still logged on without a penalty and they begin receiving calls.  This was working properly until we upgraded from version 1.6.  Are there any changes that need to be made to Queuemetrics to enable it again?

QueueMetrics:
Qm will not do this automatically, but with the variables passed to the dialplan there is one that you can use to set a penalty if you need it.

davilox:
Hi,

We are facing the same problem.. we are already passig the correct priority variable, but we think that there is a problem with the dialplan , that does not use that variable  ...

See below:

; extension 35: agent addqueuemember with hotdesking (for asterisk v1.4+)
exten => 35,1,Answer
exten => 35,2,NoOp( "QM: AddQueueMember (asterisk v1.4+) Agent/${AGENTCODE} at extension SIP/${QM_AGENT_LOGEXT} on queue ${QUEUENAME} made by '${QM_LOGIN}' with prioritylabel '${QM_AGENT_PRIOLBL}' and prioritynum '${QM_AGENT_PRIONUM}'" )
exten => 35,3,Macro(queuelog,${EPOCH},${UNIQUEID},NONE,Agent/${AGENTCODE},HOTDESK,SIP/${QM_AGENT_LOGEXT})
exten => 35,4,AddQueueMember(${QUEUENAME},SIP/${QM_AGENT_LOGEXT},${QM_AGENT_PRIONUM})
exten => 35,5,Hangup

The AddQueueMember command above was missing the ,${QM_AGENT_PRIONUM} parameter....  we added it and penalties started to work !!!   

QueueMetrics:
Yes - this is by design. Should also be written on the user manual.

Navigation

[0] Message Index

Go to full version