Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager, Release 9.1(1)
Additional registry keys configuration for Cisco Unified Personal Communicator
Download this chapter
Additional registry keys configuration for Cisco Unified Personal CommunicatorAdditional registry keys configuration for Cisco Unified Personal Communicator
Download the complete book
Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager, Release 9.1(1)Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager, Release 9.1(1) (PDF - 6 MB)
 Feedback

Additional registry keys configuration for Cisco Unified Personal Communicator

This chapter contains information about the additional registry key customizations provided by Cisco Unified Personal Communicator over and above those set aside for Active Directory.

For information specific to Cisco Jabber clients, such as Jabber for Windows, see the appropriate client documentation below:

If you wish to continue with information specific to Cisco Unified Personal Communicator, proceed with the contents in this chapter:

Registry key mapping

All registry keys discussed in this chapter are located in HKEY_CURRENT_USER\Software\Policies\Cisco Systems, Inc.\Client Services Framework\AdminData, with the exception of those associated with Dial via Office (DVO) functionality, unless otherwise noted. Registry keys associated with Dial via Office are located in HKEY_CURRENT_USER\Software\Policies\Cisco Systems, Inc.\Unified Communications\CUPC8.

Video registry setting configuration

The following table lists the registry subkeys that you must use to specify the video registry settings.

Table 1 Video Registry Settings

Subkey Names

Description

VideoEnabled

Setting this key to 'false', will disable all video capabilities in CUPC.

Video capabilities are enabled by default.

CTI registry setting configuration

The following table lists the registry subkeys that you must use to specify CTI registry settings.

Table 2 CTI Registry Settings

Subkey Names

Description

CtiServerJtapiLibDownloadPort

Allows for an alternative port to be used to download the Jtapi.jar file from CUCM.

This file is used to support deskphone mode.

By default, port 80 is used. Currently, the only other alternative port which can be used is '8080'.

Web conferencing registry setting configuration

The following table lists the registry subkeys that you must use to specify web conferencing registry settings.

Table 3 Web Conferencing Registry Settings

Subkey Names

Description

WebConfSSOIdentityProvider

If using WebEx SSO, enter the name of the provider type such as ‘meetingplace'.

Related Information

Dial via Office registry setting configuration

The following table lists the registry subkeys that you must use to specify Dial via Office registry settings.

Table 4 Dial via Office Registry Settings

Subkey Names

Description

DVOModeEnabled

Setting this key to false will disable the Dial via Office functionality introduced in Cisco Unified Personal Communicator 8.5(2).

This feature is enabled by default

For information about configuring this feature, see the Release Notes for Cisco Unified Personal Communicator Release 8.5.

Additional registry setting configuration

The following table lists additional registry keys that provide additional Cisco Unified Personal Communicator customizations.

Table 5 Additional Registry Settings

Subkey Names

Description

AudioCustomRingtone

Cisco Unified Personal Communicator supports the use of custom ring tones. Cisco will provide a set of custom ringtones. Only these ringtones are supported.

The ringtone can be specified in a registry setting or in a directory named ringtone in the CSF appdata / roaming directory. The ringtone must be copied to that location by the administrator. To change a ringtone, the new file is copied into the correct location and the client restarted.

The default is that this subkey name is not used.

DeskphoneStartupMode

This key is used to start Cisco Unified Personal Communicator in deskphone mode. In a VDI environment the client needs to be started in deskphone mode. To meet this requirement, this registry subkey has been introduced.

If the value of this key is set to 1, the client will start in deskphone mode. If is not set, or has a value other than 1, the client will start up by using the last phone mode the client used during start up.

The default is that this subkey name is not used.

AutomaticTetheredPhoneSelection

This key is used to set the Automatic Tethered Phone Selection feature. Cisco Unified Personal Communicator users will often have multiple deskphone devices assigned to them but only one that is tethered to their workstation through an Ethernet cable. This feature ensures that the tethered phone is always selected when a Cisco Unified Personal Communicator user enters deskphone mode.

This feature is disabled by default.

The following usage scenarios outline the operation of this feature when it is enabled through the registry:

  • If the user manually changes their deskphone device from the tethered device to a new one while the device is available, the new device will be chosen and automatic selection will be switched off.
  • If the user manually changes their deskphone device from tethered while the device is not available, the new phone device will be selected but when the tethered phone becomes available again Cisco Unified Personal Communicator will automatically switch back to it.
  • If the user manually changes the deskphone device to tethered, automatic selection will be switched on.
  • If the user changes phone modes, automatic selection will be switched on.
    Note   

    This feature will also work if the user is logged in to their tethered phone with extension mobility.