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.


MVPA single board malfunction causing starting conference malfunction

Publication Date:  2012-09-20 Views:  106 Downloads:  0

Issue Description

During certain opening, emerge the following phenomenon:
1. Main MCU having sub MCU and terminal, having a meeting, suddenly all other MCU and terminal left the conference except local terminal. The operator didn’t make any operation.
2. We can see this phenomenon too in the conference list.
3. 10 seconds later, other MCU and terminal join the conference again.
4. Several minutes late, repeat the phenomenon above again and again.

Alarm Information

MVPA board alarm: can’t find board

Handling Process

1. Because there is no possibility that so many meeting place and MCU gone wrong or operator control the meeting place to disconnect the meeting. So the problem should be on main MCU side.
2. Restart the conference, malfunction remain the same.
3.Check the MCU configuration of MCU, find out he MCPA board light turn to yellow in diagnose.
4. Check hardware in MCU side, find out MVPA board alarm light keeps on shinning.
5. Power down the MCU, then plug and unplug the single board, restart, single board alarm light off, restart the conference, malfunction disappear.

Root Cause

We set the adapt rate when having meeting, though we didn’t use terminals that have different rate, but as the necessary resources that having a meeting, MVPA is needed. When MVPA is malfunction, MCU will determine that the state is not enough. And force other point of the meeting to cut off. When found the MVPA, the conference will start again.