Wiki source code of iSymphony 3.3.0 Change Log
Last modified by ryanp on 2021/09/09 20:56
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
| |
1.1 | 1 | The following is a complete list of changes made between iSymphony 3.2.2 to iSymphony 3.3. |
| 2 | |||
| 3 | {{note}} | ||
| |
3.1 | 4 | If you are upgrading from iSymphony 3.2.x, please see the change log for [[iSymphony 3.2.2>>doc:iSymphony 3\.2\.2 Change Log]] as well. |
| |
1.1 | 5 | {{/note}} |
| 6 | |||
| 7 | === Features === | ||
| 8 | |||
| 9 | * ((( | ||
| 10 | Added List View to the User Widget. | ||
| 11 | ))) | ||
| 12 | * Added an interface to global configuration page in the Administrator that allows super admins to create support packages. | ||
| 13 | * Added an interface to bind recording extensions to a user in Administrator - these extensions will allow a user to listen to recordings of extensions that are not bound to the user. | ||
| 14 | * Added a desktop client application that can be downloaded and installed from the client user menu "Desktop Client" option. The client supports native OS features. Added a Desktop Client tab in the Administrator that allows setting a configurable list of iSymphony server IPs and application popup configurations. | ||
| 15 | |||
| 16 | === Resolved Bugs === | ||
| 17 | |||
| 18 | * Resolved an issue where multiple channel dial events in Asterisk version 13 would cause calls to get stuck in the queue widget. | ||
| 19 | * Resolved an issue where a user attempts to pick up a parked call by double clicking the call in the Parking Lot Widget and an exception is thrown. | ||
| 20 | * Resolved an issue where changing the recording mask without restarting the service could cause recordings to display incorrectly or not at all. | ||
| 21 | * Resolved an issue where changing the default extension of a user in iSymphony Admin could cause duplicate buttons to be created in the User Widget. | ||
| 22 | * Resolved an issue where "+" could not be used in dialed or transfered number strings, causing issues with international calls. | ||
| 23 | * Resolved a memory leak in cases where a user spends a long period of time on a client dashboard with a queue widget attached. | ||
| 24 | * Resolved an issue where multiple PBX connections with a blank recording agent set would cause errors. | ||
| 25 | * Resolved an issue where desktop notifications did not appear in the correct place on multi-monitor systems. | ||
| 26 | * Resolved an issue where a bad client login attempt when multiple cores are setup would throw an exception. | ||
| 27 | * Resolved an issue where creating dynamic conference rooms using the app_ConfBridge would fail. | ||
| 28 | * Resolved an issue where placing a call on hold in Asterisk version 13 would cause the call to disappear from the MyStream widget. | ||
| 29 | * Resolved an issue where attended transfers performed in the panel would prevent a call history entry from being logged, specifying the who called the user that transferred the call. | ||
| 30 | * Resolved an issue where blank phone numbers could be added via the REST system, resulting in an exception being thrown on startup. | ||
| 31 | * Resolved an issue where call history was not updating properly on attended transfers. | ||
| 32 | |||
| 33 | === Improvements === | ||
| 34 | |||
| 35 | * ((( | ||
| 36 | The http and https schemas are no longer forced on configured URLs in the CRMPopupWidget. This allows other URL schemas to be used. | ||
| 37 | ))) | ||
| 38 | * The REST API now supports setting a users default extension. | ||
| 39 | * The REST API now supports mute, unmute, and kick actions on conference room users. | ||
| 40 | * The REST API now supports querying the users in a specific conference room. | ||
| 41 | * The REST API now supports querying the current live conference rooms in a PBX. | ||
| 42 | |||
| 43 | === Performance Improvements === | ||
| 44 | |||
| 45 | * Large reduction in AMI traffic for multi-tenant Asterisk systems, particularly on initialization. | ||
| 46 | * Recordings now implement lazy loading and utilize temporary database storage, allowing for a smaller impact on memory and performance as the number of recordings grow. |