while UV4L itself is closed source (but free).
Let me know if you need more informations.
Would you mind sharing the library you are currently using?
We haven't really used non-bosh xmpp, so it was only an accodent that it
was open before.
We'd have to think about whether or not this could be a concern. Let us
give it a thought.
On Friday, September 4, 2015, email@example.com >>> <mailto:firstname.lastname@example.org> <email@example.com >>> <mailto:firstname.lastname@example.org>> wrote:
unfortunately, it would require some extra effort to implement the
new BOSH protocol used for signaling (XEP-0206 I suppose). At this
point, I am not sure if or when this will happen.
Could you please tell me if you guys are not going to open the XMPP
ports at meet.jit.si <http://meet.jit.si>? In which case, I am
afraid I'll have to remove meet.jit.si <http://meet.jit.si> as
default service from the web user interface for the time being.
I'll send a separate post for the issue I am observing with
Thanks for you help.
Boris Grozev wrote:
On 04/09/15 08:14, info wrote:
thanks for answering.
I did try the new configuration
( taken from http://meet.jit.si/config.js ), but it does not
me. I get DNS errors and a quick nmap meet.jit.si
<http://meet.jit.si> shows filtered ports
only. To work around this, until few days ago I had to use
lambada.jitsi.net <http://lambada.jitsi.net> as XMPP server
and "meet.jit.si <http://meet.jit.si>" as MUC service. As a
side note, I have no problems with the other "meet.jitsi.org
(although the deployed version of Jitsi Meet seems to be old
there, if I
am not wrong), or with "beta.meet.jit.si
OK, it seems that port 5222 is now filtered, since we don't use
you easily setup your client to use BOSH on
I am using the UV4L client. Some days ago I sent an email
It's a native client for the Raspberry Pi to broadcast
all the participants of a room (which does not require any
implementing all the XEP's required to communicate with the
That's really awesome!
I'll be glad to report any problems (there is one about the
beta.meet.jit.si <http://beta.meet.jit.si> especially). For
now I'd really like to understand
what's happening with meet.jit.si <http://meet.jit.si>.
Beta.meet.jit.si <http://Beta.meet.jit.si> is always running the
latest code, so if there are
problems there, they will probably eventually propagate to
users mailing list
Unsubscribe instructions and other list options:
sent from my mobile