SX20 video quality issues in multi-site calls

[jdarsigny]

We have an SX20 running in an environment of mixed 6000mxp and C40 codecs with an old Codian/Tandberg bridge.  Whenever this codec is involved in a multi-site call through our bridge, we have video quality issues when the floor changes from one site to another.  Pixilation which can become extremely pronounced if floor changes are rapid and can be accompanied by audio loss in those extreme situations.  This is the only site that experiences this problem.  Latency is not an issue, nor is bandwidth.  Any experience of this issue or suggestions for settings or hardware issues that could play in to this on the SX20?                  

[William Bell]

What happens in a p2p call with the SX20?

BW and Latency may be fine but have you checked the physical network layer? Do you have a duplexity mismatch at the access port? Are you seeing errors on the SX20's network access port or on uplinks between the SX20s access switch and the rest of the world?

What does the video look like on the SX20 side of things when you see pixilation on the remote codec?

My first thought goes to a physical layer issue. But that could be just me.

HTH

-Bill (http://ucguerrilla.com)

[jdarsigny]

Thanks Bill for weighing in.  P2p calls are fine, no problems with pixilation.  No errors on either port, no errors in the TMS logs during calls.  Further testing since my post; multi-site calls of up to four parties without the use of the bridge do not have this issue.  Same call using our bridge to facilitate, we get this problem.  This problem is only seen on the SX20.  Images from the SX20 are crystal clear with no issues and no other sites experience the issue, bridge or no bridge.

[Wayne DeNardi]

Hi Jim,

Over in the telepresence part of the forums,  I can recall someone experiencing a similar issue when a bridge was involved in the call.  (I'll see if I can find the thread reference).

If I recall correctly, it was due to the software version running on the MCU and an update to the latest version fixed the issue.

What version of the software are you running on your bridge(s) and endpoints?

Wayne

--

Please remember to rate responses and to mark your question as answered if appropriate.