Transfer and Connect: Agent Goes Ready, Queued Caller Never Delivered to Agent

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (1 revision)
m (Bot: Adding {{Template:Required Metadata}})
 
Line 1: Line 1:
 +
{{Template:Required Metadata}}
== Agent Goes Ready, Queued Caller Never Delivered to Agent ==
== Agent Goes Ready, Queued Caller Never Delivered to Agent ==

Latest revision as of 19:09, 18 December 2009

Agent Goes Ready, Queued Caller Never Delivered to Agent

Problem Summary Agent is ready but caller in queue never delivered to agent
Error Message None
Possible Cause The Interruptible box on the queuing Network VRU script is not checked.
Recommended Action In the Unified ICME Network VRU Script Explorer, look at the Network VRU script that is queuing the caller. It must be marked Interruptible for the Unified ICME software to be able to interrupt the script and deliver the caller to the available agent.
Release Release 7.0(2)
Associated CDETS # None.
Possible Cause The agent Device Target does not have a label associated with the Unified CVP routing client.
Recommended Action In ICM Device Target explorer, look at the labels for the agent device target. The label must be associated with the Unified CVP routing client. If is not associated with a Unified CVP routing client, then one must be added.
Release Release 7.0(2)
Associated CDETS # None.
Possible Cause The NetworkTransferEnabled flag has not been set to 1 in the ICM script.
Recommended Action At the beginning of the first Unified ICME caller entry script, and on every post-route script that may be invoked later in the call, the NetworkTransferEnabled variable must be set to the value of 1.
Release Release 7.0(2)
Associated CDETS # None.
Possible Cause The Gatekeeper routing is not configured properly and the Unified CVP H.323 Service cannot find the correct Unified CM to which to send the agent transfer.
Recommended Action When the H.323 Service gets a device target label from the Unified ICME, it must look up that label on the Gatekeeper in order to know to what IP address to send the call. Configure the Gatekeeper with the correct routing information to resolve this issue.
Release Release 7.0(2)
Associated CDETS # None.

Rating: 4.0/5 (1 vote cast)

Personal tools