| Problem using NowSMS with Nokia MMSC 3.1 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | |||||
| nokiola New member Username: Nokiola Post Number: 1 Registered: 07-2006 |
Hello, I am trying to send via web interface a MMS message to our Nokia MMSC v. 3.1 using NowSMS as router. Although I am perfectly capable to submit from web interface the message, NowSMS cannot send MMS message to MMSC due to "Message format corrupt" error received from MMSC. I've attached a log of the "conversation" between NowSMS and the MMSC if someone can help. Regards, Robert
| |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6202 Registered: 10-2002 |
Hi Robert, I'm sorry, but I have no idea how to interpret the log file that you have attached. I guess it's coming from the Nokia MMSC? And it doesn't seem to show any useful information ... in fact, I can't even determine which protocol you are using or attempting to use. If you instead send an MMSCDEBUG.LOG file from NowSMS (and also the SMSDEBUG.LOG since you are submitting the MMS message from the web interface of NowSMS) ... then I can see more details about the transaction, and get a better idea of the overall transaction. To enable the MMSCDEBUG.LOG and SMSDEBUG.LOG, use the checkboxes on the "Serial #" page of the configuration dialog. Repeat your sending attempt, and then post those log files in reply here. -bn | |||||
| nokiola New member Username: Nokiola Post Number: 2 Registered: 07-2006 |
I am sorry for the log uploaded... it was a mistake. I've attached now the correct debug files from NowSMS. Regards, Robert
| |||||
| nokiola New member Username: Nokiola Post Number: 3 Registered: 07-2006 |
Anyone can help here, pls? | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6247 Registered: 10-2002 |
Hi Robert, Apologies as my alternates were not able to keep up with the discussion board while I was on holiday last week. This remains a mystery to me. They are claiming that the message format is corrupt, but giving no indication as to what part of the message is believed to be corrupt. My first guess would be to try setting the configuration option "Remove White Space from MM7 XML". I've seen some past Nokia SDKs that got confused by white space (blank lines) within parts of the XML. So let's see if that makes any difference. Beyond that, try the updated NowSMS 2006 at http://www.nowsms.com/download/patch2006.zip. As I review things with a fine tooth comb, I see that the "Priority" element is not in the proper sequence, and it is possible that their XML validation has an issue with this. (This patch fixes the sequence of the "Priority" element.) Another potential problem. If the MMSC is using an older MM7 schema, then the "_" character is not valid in a VASPID or VASID value. And the presence of this character would cause an XML validation failure if the MMSC is validating against REL5-1-0 or REL5-1-1. Our default behaviour is to use the REL5-1-2 schema, which does support "_" in these values. But if the MMSC is validating against an earlier schema, this could be a problem. If possible, get your account renamed to remove the "_" and rule this out as an issue. Aside from that, it is possible that the MMSC requires an additional authentication parameter that you are not supplying. You're supplying a VASPID and VASID value, but some MMSCs also want to see a ServiceCode value. It is also possible that the MMSC is expecting a different version of the MM7 schema. NowSMS has support for a variety of different schema versions, but guessing which one to use is usually not very productive. Are there any examples available from your service provider which illustrate what they are expecting? -bn | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6251 Registered: 10-2002 |
An unrelated question asking about NowSMS and the Openwave API was moved to a new thread: http://support.nowsms.com/discus/messages/485/16679.html | |||||
MMSC Log
MMSC Log
