You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given the nature of webrtc and the support for those clients the ability for AIA to support $NUM clients is dependent on having free dynamic media ports available. We need to make sure when a datachannel connection closes that we free it and the port it has allocated for the multiplexed UDP session.
The text was updated successfully, but these errors were encountered:
From what I can tell it seems we allocate/listen on the entire defined range on init? Definitely could be wrong...
Usually that's not "how things are done" with dynamic, negotiated media ports in the real time communications space. Ideally we'd keep track of the pool, negotiated ports in use, and then allocate them with the creation of the session and free them at termination of session.
I'm also starting to wonder if this could possibly be related to the "cross-talk" issues Eric discovered...
Given the nature of webrtc and the support for those clients the ability for AIA to support $NUM clients is dependent on having free dynamic media ports available. We need to make sure when a datachannel connection closes that we free it and the port it has allocated for the multiplexed UDP session.
The text was updated successfully, but these errors were encountered: