cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Welcome to the Cisco Small Business Community

Have a question? Click on a topic board below to get started in the community.

21836
Views
29
Helpful
117
Replies
sgtpanties
Beginner

SPA112 goes catatonic, crashes, no dialtone

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?

117 REPLIES 117

I suspected that it was a network issue since I could easily reboot the unit from the webui and still have registration failures afterwards. Power cycling did seem to help though. Seems to be something that persists with a reboot, but not a full power cycle.

My router is running custom firmware and can be tempermental at times. It's been running fine lately though so I'll be more mindful of the SPA122's behavior.

Yes - this is true - running reboot from the GUI or using Mike's rebooter does not do a cold restart - I assume it restarts the production tasks but not the OS.  This would not be my choice if I had designed this device - I'm not sure what downside there is to a full restart.... I did mention this to Cisco a few weeks ago. --Dale

Aaron Mount
Beginner

My SPA122 running v1.3.1 (003) is still going strong since I installed the firmware on Dec 17 at 12:47PM. That's nearly 17 days up, which looks promising so far.

My two SPA122s running v1.1.0 and v1.2.1 last froze on Dec 26 at 6:05PM; I rebooted them then.

Dale – thanks for your notes about SNMP. I checked out my three devices, and although I don't have SNMP enabled, I also don't expressly disable it via provisioning. Since it's nothing that we use in our environments, I may just add that config parameter for good measure.

I think I may have mis-stated my experience with the reboot process.  As I recall it was the reboot that followed a SIP NOTIFY REBOOT from the PBX that does not do a full cold start (but I think it should).  It has been a few weeks since I tried this but as I think more about it, the GUI reboot is a full reboot (and then so is Mike's rebooter utility).  I don't want to take the unit down to test this but that's my current recollection.  Sorry if I pointed anybody in the wrong direction on that topic! --Dale

1.3.1. (003) - 17 days and counting....

mifreymond
Beginner

Hello,

I am running 1.3.1 (003).  My current uptime is 10.53 days.

It has not had much use for 7 of those days (away on vacation).

The SPA is behind a router, connected to a aDSL circuit.

Today, my IP address changed. 

When the IP changed, the SPA lost it's registration, and failed to recover it.   Since I was at work, I was limited in what I could do.

In order to make it re-register, I clicked the submit button.  It reregistered and is now working fine.  It did not reboot the SPA as the uptime did not reset.

My syslogs are here:

Any help is appreciated.

Thu Jan 03 12:03:57 2013: <45>Jan  3 12:04:29 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 12:13:57 2013: <45>Jan  3 12:14:29 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 12:23:57 2013: <45>Jan  3 12:24:29 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 12:33:57 2013: <45>Jan  3 12:34:29 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 12:43:58 2013: <45>Jan  3 12:44:30 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 12:53:58 2013: <45>Jan  3 12:54:30 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 12:57:44 2013: <29>Jan  3 12:58:17 SPA112 system[103]: NTP update successfully, Year:2013,Month:1,Day:3,Hour:12,Min:58,Sec:17

Thu Jan 03 13:03:58 2013: <45>Jan  3 13:04:31 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 13:13:58 2013: <45>Jan  3 13:14:31 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 13:23:59 2013: <45>Jan  3 13:24:31 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 13:33:59 2013: <45>Jan  3 13:34:31 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 13:43:59 2013: <45>Jan  3 13:44:31 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 13:53:59 2013: <45>Jan  3 13:54:32 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 14:03:59 2013: <45>Jan  3 14:04:32 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 14:14:00 2013: <45>Jan  3 14:14:32 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 14:24:00 2013: <45>Jan  3 14:24:32 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 14:34:00 2013: <45>Jan  3 14:34:32 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 14:44:00 2013: <45>Jan  3 14:44:33 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 14:54:00 2013: <45>Jan  3 14:54:33 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 15:04:01 2013: <45>Jan  3 15:04:33 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 15:14:01 2013: <45>Jan  3 15:14:33 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 15:24:01 2013: <45>Jan  3 15:24:33 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 15:34:01 2013: <45>Jan  3 15:34:34 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 15:44:01 2013: <45>Jan  3 15:44:34 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 15:44:24 2013: <29>Jan  3 15:44:57 SPA112 system[103]: NTP update successfully, Year:2013,Month:1,Day:3,Hour:15,Min:44,Sec:57

Thu Jan 03 15:54:01 2013: <45>Jan  3 15:54:34 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 16:04:01 2013: <45>Jan  3 16:04:34 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 16:14:01 2013: <45>Jan  3 16:14:34 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 16:24:02 2013: <45>Jan  3 16:24:35 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 16:34:02 2013: <45>Jan  3 16:34:35 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 16:44:02 2013: <45>Jan  3 16:44:35 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 16:54:02 2013: <45>Jan  3 16:54:35 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 17:04:02 2013: <45>Jan  3 17:04:35 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 17:14:03 2013: <45>Jan  3 17:14:36 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 17:24:03 2013: <45>Jan  3 17:24:36 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 17:34:03 2013: <45>Jan  3 17:34:36 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 17:44:03 2013: <45>Jan  3 17:44:36 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 17:54:03 2013: <45>Jan  3 17:54:36 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 18:04:04 2013: <45>Jan  3 18:04:37 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 18:14:04 2013: <45>Jan  3 18:14:37 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 18:23:35 2013: <29>Jan  3 18:24:07 SPA112 msgswitchd[162]:   MSGSWD RTCP Reqt len 12 Data 2,4051584,0,0

Thu Jan 03 18:24:04 2013: <45>Jan  3 18:24:37 SPA112 syslog-ng[118]: STATS: dropped 0

Thu Jan 03 18:25:31 2013: <29>Jan  3 18:26:04 SPA112 msgswitchd[162]:   MSGSWD RTCP Reqt len 12 Data 2,4051584,0,0

Thu Jan 03 18:25:45 2013: <6>Jan  3 18:26:18 SPA112 [18070517.564000] cordless: deinit

Thu Jan 03 18:26:00 2013: <6>Jan  3 18:26:32 SPA112 [18070531.684000] cordless: loading synergy-2012-11-05

Thu Jan 03 18:26:00 2013: <6>Jan  3 18:26:32 SPA112 [18070531.716000] cordless: init successful

Thu Jan 03 18:26:02 2013: <13>Jan  3 18:26:34 SPA112 msgswitchd:  MSGSWITCH fd_rtp fifo created 7

Thu Jan 03 18:26:02 2013: <13>Jan  3 18:26:34 SPA112 msgswitchd:  MSGSWITCH fd_ch fifo created 9

Thu Jan 03 18:26:02 2013: <13>Jan  3 18:26:34 SPA112 msgswitchd:  MSGSWITCH fd_gmep fifo created 10

Thu Jan 03 18:26:49 2013: <29>Jan  3 18:27:21 SPA112 msgswitchd[2144]:   MSGSWD RTCP Reqt len 12 Data 2,4056952,0,0

Thu Jan 03 18:31:04 2013: <29>Jan  3 18:31:37 SPA112 system[103]: NTP update successfully, Year:2013,Month:1,Day:3,Hour:18,Min:31,Sec:37

Thu Jan 03 18:34:05 2013: <45>Jan  3 18:34:37 SPA112 syslog-ng[118]: STATS: dropped 0



daleschultz
Beginner

Mine has been up for 19.5 days on FW 1.3.1(003) with Full DEBUG logging and SNMP queries every 5 minutes, CDP disabled.  I have not had to deal with an IP change recently so I'm not sure how well the new FW handles that.

Yes I have tested and experienced the same up time results in both SPA112 &122s.  but another issue has reared its ugly head in all of our SPA112's but so far not in our SPA122's test boxes. 

But this provisioning rules just doesn't work for us in our SPA112 boxes so far in this beta testing firmware. 

supersecretpassword

I think you have to nest it inside the and the tags, otherwise it behaves a little funny. i.e.

    

          supersecretpassword

    

There's probably many other settings you have in your file, but that's the general gist of it. Goto http://ata-ip/admin/config.xml to figure out the correct location of each setting

  Tthat was the issue,  once placed the rule within the correct boundaries and added another coffee to my day, that solved the issue. 

Thanks Terry

Aaron Mount
Beginner

So far, my v1.3.1 SPA122 has 531 hours (22+ days) of uptime, which is far better than the 215-hour (8-9 day) average I see  from my v1.1.0 and v1.2.1 devices.

I have the same question for the Cisco guys as Terry – do we have an idea of when the official release might be? I have about ten users who are rather upset about the continued issues, and I'm almost tempted to roll out the v1.3.1 (003) beta to those persistent few, with the express understanding that it's a beta release. Should I hang tight for just a bit longer, or push it to their devices?

I know how much work and testing goes into a release; I'm not suggesting that Cisco isn't doing their due diligance, I'm just also trying to look out for my users. Thanks to Cisco's engineers and developers, and to the Community, for all the work and feedback.

laharper
Community Member

Hello Everyone,

We have now finalized our testing and we are now proceeding to post v1.3.1(003) as the official firmware release for the SPA112 and SPA122 ATA.

The expected date of the firmware to be posted on our Cisco web site is Friday January 11, 2013.

I would like to express my appreciation to all of the SPA ATA users that provided information that helped us troubleshoot and create this latest firmware release.

Sincerely,

Lance Harper

Product Manager

Lance,

It's been a long time coming, but that's great news. Look forward to seeing the release notes as well

Thanks

Hi:

Has there been any problems reported with fax and modem connections with this new version of FW?

I have a security system that reports to a central station just fine using FW 1.2.1 but it does not work at all with any 1.3.x versions I been given to test.

Does someone know what might have changed, maybe some setting default that I can correct?

Thanks,

Dale

Sinisa Bandin
Beginner

Hello Patrick and others,

just to add my 2 euro cents to the talk: I have installed 1.3.1(003) on all of my 7 SPA's on Jan 4 and have nod had problems since.

In any case, I have disabled SNMP as someone suggested, but will try to enable it on one of the SPA's, just to see if that would make any difference...

Best regards,

Siniša

xhuntersh
Beginner

its been a month, any new news on 1.3.2?