21 Oct
2013
21 Oct
'13
12:16 p.m.
Alex Balashov writes:
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.
i have used ag mediaproxy and have done some patches to k mediaproxy
module along the way. i'm not planning to keep on using it and if the
api is changing in the future, someone should do the upgrade of k
mediaproxy module or stick to the current version of ag mediaproxy.
Yes, I know it's all open source and the it
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.
my understanding is that rtpproxy does not support kernel based
forwarding and is thus not a good choice. instead, mediaproxy-ng seems
like the best fit.
-- juha