<![CDATA[Call Queue issue]]>I have a customer with a unique issue. The customer has a support desk which a queue assigned to it. The problem is that quite often agents within the queue put themselves on "Do Not Disturb" via the FOP2 interface and then will "click" on a incoming call to answer a call in the queue to help colleges out.

The issue is that about half of the time using this methodology FOP2 allows the call to be picked up, the other half it just cuts the call off???

Any ideas where to look for this problem??

]]>http://localhost:4567/topic/432/call-queue-issueRSS for NodeTue, 27 Oct 2026 08:04:19 GMTWed, 16 Jun 2010 07:42:15 GMT60<![CDATA[Reply to Call Queue issue on Thu, 17 Jun 2010 00:48:02 GMT]]>The only way to debug is to start fop2_server in debug mode (level 15) and stop capturing just after a call is cut off... it will be quite hard to do on a production system. It is important to identify the call that was cut off somehow, as the manager is very verbose. A big file with no indications of the call that had the problem is not really useful.

To start fop2 in debug mode:

/usr/local/fop2/fop2_server -X 15

Best regards,

]]>http://localhost:4567/post/1956http://localhost:4567/post/1956Thu, 17 Jun 2010 00:48:02 GMT