[OpenSIPS-Devel] [opensips] [RFC] An initial attempt of porting rtpproxy-ng module from your twin project to OpenSIPS. (#152)

[Bogdan Andrei IANCU]

Hi all,
I agree with @saghul - I also prefer to avoid confusions as much as possible. Also I understand what @rfuchs explains (as history).
What I'm concerned of :  
- in regards to the media engine - I disagree with the name of the sipwise media engine (as conflicts with something existing); but this out of my scope, something between AG and SIPWISE.
- in regards to the OpenSIPS module - it cannot be "rtpproxy-ng" as it has nothing to do with rtpproxy engine. So, to be accepted, it must have a name which does not conflict with any other module or existing media engines.

Otherwise, such new functionality is more than welcome.

Regards,
Bogdan

---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/pull/152#issuecomment-35763209
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/devel/attachments/20140221/5164cf2c/attachment.htm>