vicidial.org

So I noticed something odd. I'm not sure if it's a backend issue, or a configuration issue on our end. In asterisk.vicidial_log, the "called_count" field is always 0 for the VDAD Answering Machine Detection status (AA). Even if we've called the same lead 10 times, this is always 0. For all other statuses this doesn't happen and the called_count number populates as expected.

Is this a known issue? If not, any thoughts on where I could look in the code to try to fix this? Thanks as always.


Vicibox 6.0.4 from Vicibox_v.6.0.x86_64-6.0.4.iso | ViciDial SVN Trunk v.2.10-443a build 140617-2017 revision 2130 | 1.8.32.3-vici | Multiple Servers: 7 Dial - 1DB - 1 Web| Amfletec VoiceSync PCI Chips | No Extra Software After Installation | Intel MultiCore Processors

1) Good job posting your specs. Earned you an answer! *)

2) It'd say it's obvious that you should consider upgrading as 2.10 was not very widely used. I consider it an "in between" version. Not promising it'll fix your issue, just suggesting that upgrading is Free and MAY solve that and other issues. Solid backup before install (DB, web, all scripts, all configuration files). And remember to load sample conf files during perl install.pl phase. We always add the option during execution so it's automatically going to be "Y" when that portion of the script arrives. And save that final "here's what we're doing" page before you tell it to execute. For posterity (and finger pointing ... and such), we store this on every upgrade either on the server itself in the root folder or in the client jacket for that server. And remember that if you updated sip.conf (externip?) or extensions.conf, they'll need to be re-updated (good reason NOT to update those files).

3) You're looking in a log for the present called count of a lead? Not looking in the list table itself which contains the called count? Hm. I'm sure there's an explanation ... but I don't have one. I suppose there's a reason you may want to know what the called count was at the moment that call was generated, but that won't get updated with later calls ...?

4) AMD scripting is fairly old. I would not doubt for a minute that it's not up to date with the rest of the system. It may not even be aware that this field exists. Just a guess.

Thanks, we might give upgrading a try. I'm going to first see if I can find/fix the AMD scripting, or maybe just populate the field with a simple cron tab script.


Yeah we just wanted to build a few custom reports based off the data of vicidial_log, and we noticed this anomle. Everything else looked normal. The called_count in vicidial_list is fine btw, it's just 0 in the log. If I find a bug/fix I'll update here with details.

i'd say a simple join would resolve the issue. and i doubt it's a "bug" so much as an "implementation in progress" that is resolved in a later svn revision.

you could load the latest vicidial into a virtual server (vSphere is our preference) and check. (also works as a great backup system and upgrade tester!)