Polycom?RealPresence?Desktop for Windows, Version 2.3 Release

Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Polycom is pleased to announce this release of the Polycom® RealPresence®
Desktop for Windows application.
RealPresence Desktop 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 Desktop offers features and user experiences similar to the
Polycom RealPresence Mobile application. It is easily installed and configured,
supports both standalone and managed modes, and enables sharing of the
desktop and content. In standalone mode, the application requires a license to
operate beyond the 30-day trial period.
In releases 2.0, 2.1, and 2.3, only the Windows platform is supported.
These release notes describe important information to assist you in installing
and using the RealPresence Desktop application.
Software Version History
Version
Release Date
Features
2.3
March 2013
Added support for some Windows 8 editions
Note: Windows Store is not supported.
Added Keyboard Noise Elimination for Non-speakers.
2.1
December 2012
Added Interactive Voice Response (IVR) support for SVC calls
2.0
November 2012
Initial release
Hardware and Software Requirements
These hardware and software requirements were determined based on test
scenarios. Your system’s actual performance may vary based on software or
hardware configurations.
March 2013
3725-69999-004/A
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Windows
Windows XP; 32-bit with Service Pack 3 or later
Windows 7; 32-bit and 64-bit
Windows 8 Standard, Pro, and Enterprise; 32-bit and 64bit
Software
•
Microsoft .Net Framework Version 4.0
•
Polycom CMA Management Application Version 6.2
or later
•
Polycom RealPresence Resource Manager
Version 7.1 or later
Processor
Intel Core i5, 2.5GB or more
RAM
4 GB
Video memory
Minimum: 256 MB
Hard drive space
200 MB
Camera
Integrated or external
Audio devices
Standard PC97 audio devices
Monitor
Recommended: 16:9, 1920 x 1080
Minimum: 1024x768
Installation
Installation of the RealPresence Desktop application requires that you have
installed Microsoft .Net Framework version 4.0.
You can view your Microsoft .Net Framework version in
%WINDIR%\Microsoft.NET\Framework.
For example, C:\Windows\Microsoft.NET\Framework.
The RealPresence Desktop installation file is provided in two different formats,
.exe and .msi, that you can download from support.polycom.com.
Points to note about the .msi File:
•
To avoid unexpected errors, please use the .msi version for centralized
software distribution only. Centralized distribution is used by corporate
system administrators for software installation or upgrade.
•
When you save the .msi file to your local disk, please DO NOT rename it.
•
If you are upgrading the RealPresence Desktop application from an older
version, you must include this line to your command:
REINSTALLMODE=vomus REINSTALL=ALL.
You should not include this line for the first–time installation.
2
Polycom, Inc.
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Using the .exe file
The .exe file is intended for easy, interactive installations by end users who do
not require extensive customization.
To install this product by using the .exe file:
1
Download the file.
2
Open the file.
3
Follow the instructions in the installation procedure.
Using the .msi file
The .msi file is intended for use by experienced Windows administrators to
support "pushed" and "silent" installations. These procedures use mechanisms
such as GroupPolicy Objects. You should already be familiar with these
mechanisms to use the .msi installation file.
For example:
Build a desktop management or group policy object as follows:
•
Writes the .msi installation file to a directory (for example, C:\temp) on the
user's local system.
•
Uses the Windows Installer (msiexec) to perform a command line
installation of the program.
— The following is an example of using the installer from the directory
where the Polycom RealPresence Desktop "MSI" file resides:
msiexec /qn /l* RPD_install.txt /i "RPDesktop.msi"
— When running the installation from a directory other than the directory
where the executable resides, include the full path in the command:
msiexec /qn /l* RPD_install.txt /i "c:\temp\ RPDesktop.msi"
The name of the.msi in your command line should be consistent with that from
the installation package.
Feature Overview
The Polycom RealPresence Desktop offers the following key features
compared to Polycom Telepresence m100 and Polycom CMA® Desktop
systems:
•
Polycom, Inc.
User interface designed similarly to that of the RealPresence Mobile
application
3
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
•
Support for the new SVC codec technology when used in conjunction with
the Polycom Real Presence platform
•
Enhanced Content Send capability
The following features offered by the CMA Desktop client are not available with
this release of RealPresence Desktop:
•
Support for the Apple Mac O/S
•
Support for Presence display
•
Support for IM and chat
•
Detailed QoS reporting
New Features in Version 2.3
Version 2.3 added support for Windows 8 and Non-speaker Keyboard Noise
Elimination.
If the non-speaker types on the keyboard or clicks on the mouse during a call,
his microphone is automatically muted.
Features in Previous Versions
Version 2.1
Version 2.1 added Interactive Voice Response (IVR) support for SVC calls.
With the IVR service, you hear audio prompts when you dial in to a conference.
Version 2.0
Firewall/NAT Support
RealPresence Desktop provides firewall and NAT (Network Address
Translator) traversal ability without the need to log in to a VPN. The following
features are supported:
4
•
Ability to keep Real-time Transport Protocol (RTP) NAT mapping alive
during a live streaming.
•
Support for guest user dialing.
•
Ability to support Secure Real-time Transport Protocol (SRTP) and
Transport Layer Security (TLS) for the secure transmission of media.
Polycom, Inc.
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
•
Ability to support Binary Floor Control Protocol (BFCP) over both TCP and
UDP links (UDP preferred). Control signaling can now be forwarded using
the best-effort traffic class in firewall and NAT traversal.
•
Support the following dial strings when you place calls without registering
to any server.
H.323
SIP
•
name@domain
•
<name>@<domain>
•
name@IP
•
<name>@<ipAddress:port>
•
extension@domain
•
<extension>@<domain>
•
extension@IP
•
<extension>@<ipAddress:port>
•
IP##extension
•
Ability to verify server certificates by using installed root certificates (SIP,
HTTPS, and LDAP) when establishing TLS connections.
•
Ability to interoperate with Acme Session Border Controller (SBC)
systems.
•
Support for SIP signaling FW/NAT traversal over TCP/TLS as defined in
RFC5626.
•
Ability to switch to a backup SIP server when the primary server fails.
Working with Content
Your RealPresence Desktop application enables you to view content sent by
others in the call, and share your desktop or running applications with
participants at the far end. The people video and the content you receive are
displayed in separate windows.
Far-End Camera Control Support
In a point-to-point call, if the far-end system is configured to allow control, you
can pan, tilt, and zoom the far-end PTZ camera.
Support for the Enterprise Scalable Video Coding Solution
The Enterprise Scalable Video Coding (SVC) solution is an alternative to the
AVC mode that has traditionally been supported. Differences between the two
modes are listed in the following table.
Polycom, Inc.
5
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
SVC Mode
AVC Mode
Each participant in the conference call
is received by the client as a separate
video stream.
The composite video image is
determined by the bridge based on
administrator configuration.
A Caller ID is indicated by text in the
appropriate window, on display
throughout the call.
Caller ID information is displayed
intermittently.
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.
Layout may be controlled by dialing
**, and then selecting a format.
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.
The SVC solution provides the following features in this release:
•
Video send and receive up to 720p resolution.
•
Frame rates of 7.5/15/30.
•
Support for AVC content.
•
Support for SVC auto layouts for video streams of up to nine far-end
participants.
Last active speakers, resolution, bandwidth, and number of participants
are adjusted based on network bandwidth and processor capabilities.
•
Supported layouts of 1x1 and 1+1 through 1+9.
The maximum layout of 1+9 comprises 9 remote participants plus 1
content sharing frame, and 1 local preview frame.
•
Support for SAC with at least two quality layers, for example, 48 kbps and
10 kbps.
•
Support the ability to mix up to three different audio streams from the MCU.
•
Support the ability to mix up to nine different SVC video streams (call rate
at 1920 kbps) from the MCUs.
Access to Media Statistics
To access media statistics, click the antenna icon
6
.
Polycom, Inc.
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Polycom, Inc.
Value
Description
Call Type
SIP or H.323 call type.
Call Encryption
Indicates whether your call is encrypted.
Far Site Name
Name of the far site.
Far Site System
Type of video conferencing system at the far end and
its software version.
Call Speed
Negotiated speed (bandwidth) for the call, which is
usually the combined video and audio speeds in the
call.
Video Protocol
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.
Video Format
Picture size currently in use.
Audio Protocol
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.
Audio Rate
Bandwidth specified for the audio portion of the call.
The proportion of the audio rate to the video rate
depends on the protocol used.
Video Rate
Bandwidth specified for the video portion of the call.
The proportion of the video rate to the audio rate
depends on the protocol used.
Video Rate Used
Actual bandwidth being used for the video portion of
the call. This is a real-time measurement, which
normally fluctuates.
Video Frame Rate
Rate your system uses to update the picture seen at
the far end. The system can send up to 15 frames
per second. 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.
Video Packets Loss
Percentage
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.
Video Jitter
Percentage of variation in the video transmission
rate.
7
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Value
Description
Audio Packet Lost
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.
Audio Packets Loss
Percentage
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.
Audio Jitter
Percentage of variation in the audio transmission
rate.
Content Protocol
Format used for the recording, compression, and
distribution of the content.
Content Format
Display resolution of the content.
Content Rate
Rate your system uses in content transmission.
Content Rate Used
Actual bandwidth being used for the content
transmission.
Content Frame Rate
Rate your system uses in content frame
transmission.
Content Packets Lost
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.
Content Packets Loss
Percentage
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.
Interoperability
Polycom CMA and RealPresence Resource Manager Systems
The RealPresence Desktop application can register to the Polycom CMA
server (version 6.2 or higher) and Polycom RealPresence Resource Manager
server (version 7.1 or higher). The CMA and RealPresence Resource Manager
systems can schedule and perform limited monitoring of the RealPresence
Desktop application, but cannot fully manage, provision, or update the
application.
8
Polycom, Inc.
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Products Tested in This Release
Polycom RealPresence Desktop systems are tested extensively with a wide
range of products. The following list is not a complete inventory of compatible
equipment. It simply indicates the products that have been tested for
compatibility with this release.
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
http://support.polycom.com/PolycomService/support/us/support/service_policies.html
to find the current Polycom Supported Products matrix.
Type
Product
Version
NAT/Firewall/Border Controller
ACME Packet Net-Net 3820
Firmware SCX6.3.0 F-2 GA
Polycom VBP 5300-ST
11.2.13
Polycom RealPresence Access Director
2.0.3
Polycom Distributed Media
5.1.0, 5.2.0
Gatekeeper, Gateways,
External MCU, Bridges,
Call Managers
Polycom, Inc.
Application™ (DMA™)
Polycom Converged Management
Application™ (CMA)
6.2.2
Polycom® RealPresence® Resource
Manager
7.1
Polycom RMX® 4000/2000
7.8
Polycom RMX 1000 with Hardware
Version C
2.4.2
Polycom RSS™ 4000
8.0, 8.5
Broadsoft SIP r17 Server
SP2
DeltaPath
2.9.2
9
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Type
Product
Version
Endpoints
Polycom HDX® systems
3.1.1
Polycom RealPresence Mobile system
2.2, 2.3 (iOS)
2.2, 2.3 (Android)
Content Sharing Applications
Polycom VVX systems
4.1.4
Polycom Telepresence m100
1.0.5
Polycom CMA Desktop
5.2.4
Polycom RealPresence Desktop
2.1, 2.3
Polycom RealPresence Group Series
4.0.1
Polycom People+Content™ IP
1.2.3 (PC only)
Supported Capabilities, Protocols, Algorithms, and
Ports
Protocols
The following table lists the protocols supported in this version of the
RealPresence Desktop application.
10
Protocol
Description
DNS
Domain Name System
H.235
Security and Encryption
H.239
Token Management
H.281
Far End Camera Control (FECC)
H.323
Signaling
H.460
Firewall/NAT Traversal
LDAP, H.350
Directory Services
NTLMv1, NTLMv2
Authentication
Polycom LPR™
Lost Packet Recovery
SIP
Session Initiation Protocol
Polycom, Inc.
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Resolutions
The following table lists the resolutions supported in this version of the
RealPresence Desktop application.
Call Speed
Video Format
Resolution
64 kbps - 511 kbps
180p
320x180
512 kbps - 1023 kbps
360p
640x360
1024 kbps - 1920 kbps
720p (HD)
1280x720
Algorithms
The following table lists the algorithms supported in this version of the
RealPresence Desktop application.
Algorithm Type
Description
Audio
•
G.711μ or G.711A
•
Siren LPR
•
G.722.1 at 24 kbps and 32 kbps
•
G.722.1 Annex C at 24 kbps, 32 kbps, and 48 kbps
•
G.719 at 32 kbps, 48 kbps, 64 kbps, and 128 kbps
•
SAC
•
Automatic gain control
•
Acoustic echo cancellation
•
H.261
•
H.263/H.263+
•
H.264 AVC
•
H.264 SVC
•
Content over H.263/H.263+/H.264 AVC
•
Video LPR
Video
Encryption
AES supported in H.323 calls
TLS/SRTP supported in SIP calls
Inbound and Outbound Ports
The following table lists the inbound and outbound ports supported in this
version of the RealPresence Desktop application.
Polycom, Inc.
11
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Inbound Ports
Port
Function
1720 (TCP)
H.323 Signaling
1719 (UDP)
Registration, Admission, and Status (RAS)
3230 - 3329 (TCP)
Call Signaling
3230 - 3237 (UDP)
Media (RTP/RTCP)
5060
SIP
3238 (UDP and TCP)
BFCP
Outbound Ports
Port
Function
443 (TCP)
Provisioning, Monitoring, Help Files, HTTPS
389 (TCP)
LDAP
5060
SIP
5061 (TCP)
SIP TLS signaling
1720 (TCP)
H.323 Signaling
1719 (UDP)
Registration, Admission, and Status (RAS)
3230 - 3329 (TCP)
Call Signaling
3230 - 3237 (UDP)
Media (RTP/RTCP)
3238 (UDP and TCP)
BFCP
Comparison: Polycom RealPresence Desktop, RealPresence Mobile,
CMA Desktop, and Telepresence m100 Systems
The following table provides a detailed comparison of the features offered by
the various soft client products from Polycom.
12
Polycom, Inc.
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Features
RealPresence
Desktop
RealPresence
Mobile
CMA
Desktop
Telepresence
m100
IVR support for SVC calls
✓
✓
Enterprise SVC solution
✓
✓
Far-end camera control
✓
✓ (iPad
professional
mode only
✓
✓
FW/NAT support
✓
✓
✓
✓
AVC H.323 calls (outgoing and incoming)
✓
✓
✓
✓
AVC SIP calls (outgoing and incoming)
✓
✓
✓
✓
H.239/BFCP Content receive
✓
✓
✓
✓
H.239/BFCP Content send
✓
✓ (PDF on
Android tablet
and iPad)
✓
✓
Automatic gain control
✓
✓
✓
✓
Acoustic echo cancellation
✓
✓
✓
✓
Call with audio-only devices
✓
✓
✓
✓
H.261
✓
✓
✓
H.263/H.263+ video
✓
✓ (Content
only on iPad)
✓
✓
Video LPR
✓
✓ (only on
iPad)
✓
✓
720p30 transmit
✓
✓ (only on
Tegra 2-based
Android
tablets’ rear
camera)
✓
720p30 receive
✓
✓ (only on
Tegra 2-based
Android
tablets)
✓
✓
VGA transmit/receive
✓
✓
✓
Siren LPR
✓
✓
✓
G.719 at 32 kbps, 48 kbps, 64 kbps,
128 kbps
✓
✓
✓
G.722.1 at 24 kbps and 32 kbps
✓
✓
✓
Polycom, Inc.
✓
13
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Features
G.722.1 Annex C at 24 kbps, 32 kbps,
48 kbps
RealPresence
Desktop
RealPresence
Mobile
CMA
Desktop
Telepresence
m100
✓
✓
✓
✓
✓
✓
Siren 14 at 24 kbps, 32 kbps, and 48 kbps
G.711µ or G.711A
✓
✓
✓
✓
Video mute
✓
✓
✓
✓
Audio mute
✓
✓
✓
✓
Volume control
✓
✓
✓
✓
DTMF–(inband tones)
✓
✓
✓
✓
DTMF–RFC 2833 (out of band events)
✓
✓
✓
✓
View call statistics
✓ (click
✓
(select
from
menu)
✓ (select from
menu)
Configuration/provisioning
feedback/status
✓
✓
✓
✓
✓
✓
)
Camera selection (in call)
✓ (touch
)
PIP/Local preview
✓ (local
preview only)
✓ (local
preview only)
✓
✓
H.323, and SIP
✓
✓
✓
✓
Dual monitor support
✓
✓
✓
Application level content share
✓
✓
✓
✓
✓
Region content share
Windowed mode
✓
Full Screen mode
✓
✓
✓
✓
Minimized running mode
✓
✓ (Android
only)
✓
✓
RealPresence Resource Manager
monitoring and reporting
✓
✓
✓
RealPresence Resource Manager
provisioning
✓
✓
✓
✓ (only
through App
Store and
Google Play)
✓
Software update
14
Polycom, Inc.
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Features
RealPresence
Desktop
RealPresence
Mobile
CMA
Desktop
Free mode
✓
✓
Recent Call list (call history)
✓
✓
✓
✓
Local contact list
✓
✓
✓
✓
Directory service
✓ (LDAP)
✓ (LDAP)
✓
(LDAP)
✓ (LDAP,
GAB)
✓
XMPP Presence
✓
Instant Messages
✓
✓ (iOS only)
Telepresence
m100
Localization
✓
Alerts/Notification log
✓
✓
Log retrieval tool
✓
✓
✓
AES encryption
✓
✓
✓
✓ (H.323
only)
H.460 firewall traversal
✓
✓
✓
✓
Acme SBC Interoperability
✓
✓
✓
✓
SIP outbound (RFC 5626)
✓
✓
Certificates for TLS connection
✓
✓
✓
✓
BFCP over UDP
✓
✓
BFCP over TCP
✓
✓
✓
✓
Secure RTP/RTCP (SDES)
✓
✓
Symmetric RTP
✓
✓
✓
✓
✓
✓
✓
Configurable fixed ports for RTP/RTCP
✓
Network adapter selection–Automatic
✓
✓
✓
Annex O
✓
✓
✓
✓
About AES Encryption
Following are requirements for using AES encryption in calls.
Polycom, Inc.
15
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
AES Encryption in H.323 Calls
To use AES encryption in H.232 calls, both you and your far end must satisfy
the following requirements:
1
Enable AES encryption
When working in the managed mode, the AES encryption of the
RealPresence Desktop application is configurable through its provisioning
server.
When working in the managed mode, the AES encryption of the
RealPresence Desktop application works as "When available" and is not
guaranteed.
2
Both you and your far end must support, or be compatible with the same
Key exchange and encryption method (H.235v3 w, or AES 128bit CBC).
AES Encryption in SIP Calls
To use AES encryption in SIP calls, both you and your far end must satisfy the
following requirements first:
1
Enable AES encryption
When working in the managed mode, the AES encryption of the
RealPresence Desktop application is configurable throught its provisioning
server.
When working in the managed mode, the AES encryption of the
RealPresence Desktop application works as "When available" and is not
guaranteed.
16
2
Enable TLS for SIP transport
3
Support, or be compatible with the same Key exchange (SDES over TLS)
and encryption method (AES 128bit CBC mode over SRTP).
Polycom, Inc.
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Corrected Issues in Version 2.1
Category
Issue ID
Description
Audio/Video
SWEP-2757
No media are shown or heard in the HDX system when the
RealPresence Desktop application calls H.323 B2B through a SIP
trunk to the H.323 HDX system in the other enterprise.
LDAP
SWEP-2740
When you have not taken an LDAP action for a prolonged period.
accessing LDAP can result in the message “Not connected to LDAP
server.”
User Interface
SWEP-2741
On some systems, the RealPresence Desktop application cannot
see Internet Explorer 8 when a user shares Monitor 1 with another
RealPresence Desktop user.
Known Issues
The following table lists the known issues for this release. If a workaround is
available, it is noted in the table.
Category
Issue ID
Description
Workaround
Audio
SWEP3461
Audio quality can be improved by removing
Conexant smart audio processing.
Remove smart audio
processing as follows:
1 Go to Control Panel
> Add/Remove
Programs.
2 Uninstall Conexant
Smart Audio.
3 Reboot the
computer.
Camera
SWEP2630
When the specified camera is in use by another
application, the RealPresence Desktop
application is unable to automatically select an
idle camera if one is available.
Camera
SWEP2782
On a 64-bit Windows 7 operating system,
selecting Polycom CX5000 Panoramic Video as
video device displays a blue screen.
Polycom, Inc.
17
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Category
Issue ID
Description
Contacts
SWEP2631
You cannot modify the following contact
information:
•
Last Name
•
First Name
•
Device Name
•
Device Type
Content
SWEP2735
Sharing content from a third or fourth monitor may
cause the RealPresence Desktop application to
stop operating correctly.
Content
SWEP3427
When you select to send application content, the
content will be paused if it is overlapped with
another application.
General
SWEP2742
The Qihoo 360 SafeGuard antivirus program
reports a false virus alert for the RealPresence
Desktop application.
General
SWEP3215
The RealPresence Desktop application cannot run
while either the Polycom CMA® Desktop or
Polycom Telepresence m100 application is
running.
Interoperability:
Lenovo
Thinkpad
SWEP2720
Sometimes the integrated or USB camera does
not send video.
SVC
SWEP2736
In a poor network connection, sometimes a
participant disconnects automatically from an SVC
call. This can result in a participant showing up in
two video streams–one frozen and one active.
Workaround
Close the other
application, or make the
content not overlapped.
Close the CMA Desktop
or Telepresence m100
application.
The RMX system will clear the frozen stream in 30
minutes.
SVC
SVC
18
SWEP2634
SWEP2372
Note these limitations for SVC conference calls.
•
The following are not supported:
– Encryption
– FECC
– RSS
•
Only SIP calls are supported.
•
A maximum of nine far-end video streams and
one content video is supported.
•
Use SIP TCP for SVC conferences.
When there is 10% or more packet loss and UDP
is used for an SVC call, the screen layout is
wrong.
Polycom, Inc.
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Category
Issue ID
Description
Workaround
SVC
SWEP2872
After you join an SVC conference by dialling a
DMA virtual entry queue, you receive no
participant video.
Polycom DMA systems
do not support SVC
entry queues.
Join SVC conferences
directly if the call is
hosted through a
Polycom DMA system.
SVC
SWEP2871
If you are the first one to dial in to a passwordprotected SVC conference, you hear noise for a
short while after the IVR prompt.
SVC
SWEP2870
Within the call rate range 128 - 256 kbps, the IVR
video quality of SVC conferences is much lower
than that of AVC calls at the same call rate.
User Interface
SWEP2739
Turning on the screen capture function of some
desktop dictionary applications can cause the
RealPresence Desktop interface to hang.
User Interface
SWEP2783
The display is truncated if the screen resolution is
1024 x 600. Functionality is not affected.
User
Interaction
SWEP2784
The keyboard Page Up, Page Down, and arrow
keys do not work with the Recent Calls, Call
Details, and Contacts tab pages.
Video
SWEP2781
If you start the RealPresence Desktop application
within 10 seconds after it has ended, sometimes
the interface does not display correctly because
the TCP socket was not released.
Video
SWEP3425
In a call with an RMX system that uses an MPM+
media card, a blue edge is displayed at the bottom
of the video window.
Use an MPMX media
card with the RMX
system.
Preparing 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.
Polycom, Inc.
19
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
To import certificates, you need to generate a Certificate Request (CSR) first by
using a computer that has installed the openSSL tool.
The following instructions use PC as the example.
To generate and import your certificate:
Make sure you have OpenSSL installed and well configured.
Open the CMD console window from your PC.
1
Generate the private key client.key. For example:
C:\OpenSSL-Win32\bin> openssl genrsa -out client.key 1024
2
Generate the certificate request client.csr. For example:
C:\OpenSSL-Win32\bin> 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.
Email Address []:pp@pp.com ---CSR info.
Enter the following 'extra' attributes to be sent with your certificate request
A challenge password []:1234 -----see [Note1]
An optional company name []:poly
Write down the challenge password. You will need it later in the procedure.
3
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---):
C:\OpenSSL-Win32\bin> type client.csr
20
Polycom, Inc.
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
b
Go to your CA's web interface http://<CA's IP address>/certsrv/, then
click Request a certificate.
c
Click advanced certificate request.
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, then click Submit.
f
Click Base 64 encoded and then click Download certificate.
The file is saved as certnew.cer by default in the folder Downloads.
4
Move the generated certnew.cer file to your current directory.
5
Convert the file ccertnew.cer to a .p12 file by using the openSSL tool. For
example:
C:\OpenSSL-Win32\bin> 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 2.
6
7
Encrypt the challenge password you set in Step 2:
a
Go to http://www.convertstring.com/EncodeDecode/Base64Encode.
b
Enter the challenge password in the text field, and then click Base64
Encode!.
c
Copy the encoded text from the following text field, and save it as a
.pwd file, for example, client.pwd.
Open the RPD appdata folder %appdata%\RealPresence Desktop\,
and then copy the files client.p12 and client.pwd to the folder.
To import the root certificate of your CA:
Polycom, Inc.
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.
21
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
3
Right-click the CA file, and select Install Certificate. Follow the
Certificate Import Wizard.
Be sure to install it to Trusted Root Certificate Authorities.
Notices
Open Source Licenses
Some of the third party software listed below may be licensed under an open source
license that gives you the right to request the original source code of that software. To
request such source code, send a specific request to opensourcevideo@polycom.com
that includes this product's name and version number, and the name of the software
whose source code you are requesting.
OpenSSL LICENSE
Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved. Redistribution and
use in source and binary forms, with or without modification, are permitted provided that
the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of
conditions and the following disclaimer.
22
Polycom, Inc.
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
2. Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the
following acknowledgment:
"This product includes software developed by the OpenSSL Project for use in the
OpenSSL Toolkit. (http://www.openssl.org/)"
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse
or promote products derived from this software without prior written permission. For
written permission, please contact openssl-core@openssl.org.
5. Products derived from this software may not be called "OpenSSL" nor may
"OpenSSL" appear in their names without prior written permission of the OpenSSL
Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
"This product includes software developed by the OpenSSL Project for use in the
OpenSSL Toolkit (http://www.openssl.org/)"
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL
PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young
(eay@cryptsoft.com). This product includes software written by Tim Hudson
(tjh@cryptsoft.com).
Original SSLeay License
Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes SSL. This library is
free for commercial and non-commercial use as long as the following conditions are
aheared to. The following conditions apply to all code found in this distribution, be it the
RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation
included with this distribution is covered by the same copyright terms except that the
holder is Tim Hudson (tjh@cryptsoft.com). Copyright remains Eric Young's, and as
such any Copyright notices in the code are not to be removed. If this package is used
in a product, Eric Young should be given attribution as the author of the parts of the
library used.
Polycom, Inc.
23
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
This can be in the form of a textual message at program startup or in documentation
(online or textual) provided with the package. Redistribution and use in source and
binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions
and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the
following acknowledgement: "This product includes cryptographic software written by
Eric Young (eay@cryptsoft.com) The word 'cryptographic' can be left out if the rouines
from the library being used are not cryptographic related :-).
4. If you include any Windows specific code (or a derivative thereof) from the apps
directory (application code) you must include an acknowledgement: "This product
includes software written by Tim Hudson (tjh@cryptsoft.com)"
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
The licence and distribution terms for any publically available version or derivative of
this code cannot be changed. i.e. this code cannot simply be copied and put under
another distribution licence [including the GNU Public Licence.]
ares LICENSE
Copyright 1998 by the Massachusetts Institute of Technology.
Permission to use, copy, modify, and distribute this software and its documentation for
any purpose and without fee is hereby granted, provided that the above copyright notice
appear in all copies and that both that copyright notice and this permission notice
appear in supporting documentation, and that the name of M.I.T. not be used in
advertising or publicity pertaining to distribution of the software without specific, written
prior permission.
M.I.T. makes no representations about the suitability of this software for any purpose.
It is provided "as is" without express or implied warranty.
Expat LICENSE
Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd and Clark
Cooper
24
Polycom, Inc.
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006 Expat maintainers.
Permission is hereby granted, free of charge, to any person obtaining a copy of this
software and associated documentation files (the "Software"), to deal in the Software
without restriction, including without limitation the rights to use, copy, modify, merge,
publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons
to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or
substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
JpegLib NOTICE
This product includes use of the Independent JPEG Group's JPEG software.
This software is used subject to the following:
LEGAL ISSUES
In plain English:
1. We don't promise that this software works. (But if you find any bugs, please let us
know!)
2. You can use this software for whatever you want. You don't have to pay us.
3. You may not pretend that you wrote this software. If you use it in a program, you must
acknowledge somewhere in your documentation that you've used the IJG code.
In legalese:
The authors make NO WARRANTY or representation, either express or implied, with
respect to this software, its quality, accuracy, merchantability, or fitness for a particular
purpose. This software is provided "AS IS", and you, its user, assume the entire risk as
to its quality and accuracy.
This software is copyright (C) 1991-2010, Thomas G. Lane, Guido Vollbeding.
All Rights Reserved except as specified below.
Permission is hereby granted to use, copy, modify, and distribute this software (or
portions thereof) for any purpose, without fee, subject to these conditions:
(1) If any part of the source code for this software is distributed, then this README file
must be included, with this copyright and no-warranty notice unaltered; and any
additions, deletions, or changes to the original files must be clearly indicated in
accompanying documentation.
(2) If only executable code is distributed, then the accompanying documentation must
state that "this software is based in part on the work of the Independent JPEG Group".
Polycom, Inc.
25
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
(3) Permission for use of this software is granted only if the user accepts full
responsibility for any undesirable consequences; the authors accept NO LIABILITY for
damages of any kind.
These conditions apply to any software derived from or based on the IJG code, not just
to the unmodified library. If you use our work, you ought to acknowledge us.
Permission is NOT granted for the use of any IJG author's name or company name in
advertising or publicity relating to this software or products derived from it. This
software may be referred to only as "the Independent JPEG Group's software".
We specifically permit and encourage the use of this software as the basis of
commercial products, provided that all warranty or liability claims are assumed by the
product vendor.
ansi2knr.c is included in this distribution by permission of L. Peter Deutsch, sole
proprietor of its copyright holder, Aladdin Enterprises of Menlo Park, CA. ansi2knr.c is
NOT covered by the above copyright and conditions, but instead by the usual
distribution terms of the Free Software Foundation; principally, that you must include
source code if you redistribute it. (See the file ansi2knr.c for full details.) However,
since ansi2knr.c is not needed as part of any program generated from the IJG code, this
does not limit you more than the foregoing paragraphs do.
The Unix configuration script "configure" was produced with GNU Autoconf. It is
copyright by the Free Software Foundation but is freely distributable. The same holds
for its supporting scripts (config.guess, config.sub, ltmain.sh). Another support script,
install-sh, is copyright by X Consortium but is also freely distributable.
The IJG distribution formerly included code to read and write GIF files. To avoid
entanglement with the Unisys LZW patent, GIF reading support has been removed
altogether, and the GIF writer has been simplified to produce "uncompressed GIFs".
This technique does not use the LZW algorithm; the resulting GIF files are larger than
usual, but are readable by all standard GIF decoders.
We are required to state that
"The Graphics Interchange Format(c) is the Copyright property of CompuServe
Incorporated. GIF(sm) is a Service Mark property of CompuServe Incorporated."
Libxml2 LICENSE
Except where otherwise noted in the source code (e.g. the files hash.c, list.c and the
trio files, which are covered by a similar licence but with different Copyright notices) all
the files are: Copyright (C) 1998-2003 Daniel Veillard. All Rights Reserved. Permission
is hereby granted, free of charge, to any person obtaining a copy of this software and
associated documentation files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to permit persons to
whom the Software is furnished to do so, subject to the following conditions: The above
copyright notice and this permission notice shall be included in all copies or substantial
portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE DANIEL VEILLARD BE LIABLE
FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
26
Polycom, Inc.
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
Except as contained in this notice, the name of Daniel Veillard shall not be used in
advertising or otherwise to promote the sale, use or other dealings in this Software
without prior written authorization from him.
OpenLDAP LICENSE
The OpenLDAP Public License
Version 2.8, 17 August 2003
Redistribution and use of this software and associated documentation ("Software"), with
or without modification, are permitted provided that the following conditions are met:
1. Redistributions in source form must retain copyright statements and notices,
2. Redistributions in binary form must reproduce applicable copyright statements and
notices, this list of conditions, and the following disclaimer in the documentation and/or
other materials provided with the distribution, and
3. Redistributions must contain a verbatim copy of this document.
The OpenLDAP Foundation may revise this license from time to time. Each revision is
distinguished by a version number. You may use this Software under terms of this
license revision or under the terms of any subsequent revision of the license.
THIS SOFTWARE IS PROVIDED BY THE OPENLDAP FOUNDATION AND ITS
CONTRIBUTORS ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE OPENLDAP FOUNDATION, ITS
CONTRIBUTORS, OR THE AUTHOR(S) OR OWNER(S) OF THE SOFTWARE BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,
OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
The names of the authors and copyright holders must not be used in advertising or
otherwise to promote the sale, use or other dealing in this Software without specific,
written prior permission. Title to copyright in this Software shall at all times remain with
copyright holders.
OpenLDAP is a registered trademark of the OpenLDAP Foundation.
Copyright 1999-2003 The OpenLDAP Foundation, Redwood City, California, USA. All
Rights Reserved. Permission to copy and distribute verbatim copies of this document
is granted.
CyrusSASL LICENSE
Copyright (c) 1994-2003 Carnegie Mellon University. All rights reserved.
Polycom, Inc.
27
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Redistribution and use in source and binary forms, with or without modification, are
permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of
conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution.
3. The name "Carnegie Mellon University" must not be used to endorse or promote
products derived from this software without prior written permission. For permission or
any legal details, please contact
Office of Technology Transfer
Carnegie Mellon University
5000 Forbes Avenue
Pittsburgh, PA 15213-3890
(412) 268-4387, fax: (412) 268-7395
tech-transfer@andrew.cmu.edu
4. Redistributions of any form whatsoever must retain the following acknowledgment:
"This product includes software developed by Computing Services at Carnegie Mellon
University (http://www.cmu.edu/computing/)."
CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITH REGARD
TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL CARNEGIE MELLON
UNIVERSITY BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL
DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE
USE OR PERFORMANCE OF THIS SOFTWARE.
DotNetZip LICENSE
Copyright © Dino Chiesa 2006 - 2009
Portions Copyright (c) 2006, 2007, 2008, 2009 Dino Chiesa and Microsoft Corporation.
Portions Copyright (c) 2006-2009 Microsoft Corporation. All rights reserved.
Microsoft Public License (Ms-PL)
This license governs use of the DotNetZip library and tools ("the software"). If you use
the software, you accept this license. If you do not accept the license, do not use the
software.
1. Definitions
The terms "reproduce," "reproduction," "derivative works," and "distribution" have the
same meaning here as under U.S. copyright law.
A "contribution" is the original software, or any additions or changes to the software.
A "contributor" is any person that distributes its contribution under this license.
"Licensed patents" are a contributor's patent claims that read directly on its contribution.
28
Polycom, Inc.
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
2. Grant of Rights
(A) Copyright Grant- Subject to the terms of this license, including the license conditions
and limitations in section 3, each contributor grants you a non-exclusive, worldwide,
royalty-free copyright license to reproduce its contribution, prepare derivative works of
its contribution, and distribute its contribution or any derivative works that you create.
(B) Patent Grant- Subject to the terms of this license, including the license conditions
and limitations in section 3, each contributor grants you a non-exclusive, worldwide,
royalty-free license under its licensed patents to make, have made, use, sell, offer for
sale, import, and/or otherwise dispose of its contribution in the software or derivative
works of the contribution in the software.
3. Conditions and Limitations
(A) No Trademark License - This license does not grant you rights to use any
contributor's name, logo, or trademarks.
(B) If you bring a patent claim against any contributor over patents that you claim are
infringed by the software, your patent license from such contributor to the software ends
automatically.
(C) If you distribute any portion of the software, you must retain all copyright, patent,
trademark, and attribution notices that are present in the software.
(D) If you distribute any portion of the software in source code form, you may do so only
under this license by including a complete copy of this license with your distribution. If
you distribute any portion of the software in compiled or object code form, you may only
do so under a license that complies with this license.
(E) The software is licensed "as-is." You bear the risk of using it. The contributors give
no express warranties, guarantees or conditions. You may have additional consumer
rights under your local laws which this license cannot change. To the extent permitted
under your local laws, the contributors exclude the implied warranties of
merchantability, fitness for a particular purpose and non-infringement.
LibSRTP LICENSE
Copyright (c) 2001-2006 Cisco Systems, Inc. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are
permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of
conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution.
Neither the name of the Cisco Systems, Inc. nor the names of its contributors may be
used to endorse or promote products derived from this software without specific prior
written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
Polycom, Inc.
29
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Log4cxx LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and
distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean
the copyright owner or entity authorized by the copyright owner that is granting the
License. "Legal Entity" shall mean the union of the acting entity and all other entities that
control, are controlled by, or are under common control with that entity. For the
purposes of this definition, "control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or otherwise, or (ii)
ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial
ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License. "Source" form shall mean the preferred
form for making modifications, including but not limited to software source code,
documentation source, and configuration files. "Object" form shall mean any form
resulting from mechanical transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation, and conversions to other
media types. "Work" shall mean the work of authorship, whether in Source or Object
form, made available under the License, as indicated by a copyright notice that is
included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is
based on (or derived from) the Work and for which the editorial revisions, annotations,
elaborations, or other modifications represent, as a whole, an original work of
authorship. For the purposes of this License, Derivative Works shall not include works
that remain separable from, or merely link (or bind by name) to the interfaces of, the
Work and Derivative Works thereof. "Contribution" shall mean any work of authorship,
including the original version of the Work and any modifications or additions to that
Work or Derivative Works thereof, that is intentionally submitted to Licensor for
inclusion in the Work by the copyright owner or by an individual or Legal Entity
authorized to submit on behalf of the copyright owner. For the purposes of this
definition, "submitted" means any form of electronic, verbal, or written communication
sent to the Licensor or its representatives, including but not limited to communication
on electronic mailing lists, source code control systems, and issue tracking systems that
are managed by, or on behalf of, the Licensor for the purpose of discussing and
improving the Work, but excluding communication that is conspicuously marked or
otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom
a Contribution has been received by Licensor and subsequently incorporated within the
Work.
30
Polycom, Inc.
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
2. Grant of Copyright License. Subject to the terms and conditions of this License, each
Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge,
royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the Work and such
Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License, each
Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge,
royalty-free, irrevocable (except as stated in this section) patent license to make, have
made, use, offer to sell, sell, import, and otherwise transfer the Work, where such
license applies only to those patent claims licensable by such Contributor that are
necessarily infringed by their Contribution(s) alone or by combination of their
Contribution(s) with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a cross-claim or counterclaim in a
lawsuit) alleging that the Work or a Contribution incorporated within the Work
constitutes direct or contributory patent infringement, then any patent licenses granted
to You under this License for that Work shall terminate as of the date such litigation is
filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative
Works thereof in any medium, with or without modifications, and in Source or Object
form, provided that You meet the following conditions:
a. You must give any other recipients of the Work or Derivative Works a copy of this
License; and
b. You must cause any modified files to carry prominent notices stating that You
changed the files; and
c. You must retain, in the Source form of any Derivative Works that You distribute, all
copyright, patent, trademark, and attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of the Derivative Works; and
d. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative
Works that You distribute must include a readable copy of the attribution notices
contained within such NOTICE file, excluding those notices that do not pertain to any
part of the Derivative Works, in at least one of the following places: within a NOTICE
text file distributed as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or, within a display
generated by the Derivative Works, if and wherever such third-party notices normally
appear. The contents of the NOTICE file are for informational purposes only and do not
modify the License. You may add Your own attribution notices within Derivative Works
that You distribute, alongside or as an addendum to the NOTICE text from the Work,
provided that such additional attribution notices cannot be construed as modifying the
License. You may add Your own copyright statement to Your modifications and may
provide additional or different license terms and conditions for use, reproduction, or
distribution of Your modifications, or for any such Derivative Works as a whole, provided
Your use, reproduction, and distribution of the Work otherwise complies with the
conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution
intentionally submitted for inclusion in the Work by You to the Licensor shall be under
the terms and conditions of this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify the terms of any
separate license agreement you may have executed with Licensor regarding such
Contributions.
Polycom, Inc.
31
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
6. Trademarks. This License does not grant permission to use the trade names,
trademarks, service marks, or product names of the Licensor, except as required for
reasonable and customary use in describing the origin of the Work and reproducing the
content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing,
Licensor provides the Work (and each Contributor provides its Contributions) on an "AS
IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express
or implied, including, without limitation, any warranties or conditions of TITLE, NONINFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR
PURPOSE. You are solely responsible for determining the appropriateness of using or
redistributing the Work and assume any risks associated with Your exercise of
permissions under this License.
8. Limitation of Liability. In no event and under no legal theory, whether in tort (including
negligence), contract, or otherwise, unless required by applicable law (such as
deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special, incidental, or
consequential damages of any character arising as a result of this License or out of the
use or inability to use the Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all other commercial
damages or losses), even if such Contributor has been advised of the possibility of such
damages.
9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative
Works thereof, You may choose to offer, and charge a fee for, acceptance of support,
warranty, indemnity, or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only on Your own behalf
and on Your sole responsibility, not on behalf of any other Contributor, and only if You
agree to indemnify, defend, and hold each Contributor harmless for any liability incurred
by, or claims asserted against, such Contributor by reason of your accepting any such
warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following boilerplate notice, with
the fields enclosed by brackets "[]" replaced with your own identifying information.
(Don't include the brackets!) The text should be enclosed in the appropriate comment
syntax for the file format. We also recommend that a file or class name and description
of purpose be included on the same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright 1999-2005 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this
file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the
License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
CONDITIONS OF ANY KIND, either express or implied. See the License for the specific
language governing permissions and limitations under the License.
NAudio LICENSE
Copyright (C) 2001-2011 Mark Heath
32
Polycom, Inc.
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Portions of this code Copyright (C) 2002-2004 Idael Cardoso.
Microsoft Public License (Ms-PL)
This license governs use of the accompanying software. If you use the software, you
accept this license. If you do not accept the license, do not use the software.
1. Definitions
The terms "reproduce," "reproduction," "derivative works," and "distribution" have the
same meaning here as under U.S. copyright law.
A "contribution" is the original software, or any additions or changes to the software.
A "contributor" is any person that distributes its contribution under this license.
"Licensed patents" are a contributor's patent claims that read directly on its contribution.
2. Grant of Rights
(A) Copyright Grant- Subject to the terms of this license, including the license conditions
and limitations in section 3, each contributor grants you a non-exclusive, worldwide,
royalty-free copyright license to reproduce its contribution, prepare derivative works of
its contribution, and distribute its contribution or any derivative works that you create.
(B) Patent Grant- Subject to the terms of this license, including the license conditions
and limitations in section 3, each contributor grants you a non-exclusive, worldwide,
royalty-free license under its licensed patents to make, have made, use, sell, offer for
sale, import, and/or otherwise dispose of its contribution in the software or derivative
works of the contribution in the software.
3. Conditions and Limitations
(A) No Trademark License- This license does not grant you rights to use any
contributors' name, logo, or trademarks.
(B) If you bring a patent claim against any contributor over patents that you claim are
infringed by the software, your patent license from such contributor to the software ends
automatically.
(C) If you distribute any portion of the software, you must retain all copyright, patent,
trademark, and attribution notices that are present in the software.
(D) If you distribute any portion of the software in source code form, you may do so only
under this license by including a complete copy of this license with your distribution. If
you distribute any portion of the software in compiled or object code form, you may only
do so under a license that complies with this license.
(E) The software is licensed "as-is." You bear the risk of using it. The contributors give
no express warranties, guarantees or conditions. You may have additional consumer
rights under your local laws which this license cannot change. To the extent permitted
under your local laws, the contributors exclude the implied warranties of
merchantability, fitness for a particular purpose and non-infringement.
SQLite LICENSE
Portions of this file copyright (c) Microsoft Corporation
Copyright Information
© 2013 Polycom, Inc. All rights reserved.
Polycom, Inc.
33
Release Notes
Polycom® RealPresence® Desktop for Windows®, Version 2.3
Polycom, Inc.
6001 America Center Drive
San Jose, CA 95002
USA
No part of this document may be reproduced or transmitted in any form or by any
means, electronic or mechanical, for any purpose, without the express written
permission of Polycom, Inc. Under the law, reproducing includes translating into
another language or format.
As between the parties, Polycom, Inc., retains title to and ownership of all proprietary
rights with respect to the software contained within its products. The software is
protected by United States copyright laws and international treaty provision. Therefore,
you must treat the software like any other copyrighted material (e.g., a book or sound
recording).
Every effort has been made to ensure that the information in this manual is accurate.
Polycom, Inc., is not responsible for printing or clerical errors. Information in this
document is subject to change without notice.No part of this document may be
reproduced or transmitted in any form or by any means, electronic or mechanical, for
any purpose, without the express written permission of Polycom, Inc.
Trademark Information
POLYCOM® and the names and marks associated with Polycom's 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.
All other trademarks are the property of their respective owners.
Patent Information
This software is provided 'as is' with no explicit or implied warranties in respect of its
properties, including, but not limited to, correctness and fitness for purpose.
34
Polycom, Inc.