Unsupported Languages for Chat Transcript Download

The default language of the chat transcript PDF is English for customers whose languages (locales) are not supported by SocialMiner. The chat transcript PDF supports all languages that SocialMiner supports except for the following:

• Chinese Simplified (zh_CN)

• Chinese Traditional (zh_TW)

• Japanese (ja_JP)

• Korean (ko_KR)

If you type in any of the unsupported languages, the PDF will have a blank line in place of the line that is in the unsupported language.

Unsupported Options on Finesse for Direct Preview Outbound

Finesse does not support Skip, Skip-Next, Skip-Close, Reject, Cancel Reservation, and Do Not Call for direct preview outbound calls.

Unsupported and Supported Features and Configurations for Progressive and Predictive Agent Outbound

Unsupported Features and Configurations for Progressive and Predictive Agent Outbound

• The "Get Reporting Statistic" step is not supported for progressive and predictive agent-based outbound campaigns.

• Unified CCX does not support the translation or modification of the phone number that it uses to dial outbound calls. If any "voice translation rules" that are configured in the gateway modify the phone number, those rules are not supported.

  Note	You can use either of the following two supported methods to modify a dialed number in the gateway:

  • To remove the initial digits of the phone number, use forward-digits or digit-strip in the dial-peer configuration.

  • To add a prefix to the phone number, use prefix in the dial-peer configuration.

• For Outbound campaigns outside North America, additional configuration is required to add the area-code-to-time-zone mapping. For more information, see the Cisco Unified Contact Center Express Administration Guide, located at http://www.cisco.com/en/US/products/sw/custcosw/ps1846/products_installation_and_configuration_guides_list.html.

• For multi-country Outbound campaigns, the area code must also include the country code.

• Unified CCX dialer will dial outbound contacts only if the publisher database is in the IN SERVICE state.

• Finesse does not support the Do Not Call option.

• Outbound license usage is not captured in the License Utilization Cisco Unified Intelligence Center report.

• You must enable Agent AutoAnswer manually for agent-based progressive and predictive calls when you upgrade from an older Unified CCX release.

Supported Features and Configurations for Progressive and Predictive Agent Outbound

• CUBE is supported with the SIP Outbound Dialer and CPA . For more information , see the Compatibility Matrix for Unified CCX, located at: http://docwiki.cisco.com/wiki/Compatibility_Matrix_for_Unified_CCX.

Unsupported Configuration for IPv6

• Cisco Unified Communications Manager does not support SIP IPv6 signaling over UDP where the maximum transmission unit (MTU) is greater than 1500. To ensure that you do not experience intermittent call failure, change the transport protocol to TCP.

  For more information, see the "Important Notes" section of the Release Notes for Cisco Unified Communications Manager, located at:

  http://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-release-notes-list.html

  Also, see "CSCuo71306" for details on this limitation.

• When using IPv6 and Outbound dialer, use a voice gateway IOS that contains the fix for "CSCul43754".

Unsupported Configurations and Scenarios for Unified CCX

Unified CCX does not support the following configurations:

• CTI route points with directory numbers (DNs) that are members of line groups and, by extension, that are members of hunt lists of Unified CM.

• Shared lines for CTI ports and CTI route points.

• Shared non-IPCC extensions with any other Directory Number, irrespective of the configured partition.

• The directory number configured for the ICD line of the agent device, cannot be shared with any other devices irrespective of the configured partition.

• Expansion servers, except for Automatic Speech Recognition (ASR), Text-To-Speech (TTS), SocialMiner, and MediaSense, which must be separate, dedicated servers.

• ICD call answer or ICD call transfer using any third-party attendant console desk software.

• Within the same script, using the "Place Call" step to generate a call and then placing the call in a queue.

• SIP REFER between a switchboard and Unified CCX if the transfer is completed after the call is answered on the Unified CCX CTI port because of media reestablishment issues.

• During TTS prompt playback, if the call is put on hold and then retrieved, the prompt does not continue from the position at which it was left.

• Use of "Consult Transfer" or "Redirect" step from scripts to a translation pattern that maps back to a route point.

• Use of "Consult Transfer", "Redirect", and "Place Call" steps to invoke or dial into "MeetMe" conferences.

• The following scenarios have issues:

  • External -> Redirect to Unmonitored device -> Call Forward No Answer (CFNA) to UCCX RP

    Use of Redirect Step to an unmonitored device which then uses CFNA to a UCCX route point.

  • External -> Consult Transfer to RP ->Consult Transfer to RP -> Redirect to Unmonitored device

  • External -> Redirect to RP -> Consult Transfer to RP -> Redirect to Unmonitored device

  • External -> Consult Transfer to RP -> Redirect to RP -> Redirect to Unmonitored device

  • External -> Consult Transfer to RP -> Redirect to Unmonitored device

    Thus, use the Call Redirect Step in the script instead of Call Consult Transfer.

• Unified CCX doesn't completely support E.164 numbering plan for route point directory numbers (DN).

  This limitation is because of the Unified CM limit on device name length set as 15 characters. We add "_" between the device name prefix and the DN. So we support a maximum of 13 characters in the DN as device name prefix is mandatory and hence at least one character is needed there. For example, (Device name prefix) + '_' + (length of DN) = 15 ==> [(1 + '_' + 13) = 15].

• Cisco Unified CCX system does not support modification, addition or deletion of the CTI ports and the CTI Route Points from the Cisco Unified Communication Manager. Performing the same can lead to issues with non-contiguous DN range for which Cisco Tomcat on Unified CCX Server needs to be restarted.

• A discrepancy in reports is observed when a call is transferred using Cisco Jabber by multiple agents in the same call flow. Use the Cisco Finesse desktop to transfer calls.

• SIP URI dialing for CTI route points, CTI ports, and agent extensions.

• Mid Call Caller ID updates when call is routed to Unified CM via MGCP gateway.

  Note	When incoming calls are routed to Unified CM via MGCP gateway, any mid call caller ID updates are reflected only after the call is connected.

Unsupported Actions for Unified CCX Agents

Use of the following softkeys on a Cisco Unified IP Phone is not supported:

• Barge

• cBarge

• DND

• GPickup

• iDivert

• MeetMe

• Park

• Pickup

Unsupported and Supported Configurations for Agent Phones

Unsupported Configurations for Agent Phones

The following configurations are not supported for agent phones:

• Two lines on an agent phone that have the same extension but exist in different partitions.

• Unified CCX extension that is assigned to multiple devices.

• Configuring the same Unified CCX extension in more than one device profile, or configuring the same Unified CCX extension in any combination of device profiles and devices. (Configuring a Unified CCX extension in a single device profile is supported.)

• In the Unified Communications Manager Administration Directory Number Configuration web page for each Unified CCX line, setting Maximum Number of Calls to a value other than 2.

• In the Unified Communications Manager Administration Directory Number Configuration web page for each Unified CCX line, setting Busy Trigger to a value other than 1.

• No Cisco Unified Communications Manager device can be forwarded to the Unified CCX extension of an agent.

• The Unified CCX extension of an agent cannot be configured to forward to a Cisco Unified CCX Trigger or CTI route point.

  Note	This is applicable to all types of forward such as, Forward All, Forward No Answer External, Forward on CTI Failure, and so on.

• Configuring the Unified Communications Manager Intercom feature.

• Configuring the Hold Reversion feature.

• Agent extensions cannot be added to hunt lists or hunt groups. If an agent has only one line, then the agent phone cannot be part of a hunt list or hunt group. In the case of multiple lines, none of the lines on the first four buttons on the phone must be part of the hunt group. For more details on multiple lines support and number of monitored lines, see the Cisco Unified Contact Center Express Design Guide, located at http://www.cisco.com/c/en/us/support/customer-collaboration/unified-contact-center-express/products-implementation-design-guides-list.html.

• Call Forward All to extensions which Unified CCX does not have control over. For example, if an agent extension has Call Forward All to a PSTN extension or Directory Number on another cluster which Unified CCX is unaware of.

• All the Cisco IP Phones for Cisco Finesse IP Phone Agent currently do not support the Simplified New Call UI.

Supported Configurations for Agent Phones

To determine the phone devices that are supported by Cisco Finesse and for use by Cisco Finesse IP Phone agents, see the Compatibility Matrix for Unified CCX, located at: http://docwiki.cisco.com/wiki/Compatibility_Matrix_for_Unified_CCX

The following configurations are supported on agent phones:

• A Unified CCX extension that is configured on a single device (but not on multiple devices).

• A Unified CCX extension that is configured in a single device profile (but not in multiple device profiles).

• Multiple agents sharing the same Unified CCX extension, which you can set up as follows:

  • Configure the Unified CCX extension to a single phone (not in a device profile).

  • Associate the phone with all the agents who will use this extension.

  • Select the appropriate directory number (DN) as the Unified CCX extension for each agent.

    In this configuration, only one agent at a time can be logged in.

    Note	All agents who currently have the Unified CCX extension to be shared must log out before you configure additional agents to share that extension.

• Video is now supported if you are using Cisco Jabber for Windows as agent phone. The agent desktop where Jabber is used for Video should comply to the Cisco Jabber hardware requirements listed in the Cisco Jabber for Windows 11.0.x and 11.1.x Release Notes , located at:

  http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/11_0/RN/JABW_BK_C5E7828C_00_cisco-jabber-windows-11-release-notes.html.

Unsupported and Supported Configurations for Remote Agents

Unified CCX supports Cisco Expressway 8.7.1 from the release 11.5(1) onward. The current version of Cisco Expressway does not support BiB and thus the contact center cannot achieve silent monitoring and recording functionalities.

Unsupported Features in Unified Communications Manager and Cisco Business Edition 6000

The following Unified Communications Manager features are not supported by Unified CCX. These features are disabled by default and you should not enable them for Unified CCX. For more information about these features, see Unified Communications Manager documentation, located at:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html.

• Block External to External Transfer.

• DSCP IP CTIManager to Application service parameter.

  You can enable this service parameter for Unified Communications Manager, but doing so does not affect Unified CCX.

• Advanced Ad Hoc Conference Enabled service parameter.

• Drop ad hoc conference when the creator leaves the conference.

• Signaling (QSIG) Path Replacement (PR).

  This feature must be disabled when Unified CCX is deployed. To disable this feature, set the Unified Communications Manager service parameters Path Replacement Enabled and Path Replacement on Tromboned Calls to False.

• Forced Authorization Code and Client Matter Code.

  Because these features can be enabled per route pattern, you should turn them off for all route patterns in the Unified Communications Manager cluster that Unified CCX might use. Enabling these features for route patterns that Unified CCX does not use does not affect Unified CCX.

• Multilevel precedence and preemption (MLPP).

  You can enable this feature for devices in the cluster that do not interact with Unified CCX.

• Do not use Unified Communications Manager Administration to add or change CTI ports or route points that are used by Unified CCX or application users that are created by Unified CCX.

Unsupported Features in Custom Reports

The Do Not Call field is no longer available in Unified CCX 11.0(1) release onward. While upgrading to Unified CCX 11.5(1), report will not be generated if the Do Not Call column is present in the custom report. You can generate the report by removing the Do Not Call column from the custom reports in Unified CCX 11.5(1).