This document collects information related to 2010 Spring DST for Cisco Unified Communications Manager (CUCM). For specific details on each issue refer to the associated hyperlink to Cisco Bug Toolkit, Cisco Software Center, or other appropriate resource.
Communications Manager (CUCM)
There are no major changes to version requirements from the Fall 2009 DST event.
Changes for time zones and DST in CUCM 7.1(3) and higher
In CUCM 7.1(3) timezone entries wtih a "*" are compatible with legacy phone loads. In this context legacy means any 3rd generation phones running firmware lower than 9.0(2). So, if you have CUCM 7.1(3) , time zones with a "*" next to them can be used with all your 3rd generation phones. Other time zones will work on these phones only if they have firmware 9.0(2) or higher. In CUCM 8.0 the "*" character changes to "‡".
2nd generation phones will work with all time zones available irrespective of the firmware they have.
CSCtc52241, clarify timezones for legacy /non-legacy phone loads
CSCtc81478, Timezone wrong on 3rd gen phones after upgrade from 5.1.3 to 7.1.3
DST updates are applied independent of CUCM software from version 7.1(3) onwards. So, you will not have to upgrade your CUCM to get DST updates. A separate DST update file will be provided if necessary. That upgrade file would be applied to all nodes in the cluster, not just the publisher. Please refer to the release notes or readme associated with a specific file for more details.
DST in United States
In the US time springs forward on March 14 2010 at 2:00 AM local time. If you have a DST issue, please check whether your CUCM version has the fix for CSCsy25150, CUCM is not sending Daylight Saving Time updates
* It is recommended to upgrade to a FCS version whenever possible. FCS versions are available in Software Center on Cisco.com. To obtain ES versions you must contact Cisco TAC.
* ES are cumulative. Any ES version higher than those mentioned above will include the fix.
The patch file ciscocm.dst_march_2009.cop.sgn provided in March 2009 only addressed the March 2009 spring forward. It does not properly address any subsequent time change and will actually cause inappropriate time changes. Any full CUCM upgrade performed after the install of that patch will effectively remove the patch.
Others with older versions need to appy the workaround. The workaround for Argentina (primary TZ currently affected) - place phones into Greenland TZ for the affected period
CSCtc85618, DST: Update CM for Argentina rescinding DST in 2009
Other DST issues
CSCsy33379, UCM is not sending DST updates on Friday, Saturday
Cisco Unified Wireless IP phone
7925, 7921 and 7920 phones rely entirely on the CUCM for their time. 2nd generation phones also do the same.3rd generation phones obtain the time zone information from CUCM and calculate its own time. So, if your CUCM is patched for CSCsy25150, then you should be good.
Good morning,on our company we are using the WebEx Room Kit and our client is using Google Meet for meeting.As we won't buy new meeting room devices to join in, which one is the way to use our existing WebEx hardware devices to join in? T...
Hello all,I've been digging through documentation but haven't so far found my answer, so I'm hoping someone can help me out. Is it normal to see multiple Jabber MRA user sessions in your expressway C? I ask this because I'm constantly seeing upw...
Hi,I am setup my B2B call, Incoming b2b call is working but outgoing call is not working.I am using my Endpoint EX90 to make a B2B call asCalling firstname.lastname@example.orgCalled email@example.comWhen dial from Ex90, it remains in connecting... state fo...
Hi all, We have an enterprise license sub for Webex Teams that is limited to around 700 core Webex users. We have around another 10000 staff that will be joining Meetings sporadically with the meetings still hosted by the Core users. ...
Hello,I need to create a around 20 Application users with diferent permissions. But I facing a problem, using BAT I can create the app users but I dont know how to configure the password. It has to be done manually after creating the users with BAT? ...