| T630 and me do not understand MMS file |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 14, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| patrick lee New member Username: Patricklee Post Number: 1 Registered: 06-2004 |
i am sorry for this stupid question, but I would really like to know more about the mms file. - I understand how the mms file is created by the MMSCOMP.EXE, I believe I have done it without problem. - I understand what should be inside the file: header, image, SMIL.... - BUT I don't know how is the mms file sent to the operator's MMSC. what is the real operation inside ? I assume when i send mms using the web interface: 1. NowSMS will accept and pack my attachments (image, amr, text) into a single .mms file 2. NowSMS forwards the .mms file to the operator MMSC which have been configured and chosen as default route. 3. Mobile handset receives a MMS notification and downloads from operator MMSC. 4. Mobile handset decomposes the .mms back to image and sound and SMIL file and displays them on screen. Am i right ? BUT I have tried these two but all failed: 1. send a pre-compiled .mms file, the mobile unable to display the content inside the mms file. 2. the handset retrieves a .mms file directly thru GPRS, but the handset (SE T630) said the "file format not supported" Why ? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2766 Registered: 10-2002 |
Patrick, Are you always sending a pre-compiled MMS file? What happens if you use NowSMS and just send the parts of the message (SMIL, image, text, etc.)? Is that working properly? I think we should troubleshoot that before we look at the pre-compiled MMS issues. Do note that if you are running a NowSMS version prior to v5.50, NowSMS had a bug that could cause problem sending some pre-compiled MMS messages via the web interface for "Send MMS Message". -bn | |||
| patrick lee New member Username: Patricklee Post Number: 3 Registered: 06-2004 |
Bryce, thanks for your kind reply. It is OK when I send mms messages with file attachments (.jpg, .mid). It just didn't work on pre-compiled mms file. I don't know understand if the mobile phone would receive the mms packet and unpack it itself and display the content. If it is the case, I thought composing the files into a .mms and injecting it to NowSMS may be a more complete and flexible way for me. But I still don't understand why my SE T630 cannot read the .mms file. Anyway, I will try the V5.5, hope I would have good news later on. And I have been using NowSMS to send MMS with MM4 connection with my mobile operator, it works perfectly both in and out (2-way), as long as I am not sending pre-composed mms file. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2795 Registered: 10-2002 |
Patrick, I think the v5.50 version will make a difference for you. There was a problem in sending some pre-compiled MMS messages through the web interface. The issue was basically that when you do this, we have to modify the recipient header of the pre-compiled MMS message before sending it on. And there were definitely situations where we were not handling this correctly. As I recall, the problem primarily occurred when the configuration was such that we were routing the message for delivery via an operator MMSC as opposed to direct delivery. Since you are using MM4, I suspect this would apply to your configuration. -bn | |||
| patrick lee New member Username: Patricklee Post Number: 5 Registered: 06-2004 |
Thanks Bryce, I tried v5.50 and it worked on precomplied mms !! But i still not quite understand the real opeartion. I have put the precompile MMS, say 123.mms, into a web server. And I try to download the 123.mms directly from mobile using WAP. My T630 said "Item not supported, cannot be downloaded". What does it mean ? Isn't the mms delivered to handset in form of a mms file ? But how come the handset does not support the .mms format ? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2820 Registered: 10-2002 |
Hi Patrick, Being able to download an MMS message directly via the WAP browser would make a lot of sense. Unfortunately, they didn't architect MMS to support that. The MMS protocol requires that the MMS client receive an MMS notification message first. Then, the MMS client will download the URL referenced in the MMS notification message, and that URL will contain the MMS message content. Most phones will not allow you to download MMS message content directly through the browser ... they require the notification first, otherwise technically it is a protocol violation. -bn | |||
| patrick lee New member Username: Patricklee Post Number: 6 Registered: 06-2004 |
Bryce, thanks very much for your explanation. I also understand the MMS notification message (which is actually a SM, I believe) contains the URL to the operator MMS gateway. And you mention "that URL will contain the MMS message content.", so what is the content ? is it a mms file or a bunch of multimedia files (e.g. jpg, gif, amr ....). If in this sense, does it mean operator MMSC will be responsible for decomposing the mms file and store in the WAP server for the handset to retrieve ? And there should be a standard for composition/decomposition of mms file. what is it ? Is it an open standard ? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2849 Registered: 10-2002 |
Patrick, The content that is delivered by the MMSC is an MMS file (MMS encapsulation format). The issue that I was getting at is that we have to decompose the binary MMS file into a different format for MM4 transmission. Then, the operator MMSC puts it back into binary MMS format for delivery. So that is what is kind of crazy. MM4 is defined in the 3GPP TS 23.140 specification. The binary MMS message file format is defined in the Open Mobile Alliance's MMS Encapsulation specification. -bn | |||
