26 Dec
2018
26 Dec
'18
12:39 p.m.
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:
--
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
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.
1) Started K where rtpengine udp:192.26.134.10:6050 is enabled but is
not running.
2) Gave kamcmd command. It two about two minutes before I got the
prompt.
3) 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