User manual POLYCOM READICONVENE - SOFTWARE 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 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 i Table of Contents 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 ii Polycom-Microsoft Deployment Guide 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 iii Table of Contents 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 iv 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. 1-1 Overview 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" · · · 1-2 Polycom-Microsoft Deployment Guide 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 1-3 Overview 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 Element 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 mainly in medium to large organizations. Both editions are supported by Microsoft­Polycom solution. Elements of the Microsoft--Polycom Environment Description · 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 user object that allows 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 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. Office Communicator and Windows Messenger 1-4 Polycom-Microsoft Deployment Guide Table 1-1 Element Elements of the Microsoft--Polycom Environment (Continued) Description 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. Enables multipoint audio and video conferencing over IP (SIP and H.323), ISDN and PSTN networks using any endpoint. Polycom MCU (MGC family) 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 1-5 Overview 1-6 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: 1 2 3 4 5 6 7 8 Setting up a Server as a Windows Domain Controller. Extending the Active Directory schema. Live Communications Server installation and activation. LCS Users definition and Client Access configuration. Defining a SIP Network Service in the MGC environment (on the MGC unit using the MGC Manager application). Configuring the MGC unit as trusted in the LCS. Setting Static Routes in the LCS. Defining 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. 2-1 Microsoft--Polycom Environment Setting 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 · · 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. To set up the Windows Domain Controller: 1 Install Windows 2000 Server or Windows Server 2003 on the Server. 2 3 4 5 6 7 8 9 Click Start->Run In the Run dialog box, enter dcpromo. The Active Directory Installation wizard opens. In the Welcome screen, click Next. In the Domain Controller Type window, select Domain Controller for a New Domain and click Next. In the Create New Domain window, select Create Domain in a new forest and click Next. In the New Domain Name window, enter the domain name (for example, polycom.com) and click Next. In the NetBIOS Domain Name window, enter the NetBIOS name (default) and click Next. In the Permissions window, select Permission compatible only with Windows 2000 or Windows Server 2003 operating systems (default setting) and click Next. 2-2 Polycom-Microsoft Deployment Guide 10 In the DNS Registration Diagnostics window, select Install and Configure the DNS server option and click Next. This step can be skipped if a DNS Server is already installed in your environment. 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: 1 Log on to the domain controller (server A) as an administrator. 2 Start the Live Communications Server 2005 Setup from the domain controller server. The Live Communication Server wizard opens. 2-3 Microsoft--Polycom Environment Setting 3 Click Standard Edition Server. 2-4 Polycom-Microsoft Deployment Guide 4 Click Prep Schema. 5 6 7 8 9 Follow the wizard's on-screen instructions, and then click Finish. Click Prep Forest, and follow the wizard's instructions. Follow the wizard's on-screen instructions, and then click Finish. Click Prep Domain. Follow the wizard's on-screen instructions, and then click Finish. 2-5 Microsoft--Polycom Environment Setting Procedure 3--Live Communications Server Installation and Activation 1 If 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. Start the Live Communications Server 2005 Setup. The Live Communication Server wizard opens. Click Standard Edition Server. Click Install Files for Live Communications Server. Follow the wizard on-screen instructions with the following: In the Server Activation window, click Yes. In 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. Click Next. In the Enable IM Archiving page, verify that the check box is cleared, and then click Next. 2 3 4 5 6 7 8 9 10 In the Start Service Option page, verify that the Start the service after activation check box is selected. 2-6 Polycom-Microsoft Deployment Guide 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: 1 Expand the Active Users and Computers tree. 2 Right-click the Users folder, click New, and then click User. 2-7 Microsoft--Polycom Environment Setting 3 In 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. 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. 4 Click Next. 2-8 Polycom-Microsoft Deployment Guide 5 In the New Object - User window, enter the user password and confirm the password. The user password must contain at least 9 characters. This password is required only for the endpoint registration with the LCS. The password is also defined for a Meeting Room or Entry Queue in the LCS, but has no significance to the conferencing process. 6 7 8 Make sure that the Password never expires option is selected. Click Next. In the users list, right-click the new user, and then click Properties. The user Properties dialog box opens. 2-9 Microsoft--Polycom Environment Setting 9 Click the Live Communications tab. 10 Click the Enable Live Communications for this user check box. 11 In the SIP URI field, enter sip:username@. For example, john@polycom.com. 12 In the Server or pool box, select the Live Communications Server that was created in "Procedure 3--Live Communications Server Installation and Activation" on page 2-6. 13 Click OK. 2-10 Polycom-Microsoft Deployment Guide Procedure 5--Creating a SIP Network Service in the MGC Environment The MGC environment must include an MCU with an IP48 card V4.23 running version 7.0 or higher, and MGC Manager version 7.0 or higher. To define an IP Network Service: The same Network Service can be used for both SIP and H.323 connections. 1 2 3 In the MGC Manager application, expand the MCU tree and then expand the MCU Configuration tree. Expand the Network Services tree. Right-click the IP Network Services icon, and then click New IP Service. The IP Network Service wizard opens. 2-11 Microsoft--Polycom Environment Setting 4 In the Settings dialog box, define the following parameters: a b c Enter the Network Service name In the Protocol box, select Both. Click Next. 2-12 Polycom-Microsoft Deployment Guide 5 In the DNS Settings dialog box, define the following parameters: a b c d In the Use DNS Servers section, select Specify. In the Primary DNS Server field, enter the IP address of the LCS server. In the Local Domain Name box, enter the domain name as defined in the Active Directory (for example, polycom.com). Click Next. 2-13 Microsoft--Polycom Environment Setting 6 In the H323 dialog box, specify the gatekeeper parameters: This step can be skipped if your environment does not include a gatekeeper. a b c d In the Use Gatekeeper section, select Specify to manually define the IP address of the preferred gatekeeper. Enter the IP address of the gatekeeper. In the Service Mode box, select Board Hunting. In the Prefix box, enter the same prefix that has been defined for the Network Service in the gatekeeper. This number is used as part of the dial-in string given to H.323 participants connecting to conferences. Click Next. e 2-14 Polycom-Microsoft Deployment Guide 7 In the SIP dialog box, specify the SIP server parameters: 8 9 In the Registrations section, in the Registration Mode box, make sure that Redirect is selected. In the Register option, select the conferencing types and methods to register with the LCS server; select OnGoing Conferences, Meeting Rooms and Entry Queues. Meeting Rooms and Entry Queues should be registered with the LCS when they are added to the Buddy/Contacts list of Office Communicator or Windows Messenger. With SIP-CX components, Meeting Rooms are usually not registered to the LCS, and Static Routes are used instead. If even one Meeting Room is to register to the LCS, select this option. However, all other Meeting Rooms for which an account was not created in the LCS will fail to register with the LCS but will be available through the Static Route definition. 10 In the Servers section, click the SIP Servers button to define the IP address of the LCS Registrar. 2-15 Microsoft--Polycom Environment Setting 11 In the SIP Settings dialog box, define the following parameters: a b In the Transport section, in the SIP Transport Type option, select TCP. In the SIP Servers section, define the following options: In the Preferred SIP Server option, click Specify. In the IP address or Name box, enter the IP address of the LCS server. · In the Port field, enter the port number the MGC unit uses for outbound and incoming communication TO and FROM the LCS. The default port is 5060; however this port number can be changed. · In the Domain Name or IP box, enter the domain name of the LCS. Click OK. The system returns to the SIP dialog box. · · c 12 In the SIP dialog box, click Next. 13 In the Authentication dialog box, click Next. 14 In the Span dialog box, click the plus (+) button. 2-16 Polycom-Microsoft Deployment Guide The IP SPAN dialog box opens. 15 Define the following parameters: a In the Circuit ID box, enter a number between 0 to 65535. The circuit identification is a number is used to identify the card's span to the system. It is assigned to a specific IP address, therefore it must be unique for each MCU. In the IP Address box, enter the IP address of the IP network card installed in the MCU. In the Communication Mode list, select the data transmission rate and duplex mode, or select Auto to let the system synchronize the data transmission rate according to the network. In the Host Name box, enter the name of the computer on the domain network. This name is added to the local domain name to identify the card, for example: IP1. If the local domain name is polycom.com, the card name will be IP1.polycom.com. A default host name is suggested by the system. b c d 2-17 Microsoft--Polycom Environment Setting e In the H.323 section, in the Alias box, enter the alias by which the IP card is identified by the gatekeeper within the network. An alias must be entered when working with a gatekeeper. Up to five aliases can be defined for each IP card. In the H.323 section, in the Alias Type list, select either: f · H.323 ID (alphanumeric ID) · E.164 (digits 0-9, * and #) 16 If required, click the Fixed Ports & NAT button to configure the firewall ports and NAT traversal. The Fixed Ports and NAT Traversal dialog box opens. a Select the Enable Fixed Ports check box to enable the configuration of firewall ports used for control and media, and the definition of the number of concurrent calls in the IP network. 2-18 Polycom-Microsoft Deployment Guide b In the Number of Calls box, enter the predicted number of simultaneous incoming video calls that require fixed port allocation and are handled by the network and MCU, up to the maximum that can be handled by the IP card. In the Port Range definition fields, define the port ranges for each of the channels; enter the first port for each channel and the system automatically fills in the end of the assigned port range. You can allocate the same port number to different channels provided the numbers are in two different protocols; one is in TCP and the other is in UDP. Select how the system handles port allocation when fixed ports are exhausted: Allocate ports dynamically--to automatically allocate any of the available ports in the firewall to calls that exceed the number of predicted simultaneous calls. · Reject--to reject any request to open additional ports. If NAT Traversal is used, in the Use Span External Address field select the method in which the public IP address is mapped to the IP card's internal address: · · · Off--no external IP address will be used. Specify--to define the IP card's public IP address. Auto--the IP card's public IP address is automatically retrieved from the HTML Answer of the external server. The address is: http://videovideo.polycom.austin.com. Click OK to return to the IP Span dialog box. · c d e f 17 In the IP Span dialog box, click OK to return to the Span dialog box. 18 In the Span dialog box, click Finish to complete the definition of the IP Network Service. The new IP Network Service is added to the IP Network Services tree. To assign the IP Network Service to the IP Card: To complete the Network Service definition, you must define the properties of the IP network connected to that IP card. This is done by assigning the IP Network Service to the IP card: 19 Expand the MCU Configuration tree 20 Expand the Cards tree 2-19 Microsoft--Polycom Environment Setting 21 Right-click the IP card icon, and then click Properties. 22 In the Card Settings dialog box, click the IP-Network Parameters tab. 23 Clear the Null Configuration check box. 2-20 Polycom-Microsoft Deployment Guide 24 In the Circuit ID box, enter the Circuit ID defined for the IP Span in the IP Network Service. The name of the assigned Network Service is updated in the appropriate field. 25 Click OK. 26 Reset the MCU. The MGC unit (the IP card) is now registered with the LCS server. To verify the registration status of the IP card with the SIP Server: 1 Expand the Cards tree. 2 3 4 Right-click the IP Card icon, and then click Properties. In the Card Settings dialog box, click the SIP tab. In the Card Settings--SIP dialog box, the LCS Server should be marked as Active (in the Role column) and its Status as OK. 2-21 Microsoft--Polycom Environment Setting Procedure 6--Defining the MGC Unit as Trusted in the LCS To be able to work with the LCS, the MGC unit must be configured as a trusted host in the LCS. This is done by defining each of the MGC unit's IP cards as a trusted host. To configure the MGC unit as trusted in the LCS: 1 Open the LCS Management application. 2 3 4 Expand the forest and domain trees until the list of servers is displayed. Right-click the Server icon, and then click Properties. Click the Host Authorization tab. 5 In the LCS Properties--Host Authorization dialog box, click the Add button. 2-22 Polycom-Microsoft Deployment Guide 6 In the Edit Authorized Host dialog box, enter the IP address of the IP card installed in the MGC unit. If you have several cards you will have to add each one of them separately to the LCS list of authorized hosts. 7 8 In the Settings section, select the Throttle as Server and Treat As Authenticated check boxes. Click OK. The defined IP card appears in the trusted servers list in the server Properties--Host Authorization dialog box. If routing between the MGC unit and the LCS using Static Routes is required, do not close this dialog box, and continue with step 4 of the following procedure. If you do not want to define Static Routes, click OK to close this dialog box. 2-23 Microsoft--Polycom Environment Setting Procedure 7-- Setting the Static Routes Between the LCS and the MGC Unit Setting Static Routes in the LCS enables SIP entities / UAs to connect to conferences without explicit registration of conferences with the LCS. Routing is performed by the LCS based on the comparison between the received URI and the provisioned static route pattern. If a match is found, the request is forwarded to the next hop according to the defined hop's address. This method alleviates the need to create a user account in the LCS for each employee for whom a Meeting Room is created, especially in large organizations with thousands of employees. This also allows users to join conferences hosted on the MCU without registering all these conferences with LCS. With MGC software version 7.5, it is recommended to register only the Entry Queues used for conference access. When working with MGC software version 7.0x, this procedure is required when using Windows Messenger to start an ad-hoc multipoint video conference using an Entry Queue, or when accessing conferences via a single-dial Entry Queue. This method is also used in ad-hoc conference creation, where the destination conference is defined based on the numeric ID the user enters using DTMF codes. As DTMF codes are not supported by Windows Messenger, the numeric ID is added to the URI string that is interpreted by the LCS according to the Static Routes configuration. Static Routes are also used to increase the system capacity, enabling the use of multiple MGC units and IP cards. For additional information, see Chapter 2, "Configuring for Office Communicator Multipoint Conference Capacity/Scalability" on page 2-40. To configure LCS Static Routes: If the server Properties dialog box remained open at the end of the previous procedure, skip to step 4. 1 2 3 Open the LCS Management application. Expand the forest and domain trees until the list of servers is displayed. Right-click the Server icon, and then click Properties. 2-24 Polycom-Microsoft Deployment Guide The server Properties dialog box opens. 4 5 Click the Routing tab. Click the Add button. 2-25 Microsoft--Polycom Environment Setting 6 In the Add Static Route dialog box, define the following parameters: a In the User box, define the wildcard characters that will be used for the Meeting Rooms and Entry Queue names, using the format xy*. For example, if you define 76*, the LCS will forward all the calls that dialed 76 at the beginning of the URI string to the MGC unit. Once the call arrives to the MGC unit, the system looks for the appropriate conference or entry queue according to the numeric ID added to the URI string. In the Domain box, enter the name of the domain where the user can be found. The domain name can be replaced by the wildcard character (*). In the Next Hop section, in the IP address box, enter the IP address of the IP card to which the IP Network Service is assigned. In the Next Hop section, in the Port box, enter the port number on the MGC system side. Click OK. The new Static Route is added to the list of static routes defined in the Routing tab. b c d e 7 Click OK. 2-26 Polycom-Microsoft Deployment Guide Procedure 8--Defining Additional Conferencing Components in the MGC Environment There are several scenarios in which a conference can start and Windows Messenger, Office Communicator and Polycom video endpoints (VSX, PVX) users can connect to these conferences. The main conferencing scenarios detailed in this guide are: · · · · Meeting Rooms Dial-out Meeting Rooms/Scheduled conference Single-dial Entry Queues Ad-hoc Entry Queues Meeting Room is a conference without resource allocation or starting date and time that is defined once but can be activated many times. A Meeting Room remains in a passive state between activations until the first participant connects to it and activates the conference. A Meeting Room can contain predefine dial-out participants, which are called by the MCU when the Meeting Room is activated. Single-dial Entry Queues are used as a single dial lobby to route participants to their target conferences. The participant enters the target conference ID using DTMF codes using the Office Communicator keypad. Entry Queues can also be defined as ad-hoc, enabling the creation of new conferences immediately. In standard ad-hoc conferencing, the new conference is created once the participant enters the conference ID using DTMF codes and no other conference with this ID is already running. When connecting to the Entry Queue from Windows Messenger that does not support DTMF codes, the conference ID must be communicated differently. This is done by adding the conference ID to the target URI provided by the participant. This addition to the URI is not recognized by the LCS, and it is based on LCS provisioned static routes. Static Routes are also used for ad-hoc conferencing, where the provided URI is not registered with LCS since the conference does not exist yet, and it is the the only way for the request to be routed to the Entry Queue/MCUs. Single-dial Entry Queues or ad-hoc Entry Queues are the recommended conferencing scenarios with Office Communicator. In these scenarios only a limited number of accounts have to be defined in the LCS (for each defined Entry Queue), that can be used for all conference access. Office Communicator users will have to add only one or two "conferencing buddies" to their list. With Meeting Rooms, a separate LCS account must 2-27 Microsoft--Polycom Environment Setting be created for each Meeting Room, and all the Meeting Room buddies have to be added to the Office Communicator contact list, thus overloading it. Definition Procedure: · When working with MGC software version 7.0x, for each Meeting Room or Entry Queue to be used for conferencing, a user account must be defined in the LCS. This procedure is identical for Entry Queues and Meeting Rooms. When working with MGC software version 7.5 with SIP-CX, a user account must be defined in the LCS for Entry Queues to be used for routing. Meeting Rooms do not have to register with the LCS, and you can create accounts only for selected Meeting Rooms, while access to all other Meeting Rooms can be accomplished using the Static Route method. For a detailed description of the User Account definition in the LCS, see "Procedure 4--LCS User Account Definition and Client Access Configuration" on page 2-7. · In the MGC Manager application, a new Meeting Room or Entry Queue is defined using the same name (the system is case sensitive) assigned to the user account in the LCS. The Meeting Room details, such as name, ID, passwords and dial-in numbers (for PSTN or ISDN connections) or string (for H.323 connections) must be communicated to the Meeting Room owner. When working with MGC software version 7.0x, or 7.5 without SIP-CX, the New Meeting Room or Entry Queue is added to the Windows Messenger and Office Communicator buddy list. This procedure is described in Chapter 3, "Adding a Meeting Room or an Entry Queue to the Buddy List" on page 3-20. When working with MGC software version 7.0x, or 7.5 without SIP-CX, the participant selects the Meeting Room or Entry Queue from the buddy list. If a Meeting Room is selected, the conference is started and the user connects to this conference. If an Entry Queue is selected, the user connects to the Entry Queue and is transferred from the Entry Queue to the target conference by entering the conference numeric ID using DTMF codes (Office Communicator) or adding it to the Entry Queue URI. For details, see Chapter 3. · · . 2-28 Polycom-Microsoft Deployment Guide Defining a Meeting Room in the MGC Manager Application To define a Meeting Room in the MGC Manager application: 1 In the MGC Manager application, expand the MCU tree. 2 3 Right-click the Meeting Rooms & Entry Queues icon, and then click New Meeting Room. In the Meeting Room Properties dialog box, enter the name of the Meeting Room using the same name as defined in the LCS user account. 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. 2-29 Microsoft--Polycom Environment Setting 4 Define the remaining parameters of the conference. You can add predefined dial-out participants to this Meeting Room. When the Meeting Room is activated by the first dial-in participant, the MCU will call the defined dial-out participants. To add participants to the Meeting Room, click the Participants tab. For a detailed description of SIP participant definition, see Chapter 3. If legacy endpoints connect to the Meeting Room, a dial-in number will be automatically assigned to the Meeting Room once it is saved to the MCU. This number is taken from the range of dial-in numbers defined in the default ISDN Network service. You can manually assign a dial-in number. For details, see the MGC Manager User's Guide, Volume I, Chapter 8. 5 Click OK. Defining an Entry Queue in the MGC Manager Application This procedure describes the definition of a new Entry Queue (for single dial). For a detailed description of the definition procedure of an Ad-hoc Entry Queue, see Chapter 4. To define a new Entry Queue in the MGC Manager application: 1 In the MGC Manager application, expand the MCU tree. 2 Right-click the Meeting Rooms & Entry Queues icon, and then click New Entry Queue. 2-30 Polycom-Microsoft Deployment Guide 3 In the Entry Queue Properties dialog box, define the Entry Queue parameters: a In the Name field, enter the name defined in the LCS for the user account representing the Entry Queue. The MGC system is case sensitive. 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. b In the Entry Queue Service list, select the Message Service to be used with this Entry Queue. When connecting to the Entry Queue, the participant hears the audio messages and prompts included with this service. These messages guide the participant to the appropriate conference or enables the participant to start a new conference. In the Numeric ID box, enter a number that can be used for dialing from an H.323 endpoint to connect to the Entry Queue. If left blank, the system will automatically assign one. c 2-31 Microsoft--Polycom Environment Setting d In the Target Conferences box, select Transcoding to allow all endpoint types to connect to the conference. If your MCU does not include a video card, select Video Switching. Make sure that the Audio and Video parameters are set to Auto to let the system select them. In the Line Rate field, select the line rate at which the participant will connect to the target conference. This should be the rate defined in all the Meeting Rooms and Ongoing conferences. If the Entry Queue will also be used by ISDN or PSTN endpoints to connect to the Entry Queue, assign a dial-in number to the Entry Queue. If no number is assigned, when the Entry Queue is saved on the MCU, the MCU will automatically assign a dial-in number from the range of dial-in numbers defined in the default ISDN Network service. Otherwise, skip this step. Click OK. e f g h 2-32 Polycom-Microsoft Deployment Guide Endpoint Settings Polycom VSX systems and PVX software support SIP calling through Microsoft LCS 2005 (SP1) proxy server. The following features are supported with VSX/PVX and MS LCS 2005: · · · · · · · · Registration using MS NTML authentication method Manual or use Network login E-mail (URI) & IP address dialing from PVX VSX/PVX user can be added into Windows Messenger/Office Communicator's buddy list Presence information sent to LCS (unreachable, busy, ready) VSX/PVX endpoints--set up SIP settings LCS 2005--define an account for each endpoint Windows Messenger/Office Communicator--add the endpoint to the buddy list To enable these features with LCS 2005 you must: VSX Settings Enabling SIP for the Endpoint 1 Go to System ­> Admin Settings ­> Network ­> Call Preference. 2-33 Microsoft--Polycom Environment Setting 2 3 Select the Enable SIP check box. Save the new settings. Network Configuration To set up the VSX for SIP conferencing: 1 Upgrade the VSX systems to version 8.0. a b c 2 3 Version 8.0 has to be purchased through one of Polycom's channel partners. Once purchased, follow the version installation procedure as described in the version's release notes. Activate the software through Polycom Resource Center (PRC) using the system's serial number. To specify SIP settings, System > Admin Settings > Network > IP > SIP Settings. Define the following parameters: a b Transport Protocol--Select TCP. User Name--Specifies the system's SIP name as will be defined in the LCS. If you leave this field blank, the system's IP address is the SIP user name. 2-34 Polycom-Microsoft Deployment Guide c Password--Specifies the password that authenticates the system to the LCS. The user password must contain at least 9 characters. This password will be used when defining the user account for this endpoint in the LCS. Registrar Server--Enter the IP address of the LCS server. By default, the SIP signaling is sent to port 5060 on the registrar server. To specify a different port, add it to the address as shown here: 10.11.12.13:5070. Proxy Server--Enter the same address as the Registrar server as the LCS performs both tasks. d e 4 Save the network settings. PVX Settings To set up the PVX for SIP conferencing: 1 Upgrade the PVX application to version 8.0. a b c Version 8.0 has to be purchased through one of Polycom's channel partners. Once purchased, follow the version installation procedure as described in the version's release notes. Activate the software through Polycom Resource Center (PRC) using the license number. 2-35 Microsoft--Polycom Environment Setting 2 To specify SIP settings, click the Settings icon, and then click IP. 3 Define the following parameters: a b c d Select the Enable SIP check box. Transport Protocol--select TCP. Type of SIP Server--select Microsoft LCS. Select either the Use network login credentials check box. In this case, the user name and password are taken from the network, or define: · User Name--Specifies the system's SIP name as will be defined in the LCS. If you leave this field blank, the system's IP address is the SIP user name. · Password--Specifies the password that authenticates the system to the LCS. The user password must contain at least 9 characters. This password will be used when defining the user account for this endpoint in the LCS. Registrar Server--Enter the IP address of the LCS server. By default, the SIP signaling is sent to port 5060 on the registrar server. To specify a different port, add it to the address as shown here: 10.11.12.13:5070. e 2-36 Polycom-Microsoft Deployment Guide f 4 Proxy Server--Enter the same address as the Registrar server as the LCS performs both tasks. Save the network settings. Defining a User Account in the LCS To define an LCS User Account for an Endpoint: 1 In the LCS Management application, expand the server tree. 2 3 4 5 Right-click the Users icon, and then click Add New User. In the New Object--User dialog box, enter the name of the endpoint as the user name. Click Next. In the New Object - User window, enter the user password and confirm the password as defined for the endpoint in the SIP Settings dialog box. The user password must contain at least 9 characters. This password is required for the endpoint registration with the LCS and for authentication. 6 7 8 Make sure that the Password never expires option is selected. Click Next. In the users list, right-click the new user, and then click Properties. The user Properties dialog box opens. 2-37 Microsoft--Polycom Environment Setting 9 Click the Live Communications tab. 10 Click the Enable Live Communications for this user check box. 11 In the SIP URI field, enter sip:username@, as defined in the endpoint's SIP Settings dialog box. For instance john@polycom.com. 12 In the Server or pool box, select the Live Communications Server that was created in "Procedure 3--Live Communications Server Installation and Activation" on page 2-6. 13 Click OK. 2-38