[asterisk-bugs] [JIRA] Commented: (ASTERISK-16468) [patch] DTMF CallerID failing wirh dtmfcidlevel with high value

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-16468:
--------------------------------------------

The part of the first patch [^1.6.2.13 DTMF CallerID.patch] to add CID_START_DTMF_NOALERT is a new feature no matter how you consider it.  That patch must be made for trunk.

The second patch [^1.6.2-DTMF-per-channel.patch] which just makes dtmfcidlevel per channel could be considered a bug fix or a new feature depending upon how you view it.  I think it is more a new feature than a bug though since it changes the behavior of an existing option.  It would also be best to make it for trunk.

Thanks

> [patch] DTMF CallerID failing wirh dtmfcidlevel with high value
> ---------------------------------------------------------------
>
>                 Key: ASTERISK-16468
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-16468
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Channels/chan_dahdi
>            Reporter: scgm11
>         Attachments: 1.6.2.13 DTMF CallerID.patch, 1.6.2-DTMF-per-channel.patch
>
>
> After some time working ok this message start to show up on the console:
> WARNING[7309]: chan_dahdi.c:9831 do_monitor: Read failed with -1: Unknown error 500
> after this calls starts to hangup at the middle of a call.
> Configuration:
> cidsignalling=dtmf
> dtmfcidlevel=1250
> cidstart=dtmf
> answeronpolarityswitch=yes
> hanguponpolarityswitch=yes
> polarityonanswerdelay=2000

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira