Problem setting up external IP

[Lukasz Gryzbon]

Hello

I have just installed BBB twice (first on AWS, then on my local machine within VirtualBox) and it seems like everything went OK on both occasions. I couldn't access it in the first case, but I can see the demo session when I access BBB locally (using the local IP: 192.168.1.68) in the latter case.

However, when I try to access it through the external IP I can't - I get the Welcome to nginx! page.

I have followed these instructions: http://docs.bigbluebutton.org/install/install.html#audio-not-working

Here is the output from sudo bbb-conf --check:

BigBlueButton Server 0.9.0-RC (741)

                    Kernel version: 3.16.0-34-generic

                      Distribution: Ubuntu 14.04.2 LTS (64-bit)

                            Memory: 4841 MB

/var/www/bigbluebutton/client/conf/config.xml (bbb-client)

  Port test (tunnel): 192.168.1.86

                              Red5: 192.168.1.86

              useWebrtcIfAvailable: true

/opt/freeswitch/conf/sip_profiles/external.xml (FreeSWITCH)

                    websocket port: 5066

                    WebRTC enabled: true

/etc/nginx/sites-available/bigbluebutton (nginx)

                       server name: 192.168.1.86

                              port: 80

                    bbb-client dir: /var/www/bigbluebutton

/var/lib/tomcat7/webapps/bigbluebutton/WEB-INF/classes/bigbluebutton.properties (bbb-web)

                      bbb-web host: 192.168.1.86

/var/lib/tomcat7/webapps/demo/bbb_api_conf.jsp (API demos)

                           api url: 192.168.1.86

/var/www/bigbluebutton/check/conf/config.xml (client check)

                      client check: 192.168.1.86

/usr/share/red5/webapps/bigbluebutton/WEB-INF/red5-web.xml (red5)

                  voice conference: FreeSWITCH

                     capture video: true

                   capture desktop: true

/usr/local/bigbluebutton/core/scripts/bigbluebutton.yml (record and playback)

                     playback host: 192.168.1.86

** Potential problems described below **

# Error: The voice application failed to register with the sip server.

#   Try running: 

#

#      sudo bbb-conf --clean

#

# Warning: The setting of (86.191.29.85) for bbb.sip.app.ip in

#

#    /usr/share/red5/webapps/sip/WEB-INF/bigbluebutton-sip.properties

#

# does not match the local IP address (192.168.1.86).

# (This is OK if you've manually changed the values to an external 

# FreeSWITCH server.)

# Error: FreeSWITCH is listening on IP address 192.168.1.86 for SIP calls, but 

# The IP address (86.191.29.85) set bbb.sip.app.ip.

#

# Warning: The API demos are installed and accessible from:

#

#    http://192.168.1.86/

#

# These API demos allow anyone to access your server without authentication

# to create/manage meetings and recordings. They are for testing purposes only.

# If you are running a production system, remove them by running:

#

#    sudo apt-get purge bbb-demo

# Warning: The client self check is installed and accessible from:

#

#    http://192.168.1.86/check

#

I got to the exact same result twice :) I followed the instructions carefully. What am I doing wrong? Can you help please?

I don't really know how to fix the errors...

Many thanks!

Lukasz

[Chad Pilkey]

You have to run "bbb-conf --setip <another_ip_or_domain_name>" to tell your server to use your external IP.

[Lukasz Gryzbon]

Thanks Chad for you reply.

I have run it:

$ sudo bbb-conf --setip 86.191.29.85

Assigning 86.191.29.85 for testing for firewall in /var/www/bigbluebutton/client/conf/config.xml

Assigning 86.191.29.85 for rtmp:// in /var/www/bigbluebutton/client/conf/config.xml

Assigning 86.191.29.85 for servername in /etc/nginx/sites-available/bigbluebutton

Assigning 86.191.29.85 for http:// in /var/www/bigbluebutton/client/conf/config.xml

Assigning 86.191.29.85 for web application URL in /var/lib/tomcat7/webapps/bigbluebutton/WEB-INF/classes/bigbluebutton.properties

Assigning 86.191.29.85 for api demos in /var/lib/tomcat7/webapps/demo/bbb_api_conf.jsp

Assigning 86.191.29.85 for record and playback in /usr/local/bigbluebutton/core/scripts/bigbluebutton.yml

Assigning 86.191.29.85 for playback of recordings: 

Assigning 86.191.29.85 for client self check to /var/www/bigbluebutton/check/conf/config.xml

Restarting the bigbluebutton server ...

 * Stopping daemon monitor monit                                         [ OK ] 

 * Stopping Red5 Server red5                                             [ OK ] 

 * Stopping Tomcat servlet engine tomcat7                                [ OK ] 

Killing: 847

 * Stopping bbb-record-core

2749 Backgrounding.

Waiting for FreeSWITCH to start: ......

 * Starting Red5 Server red5                                                     

                                                                         [ OK ]

 * Starting Tomcat servlet engine tomcat7                                [ OK ] 

 * Starting daemon monitor monit                                         [ OK ] 

Note: monit will automatically start bbb-record-core and LibreOffice within 60 seconds.

Waiting for BigBlueButton to finish starting up (this may take a minute): ...... done

and then sudo bbb-conf --clean  but it still loads the same nginx page.

The check output:

$ sudo bbb-conf --check

BigBlueButton Server 0.9.0-RC (741)

                    Kernel version: 3.16.0-34-generic

                      Distribution: Ubuntu 14.04.2 LTS (64-bit)

                            Memory: 4841 MB

/var/www/bigbluebutton/client/conf/config.xml (bbb-client)

  Port test (tunnel): 86.191.29.85

                              Red5: 86.191.29.85

              useWebrtcIfAvailable: true

/opt/freeswitch/conf/sip_profiles/external.xml (FreeSWITCH)

                    websocket port: 5066

                    WebRTC enabled: true

/etc/nginx/sites-available/bigbluebutton (nginx)

                       server name: 86.191.29.85

                              port: 80

                    bbb-client dir: /var/www/bigbluebutton

/var/lib/tomcat7/webapps/bigbluebutton/WEB-INF/classes/bigbluebutton.properties (bbb-web)

                      bbb-web host: 86.191.29.85

/var/lib/tomcat7/webapps/demo/bbb_api_conf.jsp (API demos)

                           api url: 86.191.29.85

/var/www/bigbluebutton/check/conf/config.xml (client check)

                      client check: 86.191.29.85

/usr/share/red5/webapps/bigbluebutton/WEB-INF/red5-web.xml (red5)

                  voice conference: FreeSWITCH

                     capture video: true

                   capture desktop: true

/usr/local/bigbluebutton/core/scripts/bigbluebutton.yml (record and playback)

                     playback host: 86.191.29.85

** Potential problems described below **

# IP does not match:

#                           IP from ifconfig: 192.168.1.86

#   /etc/nginx/sites-available/bigbluebutton: 86.191.29.85

# Warning: API URL IPs do not match host:

#

#                                IP from ifconfig: 192.168.1.86

#  /var/lib/tomcat7/webapps/demo/bbb_api_conf.jsp: 86.191.29.85

# Error: The voice application failed to register with the sip server.

#   Try running: 

#

#      sudo bbb-conf --clean

#

# Warning: The setting of (86.191.29.85) for bbb.sip.app.ip in

#

#    /usr/share/red5/webapps/sip/WEB-INF/bigbluebutton-sip.properties

#

# does not match the local IP address (192.168.1.86).

# (This is OK if you've manually changed the values to an external 

# FreeSWITCH server.)

# Error: FreeSWITCH is listening on IP address 192.168.1.86 for SIP calls, but 

# The IP address (86.191.29.85) set bbb.sip.app.ip.

#

# Warning: The API demos are installed and accessible from:

#

#    http://86.191.29.85/

#

# These API demos allow anyone to access your server without authentication

# to create/manage meetings and recordings. They are for testing purposes only.

# If you are running a production system, remove them by running:

#

#    sudo apt-get purge bbb-demo

# Warning: The client self check is installed and accessible from:

#

#    http://86.191.29.85/check

#

Still the same error is there... :(

Lukasz

[Chad Pilkey]

You have to follow the steps in, http://docs.bigbluebutton.org/install/install.html#audio-not-working, exactly. The --check output shows that Freeswitch is still listening on your local IP and the instructions change that to your external IP so one of the steps was likely missed.

[Lukasz Gryzbon]

I'm not 100% sure why it started working but it did. I didn't change anything...very strange.

Anyway, I'm still getting the same error in the check. No idea why... I have checked several times the settings in the "audio-not-working" section, but can't see any discrepancy there.

I have a question. Which of these ports should I open:

UDP 16384

UDP 32768

TCP 5066

TCP 1935

TCP 9123

TCP 5070

TCP 5060

Thanks!

Lukasz

[Chad Pilkey]

I don't think you've said what error you are trying to fix.

You need to open:

• UDP: all of the ports between 16384 and 32768 (inclusive)
• TCP: 80, 11935, 9123, 5066 and maybe 5070 and 5060, but I'm not sure about the last two
  

[Fred Dixon]

Hi Lucasz,

You need only open the following ports

   TCP: 80, 1935, 9123

As Chad indicated, you need to open the range 16384-32767 for UDP on your server.

Regards,.. Fred

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-s...@googlegroups.com.
To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at http://groups.google.com/group/bigbluebutton-setup.
For more options, visit https://groups.google.com/d/optout.

--

BigBlueButton Developer

http://bigbluebutton.org/
http://code.google.com/p/bigbluebutton

BigBlueButton on twitter: @bigbluebutton

[Lukasz Gryzbon]

Thanks guys!

I have updated the ports as per your suggestions.

Everything seems to be working correctly - I'm not getting any warning messages when I log in to the demo session. The microphone is working fine - I can talk to other people.

However, I still see the FreeSWITCH error in the check:

Should I be concerned with it? The check page (http://86.191.29.85/check/) doesn't flag up any problems. Is there any other way for me to check if everything is working correctly?

Thanks for your help!

Lukasz

To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-setup+unsub...@googlegroups.com.

To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at http://groups.google.com/group/bigbluebutton-setup.
For more options, visit https://groups.google.com/d/optout.

[Lukasz Gryzbon]

Just to add to it - I have checked my settings more than once against this: http://docs.bigbluebutton.org/install/install.html#audio-not-working - everything seems correct...

[Lukasz Gryzbon]

Hi

I got it working without errors eventually - there was one small mistake I was making, probably due to late hour :) So the documentation is correct! lol

However, I think the port 5066 needs to be open as well for the microphone to work, right? It is mentioned in the documentation.

Thanks,

Lukasz

[Chad Pilkey]

5066 does need to be open if you follow the "Audio not working" steps.

[HostBBB.com]

Chad, I think this is the issue at the root of some of the webrtc config issues we see.

Even though we proxy /ws thru port 80, sip.nginx references the EXTERNALIP:5066.  So the server in some infrastructures is going out the network interface to be routed back in to connect to freeswitch.  so port 5066 needs to be exposed in this case even if we use /ws.

I have tried to get mod_sofia to listen to internal port for websocket commands from nginx, but no matter how I specify the external IPs in freeswitch,  the SDP always shows the bind url for websockets as the one in which is it listening so this internal IP gets thru to sip.js and we get the infamous 1007.

Just need to dig in a little more to figure this out, ideally we want freewitch not listening 5066 externally.

Regards,

Stephen

[Calvin Walton]

On Fri, 2015-04-24 at 05:30 -0700, HostBBB.com wrote:
> Chad, I think this is the issue at the root of some of the webrtc
> config
> issues we see.
>
> Even though we proxy /ws thru port 80, sip.nginx references the
> EXTERNALIP:5066. So the server in some infrastructures is going out
> the
> network interface to be routed back in to connect to freeswitch. so
> port
> 5066 needs to be exposed in this case even if we use /ws.
>
> I have tried to get mod_sofia to listen to internal port for
> websocket
> commands from nginx, but no matter how I specify the external IPs in
> freeswitch, the SDP always shows the bind url for websockets as the
> one in
> which is it listening so this internal IP gets thru to sip.js and we
> get
> the infamous 1007.
>
> Just need to dig in a little more to figure this out, ideally we
> want
> freewitch not listening 5066 externally.
>
> Regards,
> Stephen

Yeah, this is a restriction with the way freeswitch handles websockets
presently; there's no way to change the address that the websockets
are listening on without changing the entire "external" profile, which
could cause other issues.

That said, there shouldn't really be any problem with exposing port
5066 through the firewall; as far as security goes it's the exact same
as the connection available on port 80.

In fact, the only reason we're proxying through port 80 at all instead
of using port 5066 directly is to (hopefully) work around some
restrictive firewalls.

--
Calvin Walton <calvin...@kepstin.ca>