RE: [Kannel 0000010]: HTTP requests get urlencoded twice (orevenmore) if HTTP 302 (redirect) responses are received
I think you answered your question yourself :). Yes, the querystring should be included in subsequent requests. -- Rene... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Bruno David Rodrigues Sent: dinsdag 25 maart 2003 17:08 To: [EMAIL PROTECTED] Subject: RE: [Kannel 010]: HTTP requests get urlencoded twice (orevenmore) if HTTP 302 (redirect) responses are received Citando Rene Kluwen [EMAIL PROTECTED]: About 302 (temporary) redirecting responses: After a GET request, the client (kannel) should redirect the SAME request to the URL pointed to in the Location: header. This means, the query string should not re-urlencoded. Section 3.2.2 says that URL includes the querystring, so going back to my first question - should the original querystring be added to the new location ? Imagine this: original URL: http://foobar/foo?phone=%ptext=%a Location header: http://barfoo/bar?foo=truebar=false Which URL should kannel use ? Simply the location ? should it add phone...%a to the second URL (http://barfoobar=falsephone=%ptext=%a) ? I don't see anything relevant in rfc :( After a POST request, the same request should be POSTed the the new URL. Specs tell that this should require user interaction, since this might change the conditions under which the request was issued. But I figure, this will be a little hard, as Kannel is a daemon. No, it says MUST NOT go without user intervention. As kannel is a daemon, it shouldn't follow locations if original method is a post. Unless we have a config value yes-i-ve-read-rfc-and-i-want-to-follow-post-redirections = true ;) The above also goes when the status code is 301 (Moved permanently). But Kannel should save the new URI's and use them for future connections. Should we have a url cache system ? Should we bother with it ? does IE do it ? ;) The 303 status (See Other) is an exception. The new URI given in the response should be retrieved using a GET method. This one is cute. You do your job at first location then server replies thanks for your job, now go there for more information -- Rene... Thx -- br/ 15:56:22 up 122 days, 17:10, 1 user, load average: 0.00, 0.01, 0.41 BOFH excuse #172: pseudo-user on a pseudo-terminal smime.p7s Description: S/MIME cryptographic signature
Is it possible...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ...to inquire the SMPP Message ID that my smsc returns??? I am thinking of some kind of variable that is given in the dlr-url. This, in case I want to do a query_sm to that message later. TIA, Rene Kluwen Chimit -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (MingW32) iD8DBQE/kcl84zfyqeBw6xURAqDhAJ9JkzE1eiP7lM0tjOJ2YtGfpLXTJwCcDyud v9jUdY7fh1wCpYbsm0lhjEE= =9TGX -END PGP SIGNATURE-
RE: Is it possible...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 True, I kind of figured that myself, looking at the source if I could write a patch. To clarify why I would want this: The reason that I want to know the message ID is because I also use a http interface to connect to the same sms gateway. This interface does give me the message id, and I use it to allow my users to browse through their sent messages and see DLR/Status info. Knowing the smpp message ID would allow me to keep the same user interface, regardless of how messages were sent (Kannel/SMPP or http api). Regards, Rene Kluwen Chimit - -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Stipe Tolj Sent: maandag 20 oktober 2003 16:50 To: Rene Kluwen Cc: [EMAIL PROTECTED] Subject: Re: Is it possible... Rene Kluwen wrote: ...to inquire the SMPP Message ID that my smsc returns??? I am thinking of some kind of variable that is given in the dlr-url. This, in case I want to do a query_sm to that message later. as Kannel does protocoll abstraction as much as possible, this is currently not possible AFAIK. Don't shoot me if I'm wrong. Any architectural ideas people may have to query on send messages? Stipe mailto:[EMAIL PROTECTED] - --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[EMAIL PROTECTED] http://www.wapme-systems.de/ - --- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (MingW32) iD8DBQE/lBbi4zfyqeBw6xURAtfIAJsFYSYTlFAhcmwl6ricKfUv7UhhHQCgq7cU ZNgGcT7/MAsGsp6MooKlXuo= =5pJV -END PGP SIGNATURE-
RE: Is it possible (smpp message id)...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 P.S.: I noticed that the message ID is stored in place of to-source in the DLR database. So at least, that is _something_... Regards, Rene Kluwen Chimit - -Original Message- From: Rene Kluwen [mailto:[EMAIL PROTECTED] Sent: zondag 19 oktober 2003 1:15 To: [EMAIL PROTECTED] Subject: Is it possible... - -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ...to inquire the SMPP Message ID that my smsc returns??? I am thinking of some kind of variable that is given in the dlr-url. This, in case I want to do a query_sm to that message later. TIA, Rene Kluwen Chimit - -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (MingW32) iD8DBQE/kcl84zfyqeBw6xURAqDhAJ9JkzE1eiP7lM0tjOJ2YtGfpLXTJwCcDyud v9jUdY7fh1wCpYbsm0lhjEE= =9TGX - -END PGP SIGNATURE- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (MingW32) iD8DBQE/mndT4zfyqeBw6xURAi0YAJ4kkLH5kA5uD8qAb0m21S5kQ+2yHgCeIk7c Vm5GYF5CG1F9hP92jfldwtE= =e0Sx -END PGP SIGNATURE-
RE: HTTP redirect
BASE tags in HTML documents are rarely used. Most HTML documents go without. Rene Kluwen Chimit -Original Message- From: devel-admin+AEA-kannel.org +AFs-mailto:devel-admin+AEA-kannel.org+AF0-On Behalf Of ghhou Sent: donderdag 27 november 2003 4:43 To: Stipe Tolj+ADs- devel+AEA-kannel.org Cc: rene.kluwen+AEA-chimit.nl Subject: HTTP redirect Stipe, The Base element in HTML specifies an absolute URI that acts as the base URI for resolving relative URIs. For example, given the following BASE declaration and A declaration: +ADwAIQ-DOCTYPE HTML PUBLIC +ACI--//W3C//DTD HTML 4.01//EN+ACI- +ACI-http://www.w3.org/TR/html4/strict.dtd+ACIAPg- +ADw-HTML+AD4- +ADw-HEAD+AD4- +ADw-TITLE+AD4-Our Products+ADw-/TITLE+AD4- +ADw-BASE href+AD0AIg-http://www.aviary.com/products/intro.html+ACIAPg- +ADw-/HEAD+AD4- +ADw-BODY+AD4- +ADw-P+AD4-Have you seen our +ADw-A href+AD0AIg-../cages/birds.gif+ACIAPg-Bird Cages+ADw-/A+AD4-? +ADw-/BODY+AD4- +ADw-/HTML+AD4- the relative URI +ACI-../cages/birds.gif+ACI- would resolve to: http://www.aviary.com/cages/birds.gif I'm sure you may be clear about the problem in proxy redirection. If no base element existing, problem will happen. Best Regards, Guanghua Hou - Original Message - From: +ACI-Stipe Tolj+ACI- +ADw-tolj+AEA-wapme-systems.de+AD4- To: +ACI-Rene Kluwen+ACI- +ADw-rene.kluwen+AEA-chimit.nl+AD4- Cc: +ACI-ghhou+ACI- +ADw-ghhou+AEA-utstar.com+AD4AOw- +ADw-devel+AEA-kannel.org+AD4- Sent: Thursday, November 27, 2003 8:20 AM Subject: Re: HTTP redirect +AD4- Rene Kluwen wrote: +AD4- +AD4- +AD4- +AD4- -BEGIN PGP SIGNED MESSAGE- +AD4- +AD4- Hash: SHA1 +AD4- +AD4- +AD4- +AD4- If you mean a relative URL in the Location: header. +AD4- +AD4- Then this is something against HTTP specs. One should not use them. +AD4- +AD4- Even though almost all browsers do prepend the original http-path if you do +AD4- +AD4- send them. +AD4- +AD4- nop, the point is different. +AD4- +AD4- Kannel wapbox does the Location following (hence redirection) +AD4- transparently to the WAP user agent. Hence relative URLs within the +AD4- WAP deck would result to address resources that are ment to be on a +AD4- previously redirected URL. And there is where we +ACI-may+ACI- run into +AD4- problems. +AD4- +AD4- Stipe +AD4- +AD4- mailto:tolj+AEA-wapme-systems.de +AD4- --- +AD4- Wapme Systems AG
RE: HTTP redirect
Content-Location is a http level equivalent of the base tag. But also not widely used. Why not just take the Location header of the previous response? Rene Kluwen Chimit -Original Message- From: devel-admin+AEA-kannel.org +AFs-mailto:devel-admin+AEA-kannel.org+AF0-On Behalf Of ghhou Sent: vrijdag 28 november 2003 2:21 To: rene.kluwen+AEA-chimit.nl+ADs- Stipe Tolj+ADs- devel+AEA-kannel.org Subject: Fw: HTTP redirect Rene Kluwen, In HTTP1.0, +ACI-Content-base+ACI- is base URI. But HTTP1.1 doesn't support this header. Can 'content-location' in the http response be used as base URL? Rfc2616 says +ACI-The value of Content-Location also defines the base URI for the entity.+ACI-. Best Regards, Guanghua Hou - Original Message - From: +ACI-Rene Kluwen+ACI- +ADw-rene.kluwen+AEA-chimit.nl+AD4- To: +ACI-ghhou+ACI- +ADw-ghhou+AEA-utstar.com+AD4AOw- +ACI-Stipe Tolj+ACI- +ADw-tolj+AEA-wapme-systems.de+AD4AOw- +ADw-devel+AEA-kannel.org+AD4- Sent: Thursday, November 27, 2003 10:39 PM Subject: RE: HTTP redirect +AD4- BASE tags in HTML documents are rarely used. +AD4- Most HTML documents go without. +AD4- +AD4- Rene Kluwen +AD4- Chimit +AD4- +AD4- -Original Message- +AD4- From: devel-admin+AEA-kannel.org +AFs-mailto:devel-admin+AEA-kannel.org+AF0-On Behalf Of +AD4- ghhou +AD4- Sent: donderdag 27 november 2003 4:43 +AD4- To: Stipe Tolj+ADs- devel+AEA-kannel.org +AD4- Cc: rene.kluwen+AEA-chimit.nl +AD4- Subject: HTTP redirect +AD4- +AD4- +AD4- Stipe, +AD4- +AD4- The Base element in HTML specifies an absolute URI that acts as the base URI +AD4- for resolving relative URIs. +AD4- For example, given the following BASE declaration and A declaration: +AD4- +AD4- +ADwAIQ-DOCTYPE HTML PUBLIC +ACI--//W3C//DTD HTML 4.01//EN+ACI- +AD4- +ACI-http://www.w3.org/TR/html4/strict.dtd+ACIAPg- +AD4- +ADw-HTML+AD4- +AD4- +ADw-HEAD+AD4- +AD4- +ADw-TITLE+AD4-Our Products+ADw-/TITLE+AD4- +AD4- +ADw-BASE href+AD0AIg-http://www.aviary.com/products/intro.html+ACIAPg- +AD4- +ADw-/HEAD+AD4- +AD4- +ADw-BODY+AD4- +AD4- +ADw-P+AD4-Have you seen our +ADw-A href+AD0AIg-../cages/birds.gif+ACIAPg-Bird Cages+ADw-/A+AD4-? +AD4- +ADw-/BODY+AD4- +AD4- +ADw-/HTML+AD4- +AD4- +AD4- the relative URI +ACI-../cages/birds.gif+ACI- would resolve to: +AD4- http://www.aviary.com/cages/birds.gif +AD4- +AD4- I'm sure you may be clear about the problem in proxy redirection. If no base +AD4- element existing, problem will happen. +AD4- +AD4- Best Regards, +AD4- Guanghua Hou +AD4- - Original Message - +AD4- From: +ACI-Stipe Tolj+ACI- +ADw-tolj+AEA-wapme-systems.de+AD4- +AD4- To: +ACI-Rene Kluwen+ACI- +ADw-rene.kluwen+AEA-chimit.nl+AD4- +AD4- Cc: +ACI-ghhou+ACI- +ADw-ghhou+AEA-utstar.com+AD4AOw- +ADw-devel+AEA-kannel.org+AD4- +AD4- Sent: Thursday, November 27, 2003 8:20 AM +AD4- Subject: Re: HTTP redirect +AD4- +AD4- +AD4- +AD4- Rene Kluwen wrote: +AD4- +AD4- +AD4- +AD4- +AD4- +AD4- -BEGIN PGP SIGNED MESSAGE- +AD4- +AD4- +AD4- Hash: SHA1 +AD4- +AD4- +AD4- +AD4- +AD4- +AD4- If you mean a relative URL in the Location: header. +AD4- +AD4- +AD4- Then this is something against HTTP specs. One should not use them. +AD4- +AD4- +AD4- Even though almost all browsers do prepend the original http-path if you +AD4- do +AD4- +AD4- +AD4- send them. +AD4- +AD4- +AD4- +AD4- nop, the point is different. +AD4- +AD4- +AD4- +AD4- Kannel wapbox does the Location following (hence redirection) +AD4- +AD4- transparently to the WAP user agent. Hence relative URLs within the +AD4- +AD4- WAP deck would result to address resources that are ment to be on a +AD4- +AD4- previously redirected URL. And there is where we +ACI-may+ACI- run into +AD4- +AD4- problems. +AD4- +AD4- +AD4- +AD4- Stipe +AD4- +AD4- +AD4- +AD4- mailto:tolj+AEA-wapme-systems.de +AD4- +AD4- --- +AD4- +AD4- Wapme Systems AG +AD4- +AD4- +AD4-
gwlib/gw_uuid_types.h missing
This is what I get compiling latest CVS version. Is there some file missing in the repository? gcc -D_REENTRANT=1 -I. -Igw -g -O2 -DBROKEN_PTHREADS=1 -I/usr/include/libxml 2/libxml -I/usr/include/libxml2 -I/usr/include -I'/usr/include/mysql' -I/usr /include/mysql -o gwlib/gw_uuid.o -c gwlib/gw_uuid.c gwlib/gw_uuid.c:51:33: gwlib/gw_uuid_types.h: No such file or directory make: *** [gwlib/gw_uuid.o] Error 1 Cheers! Rene Kluwen Chimit
RE: DLR sql select problem with message id containing space
Fix would be not too hard to implement... BUT... In the SMPP specs that I have (note: I am talking about v3.3) it says: Message ID, var max. 9. So taking off the terminating NUL this means that message ids can be 8 characters at most. I noticed this 'quirk' (message ids of more than 8 chars) also with a certain upstream provider that I have. Question: Has this changed in successive SMPP versions? Or is it just plainly against specifications? Regards, Rene Kluwen Chimit -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Alex KinchSent: dinsdag 23 december 2003 18:47To: [EMAIL PROTECTED]Subject: DLR sql select problem with message id containing space Hi, Just hooked up another SMPP connection, and they use rather large message ids. For example: 00047274 20031223170148.364 Kannel is inserting this whole value (including characters after the space) into the ts field on the dlr table. However, when it comes to receiving the delivery report, it's truncating the message id after the first space, so it does: DLR[mysql]: Looking for DLR smsc=, ts=00047274, dst=44xx, type=1 Which of course it won't find, as it's lost the rest of the message id. My C coding skills aren't up to much, but I would imagine it requires something that tests the first character after the space to see if it's numeric. Alex
RE: How to add new protocol to kannel?
The answer that I got (a long time ago) on the same question: Source files that have to be altered: gw/smscconn.c: to add an entry for your new smsc module gwlib/cfg.def: if u need special config params for that connection then u need to write your module. Start, mmm look at the smpp module or the emi2 module. It should meet the requirements of your upstream provider, it should meet the requirements as in smscconn_p.h and it should be nice and well behaved ;-) Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of xtjmail Sent: maandag 19 januari 2004 8:31 To: [EMAIL PROTECTED] Subject: How to add new protocol to kannel? Why no one reply? Please Help me,Thanks very much. ==, [EMAIL PROTECTED]://www.126.com25M! , !
RE: [PATCH] octstr performance
Browsed through your patch and couldn't find any boo-boo's with a bare eye. const parameters are always good... you never know when you are going to need a const, later. +1 from me -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alexander Malysh Sent: maandag 19 januari 2004 12:56 To: [EMAIL PROTECTED] Subject: [PATCH] octstr performance Hi List, attached is a patch that adds more 'const' modifiers to 'Octstr' and get better 'octstr' performance (some functions were hand-optimized but not all, means more work should be done;)). Also you can find some simple benchmarks in attached .txt file. Comments and votes please! -- Best regards / Mit besten Grüßen aus Düsseldorf Dipl.-Ing. Alexander Malysh ___ Centrium GmbH Vogelsanger Weg 80 40470 Düsseldorf Fon: +49 (0211) 74 84 51 80 Fax: +49 (0211) 277 49 109 email: [EMAIL PROTECTED] web: www.centrium.de msn: [EMAIL PROTECTED] icq: 98063111 ___ Please avoid sending me Word, Excel or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
Wanted...
Access to shell accounts with access to a working SQL server (Postgres, Oracle, MS-SQL) setup. Also it helps to have client libraries installed or be able to install :)... This to develop / test Kannel's sqlbox. Regards, Rene Kluwen Chimit
RE: SMPPbox updates
Stipe, I took up Alex Kinch' challenge on RentACoder and (almost) finished sqlbox now. My question (see your email below). I changed configure.in to allow for libraries that support MS SQL (currently sybase or freetds). What exactly was your plan or problem on how to make 'modulary configure'? So I won't do work for nothing. And secondly, I may be able to help you out with the problem you are having with it. Kind regards, Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Stipe Tolj Sent: woensdag 12 november 2003 18:28 To: Alex Kinch Cc: [EMAIL PROTECTED] Subject: Re: SMPPbox updates Alex Kinch schrieb: Sorry to sound like a broken record, but wondered how smppbox was coming along. Actually I was also wondering how the sqlbox/send using sql insert trigger was going, but one thing at a time :-) I still have no convinient way in makeing things modulary configure, hence smppbox as a seperate module is still on hold. And the sqlbox is definetly lost. I didn't had any backup copies of that beast that lived on my laptop. Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[EMAIL PROTECTED] http://www.wapme-systems.de/ --- -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.2.2 (Cygwin) mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -END PGP PUBLIC KEY BLOCK-
RE: PostgresSQL DLR support
About the psotgres patch: In configure.in linking is done against -llibpg which should be (for me) -lpg. Alexander: I saw your start of select/update abstraction. The one in which select takes a **List parameter. Are we talking about the same thing now? Implementing this won't be too hard and I can take that job upon me, as I am doing sqlbox now as well (mysql, postgres, mssql) which would also benefit from it. But.: How about different SQL syntax of different SQL server implementation? As an example: mysql: select * from table limit 0,1; ms-msql: select top 1 * from table; Also create table and field-types are kind of different. Regards, Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Stipe Tolj Sent: dinsdag 3 februari 2004 14:51 Cc: [EMAIL PROTECTED] Subject: Re: PostgresSQL DLR support Alexander Malysh wrote: hmm, that was my first attempt to get things right ;) Oracle's OCI is just complex and I've introduced 'select/update' within dbpool. IMO, we should abstract more, so that dbpool deal with DBConnection and DBConnection object should implement 'select/update'. +1 on a full dbpool abstraction layer. There are projects that try to do this. Martin, if you can have a view into those?! Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[EMAIL PROTECTED] http://www.wapme-systems.de/ --- -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.2.2 (Cygwin) mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -END PGP PUBLIC KEY BLOCK-
RE: PostgresSQL DLR support
I know linking is done w/o lib prefix. But it was an error in the Postgres patch. This was not particularly directed to anybody special except the ones who want to use that patch. About generic SQL support like dbpool_oracle.c: That was exactly what I was talking about. I dont like the select syntax solution like in libsdb dlr support so much. Like for instance some DB's not only use other names to call an animal. But also put those names in different places (compare: 'select ... limit X' with 'select top X '). The adodb style PHP abstraction layer that is really popular has seperate .select and .select_limit methods *shrugs*... A different method for every different kind of statement is also not ideal. But it is better than a different method for every db system. Just my 2 cts. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alexander Malysh Sent: dinsdag 3 februari 2004 15:52 To: Rene Kluwen; Stipe Tolj Cc: [EMAIL PROTECTED] Subject: Re: PostgresSQL DLR support On Tuesday 03 February 2004 15:32, Rene Kluwen wrote: About the psotgres patch: In configure.in linking is done against -llibpg which should be (for me) -lpg. FYI: linking is always done with -lpg (w/o lib prefix). Alexander: I saw your start of select/update abstraction. The one in which select takes a **List parameter. Are we talking about the same thing now? yep... but I'm too busy to make further changes. You can look into dbpool_oracle.c as example (it's not a ideal solution but works ;)). Other ideas on how todo it are highly welcome ;) Implementing this won't be too hard and I can take that job upon me, as I am doing sqlbox now as well (mysql, postgres, mssql) which would also benefit from it. But.: How about different SQL syntax of different SQL server implementation? As an example: mysql: select * from table limit 0,1; ms-msql: select top 1 * from table; Also create table and field-types are kind of different. yes, and it's not easy solvable problem :( We can try todo something I did for libsdb dlr support? Regards, Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Stipe Tolj Sent: dinsdag 3 februari 2004 14:51 Cc: [EMAIL PROTECTED] Subject: Re: PostgresSQL DLR support Alexander Malysh wrote: hmm, that was my first attempt to get things right ;) Oracle's OCI is just complex and I've introduced 'select/update' within dbpool. IMO, we should abstract more, so that dbpool deal with DBConnection and DBConnection object should implement 'select/update'. +1 on a full dbpool abstraction layer. There are projects that try to do this. Martin, if you can have a view into those?! Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[EMAIL PROTECTED] http://www.wapme-systems.de/ --- -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.2.2 (Cygwin) mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -END PGP PUBLIC KEY BLOCK- -- Best regards / Mit besten Grüßen aus Düsseldorf Dipl.-Ing. Alexander Malysh ___ Centrium GmbH Vogelsanger Weg 80 40470 Düsseldorf Fon: +49 (0211) 74 84 51 80 Fax: +49 (0211) 277 49 109 email: [EMAIL PROTECTED] web: www.centrium.de msn: [EMAIL PROTECTED] icq: 98063111 ___ Please avoid sending me Word, Excel or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
RE: PostgresSQL DLR support
Currently, I am fixing the start that Alexander made in dbpool_oracle.c. This means that we have 2 generic database functions, update(Octstr *sql) and select(Octstr *sql, List **result). (apart from configuration and shutdown routines). Would this not be sufficient?? I already made this for mysql, postgres, oracle (this one should exist already) and they work. I will also make this for ms sql server and -if needed- I can make this for sdb and sqlite. So far I programmed about 1000 lines in sqlbox and sql interfaces. Would this patch be accepted in current CVS? Kind regards, Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Stipe Tolj Sent: woensdag 4 februari 2004 14:00 To: Martin Atukunda Cc: [EMAIL PROTECTED] Subject: Re: PostgresSQL DLR support Martin Atukunda wrote: I'd like a pointer to some of the projects that do this, so I can have a look at them. There seems to be nothing database related at: http://kannel.org/roadmap.shtml#projects that roadmap is outdated totally. @Alex: we have to add things from our roadmap proposal here. I'll try to scratch things up this week. At least I got one good reference for the abstraction layer for DBs, which is the libdbi Project, see http://libdbi-drivers.sourceforge.net/ Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[EMAIL PROTECTED] http://www.wapme-systems.de/ --- -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.2.2 (Cygwin) mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -END PGP PUBLIC KEY BLOCK-
Wat does the...
...UUID(id) parameter in the sms-msg* structure stand for? And... how would I represent that as non-binary string? -- Rene
RE: Progress on the sqlbox
It is in the testing phase. I could pass you a copy of the patch if you want to help out with that. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: zaterdag 14 februari 2004 15:22 To: [EMAIL PROTECTED] Subject: Progress on the sqlbox Hi, I'm wondering if there has been any progress on the sqlbox ? With regards, -Ken.
RE: 5 gsm modems in one computer?
Apart from multiport cards, you can alternatively use RS232 - USB adapters. They are quite cheap and widely available. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of David Ang Sent: maandag 22 maart 2004 9:50 To: [EMAIL PROTECTED] Subject: 5 gsm modems in one computer? Hi guys... please help. i need to set up 5 Nokia 30 gsm modems in one computer. my problem here is, since nokie 30's cable is a serial, and a computer has only 2 com/serial port, how am i going to plug in the other 3 gsm modems? please provide solutions, ways how to set this up. many thanks for your time. -- Best regards, David Ang
Re: SMPP Server for Kannel
Yes, you should be able to replace sms box with another kind of box. That is what the current setup is meant for. I have some experience writing both SMPP servers and writing alternative boxes (in this case: an sqlbox that logs incoming and outgoing messages) as well... Rene Kluwen Chimit - Original Message - From: Cesar Garcia [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 22, 2004 4:45 AM Subject: SMPP Server for Kannel Hi, I'm thinking in build a SMPP Server for Kannel. I can replace the smsbox function for a new server box. You can give me some orientation about this point. SOme body have similar solution. Regards === Ing. Csar Garca email: [EMAIL PROTECTED] CEOS Integradores de Sistemas, C.A. Barcelona, Edo. Anzoategui Venezuela Telf. / Fax : +58-281-2749969
Re: Sqlbox?
Mike, There's an sqlbox of Stipe Tolj that he indicated as being lost. Because of that (in co-operation with Alex Kinch of sendmytxt) I wrote a new one that still is to be sent as a patch to the list. I will try to do this, as soon as I can find the time for it. Especially since is requested to split it up into more smaller patches. Rene Kluwen Chimit - Original Message - From: DILWORTH MICHAEL [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 28, 2004 9:13 AM Subject: Sqlbox? Hi all I am wondering if the SQLBox ever made it into the cvs or posted as a patch. I would be interested in trying it out. Thanks mike
Compile error
I am back from being away from the kannel list for a while. And with a question immediately: When compiling current CVS, I get: [EMAIL PROTECTED] gateway]$ make byacc -d -p ws_yy_ wmlscript/wsgram.y mv y.tab.c wmlscript/wsgram.c byacc: e - line 111 of wmlscript/wsgram.y, syntax error %pureparser ^ make: *** [wmlscript/wsgram.c] Error 1 I already did a make distclean (which gave me the same error) and a new ./configure. This is only on one machine, but this machine did not give me an error before. On other machines, Kannel compiles well. Does anybody recognize this? Rene Kluwen
[patch] SQLBOX
For the patch: http://www.chimit.nl/kannel/sqlbox_patch.tar I know this needs more documentation, but this patch has been kept from the mailing list so long already that I didnt want to refrain it from you anymore. For me also the standard excuse holds that I have been so busy lately that I have not been able to keep up with the list anymore. Anyhow... Here, a working version of the SQLBOX is attached. In the tar ball, there are a number of files that have been split up and a sqlbox_patch.diff that has to be applied. The patch includes Postgres, MySQL and MS-SQL support (also for DLR's) for anybody that feels the need to use it. MS-SQL client libraries are either sybase or free-tds (./configure autodetects). Here follows some documentation that in fact (I admit) should be included in the patch against the doc tree: There is one extra configure option in group = smsbox, which is: # bearerbox-is-sqlbox indicates if the smsbox is connected to the bearerbox or an sql box bearerbox-is-sqlbox = true/false For the rest, the group = sqlbox contains the following options: group = sqlbox # id corresponds to id in group = mysql-connection. # this is analogous to id in group = dlr-db id = dlr-db2 # smsbox-id indicates the box where SQL-injected messages appear to be coming fr om smsbox-id = sqlbox2 # bearerbox host to connect to bearerbox-host = 127.0.0.1 # smsbox port to be listening on smsbox-port = 13005 smsbox-port-ssl = false # sql-log-table is the table used to log all sent messages sql-log-table = sent_sms # sql-insert-table is the table that is monitored for new messages to send sql-insert-table = send_sms # global sender: If no sender is specified in sql-insert-table then this # value is used. global-sender = 06121 # log-file = # log-level = 10 # ssl-client-certkey-file = # ssl-server-cert-file = # ssl-server-key-file = # ssl-trusted-ca-file =
RE: Compile error
Alan's solution (removing wmlscript/wsgram.y) worked. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alexander Malysh Sent: maandag 24 mei 2004 10:17 To: [EMAIL PROTECTED] Cc: Rene Kluwen Subject: Re: Compile error Hi Rene, would you please try to generate wmlscript/wsgram.c with bison instead of byacc? It works just fine here: bison (GNU Bison) 1.875 Thanks in advance. On Friday 21 May 2004 23:09, Rene Kluwen wrote: I am back from being away from the kannel list for a while. And with a question immediately: When compiling current CVS, I get: [EMAIL PROTECTED] gateway]$ make byacc -d -p ws_yy_ wmlscript/wsgram.y mv y.tab.c wmlscript/wsgram.c byacc: e - line 111 of wmlscript/wsgram.y, syntax error %pureparser ^ make: *** [wmlscript/wsgram.c] Error 1 I already did a make distclean (which gave me the same error) and a new ./configure. This is only on one machine, but this machine did not give me an error before. On other machines, Kannel compiles well. Does anybody recognize this? Rene Kluwen -- Best regards / Mit besten Grüßen aus Düsseldorf Dipl.-Ing. Alexander Malysh ___ Centrium GmbH Vogelsanger Weg 80 40470 Düsseldorf Fon: +49 (0211) 74 84 51 80 Fax: +49 (0211) 277 49 109 email: [EMAIL PROTECTED] web: www.centrium.de msn: [EMAIL PROTECTED] icq: 98063111 ___ Please avoid sending me Word, Excel or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
-DOPENSSL_NO_KRB5
On a machine at a client's location, I got a lot of crazy error messages compiling Kannel. The problem was the following: It needed -DOPENSSL_NO_KRB5 as a gcc option which ./configure had missed. This is just a registration of the fact that this bug is there. Maybe somebody with autoconf experience can fix this? Cheers, Rene Kluwen Chimit
RE: -DOPENSSL_NO_KRB5
Thanks... Yours is a better solution. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nam Nguyen Sent: vrijdag 4 juni 2004 3:27 To: [EMAIL PROTECTED] Subject: RE: -DOPENSSL_NO_KRB5 I got the same messages like yours. But after ./configure finishes, locate the path to krb5.h, then add this path to the Makefile. [Before] CFLAGS=-D_REENTRANT=1 -I. -Igw -O2 -I/usr/include/libxml2 -I/usr/include/ope nssl [After] CFLAGS=-D_REENTRANT=1 -I. -Igw -O2 -I/usr/include/libxml2 -I/usr/include/ope nssl -I/usr/kerberos/include Then run make with this Makefile as usual. Enjoy, Nam Nguyen [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Rene Kluwen Sent: Thursday, June 03, 2004 11:13 PM To: [EMAIL PROTECTED] Subject: -DOPENSSL_NO_KRB5 On a machine at a client's location, I got a lot of crazy error messages compiling Kannel. The problem was the following: It needed -DOPENSSL_NO_KRB5 as a gcc option which ./configure had missed. This is just a registration of the fact that this bug is there. Maybe somebody with autoconf experience can fix this? Cheers, Rene Kluwen Chimit
RE: [patch] SQLBOX
With apologies to the people that downloaded already and stumbled upon errors, I present the SQL Box patch against current CVS version: http://www.chimit.nl/kannel/sqlbox_patch-20040608.tar Please test and vote. Kind regards, Rene Kluwen Chimit -Original Message-From: Stephen [mailto:[EMAIL PROTECTED]Sent: dinsdag 8 juni 2004 14:36To: [EMAIL PROTECTED]Subject: [patch] SQLBOX Hi Rene Ive downloaded your SQL Box patch as it would be a great addon for Kannel. However, I get errors when patching and compiling it. Which version of Kannel has SQL Box been tested with? I am testing it with a recent Snapshot.ThanksKind Regards Stephen ---Outgoing mail is certified Virus Free.Checked by AVG anti-virus system (http://www.grisoft.com).Version: 6.0.700 / Virus Database: 457 - Release Date: 2004/06/06
RE: [patch] SQLBOX
Hi Alexander, Attached is the file that you are looking for. Thanks for committing the PG DBPool support already... It made the sqlbox patch fail with some people... But that doesnt matter :)... A new patch is available already... Including the dlr_pgsql.c as well... About dbpool_mssql.c: Will fix both issues... Sorry, this is copy/pasted from an existing (home-made) abstraction class. Meanwhile, I have had some (really valid) questions from users by email and I will post them to this list together with the answers later. Question about the userguide: Which format is it in really and which is the preferred way to update? Warm regards, Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alexander Malysh Sent: dinsdag 8 juni 2004 12:33 To: [EMAIL PROTECTED] Cc: Rene Kluwen Subject: Re: [patch] SQLBOX Hi Rene, I have picked PostrgeSQL DBPool support and commited in a slightly modified version to cvs. I believe, you forgot to include 'dlr_pgsql.c' into tar archive? Please send it as separate patch and I will review/commit it... Btw. userguide patch would be great too ;) Thanks in advance! P.S. 'dbpool_mssql.c' included in tar archive, need some more work to be commited: 1) whitespaces (don't use tabs) 2) get rid of 'fprintf' use debug/info/error provided by kannel instead On Friday 21 May 2004 23:36, Rene Kluwen wrote: For the patch: http://www.chimit.nl/kannel/sqlbox_patch.tar I know this needs more documentation, but this patch has been kept from the mailing list so long already that I didnt want to refrain it from you anymore. For me also the standard excuse holds that I have been so busy lately that I have not been able to keep up with the list anymore. Anyhow... Here, a working version of the SQLBOX is attached. In the tar ball, there are a number of files that have been split up and a sqlbox_patch.diff that has to be applied. The patch includes Postgres, MySQL and MS-SQL support (also for DLR's) for anybody that feels the need to use it. MS-SQL client libraries are either sybase or free-tds (./configure autodetects). Here follows some documentation that in fact (I admit) should be included in the patch against the doc tree: There is one extra configure option in group = smsbox, which is: # bearerbox-is-sqlbox indicates if the smsbox is connected to the bearerbox or an sql box bearerbox-is-sqlbox = true/false For the rest, the group = sqlbox contains the following options: group = sqlbox # id corresponds to id in group = mysql-connection. # this is analogous to id in group = dlr-db id = dlr-db2 # smsbox-id indicates the box where SQL-injected messages appear to be coming fr om smsbox-id = sqlbox2 # bearerbox host to connect to bearerbox-host = 127.0.0.1 # smsbox port to be listening on smsbox-port = 13005 smsbox-port-ssl = false # sql-log-table is the table used to log all sent messages sql-log-table = sent_sms # sql-insert-table is the table that is monitored for new messages to send sql-insert-table = send_sms # global sender: If no sender is specified in sql-insert-table then this # value is used. global-sender = 06121 # log-file = # log-level = 10 # ssl-client-certkey-file = # ssl-server-cert-file = # ssl-server-key-file = # ssl-trusted-ca-file = -- Best regards / Mit besten Grüßen aus Düsseldorf Dipl.-Ing. Alexander Malysh ___ Centrium GmbH Vogelsanger Weg 80 40470 Düsseldorf Fon: +49 (0211) 74 84 51 80 Fax: +49 (0211) 277 49 109 email: [EMAIL PROTECTED] web: www.centrium.de msn: [EMAIL PROTECTED] icq: 98063111 ___ Please avoid sending me Word, Excel or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html dlr_pgsql.c Description: Binary data
RE: [PATCH] SMS dropped on the floor when SMSCConn down
Is there a better way to interface directly to bearerbox and bypass smsbox altogether? Another approach is to connect to the bearerbox directly. Without an intermediate smsbox. This approach is generally not recommended. Why? My question in return would be: Why not implement the SMPP (in case you are using that) side as well and have nothing in between? The sqlbox partly supports what you want by polling for messages that can be injected in a sql table (including all options) and sending them out through the bearerbox. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Martin Lucina Sent: dinsdag 8 juni 2004 13:39 To: Stipe Tolj Cc: [EMAIL PROTECTED] Subject: Re: [PATCH] SMS dropped on the floor when SMSCConn down [EMAIL PROTECTED] said: -1 on the patch, first of all. The problem can be described as follows: your client sends a msg which (in case the smsc link is in dead state) can not be transported. Kannel treads this msg as untransportable and hence the mack-ack.nack = ack_failed _is_ send to your client application (smsbox in the usualy case). A related question in this case is -- given that our application effectively does it's own routing, billing, concatenation and character set conversion of SMS messages, does it make sense for us to be interfacing to Kannel at the service layer? Is there a better way to interface directly to bearerbox and bypass smsbox altogether? This is more a semantical problem here. We may descide to threat such unroutable messages with failing DLRs. Any opionions from the others if this is reasonable?! It seems reasonable to me -- our application acts as a high-level interface for other services running on top of it, so there is a requirement for it to be able to keep track of a message over it's entire lifetime, from when it enters our system until it leaves it (is processed by the service). BTW, why isn't it an option to let the smsc links online and let them try to reconnect on their own while you drop of the tcp layer from it? This would cause Kannel to hold up the msgs in the internal quques and dispose them when the link is established again. Where the DLRs will get transported then too. The problem with this option is that I would like Kannel to reconnect ASAP after the PPP link comes back up. If I were to leave the SMSCs up at the Kannel end then Kannel will (sensibly) employ it's backoff algorithm for reconnecting, which is fine if you are experiencing a network error, but not if you want to poll the SMSC at regular intervals. The whole solution is a hack, currently the operator is refusing any other options outside of dialup or leased line and the amount of traffic on this link does not make it worthwhile to implement a leased line here. Very silly of them, since all the other operators in Belgium happily let us connect to their SMSCs via IPSec VPNs. -mato
RE: [patch] SQLBOX
Here it is... dbpool_mssql.c without tabs and without fprintf's... I really dont know what the first parameter of the function error(...) is for, but I figure that 0 is a safe value, since I see that more often :)... Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alexander Malysh Sent: woensdag 9 juni 2004 20:28 To: Rene Kluwen Cc: [EMAIL PROTECTED] Subject: Re: [patch] SQLBOX Hi Rene, On Wednesday 09 June 2004 20:01, Rene Kluwen wrote: Hi Alexander, Attached is the file that you are looking for. hmm, do you read ML ;) I have commited it already :) Thanks for committing the PG DBPool support already... It made the sqlbox patch fail with some people... But that doesnt matter :)... A new patch is available already... Including the dlr_pgsql.c as well... Hmm, I would say: Thank you for the patch! About dbpool_mssql.c: Will fix both issues... Sorry, this is copy/pasted from an existing (home-made) abstraction class. ok Meanwhile, I have had some (really valid) questions from users by email and I will post them to this list together with the answers later. Question about the userguide: Which format is it in really and which is the preferred way to update? patch against current cvs is preferred. userguide is in Docbook format. Warm regards, Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alexander Malysh Sent: dinsdag 8 juni 2004 12:33 To: [EMAIL PROTECTED] Cc: Rene Kluwen Subject: Re: [patch] SQLBOX Hi Rene, I have picked PostrgeSQL DBPool support and commited in a slightly modified version to cvs. I believe, you forgot to include 'dlr_pgsql.c' into tar archive? Please send it as separate patch and I will review/commit it... Btw. userguide patch would be great too ;) Thanks in advance! P.S. 'dbpool_mssql.c' included in tar archive, need some more work to be commited: 1) whitespaces (don't use tabs) 2) get rid of 'fprintf' use debug/info/error provided by kannel instead On Friday 21 May 2004 23:36, Rene Kluwen wrote: For the patch: http://www.chimit.nl/kannel/sqlbox_patch.tar I know this needs more documentation, but this patch has been kept from the mailing list so long already that I didnt want to refrain it from you anymore. For me also the standard excuse holds that I have been so busy lately that I have not been able to keep up with the list anymore. Anyhow... Here, a working version of the SQLBOX is attached. In the tar ball, there are a number of files that have been split up and a sqlbox_patch.diff that has to be applied. The patch includes Postgres, MySQL and MS-SQL support (also for DLR's) for anybody that feels the need to use it. MS-SQL client libraries are either sybase or free-tds (./configure autodetects). Here follows some documentation that in fact (I admit) should be included in the patch against the doc tree: There is one extra configure option in group = smsbox, which is: # bearerbox-is-sqlbox indicates if the smsbox is connected to the bearerbox or an sql box bearerbox-is-sqlbox = true/false For the rest, the group = sqlbox contains the following options: group = sqlbox # id corresponds to id in group = mysql-connection. # this is analogous to id in group = dlr-db id = dlr-db2 # smsbox-id indicates the box where SQL-injected messages appear to be coming fr om smsbox-id = sqlbox2 # bearerbox host to connect to bearerbox-host = 127.0.0.1 # smsbox port to be listening on smsbox-port = 13005 smsbox-port-ssl = false # sql-log-table is the table used to log all sent messages sql-log-table = sent_sms # sql-insert-table is the table that is monitored for new messages to send sql-insert-table = send_sms # global sender: If no sender is specified in sql-insert-table then this # value is used. global-sender = 06121 # log-file = # log-level = 10 # ssl-client-certkey-file = # ssl-server-cert-file = # ssl-server-key-file = # ssl-trusted-ca-file = -- Best regards / Mit besten Grüßen aus Düsseldorf Dipl.-Ing. Alexander Malysh ___ Centrium GmbH Vogelsanger Weg 80 40470 Düsseldorf Fon: +49 (0211) 74 84 51 80 Fax: +49 (0211) 277 49 109 email: [EMAIL PROTECTED] web: www.centrium.de msn: [EMAIL PROTECTED] icq: 98063111 ___ Please avoid sending me Word, Excel or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html -- Best regards / Mit besten Grüßen aus Düsseldorf Dipl.-Ing. Alexander Malysh ___ Centrium GmbH Vogelsanger Weg 80 40470 Düsseldorf Fon: +49 (0211) 74 84 51 80 Fax: +49 (0211) 277 49 109 email: a.malysh at centrium.de web: www.centrium.de msn: olek2002 at hotmail.com icq: 98063111 ___ Please
smsc = http, system-type = kannel
Does anybody ever use this SMSC? Has it been tested? Is it reliable? I got two big issues here. One is: (from the log) Parsing URL `http://mexico.XXX.com:13004/?username=XXXpassword=XXXto=31651931985text= Test+http+%231from=31651931985coding=0account=XXX:kluwensmsc=SMPPCONN04 dlr-url=http%3A%2F%2Fmexico.kluwen.com%2F~rene%2Fdlr.php%3Ftype%3D%25d%26id% 3D315drl-mask=31' As you can see, dlr-mask is spelt the wrong way (drl-mask). Another thing is that when trying to do the gateway DLR, I get: (from the log) URL http%3A%2F%2Fmexico.kluwen.com%2F~rene%2Fdlr.php%3Ftype%3D%25d%26id%3D320 doesn't start with `http://' nor `https://' Cheers! Rene Kluwen Chimit --- Anarchism is a tendency in the history of human thought and action which seeks to identify coercive, authoritarian, and hierarchic structures of all kinds and to challenge their legitimacy -- and if they cannot justify their legitimacy, which is quite commonly the case, to work to undermine them and expand the scope of freedom. (Noam Chomsky)
RE: smsc = http, system-type = kannel
The line comes from smsbox.log.
Rene Kluwen
Chimit
-Original Message-
From: Stipe Tolj [mailto:[EMAIL PROTECTED]
Sent: dinsdag 29 juni 2004 16:25
To: Rene Kluwen
Cc: [EMAIL PROTECTED]
Subject: Re: smsc = http, system-type = kannel
Rene Kluwen schrieb:
Does anybody ever use this SMSC? Has it been tested? Is it reliable?
I got two big issues here. One is:
(from the log)
Parsing URL
`http://mexico.XXX.com:13004/?username=XXXpassword=XXXto=31651931985text=
Test+http+%231from=31651931985coding=0account=XXX:kluwensmsc=SMPPCONN04
dlr-url=http%3A%2F%2Fmexico.kluwen.com%2F~rene%2Fdlr.php%3Ftype%3D%25d%26id%
3D315drl-mask=31'
As you can see, dlr-mask is spelt the wrong way (drl-mask).
correct, this is a stupid typo. commited the following to cvs:
RCS file: /home/cvs/gateway/gw/smsc/smsc_http.c,v
retrieving revision 1.34
diff -u -r1.34 smsc_http.c
--- gw/smsc/smsc_http.c 22 Jan 2004 13:26:04 - 1.34
+++ gw/smsc/smsc_http.c 29 Jun 2004 14:20:23 -
@@ -362,11 +362,10 @@
if (sms-sms.smsc_id) /* proxy the smsc-id to the next instance
*/
octstr_format_append(url, smsc=%S, sms-sms.smsc_id);
if (sms-sms.dlr_url) {
-octstr_url_encode(sms-sms.dlr_url);
-octstr_format_append(url, dlr-url=%S, sms-sms.dlr_url);
+octstr_format_append(url, dlr-url=%E, sms-sms.dlr_url);
}
if (sms-sms.dlr_mask != DLR_UNDEFINED sms-sms.dlr_mask !=
DLR_NOTHING)
-octstr_format_append(url, drl-mask=%d, sms-sms.dlr_mask);
+octstr_format_append(url, dlr-mask=%d, sms-sms.dlr_mask);
headers = list_create();
debug(smsc.http.kannel, 0, HTTP[%s]: Start request,
Another thing is that when trying to do the gateway DLR, I get:
(from the log)
URL
http%3A%2F%2Fmexico.kluwen.com%2F~rene%2Fdlr.php%3Ftype%3D%25d%26id%3D320
doesn't
start with `http://' nor `https://'
??? hmmm, we need to urlencode the DLR-URL within the HTTP call from
smsc_http to smsbox, right? smsbox should be then requierd to
urldecode the string back again for further processing, right?
from which log does this come?
Stipe
mailto:[EMAIL PROTECTED]
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:[EMAIL PROTECTED]
http://www.wapme-systems.de/
---
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v1.2.2 (Cygwin)
mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS
OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2
nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT
dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv
bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID
AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl
OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ
K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H
g2HyLAEKQIp30Q==
=aYCI
-END PGP PUBLIC KEY BLOCK-
RE: Problem on bearer box
Try writing admin-allow-ip completely in lowercase. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Oscar Medina Duarte Sent: woensdag 22 september 2004 0:21 To: Kannel Development list Subject: Problem on bearer box Heelp !! Im having this error on bearer box: 2004-09-22 00:13:33 [30405] [0] INFO: Debug_lvl = -1, log_file = none, log_lvl = 0 2004-09-22 00:13:33 [30405] [0] ERROR: Group 'core' may not contain field 'Admin-allow-ip'. 2004-09-22 00:13:33 [30405] [0] ERROR: Error found on line 23 of file `../conf/telcel_cool.conf'. 2004-09-22 00:13:33 [30405] [0] PANIC: Couldn't read configuration from `../conf/telcel_cool.conf'. 2004-09-22 00:13:33 [30405] [0] PANIC: ../../deploy/bin/bearerbox(gw_panic+0x19a) [0x80d2cc3] 2004-09-22 00:13:33 [30405] [0] PANIC: ../../deploy/bin/bearerbox(main+0x163) [0x80526a3] 2004-09-22 00:13:33 [30405] [0] PANIC: /lib/tls/libc.so.6(__libc_start_main+0x108) [0x402cb7f8] But the real problem is that my config file looks like this: group = core admin-port = 26659 admin-password = status-password = admin-deny-ip = *.*.*.* Admin-allow-ip = 127.0.0.1;200.88.23.188 smsbox-port = 26657 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1;200.88.23.188 wdp-interface-name = * log-file = /opt/Kannel/logs/bearer.log log-level = 0 access-log = /opt/Kannel/logs/kannel.access What can be wrong ? what can I do ? is this a bug ? Thanx to all! == Oscar
new sqlbox patch
The sqlbox programming has been a little bit behind on the kannel mainline development. Business is going well, but unfortunately it means that open source projects need a little more time to catch up. Either way, here is a link to the new patch that patches cleanly against current HEAD version. It is made available on the web because (luckily) the list doesnt allow big emails. The link: http://www.chimit.nl/kannel/sqlbox_patch-20041012.tar Apart from a few compilation warnings, this is the same version as before. Please email all experiences (good or bad) to the list or directly to me, so that appropriate action can be undertaken. Cheers! Rene Kluwen Chimit p.d.: I forget to include the FAQ, so that why it was attached seperately. A section about how-to-compile has been included. This is the SQLBOX FAQ. It's function is to help people going, at least before there is a proper documentation patch. Q. How do I compile sqlbox support into Kannel? A. untar sqlbox_patch.tar in the main Kannel source folder (the one where configure, Makefile, etc. reside). Then type: 'patch -p0 sqlbox.patch' (without the single quotes) Then (as usual): make distclean; ./configure --your-options; make Q. Is there any documentation that could help in setting it up and gain a better understanding of it? A. When runnig for the first time, sqlbox creates automatically 2 tables, called send_sms and sent_sms (configurable). In the first table, you can insert SMS messages that will be sent out (MT). In the second table, all SMS traffic from and to smsbox is logged. In kannel.conf, the following options are added: The patch includes Postgres, MySQL and MS-SQL support (also for DLR's) for anybody that feels the need to use it. MS-SQL client libraries are either sybase or free-tds (./configure autodetects). Here follows some documentation that in fact (I admit) should be included in the patch against the doc tree: There is one extra configure option in group = smsbox, which is: # bearerbox-is-sqlbox indicates if the smsbox is connected to the bearerbox or an sql box bearerbox-is-sqlbox = true/false For the rest, the group = sqlbox contains the following options: group = sqlbox # id corresponds to id in group = mysql-connection. # this is analogous to id in group = dlr-db id = dlr-db2 # smsbox-id indicates the box where SQL-injected messages appear to be coming fr om smsbox-id = sqlbox2 # bearerbox host to connect to bearerbox-host = 127.0.0.1 # smsbox port to be listening on smsbox-port = 13005 smsbox-port-ssl = false # sql-log-table is the table used to log all sent messages sql-log-table = sent_sms # sql-insert-table is the table that is monitored for new messages to send sql-insert-table = send_sms # global sender: If no sender is specified in sql-insert-table then this # value is used. global-sender = 06121 # log-file = # log-level = 10 # ssl-client-certkey-file = # ssl-server-cert-file = # ssl-server-key-file = # ssl-trusted-ca-file = Q. Does sqlbox replace sms box or is It an additional module that must be run? A. sqlbox is an additional module. You now have to start kannel in the following manner: 1st: bearerbox conf-file 2nd: sqlbox conf-file 3rd: smsbox conf-file and wapbox conf-file A picture of the new situation (with sqlbox included is as follows): http request -- [ smsbox ] -- [ sqlbox ] -- [ bearerbox ] -- sms gateway I hope this picture make things clear. In text: sqlbox is sitting in between smsbox and bearerbox, passing all messages back and forth between the two. As a side-effect, also the messages that are passed back and forth are logged in the sent_sms table. Q. Can you use http requests or posting messages to the send_sms table to send messages? A. You can use both http requests to the smsbox, as usual (nothing changes here), as well as insert messages in send_sms. SQL Box checks the records in send_sms every so many seconds and posts them to the bearerbox to be delivered to the SMSC. After that, the entry in send_sms is deleted. Q. (Configuration options part #1) bearerbox-is-sqlbox = true/false If this value is set to true would you not have to run the sqlbox as the bearerbox should function as the sqlbox? A. It is as follows: if this value is set to true then smsbox connects to sqlbox, rather than the bearerbox. (see the previous picture) Q. (Configuration options part #2) smsbox-id = sqlbox2 - Can this be any unique string? A. Yes, exactly. Q. (Configuration options part #3) # smsbox port to be listening on smsbox-port = 13005 - must this value be the same as the send-sms-port value in the smsbox? A. Nopes. This smsbox-port is the port that the bearerbox or sqlbox listen on to connections from smsbox. send-sms-port is a different port. It is the port that smsbox listens on to http requests to receive messages.
[PATCH] RE: Error compiling MySQL support on RedHat 9 - SOLVED!
I came up for the same solution for the same problem. Great minds think alike, they say. Attached is a patch for configure.in to solve this problem. Can somebody patch configure.in for me and run autoconf? Unfortunately my autoconf gives me troubles (probably a RedHat thingy again), so I would appreciate it if configure and configure.in will be commited to CVS after that. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alejandro Guerrieri Sent: dinsdag 31 augustus 2004 17:24 To: [EMAIL PROTECTED] Subject: Re: Error compiling MySQL support on RedHat 9 - SOLVED! Yep, I agree it would be good if it's fixed. The sed method I've tried worked for me, it's just a little mod on one line of the script and it shouldn't break anything in other platforms. BTW, 1.3.2 and MySQL DLR are working like a charm on RH9. Regards, On Tue, 31 Aug 2004 10:14:12 +0100, James Coleman [EMAIL PROTECTED] wrote: Brilliant Alejandro! You and Stipe did all the work. Not me. mysql_config Usage: /usr/bin/mysql_config [OPTIONS] Options: --cflags[-I'/usr/include/mysql'] --libs [-L'/usr/lib/mysql' -lmysqlclient -lz -lcrypt -lnsl -lm] --socket[/var/lib/mysql/mysql.sock] --port [3306] --version [3.23.58] Hmmm. The configure for 1.2.1 works with this. I wonder does it use mysql_config ? yes. And lots of the code in configure looks the same ... but I boggle again. :( Possibly in 1.2.1 the mysql_config check fails but a later check sets up mysql libs and vars correctly ... urngh. I went through the configure script for 1.2.1 to try see what was happening and how it works there but it would take me more time that I don't have now. I think it would be good to fix this in the configure as I guess it happens at least on all redhat systems. James. On Fri, Aug 27, 2004 at 02:23:39AM +0200, Alejandro Guerrieri wrote: Hi list, I've finally managed to find the problem compiling MySQL support on RedHat 9. The error comes from the single quotes around the library path on mysql_config output. James, you were right on the nail!: SO ... ??? could it be the -L'/usr/lib/mysql' those single quotes? I've looked but nasty to find exactly where that is set in $LIBS :) It seems at least that version of mysql (RedHat RPMs: mysql-3.23.58-1.9 and mysql-devel-3.23.58-1.9) output libraries that way... ]$ mysql_config Usage: /usr/bin/mysql_config [OPTIONS] Options: --cflags[-I'/usr/include/mysql'] --libs [-L'/usr/lib/mysql' -lmysqlclient -lz -lcrypt -lnsl -lm] --socket[/var/lib/mysql/mysql.sock] --port [3306] --version [3.23.58] And more specifically: ]$ mysql_config --libs -L'/usr/lib/mysql' -lmysqlclient -lz -lcrypt -lnsl -lm Probably a silly status bug on mysql_config output. Fortunately, a very easy-to-solve one! Looking at configure.log, those buggers are there on -L'/usr/lib/mysql' configure:4459: checking for mysql_init in -lmysqlclient configure:4478: gcc -o nftest -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -I/usr/include/libxml2 -rdynam ic conftest.c -lmysqlclient -L'/usr/lib/mysql' -lmysqlclient -lz -lcrypt -lnsl -lm -lresolv -lnsl -lm -lpthread -L/usr/lib -lxml2 -lz -lm 15 /usr/bin/ld: cannot find -lmysqlclient collect2: ld returned 1 exit status The funny part is, if you run that line on the terminal, the shell mangles things somehow and it works, but from the sh script it causes trouble. So, what I did was to modify the configure script on line 4453: Before: MYSQL_LIBS=$($MYSQL_CONFIG --libs) After: MYSQL_LIBS=$($MYSQL_CONFIG --libs | sed 's/\x27//g') Very simple: I've run the output for mysql_config through sed and removed hex character 27 (the single quote character) globally. After that, it compiled like a charm! I also did the mod on configure.in and tried to run autoconf, but it complained about libobjs: ]$ autoconf configure.in:135: error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs LIBOBJS' If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. So I left the excercise for you autoconf gurus ;) Anyway, the change to make on configure.in is on line 798: Before: MYSQL_LIBS=$($MYSQL_CONFIG --libs) After: MYSQL_LIBS=$($MYSQL_CONFIG --libs | sed 's/\x27//g') (Sorry, I'm too lazy to make a diff just for this small mod ;) ) The mod could be applied harmlessly to any installation. If the single quotes are missing (as they should be!) sed won´t change anything and it will compile as always, so I suggest this (or at least an equivalent mod) could be applied to CVS to allow to us RedHat 9 Kannellers to compile MySQL support
FW: [PATCH] Automake conversion take 3, fixed
Sorry, forgot to copy the list. -Original Message- From: Rene Kluwen [mailto:[EMAIL PROTECTED] Sent: maandag 4 oktober 2004 20:14 To: Alexander Malysh Subject: RE: [PATCH] Automake conversion take 3, fixed I have not tried the patch. But working on the mysql_config --libs bug, I found that building configure from configure.in gives some major warnings and also some errors. So I hope this patch will fix it. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alexander Malysh Sent: maandag 4 oktober 2004 20:07 To: [EMAIL PROTECTED] Subject: Re: [PATCH] Automake conversion take 3, fixed Hi, anybody there with objections? if not I will start merging this week, so please speak now... Paul P Komkoff Jr wrote: My first 2 patches was busted. I somehow managed to mess with latest cvs commit, and that in part reverts it. I fixed it. http://stingr.net/l/merge/kannel-automake-cvt-02.patch.gz -- Thanks, Alex
Re: SMPP Enquire Link
You can set (if your SMSC supports it) transceiver-mode = true in your kannel.conf. This might possibly help. Try it. Rene Kluwen Chimit Michael Bildner wrote: I'm currently using Kannel to connect to an SMSC via SMPP 3.4. I've been perusing the log files created for the SMSC connections and it seems that the enquire_link PDU is sent twice. The first enquire_link PDU is sent, then a response comes back and a second later another enquire_link PDU is immediately sent out. Is this a desired effect? Thanks __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo
Re: Sending post sms
Information about how to do it is in the userguide. Other than that: Which programming language would you like an example in? PHP, ASP, C, C++, etc.? Rene Kluwen Chimit - Original Message - From: Balaji Prasad [EMAIL PROTECTED] To: devel@kannel.org Sent: Monday, January 17, 2005 1:03 PM Subject: Sending post sms Hi all, any one can please tell me how to use post method to sendsms, is there any example anywhere! Thanks in advance.
Re: Looking to open source software that uses gwlib
Because I know that gwlib serves more purposes than just Kannel: How about creating a seperate CVS tree for it and distribute it independantly? Just a thought. Rene Kluwen Chimit - Original Message - From: Paul Bagyenda [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, January 17, 2005 8:55 AM Subject: Looking to open source software that uses gwlib Hi, We've used kannel in a variety of settings and have even in the past posted changes to the list (incl. OMA OTA provisioning and a bunch of other changes). Some of the changes made it into the code, others are waiting. We have a product we've developed that we are looking to open source fairly shortly. It uses gwlib in part, but we also added some stuff (fairly benign, in the cfg.def file primarily). My question is: How best should be handle this. Should only the gwlib changes be contributed/incorporated to the kannel project itself? Should we put this new product under kannel.org control or should we create a related project that both groups can benefit from? The trouble is that this product deviates pretty hugely from kannel's core focus, so we are not sure it properly fits under the kannel umbrella. Whatever the choice we intend to fully acknowledge kannel's contribution. Please let me have your thoughts Thanks Paul. - P. A. Bagyenda Digital Solutions P.O.Box 23833 58 Bukoto Str. Kampala, UGANDA Tel: +256-41-540143 Mob: +256-75-507743 Web: http://www.dsmagic.com - This email and any files transmitted with it are confidential, and may also be legally privileged. If you are not the intended recipient, you may not review, use, copy, or distribute this message. If you receive this email in error, please notify the sender immediately by reply email and then delete this email.
RE: Hi
Q1) Write a .php, .asp or cgi script that writes the dlr into a database. Then, point dlr-url (in the sendsms request) to your script. Dont forget to include a unique ID in the dlr-url and also dont forget to urlencode the url when you pass it to sendsms.. Q2) Write a .php, .asp or cgi script that accepts the parameters as you want. Then -in the script- mangle the parameters such as Kannel (sendsms) accepts them. Rene Kluwen Chimit Hi All, I have two questions as below. I would appreciate someone helping me with correct inputs. I run Kannel on Redhat Linux 9. I am configuring Kannel to be used as a SMS gateway. I have configured one SMPP SMSC and couple of sendsms users. Kannel binds to the SMSC properly without any errors. I am sending an SMS through the HTTP interface sendsms.php and the message gets delivered to the handset. Q1) I want Kannel to receive the delivery receipt and write it into a MySQL table. For achieving this, kannel has to submit_sm with registered_delivery = 1. When I try to set msg-id-type to 1 or 2 or 3, there is no change in the behavior. How do I make Kannel receive the delivery receipt and write it into the mysql table? Q2) I am also configuring a HTTP gateway to which SMS has to be sent. The parameters of the http gateway are different from that expected by the sendsms.php. How do I synchronize both? regards ravi
RE: RAWTCP mode (AT modem on a TCP terminal server) -- patch updated
I didnt really review the patch itself (sorry).
But I think the idea is brilliant.
Rene Kluwen
Chimit
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Stipe Tolj
Sent: donderdag 15 september 2005 21:51
To: Stanislav Sinyagin
Cc: devel@kannel.org
Subject: Re: RAWTCP mode (AT modem on a TCP terminal server) -- patch
updated
Stanislav Sinyagin wrote:
Attached, please see the patch against current CVS HEAD.
Alexander Malysh's advices and comments are integrated.
I'm looking forward for this patch to be committed,
as we're about to start deploying first production systems.
Anreas: +1, Alex: +1, Stipe: +1, hence commited to CVS.
Thanks a lot.
Stipe
mailto:stolj_{at}_wapme-group.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
RE: [PATCH] mysql_real_escape_string() usage in gw/dlr_mysql.c
Stipe, list,
IMHO consuming DBPoolConns is not a bad thing. After all, that is why the
pool even exist. So consuming and producing sql connections is not so
expensive.
In your patch: Where exactly do you escpape the parameters to the sql
string? I couldnt find that so quick.
In most of the Chimit code, we use something like this:
Octstr *sql = octstr_sql_format(SELECT * from table where pk = '%s',
PrimaryKey);
The function octstr_sql_format is crafted so that before replacing the value
of PrimaryKey on the place that says %s in the format string, automatically
it is sql-escaped.
This way, you never have to worry about escaping stuff - everything goes
automagically. This a clean and generic solution that generates little
coding effort.
Rene Kluwen
Chimit
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Stipe Tolj
Sent: maandag 26 september 2005 19:10
To: Kannel Development list
Subject: [PATCH] mysql_real_escape_string() usage in gw/dlr_mysql.c
Hi list,
according to bug #258 we don't use the string character escaping functions
from
mysql client library to ensure the safety of the SQL statements.
Attached is a patch for gw/dlr_mysql.c:dlr_mysql_add() which uses a static
mysql_escaipe() that does this. Please review and vote for commitment. This
should be also extended to the other SQL statements, right?
Actually this is a bit glitchy, since we have to consume the DBPoolConn*
_before_ passing the strings to the mysql_real_escape_string() routine. It
expects a mysql connection in order to ensure that it gets the right
character
set encoding.
Anyone having a better way in doing this? I don't feel it's the smoothes
code for it, but it safes at least a sub-sequential consumption of
DBPoolConn's
while doing the string escaping.
Any improvments welcome.
Stipe
mailto:stolj_{at}_wapme-group.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
sqlbox update
Applied patch of Thomas Gottgens: The fields udhdata and msgdata are now created as blob and text fields. Also some fields of Kannel.conf are renamed to match CVS HEAD revision of the gateway module (mysql-username = username, etc.). Known issue that I will likely solve any of the following weeks: now, if the UDH does not end in NULL-Characters like 06050440AB but is in the form 06050440AB40AB sqlbox works as expected. The trailing 0's are stripped though and replaced by the first corresponding characters from the message text. text=Hello+worldudh=%06%05%04%40%AB%40%AB results in the SMS being 'Hello World' text=Hello+worldudh=%06%05%04%40%AB%00%00 results in the SMS being 'llo World' though. Rene Kluwen Chimit
SQLBox update
There has been a minor update in the sqlbox patch. This update fixes the bug in Kannel's configure where -on some platforms- configure exits and complains about not being able libmysqlclient. This has to do with mysql_config --libs outputting single quotes around the -L parameter. Cheers, Rene Kluwen Chimit
SQLBox Postgres update
It seems that the Postgres part was very outdated, compared to Kannel CVS head and didn't even compile. This is fixed now. Alex Kinch is testing at the moment. Cheers, Rene Kluwen Chimit
Re: SQLBox Postgres update
Do you want to implement kind of a patch-o-matic, like netfilter has?
Just an idea...
-- Rene
Rene Kluwen wrote:
It seems that the Postgres part was very outdated, compared to Kannel
CVS
head and didn't even compile.
This is fixed now. Alex Kinch is testing at the moment.
great...
What about strategies towards an add-on/mudule API in order to have manual
patching absolute?
Anyone having a good, practible approach here?
Stipe
mailto:stolj_{at}_wapme-group.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: adding keywords to config file without restarting server
With a little trick, it IS possible. Using the default keyword and writing
your own script that does the keyword routing.
Rene Kluwen
Chimit
Ehi Binitie wrote:
Hi Everyone ,
Is it possible to add keywords to config file without restarting
Ive read through the mailing list archives and saw a mention of an auto
reload feature .Was this ever implemented..?
no, it hasn't been yet implemented. Currently you'll have to restart
smsbox at
least to take effect on a new config.
Actually it would be great if we have a modularization towards DB support
for
this in order to set MO routing via DB entries/keywords.
Stipe
mailto:stolj_{at}_wapme-group.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
[Fwd: [Kannel 0000278]: cannot build kannel with mysql support]
This bug can be solved by applying the sqlbox patch. Whenever I can find my mantis login (meaning when I get back to my own computer) I will update this bug. Rene Kluwen Chimit Mensaje original Asunto: [Kannel 278]: cannot build kannel with mysql support De: [EMAIL PROTECTED] Fecha: Dom, 11 de Diciembre de 2005, 4:22 Para: -- The following NEW bug has been ADDED. === http://bugs.kannel.org/view_bug_page.php?f_id=278 === Reporter: eriks Handler: === Project:Kannel Bug ID: 278 Category: General Reproducibility:always Severity: feature Priority: normal Status: new === Date Submitted: 12-11-05 03:22 GMT Last Modified: 12-11-05 03:22 GMT === Summary:cannot build kannel with mysql support Description: DLR thereby becomes impossible ===
Re: [Fwd: [Kannel 0000278]: cannot build kannel with mysql support]
Rene Kluwen wrote:
This bug can be solved by applying the sqlbox patch.
??? how did you know that?,
Because I am smart :)...
And also because I always have a problem compiling mysql on a clean checkout.
Rene Kluwen
Chimit
I can see any particular log from the report
that
indicates what is going wrong here ;)
Stipe
mailto:stolj_{at}_wapme-group.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
[Fwd: Re: [Fwd: [Kannel 0000278]: cannot build kannel with mysql support]]
Mensaje original
Asunto: Re: [Fwd: [Kannel 278]: cannot build kannel with mysql
support] De: Rene Kluwen [EMAIL PROTECTED]
Fecha: Mar, 13 de Diciembre de 2005, 0:52
Para: Peter Christensen [EMAIL PROTECTED]
--
# CFLAGS=-I/usr/include/mysql ./configure --with-mysql
--with-mysql-dir=/usr
snip
Configuring DB support ...
checking whether to compile with MySQL support... searching
checking for mysql_config... /usr/bin/mysql_config
checking mysql version... 3.23.56
checking mysql libs... -L'/usr/lib/mysql' -lmysqlclient -lz -lcrypt -lnsl
-lm checking for mysql_init in -lmysqlclient... no
configure: error: Unable to find MySQL client libraries
Hi,
Personally I have to configure kannel with:
CFLAGS=-I/usr/include/mysql ./configure --with-mysql
--with-mysql-dir=/usr
to get the desired result. Have you tried that, Rene?
--
Peter Christensen
Stipe Tolj wrote:
Rene Kluwen wrote:
Rene Kluwen wrote:
This bug can be solved by applying the sqlbox patch.
??? how did you know that?,
Because I am smart :)...
And also because I always have a problem compiling mysql on a clean
checkout.
now, agree'ing to both ;)
What are the specific problems for compiling mysql support, can you
guys please profile bugs reports, so we have a track on this.
Thanks.
Stipe
mailto:stolj_{at}_wapme-group.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
I have a...
...working Clickatell http driver in development at the moment. If there is enough animo for this, I will post it as a patch; for possible inclusion in CVS. Rene Kluwen Chimit
RE: [Kannel 0000314]: RE: [Kannel 0000315]:
Is this whilst shutting down Wapbox? Or just when terminating a WAP Session? It seems these two bugs are related. About the wsp session: Possibly http_headers are already destroyed at some other point. Have you tried mutexing this member to avoid race conditions? -- Rene
I updated the sqlbox repository...
...with the latest sqlbox patch, so the patch will apply again without fuzzyness... Nothing has changed otherwise. Rene Kluwen Chimit
[RFC]: heartbeat_stop crashes
Can I have votes on this patch? Rene Kluwen Chimit -Original Message- From: Apache [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: zondag 12 maart 2006 21:58 Subject: [Kannel 320]: heartbeat_stop crashes The following NEW bug has been ADDED. === http://bugs.kannel.org/view_bug_page.php?f_id=320 === Reporter: rene Handler:rene === Project:Kannel Bug ID: 320 Category: General Reproducibility:sometimes Severity: tweak Priority: normal Status: assigned === Date Submitted: 03-12-06 20:58 GMT Last Modified: 03-12-06 20:58 GMT === Summary:heartbeat_stop crashes Description: If -for some reason- no heartbeat at all is activated (e.g. thread could not be created, etc.) then heartbeat_stop crashes on gwlist_extract_first(heartbeat /* == NULL */) ===
Clickatell http driver patch
Hi Alex, As you suggested, I agree that we better move this thread to the ML. I posted the patch to the users ML. I will attach it to this post again for your convenience. I will fix your points 1, 2 4. Probably before the end of this week. About the authentication: Clickatell does not send a username or password along. But I will see if it is possible to make a check on api_id. Besides that, also connect-allow-ip can be used. From what I have heard from the Clickatell techs, their callback HTTP farm connects from behind one single IP address. Cheers, Rene Kluwen Chimit --- alex - 03-14-06 19:31 GMT --- Hi Rene, I agree with you that we should support as much http interfaces as possible. As to you patch... It's to hard to comment on this patch in mantis. Please post it to ML and I will review it. At least now some comments: 1) please fix comments (they mention Brunet but your patch should support Clickatell ;)) 2) please kill commented blocks which are there due to copypaste from brunet /* e.g. XSER */ 3) I don't see what should prevent me to send your MO message instead of Clickatell server (not auth. for MO and DLR) 4) minor: please fix coding style (indents) Thanks, Alex clickatell_MO.patch Description: Binary data
FW: [Kannel 0000321]: Unable to stop read_from_box fn
Alex, I agree. Do you have a better option? Rene Kluwen Chimit --- alex - 03-14-06 20:29 GMT --- Hi Rene, your patch is more a hack as solution. -1 from me.
RE: Clickatell http driver patch
I just checked the Kannel http api sources. And the ssl parameters are not used at the moment. It shouldn't be too hard to implement. But I will leave it for another occasion. Let's first see if this patch gets accepted (or not). Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alexander Malysh Sent: dinsdag 14 maart 2006 21:14 To: devel@kannel.org Subject: Re: Clickatell http driver patch Hi again, Rene Kluwen schrieb: Hi Alex, As you suggested, I agree that we better move this thread to the ML. I posted the patch to the users ML. I will attach it to this post again for your convenience. I will fix your points 1, 2 4. Probably before the end of this week. About the authentication: Clickatell does not send a username or password along. But I will see if it is possible to make a check on api_id. Besides that, also connect-allow-ip can be used. From what I have heard from the Clickatell techs, their callback HTTP farm connects from behind one single IP address. not really good interface ;) (hint: ip spoofing) Their server should connect via https with username pass... Thanks, Alex Cheers, Rene Kluwen Chimit --- alex - 03-14-06 19:31 GMT --- Hi Rene, I agree with you that we should support as much http interfaces as possible. As to you patch... It's to hard to comment on this patch in mantis. Please post it to ML and I will review it. At least now some comments: 1) please fix comments (they mention Brunet but your patch should support Clickatell ;)) 2) please kill commented blocks which are there due to copypaste from brunet /* e.g. XSER */ 3) I don't see what should prevent me to send your MO message instead of Clickatell server (not auth. for MO and DLR) 4) minor: please fix coding style (indents) Thanks, Alex
RE: Clickatell http driver patch
Alex, I fixed your points 1, 2 4 with the latest patch attached. About point 3: https server support will be nice in the http smsc driver. This is true for ALL http drivers and is not just Clickatell related. So I consider this a seperate issue. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alexander Malysh Sent: dinsdag 14 maart 2006 21:14 To: devel@kannel.org Subject: Re: Clickatell http driver patch Hi again, Rene Kluwen schrieb: Hi Alex, As you suggested, I agree that we better move this thread to the ML. I posted the patch to the users ML. I will attach it to this post again for your convenience. I will fix your points 1, 2 4. Probably before the end of this week. About the authentication: Clickatell does not send a username or password along. But I will see if it is possible to make a check on api_id. Besides that, also connect-allow-ip can be used. From what I have heard from the Clickatell techs, their callback HTTP farm connects from behind one single IP address. not really good interface ;) (hint: ip spoofing) Their server should connect via https with username pass... Thanks, Alex Cheers, Rene Kluwen Chimit --- alex - 03-14-06 19:31 GMT --- Hi Rene, I agree with you that we should support as much http interfaces as possible. As to you patch... It's to hard to comment on this patch in mantis. Please post it to ML and I will review it. At least now some comments: 1) please fix comments (they mention Brunet but your patch should support Clickatell ;)) 2) please kill commented blocks which are there due to copypaste from brunet /* e.g. XSER */ 3) I don't see what should prevent me to send your MO message instead of Clickatell server (not auth. for MO and DLR) 4) minor: please fix coding style (indents) Thanks, Alex clickatell MO Revisited.patch Description: Binary data
RE: octstr_format panic
Hi Alex, Since you prefer discussions on the mailinglist, I will paste my comments below :). This is regarding bug #323. Please comment or commit :) -- Rene Yes, it does make a difference. I just made a reasoning mistake. It was not because of octstr_destroy, but: Apart from octstr_destroy() the octstr_format() function also does other things, like octstr_insert_data, octstr_truncate, etc. At least at one occurence, this hit me. From my logs: 2006-03-13 19:04:36 [1523] [1] PANIC: gwlib/octstr.c:1381: octstr_insert_data: Assertion `!ostr-immutable' failed. Rene Kluwen Chimit
[PATCH] smsc id
I atttached a little issue that came up in the Clickatell driver.
This patch sets the smsc_id in incoming messages.
Otherwise, they are unable to be routed (smsbox_list empty).
Rene Kluwen
Chimit
Index: gw/smsc/smsc_http.c
===
RCS file: /home/cvs/gateway/gw/smsc/smsc_http.c,v
retrieving revision 1.45
diff -u -r1.45 smsc_http.c
--- gw/smsc/smsc_http.c 17 Mar 2006 10:39:01 - 1.45
+++ gw/smsc/smsc_http.c 27 Mar 2006 21:40:33 -
@@ -669,6 +669,7 @@
momsg-sms.msgdata = octstr_duplicate(text);
momsg-sms.charset = octstr_duplicate(charset);
momsg-sms.binfo = octstr_duplicate(api_id);
+ momsg-sms.smsc_id = octstr_duplicate(conn-id);
if (octstr_len(udh) 0) {
momsg-sms.udhdata = octstr_duplicate(udh);
}Index: gw/smsc/smsc_http.c
===
RCS file: /home/cvs/gateway/gw/smsc/smsc_http.c,v
retrieving revision 1.45
diff -u -r1.45 smsc_http.c
--- gw/smsc/smsc_http.c 17 Mar 2006 10:39:01 - 1.45
+++ gw/smsc/smsc_http.c 27 Mar 2006 21:40:33 -
@@ -669,6 +669,7 @@
momsg-sms.msgdata = octstr_duplicate(text);
momsg-sms.charset = octstr_duplicate(charset);
momsg-sms.binfo = octstr_duplicate(api_id);
+ momsg-sms.smsc_id = octstr_duplicate(conn-id);
if (octstr_len(udh) 0) {
momsg-sms.udhdata = octstr_duplicate(udh);
}
ota_tokenize_bookmarks
I was looking at the file ota_prov.c.
When I sent an ota-bookmark to myself, on a Siemens C60, I get an SMS
message with garbage.
Has anybody experienced this as well? And better: Does anyone have a
solution for this?
Another reason to write this email is, when looking at line 487 506, the
octstr_append function
is called with octstr_duplicate as parameter.
When looking at the octstr_append fn (and further down into
octstr_insert()), I see no disposal of
that parameter. Shouldn't the octstr_duplicate function call in the second
parameter be removed??
Am I seeing things wrong here?
See the code below: I marked the havoc lines with comments.
/* name */
if (name != NULL) {
/* PARM with attributes */
octstr_append_from_hex(msg-sms.msgdata, 87);
/* NAME=PROXY, VALUE, inline string */
octstr_append_char(msg-sms.msgdata, WBXML_TOK_NAME_NAME);
octstr_append_char(msg-sms.msgdata, WBXML_TOK_VALUE);
octstr_append_char(msg-sms.msgdata, WBXML_TOK_STR_I);
octstr_append(msg-sms.msgdata, octstr_duplicate(name));
/* = MEMORY LEAK?? */
octstr_append_char(msg-sms.msgdata, WBXML_TOK_END_STR_I);
octstr_append_char(msg-sms.msgdata, WBXML_TOK_END);
}
/* URL */
if (url != NULL) {
/* PARM with attributes */
octstr_append_from_hex(msg-sms.msgdata, 87);
/* NAME=PROXY, VALUE, inline string */
octstr_append_char(msg-sms.msgdata, WBXML_TOK_NAME_URL);
octstr_append_char(msg-sms.msgdata, WBXML_TOK_VALUE);
octstr_append_char(msg-sms.msgdata, WBXML_TOK_STR_I);
octstr_append(msg-sms.msgdata, octstr_duplicate(url));
/* === MEMORY LEAK?? */
octstr_append_char(msg-sms.msgdata, WBXML_TOK_END_STR_I);
octstr_append_char(msg-sms.msgdata, WBXML_TOK_END);
}
RE: [PATCH] ota_tokenize_bookmarks
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Alexander Malysh
Sent: donderdag 6 april 2006 12:01
To: devel@kannel.org
Subject: Re: ota_tokenize_bookmarks
Hi Rene,
you are right about memleaks. Could you please provide patch?
Thanks,
Alex
Rene Kluwen schrieb:
I was looking at the file ota_prov.c.
When I sent an ota-bookmark to myself, on a Siemens C60, I get an SMS
message with garbage.
Has anybody experienced this as well? And better: Does anyone have a
solution for this?
Another reason to write this email is, when looking at line 487 506, the
octstr_append function
is called with octstr_duplicate as parameter.
When looking at the octstr_append fn (and further down into
octstr_insert()), I see no disposal of
that parameter. Shouldn't the octstr_duplicate function call in the second
parameter be removed??
Am I seeing things wrong here?
See the code below: I marked the havoc lines with comments.
/* name */
if (name != NULL) {
/* PARM with attributes */
octstr_append_from_hex(msg-sms.msgdata, 87);
/* NAME=PROXY, VALUE, inline string */
octstr_append_char(msg-sms.msgdata, WBXML_TOK_NAME_NAME);
octstr_append_char(msg-sms.msgdata, WBXML_TOK_VALUE);
octstr_append_char(msg-sms.msgdata, WBXML_TOK_STR_I);
octstr_append(msg-sms.msgdata, octstr_duplicate(name));
/* = MEMORY LEAK?? */
octstr_append_char(msg-sms.msgdata, WBXML_TOK_END_STR_I);
octstr_append_char(msg-sms.msgdata, WBXML_TOK_END);
}
/* URL */
if (url != NULL) {
/* PARM with attributes */
octstr_append_from_hex(msg-sms.msgdata, 87);
/* NAME=PROXY, VALUE, inline string */
octstr_append_char(msg-sms.msgdata, WBXML_TOK_NAME_URL);
octstr_append_char(msg-sms.msgdata, WBXML_TOK_VALUE);
octstr_append_char(msg-sms.msgdata, WBXML_TOK_STR_I);
octstr_append(msg-sms.msgdata, octstr_duplicate(url));
/* === MEMORY LEAK?? */
octstr_append_char(msg-sms.msgdata, WBXML_TOK_END_STR_I);
octstr_append_char(msg-sms.msgdata, WBXML_TOK_END);
}
ota_leak.patch
Description: Binary data
RE: Please be gentle...
I think there IS a roadmap with an upcoming new stable version. Stipe and Alexander might be able to tell a little bit about it. I know they are working hard to achieve the goal (the goal being the new release). AFAIK, it is a matter of a few pending bugs that are supposed to be solved before the release can be called stable. Personally I think Kannel is not yet an untamed beast of code by far. There is strict coding guidelines that are being actively enforced. I see some things on the back sides as well, but will respect the subject ;) Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Josh McAllister Sent: dinsdag 25 april 2006 23:04 To: devel@kannel.org Subject: Please be gentle... I know this kind of post in a dev list can be perceived as a war cry, I hope that is not the case here. That being said, I'm curious when a new release may be coming. A year and half of patches, with no official release seems rather excessive. I know at this point many have probably been forced to roll their own release based on 1.4.0 and a myriad of patches to suit each persons own purposes, I'm getting up there myself. I fear that if I keep going I'm going to have to go through a whole battery of testing myself after upgrading to any official release... I'd like to see this situation not snowball out of control. Or is that the problem, has it already become an untamed beast of code? Ok, flak jacket is on. Let me have it. =) Josh McAllister
RE: [PATCH] SQLBOX Delivery Reports Insert
Maybe we should better introduce another type, besides MT MO (e.g. DR for Delivery Report)? This way delivery reports can be filtered out with ease by constructing a proper SQL statement. The reasons that I would prefer this way are: 1. Backwards compatibility, and 2. Some people are counting on delivery reports being inserted. They are not in all cases completely unneccesary. Another idea is to make this behaviour configurable. Comments? Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mi Reflejo Sent: zaterdag 13 mei 2006 14:24 To: devel@kannel.org Subject: [PATCH] SQLBOX Delivery Reports Insert *gw/sqlbox.c -Removed unnecessary INSERT's into database. bearerbox_to_smsbox shouldn't INSERT delivery reports as type MO. condition added to discard delivery reports.
RE: [PATCH] SQLBOX Port Bug
Very useful feature patch for what was in fact a bug in sqlbox. Will apply it at the same time as your other patch. Rene Kluwen Chimit -Original Message- From: Mi Reflejo [mailto:[EMAIL PROTECTED] Sent: maandag 29 mei 2006 10:02 To: devel@kannel.org; Rene Kluwen Subject: [PATCH] SQLBOX Port Bug SQLbox is not reading smsbox-port. It is hardcoded to 13005. There is the patch for that issue. M.
RE: [PATCH] SQLBOX Port Bug
Patch applied. -Original Message- From: Mi Reflejo [mailto:[EMAIL PROTECTED] Sent: maandag 29 mei 2006 10:02 To: devel@kannel.org; Rene Kluwen Subject: [PATCH] SQLBOX Port Bug SQLbox is not reading smsbox-port. It is hardcoded to 13005. There is the patch for that issue. M.
RE: sqlbox mysql re-connection (question)
I have been looking into the sources a little bit. But I cannot seem to find the spot where bearerbox reconnects to the MySQL daemon. I figure dbpool_check() should be called somewhere. Of course, I can just put a call to that function somewhere in sqlbox. But I would like to follow a little bit the same way as it is done elsewhere in Kannel. Rene Kluwen Chimit
RE: sqlbox mysql re-connection (question)
Thanks, Martin for your insight. First, looking at dbpool_conn_consume, I see a bug. In the while loop at line 216, the stop criterium is pc == NULL. Next, on line 286, a return (pc-conn != NULL ? pc : NULL) is done. This segfaults when the while loop hits the stop criterium in stead of being exit with break. Note that this doesn't happen in real because the p-pool list has at least one producer so if the list is empty, gwlist_consume waits until somebody produces a connection again. Nonetheless, my real question is: Before inserting or selecting something into or from the sql database, a dbpool_conn_consume is done. This should ensure, I always have a working connection, according to what you just said. So why doesn't it work? Rene Kluwen Chimit -Original Message- From: Mi Reflejo [mailto:[EMAIL PROTECTED] Sent: zondag 4 juni 2006 0:09 To: Rene Kluwen Cc: devel@kannel.org Subject: Re: sqlbox mysql re-connection (question) Actually dbpool_check is not used :). Lets asume that we are using mySQL. Before each query, dbpool_conn_consume is called. dbpool_conn_consume call the function: p-db_ops-check(pc-conn) (declaration: p-db_ops = mysql_ops; and .check = mysql_check_conn,) Check function does a mysql_ping and returns 0 or -1. If the connection is not active dbpool_conn_consume restarts the connection and checks again, while the connection is down. Hope it helps. Martin On 6/3/06, Rene Kluwen [EMAIL PROTECTED] wrote: I have been looking into the sources a little bit. But I cannot seem to find the spot where bearerbox reconnects to the MySQL daemon. I figure dbpool_check() should be called somewhere. Of course, I can just put a call to that function somewhere in sqlbox. But I would like to follow a little bit the same way as it is done elsewhere in Kannel. Rene Kluwen Chimit
RE: [PATCH] config definition file hooking (for external modules), ie. sqlbox, mbuni, etc.
-1 from me.
Reason 1:
Does this mean add-ons need to temporarily use an interim API and switch to
another API when it becomes available?
Reason 2:
mBuni, sqlbox require patches to the Kannel sources either way.
It doesn't matter if such patches also patch cfg.def or not.
Rene Kluwen
Chimit
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Stipe Tolj
Sent: zondag 11 juni 2006 19:21
To: Stipe Tolj
Cc: Kannel Development list
Subject: Re: [PATCH] config definition file hooking (for external
modules),ie. sqlbox, mbuni, etc.
Stipe Tolj wrote:
Hi list,
now, as Kannel maintains its own way of knowing what config directives
are allowed in group sections, this is a problem if external modules,
ie. Rene's sqlbox or Paul's Mbuni need to use the same gwlib/cfg.[ch]
thingies.
I tried to introduce a generic hooking mechanism for the 2 functions
is_allowed_in_group() and is_single_group() that use the #include
cfg.def for the core.
Now extenal modules can use cfg_add_hooks(void *a, void *b) to offer
their own version of these 2 routines and hence #include
foobar-cfg.def in their own code space.
The hooks are appended to a list and a wrapper loops arround the
functiokns in the lists to get a boolean value.
I know that this is not the most elegant way. Alex suggested using
dlopne() and dlsym(), which are of course a better approach, but still
we need to concatenate the defined groups and I had no idea how to do.
Please review and vote.
no objectsion from the others?...
I'm going to commit this to cvs, even while Alex means there are more
elegant
ways to solve this. I agree. When using a cleaner API for add-on boxes this
should go away, but until then it shows-up to be usable and hence considered
as
add-on (non behaviour change) commit.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
RE: [PATCH] allow multiline in config
+0 from me.
I don't have any objections to this particular patch.
But shouldn't we wait with new features until at least we have a new stable
version?
I think that has priority by now.
Rene Kluwen
Chimit
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Stipe Tolj
Sent: zondag 11 juni 2006 19:19
To: Alexander Malysh
Cc: devel@kannel.org
Subject: Re: [PATCH] allow multiline in config
Alexander Malysh wrote:
Hi,
please find attached patch that allows multilines in bash styli in the
config file. E.g.:
option = very long \
jsdgfjshf
in order to have \ at the end:
option = not long \\
Comments and votes please.
since this can be considered an feature add-on and no behaviour change, I'm
definetly +1 on this and would go with a commit today.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
RE: [PATCH] (sqlbox) sqlbox.patch
Patch committed to CVS. @Martin: Did you also change configure.in? Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mi Reflejo Sent: woensdag 14 juni 2006 0:08 To: devel@kannel.org Subject: [PATCH] (sqlbox) sqlbox.patch New sqlbox.patch for sqlbox module according to the last gateway update. Regards, Martín Conte.
RE: [PATCH] config definition file hooking (for external modules), ie. sqlbox, mbuni, etc.
Yes, you convinced me because of 2 reasons:
1. Provided that the API is not going to change when using dlopen() c.s.
and
2. Your API doesn't stop anybody from patching cfg.def either way ;)
(but I will be good :P)
Rene Kluwen
Chimit
-Original Message-
From: Stipe Tolj [mailto:[EMAIL PROTECTED]
Sent: woensdag 14 juni 2006 1:02
To: Rene Kluwen
Cc: Kannel Development list
Subject: Re: [PATCH] config definition file hooking (for external
modules),ie. sqlbox, mbuni, etc.
Rene Kluwen wrote:
-1 from me.
Reason 1:
Does this mean add-ons need to temporarily use an interim API and switch
to
another API when it becomes available?
Reason 2:
mBuni, sqlbox require patches to the Kannel sources either way.
It doesn't matter if such patches also patch cfg.def or not.
Rene Kluwen
Chimit
Hi Rene,
could I convince/argue you to a +0 at least? I'd like to commit this.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
RE: [PATCH] (sqlbox) sqlbox.patch
Some comments:
- configure SHOULD be included in the patch. Because nobody uses autoconf
to build their configure itself.
This is way different from .o files... because they are not included in the
repository.
- Yes, a seperate build tree for sqlbox might be cleaner. But we can only do
that if we work towards an unpatched Kannel that we can build against.
Meaning all patches that are in sqlbox.patch should go in CVS *or* sqlbox
should work around it in another way (e.g. in the case of cfg.def).
- The quotes issue is indeed a matter of Kannel and not of sqlbox. Yes, it
should be included in Kannel CVS.
Stipe: Try building plain Kannel (without sqlbox patch) with MySQL support
on the kannel.org host.
You will notice that it won't want to 'make'.
- The bearerbox-is-sqlbox directive is to let smsbox know that it should
connect to the sqlbox-port in stead of the bearerbox-port.
That is all there is to it.
- Maybe you should post the source codes of your smppbox here so we can all
see how you did it ;)
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Stipe Tolj
Sent: woensdag 14 juni 2006 0:56
To: Mi Reflejo
Cc: devel@kannel.org
Subject: Re: [PATCH] (sqlbox) sqlbox.patch
Mi Reflejo wrote:
New sqlbox.patch for sqlbox module according to the last gateway update.
Hi Martin,
thanks a lot for the submission. We appritiate your work on Kannel, and I
have
to admit that this is a good way to go...
Now, some critics anyway (even while Rene is more in charge for sqlbox ;)
* Please don't include configure itself in the patchset. It's generated
code
and hence, only configure.in belongs to the patchset. (It's like if we would
add
.o files to the CVS ;)
* The Makefile.in change is necessary to let Kannel core build sqlbox. This
can
be moved out of Kannel core in order to allow sqlbox (as own add-on module)
to
build itself again Kannel core (gwlib, gw) libs... I could forward you my
add-on
sceleton configure.in and Makefile.in to use for such purposes. You could
go
then and addopt it for sqlbox?
* Why is
diff -u -r1.166 configure.in
--- configure.in.orig 2006-06-13 15:27:52.0 -0600
+++ configure.in2006-06-13 15:27:15.0 -0600
@@ -936,14 +936,14 @@
dnl mysql-4.x style
MYSQL_LIBS=
if $MYSQL_CONFIG --libs_r /dev/null ; then
-MYSQL_LIBS=`$MYSQL_CONFIG --libs_r`
+MYSQL_LIBS=`$MYSQL_CONFIG --libs_r | sed -e s/\x27//g`
AC_MSG_CHECKING([mysql reentrant libs])
AC_MSG_RESULT([$MYSQL_LIBS])
AC_CHECK_LIB(mysqlclient_r, mysql_init, [ LIBS=$LIBS
$MYSQL_LIBS ],
[ MYSQL_LIBS= ], [ $MYSQL_LIBS ])
fi
if test -z $MYSQL_LIBS ; then
-MYSQL_LIBS=`$MYSQL_CONFIG --libs`
+MYSQL_LIBS=`$MYSQL_CONFIG --libs | sed -e s/\x27//g`
AC_MSG_CHECKING([mysql libs])
AC_MSG_RESULT([$MYSQL_LIBS])
AC_CHECK_LIB(mysqlclient, mysql_init, [ LIBS=$LIBS
$MYSQL_LIBS ],
necessary? Was this the issue with the ' signs?
If yes, this is of general scope and should go to gateway core itself.
* Why is config directive 'bearerbox-is-sqlbox' necessary for smsbox.c? I
don't
see a usage of the added int bearerbox_is_sqlbox in the smsbox.c patchset?
Does this mean sqlbox acts towards a patched smsbox like a bearerbox? Like
this:
user -HTTP- smsbox - sqlbox - bearerbox
?
* sqlbox should have it's own module gwlib/sqlbox-cfg.def and call the
cfg_add_hooks() routine I proposed to load the semantic checks for the new
config group.
Hope I wasn't to critic ;)... actually I like the sqlbox itself, but would
suggest Rene and you to mangle it the way I used for smppbox, where the
module
should be as much isolated from patching the core as possible. In the end I
came
up with the single (still to vote) patch for the cfg_add_hook() patch for
gwlib/cfg.[ch], and everything else would be in foobar module dir itself
works perfectly and smooth.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
RE: [PATCH] (sqlbox) sqlbox.patch
Alex, this is why Kannel needs you :)... Agreeing here. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alexander Malysh Sent: woensdag 14 juni 2006 17:37 To: devel@kannel.org Subject: Re: [PATCH] (sqlbox) sqlbox.patch Hi, why not simple define port in smsbox group always. so it would be possible: a) easier split bearerbox smsbox on different hosts w/o a need to define core group; b) tell smsbox to connect to any port also to sqlbox Anyway we have bearerbox-host config variable already in place, so just add bearerbox-port to smsbox group. That's it... Thanks, Alex Mi Reflejo schrieb: Hi Stipe, On 6/14/06, Stipe Tolj [EMAIL PROTECTED] wrote: that's a problem indeed. AFAIU the smsbox connects to the sqlbox rather then the bearerbox port. So sqlbox acts (from the view of smsbox) as bearerbox. Ok, that's why you guys need to seperate and add the config. But I think you should use a different .conf file for sqlbox, where the normal bearerbox port is set addequate to reflect the sqlbox(bearerbox)-port. This is a benefit, since it doesn't require to patch smsbox at all. Right? So, using 2 configs with core groups different for bearerbox port would solve the smsbox patching need. I don't see how a different config file *only* for sqlbox will solve anything since smsbox is who needs bearerbox port to connect. If we use a different .conf file *only* for sqlbox, smsbox would still connecting to original bearerbox-port. If we take this way, maybe a very ugly solution is to start smsbox and sqlbox with one config file and bearerbox with other but i don't like this way. M
RE: [PATCH] (sqlbox) sqlbox.patch
Okay... here's my 2 cts...
I disagree with you, Stipe.
smsbox needs to connect to the/a bearerbox. So the bearerbox-port should be
a configuration parameter of smsbox.
I will give you some logic:
1. smsbox connects to the tuple (bearerbox-host:bearerbox-port)
2. bearerbox-host is a configuration parameter of smsbox
3. ergo = bearerbox-port should be as well
The core group is designed to serve bearerbox.
A way-out-of-line argument for this is the use of smsbox for something
completely different than connecting to the bearerbox.
I leave possible uses to the creativity of the reader.
smsbox -in this light- is a stand alone application. Not related to
bearerbox at all.
Conclusion:
Both in the perspective of the user as well as in an architectural view,
group = smsbox might contain a bearerbox-port value.
Okay... so far the logic... I am self-respecting enough to come up with a
possible solution.
How about we inherit bearerbox-port from group = core BUT can be overridden
by the same entry in group = smsbox.
So the core section is only used if the same parameter in smsbox is omitted.
This way, we also stay downward compatible. And everybody will be happy!
Comments?
Maybe I can raving too far here. But we can even make this a general rule.
Taking mutual parameters in group = core when not found in group = smsbox,
wapbox, etc.
I actually do this in other software.
Rene Kluwen
Chimit
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Stipe Tolj
Sent: donderdag 15 juni 2006 2:33
To: Mi Reflejo
Cc: devel@kannel.org
Subject: Re: [PATCH] (sqlbox) sqlbox.patch
Mi Reflejo wrote:
Good one, Alex
Adding bearerbox-port to smsbox group should be a good solution.
I'll follow that way.
nop, I'm -0 on this... see my response on the other mail for argues.
Alex argues that smsbox would be runnable without core group... now, that
doesn't make sense in the current architecture. smsbox can't be running
without
bearerbox. It's a I hook into an upstream box-box and hence needs to have
a
connection to bearerbox. And that's why a core group is always semantically
necessary.
_If_ the smsbox could run without bearerbox, meaning you would launch it,
and on
the HTTP application layer side it could do things without having at the
operational time a link to bearerbox, then the approach would make sense.
But
that's not the case.
I recall again the 1-to-N architecture we have here for
bearerbox(1)-smsbox(N)
connections.
Stipe, I'm waiting for your sceleton build environment.
yep, preparing we're in WorldCup feaver... so things need more time ;)
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
RE: [PATCH] (sqlbox) gw/sqlbox_pgsql.c
Patch is VERY MUCH appreciated and committed to the sqlbox CVS. I will be honest now and admit that you saved my face due to the Postgres driver being broken all this time. Also it seems that Latin America hides some very talentfull and helpfull Kannel programmers :) Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Humberto Figuera Sent: dinsdag 20 juni 2006 20:11 To: devel@kannel.org Subject: [PATCH] (sqlbox) gw/sqlbox_pgsql.c Hi, I hope the list can appreciate it and it to be committed to CVS ;p -- Humberto Figuera - Using Linux 2.6.16 Usuario GNU/Linux 369709 Caracas - Venezuela GPG Key Fingerprint = 5AAC DF0C 00F4 2834 28BA 37AD 3364 01D1 74CA 0603
RE: resend_try and sms_resend_frequency in splitted msgs
Won't this block sending of other SMS messages as well? Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mi Reflejo Sent: woensdag 21 juni 2006 16:14 To: Alexander Malysh Cc: devel@kannel.org Subject: Re: resend_try and sms_resend_frequency in splitted msgs Yes, agree. What about check max tries from handle_split() and then resend. Please check attached patch M On 6/21/06, Alexander Malysh [EMAIL PROTECTED] wrote: Hi Martin, unfortunately this patch will not work as expected and therefore -1 from me. With this change you put part of the message into the global queue where it will be retransmitted and also rerouted again. So if you have at least 2 equal SMSCs (egal in kannel config but not the same SMSC) here is the 50/50 possibility that this part will be routed via different SMSC and the whole message will be discarded at handset because of this. The thing with splitted messages is that they must go via the same SMSC. Thanks, Alex P.S. This bug known to me for at least 2 month but didn't find elegant solution yet. The easiest solution would be to just remove resend code if smsc active but it would cause more expenses because the whole message (all parts of the message) will be resend. Mi Reflejo schrieb: When a msg is splitted and fails, handle_split() is called and every sms_resend_retry conditions are ignored so msgs are retryed infinite times. I'm attaching a patch to discuss. I don't know why handle_split() is calling smscconn_send() and is not putting msgs in outgoing_sms queue. My patch put msg in outgoing_sms and check for resend_try before. It's working for me. Any comment? Martín.
RE: sms_dict problem
At this moment I am a little bit short in time. But probably you are looking at a bug. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of francesco emmi Sent: donderdag 22 juni 2006 19:29 To: kannel devel Subject: sms_dict problem Hi list, I've start using sqlbox just now with latest cvs kannel version and I've found a strange behavior in the store file mechanism. Usually, without using sqlbox, when you send an sms with dlrmask=31 three sms are stored into sms_dict. The First is with sms_type=mt_push, the second with sms_type=report_mo (it's ack from operator) and the third with sms_type=report_mo (when we get delivery notification from operator). The first sms is removed from sms_dict when receiving ack type 8 and bb_smsconn_sent is called. The other two are removed, as I've seen throw code, when smsbox has received their own dlr messages from bearerbox, has generated their own acks (I mean msg with type=ack) and has forwarded them to bearerbox. Finally is called store_save_ack and messages are removed from sms_dict. Oknow the question. When using sqlbox the last two messages remain in sms_dict and are never removed. This is because no ack is received by bearerbox neither from smsbox nor from sqlbox. Could be my fault, maybe due a misconfiguration...or is it a bug? I've inserted sms into sqlbox with this query: INSERT INTO send_sms set momt = 'MT', sender = 'mysql', receiver = '34899', msgdata = 'test0', sms_type = 2, dlr_mask = 31; Hope that in spite of my bad english, I was able to point out the question! Thanks in advance Francesco -- Francesco Emmi A-Tono Largo Paisiello 5 - 95124 Catania Tel.: (+39) 095 7365312 http: www.a-tono.com Information in this email is confidential and may be privileged. It is intended for the addresses only. If you have received it in error, please notify the sender immediately and delete it from your system. You should not otherwise copy it, retransmit it or use or disclose its content to anyone. Thank you for your co-operation.
RE: wappush on CDMA
How can I get this patch ? Sorry... I used wrong English. I should have said: The patch is available _upon_ request (to me). But it should be clear :)... I will send it to you seperately. CDMA SAR really is on another level (SMSC level). But this patch does provide the SAR headers for the SMSC in optional parameters. Rene Kluwen Chimit -Original Message- From: Alex Antropoff [mailto:[EMAIL PROTECTED] Sent: donderdag 13 juli 2006 9:31 To: devel@kannel.org Subject: Re: wappush on CDMA On Wed, Jul 12, 2006 at 07:53:43PM +0200, Rene Kluwen wrote: RK Chimit has a patch for Wap Push on CDMA networks that consists of sending RK data_sm pdu's in stead of submit_sm pdu's to the SMPP server. RK RK It is available at no cost on request. RK RK Rene Kluwen RK Chimit How can I get this patch ? What's about splitting wap push messages using CDMA SAR ? -- Regards, Alex Antropoff
RE: SMSbox CRASH: PANIC: gwlib/octstr.c:2458 Assertion `ostr-data ==NULL'
Is this reproducable? Your smsc says Clickatell. Is this an SMPP connetion or the HTTP driver? Rene Kluwen Chimit -Original Message- From: Vincent CHAVANIS [mailto:[EMAIL PROTECTED] Sent: maandag 17 juli 2006 14:00 To: devel@kannel.org Subject: SMSbox CRASH: PANIC: gwlib/octstr.c:2458 Assertion `ostr-data ==NULL' FYI, Got new crash with smsbox... http://bugs.kannel.org/view.php?id=357 357: SMSbox CRASH: PANIC: gwlib/octstr.c:2458: seems_valid_real: Assertion `ostr-data == NULL' failed 2006-07-17 10:39:53.238 [2270] [4] INFO: Starting delivery report CLICKATELL-9 from TELEMAQUE 2006-07-17 10:39:53.239 [2270] [8] PANIC: gwlib/octstr.c:2458: seems_valid_real: Assertion `ostr-data == NULL' failed. (Called from gwlib/octstr.c:337:octstr_len.) 2006-07-17 10:39:53.276 [2270] [8] PANIC: /usr/local/bin/smsbox-1.4.1_x86_64(gw_panic+0x19a) [0x44023a] 2006-07-17 10:39:53.276 [2270] [8] PANIC: /usr/local/bin/smsbox-1.4.1_x86_64 [0x441755] 2006-07-17 10:39:53.276 [2270] [8] PANIC: /usr/local/bin/smsbox-1.4.1_x86_64(octstr_hash_key+0x5c) [0x444d8c] 2006-07-17 10:39:53.276 [2270] [8] PANIC: /usr/local/bin/smsbox-1.4.1_x86_64(dict_get+0x2c) [0x434bdc] 2006-07-17 10:39:53.276 [2270] [8] PANIC: /usr/local/bin/smsbox-1.4.1_x86_64 [0x439433] 2006-07-17 10:39:53.276 [2270] [8] PANIC: /usr/local/bin/smsbox-1.4.1_x86_64 [0x4357e7] 2006-07-17 10:39:53.276 [2270] [8] PANIC: /usr/local/bin/smsbox-1.4.1_x86_64 [0x436b05] 2006-07-17 10:39:53.276 [2270] [8] PANIC: /lib64/libpthread.so.0 [0x3f05406337] 2006-07-17 10:39:53.276 [2270] [8] PANIC: /lib64/libc.so.6(__clone+0x6d) [0x3f01acc38d] #) addr2line -e /usr/local/bin/smsbox-1.4.1_x86_64 0x44023a 0x441755 0x444d8c 0x434bdc 0x439433 0x4357e7 0x436b05 gwlib/log.c:552 gwlib/octstr.c:2470 gwlib/octstr.c:2431 gwlib/dict.c:294 gwlib/http.c:851 gwlib/fdset.c:349 gwlib/gwthread-pthread.c:135 -- Telemaque - NICE - (FR) Service Technique - Developpement http://www.telemaque.fr/ [EMAIL PROTECTED] Tel : +33 4 93 97 71 64 (fax 68)
RE: [PATCH] Service routing based on the account field
I agree with Stipe on this one (for a change ;]).
Why don't you just use smsc-id for what you want to accomplish?
Or otherwise: Please explain more.
Rene Kluwen
Chimit
-Original Message-
From: Stipe Tolj [mailto:[EMAIL PROTECTED]
Sent: zaterdag 22 juli 2006 14:14
To: Alejandro Guerrieri
Cc: devel@kannel.org
Subject: Re: [PATCH] Service routing based on the account field
Alejandro Guerrieri wrote:
I've noticed there were no way for Kannel to do service routing based
on the account field. This is specially handy when you use an HTTP
module to receive messages and the smsc gets encoded on the account
field, so you get a single smsc with different accounts depending on
the carrier.
I'm attaching a patch that adds two new sms-service parameters:
accepted-account and accepted-account-regex. Their functionality it's
exactly as their smsc counterparts (accepted-smsc and
accepted-smsc-regex) only that they do their logic on the account
field.
Hi Alejandro,
we have pretty hot temperatures currently in central europe, maybe it's
because
of that... but I didn't get the point for this one :)
This sounds to me like you use a HTTP SMSC module (maybe even own API?) and
then
use the passed 'account' field to 'represent' the smsc-id ?
So it seems to me that you have one inbound (MO) HTTP SMSC that passes you
MOs
from several operators, and provides you an 'account id' whole passing the
MO.
You put the MO into account and would like to route on smsbox level via
account.
Right?
If this is the case, then Kannel does not know about that multi-plexing of
operators behing the logical _ONE_ HTTP SMSC. I'm not quite sure if we
should
support this behaviour, since it does not corelate with generical
architecture
assuptions of Kannel.
I'm currently between -0 and +0 for this, until none of you guys can explain
why
this is the super-fancy-we-have-to-have-it-feature ;)
A GENERAL NOTE:
We, and I really think I can talk to others that contribute to Kannel and
mostly
to those that have cvs write permission and those that shortly may have (we
have
some candidates on the list ;) _appritiate_ any patch that people submit and
they feel it's a benefit to Kannel. So please don't get upsad, if we have
our
critisicm on it. We try to deal with all corners of the perspective. Some
contributers do not, they see their own need and usually have a more
subjective
way in seeing the need of a patch.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
RE: [RFC] SMPP: refusing DLRs that are not found in DLR storage?
I think this is an SMSC related issue.
Probably you will get different results based on different SMSC's.
Especially if it is not mentioned in any specs.
You are right about this being a client-side issue.
I know for once that -in my platforms- I have a single receive process
that receives incoming messages from all connected threads.
So in short: I don't think we will actually solve an issue if we start
doing things this way.
Rene Kluwen
Chimit
-Original Message-
From: Stipe Tolj [mailto:[EMAIL PROTECTED]
Sent: zondag 20 augustus 2006 2:13
To: Kannel Development list
Subject: [RFC] SMPP: refusing DLRs that are not found in DLR storage?
Hi list,
I wonder if we should/can change logic to refuse any deliver_sm PDU
containing a
DLR information when we don't find the associated DLR temp data in our
internal
storage?
This could be done by responding with deliver_sm_resp.command_status =
ESME_RX_R_APPN, which reads for me in the spec like I got the message,
but
refuse to accept it.
Anyone knows what behaviour after this a SMSC is expected to have? It's
not
defined directly via the spec. Will it discard the DLR, or retry, and if
yes,
how often?
The case issue is: connecting Kannel to a SMPP account, that is already
bound by
an other SMPP client application. The other application injects MTs, but
randomly Kannel get's DLR MOs for the MTs of the other application. Now,
we
could refuse those simply, either to force the SMSC to pick another RX
session
to deliver, or to drop.
I know that the design of this is already the wrong way to do it.
The client
should make sure that a RX session is always logically bound to the
application
layer that needs the DLR processing.
But just currious if this is a simple add-on feature and what SMSC will
do if we
reject unknown DLRs. Comments? Experimental results please?
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
RE: Release process
If someone ask for my opinion: I agree with this. Rene Kluwen Chimti -Original Message- From: Enver ALTIN [mailto:[EMAIL PROTECTED] Sent: zaterdag 21 oktober 2006 16:29 To: Stipe Tolj Cc: devel@kannel.org Subject: Release process On Sat, 2006-10-21 at 14:33 +0200, Stipe Tolj wrote: in the past we did always pre-version the development release tree and then either backport to the stable version tree or to a new stable version tree. Hence: 1.5.0 devel - a) 1.4.2 stable or b) 1.6.0 stable I'm a bit familiar with GNOME release cycle, and let me explain how that works. First of all, their release cycle is very predictable (a major release every 6 months), which is very good and we should do this IMO. Kannel CVS HEAD is 99.9% production state, I can say. Just like Kannel, odd numbers indicate development/beta versions. When they make a release 2.16.0 they branch it on CVS (modulename-2-16), and development continues on CVS HEAD. Old releases never get any new features, only translation updates and bug fixes, and they are committed to the modulename-2-16 branch in CVS. After 2.16.0 stable, any beta version will be numbered 2.17.x and bug-fix-only stable releases will still be named 2.16.x. So I believe we should stick to something like this, we should not add any new features to 1.4.x series and only backport bugfixes (new features will bring new bugs). Any beta release should be named 1.5.x, and when we're ready to make a stable release it should be named 1.6.x. To sum up what I'm saying, the differences of the proposal with the current release system are: * A predictable release cycle. * Branches on CVS for stable releases. * Development continues on HEAD, new features can be added. * Only bug fixes will be committed to last stable series. * Previously stable version (1.2.x) will be declared unmaintained (older than 2 release cycles). What do you think? -- .O. ..O Enver ALTIN | http://enveraltin.com/ OOO Software developer @ Parkyeri | http://www.parkyeri.com/
Re: [PATCH] (sqlbox-standalone) gw/sqlbox_pgsql.h
Stipe,
It would be for me if it were sqlbox.
The sqlbox patch is kind of outdated by sqlbox standalone.
Martin Conte maintains sqlbox standalone.
I suggest Martin takes over sqlbox maintanance? Just an idea. Since he is
a lot more active lately on the list and with patches.
Rene Kluwen
Chimit
Humberto Figuera wrote:
Hi,
There is a minor patch for gw/sqlbox_pgsql.h ;p
I hope the list can appreciate it and it to be committed to CVS ;p
thanks Humberto,
Rene, this one is for you I guess? ;)
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
req_feat patch
Nowadays, clickatell requires the req_feat parameter to enable to set the sender id or send binary SMS. This patch enables this. Votes? Rene Kluwen Chimit Index: gw/smsc/smsc_http.c === RCS file: /home/cvs/gateway/gw/smsc/smsc_http.c,v retrieving revision 1.54 diff -u -r1.54 smsc_http.c --- gw/smsc/smsc_http.c 15 Apr 2007 23:12:12 - 1.54 +++ gw/smsc/smsc_http.c 9 May 2007 13:15:49 - @@ -664,7 +664,7 @@ List *headers; /* form the basic URL */ -url = octstr_format(%S/sendmsg?to=%Efrom=%Eapi_id=%Euser=%Epassword=%E, +url = octstr_format(%S/sendmsg?to=%Efrom=%Eapi_id=%Euser=%Epassword=%Ereq_feat=25151, conndata-send_url, sms-sms.receiver, sms-sms.sender, conndata-system_id, conndata-username, conndata-password); /*
RE: req_feat patch
There is a possibility to extract the value, given the MSG struct and it's members. Will that be a better option? I can come up with a version that does that. But before spending time on that, I want to know if it is an acceptable solution. Rene Kluwen Chimit -Original Message- From: Vincent CHAVANIS [mailto:[EMAIL PROTECTED] Sent: woensdag 9 mei 2007 15:51 To: devel@kannel.org Subject: Re: req_feat patch -1 too for me as it. * Hardcoded is bad * If we need to implement this we should set it as a config value. Vincent -- Telemaque - 06560 SOPHIA-ANTIPOLIS - (FR) Service Technique/Reseau - NOC Developpement SMS/MMS/Kiosques http://www.telemaque.fr/ [EMAIL PROTECTED] Tel : +33 4 92 90 99 84 (fax 9142) - Original Message - From: Andreas mailto:[EMAIL PROTECTED] Fink To: Rene Kluwen mailto:[EMAIL PROTECTED] Cc: devel@kannel.org Sent: Wednesday, May 09, 2007 3:40 PM Subject: Re: req_feat patch Clickatel is not a reference. If they introduce nonstandard parameters, its their problem. There is no reason to add this to kannel in that case. And especially not something hardcoded like req_feat=25151 So my vote is -10 On 09.05.2007, at 15:25, Rene Kluwen wrote: Nowadays, clickatell requires the req_feat parameter to enable to set the sender id or send binary SMS. This patch enables this. Votes? Rene Kluwen Chimit req_feat.diff Andreas Fink Fink Consulting GmbH Global Networks Schweiz AG BebbiCell AG --- Tel: +41-61-330 Fax: +41-61-331 Mobile: +41-79-2457333 Address: Clarastrasse 3, 4058 Basel, Switzerland E-Mail: [EMAIL PROTECTED] www.finkconsulting.com www.global-networks.ch www.bebbicell.ch --- ICQ: 8239353 MSN: [EMAIL PROTECTED] AIM: smsrelay Skype: andreasfink Yahoo: finkconsulting SMS: +41792457333
RE: req_feat patch
Alex, Great idea! I haven't thought about that before. -- Rene -Original Message- From: Alexander Malysh [mailto:[EMAIL PROTECTED] Sent: donderdag 10 mei 2007 11:30 To: devel@kannel.org Subject: RE: req_feat patch Hi Rene, why not just define this parameter in send-url config variable? Rene Kluwen wrote: There is a possibility to extract the value, given the MSG struct and it's members. Will that be a better option? I can come up with a version that does that. But before spending time on that, I want to know if it is an acceptable solution. Rene Kluwen Chimit -Original Message- From: Vincent CHAVANIS [mailto:[EMAIL PROTECTED] Sent: woensdag 9 mei 2007 15:51 To: devel@kannel.org Subject: Re: req_feat patch -1 too for me as it. * Hardcoded is bad * If we need to implement this we should set it as a config value. Vincent -- Telemaque - 06560 SOPHIA-ANTIPOLIS - (FR) Service Technique/Reseau - NOC Developpement SMS/MMS/Kiosques http://www.telemaque.fr/ [EMAIL PROTECTED] Tel : +33 4 92 90 99 84 (fax 9142) - Original Message - From: Andreas mailto:[EMAIL PROTECTED] Fink To: Rene Kluwen mailto:[EMAIL PROTECTED] Cc: devel@kannel.org Sent: Wednesday, May 09, 2007 3:40 PM Subject: Re: req_feat patch Clickatel is not a reference. If they introduce nonstandard parameters, its their problem. There is no reason to add this to kannel in that case. And especially not something hardcoded like req_feat=25151 So my vote is -10 On 09.05.2007, at 15:25, Rene Kluwen wrote: Nowadays, clickatell requires the req_feat parameter to enable to set the sender id or send binary SMS. This patch enables this. Votes? Rene Kluwen Chimit req_feat.diff Andreas Fink Fink Consulting GmbH Global Networks Schweiz AG BebbiCell AG --- Tel: +41-61-330 Fax: +41-61-331 Mobile: +41-79-2457333 Address: Clarastrasse 3, 4058 Basel, Switzerland E-Mail: [EMAIL PROTECTED] www.finkconsulting.com www.global-networks.ch www.bebbicell.ch --- ICQ: 8239353 MSN: [EMAIL PROTECTED] AIM: smsrelay Skype: andreasfink Yahoo: finkconsulting SMS: +41792457333 -- Thanks, Alex
RE: req_feat patch
??? So which exactly is the _standard_ http? As far as I know, a sms-over-http RFC doesn't exist. Every provider implements their own protocol. To which http variant do you want clickatell to move? Anyhow... we discussed this before, back when the Clickatell API was admited to Kannel CVS. I don't feel like having the same discussion over again. I don't mind if this patch is not in CVS. It will just mean that the Clickatell http driver is partly broken. Rene Kluwen Chimit -Original Message- From: Andreas Fink [mailto:[EMAIL PROTECTED] Sent: woensdag 9 mei 2007 16:09 To: Rene Kluwen Subject: Re: req_feat patch The best thing is to go to clickatell and move them to do standard http. I dont know why there is even a specific http variant for it. On 09.05.2007, at 15:53, Rene Kluwen wrote: There is a possibility to extract the value, given the MSG struct and it's members. Will that be a better option? I can come up with a version that does that. But before spending time on that, I want to know if it is an acceptable solution. Rene Kluwen Chimit -Original Message- From: Vincent CHAVANIS [mailto:[EMAIL PROTECTED] Sent: woensdag 9 mei 2007 15:51 To: devel@kannel.org Subject: Re: req_feat patch -1 too for me as it. * Hardcoded is bad * If we need to implement this we should set it as a config value. Vincent -- Telemaque - 06560 SOPHIA-ANTIPOLIS - (FR) Service Technique/Reseau - NOC Developpement SMS/MMS/Kiosques http://www.telemaque.fr/ http://www.telemaque.fr/ mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] Tel : +33 4 92 90 99 84 (fax 9142) - Original Message - From: mailto:[EMAIL PROTECTED] Andreas Fink To: mailto:[EMAIL PROTECTED] Rene Kluwen Cc: mailto:devel@kannel.org devel@kannel.org Sent: Wednesday, May 09, 2007 3:40 PM Subject: Re: req_feat patch Clickatel is not a reference. If they introduce nonstandard parameters, its their problem. There is no reason to add this to kannel in that case. And especially not something hardcoded like req_feat=25151 So my vote is -10 On 09.05.2007, at 15:25, Rene Kluwen wrote: Nowadays, clickatell requires the req_feat parameter to enable to set the sender id or send binary SMS. This patch enables this. Votes? Rene Kluwen Chimit req_feat.diff Andreas Fink Fink Consulting GmbH Global Networks Schweiz AG BebbiCell AG --- Tel: +41-61-330 Fax: +41-61-331 Mobile: +41-79-2457333 Address: Clarastrasse 3, 4058 Basel, Switzerland E-Mail: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] www.finkconsulting.com www.global-networks.ch http://www.bebbicell www.bebbicell.ch --- ICQ: 8239353 MSN: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] AIM: smsrelay Skype: andreasfink Yahoo: finkconsulting SMS: +41792457333 Andreas Fink Fink Consulting GmbH Global Networks Schweiz AG BebbiCell AG --- Tel: +41-61-330 Fax: +41-61-331 Mobile: +41-79-2457333 Address: Clarastrasse 3, 4058 Basel, Switzerland E-Mail: [EMAIL PROTECTED] www.finkconsulting.com www.global-networks.ch www.bebbicell.ch --- ICQ: 8239353 MSN: [EMAIL PROTECTED] AIM: smsrelay Skype: andreasfink Yahoo: finkconsulting SMS: +41792457333
RE: req_feat patch
Feel free to contribute a patch :) Rene Kluwen Chimit -Original Message- From: Hillel [mailto:[EMAIL PROTECTED] Sent: woensdag 9 mei 2007 16:17 To: 'Rene Kluwen' Cc: Kannel Devel Subject: RE: req_feat patch Hi, Can we not rather have a generic HTTP interface that can be configured via config parameters for Clickatell or others? This will mean any provider offering a HTTP interface can offer HTTP via Kannel and so this generic interface will benefit all providers as they just need to specify their unique config parameters. Also should clickatell add new parameters you will just need to add a new config parameter and you will not need a new patch for each parameter. Rgds
Billing
I just answered an SMPPBox billing issue on the users list. I think billing shouldn't be an SMPPBox/SQLBox/SMSBox issue but rather something that handles Kannel itself (i.e. bearerbox). I think if we implement something like this, the community would benefit from that a lot. I mean, for every sms the client sends, there must be a payment... Or am I wrong? Let me know how you guys think about it. And to be more specific: How? == Rene
RE: Sqlbox and scheduled pushes
*smile* I am having a deja-vu. I sent this patch to Alex to begin with. Heh @Emmanuel: I agree with you and will suggest this on your behalf to the devel mailinglist. @devel: Alex suggested to make this even more configurable by putting the SELECT query in kannel.conf (/sqlbox.conf). However, I think this gives that much extra flexibility (and maintaining backward compatibility) that this quick patch can be incorporated already. It is useful for a lot of persons and it is just a quick patch. Todo: also patch the sql statements for other storage types. Rene Kluwen Chimit From: Emmanuel CHANSON [mailto:emmanuelchan...@gmail.com] Sent: woensdag 2 juni 2010 2:46 To: rene.klu...@chimit.nl Cc: Alejandro Guerrieri Subject: Re: Sqlbox and scheduled pushes Hello Rene I had sent my email to a wrong person... Emmanuel 2010/5/31 Emmanuel CHANSON emmanuelchan...@gmail.com Hello Rene, I would like to tell you about sqlbox and a requirement I have done on sqlbox source advised by Alex :) My need was to be able to send a scheduled batch using sqlbox. Alex told me first that sqlbox could not and I have to do this from the application but after a while he advised me to try to patch the source like this: in gw/sqlbox_mysql.h something like: SELECT sql_id, momt, sender, receiver, udhdata, \ msgdata, time, smsc_id, service, account, id, sms_type, mclass, mwi, coding, \ compress, validity, deferred, dlr_mask, dlr_url, pid, alt_dcs, rpi, \ charset, boxc_id, binfo, meta_data FROM %S WHERE time UNIX_TIMESTAMP(NOW()) LIMIT 0,1 That is what I have done and it seems to work like a charm :) So I wonder if this can not be proposed to others because it is something very usefull...for me at least.. Regards, Emmanuel -- Emmanuel CHANSON Emmanuel Mobile Nouvelle-Calédonie: +687.77.35.02 Mobile France: +33 (0) 6.68.03.89.56 @email : emmanuelchan...@gmail.com -- Emmanuel CHANSON Emmanuel Mobile Nouvelle-Calédonie: +687.77.35.02 Mobile France: +33 (0) 6.68.03.89.56 @email : emmanuelchan...@gmail.com
RE: Sqlbox and scheduled pushes
Do we really need a configuration parameter? Just a question. From: alejandro.guerri...@gmail.com [mailto:alejandro.guerri...@gmail.com] Sent: woensdag 2 juni 2010 10:07 To: Rene Kluwen; 'Emmanuel CHANSON' Cc: Kannel Devel Subject: Re: Sqlbox and scheduled pushes Hey, I've told Emmanuel already, I don't claim the copyright ;) I agree on adding it as is, we only need to add it to all db engines and put a configuration parameter to enable it. Regards, Alex BlackBerry de movistar, allí donde estés está tu oficin@ _ From: Rene Kluwen rene.klu...@chimit.nl Date: Wed, 2 Jun 2010 09:08:44 +0200 To: 'Emmanuel CHANSON'emmanuelchan...@gmail.com Cc: 'Alejandro Guerrieri'alejandro.guerri...@gmail.com; devel@kannel.org Subject: RE: Sqlbox and scheduled pushes *smile* I am having a deja-vu. I sent this patch to Alex to begin with. Heh @Emmanuel: I agree with you and will suggest this on your behalf to the devel mailinglist. @devel: Alex suggested to make this even more configurable by putting the SELECT query in kannel.conf (/sqlbox.conf). However, I think this gives that much extra flexibility (and maintaining backward compatibility) that this quick patch can be incorporated already. It is useful for a lot of persons and it is just a quick patch. Todo: also patch the sql statements for other storage types. Rene Kluwen Chimit From: Emmanuel CHANSON [mailto:emmanuelchan...@gmail.com] Sent: woensdag 2 juni 2010 2:46 To: rene.klu...@chimit.nl Cc: Alejandro Guerrieri Subject: Re: Sqlbox and scheduled pushes Hello Rene I had sent my email to a wrong person... Emmanuel 2010/5/31 Emmanuel CHANSON emmanuelchan...@gmail.com Hello Rene, I would like to tell you about sqlbox and a requirement I have done on sqlbox source advised by Alex :) My need was to be able to send a scheduled batch using sqlbox. Alex told me first that sqlbox could not and I have to do this from the application but after a while he advised me to try to patch the source like this: in gw/sqlbox_mysql.h something like: SELECT sql_id, momt, sender, receiver, udhdata, \ msgdata, time, smsc_id, service, account, id, sms_type, mclass, mwi, coding, \ compress, validity, deferred, dlr_mask, dlr_url, pid, alt_dcs, rpi, \ charset, boxc_id, binfo, meta_data FROM %S WHERE time UNIX_TIMESTAMP(NOW()) LIMIT 0,1 That is what I have done and it seems to work like a charm :) So I wonder if this can not be proposed to others because it is something very usefull...for me at least.. Regards, Emmanuel -- Emmanuel CHANSON Emmanuel Mobile Nouvelle-Calédonie: +687.77.35.02 Mobile France: +33 (0) 6.68.03.89.56 @email : emmanuelchan...@gmail.com -- Emmanuel CHANSON Emmanuel Mobile Nouvelle-Calédonie: +687.77.35.02 Mobile France: +33 (0) 6.68.03.89.56 @email : emmanuelchan...@gmail.com
RE: Sqlbox and scheduled pushes
You have a valid point there. Even two of them : ). Maybe, if there has to be an extra configuration parameter, your suggestion makes sense and better make the whole SQL query configurable. What do the others think about it? =+= Rene From: alejandro.guerri...@gmail.com [mailto:alejandro.guerri...@gmail.com] Sent: woensdag 2 juni 2010 10:50 To: Rene Kluwen; 'Emmanuel CHANSON' Cc: Kannel Devel Subject: Re: Sqlbox and scheduled pushes If you don't need the scheduling, the query would be heavier and would break backward-compatibility. BlackBerry de movistar, allí donde estés está tu oficin@ _ From: Rene Kluwen rene.klu...@chimit.nl Date: Wed, 2 Jun 2010 10:47:53 +0200 To: alejandro.guerri...@gmail.com; 'Emmanuel CHANSON'emmanuelchan...@gmail.com Cc: 'Kannel Devel'devel@kannel.org Subject: RE: Sqlbox and scheduled pushes Do we really need a configuration parameter? Just a question. From: alejandro.guerri...@gmail.com [mailto:alejandro.guerri...@gmail.com] Sent: woensdag 2 juni 2010 10:07 To: Rene Kluwen; 'Emmanuel CHANSON' Cc: Kannel Devel Subject: Re: Sqlbox and scheduled pushes Hey, I've told Emmanuel already, I don't claim the copyright ;) I agree on adding it as is, we only need to add it to all db engines and put a configuration parameter to enable it. Regards, Alex BlackBerry de movistar, allí donde estés está tu oficin@ _ From: Rene Kluwen rene.klu...@chimit.nl Date: Wed, 2 Jun 2010 09:08:44 +0200 To: 'Emmanuel CHANSON'emmanuelchan...@gmail.com Cc: 'Alejandro Guerrieri'alejandro.guerri...@gmail.com; devel@kannel.org Subject: RE: Sqlbox and scheduled pushes *smile* I am having a deja-vu. I sent this patch to Alex to begin with. Heh @Emmanuel: I agree with you and will suggest this on your behalf to the devel mailinglist. @devel: Alex suggested to make this even more configurable by putting the SELECT query in kannel.conf (/sqlbox.conf). However, I think this gives that much extra flexibility (and maintaining backward compatibility) that this quick patch can be incorporated already. It is useful for a lot of persons and it is just a quick patch. Todo: also patch the sql statements for other storage types. Rene Kluwen Chimit From: Emmanuel CHANSON [mailto:emmanuelchan...@gmail.com] Sent: woensdag 2 juni 2010 2:46 To: rene.klu...@chimit.nl Cc: Alejandro Guerrieri Subject: Re: Sqlbox and scheduled pushes Hello Rene I had sent my email to a wrong person... Emmanuel 2010/5/31 Emmanuel CHANSON emmanuelchan...@gmail.com Hello Rene, I would like to tell you about sqlbox and a requirement I have done on sqlbox source advised by Alex :) My need was to be able to send a scheduled batch using sqlbox. Alex told me first that sqlbox could not and I have to do this from the application but after a while he advised me to try to patch the source like this: in gw/sqlbox_mysql.h something like: SELECT sql_id, momt, sender, receiver, udhdata, \ msgdata, time, smsc_id, service, account, id, sms_type, mclass, mwi, coding, \ compress, validity, deferred, dlr_mask, dlr_url, pid, alt_dcs, rpi, \ charset, boxc_id, binfo, meta_data FROM %S WHERE time UNIX_TIMESTAMP(NOW()) LIMIT 0,1 That is what I have done and it seems to work like a charm :) So I wonder if this can not be proposed to others because it is something very usefull...for me at least.. Regards, Emmanuel -- Emmanuel CHANSON Emmanuel Mobile Nouvelle-Calédonie: +687.77.35.02 Mobile France: +33 (0) 6.68.03.89.56 @email : emmanuelchan...@gmail.com -- Emmanuel CHANSON Emmanuel Mobile Nouvelle-Calédonie: +687.77.35.02 Mobile France: +33 (0) 6.68.03.89.56 @email : emmanuelchan...@gmail.com
RE: smppbox
I see an excellent opportunity for you, Nikos, to prove your skills, writing documentation :) -Original Message- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: maandag 7 juni 2010 14:12 To: Rene Kluwen; Alexander Malysh Cc: devel@kannel.org Subject: Re: smppbox Dear Rene, Thanks a lot for this contribution. Upon succesful acceptance by kannel in the main svn, bear in mind that an additional component will be needed: a patch to kannel's User's guide. This is a requirement to every patch submitted to kannel. Can you take care of it? @Alex: This is a long awaited feature to bearerbox. It is also the second large contribution by Chimit. According to Rene it has been used in production for over a year without problems. I would like to see it in mainstream kannel. Is it feasible? My vote is +++1 BR, Nikos - Original Message - From: Rene Kluwen rene.klu...@chimit.nl To: us...@kannel.org Sent: Friday, May 07, 2010 11:56 PM Subject: smppbox Lectori Salutem, This email is about Chimit's smppbox. The rights to the smppbox code have been obtained by a third party, but fortunately there is some good news for the open source community. An early version of smppbox (smpp v.3.0) will now be donated back to the community. This version is by no means perfect and developers and investors are invited to contribute. All in the spirit of being an open-source community. Chimit already developed the successful sqlbox, which is now part of the main stream Kannel distribution, so if we all cooperate, this smppbox can go the same way. To get you started, here is a preliminary download: http://www.chimit.nl/kannel/smppbox.tar. Unfortunately, due to the expected response, we cannot give you support on this software, other than via the usual Kannel users mailing groups. There is nobody with experience on this particular matter of software, so please bear with me. I have little time to spend on free software. But releasing smppbox is a priority now, even when I cannot give sufficient support to all of you. If you want a carrier-grade, commerialy widely deployed smppbox or EMI server functionality, we direct you to the alternatives. For instance the smppbox that Stipe Tolj provides (s...@tolj.org). Cheers to all, Rene Kluwen Chimit
RE: smppbox
You contradict yourself now. First, you said documentation should be ready first to accept it. Now you say that you will write documentation when it is accepted. Either way, I was wrong in my original post. I thought that sqlbox was part of de gateway svn trunk already. But it is not. I don't know why not, other from historical reasons but I think (imo) smppbox should be treated the same way as sqlbox. Personally I think they both belong to 'gateway' instead of separate projects, because it is a lot easier for the users. But okay... if someone thinks they have a valid reason to have them split up (like the way it is now), it is fine for me as well. == Rene -Original Message- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: maandag 7 juni 2010 15:39 To: Rene Kluwen; 'Alexander Malysh' Cc: devel@kannel.org Subject: Re: smppbox OK, then. When it is accepted in the main kannel tree. BR, Nikos - Original Message - From: Rene Kluwen rene.klu...@chimit.nl To: 'Nikos Balkanas' nbalka...@gmail.com; 'Alexander Malysh' amal...@kannel.org Cc: devel@kannel.org Sent: Monday, June 07, 2010 4:21 PM Subject: RE: smppbox I see an excellent opportunity for you, Nikos, to prove your skills, writing documentation :) -Original Message- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: maandag 7 juni 2010 14:12 To: Rene Kluwen; Alexander Malysh Cc: devel@kannel.org Subject: Re: smppbox Dear Rene, Thanks a lot for this contribution. Upon succesful acceptance by kannel in the main svn, bear in mind that an additional component will be needed: a patch to kannel's User's guide. This is a requirement to every patch submitted to kannel. Can you take care of it? @Alex: This is a long awaited feature to bearerbox. It is also the second large contribution by Chimit. According to Rene it has been used in production for over a year without problems. I would like to see it in mainstream kannel. Is it feasible? My vote is +++1 BR, Nikos - Original Message - From: Rene Kluwen rene.klu...@chimit.nl To: us...@kannel.org Sent: Friday, May 07, 2010 11:56 PM Subject: smppbox Lectori Salutem, This email is about Chimit's smppbox. The rights to the smppbox code have been obtained by a third party, but fortunately there is some good news for the open source community. An early version of smppbox (smpp v.3.0) will now be donated back to the community. This version is by no means perfect and developers and investors are invited to contribute. All in the spirit of being an open-source community. Chimit already developed the successful sqlbox, which is now part of the main stream Kannel distribution, so if we all cooperate, this smppbox can go the same way. To get you started, here is a preliminary download: http://www.chimit.nl/kannel/smppbox.tar. Unfortunately, due to the expected response, we cannot give you support on this software, other than via the usual Kannel users mailing groups. There is nobody with experience on this particular matter of software, so please bear with me. I have little time to spend on free software. But releasing smppbox is a priority now, even when I cannot give sufficient support to all of you. If you want a carrier-grade, commerialy widely deployed smppbox or EMI server functionality, we direct you to the alternatives. For instance the smppbox that Stipe Tolj provides (s...@tolj.org). Cheers to all, Rene Kluwen Chimit
RE: smppbox
1. Thanks for the lecture. But documentation needs to be written anyway, either if the code will be part of the gateway trunk or separately. I am too busy myself to come up with some proper document any time soon. 2. I think you understood it wrong. Smppbox is similar to sqlbox with regards that it connects to bearerbox, just like smsbox. The patch is made for Kannel, but smppbox could easily be converted to some kind of smppbox-standalone, just like sqlbox is. You need to start it separately from bearerbox. So in short: Also a separate box, not required by everyone (as well as wapbox also, which happens to be part of Kannel). == Rene -Original Message- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: maandag 7 juni 2010 16:26 To: Rene Kluwen; 'Alexander Malysh' Cc: devel@kannel.org Subject: Re: smppbox Hi Rene, You may not be aware of it, but there is a 2-step acceptance. Or better phrased accept commit. Once the patch code is accepted, the patch doc is submitted. Then the whole package is committed to the svn. No sense after all to create a doc if the code is never accepted, right? That's what i meant, and this is how it is traditionally handled. SQLbox is an independent separate box, and one that is not necessary to everyone. SMPPbox is part of bearerbox. It can be activated or not based on configuration. But this is a decision for Alex. BR, Nikos - Original Message - From: Rene Kluwen rene.klu...@chimit.nl To: 'Nikos Balkanas' nbalka...@gmail.com; 'Alexander Malysh' amal...@kannel.org Cc: devel@kannel.org Sent: Monday, June 07, 2010 4:46 PM Subject: RE: smppbox You contradict yourself now. First, you said documentation should be ready first to accept it. Now you say that you will write documentation when it is accepted. Either way, I was wrong in my original post. I thought that sqlbox was part of de gateway svn trunk already. But it is not. I don't know why not, other from historical reasons but I think (imo) smppbox should be treated the same way as sqlbox. Personally I think they both belong to 'gateway' instead of separate projects, because it is a lot easier for the users. But okay... if someone thinks they have a valid reason to have them split up (like the way it is now), it is fine for me as well. == Rene -Original Message- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: maandag 7 juni 2010 15:39 To: Rene Kluwen; 'Alexander Malysh' Cc: devel@kannel.org Subject: Re: smppbox OK, then. When it is accepted in the main kannel tree. BR, Nikos - Original Message - From: Rene Kluwen rene.klu...@chimit.nl To: 'Nikos Balkanas' nbalka...@gmail.com; 'Alexander Malysh' amal...@kannel.org Cc: devel@kannel.org Sent: Monday, June 07, 2010 4:21 PM Subject: RE: smppbox I see an excellent opportunity for you, Nikos, to prove your skills, writing documentation :) -Original Message- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: maandag 7 juni 2010 14:12 To: Rene Kluwen; Alexander Malysh Cc: devel@kannel.org Subject: Re: smppbox Dear Rene, Thanks a lot for this contribution. Upon succesful acceptance by kannel in the main svn, bear in mind that an additional component will be needed: a patch to kannel's User's guide. This is a requirement to every patch submitted to kannel. Can you take care of it? @Alex: This is a long awaited feature to bearerbox. It is also the second large contribution by Chimit. According to Rene it has been used in production for over a year without problems. I would like to see it in mainstream kannel. Is it feasible? My vote is +++1 BR, Nikos - Original Message - From: Rene Kluwen rene.klu...@chimit.nl To: us...@kannel.org Sent: Friday, May 07, 2010 11:56 PM Subject: smppbox Lectori Salutem, This email is about Chimit's smppbox. The rights to the smppbox code have been obtained by a third party, but fortunately there is some good news for the open source community. An early version of smppbox (smpp v.3.0) will now be donated back to the community. This version is by no means perfect and developers and investors are invited to contribute. All in the spirit of being an open-source community. Chimit already developed the successful sqlbox, which is now part of the main stream Kannel distribution, so if we all cooperate, this smppbox can go the same way. To get you started, here is a preliminary download: http://www.chimit.nl/kannel/smppbox.tar. Unfortunately, due to the expected response, we cannot give you support on this software, other than via the usual Kannel users mailing groups. There is nobody with experience on this particular matter of software, so please bear with me. I have little time to spend on free software. But releasing smppbox is a priority now, even when I cannot give sufficient support to all of you. If you want a carrier-grade, commerialy widely deployed smppbox
Sqlbox feature request
Talking about sqlbox: If smsbox (or smppbox) is not connected, it stores the message in the sent table after which the message cannot be delivered anymore to smsbox (because it is not connected). This message could possibly be flagged with not delivered. Right? I am talking about MO messages and DLR's here. It will be a nice feature if upon connecting from an smsbox, it selects the messages that are not delivered yet and pushes them to smsbox. So those messages won't get lost. == Rene
RE: Sqlbox feature request
Sorry, maybe I am wrong. And bearerbox keeps those messages already in a queue (which is committed to the store-file?). To think about it more, I think this will be a better way to go. Can somebody shed a light about what happens to messages from bearerbox to smsbox that cannot be delivered, in the current code? I am not sure about where to look. == Rene From: devel-boun...@kannel.org [mailto:devel-boun...@kannel.org] On Behalf Of Rene Kluwen Sent: maandag 7 juni 2010 16:57 To: 'Alejandro Guerrieri' Cc: devel@kannel.org Subject: Sqlbox feature request Talking about sqlbox: If smsbox (or smppbox) is not connected, it stores the message in the sent table after which the message cannot be delivered anymore to smsbox (because it is not connected). This message could possibly be flagged with not delivered. Right? I am talking about MO messages and DLR's here. It will be a nice feature if upon connecting from an smsbox, it selects the messages that are not delivered yet and pushes them to smsbox. So those messages won't get lost. == Rene
RE: Sqlbox feature request
Ah, great! So I was worrying for nothing. Btw, the sqlbox feature as I suggested won't even possible, since if the smsbox in particular is not connected, also the messages won't be passed to sqlbox to begin with. So you can forget what I said ;=). == Rene From: Alejandro Guerrieri [mailto:aguerri...@kannel.org] Sent: maandag 7 juni 2010 17:30 To: Rene Kluwen Cc: devel@kannel.org Subject: Re: Sqlbox feature request Afaik, messages are kept on bearerbox store until the box ACK them. At that point, bearerbox deletes the message(s). Regards, Alex -- Alejandro Guerrieri aguerri...@kannel.org On 07/06/2010, at 17:06, Rene Kluwen wrote: Sorry, maybe I am wrong. And bearerbox keeps those messages already in a queue (which is committed to the store-file?). To think about it more, I think this will be a better way to go. Can somebody shed a light about what happens to messages from bearerbox to smsbox that cannot be delivered, in the current code? I am not sure about where to look. == Rene From: devel-boun...@kannel.org [mailto:devel-boun...@kannel.org] On Behalf Of Rene Kluwen Sent: maandag 7 juni 2010 16:57 To: 'Alejandro Guerrieri' Cc: devel@kannel.org Subject: Sqlbox feature request Talking about sqlbox: If smsbox (or smppbox) is not connected, it stores the message in the sent table after which the message cannot be delivered anymore to smsbox (because it is not connected). This message could possibly be flagged with not delivered. Right? I am talking about MO messages and DLR's here. It will be a nice feature if upon connecting from an smsbox, it selects the messages that are not delivered yet and pushes them to smsbox. So those messages won't get lost. == Rene
RE: smppbox
There's pro's and con's to each point of view. Technically speaking, an smppbox that is part of bearerbox isn't a box anymore, in Kannel-terminology (see figure 4-2 of the architecture document). Possibly you could also integrate smsbox wapbox to bearerbox but many reasons exist to not to do it. The protocols that bearerbox knows are smsc drivers (and UDP for wap) and on the top layer it communicates by Msg* structures over TCP. This is typically what smppbox does. It is not an smsc driver in the sense that it connects to an smsc like the ones that reside in bearerbox. In short: bearerbox protocols are clients and smppbox (and smsbox and sqlbox) are servers. Also Alex has a valid point: Using a separate box, smpp connections (and settings) can be distributed over any number of hosts. This also facilitates fail-over systems. Having kannel-boxes is for a reason and has been thought over pretty well. Anyhow, I am not saying smppbox A is better than smppbox B or smppbox C (if other implementations exist). It is just a difference between them and why opensmppbox (as some people refer to the one that I created) is built this way. == Rene -Original Message- From: Alejandro Guerrieri [mailto:aguerri...@kannel.org] Sent: maandag 7 juni 2010 18:45 To: Nikos Balkanas Cc: Rene Kluwen; devel@kannel.org Subject: Re: smppbox Well, there's (always) a tradeoff between simplicity and scalability, isn't it? Regards, -- Alejandro Guerrieri aguerri...@kannel.org On 07/06/2010, at 18:37, Nikos Balkanas wrote: Hi, Didn't intend to be pendatic. Whether smppbox is accepted in the trunk or main tree, it is still being accepted, and documentation must follow. However, if smppbox is rejected, no documentation is needed. If it is revised, documentation will again have to wait for final implementation. I am familiar with smppbox functionality from Stipe's release. However, bb is the hub for all external non-HTTP connections. I like current smppbox simplicity and efficiency (it has faster I/O than an external box). Currently it is a bb part and considerable redevelopment will be needed to make it a standalone box. Unless a compelling reason exists to externalize it, I wouldn't want to. But this is just my 2 cents worth. Cheers, Nikos - Original Message - From: Rene Kluwen rene.klu...@chimit.nl To: 'Nikos Balkanas' nbalka...@gmail.com; 'Alexander Malysh' amal...@kannel.org Cc: devel@kannel.org Sent: Monday, June 07, 2010 5:34 PM Subject: RE: smppbox 1. Thanks for the lecture. But documentation needs to be written anyway, either if the code will be part of the gateway trunk or separately. I am too busy myself to come up with some proper document any time soon. 2. I think you understood it wrong. Smppbox is similar to sqlbox with regards that it connects to bearerbox, just like smsbox. The patch is made for Kannel, but smppbox could easily be converted to some kind of smppbox-standalone, just like sqlbox is. You need to start it separately from bearerbox. So in short: Also a separate box, not required by everyone (as well as wapbox also, which happens to be part of Kannel). == Rene -Original Message- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: maandag 7 juni 2010 16:26 To: Rene Kluwen; 'Alexander Malysh' Cc: devel@kannel.org Subject: Re: smppbox Hi Rene, You may not be aware of it, but there is a 2-step acceptance. Or better phrased accept commit. Once the patch code is accepted, the patch doc is submitted. Then the whole package is committed to the svn. No sense after all to create a doc if the code is never accepted, right? That's what i meant, and this is how it is traditionally handled. SQLbox is an independent separate box, and one that is not necessary to everyone. SMPPbox is part of bearerbox. It can be activated or not based on configuration. But this is a decision for Alex. BR, Nikos - Original Message - From: Rene Kluwen rene.klu...@chimit.nl To: 'Nikos Balkanas' nbalka...@gmail.com; 'Alexander Malysh' amal...@kannel.org Cc: devel@kannel.org Sent: Monday, June 07, 2010 4:46 PM Subject: RE: smppbox You contradict yourself now. First, you said documentation should be ready first to accept it. Now you say that you will write documentation when it is accepted. Either way, I was wrong in my original post. I thought that sqlbox was part of de gateway svn trunk already. But it is not. I don't know why not, other from historical reasons but I think (imo) smppbox should be treated the same way as sqlbox. Personally I think they both belong to 'gateway' instead of separate projects, because it is a lot easier for the users. But okay... if someone thinks they have a valid reason to have them split up (like the way it is now), it is fine for me as well. == Rene -Original Message- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: maandag 7 juni 2010 15:39
smppbox standalone
This release is ONLY for developers. It contains an smppbox-standalone package, similar to sqlbox standalone. Most part were shamelessly stolen from the sqlbox trunk. Please add your own credits if you feel addressed ;). http://www.chimit.nl/kannel/smppbox_standalone.tar.gz How about making a repository from this? == Rene
