Latest revision as of 15:20, 9 April 2010

Additional Log Levels required for escalating issues related to Routing and Queuing Revert back to default log levels once relevant logs were collected for the issue otherwise this may impact the system's performance.

Error Message

None.

Possible Cause

Multiple Causes

Recommended Action

When Conference is done using Select Join or Join Across Line feature then the Agent states for the agents who are present on that conference call will be computed. Unified CCX ignores agent state transformation when the call is on an agent's Non IPCC extension except a corner case where an agent do JAL, and as a result of that the call ends up on the agent’s non IPCC extension.

Following are some of the scenarios where Unified CCX sets agent's state before and after conference :

Previous versions do not have these tracing levels. Tracing is on by default and you can collect logs by copy/pasting from Java console from system tray after launching RTR. (You also need to enable console logging through Java properties in control panel which are also enabled by default)