6900 Series Phones Fail to Connect When Accessing Personal or Corporate Directories
This information applies to CSCus28530.
6900 series phones may show a connection failed error message when they try to access personal or corporate directories. If you encounter this issue, use the workaround as described here.
Alternatively, you can use the following Cisco Options Package (COP) file: ciscocm.enable_sslv3-v1.0.cop.sgn. To obtain the file from https://software.cisco.com/download/navigator.html, navigate to Downloads > Home > Products > Unified Communications > Call Control > Unified Communications Manager (CallManager) > Unified Communications Manager Version 10.5 > Unified Communications Manager / CallManager / Cisco Unity COnnection Utilities - COP Files.
The COP file workaround affects your system security.
DTMF Mid-call Features Not Supported for Mobility-enabled Users
For end users who have mobility enabled,
DTMF-based mid-call features (for example, *81 - Hold, *83 -
Resume) are not supported, regardless of the DTMF Signaling
Method setting for the SIP trunk. This issue is present for all
SIP trunks due to issues with SIP signaling and MTP allocation.
There is no workaround.
For additional details, refer to CSCuu34247,
CSCuw95203 and CSCuw95309.
DTMF for User Control Voicemail
avoidance and for navigating IVRs at the far-end are both
Jabber Mobile DVOR and EFA Calls to Voicemail Pilot
When a Jabber mobile device places a Dial via
Office Reverse (DVOR) or Enterprise Feature Access (EFA) call to a
Unity Connection voicemail pilot, the call gets routed to an auto-attendant,
rather than directly to their voicemail box. The caller must enter
both the mailbox number and PIN to access messages.
This issue exists because when a mobile device
sends the Jabber call to Cisco Unified Communications Manager in
cellular mode, Cisco Unified Communications Manager does not
forward the original calling party number to the voicemail system,
regardless of any SIP redirects or diversion header settings for the SIP Trunk. As a result, the caller gets treated as an
external caller rather than a user calling their own mailbox to
Jabber users who want to use DVOR or EFA to
call their voicemail can use the following workarounds:
Use Jabber visual voicemail to retrieve
Use the cellular interface to retrieve
messages rather than Jabber
Administrators can configure the following
workaround on behalf of Jabber users:
Configure the voicemail pilot number in the
Emergency Number field of the Jabber client. This forces the call
to take place over the cellular interface, even if it is called from
For additional details, see
Media Sense does not record the Consult Call with Selective Recording
When Selective Recording is configured, the Media Sense server does not record the consult call during a transfer. For example, if a call between an agent and a customer is being recorded, and the agent initiates a transfer to another agent, the consult call that takes place between the two agents, prior to the call being transferred, is not recorded.
To ensure that the consult call is recorded, the agent must press the ‘Record’ softkey when the consult call starts.
Interoperability with Cisco TelePresence Management Suite
To interoperate Cisco Unified Communications Manager 11.0(1) with Cisco TelePresence Management Suite, you must run a minimum of Cisco TelePresence Management Suite 14.6.2.
Intercluster Peering Not Supported with Cisco Unified Presence 8.6
When Cisco Unified Communications Manager is operating in FIPS mode, SNMP v3 is not supported with MD5 and DES. To configure SNMP v3 while operating in FIPS mode, you must configure SHA as the authentication protocol and AES 128 as the privacy protocol.
Tomcat Certificate Regeneration with SAML SSO Deployment
If you regenerate Tomcat certificates within a SAML SSO Deployment, you must also generate a new metadata file in Cisco Unified Communications Manager and upload that metadata file to the IdP.
Bandwidth Allocations for 88xx SIP Phones
If you are deploying 88xx phones with the SIP protocol, note that these phones will use more bandwidth than the recommended 32 kbps while registering to Cisco Unified Communications Manager. Make sure to take account for the higher bandwidth requirement over registration when you configure your QoS bandwidth allocation in the APIC-EM Controller.
Change Perfmon Counter File Size Parameters in RTMT
If you have started logging perfmon counter data in RTMT and you want to change the file size and maximum number of files, you must first stop counter logging. After you stop the perfmon counters, you can make your changes and then restart perform counters.
Cisco Unified IP
Phones 7940 and 7960 Do Not Support Java Midlets
This information applies to CSCtn79567.
Cisco Unified IP
Phones 7940 and 7960 do not support Cisco-signed Java Midlets, but they can
parse the service information from the phone configuration file.
This information resolves CSCuu66150.
An ad hoc group chat room is created when a user starts a group chat session. By default such rooms are open rooms. This means a user who has signed in using a third-party XMPP client such as Psi or Pidgin, can discover and join the room and view its chat history. This is only possible through third-party clients because Jabber does not allow room discovery.
Carry out the following steps to work around this problem:
From Cisco Unified CM IM and Presence Administration, click Messaging > Group Chat and Persistent Chat.
In the Member Settings pane, check the following check boxes:
Rooms are for members only by default
Room owners can change whether or not only moderators can invite people to members-only rooms
Uncheck all of the remaining check boxes in the Member Settings pane.
Using this configuration a user who has not been invited to the chat session can discover a room but cannot join it. This solves the problem by making the room a member-only (restricted) room. This configuration also means that participants in the chat session can still invite other users to it so the user experience is not affected.
Other effects of these settings:
All new ad hoc and persistent rooms are created as members-only.
If the Cisco XCP Text Conference service is restarted, the existing public rooms become members-only.
It is not possible for the room moderator or owner to make a new room public.
Any member of a members-only room can invite another user to be a member of the room. By default, only the room moderator or owner can invite other users.
On Jabber-only deployments, this capability is limited to the room moderator or owner. This is because Jabber does not provide the option for room members to invite other users to a members-only room in its user interface.
MGCP IOS Gateway
From PSTN Does Not Support Connected Address in ISDN Notify
This information applies to CSCut08346.
The calling-line ID (CLID) information is not displayed through Media
Gateway Control Protocol (MGCP) IOS gateway after the call is transferred since
it does not support Connected Address in ISDN NOTIFY.
Secrecy is not Supported in IPsec Configuration
This information applies to CSCuu74346.
Perfect Forward Secrecy (PFS) security service is not supported in
IPsec configuration between Cisco Unified Communications Manager and Voice
Route Filter and Associated Route Patterns
When configuring your call routing, make sure that you don't assign a single route filter to too many route patterns. A system core could result if you were to edit a route filter that has hundreds of associated route patterns, due to the extra system processing that is required to update call routing for all of the route patterns that use the route filter. Create duplicate route filters to ensure that this does not occur. For more information see CSCup04938.
TFTP File Size Limit
This information addresses CSCuw28887.
You cannot upload files over 250 MB using TFTP file management in the OS Administration interface. If you try, the upload process times out.
To upload files above 250 MB, please work with the Cisco Technical Assistance Center (TAC).
IM and Presence
Service Persistent Chat Failover Behavior
applies to CSCuv40273.
In the event of an
IM and Presence Service publisher node failover, the persistent chat rooms
created on the database assigned to the failed IM and Presence Service
subscriber node are not accessible.
This limitation is
being addressed by enhancement request CSCuv81931.
IM and Presence
Service TSnames File Contains Incorrect Details Following Hostname or IP
This information applies to CSCux11567.
Use this procedure after you have changed the hostname or IP address
on an IM and Presence Service Publisher node, if the
tsnames file on the Publisher node contains incorrect
details about the updated hostname or IP address.
Cisco Unified CM IM and Presence
Messaging > External
Server Setup > External
Find to list all the External Databases.
Click the External Database connected to the Publisher node and
take note of the connection details on the
External Database Settings window.
To add the database click
Add New and enter the details saved from step
Persistent Chat Rooms Using Oracle External Database on IM and Presence Service
This information applies to
On IM and Presence Service, persistent chat rooms do not work if you are using an Oracle external database and it has not been updated with the patch for the Oracle defect: ORA-22275.
If the patch has not been updated, the following problem occurs in Jabber. When you create a persistent chat room and you do not check the Add Room to My Rooms Tab check box, the room does not appear under the All Rooms tab.
When you restart the Cisco XCP Text Conference Manager service, Jabber gives the following message: Room has been deleted. You then have to recreate the persistent chat room after every Cisco XCP Text Conference Manager service restart.
IM and Presence Server Pings to Jabber Are Not Configurable
IM and Presence server updates the presence status of the user as Unavailable if it does not receive a keep-alive from the client after two 1-minute pings.
The timings for these pings are hard-coded on the server side and are not configurable.