Version 1.1

Background
XMPP and Jabber servers have long supported external components and XMPP extention (XEP) 0114 was written to document the requirements for an external component to connect to an XMPP or Jabber server. Additionally, ever since XMPP servers have existed, users have wanted to connect to 'legacy' Instant Messaging communities. Thus, the term 'gateway' or 'transport' was coined, describing an external XMPP component that supported proxied connections to public Instant Messaging services such as AIM, ICQ, MSN and Yahoo. XEP 0100 documents the interaction between an XMPP user and an XMPP Gateway (a specialized XMPP component).

Problem
Several open source projects have emerged to provide gateways ('transports') to the XMPP community. Unfortunately, the open source gateway developers often use less than robust open source instant messaging protocol libraries. The result - an unreliable, unstable, and unsupported XMPP Gateway.

Solution
JBuddy XMPP Gateway leverages the robust, reliable and supported JBuddy SDK as its foundation so the resulting product is stable and supported. Further, because the JBuddy SDK supports AIM, ICQ, MSN, Yahoo and other enterprise Instant Messaging networks, the JBuddy XMPP Gateway provides a single, unified XMPP Gateway supporting many protocols in a simple to deploy solution.

Requirements

Public Instant Messaging Services Supported

Tested, Compatible XMPP Servers