Dahdi configuration - echo problems on transferred calls

Hi guys! I have a specific problem with dahdi configuration, users have echo problems when a call comes from outside and transferred. I have all inbound routed to an exten. and than the entrance ext transfers the call to the destination exten.
The entrance exten doesn’t have echo problems, all the destination extens(meaning sip or iax) have echo problems for calls coming this way.
I have the latest distro installed (passed from trixbox - and tried to put the same configurations I had in the Zap).
this is the dahdi status (I know that 1 fxo is maybe dead :slight_smile: )

[code][[email protected] ~]# service dahdi status

Span 1: WCTDM/4 “Wildcard TDM400P REV I Board 5” (MASTER)

1 FXO FXSKS
2 FXO FXSKS
3 FXO FXSKS RED
4 FXO FXSKS
[[email protected] ~]# service dahdi start
Loading DAHDI hardware modules:
wct4xxp: [ OK ]
wcte12xp: [ OK ]
wct1xxp: [ OK ]
wcte11xp: [ OK ]
wctdm24xxp: [ OK ]
wcfxo: [ OK ]
wctdm: [ OK ]
wcb4xxp: [ OK ]
wctc4xxp: [ OK ]
xpp_usb: [ OK ]

Running dahdi_cfg: [ OK ]
[/code]
tried to add this two lines on dahdi\system.conf but nothing changed

channels=1-4
echocanceller=mg2,1-4 

I have this on dahdi\geconf_parameters

fxoks=1
fxoks=2
fxoks=3
fxoks=4

I have this on chan_dahdi.conf
I changed echocancel, echocancelwhenbridged and echotraining
stoped the service and restarted but nothing changed.

;
; Zapata telephony interface
;
; Configuration file

[trunkgroups]

[channels]

language=en
context=from-zaptel
signalling=fxs_ks
rxwink=300		; Atlas seems to use long (250ms) winks
;
; Whether or not to do distinctive ring detection on FXO lines
;
;usedistinctiveringdetection=yes
busydetect=yes
busycount=10
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=800
rxgain=0.0
txgain=0.0
group=0
callgroup=1
pickupgroup=1
immediate=no

;faxdetect=both
;faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no


#include dahdi-channels.conf

group=1

;Include AMP configs
#include chan_dahdi_additional.conf

I am not an expert on this.
Any help is appreciated

If is a Digium card do you have an hardware echo cancel module on your card? If you do, check that its firmware has loaded using dmesg | less. There is a problem with drivers of older modules. There is a thread on the subject with a fix, just search for it.

If you don’t have hardware cancel then do fxotune which does wonders to echo.

Remember if there is a hardware module in place it takes presidence even though it might not have loaded its firmware.