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
There's a connection timeout when using rusturn against a standard turn server.
I think this is due to two things.
create_permission does not allow setting a permission when one already exists for a given client. Thus when we want to refresh a permission, the previous one first needs to be expired completely (causing a gap in communications) By dropping the check for existing permissions, create_permission can be called again even if the permission hasn't expired yet, resulting in a refreshed permission on the server side.
timeouts seem to be coded backwards. For instance refresh for allocations times out at 10/9 the lifetime rather than at 9/10 the lifetime. This is probably the main issue.
The text was updated successfully, but these errors were encountered:
Thank you for reporting this issue.
Unfortunately, I am unable to address it at this time, as the priority of rusturn development is very low.
If you could create a pull request to fix the timeout problem, I will review it.
There's a connection timeout when using rusturn against a standard turn server.
I think this is due to two things.
create_permission does not allow setting a permission when one already exists for a given client. Thus when we want to refresh a permission, the previous one first needs to be expired completely (causing a gap in communications) By dropping the check for existing permissions, create_permission can be called again even if the permission hasn't expired yet, resulting in a refreshed permission on the server side.
timeouts seem to be coded backwards. For instance
refresh
for allocations times out at 10/9 the lifetime rather than at 9/10 the lifetime. This is probably the main issue.The text was updated successfully, but these errors were encountered: