OverviewAsterisk 13 is the next Long Term Support (LTS) release of Asterisk. As such, the focus of development for this release of Asterisk was on improving the usability and features developed in the previous Standard release, Asterisk 12. Beyond a general refinement of end user features, development focussed heavily on the Asterisk APIs - the Asterisk Manager Interface (AMI) and the Asterisk REST Interface (ARI) - and the PJSIP stack in Asterisk. Some highlights of the new features include: - Asterisk security events are now provided via AMI, allowing end users to monitor their Asterisk system in real time for security related issues.
- External control of Message Waiting Indicators (MWI) through both AMI and ARI.
- Reception/transmission of out of call text messages using any supported channel driver/protocol stack through ARI.
- Resource List Server support in the PJSIP stack, providing subscriptions to lists of resources and batched delivery of
NOTIFY requests. - Inter-Asterisk distributed device state and mailbox state using the PJSIP stack.
And much more! It is important to note that Asterisk 13 is built on the architecture developed during the previous Standard release, Asterisk 12. Users upgrading to Asterisk 13 should read about the new features documented in New in 12, as well as the notes on upgrading to Asterisk 12. In particular, users upgrading to Asterisk 13 from a release prior to Asterisk 12 should read the specifications on AMI, CDRs, and CEL, as these also apply to Asterisk 13: Finally, all users upgrading to Asterisk 13 should read the notes on upgrading to Asterisk 13. | Tip |
|---|
| title | Asterisk 12 was different |
|---|
| Some of the new features listed below were released in point releases of Asterisk 12. Per the Software Configuration Management Policies laid out for Asterisk 12, new features were periodically merged and released in that branch of Asterisk. This was done to help users of Asterisk migrating to the new platform develop features in preparation for Asterisk 13. While some of the features listed below were released under an Asterisk 12 release, they are all listed here as "new in 13", for two reasons: - If you are upgrading from a previous LTS release (such as Asterisk 11), all of these features are new.
- If you are upgrading from some version of Asterisk 12, some of the previously released features may be new (as they may not have been in your version of Asterisk 12).
|
Applications- The application will now return a new
AGENT_STATUS value of NOT_CONNECTED if the agent fails to connect with an incoming caller after being alerted to the presence of the incoming caller. The most likely reason this would happen is the agent did not acknowledge the call in time.
- ChanSpy now accepts a channel uniqueid or a fully specified channel name as the
chanprefix parameter if the 'u' option is specified.
The ConfBridge dialplan application now sets a channel variable, CONFBRIGE_RESULT, upon exiting. This variable can be used to determine how a channel exited the conference. Valid values upon exiting are: | Value | Reason |
|---|
FAILED | The channel encountered an error and could not enter the conference. | HANGUP | The channel exited the conference by hanging up. | KICKED | The channel was kicked from the conference. | ENDMARKED | The channel left the conference as a result of the last marked user leaving. | DTMF | The channel pressed a DTMF sequence to exit the conference. |
- Added conference user option
'announce_join_leave_review'. This option implies 'announce_join_leave' with the added effect that the user will be asked if they want to confirm or re-record the recording of their name when entering the conference.
- The module
app_dahdibarge was deprecated and has been removed. Users of DAHDIBarge should use ChanSpy instead.
|