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

ipv4 only media current sessions number wrong after restart #1830

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

ipv4 only media current sessions number wrong after restart #1830

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

Comments

@jpyle490
Copy link

rtpengine version the issue has been seen with

12.3.1.2+0~mr12.3.1.2 git-mr12.3.1-6bbc2827

Used distribution and its version

Debian 12

Linux kernel version used

6.1.0-18-amd64

CPU architecture issue was seen on (see uname -m)

x86_64

Expected behaviour you didn't see

Current sessions ipv4 only media: 0

Unexpected behaviour you saw

Current sessions ipv4 only media: 18446744073709551597

Steps to reproduce the problem

systemctl restart ngcp-rtpengine-daemon
rtpengine-ctl list numsessions

Additional program output to the terminal or logs illustrating the issue

No response

Anything else?

Occasionally, after restarting the rtpengine daemon, the 'rtpengine-ctl list numsessions' output gives an impossibly high number for "Current sessions ipv4 only media". Another restart clears it. I've noticed this happening upon a fresh reboot before any sessions have been across the relay.

@jpyle490 jpyle490 added the bug label May 20, 2024
@rfuchs
Copy link
Member

rfuchs commented May 29, 2024

Is this what #1829 fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants