[cisco-voip] SCCP Firmware Upgrade Question

[Lelio Fulgenzi]

I believe device packs are handled differently are they not? They update the 
database with new entries in the pull down menus, so they have to be done on 
the publisher and then files extracted on the TFTP server.

Lelio
--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Java-Clavis-Domus Theorem: The ability to keep your hands on the home keys 
is inversely
related to the amount of caffeine ingested in the last 30 minutes.

----- Original Message ----- 
From: "Ryan Ratliff" <rratliff at cisco.com>
To: "Robert Kulagowski" <rkulagow at gmail.com>
Cc: <cisco-voip at puck.nether.net>; "STEVEN CASPER" <SCASPER at mtb.com>
Sent: Tuesday, March 25, 2008 9:34 AM
Subject: Re: [cisco-voip] SCCP Firmware Upgrade Question


> Correct, however since any sub has the potential to be a TFTP server
> it doesn't hurt to get the files propagated everywhere.
>
> -Ryan
>
> On Mar 25, 2008, at 9:06 AM, Robert Kulagowski wrote:
>
> STEVEN CASPER wrote:
>>  When upgrading firmware on Call Manager 4.1.3 for a SCCP phone
>> load the
>> install document directs you to download and run the SCCP .exe
>> file. Is
>> this done on the Publisher only or does it need to be done on every
>> Call
>> Manager server?
>
> Technically speaking, doesn't it just need to be installed on the pub
> and on the TFTP server?
>
> The install on the pub is done so that the device defaults page gets
> updated with whatever firmware you're installing.
> _______________________________________________
> 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
>