Enterprise Parameters
|
Connection Monitor Duration
|
If an IP phone in the cluster registers on a secondary node, use this parameter to set the amount of time that the IP phone
waits before it falls back and re-registers with the primary node after the primary node becomes available. This parameter
affects all secure devices for a specific Secure Survivable Remote Site Telephony (SRST) router.
For more information, see Security Guide for Cisco Unified Communications Manager.
Default: 120 seconds
Restart all services for the changes to take effect.
|
CCMAdmin Parameters
|
Enable Dependency Records
|
This parameter is used to display dependency records that are required for troubleshooting. Displaying the dependency records
may be beneficial during an initial system setup.
Displaying the dependency records could lead to high CPU usage spikes and could impact call processing. To avoid possible
performance issues, disable this parameter after the system setup is complete. We recommend displaying dependency records
only during off-peak hours or during a maintenance window.
When enabled, you can select Dependency Records from the Related Links drop-down list, which is accessible from most configuration windows using Unified Communications Manager.
Default: False
|
User Data Service Parameters
|
Enable All User Search
|
This parameter allows you to search the corporate directory for all users when no last name, first name, or directory number
is specified. This parameter also applies to directory searches on the Cisco CallManager Self Care (CCMUser) window.
Default: True
|
Clusterwide Domain Configuration
|
Organization Top Level Domain
|
This parameter defines the top-level domain for the organization. For example, cisco.com.
Maximum length: 255 characters
Allowed values: A valid domain using upper and lowercase letters, numbers (0-9), hyphens, and dots (as a domain label separator).
Domain labels must not start with a hyphen. The last label must not start with a number. For example, this domain is invalid
-cisco.1om.
|
Cluster Fully Qualified Domain Name
|
This parameter defines one or more Fully Qualified Domain Names (FQDN) for the cluster. Multiple FQDNs must be separated by
a space. Specify wildcards within an FQDN using an asterisk (*). Example: cluster-1.cisco.com
*.cisco.com.
Requests containing URLs, such as SIP calls, that have a host portion that matches any of the FQDNs in this parameter are
routed to that cluster and the attached devices.
Maximum length: 255 characters
Allowed values: An FQDN or a partial FQDN using the * wildcard. Upper and lowercase letters, numbers (0-9), hyphens, and dots
(as a domain label separator). Domain labels must not start with a hyphen. The last label must not start with a number. For
example, this domain is invalid -cisco.1om.
|
IPv6
|
Enable IPv6
|
This parameter determines whether Unified Communications Manager can negotiate Internet Protocol Version 6 (IPv6) and whether phones are allowed to advertise IPv6 capability.
IPv6 must be enabled on all other network components including on the platform of all nodes before you enable this parameter.
Otherwise, the system continues to run in IPv4-only mode.
This is a required field.
Default: False (IPv6 is disabled)
You must restart the following services for the IPv6 parameter change to take effect, and the affected services in the IM and Presence Service cluster.
|
Cisco Syslog Agent
|
Remote Syslog Server Name 1
|
Enter the name or IP address of the remote Syslog server. Cisco Unified Serviceability do not send the Syslog messages if
a server name is not specified. This parameter is required only if you are using the Syslog server for logs.
Maximum length: 255 characters
Allowed values: A valid remote Sylog server name using upper and lowercase letters, numbers (0-9), hyphens, and dots.
Do not specify another Unified Communications Manager node as the destination.
|
Cisco Jabber
|
Never Start Call with Video
|
This parameter determines if video is sent when a video call starts. Select True to start video calls without immediately sending video. Anytime during the video call, you can choose to start sending your
video.
This parameter overrides any IM and Presence Service preferences. When set to False, video calls start according to the preferences set in IM and Presence Service.
Default: False.
|
SSO and OAuth Configuration
|
SSO Login Behavior for iOS
|
This parameter is required to allow Cisco Jabber to perform the certificate-based authentication with the IdP in a controlled
mobile device management (MDM) deployment.
The SSO Login Behavior for iOS parameter includes the following options:
-
Use Embedded Browser—If you enable this option, Cisco Jabber uses the embedded browser for the SSO authentication. Use this option to allow iOS
devices prior to version 9 to use SSO without cross-launching into the native Apple Safari browser.
-
Use Native Browser—If you enable this option, Cisco Jabber uses the Apple Safari framework on an iOS device to perform the certificate-based
authentication with an Identity Provider (IdP) in the MDM deployment.
Note
|
We do not recommend configuring this option, except in a controlled MDM deployment, because using a native browser is not
as secure as the using the embedded browser.
|
This is a required field.
Default: Use the embedded browser (WebView).
|
OAuth with Refresh Login Flow
|
This parameter controls the login flow used by clients such as Cisco Jabber when connecting to Unified Communications Managers.
-
Enabled—If you enable this option, clients can use an oAuth-based Fast Login flow to provide a quicker and streamlined login
experience, without requiring the user input to re-log in. For example, due to a network change. The option requires support
from the other components of the Unified Communications solution, such as Expressway and Unity Connection (compatible versions
with the refresh login flow enabled).
-
Disabled—If you enable this option, the existing behavior is preserved and is compatible with older versions of other system
components.
Note
|
For Mobile and Remote Access deployment with Cisco Jabber, we recommend enabling this parameter only with a compatible version
of Expressway that supports oAuth with Refresh login flow. Incompatible version may impact the Cisco Jabber functionality.
Please refer the specific product documents for supported version and configuration requirements.
|
Important
|
This feature is applicable for Release 12.5(1)SU7 and 14SU3 onwards.
Along with the publisher, the subscriber node also has the access to update the refresh token on the requester node database
and the same will be replicated across the cluster.
|
This is a required field.
Default: Disabled.
|
Use SSO for RTMT
|
This parameter is configured to enable SAML SSO for Real-Time Monitoring Tool (RTMT).
The Use SSO for RTMT parameter includes the following options:
-
True—If you choose this option, RTMT displays the SAML SSO-based IdP sign-in window.
Note
|
When you perform a fresh install, the default value of the Use SSO for RTMT parameter appears as True.
|
-
False—If you choose this option, RTMT displays the basic authentication sign-in window.
Note
|
When you perform an upgrade from a Cisco Unified Communications Manager version where Use SSO for RTMT parameter does not exist, the default value of this parameter in the newer version appears as False.
|
This is a required field.
Default: True.
|