[asterisk-bugs] [JIRA] (ASTERISK-25639) app_amd system maxwords discrepency

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-25639:
------------------------------------------

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.

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].

> app_amd system maxwords discrepency
> -----------------------------------
>
>                 Key: ASTERISK-25639
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25639
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_amd
>    Affects Versions: 11.20.0
>            Reporter: Dade Brandon
>            Severity: Trivial
>
> app_amd documents "maximumNumberOfWords" (runtime parameter) as well as maximum_number_of_words in amd.conf.sample as "Maximum number of words in the greeting.  If exceeded then MACHINE."
> However, if this variable is set to 3, then app_amd returns as 'MACHINE' as soon as the third word begins.
> Based on the description of the variable, it should not return 'MACHINE' unless a fourth word is said.
> Considering how long app_amd has been around, I think a change to the documentation would be best, ie "If *reached*, then MACHINE" rather than "If exceeded, then MACHINE".  
> I've marked the severity as low solely because anybody using this system must already be dealing with the mentioned issue, it's not like fixing this in the documentation will do anything to improve or worsen their AMD detection.   Fixing this by making the fields match the currently documented functionality would be a bigger issue than this is itself.  Therefore this really just affects new users, or people with un-tweaked AMD settings who are trying to tweak their AMD settings.



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