[BUG] Remote host candidates may cause TURN allocation to fail

[hiszpanski]

Remote private subnets are not omitted from CreatePermission requests. If a remote private subnet is included in pTurnConnection->turnPeerList, coturn may respond with STUN error 403, which is not a STUN_ERROR_CODE that is explicitly handled by the SDK, producing the following log message and marking all TURN peers with this transactionId as failed:

turnConnectionHandleStunError(): Received STUN error response. Error type: 0x00, Error Code: 403. attribute len 16, Error detail: Forbidden IP.

Note that this will only show up if a remote private subnet candidate is included. Since remotes are often web browsers (and most all web browsers use mDNS host candidates, and the SDK does not currently resolve mDNS candidates), this does not typically show up.

SDK version number 1.7.1

[github-actions[bot]]

It looks like this issue has not been active for a long time. If the issue is not resolved, please add an update to the ticket, else it will be automatically resolved in a few days.

[github-actions[bot]]

This is a very old issue. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to open a new one.