| MMS-IN directory |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
Hi Bryce, I would like to know if the same headers are written in the hdr files in the MMS-IN directory for all different models and handset manufacturers? I am trying to build an MMS to website application so I need to know if the structure is the same for all manufacturers? If different information is posted by diff manufacturers, do you have some sample hdr files of the manufacturers? What suggestions would u give to implement this sort of thing using java to parse the hdr files. Is the sender phone number written by all manufacturers???? Thanks | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4073 Registered: 10-2002 |
Hi, You should see similar headers. But basically I'd ignore everything that isn't relevant to your needs. There should always be a sender address ("From" header) for a message routed through an operator MMSC. Just note that a from header is not strictly required, so handle it gracefully (i.e., you might skip the message) if one is missing. Subject is optional. Date should be present, but I would recommend handling it gracefully if not present. Beyond that, it is basically an issue of parsing the "X-NowMMS-Content-Location:" headers for the content. That should be relatively straightforward ... however there is one thing you might want to be aware of with regard to "text/plain" content. Some different phones may use different character sets. We'll append charset=xxxx to the content type to indicate the character set. And we do pass it through as it was received by the phone. Primarily you will see utf-8. But sometimes you will see iso-10646-ucs-2 which is 16-bit unicode. And sometimes you will see iso-8859-1 which is the standard Western Europe (Latin) character set. -bn | |||
| Anonymous |
Bryce, Is there some open source MMSC available through which I can simulate sending mms msgs through different handset simulators? Can you recommend how I can go about building this application? What points do I need to keep into consideration?How is the mms-in directory approach different from the xml/soap wrapped contentapproach? Which is better? Thanks | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4149 Registered: 10-2002 |
I'm sorry, but I don't really have any pointers for you. Well, maybe some general advice ... NowSMS is an MMSC. If you had a handset simulator that could talk to a live MMSC, then that would be a step in the right direction. The problem is that most emulators that I have seen do not implement the actual over-the-air protocols for MMS. So I don't see what value another MMSC would offer you, because if you had such a handset simualtor, you could just configure it to use NowSMS as its MMSC. Basically, there's no substitute for live devices for testing in this area. The MMS-IN directory approach is specific to NowSMS, whereas the XML/SOAP wrapped approach is based upon an open standard which would make it easier for you to deploy in different configurations in the future. Neither is necessarily better than the other. The MMS-IN directory interface is easier (especially for prototyping). The MM7 (XML/SOAP) interface is potentially more flexible for porting to other direct MMSC connections. -bn | |||
