asterisk users - Jan 2005 - Segmentation Fault after Digitnetwork X100P install

I've just installed a Digitnetworks X100P clone in my * server and run 
the install script for the voicepet-single-x100p tarball. The install 
appeared to run OK with modprobe wcfxo successful and the ztcfg 
reporting "Channel 01: FXS Kewlstart (Default) (Slaves: 01)".

When I try to start * though I get a segmentation fault after loading 
res_features.so. I discovered that the Digitnetwork install script seems 
to modify all of the .conf files, leaving .conf.old copies. I tried 
moving the .conf.old files back to .conf but am still get the seg fault.

Has anyone else run into this kind of problem ?   The * server has been 
running fine up until now.

I can't get it to show the * version right now, but compiled from CVS 
around 11 Jan.

Dave



--------
CAUTION:
This message and any attachments contain privileged and confidential
information.  If you are not the intended recipient of this message, you
are hereby notified that any use, dissemination, distribution or
reproduction of this message is prohibited. If you have received this
message in error please notify the sender immediately via email and then
destroy this message and any attachments.

Any views expressed in this message are those of the individual sender
and may not necessarily reflect the views of Winstone Pulp International
Ltd.

Just download 1.0.3, don't use the voicepet scripts.  they are versions 0.7 
and 0.9 of  *.  If it is a true clone from digit networks it will work fine 
with 1.0.3.  I just set up 3 different machines with the cards from digit 
networks.

Henry

----- Original Message ----- 
From: "Dave Green" <dave.green@winpulp.co.nz>
To: "Asterisk Users Mailing List - Non-Commercial Discussion" 
<asterisk-users@lists.digium.com>
Sent: Thursday, January 20, 2005 9:57 PM
Subject: [Asterisk-Users] Segmentation Fault after Digitnetwork X100P 
install

> I've just installed a Digitnetworks X100P clone in my * server and run
the
> install script for the voicepet-single-x100p tarball. The install appeared 
> to run OK with modprobe wcfxo successful and the ztcfg reporting
"Channel
> 01: FXS Kewlstart (Default) (Slaves: 01)".
>
> When I try to start * though I get a segmentation fault after loading 
> res_features.so. I discovered that the Digitnetwork install script seems 
> to modify all of the .conf files, leaving .conf.old copies. I tried moving 
> the .conf.old files back to .conf but am still get the seg fault.
>
> Has anyone else run into this kind of problem ?   The * server has been 
> running fine up until now.
>
> I can't get it to show the * version right now, but compiled from CVS 
> around 11 Jan.
>
> Dave
>
>
>
> --------
> CAUTION:
> This message and any attachments contain privileged and confidential
> information.  If you are not the intended recipient of this message, you
> are hereby notified that any use, dissemination, distribution or
> reproduction of this message is prohibited. If you have received this
> message in error please notify the sender immediately via email and then
> destroy this message and any attachments.
>
> Any views expressed in this message are those of the individual sender
> and may not necessarily reflect the views of Winstone Pulp International
> Ltd.
>
>
> _______________________________________________
> 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
>

On Fri, 2005-01-21 at 16:57 +1300, Dave Green wrote:
> I've just installed a Digitnetworks X100P clone in my * server and run 
> the install script for the voicepet-single-x100p tarball. The install 
> appeared to run OK with modprobe wcfxo successful and the ztcfg 
> reporting "Channel 01: FXS Kewlstart (Default) (Slaves: 01)".
> 
> When I try to start * though I get a segmentation fault after loading 
> res_features.so. I discovered that the Digitnetwork install script seems 
> to modify all of the .conf files, leaving .conf.old copies. I tried 
> moving the .conf.old files back to .conf but am still get the seg fault.
Shouldn't you contact your vendor for support and not a different
vendors support channel?


Another company with retarded disclaimers sending to a KNOWN publicly
archived mailing list. Fix the problem or be ridiculed regularly for the
stupidity.
> --------
> CAUTION:
> This message and any attachments contain privileged and confidential
> information.  If you are not the intended recipient of this message, you
> are hereby notified that any use, dissemination, distribution or
> reproduction of this message is prohibited. If you have received this
> message in error please notify the sender immediately via email and then
> destroy this message and any attachments.
> 
> Any views expressed in this message are those of the individual sender
> and may not necessarily reflect the views of Winstone Pulp International
> Ltd.
-- 
Steven Critchfield <critch@basesys.com>