QueueMetrics > General Asterisk configuration

Dynamic Agents and Asterisk ARA

<< < (2/3) > >>

QueueMetrics:

--- Quote from: supertle on July 24, 2008, 21:50:41 ---
Local/1001@Customer1 to Queue1
Local/1001@Customer2 to Queue2

QM is recognizing this as the same Agent when in fact its two different agents.

--- End quote ---

Yes - QM will turn the Local/XXX@ctxt to Agent/XXX no matter what the context is. You should use distinct IDs for each agent.
 

QueueMetrics:

--- Quote from: supertle on July 24, 2008, 23:03:29 ---Also, the realtime monitoring is looking good but when I run reports on the queue.  It is showing the phone extension rather then the Local/agent@context.  The reports does not show anything about these Local/Agents@context answering calls.  It shows the SIP/XXXX devices answering the call.

--- End quote ---

This should be easy - try switching the value here:


--- Code: ---#If a channel name is different when the call is opened from when it's closed, which one to use?
default.useEndingChannelName=true

--- End code ---

Try setting to "true" or "false".

supertle:
I tried what u suggested in:
default.useEndingChannelName=true
default.useEndingChannelName=false

and it does not make a difference with either.  In the report, it shows the agentID as the SIP/XXXX.  I need to be able to group the reports by the actual AgentID and not where the agent happenned to be sitting at the time he logged in at.  We can have many agents sitting at the same SIP/XXXX location so looking at a report grouped by phone locations does not help.

I am adding the agents in using addmemberqueue as you suggested Local/AgentID@CustomerContext. 
I have default.rewriteLocalChannels=true which is displaying the Agent ID great in the realtime monitoring but when the call is answered, it still shows the SIP/XXXX answering the call.

We have over thousands of agents that is configured like this in our database:

ABC_1001
...
ABC_1999

QST_1001
...
QST_1999

XYZ_1001
...
XYZ_1999

Each customer is assigned with a different 3 digit code.  We have many customers and these 3 digit code is how we are distinguishing agents between each customers.  Do I need to do something in the context CustomerContext to send to the queue_log to tell queuemetrics that it is this AgentXXXX@CustomerContext  answering the call and not SIP/XXXX??

QueueMetrics:
Can you post an example of a call taken from your queue_log file? and explain what went on during that call?

supertle:
1218557396|1218557354.172|NONE|Local/2301@Customer1|AGENTLOGIN|-
1218557399|1218557354.172|NONE|Local/2301@Customer1|AGENTLOGIN|-
1218557442|1218557442.173|Customer1-q6831|NONE|ENTERQUEUE||ARS_GW1
1218557486|1218557442.173|Customer1-q6831|SIP/1104-0087e4b0|CONNECT|44
1218557831|1218557442.173|Customer1-q6831|SIP/1104-0087e4b0|COMPLETECALLER|44|345


Here's a snippet of an agent logging into a queue.  Follow by a call into that queue.  How can I tweak what's written above of having SIP/1104 to agent/2301 as the one answering and completing the call. 

Navigation

[0] Message Index

[#] Next page

[*] Previous page