Bigbluebutton websocket ошибка 1002

I’m writing this to help those who still not figred out how to resolve this issue.
You need to perform one extra steps when server is behind NAT(network address translation).
You need to configre Kurento to use stun server, which you can get from the link kurento documentation,
you need to edit /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini and uncomment and assign values for stunServerAddress and stunServerPort.

For example, to use the STUN server at 64.233.177.127 with port 19302, edit the lines with stunServerAddress and stunServerPort as follows:

stunServerAddress=64.233.177.127
stunServerPort=19302

Next, this is very important

edit /opt/freeswitch/conf/sip_profiles/external.xml and ensure the value for wss-binding uses the external IP address

<param name="wss-binding" value="EXTERNAL_IP_ADDRESS:7443"/>
At this point, restart your BigBlueButton server with bbb-conf --restart, then try connecting to the WebRTC media again.

If the issue stile not resolved then edit the following files and substitute EXTERNAL_IP_ADDRESS for the external IP address (not the external hostname).

Edit /opt/freeswitch/conf/vars.xml, and
change <X-PRE-PROCESS cmd="set" data="external_rtp_ip=stun:stun.freeswitch.org"/>
To <X-PRE-PROCESS cmd="set" data="external_rtp_ip=EXTERNAL_IP_ADDRESS"/>

Change <X-PRE-PROCESS cmd="set" data="external_sip_ip=stun:stun.freeswitch.org"/>
To <X-PRE-PROCESS cmd="set" data="external_sip_ip=EXTERNAL_IP_ADDRESS"/>

Next, edit /opt/freeswitch/conf/sip_profiles/external.xml and change
<param name="ext-rtp-ip" value="$${local_ip_v4}"/>
<param name="ext-sip-ip" value="$${local_ip_v4}"/>
to
<param name="ext-rtp-ip" value="$${external_rtp_ip}"/>
<param name="ext-sip-ip" value="$${external_sip_ip}"/>

Next, edit /usr/share/red5/webapps/sip/WEB-INF/bigbluebutton-sip.properties, and make sure the values of bbb.sip.app.ip and freeswitch.ip have the internal IP address.

bbb.sip.app.ip=<internal_ip>
bbb.sip.app.port=5070

freeswitch.ip=<internal_ip>
freeswitch.port=5060

Edit /etc/bigbluebutton/nginx/sip.nginx to connect to the external IP address.

If you have configured SSL, use port 7443:

location /ws {
        proxy_pass https://EXTERNAL_IP_ADDRESS:7443;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
        proxy_read_timeout 6h;
        proxy_send_timeout 6h;
        client_body_timeout 6h;
        send_timeout 6h;
}

If enableListenOnly is set to true in /usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml, as in

$ grep enableListenOnly /usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml
    enableListenOnly: true

edit /usr/local/bigbluebutton/bbb-webrtc-sfu/config/default.yml change the value to ip to match the external IP address of the server, and the value of sip_ip to match the internal IP address of the server (where FreeSWITCH is listening to port 5066). For example, if the servers external IP address is 203.0.113.1 and the internal IP address is 172.30.1.145 then edit default.yml and change the values for ip and sip_ip as follows:

freeswitch:
    ip: 203.0.113.1
    sip_ip: 172.30.1.145
    port: 5066

After making the above changes, restart BigBlueButton.

$ bbb-conf --restart

BigBlueButton is an opensource video conference software that is becoming increasingly popular during the COVID-19 period. Every day, millions of people take classes online. Users may encounter error codes such as 1001,1006,1007,1020… What does this mean? What should be checked and how should it be fixed?

The advantage of web-based software is that there is no need to download and install anything; simply use a browser, which is very convenient and compatible with all devices. However, the user must configure the browser correctly, and the developer must configure the server correctly as well. Otherwise, error messages will be displayed.

We’ve listed the majority of the most common error messages along with the code to make it easier for you to look up and understand what’s going on when those error messages appear.

1001: WebSocket disconnected — The WebSocket had connected successfully and has now disconnected. 

What need to check: 

• internet connection 

1002: Could not make a WebSocket connection — The initial WebSocket connection was unsuccessful. 

What need to check: 

• The firewall may block was protocol, 
• The server may go down or improperly configured

1003: Browser version not supported — Browser doesn’t implement the necessary WebRTC API methods. 

What needs to check: 

• Is it the latest version of Chrome, Firefox, or Safari? 

1004: Failure on call — The call was attempted, but failed. 

What needs to check: 

• A version of Freeswitch for BBB

1005: Call ended unexpectedly — The call was successful but ended without the user requesting to end the session.

What needs to check: 

• Server down 

1006: Call timed out — The library took too long to try and connect the call.

What needs to check: 

• Is it the latest version of Chrome, Firefox, or Safari? 

1007: ICE negotiation failed — The browser and FreeSWITCH try to negotiate ports to use to stream the media and that negotiation failed. 

What needs to check: 

• TURN Server configuration

1008: Call transfer failed — A timeout while waiting for FreeSWITCH to transfer from the echo test to the real conference. 

What needs to check: 

• FreeSWITCH Configuration 

1009: Could not fetch STUN/TURN server information 

What needs to check: 

• BigBlueButton Version
• Network 

1010: ICE negotiation timeout 

What needs to check: 

• Network 

1020: Media cloud could not reach the server 

 What needs to check:

• Is server overloaded

Those are common BigBlueButton error codes; I’m sure if you’re a BigBlueButton user, you’ve seen them at some point. Also, thanks to the BigBlueButton Developer Community, some of the data is from the official BigBlueButton development document. We listed it here and added some of our own thoughts and experiences to it. I just wanted to make it easier for you to look up that code and hope it helps you detect and fix the problem. If you want to learn more about BigBlueButton troubleshooting, you can visit the official development document at this link.

https://docs.bigbluebutton.org/2.2/troubleshooting.html#Troubleshooting_

If you require additional assistance in resolving those error messages, please contact us via the support channel.

I have a dedicated server that i want to install big blue button (bbb) on it. The server is behind a NAT and its IP in the network is 192.168.10.203 and i have vc.tagsoo.ir subdomain that points to a static IP 46.249.123.202 which is my network. In the microtic i forwarded TCP ports 80, 443, 7443 and UDP 16384-32768 to the internal server. I installed exactly Ubuntu 16.04 and checked the firewall to see if i can access the ports or not. I used bbb-install.sh like below to install bbb:

wget -qO- https://ubuntu.bigbluebutton.org/bbb-install.sh | bash -s -- -v xenial-22 -s vc.tagsoo.ir -e info@tagsoo.ir -w -x -g

It installs successfully and in the network every thing works including webcam and microphone but from outside webcam and microphone doesn’t work. so i followed extra steps when server is behind NAT. I added stun server 173.194.219.127:19302 and now webcam is working from anywhere. I continued all steps and replaced external IP all places that mentioned in the help. Now I can join an audio session but for microphone (in the network or from outside) i got error 1002. I also added a dummy NIC but it didn’t help. freeswitch is running:

● freeswitch.service - freeswitch
   Loaded: loaded (/lib/systemd/system/freeswitch.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2020-09-05 18:17:43 +0430; 4min 50s ago
  Process: 33240 ExecStart=/opt/freeswitch/bin/freeswitch -u freeswitch -g daemon -ncwait $DAEMON_OPTS (code=exited, status=0/SUCCESS)
 Main PID: 33262 (freeswitch)
    Tasks: 37
   Memory: 34.7M
      CPU: 3.092s
   CGroup: /system.slice/freeswitch.service
           └─33262 /opt/freeswitch/bin/freeswitch -u freeswitch -g daemon -ncwait -nonat

Sep 05 18:17:41 tagbbb systemd[1]: Starting freeswitch...
Sep 05 18:17:41 tagbbb freeswitch[33240]: 33262 Backgrounding.
Sep 05 18:17:43 tagbbb systemd[1]: Started freeswitch.

I even changed the wss-binding to point to external point but it didn’t work. Here is the bbb-conf —check result:

BigBlueButton Server 2.2.23 (2106)
                    Kernel version: 4.4.0-187-generic
                      Distribution: Ubuntu 16.04.7 LTS (64-bit)
                            Memory: 32903 MB
                         CPU cores: 20

/usr/share/bbb-web/WEB-INF/classes/bigbluebutton.properties (bbb-web)
       bigbluebutton.web.serverURL: https://vc.tagsoo.ir
                defaultGuestPolicy: ALWAYS_ACCEPT
                 svgImagesRequired: true

/etc/nginx/sites-available/bigbluebutton (nginx)
                       server name: vc.tagsoo.ir
                              port: 80, [::]:80
                              port: 443 ssl
                    bbb-client dir: /var/www/bigbluebutton

/var/www/bigbluebutton/client/conf/config.xml (bbb-client)
                Port test (tunnel): rtmp://vc.tagsoo.ir
                              red5: vc.tagsoo.ir
              useWebrtcIfAvailable: true

/opt/freeswitch/etc/freeswitch/vars.xml (FreeSWITCH)
                       local_ip_v4: 192.168.10.203
                   external_rtp_ip: 46.249.123.202
                   external_sip_ip: 46.249.123.202

/opt/freeswitch/etc/freeswitch/sip_profiles/external.xml (FreeSWITCH)
                        ext-rtp-ip: $${external_rtp_ip}
                        ext-sip-ip: $${external_sip_ip}
                        ws-binding: :5066
                       wss-binding: 192.168.10.203:7443

/usr/local/bigbluebutton/core/scripts/bigbluebutton.yml (record and playback)
                     playback_host: vc.tagsoo.ir
                 playback_protocol: https
                            ffmpeg: 4.2.2-1bbb1~ubuntu16.04

/etc/bigbluebutton/nginx/sip.nginx (sip.nginx)
                        proxy_pass: 46.249.123.202

/usr/local/bigbluebutton/bbb-webrtc-sfu/config/default.yml (Kurento SFU)
                        kurento.ip: 192.168.10.203
                       kurento.url: ws://127.0.0.1:8888/kurento
                    kurento.sip_ip: 192.168.10.203
                    localIpAddress: 192.168.10.203
               recordScreenSharing: true
                     recordWebcams: true
                  codec_video_main: VP8
               codec_video_content: VP8

/usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml (HTML5 client)
                             build: 1006
                        kurentoUrl: wss://vc.tagsoo.ir/bbb-webrtc-sfu
                  enableListenOnly: true


# Potential problems described below
# IP does not match:
#                           IP from ifconfig: 192.168.10.203
#   /etc/nginx/sites-available/bigbluebutton: vc.tagsoo.ir

# Warning: The setting of 46.249.123.202 for proxy_pass in
#
#    /etc/bigbluebutton/nginx/sip.nginx
#
# does not match the local IP address (192.168.10.203).
# (This is OK if you've manually changed the values)

I don’t know what to do else. It’s more than one week i’m trying.