|
[Other] Cisco 7960 "protocol application invalid"I am trying to install a Cisco 7960 at my home office. I purchased the unit new off ebay. The previous owner says he uploading the 7.5 firmware on the unit but never used it.
When I power on the unit, the top screen says, "universal application loader" and the bottome says, "configuring vlan," then it goes to "configuring IP," for about 5 minutes, then it goes to "protocol application invalid." What does this mean? Can someone please help?
Thanks in advance for any advice or help. |
|
|
Copied from a web page:
"Protocol Application Invalid" Error This error message means that the application image cannot be loaded into flash memory or that the image does not exist in flash memory. This can happen for these reasons:
The ZIP package was not unzipped to the root TFTP directory.
Files were manually copied to the TFTP server (the ZIP package was not used).
The universal application loader was unable to load a new application image into flash memory (image authentication failure, nonexistent image, TFTP errors, and so forth).
OS79XX.TXT file must only contain the name of the file that you attempt to load, without the .bin extension. For example, if you attempt to load the SIP version 2.3 software, it must contain only the line P0S30203. If you try to load versions 3.0 and later, the file name must be in the format P0S3-xx-y-zz. For example, if you attempt to load the SIP version 7.4 software, it must contain the line P0S3-07-4-00.
The SIPDefault.cnf and SIPmac_address.cnf files are downloaded when a phone is reset. These files contain the image_version parameter that tells the phone which image it must run. Thus, if you attempt to load the SIP version 7.4 software, SIPDefault.cnf and SIPmac_address.cnf must contain image_version: P0S3-07-4-00.Looks like your unit isn't properly loading software into flash memory. The problem is likely in the SIPDefault.cnf file, which tells your device where to look for network settings like a tftp server. Also, the 7.5 version firmware has some bugs in it like dropping registration and not re-registering without a hard boot. Version 7.4 doesn't seem to have these issues. To change back to 7.4, you need a TFTP server to load the firmware. It can get complicated with this phone. You can read more about your phone at: » www.cisco.mn/en/US/tech/ ··· 84.shtml |
|
|
prestonlewis
Thanks for the post. Would it be possible to use a TFTP server to read the phone to see what it is doing? Then I could read the settings and post them on the forum for others to view. Maybe someone will see the problem.
Where can I get a TFTP server? Is is complicated to use the TFTP server?
Also, could this be a problem with my router? I just got the router and I don't know if it is hooked up right? |
|
priller join:2000-10-20 Gainesville, VA |
Re: [Other] Cisco 7960 "protocol application invalTry resetting the phone to factory default:
Complete these steps:
1. Go to the main Date/Time screen.
2. Press **# to unlock Network Configuration on the phone.
3. Press Settings.
4. The Network Configuration lock symbol should be unlocked. If it is not, exit to the main screen and press ** # again.
5. Press 3 on the keypad (or scroll down) for Network Configuration.
6. Press 33 on the keypad (or scroll down) for Erase Configuration.
7. Press softkey Yes.
8. Press softkey Save.
The phone should now be reset and stop looking for that image.
---
What VoIP service are you planning to use this phone with? Do you have your own CallManger?
|
|
|
Thanks DTwilliams,
But the phone will not respond to any buttons, even **#. The buttons are completely locked and there is nothing on the screen other then "Universal application" at the top, a cisco logo in the center, and "configuring IP" at the bottom.
Is there a way to reset the phone manually without pressing any of the buttons? What happens if I reset the phone and do not have the files to load back onto it?
I plan on using Terravon as a voip provider and virtual pbx. They have been extremely helpful in explaining everything else to me. I do not plan on using call manager.
Do you have any other suggestions as to unlocking the phone without the buttons?
Thanks again for your help. |
|
priller join:2000-10-20 Gainesville, VA |
Not that I'm aware of. Quick CCO search found the following, which may be totally unrelated or of little help:
----------
CSCed84163: Loader may fail - Application Invalid
Symptom: When a phone is upgrade to release 6.0(1.0), from a 5.0 release, the upgrade may fail to complete. The Display will read "Application Invalid"
Conditions: This may occur if any of the following is true:
There is no option 150 Set on the DHCP server on the native VLAN
CDP on the Switch and Phone do not converge in a timely fashion.
Workaround: Insure that if a DHCP server is configured on the native VLAN, that it's option 150 information points to a known good call manager.
-----
CSCef75275: Symptom: Phones are intermittently stuck at Universal Application Loader. Phone Displays message "Configuring VLAN"
Condition: Phone load P0030700100. CDP used but no Voice VLAN (Aux VLAN) configured.
Workaround: Configure a Voice VLAN |
|
|
DTwilliams,
This sounds like the problem. I just installed a router for the first time. The router is a Draytek 2900vg, with wireless lan, DHCP server, firewall and a bunch of other stuff that I'm not sure what it does. Anyways, this is the first time I set up a router and I didn't do any kind of setup to the DHCP server. I figured it would set up automatically.
So according to your last post, I need to input 150 into the DHCP server on the VLAN.
Can you tell me where would I input that information? |
|
VoipNewbie1 |
I should also mention that I set up my router to work on DHCP, not a static IP. Will this work with Cisco 7960 IP Phones? |
|
VoipNewbie1 |
Does anyone know of a way to reset the phone back to factory conditions without using TFTP? |
|
|
Why are you trying to avoid using TFTP?
Don't confuse a factory reset with fixing a bad image update. You have a bad image update. You will need a TFTP server to correct that. |
|
ncherry Premium Member join:2003-07-13 Monroe Township, NJ |
to VoipNewbie1
While I have a working 7960, the correct (and legal) image I need, a properly working tftpd and a properly setup dhcpd server all of this does not make me an expert. But it is my opinion that you need all of the above to get that phone work properly. The proper way to get an image is through Cisco. Sorry, I won't give you a copy of the image. I can probably give you the rest with no problems as they are just the setup files you'll need. Mine are setup for P0S3-07-4-00 (SIP image, version 7.4). |
|
|
|
DaSneaky1D
I am trying to reset without using the TFTP server, because all of my keys are locked. The phone doesn't respond to anything, except for a reset of *6settings at the same time. All other buttons do not work. I was told that the phone is looking for the IP address on the sellers computer. It may also be looking for a TFTP server on the sellers computer, but since I can't get into settings to tell the phone to look for TFTP or IP address on my computer, then I need a way to reset the phone without the TFTP server.
ncherry
I have the complete 7.5 image and the 7.4 image. I am not looking for another image, but thanks for offering.
The only two options I can see, are to reset the phone to factory conditions or send the phone back to the seller and let him open it up with his TFTP server. I would prefer to fix the phone myself since I live overseas and shipping costs back and forth would probably end up costing more then the phone is worth.
I appreciate everyone's suggestions. Please continue to posts. |
|
priller join:2000-10-20 Gainesville, VA |
said by VoipNewbie1: since I can't get into settings to tell the phone to look for TFTP or IP address on my computer, then I need a way to reset the phone without the TFTP server. The easy way would be to use a sniffer to see what address the phone is looking for the tftp server at. Then address yours to match. OR If you have a console cable, console into the phone and set those values. Step 1 Connect to and access the console. Step 2 At the console, enter the following commands. a. set tftp-addr tftp_server_ip_address where tftp_server_ip_address is the IP address of the TFTP server. b. set def-rtr default_router_ip_address where default_router_ip_address is the IP address of the default gateway router. c. set dchp on or set dhcp off depending on whether DCHP is used in your network. Step 3 If you set DCHP off in Step 2, type the following commands. Otherwise, continue to Step 4. a. set ip-addr phone_ip_address where phone_ip_address is the IP address of the phone. b. set subnet phone_subnet_mask where phone_ip_address is the subnet mask of the phone. Step 4 Type save. Step 5 Exit the connection to the phone. |
|
|
dtwilliams, thanks again for your advice. I am going to try one of your options. As you can probably tell, I am not a techie so this is the first time I have ever heard of a sniffer or console cable. I did a quick google and found a freeware program called Net Tools 4 » users.pandora.be/ahmadi/ ··· ools.htm. This program has a TCP Packet Sniffer, File Dependency Sniffer, Advanced Packet Sniffer, and Messenger Packet Sniffer. Will one of these sniffers work? I tried the TCP Packet Sniffer but received back around 1000 values which told me the IP header, Sport, IP Destination, and Protocol (most were TCP). What should I look for to find the value that is linked to the phone? On the console cable, is this a cable that I can buy from a local electronics store and just hook it up to my router or my computer? Or do I need to order one from Cisco? Do I need any special software to use a console cable? Thanks again for your help. |
|
1 edit |
to priller
I am having the same issue. Darn phone went smoothly from version 5 to version 6 of the SIP software and then it appeared to take version 7 but puked.
I have been watching this phone via Ethereal but no luck. Here is what it does: - It broadcasts CDP/VTP immediately upon reboot. - Then it performs a DHCP Request asking for the IP address that it last had. - DHCP Server Acks the request - Phone issues ARP for gateway IP Address - Phone issies ARP for DNS server IP address (neither ARP gets answered - ARP packet looks different than the ARP request issued for the gateway by the DHCP server which in turn do get answered - I'm still looking into this - Phone does a broadcast, the DHCP server seems to be directing the ARP to the getway - weird) - Phone goes off into la la land and eventually ends up with the Protocol Application Invalid Error. - Phone continues to renew its DHCP lease every 300 seconds - I changed this a couple of times in the DHCP server and it appears to pick it up every time so I think it is getting the DHCP information correctly yet it continues with the PAI error. - The phone does not respond to any keypress other then *6settings - which just loops it back to PAI.
Other: - TFTP Server is up and working correctly. I can TFTP files from it no problem. Also - I was watching on Ethereal when it went from v5 to v6 and saw all the TFTP requests, etc. - - Saw the same thing when it went to V7 but after it rebooted itself it hung.
I can get a serial cable from a friend but was wondering what setting all the IP info that DHCP is serving via the console is going to do. Cisco's web site says "troubleshooting" but only tells you how to set the IP info on the phone. That's not really troubleshooting. It looks like the phone is getting the info but then not actually doing anything with it? I'm guessing that somehow I botched the aplication load (duh) but there is nothing that I can find that says "hard reset to factory" or otherwise.
Any more help is greatly appreciated. |
|
ctirpak |
to VoipNewbie1
Problem Solved.
After a lot of staring at ethereal traces I finally figured this out. As suspected it was a DHCP/TFTP Problem.
My DHCP server (ISC running on CentOS 4.2) was configured to hand out option code 150.... or so I thought. I finally noticed deep in the DHCP ACK that it was not being handed back to the phone. Surprisingly, simply commenting out the mis-configured 150 option statement and rebooting the phone cleared it all up. The phone defaulted the TFTP server to the DHCP server address (they happen to be the same on my network) and the phone started marching through the prescribed file hunt on the tftp server. It found the good v7-4 image, loaded it, reset itself, and was back in business.
The key to the DHCP config is that when defining option code 150 it takes 2 lines in dhcp.conf - one line to declare the option and one more to set it. For some reason, I didn't notice that.
In this example: Linksys Gateway router at 192.168.1.1 Caching DNS Server inside the net at 192.168.1.5, external servers are xxx.xxx.xxx.xxx - change to suit your net. TFTP server at 192.168.1.50 DHCP server at 192.168.1.50 I used the pool statements and adjusted the default and max lease times down to 60 seconds each to keep forcing the phone to get a new IP address but that ends up being unnecessary - whenever you reboot the phone even when getting the Protocol Application Invalid error it appears to do a DHCP Discover/Request sequence. The ARP strangeness in my previous post appears to be the phone doing some Gratuitous ARP.
Example dhcp.conf:
#begin dhcpd.conf authoritative; ddns-update-style interim; ignore client-updates;
option voip-tftp-servers code 150 = ip-address; option voip-tftp-servers 192.168.1.50;
subnet 192.168.1.0 netmask 255.255.255.0 { #default gateway via the linksys option routers 192.168.1.1; option subnet-mask 255.255.255.0; option nis-domain "your.org"; option domain-name "your.org"; option domain-name-servers 192.168.1.5,xxx.xxx.xxx.xxx,xxx.xxx.xxx.xxx; option time-offset -18000; # Eastern Standard Time option ntp-servers 192.168.1.5; #range dynamic-bootp 192.168.1.100 192.168.1.254; default-lease-time 43200; max-lease-time 86400;
pool { range 192.168.1.100 192.168.1.150; deny all clients; } pool { range 192.168.1.151 192.168.1.160; #deny all clients; } } #end dhcpd.conf
So, bottom line, you can un-brick the thing but you have to set up a TFTP Server for it to talk to and your DHCP server must hand out the correct options. If you're using a gateway device like the linksys make sure to turn off its DHCP server function so there is only one DHCP server on your network. Then of course you need to make sure your TFTP server has the correct SIPDefault.cnf and SIPMAC......cnf .sb2 and .loads, files etc there but that is a different topic. |
|
joako Premium Member join:2000-09-07 /dev/null |
to VoipNewbie1
We had bought one of these Ciso phones and one PolyCom 501 phone. We could not (even with the assistance of Cisco's tech support) get the phone to load the latest firmware, much less even purchase it (the tech sent us the file). We decided it would not be worth the hassle to deal with these things, returned it and bought 20 more PolyCom phones. |
|
|
Ctirpack,
Are you saying that option 150 needs to be set in the router or the TFTP server? I haven't set that option in either place. |
|
joako Premium Member join:2000-09-07 /dev/null |
to VoipNewbie1
No, he had set it incorrectly which causes the phone to crash. If you have the capability to do so, by all means do it (it will make your life easier) but if you have a simple router the phone will boot and you need to set the TFTP server manually. |
|
|
to VoipNewbie1
What I am saying is that option 150 must be properly declared AND set in the DHCP configuration. It must give the phone the ip address of the TFTP server that will give the phone the images and config files. That TFTP server must obviously be working for the phone to retrieve the required files.
Most simple routers such as a Linksys do not have a TFTP server buily in nor do they have the ability to give out the configuration required by this phone.
i am running a Linux box that acts as the DHCP server, the TFTP server, and the Asterisk server. |
|
joako Premium Member join:2000-09-07 /dev/null 1 edit |
to VoipNewbie1
Can people read? I am seriously considering giving up helping people online for free and doing consulting (getting paid $80/hour+) full time.... Problem Solved.
After a lot of staring at ethereal traces I finally figured this out. As suspected it was a DHCP/TFTP Problem.
My DHCP server (ISC running on CentOS 4.2) was configured to hand out option code 150.... or so I thought. I finally noticed deep in the DHCP ACK that it was not being handed back to the phone. Surprisingly, simply commenting out the mis-configured 150 option statement and rebooting the phone cleared it all up.[emphasis added] I'm not even going to reproduce my prior posts, you can go back and read them yourself if you want and figure out the important parts yourself. |
|
|
I see the post, but I still don't know how to configure the phone nor the router. I have a Draytek 2900vg router. The router has a firewall, DHCP server and a whole bunch of other stuff that I don't know how to use. I purchased the router at the same time as the phone. When I installed it, I did enable DHCP server to hand out IP addresses to the phone. When I start up the TFTP server it automatically takes the same IP address that is assigned to my computer by the router. So the router has it's own IP address of 192.168.1.1, the computer is 192.168.1.10, the TFTP server is 192.168.1.10, and the phone is 192.168.1.11. But the phone does respond to anything.
I did not input an option 150 into the router. Where would I input this information? Is an option 150 a code for describe a series of things that need to be done?
You guys it's not that I am not reading the posts. It's that I am a complete newbie as my name says. I surf the internet, play with hardware on my computer, and a few other technical areas, but I have never had to use a router or Cisco phone before. So please don't get upset, just explain a little further.
I appreciate all of your comments. |
|
1 edit |
to joako
Joako, actually, your prior post will not help our friend newbie. What newbie stated is that the phone is giving an error "Protocol Application Invalid". (PAI) PAI occurs after the phone has marched through its boot sequence. Once the user is presented with PAI the phone is completely non-responsive to any keypress other than the *6settings combo. It should as prestonlewis pointed out at the top of this thread, be possible to use a serial cable and and Rj-45 to DB9 converter to get into the phone via the serial port. From the looks of Newbie's responses that is probably not a good idea for them to attempt.
What I spelled out was what I noticed after much investigation. My phone actually ended up in this state b/c it picked up a bad binary (I have reproduced the error since then). By removing the option code 150 from my DHCP configuration the phone decided that the tftp server that it needed was at the same address as my dhcp server -- I got lucky since they are - newbie probably won't get that lucky. It then re-tftp'd the necessary binaries and rebooted. These phones are notorious for these kinds of problems. No one solution seems to prevail to fix them.
Before I removed the option 150 it never tried to perform a TFTP of any kind once the PAI occured. Also option code 66 and the DHCP option tftp-server-name can send the whole thing into a tailspin. Notice that they are all TFTP server options.
As it turns out, using the DHCP server (v3.0.1) from ISC, if you leave option 66 un-declared in dhcpd.conf, but do declare/set tftp-server-name itwill hand back the string of the server name in option 66. If you declare and set option 66 along with tftp-server-name it will hand back the ip address specified. Declaring none of them seems to have the affect that the phone picks up the dhcp server ip for these purpose - however, it may be picking up the DHCP option 'next-server' which defaults to the same as the DHCP server and if I recall, is what is supposed to be used as the TFTP server address if none is specified. I'm taking a WAG that is what my phone is doing.
Newbie. A couple of observations.
1. You probably need to set your computer to a fixed IP address and turn off the DHCP server in you router to get through this. If you can set options in the DHCP server on your router then it is worth a try to go that route. Since your TFTP server is not on the router, you will have to find a way to either set the DHCP options on the router or you will need to disable DHCP on the router and install a DHCP server on your computer.
Make sure DHCP is configured to hand out these options, substituting the ip address of your TFTP server:
option tftp-sip code 66 = ip-address; option tftp-sip 192.168.1.xxx; option voip-tftp-servers code 150 = ip-address; option voip-tftp-servers 192.168.1.xxx;
The options are just that, optional parameters that DHCP would not hand out if you didn't tell it about them. The ISC DHCP server does not appear to hand them out unless it is asked for them by the requesting client.
3. Install a TFTP server on you computer. Looks like you've done that. Make sure it is working. You'll need to get familiar with this, your going to need TFTP forever with this phones. The IP address of the "TFTP Server" will be whatever the IP address of the computer it is running is. No need to specify it, that is just how 'server' software works (unless we get fancy, which we won't in this case). Same goes for the DHCP Server software above.
4. Unzip your Cisco images in the tftp directory specified in your tftp setup. On CentOS is it /tftpboot
5. Put the appropriate Cisco config files in the tftp directory also. You are going to need several. They are beyond the scope of this thread. They tell the phone which binaries to use. Assuming like me, you are using Asterisk for this project, you will also need to configure Asterisk to match.
6. Reboot the phone and make lots of notes. Get ethereal and take lots of traces. |
|
joako Premium Member join:2000-09-07 /dev/null |
to VoipNewbie1
The 150 entry tells the phone where to find the TFTP server. This is useful in a large business, just provision the phone on your server with the phone's MAC address, plug it in and the phone is configured and any updates are loaded.
In a smaller network it really isnt an issue to have to manually program the IP address of the TFTP server into the phone. It is possible, when we did this testing we were able to program the TFTP address into the phone. |
|
|
Looks like out post crossed on the wire. He can't program the phone w/out a serial cable. He's a bit of a rookie for that. He's going to need to specify these options in his DHCP somehow unless DHCP and TFTP are on the same server. |
|
1 edit |
to VoipNewbie1
VoipNewbie, If you: - Have the necessary config files/firmware binaries for your phone.
- Do not want to setup a Linux box.
- Have a Windows machine.
I would suggest the following: - Turn off your Cisco phone.
- Create a directory on your C: drive by the name of \TFTPD.
- Put all your Cisco phone firmware and config files into C:\TFTPD.
- Get a copy of TFTPD32 from »tftpd32.jounin.net. It has a TFTPD and DHCPD server in one package.
- Turn off the DHCP server on your router.
- On your Windows box, assign a static IP address to your Windows box. You accomplish this by altering your TCP/IP properties of your network interface card. I would suggest the IP address of 192.168.1.10 , netmask of 255.255.255.0, leave the gateway blank.
- Start the TFTPD32 program.
- In the TFTPD32 program, click on the "Settings" button:
- For Base Directory, input into the text input box: C:\TFTPD.
- Ensure that "TFTP Server" and "DHCP Server" checkboxes are selected.
- TFTP Security should be set to "None".
- For "Advanced TFTP Options", ensure that "Translate Unix file names" and "Allow '\' As virtual root" are selected.
- Click the "OK" to save the settings.
- Exit TFTPD32 and restart it so it will use your new settings.
- Turn on your Cisco Phone (making sure it is plugged into the same switch as your Windows machine running the TFTPD32 program).
At this stage, your Cisco Phone should start requesting an IP address via DHCP. Your Windows machine running TFTPD32 will answer the request since you have previously disabled the DHCP service on your router. Next, it should start to TFTP down all the firmware and configs from your Windows machine running the TFTPD32 program. Your "Tftp Server" window of the TFTPD32 program should start listing all the files the Cisco phone is grabbing. Once your phone is back to working order, see if you can lock down all the settings for your phone. This will alleviate the need to TFTP down the configurations for your phone ever time you reboot or power-cycle the phone. You can now exit the TFTPD32 program, enable DHCP on your router, and reconfig your Windows box to use DHCP. See ya... d.c. |
|
|
Thank you all for the advice.
I'm going to try this.
im_chandave, when I put the config files in the folder, should I only put the firmware that is currently on the phone? The phone has 7.5 on it currently, but my voip provider wants me to remove it an put 7.4 on it once it gets working. Can I just put 7.4 in the folder and then follow your steps and the phone will load 7.4 on top of the 7.5? |
|
|
The current v7.5 load is giving you problems (be it incomplete loading or whatever).
I would suggest you follow your VoIP provider's suggestion and install v7.4 to get the phone to a point where your provider can better help you with your problem.
Once you have the phone working properly with v7.4, you might upgrade to v7.5 at your discretion.
See ya...
d.c. |
|
|
Holy smokes, I've been working on this so long my posts are getting incoherent. I don't think I was making sense.
In my last post I was trying to say that I am going to try your suggestion.
What I meant to ask was can I put 7.4 firmare into the C:\TFTPD if 7.5 is currently on the phone. If I can use the 7.4 firmware, then it kills two birds with one stone. But if I can't then I will use the 7.5 and then downgrade later. |
|
|
I think the Cisco phone will try to download a versioned firmware (based on filename) unless you can tell it to use a different filename. Since your phone doesn't even boot up to the point where you can use the keypad, I don't think you can change the firmware image filename. Just watch the TFTPD server window to see which files your Cisco phone tries to download.
I'm not sure if it would work, but, you might want to try to rename the v7.4 to the filename used by v7.5. This is a very dubious suggestion since I think Cisco embeds the firmware version into the firmware file itself. Check with the Cisco documents for your phone. They should be more authoritative about this matter.
See ya...
d.c. See ya...
d.c. |
|