Re: The Destroyer picture message
Hello Ahmed, [EMAIL PROTECTED] wrote: sorry for answering on the wrong subject, here is the problem we face we have a problem when sending picture message to nokia 6100 using kannel and smpp connection it cause a full damage to the mobile it never start only flashing the software again to the mobile can solve it any one have faced this problem sounds like a serious problem. In any way it's seems like a design failure of the nokia device, since the client software should be aware that wrong encoded messages may be coming, and hence should silently discard them. Can you forward us the bearerbox.log with the specific smpp debug output for review? Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 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: Two bugs that can be closed?
Arne K. Haaje wrote: If these bugs apply to CIMD2 (no category for it in Mantis) and not CIMD then at least # 56 can be closed. closed. I also think # 94 can be closed. I can not duplicate it. resolved to unable to duplicate. Arne, I have changed your Mantis account from reporter to developer, so you're now able to resolve bugs actively on your own ;) Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 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: Problems compiling kannel 1.2.1 - libxml2
Andrew Chong wrote: After spending the last 3 days trying to make someone else's RPM binary of Kannel work, I have given up and am now trying to install via compiling from the source (gateway-1.2.1.tar.gz) first of all: 1.2.1 stable is outdated. For the most best experience ;) switch to the cvs head version, which will be tagged shorty as 1.3.2 devel. Clean install of RedHat AS 2.1 Succcessful install of gcc off the RedHat CD's: kernel-headers-2.4.9-e.3 glibc-devel-2.2.4-26 cpp-2.96-108.1 binutils-2.11.90.0.8-12 gcc-2.96-108.1 confirmed libxml2-2.4.19-2 is installed. Do I need to update libxml2, or glibc (assuming that is where pthread support comes from) If so to what versions? Kannel's configure seems to be unable to find xml2-config in the $PATH. Hence it assumes it is not available on the system. Check where the xml2-config bash script is available and add the path temporary to the $PATH, re-configure and you should be fine. Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 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: [patch] error in smsc_at.c in communication with nokia gsm modems
Wilfried Goesgens wrote:
in at2_check_sms_memory kannel tries to evaluate the number of sms the modem
is able to receive into its memory by reading the size of the storage.
something like
which type of modems do you refer on this?
at+cpms?
... ME ,77,170 ...
would be a correct reply. but i found that some of our modems just return
... ME ,77,0 ...
which makes kannel asume, the modem is able to hold zero messages in memory.
so it says: 77 messages waiting in memory and starts the memory read
function.
there it loops reading memory-slots until the number of sms successfuly read
is
equal to the number of sms waiting in memory, or the last slot of the modem
has passed.
As of kannel asumes, that there are 0 slots, it won't loop at all.
so i just did the hack to compare the number of sms'es to be read and the
assumed memory units.
if nSMS storagesize, storagesize is wrong. To reach the end, i used n-sms
+20. The clean way
would be to have it optionally configured, and warn in syslog, if it's not
configured, and
kannel find a zero...
the first part is a check if the pointer exists, which i found crashing it
in some case it being zero.
the middle part is retrying to delete an sms, if it fails.
cvs diff smsc_at.c
Index: smsc_at.c
===
RCS file: /home/cvs/gateway/gw/smsc/smsc_at.c,v
retrieving revision 1.13
diff -r1.13 smsc_at.c
156c156
if (privdata-modem-need_sleep)
---
if (privdata-modemprivdata-modem-need_sleep)
415a416
417a419,420
at2_send_modem_command(privdata, AT S7=45 S0=0 L1 V1 X4 c1 E1 Q, 0, 0);
sleep(1);
is this AT command device specific? If yes, you'll need to ensure you
don't pass it generically to any type of modem.
743a747,755
if (at2_send_modem_command(privdata, cmd, 20, 0) != 0) {
/*
* failed to delete the message, we'll just ignore it for
now,
* this is bad, since if the message really didn't get
deleted
* we'll see it next time around.
*/
error(2, AT2[%s]: REALY failed to delete message %d.,
octstr_get_cstr(privdata-name), message_number);
}
937c949,951
---
/* did the modem tell us the truth about its capacity?
if not use current number of sms+20*/
if (values[0]values[1]) values[1]=values[0]+20;
otherwise I'm +0 in commiting this.
Any other opinions, objections, votes please. ?
Stipe
mailto:[EMAIL PROTECTED]
---
Wapme Systems AG
Vogelsanger Weg 80
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: smsc = http, system-type = kannel
Rene Kluwen schrieb:
Does anybody ever use this SMSC? Has it been tested? Is it reliable?
I got two big issues here. One is:
(from the log)
Parsing URL
`http://mexico.XXX.com:13004/?username=XXXpassword=XXXto=31651931985text=
Test+http+%231from=31651931985coding=0account=XXX:kluwensmsc=SMPPCONN04
dlr-url=http%3A%2F%2Fmexico.kluwen.com%2F~rene%2Fdlr.php%3Ftype%3D%25d%26id%
3D315drl-mask=31'
As you can see, dlr-mask is spelt the wrong way (drl-mask).
correct, this is a stupid typo. commited the following to cvs:
RCS file: /home/cvs/gateway/gw/smsc/smsc_http.c,v
retrieving revision 1.34
diff -u -r1.34 smsc_http.c
--- gw/smsc/smsc_http.c 22 Jan 2004 13:26:04 - 1.34
+++ gw/smsc/smsc_http.c 29 Jun 2004 14:20:23 -
@@ -362,11 +362,10 @@
if (sms-sms.smsc_id) /* proxy the smsc-id to the next instance
*/
octstr_format_append(url, smsc=%S, sms-sms.smsc_id);
if (sms-sms.dlr_url) {
-octstr_url_encode(sms-sms.dlr_url);
-octstr_format_append(url, dlr-url=%S, sms-sms.dlr_url);
+octstr_format_append(url, dlr-url=%E, sms-sms.dlr_url);
}
if (sms-sms.dlr_mask != DLR_UNDEFINED sms-sms.dlr_mask !=
DLR_NOTHING)
-octstr_format_append(url, drl-mask=%d, sms-sms.dlr_mask);
+octstr_format_append(url, dlr-mask=%d, sms-sms.dlr_mask);
headers = list_create();
debug(smsc.http.kannel, 0, HTTP[%s]: Start request,
Another thing is that when trying to do the gateway DLR, I get:
(from the log)
URL
http%3A%2F%2Fmexico.kluwen.com%2F~rene%2Fdlr.php%3Ftype%3D%25d%26id%3D320
doesn't
start with `http://' nor `https://'
??? hmmm, we need to urlencode the DLR-URL within the HTTP call from
smsc_http to smsbox, right? smsbox should be then requierd to
urldecode the string back again for further processing, right?
from which log does this come?
Stipe
mailto:[EMAIL PROTECTED]
---
Wapme Systems AG
Vogelsanger Weg 80
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-
[FYI] cvs head needs cygwin 1.5.9 (or higher)
Just to let those know who run or develop on the cygwin plattform: Alex's recent changed introduce calls to 'sem_getvalue' which is not available on cygwin 1.5.5, but _is_ available on cygwin 1.5.9 (and higher). So please upgrade in case you use an older cygwin layer on your machines. Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 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: [ANN|RFC] Kannel 1.3.2rc1 devel tarball available
ok, looks good. I'll need to resolve at least the last bug report with %P url escape code and try to reproduce. If this is reproducable, we'll need to fix before we roll the tarball. There is also an issue with quotes within parameters values of WSP headers. Aiming to roll the tarball today. Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 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: Fw: WapPush delivery problem
Yury Mikhienko wrote: I tried to use the Openwave Wap Push library for push SI over kannel PPG. Push message was accepted by kannel PPG and sent (and delevered) to a mobile phone (NOKIA 7650) successfully, but I did not get a SI on the phone incoming messages . May be the mobile does not understand it, but if I try to push default kannel test WapPush - it works just fine with me. Can anyone help me to solve this problem? kannel logs: -- FOR OPENWAVE WapPush - 2004-07-07 09:43:28 [392] [6] DEBUG: esm_class: 67 = 0x0043 2004-07-07 09:43:28 [392] [6] DEBUG: protocol_id: 0 = 0x 2004-07-07 09:43:28 [392] [6] DEBUG: priority_flag: 0 = 0x 2004-07-07 09:43:28 [392] [6] DEBUG: schedule_delivery_time: NULL 2004-07-07 09:43:28 [392] [6] DEBUG: validity_period: 040708094328016+ 2004-07-07 09:43:28 [392] [6] DEBUG: registered_delivery: 0 = 0x 2004-07-07 09:43:28 [392] [6] DEBUG: replace_if_present_flag: 0 = 0x 2004-07-07 09:43:28 [392] [6] DEBUG: data_coding: 4 = 0x0004 2004-07-07 09:43:28 [392] [6] DEBUG: sm_default_msg_id: 0 = 0x 2004-07-07 09:43:28 [392] [6] DEBUG: sm_length: 122 = 0x007a 2004-07-07 09:43:28 [392] [6] DEBUG: short_message: 2004-07-07 09:43:28 [392] [6] DEBUG:Octet string at 0x8195698: 2004-07-07 09:43:28 [392] [6] DEBUG: len: 122 2004-07-07 09:43:28 [392] [6] DEBUG: size: 1024 2004-07-07 09:43:28 [392] [6] DEBUG: immutable: 0 2004-07-07 09:43:28 [392] [6] DEBUG: data: 06 05 04 0b 84 23 f0 00 06 32 ae a9 4f 70 65 6e .#...2..Open 2004-07-07 09:43:28 [392] [6] DEBUG: data: 77 61 76 65 20 57 41 50 20 50 75 73 68 20 4c 69 wave WAP Push Li 2004-07-07 09:43:28 [392] [6] DEBUG: data: 62 72 61 72 79 2c 20 4a 61 76 61 20 45 64 69 74 brary, Java Edit 2004-07-07 09:43:28 [392] [6] DEBUG: data: 69 6f 6e 20 31 2e 35 00 8d be c3 93 02 05 6a 00 ion 1.5...j. 2004-07-07 09:43:28 [392] [6] DEBUG: data: 45 c6 0c 03 77 61 70 2e 6d 6f 62 69 63 6f 6d 6b E...wap.mobicomk 2004-07-07 09:43:28 [392] [6] DEBUG: data: 2e 72 75 00 0a c3 07 20 04 06 07 09 42 36 10 c3 .ru B6.. 2004-07-07 09:43:28 [392] [6] DEBUG: data: 07 20 04 06 08 09 42 36 01 03 64 6f 77 6e 6c 6f . B6..downlo 2004-07-07 09:43:28 [392] [6] DEBUG: data: 61 64 20 6c 69 6e 6b 00 01 01 ad link... 2004-07-07 09:43:28 [392] [6] DEBUG:Octet string dump ends. 2004-07-07 09:43:28 [392] [6] DEBUG: SMPP PDU dump ends. 2004-07-07 09:43:28 [392] [6] DEBUG: SMPP[SMPP_TR]: Got PDU: 2004-07-07 09:43:28 [392] [6] DEBUG: SMPP PDU 0x8195590 dump: 2004-07-07 09:43:28 [392] [6] DEBUG: type_name: submit_sm_resp 2004-07-07 09:43:28 [392] [6] DEBUG: command_id: 2147483652 = 0x8004 2004-07-07 09:43:28 [392] [6] DEBUG: command_status: 0 = 0x 2004-07-07 09:43:28 [392] [6] DEBUG: sequence_number: 36 = 0x0024 2004-07-07 09:43:28 [392] [6] DEBUG: message_id: 225AAF4D 2004-07-07 09:43:28 [392] [6] DEBUG: SMPP PDU dump ends. ... - FOR KANNEL TEST_PPG WapPush -- 2004-07-07 10:40:25 [392] [6] DEBUG: esm_class: 67 = 0x0043 2004-07-07 10:40:25 [392] [6] DEBUG: protocol_id: 0 = 0x 2004-07-07 10:40:25 [392] [6] DEBUG: priority_flag: 0 = 0x 2004-07-07 10:40:25 [392] [6] DEBUG: schedule_delivery_time: NULL 2004-07-07 10:40:25 [392] [6] DEBUG: validity_period: 040708104025016+ 2004-07-07 10:40:25 [392] [6] DEBUG: registered_delivery: 0 = 0x 2004-07-07 10:40:25 [392] [6] DEBUG: replace_if_present_flag: 0 = 0x 2004-07-07 10:40:25 [392] [6] DEBUG: data_coding: 4 = 0x0004 2004-07-07 10:40:25 [392] [6] DEBUG: sm_default_msg_id: 0 = 0x 2004-07-07 10:40:25 [392] [6] DEBUG: sm_length: 78 = 0x004e 2004-07-07 10:40:25 [392] [6] DEBUG: short_message: 2004-07-07 10:40:25 [392] [6] DEBUG:Octet string at 0x81956e0: 2004-07-07 10:40:25 [392] [6] DEBUG: len: 78 2004-07-07 10:40:25 [392] [6] DEBUG: size: 1024 2004-07-07 10:40:25 [392] [6] DEBUG: immutable: 0 2004-07-07 10:40:25 [392] [6] DEBUG: data: 06 05 04 0b 84 23 f0 01 06 05 ae 8d bf c3 93 02 .#.. 2004-07-07 10:40:25 [392] [6] DEBUG: data: 05 6a 00 45 c6 0c 03 77 61 70 2e 69 6f 62 6f 78 .j.E...wap.iobox 2004-07-07 10:40:25 [392] [6] DEBUG: data: 2e 63 6f 6d 00 0a c3 05 20 03 05 07 14 10 c3 04 .com ... 2004-07-07 10:40:25 [392] [6] DEBUG: data: 20 04 09 08 01 03 57 61 6e 74 20 74 6f 20 74 65.Want to te 2004-07-07 10:40:25 [392] [6] DEBUG: data: 73 74 20 61 20 66 65 74 63 68 3f 00 01 01 st a fetch?... 2004-07-07 10:40:25 [392] [6] DEBUG:Octet string dump ends. 2004-07-07 10:40:25 [392] [6] DEBUG: SMPP PDU dump ends. 2004-07-07 10:40:25 [392] [6] DEBUG: SMPP[SMPP_TR]: Got PDU: 2004-07-07
Re: [FYI] cvs currently throws: internal error
James just fixed the corrupted file in cvs root. Applause to James please! ;) Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 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: SMPP Server
Alexei Pashkovsky wrote: I've modified the smsc_smpp module to behave as smpp server. Modifications were done on CVS dated about 2 weeks ago. At the moment it seems to work smooth, but probably more features should be added, also I believe there're memory leaks. Authentication done using mysql database. At the moment it simply allows users to connect with SMPP gateway and send messages thru, after receiving the message from smpp, it matches user/pass from DB and resends the sms with Kannel HTTP query to the gateway. Middle layer can serve as billing system as well. To simplify the whole thing, the smsbox is not being used. The original Kannel functionality is kept, while the smsc driver is called smpp2, and can be activated from config file if needed. Is there any interest on adding this to Kannel CVS ? definetly! +1 is reviewing this. Please send the patch in 'diff -u' format to the list or directly. Stipe P.S. at the moment we supply this solution to some of our customers, but I'm willing to share the source so someone can help me in bugtracing :) BTW, our smppbox is currently also to be most likely to enter the Kannel CVS as seperate module. Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 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: [Kannel-Users] Re: mBlox SMPP optional parameters
Ian Cass wrote: Nisan Bloch wrote: As for publishing with SMPP.org and hoping that the aggregators and operators will fall in line - mm I doubt it :-) - look at the variation in deliver_sm dlr text formats, look at the various non standard uses of smpp params But look at how ambiguous SMPP is! You can hardly blame them. Besides, if everyone did everything standard, companies like us wouldn't exist. That's true in some sense. But we (as enforcement of open software) should propagate standards, and SMPP should be obeyed as one. (my 2ct) Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 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: mmsbox
Forgot another _crucial_ thing! How does the phone get to your MMSC HTTP server (mmsbox). Via public (GPRS) or private (dial-in) IP connectivity? Why I'm asking this is simple. Phones do _not_ include their own MSISDN into the From: header that is in the MMS Encap PDUs. The MMS clients are not aware (technically spoken) what their MSISDN is. Hence they put the put address in here tag into that From: header. It's then up to the MMSC to know the MSISDN of that HTTP request. Here comes the MSISDN provisioning concept into play. Your WAP GW (Kannel?) should forward the MSISDN number via designated HTTP header (see gw/wap-appl.c code) to the MMSC. Hence wapbox needs to run with RADIOUS accounting proxy thread to grap the MSISDN from the NAS (network access server) via RADIUS acct packts. If you run this over the public network (GPRS), it's obvious that they won't provide you the RADIUS acct packets and hence you will be unable to see the MSISDN of the client that you currently have IP traffic with. Just some more cents to the big MMSC story. (I should write a damn concept paper on this and make it to my master thesis at Berkeley ;) Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 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: AW: mmsbox
Pommnitz, Jörg schrieb: I think MMS will require a working SAR implementation. MMS messages can easily exceed 64KB. So, some work on the WAP side of things will be necessary. SAR is available in Kannel. The only thing not yet present is ESAR (extended SAR) for messages beyond 256KB. Our MMSC beast runs with the standard wapbox and _does_ transport messages with sizes of 150-180KB. Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 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: mmsbox
Dziugas Baltrunas wrote: Hi, Stipe, Forgot another _crucial_ thing! What about the content adaptation functionality? It seems that every new mobile device today provides new screen size, accepted formats and so on. Basicly there are several different tasks MMSC should be aware of when delivering the MMS message using MM1: * If the phone doesn't support the original image, convert it to the supported one (according to the phone capabilities), if possible; correct. While content adaption should actualy been made unnecessary in the MMS world, this is still something to beware of. And in cases SDU sizes can't be read by devices or specific multipart entities are our of accept scope, those should be dropped, or converted. That's correct. * If the image (in the SMIL slide) is larger than a maximum screen size of the phone, resize it; this depends on it. Actually the MMSC can also relly on the phone to resize it to the specific screen size. It's up to the device usually. But some devices maybe dumb in that way, that they don't have the capability to resize on their own and rather drop the image display. In such cases, yes, it would be up to the MMSC. But that's again a tricky thing to distinguish. * If the phone doesn't support the original sound, convert it to the supported one (often to the AMR format) Ok, again correct (of course ;) This is all a question of legacy format support etc. It's obvious that all these tasks will require depedency with additional graphic and audio libraries, because, for example, writing WAV - AMR converter from stratch would be a suicide :) (3GPP provides a huge C API for that). correct. We would use external libs for these aims. It's not up to Kannel to handle it internally in it's code. The worst thing is that the content adaptation task can't be separated from MMSC as it's the only entity receiving the User Agent Profile (UAProf) or at least Accept headers. Shall we think about the adapter submodule of the mmsbox? what do you mean with adapter submodule? A module that transcodes the MMS on-the-fly, based on the user-agent and UAProf? Yes, this makes sense to me. Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 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-
[ANNOUNCE] Kannel 1.3.2 development release available
status and connect_time while set in various threads, optional parameters handling improved. * CIMD2 fixed for CPU load consume while idle, wrong time for messages, wrong parameter length for service description field. * AT fixed panic if UDHI in PDU is set but user data length = 0, bug in non-blocking write to modem device, few race conditions. * HTTP SMSC fixed a number of bugs. Including bearerbox crash if smsc-id is stopped and /status page is called, don't 'fail' a MT message when the HTTP server can not be triggered, instead use 'reconnect-delay' to try again, expected MO parameters to 'username' and 'password' instead of 'user' and 'pass'. * SSL fixed a serious pthread_mutex bug for call-back function to the openssl thread locking, non-blocking write mode, memory leak in SSL handshake sequence, various improvements. * Fixed generic alt_dcs re-coding misbehaviour. * HTTP fixed basic auth problem with the passwd, redirecting, serious bug in the HTTP client code causing smsbox to crash if the connection is closed directly by the HTTP server. * Fixed bearerbox behaviour while receiving SIGHUP (restart) signal, signal handling that may have caused deadlock. * Fixed ACK/NACK handling beween bearerbox and smsbox. * WAP fixed and improved XML charset encoding handling, WSP header 'Encoding-Version' handling, HTTP referer header removed due to breaking specific WAP Forum certification tests, various fixes in WML compiler character encoding handling, DOS bug within WML compiler, possible segfault if WML document doesn't contain DTD section, crashing wapbox while comparing empty cookie strings, various memory leaks, WTP bug for abort PDU in speficic timeout events, fixed variable substitution within WML compiler. * WAP Push fixed malformed xml reponses for the PAP document, none accepted pap attribute 'product-name', case insesitive handling of constants WAPPUSH and TYPE for sake of interopertibility with existing PIs, handling of Push flag, PPG specifier and prologue parsing to support other PIs, including delimiter parsing, PAP MIME parsing, various memory leaks. * Fixed partially panics caused by too long UDH sequences. * DLR smsc-id is added now to DLR MOs from the temporary DB tablespace. * Queue policies have been improved for internal bearerbox to smsbox message transmission. * Fixed race conditions within store-file handling. * Fixed serious poll() handling of POLLHUP and POLLERR. * Fixed bug that config directive 'sendsms-chars' was not used at all in the logic, only the default remained. * Fixed bug in smsbox that crashed if %A is used in get-url. -- i.r. Stipe Tolj mailto:[EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[EMAIL PROTECTED] http://www.wapme-systems.de/ ---
Re: SMPP implementation bug?
Oscar Medina Duarte schrieb: Hi all ! I think a have a small bug here, when an smsc sends a DeliverSM pdu to the gateway, with the fields, source_adde and destination_addr set to NULL, the bearerbox crashes with the following logs: 2004-07-16 18:39:20 [15969] [6] PANIC: gwlib/octstr.c:2326: seems_valid_real: Assertion `ostr != NULL' failed. (Called from gwlib/octstr.c:807:octstr_check_range.) 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox(gw_panic+0x175) [0x80c8501] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox [0x80ce67f] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox(octstr_check_range+0x26) [0x80caaa3] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox [0x807fecb] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox [0x8081e9f] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox [0x8082da9] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox [0x80be000] 2004-07-16 18:39:20 [15969] [6] PANIC: /lib/tls/libpthread.so.0 [0x86879c] 2004-07-16 18:39:20 [15969] [6] PANIC: /lib/tls/libc.so.6(__clone+0x5a) [0x6b527a] ok, confirmed... by reviewing code. Just checked the specs, it indicates the following for deliver_sm PDU: source_addr may be NULL if unknown destination_addr doesn't state if if may be NULLed, hence it may be, right? In any case, you are right. Kannel shouldn't panic here. Adding this into mantis bug tracking. Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 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: Is 1.3.2 stable enough to call it 1.2.2 ?
Alexander Malysh wrote:
Hello Bruno,
1.3.2 should be good tested and remaining bug's should be fixed first before
we can call it stable (IMO) and cvs version (before 1.3.2) was not tested
by too much people, so we should wait a bit...
P.S. why not package 1.3.2 for debian and get it more testing?
Bruno Rodrigues wrote:
Hello all.
Does anyone have any complain about 1.3.2 in comparison with 1.2.1 ?
What do you think about releasing 1.3.2 as 1.2.2 stable so I can package
it for Debian and we could have the latest stable version in Sarge ?
Stipe ?
I'd like to go for the 1.4 stable branch, rather then having this
major step under 1.2.
This is historically also been made for 1.3 devel branch.
So, I'd like to see 1.4.0 stable rolled in about a week, to give
people time to identify any remaining open issues and get the issues
out of the BTS too.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: Is 1.3.2 stable enough to call it 1.2.2 ?
Pedro B. wrote:
Bruno said he had to do the pack before August 13th.
I swear i looked at the calendar just now and appeared to me that 1 week
from now is past August 13th.
now, to make things more easy, we can roll it even earlier. I'll have
to catch-up with the list and mantis, since I was sort of
unavailable the last 1-2 weeks due to other issues.
When we are green for release, we will roll 1.4.0 stable then. So
Bruno will be able to package it for Debian. ;)
@Bruno: is this a good offer?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: send-url for HTTP-based relay in 1.3.1
Peter Beckman wrote:
Folks -- Having a little problem with kannel and binary messages sent via
HTTP.
Right now, I can't seem to successfully convert the text passed by kannel
via an HTTP relay connection back to the hex encoded string.
The original:
UDH: 0B050415810003010301
Txt:
024A3A61A5B991858DB1D5880400D522CAEB2CD49082CAB12418400410B2AD49082CB312408B26D49082CAB12408B2CD49082CAB12418400410B2AD4
What I get from Kannel:
[from] = #
[to] = 1##
[text] = J:a\0\,[EMAIL PROTECTED],[EMAIL
PROTECTED]$I,A\0A *
[smsc] = http
[coding] = 2
[udh] = \0\0\0
[textbin] = %b
[worthless] = nothing?username=nada
[password] = nada
I have a function that gets it close (taking each character and trying to
convert it to its binary then hex format, taking in account \0 is a null),
but not exact.
This is as close as I get:
[udh] = 0B05040F510003010301
OrigUDH: 0B050415810003010301
[text] =
0204033D5B550858040002005A52181228040A310802000C28081A005A521808310802000C29540029000200
OrigTxt:
024A3A61A5B991858DB1D5880400D522CAEB2CD49082CAB12418400410B2AD49082CB312408B26D49082CAB12408B2CD49082CAB12418400410B2AD4
Any suggestions? Here's my function that I use to parse:
Hi Peter,
first of all, please _do NOT_ crosspost to mailing lists. We consider
this abuse. ;)
Ok, now regarding the question itself. Unfortunatly it's a bit to
unspecified in terms of what szenario you are trying to solve. Could
you please outline a bit more in details what you are trying to do?!
At least I didn't get the point... or am I missing the obvious? ;)
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Dsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: [OT] WAP emulator for Linux
Arne K. Haaje wrote:
This is very off topic, but does anyone know of a decent WAP emulator for
Linux?
I have been using Deckit, but it is getting a bit long in the tooth.
there is such a beast living at http://www.yospace.com/ which is very
good IMO. (includes the orginal firmware look and feel of devices)
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: Is 1.3.2 stable enough to call it 1.2.2 ?
Pedro B. wrote:
Can this aspell version replace the www docs too?
yep, I'll hit it towards the htdocs dir ;)
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: Using regex
Oscar Medina Duarte wrote:
Hello my kannel e-friends !
I'm doing some testing on kannel 1.3.2 in order to put it to deploy
services in the real world, but, I have a doubt, I want to use
keyword-regex to differentiate two (and more) services, because, the
messages arrive from my Operator with a prefix, lets say pm4s, so if I
have 2 services, one named puebla and the other cholula, the request to
those would be something like :
pm4s puebla
and
pm4s cholula
I tried this on kannel:
8---
group = sms-service
keyword = pm4s
keyword-regex = ^(pm4s)[ ]+(puebla)
text = de bolas
catch-all = true
group = sms-service
keyword = pm4s
keyword-regex = ^(pm4s)[ ]+(cholula)
get-url = http://%S;
8-
But only puebla service is recognized, even if I send a pm4s message the
puebla service is triggered.
I tought that was because both have keyword = pm4s, so I tried without
the keyword config, but smsbox wouldnt start.
Could be a good idea to base a service in a keyword-regex or a keyword
and not necessarily both, that would be a nice feature!
Cheers !
== Oscar
OM MANI PEME HUM
now, obiously you are mis-using the 'keyword' directive here, IMO.
Because you have in both(!) groups the 'keyword = pm4s', this will
cause smsbox to catch always the first group, which is exactly the
behaviour that you are experiencing.
I guess you have to leavce away(/comment out) the 'keyword = pm4s'
from both(!) blocks.
Correct list?
AND ONCE AGAIN TO EVERYONE: DO _NOT_ CROSSPOST TO LISTS!
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: WARNING: SMPP: PDU element password to long (length is 9, should be 9)
Pedro B. wrote:
Let alone the fact that too long is not spelled correctly. At least in
10 locations of the code. and i only checked 4 .c files.
as I said. Patches in 'diff -u' format always welcome ;) So if you
spott something, send in a patch and we'll apply it.
I'm sorry for what i'm about to say, but it's a proven fact:
There is a vast amount of misspelling in both the old docs (that Stipe
aspelled, good stuff), and throughout all the code comments that shade a
very strong lack of credibility to Kannel.
now, Kannel was never been an US project. Finish people started it and
several other european citizen have continued it. Speaking of personal
implications: I'm a croatian citizen, born and living in Germany,
working on a finish project ;)
Everyone can make a typo, but if Kannel is really an english-based
product, there should be at least some being-elementary-school level of
spelling on all the code.
isn't it?
The english is not my mother language is a feeble and worn out excuse
for a development team that (all except Bruno, according to the first
lines of the docs) is made of ceo's, directors, chiefs and the rest of
the upper class management positions plethora.
now, Bruno is also in a remarkable position at a very large operator
(with a red logo in it). He may only be to shy to address this ;)
I guess, the problem is that we all live and work in european
countries that utilize the english language for international
communication, but none of us is really living the english language,
except Paul, Nick and the other guys that live on the islands out there ;)
So, it would be great to let us know where(!) those typos are, and
we're willing to kick them.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: WARNING: SMPP: PDU element password to long (length is 9, should be 9)
Stipe Tolj wrote:
Ok, now about the warning. I see this in gw/smsc/smpp_pdu.c:236:
...
#define NULTERMINATED(name, max_octets) \
if (p-name != NULL) { \
if (octstr_len(p-name) = max_octets) { \
warning(0, SMPP: PDU element %s to long \
(length is %ld, should be %d), \
#name, octstr_len(p-name), max_octets); \
temp = octstr_copy(p-name, 0, max_octets-1); \
} else \
temp = octstr_duplicate(p-name); \
octstr_append(os, temp); \
octstr_destroy(temp); \
} \
octstr_append_char(os, '\0');
...
Which means the warning will go out even when we have the max octets in
the pdu field.
Question should be: why do we compare = and not only ???
I don't see any good reason on the equal compare here.
ok, confirmed that I have been muggling arround that code, see:
http://www.kannel.org/cgi-bin/viewcvs.cgi/gateway/gw/smsc/smpp_pdu.c.diff?r1=1.1r2=1.2
but I actualy don't see a reason why we shouldn't change the if
statement from = compare to pure compare.
Any objections here?
Sitpe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: WARNING: SMPP: PDU element password to long (length is 9, shouldbe 9)
Pedro B. wrote:
Alex,
I'm halfway looking (more like digging) through all the code to make a
manual-spellcheck-patch.
Maybe we can split the work, or maybe you review my patch when i have it
done... can never spellcheck too much, i say :)
I guess running apspell over the diff would help too.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: WARNING: SMPP: PDU element password to long (length is 9, shouldbe 9)
Alex Kinch wrote:
- Original Message -
now, Kannel was never been an US project. Finish people started it and
several other european citizen have continued it. Speaking of personal
implications: I'm a croatian citizen, born and living in Germany,
working on a finish project ;)
Finnish you mean ;)
ok ok, got me again.
ducks
that was too fast for me ;)
I'm happy to have a look through the docs sometime and correct any spelling
mistakes, do I just check the HTML or is there a better way of doing it?
I did some aspell'ing on the userguide.xml and the .shtml files of the
kannel.org web site.
I guess we'd need some fixing in the .[ch] files comments.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: Commercial Support
Erwien Samantha Y wrote:
Is anyone know where can i get kannel commercial support ?
there is actually no real commitment from a company side to provide
commercial support for Kannel, except Wapme Systems AG (my company),
that offers this service for the Vodafone worldwide-group and their
Kannel instances running for several purposes.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: WARNING: SMPP: PDU element password to long (length is 9, should be 9)
Aarno Syvänen wrote:
The entity is NULTERMINATED, octet string is not. So \0 is added, in
the last line,
and that's why the comparison is =. And of course, max-octets does not
include
terminating \0.
ok, but is the equal comparison realy required? wouldn't be enough?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: RADIUS ACCT info used in WAP Push
Lars Kristian Roland wrote:
Hi,
Have you considered adding the RADIUS information in such a way that the
client pushing a wap push via the push proxy can send the pap-request to
an msisdn rather than an IP also when sending a udp push, but the push
proxy sends it to the IP address (wap push proxy must then do the
mapping between msisdn and ip address based on the information from
radius acct)?
I can see that you've implemented this mapping for receiving acct radius
info for normal wap requests, and I guess this would be a small
extension to that???
Hi Lars,
a good question.
But as I remember, Kannel's PPG _is_ able to send Push messages to
MSISDN numbers generically. Since it will pass it over the SMS bearer
to the phone. So I don't see the necessarity to have the RADIUS acct
mapping active here.
The _only_ benefit I see from this here is to allow PI (push
initiators) to send push messages over PPG with MSISDNs as target, and
wapbox would try to resolve this into IPs, in case the MSISDN is
online and connected to the NAS at that specific point of time. So
something like this:
a) PI sends push msg to PPG
b) PPG tries to resolve MSISDN into IP (from RADIUS acct mapping)
c) if MSISDN is online at this time, PPG is able to address the push
message via IP
d) if it's not online, utilize SMS bearer to push the message (this is
the current default behavior for MSISDN targets)
Hmm, Aarno, some comments from your side?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: RADIUS ACCT info used in WAP Push
Paul Keogh wrote:
a) PI sends push msg to PPG
b) PPG tries to resolve MSISDN into IP (from RADIUS acct mapping)
c) if MSISDN is online at this time, PPG is able to address the push
message via IP
d) if it's not online, utilize SMS bearer to push the message
(this is
the current default behavior for MSISDN targets)
This is an interesting suggestion and could solve some issues
around IP addressable phones.
Do GPRS operators maintain this kind of RADIUS accounting information
by default ? And if they do, does the network allow routing of IP
packets back to the device ?
I guess they do maintain such RADIUS acct information. If they use it
for PPG issues, that's a totally different thing.
AFAIK, you can't address the IPs from the outside world :(
Is anyone doing Push over IP ? This option offers a cost saving to
the operator by moving Push from SMS to IP, particularly
interesting for MMS notifications (Several operators have told me
MMS is pushing SMSC license costs up).
hmmm, that's true for GPRS connections. But AFAIK, GPRS does not mean
that you have a permanent IP stack available at the phone. Does it?
If yes, then you're obviously right that this would reduce SMS costs,
due to IP addressing. Unfortunatly external providers (like we at
Wapme) will a) not be able to send packets to the GPRS IPs, b) won't
know which MSISDN-IP mapping is there. So you can't address them
actually via IP from the outside world.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: RADIUS ACCT info used in WAP Push
Lars Kristian Roland wrote:
Yes, SMS is always an option, but GPRS is cheaper, so it'd be good to be
able to use it when possible, at least when there's a lot of WAP Push,
for example as part of an online game or other. It could also be the
case that the application knows the MSISDN, but doesn't know the IP of
the phone to send to.
I'd consider this the normal case. The IPs are usually covered
inside the GPRS network and when your phone talks to the outside
world, it's usually NATed.
Now that would obviously be even more sexy! It'd be excellent, in
fact...
How about digging into wapbox here and check if you can send us a
patch. I'd be willing for review.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: WARNING: SMPP: PDU element password to long (length is 9, should be 9)
Alexander Malysh wrote:
NULTERMINATED as Aarno pointed already, is C string with terminating \0.
max-octets is _including_ terminating \0. comparison is no enough,
because if octstr len even equal to max-octets than that means we will drop
1 octet (because \0 will be added at the end), so the warninng and
comparison is correct. But in order to not confuse users we could do
something like this:
...
#define NULTERMINATED(name, max_octets) \
if (p-name != NULL) { \
if (octstr_len(p-name) = max_octets) { \
warning(0, SMPP: PDU element %s to long \
(length is %ld, should be %d), \
#name, octstr_len(p-name), max_octets - 1); \
^^
temp = octstr_copy(p-name, 0, max_octets-1); \
} else \
temp = octstr_duplicate(p-name); \
octstr_append(os, temp); \
octstr_destroy(temp); \
} \
octstr_append_char(os, '\0');
...
agreed, +1, commited to cvs.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: Patch - spellchecking
Pedro B. wrote:
For consideration.
Note: It's not a FULL revision of all the files, line by line. Right now
it is just a correction of the major flaws, to make it consistent in a
global overview.
If approved, i will continue to comb the source, but to reach a state of
perfectionism, more time will be needed.
thanks a lot! -- commited to cvs, except userguide.xml, which was
rejected by patch.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: [**SPAM**] Kannel SMS
[EMAIL PROTECTED] wrote:
Dear sir,
I have just installed Kannel 1.2.2 but I can not send anything. The
following is captured error. The attached file is smskannel.conf
you should pick Kannel 1.3.2 rather then 1.2.2 (which in fact does not
exists?!, you ment 1.2.1, didn't you?)
As I see you run Cygwin 1.x, which version? Seems there is something
broken with file descriptors on that system?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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-
[Fwd: data_sm]
forwarded to the list. Stipe ---BeginMessage--- do you plan to include the data_sm pdu in smsc_smpp.c ? i think is missing in the v3.4 implementation. bye. Juan Pablo. ---End Message---
Re: Editing Kannel or Smskannel.conf
Jane P. Ifurung wrote:
Hello!
I would like to edit my smskannel.conf but I could not edit it. Do I
need GNU autoconf for that? Thanks..
off-topic, but still _relevant_!!
Please DO NOT CROSS-POST to lists! People who are reading both lists
get 2 mails.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: compiling 1.3.2 on FreeBSD 5.2.1
Hi Dimitri,
I have no access to that FreeBSD version, but please give it a try and
try the attached patch, that fixes some CFLAGS and LIBS env var
settings in configure.
Simply apply the patch and re-create the configure script by using
autoconf.
BTW, since we are getting here to development relatend questions, I'm
moving this to the devel@ list.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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-
RCS file: /home/cvs/gateway/configure.in,v
retrieving revision 1.142
diff -u -r1.142 configure.in
--- configure.in16 Jun 2004 09:47:45 - 1.142
+++ configure.in21 Aug 2004 00:53:19 -
@@ -1,7 +1,64 @@
+dnl /*
+dnl * The Kannel Software License, Version 1.0
+dnl *
+dnl * Copyright (c) 2001-2004 Kannel Group
+dnl * Copyright (c) 1998-2001 WapIT Ltd.
+dnl * All rights reserved.
+dnl *
+dnl * Redistribution and use in source and binary forms, with or without
+dnl * modification, are permitted provided that the following conditions
+dnl * are met:
+dnl *
+dnl * 1. Redistributions of source code must retain the above copyright
+dnl *notice, this list of conditions and the following disclaimer.
+dnl *
+dnl * 2. Redistributions in binary form must reproduce the above copyright
+dnl *notice, this list of conditions and the following disclaimer in
+dnl *the documentation and/or other materials provided with the
+dnl *distribution.
+dnl *
+dnl * 3. The end-user documentation included with the redistribution,
+dnl *if any, must include the following acknowledgment:
+dnl * This product includes software developed by the
+dnl *Kannel Group (http://www.kannel.org/).
+dnl *Alternately, this acknowledgment may appear in the software itself,
+dnl *if and wherever such third-party acknowledgments normally appear.
+dnl *
+dnl * 4. The names Kannel and Kannel Group must not be used to
+dnl *endorse or promote products derived from this software without
+dnl *prior written permission. For written permission, please
+dnl *contact [EMAIL PROTECTED]
+dnl *
+dnl * 5. Products derived from this software may not be called Kannel,
+dnl *nor may Kannel appear in their name, without prior written
+dnl *permission of the Kannel Group.
+dnl *
+dnl * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
+dnl * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+dnl * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+dnl * DISCLAIMED. IN NO EVENT SHALL THE KANNEL GROUP OR ITS CONTRIBUTORS
+dnl * BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
+dnl * OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
+dnl * OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
+dnl * BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
+dnl * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
+dnl * OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
+dnl * EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+dnl *
+dnl *
+dnl * This software consists of voluntary contributions made by many
+dnl * individuals on behalf of the Kannel Group. For more information on
+dnl * the Kannel Group, please see http://www.kannel.org/.
+dnl *
+dnl * Portions of this software are based upon software originally written at
+dnl * WapIT Ltd., Helsinki, Finland for the Kannel project.
+dnl */
+
+dnl
dnl configure.in -- main autoconf macro definition file
dnl
dnl Process this file with autoconf to produce a configure script.
-dnl This file is part of the Kannel WAP and SMS gateway project.
+dnl
dnl initialization
@@ -60,10 +117,15 @@
CFLAGS=$CFLAGS -DDARWIN=1
LIBTOOL=libtool -static -o
;;
- *-linux-*)
+ *-linux-*)
CFLAGS=$CFLAGS
Re: compiling 1.3.2 on FreeBSD 5.2.1
sorry, the patch has been stripped and there was something missing.
Please use the attached one.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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-
Index: gateway/configure.in
===
RCS file: /home/cvs/gateway/configure.in,v
retrieving revision 1.142
diff -u -r1.142 configure.in
--- gateway/configure.in16 Jun 2004 09:47:45 - 1.142
+++ gateway/configure.in21 Aug 2004 01:01:22 -
@@ -1,7 +1,64 @@
+dnl /*
+dnl * The Kannel Software License, Version 1.0
+dnl *
+dnl * Copyright (c) 2001-2004 Kannel Group
+dnl * Copyright (c) 1998-2001 WapIT Ltd.
+dnl * All rights reserved.
+dnl *
+dnl * Redistribution and use in source and binary forms, with or without
+dnl * modification, are permitted provided that the following conditions
+dnl * are met:
+dnl *
+dnl * 1. Redistributions of source code must retain the above copyright
+dnl *notice, this list of conditions and the following disclaimer.
+dnl *
+dnl * 2. Redistributions in binary form must reproduce the above copyright
+dnl *notice, this list of conditions and the following disclaimer in
+dnl *the documentation and/or other materials provided with the
+dnl *distribution.
+dnl *
+dnl * 3. The end-user documentation included with the redistribution,
+dnl *if any, must include the following acknowledgment:
+dnl * This product includes software developed by the
+dnl *Kannel Group (http://www.kannel.org/).
+dnl *Alternately, this acknowledgment may appear in the software itself,
+dnl *if and wherever such third-party acknowledgments normally appear.
+dnl *
+dnl * 4. The names Kannel and Kannel Group must not be used to
+dnl *endorse or promote products derived from this software without
+dnl *prior written permission. For written permission, please
+dnl *contact [EMAIL PROTECTED]
+dnl *
+dnl * 5. Products derived from this software may not be called Kannel,
+dnl *nor may Kannel appear in their name, without prior written
+dnl *permission of the Kannel Group.
+dnl *
+dnl * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
+dnl * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+dnl * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+dnl * DISCLAIMED. IN NO EVENT SHALL THE KANNEL GROUP OR ITS CONTRIBUTORS
+dnl * BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
+dnl * OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
+dnl * OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
+dnl * BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
+dnl * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
+dnl * OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
+dnl * EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+dnl *
+dnl *
+dnl * This software consists of voluntary contributions made by many
+dnl * individuals on behalf of the Kannel Group. For more information on
+dnl * the Kannel Group, please see http://www.kannel.org/.
+dnl *
+dnl * Portions of this software are based upon software originally written at
+dnl * WapIT Ltd., Helsinki, Finland for the Kannel project.
+dnl */
+
+dnl
dnl configure.in -- main autoconf macro definition file
dnl
dnl Process this file with autoconf to produce a configure script.
-dnl This file is part of the Kannel WAP and SMS gateway project.
+dnl
dnl initialization
@@ -60,10 +117,15 @@
CFLAGS=$CFLAGS -DDARWIN=1
LIBTOOL=libtool -static -o
;;
- *-linux-*)
+ *-linux-*)
CFLAGS=$CFLAGS -D_XOPEN_SOURCE=600 -D_BSD_SOURCE
LDFLAGS=$LDFLAGS -rdynamic
;;
+ *-*-openbsd* | *-*-freebsd*)
+# Do not include libc_r directly, use -pthread
Re: Supported GSM Phones/Modems as SMSC
Jane P. Ifurung wrote:
Hello!
I would like to ask a list of the supported types of modems/phones that
act as SMSCs in Kannel ver 1.3.2...I intend to use Nokia 7650 since this
is the one readily available. What is the appropriate cable to use? By
the way I'm using RedHat 9.
AFAIK, the N7650 does not have a DLR-cable for the serial bus. You may
use the IR (infra-red) port itself.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: compiling 1.3.2 on FreeBSD 5.2.1
Dimitri Aivaliotis wrote:
Hello Stipe,
If you replace the line
+LIBS=$LIBS -pthread
in your patch with
+LIBS=$LIBS -lc_r -lkse
then, it will compile.
If you include only -lkse, you will get an error like the following in config.log:
configure:1955: checking whether the C compiler works
configure:1961: ./a.out
Fatal error 'Spinlock called when not threaded.' at line 88 in file /usr/src/lib/
libpthread/thread/thr_spinlock.c (errno = 0)
./configure: line 1: 12840 Segmentation fault (core dumped) ./$ac_file
configure:1964: $? = 139
configure:1973: error: cannot run C compiled programs.
ok, great. I'll patch it and commit to cvs. Thanks a lot.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: compiling 1.3.2 on FreeBSD 5.2.1
Dimitri Aivaliotis wrote:
Hello Stipe,
If you replace the line
+LIBS=$LIBS -pthread
in your patch with
+LIBS=$LIBS -lc_r -lkse
then, it will compile.
If you include only -lkse, you will get an error like the following in config.log:
configure:1955: checking whether the C compiler works
configure:1961: ./a.out
Fatal error 'Spinlock called when not threaded.' at line 88 in file /usr/src/lib/
libpthread/thread/thr_spinlock.c (errno = 0)
./configure: line 1: 12840 Segmentation fault (core dumped) ./$ac_file
configure:1964: $? = 139
configure:1973: error: cannot run C compiled programs.
HTH
what is the libbse.a library for on FreeBSD? Is it required on the
LIBS or does -lc_r work already?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: Radius accounting problem.
maddie wrote:
Hello All!
It is my second post about radius accounting problem.
Problem is: spending some time (about 4 ore more hours) radius
MSISDN mapping is stucked on ONE MSISDN anr substitute by this all
incoming session.
I'm using ver. 1.3.2, and radius accounting from Sisco 7207 npe400
vxr ios: c7200-g6is-mz.122-8.YW3 (GPRS support IOS)
Sorry, I didn't get it. Can you give it another try and explain in
more detailed what the problem is.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: Thesis project
Hi Oscar,
Oscar Medina Duarte wrote:
Hi all,
I'm looking for an interesting topic for my bachelor degree thesis, my
first shot is to do something related to my work, that is, sms and
protocol related...
Any suggestions !??
Here is my topic candidate list so far:
Kannel security
Design of guidelines to deploy Kannel in a secure high risk environment,
as kannel systems often have something to do with making money, these
have to be run in a way to reduce risk of being successfully attacked.
correct. Even the concentration on billing and logging security
aspects would be highly relevant. Thing of the question: How do I log
and analyze traffic flows in a high-traffic-packet environment, like
Kannel, when it's driven to it's limits.
Hot points:
Secure/proper implementation (This may include change of code or
architecture to have correct practices)
Configuration and preparation of a secure environment, OS selection and
configuration.
Kannel SMPPv5 implementation
Upgrade Kannel smsc SMPP module to comply with SMPP v5.
:) yep. This would be interesting for the group too. But(!), if you
tend to implement things, I'd suggest to go for the MMAP protocoll
(the SOAP/XML dialect for SMS and mesasge transmission). In this case
I'd highly would be colaborative with using the gSOAP C preprocessor
engine (which we use for MM7, MM4 layerin in MMSC).
Kannel JMS gateway
Make a smsjmsbox for kannel, this is to create a kannel box to allow a
JMS compliant software to comunicate with kannel using an object
oriented protocol.
very interesting too. I'm not that familiar with Java internals, but
it would be highly valueable to have a docking-point to Kannel for
Java enviroment that allow Java SMS objects for various purposes.
Hot points:
Implementation of Kannel's internal protocol using java
SMS filtering rules
MO and MT billing support and accounting
Contibution to a OpenSource project
Kannel Web Service Gateway
Make a smsWSbox for kannel, this is to create a kannel box that
comunicates with other applications using a Web Service as a
communication standard.
Hot points:
Using Web Services with native software
yep, that's what I ment with the open standard from the SMPP forum,
called MMAP.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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-
[RFV] Re: [PATCH] datatype inconsistency in wsp_strings.c
This is a request for votes!
Vjacheslav Chekushin wrote:
Hi, list.
This patch fix quite obviouse data type inconsistency.
This make sence in 64 bit environment where sizeof(int) != sizeof(long)
yep, +1, thanks a lot.
Vjacheslav, since you are providing patches for some time now, I'd
like to get you upgraded to cvs access, so you'd be able to commit
obvious patches and fixes on your own. What about that?
@group: I'd vote for Vjacheslav to have cvs write access. We need at
least 2 more votes from developers with cvs access. So please review
Vjacheslav's submission history and vote!
(thinking especially on votes from Mr. Stress-test Alex and Aarno ;)
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Dsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: Problem compiling with MySql support
Alejandro Guerrieri wrote:
Hi,
I am having problems compiling 1.3.2 with MySQL support. The system doesn't
seem to find part of MySQL (mysql_init on libmysqlclient):
]#
./configure --enable-start-stop-daemon --prefix=/usr --with-defaults=speed
--disable-docs --disable-ssl --with-mysql --with-mysql-dir=/usr
loading cache ./config.cache
Configuring for Kannel gateway version 1.3.2 ...
Configuring DB support ...
checking whether to compile with MySQL support... searching
checking for mysql_config... /usr/bin/mysql_config
checking mysql version... 3.23.58
checking mysql
libs... -L'/usr/lib/mysql' -lmysqlclient -lz -lcrypt -lnsl -lm
checking for mysql_init in -lmysqlclient... no
configure: error: Unable to find MySQL client libraries
I am using RedHat 9 and I have the proper RPM packages installed:
]# rpm -qa |grep -i mysql
perl-DBD-MySQL-2.1021-3
mysql-server-3.23.58-1.9
mysql-devel-3.23.58-1.9
mysql-3.23.58-1.9
]# locate mysql.h
/usr/include/mysql/mysql.h
]# locate libmysql
/usr/lib/mysql/libmysqlclient.so.10.0.0
/usr/lib/mysql/libmysqlclient.so.10
/usr/lib/mysql/libmysqlclient_r.so.10.0.0
/usr/lib/mysql/libmysqlclient_r.so.10
/usr/lib/mysql/libmysqlclient.a
/usr/lib/mysql/libmysqlclient.so
/usr/lib/mysql/libmysqlclient_r.a
/usr/lib/mysql/libmysqlclient_r.so
Any hints?
that's sort of suspicious, since the paths seem ok. Try these and mail
us the output:
$ nm /usr/lib/mysql/libmysqlclient.a | grep mysql_init
$ mysql_config
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: Problem compiling with MySql support
Alejandro Guerrieri wrote:
Stipe,
Thank you for your help.
Here it goes:
]# nm /usr/lib/mysql/libmysqlclient.a | grep mysql_init
1100 T mysql_init
nm: my_pthread.o: no symbols
nm: my_thr_init.o: no symbols
nm: thr_mutex.o: no symbols
nm: my_port.o: no symbols
nm: getopt.o: no symbols
nm: getopt1.o: no symbols
nm: strmov.o: no symbols
nm: strnlen.o: no symbols
nm: bmove.o: no symbols
nm: strtoull.o: no symbols
nm: strtoll.o: no symbols
]# mysql_config
Usage: /usr/bin/mysql_config [OPTIONS]
Options:
--cflags[-I'/usr/include/mysql']
--libs
[-L'/usr/lib/mysql' -lmysqlclient -lz -lcrypt -lnsl -lm]
--socket[/var/lib/mysql/mysql.sock]
--port [3306]
--version [3.23.58]
ok, now, please the config.log file from Kannel's gateway dir, after
the configure has run. Please have a look into it too, it should tell
you at least why configure seems to fail in detecting the mysql_init()
routine in libmysqlclient.a.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: Problem compiling with MySql support
Alejandro Guerrieri wrote:
Dear Stipe,
Here is the mysql part from config.log. I'm not precisely an expert
analyzing this, but it seems that the linker cannot find libmysqlclient,
despite it's where it should be...
configure:4280: checking whether to compile with MySQL support
configure:4304: checking for mysql_config
configure:4402: checking mysql version
configure:4456: checking mysql libs
configure:4459: checking for mysql_init in -lmysqlclient
configure:4478: gcc -o
conftest -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -I/usr/include/libxml2 -rdynam
ic
conftest.c -lmysqlclient -L'/usr/lib/mysql' -lmysqlclient -lz -lcrypt -lnsl
-lm -lresolv -lnsl -lm -lpthread -L/usr/lib -lxml2 -lz -lm 15
/usr/bin/ld: cannot find -lmysqlclient
collect2: ld returned 1 exit status
configure: failed program was:
#line 4467 configure
#include confdefs.h
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char mysql_init();
int main() {
mysql_init()
; return 0; }
isn't there more lines after this that output the gcc output?
Try to compile the conftest.c by hand on your own (like here tried by
configure) and see what ld says about it.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: Problem compiling with MySql support
Alejandro Guerrieri wrote:
Stipe,
Nop, I've checked, make-cleaned re-configured and tail-ed the config.log and
it always ends there.
Maybe I'm missing something, but I cannot seem to find conftest.c anywhere
on the source tree.
I've even searched the .tar.gz to check if it was accidentally deleted, but
it's not there neither.
I mean:
gateway-1.3.2.tar.gz
Date: July 14 10:18
Size: 2,449,484
It's a file that comes with the distribution or it's generated during
configure?
yep, it's generated and deleted during configure run.
Simply cut and paste the small snippet that is at the end of
config.log and try to compile/link on your own.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: [PATCH] datatype inconsistency in wsp_strings.c
Vjacheslav Chekushin wrote:
Hi, list.
This patch fix quite obviouse data type inconsistency.
This make sence in 64 bit environment where sizeof(int) != sizeof(long)
--- ../gateway-1.3.2_base/wap/wsp_strings.c Thu Jan 22 16:08:25 2004
+++ wap/wsp_strings.c Mon Aug 16 14:52:38 2004
@@ -203,7 +203,7 @@
static long string_to_versioned_number(Octstr *ostr, struct table *table,
int version)
{
-unsigned int i, ret;
+long i, ret;
gw_assert(initialized);
commited to cvs. Thanks a lot.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Dsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: Problem compiling with MySql support
Alejandro Guerrieri wrote:
Dear Stipe,
conftest.c:
--
#line 4467 configure
#include confdefs.h
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char mysql_init();
int main() {
mysql_init()
; return 0; }
--
First I ran a flat compile:
]# gcc conftest.c
/tmp/ccyfJ0bD.o(.text+0x11): In function `main':
: undefined reference to `mysql_init'
collect2: ld returned 1 exit status
(Silly me) I wasn't specifying the right libraries and paths. Then I've
tried running it as config.log showed (I removed the redirector 15 to
get any output on the console).
gcc -o
nftest -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -I/usr/include/libxml2 -rdynamic
conftest.c -lmysqlclient -L'/usr/lib/mysql' -lmysqlclient -lz -lcrypt -lnsl
-lm -lresolv -lnsl -lm -lpthread -L/usr/lib -lxml2 -lz -lm
And it compiled perfectly. I then ran ./conftest and it executed and
returned without complaining about anything (nor displaying anything).
Just for kicks, I've run ldd to find out the linkage:
]# ldd conftest
libmysqlclient.so.10 = /usr/lib/mysql/libmysqlclient.so.10
(0x4001e000)
libz.so.1 = /usr/lib/libz.so.1 (0x40056000)
libcrypt.so.1 = /lib/libcrypt.so.1 (0x40064000)
libnsl.so.1 = /lib/libnsl.so.1 (0x40091000)
libm.so.6 = /lib/tls/libm.so.6 (0x400a6000)
libresolv.so.2 = /lib/libresolv.so.2 (0x400c8000)
libpthread.so.0 = /lib/tls/libpthread.so.0 (0x400da000)
libxml2.so.2 = /usr/lib/libxml2.so.2 (0x400e9000)
libc.so.6 = /lib/tls/libc.so.6 (0x4200)
/lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000)
I am also including my gcc/ld versions, just in case:
]# gcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/specs
Configured with:
../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info
--enable-shared --enable-threads=posix --disable-checking --with-system-zli
b --enable-__cxa_atexit --host=i386-redhat-linux
Thread model: posix
gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
]# ld -v
GNU ld version 2.13.90.0.18 20030206
hmm, sorry, that's all I could offer from remote.
Everything looks fine from here.
I guess you should try to dig into the configure[.in] process yourself
or consult one of your local gurus.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: [PATCH] wml compiler panics on some wml files
Vjacheslav Chekushin wrote:
Hi, list.
wml_compiler PANIC on wml files with some DOCTYPE definition.
(PANIC: gwlib/octstr.c:242: octstr_create_real: Assertion `cstr != NULL'
failed.)
One example is below. You can check with wml file
with wml_tester. Attached patch fixes this problem.
?xml version='1.0'?
!DOCTYPE chapter SYSTEM /just/a/test.dtd [
!ENTITY plainEntity FOO entity]
wml
card id=main name=Test
img src=/img/logo.wbmp alt=image/
p
a href=1.php1/abr/
a href=2.php2/abr/
a href=3.php3/abr/
a href=4.php4/abr/
/p
/card
/wml
--- ../gateway-1.3.2_base/gw/wml_compiler.c Wed Apr 21 13:45:35 2004
+++ gw/wml_compiler.c Mon Aug 9 14:51:54 2004
@@ -597,7 +597,7 @@
}
/* Return WML Version dependent on xml ExternalID string */
-if (document-intSubset != NULL)
+if ((document-intSubset != NULL) (document-intSubset-ExternalID != NULL))
externalID = octstr_create(document-intSubset-ExternalID);
if (externalID == NULL) {
(*wbxml)-wml_public_id = 0x04; /* WML 1.1 Public ID */
commited to cvs. Thanks a lot.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Dsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: [PATCH] Memory leak in wap-appl.c
Vjacheslav Chekushin wrote:
Hi, list.
There is obvious memory leak in wap-appl.c
ret = wml_compile(content-body, content-charset, wmlc,
content-version);
If you will check wml_compile function from wml_compiler.c, than you'll
see that
it allocates wmlc at the start and doesn't deallocate it even if
we have compilation error.
So in case of compilation error we must free it in wap-appl.c
Provided patch fixes this problem.
--- ../gateway_base/gw/wap-appl.c Thu Oct 9 15:04:18 2003
+++ gw/wap-appl.c Thu Oct 23 16:58:37 2003
@@ -1230,6 +1230,7 @@
if (ret == 0)
return wmlc;
+octstr_destroy(wmlc);
warning(0, WSP: WML compilation failed.);
return NULL;
}
+1, we octstr_create() it in gw/wml_compiler.c:wml_compiler() and do
not _destroy() it anywhere.
commiting to cvs. Thanks a lot.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Dsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: Problem with memoryleak in octstr
Ken A. Redergård wrote:
Hi,
I'm trying to figure out why the following octstr function leak 1 byte
of memory for each iteration:
/* test_octstr.c */
#include unistd.h
#include gwlib/gwlib.h
int main(void) {
Octstr *os;
int i;
gwlib_init();
for (i = 0; i 100; i++) {
os = octstr_format(sadfasdfasdfas);
octstr_append(os, octstr_imm(asdfasdfasdfasdf));
octstr_destroy(os);
gwthread_sleep(1);
}
gwlib_shutdown();
return 0;
}
Watching this with ps -C test_octstr -F shows that for every four
seconds it leaks 4 bytes... Is the use of octstr incorrect or is it a
problem in gwlib ?
hmm, I tried this with valgrind and get the following:
$ valgrind --tool=memcheck --leak-check=yes ./test/test_octstr
==9563== Memcheck, a memory error detector for x86-linux.
==9563== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward et al.
==9563== Using valgrind-2.1.2, a program supervision framework for
x86-linux.
==9563== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward et al.
==9563== For more details, rerun with: -v
==9563==
==9563== warning: Valgrind's pthread_cond_destroy is incomplete
==9563== (it doesn't check if the cond is waited on)
==9563== your program may misbehave as a result
==9563== warning: Valgrind's pthread_cond_destroy is incomplete
==9563== (it doesn't check if the cond is waited on)
==9563== your program may misbehave as a result
==9563== warning: Valgrind's pthread_cond_destroy is incomplete
==9563== (it doesn't check if the cond is waited on)
==9563== your program may misbehave as a result
2004-08-26 18:01:21 [9563] [0] DEBUG: Immutable octet strings: 1.
==9563==
==9563== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 28 from 2)
==9563== malloc/free: in use at exit: 1200 bytes in 29 blocks.
==9563== malloc/free: 11184 allocs, 11155 frees, 717508 bytes allocated.
==9563== For counts of detected errors, rerun with: -v
==9563== searching for pointers to 29 not-freed blocks.
==9563== checked 5445108 bytes.
==9563==
==9563== LEAK SUMMARY:
==9563==definitely lost: 0 bytes in 0 blocks.
==9563==possibly lost: 0 bytes in 0 blocks.
==9563==still reachable: 1000 bytes in 28 blocks.
==9563== suppressed: 200 bytes in 1 blocks.
==9563== Reachable blocks (those to which a pointer was found) are not
shown.
==9563== To see them, rerun with: --show-reachable=yes
So valgrind seems _not_ to see any leaking.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: Question about routing
Oscar Medina Duarte wrote:
Hello !
I'm not getting what I want I don't know what is missing, I have 5 smsc
connections, configured that bound correctly, and only one smsbox that
gets all the messages, and that is working fine. The problem is that
outbound messages are not sent, with the message :
...
2004-08-26 13:11:59 [9373] [2] DEBUG: HTTP: Creating HTTPClient for `an
IP'.
2004-08-26 13:11:59 [9373] [3] DEBUG: HTTP: Resetting HTTPClient for
`an IP'.
2004-08-26 13:12:44 [9373] [4] WARNING: smsbox_list empty!
2004-08-26 13:12:44 [9373] [4] WARNING: smsbox_list empty!
2004-08-26 13:12:50 [9373] [3] DEBUG: HTTP: Resetting HTTPClient for
`an IP'.
2004-08-26 13:13:38 [9373] [12] DEBUG: boxc_receiver: sms received
2004-08-26 13:13:38 [9373] [12] WARNING: Cannot find SMSCConn for
message to a telephone, rejected.
2004-08-26 13:13:38 [9373] [12] WARNING: Message rejected by bearerbox,
no router!
2004-08-26 13:13:38 [9373] [12] DEBUG: send_msg: sending msg to boxc:
smsbox_01
2004-08-26 13:13:44 [9373] [4] WARNING: smsbox_list empty!
2004-08-26 13:13:44 [9373] [4] WARNING: smsbox_list empty!
...
at the bearerbox, as you can see, I'm using sendsms to out bind
messages, but that is not working.
NOTE: The data included within and is data that depending on its
context may be an IP, password, phone number, etc...
Thanks !!
== Oscar
##
###bearerbox.conf ###
### Author: Oscar Medina
##
###
Core ##
###
group = core
admin-port = some_data
admin-password = some_data
status-password = some_data
admin-deny-ip = *.*.*.*
admin-allow-ip = 127.0.0.1;some_IP
smsbox-port = some_port
box-deny-ip = *.*.*.*
box-allow-ip = 127.0.0.1;some_IP
log-level = 0
log-file = logs/bearerbox.log
access-log = logs/bearerbox.access
# SMSC's #
## SMSC: test ##
## Number: some_data ##
## smscID: some_data ##
group = smsc
smsc = smpp
smsc-id = smsc_1
denied-smsc-id = smsc_2;smsc_3;smsc_4;smsc_5
allowed-smsc-id = smsc_1
preferred-smsc-id = smsc_1
host = some_IP
#host = localhost
port = some_port
transceiver-mode = true
smsc-username = some_data
smsc-password = some_data
system-type = VMA
interface-version = 0x34
enquire-link-interval = 60
max-pending-submits = 10
reconnect-delay = 30
source-addr-ton = 0
source-addr-npi = 1
source-addr-autodetect = true
dest-addr-ton = 2
dest-addr-npi = 1
log-level = 0
log-file = logs/smsc_TelcelTest.log
... plus other 4 smsc's with the same kind of config,
from with the corresponding smscID...
config looks good. This is a more semantical problem.
Your smsc groups do 'allow-smsc-id = smsc-id' which means, only a
message carrying this smsc-id will be allowed to be passed to this
smsc link.
So, if you call the sendsms HTTP interface _without_ the
'smsc=foobar' parameter, this would result exactly in the no
router error message inside the main routing facility of bearerbox.
Actually you are trying to send messages without specifying which
way to go, but on the other hand, do require (with the
allowed-smsc-id) the smsc links to have that specification.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: compilation error
wrote:
hi,everybody I had a compilation trouble with kannel-1.3.2, my
operation system is RedHat Linux Fedora 2. Now my application system does
not work in kannel, but can works in WinWAP Browser 3.1 and Nokia WAP
Gateway Simulator.
here is log:
2004-08-27 15:34:38 [5566] [0] INFO: Connected to bearerbox at localhost
port 13 002.
2004-08-27 15:35:41 [5566] [6] INFO: Fetching
http://192.168.1.100:8080/wap/login.jsp
2004-08-27 15:35:41 [5566] [7] INFO: WBXML: No wbxml version given,
assuming 1.1
2004-08-27 15:36:02 [5566] [6] INFO: Fetching
http://192.168.1.100:8080/wap/login.jsp
2004-08-27 15:36:02 [5566] [7] ERROR: WML compiler: Compiling error:
libxml retu rned a NULL pointer
2004-08-27 15:36:02 [5566] [7] WARNING: WSP: WML compilation failed.
2004-08-27 15:36:02 [5566] [7] WARNING: WSP: All converters for
`text/vnd.wap.wml' at
`http://192.168.1.100:8080/wap/login.jsp' failed.
2004-08-27 15:36:02 [5566] [6] INFO: Fetching
http://192.168.1.100:8080/wap/allMenu.jsp?userId=99passWd=99devId=2
ok, unfortunatly I don't have the time to dig into this, but _at
least_ from the ERRORs, we see that the libxml2 XML compiler fails. So
I have to assume the given WML/XML input served by the HTTP server is
not ok, right?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Dsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: [PATCHSET] For those who interested
Paul P Komkoff Jr wrote:
After a long period of inactivity due to personal occupation, I
updated my patchset to upstream cvs.
All information posted to http://stingr.net/kannel/
thanks for the note Paul. I'll have a deeper view into them tomorrow,
and comment in this thread.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Dsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: [PATCHSET] For those who interested
Paul P Komkoff Jr wrote:
Replying to Stipe Tolj:
Paul P Komkoff Jr wrote:
After a long period of inactivity due to personal occupation, I
updated my patchset to upstream cvs.
All information posted to http://stingr.net/kannel/
thanks for the note Paul. I'll have a deeper view into them tomorrow,
and comment in this thread.
Sure.
There's really nothing new. curl and radius utmp for msisdn detection.
Automake. Just resynched to upstream.
I have a little plan to make rpm version of kannel for recent fedora.
There will be great to be able to install it in parts, and build
various dlr storage support as different packages but this will need
some patching.
It will be great if you'll accept at least automake to upstream so we
can shake out bugs imposed by different platforms/OSes.
( I will even try to split automake-related stuff out if you agree
:))) )
ok, I'd be happy to have you boarded to the developers in order to let
you code for the official upstream too. And I guess, as long as
adding dependecy libs is an optional feature (like the curl thing),
this would be at least +0-+1 for me.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Dsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: CDMA
Muhyiddin A.M Hayat wrote:
Anybody know if SMS service is available for CDMA ?
Does Kannel work with CDMA ?
What other commercial gateway available for CDMA?
yes. SMS is available for CDMA too. It only requires some generic
convertion on the transportation layer (IS-41) (the SS7 thing in the
CDMA world). But this is up to the SMSC. And as long as you get a SMPP
(or EMI/UCP) account to terminate messages to the SMSC, you should be
fine.
Limitations apply to the extention features, like binary SMS, etc.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: deny or allow a user to connect my kannel gateway
wrote:
hi,
how i deny or allow a user ip to connect my kannel gateway? In the
configure file kannel.conf we can implemente this fucation ?
thanks
BTW, configuration aspects should be directed to the users@ list
instead of the devel@ list. ;)
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Dsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: kannel sms-features: limited smsc links, aggregator use
Hi Kalle,
great to have you back here again :))
(BTW, I'm a bit quite the last weeks since I'm on vacation, so please
don't thing I left things alone ;)
Kalle Marjola wrote:
Hi, I'm back and a bit out-of-touch of the current situation of my
lovely child ;]
Anyway, I was wondering how to do following operations with current
Kannel, and came up with bad solutions and possible new features..
So, things needed:
1) SMSC (SMPP) connection that needs to be broken after one sent
message, i.e. non-persistent operation.
Maybe this one (1) could be something else, I was thinking about general
'max-sends-before-reconnect' generic SMSC variable but before doing any
hacking, have to check out if there is already some ways to do it..
nop. There is no such thing already in use. BTW, I was thinking of
what scenario you need this for. But I couldn't come up with an
example. But I guess implementing this as a generic feature would be
not that of a problem.
2) Aggregator use, i.e. message from one SMSC to another (with sender
kept as original)
yep. This can be done is ome extend with the so called rerouting
features, see CVS head user's guide and search for 'reroute'.
If I'm right, this could only be done with http/send-sms trick
(to keep the sender). Some better ways:
a) keep-numbers (or maybe use-original-numbers), as a sms-service
directive (this would still require that messages are routed to smsbox,
and then bearerbox routing to replies)
b) some aggregation support directly in bearerbox
(e.g. smsc-aggregate-to directive to smsc?)
yep, that's how the rerouting works. You can define reroutes inside
smsc groups that either route via receiver numbers or via whole
smsc-id links to other links.
But this wouldn't imply the ability to provide external aggregator
access for customers wanting to MT messages. This would be possible
with the SMPP server part. Either our smppbox or a patched (SMPP
server) version of smsc_smpp_server.c.
I'll definetly try to get smppbox free'd from Wapme cage for the sake
of all Kannel users. Also in order to get more improvements into it,
even while it works quite stable and reliable up to now.
(warm greetings from sunny croatian dalmatian coast ;)
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: Confusing status 202... error
Utsman Abdurrahman wrote: Dear All, Please advice of the following confusing eeror that I found in my kannel. I dont know why, but my kannel seems work ok with sending sms message logically but unfortunately not actually. Ive been working on this error for quite some times, but I still cant figure it out some how. Please help me with this. I use kannel 1.3.2 with wmod2 wavecom gsm modem under Redhat Taroon Linux as OS platform. Kannel configuration : group = core admin-port = 13000 smsbox-port = 13001 admin-password = admin status-password = admin admin-allow-ip = *.*.*.* box-allow-ip = 127.0.0.1 log-file = /tmp/kannel.log log-level = 0 access-log = /tmp/access.log unified-prefix = 0,+62 store-file = /tmp/kannel.store group = smsc smsc-id = modem smsc = at modemtype = wavecom device = /dev/ttyS0 allowed-smsc-id = modem group = modems id = wavecom name = Wavecom detect-string = WAVECOM keepalive-cmd = AT+CBC;+CSQ message-storage = ME group = smsbox bearerbox-host = localhost sendsms-port = 13013 log-file = /tmp/smsbox.log log-level = 0 access-log = /tmp/accesskannel.log group = sendsms-user username = user password = password default-sender = +62815140 forced-smsc = modem group = sms-service keyword = default text = No service specified Sms box log: 2004-09-16 10:43:54 [13941] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 127.0.0.1 2004-09-16 10:43:54 [13941] [3] INFO: sendsms used by user 2004-09-16 10:43:54 [13941] [3] INFO: sendsms sender:user:+628151404989 (127.0.0.1) to: 628161975399 msg:Hi World 2004-09-16 10:43:54 [13941] [3] DEBUG: message length 8, sending 1 messages 2004-09-16 10:43:54 [13941] [3] DEBUG: Status: 202 Answer: Sent. 2004-09-16 10:43:54 [13941] [3] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2004-09-16 10:49:05 [13941] [1] DEBUG: HTTP: Destroying HTTPClient area 0x813a978. 2004-09-16 10:49:05 [13941] [1] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. And I see this confirmation in the log 2004-09-16 10:43:54 [13930] [9] DEBUG: boxc_receiver: sms received 2004-09-16 10:43:54 [13930] [9] DEBUG: send_msg: sending msg to box: 127.0.0.1 The bearer box configuring logs 2004-09-16 09:38:11 [13085] [0] INFO: Added logfile `/tmp/kannel.log' with level `0'. 2004-09-16 09:38:11 [13085] [0] INFO: Started access logfile `/tmp/access.log'. 2004-09-16 09:38:11 [13085] [0] DEBUG: Started thread 1 (gw/bb_store.c:store_cleanup) 2004-09-16 09:38:11 [13085] [0] INFO: SSL not supported, no SSL initialization done. 2004-09-16 09:38:11 [13085] [0] INFO: HTTP: Opening server at port 13000. 2004-09-16 09:38:11 [13085] [0] DEBUG: Started thread 2 (gwlib/fdset.c:poller) 2004-09-16 09:38:11 [13085] [0] DEBUG: Started thread 3 (gwlib/http.c:server_thread) 2004-09-16 09:38:11 [13085] [0] DEBUG: Started thread 4 (gw/bb_http.c:httpadmin_run) 2004-09-16 09:38:11 [13085] [0] DEBUG: starting smsbox connection module 2004-09-16 09:38:11 [13085] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100). 2004-09-16 09:38:11 [13085] [0] DEBUG: Started thread 5 (gw/bb_boxc.c:sms_to_smsboxes) 2004-09-16 09:38:11 [13085] [0] DEBUG: Started thread 6 (gw/bb_boxc.c:smsboxc_run) 2004-09-16 09:38:11 [13085] [0] INFO: DLR rerouting for smsc id modem disabled. 2004-09-16 09:38:11 [13085] [0] INFO: AT2[modem]: configuration shows modemtype wavecom 2004-09-16 09:38:11 [13085] [0] DEBUG: AT2[modem]: Reading modem definitions from /etc/kannel.conf 2004-09-16 09:38:11 [13085] [0] DEBUG: AT2[modem]: Found 1 modems in config 2004-09-16 09:38:11 [13085] [0] INFO: AT2[modem]: read modem definition for Wavecom 2004-09-16 09:38:11 [13085] [0] DEBUG: Started thread 7 (gw/smsc/smsc_at.c:at2_device_thread) 2004-09-16 09:38:11 [13085] [0] DEBUG: Started thread 8 (gw/bb_smscconn.c:sms_router) 2004-09-16 09:38:11 [13085] [0] INFO: 2004-09-16 09:38:11 [13085] [0] INFO: Kannel bearerbox II version 1.3.2 starting 2004-09-16 09:38:11 [13085] [1] DEBUG: Thread 1 (gw/bb_store.c:store_cleanup) maps to pid 13085. 2004-09-16 09:38:11 [13085] [2] DEBUG: Thread 2 (gwlib/fdset.c:poller) maps to pid 13085. 2004-09-16 09:38:11 [13085] [7] DEBUG: Thread 7 (gw/smsc/smsc_at.c:at2_device_thread) maps to pid 13085. 2004-09-16 09:38:11 [13085] [7] INFO: AT2[modem]: trying to use speed 9600 from modem definition 2004-09-16 09:38:11 [13085] [7] INFO: AT2[modem]: opening device 2004-09-16 09:38:11 [13085] [7] DEBUG: AT2[modem]: device opened 2004-09-16 09:38:11 [13085] [7] DEBUG: AT2[modem]: device opened 2004-09-16 09:38:11 [13085] [7] INFO: AT2[modem]: speed set to 9600 2004-09-16 09:38:11 [13085] [7] DEBUG: AT2[modem]: -- ^M 2004-09-16 09:38:11 [13085] [8] DEBUG: Thread 8 (gw/bb_smscconn.c:sms_router) maps to pid 13085. 2004-09-16 09:38:11 [13085] [0] INFO: Loading store file `/tmp/kannel.store' 2004-09-16 09:38:11 [13085] [0] INFO: Store-file size 389, starting to unpack 2004-09-16 09:38:11 [13085] [0] INFO: Retrieved 1 messages, non-acknowledged messages: 1
Re: WAP ALerts
Srinivas Munagala wrote:
Hi Aarno,
Thanks for your reply .Yes i am using Kannel PPG.
I figured out the problem. The problem is not with parameters it
is with the length of the URL.
I decreased the length of the url
http://server/VisitorManager/visitor.aspx?
http://server/VisitorManager/visitor.aspx?v=11 v=11 to
http://server/vman/visitor.aspx? http://server/vman/visitor.aspx?v=11
v=11 which is working fine
with all mobile handsets.
Please let me know if i am wrong in conclusion that problem is
with length of URL.
now in PPG specs the URL is not limited in such a way. Let me guess
here to a different position regarding the error. I guess that then
you use the long version with v=11 you get a splitted (concatenated)
SMS message, which means 2 segments. Right?
And either we (Kannel) or the phone has a problem to re-catenate it
again an interpret it correctly.
That's why it works, when you reduce the length of the URL, but still
use v=11 as parameter.
Only a guess. See in your access.log if the messages have been send as
concatenated ones.
AND BTW, DON'T CROSS-POST TO LISTS!
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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-
[RFC] adding solaris lib dependencies
Hi list,
just a quick RFC for adding lib dependency checks for solaris
sem_foobar() functions implemented in librt.a, in reference to bug #154.
This may be added to configure.in and hence made more smooth for users
that compile on solaris systems.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: [RFC] adding solaris lib dependencies
Alexander Malysh wrote:
Hi,
how about attached patch?
yes, but do we need to include the lib on our own in $LIBS before
configure runs the Makefile.in mangle and substitutes the vars?! Or is
it enough to call AC_CHECK_LIB() and it will include it on its own?
Not sure.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
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: [RFC] adding solaris lib dependencies
Alexander Malysh wrote:
Stipe Tolj wrote:
Alexander Malysh wrote:
Hi,
how about attached patch?
yes, but do we need to include the lib on our own in $LIBS before
configure runs the Makefile.in mangle and substitutes the vars?! Or is
it enough to call AC_CHECK_LIB() and it will include it on its own?
it's enough to call AC_CHECK_LIB()...
ok, then ++1 from me.
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: [RFC] adding solaris lib dependencies
Alexander Malysh wrote:
Stipe Tolj wrote:
Enver ALTIN wrote:
It would be a bit better to be under or over semaphore support checks.
hmm, parse error ;)
it's now over semaphore support check, what ist a problem here?
Also, we might want to check the *-hpux-* or, sunos part of uname
output, just to be sure this change doesn't affect other systems which
don't need librt (although autoconf/configure is supposed to handle
that).
if librt is not needed on some systems then it will not be included (see
autoconf docs ;))...
basically I'd like to go with Enver's idea to put it in the case
$host block, like we did for the libc_r.a and likse.a for OpenBSD
and FreeBSD.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: [RFC] adding solaris lib dependencies
Stipe Tolj wrote:
basically I'd like to go with Enver's idea to put it in the case $host
block, like we did for the libc_r.a and likse.a for OpenBSD and FreeBSD.
but consider this more as a +0 option. ;)
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: Test message
Nick Clarey wrote: This is a test me too.
Re: Kannel tested on Red Hat Linux 9 ?
Thomas Göttgens wrote:
Hello,
KM This reminds: could we get new stable release at some point?
KM (new devel release wouldn't hurt that much either ... no matter
KM if there has not been many updates, we could simply say like
KM '1.3.3 is almost like 1.3.2, no need to upgrade unless...)
[...]
KM New releases would also be a good sign to show that the project is alive
KM and kicking.
Agreed. If you do, can you please incorporate the sqlbox patch by Rene Kluwen? the latest
version has been working here on a small production system for 2 weeks now, handling about 400
SMS/day on an EMI/UCP link. It's the only way to feed larger quantities of MT SMS into the
system without much delay. The system here is primarily used to send alarm-pager sms
to fire fighters, paramedics, etc. so the immediate processing even of larger quantities is
quite important to me :)
i'd be willing to hack up a documentqation diff on this box if this is hindering incorporation into the main codeline.
the sqlbox should go into cvs *after* 1.4.0 stable has been declared.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
[ANNOUNCE] Kannel 1.4.0 stable release available
The Kannel Group is pleased to announce the availability of the Kannel 1.4.0 stable release via the project web site http://www.kannel.org/ -- NEWS about Kannel: Open Source WAP and SMS Gateway version 1.4.0 This is a STABLE version. It should be usable for production systems. Please do report problems to the Kannel bug tracking system available at http://bugs.kannel.org/ or send a mail to [EMAIL PROTECTED] (the development mailing list). Changes since version 1.3.2: Compatibility breakers: * fakesmsc switching from -p to -r for port, since -p is used for pid-file creation. This broke fakesmsc to use an other port then the default 1 to connect to the smsc_fake module of bearerbox. New features: * Added ability to start/stop/restart of all smscconn's that have equal smsc-id's instead of only one. * Implemented very simple priority queue ala Robert Sedgewick for gwlib. * Implemented concatenation of large sms inside bearerbox and does care of sending all message parts over one smsc link. Now we have a problem with concatenated large sms that bearerbox will try to load balance those over different smsc links and such messages arrive as junk (all parts of concatenated large sms must go through the same smsc). * SMPP added ESME dlr bit to DLR processing, added setting of sms priority flag in smsbox and smpp module. * bruNET upgrading response parsing to comply with more recent interface version (v2.0+) where bruNET delivers 'MessageId' in the HTTP response body. * AT, EMI usage of the of priority queue and priority flag. * URLTranslation added '%o' as escape code for MO msgs representing the msg-sms.account field. Which is interpreted as the operator ID for aggregator specific MO messages. ie. Xidris HTTP SMSC module. * test_ppg added support for X-WAP-Initiator-URI, use -I option. Bugfixes: * SMPP fixed panic on NULLed source_addr/destination_addr, for nulterminated string length checking of PDU elements, bug that dlr lookup was made with source instead of destination address (in dlr source and destination switched), fixed incorrect handling of GSM_ADDR_TON_ALPHANUMERIC for destination address, * AT fixed segfault when modemtype is set to 'auto' or 'autodetect', fixed '+CPIN', some modem needs ''. * HTTP fixed a binary MT bug (when DC_8BIT has been set) and various improvements for passing parameters to the HTTP request, fixing 3united (formerly Xidris) HTTP interface for binary MT messages. We passed URL-encoded binary string, but server side expected HEX encoded (2 char per byte) version. * WSP string coding bug fixed. * WML compiler fixed panic for certain DOCTYPE definitions, memory leak fixed. * XMLRPC fixed memory leak. * Fixed ISO date handling. * Fixed double encoding in smsbox when trans coding from UCS2 to UTF-8 or ISO-8859-1. * Improved pthread reader/writer-locks. * Fixed usage of native semaphores on MacOS X to avoid a not implemented error. * Fixed pthread lib settings for FreeBSD 5.2.1. * Added check for 'sem_init' in librt. This needs on Solaris HP-UX. * Fixed Linux version of gw_gethostbyname when gethostbyname_r failed. Also free buffer on error. * Fixed daemon mode (make sure stdin/stdout/sdterr are opened and do chdir(/)) and change user code (set supplementary group id's and don't destroy passwd struct). * Bug work-around causing segfault on cygwin while using uninited rwlock functions. * Various memory leak and double free fixes.
Re: ... Kannel 1.4.0 stable release available
Kalle Marjola wrote:
Thanks Stipe!
ohh.. please, no vine for me... it's been more then necessary ;)
Now I propose that we add to CVS head:
* new smsstore (that directory thing I guess, unfortunately I have had
no time to test it... is there limit to how many files can be in a
directory?)
* reply-to-sendsms (this patch I did, I can fig that horrible kludge
first)
* other pending new features...?
yep, +1
..and then get 1.5.0 out quite soon (this year?)
++1 ;)
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: ... Kannel 1.4.0 stable release available
Enver ALTIN wrote:
On Thu, 2004-11-25 at 16:35 +0200, Kalle Marjola wrote:
Thanks Stipe!
Yeah, congrats to everybody! Do we have a party soon? :-)
actually we should... but the problem is where? Most of us guys in spread
accross europe ;)
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: [ANNOUNCE] Kannel 1.4.0 stable release available
Hillel Bilman wrote:
Dear Kannel Devel,
Well done on the latest Kannel stable release.
thanks a lot. I have to add my thanks to all developers who made improvements
into Kannel possible and to the numerious people using the software and
reporting bugs... this is what open source is all about... contribution to the
community ;)
I have a few questions on the release:
1) In the article below you have said: bruNET upgrading response parsing to
comply with more recent interface version (v2.0+) where bruNET delivers
'MessageId' in the HTTP response
body.
Does this mean there is a new DLR escape code that allows one to get the
MessageId from the SMSC before the SMS has been delivered to the phone and
before the final dlr? If this is not the case, what does bruNET delivers
'MessageId' in the HTTP response mean? This is a function that the
devel team is looking into it?
speaking in Kannel internals, this means the MessageId response parameter is
passed into the 'binfo' field of the Msg structure. Hence, yes, there is a
generic URL trans escape code for getting the binfo field from specific SMSC
implementations. bruNET uses this MessageId for further transactions to
distinguish billing information... (don't want to go into details here).
So, there is _no_ new field or escape code for it.
2)I've been continually updating to the latest cvs and found it stable. Now
that the 1.4.0 release is
available is this a snapshot of the 1.3.2 development CVS? and if I keep
getting the CVS every few weeks, will it be an improvement to the 1.4.0
stable version?
yes, 1.4.0 is actually a snapshot of the CVS HEAD tree from the specific release
date.
We're now tending to seperate things again. There are a lot of new (huge)
patches waiting. They will make their way into CVS HEAD. The 1.4 stable branch
will contain only bugfixes to the current 1.4.0. So you can illustrate it via this:
1.4.0 --- 1.4 stable branch (bugfixes only, no new logic)
--- cvs head, all new and also experimental code
So you should be reviewing the cvs commits, via devel-reports@ mailing list. As
soon as we commit huge changes/patches, you're obviously not anymore on the
safe side, you should then switch to the 1.4 branch.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
[REQ] commiting bugfixes to stable 1.4 branch
Hi list,
for all developers with cvs access, please obey to commit bugfixes that are
logically fixing issues in the current 1.4.0 stable release to _both_ branches:
HEAD and stable_1_4_0
We will use the stable_1_4_0 branch to release an updated stable release called
1.4.1 after some fixes have been applied.
Feature adds and things that are new should go into HEAD. Fully experimental
code should go into an own branch, as Alex did this for the new autoconf stuff.
Is this policy ok for all? I just want to prevent to mess up the HEAD branch,
when releasing 1.4.1 (stable) and have code inside that is yet not fully
tested or something similar.
I just commited the gwli/[conn|http|charset].c commits to the stable_1_4_0
branch.
Comments please?! ;)
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: Some where is the implementation ?
Oscar Medina Duarte wrote:
Hello,
Just with a simple fast question for the proper guy to answer:
Where is the implementation of :
encode_network_long(char *, long int)
thank's to all !
hmmm... not very tricky to find, simply use a recursive search, and you'll find
the implementation at gwlib/utils.c:740
PS Just to let you know, I'm writing a spec of the current Kannel box
protocol to allow programmers in other langs (like java) to connect to
kannel as a box.
ok, interesting. What kind of spec will it be?
@Alex: what about the python interface Centrium build for Kannel interfacing?
Was it something similiar?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: Maybe a BUG: make: *** [gw/dlr_mysql.o] Error 1 // conflict with MYSQL 4.1.7 ?
ding dingding wrote: ? ?V naually gateway-1.4.0]# ./configure --disable-docs --disable-ssl --with-mysql loading cache ./config.cache Configuring for Kannel gateway version 1.4.0 ... Running system checks ... checking host system type... i686-pc-linux-gnu checking for gcc... (cached) gcc checking whether the C compiler (gcc -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -rdynamic) works... yes checking whether the C compiler (gcc -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -rdynamic) is a cross-compiler... no checking whether we are using GNU C... (cached) yes checking whether gcc accepts -g... (cached) yes checking for a BSD compatible install... (cached) /usr/bin/install -c checking for ranlib... (cached) ranlib checking for bison... (cached) bison -y checking for flex... (cached) flex checking for yywrap in -lfl... (cached) yes checking for convert... no checking for perl... (cached) /usr/bin/perl checking size of short... (cached) 2 checking size of int... (cached) 4 checking size of long... (cached) 4 checking size of long long... (cached) 8 checking for log in -lm... (cached) yes checking for accept in -lsocket... (cached) no checking for inet_ntoa in -lnsl... (cached) yes checking for inet_ntop in -lresolv... (cached) yes checking for inet_ntop in -lbind... (cached) no checking for pthread_exit in -lpthread... (cached) yes checking for libiconv in -liconv... (cached) no checking how to run the C preprocessor... (cached) gcc -E checking for ANSI C header files... (cached) yes checking for sys/ioctl.h... (cached) yes checking for sys/time.h... (cached) yes checking for sys/types.h... (cached) yes checking for unistd.h... (cached) yes checking for sys/poll.h... (cached) yes checking for pthread.h... (cached) yes checking for getopt.h... (cached) yes checking for syslog.h... (cached) yes checking for iconv.h... (cached) yes checking for zlib.h... (cached) yes checking for execinfo.h... (cached) yes checking for stdlib.h... (cached) yes checking for sys/socket.h... (cached) yes checking for sys/sockio.h... (cached) no checking for net/if.h... (cached) yes checking for netinet/in.h... (cached) yes checking for gettimeofday... (cached) yes checking for select... (cached) yes checking for socket... (cached) yes checking for strdup... (cached) yes checking for getopt_long... (cached) yes checking for localtime_r... (cached) yes checking for gmtime_r... (cached) yes checking for backtrace... (cached) yes checking for srandom... (cached) yes checking for getopt... (cached) yes checking for gethostbyname_r... (cached) yes checking for which type of gethostbyname_r... (cached) 6 checking for socklen_t in sys/socket.h... (cached) yes checking for getopt in stdio.h... (cached) no checking for getopt in unistd.h... (cached) yes checking for regex.h... (cached) yes checking for regcomp... (cached) yes Checking for POSIX threads support ... checking for working pthreads... yes checking for pthread_spinlock support... yes checking for pthread_rwlock support... yes checking for sem_init in -lrt... (cached) yes checking for semaphore support... yes Checking for libxml2 support ... checking for xml2-config... (cached) /usr/local/bin/xml2-config checking libxml version... 2.6.16 Configuring for PCRE support ... checking whether to compile with PCRE support... disabled Configuring DocBook support ... checking for jade... (cached) jade checking for jadetex... (cached) no checking for pdfjadetex... (cached) no checking for dvips... (cached) dvips checking for fig2dev... (cached) no checking for convert... (cached) no checking for /usr/lib/sgml/stylesheet/dsssl/docbook/nwalsh/html/docbook.dsl... (cached) no checking for /usr/lib/sgml/stylesheets/nwalsh-modular/html/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets-1.59/html/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets-1.77/html/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets/html/docbook.dsl... (cached) yes checking for /usr/lib/sgml/stylesheet/dsssl/docbook/nwalsh/print/docbook.dsl... (cached) no checking for /usr/lib/sgml/stylesheets/nwalsh-modular/print/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets-1.59/print/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets-1.77/print/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets/print/docbook.dsl... (cached) yes Not building documentation. Configuring parameters ... checking which malloc to use... native malloc enabling local time enabling cookies Configuring OpenSSL support ... checking whether to compile with SSL support... disabled Configuring DB support ... checking whether to compile with MySQL support... searching checking for mysql_config... (cached) /usr/bin/mysql_config checking mysql version... 4.1.7 checking mysql reentrant libs... -L/usr/lib/mysql -lmysqlclient_r -lpthread -lcrypt -lnsl -lm -lpthread -lc -lnss_files
[Fwd: new problem: DLR: storage type 'mysql' is not supported, WHY?]
forwarding to the list.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
---BeginMessage---
Dear Sir
I changed the mysql 4.1.7 down to mysql 4.0.22, OK the conflicting
types for list_delete' problen gone.
I get the 3, Bearerbox Wapbox Smsbox.
but now, new problem comes.
DLR: storage type 'mysql' is not supported,
WHY?
./configure --disable-ssl --disable-docs --with-mysql --with-pgsql
.
..
mysql support yes
pgsql supportyes
..
make
.
..
-L/usr/local/lib -lxml2 -lz -lpthread -lm -L/usr/lib/mysql -lmysqlclient_r
-lpthread -lz -lcrypt -lnsl -lm -lpthread -lc -lnss_files -lnss_dns
-lresolv -lc -lnss_files -lnss_dns -lresolv -L/usr/lib
./utils/foobar-config.sh -I/usr/local/include/kannel -D_XOPEN_SOURCE=600
-D_BSD_SOURCE -I/usr/local/include/libxml2 -I/usr/include/mysql
-I/usr/include \
-L/usr/local/lib/kannel -lgwlib -lpq -lrt -lresolv -lnsl -lm
-lpthread -L/usr/local/lib -lxml2 -lz -lpthread -lm -L/usr/lib/mysql
-lmysqlclient_r -lpthread -lz -lcrypt -lnsl -lm -lpthread -lc -lnss_files
-lnss_dns -lresolv -lc -lnss_files -lnss_dns -lresolv -L/usr/lib \
1.4.0 gw-config
chmod 0755 gw-config
BUT WHEN I RUN
# bearerbox myddsmskannel.conf
.
04-12-04 01:38:32 [11272] [0] INFO: Debug_lvl = -1, log_file = none,
log_lvl = 0
2004-12-04 01:38:33 [11272] [0] PANIC: DLR: storage type 'mysql' is not
supported!
2004-12-04 01:38:33 [11272] [0] PANIC: bearerbox(gw_panic+0x175)
[0x80c7e12]
2004-12-04 01:38:33 [11272] [0] PANIC: bearerbox(dlr_init+0x1ee)
[0x805c40d]
2004-12-04 01:38:33 [11272] [0] PANIC: bearerbox(main+0x18d) [0x8051960]
2004-12-04 01:38:33 [11272] [0] PANIC:
/lib/tls/libc.so.6(__libc_start_main+0xf8) [0xb7341748]
2004-12-04 01:38:33 [11272] [0] PANIC: bearerbox(read+0x51) [0x8050ae5]
Would you please tell me which version kannel works well with which version
mysql ?
my platform is Red hat RHEL_3
mysql: 4.0.22
kannel: 1.4
---End Message---
[REQ] Kannel on FreeBSD? anyone?
Hi list,
Kannel has currently no package maintainer for the FreeBSD port, and it seems
also that Kannel is broken on the FreeBSD alpha64 platform.
Anyone here in the list that has a vital connection/access to an FreeBSD alpha64
machine and could grant the Kannel group/developers access to it for test reasons?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
[RF Hohoho] Season's greetings
Wishing you all that contribute in this great effort that we call Kannel,
a pleasent and warm merry christmas!
We're all looking forward to push Kannel in the next year even one or two steps
further on. ;)
Merry christmas and a happy new year!
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: Kannel Stable release 1.4.0 is not stable
[EMAIL PROTECTED] wrote:
Hello Stipe ,
Hello all,
I'm a very old user for kannel , and I used to compile it on
cygwin-windows 2003 server and it was working fine till compiled the last
stable 1.4.0 then problems started bearerbox takes 100% of the cpu and I
lose the store file if I restarted kannel (all queued messages lost).
I thought that the problem in the cygwin-windows , I decided to go for linux
and I could successfully compile on redhat and I found the same problem
about 80% of the cpu goes for bearerbox and same problem if I restarted the
kannel I lose all queued messages.
Considering that
1-I return to ver 1.3.2rc1 on cygwin-windows system and on redhat system ,
all is fine and no problems cpu is about 2% and all looks so great
2-my kannel.conf was the same in my all tests
I think that something is wrong in the ver. 1.4.0
Hmm. Ok, regarding using Kannel on Cygwin (win32) it is _not_ as stable as on
Linux/UNIX. Cygwin has still problems with the pthread lib and recently we had
issues with rwlocks that Alex introduced for various issues.
But I'm having dubts that this is impacting Linux too. We don't see such load
situations on our machines.
Would you mind to forward the config file for a local test? Can you describe if
the cpu load situation can be reproduced deterministical?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Dsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: Too many processes
Enver ALTIN wrote:
Hi,
On Mon, 2004-12-27 at 13:13 -0600, Oscar Medina Duarte wrote:
I've compiled kannel on debian 3.1 and ran the same config I'm runing
in other versions of debian, Fedora and MAC OS X, but the different
thing here is that it makes around 9 processes only for the bearerbox!
They're threads, not processes.
yep, some distros of Linux tread the 'ps', 'top' command listings different for
threads.
BTW, Kannel outputs the thread pid into the standard debug line, so you have a
reference to the ps listsings which thread actually is running what and what the
cpu consumption is, in case you're debugging.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: [PATCH] Kannel bug #0000032 otherwise known as kannel's list function naming clashes with latest mysql list function naming
Davy Chan wrote:
I've submitted a patch for bug #032 to the Mantis bug tracking
system. It's 381K in size. Should I submit it also to the devel
mailing list?
This patch does not have the renaming of all List structures to
gw_List. If the list_XXX to gw_list_XXX patch is accepted,
then I'll also do the List structures patch.
yes, please provide the patch in unified diff format as attachement, not
inlined.
Mark it via the [PATCH] subject line prefix so developers can review it. Since
it's quite big, a gziped version may be prefered I guess. ;)
Please explain also what you do inside the patch. Consider those explanations as
'helping hand' to those that take time to review your patch and vote for
commiting. Thanks in advance.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: Win32 version
Edgar Zavala wrote:
I compiled succesfully some time ago Kannel using the Cywin
(http://www.cygwin.com) development tools on Windows 2000 server and
it work great, i used the irComm driver from (http://www.ircomm2k.de/)
and a T68i cell phone as ir modem to send and receive SMS messages.
confirming. Cygwin can be used for Kannel on Win32. Unfortunatly Cygwin has some
problems with the internal pthread library. Hence there are thread mutex problem
on that platform. It's not supposed to be declared stable for production (and
high-load) systems.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: [PATCH] Kannel bug #0000032 otherwise known as kannel's list function naming clashes with latest mysql list function naming
Alexander Malysh wrote:
Hi,
Davy Chan wrote:
Well, it's been about 12 days since I tried to submit the patch
but it still has not been acted on by the moderator of the
devel@kannel.org mailing list.
I'm not aware of any moderator...
our mailing list moderator is equal to the system admin at Trigenix,
it is James Chew [EMAIL PROTECTED].
Are there any other suggestions on how to submit this patch
for review?
mantis should fine... the patch is just too big and need some time for
review...
agreed, either mantis. Or (if you have the possibility) put it on a HTTP server
and reference it via the mailing list or mantis.
I've already uploaded the patch to the Mantis Bug tracking system.
Would it be possible for the reviewer to grab the patch from
there instead of waiting for the list moderator to release my 12
day old posting?
Ok, we'll grab it from mantis for review. I had a (very) quick shot on it, but
that was more something informal. Stay tuned.
@Stipe: could you please ask by trigenix guys about it?
just CC'ed James.
@James: there has been a patch submission which seems to get blocked because of
the size. Is the size limit reasonable? If you feel it's too low, please upgrade
it if possible. Many thanks in advance.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: [PATCH] gwmem-check: add backtrace support
Alexander Malysh wrote:
Hallo together,
attached you can find a patch that adds backtrace support to gwmem-check.
w/o backtrace is this module really hard to use.
Comments and votes please!
reviewed and tested. Looks good. +1 for cvs commit.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: [PATCH] http server fixes
Kalle Marjola wrote:
Looks great, and this is a _must_ for 1.4.1 I think.
1.4.1 and 1.5.0 would be nice to get out at some point.. we
did not get it out before end of the year but how about now?
ok, which means we release 1.4.1 stable as stable update to 1.4.0. +1 on
this.
What about 1.5.0 as development release with the new autoconf build etc?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: [PATCH] http server fixes
Alexander Malysh wrote:
Kalle Marjola wrote:
On Thu, 2005-01-20 at 17:26, Alexander Malysh wrote:
Hi Kalle,
I don't think it's the right time now. see mantis ML (users and devel)
for bugs that should be fixed first...
As I know it takes some time to get it finally out, my comment meant
mainly 'let's try to get it out, with current features but bugfixing
them first' :]
sure, +1 from me!
+1 too.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: [PATCH] http server fixes
Enver ALTIN wrote:
Hi,
On Thu, 2005-01-20 at 16:46 +0100, Stipe Tolj wrote:
1.4.1 and 1.5.0 would be nice to get out at some point.. we
did not get it out before end of the year but how about now?
ok, which means we release 1.4.1 stable as stable update to 1.4.0. +1 on this.
I think we need to share a list of known issues that need to be fixed
for 1.4.1, and release 1.4.1 when the list is cleared-up.
yep, the apache guys call this issues the show-stopers. Which means next
release is scheduled when all show-stopers are fixed.
Can't we addopt this within mantis itself?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: [PATCH] http server fixes
Enver ALTIN wrote:
Hi,
On Thu, 2005-01-20 at 16:46 +0100, Stipe Tolj wrote:
1.4.1 and 1.5.0 would be nice to get out at some point.. we
did not get it out before end of the year but how about now?
ok, which means we release 1.4.1 stable as stable update to 1.4.0. +1 on this.
I think we need to share a list of known issues that need to be fixed
for 1.4.1, and release 1.4.1 when the list is cleared-up.
an idea to mark the bugs that are show-stoppers for next stable 1.4.x releases
is to threat the severity value block as such marking.
Comments on that?
It's not very sexy, I have to admit. But I don't see an other ability to
declare bugs to show-stoppers in order to have an accurate TODO list for bugs.
Anyone else something in mantis?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: [PATCH] Siemens SX1 kludge
Hi Paul,
instead of pocking arround in the wsp_field_value() prototype like in your
patch, I'd suggest the following patch, that should work IMO for any generic
header type that is 0x00'ed for the value.
Can you test with SX1 and confirm? It would be more cleaner IMO.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Index: wap/wsp_headers.c
===
RCS file: /home/cvs/gateway/wap/wsp_headers.c,v
retrieving revision 1.19
diff -u -r1.19 wsp_headers.c
--- wap/wsp_headers.c 8 Aug 2004 20:39:56 - 1.19
+++ wap/wsp_headers.c 21 Jan 2005 01:11:50 -
@@ -110,7 +110,7 @@
unsigned long len;
val = parse_get_char(context);
-if (val = 0 val 31) {
+if (val 0 val 31) {
*well_known_value = -1;
parse_limit(context, val);
return WSP_FIELD_VALUE_DATA;
@@ -126,7 +126,7 @@
*well_known_value = -1;
/* We already consumed the Quote */
return WSP_FIELD_VALUE_NUL_STRING;
-} else {
+} else {/* implicite val == 0 */
*well_known_value = -1;
/* Un-parse the character we just read */
parse_skip(context, -1);
Re: [PATCH] Siemens SX1 kludge
Vjacheslav Chekushin wrote:
Just remark.
SX1 behavior _NOT_ conforms to wap specification, because besides general
encoding there is well-known encoding for Accept header:
8.4.2.7 Accept field
The following rules are used to encode accept values.
Accept-value = Constrained-media | Accept-general-form
Accept-general-form = Value-length Media-range [Accept-parameters]
Media-range = (Well-known-media | Extension-Media) *(Parameter)
Accept-parameters = Q-token Q-value *(Accept-extension)
Accept-extension = Parameter
Constrained-media = Constrained-encoding
Well-known-media = Integer-value
; Both are encoded using values from Content Type Assignments table in
Assigned Numbers
Q-token = Octet 128 )
And we have: Accept-general-form = Value-length Media-range
[Accept-parameters]
So value-length is 0 and Media-range (mandatory) is absent.
So Accept header must be either as string Accept: ... or 80 ...
and in the last case it _MUST_ be encoded as Accept-value.
ok, agreeing for the 'Accept-value = Constrained-media | _Accept-general-form_'
value. _BUT_ what about _Constrained-media_?
If comes up to Extension-media where the reference BNF is used. IMO the Accept
encoded byte 0x80 followed by a 0*TEXT (hence nothing), followed by a
end-of-string 0x00 is allowed then.
Comments on this please.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: [PATCH] Siemens SX1 kludge
Stipe Tolj wrote:
Hi Paul,
instead of pocking arround in the wsp_field_value() prototype like in
your patch, I'd suggest the following patch, that should work IMO for
any generic header type that is 0x00'ed for the value.
Can you test with SX1 and confirm? It would be more cleaner IMO.
any active votes on commiting this patch to cvs?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: WTLS?
Hi Marcus,
Marcus Schmöger wrote:
Hi,
I would like to know about the current status of WTLS integration into
Kannel.
The info on the website is somewhate ambiguous about this.
At http://www.kannel.org/addons.shtml one of the three addons (the one
from 3ui) is not available anymore.
It is still available via
http://www.kannel.org/download/wtls/
At http://www.kannel.org/roadmap.shtml#projects the text says, that 3G
LAB is working on adding this and plans to have it ready in May. May of
which year, please?
now, 3G LAB (now Trigenix) has been working on the WTLS stack in Kannel and
there have been certain parts integrated already, see wap/wtls* source files.
Unfortunatly it's yet not functional.
If you consider in adding WTLS abilities to Kannel I may advice to take the
kwtls sources and addopt them to the existing WTLS stack sources in Kannel's tree.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
[HELP] WTLS stack?
Hi list,
any crypto gurus arround who are willing to pick up the WTLS code for review and
adding the kwtls (external add-on module) to the existing code?
See Mantis bug#038 and http://www.kannel.org/download/wtls/ for more details on
the WTLS stack.
I'd like to see this getting going to someone who is eager to dig his head into
crypto stuff and get Kannel WTLS-enabled. I'd expect that it is not too much
work to do, since kwtls works in some extend. Only code reviewing and cutting
things together is the major thing about the task.
Anyone interested?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: [PATCH] bb_boxc: popup threads after accept
Alexander Malysh wrote:
Hi together,
attched you can find a patch that change behaviour in communication thread
creation. With this patch threads are created only _after_ successful
accept and so eliminate possible DOS (IMHO: it's unwise to popup thread
before check whether this box allowed/denied).
Comments and votes please!
post-cvs-commit review: +1
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: [PATCH] Bug #0000168 checks/check_ppg.sh: test: argument expected
Stefan Radman wrote:
Hi,
I've submitted a bug to the Mantis system and followed up with a patch
(attached to the bug).
Can someone review the patch and see if it's acceptable?
Alex seems to be very busy ;-)
All the necessary info is in the bug track.
commited to cvs, in slightly reduced form.
Thanks a lot for submission.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: [PATCH] WSP headers with end-of-string value
Aarno Syvänen wrote:
Have you tested the modification ? What will be result of parsing 0x80
0x00 ? Accept:empty string
is ok according the rfc 2616. (Because this is a low level parsing
function, you definitely want to test.)
Aarno, did you have chances to test this with various phones?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: Config-based Optional Parameter Functionality
Peter Beckman wrote:
Dear Kannel Developers:
I've written about this before, but I thought I would bring it up again
because I hate patching.
Many SMSC's are starting to use the optional SMPP parameters for
information like billing issues, carrier failures, etc. Kannel really
doesn't allow for this -- it detects the parameters, but is unable to
actually turn them into some sort of passable escape code(s) via
sms-service.
Take for example this log dump:
2005-01-27 16:46:56 [30186] [7] DEBUG: Optional parameter tag (0x0427)
2005-01-27 16:46:56 [30186] [7] DEBUG: Optional parameter length read as 1
2005-01-27 16:46:56 [30186] [7] DEBUG: Optional parameter tag (0x001e)
2005-01-27 16:46:56 [30186] [7] DEBUG: Optional parameter length read as 29
2005-01-27 16:46:56 [30186] [7] DEBUG: Optional parameter tag (0x1402)
2005-01-27 16:46:56 [30186] [7] DEBUG: Optional parameter length read as 1
2005-01-27 16:46:56 [30186] [7] DEBUG: Optional parameter tag (0x1404)
2005-01-27 16:46:56 [30186] [7] DEBUG: Optional parameter length read as 22
2005-01-27 16:46:56 [30186] [7] ERROR: SMPP: Unknown
TLV(0x1404,0x0016,4154265420576972656c657373205365727669636573) for PDU
type (deliver_sm) received!
2005-01-27 16:46:56 [30186] [7] DEBUG: Optional parameter tag (0x1530)
2005-01-27 16:46:56 [30186] [7] DEBUG: Optional parameter length read as 3
2005-01-27 16:46:56 [30186] [7] ERROR: SMPP: Unknown
TLV(0x1530,0x0003,504244) for PDU type (deliver_sm) received!
2005-01-27 16:46:56 [30186] [7] DEBUG: Optional parameter tag (0x1531)
2005-01-27 16:46:56 [30186] [7] DEBUG: Optional parameter length read as 90
2005-01-27 16:46:56 [30186] [7] ERROR: SMPP: Unknown
TLV(0x1531,0x005a,4e6f2050686f6e65204e756d6265723a20537562736372696265722070686f6e65206e756d62657220776173206e6f74206d617463686
56420696e2074686520515073732073797374656d206f722041575320506f7274616c20)
for PDU type (deliver_sm) received!
2005-01-27 16:46:56 [30186] [7] DEBUG: Optional parameter tag (0x1532)
2005-01-27 16:46:56 [30186] [7] DEBUG: Optional parameter length read as 6
2005-01-27 16:46:56 [30186] [7] ERROR: SMPP: Unknown
TLV(0x1532,0x0006,2d3230313030) for PDU type (deliver_sm) received!
2005-01-27 16:46:56 [30186] [7] DEBUG: Optional parameter tag (0x1533)
2005-01-27 16:46:56 [30186] [7] DEBUG: Optional parameter length read as 90
2005-01-27 16:46:56 [30186] [7] ERROR: SMPP: Unknown
TLV(0x1533,0x005a,4e6f2050686f6e65204e756d6265723a20537562736372696265722070686f6e65206e756d62657220776173206e6f74206d617463686
56420696e2074686520515073732073797374656d206f722041575320506f7274616c20)
for PDU type (deliver_sm) received!
2005-01-27 16:46:56 [30186] [7] DEBUG: SMPP[mysmsc]: Got PDU:
2005-01-27 16:46:56 [30186] [7] DEBUG: SMPP PDU 0xb5c9a5e0 dump:
2005-01-27 16:46:56 [30186] [7] DEBUG: type_name: deliver_sm
2005-01-27 16:46:56 [30186] [7] DEBUG: command_id: 5 = 0x0005
2005-01-27 16:46:56 [30186] [7] DEBUG: command_status: 0 = 0x
2005-01-27 16:46:56 [30186] [7] DEBUG: sequence_number: 877 = 0x036d
[...]
My dream for the config file:
group = smsbox
smsc-id = mysmsc
[...]
optparam = 0x1404:22:N:billerr_msg
optparam = 0x1530:3:M:happy_tag
optparam = 0x1531:90:K:secret_code
optparam = 0x1532:6:J:test_msg_id
optparam = 0x1533:90:L:secret_code2
Now the following takes place:
When an SMS arrives, it can be passed to sms-service, using %N, %M, %K,
%J and %L (assuming those are available), so I can grab them with a PHP
script and do something with them.
When submitting an SMS to kannel, I can set the URL to:
http://localhost:13013/cgi-bin/sendsms?user=[...]billerr_msg=you+spent+too+muchhappy_tag=funtext_msg_id=123FFF
And kannel will modify the PDU to include the data passed and send that
to the SMSC.
now, this approach does not handle on how you pass the SMPP specific optional
parameters in the Kannel internal msg structure to smsbox.
I see (and I agree) that we may have a generic way in passing SMSC specific
optional parameters up to the application layer and vice versa. But it should be
as clean as possible and transparently configurable for all SMSC protocols.
Therefore we need a sort of Dict that contains key:value pairs within the msg
structure. Any ideas on how we could handle this? Alex?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: AW: WAP test set up with Kannel gateway
Pommnitz, Jörg wrote:
Never tried this, but shouldn't it be possible to access Kannel either
through
Bluetooth or IRDA as well? It should not really be necessary to connect
through
the PLMN.
Did anybody ever try this?
nop. But from theory aspect this should be possible. Since Kannel doesn't care
about the lower IP-stack layer, and how it is physically provided. But I guess
it's up to the phone if it is capable of providing the IP-stack to the phone os
using IRDA or Bluetooth.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: version string and configure
fred wrote:
after doing a ./configure the version string is always cvs-, ( not
building from kannels cvs)
my usual procedure is to then edit gw-config.h and change the #define
GW_VERSION
to something descriptive to our version.
This is a real problem and pain in the ... when i am copying the same source
to different machines and doing
./configure -- the version string is again lost, this is getting
problematic;
??? the version string is contained as first line of the VERSION file. If you
have cvs in there then it's obviously a cvs snapshot.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
