I am noticing an issue were clients are using Google Hangouts, but the APP-ID is detecting the session as STUN over UDP/TCP port 19302-19309, instead of the APP-ID signature of google-hangouts-audio-video. Has anyone else noticed this behavior?
The traffic is being blocked, so I am creating a custom service for those UDP ports to apply on a specfic rule for STUN.
Has this occured after the latest content update (749) ?
There was a modified application that depends on stun ...
You could confirm this by reverting to the previous content version and test again.
You might want to reach out to support to have this investigated.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!