VoiceGuide IVR Software Main Page
Jump to content

Saytime Problem

Recommended Posts

Hello,

 

I encountered a problem and it's quite bothering. The problems seems that if it's before 9 O'clock, the say time program doesn't say time at all. (I thought it's not good before 12. But it's OK after 10am.) But from 12-13, it always says 'twelve AM', which should be 'twelve PM'. After 1PM the program is doing OK.

 

Please look at the following log:

 

095707.27 5 state [sayCurrentDateTime] Say numbers: 10/3/2008 9:56:53 AM as Date & Time - SQL Long Date & Time

095707.27 5 fn PlaySoundStartNumbers [C:\toa\ugivoice\UGI_Callout_Voice\TimeIsNow3.wav],[],[10/3/2008 9:56:53 AM],Date & Time - SQL Long Date & Time

095707.27 5 sVbsFunctionToUse=DateTimeSQLLongDateTime

095707.27 5 say numbers vbs ran shell[wscript "C:\Program Files\VoiceGuide\temp\vbs_5_081003095707_SayNumberA.vbs" //I //T:60]

095707.27 5 vbs replaced rv and ran shell[wscript "C:\Program Files\VoiceGuide\temp\vbs_5_081003095707_SayNumberB.vbs" //I //T:3600]

095707.30 5 VBScript started [wscript "C:\Program Files\VoiceGuide\temp\vbs_5_081003095707_SayNumberB.vbs" //I //T:3600]

095707.30 5 started SayNumber VBScript (C:\Program Files\VoiceGuide\temp\vbs_5_081003095707_SayNumberA.vbs)

095707.33 5 cl Play_Start C:\toa\ugivoice\UGI_Callout_Voice\TimeIsNow3.wav,month10.wav,place03.wav,

 

This is for bad one. The following is a better one, but is should say 'PM' instead of 'AM'

 

120551.45 5 state [sayCurrentDateTime] Say numbers: 10/2/2008 12:05:36 PM as Date & Time - SQL Long Date & Time

120551.45 5 fn PlaySoundStartNumbers [C:\toa\ugivoice\UGI_Callout_Voice\TimeIsNow3.wav],[],[10/2/2008 12:05:36 PM],Date & Time - SQL Long Date & Time

120551.45 5 sVbsFunctionToUse=DateTimeSQLLongDateTime

120551.45 5 say numbers vbs ran shell[wscript "C:\Program Files\VoiceGuide\temp\vbs_5_081002120551_SayNumberA.vbs" //I //T:60]

120551.47 5 vbs replaced rv and ran shell[wscript "C:\Program Files\VoiceGuide\temp\vbs_5_081002120551_SayNumberB.vbs" //I //T:3600]

120551.50 5 VBScript started [wscript "C:\Program Files\VoiceGuide\temp\vbs_5_081002120551_SayNumberB.vbs" //I //T:3600]

120551.50 5 started SayNumber VBScript (C:\Program Files\VoiceGuide\temp\vbs_5_081002120551_SayNumberA.vbs)

120551.52 5 cl Play_Start C:\toa\ugivoice\UGI_Callout_Voice\TimeIsNow3.wav,month10.wav,place02.wav,12.wav,0.wav,5.wav,am.wav

 

The following is the vbs_5_081003095707_SayNumberA.vbs's calling part.

Set vg = CreateObject("VoiceGuide.CommandLink")

sWavList=DateTimeSQLLongDateTime("10/3/2008 9:56:53 AM")

sWavList="C:\toa\ugivoice\UGI_Callout_Voice\TimeIsNow3.wav," & sWavList

vg.Play_Start 5, sWavList

Set vg = Nothing

 

By the way why there are sayNumberA and sayNumberB two script?

 

If any other information is needed, please let me know.

 

Thanks for your help.

 

 

Ronghui

Share this post


Link to post

Which version of VoiceGuide are you using?

 

This does not look like a trace from version 7

Share this post


Link to post

I am using VoiceGuide V6.0.3003. Actually I just downloaded and installed the V6.0.3386. But the script tool's version is still V6.0.3003. So they may not be same?

Share this post


Link to post

We'd recommend to just use v7 of VoiceGuide. v7 has a new much better way of performing the Say Numbers/Dates/Time/etc. (and has many other improvements over v6).

 

v6 has reached 'end of life' and there will be no more updates published for it and no testing is carried out here on v6 systems anymore.

 

If you want to use v6 then you will need to debug what is happening in the sayNumberB script and then change the lib_num2wav.vbs file accordingly. More information is at bottom of this page: http://www.voiceguide.com/vghelp/source/ht...odsaynumber.htm

Share this post


Link to post

Thanks for telling me where to change. I fixed it. By the way, do we have to repurchase license if upgrading from V6 to V7?

 

Ronghui

Share this post


Link to post
do we have to repurchase license if upgrading from V6 to V7?

Yes. You do get some credit for v6 license though.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×