1) Welcome to the Party!
2) As you are obviously new here, I have some suggestions to help us all help you:
When you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.
This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)
You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.
If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.
Similar to This:
Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600
3) I've never had this happen before, but you've given no actual information that could be used to troubleshoot it. Note that it is (definitely) useful to know the hardware and number of servers, certainly, but the most important information has been left out (ie: the above newbie request). I realize it's an unusual situation and hard to tell what may be needed, but always start with the basics (above) and we'll all do our best to help. But without those basics it's often difficult to even venture a guess. Note also that the 'Vicibox' version is in no way related to the 'Vicidial' version. Vicibox is just the installation media.
4) Since we've nothing to go by ... my only serious advice would be to see what you can do to limit paused agents. The good news is that an upgrade may resolve your issue for multiple reasons. Obviously the first reason is that this may be due to a bug that has already been squished. The second reason is that the latest version of Vicidial has an option to force-log-out agents who have been paused for a certain amount of time.
Campaign Setting:
Agent Pause Max Seconds - If this is set to greater than 0, and the agent has not gone out of PAUSED status in this number of seconds, the agent will automatically be logged out of the agent screen. Default is 0 for disabled.