Smartertrack Communicator Call Recording Broken in Windows10
Problem reported by - 6/17/2016 at 11:31 AM
We have an issue where when an agent resides in a department with forced call recording the ability to effectively use smartertrack communicator on windows 10 is lost. The symptoms appear to be extensive CPU usage of the client after each call made, the recordings are never placed in the smartertrack call log. The agent in question when they receive an inbound call will no longer be able to receive calls from the queue until the client is restarted.
Placing the agent in question within a department that does not have enforced call recordings resolves the issue and normal call processing is allowed.

Reply to Thread