Administration Guide
Cisco Unified IP Phone setup Description Character Length
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
with 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 (<>). |
Correction in IPv6 Address Field
This documentation update resolves CSCun07023.
Field |
Description |
||||
---|---|---|---|---|---|
IPv6 Address (for dualIPv4/IPv6) |
This field supports IPv6. If your network uses DNS that can map to IPv6 addresses, you can enter the hostname of the Cisco Unified Communications Manager server. Otherwise, enter the non-link-local IP address of the Cisco Unified Communications Manager server; for information on how to obtain the non-link local IP address, see the Cisco Unified Communications Manager Features and Services Guide.
|
Correction in Software Conference Bridge Maximum Audio Streams
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.
DHCP Subnet Setup Tips
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.
Directory Number Field Description Updated
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.
Directory Number Line Behavior in Cisco Unified Communications Manager
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.Disable Early Media on 180 Correction
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.
Extension Mobility Now Supports Device Owners
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.
Forbidden String When Configuring Directory Number Alert Names
This documentation update resolves CSCuv58163.
The following information is omitted from "Directory Number Settings" under topics related to Call Routing.
Caution |
Do not use the "Alert(" string anywhere in your Alerting Name or ASCII Alerting Name. Use of "Alert(" returns a security protocol error. |
Hostname and IP Address Field Can Contain a Fully Qualified Domain Name
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. |
Hostnames in IPv4 and IPv6 Environments
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.
Hub_None Location Correction
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.
ILS Data Sync to be Delayed Until after DB Replication is Completed
This documentation update resolves CSCuh55365.
The following note is omitted from the Directory number settings table in the Cisco Unified Communications Manager Administration Guide and from the Learned Global Dial Plan Data section in the Cisco Unified Communications Manager Features and Services Guide.
Note |
Cisco Unified Communications Manager pauses the recording of learned ILS patterns until replication of cluster is successfully established. |
ILS Restictions for Directory URIs
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.
Incorrect External Call Control Profile Field Description
This documentation update resolves CSCun07467.
The External Call Control Profile field is incorrectly described in the Cisco Unified Communications Manager Administration Guide. The following table contains the correct description.
Field | Description |
---|---|
Directory Number Information |
|
External Call Control Profile |
In Cisco Unified Communications Manager, you enable external call control by assigning an external call control profile to a directory number. If the directory number has an external call control profile assigned to it, and when a call occurs that matches the directory number, Cisco Unified Communications Manager immediately sends a call-routing query to an adjunct route server, and the adjunct route server directs Cisco Unified Communications Manager on how to handle the call. For more information about external call control, see topics related to external call control in the Cisco Unified Communications Manager Features and Services Guide. From the drop-down list box, choose the external call profile that you want to assign to the directory number. |
Incorrect Information about Deleting Route Patterns
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.
Incorrect Note about User Locales
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. |
Incorrect Time Period Example
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.
Insufficient Information about Call Control Agent Profile Fields
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.
The following table describes the Call Control Agent Profile settings.
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 (@). |
Line Group Deletion Correction
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. |
Location Menu Path
In the Administration Guideand online help, the Location field for H.225 and Intercluster Trunk Settings references the
menu. The correct menu path is .Maximum Hunt Timer Restriction
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. |
Missing Information for Allow Multiple Codecs in Answer SDP
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:
-
Third-party SIP endpoints that support this capability
-
SIP trunks to third-party call controls servers that uniformly support this capability for all endpoints
Do not configure this capability for SIP intercluster trunks to Cisco SME or other Cisco Unified Communications Manager systems.
Phone Support for Multilevel Precedence and Preemption
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.
Remove Resource Priority Namespace List Field from SIP Profile Settings
This documentation update resolves CSCun32999.
The Resource Priority Namespace List field under is listed in the Cisco Unified Communications Manager Administration Guide and online help, but has been removed from the SIP Profile Configuration window in Cisco Unified CM Administration.
Self-Provisioning Application Requires Phone Model with Security By Default
This documentation update resolves CSCun13382.
The following note is omitted from the "Self-Provisioning" chapter in the Cisco Unified Communications Manager Administration Guide.
Note |
Phone models (such as Cisco IP Phone 7940 and 7960; IP Communicator series) that do not support the Security By Default (SBD) feature cannot use the Self-Provisioning service. This is because the self-provisioning feature that runs as an Idle URL supports HTTPS certificates only. These phones cannot verify the HTTPS certificates because they do not support the Trust Verification Service (TVS) functionality of the SBD feature. However, these phones can still use the Self-Provisioning IVR service, provided that the phones themselves support the Self-Provisioning application. |
Service Profiles and Device Owner User IDs
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. |
SIP Trunk Fields SIP Trunk Status and SIPTrunk Duration
This documentation update resolves CSCun07961.
Field |
Description |
---|---|
SIP Trunk status as determined by SIP OPTIONS Ping |
|
Full Service status (alarm—SIPTrunkISV) status |
All the remote peers that are destinations of the SIP trunk are available. New call requests can be sent to any remote peer through the SIP trunk. |
No Service status (alarm—SIPTrunk OOS) |
All the remote peers that are destinations of the SIP trunk are unavailable. New call requests cannot be sent out via the SIP trunk. |
Partial Service status (alarm—SIPTrunkPartiallyISV) |
At least one remote peer is in service, but not all of the remote peers that are destinations of the SIP trunk are available. New call requests can be sent to an available remote peer through the SIP trunk. |
Unknown—OPTIONS Ping not enabled |
The SIP trunk status is unknown when SIP OPTIONS Ping is not enabled. |
Synchronize Trunks and Gatekeeper Sections Are Not Valid
This documentation update resolves CSCuq05944.
-
"Synchronize Trunk" section is removed from the "Trunk Setup" chapter
-
"Synchronize Gatekeeper" section is removed from the "Gatekeeper Setup" chapter
Transmit UTF8 for Calling Party Name Field Correction
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.
Insufficient Information About Automatic Fallback
This documentation update resolves CSCuz01075. The Deployment models chapter in Configuration and Administration of IM and Presence Service on Cisco Unified Communications Manager contains insufficient information about the Automatic Fallback field. The following has been omitted from the guide.
-
A critical service on Node A fails—A critical service (for example, the Presence Engine) fails on Node A. Automatic failover occurs and all users are moved to Node B. Node A is in a state called “Failed Over with Critical Services Not Running”. When the critical service recovers, the node state changes to "Failed Over." When this occurs Node B tracks the health of Node A for 30 minutes. If no heartbeat is missed in this timeframe and the state of each node remains unchanged, automatic fallback occurs.
-
Node A is rebooted—Automatic failover occurs and all users are moved to Node B. When Node A returns to a healthy state and remains in that state for 30 minutes automatic fallback will occur.
-
Node A loses communications with Node B—Automatic failover occurs and all users are moved to Node B. When communications are re-established and remain unchanged for 30 minutes automatic fallback will occur.
UDS in Remote Cluster Service Configuration is Not Supported
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.
A Server Restart is Required After Uploading a Certificate
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. |
LDAP Authentication Correction
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.
Authenticate with Multiple LDAP Domains
This documentation update resolves CSCuy37309.
Note |
When you are using the sAMAccountName value for the LDAP Attribute for User ID field, you can only authenticate with one LDAP Domain. To authenticate with multiple domains, you need to use the Active Directory Lightweight Directory Service (AD LDS). |
Field |
Description |
||
---|---|---|---|
LDAP User Search Base |
Enter the location (up to 256 characters) where all LDAP users exist. This location acts as a container or a directory. This information varies depending on customer setup.
|
Certificate Monitor Frequency Interval
This documentation update resolves CSCvc32210.
The following note is omitted from the "Monitor Certificate Expiration" procedure in the Administration Guide for Cisco Unified Communications Manager.
Note |
The certificate monitor service runs every 24 hours by default. When you restart the certificate monitor service, it starts the service and then calculates the next schedule to run only after 24 hours. The interval does not change even when the certificate is close to the expiry date of seven days. It runs every 1 hour when the certificate either has expired or is going to expire in one day. |