4 ms·
IIRC, ejabberd is agnostic about the XMPP messages going through, you should be able to use strophe.js to craft the proper Jingle packets from the browser's off
by jallmann 14y ago
IIRC, ejabberd is agnostic about the XMPP messages going through, you should be able to use strophe.js to craft the proper Jingle packets from the browser's offer/answer session description.
Given codec and SRTP compatibility with clients, eg GTalk (which I don't know about), you should be good to go.
- shmerl 14y agoBut ejabberd still had to enable support for BOSH or WebSockets first. Without it Strophe was of no use. So I assumed that similar thing has to happen with in this case in order to be able to route the Jingle stream from the browser over WebRTC. If the server modifications won't be needed at all - then of course it'll simplify things. Also, clients don't always use SRTP - there can be other methods like ZRTP for example.
- jallmann 14y agoejabberd already supports BOSH. The rest is up to the client since it's P2P.