01-06-2020 06:49 PM
Our customer has found that the proximity client is randomly trying to pair with different public IP addresses. See below from the PC Proximity logs:
2019-12-17 10:06:34.499 Info: New token for codec 81.88.106.203: '0611'.
The PC attempts a HTTPS session and fails (expected due to their security). Normal pairing with local VC units is working OK.
Home Users with no VC unit nearby are getting the same issue. The customer is getting the alerts from their HTTP proxy since it looks like some sort of malware trying to reach the internet. They are mainly using Dell laptops.
They have also tried a spetrum analyser to see if there is anything broadcasting on the 20-22khz range but did not see anything.
Is there any other occurrences of this issue, is it a known problem?
01-17-2020 09:05 PM
Hi Ray,
just found this, and will follow up with the team immediately. We also have a TAC case on this, so we should get an update fairly soon.
-Henrik
02-21-2020 06:26 AM
This should have been fixed in version 3.0.7 which was released early this week. See the release notes for 3.0.7 for more information.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide