Hi,
I am working on a simple telephonic solution that involve us creating a callout file from our system that will be then move to the Asterisk’s spool directory with the channel as DAHDI/3/123456789. We have a context in our dialplan that is dedicated for the call.
Hence when a call is setup for the DAHDI/3/123456789, our dialplan is executed with the context as per callout file.
However the problem is that, the dialplan starts right after Asterisk pick up the call file from the spool before even the phone (with number 123456789) rings.
My /etc/asterisk/chan_dahdi.conf file is
[trunkgroups]
[channels]
usecallerid=yes
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
group=1
callgroup=1
pickupgroup=1
usecallerid = yes
hidecallerid = no
callwaiting = yes
threewaycalling = yes
transfer = yes
echocancel = yes
echocancelwhenbridged = yes
rxgain = 0.0
txgain = 0.0
; FXS Modules
group = 1
signalling = fxo_ks
context = Internal_Phone
channel = 1-2
; FXO Modules
group = 2
echocancel = yes
signalling = fxs_ks
callerid = "HipLink Test" <4209211>
context = Internal_PSTN
waitfordialtone=yes
immediate=no
;busydetect = yes
;busycount = 10
;ringtimeout=8000
pulsedial=yes
channel = 3-4Also I am deploying this solution in Pakistan, and there is no tone zone/profile define in the DAHDI tools/zonedata.c file. So I have created one as listed below
{
.zone = 46,
.country = "pk",
.description = "Pakistan",
//.ringcadence = { 400, 200, 400, 2000 },
.ringcadence = { 2000, 4000 },
.tones = {
/* Reference: http://www.itu.int/ITU-T/inr/forms/files/tones-0203.pdf */
{ DAHDI_TONE_DIALTONE, "450" },
{ DAHDI_TONE_BUSY, "400/500,0/500" },
{ DAHDI_TONE_RINGTONE, "400/1000,0/2000" },
{ DAHDI_TONE_CONGESTION, "400/250,0/250" },
/* CALLWAIT - not specified */
{ DAHDI_TONE_CALLWAIT, "400/200,0/100,400/200,0/7500" },
/* DIALRECALL - not specified */
{ DAHDI_TONE_DIALRECALL, "!350+440/100,!0/100,!350+440/100,!0/100,!350+440/100,!0/100,350+440" },
/* RECORDTONE - not specified */
{ DAHDI_TONE_RECORDTONE, "1400/500,0/15000" },
/* INFO - not specified */
{ DAHDI_TONE_INFO, "!950/330,!1400/330,!1800/330,0/1000" },
/* STUTTER - not specified */
{ DAHDI_TONE_STUTTER, "!350+440/100,!0/100,!350+440/100,!0/100,!350+440/100,!0/100,!350+440/100,!0/100,!350+440/100,!0/100,!350+440/100,!0/100,350+440" },
},
.dtmf_high_level = -10,
.dtmf_low_level = -8,
.mfr1_level = -10,
.mfr2_level = -8,
},I have recompile the DAHDI driver, tools, and install the modified one. And I have use the “pk” as the value of loadzone and defaultzone. And after starting the DAHDI, the issue remains as before.
The tone profile above is not complete, and the ringcadence value is again taken from the US profile.
So my question is, the issue that I am having is due to the incomplete or incorrect tone profile? Or there is some thing missing in my configuration? Or for DAHDI calls, there is something extra that needs to be done in the dialplan? The dialplan is running fine with SIP calls.
Kindly help me out.
Thanks.