Naum Report post Posted 11/20/2007 03:51 AM I am trying to run Text to Speech over D/240JCT-T1 but no success on the following configuration: Windows-XP SP2 with all the critical updates Dialogic Ver 6.0 VoiceGuide Ver 6.0.3377 ( demo version ) Microsoft SAPI 5.1 looks like it is trying to generate a file tts_2_1.wav but it is only 1KB I do have a success if I run the same script on D/41ESC on the following configuration: Windows-2000 Server SP4 with all the critical updates Dialogic Ver 5.1.1 VoiceGuide Ver 6.0.3377 ( demo version ) Microsoft SAPI 5.1 generated file tts_1_1.wav on the first try and played it no problem. Is there anything special that needs to be set for it to work with D/240JCT-T1 ISDN ??? Did I forget to set some parameters? Share this post Link to post
SupportTeam Report post Posted 11/20/2007 04:06 AM Which TTS engine are you using? Have you read this Help file page: http://www.voiceguide.com/vghelp/source/html/config_tts.htm Have you installed the SAPI SDK? Are you able to use the demo apps to create TTS generated .WAV files? Use this app: Start -> Programs -> Microsoft Speech SDK 5.1 -> Tools -> TTSApp The select the TTS engine and press the "Save to .wav" button. Is the .WAV file created? You may need to use v7 in order to be able to reliably select the TTS engine of choice. We have had reports that selecting the default TTS engine using the "Speech applet from the Windows Control Panel" approach recommended for v6 does not always work. Share this post Link to post
Naum Report post Posted 11/20/2007 04:42 AM Which TTS engine are you using? The default engine Have you read this Help file page: http://www.voiceguide.com/vghelp/source/html/config_tts.htm Yes. Have you installed the SAPI SDK? Yes. Are you able to use the demo apps to create TTS generated .WAV files? Use this app: Start -> Programs -> Microsoft Speech SDK 5.1 -> Tools -> TTSApp Yes. I can use it OK. The select the TTS engine and press the "Save to .wav" button. Is the .WAV file created? Yes. It does create a file just fine, and I can play it back You may need to use v7 in order to be able to reliably select the TTS engine of choice. We have had reports that selecting the default TTS engine using the "Speech applet from the Windows Control Panel" approach recommended for v6 does not always work. Like I said in my previous message I have successfully execute everything on D/41ESC on Windows 2000 using VG ver 6, but the goal is to use D/240JCT, because of D240JCT I have to use Dialogic 6.0 and XP there is probably something simple that needs to be set in VG configuration files on D/41ESC configuration was just fine “out of the box” for D/240JCT I had to change to ISDN sample Everything that I need works fine on D240JCT so far. Just the issue with playing Text to Speech, or more like generating a file, since I see the file generated but it is only 1KB Share this post Link to post
SupportTeam Report post Posted 11/20/2007 05:12 AM 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 ktTel=10 ktTts=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. When posting traces/scripts please .ZIP them up and post them as attachments. Please also include in the posted .ZIP the created .WAV file created by VoiceGuide. NB. The TTS generation is done the same way regardless of whether the system is running on Digital or on Analog lines. Share this post Link to post
Naum Report post Posted 11/21/2007 03:42 AM It was strange, must have been one of Windows Flukes... I have uninstalled the Microsoft SDK 5.1 and installed it again. Nothing else was changed. Now I have TTS working with D/240JCT setup. Sorry to bother you with this nonsense Share this post Link to post
SupportTeam Report post Posted 11/21/2007 03:58 AM Thanks for letting us know that the TTS is working on this system now. Please don't hesitate to let us know if you run into any problems in the future. Share this post Link to post