| Anyone can send me a workable MMS file |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Simon Li |
Help. I always got blank in the MMS body or "unsupported media file". Thanks!!! | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Simon, I've sent you an e-mail with two compiled MMS files. -bn | |||
| Leonard Chen |
Hi Bryce, Could you please send some compiled MMS files to me? Thanks in advance. | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Leonard, You've got mail. -bn | |||
| Feras Diab |
hello Bryce is there difference between the handsets regarding the MMS file?? another thing ... can u send me some compiled MMS files too thanx alot in advance | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Hi Feras, I've sent you a couple of simple MMS files via e-mail. In general, the only differences that you have with different handsets is that different handsets support different media formats. For example, some phones support AMR for recorded audio, some don't. Some phones support MIDI ring tones, some support SMAF, some support neither. Other issues relate to the display size of images, as different phones have different display characteristics. There are also size limitations, as different phones have different overall size limits for the size of MMS file that they support (ranging from 30K to 300K in today's handsets). An MMS file essentially is a multipart message containing different file content parts within the message. -bn | |||
| Feras Diab |
Hello thank u very much... but is there any differences in the term of structure of the msg and the binary encoding for it... suppose the content are out of the discussion, does that mean the binary of any mms from any handset should be workable on the other handsets. thanx again Feras | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Feras, The structure of the message itself is the same regardless of the handset. The WAP specifications that you can download from the www.openmobilealliance.org site document the format. Basically, you're looking at an MMS file of the m-retrieve-conf type. The header MMS encapsulation specification documents the MMS header format, and then the content of the message is a MIME multipart message encoded according to the WAP multipart encoding specification, which is part of the WAP WSP spec. -bn | |||
| James |
Hiya any chance of sending me one of them MMS files, I can send binary messages through an SMSC, I'm currently trying to work out how to make up the MMS messages any hints...?! Cheers James | |||
| Lipnicki Gabor |
Hi, Is there any program that I can make MMS files with??? Is somebody has a link, please send me an E-mail!!! Thanx By the way, does anyone know an open SMSC over HTTP? | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Hi, Probably the easiest way to put together a simple MMS message file is to use the MMSCOMP utility that is included with the trial version of our product here. Basically, MMSCOMP just builds the MMS headers and creates the multipart file (multipart encoded according to WAP WSP multipart encoding) from a collection of input files. Nokia also has Java libraries for building MMS files. Good luck finding an open SMSC ... SMS providers have to pay money to be able to deliver messages to an operator's customers. -bn | |||
| Feras Diab |
hello i have a question regarding the From field in the MM. is it mandatory or optional. and if it is not required how can we know the sender of the msg. i mean is there any way to get such info from the http headers or from the gateway or any thing else. since the sender address is important if we want to send the delivery report or if we want to Bill the sender. i am assuming here that the sender is a real terminal. thanx | |||
| Bryce Norwood - NowSMS Support (Bryce) |
From a pure protocol standpoint, the "From" field is optional. Some terminals have configurations where they will automatically reject messages without a "From" field. In our MMSC (built into the Now SMS/MMS Gateway), we identify the user based upon the MMSC URL that they use when submitting a message. (The phone is configured with the MMSC URL to include a user name and password.) Alternatively, if the MMSC is installed in conjunction with a WAP Gateway that has access to the MSISDN, the MMSC can retrieve the MSISDN from the WAP Gateway. We describe how this is done in our products at the following link: Now MMSC Operator Considerations. We also talk about billing considerations in our products at this link: Now SMS/MMS Accouting Callbacks. Sorry that I can't give a generic answer, just a product related answer ... but basically the things that you are asking about fall outside of the defintions of the MMS specifications, and are implementation specific. -bn | |||
| yit |
hello! I just would like to have a sample compiled mms file also. could you send me one? Thanks a lot. | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Rather than my continuing to send these files out ... try downloading NowSMS, and using the MMSCOMP utility to create a compiled MMS file. Sorry, when I get some more time, maybe I can put up some links. | |||
| Bryce Norwood - NowSMS Support |
Since I continue to receive requests via e-mail for some sample compiled MMS files, I've uploaded a few to the following URL: http://www.nowsms.com/download/mmssamples.zip Cheers! -bn | |||
| Anonymous |
This is the part of the SIMPLE.MMS from http://www.nowsms.com/download/mmssamples.zip 01 20 3A 83 C0 22 3C 33 45 30 33 30 39 39 45 2E 74 78 74 3E 00 8E 33 45 30 33 30 39 39 45 2E 74 78 74 00 Any one can help me analyze above Hex.thanx! | |||
| Bryce Norwood - NowSMS Support |
You have passed the MMS header of the message, and moved into the content, which is encoded using application/vnd.wap.multipart.* encoding as documented in Section 8.5 of the Wireless Session Protocol (WSP) specification published by the Open Mobile Alliance. | |||
