Protocols/MSNP/MSNP12/Changes: Difference between revisions
m (1 revision imported) |
Animadoria (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{Protocols/MSNP | {{Protocols/MSNP | ||
|section=MSNP12}} | |||
= Contact Types = | = Contact Types = | ||
Latest revision as of 10:50, 13 May 2022
| MSNP Protocol |
| Version 12 |
| Overview • Changes |
| Overview |
| Introduction • Terms • Clients |
| Reference |
| Error List • Commands • Relying Party Suite • Spotlife |
| Services |
| XMPP • HTTP Gateway • Tabs • Activities |
| Documentation |
| Development Tools • MSNP Grid |
| Polygamy • URLs used by MSN |
| Documents |
| Protocol Versions |
| Version 21 |
| Version 18 |
| Version 16 |
| Version 15 |
| Version 14 |
| Version 13 |
| Version 12 |
| Version 11 |
| Version 9 |
| Version 8 |
| Version 2 |
| MSNC |
| Introduction • P2P • Object Descriptor • Display Pictures • File Transfer |
| Scenarios |
| Microsoft Messenger for Mac |
| MSNP on WebTV (MSNTV) |
Contact Types
MSNP12 introduces the notion of contact types. The contact type, also often refered to as the Network ID indicates the type of contact, or more specifically, which network the contact is connected to.
Currently the following types of contacts are known. It is unknown when these types were introduced, so some types may not be available until Protocols/MSNP/MSNP13, Protocols/MSNP/MSNP14 or higher.
0x01 : Windows Live 0x02 : Office Communicator 0x04 : Telephone 0x08 : MNI (Mobile Network Interop, used by Vodafone) 0x10 : Smtp (Jaguire, Japanese mobile interop) 0x20 : Yahoo
New commands
LKP
Note! It is uncertain whether this command was added in P11 or P12.
This command looks up phone numbers, and returns the same parameters you gave it upon success. This is useful if you want to use the "send a message to a mobile device" feature of MSN Messenger: You must first add the phone number to your AL list, and verify that the phone number is valid.
< LKP 10 tel:+31123456789 > LKP 10 tel:+31123456789
The command will return 201 if there is an incorrect parameter (for example, if you try to URL encode the phone number, or if you send it a string like "helloworld"). If the phone number could not be resolved (they cannot receive messages via MSN Messenger), it will return a 235 error.
NOT
Stands for Notification, the command still has to be explained, see the talk page for an example payload.
< NOT 870 <payload>
870 being the payload size and the payload being an HTML/XML document with informations about MSN spaces. Probably about new changes to other spaces from users on your FL, thus adding a star next the the users in the list when it has been modified.
Changed commands
LST
The LST command now has an additional parameter. The parameter represents the type of the contact. For a complete list of types, see the list on the Protocols/MSNP/MSNP14/Changes page.
LST N=email@domain.com F=Nickname C=6bef15dc-33cf-4e63-8a5c-271e5a1f5031 11 1 49824449-acba-4a44-ac09-53da2f0b59f9 LST N=tel:+131123456789 F=tel:+131123456789 C=eca0d232-2d18-4b30-9200-63d94add303d 3 4 BPR PHM tel:+131123456789 1
JOI
When someone joins a conversation, the server will now also send an additional parameter with the capabilities of the participant. This way, even if you do not have the person on your own contact list, you can still determine which features their client supports.
JOI passport@domain.com Friendly%20Name 1343062052
IRO
Like the JOI command, the IRO command now also includes the capabilities of the participant as an additional parameter.
IRO 1 1 1 passport@domain.com Friendly%20Name 1343062052