Author Topic: IVR Selection  (Read 4476 times)

Tiago

  • Newbie
  • *
  • Posts: 27
  • Karma: 0
    • View Profile
    • Email
IVR Selection
« on: November 09, 2010, 18:04:24 »
Hi,

Why when a make a custom report with ivr option (XXXX),

Only appears the calls with 1 stint

the version is Loway QueueMetrics - 1.6.1.5


Thanks

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: IVR Selection
« Reply #1 on: November 10, 2010, 10:47:50 »
There have been a couple of fixes in 1.6.2.2.

Tiago

  • Newbie
  • *
  • Posts: 27
  • Karma: 0
    • View Profile
    • Email
Re: IVR Selection
« Reply #2 on: November 11, 2010, 17:26:15 »
I already made the update, but when i make a custom report with IVR Selection, only appears calls with one stint


Thanks

Tiago

  • Newbie
  • *
  • Posts: 27
  • Karma: 0
    • View Profile
    • Email
Re: IVR Selection
« Reply #3 on: November 12, 2010, 16:55:23 »
Hi,

Can you explain me the difference in result for a ivr with or without filter active.


Thanks

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: IVR Selection
« Reply #4 on: November 15, 2010, 10:18:40 »
I think you should contact our Support Services so we can inspect a piece of your queue_log.,

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: IVR Selection
« Reply #5 on: November 18, 2010, 14:28:08 »
This is because the standard behavior of QueueMetrics when running with filters and multi-stint mode as well, is the following:
 
- get the full set of calls
- filter out those who do not match the criteria
- aggregate multiple stints out of remaining calls
 
As you only have the IVR information on the FIRST call, if you run a filter in multi-stint mode, only the FIRST stint will pass the filter; this way, the second stint is not found when running in multi-stint mode. This is a natural extension of what is explained in chapter 12.1 of the User Manual, so we do not consider this a bug.
 
This is the way QM has been working so far; you could easily get that working by adding a second IVR record for the second leg of the call.
Like e.g.:
 
Code: [Select]
1289928508|1234.1|A0|NONE|INFO|IVR|123
1289928508|1234.1|A0|NONE|ENTERQUEUE||123-5551234
1289928538|1234.1|A0|NONE|EXITWITHTIMEOUT|1

1289928540|1234.1|A1|NONE|INFO|IVR|123
1289928541|1234.1|A1|NONE|ENTERQUEUE||123-5551234
1289928611|1234.1|A1|Agent/3347|CONNECT|70|1235.2
1289928624|1234.1|A1|Agent/101|COMPLETECALLER|70|13|2


This works just fine.
 
On the other side, I think that if we change the order of execution doing multi stint aggregation before filtering your problem should go away. We expect to do just that for the next version.