topic Google meet/ hangout Stun servers aged-out in General Topics

Google meet/ hangout Stun servers aged-out

MattDaviesVSI — Thu, 11 May 2023 16:37:02 GMT

We have noticed an issue especially with Google Meet/Hangout when we often get one way audio.

I can see from the traffic logs that Stun servers are showing aged out and the application is stun. However it is using a non standard port 19303

I suspect this is the cause of the issue.

How can I ensure the traffic is correctly identified and allowed though on this non standard port ?

Or is there something else I should look at to resolve this issue ?

Thanks

Matt

Re: Google meet/ hangout Stun servers aged-out

BPry — Thu, 11 May 2023 18:51:30 GMT

@MattDaviesVSI,

aged-out is the standard response for stun traffic. We don't allow 19303 outbound and I haven't heard anyone complain about Hangouts or Meet not working, but at the same time I don't have that many people using those services.

You could always create a rule specific to stun on 19303 and allow the app-id stun on the custom service object for 19303. I'd do that as a test machine and see if that fixes the issue though; I'm not certain that you'll see any change in behavior.