Known Issues in the JBuddy SDK

Known Issues

Currently the JBuddy Bot Framework API is only directly available through XML and Java, however other environments can be leveraged using the the url or system tasks.
The JBuddy IM Bot Framework leverages the JBuddy SDK but is licensed independently of the JBuddy SDK. Please contact Zion Sales for clarity

If you don't have specially provisioned screenname(s) on the AIM server, the AIM server will limit outgoing message size and speed. An error message may be generated or a message or connection dropped if these limits are exceeded. Presently the message size limit is 2048 bytes but the command length must be taken into account so a users message should be closer to 2000 bytes to be safe.
If you don't have specially provisioned screenname(s) on the AIM server, AIM users can issue 'warnings' to other users who send them messages they find offensive or intrusive. As the warning percent increases, the AIM user has less capabilities and eventually is unable to connect to the AIM network for a 'cool off' period of time. For Server-side JBuddy use this can be a real concern especially if users don't 'opt-in' to receive your IMs./li>
JBuddy AIM does not support the following AIM features: Buddy Icon, Games, IM Image, Talk

See the AIM known issues above since some may apply to ICQ because they are both run by AOL.
JBuddy ICQ is not currently able to send conference invitations but can join c onferences if invited.
Out of band User Information Requests such as email, etc is not currently available.
No Support for Visible List. If you change your presence to Invisible, you will appear offline to anyone who may have you added to their buddy list, with the exception of the users on your "Visible" list. Users on your Visible List will always see you online. While in invisible mode, if you send someone a message, as a side effect, that recipient is added to your Visible List. This user will now see an Invisible Eye icon next to your name in their buddy list when you go into invisible mode. JBuddy 5 doesn't support the Visible List, or the Invisible List (users on this list always see you as Offline but may still contact you).

JBuddy 6.3.100815 release restores connectivity to MSN lost in early August. This interim MSN release may not support file transfers with modern MSN and Live Messenger clients. We hope to restore this functionality in the near future.
Buddy properties such as phone number and email are not currently available through the JBuddy SDK MSN API.
JBuddy uses the Reverse List Prompting mode as stored on the MSN IM Server for this user to determine if an IMessage.AUTH_REQUEST should be directed to the JBuddy client. The default mode for new MSN IM users is to prompt for authorization.
JBuddy uses the Privacy mode as stored on the MSN IM Server for this user to determine if messages directed to this user from other users not currently in the DenyList show be allowed. The default mode for new MSN IM users is to allow messages.
JBuddy MSN requires SSL for authentication. Java 1.4+ includes the SSL library however in Java 1.3.1 environments, JSSE library is required.

JBuddy Message Server currently does not support multi-user chat (conferencing) so JSC does not support the conferencing API.

JBuddy does not include support for conferencing for Microsoft Live Communications Server (LCS 2005). JBuddy does support file transfer for both LCS 2005 and OCS 2007. Also JBuddy does support conferencing for Microsoft Office Communications Server (OCS 2007).

JBuddy's support for Lotus Sametime 7.5+ does not currently include support for voice or video.

Concurrent connections (clients) supported by JBuddy is limited by the number of Threads within a JVM. Some JREs support thousands of concurrent threads. Currently JBuddy AIM, ICQ, and YIM IClient's use one thread per client. MSN, SAMETIME, use one thread per active conversation. XMPP and JSC use two threads per client.