Guest Jason Report post Posted 03/16/2004 02:50 AM I qued up 40 numbers, the same number actually 40 times to test answering machine accuracy. And VG dials 5 of the numbers then stops... It keeps listing " ready to dialout : 36 (out of 36) Its been a long time since it dialed the last number. Any ideas? Share this post Link to post
SupportTeam Report post Posted 03/16/2004 05:07 AM Are you using an unregistered evaluation version of VoiceGuide? The unregistered version can only dial out to 10 or 20 numbers before being restarted, see: http://voiceguide.com/vgFeatures.htm Are you using VG v5.2.1 or some older version? (older versions of VG were limited to dialing out to only 5 numbers between the need to restart the software) If you have MS Access installed on your computer you can easily see what is happening with the list of numbers to be called - just open the file OutDialQue.mdb (in VoiceGuide's \data\ subdirectory) and you can see at what date/time the various numbers will be dialed. Share this post Link to post
Guest Jason Report post Posted 03/17/2004 12:50 AM The version is 4.8.45 and is registered. with VG dialer. I used it before, same system, but on windows 2000. It qued up and dialed 30 000 numbers no problem. In some testing that I did, i found that if there was no wav or script specified in the numbers loader, but only a script to run if answered by human, and it was mistaken me for a answering machine, it would hang up and stop dialing. OR if I clicked hangup in the middle of the dialing or script it seemed to not want to continue after that. I made it a point to not hit the "hangup" and to eneter a wav file if answering machine detected, and its been working up to 50 qued calls so far. I think its more to do with the hangup, not the answering machine script/file not being specified since I see a line in the log file that says "resourceunavailable" and a "waitforlinedrop" The line drops, IE ON HOOK, and will sit and wait. I can call back in and the script will answer. I have seen it dial out one number after this, and I have also seen it dial the rest that are in the que, and I have also seen it not dial anymore. Rebooting server will fix it as well, and will continue to dial, excpet 1 number is dleeted from database. To stop VG, and the dialogic service (DCOM) and re-start it all, will not continue calling out. If I close and re-open VG, 1 number is removed from the list to be dialed out. IE "ready to dialout 12 (out of 12)" will change to 11 out of 11. And no, I wasn't smoking anything when I was testing this. I sure hope you don't tell me to upgrade, I'm poor. Share this post Link to post
SupportTeam Report post Posted 03/17/2004 01:18 AM and its been working up to 50 qued calls so far. Sounds like all is fine with v4.8.45 as long as there is a wav/vgs specified for an answering machine and the "Hangup" button is not pressed during dialing... To stop VG, and the dialogic service (DCOM) and re-start it all, will not continue calling out. Sounds like you would need to get the Windows' TAPI Service restarted as well... Regarding the current dialed number being deleted from database if VG is stopped while dialing that number then that's quite possible as well... I'm told that in v5.x of VG the outbound dialing was extensively rewritten and I know that in current version the above situations do not happen. Overall it sounds like the system is working system, just as it has before when you have qued up and dialed 30000 numbers no problem. so I guess there is not need to upgrade, but there is a number of nice new features in v5.2.1's Dialer (see the Help file's online page at: http://www.voiceguide.com/vghelp/html/DialListInto.htm ) Share this post Link to post
