RELEASE NOTES Phase 1 May 2016 3725-74606-000A Polycom Concierge
Contents Introducing the Polycom Concierge Solution... 3 New Features... 3 Endpoint and Meeting Control... 3 Enhanced Participant List Control... 3 Content Collaboration... 4 Calendaring... 4 Deployment, Installation, and Configuration... 4 Products Tested with this Release... 5 Limitations and Constraints... 6 Use of Multiple Devices by a Single User... 6 Auto Network Switching on Smartphones... 6 Sleep Mode on ios Smartphones... 6 Meeting Room Chairperson... 6 Multiple Endpoints... 6 Pairing... 6 Meeting Passcode... 7 Scheduling... 7 VEQ Calls... 7 VMR Dial String... 7 VMR Owner... 7 Known Issues... 9 Get Help... 10 The Polycom Community... 10 Copyright and Trademark Information... 11 Polycom, Inc. 2
Introducing the Polycom Concierge Solution Polycom Concierge is an infrastructure that uses existing Polycom products to establish an enhanced collaboration and control experience. Deploying the Polycom Concierge solution enables individuals in the enterprise to control room endpoints and collaborate in video meetings using personal computing devices. New Features Phase 1 of the Polycom Concierge solution offers the following features: Endpoint and Meeting Control Enhanced Participant List Control Content Collaboration Calendaring Endpoint and Meeting Control Polycom RealPresence Mobile and Polycom RealPresence Desktop are client systems in a Polycom Concierge deployment. These systems are dynamically managed in Polycom RealPresence Resource Manager, support the Polycom Concierge service, and have the following endpoint and meeting control capabilities in a meeting room with a supported endpoint: Initiate a call Change or mute endpoint volume End a call Start and stop recording a meeting Enhanced Participant List Control The client systems in a Polycom Concierge deployment that are dynamically managed in RealPresence Resource Manager and support the Polycom Concierge service are able to join the same meeting context as a paired room endpoint and perform the following conference control functions given the appropriate in-meeting role and associated permissions: View participant list Change roles of other participants Mute a meeting participant Mute all meeting participants but the user Drop a meeting participant Polycom, Inc. 3
Introducing the Polycom Concierge Solution Phase 1 Content Collaboration Supported RealPresence Desktop client systems are able to share, receive, and annotate in-meeting content. Calendaring Dynamically managed client systems that support the Polycom Concierge service can view and join upcoming meetings from their personal calendar. Deployment, Installation, and Configuration Information about deploying the Polycom Concierge solution is available in the Polycom Concierge Solution Deployment Guide. For installation and configuration information about Polycom Concierge solution products, see the following product documentation at Polycom Support: Polycom RealPresence Mobile User Guide Polycom RealPresence Desktop User Guide Polycom RealPresence Web Suite User Guide Polycom RealPresence Group Series Administrator Guide Polycom RealPresence Resource Manager System Operations Guide Polycom RealPresence Distributed Media Application (DMA) Operations Guide Polycom RealPresence Access Director System Administrator Guide Polycom RealPresence Media Suite Administrator Guide Polycom RealPresence Collaboration Server Administrator Guide Release Notes for the Polycom Concierge solution products Polycom, Inc. 4
Products Tested with this Release The tables in this section identify the software versions of the products that are supported and have been tested for the current release of the Polycom Concierge solution. Note: Polycom recommends that you upgrade your Polycom devices with the latest software versions, as compatibility issues may already have been addressed by software updates. Refer to the Current Polycom Interoperability Matrix to match Polycom devices with the latest software release. Supported Client and Room Endpoint Products Tested with this Release Product Minimum Version Required Tested Version Polycom RealPresence Mobile 3.5.1 3.5.1 Polycom RealPresence Desktop 3.5.1 3.5.1 Polycom RealPresence Group Series 5.1.1 5.1.1 Server Products Products Tested with this Release Product Minimum Version Required Tested Version Polycom RealPresence Resource Manager 9.0.1 9.0.1 Polycom RealPresence Web Suite 2.1.0 2.1.0 Polycom RealPresence Distributed Media Application (DMA) 6.2 6.3.2 Polycom RealPresence Collaboration Server 8.5 8.6.3 Polycom RealPresence Access Director 4.1 4.2.2 Polycom RealPresence Media Suite 2.1.0 2.5.0 Polycom, Inc. 5
Limitations and Constraints The limitations and constraints in the following sections are associated with Phase 1 of the Polycom Concierge solution. Use of Multiple Devices by a Single User Users are not allowed to join the same meeting from more than one personal device at one time. When a user joins a meeting using RealPresence Desktop, RealPresence Mobile, or the RealPresence Web Suite browser client, any previous session using the same user credentials is terminated. Auto Network Switching on Smartphones RealPresence Mobile may disconnect from paired devices and joined meetings on devices with features enabled that cause automatic network switching. One example is an auto network switching feature that automatically switches between a local network and a corporate Wi-Fi as an individual moves to different locations. Users can prevent this limitation by disabling these features on their personal devices. Sleep Mode on ios Smartphones RealPresence Mobile may disconnect from paired devices and joined meetings when ios devices enter sleep mode. Users can prevent this limitation by ensuring their personal devices do not enter sleep mode or by re-pairing and re-joining the meeting after waking up the devices. Meeting Room Chairperson Meetings that require a chairperson or that are defined to start only when the chairperson joins are not supported. In these situations, client systems attempting to join a meeting from a meeting invitation will encounter an error. Multiple Endpoints If a meeting room contains more than one endpoint, each endpoint that users may wish to pair to should have its own Beacon ID and pairing code sign. Pairing The Polycom Concierge solution supports client systems pairing with room systems according to the following: RealPresence Mobile client systems support manual pairing and pairing using a Bluetooth beacon. RealPresence Desktop supports only manual pairing. Polycom, Inc. 6
Introducing the Polycom Concierge Solution Phase 1 Polycom recommends that you assign only one endpoint and user account to a meeting room. A pairing code is assigned to one endpoint that is provisioned by RealPresence Resource Manager, and remains assigned as long as the system is active. If you, for example, delete and then later re-add an endpoint in RealPresence Resource Manager or shutdown an endpoint to replace it with another system and use the same IP address and user account, a new pairing code is assigned to the active endpoint. In these cases, you must generate a new QR code, reconfigure your Bluetooth beacon, or both depending on your setup. Note: The pairing feature supported for the Polycom Concierge solution is different from the SmartPairing function that is available in RealPresence Desktop and RealPresence Mobile system software prior to Phase 1 of the Polycom Concierge solution. Meeting Passcode When using Polycom Concierge to join a meeting that has a chairperson passcode defined but no conference passcode, the client system and the room endpoint will not have an opportunity to enter the chairperson passcode and will generally join the meeting as a regular participant. If desired, the endpoint remote can use used to manually enter the chairperson passcode for the room endpoint; however, that will not affect the meeting role of the client system s session. Scheduling For the best Polycom Concierge experience, scheduling a meeting that requires a passcode through RealPresence Resource Manager is not recommended. For Phase 1 of the solution, users must manually provide passcodes for such meetings. VEQ Calls Using Polycom Concierge to join conferences that use a virtual entry queue (VEQ) is not supported in Phase 1 of the Polycom Concierge solution. For more information about VEQ, see the Collaboration Server Administrator Guide. VMR Dial String To ensure a consistent experience in environments where H.323 and SIP dialing are both supported, the number plan used to dial VMR-based meetings must be the same for SIP and H.323 calls. VMR Owner As a best practice, meeting VMRs should be assigned to specific users and each user should schedule meetings on their own VMR. These practices ensure the user who scheduled the meeting will automatically be assigned the chairperson role and receive appropriate privileges in the meeting. Using Polycom Concierge to join meeting VMRs that are not assigned to a specific user is not recommended because no user is automatically assigned the chairperson role. Polycom, Inc. 7
Introducing the Polycom Concierge Solution Phase 1 Scheduling a meeting by someone other than the VMR owner is not recommended. For Phase 1 of the Polycom Concierge solution, the VMR owner is automatically set as the chairperson Polycom, Inc. 8
Known Issues This section provides a summary of known issues that you may encounter when deploying and using Phase 1 of the Polycom Concierge solution. Refer to the Polycom product release notes for more information about the known issues related to individual products. Category Issue No. Description Workaround Calling CAXIS-11969 When using the RealPresence Mobile pairing application for the first time, it may take several seconds for the application to complete the sign in process and be ready to detect and pair with room systems. Calling DMA-15965 When a client system that is enabled to use the Polycom Concierge service pairs with an endpoint that is not enabled to use the Polycom Concierge service and is in a call, and the client system tries to join the call, sometimes the client system is unable to join the call. Calling GS-28556 A client system that is enabled to use the Polycom Concierge service may be unable to join a call with a RealPresence Group Series system, when the call is dialed using an unsupported dial string, such as DMAIPAddress##VMRNumber Pairing SWEP-9055 RealPresence Mobile may not automatically unpair from a room system when a device leaves the room and a beacon is no longer detected. Pairing SWEP-9275 RealPresence Desktop intermittently is unable to pair with a RealPresence Group Series system. Try to join the call again. Enter a VMR number to join the conference with the RealPresence Group Series system. Select the UnPairing button in RealPresence Mobile to manually unpair from the room. Try to pair with the RealPresence Group Series system again. Polycom, Inc. 9
Get Help For more information about installing, configuring, and administering Polycom products, refer to Documents and Downloads at Polycom Support. The Polycom Community The Polycom Community gives you access to the latest developer and support information. Participate in discussion forums to share ideas and solve problems with your colleagues. To register with the Polycom Community, create a Polycom online account. When logged in, you can access Polycom support personnel and participate in developer and support forums to find the latest information on hardware, software, and partner solutions topics. Polycom, Inc. 10
Copyright and Trademark Information Copyright 2016, Polycom, Inc. All rights reserved. No part of this document may be reproduced, translated into another language or format, or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. 6001 America Center Drive San Jose, CA 95002 USA Polycom, the Polycom logo and the names and marks associated with Polycom products are trademarks and/or service marks of Polycom, Inc. and are registered and/or common law marks in the United States and various other countries. All other trademarks are property of their respective owners. No portion hereof may be reproduced or transmitted in any form or by any means, for any purpose other than the recipient's personal use, without the express written permission of Polycom. Java is a registered trademark of Oracle America, Inc., and/or its affiliates. End User License Agreement By installing, copying, or otherwise using this product, you acknowledge that you have read, understand and agree to be bound by the terms and conditions of the End User License Agreement for this product. Patent Information The accompanying product may be protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc. Open Source Software Used in this Product This product may contain open source software. You may receive the open source software from Polycom up to three (3) years after the distribution date of the applicable product or software at a charge not greater than the cost to Polycom of shipping or distributing the software to you. To receive software information, as well as the open source software code used in this product, contact Polycom by email at OpenSourceVideo@polycom.com. Disclaimer While Polycom uses reasonable efforts to include accurate and up-to-date information in this document, Polycom makes no warranties or representations as to its accuracy. Polycom assumes no liability or responsibility for any typographical or other errors or omissions in the content of this document. Limitation of Liability Polycom and/or its respective suppliers make no representations about the suitability of the information contained in this document for any purpose. Information is provided as is without warranty of any kind and is subject to change without notice. The entire risk arising out of its use remains with the recipient. In no event shall Polycom and/or its respective suppliers be liable for any direct, consequential, incidental, special, punitive or other damages whatsoever (including without limitation, damages for loss of business profits, business interruption, or loss of business information), even if Polycom has been advised of the possibility of such damages. Customer Feedback We are striving to improve our documentation quality and we appreciate your feedback. Email your opinions and comments to DocumentationFeedback@polycom.com. Visit the Polycom Support Center for End User License Agreements, software downloads, product documents, product licenses, troubleshooting tips, service requests, and more. Polycom, Inc. 11