VoiceGuide IVR Software Main Page
Jump to content

Time Switch ERROR

Recommended Posts

Hello, because it does not validate the date in the module Time Switch
It's like there's no time and it takes from 00.00 to 23.59

Windows 10

image.png.5160876e89578c220b81495d19a67e83.png

image.png.0f7772d5d6a6cf1fb1c7c37b44c201fa.png

 

Br

 

Diego

Share this post


Link to post

Can you please post the full vgEngine trace from which the screenshot was taken. We can then better see what is happening on this system and advise.

Share this post


Link to post

Tested with current version of VoiceGuide and confirmed the time switch functionality behaving as expected. See trace excerpt below.

The trace screenshot posted suggests that you are running an pretty old release of VoiceGuide. Would recommend updating system to current version.

074116.922  17   5   1     2 state [test time] Time Switch [] |
074116.922  17   5   1     2       date/time is blank. will use current date/time.
074116.922  17   5   1     2       specified range (time only): 04:00:00-09:00:00 on WeTh
074116.922  17   5   1     2       "Th" in DaysSelected list. Proceed to time check.
074116.922  17   5   1     2       checking day/time range. range=240-540(4:00-9:00), TimeToCheck=461(7:41)
074116.922  17   5   1     2       result: [Thursday, September 17, 2020 7:41 AM] falls within [04:00:00-09:00:00 on WeTh]
074116.923  17   5   1     2       find_next_vgm module title is=[play 1] (trigger_used={TRUE})

Share this post


Link to post

Can you please post the full vgEngine trace from which the screenshot above was taken (the working system). We can then better see what is happening on this system and advise.

Share this post


Link to post

Looks like the two systems use a different callflow (.vgs) file.

Please post the .vgs callflow files used by both systems.

This looks to be an issue with the 'locale' not being the same on the machine that edited the script and on the machine that is running the script.

Setting the 'locale' to be the same on both the machines should resolve this issue. You may need to edit and save the script again to ensure the date/time saved in that script is in the format expected by VoiceGuide IVR service when it reads in the script.

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
×