Overview

更新时间:
复制 MD 格式

This topic describes the deployment instructions, scenarios, and connection modes for the DingTalk Rooms Connector.

Prerequisites

Before you begin, purchase a DingTalk Rooms Connector license. For more information, see Purchase a license.

Deployment instructions

The following figure shows the public cloud deployment solution for the DingTalk Rooms Connector. The DingTalk Rooms Connector uses the SIP protocol to communicate with other devices. It can connect to standard SIP video conferencing hardware on the public network. It can also connect to private SIP audio and video devices that use firewall traversal equipment, such as Poly RPAD, Cisco VCS, or Huawei SBC.原理图

The DingTalk Rooms Connector also supports private deployment. In a private deployment, media servers and SIP Rooms Connectors are deployed to your corporate intranet to ensure data security.

Scenarios

The DingTalk Rooms Connector helps you work from anywhere and join meetings on the go. It connects standard SIP video conferencing hardware to software-based conferencing systems. This bridges the gap between online meetings and physical conference rooms, creating more ways to use the system. With a proper architecture, you can connect all your company's SIP video conferencing hardware to DingTalk video conferences. This helps you make the most of your existing assets.

Connection modes

SIP video conferencing hardware terminals can connect to the DingTalk Rooms Connector with or without registration. A Multipoint Control Unit (MCU) is a device based on the SIP protocol that allows multiple sites to join a single video conference. An MCU connects to the DingTalk Rooms Connector through a cascade.

For more information about how to configure SIP terminals, see Device configuration.