Last modified by superadmin on 2021/09/09 20:55
Show last authors
1 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>>doc:iSymphony 3\.5 Documentation.iSymphony Releases.Production Releases.iSymphony 3\.1 Release Notes.iSymphony 3\.1\.3 Change Log.WebHome]] as well.
2
3 === Features ===
4
5 * Added Support Asterisk 12 and 13
6 ** Added support for the new channel bridging mechanism used by Asterisk 12 and 13.
7 ** Added support for the new DialEnd and DialBegin AMI events.
8 ** Added support for the new ConfBridgeMute AMI event.
9 ** Added support for the new MusicOnHoldStart and MusicOnHoldStop AMI events.
10 ** Added support for the new QueueCallerJoin, QueueCallerLeave, and QueueMemberPause AMI events.
11 ** Added support for new properties in various other AMI actions and events.
12 * Added support for the PJSIP channel driver
13 ** Users can now see the registration status of PJSIP endpoints.
14 ** Users can now see and control calls based on PJSIP channels.
15 ** Users can now toggle DND for a PJSIP endpoint.
16
17 === Performance Improvements ===
18
19 * Performance of loading state from the Asterisk server, on startup or reload, has been slightly improved.
20
21 === Resolved Bugs ===
22
23 * Resolved an issue where only one device state id would be processed when handling an ExtensionStatus event.
24
25 === Regressions ===
26
27 * 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.

Search

Navigation

iSymphony