Re: [OpenSIPS-Devel] [opensips] [RFC] An initial attempt of porting rtpproxy-ng module from your twin project to OpenSIPS. (#152)
As for me I really dislike the idea of renaming this module. This module is named after the protocol, not after the backend. Exactly the same situation with rtpproxy module - it implements a protocol, not a particular backend support. One can use rtpproxy module not only with RTPproxy from Sippy Soft but also with mediaproxy-ng or erlrtpproxy backends as well. --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/pull/152#issuecomment-35799110___ 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)
Also I really don't like the direction this discussion is going. Folks, let's just calm down for a while and focus on a technical issues. I have a plenty of patches on top of the original module to be reviewed and I'd love to hear any feedback on them :) --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/pull/152#issuecomment-35799150___ 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)
@lemenkov , I agree, the modules should be named after the protocol it implements. BUT, as far as I understood from @rfuchs's posts this new module has nothing to do with the classical known RTPproxy protocol (used by RTPProxy application). The new protocol is binary, json oriented, etc.. Maybe I got it wrong and if so, please correct it. But if the protocol used in this new module has nothing to do (aside origins) with the protocal used by RTPproxy relay, not even being backward compatible, IMHO, it should not carry the name of rtpproxy-xx at all. It will be confusion and damage to the users (see the arguments in @saghul's initial post ). Please let's keep this discussion strictly technical and strictly about OpenSIPS. Thank you all, Bogdan --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/pull/152#issuecomment-35802868___ 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)
Correct, the protocol is different and incompatible, but heavily based on the original rtpproxy protocol in terms of functionality. The protocol offers all the same flags that the original rtpproxy protocol supported, just transported in a different way to allow it to be extended freely. Also, at least in the original rtpproxy-ng module, the function interface is completely identical to the rtpproxy module. --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/pull/152#issuecomment-35803475___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
