17 Jul
2017
17 Jul
'17
6:56 a.m.
Hello,
We're using Kamailio 4.2.1 with rtpengine 5.1.2.1 on Ubuntu 16.04. When
running rtpengine we get this error:
[1500263405.711288] ERR: FAILED TO CREATE KERNEL TABLE 0 (File exists),
KERNEL FORWARDING DISABLED
[1500263405.712367] CRIT: Fatal error: Failed to open UDP control
connection port
The first line I think is not important, but the second appears to be. It's
being run as root with these options:
/usr/sbin/rtpengine --interface=xx.xx.xx.xx --listen-ng=7724 --timeout=60
--silent-timeout=3600 --pidfile=/var/run/rtpengine.pid --port-min=45000
--port-max=50000 --table=0
Running "netstat -lnp | grep 7724" does not report anything listening on
port 7724 already.
Has anyone any ideas? Thanks in advance.
--
David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
Australia: +61 (0) 2 8063 9019
17 Jul
17 Jul
7:38 a.m.
Hello,
With the wisdom of Alex Balashov we got it running by adding the IP address
to the listen-ng parameter.
The question now is how to cure this iptables problem:
Starting RTP/media proxy: rtpengineiptables v1.4.21: unknown option "--id"
Try `iptables -h' or 'iptables --help' for more information.
ip6tables v1.4.21: can't initialize ip6tables table `filter': Address
family not supported by protocol
Perhaps ip6tables or your kernel needs to be upgraded.
The iptables module is compiled and installed:
# ls /lib64/xtables/
libxt_RTPENGINE.so
This is on Ubuntu. Any ideas?
Thanks in advance.
On 17 July 2017 at 15:56, David Cunningham <dcunningham(a)voisonics.com>
wrote:
Hello,
We're using Kamailio 4.2.1 with rtpengine 5.1.2.1 on Ubuntu 16.04. When
running rtpengine we get this error:
[1500263405.711288] ERR: FAILED TO CREATE KERNEL TABLE 0 (File exists),
KERNEL FORWARDING DISABLED
[1500263405.712367] CRIT: Fatal error: Failed to open UDP control
connection port
The first line I think is not important, but the second appears to be.
It's being run as root with these options:
/usr/sbin/rtpengine --interface=xx.xx.xx.xx --listen-ng=7724 --timeout=60
--silent-timeout=3600 --pidfile=/var/run/rtpengine.pid --port-min=45000
--port-max=50000 --table=0
Running "netstat -lnp | grep 7724" does not report anything listening on
port 7724 already.
Has anyone any ideas? Thanks in advance.
--
David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092 <+1%20213-221-1092>
Australia: +61 (0) 2 8063 9019 <+61%202%208063%209019>
--
David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
Australia: +61 (0) 2 8063 9019
7:43 a.m.
Reading further into this error message, it sounds like you are using an
init script for RTPengine which attempts to install the -j RTPENGINE
rule for both the IPv4 and IPv6 netfilter tables, which are separate,
using iptables and ip6tables respectively. I believe that is what the
stock Sipwise init scripts / systemd units do.
If IPv6 is disabled on your host, that's not going to work. Try
commenting out the ip6tables line (but not the iptables line) in the
rtpengine init script / unit and see if it makes a difference.
-- Alex
On Mon, Jul 17, 2017 at 04:38:24PM +1200, David Cunningham wrote:
Starting RTP/media proxy: rtpengineiptables v1.4.21:
unknown option "--id"
Try `iptables -h' or 'iptables --help' for more information.
ip6tables v1.4.21: can't initialize ip6tables table `filter': Address
family not supported by protocol
Perhaps ip6tables or your kernel needs to be upgraded.
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
2:51 p.m.
On 07/17/2017 12:43 AM, Alex Balashov wrote:
Reading further into this error message, it sounds
like you are using an
init script for RTPengine which attempts to install the -j RTPENGINE
rule for both the IPv4 and IPv6 netfilter tables, which are separate,
using iptables and ip6tables respectively. I believe that is what the
stock Sipwise init scripts / systemd units do.
If IPv6 is disabled on your host, that's not going to work. Try
commenting out the ip6tables line (but not the iptables line) in the
rtpengine init script / unit and see if it makes a difference.
IPv6 not being
available would also be my guess for an explanation, and
would also explain the original error (control UDP socket not being able
to be opened) as by default the control socket would be opened for both
IPv4 and IPv6 also.
Cheers
18 Jul
18 Jul
2:29 a.m.
Hi Alex and Richard,
After commenting out all the ip6tables there's still one warning about
'unknown option "--id"'. Evidently somewhere else it's trying to
use
iptables for IPv6.
Anyway, we'll check if it's actually a problem. Thank you for your
suggestions!
On 17 July 2017 at 23:51, Richard Fuchs <rfuchs(a)sipwise.com> wrote:
On 07/17/2017 12:43 AM, Alex Balashov wrote:
--
David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
Australia: +61 (0) 2 8063 9019
Reading further into this error message, it
sounds like you are using an
init script for RTPengine which attempts to install the -j RTPENGINE
rule for both the IPv4 and IPv6 netfilter tables, which are separate,
using iptables and ip6tables respectively. I believe that is what the
stock Sipwise init scripts / systemd units do.
If IPv6 is disabled on your host, that's not going to work. Try
commenting out the ip6tables line (but not the iptables line) in the
rtpengine init script / unit and see if it makes a difference.
IPv6 not being available would also be my guess for an explanation, and
would also explain the original error (control UDP socket not being able to
be opened) as by default the control socket would be opened for both IPv4
and IPv6 also.
Cheers
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
2688
days inactive
2688
days old
4 comments
3 participants
participants (3)
-
Alex Balashov -
David Cunningham -
Richard Fuchs