|
This space left intentionally blank. |
Oscar Protocol Documentation |
Random Pidgin Files
|
Oscar Protocol Specification: Family 0x0015, Subtype 0x0003 unfinished
This can contain a wide array of information from the server. Info of other ICQ users,
Thanks to Adam Fritzler's libfaim for the basic structure of this.
Source: Server
Length | Description |
2 bytes | Family (0x0015) |
2 bytes | Subtype (0x0003) |
2 bytes | Flags |
4 bytes | Snac Request ID |
2 bytes | Type - 0x0001 |
2 bytes | Length L of the following |
L bytes | All information for this SNAC is in the value of this TLV, and the information is given in network byte order. This shows the sloppy way that ICQ support was added to oscar, IMO.
Length | Description |
2 bytes | Command length. This is L-2 |
4 bytes | The destination UIN (us) |
2 bytes | Command. This actually tells what the rest of the SNAC contains. You decide how to read in the rest of it based on what command it is. |
2 bytes | Request ID |
If command is 0x0041, then this is an offline message.
Length | Description |
4 bytes | The originating UIN (them) |
2 bytes | The year the message was sent |
1 byte | The month the message was sent |
1 byte | The day the message was sent |
1 byte | The hour the message was sent |
1 byte | The minute the message was sent |
2 bytes | The type of message |
2 bytes | Length L of the following |
L bytes | The actual message |
|
|
All material Copyright © 2000-2014, All Rights Reserved
Linux is a registered trademark of Linus Torvalds.
AIM is a registered trademark of America Online, Inc.
ICQ is a registered trademark of ICQ Inc.
All other trademarks are property of their respective owners.
|