similar to: Unable to enable echo cancellation on channel 1 (No such device)

Hi All; To overcome the echo problem, what mainly I have to do in the configuration other than the following line in the system.conf under dahdi directory? echocanceller=mg2,1-16 1) How can I know if the digium card supporting echo cancellator? 2) If I am getting a message in the consol that unable to enable the echo cancelator, then what does it means? The hardware is not supporting echo

Hello On a brand new CentOS 5.5 host, I wanted to install Dahdi before installing Asterisk 1.4.x. So I untarred dahdi-linux-complete-2.4.0+2.4.0.tar.gz, followed by make, make install, make config. Next, I created the following files from scratch: ============ /etc/modprobe.d/dahdi.conf: options wctdm opermode=FRANCE ============ /etc/dahdi/modules wctdm ============ /etc/dahdi/system.conf

Hello all, Ok it is Sunday afternoon and I am going crazy. I have been running in circles so long that I can't think straight. As an example, I sent this message to the wrong address the first try, AAARRRRGGGGGGHHHHH. I have Asterisk 1.6.0.6 and DAHDI Tools Version - 2.1.0.2, DAHDI Version: 2.1.0.4, OpenSuSE 10.3 x86_64, tdm422 at the end of installing dahdi-linux and dahdi-tools I get:

Just another bit of info which might help solve this: Looking at the Asterisk log messages - I notice when I start up Asterisk, I see the error: pbx_config.c: Can't use 'next' priority on the first entry! Could I be right that its something got to do with priorities? I changed the incomingpstn context to the following eliminating the 'n' field and still the same errors were

Hi, Yes InternalExtension is the context and 2093 the extension. Just to explain something odd that?s happening (and I?m very stumped with this) .I think my contexts are definately the reason that I can?t interrupt the menu for incoming pstn calls to choose a submenu: My users register with my sip proxy (SER). Therefore when I create an entry for them in sip.conf I set only one context. Also to

Hi all! I have installed a quite old Asterisk 1.6.2.0-rc2 with latest DAHDI on Ubuntu 9.10 from repository. It is working now but mysql logging is very strange. All calls have logged in mysql cdr table, which is fine, but disposition is 'NO ANSWER' even if I had talked on phone. Duration is correct but billsec is zero. Any idea why? Unfortunately I cannot upgrade to newer version because

Dear, I have Asterisk 1.6 with an E1 Digium card with echo cancellation module. So I need to use just the echo cancellation by hardware and disable the echo cancellation by software. I use DAHDI for my telephony hardware. If the lines involved with echo cancel are: In /etc/dahdi/system.conf: echocanceller=mg2,1-15,17-31 In /etc/asterisk/chan_dahdi.conf: echocancel=yes echocancelwhenbridged=no

Hi all, I am having difficulty getting incoming PSTN calls working. I have set up an account with a third party provider. In my system, the user register with SER and use Asterisk for PSTN access, voicemail etc My provider told me to change my sip.conf as follows register => username:password@sip.blueface.ie/2093 ; To receive incoming calls specify this block and

Hi All - I pulled from a working system a TDM400 with one s110 fxs and three x100 fxos. I put it into a new box and the fxs no longer works. The fxos work just fine. I thought it was odd, but I chalked it up to a random chance failure and ordered another s110. The replacement doesn't work either, and now I'm confused. dahdi_scan recognizes the s110, but it says it fails. Output

Greetings folks- I'm experiencing issues with a freshly installed box. When a call comes in via PRI (Sangoma AFT-A104), I see this in my logs: [Dec 15 14:26:10] WARNING[23546] chan_dahdi.c: Unable to enable echo cancellation on channel 12 (Invalid argument) [Dec 15 14:26:10] WARNING[23546] chan_dahdi.c: Unable to enable echo cancellation on channel 8 (Invalid argument) [Dec 15 14:26:10]

HI, I'm using asterisk-1.4.24, dahdi-linux-complete-2.4.0+2.4.0 and libpri-1.4.11.4 When dial, when 492131 answer, in console appear some error messages -- AGI Script Executing Application: (DIAL) Options: (DAHDI/g1/492131|60) -- Requested transfer capability: 0x00 - SPEECH -- Called g1/492131 [Dec 4 11:15:59] WARNING[7669]: chan_dahdi.c:1776 dahdi_enable_ec: Unable to enable

Hi, I have an issue which is kind of a catch 22 situation. I had outgoing calls to my new PSTN provider working perfectly. Then I started focussing on incoming calls. It seems that I can solve an error which gets my incoming calls working but that in turns means my outgoing calls don't work. - Strange Anyhow I was getting an error: Process_sdp: No compatible codecs! And from the SIP

I've got a piece of CPE equipment that has an FXS port that I have tied to an FXO port on a TDM400 clone card. Normally, if I go off-hook with a standard telephone connected to it, I get a dialtone. If I dial a digit, and send a hookflash, the device will provide a dialtone back for the next available channel on the device. I'm trying to recreate this same behavior with Asterisk,

Hello I'm trying to install Dahdi through source code on a Fedora 13 host to use an OpenVox PCI card with a single FXO port, but dahdi_cfg -vv isn't happy. 1. After successfully running "make all; make install; make config", I edited /etc/dahdi/system.conf thusly: loadzone=fr defaultzone=fr fxsks=1 2. Then ran "dahdi_cfg -vv" which says: ------------- DAHDI Tools

-- Attempting call on DAHDI/1wwwwww for smvoice_callprogress at smvoice-dialout:1 (Retry 1) [Oct 16 14:36:42] WARNING[16408]: chan_dahdi.c:8132 dahdi_request: Unknown option 'w' in '1wwwwww' [Oct 16 14:36:43] WARNING[16408]: chan_dahdi.c:1481 dahdi_enable_ec: Unable to enable echo cancellation on channel 1 (No such device) Does DAHDI not know about the W ??? I think zaptel used

Hello No matter if I use the entry-level OpenVox A400 with a single FXO module or the most-often-garbage card from ww.x100p.com, I get the following error after just adding this card to Mini-ITX with a single PCI slot (OS = CentOS 5.4): ============ # lspci -v 03:00.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface Subsystem: Unknown device b100:0003

Hello! I want to use TE121 for E1 data link to cisco. Really only for tests now. So I wrote: span = 1,1,0,ccs,hdb3,crc4 #span=1,1,0,esf,b8zs nethdlc=1-31:hdlc0 may be first line is wrong, problem is somewhere else anyway. Just because I get: # dahdi_cfg DAHDI_CHANCONFIG failed on channel 1: Function not implemented (38) This is centos 6.4 box with dahdi 2.7.0.1. Could you tell me is it

On a BT line, how do I determine whether the number on an incoming call has been deliberately withheld (by dialling 141) or is merely unavailable (e.g. because it originated from overseas or passed through some ancient switching equipment) ? In the first case, I want the caller to be played a message to the effect that we are not at home to anonymous cowards but if their business is

Hello I was editing files manually, and noticed that if I include the familiar "fxsks=1" in /etc/dahdi/system.conf, Dahdi fails loading: ===================== # cat /etc/dahdi/system.conf loadzone = fr defaultzone = fr fxsks=1 ===================== # /etc/init.d/dahdi start Loading DAHDI hardware modules: wctdm: [ OK ] /usr/share/dahdi/waitfor_xpds: Missing

Running Asterisk 1.6.2.9, DAHDI 2.3.0.1, CentOS 5.5 (update to date as of a week ago), I've installed a Digium AEX800P with 2 X400M FXO Modules and 1 VPMADT032 Module, hooked up to 5 analog lines. I get the error message referenced in the subject in my dmesg output everytime I load / reload DAHDI using the command "system dahdi start/restart". When I make an outbound call over