Product Overview - Icecat

HUAWEI SMC2.0V500R002C00

Product Overview

Issue 03

Date 2016-05-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2016. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respectiveholders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees orrepresentations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://e.huawei.com

Issue 03 (2016-05-30) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://e.huawei.com

Contents

1 Product Positioning and Highlights.......................................................................................... 11.1 Positioning...................................................................................................................................................................... 21.2 Highlights....................................................................................................................................................................... 3

2 Application Scenarios...................................................................................................................52.1 Deployment in a Large Enterprise and Its Branches...................................................................................................... 62.2 Firewall Traversal Solution............................................................................................................................................ 82.3 Multi-SMC2.0 Interconnection...................................................................................................................................... 92.4 Video Surveillance Convergence Solution................................................................................................................... 11

3 Structure and Appearance..........................................................................................................133.1 System Architecture..................................................................................................................................................... 143.2 Server Appearance........................................................................................................................................................15

4 Features and Benefits..................................................................................................................184.1 Conference Template Predefinition.............................................................................................................................. 194.2 Multiple Conferencing Modes......................................................................................................................................194.3 Convenient Multi-Level Conferencing.........................................................................................................................194.4 Rich Conference Control Functions............................................................................................................................. 204.5 Preset Conference Functions........................................................................................................................................ 224.6 Conference Recording and Live Broadcast.................................................................................................................. 234.7 SMS and Email Notifications....................................................................................................................................... 234.8 Various Devices............................................................................................................................................................ 244.9 Unified Resource Scheduling....................................................................................................................................... 274.10 Device Template Predefinition................................................................................................................................... 274.11 Parameter Locking......................................................................................................................................................284.12 Real-Time Display of Device Status.......................................................................................................................... 284.13 Batch Participant Processing...................................................................................................................................... 294.14 Participant Predefinition............................................................................................................................................. 304.15 Device Auto-Detect.................................................................................................................................................... 304.16 Detailed Reports and Statistics................................................................................................................................... 304.17 Flexible Permission Control....................................................................................................................................... 324.18 Corporate Directory....................................................................................................................................................334.19 Intuitive Topology Management.................................................................................................................................334.20 Allocating Virtual Ports.............................................................................................................................................. 34

HUAWEI SMC2.0Product Overview Contents


ii

4.21 Comprehensive SC Management Mechanism............................................................................................................354.21.1 Zone Management................................................................................................................................................... 364.21.2 Registration Control................................................................................................................................................ 374.21.3 Call Control............................................................................................................................................................. 384.21.4 Bandwidth Management..........................................................................................................................................394.21.5 Route restriction...................................................................................................................................................... 39

5 Reliability......................................................................................................................................41

6 Unparalleled Security................................................................................................................. 43

7 Openness.......................................................................................................................................45

8 Operation and Maintenance......................................................................................................468.1 Web Interface................................................................................................................................................................478.2 Logs and Alarms...........................................................................................................................................................488.3 Device Upgrades...........................................................................................................................................................508.4 Device Inspection......................................................................................................................................................... 50

9 Technical Specification.............................................................................................................. 519.1 Environmental specifications....................................................................................................................................... 529.2 Performance and Capacity............................................................................................................................................529.3 Standards Compliance.................................................................................................................................................. 54

10 Acronyms and Abbreviations................................................................................................. 56

HUAWEI SMC2.0Product Overview Contents


iii

1 Product Positioning and Highlights

This topic describes basic concepts, advantages, and benefits of the HUAWEI ServiceManagement Center (SMC2.0).

HUAWEI SMC2.0Product Overview 1 Product Positioning and Highlights


1

1.1 PositioningThis topic describes the position of SMC2.0.

The HUAWEI SMC2.0 service management system (SMC2.0 for short) is a new-generationvideoconferencing service management system that centralizes the management of videocommunications services for middle- and large-sized enterprises. The SMC2.0 is a maturemanagement system for video communication, which enables enterprise IT decision makers,system administrators, and operators to smoothly communicate and collaborate with eachother remotely, thereby greatly reducing enterprise operating costs.

Figure 1-1 shows the SMC2.0 in an overall network solution.

Figure 1-1 SMC2.0 in an overall network solution

Based on its superior architecture, the SMC2.0 provides:

l Intuitive web interface: It allows users to easily interact with the videoconferencingsystem.

l Intelligent management: The unified management platform allows for real-timemonitoring and remote diagnostics, maintenance, and upgrades for devices in thevideoconferencing system.

l Flexible resource allocation: In middle- and large-sized videoconferencing networks,conference resources can be allocated by service area. Instant conferences can be easilyhosted.



2

l Improved compatibility: The SMC2.0 preserves third-party interfaces for conferencesinitiation from third-party platforms. Meanwhile, it supports various types of devices,which helps maintain customers' investment profitability.

1.2 HighlightsThe SMC2.0 is one of the most capable systems for conference and device management. Itsupports large networks and provides third-party interfaces for convergence.

Centralized Control

From the SMC2.0 web interface, users can manage multiple devices in the following ways:

l Administrators can manage a complete portfolio of videoconferencing resources withone device, including MCUs, GK/SIP servers, recording devices, and video endpoints.

l Powerful device management functions include auto detection, batch parameterconfiguration, visualized network topology and management, locked parameters forconsistent operation, batch software version management and upgrade, querying andhandling of alerts, and parameters configuration and alerts management for mainstreamendpoints.

l Flexible and easy-to-create statistical reports deliver video resource usage updates in realtime for more efficient resource management and fast decision making.

l Administrators can flexibly manage large-scale videoconferencing networks bydeploying MCUs and gatekeepers in geographically dispersed corporate branches as wellas balance MCU cloud resource center loads with internal backup or between MCUs toimprove resource utilization and conference reliability.

l Distributed videoconferencing network by deploying SMC2.0s is designed for multi-level organization in government and enterprise industry. Device management by eachorganization and communication between different organizations including schedulingconference, conference control and so on are supported.

l The NLog end-to-end quality-monitoring function empowers operators to monitorconference quality and analyze fault history.

Hierarchical and Role-Based Authentication for Multiple Usersl Large enterprises can categorize users according to corporate organizational structures

and define or assign user roles and access rights depending on organizationalarchitecture.

l Graphics-based tree architecture displays show usage by individual users.l Operators can establish large-scale video operating networks to provide hierarchical and

role-based virtual operation services for multiple corporations.

Efficient Conference Schedulingl SMC2.0 provides an easy-to-use User Interface (UI) that enables users to conveniently

schedule conferences, view the status of conference rooms, choose appropriateconference times and sites, and send conference notices to participants via email.

l Conference templates and conference history functions allow users to define andschedule large cascaded conferences. The SMC2.0 system also allows automaticcascading of MCUs as needed with seamless management of multisite calls



3

l SMC2.0 can be integrated with Office Automation (OA) systems. For example, userscan schedule conferences, cancel conferences, and view the availability of participants orconference rooms with the integrated Outlook application. Conference notifications areautomatically added to participants Outlook calendars.

l SMC2.0 can be integrated with Office Automation (OA) systems. For example, userscan schedule conferences, cancel conferences, and view the availability of participants orconference rooms with the integrated Outlook application. Conference notifications areautomatically added to participants Outlook calendars.

l Users can join a conference by using the One-Click-to-Joinbutton on the touchscreen orby initiating an ad-hoc conference with a unified access number.

Multiple Backups

The SMC2.0 adopts backup mechanisms for the server, SC, and MCU to achieve highreliability.

l Cluster deployment: Active and standby servers can be deployed on the network to forma cluster and implement failovers.

l SC hot backup: If network errors occur on the active SC, the standby SC can take over.

l MCU backup: If an MCU fails, the SMC2.0 automatically switches services to anavailable MCU in the same or standby service area.

Embedded SC and Standalone SC

By default, the SMC2.0 is provided with an embedded SC. The SMC2.0 also supportsstandalone SCs.

l An embedded SC provides up to 1000 registration nodes.

l A standalone SC provides up to 6000 registration nodes, covering the needs of large-sized networks.

l Embedded SC enables integrated deployment, firewall traversal, partition management,B2B calls and call routing.

l SMC2.0 adds the ability to manage multiple standalone Switch Centers (GK/SIP Server),which allows for networking on a large scale and large-capacity firewall traversal.

Preserved Third-Party Interfaces

The SMC2.0 provides standard third-party interfaces for convergent conferences with third-party platforms.

l SMC2.0 provides APIs for integration with other vendor products and seamlessintegration with Microsoft® Active Directory and OA systems.

l Support for integration with existing user-authentication system in enterprises satisfiesthe need for unified account working in office.

l SMC2.0 seamlessly integrates with other mainstream video surveillance platforms bystreaming surveillance camera video directly to video conferences.

l Integration with mainstream SMS platform is supported so that it can make it easy to usethe system.



4

2 Application Scenarios

This topic describes use of the SMC2.0 in different application scenarios.

HUAWEI SMC2.0Product Overview 2 Application Scenarios


5

2.1 Deployment in a Large Enterprise and Its BranchesThe SMC2.0 can be deployed on a network for a large enterprise and its branches so all typesof devices on the network can join HD video conferences.

The SMC2.0 serves as a service management platform in a large enterprise and its branchesand integrates all components in the videoconferencing system, enabling fast deployment forenterprise applications and eliminating the need for installing multiple components.

Figure 2-1 shows the deployment in a large enterprise and its branches.

Figure 2-1 Deployment in a large enterprise and its branches

In the network for a large enterprise and its branches:

l The SMC2.0 serves as a service management platform that supports H.323 and SIP,manages conference resources and devices in the system, and provides functions, such asconference scheduling.

l The embedded SC manages the endpoints registered with it. Standalone SCs can bedeployed to expand network capacity based on service requirements.

l An administrator logs in to the web interface of the SMC2.0 to control the permissionsby specifying user types and their organizations. Users can schedule conferences fromthe web interface.



6

SMC2.0 Networking with VP9000 Series MCUs

The SMC2.0 can work with VP9000 series MCUs, recording servers, HD videoconferencingendpoints, and telepresence systems using the IP connection type. (If the VP9660 or VP9650MCUs are used, the ISDN connection type is also supported). Enterprise users can deployMCUs, endpoints, and telepresence systems based on site requirements. The SMC2.0manages MCUs, endpoints, and telepresence systems in a unified manner and can be used toschedule and control conferences.

Figure 2-2 shows the network where the SMC2.0 works with VP9000 series MCUs.

Figure 2-2 SMC2.0 networking with VP9000 series MCUs

l The SMC2.0 manages MCUs and recording servers in a unified manner and allocates

them based on the conference scheduling policy when scheduling conferences.l Users can schedule conferences on the SMC2.0. On endpoints, users can use SiteCall or

dial the unified access number to initiate conferences.l After registering with an SC using both SIP and H.323, an MCU allows both SIP and H.

323 endpoints to join the same conference.l During a conference, each participant can use continuous presence per port.

SMC2.0 Networking with ViewPoint 8000 Series and VP9000 Series MCUs

In this network, the MCU resource pool has both ViewPoint 8000 series and VP9000 seriesMCUs.



7

l If a conference is held on a ViewPoint 8000 series MCU, participants enjoy conferenceexperience provided by the ViewPoint 8000 series MCU. All participants view a fixedcontinuous presence layout provided by the MCU or are provided with certain fixedcontinuous presence layouts provided by the MCU. If a conference is held on a VP9000series MCU, participants enjoy conference experience provided by the VP9000 seriesMCU. Participants are allowed to select desired continuous presence layouts on theirendpoints.

l The SMC2.0 selects the matching recording server based on the MCU where aconference is being held. The ViewPoint 8000 series MCUs work only with therecording server CR10. The VP9000 series MCUs can work with the recording serversRSE6500 and CR10. The RSE6500 is recommended.

SMC2.0 Networking with VP9000 Series MCUs shows the network where the SMC2.0works with ViewPoint 8000 series and VP9000 series MCUs.

2.2 Firewall Traversal SolutionIn a large-sized enterprise network, the traversal between private and public networks must beavailable because videoconferencing endpoints and MCUs may be installed in different placesand used in different ways. The SMC2.0 provides different networking solutions based on thenetworks where endpoints are deployed.

Single SC Deployed on the DMZSingle SC is deployed on the DMZ zone and serves for the public and private endpoints andMCUs. Two network segments are divided, with one IP address provided to connect deviceson the private network, and the other to connect devices on the public network by NATmapping.

The Session Initiation Protocol (SIP) is used for controlling multimedia communicationsessions such as voice and video calls.

Devices on the private network can communicate with those on the public network throughSC which transfers signaling and media streams.

Figure 2-3 Single SC deployed on the DMZ

Network description:



8

l Video conferencing devices are deployed on the public network and private network, andmost are deployed on the private network.

l MCU registers with SC using H.323 and SIP, and H.323 and SIP endpoints can join amultipoint conference concurrently.

l SC is deployed on the DMZ, and separated from public and private networks, to improvesecurity of enterprise private network.

l Corresponding ports are opened on firewall to ensure data communication between SCand devices.

l Deployment of a single SC lowers the network-building cost.l The SC can work with the firewall to open and close of dynamic UDP ports used for

video and audio traffic.

SC Video FirewallIn video firewall mode, one server simultaneously processes information for multiplenetworks. A server where a standalone SC is installed uses different service addresses tosimultaneously access different networks. By processing and forwarding data betweennetworks, the SC allows devices on private and public networks to communicate with eachother.

Using the GK video firewall for firewall traversal is simple, as shown in Figure 2-4.

Figure 2-4 SC video firewall

In the SC video firewall network:

l The SC uses different service addresses to simultaneously access up to four differentnetworks.

l The SC forwards signaling and media streams between devices on different networks toimplement interoperability.

2.3 Multi-SMC2.0 InterconnectionThe SMC2.0 interconnection scheme is recommended if the number of videoconferencingdevices is large and scattered in many locations.

In some videoconferencing systems, devices are deployed in many locations, with certaindevices gathered in a place. To manage these devices, the SMC must be able to implementcentralized intra-zone management and flexible cross-zone management. After multipleSMC2.0s that are scattered in different places are connected, they can communicate with each



9

other and are able to implement cross-zone conference scheduling. Figure 2-5 shows theSMC2.0 interconnection network.

Figure 2-5 Network where multiple SMC2.0s are connected

The following describes the network:

l Inter-zone managementThe SMC2.0s are deployed in different zones to manage all devices in the zone andschedule services in the zone. Devices in different zones are independent.

l Cross-zone connectionThe SMC2.0s deployed in different zones can be connected to schedule and controlconferences in these zones. If multiple SMC2.0s are deployed, they can be connected asrequired. Figure 2-6 shows two typical networks.



10

Figure 2-6 Networks where SMC2.0s are connected

l Controlled rightsThe system has the following requirements on SMC2.0 interconnection configuration:– A whitelist needs to be configured to specify the SMC2.0s that can be connected.– Each SMC2.0 interconnection operation must be confirmed and approved by the

administrator.– Only the administrator can configure interconnection users and grant rights to them.

2.4 Video Surveillance Convergence SolutionWhen the SMC2.0's embedded converged gateway interconnects with Huawei intelligentvideo surveillance (IVS), Tiandy video surveillance systems, or eLTE trunking system, userscan schedule collaborative conferences from the VSD.

In a collaborative conference, surveillance videos can be displayed in video conferences,allowing users to view videos captured by surveillance cameras in real time.

The video surveillance convergence solution supports two networking modes:l Cross-network-segment mode

The SMC2.0 uses two network ports to separately connect to a videoconferencingnetwork and a video surveillance network, as shown in Figure 2-7.

Figure 2-7 Cross-network-segment mode



11

l Intra-network-segment mode

All videoconferencing and video surveillance devices are in the same network segment,as shown in Figure 2-8.

Figure 2-8 Intra-network-segment mode

In both networking modes, the video surveillance convergence solution provides thefollowing features:

l The converged gateway uses the following protocols to interconnect with videosurveillance systems:– Huawei IVS system: TCP/UDP+GB28281– Tiandy video surveillance system: TCP/UDP and HTTP– eLTE trunking system: TCP/UDP

l A single converged gateway can be used to hold collaborative conferences concurrentlyfrom different VSD clients.

l A maximum of 30,000 cameras can be connected.l VSD clients interconnect with the SMC2.0 using HTTP.l From the VSD UI, users can schedule collaborative conferences, define conference

plans, and perform conference control, PTZ control, and recording & streamingoperations.



12

3 Structure and Appearance

This topic describes the system structure and appearance of the SMC2.0, providing you with amore vivid impression of the SMC2.0.

HUAWEI SMC2.0Product Overview 3 Structure and Appearance


13

3.1 System ArchitectureThis topic describes the system architecture of SMC2.0.

The SMC2.0 is composed of three parts: web client, back-end service, and database, as shownin Figure 3-1.

Figure 3-1 SMC2.0 system architecture

The functions of system components are as follows:

l Web clientThe web client provides the human machine interface. Users can log in to the webinterface and perform the following operations allowed for their user roles:Administrators can maintain system devices and configure resource usage policies; otherusers can only schedule and initiate conferences. All functions, including user rightsmanagement, are implemented from the web interface.

l Back-end serviceThe back-end service is the SMC2.0 engine, which provides E-mail management service,device management service, and others.

l DatabaseThe database is the SMC2.0's data warehouse. It supports efficient and stable dataaccess, contributing to a high performance SMC2.0.

SMC2.0 Software InstallationThe SMC2.0 can be released in a software package, which can be installed on a standarddedicated server or a VMware VM. The SMC2.0 must be hardened using scripts to ensureservice security.

Table 3-1 describes the configurations required for the SMC2.0 software installation.



14

Table 3-1 SMC software installation requirements

Installation Environment Required Configurations

Standard dedicated server, common PCserver, or VMware VMNOTE

l The standard dedicated server can beprovided by HP, IBM, or Huawei.

l To install the SMC2.0 on a VM, use theSMC2.0 image package.

l CPU: 4 corel Memory: 8 GBl Hard disk: 300 GBl Network adapter: GE adapter (In the

scenario where the built-in SC is usedand traversal between private and publicnetworks exists, dual network adaptersare required.)

l OS: Windows Server 2008 R2

SC Software Installation

The SC can be released in a software package, which can be installed on a standard dedicatedserver or a VMware VM. The SC must be hardened using scripts to ensure serverperformance.

Table 3-2 describes the configurations required for the SC software installation.

Table 3-2 SC software installation requirements

Installation Environment Required Configurations

Standard dedicated server, common PCserver, or VMware VMNOTE

l The standard dedicated server can beprovided by HP, IBM, or Huawei.

l To install the SC on a VM, use the SC imagepackage.

l CPU: 4 corel Memory: 8 GBl Hard disk: 300 GBl Network adapter: GE adapter (In the

scenario where the SC is used andtraversal between private and publicnetworks exists, dual network adaptersare required.)

l OS: SUSE Linux Enterprise Server 11SP1 or Red Hat Enterprise Linux Server6.5

3.2 Server AppearanceThis topic describes the server appearance of SMC2.0.

It is recommended that the SMC2.0 use the HUAWEI Tecal RH2285 V2 server. For detailsabout the server, see the provided document.

Figure 3-2 shows the server appearance.



15

Figure 3-2 Server appearance

Front Panel

Figure 3-3 shows the front panel of the server.

Figure 3-3 Front Panel

1 UID button/indicator 2 HEALTHY indicator



16

3 Ethernet port indicator 1 4 Ethernet port indicator 2

5 Power button/indicator 6 VGA port

7 Embedded DVD-ROM drive (availablewhen only eight hard disks are configured)

8 Label (showing RH2285 V2 hardwareconfigurations)

9 Hard disk (slots 0 to 7 from left to right) 10 USB port

11 Hard disk active indicator 12 Hard disk fault indicator

Rear PanelFigure 3-4 shows the rear panel of the server.

Figure 3-4 Rear Panel

1 Data transmission status indicator 2 Connection status indicator

3 Ground screw 4 DB9 serial port

5 DB15 VGA port 6 UID indicator

7 RJ45 BMC management network port 8 GE port 2

9 GE port 1 10 USB port

11 Power socket for PSU 2 12 Indicator for PSU 2

13 PSU 2 14 Power socket for PSU 1

15 Indicator for PSU 1 16 PSU 1

17 2.5-inch hard disk 18 2.5-inch hard disk



17

4 Features and Benefits

This topic describes the main features and benefits of the SMC2.0.

HUAWEI SMC2.0Product Overview 4 Features and Benefits


18

4.1 Conference Template PredefinitionA conference template is a collection of conference settings that are stored in the SMC2.0,including the conference participants. It can be used for conference scheduling, improvingconference scheduling efficiency.

The SMC2.0 supports the following types of conference templates:l Common conference: No conference ID is specified, and participants can join the

conference only after the conference administrator initiates it from the SMC2.0.l Ad hoc conference: A conference ID is specified. The conference administrator or any

participants can activate the conference by dialing the conference ID and entering theactivation password.

l Multi-level conference: Multiple common conferences can be cascaded into oneconference in the specified structure.

4.2 Multiple Conferencing ModesThe SMC2.0 supports multiple conferencing modes so users can initiate or join conferencesflexibly:

The SMC2.0 allows for the following conferencing modes:

l Initiate conferences from the SMC2.0 web interface using conference templates or bycreating new conferences.

l Call ad hoc conference IDs to activate conferences from videoconferencing endpoints.l Call the unified access number to activate conferences from videoconferencing

endpoints.l Call the unified access number to create conferences from videoconferencing endpoints.l Call Point-to-Point to Multipoint Conference ID to activate Point-to-Point to Multipoint

conferences from videoconferencing endpoints.l Initiate conference using the SiteCall function.l Initiate conferences using a third-party interface.l Initiate conferences using Outlook.

4.3 Convenient Multi-Level ConferencingOn the SMC2.0, common conferences can be cascaded to form a multi-level conference inspecified structure.

Typical Scenario 1A province-level seminar that contains and city conference center B needs to be held.Conference template A and conference template B are usually used to initiate conferences forcity conference center A and city conference center B, respectively. In this case, conferencetemplate A and conference template B can be merged to form a multi-level conferencetemplate. This multi-level conference template can be used to initiate the desired seminar.Conference template A and conference template B do not need to be modified.



19

Typical Scenario 2Conference center A is holding a food seminar, while conference center B is holding a healthylife seminar. If a manager wants to merge these two seminars, multi-level conferencing can beused.

4.4 Rich Conference Control FunctionsUsers can search conferences and view conference details. For active conferences, theSMC2.0 provides various conference controls.

Table 4-1 lists the available conference controls.

Table 4-1 Conference controls

Type Conference Controls

Participant Add, create, or delete a participant.

Add participant(Advanced Parameter)

Add a cascaded participant.

Call specific or all participants and disconnect specificparticipants.

View presence of anonymous participants.

Select a participant to view.

View the information about an active participant.

View participant capabilities.

Enable or disable voice activation.

Query participant network data.

View participant snapshots.

View cascaded participants.

Set and cancel the participant sequence.

Set and cancel the participant captions.

Set Two-stage dialing

Active/Standby participant switchover

Move Participant

Microphone, speaker,and volume

Mute and unmute a speaker.

Mute and unmute all speakers.

Mute and unmute a microphone.

Mute and unmute all microphones.



20

Type Conference Controls

Enable or disable discussion.

Audio, video, and camera Adjust the conference audio volume after an MCU performsaudio mixing.

Turn on or off video.

Lock and unlock video sources.

Adjust cameras.

Presentation Send and stop presentation

Lock the presentation sharing right for a conference orparticipant.

Unlock the presentation sharing right.

Revoke the presentation sharing right.

Broadcasting Start and stop broadcasting a participant.

Set and cancel scheduled broadcasting.

Start and suspend scheduled broadcasting.

Continuous presence Customize continuous presence

Set continuous presence.

Set participant broadcasting in continuous presence in turn.

Start and stop broadcasting continuous presence.

Start, suspend, and stop participant broadcasting in continuouspresence in turn.

Chair Conferring and revoking chair control rights.

Give the floor.

Send a notification before giving the floor.

Set broadcasting in turn for the chair participant.

Start, suspend, and stop broadcasting in turn for the chairparticipant.

Conference Set the conference live broadcasting and recording parameters.

Extend or end a conference.

Merge or splitting conferences.

Customizing settings Send instant messages to selected or all participants.

Set and cancel the conference banners.

Set and cancel the conference captions.



21

4.5 Preset Conference FunctionsThe SMC2.0 allows users to preset conference functions before a conference starts so thosefunctions can be used during the conference.

Table 4-2 lists the preset functions that the SMC2.0 supports.

Table 4-2 Preset functions

Preset Function Description

Presetting Continuous Presence Continuous presence indicates thecombination of panes of multipleconference participants. This enables eachparticipant to view multiple participants atthe same time.

Presetting Broadcasting in Turn forContinuous Presence

After you broadcast participants in turn forcontinuous presence, selected participantsare broadcast in selected panes at thespecified intervals.

Presetting Scheduled Broadcasting After you set scheduled broadcasting,selected participants are broadcast in thespecified sequence and at the specifiedintervals.

Presetting Broadcasting in Turn After you set broadcasting in turn, the chairparticipant views the selected participants inturn at specified intervals.

Presetting Locked Video Sources If you lock the video source for aparticipant, no conference controls exceptView Participant will affect the videosource of the participant.

Presetting the Participant Sequence The participant sequence is the order inwhich participants are placed in theparticipant list. You can adjust theparticipant sequence so that importantparticipants are placed at the top of theparticipant list.

Setting a Conference Banner A conference banner is displayed at the topof participants' screens.

Presetting a Conference Caption A conference caption is displayed on thescreens of participants. You can set thedisplay position and effects on theparticipant endpoints.



22

Preset Function Description

Preset Remote SMC Administrator After a remote SMC administrator is preset,the administrator can approve conferencescheduling requests when the correspondingremote SMC receives the requests.

4.6 Conference Recording and Live BroadcastThe SMC2.0 manages recording servers and allocates recording resources for single-point andmultipoint conferences.

BackgroundAfter a recording server is registered with a Switch Center (SC), an endpoint can dial theunified recording number to access the recording server to perform single-point recording. Ifthe recording server is called into a multipoint conference, multipoint recording is available inthe conference.

Various Recording ConferencesThe SMC2.0 manages recording servers based on organizations and supports the followingtwo types of recording conferences:l Live broadcast conference: Users can view a live broadcast conference on the recording

server in real time. After a conference is scheduled, the SMC2.0 sends the live broadcastaddress using emails.

l Recorded conference: Users can view a recorded conference only after the conferenceends. After the conference, the SMC2.0 sends the recorded file address using emails ormessage.

4.7 SMS and Email NotificationsThe SMC2.0 can be used to send real-time notifications to users to notifying them ofconference information, participant information, user information, and alarm information. Thenotifications can be sent through SMSs or emails.

The SMC2.0 can send the following types of information to related persons through SMSs oremails in real time:l Conference information

– Scheduled conference information– Conference modification or cancelation information

l Participant informationParticipant addition or modification information about a scheduled conference

l User information– User information when a local user is added– Initial password when an administrator resets the password of a local user

l Alarm information



23

Information about alarms generated in the SMC2.0

4.8 Various DevicesThe SMC2.0 allows connections from various devices and provides a web interface formanaging and maintaining those devices.

On the SMC2.0, devices are classified into manageable and unmanageable devices:l Manageable devices: These devices support online configuration, online update, device

alarm viewing, backup, and configuration restoration.l Unmanageable devices: These devices are resources for conference scheduling but do

not support online configuration, online update, device alarm viewing, backup, orconfiguration restoration.

NOTE

l Adding manageable devices: After a static IP address and trap address are set on a device, search forthe IP address of the device on the SMC2.0. The device can then be added to the SMC2.0 using aconfiguration template or by setting device parameters.

l Adding unmanageable devices: Add devices to the SMC2.0 in unmanageable mode.

Multiple Participant Endpoint ModelsThe SMC2.0 supports SIP and H.323 participants. Table 4-3 lists the models of participantendpoints that can be added to the SMC2.0.



24

Table 4-3 Participant endpoint models and versions

Manageable orNot

Model

Manageable

HUAWEI 9000 HD videoconferencing endpoint

HUAWEI TE20

HUAWEI TE30/40/50/60 videoconferencing endpoint

HUAWEI TX50

HUAWEI TP1102/TP1002 series telepresence systems

HUAWEI TP3006/3016/3106_55/3106/3206/3118S/3118

HUAWEI RP series telepresence systems

HUAWEI DP300 videoconferencing endpoint

Polycom HDX 4000/6000/7000/8000/9000

Cisco TelePresence Codec C20/C40/C60/C90

Unmanageable

HUAWEI 9000 HD videoconferencing endpoint

HUAWEI TP series telepresence systems

HUAWEI RP series telepresence systems

HUAWEI TE20

HUAWEI TE30/40/50/60 videoconferencing endpoint

HUAWEI TX50

HUAWEI TE Desktop&TE Mobile

HUAWEI DP300 videoconferencing endpoint

Polycom HDX 4000/6000/7000/8000/9000

Cisco TelePresence Codec C20/C40/C60/C90

Others

NOTEThe HUAWEI RP series telepresence systems can only be regarded as HD videoconferencing endpointswhen they are added to the SMC2.0 as manageable devices.

On the SMC2.0, users can view the call information about manageable participants, controltheir call bandwidth and protocol, and end the current calls for the participants.



25

Figure 4-1 Call list

The SMC2.0 web interface displays the local and remote screenshots of manageableparticipants in a conference.

Figure 4-2 Screenshots

Multiple MCU ModelsTable 4-4 lists the models of MCUs that can be added to the SMC2.0.



26

Table 4-4 MCU models and versions

Manageable or Not

Model Software Version

ManageableHUAWEI VP9660/VP9650/VP9630 Unrestricted

ViewPoint 8660/8650/8650C V100R008 or later

Unmanageable

HUAWEI VP9620/9610 Unrestricted

ViewPoint 8660/8650/8650C Unrestricted

NOTEAll MCUs can be added to the SMC2.0 as unmanageable MCUs.

4.9 Unified Resource SchedulingThe SMC2.0 manages MCUs and recording servers as resources and provides differentscheduling policies for them.

MCU SchedulingThe SMC2.0 allows you to add universal transcoding MCUs and universal transfer MCUs.Huawei ViewPoint 8000 series (ViewPoint 8660, ViewPoint 8650, and ViewPoint 8650C)MCUs are non-universal transcoding MCUs. Huawei VP 9000 series (VP9660, VP9650, andVP9630) MCUs can be set to universal transcoding or universal transfer MCUs.

NOTE

A universal transcoding MCU allows endpoints to join a conference with any protocol, format, orbandwidth. The endpoints can use any ports of the MCU. However, a universal transfer MCU cannot.By default, VP9000 series MCUs are configured as universal transcoding MCUs.

l Switching MCU resource typesA VP9000 series MCU can be configured as a universal transcoding or universal transferMCU.

l Scheduling MCUs on the SMC2.0On the SMC2.0 web interface, you can add, modify, or delete MCUs and view details,alarms, logs, node relationships, and usage of MCUs.

RSE SchedulingOn the SMC2.0 web interface, you can add, modify, or delete RSEs and view details, alarms,logs, node relationships, and usage of recording servers.

4.10 Device Template PredefinitionA device template is a collection of device settings that are stored in the SMC2.0. It can thenbe used to quickly add devices to the SMC2.0.

The SMC2.0 supports the following types of device templates:



27

l ParticipantParameters that can be predefined in this type of template: H.323, SIP, DNS, SNMP,time, call, and others.

l MCUParameters that can be predefined in this type of template: H.323, SIP, DNS, and SNMP.

4.11 Parameter LockingThe SMC2.0 allows parameters of manageable devices to be locked.

On the SMC2.0 web interface, users can modify the settings of manageable devices and lockcertain parameters. The locked parameters are not editable. When settings are modified on adevice, the SMC2.0 restores the locked parameter settings on the device.

Figure 4-3 Parameter locking

4.12 Real-Time Display of Device StatusOn the SMC2.0, a user can check idle/busy status of participants, packet loss rates, and statusof converged gateways.

Viewing Participants' Idle/Busy StatusWhen scheduling a conference, a user can view participants' idle/busy status and selectappropriate participants to join the conference accordingly.

Figure 4-4 Idle/Busy status of participants



28

Viewing Packet Loss Rates of ParticipantsThe SMC2.0 supports the network statistics tool (Nlog V2) to view participants' real-timepacket loss data or data history, as shown in Figure 4-5.

Figure 4-5 Nlog V2

Viewing the Status of Converged GatewaysOn the SMC2.0, a user can view the status, used and available monitoring channels, alarms,logs, and start ID and total IDs of participants for each converged gateway.

4.13 Batch Participant ProcessingThe SMC2.0 allows you to import and export unmanageable participant information to helpadd, modify, and delete unmanageable participants in batches.

l To add multiple unmanageable participants, download the Batch Import Template, fill inthe unmanageable participant information, and upload the saved file to the SMC2.0 toimport unmanageable participant information to the SMC2.0 in batches.

l If you want to modify or delete multiple unmanageable participants, export theparticipants. In the exported file, modify or deleted related information and upload thefile to the SMC2.0 again.



29

4.14 Participant PredefinitionOn the SMC2.0, users can predefine manageable participants.

Typical ScenarioEngineer A is deploying videoconferencing devices for an enterprise. The SMC2.0 isavailable for use, but some endpoints in the enterprise have not been powered on. In this case,engineer A can predefine participants by configuring the participant endpoint settings(consistent with the endpoints not powered on). Then when the endpoints are powered on andpass the authentication by the SMC2.0, the endpoints automatically load the settings from theSMC2.0 and are added to the SMC2.0.

4.15 Device Auto-DetectThe SMC2.0 is able to auto-detect devices, and the administrator can add the detected devicesto the SMC2.0.

PrerequisitesThe trap address on the device is the SMC2.0 IP address.

Typical ScenarioThe administrator wants to add a device to the SMC2.0, but forgets the device IP address. Inthis case, the administrator can use the SMC2.0's auto-detect function to obtain the list ofdevices that are connected but have not been added to the SMC2.0. The administrator canthen check and modify the device information in the list and add the desired device to theSMC2.0.

Types of Devices That Can Be Auto-DetectedThe SMC2.0 can auto-detect the following devices:l Automatically detecting participants: A participant, whose trap address is set the

SMC2.0's IP address, automatically sends a trap message to the SMC2.0 using SimpleNetwork Management Protocol (SNMP). The SMC2.0 administrator can then add thisparticipant to the SMC2.0.

l Automatically detecting MCUs: An MCU, whose trap address is set the SMC2.0's IPaddress, automatically sends a trap message to the SMC2.0 using SNMP. The SMC2.0administrator can then add this MCU to the SMC2.0.

4.16 Detailed Reports and StatisticsThe SMC2.0 provides conference reports, device reports, alarm reports, return on investment(ROI) reports, and call detail record (CDR) statistics.

Basic ReportsOn the SMC2.0, users can set different conditions to display conferencing reports. Forexample, conferencing information can be displayed by scheduling source, billing code, or



30

organization. In addition, the SMC2.0 supports reports of other types, such as device usage,alarm, and return on investment reports.

The following lists basic SMC2.0 reports:l Conferencing reports

– Conference statistics report– Statistics report based on scheduling sources– Statistics report based on billing codes– Statistics report based on organizations– Statistics report based on conference participants

l Device reports– Device statistics report– Participant's conferencing report– Participant usage report– MCU usage report– RSE usage report

l Alarm reportl Return on investment report

Figure 4-6 Return on investment

Exported reports can be directly printed or saved as Excel or PDF files.

CDR

When creating a conference template, you can set a billing code. After a conference ends, theSMC2.0 records conference information statistics based on the billing code and generates acall detail record (CDR) for third-party billing.

The SMC2.0 supports the following types of CDRs:

l Multipoint CDR



31

Includes Conference Name, Participant Name, Endpoint Details, Device type,Calling Participant Type, Call Rate, Call Start Time, Call End Time, Billing Code,Conference ID, and Conference Scheduler. For details, see Figure 4-7.

l Point-to-point CDRIncludes Caller Label, Calling Protocol, Called Label, Called Protocol, CallBandwidth, Call Start Time, and Call End Time. For details, see Figure 4-8.

Exported CDRs can be directly opened or saved as .cvs files.

Figure 4-7 Multipoint CDR

Figure 4-8 Point-to-point CDR

4.17 Flexible Permission ControlPermission on the SMC2.0 includes organization permission and user permission.

Organization Permission

The functions of the SMC2.0 are based on organizations. Each organization providescomprehensive services, including user rights, MCUs, participants, conference templates,conference scheduling, conference control, as well as statistics and reports.

l Users are managed based on organizations:– A user can log in to the system only after the user has been added to an

organization.– When a user is added to multiple organizations, the user rights may vary with the

organizations.– When the rights of a lower-level organization node are not specified, the node

inherits the rights of its upper-level organization.l Endpoints are managed based on organizations. An organization can have multiple

endpoints, and an endpoint can belong to multiple organizations.l Conferences are managed based on organizations.



32

User Permission

The SMC2.0 provides three default user types: system administrator, conferenceadministrator, and conference operator. These default user types cannot be modified ordeleted. Users can define user types of their own.

Users can control participants, MCUs, conference templates, and conferences at the currentorganizational level and below.

l System administrator:Has all administrator rights, including management of devices (participants, MCUs, SCs,recording servers, and converged gateways), conferences, and system settings.

l Conference administrator:Has administrator rights for the own organization, including management of devices(participants and MCUs) and conferences.

l Conference operator:Has participant query and conference template operation rights for its own organization.

l Customized user type:Has all administrator rights, including management of devices (participants, MCUs, SCs,recording servers, and converged gateways), users, organizations, conferences, third-party interfaces, and system settings.

4.18 Corporate DirectoryAfter EUA server is deployed, its information can be synchronized with the SMC2.0 and ADserver. When a conference is being held on the SMC2.0, participants in the corporatedirectory can be directly selected to join the conference.

The EUA uses the Lightweight Directory Access Protocol (LDAP) to provide address bookservices. The EUA server is co-installed with the SC or SMC2.0 and is managed by theSMC2.0, and EUA support connect with AD and TMS.

The SMC2.0 can synchronize the following information from the corporate directory:

l User information: information that is generated when a user is added, deleted, ormodified or when a user's relationship is modified

l Organization information: information that is generated when an organization is added,deleted, or modified

l Participant information: information that is generated when a participant is added ordeleted, when the relationship of a participant is modified, or when participantparameters (participant number, participant URI, IP address, participant name, orprotocol) are modified

l Ad hoc conference information: information that is generated when an ad hoc conferenceis added or deleted or when parameters (conference access number or conference name)of an ad hoc conference are modified

4.19 Intuitive Topology ManagementA topology intuitively shows the location of devices on a network. Users can add and editmulti-level topologies on the SMC2.0.



33

For a topology, users can add, delete, modify, enlarge, and shrink a map, customize thebackground image, set device locations, and view alarms and call status of devices. Figure4-9 shows a topology.

Figure 4-9 Topology

l Alarm status: If a device icon is red, an alarm is generated on the device.l Device status: Different icons are displayed to signify the device status (online,

disconnected, calling, or offline).l Device information: To view details about a device, click its name on the topology.

4.20 Allocating Virtual PortsIn an operation environment, a carrier can use the virtual port allocation function provided bythe SMC2.0 to allocate devices' port resources to different enterprises to lease the ports to theenterprises.

When an MCU is used to hold a video conference, the MCU automatically allocates a port toeach participant for the participant to connect to the conference. Virtual ports are a series ofports predefined on the SMC2.0, used to limit MCU resources that can be used byconferences initiated from each organization.

Figure 4-10 shows how virtual ports are allocated by organization. If the virtual port quantityis configured for an organization, the number of ports used by the organization and itschildren organizations cannot exceed this value.



34

Figure 4-10 Allocating virtual ports by organization

Description:

1. Enterprise 1 (100 ports)

– The number of ports concurrently used by enterprise 1 and its childrenorganizations cannot exceed 100.

– The number of ports used by enterprise 1's headquarter and branch 1 cannot exceed80, respectively.

– The number of ports used by branch 2 cannot exceed 100.

2. Medical customer group (with no port limit is specified)

– The number of ports concurrently used by the medical customer group and itschildren organizations is not limited.

– The number of ports used by medical customer group 1 cannot exceed 30.

– The number of ports used by medical customer group 2 cannot exceed 20.

4.21 Comprehensive SC Management MechanismFrom the SMC2.0 web interface, Switch Centers (SCs) can be configured, monitored, andmaintained intuitively.

SCs come in two forms:

l Embedded SC: This type of SC is integrated into the SMC2.0 and provides mediaswitching and network control.

l Standalone SC: This type of SC independently runs in Linux and provides mediaswitching and network control.

Users can find the following information about SCs on the SMC2.0: logs, alarms, zones,member rules, number conversion rules, search rules, network address books, bandwidthmanagement, and route control. Users can also modify SC settings on the SMC2.0.



35

4.21.1 Zone ManagementA zone is a geographically or virtually defined unit. Switch Center (SC) services areimplemented by zone.

BackgroundZones are divided into local zones and neighboring zones.l Local zone: a zone that is created to restrict communication between nodes (including

endpoints, MCUs, and gateways) registered with the local SC.l Neighboring zone: a zone that is created to restrict communication between nodes

(including endpoints, MCUs, and gateways) registered with a remote SC.

Zone DivisionAfter zone division is implemented, the following videoconferencing services can bemanaged by zone: node registration, node calling, bandwidth allocation, and call bandwidthcontrol. Figure 4-11 shows a zone division example.

Figure 4-11 Zone division



36

Table 4-5 describes the zone division example.

Table 4-5 Zone division description

Zone Prefix

Zone A 0755

Zone B 0512

Zone C 025

NOTEA zone prefix is similar to a zone ID. The SMC2.0 finds the corresponding zone for registration andcalling services based on zone prefixes.

Zone Member RulesA member rule is used to define criteria for matching a zone. Available matching modes are:l Prefixl Suffixl Addressl Regular expression

4.21.2 Registration ControlYou can define local management domains, blacklist and whitelist to realize registrationcontrol and management.

Local Management DomainsWhen the SMC2.0 manages multiple SCs, the administrator may not be able to determine theSC with which each device must register. If the administrator adds local management domainsfor SCs, the SMC2.0 will match a device with a management domain based on the device'salias and determine the SC with which each device must register. Figure 4-12 shows theworking principle of local management domains.



37

Figure 4-12 Working principle of local management domains

l If no local management domain is defined for an SC, this SC allows registrations from

all devices.l After a local management domain is defined for an SC, this SC allows registrations from

only devices covered by the domain. Multiple local management domains can be definedfor one SC.

Blacklist And Whitelistl When SC registration jurisdiction control for white list, then in any login request alias

has one to satisfy the white list the scope, SC accepts this login request. Otherdissatisfied white list scope login request will be rejected.

l When SC registration jurisdiction control for blacklist, then in any login request alias hasone to satisfy the blacklist the scope, SC rejects this login request. Other dissatisfiedblacklist scope login request will be accepted.

4.21.3 Call ControlSwitch Centers (SCs) controls calls based on number conversion and search rules.

BackgroundAn SC performs the following steps to control calls:

1. With the number conversion and search rules, the SC finds the zone where the calledparty is located.

2. The SC determines the restricted applications based on the location information of thecalling and called parties.

Number ConversionWith a number conversion rule, the SMC2.0 converts numbers that match the specified aliasesbased on that rule, facilitating number searching.



38

Search RuleA search rule helps an SC identify the zone to which a called party belongs.

4.21.4 Bandwidth ManagementYou can configure the inter-zone bandwidth to limit the bandwidth between two zones,achieving flexible call bandwidth management.

The inter-zone bandwidth management rule is used to limit the single call and total callbandwidth between any two zones of the SC. When devices in two zones configured with aninter-zone bandwidth management rule call each other, the SC checks the call, anddisconnects the call that exceeds the specified bandwidth limit.

NOTEThe embedded SC and standalone SC support a maximum of 200 and 1000 bandwidth management rulesrespectively.

Different bandwidth management rules between different zones make differentiated callmanagement possible.

Table 4-6 Example bandwidth

Zone Device Quantity Bandwidth (Mbit/s)

A 30 100

B 28 100

C 5 50

According to Table 4-6:

l Zones A and B support a high bandwidth but contain many devices. You can set the totalbandwidth between zone A and zone B to 100 Mbit/s, and set the single call bandwidthto 5 Mbit/s. This prevents the failure to set up calls due to the excessive bandwidth usageof a single call.

l Zone C supports a low bandwidth and contains few devices. You must set the totalbandwidth between zone A and zone C to 50 Mbit/s. The single call bandwidth can beset to 10 Mbit/s.

4.21.5 Route restrictionThe media route function enables the SC to forward media (video and audio) data betweentwo nodes that cannot exchange data.

If two nodes registering with the same SC belong to two different zones and the two zonescannot exchange data with each other due to network disconnection or firewall isolation, youcan configure the media route between the two zones so that the SC can forward media datafor them, as shown in Figure 4-13.



39

NOTE

l The embedded SC supports a maximum of 60 Mbit/s media route bandwidth.

l The standalone SC supports a maximum of 300 Mbit/s media route bandwidth.

Figure 4-13 Route restriction



40

5 Reliability

The SMC2.0 adopts multiple backup mechanisms so services of a network carrier are notinterrupted by the failure of any single device.

The SMC2.0 adopts hierarchical backup mechanisms to achieve high reliability.

l Cluster

The SMC2.0 supports cluster deployment. When the active server is faulty, all servicesare automatically switched to the standby server without interrupting the ongoingconferences.

l SC backup

The SMC2.0 supports SC backup. When the active SC is faulty, all services areautomatically switched to the standby SC to ensure reliable communications.

Figure 5-1 Cluster and SC backup

l MCU backup

HUAWEI SMC2.0Product Overview 5 Reliability


41

If an MCU fails, the SMC2.0 automatically switches services to an available MCU in thesame or standby service area. This helps ensure that conferences run smoothly.

l Device configuration backupOn the SMC2.0, users can back up the current configuration of a manageable device tothe server and restore the device to the backup configuration when required.

HUAWEI SMC2.0Product Overview 5 Reliability


42

6 Unparalleled Security

The SMC2.0 takes security measures at the application, system, network, and managementlayers, better securing user services.

Application LayerAt the application layer, the security solution protects SMC2.0 applications using thefollowing measures:l The authentication method SHA256 Salt, a Secure Hash Algorithm (SHA) is used to

ensure the security of the user login passwordl If a user enters an incorrect password for three consecutive times, a graphical verification

code is required for the fourth login attempt. By default, after entering an incorrectpassword for ten consecutive times, the user is locked out and must be unlocked by ahigher-level administrator.

l Prompts users to change their passwords after the administrator resets the passwords.l Enforces password complexity.l Uses SHA256 Salt, to encrypt passwords before saving them to the database.l Provides HTTPS for enhanced data transmission security. The SMC2.0 uses HTTPS for

functions with high security requirements. For example, HTTPS is used during passwordchange to prevent the current and new passwords from being transmitted in plaintext.

l Allows access to the database in only Windows authentication mode.l Provides comprehensive logging to record and track user operations.

System LayerThe security solution at the system layer protects the operating system, database, and servicesrequired for application running.l Provides the security hardening policy file for the operating system, closes unused

Windows services, enables the firewall, and enables the minimum ports.l Uses the OfficeScan antivirus software to protect Windows from malware, viruses,

spyware, web-based attacks, and blended threats.

Network Layerl Implements security on routers and switches, helping ensure transmission security for the

SMC2.0 database.

HUAWEI SMC2.0Product Overview 6 Unparalleled Security


43

l Uses firewalls for security check, preventing the SMC2.0 from being attacked bymalware.

Management LayerThe security solution at the management layer implements logging and patch installation toensure that the SMC2.0 runs properly.

HUAWEI SMC2.0Product Overview 6 Unparalleled Security


44

7 Openness

The SMC2.0 provides a SOAP-based third-party interface for developers to query and controlthe conferences on the SMC2.0.

The third-party interface of the SMC2.0 supports SOAP 1.1, SOAP 1.2, HTTP access, andHTTPS access. The interface uses the session management mode that is compatible withASP.NET.

To use this interface, third-party developers need to purchase a license of the SMC2.0, enablethe third-party interface function, and add their user accounts.

HUAWEI SMC2.0Product Overview 7 Openness


45

8 Operation and Maintenance

This topic describes the operation and maintenance of SMC2.0

HUAWEI SMC2.0Product Overview 8 Operation and Maintenance


46

8.1 Web InterfaceThe SMC2.0 supports conference scheduling and control from its web interface, andconcurrent logins by 100 users.

After logging in to the web interface, a user can view the system running information, such asalarms and the CPU and memory usage rates of the SMC2.0 server. On the home page, a usercan access the participant list and MCU list, process alarms, and solve system issues.

Figure 8-1 Home page

Table 8-1 lists the functions on the SMC2.0 web interface.

Table 8-1 Functions on the web interface

Function Description

Conference management Users can manage conferences and conference templates.They can:l Create a conference.l Add, edit, and delete a conference template.l Initiate a conference using a conference template.l Edit or cancel a scheduled conference.l Control an ongoing conference.l View the conference history and save a conference as a

conference template.



47

Function Description

Device management Users can manage devices including participants, MCUs, SCs,corporate directory servers, remote SMCs, and recordingservers. They can:l Add, edit, and delete a device.l Modify connection parameters.l Manage the organizations that a device belongs to.l Change the management mode of a device.l Add, edit, and delete a device configuration template.l Automatically detect devices and add them to the SMC2.0.l Predefine participants.l Manage device software versions and remotely upgrade

devices.l Backup and restore the configuration of a manageable

device.l Query and unregister endpoints on the GK.l Add voice gateways to or remove gateways from the GK.l Inspect devices.

Report management Users can view the reports on the SMC2.0 and export a reportin a specific format.

My tasks Users with different administrative rights can process tasksthat they initiate and pending tasks for them on the My Taskspage. They can also view task progress and details as well asdelete and suspend tasks. The tasks are classified intoconference convening tasks, interconnection request tasks,device inspection tasks, batch participant import tasks,corporate directory synchronization tasks.

System management Users can query or configure the SMC2.0 system settings,logs, and alarms. They can:l Set system parameters.l Add, edit, and delete an organization.l Add, edit, and delete a user type.l Add, edit, delete, and manage the users in an organization.l View logs and alarms.

License management Users can view, import, or invalidate licenses.

8.2 Logs and AlarmsThis topic describes logs and alarms on the SMC2.0 web interface.



48

LogsUsers can view logs on the SMC2.0 web interface. The SMC2.0 logs the followinginformation:

l System alarmsl Web user logins and logoutsl Conference operationsl Conference scheduling operationsl Videoconference endpoints in conferencesl Device trap alarmsl Operations of adding, editing, and deleting devices

Figure 8-2 Logs

AlarmsOn the SMC2.0 web interface, users can view alarms and customize severities andnotification modes for alarms in each scenario.

l Viewing alarmsWhile viewing alarms, users can acknowledge or clear ongoing alarms.

Figure 8-3 Viewing alarms

l Setting alarms

The SMC2.0 has typical alarm scenarios. You can set the severity, notification methods,and alarm sound for alarms in these scenarios.

Figure 8-4 Setting alarms



49

8.3 Device UpgradesFrom the SMC2.0, users can upgrade manageable Huawei devices.

The following devices can be upgraded from the SMC2.0:l VP9600 series MCUsl ViewPoint 8600 series MCUsl ViewPoint 9000 series videoconferencing endpointsl TEX0 series videoconferencing endpointsl TX50 videoconferencing endpointl DP300 videoconferencing endpointl TP3100 series telepresence systemsl TP1100 series telepresence systemsl Switch Centers (SCs)Before upgrading a device, a user needs to upload the version file to the SMC2.0. TheSMC2.0 can then remotely upgrade the device. Batch upgrades are also supported.

8.4 Device InspectionThe SMC2.0 supports inspection for manageable devices.

The inspection is available to the following devices:l SMC2.0l SC: embedded SC and standalone SCl MCU: VP9000 series MCUs (VP9630, VP9650, and VP9660)l Endpoint: TE series endpoints (TE30, TE40, TE50, and TE60), TX50, and DP300

To inspect a device inspection, download the inspection template, modify the inspection itemsas required, upload the saved file to the SMC2.0, and start the inspect.



50

9 Technical Specification

This topic describes environmental specifications, performance and standards compliance ofSMC2.0.

HUAWEI SMC2.0Product Overview 9 Technical Specification


51

9.1 Environmental specificationsThis topic describes environmental specifications of SMC2.0.

Table 9-1 describes its environmental specifications.

Table 9-1 Environmental specifications

Item Specifications

Dimensions (H × W ×D)

87.3 mm x 447 mm x 760 mm

Weight in fullconfiguration

24kg

Rated input voltage 100 V AC to 120 V AC or 200V AC to 240 V AC

Temperature Operating temperature: 10°C to 35°CStorage temperature: -40°C to +65°CThe temperature change rate is smaller than 20°C/h.

Pressure The maximum altitude is 3000 m (9842.40 ft). The operatingtemperature decreases by 1°C/300 m (1.8°F/984.24 ft) when thealtitude is higher than 900 m (2952.72 ft).

Humidity Operating humidity: 8% to 85% RH (non-condensing)Storage humidity: 5% to 95% RH (non-condensing)The humidity change rate is smaller than 20% RH/h.

9.2 Performance and CapacityThis topic describes the performance and capacity of the SMC2.0.

Table 9-2 lists the performance and capacity specifications of the SMC2.0.

Table 9-2 Performance and capacity specifications

Type Item Indicator

Device Maximum number ofmanageable users

500

Maximum concurrent loginusers

100

Maximum number ofmanageable SCs

50

Maximum number ofmanageable MCUs

128



52

Type Item Indicator

Maximum number ofmanageable recording servers

128

Maximum number ofunmanageable participants

5000

Maximum number ofmanageable and unmanageableparticipants

l Preinstallation: 10000l Onsite installation: 100

Conference Maximum number ofparticipants in a conference


Maximum number ofmanageable conferencetemplates

1000

Maximum number of scheduledconferences

10000

Maximum number of activeparticipants

5000

Maximum number ofparticipants in a scheduledconference


SMCinterconnection

Maximum number of SMCs thatcan be connected


SC Embedded SC l Maximum number of registerednodes: 1000

l Maximum number of calls: 1000l Maximum media traversal bandwidth:

60 Mbit/s

Standalone SC l Maximum number of registerednodes: 6000

l Maximum number of calls: 4000(1000 routing calls + 3000 non-routingcalls)

l Maximum media traversal bandwidth:– Preinstallation: 300 Mbit/s (support

for a maximum of 1000 calls)– Onsite installation: 120 Mbit/s

(support for a maximum of 120calls)

Topologyview

Maximum number of supportedtopology levels

4



53

Type Item Indicator

Maximum number of subtopologies allowed for atopology

20

Maximum number of supportedtopologies

100

Maximum number of devicesallowed in a topology

100

Co-installationof the EUAand SC

Number of VC participants bythe Standalone SC

> 1000

Number of users supported bythe EUA

1000 to 6000

Maximum number of concurrentconnections to the EUA

20

Co-installationof theSMC2.0,SC, andEUA

Number of VC participants bythe Embedded SC

<1000


0 to 1000


10

Co-installationof theSMC2.0,SC, EUA,and eMP

Number of VC participants bythe Embedded SC

< 100


0 to 1000


10

Number of UC participants bythe Embedded SC

< 3000

NOTEThe following indicators are limited by the license:

l Maximum number of manageable users

l Maximum number of manageable devices (SC, MCU, participant, and recording server)

l Maximum number of nodes that can be registered with the embedded SC (including Huaweisoftware clients and non-Huawei software clients)

l Media traversal bandwidth

9.3 Standards ComplianceThis topic describes the standards compliance of SMC2.0.



54

Table 9-3 lists the standards that the SMC2.0 complies with.

Table 9-3 Standards compliance

Item Standard

Control signaling l ITU-T H.235l ITU-T H.245l ITU-T H.450.1l ITU-T Q.931l ITU-T X.224l YD/T 936-1997l E.164

RFC l RFC793l RFC791l RFC2273l RFC2578l RFC2579l RFC2580l RFC1321

HTTP l RFC1945l RFC2616l RFC2818

SOAP l W3 SOAP 1.2l W3 SOAP 1.1l W3 WSDL 1.1

SNMP l RFC 1065-1067, RFC1155-1157, RFC1214l RFC1441-1452, RFC1901-1910l RFC3411-3418

SSH RFC4250-4256, RFC4335, RFC4344, RFC4345

SHA FIPS



55

10 Acronyms and Abbreviations

Acronym orAbbreviation

Full Name

AD Active Directory

CDR Call Detail Record

CPU Central Processing Unit

DMZ Demilitarized Zone

SC Switch Center

GK Gatekeeper

HTTP Hypertext Transfer Protocol

HTTPS Hypertext Transfer Protocol Secure

ISDN Integrated Services Digital Network

IVR Interactive Voice Response

LDAP Lightweight Directory Access Protocol

MCU Multipoint Control Unit

OA Office Automation

SIP Session Initiation Protocol

SMC2.0 Service Management Center

SOAP Simple Object Access Protocol

XML Extensible Markup Language

RSE Recording & Streaming Engine

HUAWEI SMC2.0Product Overview 10 Acronyms and Abbreviations


56

Product Overview - Icecat

Documents