Properly handle STUN 437 Allocation Mismatch Error
Open
analysis
bug
- Dominant language
- Python
- Stars
- 78
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
This is an indication that the server believes we have a different allocation already. Since we don't know of the transaction ID for this allocation, we cannot cancel it. Solution is to use a new random port and attempt again.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.