* You are viewing Posts Tagged ‘echo cancellation’

Echo Cancellation

Hello;

If our Digium Telephony Card does not support echo cancellation like (1TDM410PLF or 1AEX410PLF), what is the best and simple way to overcome the echo?

Regards Bilal

Bug? ‘dahdi Show Channel X’ HWEC Echo Cancellation Display Is Incorrect While Not On A Call

When doing a ‘dahdi show channel X’ from the asterisk console, when the line is not part of a call the echo cancellation line ALWAYS says ‘currently OFF’. Once a call is in progress, it will change to ‘ON’. Is this a bug, or is the behavior by design?

My setup:

Asterisk 10.10.0
Dahdi 2.6.1
TE820 T1 card

In chan_dahdi.cfg:
… echocancel=yes echocancelwhenbridged=yes echotraining=800



And in #included chan_dahdi_additional.conf (this is a freepbx install):


;;;;;;[3884]
signalling=fxo_ks pickupgroup=
mailbox=3884@default immediate=no echotraining=800
echocancelwhenbridged=yes echocancel=yes context=from-internal callprogress=no callgroup=
callerid=John Doe <3884>
busydetect=no busycount=7
accountcode=
channel=>73


-Justin Killen

Dahdi 2.6.1 with OSLEC support

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@callcenter ~]# dahdi_cfg -vvv
DAHDI Tools Version – 2.6.1

DAHDI Version: 2.6.1
Echo Canceller(s): HWEC
Configuration
======================

Channel map:

Channel 01: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 01)
Channel 02: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 02)
Channel 03: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 03)
Channel 04: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 04)
Channel 05: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 05)
Channel 06: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 06)
Channel 07: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 07)
Channel 08: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 08)
Channel 09: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 09)
Channel 10: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 10)
Channel 11: FXS Kewlstart (Default) (Echo Canceler: oslec)(Slaves: 11)
Channel 12: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 12)
Channel 13: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 13)
Channel 14: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 14)
Channel 15: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 15)
Channel 16: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 16)

16 channels to configure.

Setting echocan for channel 1 to oslec
DAHDI_ATTACH_ECHOCAN failed on channel 1: Invalid argument (22)

I try to change to /etc/dahdi/system.conf to
fxsks=1
echocanceller=hwec,1

Still doesn’t work and this error still occured: DAHDI_ATTACH_ECHOCAN
failed on channel 1: Invalid argument (22)

[root@callcenter dahdi]# asterisk -rvvv
Asterisk 1.8.7.0, Copyright (C) 1999 – 2011 Digium, Inc. and others.
Created by Mark Spencer
Asterisk comes with ABSOLUTELY NO WARRANTY; type ‘core show warranty’ for
detail
s.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it
under
certain conditions. Type ‘core show license’ for details.
=========================================================================
== Parsing ‘/etc/asterisk/asterisk.conf': == Found
== Parsing ‘/etc/asterisk/extconfig.conf': == Found
Connected to Asterisk 1.8.7.0 currently running on callcenter (pid = 6908)
Verbosity is at least 3
callcenter*CLI> dahdi show channel 1
Channel: 1
File Descriptor: 12
Span: 1
Extension:
Dialing: no
Context: from-pstn
Caller ID:
Calling TON: 0
Caller ID name:
Mailbox: none
Destroy: 0
InAlarm: 0
Signalling Type: FXS Kewlstart
Radio: 0
Owner:
Real:

Callwait:

Threeway:

Confno: -1
Propagated Conference: -1
Real in conference: 0
DSP: no
Busy Detection: no
TDD: no
Relax DTMF: yes
Dialing/CallwaitCAS: 0/0
Default law: ulaw
Fax Handled: no
Pulse phone: no
Gains (RX/TX): 0.00/0.00
Dynamic Range Compression (RX/TX): 0.00/0.00
DND: no
*Echo Cancellation:
128 taps
(unless TDM bridged) currently OFF*
Wait for dialtone: 0ms
Actual Confinfo: Num/0, Mode/0x0000
Actual Confmute: No
Hookstate (FXS only): Offhook
callcenter*CLI>

wct4xxp Interrupts not detected with dahdi 2.6, but working ok with 2.5

Hi,

I’ve tried upgrading one of my servers with yum update to the latest dahdi/asterisk, and found out that my 4th gen TE410P is failing the dahdi init with

Running dahdi_cfg: DAHDI startup failed: Input/output error

Rolling back to 2.5 restores the normal operation, and reading the dahdi 2.6 change log I think I’m hitting this bug fix with my mobo/card combo?

2011-12-14 19:02 +0000 [r10379-10380] Shaun Ruffell

With dahdi 2.6 I’m getting this:

#cat /proc/interrupts

209: 1 0 IO-APIC-level wct4xxp

No interrupts?!

#dmesg

kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 24 (level, low) -> IRQ 209
kernel: wct4xxp 0000:02:01.0: Firmware Version: c01a016c
kernel: wct4xxp 0000:02:01.0: FALC Framer Version: 2.1 or earlier
kernel: wct4xxp 0000:02:01.0: Found a Wildcard: Wildcard TE410P (4th Gen)
kernel: VPM450: echo cancellation for 128 channels
kernel: wct4xxp 0000:02:01.0: VPM450: hardware DTMF disabled.
kernel: wct4xxp 0000:02:01.0: VPM450: Present and operational servicing 4 span(s)

kernel: wct4xxp 0000:02:01.0: TE4XXP: Span 1 configured for CCS/HDB3/CRC4
kernel: wct4xxp 0000:02:01.0: RCLK source set to span 1
kernel: wct4xxp 0000:02:01.0: System timing mode, RCLK set to span 1
kernel: wct4xxp 0000:02:01.0: TE4XXP: Span 2 configured for CCS/HDB3/CRC4
kernel: wct4xxp 0000:02:01.0: RCLK source set to span 1
kernel: wct4xxp 0000:02:01.0: System timing mode, RCLK set to span 1
kernel: wct4xxp 0000:02:01.0: TE4XXP: Span 3 configured for CCS/HDB3/CRC4
kernel: wct4xxp 0000:02:01.0: RCLK source set to span 3
kernel: wct4xxp 0000:02:01.0: Recovered timing mode, RCLK set to span 3
kernel: wct4xxp 0000:02:01.0: SPAN 3: Primary Sync Source
kernel: wct4xxp 0000:02:01.0: Interrupts not detected.

With dahdi 2.5 everything is OK:

#cat /proc/interrupts

201: 9157 962863 IO-APIC-level wct4xxp

#dmesg
kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 24 (level, low) -> IRQ 201
kernel: wct4xxp 0000:02:01.0: Found TE4XXP at base address f2000000, remapped to f887c000
kernel: wct4xxp 0000:02:01.0: Firmware Version: c01a016c
kernel: wct4xxp 0000:02:01.0: Burst Mode: On
kernel: wct4xxp 0000:02:01.0: Octasic Optimizations: Enabled
kernel: wct4xxp 0000:02:01.0: FALC Framer Version: 2.1 or earlier
kernel: wct4xxp 0000:02:01.0: Board ID: 00
kernel: wct4xxp 0000:02:01.0: Reg 0: 0x37554400
kernel: wct4xxp 0000:02:01.0: Reg 1: 0x37554000
kernel: wct4xxp 0000:02:01.0: Reg 2: 0x00000000
kernel: wct4xxp 0000:02:01.0: Reg 3: 0x00000000
kernel: wct4xxp 0000:02:01.0: Reg 4: 0x00003101
kernel: wct4xxp 0000:02:01.0: Reg 5: 0x00000000
kernel: wct4xxp 0000:02:01.0: Reg 6: 0xc01a016c
kernel: wct4xxp 0000:02:01.0: Reg 7: 0x00001f00
kernel: wct4xxp 0000:02:01.0: Reg 8: 0x00000000
kernel: wct4xxp 0000:02:01.0: Reg 9: 0x00ff0031
kernel: wct4xxp 0000:02:01.0: Reg 10: 0x0000004a
kernel: wct4xxp 0000:02:01.0: Found a Wildcard: Wildcard TE410P (4th Gen)
[snip]
wct4xxp 0000:02:01.0: TE4XXP: Span 1 configured for CCS/HDB3/CRC4
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000010c, CIS = 0080
wct4xxp 0000:02:01.0: RCLK source set to span 1
wct4xxp 0000:02:01.0: System timing mode, RCLK set to span 1
wct4xxp 0000:02:01.0: TE4XXP: Span 2 configured for CCS/HDB3/CRC4
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000010c, CIS = 0080
wct4xxp 0000:02:01.0: RCLK source set to span 1
wct4xxp 0000:02:01.0: System timing mode, RCLK set to span 1
wct4xxp 0000:02:01.0: TE4XXP: Span 3 configured for CCS/HDB3/CRC4
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000010d, CIS = 0081
wct4xxp 0000:02:01.0: RCLK source set to span 3
wct4xxp 0000:02:01.0: Recovered timing mode, RCLK set to span 3
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000010a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: SPAN 3: Primary Sync Source
wct4xxp 0000:02:01.0: TE4XXP: Span 4 configured for CCS/HDB3/CRC4
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000d, CIS = 0084
wct4xxp 0000:02:01.0: RCLK source set to span 3
wct4xxp 0000:02:01.0: Recovered timing mode, RCLK set to span 3
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000b, CIS = 0088
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000b, CIS = 008a
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000b, CIS = 0085
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000b, CIS = 008a
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000
wct4xxp 0000:02:01.0: 2G: Got interrupt, status = 0000000a, CIS = 0080
wct4xxp 0000:02:01.0: Reg 5 is 00000000

Very slow faxing with Fax For Asterisk

I have been testing Fax For Asterisk with an analog fax sitting behind a Grandstream Handytone 286. I have been sending a number of faxes but I find that they send extremely slow. In my most basic test of sending from the HT286 straight to a tiff image
on Asterisk on the same subnet I am seeing as much as 200 seconds to send a single page. Debug in the CLI shows that we are negotiating down to T.38 4800. I have disabled echo cancellation and noise suppression on the HT286 but with no change. I have
tested with different fax machines (HP 1040 Fax and Sharp UX-B800SE) but with the same results. My Asterisk and FFA module versions are:

FAX For Asterisk Components:
Applications: SVN-branch-1.8-digiumphones-r357808-/branches/1.8
Digium FAX Driver: 1.8.4_1.3.0 (optimized for generic_64)

Your suggestions are appreciated. Thank you.

Chet Stevens
cwstevens@interact.ccsd.net

Questions on hardware or software-based echo cancellation

Hi,

I’m having some questions related to echo cancellation configuration
on a Digium board enabled systems (B410P, TE420, TE420B, ….) for
cases when a hardware ech canceller is present or not.

I read in TEXXX manual that when setting echocancel=yes in
chan_dahdi.conf on a VPMOCT64-equiped system, 128ms hardware echo
cancellation was enabled.

1. I’m correct thinking that it is then impossible to switch from
hardware to software echo can without removing the VPMOCT64 module
itself ?
2. Does the same also apply to HA8 and its VPMOCT032 module ?
3. Are the only options for OSLEC configuration the echocancel=128 or
echocancel=256 values in chan_dahdi.conf ?
4. How could be compared user experience with oslec/256, mg2/256,
mg2/1024 on a HA8 without hardware module ? Which would you recommend
?

Regards