Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - tank30

Pages: [1] 2 3 4
1
Running QueueMetrics / Re: phantom ABANDON calls!
« on: February 26, 2009, 09:18:03 »
RINGNOANSWER only happens if the call TIMES OUT ringing the agent and it returns to the queue. If  agent has a 30 second timeout and the caller ABANDONS the call in 5 seconds it will log an ABANDON not a RINGNOANSWER.

This is the only time ast_queue_log is executed with RINGNOANSWER. The subsequent code of this function goes on to autopause the agent/member if autopause is enabled. Not something that happens when callers hang up when ringing the agents.

/*! \brief RNA == Ring No Answer. Common code that is executed when we try a queue member and they don't answer. */
static void rna(int rnatime, struct queue_ent *qe, char *interface, char *membername)
{
if (option_verbose > 2)
ast_verbose( VERBOSE_PREFIX_3 "Nobody picked up in %d ms\n", rnatime);
ast_queue_log(qe->parent->name, qe->chan->uniqueid, membername, "RINGNOANSWER", "%d", rnatime);


2
Running QueueMetrics / Re: phantom ABANDON calls!
« on: February 12, 2009, 12:48:11 »
So when you mentioned above that the agent was on the phone with the customer for 13 seconds is not valid. 

What happens when the customer abandons the call when Asterisk is ringing an Agent. Wouldnt that mean that the agent code will appear in the queue log line?


3
Running QueueMetrics / Re: phantom ABANDON calls!
« on: February 11, 2009, 14:43:51 »
If the agent was in conversation the status would have been COMPLETEAGENT or COMPLETECALLER one in which the agent was connected to the caller and then a hangup occurred. ABANDON only gets recorded when the caller hangs up while still in Queue, not after a call is connected.
ARG3 of ABANDON is hold time not call duration.

ABANDON(position|origposition|waittime)

The caller abandoned their position in the queue. The position is the
caller's position in the queue when they hungup, the origposition is
the original position the caller was when they first entered the
queue, and the waittime is how long the call had been waiting in the
queue at the time of disconnect.


4
Running QueueMetrics / Re: phantom ABANDON calls!
« on: February 09, 2009, 09:25:23 »
Hi , i was looking for an answer on asterisk relevant forums and i got this reply:
"ok, from the information provided everything looks good. Looks like the call hit your IVR and the user selected 4, which immediately launched the application Queue(TechSupportQueue,tT), the caller was listening to musiconhold for 13 seconds while the call was being offered to Agent/1010. Unfortunately the caller hung up before Agent/1010 could pick up the phone, which is why you have 2 log entries for abandoned. However, both those log entries record the exact same uniqueid 1233843585.3162, so your analysis software just needs to record 1 abandoned call.

Running the statistics needs to assemble a table of call records (based on uniqueid) and then report the status based on the log entry. Once said table is assembled, then totals can be extrapolated from the table. Simply doing a count of the word ABANDON or any other status will yield erroneous data, like when a caller waits, agent 1 doesnt answer, caller remains in queue, agent 2 doesnt answer, caller remains in queue even longer, and then agent 3 answers. All those offers to agents will log on that uniqueID but the final status of the call itself will be COMPLETEAGENT or COMPLETECALLER or maybe even TRANSFER, even with all the RINGNOANSWER entries.
"

This is the cdr of the call in question above:
"","22372345","4","131_voice_menu_GR","""22372345"" <22372345>","SIP/5060-aad1b4d0","","Queue","TechSupportQueue|tT","2009-02-05 16:19:45","2009-02-05 16:19:47","2009-02-05 16:20:32",47,45,"ANSWERED","DOCUMENTATION","1233843585.3162",""


and this is what i got in the queue.log

1233843632|1233843585.3162|TechSupportQueue|Agent/1010|ABANDON|1|1|13
1233843632|1233843585.3162|TechSupportQueue|NONE|ABANDON|1|1|13






5
Running QueueMetrics / Re: phantom ABANDON calls!
« on: February 03, 2009, 16:04:39 »
I am using ring strategy random and my Agents are not dynamic.


 


6
Running QueueMetrics / Re: phantom ABANDON calls!
« on: February 02, 2009, 08:26:46 »
Hi,
  I am using 1.4.22.

7
Yes but what happens if the Agent that the call is forwarded to is within the same queue?
Forwarding a call does not necesarily means that we send it to second level support.
For example perhaps the customer is calling for second time and he want to talk with the agent that took the first call.

8
Running QueueMetrics / phantom ABANDON calls!
« on: January 29, 2009, 12:03:12 »
Hello,
  I am getting weird phantom calls with disconnection "Abandon" and "*"  as caller.



from the queue log i found the below:

1233144264|1233144140.2005|SalesQueue|Agent/1015|COMPLETEAGENT|10|57|1
1233144304|1233144089.1998|SalesQueue|Agent/1009|COMPLETECALLER|7|179|1
1233144314|1233144302.2038|ReceptionQueueGR|NONE|ENTERQUEUE||22740223
1233144318|1233144302.2038|ReceptionQueueGR|SIP/334|CONNECT|4|1233144314.2039
1233144322|1233144288.2037|TechSupportQueue|NONE|ENTERQUEUE||99826624
1233144330|1233144288.2037|TechSupportQueue|Agent/1007|CONNECT|8|1233144322.2043
1233144376|1233144302.2038|ReceptionQueueGR|SIP/334|TRANSFER|s|macro-tl-userexten-base|4|58
1233144488|1233144475.2058|ReceptionQueueGR|NONE|ENTERQUEUE||Unavailable
1233144493|1233144475.2058|ReceptionQueueGR|SIP/334|CONNECT|5|1233144488.2059
1233144542|1233144496.2060|SalesQueue|NONE|ENTERQUEUE||99102821
1233144555|1233144496.2060|SalesQueue|Agent/1009|ABANDON|1|1|13
1233144555|1233144496.2060|SalesQueue|NONE|ABANDON|1|1|13

1233144572|1233144475.2058|ReceptionQueueGR|SIP/334|COMPLETEAGENT|5|79|1
1233144649|1233144613.2082|SalesQueue|NONE|ENTERQUEUE||22813888
1233144659|1233144613.2082|SalesQueue|Agent/1015|CONNECT|10|1233144649.2086
1233144674|1233144615.2083|SalesQueue|NONE|ENTERQUEUE||22882600
1233144682|1233144615.2083|SalesQueue|Agent/1009|CONNECT|8|1233144674.2091
1233144783|1233144288.2037|TechSupportQueue|Agent/1007|COMPLETECALLER|8|453|1
1233144802|1233144615.2083|SalesQueue|Agent/1009|COMPLETECALLER|8|120|1
1233143781|1233143760.1978|Outbound|Agent/1014|CONNECT|21|


Any ideas?
thanks,
KM

9
QueueMetrics installation / Re: Upgrade from 1.4.4 to 1.4.7 problem
« on: January 08, 2009, 13:46:55 »
Hello and Happy New Year!

Sorry but i forgot to send a reply after the upgrade...   :P
It solved the problem as predicted.

Thanks for the support!

KM

10
QueueMetrics installation / Re: Upgrade from 1.4.4 to 1.4.7 problem
« on: December 17, 2008, 10:54:32 »
I will probably be doing the upgrade tonight. Will let you know how it goes.


11
QueueMetrics installation / Re: Upgrade from 1.4.4 to 1.4.7 problem
« on: December 04, 2008, 13:32:16 »
Hi,
Did you find out anything using the files i sent?


12
QueueMetrics installation / Re: Upgrade from 1.4.4 to 1.4.7 problem
« on: December 01, 2008, 15:49:05 »
Files sent via mail succesfully today!   
I guess you cleand up your inbox!    ;D ;D ;D

13
QueueMetrics installation / Re: Upgrade from 1.4.4 to 1.4.7 problem
« on: November 28, 2008, 12:09:29 »
Hi,
  i have sent the reqistered info to queuemetrics (at) loway dot ch  but the mail  keeps coming back because the mailbox is full!
I am eagerly waiting for news.

thanks! 

14
QueueMetrics installation / Re: Upgrade from 1.4.4 to 1.4.7 problem
« on: November 21, 2008, 08:41:22 »
Anyone else having this issue? The users are getting really upset here... 
They are probably setting up a lynch mob right now!

15
QueueMetrics installation / Re: Upgrade from 1.4.4 to 1.4.7 problem
« on: November 21, 2008, 08:35:32 »
I get a really big list of filenames. Here is the start of the page



Show filesystem
This page is a helper to trace the content of available directories under the "default.monitored_calls" parameter.

User has the CALLMONITOR key? true
Search path: /var/spool/asterisk/monitor/



.gsm files


.wav files


.WAV files
/var/spool/asterisk/monitor/queue-TechnicalFaultQueue-2008-08-03-19:50:08-26944079-1217782179.304-.WAV
/var/spool/asterisk/monitor/queue-TechnicalFaultQueue-2008-11-20-20:09:17-99240796-1227204530.2741-.WAV
/var/spool/asterisk/monitor/queue-Outbound-2008-10-15-10:46:42-131-1224056802.1370-.WAV
/var/spool/asterisk/monitor/queue-Outbound-2008-08-30-11:21:12-131-1220084472.283-.WAV
/var/spool/asterisk/monitor/queue-SalesQueue-2008-07-15-13:22:18-99328533-1216117295.2581-.WAV
/var/spool/asterisk/monitor/queue-Outbound-2008-09-17-15:41:53-131-1221655313.3939-.WAV
/var/spool/asterisk/monitor/queue-Reception333-2008-05-06-11:39:03-22772973-1210063143.2407-.WAV
/var/spool/asterisk/monitor/queue-SalesQueue-2008-07-18-14:22:47-96547922-1216380136.3010-.WAV
/var/spool/asterisk/monitor/queue-SalesQueue-2008-07-15-14:27:49-99814514-1216121233.2881-.WAV
/var/spool/asterisk/monitor/queue-TechnicalFaultQueue-2008-04-25-11:30:58-99626130-1209112226.175-.WAV
/var/spool/asterisk/monitor/queue-TechSupportQueue-2008-11-14-13:55:33-99537729-1226663697.2965-.WAV
/var/spool/asterisk/monitor/queue-AccountingQueue-2008-08-21-09:24:50-99440121-1219299860.413-.WAV
/var/spool/asterisk/monitor/queue-AnyOtherQueue-2008-06-17-11:11:08-25633047-1213690233.1203-.WAV
/var/spool/asterisk/monitor/queue-SalesQueue-2008-09-25-17:56:50-25721285-1222354569.4577-.WAV
/var/spool/asterisk/monitor/queue-TechnicalFaultQueue-2008-04-01-10:09:23-22325032-1207033732.58-.WAV
/var/spool/asterisk/monitor/queue-AnyOtherQueue-2008-10-31-19:05:13-99409779-1225472674.7107-.WAV
/var/spool/asterisk/monitor/queue-TechnicalFaultQueue-2008-09-24-12:08:14-22387751-1222247259.2020-.WAV
/var/spool/asterisk/monitor/queue-SalesQueue-2008-08-01-16:19:10-99592366-1217596701.2760-.WAV
/var/spool/asterisk/monitor/queue-TechSupportQueue-2008-09-06-12:17:22-99889746-1220692609.485-.WAV
/var/spool/asterisk/monitor/queue-SalesQueue-2008-10-18-13:13:33-96573166-1224324767.507-.WAV
/var/spool/asterisk/monitor/queue-SalesQueue-2008-10-17-09:13:38-22482227-1224224013.526-.WAV
/var/spool/asterisk/monitor/queue-TechSupportQueue-2008-05-14-10:33:23-26819735-1210750371.1366-.WAV


Pages: [1] 2 3 4