Professional Documents
Culture Documents
0
V500R002C00
Configuration Guide
Issue 05
Date 2016-09-30
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 respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase 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 or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://e.huawei.com
Purpose
This document helps engineers implement configuration on the SMC2.0, by providing
preparations, procedures, and precautions for zone, basic, service, and typical networking
configuration.
Intended Audience
This document is intended for:
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Symbol Description
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue 05 (2016-09-30)
This issue is used for fifth office application (FOA).
Issue 04 (2016-08-15)
This issue is used for forth office application (FOA).
Issue 03 (2016-05-23)
This issue is used for third office application (FOA).
Issue 02 (2016-02-28)
This issue is used for second office application (FOA).
Issue 01 (2015-12-15)
This issue is used for first office application (FOA).
Contents
2 Configuration Preparation...........................................................................................................5
2.1 Checking for Prerequisites..............................................................................................................................................6
2.2 Preparing Configuration Tools....................................................................................................................................... 8
3 Area Planning...............................................................................................................................10
3.1 What's Zone.................................................................................................................................................................. 11
3.2 Adding a Zone.............................................................................................................................................................. 15
3.3 Adding a Member Rule................................................................................................................................................ 17
3.4 Adding a Service Area..................................................................................................................................................20
4 Configuring SC............................................................................................................................ 24
4.1 Adding a Standalone SC...............................................................................................................................................24
4.2 Configuring External Authentication for Standalone and Built-in SCs....................................................................... 25
4.3 Configuring a Standalone/Embedded SC..................................................................................................................... 31
4.3.1 Configuring a Local Management Domain............................................................................................................... 32
4.3.2 Configuring a Neighboring Zone.............................................................................................................................. 33
4.3.3 Configuring a Search Rule........................................................................................................................................ 37
4.3.4 Configuring a Number Conversion Rule...................................................................................................................40
4.3.5 Configuring the Inter-Zone Bandwidth..................................................................................................................... 42
4.3.6 Configuring the Network Address Book................................................................................................................... 45
4.3.7 Configuring the Media Route.................................................................................................................................... 49
5 Basic Settings................................................................................................................................51
5.1 Setting a Device Configuration Template.....................................................................................................................52
5.2 Configuring a Participant..............................................................................................................................................54
5.2.1 Determining the Adding Method...............................................................................................................................54
5.2.2 Predefining a Participant........................................................................................................................................... 55
6 Service Configuration...............................................................................................................100
6.1 Configuring the Corporate Directory Server.............................................................................................................. 101
6.2 Configuring Device Updates...................................................................................................................................... 104
6.3 Configuring a Topology..............................................................................................................................................107
6.4 Configuring the Range Setting Policy........................................................................................................................ 108
6.4.1 Old Rate Adaptation Rules...................................................................................................................................... 109
6.4.2 New Rate Adaptation Rules.....................................................................................................................................110
6.5 Configuring the NlogV2 Alarm Function...................................................................................................................112
6.6 Configuring the Service Alarm Function....................................................................................................................113
6.7 Configuring Email Notifications................................................................................................................................ 114
6.8 Configuring SMS Notifications.................................................................................................................................. 116
6.9 Configuring LDAP Settings........................................................................................................................................119
6.10 Configuring External User Login............................................................................................................................. 121
6.10.1 Configuring Default Rights................................................................................................................................... 121
6.10.2 Configuring AD User Login..................................................................................................................................122
6.10.3 Configuring CAS SSO User Login....................................................................................................................... 126
6.10.4 Adding External Users...........................................................................................................................................128
6.11 Synchronizing the Clock Source...............................................................................................................................129
8 Troubleshooting........................................................................................................................ 166
8.1 Failure to Log In to the SC......................................................................................................................................... 167
8.2 MCU Displayed as Offline on the SMC2.0................................................................................................................167
8.3 Failure to Register a Participant with a GK................................................................................................................168
8.4 Failure to Search for an MCU.................................................................................................................................... 170
8.5 Failure to Search for a Videoconferencing Participant...............................................................................................171
8.6 Failure to Search for a Telepresence Participant........................................................................................................ 172
8.7 Failure to Search for a Recording Server................................................................................................................... 173
8.8 "Test failed" Is Displayed During a Test of the Directory Service Configuration..................................................... 174
8.9 HTTP Error Occurs During Your Login to the SMC2.0............................................................................................ 175
8.10 Display Issue on the SMC2.0 Web Interface............................................................................................................176
8.11 "Message sending timed out" Is Displayed During an Attempt to Add a Participant.............................................. 178
1 Configuration Overview
Participant
Participants are SD endpoints, HD endpoints, voice endpoints, software clients, and
telepresence endpoints that can be added to the SMC2.0.
Manageable/Unmanageable
Participants and MCUs can be added to the SMC2.0 as manageable or unmanageable. The
model and software version of a participant or an MCU decide whether the participant or
MCU is manageable or not.
l Manageable: Devices of this type support online configuration, updates, backup, and
configuration restoration, and are able to report alarms to the SMC2.0.
l Unmanageable: Devices of this type are resources for conference scheduling but do not
support online configuration, updates, backup, or configuration restoration.
Auto Detect
Auto detect is one of the methods for adding a device. Manageable participants and MCUs
can be added using this method. Once connected to the network, they automatically report
their address information to the SMC2.0. As an SMC2.0 administrator, you can then obtain
the list of devices that are connected to but not added to the SMC2.0, and add a desired device
to the SMC2.0, without knowing the device IP addresses.
Calling/Called Node
l Calling node: party that initiates a call.
l Called node: party that receives a call.
In a video conference, calling and called nodes can be endpoints or MCUs of various types.
HUAWEI SMC2.0 Comes with the SMC2.0 software and provides help information
V500R002C00 Online about parameters and operations on SMC2.0.
Help
1.5 Precautions
Keep the following precautions in mind to avoid system exceptions while performing
configuration:
l Do not delete databases without the database administrator's permission.
l Back up files before you modify and delete any of them.
l Change the administrator password at your first login to the SMC2.0, and keep the new
password. Periodically change the password. For more details, see the Quick Start Guide.
l Do not modify the hardware settings of the SMC2.0 server, for example, a parameter for
specifying whether to enable or disable the network adapter. Otherwise, the equipment
serial number (ESN) in the license file is inconsistent with the server ESN.
l Back up database information periodically.
2 Configuration Preparation
This chapter describes how to prepare for the SMC2.0 configuration, including checking
preconditions and obtaining tools.
Version Number
Log in to the SMC2.0 web interface. Choose Help > Version and confirm that the SMC2.0
version number meet the site requirements.
If the version number is inconsistent, follow the instructions in the Upgrade Guide to upgrade
the SMC2.0.
NOTE
Unless otherwise specified, the system administrator account is used to log in to the SMC2.0 web interface in
this document.
No. Service
8 PGSQL
If any of the preceding services have not started, right-click those services and choose
Start from the displayed shortcut menu.
l SMC2.0 services
On the SMC2.0 server, choose Start > Administrative Tools > Server Manager >
Configuration > Services. Then, check whether the services listed in Table 2-2 have
started.
If any of the preceding services have not started, right-click those services and choose
Start from the displayed shortcut menu.
l SMC2.0 Web Sites
On the SMC2.0 server, choose Start > Administrative Tools > Server Manager >
Roles > Web Server (IIS) > Internet Information (IIS) Manager > Sites, as shown in
Figure 2-1.
Figure 2-1 Checking the operating status of the SMC2.0 Web Sites
License Status
Log in to the SMC2.0 web interface. Choose Help > License and confirm that License status
is normal. If the status is abnormal, contact Huawei technical support engineers.
Server Peripherals
As only one RH2285 V2 server is delivered in the SMC2.0 package, you need to prepare the
peripherals listed in Table 2-3 for the configuration.
SSH Client
When you are adding MCUs to the SMC2.0, some MCU parameters must be set from the
command-line interface (CLI). In this case, you need an SSH client to access the CLI. As SSH
command components create an encrypted channel between the application layer and client,
using an SSH client to log in to MCUs improves data security.
3 Area Planning
Zone
As a logic entity, a zone can be a geographic location or virtual division. In Figure 3-1, zone
B and zone C are geographic locations, while zone A is a virtual division.
l defaultEPZone: If a node registered with the local SC does not match any zone based on
the member rules, this node is allocated to the defaultEPZone.
l defaultZone: During a call, if a calling or called node is not allocated to any zone of the
local SC, this node is allocated to the defaultZone.
Service Area
Device resources managed by the SMC2.0 include MCUs and recording servers. To better use
those resources, you can define the area, so called service area, serviced by each MCU and
recording server.
Through service area management, videoconferencing users in a service area have the
precedence in using the device resources in this service area. Each device belongs to one
service area. Figure 3-2 shows a service area management model.
You can create service areas based on the geographic locations covered by the
videoconferencing service and following rules:
l Create a service area centered on the area where videoconferencing users and MCUs are
concentrated.
l To reduce costs associated with long-distance calls, it is recommended that the zones in a
service area be adjacent.
l Assign at least one MCU to each service area.
Follow the following steps when defining service areas and allocating device resources:
You can configure backup service areas when the SMC2.0 manages multiple service areas.
Multiple backup service areas can be bound to a main service area. If device resources are
insufficient in the main service area, the SMC2.0 automatically uses resources in the backup
service areas to schedule conferences. You can set the priorities of the backup service areas to
specify the order of using the device resources in those backup service areas.
Service areas are used as follows:
l If a service area prefix is specified for an MCU or recording server, the MCU or
recording server is a resource of the service area, as shown in Figure 3-8.
l The number of a videoconferencing participant determines whether the participant
belongs to a service area. Each participant number starts with a prefix, and the
participant belongs to the service area with the same prefix.
l When the SMC2.0 is used to schedule a conference, the following rules apply:
– If you select Auto for Active MCU when scheduling a conference, the SMC2.0
behaves as follows: If conference participants belong to the same service area, the
SMC2.0 assigns the MCU in the service area to host the conference. If conference
participants belong to different service areas, the SMC2.0 determines the master
MCU and starts a cascaded conference.
– If a conference supports recording or live broadcast and you select Auto for
Recording server, the SMC2.0 assigns the recording server in the service area
where the master MCU belongs for the conference.
NOTE
l To facilitate unified management of registration, calling, and resource allocation services on the
SMC2.0, it is recommended that service area planning on the SMC2.0 be consistent with that on the
SC.
l If the numbers of device registrations and calls supported by the SMC2.0's embedded SC do not
meet requirements for large video conferences, you can add standalone SCs to the SMC2.0.
City B1 0755
Province B
City B2 0756
City C1 0512
Province C
City C2 0519
NOTICE
A prefix cannot be the same as or start with an existing unified access number, conference
special service number, or unified recording number.
In 3.2 Adding a Zone, 3.3 Adding a Member Rule, and 3.4 Adding a Service Area, city A1
of province A with settings in Table 3-1 is used as an example.
Step 2 Choose Devices > Switch Centers and click the name of the embedded SC.
Zone type Type of the zone to add. The options are as If you are adding a zone
follows: on the local SC, select
l Endpoint zone: zone on the local SC, used Endpoint zone.
to manage all nodes registered with the
local SC.
l Neighbor zone: zone on a remote SC, used
to manage the communication between
nodes registered with the local SC and
nodes registered with the remote SC. For
the SMC2.0's embedded SC, you can set
the neighboring zone to a zone on one of
the standalone SCs that have been added to
the SMC2.0.
l Gateway zone: a special neighboring zone
whose call requests are directly sent
without being parsed by the local and
neighboring SCs.
l Traversal-server zone: zone on a remote
SC, located outside a firewall and working
with the cross-client zone inside the
firewall to implement firewall traversal for
media streams.
l Traversal-client zone: zone on a remote
SC, located inside a firewall and working
with the cross-client zone outside the
firewall to implement firewall traversal for
media streams.
Name Name of the zone to identify it on the SC. The name must be unique
on the same SC.
Example: A
Server IP Address of the media proxy that sets up Default value: Auto
address sessions between two devices registered with You can use the default
the SC. value or enter a value.
Restrict total Whether to limit the total bandwidth. The total This parameter is not
bandwidth bandwidth indicates the sum of the selected by default.
bandwidths for calls between nodes within a
zone and between nodes in different zones at a
specific point in time.
Restrict each Whether to limit the bandwidth for a single This parameter is not
incoming call between nodes in different zones. selected by default.
call's
bandwidth
Restrict each Whether to limit the bandwidth for a single This parameter is not
internal call's call between nodes in the same zone. selected by default.
bandwidth
Internal call Bandwidth for a single call between nodes in Value range:
bandwidth the same zone. 1-100000000
limit (kbit/s) Default value: 1920
Require Policy used for authenticating nodes before This parameter is selected
authenticatio they register with the SC. by default.
n If you select this parameter, nodes to which
the SMC2.0 has allocated numbers (number-
allocated nodes) must pass the authentication
before they register with the SC, while
dynamic nodes can directly register with the
SC.
Enable If media routing is enabled, the SC performs Set this parameter based
media route media forwarding for all calls in the zone, as on the site requirements.
well as incoming and outgoing calls.
----End
Step 2 Choose Devices > Switch Centers and click the name of the embedded SC.
Rule name Name of the rule to identify it on the The name must be unique on the
SC. same SC.
Example: A1
Enable Whether to apply the rule to the SC. This parameter is selected by
default.
Registration Zone to which the node that Set this parameter based on the site
zone conforms to the rule belongs. requirements. One zone can have
multiple member rules.
Example: A
NOTE
The drop-down list box can display a
maximum of 30 zone names. You can
enter a keyword to search for required
zone information.
IP address Whether to match the rule by IP Set this parameter based on the site
match address. requirements.
Example: Do not select this
parameter.
Start IP Start and end IP addresses for IP Enter the start and end IP addresses
address address matching. of the zone corresponding to the
rule. The start and end IP addresses
End IP must of the same type, and the end
address IP address cannot be smaller than
the start IP address.
Alias match Whether to match the rule by alias. Set this parameter based on the site
requirements.
This parameter is not selected by
default.
Match type Type used for matching the rule. Set this parameter based on the site
Available options are: requirements.
l Exact match Example: Prefix match
l Prefix match
l Suffix match
l Regular expression match
NOTE
A regular expression is a sequence of
characters that forms a search pattern,
mainly for use in pattern matching with
strings.
Matching Content used for matching the rule, The type of value entered varies
Criteria which can be a number, alias, URI, according to the settings of Match
or regular expression. type.
l Exact match: Enter a string of
characters. For a node to match
the rule, the node's alias must
exactly match the entered string.
l Prefix match: Enter a string of
digits. The SMC2.0 searches for
matching rules by starting from
the first digit.
l Suffix match: Enter a string of
URI characters. The SMC2.0
searches for matching rules by
starting from the first character
following at (@).
l Regular expression match:
Enter a string of regular
expression. For example, to
search for aliases that start with
abc, enter abc(.*).
Example: 025
----End
Step 2 Choose System > Settings > Service Areas, click Add Service Area.
Step 3 Set the service area parameters described in Table 3-4. Then click Add.
Step 4 Select the new service area. On the center of the page, click Add Prefix.
Prefix name Name of the area prefix to identify it on the Example: Province A
SMC2.0. Multiple prefixes can be specified
for one service area.
Service area Number of the area prefix. Based on this Example: 025
prefix number, the SMC2.0 matches the service area
with device resources (MCUs and recording
servers) belonging to the service area.
----End
Before the configuration, add service area B by referring to Step 1 through Step 6 in Adding
a Service Area.
Step 1 Select service area A and click the Service Area Backup tab, as shown in Figure 3-9.
Step 2 Click Add and select B on the displayed page, as shown in Figure 3-10.
----End
4 Configuring SC
Procedure
Step 1 Log in to the SMC2.0 web interface.
Step 2 Choose Devices > Switch Centers and click Add.
Step 3 Enter the SC IP address in IP Address and click Next.
NOTE
Table 9-1 lists the authentication information when a standalone SC is added to the SMC2.0. For details
about how to change and maintain the connection password, see the Security Maintenance.
----End
l H.350: The SC requests the external server through H.350 to authenticate the device.
l LDAP: The SC requests the external server through LDAP to authenticate the device.
LDAP authentication is classified into domain account authentication and non-domain
account authentication.
a. Domain account authentication: If you want to authenticate a device through its
domain account, set the external authentication mode to this option.
b. Non-domain account authentication: If you want to authenticate a device through a
non-domain account, set the external authentication mode to this option.
You can configure the SC external authentication mode on the SMC2.0 web interface. The
following describes the procedure.
Procedure
Step 1 Log in to the SMC2.0 web interface.
Step 4 In External Authentication Mode, configure the SC external authentication mode, as shown
in Figure 4-2. Table 4-1 describes the parameters.
Server IP address Indicates the IP address of the Set this parameter to the actual IP
external device. address of the external device.
User name Indicates the user name used to Set this parameter to the actual H.
connect to the H.350 server when 350 server user name.
the SC uses the H.350
authentication mode.
Key Indicates the key used to connect Set this parameter to the actual H.
to the H.350 server when the SC 350 server key.
uses the H.350 authentication
mode.
Transmission Indicates the protocol used by the Set this parameter to LDAP or
protocol SC to communicate with the LDAPS based on the site
external device. requirements.
Default value: LDAPS NOTE
If this parameter is set to LDAPS,
click Import LDAP Certificate and
upload an LDAP certificate based on
the onscreen instruction.
Base DN Indicates the directory where Set this parameter to the actual
(distinguished authentication information is base DN of the external device.
name) stored on an external device. For example, if the authentication
After you set this parameter, the information for an external
SC can determine the device device is stored in
information at which location to cn=user00x,ou=users,o=exampl
be used during authentication. e,c=com, set this parameter to
cn=user00x,ou=users,o=exampl
e,c=com.
Server IP address Indicates the IP address of the Set this parameter to the actual IP
external device. address of the external device.
Transmission Indicates the protocol used by the Set this parameter to LDAP.
protocol SC to communicate with the
external device.
Default value: LDAPS
Server IP address Indicates the IP address of the Set this parameter to the actual IP
external device. address of the external device.
Transmission Indicates the protocol used by the Set this parameter to LDAP or
protocol SC to communicate with the LDAPS based on the site
external device. requirements.
Default value: LDAPS NOTE
If this parameter is set to LDAPS,
click Import LDAP Certificate and
upload an LDAP certificate based on
the onscreen instruction.
Base DN Indicates the directory where Set this parameter to the actual
(distinguished authentication information is base DN of the external device.
name) stored on an external device. For example, if the authentication
After you set this parameter, the information for an external
SC can determine the device device is stored in
information at which location to cn=user00x,ou=users,o=exampl
be used during authentication. e,c=com, set this parameter to
cn=user00x,ou=users,o=exampl
e,c=com.
Naming attribute Indicates the user name of the Set this parameter to the naming
external device server. attribute of the external device.
For example, if the naming
attribute of an external device is
cn, set this parameter to cn.
----End
Verification
Assume that a TE Desktop client uses domain account authentication to register with the SC.
The following describes how to verify the preceding configuration. Ensure that the following
conditions are met:
l The authentication mode for the SC has been set to domain account authentication on the
SMC2.0 web interface.
l A domain account and its password have been obtained. The account and password are
used for registering with the SC and logging in to the TE Desktop.
Step 1 Open TE Desktop and click Server Settings in the login window.
The registration server configuration window is displayed.
Step 2 On the Registration Server tab page, enter the server IP address and URI in Address and
SIP URI respectively, as shown in Figure 4-3.
Step 3 On the Advanced Settings tab page, set Transmission Type, as shown in Figure 4-4.
Step 9 Click the Registered Nodes tab on the page that is displayed.
If the authentication type is External, as shown in Figure 4-6, the domain account
authentication for the SC has been configured successfully.
----End
When the SMC2.0 manages multiple SCs, you may not be able to determine the SC with
which each device must register. If you add local management domains for SCs, the SMC2.0
will match a device with a management domain based on the device's alias and determine the
SC with which each device must register. Figure 4-7 shows the 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 defined
for one SC.
NOTE
After a standalone SC is added to the SMC2.0, add local management domains for all SCs (including the
embedded SC). This helps ensure that you are sure about the SC to register when adding a device.
Step 2 Choose Devices > Switch Centers and click the name of the desired SC.
Step 4 Set the local management domain parameters described in Table 4-5.
Name Name of the management domain to The name must be unique on the
identify it on the SC. same SC.
Example: A1
Matching Content used for matching the The type of value entered varies
criteria management domain. according to the settings of Type.
l Prefix: Enter a string of digits.
The SMC2.0 searches for
matching management domains
by starting from the first digit.
l Suffix: Enter a string of URI
characters. The SMC2.0
searches for matching rules by
starting from the first character
following at (@).
----End
As described in Table 3-1, Province B is a zone on SC1, while Province C is a zone on SC2.
The following procedure describes how to configure Province C as a neighboring zone on
SC1:
NOTE
Configuration of a neighboring zone is uni-directional. Therefore, after Province C is configured as a
neighboring zone on SC1, SC1 can identify Province C as its neighboring zone, but SC2 cannot identify
Province B as its neighboring zone. To enable SC2 to identify Province B as its neighboring zone, add
Province B as a neighboring zone on SC2. To ensure calls are set up successfully, configure neighboring
zones on both SCs.
Step 2 Choose Devices > Switch Centers and click the name of SC1.
Name Name of the zone to identify it on the SC. The name must be
unique on the same SC.
To help identify the
zone, specify the zone
directivity in the name.
Example: SC2_C
Server IP address Address of the media proxy that sets up Default value: Auto
sessions between two devices registered You can use the default
with the SC. value or enter a value.
H.323 port Number of the port the SC uses to process Default value: 1719
H.323 calls.
SIP transport Protocol used at the SIP transport layer. The value must be the
layer protocol Available options are: TCP, UDP, and same as the value of SIP
TLS. transport layer protocol
configured on the
neighboring SC.
SIP port Number of the port the SC uses to process The value must be the
SIP calls. same as the value of SIP
port configured on the
neighboring SC.
Support call Whether to enable the call transfer function This parameter is not
transfer when SIP is used. If this parameter is selected by default.
selected, the SC implements the call
transfer function for endpoints that do not
support this function.
Enable media If media routing is enabled, the SC Set this parameter based
route performs media forwarding for all calls in on the site requirements.
the zone, as well as incoming and outgoing
calls.
Step 6 Repeat Step 2 through Step 5 to add Province B as neighboring zone SC1_B on SC2.
If you select Enable keepalive for SC1_B on SC2, the keepalive function is displayed as
active in the zone details, as shown in Figure 4-10.
----End
Step 2 Choose Devices > Switch Centers and click the name of SC1.
Rule name Name of the rule to identify it on the The name must be unique on the
SC. same SC.
To help identify the rule, specify the
rule directivity in the name.
Example: To SC2_C_C1
Enable Whether to apply the rule to the SC. This parameter is selected by
default.
Priority Priority of the rule used when the A smaller value indicates a higher
SC selects search rules to apply. priority.
Default value: 1
Source Zone to which the calling party Set this parameter based on the site
Domain belongs. requirements.
Type l LOCAL: all zones on the local Example: LOCAL
SC
l ANY: no restriction on the zone
to which the calling party
belongs
Destination Zone to which the called party Set this parameter based on the
Domain belongs. directivity of the search rule.
l LOCAL: all node zones on the Example: SC2_C
local SC NOTE
l Another zone: external zone The drop-down list box can display a
maximum of 30 zone names. You can
defined on the local SC,
enter a keyword to search for required
including Neighbor zone, zone information.
Gateway zone, Traversal-
server zone, and Traversal-
client zone.
Matching Search mode. Available options are: Set this parameter based on the site
type l Exact match requirements.
l Prefix match Example: Prefix match
l Suffix match
l Regular expression match
Matching Search criteria, which can be a The type of value entered varies
Criteria number, alias, URI, or regular according to the settings of Match
expression. type.
l Exact match: Enter a string of
characters. For a node to match
the rule, the node's alias must
exactly match the entered string.
l Prefix match: Enter a string of
digits. The SMC2.0 searches for
matching rules by starting from
the first digit.
l Suffix match: Enter a string of
URI characters. The SMC2.0
searches for matching rules by
starting from the first character
following at (@).
l Regular expression match:
Enter a string of regular
expression. For example, to
search for aliases that start with
abc, enter abc(.*).
Example: 0512
Conversion Conversion content.. This parameter Enter the content for conversion.
content is available only when Conversion
Type is set to Replace.
----End
Step 2 Choose Devices > Switch Centers and click the name of the desired SC.
Step 4 Set the number conversion rule parameters described in Table 4-8.
Source domain Zone to which the calling party Set this parameter based on the
belongs. site requirements.
NOTE
The drop-down list box can
display a maximum of 30 zone
names. You can enter a keyword to
search for required zone
information.
Matching type Type used for matching the rule. Set this parameter based on the
Available options are: site requirements.
l Exact match Example: Exact match
l Prefix match
l Suffix match
l Regular expression match
Matching Criteria Content used for matching the Example value: 9000
rule, which can be a number,
alias, URI, or regular
expression.
Conversion rule Type used for converting Set this parameter based on the
numbers. Available options are: site requirements.
l Delete Example: Replace
l Replace
l Add prefix
l Add suffix
----End
The inter-zone bandwidth management rule is used to limit the single call and total call
bandwidth between any two zones of the SC. When devices in two zones configured with an
inter-zone bandwidth management rule call each other, the SC checks the call, and
disconnects the call that exceeds the specified bandwidth limit.
NOTE
The embedded SC and standalone SC support a maximum of 200 and 1000 bandwidth management rules
respectively.
Different bandwidth management rules between different zones make differentiated call
management possible.
A 30 100
B 28 100
C 5 50
Step 2 Choose Devices > Switch Centers and click the specified SC name.
----End
Selecting Zones
A bandwidth management rule is used to limit the communication bandwidth between a pair
of zones. A bandwidth management rule can apply to multiple pairs of zones.
Step 1 Select a bandwidth management rule and click Add in Bandwidth Management Zones.
Step 2 Set the bandwidth management zone parameters according to Table 4-11.
Start Zone Name Zones to which the Select a zone from the drop-
bandwidth management rule down list box or directly
End Zone Name applies. type a defined zone name.
The drop-down list box
displays a maximum of 30
zones that have been added
to the SC.
----End
Background
Each participant the administrator adds to the SMC2.0 contains information such as name,
number, and type. The SMC2.0 generates the network address book using these information,
and pushes the network address book to all registered participants through the SC. Then the
participants can implement point-to-point calls among each other or use SiteCall to initiate
conferences.
If the automatic update function is enabled for the network address book on the SMC2.0, the
SMC2.0 updates the network address book every 15 minutes and pushes the updated network
address book through the SC.
To enable the automatic update function for the network address book, choose System >
Settings > Network Services and select Auto update network address book.
By default, the generated network address book is stored in the D:\Huawei Technologies Co.,
Ltd\SMC 2.0\Bin\FTP\NetBook\ directory of the SMC2.0 server.
l Netaddrs.vcf: network address book.
l Version.txt: file that records the version number of the network address book.
Step 3 Set the network address book authentication parameters according to Table 4-12 and click
Save.
Step 4 Access the Address Book page and click the Address Book tab. Then click Download FTP
Address Book.
The latest network address book is obtained.
----End
If the server where the network address book is stored connects to two networks at the same
time, the SC allows you to configure two FTP addresses so that a participant can select a
proper network to obtain the network address book.
Step 2 Choose Devices > Switch Centers and click the specified SC name.
Step 3 Click the Network Address Book tab and click Add.
Step 4 Set the network address book parameters according to Table 4-13.
Product ID Type of the participant to which Select the desired type from the
the network address book is drop-down list box.
pushed. A participant can
receive the network address
book only after registering with
the SC. The options are as
follows:
l VIEWPOINT 8000:
HUAWEI 8000 series group
videoconferencing endpoints
l VIEWPOINT 9000:
HUAWEI 9000 series HD
videoconferencing endpoints
l HUAWEI TEX0: HUAWEI
TE series videoconferencing
endpoints
l TE Desktop: TE series
desktop endpoints
l TE Mobile: TE series mobile
endpoints
FTP login account Account for authentication when Set this parameter based on the
the participant reads the network site requirements. Enter ftpuser
address book from the server. for the network address book
generated by the SMC2.0.
FTP login password Password for authentication Set this parameter based on the
when the participant reads the site requirements. Enter
network address book from the Change_Me for the network
server. address book generated by the
SMC2.0.
Step 6 Click Notify Change in the upper-right corner to update the network address book on the
participant side.
----End
NOTE
Step 2 Choose Devices > Switch Centers and click the specified SC name.
Source Domain Start zone for the media Select a zone from the drop-
route. down list box or directly
type a defined zone name.
The drop-down list box
displays the zones that have
been added to the SC.
NOTE
The drop-down list box can
display a maximum of 30 zone
names. You can enter a
keyword to search for required
zone information.
Destination Domain End zone for the media Select a zone from the drop-
route. down list box or directly
type a defined zone name.
The drop-down list box
displays the zones that have
been added to the SC.
NOTE
The zone selected for Source
Domain is not displayed in the
Destination Domain drop-
down list box.
----End
5 Basic Settings
This section describes basic settings on the SMC2.0, such as settings of device templates,
participants, MCUs, and recording servers.
Background
There are two template types: MCU and participant.
l MCU template
Contains H.323, SIP, DNS, and SNMP parameters.
l Participant template
Contains H.323, SIP, DNS, SNMP, time, call, and update parameters.
You can identify different template types by naming the templates, for example 9xxx MCU,
8xxx MCU, H.323 participant, and SIP participant.
When adding several devices of the same type, using a configuration template can simplify
your operations.
Moreover, using the template can protect the parameter settings on the device against manual
changes. If any parameter set on a device is inconsistent with that specified in the
configuration template, the SMC2.0 can change the parameter value to be the same as that in
the template during the SMC2.0's periodical check.
Prerequisites
l The device to add is a manageable device.
l The parameters to be set on the device are the same as those in the template.
Procedure
Step 1 Log in to the SMC2.0 web interface.
----End
NOTE
A participant can be connected to a videoconferencing network through the H.323 or SIP protocol. To
ensure flexible communication between the participant and the soft client, it is recommended that you
register a manageable participant with both a GK and a SIP server when adding the participant.
Others Unrestricted
NOTE
Manageable devices can also be added to the SMC2.0 in unmanageable mode.
Prerequisites
The SMC Local Address parameter is set to the SMC2.0 server IP address, as shown in
Figure 5-3. This requirement must be met if the participant you want to predefine uses a
HUAWEI TP series telepresence endpoint. Set the parameter under System > Settings >
General.
Model Device model of the predefined Select the device model from the
participant. drop-down list box.
Protocol type Data connection type used by the If the participant is on a typical
participant. videoconferencing network,
If the participant supports select H.323.
multiple data connection types, it
uses the type specified by this
parameter by default when
joining a conference.
Contact number Phone number of the contact to Enter the phone number actually
add. used by the contact.
User email Email address of the contact to Enter the email address actually
add. used by the contact.
E.164 alias Number the participant uses to Enter a number that starts with
register with the GK. the zone prefix and complies
with the zone requirements.
Switch Center Name of the SC to which the Select the desired SC from the
participant belongs. drop-down list box.
GK address IP address of the GK (that is, IP Select the IPv4 or IPv6 address
address of the SC) with which of the desired SC from the drop-
you want to register the down list box.
participant.
Server IP address IP address of the SIP server with Select the IPv4 or IPv6 address
which you want to register the of the desired SC from the drop-
participant. down list box.
----End
If the participant fails to get online, troubleshoot the failure by following the instructions in
8.5 Failure to Search for a Videoconferencing Participant or 8.6 Failure to Search for a
Telepresence Participant.
Prerequisites
The prerequisites for the SMC2.0 to automatically detect a participant are as follows:
l On a videoconferencing participant endpoint: Under System Settings > Network >
SNMP Settings, Enable SNMP is selected and Trap server address is set to the
SMC2.0 IP address.
l On a telepresence participant endpoint (telepresence host): Under System Settings >
Other Users, Network Manager is set to the SMC2.0 IP address.
l If the participant uses a HUAWEI TP series telepresence endpoint, the SMC Local
Address parameter is set to the SMC2.0 server IP address, as shown in Figure 5-7. Set
the parameter under System > Settings > General.
Step 5 Select an organization to which you want to add the participant and click OK.
The SMC2.0 connects to the participant endpoint and displays the participant configuration
information.
Step 6 Add the participant as a manageable participant to the SMC2.0. For details, see 5.2.4 Adding
a Manageable Participant.
----End
Key Points
The key points for successfully adding a manageable participant are as follows:
l A management connection is set up between the SMC2.0 and participant endpoint, as
indicated by the icon.
l The participant endpoint has registered with a GK, as indicated by the icon.
l The participant endpoint has registered with a SIP server, as indicated by the icon.
NOTE
The SMC2.0 connects to a telepresence participant using HTTP; therefore, you must select Perform
non-SNMP search (connection time will significantly increase).
The SMC2.0 starts to search for the participant. If the search is successful, the participant
configuration information is displayed.
If the search fails, take troubleshooting measures according to 8.5 Failure to Search for a
Videoconferencing Participant or 8.6 Failure to Search for a Telepresence Participant.
Step 5 Set the participant parameters described in Table 5-3.
Contact number Phone number of the contact to Enter the phone number actually
add. used by the contact.
User email Email address of the contact to Enter the email address actually
add. used by the contact.
Register with Whether to register the participant Select Register with gatekeeper.
gatekeeper with a GK.
E.164 alias Number the participant uses to Enter a number that starts with the
register with the GK. zone prefix and complies with the
zone requirements.
Switch Center Name of the SC to which the Select the desired SC from the
participant belongs. drop-down list box.
GK address IP address of the GK (that is, IP Select the IPv4 or IPv6 address of
address of the SC) with which you the desired SC from the drop-
want to register the participant. down list box.
SIP URI Unified identifier the participant Enter a string of digits, IP address,
uses to register with the SIP or URI characters that are
server. different from the value of H.323
ID.
Server IP IP address of the SIP server with Select the IPv4 or IPv6 address of
address which you want to register the the desired SC from the drop-
participant. down list box.
If the participant fails to register with the specified GK, take troubleshooting measures
according to 8.3 Failure to Register a Participant with a GK.
----End
Step 2 Choose Devices > Participant > More > Add Unmanageable Participant.
Support dual Whether to enable the participant This parameter is not selected by
protocols to support the H.323 and SIP default.
protocols.
Switch Center Name of the SC to which the Select the desired SC from the
participant belongs. drop-down list box.
Step 4 Click Capability, set the capability parameters, and return to the Add Unmanageable
Participant page.
Step 5 Click Other Parameters, set the contact parameters, and return to the Add Unmanageable
Participant page.
In the participant list, the participant is in unregistered state, as indicated by the icon.
3. Click Save.
Step 8 Run the TE Desktop client. The login window shown in Figure 5-14 is displayed.
Step 9 Set the login parameters described in Table 5-5 and click Log In.
Server address Server address (that is, SC Enter the IP address or domain
address) that the participant is to name of the SC.
register. NOTE
NOTE It is recommended that you set
Server address to the SC's domain
At your first login, click to set name. When setting this parameter to
the addresses of the registration the SC's IP address, enter its private
server and upgrade server. IP address if you reside on the private
network and enter its public IP
address if you reside on the public
network.
Account User name for authentication This parameter value must be the
when the participant registers with same as that of Label set on the
a SIP server. SMC2.0.
Password Password for authentication when This parameter value must be the
the participant registers with a SIP same as that of Password set on
server. the SMC2.0.
If a participant is online:
l is displayed on the TE Desktop client.
Rate Default rate for the participant to Select an appropriate rate for
join a conference. joining a conference from the
drop-down list box.
Left screen label/ Unique identifier the participant Enter a string of digits, IP
Center screen label/ uses to register with a server. address, or URI characters.
Right screen label Record your setting here. The
value of Left screen site
number/Center screen site
number/Right screen site
number set on the participant
side must be the same as this
parameter value.
Switch Center Name of the SC to which the Select the desired SC from the
participant belongs. drop-down list box.
Step 4 Click Capability, set the capability parameters, and return to the Add Unmanageable
Participant page.
Step 5 Click Other Parameters, set the contact parameters, and return to the Add Unmanageable
Participant page.
In the participant list, the participant is in unregistered state, as indicated by the icon.
Step 7 Log in to the web interface of the telepresence participant codec, and choose System Settings
> Network > H.323/SIP Settings.
NOTE
By default, the web-based login function of the TP3106–70/TP3206–55 codec is disabled. You can run the
web set on command using an SSH tool, for example, PuTTY, to enable this function. After you set
parameters on the web page, run the web set off command to disable the function again.
Center screen Number the participant uses to This parameter value must be the
site number/ register with the GK. same as that of Center screen
Left screen label/Left screen label/Right
site number/ screen label set on the SMC2.0.
Right screen
site number
H.323 ID Alias the participant uses to This parameter value must be the
register with the GK. same as that of Name set on the
SMC2.0.
Authentication User name for authentication when This parameter value must be the
user name the participant registers with a GK. same as that of User name set on
the SMC2.0.
Password Password for authentication when This parameter value must be the
the participant registers with a GK. same as that of Authentication
password set on the SMC2.0.
The participant is displayed in online state on the SMC2.0 web interface, as indicated by .
----End
Context
For batch operations on unmanageable participants, note that:
l Users who have only the rights to add and view participants cannot perform batch import
or export operations.
l The language used to log in to the SMC2.0 must be the same as the language of the batch
import template.
l The web browser must be a web browser supported by the SMC2.0, including Internet
Explorer 8 or later and latest versions of FireFox, Chrome, and Safari; otherwise, the
batch import template will fail to be downloaded or uploaded.
Step 3 In the left pane, select an organization to which unmanageable participants are to be added.
NOTE
If you do not have the template on your PC, click Download Template to download the template. The
instructions to add, modify, and delete unmanageable participants in the template are provided in the
Description sheet.
Step 5 After adding necessary information in the template, click Browse... to select the template.
Step 6 Click Import.
The Prompt dialog box is displayed.
l Click OK to start the bulk addition task.
l Click Go to My Tasks to access the My Tasks page, on which you can check the bulk
addition result.
NOTE
If the bulk addition task fails, click Export Failure Results to export the failure cause.
----End
Step 3 Click Batch Export. The Batch Export dialog box shown in Figure 5-18 is displayed.
Step 4 Click Export to export the table that contains all unmanageable participants and change the
state of unmanageable participants to delete to DELETE.
NOTE
The instructions to add, modify, and delete unmanageable participants in the template are provided in the
Description sheet.
----End
NOTE
To enable an MCU to allow connections from both SIP and H.323 participants, register the MCU with
both GK and SIP servers when you add the MCU to the SMC2.0.
Determine whether an MCU is manageable based on the model and version of the MCU. For
details, see Table 5-8.
For a manageable MCU, further determine its adding method based on its deployment mode.
l If the MCU is deployed before the SMC2.0, set the network management address on the
MCU, and enable the SMC2.0 to auto-detect the MCU.
l If the MCU needs to be added to the SMC2.0 because of a site upgrade, add the MCU as
a manageable MCU to the SMC2.0.
NOTE
Manageable devices can also be added to the SMC2.0 in unmanageable mode.
Prerequisites
The prerequisites for the SMC2.0 to automatically detect an MCU are as follows:
Step 2 At the prompt <HUAWEI VP9660>, enter system-view snmp-config and press Enter.
SNMP V3trap send mode Trap message transmission Set this parameter to trap.
method in SNMPv3 mode.
SNMP trap time out Timeout duration for a trap Retain the default value 5.
operation.
SNMP trap retry times Number of retry attempts for Retain the default value 3.
a trap operation.
SNMP 1 Trap Dest Add Destination IP address for a Set this parameter to the
IpV4 trap operation. The MCU SMC2.0 IP address.
reports its configuration
information to the SMC2.0
that uses this IP address.
Step 4 At the prompt <HUAWEI VP9660>, enter save and press Enter, then, enter y.
----End
Step 4 Select the MCU you want to add and click Add to System.
Step 5 Select the organization to which you want to add the MCU and click OK.
The SMC2.0 connects to the MCU and displays the MCU configuration information.
Step 6 Add the MCU as a manageable device to the SMC2.0.
For details, see 5.3.3 Adding a Manageable MCU.
----End
Key Points
The key points for successfully adding a manageable MCU are as follows:
l A management connection is set up between the SMC2.0 and MCU, as indicated by the
icon.
l A service connection is set up between the SMC2.0 and MCU, as indicated by the
icon.
l The MCU has registered with a SIP server, as indicated by the icon.
When the SMC2.0 and MCU are correctly connected to a network, you can set the MCU
parameters on the SMC2.0. Your settings take effect on the MCU. The MCU parameters
exclude Connection mode and Connection password, which are authentication parameters
for setting up a service connection between the SMC2.0 and MCU.
Listening port Communication port between the Record your setting here. It must
MCU and the SMC2.0. be consistent with the setting of
Port on the SMC2.0.
Default value: 5000
Connection Whether the MCU connects to the Record your setting here. It must
mode SMC2.0 in encrypted mode. be consistent with the setting of
Connection mode on the
SMC2.0.
Default value: Encrypt
Connection Password the MCU uses to Record your setting here. It must
Password connect to the conference be consistent with the setting of
management system. Connection password on the
SMC2.0.
Example: smc_to_mcu
----End
The SMC2.0 starts to search for the MCU. If the search is successful, the MCU configuration
information is displayed.
If the search fails, take troubleshooting measures according to 8.4 Failure to Search for an
MCU.
Step 5 Set the MCU parameters according to Table 5-11.
Name Name of the MCU to identify on The name can contain a maximum
the SMC2.0. of 64 characters.
Port Communication port between the This parameter value must be the
SMC2.0 and the MCU. same as the value of Listening
Listening port port set on the MCU.
Connection Whether encryption mode is used This parameter value must be the
mode for the connection between the same as the value of Connection
SMC2.0 and MCU. mode set on the MCU.
Default value: Encrypt
HTTP Password the SMC2.0 uses to This password must be the same
connection update the MCU online. as the administrator password set
password on the MCU.
Default value: Change_Me
Register with Whether to register the MCU with Select Register with gatekeeper.
gatekeeper a GK.
Switch Centers SC to which the MCU belongs. Select the desired SC from the
drop-down list box.
SIP URI URI the MCU uses to register Enter a string of digits, IP address,
with the SIP server. or URI characters that are
different from the value of H.323
ID.
Register server Whether to register the MCU with Select Register server.
a SIP server.
Server IP address IP address of the SIP server with Enter the SIP server IP address. If
which you want to register the you are using the SMC2.0's
MCU. embedded SC, enter the SMC2.0
IP address.
If the MCU status is offline, take troubleshooting measures according to 8.2 MCU Displayed
as Offline on the SMC2.0.
----End
Key Points
The key points for successfully adding an unmanageable MCU are as follows:
l A service connection is set up between the SMC2.0 and MCU, as indicated by the
icon.
l The MCU has registered with a SIP server, as indicated by the icon.
The following describes how to add an unmanageable MCU, using the VP9610 as an
example:
l By default, HTTP is used for connections between the SMC2.0 and the VP9610 or VP9620 MCU. If
you select Support HTTPS, the connection between the SMC2.0 and MCU is encrypted.
l The connection mode and password set on the MCU and SMC2.0 must be the same. Otherwise, the
service connection between the two fails.
l The connection mode for the ViewPoint 8660, ViewPoint 8650, or ViewPoint 8650C MCU of the
V100R007 version can be set only from the CLI. To enable encryption, run the system-view telnet
enable-security-mode 1 command.
HTTP HTTP connection port through Retain the default value 8080.
connection port which the MCU can connect to
the conference management
system.
HTTPS HTTPS connection port through Retain the default value 8443.
connection port which the MCU can connect to
the conference management
system.
Connection Password the MCU uses to Record your settings here. They
password connect to the conference must be consistent with the
management system. settings of Connection password
on the SMC2.0.
Example: smc_to_mcu
Step 7 On the Gatekeeper tab, set the GK parameters described in Table 5-13.
Register with Whether to register the MCU with Select Register with Gatekeeper.
Gatekeeper a GK.
H.323 ID Alias the MCU uses to register Record your settings here. They
with the GK. must be consistent with the
settings of H.323ID on the
SMC2.0.
Example: 075513101
Step 8 On the SIP tab, set the SIP parameters described in Table 5-14.
User name Alias the MCU uses to register Record your settings here. They
with the SIP server. must be consistent with the
settings of SIP URI on the
SMC2.0.
Example: 075513102
Password Password the MCU uses to Record your settings here. They
register with the SIP server. must be consistent with the
settings of Authentication
password on the SMC2.0.
Register with Whether to register the MCU with Select Register with SIP Server.
SIP Server a SIP server.
Server address IP address of the SIP server with Enter the GK IP address. If you
which you want to register the are using the SMC2.0's embedded
MCU. SC, enter the SMC2.0 IP address.
NOTE
If you change the value of Connection type, choose Settings > Maintenance > Restart MCU and click
Restart MCU to restart the MCU.
----End
Step 2 Choose Devices > MCUs > More > Add Unmanageable MCU.
Name Name of the MCU to identify on Enter a name, which must be the
the SMC2.0. same as the value of H.323 ID set
on the MCU.
Connection Password the SMC2.0 uses to This parameter value must be the
password connect to the MCU. same as the value of Connection
password set on the MCU.
Example: smc_to_mcu
H.323ID Alias the MCU uses to register This parameter value must be the
with the GK. same as the value of H.323 ID set
on the MCU.
H.323 server Device that provides GK services Select the desired SC from the
for the MCU. drop-down list box.
SIP registration Whether to register the MCU with Select SIP registration.
a SIP server.
SIP URI URI the MCU uses to register This parameter value must be the
with the SIP server. same as the value of User name
set on the MCU.
Authentication Password the MCU uses to This parameter value must be the
password register with the SIP server. same as the value of Password set
on the MCU.
SIP server Device that provides SIP services Select the desired SC from the
for the MCU. drop-down list box.
On the MCUs page, the MCU status is online, as shown in Figure 5-28.
If the MCU status is offline, take troubleshooting measures according to 8.2 MCU Displayed
as Offline on the SMC2.0.
----End
The SMC2.0 allows users to add two types of recording servers: RSE6500 and REACH.
Table 5-16 lists the function differences between them.
Conn Mode in which the RSE6500 manages Set this parameter to SMC/Third
ection live broadcast and recording services. party.
type
Conn User account used by a third party to The value of Connection account must
ection set up a session with the RSE6500. be the same as that of User name under
accou Add RSE on the SMC2.0 web
nt interface.
Example: rse
Conn Password used by a third party to set up The value of Connection password (If
ection a session with the RSE6500. left blank, the previous password will
passw The password is a string of 8 to 32 be used.) must be the same as that of
ord (If characters that contain at least two Password under Add RSE on the
left types of the following: uppercase SMC2.0 web interface.
blank, letters, lowercase letters, digits, and Example: Change_Me
the special characters.
previo
NOTE
us To secure the account, change the password
passw regularly.
ord
will
be
used.)
Step 5 Log in to the RSE6500 web interface and choose System > System Settings.
Step 6 Choose the Gatekeeper Configuration tab, set the GK parameters described in Table 5-18.
Gatekeeper address IP address of the GK (SC) with Enter the IP address of the SC.
which you want to register the
recording server.
H.323 ID Alias the recording server uses This parameter value must be
to register with the GK. the same as that of H.323 ID set
on the SMC2.0.
Authentication user User name the recording server This parameter value must be
name uses to pass the authentication the same as that of H.323
when registering with the GK. Authentication user name set
on the SMC2.0.
Step 7 Choose the SIP tab, set the SIP parameters described in Table 5-19. Then click Save.
Authentication user User name the recording server This parameter value must be
name uses to pass the authentication the same as that of SIP
when registering with the SIP Authentication user name set
server. on the SMC2.0.
Register with SIP Whether to register the Select Register with SIP
server recording server with a SIP server.
server.
SIP server address IP address of the GK (SC) with Enter the IP address of the SC.
which you want to register the
recording server.
----End
Step 3 Select the organization to which the recording server belongs and click Add Server.
Step 4 Enter the recording server IP address in IP Address and click Next.
If the search fails, take troubleshooting measures according to 8.7 Failure to Search for a
Recording Server.
Step 5 Set the recording server parameters described in Table 5-20.
NOTE
To adapt the recording server to diverse scenarios, such as multi-party conference recording and single-
point SIP conference recording, it is recommended that you register the recording server with both a GK
and a SIP server when adding the recording server.
Switch Centers SC to which the recording Select the desired SC from the
server belongs. drop-down list box.
User name User name and password used Enter a string of characters.
when recording server registers
Password with the GK. The value contains eight
characters or more, including at
least two types of the following:
lowercase letters, uppercase
letters, digits, and special
characters (except spaces).
Switch Centers SC to which the recording Select the desired SC from the
server belongs. drop-down list box.
Authentication user User name and password used Enter a string of characters.
name when recording server registers
with the SIP server.
Password The value contains eight
characters or more, including at
least two types of the following:
lowercase letters, uppercase
letters, digits, and special
characters (except spaces).
----End
Step 3 On the SMC link Configuration tab page, set the SMC Password parameter and click Save,
as shown in Figure 5-33.
Step 4 On the Restart and Synchronize tab page, click Restart the server, as shown in Figure
5-34.
----End
Step 2 Choose Devices > Recording Servers > More > Add Unmanageable Recording Server.
----End
6 Service Configuration
Service configuration on the SMC2.0 includes configuration for recording servers, billing
codes, and network address books.
NOTE
The Verify certificate check box is selected by default to secure the connection between the SMC2.0
and the corporate directory server. To verify the security certificate on the device to which the SOAP
port on the SMC2.0 is connected, choose System > Settings > Devices and select Verify server
certificate.
----End
Step 4 Set required parameters, such as AD server IP address and AD server port.
To synchronize certain user and organization information from the AD server to the Corporate
Directory Servers, set AD filter criteria to specify the filter criteria.
NOTE
l Then the Corporate Directory Servers synchronizes information about only the users and organizations
that meet the specified filter criteria.
l The most common attribute is ObjectClass. If you enter this attribute, the corporate directory server
synchronizes the participants that have this attribute and attribute value.
l The value of AD filter criteria can be empty, a single criterion, or a combination of more than one
criterion.
NOTE
l To synchronize the information about sites and organizations that are mapping between the AD
server and the corporate directory server, click AD-Enterprise Corporate Directory Full
Synchronization.
l To modify the mappings of sites and organizations between the AD server and the corporate
directory server, click Import AD Data Model, download the template, modify the mappings in the
template, and upload the modified template to the SMC2.0.
l If Encrypt is selected and the AD server has a root certificate, change the AD server port to 636 and
click Import AD Root Certificate to upload the root certificate to the SMC2.0.
----End
Other Configurations
On the Other Settings tab page under Enterprise Corporate Directory servers, the system
administrator can perform many tasks, such as resetting the login password of the corporate
directory server and configuring alarm query.
Step 4 Under Other Operations, click Reset SMC Password, Reset TMS Password, or Reset
eMP Password to reset the passwords used for accessing the corporate directory server by the
SMC2.0, TMS, or eMP respectively.
Step 5 Under Other Operations, click Manual Full Synchronization to synchronize all
information about users, organizations, participants, and Ad hoc conferences from the
SMC2.0 to the corporate directory server.
Step 6 Set the parameters shown under Other Settings in Figure 6-3.
NOTE
l After resetting the password used by the SMC2.0 to access the corporate directory server, go to the
Details tab page and change the login password to the new one; otherwise, the login account will be
locked when you attempt to access the corporate directory server. (When resetting the password,
ensure that the old password you enter is the same as the password set on the Details tab page.)
l Only the admin user is allowed to execute the Manual Full Synchronization task.
l The corporate directory server will automatically restart if you click Save after modifying
Corporate directory security level.
----End
Background
On the SMC2.0, you can remotely update a manageable device if you have specified the
software version and uploaded the version file to the file server, which is located on the same
computer as the SMC2.0.
The SMC2.0 supports batch updates for devices. When updating devices in batches, the
SMC2.0 estimates the update end time for each device. Table 6-1 lists the reference update
duration for various device model series.
The SMC2.0 can update a maximum of 10 devices (including MCUs, participants, and SCs)
at a time. If the number of devices to update exceeds 10, the additional devices wait in a
queue.
Prerequisites
A manageable device can be updated successfully on the SMC2.0 only if:
l The update password for the device is the same as that for the SMC2.0.
l The scheduled update time is appropriate, especially when devices are updated in
batches.
If the update end time scheduled for a device arrives and the device has not yet started
the update, the SMC2.0 cancels the update task for the device.
Step 4 Click Browse..., select the version file to upload, and click Open.
Table 6-2 lists the version files required for various devices.
VP9600 series MCU A .dat file. If you need to update the interactive
voice response (IVR), compress the .bin and .ivr
files as a .zip file.
VP8600 series MCU A .bin file. If you need to update the IVR, compress
the .bin and .ivr files as a .zip file.
NOTE
For VP8600 series MCU, you need to enter its version number when uploading the version file. For other
devices, the SMC2.0 automatically reads the version number from the software version.
Step 5 In Software information, enter a description of the software. Then, click Finish.
----End
NOTE
l If the device fails to successfully start the update when the time specified by Start time arrives, the
SMC2.0 repeatedly restarts the update task until update prerequisites are met.
l End time specifies the time for stopping restarting the update task. To be specific, if the device still
cannot start the update when the time specified by End time arrives, the SMC2.0 cancels the update
task. The cause of the update failure may be that the update password is incorrect or the device is
being used for a call.
----End
Adding a Topology
----End
Editing a Topology
Step 1 In the left pane of the Set page, select the topology you want to edit, and click .
The Edit Topology dialog box is displayed.
Step 2 In Topology name, rename the topology.
----End
Deleting a Topology
Step 1 In the topology list, select the topology you want to delete.
Step 2 Click .
The Confirm dialog box is displayed.
Step 3 Click Yes.
----End
Step 1 In the left pane of the Set page, select the topology you want to edit, and click .
The Set Background dialog box is displayed.
Step 2 Click Browse... and select a background picture to upload.
The SMC2.0 automatically uploads the image.
Step 3 Specify whether to show the background image.
l Show background picture: The background image is displayed.
l Hide background picture: The background image is not displayed.
Step 4 Click OK.
----End
Adding a Device
Step 1 In the left pane of the Set page, select the topology you want to edit, and click .
The Add Device to Topology dialog box is displayed.
Step 2 Select Include child nodes and select a device from the displayed device list.
Step 3 Click the name of the selected device and move the device icon to the correct position on the
topology.
----End
Background
To save MCU transrating resources, divide the conference rate range (128 kbit/s to 8 Mbit/s)
into several subranges and specify audiovisual parameters for each subrange. Any two
neighboring subranges must be adjacent but not overlapping. When a conference is to be held,
the SMC2.0 determines the conference parameters (including the video protocol, video
format, and audio protocol) based on the conference rate and participant parameters
(including the video protocol, video format, and audio protocol) based on the number of
participants and rate range thresholds.
NOTE
Range setting policies are used to adjust rates and parameters for conferences and participants on the
universal transcoding MCU. Now two sets of range setting policies are available: the old set and the new
set. The new set of range setting policies are used to adjust rates of conferences on the universal
transcoding MCU, but do not take effect for parameters of conferences or rates and parameters of
participants.
Prerequisites
The conference and participant parameters for a conference have been set to Auto.
Procedure
To configure the range setting policy, perform the following steps:
NOTE
l Rate ranges provided by the SMC2.0 by default also provide audio and video parameters. The
default settings are recommended. If you really need to modify audio and video parameters, click a
default parameter and select a new one from the drop-down list box. The video format can only be
one of those supported by the specified video protocol. Therefore, you have to specify the video
protocol first and then set the video format accordingly.
l You can click Set Minimum Rate to change the minimum rate of a rate range.
l You can adjust the minimum rate of a rate range to determine the rate range and adjust the number of
rate ranges. After the minimum rate of a rate range is changed, the maximum rate of the next rate
range will be changed accordingly. (By default, the maximum rate of the first rate range is 8 Mbit/s
and the minimum rate of the last rate range is 192 kbit/s.)
----End
Step 2 Adjust the conference rate and parameters. Use the conference rate specified beforehand and
audiovisual parameters in the corresponding rate range.
Step 3 Adjust the participant rate and parameters. Check whether the number of participants in rate
ranges exceed the thresholds and determine the participant rate and parameters accordingly.
l If the number of participants is no smaller than the threshold, check whether all
participants have the same rate. If yes, the participants still use the rate. If no, all
participants decrease their rates to the minimum in their rate ranges.
l If the number of participants is smaller than the threshold and participants exist in the
next rate range, the participants within the current rate range will use the maximum rate
in the next rate range.
l If the number of participants is smaller than the threshold and the next rate range does
not have any participants, the participants within the current rate range will use the
minimum rate in the next rate range.
l Participant parameters use audiovisual parameters adopted after participant rate is
adjusted. If the value of an audiovisual parameter goes beyond the value range allowed
the participant, the SMC2.0 automatically adjusts the audiovisual parameter to the
maximum value allowed by the participant.
----End
Examples
This section assumes four rate ranges and describes how old rate adaption rules determine the
participant rate.
l Rates are divided into six ranges: [4 Mbit/s, 8 Mbit/s], [1536 kbit/s, 4 Mbit/s), [512
kbit/s, 1536 kbit/s), [192 kbit/s, 512 kbit/s).
l The maximum numbers of participants allowed in ranges 2 and 3 are 4 and 2
respectively.
l The conference has three participants: participant 1 (1920 kbit/s), participant 2 (1152
kbit/s), and participant 3 (1216 kbit/s).
Based on the participants' transmission rates, the SMC2.0 recognizes that participant 1
belongs to range 2, and participants 2 and 3 belong to range 3.
Following the rule for determining the participant rate, the SMC calculates the participant rate
as follows:
1. The number of participants with rates falling into range 2 is smaller than the threshold
set for range 2, so participant 1 in range 2 will decrease its rate to the maximum rate of
range 3 that is, 536 kbit/s.
2. Now three participants reside in range 3. However, only two participants are allowed in
range 3 at most.
3. The three participants have different rates (that is, 1152 kbit/s, 1216 kbit/s, and 1919
kbit/s), so they finally use the lowest one among the three rates, that is, 1152 kbit/s.
As a result, the three participants join the conference all at 1152 kbit/s.
Step 2 Adjust the conference rate and parameters. Adopt the lowest rate in a rate range as the
conference rate and audiovisual parameters in the rate range.
Step 4 Reserve resources for the rate range that does not contain any participants and all its lower
ranges.
During a conference, the conference's capabilities, participants' capabilities, and rate ranges'
capabilities are sorted. The participant that joins the conference later will adopt the maximum
capabilities among the sorted capabilities.
----End
Examples
This section assumes four rate ranges and describes how new rate adaption rules adjust the
rates and parameters of a conference and its participants.
l Rates are divided into six ranges: [4 Mbit/s, 8 Mbit/s] H.264 1080p, [1536 kbit/s, 4
Mbit/s) H.264 720p, [512 kbit/s, 1536 kbit/s) H.264 4CIF, [192 kbit/s, 512 kbit/s) H.264
CIF.
NOTE
New rate adaption rules have nothing to do with thresholds, which will not be described here.
l The conference has a rate of 2 Mbit/s and contains four participants: participant 1 (2
Mbit/s H.264 1080p/720p/CIF), participant 2 (1 Mbit/s H.264 1080p/720p/4CIF),
participant 3 (5 Mbit/s H.264 1080p60/1080p/720p), and participant 4 (5 Mbit/s H.264
720p).
l Participant 1 falls into range 2 and supports the adjusted conference parameters, so
participant 1 adopts the rate of 1536 kbit/s and the parameter of H.264 1080p.
l Participant 2 falls into range 2 and supports the adjusted conference parameters, so
participant 2 adopts the rate of 1536 kbit/s and the parameter of H.264 1080p.
l Participant 3 falls into range 1 and supports the adjusted conference parameters, so
participant 3 adopts the rate of 4 Mbit/s and the parameter of H.264 1080p.
l Participant 4 falls into range 1 but does not support the adjusted conference parameters.
As participant 4 supports audiovisual parameters in range 1, participant 4 is moved to
range 2 but still does not support audiovisual parameters in range 2. Then participant 4 is
moved to range 3, and it supports audiovisual parameters in range 3. Finally, participant
4 adopts the rate of 512 kbit/s and the parameter of H.264 4CIF.
As a result, the conference's rate is 2 Mbit/s H.264 1080p, participant 1's rate is 1536 kbit/s H.
264 1080p, participant 2's rate is 1536 kbit/s H264 720p, participant 3's rate is 4 Mbit/s H.264
1080p, and participant 4's rate is 512 kbit/s H.264 4CIF.
NOTE
The SMC2.0 adopts new rate adaption rules by default. To use old rate adaption rules, access the
SMC2.0 database and change the rule choice. For details, see the Not Commonly Used Configurations.
Background
NlogV2 alarm thresholds are classified into alarm thresholds and critical alarm thresholds. If a
participant's data statistics exceeds a threshold, a corresponding alarm symbol will be
displayed on the Participants tab of the Conference List page.
Symbols for alarms at different levels are in the following:
l Alarm:
l Critical alarm:
Procedure
Step 1 Log in to the SMC2.0 web interface.
----End
Configuration Verification
If the "Operation succeeded." message is displayed in the lower right corner after you click
Save, the configuration is successful.
Background
The SMC2.0 has default alarm scenarios. You can set the levels and notification methods of
alarms in these scenarios.
Procedure
Step 1 Log in to the SMC2.0 web interface.
Click Alarm Severity and select Set as Major or Set as Minor from the drop-down list
box.
l Alarm Inhibition
Click Alarm Inhibition and select Enable Reporting or Disable Reporting from the
drop-down list box.
l Alarm Sound
Click Alarm Sound and select Muted or Unmuted from the drop-down list box.
l Set Sound
Click Set Sound and select Set Major Alarm Sound, Set Minor Alarm Sound or
Restore Default Sound from the drop-down list box.
----End
Verification
In the alarm scenario list, you can view alarm details, as shown in Figure 6-8.
Background
Using emails, the SMC2.0 can send:
l conference information to participants
l device alarms to device administrators
l notifications to users about new user accounts and passwords
To implement the email notification function, register the SMC2.0 with the email server and
define the email sender's information on the SMC2.0. When a conference is going to take
place, the conference notification is sent to the participants' email addresses you defined. If an
alarm is generated for a device, the alarm is automatically sent to the defined contact's email
address.
A conference notification contains the conference name, start time, end time, password, ID,
and a list of participants.
Prerequisites
l You have obtained the email server IP address.
l You have obtained the account information, including the email address and
authentication password, for logging in to the email server.
Procedure
Step 1 Log in to the SMC2.0 web interface.
Step 3 Choose Email and SMS and select Enable email notification. On the page shown in Figure
6-9, set the parameters and click Save.
NOTE
----End
Configuration Verification
Choose Email and SMS. On the displayed page, click Test Email Settings. If the "Test
email message sent." message is displayed in the lower right corner, the configuration is
successful.
Context
Using SMS messages, the SMC2.0 can send conference information to participants, send
device alarms to device administrators, and send notifications to users about new user
accounts and passwords.
To implement the SMS notification function, obtain the eSDK SMS IP address and add it to
the SMC2.0. Then the SMC2.0 can collaborate with the eSDK SMS server to perform the
following tasks:
l The SMC2.0 sends conference notifications to participants' contact numbers (specified
by conferences or participants in advance) through the eSDK SMS server.
l The SMC2.0 sends device alarms to device administrators' contact numbers (specified
during the device installation) through the eSDK SMS server.
l The SMC2.0 sends new user accounts and passwords to users' contact numbers
(specified upon adding users) through the eSDK SMS server.
A conference notification contains the conference name, start time, end time, password, ID,
and a list of participants.
NOTE
The SMS tunnel is unencrypted, so security risks may arise from enabling the SMS notification
function.
Procedure
Step 1 Log in to the SMC2.0 web interface.
NOTE
----End
Verification
On the Email and SMS page, after you select Enable SMS notification and set SMSGW
address, the Test button appears at the bottom of this page.
Click the Test button. In the Test SMS Settings dialog box that is displayed, enter your
mobile number and click Test. If the message SMS message test succeeded. is displayed in
the lower right corner, the SMS notification function is configured successfully.
NOTE
In an SMS notification template, keywords are placed in curly braces ({ }).
You can modify an SMS notification template on the SMC2.0 by following the procedure:
Step 3 Choose Email and SMS, select a template in the SMS Templates area, and click Edit.
The dialog box for modifying an SMS notification template (Conference scheduling used as
an example here) is displayed, as shown in Figure 6-12.
NOTE
Keywords in SMS notification templates cannot be modified.
----End
Background
The Lightweight Directory Access Protocol (LDAP) is an application protocol for accessing
and maintaining Active Directory (AD) server services over an IP network. When adding
participants to an ongoing conference, you can select the participants defined on the SMC2.0
or from an LDAP address book. In the solution for interoperating with Microsoft unified
communications (UC) systems, the SMC2.0 can use LDAP to access the Microsoft AD.
Prerequisites
Before specifying LDAP settings, set the Preferred DNS server parameter on the SMC2.0
server to the DNS server for the domain where the LDAP server is located. Otherwise, the
SMC2.0 will take a long time in reading LDAP address books.
Procedure
Step 1 Log in to the SMC2.0 web interface.
Step 3 Choose Network Services and set the parameters shown in Figure 6-13. Then, click Save.
NOTE
----End
Configuration Verification
Click Test Directory Service Configuration, if the Test succeeded. message is displayed,
the configuration is successful. If the message Test failed. is displayed, take troubleshooting
measures according to 8.8 "Test failed" Is Displayed During a Test of the Directory
Service Configuration.
Check whether you can add participants from the LDAP address book when scheduling a
conference, as shown in Figure 6-14.
NOTE
l The View participant, Add (inter-node), View (Ad hoc), and Schedule (inter-node) rights are
selected by default.
l No organization is selected by default.
Before an external user logs in to the SMC2.0, modify the default user rights and add an
organization that the external user can access.
Step 3 Click Default User Rights. Then select rights you want to grant to external users on the
External User tab page and select organizations open to external users on the Accessible
node tab page.
----End
NOTE
In the cluster environment, perform step 5 only for AD user login configuration.
6. Click OK.
Step 3 Add the SMC2.0 server to the domain.
1. Log in to the SMC2.0 server.
2. Click Start, right-click Computer, and choose Properties.
The System window is displayed.
3. Click Advanced system settings.
The System Properties dialog box is displayed.
4. On the Computer Name tab, click Change.
The Computer Name/Domain Changes dialog box is displayed.
5. Select Domain under Member of, enter the domain name, and click OK, as shown in
Figure 6-18.
The dialog box for confirming the DNS account and password is displayed.
6. Enter the DNS user name and password added in step 1 and press Enter.
The SMC2.0 server's desktop is displayed with a welcome message.
7. Click OK.
A dialog box is displayed, prompting you to restart the computer.
8. Restart the SMC2.0 server.
After being restarted, the SMC2.0 server is added to the domain successfully.
7. As prompted in the window, check whether the SMC service account is the default
account smc20_service_user.
– If yes, enter Y and press Enter.
– If no, enter the actual account and password and press Enter.
8. In the window that is displayed, enter the password of the local administrator user and
click OK.
NOTE
If the password of the user added in step 1 is changed, perform sub steps 4 to 8 under step 4 again.
5. Click Save.
The Confirm dialog box is displayed, telling that the SMC2.0 web interface will be
restarted if you change external user login settings.
6. Click Yes.
The SMC2.0 web interface is restarted and displays the login page that contains an
external user login entry.
You can log in to the SMC2.0 using an external user account from this entry.
NOTE
If the external user login entry does not appear, refresh the login page and check whether the entry
is displayed.
----End
Step 3 Choose Network Services and set parameters under External User Login Configuration.
Step 4 Select CAS SSO login from the User login type drop-down list box and set other parameters,
as shown in Figure 6-20.
NOTE
l In CAS SSO server login address, enter the URL of the CAS SSO server. For example, enter
https://192.168.51.120:8443/cas/login.
l In CAS SSO server URL prefix, enter the URL prefix of the CAS SSO server. For example, enter
https://192.168.51.120:8443/cas/.
Step 5 Click Test Connection. The system jumps to the CAS page.
The Confirm dialog box is displayed, telling that the SMC2.0 web interface will be restarted
if you change external user login settings.
The SMC2.0 web interface is restarted and displays the login page that contains an external
user login entry.
You can log in to the SMC2.0 using an external user account from this entry.
NOTE
If the external user login entry does not appear, refresh the login page and check whether the entry is
displayed.
----End
Step 5 Enter the account of an external user in the User name field or click Select... to select an
external user from the external user list.
NOTE
The Select... button is unavailable if User login type is set to CAS SSO login.
Step 6 Select a user type from the User type drop-down list box.
The default value of User type is Operator.
Step 7 Set other parameters based on the site requirements. Then click Add.
The message indicating that the external user is added successfully is displayed.
Step 8 Click OK. You will see the external user in the user list.
NOTE
l The password resetting operation cannot be performed on external users from the SMC2.0.
l If an AD user who has been added to the SMC2.0 is deleted from the AD server, the AD user will
not disappear from the SMC2.0 until you delete it. This also applies to CAS SSO users.
----End
Procedure
Step 1 Click Start to execute the mmc.exe program.
The Console1–[Console Root] window is displayed.
Step 2 Click File and choose Add or Remove Snap-ins.
The Add or Remove Snap-ins window shown in Figure 6-22 is displayed.
Step 3 In the Available snap-ins pane, select Group Policy Object Editor and click Add.
The Select Group Policy Object dialog box is displayed.
Step 4 Click Finish.
The system returns to the Add or Remove Snap-ins window.
Step 5 Click OK to return to the Console1–[Console Root] window. The Local Computer Policy
directory appears in the left pane, as shown in Figure 6-23.
Step 6 Choose Local Computer Policy > Computer Configuration > Administrative Templates
> System > Windows Time Service > Time Providers in the left pane and double-click
Configure Windows NTP Client in the right pane.
The Configure Windows NTP Client window shown in Figure 6-24 is displayed.
Step 7 Select Enable and follow the instructions in the Help pane to set parameters in the Options:
pane.
Step 8 Click OK.
The system returns to the Console1–[Console Root], in which the state of Configure
Windows NTP Client is displayed as Enable. This means that the Windows NTP client is
configured successfully.
----End
Typically, the SMC2.0 is networked with all VP9000 series MCUs or a hybrid of ViewPoint
8000 series and VP9000 series MCUs.
7.1.1 Scenario
When the SMC2.0 networks with all VP9000 series MCUs, all types of devices within the
enterprise can join HD video conferences.
Network
Figure 7-1 shows the network where SMC2.0 works with all VP9000 series MCU.
Key Components
Table 7-1 lists the key components.
Network Description
l The SMC2.0 manages MCUs and recording servers in unified manner and allocates them
based on the conference scheduling policy when scheduling conferences.
l Users can schedule conferences on the SMC2.0. On the endpoints, users can use SiteCall
or dial the unified access number to initiate conferences.
l After registering with the SC using both SIP and H.323, an MCU allows both SIP and H.
323 endpoints to join the same conference.
l When TE Desktop&TE Mobile endpoints are deployed, devices including MCUs,
telepresence systems, HD videoconferencing endpoints, and recording servers must
register with the SC using both SIP and H.323 to ensure that the TE Desktop&TE
Mobile endpoints can communicate with other types of endpoints.
l During a conference, each participant can use continuous presence per port.
Adding a SMC Participant endpoint IP address. Set this parameter based on the
manageabl 2.0 site requirements.
e
participant H.323 ID Alias the participant endpoint
uses to register with the SC
using H.323.
7.1.4 Verification
You can initiate a multipoint conference supporting recording in the SMC2.0 to verify the
networking configuration.
Step 6 Select the added participants and click Add. Then click Close.
----End
7.2.1 Scenario
When the SMC2.0 networks with a hybrid of ViewPoint 8000 series and VP9000 series
MCUs, all types of devices within the enterprise can join HD video conferences.
Network
Figure 7-5 shows the network where SMC2.0 works with a hybrid of ViewPoint 8000 series
and VP9000 series MCUs.
Figure 7-5 SMC2.0 networking with a hybrid of ViewPoint 8000 series and VP9000 series
MCUs
Key components
Table 7-4 lists the key components.
Network Description
On the network where SMC2.0 works with a hybrid of ViewPoint 8000 series and VP9000
series MCUs, both ViewPoint 8000 series and VP9000 series MCUs are available in the MCU
resource pool. Endpoints residing on MCUs of different types have different
videoconferencing experience. Endpoints residing on the ViewPoint 8000 series MCUs can
view conference continuous presence. Endpoints residing on the VP9000 series MCUs can
view continuous presence per port.
Except this difference, the network description for the two networking modes is the same. For
details, see Network Description for All VP9000 Series MCUs.
Adding a SMC Participant endpoint IP address. Set this parameter based on the
manageabl 2.0 site requirements.
e
participant H.323 ID Alias the participant endpoint
uses to register with the SC
using H.323.
Order Task
7.2.4 Verification
You can initiate a cascaded conference in the SMC2.0 to verify the networking configuration.
Step 1 Initiate two common conferences on the SMC2.0 and specify a VP8000 series MCU and a
VP9000 series MCU as the main MCUs for them respectively.
1. On the home page, choose Conferences > New Conference.
2. Click Advanced Settings on the New Conference page.
The dialog box shown in Figure 7-6 is displayed.
NOTE
Enter the string following 9000 in the Label text box. Otherwise, the cascaded conference will fail
to be initiated.
For Conf1, set Device type to Lower-level participant, and set Label to the Conf2
access number (01010183).
For Conf2, set Device type to Upper-level participant, and set Label to the Conf1
access number (075510182).
----End
Network Description
l On the SMC2.0 interconnection network, the SMC2.0 manages MCUs and participants
in a unified manner.
l Interconnected SMC2.0s can communicate with each other and schedule conferences
across regions.
SMC2.0_A 192.168.2.192
SMC2.0_B 192.168.2.193
SMC2.0_C 192.168.2.194
Step 3 Choose Interconnection Settings. On the Basic Settings tab page, set required parameters, as
shown in Figure 7-10.
NOTE
To enable the interconnection function, it is recommended that you select Officical use certificate for
Certificate source and upload a certificate. The certificate's encrypted password must meet complexity
requirements. If you have not bought a commercial certificate yet, select Self-signed certificate for
Certificate source.
Step 6 Set Number Segment Type and Matching Criteria and click OK.
Step 7 Repeat the preceding steps to enable the interconnection function for SMC2.0_B and
SMC2.0_C.
----End
Configuring Interconnections
This section describes how to interconnect two SMCs (SMC2.0_A and SMC2.0_B used as an
example here).
Step 2 Choose Devices > Remote SMC and click Add Remote SMC.
Step 3 Enter the SMC2.0_B IP address in the IP address field and click Next.
NOTE
If you select Self-signed certificate for Certificate source when enabling the interconnection function,
the dialog box shown in Figure 7-12 will be displayed. In this case, click Yes to go to the next step.
Step 4 On the SMC2.0_B configuration information page shown in Figure 7-13 that is displayed,
check the information and click Next.
The system returns to the remote SMC list, in which Authentication Status of SMC2.0_B is
Awaiting confirmation.
Step 5 Log in to SMC2.0_B as the admin user and choose My Tasks > My to-do list >
Interconnection Application.
Step 6 Locate the interconnection request from SMC2.0_A and click Confirm, as shown in Figure
7-14.
Step 7 Choose Devices > Remote SMC. In the remote SMC list, SMC2.0_A is in connected state.
In the remote SMC list on SMC2.0_A, SMC2.0_B is also in connected state, as shown in
Figure 7-15.
Step 8 Repeat the preceding steps to configure interconnections between SMC2.0_A and
SMC2.0_C and between SMC2.0_B and SMC2.0_C.
----End
Configuring default rights for interconnection users actually means configuring organizations
that are accessible to interconnection users on remote SMCs. When scheduling
interconnection conferences, interconnection users can select only participants under these
organizations to join interconnection conferences.
Step 3 Choose Default User Rights and click the Interconnection user tab.
Step 4 Select organizations under Accessible node, as shown in Figure 7-16. Then click Save.
----End
7.3.4 Verification
This section verifies the interconnection result by scheduling interconnection conferences on
SMC2.0_A.
Before scheduling an interconnection conference, ensure that interconnected SMC2.0s are
time synchronized and participants to join the conference have registered with the same SC or
neighboring SCs.
Step 5 On the Participants tab page, select local participants to join the conference.
Step 6 On the Remote SMC tab page, select Remote participant. In the participant list, select
remote participants to join the conference.
NOTE
To add remote participants, you can also select Remote SMCs and add the remote SMC to the local
SMC. Then the administrator of the remote SMC can add remote participants on the remote SMC. The
information about these participants will be synchronized to the local SMC. The administrator who can
perform this task is specified when the conference is initiated. For details, see Preset Remote SMC
Administrator under 7.2 Presetting a Conference in the HUAWEI SMC2.0 V500R002C00
Administrator Guide.
----End
7.4.1 Scenario
When the SC is deployed in a two-node cluster, services are smoothly switched between the
active and standby SCs to ensure service continuity.
Network
Figure 7-18 shows the network of the SC two-node cluster.
Network Description
l The active and standby SCs are deployed in the same network segment and managed by
the SMC2.0 in a unified manner.
l The active and standby SCs use separate management IP addresses and service IP
addresses, but share the same floating IP address.
l On a network where traversal between public and private networks are allowed, the
active and standby SCs with dual network adapters use floating IP address IP1 to provide
registration and calling services on the private network and use floating IP address IP2 to
provide registration and calling services on the public network.
Table 7-10 provides the data plan for the two SCs.
NOTE
l To specify the SC where a configuration operation is performed, this section uses SC1 to stand for
the active SC and SC2 to stand for the standby SC. The two SCs are identified as only one SC on the
SMC2.0.
l The management IP addresses, service IP addresses, and floating IP addresses of the active and
standby SCs must reside on the same network segment. (Note: When configuring the active/standby
relationship, ensure that floating IP addresses you select are not occupied.)
l After the active/standby relationship is configured for the two SCs, their network settings cannot be
modified.
l When configuring the active/standby relationship, configure SC1 as the active SC and then
configure SC2 as the standby SC.
l When removing the active/standby relationship, run the following command on the standby SC and
then on the active SC.
system-view hot-standby disable
Step 1 Log in to SC1 and SC2 using the SSH tool. The default user name and password are admin
and Change_Me.
Step 2 Check the license status.
Run the following command to check the license status on SC1 and SC2, respectively. Ensure
that the license statuses on the active and standby SCs are the same, excluding the value of
esnNum. If their statuses are different, the configuration will fail.
display license
maxRegisterNum:10000
maxSoftRegisterNum:10000
maxESDKNum:0
maxTraversalCapacity:300Mbps
dateExpiry:2016-01-31
status:DEMO_STATE
esnNum:057612E84C********6AA000E95A510A1CAAE47A
sipBusinessBound:0
forbiddenSipTls:0
swid:
registerCount:0
esdkCountUsed:0
traversalCapacityUsed:0kbps
NOTE
Save the modification and exit. Then run the following command to restart the network for the
modification to take effect:
service network restart
– When SC1 is installed on a REDHAT operating system, run the following command
to change the value of ifcfg-eth0 in /etc/sysconfig/network-scripts/:
vi /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
HWADDR=00:0C:29:42:CC:13
TYPE=Ethernet
UUID=a111c111-1111-1cfd-ae1c-111a1111a1f1
NOTE
Save the modification and exit. Then run the following command to restart the network for the
modification to take effect:
service network restart
If the service IP address types or quantities of SC1 and SC2 are different, run the following
commands to delete or add corresponding IP addresses:
system-view sys-config security-config service-ip add ip 192.168.1.1
system-view sys-config security-config service-ip delete ip 192.168.1.1
NOTE
After deleting or adding an IP address, run the reboot command to restart the SC for the operation to take
effect.
Step 5 Run the following command to set SC1 as the active SC. Table 7-11 describes the parameters.
system—view hot-standby enable mode 1 share-key admin123456789123456789 local-IP1
192.168.1.1 virtual-v4ip1 192.168.1.3 virtual-v6ip1 FEC0:0:0:0:192:168:1:3 local-IP2
11.11.11.1 virtual-v4ip2 11.11.11.3 virtual-v6ip2 FEC0:0:0:0:11:11:11:3
execute success
----End
Step 3 In the IP Address field, enter the management IP address of the active or standby SC (active
SC used as an example here) and click Next.
NOTE
The authentication information needed for adding the SCs to the SMC2.0 is provided in Table 9-1. You can
change the connection password by following the instructions in the HUAWEI SMC2.0 V500R002C00
Security Maintenance.
Step 4 Set Device Name for the active SC, as shown in Figure 7-19.
----End
Step 3 Run the following command to obtain the license invalidation code:
display revoke-ticket
LIC2016071401A850:11E111111DAF1D1A11D1DDD1B111F11A1C1A1E1F
Step 4 Log in to Huawei ESDP and choose License Commissioning and Maintenance >
Invalidate License Regenerate. Use the invalidation code to invalidate the license following
the onscreen instructions.
----End
NOTE
It is recommended that you apply for a license file that contains the licenses of both the active and
standby SCs. Therefore, you only need to import one license file.
Step 1 Click the name of the active SC to access the Details tab page.
Step 2 Click Import License.
The Import License dialog box shown in Figure 7-21 is displayed.
----End
7.4.4 Verification
You can add a participant to the SMC2.0 and register the participant with the SC two-node
cluster to verify the SC two-node cluster configuration.
If the participant is successfully registered with the GK, the SC two-node cluster
configuration is successful.
----End
8 Troubleshooting
Possible Causes
The port used to log in to the SC is incorrect.
Procedure
Step 1 Verify that the port used to log in to the SC is port 122.
Step 2 Check the user name and password used to log in to the SC.
NOTE
The default user name and password are admin and Change_Me respectively.
----End
Possible Causes
l The port settings on the SMC2.0 and MCU are different.
l The connection modes or passwords set on the MCU and SMC2.0 are different.
Procedure
Step 1 Check whether the MCU connection type is set to SMC2.0/IMS.
1. Log in to the MCU web interface and choose Settings > System > Connection
Management.
2. Check whether the value of Connection type is SMC2.0/IMS.
Step 2 Check whether the same port is specified on the SMC2.0 and MCU for their connection.
1. Log in to the MCU web interface, choose Settings > System > Connection
Management, and check the value of Port.
2. Log in to the SMC2.0 web interface, select the MCU you want to check, click Edit
MCU, and change the value of Port to the port number that you see in the previous step.
3. Click Save and check whether the MCU gets online. If it is still offline, repeat Step 3.
Step 3 Check whether the same connection mode and password are specified on the SMC2.0 and
MCU for their connection.
1. Log in to the MCU web interface and choose Settings > System > Connection
Management.
2. Check the values of Connection mode and Connection password.
3. Log in to the SMC2.0 web interface, select the MCU you want to check, and click Edit
MCU.
4. Set Connection mode and Connection password to the values you have obtained in
step 2.
5. Save the modifications. The system returns to the MCU list page, on which the MCU
gets online, indicated by .
----End
Symptom
After a participant is added to the SMC2.0, it fails to register with the specified GK, as
indicated by .
Possible Causes
The participant numbers on the participant and SMC2.0 are inconsistent.
Fault Diagnosis
Log in to the participant endpoint web interface. Choose Maintenance > System Status >
Line Status. Take the troubleshooting measures based on the GK failure message displayed.
Confirm that the participant numbers on the participant and SMC2.0 are inconsistent.
NOTE
When a participant is added to the SMC2.0 as a manageable participant, its number is configured on the
SMC2.0. Unless manually changed on the participant endpoint, the number on the participant is the
same as that on the SMC2.0. When a participant is added to the SMC2.0 as an unmanageable
participant, all participant parameters are manually set on the participant and SMC2.0. In this case, you
must pay attention to the consistency between the parameter settings. In this example, an unmanageable
participant is used to describe how to check the parameter settings on the participant and SMC2.0.
Procedure
Step 1 Log in to the SMC2.0 web interface. Choose Devices > Participant. In the participant list,
select the desired participant and click Edit Participant. In the displayed dialog box, change
the values of Label, as shown in Figure 8-2.
Step 3 Log in to the participant endpoint web interface. Choose System Settings > Protocol > H.
323/SIP Settings. Change the values of E.164 so it is consistent with that of Label on the
SMC2.0, as shown in Figure 8-3.
Step 5 Check whether the participant successfully registers with the GK.
----End
Symptom
After a user enters an MCU address on the SMC2.0 web interface to search for that MCU, the
search fails, and the message "SNMP search timed out" is displayed.
Possible Causes
The SMC2.0 uses SNMP to search for MCUs. If the SNMP settings on the SMC2.0 and an
MCU are consistent, authentication cannot be passed and therefore the search for that MCU
fails.
Procedure
Step 1 Retain the default SNMP settings on the SMC2.0. (The default settings are listed in Table
9-1.)
Step 2 Use an SSH client to log in to the MCU. Run system-view snmp-config to set the SNMP
connection mode to V3 Mode.
Step 3 Run system-view snmpv3-user-config to modify the SNMP settings on the MCU so they are
the same as those on the SMC2.0, as shown in Table 8-1.
select operation User whose settings you want to Select 1, which indicates that you
type modify. want to modify the SNMPv3 user
settings.
add user name New user name. Enter v3user so the settings are
consistent with the default SMC2.0
settings.
enable des Whether to use DES. Select 1, which indicates that you
want to use DES. This is consistent
with the default SMC2.0 settings.
----End
Symptom
After a user enters the device address to search for a videoconferencing participant, the search
fails.
Possible Causes
Determine the possible cause based on the displayed error message.
l Cause 1: The authentication settings on the participant and SMC2.0 are inconsistent,
resulting in an authentication failure. If this is the case, the message "The device user
name or password is incorrect." is displayed.
l Cause 2: The SNMP settings on the participant and SMC2.0 are inconsistent, resulting in
a connection failure. If this is the case, the message "SNMP search timed out." is
displayed.
Fault Diagnosis
When the SMC2.0 attempts to connect to participants using HUAWEI 9000 or HUAWEI
TEX0 videoconferencing endpoints, the endpoints verify the authentication information. If the
SMC2.0 settings are inconsistent with the API settings on those endpoints, the authentication
fails, and no connection can be set up.
Procedure
Step 1 If cause 1 results in the search failure:
1. Log in to the participant endpoint web interface. Choose System Settings > Personal.
Record the API user name and password.
2. On the SMC2.0's participant search page, change the settings of User name and
Password for Authentication so they are the same as the settings on the participant.
3. Click Next to search for the participant again.
3. Save the settings. On the SMC2.0, search for the participant again.
----End
Symptom
After a user enters a device address to search for a telepresence participant, the search fails.
Possible Causes
Determine the possible cause based on the displayed error message.
l Cause 1: None of the IP addresses for Network Manager is set to the SMC2.0 IP
address on the telepresence participant endpoint. If this is the case, the message "The
SMC2.0 cannot communicate with this device" is displayed.
NOTE
The SMC2.0 uses non-SNMP mode (HTTP or HTTPS) to search for telepresence participants. If
the network manager on the telepresence participant endpoint is not set to the SMC2.0, the
SMC2.0 cannot connect to the telepresence participant.
l Cause 2: The authentication settings on the participant and SMC2.0 are inconsistent,
resulting in an authentication failure. If this is the case, the message "The device user
name or password is incorrect." is displayed.
l Cause 3: Perform non-SNMP search (connection time will significantly increase) is
not selected on the SMC2.0. If this is the case, the message "SNMP search timed out." is
displayed.
Procedure
Step 1 If cause 1 results in the search failure:
1. Log in to the telepresence host web interface of the participant. Choose System Settings
> Users and set one of the IP addresses for Network Manager to the SMC2.0 IP
address.
2. Save the settings. On the SMC2.0, search for the participant again.
----End
Symptom
After a user enters a recording server address on the SMC2.0 web interface to search for that
recording server, the search fails, and the message "Message sending timed out." is displayed.
Possible Causes
The authentication settings on the recording server and SMC2.0 are inconsistent, resulting in
an authentication failure.
Procedure
Step 1 Record the SMC2.0's default recording server authentication settings, as described in Table
9-1.
Step 2 Log in to the recording server web interface. Choose System > System Settings > Basic
Settings > Management.
Step 3 Modify the settings of Connection account and Connection password so they are consistent
with those on the SMC2.0, as shown in Figure 8-5.
----End
Symptom
On the SMC2.0 web interface, when a user configures directory services and clicks Test
Directory Service Configuration, the message Test failed. is displayed.
Possible Causes
l The LDAP server IP address or authentication information is incorrect.
l The value of Base DN is incorrect.
Procedure
Step 1 Verify that Server IP address, User name, and Password are correctly set.
Symptom
Although the SMC2.0 services start properly, HTTP errors occur during your login to the
SMC2.0 web interface.
Possible Causes
The Internet Information Services (IIS) have not been enabled on the SMC2.0 server.
Procedure
Step 1 On the SMC2.0 server, choose Start > Administrative Tools > Server Manager > Roles >
Add Roles.
The Add Roles Wizard window is displayed, as shown in Figure 8-6.
Step 3 Select Web Server(IIS) and follow the onscreen instructions to complete the configuration.
NOTE
After adding the Web Server(IIS) role, log in to the SMC2.0 web interface using a browser. If the error
persists, reinstall the SMC2.0.
----End
Symptom
You use Internet Explorer to log in to the SMC2.0, but the SMC2.0 web interface is
incorrectly displayed.
Possible Causes
The SMC2.0 version on the server has changed but the Internet Explorer client has not deleted
its cache.
Procedure
Step 1 Open Internet Explorer. Choose Tools > Internet Options.
The Internet Options dialog box is displayed, as shown in Figure 8-7.
----End
Symptom
When a user attempts to add a participant on the SMC2.0, the "Message sending timed out"
message is displayed. If the user attempts to add the participant on the SMC2.0 again, the
participant is added successfully.
Possible Cause
When the SMC2.0 is setting up a connection with a participant device, Windows authenticates
the Certificate Authority (CA) certificate, which may cause a communication timeout
between the SMC2.0 and the participant.
Solution
l Install the CA certificate provided with the SMC2.0.
For the installation procedure, see the Security Maintenance.
l Disable the function to automatically update the root certificate in Windows.
a. Log in to the SMC2.0 server as the system administrator.
b. Choose Start > Run.
c. Enter gpedit.msc and press Enter.
d. In the displayed Local Group Policy Editor window, choose Computer
Configuration > Administrative Templates > System > Internet
Communication Management > Internet Communication Settings.
e. In the settings list on the right, right-click Turn off Automatic Root Certificates
Update and choose Edit from the shortcut menu.
f. In the displayed Turn off Automatic Root Certificates Update window, select
Enabled.
g. Click OK.
----End
9 Default Settings
By default, the SIP conference control function is disabled for MCUs. After the function is
enabled, conference control operations can be performed on SIP multipoint conferences. For
example, you can change a point-to-point conference to a multipoint conference or control a
conference on a TE Desktop.
2. In Host Name (or IP address), enter the IP address of the GE0 port on the main control
board, for example, 192.168.0.109.
NOTE
The default IP address of the MCU's GE0 port on the main control board is:
– VP9660: 192.168.2.1 (slot 0) / 192.168.2.2 (slot 1)
– VP9650: 192.168.2.1
– VP9630: 192.168.2.1
If the VP9660 has active and standby main control boards, use the active one for logins.
3. Select SSH for Connection type. Use the default value for Port.
4. Click Open.
The login window is displayed.
5. Enter the user name and password and press Enter.
NOTE
The default user name and password are admin and Change_Me respectively. The account is
locked out for five minutes by default if you enter incorrect passwords three consecutive times
when attempting to log in to the MCU.
Step 2 At the <HUAWEI VP9650> prompt, enter system-view conf-policy enable-sip-confctrl and
press Enter.
Step 3 At the enable sip confctrl{0:disable 1:enbale}[0]: prompt, enter 1 and press Enter.
The following message is displayed:
Info:set enable sip confctrl success!
The message indicates that the configuration is successful.
Step 4 At the <HUAWEI VP9650> prompt, enter save and press Enter.
Step 5 At the are you sure to save config?(y/n): prompt, enter y and press Enter.
The following message is displayed:
Info:save config success!
The message indicates that the configuration is successfully saved.
----End