The following is a complete list of changes made between iSymphony 3.1.3 and iSymphony 3.2 alpha 2. If you are upgrading from iSymphony 3.0.x, please see the changelog for iSymphony 3.1.3 as well.

Features

• Added Support Asterisk 12 and 13
  • Added support for the new channel bridging mechanism used by Asterisk 12 and 13.
  • Added support for the new DialEnd and DialBegin AMI events.
  • Added support for the new ConfBridgeMute AMI event.
  • Added support for the new MusicOnHoldStart and MusicOnHoldStop AMI events.
  • Added support for the new QueueCallerJoin, QueueCallerLeave, and QueueMemberPause AMI events.
  • Added support for new properties in various other AMI actions and events.
• Added support for the PJSIP channel driver
  • Users can now see the registration status of PJSIP endpoints.
  • Users can now see and control calls based on PJSIP channels.
  • Users can now toggle DND for a PJSIP endpoint.

Performance Improvements

• Performance of loading state from the Asterisk server, on startup or reload, has been slightly improved.

Resolved Bugs

• Resolved an issue where only one device state id would be processed when handling an ExtensionStatus event.

Regressions

• Due to the new method of setting SIP headers for PJSIP endpoints, iSymphony will no longer auto answer any calls that are stolen from another extension, or transferred from a parking lot, if the destination of the call is a PJSIP endpoint. Auto answer, in these situations, will still fiction as before, if the endpoint is managed by the chan SIP driver. Auto answer, on origination from a PJSIP endpoint, will function correctly.