10-26-2012 06:09 AM - edited 03-21-2019 09:54 AM
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 [41069265] 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[136]: 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[1]: notify add wan1 interface(br0)
Jan 1 00:00:27 SPA112 daemon.err system[1]: start 0 vlan-id... ok
Jan 1 00:00:39 SPA112 daemon.err dnsmasq[136]: 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?
12-13-2012 02:00 PM
Hi Aaron,
Thanks for the feedback. I'm pleased to read that the 1.3.1(002) firmware is holding up.
Regards,
Patrick---
12-14-2012 02:15 PM
I installed the 1.3.1(002) firmware on Dec 10th.
The device hung again today; however in a new (to me) way.
No dialtone on the connected handset, intermittenent ping response. The web interface would let me log in, but not navigate to the different tabs. I power cycled it to restore functionality.
The relevant portion of my syslog is below:
...
Fri Dec 14 15:12:48 2012: <4>Dec 14 15:13:23 SPA112 [17501910.408000] ###### sock_sendmsg return 172
Fri Dec 14 15:12:48 2012: <4>Dec 14 15:13:23 SPA112 [17501910.412000]
Fri Dec 14 15:12:48 2012: <4>Dec 14 15:13:23 SPA112 [17501910.412000] #### RTP STOP Flag set in this channel break ####
Fri Dec 14 15:12:48 2012: <4>Dec 14 15:13:23 SPA112 [17501910.420000] In cordless Driver Codec 0 and str PCMU/8000 chan 0
Fri Dec 14 15:12:48 2012: <4>Dec 14 15:13:23 SPA112 [17501910.420000] In cordless Driver Codec 8 and str PCMA/8000 chan 0
Fri Dec 14 15:12:48 2012: <4>Dec 14 15:13:23 SPA112 [17501910.420000] In cordless Driver Codec 100 and str NSE/8000 chan 0
Fri Dec 14 15:12:48 2012: <4>Dec 14 15:13:23 SPA112 [17501910.420000] In cordless Driver Codec 112 and str encaprtp/8000 chan 0
Fri Dec 14 15:12:48 2012: <4>Dec 14 15:13:23 SPA112 [17501910.420000] In cordless Driver Codec 255 and str chan 0
Fri Dec 14 15:12:48 2012: <4>Dec 14 15:13:23 SPA112 [17501910.420000] In cordless Driver Codec 255 and str chan 0
Fri Dec 14 15:17:20 2012: <45>Dec 14 15:17:55 SPA112 syslog-ng[117]: STATS: dropped 0
Fri Dec 14 15:20:57 2012: <29>Dec 14 15:21:32 SPA112 msgswitchd[162]: MSGSWD RTCP Reqt len 12 Data 2,1965716,7312,0
Fri Dec 14 15:20:57 2012: <4>Dec 14 15:21:32 SPA112 [17502399.384000] RTCP is running so calling rtcp stop
Fri Dec 14 15:20:57 2012: <4>Dec 14 15:21:32 SPA112 [17502399.384000] chan->kmode is present not null
Fri Dec 14 15:20:57 2012: <4>Dec 14 15:21:32 SPA112 [17502399.392000] ###### RTCP sock_sendmsg return 172
Fri Dec 14 15:20:57 2012: <4>Dec 14 15:21:32 SPA112 [17502399.396000]
Fri Dec 14 15:20:57 2012: <4>Dec 14 15:21:32 SPA112 [17502399.396000] #### RTP STOP Flag set in this channel break ####
Fri Dec 14 15:20:57 2012: <4>Dec 14 15:21:32 SPA112 [17502399.400000] ###### sock_sendmsg return 172
Fri Dec 14 15:27:20 2012: <45>Dec 14 15:27:55 SPA112 syslog-ng[117]: STATS: dropped 0
Fri Dec 14 15:31:17 2012: <29>Dec 14 15:31:46 SPA112 system[103]: NTP update successfully, Year:2012,Month:12,Day:14,Hour:15,Min:30,Sec:54
Fri Dec 14 15:37:28 2012: <4>Dec 14 15:38:57 SPA112 [17503371.716000] In cordless Driver Codec 0 and str PCMU/8000 chan 0
Fri Dec 14 15:37:28 2012: <4>Dec 14 15:39:08 SPA112 [17503371.716000] In cordless Driver Codec 18 and str G.729/8000 chan 0
Fri Dec 14 15:37:28 2012: <4>Dec 14 15:39:10 SPA112 [17503371.716000] In cordless Driver Codec 8 and str PCMA/8000 chan 0
Fri Dec 14 15:37:28 2012: <4>Dec 14 15:39:10 SPA112 [17503371.716000] In cordless Driver Codec 100 and str NSE/8000 chan 0
Fri Dec 14 15:37:28 2012: <4>Dec 14 15:39:10 SPA112 [17503371.716000] In cordless Driver Codec 112 and str encaprtp/8000 chan 0
Fri Dec 14 15:37:28 2012: <4>Dec 14 15:39:10 SPA112 [17503371.716000] In cordless Driver Codec 255 and str chan 0
Fri Dec 14 15:37:38 2012: <45>Dec 14 15:39:15 SPA112 syslog-ng[117]: STATS: dropped 0
Fri Dec 14 15:38:20 2012: <29>Dec 14 15:39:32 SPA112 msgswitchd[162]: MSGSWD RTCP Reqt len 12 Data 2,3702952,7312,0
Fri Dec 14 15:38:20 2012: <4>Dec 14 15:40:03 SPA112 [17503416.032000]
Fri Dec 14 15:38:20 2012: <4>Dec 14 15:40:03 SPA112 [17503416.032000] #### RTP STOP Flag set in this channel break ####
Fri Dec 14 15:38:20 2012: <4>Dec 14 15:40:03 SPA112 [17503416.032000] ###### sock_sendmsg return 172
Fri Dec 14 16:50:33 2012: <45>Dec 10 17:03:30 SPA112 syslog-ng[119]: syslog-ng version 1.6.12 starting
Fri Dec 14 16:50:33 2012: <5>Dec 10 17:03:30 SPA112 [ 0.000000] Linux version 2.6.26.5 (jlai2@ubuntu) (gcc version 4.1.2) #1 PREEMPT Wed Dec 5 11:38:19 PST 2012
Fri Dec 14 16:50:33 2012: <4>Dec 10 17:03:30 SPA112 [ 0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
...
12-17-2012 02:00 AM
I've had mixed results with the beta firmware. I currently have just over 100 sites running on 1.3.0(017). Most of these have been pretty stable (with some up for 11 days and counting) and for the majority it appears to have fixed an issue with fax failing if a call is already established on the other line. For some however, the ATA needs rebooting at least once a day. A couple of sites still had issues with the Fax failing (I'll probably post a new thread for this), so I've upgraded them to 1.3.1(002). Stability wise, they're still up and running after 72hrs.
I also have around 400 sites still on 1.2.1(004), however, these are all configured to resync/reboot every night, so have not encountered so many issues with stability.
12-14-2012 09:31 PM
Hi,
I am currently running the test firmware provided last week. My SPA112 hung again today.
I had tried to make the perl script work, but my perl skills lacking, and I was unable to make the script provided work correctly.
I wrote a small .NET console app to reboot the SPA112. It can be run from a command line, or a schedulded task. You can schedule it (using a schedulded task) to run automatically in the middle of the night.
I have put up a small web page at http://www.freymond.ca/SPA112
There is no installation. To run it, provide it the following 3 command line options:
-username=
-password=
-address=
For example:
SPA112_Rebooter.exe -username=admin -password=admin -address=192.168.1.5
If the information is correct, it will reboot the SPA112.
Any questions, ask here so the whole community can benefit from them.
12-17-2012 06:08 AM
Hey everybody -
I was hopeful with 1.3.1 (002) but still crashed after about 4 days.
Mike's rebooter works great. I first tried a SIP NOTIFY to reboot, and that seems to restart the VOIP task but does not actually reboot the device (seems like it should (?)).
Mike's tool actually uses the web interface and seamlessly does the job. You can redirect output and check the success message.
If you have a way to do this, one option for rebooting is to check the response time from a SIP OPTIONS command. On my system it is typically under 50 ms but goes over a second prior to hanging. I use my network monitor (PRTG) to watch this every minute and if it exceeds 250 ms, I run Mike's rebooter. This way I am getting Cisco some data on uptime, rather than rebooting every night.
Mike's tool is free, but he'd gladly accept a paypal donation.
Also, I keep looking under System Information/Status for uptime but it's not shown - is it somewhere else in the GUI?
--Dale Van Aken
12-17-2012 12:01 PM
Hi Community,
Thanks for reporting the problems with 1.3.1(002) release candidate. It turns out that and error in the build file did not bring in an updated module. Please accept my apologies.
Here's a link to the 1.3.1(003) release candidate on my SkyDrive
Regards,
Patrick---
Message was edited by: Patrick Born--removed link, there's an error with the version number. Will correct shortly
12-18-2012 08:12 AM
Hi Patrick, and everyone...
I'm adding a "me too" (and Patrick, I'll email you directly with my info).
I've been having this problem since I purchased my SPA112, and it hasn't gotten the point where I've wanted to try to brave TAC (okay, I guess it's "small business support") to open a case until I realized that if I needed to deal with this as a warranty issue I only had a couple of weeks left.
I saw a lot of references to CallCentric, but I'm actually using this as part of a system running Asterisk - so I have the ability to monitor (capture) all of the traffic to and from the unit from either end (of the LAN). I haven't ever seen anything interesting or seemingly useful in the logging.
I noticed the Perl script posted to restart the unit periodically. I haven't looked at this yet, but I did write a script myself that likely does the same thing. Still, I see coma about every 5-10 days (I get a log entry every time the reset script dies). As with everyone else, only pulling the plug fixes it.
I'd be happy to try any beta or lab firmware updates that you can provide - I can tell you that I have had at least one attempt to update f/w fail with the unit frozen for several hours before I finally put it out of its misery. Currently it's running 1.2.1 .
Glad to find this thread (what an uncommonly accurate subject line). Thanks for any help, and let me know how I can contribute.
12-18-2012 08:36 AM
Hi, I just wanted to report that my SPA112 has been up for a whole month now and working great. I'm using the 1.3.0 (016) firmware. I must also admit I never fax and my call volume is about 1 call per day.
12-18-2012 08:46 AM
Tom --Glad to know your unit is stable. What does your network side look like if I may ask? Is the SPA on a PBX or direct to a provider? Is the network busy? I wonder if part of my issue is that my SPA sits as an extension (2, really) on my Asterisk PBX and has a fair amount of "keepalive" traffic. The last post from KMPeterson mentioned Asterisk and he gets 5-10 days before a hang. I have been getting about 4 days. Not that this should cause the crashes, but it may be a clue as to the cause. Thanks.
12-18-2012 08:51 AM
Hi Community,
Here's a link to the 1.3.1(003) release candidate firmware on my SkyDrive: http://sdrv.ms/U6F8nW
Please note that this is not officical firmware at this stage but you're welcome to test it if your SPA1x2 is exhibiting the issues described in this thread.
Regards,
Patrick---
12-18-2012 09:02 AM
Patrick - For those of us that installed the build mis-named 2.00.06(002), can you tell us if this latest is any different (other than the revision name)? If I don't have to take it down right now I'd prefer to let it run.
01-08-2013 08:36 AM
Do we have a rough eta on when the next official firmware release will be? 1.3.1 (003) appears to be much better than 1.2.1 (004), but would like an official release to roll out to the estate.
12-18-2012 02:21 PM
I'm just a home user with a DSL line going into a Asus router and my ATA connected to the router. I'm using the QoS features of the router of course. I'm using Callcentric.
12-18-2012 10:47 AM
FYI... 1.3.1(002) (Dec. 7 vintage) crashed after 4 days.
12-18-2012 01:22 PM
Hi Dale,
During our testing, we discovered that the 1.3.1(002) Dec.7 firmware did not include the fixes due to an issue with the build file. If you're still up for it, please consider trying out the 1.3.1(003) release candidate whose link I posted in this thread a few hours ago today (Dec/18th 2012).
Regards,
Patrick---
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide