Linux

Launching the client

Once registered, log in and download the client from the Downloads section.

There's actually no installer for Linux: the download is a simple tar.gz archive, so you'll just need to extract the file somewhere, e.g. your home folder:

cd $HOME
cp /path/to/Meetecho_linux.tar.gz .
tar xfvz Meetecho_linux.tar.gz

This will create a "Meetecho" folder in the folder you chose to install the application in. To start the application, just enter this new folder and launch start.sh, by either double-clicking on it or in a shell:

cd Meetecho
./start.sh

This script will first check if Java Media Framework (JMF) is installed: if not, it will automatically try to install it for the application. After that, the application itself will be started.

 

Before proceeding with the tutorial, check the Troubleshooting section at the end of this page for a few prerequisites to make sure the application works fine, in order to avoid potential issues later on.

 

Logging in

Once the client has been launched you will be asked for your credentials.

You have to use credentials and server name provided by the Meetecho Server Administrator.

 

Configuring the settings

You can set your preferences pressing the setting button on the right hand side

 

The list of conferences

After the login phase you will be presented with the list of virtual rooms hosted by the server.

 

A tool tip will show you the tools available in every room

 

Information details:

  • ConferenceId: the unique identifier of a room;
  • Subject: room’s subject;
  • Status:
    • Registered: the room is empty;
    • Active: at least one participant is in the room.
  • Access: if “Private” you will need a PIN to access the room;
  • Media:
    • Audio: VoIP or PSTN access;
    • Video: video mixing facility;
    • JSummit: whiteboard and polling ;
    • Slide Presentation: each user can upload a document to show to the other participants (supported formats: Microsoft Office, Open Office or PDF);
    • Remote Desktop: each user can choose to show his desktop and grant remote control to other participants.

 

Joining a conference

In order to access a room you just need to double click the corresponding ConferenceID.

 

Room main view

 

 

Audio/Video Moderation and Media Control

Once accessed the room a participant can use all the media available but it will not be able to transmit its audio and video flows.

To be un-muted and transmit your video you can use the “Audio Request” and “Video Request” buttons on the right hand panel.

 

Taskbar and Shortcuts

The upper tools bar provide users with two different kind of tools

Using these buttons you can select one of the multiple windows opened in your client (corresponding to different available tools). The same buttons are used to notify important events happened in a window.     

The right side of the bar let you use the following features

  • Invite: to invite users to this room
  • Presentation: to upload a document for presentation
  • Send File: to send a file to the other participants
  • Polling: to create a poll
  • Share: to share your desktop
  • Viewer: to open a remote desktop viewer
  • Exit: to leave the room

 

Troubleshooting

There are a couple of prerequisites to satisfy in order to make sure Meetecho works fine on your Linux-powered machine. In fact, we currently rely on Java Media Framework (JMF) for what concerns multimedia functionality in the Meetecho desktop client, and JMF may need a bit of tuning to work correctly.

All recent Linux distros make use of the Video for Linux 2 (v4l2) API: sadly, JMF (as many other legacy applications) currently does not work when v4l2 alone is employed. Fortunately, Linux distros usually also provide a v4l1 wrapper to allow legacy applications to work as well: our Meetecho application tries to automatically take advantage of such a feature, by preloading the required library (LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so). This is a well-known workaround that is needed for other applications as well.

Of course, this implicitly assumes you have the library installed, and that it is actually found in that path. Make sure this is true for your linux installation:

ls -la /usr/lib/libv4l/v4l1compat.so

If the file can't be found, install the required package using your package manager and try again. For instance, on Fedora 14 the command would be:

yum install libv4l.i686

You can check if everything's fine by testing your webcam using the JMStudio test application which is shipped with JMF:

cd /path/to/Meetecho
cd JMF-2.1.1e/bin
LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so ./jmstudio

From there, choose the File menu, and then the Capture option: select the video device and then press OK. If you can see your webcam video, then it will be properly working in Meetecho as well.

NOTE: The above mentioned test only works if you have a 32-bit JRE installed on your machine: in fact, JMF performance pack is only available as a 32-bit library, and its video support breaks when invoked from a 64-bit JRE. That's why why ship the Linux Meetecho Desktop Client with a JRE: if the test fails because of your 64-bit JRE, Meetecho may still work fine with video anyway.

 

 

Check the following FAQ for other issues you might encounter while using the Meetecho client. 

 Let us know if this FAQ actually helped you or not: your feedback is important to help us improve the service!

 

  1. I can't login!
    Are username/password correct? Please beware that the site registration account and the Meetecho system account are different things, and you need a Meetecho system account to access the collaboration functionality. If you're sure about your credentials, make sure no firewall/proxy/ALG is in place to filter XMPP traffic.
     
  2. Windows/frames move very slowly!
    This may be related to some problems Java sometimes has with 2D on Linux, for which there is a well-known workaround. Try launching the application using these two environment variables:

         _JAVA_OPTIONS='-Dsun.java2d.pmoffscreen=false' J2D_PIXMAPS=shared ./start.sh

    This should increase the performance of 2D drawing.
     
  3. I don't see any video and/or my Participant controls are greyed out!
    This usually means the SIP call to enable the audio/video functionality didn't work for some reason. Make sure no firewall/proxy/ALG is in place to filter SIP/RTP traffic, e.g. by your router and/or provider. Specifically, make sure incoming SIP messages are not blocked: in fact, we currently rely on a server-originated reINVITE to negotiate BFCP moderation (see RFC4583), and we noticed that in some environments the reINVITE is blocked and never reached the applications, thus invalidating the SIP session.

    If you're sure SIP is supposed to work, use a third-party softphone to access the multimedia functionality (i.e., sip:0xxxxxxx@conf.meetecho.com, where xxxxxxx is the room number), and take advantage of the Meetecho client for all the other features.
     
  4. I can see video, but can't hear anything!
    This may be a dumb question, but does audio work for the other Java applications? Well it's worth a shot! Linux and Java aren't always best friends when it comes to audio, and some tweaking may be necessary. First of all, launch the JMSTudio application as explained at the beginning of the Troubleshooting section, and try to open a generic WAV file (File -> Open file). If you can't hear anything, try forcing Java to use the alsa-oss wrapper (install it if needed): this can be done by prefixing the Java application to launch with the aoss application, e.g.:

            aoss ./jmstudio

    Try opening the WAV file again. If it works, then edit the start_meetecho.sh script in "Meetecho/spark" and aoss after the preload directive. This is verified to work on Fedora 14 x86_64.
     
  5. Other people can't hear/see me!
    Did you make an audio request using the Participant floor client panel? Moderation is involved for both audio and video, meaning you have to ask the system/chair for permission to participate to the mix. If you made the request and it got accepted, check your OS mixer in order to make sure the microphone is right enabled and being recorded. Java usually takes the first microphone it finds, so check no other recording device is actually being used (e.g. Pulseaudio allows to check that). For what concerns video, check the beginning of the Troubleshooting section to make sure your webcam is correctly detected.
     
  6. Other questions to follow...
    ... and we will answer them!