(I squashes the two commits into one, just now.)
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/pull/174#issuecomment-36837723___
Devel mailing list
Devel@lists.opensips.org
Speaking with my @sipwise hat on, there will be a name change of at least the
mediaproxy-ng back-end part soon, to clear things up for the future. I
understand the concerns of AG in regards to name clashing, and we don't like
the confusion either. No plans yet for the rtpproxy-ng module name
Hi Andreas,
Not sure if you are referring to me but in case you do. I am not demanding any
apology. Personally, I have no issue with the name you have chosen. If you
knowingly chose that name mediaproxy-ng which I was using since 2008 and
expected me to complain about it, is really weird. I am
Adrian, you were are asking @rfuchs to admit his mistake in naming the project
and you proposed a draft in his name on how he should have approached the
opensips project properly.
This is ridiculous, as the ongoing efforts to bring all this to opensips (where
it seems to cause the confusion)
Even if this new protocol (rtpproxy-ng) is based on the original rtpproxy
protocol, naming it as rtpproxy-ng seems a bad idea IMHO as it will generate
unavoidable confusion. The fact that the Sippy RTP relayer is named RtpProxy
(same name as the protocol) does not help, and things become worse
Hi,
I have recently installed Opensip on Amazon EC2. I could see opensip is
running, but when I try register a user to the server, i get error 483: Too
many hops.
Please help me on this on urgent basis.
Best Regards,
Maqbul A Khan,
*Reform Infotech*, India
*URL: http://www.reforminfotech.com/
