Hello, jitsi-meet developers:
Could you help outline whether public stun servers are needed for hosting jitsi-meet demo system?Or we can setup a stun server automatically just by following the quick install procedures as "https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md" ?
In the source code downloaded from jithub, I guess it is following code that will assign stun server to webrtc client?Also by sniffer the packet between chrome browser and jitsi-meet host, I can see there only STUN message between chrome browser and jitsi-meet server.
Anyone could help clarify? Much appreciate!
getStunAndTurnCredentials: function () { // get stun and turn configuration from server via xep-0215 ... function (res) { var iceservers = []; $(res).find('>services>service').each(function (idx, el) { el = $(el); var dict = {}; var type = el.attr('type'); switch (type) { case 'stun': dict.url = 'stun:' + el.attr('host'); if (el.attr('port')) { dict.url += ':' + el.attr('port'); } iceservers.push(dict); break;
Could you help outline whether public stun servers are needed for hosting jitsi-meet demo system?Or we can setup a stun server automatically just by following the quick install procedures as "https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md" ?
In the source code downloaded from jithub, I guess it is following code that will assign stun server to webrtc client?Also by sniffer the packet between chrome browser and jitsi-meet host, I can see there only STUN message between chrome browser and jitsi-meet server.
Anyone could help clarify? Much appreciate!
getStunAndTurnCredentials: function () { // get stun and turn configuration from server via xep-0215 ... function (res) { var iceservers = []; $(res).find('>services>service').each(function (idx, el) { el = $(el); var dict = {}; var type = el.attr('type'); switch (type) { case 'stun': dict.url = 'stun:' + el.attr('host'); if (el.attr('port')) { dict.url += ':' + el.attr('port'); } iceservers.push(dict); break;
In the source code downloaded from jithub, I guess it is following code that
will assign stun server to webrtc client?
Also by sniffer the packet between chrome browser and jitsi-meet host, I can
see there only STUN message between chrome browser and jitsi-meet server.
Anyone could help clarify? Much appreciate!
getStunAndTurnCredentials: function () {
// get stun and turn configuration from server via xep-0215
...
function (res) {
var iceservers = []; \(res\)\.find\('>services>service'\)\.each\(function \(idx, el\) \{
el = (el);
var dict = {};
var type = el.attr('type');
switch (type) {
case 'stun':
dict.url = 'stun:' + el.attr('host');
if (el.attr('port')) {
dict.url += ':' + el.attr('port');
}
iceservers.push(dict);
break;
This was only used for a TURN-TCP server but it is no longer necessary
today because Jitsi Videobridge now has support for TCP.