Child pages
  • XmppMucHowTo
Skip to end of metadata
Go to start of metadata

How to join the Omea XMPP MUC Room (xmpp:omea@conference.jabber.labs.intellij.net)?

XMPP MUC Room

XMPP stands for the Extensible Messaging and Presence Protocol, the protocol that enpowers such instant messaging services as Jabber, Google Talk, LJ Talk, and so on.

If you have an account in any of these, and some client software to go online, then you can participate in XMPP communications.

MUC Room is a multi-user chat room, like an IRC Channel incarnation on top of the modern technology.

Joining a Room

To join a MUC Room, you need an XMPP client that supports the MUC profile. There's a selection of XMPP client software listed at Google or Jabber.Org. Unfortunately, the stock Google Talk client software is poor of its feature set and would not support Multi-User Chats, so an alternative is to be used.

Generally, to join a room you should execute the "Join Group" action from the menu or toolbar of the client. The full name of the room is omea@conference.jabber.labs.intellij.net, or, if there are separate Server and Group fields, their values should be conference.jabber.labs.intellij.net and omea, respectively. Enter a Nickname of your choice and leave the Password field blank.

Behind a Firewall

The XMPP port at TCP 5222 might be blocked on a firewall, which prevents ordinary connections to XMPP servers, and, consequently, joining the chat room. To circumvent the limitation, ports or protocols allowed by the firewall could be used, if supported by the XMPP server. The below examples include just one server and one software client, but the same ideas may be applied to the others, in case they support the necessary features.

Case 1. The firewall blocks non-HTTP ports, but allows any traffic thru the TCP 80 port (HTTP) and does not require the use of an HTTP proxy.

Try explicitly specifying the allowed port (eg TCP 80 for the HTTP protocol) in the connection settings of your software client. For example, if you have an XMPP account on the jabber.ru server, you should explicitly specify allports.jabber.ru:80 or ssl.jabber.ru:80 as the host and port to connect to (without changing the server part of your login name, of course).

Case 2. The firewall blocks any non-HTTP traffic, or requires the use of an HTTP proxy.

It's still possible to open the connectin in the so-called "HTTP Polling" mode. In this configuration, the communication is carried over separate short-lived HTTP connections, in a request-response manner. This mode must be supported by both the server and the client.

An example of the working server-client pair is the jabber.ru server and the Tkabber client. An XMPP account is created on-demand on the server, on the first logon attempt for an account that does not exist yet. To set up the HTTP Polling connection in the Tkabber client, specify your ordinary logon information on the Account page of the logon prompt, turn on the Connect via HTTP polling checkbox on the HTTP Poll page (leave the URL to poll field empty, as it will be retrieved from the DNS SRV records), and optionally specify the proxy server information on the Proxy page.

  • No labels