Guest

Preview Tool

Cisco Bug: CSCuq99408 - ICS file sent with confirmation E-mail doesn't carry correct DST informa

Last Modified

Jun 10, 2015

Products (1)

  • Cisco TelePresence Management Server

Known Affected Releases

14.4 14.4.1 14.4.2 14.5

Description (partial)

Symptom:
When viewing a icalendar attachment provided for a conference scheduled through TMS, the meeting time shown is off by an hour for meetings on specific dates.  The meeting shows correctly in the TMS web interface and when viewed in the client's calendar after saving the icalendar attachment.  The variation can be confirmed by viewing the icalendar attachment in a text editor and seeing the  RRULE entry for the timezones having the wrong rules for when DST changes.

Conditions:
- Conference must have been saved in TMS v14.4 or newer
- Meeting must be a single instance meeting
- The timezone for the conference must be one where where Windows has updated revisions of the Daylight Savings time zone rules (timezones whose DST rules have changed after 2003)
- The meeting's date must fall on a date in between the old DST and new DST changeover dates.  The specific date range impacted is specific to the conference timezone scheduled for the meeting.

Example:  For a meeting scheduled in the Australian Eastern Standard time zone, the .ics attachment shows DST starting Oct 5, but the actual DST changeover date is Oct 26th.  The .ics attachment created for single instance meetings scheduled to run between Oct 5 and Oct 26th will show the meeting time off by 1hr.

- The actual times for the meeting will be saved correctly in TMS and the meeting will execute at the correct time - only views where clients view the iCalendar attachment in the timezone rules of the attachment will display the incorrect time.  Clients that view the meeting in the client's timezone, will display the meeting at the correct time.  Example: Outlook 2010 will display the time accurately when viewing the entry in the calendar.

List of Timezones that Windows has multiple revisions of the DST rules defined (Dynamic DST) which put them at risk for this defect:
	Alaskan Standard Time
	Arabic Standard Time
	Argentina Standard Time
	Atlantic Standard Time
	AUS Eastern Standard Time
	Azores Standard Time
	Bahia Standard Time
	Bangladesh Standard Time
	Caucasus Standard Time
	Cen. Australia Standard Time
	Central Brazilian Standard Time
	Central Standard Time
	E. South America Standard Time
	Eastern Standard Time
	Egypt Standard Time
	Ekaterinburg Standard Time
	Fiji Standard Time
	Greenland Standard Time
	Iran Standard Time
	Israel Standard Time
	Jordan Standard Time
	Kaliningrad Standard Time
	Libya Standard Time
	Magadan Standard Time
	Mauritius Standard Time
	Middle East Standard Time
	Montevideo Standard Time
	Morocco Standard Time
	Mountain Standard Time
	N. Central Asia Standard Time
	Namibia Standard Time
	New Zealand Standard Time
	Newfoundland Standard Time
	North Asia East Standard Time
	North Asia Standard Time
	Pacific SA Standard Time
	Pacific Standard Time
	Pakistan Standard Time
	Paraguay Standard Time
	Russian Standard Time
	Samoa Standard Time
	Syria Standard Time
	Tasmania Standard Time
	Turkey Standard Time
	US Eastern Standard Time
	Venezuela Standard Time
	Vladivostok Standard Time
	W. Australia Standard Time
	Yakutsk Standard Time
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.