I am on my second SPA400 in as many weeks. I thought the first one had a problem because after doing some configuration it would start re-booting itself on approximately 10 ~ 15 second intervals. I suppose I don't know for sure that they were re-boots, but the SPA400 would lose it's connectivity for a bit, then it would come back for a bit, then lose it for a bit, etc. This was verified by running constant pings to the SPA400.
With both SPA's, they seemed to work fine out of the box with the exception of multiple out-bound calls not working (later fixed by altering the ground-loop start setting). However, following the instructions I upgraded the firmware to 18.104.22.168 and that's when the problems started.
This is apparently random as you may configure any number of things on the SPA400 before the re-boot cycle starts. It doesn't seem to matter what you configure, either. Sometimes you configure option X and it works fine, then later you configure the same option and the cycle starts.
Once it starts, the only way I have found to fix it is to catch it while it is up and do a factory reset on the device (you must work quickly because you only have a few seconds). Then you begin the process all over again.
I also upgraded to the beta firmware of 22.214.171.124, but this didn't fix the problem.
Again, this behavior has been consistent on both SPA400's. At this point I am reluctant to make any configuration changes for fear of it starting to re-boot itself over and over again, but my configuration is less than optimal (default passwords, DHCP, etc.).
If someone could help, I'd really appreciate it.
One possible temporary solution, try to unplug the line cable from SPA400 and put it back again after a few seconds. This might solve your resetting to factory default problem.
HI Naazish -
Unfortunately, the problem isn't that the unit goes back to factory defaults. The problem is that it suddenly gets into a boot-loop after making configuration changes. The only way I've found to get it out of this mode is to factory reset the unit.
What I need is for the unit to stop going into this mode of continuously re-booting itself after making configuration changes.
This is definitively not normal. What configuration parameters are you changing? Are you using it with SPA9000? Is it using latest release?
Hi! Yes, I agree it is not normal, but two SPA400's have done this. It is being used with an SPA9000 and SPA series phones. The SPA9000 is running the latest firmware, and the SPA400 is now under a beta firmware release of 126.96.36.199 as 188.8.131.52 started causing my problems. I've seen other users in the forum mention the re-boot issue as well, but nobody seems to have a fix for it.
As for what I configure that causes the problem? Off the top of my head any of the following changes started causing the device to go into this mode, though it's not consistent (i.e. configuring one of these items doesn't always cause the problem):
pretty much all of your fairly normal configuration changes have cause this behavior to manifest itself.
Hi everyone -
Is there really no answer on this at all? I saw several other threads mention the same problem. Can someone at least tell me if Cisco is investigating this or if I need to find another product? My customer is pretty upset at the moment.
Is it there any way you can plug another SPA400 (it may be a defective unit)?
Otherwise, this may be caused by an invalid value you are introducing. As said, this is not common.
If you require urgent assistance, I suggest you contact the Small Business Support Center (details on the community main page).
Thanks for the suggestion. I had already tried a second SPA400. It pretty much behaved in the same fashion (started cycling after a firmware upgrade and upon configuring the unit). The second one also died during a firmware upgrade and never came back to life even with the recovery utility. That one is being RMA'd and I now have a third unit on the way.
As a side note, I am used to working with UC products and I have to say that this is a little dissapointing even though I believe the unit would be good value for the money if I weren't having these issues.
I tried using the beta 184.108.40.206 firmware and it had the same problem. To be frank, I'm surprised that this issue has not been addressed. I saw several other threads on the same issue and none of them have been resolved.
At this point I am running a really old version of firmware because any of the newer firmware's introduce the problem. This makes it difficult because I can clearly tell that the older firmware doesn't handle some of the features nearly as well, but I'm afraid to upgrade it lest the SPA400 start rebooting constantly.
This is not a good situation. You should not have to be concerned about "touching" your equipment and making configuration changes.
This is not a normal behavior. Unit should not reboot. I suggest (if under warranty) you RMA the product.
I realize that this is not normal behavior, but I it is apparently frequent enough that other user's have the same problem. I have already RMA'd two SPA400's and am on my third one. This is the one I am afraid to touch.
What I'd really like to see is a definitive answer from Cisco saying that the cause is known and this is what fixed it - even if it is due to a bad batch of SPA400's in the manufacturing process. Simply returning them over and over again doesn't do anything but frustrate everyone involved.
I'm on my second SPA400 and within minutes or running with the latest firmware (220.127.116.11), it started rebooting and then locked up. It took a while to get a hard factory reset, but eventually it came up and I loaded an older firmware version, 1.0.4.x, which seems stable. I doubt these SPA400 units have manufacturing defects - it seems clear it's a firmware problem.
Cisco: Where's the firmware to correct this problem? Or should we just indefinitely use the older firmware version?
I experienced this issue last month during a late night installation so hopefully my memory serves me correctly. I had intended to send to Cisco as I had an open case, but got pushed back.
If you can get into the SPA400 you need to change the SPA9000 Address from Static Address (IP Address and Port) to Discover Automatically. Now the Cisco documentation recommends you use a Static Address, however I have only had problems with it and always use the Discover Automatically.
I confirmed that this resolved our issue and also was able to reproduce so hopefully this will resolve your issue.
Please report back, now if this is not the problem I may be able to review some of our case logs and search or the problem
SPA900 - SPA500 IP Phones
Thanks for the response. I'm out of town at the moment and don't want to take a chance on this remotely. I'll be back in a few days and will give this a try.
I'm curious, in your testing were you able to run the latest firmware versions?
Yes the latest firmware 18.104.22.168. This was just a few weeks ago.
SPA900 - SPA500 IP Phones
Is there any word from Engineering on the SPA400 rebooting issue? It's now been more than 2 weeks since getting escalated. If this issue is caused by a static IP in the SPA400, then this should be easily reproduced by engineering and then a firmware update built.
Did making this change fix the problem or not? Cisco may or may not be able to reproduce. I recommend you attempt the resolution I posted, if it works you have solid information you can provide to them for them to address w/ QA, but I wouldnt be beholden to the firmware fix as you may be waiting a while when you can make the change and move on.
In my setup the SPA400 must have a static IP. For example, the only way that I can reach the SPA400 voice mail from an AA Dial Plan in the SPA9000, is: email@example.com:5090 (where .10.201 is the SPA400) Normally something like "vmm" should work. I need to do it this way because of yet other bugs in the SPA9000/SPA400 - calls to Cisco support resulted in no answer to this bug, they simply gave kudos to my "800:..." work-around.
I have serveral installations and I almost always require VM access from the dial plan so users can either check VM remotely or some sort of hunt group when nobody answers. I never use the Static Address setting.
As a test I would use the discovery address and see if this fixes your issues.
OK, I just set the SPA400 to Discover automatically. I see this setting is not related to the static IP of either the SPA9000 or SPA400. So we'll wee what happens now.
I had wondered why you questioned the IP Address becuase you had to hard code the IP into your DP. Makes sense now.
You are correct, it is not the static IP Address of either the SPA9000 or SPA400. I have used the settings interchangable for some time, but the time I had issues w/ the reboot, fixed the problem. In discovery mode the SPA400 finds out about the SPA9000 when the SPA9000 registers to the SPA400. Otherwise setting it statically it know automatically. I am not sure why there is an option.
Make sure you reboot everything after making the changes and cross your fingers.
After only changing the SPA400 to "Discover Automatically" (from specifying a static IP for the SPA9000), after a few minutes the SPA9000 "Failed to Register". Reboots all around didn't help. When I changed the SPA400 back to giving a static IP for the SPA9000, things went back to normal. (Or about as normal as immediately before this change.)
So, the question to Cisco still remains: Has this issue been investigated yet???
Did that stop the constant reboots? If so you may want to find out why the REGISTER failed. You may or may not get an answer from Cisco in the time you need, so you may want to see what you can do on your own... or not.
The constant SPA400 reboots occurred with the 22.214.171.124 version of the firmware (the latest). When I loaded 126.96.36.199, the reboots stopped. And these reboots with 188.8.131.52 occurred within minutes of opening the box, plugging it into a network with only an SPA9000, one SPA504g phone, a PC, and the router/switch. Basically, out of the box, minimal setup, updates to latest firmware all around. The SPA400 was replaced but the exact same thing happened, and that's when I went back to an older firmware, which was mentioned on another forum.
What stopped the reboots was to load an older version of the SPA400 firmware. (I suppose I could just be content with this older firmware, but we're having too many other problems that I suspect there are some things fixed in the current firmware, however a reboot every 30 seconds would make the system totally useless.)
As a reminder here are the open issues we have:
One of the lines on some phones will go into a "Share Call Active" state several times a day. This even happens by itself - when staff goes home at night things the phones looks OK, but when they arrive in the morning the phones are in this state. Then it mysteriously goes away after a few calls. The only fix is to reboot the SPA9000.
The SPA400 freezes up every few days, for no apparent reason. This varies from 2 to 4 days. The only fix is a power cycle.
When calls are answered by lifting up the handset on the SPA504g phones, about 20% of the time the call goes to the speaker and the handset is dead. The fix is to put down the handset and pick it up again.
We have been running SPA9000 with SPA400 and 4 SPA942 phones for over a year now without any problems. That is until last Monday when without any obvious reason the SPA400 starts to reboot after about 45~50 seconds. There were no configuration changes and it has the latest software version.
This is the phone system for our retail store and as a result our customers can no longer reach us.
Is there a solution available?
PS I have setup syslog on the router and the reboot starts everytime after the same message.
|04-22-2010||16:22:34||Local7.Debug||192.168.29.6||0000019362 - TIU: 1st FXO state report sent|
|04-22-2010||16:22:23||Local7.Debug||192.168.29.6||0000013811 - TIU: All FXO port get a state|
|04-22-2010||16:22:23||Local7.Debug||192.168.29.6||0000013807 - Global initialization done.|
|04-22-2010||16:22:23||Local7.Debug||192.168.29.6||0000013806 - ast_main done USB: 0, vms: 0|
|04-22-2010||16:22:23||Local7.Debug||192.168.29.6||0000013805 - <027>[1;37;40mAsterisk Ready.<010><027>[0;37;40m|