No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


SMC2.0 Fails to Initiate a Conference, with an Error Saying That Mainstream Video Protocols Are Not Supported

Publication Date:  2019-04-12 Views:  12 Downloads:  0
Issue Description

The SMC2.0 fails to initiate a conference, with an error saying that mainstream video protocols are not supported.

Alarm Information
Handling Process

Collect required information:

When the ClouldMCU initiates a conference, the system displays a message indicating that mainstream video protocols are not supported.

The relevant license is confirmed normal. Conference initiating operations on the SMC2.0 are normal. The audio and video format protocol parameters are normal.

Device version: SMC2.0 V6R6C10SPC600, CloudMCU V6R6C10SPC300

VMware virtualization deployment is adopted.

Log in to the CloudMCU and check whether any alarm is generated:

The problem cause cannot be confirmed based on the alarm information.

It is suspected that the resources are insufficient. Ask field engineers to provide resource information screenshots of the device.

According to information about the CloudMCU system resources, there are only two audio resources and three video resources. This quantity of resources is obviously different from that provided by a standard server. [In normal conditions, there should be over 200 audio resources and about 120 video resource in the CoreCap rows].

Ask field engineers to provide the hardware configuration, which is too low: Lenovo R680 server, CPU E7-4820 V2.

According to CloudMCU server requirements, the CPU version must be V4 or later and the memory bandwidth must be higher than 2133. The following figure shows the recommended configurations.

Root Cause

The performance of the server is too low.


Replace the server with a high-performance one.