sipwise / rtpengine

The Sipwise media proxy for Kamailio
GNU General Public License v3.0
763 stars 360 forks source link

RTP silent-timeou is not working #1832

Closed vbatistela closed 1 month ago

vbatistela commented 1 month ago

rtpengine version the issue has been seen with

Version: git-HEAD-1aec5d31

Used distribution and its version

CentOS 8

Linux kernel version used

4.18.0-348.7.1.el8_5.x86_64

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

x86_64

Expected behaviour you didn't see

How does silent timeout work? I did some tests and found that this timer doesn't seem to be working. I'm using two SIPp instances and after answering, they only send audio streams for 5s. So in in the next period until the call is released, I don't see any communication between rtpengine and kamailio. I think that after 80s (silent-timeout) the call should be released, right?

Unexpected behaviour you saw

The call is not released by rtpengine (silent-timeou is not working) . The call is released by the caller.

Steps to reproduce the problem

SIPp uac generates a call with audio stream for 5s and then after 120 s released the call.

Additional program output to the terminal or logs illustrating the issue

No response

Anything else?

syslog_rtpa.log

vbatistela commented 1 month ago

I am using this rtpengine config: OPTIONS="--interface int1/192.168.24.226 -n 127.0.0.1:2223 --mos=LQ -m 10000 -M 65000 -L 7 --log-facility=local1 --delete-delay=0 --timeout=60 --silent-timeout=80 --final-timeout=7200 --offer-timeout=60 --num-threads=12 --tos=184 --no-fallback --measure-rtp --silence-detect=0.13"

vbatistela commented 1 month ago

image

rfuchs commented 1 month ago

No this is not what silent-timeout is for. Use the mailing list if you have questions or are unsure about how things work.