similar to: debian/dahdi/zaphfc - Unable to receive TEI from network!

Hi list, Attempting to get an ISDN-BRI line connected using an HFC-S PCI card together with Asterisk v1.4.14 and Zaptel 1.4.7 on a Debian etch system, I find that I can't access the card's resources because the channels are always be busy. An attempt to call out results in the following CLI output: == Primary D-Channel on span 1 down == Primary D-Channel on span 2 down

Hi list, After upgrading from Asterisk v1.2 to v1.4.14, all kinds Zaptel error messages related to my HFC-S PCI card disappeared, but now I can't access the card's resources because it always seems to be busy. Any idea why? Thanks, Jaap PS -- Below is some info regarding my configuration. =========================== Zaptel version: 1.4.7 (incl. firmware and modules). OS: Debian

Trying to build oslec. Following dahdi-linux README I copy drivers/staging/echo to dahdi-linux/drivers/staging. I uncomment the 2 oslec lines in drivers/dahdi/Kbuild. That doesn't work: /home/asterisk/build/dahdi/svn/dahdi-linux/drivers/dahdi/dahdi_echocan_oslec.c:33:35: error: ../staging/echo/oslec.h: No such file or directory So: wget

Hi I wonder if anyone has any sugestions I have had a TDM400 for a couple of years, and I have always had problems with noise on the line, so tonight I have been doing some research and have found that if I load the CPU dahdi_test has almost perfect results and no noise dahdi_test Opened pseudo dahdi interface, measuring accuracy... 99.997% 99.999% 99.998% 99.997% 99.999% 99.998% 99.998%

I'm hoping someone can help me here. I've purchased replacement systems for 3 aging 1.4.x installs. I'm hoping to setup Asterisk 11, dahdi 2.6.1 and Oslec. I'm also moving those installs from Mandriva 10.0 to Debian 6.06 (Squeeze). In my testing, the TE220P PCIe cards that I have, the timing was awful on both slots, so I compiled Kernel 3.6.9 from kernel.org. Timing jumped to

Hello list, I'm facing a little issue with dahdi attempting to load the OSLEC echo canceller into my current kernel. After compiling dahdi 2.3.0.1 with OSLEC support, I get the following error when set 'oslec' as the echocanceller: DAHDI_ATTACH_ECHOCAN failed on channel 1: Invalid argument (22) - Similar errors are *NOT* present using other echo canncelers. - I tried adding the

Hi All, I have followed below steps to enable echo cancellation. # cd /usr/src # wget http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.28.tar.bz2 # tar xjf linux-2.6.28.tar.bz2 # tar zxvf dahdi-linux-2.1.0.4.tar.gz # ln -s /usr/src/dahdi-linux-2.1.0.4 /usr/src/dahdi # mkdir /usr/src/dahdi/drivers/staging # cp -fR /usr/src/linux-2.6.28/drivers/staging/echo /usr/src/dahdi/drivers/staging # sed -i

On Thu, 22 Oct 2015 15:06:59 +0300 Tzafrir Cohen <tzafrir.cohen at xorcom.com> wrote: > On Wed, Oct 21, 2015 at 01:33:27PM -0200, Ethy H. Brito wrote: > > > > Hi > > > > Who should insert dahdi_echocan_oslec.ko module in Ubuntu 14.04? > > dahdi_echocan_oslec should be built by default. What you may miss is the > 'echo.ko' (OSLEC) kernel module.

On Fedora 11, gcc-4.4, I'm trying to build oslec in dahdi-linux, but: [asterisk at asterisk dahdi-linux]$ make make -C drivers/dahdi/firmware firmware-loaders make[1]: Entering directory `/home/asterisk/build/dahdi/svn/dahdi-linux/drivers/dahdi/firmware' make[1]: Leaving directory `/home/asterisk/build/dahdi/svn/dahdi-linux/drivers/dahdi/firmware' make -C

Hello everyone, I have a Atcom AX-1600P(1) card with a FXO module and I can't configure it. I have four extension with this PJSIP settings: --- /etc/asterisk/pjsip.conf --- [transport-udp] type=transport protocol=udp bind=0.0.0.0 [6001] type=endpoint transport=transport-udp context=from-internal disallow=all allow=ulaw auth=6001 aors=6001 direct_media=no rtp_symmetric=yes force_rport=yes

Hi List. I've bought a new server for my home asterisk installation and I'm trying to install asterisk with dahdi drivers and OSLEC. To do that I've got the svn dahdi-linux trunk revision 5366 and the echo subproject from the 2.6.28-rc6 Linux kernel sources. As reported in the dadhi README file I've uncommented out the two OSLEC related lines at Kbuild file in the

Hi, I setup an asterisk system (asterisk 1.8-rc3, dahdi-linux-2.4.0 with dahdi-extra from Tzafrirs git, kernel 2.6.35.4). The hardware is an older pc system with Celeron CPU (2.5 GHz) with a Beronet BN4S0 ISDN card. The system starts without any errors. I discovered a severe issue. The kernel panics on a very small load. The first call normally gets through. If I start the second or third call

Hi, I did replace an old asterisk box by a new shiny one (2 BRI ports used on a quad port card - BeroNet PCI Express) I noticed a message in the logs that puzzles me: May 11 19:10:02 kernel: dahdi: Master changed to B4/0/1 May 11 19:10:08 kernel: wcb4xxp 0000:05:04.0: PCI INT A disabled May 11 19:10:08 kernel: wcb4xxp 0000:05:04.0: Driver unloaded. May 11 19:10:08 kernel: dahdi: Telephony

Hi list, Has anyone been able to get ISDN-BRI support to work reliably on Asterisk 1.4? If so, I'd love to know how you did it (hardware, distro, kernel, modules, versions, config files). I've tried to get it to work on a Debian etch system with an HFC-PCI card and the zaptel package (v1.4.7, also from xorcom.com), but with no luck: all three channels that are created when the

Hi, 1. Has someone met any success at all, connecting a Digium B410P to a Patton Smartnode 4638 (with latest 5.3 firmware) ? 2. If positive, then, which signalling was used on both sides ? My project's goal is use a Patton Smartnode 4638 to act as telco BRI lines, from a B410P-enabled asterisk box. In my testings, I can see channel is respectively up (with patton web server status page)

Hi list! I'm totally fed up with bristuff (or it's instability with a simple HFC-S card), 2 out of 3 times when people try to call they get the information tone that the number is not connected. I would like to try vzaphfc and I am looking for information on it. >From previous posts I found that the only place where the sources seem to be maintained and available is at the debian

Hi Who should insert dahdi_echocan_oslec.ko module in Ubuntu 14.04? dahdi start/stop service? I have a test installation that is not launching it when asterisk/dahdi starts. Clues? Regards Ethy

Hi all, On an Asterisk/Zaptel 1.4 system, one way to gather diagnostic info is: ~# cat /proc/zaptel/* Span 1: ZTHFC1 "HFC-S PCI A Zaptel Driver card 0 [TE]" (MASTER) AMI/CCS 1 ZTHFC1/0/1 Clear (In use) 2 ZTHFC1/0/2 Clear (In use) 3 ZTHFC1/0/3 HDLCFCS (In use) Span 2: ZTHFC2 "HFC-S PCI A Zaptel Driver card 1 [TE]" AMI/CCS 4 ZTHFC2/0/1 Clear 5 ZTHFC2/0/2

so here it is, the problem that's been nagging me for the past 2 days: connected a box to my telco's NTBA <-> zap/asterisk. which works: box:/etc/asterisk# cat /proc/zaptel/1 Span 1: ZTHFC1 "HFC-S PCI A ISDN card 0 [TE] layer 1 ACTIVATED (F7)" HDB3/CCS 1 ZTHFC1/0/1 Clear (In use) 2 ZTHFC1/0/2 Clear (In use) 3 ZTHFC1/0/3 HDLCFCS (In

Hi list, I install dahdi-linux successfully with the module of oslec for the echo, but when I specify it in the system.conf the echo canceller oslec it shows me errors: DAHDI_ATTACH_ECHOCAN failed on channel 4: Invalid argument (22) I see that the echo cancellers is supported: mg2, kb1, sec2, and sec because oslec is not supported?, but he has support to compile it with dahdi_linux! best