paul1125 Report post Posted 01/18/2008 03:31 AM Hello, I put a chinese word into VBscript file, when VoiceGuide ran to this VBscript file then VoiceGuide will hang up the line and break off whole procedures. Is it meaning the VoiceGuide doesn't support double bytes or chinese character set? The attached file is the VBscript file, please someone can help me to solve the problem. Thanks ! Paul lib_num2wav.zip Share this post Link to post
SupportTeam Report post Posted 01/18/2008 03:40 AM Not sure if VBScript itself supports chinese characters. Have you tried creating a test VBScript file with chinese characters in it and running that VBScript using the wscript.exe or cscript.exe tools? Would it be possible for you to work around using the chinese characters by writing the actual VBScript code in the Roman/Western letters? We would need to see a trace from VoiceGuide to see what actually happened when the script was ran. Could you please post a copy of VoiceGuide's Trace Logs which captures the problem, this will allow us to see what happened. Enable logging by setting the log levels to 10 in VG.INI as per below: [Log] VoiceGuide=10 Then restart VG and make a test call which demonstrates the problem. Trace files will be created in VG's \log\ subdirectory. Please post the traces and the VoiceGuide script used. When posting traces/scripts please .ZIP them up and post them as attachments. Share this post Link to post
paul1125 Report post Posted 01/18/2008 08:32 AM The attached file is a copy of VoiceGuide's Trace Logs, thanks. Paul Not sure if VBScript itself supports chinese characters. Have you tried creating a test VBScript file with chinese characters in it and running that VBScript using the wscript.exe or cscript.exe tools? Would it be possible for you to work around using the chinese characters by writing the actual VBScript code in the Roman/Western letters? We would need to see a trace from VoiceGuide to see what actually happened when the script was ran. Could you please post a copy of VoiceGuide's Trace Logs which captures the problem, this will allow us to see what happened. Enable logging by setting the log levels to 10 in VG.INI as per below: [Log] VoiceGuide=10 Then restart VG and make a test call which demonstrates the problem. Trace files will be created in VG's \log\ subdirectory. Please post the traces and the VoiceGuide script used. When posting traces/scripts please .ZIP them up and post them as attachments. 0118vgm.zip Share this post Link to post
SupportTeam Report post Posted 01/18/2008 10:00 PM Traces show VoiceGuide started the VBScript, but looks like the VBScript with the chinese characters had problems running. Suggest you do not use chinese characters in VBScript files. Have you tried creating a test VBScript file with chinese characters in it and running that VBScript using the wscript.exe or cscript.exe tools? Would it be possible for you to work around using the chinese characters by writing the actual VBScript code in the Roman/Western letters? Share this post Link to post