Polycom ReadiConvene Quick reference guide

Polycom–Microsoft
Integrated Solution
Deployment Guide
Phase 3

Copyright © 2006 Polycom, Inc.
All Rights Reserved
Catalog No. DOC2222A
Version 1
Proprietary and Confidential
The information contained herein is the sole intellectual property of Polycom, Inc. No distribution, reproduction or unauthorized
use of these materials is permitted without the expressed written consent of Polycom, Inc. Information contained herein is subject
to change without notice and does not represent commitment of any type on the part of Polycom, Inc. Polycom and Accord are
registered trademarks of Polycom, Inc.
Notice
While reasonable effort was made to ensure that the information in this document was complete and accurate at the time of
printing, Polycom, Inc., cannot assume responsibility for any errors. Changes and/or corrections to the information contained in
this document may be incorporated into future issues.

Polycom-Microsoft Deployment Guide
i
Table of Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
About this Guide ....................................................................................1-2
Microsoft—Polycom Environment ...................................................... 1-3
Environment Requirements .................................................................. 1-5
Microsoft—Polycom Environment Setting . . . . . . .2-1
Microsoft—Polycom Environment Configuration ............................ 2-2
Procedure 1—Setting Up a Server As the Windows Domain
Controller ......................................................................................... 2-2
Procedure 2—Extending the Active Directory Schema ............ 2-3
Procedure 3—Live Communications Server Installation and
Activation ......................................................................................... 2-6
Procedure 4—LCS User Account Definition and Client Access
Configuration .................................................................................. 2-7
Procedure 5—Creating a SIP Network Service in the MGC
Environment ..................................................................................2-11
Procedure 6—Defining the MGC Unit as Trusted in the LCS 2-22
Procedure 7— Setting the Static Routes Between the LCS and the
MGC Unit ....................................................................................... 2-24
Procedure 8—Defining Additional Conferencing Components in
the MGC Environment .................................................................2-27
Defining a Meeting Room in the MGC Manager
Application ............................................................................. 2-29
Defining an Entry Queue in the MGC Manager
Application ............................................................................. 2-30
Endpoint Settings ..................................................................................2-33
VSX Settings ................................................................................... 2-33
Enabling SIP for the Endpoint ............................................. 2-33
Network Configuration ......................................................... 2-34
PVX Settings ..................................................................................2-35
Defining a User Account in the LCS .......................................... 2-37
Adding the Endpoint to Office Communicator and Windows
Messenger Buddy List .................................................................. 2-39
Configuring for Office Communicator Multipoint Conference

Table of Contents
ii
Capacity/Scalability ............................................................................ 2-40
Microsoft—Polycom Meeting Scenarios . . . . . . . . .3-1
Point-to-Point Meeting .......................................................................... 3-2
Multipoint Conferencing—Preparations ............................................ 3-3
Enabling Office Communicator Conferencing Features ........... 3-4
Enabling Direct Conferencing from within Office
Communicator in Windows ................................................... 3-4
Enabling video calls with Office Communicator ................ 3-8
Enabling data sharing with Office Communicator ............. 3-8
Bandwidth Allocation Modification ................................... 3-10
Modifying Windows Hosts List to Include the LCS ............... 3-12
Signing-in Windows Messenger and Office Communicator
Clients to the Live Communications Server ............................. 3-14
Office Communicator Configuration .................................. 3-14
Windows Messenger Configuration ................................... 3-16
Defining the Conferencing Properties in your Office
Communicator .............................................................................. 3-18
Adding a Meeting Room or an Entry Queue to the Buddy
List .................................................................................................. 3-20
Office Communicator ............................................................ 3-20
Windows Messenger ............................................................. 3-22
Adding Endpoints to Office Communicator and Windows
Messenger Buddy Lists ................................................................ 3-24
Office Communicator ............................................................ 3-24
Windows Messenger ............................................................. 3-24
Multipoint Conferencing Scenarios ................................................... 3-25
Meet Me—Starting an Ongoing Video Conference from Windows
Messenger and Office Communicator ....................................... 3-25
Joining the Ongoing Conference ......................................... 3-28
MGC Manager Monitoring .................................................. 3-29
Single Dial Entry Queue .............................................................. 3-30
Joining the Ongoing Conference ......................................... 3-32
MGC Manager Monitoring .................................................. 3-33
Ad-hoc Entry Queue and Conference Creation ....................... 3-34
Dial-out to Conference Participants ........................................... 3-35
Joining the Conference .......................................................... 3-36

Polycom-Microsoft Deployment Guide
iii
Escalating Windows Messenger or Office Communicator IM
Multiparty Session to an Audio/Video Conference ................ 3-37
Windows Messenger ............................................................. 3-37
Office Communicator ............................................................ 3-40
Office Communicator New Multipoint Conferencing Scenarios Based
on SIP-CX Protocol ............................................................................... 3-44
Starting a New Conference Directly from within Office
Communicator .............................................................................. 3-44
An Office Communicator User Invites another Office
Communicator Contact to the Conference ................................3-47
An Office Communicator User Joins an Existing Conference 3-49
An Office Communicator User Dials out to another Office
Communicator User ..................................................................... 3-51
Adding Audio/Video to an Office Communicator Multiparty IM
Session ............................................................................................ 3-53
Scheduling a Meeting—Office Communicator–Outlook
Integration ...................................................................................... 3-56
Starting a Data Sharing Session ..................................................3-58
Conference Control via Office Communicator SIP-CX Protocol ...3-61
Ad-hoc Conferencing and Active Directory
Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1
Ad Hoc Conferencing Requirements ................................................... 4-3
Ad Hoc Conferencing and Validation Scenarios ...............................4-4
Ad Hoc Conferencing without Active Directory Validation ... 4-4
Ad Hoc Entry Queue with Active Directory Validation ...........4-5
Ad Hoc Entry Queue with Conference Password Validation with
Active Directory .............................................................................. 4-6
Defining the Ad Hoc Conferencing Components in the MGC
Environment ............................................................................................ 4-9
MCU Configuration to Access the External Database
Application ...................................................................................... 4-9
Entry Queue Service with Access to the External Database ... 4-10
IVR Service with Access to the External Database
Application .................................................................................... 4-11
Profiles ............................................................................................ 4-12
Defining Profiles .................................................................... 4-12
Ad Hoc-enabled Entry Queue ....................................................4-13

Table of Contents
iv
Known Limitations . . . . . . . . . . . . . . . . . . . . . . . . .5-1
Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1
Office Communicator Callback Model .............................................. A-1
Examples .................................................................................. A-3
Canceling the SIP-CX Environment Setting ...................................... A-4

1-1
1
Overview
This document describes the Microsoft–Polycom integrated solution,
Phase 3. With this release, Microsoft–Polycom integrated solution offers
high quality point-to-point and multipoint voice, and video
conferencing calls (in any combination) across communication devices,
applications and services. This solution empowers users to connect and
share information in real-time regardless of type of call. Polycom
enhances Microsoft’s environment by:
• enabling Polycom endpoints (VSX and PVX) to be added to Office
Communicator and Windows Messenger buddy list
• bridging between Microsoft SIP-only environment and legacy
ISDN, PSTN and H.323 endpoints
• displaying the user/endpoint presence in the buddy list
• starting a point-to-point or multipoint meeting directly from
Polycom endpoints, Office Communicator and Windows
Messenger.
In Phase 3 that is based on the MGC software version 7.5, the integrated
solution fully supports Microsoft SIP-CX conferencing capabilities,
giving Office Communicator users complete conference control from
within the Office Communicator client; enabling them to monitor their
ongoing conference, invite others to join their conference and schedule a
conference. It also enables Office Communicator users to select the
conferencing device with which to join the media portion of the
conference: Office Communicator, phone, video conferencing system or
a mobile 3G videophone.

Overview
1-2
About this Guide
This document provides the setup information required to install and
configure the various elements of the Microsoft—Polycom environment
and how to start and run point-to-point and multipoint meetings in the
various scenarios.
This document includes these chapters:
•Chapter 1, “Overview,” describes the Microsoft—Polycom
environment.
•Chapter 2, “Microsoft—Polycom Environment Setting,” provides
step-by-step instructions for installing and setting up the Microsoft
LCS 2005, the Active Directory server, creating user accounts in the
LCS, defining Polycom conferencing elements and setting Polycom
endpoints to use SIP communication.
•Chapter 3, “Microsoft—Polycom Meeting Scenarios,” describes the
various ways to start an ongoing audio and video point-to-point or
multipoint meeting.
•Chapter 4, “Ad-hoc Conferencing and Active Directory
Integration,” provides step-by-step instructions for configuring the
MCU to ad-hoc conferencing and using the Active Directory to
validate the participant rights to start a new conference.
•Appendix A, “Known Limitations”

Polycom-Microsoft Deployment Guide
1-3
Microsoft—Polycom Environment
Microsoft—Polycom integrated solution offers high quality point-to-point
and multipoint voice and video conferencing calls (in any combination)
across communication devices, applications and services. This solution
empowers users to connect and share information in real-time regardless
of location or type of call.
Microsoft—Polycom environment combines the presence awareness and
instant messaging capabilities of Microsoft® Office Live Communications
Server and Windows® Messenger and Office Communicator with
Polycom’s widely installed ViewStation EX, FX, PVX and VSX desktop
and group video conference systems; MGC voice and video bridges.
The Polycom MCU acts as a video conferencing server that can connect
between PC users (SIP), video conferencing devices, and legacy video
conferencing devices such as those based on H.320 and H.323. The
Microsoft—Polycom environment is scalable and can support several
MCUs.
Figure 1-1 shows the Microsoft—Polycom environment with its elements.
Figure 1-1 Microsoft—Polycom Environment

Overview
1-4
Microsoft SIP-CX protocol is supported by the Polycom MGC
environment, enabling the MGC unit to serve as a conferencing server
that allows Office Communicator users to initiate and join conferences as
well as control and monitor ongoing conferences.
Microsoft—Polycom environment is scaleable and you can use several
MCUs as conferencing servers.
Table 1-1 Elements of the Microsoft—Polycom Environment
Element Description
Microsoft Elements
Microsoft Live
Communications
Server (LCS)
Provides a scalable, enterprise platform for presence
awareness and instant messaging based on SIP protocol.
LCS 2005 comes in two configurations, Standard Edition
and Enterprise edition. Both editions require Microsoft
Active Directory. The Standard Edition is primarily for
small businesses and the Enterprise Edition is deployed
mainlyin medium to large organizations. Both editionsare
supported by Microsoft–Polycom solution.
•LCS Standard Edition supports up to 15,000
simultaneous users and provides a stand-alone
presence engine and IM server, which both run on a
single Windows 2003 Server. MSDE provides the user
information database.
•LCS Enterprise Edition can consist of two or more
LCS Enterprise Edition servers connected to a
separate, shared SQL server database.
Active Directory Active Directory directory service is used by the Live
Communications Server to manage the identities and
relationships that make up network environments. It
includes the userobject thatallows a unified user name to
be used across multiple home servers. In addition, Active
Directory acts as the central authority for network security.
Office
Communicator
and Windows
Messenger
Office Communicator and Windows Messenger enable
instant communication with co-workers all around the
world from your computer using text chat, voice and video
communication. Office Communicator and Windows
Messenger gives you control over who you talk to, and
when, by letting you view the status of buddies, and add
new buddies to your contact list.

Polycom-Microsoft Deployment Guide
1-5
Environment Requirements
The following software versions are required to enable the Microsoft—
Polycom integrated solution:
• Microsoft LCS 2005 SP1
• Office Communicator version 1.0
• Windows Messenger version 5.1
• MGC unit software version 7.5
• Polycom PVX version 8.0.1
• Polycom VSX version 8.0.3
Polycom Elements
Polycom Endpoint All Polycom video endpoints supporting SIP (PVX and
VSX family of room systems) and legacy endpoints
supporting H.323 and H.320.
Polycom MCU
(MGC family) Enables multipoint audio and video conferencing over IP (SIP and H.323), ISDN and PSTN networks using any
endpoint.
Table 1-1 Elements of the Microsoft—Polycom Environment (Continued)
Element Description

Overview
1-6

2-1
2
Microsoft—Polycom
Environment Setting
Point-to-point and multipoint audio and video meetings can be initiated
from Office Communicator, Windows Messenger and Polycom video
endpoints (VSX and PVX) when the following configuration procedures
have been completed:
1Setting up a Server as a Windows Domain Controller.
2Extending the Active Directory schema.
3Live Communications Server installation and activation.
4LCS Users definition and Client Access configuration.
5Defining a SIP Network Service in the MGC environment (on the
MGC unit using the MGC Manager application).
6Configuring the MGC unit as trusted in the LCS.
7Setting Static Routes in the LCS.
8Defining additional conferencing components in the MGC
environment; defining Meeting Rooms and Entry Queues.
In addition, this chapter describes Polycom endpoint configuration to
enable SIP calls.
End user’s computer and Office Communicator settings are described in
Chapter 3.
The Office Communicator Callback model and the MGC flag settings to enable
this model are described in Appendix A.
The procedure for canceling the SIP-CX Environment Setting in the MGC is
also described in Appendix A.

Microsoft—Polycom Environment Setting
2-2
Microsoft—Polycom Environment
Configuration
This section describes the required procedures to set up the Microsoft and
Polycom entities to start and run point-to-point and multipoint audio and
video conferences from Office Communicator, Windows Messenger and
Polycom video endpoints (VSX and PVX).
Procedure 1—Setting Up a Server As the Windows Domain
Controller
To set up the Windows Domain Controller:
1Install Windows 2000 Server or Windows Server 2003 on the Server.
2Click Start->Run
3In the Run dialog box, enter dcpromo.
The Active Directory Installation wizard opens.
4In the Welcome screen, click Next.
5In the Domain Controller Type window, select Domain Controller for
a New Domain and click Next.
6In the Create New Domain window, select Create Domain in a new
forest and click Next.
7In the New Domain Name window, enter the domain name (for
example, polycom.com) and click Next.
8In the NetBIOS Domain Name window, enter the NetBIOS name
(default) and click Next.
9In the Permissions window, select Permission compatible only with
Windows 2000 or Windows Server 2003 operating systems (default
setting) and click Next.
•This procedure can be skipped if a Domain Controller is already installed in
your environment.
•The Domain Controller and the Live Communication Server can be installed
on different computers or on the same computer.

Polycom-Microsoft Deployment Guide
2-3
10 In the DNS Registration Diagnostics window, select Install and
Configure the DNS server option and click Next.
The Active Directory is configured by the wizard. At the end of this
process, the domain controller is configured and PCs can be assigned
to this domain.
Procedure 2—Extending the Active Directory Schema
Before you deploy Live Communications Server, you must prepare the
Active Directory® directory service. The following procedure is specific
to deployment in a single forest with a single domain.
As the Live Communications Server 2005 is installed in the forest root
rather than in another domain, Domain Add to Forest Root operation can be
skipped.
To extend the Active Directory Schema for LCS 2005:
1Log on to the domain controller (server A) as an administrator.
2Start the Live Communications Server 2005 Setup from the domain
controller server.
The Live Communication Server wizard opens.
This step can be skipped if a DNS Server is already installed in your
environment.

Microsoft—Polycom Environment Setting
2-4
3Click Standard Edition Server.

Polycom-Microsoft Deployment Guide
2-5
4Click Prep Schema.
5Follow the wizard’s on-screen instructions, and then click Finish.
6Click Prep Forest, and follow the wizard’s instructions.
7Follow the wizard’s on-screen instructions, and then click Finish.
8Click Prep Domain.
9Follow the wizard’s on-screen instructions, and then click Finish.

Microsoft—Polycom Environment Setting
2-6
Procedure 3—Live Communications Server Installation and
Activation
1If the LCS 2005 is installed on a computer other than the one used for
the Domain Controller, log on to the second server (LCS Server) as an
administrator. Otherwise, skip this step.
2Start the Live Communications Server 2005 Setup.
The Live Communication Server wizard opens.
3Click Standard Edition Server.
4Click Install Files for Live Communications Server.
5Follow the wizard on-screen instructions with the following:
6In the Server Activation window, click Yes.
7In the Welcome to the Activate Live Communications Server wizard, click
Next.
—In the Select Account page, enter a new or existing service account
(LCS Service is listed by default) and specify and confirm the
password.
—If you specify a new account, the wizard creates and configures
this account automatically.
8Click Next.
9In the Enable IM Archiving page, verify that the check box is cleared,
and then click Next.
10 In the Start Service Option page, verify that the Start the service after
activation check box is selected.

Polycom-Microsoft Deployment Guide
2-7
Procedure 4—LCS User Account Definition and Client Access
Configuration
Office Communicator, Windows Messenger and Polycom endpoint users
must be defined in the LCS and sign-in. Point-to-point meetings can be
started from Office Communicator and Windows Messenger using
Polycom endpoints if these endpoints are registered as users in the LCS.
Multipoint audio and video conferencing is available if Meeting Rooms
and Entry Queues are created in the MGC Manager application and are
also defined as users in the LCS.
To define a new user account:
1Expand the Active Users and Computers tree.
2Right-click the Users folder, click New, and then click User.

Microsoft—Polycom Environment Setting
2-8
3In the New Object - User window, enter the user general parameters,
such as, the user first and last name and select the name of the
domain defined in the previous steps.
If you are defining an account for a Meeting Room or Entry Queue,
enter the Meeting Room or Entry Queue name as the user name. For
example, if the name of the Meeting Room is Sales Weekly, enter the
user First Name as Sales, Last Name as Weekly, Full Name as
SalesWeekly and the Logon Name as SalesWeekly. For a detailed
description of Meeting Room and Entry Queue definition procedure,
see "Procedure 8—Defining Additional Conferencing Components in
the MGC Environment” on page 2-27.
4Click Next.
The MGC environment is case sensitive to Conference, Meeting Room and
Entry Queue names, therefore, make sure to use the same name spelling in the
LCS and the MGC Manager.