Re: MMS client

Hi Marcel,

> I can put it somewhere public tomorrow, it will probably be as crude as
> a tarball of my source; 'configure' and 'make' should work as normal.
> 
> Since I wasn't familiar enough with the kannel setup to design with
> integration in mind I decided to just change and remove things to suit
> the MMS client. The biggest difference is that bearerbox, wapbox and
> smsbox have been collapsed into one executable, appropriate for a client
> in my opinion.

ok, I guess we'll have to see how to addopt. If it's way to huge to
addopt it to the current tree, we'll put it into an own cvs module. I
guess this is the cleanest way.

> It's not interpreting the MMS contents. If you are refering to the
> PDUs: similar to WSP and WDP and those lovely preprocessor tricks
> that confused the hell out of my debugger.

yep. I did the MMS encoder/decoder with the WSP header code ;)

> MMS messages are currently written to a file in XML format (although
> this can be easily changed), here's an example:
> 
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <mms>
>     <x_mms_message_type>132</x_mms_message_type>
>     <x_mms_mms_version>1.0</x_mms_mms_version>
>     <date>1051305903</date>
>     <subject_charset>128</subject_charset>
>     <subject>mms message subject 2</subject>
>     <content_type>application/vnd.wap.multipart.mixed</content_type>
>     <data
> encoding="base64">ASAig8AiPDNFQTk0MDFGLnR4dD4AjjNFQTk0MDFGLnR4dABUaGlzIGlzIH
> RoZSB0ZXh0DQpJdCBk ZWZpbmF0ZWx5IGlz </data>
> </mms>

ok, this is an approach. Others may vary.

Stipe

[email protected]
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: [email protected]
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are