Hi Ken, thanks for your input. Yes, I suspected the content type myself, so I will do some further experimenting in this area. I was not aware that the content type is actually limited to application/vnd.wap.multipart.mixed. The T-Mobile MMSC here in Germany happily accepts whatever I send (tested with text/plain, image/jpeg, image/gif) and the T610 displays all of this.
To answer your question: This is a trace from my MMS client. I choose the Ericsson User-Agent header because this is what I used to test the SIM cards to make sure they are actually MMS enabled. Kind regards J�rg -----Urspr�ngliche Nachricht----- Von: Ken Kim [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 29. Januar 2004 22:39 An: J�rg Pommnitz; 'Kannel-Devel (E-Mail)' Betreff: RE: A plea for help to the MMS experts Hi, Just quickly scanning your pdu, I noticed that your content-type is 0x83 (text/plain). This should be 0xA3(application/vnd.wap.multipart.mixed) followed by 0x01(representing the number of contents in your multipart mixed mime message.) See 7.4.1 of the mms conformance doc for more details. You can only have application/vnd.wap.multipart.mixed or application/vnd.wap.multipart.related(for smil) Then for each mime part your start out with: ----- <length of content-type> eg:0x01 <length of data> 0x83 -- content-type:text/plain {data....} ----- Something like that. Just curious, is this what the T610 spits out, or is this your own mms client? Cheers, Ken -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of J�rg Pommnitz Sent: January 29, 2004 11:47 AM To: Kannel-Devel (E-Mail) Subject: A plea for help to the MMS experts Hi List, I'm trying to get a MMS client to work. Unfortunately with only minor success so far. Attached is a tcpdump of the communication between the MMS WAP gateway (from the German network operator E-Plus) and my MMS client. You can view it with ethereal (both, under Linux and Windows). Any ideas what I'm doing wrong? Thanks in advance J�rg
