Configuration Guide for Cisco UC Integration for Cisco WebEx Connect C7
Configuring the Device Type on Cisco Unified Communications Manager
Downloads: This chapterpdf (PDF - 160.0KB) The complete bookPDF (PDF - 761.0KB) | Feedback

Configuring the Device Type on Cisco Unified Communications Manager

Table Of Contents

Configuring the Device Type on Cisco Unified Communications Manager

Preparing Cisco Unified Communications Manager

Creating Devices and Directory Numbers for Users

QoS Packet Marking on Windows Vista

Enabling Packet Marking for CSF with Active Directory 2008 on Windows Vista


Configuring the Device Type on Cisco Unified Communications Manager


Configuring Cisco Unified Communications Manager for Cisco UC Integration for Cisco WebEx Connect, involves adding the device type to Cisco Unified Communications Manager and setting up the directory number. Before you begin you must have a properly working Cisco Unified Communications configuration with the following services enabled:

Cisco Unified Communications Manager service. For information about the Cisco Unified Communications Manager service see the documentation at the following URL:

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

Cisco Trivial File Transfer Protocol (TFTP) service. For information about Cisco TFTP service, see the Cisco Unified Communications Manager System Guide at the following URL:

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

Cisco CTIManager service. For information about Cisco CTIManager service, see the Cisco Unified Communications Manager System Guide at the following URL:

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

Cisco Unified Communications Manager IP Phone (CCMCIP) service.


Note Administrators do not control the CCMCIP service. It is on by default and administrators should configure their clients to use the CUCM Subscriber for the CCMCIP Service.


Preparing Cisco Unified Communications Manager

The Cisco UC Integration for Cisco WebEx Connect requires a new Cisco Unified Communications Manager device type called Client Services Framework. Depending on which release of Cisco Unified Communications Manager is installed in your Cisco Unified Communications system, you might need to patch Cisco Unified Communications Manager with a Cisco Options Package (COP) file.

You must run the COP file if your Cisco Unified Communications Manager does not have the Client Services Framework device type. You run the COP file on the Cisco Unified Communications Manager publisher server. After you apply the COP file, you must restart the Cisco Unified Communications Manager publisher server, and all other servers.

The COP file is available from the Administration Toolkit. To access the Administration Toolkit, navigate to Cisco UC Integration for Cisco WebEx Connect from the Download Software page at the following URL:

http://www.cisco.com/cisco/software/release.html?mdfid=282811017&flowid=5464&softwareid=282888767&release=7.1(6)&rellifecycle=&relind=AVAILABLE&reltype=latest

For more information refer to the Cisco Unified Communications Manager release notes:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/7_0_1/cucm-rel_notes-701.html#wp684478

Creating Devices and Directory Numbers for Users

Procedure


Step 1 Select Device > Phone in Cisco Unified Communications Manager Administration.

Step 2 Select Add New.

Step 3 From the Phone Type drop down box, select Cisco Unified Client Services Framework.

Step 4 Select Next.

Step 5 Enter information for the phone in the Phone Configuration window, as follows:

Field
Description
Device Information

Device Name

Enter a name to identify the Cisco Unified Client Services Framework device. The name contains character including alphanumeric characters, periods, hyphens, and underscores. The device name does not need to relate to the user ID of the user.

Description

(Optional) Enter a description of the device.

Device Pool

Select the device pool to which you want the phone assigned. The device pool defines sets of common characteristics for devices, such as region, date/time group, softkey template, and Multilevel Precedence and Preemption (MLPP) information.

Common Device Configuration

(Optional) Select the common device configuration to which you want this device assigned. The common device configuration includes the attributes (services or features) that are associated with a particular user.

Phone Button Template

Select the applicable phone button template. The phone button template determines the configuration of buttons on a phone and identifies which feature (line, speed dial, and so on) is used for each button.

Common Phone Profile

Select a name to identify the phone profile.

Calling Search Space

(Optional) Select from the list of partitions. A calling search space comprises a collection of partitions that are searched for numbers that are called from this directory number. The value that you select applies to all devices that are using this directory number.

Media Resource Group List

(Optional) This window lists the media resource groups. The list includes only previously defined media resource groups and are listed in order of priority highest to lowest.

User Hold MOH Audio Source

(Optional) Select to the sound plays when a user initiates a hold action.

Network Hold MOH Audio Source

(Optional) Select to the sound plays when the network initiates a hold action.

Location

Select a location to change the RSVP policy setting.

User Locale

(Optional) Select to identify a set of detailed information to support end users including language and font.

Network Locale

(Optional) Select the locale that is associated with the gateway. The network locale identifies a set of detailed information to support the hardware in a specific location. The network locale contains a definition of the tones and cadences that are used by the device in a specific geographic area.

Note: Select only a network locale that is already installed and supported by the associated devices. The list contains all available network locales for this setting, but not all are necessarily installed. If the device is associated with a network locale that it does not support in the firmware, the device will fail to come up.

Device Mobility Mode

Turn the device mobility feature on or off for this device or select Default to use the default device mobility mode. The default setting uses the value for the Device Mobility Mode service parameter for the device.

Owner User ID

(Optional) Select the user ID of the assigned phone user. The user ID is recorded in the call detail record (CDR) for all calls made from this device.

Note: Do not configure this field if you are using extension mobility. Extension mobility does not support device owners.

Note: The Owner User ID and Mobility User ID can differ.

Mobility User ID

(Optional) Select the user ID of the person to whom this dual-mode phone is assigned.

Note: The Mobility User ID configuration is used for the Mobile Connect and Mobile Voice Access features for dual-mode phones.

Note: The Owner User ID and Mobility User ID can differ.

Primary Phone

(Optional) Select the physical phone that will be associated with the application, such as IP communicator or Cisco Unified Communications Integration. When you select a primary phone, the application consumes fewer device license units and is considered an "adjunct" license (to the primary phone).

Use Trusted Relay Point

Enable or disable whether Cisco Unified Communications Manager inserts a trusted relay point (TRP) device with this media endpoint. Select one of the following values:

Default - If you select this value, the device uses the Use Trusted Relay Point setting from the common device configuration with which this device associates.

Off - Select this value to disable the use of a TRP with this device. This setting overrides the Use Trusted Relay Point setting in the common device configuration with which this device associates.

On - Select this value to enable the use of a TRP with this device. This setting overrides the Use Trusted Relay Point setting in the common device configuration with which this device associates.

A Trusted Relay Point (TRP) device designates an MTP or transcoder device that is labeled as Trusted Relay Point.

Always Use Prime Line

Enable or disable one of the following options:

Default - Cisco Unified Communications Manager uses the configuration from the Always Use Prime Line service parameter, which supports the Cisco CallManager service.

Off - When the phone is idle and receives a call on any line, the phone user can answer the call from the line on which the call is received.

On - When the phone is idle (off hook) and receives a call on any line, the primary line gets selected for the call. Calls on other lines continue to ring, and the phone user must select those other lines to answer these calls.

Always Use Prime Line for Voice Message

Enable or disable one of the following options:

On - If the phone is idle, the primary line on the phone becomes the active line for retrieving voice messages when the phone user presses the Messages button on the phone.

Off - If the phone is idle, pressing the Messages button on the phone automatically dials the voice-messaging system from the line that has a voice message. Cisco Unified Communications Manager always selects the first line that has a voice message. If no line has a voice message, the primary line gets used when the phone user presses the Messages button.

Default - Cisco Unified Communications Manager uses the configuration from the Always Use Prime Line for Voice Message service parameter, which supports the Cisco CallManager service.

Calling Party Transformation CSS

(Optional) This setting permits you to localize the calling party number on the device. Make sure that the Calling Party Transformation CSS that you select contains the calling party transformation pattern that you want to assign to this device.

Tip: Before the call occurs, the device must apply the transformation by using digit analysis. If you configure the Calling Party Transformation CSS as None, the transformation does not match and does not get applied. Verify that you configure the Calling Party Transformation Pattern in a non-null partition that is not used for routing.

Geolocation

(Optional) Select the Unspecified geolocation which designates that this device does not associate with a geolocation.

Use Device Pool Calling Party Transformation CSS

Check this box to use the Calling Party Transformation CSS that is configured in the device pool assigned to this device. If you do not select this check box, the device uses the Calling Party Transformation CSS that you selected in the Phone Configuration window.

Ignore Presentation Indicators (internal calls only)

Check this box to configure call display restrictions on a call-by-call basis. When this check box is checked, Cisco Unified Communications Manager ignores any presentation restriction that is received for internal calls.

Allow Control of Device from CTI

Select this option if you want Cisco UC Integration for Cisco WebEx Connect to control and monitor the desk phone of the user with the Computer Telephony Integration (CTI) server.

Ensure that the user is added to the Standard CTI Enabled user group.

Logged Into Hunt Group

Check this box to indicate that the phone is currently logged in to a hunt list (group). When the phone is added to a hunt list, the administrator can log the user in or out by checking (and unchecking) this check box.

Users use the softkey on the phone to log their phone in or out of the hunt list.

Remote Device

Check this box if you are experiencing delayed connect times over SCCP pipes to remote sites. Selecting this check box tells the Cisco Unified Communications Manager to allocate a buffer for the phone device when it registers and to bundle SCCP messages to the phone.

Tip: Because this feature consumes resources, be sure to check this check box only when you are experiencing signaling delays for phones that are running SCCP. Most users do not require this option.

Protocol Specific Information

Packet Capture Mode

This setting exists for troubleshooting encryption only; packet capturing may cause high CPU usage or call-processing interruptions. Select one of the following options from the drop-down list box:

None - This option, which serves as the default setting, indicates that no packet capturing is occurring. After you complete packet capturing, configure this setting.

Batch Processing Mode - Cisco Unified Communications Manager writes the decrypted or non encrypted messages to a file, and the system encrypts each file. On a daily basis, the system creates a new file with a new encryption key. Cisco Unified Communications Manager, which stores the file for seven days, also stores the keys that encrypt the file in a secure location. Cisco Unified Communications Manager stores the file in the PktCap virtual directory. A single file contains the time stamp, source IP address, source IP port, destination IP address, packet protocol, message length, and the message. The TAC debugging tool uses HTTPS, administrator username and password, and the specified day to request a single encrypted file that contains the captured packets. Likewise, the tool requests the key information to decrypt the encrypted file.

Packet Capture Duration

(Optional) This setting exists for troubleshooting encryption only; packet capturing may cause high CPU usage or call-processing interruptions.

This field specifies the maximum number of minutes that is allotted for one session of packet capturing. The default setting equals 0, although the range exists from 0 to 300 minutes.

To initiate packet capturing, enter a value other than 0 in the field. After packet capturing completes, the value, 0, displays.

Presence Group

Select a Presence group for the end user. The selected group specifies the devices, end users, and application users that can monitor this directory number.

The default value for Presence Group specifies Standard Presence group, configured with installation. Presence groups that are configured in Cisco Unified Communications Manager Administration also appear in the drop-down list box.

SIP Dial Rules

(Optional) Select the appropriate SIP dial rule. SIP dial rules provide local dial plans for Cisco Unified IP Phones 7905, 7912, 7940, and 7960, so users do not have to press a key or wait for a timer before the call gets processed.

Leave the SIP Dial Rules field set to <None> if you do not want dial rules to apply to the IP phone that is running SIP. This means that the user must use the Dial softkey or wait for the timer to expire before the call gets processed.

MTP Preferred Originating Codec

(Optional) Select the codec to use if a media termination point is required for SIP calls.

Device Security Profile

Select the security profile you require for the phone.

If you select Client Services Framework- Standard SIP Secure Profile, do the following:

1. Enter certification and authentication information in the Certification Authority Proxy Function (CAPF) Information section.

2. Select Generate String.

3. Email the contents of the Authentication String field to the user.

Rerouting Calling Search Space

(Optional) Select a calling search space to use for rerouting.

The rerouting calling search space of the refered is used to find the route to the refer-to target. When the Refer fails due to the rerouting calling search space, the Refer Primitive rejects the request with the "405 Method Not Allowed" message.

The redirection (3xx) primitive and transfer feature also uses the rerouting calling search space to find the redirect-to or transfer-to target.

SUBSCRIBE Calling Search Space

(Optional) From the drop-down list box, select the SUBSCRIBE calling search space to use for presence requests for the phone. All calling search spaces that you configure in Cisco Unified Communications Manager Administration display in the SUBSCRIBE Calling Search Space drop-down list box.

If you do not select a different calling search space for the end user from the drop-down list, the SUBSCRIBE calling search space defaults to None.

To configure a SUBSCRIBE calling search space specifically for this purpose, you configure a calling search space as you do all calling search spaces.

Supported with the Presence feature, the SUBSCRIBE calling search space determines how Cisco Unified Communications Manager routes presence requests that come from the phone. This setting permits you to apply a calling search space separate from the call-processing search space for presence (SUBSCRIBE) requests for the phone.

SIP Profile

Select the default SIP profile or a specific profile that was previously created. SIP profiles provide specific SIP information for the phone such as registration and keepalive timers, media ports, and do not disturb control.

Digest User

(Optional) Select the default SIP profile or a specific profile that was previously created. SIP profiles provide specific SIP information for the phone such as registration and keepalive timers, media ports, and do not disturb control.

Media Termination Point Required

Use this field to indicate whether a media termination point is used to implement features that H.323 does not support (such as hold and transfer).

Select the Media Termination Point Required check box to use an MTP to implement features. Uncheck the Media Termination Point Required check box if you do not want to use an MTP to implement features.

Use this check box only for H.323 clients and those H.323 devices that do not support the H.245 empty capabilities set or if you want media streaming to terminate through a single source.

If you check this check box to require an MTP and this device becomes the endpoint of a video call, the call will be audio only.

Unattended Port

Check this check box to indicate an unattended port on this device.

Require DTMF Reception

Select this check box to require DTMF reception for this phone and phones that are running SIP and SCCP,

Note: In configuring Cisco Unified Mobility features, when using intercluster DNs as remote destinations for an IP phone via SIP trunk (either intercluster trunk [ICT] or gateway), check this check box so that DTMF digits can be received out of band, which is crucial for Enterprise Feature Access midcall features.

Certification Authority Proxy Function (CAPF) Information

Certificate Operation

From the drop-down list box, select one of the following options:

No Pending Operation - Displays when no certificate operation is occurring (default setting).

Install/Upgrade - Installs a new or upgrades an existing locally significant certificate in the phone.

Delete - Deletes the locally significant certificate that exists in the phone.

Troubleshoot - Retrieves the locally significant certificate (LSC) or the manufacture installed certificate (MIC), so you can view the certificate credentials in the CAPF trace file. If both certificate types exist in the phone, Cisco Unified Communications Manager creates two trace files, one for each certificate type.

By choosing the Troubleshooting option, you can verify that an LSC or MIC exists in the phone.

Authentication Mode

This field permits you to select the authentication method that the phone uses during the CAPF certificate operation.

From the drop-down list box, select one of the following options:

By Authentication String - Installs/upgrades, deletes, or troubleshoots a locally significant certificate only when the user enters the CAPF authentication string on the phone.

By Null String - Installs/upgrades, deletes, or troubleshoots a locally significant certificate without user intervention.

This option provides no security; Cisco strongly recommends that you select this option only for closed, secure environments.

By Existing Certificate (Precedence to LSC) - Installs/upgrades, deletes, or troubleshoots a locally significant certificate if a manufacture-installed certificate (MIC) or locally significant certificate (LSC) exists in the phone. If a LSC exists in the phone, authentication occurs via the LSC, regardless whether a MIC exists in the phone. If a MIC and LSC exist in the phone, authentication occurs via the LSC. If a LSC does not exist in the phone, but a MIC does exist, authentication occurs via the MIC.

Before you select this option, verify that a certificate exists in the phone. If you select this option and no certificate exists in the phone, the operation fails.

At any time, the phone uses only one certificate to authenticate to CAPF even though a MIC and LSC can exist in the phone at the same time. If the primary certificate, which takes precedence, becomes compromised for any reason, or, if you want to authenticate via the other certificate, you must update the authentication mode.

By Existing Certificate (Precedence to MIC) - Installs, upgrades, deletes, or troubleshoots a locally significant certificate if a LSC or MIC exists in the phone. If a MIC exists in the phone, authentication occurs via the MIC, regardless whether a LSC exists in the phone. If a LSC exists in the phone, but a MIC does not exist, authentication occurs via the LSC.

Before you select this option, verify that a certificate exists in the phone. If you select this option and no certificate exists in the phone, the operation fails.

Note: The CAPF settings that are configured in the Phone Security Profile window interact with the CAPF parameters that are configured in the Phone Configuration window.

Authentication String

(Optional) If you select the By Authentication String option in the Authentication Mode drop-down list box, this field applies. Manually enter a string or generate a string by clicking the Generate String button. Verify the string contains 4 to 10 digits.

To install, upgrade, delete, or troubleshoot a locally significant certificate, the phone user or administrator must enter the authentication string on the phone.

Key Size (Bits)

Select the key size for the certificate from the drop-down list box. The default setting equals 1024. Other options include 512 and 2048.

If you select a higher key size than the default setting, the phones take longer to generate the entropy that is required to generate the keys. Key generation, which is set at low priority, allows the phone to function while the action occurs. Depending on the phone model, you may notice that key generation takes up to 30 or more minutes to complete.

Note: The CAPF settings that are configured in the Phone Security Profile window interact with the CAPF parameters that are configured in the Phone Configuration window.

Operation Completes By

(Optional) This field, which supports the Install/Upgrade, Delete, and Troubleshoot Certificate Operation options, specifies the date and time in which you must complete the operation.

The values that display apply to the publisher database server.

Extension Information

Enable Extension Mobility

 

Log Out Profile

(Optional)

MLPP Information

MLPP Domain

(Optional) Select an MLPP domain from the drop-down list box for the MLPP domain that is associated with this device. If you leave the None value, this device inherits its MLPP domain from the value that was set for the device pool of the device. If the device pool does not have an MLPP domain setting, this device inherits its MLPP domain from the value that was set for the MLPP Domain Identifier enterprise parameter.

Do Not Disturb

Do Not Disturb

Check this check box to enable Do Not Disturb on the phone.

DND Option

When you enable DND on the phone, this parameter permits you to specify how the DND features handle incoming calls:

Call Reject - This option specifies that no incoming call information gets presented to the user. Depending on how you configure the DND Incoming Call Alert parameter, the phone may play a beep or display a flash notification of the call.

Ringer Off - This option turns off the ringer, but incoming call information gets presented to the device, so the user can accept the call.

Use Common Phone Profile Setting - This option specifies that the DND Option setting from the Common Phone Profile window will get used for this device.

Note: For 7940/7960 phones that are running SCCP, you can only choose the Ringer Off option. For mobile devices and dual-mode phones, you can only choose the Call Reject option. When you activate DND Call Reject on a mobile device or dual-mode phone, no call information gets presented to the device.

DND Incoming Call Alert

(Optional) When you enable the DND Ringer Off or Call Reject option, this parameter specifies how a call will be displayed.

From the drop-down list, select one of the following options:

None - This option specifies that the DND Incoming Call Alert setting from the Common Phone Profile window gets used for this device.

Disable - This option disables both beep and flash notification of a call, but, for the DND Ringer Off option, incoming call information still gets displayed. For the DND Call Reject option, no call alerts display, and no information gets sent to the device.

Beep Only - For an incoming call, this option causes the phone to play a beep tone only.

Flash Only - For an incoming call, this option causes the phone to display a flash alert.



Note Cisco UC Integration for Cisco WebEx Connect does not support secure phone device configurations.


Step 6 Select Save.

Step 7 Click Apply Config to activate the settings.

Step 8 Click OK.

Step 9 Select the Add a new DN (directory number) link in the Association Information section on the Phone Configuration window.

Step 10 Enter information for the directory number in the Directory Number Configuration window.

Step 11 Select Save.

Step 12 Select Associate End Users in the Directory Number Configuration window.

Step 13 Search for the user in the Find and List Users window, select the user, then select Add Selected.

Step 14 Select Save.

Step 15 Select User Management > End User in Cisco Unified Communications Manager Administration.

Step 16 Search for the user in the Find and List Users window, then select the user.

Step 17 Verify that the device is listed for the user in the Controlled Devices list box in the Device Associations group.

QoS Packet Marking on Windows Vista

Quality of Service (QoS) packet marking requires administrator privileges for Windows Vista computers in Active Directory 2003 domains. Therefore users must have administrator privileges to overcome this operating system limitation and enable QoS packet marking for CSF deployments on Windows Vista on Active Directory 2003 domains.

For Windows Vista computers in Active Directory 2008 Domains you can use Group Policy to overcome this limitation, as described in the following procedure.

Enabling Packet Marking for CSF with Active Directory 2008 on Windows Vista

Procedure


Step 1 Start the Group Policy Management Editor application.

Step 2 Expand the User Configuration node.

Step 3 In Policies > Windows Settings, right-click Policy-based QoS, then select Create new policy.

For example, create a policy called Cisco CSF UDP.

Step 4 Check Specify DSCP Value, and enter 46 as the value, to mark traffic as expedited forwarding (EF).

Step 5 Select Next.

Step 6 Select the Only applications with this executable name option, then enter the following executable name:

cucsf.exe

Step 7 Select Next.

Step 8 Specify that the QoS policy applies to any pair of source and destination IP addresses. To do this, select the following options:

Any source IP address

Any destination IP address

Step 9 Select Next.

Step 10 Select the protocol to which the QoS policy applies, then specify the port or port ranges for the source and destination of the traffic.

For example, select UDP, and select From any source port and To any destination port.

Step 11 Select Finish.

Step 12 Apply the group policy you created to your client computers.

The settings that are applied to the client computers from the example above are as follows:

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\QoS\Cisco CSF UDP]

"Version"="1.0"

"Application Name"="cucsf.exe"

"Protocol"="UDP"

"Local Port"="*"

"Local IP"="*"

"Local IP Prefix Length"="*"

"Remote Port"="*"

"Remote IP"="*"

"Remote IP Prefix Length"="*"

"DSCP Value"="46"

"Throttle Rate"="-1"