The SMC2.0 and the MCU are connected to provide video conference services. The SMC2.0 centrally manages a diversity of NEs and endpoints, including RSE6500, telepresence, and videoconferencing endpoints.

Figure 1 SMC2.0 and MCU networking

Network description:

• The SMC2.0 supports MCU and RSE resource management, multi-MCU/RSE deployment, endpoint management, conference scheduling, and conference control.

• VP9600 series MCUs (VP9660/VP9650/VP9630) and CloudMCU support hybrid networking.

• Endpoints allow users to hold a conference by SiteCall or IVR, and control the conference on web pages, the touchscreen, or remote control.

• Users can click the link in a conference notification email to start the web conference client, join CloudMCU-based voice, video, and data conferences, and use a web conference client to control the conferences.

• All-IPv4 networking, and IPv4 and IPv6 hybrid networking are supported.

• When an MCU with universal transcoding is used, multi-point conferences support continuous presence for each port.

• Users can watch video conference live streaming and VoD on a variety of devices, including computers, tablets, smartphones, and conferencing endpoints.

When videoconferencing devices are distributed widely, the multi-SMC2.0 interconnection networking is recommended to enable unified device management.

With the continuous development of videoconferencing services, devices tend to be scattered on the whole and centralized in a small region. In this deployment mode, a service management system needs to enable centralized management in a region and flexible scheduling across regions. In the multi-SMC2.0 interconnection networking scheme, SMC2.0s are interconnected equally with flexible communications between two SMC2.0s, implementing cross-regional conference scheduling.

Figure 1 Multi-SMC2.0 interconnection networking

Network description:

• Regional autonomy

  SMC2.0s are deployed in different regions to manage devices and schedule services under their jurisdiction. Management operations in different regions are independent from each other.

• Cross-regional interconnection

  Interconnection relationships can be configured across SMC2.0s to enable conference scheduling and control. When multiple SMC2.0s are deployed, flexibly configure the relationships among SMC2.0s to form different interconnection structures, as shown in Figure 2.

Figure 2 Interconnection structures

• Well-defined rights and responsibilities

  Interconnection rights can be restricted in any of the following ways:

  • Configure the interconnection whitelist to restrict the scope of interconnected objects.

  • Interconnection requests are administrators' routine tasks, and must be confirmed and approved by the administrators.

  • Administrators can configure interconnected users and assign appropriate rights to them.

The VP9650/VP9630 provides a built-in web module to manage conferences. After being connected to the VP9650/VP9630, conferencing endpoints can directly hold conferences. When the VP9650/VP9630 is used as the media exchange platform of an enterprise's conferencing system, users do not need an additional videoconferencing service management system. This improves cost-effectiveness and usability.

Figure 1 Independent MCU networking

Network description:

• An independent MCU networking scheme consists of the VP9650/VP9630, endpoint, and IP network, supporting the intelligent access of telepresence and videoconferencing endpoints.

• The MCU provides a built-in GK which resolves MCU and endpoint addresses and provides call and bandwidth control functions. The MCU and endpoints use the GK as a bridge to convey call information between calling and called parties.

• The MCU provides a built-in web module to support device management, registration management, conference creation, and conference control.

RP series, TE series, and DP300 endpoints provide a built-in MCU, allowing users to hold multi-party conferences without the SMC2.0 or an independent MCU. This applies to video conferences in small and medium-sized enterprises.

Figure 1 Networking for endpoints with a built-in MCU

Network description (TE30 is used as an example):

• Powered by a built-in MCU, a non-encrypted conference supports the maximum access bandwidth of 4.5 Mbit/s, with 1.5 Mbit/s for each video site: 4 x 576p30 fps HD video sites + 3 x voice-only sites. For the capabilities of a built-in MCU for other endpoints, see Table 1.

• Supports the concurrent access of H.323 and SIP voice-only conference sites; SD and HD hybrid conferences; and the sending of H.239 or BFCP content streams.

• The continuous presence layout can be automatically adjusted to display new sites. The local site is not displayed by default. The site where a participant speaks is displayed on the largest pane.

• Endpoints (with a built-in MCU) support a wide range of conference control functions, including applying for and releasing the chair, enabling and disabling the chair, locking and unlocking conferences, and configuring the conference video layout.

• When voice-only sites are connected through IP phones, the SMC2.0 must be deployed to support call access, as shown in the Network containing IP phones part in Figure 1.

To connect extranet endpoints and ensure network security, the intranet must be isolated from the Internet, with a firewall deployed at the network edge. Huawei's videoconferencing solution provides different networking schemes based on different network scales and security requirements.

Co-deploying the SC, SMC2.0, and USM-EUA in the DMZ

When the user capacity is lower than 1000, the SC is co-deployed with SMC2.0 and USM-EUA in the Demilitarized Zone (DMZ), ensuring cost-effectiveness without compromising security. If an enterprise does not have a DMZ, they are co-deployed in the intranet.

Figure 1 shows the networking, signaling interaction, and audiovisual streams.

Figure 1 Co-deploying the SC, SMC2.0, and USM-EUA in the DMZ

• SIP endpoints in the intranet register with the SC through the SIP.

• H.323 endpoints in the intranet register with the SC through the H.323.

• H.323/SIP dual-protocol endpoints and MCUs in the intranet register with the SC through the H.323/SIP.

• SIP endpoints and H.323 endpoints in the extranet register with the SC.

Deploying the SBC in the DMZ

When an open port is allowed by an intranet firewall, the Session Border Controller (SBC) can be deployed in the DMZ, and the SMC2.0, SC, and MCU can be deployed in the intranet, enhancing system security. If an enterprise does not have a DMZ, they are co-deployed in the intranet.

Figure 2 shows the networking, signaling interaction, and audiovisual streams.

Figure 2 Deploying the SBC in the DMZ

• SIP endpoints in the extranet register with the SC in the intranet through the SBC. The SBC can be SE1000 based on the extranet access capacity.

• H.323 endpoints in the extranet register with the SC in the intranet after the SC opens its H.323 signaling and media ports to the extranet.