Rosella,<br><br>I've seen this caused by lack of QoS for the agent desktop traffic. In the right conditions it would cause completely random drops that we couldn't attribute to anything else. I think we matched based on the CRS server IPs and the appropriate ports (for the desktop) and then put it into a proper bucket so that it had some level of priority over other traffic. <br>
<br>I'd try that if you're not already doing it. <br><br><div class="gmail_quote">On Mon, Oct 19, 2009 at 1:36 PM, Rossella Mariotti-Jones <span dir="ltr"><<a href="mailto:rossella.mariotti.jones@chemeketa.edu">rossella.mariotti.jones@chemeketa.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal">We’ve been getting complaints from agents who once in
a while get bumped out of the agent desktop with this message “lost
connection with the cisco crs application server”, they can log back in right
away. This happened a few times last week and once today. I’m trying to
figure out if it might be a license issue, we have 10 seats and 13 configured
Resources/agents (maybe 6 of them in use at the same time). I turned on CRS
Desktop Services traces, would this shed some light? Where do I pick up the
logs? Any other ideas? Thanks in advance.</p>
</div>
</div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>