Differences between version 2 and predecessor to the previous major change of JabberTransport.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Sunday, April 18, 2004 8:22:40 pm | by DanielLawson | Revert |
| Older page: | version 1 | Last edited on Sunday, April 18, 2004 7:31:29 pm | by AristotlePagaltzis | Revert |
@@ -2,14 +2,12 @@
----
''InNeedOfRefactor: rest needs fixing up''
-
-For example, you can add the JIT (Jabber ICQ transport) at jit.jabber.meta.net.nz. Fill in your ICQ account details, and it will automatically pull down your server-stored ICQ contact list and add them to your Jabber roster. They get given JIDs of ''[UIN]''@jit.jabber.meta.net.nz, and can be addressed as such.
__Note__: the [DNS] names below are fictional, make sure you check what your [Jabber] server uses.
[ICQ] and [AIM] actually use the same protocol, so the AIM-t transport can be used for [ICQ] as well. However, the JIT transport handles [ICQ] messaging and ICQ-SMS a lot better than the AIM-t transport.
If your [Jabber] server uses the AIM-t transport, you should subscribe to the icq.jabber.example.net agent, using your ICQ username and password, and then you can add contacts of the form icqid@icq.jabber.example.net. You can send [SMS] messages by sending something like the following to any [ICQ] recipient on your roster: __SEND-SMS:+cellphonenumber:<message>__
If your [Jabber] server uses the JIT transport, then use that instead. Its a lot nicer, supports user searching correctly, handles [SMS] better, so on. You can add contacts of the form icqid@jit.jabber.example.net for [ICQ], or phonenumber@sms.jabber.example.net for [SMS].
