| MMS UTF code format |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 09, 2011 ⬆ |
◄ ► |
| Author | Message | ||||
| mohammed New member Username: Mta Post Number: 5 Registered: 07-2006 |
Dear Some of our GSM operator they get error when I post MMS to them (MM7) after long trace they told us that they want to remove the " " around the UTF-8 code see the example down How we can do this " Please remove “ “ in charset Content-Type: text/xml; charset="utf-8" " Thank you Regards Mohammed | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2609 Registered: 08-2008 |
Hi Mohammed, Unfortunately there is no configuration option to do this. I have asked our engineering department to investigate this. They indicate that the Content-Type charset= parameter is valid with or without quotes. Since there is no reason that we need to include the quotes, they have indicated that they will remove the quotes in an update. This update should be ready in approximately 24 to 48 hours. -- Des NowSMS Support | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2627 Registered: 08-2008 |
Hi Mohammed, An update which changes: Content-Type: text/xml; charset="utf-8" to Content-Type: text/xml; charset=utf-8 ... is now available at http://www.nowsms.com/download/nowsms20101104.zip -- Des NowSMS Support | ||||
| mohammed New member Username: Mta Post Number: 7 Registered: 07-2006 |
dear we try it but still the oprator say to us that they reject the MMS and they say "the issue become of SAAJ version you used to send the MM7 , please contact with the development team to check that because it's clear from internet there is bug in SAAJ and that create that issue with content-type not organized" i want your advise thank you mohammed | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7934 Registered: 10-2002 |
Hi Mohammed, We do not use SAAJ, so I do not know what they are referring to. Or how the content-type header would be considered "not organized". Can you enable the MMSCDEBUG.LOG and try again. I would like to see the error that is being returned. Is it a SOAP level issue or an MM7 level issue? It could be an issue of MM7 schema versions. I'd like to see the request/response to see if it provides any clue. If you do not want to post the log details here, please email them to nowsms@nowsms.com, placing Attentiion: Bryce in the subject line. Also post a followup here to tell me to look for that email. -bn | ||||
| mohammed New member Username: Mta Post Number: 8 Registered: 07-2006 |
i sent you e-mial reagrding this thank you reagrds mohammed | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2666 Registered: 08-2008 |
Hi mohammed, This is very odd. The server is returning an MM7 error code of 3000, which is defined as meaning: "Server error - The server failed to fulfill an apparently valid request." However, there is also additional information: "Failed processing request (class com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message)" I don't see any obvious issues in reviewing the format of the response coming back from the server. I do have one idea that I'm going to ask our engineering department to add a configuration option for us to try a slight variation in message formatting. However, the chances of this idea making a difference is a longshot, and is unlikely to make a difference. I would suggest that you make sure that you are using the correct VASPID, VASID and sender address values, as authorised by your provider. It is possible that the problems you are experiencing could be caused by using incorrect values for these parameters. Also, in the MM7 options in NowSMS (in the "MMSC Routing" definition), try selecting the option "Remove White Space from MM7 XML". I notice that your provider responses do not include any white space, and we have seen situations in the past where bad software implementations were confused by the presence of white space. (White space characters are things like line breaks, which make it easier for humans like us to read debug logs.) I would also suggest asking your provider if they can provide you with a connection trace that shows an MM7 message successfully being submitted to their service. I am guessing that their software is expecting something specific that is not required by the MM7 standard ... but without seeing an example that works on their system, it is impossible to guess what this might be. -- Des NowSMS Support | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2673 Registered: 08-2008 |
Hi mohammed, Try the test version of NowSMS at http://www.nowsms.com/download/nowsmstestversion.zip and see if this makes any difference. We'd like to see an MMSCDEBUG.LOG from this version, like you e-mailed before as well. It is a longshot (low probability) that this will fix the problem. However, from what we can see of your logs, the MMSC appears to be having problems parsing the multipart MMS content. (By contrast, there is some single part content that seems to be getting parsed correctly.) So we're guessing that there may be a white space issue that is confusing the Java libraries being used by your provider. This is only a guess, but since we have no other ideas, seems to be worth trying. -- Des NowSMS Support | ||||
| mohammed New member Username: Mta Post Number: 9 Registered: 07-2006 |
dear still we face same probelm can you see the log file i send it to you in e-mail thank you | ||||
| mohammed New member Username: Mta Post Number: 10 Registered: 07-2006 |
dear i sedn you other e-mial you will see that there is 3 example for successfully MMS thank you | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2782 Registered: 08-2008 |
Is it working now? I did not receive the e-mail. Did you put Attention: Des in the subject line when sending it to nowsms@nowsms.com? This routes it to my tech support queue. -- Des NowSMS Support | ||||
| mohammed New member Username: Mta Post Number: 11 Registered: 07-2006 |
dear i sedn it agian to you but still not working i sedn you example for mms that work fine with them i want same xml in nowsms to work you told me to i give you exmaple for other mmsc that work fine so that was waht i send you thank you | ||||
| mohammed New member Username: Mta Post Number: 12 Registered: 07-2006 |
dear i did some change to make it like one of the example that i give you but still not work there littile diffrent i sedn you e-mial regard this thank you | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2785 Registered: 08-2008 |
The attachments were missing from the message that referred to working examples. Please resend that message with attachments. (I replied in e-mail about this as well.) | ||||
| mohammed New member Username: Mta Post Number: 13 Registered: 07-2006 |
i send the e-mail again thank you | ||||
| mohammed New member Username: Mta Post Number: 14 Registered: 07-2006 |
i will attached hre becuse the e-mail give me that cant reach
| ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2793 Registered: 08-2008 |
Hmm... The working examples are so similar to the non-working examples that it is difficult to determine what the problem is. My best guess is that the server does not like the <TransactionID> value generated by NowSMS. Specifically, I am wondering if the fact that we are including an @ character in the <TransactionID> is causing a problem. I wonder this because this character was actually not allowed in early versions of the MM7 schema. (This MMSC claims to be using an updated version of the schema which would support @, but maybe it does have a problem with it.) Try editing the MMSC Routing and change the MM7 schema version to REL-5-MM7-1-1 When NowSMS uses this older schema version, it will avoid the use of the @ character in a TransactionID value. Unfortunately, using this older schema version changes the format of the <SenderAddress> field when submitting messages, which may not be compatible with that MMSC. But I am curious to see if the error changes when you try the different schema. We can try a custom build that avoids the @ symbol in all schema versions, but I might not be able to get our engineering team to do this until next week. -- Des NowSMS Support | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2812 Registered: 08-2008 |
Hi Mohammed, Were you able to test the schema version change that I mentioned above? I have now posted an updated version of NowSMS that does not use the "@" character in the <TransactionID> field. Studying the examples and differences between those transactions and NowSMS, and judging from the fact that responses from the server include ERROR in the <TransactionID> field, I am guessing that the server in question does not like the "@" character in this value. (It is perfectly legal to be present in the value according to the XML schemas.) An update that changes the <TransactionID> format can be downloaded at http://www.nowsms.com/download/nowsmstestversion.zip Please let me know the results. -- Des NowSMS Support | ||||
| mohammed New member Username: Mta Post Number: 15 Registered: 07-2006 |
hi i sedn it in e-mail and it give ame error i will try this new update that you sedn it now for me and i will back to you thank you mohammed | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2813 Registered: 08-2008 |
Hi Mohammed, I've sent you another e-mail with some test cases to try via TELNET. Let's see if we can figure out what the insignificant difference is that your service provider does not like. -- Des NowSMS Support | ||||
mms example
