| Summary: | ASTERISK-25398: chan_iax2 call failed to authenticate | ||
| Reporter: | Stefan Tichy (st) | Labels: | |
| Date Opened: | 2015-09-17 11:52:32 | Date Closed: | 2015-09-18 11:14:48 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_iax2 Resources/res_config_odbc |
| Versions: | 13.5.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Debian Wheezy PostgreSQL 9.1+134wheezy Asterisk 13.5.0 ODBC used for database connection | Attachments: | ( 0) iax2_show_peer.txt |
| Description: | 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. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2015-09-17 11:52:33.513-0500 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]. By: Stefan Tichy (st) 2015-09-17 11:53:54.960-0500 iax2 show peer By: Stefan Tichy (st) 2015-09-18 11:14:48.757-0500 At least no Asterisk Bug. It was caused by a typo. Sorry. | ||