Page 1 Polycom–Microsoft Integrated Solution Deployment Guide Phase 3...
Page 2 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.
Page 3: Table Of Contents
About this Guide ... 1-2 Microsoft—Polycom Environment ... 1-3 Environment Requirements ... 1-5 Microsoft—Polycom Environment Setting Microsoft—Polycom Environment Configuration ... 2-2 Endpoint Settings ... 2-33 Configuring for Office Communicator Multipoint Conference Procedure 1—Setting Up a Server As the Windows Domain Controller ...
Page 4 Table of Contents Capacity/Scalability ... 2-40 Microsoft—Polycom Meeting Scenarios ..3-1 Point-to-Point Meeting ... 3-2 Multipoint Conferencing—Preparations ... 3-3 Multipoint Conferencing Scenarios ... 3-25 Enabling Office Communicator Conferencing Features ... 3-4 Enabling Direct Conferencing from within Office Communicator in Windows ...
Page 5 Application ... 4-9 Entry Queue Service with Access to the External Database ... 4-10 IVR Service with Access to the External Database Application ... 4-11 Profiles ... 4-12 Defining Profiles ... 4-12 Ad Hoc-enabled Entry Queue ... 4-13 Polycom-Microsoft Deployment Guide...
Page 6 Table of Contents Known Limitations ......5-1 Appendix A Office Communicator Callback Model ... A-1 Canceling the SIP-CX Environment Setting ... A-4 .
Page 7: Overview
Polycom enhances Microsoft’s environment by: • enabling Polycom endpoints (VSX and PVX) to be added to Office Communicator and Windows Messenger buddy list • bridging between Microsoft SIP-only environment and legacy ISDN, PSTN and H.323 endpoints...
Page 8: Known Limitations
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: •...
Page 9: Microsoft-Polycom Environment
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.
Page 10 Overview Microsoft SIP-CX protocol is supported by the Polycom MGC environment, enabling the MGC unit to serve as a conferencing server that allows Office Communicator users to initiate and join conferences as well as control and monitor ongoing conferences. Microsoft—Polycom environment is scaleable and you can use several MCUs as conferencing servers.
Page 11: Environment Requirements
• Polycom VSX version 8.0.3 Elements of the Microsoft—Polycom Environment (Continued) Description All Polycom video endpoints supporting SIP (PVX and VSX family of room systems) and legacy endpoints supporting H.323 and H.320. Enables multipoint audio and video conferencing over IP (SIP and H.323), ISDN and PSTN networks using any...
Page 12 Overview...
Page 13: Office Communicator Callback Model
Setting Static Routes in the LCS. Defining additional conferencing components in the MGC environment; defining Meeting Rooms and Entry Queues. In addition, this chapter describes Polycom endpoint configuration to enable SIP calls. End user’s computer and Office Communicator settings are described in Chapter 3.
Page 14: Microsoft-Polycom Environment Configuration
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).
Page 15: Procedure 2-Extending The Active Directory Schema
To extend the Active Directory Schema for LCS 2005: Log on to the domain controller (server A) as an administrator. Start the Live Communications Server 2005 Setup from the domain controller server. The Live Communication Server wizard opens. Polycom-Microsoft Deployment Guide...
Page 16 Microsoft—Polycom Environment Setting Click Standard Edition Server.
Page 17 Follow the wizard’s on-screen instructions, and then click Finish. Click Prep Forest, and follow the wizard’s instructions. Follow the wizard’s on-screen instructions, and then click Finish. Click Prep Domain. Follow the wizard’s on-screen instructions, and then click Finish. Polycom-Microsoft Deployment Guide...
Page 18: Procedure 3-Live Communications Server Installation And Activation
Microsoft—Polycom Environment Setting Procedure 3—Live Communications Server Installation and Activation 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.
Page 19: Procedure 4-Lcs User Account Definition And Client Access Configuration
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.
Page 20 Microsoft—Polycom Environment Setting 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.
Page 21 Queue in the LCS, but has no significance to the conferencing process. Make sure that the Password never expires option is selected. Click Next. In the users list, right-click the new user, and then click Properties. The user Properties dialog box opens. Polycom-Microsoft Deployment Guide...
Page 22 Microsoft—Polycom Environment Setting 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@<domain name>. For example, john@polycom.com. 12 In the Server or pool box, select the Live Communications Server that was created in "Procedure 3—Live Communications Server...
Page 23: Procedure 5-Creating A Sip Network Service In The Mgc Environment
7.0 or higher, and MGC Manager version 7.0 or higher. To define an IP Network Service: The same Network Service can be used for both SIP and H.323 connections. In the MGC Manager application, expand the MCU tree and then expand the MCU Configuration tree.
Page 24 Microsoft—Polycom Environment Setting In the Settings dialog box, define the following parameters: 2-12 Enter the Network Service name In the Protocol box, select Both. Click Next.
Page 25 In the Use DNS Servers section, select Specify. In the Primary DNS Server field, enter the IP address of the LCS server. In the Local Domain Name box, enter the domain name as defined in the Active Directory (for example, polycom.com). Click Next. Polycom-Microsoft Deployment Guide 2-13...
Page 26 In the Service Mode box, select Board Hunting. In the Prefix box, enter the same prefix that has been defined for the Network Service in the gatekeeper. This number is used as part of the dial-in string given to H.323 participants connecting to conferences.
Page 27 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. Polycom-Microsoft Deployment Guide 2-15...
Page 28 Microsoft—Polycom Environment Setting 11 In the SIP Settings dialog box, define the following parameters: 12 In the SIP dialog box, click Next. 13 In the Authentication dialog box, click Next. 14 In the Span dialog box, click the plus (+) button.
Page 29 It is assigned to a specific IP address, therefore it must be unique for each MCU. In the IP Address box, enter the IP address of the IP network card installed in the MCU. In the Communication Mode list, select the data transmission rate and duplex mode, or select Auto to let the system synchronize the data transmission rate according to the network.
Page 30 2-18 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.
Page 31 To assign the IP Network Service to the IP Card: To complete the Network Service definition, you must define the properties of the IP network connected to that IP card. This is done by assigning the IP Network Service to the IP card:...
Page 32 Microsoft—Polycom Environment Setting 21 Right-click the IP card icon, and then click Properties. 22 In the Card Settings dialog box, click the IP-Network Parameters tab. 23 Clear the Null Configuration check box. 2-20...
Page 33 24 In the Circuit ID box, enter the Circuit ID defined for the IP Span in the IP Network Service. The name of the assigned Network Service is updated in the appropriate field. 25 Click OK. 26 Reset the MCU.
Page 34: Procedure 6-Defining The Mgc Unit As Trusted In The Lcs
Microsoft—Polycom Environment Setting Procedure 6—Defining the MGC Unit as Trusted in the LCS To be able to work with the LCS, the MGC unit must be configured as a trusted host in the LCS. This is done by defining each of the MGC unit’s IP cards as a trusted host.
Page 35 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. Polycom-Microsoft Deployment Guide 2-23...
Page 36: Procedure 7- Setting The Static Routes Between The Lcs And The Mgc Unit
Microsoft—Polycom Environment Setting Procedure 7— Setting the Static Routes Between the LCS and the MGC Unit Setting Static Routes in the LCS enables SIP entities / UAs to connect to conferences without explicit registration of conferences with the LCS. Routing is performed by the LCS based on the comparison between the received URI and the provisioned static route pattern.
Page 37 The server Properties dialog box opens. Click the Routing tab. Click the Add button. Polycom-Microsoft Deployment Guide 2-25...
Page 38 In the Next Hop section, in the IP address box, enter the IP address of the IP card to which the IP Network Service is assigned. In the Next Hop section, in the Port box, enter the port number on the MGC system side.
Page 39: Procedure 8-Defining Additional Conferencing Components In The Mgc Environment
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: •...
Page 40 Microsoft—Polycom Environment Setting be created for each Meeting Room, and all the Meeting Room buddies have to be added to the Office Communicator contact list, thus overloading it. Definition Procedure: • When working with MGC software version 7.0x, for each Meeting...
Page 41: Defining A Meeting Room In The Mgc Manager Application
Meeting Room using the same name as defined in the LCS user account. The MGC environment is case sensitive to Conference, Meeting Room and Entry Queue names, therefore, make sure to use the same name spelling in the LCS and the MGC Manager. Polycom-Microsoft Deployment Guide 2-29...
Page 42: Defining An Entry Queue In The Mgc Manager Application
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.
Page 43 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. Polycom-Microsoft Deployment Guide 2-31...
Page 44 Microsoft—Polycom Environment Setting 2-32 In the Target Conferences box, select Transcoding to allow all endpoint types to connect to the conference. If your MCU does not include a video card, select Video Switching. Make sure that the Audio and Video parameters are set to Auto to let the system select them.
Page 45: Endpoint Settings
Endpoint Settings Polycom VSX systems and PVX software support SIP calling through Microsoft LCS 2005 (SP1) proxy server. The following features are supported with VSX/PVX and MS LCS 2005: • Registration using MS NTML authentication method • Manual or use Network login •...
Page 46: Network Configuration
To specify SIP settings, System > Admin Settings > Network > IP > SIP Settings. Define the following parameters: 2-34 Version 8.0 has to be purchased through one of Polycom’s channel partners. Once purchased, follow the version installation procedure as described in the version’s release notes.
Page 47: Pvx Settings
10.11.12.13:5070. Proxy Server—Enter the same address as the Registrar server as the LCS performs both tasks. Version 8.0 has to be purchased through one of Polycom’s channel partners. Once purchased, follow the version installation procedure as described in the version’s release notes.
Page 48 Transport Protocol—select TCP. Type of SIP Server—select Microsoft LCS. Select either the Use network login credentials check box. In this case, the user name and password are taken from the network, or define: • User Name—Specifies the system’s SIP name as will be defined in the LCS.
Page 49: Defining A User Account In The Lcs
Make sure that the Password never expires option is selected. Click Next. In the users list, right-click the new user, and then click Properties. The user Properties dialog box opens. Proxy Server—Enter the same address as the Registrar server as the LCS performs both tasks. Polycom-Microsoft Deployment Guide 2-37...
Page 50 Microsoft—Polycom Environment Setting 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@<domain name>, as defined in the endpoint’s SIP Settings dialog box. For instance john@polycom.com.
Page 51: Adding The Endpoint To Office Communicator And Windows Messenger 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 and Windows Messenger Buddy Lists” on page 3-24. Polycom-Microsoft Deployment Guide 2-39...
Page 52: Configuring For Office Communicator Multipoint Conference
MCU includes more than one IP card, or if you want to use several MCUs in your configuration to increase system capacity, additional considerations may be required when configuring the Microsoft–Polycom environment. Figure 2-1 shows an example of such configuration.
Page 53 002MR, and they are routed to the second IP card (or MCU). IP+12 card supports up to 12 Office Communicator SIP-CX participants. IP+24 card supports up to 24 Office Communicator SIP-CX participants. Polycom-Microsoft Deployment Guide 2-41...
Page 54 Microsoft—Polycom Environment Setting 2-42...
Page 55: Microsoft-Polycom Meeting Scenarios
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...
Page 56: Point-To-Point Meeting
• 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.
Page 57: Multipoint Conferencing-Preparations
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 Polycom-Microsoft Deployment Guide...
Page 58: Enabling Office Communicator Conferencing Features
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: •...
Page 59 Right-click the Administrative Templates, and then select Add/ Remove Templates. In the Add/Remove Templates dialog box, click the Add button. Polycom-Microsoft Deployment Guide...
Page 60 Microsoft—Polycom Meeting Scenarios In the Policy Templates dialog box, select communicator.adm and click Open. The selected file is added to the Add/Remove Templates dialog box. 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...
Page 61 11 In the Feature Policies - Settings list, double-click Enable Conferencing. The Enable Conferencing Properties dialog box opens. 12 Click Enabled, and OK. Polycom-Microsoft Deployment Guide...
Page 62: Enabling Video Calls With Office Communicator
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).
Page 63 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. Polycom-Microsoft Deployment Guide...
Page 64: Bandwidth Allocation Modification
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...
Page 65 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. Click OK. Close the Group Policy window without saving (click NO when prompted). Polycom-Microsoft Deployment Guide 3-11...
Page 66: Modifying Windows Hosts List To Include The Lcs
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: Using Windows Explorer, browse to the following folder:...
Page 67 Polycom-Microsoft Deployment Guide For example: 172.22.187.159 pool01.ip.co.il 172.22.187.159 ip.co.il Save the file. 3-13...
Page 68: Signing-In Windows Messenger And Office Communicator Clients To The Live Communications Server
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.
Page 69 Click the Accounts tab. Click the Advanced button. Enter the sign-in name as defined in the LCS. In the Advanced Connection Settings dialog box, click Configure settings. Polycom-Microsoft Deployment Guide 3-15...
Page 70: Windows Messenger Configuration
Microsoft—Polycom Meeting Scenarios In Server name or IP address field, enter the IP address of the LCS server. In the Connect using box, select TCP as the protocol to use for the connection. Click OK. 10 Click OK to exit the Options dialog box.
Page 71 (Server B in the configuration). In the Connect using section, select TCP as the protocol to use for the connection. Click OK to complete the configuration. Windows Messenger can now be used to communicate between clients. Polycom-Microsoft Deployment Guide 3-17...
Page 72: Defining The Conferencing Properties In Your Office Communicator
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.
Page 73 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. Polycom-Microsoft Deployment Guide 3-19...
Page 74: Adding A Meeting Room Or An Entry Queue To The Buddy List
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.
Page 75 Enter the Meeting Room/Entry Queue e-mail address, or use the Search option, and then click Next. A confirmation message is displayed. Click Finish. The name of the Meeting Room or Entry Queue appears in the Office Communicator Contact list. Polycom-Microsoft Deployment Guide 3-21...
Page 76: Windows Messenger
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.
Page 77 Polycom-Microsoft Deployment Guide 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...
Page 78: Adding Endpoints To Office Communicator And Windows Messenger Buddy Lists
Microsoft—Polycom Meeting Scenarios Adding Endpoints to Office Communicator and Windows Messenger Buddy Lists 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 of endpoint configuration and the creation of its user account in the LCS, see Chapter 2, “Endpoint Settings”...
Page 79: Multipoint Conferencing Scenarios
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.
Page 80 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.
Page 81 To start a video conference using the Meeting Room in Office Communicator: In Office Communicator buddy list, select the Meeting Room (for example, MR01) and then click Call. The Conversation window opens. Click the Start a video conversation icon to activate and join the conference. Polycom-Microsoft Deployment Guide 3-27...
Page 82: Joining The Ongoing Conference
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...
Page 83: Mgc Manager Monitoring
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.
Page 84: Single Dial Entry Queue
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.
Page 85 Click the Start a video conversation icon to activate and join the conference. 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. Polycom-Microsoft Deployment Guide 3-31...
Page 86: Joining The Ongoing Conference
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.
Page 87: Mgc Manager Monitoring
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-33...
Page 88: Ad-Hoc Entry Queue And Conference Creation
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.
Page 89: Dial-Out To Conference Participants
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.
Page 90: Joining The Conference
Microsoft—Polycom Meeting Scenarios Define the following parameters: 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"...
Page 91: Escalating Windows Messenger Or Office Communicator Im Multiparty Session To An Audio/Video Conference
(no need to add the MGC Entry Queue to the Contacts list). Windows Messenger To add Audio and Video to a Windows Messenger session: Start a Windows Messenger session by inviting the required buddies from the list. Polycom-Microsoft Deployment Guide 3-37...
Page 92 Microsoft—Polycom Meeting Scenarios 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.
Page 93 Polycom-Microsoft Deployment Guide 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.
Page 94: Office Communicator
Microsoft—Polycom Meeting Scenarios Office Communicator To add Audio and Video to an Office Communicator session: Start an Office Communicator session by inviting the required buddies from the list. Add the Ad-hoc Entry Queue from the buddy list: 3-40 Click the Invite someone to join this conversation icon.
Page 95 Polycom-Microsoft Deployment Guide In the Invite someone to join this conversation window, select the name of the ad-hoc Entry Queue. 3-41...
Page 96 Microsoft—Polycom Meeting Scenarios 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. Participants must accept the invitation to join the video conference.
Page 97 Polycom-Microsoft Deployment Guide 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.
Page 98: Office Communicator New Multipoint Conferencing Scenarios Based On Sip-Cx Protocol
Microsoft—Polycom Meeting Scenarios 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;...
Page 99 "user=xxx" attribute. For example, an H.323 callback address is specified with "123" as the target address: 123@lcs2005.co.il;user=h323. This would result in the MGC initiating an H.323 dial out to alias=123 via its configured gatekeeper. Polycom-Microsoft Deployment Guide 3-45...
Page 100 Microsoft—Polycom Meeting Scenarios 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-46...
Page 101: 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: In Office Communicator, click Actions and then click Invite Someone to Join This Conversation. Polycom-Microsoft Deployment Guide 3-47...
Page 102 Microsoft—Polycom Meeting Scenarios 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.
Page 103: An Office Communicator User Joins An Existing Conference
In Office Communicator, click Actions, click More, and then click Join an Existing Conference. 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-49...
Page 104 Microsoft—Polycom Meeting Scenarios 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.
Page 105: An Office Communicator User Dials Out To Another Office Communicator User
To dial out to another Office Communicator user: Start a new conference. Add a participant that is away or offline to the conference. 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 3-51...
Page 106 Microsoft—Polycom Meeting Scenarios 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.
Page 107: Adding Audio/Video To An Office Communicator Multiparty Im Session
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/...
Page 108 Microsoft—Polycom Meeting Scenarios The Join the Conference dialog box opens in the Conversation window. 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.
Page 109 The Join Conference dialog box is displayed in the remaining participants Office Communicator client. 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 3-55...
Page 110: Scheduling A Meeting-Office Communicator-Outlook Integration
Microsoft—Polycom Meeting Scenarios Scheduling a Meeting—Office Communicator–Outlook Integration Office Communicator users can schedule conferences using Outlook from their Office Communicator client. To schedule a conference: In Office Communicator, on the Actions menu, click Schedule a Conference. 3-56...
Page 111 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. Polycom-Microsoft Deployment Guide 3-57...
Page 112: Starting A Data Sharing Session
Microsoft—Polycom Meeting Scenarios 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: In the Conversation window, click the Data Sharing button.
Page 113 Polycom-Microsoft Deployment Guide Once the invitation is accepted by the meeting participants, the Sharing Controls at the bottom of the Conversation window are enabled. Click the Application Sharing button to start an application sharing session. 3-59...
Page 114 Microsoft—Polycom Meeting Scenarios The Sharing dialog box opens. Click the application you want to share, and click the Share button. The Application opens on the computers of all meeting participants. 3-60...
Page 115: Conference Control Via Office Communicator Sip-Cx Protocol
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. Polycom-Microsoft Deployment Guide 3-61...
Page 116 Microsoft—Polycom Meeting Scenarios 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-62...
Page 117: Ad-Hoc Conferencing And Active Directory
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 and is linked to the Entry Queue.
Page 118 Ad-hoc Conferencing and Active Directory Integration 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.
Page 119: Ad Hoc Conferencing Requirements
MCU together with the permission to create the conference and it replaces the conference data taken from the Profile. To work with the Active Directory database, the Entry Queue and IVR Services must be configured accordingly. Polycom-Microsoft Deployment Guide...
Page 120: Ad Hoc Conferencing And Validation Scenarios
Ad-hoc Conferencing and Active Directory Integration 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.
Page 121: Ad Hoc Entry Queue With Active Directory Validation
Contacts list. Dial in to the Ad-hoc enabled Entry Queue. You are prompted for the conference Numeric ID. Using Office Communicator Keypad or your endpoint remote control to send DTMF codes, enter the conference Numeric ID. Polycom-Microsoft Deployment Guide...
Page 122: Ad Hoc Entry Queue With Conference Password Validation With Active Directory
Ad-hoc Conferencing and Active Directory Integration 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.
Page 123 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. Polycom-Microsoft Deployment Guide...
Page 124 Ad-hoc Conferencing and Active Directory Integration 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: •...
Page 125: Defining The Ad Hoc Conferencing Components In The Mgc Environment
The port number used by the MCU to access the Active Directory server. The user name defined in the Active Directory for the MCU. The default user name is: POLYCOM. The password associated with the user name defined for the MCU in the Active Directory. The...
Page 126: Entry Queue Service With Access To The External Database
Ad-hoc Conferencing and Active Directory Integration Table 4-1 Flag EXTERNAL_DB_DI RECTORY Entry Queue Service with Access to the External Database Access to an external database application must be configured in the Entry Queue Service to verify the conference Numeric ID, permission to start a new conference and enable the Numeric ID Audio Messages.
Page 127: Ivr Service With Access To The External Database Application
• 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. Polycom-Microsoft Deployment Guide 4-11...
Page 128: Profiles
Ad-hoc Conferencing and Active Directory Integration Profiles Profiles are conference templates stored on the MCU, designed mainly for Ad Hoc conferences. They must be defined for all Ad Hoc conferencing scenarios. Profiles are assigned to Entry Queues designated for Ad Hoc conferencing.
Page 129: Ad Hoc-Enabled Entry Queue
Ad Hoc-enabled Entry Queue conference. Right-click the Meeting Rooms & Entry Queues icon, and then click New Entry Queue. The Entry Queue Properties dialog box opens. In the Entry Queue Properties dialog box, define the Entry Queue parameters: Polycom-Microsoft Deployment Guide 4-13...
Page 130 Entry Queue. If no number is assigned, when the Entry Queue is saved on the MCU, the MCU will automatically assign a dial-in number from the range of dial-in numbers defined in the default ISDN Network service. Otherwise, skip this step. Click OK.
Page 131: Known Limitations
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.
Page 132 Known Limitations • 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. •...
Page 133: Office Communicator Callback Model
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.
Page 134 Appendix A — The user's selection is passed in the REFER request's Refer-To 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"...
Page 135: Examples
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: bond@polycom.co.il;user=h323 - with the H323 alias=bond specified in the SIP URI user part. Office Communicator will add a "SIP:"...
Page 136: Canceling The Sip-Cx Environment Setting
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).
Page 137 In the Item=Value box, click the SIP_CONF_WATCH_CONTROL flag. The flag value appears in the Edit Value box. Enter NO and click the Set Value button. Click OK. The Sysconfig window closes. Right-click the MCU icon and then click Reset MCU. Polycom-Microsoft Deployment Guide...
Page 138 Appendix A...

Polycom ReadiConvene Deployment Manual

Overview

Microsoft-Polycom Environment Setting

Microsoft-Polycom Meeting Scenarios

Ad-Hoc Conferencing and Active Directory

Integration

Known Limitations

Appendix A

Appendix A

Quick Links

Need help?

Questions and answers

Related Manuals for Polycom ReadiConvene

Summary of Contents for Polycom ReadiConvene

Table of Contents