Create an account on the HP Community to personalize your profile and ask a question
05-01-2018 09:47 AM
I have tried to raise a support case on this but have been blocked by requests for serial number (License key is unrecognised), and the contact a call centre link (as well as the support pages for RDP at the moment) end up in a 404.
When configuring RDP PC client in Windows 10 (v3.9) to use SIP TCP (no proxy registration) and a manual NAT override, the SDP Contact and Origin lines get completely managed. Please see the obfuscated images files from Wireshark, however the issue is also confirmed from the RPD logs.
It looks as if the replacing of test has gone awry. Hopefully this can get to the right people as this is a good product.
05-03-2018 04:24 AM
welcome to the Polycom Community.
I have forwarded this to Engineering and they believe this is a bug.
I will keep updating this post.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Polycom Global Services
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.
Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
Didn't find what you were looking for? Ask the community