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.
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:
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.