Send internet format message/content as MMS

Send internet format message/content as MMS SearchSearch
Author Message
swathi
New member
Username: Swathi

Post Number: 5
Registered: 05-2009
Posted on Friday, June 05, 2009 - 08:32 am:   

Hi,

i have a message structured according to internet email that is according to RFC 2387 .

Now i want to send this message as mms . So do i need to consider the encoding of this message or direclty can i send this to MMSC by setting this content to the MM1 PDU . If so are there any tools to do this.

Please suggest.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 908
Registered: 08-2008
Posted on Friday, June 05, 2009 - 07:52 pm:   

Hi,

You seem to have many questions that are all related. I'm not going to comment on them all ... but here is a general comment ...

In another thread, you have built an MM1 PDU, which is what you would need to do if you are submitting an MMS message to an operator MMSC over a modem connection.

You're not going to get very far trying to post an internet e-mail format message to an MMSC. (That format is similar to what is used for an MM4 inter-operator connection, but not similar enough to an MM1 PDU.)

--
Des
NowSMS Support
swathi
New member
Username: Swathi

Post Number: 7
Registered: 05-2009
Posted on Saturday, June 06, 2009 - 07:13 am:   

yes you are right Des.

Actually iam new to MMS and i have lot of confusion related to MM1 content encoding which i think can be cleared only by people like you.

I understand your comments and i am confused and unable to conclude is

Iam contructing the MM1 PDU . the mm1 headers iam clear. but coming to the mm1 content do i need to encode the internet e-mail format message before setting it as mm1 content ?

Please suggest.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 918
Registered: 08-2008
Posted on Monday, June 08, 2009 - 10:17 pm:   

I think I understand your confusion now.

The content of the MMS is message is indeed multipart/related (can also be multipart/mixed) ... at least, "logically" it is.

Physically it is encoded as application/vnd.wap.multipart.related (or application/vnd.wap.multipart.mixed).

This is a binary encoding for a multipart message. It is defined as part of the WAP WSP specification (WAP-230-WSP). http://www.openmobilealliance.org/tech/affiliates/wap/wapindex.html

--
Des
NowSMS Support
swathi
New member
Username: Swathi

Post Number: 8
Registered: 05-2009
Posted on Tuesday, June 09, 2009 - 02:55 pm:   

Thanks a lot Des for the info .

I went through the bianry encodiing for multipart message in the specification .But iam unable to map i meam wrt implementation how to change/encode the internet email multipart message according to the given specification.
do i have to get the content parts from the internet email multipart message and encode according to specification ? or directly i can encode it . If sp it would be great if you could give me some pointers how to go about.

Thanks & Regards
swathi
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 932
Registered: 08-2008
Posted on Wednesday, June 10, 2009 - 09:34 pm:   

Hi swathi,

There is a one-to-one mapping between the formats.

The primary difference is that the encoding of the headers uses a binary encoding instead of a text encoding.

Instead of MIME boundary markers, each part starts with a header length field that tells how large the header is, and a body length field that tells the size of the body part.

The headers are encoded using the WSP header encoding.

The content parts are not encoded at all (8-bit binary), whereas in an SMTP message you might see BASE64 or quoted-printable encoding. So if you are receiving internet e-mail, you would need to decode any encoded content parts.

It's definitely a bit overwhelming at first glance.

If you search out here using keywords of WSP encoding multipart, there are some old threads that have MM1 PDU examples which may help in some understanding.

Most of the threads that I found have the MM1 PDU inside of a WSP POST PDU. WSP POST is WSP encoding of an HTTP POST, which is similar. You don't necessarily need to understand that part, just the MM1 part of it.

One good example is in http://support.nowsms.com/discus/messages/12/522.html.

Half way down that thread, Bryce shares a dump of a simple WSP POST transaction. Search the page for "8C 80 98 31" to find the start of the MM1 PDU within the POST.

That's probably the best help I can give you ... point you to a message that you can look at to try to decode to better understand.

--
Des
NowSMS Support