Re: [PATCH] Octstr additions
Hi Nisan, Some additions to octstr.[ch] /* * Strip all occurence of char ch from start of Octstr */ void octstr_strip_char(Octstr *text, char ch); /* * Check if ostr is numeric */ int octstr_isnum(Octstr *ostr1); /* * Replace all occurences of needle with repl within haystack */ void octstr_replace(Octstr *haystack, Octstr *needle, Octstr *repl); /* * Symbolise hexstr - 78797a becomes %78%79%7a */ int octstr_symbolize(Octstr *ostr); that's cool. I'm +1 for adding this 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: [FYI] Adding delivery reports to ppg
Aarno Syvänen wrote: i now have code for ppg delivery reports. It use dlr-url and drl-mask, quite normal Kannel style. But there is one thing: dlrs are delivered by smsbox, so the use must define one. And there must be smsbox-id defined for smsbox sending the dlrs and service-name for ppg (smsbox will names). However, I think it is better that smsbox sends the delivery reports in all cases. Only wap over sms would merit wapbox handling of mo sms. great Aarno. Can you post the patch to the list before commiting please. 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
[FYI] pthread_mutex bug in openssl thread locking fixed
Hi list, just to let you all know that I have fixed and commited a long standing openssl call-back function bug causing to break with pthread_mutex locking. The problem was, that we registered the two different call-back functions to the openssl crypto library, one for the ssl client and one for the ssl server side. But openssl does not know about those issues, it let's you only registed one bunch of mutex locks for it's internal thread locking. This fix should cleanup some ssl related problems. So if you had experienced problems with it, please update your cvs tree and try the latest version. See http://www.kannel.org/cgi-bin/viewcvs.cgi/gateway/gwlib/conn.c.diff?r1=1.58r2=1.59 for the changes. 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] Octstr additions
Commited to cvs. Thanks Nisan. 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] SMPP Optional params
Hi Nisan, could you please attach the patch files to the mail?! Text formating breaks in some cases when you simply inline the patch file to the mail body. Thanks in advance. 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
[RFC] smsc logging patch commit?!
Hi list, I'd like to apply my patch this afternoon. It an 'feature-add' and hence does not break any common behaviour. If someone has considerable constrainst against a commit, please veto. 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
[RFC] re-connect timming harmonization (SMPP vs. EMI2)
Hi list, I'd like to suggest to patch the EMI2 module to use the same re-connect timing config directive as SMPP, SMASI, 'reconnect-delay', instead of the exponential backoff. Main reason is that some SMSC we are connected to leave us some minutes waiting before allowing to login, and the exponential backoff tends to be not very time-near in sense of 'get back to connect ASAP'. Anyway harmonization of the SMSC module behaviour should be a global interest I guess. Any complains or constraints against this?! 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] trivial dcs_to_fields fix
Hi Alex, ok, I see that's it's only MO related. Commiting this to cvs. If someone complains, we will roll-back. 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
[FYI] smsc logging patch commited
Hi list, I have now commited my smsc logging patch that has been introduced some days ago. Please update your cvs trees and report any problems. In case we have to roll-back, I have tagged the tree with pre_smsc_logging before commiting, so a roll-back should be pretty easy. 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
[RFC] smsc logging
Hi list, anyone had the chance to check the patch?! I'm interested what other people think of it. 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] quick fixes for last log.c changes
Attached a patch to fix some minor problems with last log.c patch 1) fixes wrong use of in a info() call (spotted by gwlib/log.c:105: warning: char format, different type arg (arg 3)) 2) more consistent and safe check for stderr thanks, 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: [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: [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: [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
[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: [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;
Re: multiple bearer box - Netikos?
Nisan Bloch wrote: At 11:37 AM 2/25/03 +0100, Stipe Tolj wrote: Kalle Marjola wrote: That's why I published them, altought I knew that some things are a bit too radical. As we have no resources to do any development on it right now, I hope that you can scavenge useful things out from it and this way improve the Kannel project. yep, +1 :) that's what we all do. ditto +1 i dont have much spare time, but I could over the next week or so make a list of those pieces that we can move over basically transparently (eg http libs) and those that would be relatively easy (eg adding the sms-service rules from NMGW) and those that cannot be done without some major changes to Kannel. ok, go for it. Listen anyway to the list, because we may start already with sync'ing some parts from Netikos version to the official tree. 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: SMSC Modules (Was: Kannel Swisscom)
Hi list, this thread leads us to a discussion I had yesterday with Alexander from Centrium (and also Harrie Hazewinkel, who is hopefully still subscribed to the list :) We need to design a clean module API interface (which is already there in some extended sense) and allows to plug them in via dynamical loading of shared objects. In that way you would only load the SMSC module types you need and we may offer template, bare-bone source for new ones to follow. Has anyone checked the approach Harrie did for it? It's available on the web site at http://www.kannel.org/module_api/ Please do have a look and let's get started with this. 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: Storing data into mysql server
Hi Srinivasa, Srinivasa Rao Munagala wrote: Hi, I am trying to configure the kannel gateway. I was able to configure the kannel gateway with dlr-db as mysql. There are no panics when the gateway is started using ./bearerbox confile. Problem when i am sending fake smsc i am getting reply from the kannel gateway. But the data related to fake sms is not stored in Mysql database. Please can one help me to configure the kannel to store the sms data into mysql server database. I guess you didn't get the point. The dlr-db group defines where to store (in your case the mysql db) the temporary DLR (delivery report) data, *not* the sms data itself! So when you fire out an SMS to an *real* SMSC and you want them to reply with a receive report you have to store that temporary data somewhere, either in memory or in the mysql db. So you mistaked by two ways: 1. Assuming that the fakesmsc would deliver DLRs, which it does not, AFAIK. 2. Assuming that the dlr-db group stores the messages into the db. If you want to store messages into your mysql db, then this should be out of scope of Kannel. Hence for MO messages smsbox is sending them to an HTTP server. Let the HTTP server do the storing of the SMS to your mysql db. Another suggested approach would be: (list, please thread this as proposal ;) Implement an 'msg-db' group that defines the fields of an SMS entry and a 'store-db' action in the 'sms-servce' group to tell smsbox to which db id to store an MO'ed message. So you'd get something like this: group = msg-id id = msg_store table = messages field-source = source_address field-destination = destination_address ... group = sms-service keyword = default store-db = msg_store max-messages = 0 This would allow you to store all incoming messages to the mysql table without replying to them directy. You could even extend the beast by implementing a read thread that queues in an outgoing messsages table and sends those to bearerbox for MT transport. 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: Kannel _ WTLS
I would like to develop a WTLS setup using kannel. Do you know if anyone has tried it? you both guys should first of all dig into the mailing list archive. Nick has send some mails about where he stopped with development of the WTLS layer in Kannel. I guess he's getting pi**ed when we ask him to explain it once more ;) Beware that you should have extended experience with SSL and TLS related stuff. The word 'openssl' should make your eyes glue, in order to get your hands on this. As a base you can use the kwtls patch that is still available at http://www.kannel.org/download/wtls/kwtls-1.0.3.tar.gz and try to implement the still missing things into Kannel's own WTLS stack. 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: SMPP 3.4 C-Octet String Termination
Alex Judd wrote: We're working with a SMPP 3.4 server that validly (according to the 3.4 specs) terminates the C-Octet Strings it sends us with a NULL character. This currently isn't handled directly by Kannel and ends up as an extra character on the message content. For example a message of AAA, length 3, now arrives at Kannel as AAA@, length 4 [which is obviously wrong] I've made a short term workaround to remove the character by using the octstr_strip_nonalphanums on the msg-sms.msgdata however I'm interested in whether everyone thinks Kannel should strip off this null character (like I do) or whether this should occur at application level? If it's Kannel I'll submit a proper patch hmm, so someone is not acting spec conform, either Kannel or they?! 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: SMPP 3.4 C-Octet String Termination
I think kannel should respect the length. So a single octstr_trim(packet,len) should do the trick I guess. if you guys consider it a bug in Kannel, then pass the information you have to the bug tracking system. 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: SMPP 3.4 C-Octet String Termination
Alexander Malysh wrote: this is not the kannel problem! Your smsc sned wrong pdu: please look smpp v.3.4 issue 1.2 site 61... short_message field is Octet-String and not C-Octet-String. Your smsc is just buggy ;) if that's the case, Alex, could you ask which explicit SMSC it is? So we can put the vendor and the model on a not spec conform black-list :) 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: SMPP 3.4 C-Octet String Termination
Alexander Malysh wrote: it can't be C-Octet-String at all ;) Just think that '@' in GSM 03.38 is 0x00 ;) so it's a pat situation?! 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: multiple bearer box - Netikos?
Kalle Marjola wrote: That's why I published them, altought I knew that some things are a bit too radical. As we have no resources to do any development on it right now, I hope that you can scavenge useful things out from it and this way improve the Kannel project. yep, +1 :) that's what we all do. 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: Kannel Swisscom
Illimar Reinbusch wrote: Hi Has anyone wrote a connector for Swisscom socket interface? please don't CC to both lists. I guess that Swisscom thingy is something properietary, right?! Andreas, you're closely related to Swisscom (in some sense ;), what about your experience with it? 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] add restart to bearerbox
Alexander Malysh wrote: Hi list, attached patch adds restart functionality to bearerbox and will fix small bug in bb_boxc.c (not closing of listen socket while shutting down). Please look in it and vote ;) +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: rpm files for v.1.3.1
Oleg Titov wrote: I made rpm files for v.1.3.1. Get them from http://www.aleph-tec.com/gsm/kannel.html I have included Alan McNatty [EMAIL PROTECTED] logrotate support (is it possible to include that file into cvs tree?). kannel-manual was renamed to kannel-doc (please, rpm -e kannel-manual before upgrading to kannel-doc). In a few days I'll post the spec file (after I get some error reports). thanks a lot Oleg, you should coordinate with Bruno for the RPM file builds. He's doing mainly the whole Debian stuff. 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] Re: RE : SMPP 3.3 trouble
David Holland wrote: On Fri, Feb 21, 2003 at 04:45:53PM +0100, Angel Fradejas wrote: It seems someone rolled it back :-( Oops. I think Stipe took it out in revision 1.12... Stipe, was that deliberate? Hmm, I don't see what you mean?! I rolled-back Andreas changes concerning msg-id-type handling. 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] Re: RE : SMPP 3.3 trouble
Angel Fradejas wrote: Yep of course +1, this is something I already submitted on Sep 06 2002, and was accepted. See http://www.kannel.3glab.org/cgi-bin/viewcvs.cgi/gateway/gw/smsc/smsc_smpp.c. diff?r1=1.9r2=1.10 http://www.kannel.3glab.org/cgi-bin/viewcvs.cgi/gateway/ChangeLog.diff?r1=1. 1950r2=1.1951 It seems someone rolled it back :-( yes, blame to me :( I deleted the line by mistake while rolling back a revision from Andreas mistakenly applied msg-id-type patch. Sorry, I'm fixing this again now. 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] Re: RE : SMPP 3.3 trouble
thanks Alexander for detecting the mistakenly deleted line from a roll-back. It's fixed now in 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: multiple bearer box - Netikos?
Nisan Bloch wrote: I think rolling NMGW into Kannel would be worthwhile. At the same time come up with a combined bbox+smsbox version, with the same HTTP interface. In addition an API to build XXXboxs with. Smsbox would be the first such app and maybe the smppbox and emibox that have been mentioned on the list. definetly. We should merge things from Netikos version into official Kannel. Main question would be how many efforts Netikos is *still* doing in continued development of their branch? Kalle? You guys could switch off to the official tree and get your great things included there. This would cause a benefit for all. 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: multiple bearer box ?
Nisan Bloch wrote: At 10:29 AM 2/20/03 +0100, Stipe Tolj wrote: ok, as all of you kick-ass with benchmark figures, I'll do too ;)) The max. throughput we reached with a Dell PowerEdge 2x CPU (1.2 GHz) Linux 2.4 Kernel in a fakesmsc - bearerbox - smsbox chain was approx. 2400 msg/sec. We had also MO values while loading the bearerbox quueue (fakesmsc - bearerbox) with over 1 msg/sec. So I guess this is pretty fast :) that is - but tell me were you using dlr acks? And if so internal or mysql store? nop, none of them ;) 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: kannel
joseph lapuz wrote: Hi Im using the sms gateway of your kannel in sending text messages, is there's a way to change the sender's mobile number when sending a message? you should definetly read the user's guide. 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: multiple bearer box ?
Alexander Malysh wrote: Not 100% true ;) We run one logical link per bearerbox (e.g. 3 sessions for one offerer). For now I have not seen any performance bottleneck issues with bearerbox. Some of our bearerboxes running with ~60sms/sec. Now you will ask, why multiple bearerboxes ;) It's easy... It's more simple to maintain/route messages beetwen multiple bearerboxes. For example bearerbox do not support dynamic config reload and it's just more simple to read/write ~30 Lines of config file as 300 lines ;) that's true. That's why we implemented the 'include = file' feature for the config file handling, so you can structurize the global config file for your own needs. It's like you setup an apache config for every VHost you'd like to run. The best argument for the one bearerbox per logical link ;) is indeed the lacking of hot-restart functionability. AFAIK, the Netikos version had such things. We should definetly start to port things from their version to the official tree. 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: multiple bearer box ?
Aarno Syvänen wrote: I once stress tested stand-alone bearerbox. (Standalone meaning I was using smsboxes that did not do any fetch, but returned a standard text message instead.) I got value 1200 msg/s and must use ~20 smsboxes before I reached 100 % cpu utilisation. Cpu was AMD Athlon, 800 MHz. ok, as all of you kick-ass with benchmark figures, I'll do too ;)) The max. throughput we reached with a Dell PowerEdge 2x CPU (1.2 GHz) Linux 2.4 Kernel in a fakesmsc - bearerbox - smsbox chain was approx. 2400 msg/sec. We had also MO values while loading the bearerbox quueue (fakesmsc - bearerbox) with over 1 msg/sec. So I guess this is pretty fast :) 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: multiple bearer box ?
Kalle Marjola wrote: The current Kannel is, however, made in that way that it gets trashed if it receives messages faster than it can handle, so beware :] yes, in some sense. But that would mean you have an permanent(!) input stream of 100-200 msg/sec. and this is very unlikely. Of course you could have peaks with such or even higher values, but I don't think anyone of us here arround has a permanent load of 200 msg/sec., or am I wrong? 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: multiple bearer box ?
Alexander Malysh wrote: Am Donnerstag, 20. Februar 2003 09:35 schrieb Kalle Marjola: The current Kannel is, however, made in that way that it gets trashed if it receives messages faster than it can handle, so beware :] I have sent patch to the list for avoiding this issue , but unfortunately it was not accepted ;( I will rework this patch and resend to the list. We use this patch in production and do not have any problems that kannel trashed. please re-send and also quote which mail thread contained your orginal patch, so we can review why we didn't commit it yet. 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: Cookie handling
Bruno Rodrigues wrote: Citando Wilms, Stefan, VIS-THND [EMAIL PROTECTED]: Dear all, trying to get access to our intranet via WAP, using kannel 1.1.6 (with --enable-cookies compiled) There's something wrong with cookie support but as I'm gonna need them to work soon for a project of mine, I'll look at the code and will make sure they work. me too. Bruno keep me and the others informed about issues via the mailing list, please. 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: multiple bearer box ?
Bruno Rodrigues wrote: We have only one bearerbox and one smsbox for 16 connections and alot of messages per day, and sometimes I'm scared when I enable a 50msg/sec on one of those connections for doing mass spam but then, while I'm sending them, I'm watching and testing the other connections and kannel works like a charm. Please note that usually I use post-xml to enable me to send like 10k destinations at one time, and thus have smsbox processing a xml post with 350KBytes, have the xml processing overhead, and have one smsbox thread creating that many messages in queue. What I mean it's might be a bigger peak processing than having 10k GET's and it works perfectly cool. What was the highest peak (msg/sec.) you had in the bearerbox (over all connections)? 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: Kannel wap limits ?
I'm trying to force kannel to let a mobile download realplayer.sis file (584.720bytes) through it. I know that I'm crazy to try it, but I just need to know the limits of kannel and see if we can do better than CMG ;) we definetly sould do better :) 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: DCS and PID handling in Kannel
If it's DCS is really broken up in MO SMPP, then please re-send the patch. Use [PATCH] in the mail subject line. And try to explain in the mail what the problem was and what you patch does to fix it. Thanks in advance. I'm definetly willing to review it and vote. At least we can offer you that alternative option. 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] allow setting service-type for SMPP SMSC
David Holland wrote: Please find below a patch to allow an SMPP SMSC group to contain a service-type definition. Previously Kannel would always send NULL, i.e. use default service-type. I've tested this patch and it works against Xwireless/Mblox SMPP server. If no-one objects I'll commit it to CVS and update the userguide. Many thanks to Nick Clarey for writing this when I realised what the missing functionality was. seems clean to me from first glance, +1. One thing only: what's the default of the value if *no* config directive is given?! It looks you don't initialize the variable and hence you will pass garbage, or does cfg_get() return NULL in case the value is not given?! 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] allow setting service-type for SMPP SMSC
David Holland wrote: On Tue, Feb 18, 2003 at 02:58:12PM +0100, Stipe Tolj wrote: One thing only: what's the default of the value if *no* config directive is given?! NULL. (and I have tested that -- it appears correctly in the PDU dump) It looks you don't initialize the variable and hence you will pass garbage, or does cfg_get() return NULL in case the value is not given?! Yes, that's what happens. ok, then I'm off with ++1 :) 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] allow setting service-type for SMPP SMSC
+1 from me too. We use similar patch for a while... so why didn't you post it ;)) 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] allow setting service-type for SMPP SMSC
Ian Cass wrote: David Holland [EMAIL PROTECTED] wrote: I've tested this patch and it works against Xwireless/Mblox SMPP server. Heh, I wrote that server :) ok, so we know who to blaim ;)) just kidding. I guess you're then interested in getting smppbox into Kannel's cvs repository, right?! 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] allow setting service-type for SMPP SMSC
just kidding. I guess you're then interested in getting smppbox into Kannel's cvs repository, right?! No, it's a standalone app that has nothing to do with Kannel. I know (or I assumed to be more precise :). But I guessed you'd be interested in playing arround with out SMPP server implementation based on Kannel's sources. 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: MMS compiler
Friedrich, Jason Brian wrote: Hello everyone, i am able to send MMS Notifcations now (and i have toasted a 7650 already ;).*hooray* But i am facing a new problem *g*. How to compile MMS? At the moment i use NowSMS to compile them but it runs only with a Windows Operating System. which is definetly the choise to have ;) Does someone know a (license-)free tool which compiles MMS for Linux? Or does someone write his/her own tool to compile them? We aim to have corresponding functions in Kannel, but they haven't been implemented yet. Which application is the best or most preferred to build MMS? I have heard about a Nokia application but i am not able to find it on the very weird and unsorted site of http://forum.nokia.com. We you the Nokia Java libraries on our MMSC. They are pretty well. 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: MMS compiler
Jason Brian Friedrich wrote: On Mon, 2003-02-17 at 10:45, Stipe Tolj wrote: which is definetly the choise to have ;) Not really *gg* We aim to have corresponding functions in Kannel, but they haven't been implemented yet. That would be really great. Are there any plans or can you estimate when there will be a beta version of Kannel which supports it? Your So called beta- or cvs-versions are (many, many times) better than releases of some other developers ;) no, there are no plans yet. I'd like to setup a couple of people that would implement this. Basically I need volonteers that do re-engeneer the Nokia classes to C code. Hmm, pretty simple, or?! But who is going to have time for this? Jason maybe you?! :) 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
[RFC] urltrans'lations
Hi list, I got an idea that would be an easy but powerfull feature for the sms-service urltrans()ing. I'd like to introduce a boolean sms-service config directive, maybe 'non-authorative' (defaulted to 'no') that does the following: If set to yes, then the urltrans search is continued and hence two (or even more) sms-service groups matched for the keyword and hence two (or even more) URLs, text or exec (or whatever) would be triggered by one MO SMS. I'm not quite sure how this would be implemented in smsbox:obey_request_thread(), but it's just an idea I have. BTW, anyone tried to port Netikos's urltrans() routines (which are very good IMO) to the official source tree?! 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: [RFC] urltrans'lations
Alexander Malysh wrote: Hi Stipe, List, Am Montag, 17. Februar 2003 16:48 schrieb Stipe Tolj: [snip] BTW, anyone tried to port Netikos's urltrans() routines (which are very good IMO) to the official source tree?! Can you please provide link to their changes/patches ? please check the mail archive. Kalle Marjola send the email containing the link to their patched version. 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] Re: EMI Driver Bug
Alexander Malysh wrote: Hi All, attached patch should solve the bug , make small cleanup and add additional sanity check... please look in it and vote ... ok, we had positive votes on this, so I'm commiting this. AFAIS, Andreas was the only one with objections?! If he doesn't veto the patch, we'll leave it in. 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: Ok thanks - I see now how it works .. I've attached patch below in unified format. I've changed the order so that you first check for --enable-docs, etc then check to see if jade, jadetex, etc are all installed before confirming that indeed the docs should be made. It's a bit more all or nothing, that is you either have all the 'right things' installed to build all the docs or you don't so can't proceed. I'm not sure if everyone will like this - just something to test and consider. +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: [RFC] yesterday commits
Aarno Syvänen wrote: I will fix this. I'd prefer a roll-back to the previous revision for the gwlib/socket.c file, cause there haven't been any bug or problem reports on this issue. 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: SMPP driver default autodetect should be 1
ok, 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: nokia 7110
2) in your opinion, what is a heavy duty GSM modem? does anyone else on the list have an opinion/recommendation for a heavy duty GSM modem? i've seen people mention wavecom before ? we run some Siemens M20 (with updated firmware). They work pretty well and for that ammount you need they should be ok. (but don't blame me if they don't do there job ;) AFAIK, most people suggest the Falcom GSM modems. 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 (userguide patch)
applied to cvs. Thanks. 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
[Fwd: Support]
forwarded from wrong mailing list. 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 ---BeginMessage--- Title: PervasiveOne Hi, I am testing kannel gateway with the smsc server of our own. I want to know how to configurethe following parameters for UCP protocol, Oadc , OTON, ONPI , STYP, and OPID .. thanking you , vijay. Germany: Am Manfredhof 43, 83646 Bad Toelz; Ph: +49 89 693 723 70 FAX +49 89 693 723 80 India: C-071 B, DLF Supermart I, DLF City Phase IV, Gurgaon, Haryana, 122 002 India; Ph: +91 124 8942538 Fax: +91 124 8942539 UK: 1, Sabin Gates, Old Bracknell Lane East, Bracknell Berkshire RG12 7AG UK; Ph: +44 1344 409320 Fax: +44-1344-862263www.PervasiveOne.com E-mail: [EMAIL PROTECTED] This email and any attachments are sent in confidence, subject to applicable legal privilege and upon the basis that the recipient will conduct appropriate virus checks. If you receive this email in error, please contact us upon receipt: you are strictly prohibited from using, copying or disseminating it or any information contained in it save to the intended recipient. Internet communications are not secure and PervasiveOne Solutions Limited, formerly known as Telcon Limited, is not responsible for their abuse by third parties, nor for any alteration or corruption in transmission, nor for any damage or loss caused by any virus or other defect. ---End Message---
Re: receiving a Vcard and save toa DB
joseph mercado wrote: Has anyone already implemented kannel to recieve a Vcard and point to a url where it get parse and be save to DB I have played a bit with the Nokia smart messaging stuff. I didn't recall exactly if the vcard is delivered with alternative DCS fields?! AFAIK, binary DCS field are not supported for most SMSC modules. *ehmmm* *ducking head* Hope others that run such services don't flame me now ;) But the idea is cool. 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: Urgent Query ??
Dheeraj Anand wrote: I need some information very urgently. a urgent reply will be appreciated. my ques is: Hmm, your mail is dated from Saturday morning CET, but I received it now. So it appears you didn't tell your SMTP server that this issue is urgent ;)) *g* Is Kannel 100% wap 1.2.1 specification compliant. If not then I want to know what features does the kannel gateway support which are possible as per wap 1.2.1 specifications. i actually need a detailed list. i've gone thru whole kannel site but all the info there is very brief. so any1 who can help me please do the needful. No, Kannel is not fully WAP 1.2.1 compliant. We cover the most important parts: WTP-SAR, WAP Push, no UAProf. You should pick a glance on the user's guide. If you don't find anything mentioned about 1.2.1 specific features in there, then it's obviously yet not implemented :) 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: (no subject)
Hi Kang, BTW, cool, we have people from Siemens, Nokia and Motorola on the list. :)) I guess the swidish Ericssons are a little bit shier then the others :)) I like the idea that members of those device manufacturer companies deal with Kannel. It's definetly a positive signal to Kannel and I'd like to take the opportunity to congratulate all developers and participants in the Kannel project effort! You all are doing a great job! Kang Minfeng-a18629 wrote: Hi, List: I have a question about WTP-SAR, it is not about kannel, but maybe some experts here can help me. the WTP-SAR experts are definetly Aarno and Igor, I CCed them on this issue. Please keep the discussions on the list, so others can follow. I develop wap-client on mobile. When I send a Invoke message by WTP-SAR to gateway, I get the abort PDU. Following is the flow: Invoke, SegInvoke, PSN=1 SegInvoke, G, PSN=2 Ack, PSN=2 -SegInvoke, PSN=3 -SegInvoke, PSN=4 -SegInvoke, T, PSN=5 -Abort, Abort Reson = 0xE1(disconnect) I donot know why the gateway send the abort PDU intead of the result PDU, and the abort reason can not tell me more information about it. Can anybody here help me? 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: Urgent Query ??
Bruno Rodrigues wrote: Citando Stipe Tolj [EMAIL PROTECTED]: No, Kannel is not fully WAP 1.2.1 compliant. We cover the most important parts: WTP-SAR, WAP Push, no UAProf. I might have some news about UAProf one of these days ;) Hint: Deli, Cocoon, Vodafone live that would be great. BTW, can I shoot this evening for development release 1.3.1?! 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
[RFC] config directive 'country-prefix' in wap-push-user group
Hi Aarno,
Hi others,
AFAIS, the 'country-prefix' is simply prefixed to the given number in
case it's set for a wap-push-user group, see
gw/wap_push_ppg_pushuser.c:770:
if (u-denied_prefix != NULL) {
denied = octstr_split(u-denied_prefix, octstr_imm(;));
for (i = 0; i list_len(denied); ++i) {
listed_prefix = list_get(denied, i);
if (u-country_prefix != NULL)
octstr_insert(listed_prefix, u-country_prefix, 0);
if (compare_octstr_sequence(number, listed_prefix,
0) == 0) {
goto denied;
}
}
}
hmm, shouldn't this be done via out 'unified-prefix' prefix
normalization routine?! Basically the functionality is similiar, but
there are two approaches.
I'd like to eliminate country-prefix and use either the global
unified-prefix from group core or allow a dedicated unified-prefix for
a wap-push-user group. (the same way we do it for smsc groups).
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 (userguide patch)
Hi Alex, logrotate being owned by RedHat is not currently updated on Solaris, so instead I'm using rotatelog which is Perl based and very portable. I'll add some documentation on that (as well as example configurations) if of interest to the Solaris users among us? definetly. Please setup a section in the user's guide and mail the patch (in unified diff format, as you may know ;) to the mailing list. 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
[REQ] submitting patches
Hi there, Please, could anyone who submits patches in attached files prefix the mail subject with [PATCH], this makes it easier for us to identify those mails that contain patches, i.e. [PATCH] fixes a bug in the smsc_smpp.c module, etc. This holds also for patches that are re-submited within a thread. Thanks. 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: SMPP driver default autodetect should be 1
Alex Judd wrote: By default we are disabling the auto switching of TON and NPI in the SMPP driver. I think we should enable this by default and then allow to explicitly turn it off. smsc_smpp.c, line 1272, autodetect_addr = 1; Make sense to everyone? any objections from the others? I'm +0 on this. 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: Billing Kannel SMS side
Kita B. Ndara wrote: Is there any good reason why the kannel sms part does not incorporate some kind of billing support? What I have in mind is: - Before a message is sent to the SMSC, a script is run by bearerbox. If it returns zero, the message is sent. This is for balance checking - When the SMSC accepts the message, another command is run. Both commands would be specified in the SMSC group of the conf file, and %P, %i, etc are allowed. what do you mean with %P, %i, etc is allowed? Any thoughts? Kannel's scope of function is beyond billing. In other words, billing should be done by software component entities that are *not* part of Kannel. To make it short and simple. It's more or less a religious question if you incorporate billing facilities to Kannels functional scope. Most of us decided not to do this, because billing (in that SMS traffic sense) is not standardized in any way and hence we would implement properietary things, which open source developer don't like :) 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: Problem with SMPP 3.3 SMSC in message delivery
Ritesh Shah wrote: The Kannel 1.0.3 version works fine, but the later versions give this error when the gw. receives the msg. (got DLR but could not find message or was not interested in it) This prob. is happening only with logica SMSC, I haven't faced this issue with any other SMSC. try the current cvs snapshot or the upcoming 1.3.1 version. It contains some fixes for the SMPP optional parameter parsing code. 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
[RFC] yesterday commits
Hi Aarno,
can you comment on this part of your patch, please:
Index: gateway/gwlib/socket.c
diff -u gateway/gwlib/socket.c:1.53 gateway/gwlib/socket.c:1.54
--- gateway/gwlib/socket.c:1.53 Wed Nov 13 10:22:56 2002
+++ gateway/gwlib/socket.c Thu Feb 13 10:35:48 2003
@@ -510,7 +510,7 @@
}
-static void setup_official_name(void)
+static int setup_official_name(void)
{
struct utsname u;
struct hostent h;
@@ -519,14 +519,15 @@
if (uname(u) == -1)
panic(0, uname failed - can't happen, unless GW_NAME is
buggy.);
if (gw_gethostbyname(h, u.nodename) == -1) {
-error(0, Can't find out official hostname for this host,
- using `%s' instead., u.nodename);
+/*error(0, Can't find out official hostname for this host,
+ using `%s' instead., u.nodename);*/
official_name = octstr_create(u.nodename);
official_ip = octstr_create(127.0.0.1);
-} else {
-official_name = octstr_create(h.h_name);
- official_ip = gw_netaddr_to_octstr(AF_INET, h.h_addr);
-}
+return 0;
+}
+
+official_name = octstr_create(h.h_name);
+official_ip = gw_netaddr_to_octstr(AF_INET, h.h_addr);
}
why is that change necessary?
BTW, it throughs warnings on the automatic compilation test, as you
may have noticed. See devel-report@ list.
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: Billing Kannel SMS side
Arne K. Haaje wrote: I am thinking about adding support to the CIMD2 module for the Tarrif field. This is in Nokias official specifications. It is a field like any others where you can set the tarrif class. As it is in the official specs. I think it would be useful. Are there any objections to me adding support for it? no, definetly not. If billing issues are part of the SMSC specs, they should be implemented. The point is we don't want things in there, because billing is usually a very individual thing and it wouldn't fit for everyone if we decided to do it on a specific way. So we leave the choice to the users how to do it. 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: SMPP driver default autodetect should be 1
Andreas Fink schrieb: any objections from the others? I'm +0 on this. Can anyone enlighten me on what it is autodetecting here? Then I can come to some opinion... it's autodetecting the TON, and hence sets the destination TON accordingly for submit_sm PDUs. 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: Fw: kannel dependancies
Bruno Rodrigues wrote: After Stipe releases devel 1.3.1, I'll generate and upload new debian packages for that release. I don't have time now for generating 1.3.0 packages when we are so close to 1.3.1 release. which will be in the upcoming days. (or even today, if I don't find anything better to do :)) 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: connection of bearerbox with GSM modem
Anupama R wrote: 1) connect the gsm modem to usb port 2) start bearerbox to connect to modem at 115200 (speed set in conf file) 3) bearerbox fails to connect, because after opening port at that speed, at command fails 4) connect the modem through hyperterminal (Hilgraeve product, comes with win 2k) at 115200 5) disconnect the modem from hyperterminal 6) reconnect with the same configuration file from bearerbox, this time connection will succeed. This is not sporadic behaviour. I run through this process everytime I connect the gsm modem. I wanted to know if there are any workarounds for this. I guest this is more of a Cygwin and USB port issue then kannel. Maybe you should post a USB related question to the cygwin mailing list. Sorry, but it's definetly out of scope for this mailing list. (Which doesn't mean someone who knows what this effect is shouldn't head up now and explain :)) 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
[Fwd: Removing WTP-SAR limit 32768 B]
Hi list, forwarded. 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 ---BeginMessage--- Stipe, Could you please advise how to remove limit 32768 B for downloading files with larger sizes. I have Kannel 1.3.0 with WTP-SAR (Debian package) but when I try to download .jar file I get a message: WARNING: WSP: Entity at http://my_site/file.jar too large (size 69885 B, limit 32768 B) Best regards, Max ---End Message---
Re: connection of bearerbox with GSM modem
Anupama R wrote: Hello, I work with the cygwin installation of kannel on a win2k machine. I have a peculiar problem with the bearerbox. When I start bearerbox utility and try and connect to the modem, the speed in the conf file does not seem to match and the connection fails. But if I try to connect to the modem thru the HyperTerminal (developed by Hilgraeve for microsoft) to the modem with the same speed, the connection comes through correctly. Consequently if I try the bearerbox connection with the same conf file, the bearerbox is up and running fine. Any idea why this would happen? so do you get a valid connection to the device or not? I didn't get the point, sorry. 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: MMS-Ind: Ports and expiry date
Friedrich, Jason Brian wrote: could somebody tell me more about the ports section in the mms notification? Why is there a source and destination port? I thought that only a destination port is necessary. (Nokia has different ports for different applications). MMS notifications are pushed via WAP Push, which may also been utilaized over IP, hence source addresses are of possible relevance. 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
Alan, please do not patch configure itself. It's the autoconf output out of configure.in. If you have to change something, please try to patch configure.in and provide a patch to it. After that we can run autoconf and commit an auto-generated configure script. 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
Alan, can you provide the userguide.xml patch in diff -u (unified) format, that should be easier to read and to apply. Thanks in advance. 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: User Guide for Palm OS
http://www.aleph-tec.com/gsm/kannel.html a link will be available in http://www.kannel.org/doc.shtml to your page shortly. 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: smscconn cimd2
Kalle Marjola wrote: The patch required some work to do from our CVS version and that final version is only at my desktop computer - which currently does not boot (disk crash) and I'm about 3000 kms away from fixing it. I guess that are some bad pre-conditions to get a patch from you ;))) Anyone else volonteering to grap Kalle's rcsdiff'ed patch an reconstruct the CIMD2 patch? 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] DLRs crash smsbox using CIMD2
--- smsc_cimd2.c.cvsThu Feb 6 12:55:00 2003
+++ smsc_cimd2.cThu Feb 6 12:54:12 2003
@@ -1588,8 +1588,7 @@
goto io_error;
next_reply:
-/*reply = cimd2_get_packet(smsc,ts);*/
-reply = cimd2_get_packet(smsc, NULL);
+reply = cimd2_get_packet(smsc,ts);
if (!reply)
goto io_error;
@@ -1880,9 +1879,9 @@
octstr_get_cstr(msg-sms.dlr_url),
msg-sms.dlr_mask,
octstr_get_cstr(msg-sms.boxc_id));
-octstr_destroy(ts);
-ts = NULL;
}
+octstr_destroy(ts);
+ts = NULL;
if (ret == 0 || ret == -1)
break;
if (cimd2_reopen(smsc) 0) {
Please comment and vote.
+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: Motorolla 350 OTA
Maria Turk wrote: does anyone have example binary OTA for the new motorolla 350. you mean OTA config SMS? I'm not aware that Motorola supports that. 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: Where's my FOO ? [Was: Daily patch: gateway]
ok, Bruno will get it's Foo back :)) For the sake of foo'ness ;) 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] Sender as shortnumber with CIMD2
Andreas Fink wrote: Kannel should send the originator in the format it was submitted. I dont think adding another parameter is the right way to solve this. yep, I disagree also in adding more SMSC module specific config directives. It's already complicated enough. So I'd vote -1 for this. Why doesn't the sender number been send as passed to the sendsms HTTP interface? 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] Sender as shortnumber with CIMD2
Andreas Fink wrote: I don't understand what's the issue here. If you send the number as 123 it arrives on the phone as 123, if you send it as +123 it will arrive as +123. So is this not good enough?? agreed! I don't see any reason for issue either. 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] Sender as shortnumber with CIMD2
Arne K. Haaje wrote: I don't understand what's the issue here. If you send the number as 123 it arrives on the phone as 123, if you send it as +123 it will arrive as +123. So is this not good enough?? Not it looks like the operators MC adds the + sign even when sending just 123. hmm, and how do you want to avoid this then?! I don't see how. What the patch does is just that it treats all numerical 'from=' fields up to shortnumber= digits as an alphanumeric sender. This avoids the MC prepending the pluss sign. So if shortnumber=4 - from=2030 will be received without the pluss sign. Ok, I guess I understand know what the point is. the parm_valid_address() checks if it's an alphanumber address and that's where you problem begins while you want to send 2030 as alphanumeric and not numeric to avoid the prepending +. Ok, it's a problem for you in some sence. But adding shortnumber as smsc directive is a -1 vote IMO. You should try to solve this on another way. You may use the existing 'source-addr-ton' and/or 'source-addr-npi' directives for CIMD2. This would be a better way in using common directives for various SMSC module types. 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: Text messages with UDH, bad DCS
Enzo dell'Aquila wrote: I tried to send text messages with UDH with emi2 driver. This feature appears as y? (driver probably has this feature, has not been tested). I would like generate TP-DCS = 00h (it's good also 11h or 12h), I need 7 bit coding in DCS I use these parameters: UDHI = 1; MClass = 2; // this should be for 12h; or MClass = '1' for 11h; or MClass = '' for 00h Coding = 1; MWI = ''; DLRmask = 0; PID = 0; AltDCS = 0; Note: UDH is 8bit encoded, Body is 7 bit encoded! But i get DCS = 14h, that's 8 bit coding, not 7 bit! kannel userguide says: If unset, defaults to 7 bits unless a udh is defined, which sets coding to 8bits. Is this a bug in emi2 kannel driver or doesn't emi2 support text messages with UDH ? Please reply, this bug should interest a lot of developers! I didn't get the point, can someone enlight me? :) We do use UDH 8-bit messages over EMI2 links that do work as expected. 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: PPG: wap-push-user specific smsc-id config
Bruno Rodrigues wrote: Don't we have a forced-smsc-id in sendsms ? please use it instead of smsc-id to maintain consistency ;) yep, that's for the sendsms-user group, *not* for the wap-push-user group. They are not the same. I agree that we may name the smsc-id config directive in the wap-push-user group better force-smsc in compliance with the same behaviour for the sendsms-user group. 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: RedHat spec file
Oleg Titov wrote: Hello Kannel list, I was looking for kannel-*.rpm package and was unable to find it. I have downloaded v.1.3.0 sources and there I found 2 spec's files for RedHat system. Let me ask some questions: 1. Do Kannel developers team support RedHat? yep, we support any Linux distro, including SuSE, GNU/Debian and whatever. 2. Do you provide pre-build rpm files? there have been some flowing arround on our download site. But you should be pretty fine with a very out-of-the-box configure and build of the source tree. 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: RedHat spec file
Bruno Rodrigues wrote: (Zeca, are you there ? lunch at 13h30 ?) slightly off-topic, right?! :) 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: Need assistance....
group = smsc smsc = at2 smsc-id = check modemtype = nokiaphone device = COM1 validityperiod = 167 speed = 9600 Is this correct for device.. variable under windows because it's not working with /dev/ttyS0? device = /dev/com1 would be the cygwin style to define COM1 serial device. Also, what can be responsible for the error output in smsbox shell when a http resquest is made to the smsbox. 2003-01-13 17:19:22 [5] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 192.168.77.84 2003-01-13 17:19:22 [5] INFO: sendsms used by tester 2003-01-13 17:19:22 [5] INFO: sendsms sender:tester:13013 (192.168.77.84) to:08024569875 msg:I will always love u. 2003-01-13 17:20:27 [3] ERROR: Error reading from fd 24: 2003-01-13 17:20:27 [3] ERROR: System error 104: Connection reset by peer 2003-01-13 17:20:27 [3] ERROR: Error reading from fd 24: 2003-01-13 17:20:27 [3] ERROR: System error 104: Connection reset by peer 2003-01-13 17:30:48 [5] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 192.168.77.84 2003-01-13 17:30:48 [5] INFO: sendsms used by tester 2003-01-13 17:30:48 [5] INFO: sendsms sender:tester:13013 (192.168.77.84) to:08024569875 msg:I will always love u. 2003-01-13 17:31:19 [0] ERROR: Error reading from fd 21: 2003-01-13 17:31:19 [0] ERROR: System error 104: Connection reset by peer 2003-01-13 17:31:19 [0] ERROR: Error reading from fd 21: 2003-01-13 17:31:19 [0] ERROR: System error 104: Connection reset by peer from the above ERROR: Error reading from fd 24: 2003-01-13 17:20:27 [3] ERROR: System error 104: Connection reset by peer 2003-01-13 17:20:27 [3] ERROR: Error reading from fd 24: 2003-01-13 17:20:27 [3] ERROR: System error 104: Connection reset by so, what can I do to eradicate the error and what can be responsible for this? that's a more TCP related problem. Which Cygwin version are you running? Corinna (official cygwin developer) has made recent fixes in TCP state handling, see cygwin snapshots. 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
Bruno Rodrigues wrote: Citando Alan McNatty [EMAIL PROTECTED]: This might be useful for you ... (add to /etc/logrotate.d or similar). Note: you need to restart Kannel as it doesn't have full signal support. you just need to killall -HUP bearerbox smsbox wapbox. -HUP doesn't re-read configuration, but it reopens log files. And yes, logrotate is the way to go what about pipelined logging, like cronolog for Apache?! Has anyone thought of this option. This may be rotating without -HUP'ing the processes. Just an idea... may be hit to the TODO task list, at least with low priority. 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: MMS files.
Bruno Rodrigues wrote: Citando Maria Turk [EMAIL PROTECTED]: Does anyone know if there is a difference between MMS formats between nokia 7650 sony ericsson T68i and the GX10. Yes, they are. But there's a common mms format that works in them all (including Panasoinc GAD87). My experience says that it's too much dependent of your mmsc, specially through email interface. You need to try to send and try with combinations of start tag and content-id hey, I love the company quote: yes, we are member of the WAP forum and we are interested in having a well-defined, open standard protocoll to enforce the use and acceptance of the wireless messaging :)) Why do they make our life so difficult? We at Wapme have NDA's with Ericsson and Nokia. Usually we tell Ericsson engeneers what they should do to be protocoll conform and tell Nokia what they do wrong in their MMSC to serve Ericsson devices. Hmm, and why is my bill payed by Wapme and not by all of them ;)) 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: kannel,devicehome,urgent
The issue here is that the end user phone doesnt request device:home which you can then map to your default page but your device requests the URL www.phone.com. So the only way to fix this is to change the settings of the phone to request something else. This is not an issue of Kannel but of the crappy Motorola phones. If you got it from some US carrier, you might not even be able to set the startup page. Welcome to stone age in mobile communications (also known as USA) If you are in control of the WAP gateway node inside your communication linkage, i.e. using kannel, then you may use map-url = http://www.phone.com some other url. But as Andreas pointed out. Motorola has been to deeply laying with Openwave (aka phone.com). Usually the Motorola phones did send a device:home as URL starting page. It that does not work for your phone, then use the map-url. This is only possible if kannel is running as WAP gateway for your phone setup. 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: MMS binary
Maria Turk wrote: I tried those but they don't work with T68i and GX10. any suggestions. hip hip hurrey, f**k the standards. :( 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
