Using TLS forwarding, a new stream is created when the SSRC changes
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- linux, ubuntu
- Domain
- audio-video-rtc
Research direction
Reproduce first on Ubuntu 22.04 with rtpengine 13.5.1.1: start TLS forwarding for a specific stream, then change the SSRC mid-stream and watch whether a second TLS connection appears alongside the original. From there, trace how forwarded streams are keyed and where an SSRC change is turned into a new stream, since that is the decision this report disputes. Done means a single TLS connection per forwarded stream survives an SSRC change while PCM keeps flowing. No comments, assignee or pull request exist, and the issue is months old, so expect to work this out alone.
Written by the indexing model from the issue text.
Description
rtpengine version the issue has been seen with
13.5.1.1+0~mr13.5.1.1
Used distribution and its version
Ubuntu 22.04.5 LTS
Linux kernel version used
6.8.0-1044-aws
CPU architecture issue was seen on (see uname -m)
None
Expected behaviour you didn't see
When using the start forwarding command for specific streams, a TLS connection is created and PCM is streamed to the TLS connections - regardless of a change to the SSRC in the recorded RTP
Unexpected behaviour you saw
When using the start forwarding command for specific streams a TLS connection is created and PCM is streamed to the TLS connections as expected.
When the SSRC changes on one of the streams, the initial connection for the stream stays connected and a new connection is created for the stream audio
Steps to reproduce the problem
have the RTP stream change SSRC mid forwarding for a stream
Additional program output to the terminal or logs illustrating the issue
Anything else?
No response
- Dominant language
- Perl
- Stars
- 992
- Forks
- 459
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sipwise/rtpengine
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 2 days
-
HTTP/WS worker threads spin forever in `__websocket_write_done()` (`sched_yield` loop) — 100% CPU with `--listen-http`Possibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 4/5 3-5 days Newbie friendliness 15/100
sipwise/rtpengine#2197 · 1 comment ·
Maintainers usually reply within 2 days
-
Kernel NULL pointer dereference in target_put() during target deletionPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
sipwise/rtpengine#2190 · 1 comment ·
Maintainers usually reply within 2 days
-
Calls using a third logical interface are silently never written to Redis (breaks keyspace-notification HA)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sipwise/rtpengine#2181 · 4 comments ·
Maintainers usually reply within 2 days
All issues in sipwise/rtpengine
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
bioconda/bioconda-recipes#70187 ·
Maintainers usually reply within 2 days
-
documentation Needs Triage
Difficulty 1/5 Under an hour Newbie friendliness 93/100
Maintainers usually reply within 1 day
-
Proposed Text EditsOpen
Difficulty 1/5 Under an hour Newbie friendliness 82/100
curl/everything-curl#658 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
PDLPorters/pdl#561 ·