dear all,
how to create a dahdi extension
There is not a simple answer to your question. I recommend looking through Asterisk: The Definitive Guide.
I will show my confugurations .But still my phone is not ringing
chan_dahdi.cof
[general]
[channels]
#include dahdi-channels.conf
;;[901]
usecallerid=yes
cidsignalling=dtmf
cidstart=dtmf
hidecallerid=no
callwaiting=yes
threewaycalling=yes
transfer=yes
echocancel=yes
echocancelwhenbridged=yes
rxgain=0.0
txgain=0.0
busydetect=yes
busycount=3
immediate=yes
rxwink=300
INPUT_USER=300
faxdetect=OFF
musiconhold=default
switchtype=national
;FXS Modules
group=0
signalling=fxs_ks
context=from-internal
channel=1-3
;FXO Modules
group=5
echocancel=yes
signalling=fxo_ks
channel=4
mailbox=200@device
immediate=no
echotraining=800
echocancelwhenbridged=no
echocancel=yes
context=internal
callprogress=no
callgroup=
callerid=TRan <200>
busydetect=no
busycount=7
accountcode=
channel=>4
Zap2dahdicompat=yes
I could be wrong, as I don’t use dahdi lines, but I believe that FX* on cards refers to what is connected at the other end, whereas fx* on signalling refers to the signalling type of the near end.
In any case, General forums are not intended for questions (except rhetorical ones) and questions like this are best addressed to the card vendor.
If you are using a Digium card you need to read this viewtopic.php?f=1&t=81808
if not contact your card vendor. Remember that we cant guess your system, please next time try to provide more details that could be critical for a successful configuration. Like Asterisk and DAHDI version, The exact card Model.
Remember the signalling type to use with your interface is the only mandatory setting. You must set a signalling type before allocating a channel. If you are connecting analog telephone equipment, note that analog phone signalling can be a source of some confusion. FXS channels are signalled with FXO signalling, and vice versa. Asterisk ‘talks’ to internal devices as the opposite side. An FXO interface card is signalled with FXS signalling by Asterisk, and should be configured as such.
That’s what I suspected, and what is wrong in this case.