kernel-player is not working properly
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c, linux
- Domain
- audio-video-rtc, backend
Research direction
Start by tracing the kernel-player startup path and the log message “Decoder not finished yet, waiting to start kernel player index”; the report gives the relevant setup in rtpengine.conf and a two-call reproduction using play_media from Kamailio. Reproduce with player-cache enabled and the preloaded WAV file, then compare the first and second calls. Done means audio plays on subsequent calls without the repeated wait message.
Written by the indexing model from the issue text.
Description
rtpengine version the issue has been seen with
Version: 13.5.1.25+0~mr13.5.1.25
Used distribution and its version
Debian 12
Linux kernel version used
6.1.0-42-amd64
CPU architecture issue was seen on (see uname -m)
x86_64
Expected behaviour you didn't see
With the following configuration:
[rtpengine]
...
table = 0
player-cache = true
kernel-player = 512
preload-media-files = /var/lib/rtpengine/media/test.wav
...
When I call "play media", the audio is played normally.
Unexpected behaviour you saw
After restarting rtpengine, audio plays normally in the first call. However, for the second call and all subsequent calls, no audio is played at all. The log shows the following:
[core] Decoder not finished yet, waiting to start kernel player index 16
Every call after that prints the same log message.
Steps to reproduce the problem
1、Configure the kernel player related options in rtpengine.conf, for example table=0, player-cache=true, kernel-player=512 and preload-media-files=/var/lib/rtpengine/media/test.wav.
2、Trigger play_media from Kamailio during a call.
3、Hang up, then place a second call and trigger play_media again.
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 3 days
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 3 days
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 3 days
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
sipwise/rtpengine#2231 · 3 comments ·
Maintainers usually reply within 3 days
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
sipwise/rtpengine#2190 · 1 comment ·
Maintainers usually reply within 3 days
All issues in sipwise/rtpengine
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
ai-driven-fuzzing bug claude Minor
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
linagora/lemonldap-ng-plugins#170 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
libwww-perl/HTTP-Message#236 ·
-
1.severity: security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
wave-followup
Difficulty 2/5 1-3 hours Newbie friendliness 74/100