Dahdi 2.3.0.0 on Asterisk 1.6.2.9 problems

I’m using Asterisk 1.6.2.9 with Dahdi 2.3.0.1 on Karmic with the 2.6.31-22-generic headers. I compilied everything.
Although some things work I can’t get the echo canceller to work and various displays of the dahdi commands don’t seem to display correctly. Also the context seems to stay obstinately at “default” when I have tried to configure it to be “incoming”.

So what have I missed?

The documentation on Dahdi is far from exhaustive, you seem to have to pick up bits all over the place. Especially since the simple case of one TDM400P with 1 or more modules installed isn’t clearly explained as a starting point before moving on to BRIs and PRIs.

dmesg gives:
[ 17.524241] dahdi: Telephony Interface Registered on major 196
[ 17.524246] dahdi: Version:
[ 17.527359] wctdm 0000:02:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 17.527567] Freshmaker version: 73
[ 17.527930] Freshmaker passed register test
[ 18.020095] Module 0: Not installed
[ 18.020187] Module 1: Not installed
[ 18.020278] Module 2: Not installed
[ 18.220291] Module 3: Installed – AUTO FXO (FCC mode)
[ 18.243370] Found a Wildcard TDM: Wildcard TDM400P REV I (1 modules)

CLI> dahdi show channels
Chan Extension Context Language MOH Interpret Blocked State
pseudo default default In Service
4 default default In Service
but
CLI> dahdi show status
Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO

doesn’t show anything
and
CLI> dahdi show version
DAHDI Version: Echo Canceller: KB1

/etc/dahdi/system.conf

This file is parsed by the Dahdi Configurator, dahdi_cfg

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

channel 1, WCTDM/4/0, no module.

channel 2, WCTDM/4/1, no module.

channel 3, WCTDM/4/2, no module.

fxsks=4
echocanceller=kb1,4

Span 2: DAHDI_DUMMY/1 “DAHDI_DUMMY/1 (source: HRtimer) 1”

Global data

loadzone = fr
defaultzone = fr

/etc/asterisk/chan_dahdi.conf
#include dahdi-channels.conf
[trunkgroups]
;
; Trunk groups are used for NFAS or GR-303 connections.
;
; Group: Defines a trunk group.
; trunkgroup => ,[,…]
;
; trunkgroup is the numerical trunk group to create
; dchannel is the zap channel which will have the
; d-channel for the trunk.
; backup1 is an optional list of backup d-channels.
;
;trunkgroup => 1,24,48
;trunkgroup => 1,24
;
; Spanmap: Associates a span with a trunk group
; spanmap => ,[,]
;
; dahdispan is the DAHDI span number to associate
; trunkgroup is the trunkgroup (specified above) for the mapping
; logicalspan is the logical span number within the trunk group to use.
; if unspecified, no logical span number is used.
;
spanmap => 1,1,1
;spanmap => 2,1,2
;spanmap => 3,1,3
;spanmap => 4,1,4
[channels]
rxwink=300 ; Atlas seems to use long (250ms) winks
busydetect=yes
usecallerid=yes
callerid=asreceived
cidsignalling=v23
cidstart=usehist
hidecallerid=no
callwaiting=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=yes
progzone=fr
rxgain=5.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no
faxdetect=both
signalling=fxs_ks
channel => 4

;
; Default language
;
language=fr
;
; Default context
;
context=incoming


CLI> dahdi show channel 4
Channel: 4
File Descriptor: 16
Span: 1
Extension:
Dialing: no
Context: default
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: yes
Busy Count: 3
Busy Pattern: 0,0
TDD: no
Relax DTMF: no
Dialing/CallwaitCAS: 0/0
Default law: ulaw
Fax Handled: no
Pulse phone: no
DND: no
Echo Cancellation:
128 taps
currently OFF
Wait for dialtone: 0ms
Actual Confinfo: Num/0, Mode/0x0000
Actual Confmute: No
Hookstate (FXS only): Onhook

As usual I end up replying to myself.

Everything seems to work. I’ve also reinstalled the G729 codec from Digium which I had installed on 1.4.
The dahdi show status and show version CLI commands still don’t give the correct answers but that doesn’t seem to stop dahdi from working.

The echo canceller seems to work.

My main “problem” is that I seem to be obliged to use “default” as the context for calls on DAHDI although I’ve set the value to “incoming” in the config files.

As a workaround I have changed my incoming context in extensions.conf to default but This seems to be an error.

More news if I find anything else. I can’t say the migration was easy but it seems to have been succesfull. I hope I’ll get some value from it.

BTW: I couldn’t even start Ubuntu Lucid with the TDM400P installed but that bug is posted elsewhere so for the moment I’m running Ubuntu Karmic.