Sorry, forgot to post to the list. -----Original Message----- From: Rene Kluwen [mailto:[EMAIL PROTECTED] Sent: woensdag 9 juni 2004 20:38 To: Alexander Malysh Subject: RE: [patch] SQLBOX
Alexander, 1. You were ahead of me... and posted before I read all the msgs in the list... my bad... 2. I will look up which is exactly DocBook format. No experience with that... But will try... 3. Attached is a FAQ, meant to be preliminary documentation before the documentation patch is ready. Cheers, 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 avoid sending me Word, Excel or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
This is the SQLBOX FAQ. It's function is to help people going, at least before there is a proper documentation patch. 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.
