-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Poly Video Conferencing
- Meeting Room Solutions
- Polycom RPD Issue with new firmware

Create an account on the HP Community to personalize your profile and ask a question

06-05-2017 05:55 AM
Hello team,
May I know is there any known issue of new version RPD?
When I use version "RPD-release_3.7" with my Yealink T49G, video from the other side can't be seen.
Downloading to previous version "RPD-release_3.3_50871" or ealier version solve the issue imediatelly.
Pcap trace has been attached.
Regards,

06-05-2017 08:41 AM
In your packet trace:
DynamicRTP-Type-97 and 123 packets are coming in from 10.15.151.2
Is it possible that traffic is being dropped between the packet capture point and the endpoint?
You might provide a PCAP file of a good call for comparison.

06-06-2017 03:33 PM
To confirm my interpretation of the scenario:
Polycom RPD 3.3 H.323 calling Yealink SIP T49G, video received fine from T49G
Polycom RPD 3.7 H.323 calling Yealink SIP T49G, video failing from T49G
Packet captures are from the Polycom RPD end but where exactly, the Desktop PC or a intermediary switch/router/firewall or gatekeeper?
What do you have doing the H.323 to SIP conversion? The gatekeeper the RPD is registering to?
The packet captures appear similar with TCP/UDP port numbers changing as the calls advance thru the alloted port ranges.

06-06-2017 08:25 PM

06-06-2017 11:19 PM
If you have purchased a license for your RPD then you should probably open a ticket with Polycom. They might be able to determine the difference between RPD 3.3 and RPD 3.7 that is causing the issue. May be simple as a configuration setting.
In the RPD log files, the 3.7 calls contain numerous 'SendKeyFrameRequest, GDR but the frequency is too high.'s and the 3.3 calls do not. There may be some problem with the incoming video frames and the RPD 3.7 interpreting them.