MMS Tech Problem with J2ME JSR205 in Nokia S40 platform

MMS Tech Problem with J2ME JSR205 in Nokia S40 platform SearchSearch
Author Message
victor.yu
New member
Username: Victoryu

Post Number: 6
Registered: 11-2009
Posted on Thursday, December 03, 2009 - 07:12 am:   

We test Application id is SonyEricsson K810i and Nokia S60 platform ok.
But we test in Nokia S40 platform , it's still receive by default Application. Not receive by our J2ME program.

But we test in Nokia S60 platform, it is ok.

But S40 can receive MMS that sended by our J2ME sender program , the J2ME program run in any Java platform phone.

Can youn help us to fix this issue.

We test fault in Nokia 2720a and Nokia 7210 Supernova Series 40 5th Ed FP1.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1487
Registered: 08-2008
Posted on Thursday, December 03, 2009 - 03:28 pm:   

Hi Victor,

Interesting.

I don't have access to any Nokia S40 phones that support JSR-205.

Do you have a GSM modem connected to your NowSMS server that can receive MMS messages? I would like to see a message generated by your J2ME sender program received by the modem in NowSMS to see what is encoded differently. (MMSWAPDEBUG.LOG would show us the raw received message data.)

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1488
Registered: 08-2008
Posted on Thursday, December 03, 2009 - 03:37 pm:   

A follow-up thought ...

I've been reviewing the relevant specifications, and I might have noticed something.

When sending the MMS message via NowSMS, try putting an extra ":" at the start of the application id.

--
Des
NowSMS Support
victor.yu
New member
Username: Victoryu

Post Number: 7
Registered: 11-2009
Posted on Monday, December 07, 2009 - 03:28 am:   

I test extra ":" , it is fault.
We can't used NowSMS to receive MMS.
Can you try to receive MMS from feature phone.
That http://support.nowsms.com/discus/messages/1/41956.html
has a jar file to send MMS from feature phone.
victor.yu
New member
Username: Victoryu

Post Number: 8
Registered: 11-2009
Posted on Monday, December 07, 2009 - 03:37 am:   

We make MMS file to send MMS it's ok to send.
But it still have some issues in feature phone.
Nokia S40 Feature phone receives MMS (Sended by NowSMS) will pop a message "U have a data". But J2ME send MMS to Nokia Phone. it don't show any information. That is we need. I don't know how is different MMS header with J2ME sending between NowSMS sending.

text/plainour header for hdr
a.hdr (0.6 k)
application/octet-streamour hrader for smil
b.smil (0.3 k)
application/octet-streamour mms , it can receive by J2ME
a.MMS (28.6 k)
victor.yu
New member
Username: Victoryu

Post Number: 9
Registered: 11-2009
Posted on Monday, December 07, 2009 - 08:53 am:   

can we send MMS format that choice wap used by Service Indication (SI) or Service Load (SL)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1505
Registered: 08-2008
Posted on Monday, December 07, 2009 - 09:50 pm:   

I'm sorry, I do not understand.

Let me explain where I need clarification.


quote:

I test extra ":" , it is fault.




This means what? Extra ":" works or does not work?

I assume "does not work".


quote:

We make MMS file to send MMS it's ok to send.




How do you send "a.mms" and it works?

a.) You send it using J2ME from a phone.

b.) You send it using NowSMS?

I assume "a".

If so, does it also work if you send it using "b". (Put "mms" file in as "Content File" in "Send MMS Message" web page.)

It looks like "a.mms" was built with MMSCOMP, so it should have the same format as "Send MMS Message" from NowSMS web page.

The only thing that might be different when sending "a.mms" with NowSMS is this:

"a.mms" contains MMS 1.3 application-id headers. When you send to an application id with NowSMS, NowSMS builds both MMS 1.3 application-id headers and JSR-205 application-id headers. (JSR-205 application-id headers go into the "Content-Type" field. MMS 1.3 application-id headers are separate headers in the MMS message header.)

When your J2ME application sends "a.mms", it sends it as is.

When NowSMS sends "a.mms", it may downgrade the MMS 1.3 headers depending on the MMS version number configured for the "MMSC Routing" definition. Check the "MMSC Routing" definition in NowSMS, and try setting the "MMS Version" to "1.3" to see if this resolves the problem.


quote:

can we send MMS format that choice wap used by Service Indication (SI) or Service Load (SL)




No.

You can send it as an MMS Notification, which is similar. The ".mms" content goes on a web server, and you send an "MMS Notification" that includes the URL for the full MMS.

HOWEVER ... many mobile operators block this type of external MMSC delivery, so it may not work in your environment.

--
Des
NowSMS Support
victor.yu
New member
Username: Victoryu

Post Number: 10
Registered: 11-2009
Posted on Tuesday, December 08, 2009 - 08:33 am:   

Hi
put push wrong a.mms files. Now i put the correct mms files. u can get in web.
we used nowSMS to make a.mms files by MMSCOMP.
application/octet-streama.mms can send to S40 j2ME
a.MMS (28.6 k)



we try extra ":" it can't work.
text/plainheader
a.hdr (0.6 k)


We use NOWSMS web interface send MMS files.
NowSMS UI


But it has one issue by our make mms file.
We hope the feature phone receive the mms file and auto-download it.
But the feature phone will pop up message to user "you have a new data" , user needs to enry "ok" key to download it.

But we send the same file a.jpg (not mms file) by J2ME program in feature phone.
It mean feature send a.jpg to feature phone by J2ME(sender and receiver are in J2ME environment.). The feature pphone receive mms a.jpg file and auto-dwonload it. The feature phone don't pop up any information.

We think, it WAP protocol issue. or maybe it's mms format issue. some format headers are different by J2ME creating it.

Thank your help.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1518
Registered: 08-2008
Posted on Tuesday, December 08, 2009 - 08:59 pm:   

Hi Victor,

The "a.mms" that did not work had an extra space at the end of the application-id. MMSCOMP should probably remove trailing spaces when it builds the MMS file, but it does not.

The "a.mms" that works looks of the same format as when NowSMS sends from the web interface. NowSMS takes all of the files that you specify in the web interface, automatically generates an MMS header and calls MMSCOMP to build the MMS message.

If you do not include a SMIL file in the web interface, NowSMS builds a simple one. I do not think this SMIL file would make a difference. (Although building an MMS without a SMIL file might be what is different about your auto-download .jpg. Maybe the feature phone only pops up a message if a SMIL file is present in the MMS message. You could try using MMSCOMP to build an MMS message without a SMIL file to see if this is the secret. If it is the secret, there is a parameter to stop NowSMS from generating one automatically. Add EMailAutoSmil=No under the [MMSC] header of MMSC.INI.)

When you send via NowSMS with separate content files, do you also attach a SMIL file? Can you try attaching your own SMIL file?

--
Des
NowSMS Support
victor.yu
New member
Username: Victoryu

Post Number: 11
Registered: 11-2009
Posted on Wednesday, December 09, 2009 - 01:27 am:   

application/octet-streamsmil file
b.smil (0.3 k)

This is our smil file.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1524
Registered: 08-2008
Posted on Wednesday, December 09, 2009 - 04:31 pm:   

If you include both b.smil and video.jpg in the NowSMS "Send MMS Message" form, does this work?

The resulting MMS should be identical to a2.mms, except for timestamps, and that the Content-ID for the SMIL will be <b.smil> instead of <presentation-part>.

--
Des
NowSMS Support