[cisco-voip] 7960 firmware load P00306000400

[Vandy Hamidi]

http://www.cisco.com/en/US/customer/products/sw/voicesw/ps4967/products_
upgrade_guides09186a008022a968.html


-----Original Message-----
From: Vandy Hamidi 
Sent: Thursday, December 02, 2004 4:58 PM
To: Vandy Hamidi; Mike Armstrong; cisco-voip at puck.nether.net; Candace
Holman
Subject: RE: [cisco-voip] 7960 firmware load P00306000400

Sorry, Found this on Cisco.com

Signed and Unsigned Images (Image Authentication) 
There are two types of images that are used on the Cisco IP Phone 7960
and 7940: signed and unsigned. Image authentication is done through
signed binary files. Signed images have a .sbn extension, while unsigned
images have a .bin extension. 

Image authentication requires that the binary image not be changed prior
to being loaded into the phone. Versions prior to 5.x accept unsigned
binary files. 

Version 5.x and later images accept only signed binary files, which
improves security on the Cisco IP Phone 7960 and 7940. However, the use
of signed binary files does not allow you to return to an earlier
software version. Once a Version 5.0 firmware image is installed, for
instance, regardless of protocol, it cannot be replaced with any
previous version. The firmware image can be replaced only with another
signed image 5.x or later. All versions prior to a Cisco IP Phone 7960
and 7940 Version 5.0 will not load onto the phone after it is installed.




-----Original Message-----
From: Vandy Hamidi 
Sent: Thursday, December 02, 2004 4:58 PM
To: 'Mike Armstrong'; cisco-voip at puck.nether.net; Candace Holman
Subject: RE: [cisco-voip] 7960 firmware load P00306000400

Found this on Cisco.com


-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Mike Armstrong
Sent: Wednesday, November 24, 2004 1:21 PM
To: cisco-voip at puck.nether.net; Candace Holman
Subject: Re: [cisco-voip] 7960 firmware load P00306000400

Did you try to go the other way -- i.e., upgrade to P00306000500?
That's 
what I'm running, and the time seems to be synched OK.  Of course, there
may 
be other problems, but none that seem to affect us.

mike
----- Original Message ----- 
From: "Candace Holman" <Candace_Holman at harvard.edu>
To: "Mike Armstrong" <mfa at crec.ifas.ufl.edu>;
<cisco-voip at puck.nether.net>
Sent: Wednesday, November 24, 2004 3:08 PM
Subject: Re: [cisco-voip] 7960 firmware load P00306000400


> 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
> 

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip