+1 what is erlrtproxy? (Other then assuming its an Erlang port of rtpproxy) On Jan 2, 2013 1:14 PM, "Klaus Darilion" <[email protected]> wrote:
> Am 19.12.2012 12:28, schrieb Peter Lemenkov: > >> 2012/12/19 Juha Heinanen <[email protected]>: >> >>> ice seems to be at least in theory supported by several sip clients: >>> baresip, csipsimple, pjsip based clients, etc. >>> >>> one of the problems of ice is that is uses turn protocol to find ip >>> addresses/ports of relays in case end-to-end connectivity cannot be >>> established otherwise. turn server, on the other hand, must >>> authenticates its clients. this doubles authentication work and, worse, >>> a single turn server does not seem to be able to handle more than one >>> domain. having each domain its own turn server is clearly not a >>> scalable solution. so life would be easier without turn servers. >>> >>> mediaproxy module has solved this problem so that it adds the ice relay >>> candidates to sdp on behalf of ice clients and therefore no separate >>> turn servers nor turn client authentication are needed. >>> >>> have people who have worked on rtpproxy or mediaproxy-ng considered >>> supporting ice in the way mediaproxy modules does today? any other >>> thoughts about this? >>> >> I plan to add STUN/TURN directly into erlrtpproxy. And yes, this >> definitely needs a completely new protocol, JSON-based. >> > Hi Peter! > > I just heard of erlrtpproxy for the first time. There is pretty no > documentation in github. Is it comatible with rtpproxy. Are there any > advantages over rtpproxy? > > I would be cool of you can shortly present erlrtpproxy to the Kamailio > users. > > Thanks > Klaus > > ______________________________**_________________ > sr-dev mailing list > [email protected] > http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**dev<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev> >
_______________________________________________ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
