[jitsi-users] No audio/video from users in a particular network


#1

Hi,
Thanks to your help I have a running instance of Jitsi-Meet with secure
rooms configured properly at https://bhuvan-gurukul.nrsc.gov.in. The
installation is on a fresh Ubuntu 16.04 VM using the quick install setup.
The server is behind a NAT and all configurations have been made
accordingly. I have tested it using multiple networks using both wired as
well as independent mobile connections.

I am facing a problem that I am not able to wrap my head around:

Users from only one particular network are able to connect to any room and
their text chats are visible, but no audio/video appears. At my end it just
shows that the user is 'having connectivity issues'.

Their console log (apart from other normal stuff) shows:
CONFERENCE FAILED: conference.setup_failed Error: ICE fail
    at r.peerconnection.oniceconnectionstatechange
(lib-jitsi-meet.min.js?v=2441:sourcemap:2)
    at RTCPeerConnection.peerconnection.oniceconnectionstatechange
(lib-jitsi-meet.min.js?v=2441:sourcemap:2)

I had them connect to a room at https://meet.jit.si/ and all was perfectly
fine with audio/video working properly. Since we have a number of
conferences going in parallel, it is difficult for me to find out the
relevant portions of the log. If needed, I can clear out the log and try to
log the problem, but that can only be done at a later time.

Right now, I want to understand if there is any fundamental difference
between the way I have hosted my setup vs. that done at meet.jit.si. What
is the minimum expectation from the network firewall at the client end
which allows them to connect to meet.jit.si but not to my setup.

If it matters in anyway, the client network facing problem is the one that
hosts the DNS that I am using and has a pretty strict firewall in terms of
content access otherwise.

Please let me know as to how I can go about getting to the root of the
problem.

Cheers!

Gaurav Kumar

···

--
Scientist/Engineer
Regional Remote Sensing Centre
NRSC/ISRO/DOS
CAZRI Campus
Jodhpur, Rajasthan


#2

Hi,

Are you using nginx/apache or you are serving the web using the jetty that
is inside jvb.
In the second case port 443 is used not only for web content, but also for
media over tcp, which can be a fallback in case of restrictive firewalls.
In case of a webserver, jvb will use by default port 4443(as 443 is already
taken) which will not be an option if such restrictive firewall is in front
of it.

Regards
damencho

···

On Jan 29, 2018 02:40, "Gaurav Kumar" <gaurav1089@gmail.com> wrote:

Hi,
Thanks to your help I have a running instance of Jitsi-Meet with secure
rooms configured properly at https://bhuvan-gurukul.nrsc.gov.in. The
installation is on a fresh Ubuntu 16.04 VM using the quick install setup.
The server is behind a NAT and all configurations have been made
accordingly. I have tested it using multiple networks using both wired as
well as independent mobile connections.

I am facing a problem that I am not able to wrap my head around:

Users from only one particular network are able to connect to any room and
their text chats are visible, but no audio/video appears. At my end it just
shows that the user is 'having connectivity issues'.

Their console log (apart from other normal stuff) shows:
CONFERENCE FAILED: conference.setup_failed Error: ICE fail
    at r.peerconnection.oniceconnectionstatechange
(lib-jitsi-meet.min.js?v=2441:sourcemap:2)
    at RTCPeerConnection.peerconnection.oniceconnectionstatechange
(lib-jitsi-meet.min.js?v=2441:sourcemap:2)

I had them connect to a room at https://meet.jit.si/ and all was perfectly
fine with audio/video working properly. Since we have a number of
conferences going in parallel, it is difficult for me to find out the
relevant portions of the log. If needed, I can clear out the log and try to
log the problem, but that can only be done at a later time.

Right now, I want to understand if there is any fundamental difference
between the way I have hosted my setup vs. that done at meet.jit.si. What
is the minimum expectation from the network firewall at the client end
which allows them to connect to meet.jit.si but not to my setup.

If it matters in anyway, the client network facing problem is the one that
hosts the DNS that I am using and has a pretty strict firewall in terms of
content access otherwise.

Please let me know as to how I can go about getting to the root of the
problem.

Cheers!

Gaurav Kumar

--
Scientist/Engineer
Regional Remote Sensing Centre
NRSC/ISRO/DOS
CAZRI Campus
Jodhpur, Rajasthan

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users