Microsoft Polycom Integrated Solution Deployment Guide Phase 5

Microsoft–Polycom Integrated Solution Deployment Guide Phase 5 Copyright © 2007 Polycom, Inc. All Rights Reserved Catalog No. eDOC2222C Version 3.0...
Author: Augusta Moody
0 downloads 2 Views 7MB Size
Microsoft–Polycom Integrated Solution Deployment Guide Phase 5

Copyright © 2007 Polycom, Inc. All Rights Reserved

Catalog No. eDOC2222C Version 3.0

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-7

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 Assigning the IP Network Service to the IP Card ............. 2-20 Modifying the system.cfg Flags (optional) ......................... 2-21 Verifying the Registration Status of the IP card with the SIP Server ....................................................................................... 2-22 Procedure 6—Defining the MGC Unit as Trusted in the LCS 2-23 Procedure 7— Setting the Static Routes Between the LCS and the MGC Unit ....................................................................................... 2-25 Procedure 8—Defining Additional Conferencing Components in the MGC Environment ................................................................. 2-29 Defining a Meeting Room in the MGC Manager Application ............................................................................. 2-31 Defining an Entry Queue in the MGC Manager Application ............................................................................. 2-32 Setting an Entry Queue as Default ...................................... 2-34 Procedure 9 – V2IU Settings ........................................................ 2-35 V2IU and Access Proxy Requirements ............................... 2-35 V2IU Installation .................................................................... 2-36 V2IU Access Proxy Installation and Configuration .......... 2-37

i

Table of Contents

Endpoint Settings ................................................................................. 2-41 VSX Settings .................................................................................. 2-41 Enabling SIP for the Endpoint ............................................. 2-42 Network Configuration ........................................................ 2-42 Creating the Contact List on the VSX or V500 System ..... 2-44 Adding Contacts .................................................................... 2-44 PVX Settings .................................................................................. 2-45 SoundPoint® IP SIP 2.0 Settings ................................................ 2-47 Dual Registration with Microsoft® Office Live Communications Server 2005 as the Presence Server ...... 2-48 Adding Contacts to the SoundPoint® IP SIP 2.0 .............. 2-49 Defining a User Account in the LCS .......................................... 2-50 Adding the Endpoint to Office Communicator, Windows Messenger and SoundPoint IP 2.0 Buddy List ......................... 2-52 Cross Federation Implementation Tips ............................................. 2-53

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, Windows Messenger and SoundPoint IP SIP 2.0 Buddy Lists ................ 3-24

ii

Polycom-Microsoft Deployment Guide

Office Communicator ............................................................ 3-24 Windows Messenger ............................................................. 3-24 SoundPoint® IP SIP 2.0 ......................................................... 3-25 Creating the Contact List on the VSX or V500 System ............ 3-26 Displaying Contacts on the Home Screen .......................... 3-26 Viewing and Changing Presence Status ............................. 3-27 Multipoint Conferencing Scenarios ................................................... 3-29 Meet Me—Starting an Ongoing Video Conference from Windows Messenger and Office Communicator ....................................... 3-29 Joining the Ongoing Conference ......................................... 3-32 MGC Manager Monitoring ................................................... 3-33 Single Dial Entry Queue .............................................................. 3-34 Joining the Ongoing Conference ......................................... 3-36 MGC Manager Monitoring ................................................... 3-37 Ad Hoc Entry Queue and Conference Creation ....................... 3-38 Ad Hoc Conferencing with SIP-CX Support ..................... 3-38 Standard Ad Hoc Conferencing .......................................... 3-39 Dial-out to Conference Participants ........................................... 3-40 Joining the Conference .......................................................... 3-41 Escalating Windows Messenger or Office Communicator IM Multiparty Session to an Audio/Video Conference ................ 3-42 Windows Messenger ............................................................. 3-42 Office Communicator ............................................................ 3-45 Office Communicator New Multipoint Conferencing Scenarios Based on SIP-CX Protocol ............................................................................... 3-49 Starting a New Conference Directly from within Office Communicator .............................................................................. 3-49 An Office Communicator User Invites another Office Communicator Contact to the Conference ................................ 3-52 An Office Communicator User Joins an Existing Conference 3-54 An Office Communicator User Dials out to another Office Communicator User ..................................................................... 3-56 Adding Audio/Video to an Office Communicator Multiparty IM Session ............................................................................................ 3-58 Scheduling a Meeting—Office Communicator–Outlook Integration ...................................................................................... 3-61 Starting a Data Sharing Session .................................................. 3-63 Conference Control via Office Communicator SIP-CX Protocol ... 3-66

iii

Table of Contents

Ad-hoc Conferencing and Active Directory Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Ad Hoc Conferencing for OC Users with SIP-CX Support .............. 4-2 Requirements for Ad Hoc Conferencing with SIP-CX Support ............................................................................................. 4-3 Flag Settings for Ad Hoc Conferencing with SIP-CX Support 4-4 Standard Ad Hoc Conferencing ........................................................... 4-5 Standard Ad Hoc Conferencing Requirements ......................... 4-6 Standard Ad Hoc Conferencing and Validation Scenarios ...... 4-7 Ad Hoc Conferencing without Active Directory Validation ................................................................................. 4-7 Ad Hoc Entry Queue with Active Directory Validation ... 4-8 Ad Hoc Entry Queue with Conference Password Validation with Active Directory .............................................................. 4-9 Defining the Ad Hoc Conferencing Components in the MGC Environment ......................................................................................... 4-11 Profiles ........................................................................................... 4-11 Entry Queue Service Definition .................................................. 4-12 Entry Queue Service with Access to the External Database .................................................................................. 4-14 IVR Service with Access to the External Database Application ............................................................................. 4-15 Ad Hoc-enabled Entry Queue .................................................... 4-16 System Flags Configuration ........................................................ 4-18 Configuring the Access to an External Database Application for Validation (Standard Ad Hoc Conferencing) .............. 4-19

Limitations and Pending Issues

. . . . . . . . . . . . . . 5-1

Known Limitations ................................................................................ 5-1 Pending Issues ........................................................................................ 5-3

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 5. 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 audio and video endpoints (VSX, PVX and SoundPoint) 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 5 that is based on the MGC software version 8, 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. This solution 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:

1-2



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 Office 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

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 single domain environment and its elements.

Figure 1-1 Microsoft–Polycom Single Domain Environment

Microsoft—Polycom environment enables presence and buddy lists on Polycom VSX video systems and SoundStation and SoundPoint phones to

1-3

Overview

simplify rich media calling for end-users, making it as easy to connect a call from your phone or video system as it is using Communicator on your PC. 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. Customers using Microsoft Office LCS and Polycom endpoints cannot make calls through federated links over the public internet, as calls will not successfully complete due to: •

Address translation



Quality of Service



Bandwidth management

Microsoft—Polycom environment solution also supports cross federation (cross firewall/NAT) with audio and video for Point-to-point and multipoint scenarios, using the Polycom V2IU as an intermediary. LAN

DMZ

DMZ

LAN

Certificate Authority

LCS

LCS

Access Proxy

Access Proxy

Public Domain

Office Communicator V2IU-E

Office Communicator V2IU-E

VSX Endpoint

MGC Unit

Figure 1-2 Microsoft–Polycom Environment, Cross Domains

1-4

VSX Endpoint

Polycom-Microsoft Deployment Guide

With this solution, calls are routed through the V2IU, which translates public to private addresses, and provides QOS and bandwidth management functionality. Since the V2IU is also federated with Live Communications Server, network administrators also benefit from a single directory, set of IT policies, and common user privileges for managing voice, video, and data on a single call. 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 Office Live Communications Server (LCS)

Active Directory

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.



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 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.

1-5

Overview

Table 1-1

Elements of the Microsoft—Polycom Environment (Continued)

Element

Description

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 give 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 Elements

1-6

Polycom Video Endpoint

All Polycom video endpoints supporting SIP (PVX and VSX family of room systems) and legacy video endpoints supporting H.323 and H.320.

Polycom SoundPoint IP SIP 2.0 endpoint

A family of Voice over IP (VoIP) endpoints supporting SIP and legacy audio 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.

Polycom V2IU and V2IU Access Proxy Service

Provide network addressing and firewall traversal solution with Microsoft Office Live Communications Server and Microsoft Office Communicator. The V2IU Access Proxy Service is installed on an LCS Access Proxy and connect the Microsoft Office LCS to the V2IU.

Polycom-Microsoft Deployment Guide

Environment Requirements The following software versions are required to enable the Microsoft— Polycom integrated solution: •

Microsoft Office LCS 2005 SP1



Office Communicator version 1.0



Windows Messenger version 5.1



MGC unit software version 8.0



Polycom PVX version 8.0.1



Polycom VSX version 8.5



Polycom SoundPoint IP SIP version 2.0

For cross federation video sessions, the following entities are required: •

Polycom V2IU-E with LCS license



Polycom V2IU Access Proxy Service version 1.0



Microsoft Windows 2003 Server

1-7

Overview

1-8

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

Setting up a Server as a Windows Domain Controller.

2

Extending the Active Directory schema.

3

Live Communications Server installation and activation.

4

LCS Users definition and Client Access configuration.

5

Defining a SIP Network Service in the MGC environment (on the MGC unit using the MGC Manager application).

6

Configuring the MGC unit as trusted in the LCS.

7

Setting Static Routes in the LCS.

8

Defining additional conferencing components in the MGC environment; defining Meeting Rooms and Entry Queues.

9

Configuring the V2IU for cross federation conferencing

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-2

2

Click Start->Run

3

In the Run dialog box, enter dcpromo. The Active Directory Installation wizard opens.

4

In the Welcome screen, click Next.

5

In the Domain Controller Type window, select Domain Controller for a New Domain and click Next.

6

In the Create New Domain window, select Create Domain in a new forest and click Next.

7

In the New Domain Name window, enter the domain name (for example, polycom.com) and click Next.

8

In the NetBIOS Domain Name window, enter the NetBIOS name (default) and click Next.

9

In the Permissions window, select Permission compatible only with Windows 2000 or Windows Server 2003 operating systems (default setting) and click Next.

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

2-4

Click Standard Edition Server.

Polycom-Microsoft Deployment Guide

4

Click Prep Schema.

5

Follow the wizard’s on-screen instructions, and then click Finish.

6

Click Prep Forest, and follow the wizard’s instructions.

7

Follow the wizard’s on-screen instructions, and then click Finish.

8

Click Prep Domain.

9

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.

2

Start the Live Communications Server 2005 Setup. The Live Communication Server wizard opens.

3

Click Standard Edition Server.

4

Click Install Files for Live Communications Server.

5

Follow the wizard on-screen instructions with the following:

6

In the Server Activation window, click Yes.

7

In the Welcome to the Activate Live Communications Server wizard, click Next.

8 9

— 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.

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-29. 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

2-8

Click Next.

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

Make sure that the Password never expires option is selected.

7

Click Next.

8

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, [email protected]. 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 or any IP+ card running version 8.0 or higher and MGC Manager version 8.0 or higher. To define an IP Network Service: The same Network Service can be used for both SIP and H.323 connections. 1

In the MGC Manager application, expand the MCU tree and then expand the MCU Configuration tree.

2

Expand the Network Services tree.

3

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

2-12

In the Settings dialog box, define the following parameters:

a

Enter the Network Service name. This name will be later used to designate this IP Network Service as SIP-CX enabled in the system.cfg. When assigning this IP Network Service to specific IP+48 cards, only these cards are limited to 24 IP participants while all other IP+48 cards that are assigned to non SIP-CX IP Network Service can connect up to 48 H.323 and standard SIP participants.

b

In the Protocol box, select Both.

c

Click Next.

Polycom-Microsoft Deployment Guide

5

In the DNS Settings dialog box, define the following parameters:

a

In the Use DNS Servers section, select Specify.

b

In the Primary DNS Server field, enter the IP address of the LCS server.

c

In the Local Domain Name box, enter the domain name as defined in the Active Directory (for example, polycom.com).

d

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.

2-14

a

In the Use Gatekeeper section, select Specify to manually define the IP address of the preferred gatekeeper.

b

Enter the IP address of the gatekeeper.

c

In the Service Mode box, select Board Hunting.

d

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.

e

Click Next.

Polycom-Microsoft Deployment Guide

7

In the SIP dialog box, specify the SIP server parameters:

8

In the Registrations section, in the Registration Mode box, make sure that Redirect is selected.

9

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

In the Transport section, in the SIP Transport Type option, select TCP.

b

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.

In cross-federation environment, when V2IU is installed, you must specify the domain name in the Domain name field.

c

Click OK. The system returns to the SIP dialog box.

12 In the SIP dialog box, click Next.

2-16

Polycom-Microsoft Deployment Guide

13 In the Authentication dialog box, click Next. 14 In the Span dialog box, click the plus (+) button. 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.

b

In the IP Address box, enter the IP address of the IP network card installed in the MCU.

c

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.

d

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.

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.

f

In the H.323 section, in the Alias Type list, select either:

• 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

2-18

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.

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.

c

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.

d

Select how the system handles port allocation when fixed ports are exhausted: •

e

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: • • •

f

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.

17 In the IP Span dialog box, click OK to return to the Span dialog box. 18 If your system includes several IP+ cards to be used with this IP Network Service, repeat steps 14 to 17 to add them to the spans list. Ongoing conferences with Microsoft Office Communicator participants can span over several IP+ cards installed in the MCU. Once the an IP+ card is full, the MCU forwards the call to the next IP card without involving the endpoint or the LCS server in the process. 19 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.

2-19

Microsoft—Polycom Environment Setting

Assigning the IP Network Service to the IP Card To complete the Network Service definition, you must assign the IP Network Service to the IP card:

2-20

1

Expand the MCU Configuration tree.

2

Expand the Cards tree.

3

Right-click the IP card icon, and then click Properties.

4

In the Card Settings dialog box, click the IP-Network Parameters tab.

Polycom-Microsoft Deployment Guide

5

Clear the Null Configuration check box.

6

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.

7

Click OK.

8

If several IP cards (Spans) are defined in the IP Network Service to be used with Microsoft SIP-CX enabled endpoints, repeat steps 22 to 26 for each of these IP cards to assign the IP Network Service to them.

9

If this IP Network Service is not SIP-CX enabled, you can skip the next steps (Modifying the system.cfg Flags (optional) and reset the MCU. Otherwise, first modify the system.cfg flags and only then reset the MCU.

Modifying the system.cfg Flags (optional) When assigning the SIP-CX enabled IP Network Service to specific IP+48 cards, only these cards are limited to 24 IP participants while all other IP+48 cards that are assigned to non SIP-CX IP Network Service can connect up to 48 H.323 and standard SIP participants.

To Modify the system.cfg flags: For a detailed description on how to modify the MGC system.cfg file, see the MGC Administrator’s Guide, Chapter 5. 1

Right-click the MCU icon, click MCU Utils and then click Edit “system.cfg”.

2

To enable the SIP-CX environment for the MCU, in the SIP Section, set the flag SIP_CONF_WATCH_CONTROL to YES.

3

To designate a SIP-CX enabled IP Network Service, in the SIP Section, set the prefix of the IP network service name in the flag MSFT_IP_SERVICE_NAME_PREFIX. For example, if you enter MSFT as the prefix, the IP Network service whose name starts with MSFT (MSFT1, MSFT2, etc.) will be considered by the system as SIP-CX enabled.

4

Reset the MCU.

The MGC unit (the IP card) is now registered with the LCS server.

2-21

Microsoft—Polycom Environment Setting

Verifying the Registration Status of the IP card with the SIP Server

2-22

1

Expand the Cards tree.

2

Right-click the IP Card icon, and then click Properties.

3

In the Card Settings dialog box, click the SIP tab.

4

In the Card Settings—SIP dialog box, the LCS Server should be marked as Active (in the Role column) and its Status as OK.

Polycom-Microsoft Deployment Guide

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

Expand the forest and domain trees until the list of servers is displayed.

3

Right-click the Server icon, and then click Properties.

4

Click the Host Authorization tab.

5

In the LCS Properties—Host Authorization dialog box, click the Add button.

2-23

Microsoft—Polycom Environment Setting

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

In the Settings section, select the Throttle as Server and Treat As Authenticated check boxes.

8

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-24

Polycom-Microsoft Deployment Guide

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 8.0, 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, “Procedure 5—Creating a SIP Network Service in the MGC Environment” on page 2-11. To configure LCS Static Routes: To support multiple MGC IP cards in a LCS deployment, define an LCS Static Route for each MGC IP card using the card's IP address.

If the server Properties dialog box remained open at the end of the previous procedure, skip to step 4. 1

Open the LCS Management application.

2

Expand the forest and domain trees until the list of servers is displayed.

2-25

Microsoft—Polycom Environment Setting

3

Right-click the Server icon, and then click Properties. The server Properties dialog box opens.

2-26

4

Click the Routing tab.

5

Click the Add button.

Polycom-Microsoft Deployment Guide

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.

2-27

Microsoft—Polycom Environment Setting

To support multiple IP cards installed the MGC system, in the User box, enter the IP address of the IP card starting with the wild card *_. For example, *_172.22.190.26, as shown in the example below.

7

2-28

b

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 (*).

c

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.

d

In the Next Hop section, in the Port box, enter the port number on the MGC system side.

e

Click OK. The new Static Route is added to the list of static routes defined in the Routing tab.

Click OK.

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-29

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. In MGC version 8.0, you can designate an Entry Queue to Office Communicator users. In such a case, when a new conference is created its ID, conference password and chairperson password are taken from the request (Subscribe) sent by the Office Communicator user, without input from the user. For more details about Ad Hoc Entry Queues and their definition, see Chapter 4. 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 or 8.0 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.

2-30



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.



You can set an Entry Queue as default, hence, if there is a problem with the conference numeric ID or if the dialing string is consists only the IP Network Service Prefix or the IP card IP address, the participants are automatically routed to this Entry Queue. Once in the default Entry Queue they can enter the conference ID and still reach the target conference.



When working with MGC software version 7.0x and higher 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 Chapter 3, “Adding a Meeting Room or an Entry Queue to the Buddy List” on page 3-20.

Polycom-Microsoft Deployment Guide



When working with MGC software version 7.0x and higher 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.

Defining a Meeting Room 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 Meeting Room.

3

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.

2-31

Microsoft—Polycom Environment Setting

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

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

2-32

Right-click the Meeting Rooms & Entry Queues icon, and then click New Entry Queue.

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.

c

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.

2-33

Microsoft—Polycom Environment Setting

d

If you are creating an Ad Hoc Entry Queue, select the Ad Hoc check box. For more details about the definition of Ad Hoc Entry Queues, see Chapter 4.

e

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.

f

Make sure that the Audio and Video parameters are set to Auto to let the system select them.

g

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.

h

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.

i

Click OK.

Setting an Entry Queue as Default 1

In the MGC Manager application, expand the MCU tree.

2

In the Meeting Rooms, Entry Queues & SIP Factories list, right-click the Entry Queue icon and select Set as Default.

The default Entry Queue is identified by a bold name.

2-34

Polycom-Microsoft Deployment Guide

Procedure 9 – V2IU Settings V2IU and Access Proxy Requirements The requirements for V2IU and V2IU Access Proxy deployment are: •

The V2IU-E requires a separate public non NATed Internet address



The Access Proxy and V2IU-E must be able to communicate over TCP Port 30000 on the LAN side



Video and Audio endpoints must be able to send UDP/RTP traffic to the V2IU-E.



Ensure that the Microsoft Office LCS and Access Proxy installation has successfully completed by testing with Office Communicator Instant Messaging.

For federated environment installation tips, see "Cross Federation Implementation Tips” on page 2-53.

2-35

Microsoft—Polycom Environment Setting

V2IU Installation To configure and install the V2IU, see the V2IU installation guide.

2-36

1

Verify that the LCS support is enabled; select System >> View License Key.

2

Configure the WAN side of the V2IU with a public IP address.

3

Ensure that TCP port 30000 is open between the LCS Adapter Application and the V2IU on the LAN side of the network.

Polycom-Microsoft Deployment Guide

4

Configure the network to allow UDP/RTP traffic between endpoints and the LAN side of the V2IU.

5

Configure the V2IU bandwidth parameters. In addition to existing Bandwidth Settings described in the V2IU documentation, enter default bandwidths for audio and video streams. The V2IU will use these values if it cannot determine the actual bandwidth of an audio or video stream. Figure 2-1 shows an example of bandwidth configuration.

Figure 2-1 V2IU bandwidth configuration sample

V2IU Access Proxy Installation and Configuration The V2IUProxy Service contains the following three components: •

V2IUProxyService.exe



V2IUProxyService.exe.config



RegisterService.bat

2-37

Microsoft—Polycom Environment Setting

EWProxy Service Installation The V2IUProxy Adapter application is contained in the file V2IUProxyServiceSetup.msi. If you are installing from a CD, this application should automatically launch. If it does not launch, or if you are installing from a network server or hard drive, manually execute the program V2IUProxyServiceSetup.msi.

2-38

1

Enter the following information:

2

The installer will create an account to install and manage the LCS Filter. In the Password field, enter a valid Windows password. The user account name is V2IUProxyService and will be added to the RTC Server Applications group.

3

In the IP Address field, enter the LAN address of the V2IU.

Polycom-Microsoft Deployment Guide

4

At the end of the installation procedure, select the Run V2IUProxy Service after Installation check box to automatically start the service when the installer terminates.

5

Verify the service has been successfully installed: a

If you did not select to start the service after installation, start the windows service EWProxyService using the Windows Services Console.

b

Check the Windows Event Viewer for any error events logged by EWProxyService. You should see the following two entries: • •

EWProxyService: Service Started. Live Communication Server Application Module: Live Communication Server application has successfully registered

2-39

Microsoft—Polycom Environment Setting

c

Verify that the LCS Adapter Application Service is registered.

d

Verify that the V2IU Proxy Application has been registered with LCS.

V2IUProxy Service configuration is complete.

2-40

Polycom-Microsoft Deployment Guide

Endpoint Settings Polycom VSX systems and PVX software support SIP calling through Microsoft Office 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)

To enable these features with LCS 2005 you must: •

VSX/PVX endpoints—set up SIP settings



SoundPoint® IP SIP 2.0 - verify that the presence and messaging features are enabled



LCS 2005—define an account for each endpoint



Windows Messenger/Office Communicator/SoundPoint® IP SIP 2.0—add the endpoint to the buddy list

VSX Settings Integration of Polycom VSX and V500 system with Microsoft Office Live Communications Server provides organizations with voice, video, and an extensible platform that connects people, information, and business processes—enabling better decisions faster. With VSX and V500 version 8.5, you can set up a list of contacts, then see their availability and call them by selecting from the list. The contact list feature uses the SIP communication protocol and active registration to a Microsoft Office LCS server. To use the contact list feature, a user account for the VSX or V500 system must be created in the LCS server and then the VSX or V500 system must subscribe to Microsoft Office LCS. For a detailed description of the creation of a user account on the LCS, see "Procedure 4—LCS User Account Definition and Client Access Configuration” on page 2-7.

2-41

Microsoft—Polycom Environment Setting

Enabling SIP for the Endpoint 1

Go to System –> Admin Settings –> Network –> Call Preference.

2

Select the Enable SIP check box.

3

Save the new settings.

Network Configuration To set up the VSX for SIP conferencing: 1 Upgrade the VSX systems to version 8.5.

2

2-42

a

Version 8.5 has to be purchased through one of Polycom’s channel partners.

b

Once purchased, follow the version installation procedure as described in the version’s release notes.

c

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.

Polycom-Microsoft Deployment Guide

3

4

Define the following parameters:

Setting

Description

Transport Protocol

Select TCP.

User Name

The user name created for your VSX or V500 system with the LCS server. If you leave this field blank, the system’s IP address is the SIP user name.

Password

The password for this user name. 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

The location (IP or DNS) of the LCS server.

Proxy Server

The location (IP or DNS) of the LCS server.

Save the network settings.

The VSX or V500 system attempts to register with the LCS server using these settings. If you see a message that registration was not successful, check the configuration information on the LCS server and the system SIP Settings.

2-43

Microsoft—Polycom Environment Setting

To view the status of the current LCS registration, do one of the following: 1 Go to System > Admin Settings > Global Services > Directory Servers > Microsoft. 2

Select the global directory server icon at the top of the Directory screen.

Creating the Contact List on the VSX or V500 System With VSX and V500 version 8.5, you can set up a list of contacts, then see their availability and call them by selecting from the list. To enable the Contact List feature on the VSX or V500 system, the LCS administrator must configure the VSX or V500 system account information on the LCS server and supply you with the appropriate information to configure the system.

Adding Contacts You cannot add contacts directly from the VSX or V500 system. To add contacts to the list on your system, use the Microsoft Office Communicator client. Log in to the client using the VSX or V500 system account information (multiple clients can be logged in as the same account). Add contacts for the account, and the contacts will show up on the system.

2-44

Polycom-Microsoft Deployment Guide

To display contacts on the home screen: 1 Go to System > Admin Settings > General > Home Screen Settings. 2

Select Contact List.

To configure display options for contact list information: 1 Go to System > Admin Settings > Global Services > Directory Servers > Microsoft. You can also select the global directory server icon at the top of the Directory screen. 2

Configure these settings: Table 2-1

Directory Server - Microsoft Settings

Setting

Description

Display Contacts

Specifies whether to display your contacts on the contact list home screen and in the directory.

Show My Offline Contacts

Specifies whether to include offline contacts on the contact list home screen or in the directory.

PVX Settings To set up the PVX for SIP conferencing: 1 Upgrade the PVX application to version 8.0. a

Version 8.0 has to be purchased through one of Polycom’s channel partners.

b

Once purchased, follow the version installation procedure as described in the version’s release notes.

c

Activate the software through Polycom Resource Center (PRC) using the license number.

2-45

Microsoft—Polycom Environment Setting

2

To specify SIP settings, click the Settings icon, and then click IP.

3

Define the following parameters: a

Select the Enable SIP check box.

b

Transport Protocol—select TCP.

c

Type of SIP Server—select Microsoft Office LCS.

d

Select either the Use network login credentials check box. In this case, the user name and password are taken from the network, or define: •

e

f 4

2-46

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. Proxy Server—Enter the same address as the Registrar server as the LCS performs both tasks.

Save the network settings.

Polycom-Microsoft Deployment Guide

SoundPoint® IP SIP 2.0 Settings SoundPoint IP® phones can be deployed in two basic methods. In the first method, Microsoft Office Live Communication Server 2005 serves as the call server and the phones have a single registration. In the second method, the phones have a single registration to a call server that is not LCS and a secondary registration to LCS for presence purposes only. To modify SoundPoint® IP SIP 2.0 for use with LCS: 1 Open the SIP Configuration file (sip.cfg) in an XML editor.

• •

2

a

Locate the feature parameter.

b

For the feature.1.name = presence attribute, set feature.1.enabled to 1.

c

For the feature.2.name = messaging attribute, set feature.2.enabled to 1.

d

Locate the voIpProt parameter.

e

Set the voIpProt.server.x.transport attribute to TCPpreferred or TLS, depending on the LCS configuration.

x is the server number. Multiple servers would be used for fault tolerance. The TLS protocol is not supported on SoundPoint IP 300 and 500 phones.

f

Set the voIpProt.server.x.address to the LCS address, for example, voIpProt.server.1.address - "lcs2005.local".

g

Set the voIpProt.SIP.lcs attribute to 1.

h

(Optional) If SIP forking is desired, set voIpProt.SIP.ms-forking attribute to 1.

i

Save the modified SIP Configuration file.

Open the Per-Phone Configuration file (phone1.cfg) in an XML editor. a

Locate the registration parameter.

b

(Optional) Set the reg.1.address to the LCS address.

x is the registration number. The value is dependent on the phone model (see table below).

2-47

Microsoft—Polycom Environment Setting

Table 2-2

Registration Number per Phone Model

Model Number

Number of Registrations

300, 301

1, 2

500, 501

1, 2, 3

600

1, 2, …, 6

601 with Expansion Module

1, 2, …, 12

4000

1

c

Set the reg.1.server.y.address to the LCS server name.

y is the server number. Multiple servers would be used for fault tolerance.

3

d

(Optional) Set the reg.1.server.y.transport attribute to the same value selected in step 1e (TCPpreferred or TLS), depending on the LCS configuration.

e

Set reg.1.auth.userId to the phone's LCS username, for example, reg.1.auth.userID = "jbloggs".

f

Set reg.1.auth.password to the LCS password, for example, reg.1.auth.password = "Password1".

g

Locate the roaming_buddies attribute.

h

Set the roaming_buddies.reg element to 1.

i

Locate the roaming_privacy attribute.

j

Set the roaming_privacy.reg element to 1.

k

Save the modified Per-Phone Configuration file.

Schedule a reboot of all phones.

Dual Registration with Microsoft® Office Live Communications Server 2005 as the Presence Server (Optional) To modify the sip.cfg configuration file: 1 Open sip.cfg in an XML editor. 2

2-48

Locate the feature parameter.

Polycom-Microsoft Deployment Guide

3

For the feature.1.name = presence attribute, set feature.1.enabled to 1.

4

For the feature.2.name = messaging attribute, set feature.2.enabled to 1.

5

Locate the voIpProt parameter.

6

If SIP forking is desired, set voIpProt.SIP.ms-forking attribute to 1.

7

Save the modified SIP Configuration file.

To modify the phone1.cfg configuration file: 1 Open phone1.cfg in an XML editor. 2

Locate the registration parameter.

3

Select a registration to be used for the Microsoft® Office Live Communications Server 2005. Typically, this would be 2.

4

Set the reg.x.address to the LCS address. For example, reg.2.address = "7778"

5

Set the reg.x.server.y.address to the LCS server name.

6

(Optional) Set the reg.2.server.y.transport attribute to TCPpreferred or TLS. (Your selection depends on the LCS configuration.)

7

Set reg.x.auth.userId to the phone's LCS username. For example, reg.2.auth.userId = "jbloggs"

8

Set reg.x.auth.password to the LCS password. For example, reg.2.auth.password = "Password2"

9

Locate the roaming_buddies attribute.

10 Set the roaming_buddies.reg element to the number coresponding to the LCS registration. For example, roaming_buddies.reg = 2. 11 Locate the roaming_privacy attribute. 12 Set the roaming_privacy.reg element to the number coresponding to the LCS registration.For example, roaming_privacy.reg = 2. 13 Save the modified Per-Phone Configuration file. For more information on the SIP Configuration File, see the SoundPoint® IP SIP 2.0 Administrator Guide. Adding Contacts to the SoundPoint® IP SIP 2.0 1

Press the Buddies soft key on the idle display to get to the Buddy Status screen or press Menu > Features > Presence > Buddy Status.

2

Press More.

2-49

Microsoft—Polycom Environment Setting

3

Press Add.

4

Enter the number of the buddy, for example, 7778.

5

Press Submit. If the buddy is added successfully, you are able to scroll to it on the Buddy Status screen. Any contacts added through the SoundPoint® IP 2.0 buddy list will appear in as a contact in Office Communicator and Windows Messenger.

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-50

2

Right-click the Users icon, and then click Add New User.

3

In the New Object—User dialog box, enter the name of the endpoint as the user name.

4

Click Next.

5

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

Make sure that the Password never expires option is selected.

Polycom-Microsoft Deployment Guide

7

Click Next.

8

In the users list, right-click the new user, and then click Properties. The user Properties dialog box opens.

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 [email protected]. 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-51

Microsoft—Polycom Environment Setting

Adding the Endpoint to Office Communicator, Windows Messenger and SoundPoint IP 2.0 Buddy List Once the endpoint is registered with LCS, you can add it to the buddy list of Windows Messenger and Office Communicator. For a detailed description, see Chapter 3, “Adding Endpoints to Office Communicator, Windows Messenger and SoundPoint IP SIP 2.0 Buddy Lists” on page 3-24.

2-52

Polycom-Microsoft Deployment Guide

Cross Federation Implementation Tips When implementing the Microsoft-Polycom solution cross federation, the following tips may facilitate the process. Prerequisites: The provided tips assume: •

Two complete networks and domains with DNS set up on each



Public CA



Entries in Internet DNS for each access proxy



LCS Phase 3 Integration complete for one network



LCS installation complete in other network

Phase 4 Problem areas and Troubleshooting Tips: 1 Certificates- On every server involved in Federation, you must download and install the Certificate Chain and request a personal certificate. The Certificate Chain allows the server to trust any certificate issued by the CA. The personal certificates must be made out to each server's FQDN and will be used in setting up Mutual TLS. When requesting the certificates, follow the instructions based on which type of CA you are using. 2

Routing and Remote Access is not needed on the access proxies and will block traffic on ports 5060 and 5061. In fact, since the V2IU's support NAT by default, they make excellent Default Gateway's for the respective networks.

3

Create a forwarder from each network's DNS server to the internet DNS server so you don't have to mess with host files. Furthermore, when set up correctly, all servers on a network should be able to ping the access proxy of the other network.

4

If you install the V2IU proxy service before correctly configuring the LCS proxy server, the V2IU proxy service will eat up most of your CPU time and cause the system to slow down.

5

Enable full (level 4) logging on both the LCS access proxy and the LCS server if you are having problems getting sip messages to send between clients.

6

Testing each network's access proxy can be done using remote user OC clients before attempting to enable Federation. To do so, get a client machine on the internet to trust the CA you are using, then

2-53

Microsoft—Polycom Environment Setting

attempt to connect to the access proxy of the network you are testing. The client must use TLS.

2-54

7

As of VSX version 8.5, you can only enable SIP or H.323 at the same time. H.323 must be disabled before SIP will take effect. If required, reboot it after disabling H.323.

8

Ensure both the LCS server and LCS access proxy is at Service Pack 1 or you will run into problems.

3 Microsoft—Polycom Meeting Scenarios In the Microsoft—Polycom environment, two arrays of meeting scenarios are available; Those intended for Windows Messenger and Office Communicator that do not leverage and are not based on SIP-CX conferencing and those intended for Office Communicator and are based on SIP-CX conferencing. Windows Messenger and Office Communicator scenarios that do not leverage and are not base on SIP-CX conferencing The Meeting Rooms and/or Entry Queues defined in Polycom MGC Manager application and LCS 2005 are used in the Windows Messenger and Office Communicator to initiate multipoint video conferences. This chapter details the various multipoint conferencing scenarios and how to start an ongoing video conference from your Windows Messenger or Office Communicator. The following meeting scenarios are explained: •

Multipoint Meet-Me



“Single dial” Entry Queue (Office Communicator users only)



Multipoint Ad-hoc conferencing



Reservation-based dial-out



Extending an ongoing Windows Messenger or Office Communicator multipoint session into a multipoint audio and video conference.

3-1

Microsoft—Polycom Meeting Scenarios

Office Communicator scenarios that are based on SIP-CX conferencing: With SIP-CX component you can start or join a meeting and you can control and monitor the ongoing meeting that are based on SIP-CX conferencing features directly from within Office Communicator. Additional conferencing scenarios are available with Office Communicator SIP-CX component: •

Starting a New Conference directly from within Office Communicator



An Office Communicator user invites another Office Communicator user to the Conference



An Office Communicator user dials out to another office communicator user media device



Adding Audio/Video to an Office Communicator multiparty IM session from the Conversation window using the Conferencing button



Scheduling a Meeting—Office Communicator–Outlook integration

Point-to-Point Meeting Polycom PVX and VSX high quality video endpoints are LCS 2005 compatible; they can register with the LCS 2005 and can be added to Windows Messenger and Office Communicator buddy lists, displaying their presence status. This enables you to start a point-to-point video conference from your buddy list (in this scenario, the MGC unit is not required).

3-2

Polycom-Microsoft Deployment Guide

Multipoint Conferencing—Preparations This section describes the configuration procedures required to enable multipoint conferencing with Office Communicator and Windows Messenger clients. Several procedures are required by Office Communicator users only, to enable direct conferencing, monitoring and control capabilities and conference scheduling from within Office Communicator. •

Enabling direct conferencing from within Office Communicator



Enabling video calls with Office Communicator



Enabling data sharing with Office Communicator



Optional. Limiting the bandwidth allocated to the audio/video connection to a conference via Office Communicator



Modifying Windows Hosts list to include the LCS



Signing-in Office Communicator and Windows Messenger clients with the Live Communications Server



Defining the conference properties in the participant’s Office Communicator client

To enable conference access via Entry Queue and to add SIP endpoints to the Contacts list, the following procedures must be performed from the Windows Messenger or Office Communicator client: •

Adding a Meeting Room or Entry Queue to the Buddy/Contacts list



Adding SIP only endpoints to Office Communicator and Windows Messenger Buddy/Contacts list

3-3

Microsoft—Polycom Meeting Scenarios

Enabling Office Communicator Conferencing Features This procedure is required only when using Office Communicator conferencing features to start, join or control a multipoint audio and video conference directly from within Office Communicator. This section describes enabling the following features: •

Enabling direct conferencing from within Office Communicator



Enabling video calls with Office Communicator



Enabling data sharing with Office Communicator



Optional. Limiting the bandwidth allocated to the audio/video connection to a conference via Office Communicator

Using Group Policy (built in toll in Active directory) you can enforce OC configuration to all users or only for some of them: • http://support.microsoft.com/kb/913192/en-us - see under the "MORE INFORMATION" paragraph.



http://www.microsoft.com/downloads/details.aspx?familyid=9253DBEACC4F-4934-B35D-E2C90B6406DB&displaylang=en.



Microsoft Office Communicator 2005 Trial Edition includes the Communicator.adm file. The Communicator.adm file must be manually copied to the %windir%\inf folder.

Enabling Direct Conferencing from within Office Communicator in Windows This procedure consists of two stages: •

Copying the appropriate Communicator file to the required Windows directory



Enabling the conferencing feature in Windows.

To enable conferencing from within Office Communicator: 1 Close and exit your Office Communicator client.

3-4

2

Copy the file communicator.adm received with Office Communicator installation from the application folder to: C:\WINDOWS\inf directory (note that "inf" is a hidden directory).

3

Click Start—> Run

4

In the Run dialog box, enter gpedit.msc (Group Policy edit). The Group Policy window opens.

Polycom-Microsoft Deployment Guide

5

In the Local Computer Policy tree, expand the Computer Configuration tree.

6

Right-click the Administrative Templates, and then select Add/ Remove Templates.

7

In the Add/Remove Templates dialog box, click the Add button.

3-5

Microsoft—Polycom Meeting Scenarios

8

In the Policy Templates dialog box, select communicator.adm and click Open.

The selected file is added to the Add/Remove Templates dialog box. 9

In the Add/Remove Templates dialog box, click Close.

10 In the Group Policy window, in the Local Computer Policy tree, expand the Administrative Templates—>Microsoft Office Communicator Policy Setting and click the Microsoft Office Communicator Feature Policies folder. The list of features is displayed in the right pane.

3-6

Polycom-Microsoft Deployment Guide

11 In the Feature Policies - Settings list, double-click Enable Conferencing.

The Enable Conferencing Properties dialog box opens. 12 Click Enabled, and OK.

3-7

Microsoft—Polycom Meeting Scenarios

The system returns to the Group Policy window. At this point you can either close the Group Policy window, or you can modify the bandwidth allocated to video conferencing (optional and not required if using Office Communicator default allocation).

Enabling video calls with Office Communicator 13 In the Group Policy window, in the features list displayed on the right pane, double-click the Prevent video calls option. 14 In the Prevent video calls Properties dialog box, click the Disabled button.

15 Click OK. The system returns to the Group Policy window. Enabling data sharing with Office Communicator 16 In the Group Policy window, in the features list displayed in the right pane, double-click the Prevent collaboration features option.

3-8

Polycom-Microsoft Deployment Guide

17 In the Prevent collaboration features properties dialog box, click the Disabled button.

18 Click OK. The system returns to the Group Policy window. 19 If you do not need to modify the bandwidth allocation, close the Group Policy window. 20 Click No when prompted if you wish to save the changes.

3-9

Microsoft—Polycom Meeting Scenarios

Bandwidth Allocation Modification This procedure is optional and is required only if you need to change the default bandwidth allocated by Office Communicator (default allocation is 1 MB per second) for audio and video calls. To modify the Bandwidth allocated to Office Communicator audio and video calls: 1 In the Group Policy window, double-click the Limit bandwidth for audio and video calls entry.

3-10

Polycom-Microsoft Deployment Guide

2

In the Limit bandwidth for audio and video calls Properties dialog box, click Enabled.

3

In the Maximum bandwidth box, enter the maximum bandwidth that can be allocated to a video call.

For example, to limit the bandwidth to 384 Kbps, enter 384000. 4

Click OK.

5

Close the Group Policy window without saving (click NO when prompted).

3-11

Microsoft—Polycom Meeting Scenarios

Modifying Windows Hosts List to Include the LCS This procedure is required to enable data transfer between your computer and the LCS. To define the LCS as a local host: 1 Using Windows Explorer, browse to the following folder: C:\WINDOWS\system32\drivers\etc or in the Address box, enter %windir%\system32\drivers\etc 2

Double-click the Hosts file and select the Notepad application to display its contents.

3

Under Local Hosts add the following lines: — IP address of the LCS server and pool domain name — IP address and domain name of the LCS server

3-12

Polycom-Microsoft Deployment Guide

For example: 172.22.187.159 pool01.ip.co.il 172.22.187.159 ip.co.il

4

Save the file.

3-13

Microsoft—Polycom Meeting Scenarios

Signing-in Windows Messenger and Office Communicator Clients to the Live Communications Server To sign in Windows Messenger and Office Communicator users to the LCS, the IP address of the LCS server must be configured in the Windows Messenger and the Office Communicator. Office Communicator Configuration 1

Open Office Communicator.

2

On the Actions menu, click Options.

The Options dialog box opens.

3-14

Polycom-Microsoft Deployment Guide

3

Click the Accounts tab.

4

Click the Advanced button.

5

Enter the sign-in name as defined in the LCS.

6

In the Advanced Connection Settings dialog box, click Configure settings.

3-15

Microsoft—Polycom Meeting Scenarios

7

In Server name or IP address field, enter the IP address of the LCS server.

8

In the Connect using box, select TCP as the protocol to use for the connection.

9

Click OK.

10 Click OK to exit the Options dialog box. Windows Messenger Configuration To configure the connection parameters: 1 Open Windows Messenger.

3-16

2

On the Tools menu, click Options.

3

Click the Accounts tab.

4

In the Options—Accounts dialog box, in the SIP Communications Service Account section, make sure that the My contacts include users of a SIP Communication Service check box is selected.

5

Click the Advanced button.

Polycom-Microsoft Deployment Guide

6

In the SIP Communications Service Connection Configuration dialog box, click Configure settings.

7

In Server name or IP address box, enter the IP address of the LCS server (Server B in the configuration).

8

In the Connect using section, select TCP as the protocol to use for the connection.

9

Click OK to complete the configuration.

Windows Messenger can now be used to communicate between clients.

3-17

Microsoft—Polycom Meeting Scenarios

Defining the Conferencing Properties in your Office Communicator The properties defined here are based on the Meeting Room properties created by the system administrator in the MGC Manager. These parameters enable you to automatically start and join your conference from Office Communicator. Before proceeding, make sure that you have set the following parameters: •

Conference name or Numeric ID



Leader (chairperson) password



Participant code (conference entry password)



Domain

Optional parameters (if the conferencing server—MCU is connected to PSTN/ISDN lines): •

Toll dial-in number (assigned to the conference)



Toll free number (assigned to the conference)

To define your conference properties: 1 In Office Communicator, in the Actions menu, click Options. 2

3-18

In the Options dialog box, click the Accounts tab.

Polycom-Microsoft Deployment Guide

3

In the Conferencing Information section, enter the following information: Table 3-1

4

Conference Information Parameters

Field

Description

Conference ID

Enter the name assigned to your Meeting Room in the MGC environment. If an Entry Queue is used for conference access, use numerals.

Leader code

Enter the password defined for your conference in the MGC environment that identifies you as conference chairperson and enables you to control it while it is running.

Participant code

Enter the entry password defined for your conference in the MGC environment. This password enables you to start and join your conference.

Domain

Enter your domain name. This is required for callback.

Toll

Optional. Enter the dial-in number (PSTN or ISDN) assigned to the Meeting Room in MGC environment. The PSTN / ISDN dial-in numbers can be either the Meeting Room dial-in numbers or an Entry Queue number. Using a single-dial Entry Queue and specifying the target conference ID via DTMF enables you to use a limited number of PSTN dial-in numbers, which are precious resources and it might not be feasible to allocate a separate individual number for each Meeting Room.

Toll free

Optional. Enter the toll free dial-in number (PSTN or ISDN) assigned to the Meeting Room in MGC environment. Toll free numbers are usually a 1-800 number assigned to the Entry Queue and not an individual conference number. Therefore, conference ID / name specified should consist of numerals and not characters.

Click OK.

3-19

Microsoft—Polycom Meeting Scenarios

Adding a Meeting Room or an Entry Queue to the Buddy List To enable the multipoint conferencing scenarios from Windows Messenger or Office Communicator (without SIP-CX component), the Meeting Rooms and Entry Queues must be added to their buddy lists. This procedure is performed only after the Meeting Room or Entry queue is defined in the MGC Manager and LCS 2005. For more details, see Chapter 2, “Procedure 8—Defining Additional Conferencing Components in the MGC Environment” on page 2-29. Office Communicator To add the Meeting Room or Entry Queue as a Contact in the Office Communicator buddy list: Once the Meeting Room is defined and registered with the LCS, it can be added to the buddy list of all Office Communicator users in the organization. 1

On the Contacts menu, click Add a Contact.

The Add a Contact wizard opens.

3-20

Polycom-Microsoft Deployment Guide

2

Select the option to add the contact by e-mail address, and click Next.

3

Enter the Meeting Room/Entry Queue e-mail address, or use the Search option, and then click Next.

A confirmation message is displayed. 4

Click Finish. The name of the Meeting Room or Entry Queue appears in the Office Communicator Contact list.

3-21

Microsoft—Polycom Meeting Scenarios

Windows Messenger To add the Meeting Room or Entry Queue as a Contact in the Windows Messenger buddy list: Once the Meeting Room is defined, it can be added to the buddy list of all Windows Messenger users in the organization.

3-22

1

On the Tools menu, click Add a Contact. The Add a Contact wizard opens.

2

Select the option to add a contact by e-mail address, or use the Search option and then click Next.

Polycom-Microsoft Deployment Guide

3

Make sure that the selected service is SIP and enter the Meeting Room/Entry Queue SIP address.

The name of the Meeting Room or Entry Queue appears in the Windows Messenger Buddy list.

3-23

Microsoft—Polycom Meeting Scenarios

Adding Endpoints to Office Communicator, Windows Messenger and SoundPoint IP SIP 2.0 Buddy Lists Once the endpoint is registered with LCS, you can add it to the buddy list of Windows Messenger, Office Communicator and SoundPoint IP SIP version 2.0. For a detailed description of endpoint configuration and the creation of its user account in the LCS, see Chapter 2, “Endpoint Settings” on page 2-41. Office Communicator To add the endpoint as a Contact in the Office Communicator buddy list: 1 On the Contacts menu, click Add a Contact. The Add a Contact wizard opens. 2

Select the option to add the contact by e-mail address, and click Next.

3

Enter the endpoint’s e-mail address, or use the Search option, and then click Next. A confirmation message is displayed.

4

Click Finish to complete this procedure and exit the wizard, or click Next to add additional endpoints. The name of the endpoint appears in the Office Communicator Buddy list.

Windows Messenger To add the endpoint as a Contact in Windows the Messenger buddy list: 1 On the Tools menu, click Add a Contact. The Add a contact wizard opens.

3-24

2

Select the option to add a contact by E-mail address, or use the Search option and then click Next.

3

Make sure that the selected service is SIP and enter the endpoint’s SIP address. The name of the endpoint appears in the Windows Messenger Buddy list.

Polycom-Microsoft Deployment Guide

SoundPoint® IP SIP 2.0 To add the endpoint as a Contact in the SoundPoint® IP SIP 2.0 buddy list: 1 Press the Buddies soft key on the idle display to get to the Buddy Status screen or press Menu > Features > Presence > Buddy Status. 2

Press More.

3

Press Add.

4

Enter the number of the buddy, for example, 7778.

5

Press Submit. If the buddy is added successfully, you are able to scroll to it on the Buddy Status screen.

Any contacts added through the SoundPoint® IP 2.0 buddy list will appear in as a contact in Office Communicator and Windows Messenger.

3-25

Microsoft—Polycom Meeting Scenarios

Creating the Contact List on the VSX or V500 System With VSX and V500 version 8.5, you can set up a list of contacts, then see their availability and call them by selecting from the list. For more details, see Chapter 2, “VSX Settings” on page 2-41. Displaying Contacts on the Home Screen When you are registered to LCS, your LCS contacts appear in the Directory. In addition, you can display the contact list on the system home screen.

To display contacts on the home screen: 1 Go to System > Admin Settings > General > Home Screen Settings. 2

Select Contact List. Besides LCS contacts, the home screen also displays sites you have entered on the Sites screen at System > Admin Settings > General > Home Screen Settings.

To configure display options for contact list information: 1 Go to System > Admin Settings > Global Services > Directory Servers > Microsoft. You can also select the global directory server icon at the top of the Directory screen.

3-26

Polycom-Microsoft Deployment Guide

2

Configure these settings: Table 3-2

Directory Server - Microsoft Settings

Setting

Description

Display Contacts

Specifies whether to display your contacts on the contact list home screen and in the directory.

Show My Offline Contacts

Specifies whether to include offline contacts on the contact list home screen or in the directory.

Viewing and Changing Presence Status Icons next to contact list sites indicate whether the system is available to take a call. The following table describes each status icon that appears on the VSX or V500 system, either in the Directory or on the home screen. Table 3-1 Status Available

VSX Presence Icons VSX System Icon

Description The video conferencing system is powered on and is available to take calls. • The system is set to I am available.

• • Busy

The system is not in a call, or it is in a call but able to add another site.

The video conferencing system is powered on but is not available to take calls for one of the following reasons: • The system is set to I am Busy.

• • Offline

Do Not Disturb is not enabled on the system.

Do Not Disturb is enabled on the system. The system is in a call and cannot add another site.

The video conferencing system is powered off.

3-27

Microsoft—Polycom Meeting Scenarios

Setting your status to I am Available or I am Busy on the contact list home screen changes the Do Not Disturb icon status (if displayed) on the Place a Call screen. Likewise, changing the Do Not Disturb icon on the Place a Call screen changes your status on the contact list home screen.

3-28

Polycom-Microsoft Deployment Guide

Multipoint Conferencing Scenarios This section describes the various multipoint conferencing scenarios available with Microsoft Windows Messenger or Office Communicator and Polycom endpoints and MGC unit.

Meet Me—Starting an Ongoing Video Conference from Windows Messenger and Office Communicator The Meeting Room that was added to the buddy list of Office Communicator or Windows Messenger can be used to start a multipoint video conference. You select it from the buddy list. PVX, VSX and legacy endpoints can all dial the Meeting Room number (ISDN)/alias (H.323)/ SIP URI to join the running conference. To start a video conference using the Meeting Room in Windows Messenger: 1 In the Windows Messenger buddy list, right-click the Meeting Room name, and then click Start a Video Conversation.

3-29

Microsoft—Polycom Meeting Scenarios

The video is displayed in the Windows Messenger window.

Since Windows Messenger does not support DTMF codes, conference password as a security measure cannot be implemented, and the video layout cannot be changed via Click&View (a feature of using Polycom endpoints and the MGC MCU). The Meeting Room is activated, and you are added to the Meeting Room as the first participant. The video layout displayed in the Windows Messenger window depends on the Meeting Room video settings.

3-30

Polycom-Microsoft Deployment Guide

To start a video conference using the Meeting Room in Office Communicator: 1 In Office Communicator buddy list, select the Meeting Room (for example, MR01) and then click Call.

The Conversation window opens. 2

Click the Start a video conversation icon to activate and join the conference.

3-31

Microsoft—Polycom Meeting Scenarios

The Meeting Room is activated, and you are added to the Meeting Room as the first participant. If a conference password is implemented as a security measure, you must enter the appropriate conference password to enter the conference using the Office Communicator keypad selected from the Audio Controls pane.

The video layout displayed in the Office Communicator window depends on the Meeting Room video settings. The conference video layout can be changed via Click&View (a feature of using Polycom endpoints and the MGC MCU) using the appropriate DTMF code. Joining the Ongoing Conference Other Windows Messenger or Office Communicator users can join the conference by selecting the same Meeting Room from the Contact/Buddy list (provided the Meeting Room was added to their contact/buddy list). Other, non-Windows Messenger or Office Communicator users can join the conference. Participants using an ISDN connection dial the conference dial-in number as allocated to the Meeting Room when it was created.

3-32

Polycom-Microsoft Deployment Guide

When using Office Communicator that supports the use of DTMF codes, a conference password can be implemented as a security measure. Office Communicator users joining the conference enter the conference password using the keypad from the Audio Controls pane. In addition, the conference video layout can be changed via Click&View (a feature of using Polycom endpoints and the MGC MCU). Participants using an H.323 connection dial a string composed of the IP Network Service Prefix and the conference numeric ID. For example, if the IP Network Service Prefix is 34 and the conference Numeric ID is 2879, H.323 participants will dial 342879 to connect to the conference. MGC Manager Monitoring The active Meeting Room is displayed in the MGC Manager, in the On Going Conferences list.

3-33

Microsoft—Polycom Meeting Scenarios

Single Dial Entry Queue An Entry Queue is used as a special routing lobby to all Meeting Rooms and conferences, enabling one dial-in number to be used for joining all conferences. Participants are routed to the destination conference by entering the conference ID using DTMF codes. This scenario is supported only with Office Communicator. Windows Messenger does not support DTMF codes.

In this mode, only one or a few Entry Queues are defined and added to the Office Communicator contacts list, which keeps the list small and easy to manage, while with Meeting Rooms, it requires each Meeting Room to be defined and added to the contacts list resulting in a long list. The Entry Queue is created and added to the buddy list of Office Communicator. The target conferences (Meeting Rooms) are also created in the MGC Manager application. This is the recommended meeting scenario. To start a video conference using the Meeting Room in Office Communicator: 1 In Office Communicator, in the buddy list, select the Entry Queue and then click Call or double-click the Entry Queue entry.

3-34

Polycom-Microsoft Deployment Guide

The Conversation window opens. 2

Click the Start a video conversation icon to activate and join the conference.

3

Once connected to the Entry Queue the IVR system prompts you for the target conference ID. Click the keypad icon in the Office Communicator Audio Controls pane.

3-35

Microsoft—Polycom Meeting Scenarios

4

On the keypad, enter the target conference ID followed by the pound (#) key.

You are moved to the conference. Joining the Ongoing Conference Other Office Communicator users can join the conference by connecting to the Entry Queue and entering the target conference ID as described in steps 1-4. Other, non-Office Communicator users can join the conference via the Entry Queue. Participants using ISDN connection dial the Entry Queue dial-in number. Participants using H.323 connection dial a string composed of the IP Network Service Prefix and the Entry Queue numeric ID. Once connected to the Entry Queue they are routed to their target conference according to the conference ID they enter using DTMF codes.

3-36

Polycom-Microsoft Deployment Guide

MGC Manager Monitoring The active Entry Queue and Meeting Room are displayed in the MGC Manager, in the On Going Conferences list.

3-37

Microsoft—Polycom Meeting Scenarios

Ad Hoc Entry Queue and Conference Creation This procedure is similar to the Single Dial Entry Queue procedure, with the exception that the Meeting Room is not defined in the MGC Manager in advance and the ongoing conference is created on-the-fly. In addition, the Entry Queue must be set as Ad-hoc, and the conference Profile must be assigned to it. There are two Ad Hoc conferencing scenarios; one that supports Office Communicator users and one that supports all users (Standard Ad Hoc conferencing) but is not recommended for Office Communicator users. Ad Hoc conferencing scenarios are supported only with Office Communicator users and are not supported with Windows Messenger as it does not support DTMF codes. Ad Hoc conferencing is the recommended scenario for Office Communicator users as no Meeting Rooms have to be defined in advance and stored in the MCU memory.

Ad Hoc Conferencing with SIP-CX Support Entry Queues are designated for SIP-CX by assigning a Profile defined as Microsoft enabled. Using such an Entry Queue, Office Communicator users call the Ad Hoc Entry Queue. The conference name is taken from the request (Subscribe) sent by the Office Communicator user, without input from the user (assuming that no validation with an external database application is performed). If a conference with this name does not exist, a new conference is created on the MCU and the conference password, chairperson password and dial-in number are taken from the same request sent by the Office Communicator user. The conference initiator is also automatically connected to the conference once it is started. The conference password is sent by conference initiator to all the conference participants. In addition, the conference dial in number is communicated to potential participants with ISDN/PSTN endpoints so they can also connect to the conference. Other Office Communicator users and ISDN/PSTN call the same Entry Queue and are routed to their conference according to the password they enter. For a detailed description of Ad-hoc conferencing with SIP-CX support, see Chapter 4, “Ad Hoc Conferencing for OC Users with SIP-CX Support” on page 4-2.

3-38

Polycom-Microsoft Deployment Guide

Standard Ad Hoc Conferencing When the user enters the target conference ID, the MCU checks for an ongoing conference with this ID. If such a conference does not exist, a new conference is created using the parameters defined in the conference Profile. The conference ID sent by the user (using DTMF codes) is assigned to the new conference For a detailed description of Ad-hoc conferencing and External database Authentication, see Chapter 4, “Standard Ad Hoc Conferencing” on page 4-5.

3-39

Microsoft—Polycom Meeting Scenarios

Dial-out to Conference Participants In this scenario, a video conference is scheduled on a Polycom MCU and it includes predefined participants; Office Communicator, Windows Messenger and other SIP and non-SIP users. At the scheduled time the conference is activated and the MCU automatically dials out to the predefined participants and connects them to the conference. Once dial out is attempted by the MCU, the INVITE request will be routed to each participant's UA assuming participant's UA is registered with the LCS at that time. For a detailed description of the conference definition, see the MGC Manager User’s Guide, Volume I, Chapter 4. To define a SIP participant: 1 In the Conference or Reservation Properties dialog box, click the Participants tab. 2

In the Participants tab, click the New button to define a new participant. The Participant Properties - Identification dialog box opens.

3-40

Polycom-Microsoft Deployment Guide

3

4

Define the following parameters: a

Name—Enter the participant name.

b

Connection Type—Select Dial-Out.

c

Interface Type—Select SIP.

d

SIP Address—Enter the participant address in the format [user name]@[domain]. Do not use spaces or special characters such as commas, quotation marks, inverted tags and so forth either in the user name or in the domain part.

e

Address Type—Select SIP URI.

f

Click OK to close the dialog box and return to the conference Properties dialog box.

Complete the conference definition and click OK.

Joining the Conference Once the conference is activated, the MCU calls the defined participants. Office Communicator and Windows Messenger users must accept the invitation sent from the video conference to join the conference ("conf4" shown in the example below, is the name of the conference running on the MCU).

3-41

Microsoft—Polycom Meeting Scenarios

Escalating Windows Messenger or Office Communicator IM Multiparty Session to an Audio/Video Conference When you invite several buddies to a Windows Messenger or Office Communicator IM session, you can add audio and video to the conference after it has started (provided that the other participants have video capabilities). These can be done in one of the following methods: •

Defining an Ad-hoc Entry Queue (see Chapter 2, “Procedure 8— Defining Additional Conferencing Components in the MGC Environment” on page 2-29) and registering this Entry Queue with the LCS so it will appear in the buddy list (see Chapter 3, “Multipoint Conferencing—Preparations” on page 3-3).



Using Office Communicator native conferencing capabilities; using the new conference icon (no need to add the MGC Entry Queue to the Contacts list).

Windows Messenger To add Audio and Video to a Windows Messenger session: 1 Start a Windows Messenger session by inviting the required buddies from the list.

3-42

Polycom-Microsoft Deployment Guide

2

Add a new buddy to the conference, selecting the Ad-hoc Entry Queue from the buddy list.

A new conference is created and is automatically assigned an identification number (for example, 6741). An invitation to join the video conference is sent from the MCU (conference 6741) to all the IM session participants.

3

Participants must accept the invitation to join the video conference.

3-43

Microsoft—Polycom Meeting Scenarios

4

Once the invitation is accepted and the participant joins the conference, the video is displayed in Windows Messenger window according to the selected conference layout.

The ongoing video conference is also added to the list of On Going Conferences in the MGC Manager application.

3-44

Polycom-Microsoft Deployment Guide

Office Communicator To add Audio and Video to an Office Communicator session: 1 Start an Office Communicator session by inviting the required buddies from the list. 2

Add the Ad-hoc Entry Queue from the buddy list: a

Click the Invite someone to join this conversation icon.

3-45

Microsoft—Polycom Meeting Scenarios

b

3-46

In the Invite someone to join this conversation window, select the name of the ad-hoc Entry Queue.

Polycom-Microsoft Deployment Guide

3

A new conference is created and is automatically assigned an identification number (for example, 6741). An invitation to join the video conference is sent from the MCU (conference 6741) to all the IM session participants.

4

Participants must accept the invitation to join the video conference.

3-47

Microsoft—Polycom Meeting Scenarios

5

Once the invitation is accepted and the participant joins the conference, the video is displayed in the Windows Messenger window according to the selected conference layout.

The ongoing video conference is also added to the list of On Going Conferences in the MGC Manager application.

3-48

Polycom-Microsoft Deployment Guide

Office Communicator New Multipoint Conferencing Scenarios Based on SIP-CX Protocol This section describes Office Communicator New Multipoint Conferencing Scenarios Based on Microsoft SIP-CX conference control capabilities. SIP-CX protocol enables Office Communicator users complete conference control from within the Office Communicator client; monitor their ongoing conference, invite others to join their conference and schedule a conference. It also enables users to select the conferencing device with which to join the conference; Office Communicator, phone, video conferencing system or a mobile 3G videophone.

Starting a New Conference Directly from within Office Communicator To start a new audio or video conference: 1 In the Office Communicator, click Actions—>More—>Start a New Conference.

3-49

Microsoft—Polycom Meeting Scenarios

The Join the Conference dialog box opens, with the indication Connecting to the conference. Once the connection to the conference is established, you are requested to select where the conferencing service will call you back to connect you to the conference. 2

Select the callback number / address to be used by the MGC.

Select one of the following options: — — — a

A predefined E.164 number Computer to specify the Office Communicator client Other Address to specify any SIP URI. If you select Other Address, the New Address dialog box opens.

b

Enter the SIP URI in the format: sip:user name@domain. To specify a non-SIP callback address the Office Communicator user enters the "user=xxx" attribute. For example, an H.323 callback address is specified with "123" as the target address: [email protected];user=h323. This would result in the MGC initiating an H.323 dial out to alias=123 via its configured gatekeeper.

3-50

Polycom-Microsoft Deployment Guide

3

The Office Communicator is expanded to show the video window and the conference controls, and your self image is displayed in the video window. In addition, the conference connection parameters are displayed in the Conversation window.

3-51

Microsoft—Polycom Meeting Scenarios

An Office Communicator User Invites another Office Communicator Contact to the Conference Office Communicator users running a conference can invite other Office Communicator users to their conference. To Invite another Office Communicator user to your conference: 1 In Office Communicator, click Actions and then click Invite Someone to Join This Conversation.

3-52

Polycom-Microsoft Deployment Guide

2

Select the contact to be invited to your conference from the contacts list, or enter the contact name to find.

An invitation is sent from the inviter to the invitee’s Office Communicator UA with the conference details which are displayed in the invitee's Office Communicator client. 3

The invitee must accept the invitation to become a conference watcher/ controller and may select dialing in or call back as described for "Starting a New Conference Directly from within Office Communicator” on page 3-49.

3-53

Microsoft—Polycom Meeting Scenarios

An Office Communicator User Joins an Existing Conference An Office Communicator user can select to join someone else's conference by specifying the conference details (name and password). To Join an existing conference: 1 In Office Communicator, click Actions, click More, and then click Join an Existing Conference.

2

3-54

In the Enter Conference Information dialog box, enter the conference name (in the format name@domain), conference entry password (participant passcode) and chairperson password (Leader passcode) (optional).

Polycom-Microsoft Deployment Guide

3

The user gets an invitation in his Conversation window with the conference details.

The user can join the conference with their preferred media either by dialing in using the displayed conference SIP URI, or select/specify a callback number/address in the displayed Join the Conference dialog.

3-55

Microsoft—Polycom Meeting Scenarios

An Office Communicator User Dials out to another Office Communicator User Office Communicator users can specify and add a new participant to their ongoing conference. The invitee MUST be on the user’s Office Communicator contact list but can be offline or can be away and the connection can be done to the user’s media device such as cellular phone, laptop, telephone, etc. To dial out to another Office Communicator user: 1 Start a new conference.

3-56

2

Add a participant that is away or offline to the conference.

3

In the Office Communicator Contacts list, right-click the contact to call, click Call via Conferencing Service, and then click Other.

Polycom-Microsoft Deployment Guide

The New Phone Number dialog box opens.

The MGC system supports the use of a dial plan for parsing and interpreting a received number as an H.323 alias, SIP URI or ISDN number to be used accordingly by the MGC system for initiating a callback to that device. The E.164 number (no SIP URI) is converted into a SIP URI by Office Communicator, inserted into the Refer-To field and sent in the REFER transaction to the MGC system. For example: the user enters "1234567". The Refer-To field sent by Office Communicator to the MGC will have: "sip:1234567@domain;user=phone". Now the MGC unit can use the dial plan, as defined in system.cfg, to parse and interpret the "1234567" string and initiate a corresponding H.323, SIP, ISDN or PSTN dial out. The REFER request sent to MGC contains a "ms-associated-sip-uri" field that includes the invitee’s URI. The MGC system can use this information to identify the name of the new participants in notifications it sends to Office Communicator conference watchers.

3-57

Microsoft—Polycom Meeting Scenarios

Adding Audio/Video to an Office Communicator Multiparty IM Session In this scenario the a multiparty IM session is escalated into an audio / video conference on a Polycom MGC unit from the Office Communicator toolbar. To escalate an Office Communicator multiparty IM Session to an audio/ video multipoint conference: 1 While a multiparty IM session is running in Office Communicator, on the toolbar click the Conference button.

3-58

Polycom-Microsoft Deployment Guide

The Join the Conference dialog box opens in the Conversation window.

2

The IM session organizer can select / specify a callback number / address to be used by the system, or selects Computer to use the audio/video device used by Office Communicator itself. The IM session organizer can select any other SIP, ISDN, PSTN, H.323 device to be called back by the MGC.

3

Click the Go button. A SIP REFER request is sent to the conferencing server (MGC) with the user's callback address. While being "referred" and until the dial out from the MGC to the participants happen, the "Calling…" status indication is displayed in the IM session organizer Office Communicator client.

4

All other IM buddies get an invitation in their Office Communicator IM pane, with PSTN dial-in details, and a hyper link to the conference. Each invitee can now select between dialing manually into the conference or having the conferencing server dial back to the selected conferencing device. Users are able to select any device for their media participation in the conference including their PSTN phone, ISDN video endpoint, a SIP UA (that can be their OC client) or an H.323 video device.

3-59

Microsoft—Polycom Meeting Scenarios

5

Click the link to select the callback option.

The Join Conference dialog box is displayed in the remaining participants Office Communicator client. 6

3-60

Select/specify a callback number / address to be used by the system, or selects Computer to use the endpoint connected to the user’s Office Communicator client.

Polycom-Microsoft Deployment Guide

Scheduling a Meeting—Office Communicator–Outlook Integration Office Communicator users can schedule conferences using Outlook from their Office Communicator client. To schedule a conference: 1 In Office Communicator, on the Actions menu, click Schedule a Conference.

3-61

Microsoft—Polycom Meeting Scenarios

The Outlook New Meeting Request window opens, with the meeting organizer’s conference information taken from the conference parameters configured in the Office Communicator Options— Accounts. For detailed description, see "Defining the Conferencing Properties in your Office Communicator” on page 3-18.

The following parameters are displayed:

2

— The conference SIP URI, for example, [email protected] — Conference toll free dial in number, for example, 1-800-3333333 — Conference toll number, for example, 617-1111111111 — Conference entry Password, for example, 5678 You can add to the invitation conference participants, subject, location, date and time as with any regular Outlook invitation.

At the conference due time the Outlook invitation reminder opens on all invitees’ PCs. Invitees can select between using the displayed conference information for dialing in and joining the conference or click the Join Conference link which will activate your Office Communicator application and use the callback option.

3-62

Polycom-Microsoft Deployment Guide

Starting a Data Sharing Session During an ongoing point-to-point or multipoint audio and video meeting you can add data sharing; application sharing and whiteboard. The data sharing invitation is sent to all meeting participants. To start a data sharing session during an ongoing conference: 1

In the Conversation window, click the Data Sharing button.

2

An invitation is sent to all the meeting participants who must accept it in order to participate in the sharing session.

3-63

Microsoft—Polycom Meeting Scenarios

Once the invitation is accepted by the meeting participants, the Sharing Controls at the bottom of the Conversation window are enabled. 3

3-64

Click the Application Sharing button to start an application sharing session.

Polycom-Microsoft Deployment Guide

The Sharing dialog box opens.

4

Click the application you want to share, and click the Share button. The Application opens on the computers of all meeting participants.

3-65

Microsoft—Polycom Meeting Scenarios

Conference Control via Office Communicator SIP-CX Protocol Once the conference has started, the meeting organizer can perform various operations using the Office Communicator controls.

Controls available to the meeting organizer: •

Self Mute/Unmute



Leave conference



Lock conference



Mute/Unmute all but me



Terminate the conference



Change self broadcasting and listening volumes

Participant that is not the meeting organizer can mute or unmute the endpoint and change the self broadcasting and listening volumes.

3-66

Polycom-Microsoft Deployment Guide

In addition, using the participant menu, the meeting organizer can: •

Mute/Unmute a participant



Remove participant from the conference



Play recorded announcement



Send a file or e-mail to the participant

3-67

Microsoft—Polycom Meeting Scenarios

3-68

4 Ad-hoc Conferencing and Active Directory Integration An ad hoc conference is a conference that is started instantly, without a reservation or conference definition. The new conference parameters are taken from a Profile that is stored on the MCU. In contrast to Meeting Rooms that are defined individually and saved on the MCU, in ad-hoc conferencing only the Profile is predefined and it is used to start many conferences, saving configuration time and MCU resources. Once an adhoc conference is started it becomes an On Going Conference and it is monitored and controlled as any standard On Going Conference. The Microsoft-Polycom solution supports two Ad Hoc conferencing solutions: •

Ad Hoc conferencing for Office Communicator with SIP-CX support



Standard Ad Hoc conferencing

4-1

Ad-hoc Conferencing and Active Directory Integration

Ad Hoc Conferencing for OC Users with SIP-CX Support In MGC version 8.0, in addition to the support for standard Ad Hoc conferencing, you can designate a Profile to support SIP-CX Office Communicator users. This is done by specifying a conference Profile that is Microsoft-specified in the system configuration file. Using such a Profile, Office Communicator users request to start a new conference from their Office Communicator (Actions ->More ->Start a New Conference). The name of the conference is defined in the Office Communicator (Actions ->Options ->Accounts tab, Conference Properties pane) and its prefix is also defined in the LCS - Static Routes. The Subscribe request sent from the Office Communicator to the LCS is forwarded to the MCU according to the definition in the Static Routes. Once the call reaches the MCU, it checks whether a conference by the name included in the subscribe request is running on the MCU. If such a conference does not exist on the MCU, the system create a new conference based on the Profile designated to support Microsoft SIP-CX conferencing requests. The conference name, the conference password, chairperson password and dial-in number are taken from the request (Subscribe) sent by the Office Communicator user, without input from the user. The conference initiator is also automatically connected to the conference once it is started. If required, the conference dial-in number and password are communicated to participants with ISDN/PSTN endpoints so they can also connect to the conference directly, or if required via an Entry Queue that is configured to use password for routing participants to their destination conferences. In this scenario, the Office Communicator user must be the first participant to connect and start the conference. ISDN/PSTN participants can only join a running conference, or start their own conference from a Meeting Room.

4-2

Polycom-Microsoft Deployment Guide

Requirements for Ad Hoc Conferencing with SIP-CX Support Before a participant can initiate an Ad-hoc conference, the following components must be defined on the MGC unit. •

Profiles A Profiles that includes the conference parameters. The Profile must be designated to support Microsoft CIP-CX conferencing requests in the MCU configuration file. For a detailed description of Profile definition, see "Profiles” on page 4-11.



Flag Setting in the configuration file (Profile setting) Specify the name of the Profile to be used for Microsoft CIP-CX Ad Hoc conferencing in the system.cfg configuration file.

Optional: •

Flag Setting in the configuration file (Entry Queue Routing method) To enable ISDN/PSTN endpoints to connect to the conference via Entry Queue, using the conference password for routing to the destination conference, the MCU must be set to support Password as the Entry Queue Routing method. This is done by setting the appropriate flag in the system.cfg file.

4-3

Ad-hoc Conferencing and Active Directory Integration

Flag Settings for Ad Hoc Conferencing with SIP-CX Support To designated a Profile as Ad Hoc for Microsoft Office Communicator SIP-CX users, in the system.cfg in the SIP section, manually add the flag AD_HOC_PROFILE_ MSFT with the Profile name. For example, if the flag is set to AD_HOC_PROFILE_ MSFT=OCMR, the the Profile named OCMR is designated as Ad Hoc for Microsoft Office Communicator SIP-CX users and the conference parameters will be taken from this Profile. The Profile line rate and video parameters must match the SIP endpoint capabilities, as configured in Office Communicator. As the system.cfg flags must be written in capital letters, the Profile name must also be defined using capital letters (the MCU is case sensitive), and it is not recommended to use spaces.

To Set the Profile as Microsoft SIP-CX enabled: 1 Right-click on the MCU icon, then click MCU Utils and then click Edit “system.cfg”. 2

In the SysConfig dialog box, select the SIP section

3

Click the Set Value button.

4

Click the Add-Item button. The Add Item dialog box opens.

5

In the Item field, enter AD_HOC_PROFILE_ MSFT.

6

In the Value field, enter the name of the Profile to be used for conferences initiated by Office Communicator SIP-CX users. For example, if you enter OCMR, the conference parameters will be taken from the Profile named OCMR.

7

Click OK. The new flag is added to the SIP section.

Optional. To modify the routing method: 8 Return to the Section list, and select the section GREET_AND_GUIDE\IVR. 9

Set the flag QUICK_LOG_IN_VIA_ENTRY_QUEUE to YES.

To Complete the flag definition: 10 Click OK to apply the changes, or select another section to set up its flags.

4-4

Polycom-Microsoft Deployment Guide

Standard Ad Hoc Conferencing The Active Directory is used as an external database for validation. The validation can be done at the Entry Queue level or at the conference level, or both. The database can contain additional information associated with the ID entered by the user. This information can be sent back to the MCU together with the permission to create the conference and it replaces the conference data taken from the Profile. At the Entry Queue level, the user is prompted for the conference ID. The ID entered by the user is checked against the list of ongoing conferences. If such a conference does not exist on the MCU, a query is sent to the Active Directory server to verify whether this ID can be used to create a new conference. If the ID is confirmed, a new conference is started on the MCU. If additional data is defined for this ID, the information is returned from the Active Directory to the MCU and it replaces the existing conference data taken from the Profile. The following fields can be returned by the Active Directory for the conference: •

The conference name.



The conference entry and chairperson passwords.



The conference billing code.



The conference owner.



The maximum number of participants allowed for the conference.



The minimum number of participants for whom resources should be reserved.



The contents of the User Defined fields for the conference, that is, conference information to be written to the CDR file, such as the company name or telephone number.

At the conference level, the participant’s access to the conference or the participant’s role as the conference chairperson are validated with the Active Directory server. If the password entered by the user is used as a PIN code to identify the user, this information is returned from the Active Directory to the MCU and is displayed in the Participant Properties dialog box in the MGC Manager application and is save to the CDR file. The following participant parameters can be returned from the Active Directory database to the MCU: •

The participant's visual name.



Whether or not the participant is a conference chairperson.

4-5

Ad-hoc Conferencing and Active Directory Integration



Whether or not the participant is a VIP.



The contents of the User Defined fields for the participant, that is participant information to be written to the CDR file, such as the participant's e-mail address.

Standard Ad Hoc Conferencing Requirements Before a participant can initiate an Ad-hoc conference, the following components must be defined: •

Profiles Profiles are conference templates stored on the MCU, designed mainly for Ad Hoc conferences.



Entry Queue Service The Entry Queue Service includes voice prompts and it is configured to prompt for the conference Numeric ID. The Numeric ID as routing method (for standard OC clients) is used to check whether the required conference is running or a new one should be created. When creating a new conference, the Numeric ID is used to validate the creation of the new conference with an external database if validation is required, and configured for the Entry Queue Service.



Ad Hoc-enabled Entry Queue This routing Lobby is configured to initiate an ad hoc conference based on the Entry Queue Service and the Profile assigned to it. You can designate an Ad Hoc Entry Queue for Office Communicator users. In such a case, the new conference passwords are taken from the Office Communicator user parameters.



Active Directory (external database) - Optional. The Active Directory can be used to validate the user right to start a new conference. To work with the Active Directory database, the Entry Queue and IVR Services must be configured accordingly. In addition, the appropriate MCU flags must be set in the MGC configuration file.

4-6

Polycom-Microsoft Deployment Guide

Standard Ad Hoc Conferencing and Validation Scenarios Ad-hoc conferences can be created with or without validation from the Active Directory. In all these scenarios, the Entry Queue is configured to support ad hoc conferencing. In addition, the right to join a conference or be defined as its chairperson can be validated with an external database. In such a case, a user that enters any number that is defined in the database can join the conference. However, this method can be used as a PIN code if the database returns additional user parameters that can identify the user and can be added to the CDR file. The validation of the password with an external database is configured in the IVR Service assigned to the conference. Ad Hoc Conferencing without Active Directory Validation This method allows any participant to dial-in to the Entry Queue to initiate an Ad-hoc conference on the MCU. To start an Ad-hoc conference without validation: 11 In LCS 2005, create a User account for the Entry Queue. For details, see Chapter 2. 12 In the MGC Manager application, define a conference Profile containing the conference parameters. 13 In the MGC Manager application, configure an Entry Queue Service with the appropriate Numeric ID Request messages. 14 In the MGC Manager application, define an Entry Queue in which the Ad Hoc option is enabled, and a conference Profile and an Ad Hoc-enabled Entry Queue Service are assigned. As the system is case sensitive, use the same name defined in the LCS for the Entry Queue user account. 15 In the Office Communicator window, add the Entry Queue as a new contact to the Contacts list. 16 Dial-in to the Ad-hoc enabled Entry Queue. You are prompted for the Conference Numeric ID. 17 Using Office Communicator Keypad or your endpoint remote control to send DTMF codes, enter the conference ID. Using this method, if no other conference with this ID is running, the MCU creates a new conference with the Numeric ID entered by the participant. Other participants can join the conference using this Numeric ID. The conference initiator must communicate the conference Numeric

4-7

Ad-hoc Conferencing and Active Directory Integration

ID to other conference participants to let them join the conference. One method is to assign each user a personal numeric ID that can be sent to all the conference participants ahead of time. Alternatively, the conference initiator can send an E-mail with the conference ID that was just used to initiate the new conference. Ad Hoc Entry Queue with Active Directory Validation To increase system security and ensure that only users that enter an approved conference ID can start a new conference, an external database can be used to validate the conference ID entered by the participant. To start a new conference with Active Directory validation: 1 In LCS 2005, create a User account for the Entry Queue. For details, see Chapter 2. 2

In the MGC Manager application, define a conference Profile containing the conference parameters.

3

In the Active Directory database, assign users the appropriate Numeric IDs and other relevant properties for the conference and participants. This information will be returned to the MCU and will be used to replace the default information taken from the Profile.

4

In the MGC Manager application, configure an Entry Queue Service with the appropriate Numeric ID Request messages and enable the validation with the external database.

5

Configure the MCU to access the external database.

6

In the MGC Manager application, define an Ad Hoc-enabled Entry Queue with the appropriate Profile, and Entry Queue Service.

7

In the Office Communicator window, add the Entry Queue as a new contact to the Contacts list.

8

Dial in to the Ad-hoc enabled Entry Queue. You are prompted for the conference Numeric ID.

9

Using Office Communicator Keypad or your endpoint remote control to send DTMF codes, enter the conference Numeric ID.

Using this method, when the conference Numeric ID is entered by the participant, the system checks if there is an active conference with this ID. If there is an On Going Conference with this Numeric ID and the Chairperson Password is not validated with the Active Directory, the conference initiator joins the conference as chairperson. All other participants join the conference as standard participants.

4-8

Polycom-Microsoft Deployment Guide

If there is no On Going Conference with that Numeric ID, it is validated with the Active Directory database. If the number is registered in the database with the permission to start a new conference, the authorization to start the new conference is returned by the database to the MCU. If the Numeric ID is not registered in the database, the conference cannot be started and the user is disconnected from the Entry Queue. Ad Hoc Entry Queue with Conference Password Validation with Active Directory An additional security measure may be added to the Ad Hoc conference initiation by verifying the conference entry password and Chairperson Password with the Active Directory. In this case, only participants that enter a password that is registered in the database with the permission to join conferences are granted permission to join the conference. If a password is used as a PIN code to identify the user, additional information can be returned from the database to the MCU, replacing default participant information. This information is also recorded in the CDR file. To initiate an Ad-hoc conference with conference password or chairperson password validation: 1 In LCS 2005, create a User account for the Entry Queue. For details, see Chapter 2. 2

In the MGC Manager application, in the IVR Service, enable the validation with the external database (Conference Entry Password or Chairperson Password). The Chairperson Password validation should be done only when the participant enters the chairperson identifier key (either pound or star).

3

In the MGC Manager application, define a conference Profile containing the conference parameters. Make sure to select an IVR Service in which external database access for validation is enabled.

4

In the Active Directory database, assign users the appropriate Numeric IDs, conference or chairperson password, the participant's CLI number or Alias (optional) and other relevant properties for the participant. This information will be returned to the MCU and will be used to replace the default information taken from the Profile.

5

In the MGC Manager application, configure an Entry Queue Service with the appropriate Numeric ID Request messages and enable validation with the external database.

4-9

Ad-hoc Conferencing and Active Directory Integration

6

Configure the MCU to access the external database.

7

In the MGC Manager application, define an Ad Hoc-enabled Entry Queue with the appropriate Profile, and Entry Queue Service.

8

In the Office Communicator window, add the Entry Queue as a new contact to the Contacts list.

9

Dial in to the Ad Hoc-enabled Entry Queue. You are prompted for the Conference Numeric ID.

10 Using Office Communicator Keypad or your endpoint remote control to send DTMF codes, enter the conference Numeric ID. 11 Using Office Communicator Keypad or your endpoint remote control to send DTMF codes, enter the conference password or chairperson password, depending on the IVR Service configuration. Using this method, when the conference Numeric ID is entered by the participant, the system checks if there is an active conference with this ID. If there is an On Going Conference with this Numeric ID and the chairperson password is not validated with the Active Directory, the conference initiator joins the conference as Chairperson. All other participants join the conference as standard participants. If there is no On Going Conference with that Numeric ID, it is validated with the Active Directory database. If the number is registered in the database with the permission to start a new conference, the authorization to start the new conference is returned by the database to the MCU. In addition, the Conference Entry Password and the Chairperson Password are also returned to the MCU and override the parameters in the conference Profile. If this Numeric ID is not registered in the database, the conference cannot be started and the user is disconnected from the Entry Queue. When the participant is moved to the conference, the participant is prompted for the conference password or the chairperson password, depending on the IVR Service configuration. This password is validated with the Active Directory database. If there is a match, the external database application can also return the following parameters to the MCU:

4-10



Participant name (visual name)



Whether or not the participant is the conference chairperson



Whether or not the participant status is VIP



The User Defined 1, 2, 3 and 4 fields in the participant Properties

Polycom-Microsoft Deployment Guide

If the password is incorrect, and the Operator’s Assistance option is enabled, the participant is moved to the Participants Queue for assistance. If there is no active Operator conference running on the system, the participant is disconnected from the MCU.

Defining the Standard Ad Hoc Conferencing Components in the MGC Environment The following components must be defined in the MGC to enable Ad Hoc Conferencing in the Microsoft-Polycom environment: •

Conference Profiles



Entry Queue and IVR Services



Entry Queues



System Flags

System flags can be defined anytime during the definition process of the components. The MCU must be reset after system flag modifications for changes to take effect.

Profiles Profiles are stored on the MCU and can only be accessed from the MCU Configuration tree by an operator with Superuser permission. Profile definition is done in the same way as defining a regular conference. It is recommended to create only Profiles required for Ad-hoc conferences and use templates (database or MGC) for all other conferencing modes. To define a new Profile: 1 In the MGC Manager Browser area, expand the MCU tree and then expand the MCU Configuration tree. 2

Right-click the Profiles icon, and then click New Profile. The Conference Properties - General dialog box is displayed.

3

In the Name field, enter the Profile name using capital letters as this Profile name will be set later in the system.cfg to identify the Entry Queue to which it is assigned as being used in Office Communicator SIP-CX environment. This will enable the MGC to take the required information (such as conference name and passwords) from the SIP

4-11

Ad-hoc Conferencing and Active Directory Integration

subscribe request. If defining a Profile for standard Ad Hoc conferencing, you can name the profile lower or upper case letters. 4

Define the Profile parameters. The definition of these parameters is identical to the Conference Template parameter definition. The Profile line rate and video parameters must match the SIP endpoint capabilities, as configured in Office Communicator. For more details, see the MGC Manager User’s Guide, Volume I, Chapter 4. —

In standard Ad Hoc conferencing, if conference access is validated with the Active Directory server, in the Properties Settings dialog box select an IVR Service in which the External Server Authentication option is set to Always or Upon Request

.



It is not recommended to enter the Conference Entry Password, Chairperson Password and the conference Numeric ID in the profile.



The option for adding participants to the Profile is intended for recording port and cascading link definitions and should not be used for Ad Hoc conferencing in Microsoft environment.

Entry Queue Service Definition If you configure the MCU to use Password as the Entry Queue routing method, you must select the appropriate voice messages for password related prompts. In standard Ad Hoc conferencing, if an external database is used for authentication for conference creation, the authentication process must be enabled in the Entry Queue Service. You can also enable the authentication process for joining the conference by enabling it in the IVR Service.

4-12

Polycom-Microsoft Deployment Guide

To select the Password Request prompts in the Entry Queue Service: 1 Right-click the IVR Services icon, and then click New Entry Queue Service.

The Entry Queue Service General dialog box opens. 2

Define the Entry Queue parameters as described in the MGC Manager User’s Guide, Volume II, Chapter 2.

3

In the Conference ID dialog box, select voice messages for the following prompts:

Table 4-1: Entry Queue Properties - Conference Id Prompts Field/Option

Description

Request Conference ID/ Password

Prompts the participant for the conference Numeric ID or password, depending on the Entry Queue routing mode as configured in the "system.cfg" file.

4-13

Ad-hoc Conferencing and Active Directory Integration

Table 4-1: Entry Queue Properties - Conference Id Prompts

4

Field/Option

Description

Join Failure Message

When the participant entered an incorrect conference Numeric ID or password, requests the participant to type the Numeric ID or password again.

Assign an audio file to each message type, as follows: a

Click the table entry (Name). The message type appears at the bottom of the table and the drop-down list displays the names of the audio files stored in the MGC unit’s memory.

b

Select the appropriate file from the Message File list.

If the files were not downloaded prior to the definition of the IVR Service or if you want to add new audio files, click Add Message File to download the appropriate audio file to the MGC unit’s memory. For the downloading procedure, see the MGC Manager User’s Guide, Volume II, Chapter 2, “Defining a New Entry Queue Service”.

Entry Queue Service with Access to the External Database Entry Queue Services can be configured to validation the participant right to start a new conference with the Active Directory database, using the conference Numeric ID entered by the participant when accessing the Entry Queue. In such a case, the Entry Queue Service must be configured to prompt for the conference Numeric ID, and the MCU must be configured to use Numeric ID as the routing method. This mode is applicable to standard Ad Hoc conferencing with external database validation only. This procedure should be skipped when using Ad Hoc conferencing with SIP-CX support or Standard Ad Hoc conferencing without external database validation.

To define the access to the External Database application: 1 Access the parameters of an existing Entry Queue Service, or create a New Entry Queue Service. The Entry Queue Service General dialog box opens.

4-14

Polycom-Microsoft Deployment Guide

2

Define the Entry Queue parameters as described in the MGC Manager User’s Guide, Volume II, Chapter 2, “Defining a New Entry Queue Service”. — In the General dialog box, in the External Server field, select Conference NID to validate the conference Numeric ID with the Active Directory server. — In the Conference ID dialog box, select the appropriate voice messages to prompt participants for the conference ID.

IVR Service with Access to the External Database Application Entry Queue Services can be configured to validation the participant right to join a conference with the Active Directory database, using the conference password. This mode is applicable to standard Ad Hoc conferencing with external database validation only. This procedure should be skipped when using Ad Hoc conferencing with SIP-CX support or Standard Ad Hoc conferencing without external database validation.

To configure the IVR Service with Active Directory Validation: 1 Access the parameters of an existing IVR Service, or create a New IVR Service. 2

Define the IVR Service parameters as described in the MGC Manager User’s Guide, Volume II, Chapter 2. — In the General dialog box, in the External Server field, select: • Never to disable this option. • Upon Request to verify the Chairperson Password with an external database application. The validation process occurs only when the participant enters the Chairperson Identifier key (pound or star). All other participants are connected to the conference as standard, undefined participants. • Always to verify the Conference Entry Password (or the participant’s personal password) with an external database application. The verification process occurs for all participants attempting to join the conference.

4-15

Ad-hoc Conferencing and Active Directory Integration

Ad Hoc-enabled Entry Queue To enable Ad Hoc conferencing, enable the Ad Hoc option in the Entry Queue and assign the appropriate Profile and Entry Queue Service to it. To define an Ad Hoc-enabled Entry Queue: 1 Ensure that the Profiles and Entry Queue Service are defined prior to the definition of the Ad Hoc-enabled Entry Queue conference.

4-16

2

Right-click the Meeting Rooms, Entry Queues & SIP Factories icon, and then click New Entry Queue. The Entry Queue Properties dialog box opens.

3

In the Entry Queue Properties dialog box, define the Entry Queue parameters:

a

In the Name box, enter a name for the Entry Queue. This name will be used to call the Entry Queue. In Standard Ad Hoc Conferencing, enter the name defined in the LCS for the user account representing the Entry Queue. The MGC system is case sensitive.

b

In the Entry Queue Service list, select the Message Service to be used with this Entry Queue.

Polycom-Microsoft Deployment Guide

Select the appropriate service if External database validation is required. c

In the Numeric ID field, 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.

d

Select the Ad Hoc check box to enable ad hoc conferencing.

e

If Ad Hoc option was selected, select the name of the Profile whose conference parameters will be used to create of the target conference. In SIP-CX enabled Ad Hoc conferencing, the Profile name is also defined in the system.cfg to enable the MGC to identify this Entry Queue as being used in Office Communicator SIP-CX environment and take the required information (such as conference name and passwords) from the SIP Subscribe request.

To define an Ad Hoc Entry Queue, at least one conference Profile must be defined in the MGC Manager.

f

If the Entry Queue will be also 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.

g

Click OK.

4-17

Ad-hoc Conferencing and Active Directory Integration

System Flags Configuration Various system configuration flags must be set to enable Ad Hoc Conferencing with SIP-CX support and for standard Ad Hoc Conferencing with Active Directory validation. All these flags are set in the system.cfg files. For a detailed description of the flag settings for Ad Hoc conferencing with SIP-CX support, see "Flag Settings for Ad Hoc Conferencing with SIP-CX Support” on page 4-4. To access the appropriate flags in the system.cfg: 1 Right-click on the MCU icon, then click MCU Utils and then click Edit “system.cfg”.

4-18

Polycom-Microsoft Deployment Guide

The SysConfig dialog box appears. List of sections containing parameters whose values can be modified. To view/modify the parameter values, double-click

When a parameter is selected, the value is displayed

Use these buttons to add new parameters to the file

When a parameter is selected, the value is displayed

Use these buttons to remove a section/subsection or line from the file

2

Modify the required flags, as described in the procedures below and click OK.

3

After changes in the MCU flags, reset the MCU for the changes to take effect.

For more details about setting system.cfg flags, see the MGC Administrator’s Guide, Chapter 5. Configuring the Access to an External Database Application for Validation (Standard Ad Hoc Conferencing) In Ad-hoc conferencing with Active Directory validation, access to the Active Directory database must be configured for the MCU in the MGC Manager application, in the “system.cfg” file. To set the external database flags in the system configuration file: 1 In the SysConfig dialog box, In the Section pane, double-click the EXTERNAL DB option. The External DB flags are displayed in the Item =Value pane.

4-19

Ad-hoc Conferencing and Active Directory Integration

2

In the Item=Value pane, define the following flags: Table 4-2

3

4-20

System.cfg Values for Accessing External Database Application

Flag

Description and Value

EXTERNAL_DB_IP

The IP address of the Active Directory server.

EXTERNAL_DB_PO RT

The port number used by the MCU to access the Active Directory server.

EXTERNAL_DB_LO GIN

The user name defined in the Active Directory for the MCU. The default user name is: POLYCOM.

EXTERNAL_DB_PA SSWORD

The password associated with the user name defined for the MCU in the Active Directory. The default password is: POLYCOM.

EXTERNAL_DB_DI RECTORY

The URL of the Active Directory server.

Click OK.

5 Limitations and Pending Issues Known Limitations •

The IP+48 card installed in the MGC unit supports up to 24 concurrent Office Communicator SIP-CX users connections to conferences running on the MGC unit. This is because each Office Communicator SIP-CX user appears as two users to the MGC system: media and controller/watcher.

IP+24 and IP+12 card capacities (24 and 12 participants respectively) do not change in this mode.

You can cancel the SIP-CX environment settings by changing the appropriate flag settings in the system.cfg configuration file. In this mode, the SIP-CX conferencing scenarios and conference control tool are unavailable to Office Communicator users. For a description of the flag configuration see Appendix A, “Canceling the SIP-CX Environment Setting” on page A-4. •

In Office Communicator, the Keypad for entering DTMF codes is unavailable in multipoint conferences. The Keypad is available in point-to-point meetings.



In Office Communicator, when using the option to join an existing conference, an additional Conversation window opens and the Office Communicator user must accept the invitation in order to connect to the conference. This is the Office Communicator design.



The number of digits in the ISDN, H.323 and SIP dial-out strings provided by the Office Communicator user when specifying a callback number must be identical to the number of digits specified

5-1

Limitations and Pending Issues

in the corresponding flags in the system configuration file in the MGC (system.cfg). Note: this limitation is not relevant to SIP-CX callback, where the callback string is specified (using the tag format user=x), and the protocol is specified exactly in the tag and is not indicated in the string as a prefix. •

When adding a Buddy from a federated company/enterprise on the phone, although it is expected to display the actual Presence status of the federated buddy in the Buddy Status list and on the 'speed dial' keys on the phone or Expansion modules, the status is always “off-line”. If you attempt to call these endpoints, using the speed-dial key the call rings busy. Buddy Presence and dialing works correctly in a single domain and the phone presence can be 'watched' by Office Communicator or VSX clients in the other federation. To overcome this problem and call someone from another federation, manually set up a speed-dial or use URL dialing.



V2IU can be configured to restrict the bandwidth of calls going through it across Microsoft federations. In such a case, when placing a call with bandwidth higher than the bandwidth configured in the V2IU (as indicated in its SDP offer), the call will be rejected and fail. To avoid such failure when initiating cross federations calls, make sure that the bandwidth requested by LCS clients or Polycom MCU is not higher than the bandwidth configured in the V2IU.



5-2

Do not use the VSX internal MCU for multipoint calls in the Microsoft-Polycom environment. Instead, use the MGC unit.

Polycom-Microsoft Deployment Guide

Pending Issues •

VSXs with 64 MB memory cannot be used in the Microsoft-Polycom integrated environment. Use the VSXs with 128 MB memory.



The VSX Stereo must be switched off whenever the MicrosoftPolycom deployment includes multipoint conferencing with the MGC unit. To disable the VSX Stereo: — From VSX web client or directly using the VSX menu, select Settings ->Audio — Clear the surround sound check box.

5-3

Limitations and Pending Issues

5-4

Appendix A Office Communicator Callback Model When starting a new conference or when joining another conference, the Office Communicator user first becomes a watcher of the conference and then a controller. This is implemented by Office Communicator UA sending a SIP SUBSCRIBE and then an INVITE to the conferencing server (MGC unit) where the conference is defined. An Office Communicator user has basically two ways of joining a conference (his own or someone else's) with media (audio/video): Dialin and Callback: •

Dial-in — Using the conference dial in information, participants can use their favorite device to dial in directly into the conference and join it with audio and video. Microsoft currently supports E.164 dial in numbers only so no SIP or H.323 alias dial in addresses are provided via Microsoft UI.



Callback—The following stages are performed: — The Office Communicator users can select / specify the media device they would like to use for the media part. This can be the Office Communicator client or another SIP or legacy device including H.323, ISDN or PSTN device. — A REFER request is consequently sent from the user's Office Communicator to the conferencing server (MGC) where the conference is running with the user's device/address selection in the "refer-to" field. — Upon receiving the REFER request the MGC dials out to the specified device joining it to the conference with audio and video. — The Office Communicator user can specify a callback address for the media device selected for audio / video conference participation. This address is passed from the Office

A-1

Appendix A

Communicator to the conferencing server / MGC, in a REFER SIP request over the SIP-CX control dialog, and used for initiating a corresponding dial-out by the MGC to the specified address using the specified protocol which can be any of: H.323, ISDN, SIP or PSTN. — The user's selection is passed in the REFER request's Refer-To header in the following format: "sip:user@domain;user=user_type" where "user_type" can be any of the following: • h323 - for MGC to initiate an H.323 callback • isdn - for MGC to initiate an ISDN / H.320 callback • sip (or none) - for MGC to initiate a SIP callback. • phone - see explanation next To enable the callback and the selection of the device, system.cfg flags are used to interpret E.164 numbers containing digits which are passed in the REFER for some scenarios. If the callback string passed in the REFER is of the type "SIP:user@host;user=user_type" then these MGC flags are not required and are irrelevant. For example in "SIP:[email protected];user=h323" the MGC flags are irrelevant and MGC will do a H.323 dial out to alias=123. The following flags can be modified in the MGC system.cfg file, in the SIP_REFER_PREFIX_AND_PHONES section: •

DIGITS_IN_PHONE_NUMBER



DIGITS_IN_PREFIX_NUMBER



SIP_REFER_ISDN_PREFIX



SIP_REFER_H323_PREFIX



SIP_REFER_PREFIX

These flags are used by MGC in parsing an E.164 number received in a REFER request. The type of callback (SIP, ISDN, H323, PSTN) is determined by MGC based on the prefix. The prefix is used in scenarios where the user can only provide digits and cannot specify a "user=XXX" tag. In case of a missing prefix the default is PSTN.

A-2

Polycom-Microsoft Deployment Guide

Examples “user type”=h323 To initiate a callback from MGC to a H.323 video device registered under Mr. Bond's alias, the OC user would specify the following string in the "other address…" field: [email protected];user=h323 - with the H323 alias=bond specified in the SIP URI user part. Office Communicator will add a "SIP:" prefix to the user's string (if one was not added by the user) and send it to MGC as sip:[email protected];user=h323. The MGC will extract the "bond" alias and based on the "user=h323" part initiate a dial out through the configured GK (in MGC IP service) to Mr. Bond's video device joining him into the conference. The domain part of the SIP URI received is omitted by MGC and has no use.

“user_type"=phone The OC user can enter a phone number in the "other phone number" entry field or choose a phone number from his list. In either case there is no need to type: user@domain;user=phone. The user simply provides / selects the phone number and OC turns it into a SIP URI with the "user=phone" tag and passes it to MGC in the REFER's Refer-To field. If the MGC receives [email protected];user=phone, the MGC analyzes the request based on the flags definition as: DIGITS_IN_PHONE_NUMBER=7 DIGITS_IN_PREFIX_NUMBER=3 SIP_REFER_H323_PREFIX=323 MGC will initiate a H.323 dial video out call to address=1234567 (via the gatekeeper) adding the user to the conference. If the received phone number includes more digits than defined in both flags: DIGITS_IN_PHONE_NUMBER and DIGITS_IN_PREFIX, it is considered as an error and MGC will ignore the REFER request. If the received phone number includes more digits than defined in the flag DIGITS_IN_PHONE_NUMBER but less than the digits defined for both flags DIGITS_IN_PHONE_NUMBER and DIGITS_IN_PREFIX, it is considered as an error and MGC will ignore the REFER request. If the received phone number includes digits less or equal to the number of digits defined for the flag DIGITS_IN_PHONE_NUMBER (no Prefix), the MGC will initiate a PSTN dial out call to the received number.

A-3

Appendix A

Canceling the SIP-CX Environment Setting By default the MCU is configured to work with Office Communicator SIP-CX, the MCU must be configured accordingly. In this configuration, up to 24 IP participants (H.323, standard SIP and Office Communicator SIP-CX participants) can connect to one IP+48 card (instead of 48 participants). IP+24 cards and IP+12 cards capacities (24 and 12 participants respectively) do not change in this mode.

You can cancel this configuration by setting the flag SIP_CONF_WATCH_CONTROL to NO in the system configuration file. When cancelling the SIP-CX environment settings, Office Communicator users cannot use the SIP-CX conferencing scenarios and conferencing tools. To modify the default system configuration: 1 Right-click the MCU icon, click MCU Utils, and then click Edit “system.cfg”.

The Sysconfig window opens. 2

A-4

In the SECTION box, click SIP.

Polycom-Microsoft Deployment Guide

The SIP flags are displayed in the Item=Value box. 3

In the Item=Value box, click the SIP_CONF_WATCH_CONTROL flag. The flag value appears in the Edit Value box.

4

Enter NO and click the Set Value button.

5

Click OK. The Sysconfig window closes.

6

Right-click the MCU icon and then click Reset MCU.

A-5

Appendix A

A-6

Suggest Documents