RE: sqlbox issue
You are right. The startup sequence should be bearerbox first en then smsbox and sqlbox respectively. The scheme that I gave refers to the message flow. == Rene From: Willy Mularto [mailto:sangpr...@gmail.com] Sent: Thursday, 22 March, 2012 15:50 To: Rene Kluwen Cc: 'Ravindra Gupta // Viva'; users-requ...@kannel.org; users@kannel.org; users-ow...@kannel.org Subject: Re: sqlbox issue I usually have bearerbox-sqlbox-smsbox. What's the effect of your startup scenario Rene? On Mar 22, 2012, at 9:14 PM, Rene Kluwen wrote: The usual setup is sqlbox -> smsbox -> bearerbox. In group = smsbox, you need: bearerbox-port = 13005. =+= Rene From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Ravindra Gupta // Viva Sent: Wednesday, 21 March, 2012 11:59 To: users-requ...@kannel.org; users@kannel.org; users-ow...@kannel.org Subject: sqlbox issue Hii, I have configured sqlbox to sending the SMS and I am facing bearerbox connectivity issue. Kindly find the below smskannel.conf file parameters. sqlbox ---> bearerbox >smsbox # # THIS IS A SAMPLE CONFIGURATION FOR SMS KANNEL #- # CORE # # There is only one core group and it sets all basic settings # of the bearerbox (and system). You should take extra notes on # configuration variables like 'store-file' (or 'store-dir'), # 'admin-allow-ip' and 'access.log' group = core admin-port = 13000 smsbox-port = 13001 #smsbox-port = 13003 admin-password = demokannel status-password =demokannel #status-password = foo #admin-deny-ip = "" #admin-allow-ip = "" log-file = "/var/log/kannel/bearerbox.log" log-level = 0 box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1" #unified-prefix = "+358,00358,0;+,00" access-log = "/var/log/kannel/kannel_access.log" store-file = "/home/kannel.store" #ssl-server-cert-file = "cert.pem" #ssl-server-key-file = "key.pem" #ssl-certkey-file = "mycertandprivkeyfile.pem" #dlr-storage= sqlbox sms-resend-freq=60 sms-resend-retry=5 #- # SMSC CONNECTIONS # # SMSC connections are created in bearerbox and they handle SMSC specific # protocol and message relying. You need these to actually receive and send # messages to handset, but can use GSM modems as virtual SMSCs group= smsc smsc = smpp smsc-id = demo host= 127.0.0.1 smsc-username= demo smsc-password= demo port = 1234 #receive-port= 1234 connect-allow-ip = 127.0.0.1 system-type="" #address-range="" #alt-charset=1 #alt-charset="ASCII" source-addr-ton=1 source-addr-npi=1 dest-addr-ton=1 dest-addr-npi=1 #msg-id-type=0x01 allowed-smsc-id= demo #transceiver-mode=1 throughput= 10 group= smsc smsc = smpp smsc-id = demo host= 127.0.0.1 smsc-username= demo smsc-password= demo #port = 1234 receive-port= 1234 connect-allow-ip = 127.0.0.1 system-type="" #address-range="" #alt-charset=1 #alt-charset="ASCII" source-addr-ton=1 source-addr-npi=1 dest-addr-ton=1 dest-addr-npi=1 #msg-id-type=0x01 allowed-smsc-id= demo #transceiver-mode=1 throughput= 10 # This is a fake smsc connection, _only_ used to test the system and services. # It really cannot relay messages to actual handsets! #--- # SMSBOX SETUP # # Smsbox(es) do higher-level SMS handling after they have been received from # SMS centers by bearerbox, or before they are given to bearerbox for delivery group = smsbox smsbox-id=dlrbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 #sendsms-port = 13003 global-sender = demo #sendsms-chars = "0123456789 +-" log-file = "/var/log/kannel/smsbox.log" log-level = 0 #access-log = "/tmp/access.log" http-request-retry=5 http-queue-delay=50 #- # SEND-SMS USERS # # These users are used when Kannel smsbox sendsms interface is used to # send PUSH sms messages, i.e. calling URL like # http://kannel.machine:13013/cgi-bin/sendsms?username=tester <http://kannel.machine:13013/cgi-bin/sendsms?username=tester&password=foobar .> &password=foobar... group = sendsms-user username = tester password = foobar #user-deny-ip = "" #user-allow-ip = "" concatenation = true default-smsc = demo #- # SERVICES # # These are 'responses' to sms PULL messages, i.e. messages arriving from # handsets. The response is based on message content. Only one sms-service is # applied, using the first one to match. group = sms-service keyword = nop accepted-smsc= demo text = "You asked nothing and I did
RE: sqlbox issue
The usual setup is sqlbox -> smsbox -> bearerbox. In group = smsbox, you need: bearerbox-port = 13005. =+= Rene From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Ravindra Gupta // Viva Sent: Wednesday, 21 March, 2012 11:59 To: users-requ...@kannel.org; users@kannel.org; users-ow...@kannel.org Subject: sqlbox issue Hii, I have configured sqlbox to sending the SMS and I am facing bearerbox connectivity issue. Kindly find the below smskannel.conf file parameters. sqlbox ---> bearerbox >smsbox # # THIS IS A SAMPLE CONFIGURATION FOR SMS KANNEL #- # CORE # # There is only one core group and it sets all basic settings # of the bearerbox (and system). You should take extra notes on # configuration variables like 'store-file' (or 'store-dir'), # 'admin-allow-ip' and 'access.log' group = core admin-port = 13000 smsbox-port = 13001 #smsbox-port = 13003 admin-password = demokannel status-password =demokannel #status-password = foo #admin-deny-ip = "" #admin-allow-ip = "" log-file = "/var/log/kannel/bearerbox.log" log-level = 0 box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1" #unified-prefix = "+358,00358,0;+,00" access-log = "/var/log/kannel/kannel_access.log" store-file = "/home/kannel.store" #ssl-server-cert-file = "cert.pem" #ssl-server-key-file = "key.pem" #ssl-certkey-file = "mycertandprivkeyfile.pem" #dlr-storage= sqlbox sms-resend-freq=60 sms-resend-retry=5 #- # SMSC CONNECTIONS # # SMSC connections are created in bearerbox and they handle SMSC specific # protocol and message relying. You need these to actually receive and send # messages to handset, but can use GSM modems as virtual SMSCs group= smsc smsc = smpp smsc-id = demo host= 127.0.0.1 smsc-username= demo smsc-password= demo port = 1234 #receive-port= 1234 connect-allow-ip = 127.0.0.1 system-type="" #address-range="" #alt-charset=1 #alt-charset="ASCII" source-addr-ton=1 source-addr-npi=1 dest-addr-ton=1 dest-addr-npi=1 #msg-id-type=0x01 allowed-smsc-id= demo #transceiver-mode=1 throughput= 10 group= smsc smsc = smpp smsc-id = demo host= 127.0.0.1 smsc-username= demo smsc-password= demo #port = 1234 receive-port= 1234 connect-allow-ip = 127.0.0.1 system-type="" #address-range="" #alt-charset=1 #alt-charset="ASCII" source-addr-ton=1 source-addr-npi=1 dest-addr-ton=1 dest-addr-npi=1 #msg-id-type=0x01 allowed-smsc-id= demo #transceiver-mode=1 throughput= 10 # This is a fake smsc connection, _only_ used to test the system and services. # It really cannot relay messages to actual handsets! #--- # SMSBOX SETUP # # Smsbox(es) do higher-level SMS handling after they have been received from # SMS centers by bearerbox, or before they are given to bearerbox for delivery group = smsbox smsbox-id=dlrbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 #sendsms-port = 13003 global-sender = demo #sendsms-chars = "0123456789 +-" log-file = "/var/log/kannel/smsbox.log" log-level = 0 #access-log = "/tmp/access.log" http-request-retry=5 http-queue-delay=50 #- # SEND-SMS USERS # # These users are used when Kannel smsbox sendsms interface is used to # send PUSH sms messages, i.e. calling URL like # http://kannel.machine:13013/cgi-bin/sendsms?username=tester <http://kannel.machine:13013/cgi-bin/sendsms?username=tester&password=foobar .> &password=foobar... group = sendsms-user username = tester password = foobar #user-deny-ip = "" #user-allow-ip = "" concatenation = true default-smsc = demo #- # SERVICES # # These are 'responses' to sms PULL messages, i.e. messages arriving from # handsets. The response is based on message content. Only one sms-service is # applied, using the first one to match. group = sms-service keyword = nop accepted-smsc= demo text = "You asked nothing and I did it!" # -- SMS BOX ROUTE --- # group = smsbox-route smsbox-id = dlrbox smsc-id = demo # There should be always a 'default' service. This service is used when no # other 'sms-service' is applied. group = sms-service keyword = default text = <480 Characters with spaces> concatenation = true max-messages = 5 group = mysql-connection id = mydlr host = localhost username = root password = root database = dlr group = dlr-db id = mydlr table = dlr field-smsc = smsc fiel
Re: sqlbox issue
Hi, you are missing the bearerbox-port variable in your smsbox group config, the arch is a little different from what you have, it should be: smsbox --> sqlbox --> bearerbox So, in your smsbox, your bearerbox-port should be the same as the sqlbox-smsbox-port. Hope it helps. JuanL From: Ravindra Gupta // Viva Date: Wed, 21 Mar 2012 16:29:16 +0530 To: , , Subject: sqlbox issue Hii, I have configured sqlbox to sending the SMS and I am facing bearerbox connectivity issue. Kindly find the below smskannel.conf file parameters. sqlbox ---> bearerbox >smsbox # # THIS IS A SAMPLE CONFIGURATION FOR SMS KANNEL #- # CORE # # There is only one core group and it sets all basic settings # of the bearerbox (and system). You should take extra notes on # configuration variables like 'store-file' (or 'store-dir'), # 'admin-allow-ip' and 'access.log' group = core admin-port = 13000 smsbox-port = 13001 #smsbox-port = 13003 admin-password = demokannel status-password =demokannel #status-password = foo #admin-deny-ip = "" #admin-allow-ip = "" log-file = "/var/log/kannel/bearerbox.log" log-level = 0 box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1" #unified-prefix = "+358,00358,0;+,00" access-log = "/var/log/kannel/kannel_access.log" store-file = "/home/kannel.store" #ssl-server-cert-file = "cert.pem" #ssl-server-key-file = "key.pem" #ssl-certkey-file = "mycertandprivkeyfile.pem" #dlr-storage= sqlbox sms-resend-freq=60 sms-resend-retry=5 #- # SMSC CONNECTIONS # # SMSC connections are created in bearerbox and they handle SMSC specific # protocol and message relying. You need these to actually receive and send # messages to handset, but can use GSM modems as virtual SMSCs group= smsc smsc = smpp smsc-id = demo host= 127.0.0.1 smsc-username= demo smsc-password= demo port = 1234 #receive-port= 1234 connect-allow-ip = 127.0.0.1 system-type="" #address-range="" #alt-charset=1 #alt-charset="ASCII" source-addr-ton=1 source-addr-npi=1 dest-addr-ton=1 dest-addr-npi=1 #msg-id-type=0x01 allowed-smsc-id= demo #transceiver-mode=1 throughput= 10 group= smsc smsc = smpp smsc-id = demo host= 127.0.0.1 smsc-username= demo smsc-password= demo #port = 1234 receive-port= 1234 connect-allow-ip = 127.0.0.1 system-type="" #address-range="" #alt-charset=1 #alt-charset="ASCII" source-addr-ton=1 source-addr-npi=1 dest-addr-ton=1 dest-addr-npi=1 #msg-id-type=0x01 allowed-smsc-id= demo #transceiver-mode=1 throughput= 10 # This is a fake smsc connection, _only_ used to test the system and services. # It really cannot relay messages to actual handsets! #--- # SMSBOX SETUP # # Smsbox(es) do higher-level SMS handling after they have been received from # SMS centers by bearerbox, or before they are given to bearerbox for delivery group = smsbox smsbox-id=dlrbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 #sendsms-port = 13003 global-sender = demo #sendsms-chars = "0123456789 +-" log-file = "/var/log/kannel/smsbox.log" log-level = 0 #access-log = "/tmp/access.log" http-request-retry=5 http-queue-delay=50 #- # SEND-SMS USERS # # These users are used when Kannel smsbox sendsms interface is used to # send PUSH sms messages, i.e. calling URL like # http://kannel.machine:13013/cgi-bin/sendsms?username=tester&password=foobar. .. group = sendsms-user username = tester password = foobar #user-deny-ip = "" #user-allow-ip = "" concatenation = true default-smsc = demo #- # SERVICES # # These are 'responses' to sms PULL messages, i.e. messages arriving from # handsets. The response is based on message content. Only one sms-service is # applied, using the first one to match. group = sms-service keyword = nop accepted-smsc= demo text = "You asked nothing and I did it!" # -- SMS BOX ROUTE --- # group = smsbox-route smsbox-id = dlrbox smsc-id = demo # There should be always a 'default' service. This service is used when no # other 'sms-service' is applied. group = sms-service keyword = default text = <480 Characters with spaces> concatenation = true max-messages = 5 group = mysql-connection id = mydlr host = localhost username = root password = root database = dlr group = dlr-db id = mydlr table = dlr field-smsc = smsc field-timestamp = ts field-source = source field-destination = destination field-service = service field-url = url field-mask = mask field-status = status field-boxc-id= boxc ##sqlbox .conf# group = sqlbox id = sqlbox-db sm
sqlbox issue
Hii, I have configured sqlbox to sending the SMS and I am facing bearerbox connectivity issue. Kindly find the below smskannel.conf file parameters. *sqlbox ---> bearerbox >smsbox* # # THIS IS A SAMPLE CONFIGURATION FOR SMS KANNEL #- # CORE # # There is only one core group and it sets all basic settings # of the bearerbox (and system). You should take extra notes on # configuration variables like 'store-file' (or 'store-dir'), # 'admin-allow-ip' and 'access.log' group = core admin-port = 13000 smsbox-port = 13001 #smsbox-port = 13003 admin-password = demokannel status-password =demokannel #status-password = foo #admin-deny-ip = "" #admin-allow-ip = "" log-file = "/var/log/kannel/bearerbox.log" log-level = 0 box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1" #unified-prefix = "+358,00358,0;+,00" access-log = "/var/log/kannel/kannel_access.log" store-file = "/home/kannel.store" #ssl-server-cert-file = "cert.pem" #ssl-server-key-file = "key.pem" #ssl-certkey-file = "mycertandprivkeyfile.pem" #dlr-storage= sqlbox sms-resend-freq=60 sms-resend-retry=5 #- # SMSC CONNECTIONS # # SMSC connections are created in bearerbox and they handle SMSC specific # protocol and message relying. You need these to actually receive and send # messages to handset, but can use GSM modems as virtual SMSCs group= smsc smsc = smpp smsc-id = demo host= 127.0.0.1 smsc-username= demo smsc-password= demo port = 1234 #receive-port= 1234 connect-allow-ip = 127.0.0.1 system-type="" #address-range="" #alt-charset=1 #alt-charset="ASCII" source-addr-ton=1 source-addr-npi=1 dest-addr-ton=1 dest-addr-npi=1 #msg-id-type=0x01 allowed-smsc-id= demo #transceiver-mode=1 throughput= 10 group= smsc smsc = smpp smsc-id = demo host= 127.0.0.1 smsc-username= demo smsc-password= demo #port = 1234 receive-port= 1234 connect-allow-ip = 127.0.0.1 system-type="" #address-range="" #alt-charset=1 #alt-charset="ASCII" source-addr-ton=1 source-addr-npi=1 dest-addr-ton=1 dest-addr-npi=1 #msg-id-type=0x01 allowed-smsc-id= demo #transceiver-mode=1 throughput= 10 # This is a fake smsc connection, _only_ used to test the system and services. # It really cannot relay messages to actual handsets! #--- # SMSBOX SETUP # # Smsbox(es) do higher-level SMS handling after they have been received from # SMS centers by bearerbox, or before they are given to bearerbox for delivery group = smsbox smsbox-id=dlrbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 #sendsms-port = 13003 global-sender = demo #sendsms-chars = "0123456789 +-" log-file = "/var/log/kannel/smsbox.log" log-level = 0 #access-log = "/tmp/access.log" http-request-retry=5 http-queue-delay=50 #- # SEND-SMS USERS # # These users are used when Kannel smsbox sendsms interface is used to # send PUSH sms messages, i.e. calling URL like # http://kannel.machine:13013/cgi-bin/sendsms?username=tester&password=foobar. .. group = sendsms-user username = tester password = foobar #user-deny-ip = "" #user-allow-ip = "" concatenation = true default-smsc = demo #- # SERVICES # # These are 'responses' to sms PULL messages, i.e. messages arriving from # handsets. The response is based on message content. Only one sms-service is # applied, using the first one to match. group = sms-service keyword = nop accepted-smsc= demo text = "You asked nothing and I did it!" # -- SMS BOX ROUTE --- # group = smsbox-route smsbox-id = dlrbox smsc-id = demo # There should be always a 'default' service. This service is used when no # other 'sms-service' is applied. group = sms-service keyword = default text = <480 Characters with spaces> concatenation = true max-messages = 5 group = mysql-connection id = mydlr host = localhost username = root password = root database = dlr group = dlr-db id = mydlr table = dlr field-smsc = smsc field-timestamp = ts field-source = source field-destination = destination field-service = service field-url = url field-mask = mask field-status = status field-boxc-id= boxc ##sqlbox .conf# group = sqlbox id = sqlbox-db smsbox-id = sqlbox #global-sender = "" bearerbox-host = localhost bearerbox-port = 13001 smsbox-port = 13005 smsbox-port-ssl = false sql-log-table = sent_sms sql-insert-table = send_sms log-file = "/var/log/kannel/kannel-sqlbox.log" log-level = 0 #ssl-client-certkey-file = "" #ssl-server-cert-file = "" #ssl-server-key-file = "" #ssl-trusted-ca-file = "" # Database connection examples. Please uncomment as needed # Example MYSQL Connection group = mysql-connection id = sqlbox-db host = localhost username = root password = sqladmin database = smart_kannel so kindly let me if any wrong parameters I have mention.
Re: SQLBOX issue
I think it could be a DNS issue, maybe you try to add the hostname to your /etc/hosts file Regards On Tue, Mar 20, 2012 at 1:01 PM, ha...@aeon.pk wrote: > Hi, > > > > I am connecting multiple sqlboxes with single bearerbox. It was working > fine before today, when my second instance of sqlbox is giving following > error on starting: > > > > 2012-03-20 22:56:40 [12711] [0] ERROR: Error while gw_gethostbyname occurs. > > 2012-03-20 22:56:40 [12711] [0] ERROR: System error 1: Operation not > permitted > > 2012-03-20 22:56:40 [12711] [0] ERROR: Can't find out official hostname > for this host, using `xx' instead. > > 2012-03-20 22:56:40 [12711] [0] INFO: Debug_lvl = 1, log_file = , > log_lvl = 0 > > 2012-03-20 22:56:40 [12711] [0] INFO: Starting to log to file > /usr/smsc/logs/sqlbox.log level 0 > > 2012-03-20 22:56:40 [12711] [0] INFO: Added logfile > `/usr/smsc/logs/sqlbox.log' with level `0'. > > 2012-03-20 22:56:40 [12711] [0] INFO: MYSQL: Connected to server at > localhost. > > 2012-03-20 22:56:40 [12711] [0] INFO: MYSQL: server version 5.1.56-log, > client version 5.1.56. > > 2012-03-20 22:56:40 [12711] [1] INFO: Connected to bearerbox at > xxx port 13002. > > 2012-03-20 22:56:40 [12711] [2] ERROR: Error reading from fd 11: > > 2012-03-20 22:56:40 [12711] [2] ERROR: System error 104: Connection reset > by peer > > 2012-03-20 22:56:40 [12711] [2] ERROR: Connection to bearerbox broke. > > > > Can someone help about what is going on? > > > > Regards, > > Hamza >
SQLBOX issue
Hi, I am connecting multiple sqlboxes with single bearerbox. It was working fine before today, when my second instance of sqlbox is giving following error on starting: 2012-03-20 22:56:40 [12711] [0] ERROR: Error while gw_gethostbyname occurs. 2012-03-20 22:56:40 [12711] [0] ERROR: System error 1: Operation not permitted 2012-03-20 22:56:40 [12711] [0] ERROR: Can't find out official hostname for this host, using `xx' instead. 2012-03-20 22:56:40 [12711] [0] INFO: Debug_lvl = 1, log_file = , log_lvl = 0 2012-03-20 22:56:40 [12711] [0] INFO: Starting to log to file /usr/smsc/logs/sqlbox.log level 0 2012-03-20 22:56:40 [12711] [0] INFO: Added logfile `/usr/smsc/logs/sqlbox.log' with level `0'. 2012-03-20 22:56:40 [12711] [0] INFO: MYSQL: Connected to server at localhost. 2012-03-20 22:56:40 [12711] [0] INFO: MYSQL: server version 5.1.56-log, client version 5.1.56. 2012-03-20 22:56:40 [12711] [1] INFO: Connected to bearerbox at xxx port 13002. 2012-03-20 22:56:40 [12711] [2] ERROR: Error reading from fd 11: 2012-03-20 22:56:40 [12711] [2] ERROR: System error 104: Connection reset by peer 2012-03-20 22:56:40 [12711] [2] ERROR: Connection to bearerbox broke. Can someone help about what is going on? Regards, Hamza
Re: sqlbox issue
Cavit is absolutely right. Just two things: 1) Take a look to the example file configuration located in "example" directory. 2) To compile sqlbox in another directory: ./configure --prefix=/DIRECTORY M On 10/30/06, Cavit Dolgun <[EMAIL PROTECTED]> wrote: As far as I know the patch will not work with kannel 1.4.1, it doesn't even work with the latest cvs version of kannel since there have been some changes in the source code of kannel. The sqlbox standalone is a separate application so you can not define directives for it in the kannel configuration. It is normal for kannel to give error messages since it is not expecting that directive in the kannel configuration file. If you use the patch (which will not work and I don't know which version of kannel it works with to be exact) then since kannel will be modified to read that directive from the config file, it will work fine. You can install bearerbox and sqlbox in different or the same locations. It should not make any difference. If you dig the archives you can see a recent post about sqlbox standalone and some information about it. Regards, Cavit Dolgun From: Eyram Schwinger [mailto:[EMAIL PROTECTED] Sent: Monday, October 30, 2006 14:46 To: kannel Subject: sqlbox issue I read an faq for sqlbox patch with the cvs version of kannel. I am using kannel 1.4.1 and I want to know if the standalone version of sqlbox also works with this faq. I realizedc that when I build sqlbox it is installed into /usr/local/bin while the bearerbox is installed into /usr/local/bin. So my first question is should that be the case? Also after building both when I insert the configuration bearerbox-is-sqlbox in the smsbox group and run kannel with that configuration file it gives me an error that bearerbox-is-sqlbox is not supposed to be there so then I wonder if that only works for the patch and if so whether the patch works for 1.4.1 as well. That is the patch here http://www.chimit.nl/kannel/sqlbox_patch-20041012.tar hope to get a reply soon Send instant messages to your online friends http://uk.messenger.yahoo.com
RE: sqlbox issue
As far as I know the patch will not work with kannel 1.4.1, it doesn’t even work with the latest cvs version of kannel since there have been some changes in the source code of kannel. The sqlbox standalone is a separate application so you can not define directives for it in the kannel configuration. It is normal for kannel to give error messages since it is not expecting that directive in the kannel configuration file. If you use the patch (which will not work and I don’t know which version of kannel it works with to be exact) then since kannel will be modified to read that directive from the config file, it will work fine. You can install bearerbox and sqlbox in different or the same locations. It should not make any difference. If you dig the archives you can see a recent post about sqlbox standalone and some information about it. Regards, Cavit Dolgun From: Eyram Schwinger [mailto:[EMAIL PROTECTED] Sent: Monday, October 30, 2006 14:46 To: kannel Subject: sqlbox issue I read an faq for sqlbox patch with the cvs version of kannel. I am using kannel 1.4.1 and I want to know if the standalone version of sqlbox also works with this faq. I realizedc that when I build sqlbox it is installed into /usr/local/bin while the bearerbox is installed into /usr/local/bin. So my first question is should that be the case? Also after building both when I insert the configuration bearerbox-is-sqlbox in the smsbox group and run kannel with that configuration file it gives me an error that bearerbox-is-sqlbox is not supposed to be there so then I wonder if that only works for the patch and if so whether the patch works for 1.4.1 as well. That is the patch here http://www.chimit.nl/kannel/sqlbox_patch-20041012.tar hope to get a reply soon Send instant messages to your online friends http://uk.messenger.yahoo.com
sqlbox issue
I read an faq for sqlbox patch with the cvs version of kannel. I am using kannel 1.4.1 and I want to know if the standalone version of sqlbox also works with this faq. I realizedc that when I build sqlbox it is installed into /usr/local/bin while the bearerbox is installed into /usr/local/bin. So my first question is should that be the case? Also after building both when I insert the configuration bearerbox-is-sqlbox in the smsbox group and run kannel with that configuration file it gives me an error that bearerbox-is-sqlbox is not supposed to be there so then I wonder if that only works for the patch and if so whether the patch works for 1.4.1 as well. That is the patch herehttp://www.chimit.nl/kannel/sqlbox_patch-20041012.tarhope to get a reply soonSend instant messages to your online friends http://uk.messenger.yahoo.com
