I thought that was the case. One thing I did try doing was to cp my zaptel.conf to chan_dahdi.conf. I'm sure that at least part of the problem was that I didn't have dahdi configured. However, after doing that dahdi is still not functional so I'm back on 0.6.8:
Nov 15 12:46:57 pbx local0.warn asterisk[1979]: WARNING[1979]: chan_dahdi.c:1233 in dahdi_open: Unable to specify channel 1: No such device or address Nov 15 12:46:57 pbx local0.err asterisk[1979]: ERROR[1979]: chan_dahdi.c:7669 in mkintf: Unable to open channel 1: No such device or address here = 0, tmp->channel = 1, channel = 1 Nov 15 12:46:57 pbx local0.err asterisk[1979]: ERROR[1979]: chan_dahdi.c:11298 in build_channels: Unable to register channel '1' -----Original Message----- From: Darrick Hartman [mailto:dhart...@djhsolutions.com] Sent: Sunday, November 15, 2009 11:06 AM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] Astlinux-0.7 Upgrade? As I recall wancfg requires several perl modules. The config files must be hand-generated as it's not feasible for us to include more than 'mini-perl' in AstLinux. Tom Mazzotta wrote: > This may be the problem. However with my original 0.6 system I needed to > prepare the wanpipe1.conf file off line because wancfg wouldn't run with > astlinux. The sangoma site says to run /usr/sbin/wancfg_dahdi, will I have > the same problems with wancfg under 0.7, or has that problem been fixed? As I > mentioned previously, my zaptel version of wanpipe1 was produced when I ran > FreeBSD on the net5501 (which I have since abandoned for various reasons). > How can I produce a dahdi version if 0.7 hasn't resolved the issues running > wancfg? Granted, this info is only a text file, so if I knew what needed to > be in the file for it to work, I'm happy to hand edit it. > > -tm > > -----Original Message----- > From: Lonnie Abelbeck [mailto:li...@lonnie.abelbeck.com] > Sent: Sunday, November 15, 2009 7:28 AM > To: AstLinux Users Mailing List > Subject: Re: [Astlinux-users] Astlinux-0.7 Upgrade? > > Anyone? could Tom's Sangoma issue be a wanpipe - DAHDI issue, since 0.7 is > built using DAHDI ? > > Tom, possibly your wanpipe1.conf needs to be changed reconfigured for DAHDI ? > > 0.7 uses wanpipe version 3.4.4 > > Lonnie > > > On Nov 14, 2009, at 11:26 PM, Darrick Hartman wrote: > >> Tom, >> >> Do you happen to have a spare Sangoma board and a spare system that we >> could get someone to connect in to? There are some changes between 0.6 >> and 0.7 with the Sangoma code. I really haven't used any of their >> hardware, but second hand from Philip, their package is a bit >> 'convoluted' compared to most. >> >> I'm swamped this weekend with a server migration, but perhaps some of >> the other users who actually have Sangoma boards would be able to >> provide some additional information. >> >> Darrick >> >> Tom Mazzotta wrote: >>> After reverting back to 0.6.8 I can confirm that 0.7 definitely has a >>> problem with Sangoma support. Now "wanrouter status" reports the board as >>> "connected" and I see a "wag1" i/f using ifconfig. And most importantly, my >>> FXO/FXS based channels all appear to be working normally again. >>> >>> Let me know if there is something you would like me to test to help resolve >>> the problem. I'm assuming that if I "revert to previous" the firmware will >>> go back to 0.7. >>> >>> -----Original Message----- >>> From: Tom Mazzotta [mailto:tmazzo...@titanmicro.com] >>> Sent: Saturday, November 14, 2009 6:21 PM >>> To: AstLinux Users Mailing List >>> Subject: Re: [Astlinux-users] Astlinux-0.7 Upgrade? >>> >>> Lonnie, >>> >>> [I'm taking the thread back onto the list] >>> >>> Correcting the NAT rules fixed the problem w/ Arno, at least for my local >>> system. I will trouble shoot the remote box next. >>> >>> Even after correcting the f/w problem and rebooting, my Sangoma board is >>> still disconnected: >>> >>> pbx ~ # wanrouter status >>> >>> Devices currently active: >>> wanpipe1 >>> >>> >>> Wanpipe Config: >>> >>> Device name | Protocol Map | Adapter | IRQ | Slot/IO | If's | CLK | Baud >>> rate | >>> wanpipe1 | N/A | A200/400/600| 10 | 14 | 0 | N/A | 0 >>> | >>> >>> Wanrouter Status: >>> >>> Device name | Protocol | Station | Status | >>> wanpipe1 | A-ANALOG | N/A | Disconnected | >>> >>> I should also see a wag i/f via ifconfig and I don't. Any ideas? Especially >>> if this is a legit problem w/ the beta release, I'd like to help out anyway >>> I can, but I do need to get the phones online in my house by tomorrow. >>> >>> -tm ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.