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 - coolname

Pages: [1] 2 3 ... 11
1
Running QueueMetrics / Re: agent login in realtime page
« on: May 22, 2012, 03:43:54 »
100[S:1]

2
Running QueueMetrics / Re: how to track ivr?
« on: May 22, 2012, 03:37:23 »
but it doesn't
could you show me a example ivr data?

3
Running QueueMetrics / agent login in realtime page
« on: May 17, 2012, 12:24:13 »
i found that even if the agent log off,she is remain in the login table in realtime page
i post a excel on netdrive for the agent 50223's record ,i can see her in realtime page after 18:00,what's wrong?
http://g.zhubajie.com/urllink.php?id=12354022aznbfo7g3sihmwvf

4
Running QueueMetrics / Re: how to track ivr?
« on: May 16, 2012, 16:47:03 »
the time_id of info-ivr  is lower than enterqueue

5
Running QueueMetrics / Re: how to track ivr?
« on: May 15, 2012, 11:32:19 »


i change the queue_log to suit my use

6
Running QueueMetrics / Re: how to track ivr?
« on: May 13, 2012, 08:27:52 »
yes i configured ,but the total duration *** are empty

7
Running QueueMetrics / how to track ivr?
« on: May 10, 2012, 03:39:11 »


how to configure asterisk to track the new attribute of the ivr

8
really? :D :D :D when would it realeased?

9
no ,i manually restart the qm

10
after run about 20 days,it occured agagin

11
after change into centos 6.2 64bit,mem 8GB,the problem has gone

12
Running QueueMetrics / can i edit the qa data in a complete qa
« on: March 30, 2012, 05:10:44 »
can i edit the qa data in a complete qa?

13
i also have this problem

14
Running QueueMetrics / Re: update data may cost a long time
« on: March 24, 2012, 16:07:35 »
because i found i can't open qm report, so i want to debug it out

15
Running QueueMetrics / update data may cost a long time
« on: March 14, 2012, 03:16:52 »
today i found qm can't show the report.After debug,i found it was a problem with mysql.A update query take a long time and update statement is ' update queuemetrics.queue_log set data1='12' where call_id='******' and verb='CONNECT' limit 1 '.But this statement usually execute very quick,what may cause it? *** was my call id

Pages: [1] 2 3 ... 11