Asterisk upgrade breaks IAX extensions

If you have upgraded your version of Asterisk and find that your IAX2 extensions no longer work then the cause could be a change to the IAX protocol. This was made to resolve a security issue that could result in a denial of service attack.

You will see this error in the Asterisk log file if you are suffering from this issue -

chan_iax2.c: Call rejected, CallToken Support required.

If you use FreePBX then Asterisk can be made to function the same as before by adding the following 2 lines to /etc/asterisk/iax_general_custom.conf -

calltokenoptional = 0.0.0.0/0.0.0.0
maxcallnumbers = 16382

You will also need to do a -

 iax2 reload

or restart Asterisk for the changes to take effect.

More information about the reason for this change and the implications for disabling call token checking can be found here –
http://svn.digium.com/svn/asterisk/branches/1.6.0/doc/IAX2-security.pdf




Related posts:

  1. Integrating FreePBX with A2Billing
  2. Asterisk/FreePBX dial plan injection vulnerability
  3. FBI / IC3 issue warning for Asterisk users


One Comment

  1. Frode:

    When implementing the workaround as mentioned above, and in the original Digium document, connections to external IAX trunks (such as Les.net) stop working. In addition, an internal S100-FX IAX analog converter is still unable to connect to * after this change has been performed.

Leave a comment