Topics

1

Problems / Custom report error with time range

« on: July 21, 2009, 01:09:30 »

Hi I am currently using Loway QueueMetrics - 1.5.3 and when we run a custom report where we want to say show calls between 1600 and 1800 hrs for any date range longer than 1 day it shows the calls within times for first day and then goes to all calls for other days. Regards Mal

2

Outbound and QueueMetrics / Using Hot Desking and Outbound Agent ID

« on: May 11, 2008, 02:08:25 »

Hi. I have all working very well except for one small issue. We use Hotdesks so different agent logs on to the same extn at different times of day. To do theis agent numbers do not match the extn. ie extn 6811 might have agent 701, 702, 703 use it during the day.
This works perfect for inbound calls.
However on outbound the queuedial tells it to
exten => _XXX.,3,SetVar(MY_AGENT=${CALLERIDNUM})

This logs the call with

1210461473|asterisk-2599-1210461473.31|q-777|NONE|ENTERQUEUE|-|0405001763
1210461473|asterisk-2599-1210461473.31|q-777|Agent/6811|CONNECT|0|
1210461481|asterisk-2599-1210461473.31|q-777|Agent/6811|CONNECT|8|
1210461487|asterisk-2599-1210461473.31|q-777|Agent/6811|COMPLETEAGENT|8|6
1210461487|asterisk-2599-1210461473.31|q-777||COMPLETECALLER|0|6

As can be seen Agent is extn number as is calleridnum.

This shows the call correctly in Real Time Monitor as Calls being Processed.
However it also Logs in the extn so under
Real time Monitor - Agents Logged In  you will see a new entry for Agent 6811.
This also means reports so under extn for outbounds when they could be different agents.


Is it possible to amend this so that instead of agent = calleridnum
we pck up the agent logged on to that extn and use that.

Hope you can help
Regards
Mal

3

Outbound and QueueMetrics / Queuemetrics not recognising Caller (A Party) hangup on outbound call.

« on: April 30, 2008, 04:06:24 »

Hi
Have noticed what believe is a bug in outgoing where call record shows as ongoing in queuemetrics.
It seems to work fine as per logs file example you show if the CALLED (B) party hangs up first as shown from log:-

1195784028|1195784028.43|q-777|NONE|ENTERQUEUE|-|0294674000
1195784028|1195784028.43|q-777|Agent/105|CONNECT|0|
1195784033|1195784028.43|q-777|Agent/105|CONNECT|5|
1195784037|1195784028.43|q-777|Agent/105|COMPLETECALLER|5|4

However if A party or Originator hangs up first only shows first 2 rows. 1195784127|1195784127.51|q-777|NONE|ENTERQUEUE|-|0294674000
1195784127|1195784127.51|q-777|Agent/105|CONNECT|0|

This seems to be the opposite to current issues and responses where they are saying if Rmote (B) hangs up first. I have no issue with that. 

Asterisk Version 1.2.22

I have tried suggestions and thread links in "Queuemetrics not recognising Remote Caller hangup and that doesn't change anything.

Regards and hope you can help