numsessions "current sessions own" and "ipv4 only media" almost always differ
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
Research direction
This is an accounting question, not a located defect: the reporter only shows output of rtpengine-ctl list numsessions and asks which counter is right. Start by finding where the "sessions own" and "ipv4 only media" counters are maintained in the daemon's stats code and under what conditions each is incremented or decremented (timeouts, re-invites, kernel-module teardown). A fix means making the two counters agree, or documenting why they legitimately differ; nothing in the payload names a file or a reproduction.
Written by the indexing model from the issue text.
Description
version 12.3.1.2+0~mr12.3.1.2 git-mr12.3.1-6bbc2827, on Debian 12 x86_64
While watching the output of rtpengine-ctl list numsessions I notice that the ipv4-only number is almost always higher than the current sessions number. In my configuration I'm not using ipv6, so that's always 0.
For example, right now on one relay that's been up for a few days:
Current sessions own: 66
Current sessions foreign: 0
Current sessions total: 66
Current transcoded media: 0
Current sessions ipv4 only media: 268
Current sessions ipv6 only media: 0
Current sessions ip mixed media: 0
Is this normal and correct? What accounts for the difference? I've been combing through the stats in Graphite and don't see anything (like timeouts) that would account for this.
The "sessions own" number is closer to what I'd expect based on what I'm sending it from OpenSIPS. And, everything seems to work alright. All the sessions are simple RTP forwarding with the kernel module between two network interfaces. No transcoding, recording, DTMF changes, packet size changes, SRTP <--> RTP, etc. I don't see a constant ratio between the two numbers.
- 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
-
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
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
sipwise/rtpengine#2162 · 1 comment ·
Maintainers usually reply within 2 days
All issues in sipwise/rtpengine
Similar issues
-
Add .gitattributes so share/skel keeps LF on a Windows git checkoutPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
PerlDancer/Dancer2#1854 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
major/MySQLTuner-perl#1007 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
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