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>


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


The conference site can’t connect caused by the V.35 board fault

Publication Date:  2012-09-22 Views:  13 Downloads:  0
Issue Description
There are two conference sites can’t connect before the test.
Alarm Information
Handling Process
Because this problem has been reared up in the past, we can do as it used to be. Check MCU and the system data of terminal firstly, ok; Then check if the tab is loose connection, ok; Then having the local loopback of board and line, ok; So we can ensure the problem is transmission site. After testing by BER tester, the path is OK. Looking carefully, these two sites is always normal and oppose to the same E1 interface. So we can ensure it’s V.35 board’s problem. It comes to normal after replacing.
Root Cause
If we find the two users in the board have problem which is accessed by V.35, we should think about the fault of this board. (Although there is no alarm in MCU operation bench).