Cisco Cisco Unified Contact Center Enterprise 10.0(1) Installation Guide
4-5
Remote Silent Monitoring Installation and Administration Guide
Chapter 4 Installation
Configuration Manager
•
# Monitor Pool Simphones— Maximum simultaneous, real-time monitor
requests the platform can handle for the cluster. This should equal the number
of simphones in the cluster that are not used in the login pool. For example,
if 50 devices have been created total for the cluster, and 5 are used for the
login pool, then this value should be set to 45. (Registry key:
ClusterN_MaxNumRequests)
requests the platform can handle for the cluster. This should equal the number
of simphones in the cluster that are not used in the login pool. For example,
if 50 devices have been created total for the cluster, and 5 are used for the
login pool, then this value should be set to 45. (Registry key:
ClusterN_MaxNumRequests)
•
Peripheral ID—Peripheral instrument ID used to denote the cluster in
Unified ICME e.g., the ICME peripheral ID of the PIM for the UCM cluster.
(Registry key: ClusterN_PeripheralID)
Unified ICME e.g., the ICME peripheral ID of the PIM for the UCM cluster.
(Registry key: ClusterN_PeripheralID)
•
JTAPI Username—JTAPI application user username used by RSM to
connect to the specified UCM servers in the cluster. Refer to the “RSM
Application User Creation” topic in Chapter 3, Pre-Installation Tasks, for more
information. (Registry key: ClusterN_JTAPI_UserName)
connect to the specified UCM servers in the cluster. Refer to the “RSM
Application User Creation” topic in Chapter 3, Pre-Installation Tasks, for more
information. (Registry key: ClusterN_JTAPI_UserName)
•
Start MAC Range—First MAC address to use for auto-generation of MAC
range for simphone device names. For example, if 000000100010 is
specified, the range would proceed with SIP000000100010,
SIP000000100011, SIP000000100012, and so forth. MAC ranges must not
overlap between clusters. Note that the 0000:5Exx range is normally reserved
for public use, as per IANA standards. Refer to the “Simulated Phones
Configuration” topic in Chapter 3, Pre-Installation Tasks, for more
information. (Registry key: ClusterN_PhoneSim_StartMACRange)
range for simphone device names. For example, if 000000100010 is
specified, the range would proceed with SIP000000100010,
SIP000000100011, SIP000000100012, and so forth. MAC ranges must not
overlap between clusters. Note that the 0000:5Exx range is normally reserved
for public use, as per IANA standards. Refer to the “Simulated Phones
Configuration” topic in Chapter 3, Pre-Installation Tasks, for more
information. (Registry key: ClusterN_PhoneSim_StartMACRange)
•
Start Line Num Range—First extension number to use for auto-generation
of line extension range for simphone DNs. Line extension ranges must not
overlap between clusters. Correlates to
ClusterN_PhoneSim_StartMACRange value. If 1000 is specified, and
000000100010 is ClusterN_PhoneSim_StartMACRange, then the first
simphone device name generated will be SIP000000100010 and will have
line extension 1000; SIP000000100011 will have line extension 1001;
SIP000000100012 will have line extension 1002, and so forth. Refer to the
“Simulated Phones Configuration” topic in Chapter 3, Pre-Installation Tasks,
for more information. (Registry key:
ClusterN_PhoneSim_StartLineNumRange)
of line extension range for simphone DNs. Line extension ranges must not
overlap between clusters. Correlates to
ClusterN_PhoneSim_StartMACRange value. If 1000 is specified, and
000000100010 is ClusterN_PhoneSim_StartMACRange, then the first
simphone device name generated will be SIP000000100010 and will have
line extension 1000; SIP000000100011 will have line extension 1001;
SIP000000100012 will have line extension 1002, and so forth. Refer to the
“Simulated Phones Configuration” topic in Chapter 3, Pre-Installation Tasks,
for more information. (Registry key:
ClusterN_PhoneSim_StartLineNumRange)
•
SIP Transport—Tells PhoneSim how to conduct the SIP transmission with
Contact Manager for the cluster, via TCP or UDP. Must be set to tcp.
(Registry key: ClusterN_PhoneSim_SIPTransport)
Contact Manager for the cluster, via TCP or UDP. Must be set to tcp.
(Registry key: ClusterN_PhoneSim_SIPTransport)