Multi Language Number Speaking - Different Logic

[Zoltan]

I could almost succesfully implement using English and Chinese by using DIRSYSTEMVOICE result variable. However, in the Speak number module I want VG to say the number – but the logic of the two languages to interpret the number is different. E.g 123456 – Chinese says: Twelve_TenThousand_ThreeThousand_FourHundred_FiveTen_Six

 

I know I need to modify lib_num2wav script for the Chinese– but I need English and Chinese at the same time.

 

As I can create 2 system voice folders for the two languages, I should be able to create two system folders or two lib_num2wav files – one for each language or some conditions inside lib_num2wav. What is the solution? So if the caller chooses English, they hear the number in English language and English way of saying numbers; if they choose Chinese they hear it in Chinese language and in Chinese logic. I have already have the necessary sound files.

[Zoltan]

I tried to modify the lib_num2wav file by adding a condition with a result variable:

If $RV[Language] = 1 Then

...

End if

 

Also tried "$RV[Language]". Either there was an error during the call or the module said "zero" instead of the number.

 

The $RV[Language] variable worked well in VG modules but I cannot use it in the lib_num2wav file.

So how can i manage the different algoritm in different languages?

[SupportTeam]

Editing lib_num2wav.vbs is the right approach.

 

Are you setting $RV[Language] in a script before running the SayNumbers module?

 

Have you tried:

 

If "$RV[Language]" = "1" Then

[Zoltan]

Are you setting $RV[Language] in a script before running the SayNumbers module?

 

Have you tried:

 

If "$RV[Language]" = "1" Then

 

Yes I defined $RV[Language] earlier in the script and the speak number module works well in English if I do not place

If "$RV[Language]" = "1" Then etc. inside the lib_num2wav file - that is, if I use the original file.

 

The problem is that $RV[Language] is not replaced by the actual number in the lib_num2wav file!!!

I have checked the automatically created vbs_4_SayNumber vbscript file in C:\Program Files\VoiceGuide\data and it shows no replacement.

 

The result variables are replaced correctly in every module but not in the lib_num2wav file.

If I omit the " " around the result variable then the script gives error because of the $ sign.

 

I suspect that it is the VG software problem. Haven't you forgotten to provide the result variable replacement in lib_num2wav file???? Just test it!

When I use the VBscript for creating the Chinese wav files in a VBS module + Play file module both the Chinese and English works well.

[SupportTeam]

Enable logging by setting the log levels to 10 in VG.INI as per below:

[Log]

 

VoiceGuide=10

NumberLoader=0

VoicemailManager=0

EmailSender=0

TapiWrapOcx=0

SapiWrapOcx=0

Then restart VG and make a test call which demonstrates the problem.

 

Debug Trace files will be created in VG's \log\ subdirectory.

 

Please post the traces and the VoiceGuide script used as well as the vbs_4_SayNumber vbscript file and your modified lib_num2wav file.

 

When posting traces/scripts please .ZIP them up and post them as attachments.

[Zoltan]

I have attached all the files.

Language.zip

[SupportTeam]

Please update system with attached .exe and post vgm trace if you still encounter issues.

VgMulti_6.0.3118.zip

[Zoltan]

A few times it worked but most of the times it freezed VG or the line hung up when it should say the number.

It created 2 files: vbs_3_rr_SayNumber and vbs_3_SayNumber. All attached.

vgm0623.zip

[SupportTeam]

The attached new version should fix the problem you encountered.

 

To update to new versions do:

 

1. stop VG

 

2. run in C:\Windows\System32\ (at command prompt):

 

regsvr32 -u ktTelControl.ocx

 

3. make backup of ktTelControl.ocx (onto a floppy or other machine on

network - do not just rename it)

 

4. copy new ktTelControl.ocx to C:\Windows\System32\

 

5. run in C:\Windows\System32\ (at command prompt):

 

regsvr32 ktTelControl.ocx

 

6. copy new VgMulti.exe to VG's directory. (make backup first).

 

Now you can run the test calls again.

vg_6.0.0.3120.zip