25 Dec
2018
25 Dec
'18
1:35 a.m.
* Paolo Visintin - evosip.cloud writes:
we solved starting with no rtpengine this produces at startup: WARNING: rtpengine [rtpengine_db.c:100]: rtpp_load_db(): No rtpproxy instances in database and then, after rtpengine instances are up and correctly running we send an `rtpengine.reload` to kamailio
That would work for me too. Also starting with all rtpproxies disabled and then enabling them after start.
Note that after the startup, if an rtpengine instance fails no hangs in kamailio just put in disabled state and everything works!
Exactly, but all these are hacks. This is a VERY serious issue and needs to be properly fixed.
-- Juha