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.

When sizing your deployment, keep these guidelines in mind around OVA requirements:

• For multi-cluster deployments, we recommend that you deploy a minimum OVA of 15,000 users

• For Persistent Chat deployments, we recommend that you deploy a minimum OVA of 15,000 users

• For Centralized deployments, we recommend a minimum OVA of 25,000 users

Note

If you plan to enable Multiple Device Messaging, measure deployments by the number of clients instead of by the number of users as each user may have multiple Jabber clients. For example, if you have 25,000 users, and each user has two Jabber clients, your deployment must have the capacity of 50,000 users.

Note that if you edit the setting of the SDL Listening Port service parameter, you must restart the Cisco CTIManager service on all cluster nodes where the service is running. Currently, the help text says to restart the service, but does not specify that you must restart the service on all nodes where the service is running. You can access this service parameter from Cisco Unified CM Administration by going to System > Service Parameters, selecting Cisco CTIManager as the service, and clicking Advanced to see a complete list of CTIManager service parameters.

This update is a part of CSCvp56764.

If you run Cisco TelePresence Management Suite (TMS) for scheduling, then the node that you add it to sends multiple AXL queries to fetch endpoint information. Because of the load that TMS generates, we recommend that you do not configure other applications that use AXL (such as Cisco Emergency Responder or Cisco Unified Attendant Console) to send AXL requests to these nodes.

This information applies to CSCva12833.

Cisco Unified Attendant Console Releases 11.x and earlier are not compatible with Cisco Unified Communications Manager Release 11.5(1). You must install or upgrade to Cisco Unified Attendant Console Advanced Release 11.0.1.

See here for more information.

To interoperate Cisco Unified IM and Presence Service Release 11.5(1) and Expressway-C, you must be running a minimum version of Expressway-C X8.8. IM and Presence Service 11.5(1) does not support earlier versions of Expressway-C.

If you are upgrading from an earlier release where you are already interoperating with Expressway-C, upgrade your Expressway-C system to X8.8. After upgrading Expressway-C, you can upgrade your IM and Presence Service.

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.

Cisco Unified Presence 8.6 is not supported as an intercluster peer for Cisco Unified IM and Presence Service 11.x. For information on supported intercluster peer configurations, see the Compatibility Matrix for Cisco Unified Communications Manager and IM and Presence Service at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/compat/11_x/cucm_b_cucm-imp-compatibility-matrix-11x.html#CUP0_RF_I0092C6B_00.

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.

If you have Persistent Chat configured with Microsoft SQL Server as the external database, chat messages where the total message body (HTML tags + text message) exceeds 4000 characters are rejected and are not delivered. See CSCvd89705 for additional detail. This issue exists from Release 11.5(1)SU3 onward.

If the Cisco Unified Communications Manager and IM and Presence Service publisher nodes are both unavailable, such as may occur in a UCS server crash, do not restart any IM and Presence Service subscriber nodes as the subscriber node may not recover, and Jabber users may not be able to log in, thereby requiring a rebuild of the IM and Presence cluster.

Make sure to get the Cisco Unified Communications Manager and IM and Presence Service publisher nodes up and running before you restart any IM and Presence subscriber nodes.

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.

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.