Re: What's the SAR status ??
We are using SAR here at Global Network Inc for wap gateway serving our mmsc. It works quite fine. Aarno On Thursday, February 27, 2003, at 05:23 AM, [EMAIL PROTECTED] wrote: hi all ! We've seen some of SAR patches moving around. I think newer kannel version(1.2.1) supports it. Has anybody tested this functionality with newer gateways ? Or are they still developing SAR ? Does anyone have a new patch ? urs, denzel.
Re: [PATCH] trivial dcs_to_fields fix
Alexander Malysh wrote: attached patch should fix dcs_to_fields and versus functions. The problem: assume you got dcs=0xf5 in your smpp/ucp triber. Simple call: dcs = 0xf5; dcs_to_fields(dcs,msg); filds_to_dcs(msg, msg-sms.alt_dcs); And look what happens ;) Please apply... that patch would change the alt_dcs behaviour from alt_dcs = 0 to alt_dcs = 1 for all MT messages. Specifically we would default the 'alt-dcs' config directive of the smsc group to 1 instread of 0. Any comments/votes from the others?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: What's the SAR status ??
Aarno Syvänen wrote: We are using SAR here at Global Network Inc for wap gateway serving our mmsc. It works quite fine. yep, we to at Wapme. :)) SAR is working fine within Kannel. There will be some further extentions to ESAR, but that's still in development in some sense. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Does Kannel log support logrotation (configure.in patch)
Alan McNatty wrote: Sorry - missed an check to see if --enable/disable-docs had been set. As is configure.in yep, +1, commited to cvs. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: bug in smsc_smpp.c login failure
Alan McNatty wrote: On Thu, 2003-02-27 at 18:54, Nisan Bloch wrote: Hi At 03:46 PM 2/27/03 +1300, Alan McNatty wrote: Hello, found that if I type in the smpp password incorrectly kannel loops forever trying to reconnect. ie: -1 from me In the current form this path will not allow any retries for any sort of bind error. eg what happens if there is a temporary connectivity issue, or the SMPP server is down for a short while/ What I'm trying highlight is that there is a gap in logic .. Currently regardless of the type of error we continually retry to bind. If we specifically receive an error indicating the password is invalid the SMSC is obviously up but we may as well kill the thread. yep, that's true in some sense. Trying to reconnect forever while we get the error information from the SMSC that we can't login with that credentials *could* be considered as login abuse :) At least I would consider this if our SMPP clients would hammer our SMPP server with invalid credentials. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
RE: What's the SAR status ??
What about NACK request? It seems to me that it is not yet implemented. Or maybe I missed it? I'm using this feature from Danzel's patch. Look at Igor's post few months ago: http://www.mail-archive.com/[EMAIL PROTECTED]/msg05978.html Damir -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Stipe Tolj Sent: 27. veljaca 2003 10:22 To: Aarno Syvänen Cc: [EMAIL PROTECTED]; kannel-mailing-list Subject: Re: What's the SAR status ?? Aarno Syvänen wrote: We are using SAR here at Global Network Inc for wap gateway serving our mmsc. It works quite fine. yep, we to at Wapme. :)) SAR is working fine within Kannel. There will be some further extentions to ESAR, but that's still in development in some sense. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
RE: What's the SAR status ??
Title: RE: What's the SAR status ?? Yes, it's not implemented yet -Original Message- From: Damir Salantic [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 27, 2003 11:40 AM To: 'Stipe Tolj'; 'Aarno Syvanen' Cc: [EMAIL PROTECTED]; 'kannel-mailing-list' Subject: RE: What's the SAR status ?? What about NACK request? It seems to me that it is not yet implemented. Or maybe I missed it? I'm using this feature from Danzel's patch. Look at Igor's post few months ago: http://www.mail-archive.com/[EMAIL PROTECTED]/msg05978.html Damir -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Stipe Tolj Sent: 27. veljaca 2003 10:22 To: Aarno Syvänen Cc: [EMAIL PROTECTED]; kannel-mailing-list Subject: Re: What's the SAR status ?? Aarno Syvänen wrote: We are using SAR here at Global Network Inc for wap gateway serving our mmsc. It works quite fine. yep, we to at Wapme. :)) SAR is working fine within Kannel. There will be some further extentions to ESAR, but that's still in development in some sense. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] generic support for our-host smsc directive
commited to cvs. Thanks Angel. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: bug in smsc_smpp.c login failure
Hi,
what about attached patch ?
Am Donnerstag, 27. Februar 2003 10:30 schrieb Stipe Tolj:
Alan McNatty wrote:
On Thu, 2003-02-27 at 18:54, Nisan Bloch wrote:
Hi
At 03:46 PM 2/27/03 +1300, Alan McNatty wrote:
Hello,
found that if I type in the smpp password incorrectly kannel loops
forever trying to reconnect. ie:
-1 from me
In the current form this path will not allow any retries for any sort
of bind error. eg what happens if there is a temporary connectivity
issue, or the SMPP server is down for a short while/
What I'm trying highlight is that there is a gap in logic ..
Currently regardless of the type of error we continually retry to bind.
If we specifically receive an error indicating the password is invalid
the SMSC is obviously up but we may as well kill the thread.
yep, that's true in some sense. Trying to reconnect forever while we
get the error information from the SMSC that we can't login with that
credentials *could* be considered as login abuse :)
At least I would consider this if our SMPP clients would hammer our
SMPP server with invalid credentials.
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf
Tel: +49-211-74845-0
Fax: +49-211-74845-299
E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are
--
Best regards / Mit besten Grüßen aus Köln
Dipl.-Ing.
Alexander Malysh
___
Centrium GmbH
Ehrenstraße 2
50672 Köln
Fon: +49 (0221) 277 49 240
Fax: +49 (0221) 277 49 109
email: [EMAIL PROTECTED]
web: www.centrium.de
msn: [EMAIL PROTECTED]
icq: 98063111
Index: gw/smsc/smsc_smpp.c
===
RCS file: /home/cvs/gateway/gw/smsc/smsc_smpp.c,v
retrieving revision 1.25
diff -a -u -r1.25 smsc_smpp.c
--- gw/smsc/smsc_smpp.c 23 Feb 2003 11:35:34 - 1.25
+++ gw/smsc/smsc_smpp.c 27 Feb 2003 10:25:35 -
@@ -62,6 +62,8 @@
*/
enum {
+SMPP_ESME_RINVPASWD = 0x000E,
+SMPP_ESME_RINVSYSID = 0x000F,
SMPP_ESME_RMSGQFUL= 0x0014,
SMPP_ESME_RTHROTTLED = 0x0058,
SMPP_ESME_RX_T_APPN = 0x0064,
@@ -958,6 +960,9 @@
code 0x%08lx.,
octstr_get_cstr(smpp-conn-id),
pdu-u.bind_transmitter_resp.command_status);
+if (pdu-u.bind_transmitter_resp.command_status == SMPP_ESME_RINVSYSID ||
+pdu-u.bind_transmitter_resp.command_status == SMPP_ESME_RINVPASWD)
+smpp-quitting = 1;
} else {
*pending_submits = 0;
smpp-conn-status = SMSCCONN_ACTIVE;
@@ -972,6 +977,9 @@
code 0x%08lx.,
octstr_get_cstr(smpp-conn-id),
pdu-u.bind_transceiver_resp.command_status);
+if (pdu-u.bind_transceiver_resp.command_status == SMPP_ESME_RINVSYSID ||
+pdu-u.bind_transceiver_resp.command_status == SMPP_ESME_RINVPASWD)
+smpp-quitting = 1;
} else {
*pending_submits = 0;
smpp-conn-status = SMSCCONN_ACTIVE;
@@ -986,6 +994,9 @@
code 0x%08lx.,
octstr_get_cstr(smpp-conn-id),
pdu-u.bind_receiver_resp.command_status);
+if (pdu-u.bind_receiver_resp.command_status == SMPP_ESME_RINVSYSID ||
+pdu-u.bind_receiver_resp.command_status == SMPP_ESME_RINVPASWD)
+smpp-quitting = 1;
} else {
/* set only resceive status if no transmitt is bind */
if (smpp-conn-status != SMSCCONN_ACTIVE) {
Re: [PATCH] admin http 'loglevel' command for bearerbox
+1 from me. Looks great and very handy. - Original Message - From: Angel Fradejas To: Kannel Developers Sent: Thursday, February 27, 2003 11:03 AM Subject: [PATCH] admin http 'loglevel' command for bearerbox Hi all Find attached a patch to support an admin HTTP command to change the log level without restaring bearerbox. Example: http://localhost:13000/loglevel?password=xlevel=1 Please consider committing to cvs. Angel FradejasMediafusión España, S.A.[EMAIL PROTECTED]www.mediafusion.esTel. +34 91 252 32 00Fax +34 91 572 27 08
Re: [PATCH] admin http 'loglevel' command for bearerbox
yep, +1 from me to. I'm just addding some more things to it. Especially the ability to change the log-level of a specific logfile too. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
unsbscribe
-- ȨÍþµ÷ÖÆ ÐÂÎÅ¿ì²Í£»ÓÑÇ黥¶¯ ¶ÌÐÅ´«Çé¡£ »¶ÓÔì·ÃÈËÃñÍø¶ÌÐÅƵµÀ£ºhttp://sms.people.com.cn
[RFC] log-file, log-level per smsc group
Hi list, I'm hacking arround the whole day trying to implement a way to log entries to smsc-id specific log-files, so that you have group = smsc ... log-file = /tmp/smsc-a.log log-level = 0 which is exclusive to the main bearerbox.log. So if you have log-file and log-level set all logging output will be passed there instread of the main file. This seems to be very tricky. Assistense is highly appriated :) Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] admin http 'loglevel' command for bearerbox
Hi kewl +1 nisan At 12:03 PM 2/27/03 +0100, Angel Fradejas wrote: Hi all Find attached a patch to support an admin HTTP command to change the log level without restaring bearerbox. Example: http://localhost:13000/loglevel?password=xlevel=1 Please consider committing to cvs. Angel Fradejas Mediafusión España, S.A. [EMAIL PROTECTED] www.mediafusion.es Tel. +34 91 252 32 00 Fax +34 91 572 27 08
Re: [RFC] log-file, log-level per smsc group
Hi Stipe Yup.. I looked at the same and at the time decided it wasnt worth the time and effort. Our log files do tend to balloon quite rapidly, and its a real pain trying to trawl debug info out with many SMSC connections. SO this would be real handy, but would probabally require rewriting the log functions in gwlib and most likely we would have to include params to indicate which log file the debug, info, warning calls relate to. Nisan At 06:57 PM 2/27/03 +0100, you wrote: Hi list, I'm hacking arround the whole day trying to implement a way to log entries to smsc-id specific log-files, so that you have group = smsc ... log-file = /tmp/smsc-a.log log-level = 0 which is exclusive to the main bearerbox.log. So if you have log-file and log-level set all logging output will be passed there instread of the main file. This seems to be very tricky. Assistense is highly appriated :) Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: bug in smsc_smpp.c login failure
hi yeah.. great +1 nisan At 11:27 AM 2/27/03 +0100, Alexander Malysh wrote: Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-MIME-Autoconverted: from 8bit to quoted-printable by mail-in-01.piro.net id LAA28081 Hi, what about attached patch ? Am Donnerstag, 27. Februar 2003 10:30 schrieb Stipe Tolj: Alan McNatty wrote: On Thu, 2003-02-27 at 18:54, Nisan Bloch wrote: Hi At 03:46 PM 2/27/03 +1300, Alan McNatty wrote: Hello, found that if I type in the smpp password incorrectly kannel loops forever trying to reconnect. ie: -1 from me In the current form this path will not allow any retries for any sort of bind error. eg what happens if there is a temporary connectivity issue, or the SMPP server is down for a short while/ What I'm trying highlight is that there is a gap in logic .. Currently regardless of the type of error we continually retry to bind. If we specifically receive an error indicating the password is invalid the SMSC is obviously up but we may as well kill the thread. yep, that's true in some sense. Trying to reconnect forever while we get the error information from the SMSC that we can't login with that credentials *could* be considered as login abuse :) At least I would consider this if our SMPP clients would hammer our SMPP server with invalid credentials. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are -- Best regards / Mit besten Grüßen aus Köln Dipl.-Ing. Alexander Malysh ___ Centrium GmbH Ehrenstraße 2 50672 Köln Fon: +49 (0221) 277 49 240 Fax: +49 (0221) 277 49 109 email: [EMAIL PROTECTED] web: www.centrium.de msn: [EMAIL PROTECTED] icq: 98063111
compile with cygwin
Hi I want to compile kannel with cygwin, but I've got the error libgwlib.a(charset.o)(.text+0xec8): In function `charset_convert': /tmp/kannel-snapshot/gwlib/charset.c:480: undefined reference to `_libiconv_open ' libgwlib.a(charset.o)(.text+0xf5d):/tmp/kannel-snapshot/gwlib/charset.c:494: und efined reference to `_libiconv' libgwlib.a(charset.o)(.text+0xf67):/tmp/kannel-snapshot/gwlib/charset.c:495: und efined reference to `_libiconv_close' collect2: ld returned 1 exit status make: *** [wmlscript/wmlsc.exe] Error 1 Does anyone has an idee? Thanks for your response -- Eric Debienne Ingénieur RD - Atos Origin - Activité Multimédia [EMAIL PROTECTED] Tel: +33 3 20 60 80 14 - Fax: +33 3 20 60 77 88 www.atosorigin.com
Re: [RFC] log-file, log-level per smsc group
Nisan Bloch wrote: Hi Stipe Yup.. I looked at the same and at the time decided it wasnt worth the time and effort. Our log files do tend to balloon quite rapidly, and its a real pain trying to trawl debug info out with many SMSC connections. SO this would be real handy, but would probabally require rewriting the log functions in gwlib and most likely we would have to include params to indicate which log file the debug, info, warning calls relate to. I got now a working solution with minimum changes in gw/log.c and elsewhere. I'll first commit Angel's HTTP admin 'loglevel' patch and then post my patch to the mailing list for review and testing. Stay tuned... Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] admin http 'loglevel' command for bearerbox
commited to cvs. Thanks Angel. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
[PATCH] smsc specific logging
Hi list,
inspired by Angel's HTTP admin command 'loglevel' I had my hands on
the 'logging every smsc to it's own log-file' task today. This was on
my TODO for some time.
Ok, this seems to work for me and it's pretty simple, without changing
to heavily the gwlib/log.[ch] logic.
Here is what it does:
* gw/smscconn.c: adding new fields to the SMSCConn structure
log_idx: holds the gwlib/log.c:logfiles[] array index we will
write to
log_file: the log-file filename
log_level: the log-level
* gw/log.c:log_open() has to be extended to determine if we are
opening the log-file exlusively (GW_EXCL) or not (GW_NON_EXCL).
* gw/bearerbox.c, gw/smsbox.c, gw/wapbox.c, and various others:
extend the log_open() call to indicate this log-file is opened in
GW_NON_EXCL mode.
* gw/log.c: added thread_to[] array to map thread id to logfiles[]
index.
* gw/log.c:log_thread_to() new function to allow smsc threads to
register to a specific logfiles[] array index to write their output to
an GW_EXCL log. This is done using an entry in the thread_to[] mapping
array.
* gw/log.c:debug(), info(), warning(), error() checks if the current
thread has been registed for exlusive log file writing. If yes cann
FUNCTION_GUTS_EXCL instead of FUNCTION_GUTS which causes not to loop
throught all GW_NON_EXCL log files, but only to it's registered
GW_EXCL log file in the given logfiles[] entry.
* gw/log.c:log_init() new initialization function to set all entries
within the thread_to[] mapping array to the default 0.
* gwlib/gwlib.c: adding log_init() for the gwlib_init() call.
* gwlib/log.c: a maximum of 128 log files can be opened now.
* doc/userguide/userguide.xml: the documentatin section for the smsc
group
* gw/smsc_[at2|cgw|emi2|fake|http|smasi|smpp|wrapper].c: added
log_thread_to() registration calls to all working threads. They will
register the working thread to an GW_EXCL log in case a specific log
file should be used.
Ok, I hope you guys know now what I did ;)
Try on your own. I'd like to see some votes for this please. Have fun.
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf
Tel: +49-211-74845-0
Fax: +49-211-74845-299
E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you arediff -ur gateway/doc/userguide/userguide.xml gateway-new/doc/userguide/userguide.xml
--- gateway/doc/userguide/userguide.xml 2003-02-27 21:33:11.0 +0100
+++ gateway-new/doc/userguide/userguide.xml 2003-02-27 21:42:54.0 +0100
@@ -2064,6 +2064,21 @@
end. TCP/IP connection only.
/entry/row
+rowentryliterallog-file/literal/entry
+ entryfilename/entry
+ entry valign=bottom
+A file in which to write a log of the given smsc output. Hence
+ this allows to log smsc specific entries to a seperate file.
+ /entry/row
+
+rowentryliterallog-level/literal/entry
+ entrynumber 0..5/entry
+ entry valign=bottom
+Minimum level of logfile events logged. 0 is for 'debug', 1
+'info', 2 'warning, 3 'error' and 4 'panic' (see Command Line
+Options)
+ /entry/row
+
/tbody
/tgroup
/table
diff -ur gateway/gw/bearerbox.c gateway-new/gw/bearerbox.c
--- gateway/gw/bearerbox.c 2003-02-27 20:23:44.0 +0100
+++ gateway-new/gw/bearerbox.c 2003-02-27 21:43:55.0 +0100
@@ -300,7 +300,7 @@
if (log != NULL) {
if (cfg_get_integer(loglevel, grp, octstr_imm(log-level)) == -1)
loglevel = 0;
- log_open(octstr_get_cstr(log), loglevel);
+ log_open(octstr_get_cstr(log), loglevel, GW_NON_EXCL);
octstr_destroy(log);
}
diff -ur gateway/gw/smsbox.c gateway-new/gw/smsbox.c
--- gateway/gw/smsbox.c 2003-02-27 20:23:44.0 +0100
+++ gateway-new/gw/smsbox.c 2003-02-27 21:44:02.0 +0100
@@ -2978,7 +2978,7 @@
if (logfile != NULL) {
info(0, Starting to log to file %s level %ld,
octstr_get_cstr(logfile), lvl);
- log_open(octstr_get_cstr(logfile), lvl);
+ log_open(octstr_get_cstr(logfile), lvl, GW_NON_EXCL);
octstr_destroy(logfile);
}
if (global_sender != NULL) {
diff -ur gateway/gw/smsc/smsc_at2.c gateway-new/gw/smsc/smsc_at2.c
--- gateway/gw/smsc/smsc_at2.c 2003-01-29 23:59:52.0 +0100
+++ gateway-new/gw/smsc/smsc_at2.c 2003-02-27 22:11:48.0 +0100
@@ -832,6 +832,9 @@
conn-status = SMSCCONN_CONNECTING;
+/* Make sure we log into our own log-file if defined */
+log_thread_to(conn-log_idx);
+
reconnect:
do {
diff -ur gateway/gw/smsc/smsc_cgw.c gateway-new/gw/smsc/smsc_cgw.c
--- gateway/gw/smsc/smsc_cgw.c 2003-02-26 23:15:59.0 +0100
+++ gateway-new/gw/smsc/smsc_cgw.c 2003-02-27 22:12:40.0 +0100
@@ -568,6 +568,9 @@
conn-status = SMSCCONN_CONNECTING;
