|Attention: DocWiki has reached EOL and will be decommissioned January 25, 2019.|
Issues related to Agents Using Shared Lines
m (1 revision)
Revision as of 15:57, 14 September 2011
|Problem Summary||Issues related to agents using shared line leading to NonUniqueObjectException in HRDM.|
|Possible Cause||Agent having a shared line (IPCC or NON IPCC ) on his phone|
|Recommended Action|| Unified CCX has to detect and ignore the NON ACD shared line/s on agent's phone. CCX will not be doing reporting and other event handling which will happen on that shared line. An agent should not use that shared line to do operations line JAL and DTAL with other lines on agent's phones which are being monitored by Unified CCX.
For the detection of the shared lines the fix ( for bug# CSCth96226) is provided in 8.0(2)SU1 and onward releases. So if agents are using the shared lines then 8.0(2)SU1 should be applied. To do a check that whether the shared line detection is working (after applying 8.0(2)SU1), do the following : 1. Login the agent who has shared NON ACD line on his phone 2. Check MIVR logs for the below log statement (SS_RM DEBUG should be enabled)
Sometimes this shared line detection doesn't work as expected and thus leads to problems like Agent state record writing in DB.
Error in writing into DB: Table=AgentStateDetail,Exception=javax.persistence.PersistenceException: org.hibernate.NonUniqueObjectException: a different object with the same identifier value was already associated with the session:
To problem happens when the line is shared between agents and non agents. To solve this associate all the phones sharing extensions with agent/s with RM JTAPI application user in Cisco Unified Call Manager.
Please refer to the details mentioned here.
|Associated CDETS #||CSCth96226|