Protocols/MSNP/MSNC/SIP: Difference between revisions
Jump to navigation
Jump to search
(→I) |
Animadoria (talk | contribs) No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Protocols/MSNP | {{Protocols/MSNP | ||
|section=MSNC}} | |||
Latest revision as of 03:40, 31 August 2023
| MSNP Protocol |
| MSNC |
| Overview • MSNObject |
| Client Capabilities |
| P2P protocol |
| Transports • MSNSLP |
| Headers |
| P2Pv1 Binary headers |
| P2Pv2 Binary headers |
| Transfers |
| Display Pictures |
| Custom Emoticons |
| File Transfer |
| 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) |
Overview
SIP, Session Initiation Protocol, is commonly used along with the UBM command. It is sent in XML form, and has more important data in a massive base64 encoded string sent along with it. Very much alike MSNSLP See http://www.ietf.org/rfc/rfc2543.txt for details.
Example
Within the UBM payload:
<sip e="base64" fid="0" i="2d20e210bb3f45fead80f7bf7ee8bf07"><msg> SU5WSVRFIHNpcDpvbWVnbGVib3RAaG90bWFpbC5jb20gU0lQLzIuMA0KYzogYXBwbGljYXRpb24v c2RwDQpVc2VyLUFnZW50OiBVQ0NBUEkvMy41LjY4NzIuMA0KQ1NlcTogMSBJTlZJVEUNCnY6IFNJ ...</msg></sip>
Explanation of basic fields
E
This specifies the what the message is encoded with. This is base64 almost every time. Other types are unknown.
Fid
This is presumably an ID number of the request.
I
The value of the Call-ID field.
The MSG element
Inside the msg element, is a, usually very long, base 64 encoded message.
Example
A typically decoded message looks like this: (This is from a Windows Live Messenger 'Voice Call' request.
INVITE sip:email@addr.ess SIP/2.0\r\n c: application/sdp\r\n User-Agent: UCCAPI/3.5.6872.0\r\n CSeq: 1 INVITE\r\n v: SIP/2.0/TCP 127.0.0.1:1373\r\n v: SIP/2.0/TCP 127.0.0.1:1376\r\n MS-Keep-Alive: UAC;hop-hop=yes\r\n Allow: INVITE, BYE, ACK, CANCEL, INFO, UPDATE, REFER, NOTIFY, BENOTIFY, OPTIONS\r\n f: <sip:buddy@live.com;mepid=AB14091188684C439B51838E21CC464D>;tag=46f287b705;epid=5e67e6a2c0\r\n i: 2d20e210bb3f45fead80f7bf7ee8bf07\r\n Max-Forwards: 70\r\n k: 100rel\r\n k: Replaces\r\n k: ms-early-media\r\n k: ms-sender\r\n k: ms-safe-transfer\r\n k: histinfo\r\n k: timer\r\n m: <sip:buddy@live.com;mepid=AB14091188684C439B51838E21CC464D>;proxy=replace;+sip.instance="<urn:uuid:396BFFAF-8595-52C8-9ACB-00B50175C93F>"\r\n t: <sip:email@addr.ess>\r\n MS-Conversation-ID: f=0\r\n Record-Route: <sip:127.0.0.1:1373;transport=tcp>\r\n l: 1760\r\n \r\n v=0\r\n o=- 0 0 IN IP4 207.46.124.251\r\n s=session\r\n c=IN IP4 207.46.124.251\r\n b=CT:99980\r\n t=0 0\r\n m=audio 41994 RTP/AVP 114 111 112 115 116 4 8 0 97 13 118 101\r\n a=ice-ufrag:FRzl\r\n a=ice-pwd:26U2T6AAOAThyPbh0uxjJLOc\r\n a=candidate:1 1 UDP 2130706431 10.0.1.55 22246 typ host \r\n a=candidate:1 2 UDP 2130705918 10.0.1.55 11556 typ host \r\n a=candidate:2 1 UDP 16647679 207.46.124.251 41994 typ relay raddr 207.46.124.251 rport 41994 \r\n a=candidate:2 2 UDP 16647678 207.46.124.251 56207 typ relay raddr 207.46.124.251 rport 56207 \r\n a=candidate:3 1 TCP-PASS 6555135 207.46.124.205 52918 typ relay raddr 207.46.124.205 rport 52918 \r\n a=candidate:3 2 TCP-PASS 6555134 207.46.124.205 52918 typ relay raddr 207.46.124.205 rport 52918 \r\n a=candidate:4 1 UDP 1694235647 **.175.**.100 34353 typ srflx raddr 10.0.1.55 rport 34353 \r\n a=candidate:4 2 UDP 1694235134 **.175.**.100 33468 typ srflx raddr 10.0.1.55 rport 33468 \r\n a=candidate:5 1 TCP-ACT 7076351 207.46.124.205 52918 typ relay raddr 207.46.124.205 rport 52918 \r\n a=candidate:5 2 TCP-ACT 7075838 207.46.124.205 52918 typ relay raddr 207.46.124.205 rport 52918 \r\n a=candidate:6 1 TCP-ACT 1684797439 **.175.**.100 48701 typ srflx raddr 10.0.1.55 rport 48701 \r\n a=candidate:6 2 TCP-ACT 1684796926 **.175.**.100 48701 typ srflx raddr 10.0.1.55 rport 48701 \r\n a=maxptime:200\r\n a=rtcp:56207\r\n a=rtpmap:114 x-msrta/16000\r\n a=fmtp:114 bitrate=29000\r\n a=rtpmap:111 SIREN/16000\r\n a=fmtp:111 bitrate=16000\r\n a=rtpmap:112 G7221/16000\r\n a=fmtp:112 bitrate=24000\r\n a=rtpmap:115 x-msrta/8000\r\n a=fmtp:115 bitrate=11800\r\n a=rtpmap:116 AAL2-G726-32/8000\r\n a=rtpmap:4 G723/8000\r\n a=rtpmap:8 PCMA/8000\r\n a=rtpmap:0 PCMU/8000\r\n a=rtpmap:97 RED/8000\r\n a=rtpmap:13 CN/8000\r\n a=rtpmap:118 CN/16000\r\n a=rtpmap:101 telephone-event/8000\r\n a=fmtp:101 0-16\r\n a=encryption:rejected\r\n \r\n