Re: wap push to siemens again

Szymon Stasik <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
Aarno Syvänen wrote:
> UDH (both ports and SAR) are defined in WAP-259 (WDP Spec). Port numbers 
> are
> capitulated in appendix 4 (A.4). SI spec is WAP-167 (contains an example 
> tokenized
> SI document). Usually only Content-type is required here (actually 
> WAP-145 states
> that only it is mandatory).

thanks, I'll look there

> What kind of Siemens phone did you use ? And a very stupid question: 
> does it support
> WAP 1.2 ?

siemens m50, mt50 (actually its the same phone), me45, s45. All of them 
supprost wap 1.2.1 and than wap push (there are configuration options 
for push, all set to full access).

Someone have answered to me that he have exactly the same problem (and 
no one have reported any success with push working on this phones till now;)


Szymon

> Aarno
> 
> On Friday, November 22, 2002, at 02:11 AM, Szymon Stasik wrote:
> 
>> and which wap spec should I look into? I guess there is something 
>> wrong in UDH...
>>
>> Stipe Tolj wrote:
>>
>>>> I'd like to investigate the problem deeper and my question is if there
>>>> is any possibility to have some push message correctly recognised on
>>>> siemens phone? I can look into wapforum specs, however any working case
>>>> or some other tips would be helpfull.
>>>
>>> unfortunatly we at Wapme don't have these phones here, otherwise I may
>>> test too. Anyone that could provide more debugging here?!
>>> Stipe
>>> [email protected]
>>> -------------------------------------------------------------------
>>> Wapme Systems AG
>>> Vogelsanger Weg 80
>>> 40470 Düsseldorf
>>> Tel: +49-211-74845-0
>>> Fax: +49-211-74845-299
>>> E-Mail: [email protected]
>>> Internet: http://www.wapme-systems.de
>>> -------------------------------------------------------------------
>>> wapme.net - wherever you are
>>
>>
>>
>>
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.