| Can't send Nokia Java library generated MMS file |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 14, 2004 ⬆ |
◄ ► |
| Author | Message | |||||
| Derek Liu Unregistered guest |
Hi, I am able to send mmscomp generated MMS file through the web menu interface. I also tried to use Nokia Java Library 1.1's sample to generate one MMS file. The MMS file was generated ok and can be previewed from Nokia phone simulator. However, when i tried to send it through the web menu interface, NowSmS can't send it. From the SMSDEBUG.LOG (attached and see the last transaction), it seems NowSMS is hanging on process the file. I also attached the MMS file that generated from Nokia Java Library. I am pretty new to this field and can't figure out what's the problem. Please help. Thanks Derek
| |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2316 Registered: 10-2002 |
Hi Derek, Are you able to send other MMS message content ... for example specifying a JPG attachment on the web page instead of a pre-compiled MMS? I downloaded your "test.mms" file, and I believe that the problem is that it has no recipients specified in it, and I believe that is the problem. I know it is strange that you are posting the message via the "Send MMS Message" form, and the form allows you to specify recipients ... so you're probably asking, why do I need to specify them in the pre-compiled MMS file? Well, the ability to send a pre-compiled MMS file through that page is a "back door". When one of the files is a ".mms" file, it is processed directly and the other input on the form is ignored. When the files are regular content files, NowSMS builds a ".mms" file that includes all of the information referenced in the form and sends that out. If you really want to work with pre-compiled MMS files, but send them out to a dynamically generated list of recipients each time, you could submit through the EAIF interface. That interface is HTTP POST based and it accepts a pre-compiled MMS, along with headers that can override the recipient list in the precompiled message. Unfortunately, we don't include much detail on EAIF on our web site, just the information at http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_c ontent/Submitting_MMS_Messages_EAIF.htm. -bn | |||||
| Derek Liu Unregistered guest |
Yes, sending a gif file works fine. Also, i did further analysis by using Nokia's MMS tool. by comparing the .mms file generated by mmscomp with the one generated by Nokia Java Library, i found a few differences. I then modified the .mms file through the Nokia tool to make the .mms file more like mmscomp generated and then saved the file. I then send the newly saved .mms file through web menu interface. The send part went through and the phone got notification. However, the phone reported a corrupted mms received and can't render the content. So, it's clear the .mms generated from Java tool has some problem. I remeber someone said the tools from different vendor doesn't work on other vendor's phone. Maybe this is the case. For now, I called mmscomp in my java program and that worked around this problem. However, it seems more natural to use the Java Library. Could you share any successful story of using Nokia Java Library in NowSMS environment? Regards, Derek | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2371 Registered: 10-2002 |
Derek, The biggest problem that we have seen with MMS files created by the Nokia Java libraries is that they are in the m-send-req format, which is the format for submitting to an MMSC. MMSCOMP defaults to m-retrieve-conf format, which is the format that a phone expects to see when it retrieves the message from the MMSC. Because of this issue, NowSMS automatically detects the appropriate format, and it switches the format if necessary. There is also an issue that some headers are mandatory in m-retrieve-conf format, but optional in m-send-req ... so NowSMS has to manipulate the header of the precompiled MMS to insert headers if necessary. Since you posted your "test.mms" file here, I decided to give it a try. And I also encountered a problem trying to send it through the "Send MMS Message" form. This header manipulation that I mention here has a bug that can sometimes cause problems when NowSMS processes a pre-compiled MMS message that already includes a recipient list, and tries to replace that recipient list with the recipient(s) specified in the request. I'm currently testing a fix to that problem. It doesn't look like a major problem. I can send it to you in a day or two if you like. -bn | |||||
| Yoram Givon New member Username: Yoram_gi Post Number: 12 Registered: 11-2003 |
Dear friends, I have spent many hours with the Nokia Java MMS API and I have discovered that in most cases to solve the problem you are presenting there are two things that need to be done: 1) as you mentioned bryce, change the message type to m-retrive-conf = 84 in byte presentation 2)check that the date format is correct. you will be supprised how many device will just not accept the MMS if the date format is not present or nor correct, especialy Sony Ericsson devices. I have ported the Nokia Java API to C# with the needed changes and tested it with Now sms, so if you are interested in it just pop me an Email. | |||||
SMSDEBUG.log
