Connectivity problem on Tandberg 1700MXP

[Q-Bee]

Any push in the right direction would be greatly appreciated. I have an MCU and bridge calls for a good number of endpoints and a growing number of desktop Tandbergs. A problem I keep experiencing is a video connectivity issue. We use them strictly IP, no ISDN, no gatekeeper, or anything else. My problem is that sometimes when I connect the tandberg from my bridge or from its IP interface I get no video in or out. When trying to connect at 384 (which is std for us) it will only bond 256kbps (no video). Slowing down my speed does not help. I have called our network guys to make sure the port is opened 100/Full, all settings seem to be correct. Just no video. However, when I go back later (this last time it was @ 25 mins) it connects up with no problems at all, audio, video, 384kbs. Please help. I'm thinking this is something with my network. Any suggestions?????? :confused:

[JustBuck24]

What type of bridge are you using and what software ver is it running? What version software are you running on the MXP units?

[Q-Bee]

I don't know why but we are running on Polycom MGC 100s, software ver. 8.0.0.14 and the MXP is running on F6.0 NTSC. All of our desktops and the CODECs running in our rooms are Tandberg. I don't know who before me chose to use Polycom for our bridges. Might this be a part of the problem?

[helix-2000]

When you get the no video have you had someone check the codec to see what call stats look like?

[Q-Bee]

Sitting in front of the MXP I'm looking at a black screen that says "No Incoming Video" and when I remote into it to look at the call's System Status it says in red next to video out "No Video". Even though I can monitor both sites from our hub there is no video in or out at that Tandberg.

[JustBuck24]

Either upgrade your MXPs to something other than f6.0 or telnet into the MXP systems and turn off RCDO.

[Q-Bee]

Boy this probably sounds amateurish...what is RCDO?

[Sean Lessman]

Either upgrade your MXPs to something other than f6.0 or telnet into the MXP systems and turn off RCDO.

Or run the latest software from the Accord where they should have fixed the problem.

Sean

[Sean Lessman]

Boy this probably sounds amateurish...what is RCDO?

It is an additional codec based on H.264 and the use of it is specified within H.241 Annex B. In short, its another video codec in addition to H.261, H.263 and H.264. The Accord sees it in the capability set of the MXP and instead of ignoring (like they would with AAC-LD or any of the other caps they dont understand) the Accord turns off the video.

Polycom has fixed this in the Accord last I heard.

Sean

[Q-Bee]

Thank you so much - it worked!!!

[11B-33T]

Thank you so much - it worked!!!

What worked? Turning off the RCDO, upgrading your codec SW, or upgrading the MCU?

[Sean Lessman]

What worked? Turning off the RCDO, upgrading your codec SW, or upgrading the MCU?

Both should work. If you turn off RCDO, the TANDBERG will remove it from the capabilities declaration thereby not confusing the Accord and causing it to choke.

Or...use the Accord software where they properly handle capabilities they don't support.

Sean

[Q-Bee]

I went into the Tandberg and turned it off. Thx again!