Re: Fw: Wapbox problem, please help!
On Wed, 6 Nov 2002 12:03:06 +0300
Yury Mikhienko [EMAIL PROTECTED] wrote:
On Tue, 05 Nov 2002 15:59:37 +0200
Vjacheslav Chekushin [EMAIL PROTECTED] wrote:
I don't know about your case, but in my case I got this error
using new nokia 7650 in connection-less mode.
Skipped wapbox.log part must show it. If this is the case, then
you have to possibilites:
1. Recomplile kannel with force-sar flag.
2. Apply SAR patch (can be found on list).
Then nokia 7650 users must switch phones to connection-oriented mode.
Hi again Vjacheslav!
Thanks for your reply!
I applied SAR patch to kannel v1.2.1
(SAR-cumulative.patch
# From: Igor Ivoilov
# Subject: RE: WSP SAR and PDU types
# Date: Thu, 03 Oct 2002 01:36:17 -0700)
And I recompilled kannel with this patch without any problems (and without force-sar
flag, because I did not find this flag in configure script)
I changed kannel source for dumping the next information:
in wapbox.log now:
2002-11-12 09:21:45 [1] DEBUG: WSP 227/4150: New method state REPLYING
2002-11-12 09:21:45 [1] DEBUG: WSP 227: New state CONNECTED
2002-11-12 09:21:45 [2] WARNING: WSP PDU with unknown type -1
2002-11-12 09:21:45 [2] WARNING: Incoming Octetstr has been dumped!!!
2002-11-12 09:21:45 [2] DEBUG: Octet string at 0x89a77c8:
2002-11-12 09:21:45 [2] DEBUG:len: 74
2002-11-12 09:21:45 [2] DEBUG:size: 76
2002-11-12 09:21:45 [2] DEBUG:immutable: 0
2002-11-12 09:21:45 [2] DEBUG:data: 73 5a 12 01 10 13 30 04 sZ0.
2002-11-12 09:21:45 [2] DEBUG:data: 80 86 a0 00 04 81 92 a7
2002-11-12 09:21:45 [2] DEBUG:data: 60 02 82 00 02 83 05 02 `...
2002-11-12 09:21:45 [2] DEBUG:data: 84 01 80 80 83 99 81 ea
2002-11-12 09:21:45 [2] DEBUG:data: a9 4e 6f 6b 69 61 37 36 .Nokia76
2002-11-12 09:21:45 [2] DEBUG:data: 35 30 2f 31 2e 30 20 53 50/1.0 S
2002-11-12 09:21:45 [2] DEBUG:data: 79 6d 62 69 61 6e 4f 53 ymbianOS
2002-11-12 09:21:45 [2] DEBUG:data: 2f 36 2e 31 20 53 65 72 /6.1 Ser
2002-11-12 09:21:45 [2] DEBUG:data: 69 65 73 36 30 2f 30 2e ies60/0.
2002-11-12 09:21:45 [2] DEBUG:data: 39 00 9.
2002-11-12 09:21:45 [2] DEBUG: Octet string dump ends.
2002-11-12 09:21:45 [6] DEBUG: Thread 6 (gw/wap-appl.c:main_thread) terminates.
How can I solve this? May be I shall apply another SAR patch (which one?)?
Or this problen can be solved another way?
Now I solved the problem with dirty hack the gwthread-pthread.c:
in:
static void *new_thread(void *arg)
{
int ret;
struct new_thread_args *p = arg;
(p-func)(p-arg);
/* Changed by me */
do
{
lock();
debug(gwlib.gwthread, 0, Thread %ld (%s) terminates. ,
p-ti-number, p-ti-name);
debug(gwlib.gwthread, 0, Try up Thread %ld (%s). ,
p-ti-number, p-ti-name);
unlock();
ret = pthread_setspecific(tsd_key, p-ti);
if (ret != 0) {
panic(ret, gwthread-pthread: pthread_setspecific failed);
}
(p-func)(p-arg);
}while(p-ti-number==6 !strcmp(p-ti-name,gw/wap-appl.c:main_thread));
//**
};
It works, but it is not a good way :((
Thanx.
--
Best regards,
Yury Mikhienko.
IT engineer, ZAO Mobicom-Kavkaz
Re: Fw: Wapbox problem, please help!
On Tue, 05 Nov 2002 15:59:37 +0200 Vjacheslav Chekushin [EMAIL PROTECTED] wrote: I don't know about your case, but in my case I got this error using new nokia 7650 in connection-less mode. Skipped wapbox.log part must show it. If this is the case, then you have to possibilites: 1. Recomplile kannel with force-sar flag. 2. Apply SAR patch (can be found on list). Then nokia 7650 users must switch phones to connection-oriented mode. Hi again Vjacheslav! So, I applied SAR patch to kannel v1.2.1 (SAR-cumulative.patch # From: Igor Ivoilov # Subject: RE: WSP SAR and PDU types # Date: Thu, 03 Oct 2002 01:36:17 -0700) And I recompilled kannel with this patch without any problems (and without force-sar flag, because I did not find this flag in configure script) I am starting kannel and having problems again after it works for 4 hours :((( in wapbox.log: 2002-11-05 22:33:39 [1] DEBUG: WSP 2/174: New method state REQUESTING 2002-11-05 22:33:39 [1] DEBUG: WSP 2: New state CONNECTED 2002-11-05 22:33:39 [6] DEBUG: expire_cookies: No cookies in cache 2002-11-05 22:33:39 [6] DEBUG: set_cookies: No cookies in cache 2002-11-05 22:33:39 [1] DEBUG: WSP: machine 0x80dc538, state CONNECTED, event S-MethodInvoke.res 2002-11-05 22:33:39 [1] DEBUG: WSP: method 174, state REQUESTING, event S-MethodInvoke.res 2002-11-05 22:33:39 [1] DEBUG: WSP 2/174: New method state PROCESSING 2002-11-05 22:33:39 [1] DEBUG: WSP 2: New state CONNECTED 2002-11-05 22:33:39 [5] DEBUG: WTP: resp_machine 174, state INVOKE_RESP_WAIT, event TR-Invoke.res. 2002-11-05 22:33:39 [5] DEBUG: WTP 174: New state RESULT_WAIT connect to HTTP PROXY 2002-11-05 22:33:39 [10] DEBUG: HTTP: Opening connection to `111.111.11.111:' (fd=33). 2002-11-05 22:33:39 [10] DEBUG: HTTP: Sending request: 2002-11-05 22:33:39 [10] DEBUG: Octet string at 0x80eb078: 2002-11-05 22:33:39 [10] DEBUG: len: 933 2002-11-05 22:33:39 [10] DEBUG: size: 934 2002-11-05 22:33:39 [10] DEBUG: immutable: 0 2002-11-05 22:33:39 [10] DEBUG: data: 47 45 54 20 68 74 74 70 GET http 2002-11-05 22:33:39 [10] DEBUG: data: 3a 2f 2f 77 61 70 2e 66 ://wap.f 2002-11-05 22:33:39 [10] DEBUG: data: 6f 72 66 6c 69 72 74 2e orflirt. 2002-11-05 22:33:39 [10] DEBUG: data: 72 75 2f 69 6e 64 65 78 ru/index 2002-11-05 22:33:39 [10] DEBUG: data: 2e 77 6d 6c 3f 6f 3d 31 .wml?o=1 ... User agent: 2002-11-05 22:33:39 [10] DEBUG: data: 0a 55 73 65 72 2d 41 67 .User-Ag 2002-11-05 22:33:39 [10] DEBUG: data: 65 6e 74 3a 20 53 41 4d ent: SAM 2002-11-05 22:33:39 [10] DEBUG: data: 53 55 4e 47 2d 53 47 48 SUNG-SGH 2002-11-05 22:33:39 [10] DEBUG: data: 2d 52 32 31 30 53 2f 31 -R210S/1 2002-11-05 22:33:39 [10] DEBUG: data: 2e 30 20 55 50 2f 34 2e .0 UP/4. 2002-11-05 22:33:39 [10] DEBUG: data: 31 2e 31 39 6b 0d 0a 41 1.19k..A 2002-11-05 22:33:39 [10] DEBUG: data: 63 63 65 70 74 2d 4c 61 ccept-La 2002-11-05 22:33:39 [10] DEBUG: data: 6e 67 75 61 67 65 3a 20 nguage: 2002-11-05 22:33:39 [10] DEBUG: data: 65 6e 0d 0a 41 63 63 65 en..Acce 2002-11-05 22:33:39 [10] DEBUG: data: 70 74 3a 20 69 6d 61 67 pt: imag 2002-11-05 22:33:39 [10] DEBUG: data: 65 2f 76 6e 64 2e 77 61 e/vnd.wa 2002-11-05 22:33:39 [10] DEBUG: data: 70 2e 77 62 6d 70 0d 0a p.wbmp.. 2002-11-05 22:33:39 [10] DEBUG: data: 41 63 63 65 70 74 2d 43 Accept-C 2002-11-05 22:33:39 [10] DEBUG: data: 68 61 72 73 65 74 3a 20 harset: 2002-11-05 22:33:39 [10] DEBUG: data: 75 74 66 2d 38 0d 0a 41 utf-8..A ... Gateway: 2002-11-05 22:33:39 [10] DEBUG: data: 0a 58 2d 57 41 50 2d 47 .X-WAP-G 2002-11-05 22:33:39 [10] DEBUG: data: 61 74 65 77 61 79 3a 20 ateway: 2002-11-05 22:33:39 [10] DEBUG: data: 4b 61 6e 6e 65 6c 2f 31 Kannel/1 2002-11-05 22:33:39 [10] DEBUG: data: 2e 32 2e 31 0d 0a 58 2d .2.1..X- 2002-11-05 22:33:39 [10] DEBUG: data: 57 41 50 2d 53 65 73 73 WAP-Sess 2002-11-05 22:33:39 [10] DEBUG: data: 69 6f 6e 2d 49 44 3a 20 ion-ID: 2002-11-05 22:33:39 [10] DEBUG: data: 32 0d 0a 0d 0a2 2002-11-05 22:33:39 [10] DEBUG: Octet string dump ends. ##!! this again :((( !!# 2002-11-05 22:33:39 [2] WARNING: WSP PDU with unknown type -1 2002-11-05 22:33:39 [6] DEBUG: Thread 6 (gw/wap-appl.c:main_thread) terminates. # :((( ## 2002-11-05 22:33:39 [9] DEBUG: HTTP: Status line: HTTP/1.0 200 OK ... kannel configuration: group = core admin-port = 13000 smsbox-port = 13001 wapbox-port = 9201 admin-password = admin status-password = password admin-deny-ip = *.*.*.* admin-allow-ip = 10.10.10.10;127.0.0.1 log-file = /var/log/kannel/bearerbox.log log-level = 0 wdp-interface-name = 111.111.11.110 box-deny-ip = *.*.*.* box-allow-ip = 111.111.11.110;127.0.0.1 unified-prefix = 928,00928,0 access-log = /var/log/kannel/access.log http-proxy-host=111.111.11.111 http-proxy-port= my wapbox configuration: group = wapbox bearerbox-host = 111.111.11.110 log-file =
Re: Fw: Wapbox problem, please help!
Hi, I am not a kannel developper but I had initially a similar Pb (unknown message ... -1) with any previous stable versions of kannel. I posted many questinos about the pb and initially thought it was a GPRS issue (it is certainly not, can you confirm that ?). Finally, a linux expert helped me to compile myself the kannel gateway on the target system. This solved this pb and others and by this time kannel wapbox works perfectly. I advise you to find some help to compile yourself kannel on your system. I hope this will help. PYB --- Yury Mikhienko [EMAIL PROTECTED] a écrit : Begin forwarded message: Date: Mon, 4 Nov 2002 10:15:22 +0300 From: Yury Mikhienko [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Wapbox problem, please help! Hi all! Time for time I have the strange problem for kannel wapbox. The symptom of problem is following (in wapbox.log): ... 2002-11-04 01:12:54 [10] DEBUG: HTTP: Sending request: 2002-11-04 01:12:54 [10] DEBUG: Octet string at 0x8142218: 2002-11-04 01:12:54 [10] DEBUG: len: 757 2002-11-04 01:12:54 [10] DEBUG: size: 758 2002-11-04 01:12:54 [10] DEBUG: immutable: 0 2002-11-04 01:12:54 [10] DEBUG: data: 47 45 54 20 68 74 74 70 GET http ... 2002-11-04 01:12:54 [10] DEBUG: data: 58 2d 57 41 50 2d 47 61 X-WAP-Ga 2002-11-04 01:12:54 [10] DEBUG: data: 74 65 77 61 79 3a 20 4b teway: K 2002-11-04 01:12:54 [10] DEBUG: data: 61 6e 6e 65 6c 2f 31 2e annel/1. 2002-11-04 01:12:54 [10] DEBUG: data: 32 2e 30 0d 0a 58 2d 57 2.0..X-W 2002-11-04 01:12:54 [10] DEBUG: data: 41 50 2d 53 65 73 73 69 AP-Sessi 2002-11-04 01:12:54 [10] DEBUG: data: 6f 6e 2d 49 44 3a 20 31 on-ID: 1 2002-11-04 01:12:54 [10] DEBUG: data: 31 0d 0a 0d 0a1 2002-11-04 01:12:54 [10] DEBUG: Octet string dump ends. 2002-11-04 01:12:54 [9] DEBUG: HTTP: Status line: HTTP/1.0 200 OK 2002-11-04 01:12:54 [7] INFO: WSP: Fetched http://wap.mts.ru (text/vnd.wap.wml, charset='') 2002-11-04 01:12:54 [7] DEBUG: get_cookies: Examining header (Date: Thu, 26 Sep 2002 11:50:47 GMT) 2002-11-04 01:12:54 [7] DEBUG: get_cookies: Examining header (Server: Apache/1.3.14 (Unix) rus/PL30.1) 2002-11-04 01:12:54 [7] DEBUG: get_cookies: Examining header (Last-Modified: Tue, 30 Apr 2002 10:57:11 GMT) 2002-11-04 01:12:54 [7] DEBUG: get_cookies: Examining header (ETag: 1b4837-11c-3cce7887) 2002-11-04 01:12:54 [7] DEBUG: get_cookies: Examining header (Accept-Ranges: bytes) 2002-11-04 01:12:54 [7] DEBUG: get_cookies: Examining header (Content-Length: 284) 2002-11-04 01:12:54 [7] DEBUG: get_cookies: Examining header (Content-Type: text/vnd.wap.wml) 2002-11-04 01:12:54 [7] DEBUG: get_cookies: Examining header (Age: 140424) 2002-11-04 01:12:54 [7] DEBUG: get_cookies: Examining header (X-Cache: HIT from wapgate.mobicomk.donpac.ru) 2002-11-04 01:12:54 [7] DEBUG: get_cookies: Examining header (X-Cache-Lookup: HIT from wapgate.mobicomk.donpac.ru:3128) 2002-11-04 01:12:54 [7] DEBUG: get_cookies: Examining header (Proxy-Connection: keep-alive) 2002-11-04 01:12:54 [7] DEBUG: get_cookies: End 2002-11-04 01:12:54 [7] DEBUG: WSP: Setting Referer URL to http://wap.mts.ru 2002-11-04 01:12:54 [1] DEBUG: WSP: machine 0x80da7f8, state CONNECTED, event S-MethodResult.req 2002-11-04 01:12:54 [1] DEBUG: WSP: method 111, state PROCESSING, event S-MethodResult.req 2002-11-04 01:12:54 [5] DEBUG: WTP: resp_machine 111, state RESULT_WAIT, event TR-Result.req. 2002-11-04 01:12:54 [5] DEBUG: WTP 111: New state RESULT_RESP_WAIT 2002-11-04 01:12:54 [1] DEBUG: WSP 11/111: New method state REPLYING 2002-11-04 01:12:54 [1] DEBUG: WSP 11: New state CONNECTED 2002-11-04 01:12:55 [5] DEBUG: WTP: resp_machine 102, state TIDOK_WAIT, event RcvAbort. 2002-11-04 01:12:55 [5] DEBUG: WTP 102: New state LISTEN 2002-11-04 01:12:55 [5] DEBUG: WTP: Destroying WTPRespMachine 0x80db110 (102) !!in this lines*!! 2002-11-04 01:12:55 [2] WARNING: WSP PDU with unknown type -1 ** -- 2002-11-04 01:12:55 [6] DEBUG: Thread 6 (gw/wap-appl.c:main_thread) terminates. !!*!! 2002-11-04 01:12:56 [5] DEBUG: WTP: Created WTPRespMachine 0x80db110 (112) 2002-11-04 01:12:56 [5] DEBUG: WTP: resp_machine 112, state LISTEN, event RcvInvoke. 2002-11-04 01:12:56 [5] DEBUG: WTP 112: New state INVOKE_RESP_WAIT 2002-11-04 01:12:56 [1] DEBUG: WSP: machine 0x80da7f8, state CONNECTED, event TR-Invoke.ind 2002-11-04 01:12:56 [1] DEBUG: WSP: method 112, state NULL_METHOD, event TR-Invoke.ind 2002-11-04 01:12:56 [1] DEBUG: WSP 11/112: New method state HOLDING 2002-11-04 01:12:56 [1] DEBUG: WSP: method 112, state HOLDING, event Release 2002-11-04 01:12:56 [1] DEBUG: WSP 11/112: New method state REQUESTING 2002-11-04 01:12:56 [1] DEBUG: WSP 11: New state CONNECTED 2002-11-04 01:12:57 [4] DEBUG: Timeout-R elapsed. 2002-11-04 01:12:57 [5] DEBUG: WTP: resp_machine 110, state
Re: Fw: Wapbox problem, please help!
On Tue, 5 Nov 2002 13:40:15 +0100 (CET) Pierre-Yves BOURGEOIS [EMAIL PROTECTED] wrote: Hi, I am not a kannel developper but I had initially a similar Pb (unknown message ... -1) with any previous stable versions of kannel. I posted many questinos about the pb and initially thought it was a GPRS issue (it is certainly not, can you confirm that ?). Finally, a linux expert helped me to compile myself the kannel gateway on the target system. This solved this pb and others and by this time kannel wapbox works perfectly. I advise you to find some help to compile yourself kannel on your system. I hope this will help. PYB Hi,thanx for you reply. But what is the target system? May be kannel properly works only on RedHat (or Debian) linux? I have compiled kannel on mandrake linux (kernel v2.4) without any problems... And my mobile network does not support GPRS. I don't understand where I'm wrong :((( -- Best regards, Yury Mikhienko. IT engineer, ZAO Mobicom-Kavkaz
Re: Fw: Wapbox problem, please help!
On Tue, 05 Nov 2002 15:59:37 +0200 Vjacheslav Chekushin [EMAIL PROTECTED] wrote: I don't know about your case, but in my case I got this error using new nokia 7650 in connection-less mode. Skipped wapbox.log part must show it. If this is the case, then you have to possibilites: 1. Recomplile kannel with force-sar flag. 2. Apply SAR patch (can be found on list). Then nokia 7650 users must switch phones to connection-oriented mode. Hi Vjacheslav! I found and applied SAR patch to kannel v1.2.1 , but I did not find force-sar flag in configure :(( How I can refer to compiller this flag? -- Best regards, Yury Mikhienko. IT engineer, ZAO Mobicom-Kavkaz
