Re: [Gaim-devel] WinAIM 5.2 OSCAR protocol

[Matthew S. <mat...@ze...>]

On Thu, Sep 25, 2003 at 10:13:57PM -0700, Bryce C wrote:
> I'm not familiar with "WinAIM" but I do know that SMS is simply an addon
> to the OSCAR protocol. Just send an IM to the SN +1XXXXXXXXXX, where the
> +1 is country code (I think it's U.S. only right now), and XXXXXXXXXX is
> your 10 digit SMS/cell phone number.

Nifty; I have my client (Net::OSCAR, perl implementation) signon on as 
5.2 beta, and it works.  The resulting SMS claims that I can reply to 
that message.  Of course, I didn't have that capability set, so that 
capability must be something else.  I guess it's either "encrypted IM" 
(although aim.h already has a SECUREIM capability) or "enhanced file 
transfer and direct IM".

Here's the clientinfo for 5.2.3292:

#define CLIENTINFO_AIM_5_2_3292 { \
        "AOL Instant Messenger, version 5.2.3292/WIN32", \
        0x109, \
        0x0005, 0x0002, \
        0x0000, 0x0cdc, \
        0x000000ee, \
        "us", "en", \
}

Also, all of the 0x0629 toolversions are now 0x0739, and the TLV chain 
in the 0x0017/0x0002 signon SNAC has an empty value 0x004C.

> On Thu, 2003-09-25 at 21:58, Matthew Sachs wrote:
> > I'm going to have a go at figuring out the protocol for the new 
> > features in WinAIM 5.2, particularly the SMS stuff.  I'm looking at 
> > the set_info (0x0002/0x0004) packet it's sending out, and I've noticed 
> > a few interesting features:
> > 
> > -Capabilities:
> > 	games sendlist chat interop voice extstatus sendfile 
> > 	unknown2 directim buddyicon addins
> > 
> > 	"unknown":
> > 	    0x09 0x46 0x01 0xff 0x4c 0x7f 0x11 0xd1
> > 	    0x82 0x22 0x44 0x45 0x53 0x54 0x00 0x00
> > 
> > 	I'm thinking that this is probably the capability for the SMS 
> > 	features.
> > 
> > Also, the TLV chain has type 0x06 with data 0x0004 0x0002 0x0002.  Any 
> > clues as to what this might be?