similar to: dial_exec_full problems with TDM400

I was previously using an old computer running Asterisk 1.2 with zaptel. Once the CPU fried I switch to a new computer and I chose AsteriskNow 1.5 running in 64bits to simplify the installation process. I manage to find my way with configuring dahdi instead of zaptel and to switch all my previous config to the new computer. Now everything is fine except that even if I use the md2 echo

I am having an issue with a couple of phones where they ring, but there is a long delay after the phone is picked up before the audio starts. My setup: * Server running Asterisk 13.9.1, Dahdi 2.11.1 w/ OSLEC * Server is CentOS 7 * Quad core CPU with 16GB Ram * 2 Snom 300 phones. * NO NAT. Server and phone are on the same subnet with only a gigabit switch between them. * Digium

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

Yesterday I pulled in the latest svn of Dahdi and added the files from a recent kernel in the drivers/staging/echo structure and modified the Kbuild file so it would compile without error. I insmod'ed the module in, and modified my system.conf has echocanceller=oslec. cat /proc/dahdi/1 shows: Span 1: WCTDM/0 "Wildcard TDM410P Board 1" (MASTER) IRQ misses: 1 1

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

In order solve my incoming caller ID problem, I upgrade the dahdi to version 2.6.1 from version 2.4.x. After upgrade, I found the echo cancellation doesn't working (I'm using Digium AEX800B PCI Express card). I can hear my self talking on the phone. How to solve this? I think I need to recompile dahdi 2.6.1 with OSLEC support? how? [root at callcenter ~]# dahdi_cfg -vvv DAHDI Tools

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, I've a problem: I can't configure DAHDI with ech canceller OSLEC. I have Asterisk 1.4.24 and DAHDI 2.1.0.2. I compiled also OSLEC. But when in /etc/dahdi/systems.conf I insert value echocanceller=oslec,1-4, command dahdi_cfg -vvvvvvvvvvvv give me an error about oslec. Someone can help me? Thanks Marco -------------- next part -------------- An HTML attachment was scrubbed... URL:

From asterisk -cvvvvv == Parsing '/etc/asterisk/chan_dahdi.conf': == Found == Parsing '/etc/asterisk/users.conf': == Found -- Automatically generated pseudo channel [Nov 11 17:43:28] WARNING[5756]: chan_dahdi.c:18155 process_dahdi: Ignoring any changes to 'userbase' (on reload) at line 23. [Nov 11 17:43:28] WARNING[5756]: chan_dahdi.c:18155 process_dahdi:

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

Hi, I'm used to add OSLEC source code into asterisk and use it as default echo canceller. Currently, I'm proceeding this way: download the kernel source code roughly matching the kernel version I'm targeting with command such as "wget http://kernel.org/pub/linux/kernel/v3.0/linux-3.2.46.tar.bz2" copy the echo subtree into dahdi change dahdi's Kbuild file (for dahdi

Hi All, Which echo cancellation is good between OSLEC and MG2. Dahdi by default use MG2 echo cancellation on channel. If i want to use OSLEC then what should i need to do ? Do i need to recompile dahdi with OSLEC ? -S -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, 1. Is there any manual entry about modprobe's options relative to a given Dahdi driver (wctdm24xxp, for instance) ? 2. When loading a wctdm24xxp driver, is there any parameter to pass to modprobe to configure a span in NT/point to point mode ? 3. After running dahdi_cfg -vvvvv , I can read with dmesg : [ 1986.289277] wctdm24xxp 0000:04:06.0: xhfc: Configuring port 0 span 1 in TE mode

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.

Well, I thought I had the problem solved. Ported everything over to PJSip and build RDNS records for the phones and the server, but I am still experiencing the problem on incoming calls. ** On 6/7/2016 1:00 PM, Faheem Muhammad wrote: > I've faced the same issue. The issue was related to DNS, the reverse > lookup query failure caused the delay around(7-9 seconds). The purpose >

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

I am about to setup a new machine and based on a thread in the freetel-oslec list, I came across the idea of compiling Intel optimizations in when using oslec w/ dahdi. So I edit dahdi-linux-complete-2.1.0.4+2.1.0.2/linux/drivers/dahdi/dahdi_config.h to #define CONFIG_DAHDI_MMX which on its own wont compile. It was suggested to edit dahdi-linux-complete-2.1.0.4+2.1.0.2/linux/drivers/dahdi/Kbuild

Have an intersting issue whem migrating a site from Zap on 1.3 to DAHDI on 1.4.. Nothing special about the hardware - older TDM400 card, 2 red modules fitted... Both channels work fine under 1.2/Zaptel. With 1.4/DAHDI both channels still work OK, but only for one line - the 2nd line causes it to refuse to dial-out no matter which port it's plugged into. The Lines are bog-standard BT

I have a pretty large setup on one of my customers. Digium TE420B (with echo cancelling module), 3 Xorcom Astribanks with 32 FXS each and 1 Xorcom Astribank with 16 FXO. These FXO ports are NOT used for fax/data transmission, as they are connected to cell phones. Not really related to the issue, but there are also 250 SIP phones. The problem is that fax and dial-up connections are really

Hi, I'm using revision 6822 of Dahdi Tools. # dahdi_hardware pci:0000:05:06.0 wcb4xxp+ d161:b410 Digium Wildcard B410P # asterisk -rx "dahdi show version" DAHDI Version: 2.2.0.2 Echo Canceller: OSLEC # cat /etc/dahdi/genconf_parameters ... pri_termtype SPAN/1 TE SPAN/2 TE SPAN/3 NT SPAN/4 NT #