Hello,
I have opened a TAC Case with Cisco about the issue when I launch a multipoint session (Telepresence Server 8710) with some devices like a HDX6000 HD, Cisco SX20 and Cisco CTS500.
The issue is with the TS8710 version 4.1(2.29), with the version 3.1(1.95) is working fine. When SX20 or CTS500 try to share content with all devices involve in the multipoint session, the HDX6000 HD doesn't receive anything, a black screen.
Cisco said the following:
I analyzed the logs by looking into the pcaps only but managed to see what I wanted to see ultimately.
So what I see the following:
So for the CTS the same ports are used for video and content but for Polycom it does use different ports, however we just see the correct RTP traffic. Also had a look on the release notes of the latest Polycom HDX software (http://downloads.polycom.com/video/hdx/ReleaseNotes/hdx_rel_notes_v3_1_7.pdf) but could not see any recent improvements for interoperability with Cisco. In fact I did not see any recent updates, besides OpenSSL updates in it so I don't know if Polycom will bring out new updates on it.
What we need to do now is to ask Polycom why it does not display the content video as we see the RTP traffic going to the device but then it does not get displayed at all. Because we don't have a Polycom account for support and you are the current holder of the Polycom endpoint(s), it is best to open a new case at Polycom for this where you explain that we send the RTP traffic to it but then it does not get displayed at the Polycom endpoint. Note also that you only see this with the HDX 6000 endpoint as the other ones still seem to work properly. It might seem like an issue at our side but we see that the RTP traffic is sent correctly to the Polycom endpoint, from there on it is currently the question why Polycom does not display this content. If you open a case with Polycom, then put the Polycom case-owners in our loop so we can have a look with the Polycom responsible on this issue.
We have some polycom models, like a HDX7000, HDX9000,... and all devices are working fine except the HDX 6000 HD.
Don you find some issues with this device and this scenario?
Thanks in advance.
Regards.
Solved! Go to Solution.
Hello maromero,
welcome back to the Polycom Community.
I am aware that you mention the 3.1.7 release notes but it is still always useful to include the currently used software version as issues experienced may already be addressed in a newer release.
You can raise a Polycom support case via your Polycom reseller for out of warranty devices usually via a Pay per Incident ticket. Your Polycom reseller should be able to assist you so we can look at the logs if required.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
If official support is required please check how to phone or open a case here
----------------Hello maromero,
welcome back to the Polycom Community.
I am aware that you mention the 3.1.7 release notes but it is still always useful to include the currently used software version as issues experienced may already be addressed in a newer release.
You can raise a Polycom support case via your Polycom reseller for out of warranty devices usually via a Pay per Incident ticket. Your Polycom reseller should be able to assist you so we can look at the logs if required.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
If official support is required please check how to phone or open a case here
----------------check the call preference mobe...
HDX 6000 has different content decoding capabilities than other HDX series systems. HDX 6000 isn't necessarily capable of decoding content video bitstream that HDX 900x or HDX 8000 can decode.
"Black" video typically suggests that H.239 token exchange was done as expected and HDX 6000 is ready to receive and decode content video; however, the HDX 6000 is either not receiving RTP (which doesn't appear to be the case here) or HDX 6000 is unable to decode the bitstream for one reason or another.