| MMSCOMP header file |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 09, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| David Klugmann |
Does anyone have a sample header file I can use when compiling a GIF and an AMR into an MMS using the MMSCOMP utility ? Many thanks for any help. David | |||
| Bryce Norwood - NowSMS Support |
David, A header file for MMSCOMP can be very simple (with reasonable defaults selected by MMSCOMP), or it can be more complex for specialised needs. I tend to keep it simple. I usually recommend that you include at least a "From:" and a "Subject:" header. So you might do something like this:
(Although the docs say that "X-MMS-Message-Type:" is required, we will default to "m-retrieve-conf" if that header is not provided.) Let's say you save the above as "test.hdr", and that your GIF is named "image.gif" and your AMR is named "sound.amr". To turn that into a compiled MMS message, run:
Alternatively, you could add "X-NowMMS-Content-Location:" headers to reference image.gif and sound.amr ... instead of referencing them on the command line. MMSCOMP reads default MIME content type assignments for file extensions from MMSCTYPE.INI, but you can also set them explicitly using this "X-NowMMS-Content-Location:" header. For example:
Without a SMIL file in the MMS message, the MMS client will not automatically play your audio. Usually the user would need to scroll to an icon for the audio file, and click a button to play it manually. So you might want to consider adding a SMIL file into the list of content files. I posted an example of a SMIL file for this purpose on the following thread: http://support.nowsms.com/discus/messages/1/828.html When you create the SMIL file, simply add it to the command line above as an additional content file, or add an "X-NowMMS-Content-Location:" header for it as above. Basically, the SMIL file gets packed into the MMS message, just like the image and audio files. -bn | |||
| David Klugmann |
Bryce Thanks very much for the prompt support and the sample header files. A few more things. We have opted for the moment for storing compiled messages on a file system accessible via HTTP and delivered via MMS notification. 1) Is the To column in the header optional ? Since an MMS notification will already have been sent to the phone is it therefore true it's not needed as part of the MMS itself. Also having the To column I suppose limits you if you want to have the same MMS able to be sent to many users, or is it purely descriptive and has no functional use ? 2) We compiled a message with mmscomp and used the from/to header you suggested. It worked fine. Is there any way to view it running before sending it to the phone. That way at least we know it's a fully functioning MMS and isolates any problems not to do with transmission. Can anything like MMS composer read and play files generated by MMSCOMP ? 3) Out of interest where does the MMSC store it's MMS's and can we see them ? I assume with our setup (MMS notification only) the MMSC is not required for us. Thanks again David | |||
| Bryce Norwood - NowSMS Support |
David, 1.) Yes, the "To:" field is optional. An MMS client wouldn't do anything with this field anyway, except maybe to offer a "Reply All" option, in addition to a "Reply" just to the sender. 2.) I've got the Nokia Multimedia Player installed on my system, and it will play ".mms" files. But I have to say it is really lousy quality (and it is not happy if there is not a SMIL file in the MMS message). Some simulators will let you open an MMS (for example, the Nokia 7210 simulator has a file/open option, and you can have the simulator receive an MMS using this dialog and pointing it to a compiled MMS file on the local hard drive). In my mind, there's really no substitute for a real phone. But the above might help you out. 3.) Under the MMSCDATA directory. | |||
| David Klugmann |
Thanks again for the help. David | |||
