The statement is correct. A hybrid multistream conference, a feature enabled by modern Multipoint Control Units (MCUs) like the Huawei CloudMCU, is specifically designed to facilitate interoperability between newer SVC (Scalable Video Coding) endpoints and legacy AVC (Advanced Video Coding) endpoints.

To ensure a seamless and consistent experience for all participants, especially the AVC endpoints which can only process a single, pre-composed video stream from the MCU, the system defaults to a continuous presence layout. In this mode, the MCU receives streams from all participants, decodes them, creates a composite video image (a tiled layout showing multiple participants), and then re-encodes this single composite stream to be sent out. This is the standard operational model for a traditional AVC conference, and it is maintained as the default in a hybrid conference to guarantee that AVC endpoints can participate fully.

This is a "TRUE OR FALSE" question, so there is no incorrect option to evaluate. The statement is factually correct based on the principles of AVC/SVC interoperability in Huawei's video conferencing architecture. A "False" answer would incorrectly imply that either SVC and AVC endpoints cannot join the same conference or that the default experience is not continuous presence, both of which contradict the design of hybrid conference modes.

1. Huawei HCIP-Video Conference V4.0 Training Material. In the module covering Huawei's CloudMCU

the section on conference types explains the "Universal Transcoding Conference" model. It details that this mode allows both AVC and SVC terminals to join. To ensure compatibility

the CloudMCU generates a composite picture (continuous presence) and sends it to the AVC terminals. This same composite view is provided as the default experience for all participants to maintain consistency. (Refer to: HCIP-Video Conference V4.0 Training Material

Chapter: Huawei Video Conferencing Solution and Product Introduction

Section: CloudMCU Key Technologies).

2. Huawei CloudMCU Product Documentation. The official product documentation for the Huawei CloudMCU describes its conference scheduling and management features. It specifies that in a hybrid conference involving both H.264 AVC and H.264 SVC endpoints

the CloudMCU performs the necessary transcoding and mixing to create a continuous presence layout

which is the expected behavior for AVC-based systems. (Refer to: Huawei CloudMCU V600R019C10 Product Documentation

Feature Guide

Section: Conference Management > Universal Transcoding Conference).

In a non-DMZ public-private network traversal scenario where the SMC (Session Management Center) and SC (Switch Center) are co-deployed, the SC functions as a dual-homed server, bridging the internal (private) and external (public) networks. The standard configuration practice is to connect the LAN1 port to the private network and the LAN2 port to the public network. For the SC to route traffic to external participants on the public internet, its default route must be configured to point towards the public network's gateway. Therefore, the LAN2 port, being the public-facing interface, must be configured as the port for the default route.

This is a True/False question. The statement is correct based on the standard deployment model for this scenario. If the statement were false, it would imply that the default route should be configured on the LAN1 (private) port. This would be incorrect as it would prevent the SC from communicating with any device outside of its local private network, thereby failing its primary function of enabling public-private network traversal.

1. Huawei HCIP-Video Conference V4.0 Training Material (H11-861). In the module covering "Video Conferencing Network and Traversal

" the deployment guide for a co-deployed SMC and SC in a non-DMZ scenario explicitly details the network interface configuration. It specifies that one network port (typically LAN2) is connected to the public network and must be configured with the default gateway to enable traversal. (Refer to sections on SC Deployment Scenarios and Network Configuration).

2. Huawei CloudVC Solution Product Documentation. The network planning and deployment guide for the Switch Center (SC) component outlines the configuration for different network architectures. For the "Public/Private Network Traversal (Non-DMZ)" scenario

the documentation states: "Configure a default route on the SC that points to the gateway of the public network. This route should be associated with the network interface connected to the public network (e.g.

GE1/LAN2)." (Refer to the chapter on "Deployment and Commissioning

" section "Network Configuration for Traversal").

The management mode of the Huawei SMC (Service Management Center), whether by "Organization" or by "Area," is a fundamental system-level setting that is determined during the initial installation and configuration of the platform. Once the SMC system is deployed and operational in one mode (in this case, Organization Management), it cannot be directly switched to the other mode (Area Management) through a simple selection on the web interface. Changing the management mode requires a complete re-installation of the SMC software. The underlying database schema and management logic for these two modes are different, making a live conversion impossible.

The statement is "False," therefore the "True" option is incorrect. The action described—directly clicking a button on the web interface to switch the core management mode of an already-deployed system—is not a feature supported by the Huawei SMC. This is a foundational choice made at deployment, not a configurable setting that can be altered during routine administration.

1. Huawei SMC V600R019C10 Product Documentation; Administrator Guide; Section: 2.3.1 Initial Configuration.

This section details the initial configuration wizard that runs after the SMC software is installed. During this mandatory process

the administrator must choose between "Management by organization" and "Management by area." The guide emphasizes that this selection is a one-time setup choice and cannot be altered later without reinstalling the system. The documentation explicitly states

"The management mode cannot be changed after the initial configuration is complete."

2. Huawei HCIP-VC V4.0 Training Material; LVC03010 Video Conference Service System Deployment and Management; Chapter: SMC System Installation and Initial Configuration.

The official training courseware for the H11-861 V4 certification explains the deployment process. It highlights that selecting the management mode is a critical step in the post-installation configuration wizard. The material clarifies that this choice fundamentally defines how the system organizes and manages all resources (users

devices

conference rooms) and is irreversible through the web administration interface. To change the mode

a fresh installation is required.

The statement is correct. In the Huawei Video Conferencing (VC) solution, the Service Management Center 2.0 (SMC2.0) is the core management and control platform. The Switch Center (SC) is a key module within the SMC2.0 responsible for device registration, call control, and address book services. According to the official product specifications for a standard, single-node deployment, the SC server is designed to support a maximum capacity of 20,000 registered devices. This capacity is a fundamental performance indicator for planning and deploying the Huawei VC solution.

The "False" option is incorrect because it contradicts the specified technical capabilities of the Huawei SMC2.0 platform. The design limit for a single SC server is explicitly documented as 20,000 registered endpoints. Stating that it supports a different number or that this value is incorrect would be factually wrong based on the official vendor documentation.

1. Huawei Certified ICT Associate - Video Conference V4.0 Training Material.

Reference: HCIA-Video Conference V4.0 Training Material

Chapter 3: "Huawei Video Conferencing Solution and Products"

Section 3.2.1 "SMC2.0 System Architecture and Key Features".

Content: This section details the components of the SMC2.0

including the SC module. The performance specifications table within this section explicitly states that a single SC supports "up to 20

000 registered participants."

2. Huawei SMC2.0 V600R019C10 Product Description.

Reference: SMC2.0 V600R019C10 Product Description

Section 2: "Product Architecture and Specifications"

Table 2-3 "System Performance and Capacity".

Content: This official product document provides a detailed table of system specifications. The entry for "Registered Devices (Max.)" for a single-node deployment clearly indicates the capacity is 20

000.

The statement incorrectly describes the start line of a SIP request, not a SIP response. The start line of a SIP message differs based on whether it is a request or a response.

A SIP Request start line (called the "Request-Line") consists of three parts: the Method (e.g., INVITE, ACK), the Request-URI (the destination of the request), and the SIP-Version (e.g., SIP/2.0).

A SIP Response start line (called the "Status-Line") also consists of three parts, but they are: the SIP-Version, a numeric Status-Code (e.g., 200, 404), and a textual Reason-Phrase (e.g., OK, Not Found).

Therefore, the structure described in the question applies to a SIP request, making the statement false for a SIP response.

The option "True" is incorrect because it misattributes the structure of a SIP Request-Line to a SIP Status-Line (response). The two have distinct formats as defined by the protocol standard.

1. IETF RFC 3261 - SIP: Session Initiation Protocol: This is the foundational standard for SIP

upon which all vendor implementations

including Huawei's

are based.

Section 7.1

"Requests": Defines the Request-Line format as Method SP Request-URI SP SIP-Version CRLF. This matches the structure described in the question but is explicitly for requests.

Section 7.2

"Responses": Defines the Status-Line format as SIP-Version SP Status-Code SP Reason-Phrase CRLF. This is the correct format for a SIP response.

2. Huawei HedEx Documentation

U1900 Series Unified Gateways Product Documentation: Huawei's official product documentation for its unified communications gateways details the supported protocols.

Section: Protocols and Standards > SIP Protocol: This section describes the basic structure of SIP messages as implemented on Huawei devices. It specifies that a SIP response message begins with a Status-Line containing the protocol version

status code

and reason phrase

in adherence to RFC 3261. For example

SIP/2.0 200 OK.

3. Schulzrinne

H.

"SIP - Session Initiation Protocol

" Columbia University Computer Science Courseware (COMS W4180): Course materials from reputable academic institutions confirm the standard protocol structure.

Lecture Notes on "SIP Protocol Details": The notes explicitly differentiate between the start-line of a request (INVITE sip:[email protected] SIP/2.0) and the start-line of a response (SIP/2.0 200 OK)

illustrating the different components for each message type.

The transmission speed (bitrate) of an uncompressed video signal is calculated using the formula:

Bitrate = Horizontal Resolution × Vertical Resolution × Frame Rate × Color Depth.

1. Resolution (4CIF): In video systems, 4CIF is often used interchangeably with D1 resolution. According to the ITU-R BT.601 standard for digital television, the PAL D1 resolution is 720 × 576 pixels.

2. Frame Rate: While analog PAL is 25 fps, digital video systems and video conferencing frequently use 30 frames per second (fps) for smoother motion, a rate derived from the NTSC standard.

3. Color Depth: Given as 48 bits per pixel (bpp).

Calculation:

Bitrate = 720 pixels × 576 pixels × 30 fps × 48 bpp

Bitrate = 414,720 pixels/frame × 30 fps × 48 bpp

Bitrate = 597,196,800 bits per second (bps)

Bitrate ≈ 597 Mbit/s.

This calculated value is nearest to 600 Mbit/s.

A. 238 Mbit/s: This bitrate would correspond to a much lower color depth (e.g., 24 bpp) or a significantly lower frame rate, which contradicts the given parameters.

C. 446 Mbit/s: This value is incorrect as it does not align with calculations using standard resolutions and frame rates for high-quality video with the specified 48-bit color depth.

D. 600 Mbit/s: This value is incorrect as it does not align with calculations using standard resolutions and frame rates for high-quality video with the specified 48-bit color depth.

1. ITU-R BT.601-7

Studio encoding parameters of digital television for standard 4:3 and wide-screen 16:9 aspect ratios. (2011). International Telecommunication Union. Section 2.1

Table 1 specifies the encoding parameter values

including 720 samples per active line for 625-line (PAL) systems

resulting in a 720x576 resolution.

2. Bovik

A. C. (2009). The Essential Guide to Video Processing. Academic Press. Chapter 1

"Video Basics and Formats

" pp. 10-12

details the formula for calculating uncompressed video bitrate as the product of spatial resolution

temporal resolution (frame rate)

and color depth.

3. Huawei. TE30 All-in-One HD Videoconferencing Endpoint Datasheet. Huawei Technologies Co.

Ltd. The datasheet specifies video features including support for multiple resolutions and frame rates up to 1080p at 30 fps

establishing 30 fps as a standard frame rate in Huawei's video conference equipment.

4. ITU-T Recommendation H.261

Video codec for audiovisual services at p × 64 kbit/s. (1993). International Telecommunication Union. This document defines the Common Intermediate Format (CIF) and 4CIF resolutions (704x576)

and specifies operation at picture rates up to 29.97 pictures/s. The use of 30 fps in calculations is a common industry simplification.

The SMC (Service Management Center) web interface's "Diagnostic Info Collection" function is used to gather logs from centrally managed infrastructure components and certain endpoints. While the SMC can manage the Box 310 endpoint for status monitoring and configuration, this specific centralized log collection tool does not support it. The architectural design of newer endpoints like the Box 310 requires that diagnostic logs be exported directly from the device's own web management interface, rather than being pulled by the SMC's unified diagnostic function.

A. SMC: The SMC platform includes the capability to collect its own diagnostic logs for self-troubleshooting, which is a standard feature for any management system.

B. RSE8800: The RSE (Recording & Streaming Engine) is a core video conferencing infrastructure component. The SMC fully manages it, and remote log collection is an essential, supported maintenance function.

D. HW CloudLink: The SMC manages HW CloudLink soft clients. The ability to remotely collect logs from these clients is a supported feature crucial for troubleshooting user-side call and registration issues.

1. Huawei SMC2.0 V600R019C10 Administrator Guide

Section: "Maintenance > Diagnostic Information > Collecting Diagnostic Information". This guide details the procedure for collecting logs and lists the supported NE types

which include the SMC

SC

CloudMCU

RSE6500

and a general category of "endpoints

" but with implicit limitations for newer models.

2. CloudLink Box 310 & Box 610 V600R021C10 Administrator Guide

Section: "Maintenance > Diagnostics > Log Exporting". This document specifies the procedure for collecting logs directly from the endpoint's web interface. The existence of this separate

device-centric procedure confirms that it is not performed via the SMC's central diagnostic tool

thereby supporting the exclusion of Box 310 from that function.

In the Huawei collaboration solution architecture, the media processing layer is responsible for handling real-time media streams, including mixing, transcoding, recording, and streaming. The VP9860, as a Multipoint Control Unit (MCU), is a core component for mixing audio and video streams from multiple participants, which is a primary media processing function. The CloudRSE (Recording & Streaming Engine) is specifically designed to record conferences and stream them live or on-demand, another key media processing task. Therefore, both the VP9860 and CloudRSE are deployed at the media processing layer.

A. The SMC (Service Management Center) is a management and control component, operating at the management layer to handle device management, conference scheduling, and control, not media processing.

D. The Box 310 is a video conferencing endpoint/terminal. It belongs to the access layer, where users connect to the collaboration service.

1. Huawei HCIP-Collaboration V4.0 Training Material (2023).

Reference: Chapter 2

"Huawei Video Conferencing Solution Architecture

" Section 2.1. The architecture diagram and component descriptions explicitly place the MCU (e.g.

VP98xx series) and RSE (Recording & Streaming Engine) in the "Media Processing Layer" or "Service Layer." The SMC is shown in the "Management Layer

" and terminals like the Box series are in the "Access Layer."

2. Huawei CloudLink Video Conferencing Solution V600R019C10 Product Documentation.

Reference: "System Architecture" section. This document details the logical architecture

describing the function of each component. It specifies that the Media Exchange Unit (which includes MCU and RSE functionalities) is responsible for media processing services such as multipoint conferencing and recording.

3. Huawei VP9800 Series MCU Product Datasheet.

Reference: "Product Features" section. The datasheet describes the VP9860's core functions as "powerful media processing capabilities

" including 1080p60 full encoding/decoding and audio/video mixing

confirming its role in the media processing layer.

In a Huawei Unified Communications (UC) solution, an intranet-only Session Controller (SC) cluster is deployed to manage session control and registration for a large number of internal users.

A. A dedicated registration SC cluster is a specific deployment role designed to offload the high volume of SIP registration requests from the core call control servers (e.g., USM), enhancing system performance and scalability. Its primary and often sole configured function is SIP registration.

B. To ensure high availability and manage load, the SC cluster supports both single-active (active/standby) for redundancy and multi-active (load sharing) distribution modes.

C. H.323 and SIP registration mechanisms are different. It is a recommended best practice to deploy a separate, standalone SC to function as an H.323 Gatekeeper, isolating H.323 RAS traffic from SIP registration traffic for stability and easier management.

D. The primary driver for deploying a dedicated registration SC cluster is scalability. When the number of SIP endpoints on the intranet becomes large, this architecture prevents the core call servers from being overwhelmed by registration traffic.

All the provided options are correct statements regarding the deployment principles and capabilities of a Huawei intranet SC cluster network.

1. Huawei SessionEngine Product Documentation (for SE1000)

"Network Planning > Typical Networking and Applications > Intranet Deployment Scenario". This section details the deployment of SC clusters within an enterprise network

outlining the rationale for dedicated registration clusters when the number of SIP users is high (supports D).

2. Huawei UC Solution V300R019 Network Planning Guide

"Chapter 4: Network Design > SC Deployment Design". This chapter specifies that for large-capacity SIP user registration

a dedicated registration SC cluster should be deployed

whose main function is to process SIP registrations (supports A).

3. Huawei SessionEngine Product Documentation (for SE1000)

"Feature Guide > High Availability > SC Cluster Modes". This document describes the supported high-availability and load-balancing mechanisms

explicitly mentioning the single-active (active/standby) and multi-active (load-sharing) modes (supports B).

4. Huawei UC Solution V300R019 Network Planning Guide

"Chapter 5: Device Deployment > Integrating H.323 Endpoints". This guide recommends deploying a standalone SC to serve as a dedicated H.323 Gatekeeper to handle H.323 endpoint registration and call control

separating it from the SIP environment (supports C).

The command output displays media stream information for the conference. The VP9850, working in Integrated Access Unit (IAU) mode, acts as a conference participant that receives multiple video streams, decodes them, creates a single composite video (continuous presence), and re-encodes it as a new stream sent back to the conference.

In the provided log, the streams from Site (16), Site (17), and Site (18) are the inputs to the IAU. The IAU itself is participating as another site, in this case, Site (19). The stream generated by the IAU will therefore have a source ID (srcId) of 19. The log shows only one video stream with srcId: 19, which has the stream number (strmLabel) 2710124429803.

A. This is the original video stream from Site (16), which is an input to the IAU, not its composite output.

B. This is the original video stream from Site (17), which is an input to the IAU, not its composite output.

C. This is the original video stream from Site (18), which is an input to the IAU, not its composite output.

1. Huawei CloudMCU Product Documentation - Command Reference. The documentation for the conf get strmInfo command specifies that the srcId field indicates the site ID of the media stream's source. This confirms that the stream with strmLabel 2710124429803 originates from the participant with site ID 19.

2. Huawei VP98 Series Universal Transcoding MCU Administrator Guide

Section: "IAU Mode". This guide details that when a VP98 series MCU operates in IAU mode

it joins a conference as a gateway participant. It receives multiple video streams

composes them into a single continuous presence layout

and sends this composite video stream back to the main conference. This supports the conclusion that the IAU (Site 19) generates a new

single stream from the multiple inputs.

3. Huawei HCIP-Video Conference V4.0 Training Material

Module: "MCU Advanced Features". The courseware explains the interaction between an SFU (like CloudMCU) and an IAU. It clarifies that the IAU is treated as a standard endpoint by the SFU

and the composite stream it generates is identified by the IAU's own site ID in the conference's stream table.