[cisco-voip] 7960 firmware load P00306000400

[Wes Sisk]

ccmadmin shows what is in the database of the publisher callmanager. 
even if pub is down, the SQL database is replicated down to the 
subscribers.  Problems can arise if you put a new device load in the 
TFTPPath directory of the publisher, but your DHCP option 150 points to 
a subscriber (or if you use CiscoCM1 pointing to the sub or any of the 
other TFTP resolution methods).

/Wes

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