Re: [reSIProcate] WebRTC branch available now
I've added a wiki page about this now, from a user perspective:
https://www.resiprocate.org/WebRTC_and_SIP_Over_WebSockets
(but it is not ready for users yet)
On 15/02/13 16:19, Daniel Pocock wrote:
>
>
> Scott Godin <sgodin@xxxxxxxxxxxxxxx> wrote:
>
>> Thanks Daniel!
>>
>> Note: This is implementation is not everything you need to implement
>> WebRTC, it is more accurately described as web socket transport support
>> for
>> resip and repro. Websockets are an important part of WebRTC, allowing
>> browsers to communicate with SIP servers and proxies.
>
> Agreed, my email was not technically specific. In fact, SIP is not a
> mandatory part of WebRTC, but they play together in a manner described by
> draft-ietf-sipcore-sip-websocket and that is the specific piece of the puzzle
> that repro has the potential to fill here.
>
> Kamailio already has something like this too and a couple of open source
> Javascript user agents already exist, eg sipml5
>
> Another part of reSIProcate does have the honour of being a core element of
> WebRTC: reTurn. ICE appears to be a mandatory part of the WebRTC model.
>
>
>>
>> Scott
>>
>> On Thu, Feb 14, 2013 at 5:35 PM, Daniel Pocock <daniel@xxxxxxxxxxxxx>
>> wrote:
>>
>>>
>>>
>>> I've just started a branch for WebRTC support:
>>>
>>> https://svn.resiprocate.org/rep/resiprocate/branches/b-webrtc
>>>
>>> This is based on a patch against trunk/main r9737 (May 2012)
>> developed
>>> by Doubango Telecom and distributed through their own project. As
>> their
>>> patch was distributed with a Vovida license block, I have adapted the
>>> license to name Doubango (rather than Vovida) as the contributor for
>> new
>>> files.
>>>
>>> I also managed to reduce the size of their patch by 75% just by using
>>> diff arguments to ignore whitespace/EOL style changes. This makes it
>>> easier to analyze the actual changes introduced.
>>>
>>> Other than that, I have made no changes of my own (yet)
>>>
>>> I would be interested in feedback from anybody else keen to develop
>> or
>>> test this initiative. With enough community support, I believe this
>>> could be released in reSIProcate 1.9.x within Q2 2013.
>>>
>>> _______________________________________________
>>> resiprocate-devel mailing list
>>> resiprocate-devel@xxxxxxxxxxxxxxx
>>> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>>>
>
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel