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

numsessions "current sessions own" and "ipv4 only media" almost always differ #1831

Open
jpyle490 opened this issue May 20, 2024 · 1 comment

Comments

@jpyle490
Copy link

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.

@rfuchs
Copy link
Member

rfuchs commented May 29, 2024

Try with an LTS version

Edit: Actually try with current master

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

2 participants