Cisco Cisco IP Contact Center Release 4.6.2 Technical References
18
Overview
Queue Types
Avaya ARI supports Virtual VRU queuing of calls. This type of queue uses
specially configured VDNs to position the call on the ACD while waiting for
an available agent.
Avaya ARI supports Virtual VRU queuing of calls. This type of queue uses
specially configured VDNs to position the call on the ACD while waiting for
an available agent.
If an external VRU is used to queue a call, you must configure a VRU PG as
a type 2 VRU in Unified ICM. The scripts for the new call VDNs should
use the TranslationRoute to VRU node to send the call to the VRU.
a type 2 VRU in Unified ICM. The scripts for the new call VDNs should
use the TranslationRoute to VRU node to send the call to the VRU.
If you use CVP to queue calls, you must configure a VRU PG and CVP must
be configured as a type 10 VRU.
be configured as a type 10 VRU.
1.7. Unsupported Features
• The following features are unsupported:
• Trunk and Trunk Group Reporting
• Peripheral Service Level Reporting
• RONA
• Avaya ACD Queues
• Silent Monitoring
• Agent ID calls in Avaya ARI
• Trunk and Trunk Group Reporting
• Peripheral Service Level Reporting
• RONA
• Avaya ACD Queues
• Silent Monitoring
• Agent ID calls in Avaya ARI
1.8. Avaya Notes and Restrictions
• If the hard phone is used to change agent state via a dedicated button on
the phone, it may take several seconds (a configurable value) to be
informed of the state change. This can be overcome by jiggling the
handset. See Table 17 for details on configuration settings.
• There is a very small window during startup in which an agent can
informed of the state change. This can be overcome by jiggling the
handset. See Table 17 for details on configuration settings.
• There is a very small window during startup in which an agent can
log in via his hard phone but will not be seen as “Logged In” by
Unified ICM. Two actions can be performed if this happens:
Unified ICM. Two actions can be performed if this happens:
• The agent sees that Unified ICM shows he is logged out on his soft
phone and logged in on his hard phone (if equipped to do so). If he
logs in again using the soft phone, Unified ICM accepts the login.
logs in again using the soft phone, Unified ICM accepts the login.
• The agent can change his state via his hard phone. This causes Unified
ICM to see the state change and mark the agent as logged in.
• Each agent device is allowed only one line appearance. This means that
an agent will not be able to answer a second call using the soft phone,
although they may be able to do so with his (or her) hard phone.
although they may be able to do so with his (or her) hard phone.
• Callers in a VVRU script on the switch may be lost if the ARS PIM is
restarted or a switch from Side A to Side B occurs.
• If hard phone support is enabled, agent state changes via the hard phone
will be delayed because the phone is not periodically checked for status.
Soft phone agent state control is the preferred method.
Soft phone agent state control is the preferred method.