Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

rtpengine-recording: Failed to add frame to mixer: received samples for old re-used input channel?

Open
  • Is something wrong?
#1,689 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
networking

Research direction

Start by comparing the reported pcap files with the rtpengine-recording log lines, focusing on when the SSRC changes during a call and when the mixer errors begin. The issue names no source files or tests; done would mean explaining the error and identifying whether a setting or other action can prevent it.

Written by the indexing model from the issue text.

Description

Hi Richard,

We have deployed rtpengine and rtpengine-recording in an environment with lot's of siprec traffic. We have approx. 500 concurrent calls per node. I've seen in the pcap files that the ssrc can change during a call.

I see lot's of log-lines like these:

Jul 11 09:04:33 wfrstdrec01 rtpengine-recording[26839]: ERR: [C 07a4d24d-9a5c-123c-9a87-005056b8556a-a1edcdfdddbbe0a8.meta] [S tag-0-media-1-component-1-RTP-id-2] [0x7228c746] [core] Failed to add frame to mixer: received samples for old re-used input channel
Jul 11 09:04:33 wfrstdrec01 rtpengine-recording[26839]: ERR: [C 07a4d24d-9a5c-123c-9a87-005056b8556a-a1edcdfdddbbe0a8.meta] [S tag-0-media-1-component-1-RTP-id-2] [0x7228c746] [core] Failed to add decoded packet to mixed output

Probably for each RTP packet that is received after a issue has occurred.

Can you explain what is happening? Is there a setting that we could try?

Best regards,
Sjoerd.

Dominant language
Perl
Stars
992
Forks
459
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sipwise/rtpengine

All issues in sipwise/rtpengine

Similar issues

More Perl issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.