It seems to be a bug? with libxml, perhaps. I've two scenarios, a production environment & a test environment.
THE TEST SYSTEM: RedHat Linux 7.2 Kannel CVS version 2002/02/28 LibXML version libxml2-2.4.10-1 (devel & XML Packet) THE PRODUCTION SYSTEM: RedHat Linux 7.0 Kannel CVS version 2002/02/28 LibXML version libxml2-2.4.6-1 (devel & XML Packet) In the "test environment" Siemens S35 works with Kannel WAP standard configuration. (strange!) In the production environment it does not work!!!! (with Kannel WAP standart conf.) And if I've configured ppg push I got the message, ### 2002-03-02 19:46:08 [1] WARNING: Unknown content type 0x202. 2002-03-02 19:46:08 [1] WARNING: Skipping faulty header. 2002-03-02 19:46:08 [1] WARNING: Unknown content type 0x201. 2002-03-02 19:46:08 [1] WARNING: Skipping faulty header. 2002-03-02 19:46:08 [1] WARNING: Unknown content type 0x203. 2002-03-02 19:46:08 [1] WARNING: Skipping faulty header. 2002-03-02 19:46:08 [1] WARNING: Unknown content type 0x206. 2002-03-02 19:46:08 [1] WARNING: Skipping faulty header. 2002-03-02 19:46:08 [1] WARNING: Unknown content type 0x204. etcetera ### No page will be displayed! And if I've NOT configured ppg push I get the message, I got nothing from the phone and Kannel, strange, isn't it? (I HAVE NOT YET TESTED the libxml2-2.4.10-1 on the production environment)!! I suppose it will be run. (I try to change the "libxml" version to ibxml2-2.4.10-1 on our production site tonight) I have nothing to do like this. :-))) What do you think ???? Thanks for your answers, I'm on your guiltiness, anyway ! Bjoern > -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]Im Auftrag von Bjoern Buettner > Gesendet: Samstag, 2. März 2002 03:56 > An: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Betreff: AW: Problems using WAP with siemens S35 /prev.("WARNING: > Skipping faulty header. / trouble with SIEMENS S35 / Kannel WAP /" ) > > > > Does wdp-interface-name in core group match the IP address > > configured in the > > phone's WAP settings? This can be a problem with Openwave > browsers if > > > the > > machine has more than one IP address. > Yes it does ! I've tested the "Asterix" and IP Numbers. > > Andreas wrote @ 31.01.2002 15:20: > > This is the usual additional nonstandard headers phones are sending > > which are using the phone.com (now openwave) browser. You can safely > > ignore it. It just means that your phone sends more than what the > > standards are specifying. > I cannot see any WML Page ! > > Stipe wrote @ 31.01.2002 15:30: > > 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. > Shit :-) I do not see anything with Siemens Phones! > > > > 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. > What can I do? I can get some contacts with "OpenWave.com"? I'm working on > it! > > I've the same problem with Kannel "2002-02-28-cvs". I've tested it today. > That's my new test version. ( I' hope I can be productive with > this version > very soon) > > Has anybody testet the Siemens ME45 mobile phone, successfully ? > > Please see Subject "WARNING: Skipping faulty header. / trouble > with SIEMENS > S35 / Kannel WAP /" postings. > The problem is unfortunately not solved, yet and wellknown! > > Why is the stable version of Kannel running with this phone (Siemens S35) > and not the current cvs versions? > > I have a big project running with "Kannel" or I want to run it with this! > Naturally, I can run the official stable version of Kannel (1.0.3), it > work's, but I want to use some new features of the CVS version. > > Oh guys, damn, I love Kannel, but I need a some working Siemens > phones! :-)) > > How can I help. I'm not a "C" programmer, yet, but I want help, :-) > > I can't sleep while the problem is not solved !!! :-) > > Thanx for your answers, guys! > > Bjoern > > > > -----Ursprüngliche Nachricht----- > > Von: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]Im Auftrag von Ian Daly > > Gesendet: Freitag, 1. März 2002 11:21 > > An: [EMAIL PROTECTED] > > Betreff: RE: Problems using WAP with siemens S35 > > > > > > It looks like the wapbox is waiting for an acknowledgement from > the phone. > > Does wdp-interface-name in core group match the IP address > > configured in the > > phone's WAP settings? This can be a problem with Openwave > browsers if the > > machine has more than one IP address. > > > > Ian > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED]]On Behalf Of Bjoern Buettner > > > Sent: 28 February 2002 21:56 > > > To: [EMAIL PROTECTED] > > > Subject: Problems using WAP with siemens S35 > > > > > > > > > Hi list, > > > > > > Has anybody the Siemens S35 WAP (UP -Browser ) succsessfully > > > tested with the > > > current CVS Version? > > > > > > I know it's a UP-browser problem but (it was discussed > > > earlier in the list), > > > i have to need the run with this phone. > > > > > > Is it possible to make a UP upgrade or something like that. > > > Or what can we do? > > > > > > Which phones & browser are testet sucsessfully ? > > > > > > > > > Thanks guys > > > > > > Bjoern > > > > > > here is the debug mesg. > > > > > > ####################################### > > > > > > 2002-02-28 21:45:09 [1] INFO: Returning to code page 1 (default). > > > 2002-02-28 21:45:09 [6] DEBUG: WTP: Created WTPRespMachine > > > 0x81fb718 (1) > > > 2002-02-28 21:45:09 [6] DEBUG: WTP: resp_machine 1, state > > > LISTEN, event > > > RcvInvoke. > > > 2002-02-28 21:45:09 [6] DEBUG: WTP 1: New state INVOKE_RESP_WAIT > > > 2002-02-28 21:45:09 [1] DEBUG: WSP: Created WSPMachine 0x81f4fc0 > > > 2002-02-28 21:45:09 [1] DEBUG: WSP: machine 0x81f4fc0, state > > > NULL_SESSION, > > > event TR-Invoke.ind > > > 2002-02-28 21:45:09 [6] DEBUG: WTP: resp_machine 1, state > > > INVOKE_RESP_WAIT, > > > event TR-Invoke.res. > > > 2002-02-28 21:45:09 [1] DEBUG: WSP: decoding headers: > > > 2002-02-28 21:45:09 [6] DEBUG: WTP 1: New state RESULT_WAIT > > > 2002-02-28 21:45:09 [1] DEBUG: Octet string at 0x81eee58: > > > 2002-02-28 21:45:09 [1] DEBUG: len: 42 > > > 2002-02-28 21:45:09 [1] DEBUG: size: 43 > > > 2002-02-28 21:45:09 [1] DEBUG: immutable: 0 > > > 2002-02-28 21:45:09 [1] DEBUG: data: 80 05 94 83 02 04 54 > > > 80 ......T. > > > 2002-02-28 21:45:09 [1] DEBUG: data: 94 80 95 01 a9 53 49 > > > 45 .....SIE > > > 2002-02-28 21:45:09 [1] DEBUG: data: 2d 53 33 35 2f 33 2e > > > 30 -S35/3.0 > > > 2002-02-28 21:45:09 [1] DEBUG: data: 20 55 50 2f 34 2e 31 > > > 2e UP/4.1. > > > 2002-02-28 21:45:09 [1] DEBUG: data: 31 36 6d 00 83 99 80 > > > a1 16m..... > > > 2002-02-28 21:45:09 [1] DEBUG: data: 81 ea .. > > > 2002-02-28 21:45:09 [1] DEBUG: Octet string dump ends. > > > 2002-02-28 21:45:09 [1] INFO: Returning to code page 1 (default). > > > 2002-02-28 21:45:09 [1] DEBUG: WSP: decoded headers: > > > 2002-02-28 21:45:09 [1] DEBUG: Accept: > > > application/vnd.wap.wmlc; type=1108 > > > 2002-02-28 21:45:09 [1] DEBUG: Accept: application/vnd.wap.wmlc > > > 2002-02-28 21:45:09 [1] DEBUG: Accept: application/vnd.wap.wmlscriptc > > > 2002-02-28 21:45:09 [1] DEBUG: User-Agent: SIE-S35/3.0 UP/4.1.16m > > > 2002-02-28 21:45:09 [1] DEBUG: Accept-Language: en > > > 2002-02-28 21:45:09 [1] DEBUG: Accept: image/vnd.wap.wbmp > > > 2002-02-28 21:45:09 [1] DEBUG: Accept-Charset: utf-8 > > > 2002-02-28 21:45:09 [1] DEBUG: WSP: End of decoded headers. > > > 2002-02-28 21:45:09 [1] DEBUG: WSP 1: New state CONNECTING > > > 2002-02-28 21:45:09 [1] DEBUG: WSP: machine 0x81f4fc0, state > > > CONNECTING, > > > event S-Connect.res > > > 2002-02-28 21:45:09 [1] DEBUG: WSP 1: New state CONNECTING_2 > > > 2002-02-28 21:45:09 [6] DEBUG: WTP: resp_machine 1, state > > > RESULT_WAIT, event > > > TR-Result.req. > > > 2002-02-28 21:45:09 [6] DEBUG: WTP 1: New state RESULT_RESP_WAIT > > > 2002-02-28 21:45:14 [6] DEBUG: WTP: resp_machine 1, state > > > RESULT_RESP_WAIT, > > > event RcvInvoke. > > > 2002-02-28 21:45:14 [6] DEBUG: WTP 1: New state RESULT_RESP_WAIT > > > 2002-02-28 21:45:16 [4] DEBUG: Timeout-R elapsed. > > > 2002-02-28 21:45:16 [6] DEBUG: WTP: resp_machine 1, state > > > RESULT_RESP_WAIT, > > > event Timeout-R. > > > 2002-02-28 21:45:16 [6] DEBUG: WTP 1: New state RESULT_RESP_WAIT > > > 2002-02-28 21:45:21 [6] DEBUG: WTP: resp_machine 1, state > > > RESULT_RESP_WAIT, > > > event RcvInvoke. > > > 2002-02-28 21:45:21 [6] DEBUG: WTP 1: New state RESULT_RESP_WAIT > > > 2002-02-28 21:45:23 [4] DEBUG: Timeout-R elapsed. > > > 2002-02-28 21:45:23 [6] DEBUG: WTP: resp_machine 1, state > > > RESULT_RESP_WAIT, > > > event Timeout-R. > > > 2002-02-28 21:45:23 [6] DEBUG: WTP 1: New state RESULT_RESP_WAIT > > > 2002-02-28 21:45:30 [4] DEBUG: Timeout-R elapsed. > > > 2002-02-28 21:45:30 [6] DEBUG: WTP: resp_machine 1, state > > > RESULT_RESP_WAIT, > > > event Timeout-R. > > > 2002-02-28 21:45:30 [6] DEBUG: WTP 1: New state RESULT_RESP_WAIT > > > 2002-02-28 21:45:37 [4] DEBUG: Timeout-R elapsed. > > > 2002-02-28 21:45:37 [6] DEBUG: WTP: resp_machine 1, state > > > RESULT_RESP_WAIT, > > > event Timeout-R. > > > 2002-02-28 21:45:37 [6] DEBUG: WTP 1: New state RESULT_RESP_WAIT > > > 2002-02-28 21:45:44 [4] DEBUG: Timeout-R elapsed. > > > 2002-02-28 21:45:44 [6] DEBUG: WTP: resp_machine 1, state > > > RESULT_RESP_WAIT, > > > event Timeout-R. > > > 2002-02-28 21:45:44 [6] DEBUG: WTP 1: New state RESULT_RESP_WAIT > > > 2002-02-28 21:45:51 [4] DEBUG: Timeout-R elapsed. > > > 2002-02-28 21:45:51 [6] DEBUG: WTP: resp_machine 1, state > > > RESULT_RESP_WAIT, > > > event Timeout-R. > > > 2002-02-28 21:45:51 [6] DEBUG: WTP 1: New state RESULT_RESP_WAIT > > > 2002-02-28 21:45:58 [4] DEBUG: Timeout-R elapsed. > > > 2002-02-28 21:45:58 [6] DEBUG: WTP: resp_machine 1, state > > > RESULT_RESP_WAIT, > > > event Timeout-R. > > > 2002-02-28 21:45:58 [6] DEBUG: WTP 1: New state RESULT_RESP_WAIT > > > 2002-02-28 21:46:05 [4] DEBUG: Timeout-R elapsed. > > > 2002-02-28 21:46:05 [6] DEBUG: WTP: resp_machine 1, state > > > RESULT_RESP_WAIT, > > > event Timeout-R. > > > 2002-02-28 21:46:05 [6] DEBUG: WTP 1: New state RESULT_RESP_WAIT > > > 2002-02-28 21:46:12 [4] DEBUG: Timeout-R elapsed. > > > 2002-02-28 21:46:12 [6] DEBUG: WTP: resp_machine 1, state > > > RESULT_RESP_WAIT, > > > event Timeout-R. > > > 2002-02-28 21:46:12 [6] DEBUG: WTP 1: New state LISTEN > > > 2002-02-28 21:46:12 [6] DEBUG: WTP: Destroying WTPRespMachine > > > 0x81fb718 (1) > > > 2002-02-28 21:46:12 [1] DEBUG: WSP: machine 0x81f4fc0, state > > > CONNECTING_2, > > > event TR-Abort.ind > > > 2002-02-28 21:46:12 [1] DEBUG: WSP 1: New state NULL_SESSION > > > 2002-02-28 21:46:12 [1] DEBUG: Destroying WSPMachine 0x81f4fc0 > > > > > > > > > > > > kind regards > > > > > > Vodafone TeleCommerce GmbH > > > Architecture & Engineering > > > Bjoern Buettner > > > Daniel Goldbach Str. 17-19 > > > 40880 Ratingen > > > > > > Tel. +49 (0) 21 02 / 97 20 13 > > > Fax +49 (0) 21 02 / 97 15 14 > > > > > > mailto:[EMAIL PROTECTED] > > > www.vodafone.com > > > www.vodafone-telecommerce.de > > > > > > > > > > > > > > > > --------------------------------------------------------- > > 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! > --------------------------------------------------------- >
