Re: Siemens S55 WAP problems fixed?!

On Thursday, April 17, 2003, at 10:10 AM, Andreas Fink wrote:

>
> On Donnerstag, April 17, 2003, at 10:18  Uhr, Paul Keogh wrote:
>
>>>
>>> have someone seen Siemens s55 mms working ? Even with
>>> some great operator ? This would of course help me.
>>>
>>
>> We've seen it working through our in-house WAP gateway.
>> The required change, as suggested by this list, is to
>> remove "application/vnd.wap.mms-message" from the wsp-strings.def
>> file so that the content type encoding is long form rather than
>> short form. This is because the S55 is strictly WSP 1.3 compliant
>> and the MMS content type was defined in WSP 1.4.
>
> in other words, the S55 is absolutely definitively unable to support 
> MMS according to specs?

Specs themselves seems to be rather vague what to do with the push. S55 
is sending Encoding-
Version: 1.3, which tells that it does not understand tokenized 
"application/vnd.wap.mms-message".
Ok when pulling, but what to do when pushing ? Just send untokenized 
content-type type in every
case ?

>
>
>> So the S55 fix is easy but does it raise the bigger issue of whether
>> or not Kannel needs to be aware of what version WSP encoding is being
>> used in a particular session ? Ideally Kannel would support all
>> versions of WSP but only enable up to a revision level indicated by
>> the device.
>
> How can you know in advance what revision a phone supports when you 
> send a WAP push to the phone??

Tokenized Content-Type would be great when doing notifications (when 
every single character counts), but
it a lot less useful when fecthing - expect if some 1.4 decides that it 
does not understand untokenized value

Aarno