[Asterisk-Users] ZT_CHANCONFIG failed on channel 1 - WAS WORKING!!

Mark Edwards mark.p.edwards at gmail.com
Sat Aug 20 07:32:06 MST 2005


concur that the best way around this is to perioically restart.

FWIW this is my restart script which I invoke from cron in the middle
of the night...

#!/bin/bash
ASTERISK=/usr/sbin/asterisk
RMMOD=/sbin/rmmod
MODPROBE=/sbin/modprobe
ZTCFG=/sbin/ztcfg

echo "Stopping"
$ASTERISK -rx "stop when convenient"
if [ $? == 0 ]; then

        #let COUNT=0
        while true; do
                echo "waiting for asterisk to stop"
                if [ ! -e /var/run/asterisk.pid ]; then
                        break;
                fi
                sleep 5;
                echo "."
        #       let COUNT=COUNT+1
        #       if [ $COUNT == 40 ]; then
        #               break;
        #       fi
        done

fi

echo unloading modules....
$RMMOD wctdm
sleep 5
$RMMOD zaptel
sleep 15
killall -9 mpg123
echo loading modules
$MODPROBE zaptel
sleep 15
$MODPROBE wctdm
sleep 15
$ZTCFG -v
sleep 5
echo "Starting...."
$ASTERISK


mark

On 8/20/05, Rich Adamson <radamson at routers.com> wrote:
> Seems the latest distro's have changed the layout of the linux source tree
> needed to compile the zaptel stuff. I'm using FC3, upgraded the kernel, and
> have the same issue. Was able to install new sources, but they too are
> completely different tree layout compared to earlier stuff. The same is
> apparently happening with other distro's as well.
> 
> There has been a bug item open for last several weeks relative to reworking
> the make files for these items.
> 
> ------------------------
> >
> > That suggestion is possibly on the right track.  It made me remember that -
> > although I'm not using Fedora, but SuSE 9.3, that it went through an
> > automatic network update just recently.  After that, I tried updating the
> > Zaptel files from CVS and recompiling everything, but to no avail.  The
> > same error still occured.  I eliminated hardware by swapping out a working
> > TDM400 with the same FXS/FXO configuration.  The same error occurs.  The
> > SuSE update may have moved some of the required files, although there are
> > no complaints during the build and I can't determine what may have moved.
> >
> > I have still present and installed Bison 1.875, OpenSSL and zlib-devel, and
> > of course Linux source for this SuSE disto.  I'm completely faklempt!  Can
> > someone shed light on this delima??   Thanks so much if you can.  I want my
> > As-terisk back!!!  It was working, damnit.   Thanks, Matt for your suggestion.
> >
> > Scott
> >
> > At 09:30 PM 8/19/2005, you wrote:
> > >sbrown at andersonis.com wrote:
> > > >
> > > > Hi:
> > > > I hope that someone can help with this problem that came up suddenly. I
> > >
> > >Did you upgrade Fedora Core?
> > >
> > >Check if the udev files still contain the required entries (normally fedora
> > >copies the old ones to 50-udev-rules.old and makes new ones).
> 
> 
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at 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
> 


-- 
regards,

Mark P. Edwards
FWD: 667917



More information about the asterisk-users mailing list