i also purchased HPEC from digium but the installation refers to the full dahdi package that does not seem to be included in freepbx…
dahd_cfg -vv output:
DAHDI Tools Version - 2.11.1
Setting echocan for channel 1 to oslec
Setting echocan for channel 2 to oslec
Setting echocan for channel 3 to oslec
Setting echocan for channel 4 to oslec
Setting echocan for channel 5 to oslec
Setting echocan for channel 6 to oslec
Setting echocan for channel 7 to oslec
Setting echocan for channel 8 to oslec
Setting echocan for channel 9 to oslec
Setting echocan for channel 10 to oslec
Setting echocan for channel 11 to oslec
Setting echocan for channel 12 to oslec
yesterday i received the authentic replacement card, i placed the hardware EC on it. Now i only have one Digium card with 6 FXO channels:
dahdi_scan
[1]
active=yes
alarms=OK
description=Wildcard AEX800
name=WCTDM/0
manufacturer=Digium
devicetype=Wildcard AEX800
location=PCI Express Bus 03 Slot 09
basechan=1
totchans=8
irq=0
type=analog
port=1,FXO
port=2,FXO
port=3,none
port=4,none
port=5,FXO
port=6,FXO
port=7,FXO
port=8,FXO
Setting echocan for channel 1 to oslec
Setting echocan for channel 2 to oslec
Setting echocan for channel 5 to oslec
Setting echocan for channel 6 to oslec
Setting echocan for channel 7 to oslec
Setting echocan for channel 8 to oslec
OSLEC seems to be working as long as the user does not speak while the other end of the call is speaking at the same time. but the hardware EC is not being detected. Could it be a firmware issue or a DAHDI version incompatibility?
specifically
.
.
; Enable echo cancellation
; Use either “yes”, “no”, or a power of two from 32 to 256 if you wish to
; actually set the number of taps of cancellation.
;
; Note that when setting the number of taps, the number 256 does not translate
; to 256 ms of echo cancellation. echocancel=256 means 256 / 8 = 32 ms.
;
; Note that if any of your DAHDI cards have hardware echo cancellers,
; then this setting only turns them on and off; numeric settings will
; be treated as “yes”. There are no special settings required for
; hardware echo cancellers; when present and enabled in their kernel
; modules, they take precedence over the software echo canceller compiled
; into DAHDI automatically.
;
;
echocancel=yes
;
; Some DAHDI echo cancellers (software and hardware) support adjustable
; parameters; these parameters can be supplied as additional options to
; the ‘echocancel’ setting. Note that Asterisk does not attempt to
; validate the parameters or their values, so if you supply an invalid
; parameter you will not know the specific reason it failed without
; checking the kernel message log for the error(s) put there by DAHDI.
;
;echocancel=128,param1=32,param2=0,param3=14
;
; Generally, it is not necessary (and in fact undesirable) to echo cancel when
; the circuit path is entirely TDM. You may, however, change this behavior
; by enabling the echo canceller during pure TDM bridging below.
;
echocancelwhenbridged=yes
;
; In some cases, the echo canceller doesn’t train quickly enough and there
; is echo at the beginning of the call. Enabling echo training will cause
; DAHDI to briefly mute the channel, send an impulse, and use the impulse
; response to pre-train the echo canceller so it can start out with a much
; closer idea of the actual echo. Value may be “yes”, “no”, or a number of
; milliseconds to delay before training (default = 400)
;
; WARNING: In some cases this option can make echo worse! If you are
; trying to debug an echo problem, it is worth checking to see if your echo
; is better with the option set to yes or no. Use whatever setting gives
; the best results.
;
; Note that these parameters do not apply to hardware echo cancellers.
;
;echotraining=yes
;echotraining=800
.
.
.
If the hardware is there
I hear you, i think it may be incompatibility of cards i had initially bought the HWEC (VPM100M) for the tdm800p but now i am using a AEX800. it may be that the VPM100M is not compatible with the AEX800, in the product documentation they recommend VPMADT032. i need to validate if in fact the VPM100M is not compatible with my new card.