This repository was archived by the owner on Jul 12, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 10
KMS per media ice-ufrag/ice-pwd using wrong username/password #481
Labels
bug
Non-critical bug affecting expected behavior
Comments
Hello @space88man 👋 this issue is being automatically closed because it does not follow the issue template. |
Reopening; I think the template check action might be a bit overzealous here... will review that. |
Can definitely see KMS consuming both sets of ICE attributes. This SDP has per-media ICE attributes. It seems that the second set overwrites the first set, no?
Then we go into ICE checks and always the check for index=0 will fail as KMS uses index=1 credentials during the ICE exchange. If I mangle the SDP so that both sets of ICE attributes are the same, then aiortc <--> KMS will work. Is this enough information? If not, I will try to hack a script and my current setup is baroque.. |
This SDP will cause ICE to fail:
|
3 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Uh oh!
There was an error while loading. Please reload this page.
Issue description
aiortc is the WebRTC peer; when it sends SDP with per-media ice-ufrag/ice-pwd (i.e., m=audio, m=video have different ICE attributes) KMS will use the second pair (i.e. from m=video) to do ICE checks for m=audio.
Reference: aiortc/aiortc#370
aiortc states that KMS is in error as it should handle per-media ICE-attributes.
Context
aiortc --- openvidu for signalling
aiortc --- KMS for RTP
How to reproduce?
For example:
Send this type of SDP to KMS (excerpted):
Expected & current behavior
Expected: ICE converges.
Current : The error is KMS -> aiortc ICE REQUEST fails as it uses the second set of ICE attributes when doing ICE checks for m=audio. When I dump the STUN packets, I see the KMS is using m=video ICE attributes for m=audio ICE candidates.
(Optional) Possible solution
Does KMS not handle per-media ICE attributes?
INFO about Kurento Media Server
INFO about your Application Server
INFO about end-user clients
The text was updated successfully, but these errors were encountered: