<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>SIP – WebRTC gateway</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><SPAN LANG="en-us"><FONT FACE="Times New Roman">Hello, </FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT FACE="Times New Roman">I’m figuring out the best approach to deploy a bridge between Websocket\Webrtc and SIP\rtp.</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT FACE="Times New Roman">Can Kamailio (+mediaproxy-ng or something else) operate as a full Webrtc\SIP gateway (signaling, audio or video transcoding, ICE and so on)? </FONT></SPAN></P>
<P><SPAN LANG="en-us"><FONT FACE="Times New Roman">Some months ago I found the architecture described here </FONT><FONT COLOR="#009700" FACE="Times New Roman"><A HREF="http://www.kamailio.org/wiki/devel/rtcweb_breaker">http://www.kamailio.org/wiki/devel/rtcweb_breaker</A></FONT><FONT FACE="Times New Roman"> that proposes to introduce a new RTCWeb </FONT></SPAN></P>
<P><SPAN LANG="en-us"><FONT FACE="Times New Roman">Breaker.</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT FACE="Times New Roman">Is it just a proposal or is Kamailio moving following this approach? </FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT FACE="Times New Roman">If Kamailio really requires a RTCWeb Breaker, what are the main issues against using Doubango webrtc2sip with Kamailio? Performance? Interoperability? License? ...</FONT></SPAN></P>
<P><SPAN LANG="en-us"><FONT FACE="Times New Roman">Thanks </FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT FACE="Times New Roman">Daniele</FONT></SPAN><SPAN LANG="it"></SPAN><SPAN LANG="it"></SPAN>
</P>
<p>**********************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
message
by anyone else is unauthorized. If you are not the intended
recipient, any
disclosure, copying, or distribution of the message, or any action
or
omission taken by you in reliance on it, is prohibited and may be
unlawful.
Please immediately contact the sender if you have received this
message in error.
**********************************************************************</p>
</BODY>
</HTML>