Re: WARNING: Skipping faulty header. / trouble with SIEMENS S35 /Kannel WAP /

Hi  Werkstudent :-)

My Siemens S35 get the Time out.

Here is the Debug message from kannel.

Thanx


Bjoern

#########
Kannel WAP DEBUG
###
2002-01-31 13:17:37 [0] DEBUG: Started thread 14
(gw/heartbeat.c:heartbeat_thread)
2002-01-31 13:19:12 [6] DEBUG: WTP: Created WTPRespMachine 0x821c9f0 (0)
2002-01-31 13:19:12 [6] DEBUG: WTP: resp_machine 0, state LISTEN, event
RcvInvoke.
2002-01-31 13:19:12 [6] DEBUG: WTP 0: New state INVOKE_RESP_WAIT
2002-01-31 13:19:12 [1] DEBUG: WSP: Created WSPMachine 0x821d4d8
2002-01-31 13:19:12 [1] DEBUG: WSP: machine 0x821d4d8, state NULL_SESSION,
event TR-Invoke.ind
2002-01-31 13:19:12 [6] DEBUG: WTP: resp_machine 0, state INVOKE_RESP_WAIT,
event TR-Invoke.res.
2002-01-31 13:19:12 [6] DEBUG: WTP 0: New state RESULT_WAIT
2002-01-31 13:19:12 [1] DEBUG: WSP: decoding headers:
2002-01-31 13:19:12 [1] DEBUG: Octet string at 0x821d270:
2002-01-31 13:19:12 [1] DEBUG:   len:  162
2002-01-31 13:19:12 [1] DEBUG:   size: 163
2002-01-31 13:19:12 [1] DEBUG:   immutable: 0
2002-01-31 13:19:12 [1] DEBUG:   data: 80 05 94 83 02 04 54 80   ......T.
2002-01-31 13:19:12 [1] DEBUG:   data: 94 80 95 80 03 02 02 02   ........
2002-01-31 13:19:12 [1] DEBUG:   data: 80 03 02 02 01 80 03 02   ........
2002-01-31 13:19:12 [1] DEBUG:   data: 02 03 80 03 02 02 06 80   ........
2002-01-31 13:19:12 [1] DEBUG:   data: 03 02 02 04 80 03 02 02   ........
2002-01-31 13:19:12 [1] DEBUG:   data: 05 80 03 02 02 09 80 b3   ........
2002-01-31 13:19:12 [1] DEBUG:   data: 80 a3 80 61 70 70 6c 69   ...appli
2002-01-31 13:19:12 [1] DEBUG:   data: 63 61 74 69 6f 6e 2f 78   cation/x
2002-01-31 13:19:12 [1] DEBUG:   data: 2d 75 70 2d 64 65 76 69   -up-devi
2002-01-31 13:19:12 [1] DEBUG:   data: 63 65 00 80 03 02 02 0a   ce......
2002-01-31 13:19:12 [1] DEBUG:   data: 80 61 70 70 6c 69 63 61   .applica
2002-01-31 13:19:12 [1] DEBUG:   data: 74 69 6f 6e 2f 6f 63 74   tion/oct
2002-01-31 13:19:12 [1] DEBUG:   data: 65 74 2d 73 74 72 65 61   et-strea
2002-01-31 13:19:12 [1] DEBUG:   data: 6d 00 10 99 81 91 81 93   m.......
2002-01-31 13:19:12 [1] DEBUG:   data: 81 01 a9 53 49 45 2d 53   ...SIE-S
2002-01-31 13:19:12 [1] DEBUG:   data: 33 35 2f 33 2e 30 20 55   35/3.0 U
2002-01-31 13:19:12 [1] DEBUG:   data: 50 2f 34 2e 31 2e 31 36   P/4.1.16
2002-01-31 13:19:12 [1] DEBUG:   data: 6d 00 83 99 80 a1 81 ea   m.......
2002-01-31 13:19:12 [1] DEBUG:   data: 10 87 82 86 80 88 85 8d   ........
2002-01-31 13:19:12 [1] DEBUG:   data: 81 10 80 06 c2 03 11 5d   .......]
2002-01-31 13:19:12 [1] DEBUG:   data: 00 ff                     ..
2002-01-31 13:19:12 [1] DEBUG: Octet string dump ends.
2002-01-31 13:19:12 [1] WARNING: Unknown content type 0x202.
2002-01-31 13:19:12 [1] WARNING: Skipping faulty header.
2002-01-31 13:19:12 [1] WARNING: Unknown content type 0x201.
2002-01-31 13:19:12 [1] WARNING: Skipping faulty header.
2002-01-31 13:19:12 [1] WARNING: Unknown content type 0x203.
2002-01-31 13:19:12 [1] WARNING: Skipping faulty header.
2002-01-31 13:19:12 [1] WARNING: Unknown content type 0x206.
2002-01-31 13:19:12 [1] WARNING: Skipping faulty header.
2002-01-31 13:19:12 [1] WARNING: Unknown content type 0x204.
2002-01-31 13:19:12 [1] WARNING: Skipping faulty header.
2002-01-31 13:19:12 [1] WARNING: Unknown content type 0x205.
2002-01-31 13:19:12 [1] WARNING: Skipping faulty header.
2002-01-31 13:19:12 [1] WARNING: Unknown content type 0x209.
2002-01-31 13:19:12 [1] WARNING: Skipping faulty header.
2002-01-31 13:19:12 [1] WARNING: Unknown content type 0x20a.
2002-01-31 13:19:12 [1] WARNING: Skipping faulty header.
2002-01-31 13:19:12 [1] WARNING: Shift to unknown code page 16.
2002-01-31 13:19:12 [1] WARNING: Will try to skip headers until next known
code page.
2002-01-31 13:19:12 [1] DEBUG: Skipping field 0x99.
2002-01-31 13:19:12 [1] DEBUG: Skipping field 0x91.
2002-01-31 13:19:12 [1] DEBUG: Skipping field 0x93.
2002-01-31 13:19:12 [1] INFO: Returning to code page 1 (default).
2002-01-31 13:19:12 [1] WARNING: Shift to unknown code page 16.
2002-01-31 13:19:12 [1] WARNING: Will try to skip headers until next known
code page.
2002-01-31 13:19:12 [1] DEBUG: Skipping field 0x87.
2002-01-31 13:19:12 [1] DEBUG: Skipping field 0x86.
2002-01-31 13:19:12 [1] DEBUG: Skipping field 0x88.
2002-01-31 13:19:12 [1] DEBUG: Skipping field 0x8d.
2002-01-31 13:19:12 [1] WARNING: Shift to unknown code page 16.
2002-01-31 13:19:12 [1] WARNING: Will try to skip headers until next known
code page.
2002-01-31 13:19:12 [1] DEBUG: Skipping field 0x80.
2002-01-31 13:19:12 [1] DEBUG: WSP: decoded headers:
2002-01-31 13:19:12 [1] DEBUG: Accept: application/vnd.wap.wmlc; type=1108
2002-01-31 13:19:12 [1] DEBUG: Accept: application/vnd.wap.wmlc
2002-01-31 13:19:12 [1] DEBUG: Accept: application/vnd.wap.wmlscriptc
2002-01-31 13:19:12 [1] DEBUG: Accept: application/vnd.wap.multipart.related
2002-01-31 13:19:12 [1] DEBUG: Accept: application/vnd.wap.multipart.mixed
2002-01-31 13:19:12 [1] DEBUG: Accept: application/x-up-device
2002-01-31 13:19:12 [1] DEBUG: Accept: application/octet-stream
2002-01-31 13:19:12 [1] DEBUG: User-Agent: SIE-S35/3.0 UP/4.1.16m
2002-01-31 13:19:12 [1] DEBUG: Accept-Language: en
2002-01-31 13:19:12 [1] DEBUG: Accept: image/vnd.wap.wbmp
2002-01-31 13:19:12 [1] DEBUG: Accept-Charset: utf-8
2002-01-31 13:19:12 [1] DEBUG: WSP: End of decoded headers.
2002-01-31 13:19:12 [1] DEBUG: WSP 0: New state CONNECTING
2002-01-31 13:19:12 [1] DEBUG: WSP: machine 0x821d4d8, state CONNECTING,
event S-Connect.res
2002-01-31 13:19:12 [1] DEBUG: WSP 0: New state CONNECTING_2
2002-01-31 13:19:12 [6] DEBUG: WTP: resp_machine 0, state RESULT_WAIT,
event TR-Result.req.

----- Original Message -----
From: "WERKSTUDENT1" <[email protected]>
To: <[email protected]>
Cc: <[email protected]>
Sent: Friday, February 01, 2002 10:23 AM
Subject: AW: WARNING: Skipping faulty header. / trouble with SIEMENS S35
/Kannel WAP /


> Hi!
> May I ask, what kind of timeout? Maybe you can send the log-information?
>
> Thanks,
> Marc
>
> -----Ursprüngliche Nachricht-----
> Von: Bjoern Buettner [mailto:[email protected]]
> Gesendet: Donnerstag, 31. Januar 2002 21:42
> An: Stipe Tolj
> Cc: [email protected]
> Betreff: AW: WARNING: Skipping faulty header. / trouble with SIEMENS S35
> /Kannel WAP /
>
>
> Hi again,
>
> I'm so sorry!!!
> What i want to say is, i did a mistake.
> Our production environment is Kannel WAP version 1.0.3
> our Test environment is Kannel WAP version 1.1.5. (not 1.0.5 that's
bullshit
> :-)) )
>
> Sorry again ;-(
>
> > > AFAIK, phone.com did this to enable properietary functionality with
> > > their own phone.com WAP GW. So the WML deck should be displayed using
> > > kannel, but you still get the warnings in the log.
>
> > The main problem is that I cannot get the WML content of my W@P Server,
> > The Siemens phone get's a timeout  :-((  and no page !
> Has anybody a solution regarding my problem?
>
> That's very important, because I want to make (or must) an upgrade to the
> CVS version from 30-dec-2001 or later. We plan to lauch a "a BIG PROJECT"
> with Kannel WAP/SMS, "perhaps". I mean, I have a chance to establish
Kannel
> for a worldwide project, that pretty cool I think.
>
> And "perhaps", I have a chance to sponsor Kannel! (I cannot pledge it,
that
> it works, but I will work on it )
>
> I need a Kannel version that works with most mobiles (Siemens, Nokia,
> (Motorrola), Erricson)
> and i need WTLS/SSL encryption for WAP/SMS.
>
> Thanx to all guys
>
>
> Bjoern
>
> Leave me not alone ;-)
>
>
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: [email protected]
> > [mailto:[email protected]]Im Auftrag von Bjoern Buettner
> > Gesendet: Donnerstag, 31. Januar 2002 16:27
> > An: Stipe Tolj
> > Cc: [email protected]
> > Betreff: Re: WARNING: Skipping faulty header. / trouble with SIEMENS S35
> > /Kannel WAP /
> >
> >
> > Stipe wrote:
> > > AFAIK, phone.com did this to enable properietary functionality with
> > > their own phone.com WAP GW. So the WML deck should be displayed using
> > > kannel, but you still get the warnings in the log.
> >
> > The main problem is that I cannot get the WML content of my W@P Server,
> > The Siemens phone get's a timeout  :-((  and no page !
> >
> > > The browser seems to set headers that are explicitly out of the
> > > official specification and hence Kannel detects it as unknown content
> > > types!
> > But it was working in version 1.0.3 & 1.0.5
> >
> > Bjoern
> >
> > ----- Original Message -----
> > From: "Stipe Tolj" <[email protected]>
> > To: "Bjoern Buettner" <[email protected]>
> > Cc: <[email protected]>
> > Sent: Thursday, January 31, 2002 3:29 PM
> > Subject: Re: WARNING: Skipping faulty header. / trouble with SIEMENS S35
> > /Kannel WAP /
> >
> >
> > > Bjoern Buettner wrote:
> > > >
> > > > I've configured the kannel WAP GW- in version "cvs 30-dec.2001".
> > > >
> > > > Previous version of Kannel WAP  was 1.0.5,  it worked very fine.
> > > > With the new version, we have some problems with SIEMENS S35 Phones.
> > > > If I try to connect with the SIEMENS S35 to the gw, following error
> > appears.
> > > >
> > > > "2002-01-31 13:19:12 [1] WARNING: Unknown content type 0x202."
> > > > "2002-01-31 13:19:12 [1] WARNING: Skipping faulty header."
> > > >
> > > > Is it a problem with Kannel or the SIEMENS S35 WAP Browser ?
> > >
> > > I guess this is a problem with the user agent of Siemens S35, the
> > > openwave.com (aka phone.com) browser.
> > >
> > > The browser seems to set headers that are explicitly out of the
> > > official specification and hence Kannel detects it as unknown content
> > > types!
> > >
> > > AFAIK, phone.com did this to enable properietary functionality with
> > > their own phone.com WAP GW. So the WML deck should be displayed using
> > > kannel, but you still get the warnings in the log.
> > >
> > > There has been a thread on the mailing list if we should figure out
> > > what this headers are used to mean and if we would try to support
> > > them. But as you may imagine this would mean getting onto to
> > > properietary line of phone.com and the group das declined to do so.
> > >
> > > Stipe
> > >
> > > [email protected]
> > > -------------------------------------------------------------------
> > > Wapme Systems AG
> > >
> > > Münsterstr. 248
> > > 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
> > >
> > >
> > >
> > > ---------------------------------------------------------
> > > This Mail has been checked for Viruses
> > > Attention: Encrypted mails can NOT be checked!
> > >
> > > **
> > >
> > > Diese Mail wurde auf Viren geprueft
> > > Hinweis: Verschluesselte mails koennen NICHT auf Viren geprueft
werden!
> > > ---------------------------------------------------------
> > >
> >
> >
> >
> >
> > ---------------------------------------------------------
> > This Mail has been checked for Viruses
> > Attention: Encrypted mails can NOT be checked!
> >
> > **
> >
> > Diese Mail wurde auf Viren geprueft
> > Hinweis: Verschluesselte mails koennen NICHT auf Viren geprueft werden!
> > ---------------------------------------------------------
> >
>
>
>
>
> ---------------------------------------------------------
> This Mail has been checked for Viruses
> Attention: Encrypted mails can NOT be checked!
>
> **
>
> Diese Mail wurde auf Viren geprueft
> Hinweis: Verschluesselte mails koennen NICHT auf Viren geprueft werden!
> ---------------------------------------------------------
>