Hi all, > What I was wonder was if anybody had successfully used the pdu: > > Text part: > 0f 06 0d be 96 7f 00 a9 7f 00 af 84 8d c1 b4 80 3f 3f 3f 39 39 39 39 40 > 66 6c 79 65 72 6f 6e 65 2e 63 6f 6d 00 3f 90 > 3f 3f 3f 01 64 3f 06 3f 04 3d 2b 2f 4a 3f 68 74 74 70 3a 2f 2f 77 77 77 > 2e 66 6c 79 65 72 6f 6e 65 2e 63 6f 6d 2f 00 3f be > > udh: > 06 05 04 0b 84 23 f0
I think you forget something, try this (looking ad previous posts): UDH: 0605040b8423f0 Text part: 0f060dbe967f00a97f00af848dc1b4800f0603ceaf843f3f3f3939393940666c7965726f6e65 2e636f6d003f903f3f3f01643f063f043d2b2f4a3f687474703a2f2f7777772e666c7965726f 6e652e636f6d2f003fbe I'm not sure this is correct (not tested yet), who can post a simple working example? > When the phone gets a notification, it starts the fetch. To get content, > you must implement other MMSC features. Aarno, what do you mean here? Which features? If content-location is mysite/mms.txt and mms.txt is a text file, this should work or not? --- mms.txt begin --- X-Mms-Message-Type: m-retrieve-conf X-Mms-MMS-Version: 1.0 Date: ... To: ... Content-Type: application/vnd.wap.multipart.related; start="<0@mms>"; boundary="----=_NextPart_000_0088_01C21B74.C108A240"; type="application/smil" ------=_NextPart_000_0088_01C21B74.C108A240 Content-ID: <0@mms> Content-Type: application/smil; charset="US-ASCII" <smil> <head> ... --- mms.txt end --- Hi, Enzo
