OpenWave MMS library

OpenWave MMS library SearchSearch
Author Message
David Chkhartishvili
New member
Username: Datoch

Post Number: 16
Registered: 06-2004
Posted on Friday, October 29, 2004 - 10:26 am:   

Hi,

I've tried Openwave's MMS library to test MM7 functionality. Everything went well except smil content parsing (from mobile to openwave).
I've posted problem on OpenWave's message board. They replyed that it *MIGHT* be bug in NowSMS.
Here is debug log, please confirm/decline openwave's words:
SOAPAction: ""
Content-Length: 1964
Content-Type: multipart/related; boundary="---mime-boundary-90916EFC.36BBAA7D---"; type="text/xml"; start="<mm7_msg>"
Connection: close

-----mime-boundary-90916EFC.36BBAA7D---
Content-Type: text/xml; charset=utf-8
Content-ID: <mm7_msg>

<?xml version="1.0" ?>
<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">
20041019182733-8CAECE3B@mms.magtigsm.ge </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>xxxxxxxxxxx</Number>
</Sender>
<Recipients>
<To>
<Number>1111</Number>
</To>
</Recipients>
<Priority>Normal</Priority>
<Subject>Test</Subject>
<Content href="cid:mms_cid"/>
</DeliverReq>
</env:Body>
</env:Envelope>

-----mime-boundary-90916EFC.36BBAA7D---
Content-Type: multipart/related; type="application/smil"; start="<mmmm>"; boundary="---mime-boundary-118D10BE.EEB131BF---"
Content-ID: <mms_cid>

-----mime-boundary-118D10BE.EEB131BF---
Content-Type: application/smil; charset=utf-8; name="mms.smil"
Content-ID: <mmmm>
Content-Transfer-Encoding: quoted-printable

<smil><head><layout><root-layout width=3D"240" height=3D"160"/><region id=3D"REGION_1=
" left=3D"0%" top=3D"0%" height=3D"67%" width=3D"100%" fit=3D"meet"/><region id=3D"REGION_2=
" left=3D"0%" top=3D"67%" height=3D"33%" width=3D"100%" fit=3D"meet"/></layout></head><bo=
dy><par dur=3D"5s"><text src=3D"smiltextpartfilename0.txt" type=3D"text/plain" region=
=3D"REGION_1" /></par></body></smil>
-----mime-boundary-118D10BE.EEB131BF---
Content-Type: text/plain; charset=utf-8; name="smiltextpartfilename0.txt"
Content-location: smiltextpartfilename0.txt
Content-ID: <smiltextpartfilename0.txt>

Test
-----mime-boundary-118D10BE.EEB131BF-----

-----mime-boundary-90916EFC.36BBAA7D-----

21623 [Thread-0] DEBUG com.openwave.mms.mm7.Listener - [End Incoming Request From Relay]
TransactionID:
20041019182733-8CAECE3B@mms.magtigsm.ge
Linked ID: null
Sender: xxxxxxxxxxx
To: 1111
Subject: Test

====================================
ContentException: smil-parsing-failed
====================================

22329 [Thread-0] DEBUG com.openwave.mms.mm7.Listener - [Begin Outgoing Response To Relay]

22329 [Thread-0] DEBUG com.openwave.mms.mm7.Listener - HTTP/1.0 200 OK

22329 [Thread-0] DEBUG com.openwave.mms.mm7.Listener - Content-Type: text/xml

22332 [Thread-0] DEBUG com.openwave.mms.mm7.Response - Content-length: 591


22332 [Thread-0] DEBUG com.openwave.mms.mm7.Response - <?xml version='1.0' ?><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">
20041019182733-8CAECE3B@mms.magtigsm.ge </mm7:TransactionID></env:Header><env:Body><DeliverRsp xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2"><MM7Version>5.3.0</MM7Version><Status><StatusText>got it!</StatusText><StatusCode>1000</StatusCode></Status><ServiceCode>sample-servic e-code</ServiceCode></DeliverRsp></env:Body></env:Envelope>
22332 [Thread-0] DEBUG com.openwave.mms.mm7.Listener - [End Outgoing Response To Relay]

Thank you in advance.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3673
Registered: 10-2002
Posted on Friday, October 29, 2004 - 05:18 pm:   

It might be a bug in Openwave's library too.

If I understand you correctly, you got the text, but you didn't get the SMIL?

What happens if you try objects with more parts ... do you get all of the parts properly, excepting the SMIL?

Maybe the Openwave library doesn't like "quoted-printable" encoding for the SMIL part.

We only use that when there is something about the SMIL that would cause it to break e-mail transcoding rules. There is not a strict requirement that we follow the same rules for MM7, we just opted to use the same MIME encoding engine, so the e-mail rules are applying here.

Anyway ... some phones don't put any line breaks in their SMIL. When that happens, the e-mail transcoding rules require us to use quoted printable encoding.

As it is unlikely that Openwave will fix any bugs in their libraries ... if this is indeed the problem ... we can explore a configuration option to disable the use of quoted-printable encoding on the SMIL.

But first, I'd like to confirm that is the problem.

Can you try some different handsets (preferably from different manufacturers)? Only a few of them don't include line breaks in their auto generated SMIL, so you might find one of your handsets will send the message in a way that it does not force quoted printable encoding.

-bn
David Chkhartishvili
New member
Username: Datoch

Post Number: 17
Registered: 06-2004
Posted on Tuesday, November 02, 2004 - 09:27 am:   

Hi Bryce,

I've tested couple handsets against openwave mms library, only phone I found fully working was SonyEricsson T630 (maybe other SE phones will work).
With Motorola I got "smil-parsing-failed".
With Nokia, I didn't get any error but, smil wasn't saved to file.
So, with 3 different phones manufacturers I got 3 different result, that forces me to forget about that library.

My question is:

Do you know any MMS library which works correctly (fully) with NowSMS?

Thanks.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3684
Registered: 10-2002
Posted on Tuesday, November 02, 2004 - 10:23 pm:   

David,

I don't have any library recommendations (although I have seen others using the Nokia libraries). So let's go back to testing my theory.

When you tried the three different phones, look at the MIME header for the SMIL part in the MMSCDEBUG.LOG.

Did the one that worked have no "Content-Transfer-Encoding" parameter, while the others used "quoted-printable"?

If so, we're willing to add a setting to disable the use of "quoted-printable" encoding against SMIL in the MM7 interface. As I said, we're only doing it for consistency with our MM4 & SMTP interfaces where it is required.

I'd just like to get a confirmation that this is indeed the issue before we put the development effort toward this.

-bn
David Chkhartishvili
New member
Username: Datoch

Post Number: 18
Registered: 06-2004
Posted on Wednesday, November 03, 2004 - 07:44 am:   

Bryce,

In addition to 3 handsets tested earlier, I've added Siemens ST60.

Here are results:

Siemens ST60: works fine, text and image saved to file. Uses Content-Transfer-Encoding: quoted-printable.

Motorola V4000p: smil parsing fails. Also quoted-printable.

SonyEricsson T630: works fine, text and image saved to file. Uses Content-Transfer-Encoding: quoted-printable.

Nokia 6610: seems like, that phone doesn't know what is smil. It sends pictures as attachment. Images and text were not saved to file.


Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3687
Registered: 10-2002
Posted on Wednesday, November 03, 2004 - 06:33 pm:   

David,

Ok ... so it sounds like quoted-printable encoding is not the issue.

Can you post the excerpt of the log that contains the SMIL part for each of these devices?

Also, I'd like to see the "Content-type:" header for the "multipart/related" or "multipart/mixed" wrapper on the content object. (e.g., the one that in the above example is Content-Type: multipart/related; type="application/smil"; start="<mmmm>"; boundary="---mime-boundary-118D10BE.EEB131BF---") Basically, I want to confirm that the start= parameter points to the content-id of the SMIL object,and that the type="application/smil" header is present.

Let's compare these two things between the ones that work, and the ones that do not, and hopefully we can then identify what the problem is. Since it doesn't look like my guess of "quoted-printable" encoding being the issue ... hopefully this will give us another clue, like perhaps there is something about the actual SMIL that is the problem ... or there is an issue with the Content-type header and the "start=" pointer to the SMIL object.

-bn
David Chkhartishvili
New member
Username: Datoch

Post Number: 19
Registered: 06-2004
Posted on Friday, November 05, 2004 - 01:43 pm:   

Bryce,

Here are logs for phones described in my last message.
text/plainSiemens ST60
Siemens_ST60.txt (3.2 k)

text/plainSonyEricsson T630
SE_T630.txt (3.4 k)

text/plainNokia 6610
Nokia_6610.txt (2.5 k)

text/plainMotorola V400p
Mot_V400p.txt (3.4 k)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3718
Registered: 10-2002
Posted on Monday, November 08, 2004 - 07:47 pm:   

Hi David,

I'm sorry, but I'm really out of ideas on this one.

Comparing what works for the T630 and ST60 ... the only thing I notice different in the V400p's SMIL is that it includes a "type=" parameter in the "text" and "img" elements. If the library is actually complaining about the SMIL content, it would be a tall order for us to deal with this on our end.

Also, for the phone that is not including SMIL, I'm afraid there's not much that we can do there.

Maybe you could try Nokia's libraries? I haven't had any personal experience using them, but we have had several postings here from people who were trying to use them with NowSMS. (And when there were problems, they seemed like more logical problems than an error parsing the SMIL, which I can't imagine why the library even needs to be concerned with this ...)
David Chkhartishvili
New member
Username: Datoch

Post Number: 20
Registered: 06-2004
Posted on Tuesday, November 09, 2004 - 08:17 am:   

Thank you Bryce.

Actually, I was trying to get mms and then forward it to e-mail.
As I remember few people requested that feature, are you going to implement (in MMSC Routing) it and if yes approx. when?

Thanks again.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3738
Registered: 10-2002
Posted on Thursday, November 11, 2004 - 08:46 pm:   

Hi David,

There was a recent thread where someone wanted the ability to redirect MMS messages being sent to an e-mail address so that they were routed via an "MMSC Routing" definition, instead of having NowSMS attempt to route them directly to e-mail.

But I don't think that is what you are looking for.

Can you explain what you're trying to do. There might be a way. You can do an MM4 connection in "MMSC Routing", and we'll add a domain name on to the phone number for routing the message.

-bn
David Chkhartishvili
New member
Username: Datoch

Post Number: 21
Registered: 06-2004
Posted on Tuesday, November 16, 2004 - 09:13 am:   

Hi Bryce,

I meant to add forwarding to email feature to "MMSC Routing".
For example: I want to forward all incoming mms's sent to number: 1234 to email address: test@test.com.

Thanks
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3788
Registered: 10-2002
Posted on Sunday, December 05, 2004 - 10:28 pm:   

Hi David,

I see what you mean. You want an "MMSC Routing" that forwards to a fixed e-mail address instead of phonenumber@domain.

Let me do some thinking on that, as I'm sure there must be some easy way that we could facilitate this.

-bn
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3791
Registered: 10-2002
Posted on Thursday, December 09, 2004 - 05:45 pm:   

Hi David,

I apologise that I didn't think of this earlier. But there is actually a way to accomplish what you want.

We've got a "short code" table, which allows you to convert a "short code" into a longer phone number, or to an e-mail address.

Here is a note that provides some explanation:

Short codes can be used to map a short phone number to a longer phone number or e-mail address. Short codes can also be used to map an e-mail address to a short code that is route to a VASP.
For example, a short code of 200 could be rerouted to an e-mail address. To define short codes, create a section titled [ShortCode] in the MMSC.INI file. Under that section, create entries in the following format:
###=+44335830375474/TYPE=PLMN
###=user@domain.com
In the examples above, "###" is a numeric short code address, and the value after the "=" sign is the address the short code should be rerouted to, specified as either a phone number in MMS addressing format (/TYPE=PLMN) or as an e-mail address.
Similarly, to route an e-mail address to a short code that is routed via a VASP, use the following format:
user@domain.com=6000/TYPE=PLMN

Basically, for your example above, what you want to do is edit MMSC.INI, and add the following:

[ShortCode]
1234=test@test.com

I would like to see us work another scenario for this where we map it into the "MMSC Routing" logic, but this might solve your issue without any changes to the software.

-bn
David Chkhartishvili
New member
Username: Datoch

Post Number: 22
Registered: 06-2004
Posted on Friday, December 10, 2004 - 09:34 am:   

Thanks Bryce,

I will try shortcode on monday and inform you about results.

BR,
David

David Chkhartishvili
New member
Username: Datoch

Post Number: 23
Registered: 06-2004
Posted on Monday, December 13, 2004 - 10:15 am:   

Bryce,

I've tried your solution, that's exactly what I wanted.

Thank you.