Cisco Cisco Unified Contact Center Enterprise 9.0(2) Technical References
40
Additional Avaya Gateway Registry Settings
4.1. Config Registry Settings
Configuration settings are those that require the Avaya Gateway to be
restarted before they take effect.
restarted before they take effect.
Table 16 shows the Config Registry entries.
Table 16: Config Registry Entries
Registry Key
String
String
Valid
Values
Values
Default
Value
Value
Description
MaxEventMo
nitoringClust
erIDs
nitoringClust
erIDs
1-n
8000
This is the number of Avaya Cluster
IDs that can be used for monitoring
events on a VDN for the Avaya
Gateway. These VDNs are used for
the Virtual VRU functionality. Event
Monitoring Cluster IDs as are also
used by other processes in the Avaya
Gateway to query devices and agents
to get current state information.
IDs that can be used for monitoring
events on a VDN for the Avaya
Gateway. These VDNs are used for
the Virtual VRU functionality. Event
Monitoring Cluster IDs as are also
used by other processes in the Avaya
Gateway to query devices and agents
to get current state information.
MaxCallCont
rolClusterIDs
rolClusterIDs
1-n
6000
This is the number of Avaya Cluster
IDs that can be used for call control
associations by the Avaya Gateway.
The Avaya Gateway uses Call
Control associations to perform
various call control functions like call
hold, make call, transfer, etc.
IDs that can be used for call control
associations by the Avaya Gateway.
The Avaya Gateway uses Call
Control associations to perform
various call control functions like call
hold, make call, transfer, etc.
MaxDomain
ControlCluste
rIDs
ControlCluste
rIDs
1-n
10000
This is the number of Avaya Cluster
IDs that can be used for Domain
Control associations by the Avaya
Gateway. Note that it is common for
the Gateway to use a second Domain
Control association (in addition to the
Domain control association used to
monitor a device) to perform call
control actions (transfer, make call,
etc.) For this reason, this number
should be twice the number of agent
extensions that are to be monitored on
the switch.
IDs that can be used for Domain
Control associations by the Avaya
Gateway. Note that it is common for
the Gateway to use a second Domain
Control association (in addition to the
Domain control association used to
monitor a device) to perform call
control actions (transfer, make call,
etc.) For this reason, this number
should be twice the number of agent
extensions that are to be monitored on
the switch.
4.1.1. Cluster IDs
The number of Cluster IDs that are available on the Avaya switch
(regardless of the type of Cluster ID) is a global value for all adjunct
applications attached to the switch. If there are other applications in addition
to the Avaya Gateway using Cluster IDs from this global pool, the number
of Cluster IDs that the Avaya Gateway can use will be reduced. Reducing
the number of Cluster IDs that can be used by the Gateway will affect its
performance. If the Avaya Gateway attempts to use more Cluster IDs than
are configured (or the default number if no registry entry is found), or more
(regardless of the type of Cluster ID) is a global value for all adjunct
applications attached to the switch. If there are other applications in addition
to the Avaya Gateway using Cluster IDs from this global pool, the number
of Cluster IDs that the Avaya Gateway can use will be reduced. Reducing
the number of Cluster IDs that can be used by the Gateway will affect its
performance. If the Avaya Gateway attempts to use more Cluster IDs than
are configured (or the default number if no registry entry is found), or more