Re: MMS notification

Aarno Syvänen <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
Hi,

On Saturday, May 31, 2003, at 06:53 PM, Dean Maslic wrote:

> Hi all,
>
> Just a few questions in regards to m-notification-ind to which I
> couldn't find answers in the specs & mail-list:
>
> 1. Are there any other mandatory WSP headers except
> X-Wap-Application-Id: mms.ua (AF 84) ?
> 	(Ive seen Stipe use 96=Host, 8D=Content-length, B4=Push-flag,
> see extract)

I have removed Host (a bug) and Push-Flag (a misfeature), see the
patch in the list. We could start arguing about Content-Length, i think
it is mandatory. But, of course, you need Content-Type

>
> 2. Is it possible to use OMNA WSP Content Type Number "0x3E" for
> "application/vnd.wap.mms-message" instead of encoding the whole string 
> ?

No, if you want to speak with all phones. S55 demands the string (Token
is part of wsp v 1.4, and this phone supports only v 1.3). But you can 
drop
From, which is optional.

>
> 3. Does the 140 byte limit per binary sms include &udh part or just the
> &text part in case of using sendsms ?

Both text and udh (including SAR UDH)

Aarno

>
>
> This is the extract form
> http://www.kannel.org/mailman/private/devel/2003-April/017016.html
>
>    data: 00 06 36 61 70 70 6c 69   ..6appli
>    data: 63 61 74 69 6f 6e 2f 76   cation/v
>    data: 6e 64 2e 77 61 70 2e 6d   nd.wap.m
>    data: 6d 73 2d 6d 65 73 73 61   ms-messa
>    data: 67 65 00 96 6c 6f 63 61   ge..loca
>    data: 6c 68 6f 73 74 3a 39 30   lhost:90
>    data: 39 30 00 af 84 8d fc b4   90......
>    data: 80 8c 82 98 35 64 30 64   ....5d0d
>    data: 32 66 61 62 32 61 30 63   2fab2a0c
>    data: 66 37 34 65 61 63 63 37   f74eacc7
>    data: 39 64 64 63 62 36 34 34   9ddcb644
>    data: 64 62 35 37 00 8d 90 8a   db57....
>    data: 80 8e 02 02 32 88 05 81   ....2...
>    data: 03 01 51 80 83 68 74 74   ..Q..htt
>    data: 70 3a 2f 2f xx xx 2e xx   p://xx.x
>    data: xx 2e xx xx 2e xx 36 xx   x.xx.xx:
>    data: xx xx xx xx 2f 72 65 63   xxxx/rec
>    data: 65 69 76 65 6d 6d 73 3f   eivemms?
>    data: 6d 69 64 3d 35 64 30 64   mid=5d0d
>    data: 32 66 61 62 32 61 30 63   2fab2a0c
>    data: 66 37 34 65 61 63 63 37   f74eacc7
>    data: 39 64 64 63 62 36 34 34   9ddcb644
>    data: 64 62 35 37 00            db57.
>
>
> Appreciate any response
>
> Dean
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.