Turn Server is configured with two physical IPs with two NAT.
- Dominant language
- JavaScript
- Stars
- 7.8k
- Forks
- 983
- PR merge metrics
- No merged PRs in 30d
Description
**What version of this package are you using?**
9.11.0
**What operating system, Node.js, and npm version?**
node 12.16.3, npm 6.14.4
**What happened?**
Turn Server is configured with two physical IPs and each IP has a separate NAT address associated with it. Peer Initiator connects to physical IP 1 with the NAT address. Receiver Peer only has access to physical IP 2 on NAT address associated with it. Initiating peer receives all NATs from turn server, but will randomly send the relay IPs in different order in the ICE candidates. The negotiation fails if the wrong relay IP is sent as the first candidate and is successfully if the right one is sent first.
**What did you expect to happen?**
Receiving Peer should try both relay IPs instead of trying only the first one and failing.
**Are you willing to submit a pull request to fix this bug?**
Do not have a solution.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.