Re: [Astlinux-users] Astlinux-0.7 Upgrade?
Yeah, I'm still traumatized from previous dealings with Sangoma.
"Convoluted" is actually being quite generous. "Baroque" and "overly
complicated" don't begin to describe how they did things. Clearly, "KISS" is
not a known principle in their corporate culture.
They could have used automake, autoconf, the Linux firmware manager, udev
hooks, and Kbuild.
They did none of those, and chose instead to reinvent the wheel (square,
apparently).
I would suggest doing a build and seeing what the logs say.
toolchain/build is handy for this purpose.
On 11/14/2009 09: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
>> -Original Message-
>> From: Lonnie Abelbeck [mailto:li...@lonnie.abelbeck.com]
>> Sent: Saturday, November 14, 2009 6:01 PM
>> To: Tom Mazzotta
>> Subject: Re: [Astlinux-users] Astlinux-0.7 Upgrade?
>>
>> Tom,
>>
>> For your NAT -> DMZ, the Destination must be a single IP address not network
>> notation, so use 192.168.169.101 and not 192.168.169.101/32.
>>
>> So, click on the " + " by the NAT -> DMZ entries, delete the /32 for the
>> destination, save settings, and then delete the previous entry... all for
>> each NAT entry.
>>
>> Then restart the firewall...
>>
>> Let me know if that fixes your firewall errors.
>>
>> Now for the Sangoma, was you 0.7-beta built with wanpipe support? I know
>> basically nothing about Sangoma hardware, Darrick knows much more than I on
>> that. But we need to get this working. Could this be related to your
>> firewall problems?
>>
>> If you need to revert back, you should be able to use the System tab and
>> "Revert to Previous" {Firmware}, after the reboot, then follow the same
>> firewall 'upgrade' procedure for 0.7 to 0.6 as you did form 0.6 to 0.7.
>>
>>
>> Lonnie
>>
>>
>>
>> On Nov 14, 2009, at 4:31 PM, Tom Mazzotta wrote:
>>
>>
>>> Lonnie,
>>>
>>> I believe the problem is due to NAT -> DMZ port forwarding rules. Below you
>>> will find the errors. If I disable the rules and restart the f/w, I do not
>>> get the "Action Failed" warning. I don't understand why I have the problem;
>>> my DMZ i/f (eth3) is 192.168.169.1 and I am forwarding ports to an Xbox360
>>> on the DMZ at 192.168.169.101. The Xbox is mapped to that IP via its MAC
>>> using the "DNS Forwarder Hosts" form.
>>>
>>> Now the BIG problem is that my Sangoma board no longer functions following
>>> the upgrade. I have 2x FXO's connected to POTS lines from my cable modem
>>> service and 2x FXS ports connected to outside doorbell boxes. I can make
>>> extension calls via SIP without any problem in the house, however, I can't
>>> make/receive an outside call OR use the intercom on the doorbell boxes.
>>> FYI, the wanpipe1.conf file that I originally prepared using a FreeBSD
>>> system is still in th
Re: [Astlinux-users] Astlinux-0.7 Upgrade?
>This would imply that the define "CONFIG_PRODUCT_WANPIPE_TDM_VOICE" >is not set when wanpipe is build. > >This is definitely a Philip question... > >Lonnie Maybe it is even more complicated: When you look at ftp://ftp.sangoma.com/linux/current_wanpipe/ChangeLog.3.4 you'll see that Dahdi 2.2 support was added in Version 3.4.5 (the latest is 3.4.6) - we are using 3.4.4. > >On Nov 15, 2009, at 3:35 PM, Tom Mazzotta wrote: > >> Lonnie, >> >> These tips helped me make a lot of progress. On the remote system >>with the TDM card, "dahdi show status" is recognizing the card. >>However, my local system with the Sangoma board is still a problem. >>My concern is the message "wanpipe1: Error: TDM VOICE prot not >>compiled" reported by dmesg (see below). Is it possible that there >>is some required component of wanpipe that was left out of the 0.7 >>build I am testing? >> >> pbx ~ # dmesg | grep wanpipe >> wanpipe1: Running post initialization... >> wanpipe1: Remora config done! >> wanpipe1: AFT Data Mux Bit Map: 0x01234567 >> wanpipe1: Front End Interface Ready 0x >> wanpipe1: Register EC interface wanec1 (usage 1, max ec chans 32)! >> wanpipe1: Configuring Device :wanpipe1 FrmVr=11 >> wanpipe1:Global MTU = 1500 >> wanpipe1:Global MRU = 1500 >> wanpipe1:Data Mux Map = 0x01234567 >> wanpipe1:Rx CRC Bytes = 0 >> wanpipe1:Global TDM Int = Disabled >> wanpipe1:Global TDM Ring = Disabled >> wanpipe1:TDMV HW DTMF/FAX = Enabled/Disabled(0) >> wanpipe1:TDMV Span= 1 : Enabled >> wanpipe1:RTP TAP = Disabled >> wanpipe1: Error: TDM VOICE prot not compiled >> wanpipe1:during installation process! >> wanpipe1: Shutting Down! >> wanpipe1: TASKQ Not Running > > wanpipe1: Unconfiguring FXS/FXO Front End... > > wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Device Down) > > wanpipe1: Unregister interface from wanec1 (usage 1)! > > wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Device Down) >> wanpipe1: Global Chip Shutdown Usage=1 >> wanpipe1: Unconfiguring FXS/FXO Front End... >> wanpipe1: Master shutting down >> af_wanpipe: Unregistering Wanpipe API Socket Module >> wanpipe: WANPIPE Modules Unloaded. >> pbx ~ # >> >> -Original Message- >> From: Lonnie Abelbeck [mailto:li...@lonnie.abelbeck.com] >> Sent: Sunday, November 15, 2009 2:51 PM >> To: AstLinux Users Mailing List >> Subject: Re: [Astlinux-users] Astlinux-0.7 Upgrade? >> >> Tom, >> >> DAHDI files should be located as /mnt/kd/dahdi/*.conf >> >> A reboot is required for DAHDI to see them. Also, after such >>files are created, they may be edited via the Edit tab. >> >> While this is painful, clearly DAHDI is the future, and the >>transition from ZAPTEL needs to occur. >> >> Lonnie > > >-- >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. Michael http://www.mksolutions.info -- 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.
Re: [Astlinux-users] Astlinux-0.7 Upgrade?
This would imply that the define "CONFIG_PRODUCT_WANPIPE_TDM_VOICE" is not set when wanpipe is build. This is definitely a Philip question... Lonnie On Nov 15, 2009, at 3:35 PM, Tom Mazzotta wrote: > Lonnie, > > These tips helped me make a lot of progress. On the remote system with the > TDM card, "dahdi show status" is recognizing the card. However, my local > system with the Sangoma board is still a problem. My concern is the message > "wanpipe1: Error: TDM VOICE prot not compiled" reported by dmesg (see below). > Is it possible that there is some required component of wanpipe that was left > out of the 0.7 build I am testing? > > pbx ~ # dmesg | grep wanpipe > wanpipe1: Running post initialization... > wanpipe1: Remora config done! > wanpipe1: AFT Data Mux Bit Map: 0x01234567 > wanpipe1: Front End Interface Ready 0x > wanpipe1: Register EC interface wanec1 (usage 1, max ec chans 32)! > wanpipe1: Configuring Device :wanpipe1 FrmVr=11 > wanpipe1:Global MTU = 1500 > wanpipe1:Global MRU = 1500 > wanpipe1:Data Mux Map = 0x01234567 > wanpipe1:Rx CRC Bytes = 0 > wanpipe1:Global TDM Int = Disabled > wanpipe1:Global TDM Ring = Disabled > wanpipe1:TDMV HW DTMF/FAX = Enabled/Disabled(0) > wanpipe1:TDMV Span= 1 : Enabled > wanpipe1:RTP TAP = Disabled > wanpipe1: Error: TDM VOICE prot not compiled > wanpipe1:during installation process! > wanpipe1: Shutting Down! > wanpipe1: TASKQ Not Running > wanpipe1: Unconfiguring FXS/FXO Front End... > wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Device Down) > wanpipe1: Unregister interface from wanec1 (usage 1)! > wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Device Down) > wanpipe1: Global Chip Shutdown Usage=1 > wanpipe1: Unconfiguring FXS/FXO Front End... > wanpipe1: Master shutting down > af_wanpipe: Unregistering Wanpipe API Socket Module > wanpipe: WANPIPE Modules Unloaded. > pbx ~ # > > -Original Message- > From: Lonnie Abelbeck [mailto:li...@lonnie.abelbeck.com] > Sent: Sunday, November 15, 2009 2:51 PM > To: AstLinux Users Mailing List > Subject: Re: [Astlinux-users] Astlinux-0.7 Upgrade? > > Tom, > > DAHDI files should be located as /mnt/kd/dahdi/*.conf > > A reboot is required for DAHDI to see them. Also, after such files are > created, they may be edited via the Edit tab. > > While this is painful, clearly DAHDI is the future, and the transition from > ZAPTEL needs to occur. > > Lonnie -- 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.
Re: [Astlinux-users] Astlinux-0.7 Upgrade?
Lonnie, These tips helped me make a lot of progress. On the remote system with the TDM card, "dahdi show status" is recognizing the card. However, my local system with the Sangoma board is still a problem. My concern is the message "wanpipe1: Error: TDM VOICE prot not compiled" reported by dmesg (see below). Is it possible that there is some required component of wanpipe that was left out of the 0.7 build I am testing? pbx ~ # dmesg | grep wanpipe wanpipe1: Running post initialization... wanpipe1: Remora config done! wanpipe1: AFT Data Mux Bit Map: 0x01234567 wanpipe1: Front End Interface Ready 0x wanpipe1: Register EC interface wanec1 (usage 1, max ec chans 32)! wanpipe1: Configuring Device :wanpipe1 FrmVr=11 wanpipe1:Global MTU = 1500 wanpipe1:Global MRU = 1500 wanpipe1:Data Mux Map = 0x01234567 wanpipe1:Rx CRC Bytes = 0 wanpipe1:Global TDM Int = Disabled wanpipe1:Global TDM Ring = Disabled wanpipe1:TDMV HW DTMF/FAX = Enabled/Disabled(0) wanpipe1:TDMV Span= 1 : Enabled wanpipe1:RTP TAP = Disabled wanpipe1: Error: TDM VOICE prot not compiled wanpipe1:during installation process! wanpipe1: Shutting Down! wanpipe1: TASKQ Not Running wanpipe1: Unconfiguring FXS/FXO Front End... wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Device Down) wanpipe1: Unregister interface from wanec1 (usage 1)! wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Device Down) wanpipe1: Global Chip Shutdown Usage=1 wanpipe1: Unconfiguring FXS/FXO Front End... wanpipe1: Master shutting down af_wanpipe: Unregistering Wanpipe API Socket Module wanpipe: WANPIPE Modules Unloaded. pbx ~ # -Original Message- From: Lonnie Abelbeck [mailto:li...@lonnie.abelbeck.com] Sent: Sunday, November 15, 2009 2:51 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] Astlinux-0.7 Upgrade? Tom, DAHDI files should be located as /mnt/kd/dahdi/*.conf A reboot is required for DAHDI to see them. Also, after such files are created, they may be edited via the Edit tab. While this is painful, clearly DAHDI is the future, and the transition from ZAPTEL needs to occur. Lonnie On Nov 15, 2009, at 1:28 PM, Tom Mazzotta wrote: > Correction to my last post, I copied zapata.conf to chan_dahdi.conf. > > I also tested my remote system which contains a TDM400P and it logs the same > dahdi warnings/errors, which leads me to believe that my problem has more to > do with the dahdi configuration. In doing more Google searching, it seems > like I need a system.conf under a dahdi directory. Apparently the recommended > technique to create this file is via dahdi_genconf, which I believe will not > run because it requires a full Perl implementation. I did find a sample > online which I should be able to mod for my config, however, on my box this > file is located under /stat/etc/dahdi. Now I typically have only edited files > under /mnt/kd, so I hesitate to modify this file. Should I configure the > system.conf in /stat/etc/dahdi or should it be put in another place? Or am I > on the wrong track here?? > > And since this is the first time that I am configuring dahdi, what are the > files (and their locations) that need to be configured? > > Lastly, my sincere apologies for rambling on with this post. And I very much > appreciate everyone's support with this issue. > > -Original Message- > From: Tom Mazzotta [mailto:tmazzo...@titanmicro.com] > Sent: Sunday, November 15, 2009 1:03 PM > To: AstLinux Users Mailing List > Subject: Re: [Astlinux-users] Astlinux-0.7 Upgrade? > > 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
Re: [Astlinux-users] Astlinux-0.7 Upgrade?
Tom, DAHDI files should be located as /mnt/kd/dahdi/*.conf A reboot is required for DAHDI to see them. Also, after such files are created, they may be edited via the Edit tab. While this is painful, clearly DAHDI is the future, and the transition from ZAPTEL needs to occur. Lonnie On Nov 15, 2009, at 1:28 PM, Tom Mazzotta wrote: > Correction to my last post, I copied zapata.conf to chan_dahdi.conf. > > I also tested my remote system which contains a TDM400P and it logs the same > dahdi warnings/errors, which leads me to believe that my problem has more to > do with the dahdi configuration. In doing more Google searching, it seems > like I need a system.conf under a dahdi directory. Apparently the recommended > technique to create this file is via dahdi_genconf, which I believe will not > run because it requires a full Perl implementation. I did find a sample > online which I should be able to mod for my config, however, on my box this > file is located under /stat/etc/dahdi. Now I typically have only edited files > under /mnt/kd, so I hesitate to modify this file. Should I configure the > system.conf in /stat/etc/dahdi or should it be put in another place? Or am I > on the wrong track here?? > > And since this is the first time that I am configuring dahdi, what are the > files (and their locations) that need to be configured? > > Lastly, my sincere apologies for rambling on with this post. And I very much > appreciate everyone's support with this issue. > > -Original Message- > From: Tom Mazzotta [mailto:tmazzo...@titanmicro.com] > Sent: Sunday, November 15, 2009 1:03 PM > To: AstLinux Users Mailing List > Subject: Re: [Astlinux-users] Astlinux-0.7 Upgrade? > > 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 al
Re: [Astlinux-users] Astlinux-0.7 Upgrade?
I should have also added... Define "DAHDIMODS=" for any modules that need to be modprob'ed, as ZAPMODS of the past. Use /stat/etc/dahdi/system.conf as a template to create your /mnt/kd/dahdi/system.conf file. Configure chan_dahdi.conf in asterisk as needed. Lonnie On Nov 15, 2009, at 1:51 PM, Lonnie Abelbeck wrote: > Tom, > > DAHDI files should be located as /mnt/kd/dahdi/*.conf > > A reboot is required for DAHDI to see them. Also, after such files are > created, they may be edited via the Edit tab. > > While this is painful, clearly DAHDI is the future, and the transition from > ZAPTEL needs to occur. > > Lonnie > > > On Nov 15, 2009, at 1:28 PM, Tom Mazzotta wrote: > >> Correction to my last post, I copied zapata.conf to chan_dahdi.conf. >> >> I also tested my remote system which contains a TDM400P and it logs the same >> dahdi warnings/errors, which leads me to believe that my problem has more to >> do with the dahdi configuration. In doing more Google searching, it seems >> like I need a system.conf under a dahdi directory. Apparently the >> recommended technique to create this file is via dahdi_genconf, which I >> believe will not run because it requires a full Perl implementation. I did >> find a sample online which I should be able to mod for my config, however, >> on my box this file is located under /stat/etc/dahdi. Now I typically have >> only edited files under /mnt/kd, so I hesitate to modify this file. Should I >> configure the system.conf in /stat/etc/dahdi or should it be put in another >> place? Or am I on the wrong track here?? >> >> And since this is the first time that I am configuring dahdi, what are the >> files (and their locations) that need to be configured? >> >> Lastly, my sincere apologies for rambling on with this post. And I very much >> appreciate everyone's support with this issue. >> >> -Original Message- >> From: Tom Mazzotta [mailto:tmazzo...@titanmicro.com] >> Sent: Sunday, November 15, 2009 1:03 PM >> To: AstLinux Users Mailing List >> Subject: Re: [Astlinux-users] Astlinux-0.7 Upgrade? >> >> 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 mig
Re: [Astlinux-users] Astlinux-0.7 Upgrade?
Correction to my last post, I copied zapata.conf to chan_dahdi.conf. I also tested my remote system which contains a TDM400P and it logs the same dahdi warnings/errors, which leads me to believe that my problem has more to do with the dahdi configuration. In doing more Google searching, it seems like I need a system.conf under a dahdi directory. Apparently the recommended technique to create this file is via dahdi_genconf, which I believe will not run because it requires a full Perl implementation. I did find a sample online which I should be able to mod for my config, however, on my box this file is located under /stat/etc/dahdi. Now I typically have only edited files under /mnt/kd, so I hesitate to modify this file. Should I configure the system.conf in /stat/etc/dahdi or should it be put in another place? Or am I on the wrong track here?? And since this is the first time that I am configuring dahdi, what are the files (and their locations) that need to be configured? Lastly, my sincere apologies for rambling on with this post. And I very much appreciate everyone's support with this issue. -Original Message- From: Tom Mazzotta [mailto:tmazzo...@titanmicro.com] Sent: Sunday, November 15, 2009 1:03 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] Astlinux-0.7 Upgrade? 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
Re: [Astlinux-users] Astlinux-0.7 Upgrade?
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 __
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.
Re: [Astlinux-users] Astlinux-0.7 Upgrade?
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
>> -Original Message-
>> From: Lonnie Abelbeck [mailto:li...@lonnie.abelbeck.com]
>> Sent: Saturday, November 14, 2009 6:01 PM
>> To: Tom Mazzotta
>> Subject: Re: [Astlinux-users] Astlinux-0.7 Upgrade?
>>
>> Tom,
>>
>> For your NAT -> DMZ, the Destination must be a single IP address not network
>> notation, so use 192.168.169.101 and not 192.168.169.101/32.
>>
>> So, click on the " + " by the NAT -> DMZ entries, delete the /32 for the
>> destination, save settings, and then delete the previous entry... all for
>> each NAT entry.
>>
>> Then restart the firewall...
>>
>> Let me know if that fixes your firewall errors.
>>
>> Now for the Sangoma, was you 0.7-beta built with wanpipe support? I know
>> basically nothing about Sangoma hardware, Darrick knows much more than I on
>> that. But we need to get this working. Could this be related to your
>> firewall problems?
>>
>> If you need to revert back, you should be able to use the System tab and
>> "Revert to Previous" {Firmware}, after the reboot, then follow the same
>> firewall 'upgrade' procedure for 0.7 to 0.6 as you did form 0.6 to 0.7.
>>
>>
>> Lonnie
>>
>>
>>
>> On Nov 14, 2009, at 4:31 PM, Tom Mazzotta wrote:
>>
>>> Lonnie,
>>>
>>> I believe the problem is due to NAT -> DMZ port forwarding rules. Below you
>>> will find the errors. If I disable the rules and restart the f/w, I do not
>>> get the "Action Failed" warning. I don't understand why I have the problem;
>>> my DMZ i/f (eth3) is 192.168.169.1 and I am forwarding ports to an Xbox360
>>> on the DMZ at 192.168.169.101. The Xbox is mapped to that IP via its MAC
>>> using t
Re: [Astlinux-users] Astlinux-0.7 Upgrade?
Darrick,
I have reverted back to 0.6.8 for the moment, so there is no sense of urgency
at this point. While I don't have a spare Sangoma system available for testing
I'm comfortable allowing one of the core developers ssh access when convenient.
-tm
-Original Message-
From: Darrick Hartman [mailto:dhart...@djhsolutions.com]
Sent: Sunday, November 15, 2009 12:27 AM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] Astlinux-0.7 Upgrade?
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
> -Original Message-
> From: Lonnie Abelbeck [mailto:li...@lonnie.abelbeck.com]
> Sent: Saturday, November 14, 2009 6:01 PM
> To: Tom Mazzotta
> Subject: Re: [Astlinux-users] Astlinux-0.7 Upgrade?
>
> Tom,
>
> For your NAT -> DMZ, the Destination must be a single IP address not network
> notation, so use 192.168.169.101 and not 192.168.169.101/32.
>
> So, click on the " + " by the NAT -> DMZ entries, delete the /32 for the
> destination, save settings, and then delete the previous entry... all for
> each NAT entry.
>
> Then restart the firewall...
>
> Let me know if that fixes your firewall errors.
>
> Now for the Sangoma, was you 0.7-beta built with wanpipe support? I know
> basically nothing about Sangoma hardware, Darrick knows much more than I on
> that. But we need to get this working. Could this be related to your
> firewall problems?
>
> If you need to revert back, you should be able to use the System tab and
> "Revert to Previous" {Firmware}, after the reboot, then follow the same
> firewall 'upgrade' procedure for 0.7 to 0.6 as you did form 0.6 to 0.7.
>
>
> Lonnie
>
>
>
> On Nov 14, 2009, at 4:31 PM, Tom Mazzotta wrote:
>
>> Lonnie,
>>
>> I believe the problem is due to NAT -> DMZ port forwarding rules. Below you
>> will find the errors. If I disable the rules and restart the f/w, I do not
>> get the "Action Failed" warning. I don't understand why I have the problem;
>> my DMZ i/f (eth3) is 192.168.169.1 and I am forwarding ports to an Xbox360
>> on the DMZ at 192.168.169.101. The Xbox is mapped to that IP via its MAC
>> using the "DNS Forwarder Hosts" form.
>>
>> Now the BIG problem is that my Sangoma board no longer functions following
>> the upgrade. I have 2x FXO's connected to POTS lines from my cable modem
>> service and 2x FXS ports connected to outside doorbell boxes. I can make
>> extension calls via SIP without any problem in the house, however, I can't
>> make/receive an outside call OR use the intercom on the doorbell boxes. FYI,
>> the wanpipe1.conf file that I originally prepared using a FreeBSD system is
>> still in the wanpipe directory following the upgrade. Unless I can get this
>> fixed pretty quickly, I will need to rollback to 0.6.8. I can only endure
>> the screaming from my wife for so long.
>>
>>
>> -Original Message-
>> From: Lonnie Abelbeck
Re: [Astlinux-users] Astlinux-0.7 Upgrade
All, Oops. Never mind. I found the solution [http://lonnie.abelbeck.com/astlinux/info/webgui.php] here. RTF! Once changing the password, all is well. Sorry for the noise and wasted bandwidth. Dan -Original Message- From: d...@ryson.org Sent: Sunday, November 15, 2009 8:18am To: "AstLinux Users Mailing List" Subject: [Astlinux-users] Astlinux-0.7 Upgrade All, This is the first time I've upgraded AstLinux from the GUI. Wow! That's really slick. I'm noticing only one little problem, the following error is reported under Active Channels: The "manager.conf" file does not have the [webinterface] user defined properly. The webinterface section of manager.conf looks like this: ; Web interface localhost user for AstLinux ; [webinterface] secret = [same password as for gui admin logon] deny = 0.0.0.0/0.0.0.0 permit=127.0.0.1/255.255.255.255 read = command write = command As always, your assistance would be greatly appreciated. Dan -- 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.
[Astlinux-users] Astlinux-0.7 Upgrade
All, This is the first time I've upgraded AstLinux from the GUI. Wow! That's really slick. I'm noticing only one little problem, the following error is reported under Active Channels: The "manager.conf" file does not have the [webinterface] user defined properly. The webinterface section of manager.conf looks like this: ; Web interface localhost user for AstLinux ; [webinterface] secret = [same password as for gui admin logon] deny = 0.0.0.0/0.0.0.0 permit=127.0.0.1/255.255.255.255 read = command write = command As always, your assistance would be greatly appreciated. Dan -- 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.
[Astlinux-users] Update Website for 0.6.8
Hi devs, can someone please update the www.astlinux.org website, mentioning that 0.6.8 is released, but only available via "System Firmware Upgrade". This could be also noted as news at Sourceforge project site. What about making more promotion for Astlinux in general: E.g. links at the Soekris and PC Engines http://soekris.com/support.htm http://pcengines.ch/alix.htm http://pcengines.ch/wrap.htm Or an entry on the english Wikipedia (it is mentioned at the German WP) or maybe a subpage like Elastix. Michael http://www.mksolutions.info -- 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.
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
>> -Original Message-
>> From: Lonnie Abelbeck [mailto:li...@lonnie.abelbeck.com]
>> Sent: Saturday, November 14, 2009 6:01 PM
>> To: Tom Mazzotta
>> Subject: Re: [Astlinux-users] Astlinux-0.7 Upgrade?
>>
>> Tom,
>>
>> For your NAT -> DMZ, the Destination must be a single IP address not network
>> notation, so use 192.168.169.101 and not 192.168.169.101/32.
>>
>> So, click on the " + " by the NAT -> DMZ entries, delete the /32 for the
>> destination, save settings, and then delete the previous entry... all for
>> each NAT entry.
>>
>> Then restart the firewall...
>>
>> Let me know if that fixes your firewall errors.
>>
>> Now for the Sangoma, was you 0.7-beta built with wanpipe support? I know
>> basically nothing about Sangoma hardware, Darrick knows much more than I on
>> that. But we need to get this working. Could this be related to your
>> firewall problems?
>>
>> If you need to revert back, you should be able to use the System tab and
>> "Revert to Previous" {Firmware}, after the reboot, then follow the same
>> firewall 'upgrade' procedure for 0.7 to 0.6 as you did form 0.6 to 0.7.
>>
>>
>> Lonnie
>>
>>
>>
>> On Nov 14, 2009, at 4:31 PM, Tom Mazzotta wrote:
>>
>>> Lonnie,
>>>
>>> I believe the problem is due to NAT -> DMZ port forwarding rules. Below you
>>> will find the errors. If I disable the rules and restart the f/w, I do not
>>> get the "Action Failed" warning. I don't understand why I have the problem;
>>> my DMZ i/f (eth3) is 192.168.169.1 and I am forwarding ports to an Xbox360
>>> on the DMZ at 192.168.169.101. The Xbox is mapped to that IP via its MAC
>>> using the "DNS Forwarder Hosts" form.
>>>
>>> Now the BIG problem is that my Sangoma board no longer functions following
>>> the upgrade. I have 2x FXO's connected to POTS lines from my cable modem
>>> service and 2x FXS ports connected to outside doorbell boxes. I can make
>>> extension calls via SIP without any problem in the house, however, I can't
>>> make/receive an outside call OR use the intercom on the doorbell boxes.
>>> FYI, the wanpipe1.conf file that I originally prepared using a FreeBSD
>>> system is still in the wanpipe directory following the upgrade. Unless I
>>> can get this fixed pretty quickly, I will need to rollback to 0.6.8. I can
>>> only endure the screaming from my wife for so long.
>>>
>>>
>>> -Original Message-
>>> From: Lonnie Abelbeck [mailto:li...@lonnie.abelbeck.com]
>>> Sent: Saturday,
