Guest Kyle Sampson Report post Posted 04/19/2004 05:57 PM Is there a way to run a VB script or command when an outgoing call gets a busy signal or no answer, but it still has retries left? On all of the tests I've done so far, using <OnNotConnected/> will only run the specified script when the last retry has been completed. Thanks. Share this post Link to post
Guest Kyle Sampson Report post Posted 04/19/2004 08:39 PM On a related note, is there any way to differentiate between busy signals and no answers? This information is essential for the scripts we're creating, but it's not even listed in the possible values for $RV[OutDial_Result]. During testing it looks like calls that get busy signals are recorded in OutDial_Uncontactable_NoAnswer.txt file, but since that file contains no-answers as well, it doesn't help us much. Share this post Link to post
SupportTeam Report post Posted 04/19/2004 11:46 PM Is there a way to run a VB script or command when an outgoing call gets a busy signal or no answer, but it still has retries left? The only function available at this stage is the one specified using <OnNotConnected/> and (as you correctly note) VG will only run the specified script when the last retry has been completed. You could just have each outgoing entry set to 0 retries - and then requeue new entries from within <OnNotConnected/> is there any way to differentiate between busy signals and no answers?Please update your v5.2.1 install with attached .exe This new .exe splits the "Uncontactable" numbers into these files: Uncontactable_NoAnswer Uncontactable_Busy Uncontactable_OnDontDialList Uncontactable_NoDialer Uncontactable_SystemError VgMulti_5.2.1026.zip Share this post Link to post
Guest Kyle Sampson Report post Posted 04/22/2004 03:06 PM That seems to work, thanks. Share this post Link to post