Installation Guide for Cisco Unified Communications Integration for Microsoft Office Communicator Release 8.0
Configuring Servers for Cisco Unified Communications Integration for Microsoft Office Communicator
Downloads: This chapterpdf (PDF - 304.0KB) The complete bookPDF (PDF - 2.26MB) | Feedback

Configuring Servers for Cisco Unified Communications Integration for Microsoft Office Communicator

Table Of Contents

Configuring Servers for Cisco Unified Communications Integration for Microsoft Office Communicator

How to Configure Active Directory Server and OCS Server

E.164 Formatting

Phone Numbers for Active Directory Users Must Use +E.164 Formatting

Enabling Users for OCS

Configuration of Telephony Options for Users

Updating OCS Address Book Manually

Verifying OCS Address Book Synchronization

Dial Plan Options for Cisco UC Integration for Microsoft Office Communicator

Dialing Rules Required for Cisco UC Integration for Microsoft Office Communicator

Application Dialing Rules

Directory Lookup Dialing Rules

How to Configure Cisco Unified Communications Manager Server

Prerequisites for Configuring Cisco Unified Communications Manager

Cisco Unified Client Services Framework Device Type

Enabling LDAP Synchronization

Enabling LDAP Authentication

Creating Client Services Framework Devices and Directory Numbers for Users

Adding Users to User Groups and Associating Controlled Devices

How to Configure Cisco Unified IP Phones for Video

Connecting a Cisco Unified IP Phone to the Network and Your Computer

Enabling Video for a Cisco Unified IP Phone

Securing IP Phones

Configuring Cisco Unified Communications Manager for Ad-Hoc Video Conferencing

(Optional) Specifying a Minimum Number of Video-Capable Participants for Ad-Hoc Conferences

How to Make Cisco Unified Communications Manager Dialing Rules Accessible

Verifying That Dialing Rules Are Configured on Cisco Unified Communications Manager

Generating Copies of the Dialing Rules

Verifying That Copies of the Dialing Rules Were Generated

Restarting the TFTP Service

Ensuring That Cisco UC Integration for Microsoft Office Communicator Clients Are Restarted

Configuring Failover to Cisco Unified Survivable Remote Site Telephony (SRST)

How To Configure Cisco Unified MeetingPlace

Meeting Types and Authentication

Reservationless Meetings

Authentication

Reserving Audio and Video Resources

Configuring a Cisco Unified MeetingPlace Application Server for Ad-Hoc Video Conferencing

Configuring a Cisco Unified MeetingPlace Application Server for Scheduled Video Conferencing

Adding Custom Cisco Unified MeetingPlace Template Files to a Cisco Unified MeetingPlace 7.x Web Server

How to Configure Cisco Unity Server for Voicemail Access

Installing the Voicemail Web Service (VMWS)

Setting the DCOM Permissions

Testing That the Voicemail Web Service Is Accessible

How to Configure Cisco Unity Connection Server for Voicemail Access

Configuring User Access

Enabling Secure Access to Voice Messages


Configuring Servers for Cisco Unified Communications Integration for Microsoft Office Communicator


Revised: July 7, 2011

How to Configure Active Directory Server and OCS Server

Dial Plan Options for Cisco UC Integration for Microsoft Office Communicator

How to Configure Cisco Unified Communications Manager Server

How To Configure Cisco Unified MeetingPlace

How to Configure Cisco Unity Server for Voicemail Access

How to Configure Cisco Unity Connection Server for Voicemail Access

How to Configure Active Directory Server and OCS Server

When you configure your servers for Cisco UC Integration for Microsoft Office Communicator, you must ensure that the user IDs, devices, and directory numbers match in the following servers:

Active Directory server

Office Communications Server (OCS)

Cisco Unified Communications Manager server

You must also configure your users so that each user has a phone number that can be correctly dialed within the context of your Cisco Unified Communications Manager configuration.

For more information about the importance of the use of the +E.164 format to the deployment of Cisco UC Integration for Microsoft Office Communicator, read the following topics:

E.164 Formatting

Phone Numbers for Active Directory Users Must Use +E.164 Formatting

To configure the Active Directory server and the OCS server for Cisco UC Integration for Microsoft Office Communicator, you must perform the following tasks:

Enabling Users for OCS

Updating OCS Address Book Manually

Verifying OCS Address Book Synchronization

E.164 Formatting

The E.164 standard defines an international numbering plan for public phone systems. In the E.164 standard, each number contains a country code, an area code, and a subscriber number. Each phone user has a globally unique number. In Cisco UC Integration for Microsoft Office Communicator, phone numbers in E.164 format must begin with a plus character ("+"), therefore we say that the numbers are in +E.164 format.

Phone Numbers for Active Directory Users Must Use +E.164 Formatting

You must define phone numbers in +E.164 format for each user in your Active Directory. This ensures the following:

When Microsoft Office Communicator downloads the OCS address book, each user in the OCS address book is assigned a number in the correct format.

Each user has a phone number that can be correctly dialed within the context of your Cisco Unified Communications Manager configuration.

The Microsoft Office Communicator Automation API reads contacts and their associated phone numbers from Active Directory, and passes this data to the Cisco UC Integration for Microsoft Office Communicator.


Tip Define phone numbers in +E.164 format for each user in your Active Directory. If you do not do this, you must configure a set of phone number normalization rules on the OCS server, so that a phone number that can be correctly dialed is available in the OCS address book. Configuring phone number normalization rules can be an error-prone task, especially for international and enterprise dial plans. If you choose not to define phone numbers in +E.164 format, see Appendix A, "Normalization Rules for OCS".


What to Do Next

Enabling Users for OCS

Enabling Users for OCS

Procedure


Step 1 Start the Active Directory Users and Computers administrative tool.

Step 2 Expand the domain that contains your users.

Step 3 Open the organizational unit (OU) that contains your users.

Step 4 Check the following details for all users that you want to enable for OCS:

All users have valid email addresses.

All users are assigned to a group.

All the phone numbers for each user are in +E.164 format, and can be correctly dialed within the context of your Cisco Unified Communications Manager configuration.

Step 5 Right-click the users, then select Enable users for Communications Server.

Active Directory uses the User logon name field and the domain name to form a SIP email address in the Office Communications Server Address column. This address is used to sign users in to Microsoft Office Communicator, and enables users to send instant messages.


Related Topics

Configuration of Telephony Options for Users

Phone Numbers for Active Directory Users Must Use +E.164 Formatting

What to Do Next

Updating OCS Address Book Manually

Configuration of Telephony Options for Users

We recommend that you do not select the following telephony options for your users:

Enable Remote call control

Enable Enterprise Voice

If you select either of these options, voice traffic is allowed from both Cisco UC Integration for Microsoft Office Communicator and Microsoft Office Communicator. This can result in the following problems:

A confusing user experience, as users can place and receive calls from a mixture of user interface elements in both applications.

Inconsistent voice traffic. That is, calls from Cisco UC Integration for Microsoft Office Communicator might give a different audio experience to Microsoft Office Communicator.

A mixed configuration is more difficult to manage, as administrators must track traffic from two sources. You might want to monitor voice usage in your network and if you use both applications, you must configure your monitoring tools to track traffic from both applications.

Related Topics

Enabling Users for OCS

Updating OCS Address Book Manually

To ensure that the OCS address book has the latest information from the Active Directory server, you must update the OCS address book manually. For information about how to perform this task, see the following URL:

http://technet.microsoft.com/en-us/library/bb936631.aspx

What to Do Next

Verifying OCS Address Book Synchronization

Verifying OCS Address Book Synchronization

You must verify that the users are enabled for OCS, that the OCS address book is synchronized with the Active Directory server, and that the OCS address book is configured and operational.

To resolve problems associated with synchronization of the OCS address book, see Troubleshooting Cisco Unified Communications Integration for Microsoft Office Communicator, page 6-1. Alternatively, see the relevant Microsoft documentation.

Procedure


Step 1 Use one of the user accounts to sign in to Microsoft Office Communicator.

This step signs the user in to OCS.

Step 2 Verify that the following message is not displayed in the notifications area in Microsoft Office Communicator after the user signs in:

Cannot Synchronize Address Book


Dial Plan Options for Cisco UC Integration for Microsoft Office Communicator

The following table summarizes the dial plan options available when you deploy Cisco UC Integration for Microsoft Office Communicator:

Option
Phone Numbers in Active Directory
Phone Numbers in Cisco Unified Communications Manager
Comments
1

+E.164 number format

+E.164 number format

Requires Cisco Unified Communications Manager Release 7.0 or later.

2

+E.164 number format

Private numbering plan

Requires you to do the following:

Configure application dialing rules and directory lookup dialing rules on Cisco Unified Communications Manager.

3

Private numbering plan

Private numbering plan

Requires you to do the following:

Configure normalization rules on OCS.

Configure application dialing rules and directory lookup dialing rules on Cisco Unified Communications Manager.


This chapter deals with options 1 and 2. Appendix A, "Normalization Rules for OCS" deals with option 3.


Note If you choose option 3, you must configure a set of phone number normalization rules on the OCS server. Configuring OCS normalization rules can be an error-prone task, especially for international and enterprise dial plans. For more information about this topic, see Appendix A, "Normalization Rules for OCS".


Dialing Rules Required for Cisco UC Integration for Microsoft Office Communicator

If your Cisco Unified Communications Manager uses a private numbering plan, you must configure the following types of dialing rules in Cisco Unified Communications Manager:

Application Dialing Rules

Directory Lookup Dialing Rules

For detailed conceptual and task-based information on dialing rules, see the Cisco Unified Communications Manager Administration online help or the Cisco Unified Communications Manager Administration Guide and the Cisco Unified Communications Manager System Guide:

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


Note If your Cisco Unified Communications Manager uses dialing rules, you must ensure that Cisco UC Integration for Microsoft Office Communicator and Cisco Unified Client Services Framework can access these dialing rules.


Related Topics

How to Make Cisco Unified Communications Manager Dialing Rules Accessible

Application Dialing Rules

Application dialing rules modify the dial string on outbound calls to conform to the route plan on the Cisco Unified Communications Manager. For Cisco UC Integration for Microsoft Office Communicator, application dialing rules map numbers in the OCS address book to a number format that can be correctly dialed within the context of your Cisco Unified Communications Manager configuration. That is, you must define application dialing rules to map +E.164 numbers to the private numbering plan.

Example Application Dialing Rule for Contacts with North American Numbers

The following table illustrates the application dialing rule that you need to use to resolve +E.164-format numbers to a Cisco Unified Communications Manager private numbering plan that uses six-digit numbers beginning with 8.

 
1
2
3
4
5
6
7
8
9
10
11
12

Number for contact in OCS address book in +E.164 format

+

1

4

0

8

5

5

5

0

1

0

0

Number begins with +1408555

 

Number of digits is 12

Operations performed by application dialing rule

+

1

4

0

8

5

5

5

0

1

0

0

Number of digits to remove is 7

 

Prefix with 8

Dialed number

850100


Example of Application Dialing Rule for Contacts with Spanish Numbers

The following table illustrates the application dialing rule that you need to use to resolve +E.164-format numbers to a Cisco Unified Communications Manager private numbering plan that uses nine-digit numbers beginning with 91.

 
1
2
3
4
5
6
7
8
9
10
11
12

Number for contact in OCS address book in +E.164 format

+

3

4

9

1

2

3

4

5

6

7

8

Number begins with +34

 

Number of digits is 12

Operations performed by application dialing rule

+

3

4

9

1

2

3

4

5

6

7

8

Number of digits to remove is 3

 

No prefix required

Dialed number

912345678


Directory Lookup Dialing Rules

Directory lookup dialing rules transform caller identification numbers into numbers that can be looked up in the directory. For example, if the Cisco Unified Communications Manager reports a call from 85550100, that number must be transformed into the +E.164 format of +14085550100, as stored in LDAP to identify the caller as a contact. If numbers in the LDAP are not in +E.164 format, but the enterprise routable number is stored in LDAP, then the directory lookup dialing rules need to map incoming numbers to the enterprise routable numbers.

For Cisco UC Integration for Microsoft Office Communicator, directory lookup dialing rules map private numbering plan numbers to the number format used in Active Directory. That is, you must define directory lookup dialing rules to transform private numbering plan numbers to +E.164-format numbers.

Example of Directory Lookup Dialing Rule for Contacts with North American Numbers

The following table illustrates the directory lookup dialing rule that you need to use to resolve a number from a Cisco Unified Communications Manager private numbering plan that uses six-digit numbers beginning with 81, to a +E.164-format number.

 
1
2
3
4
5
6
7
8
9
10
11
12

Private numbering plan number from Cisco Unified Communications Manager

 

8

1

0

1

9

9

 

Number begins with 81

 

Number of digits is 6

Operations performed by directory lookup dialing rule

+

1

4

0

8

5

5

5

0

1

9

9

Prefix with +1408555

 

Digits to remove is 2

Resulting +E.164-format number

+14085550199


Example of Directory Lookup Dialing Rule for Contacts with Spanish Numbers

The following table illustrates the directory lookup dialing rule that you need to use to resolve a number from a Cisco Unified Communications Manager private numbering plan that uses nine-digit numbers beginning with 91, to a +E.164-format number.

 
1
2
3
4
5
6
7
8
9
10
11
12

Private numbering plan number from Cisco Unified Communications Manager

 

9

1

2

3

4

5

6

7

9

 

Number begins with 91

 

Number of digits is 9

Operations performed by directory lookup dialing rule

+

3

4

9

1

2

3

4

5

6

7

9

Prefix with +34

 

Digits to remove is 0

Resulting +E.164-format number

+34912345679


How to Configure Cisco Unified Communications Manager Server

Before you configure the Cisco Unified Communications Manager server, read the following topics:

Prerequisites for Configuring Cisco Unified Communications Manager

Cisco Unified Client Services Framework Device Type

To configure the Cisco Unified Communications Manager server for Cisco UC Integration for Microsoft Office Communicator, you must perform the following tasks:

Enabling LDAP Synchronization

Enabling LDAP Authentication

Creating Client Services Framework Devices and Directory Numbers for Users

Adding Users to User Groups and Associating Controlled Devices

How to Configure Cisco Unified IP Phones for Video

Configuring Cisco Unified Communications Manager for Ad-Hoc Video Conferencing

How to Make Cisco Unified Communications Manager Dialing Rules Accessible

Configuring Failover to Cisco Unified Survivable Remote Site Telephony (SRST)

Prerequisites for Configuring Cisco Unified Communications Manager

You must have a properly working Cisco Unified Communications configuration with the following servers:

Cisco Unified Communications Manager server

For information about Cisco Unified Communications Manager servers, 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) server

For information about Cisco TFTP servers, see the Cisco Unified Communications Manager System Guide.

Cisco CTIManager server

For information about Cisco CTIManager servers, see the Cisco Unified Communications Manager System Guide.

Cisco Unified Communications Manager IP Phone (CCMCIP) server

Cisco Unified Client Services Framework Device Type

The Cisco UC Integration for Microsoft Office Communicator requires a new Cisco Unified Communications Manager device type called Cisco Unified 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 Cisco Unified 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.

For information about which releases of Cisco Unified Communications Manager require you to run the COP file to install the Cisco Unified Client Services Framework device type, see the release notes at the following URL:

http://www.cisco.com/en/US/products/ps10317/prod_release_notes_list.html

The COP file is included in the Administration Toolkit for Cisco UC Integration for Microsoft Office Communicator. To access the Administration Toolkit, navigate to Cisco UC Integration for Microsoft Office Communicator from the Download Software page at the following URL:

http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=282588075

What to Do Next

Enabling LDAP Synchronization

Enabling LDAP Synchronization

This procedure allows Cisco Unified Communications Manager to integrate with Active Directory and build the Cisco Unified Communications Manager user database from the same data source where Windows users and Microsoft Office Communicator users are defined.

If you synchronize the Cisco Unified Communications Manager with Active Directory, the Cisco UC Integration for Microsoft Office Communicator user IDs will be the same as the Windows and Microsoft Office Communicator user IDs. If you synchronize the Cisco Unified Communications Manager with Active Directory, you must also enable LDAP authentication. For more information about how to enable LDAP authentication, see Enabling LDAP Authentication.


Note If you choose not to synchronize the Cisco Unified Communications Manager with Active Directory, you must set the value of the ContactService_UseCredentialsFrom registry key to specify the source of the credentials for Cisco UC Integration for Microsoft Office Communicator.


Procedure


Step 1 Select System > LDAP > LDAP System in Cisco Unified Communications Manager Administration.

Step 2 Select Enable Synchronizing from LDAP Server.

Step 3 Select Microsoft Active Directory from the LDAP Server Type list box.

Step 4 Select the LDAP attribute that you want to use as the User ID in Cisco Unified Communications Manager from the LDAP Attribute for User ID list box.

Step 5 Select Save.

Step 6 Select System > LDAP > LDAP Directory.

Step 7 Select Add New.

Step 8 Enter data in the LDAP Directory window as required.

Step 9 Select Save.

Step 10 Select Perform Full Sync Now.

For information about how to synchronize with LDAP, see the LDAP Directory Integration information in the Cisco Unified Communications System Solution Reference Network Design (SRND) guides at the following URL:

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


What to Do Next

Enabling LDAP Authentication

Related Topics

Normalization Rules for OCS, page A-1

Specifying Account Credential Synchronization Value Names, page 3-10

Enabling LDAP Authentication

If you enable LDAP authentication in Cisco Unified Communications Manager, the Active Directory provides authentication services to Cisco Unified Communications Manager by proxy. For example, Cisco Unified Communications Manager can forward authentication requests from the Cisco UC Integration for Microsoft Office Communicator to Active Directory, and Active Directory responds to the request.

Procedure


Step 1 Select System > LDAP > LDAP Authentication in Cisco Unified Communications Manager Administration.

Step 2 Select Use LDAP Authentication for End Users.

Step 3 Select Save.


What to Do Next

Creating Client Services Framework Devices and Directory Numbers for Users

Creating Client Services Framework Devices and Directory Numbers for Users

The Client Services Framework device is required for users who want to use the phone on the computer.

Procedure


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

Step 2 Select Add New.

Step 3 Select Cisco Unified Client Services Framework from the Phone Type list box, then select Next.

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

Field
Description

Device Name

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

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.

Phone Button Template

Select the appropriate 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.

Allow Control of Device from CTI

Uncheck this option.

Client Services Framework does not support Computer Telephony Integration (CTI) servitude.

Device Security Profile

Select the security profile you require for the phone.

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

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

b. Select Generate String.

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

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.


Step 5 Enter any other required information, then select Save.

Step 6 Select the Add a new DN link in the Association Information section on the Phone Configuration window.

Step 7 Enter information for the directory number on the Directory Number Configuration window.

Step 8 Select Save.

Step 9 Select Reset on the Phone Configuration window to reset the phone.

Step 10 Select Associate End Users on the Directory Number Configuration window.

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

Step 12 Select Save.

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

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

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


What to Do Next

Adding Users to User Groups and Associating Controlled Devices

Related Topics

Cisco Unified Client Services Framework Device Type

Adding Users to User Groups and Associating Controlled Devices

Before You Begin

To configure Cisco UC Integration for Microsoft Office Communicator to control the desk phone and soft phone of the user, you must do each of the following:

Select the Allow Control of Device from CTI option when you create the desk phone device for the user in Cisco Unified Communications Manager.

Ensure that the user is added to the appropriate user groups, as described in the following procedure.

Select the Cisco Unified Client Services Framework device and any desk-phone devices as controlled devices for the user, as described in the following procedure.

Procedure


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

Step 2 Select the user that you want to add.

Step 3 Select Add to User Group in the Permissions Information group in the End User Configuration window.

Step 4 Search for "Standard CTI" in the Find and List User Groups window.

Step 5 Select the Standard CTI Enabled user group.

Step 6 If the phone of the user is a Cisco Unified IP Phone 9900 or 8900 series model, also select the Standard CTI Allow Control of Phones supporting Connected Xfer and conf group.

Step 7 If the phone of the user is a Cisco Unified IP Phone 6900 series model, also select the Standard CTI Allow Control of Phones supporting Rollover Mode group.

Step 8 Select Add Selected.

Step 9 Select Device Association in the Device Information group.

Step 10 Search for the devices that you want to associate with the user in the User Device Association window.

Step 11 Select the devices you require, then select Save Selected/Changes.

For example, you might select a device whose type is Cisco Unified Client Services Framework, and a desk-phone device.

Step 12 Select Back to User from the Related Links drop-down list, then select Go.

Step 13 Select Save in the End User Configuration window.


How to Configure Cisco Unified IP Phones for Video

The Client Services Framework device type is always video-enabled, so you do not need to configure devices of this type. However, you must explicitly configure Cisco Unified IP Phones to enable video.

If you want Cisco UC Integration for Microsoft Office Communicator to be able to send and receive video, you must also select the following devices as controlled devices for the user:

The Cisco Unified Client Services Framework device

Any desk-phone devices


Note Only Skinny Client Control Protocol (SCCP) Cisco Unified IP Phones support video with Client Services Framework.


To configure a Cisco Unified IP Phones for video, you must perform the following tasks:

Connecting a Cisco Unified IP Phone to the Network and Your Computer

Enabling Video for a Cisco Unified IP Phone

Adding Users to User Groups and Associating Controlled Devices

Securing IP Phones

For more information about how to configure Cisco UC Integration for Microsoft Office Communicator for video, see the release notes for the product at the following URL:

http://www.cisco.com/en/US/products/ps10317/prod_release_notes_list.html

For more detailed information about IP video telephony in Cisco Unified Communications Manager, please refer to the Cisco Unified Communications System Release 8.x SRND at the following URL:

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

Connecting a Cisco Unified IP Phone to the Network and Your Computer

Procedure


Step 1 Connect the SW port on the Cisco Unified IP Phone to the network.

Step 2 Connect the PC port on the Cisco Unified IP Phone to the controlling PC with an Ethernet cable.


What to Do Next

Enabling Video for a Cisco Unified IP Phone

Enabling Video for a Cisco Unified IP Phone

Procedure


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

Step 2 Find the device that you want to configure.

Step 3 Click on the Device Name.

Step 4 Scroll to the Product Specific Configuration Layout section.

Step 5 Select Enabled from the PC Port drop-down list.

Step 6 Select Enabled from the Video Capabilities drop-down list.

Step 7 Select Save.

When video is enabled on the phone, a video icon is displayed in the lower-right corner of the LCD screen.


What to Do Next

Adding Users to User Groups and Associating Controlled Devices

Related Topics

Securing IP Phones

Securing IP Phones

For information about how to secure your IP phone device, see the Cisco Unified Communications Manager Security Guide at the following URL:

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

Configuring Cisco Unified Communications Manager for Ad-Hoc Video Conferencing

To enable ad-hoc video conferencing on your Cisco Unified Communications system, you must do the following:

Configure a conference bridge. The conference bridges supported are:

Cisco Unified MeetingPlace

Cisco Unified Video Conferencing (CUVC)

Cisco IP Video Conferencing (IPVC) 35xx series MCU

For detailed task-based information about how to configure a conference bridge, see the Configuration Guide for Cisco Unified MeetingPlace:

http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html

Configure a media resource group and a media resource group list. For information about how to configure a media resource group and a media resource group list, see the Cisco Unified Communications Manager Administration online help or the Cisco Unified Communications Manager Administration Guide:

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

Configure the devices of your users to use the media resource group list that contains the conference bridge. For information about how to configure the devices of your users, see the Cisco Unified Communications Manager Administration online help or the Cisco Unified Communications Manager Administration Guide:

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

(Optional) Specifying a Minimum Number of Video-Capable Participants for Ad-Hoc Conferences

If you enable ad-hoc video conferencing on your Cisco Unified Communications system, you can also specify a minimum number of video-capable participants for ad-hoc conferences. When an ad-hoc conference starts, the conference uses an audio bridge or a video bridge, depending on the value in this setting.

For example, if you set this setting to 2, a minimum of two participants in the conference must have video-enabled devices. If at least two participants do not have video-enabled devices, then the conference becomes an audio-only conference. The participants cannot change the conference to video after this happens.

Procedure


Step 1 Select System > Service Parameters in Cisco Unified Communications Manager Administration.

Step 2 Select your Cisco Unified Communications Manager server from the Server drop-down list.

Step 3 Select the appropriate Cisco Unified Communications Manager service from the Service drop-down list.

Step 4 Enter the minimum number of video-capable participants in the Minimum Video Capable Participants To Allocate Video Conference field in the Clusterwide Parameters (Feature - Conference) section.

Step 5 Select Save.


How to Make Cisco Unified Communications Manager Dialing Rules Accessible

If your Cisco Unified Communications Manager uses dialing rules, you must ensure that Cisco UC Integration for Microsoft Office Communicator and Client Services Framework can access these dialing rules.

You must run a COP file to generate copies of the dialing rules in XML format, which Cisco UC Integration for Microsoft Office Communicator and Client Services Framework can access. You can get the COP file, called cmterm-CUPC-dialrulewizard.cop, from the Administration Toolkit. To access the Administration Toolkit, navigate to Cisco UC Integration for Microsoft Office Communicator from the Download Software page at the following URL:

http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=282588075


NoteEvery time you update the dialing rules in your Cisco Unified Communications Manager, you must run the COP file again, to ensure that Cisco UC Integration for Microsoft Office Communicator and Client Services Framework can access the updated dialing rules.

You must run the COP file on each Cisco Unified Communications Manager that runs a TFTP server.


To make the Cisco Unified Communications Manager dialing rules accessible by Cisco UC Integration for Microsoft Office Communicator and Client Services Framework, you must perform the following tasks:

Verifying That Dialing Rules Are Configured on Cisco Unified Communications Manager

Generating Copies of the Dialing Rules

Verifying That Copies of the Dialing Rules Were Generated

Restarting the TFTP Service

Ensuring That Cisco UC Integration for Microsoft Office Communicator Clients Are Restarted

Verifying That Dialing Rules Are Configured on Cisco Unified Communications Manager

Procedure


Step 1 Select Call Routing > Dial Rules > Application Dial Rules in Cisco Unified Communications Manager Administration.

Step 2 Search for the dialing rules in the Find and List Application Dial Rules window.

Step 3 Verify that application dialing rules are found.

Step 4 Select Call Routing > Dial Rules > Directory Lookup Dial Rules in Cisco Unified Operating System Administration.

Step 5 Search for the dialing rules in the Directory Lookup Dial Rule Find and List window.

Step 6 Verify that directory lookup rules are found.

If there are no application dialing rules or directory lookup dialing rules on your Cisco Unified Communications Manager, you do not need to make dialing rules accessible by Cisco UC Integration for Microsoft Office Communicator.



Tip To ensure that the dialing rules are working properly, try making a call from Cisco UC Integration for Microsoft Office Communicator.


What to Do Next

Generating Copies of the Dialing Rules

Generating Copies of the Dialing Rules

You must run a COP file to generate copies of the dialing rules in XML format. You can get the COP file, called cmterm-CUPC-dialrulewizard.cop, from the Administration Toolkit. To access the Administration Toolkit, navigate to Cisco UC Integration for Microsoft Office Communicator from the Download Software page at the following URL:

http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240

Procedure


Step 1 Select Software Upgrades > Install/Upgrade in Cisco Unified Operating System Administration.

Step 2 Specify the location of the COP file in the Software Installation/Upgrade window.

Step 3 Select Next.

Step 4 Select the appropriate file from the Available Software list box.

Step 5 Select Next.

Step 6 Select Install.


What to Do Next

Verifying That Copies of the Dialing Rules Were Generated

Verifying That Copies of the Dialing Rules Were Generated

Procedure


Step 1 Select Software Upgrades > TFTP File Management in Cisco Unified Operating System Administration.

Step 2 Search for a directory that begins with CUPC in the TFTP File Management window.

Step 3 Verify that the following files are found:

AppDialRules.xml

DirLookupDialRules.xml


What to Do Next

Restarting the TFTP Service

Restarting the TFTP Service

After you verify the generation of the copies of the dialing rules, restart the TFTP service. You must restart the TFTP service on every server on which you ran the COP file.

For information about how to restart TFTP services, see Cisco Unified Serviceability Administration Guide at the following URL:

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

What to Do Next

Ensuring That Cisco UC Integration for Microsoft Office Communicator Clients Are Restarted

Ensuring That Cisco UC Integration for Microsoft Office Communicator Clients Are Restarted

Procedure


Step 1 Select in the Microsoft Office Communicator title bar.

Step 2 Select Tools > Stop Cisco UC.


Note It can take approximately 2 minutes for the cucsf.exe process to stop. Use the Task Manager to check if the process has stopped before proceeding to Step 3.


Step 3 Select in the Microsoft Office Communicator title bar.

Step 4 Select Tools > Start Cisco UC.

The Cisco UC Integration for Microsoft Office Communicator client and the cucsf.exe process are automatically restarted.


Configuring Failover to Cisco Unified Survivable Remote Site Telephony (SRST)

Cisco UC Integration for Microsoft Office Communicator supports failover to Cisco Unified Survivable Remote Site Telephony (SRST) to keep calls connected if Cisco Unified Communications Manager becomes unavailable.

Procedure


Step 1 Select System > SRST in Cisco Unified Communications Manager Administration.

Step 2 Select Add New and specify the SRST reference information.

Step 3 Select System > Device Pool.

Step 4 Select the device pool for the target office.

Step 5 In the Roaming Sensitivity Settings section, select the SRST reference that you created in Step 2 from the SRST Reference drop-down list.

Step 6 Select Save.



Note To configure an SRST router that connects directly to the target Branch office LAN and is the default gateway for the branch office LAN, you can omit steps 1-2, and in the target office Device Pool Configuration > Roaming Sensitivity Settings section, select Use Default Gateway from the SRST Reference drop-down list.


How To Configure Cisco Unified MeetingPlace

Before You Begin

You must have a working Cisco Unified MeetingPlace Release 8.0 server configured in one of the following modes:

Software Mixing Mode (SMS Mode). This mode supports ad-hoc and scheduled video conferences in all video resolutions, that is, QCIF, CIF, VGA, and 720p HD.

Hardware Mixing Mode (HMS Mode) using an external hardware mixer. This mode supports scheduled and reservationless meetings only.

For more information about how to configure video conferences on Cisco Unified MeetingPlace Release 8.0, see the documentation at the following URL:

http://www.cisco.com/en/US/products/sw/ps5664/ps5669/tsd_products_support_series_home.html

To configure Cisco Unified MeetingPlace, you must perform the following tasks:

Configuring a Cisco Unified MeetingPlace Application Server for Ad-Hoc Video Conferencing

Configuring a Cisco Unified MeetingPlace Application Server for Scheduled Video Conferencing

Adding Custom Cisco Unified MeetingPlace Template Files to a Cisco Unified MeetingPlace 7.x Web Server

Meeting Types and Authentication

Reservationless Meetings

If reservationless meetings are enabled for users, users can start a meeting from Cisco UC Integration for Microsoft Office Communicator. For these meetings, Cisco Unified MeetingPlace is the front-end server. Cisco UC Integration for Microsoft Office Communicator schedules the meeting through Cisco Unified MeetingPlace.

Users can have only one reservationless meeting at a time. If the reservationless meeting of the user is in use at the time the user starts the meeting from Cisco UC Integration for Microsoft Office Communicator, their existing reservationless meeting is used.

To avoid this behavior, users must either end their reservationless meeting before they start a meeting, or ask their administrator to disable reservationless meetings in their Cisco Unified MeetingPlace user profile.

Meeting passwords are ignored for reservationless meetings.

Authentication

Cisco UC Integration for Microsoft Office Communicator includes support for all types of Cisco Unified MeetingPlace authentication, except for Trust External Authentication.

Reserving Audio and Video Resources

When a user starts a meeting, Cisco Unified MeetingPlace reserves audio resources, but does not reserve any video resources.

Configuring a Cisco Unified MeetingPlace Application Server for Ad-Hoc Video Conferencing

Procedure


Step 1 Select System Configuration > Call Configuration in Cisco Unified MeetingPlace Administration Center.

Step 2 Select Ad-Hoc Cisco Unified Communications Manager Configuration.

Step 3 Enter the IP address and port for your Cisco Unified Communications Manager in the Primary TFTP server fields.

Step 4 Select Save.

Step 5 Select System Configuration > Media Resource Configuration.

Step 6 Select Yes in the Enable ad-hoc video drop-down list.

Step 7 Select one of the H.264 options from the Ad-hoc video mode drop-down list.

For mobile video, select H.264 AVC (Level 1.1). For video on computers, select H.264 AVC (Level 1.3), H.264 AVC (Level 3.0), or H.264 AVC (Level 3.1).


Note The setting that you select here is used for all video endpoints joining all ad-hoc conferences. If a video endpoint does not support the specified profile, this endpoint joins the conference in audio-only.


Step 8 Select Save.


Related Topics

Configuring Failover to Cisco Unified Survivable Remote Site Telephony (SRST)

Configuring a Cisco Unified MeetingPlace Application Server for Scheduled Video Conferencing

Procedure


Step 1 Select User Configuration > User Groups in Cisco Unified MeetingPlace Administration Center.

Step 2 Select Edit next to the name of the User Group that you want to configure for scheduled video conferencing.

Step 3 In the Video Preferences section, select one of the following options from the Available video types drop-down list:

Mobile

Compatibility

High Quality

HD

This setting determines the type of video for scheduled video conferencing.

Step 4 Select Save.


Adding Custom Cisco Unified MeetingPlace Template Files to a Cisco Unified MeetingPlace 7.x Web Server

If your Cisco Unified Communications system uses Cisco Unified MeetingPlace Release 7.x, you must install the following files on the Cisco Unified MeetingPlace Web server:

CSFGetProfileSuccess.tpl

CSFScheduleSuccess.tpl

You can get the above files from the Administration Toolkit. To access the Administration Toolkit, navigate to Cisco Unified Communications Integration for Microsoft Office Communicator from the Download Software page at the following URL:

http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240

You can copy these files to the correct location on the Cisco Unified MeetingPlace Web server. You do not need to restart the server. The default location for these files is as follows:

C:\Program Files\Cisco Systems\MPWeb\Template

How to Configure Cisco Unity Server for Voicemail Access

Cisco Unity provides Cisco UC Integration for Microsoft Office Communicator users with the ability to view, play, sort, and delete voicemail messages from the Cisco UC Integration for Microsoft Office Communicator interface.

Before You Begin

Install and configure a supported release of Cisco Unity.

Integrate Cisco Unified Communications Manager and Cisco Unity. Both servers must be installed and running to configure voicemail ports.

If you plan to use SSL to provide secure transmission with the mailstore server, you must set up Cisco Unity to use SSL during the installation or upgrade (or at any time after the installation or upgrade is complete). You must designate a server to act as your certificate authority, submit a certificate request, issue the certificate, and install it on the Cisco Unity server.

Install the Cisco Unity VoiceMail Web Service (VMWS).

Set the Distributed Component Object Model (DCOM) permissions.

For more information, see the following topics:

Installing the Voicemail Web Service (VMWS)

Setting the DCOM Permissions

Testing That the Voicemail Web Service Is Accessible

Installing the Voicemail Web Service (VMWS)

Procedure


Step 1 To install the Cisco Unity Voicemail Web Service, go to the following URL:

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

Step 2 Select the Download Software link, navigate to your Cisco Unity version, select Unity System Software, and select the installation file for VMWS.

Step 3 Run the installation file and follow the instructions in the installation wizard to install VMWS.


What To Do Next

Setting the DCOM Permissions

Setting the DCOM Permissions

Use the Cisco Unity Permissions Wizard to grant DCOM permissions to the accounts that you require.

We recommend that you download and run the latest version of the Permissions wizard that is applicable to your version of Cisco Unity. The Permissions wizard is available at:

http://www.ciscounitytools.com/Applications/Unity/PermissionsWizard/Unity50/PW50.html

For information on granting permissions with the Permissions wizard, see the Permissions wizard Help file PWHelp_<language>.htm that is included with the version of the Permissions wizard that you are using.

Testing That the Voicemail Web Service Is Accessible

Procedure


Step 1 Start a browser.

Step 2 Use the HTTP or HTTPS protocol to access the URL of the voicemail web service on the Cisco Unity server.

You can access the URL structured as follows:

http://<domain-name-of-Cisco Unity-server>/vmws/vmws.dll?Handler=GenAuthenticationWSDL

For example, access a URL similar to the following:

http://unityserver/vmws/vmws.dll?Handler=GenAuthenticationWSDL

If the source of an XML file is displayed, the voicemail web service has been correctly installed.


How to Configure Cisco Unity Connection Server for Voicemail Access

Cisco Unity Connection provides Cisco UC Integration for Microsoft Office Communicator users with the ability to view, play, sort, and delete voicemail messages from the Cisco UC Integration for Microsoft Office Communicator interface.

Before You Begin

Install and configure a supported release of Cisco Unity Connection.

Integrate Cisco Unified Communications Manager and Cisco Unity Connection. Both servers must be installed and running to configure voicemail ports.

Configuring User Access

Procedure


Step 1 Set up a new or existing class of service in Cisco Unity Connection Administration to enable Internet Mail Access Protocol (IMAP) client access to voice messages, as follows:

a. Expand Class of Service in the left pane.

b. Select Class of Service.

c. Select the display name of the applicable class of service in the Search Results table, in the Search Class of Service window.

d. For all other ports and protocols, perform the following steps:

Check Allow Users to Access VoiceMail Using an IMAP Client under Licensed Features.

Select Allow Users to Access Message Bodies.

Check Allow Users to Use Unified Client to Access Voice Mail under Features.

e. Select Save.

Step 2 In Cisco Unity Connection Serviceability, select Tools > Service Management > Optional Services.

a. Validate that the Activate Status of the Connection IMAP Server is Activated.

b. Validate that the Service Status of the Connection IMAP Server is Started.

Step 3 Configure the user:

If the users are existing Cisco Unity Connection users, add them to the Cisco Unified Communications Manager database. Proceed to Step 4.

If the user is a new Cisco UC Integration for Microsoft Office Communicator user, add the user to Cisco Unified Communications Manager database and Cisco Unity Connection.

Step 4 Create a Connection user account on the Cisco Unity Connection server with a voice mailbox for each Cisco UC Integration for Microsoft Office Communicator user.


Note To avoid problems with conflicting user IDs, consider importing users from the Cisco Unified Communications Manager database where possible.


Step 5 If one does not already exist, specify a web application password in Cisco Unity Connection for the applicable user accounts.

Step 6 You must populate the Cisco Unity Connection SMTP proxy addresses for subscribers if either of the following is true:

The voice message system and the Microsoft Office Communicator directory are not in the same domain.

The user IDs of the Cisco Unity Connection subscribers are different to the Cisco Unified Communications Manager user IDs or Windows and Microsoft Office Communicator user IDs.


Enabling Secure Access to Voice Messages

Procedure


Step 1 Enable secure messaging in Cisco Unity Connection Administration as follows:

a. Expand Class of Service in the left pane.

b. Select an existing Class of Service from the right pane.

c. Select an option from Require Secure Messaging in the Message Options section to enable secure messages.

Step 2 (Optional) Specify how to handle unidentified caller message security for your users as follows:

a. Expand Users in the left pane.

b. Select Users.

c. Select the alias of a user.

d. Select Edit > Message Settings.

e. Check Mark Secure in Unidentified Callers Message Security.