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
Hi,
I am facing an issue which looks like a race condition or me using Kurento incorrectly.
I am establishing a P2P connection with an WebRTC camera which sends an SDP answer with a=sendrecv for audio group and a SSRC of value 3423822970 for audio. What is happening is that Kurento starts sending audio RTP packets to camera which acknowledges with RTCP RR. These reports include a sender SSRC 3271586621 and Kurento uses this sender's SSRC to create an RTP pad named recv_rtcp_sink_0. When camera also sends audio, Kurento also tries to create the same RTP pad name recv_rtcp_sink_0 which causes pipeline to fail with error already linked.
Did anyone faced similar issue? Is the expected behavior of Kurento to create RTP sinks on RR sender SSRCs? I wonder if there shouldn't be a check in Kurento to only create the recv_rtcp_sink_0 for the SSRC reported in the SDP...
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I am facing an issue which looks like a race condition or me using Kurento incorrectly.
I am establishing a P2P connection with an WebRTC camera which sends an SDP answer with a=sendrecv for audio group and a SSRC of value 3423822970 for audio. What is happening is that Kurento starts sending audio RTP packets to camera which acknowledges with RTCP RR. These reports include a sender SSRC 3271586621 and Kurento uses this sender's SSRC to create an RTP pad named recv_rtcp_sink_0. When camera also sends audio, Kurento also tries to create the same RTP pad name recv_rtcp_sink_0 which causes pipeline to fail with error
already linked
.Did anyone faced similar issue? Is the expected behavior of Kurento to create RTP sinks on RR sender SSRCs? I wonder if there shouldn't be a check in Kurento to only create the recv_rtcp_sink_0 for the SSRC reported in the SDP...
Thanks,
Beta Was this translation helpful? Give feedback.
All reactions