I tried quickly with a rtpengine that was not running, and kamailio started fine and then was responding fast for sip requests.
To clarify: you actually have more rtpengine configured (at least two) in a set and one is not available, right?
Is the CPU usage very high? Because it is strange that is responding, but with long delay ...
Cheers, Daniel
On 25.12.18 00:34, Juha Heinanen wrote:
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