MGC-100 Primary Timing Source

[TJvtc]

I'm using one of my H.320 circuits as my Primary Timing source for the MGC-100. Whenever that link is disconnected on the bridge or drops due to a hard fault it's causing all the other participants on the bridge to go faulty connect with frozen or blue video. The only change on the bridge lately was an upgrade from version 6 to version 8 on the MGC Manager. I was just wondering if anyone else was having the same issues.

[Slimey]

Are the other endpoints h320? This is normal and expected when received clock is lost, if it happens quite often you may want to have your service provider test the circuit.

[Joe Vallender]

What version are you running on the MCU (you say v8 on the MGR)? The assumption is you have a backup clock source defined as well, correct? That circuit might have to be checked as well.

[TJvtc]

We are using version 8 on the MCU as well. The primary and secondary are both running to the same location. We have several other H.320 circuits, but these are the only links that we have going back Stateside. If I use a local (more reliable) circuit to provide my timing, will that effect my conferencing back to the US?

[Shastac64]

Try moving your timing to an unused H320 position.