Announcing the UC320W 2.3 Release Candidate firmware

Question

UPDATE: 
General availability release announcement can be found here: 
https://supportforums.cisco.com/thread/2173943
WHAT:
Today  we are announcing the release of the Cisco UC320W 2.3.1 Release Candidate firmware feature release. Release Candidate quality means that is has gone through Cisco’s internal testing, but there might be a few new issues that surface in real world deployments.  Partners are encouraged to test the firmware in their labs before deploying on their customers systems.  Installation instructions, features and bug fixes are described in the 2.3.1 release notes below.
NOTE: The open source tar file will not be available upon request because this is an RC release.  Proceed with the installation of this firmware only if you agree with these terms and conditions.
WHEN:
The 2.3.1 firmware version is available via the Cloud now by using the attached Platform Modification File (PMF).   This firmware will not be posted on CCO.  A General Availability release will be made available at a later date.
HOW:
Installation:
Perform a system backup of the UC320W before loading the PMF file.
Download the PMF and save to your PC.
Unzip the PMF file.
Launch and log into the UC320W Configuration Utility.
Click on the Status option at the top.
Click on Devices submenu.
Click on Alter PMFs button.
Click Add PMF from your PC button, select the unzipped file and install.
Click Done to close the dialog.
NOTE:  If  you are on a release version lower than 2.1.2, please see this  discussion for more information and a workaround for the Adobe Flash  Player version 11 compatibility issue:
https://supportforums.cisco.com/thread/2112911
Release Notes can be found here:  >>> LINK <<<
Any problems found on the Release Candidate firmware should be reported  immediately to the Cisco Small Business Customer Support Center.  When calling the SBCS please indicate that you  are a Release Candidate participant and specify the firmware version  found on the UC320W Configuration Utility login or About screen as well as your Region.

Answer 1

Randy,
Thank you for getting back to me - much appreciated.
This is why I think it's a bug. Time is set correctly as well as the time zone, but the system still won't transition from night to day. Perhaps you can duplicate my scenario in your enviornment -I have a unique customer requirement for this feature which may be triggering this issue (but nevertheless I still feel it's a bug becuase it's not behaving as expected) The customer needs to be 'day' 24x7 except for Thursdays between 8:30am-4:30pm where this is 'night'. In order to test this configuration functionality I set the current day (in this case it was Saturday 9/16) to be 'night'. What I found that it did indeed set the mode to 'night' - however when I reverted back to the desired schedule (turned Saturday back to 'day' the night mode wouldn't switch back, even though I set back Saturday to be 'day'. If I disabled night/day mode it would go back to day, but when I put it back to the day/nigh schedule (with the desired schedule) - it would go back to 'night' mode incorrectly as Saturday was scheduled as 'day'. I then enabled the force night button on one of the phones which (correct me if I'm wrong) should allow me to toggle the modes. In corresponding with the mode, the phone button indicated amber, but when I pressed it it would turn green, but the Status -> Devices would still show that 'night' mode was still on. I also confirmed that it wasn't an error in display, when it was in 'night' mode it would behave as such with the corresponding call routing rules in place.
I hope this makes sense - I would welcome you to take a look at the system but I need to arrange this with my customer.
Regards,
Ed Tsai