[cisco-voip] 7960 firmware load P00306000400

[Candace Holman]

No, this isn't a problem here.  Also, I discovered that there are several 
7960's that have this problem.  Some of the phones still use the default 
load and some just won't downgrade to the default load.  If noone has 
seen/fixed this problem I guess I'll open a TAC ticket and report a bug or 
RMA them.

The reason this is a problem is that this load will not keep a correct 
clock synchronization with CM 3.3.3.

Candace

At 01:57 PM 11/24/2004, Mike Armstrong wrote:
>I had a similar problem, which turned out that I had updated phone 
>firmware loads in the CM Publisher OK, but neglected to update the 
>Subscriber. However, the phones were registered to the Subscriber, so when 
>they reset, they got the loads that were in the Subscriber.  I do remember 
>looking in the Subscriber System->Device Defaults and seeing the new loads 
>listed, and thinking that somehow the Subscriber had automagically updated 
>itself. Needless to say....
>
>Mike Armstrong
>UF/IFAS CREC
>
>>Date: Tue, 23 Nov 2004 15:43:59 -0500
>>From: Candace Holman <Candace_Holman at harvard.edu>
>>Subject: [cisco-voip] 7960 firmware load P00306000400
>>To: cisco-voip at puck.nether.net
>>Message-ID: <5.2.1.1.2.20041123153736.02a34720 at camail.harvard.edu>
>>Content-Type: text/plain; charset="us-ascii"; format=flowed
>>
>>I have a phone stuck with firmware load P00306000400 (6.0-3).  I set the
>>device record in CM (3.3.3) to force it to use P00305000400 (5.0-4) and it
>>will not pick up the older load on a reset.  There are no errors in the
>>status messages on the phone, and no tftp errors on the server.  Does
>>anyone know a workaround?
>>
>>Thanks,
>>
>>=====================================================================
>>Candace Holman
>
>_______________________________________________
>cisco-voip mailing list
>cisco-voip at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-voip