Hi, I am a home user and ex-programmer. I'm using the Cisco SPA112 with the latest firmware 1.2.1 (004). Every two or three days the ATA crashes. Here are the symptoms:
a) no dial tone
b) line 1 LED is ON (as normal)
c) ATA is PINGable
d) IVR is unresponsive
e) web setup URL does not respond, can not get to the setup page
f) The reset button does not respond.
My only recourse now is the check if I have a dialtone every morning and, if not, pull and reinsert the power plug. The cold boot of course results in the local log being lost. Here is the log right after boot up.
Jan 1 00:00:04 SPA112 kern.warning [ 0.000000] CPU: ARM926EJ-S  revision 5 (ARMv5TEJ), cr=00053177
Jan 1 00:00:04 SPA112 kern.warning [ 0.000000] Machine: NXP PNX8181
Jan 1 00:00:04 SPA112 kern.warning [ 0.000000] Memory policy: ECC disabled, Data cache writeback
Jan 1 00:00:04 SPA112 kern.warning [ 0.000000] CPU0: D VIVT write-back cache
Jan 1 00:00:04 SPA112 kern.warning [ 0.000000] CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
Jan 1 00:00:04 SPA112 kern.warning [ 0.000000] CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
Jan 1 00:00:04 SPA112 kern.warning [17179569.184000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 7874
Jan 1 00:00:04 SPA112 kern.warning [17179569.184000] PID hash table entries: 128 (order: 7, 512 bytes)
Jan 1 00:00:04 SPA112 kern.warning [17179569.184000] Console: colour dummy device 80x30
Jan 1 00:00:04 SPA112 kern.warning [17179569.260000] Mount-cache hash table entries: 512
Jan 1 00:00:04 SPA112 kern.warning [17179569.264000] Board HW MODEL : 0x3
Jan 1 00:00:04 SPA112 kern.warning [17179569.336000] squashfs: LZMA suppport for slax.org by jro
Jan 1 00:00:04 SPA112 kern.warning [17179569.384000] [ip3912] : Bridge Mode...
Jan 1 00:00:04 SPA112 kern.err [17179569.408000] physmap-flash physmap-flash.0: map_probe failed
Jan 1 00:00:04 SPA112 kern.warning [17179569.416000] Using Full Image\'s RootFS
Jan 1 00:00:04 SPA112 kern.warning [17179569.420000] Using static partition definition
Jan 1 00:00:04 SPA112 kern.warning [17179569.424000] !!! do adler32 checksum !!!
Jan 1 00:00:04 SPA112 kern.warning [17179571.260000] File system image checksum OK
Jan 1 00:00:04 SPA112 kern.err [17179571.344000] ksz8873 0-005f: failed with status -1
Jan 1 00:00:04 SPA112 kern.warning [17179571.348000] ksz8873: probe of 0-005f failed with error -1
Jan 1 00:00:04 SPA112 kern.warning [17179571.352000] PNX8181 watchdog timer: timer margin 16 sec
Jan 1 00:00:04 SPA112 kern.warning [17179571.372000] GACT probability on
Jan 1 00:00:04 SPA112 kern.warning [17179571.376000] Mirror/redirect action on
Jan 1 00:00:04 SPA112 kern.warning [17179571.380000] u32 classifier
Jan 1 00:00:04 SPA112 kern.warning [17179571.384000] Performance counters on
Jan 1 00:00:04 SPA112 kern.warning [17179571.388000] input device check on
Jan 1 00:00:04 SPA112 kern.warning [17179571.392000] Actions configured
Jan 1 00:00:04 SPA112 kern.warning [17179571.396000] Netfilter messages via NETLINK v0.30.
Jan 1 00:00:04 SPA112 kern.warning [17179571.400000] nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
Jan 1 00:00:04 SPA112 kern.warning [17179571.412000] ipt_time loading
Jan 1 00:00:04 SPA112 kern.warning [17179571.464000] VFS: Mounted root (squashfs filesystem) readonly.
Jan 1 00:00:04 SPA112 kern.warning [17179576.144000] ***** LED_DRV init *****
Jan 1 00:00:04 SPA112 kern.warning [17179576.148000] ***** LED_DRV end *****
Jan 1 00:00:04 SPA112 kern.warning [17179576.176000] *** sys event driver initialized ***
Jan 1 00:00:04 SPA112 kern.err [17179579.184000] br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
Jan 1 00:00:04 SPA112 kern.warning [17179580.880000] Empty flash at 0x00069454 ends at 0x00069600
Jan 1 00:00:05 SPA112 daemon.err dnsmasq: failed to load names from /etc/hosts: No such file or directory
Jan 1 00:00:23 SPA112 kern.err [17179600.844000] br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
Jan 1 00:00:27 SPA112 daemon.err system: notify add wan1 interface(br0)
Jan 1 00:00:27 SPA112 daemon.err system: start 0 vlan-id... ok
Jan 1 00:00:39 SPA112 daemon.err dnsmasq: failed to load names from /etc/hosts: No such file or directory
Here are some things I have tried on my own, to no effect:
a) Tried running with Provisioning/Firmware Upgrade/Upgrade set to false.
b) Reloaded the firmware with IE. Before, I did it with FireFox.
c) Did a factory reset and re-entered the settings suggested for my ATA from Callcentric.
How should I proceed?
Cisco did not give me a release date, but neither did I ask.
During Callcentric's DDoS crisis, after logging in, one was immediately directed to a "crisis page". That page does not display now. On the crisis page they specified slightly different settings than in their usual SPA1x2 setup page does. Here they are:
Outbound Proxy: srv.callcentric.com
Register Expires: 120
All the rest are the same as on the SPA1x2 page. I DO remember changing the Outbound Proxy back and forth and having bad results when set to callcentric.com. Don't know why. This VOIP stuff is still somewhat magic to me.
I would like to remind everyone to adjust the QoS settings in your router to give the ATA top priority. I've set my rule up specifying the ATA's MAC address and it is working well.
My QOS is working well. When the SPA112 locks up, it locks up so that not even the GUI is available. It needs to be cold booted. That's why I was suspecting a memory leak in the Cisco firmware. I had the registration set to 120 for a while too and I'm not sure if it locked up any more or less, but that's way lower than 3600 which was their old recommended CC setting before the DDOS. I tried srv.callcentric.com, callcentric.com, both seemed flakey. Now I am using callcentric.com for the proxy (as per their new SPA112 config instructions).
Automatically soft booting it nightly from a perl script before it crashes is the only fix that I have found and this prevents it from locking itself up completely. This also points strongly to a Cisco software bug (not hardware). This solution is okay for one or two devices, but hard to script reboot devices that are configured via DHCP and on remote networks.
Since yours has been running for a week at 120, I suspect that the beta does fix something, so I'm going to have to hold out for the release 1.3.0
Thanks for your (and others) responses in this thread. This thread has been amazingly helpful.
I have the same problem with 7 of the SPA112's. They exhibit the same symptoms as the OP has described. All flashed with newest official firmware (1.2.1 004).
How can I get that 1.3 beta? My users are preparing a revolution, since I took away a perfectly good Panasonic 6/16 15years old PBX, and replaced it with the shiny new non-working Cisco's
We're actively working the issue with several Community volunteers.
Some folk have found that our test firmware helped them while a few continue to have issues.
We're continuing to test our latest fix which we'll make available as soon as possible. I don't have a specific date, but am expecting it in days, not weeks.
I would be more than happy to be able to try newer firmware, on at least one of my 7 SPA's, and I feel comfortable installing beta/prerelease versions (currently using Linux kernel 3.7rc6 on openSUSE 12.3 Milestone1).
Please let me know if and how can I get it?
I sent an e-mail to you last week.
I am having the problem described; Need to get this resolved sooner rather than later.
Just had my beta 1.3.0 (008) Sep 24 2012 firmware crash after 30 days. Wasn't the full crash where unit was totally lala, just the voice components weren't available in browser and of course calls unable to be made or taken.
Another side effect of 1.3.0 (008) Sep 24 2012 and 1.3.0 (015) Oct 31 2012 I found was that they don't work with my alarms any more, like the previous firmware did. I heard today from cisco helpdesk that alarms are not suported on these (or any cisco devices), The sales blurb says they are "phone line adapters" and I haven't seen any caveats to say they aren't unsupported.
We bought 40+ units to replace the analog lines on the pbx to cover faxes, alarms and the odd common area phone and have had nothing but hassels with crashes, faxes unreliable and alarms not communicating. Looks like this product is not fit for purpose.
Whilst alarms may be officially unsupported I have not had any issues with my DSC alarm and the SPA112. I'm running the 1.3.0(016) version.
I've been running the latest 1.3.1(002)RC Dec.7 firmware since Friday. So far so good, no issues and no required resets.
I wish we knew of a way to induce a lockup, rather then sit and wait a month for it to crash.
About a week and a half ago, we upgraded about 25-40 ATA's with the beta 1.3.0 (017) and now 1.4.0 (001). We haven't seen any lockups on the ATA's running this firmware although we're still getting lockups on ATA's running 1.2.1.
Also note that we reboot about half of the ATA's each night.
I have an unofficial release candidate of 1.3.1(002) firmware available for the SPA1x2 ATA devices if you'd like to try it out. It's just over 9MB in size so I've shared it on my SkyDrive at the URL.
When released, (I don't have an official release date yet) this firmware is intended to address the locking up / freezing / catatonic issues that have been reported. Special thanks to each and every one of you who mailed me directly, tested firmware, and helped my colleagues and I.
Message was edited by: Patrick Born
there are problems with 1.3.1(002) release candidate so I've removed the link. I'll post an update release candidate as soon as I'm able.
I've been running three SPA122s side by side for the last week or so, each one running a different firmware revision. I haven't been using them for any calls, they're just registered to my SIP server and sitting idle.
I don't know if any of this information is helpful, but I figure some feedback is better than none.