Re: [OpenSIPS-Devel] [opensips] presence_dialoginfo: Fix memory leak in dlginfo_agg_nbody. (#174)
(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 http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [opensips] [RFC] An initial attempt of porting rtpproxy-ng module from your twin project to OpenSIPS. (#152)
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 though, because as @rfuchs pointed out, it's really an evolution of the rtpproxy module, and it can be used as rtpproxy drop-in replacement when switching the back-end. Since only the module part (rtpproxy-ng) is going to be maintained by you guys (we don't use opensips, so there are no plans to support the module for opensips), you can name it however you like. However, I find it extremely offensive from this community to have a module pulled into your project, then start accusing the author and demanding an apology for the name, after he's kind enough to chime in and provide an explanation for the naming clashes. The media proxy is available as open source on github since nearly two years, and I would have expected some feedback from AG if there were concerns about the name over this period (it's not that the guys at AG don't know who we are and what we do). --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/pull/152#issuecomment-36845295___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [opensips] [RFC] An initial attempt of porting rtpproxy-ng module from your twin project to OpenSIPS. (#152)
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 not polling github every day just in case something like this happens. The issue emerged now, in the context of OpenSIPS project where we have an obvious overlap of naming and purpose at the same time. As I mentioned, your software is a great addition and we just asked to eliminate any confusion by renaming it. If you can help with the name change is great, if not then so be it, I don’t really care about your choices and I don’t need any apologies from you or anybody else. Adrian On 06 Mar 2014, at 09:07, Andreas Granig notificati...@github.com wrote: 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 though, because as @rfuchs pointed out, it's really an evolution of the rtpproxy module, and it can be used as rtpproxy drop-in replacement when switching the back-end. Since only the module part (rtpproxy-ng) is going to be maintained by you guys (we don't use opensips, so there are no plans to support the module for opensips), you can name it however you like. However, I find it extremely offensive from this community to have a module pulled into your project, then start accusing the author and demanding an apology for the name, after he's kind enough to chime in and provide an explanation for the naming clashes. The media proxy is available as open source on github since nearly two years, and I would have expected some feedback from AG if there were concerns about the name over this period (it's not that the guys at AG don't know who we are and what we do). — Reply to this email directly or view it on GitHub. ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel signature.asc Description: Message signed with OpenPGP using GPGMail ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [opensips] [RFC] An initial attempt of porting rtpproxy-ng module from your twin project to OpenSIPS. (#152)
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) is in no way initiated or driven by the authors (although I really appreciate the efforts of @lemenkov and his contributions to our project, thanks for that!), and Richard made that perfectly clear. On a side note, the history of the name mediaproxy-ng dates back to May 2007 when the rewrite was done, it got open sourced under that same name in 2010, and the repo was made public in 2012. No bad intentions here, and it obviously wasn't a problem until Peter tried to bring it to opensips. If you guys find it useful, please go ahead and use it (there are really cool features coming up over the next months), but you have to handle the naming and everything else around it by yourselves. Renaming the back-end is a good thing to do to make it more distinguishable, so we're going to do that. Everything else is up to you guys. And that's it from our side. --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/pull/152#issuecomment-36877427___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [opensips] [RFC] An initial attempt of porting rtpproxy-ng module from your twin project to OpenSIPS. (#152)
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 given that there is a protocol (and proxy module) called x-ng which connects to a media relayer called y-ng (where x != y, and y is already used by other protocol, module and server, this is: mediaproxy). I strongly suggest choosing a new name for the protocol (eg. SMCP - Sipwise Media Control Protocol, or whatever), rename the SIP proxy module with that name, and then rename the current mediaproxy-ng server with any name (may not include the SMCP keyword), eg. SipWise Media Relayer. --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/pull/152#issuecomment-36883844___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] Error 483: Too many hops
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/ http://www.reforminfotech.com/* *E-mail: maq...@reforminfotech.com maq...@reforminfotech.com* *Gmail/Gtalk: **maqbulk...@gmail.com maqbulk...@gmail.com* *Skype: maqbul.a* *M: +91 99988 97686* ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
