Author Topic: Tracking IVR on multi-stint scenario  (Read 2352 times)

andrebarbosa

  • Newbie
  • *
  • Posts: 1
  • Karma: 0
    • View Profile
    • Email
Tracking IVR on multi-stint scenario
« on: July 28, 2010, 20:28:04 »
Hi all,

I'm having a problem tracking IVR activities.
I have a multi-stint queue scenario and the IVR selection is not saved when I move to queue 2.

Here is an example:

shell> tail -100000 /var/log/asterisk/queue_log  | grep 1280337903.199545
1280337951|1280337903.199545|Assistencia|NONE|INFO|IVR|Operador
1280337951|1280337903.199545|Assistencia|NONE|ENTERQUEUE||Zurich-XXXXXX
1280337981|1280337903.199545|Assistencia|NONE|EXITWITHTIMEOUT|1
1280338003|1280337903.199545|Assistencia1|NONE|INFO|IVR|Operador
1280338003|1280337903.199545|Assistencia1|NONE|ENTERQUEUE||Zurich-XXXXX
1280338098|1280337903.199545|Assistencia1|Agent/3458|CONNECT|95|1280338096.199625
1280338422|1280337903.199545|Assistencia1|Agent/3458|COMPLETEAGENT|95|324|5

This call above does not store the IVR selection "Operador"

But in a single-stint call:
shell> tail -100000 /var/log/asterisk/queue_log  | grep 1280338721.199818
1280338741|1280338721.199818|Assistencia|NONE|INFO|IVR|AIDE
1280338741|1280338721.199818|Assistencia|NONE|ENTERQUEUE||AIDE-XXXXXXX
1280338756|1280338721.199818|Assistencia|Agent/3303|CONNECT|15|1280338754.199838
1280339359|1280338721.199818|Assistencia|Agent/3303|COMPLETEAGENT|15|603|3

I can see the IVR selection in the call details and in the reports.


I also tried to do a single QueueLog call in the multi-stint scenario but the result was the same, no IVR selection.
Can you help me here?

Thanks!

Software release:   Loway QueueMetrics - 1.6.0.1

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: Tracking IVR on multi-stint scenario
« Reply #1 on: July 29, 2010, 12:06:50 »
I mean, can you see it for both calls when you run in single-stint mode?

We fixed an issue:

Quote
#1125 - Keeping track of completion codes on muti-stint calls

For 1.6.1, so maybe you should try and update.