name mode size
doc 040000
Makefile 100644 198B
README 100644 5.6kB
jabber.c 100644 8.28kB
jc_pool.c 100644 25kB
jc_pool.h 100644 2.92kB
lock.c 100644 2.81kB
lock.h 100644 1.27kB
m_sem.c 100644 1kB
m_sem.h 100644 272B
mdefines.h 100644 653B
sha.c 100644 5.56kB
sip2jabber.c 100644 9.66kB
sip2jabber.h 100644 1.14kB
tree234.c 100644 41.16kB
tree234.h 100644 5.83kB
xml_jab.c 100644 13.67kB
xml_jab.h 100644 1.18kB
# $Id$ To: sr <> Subject: [Sr] IM gateway capabilities and limitations Hello, I made a brief about what IM gateway can or cannot do. The characteristics are what I found about on mailing lists or home page of the applications. I will keep the document updated with what it's coming. There is some place where I can put these documents, this, the other one sent couple days ago (imgw.pdf) and other future documents, where they can be accessed by anybody of us? Sending them to the list wastes a lot of space. Best regards, Daniel IM Gateway - capabilities and limitations - v1.0 ================================================ The gateway allows the message passing between SIP users and other IM users (ICQ, AIM, Yahoo ...). IM Gateway uses for this a Jabber server which has the facility of supporting many IM protocols (they are called IM transports). So, in fact, the gateway is between SIP and Jabber. Because the most of the IM protocols are not open source and they are the property of some companies, Jabber does not provide full support for these protocols. From time to time, the owner of the protocol changes the protocol structure, and for a while, that transport is no longer available. There are some guys doing some kind of reverse engineering on these protocols. But not whole protocol structure is discovered, each transport has its own limitations. In additions, many of the IM native clients allow only one user to be online at a moment, and IM servers could easy say that the hosts which have more than one open connection are not using a native client and block those addresses or the accounts. Next, are presented the IM transports that are running on our Jabber server, or they are wanted to be available. The capabilities and limitations are what can be found on the net about transports. AIM transport ------------- It is only one well known version of aim-transport. (web location: AIM-t provides basic interoperability between Jabber and AIM/ICQ network. Currently AIM-t is undergoing massive changes. It will be a standalone component once this is finished. * capabilities - currently supporting basic presence and messaging. - 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) * limitations - NO file transfer - NO multichat - NO user search - NO incoming SMS - NO import of server buddy lists - NO handling of incoming ICQ auth requests - ICQ messages may get dropped by AOL servers if your contact uses an old ICQv5 client. ICQ transport ------------- Excepting the AIM transport, there exists another distribution for ICQ transport. (web location: * capabilities - messaging (through server only) - presence notification - SMS support * limitations - no file transfer The AIM transport for ICQ. - see AIM transport A new versions of ICQ transport seems to be available now. But now place from where it can be downloaded - I sent a mail asking for a distribution. A short description can be found at IRC transport ------------- (web location: This version of IRC transport is a beta version * capabilities - It will connect to irc servers and allow you to talk to them, but it is still in heavy development * limitations - private messaging does not yet function - transport registration/notify will not be supported - groupchat 1.0 and 1.1 will not be supported in favor of the 2.0 iq:conferenec/iq:browse protocol you will be able to log into and create password protected groups now (although this may not work yet) - there still may be some other bugs but they aren't caught yet. - in testing, it has been fairly stable, although some functionality may not be there yet. - requires jabberd version 1.4 several functions used, including MIO, MTQ, and xhash functions were not available in previous jabber server versions MSN transport ------------- (web location: * capabilities - provides basic interoperability between Jabber and MSN (messaging/presence) * limitations - there are memory leaks in MSN-t so is better to be run in a seperate process and restart it from time to time - MSN-t uses TCP port 1863 for incoming connections so you have to open this port if you use a firewall. - the other parts excepting messaging/presence Yahoo transport --------------- (web location: As of 2002-07-10 this transport has ceased functioning (probably due to YIM protocol changes). The transport is being worked on - see JDEV mailing list : * capabilities - log into Yahoo Messenger server, and send/recv messages. * limitations ------------------------------------------------------- I've been trying to make available the Yahoo! transport on Jabber server from '', but Jabber does not connect to Yahoo server. The problem is that Yahoo! changed the protocol. Someone is working on the new version. Best regards, Daniel