[asterisk-bugs] [JIRA] (ASTERISK-27033) chan_dahdi is unable to detect dialtone

[Richard Mudgett (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237317#comment-237317 ] 

Richard Mudgett edited comment on ASTERISK-27033 at 6/6/17 10:51 AM:
---------------------------------------------------------------------

{noformat}
; On trunk interfaces (FXS) it can be useful to attempt to follow the progress
; of a call through RINGING, BUSY, and ANSWERING.   If turned on, call
; progress attempts to determine answer, busy, and ringing on phone lines.
; This feature is HIGHLY EXPERIMENTAL and can easily detect false answers,
; so don't count on it being very accurate.
;
; Few zones are supported at the time of this writing, but may be selected
; with "progzone".
;
; progzone also affects the pattern used for buzydetect (unless
; busypattern is set explicitly). The possible values are:
;   us (default)
;   ca (alias for 'us')
;   cr (Costa Rica)
;   br (Brazil, alias for 'cr')
;   uk
;
; This feature can also easily detect false hangups. The symptoms of this is
; being disconnected in the middle of a call for no reason.
;
;callprogress=yes
;progzone=uk
{noformat}

The {{progzone}} option affects dialtone detection in chan_dahdi.  The only supported country that has a 425 Hz detection is Costa Rica and that is the only tone enabled for that country.  According to a quick lookup, Poland only uses a 425 Hz tone for its signaling so the Costa Rica setting should work.


was (Author: rmudgett):
{noformat}
; On trunk interfaces (FXS) it can be useful to attempt to follow the progress
; of a call through RINGING, BUSY, and ANSWERING.   If turned on, call
; progress attempts to determine answer, busy, and ringing on phone lines.
; This feature is HIGHLY EXPERIMENTAL and can easily detect false answers,
; so don't count on it being very accurate.
;
; Few zones are supported at the time of this writing, but may be selected
; with "progzone".
;
; progzone also affects the pattern used for buzydetect (unless
; busypattern is set explicitly). The possible values are:
;   us (default)
;   ca (alias for 'us')
;   cr (Costa Rica)
;   br (Brazil, alias for 'cr')
;   uk
;
; This feature can also easily detect false hangups. The symptoms of this is
; being disconnected in the middle of a call for no reason.
;
;callprogress=yes
;progzone=uk
{noformat}

The {{progzone}} option affects dialtone detection in chan_dahdi.  The only supported country that has a 425 Hz detection is Costa Rica and that is the only tone enabled for that country.  According to a quick lookup, Poland only uses a 425 Hz for its signaling so the Costa Rica setting should work.

> chan_dahdi is unable to detect dialtone
> ---------------------------------------
>
>                 Key: ASTERISK-27033
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27033
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_dahdi
>    Affects Versions: 13.15.0
>         Environment: Linux Debian jessie 64 bits, Wildcard TDM410P PCI card with 1 FXO
>            Reporter: Henry Moffett
>            Severity: Minor
>
> Recently I bought Wildcard TDM410P PCI card with 1 FXO port in order to make and receive calls on PSTN analog line.
> I've been playing with it for few days, and I've noticed that two options in chan_dahdi.conf: dialtone_detect and waitfordialtone don't detect the dialtone at all. At least not the 425 Hz.
> If I set waitfordialtone, I cannot make an outgoing call.
> I'm using "loadzone=pl" in /etc/dahdi/system.conf, and "options wctdm24xxp opermode=POLAND" in /etc/modprobe.d/dahdi.conf.



--
This message was sent by Atlassian JIRA
(v6.2#6252)