health4us Report post Posted 12/13/2003 07:44 PM I have tried to add a call to the outgoing queue using the vb script example in the user manual to test if it worked before altering it for my own use... set vg = CreateObject("VoiceGuide.CommandLink") vg.Dialer_OutDialQueAdd "0,5551234", 0, 0, 0, "", "c:\sendinfo\announce.wav", "c:\sendinfo\InfoMenu.vgs", "c:\sendinfo\CallBackDetails.wav", "[CustomerID]{44563}", 0, 2, 5 set vg = Nothing I pasted it into the VBS module as above and when it was run error message popped up.. ARGUMENT NOT OPTIONAL V.G.DIALER_OUTDIALQUEADD VBS_40_38.VBS 123056.06 11 [Queue Call] Running VB Script... 123056.15 11 Run Script waiting... (shellid=5524, process=180) 123057.06 11 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE 123057.06 11 task still running (shellid=5524, process=180) 123058.07 11 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE 123058.09 11 task still running (shellid=5524, process=180) 123059.10 11 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE 123059.10 11 task still running (shellid=5524, process=180) 123100.12 11 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE 123100.13 11 task still running (shellid=5524, process=180) 123101.14 11 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE 123101.15 11 task still running (shellid=5524, process=180) 123102.15 11 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE 123102.15 11 task still running (shellid=5524, process=180) 123103.16 11 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE 123103.16 11 task still running (shellid=5524, process=180) 123104.18 11 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE 123104.18 11 task still running (shellid=5524, process=180) 123105.19 11 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE 123105.19 11 task still running (shellid=5524, process=180) 123106.18 11 callstate DISCONNECTED 66152,0,0 123106.19 11 LsRunWaitTillFinished EV_REMOTEPARTY_DISCONNECT 123106.20 11 Hanging up call... 123106.21 11 RecSoundStop ok 123106.22 11 PlaySoundStop ok 123106.22 11 fnHangupCall end 123106.27 11 linedevstate 2048 0 0 123106.28 11 callstate IDLE 66152 0 0 123106.28 11 WorkingMode@Idle= 123106.31 11 tapi Reply (LineEvReply) ok 65981 0 123107.23 11 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE 123107.24 11 ReinitTelephony due to IDLE start 123107.25 11 tapic lineDeallocateCall(MainCall:66152) 0 123107.43 11 lineOpen(11) => 0 123107.44 11 Waiting for a call... 123107.45 11 lineOpen(11)LineHandle=66033 Share this post Link to post
SupportTeam Report post Posted 12/14/2003 12:32 AM As the error message suggests, there is a parameter missing (I think that you are using a Help file from an older version of VG). The current Help file has the correct syntax & example: set vg = CreateObject("VoiceGuide.CommandLink") vg.Dialer_OutDialQueAdd "0,5551234", 0, 0, 0, "", "c:\sendinfo\announce.wav", "c:\sendinfo\InfoMenu.vgs", "c:\sendinfo\CallBackDetails.wav", "[CustomerID]{44563}", 0, 2, 5, "" set vg = Nothing As you can see you need to add a: , "" to the end of your current command... Share this post Link to post
health4us Report post Posted 12/15/2003 08:32 AM I tried your scenario thanks.. My script followed the fail path after the call was added even though it was added to the database... Any idea why? Thanks Matt 082620.66 11 [Queue Call] Running VB Script... 082620.86 11 Run Script waiting... (shellid=6080, process=1552) 082620.90 0 cl Dialer_OutDialQueAdd 0,5551234, 0, 0, 0, , c:\sendinfo\announce.wav, c:\sendinfo\InfoMenu.vgs, c:\sendinfo\CallBackDetails.wav, , 0, 2, 5, , 082620.91 0 cl Dialer_QueCall 0,5551234, 0, 0, 0, MoTuWeThFrSaSu, c:\sendinfo\announce.wav, c:\sendinfo\InfoMenu.vgs, c:\sendinfo\CallBackDetails.wav, , 0, 2, 5, , 082620.93 0 dial DialListDB_AddCall '0,5551234', 0, 0, 0, MoTuWeThFrSaSu, c:\sendinfo\announce.wav, c:\sendinfo\InfoMenu.vgs, c:\sendinfo\CallBackDetails.wav, , 0, 2, 5, ESCALATION: 082620.94 -1 dial DialListDB_AddCall insert ok 082621.77 11 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE 082621.77 11 task completed (shellid=6080, process=1552) 082621.78 11 No information returned from program to VG (no VGRUNRESULT_11.TXT or SHLRESLT.TXT) Share this post Link to post
SupportTeam Report post Posted 12/15/2003 08:59 AM The Run VB Script module would have followed a Fail path after wards because as we can see in the trace: 082621.78 11 No information returned from program to VG (no VGRUNRESULT_11.TXT or SHLRESLT.TXT) It does not matter to VG what happens in VB Script / Program - VG just waits for VB Script / Program to tell it what to do next... You should use Run_ResultReturn function to return a result back to VG if you want that module to take a path other then 'Fail'... eg: vg.Run_ResultReturn $RV_LINEID, "success" Share this post Link to post