Hello.
Currently we are struggling to make Interaction Connect work for one of our customers. We have installed it on new IIS server, and we can't find a way to make it work smoothly. Customer performed many tests, which are showing slow reaction time, errors ("This folder could not be opened, please reload"), lags.
Customer insist to re-create the view that they were using in Desktop, which contains speed dial window, about 5-6 workgroup directories, company directory and two custom addins (although we did not installed those addins yet).
When Connect is opened on Chrome or Firefox on CIC server (same network as web server of course), and we have only 2-3 windows (my interactions and company directory), it works fine. After adding few workgroup directories and speed dial list, it's still not bad, but errors are happening sometimes - but that only when we are not using customer's proxy (which they insist should be used). With proxy the situation is worse. And if Connect is launched on agent's computer connected to CIC network via VPN, it gets really bad.
I would really appreciate feedback from anyone who is using Connect with 30 or more agents, which are using multiple views in their Connects and are (at least partially) connecting from home.
If Connect works fast for You, and generates no error - could You please describe some details about configuration? PureConnect and Connect versions, web server type and operating system, how many views agents are using, details about Pureconnect and web server gear (memory, CPU).
We are on the verge of informing the customer that we are simply unable to make it work, and I would like to try every possibility before we surrender.
Many thanks for Your inputs!
Pawel Godek
Telefonix
#Unsure/Other------------------------------
Pawel Godek
Telefonix Sp. Z o.o
------------------------------