Summary

• Page properties (4 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-iSymphony 3.5.5 Change Log
	1	+iSymphony 3.5.9.8 Change Log

Parent

...	...	@@ -1,0 +1,1 @@
	1	+iSymphony 3\.5 Release Notes

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.michelk
	1	+XWiki.arthurh

Content

...	...	@@ -1,28 +1,44 @@
1		-The following is a complete list of changes made between iSymphony 3.5.3 and iSymphony 3.5.4.
	1	+The following is a list of changes made between iSymphony 3.5.4 and iSymphony 3.5.9.8. This release should greatly improve memory utilization and resolves several memory leaks which users in high-volume environments  where customers reported the need to restart the iSymphony Server periodically. Please report any anomalies at [[http:~~/~~/support.getisymphony.com>>url:http://support.getisymphony.com||shape="rect"]]
2	2
	3	+\\
	4	+
3	3	{{note}}
4		-If you are not upgrading from iSymphony 3.5.3, be sure to check the change log and upgrade notes for previous versions as well.
	6	+If you are not upgrading from iSymphony 3.5.4, be sure to check the change log and upgrade notes for previous versions as well.
5	5	{{/note}}
6	6
7		-=== Improvement ===
	9	+(% class="auto-cursor-target" %)
	10	+\\
8	8
9		-* (((
10		-Improved the way AMI events are received and distributed throughout iSymphony to better take advantage of parallelization for the majority of incoming AMI traffic. This improvement significantly increases load tolerance for multicore systems with heavy call and/or queue traffic.
11		-)))
	12	+{{note}}
	13	+(% style="color: rgb(255,0,0);" %)__**IMPORTANT ERRATA:**__(%%) This version contains upgraded(% style="color: rgb(0,0,0);text-decoration: none;" %) websocket push libraries (moving away from jquery push methods to plain javascript push). **The side effect of this is that end users may get a **(% style="color: rgb(0, 0, 0); text-decoration: none; color: rgb(255, 0, 0)" %)**"unable to load push"**(% style="color: rgb(0,0,0);text-decoration: none;" %)** message when upgrading from any previous version(s) in a BIG RED BANNER at the top of the page when opening the client or administrator web interfaces after upgrading to this version.** **If a user obtains this message, they should clear their browser cache or reload the page bypassing and refreshing the local cache (CTRL+F5 or Shift+Click Reload Button) or equivalent in the end-user's browser.**
12	12
	15	+(% style="color: rgb(0,0,0);text-decoration: none;" %)Future upgrades will not require this step as HTTP headers should now disable caching and the proper version should always be downloaded.
	16	+{{/note}}
	17	+
	18	+=== Improvements ===
	19	+
	20	+* Improved reliability and performance of HTTP push, switched to pure javascript AJAX push libraries for client DOM modifications.
	21	+* Added HTTP push strategies. iSymphony will now use websockets in most browsers and falls back to long polling where websockets.
	22	+* Added code resolving two Security vulnerabilities reported by 1st & 3rd party vulnerability scans.
	23	+
13	13	=== Resolved Bugs ===
14	14
15	15	* (((
16		-Resolved an issue where current queue calls failed to load in the My Stream Widget if the user logged out and back in.
	27	+Resolved an issue where iSymphony cannot transfer calls that are ringing
17	17	)))
	29	+* Resolved several memory and performance issues which were reported on high-volume systems
	30	+** Resolved memory leak in in-memory data store
	31	+** Resolved an issue where HTTP Push caused memory leak under certain circumstances.
	32	+** Upgraded components of a third party User Interface library resolving several memory leaks in the User Interface
	33	+** Resolved issue with client side (browser) memory leaks on AccountPopupButton instantiations due to server holding reference in List View. Large List views benefit greatly.
	34	+* Resolved issue where leftover ASTDB values were causing invalid parsing of presence state when invalid entries existed in ASTDB during a "presencestate list" command and the extension entries did not exist within cxpanel model. This should resolve invalid presence state representations.
18	18	* (((
19		-Resolved an issue where "Hold" state would show incorrectly in the User Widget in some cases.
	36	+Fixed an issue where "remember me" wasn't working right in some instances.
20	20	)))
21	21	* (((
22		-Resolved an issue where Queue Widget would throw an NPE for attended transfer events with no destination application set.
	39	+Fixed an issue where "box width" in users box view wasn't saved after setting and clicking "Ok"
23	23	)))
24	24	* (((
25		-Resolved an issue where calls placed on hold could occasionally disappear from the user's My Stream preventing them from taking the active call off hold.
26		-
	42	+Added cache and pragma HTTP headers to resolve future issues with cached JS dependencies
27	27
28	28	)))