QueueMetrics > Running QueueMetrics

Real time monitoring: Some agents SIP/XXXX, some Agent/XXXX

(1/1)

theeye:
I am trying to get Real time monitoring fully functional.
I have 16 queues, but only 1 queue is currently using dynamic agents.

When the dynamic agents login to the queue, they show up on the live monitor as their description, or Agent/XXXX, and I can monitor these calls

Any other agents who are statically in queues show up as 'SIP/XXXX' and I do NOT have the ability to monitor these calls.

I don't understand what the difference is or why this is happening.

Scott H.

QueueMetrics:
Have a look at the logging made on the queue_log by each agent, and please post here the findings.

My guess is that it will be local/123@context for dynamic ones and SIP/123 for static ones.

theeye:
Your guess is correct

1279664489|1279664443.548732|12015|SIP/4004|RINGNOANSWER|1000
1279664489|1279664443.548732|12015|SIP/4010|RINGNOANSWER|0
1279664489|1279664443.548732|12015|SIP/4023|RINGNOANSWER|0
1279664489|1279664443.548732|12015|SIP/4025|RINGNOANSWER|0
1279720163|1279720153.560960|12008|Local/4489@from-queue/n|ADDMEMBER|
1279720164|1279719483.560154|12008|Local/4489@from-queue/n|RINGNOANSWER|0
1279720168|1279720161.560981|12008|Local/4489@from-queue/n|RINGNOANSWER|0
1279720176|1279720051.560825|12008|Local/4489@from-queue/n|CONNECT|125|1279720172.560997

It would seem that the queue with dynamic members are Local/XXXX@from-queue while the statics members of other queues are SIP/XXXX.

How would I got about fixing that?

theeye:
It seems that it is related to how I setup my queues.

I was having problems with large queues killing the server every time they were hit by many calls at once.  I found this article on the topic:

http://www.freepbx.org/news/2010-02-26/heavy-queue-usage-in-freepbx

So I proceeded to setup my queues so that all agents in the queue are listed as SXXXX,0
When I remove the S on the queues with static agents, then it appears correctly in the Queuemetrics Real Time screen and I can listen in on the call.

Is there a way I can work around this in Queuemetrics so I can have the best of both worlds?

QueueMetrics:
I would simply keep it as it is, because you have static members, and those should "stand out" from the rest.
(or I would remove all static members, even better...)

Navigation

[0] Message Index