No relevant resource is found in the selected language.

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

Reminder

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

upgrade

Clock Problems Cause Delayed Initiation of Conferences in SMC2.0 Interconnection

Publication Date:  2019-04-10 Views:  11 Downloads:  0
Issue Description

Version: HUAWEI SMC2.0 V500R002C00

Networking overview: A provincial SMC2.0 is at the upper level. A municipal MCU is at the lower level. The network is a dedicated network, which has no firewall or NAT and provides reachable routes to the SMC2.0, MCU, and terminals.

Networking diagram:

Configuration scripts:

SMC2.0 interconnection relationships can be configured only after their interconnection capabilities are enabled.

Log in to the SMC2.0 web interface as user admin. (Other administrator accounts do not have the rights to configure interconnection.)

Choose system > configure.

Click Interconnected configuration and click the basic configuration tab. Refer to product documentation for normal configuration.


Fault symptom:

SMC2.0s are interconnected. After the upper-level SMC2.0 initiates an MCU cascaded conference, the lower-level SMC2.0 cannot initiate a conference immediately. The lower-level SMC2.0 cannot join the conference until one minute later.

Alarm Information
No alarm information.
Handling Process

Check the configurations of the upper-level and lower-level SMC2.0s. Successful initiation of a cascaded conference proves that SMC2.0 interconnection configuration is correct. Check the time of the SMC2.0 servers and find that there is one minute of time difference between the upper-level and lower-level SMC2.0s. This problem delays the conference initiation for one minute.

Root Cause

There is one minute of time difference between the upper-level and lower-level SMC2.0s. This problem delays the conference initiation for one minute.

Solution

User the upper-level SMC2.0 as the clock server, so that its time is used by all lower-level SMC2.0s. After the clocks are synchronized, conferences can be immediately initiated in SMC2.0 interconnection. The fault is then rectified.

Suggestions

When several SMCs are interconnected, use the upper-level SMC2.0as the clock server (or use a unified clock server on the entire network). In this way, the time of lower-level SMC2.0s is synchronized with the upper-level SMC2.0. This will prevent delayed initiation of conferences due to clock difference.

END