First WebRTC call after machine boots up fails due to Chrome UDP socket error: 10053 (WSAECONNABORTED)

Hey there,

We are a CCaaS software provider. Recently our customers reported for a certain set of users faced call setup failure on first calls that they take using Chrome just after machine restart. We dug deeper into Chrome runtime logs and found out the root cause, it was happening because of UDP socket failure with UDP socket error: 10053 (WSAECONNABORTED). This issue did not reproduce for Firefox.

That specific code means the following as per learn.microsoft.com/en-us/windows/win32/winsock/windows-sockets-error-codes-2.

Software caused connection abort.
An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.

What other logs can we check to debug and resolve this?