ICQ gateway in OpenFire

Published on July 24, 2009

ICQ gateway in OpenFire

    Everything turns out to be very simple. Only here, not all clients can support this (for example, Spark does not know how to work, but QIP Infium can).
    Where to start and what to do:
    1. There is an installed and configured jabber server - OpenFire (http://www.igniterealtime.org/)
    2. There are IM clients based on QIP Infium that are already connected to our jabber server


    So proceed to the "file"


    The first step is to install the IM Gateway plugin , which is on the list of available ones. To do this, in the administration panel of the OpenFire server (http: // servername: 9090), go to the " Plugins " section and go to " Available Plugins " in the left menu . We have a list with plugins available for installation. We need to click on the (+) mouse in the line of the " IM Gateway " plugin and wait for a while, during which the server downloads and installs this extension.

    “File”


    Actually, the configuration of the ICQ gateway is ahead. In the OpenFire server control panel : Server -> Gateways we find the following picture: we are presented with a list of possible gateways to IM servers - AOL, ICQ, IRC, MSN, Gadu-Gadu, Yahoo! Messenger and a little bit more experimental. It will take a little to configure the gateway we need, namely ICQ, so we put a checkmark in front and open the " Options " tab. Of all that was installed by default, you only need to change the “Encoding” line to support the “Great and Mighty”. In my case, I chose UTF-8, because QIP client works without problems with this type of encoding. Actually the image of what we see:



    In the “Permissions” tab, you may need to specify which user or groups are allowed to use this gateway, by default it is set that everyone can.

    In the “Test” tab, the connection to the ICQ server is checked.

    Actually, the server-side configuration on this will be completed.

    "Welcome" or connect IM client


    There are two ways to configure connections to the gateway:
    1. The administrator of the jabber server himself adds users to the gateway

    2. The user himself configures the client to connect

    Admin hands

    To do this, you need the UIN of the user and his password for the ICQ service. Then, through the admin panel, go to Server -> Gateways -> Registrations and select " Add a new registration " and fill in the fields: where user (JID) is the username on the jabber server, gateway is the configured gateway, username is the user UIN, password is the password from the specified UIN on the ICQ server, nickname - actually the nickname. And click "Add" to add the user to the list, if the user was connected, then he will automatically connect to the gateway in a few moments. Cons of this method: "knock out" the password and UIN from the user.





    User hands

    In the client, go to the settings "server transports": On the line with the host name, call the drop-down menu and select the " Registration " or double-click: In the window that appears, simply enter the UIN and password and if everything was correct, then users will appear in the roadster, that you have in your ICQ contacts. Cons of this method: the average user will have to explain / show / do this procedure for him.









    What happened


    When everything was done correctly, the user gets access to communication through ICQ. In this case, the administrator or management gets the opportunity to give / not to let people communicate via ICQ and, in the case of the installed Archive plug-in, view users ’correspondence via ICQ. That's all.