Skip to Content
Last modified by ryanp on 2021/09/09 20:55
From version 4.1
edited by ryanp
on 2021/09/09 18:01
Change comment: Import
To version 5.2
edited by ryanp
on 2021/09/09 20:47
Change comment: Update document after refactoring.

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +ISYMDOCS.Home.iSymphony Releases.Beta Releases.iSymphony 3\.3 Beta Release Notes.WebHome
Content
... ... @@ -1,34 +1,43 @@
1 -The following is a complete list of changes made between iSymphony 3.2 Beta 1 and iSymphony 3.2 Beta 2. If you are upgrading from iSymphony 3.0.x, please see the changelog for [[iSymphony 3.1.4>>doc:iSymphony 3\.1\.4 Changelog]] as well.
1 +The following is a complete list of changes made between iSymphony 3.2.2 and iSymphony 3.3 Beta 1.
2 2  
3 +{{note}}
4 +If you are upgrading from iSymphony 3.2.x, please see the changelog for [[iSymphony 3.2.2>>doc:iSymphony 3\.2\.2 Change Log]] as well.
5 +{{/note}}
6 +
3 3  === Features ===
4 4  
5 5  * (((
6 -Users can now check the version of the current iSymphony server installation by running the following command:
7 -
8 -{{code language="bash"}}
9 -service iSymphonyServerV3 version
10 -{{/code}}
10 +Added List View to the User Widget.
11 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.
12 12  
13 13  === Resolved Bugs ===
14 14  
15 -* Resolved an issue where some recording metadata would not appear in the Recording Widget, for extensions that are part of a FreePBX Find Me Follow Me configuration.
16 -* Resolved an issue that would cause the server.xml configuration file to get wiped out in some rare instances, preventing startup of the server.
17 -* Resolved an issue where the CDR database connection would cease to function after some time of inactivity, preventing recording metadata from populating properly.
18 -* Resolved an issue where call history items, with blank caller ID would be created, when listening to voicemail or recordings over the phone, or calling a queue, conference room, or parking lot directly.
19 -* Resolved an issue where the voicemail playback bar would not hide properly, when multiple voicemails were selected.
20 -* Resolved an issue that prevented some exception stack traces from being written to the log.
21 -* Resolved an issue where multiple CRM popups would open when a space was present in the URL.
22 -* Resolved an issue where the extension login button, above the Agent List in the Queue Widget, would still be visible if the user did not have permission to log agents into the currently selected queue.
23 -* Resolved an issue where an upgrade performed via the iSymphony Administration Interface or the install.sh script would fail, when the current JAVA_HOME path was not set to /usr/java/latest.
24 -* Resolved an issue that would cause client sessions to leak memory, eventually leading to OutOfMemoryErrors and server instability.
25 -* Resolved an issue that would sporadically prevent call state from appearing in the queue agent list.
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.
26 26  
27 27  === Improvements ===
28 28  
29 -* The UNIQUEID variable is now available via the CRM widget, when using newer versions of Asterisk that do not report the UNIQUEID value as a channel variable over the AMI.
30 -* The startup scripts now verify the Java version before attempting to launch the server process. If the current installed version of Java is not supported by the current iSymphony server installation, an error message will be displayed and the server startup will abort.
32 +* (((
33 +The http and https schemas are no longer forced on configured URLs in the CRMPopupWidget. This allows other URL schemas to be used.
34 +)))
35 +* The REST API now supports setting a users default extension.
36 +* The REST API now supports mute, unmute, and kick actions on conference room users.
37 +* The REST API now supports querying the users in a specific conference room.
38 +* The REST API now supports querying the current live conference rooms in a PBX.
31 31  
32 -=== Regressions ===
40 +=== Performance Improvements ===
33 33  
34 -* 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.
42 +* Large reduction in AMI traffic for multi-tenant Asterisk systems, particularly on initialization.
43 +* 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.