No relevant resource is found in the selected language.

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


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


Clock issue cause system often drop off form conference

Publication Date:  2012-09-18 Views:  158 Downloads:  0

Issue Description

After certain system take charge of dispatching the conference, all of the terminal keep on dropping off from the conference. 

Alarm Information


Handling Process

Consider the situation and determine the problem as clock synchronization issue.
1. Change the clock to internal clock type at the MCU background.
2. Do not add “00” port when our company setting local meeting.
After taking the step above, the problem disappeared.

Root Cause

This problem is caused by the clock influence, because the superior MCU has been turned on, though this system’s MCU is not allowed to attend the meeting, and will not get any image and sound signal. But still, there is code flow to receive. So, when this system’s MCU receive this code flow, it will consider the superior MCU has been turned on, and it can attend the meeting, and choose the superior MCU clock as its dispatching conference clock. Although the conference dispatched on this system MCU’s background is local network conference, and does not include the superior MCU. But the system still get clock from “00” port. This is the reason why local network meeting can’t synchronize very well, and often drop off the conference.