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 "xxxxx-ng" which connects to a
media relayer called "yyyyy-ng" (where "xxxxx" != "yyyyy", and "yyyyy" 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
