Are you sure that the expiry date is in the future ? Use date -r to
check this.
Aarno
On Wednesday, September 11, 2002, at 07:02 PM, FERLA Alessandro
Consultant wrote:
I tryed again with the conversion form that I found on the site but
it's not
working.
8c 82
// X-MMS-Message-Type:
the
%0A is the new line character and should work w/o problems, unless your handset
drops the new lines in favor of compacting the text for easier readability as my
Noika 7160 does.
--Oded Arbelm-Wise mobile solutions[EMAIL PROTECTED]
+972-9-9581711 (116)+972-67-340014
::..Player1: "What
Hi,
Is this a bug or a known feature? If I POST stuff as
application/vnd.wap.multipart.form-data and the content
is compressed wml then Kannel lets the whole thing
through with the same content encoding..without
decompressing the wmlc.
I tried this on another gateway and it decompressed
the
I tryed with date -r filename but I just get back the date of creation of
the file. I can't understand how the X-MMS-Expiry date is encoded. Is there
any documentation about that?
Thank you.
Alessandro.
-Messaggio originale-
Da: Aarno Syvänen [mailto:[EMAIL PROTECTED]]
Inviato:
I tryed with date -r filename but I just get back the date
of creation of
the file. I can't understand how the X-MMS-Expiry date is
encoded. Is there
any documentation about that?
Look at 7.2.10 of WAP-209-MMSEncapsulation-20020105-a for Expiry field
encoding.
Then look at WSP for
Is this a bug or a known feature? If I POST stuff as
application/vnd.wap.multipart.form-data and the content
is compressed wml then Kannel lets the whole thing
through with the same content encoding..without
decompressing the wmlc.
I tried this on another gateway and it decompressed
the
-Original Message-
From: Paul Keogh [mailto:[EMAIL PROTECTED]]
[...]
There is no support in Kannel for the WSP multipart data construct
which I guess is the encoding used for
application/vnd.wap.multipart.form-data
MIME types. No support means no encoding or decoding support.
