Unity Connection greeting end time off by 1 hour

[CrowleyFleck]

I have a weird thing happening with Unity Connection.

I'm on ver 10.0.1.12900-2.

When a user sets an end date and time for an alternate greeting, the time that is read back by the system is one hour earlier than the time they enter on the phone.

If I enter an end date of tomorrow, and time of 10:00 AM, the system says "The greeting is set to expire tomorrow, at 9:00 AM", and it does expire at 9:00AM the next day.

My phone is in the same time zone as the server, and the time stamps on messages are correct. Servers all have the correct time/ntp config.

Any ideas what might cause this?

[Rob Huffman · Accepted solution]

Hi there,

I believe you may be hitting this 10.x bug;

Cheers!

Rob

Alt greeting end time config off 1 hour due to DST change

CSCur89579

https://tools.cisco.com/bugsearch/bug/CSCur89579

Symptom:
Alternate Greeting end time 1 hour off from what was configured via TUI.
This issue is dependent on Timezone. Reproduce only with DST affected timezone.

Conditions:
Unity Connection 10.x

Process:
sign in to CUC via TUI, update alt greeting. when scheduling end time and saving, the system will respond with time that is 1 hour off of what you entered. Alternate greeting config on GUI will match the incorrect time spoken by system

Workaround:
1) administrator may configure end time for alt greetings via a GUI.
2) if you using TUI, change your entered time by 1 hour to offset what the system will save it as.

[CrowleyFleck]

Good info, thanks!