[asterisk-bugs] [JIRA] (ASTERISK-20688) IAX2 authdebug=no suppresses Logger/CLI Notice messages of failed authorization attempts (invalid user, bad password)

[Michael L. Young (JIRA)]

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

Michael L. Young commented on ASTERISK-20688:
---------------------------------------------

Features requests are no longer submitted to or accepted through the issue tracker. Features requests are openly discussed on the mailing lists [1] and Asterisk IRC channels and made note of by Bug Marshals.

[1] http://www.asterisk.org/support/mailing-lists

In taking a quick peak at the code, the behavior that you are noticing has been there for a while and it appears to be working as it was programmed for.
                
> IAX2 authdebug=no suppresses Logger/CLI Notice messages of failed authorization attempts (invalid user, bad password)
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20688
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20688
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: 1.8.18.0
>         Environment: CentOS 64-Bit 5.x
>            Reporter: Ian Anderson
>            Severity: Minor
>
> Having authdebug=no suppresses any NOTICE messages regarding an IAX2 authentication failure... ie. bad password, user not existing, IP not matching permit/deny masks.
> It should only stop IAX2 auth information when doing IAX2 debugging and not logging NOTICEs to CLI and/or log file.
> I was not receiving any notices in CLI when I tried to register with a bad password.  Subsequent testing revealed I could only get the NOTICEs to show was by using authdebug=yes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira