[jdev] Jingle WebRTC implementation

[Emil Ivov]

Hey there,

On 16.05.12 12:42, Sergey Dobrov wrote:
> I have discovered that at the moment it's impossible to implement Jingle
> on top of WebRTC because of this bug:
> https://groups.google.com/forum/#!topic/discuss-webrtc/6K95fm0r2J4
> 
> Still can't understand if jitsi actually can do SRTP communications (and
> not ZRTP).

Just to be clear here: SRTP is a transport protocol and ZRTP is one key
negotiation mechanism among others, that works with SRTP. Another
popular key negotiation mechanism that also uses SRTP is SDES. I suppose
that in this case you were referring to SDES.

We do have SDES in Jitsi but it's currently only implemented for SIP.
Adding it for Jingle should be rather trivial.

Cheers,
Emil

--
http://jitsi.org

> 
> Created a ticket for Gajim to implement SRTP:
> https://trac.gajim.org/ticket/7157
> 
> On 05/15/2012 07:34 PM, Sergey Dobrov wrote:
>> Hello,
>>
>> I am trying to implement Jingle in my habahaba project
>> (http://habahaba.im/) and trying to find another Jingle implementation
>> to test with and see that the situation with them is awful.
>>
>> To establish a connection, WebRTC requires to use SRTP and not RTP.
>> Okay, have we any client that can do that? I don't see any except of
>> jitsi that judging by code has some support of jingle:encryption
>> element. But in actual fact, it seems for me, that jitsi can use only
>> ZRTP for outgoing sessions and can serve SRTP for incoming sessions.
>>
>> Okay, try to use it! Make outgoing call from my web client to jitsi.
>> Send "session-initiate" populated with my contents and transports and
>> expect for "session-accept" but suddenly receive "transport-info". Is
>> this behavior of jitsi correct? I look throw flows in XEPs and don't
>> understand how I can process "session-accept" here.
>>
>> If anybody can suppose a client with SRTP support, I will be grateful.
>> Anyone interested in the project is welcomed for the discussion.
>>
> 
>