[asterisk-bugs] [JIRA] (ASTERISK-25398) chan_iax2 call failed to authenticate

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-25398:
------------------------------------------

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

> chan_iax2 call failed to authenticate
> -------------------------------------
>
>                 Key: ASTERISK-25398
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25398
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2, Resources/res_config_odbc
>    Affects Versions: 13.5.0
>         Environment: Debian Wheezy
> PostgreSQL 9.1+134wheezy
> Asterisk 13.5.0
> ODBC used for database connection
>            Reporter: Stefan Tichy
>
> Asterisk 13.5.0 has one IAX friend configured (output from "iax2 show peer" see attachement)
> some Asterisk 11.18.0 registers
> Scenario A: Static configuration used for iax2 friend: no problems
> Scenario B: realtime configuration used for iax2 friend
> Registration still works but no calls to the Asterisk 13.5.0 are possible.
> chan_iax2.c:11213 socket_process_helper:
> Host 10.11.12.13:4569 failed to authenticate as 8357f2b5085552ecdda65b04
> Asterisk 13.5 does not even evaluate the response. It just had send a fake authentication request.
> It does not matter if rtcachefriends is set to yes or no.



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