Cisco Cisco IPCC Web Option Technical References
Registry Keys
75
75
-DEFROUTE 3214
If a default route is not configured, the PG will give a negative
acknowledgement (NAK) to the Avaya causing vector processing to proceed.
The NAK may be the desirable action, depending on how the Avaya vectors are
written.
acknowledgement (NAK) to the Avaya causing vector processing to proceed.
The NAK may be the desirable action, depending on how the Avaya vectors are
written.
3.15. Unified
ICM Configuration for “CMS-less” PGs
In a PG configuration that does not use CMS, some additional configuration is
necessary in Unified ICM software. Each of the following changes can be made
by using the Configuration Manager’s PG Explorer tool.
necessary in Unified ICM software. Each of the following changes can be made
by using the Configuration Manager’s PG Explorer tool.
You must configure all agents in Unified ICM database.
You must map agents to skill groups in Unified ICM database. The agent-
to-skill group mapping must match the Avaya configuration. In addition, the
subgroup must correctly map to the agent’s priority.
to-skill group mapping must match the Avaya configuration. In addition, the
subgroup must correctly map to the agent’s priority.
You must configure monitored instruments in the Peripheral Monitor table
of Unified ICM database. Agent stations should be monitored.
of Unified ICM database. Agent stations should be monitored.
You must configure Peripheral Targets in Unified ICM database for all
VDNs through which monitored calls flow.
VDNs through which monitored calls flow.
3.16. Maintaining Your Configuration
It is preferred that changes made to your configuration be accomplished first on
the Avaya/CMS, then in Unified ICM database. This will ensure that the PG
sees the configuration updates on the Avaya/CMS systems.
the Avaya/CMS, then in Unified ICM database. This will ensure that the PG
sees the configuration updates on the Avaya/CMS systems.
It is imperative that the Avaya, CMS, and Unified ICM Database configurations
are kept synchronized (that is, up-to-date with each other). Inaccurate or
incomplete data could result in inaccurate agent and/or call data.
are kept synchronized (that is, up-to-date with each other). Inaccurate or
incomplete data could result in inaccurate agent and/or call data.
3.17. Registry Keys
This section provides the recommended values for the PIM dynamic registry
keys and PIM config registry keys.
keys and PIM config registry keys.
The recommended values for the PIM dynamic registry keys are:
BriCheckMeters = 0 (for CMS), 1 (for CMS-less)
This value indicates whether the PIM should throttle the ASAI/ CTI message
rates or not. “1” indicates that it should enable message metering (that is,
throttle outgoing messages).
rates or not. “1” indicates that it should enable message metering (that is,
throttle outgoing messages).
Note:
The dynamic registry field “BriMaxOutstandingMessages” is used along with
“BriCheckMeters” registry field to indicate the number of outstanding ASAI/
CTI messages (that is, messages waiting for a response from the CVLAN
Server). After the PIM has reached the maximum number of outstanding
messages, it will not send messages until one pending ASAI/ CTI message has
been received.
“BriCheckMeters” registry field to indicate the number of outstanding ASAI/
CTI messages (that is, messages waiting for a response from the CVLAN
Server). After the PIM has reached the maximum number of outstanding
messages, it will not send messages until one pending ASAI/ CTI message has
been received.
During the startup of the PIM process, the PIM will send the ASAI/ CTI
messages at a faster rate until the limit controlled by the
“BriMaxOutstandingMessages” field. The high priority outgoing messages
take precedence over the normal priority outgoing messages.
messages at a faster rate until the limit controlled by the
“BriMaxOutstandingMessages” field. The high priority outgoing messages
take precedence over the normal priority outgoing messages.