Differences between current version and revision by previous author of JabberTransport.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
Newer page: | version 8 | Last edited on Friday, July 7, 2006 2:04:00 pm | by CraigBox | |
Older page: | version 7 | Last edited on Sunday, May 23, 2004 6:44:51 am | by AristotlePagaltzis | Revert |
@@ -1,13 +1 @@
[Jabber] supports transports, server-side plugins which provide a gateway to other communication services such as multiuser conferencing, or foreign protocols like [ICQ], [AIM], [MSN], YahooMessenger, [IRC], or even [SMTP] and [IMAP] (ie [Email]). Thus, JabberClients need not support any other protocol than [Jabber] itself. [Jabber] servers usually have a list of available transports, often with descriptive names like __icq.jabber.org__.
-
-----
-
-''InNeedOfRefactor: rest needs fixing up''
-
-__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. It's a lot nicer, supports user searching correctly, handles [SMS] better, and so on. 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. It maps [UIN]s to [JID]s of the form ''[UIN]''@jit.jabber.example.net for [ICQ], or ''phonenumber''@sms.jabber.example.net for [SMS].