health4us Report post Posted 02/18/2004 11:11 AM I have a script which has been working perfectly for months now i installed v.5.1.8 and theres a problem.. It uses a results variable called "NEXTCALL" AND in this example its been set as "CALL 1" however later in the call flow the "NEXTCALL" RV is called but is now blank containing nothing which causes my script to go wrong. Please can you let me know the fix asap as nothing on my system will now work obvioulsly. 110716.66 11 [SET Next Call Result Var] Evaluate [$RV[Next Call_1_1]] 110716.66 11 RVreplace start: [$RV[Next Call_1_1]] 110716.68 11 RVreplace end: [CALL 1] 110716.68 11 .Eval(CALL 1) 110716.68 11 Error: 1002 110716.68 11 Eval Expr result:[] stored in $RV[NEXTCALL] 110716.68 11 path {} not found 110716.69 11 [Type Of Lead] DB Query 110716.69 11 Jet mode used (To use ODBC mode specify ODBC Connect string) 110716.70 11 RVreplace start: [SELECT WFHProspects.TypeOfLead FROM WFHProspects WHERE (((WFHProspects.JobID)="$RV[JOBID]") AND ((WFHProspects.MemberRef)='$RV[Member Number]'));] 110716.70 11 About to execute Retrieve Operation [SELECT WFHProspects.TypeOfLead FROM WFHProspects WHERE (((WFHProspects.JobID)="1609") AND ((WFHProspects.MemberRef)='1000'));] 110716.70 11 [Type Of Lead] row count=1 110716.71 11 [Which Call] Evaluate [$RV[NEXTCALL]] 110716.71 11 RVreplace start: [$RV[NEXTCALL]] 110716.71 11 RVreplace end: [] 110716.71 11 .Eval() 110716.71 11 Eval Expr result:[] 110716.71 11 path {} not found 110716.71 11 Hanging up call... [No path (False) to next module defined.] 110716.73 11 RecSoundStop ok 110716.76 11 PlaySoundStop err=0 110716.78 11 fnHangupCall end 110716.82 11 linedevstate 2048 0 0 110716.84 11 callstate IDLE 66031 0 0 110716.84 11 WorkingMode@Idle= 110716.86 11 tapi Reply (LineEvReply) ok 65758 0 110717.78 11 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE 110717.78 11 ReinitTelephony due to IDLE 110717.78 11 tapic lineDeallocateCall(MainCall:66031) 0 110718.09 11 lineOpen(11) => 0 110718.09 11 Waiting for a call... 110718.09 11 LineHandle=65775 Share this post Link to post
health4us Report post Posted 02/18/2004 11:32 AM Heres another example of RV not working... this time the RV "YES" was found and these were the paths it could have gone down ---- but it stopped again as tried to look for the false path for some reason when you can clearly see is should go down the "YES" path...... on {Yes} goto [Menu] on {No} goto [c:\program files\voiceguide\scripts\distributors\Call-Admin\InitialSetup.vgs|Intro] 111630.26 11 [Setup] row count=1 111630.27 11 [Setup Complete?] Evaluate [$RV[Setup_1_1]] 111630.27 11 RVreplace start: [$RV[Setup_1_1]] 111630.27 11 RVreplace end: [Yes] 111630.28 11 .Eval(Yes) 111630.28 11 Eval Expr result:[] 111630.28 11 path {} not found 111630.28 11 Hanging up call... [No path (False) to next module defined.] 111630.30 11 RecSoundStop ok 111630.32 11 PlaySoundStop err=0 111630.36 11 fnHangupCall end 111630.41 11 linedevstate 2048 0 0 111630.42 11 callstate IDLE 65929 0 0 111630.42 11 WorkingMode@Idle= 111630.64 11 tapi Reply (LineEvReply) ok 65673 0 111631.54 11 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE 111631.54 11 ReinitTelephony due to IDLE 111631.55 11 tapic lineDeallocateCall(MainCall:65929) 0 111631.86 11 lineOpen(11) => 0 111631.86 11 Waiting for a call... 111631.86 11 LineHandle=65656 Share this post Link to post
SupportTeam Report post Posted 02/18/2004 11:35 AM In the module [sET Next Call Result Var] you should be evaluating "$RV[Next Call_1_1]" not $RV[Next Call_1_1] ie: you must use quotes when the intended result is a string... Share this post Link to post
health4us Report post Posted 02/18/2004 11:44 AM 1\ Weird as this has been working fine for 6 months? Your alteration fixed that little prob -- Has something changed in the new version? Basically everywhere i need to set a RV now i need to go and add "" to the RV so its like this "$RV[name]" is this right? 2\ Problem 2 still exists... even though the right path is there as per the RV Voiceguide wont follow it and looks for the false path. As you can see the right paths are available so whats wrong this time? on {CALL 1} goto [C:\Program Files\VoiceGuide\Scripts\recruitment\IncomingCall\WFHcall1\Call1.vgs|Call1 Update] on {CALL 2} goto [C:\Program Files\VoiceGuide\Scripts\recruitment\IncomingCall\WFHcall2\Call2.vgs|Call2 database Update EXTRA] 114135.36 11 [Which Call] Evaluate [$RV[NEXTCALL]] 114135.37 11 RVreplace start: [$RV[NEXTCALL]] 114135.37 11 RVreplace end: [CALL 1] 114135.37 11 .Eval(CALL 1) 114135.37 11 Error: 1002 114135.37 11 Eval Expr result:[] 114135.38 11 path {} not found 114135.38 11 Hanging up call... [No path (False) to next module defined.] 114135.40 11 RecSoundStop ok 114135.42 11 PlaySoundStop err=0 Share this post Link to post
health4us Report post Posted 02/18/2004 11:48 AM some more " " did the job... so weird as everything is fine for 6 months.... Has something changed in the new version? Basically everywhere i need to set a RV now i need to go and add "" to the RV so its like this "$RV[name]" is this right? Share this post Link to post
SupportTeam Report post Posted 02/18/2004 12:04 PM Change was made to bring the way Evaluate Expression module behaves into line with the rest of the system - quotes are required everywhere else, and doing it that way also better indicates what the intention is - but looking at it again it was probably better to leave it backwardly compatible... The attached vgmulti.exe behaves the same way as the previous versions. We will also update the main install to use this new .exe VgMulti_5.1.8001.zip Share this post Link to post
health4us Report post Posted 02/18/2004 12:11 PM I agree with you thanks... It would also be nice that yuo tell us the users what you have altered so that we know if it will screw our systems up and avoid wasting you hours and us also.... please can you email me the new vgmulti.exe zip file as i can never download them from your website without them been corrupt.. Thanks Matt Share this post Link to post
SupportTeam Report post Posted 02/18/2004 12:17 PM Major changes are now listed in history.txt file - there is a link to it on the downloads page - right next to the link for v5.1.8. What is your email address? Share this post Link to post
health4us Report post Posted 02/18/2004 12:39 PM Does anything work in the new version now TTS that ive had for 5 or 6 months wont play... going from bad to worse 123850.19 11 [Menu] Playing 123850.21 11 tts generate start[<xml version="1.0"> <SAPI> <VOICE REQUIRED="NAME=Audrey16"><RATE SPEED="1">Membership number and password verified.<SILENCE MSEC="1500"/>Please listen carefully to the following options<SILENCE MSEC="2000"/>Press 1 on your phone keypad to go to the calling menu.<SILENCE MSEC="1500"/>Press 2 on your phone keypad to go to the reports menu.<SILENCE MSEC="2000"/>Press 3 on your phone keypad to repeat these options</RATE> </VOICE> </SAPI> </xml>] 123850.31 11 ERROR 5.1.8001 RunModule:0:13:Type mismatch:VoiceGuide 123850.33 11 Hanging up call... [RunModule Error] 123850.36 11 RecSoundStop ok 123850.40 11 PlaySoundStop err=0 123850.43 11 fnHangupCall end 123850.47 11 linedevstate 2048 0 0 123850.49 11 callstate IDLE 65809 0 0 123850.52 11 WorkingMode@Idle= 123850.70 11 tapi Reply (LineEvReply) ok 65791 0 123851.61 11 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE 123851.63 11 ReinitTelephony due to IDLE 123851.64 11 tapic lineDeallocateCall(MainCall:65809) 0 123852.05 11 lineOpen(11) => 0 123852.07 11 Waiting for a call... 123852.09 11 LineHandle=65774 Is there anymore surpirises? Share this post Link to post
SupportTeam Report post Posted 02/18/2004 02:08 PM Looks like the old SAPIWRAP.OCX wound up in the distributable. Attached to this post is the correct one. 1. Go to Windows System 32 directory (in DOS box) 2. run regsvr32 -u SapiWrap.ocx 3. copy new SapiWrap.ocx into the System32 directory 4. run regsvr32 SapiWrap.ocx The main install file will also be updated with correct OCX. SapiWrap.zip Share this post Link to post
health4us Report post Posted 02/18/2004 02:53 PM please can you email me the sapi file like the last file to matt@health4us.co.uk as it doesnt download right Share this post Link to post
SupportTeam Report post Posted 02/18/2004 03:11 PM It was emailed at the same time as the post was put up. (we tested the file downloads a number of times from different places/accounts and it always worked OK for us, and we got no other reports of downloads being corrupted...) Share this post Link to post
health4us Report post Posted 02/18/2004 03:43 PM ok thanks the sapi seemed to fix the issue... next issue is now voiceguide wont recognise an entry in the database and call... Whats wrong with the format of the entry that voiceguide does to allow it to be called? the lines are set to call etc etc voiceguide calls if entry is sent from the phone number loader but nit if entry is inserted straight into the database... ive sent the database as well.. thanks Matt OutDialQue.zip Share this post Link to post
SupportTeam Report post Posted 02/19/2004 01:39 AM With v5.1.8000 and v5.1.8001 when inserting into the OutDialQue.mdb database directly the database fields "LineSelection" need to have a value assigned to them (even if it is just an empty string). Looks like LineSelection field was not initialized and hence was set to NULL in the database... (Please note that the VGDialer and the Send Phone Message modules etc. were still adding the dial entries correctly and they were being dialed OK by VG ) Attached vgmulti.exe will also accept NULL values in the OutDialQue.mdb database fields - please update your v5.1.8 install with this .exe. We tested it on the sample DB you supplied and new .exe found the dial entry and called the number. (.ZIPed file was also emailed) VgMulti_5.1.8002.zip Share this post Link to post
health4us Report post Posted 02/19/2004 07:57 AM Really weird but it still wont work,,, i deleted the old database and let voiceguide add a new one but still nothing? anymore ideas?? Matt Share this post Link to post
health4us Report post Posted 02/19/2004 09:17 AM i have worked out the problem... if i tell the database what lines i want to call on it does not recognise the job... i.e dxxxB1C1 for instance... hope this helps fix it quickly.. Matt Share this post Link to post
SupportTeam Report post Posted 02/19/2004 11:06 AM The OurDialQue.mdb database must be storing each channel name with commas on either side - so if you are inserting the rows into the database yourself directly the LineSelection field should contain: ,dxxxB1C1, if two lines are specified you should insert them like this: ,dxxxB1C1,dxxxB1C2, it's probably best to see how the Telephone Number Loader app loads the entries into the OurDialQue.mdb database and then mimic it... Share this post Link to post