I have just finished upgrading my * box after 790 days of uptime!! - yeah - set it and forget it.
Needed to shift the box so took the opportunity to upgrade from 1.4 and zaptel to :-
1.6.2.7 via asterisk.com rpm onto new CentOS 5.5 with dahdi-linux-complete-2.3.0 with my original rhino R4FXO-EC card.
All works well - can make SIP to SIP calls, receive incoming calls from the PSTN lines via the rhino card to SIP, and if I use
Dial(Dahdi/1/407XXXXXXX) outgoing calls work also.
However, that only seems to select the first trunk in group 1 i.e. no trunk selection.
If I use Dahdi/r1 or g1 or R1 or G1 the calls fail.
What am I missing?
Posted on Asterisk guru but it seems to be dead group with little to no support.
Asterisk CLI gives:
– Executing [4073413815@intern:1] Dial(“SIP/6342-00000023”, “DAHDI/r1/4073413815”) in new stack
[Jun 2 21:50:19] WARNING[10394]: app_dial.c:1747 dial_exec_full: Unable to create channel of type ‘DAHDI’ (cause 0 - Unknown)
== Everyone is busy/congested at this time (1:0/0/1)
– Auto fallthrough, channel ‘SIP/6342-00000023’ status is 'CHANUNAVAIL’
Any pointers appreciated.
TIA
You need to put your channels into groups.
Specifying DAHDI/1 says to use channel 1 of DAHDI.
In your dahdi-channels.conf use the group= line to designate channels within a group.
Then when you do a dial and try to use DAHDI/g1 for instance, it will use the range of channels you have specified in that group.
I have one PRI with only 8 channels and called it group 88
[quote]; Span 1: TE2/0/1 “T2XXP (PCI) Card 0 Span 1” (MASTER)
group=88
context=from-pstn-fax
switchtype = national
signalling = pri_cpe
channel => 1-8
[/quote]
From asterisk issuing a DAHDI SHOW CHANNELS GROUP 88 shows:
Solved - I had all the lines needed in chan_dahdi.conf but I had them in the wrong order!!
I had just worked my way through the example .conf and removed comments and made edits at the locations where each parameter is explained.
i.e the group is explained below the signaling and channel lines thus I had them out of order.
Many thanks for the example - once I did a grep -v ; chan_dahdi.conf and saw them out of order it was obvious.
Hope this helps others.
I did have:
[trunkgroups]
[channels]
context=from-pstn
signalling=fxs_ks
channel => 1,2
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
rxgain=2.0
txgain=3.0
group=1
callgroup=1
pickupgroup=1
immediate=no
callerid = asreceived
busydetect=yes
busycount=6
callprogress=yes
progzone=us
tonezone = 0
ringtimeout=8000
faxdetect=both
faxbuffers=>6,full
and now have:
[channels]
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
rxgain=2.0
txgain=3.0
group=1
context=from-pstn
signalling=fxs_ks
channel => 1,2
callgroup=1
pickupgroup=1
immediate=no
callerid = asreceived
busydetect=yes
busycount=6
callprogress=yes
progzone=us
tonezone = 0
ringtimeout=8000
faxdetect=both
faxbuffers=>6,full