I have a couple of questions regarding the tokenization, as I still haven't managed to get this working.
> --asdlfjiuvwghasf > Content-Type: application/vnd.wap.mms-message > X-MMS-Message-Type: m-notification-ind > X-MMS-Transaction-Id: 125 > X-MMS-Version: 1.0 > X-MMS-Message-Class: personal > X-MMS-Message-Size: 100 > X-MMS-Expiry: 256; type=relative > X-MMS-Content-Location: your URI > --asdlfjiuvwghasf-- Should the encoded headers be posted to the PPG as mime encoded or not? In the example I've attached below, stuff isn't submitted as mime encoded, which atleast looks ok. > 84bc This is the content-type, so it should be last (7.0 in MMSEncapsulation). > 8c82 > 9831323500 > 8d90 > 8a80 > 8e0164 > 880481020100 > 83"yout URI"00 Anyway, here's my MMSEncapsulated doc: 8c 82 // X-MMS-Message-Type: m-notification-ind 98 39 39 39 39 40 66 6c 79 65 72 6f 6e 65 2e 63 6f 6d 00 // X-MMS-Transaction-Id: [EMAIL PROTECTED] 8d 90 // X-MMS-Version: 1.0 8a 80 // X-MMS-Message-Class: Personal 8e 01 64 // X-MMS-Size: 100 88 06 80 04 3d 2b 32 4a // X-MMS-Expiry: an Absolute value, in the future 83 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 // X-MMS-Content-Location: http://www.flyerone.com/ 84 be // Content-type: application/vnd.wap.mms-message When this is sent to the ppg, the resulting push OTA message looks like this: 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 haven't yet been able to decode this message, so I'd like some feedback if it even remotely looks like something that could work, or if there's some obious flaw. When the handset (a 7650) receives the message, something happens (the gprs indicator changes status), but no fetch is still happening at http://www.flyerone.com/. Regards, - Anders
