poly RealPresence Desktop for Windows Instruction Manual

poly RealPresence Desktop for Windows Instruction Manual

What’s New in This Release
Poly RealPresence Desktop 3.11.10 is a maintenance release that includes bug fixes only

Security Updates
See the Security Center for information about known and resolved security vulnerabilities.

Hardware and Software Requirements

The following hardware requirements were determined based on test scenarios. Your system’s actual performance may vary based on software or hardware configurations.

Enterprise: 32-bit and 64-bit Windows 7: 32-bit and 64-bit
Processor|

• Real Presence Desktop system’s capabilities vary depending on processor performance. The processor types and speeds listed below are intended as reference. Real Presence Desktop has equivalent capabilities on other processors with equivalent performance. Recommended CPU: Intel Core i5, 2.5 GHz or higher .Basic Video Transmit (up to QVGA 30 fps sending, up to 720p 15 fps receiving)
• Single core
• Dual logical cores, lower than 2.0 GHz
• Quad logical cores, lower than 1.3 GHz
• Premium Video Transmit (up to VGA 30 fps sending, up to 720p 30 fps receiving)
• Dual logical cores, 2.0 GHz or higher
• Quad logical cores, 1.3 GHz or higher HD Transmit
• Quad logical cores, 2.0 GHz or higher, fourth generation or newer Intel CPU (up to 720p 30 fps sending, up to 1080p 30 fps receiving)
• Dual logical cores, 2.5 GHz or higher (up to 720p 15 fps sending, up to 720p 30 fps receiving)
• Quad logical cores, 1.6 GHz or higher (up to 720p 15 fps sending, up to 720p 30 fps receiving)
• Apple M1 processor

RAM| 4 GB
Video memory| Minimum: 256 MB
Hard drive space| 200 MB
Camera| Integrated or external
Audio devices| Note: Real Presence Desktop only supports directly connecting with common cameras. Real Presence Desktop doesn’t support connecting with video transcoding devices, for example, Black Magic Web Presenter.
Monitor| Standard PC97 audio devices

Install RealPresence Desktop

This section discusses how to install RealPresence Desktop in both standalone and managed mode. In standalone mode, you will need a license number and activation key code or license file to activate the product and use it beyond the 30-day trial period.

The RealPresence Desktop installation file is available in two formats:

• The .exe file is intended for easy, interactive installation by end users in standalone mode.
• The .msi file is intended for use by experienced Windows administrators to support provisioned and silent installations in managed mode.

Installation Notes
Here are some things to consider when doing a RealPresence Desktop installation:

• Installation of the RealPresence Desktop application requires that you have Microsoft .NET Framework version 4.0 installed. You can view your Microsoft .Net Framework version in C:\Windows\Microsoft.NET\Framework.
• The RealPresence Desktop user interface supports the following languages: English, International Spanish, French, German, Simplified Chinese, Korean, Japanese, Russian, Portuguese, Kazakh, Czech, and Traditional Chinese.
• When installing RealPresence Desktop for the first time, you can select one of the supported languages. The language you selects affects the language display during installation process.
• The RealPresence Desktop installation user interface doesn’t support Kazakh because the Windows InstallShield doesn’t support Kazakh.
• You can view the license number of the RealPresence Desktop by selecting Polycom RealPresence Desktop on the application’s title bar and selecting the About option

Install RealPresence Desktop in Standalone Mode

This section describes how to install RealPresence Desktop in standalone mode. The .exe file is intended for easy, interactive installation by end users.

To install RealPresence Desktop using the .exe file:

1. Download the .exe file from Poly Support.
2. Open the file and follow the instructions in the installation procedure.

To activate RealPresence Desktop license:

1. Start RealPresence Desktop application and in the Individual Account box select Enter.
2. Select Activate to activate the application with a license. Then do one of the following:
   • Select More to select a license file. The license file is a .txt file that contains the license number and activation key.
   • Specify your License Number and Activation Key Code manually. You can press the TAB key to navigate among different text fields. You can also copy your key string, select in the first text field, and then press Ctrl + V to paste it.
3. Select Activate .

Install RealPresence Desktop in Managed Mode

In managed mode, an administrator can distribute the latest version of RealPresence Desktop to all managed systems. To do this, the administrator uploads the RealPresence Desktop distribution package (.tar.gz) to the Poly Clariti Manager system. This process is described in detail in the Distribute Polycom

Applications topic in the Poly Clariti Manager Administrator Guide.

Upgrade RealPresence Desktop Through Poly Clariti Manager

This section describes how to upgrade RealPresence Desktop when an upgrade package is available on the Poly Clariti Manager.

The Poly Clariti Manager can schedule and perform limited monitoring of the RealPresence Desktop application as well as manage and provision the application. The CMA system can’tt upgrade the

RealPresence Desktop application, and the Poly Clariti Manager system can upgrade the application only from version 8.0.

For more information on upgrading managed RealPresence Desktop systems, see the Using Dynamic
Software Updates Applications topic in the Poly Clariti Manager Administrator Guide.

To check upgrade:

1. Select the RealPresence Desktop logo on the application’s title bar.
   

2. Select Check Upgrade.

Install RealPresence Desktop in Microsoft Centralized Distribution Mode

Corporate system administrators use centralized distribution for software installation or upgrades. To do this, the administrator makes use of the Centralized Distribution package (.zip).

The .msi file is intended for use by experienced Windows administrators to support managed, provisioned, and silent installations. These procedures use methods such as Group Policy Objects (GPOs). You must already be familiar with these methods to use the .msi installation file.

About the .msi file:

• When you save the .msi file to your local disk, don’t rename it.
• Silent installation requires administrator level permission.
• The name of the . msi in your command line must be consistent with the installation package

By choosing the correct installer, you can install the application in different user space:

• RPDesktopSystemInstall.msi: Installs the executable in the admin space (C:/Program Files/) and the application is available to all users.
• RPDesktop.msi: Installs the executable in the user space (C:/Users//APPDATA/) and the application is available only to this user.

To work with Poly RealPresence Web Suite, you must install the .msi to your user space (C:/Users//APPDATA/).

To install RealPresence Desktop using code commands:

• Save the .msi installation file of RealPresence Desktop to a directory:
• RPDesktopSystemInstall.msi: Saves it to a directory under C:/Program Files/.
• RPDesktop.msi: Saves it to a directory under C:/Users//APPDATA/.
• Build a desktop management or group policy object that writes the .exe installation file to the directory.
• Run the command line in Command Prompt to install RealPresence Desktop. Msiexec /qn /i /l*v log

Silent Installation of RealPresence Desktop with Options Enabled

As part of that installer, the administrator can include a command-line statement to set configuration parameters that affect the user interface.

From version 3.9, the configured parameters below are only valid for the first-time installation of RealPresence Desktop. Upgraded RealPresence Desktop uses the configurations saved from the previous release.

The format of this silent installation with options command-line statement is: msiexec /qn /i CMDLINE=”=;=;…” /l*v log

How to set default call rate to 512k when using silent installation: msiexec /qn /i CMDLINE=”DEFAULT_CALL_RATE=CALLRATE512″ /lv log How to enable shorten SDP feature when using silent installation: msiexec /qn /i CMDLINE=”SUPPORT_SIMPLE_SDP=true” /lv log How to enable single sign on feature when using silent installation: msiexec /qn /iCMDLINE=”ENTRANCE_MODE=1;ENABLE_CMA=true;CMA_SERVER_ADDRESS=pctcgk.polycom.com;C _INT EGRATED_LOGIN=true” /l*v log

The following table identifies some of the RealPresence Desktop configuration parameters that can be set as part of the silent installation:

256CALLRATE384 = 384CALLRATE512 = 512CALLRATE768 = 768CALLRATE1024 = 1024CALLRATE1920 = 1920
Enable Simple Session Description Protocol (SDP) size adjustment feature for SIP| SUPPORT_SIMPLE_SDP| TRUE or FALSE
Enable Managed mode| ENTRANCE_MODE| 0 = Stand-alone mode 1 = Managed mode
Enable provisioning server| ENABLE_CMA| TRUE or FALSE
Identify provisioning server| CMA_SERVER_ADDRESS|
Enable single sign-on| CMA_INTEGRATED_LOGIN| TRUE or FALSE

Upgrade RealPresence Desktop using Code Commands

You can upgrade RealPresence Desktop using code commands.

To upgrade RealPresence Desktop using code commands:

1. Save the msi installation file of RealPresence Desktop to a directory (for example, C:\temp) on your local system.
2. Build a desktop management or group policy object that will write the .exe installation file to a directory (for example, C:\temp) on your local system.
3. Run the command line in Command Prompt to install RealPresence Desktop.

The following is an example of using the installer from the directory where the Polycom RealPresence Desktop .msi file resides: msiexec /qn /i /l*v log

If you run the installation from a directory other than the directory where the executable file resides, include the full path in the command: msiexec /qn /i “c:\temp\” /l*v log

Uninstall RealPresence Desktop Using Code Commands

This section describes how to uninstall RealPresence Desktop application using code commands.

To uninstall RealPresence Desktop using the .msi file:

Run this command
: msiexec /qn /x

If corporate security policy blocks the MSI uninstallation command performed by a non-admin computer user, the user may fail to uninstall the RealPresence Desktop 3.9. You can use WMIC as an alternative.

To uninstall RealPresence Desktop using WMIC.exe:

Run this command: WMIC product where name=”Polycom RealPresence Desktop” call uninstall /nointeractive

Products Tested with This Release

The RealPresence Desktop is tested with other products. The following list is not a complete inventory of compatible equipment. It indicates the products that have been tested for compatibility with this release.

Poly recommends that you upgrade your Poly devices with the latest software versions, as compatibility issues may already have been addressed by software updates. See the Current Poly Interoperability Matrix to match product and software versions.

Media Application (DMA) 7000
Poly Clariti Manager
| Poly RealPresence Collaboration Server (RMX) 800, Virtual Edition
| Poly Clariti Relay
Endpoints| Poly RealPresence Group 500
| Poly RealPresence Desktop
| Poly RealPresence Mobile

Interoperability Issues

You may encounter the following issues when using RealPresence Desktop with other products or on specific operating systems.

On a 64-bit Windows 7 operating system, selecting Polycom CX5000 Panoramic Video as the video device displays a blue screen.| On 64-bit Windows 7, use another video device.
On a 32-bit Windows 7 operating system, when you share a Microsoft PowerPoint 2007 file and expand it to full screen, the content share control bar is covered by the RealPresence Desktop application.| To display the content control bar, minimize or restore the screen.

Interoperability Limitations Related to Other Poly Products

In a motion mode conference, RealPresence Desktop receives video with a large delay because the video is 60 fps.| Set a conference with sharpness mode on the MCU.
If you create a Continuous Presence (CP) only conference call on RealPresence Collaboration Server (RMX) 4000/2000 and Poly RealPresence Collaboration Server 800s 8.1 with default content settings (Content Settings set to HiResGraphics and Content Protocol set to H.264 HD), the RealPresence Desktop application can’t send or receive content if the call rate is set to 384 Kbps or below.| In this case, you need to do the following:·      Change the RealPresence Collaboration Server (RMX) Content Settings to Graphics, and Content Protocol to H.263 &H.264 Auto Selection.·      Set the call rate on RealPresence Desktop to above 384 Kbps.
RealPresence Desktop supports using only English user names and passwords to sign in to the Poly CMA server and RealPresence Resource Manager, or to register to a gatekeeper or an SIP server.| Use English user names and passwords.
If you use an MPM+ media card in a call with a RealPresence Collaboration Server (RMX) system, a blue edge displays at the bottom of the video window.| Use only an MPMx media card with the RealPresence Collaboration Server (RMX) system.
When RealPresence Desktop and m100 aren’t in the same local network, RealPresence Desktop fails to call m100.| Let m100 call RealPresence Desktop.
When you enable mutual TLS (Transport Layer Security) from RealPresence Resource Manager, RealPresence Desktop fails to upgrade from RealPresence Resource Manager.| Disable mutual TLS.
With NoiseBlock on, when a participant speaks after a long period of silence, the participant’s first syllables may not be heard.| None.
In some MCU conference templates, the virtual business card is truncated.| None.
RealPresence Desktop SIP call transfers by VVX phones may fail when the endpoints aren’t registered with a RealPresence DMA system.| Register the endpoints.

System Capabilities and Constraints
The following protocols, resolutions, algorithms, and ports are supported for RealPresence Desktop.

Protocols
The following table lists the supported protocols.

Resolutions
The following table lists the supported resolutions.

Algorithms
The following table lists the supported algorithms

KbpsG.722.1 at 16 Kbps, 24 Kbps, and 32 KbpsG.722.1 Annex C at 24 Kbps, 32 Kbps, and 48 Kbps G.719 at 32 Kbps, 48 Kbps, 64 KbpsG.729 G.728 SACAutomatic gain control Acoustic echo cancellation
Video| H.261 H.263/H.263+H.264 AVCH.264 SVCH.264 high profileContent over H.264/H.263/H.263+Video Poly Lost Packet Recovery (LPR) QoS technology
Encryption| AES-128 media encryption TLS/SRTP supported in SIP calls

Inbound and Outbound Ports
The following tables list the supported inbound and outbound ports.

About Full Duplex Echo Cancellation
Sometimes, RealPresence Desktop may not provide full duplex echo cancellation. To enable full duplex echo cancellation, your laptop needs to satisfy the following requirements:

• The audio clocks of microphone and speaker must synchronize.
• No caustic coupling exists between the microphone and speaker.
• No nonlinear process in the handling of the microphone and speaker data.

Unfortunately, many laptop microphones and speakers don’t meet the above requirements, which makes full duplex audio difficult. Additionally, USB microphones normally contain their own audio clock, making synchronization difficult.

To get the optimum audio experience, Poly recommends you to use the Poly room systems instead.

Resolved Issues
This release includes the following resolved issues.

Resolved Issues

Desktop couldn’t get the far end video.
EN-242748| Poly RealPresence Desktop always shows the meeting Call Time as 00.00.00.
EN-243130| You can’t find the version number of Poly RealPresence Desktop in your computer’s Settings > Apps > Apps & features.

Known Issues
This section identifies the known issues in this release.

IMPORTANT:
These release notes do not provide a complete listing of all known issues for the software. Issues not expected to significantly impact customers with standard voice and video conferencing environments may not be included. In addition, the information in these release notes is provided as-is at the time of release and is subject to change without notice.

None.
EN-144570| Sometimes the RealPresence Desktop vCard is empty during a conference and in the profile.| None.
EN-165936| When using RealPresence Desktop, Auto-Answer sometimes doesn’t work on incoming calls from non-RealPresence Desktop endpoints.| None.
EN-164444| Calls between RealPresence Group 500 systems running software version 6.2.2 and RealPresence Desktop 3.10 sometimes have lip sync and audio dropout issues.| None.
EN-169889| When you use a Logitech Meetup USB camera as your video input, RealPresence Desktop (version 3.10 and higher) video quality is lower than expected.| None.
EN-171131| When RealPresence Desktop is the provisioning mode, it can’t call in to Zoom conferences. The prompt shows Please enable encryption option on your room system.| None.
EN-176515| Sometimes, RealPresence Desktop can’t receive new content after a content sender stops content and sends it again.| None.
EN-176541| RealPresence Desktop user search is case-sensitive. You can find users in the address book, but they don’t display as search results. This issue applies to both local and Access Directory users.| None.
EN-207836| While logging in to RealPresence Desktop with AD user credentials, if you input a wrong password, RealPresence Desktop sends error message Invalidserver address. The error message isn’t accurate.| None.
EN-238934| If you place a call using the video protocol H.264, RealPresence Desktop shows H.264SVCHigh as the video protocol in Call Statistics.| None. This is a known display issue. For H.323 calls, video protocol isH.264 or H.264High, depending on your H.264High Profile setting.

Known Limitations
This section identifies the known limitations in this release when running in the specified environmen

the.msi file.
EN-144583| You installed RealPresence Desktop 3.9 using the.msi file.| None.
EN-143170| Your computer administrator upgraded RealPresence Desktop to 3.9 using RealPresence Resource Manager.| None.
EN-171112| RealPresence Desktop 3.10.3 intermittently fails to display content sent from RealPresence Collaboration Server in encrypted SIP calls.| None.
EN-175749| When the Outlook user interface is in Russian, RealPresence Desktop’s Outlook meeting invitation fails to include the meeting ID prefix in the Join button link.| None.
EN-177679| RealPresence Desktop can’t send DTMF out-of-band in H.323 calls. However, this feature is available in SIP calls.| None.
EN-188102| Due to resolution limitations, RealPresence Desktop may not start up on a two-monitor system if its default monitor is in portrait mode.| None.

Known Limitations for Windows 10
This section identifies the known limitations in this release when running in a Microsoft Windows 10 environment.

version of Microsoft Skype, selecting a callto: or sip: URL always launches the Skype application instead of RealPresence Desktop.| Do one of the following:

• Launch RealPresence Desktop and dial your call manually.
• Uninstall the consumer version of Microsoft Skype..

SWEP-8227| Logging in to Poly Clariti Manager from RealPresence Desktop Enterprise fails when using Cyrillic or Chinese names.| None.
SWEP-7802| When you share Microsoft Edge content, the application icon doesn’t appear on the left of the application name in the Share Application section.| None

Enterprise Scalable Video Coding (SVC) Mode
The Enterprise Scalable Video Coding (SVC) mode is an alternative to the AVC mode that has traditionally been supported. Differences between the two modes are listed in the following table

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, which remains 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 the remote video, content video, or local preview expands that video to full screen. Double-clicking or tapping again reverts the display to the composite image.

SVC mode provides the following features:

• Video sends and receives 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.

When using SIP UDP in an SVC call and there’s more than 10 percent Packet Loss, the screen layout may display incorrectly. Changing to SIP TLS or TCP is recommended.

• Supported layouts of 1×1 and 1+1 through 1+10 The maximum layout of 1+10 comprises nine remote participants plus one content sharing frame, and one local preview frame
• Support for SAC with at least two quality layers, for example, 48 Kbps and 10 Kbps
• Support for mixing up to three different audio streams from the MCU
• Support for combining up to nine different SVC video streams (call rate at 1920 Kbps) from the MCUs

SVC conference calls currently do not support the following:

• Far-end Camera Control (FECC)
• Recording with RealPresence Capture Server
• H.323 calls

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 RealPresence Collaboration Server (RMX) system will clear the frozen stream in 30 minutes..

Access Media Statistics

To access media statistics, select Statistics on the in-call toolbar during a call.

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

About AES Encryption
The following are requirements for using AES encryption in calls.

AES Encryption in H.323 Calls

To use AES encryption in H.323 calls, both you and the far end must satisfy the following requirements:

• 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 standalone mode, the AES encryption of the RealPresence Desktop application works as “When available” and isn’t guaranteed.

• 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 the far end must satisfy the following requirements:

• Enable AES encryption
• Enable TLS for SIP transport
• Support for SDES over TLS key exchange
• Support for AES 128-bit CBC mode over SRTP

When working in the managed mode, the AES encryption of the RealPresence Desktop application is configurable through its provisioning server.

When working in the standalone mode, the AES encryption of the RealPresence Desktop application works as “When available” and isn’t guaranteed.

Preparing Your Device for Mutual Transport Layer Security

You can establish secure communications using Mutual Transport Layer Security (MTLS) with provisioning servers such as Poly RealPresence DMA, CMA, or Poly Clariti 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.

Generate and Import Your Certificate

To import certificates, you must generate a Certificate Request (CSR) first by using a computer that has installed the OpenSSL tool.

To generate and import your certificate on a PC:

1. Make sure you have OpenSSL installed and configured.

2. Open the CMD console window from your PC.

3. Generate the private key client.key. For example: C:\OpenSSL-Win32\bin> openssl genrsa -out client.key 1024

4. Generate the certificate request client.csr. For example: C:\OpenSSL-Win32\bin> openssl req -new -key client.key -out client.csr 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 []:[email protected] —CSR info.

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

6. Submit the certificate request to your CA:

   • a View the content of the file client.csr using the following command: Select and copy its content (from —BEGIN CERTIFICATE REQUEST to END CERTIFICATE REQUEST—): C:\OpenSSL-Win32\bin> type client.csr
   • b Go to your CA’s web interface http://<CA’s IP address>/certsrv/, and then choose Request a certificate.
   • c Select Advanced certificate request.
   • d Select 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 in the Saved Request text field, and select.
   • f Choose Base 64 encoded and select Download certificate.
     The file is saved as certnew.cer by default in the Downloads folder.

7. Move the generated certnew.cer file to your current directory.

8. Convert the file ccertnew.cer to a .p12 file by using the OpenSSL tool. The export password should be the same as the challenge password you set in Step 4. For example: C:\OpenSSL-Win32\bin> openssl pkcs12 -export -in certnew.cer -in key client.key -out client.p12 -name testp12 Enter Export Password: Verifying – Enter Export Password:

9. Encrypt the challenge password you set in Step 4:

   • a Go to Convert String.
   • b Enter the challenge password in the text field, and select Base64 Encode!.
   • c Copy the encoded text from the following text field, and save it as a .pwd file. For example: client.pwd.

10. Open the RealPresence Desktop application data folder %appdata%\RealPresence Desktop\, and then copy the files client.p12 and client.pwd to the folder

Import the Root Certificate of Your CA

To establish MTLS connections, the client and server must also hold the root certificate of your CA.

To import the root certificate of your CA:

1. Go to your CA’s web address http://<CA’s IP address>/certsrv/, select Download a CA certificate, certificate chain, or CRL.
2. Select Base 64, and select Download CA Certificate.
3. Right-click the CA file, and select Install Certificate.
4. Follow the Certificate Import Wizard. Be sure to install it to Trusted Root Certificate Authorities.

About Section 508 Accessibility Standards
For information about how RealPresence Desktop conforms to the Section 508 and Section 255 accessibility standards, see Voluntary Product Accessibility Template Reports.

Get Help
For more information about installing, configuring, and administering Poly products or services, go to Poly Support.

Privacy Policy
Poly products and services process customer data in a manner consistent with the Poly Privacy Policy.
Please direct comments or questions to [email protected].

Copyright and Trademark Information

©2023 Poly.
Poly
345 Encinal Street
Santa Cruz, California
95060

References

• Your request has been blocked. This could be due to several reasons.
• Log in - Poly JIRA
• Log in - Poly JIRA
• Log in - Poly JIRA
• Poly | Video & Voice Collaboration Solutions | HP® Official Site
• poly.com/us/en/support
• poly.com/us/en/support/security-center

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>