Configurations and settings for third-party SIP devices connecting to RingCentral Video with RingCentral
Room Connector

Last updated on January 21, 2022

Table of contents

Using Polycom devices with RingCentral Room Connector

Confirming security configurations for Polycom devices

RingCentral enforces TLS/SRTP to ensure the highest level of security for your meetings. As an admin, you might not need to do anything if your devices are already enabled for the highest level of security. However, if you are unsure, you can quickly check based on the information below.

Polycom device administration

Checking the require AES encryrption for calls setting
Checking transport protocol

Using Cisco devices with RingCentral Room Connector

Uploading standard certificates for Cisco devices

Cisco devices that want to connect using RingCentral Room Connector require some updates. Cisco devices do not “out-of-the-box” have standard certificates (e.g. those provided by GoDaddy and others).

Therefore, a customer who wants to continue to keep TLSverify settings ON during the meeting needs to upload standard certificates to their endpoints.
Please refer to the Cisco support article:
The certifications can be downloaded from the following sites:

Using Lifesize devices with RingCentral Room Connector

Lifesize devices must not be registered to Lifesize cloud and must be in SIP mode rather than H.323. Note: Lifesize is working on adding support for Lifesize devices registered to Lifesize cloud and connecting to Room Connector.

Enabling or disabling support for SIP calls

Clear Use SIP in Preferences > SIP Registrar 1 (and 2) > General when the system is not in a call.

Disabling support for H.323 calls

Clear Use H.323 in Preferences > H.323 > General when the system is not in a call.

You can refer to the Lifesize documentation.
© 1999-2022 RingCentral, Inc. Todos los derechos reservados.
We've sent you a link, please check your phone!
Please allow a full minute between phone number submissions.
There was an issue with SMS sending. Please try again. If the issue persists, please contact support.