thr3ads.net - asterisk users - [Asterisk-Users] SPA-2000's rebooting every hour or so... [Oct 2004]

If this information is useful, please help other people find it:
Share via:

Mike Benoit

2004-Oct-14 10:36 UTC

[Asterisk-Users] SPA-2000's rebooting every hour or so...

I realize this is slightly off-topic here, but I know quite a few people
on this list use Sipura products. Has anyone else experienced the same
rebooting problem I'am? 

I have about 8 SPA-2000's and about half of them just started rebooting
4-8times/day in the last month or so. (they used to be rock solid) 

I already emailed Sipura support, but they seem to be "on strike" as
of
late. 

Here is the debug output from just one of the devices: (I've trimmed it
for size, it happens more often than what is shown)

Oct 12 08:18:33 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 12 08:18:33 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 12 08:33:37 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 12 08:33:37 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 12 08:53:52 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 12 08:53:52 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 12 21:34:14 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 11:20:55 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 11:28:31 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:28:31 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:48:55 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:48:55 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:53:08 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 11:53:08 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 11:54:23 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:54:23 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:55:15 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:55:15 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:56:46 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:56:46 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:59:05 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:59:05 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 12:40:58 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 12:40:58 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 14:00:51 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 13 14:00:51 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 13 15:20:54 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 13 15:20:54 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 13 16:44:57 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 16:44:57 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 18:01:03 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 18:01:03 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 19:21:06 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 19:21:06 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 22:01:05 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 13 22:01:05 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 13 23:21:17 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 23:21:17 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 00:41:20 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 00:41:20 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 02:01:20 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 02:01:20 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 03:21:23 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 03:21:23 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 04:41:24 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 04:41:24 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 06:01:29 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 06:01:29 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 08:08:18 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 08:08:18 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 08:28:24 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 08:28:24 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 09:08:26 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 09:08:26 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0



-- 
Mike Benoit <ipso@snappymail.ca>

versini

2004-Oct-14 10:55 UTC

head link

[Asterisk-Users] Record and Maxduration not working... sometimes

Hi all!

I have an * box that I use to record existing calls via a 3rd leg that
I conference with the existing call via another PBX (which is not able
to do recordings)....
The recording is limited to 20 sec even if the existing call lasts longer.
Here is an extract from my extension.conf:
----
exten => _123.,1,Record(/tmp/record/${EXTEN}:WAV|0|20)
exten => _123.,2,Hangup
----

This is working fine within the normal case... However, if * is too
busy to answer in time, I have a timeout on the other PBX which then
sends a CANCEL. Unfortunately, when * is at last available, it picks
up the INVITE, start to record the call and never treats the CANCEL...
Because of that situation, I have several ghost channels of recording,
not recording anything...

To reproduce this behavior, I can simply suspend * (CTRL Z on the
runing console), try to start the recording, hang up, and reactivate *
(fg)...

Does anyone know if I'm doing something wrong?
Thanks  for your help!
Arno

Dooz Owings

2004-Oct-14 12:36 UTC

head link

[Asterisk-Users] SPA-2000's rebooting every hour or so...

try to run a firmware update on one and see if it works, just a guess. What
all have you tried ?

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com]On Behalf Of Mike Benoit
Sent: Thursday, October 14, 2004 10:36 AM
To: asterisk-users@lists.digium.com
Subject: [Asterisk-Users] SPA-2000's rebooting every hour or so...


I realize this is slightly off-topic here, but I know quite a few people
on this list use Sipura products. Has anyone else experienced the same
rebooting problem I'am?

I have about 8 SPA-2000's and about half of them just started rebooting
4-8times/day in the last month or so. (they used to be rock solid)

I already emailed Sipura support, but they seem to be "on strike" as
of
late.

Here is the debug output from just one of the devices: (I've trimmed it
for size, it happens more often than what is shown)

Oct 12 08:18:33 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 12 08:18:33 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 12 08:33:37 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 12 08:33:37 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 12 08:53:52 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 12 08:53:52 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 12 21:34:14 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 11:20:55 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 11:28:31 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:28:31 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:48:55 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:48:55 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:53:08 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 11:53:08 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 11:54:23 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:54:23 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:55:15 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:55:15 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:56:46 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:56:46 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:59:05 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 11:59:05 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:C200
Oct 13 12:40:58 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 12:40:58 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 14:00:51 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 13 14:00:51 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 13 15:20:54 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 13 15:20:54 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 13 16:44:57 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 16:44:57 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 18:01:03 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 18:01:03 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 19:21:06 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 19:21:06 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 22:01:05 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 13 22:01:05 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H73720143
Oct 13 23:21:17 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 13 23:21:17 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 00:41:20 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 00:41:20 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 02:01:20 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 02:01:20 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 03:21:23 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 03:21:23 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 04:41:24 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 04:41:24 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 06:01:29 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 06:01:29 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 08:08:18 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 08:08:18 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 08:28:24 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 08:28:24 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 09:08:26 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0
Oct 14 09:08:26 192.168.1.189 System started: ip@192.168.1.189, reboot
reason:H0



--
Mike Benoit <ipso@snappymail.ca>

_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

asterisk users - Oct 2004 - SPA-2000's rebooting every hour or so...

[Asterisk-Users] SPA-2000's rebooting every hour or so...

[Asterisk-Users] Record and Maxduration not working... sometimes

[Asterisk-Users] SPA-2000's rebooting every hour or so...