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

[Peter Lemenkov]

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/devel/attachments/20140222/af21046b/attachment.htm>