bigbluebutton / docker

Docker files for BigBlueButton
GNU Lesser General Public License v3.0
360 stars 242 forks source link

bbb-docker on AWS: ICE ERROR - 1004 #142

Open 1modica opened 2 years ago

1modica commented 2 years ago

Describe the bug: When starting a new video call from greenlight, when clicking the "mic" option in the pop up the audio test fails and i get the 1004 error.
image Setup: I have been following the instructions on github using as development server a c5.xlarge with ubuntu-focal-20.04 on AWS as suggested in https://docs.bigbluebutton.org/2.2/install.html#minimum-server-requirements.

My .env file has been generated using the ./scripts/setup from the github docs mentioned above: bbb-docker-env.txt Here instead you have my freeswitch container log where the error arises: freeswitch-container-log.txt

2021-07-29 07:13:06.425040 [ERR] switch_core_media.c:9685 AUDIO RTP REPORTS ERROR: [Bind Error! my.external.ipv4.address:18158] I did check the connectivity on that port via nc and it seems alright.

Expected behavior: The call should start

Actual behavior: User gets 1004 Error, the call fails

Additional context: My first idea was a problem with AWS inbounds rules of the security group, this is my actual setup: image

longshuai commented 2 years ago

[Bind Error! my.external.ipv4.address:18158] This is because, your server is behind the NAT, your external IP address is not your network card ip address, freeswitch can not bind to a address that not exist.

the first method is: follow th docs/behind-nat.md add your External IP address to your Loopback or network card ip addr add External-IP-addrss/32 dev lo

The second Method is: you can change the file bbb-docker/mod/freeswitch/conf/sip_profiles/external.xml change param name="rtp-ip" value="$${external_ip_v4}" to param name="rtp-ip" value="$${local_ip_v4}" But I do not understand why bigbluebuttong set the rtp-ip to external_ip_v4.

privatejava commented 2 years ago

@longshuai After using your solution now it is not even showing any error at logs but in the UI it is showing same 1004 error