1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
|
AIM/ICQ-Transport (stable branch)
=================================
http://aim-transport.jabberstudio.org
$Id: README,v 1.12.2.4 2003/03/14 15:05:45 maqi Exp $
Features
--------
- reliable messaging (via server only)
- simple user info retrieval (ICQ only)
may take some time, just wait...
- SMS sending (ICQ)
send "SEND-SMS:number:text" to any ICQ user, for example
"SEND-SMS:+4917012345:Test"
- away message retrieval (AIM only)
- offline messages (ICQ only)
- NO file transfer
- NO multichat
- NO user search
- NO incoming SMS
- NO import of server buddy lists
- NO handling of incoming ICQ auth requests
hint: disable "auth req'd" - it is insecure anyway
Installation
------------
This version of AIM-t is a module for Jabberd 1.4.x. While it can connect
to any Jabber server that supports the connect/accept mechanism, it can
only be run in a 1.4.x binary.
To build AIM-t uncompress the tarball. If you uncompressed it into the
Jabber directory you can run the configure directly and it will find the
jabberd 1.4.x sources needed to compile. Otherwise, you need to use the
--with-jabberd=PATH option to configure. At this point you can run make
and it should build just fine.
1. Main Jabber server configuration files
In order to have your main Jabber server accept connections from AIM-t,
you have to configure it accordingly.
For jabberd server, add the following to the <service> section of its
configuration file.
<service id="aim">
<host>aim.localhost</host>
<accept>
<ip>127.0.0.1</ip>
<port>5555</port>
<secret>someSecret</secret>
<timeout>30</timeout>
</accept>
</service>
Be sure to replace "localhost" with the full host name of your server
if you want users of other Jabber servers to be able to use this
transport. Also, the host name of the transport has to be resolveable
via DNS then.
In order to advertise the transport's services to the Jabber clients, add
the following to the <browse> section of the main jabberd configuration
file.
<service type="aim" jid="aim.localhost" name="AIM Link">
<ns>jabber:iq:gateway</ns>
<ns>jabber:iq:register</ns>
</service>
2. AIM module configuration files
An example configuration file is included (aim.xml), modify it as needed.
If you want to set up a separate transport for ICQ, just duplicate all
sections mentioned above and replace "aim" by "icq". Be sure to change
the connect/accept ports for the second transport instance of course.
Running
-------
Be sure to have the main Jabber server running, then
jabberd/jabberd -c aim-transport/aim.xml
Repeat this for the second AIM-t advertised as ICQ-t if needed.
If you run into trouble, add "-D" for debug output.
Notes
-----
- Firewalls
AIM-t currently only uses an outgoing TCP connection per session. So no
incoming ports need to be opened.
- Dropped Messages
ICQ messages may get dropped by AOL servers if your contact uses an old
ICQv5 client. This is not AIM-t's fault. Your contact should upgrade or
switch to Jabber ;-).
Bugs
----
If you experience crashes, please include a backtrace in your bug report
(see AIM-t's website). You get a backtrace by using gdb ("gdb -c core
jabberd/jabberd", "bt" command within gdb). To enable core dump files
use "ulimit -c unlimited" (bash).
|
