Over the weekend I tried to migrate a system from
asterisk 1.4.25, libpri 1.4.1 ZAPTEL 1.4.12.1
to
asterisk 1.4.25, libpri 1.4.7 (not 1.4.1) and DAHDI 2.2.0
I removed all old zaptel by:
mv /etc/zaptel.conf /tmp
mv /etc/asterisk/zapata.conf /tmp
rm /etc/init.d/zaptel
rm /etc/sysconfig/zaptel
rm /etc/modprobe.d/zaptel 2> /dev/null > /dev/null
rm /etc/udev/rules.d/zaptel.rules
rm /etc/rc.d/rc*/*zaptel
rm /sbin/zt*
rm -rf /usr/share/zaptel
rm -rf /usr/include/zaptel
Then I just did a CLEAN install of dahdi, libpri and asterisk again.
After upgrading incoming calls seemed to work just fine.
Outgoing calls gave me an error 99
I have a TE205P installed.
I did change the extensions.conf to use DAHDI and not Zap.
I had to quickly change back as it is a production system.
Any thoughts on what might have happened here?
I didnt know if have two libpri versions confused things or what?
ANy thoughts for the next time I try are appreciated.
Jerry
On Jul 6, 2009, at 10:00 AM, Jerry Geis wrote:> Over the weekend I tried to migrate a system from > asterisk 1.4.25, libpri 1.4.1 ZAPTEL 1.4.12.1 > > to > asterisk 1.4.25, libpri 1.4.7 (not 1.4.1) and DAHDI 2.2.0 > > I removed all old zaptel by: > mv /etc/zaptel.conf /tmp > mv /etc/asterisk/zapata.conf /tmp > > rm /etc/init.d/zaptel > rm /etc/sysconfig/zaptel > rm /etc/modprobe.d/zaptel 2> /dev/null > /dev/null > rm /etc/udev/rules.d/zaptel.rules > rm /etc/rc.d/rc*/*zaptel > rm /sbin/zt* > rm -rf /usr/share/zaptel > rm -rf /usr/include/zaptel > > Then I just did a CLEAN install of dahdi, libpri and asterisk again. > > After upgrading incoming calls seemed to work just fine. > Outgoing calls gave me an error 99 > > > I have a TE205P installed. > > I did change the extensions.conf to use DAHDI and not Zap. > > I had to quickly change back as it is a production system. > > Any thoughts on what might have happened here? > I didnt know if have two libpri versions confused things or what? > > ANy thoughts for the next time I try are appreciated. >Jerry, Check the dahdichanname setting in asterisk.conf. I had the same issue myself - Niles
Having gone through similar pains myself, I highly recommend going the the SVN asterisk 1.4 branch. I have had far fewer headaches following this path. -----Original Message----- From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Niles Ingalls Sent: Monday, July 06, 2009 9:34 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] migrate from zaptel to dahdi On Jul 6, 2009, at 10:00 AM, Jerry Geis wrote:> Over the weekend I tried to migrate a system from > asterisk 1.4.25, libpri 1.4.1 ZAPTEL 1.4.12.1 > > to > asterisk 1.4.25, libpri 1.4.7 (not 1.4.1) and DAHDI 2.2.0 > > I removed all old zaptel by: > mv /etc/zaptel.conf /tmp > mv /etc/asterisk/zapata.conf /tmp > > rm /etc/init.d/zaptel > rm /etc/sysconfig/zaptel > rm /etc/modprobe.d/zaptel 2> /dev/null > /dev/null > rm /etc/udev/rules.d/zaptel.rules > rm /etc/rc.d/rc*/*zaptel > rm /sbin/zt* > rm -rf /usr/share/zaptel > rm -rf /usr/include/zaptel > > Then I just did a CLEAN install of dahdi, libpri and asterisk again. > > After upgrading incoming calls seemed to work just fine. > Outgoing calls gave me an error 99 > > > I have a TE205P installed. > > I did change the extensions.conf to use DAHDI and not Zap. > > I had to quickly change back as it is a production system. > > Any thoughts on what might have happened here? > I didnt know if have two libpri versions confused things or what? > > ANy thoughts for the next time I try are appreciated. >Jerry, Check the dahdichanname setting in asterisk.conf. I had the same issue myself - Niles _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
> > Jerry, > Check the dahdichanname setting in asterisk.conf. I had the same issue > myself - Niles > >Niles, I did a grep -i dahdichanname /etc/asterisk/* and no results. Jerry
On Mon, Jul 06, 2009 at 10:00:12AM -0400, Jerry Geis wrote:> After upgrading incoming calls seemed to work just fine. > Outgoing calls gave me an error 99What is the outout of: cat /proc/dahdi/* Can you provide a trace of such a failed call? -- Tzafrir Cohen icq#16849755 jabber:tzafrir.cohen at xorcom.com +972-50-7952406 mailto:tzafrir.cohen at xorcom.com http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir