| Problem with X-NowMMS-Content-Location using MMSComp |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | ||||
| Stefan Li Unregistered guest |
Hi! I am using MMSComp to generate messages and I've found a problem. I need to define my own mimetypes for file extensions so I do this with your X-NowMMS-Content-Location: header field. The problem is, this only work when I generate pdu's using a smil file! When I try with the same .hdr file but without smil, i.e. "mmscomp test.hdr file1 file2 …" it ignores my defined mimetypes. Is it supposed to be this way or is it a bug? Regards Stefan Li | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5283 Registered: 10-2002 |
Hi Stefan, Sorry, this is an old posting that I missed. If you are still encountering a problem, can you please provide ZIP files with examples that illustrate your problem. (Preferably one zip where it all works correctly, and another where it does not.) In addition to putting the MIME types into the HDR file, you can define file extension to MIME type mappings in the MMSCTYPE.INI file (or in Windows itself). -bn | ||||
| Stefan Li New member Username: Stefan_li Post Number: 1 Registered: 12-2005 |
Hi bryce. I've attached and uploaded a zip file containg two examples. One with a directory called "WORKING" and another "NOT WORKING" As you will see in the testcase_1.hdr file I have added: "X-NowMMS-Content-Location: midifile.mid;TEST_CHANGE" at the end. In the "WORKING" directory I use the following command: "mmscomp testcase_1.hdr testcase_1.smil" Where the smil file links to a midifile. And in the "NOT WORKING" directory I use this: "mmscomp testcase_1.hdr midifile.mid" The execution in the "WORKING" directory results in a .mms file containg a midifile with Content-type "TEST_CHANGE" and everything works as it should. In the "NOT WORKING" directory however the .mms file has content-type "audio/mid" i.e. my definition in the .hdr file has been ignored.
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5361 Registered: 10-2002 |
Hi Stefan, I tried the "NOT WORKING" header file, and it worked for me. So I can only figure that something was fixed in more recent builds of MMSCOMP.EXE. I used the version that is included in http://www.nowsms.com/download/latestpatch.zip. -bn | ||||
| Stefan Li New member Username: Stefan_li Post Number: 2 Registered: 12-2005 |
Hi Bryce What do you mean by "worked for me"?. Because the setup in the "NOT WORKING" directory "works" here as well, it's just that the content type of the midifile.mid I defined in the header file is ignored. The header file is identical in both setups, the difference is the way I generate the message, i.e. in the first setup I use the header and smil file to generate the message and in the second setup I use the header and midifile directly. I tried with the latest patch and got the same result. | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5437 Registered: 10-2002 |
Hi Stefan, Apologies for the long delay. I guess I should have been more clear. In the "NOT WORKING" case, when I look at the resulting MMS message, I see TEST_CHANGE as the content type of midifile.mid file within the MMS message. I just confirmed, and I'm definitely using the MMSCOMP.EXE from the ZIP file that I referenced above. It has a file date of Aug-26-2005. Can you confirm that this is the MMSCOMP version that you are running, as I can't understand why we would be seeing this different behaviour. -bn | ||||
example setups
