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

[Nick Altmann]

Bogdan, about 10 days ago the mediaproxy-ng project was renamed into
rtpengine. What about to add new module with this name? As for me, I'd like
to use rtpengine for a long time, but I've never had a module. And I'm
unhappy that we will have this module only in trunk, but not in 1.11.

--
Nick


2014-02-21 19:33 GMT+04:00 Bogdan Andrei IANCU <notifications at github.com>:

> @lemenkov <https://github.com/lemenkov> thanks for the update...I'm a but
> confused and puzzled. .....The media engine from sipwise is called
> mediaproxy-ng, but has noting to do to with mediaproxy from AG-projects
> (not even a fork) - how comes this ???
> Further more, why to name the module in OpenSIPS rtpproxy-ng, while it has
> nothing to do with the RTPproxy media relay ??
>
> It is a lot of confusion and IMHO we should try to clear it up before
> considering any code.
>
> Regards,
> Bogdan
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/OpenSIPS/opensips/pull/152#issuecomment-35740773>
> .
>
> _______________________________________________
> Devel mailing list
> Devel at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/devel/attachments/20140407/0428d2e3/attachment.htm>