Field Notice: FN74449 - Cisco Unified Contact Center Solutions Daylight Saving Time Updates For Canadian Regions - Workaround Provided

British Columbia has deprecated standard time and adopted daylight saving time permanently, with new time rules taking effect on March 8, 2026, at 2:00 a.m. local time. This means there will not be time adjustments going forward and the previously scheduled adjustment back to standard time on November 1, 2026, is no longer valid. Canada-wide daylight standard time ends (excluding in British Columbia). Clocks move back one hour. Systems that have not been updated with the new British Columbia time rules will exhibit a one-hour time clock offset until they are patched.

Cisco Unified Contact Center Enterprise (Unified CCE), Cisco Packaged Contact Center Enterprise (Packaged CCE), and Cisco Unified Contact Center Express (Unified CCX) rely on the underlying Windows operating system and Java time zone (tzdata) databases to drive time-of-day call routing scripts, agent scheduling, callback scheduling, and both historical and real-time reporting. These time zone definitions must be updated to reflect the permanent transitioning of British Columbia to Pacific Time and to ensure that the standard 2026 daylight saving time start (March 8) and end (November 1) dates are correctly observed elsewhere in Canada. Deployments that are running without an updated time zone database will calculate local time incorrectly for affected regions.

Unified Contact Center Solutions Windows-based components, such as the Unified CCE Router, Logger, and Admin Workstation (AW) servers, require the applicable Microsoft time zone update.

Cisco Voice Operating System (VOS) based components, such as Cisco Unified CCX, Cisco Cloud Connect, Cisco Customer Collaboration Platform (CCP), Cisco Finesse, Cisco Identity Service, Cisco Unified Intelligence Center, and Cisco Virtualized Voice Browser, require the DST COP 2026 file to be applied.

On November 28, 2019, British Columbia passed Bill 40, 4th Session, 41st Leg the Interpretation Amendment Act repealing Section 26 of the Interpretation Act, R.S.B.C. 1996, c.238, making daylight saving time permanent provided neighboring states and provinces also converted. British Columbia’s Order in Council 63/2026 removed the neighboring states clause and enacted permanent daylight saving time after the March 8, 2026, time change.

This change will eliminate further references to Pacific Standard Time and Pacific Daylight Saving Time, substituting Pacific Time. Pacific Time means seven hours behind Coordinated Universal Time (UTC).

These changes affect any deployment of Cisco CCP, Cisco Packaged CCE, Cisco Unified CCE, and Cisco Unified CCX that schedules agents, routes calls by time of day, or reports on call data using the affected Canadian time zones. Customers who are operating components for these products or serving these regions should verify that their underlying operating system and application time zone definitions are current.

If the required time zone updates are not applied, customers who are running components of Cisco CCP, Cisco Packaged CCE, Cisco Unified CCE, and Cisco Unified CCX that are serving Canadian users may experience the following problems:

• Time-of-day call routing scripts that are executing one hour early or late for British Columbia callers after November 1, 2026
• Agent schedules, callback requests, and skill-group business hours that are misaligned with actual local time
• Historical and real-time reporting timestamps that do not match true local time for affected sites

Workaround

To ensure that Cisco CCP, Cisco Packaged CCE, Cisco Unified CCE, and Cisco Unified CCX components calculate Canadian local time correctly following the 2026 daylight saving time changes, customers can take the following steps:  

For Cisco Unified Contact Center Solution VOS-based components (Cisco Unified Intelligence Center, Cisco Finesse, Cisco Identity Service, Cisco Cloud Connect, Cisco Virtualized Voice Browser, Cisco CCP and Cisco CXP release(s) 12.5(X) and 12.6(X), administrators can use the following CLI command to manually set the system to the correct UTC offset: 

Alberta: use show timezone to select timezone 344 – Etc/GMT-6 or timezone 173 – America/Regina. Apply with set timezone 344 or set timezone 173. 

Note: For Cisco Unified CCE and Unified CCX Release 15.0(X), there is no manual workaround. See the Solution section for instructions.  

For Cisco Unified Contact Center Solution Windows-based components such as Router, Logger, PG, and AW for Intelligent Contact Management (ICM) and Cisco Unified Customer Voice Portal- (Unified CVP) based components (such as OAMP and Reporting Server), see the following Solution section.

Solution

For Unified Contact Center Solution 15.0(X) VOS-based components (Cisco Unified Intelligence Center, Cisco Finesse, Cisco Identity Service, Cisco Cloud Connect, Cisco Virtualized Voice Browser, Cisco CCP and Cisco CXP), apply the following DST COP 2026c files. 

• Unified CCE: DST 2026c TZData Update cop ucos.dst-updater.2026c-el8_10-00.15.0.1.cop.sha512
• Unified CCX: DST 2026c TZData Update cop ucos.dst-updater.2026c-el8_10-00.15.0.1.cop.sha512
• Unified Intelligence Center: DST 2026c TZData Update cop ucos.dst-updater.2026c-el8_10-00.15.0.1.cop.sha512

For Windows-based components, apply time zone updates as explained in the following steps:

1. On the Cisco Unified CCE AW server, do the following:
   a. Download the updated Region_Prefix_Data.txt file and replace the outdated file located at c:\icm\bin\Region_Prefix_Data.txt.
   b. Run c:\icm\bin\RegionFix.exe to update the region prefixes. For instructions on running RegionFix.exe, see the Outbound Option Guide for Unified Contact Center Enterprise.
   c. Validate the updated region(s) using Configuration Manager by logging on to the Cisco Unified CCE AW server, and from the Start menu, choosing All Programs > Cisco Unified CCE Tools > Administration Tools > Configuration Manager > Explorer Tools > Region Explorer.
2. Apply the latest Microsoft Windows time zone update and, where applicable, the corresponding Java Runtime Environment (JRE) time zone (tzdata) update to all Windows-based Cisco Unified CCE and Packaged CCE servers (such as Router, Logger, and AW) and agent desktops that are operating in or serving Canadian time zones. For reference, see the following articles:
   • Microsoft Interim guidance for Alberta permanent DST 2026 
   • Microsoft Interim guidance for British Columbia time zone changes 2026 
   • Microsoft Interim guidance for Manitoba permanent DST 2026 

3. Apply the latest Microsoft Windows time zone update and, where applicable, the corresponding Java Runtime Environment (JRE) time zone (tzdata) update to Windows-based CVP Servers, which include OAMP, CVP, and Reporting Server.

Note: COP files for Cisco Unified Intelligence Center Software Release 12.6(2) ES09 and Cisco Unified CCX Software Release 12.5(1) SU3 ES09 will be delivered to address the daylight saving time changes. This field notice will be updated once the COP files are available.

Post-Update Verification Actions 

After the time zone updates have been applied, perform the following steps: 

1. Verify server time zone settings: Confirm that each Cisco CCP, Packaged CCE, Unified CCE, and Unified CCX server reflects the correct time zone (such as Pacific Time for British Columbia) and that the system clock displays the correct local time.
2. Validate time-of-day scripts and schedules: Review ICM or CCE routing scripts, agent schedules, and callback or skill-group business hours that reference British Columbia or other affected time zones to confirm they execute at the intended local time.
3. Confirm reporting accuracy: Check historical and real-time reporting data spanning the March 8, 2026, and November 1, 2026, transition dates to confirm that timestamps align with the correct local time, and re-run or annotate any reports generated during the transition window.
4. Verify server time zone settings: Confirm that the CVP Reporting Server reflects the correct time zone (such as Pacific Time for British Columbia) and that the system clock displays the correct local time.
5. Verify in the CVP Reporting Server database: Check that the data and time fields of the call table reflect as expected.