| MMS Conformance |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through February 03, 2005 ⬆ |
◄ ► |
| Author | Message | ||||
| manuel Unregistered guest |
hi everyone: i followed wap-209 to encode my mms. The result was shown correctly on the nokia 6230 emulator on my pc. however, the same thing transferred to a real sony ericsson t310 doesn't work. "message format corrupted" was shown on the screen of the phone. I wonder what the difference is in interpretation between the phones on the SAME mms, which is supposedly MMS 1.0 compliant?? manuel. | ||||
| manuel Unregistered guest |
hi everyone: the head for the mms in hex is starts like this: 8C 84 8D 90 85 04 41 25 E5 D5 84 1F 1F B3 89 61 70 70 6C 69 63 61 74 69 6F 6E 2F 73 6D 69 6C 00 8A 3C 53 4D 49 4C 50 41 52 54 3E 00 04 0E 34 03 83 81 EA 8E 74 65 78 74 2E 74 78 74 00 48 65 6C 6C 6F 2C 20 74 68 69 73 20 69 73 20 61 20 74 65 73 74 20 74 65 78 74 20 6D 65 73 73 61 67 65 2E 20 48 61 76 65 20 61 20 6E 69 63 65 20 64 61 79 21 21 82 71 13 61 70 70 6C 69 63 61 74 69 6F 6E 2F 73 6D 69 6C 00 81 EA C0 22 3C 53 4D 49 4C 50 41 52 54 3E 00 3C 73 6D 69 6C 3E 0A 0A 3C 68 65 61 64 3E 0A 0A 3C 6C 61 79 6F 75 74 3E 0A 0A 3C .... more data i suspect sony ericsson needs more mms headers as required by the wap209 specs. i have previously been successful in sending a similar MMS to the ericsson, but the source for generating it has been modified, and changes cannot be traced. my only memories is that there were a lot more headers before, and i got down to this refactored and trimmed version according to wap209... now i have to go back to redo all things again... meanwhile anyone can tell me where i got it wrong. manuel manuel | ||||
| George A. K Unregistered guest |
I think you have missed the mandatory header Transaction-ID. It should be after the message type header. | ||||
| manuel Unregistered guest |
Hi George, Thanks for your reply. I looked up one of my saved mms binary (which was supposed to be good, so I saved it) and found the Transaction-ID header. But strange that the Ericsson keep rejecting my mms even after the header has been added. Below is a segment of hex code from my mms, 8C 84 - retrieve conf 98 31 30 00 - transaction id 8D 90 - mms ver 1.0 85 04 41 29 A7 54 - date/time 89 18 80 2B 38 35 32 39 31 30 30 31 32 33 34 2F 54 59 50 45 3D 50 4C 4D 4E 00 97 2B 38 35 32 39 34 35 37 38 39 32 34 2F 54 59 50 45 3D 50 4C - from, followed by to 96 54 65 73 74 41 67 61 69 6E 00 - subject okie, i think this is quite enough for an mms client to display the mms on the client. but, coz i always get things wrong, pls check if my interpretation is correct. and also, is there something missing that i need to add to? the strange thing is the the original saved mms binary worked a while ago on the same ericsson phone...
| ||||
| manuel Unregistered guest |
Hi everyone, I got a nokia 6100 for testing, and the result is that the nokia couldn't get the mms from my web server as well... (same as the ericsson t310). there's something wrong which i cannot trace by now. the mms binary itself seems to be fine. i have to seek your experience to guide me thru this one.......... anything that u think might help, pls let me know, and i can put the info up here. thanks a lot. manuel | ||||
| George A. K Unregistered guest |
Manuel, I looked at attached MMS message (8002.mms). I find that there is an error in the Multipart encoding. The number of parts is mentioned as four while there are only three parts(text, Smil & the image)in the message. Pls correct me if I am wrong. George | ||||
