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

The Asterisk Development Team is pleased to announce the release of DAHDI-Linux 2.5.0.2 and DAHDI-Tools 2.5.0.2.

2.5.0.2 is a bug fix release. It is recommended that current users of v2.5 to upgrade.

DAHDI-Linux 2.5.0.2, DAHDI-Tools 2.5.0.2, and DAHDI-Linux-Complete 2.5.0.1+2.5.0.1 are available for immediate download at:

http://downloads.asterisk.org/pub/telephony/dahdi-linux
http://downloads.asterisk.org/pub/telephony/dahdi-tools
http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete

Issues closed by this release:
DAHLIN-257: wcb4xxp shows hardware EC in /proc/dahdi/* for B410P although vpmsupport=0
DAHLIN-260: wctdm24xxp/base.c fails to compile in 2.6.16 kernel

The DAHDI-Linux short log from v2.5.0.1 is:

Shaun Ruffell (8):
dahdi: Decrease the initial coretimer delay to 4ms from 1 second.
wctdm24xxp, wcte12xp: Advertise VPMOCT032 presence in dahdi_span.devicetype.
dahdi: Check for master in DAHDI_STARTUP / resolves MeetMe regression.
wctdm24xxp: Set dahdi_span.devicetype string in one place.
wctc4xxp: Allow G723 SID frames to pass to the hardware decoder.
wct4xxp: Fix condition where hardware echo canceler erroneously mutes DTMF.
wcb4xxp: Do not show LASVEGAS2 as echocan name if vpmsupport is set to 0
dahdi: Move WARN_ON_ONCE from wctc4xxp driver to include/dahdi/kernel.h

Tzafrir Cohen (1):
xpp: fxs: bugfix for 2fxs+6fxo cards

The DAHDI-Tools short log from v2.5.0.1 is:

Shaun Ruffell (2):
dahdi_genconf: Assume spans with unknown term types are software selectable.
dahdi_genconf: Use ‘dahdi_scan’ to determine span_type for B410P cards.

And the diff stat for this release from v2.5.0.1 is:

drivers/dahdi/dahdi-base.c | 6 +++++-
drivers/dahdi/wcb4xxp/base.c | 2 +-
drivers/dahdi/wct4xxp/base.c | 2 –
drivers/dahdi/wctc4xxp/base.c | 21 ++++—————–
drivers/dahdi/wctdm24xxp/base.c | 31 +++++++++++++++++++++++——–
drivers/dahdi/wcte12xp/base.c | 8 +++++++-
drivers/dahdi/xpp/card_fxs.c | 39 +++++++++++++++++++++++++++++++——–
include/dahdi/kernel.h | 13 +++++++++++++
8 files changed, 84 insertions(+), 38 deletions(-)

and for DAHDI-Tools:

xpp/perl_modules/Dahdi/Span.pm | 37 +++++++++++++++++++++++++++++++++++–
1 files changed, 35 insertions(+), 2 deletions(-)

For a full list of changes in these releases, please see the ChangeLog at
http://svn.asterisk.org/svn/dahdi/linux/tags/2.5.0.2/ChangeLog and
http://svn.asterisk.org/svn/dahdi/tools/tags/2.5.0.2/ChangeLog .

Issues found in this release can be reported in the
DAHDI-Linux [1] and DAHDI-Tools [2] projects at
https://issues.asterisk.org/jira

[1] https://issues.asterisk.org/jira/browse/DAHLIN
[2] https://issues.asterisk.org/jira/browse/DAHTOOL

Thank you for your continued support of Asterisk!

Dear;

We are using ISDN PRI, and the telephony card is Digium card supported 2 ports of E1s, and in the system.conf, I selected the zone to be uk loadzone = uk (loadzone = uk and defaultzone=uk). Actually the Asterisk in Jordan and connected to Jordan Telecom provider.

This is the output of some commands that help to give the specification of the hardware:

[root@CC dahdi]# dahdi_hardware
pci:0000:05:08.0 wct4xxp+ d161:1220 Wildcard TE220 (5th Gen)

[root@CC dahdi]# dahdi_scan
[1]
active=yes
alarms=OK
description=T2XXP (PCI) Card 0 Span 1
name=TE2/0/1
manufacturer=Digium
devicetype=Wildcard TE220 (5th Gen) (VPMOCT064)
location=Board ID Switch 0
basechan=1
totchans=31
irq=34
type=digital-E1
syncsrc=1
lbo=0 db (CSU)/0-133 feet (DSX-1)
coding_opts=AMI,HDB3
framing_opts=CCS,CRC4
coding=HDB3
framing=CCS/CRC4
[2]
active=yes
alarms=UNCONFIGURED
description=T2XXP (PCI) Card 0 Span 2
name=TE2/0/2
manufacturer=Digium
devicetype=Wildcard TE220 (5th Gen) (VPMOCT064)
location=Board ID Switch 0
basechan=32
totchans=31
irq=34
type=digital-E1
syncsrc=1
lbo=0 db (CSU)/0-133 feet (DSX-1)
coding_opts=AMI,HDB3
framing_opts=CCS,CRC4
coding=
framing=CAS

Regards
Bilal

I have naive question. I do not have any hardware on my asterisk host. All I
have are either SIP trunk for DID or hardware ATA which bridges the asterisk
to PSTN. Do I need Dahdi install? Do i have ztdummy for timing issue? I
encounter problem in this when I try to install Dahdi latest but I found it
is not running, Instead it runs when service starts but I can’t find its
status when I type in service dahdi status.

I am using Asterisk 1.8.7 on centos 5.7 32 bit.

CK

Is there any reason not to run Asterisk on an Intel Atom board?