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 a client negotiates an SDP offer with the a=ice-lite attribute, Kurento responds with an SDP answer in ice-lite mode. As I understand it, and based on its behavior, Kurento is actually acting as ice-full rather than ice-lite (I've seen it perform ICE candidate validations by sending STUN requests).
v=0
o=- 3953178299 3953178299 IN IP4 0.0.0.0
s=Kurento Media Server
t=0 0
a=ice-lite
a=ice-options:trickle
a=msid-semantic:WMS 74b4e4f295854f7eaacf7c5dadc8aa10
a=group:BUNDLE audio video
m=audio 55758 UDP/TLS/RTP/SAVP 96
c=IN IP4 10.50.2.247
a=sendrecv
a=mid:audio
a=rtcp:55758 IN IP4 10.50.2.247
a=rtpmap:96 opus/48000/2
a=fmtp:96 maxplaybackrate=16000; sprop-maxcapturerate=16000; sprop-stereo=0; stereo=0
a=ptime:20
a=maxptime:120
a=setup:active
a=rtcp-mux
a=ssrc:1055466269 cname:user1865411734@host-7b219810
a=ice-ufrag:NRqr
a=ice-pwd:1g+AsS3DOkGxypCj65Q6MB
a=fingerprint:sha-256 D7:E6:B1:B8:5A:A1:37:5A:DE:64:50:5A:86:A9:61:13:A7:DA:47:AB:C6:6F:46:D2:54:8D:FE:47:B6:81:F2:A6
a=candidate:1 1 UDP 2015363327 y.y.y.y 6049 typ host
a=candidate:2 1 TCP 1015021823 y.y.y.y 9 typ host tcptype active
a=candidate:3 1 TCP 1010827519 y.y.y.y 34632 typ host tcptype passive
a=candidate:1 2 UDP 2015363326 y.y.y.y 9847 typ host
a=candidate:2 2 TCP 1015021822 y.y.y.y 9 typ host tcptype active
a=candidate:3 2 TCP 1010827518 y.y.y.y 19073 typ host tcptype passive
a=candidate:7 1 TCP 847249663 10.50.0.185 9 typ srflx raddr y.y.y.y rport 9 tcptype active
a=candidate:8 1 TCP 843055359 10.50.0.185 34632 typ srflx raddr y.y.y.y rport 34632 tcptype passive
a=candidate:9 1 UDP 337641727 10.50.2.247 55758 typ relay raddr y.y.y.y rport 9
a=candidate:7 1 TCP 847249663 10.50.2.176 9 typ srflx raddr y.y.y.y rport 9 tcptype active
a=candidate:8 1 TCP 843055359 10.50.2.176 34632 typ srflx raddr y.y.y.y rport 34632 tcptype passive
a=candidate:7 2 TCP 847249662 10.50.1.169 9 typ srflx raddr y.y.y.y rport 9 tcptype active
a=candidate:8 2 TCP 843055358 10.50.1.169 19073 typ srflx raddr y.y.y.y rport 19073 tcptype passive
a=candidate:9 2 UDP 337641726 10.50.2.247 61903 typ relay raddr y.y.y.y rport 9
m=video 55758 UDP/TLS/RTP/SAVPF 99 100
c=IN IP4 10.50.2.247
a=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=sendrecv
a=mid:video
a=rtcp:55758 IN IP4 10.50.2.247
a=rtpmap:99 vp8/90000
a=rtpmap:100 h264/90000
a=fmtp:99 max-fr=30; max-fs=3600
a=fmtp:100 profile-level-id=42c01f; packetization-mode=0
a=framerate:30
a=setup:active
a=rtcp-mux
a=ssrc:103812202 cname:user1865411734@host-7b219810
a=ice-ufrag:NRqr
a=ice-pwd:1g+AsS3DOkGxypCj65Q6MB
a=fingerprint:sha-256 D7:E6:B1:B8:5A:A1:37:5A:DE:64:50:5A:86:A9:61:13:A7:DA:47:AB:C6:6F:46:D2:54:8D:FE:47:B6:81:F2:A6
a=candidate:1 1 UDP 2015363327 y.y.y.y 6049 typ host
a=candidate:2 1 TCP 1015021823 y.y.y.y 9 typ host tcptype active
a=candidate:3 1 TCP 1010827519 y.y.y.y 34632 typ host tcptype passive
a=candidate:1 2 UDP 2015363326 y.y.y.y 9847 typ host
a=candidate:2 2 TCP 1015021822 y.y.y.y 9 typ host tcptype active
a=candidate:3 2 TCP 1010827518 y.y.y.y 19073 typ host tcptype passive
a=candidate:7 1 TCP 847249663 10.50.0.185 9 typ srflx raddr y.y.y.y rport 9 tcptype active
a=candidate:8 1 TCP 843055359 10.50.0.185 34632 typ srflx raddr y.y.y.y rport 34632 tcptype passive
a=candidate:9 1 UDP 337641727 10.50.2.247 55758 typ relay raddr y.y.y.y rport 9
a=candidate:7 1 TCP 847249663 10.50.2.176 9 typ srflx raddr y.y.y.y rport 9 tcptype active
a=candidate:8 1 TCP 843055359 10.50.2.176 34632 typ srflx raddr y.y.y.y rport 34632 tcptype passive
a=candidate:7 2 TCP 847249662 10.50.1.169 9 typ srflx raddr y.y.y.y rport 9 tcptype active
a=candidate:8 2 TCP 843055358 10.50.1.169 19073 typ srflx raddr y.y.y.y rport 19073 tcptype passive
a=candidate:9 2 UDP 337641726 10.50.2.247 61903 typ relay raddr y.y.y.y rport 9
Context
I'm attempting to negotiate the SDP generated by another media server with Kurento, but the other media server raises issues regarding the way ICE candidate validation is performed (specifically, the STUN request). From what I've observed, one of the underlying causes is that Kurento advertises itself as ICE-lite in the SDP, but it behaves as an ICE-full agent instead.
How to reproduce?
Create a media pipeline and an WebRtcEndpoint
Process the previous SDP using the created WebRTCEndpoint
The sdpAnswer contains the attribute a=ice-lite
The STUN request containes ufragA:ufragB format (as far as I know this is expected using ice-full)
Expected & current behavior
Current behaviour: Kurento includes ice-lite attribute to the SDP answer.
Thanks for your issue information. It is really complete and help us a lot analysing the issue and providing an answer.
We need to analyze the information, but form your description it seems that you are right. Kurento does not implement ICE-lite, so the ice-lite attribute should not be there.
Allow us to fully analize the issue and I hope we can fix it soon.
Prerequisites
These are MANDATORY, otherwise the issue will be automatically closed.
Issue description
When a client negotiates an SDP offer with the a=ice-lite attribute, Kurento responds with an SDP answer in ice-lite mode. As I understand it, and based on its behavior, Kurento is actually acting as ice-full rather than ice-lite (I've seen it perform ICE candidate validations by sending STUN requests).
SDP offer
Kurento SDP answer
Context
I'm attempting to negotiate the SDP generated by another media server with Kurento, but the other media server raises issues regarding the way ICE candidate validation is performed (specifically, the STUN request). From what I've observed, one of the underlying causes is that Kurento advertises itself as ICE-lite in the SDP, but it behaves as an ICE-full agent instead.
How to reproduce?
Expected & current behavior
Current behaviour: Kurento includes ice-lite attribute to the SDP answer.
Expected: the attribute should be removed
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: