Hello Juha, I think we have experienced the same behaviour (also `service kamailio restart` does strange things like freezed processes and failure of reloading procedure) 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
Note that after the startup, if an rtpengine instance fails no hangs in kamailio just put in disabled state and everything works!
Cheers
*Paolo Visintin* *CTO* evosip.cloud [image: Risultati immagini per evosip]
Il giorno mar 25 dic 2018 alle ore 00:45 Juha Heinanen jh@tutpro.com ha scritto:
Daniel-Constantin Mierla writes:
Can you see the packet being sent over the network (with ngrep, tcpdump, ...)?
Yes, UDP register is sent, but kamailio does not respond to it.
Then I did this.
- Started K where rtpengine udp:192.26.134.10:6050 is enabled but is
not running.
- Gave kamcmd command. It two about two minutes before I got the
prompt.
- Gave 'rtpengine.show all' command. It took perhaps 30 seconds to
produce:
{ url: udp:127.0.0.1:6050 set: 0 index: 0 weight: 10 disabled: 0 recheck_ticks: 0 } { url: udp:192.26.134.10:6050 set: 0 index: 2 weight: 1 disabled: 1 recheck_ticks: 60 } { url: udp:192.26.134.10:6050 set: 1 index: 1 weight: 1 disabled: 1(permanent) recheck_ticks: N/A }
Now udp:192.26.134.10:6050 shows as disabled and kamailio started to accept sip requests.
How is it possible that one non-responding rtpengine can paralyze the whole sip proxy?
-- Juha
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users