[ejabberd] ability to interface with external components

Sander Devrieze s.devrieze at pandora.be
Fri May 21 02:24:15 MSD 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op vrijdag 21 mei 2004 00:21, schreef Erik Rojas Zúñiga:
> Hello,
>
> Ejabberd documentation says it has the ability to interface with
> external components like MSN, Yahoo, JIT, etc. But I have not seen any
> reference in the documentation that says how can that be configured.

Yes, that would be nice to have.

> Can anyone explain me how can I configure ejabberd so that clients can
> communicate with MSN, Yahoo, ICQ using ejabberd as gateway.

In the configuration of ejabberd under listened ports I have something like 
this:

          {5222, ejabberd_c2s,     [{access, c2s},
                                    {shaper, c2s_shaper}]},
          {5223, ejabberd_c2s,     [{access, c2s},
                                    {ssl, [{certfile, "/path/to/key.pem"}]}]},
          {5233, ejabberd_service, [{host, "aim.<serveraddress>",
                                   [{password, "<here the secret>"}]}]},
          {5234, ejabberd_service, [{hosts, ["icq.<serveraddress>", 
"sms.icq.<serveraddress>"],
                                   [{password, "<here the secret>"}]}]},
          {5235, ejabberd_service, [{host, "msn.<serveraddress>",
                                   [{password, "<here the secret>"}]}]},
          {5236, ejabberd_service, [{host, "yahoo.<serveraddress>",
                                   [{password, "<here the secret>"}]}]},
          {5237, ejabberd_service, [{host, "gg.<serveraddress>",
                                   [{password, "<here the secret>"}]}]},
          {5238, ejabberd_service, [{host, "ile.<serveraddress>",
                                   [{password, "<here the secret>"}]}]},
          {5239, ejabberd_service, [{host, "ll.<serveraddress>",
                                   [{password, "<here the secret>"}]}]},
          {5269, ejabberd_s2s_in,  [{shaper, s2s_shaper}]},

Remarks:
o You best use a recent version of jabberd1.4.x for the transports
o Verify the secrets over and over again if something don't works...this might 
help as I know :D
o You need to make the transports log and do xdb by themselves:

  <!--
     You need to add elogger and rlogger entries here when using ejabberd.
     In this case the transport will do the logging.
  -->

  <log id='elogger'>
    <host/>
    <logtype/>
    <format>%d: [%t] (%h): %s</format>
    <file>/var/log/jabber/error/aim-t.log</file>
  </log>

  <log id='rlogger'>
    <host/>
    <logtype>record</logtype>
    <format>%d %h %s</format>
    <file>/var/log/jabber/record/aim-t.log</file>
  </log>

  <!--
     Some Jabber server implementations do not provide
     XDB services (for example jabberd 2.0 and ejabberd).
     AIM-t is loaded into handle all XDB requests.
  -->

  <xdb id="xdb">
    <host/>
    <load>
      <xdb_file>/usr/lib/jabber/xdb_file.so</xdb_file> <!-- this is a lib of 
wpjabber or jabberd -->
      </load>
    <xdb_file xmlns="jabber:config:xdb_file">
      <spool><jabberd:cmdline 
flag='s'>/var/spool/jabber</jabberd:cmdline></spool>
    </xdb_file>
  </xdb>


- -- 
Mvg, Sander Devrieze.

JabberID: sander at l4l.be -- ( http://jabber.l4l.be/ )
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFArTATK+G8aHNHCSMRAnOaAKDPmuAzf/QIBUqoyvmBU7/SvmNGwQCfd+OR
MFcVBJFL9n5OsgF6zTUa+24=
=Vtzh
-----END PGP SIGNATURE-----


More information about the ejabberd mailing list