I'm having an issue with a custom auto-attendant script for Unity Express 8.6.6.
A brief overview of the expected call flow:
My first version had a Business Hours object, with a schedule parameter set so that the schedule could be chosen in the CUE GUI. This script did not appear to work properly, as the AfterHours option was always selected by the script. My current version removed this object and replaced it with manual Time-and-Day objects, but the same behavior as above occurs – the AfterHours option is always selected.
Both scripts validated in the editor, and the CUE has been rebooted since the script was first uploaded. TAC validated that nothing in the "show run" is causing CUE to ignore the time-and-day checks. I've attached a ZIP file that contains the scripts, "show software version" and "show license status application" output.
Am I missing anything?
did you create the time-range trigger on the cue ?
Thank you for replying.
I believe I have implemented the proper triggers for the script, but I am not certain - the information for creating these scripts has eluded me, and I have mostly deconstructed sample scripts to get what I have here.
This is the original script. The Call Redirects for MainMenu and AfterHours have only the End object in them, so I left them collapsed. This script has a parameter to choose which schedule to use within the Unity Express GUI.
This is the new script, where I deleted the Business Hours check and made an explicit time of day check. The rest of the script remains the same, so I did not include it in this screencap.
You'll want to grab a trace--take a look at the branching it is/isn't taking as well as the actual day/time on the CUE.
I read through the document, and it says that the atrace.log file that is generated is not cleartext. Is there any application I can use to read the traces I generate?
EDIT: Apologies, it appears this documentation needs to be rewritten. I was looking at the process to enable traces on an AIM module, when our Unity Express module is on an Internal Services Module 300. I issued "show trace buffer trail" and placed a test call, and this is what I see:
It appears as though the script engine is seeing the Day of Week object, acknowledging it without somehow doing anything with it, and then choosing a "goto AfterHours" step within that object and playing that prompt, which is consistent with the behavior we're seeing.
It looks to me like the module thinks its 05/25, which would be a Sunday/weekend (at least in 2014). Can you check the date/time of the module?
There was a problem with NTP; the server we were synchronizing to went offline. NTP is working and the server shows the proper time, but the issue continues to occur.
Any other thoughts?
Could we get an updated trace with the new date/time? It looked like it was behaving correctly considering the date/time last time, so maybe its failing elsewhere now.