Did your DST rollforward work?

Published: 2009-03-09
Last Updated: 2009-03-09 22:07:42 UTC
by Joel Esler (Version: 4)
0 comment(s)

If you have a Cisco IP phone, your DST rollfoward may not have worked, so you might want to rely on a different clock until the issues gets fixed.

Update:  This only affects the Linux version of the Cisco CallManager.

Reader Steven (Thanks Steven) to tell us about an issue with Cisco IP phones.  Specifically  Cisco IP Phone Models: 7905, 7910, 7912, 7920, 7921, 7935, 7936, 7937, 7940, 7960.

There are three work arounds if you are affected by this issue according to Cisco:

Workaround #1:
Do nothing and wait for time to automatically correct on March 15.

Workaround #2:
Apply a temporary configuration workaround. Note this workaround will have to be removed when system is patched or after March 15, whichever comes first.
a. Using CUCM Admin go to: System---Date / Time Group
b. Create new Date / Time group with one hour extra of local time.
c. Go to System --- Device pool
d. Create a New Device pool and assign the (one hour extra Date time
group) to this device pool.
e. Assign the new Device pool to and Cisco IP Phones that are displaying
the incorrect time.
f. use BAT or BPS to apply to specific groups based on (devicemodel,currentdevicepool).
Remember, this change will have to be backed out after patching the system or after March 15, whichever comes first.

Workaround #3:
Apply a patch to be released by Cisco. Updates coming soon.

I would publish a link to Cisco's bug database, but apparently it's offline right now.

Update 2:  Soon after I published this, Cisco published a patch to fix the issue.

Not necessarily security related, but it might affect when you go home today!

-- Joel Esler http://www.joelesler.net

0 comment(s)


Diary Archives