RVOUS_PROPOSE:ghoulgle:09461345-4C7F-11D1-8222-444553540000:ptHqF5JzAAA=:1:0.5.0.2:192.168.2.191:65.189.106.123:2607
This is what's sent when you try direct connect to another user on AIM. All the documentation I found on the TOC protocol skips this 1 command so I have no idea the structure.
Quote: "
toc_rvous_propose - Not Implemented Yet
"
Here's what I do know so far:
ghougle
= person who sent the request
09461345-4C7F-11D1-8222-444553540000
= service or UUID
192.168.2.191
= local IP from sender
65.189.106.123
= global IP from sender (ip to connect to)
2607
= probably suggested port to connect to
Here's what I'm guessing:
ptHqF5JzAAA=
= base64 encoded values?
1
= TLV
0.5.0.2
= cookie?
Here's the command to accept the connection invitation
Quote: "
toc_rvous_accept <nick> <cookie> <service> <tlvlist>
Accept a rendezvous proposal from the user <nick>.
<cookie> is the cookie from the RVOUS_PROPOSE
message. <service> is the UUID the proposal was
for. <tlvlist> contains a list of tlv tags followed by
base64 encoded values.
"
Any ideas?
Deadly Night Assassins