21 Oct
2013
21 Oct
'13
12:16 p.m.
The only reason I can think of why it might be a worth trying to salvage iptrtpproxy is
political in nature. Mediaproxy is put out by AG Projects, which, as far as I can tell, is
firmly with The Other Project in terms of its personal sympathies and affinities (perhaps
I'm wrong?). That has always made future compatibility with Kamailio a concern for me.
Yes, I know it's all open source and there isn't necessarily a good reason why we
can't hack in new changes to the control protocol, but I've always thought it
worth keeping in mind. It's also a key reason why I generally recommend rtpproxy
instead to customers.
Peter Dunkley <peter.dunkley(a)crocodilertc.net> wrote:
Hello,
I was looking through the module dependencies for this and noticed that
it
requires the netfilter-rtpproxy which has not had a new release in over
two
years. Further, there is a recent bug report
(http://www.2p.cz/en/node/1419 )
which indicates that netfilter-rtpproxy won't even compile with Linux
kernels 2.6.18 and above.
In-kernel forwarding is a feature of mediaproxy-ng (through the
rtpproxy-ng
module), so it looks like iptrtpproxy doesn't provide any features that
aren't available elsewhere.
Should there be some consideration about declaring this module obsolete
in
Kamailio 4.1.0?
Regards,
Peter
--
Peter Dunkley
Technical Director
Crocodile RCS Ltd
------------------------------------------------------------------------
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Sent from my Nexus 10, with all the figments of autocorrect that might imply.
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
United States
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/