[SR-Users] kamailio does not responde if an rtpengine is unreachable

Daniel-Constantin Mierla miconda at gmail.com
Fri Dec 28 10:00:42 CET 2018

Indeed I stopped at the wrong param for the timeout, should have been
another one:

modparam("rtpengine", "rtpengine_tout_ms", 500)


On 26.12.18 12:16, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>> Maybe you would also want to tune the timeout with the modparam:
>> modparam("rtpengine", "rtpengine_disable_tout", 5)
>> So detection of unavailable rtpproxy is fast, otherwise it is 60 sec by
>> default, so you may still experience some slow start per child
>> process.
> I understand from the param description that it tells how to behave
> AFTER rtp proxy has been marked disabled:
>   Once an RTP proxy was found unreachable and marked as disabled, the
>   rtpengine module will not attempt to establish communication to that
>   RTP proxy for rtpengine_disable_tout seconds.
> The problem that I have experienced is that it takes long time (2
> minutes or so) before rtpengine modules disables a non-responding
> rtp proxy.
> Also, no matter what the module does, it must not make the whole sip
> proxy non-responsive for any number of seconds.
> -- Juha

Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com
Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

More information about the sr-users mailing list