The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This documentation update resolves CSCut08307.
Field |
Description |
---|---|
Description |
Identify the purpose of the device. You can enter the user name (such as John Smith) or the phone location (such as Lobby) in this field. For Cisco VG248 gateways, begin the description withVGC<mac address>. The description can include up to 128 characters in any language, but it cannot include double-quotes ("), percentage sign (%), ampersand (&), back-slash (\), or angle brackets (<>). |
This documentation update resolves CSCuu44805.
The maximum audio streams per software conference bridge is incorrectly listed as 128 in the "Software Conference Devices" section of the Cisco Unified Communications Manager Administration Guide. The correct value is 256.
This documentation update resolves CSCve07463.
The DHCP subnet setup tip is incorrect in the Cisco Unified Communications Manager Administration Guide. The correct information for "DHCP Subnet Setup Tips" is as follows:
Changes to the server configuration do not take effect until you restart DHCP Monitor Service.
This documentation update resolves CSCur86259.
The following information is omitted from the "Directory Number Settings" topic in the Cisco Unified Communications Manager Administration Guide and online help:
The Directory Number is a mandatory field.
This documentation update resolves CSCuo74599.
The following information is omitted in the "Set Up Cisco Unified IP Phone" procedure in the Cisco Unified Communications Manager Administration Guide:
After you add a directory number to a phone and click Save, the following message appears:
Directory Number Configuration has refreshed due to a directory number change. Please click Save button to save the configuration.This documentation update resolves CSCup68350.
The "SIP Profile Settings" section in the Administration Guide contains incorrect information about the Disable Early Media on 180 check box. The description states that the setting applies to both the 180 and 183 responses, but the setting applies to only the 180 response.
This documentation update resolves CSCun04965.
You can now configure the Owner User ID in the Phone Settings interface if you are using Extension Mobility. Extension Mobility now supports device owners. A note indicating otherwise is listed in error in the Cisco Unified Communications Manager Administration Guide.
This documentation update resolves CSCur62680.
The following information is omitted from the Host Name/IP Address field description, listed under the "Server Setup" chapter in the Administration Guide and the online help.
Note | If Jabber clients are used, we recommend that you use an FQDN instead of a hostname so that the Jabber clients can resolve the Unified Communications Manager domain name. |
This documentation update resolves CSCun74975.
The following information is omitted from the IPv6 Address (for dual IPv4/IPv6) field description under "Server Settings" in the Cisco Unified Communications Manager Administration Guide:
You cannot use an IPv4 address as a hostname in a network environment with both IPv4 and IPv6 addresses.
This documentation update resolves CSCuu40700.
The "Location" chapter in the Administration Guide and online help states that " The Hub_None location specifies unlimited audio bandwidth and unlimited video bandwidth." This information is inacurrate. The correct information for Hub_None is as follows:
Hub_None is an example location that typically serves as a hub linking two or more locations. It is configured by default with unlimited intra-location bandwidth allocations for audio, video, and immersive bandwidth, but you can specify bandwidth allocations for each of these. By default, devices not assigned to other locations are assigned to Hub_None.
This documentation update resolves CSCus74994.
The following information about Directory URIs has been added to the Directory number settings table in the Cisco Unified Communications Manager Administration Guide:
The maximum number of directory URIs that the Intracluster Lookup Service (ILS) can replicate is seven.
The Cisco Unified Communications Manager Administration Guide and online help contain incorrect information about deleting route patterns such as route groups, hunt lists, and hunt pilots.
The following information further explains the context:
The association of any pattern or directory number (DN) to any device is separate from the devices and patterns themselves. As a result, you can delete a route list even if it is currently used for a route pattern. The same applies to hunt lists, hunt pilots, phones, and DNs.
As a best practice, whenever you remove a device, you must ensure that any associated pattern or DN is accounted for in your numbering plan. If you no longer need a pattern or DN, you must delete it separately from the device with which it was associated. Always check the configuration or dependency records before you delete a hunt list.
The following is an example of incorrect information in the guide:
Cisco Unified Communications Manager associates hunt lists with line groups and hunt pilots; however, deletion of line groups and hunt pilots does not occur when the hunt list is deleted. To find out which hunt pilots are using the hunt list, click the Dependency Records link from the Hunt List Configuration window. If dependency records are not enabled for the system, the dependency records summary window displays a message.
The following is the corrected information:
Cisco Unified Communications Manager associates hunt lists with line groups and hunt pilots. You can delete a hunt list even when it is associated with line groups and hunt pilots. To find out which hunt pilots are using the hunt list, click the Dependency Records link from the Hunt List Configuration window. If dependency records are not enabled for the system, the dependency records summary window displays a message.
This documentation update resolves CSCuq42434.
The note about user locales in the Cisco Unified IP Phone settings section of the Administration Guide incorrectly states that Cisco Unified Communications Manager uses the user locale that is association with the device pool. The following is the correct note:
Note | If no user locale is specified, Cisco Unified Communications Manager uses the user locale that is associated with the common device configurations. |
This documentation update resolves CSCvb74432.
The time period documentation contains an incorrect example that can cause configuration problems. It suggests to use a date range for a single day time period: "Choose a Year on value of Jan and 1 and an until value of Jan and 1 to specify January 1st as the only day during which this time period applies."
That is incorrect; please avoid using this example for the "Year on...until" option for time periods.
This documentation update resolves CSCuq11351.
The Call Control Agent Profile chapter in Cisco Unified Communications Manager Administration Guide contains insufficient information about the Call Control Agent Profile configuration fields. The following table contains the detailed information.
Field |
Description |
|
---|---|---|
Call Control Agent Profile Configuration |
||
Call Control Agent Profile ID |
Enter a unique ID for the Call Control Agent Profile. This ID is associated with the Directory Number. It is a mandatory field. The allowed values are alphanumeric (a-zA-Z0-9), period (.), dash (-), and space ( ). |
|
Primary Softswitch ID |
Enter the primary softswitch ID (prefix) of the directory number alias servers. It is a mandatory field. The allowed values are alphanumeric (a-zA-Z0-9), period (.), dash (-), and space ( ). |
|
Secondary Softswitch ID |
Enter the secondary softswitch ID (suffix) of the directory number alias servers. The allowed values for this field are alphanumeric (a-zA-Z0-9), period (.), dash (-), and space ( ). |
|
Object Class |
Enter the object class name for the directory numbers associated with the call control agent profile. It is a mandatory field. The allowed values are alphanumeric (a-zA-Z0-9), period (.), dash (-), and space ( ). |
|
Subscriber Type |
Enter the subscriber type of the directory numbers associated with the call control agent profile. The allowed values are alphanumeric (a-zA-Z0-9), period (.), dash (-), space ( ), and at (@). |
|
SIP Alias Suffix |
Enter the SIP alias suffix. The E.164 number that you specify for the directory number is appended to this suffix when mapping to the SIP Alias field in the LDAP directory. The allowed values are alphanumeric (a-zA-Z0-9), period (.), dash (-), space ( ), and at (@). |
|
SIP User Name Suffix |
Enter the SIP user name suffix. The E.164 number that you specify for the directory number is appended to this suffix when mapping to the SIP User Name field in the LDAP directory. The allowed values are alphanumeric (a-zA-Z0-9), period (.), dash (-), space ( ), and at (@). |
This documentation update resolves CSCuq26110.
The following is a correction to Line Group Deletion.
You can delete a line group that one or more route/hunt lists references. If you try to delete a line group that is in use, Cisco Unified Communications Manager displays an error message.
Tip | Dependency Records is not supported for line groups. As a best practice, always check the configuration before you delete a line group. |
This documentation update resolves CSCuo90637.
The following note is omitted from the Cisco Unified Communications Manager Administration Guide and online help for Hunt Group configuration:
Caution | Do not specify the same value for the Maximum Hunt Timer and the RNA Reversion Timeout on the associated line group. |
This documentation update resolves CSCup79162.
The following information is omitted from the "SIP Profile Settings" topic in the Cisco Unified Communications Manager Administration Guide and online help:
Do not configure this capability for SIP intercluster trunks to Cisco SME or other Cisco Unified Communications Manager systems.
This documentation update resolves CSCvb37715.
The restrictions in the Multilevel Precedence and Preemption (MLPP) chapter incorrectly state that only SCCP phones support this feature.
SCCP phones and some SIP phones support MLPP. To verify feature support, see the Cisco Unified IP phone administration guide for your model.
This documentation update resolves CSCuu43939.
The following information is omitted from the "Service Profile Setup" chapter in the Cisco Unified Communications Manager Administration Guide:
A service profile is applied for a given device only when the owner user ID is specified. In that case, the service profile configured for the respective user is applied.
A note in the Service Profile Settings table is incorrect. The correct note is:
Note | If you specify a default service profile, end users that do not have an associated service profile automatically inherit the default service profile settings. In the same manner, any devices that do not have specified a owner user ID inherit the default service profile settings. |
This documentation update resolves CSCvb24186.
The phone reset tips in the "Cisco Unified IP Phone Setup" chapter do not state what happens when a shared directory number is added to a phone, or when the shared directory number's settings are updated.
This statement explains this scenario:
You do not have to reset a Cisco Unified IP Phone after you add a directory number or update its settings for your changes to take effect. Cisco Unified Communications Manager automatically performs the reset. In a shared line scenario, phones that have a shared line may reset when the shared directory number is added to another phone, or when those directory number settings are updated. You may reset a Cisco Unified IP Phone at any time by using the following procedure.
This information relates to CSCul67741.
The following note appears in the Cisco Unified OS Administration user interface in the
menu and the Cisco Unified OS Administration Guide:Note | Before you can manually configure the server time, you must delete any NTP servers that you have configured. |
Because it is mandatory to have at least one NTP server, this note is inaccurate. The following is the correct note:
Note | You cannot configure time manually from the Time window, because you cannot delete all NTP servers and one NTP server is required. |
This documentation update resolves CSCup45037.
The Cisco Unified Communications Manager Administrator Guide specifies that the SIP trunk field Transmit UTF-8 for Calling Party Name uses the user locale setting of the device pool to determine what to send in the Calling Party Name field. However, the device pool does not have a user locale field. It has a network locale field, and both the Common Device Configuration record, and the Phone record itself have user locale fields.
The following is the process that the SIP trunk uses to obtain the user locale:
If the Transmit UTF-8 for Calling Party Name is checked to obtain the locale, the SIP trunk attempts to obtain the locale from the device. If that attempt fails, the SIP trunk attempts to obtain the user locale from the Common Device Configuration, and if that attempt fails, the SIP trunk obtains the user locale that is used for the Enterprise Parameters.
This documentation update resolves CSCuv67224.
In the "Remote Cluster Settings" table under topics related to advanced features, the content about the usage of the UDS check box is incorrect; even though a check box appears on the user interface under , the setting is not supported. User Data Service (UDS) is a service that is enabled by default.
This documentation update resolves CSCux00028.
The "Update LDAP Authentication " section in the Cisco Unified Communication Manager Administration Guide contains incorrect information about "LDAP Authentication". The description states that the LDAP synchronization must be disabled to make changes to the LDAP authentication settings. The correct information for "LDAP Authentication" is as follows:
LDAP synchronization must be enabled to make changes to the LDAP authentication settings.
This documentation update resolves CSCux67134.
The following is note omitted from the "Upload Certificate or Certificate Chain" chapter in the Administration Guide for Cisco Unified Communications Manager:
Note | Restart the affected service after uploading the certificate. When the server comes back up you can access the CCMAdmin or CCMUser GUI to verify your newly added certificates in use. |
This documentation update resolves CSCum94975.
The character length for the User Template Name field is incorrect in the Cisco Unified Communications Manager Bulk Administration Guide. The following table shows the correct description.
Field |
Description |
---|---|
User Template Name |
Enter a unique name, up to 132 alphanumeric characters, for the user template. |
This documentation update resolves CSCuy38765.
The following information is omitted from the "Insert EMCC Devices" procedure in the Bulk Administration Guide:
To determine how many EMCC devices to add, look at the number of registered phones and add 5% to account for devices that may not be registered at the moment. If you have 100 phones, multiply 100 by 0.5, which equals 5. You add the result (5) to the total (100). The number of EMCC devices is 105.
To display information about the number of registered phones, gateways, and media resource devices on Cisco Unified Communications Manager, open RTMT and choose Voice/Video > Device > Device Summary.
This documentation update resolves CSCvd21759.
The "Text-Based CSV Files" chapter in the Cisco Unified Communications Manager Bulk Administration Guide incorrectly state, you can create a CSV data file by using a text editor, such as Microsoft Notepad. The correct text editor to create a CSV data file is Notepad ++.
Using a text editor, such as Notepad++, you can select encoding as UTF-8 without Byte Order Mark (BOM) from the Encoding drop-down.
The Call Recording section of the CDR Examples chapter in the Cisco Unified Communications Manager Call Detail Records Administration Guide contains two call recording scenarios. However, the CDR examples that accompany the scenarios are monitoring CDRs. Following are the recording CDRs.
The customer (9728134987) calls the agent (30000), and the agent answers. The Recorder's DN is 90000. The recording feature creates two recording calls to the recording device, which results in two additional CDRs: one for the agent voice, and another for the customer voice. The origConversationID from the recording CDRs matches the destLegCallIdentifier of the recorded CDR. In this scenario, the customer hangs up.
Recording Call CDR2 |
|||
---|---|---|---|
11 |
|||
16777122 |
|||
16777123 |
|||
BIB |
|||
90000 |
|||
90000 |
|||
90000 |
|||
0 |
|||
0 |
|||
354 |
|||
354 |
|||
27 |
|||
27 |
|||
16777111 |
The agent (30000) calls the customer (9728134987), and the customer answers. The Recorder's DN is 90000. The recording feature creates two recording calls to the recording device, which results in two additional CDRs: one for the agent voice, and another for the customer voice. The origConversationID field from the recording CDRs will match the origLegCallIdentifier field of the recorded CDR. In this scenario, the agent hangs up.
Recording Call CDR 2 |
|||
---|---|---|---|
110 |
|||
16777222 |
|||
16777223 |
|||
BIB |
|||
90000 |
|||
90000 |
|||
90000 |
|||
16 |
|||
0 |
|||
354 |
|||
354 |
|||
27 |
|||
27 |
|||
16777113 |
This documentation update resolves CSCus91749.
The following information about CDR entry for FAC and CMC calls is omitted in the Forced authorization code (FAC) and Client Matter Code (CMC) topic in the Cisco Unified Communications Manager Call Detail Records Administration Guide .
Note | This call will not have any connect time since media is not connected for this call. The CDR will be logged regardless of the service parameter CdrLogCallsWithZeroDurationFlag if FAC is present in the call. |
Call from 136201 to 136111.
136111 answers and speaks for a few seconds.
136201 presses the Conference softkey and dials 136203.
The user is prompted to enter the FAC code and the user enters 124. FAC code 124 is configured as level 1 and given a name as Forward_FAC.
While 136203 is ringing, 136201 presses the Conference softkey to complete the conference.
136203 answers the call.
The three members in the conference talk for sometime.
136111 hangs up, leaving 136201 and 136203 in the conference. Since there are only two participants in the conference, the conference feature will join these two directly together and they talk for a few seconds.
FieldNames |
Orig Call CDR |
Setup Call CDR |
Conference CDR 1 |
Conference CDR 2 |
Conference CDR 3 |
Final CDR |
---|---|---|---|---|---|---|
globalCallID_callId |
60015 |
60016 |
60015 |
60015 |
60015 |
60017 |
origLegCallIdentifier |
23704372 |
23704374 |
23704373 |
23704372 |
23704376 |
23704377 |
destLegCallIdentifier |
23704373 |
23704376 |
23704381 |
23704380 |
23704382 |
23704378 |
callingPartyNumber |
136201 |
136201 |
136111 |
136201 |
136203 |
136201 |
origCalledPartyNumber |
136111 |
136203 |
b00105401002 |
b00105401002 |
b00105401002 |
136203 |
finalCalledPartyNumber |
136111 |
136203 |
b00105401002 |
b00105401002 |
b00105401002 |
136203 |
lastRedirectDn |
136111 |
136203 |
136201 |
136201 |
136201 |
136203 |
origCause_Value |
393216 |
0 |
16 |
393216 |
393216 |
0 |
dest_CauseValue |
393216 |
0 |
393216 |
393216 |
393216 |
16 |
authCodeDescription |
Forward_FAC |
|||||
authorizationLevel |
0 |
1 |
0 |
0 |
0 |
0 |
Duration |
18 |
0 |
37 |
37 |
32 |
38 |
authorizationCode |
124 |
Note | The setup call CDR for this example is generated even though it is of zero duration since FAC is used for this call. |
Call from 136201 to 136111.
136111 answers and speaks for a few seconds.
136201 presses the Conference softkey and dials 136203.
The user is prompted to enter the CMC code and the user enters 125. CMC code 125 is configured as level 1 and is given a name as Forward_CMC.
While 136203 is ringing, 136201 presses the Conference softkey to complete the conference.
136203 answers the call.
The three members in the conference talk for sometime.
136111 hangs sup, leaving 136201 and 136203 in the conference. Since there are only two participants in the conference, the conference feature will join these two directly together and they talk for a few seconds.
FieldNames |
Orig Call CDR |
Setup Call CDR |
Conference CDR 1 |
Conference CDR 2 |
Conference CDR 3 |
Final CDR |
---|---|---|---|---|---|---|
globalCallID_callId |
60025 |
60026 |
60025 |
60025 |
60025 |
60027 |
origLegCallIdentifier |
23704522 |
23704524 |
23704523 |
23704522 |
23704526 |
23704527 |
destLegCallIdentifier |
23704523 |
23704526 |
23704531 |
23704530 |
23704532 |
23704528 |
callingPartyNumber |
136201 |
136201 |
136111 |
136201 |
136203 |
136201 |
origCalledPartyNumber |
136111 |
136203 |
b00105401002 |
b00105401002 |
b00105401002 |
136203 |
finalCalledPartyNumber |
136111 |
136203 |
b00105401002 |
b00105401002 |
b00105401002 |
136203 |
lastRedirectDn |
136111 |
136203 |
136201 |
136201 |
136201 |
136203 |
origCause_Value |
393216 |
0 |
16 |
393216 |
393216 |
0 |
dest_CauseValue |
393216 |
0 |
393216 |
393216 |
393216 |
16 |
authCodeDescription |
Forward_CMC |
|
|
|||
authorizationLevel |
0 |
1 |
0 |
0 |
0 |
0 |
Duration |
20 |
0 |
32 |
32 |
25 |
48 |
authorizationCode |
125 |
Note | The setup call CDR for this example is generated even though it is of zero duration since CMC is used for this call. |
This documentation update resolves CSCun73445.
For each cluster where the publisher/subscriber node being changed is an intercluster peer, remove the publisher’s/subscriber’s cluster from the list of intercluster peers.
For example, ClusterA, ClusterB and ClusterC are all intercluster peers. You want to change the hostname on the publisher node of ClusterA. You must first remove the ClusterA publisher node from the list of intercluster peers on both ClusterB and ClusterC.
This documentation update resolves CSCvc70649.
The following information is omitted from the "IP Address and Hostname Changes" chapter in the Changing IP Address and Hostname for Cisco Unified Communications Manager and IM and Presence Service.
Changing the IP address or hostname triggers an automatic self-signed certificate regeneration. This causes all devices in the cluster to reset so that they can download an updated ITL file. If your cluster is using CA-signed certificates, you will need to have them re-signed.
This documentation update resolves CSCuw76028.
The following information is omitted from the " Domain Name and Node Name Changes" chapter in the Changing IP Address and Hostname for Cisco Unified Communications Manager and IM and Presence Service Guide.
You can use the Command Line Interface (CLI) to change the domain name for Cisco Unified Communications Manager. Update the DNS domain name on all applicable nodes using the CLI. The CLI command makes the required domain name change on the node and triggers an automatic reboot for each node.
For more information, see the " Post-Change Tasks and Verification" chapter in the Changing IP Address and Hostname for Cisco Unified Communications Manager and IM and Presence Service guide.
This documentation update resolves CSCuo56537.
Warning | FIPS 140-2 mode for IM and Presence Service is pending certification at this time and is not supported until certification is complete. |
Consider the following information before you enable or disable FIPS 140-2 mode for IM and Presence Service: After you enable or disable FIPS 140-2 mode for IM and Presence Service, the Tomcat certificate is regenerated and the node reboots. The Intercluster Sync Agent syncs the new Tomcat certificate across the cluster; this can take up to 30 minutes. Until the new Tomcat certificate is synced across the cluster, an IM and Presence Service subscriber node cannot access information from the IM and Presence Service database publisher node. For example, a user who is logged in to the Cisco Unified Serviceability GUI on a subscriber node cannot view services on the IM and Presence Service database publisher node. Users see the following error message until the synching is complete: Connection to server cannot be established (certificate exception)
This documentation update resolves CSCup03425.
The set network domain command section of the Set Commands chapter in the Command Line Interface Guide for Cisco Unified Communications Solutions contains conflicting information about manual and automatic certificate regeneration of all Cisco Unified Communications Manager certificates. At present, only automatic regeneration of certificates is supported.
The content related to manual certificate regeneration has been removed from the Usage Guidelines section. The following is the final content of the Usage Guidelines section:
The system asks whether you want to continue to execute this command.
Caution | If you continue, this command causes a temporary loss of network connectivity. |
This documentation update resolves CSCuo70238.
Note | The output that this command returns depends on the number of endpoints that is configured in the Route Groups in Cisco Unified Communications Manager. |
The utils vmtools status CLI command is no longer supported. For VMware status, check the vSphere client instead.
This documentation update resolves CSCvf93618.
The utils dbreplication clusterreset command is deprecated, instead run utils dbreplication reset command to repair replication.
admin:utils dbreplication clusterreset ******************************************************************************************** This command is deprecated, please use 'utils dbreplication reset' to repair replication! ******************************************************************************************** Executed command unsuccessfully
For more details on utils dbreplication reset command, see the "Utils Commands" chapter in the Command Line Interface Guide for Cisco Unified Communications Solutions at https://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-maintenance-guides-list.html.
This documentation update resolves CSCur93869.
The following information is missing from the "ISR-G2 Gateways" topic in the Compatibility Information for Cisco Unified Communications Manager Release 10.x.
ISR Voice gateway series (Cisco 4431 and 4451).
This documentation update resolves CSCus62385
Direct upgrade using DMA from 7.1.5 to 10.0 is not supported; therefore 6.0x, 7.0x, 8.0x, and 8.5x versions were added under the Supported section and the information was deleted from the Direct upgrade section.
This documentation update resolves CSCur96680.
The following information is omitted from the Disaster Recovery System Administration Guide.
Note | We recommend that you retest the DRS with your SFTP server after you upgrade your Unified Communications Manager, upgrade your SFTP server, or you switch to a different SFTP server. Perform this step to ensure that these components operate correctly together. As a best practice, perform a backup and restore on a standby or backup server. |
SFTP Server |
Information |
---|---|
SFTP Server on Cisco Prime Collaboration Deployment |
This server is provided and tested by Cisco, and supported by Cisco TAC. Version compatibility depends on your version of Unified Communications Manager and Cisco Prime Collaboration Deployment. See the Cisco Prime Collaboration Deployment Admin Guide before you upgrade its version (SFTP) or Unified Communications Manager to ensure that the versions are compatible. |
SFTP Server from a Technology Partner |
These servers are third party provided, third party tested, and jointly supported by TAC and the Cisco vendor. Version compatibility depends on the third party test. See the Technology Partner page if you upgrade their SFTP product and/or upgrade UCM for which versions compatible: |
SFTP Server from another Third Party |
These servers are third party provided, have limited Cisco testing, and are not officially supported by Cisco TAC. Version compatibility is on a best effort basis to establish compatible SFTP versions and Unified Communications Manager versions. For a fully tested and supported SFTP solution, use Cisco Prime Collaboration Deployment or a Technology Partner. |
This documentation update resolves CSCvd22758.
The following note is omitted from the "Add Directory Number to a Device" procedure in the Feature Configuration Guide for Cisco Unified Communications Manager.
Note | The Calling Search Space (CSS) and partition of DN are mandatory on devices. The CTI Remote Device should not block its own DN. The CSS is important for the CTIRD device to reach its own DN. |
This documentation update resolves CSCuo56960.
The following restriction is omitted from the Features and Services Guide for Cisco Unified Communications Manager:
When calling or called party transformations are applied at the gateway or route list level, the calling number in the facility information element (IE) for QSIG calls is the post-transformation number. However, the called party in the facility IE is the pre-transformation called party number.
The calling party that is sent after transformation through the gateway is typically localized and does not cause an issue with the display and routing. The called party is typically the dialed digits and is displayed on the calling phone, so the transformation is not relayed for called party transformations. Called party transformation is designed to send the information based on the gateway that the call is going through, regardless of how the number is dialed. Called party transformation is kept at the gateway level and not updated, whereas the calling party is updated.
This documentation update resolves CSCuy92491.
The following restriction is omitted from the "Call Pickup" chapter in the Feature Configuration Guide for Cisco Unified Communications Manager.
Restriction |
Description |
---|---|
Incoming Calling Party International Number Prefix - Phone |
If you have configured a prefix in the "Incoming Calling Party International Number Prefix - Phone " service parameter, and an international call is placed to a member in the Call Pickup Group, the prefix does not get invoked in the calling party field if the call gets picked up by another member of the Call Pickup Group. |
The Performance and Scalability topic in the Call Queuing chapter of the Cisco Unified Communications Manager Features and Services Guide contains a bullet that says that call queuing is not supported with broadcast algorithm hunt lists. This bullet point is incorrect and should be removed.
This documentation update resolves CSCvc37425.
The following restriction is omitted from the Cisco Unified Communications Manager Assistant Overview chapter in the Feature Configuration Guide for Cisco Unified Communications Manager:
Only one assistant at a time can assist a manager.
This documentation update resolves CSCuv22205.
The following information is omitted from the "Cisco Unified Mobility" chapter:
When an enterprise user initiates a call from a remote destination to Cisco Jabber, Cisco Unified Communications Manager tries to establish a data call with Cisco Jabber by sending an INVITE message to Cisco TelePresence Video Communication Server (VCS). The call is established regardless of receiving a response from VCS.
This documentation update resolves CSCva32400.
The "Client Matter Codes and Forced Authorization Codes" chapter mentions "Mobile phones with Cisco Jabber installed that support CMCs and FACs" as a prerequisite. This information is inaccurate.
Cisco Jabber does not support CMCs or FACs.
This documentation update resolves CSCuv41976.
The following information is omitted from the "Interactions and Restrictions" section of the Client Matter Codes (CMC) and Forced Authorization Codes (FAC) chapter:
CMCs and FACs do not support failover calls.
This documentation update resolves CSCuv84693.
The "License Usage Report" topic in the "Licensing" chapter states that "Usage information is updated once daily". This statement is incorrect.
The correct update interval for the license report (accessed through
) is once every six hours.This documentation update resolves CSCuz63406.
The "Client Matter Codes and Forced Authorization Codes" chapter states that "Mobile phones with Cisco Jabber installed support CMC and FAC." This information is inaccurate. The correct information is as follows:
Mobile phones with Cisco Jabber installed support only CMC. FACs are not supported.
The System Requirements topic in the Monitoring and Recording chapter of the Cisco Unified Communications Manager Features and Services Guide contains a list of supported gateways for recording, including the ISR-G2 Gateways (29XX, 39XX) running release 15.3(3)M. It should say that release 15.3(3)M or later are supported.
This documentation update resolves CSCuv20382.
The "Device Mobility" chapter incorrectly states to run a report in Cisco Unified Reporting to determine device support for device mobility. Because this feature is related to Unified Communications Manager and not devices, the report does not apply to device mobility.
In Cisco Unified Reporting, "Mobility" refers to WiFi connections.
This documentation update resolves CSCur73944.
The following information is omitted from the Limitations section of the "Cisco Unified Mobility" chapter in the Features and Services Guide.
When initially configured, Jabber devices count as registered devices. These devices increase the count of registered devices in a node, set by the Maximum Number of Registered Devices service parameter.
This documentation update resolves CSCum47807.
The following note is missing from "Licensing" chapter in the Features and Services Guide:
Note | MGCP FXS ports do not require any license because they are not considered to be analog phones. |
The Announcements with Music On Hold document discusses Native Call Queuing and the added capabilities that are related to customized audio announcements and Music On Hold. Access this document at the following URL:
This documentation update resolves CSCus42103.
This documentation update resolves CSCtd43582.
The following restriction is omitted from the "Cisco Mobility" chapter in the Features and Services Guide for Cisco Unified Communicatins Manager:
A remote destination call does not work when Auto Answer is enabled.
This documentation update resolves CSCuv11445.
The following information is omitted from "ILS Troubleshooting Tips" in the "Intercluster Lookup Service" chapter of the Features and Services Guide:
If you receive an error message when trying to establish ILS between your clusters, you can try to restart the Cisco Intercluster Lookup service from Cisco Unified Serviceability Administration.
This documentation update resolves CSCuq44567.
The following note is missing from the "SAML Single Sign-On" chapter in Feature and Services Guide for Cisco Unified Communications Manager.
Note | Cisco Unified Communications Manager currently supports only sAMAccountName option as the LDAP attribute for user ID settings. |
This documentation update resolves CSCut20187.
The following information is omitted from the Limitations section in the "Enhanced Location Call Admission Control" chapter:
If video capabilities are enabled, then bandwidth for audio will be allocated from video.
This documentation update resolves CSCvd10033.
The following note is omitted from the "Install a New Node in an Existing Cluster" chapter in Installation Guide for Cisco Unified Communications Manager and IM and Presence Service.
Note | You can collect the logs from RTMT of a new node added to the existing FQDN cluster, only when you restart the trace collection service. When you sign in to Unified RTMT without restarting the trace collection, the following error message is displayed: Could not connect to 'Server' <new node name>. |
This information applies to CSCug48896.
The following information applies when you install an IM and Presence Service cluster:
Warning | Do not add a node in the Cisco Unified Communications Manager server list during the installation process. |
Warning | Complete the installation of the IM and Presence Service database publisher node and confirm that services are running before you begin to install IM and Presence Service subscriber nodes. |
This documentation update resolves CSCum39340.
Applications that use JTAPI, including Unified Contact Center Express (UCCX), are unable to dial MeetMe conference numbers to begin a MeetMe conference or join an already started MeetMe conference. MeetMe is not a feature supported by JTAPI and therefor any application that uses JTAPI for call control is unable to perform actions on MeetMe conferences. For Unified Contact Center Express (UCCX), this prevents MeetMe conferences DN from being the destination of Place Call script steps.
This documentation update resolves CSCuv32781.
The following information is omitted from the "Simple Management Network Protocol" chapter in the Managed Services Guide:
Your system does not allow more than ten concurrent polling queries. We recommend a maximum of eight trap destinations; anything higher will affect CPU performance. This requirement applies to all installations regardless of the OVA template that you use.
The Cisco Unified Communications Manager Managed Service Guide contains a list of system error alarm messages that may not be up to date.
For a complete list of system error messages, see the System Error Messages document for your release at the following URL:
http://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-system-message-guides-list.htmlThis documentation update resolves CSCuu94393.
The Disaster Recovery System online help incorrectly states that you can configure up to fourteen backup devices. The correct limit is ten devices.
This documentation update resolves CSCux74230.
The Remote Destination Configuration Settings field description in the Cisco Unified CM Administration Online Help incorrectly states that you can "Enter the telephone number for the destination". The correct statement is "Enter the PSTN telephone number for the destination".
This documentation update resolves CSCvd75418.
The Time Schedule Settings topic in the "Call Routing Menu" chapter of the Cisco Unified CM Administration Online Help contains insufficient information about the selected time period for a day. The following scenario is omitted from the guide:
Field |
Description |
||
---|---|---|---|
Time Period Information |
|||
Selected Time Periods |
Scenario: If multiple time periods are associated to a time schedule and the time periods does not overlap. However, overlap in a day, then the single day period takes precedence and other time periods for that day is ignored. Example 1: Three time periods are defined in the time schedule: Range of Days: Jan 1 - Jan 31: 09:00 - 18:00 Day of Week: Mon - Fri: 00:00 - 08:30 Day of Week: Mon - Fri: 18:30 - 24:00 In this case, even though the times are not overlapping, Range of Days is ignored for a call on Wednesday at 10:00. Example 2: Three time periods are defined in the time schedule: Single Day: Jan 3 2017 (Tues): 09:00 - 18:00 Day of Week: Mon - Fri: 00:00 - 08:30 Day of Week: Mon - Fri: 18:30 - 24:00 In this case, even though the times are not overlapping, Day of Week is ignored for a call on Jan 3 at 20:00.
|
This documentation update resolves CSCvc30013.
The LDAP Authentication Settings in the System Menu chapter in Cisco Unified CM Administration Online Help contains insufficient information about LDAP User Authentication. The following note is omitted from the guide:
Note | You can do LDAP User Authentication using the IP address or the hostname. When IP address is used while configuring the LDAP Authentication, LDAP configuration needs to be made the IP address using the command utils ldap config ipaddr. When hostname is used while configuring the LDAP Authentication, DNS needs to be configured to resolve that LDAP hostname. |
This documentation update resolves CSCuy28500.
The following note is omitted from the "Directory Number Settings" topic in the online help and "User Device Profile Fields Descriptions in BAT Spreadsheet" topic in the Cisco Unified Communications Manager Bulk Administration Guide:
Note | The "Disable " or "Flash only" setting options apply only for the handset. The led light on the phone button line will still flash. |
This documentation update resolves CSCvb88447.
The Timer Information field has incorrect information in the help page. It states the time in "milliseconds", the correct time is set in "seconds".
The Timer Informationsection lists incorrect order in the help page. The correct orders of the fields are: Delay Before Ringing Timer, Answer Too Soon Timer, and Answer Too Late Timer.
This information relates to CSCul67741.
The following note appears in the Cisco Unified OS Administration user interface in the
menu and the Cisco Unified OS Administration Guide:Note | Before you can manually configure the server time, you must delete any NTP servers that you have configured. |
Because it is mandatory to have at least one NTP server, this note is inaccurate. The following is the correct note:
Note | You cannot configure time manually from the Time window, because you cannot delete all NTP servers and one NTP server is required. |
This documentation update resolves CSCut87382.
The following procedure is omitted from the "Manage Certificates" section in the "Security" chapter.:
When using a CA signed CAPF Certificate, follow these steps to add the root certificate to the CallManager trust store.
This documentation update resolves CSCuq28511.
The following note is omitted from the "Cisco Unified Analysis Management" chapter in the Cisco Unified Real-Time Monitoring Tool Administration Guide.
Caution | The Analyze Call Path Tool might not work correctly if your computer is set to a language other than English. |
This documentation update resolves CSCuq39087.
The default threshold value for LogPartitionLowWaterMarkExceeded alert is incorrectly described in the Cisco Unified Real-Time Monitoring Tool Administration Guide. The following table contains the correct value.
Value |
Default Configuration |
---|---|
Threshold |
Trigger alert when following condition met: Log Partition Used Disk Space Exceeds Low Water Mark (90%) |
This documentation update resolves CSCuz11160.
The Real-Time Monitoring Tool Guide states an incorrect minimum amount for monitoring a performance counter. This is the correct statement:
High-frequency polling rate affects the performance on the server. The minimum polling rate for monitoring a performance counter in chart view is 5 seconds; the minimum rate for monitoring a performance counter in table view is 5 seconds. The default for both specifies 10 seconds.
This documentation update resolves CSCuu72197.
The LowAvailableVirtualMemory threshold value in the Cisco Unified Real-Time Monitoring Tool Administration Guide is incorrectly listed as below 30%. The correct value is below 25%.
This documentation update resolves CSCul78860.
The table in the "End user digest credential settings" subsection of the "Digest authentication for SIP phones setup" section states that Digest Credentials accepts alphanumeric characters, which is wrong. The Digest Credentials accepts only hexadecimal characters for BAT User Template.
This documentation update resolves CSCvg10775.
The following note is omitted from the "Security Overview" chapter in Security Guide for Cisco Unified Communications Manager.
Note | The maximum supported size of certificate for DER or PEM is 4096 bits. |
If you run your system in mixed mode, some endpoints may not accept CA certificates with a key size of 4096 or longer. To use CA certificates in mixed mode, choose one of the following options:
This documentation update resolves CSCuz68165.
The following note is omitted from the "Phone Models Supporting Encrypted Configuration File" topic in the Security Guide for Cisco Unified Communications Manager.
Note | Cisco Unified IP Phones 6901 and 6911 do not request for the ITL file as they do not support security by default. Therefore, the Cisco Unified Communications Manager cluster should be set to secure (Mixed) mode for the Cisco Unified IP Phones(6901 and 6911) to get the Cisco CTL file containing Cisco Certificate Authority Proxy Function (CAPF) details for the encrypted configuration file to work on the Cisco IP Phones (6901 and 6911). |
This documentation update resolves CSCuy05368.
The following information is omitted from the "Configure VPN Feature Parameters" section of the VPN Feature Setup chapter in the Cisco Unified Communications Manager Security Guide:
When True, a user password gets saved in the phone, if Reset button or "**#**" is used for reset. The password does not get saved and the phone prompts for credentials if the phone loses power or you initiate a factory reset.
Default: False
This information applies to CSCun49156.
For IP Phones that use SSL VPN, third-party firewalls are not supported.
This documentation update resolves CSCvb44649.
The following information is omitted from the "Initial Trust List " chapter of the Security Guide for Cisco Unified Communications Manager:
If a Cisco Unified Communications Manager cluster has more than 39 certificates, then the ITL file size on Cisco Unified IP Phone exceeds 64 kilobytes. Increase in the ITL file size affects the ITL to load properly on the phone causing the phone registration to fail with Cisco Unified Communications Manager.
This documentation update resolves CSCum47807.
The following note is missing from "Licensing" chapter in the Features and Services Guide:
Note | MGCP FXS ports do not require any license because they are not considered to be analog phones. |
Note | When you upload an updated certificate with the same Common Name (CN) to Phone-VPN-trust, you overwrite the old certificate. Upload the new certificate to the subscriber instead of the publisher. Phone-VPN-trust does not replicate to other servers but this process will still add the new certificate to the database for the Phone VPN Gateway configuration. Therefore, the old certificate will not be overwritten. |
Step 1 | Install the new ASA certificate on the ASA, but do not activate it. |
Step 2 | Add the new ASA certificate to the trust store (Phone-VPN-trust). |
Step 3 | Add the new ASA certificate to VPN Gateway Configuration. Select and add the new ASA certificate to "VPN certificates in this location." |
Step 4 | Gather information about which VPN phones are registering and which VPN phones are not registering. |
Step 5 | Apply the new configuration file to the phones from the Common Phone Profile Configuration window that is used for VPN phones or from the Device Pool Configuration window that used for VPN phones. |
Step 6 | Reset the VPN phones. |
Step 7 | Ensure that
the phone received the updated configuration file or verify that the phone has the new ASA certificate hash information in its configuration file.
For more information, see https://supportforums.cisco.com/document/33891/ip-phone-ssl-vpn-asa-using-anyconnect. |
Step 8 | Activate the new ASA certificate on the ASA. |
Step 9 | Verify that the previously registered VPN phones are registering back to Unified Communications Manager. |
Step 10 | Repeat Steps 4, 5, 6, and 8. |
Step 11 | Remove the old ASA certificate from the VPN Gateway Configuration. |
This documentation update resolves CSCuq04604.
In the Cisco Unified Communications Manager Security Guide, the section about secure and nonsecure indication tones states that "Protected devices can call nonprotected devices that are either encrypted or nonencrypted. In such cases, the call specifies nonprotected and the nonsecure indication tone plays." This statement applies only if a protected phone calls a nonencrypted, nonprotected phone. If the call is encrypted for both parties, the indication tone plays the secure tone.
Protected devices that call nonprotected devices that are encrypted play the secure tone, while protected devices that call nonprotected and nonencrypted devices play the nonsecure tone.
This documentation update resolves CSCve06893.
The following note is omitted from the "Security Overview" chapter in the Cisco Unified Communications Manager Security Guide.
Note | When using Multi-server (SAN) CA-signed certificates, the Multi-server certificate is only applied to nodes in the cluster at the time the certificate is uploaded to the Publisher. Therefore, anytime a node is rebuilt or a new node is added to the cluster, it is necessary to generate a new Multi-server certificate and upload it to the cluster. |
This documentation update resolves CSCuz42447. The Call Admission Control chapter in Cisco Unified Communications Manager System Guide contains incorrect information about the Bandwidth Calculations field. This option of resync bandwidth is no longer required and the following has been omitted from the guide:
When a link to a location experiences blockage, it may result from bandwidth leakage that has reduced the usable bandwidth for the location. You can resynchronize the bandwidth allotment to the maximum setting for the location without restarting the Cisco Unified Communications Manager server. If you resynchronize the bandwidth for a location when calls are using the link, the bandwidth might be oversubscribed until all calls that are using the link disconnect. An oversubscribed link can cause audio and video quality to degrade. For this reason, resynchronize the location bandwidth during hours when the link has low traffic.
This documentation update resolves CSCup00956.
Information regarding the Cisco AXL Web Service for interclustering on IM and Presence Service was updated as follows:
If intercluster communication is configured, this service must be enabled on both nodes in the sub-cluster where remote peers are configured to sync from.
This documentation update resolves CSCup98304.
The following service is omitted from the "Services" chapter in the Cisco Unified Communications Manager Serviceability Guide and online help.
Cisco CAR DB manages the Informix instance for the CAR database, which allows Service Manager to start or stop this service and to bring up or shut down the CAR IDS instance respectively. This is similar to the Unified Communications Manager database that is used to maintain the CCM IDS instance.
The Cisco CAR DB service is activated on the publisher by default. The CAR DB instances are installed and actively run on the publisher, to maintain the CAR database. This network service is used only on the publisher and is not available on the subscribers.
This documentation update resolves CSCup84785.
The following content is omitted from the Platform Services section of the "Services" chapter in the Cisco Unified Serviceability Administration Guide:
This service keeps certificates of components like Tomcat, CallManager, and XMPP automatically synchronized across all nodes in the cluster. When the service is stopped and you regenerate certificates, you have manually upload them to Certificate Trust on the other nodes.
This documentation update resolves CSCur03499.
The Service groups and CM Services sections in Cisco Unified Serviceability Administration Guide mention Cisco IP Phone Service. This service has been removed from CM Services as IP Phone services is offered through the User Data Services (UDS) component starting Cisco Unified Communications Manager, Release 10.0(1).
This documentation update resolves CSCup98302.
The following service is omitted from the "Services" chapter in the Cisco Unified Communications Manager Serviceability Guide and online help.
The Cisco SOAP-CallRecord service runs by default on the publisher as a SOAP server, so that the client can connect to CAR database through the SOAP API. This connection happens through the use of the CAR connector (with a separate CAR IDS instance).
This documentation update resolves CSCuv32781.
The following information is omitted from the "Set up SNMP" procedure in the "Simple Management Network Protocol" chapter in the Serviceability Administration Guide:
Your system does not allow more than ten concurrent polling queries. We recommend a maximum of eight trap destinations; anything higher will affect CPU performance. This requirement applies to all installations regardless of the OVA template that you use.
This documentation update resolves CSCuz69271. The following note is omitted from the "Services" chapter in Cisco Unified Serviceability Administration Guide.
Devices using IM and Presence are configured to use a Postgres external database to support persistent chat, compliance, and file transfer. However, the connection between IM and Presence server and Postgres is not secured and the data passes without any check. For the services or devices that do not support TLS, there is another way to provide secure communication by configuring IP Sec, which is a standard protocol for secure communications by authenticating and encrypting each IP packet of a communication session.
This documentation update resolves CSCuq22399.
The following service is omitted from the "Services" chapter in the Cisco Unified Communications Manager Serviceability Guide and online help.
The Cisco Unified Real-Time Monitoring Tool (RTMT) uses the SOAP-Diagnostic Portal Database Service to access the RTMT Analysis Manager hosting database. RTMT gathers call records based on operator-defined filter selections. If this service is stopped, RTMT cannot collect the call records from the database.
This documentation update resolves CSCux59529.
The "CISCO-SYSLOG-MIB Trap Parameters" topic incorrectly lists the command for "Set clogMaxSeverity" as snmpset -c public -v2c 1<transmitter ipaddress> 1.3.6.1.4.1.9.9.41.1.1.3.0 i <value>.
The correct command is snmpset -c public -v2c <transmitter ipaddress> 1.3.6.1.4.1.9.9.41.1.1.3.0 i <value>.
This documentation update resolves CSCve84930.
The following information is added under "Alarms" chapter in the Cisco Unified Serviceability Administration Guide.
Name |
Description |
---|---|
CLM_IPSecCertUpdated |
The IPSec self-signed cert from a peer node in the cluster has been imported due to a change. |
CLM_IPAddressChange |
The IP address of a peer node in the cluster has changed. |
CLM_PeerState |
The ClusterMgr session state with another node in the cluster has changed to the current state. |
CLM_MsgIntChkError |
ClusterMgr has received a message which has failed a message integrity check. This can be an indication that another node in the cluster is configured with the wrong security password. |
CLM_UnrecognizedHost |
ClusterMgr has received a message from an IP address which is not configured as a node in this cluster. |
CLM_ConnectivityTest |
Cluster Manager detected a network error. |
ServiceActivated |
This service is now activated. |
ServiceDeactivated |
This service is now deactivated. |
ServiceActivationFailed |
Failed to activate this service. |
ServiceDeactivationFailed |
Failed to deactivate this service. |
ServiceFailed |
The Service has terminated abruptly. Service Manager will try to restart it. |
ServiceStartFailed |
Failed to start this service. Service Manager will attempt to start the service again. |
ServiceStopFailed |
Unable to stop the specified service after serveral retries. The service will be marked stopped. |
ServiceRestartFailed |
Unable to restart the specified service. |
ServiceExceededMaxRestarts |
Service failed to start, even after the max restarts attempts. |
FailedToReadConfig |
Failed to read configuration file. Configuration file might be corrupted. |
MemAllocFailed |
Failure to allocate memory. |
SystemResourceError |
System call failed. |
ServiceManagerUnexpectedShutdown |
Service Manager restarted successfully after an unexpected termination. |
OutOfMemory |
The process has requested memory from the operating system, and there was not enough memory available. |
CREATE-DST-RULE-FILE-CLI |
New DST rules file is generated from cli. Phones need to be restarted.Not restarting the phones would result in wrong DST start / stop dates. |
CREATE-DST-RULE-FILE-BOOTUP |
New DST rules file is generated during bootup. Phones need to be restarted.Not restarting the phones would result in wrong DST start / stop dates. |
CREATE-DST-RULE-FILE-CRON |
New DST rules file is generated from cron. Phones need to be restarted.Not restarting the phones would result in wrong DST start / stop dates. |
PermissionDenied |
An operation could not be completed because the process did not have authority to perform it. |
ServiceNotInstalled |
An executable is trying to start but cannot because it is not configured as a service in the service control manager. The service name is %s. |
ServiceStopped |
A service has stopped. |
ServiceStarted |
A service has started. |
ServiceStartupFailed |
A service has started. |
FileWriteError |
Failed to write into the primary file path. |
This documentation update resolves CSCuz42436. The Call Admission Control chapter in Cisco Unified Communications Manager System Guide contains incorrect information about the Bandwidth Calculations field. It is mentioned that the iLBC call uses 24 kb/s. The correct bandwidth consumption at 20ms should be 31.2kb/s.
This documentation update resolves CSCuw57732.
The following information is omitted from the "Phone Features" section in "Cisco Unified IP phones" chapter:
If a call transfer to a hunt pilot is initiated when an announcement is in progress, the call is redirected only after the announcement is complete.
This documentation update resolves CSCve02996.
The following information is omitted from the "Cisco Unified Communications Manager TCP and UDP Port Usage" chapter of the System Configuration Guide for Cisco Unified Communications Manager.
From (Sender) |
To (Listener) |
Destination Port |
Purpose |
---|---|---|---|
Endpoint |
Unified Communications Manager |
443, 8443 / TCP |
Used for Cisco User Data Services (UDS) requests |
This documentation update resolves CSCvd37400.
The following note is omitted from the "Configure Conference Bridges" chapter in the Cisco Unified Communications Manager System Guide.
Note | When Cisco Unified Communications Manager server is created, the Conference Bridge Software is also created automatically and it cannot be deleted. You cannot add Conference Bridge Software to Cisco Unified Communications Manager Administration. |
This documentation update resolves CSCur55902.
The following information is omitted from the "Directory Overview" in the Cisco Unified Communications Manager System Guide.
Note | For the users that must be synchronized to the Cisco Unified Communications Manager database, their email ID fields on the active directory server must be unique or blank. |
The "Configure LDAP Directory" topic in the Cisco Unified Communications Manager System Guide, Release 10.0(1) contains a list of supported LDAP directories. However, this list should include Microsoft Active Directory 2012 and Microsoft Lightweight Directory Services 2012 R1/R2.
This documentation update resolves CSCvc16660.
Restriction |
Description |
---|---|
Ringback tone restriction for Cisco Video Communications Server (VCS) registered to third-party SIP Endpoints |
Blind transfer or switch to request the transfer which occurs over VCS registered endpoints with Cisco Unified Communications Manager will not have a ringback tone. If you do a supervised transfer, then you allocate Music On Hold (MOH) but, not a ringback tone. |
This documentation update resolves CSCva13963.
The following information is omitted from the "Configure Time of Day Routing" topic in the System Configuration Guide for Cisco Unified Communications Manager.
Time of Day routing is not implemented for Message Waiting Indicator intercept.
This documentation update resolves CSCuy48640.
The "Common Service Ports" table incorrectly describes ILS as Intracluster Lookup Service. The following table contains the correct name.
From (Sender) |
To (Listener) |
Destination Port |
Purpose |
---|---|---|---|
Unified Communications Manager |
Unified Communications Manager |
7501 |
Used by Intercluster Lookup Service (ILS) for certificate based authentication. |
This documentation update resolves CSCus05634.
From (Sender) |
To (Listener) |
Destination Port |
Purpose |
---|---|---|---|
Unified Communications Manager Publisher |
Unified Communications Manager Subscriber |
22 / TCP |
Cisco SFTP service. You must open this port when installing a new subscriber. |
This documentation update resolves CSCus26925.
From (Sender) |
To (Listener) |
Destination Port |
Purpose |
---|---|---|---|
Unified Communications Manager |
Cisco License Manager |
5555 / TCP |
Cisco License Manager listens for license requests on this port |
This documentation update resolves CSCuy48628.
From (Sender) |
To (Listener) |
Destination Port |
Purpose |
---|---|---|---|
ILS Service Port |
|
8006 / TCP |
|
This documentation update resolves CSCus37007.
For Cisco Unified Communications Manager 9.0(1) and later releases, choose Detailed as Default trace level. For earlier releases, choose Error.
This document update resolves CSCuq07331.
The following information is omitted from the "Preupgrade Tasks" chapter in the Upgrade Guide for
It is recommended that you disable or postpone the LDAP synchronization on Unified Communications Manager during an upgrade. If the synchronization is scheduled in for a time period which falls after the Unified Communications Manager upgrade and before the IM and Presence Service upgrade, then the result can negatively affect the IM and Presence Service if user changes occurred in this timeframe.
This documentation update resolves CSCup31306.
In the Change Virtual Machine Configuration Specifications procedure, Step 6 ("Shut down the virtual machine") should be performed before Step 3 ("Change the configuration of the virtual machine").
The application user group roles InterCluster Peer-User and Admin-CUMA are deprecated from release 10.0(1). Any application users with these roles configured in releases 8.x or 9.x have the roles removed during an upgrade to any 10.x release. After the upgrade the administrator must configure appropriate roles for these users.
Note | For intercluster to function correctly, the AXL user defined on the IM and Presence Service user interface ( ) must have a Standard AXL API Access role associated with it on the Cisco Unified Communications Manager application user page. |
This documentation update resolves CSCuy96037.
The following information is omitted from the "Chat Node Alias Management" topic in the Configuration and Administration of IM and Presence Service on Cisco Unified Communications Manager guide.
To ensure that the user has access to all the old chat rooms, take a backup of all the existing aliases before deleting a node and assign the same alias to a new node.