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

Pages: 1 [2] 3 4 ... 7
16
Running QueueMetrics / fake queue
« on: April 05, 2014, 22:59:16 »
HI all

I am trying to do a fake queue to my agents so, I can bill their time through QM, all they have to do is pauses between activities and offcurse login with their users. But it turns out statics appear only after a real call inbound and I do not need calls inbound, I just using the queues as a trigger.

Is there any way of do this?

17
Running QueueMetrics / Re: misunderstood results
« on: November 20, 2013, 19:00:44 »
Well, i pointed back statics  to a queue_log shared with NFS instead of using Mysql and qloaderd.. and statics are OK...  :-[, mysql statics were the problem.

18
Running QueueMetrics / Re: misunderstood results
« on: November 04, 2013, 23:30:16 »
Well, i have the old QM  server reading the local  queue_log file and i have qloaderd running on old server saving info to my new QM server using mysql.

19
Running QueueMetrics / misunderstood results
« on: October 29, 2013, 03:18:40 »
EHLO.

I installed few years ago queuemetrics for a callcenter  and everything was perfect, recently they call me up again to upgrade to the newest version, so i did it  but on a second server, configure  qloaderd, and my newest QM run perfectly . When my client decide to compare information from the oldest QM and newest, some information just seems confusing.

here are the examples:

Old server Qm version is -1.6.3.1

Report Details:    
Atomic queue(s) considered:    400 [400]
Period start date:    October 25 2013, 00:00
Period end date:    October 25 2013, 23:59
Total calls processed:    106
78.3% ans / 21.7% unans

All calls

All calls:    
N. calls answered by operators:    83
Average call length:    215.7 s.
Min call length:    0:02
Max call length:    15:57
Total call length:    5.0 H
Average call waiting time:    20.0 s.
Min waiting time:    0:00
Max waiting time:    8:17
Total waiting time:    0.5 H
Average initial position    1.0
Min initial position    1
Max initial position    2
Coverage    78.3%

Calls fully within the given time interval

Calls fully within the given time interval:    
N. calls answered by operators:    83
Average call length:    215.7 s.
Min call length:    0:02
Max call length:    15:57
Total call length:    5.0 H
Average call waiting time:    20.0 s.
Min waiting time:    0:00
Max waiting time:    8:17
Total waiting time:    0.5 H
Average initial position    1.0
Min initial position    1
Max initial position    2
Coverage    78.3%

Agents on queue

Agent       N. Calls            ...    Total call time    Average call time
DIANA CAROLINA OLAYA ROJAS    20    24.1%       1:30:19      4:30 
DAYANA VANESSA OLIVER ARIAS    31    37.3%       1:59:10      3:50 
ANGIE CATHERINE MORENO VARGAS    32    38.6%       1:28:53      2:46   

new server QM version is  13.04.2-557
 
Report Details:    
Atomic queue(s) considered:    400 [400]
Period start date:    October 25 2013, 00:00
Period end date:    October 25 2013, 23:59
Total calls processed:    106
78.3% ans / 21.7% unans
Multi-stint calls joined together    106


All calls:    
N. calls answered by operators:    83
Average call length:    431.4 s.
Min call length:    0:04
Max call length:    31:54
Total call length:    9.9 H
Average call waiting time:    40.1 s.
Min waiting time:    0:00
Max waiting time:    16:34
Total waiting time:    0.9 H
Average initial position    0.0
Min initial position    0
Max initial position    0
Coverage    0.0%

Calls fully within the given time interval

Calls fully within the given time interval:    
N. calls answered by operators:    83
Average call length:    431.4 s.
Min call length:    0:04
Max call length:    31:54
Total call length:    9.9 H
Average call waiting time:    40.1 s.
Min waiting time:    0:00
Max waiting time:    16:34
Total waiting time:    0.9 H
Average initial position    0.0
Min initial position    0
Max initial position    0
Coverage    0.0%

Agents on queue

DIANA CAROLINA O...
DAYANA VANESSA O...
ANGIE CATHERINE ...
Agent       N. Calls            ...    Total call time    Average call time
DIANA CAROLINA OLAYA ROJAS    20    24.1%       3:00:38      9:01 
DAYANA VANESSA OLIVER ARIAS    31    37.3%       3:58:20      7:41 
ANGIE CATHERINE MORENO VARGAS    32    38.6%       2:57:46      5:33   

--------------------------------------------------------------------------------------------------
As you can see calls and percent match on each server on Total calls processed,  but Average call length, Average call waiting time duplicate his value to double, Coverage on old server is 78% while in the new server is 0%.
Agents on queue values  like total call time and Average call time is duplicated on new version too.

i activate the parameter default.joinMultiStintCalls to true on new server because if i didn't calls duplicate to 200% percent.

I really don't know how to explain this to my client because new version should be start to be on production as soon as possible but they don't trust on it or maybe the problem is the old one.  perhaps i should adjust some option on new version , i  don't know.

Thanks !

20
MySQL storage and Qloaderd/Uniloader / Re: queue_log on mysql
« on: September 30, 2013, 21:40:09 »
Well, finally the info is being displayed but  now every single call it is showed as unaswered.......  :'(

21
MySQL storage and Qloaderd/Uniloader / queue_log on mysql
« on: September 26, 2013, 20:44:49 »
 Hey guys

I want to configure QM so it can check queue_log from mysql, but i did what the manual says:

# This is the default queue log file.
default.queue_log_file=sql:|1

my sqlpreset is 1

restarted QM but it is know working either, any other consideration i should take? what i am missing?
 :o

22
When an agent do an Attended Transfer to an extension (1100). And then i check my reports.... the answer details says.

DATE                      |CALLER      | QUEUE       |WAIT    |DURATION |POS |DISCONECTION |HANDLED BY        ATTEMPTS| CODE         |  STINTS
11/01 - 07:51:38    14227660    Operadora    0:08      1:13             0    Transfer 800      Pedro Sandoval    1                transf-rr.hh    1    


The transfer was done to extensions 1100 but  says TRANSFER 800  which is a queue.

23
HI

as the title said, my attended transfer appear  in QM :

- Transferred to:       800

not to the extension was really transfered, when the transfered is blind its OK.

why is that? :o

24
Running QueueMetrics / Re: Agentlogin and attempts greater that 1
« on: September 22, 2011, 17:17:52 »
OK thanks   ::)

25
Running QueueMetrics / Agentlogin and attempts greater that 1
« on: September 05, 2011, 19:47:31 »
Greetings  ;D
 

I am kind of  confused,  why when i am checking reports  my inbound queues and  some calls  in answered section appear  with,    Attempts  greater than 1 even 10 or more. when this  should happen?, i mean because  i am using "agentlogin"  for  login agents so a call can not ring to them.

 ???

26
Running QueueMetrics / Re: what does mean PU?
« on: August 23, 2011, 16:55:38 »
The calls with "pu" does not have CALLSTATUS record on queue_log but the others does.


example of call with pu

1310646669|1310645459.37|800|Agent/1032370692|CONNECT|177|1310646667.122|0
1310646690|1310645459.37|800|Agent/1032370692|COMPLETEAGENT|177|21|3


calls without it

1310646660|1310645969.56|800|Agent/52555227|CONNECT|188|1310646658.121|0
1310646728|1310645969.56|800|Agent/52555227|COMPLETECALLER|188|68|2
1310646783|1310645969.56|NONE|Agent/52555227|CALLSTATUS|Otros-Otras.Consultas.Sucursal


27
Running QueueMetrics / Re: what does mean PU?
« on: July 28, 2011, 00:02:11 »
any ideas??????????
 ???

28
Running QueueMetrics / Re: working with outgoing calls
« on: July 15, 2011, 16:38:14 »
All right.  ;D

We have outbound agents and inbound agents, the inbound agents login with agentlogin, so they appear connected in real time page, and when they do pause, we can see the status and when i do my reports all those status appear on it so  I want to see my inbound agents in the same way as inbound agents.


 ???

29
Running QueueMetrics / Re: what does mean PU?
« on: July 15, 2011, 16:06:26 »
here it is

the code parte has  PU on some records.. but nobody tipify like that.

http://i279.photobucket.com/albums/kk121/emel_punk/grafica-con-PU.png

30
Running QueueMetrics / what does mean PU?
« on: July 07, 2011, 23:24:30 »
HI


when i do my daily reports i see that some calls has code  with PU, but i never created that code on outomes, so what does mean?

 ???

Pages: 1 [2] 3 4 ... 7