Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

During buildup of GstRtpBin demuxer seems to be ending up using wrong ssrc for jitterbuffer #4

Open
ehasting opened this issue Mar 1, 2022 · 0 comments

Comments

@ehasting
Copy link

ehasting commented Mar 1, 2022

Hello,

Thanks for the great effort on the implementation of kms-siprtpendpoint.
We are seeing some weird issues when we connect up the kms-siprtpendpoint to a webrtcendpoint.

as part of the details, we are using the playerendpoint as a waiting endpoint until they are both ready to be connected together.

What seems to be going on is that the wrong ssrc is being connected into the opusDepay which results in the sip endpoint fails to keep any audio channel.

kurento_problem_depay
(full render)
dotgraph_20220301110201

i have the dotfile on request.

Also i have logs, we can see the correct ssrc getting
0:00:12.760255868 9 0x7f7e98044f00 WARN basertpendpoint kmsbasertpendpoint.c:3278:kms_base_rtp_endpoint_rtpbin_on_ssrc_sdes: SSRC 1547351529 not valid

which is due to the ssrc for the endpoint already being set.

Any clue whats going on?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant