| Now SMS 2009_attachment problem |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through July 28, 2010 ⬆ |
◄ ► |
| Author | Message | ||||
| Annie Hong New member Username: Linksoft Post Number: 1 Registered: 04-2010 |
Dear Keith, The customer from HTC Corporation had upgraded the software Now SMS 2009 but he encountered some problem about the MMS sending and its attached file. When he sent a MMS message with an .pdf or .txt attachment to the device, the mobile only receive the message but can’t download the attachment well. However if the attachment is others format like .jpg or ,mp4, it can be sent and received well. Do you have solution for this problem? Thank you. Best Regards, Annie Hong Linksoft Inc. www.linksoft.com.tw Tel: 886-2-2221-2155 Fax: 886-2-2221-9008 12F.-9, No.1180, Jhongjheng Rd.Jhonghe City, Taipei County 23586, Taiwan | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2043 Registered: 08-2008 |
Hi Annie, Are you saying that this worked before the upgrade? I will assume that it did not work before the upgrade, or that it was never tried before the upgrade. If this is incorrect, please clarify. Here is an explanation of two issues related to content types in MMS messages. One, or both, of these issues is likely to be causing problems. 1.) File extension to MIME Content-Type mapping: When you send MMS messages using the NowSMS web form, NowSMS uses the file extension to determine the content type. For example, for a file named "manual.pdf", "pdf" is the file extension. MMS clients do not look at the file extension to determine content type. Instead, they look at the MIME content-type header in the MMS message. NowSMS uses the file extension to decide what MIME content-type header to include in the MMS message. First, NowSMS looks in a configuration file named MMSCTYPE.INI (Program Files\NowSMS directory). This file contains a list of common file extension to content-type mappings. Next, NowSMS queries the Windows registry for file extension to content-type mappings, which can vary depending on what applications are installed on the PC running NowSMS. Finally, if no match is found, NowSMS uses a MIME content-type of application/extension (e.g., application/pdf). In the context of the problem that you are describing, it is very important that the text file have a ".txt" extension, and the PDF file have a ".pdf" extension. .txt=text/plain is defined in MMSCTYPE.INI. .pdf is not defined in MMSCTYPE.INI, however it should be OK. The accepted MIME type for PDF files is "application/pdf", which is what NowSMS would generate if it does not find ".pdf" defined in MMSCTYPE.INI or the Windows registry. 2.) UAProf files and accepted content types: Note: This applies ONLY if NowSMS is being used as a direct delivery MMSC. (Configurations where the MMS client connects back to the NowSMS MMSC to retrieve MMS messages.) Every MMS client is supposed to have a UAProf file associated with (UAProf = User Agent Profile). When the MMS client connects to the MMSC to retrieve a message, it includes a reference to its UAProf in the "X-WAP-Profile:" header. NowSMS downloads this profile to see what content types the MMS client will accept. If a content type is not listed as an acceptable type in the UAProf, it is not delivered to the handset. Note that there are two sections of this file, one has content types supported by the browser, and the other has content types supported by the MMS client <MmsCcppAccept>. We did encounter a mobile phone last year, which neglected to list "text/plain" as a supported content type. NowSMS 2009.03.31 and later ignore this, and send "text/plain" even if the UAProf does not list it as supported. Also, note, since HTC is a handset developer, there may be another issue. NowSMS caches UAProf files and does not redownload them. So if there was a content type missing from the UAProf file, and it is now fixed, it is necessary to delete the cached copy from the NowSMS UAProf subdirectory in order to force NowSMS to redownload the new version. -- Des NowSMS Support | ||||
| Annie Hong New member Username: Linksoft Post Number: 2 Registered: 04-2010 |
Dear Des, I passed your comment to the end user and below is his further questions... Thanks for your provide information. According to yours replied that I have tried to check these two MIME-type and UA-Prof files about this issue. Unfortunately, the problem is still existed. That I thought there is some relative information is needed for your reference. That is, now we are building two Now-SMS server to use, and currently Now-SMS server is ver.5.51b that occurred this problem, otherwise it is not upgrade and another Now-SMS server is order for upgrade by you in recent. By testing on several of methods, that I found the MMS client factors was exclude because of Now-SMS (new version) web can receive MMS files well, but it will lost the MMS attach file like .txt via Now-SMS (ver.5.51b). But compared to these two Now-SMS server, that I found there was the different on it. That is, as the below image, after sending MMS Message via web, its Message ID format didn’t the same, and even v.5.51b has repeated Message ID. I were confused about if this is related our issue. Please help to check this problem and the previous existed issue. Very thanks for your help. Best Regard, Annie | ||||
| Annie Hong New member Username: Linksoft Post Number: 3 Registered: 04-2010 |
Dear Des, I passed your comment to the end user and below is his further questions... Thanks for your provide information. According to yours replied that I have tried to check these two MIME-type and UA-Prof files about this issue. Unfortunately, the problem is still existed. That I thought there is some relative information is needed for your reference. That is, now we are building two Now-SMS server to use, and currently Now-SMS server is ver.5.51b that occurred this problem, otherwise it is not upgrade and another Now-SMS server is order for upgrade by you in recent. By testing on several of methods, that I found the MMS client factors was exclude because of Now-SMS (new version) web can receive MMS files well, but it will lost the MMS attach file like .txt via Now-SMS (ver.5.51b). But compared to these two Now-SMS server, that I found there was the different on it. That is, as the below image, after sending MMS Message via web, its Message ID format didn’t the same, and even v.5.51b has repeated Message ID. I were confused about if this is related our issue. Please help to check this problem and the previous existed issue. Very thanks for your help. Best Regard, Annie | ||||
| Annie Hong New member Username: Linksoft Post Number: 4 Registered: 04-2010 |
Dear Des, I passed your comment to the end user and below is his further questions... Thanks for your provide information. According to yours replied that I have tried to check these two MIME-type and UA-Prof files about this issue. Unfortunately, the problem is still existed. That I thought there is some relative information is needed for your reference. That is, now we are building two Now-SMS server to use, and currently Now-SMS server is ver.5.51b that occurred this problem, otherwise it is not upgrade and another Now-SMS server is order for upgrade by you in recent. By testing on several of methods, that I found the MMS client factors was exclude because of Now-SMS (new version) web can receive MMS files well, but it will lost the MMS attach file like .txt via Now-SMS (ver.5.51b). But compared to these two Now-SMS server, that I found there was the different on it. That is, as the below image, after sending MMS Message via web, its Message ID format didn’t the same, and even v.5.51b has repeated Message ID. I were confused about if this is related our issue. Please help to check this problem and the previous existed issue. Very thanks for your help. Best Regard, Annie | ||||
| Annie Hong New member Username: Linksoft Post Number: 5 Registered: 04-2010 |
Sorry for the triple post because it showed the website is unavailable after submitting the message. | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2060 Registered: 08-2008 |
Hi Annie, We do seem to be having some web site configuration problems which have hopefully now been corrected. I would need to see the actual message and transaction details in order to answer your question. My advice would be to enable the SMSDEBUG.LOG and MMSCDEBUG.LOG. (Checkbox option on the "Serial #" page.) Then, repeat the test. Reply back with the SMSDEBUG.LOG and MMSCDEBUG.LOG files in a ZIP or RAR file. -- Des NowSMS Support | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2061 Registered: 08-2008 |
P.S. - Please use the newer version of NowSMS for generating the debug logs. The difference in the HTTP "MessageID" response doesn't mean much to the user. But it is helpful for our debugging, where it means this ... when "MMSMessageID=" is present, the message has been posted via the MMSC. When only "MessageID=" is present, the web interface has used a "back door" to generate the MMS message content on the MMSC. | ||||
| Annie Hong New member Username: Linksoft Post Number: 6 Registered: 04-2010 |
Dear Des, Thanks for your reply. Per your request, please check the attachment. The version of NowSMS used to generate the debug lots is ver.5.51b. Thank you. Best Regard, Annie | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2067 Registered: 08-2008 |
Hi Annie, It is the SMSDEBUG.LOG and MMSCDEBUG.LOG that I need to see. These logs are only generated if they are explicitly enabled. There is a checkbox option on the "Serial #" page of the configuration dialog. I am not certain, but this checkbox option might not be present in v5.51b, so please generate the debug logs with the newer version. -- Des NowSMS Support | ||||
NowSMS version difference
