Stipe Tolj kirjoittaa tiistaina, 9. hein�kuuta 2002, kello 14:23:Aarno,
>
> you seem to be familiar with the MMS encoding, can you write a short
> text file that contains a PPG request with a M.notification-ind and
> the corresponding data hex representation, so we others can see how
> the beasts look like.
>
> I have certain immagination, but yet it does not clear up for me in my
> clouded head ;)
Here it comes (my reading of specs)
In full textual format:
Headers:
Content-Type: multipart/related; boundary=asdlfkjiuvwghasf;
type="application/xml"
X-WAP-Application-Id: x-wap-application:mms.ua
Content:
--asdlfkjiuvwghasf
<?xml version="1.0"?>
<!DOCTYPE pap PUBLIC "-//WAPFORUM/DTD PAP 1.0//EN"
"http://www.wapforum.org/DTD/pap_1.0.dtd";>
<pap>
<push-message push-id="[EMAIL PROTECTED]">
<address address-value="WAPPUSH=+12234567 /TYPE=PLMN@
ppg.carrier.com">
</address>
</push-message>
</pap>
--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--
When the content is tokenized, it would look like this (headers in
different lines):
84bc
8c82
9831323500
8d90
8a80
8e0164
880481020100
83"yout URI"00
Aarno
