The NOTRACK target occasionally appears but Media Proxy is working fine since
changing to a lower NAT test: client_nat_test("1") , on the reply route. It
seems unnecessary modifications were being done.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/i
Hi Saghul,
There is some information here:
http://cateee.net/lkddb/web-lkddb/NETFILTER_XT_TARGET_NOTRACK.html
Below is a piece of log when mediaproxy is engaged.
Feb 22 23:20:34 sip /usr/sbin/opensips[2033]: Call control: user
sip:xxx...@example.net currently has: 1 call(s), Limit 2
Feb 22
Hi @jalung. Thanks for comment. Do you have any links/docs regarding NOTRACK vs
CT targets and supported versions?
As for why we need it, we first create those NOTRACK entries in the PREROUTING
(table raw), then, after the conntrack rule has been created they are removed.
---
Reply to this ema
This post is to make a comment rather than to report a bug.
Mediaproxy built on fedora 18 results in media transport issues.
Based on the documentation, Mediaproxy requires netfilter "NOTRACK" target
support, but this has been deprecated in favor of the newer "CT" target
available in iptables.
