You only need to implement COLIBRI if you absolutely want to be doing
your own signaling. Otherwise, if your use case is close to Jitsi
Meet, you can also just use that or at least start from there. This
would provide you with WebRTC clients that run in the browser and an
entity that controls the bridge and then initiates calls with
endpoints. Jitsi Meet's server side signaling entity is called Jitsi
Conference Focus you can get it at https://github.com/jitsi/jicofo .
You can get the client here https://jitsi.org/meet
Depending on what your needs are, you can use either of the above or
Both client and server have been tried to work with Openfire, Prosody,
ejabberd and Tigase.
Obviously, you can also write your own signaling and client entities
or use other implementations like the one Peter mentioned (I believe
there's only a server available for that one and you'd still need to
develop your own client)
On Wed, Dec 10, 2014 at 4:34 PM, Andy Bell <email@example.com> wrote:
I am new to the list and Jitsi so please be gentle.
I have an app for iOS which uses WebRTC to make video calls. I will be
using an OpenFire XMMP server for the signaling, at the moment I am using
PubNub, and I was wondering what I need to do to get Jitsi integrated with
my setup. Am I right to assume I need to implement extension XEP-0340? Is
this right and would I need to implement anything else
dev mailing list
Unsubscribe instructions and other list options: