asterisk users - Oct 2003 - 7940/60 TFTP Problem

> -----Original Message-----
> From: Babak Pasdar [mailto:bpasdar@IGXGlobal.com]
> 
> I was wondering if anyone else has had this problem.  I have purchused
> several Cisco 7940 and 7960 phones.  Of the 5 phones so far I have run
> accross 2 that that give me malformed TFTP and refuse to upgrade to
the
> latest version of SIP code -- 5.3.  In fact some of the other phones
also
> give malformed packets do this but they seem to work OK.  The ones
giving
> me the problem when looking in ethereal are misiing part of the
filename
> to get it upgraded to SIP.
Babak,

Try a staged upgrade, especially is upgrading from a really old
firmware. I.e., in OS79XX.TXT place an intermediate SIP image and then
in SIPDefault.cnf put the image you wish to ultimately upgrade to.
Here's my current files:

[me@here tftpboot]# more OS79XX.TXT
P0S30202

[me@here tftpboot]# more SIPDefault.cnf
image_version:P0S3-04-4-00
proxy1_address: xx.xx.xx.xx
tftp_cfg_dir: /configs/cisco7900/
proxy_register : 1

Phone starts off at Skinny 2.x, then upgrades to SIP 2.2 then to SIP
4.4. 4.4 could be assumably replaced by 5.3....

HTH,

--- Gavin

OK, I got it figured out. Here is the process to fix this problem in the future.

The key here on MGCP phones was to recognize that they only understand the 8.3
naming format until a few revs up.  What seemed like corruption was the Cisco
phones inability to understand bigger than 8.3 names, such as what Cisco uses
for the SIP images.

Here is the step-by-step:

1. Upgrade to a newer version of the MGCP code.

I went to: P0M3-03-0-00.bin

However this does not work out of the box,I had to copy the file to P0M30300.bin
to adhere to the 8.3 name standard.

Modify the OS79XX.TXT to say only the following:

P0M30300

This process apparently reorganizes the image memory mapping on the phone to
make room for the larger image to come.

2. Once the upgrade is complete upgrade to a newer MGCP code.

I went to : P0M3-04-4-00.bin

I again copied the file to P0M30440.bin and modified OS79XX.TXT to:

P0M30440

3. Only now am I ready to upgrade to the SIP 5.3 image.

I'm not sure if I still had to adhere to the 8.3 naming convention, I did it
just to be safe, but I am now running on 5.3 SIP.

SOme screwy things happened with my config.  I got garbage on my domain name
field that I could not back space to erase.  I just reset to factory to adress
this issue.

Thanks for everyone's help and I hope this document is useful to someone in
the future.

Babak  


Rich Adamson wrote:
> Babak,
> 
> I don't have a clue where these came from. ;)
> 
> Rich
> 
> > Would someone have a 2.2 SIP that I could try to keep in accordance 
> > to Rich's methodology?
> > 
> > Babak
> 
> 
--
Babak Pasdar
Founder/CTO
IGX Global
389 Main St.
Hackensack, NJ 07601
www.igxglobal.com
(201) 498-0555 ext. 2205

The electronic message that you have received and any attachments are solely
intended for the use of the addressee(s) and may contain information that is
confidential.

If you receive this email in error, please advise us by responding to
NOC@igxglobal.com. You are required to delete the contents and destroy any
copies immediately.  IGX Global is not liable for the views expressed in this
electronic message or for the consequences of any computer viruses that may be
unknowingly transmitted within this message.
        
This electronic message is also subject to standard copyright/ownership laws. It
is not intended to be reproduced, or re-transmitted without the consent of the
originator.

www.igxglobal.com