I commented out the 2 lines (Answer, NVFaxDetect) and re-faxed
myself... no segfault. It does appear NVFaxDetect is the culprit. Has
anyone else seen a similar issue?
cheers,
S.
> Lonnie,
>
> This segfaults every time the incoming call is a fax. There is no
> problem if it is a regular voice c
Lonnie,
This segfaults every time the incoming call is a fax. There is no
problem if it is a regular voice call... that has been and still is
working normally. I will try commenting out the NVFaxDetect line and
report back...
For reference, here is my extensions.conf:
[incoming]
exten =>
-- Executing [fax@incoming:1]
> Hangup("IAX2/outbound-unlimitel-5255", "") in new stack
> == Spawn extension (incoming, fax, 1) exited non-zero on
> 'IAX2/outbound-unlimitel-5255'
> -- Hungup 'IAX2/outbound-unlimitel-5255'
>-- Hungup &#
tack
== Spawn extension (incoming, fax, 1) exited non-zero on
'IAX2/outbound-unlimitel-5255'
-- Hungup 'IAX2/outbound-unlimitel-5255'
-- Hungup 'IAX2/outbound-unlimitel-7119'
== Spawn extension (outbound_fax, 7057974880, 2) exited non-zero on
'DAHDI/
Shamus,
Great description, I think you have a finger on the problem. I'm not sure
NVFaxDetect() is the problem, but definitely is in the path.
Do you understand why your Dial(IAX2/iaxmodem) is failing with BUSY?
If you can, disable the iaxmodem call
exten => fax,1,Hangup
and see if the segfau
something else?
> Message: 2
> Date: Mon, 17 Jan 2011 14:59:25 -0600
> From: Lonnie Abelbeck
> Subject: Re: [Astlinux-users] segfault error
> To: AstLinux Users Mailing List
> Message-ID: <[email protected]>
> Content-Type: text/
sorry for the re-post... forgot to change the subject.
I did the upgrade to 0.7.5 about a week ago. These errors didn't start
to occur until a couple of days ago; since then, they've been
consistent every 24-40 hours. No other changes have been made... could
this be a dying CF card?
cheers,
S.
Do you have Change The eth0 to other?¿can you to acess The Gui-astlinux?
Enviado desde mi iPhone
El 17/01/2011, a las 17:15, Shamus Rask escribió:
> I've been using AstLinux for > 1 year now and it has been wonderfully stable.
> Recently, I've started to receive the following error every ~40 h
Shamus,
I suppose it could be a dying CF card.
Unless this thread generates other reports with similar segfaults, it seems
unique to your setup.
In your asterisk config, are you using CURL() or system() calls, or other
things reaching outside of asterisk?
Lonnie
On Jan 17, 2011, at 2:07 PM,
On Jan 17, 2011, at 12:22 PM, Shamus Rask wrote:
> Lonnie,
>
> AstLinux 0.7.5 (generic x86)
> Asterisk 1.4.36 with a single WCTDM/4 Wildcard board with 1x FXO, 2x
> FXS installed
> runnix 0.3.2
Hmmm, seems pretty standard. If you have any clues on what may have changed on
your setup (upgrade,
Lonnie,
AstLinux 0.7.5 (generic x86)
Asterisk 1.4.36 with a single WCTDM/4 Wildcard board with 1x FXO, 2x
FXS installed
runnix 0.3.2
manager.conf already has the entries as you outlined. My comment was
that on receiving the "segfault" error, Asterisk seems to die and I'm
unable to restart it thro
Shamus,
What AstLinux version are your using? What asterisk version?
Michael has seen the same asterisk segfault, but only with asterisk 1.4.37+, we
have only shipped 1.4.36 because of that reason.
Are you using mISDN ? anything unusual?
Regarding the web interface and "Reload Asterisk Modu
I've been using AstLinux for > 1 year now and it has been wonderfully
stable. Recently, I've started to receive the following error every ~40
hours:
Jan 17 09:54:54 pbx user.info kernel: asterisk[1713]: segfault at 62616237
> ip 400a5625 sp bebfb29c error 4 in libuClibc-0.9.28.so[4006e000+44000]
13 matches
Mail list logo
