Jabber Service at ISI Postel Center

0.  Information

    Jabber is an instant messaging (IM) service based on a set of streaming
    XML protocols (RFC3920 & RFC3921). Refer to <http://www.jabber.org> for
    more information.

    Contact and support:

      o Mailing List for questions and announcements:

        jabber-users@postel.org

        Subscribe: <http://www.postel.org/mailman/listinfo/jabber-users>
                   <mailto:jabber-users-request@postel.org?subject=subscribe>
        Archive:   <http://www.postel.org/pipermail/jabber-users>

      o Administrator email: jabber - admin@postel.org

    Server Software:

      o ejabberd 0.9.1 <http://ejabberd.jabber.ru>

1.  Instructions

    The following instructions are specific to the Jabber service hosted
    at the Postel Center <http://www.postel.org>. Terminology and examples
    are based on a couple of popular Jabber clients (Psi & Gaim), but should
    be similar on other clients.

  1.1 Jabber Client Software

    You need a Jabber client software to use the jabber service. Most IM
    software also supports Jabber. Check the following link for an extensive
    list of client software:

    http://www.jabber.org/software/clients.shtml

  1.2 Account Registration

    Registration is required for every new user to create a new account.
    Select a Jabber ID in the form of "foo@jabber.postel.org", replace
    "foo" with your screen name. Registration is not needed when setting
    up a new client software with an existing account.

    When adding a new account in your clients:
      - Psi:  check "Register new account" & enter the complete Jabber ID
              (including "@jabber.postel.org") in the "Jabber ID" field
      - Gaim: enter the screen name (foo) and server name (jabber.postel.org)
              separately, then click "Register"

    Note that you also need to setup the correct connection parameters
    described below in order to register.

  1.2 Server Connection Parameters

    o Server: jabber.postel.org

    o Supported Settings:

      The server is open, supports both unencrypted and encrypted (TLS/SSL)
      connections using non-plaintext (hashed) passwords on the default ports
      (5222/5223). Default settings on most clients should work. The following
      settings are recommended:

      Select

        [o] Use TLS if available / STARTTLS (if the client applications
            support TLS such as Gaim)

        or

        [o] Use SSL encryption / Force old SSL (Psi does not support TLS)

      Uncheck

        [ ] Allow Plaintext Login / Allow plaintext auth over unencrypted
            streams
            (AFAIK no effect during registration)

    o Ports:

      For reference only, should be the same as the default on most clients.

        5222: TLS (STARTTLS) or unencrypted
        5223: SSL

2.  Proxy Setup

    This is only needed when you are behind a firewall that blocks the default
    jabber ports (5222/5223).

    o Type: HTTP Polling (NOT HTTP or HTTP Connect)[*]
    o Host: (blank)
    o Port: 0
    o Polling URL: http://jabber.postel.org:80/http-poll

    [*] Unfortunately, Gaim does not seem to support HTTP Polling, and the
        server on jabber.postel.org does not support HTTP (HTTP Connect).

3.  MUC - Multi-User Chat

    MUC services is enabled on jabber.postel.org. Users could create chatrooms
    and invite other users to join.

    To create or join a chatroom, use the following parameters:

    o Server/Host: conference.jabber.postel.org
    o Room: (the name of the chatroom)
    o Handle/Nickname: (the name you will appear in the room)
    o Password: (blank)

    Note that to create a chatroom, a user simply needs to join an unused room.
    You can also get a list of active or permanent rooms either through the
    "Room List" menu or "Service Discovery" on your Postel.org jabber account.
    Specify "conference.jabber.postel.org" as the conference server when
    prompted. On service discovery, chatrooms are listed under
    "ejabberd/mod_muc."

4.  Notes

  4.1 Psi Warning on Self-Signed Certificates

    Because jabber.postel.org uses self-signed certificate on the server side
    for SSL/TLS encryption, some clients will generate warning messages such
    as this:

    "The jabber.postel.org certificate failed the authenticity test.
     Reason: Certificate is self-signed."

    This only means the certificate for jabber.postel.org is not signed by
    any one of the commercial certificate authority ($199+ per year).

    There are two ways to avoid the warning message:

    (1) Under "Account Properties" => "Preference" tab:

        Check or select "Ignore SSL warnings".

    (2) Download the following certificate file and copy it to the Psi
        root certificate directory:

          <http://www.postel.org/jabber/jabber.postel.org.xml>

        Psi root certificate directory:

          FreeBSD:  /usr/local/share/psi/certs
          Linux:
          Mac OSX:  /Applications/Psi.app/Contents/Resources/certs
          Windows: