MM7 to Nokia Java Libs 1.3 Problem

MM7 to Nokia Java Libs 1.3 Problem SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through July 14, 2004 » MM7 to Nokia Java Libs 1.3 Problem « Previous || Next »
Author Message
Wolfgang Röckelein
Unregistered guest
Posted on Wednesday, May 12, 2004 - 07:20 pm:   

Hi,

when I send a MMS from NowSMS 5.50 b20040503 to the Nokia MMS Java Libraries v1.3 via MM7, I get the following error at the Nokia MMS Java Library:

[ERROR] com.nokia.mobile.services.driver.common.wsi.axis.AxisHTTPService: Failed to execute SOAP request

org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.

What is wrong? What can I do (besides using EAIF instead of MM7)?

Also: How can I remove the problem causing MMS message from NowSMS?

Thank you very much in advance,
Wolfgang
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2597
Registered: 10-2002
Posted on Friday, May 14, 2004 - 02:13 am:   

Hi Wolfgang,

And they say that some of our error messages are not intuitive.

It would be nice if the error message gave an indication of what child element it considered to be unexpected.

Can you give me a crash course on setting up the Nokia Java Library? What exactly are you running to receive the messages?

As I look at the Java libraries, I don't really see an MM7 server emulator. So I suspect you are running a client software that is expecting to receive messages from an MMSC.

It would expect to see MM7_deliver.REQ messages, and in a default configuration, NowSMS is sending out MM7_submit.REQ messages.

For situations where the default behaviour is not appropriate, we have configuration settings that can force messages being routed via MM7 to use either submitReq or deliverReq format.

You will find a configuration file named VASPOUT/accountname/VASP.INI. In this file, under the [VASP] section header, you can specify one of the following parameters:

mm7DeliverReq=Yes
mm7SubmitReq=Yes

Including either of these settings will force all messages routed out via that connection to be converted to deliverReq or submitReq format.

In your case, add mm7DeliverReq=Yes ... and see if that doesn't make a difference.

If it doesn't, then let me know what code you are running from the libraries to receive the messages, so that I can try running it on my end.

-bn
Wolfgang Röckelein
Unregistered guest
Posted on Friday, May 21, 2004 - 07:37 pm:   

OK, done that. First problem solved.
New problem: I don't receive a sender address (but I receive a to address). The ini-file in the VASPQ dir has the sender address. When I activate "Allow Sender Address Override" address I get an error from the Nokia MM7 Library: no supported address type in MM7 AddressType object.
Wolfgang Röckelein
Unregistered guest
Posted on Tuesday, June 01, 2004 - 02:08 pm:   

OK, I am bit wiser now: NowSMS sends:

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header>
<mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2" env:mustUnderstand="1">
20040601/16/2ACAEFE8@pckl735.uni-regensburg.de
</mm7:TransactionID>
</env:Header>
<env:Body>
<DeliverReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2">
<MM7Version>5.3.0</MM7Version>
<Sender>
<Number>+491751804646</Number> </Sender>
<Sender>+491751804646/TYPE=PLMN</Sender>
<Recipients>
<To>
<Number>234</Number>
</To>
</Recipients>
<Subject>Multimedia Message</Subject>
<Content href="cid:mms_cid" />
</DeliverReq>
</env:Body>
</env:Envelope>


I think the problem is the second <Sender> element, which has no subentry of RFC2822Address, Number or Shortcode and thus leads to no sender number. AS I read the scheme, <Sender> should occur only once...

Wolfgang
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2764
Registered: 10-2002
Posted on Tuesday, June 08, 2004 - 08:32 pm:   

Hi Wolfgang,

Apologies for the delay in responding to your message.

We do have a patch that corrects this behaviour, it just hasn't been uploaded yet. (I'll have to get on that, as this particular problem was corrected over a month ago.)

I will send you an e-mail with the patch.

-bn
Wolfgang Röckelein
Unregistered guest
Posted on Wednesday, June 09, 2004 - 10:08 am:   

Hi Bryce,

thanks for the patch. I applied it, my application now succesfully receives MMS via MM7. However when submitting a MMS via MM7 (still with the Nokia Libraries), I receive
"transaction id in response does not match the transaction id sent in the request"

What is now wrong?

Wolfgang
Wolfgang Röckelein
Unregistered guest
Posted on Wednesday, June 09, 2004 - 10:54 am:   

Hi,

problem solved, there was an error in the the Nokia Library:
in void com.nokia.mobile.services.driver.mms.mm7.TransactionIDHandler.invoke(MessageCont ext msgContext) throws AxisFault

in the line
String transactionID = getTransactionID(msgContext, !isSOAPFault(message)).trim();

the trim was missing...

Everything works now, thanks.

Wolfgang
Nosapo Nijui
New member
Username: Nosaponijui

Post Number: 3
Registered: 06-2004
Posted on Saturday, July 10, 2004 - 11:49 pm:   

I have the same problem , can emailme the patch?

Thanks!
Wolfgang Röckelein
Unregistered guest
Posted on Tuesday, July 13, 2004 - 08:44 pm:   

You could try the Nokia server service SDK 1.4 lib first, which just came out.

Login Login / Register Logout Logout Search Last 30 Days Topics Topics