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
When the SDP offer has different ice-ufrag and ice-pwd for each media, Kurento only uses one of the pairs to perform ICE candidate checks. This issue was previously reported in the Kurento bugtracker, but it hasn't been imported into this repository. I’ve seen that this is still happening in the latest version of Kurento.
Context
I am attempting to negotiate the SDP generated by another media server with Kurento; however, the other media server raises concerns regarding the method of ICE candidate validation, particularly with respect to the STUN request. XMS reports that Kurento is making STUN requests with incorrect credentials. Upon reviewing the Wireshark traces, I observe that Kurento consistently uses the same ufrag for both media streams.
How to reproduce?
Create a media pipeline and an WebRtcEndpoint
Process an SDP with different ice-ufrag and ice-pwd per media track
The STUN requests contain always the same userA:userB pair
Expected & current behavior
Kurento should use the corresponding ice-ufrag and ice-pwd for each media stream in each STUN request.
Thanks for your issue description. I think that you are right, that the previous issue got lost when we switched to our current mono-repo.
Anyway, allow us a little time to analyze the issue and see possible fixes.
Prerequisites
These are MANDATORY, otherwise the issue will be automatically closed.
Issue description
When the SDP offer has different ice-ufrag and ice-pwd for each media, Kurento only uses one of the pairs to perform ICE candidate checks. This issue was previously reported in the Kurento bugtracker, but it hasn't been imported into this repository. I’ve seen that this is still happening in the latest version of Kurento.
Context
I am attempting to negotiate the SDP generated by another media server with Kurento; however, the other media server raises concerns regarding the method of ICE candidate validation, particularly with respect to the STUN request. XMS reports that Kurento is making STUN requests with incorrect credentials. Upon reviewing the Wireshark traces, I observe that Kurento consistently uses the same ufrag for both media streams.
How to reproduce?
Expected & current behavior
Kurento should use the corresponding ice-ufrag and ice-pwd for each media stream in each STUN request.
Info about your environment
About Kurento Media Server
About your Application Server
About end-user clients
Run these commands
The text was updated successfully, but these errors were encountered: