Ignite - Screen Refresh rates on 2nd screen

[acloghesy]

Hello,
Our callcenter tend to have the weirdest issues with Ignite.
Has anyone had similar issues?
Currently when one would use Ignite on their secondary screen. (2 screen setup)
the refresh rates would be out of wack while writing an email.

Also, now that we have the Classifications Codes setup. Sometimes the screen does not refresh the part of the account codes and we have alot of issues?
Has anyone resolved this? Or have suggestions? Thank you in advance,

[JasonTaylor]

I have seen lag on the Ignite web browser (8.1.0.0) which appears to be disconnected and is cured with a refresh/F5 but no problems in desktop ignite.

[StevenH510]

Hello,

We've seen the same issues around the desktop client of Ignite, and strangely enough when a member of Mitel's technical team came on site, his client behaved in the same way on the projector during a demostration.

Sadly after raising this as a fault with our 3rd party suppliers we were told to migrate away from Desktop and start using the web client.

The problem for us is we need to enforce all calls to be classified with account codes at the end of the calls, and agents just weren't able to do so.

Sorry I can't answer a work around, but be assured your not the only one with this problem, it occurs on all our Windows 7, Windows 10 Desktops & also in our VDI solution with the same OS's.

Cheers

Steve

[acloghesy]

I am in the same boat. We need to force Classification Codes so Desktop version is a must.

Funny enough it seemed to work better for some people than others, even with the same hardware.
I am at the point that I"m comparing software & Plugins installed to see what could be causing the issue.
I will update the post when I find something new! Thanks.

[maxbernard]

did you find a solution as I am having the same issue?

[acloghesy]

Sorry, I never recieved the updates about this ticket via email.
However, for this issue the problem was with the secondary screen.
So depending where the primary screen was it would work better, made physical adjustments to resolve the issue.

But, I think since the last update it's been working well on both screens unless people aren't complaining anymore.