Enhanced Disconnection Logging Improvements

[jamiemurray]

I have identified some room for improvements on the Enhanced Disconnection Logging feature within FASTagi_log.pl

This has come off the back of an investigation into why a few clients wait times increased unexpectedly and ASR fell dramatically. It turned out it was because disconnected numbers were being retried up to 5 times (because they were being marked NA or B on previous attempts and then accumulating to the point that's all there was within a list). The recycling is set to 5 attempts 4 hours apart on statuses A,AA,B, and NA in my case.

A) Hangup Cause 19 is treated as AB / B. (Caused by FASTagi_log.pl requiring DIALSTATUS to be CONGESTION at line 1041 when the DIALSTATUS is in fact BUSY)

B) Hangup Cause 18 is treated as NA and the call hangs around on Vici until the dial timeout on the campaign is reached. (Caused by FASTagi_log.pl line 1032 condition not including cause 18 on CHANUNVAIL section)

C) Hangup Cause 102 is not handled by the Enhanced Disconnection Logging section. Some carriers are sending this code back on valid but disconnected or unallocated numbers and should be added in my opinion should be treated as an ADCT.

I posted on the issue tracker and created a patch if anyone else would like to benefit from it http://www.vicidial.org/VICIDIALmantis/view.php?id=1256

[carpenox]

nice, good shit

[jamiemurray]

Just posting some feedback after having this in production today, I've seen a decrease in wait time as a result of cause 18 hanging around for dial time out on campaign and lots of invalids detected that weren't before and no ill effects that I can report so far.

[sadikhov]

how to apply this patch?

[mflorell]

We've added this as a new "Enhanced Disconnect Logging" option '2' in System Settings. Just upgrade to svn/trunk rev 3378 and change the setting and give it a try.

[carpenox]

Niiice that's sweet matt