Issue with Kannel as a wap gateway
Hi list. I have some problem with using kannel as a wap gateway. I have two machines, one with a CVS snapshot of about a month ago and one with a recent CVS snapshot (let's say - today). now I'm using a kyocera phone to access the gateway, and it works with the old version but not with the new one. For the life of me I can't figure why. From the logs it looks like a problem in the WTP state machine - on the machine that works I get this: 2004-05-05 11:27:29 [6] DEBUG: WTP: Created WTPRespMachine 0x4999fb48 (1925) 2004-05-05 11:27:29 [6] DEBUG: WTP: resp_machine 1925, state LISTEN, event RcvInvoke. 2004-05-05 11:27:29 [6] DEBUG: WTP 1925: New state INVOKE_RESP_WAIT 2004-05-05 11:27:29 [1] DEBUG: WSP: Created WSPMachine 0x499ad158 2004-05-05 11:27:29 [1] DEBUG: WSP: machine 0x499ad158, state NULL_SESSION, event TR-Invoke.ind 2004-05-05 11:27:29 [6] DEBUG: WTP: resp_machine 1925, state INVOKE_RESP_WAIT, event TR-Invoke.res. 2004-05-05 11:27:29 [6] DEBUG: WTP 1925: New state RESULT_WAIT 2004-05-05 11:27:29 [1] DEBUG: WSP: decoding headers: 2004-05-05 11:27:29 [1] INFO: Returning to code page 1 (default). 2004-05-05 11:27:29 [1] DEBUG: WSP: decoded headers: 2004-05-05 11:27:29 [1] DEBUG: WSP: End of decoded headers. 2004-05-05 11:27:29 [1] DEBUG: WSP 582: New state CONNECTING 2004-05-05 11:27:29 [1] DEBUG: WSP: machine 0x499ad158, state CONNECTING, event S-Connect.res All this is the same on both machines. then the one that works say this: 2004-05-05 11:27:29 [6] DEBUG: WTP: resp_machine 1925, state RESULT_WAIT, event TR-Result.req. 2004-05-05 11:27:29 [1] DEBUG: WSP 582: New state CONNECTING_2 2004-05-05 11:27:29 [6] DEBUG: WTP 1925: New state RESULT_RESP_WAIT 2004-05-05 11:27:30 [6] DEBUG: WTP: resp_machine 1925, state RESULT_RESP_WAIT, event RcvAck. 2004-05-05 11:27:30 [6] DEBUG: WTP 1925: New state LISTEN 2004-05-05 11:27:30 [6] DEBUG: WTP: Destroying WTPRespMachine 0x4999fb48 (1925) 2004-05-05 11:27:30 [1] DEBUG: WSP: machine 0x499ad158, state CONNECTING_2, event TR-Result.cnf 2004-05-05 11:27:30 [1] DEBUG: WSP 582: New state CONNECTED 2004-05-05 11:27:30 [6] DEBUG: WTP: Created WTPRespMachine 0x499bd0a8 (1926) 2004-05-05 11:27:30 [6] DEBUG: WTP: resp_machine 1926, state LISTEN, event RcvInvoke. 2004-05-05 11:27:30 [6] DEBUG: WTP 1926: New state INVOKE_RESP_WAIT and it goes on fetching HTTP request and everything is ok. OTOH the newer version say this: 2004-05-05 14:01:59 [6459] [1] DEBUG: WSP: Mapping `Encoding-Version', WSP 1.2 to 0x. 2004-05-05 14:01:59 [6464] [6] DEBUG: WTP: resp_machine 0, state RESULT_WAIT, event TR-Result.req. 2004-05-05 14:01:59 [6459] [1] DEBUG: WSP 0: New state CONNECTING_2 2004-05-05 14:01:59 [6464] [6] DEBUG: WTP 0: New state RESULT_RESP_WAIT 2004-05-05 14:02:04 [6464] [6] DEBUG: WTP: resp_machine 0, state RESULT_RESP_WAIT, event RcvInvoke. 2004-05-05 14:02:04 [6464] [6] DEBUG: WTP 0: New state RESULT_RESP_WAIT 2004-05-05 14:02:06 [6462] [4] DEBUG: Timeout-R elapsed. 2004-05-05 14:02:06 [6464] [6] DEBUG: WTP: resp_machine 0, state RESULT_RESP_WAIT, event Timeout-R. 2004-05-05 14:02:06 [6464] [6] DEBUG: WTP 0: New state RESULT_RESP_WAIT 2004-05-05 14:02:12 [6464] [6] DEBUG: WTP: resp_machine 0, state RESULT_RESP_WAIT, event RcvInvoke. 2004-05-05 14:02:12 [6464] [6] DEBUG: WTP 0: New state RESULT_RESP_WAIT 2004-05-05 14:02:13 [6462] [4] DEBUG: Timeout-R elapsed. And repeats the last 5 lines over and over and over again until I get bored and turn off the phone. I don't know much about Kannel's wap internals but it looks like a timeout somewhere , but 2 seconds is really not that long. I tried to compare the code from both versions but I can't put my finger on what might be causing the probelm - mostly as there are about 20 lines of codes changed between both versions, mostly to do with whitespace and other non-crucial stuff. Please tell me what am I missing -- Oded Arbel m-Wise mobile solutions [EMAIL PROTECTED] +972-9-9611212 (204) +972-54-7340014 ::.. Leeloo : "Everything you create, you use to destroy." Korben Dallas : "Yeah, we call it human nature." -- from "The Fifth Element"
Re: Issue with Kannel as a wap gateway
Hi Paul,
I personally don't like strXX functions family if I can avoid this :)
Please check attached patch and if it ok then I will commit it to cvs...
Btw. would you care for userguide patch, due to config option change?
Thanks in advance.
On Thursday 06 May 2004 13:42, Paul P Komkoff Jr wrote:
> Replying to Stipe Tolj:
> > have you posted the patch to the devel@ list?! If no, please do, so we
> > can review and commit to cvs.
>
> Stipe!
>
> For a long time I'm only posting and posting patches to devel list,
> and noone paying attention to it.
>
> attached split-up of bb_udp only change, which should do multiple wdp
> interfaces trick.
--
Best regards / Mit besten Grüßen aus Düsseldorf
Dipl.-Ing.
Alexander Malysh
___
Centrium GmbH
Vogelsanger Weg 80
40470 Düsseldorf
Fon: +49 (0211) 74 84 51 80
Fax: +49 (0211) 277 49 109
email: a.malysh (at) centrium.de
web: www.centrium.de
msn: a.malysh (at) centrium.de
icq: 98063111
___
Please avoid sending me Word, Excel or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
Index: gw/bb_udp.c
===
RCS file: /home/cvs/gateway/gw/bb_udp.c,v
retrieving revision 1.32
diff -a -u -r1.32 bb_udp.c
--- gw/bb_udp.c 22 Jan 2004 14:08:24 - 1.32
+++ gw/bb_udp.c 13 May 2004 21:33:58 -
@@ -322,8 +322,9 @@
int udp_start(Cfg *cfg)
{
-Octstr *interface_name;
CfgGroup *grp;
+Octstr *iface;
+List *ifs;
int allow_wtls;
if (udp_running) return -1;
@@ -331,8 +332,8 @@
debug("bb.udp", 0, "starting UDP sender/receiver module");
grp = cfg_get_single_group(cfg, octstr_imm("core"));
-interface_name = cfg_get(grp, octstr_imm("wdp-interface-name"));
-if (interface_name == NULL) {
+iface = cfg_get(grp, octstr_imm("wdp-interface-name"));
+if (iface == NULL) {
error(0, "Missing wdp-interface-name variable, cannot start UDP");
return -1;
}
@@ -346,23 +347,30 @@
udpc_list = list_create(); /* have a list of running systems */
-add_service(9200, octstr_get_cstr(interface_name)); /* wsp */
-add_service(9201, octstr_get_cstr(interface_name)); /* wsp/wtp */
+ifs = octstr_split(iface, octstr_imm(";"));
+octstr_destroy(iface);
+while (list_len(ifs) > 0) {
+iface = list_extract_first(ifs);
+ info(0, "Adding interface %s", octstr_get_cstr(iface));
+add_service(9200, octstr_get_cstr(iface)); /* wsp */
+add_service(9201, octstr_get_cstr(iface)); /* wsp/wtp */
+
#ifdef HAVE_WTLS_OPENSSL
-if (allow_wtls) {
-add_service(9202, octstr_get_cstr(interface_name));/* wsp/wtls */
-add_service(9203, octstr_get_cstr(interface_name));/* wsp/wtp/wtls */
-}
+if (allow_wtls) {
+ add_service(9202, octstr_get_cstr(iface)); /* wsp/wtls */
+ add_service(9203, octstr_get_cstr(iface)); /* wsp/wtp/wtls */
+}
#else
-if (allow_wtls)
- error(0, "These is a 'wtls' group in configuration, but no WTLS support compiled in!");
+if (allow_wtls)
+ error(0, "These is a 'wtls' group in configuration, but no WTLS support compiled in!");
#endif
/* add_service(9204, octstr_get_cstr(interface_name)); * vcard */
/* add_service(9205, octstr_get_cstr(interface_name)); * vcal */
/* add_service(9206, octstr_get_cstr(interface_name)); * vcard/wtls */
/* add_service(9207, octstr_get_cstr(interface_name)); * vcal/wtls */
-
-octstr_destroy(interface_name);
+octstr_destroy(iface);
+}
+list_destroy(ifs, NULL);
list_add_producer(incoming_wdp);
udp_running = 1;
@@ -377,8 +385,10 @@
int udp_addwdp(Msg *msg)
{
int i;
-Udpc *udpc;
+Udpc *udpc, *def_udpc;
+Octstr *ip;
+def_udpc = NULL;
if (!udp_running) return -1;
assert(msg != NULL);
assert(msg_type(msg) == wdp_datagram);
@@ -388,13 +398,26 @@
for (i=0; i < list_len(udpc_list); i++) {
udpc = list_get(udpc_list, i);
- if (msg->wdp_datagram.source_port == udp_get_port(udpc->addr))
- {
- list_produce(udpc->outgoing_list, msg);
- list_unlock(udpc_list);
- return 0;
+ if (msg->wdp_datagram.source_port == udp_get_port(udpc->addr)) {
+ def_udpc = udpc;
+ip = udp_get_ip(udpc->addr);
+ if (octstr_compare(msg->wdp_datagram.source_address, ip) == 0)
+ {
+octstr_destroy(ip);
+ list_produce(udpc->outgoing_list, msg);
+ list_unlock(udpc_list);
+ return 0;
+ }
+octstr_destroy(ip);
}
}
+
+if (NULL != def_udpc) {
+ list_produce(def_udpc->outgoing_list, msg);
+ list_unlock(udpc_list);
+ return 0;
+}
+
list_unlock(udpc_list);
return -1;
}
pgp0.pgp
Description: signature
Re: Issue with Kannel as a wap gateway
Replying to Oded Arbel: > Please tell me what am I missing Have you tried putting same old version to machine which isn't working now? For those symptoms that you're described (and no more) I will suggest 2 things which can cause such problems: 1. machine (e.g. network) config 2. libraries you're linked your wapbox with. -- Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key This message represents the official view of the voices in my head
Re: Issue with Kannel as a wap gateway
בThursday 06 May 2004 12:37, נכתב על ידי Paul P Komkoff Jr: > Replying to Oded Arbel: > > Please tell me what am I missing > > Have you tried putting same old version to machine which isn't working > now? > > For those symptoms that you're described (and no more) I will suggest > 2 things which can cause such problems: > 1. machine (e.g. network) config Yes - that indeed was the problem. the bearerbox was configured to bind the WDP listener to all interfaces, which included an interface with a few virtual IPs (aliases). the packets from the phone where received on one of these aliases, but the response was sent from the primary (real) interface. the firewall in front of the machine then probably discarded the packet as not belonging to the same connection (its a stateful firewall. I'm not sure that it did that, but the fact was that the response was sent, but never received by the phone). I think that the response should be generated from the same IP the request was made to. -- Oded Arbel m-Wise mobile solutions [EMAIL PROTECTED] +972-9-9611212 (204) +972-54-7340014 ::.. MIPS: Meaningless Indicator of Processor Speed.
Re: Issue with Kannel as a wap gateway
Replying to Oded Arbel: > Yes - that indeed was the problem. the bearerbox was configured to bind the > WDP listener to all interfaces, which included an interface with a few > virtual IPs (aliases). the packets from the phone where received on one of > these aliases, but the response was sent from the primary (real) interface. > the firewall in front of the machine then probably discarded the packet as > not belonging to the same connection (its a stateful firewall. I'm not sure > that it did that, but the fact was that the response was sent, but never > received by the phone). :))) I'v beaten by the issue long time. Some phones working with this setup, some don't. > I think that the response should be generated from the same IP the request was > made to. I have a patch (along with others) which address this issue, and many more. Basically, you put space-separated list of ip addresses in wdp-interfaces statement in .conf, and patched kannel send responces from proper addresses. -- Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key This message represents the official view of the voices in my head
Re: Issue with Kannel as a wap gateway
Paul P Komkoff Jr schrieb: > > Replying to Oded Arbel: > > Yes - that indeed was the problem. the bearerbox was configured to bind the > > WDP listener to all interfaces, which included an interface with a few > > virtual IPs (aliases). the packets from the phone where received on one of > > these aliases, but the response was sent from the primary (real) interface. > > the firewall in front of the machine then probably discarded the packet as > > not belonging to the same connection (its a stateful firewall. I'm not sure > > that it did that, but the fact was that the response was sent, but never > > received by the phone). > > :))) > I'v beaten by the issue long time. Some phones working with this > setup, some don't. > > > I think that the response should be generated from the same IP the request was > > made to. > > I have a patch (along with others) which address this issue, and many > more. > > Basically, you put space-separated list of ip addresses in > wdp-interfaces statement in .conf, and patched kannel send > responces from proper addresses. have you posted the patch to the devel@ list?! If no, please do, so we can review and commit to cvs. Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[EMAIL PROTECTED] http://www.wapme-systems.de/ --- -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.2.2 (Cygwin) mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -END PGP PUBLIC KEY BLOCK-
Re: Issue with Kannel as a wap gateway
Replying to Stipe Tolj:
> have you posted the patch to the devel@ list?! If no, please do, so we
> can review and commit to cvs.
Stipe!
For a long time I'm only posting and posting patches to devel list,
and noone paying attention to it.
attached split-up of bb_udp only change, which should do multiple wdp
interfaces trick.
--
Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key
This message represents the official view of the voices in my head
--- ../gateway/gw/bb_udp.c 2004-01-22 17:08:24.0 +0300
+++ am3/gw/bb_udp.c 2004-05-06 13:42:36.608966019 +0400
@@ -324,6 +324,8 @@
{
Octstr *interface_name;
CfgGroup *grp;
+Octstr *Ifaces;
+char* cIf;
int allow_wtls;
if (udp_running) return -1;
@@ -346,13 +348,18 @@
udpc_list = list_create(); /* have a list of running systems */
-add_service(9200, octstr_get_cstr(interface_name)); /* wsp */
-add_service(9201, octstr_get_cstr(interface_name)); /* wsp/wtp */
+Ifaces = octstr_duplicate(interface_name);
+cIf = strtok(octstr_get_cstr(Ifaces), " ,;");
+while (cIf != NULL) {
+ info(0, "Adding interface %s", cIf);
+add_service(9200, cIf); /* wsp */
+add_service(9201, cIf); /* wsp/wtp */
+
#ifdef HAVE_WTLS_OPENSSL
-if (allow_wtls) {
-add_service(9202, octstr_get_cstr(interface_name));/* wsp/wtls */
-add_service(9203, octstr_get_cstr(interface_name));/* wsp/wtp/wtls */
-}
+if (allow_wtls) {
+ add_service(9202, cIf);/* wsp/wtls*/
+ add_service(9203, cIf);/* wsp/wtp/wtls */
+}
#else
if (allow_wtls)
error(0, "These is a 'wtls' group in configuration, but no WTLS support
compiled in!");
@@ -361,6 +368,9 @@
/* add_service(9205, octstr_get_cstr(interface_name)); * vcal */
/* add_service(9206, octstr_get_cstr(interface_name)); * vcard/wtls */
/* add_service(9207, octstr_get_cstr(interface_name)); * vcal/wtls*/
+cIf = strtok(NULL, " ,;");
+}
+octstr_destroy(Ifaces);
octstr_destroy(interface_name);
@@ -377,8 +387,10 @@
int udp_addwdp(Msg *msg)
{
int i;
-Udpc *udpc;
+Udpc *udpc, *def_udpc;
+Octstr *ip;
+def_udpc = NULL;
if (!udp_running) return -1;
assert(msg != NULL);
assert(msg_type(msg) == wdp_datagram);
@@ -388,13 +400,26 @@
for (i=0; i < list_len(udpc_list); i++) {
udpc = list_get(udpc_list, i);
- if (msg->wdp_datagram.source_port == udp_get_port(udpc->addr))
- {
- list_produce(udpc->outgoing_list, msg);
- list_unlock(udpc_list);
- return 0;
+ if (msg->wdp_datagram.source_port == udp_get_port(udpc->addr)) {
+ def_udpc = udpc;
+ip = udp_get_ip(udpc->addr);
+ if (octstr_compare(msg->wdp_datagram.source_address, ip) == 0)
+ {
+octstr_destroy(ip);
+ list_produce(udpc->outgoing_list, msg);
+ list_unlock(udpc_list);
+ return 0;
+ }
+octstr_destroy(ip);
}
}
+
+if (NULL != def_udpc) {
+ list_produce(def_udpc->outgoing_list, msg);
+ list_unlock(udpc_list);
+ return 0;
+}
+
list_unlock(udpc_list);
return -1;
}
Re: Issue with Kannel as a wap gateway
Replying to Paul P Komkoff Jr: > For a long time I'm only posting and posting patches to devel list, > and noone paying attention to it. So another patch with the same result. It seems that no one will ever accept anything I am doing here. And it will be silly to think that anyone WANT it. Except me. -- Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key This message represents the official view of the voices in my head
Re: Issue with Kannel as a wap gateway
Paul P Komkoff Jr writes: > Replying to Paul P Komkoff Jr: > > For a long time I'm only posting and posting patches to devel list, > > and noone paying attention to it. > > So another patch with the same result. Well leave them more than 3 hours to pay attention :) > It seems that no one will ever accept anything I am doing here. And it > will be silly to think that anyone WANT it. It seems obvious to me, even if I'm very new on this list, that they don't have much time for reviewing/merging/accepting patches. Only Alexander seems to do it from time to time, but only to small patches, as far as I can see. And he can't be specialist of all parts of kannel anyway.. I myself have one rather large documentation patch and one patch to fakesmsc that haven't been answered to. Hopefully, their acceptance are not critical to us. However, I'm going to add dbpool support to the sdb database driver, peer reviewing would be more important there, I hope it'll be possible.. Well, anyway. -- Guillaume Cottenceau
Re: Issue with Kannel as a wap gateway
Hi All, I'm sorry not be able (at the moment) todo anything (or better to say, limited amount of time), because I'm too busy at work right now and at home have no Inet access yet. Only I can say: Kannel Developer, where are you??? For all who contribute to project: It's very appriciated, what are you doing! and please fill bug reports for your patches, so we will not lose it... Sorry, real life :( On Thursday 06 May 2004 17:28, Guillaume Cottenceau wrote: > Paul P Komkoff Jr writes: > > Replying to Paul P Komkoff Jr: > > > For a long time I'm only posting and posting patches to devel list, > > > and noone paying attention to it. > > > > So another patch with the same result. > > Well leave them more than 3 hours to pay attention :) > > > It seems that no one will ever accept anything I am doing here. And it > > will be silly to think that anyone WANT it. > > It seems obvious to me, even if I'm very new on this list, that > they don't have much time for reviewing/merging/accepting > patches. Only Alexander seems to do it from time to time, but > only to small patches, as far as I can see. And he can't be > specialist of all parts of kannel anyway.. I myself have one > rather large documentation patch and one patch to fakesmsc that > haven't been answered to. Hopefully, their acceptance are not > critical to us. However, I'm going to add dbpool support to the > sdb database driver, peer reviewing would be more important > there, I hope it'll be possible.. Well, anyway. -- Best regards / Mit besten Grüßen aus Düsseldorf Dipl.-Ing. Alexander Malysh ___ Centrium GmbH Vogelsanger Weg 80 40470 Düsseldorf Fon: +49 (0211) 74 84 51 80 Fax: +49 (0211) 277 49 109 email: [EMAIL PROTECTED] web: www.centrium.de msn: [EMAIL PROTECTED] icq: 98063111 ___ Please avoid sending me Word, Excel or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
Re: Issue with Kannel as a wap gateway
Replying to Guillaume Cottenceau:
> It seems obvious to me, even if I'm very new on this list, that
> they don't have much time for reviewing/merging/accepting
> patches. Only Alexander seems to do it from time to time, but
> only to small patches, as far as I can see. And he can't be
> specialist of all parts of kannel anyway.. I myself have one
> rather large documentation patch and one patch to fakesmsc that
> haven't been answered to. Hopefully, their acceptance are not
> critical to us. However, I'm going to add dbpool support to the
> sdb database driver, peer reviewing would be more important
> there, I hope it'll be possible.. Well, anyway.
I just was very upset, sorry, too much trouble here.
I'm tired of posting same thing again and again. For the first look,
maybe it seems not so important.
But when patch loss leads to problems being shown up (which can easily
be avoided) it is not good.
Of course, it's just from my point of view. I've ran with many
problems with many software, open-source and proprietary. I'm always
trying to fix things myself - but such fixing often done in emergency,
"aargh this thing is not working! panic! catastrophe!"
When the fix is already available, it is the one of the worst things
we can do - to hide it from community.
(Again, I'm not offering you another crazy systems - I'm just trying
to solve real problems I'm running in as csd-wap gateway admin in gsm
company ...)
.
I'm tired of splitting my work in pieces and maintaining it at a whole
thing. If you are interested in any features I am explaining here and
want to participate but for any reason you are afraid of changes -
maybe together we will solve this problems. Maybe overall quality of
product will be improved, and (while wap 2 will not over-take wap 1)
more companies will consider use of kannel, with commercial support or
not.
All I can do for it is designing and writing code, not so much ...
P.S. Somebody can reply to me here "don't use development versions of
open-cource, not certified by ${VENDOR} software in production". I
will leave disproof of this concept to reader's exercise.
--
Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key
This message represents the official view of the voices in my head
Re: Issue with Kannel as a wap gateway
Replying to Alexander Malysh: > Hi Paul, > > I personally don't like strXX functions family if I can avoid this :) > Please check attached patch and if it ok then I will commit it to cvs... I am sick now, so cannot really test it but I think it's ok :) > Btw. would you care for userguide patch, due to config option change? Will do in a couple of days ... -- Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key This message represents the official view of the voices in my head
Re: Issue with Kannel as a wap gateway
Hi, patch commited to cvs. Thanks a lot! P.S. please don't forget userguide patch :) On Friday 14 May 2004 09:05, Paul P Komkoff Jr wrote: > Replying to Alexander Malysh: > > Hi Paul, > > > > I personally don't like strXX functions family if I can avoid this :) > > Please check attached patch and if it ok then I will commit it to cvs... > > I am sick now, so cannot really test it but I think it's ok :) > > > Btw. would you care for userguide patch, due to config option change? > > Will do in a couple of days ... -- Best regards / Mit besten Grüßen aus Düsseldorf Dipl.-Ing. Alexander Malysh ___ Centrium GmbH Vogelsanger Weg 80 40470 Düsseldorf Fon: +49 (0211) 74 84 51 80 Fax: +49 (0211) 277 49 109 email: a.malysh (at) centrium.de web: www.centrium.de msn: a.malysh (at) centrium.de icq: 98063111 ___ Please avoid sending me Word, Excel or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html pgpkUveF5s75e.pgp Description: signature
