Ошибка 1004 bigbluebutton на телефоне

Comments

Describe the bug
When the setting public.app.skipCheck in /usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml is set to true, a first-time user will get a «Failure on call (reason=ICE error) (error 1004)» error after allowing their browser to share the microphone.

To Reproduce
Steps to reproduce the behavior:

1. Make sure that the BigBlueButton server HTML5 client settings (/usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml) has public.app.skipCheck set to true (this instructs the HTML5 client to skip the Echo Test)
2. Join a meeting from a browser that has not been allowed to share the microphone with it
3. Choose to join with microphone
4. Allow the browser to use your microphone
5. See error

Expected behavior
Audio conference should be joined without problems

Actual behavior
A «Failure on call (reason=ICE error) (error 1004)» error is presented to the user, the audio joining method window stays active, but pushing neither «Microphone» or «Listen only» works. Closing the «How would you like to join» window and restarting the audio join process works without a problem.

Screenshots

BBB version (optional):
$ sudo bbb-conf —check | grep BigBlueButton
BigBlueButton Server 2.2.31

Desktop (please complete the following information):

• OS: Mac
• Browser Chrome
• Version 88.0.4324.146

Describe the bug
When the setting public.app.skipCheck in /usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml is set to true, a first-time user will get a «Failure on call (reason=ICE error) (error 1004)» error after allowing their browser to share the microphone.

To Reproduce
Steps to reproduce the behavior:

1. Make sure that the BigBlueButton server HTML5 client settings (/usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml) has public.app.skipCheck set to true (this instructs the HTML5 client to skip the Echo Test)
2. Join a meeting from a browser that has not been allowed to share the microphone with it
3. Choose to join with microphone
4. Allow the browser to use your microphone
5. See error

Expected behavior
Audio conference should be joined without problems

Actual behavior
A «Failure on call (reason=ICE error) (error 1004)» error is presented to the user, the audio joining method window stays active, but pushing neither «Microphone» or «Listen only» works. Closing the «How would you like to join» window and restarting the audio join process works without a problem.

Screenshots

BBB version (optional):
$ sudo bbb-conf —check | grep BigBlueButton
BigBlueButton Server 2.2.31

Desktop (please complete the following information):

• OS: Mac
• Browser Chrome
• Version 88.0.4324.146

Была ли эта страница полезной?

0 / 5 — 0 рейтинги

Describe the bug
When the user tries to join the audio in android mobile/tablet with Chrome especially in android 11, everytime user will get a «Failure on call (reason=ICE error) (error 1004)» error after allowing their browser to share the microphone .

To Reproduce
Steps to reproduce the behavior:

1. Make sure that the BigBlueButton server HTML5 client settings
   (/usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml) has
   public.app.skipCheck set to true (this instructs the HTML5 client to skip the EchoTest)

2. Join a meeting from a browser that has not been allowed to share the microphone
   with it

3. Choose to join with microphone

4. Allow the browser to use your microphone

5. See error

Expected behavior
Audio conference should be joined without problems.

Actual behavior
A «Failure on call (reason=ICE error) (error 1004)» error is presented to the user,when
pushing neither «Microphone» or «Listen only»

Screenshots

**Smartphone **

• Device: Android Mobile/tablets…
• OS: Android 11
• Browser chrome
• Version [96.0.4]

Describe the bug
When the user tries to join the audio in android mobile/tablet with Chrome especially in android 11, everytime user will get a «Failure on call (reason=ICE error) (error 1004)» error after allowing their browser to share the microphone .

To Reproduce
Steps to reproduce the behavior:

1. Make sure that the BigBlueButton server HTML5 client settings
   (/usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml) has
   public.app.skipCheck set to true (this instructs the HTML5 client to skip the EchoTest)

2. Join a meeting from a browser that has not been allowed to share the microphone
   with it

3. Choose to join with microphone

4. Allow the browser to use your microphone

5. See error

Expected behavior
Audio conference should be joined without problems.

Actual behavior
A «Failure on call (reason=ICE error) (error 1004)» error is presented to the user,when
pushing neither «Microphone» or «Listen only»

Screenshots

**Smartphone **

• Device: Android Mobile/tablets…
• OS: Android 11
• Browser chrome
• Version [96.0.4]

wget -qO- https://ubuntu.bigbluebutton.org/bbb-install.sh | bash -s -- -w -a -v xenial-22 -s bbb.example.com -e info@example.com

Failure on call (reason=ICE error) (error 1004)

2 ответа

Лучший ответ

current_host = URI(settings[:default_return_url] || "http://www.instructure.com").host
    send_request(:create, {
      :meetingID => conference_key,
      :name => title,
#      :voiceBridge => format("%020d", self.global_id),
      :attendeePW => settings[:user_key],
      :moderatorPW => settings[:admin_key],
      :logoutURL => (settings[:default_return_url] || "http://www.instructure.com"),
      :record => settings[:record] ? "true" : "false",
      :welcome => settings[:record] ? t("This conference may be recorded.") : "",
      "meta_canvas-recording-ready-user" => recording_ready_user,
      "meta_canvas-recording-ready-url" => recording_ready_url(current_host)
    }) or return nil

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.