The Asterisk Development Team is pleased to announce the second beta release of Asterisk 13.0.0. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/releases
All interested users of Asterisk are encouraged to participate in the Asterisk 13 testing process. Please report any issues found to the issue tracker, https://issues.asterisk.org/jira. All Asterisk users are invited to participate in the #asterisk-bugs channel to help communicate issues found to the Asterisk developers. It is also very useful to see successful test reports. Please post those to the asterisk-dev mailing list (http://lists.digium.com). Asterisk 13 is the next major release series of Asterisk. It will be a Long Term Support (LTS) release, similar to Asterisk 11.
For more information about support time lines for Asterisk releases, see the Asterisk versions page:
For important information regarding upgrading to Asterisk 13, please see the Asterisk wiki:
A short list of new features includes:
- Asterisk security events are now provided via AMI, allowing end users to monitor their Asterisk system in real time for security related issues.
- Both AMI and ARI now allow external systems to control the state of a mailbox. Using AMI actions or ARI resources, external systems can programmatically trigger Message Waiting Indicators (MWI) on subscribed phones. This is of particular use to those who want to build their own VoiceMail application using ARI.
- ARI now supports the reception/transmission of out of call text messages using any supported channel driver/protocol stack through ARI. Users receive out of call text messages as JSON events over the ARI websocket connection, and can send out of call text messages using HTTP requests.
- The PJSIP stack now supports RFC 4662 Resource Lists, allowing Asterisk to act as a Resource List Server. This includes defining lists of presence state, mailbox state, or lists of presence state/mailbox state; managing subscriptions to lists; and batched delivery of NOTIFY requests to subscribers.
- The PJSIP stack can now be used as a means of distributing device state or mailbox state via PUBLISH requests to other Asterisk instances. This is analogous to Asterisk’s clustering support using XMPP or Corosync; unlike existing clustering mechanisms, using the PJSIP stack to perform the distribution of state does not rely on another daemon or server to perform the work.
And much more!
More information about the new features can be found on the Asterisk wiki:
A full list of all new features can also be found in the CHANGES file:
For a full list of changes in the current release, please see the ChangeLog:
Thank you for your continued support of Asterisk!