Besoin d'aide pour configurer dahdi

[charly]

Bonjour,

J'aurais besoin d'un coup de main pour configurer les fichiers:
- dahdi-channels.conf
- chan_dahdi.conf

J'utilise:
Trixbox 2.0.8.04
DAHDI Tools : 2.3.0-1_trixbox
DAHDI_linux: 2.3.0.1-1_trixbox

j'ai une carte digium tdm400p.

La commande dahdi show channels m'affiche
-bash: dahdi: command not found


La commande dahdi_cfg -vv m'affiche:

DAHDI Version: 2.3.0.1
Echo Canceller(s):
Configuration
======================


Channel map:

Channel 01: FXS Kewlstart (Default) (Echo Canceler: none) (Slaves: 01)
Channel 02: FXO Kewlstart (Default) (Echo Canceler: none) (Slaves: 02)

2 channels to configure.

Setting echocan for channel 1 to none
Setting echocan for channel 2 to none

Merci pour votre aide.

[ffossard]

Je déplace le sujet dans la catégorie configuration/support, puisqu'il s'agit de configurer un dahdi qui est déjà installé.

"dahdi show channels" est une commande de la CLI Asterisk, pas une commande linux.
Tape ceci pour ouvrir la CLI:

asterisk -vvvvvvvr
Tu devrai se retrouver dans la CLI et pouvoir taper la commande:

CLI> core show channels

Tu semble avoir une tdm11b, tu peux regarder sa configuration dans /etc/dahdi/system.conf, c'est ce qui corresponds à la sortie de la commande "dahdi_cfg -vv" :wink:

Quel est le contenu actuel de dahdi-channels.conf et chan_dahdi.conf ?

[charly]

voici la conf des fichiers et merci pour ta réponse

fichier dadhi_channel.conf :
; Autogenerated by /usr/sbin/dahdi_genconf on Wed Dec 15 07:51:46 2010
; If you edit this file and execute /usr/sbin/dahdi_genconf again,
; your manual changes will be LOST.
; Dahdi Channels Configurations (chan_dahdi.conf)
;
; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended
; to be #include-d by /etc/chan_dahdi.conf that will include the global settings
;

fichier chan_dahdi.conf :
;
; DAHDI telephony
;
; 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

usecallerid=yes

[cedricscha]

t'as déjà essyé un :


dahdi_genconf

[charly]

J'avoue être un peu beaucoup perdu.:cry:
voilà le
fichier /etc/dahdi/genconf.parameters:

# 'yes' - forces BRI cards to use 'hardhdlc' signalling.
# 'no' - forces BRI cards to use 'dchan' (an alias for 'fcshdlc').
# It is usefull only for dahdi with the bristuff patch.
#
# If it is left out or set to 'auto':
# * Information supplied by the driver is used to decide:
# - Currently implemented for Astribanks.
# - Taken from /sys/bus/xpds/drivers/bri/dchan_hardhdlc.
# * Without this info, falls back to 'hardhdlc'.
#bri_hardhdlc auto

# For MFC/R2 Support: 'R2' will make E1 spans CAS and with the
# 'r2_idle_bits' bit in system.conf . It will also make dahdi_genconf default
# to generating the channels of this card in unicall.conf rather than in
# chan_dahdi.conf . The meaning of this may be extended somehow to support
# R2 through openr2/chan_dahdi later on.
#pri_connection_type R2
#pri_connection_type CAS
#
# Explicitly set the idle bits for E1 CAS (Sample value is the default):
#r2_idle_bits 1101
#
# Set T1 framing type to d4 instead of esf:
#tdm_framing d4
#
# Use E&M on CAS (default is FXS/FXO). If set, E1 spans will be used as
# E&M-E1 and T1 will use the requested type:
#em_signalling em
#em_signalling em_w
#em_signalling featd
#em_signalling featdtmf
#em_signalling featdtmf_ta
#em_signalling featb
#em_signalling fgccama
#em_signalling fgccamamf
#
# pri_termtype contains a list of settings:
# Currently the only setting is for TE or NT (the default is TE). This
# sets two different but normally related configuration items:
#
# A TE span will have *_cpe signalling in Asterisk and will also get
# timing from the remote party.
#
# A NT span will have *_new signalling in Asterisk and will provide
# timing to the remote party.
#
# pri_termtype is a list if span specs and configuration (TE/NT) for
# them. The first spec that matches is used. The matching is of perl
# regular expressions, but with '*' and '?' have their meaning from
# basic regular expressions.
#pri_termtype
# SPAN/2 NT
# SPAN/4 NT
#
#pri_termtype
# SPAN/* NT
#