blob: cb2dd053f53307ec2e5f83b26cfcb6f5a833a625 (
plain)
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
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
|
<jabber>
<!-- you can add elogger and rlogger entries here if
you don't want the main Jabber server do the
logging
<log id='elogger'>
<host/>
<logtype/>
<format>%d: [%t] (%h): %s</format>
<file>icqerror</file>
</log>
<log id='rlogger'>
<host/>
<logtype>record</logtype>
<format>%d %h %s</format>
<file>icqrecord</file>
</log> -->
<!-- Some Jabber server implementations do not
provide XDB services (for example jabberd 2.0).
Configure XDB here to have WPJabber handle all
XDB requests. This is strongly recommended if
you use xdb_ldap, xdb_sql or other non-file XDB
implementations, too.
See xdb_file directory for more information.
<xdb id="xdb">
<host/>
<load>
<xdb_file>xdb_file/xdb_file.so</xdb_file>
</load>
<xdb_file xmlns="jabber:config:xdb_file">
<spool><jabberd:cmdline flag='s'>./spool</jabberd:cmdline></spool>
</xdb_file>
</xdb> -->
<!--
localhost is your jabber host.
Replace "localhost" by the full host name of your server
and have all host names here resolveable via DNS if you
want the transport to be available to the public.
-->
<service id="icq.localhost">
<!-- to enable sms. Replace localhost with the same name as above -->
<host>sms.icq.localhost</host>
<!-- JIT configuration -->
<icqtrans xmlns="jabber:config:icqtrans">
<sms>
<host>sms.icq.localhost</host>
<show>away</show>
<status></status>
</sms>
<instructions>Please enter your UIN and password</instructions>
<search>Search users in ICQ</search>
<vCard>
<FN>JIT</FN>
<DESC>Jabber ICQ Transport</DESC>
<URL>http://jit.jabberstudio.org</URL>
</vCard>
<!-- Hashtable for users -->
<prime>3907</prime>
<!-- Send messages from icq as chat to jabber clients -->
<chat/>
<!-- Enable this for ICQ web presence
<web/> -->
<!-- If you don't want jabber:x:data forms
in reg and search uncomment this tag.
Not recomended -->
<no_xdata/> -->
<!-- Remove this tag to disable JIT's own contact list.
This will break the transport if it can not request
the user's roster via xdb get then (meaning the peer
uses jabberd 2 or the peer uses a remote jabber
server). -->
<own_roster/>
<!-- When present, this tag will tell JIT not to try to
get the user's roster (which will take a bit of time
to fail in scenarios described above). -->
<no_jabber_roster/>
<!-- File with stats -->
<user_count_file>/var/log/jabber/jit.session_count.log</user_count_file>
<!-- Interval beetween checking sessions: ping, messages, acks -->
<session_check>5</session_check>
<!-- Reconnect retries. -->
<reconnects>5</reconnects>
<!-- Time in sec when session can be inactive, 0 - disabled -->
<session_timeout>18000</session_timeout>
<!-- Charset -->
<charset>windows-1252</charset>
<!-- These IP is login.icq.com
Use only IPs here, no host names.
You can use hostnames but this will slow down JIT due to DNS resoling
ICQ Changes the IP alot. So will use name here
-->
<server>
<host port="5190">login.icq.com</host>
</server>
</icqtrans>
<!-- JIT module -->
<load>
<icqtrans>/usr/lib/wpjabber/jit.so</icqtrans>
</load>
</service>
<pidfile>/var/log/jabber/jit.pid</pidfile>
<!--
The settings here have to match the setting you made
in your main Jabber server's configuration file.
Replace localhost with your main jabber server host name
-->
<service id="icqlinker">
<uplink/>
<connect>
<ip>127.0.0.1</ip>
<port>5555</port>
<secret>someSecret</secret>
</connect>
</service>
</jabber>
|
GitWeb