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 126.96.36.199: '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?
Proximity 3.0.7 primarily addresses issues with false positives in the ultrasound pairing message decoder. This was reported in to us in the support forums.
The steps taken to address this are:
Require higher coinfidence when receiving ultrasound...
Cisco Proximity 2.0.8 includes some changes to the Windows installation package to facilitate mass deployment. None of these changes break backwards compatibility. The changes are these added msi properties:
LAUNCHPROXIMITY (Default: 1)
If set to 0, pr...
The Cisco Technical Support mobile application for iOS and Android devices provides access to our most frequent support tools and information while you are on the go. Several features are freely accessible by anyone including access to the Cisco...