Guest dpaschal Report post Posted 04/29/2008 09:15 AM I was using the Dialer_OutDialQueAdd subroutine in a VBS module. I kept getting type-mismatch errors, even though I was feeding it a string for the phone number (as the help file seems to suggest) I reduced it down to just the barest functional elements and still get this error. Here's the code in question: set vg = CreateObject("VoiceGuide.CommandLink") phoneNumber = "18183046281" vg.Dialer_OutDialQueAdd phoneNumber, 0, 0, 0, "", "4", 1, "", "C:\Program Files\VoiceGuide2\Scripts\catch_call_test.vgs", "C:\Program Files\VoiceGuide2\Scripts\catch_call_test.vgs", "[thisActivity]{1}", 0, 2, 5, "C:\Program Files\VoiceGuide2\Scripts\no_one_home.vgs","" vg.Run_ResultReturn $RV_LINEID, phoneNumber set vg = Nothing WScript.Quit I've tried converting the value to a string, even as other data types, but it always gives me a type-mismatch error. I've even tried dimensioning the variable. Am I missing something here? Share this post Link to post
SupportTeam Report post Posted 04/29/2008 09:23 AM Which version of VoiceGuide are you using? Share this post Link to post
Guest dpaschal Report post Posted 04/29/2008 07:40 PM Which version of VoiceGuide are you using? Voiceguide 6.0.3003 Dialer: 6.0.2003 It should be noted that when I put the string directly in, it adds it correctly. It only gives me this problem when I use a variable. I've scoured the web for vbscript help, and tried various ploys, but all seemed to result in the same outcome. Share this post Link to post
SupportTeam Report post Posted 04/29/2008 08:04 PM Voiceguide 6.0.3003 Please update to the latest version ov VG v6 - available for download from our WWW Download pages. Then use the demo provided in the Help file's section on Dialer_OutDialQueAdd as a test first. Share this post Link to post
Guest dpaschal Report post Posted 04/29/2008 09:20 PM Voiceguide 6.0.3003 Please update to the latest version ov VG v6 - available for download from our WWW Download pages. Then use the demo provided in the Help file's section on Dialer_OutDialQueAdd as a test first. Updated to 6.0.3379 Same result. Specific error message: Script: C:\Program Files\Voiceguide2\temp\vbs_4_1.vbs Line: 7 Char: 1 Error: Type mismatch: 'vg.Dialer_OutDialQueAdd' Code: 800A000D Source: Microsoft VBScript runtime error Specific code in question: set vg = CreateObject("VoiceGuide.CommandLink") phoneNumber = "18183046281" vg.Dialer_OutDialQueAdd phoneNumber, 0, 0, 0, "", "4", 1, "", "C:\Program Files\VoiceGuide2\Scripts\catch_call_test.vgs", "C:\Program Files\VoiceGuide2\Scripts\catch_call_test.vgs", "[thisActivity]{1}", 0, 2, 5, "C:\Program Files\VoiceGuide2\Scripts\no_one_home.vgs","" vg.Run_ResultReturn $RV_LINEID, phoneNumber set vg = Nothing WScript.Quit Error logs pertinent section: 141737.52 4 next module is [Queue_Next_Calls] (idx=23) 141737.52 4 RunModule start [Run VB Script,[Queue_Next_Calls],23,,] 141737.52 4 timer clear bForceClear=False 141737.52 4 state [Queue_Next_Calls] Running VB Script... 141737.52 4 rv replace start: [set vg = CreateObject("VoiceGuide.CommandLink") phoneNumber = "18183046281" vg.Dialer_OutDialQueAdd phoneNumber, 0, 0, 0, "", "4", 1, "", "C:\Program Files\VoiceGuide2\Scripts\catch_call_test.vgs", "C:\Program Files\VoiceGuide2\Scripts\catch_call_test.vgs", "[thisActivity]{1}", 0, 2, 5, "C:\Program Files\VoiceGuide2\Scripts\no_one_home.vgs","" vg.Run_ResultReturn $RV_LINEID, phoneNumber set vg = Nothing WScript.Quit ] 141737.52 4 rvns [PathSysVoice]{C:\Program Files\VoiceGuide2\system\voice\}[PathApp]{C:\Program Files\VoiceGuide2\}[PathDataVm]{C:\Program Files\VoiceGuide2\data\}[PathVgSys]{C:\Program Files\VoiceGuide2\system\}[thisActivity]{2}[OutDial_ID]{99}[OutDial_OnNotConnected]{}[OutDial_Answer imeout]{60}[OutDial_RetriesLeft]{2}[OutDial_PauseBetweenRetries]{120}[OutDial_Re ult]{Contacted_AM}[AmWelcMsg_RecLen100ms]{42}[scriptEnd_Time]{4/29/2008 2:17:37 PM}[scriptEnd_Goto_Script]{C:\Program Files\VoiceGuide2\Scripts\voicesolutions.vgs}[scriptEnd_Goto_Module]{}[scriptStart_Time]{4/29/2008 2:17:37 PM}[scriptStart_CalledFrom_Module]{Queue_Next_Calls}[scriptsPath]{C:\Program Files\VoiceGuide2\Scripts\}[scriptPath]{C:\Program Files\VoiceGuide2\Scripts\}[Activity_Select_RowCount]{1}[Activity_Select_1_1]{2}[Activity_Select_2_1] 1}[Activity_Select_3_1]{8183046281}[Activity_Select_4_1]{0}[Activity_Select_5_1] 352-644-1512}[Activity_Select_6_1]{4/14/2008 2:03:03 PM}[Activity_Select_7_1]{1}[Activity_Select_8_1]{1}[Activity_Select_9_1]{4/4/2008}[Activity_Select_10_1]{12:00:00 AM}[Activity_Select_11_1]{4/14/2008}[Activity_Select_12_1]{10}[Activity_Select_13_1]{3}[Activity_Select_14_1]{1 [Activity_Select_15_1]{4/14/2008 2:03:03 PM} 141737.52 4 vbs run [vbs_4_1.vbs], cmd [wscript "C:\Program Files\VoiceGuide2\temp\vbs_4_1.vbs" //I //T:60] 141737.58 4 Run Script waiting. iRunWait=1 (shellid=1860, process=1512) Share this post Link to post
Guest dpaschal Report post Posted 04/29/2008 09:44 PM I used the version from the new helpfile, and that seemed to work. The difference between what I tried and what was in the help file was that I used cstr before, when I populated the variable, and the helpfile used it within the subroutine argument. I guess it's more like a cast than an actual function (cstr, that is) I see you guys caught the thing about "escalation level" not actually being "optional" in the "don't put anything" sense of the word I'm retrofitting my production code with the modification now. Thanks! Share this post Link to post
SupportTeam Report post Posted 04/29/2008 11:07 PM OK, thanks for letting us know its working now. Share this post Link to post