[Asterisk-Users] nasty segfault with previous strange Zaptel warnings
Thomas Haeger
asterisk-mailing at beronet.com
Tue Feb 17 06:54:43 MST 2004
Hi all,
i try to get help from you guys.
I have wrote a little call generation script that generate calls every few
minutes on a PRI Line which is connected through as E400P...
#! /usr/bin/php4
<?
$numbers=file("/home/thaeger/callscript/numbers.list");
while (true) {
foreach ($numbers as $number) {
if (substr($number,0,1) != "#") {
// echo ("$number");
$fh = fopen("/var/spool/asterisk/outgoing/call.$number",w);
fputs ($fh,"Channel: Zap/g2/01033$number\nMaxRetries:
0\nWaitTime: 5\nContext: callgen\nExtension: 1\nPr
fclose($fh);
sleep(5);
}
}
sleep(120);
}
?>
On the other side there comes everytime a call rejection, and it should be
so.
The normal log output must look like this:
-- Attempting call on Zap/g2/0103302289319048 for 1 at callgen:1 (Retry 1)
-- Hungup 'Zap/32-1'
Feb 17 13:04:26 NOTICE[376852]: pbx_spool.c:199 attempt_thread: Call failed
to go through, reason 3
But then sometimes there comes strange warnigs:
-- Attempting call on Zap/g2/01033028712747781 for 1 at callgen:1 (Retry 1)
-- Moving call from channel 1 to channel 19
Feb 17 13:04:43 WARNING[442388]: chan_zap.c:595 zt_get_index: Unable to get
index, and nullok is not asserted
Feb 17 13:04:43 WARNING[442388]: chan_zap.c:3425 zt_read: We dont exist?
-- Hungup 'Zap/32-1'
Or like this:
Feb 17 12:52:00 WARNING[589843]: chan_zap.c:3992 zt_new: Channel 32 already
has a Real call
Feb 17 12:52:32 WARNING[688147]: chan_zap.c:595 zt_get_index: Unable to get
index, and nullok is not asserted
Feb 17 12:52:32 WARNING[688147]: chan_zap.c:3425 zt_read: We dont exist?
And after a few minutes, so between 20 and 60, there comes a nasty SEGFAULT
with these messages:
/usr/sbin/safe_asterisk: line 6: 18118 Segmentation fault asterisk
${ASTARGS} 1>&/dev/${TTY} </dev/${TTY}
Asterisk ended with exit status 139
Asterisk exited on signal 11.
Automatically restarting Asterisk.
Asterisk ended with exit status 1
Asterisk died with code 1. Aborting.
Automatically restarting Asterisk.
Asterisk ended with exit status 1
Asterisk died with code 1. Aborting.
Automatically restarting Asterisk.
Asterisk ended with exit status 1
Asterisk died with code 1. Aborting.
Automatically restarting Asterisk.
Disconnected from Asterisk server
Executing last minute cleanups
Have somebody an idea what the problem is ?
The Zap Hardware which is running on my machine is a E400P.
Thanks for help.
Best regards,
Thomas.
More information about the asterisk-users
mailing list