Re: [Astlinux-users] How many Ethernets do you really need?
Unless you are going to use the full functionality of ASTLinux one port should suffice. I only use AST for VoIP and out of 3 ports I have only use one.. Though if you need to segregate your phone in different subnets, etc... Having several ports could be handy. Thank You, Fernando Fuentes DIGITALVOIPNET.COM On Fri, Aug 17, 2012 at 9:53 PM, Michael Knill < michael.kn...@ipcsolutions.com.au> wrote: > Just wanting to put a quick question to the group on how often the 3rd or > more Ethernet interface is used. > I am looking at standardising on the Jetway NF96 and want to know whether > I purchase the single port or 3 port Ethernet daughter card. > Yes I do realise that the NF99 has dual port Ethernet but I like the fact > that the NF96 has onboard PSU and I can use IDE DOM which is a little > cheaper than the SATA as well. > > PS. I also really don't like the Mini-Box cases. The M200/300 LCD has a > power button that sticks out and if you just touch it, the system is turned > off. Not too sure if this is the case with the non LCD variants. I also > don't like the M350 as its too open. Wouldn't want to spill anything on the > top of that and I am sure it must get really dusty inside. > > Thanks > Mike > > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ___ > 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. > -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ 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] How many Ethernets do you really need?
Just wanting to put a quick question to the group on how often the 3rd or more Ethernet interface is used. I am looking at standardising on the Jetway NF96 and want to know whether I purchase the single port or 3 port Ethernet daughter card. Yes I do realise that the NF99 has dual port Ethernet but I like the fact that the NF96 has onboard PSU and I can use IDE DOM which is a little cheaper than the SATA as well. PS. I also really don't like the Mini-Box cases. The M200/300 LCD has a power button that sticks out and if you just touch it, the system is turned off. Not too sure if this is the case with the non LCD variants. I also don't like the M350 as its too open. Wouldn't want to spill anything on the top of that and I am sure it must get really dusty inside. Thanks Mike -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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-devel] AstLinux 1.0.4 Released
Should anyone question the usefulness of AstLinux's "Revert to Previous" Firmware feature, Tom's adventures here is a prime example where a production system can be maintained while easily testing and sorting out an issue with a newer firmware release. BTW, the Curiosity Mars Rover has the same firmware management feature. :-) Lonnie On Aug 17, 2012, at 1:16 PM, Darrick Hartman wrote: > Tom, > > Glad I could help. I couldn't remember the other day what the exact change > was in the 2.5 to 2.6 transition. > > Darrick > > -Original Message- > From: Tom Chadwin [mailto:nnpait.servi...@googlemail.com] > Sent: Friday, August 17, 2012 8:18 AM > To: 'AstLinux Users Mailing List' > Subject: Re: [Astlinux-users] [Astlinux-devel] AstLinux 1.0.4 Released > > Solved. > > Darrick, 100% correct. Added the following to dahdi/system.conf: > > echocanceller=hwec,1-2 > > Audio now working. Many apologies for the non-Astlinux issue, and many, many > thanks for the help fixing it anyway. > > Thanks > > Tom > > > -Original Message- > From: Darrick Hartman [mailto:dhart...@djhsolutions.com] > Sent: 17 August 2012 12:52 > To: 'AstLinux Users Mailing List' > Subject: Re: [Astlinux-users] [Astlinux-devel] AstLinux 1.0.4 Released > > Tom, > > I believe with 2.6 you need to specify the echo canceler used. In the past, > if none was specified a default was used. That behavior changed and you must > now specify one in the DAHDI system.conf > > Examples: echocanceller=hwec, (if you have hardware ec) . Other > options include mg2, kb1 > > Hope that gets you in the right direction. > > Darrick > > -Original Message- > From: Tom Chadwin [mailto:nnpait.servi...@googlemail.com] > Sent: Friday, August 17, 2012 3:23 AM > To: 'AstLinux Users Mailing List' > Subject: Re: [Astlinux-users] [Astlinux-devel] AstLinux 1.0.4 Released > >> Any DAHDI syslog errors with AstLinux 1.0.4 ? > > Looks like it might be the echo canceller: > > wctdm24xxp :00:0e.0: Error pinging DSP (2) > > This error is not present in 1.0.2. > >> From the asterisk prompt "dahdi restart" any errors with AstLinux 1.0.4 ? > > ingrampbx*CLI> dahdi restart > Destroying channels and reloading DAHDI configuration. > Initial softhangup of all DAHDI channels complete. > Final softhangup of all DAHDI channels complete. > == Unregistered channel -2 > == Unregistered channel 1 > == Unregistered channel 2 > == Parsing '/etc/asterisk/chan_dahdi.conf': Found [Aug 17 09:04:55] > WARNING[2919]: chan_dahdi.c:1313 dahdi_open: Unable to specify channel 1: > Device or resource busy >-- Reconfigured channel 1, FXS Kewlstart signalling >-- Reconfigured channel 2, FXS Kewlstart signalling >-- Automatically generated pseudo channel > == Parsing '/etc/asterisk/users.conf': Found > > Not sure if that WARNING is a concern. I have no other DAHDI boxes with which > to compare. > >> From the CLI prompt "show-union", any dahdi files/modules shown ? > > Not exactly DAHDI, but the echo canceller again: > > /oldroot/mnt/asturw/lib > /oldroot/mnt/asturw/lib/firmware > /oldroot/mnt/asturw/lib/firmware/zaptel-fw-vpmadt032.bin > >> Possibly "dahdi_tool" from the CLI might shed some light. Compare >> results > 1.0.2 vs. 1.0.4 > > 1.0.2 and 1.0.4 both give: > > Current Alarms: No alarms. > Sync Source:Internally clocked > IRQ Misses: 3 > Bipolar Viol: 0 > Tx/Rx Levels: 0/ 0 > Total/Conf/Act: 4/ 2/ 2 > >> Possibly a DAHDI config error effects you with DAHDI 2.6 and not with > DAHDI 2.5. Maybe a UK thing. > > Possibly. No idea what, though. I'll check my DAHDI config. > > Thanks for the help. Any other ideas? Do you think the "Error pinging DSP" > could point towards something? Could the VPMADT032 have failed? I had major > problems with that module back at Astlinux 0.7.2, and it related to the > driver for that module. > > Thanks > > Tom > > > > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ___ > 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. > > > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest in malw
Re: [Astlinux-users] [Astlinux-devel] AstLinux 1.0.4 Released
Tom, Glad I could help. I couldn't remember the other day what the exact change was in the 2.5 to 2.6 transition. Darrick -Original Message- From: Tom Chadwin [mailto:nnpait.servi...@googlemail.com] Sent: Friday, August 17, 2012 8:18 AM To: 'AstLinux Users Mailing List' Subject: Re: [Astlinux-users] [Astlinux-devel] AstLinux 1.0.4 Released Solved. Darrick, 100% correct. Added the following to dahdi/system.conf: echocanceller=hwec,1-2 Audio now working. Many apologies for the non-Astlinux issue, and many, many thanks for the help fixing it anyway. Thanks Tom -Original Message- From: Darrick Hartman [mailto:dhart...@djhsolutions.com] Sent: 17 August 2012 12:52 To: 'AstLinux Users Mailing List' Subject: Re: [Astlinux-users] [Astlinux-devel] AstLinux 1.0.4 Released Tom, I believe with 2.6 you need to specify the echo canceler used. In the past, if none was specified a default was used. That behavior changed and you must now specify one in the DAHDI system.conf Examples: echocanceller=hwec, (if you have hardware ec) . Other options include mg2, kb1 Hope that gets you in the right direction. Darrick -Original Message- From: Tom Chadwin [mailto:nnpait.servi...@googlemail.com] Sent: Friday, August 17, 2012 3:23 AM To: 'AstLinux Users Mailing List' Subject: Re: [Astlinux-users] [Astlinux-devel] AstLinux 1.0.4 Released > Any DAHDI syslog errors with AstLinux 1.0.4 ? Looks like it might be the echo canceller: wctdm24xxp :00:0e.0: Error pinging DSP (2) This error is not present in 1.0.2. > From the asterisk prompt "dahdi restart" any errors with AstLinux 1.0.4 ? ingrampbx*CLI> dahdi restart Destroying channels and reloading DAHDI configuration. Initial softhangup of all DAHDI channels complete. Final softhangup of all DAHDI channels complete. == Unregistered channel -2 == Unregistered channel 1 == Unregistered channel 2 == Parsing '/etc/asterisk/chan_dahdi.conf': Found [Aug 17 09:04:55] WARNING[2919]: chan_dahdi.c:1313 dahdi_open: Unable to specify channel 1: Device or resource busy -- Reconfigured channel 1, FXS Kewlstart signalling -- Reconfigured channel 2, FXS Kewlstart signalling -- Automatically generated pseudo channel == Parsing '/etc/asterisk/users.conf': Found Not sure if that WARNING is a concern. I have no other DAHDI boxes with which to compare. > From the CLI prompt "show-union", any dahdi files/modules shown ? Not exactly DAHDI, but the echo canceller again: /oldroot/mnt/asturw/lib /oldroot/mnt/asturw/lib/firmware /oldroot/mnt/asturw/lib/firmware/zaptel-fw-vpmadt032.bin > Possibly "dahdi_tool" from the CLI might shed some light. Compare > results 1.0.2 vs. 1.0.4 1.0.2 and 1.0.4 both give: Current Alarms: No alarms. Sync Source:Internally clocked IRQ Misses: 3 Bipolar Viol: 0 Tx/Rx Levels: 0/ 0 Total/Conf/Act: 4/ 2/ 2 > Possibly a DAHDI config error effects you with DAHDI 2.6 and not with DAHDI 2.5. Maybe a UK thing. Possibly. No idea what, though. I'll check my DAHDI config. Thanks for the help. Any other ideas? Do you think the "Error pinging DSP" could point towards something? Could the VPMADT032 have failed? I had major problems with that module back at Astlinux 0.7.2, and it related to the driver for that module. Thanks Tom -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest
Re: [Astlinux-users] [Astlinux-devel] AstLinux 1.0.4 Released
Solved. Darrick, 100% correct. Added the following to dahdi/system.conf: echocanceller=hwec,1-2 Audio now working. Many apologies for the non-Astlinux issue, and many, many thanks for the help fixing it anyway. Thanks Tom -Original Message- From: Darrick Hartman [mailto:dhart...@djhsolutions.com] Sent: 17 August 2012 12:52 To: 'AstLinux Users Mailing List' Subject: Re: [Astlinux-users] [Astlinux-devel] AstLinux 1.0.4 Released Tom, I believe with 2.6 you need to specify the echo canceler used. In the past, if none was specified a default was used. That behavior changed and you must now specify one in the DAHDI system.conf Examples: echocanceller=hwec, (if you have hardware ec) . Other options include mg2, kb1 Hope that gets you in the right direction. Darrick -Original Message- From: Tom Chadwin [mailto:nnpait.servi...@googlemail.com] Sent: Friday, August 17, 2012 3:23 AM To: 'AstLinux Users Mailing List' Subject: Re: [Astlinux-users] [Astlinux-devel] AstLinux 1.0.4 Released > Any DAHDI syslog errors with AstLinux 1.0.4 ? Looks like it might be the echo canceller: wctdm24xxp :00:0e.0: Error pinging DSP (2) This error is not present in 1.0.2. > From the asterisk prompt "dahdi restart" any errors with AstLinux 1.0.4 ? ingrampbx*CLI> dahdi restart Destroying channels and reloading DAHDI configuration. Initial softhangup of all DAHDI channels complete. Final softhangup of all DAHDI channels complete. == Unregistered channel -2 == Unregistered channel 1 == Unregistered channel 2 == Parsing '/etc/asterisk/chan_dahdi.conf': Found [Aug 17 09:04:55] WARNING[2919]: chan_dahdi.c:1313 dahdi_open: Unable to specify channel 1: Device or resource busy -- Reconfigured channel 1, FXS Kewlstart signalling -- Reconfigured channel 2, FXS Kewlstart signalling -- Automatically generated pseudo channel == Parsing '/etc/asterisk/users.conf': Found Not sure if that WARNING is a concern. I have no other DAHDI boxes with which to compare. > From the CLI prompt "show-union", any dahdi files/modules shown ? Not exactly DAHDI, but the echo canceller again: /oldroot/mnt/asturw/lib /oldroot/mnt/asturw/lib/firmware /oldroot/mnt/asturw/lib/firmware/zaptel-fw-vpmadt032.bin > Possibly "dahdi_tool" from the CLI might shed some light. Compare > results 1.0.2 vs. 1.0.4 1.0.2 and 1.0.4 both give: Current Alarms: No alarms. Sync Source:Internally clocked IRQ Misses: 3 Bipolar Viol: 0 Tx/Rx Levels: 0/ 0 Total/Conf/Act: 4/ 2/ 2 > Possibly a DAHDI config error effects you with DAHDI 2.6 and not with DAHDI 2.5. Maybe a UK thing. Possibly. No idea what, though. I'll check my DAHDI config. Thanks for the help. Any other ideas? Do you think the "Error pinging DSP" could point towards something? Could the VPMADT032 have failed? I had major problems with that module back at Astlinux 0.7.2, and it related to the driver for that module. Thanks Tom -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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-devel] AstLinux 1.0.4 Released
Hi Darrick >From upgrade.txt in dahdilinux 2.6.1: " Note: It is *mandatory* to configure an echo canceler for the system's channels using dahdi_cfg unless the interface cards in use have echo canceler modules available and enabled. There is *no* default software echo canceler with DAHDI." The "unless" means I'm not clear whether I need to specify ec explicitly given that I have the hardware module. I can't believe how difficult I am finding it to get config instructions for dahdi 2.6.1. I can confirm that the existing 2.5.0.2 box has no echocanceller entry in dahdi/system.conf. So if you are right, that could easily be the explanation. Damned if I can find primary documentation to confirm, though. Thanks - I'll keep looking Tom -Original Message- From: Darrick Hartman [mailto:dhart...@djhsolutions.com] Sent: 17 August 2012 12:52 To: 'AstLinux Users Mailing List' Subject: Re: [Astlinux-users] [Astlinux-devel] AstLinux 1.0.4 Released Tom, I believe with 2.6 you need to specify the echo canceler used. In the past, if none was specified a default was used. That behavior changed and you must now specify one in the DAHDI system.conf Examples: echocanceller=hwec, (if you have hardware ec) . Other options include mg2, kb1 Hope that gets you in the right direction. Darrick -Original Message- From: Tom Chadwin [mailto:nnpait.servi...@googlemail.com] Sent: Friday, August 17, 2012 3:23 AM To: 'AstLinux Users Mailing List' Subject: Re: [Astlinux-users] [Astlinux-devel] AstLinux 1.0.4 Released > Any DAHDI syslog errors with AstLinux 1.0.4 ? Looks like it might be the echo canceller: wctdm24xxp :00:0e.0: Error pinging DSP (2) This error is not present in 1.0.2. > From the asterisk prompt "dahdi restart" any errors with AstLinux 1.0.4 ? ingrampbx*CLI> dahdi restart Destroying channels and reloading DAHDI configuration. Initial softhangup of all DAHDI channels complete. Final softhangup of all DAHDI channels complete. == Unregistered channel -2 == Unregistered channel 1 == Unregistered channel 2 == Parsing '/etc/asterisk/chan_dahdi.conf': Found [Aug 17 09:04:55] WARNING[2919]: chan_dahdi.c:1313 dahdi_open: Unable to specify channel 1: Device or resource busy -- Reconfigured channel 1, FXS Kewlstart signalling -- Reconfigured channel 2, FXS Kewlstart signalling -- Automatically generated pseudo channel == Parsing '/etc/asterisk/users.conf': Found Not sure if that WARNING is a concern. I have no other DAHDI boxes with which to compare. > From the CLI prompt "show-union", any dahdi files/modules shown ? Not exactly DAHDI, but the echo canceller again: /oldroot/mnt/asturw/lib /oldroot/mnt/asturw/lib/firmware /oldroot/mnt/asturw/lib/firmware/zaptel-fw-vpmadt032.bin > Possibly "dahdi_tool" from the CLI might shed some light. Compare > results 1.0.2 vs. 1.0.4 1.0.2 and 1.0.4 both give: Current Alarms: No alarms. Sync Source:Internally clocked IRQ Misses: 3 Bipolar Viol: 0 Tx/Rx Levels: 0/ 0 Total/Conf/Act: 4/ 2/ 2 > Possibly a DAHDI config error effects you with DAHDI 2.6 and not with DAHDI 2.5. Maybe a UK thing. Possibly. No idea what, though. I'll check my DAHDI config. Thanks for the help. Any other ideas? Do you think the "Error pinging DSP" could point towards something? Could the VPMADT032 have failed? I had major problems with that module back at Astlinux 0.7.2, and it related to the driver for that module. Thanks Tom -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security
Re: [Astlinux-users] [Astlinux-devel] AstLinux 1.0.4 Released
Tom, I believe with 2.6 you need to specify the echo canceler used. In the past, if none was specified a default was used. That behavior changed and you must now specify one in the DAHDI system.conf Examples: echocanceller=hwec, (if you have hardware ec) . Other options include mg2, kb1 Hope that gets you in the right direction. Darrick -Original Message- From: Tom Chadwin [mailto:nnpait.servi...@googlemail.com] Sent: Friday, August 17, 2012 3:23 AM To: 'AstLinux Users Mailing List' Subject: Re: [Astlinux-users] [Astlinux-devel] AstLinux 1.0.4 Released > Any DAHDI syslog errors with AstLinux 1.0.4 ? Looks like it might be the echo canceller: wctdm24xxp :00:0e.0: Error pinging DSP (2) This error is not present in 1.0.2. > From the asterisk prompt "dahdi restart" any errors with AstLinux 1.0.4 ? ingrampbx*CLI> dahdi restart Destroying channels and reloading DAHDI configuration. Initial softhangup of all DAHDI channels complete. Final softhangup of all DAHDI channels complete. == Unregistered channel -2 == Unregistered channel 1 == Unregistered channel 2 == Parsing '/etc/asterisk/chan_dahdi.conf': Found [Aug 17 09:04:55] WARNING[2919]: chan_dahdi.c:1313 dahdi_open: Unable to specify channel 1: Device or resource busy -- Reconfigured channel 1, FXS Kewlstart signalling -- Reconfigured channel 2, FXS Kewlstart signalling -- Automatically generated pseudo channel == Parsing '/etc/asterisk/users.conf': Found Not sure if that WARNING is a concern. I have no other DAHDI boxes with which to compare. > From the CLI prompt "show-union", any dahdi files/modules shown ? Not exactly DAHDI, but the echo canceller again: /oldroot/mnt/asturw/lib /oldroot/mnt/asturw/lib/firmware /oldroot/mnt/asturw/lib/firmware/zaptel-fw-vpmadt032.bin > Possibly "dahdi_tool" from the CLI might shed some light. Compare > results 1.0.2 vs. 1.0.4 1.0.2 and 1.0.4 both give: Current Alarms: No alarms. Sync Source:Internally clocked IRQ Misses: 3 Bipolar Viol: 0 Tx/Rx Levels: 0/ 0 Total/Conf/Act: 4/ 2/ 2 > Possibly a DAHDI config error effects you with DAHDI 2.6 and not with DAHDI 2.5. Maybe a UK thing. Possibly. No idea what, though. I'll check my DAHDI config. Thanks for the help. Any other ideas? Do you think the "Error pinging DSP" could point towards something? Could the VPMADT032 have failed? I had major problems with that module back at Astlinux 0.7.2, and it related to the driver for that module. Thanks Tom -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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-devel] AstLinux 1.0.4 Released
Probably a dead end, but any TDM410P/TDM400 net5501s I've ever had have always had this issue: wctdm24xxp :00:0e.0: Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp :00:0e.0: Port 2: Installed -- AUTO FXO (FCC mode) wctdm24xxp :00:0e.0: Port 3: Not installed wctdm24xxp :00:0e.0: Port 4: Not installed wctdm24xxp :00:0e.0: Booting VPMADT032 wctdm24xxp :00:0e.0: VPM present and operational (Firmware version 125) wctdm24xxp :00:0e.0: Found a Wildcard TDM: Wildcard TDM410P (0 BRI spans, 2 analog channels) wctdm24xxp :00:0e.0: Missed interrupt. Increasing latency to 9 ms in order to compensate. wctdm24xxp :00:0e.0: Missed interrupt. Increasing latency to 15 ms in order to compensate. wctdm24xxp :00:0e.0: Missed interrupt. Increasing latency to 21 ms in order to compensate. wctdm24xxp :00:0e.0: Host failed to service card interrupt within 128 ms which is a hardunderun. wctdm24xxp :00:0e.0: ERROR: Unable to service card within 25 ms and unable to further increase latency. wctdm24xxp :00:0e.0: ERROR: Unable to service card within 25 ms and unable to further increase latency. wctdm24xxp :00:0e.0: Host failed to service card interrupt within 128 ms which is a hardunderun. wctdm24xxp :00:0e.0: ERROR: Unable to service card within 25 ms and unable to further increase latency. wctdm24xxp :00:0e.0: ERROR: Unable to service card within 25 ms and unable to further increase latency. wctdm24xxp :00:0e.0: Host failed to service card interrupt within 128 ms which is a hardunderun. All installs I've had have had the " Unable to service card within 25 ms" error, and some have the hardunderun one. The dmesg above is from the current live 1.0.2 box. Google mentions noapic=yes as a possible solution to interrupt problems, but I don't know if that is relevant/an option on the net5501. The other meaningful page I've found (plenty of replies from sruffell) deals with interrupts: http://asteriskfaqs.org/2010/09/08/asterisk-users/problem-with-new-aex800-ca rd-dying-because-of-interrupt-problems.html Any ideas what I should do next? I shall try to register the card with Digium and see if they can help out. Thanks Tom -Original Message- From: Lonnie Abelbeck [mailto:li...@lonnie.abelbeck.com] Sent: 16 August 2012 17:29 To: AstLinux Users Mailing List Cc: Tom Chadwin Subject: Re: [Astlinux-users] [Astlinux-devel] AstLinux 1.0.4 Released Tom, My suggestions... (I'm not a DAHDI guru) 1) Any DAHDI syslog errors with AstLinux 1.0.4 ? 2) From the asterisk prompt "dahdi restart" any errors with AstLinux 1.0.4 ? 3) From the CLI prompt "show-union", any dahdi files/modules shown ? 4) Possibly "dahdi_tool" from the CLI might shed some light. Compare results 1.0.2 vs. 1.0.4 5) Possibly a DAHDI config error effects you with DAHDI 2.6 and not with DAHDI 2.5. Maybe a UK thing. Lonnie On Aug 16, 2012, at 10:00 AM, Tom Chadwin wrote: > Nothing in the changelog jumps out at me as being a likely cause, but > it must be something in DAHDI between 2.5.0.2 and 2.6.0. Not found any > reports of similar symptoms online. > > Any ideas? > > Tom > > PS Never enjoyed reading an entry in a changelog so much as "Force > some reserved bits to really be 1 in E1 mode (otherwise terrorists will win)." > > > -Original Message- > From: Tom Chadwin [mailto:nnpait.servi...@googlemail.com] > Sent: 16 August 2012 14:47 > To: 'AstLinux Users Mailing List' > Subject: RE: [Astlinux-devel] AstLinux 1.0.4 Released > > [Mistakenly originally posted to -devel - apologies] > > Thanks, both. Some more details: > > We have various boxes with berofix ISDN (BRI and PRI) which are > working fine, now at 1.0.4. We have one box with a TDM410P 2FXO. This > was running fine with Astlinux 1.0.2 (not 1.0.3). I upgraded to 1.0.4, > and bizarrely we end up with one-way audio on calls over the FXO - > user on SIP handset behind that Astlinux box hears nothing, but external party can hear them. > IAX2 calls are fine. > > Reverted to 1.0.2, and problem disappeared. Upgraded to 1.0.3 (worked > out the URL of that firmware by reading upgrade-image-check code - > would be worth documenting somewhere, or enable directory listing via > HTTP on mirror.astlinux.org). Problem reappeared. Have reverted again > to 1.0.2, and problem is gone. > > So, I'm going to start looking through the DAHDI 2.6.0 changelog > (thanks, Michael). I am hamstrung by my lack of knowledge. I know the > driver in question is wctdm24xxp, but I don't know what dependencies > that has. Much of the DAHDI changelog is Astribank stuff, and hence > presumably irrelevant, but I'll do my best. > > If anyone else has any thoughts, or can recreate this problem, I'd be > grateful to hear it. > > Thanks > > Tom > > > -Original Message- > From: Michael Keuter [mailto:li...@mksolutions.info] > Sent: 16 August 2012 13:03 > To: AstLinux Developers Mailing List > Subject: Re: [Astlinux-devel] AstLinux
Re: [Astlinux-users] [Astlinux-devel] AstLinux 1.0.4 Released
> Any DAHDI syslog errors with AstLinux 1.0.4 ? Looks like it might be the echo canceller: wctdm24xxp :00:0e.0: Error pinging DSP (2) This error is not present in 1.0.2. > From the asterisk prompt "dahdi restart" any errors with AstLinux 1.0.4 ? ingrampbx*CLI> dahdi restart Destroying channels and reloading DAHDI configuration. Initial softhangup of all DAHDI channels complete. Final softhangup of all DAHDI channels complete. == Unregistered channel -2 == Unregistered channel 1 == Unregistered channel 2 == Parsing '/etc/asterisk/chan_dahdi.conf': Found [Aug 17 09:04:55] WARNING[2919]: chan_dahdi.c:1313 dahdi_open: Unable to specify channel 1: Device or resource busy -- Reconfigured channel 1, FXS Kewlstart signalling -- Reconfigured channel 2, FXS Kewlstart signalling -- Automatically generated pseudo channel == Parsing '/etc/asterisk/users.conf': Found Not sure if that WARNING is a concern. I have no other DAHDI boxes with which to compare. > From the CLI prompt "show-union", any dahdi files/modules shown ? Not exactly DAHDI, but the echo canceller again: /oldroot/mnt/asturw/lib /oldroot/mnt/asturw/lib/firmware /oldroot/mnt/asturw/lib/firmware/zaptel-fw-vpmadt032.bin > Possibly "dahdi_tool" from the CLI might shed some light. Compare results 1.0.2 vs. 1.0.4 1.0.2 and 1.0.4 both give: Current Alarms: No alarms. Sync Source:Internally clocked IRQ Misses: 3 Bipolar Viol: 0 Tx/Rx Levels: 0/ 0 Total/Conf/Act: 4/ 2/ 2 > Possibly a DAHDI config error effects you with DAHDI 2.6 and not with DAHDI 2.5. Maybe a UK thing. Possibly. No idea what, though. I'll check my DAHDI config. Thanks for the help. Any other ideas? Do you think the "Error pinging DSP" could point towards something? Could the VPMADT032 have failed? I had major problems with that module back at Astlinux 0.7.2, and it related to the driver for that module. Thanks Tom -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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-devel] AstLinux 1.0.4 Released
> http://wiki.openvox.cn/index.php/Troubleshooting_of_Analog_cards I can't see anything relevant in here. Thanks Tom -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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.
