Messages

1

Running QueueMetrics / Re: Migrate version (1.3 to 1.4)

« on: September 07, 2007, 16:53:53 »

Hi.

OK is very good.

Is correct.

Bye

2

Running QueueMetrics / Re: Diference between Unanswer Calls reports

« on: September 07, 2007, 16:37:44 »

Hi.

OK is very good.

The bug is solved.

Thanks for everything.

Edgar.   

3

Running QueueMetrics / Migrate version (1.3 to 1.4)

« on: September 04, 2007, 23:24:04 »

Hi.

I am working with the QM 1.3 version. Now I would like to migrate the version to QM 1.4, but the queuemetrics_sample.sql (of version 1.4) is diferent in some field and tables of QM 1.3 database.

I can't change the database because I have a lot of information that I can't loose.

How do I adapt my database of QM 1.3 version to work whit QM 1.4 version

"Running /WEB-INF/README/updating.txt of QM 1.4 over the database of QM 1.3"?

Bye

4

Running QueueMetrics / Re: Diference between Unanswer Calls reports

« on: September 04, 2007, 20:52:19 »

Thanks for everything. 
I hope that the new version fixed the bug.

5

Running QueueMetrics / Re: Diference between Unanswer Calls reports

« on: August 29, 2007, 16:50:51 »

Hi.

Thanks for everything.

Please send mail to my mailbox to resend it whit the queue_log (Atachment) for analysis (my mail is ecriollo@vocatel.com.co). Or write what is your mail to send queue_log.

Edgar.

6

Running QueueMetrics / Re: Diference between Unanswer Calls reports

« on: August 28, 2007, 21:20:36 »

OK. 

Always my calls are made between 9:00:00 AM and 10:00:00PM.

Now. Today I make the report of full last day (24 hours of 00:00:00 until 23:59:59), then why both class of report are'nt equals in amount of calls.

Edgar.

7

Running QueueMetrics / Re: Diference between Unanswer Calls reports

« on: August 28, 2007, 18:12:55 »

Hi.

But the report that I make is of full day (24 hours of 00:00:00 until 23:59:59), then boths class of report must be equals in amount of calls… is not  correct ?

Edgar.

8

Running QueueMetrics / Diference between Unanswer Calls reports

« on: August 28, 2007, 01:47:24 »

When, I study the reports stats of my queues, in the seccion of the Unanswer call (Unans)
there are two clasess of reports, for example:

Unanswered calls

All calls:    
N.of unanswered calls:    60
Average wait time before disconnection:    16.4 s.
Min wait time before disconnection:    0:01
Max wait time before disconnection:    1:25
Total wait time before disconnection:    0.2 H
...
   
Calls fully within the given time interval:    
N.of unanswered calls:    42
Average wait time before disconnection:    16.4 s.
Min wait time before disconnection:    0:01
Max wait time before disconnection:    1:25
Total wait time before disconnection:    0.2 H
...

Why when I make a report of a full day (24 Hours. 00:00:00 at 23:59:59 ) gives me a difference between thats class of reports, why the number of call are diferent and the average are equals.

Edgar.

9

Running QueueMetrics / status agents in Start realtime monitoring

« on: July 23, 2007, 23:26:36 »

Hello.

Why could the realtime monitoring show an agent available (green status) while the agent is really in inbound call (busy).

Bye

10

Running QueueMetrics / Ready agents in 0

« on: July 06, 2007, 20:36:37 »

Hello.

Why when the qloader.pl server  is restarted,  the Start realtime monitoring  option in the Queuemetrics  shows Ready agents in 0, however in my asterisk server there are some agents logged and ready.

Bye

11

Running QueueMetrics / Re: Conexion Mysql

« on: July 05, 2007, 15:34:50 »

Hello Leo.

The features of my QueueMetrics server are: 

Red Hat Enterprise Linux ES release 4 (Nahant Update 3)
Mysql Server 4.1.12

and Queuemetrics version is QueueMetrics 1.3.1

Bye

12

Running QueueMetrics / Conexion Mysql

« on: July 04, 2007, 18:36:09 »

Hello.

Why in my queuemetrics server  when i am typing the netstat in the command line
show....

tcp        0      0 localhost.localdomain:43358 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43357 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43356 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43355 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43354 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43353 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43352 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43351 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43375 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43374 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43373 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43372 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43371 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43370 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43369 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43368 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43367 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43366 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43365 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43364 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43363 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43362 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43361 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43360 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43378 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43377 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43376 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43502 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43519 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43518 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43516 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43515 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43514 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43513 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43512 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43511 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43510 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43508 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43506 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43505 localhost.localdomain:mysql TIME_WAIT
tcp        0      0 localhost.localdomain:43504 localhost.localdomain:mysql TIME_WAIT

Is normal?

Bye

13

Running QueueMetrics / Problem with duration of call

« on: May 29, 2007, 16:44:28 »

Hello.

we have queue from you and in the duration of the calls it start at 11 or 12 minutes, instead of what it should be, i guess 0 seconds since the call is starting.

could you please let me know why this is happenning and how to fix it ?

thank you very much

Edgar Criollo.
+ 57 1 6214492

14

Running QueueMetrics / User supervisor

« on: March 31, 2007, 02:14:46 »

Hello.

In the queuemetrics user guide say:

You can also assign each agent to al Location, i.e. a group of agents working together that you want to monitor as an unit. They might be a supervisor’s team, or people working in the same building, or maybe in the same location for big multinational call-centres. This way you can avoid being cluttered with information about all agents working on the selected queue(s)  and only see those you are actually interested in.

Imagine you have two groups of agents, one working in NY and the other one in LA. You are the supervisor of the NY group, so you are filtering by location. You see a call entering your queue and then disappear. The reason why might be that it was answered by someone in LA, so QueueMetrics filters it out for you.

but how i do that.

I create a LocationX ,
I create a YAgent  and asigned it to Location X.

How I creat a User supervisor that just can monitoring  YAgent.

15

Running QueueMetrics / About status of call "Unanswered yet"

« on: March 16, 2007, 14:48:35 »

In First place, I feel happy with your software, is a good product. Thanks for the aids that it give me.

Now I have a questions.

In the reports of queuemetrics some call have the status of  "Unanswered yet",  What it means this?

Thanks for everything.

Edgar.