[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
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
Re: [RFC] smsc logging patch commit?!
Hi Stipe, I have not tried your patch but at first glance it looks good... +1 from me Am Dienstag, 4. März 2003 14:26 schrieb Stipe Tolj: > 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 -- 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
RE: [FYI] pthread_mutex bug in openssl thread locking fixed
Great. Good work, Stipe. 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 -Mensaje original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] nombre de Stipe Tolj Enviado el: martes 4 de marzo de 2003 13:36 Para: [EMAIL PROTECTED] Asunto: [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.58&; r2=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: [RFC] smsc logging patch commit?!
Hi Stipe, I didn't have the time to try your patch, but, at first sight and from your comments, it looks ok to me. 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 -Mensaje original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] nombre de Stipe Tolj Enviado el: martes 4 de marzo de 2003 14:27 Para: [EMAIL PROTECTED] Asunto: [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
[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
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
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
questions
Hi all, i thought about some features of Kannel which are not yet implemented. as far i as know, kannel still doesn't support SIGHUP in order to reread the configuration file, and it seems, when it gets HUP, it only reopens log files and puts appropriate message in the log files. the second, more complicated feature is about "load balancing" or "fault tolerance". here, in Lithuania, some mobile operators have several SMSC and require to use "load balancing" system. it means that if one of few SMSC isn't working, you have to route all SMS traffic through another. my tests showed that bearerbox would not start if it cannot make connection with all SMSC defined in configuration file. but if start of the program is successful and during the execution time kannel losts connection with any of SMSC, it puts this SMSC in "reconnecting" state and keeps working. i would like to ask, are such features going to be implemented in kannel? and if not, maybe i could get some hints from developers in order to try to make things work. regards, Dziugas Baltrunas
[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.58&r2=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: OpenWave browser PUSH configuration/provisioning
I'm looking for some information about configuring an OpenWave browser using e.g. push. Nokia/Ericsson has the OTA specification describing how to setup their browser using wsp unconfirmed push. Does something similar exist for the OpenWave browser? (without having to use an OpenWave GW) Every hint or comment will be greatly appreciated! Openwave have in my experience regarded this information as a Big Secret, available only to device manufacturers and operators (ie. if you've got lots of $$$...). I did once see a document that showed a text based SMS format for partial OTA of an Openwave browser but it looked as if it needed an Openwave WAP g/way to complete the process. However, I notice that Vizazzi are now offering OTA WAP settings for Siemens A50 handsets so maybe the veil is lifting a little. <>
OpenWave browser PUSH configuration/provisioning
Title: OpenWave browser PUSH configuration/provisioning Hi I'm looking for some information about configuring an OpenWave browser using e.g. push. Nokia/Ericsson has the OTA specification describing how to setup their browser using wsp unconfirmed push. Does something similar exist for the OpenWave browser? (without having to use an OpenWave GW) Every hint or comment will be greatly appreciated! Best regards Søren Corneliussen
Urgent: Priority for messages...
based on the CIMD2 specs you can set the priority of sent messages whether flash or ordinary text, is kannel capable to setting the priority of messages on the fly? are there patches for this? i already read the documentation and found nothing that would help me.. or maybe i missed out something.. TIA __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/
RE: [PATCH] Octstr additions
+1 too. These functions can be quite handy.
Angel Fradejas
Mediafusion Espana, S.A.
[EMAIL PROTECTED]
www.mediafusion.es
Tel. +34 91 252 32 00
Fax +34 91 572 27 08
-Mensaje original-
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
nombre de Nisan Bloch
Enviado el: martes 4 de marzo de 2003 08:02
Para: [EMAIL PROTECTED]
Asunto: [PATCH] Octstr additions
Hi All
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);
Nisan
--- ../cvs/gateway/gwlib/octstr.h Thu Sep 5 21:11:59 2002
+++ ../gateway-click/gwlib/octstr.h Sat Mar 1 00:07:32 2003
@@ -582,4 +582,25 @@
*/
int octstr_recode (Octstr *tocode, Octstr *fromcode, Octstr *orig);
+/*
+ * 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);
+
#endif
--- ../cvs/gateway/gwlib/octstr.c Wed Sep 25 16:05:51 2002
+++ ../gateway-click/gwlib/octstr.c Sat Mar 1 00:07:59 2003
@@ -2181,3 +2181,81 @@
return resultcode;
}
+
+void octstr_strip_char(Octstr *text, char ch)
+{
+int start = 0, end, len = 0;
+
+seems_valid(text);
+gw_assert(!text->immutable);
+
+/* Remove char from the beginning of the text */
+while ((ch == octstr_get_char(text, start)) &&
+ start <= octstr_len(text))
+start ++;
+
+if (start > 0)
+octstr_delete(text, 0, start);
+
+
+seems_valid(text);
+}
+
+int octstr_isnum(Octstr *ostr1)
+{
+
+
+int start = 0;
+char c;
+
+seems_valid(ostr1);
+while (start < octstr_len(ostr1))
+{
+c = octstr_get_char(ostr1, start);
+if (!isdigit(c) && (c!='+'))
+return 0;
+start++;
+}
+return 1;
+
+}
+
+
+void octstr_replace(Octstr *haystack, Octstr *needle, Octstr *repl)
+{
+int p=-1;
+long len;
+
+len = octstr_len(needle);
+
+while ((p = octstr_search(haystack,needle,p+1)) != -1)
+{
+octstr_delete(haystack, p, len);
+octstr_insert(haystack, repl, p);
+}
+}
+
+// symbolise string, return 0 if empty, -1 on error or 1 on success
+int octstr_symbolize(Octstr *ostr)
+{
+long len, i;
+
+seems_valid(ostr);
+gw_assert(!ostr->immutable);
+
+if (ostr->len == 0)
+return 0;
+
+/* Check if it's in the right format */
+if (!octstr_check_range(ostr, 0, ostr->len, gw_isxdigit))
+return -1;
+
+len = ostr->len + (ostr->len/2);
+octstr_grow(ostr, ostr->len * 2);
+
+for (i=0;i
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
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
[FYI] Adding delivery reports to ppg
Hi List, 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. Aarno
