| Sending MMS notification from the NowSMS MMS GUI |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through February 20, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Ivan Markoski Unregistered guest |
When trying to send a precompiled MMS message (which was compiled with Adobe Golive + Nokia add-on) I get the follwing error: Error: Invalid MMS Content MMS Message Type missing or invalid (should be m-retrieve-conf) Any help? Advice how to precompile a message with NowSMS? Thanks, Ivan | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1091 Registered: 10-2002 |
Hi Ivan, The Nokia tools like to create compiled MMS messages of the type "m-send-req". This format is the format that you use to submit a message to an MMSC. Unfortunately, if you try to send an MMS notification message out to tell a mobile phone to fetch one of these "m-send-req" messages, the mobile phone will reject the message, just as NowSMS does. (This is why we include this check.) As the format of the "m-send-req" and "m-retrieve-conf" messages is very similar, you can often just flip the second byte of the file to convert formats. An "m-send-req" format file always starts with the bytes 8C 80. An "m-retrieve-conf" format file always starts with the types 8C 84. So changing that second byte will often do the trick. There's just one problem that you can run into doing this. In the "m-send-req" format, the "Date:" header is optional, while it is required in the "m-retrieve-conf" format. Some MMS clients will refuse an MMS message if it does not have a "Date:" header. If you actually post the content of the compiled MMS message to NowSMS (Send MMS Message instead of Send MMS Notification), we will convert the format and insert required headers. -bn | |||
