client
client copied to clipboard
Properly handle STUN 437 Allocation Mismatch Error
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.
has this been sorted or is it still an open issue?
Needs more analysis to see if it's still a thing.
I haven't seen any reports on this, is it still an issue?