Samsung | SM-T217A | User manual | Polycom RealPresence Mobile for Android Release Notes
Add to my manuals
30 Pages
advertisement
Release Notes
3.2.1 | July 2014 |
3725-82877-015/B
Polycom
®
RealPresence
®
Mobile, for Android
®
Copyright © 2014, 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. The EULA for this product is available on the Polycom Support page for the 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.
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 [email protected]
.
Polycom Support
Visit the Polycom Support Center for End User License Agreements, software downloads, product documents, product licenses, troubleshooting tips, service requests, and more.
2
Contents
Polycom, Inc. 3
Release Notes
Polycom is pleased to announce an update release of the Polycom RealPresence Mobile application.
RealPresence Mobile is a standards-based application that enables you to meet and collaborate face-to-face with anyone from anywhere—improving teamwork, collaborative decision-making, and productivity with colleagues, customers, and business partners.
RealPresence Mobile offers features and user experiences similar to the Polycom RealPresence Desktop application. It is easily installed and configured, supports both basic and professional modes.
This document provides the latest information about the RealPresence Mobile application, release 3.2, for
Android-powered smart phones and tablet devices.
Release History
The following table shows the release history of the RealPresence Mobile application.
Release History
Version
3.2.1
Release Date
July 2014
3.2
3.1.1
3.1
June 2014
March 2014
January 2014
Features
The versions.
Roster display button is not shown in CloudAXIS 1.5 and earlier
Fixed an OpenSSL security vulnerability (CVE-2014-0224).
Support for CloudAXIS HTTPs tunneling
Support for roster display in a CloudAXIS meeting
Support for log collector
Support for Far-end Camera Control (FECC) on Android tablets in professional mode
Support for sharing pictures on Android tablets in professional mode
Support for the following new devices:
•
Samsung Galaxy Tab 3 7” SM-T217A Tablet
•
Samsung Galaxy Tab 3 8” SM-T311 Tablet
Fixed the issue SWEP-5765. See
Support for portrait mode in a call (Android only)
Support for higher quality video on Tegra-3 tablets (test feature)
Support for the following new Android devices:
•
Samsung Galaxy Tab 10.1" LTE SC-01D tablet
•
Samsung Galaxy Note II GT-N7100 phone
•
HTC One 801e phone
Polycom, Inc. 4
1.3
1.1
1.0.4
1.0.3
Release Notes
Release History
Version
3.0
2.3
2.2
2.1
2.0
1.3.1
Release Date
July 2013
March 2013
February 2013
December 2012
November 2012
August 2012
June 2012
February 2012
January 2012
December 2011
Features
Support for H.264 high-profile calls (outgoing and incoming).
Support for auto-answer incoming calls. When enabled, this feature allows users to choose to mute the audio or video of auto-answered calls.Support for the following devices:
•
Samsung Galaxy S4 GT-I9500 Phone
•
Samsung Galaxy Note 8.0 GT-N5100 Tablet
•
LG Optimus G pro LG-F240L Phone
•
Sony Xperia ZL L35h Phone
•
Sony Xperia Z SGP312 Tablet
Enabled users to hide or display local self-view.
Support for the Polycom RealPresence CloudAXIS™ solution.
Support for the following new features on non-Tegra 2 Android tablets:
•
Polycom SmartPairing™ which enables you to control and swipe calls to
Polycom HDX and Group Series devices from a tablet.
•
Content sharing
Supported only in the professional mode.
Only PDF files can be shared.
Support for the enterprise Scalable Video Coding (SVC) solution on non-Tegra
2 Android tablets and phones. IVR service in SVC calls is also supported.
Bug fix.
Support for H.460 firewall traversal in basic mode.
Access to media statistics.
Support for Samsung Galaxy Note 10.1” SHW-M480K tablet.
Support for the following devices:
•
Samsung Galaxy Tab 2 7” GT-P3110 tablet
•
Samsung Galaxy Tab 2 10” GT-P5100 tablet
•
Samsung Galaxy Note GT-I9220 phone
•
Samsung Galaxy SII GT-I9100 phone
•
Samsung Galaxy SIII GT-I9300 phone
•
ASUS Transformer Pad TF300T tablet
Added Android 4.1 support for tablets that use hardware codecs.
Ability to run on Android phone.
Support for firewall/NAT.
XOOM and Galaxy: Enhanced user interface experience.
DROID XYBOARD: Added automatic provisioning support.
XOOM and Galaxy: Added support for Android 4.0.
XOOM and Galaxy: Enabled users to disable H.323 calls. User interface enhancements. Added support for server provisioning, AES for H.323 calls, and H.460 firewall traversal.
Polycom, Inc. 5
Release Notes
Release History
Version
1.0.2.1
1.0.2
1.0
Release Date
November 2011
October 2011
October 2011
Features
DROID XYBOARD: Software release specially for DROID XYBOARD.
XOOM and Galaxy: Fixed some known issues.
XOOM and Galaxy: Initial release.
Polycom, Inc. 6
Release Notes
Hardware and Software Requirements
The following hardware and software requirements were determined based on test scenarios. Your system’s actual performance may vary based on software or hardware configurations.
Hardware and Software Requirements
Manufacturer
ASUS
HTC
LG
Motorola
Samsung
SONY
Model
Transformer Pad TF300T tablet
One X phone
One 801e
Optimus G pro LG-F240L
Phone
DROID XYBOARD tablet
Galaxy Tab 8.9” SHV-E140S tablet
Galaxy Tab 2 7” GT-P3110 tablet
Galaxy Tab 2 10” GT-P5100 tablet
Galaxy Tab 10.1" LTE
SC-01D tablet
Galaxy SII GT-I9100 phone
Galaxy SIII GT-I9300 phone
Galaxy Note 10.1”
SHW-M480K tablet
Galaxy S4 GT-I9500 Phone
Galaxy Note 8.0 GT-N5100 tablet
Galaxy Note II GT-N7100 phone
Galaxy Tab 3 7” SM-T217A
Tablet
Galaxy Tab 3 8” SM-T311
Tablet
Xperia ZL L35h Phone
Xperia Z SGP312 Tablet
Android
Version
4.2.1
4.2.2
4.4.2
4.1.2
4.0.4
4.0.4
4.1.1
4.1.2
4.0.4
4.1.2
4.1.2
4.1.2
4.4.2
4.1.2
4.3
4.2.2
4.2.2
4.2.2
4.3
Network
Requirements
•
Wireless Local
Area Network
(WLAN), 802.11 a/b/g/n
•
3G or 4G network
Optional Peripheral
Devices
•
3.5 mm headset
•
Stereo Bluetooth headset
Polycom, Inc. 7
Release Notes
To view your Android system version:
» From your device, touch Settings > About device > Android Version.
Interoperability
This section explains the Interoperability of RealPresence Mobile and other applications.
Polycom CMA ® System and RealPresence Resource Manager System
The RealPresence Mobile application can register to the Polycom CMA Server and Polycom RealPresence
Resource Manager server. Some management features have limitations relative to other Polycom endpoints. For example, software updates of RealPresence Mobile are not supported and the QOS monitoring is limited.
Products Tested in This Release
Polycom RealPresence Mobile systems are tested extensively with a wide range of products. The following table does not provide a complete inventory of compatible equipment, but indicates the products that have been tested for compatibility with this release.
Note: Upgrade Polycom Products
You are encouraged to upgrade all your Polycom systems with the latest software before contacting
Polycom support to ensure that the issue has not already been addressed by vendor software updates. Go to
Polycom support to find the current Polycom Supported Products matrix.
Products Tested in This Release
Type
NAT/Firewall/Border
Controller
Product
ACME Packet Net-Net 3820
Polycom VBP® 5300-ST
Polycom VBP-E
Polycom RealPresence® Access Director™
Version
Firmware SCX6.3.0 MR-5 Patch 2
11.2.17
11.2.17
4.0, 3.1
Polycom, Inc. 8
Release Notes
Products Tested in This Release
Type
Gatekeeper, Gateways,
External MCU,
Bridges, Call Managers
Endpoints
Product
Polycom Distributed Media Application™
(DMA®) 7000
Polycom Converged Management Application™
(CMA®) 4000/5000
Polycom RealPresence Resource Manager
Polycom RMX® 4000/2000
Polycom RealPresence® Collaboration Server
1800
Polycom RMX® 1000C
Polycom RSS™ 4000
Polycom RealPresence Capture Server
Broadsoft SIP r19 Server
Polycom HDX® Series
Polycom RealPresence Mobile
Polycom VVX®
Polycom CMA® Desktop
Polycom Telepresence m100
Polycom RealPresence Desktop
Polycom RealPresence Group Series
Version
6.1.0, 6.0.4
6.2.5
8.2, 8.1
8.4, 8.3
8.4, 8.3
2.5.1
8.5.1
1.6
r19
3.1.3, 3.1.2
3.2, 3.1(iOS)
3.2, 3.1(Android)
5.0.1
5.2.5
1.0.6
3.2, 3.1(Windows)
3.2, 3.1(Mac)
4.1.3, 4.1.1
Polycom, Inc. 9
Release Notes
Install and Uninstall RealPresence Mobile
This section explains how to install and uninstall RealPresence Mobile.
To install RealPresence Mobile:
1 From the Google Play application, search for polycom or video conferencing to find the
RealPresence Mobile application.
2 Touch Free, and touch OK to accept permission. The application downloads and installs automatically.
To uninstall the RealPresence Mobile application:
1 From your device’s application list, touch Settings > Applications > Manage applications, and touch Video.
2 Touch Uninstall.
3 When you are prompted to confirm, touch OK. Your user data is deleted when you uninstall this application.
Polycom, Inc. 10
Release Notes
Feature Overview
The following table lists the available features. Features marked with an asterisk (*) are enabled by a provisioning server.
RealPresence Mobile Features
Category
Call functions and capability
Features
Enterprise SVC solution
IVR service in SVC calls
Placing H.323 calls
Enabling and disabling H.323 calling
Specifying H.323 gatekeepers
Specifying internal or external gatekeepers
Receiving H.264 content during H.323 calls
Receiving H.263 and H.263 + content during H.323 calls
Registering to SIP servers
Specifying SIP proxy servers
Placing SIP calls over UDP
Placing SIP calls over TCP
Receiving H.264 content during SIP calls
Receiving H.263 and H.263 + content during SIP calls
✓
✓
✓
✓
✓
✓
✓
✓
✓
Android
Phone
Basic
Mode
✓
Android
Phone
Professional
Mode
✓
✓
✓
✓
*
✓
✓
✓
Android
Tablet
Basic
Mode
✓
✓
*
✓
✓
✓ *
✓
*
✓ *
✓
*
✓
✓
✓
✓
✓
✓
✓
✓
✓ *
✓
*
✓ *
✓
*
✓
Android
Tablet
Professional
Mode
✓
✓
✓
✓
*
✓
*
✓
✓
✓
Polycom, Inc. 11
Release Notes
RealPresence Mobile Features
Category
Call functions and capability
Features
Selectable call rates between
64 kbps and 512 kbps
H.264 content sending up to
720 p (PDF only)
H.263 and H.263+ content sending up to XGA (PDF only)
•
H.264 encode at up to 320 x
180 (video)
•
H.264 decode at up to 640 x
480 (video)
H.264 decode at up to 720 p
(content)
H.264 high profile calls
(outgoing and incoming)
H.263 and H.263+ decode at up to XGA (content)
Automatic gain control
Acoustic echo cancellation
Automatic noise control
Polycom Siren Lost Packet
Recovery
WLAN, 3G and 4G network support
✓
✓
✓
✓
✓
✓
✓
Android
Phone
Basic
Mode
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
Android
Phone
Professional
Mode
✓
Android
Tablet
Basic
Mode
✓
Android
Tablet
Professional
Mode
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
Polycom, Inc. 12
Release Notes
RealPresence Mobile Features
Category
Call control
SmartPairing
Security and
Encryption
Features
Muting your audio during a call
✓
Pause your video during a call
✓
DTMF during a call
Viewing call statistics by touching
✓
✓
Switching between the front and rear cameras
Adjusting volume during a call
✓
✓
Network quality indicator during a call
✓
Portrait Mode
Far-end Camera Control
(FECC)
SmartPairing
Android
Phone
Basic
Mode
✓
Transferring calls to HDX or
RealPresence Group systems
H.460 firewall traversal
Encrypting H.323 calls
SIP digest authentication
RTP keep-alive
TLS/SRTP support
BFCP over UDP
SIP dial string
Certificate verification (Android
4.0 and later)
SBC Interoperability
SIP outbound proxy
SIP fail-over
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓ *
✓
✓
✓
Android
Phone
Professional
Mode
✓
✓
✓
✓
Android
Tablet
Basic
Mode
✓
✓
✓
✓
Android
Tablet
Professional
Mode
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
*
✓ *
✓
✓
✓
✓
✓
✓
✓
✓
Polycom, Inc. 13
Release Notes
RealPresence Mobile Features
Category
Professional features
Features
Provisioning service
Local address book
LDAP service
Android
Phone
Basic
Mode
Android
Phone
Professional
Mode
✓
✓
✓
Android
Tablet
Basic
Mode
Android
Tablet
Professional
Mode
✓
✓
✓
Polycom, Inc. 14
Release Notes
What’s New in Release 3.2.1
RealPresence Mobile 3.2.1 includes the features and functionality of previous releases and includes the following new features:
RealPresence Mobile shows the Roster button only for the CloudAXIS versions 1.6 and later.
CloudAXIS 1.5 and earlier versions do not support Roster display.
● Fixed an OpenSSL security vulnerability (CVE-2014-0224).
Note: Get latest product information from Polycom Support
To view the latest Polycom product documentation, visit the Support page of the Polycom web site at
Polycom Support .
New Features in Previous Releases
This section describes the new features in the previous releases.
Release 3.2
Release 3.2 includes the following new features:
●
Support for RealPresence CloudAXIS HTTPS Tunneling and Roster Display in a CloudAXIS Meeting
●
●
Support for Far-end Camera Control (FECC)
●
Support for Sharing Pictures
●
Support for RealPresence CloudAXIS HTTPS Tunneling and Roster Display in a
CloudAXIS Meeting
This release adds support for Polycom RealPresence CloudAXIS HTTPS tunneling, which allows you to join a CloudAXIS meeting with limited Internet access through HTTPS tunneling mechanism. If you are invited to a CloudAXIS meeting, you will receive a meeting invitation e-mail. You can attend the CloudAXIS meeting through the URI in the e-mail.
In the meeting, you can view the participant list by touching supported on CloudAXIS 1.6 or higher versions.
on the in-call tool bar. This feature is only
Support for Log Collector
You can send RealPresence Mobile logs by clicking Send the log report under Settings > General
Settings.
Support for Far-end Camera Control (FECC)
In calls that support FECC, you can adjust the far-end camera to give you a better view. This feature is only available on Android tablets in the professional mode.
Polycom, Inc. 15
Release Notes
Support for Sharing Pictures
On Android tablets, after you register to a provisioning server in the professional mode, you can share pictures in a call. The JPG, JPEG, PNG, and BMP formats are supported.
This feature is only available on Android tablets.
Add Support for New Devices
RealPresence Mobile 3.2 adds support for the following Android devices:
● Samsung Galaxy Tab 3 7” SM-T217A Tablet
● Samsung Galaxy Tab 3 8” SM-T311 Tablet
Release 3.1
Release 3.1 supports the following features:
● Support for Portrait Mode in a Call (Android only)
When you rotate your tablet 180 or 90 degrees during a call, RealPresence Mobile will adjust the video accordingly and will also send the adjusted content to far end systems.
If you enable SmartPairing, after you rotate your device 90 degrees during a call, you cannot see the swipe call button.
This feature is available when you enable auto-rotation on your device.
● Support for Higher Quality Video (Test Feature)
You can get higher quality video on Tegra-3 tablets by checking the Enable Hardware Codec checkbox under Settings > Test Features.
To use this feature,
a Go to Settings > Test Features.
b Select the Enable Hardware Codec checkbox.
c Enter the password, 456 and touch OK.
d Touch Yes to restart RealPresence Mobile.
After restart, the 768 Kbps and 1 Mbps call rates will be available under Network Settings. Choose a high call rate to get better quality video.
After this feature is enabled, SVC, SmartPairing, and content sending will be disabled.
You can see this feature only on Tegra-3 tablets. Polycom recommends you to test this feature and send us logs via the Polycom Community.
● Support for new Android devices
Samsung Galaxy Tab 10.1" LTE SC-01D tablet
Samsung Galaxy Note II GT-N7100 phone
HTC One 801e phone
Release 3.0
Release 3.0 supports the following features:
● Support for H.264 high profile calls (outgoing and incoming).
● Support for auto-answer of incoming calls. When you enable this feature, you can choose to mute the audio or video of auto-answered calls.
Polycom, Inc. 16
Release Notes
● Enables you to hide or display local self-view.
● PSupport for the following devices:
Samsung Galaxy S4 GT-I9500 Phone
Samsung Galaxy Note 8.0 GT-N5100 Tablet
LG Optimus G pro LG-F240L Phone
Sony Xperia ZL L35h Phone
Sony Xperia Z SGP312 Tablet
Polycom, Inc. 17
Release Notes
System Capabilities and Constraints
The following protocols, resolutions, algorithms, and ports are supported for RealPresence Mobile.
Capabilities
Capabilities
Call Rate
512 kbps
384 kbps
256 kbps
64 kbps
Video Capability
180p
Audio only
Protocols
The following table lists the protocols supported in this version of the RealPresence Mobile application.
Protocols
Protocol
DNS
H.235
H.239
H.323
H.460
LDAP, H.350
NTLMv2
Polycom LPR™
SIP
Description
Domain Name System
Security and Encryption
Token Management
Signaling
Firewall/NAT Traversal
Directory Services
Authentication
Lost Packet Recovery
Session Initiation Protocol
Note: H.239 and BFCP support
H.239 and BFCP are supported only when you are registered to a provisioning server.
Resolutions
The following table lists the resolutions supported in this version of the RealPresence Mobile application.
Polycom, Inc. 18
Release Notes
Resolutions and Frame Rate
Resolution and Frame Rate
Up to 320x180, 15 fps
Up to 640x480 (VGA), 30 fps
Up to 720p, 7.5 fps
Up to 720 p, 3 fps (Tablets only)
Source
Video sent from camera
Video received from far end
Content received from far end
Content showing from the tablets
Note: Video capability
Actual transmitted video resolution is determined by several factors, such as camera capability, computer performance, network conditions, the far-end system’s capabilities, and whether content is being received.
HD/720p fps is the maximum video receiving capability. The actual resolution is based on the negotiation with the far end.
Algorithms
The following table lists the algorithms supported in this version of the RealPresence Mobile application.
Algorithms
Algorithm Type
Audio
Video
Encryption
Description
G.722.1 Annex C
G.711u
G.711a
Siren LPR
Acoustic Echo Cancellation (AEC)
Automatic Gain Control (AGC)
Scalable Audio Coding (SAC)
H.264 SVC
H.264 AVC
H.264 high profile
H.263 and H.263+ (for content only)
AES-128 media encryption
TLS for SIP calls
Note: Availability of AES and TLS encryption
AES encryption is available only when you are registered to a provisioning server.
TLS encryption is available only when you are registered to a provisioning server.
Polycom, Inc. 19
Release Notes
Inbound and Outbound Ports
The following table lists the inbound and outbound ports supported in this version of the RealPresence
Mobile application.
Inbound Ports
Port
1720 (TCP)
1719 (UDP)
3230 - 3250 (TCP)
3230 - 3250 (UDP)
3238 (UDP and TCP)
5060 (UPD and TCP)
Function
H.323 Call Signaling (H.225)
H.323 Registration, Admission, and Status (RAS)
H.323 Call Signaling (H.245)
Media (RTP/RTCP)
BFCP
SIP
Outbound Ports
Port
443 (TCP)
389 (TCP)
5060 (UDP and TCP)
5061 (TCP)
1720 (TCP)
1719 (UDP)
3230 - 3250 (TCP)
3230 - 3250 (UDP)
3238 (UDP and TCP)
Function
Provisioning, Monitoring, Help Files, HTTPS
LDAP
SIP
SIP TLS signaling
H.323 Signaling (H.225)
H.323 Registration, Admission, and Status (RAS)
H.323 Signaling (H.245)
Media (RTP/RTCP)
BFCP
Polycom, Inc. 20
Release Notes
Interoperability Issues
You may encounter the following issues when using RealPresence Mobile with other products or on specific operating systems.
Interoperability Issues
Limitation
Type
Limitations
Related to the
Android
Versions and
Devices
Description
The RealPresence Mobile log file on Android 4.4 may only catch 16 KB size logs.
SmartPairing auto detection does not work on
Sony tablets.
The speaker’s volume is a little low during a call on the following Samsung tablets:
•
Tab3 7” T217A
•
Tab3 8” T311
RealPresence Mobile Android version 3.0 and later cannot launch on Tegra-2 devices (XOOM tablet and Galaxy Tab 10.1”
GT-P7510/GT-P7500 tablet).
The following two issues are due to the system limitation on tables using Acoustic Echo
Cancellation (AEC):
• On the Samsung Galaxy Tab 8.9”, Samsung
Galaxy Tab 10.1" LTE SC-01D, and ASUS
Transformer Pad TF300T tablets, you cannot adjust the speaker volume by using the hardware
Volume control.
• If a Transformer Pad TF300T tablet is close to
Polycom HDX or Group Serial 500 systems which enable Ultrasound, you can hear noise from the far end.
The far end can hear an echo if RealPresence
Mobile running on Android device is in the same conference and does not mute.
•
Sony Xperia Z SGP312 Tablet
•
Transformer Pad TF300T Tablet
•
DROID XYBOARD Tablet
•
Galaxy Tab 2 10" GT-P5100 Tablet
When you run RealPresence Mobile on HTC smart phones, the loudspeaker volume is too low to be heard during a call.
Solution
It is a limitation of the Android 4.4 OS. You can use adb logcat to catch
RealPresence Mobile logs.
Use manual detection.
Adjust the volume to the maximum on the tablets.
To enjoy the full features (RPM 2.3 release) of this application on your Tegra-2 tablets, download REALPRESENCE MOBILE -
TEGRA 2 from Google Play.
This is a system limitation of the tablet. The tablet’s system volume control is used for
RealPresence Mobile. When a tablet uses
AEC, the system volume control does not work.
This is a limitation of the tablet.The microphone and the speaker are placed very close.
Use a headset or lower the speaker’s volume.
This is a limitation of the tablet.
Use a headset.
Polycom, Inc. 21
Release Notes
Interoperability Issues
Limitation
Type
Limitations
Related to the
Android
Versions and
Devices
Description
Placing SIP calls over TCP may fail on the following tablets:
•
Transformer Pad TF300T Tablet 4.1.1 and
4.2.1
•
HTC One X 4.1.1 and 4.2.2
•
HTC One 801e phone 4.2.2 and 4.4.2
•
Samsung Tab2 7" GT-P3110 Tablet 4.0.3
•
Samsung Tab2 10" GT-P5100 Tablet 4.0.3
•
Samsung Galaxy SII GT-I9100 Phone 4.0.3
•
Samsung Galaxy Note GT-I9220 Phone 4.0.3
•
SONY Xperia ZL L35h Phone 4.1.2, 4.2.2, and 4.3
•
SONY Xperia Z SGP312 Tablet 4.1.2 and
4.2.2
Placing SIP calls over UDP (Default) and SIP over TLS on the above tablets works well.
The root cause is TCP/IP stack on Android 4.0.3 will check SIP messages. If TCP packet size is larger than 1500 bytes, it may be dropped by the system.
When using Android tablets with Acoustic Echo
Cancellers, SmartPairing fails with auto-detection.
•
On Transformer Pad TF300T tablets, auto detection does not work.
•
On Galaxy Tab 8.9” SHV-E140S, Galaxy Tab
10.1" LTE SC-01D, and Galaxy Tab 2 10”
GT-P5100 tablets, auto detection does not work during calls.
•
On SONY Xperia Z SGP312 tablet, auto detection does not work.
On the Samsung Galaxy Tab2 PT-3110 tablet and Samsung Galaxy Tab2 PT-5100, received video is delayed on long calls, or when you are sharing content.
Solution
Try one of the following:
•
Use SIP over UDP (Default) or SIP over
TLS.
•
Change the UDP or TCP listening port to a non-standard port on the SIP server.
You can manually add the room systems’ IP addresses to control the room systems on non-AEC tablets.
This is due to the low CPU capability of the tablets.
To avoid performance issues, only 1x1 layout is supported in SVC meetings. Users can see only the active speaker during SVC meetings.
Polycom, Inc. 22
Release Notes
Interoperability Issues
Limitation
Type
Limitations
Related to
Other Polycom
Products
Description
If you create a Continuous Presence (CP) only conference call on Polycom RMX 4000/2000 system and Polycom RealPresence
Collaboration Server 800s version 8.1 with default content settings (Content Settings:
HiResGraphics and Content Protocol: H.264
HD), the RealPresence Mobile application cannot send or receive content if call rate is set as 384 kbps or below.
Prior to version 4.1.0, Polycom VVX 1500 always reboots when the RealPresence Mobile application sends 320 x 180 video to a Polycom
VVX 1500 system.
RealPresence Mobile only supports using
English user name and password to sign in
Polycom CMA server and RealPresence
Resource Manager, or register to a gatekeeper or an SIP server.
If you use an MPM+ media card in a call with an
RMX system, a blue edge is displayed at the bottom of the video window.
In a motion mode conference, RealPresence
Mobile receives video with a large delay because the video is 60 fps.
RealPresence Mobile in internet may fail to call
Telepresence m100 in intranet.
When VSX
®
Visual Concert™ calls
RealPresence Mobile, only audio is connected.
Solution
•
Change the RMX Content Settings to
Graphics, and Content Protocol to
H.263 & H.264 Auto Selection.
•
Set the call rate on RPM to above 384 kbps.
This issue was fixed in VVX 1500 4.1.0, upgrade to 4.1.0 or newer version when using RealPresence Mobile with VVX 1500.
Use English user name and password.
Do not use an MPM+ media card and use an MPMX media card with the RMX system.
Set a conference with sharpness mode on
MCU.
Let Telepresence m100 call RealPresence
Mobile.
Let RealPresence Mobile call VSX Visual
Concert.
Polycom, Inc. 23
Release Notes
Known Issues
The following table lists the known issues for this release. If a workaround is available, it is noted in the table.
Known Issues
Category
Content
SVC
Issue ID Description
SWEP-6290 You might see mosaic screen when RealPresence Mobile joins a
RMX conference which enables content transcoding, and there is packet loss to the H.264 content stream.
SWEP-6350 RealPresence Mobile may stop working after joining an SVC conference with more than 100 SVC participants.
Workaround
Disable content transcoding on
RMX.
None.
Resolved Issues
The following table lists the resolved Issues in version 3.2
3.2 Resolved Issues
Category
Content
Issue ID
SWEP-4932
Other
Video
DSTC-1541
SWEP-5592
Description
(SIP Call only) When the call rate of Telepresence m100 is lower than the call rate of RealPresence Mobile and when M100 calls RealPresence Mobile,
RealPresence Mobile cannot send content to M100.
When you are trying to sign in RealPresence Mobile, RealPresence Mobile may incorrectly display a certificate warning for the intermediate CA issued certificate.
The RealPresence Mobile received video is stretched when RealPresence
Mobile is inter-operating with VSX Visual Concert.
Version 3.1.1 fixed the issue SWEP-5765.
3.1.1 Resolved Issues
Category
CloudAXIS
Issue ID
SWEP-5765
Description
Android participants are not able to join CloudAXIS meetings.
The following table lists the resolved Issues in version 3.0.
3.0 Resolved Issues in Version 3.0
Category
Video
Issue ID
SWEP-3772
Description
When you answered a telephone call, the RealPresence Mobile application remained active and transferred audio to far end. This issue has been fixed.
Polycom, Inc. 24
Release Notes
Enterprise Scalable Video Coding Solution
SVC is a scalable media relay conferencing solution based on SVC and Scalable Audio Coding (SAC) codecs. It is an alternative to the Advanced Video Coding (AVC) mode that has traditionally been supported.
Differences between the two modes are listed in the following table.
Differences Between SVC and AVC
SVC Mode
Each participant in the conference call is received by the client as a separate video stream.
A Caller ID is indicated by text in the appropriate window, on display throughout the call.
Double-clicking or tapping on a participant’s video, content video, or local preview expands that video to full screen. Double-clicking or tapping again reverts the display to the composite image.
Pinch controls enable you to zoom in and out on a participant’s video or content video.
AVC Mode
The composite video image is determined by the bridge based on administrator configuration.
Caller ID information is displayed intermittently.
Layout may typically be controlled by dialing **, and then selecting a format.
● For video send, support 180p (320 x 180)
● For video receive, support up to 360p with no bandwidth limitation; average is 270p or 180p
(480x270)
● For video send, support 7.5/15 fps
● For video receive, support 7.5/15 fps
● Support auto layouts of 1x1, 1+1 through 1+5.
The maximum layout of 1+5 comprises 4 remote participants plus 1 content-sharing frame, and 1 local preview frame.
● Support for AVC content.
● Support for Scalable Audio Coding (SAC) with at least two quality layers.
● Ability to mix up to three different audio streams from the MCU.
● Ability to combine up to four different SVC video streams (call rate at 512kbps) from the MCUs.
● Support for SVC dial-out from DMA.
Using SVC conference calls has following limitations:
● Does not support recording.
● Far-end Camera Control (FECC)
● In a SIP call, when networks using UDP experience 10 percent packet loss, the screen layout on received devices can be incorrect.
● Does not support H.323 call
● In a poor network connection, sometimes a participant disconnects automatically from an SVC call.
This can result in a frozen video stream of the participant. The RMX system will clear the frozen stream in 30 minutes.
Polycom, Inc. 25
Release Notes
Access Media Statistics
To access media statistics, click . The following table shows the meaning of each value.
Media Statistics
Value
Call Type
Call Encryption
Far Site Name
Far Site System
Call Speed
Video Protocol
Video Format
Audio Protocol
Audio Rate
Video Rate
Video Rate Used
Video Frame Rate
Video Packets Loss
Percentage
Video Jitter
Audio Packet Lost
Audio Packets Loss
Percentage
Audio Jitter
Content Protocol
Content Format
Description
SIP or H.323 call type.
Indicates whether your call is encrypted.
Name of the far site.
Type of video conferencing system at the far end and the software version.
Negotiated speed (bandwidth) for the call, which is usually the combined video and audio speeds in the call.
ITU-C video algorithm and annexes used in the current call. The video protocol used depends on the capabilities of the system at the far end as well as on your system's configuration.
Picture size currently in use.
Audio algorithm and annexes used in the current call. The audio protocol used depends on the capabilities of the system at the far end as well as on your system’s configuration.
Bandwidth specified for the audio portion of the call. The proportion of the audio rate to the video rate depends on the protocol used.
Bandwidth specified for the video portion of the call. The proportion of the video rate to the audio rate depends on the protocol used.
Actual bandwidth being used for the video portion of the call. This is a real-time measurement, which normally fluctuates.
Rate your system uses to update the picture seen at the far end. The system can send up to 15 fps. If the camera picks up large, continuous, or frequent motions, the software takes longer to assemble the data into video frames, and the frame rate drops. Changes in lighting also reduce the frame rate.
Total video packet loss as a percentage of the total number of video packets transmitted by your system and those transmitted by the far end.
Percentage of variation in the video transmission rate.
Number of audio data packets lost during the call, including transmitted packets and incoming packets. Packet loss indicates congestion or other problems on the network.
Total audio packet loss as a percentage of the total number of audio packets transmitted by your system and those transmitted by the far end.
Percentage of variation in the audio transmission rate.
Format used for the recording, compression, and distribution of the content.
Display resolution of the content.
Polycom, Inc. 26
Release Notes
Media Statistics
Value
Content Rate
Content Rate Used
Content Frame Rate
Content Packets Lost
Content Packets Loss
Percentage
Description
Rate your system uses in content transmission.
Actual bandwidth being used for the content transmission.
Rate your system uses in content frame transmission.
Number of content data packets lost during the call, including transmitted packets and incoming packets. Packet loss indicates congestion or other problems on the network.
Total audio packet loss as a percentage of the total number of content packets transmitted by your system and those transmitted by the far end.
Polycom, Inc. 27
Release Notes
Prepare Your Device for Mutual Transport Layer
Security
You can establish secure communications using Mutual Transport Layer Security (MTLS) with provisioning servers such as Polycom DMA, CMA, or RealPresence Resource Manager systems.
To establish MTLS connections, the client and server need to hold certificates issued from the same
Certificate Authority (CA) and the root certificate of this CA.
To import certificates into your Android device, you need to generate a Certificate Request (CSR) first by using a computer that has installed the OpenSSL tool.
The following example uses Mac as the example.
To generate and import your certificate:
1 Open the terminal from your Mac computer.
2 Generate the private key client.key. For example:
Mike-MacBook-Pro:~ root# openssl genrsa -out client.key 1024
3 Generate the certificate request client.csr. For example:
Mike-MacBook-Pro:~ root# openssl req -new -key client.key -out client.csr
You are about to be asked to enter information that will be incorporated into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For som-----
Country Name (2 letter code) [GB]:cn ---CSR info.
State or Province Name (full name) [Berkshire]:bj ---CSR info.
Locality Name (eg, city) [Newbury]:bj ---CSR info.
Organization Name (eg, company) [My Company Ltd]:plcm ---CSR info.
Organizational Unit Name (eg, section) []:caqa ---CSR info.
Common Name (eg, your name or your server's hostname) []:caqa ---CSR info.
E-mail Address []:[email protected] ---CSR info.
Enter the following extra attributes to be sent with your certificate request. Write down the challenge password. You will need it later in the procedure
A challenge password []:1234 -----see [Note1]
An optional company name []:poly
4 Submit the certificate request to your CA:
a View the content of the file client.csr using the following command, then select and copy its content (from ---BEGIN CERTIFICATE REQUEST to END CERTIFICATE REQUEST---):
Mike-MacBook-Pro:~ root# cat client.csr
b Go to your CA’s web interface http://<CA’s IP address>/certsrv/ , and click Request a certificate.
c Click advanced certificate request.
Polycom, Inc. 28
Release Notes
d Click Submit a certificate request by using a base-64-encoded CMC or PKCS #10 file, or
submit a renewal request by using a base-64-encoded PKCS #7 file.
e Paste the content of the file client.csr to the text filed under Saved Request text field, and click
Submit.
f
Click Base 64 encoded and click Download certificate.
The file is saved as certnew.cer by default in the folder Downloads.
5 Move the generated certnew.cer file to your current directory.
6 Convert the file ccertnew.cer to a .p12 file by using the OpenSSL tool. For example:
Mike-MacBook-Pro:~ root#openssl pkcs12 -export –in certnew.cer –inkey client.key –out client.p12 –name testp12
Enter Export Password:
Verifying - Enter Export Password:
The export password should be the same as the challenge password you set in step 3 .
7 Encrypt the challenge password you set in step 3 :
a Go to Convert Strings.
b Enter the challenge password in the text field, and click Base64 Encode!.
c Copy the encoded text from the following text field, and save it as a .pwd file, for example, client.pwd.
8 Connect your Android phone or tablet to a PC using a USB cable, then copy file client.p12 and
client.pwd to your phone or tablet’s internal storage, under the directory /polycom/certificates.
To import the root certificate of your CA into Android device:
1 Go to your CA’s web address http://<CA’s IP address>/certsrv/ , click Download a CA certificate,
certificate chain, or CRL.
2 Select Base 64, and then click Download CA Certificate.
3 Connect your Android phone or tablet to a PC using a USB cable.
4 From your Android phone or tablet, tap Settings > Security > Install from Storage.
5 Follow the screen prompt to enter, or set, screen lock password.
6 Name the certificate, or accept the suggested name.
7 Click OK to install the certificate.
The certificate is now installed on your device.
Polycom, Inc. 29
Release Notes
Note: Hold CA root certificate and system’s certificates on servers
To establish MTLS connection with servers such as Polycom DMA, CMA, or RealPresence
Resource Manager systems, the Polycom DMA, CMA, or RealPresence Resource Manager system should also hold the CA root certificate and the system’s certificates.
Polycom, Inc. 30
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement