Guest newpop1 Report post Posted 03/31/2008 06:56 PM Hello, we are upgrading from VG6 analog dialogic D4PCIU to: -Windows 2003 STD Server -LOCAL T1:DYNAP 23+1D VOICE -Dialogic DMV600BTEPeq combined media board -VG 7.x version In the C:\Program Files\VoiceGuide\Config I see several XML files, which one should we use as a tenplate for this type of digital T1 line and the type of Dialogic digital board? Also, anything special we need to do to VG to make it work with the T1? Thank You Share this post Link to post
Guest newpop1 Report post Posted 03/31/2008 10:39 PM Hello, forgot to add that we have a 23+1 line so we used the 23 Line T1 configuration and it seems it worked ok with the VG 7 demo version. The questions we have: 1) Do we have to configure the ring tone frequency for T1 lines like we had to for the analog service? or does the default setup should work? 2) Can we use the same WAV files we used with our old Dialogic boards 8-Mono with the new Dialogic board listed above and VG 7? Thank You Share this post Link to post
SupportTeam Report post Posted 03/31/2008 10:52 PM Please try the attached config file - just rename it to Config.xml and restart the VoiceGuide service. 1) Do we have to configure the ring tone frequency for T1 lines like we had to for the analog service? or does the default setup should work? You so not really need to con figure any tones for ISDN lines. That’s the great advantage of ISDN - ISDN network will send a special message on the D channel to immediately inform us when the calls is answered and when it is ended. The ConfigLine for ISDN (Sample ConfigLine for ISDN lines.xml) has some tones defined but this is mainly fax and international dial tones, which are never really used with ISDN unless dialing through elaborate international interconnections. Rename Sample ConfigLine for ISDN lines.xml to ConfigLine.xml. 2) Can we use the same WAV files we used with our old Dialogic boards 8-Mono with the new Dialogic board listed above and VG 7? Yes, you can, but we would recommend using ULaw files - that is the actual encoding used on the T1 lines in US, so the actual sound files will get digitally transmitted through the whole network without any re-encoding, resulting in a clearer sound. Which ISDN protocol is used on these T1 lines? Share this post Link to post
Guest newpop1 Report post Posted 04/01/2008 01:21 PM Which ISDN protocol is used on these T1 lines? We are using DMS100 We installed everything and ran into one problem: 1) After installing the AT&T natural voices CDs we found that we could not find the SPEECH icon under control panel in order to select the voice. The server does not have a sound card, do we need one or is there a different location where we select this under W2003 server? 2) How do we convert the WAV to Ulaw format? Thanks Share this post Link to post
SupportTeam Report post Posted 04/01/2008 07:04 PM we could not find the SPEECH icon under control panel in order to select the voice. In VoiceGuide v7 the SAPI voice selection is made in VG.INI file. From: http://www.voiceguide.com/vghelp/source/html/config_tts.htm : VoiceGuide v7 The default TTS voice is set in VG.INI, section [sAPI], field TTSEngine. eg: [sAPI] TTSEngine=Cepstral David-8kHz The server does not have a sound card Please try the above first. You may however need to have a sound card in order for the whole SAPI system to work. 2) How do we convert the WAV to Ulaw format? You can use SOX. Found two previous posts which show how to do this, the command line is a bit different between the two so I'll post them both here: You can use SOX ( from: sox.sourceforge.net ) to easily change format from PCM to A-Law or u-Law here is a line from a batch file which will do the conversion for all .WAV files in current directory and will place output in subdirectory voice_ULaw: FOR %%X IN (*.WAV) DO sox %%X -r 8000 -U -b -V -c 1 "voice_ULaw\%%X" for A-Law use: FOR %%X IN (*.WAV) DO sox %%X -r 8000 -A -b -V -c 1 "voice_ALaw\%%X" and: You can convert the sound files you have from PCM to ULaw or to ALaw using most sound editor programs. For easy batch conversion see the SOX app: http://sox.sourceforge.net/ The attached files were converted from supplied PCM original with SOX. Here is the command used in a batch file to do the conversion using SOX: FOR %%X IN (*.WAV) DO sox %%X -t au -r 8000 -U -b -c 1 "ULaw\%%X" FOR %%X IN (*.WAV) DO sox %%X -t au -r 8000 -A -b -c 1 "ALaw\%%X" Another batch converter can be found here: http://www.xrlly.com/audio-converter.htm Share this post Link to post
Guest newpop1 Report post Posted 04/02/2008 02:08 AM VoiceGuide v7 The default TTS voice is set in VG.INI, section [sAPI], field TTSEngine. eg: [sAPI] TTSEngine=Cepstral David-8kHz Quick question, AT&T Natural voices we bought has Mike and Crystal 16khz, I may have gotten the syntax wrong: [sAPI] TTSEngine=AT&T Natural Voices Crystal-16kHz Is the above correct? it did not work for me. Or because it is 16kHz won't work? It should right? Thank You Share this post Link to post
SupportTeam Report post Posted 04/02/2008 02:46 AM The ktTts trace lists the names of all TTS engines installed. Look in the ktTts trace log and use the name exactly as is listed there. As you are using a Windows 2003 Server you will need to ensure that the version of the TTS engine you have can run on "Server". Contact the supplier of TTS engine if the version you were supplied cannot work on "Server" versions of Windows. Share this post Link to post
Guest newpop1 Report post Posted 04/02/2008 03:52 AM What is the ktTts trace list? and how do I enable it so I can look at it? Thank You Share this post Link to post
SupportTeam Report post Posted 04/02/2008 04:27 AM Enable logging by setting the log levels to 10 in VG.INI as per below: [Log] VoiceGuide=10 CallLoader=0 VoicemailManager=0 EmailSender=0 ktTel=10 ktTts=10 Then restart the VoiceGuide Service. Trace files will be created in VG's \log\ subdirectory. Share this post Link to post
Guest newpop1 Report post Posted 04/02/2008 11:45 AM Here is what I got: 064148.890 ------------------------------------------------------------------------------ 064148.890 ktTtsSapi v2.0 064148.890 Mar 19 2008 12:16:04 064148.890 zsLogPath [g:\Program Files\VoiceGuide\log\] 064148.890 ------------------------------------------------------------------------------ 064148.906 ProcessAnyQueuedTTSJobs CreateThread call 064148.906 ProcessAnyQueuedTTSJobs CreateThread returned 064148.906 ProcessAnyQueuedTTSJobs thread started 064148.921 voice 0 is: [Microsoft Mary], ID=[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\MSMary] 064148.921 voice 1 is: [ATT DTNV 1.4 Mike16], ID=[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\ATT-DT-14-Mike16] 064148.921 voice 2 is: [ATT DTNV 1.4 Crystal16], ID=[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\ATT-DT-14-Crystal16] 064148.921 voice 3 is: [Microsoft Mike], ID=[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\MSMike] 064148.921 voice 4 is: [Microsoft Sam], ID=[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\MSSam] 064148.921 voice 5 is: [sample TTS Voice], ID=[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\SampleTTSVoice] If I want AT&T Crystal 16 should I make the entry look like this? TTSEngine=ATT DTNV 1.4 Crystal16 Share this post Link to post
SupportTeam Report post Posted 04/02/2008 10:42 PM If I want AT&T Crystal 16 should I make the entry look like this? TTSEngine=ATT DTNV 1.4 Crystal16 Yes. NB. Most systems use the 8 bit version of the TTS, not the 16 bit version. Share this post Link to post
Guest newpop1 Report post Posted 04/03/2008 03:01 AM When we bought AT&T NV 2 years ago, we could only get the 16mHz and worked fine with the dialogic board for 8 lines. 1) Now for our 23 line digital dialogic board you are saying we will need the server edition only? 2) By following the links to AT&T NV from your site, we got to wizzardsoftware but they do not list AT&T Server edition, they only have the developer edition listed in their website. Is there another place where we can get the 8mHz AT&T NV Server edition? Thank You Share this post Link to post
SupportTeam Report post Posted 04/03/2008 03:11 AM I suppose that as you were able to install the TTS then you already have a version which can run on the "Server" versions of Windows. I wasn't saying that the 16-bit version would not work, just that the 8 bit is sufficient as the telephone lines transmit voice information with an 8 bit resolution. 16 bit is fine. Share this post Link to post