[Asterisk-Users] RE: Cisco 7960G phone crashes during SIP upgrade
Adi Linden
adil at adis.on.ca
Thu Feb 3 09:08:08 MST 2005
I can confirm that the Cisco instruction for installing/upgrading to the
7.3 SIP image do not work. When I originally installed SIP on some brand
new phones Cisco TAC indicated that a phone has to run 6.3 before it can
be upgraded to 7.3.
Loading the 6.3 SIP image has been a success. I've had no problems
switching between 6.3 SIP and various SCCP images back and forth.
I might try your suggested method to get up to the 7.3 SIP image.
However, it doesn't sound like a hassle free method of loading SIP at all.
I'd much prefer if I could tell the phone via the dhcp server to load from
tftp server x.x.x.x and automatically loads SIP or load from tftp server
y.y.y.y and automatically load SCCP (where x.x.x.x is Asterisk and y.y.y.y
is Cisco CCM).
Adi
On Thu, 3 Feb 2005, Gene Willingham wrote:
> I found the phones to be very flaky.
>
> Make SURE:
>
> 1. The txt files are unix txt files. NO CR/LF at end of line. If you edit
> the files on a PC use wordpad only. If you use Notepad they will ADD extra
> characters that causes the phone to reject the files. Do not save them as
> Unicode text files, this is cause it to fail as well.
>
> 2. The 7.x SIP image is not a full image, you have to start with 6.3 or
> 6.0. I have had success starting with 6.3 on some phones, but others
> required me to start with 6.0
>
> 3. Upgrade path 6.0 > 6.3 > 7.3
>
> 4. The 7.3 upgrade fails because the directions on how to upgrade are
> wrong. Try this.
>
> a. Edit OS79XX.TXT and put P003-07-3-00 as image name
> b. Edit SIPDefault.txt and put image name as P003-07-3-00
>
> Reboot the phone.
>
> The phone will upgrade the universal loader application, then fail
> on loading the 7.3 application w/ a "Protocol Application Invalid" error.
> DO NOT UNPLUG THE PHONE:
>
> c. Now Edit SIPDefault.txt and change image name to P0S3-07-3-00
>
> When the phone reboots by itself, it will upgrade the SIP image to
> 7.3 and hopefully you are done. I have found with no explanation that
> sometimes the phone will take multiple reboot with errors before it will
> work. Cisco says there is a "Checklist" of things it is looking for.
> Apparently this checklist progresses from each successive reboot. If you
> unplug the phone all you are doing is starting over again. Be patient it
> could take 20 - 30 minutes for each phone.
>
> I am not an expert, I have successfully upgraded 20 phones. This was the
> best I could figure out through trial and error.
>
> If you get a checksum error on the SIP 6.3 image, the problem is with your
> config files not the image.
>
> Good luck. I have found upgrading polycoms easier. Found the phone quality
> to be very good. They have a bug in their 1.3 image that affects phone to
> phone dialing on the polycom. That appears to have gone away when I
> upgraded to 1.4
>
> Gene
>
>
> ------------------------------
>
> Message: 8
> Date: Thu, 3 Feb 2005 13:18:28 +0000
> From: Nicolas Chabbey <epromix at gmail.com>
> Subject: [Asterisk-Users] Cisco 7960G phone crashes during SIP upgrade
> To: asterisk-users at lists.digium.com
> Message-ID: <afc676250502030518274c0f22 at mail.gmail.com>
> Content-Type: text/plain; charset=US-ASCII
>
> Hello,
>
> I've recently received a Cisco 7960G phone with the factory default
> SCCP firmware on it.
> As we're using SIP on our network, the first things i've done was to
> upgrade but unfortunately the phone just restarted. By looking on the
> TFTP logs and tcpump output, i've seen that the phone crashed and
> restarted just after downloading the OS79XX.TXT file, without
> requesting the image file at any moment.
>
> If i'm putting a SCCP image file name (without ext.) on the OS79XX.TXT
> (begining with P003), the phone doesn't crash and request the
> respective SEP<mac>.xml file. Unfortunately (again), just after
> downloading the xml configuration it hang and restart. I've checked
> the syntax and they's no error on it, if they's one the phone output
> the error on the display without crashing. Note that i've both put
> with and without the load information statement, with the same result.
>
> Both statical and DHCP configuration has been tried.
> Maybe it's an hardware failure or i've miss somethings realy important :)
>
> Thanks
>
>
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
More information about the asterisk-users
mailing list