| More on decoding a .mms file.... (M-Retrieve.conf) |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Craig Dunn |
Im just ploughing through decoding the contents of an example MMS message that I picked up on a Kannal discussion list - I've decoded all apart from one bit, can anyone shed any light on this.... 8c 84 : Message type - M-retrieve.conf 98 31 77 37 37 34 51 6f 4b 75 74 45 50 39 66 7a 58 56 35 34 6e 62 41 20 00 - MMS ID - w774QoKutEP9fzXV54...etc 8d 90: MMS Transaction ID 85 04 3d ef 78 cb : Date from 1970 89 18 80 2b 33 35 37 39 39 35 33 36 32 31 34 2f 54 59 50 45 3d 50 4c 4d 4e 00 : From - +35799536214/TYPE=PLMN 97 2b 34 34 37 37 34 30 33 30 35 31 31 35 2f 54 59 50 45 3d 50 4c 4d 4e 00 : To: +447740305115/TYPE=PLMN 96 54 68 65 20 4d 61 74 72 69 78 00 : Subject- The Matrix 86 81 : DElivery report No? 90 81 : Read reply : No 8a 80 : Message class personal 84 content-type 19 b3 89 : ????????????????? 61 70 70 6c 69 63 61 74 69 6f 6e 2f 73 6d 69 6c 00 : application/smil ----- Does anyone know what 19 b3 89 is? And where those fields are defined? Thanks in advance. Craig | |||
| Todd Lucas |
Craig, The content type is encoded according to WAP-230-WSP, section 8.4.2.24. Its grammar is somewhat overloaded, which can lead to ambiguities that must be resolved at a higher level (see the MUST comments in the associated text). Your PDU has a value-length prefix, which means that it's encoded according to the content-general-form. The reason is that parameters were specified along with the content type. The length of 0x19 suggests that there's more to this chunk than was posted, so I can only guess at the details. The content type (media-type in the BNF) is 0xb3, which is 0x33 or application/vnd.wap.multipart.related. The parameter 0x89 is 0x09 which, according to Table 38 in Appendix A (Well-Known Parameter Assignments), means Type. - Todd | |||
