7960 Protocol Application Invalid

[thomson.ian]

Hello all!

Firstly, I'm sorry to have to post here. I can assure you I've done my reading on the various posts about this issue and tried to troubleshoot myself with no luck. My situation is probably similar to the other posters on this issue. I'm new to the VOIP world, and bought a used 7960 on ebay, last night attempted to load the SIP firmware on when the transfer failed (it was looking for a few files that weren’t there) Now I'm getting the dredged Protocol Application Invalid.

What I've tried is to plug the phone and just a laptop with TFTP (and DHCP with option 150 set - laptop given a static IP of 192.168.0.99 and the IP pool set to 5 addresses starting at 192.168.0.100) into a simple d-link switch and tried to reload the firmware. When the device boots in this setup the DHCP seems to give all the addresses in the pool to the phone and then proceeds to keep requesting them from the server (it also looks like it's looking for the IP of 0.0.0.84) after which it doesn't even start transferring files from the TFTP.

My next thought was to put a static reservation in DHCP but with the limited options on the TFTP/DHCP server I'm not sure how that would work

Any help anyone could give would be very much appreciated.

Thanks!

[paolo bevilacqua]

Likely the firmware you're trying to load is too new, and you will have to proceed with staged upgrades.

You can search the forum for many threads about that.

[thomson.ian]

Hi Paolo,

Thanks for your reply, I really appriciate the assistance. I wondered about the firmware being to new too and I'll admit I did try and load the newest version on it. I was wondering though about the current state of the phone. If I put an older version of the SIP firmware on my TFTP server, and boot the phone will it get a single IP and resume downloading the firmware from TFTP? As it stands now, according to the log it's stuck looking endlessly for IP's and doesn't even start transfering anything from the TFTP server.

[paolo bevilacqua]

You can also try a factory reset sequence. Note soem version of tftp32 do not hande option 150 correctly.