Agent State transformations in Select Join and Join Across Line scenarios

From DocWiki

(Difference between revisions)
Jump to: navigation, search
Anitin (Talk)
(Agent State transformations in Select Join and Join Across Line scenarios)
Newer edit →

Revision as of 10:24, 30 November 2009

Agent State transformations in Select Join and Join Across Line scenarios



Problem Summary Agent States are behaving differently when agent uses Select Join or Join Across Line features to do conference
Error Message None.
Possible Cause Agent uses Select Join or Join Across Line to do conference
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 :


S.No Scenario Agent State before Conference Agent State after Conference
11.Call C1 arrives on ICD Route Point and it gets routed to Agent A1.
2. Agent A1 puts call C1 on hold and then initiates another Call C2 to Agent A2’s IPCC extension.
3. Agent A2 answers the call.
4. A1 does Select Join between the two calls.
A1: TALKING state.
A2: NOT READY state.
A1: TALKING state.
A2: TALKING state.
21. Call C1 arrives on ICD Route Point and it gets routed to Agent A1.
2. Agent A1 puts call C1 on hold and then initiates another Call C2 to Agent A2’s Non IPCC extension.
3. Agent A2 answers the call.
4. A1 does Select Join between the two calls.
A1: TALKING state.
A2: On receiving call C2 Agent State will not change.
A1: TALKING state.
A2: Agent State of will not change.
31. Call C1 arrives on ICD Route Point and it gets routed to Agent A1.
2. Agent A1 then initiates another Call C2 from his Non IPCC extension to Agent A2’s IPCC extension.
3. Agent A2 answers the call.4. A1 does Join Across Line between the two calls.
A1: TALKING state.
A2: NOT READY state.
A1: TALKING state.

A2: TALKING state.

41. Call C1 arrives on ICD Route Point and it gets routed to Agent A1.
2. Agent A1 then initiates another Call C2 from his Non IPCC extension to Agent A2’s Non IPCC extension.
3. Agent A2 answers the call.
4. Agent A1 does Join Across Line between the two calls.
A1: TALKING state.
A2: On receiving call C2 Agent State will not change.
A1: TALKING state.
A2: Agent State of will not change.
51. Call C1 arrives on ICD Route Point and it gets routed to Agent A1.
2. Agent A1 puts call C1 on hold and then initiates another Call C2 to ICD Route point again.
3. A1 does Select Join between the two calls.
A1: TALKING state. A1: TALKING state.
61. Call C1 arrives on ICD Route Point and it gets routed to Agent A1.
2. Agent A1 then initiates another Call C2 from his Non IPCC extension to ICD Route point again.
3. Agent A1 does Join Across Line between the two calls.
A1: TALKING state. A1: TALKING state.
71. Call C1 arrives on ICD Route Point and it gets routed to Agent A1.
2. Agent A2 then initiates another Call C2 from his IPCC extension to Agent A1’s Non IPCC extension.
3. Agent A1 does Join Across Line between the two calls.
A1: TALKING state.
A2: NOT READY state.
A1: TALKING state.
A2: TALKING state.
81. Call C1 arrives on ICD Route Point and it gets routed to Agent A1.
2. Agent A2 then initiates another Call C2 from his Non IPCC extension to Agent A1’s Non IPCC extension.
3. Agent A1 does Join Across Line between the two calls.
A1: TALKING state.
A2: On initiating call C2 Agent State will not change.
A1: TALKING state.
A2: Agent State of will not change


Release Release 8.0(1)
Associated CDETS # None


Rating: 3.0/5 (1 vote cast)

Personal tools