A demonstration client for Muji is available as a tarball or from git. Note that the Client is meant as a technical demonstrator of the underlying components and protocol, as such the user experience might be lacking. Futhermore as Telepathy is a modular framework, the client is not a full IM client. It relies upon another Telepathy Client for handling accounts, connecting to the IM network and to handle IM conversations (such as in the muc room the call is being held in).
Requirements
A modern Telepathy client such as Empathy
telepathy-gabble >= 0.9.12
farsight 2 >= 0.0.20
Recent version of gstreamer, gstreamer-plugins-base, gstreamer-plugins-good and gstreamer-plugins-bad
twisted, twisted words
- pygtk and pygobject
- A good headset :). Unfortunately echo cancellation on the linux desktop is still lacking, so a headset is a must..
All the software requirements are available in Ubuntu Lucid with the telepathy PPA and Debian Unstable
These commands should install all dependencies under Ubuntu Lucid: sudo add-apt-repository ppa:telepathy/ppa; sudo aptitude install empathy telepathy-gabble libtelepathy-farsight0 python-farsight libgstfarsight0.10-0 gstreamer-plugins-base, gstreamer-plugins-good and gstreamer-plugins-bad python-telepathy python-twisted python-gtk2 python-gobject; sudo aptitude dist-upgrade
Usage
The first step is to make sure you have an XMPP account setup and connected in your Telepathy client (e.g. Empathy). This can be any XMPP/Jabber account that supports MUCs and ideally federates with the wider world (google talk, jabber.org, many many others, but not facebook).
Once this is done we can start the demo client. The environment variable VIDEO_DEVICE is used to determine which webcam to be used (when it's not defined a test pattern will be used for the video input). On most machines with a webcam running the client as: VIDEO_DEVICE=/dev/video0 python callui.py should do the right thing. Without video, the command is ./callui.py . Now the following screen will be shown:
- The first entry is the type of call, either 1-to-1 (a normal voip call) or Conference (for a muji call)
- The second entry is the account to use, if there are no entries in this box either your telepathy-gabble is too old or there are currently no XMPP accounts connected
- The third entry (textbox) is the address to call. Should be a contact for 1-to-1 calls or an XMPP MUC for Muji calls
For example to call to muji@conference.jabber.org fill in the ui as such:
Click Audio call or Video call.
Wait for State to say Pending Initiator.
Click Accept.
The State should go to Accepted pretty quickly at which point you're in the Call. Now you just need to get some other people involved and you can have a conference 
FAQ
Please first check the main Muji FAQ
When I try Muji in a room on conference.jabber.org the state stays in ''Pending Receiver''
An XMPP Muc is allowed to filter out namespaces it doesn't know about. Most Muc implementations don't do this, but unfortunately the one on jabber.org does and filters out the muji namespace. Future versions will provide a proper error when this happens. Only solution is to retry with a jabber server that's a bit more lenient (such as the luon.net conference server)
I'm a UI/Interaction designer and this UI makes me cry
It's not meant for you/end-users... Basically no effort was put into the UI, its only goal is to provide something to easily test our backends with as such various implementation details shine through in the UI. Luckily Telepathy is a modular framework, so in the future we can build a nicer end-user UI on top of this backend. (Also if you happen to give presentations about bad UIs, feel free to use it as an example, but please add the disclaimer that it wasn't targetted at users )