[asterisk-bugs] [JIRA] (ASTERISK-29009) app_amd: Detection issues when silence is not transmitted

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-29009:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

> app_amd: Detection issues when silence is not transmitted
> ---------------------------------------------------------
>
>                 Key: ASTERISK-29009
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29009
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_amd
>    Affects Versions: 13.30.0
>            Reporter: Corey Farrell
>            Severity: Minor
>
> I've run into an issue when retesting an integration which uses {{AMD()}} when using 13.35.0.  Reverting the change from ASTERISK-28608 fixes my tests.  The issue occurs when I run AMD on a call to the following dialplan:
> {code}
> exten => s,1,Answer()
> same => n,Wait(0.5)
> ; Play hello.ulaw from asterisk-core-sounds-en-ulaw-1.6.tar.gz
> same => n,Playback(hello)
> same => n,Wait(5)
> same => n,HangUp()
> {code}
> My tests run PJSIP to PJSIP between two Asterisk PBX instances, one instance runs {{AMD()}} on an outbound call, the other instance simulates a human answering with the above context. Specifically the issue is that {{Wait(number)}} does not normally transmit silence.  In Asterisk 13.28.0 {{AMD()}} would detect a call to this context as "HUMAN" but in 13.30.0 it is detected as "NOTSURE".
> Setting {{transmit_silence=yes}} in the asterisk.conf of my daemon also fixed the tests, so I assume this is related to {{AST_FRAME_NULL}} handling.
> I know this module is extended support, I will eventually be able to dig deeper and hopefully create a patch but for now I just wanted to get the report open to document my findings.



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