Asterisk IAX error No Authority Found

This error is usually caused by a username/secret/type mismatch.

This error also occurs when the context requested in the incoming call is different from one in the section of incoming peer. Multiple contexts in the peer section can be defined.

Valid Example Configs

Below is an example of working IAX trunk configuration between two Asterisk servers.

Basic Server Transactions

Below is basic call transaction from server1 to server2:

server1 connects to server2
server1 sends username: server2
server1 send secret: 1234
server2 looks for iax entry [username] e.g. [server2]
server2 checks secret
server2 accepts connection

This is outlined in more detail in Asterisk IAX authentication

Explanation

The ‘No authority found’ error is generated when an iax entry [example] matching the username sent can not be found.
It will also occur if the secret is wrong.

Example Error

Rx-Frame Retry[ No] — OSeqno: 000 ISeqno: 000 Type: IAX Subclass: NEW
Timestamp: 00002ms SCall: 16385 DCall: 00000 [111.111.111.111:4569]
VERSION : 2
CALLED NUMBER : 12345678
CODEC_PREFS : (g729)
CALLING NUMBER : 87654321
CALLING PRESNTN : 0
CALLING TYPEOFN : 0
CALLING TRANSIT : 0
CALLING NAME : 87654321
LANGUAGE : en
CALLED CONTEXT : example_context
USERNAME : example_username
FORMAT : 256
CAPABILITY : 63744
ADSICPE : 2
DATE TIME : 2007-06-20 16:02:58

[Jun 20 16:02:58] NOTICE[6301]: chan_iax2.c:6780 socket_process: Rejected connect attempt from 111.111.111.111, who was trying to reach ‘12345678@example_context’
Tx-Frame Retry[-01] — OSeqno: 000 ISeqno: 001 Type: IAX Subclass: ACK
Timestamp: 00002ms SCall: 00005 DCall: 16385 [111.111.111.111:4569]
Tx-Frame Retry[000] — OSeqno: 000 ISeqno: 001 Type: IAX Subclass: REJECT
Timestamp: 00008ms SCall: 00005 DCall: 16385 [111.111.111.111:4569]
CAUSE : No authority found
CAUSE CODE : 50

Rx-Frame Retry[ No] — OSeqno: 001 ISeqno: 001 Type: IAX Subclass: ACK
Timestamp: 00008ms SCall: 16385 DCall: 00005 [111.111.111.111:4569]