AIL PROTECTED]>
Sent: Wednesday, January 07, 2004 11:05 AM
Subject: RE: [Asterisk-Users] * crashed
May be it's due to a kernel patch ... ??
Try to recompile zaptel, asterisk, ...
Van: Jess Magnaye [mailto:[EMAIL PROTECTED]
Verzonden: wo 7/01/2004 17:3
On Wed, Jan 07, 2004 at 10:56:14AM -0600, Tilghman Lesher wrote:
> >
> > WARNING[1074412224]: File loader.c, Line 312 (ast_load_resource):
> > chan_zap.so: load_module failed, returning -1 Segmentation fault
> > (core dumped)
>
> Did you remember to reload the kernel modules for your specific
> ha
May be it's due to a kernel patch ... ??
Try to recompile zaptel, asterisk, ...
Van: Jess Magnaye [mailto:[EMAIL PROTECTED]
Verzonden: wo 7/01/2004 17:36
Aan: [EMAIL PROTECTED]
Onderwerp: [Asterisk-Users] * crashed
nesday, January 07, 2004 11:52
AM
Subject: RE: [Asterisk-Users] *
crashed
Are you doing these
items before trying to start asterisk:
loadmod driver (In my case its wcfxo)
After that is
completed:
Ztcfg
This configures all
On Wednesday 07 January 2004 10:36, Jess Magnaye wrote:
> I am just wondering if this is normal. I have my * running for a
> week now and I'm still testing its interoperability with other voip
> provider (in sip using codecs other than g711). yesterday, i
> changed my linux's (RH9). and since the
automatically.
- Brent
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jess Magnaye
Sent: Wednesday, January 07, 2004
11:36 AM
To:
[EMAIL PROTECTED]
Subject: [Asterisk-Users] *
crashed
Importance: High
I am just wondering if this is
normal. I
I am just wondering if this is normal. I have
my * running for a week now and I'm still testing its interoperability with
other voip provider (in sip using codecs other than g711). yesterday, i changed
my linux's (RH9). and since the new ip i assigned is located on a different
site, i have
Assuming you haven't cvs updated yet I can look at this problem but I need
matching sources/binaries/cores. If you've cvs updated, there isn't much
I can do.
Mark
On Thu, 27 Nov 2003, Tais M. Hansen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thursday 27 November 2003 05:57,
slack here too - * is working STABLE
Lubo
Tais M. Hansen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 27 November 2003 05:57, Patrick Cantwell wrote:
Just for the record, I'm using a slackware 9.0 and a slackware 9.1 box
with asterisk, and I had no problems obtaining, buildin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 27 November 2003 05:57, Patrick Cantwell wrote:
> Just for the record, I'm using a slackware 9.0 and a slackware 9.1 box
> with asterisk, and I had no problems obtaining, building/compiling, or
> running asterisk with a fresh install.
I'll
Just for the record, I'm using a slackware 9.0 and a slackware 9.1 box
with asterisk, and I had no problems obtaining, building/compiling, or
running asterisk with a fresh install.
-Pat
On Wed, 26 Nov 2003, Clif Jones wrote:
> Thanks for the truly useful feedback. I'm having a real hard time wi
Thanks for the quick feedback! I don't have a lot of free time to play
with Asterisk
right now but a friend of mine wanted me to get it working on Red Hat
for him which
resulted in the RH problems/questions. Personally, I prefer Debian
which suites my
needs for embedded projects and hacked up
On Wed, Nov 26, 2003 at 01:55:36PM -0500, Clif Jones wrote:
> Thanks for the truly useful feedback. I'm having a real hard time with
> the FAQ pages listing
> RH 8 & 9 FIRST in the list of Linux distros that Asterisk compiles and
> runs on and having
> any bugs (oh I mean RH problems) discarded.
On Wed, 2003-11-26 at 12:55, Clif Jones wrote:
> Thanks for the truly useful feedback. I'm having a real hard time with
> the FAQ pages listing
> RH 8 & 9 FIRST in the list of Linux distros that Asterisk compiles and
> runs on and having
> any bugs (oh I mean RH problems) discarded. It would be
On Wed, Nov 26, 2003 at 01:55:36PM -0500, Clif Jones wrote:
> Thanks for the truly useful feedback. I'm having a real hard time with
> the FAQ pages listing
> RH 8 & 9 FIRST in the list of Linux distros that Asterisk compiles and
> runs on and having
> any bugs (oh I mean RH problems) discarded.
Thanks for the truly useful feedback. I'm having a real hard time with
the FAQ pages listing
RH 8 & 9 FIRST in the list of Linux distros that Asterisk compiles and
runs on and having
any bugs (oh I mean RH problems) discarded. It would be much more help
to have responses
such as yours or to ha
> Stop using RH9 since its majorly broken and that wont happen
Since not all of us are so enlightened, please complete the sentence
so that at least some of us have a clue as to the non-partisan issues?
No offense intended, but there really are folks here that would like t
Brian,
Since not all of us are so enlightened, please complete the sentence
so that at least some of us have a clue as to the non-partisan issues?
No offense intended, but there really are folks here that would like to
learn from other's experience however boring that might be.
-
Stop using RH9 since its majorly broken and that wont happen
bkw
On Tue, 25 Nov 2003, Clif Jones wrote:
> Also I have found that "safe_asterisk" needs to have something like
> "sleep 5" following the
> echo "Restarting Asterisk...". If not, asterisk will immediately exit
> with return code 1 a
Also I have found that "safe_asterisk" needs to have something like
"sleep 5" following the
echo "Restarting Asterisk...". If not, asterisk will immediately exit
with return code 1 after
restarting.
Clif Jones wrote:
I have finally crashed Asterisk for the first time and I'm wondering
if anyo
I have finally crashed Asterisk for the first time and I'm wondering if
anyone has seen this.
This is a configuration with SIP endpoints and an IAX2 channel to
another Asterisk PBX.
The main PBX dropped a core file after a SEGV (signal 11 ) with the
following trace:
#0 0x42079133 in strchr ()
21 matches
Mail list logo
