Re: kannel performance
Hi Nikkos, Thanks again for ur time and support. I wil try with spool and fakesmsc and get back to you. but as usggested by you i had serious look at the logs and what makes sense to inform u is bellow findings. i m sending sms through http as bellow http://$kannelHost:$kannelPort/cgi-bin/sendsms?dlr=1dlr-mask=31dlr-url=$durlusername=$userNamepassword=$userPasswordfrom=$fromto=$totext=$msgsmsc=putty where $userName = daf; and $userPassword = daf; how ever in bearerbox access.log i see the folowing.for some numbers it adds send-SMS request added 2 times.and for other only once. bellow is an example where it is trying 2 times. 2010-10-06 12:13:21 send-SMS request added - sender:daf:daffodil 77.91.205.191 target:351919582869 request: 'kannel is a beautifull world 2010-10-06 12:12:43' 2010-10-06 12:13:21 send-SMS request added - sender:tester:daffodil 77.91.205.230 target:351919582869 request: 'kannel is a beautifull world 2010-10-06 12:12:43' and u can see my config as bellow group=sendsms-user username=daf password=daf user-allow-ip= *.*.*.* # SMSC HTTP group = smsc smsc = http msg-id-type=0x01 smsc-id = C system-type = kannel smsc-username = tester smsc-password = foobar port = 13015 connect-allow-ip = *.*.*.* send-url = http://daf.com:13013/cgi-bin/sendsms; # SMSC SMPP group = smsc smsc=smpp smsc-id=putty host=213.30.43.217 port=7677 transceiver-mode=true alt-charset=ISO-8859-1 msg-id-type=0x01 system-type=putty2 service-type=12664 address-range= max-pending-submits=10 smsc-username=putty smsc-password=putty12664 connect-allow-ip=*.*.*.* dest-addr-npi=1 dest-addr-ton=1 flow-control=0 log-file=/var/log/kannel/smsc.log log-level=3 wait-ack=120 wait-ack-expire=0x02 throughput=100 window=10 validityperiod = 10 Br Daf Nikos Balkanas wrote: Hi, 1) Test sending 1 sms using fakesmsc, as to avoid costs. Check storage status at end. 2) Spool is generally faster and more real-time than file for storage. Depends on fs parameters. 3) Resubmission is a problem, since it implies that smsc is not sending ACKs back. However, since you have specified to wait for an ACK indefinitely, it shouldn't resend the same sms again. I am assuming you are using the SMPP smsc. Try on sending a few SMS (~5), comment out log-file in smsc group and turn bb logs to maximum detail. Watch for anything unusual, especially ACKs. Post relevant portions if you get any problems. BR, Nikos - Original Message - From: dafodil neo.tu...@yahoo.com To: users@kannel.org Sent: Friday, October 08, 2010 8:44 PM Subject: Re: kannel performance Hi nikkos, just to add more operator says that kannel is senindg submit_sm for same number multiple times. Br daf Nikos Balkanas wrote: Hi, I don't think it is practical to set log-level to 0 for 10k SMS :-( How does it behave when sending just a few messages? Try changing store-type to spool. Describe test conditions. Were all of your smsc active during tests? BR, Nikos - Original Message - From: Willy Mularto sangpr...@gmail.com To: dafodil neo.tu...@yahoo.com Cc: users@kannel.org Sent: Friday, October 08, 2010 5:55 PM Subject: Re: kannel performance It would be helpful if you provide us your detailed log. Please set log-level to 0. sangprabv sangpr...@gmail.com http://www.petitiononline.com/froyo/ On Oct 8, 2010, at 6:54 PM, dafodil wrote: Hi List, Good Day. While stress testing with kannel i found the follwing.i was trying to send 10 k sms through HTTP/sendsms. storage internal queued grows to 230. kannel.store size keeps growing and now it seems to be 480,630,358. now i find a kannel.store.new is created with size more than 2000. my configuration are as bellow.I feel i have some wrong configuration. my provider does not have any problem and supports more than 100 sms/sec. my bearerbox size keeps growing.can any one suggest or guide me where i m wrong. all sms are not reaching smsc provider. group = core admin-port=13000 admin-password=xxx status-password=xxx sms-resend-retry = 1 sms-resend-freq = 120 admin-allow-ip=*.*.*.* log-level= 3 log-file = /var/log/kannel/bearerbox.log smsbox-port=13001 wapbox-port=13002 wdp-interface-name=* store-file=/var/log/kannel/kannel.store # SMSC FAKE group = smsc smsc-id = A smsc = fake port = 1 connect-allow-ip = *.*.*.* # SMSC SMPP group = smsc smsc=smpp smsc-id= host=222.22.22.222 port=7677 transceiver-mode=true alt-charset=ISO-8859-1 msg-id-type=0x01 system-type=xxx service-type=xxx address-range= max-pending-submits=10 smsc-username=xxx smsc-password=x connect-allow-ip=*.*.*.* dest-addr-npi=1 dest-addr-ton=1 flow-control=0 log-file=/var/log/kannel/mylog.log log-level=3 wait-ack=120 wait-ack-expire=0x02 throughput=100 window=10 validityperiod = 10 # SMSC HTTP group = smsc smsc = http msg-id-type=0x01 smsc-id = C system-type = kannel
RE: Regarding OTA Message
Sir,
I am able to send the OTA Settings Message by using following Method.
In the following method UserPin has been used , But i want to use Netwpin (Imsi
No) .
I had already verified my IMSI no and it is ok . It has 15 digit .
After reading and searching i came to know that we should provide Netwpin as
semi-octets .
Please help me to know how can i use Netwpin to send the following settings.
Regards
Harmeet Singh
From: Benaiad [mailto:bena...@gmail.com]
Sent: 24 May 2010 04:00
To: Harmeet Singh
Cc: kannel users
Subject: Re: Regarding OTA Message
Hi,
I wrote a java method for this and I hope it helps:
Note: I've tested this on the latest kannel svn and you have to do the same.
public String sendOMASettings(String to, String pin) {
String result = ;
try {
StringBuffer buffer = new StringBuffer();
if (pin == null) {
pin = ;
}
buffer.append(?xml version=\1.0\?\r\n).
append(!DOCTYPE wap-provisioningdoc PUBLIC
\-//WAPFORUM//DTD PROV 1.0//EN\ \http://www.wapforum.org/DTD/prov.dtd\
http://www.wapforum.org/DTD/prov.dtd/ \r\n).
append(wap-provisioningdoc \r\n).
append(characteristic type=\NAPDEF\\r\n).
append(parm name=\NAPID\ value=\inet\/\r\n).
append(parm name=\NAME\ value=\Idea Internet\/\r\n).
append(parm name=\BEARER\ value=\GSM-GPRS\/\r\n).
append(parm name=\NAP-ADDRESS\
value=\internet\/\r\n).
append(parm name=\NAP-ADDRTYPE\
value=\internet\/\r\n).
append(parm name=\INTERNET\/\r\n).
append(/characteristic\r\n).
append(characteristic type=\APPLICATION\\r\n).
append(parm name=\APPID\ value=\w2\/\r\n).
append(parm name=\TO-NAPID\ value=\inet\/\r\n).
append(characteristic type=\RESOURCE\\r\n).
append(parm name=\URI\
value=\http://google.com\/\r\n).
append(parm name=\STARTPAGE\/\r\n).
append(/characteristic\r\n).
append(/characteristic\r\n).
append(/wap-provisioningdoc\r\n);
String data = java.net.URLEncoder.encode(buffer.toString(), UTF8);
String toInURL = java.net.URLEncoder.encode(to, UTF8);
String sendURL = http://; + kannelServerIP + : +
serverSendPort + /cgi-bin/sendota?username= + user
+ password= + password + coding=2to= + toInURL + text=
+ data + smsc= + yoursmsc + from=
+ yourShortNumber + type=oma-settings + sec=userpin +
pin= + pin ;
java.net.URL url = new java.net.URL(sendURL);
java.io.InputStream in = url.openStream();
java.io.BufferedInputStream bufIn = new
java.io.BufferedInputStream(in);
for (;;) {
int car = bufIn.read();
if (car == -1) {
break;
} else {
result = result + (char) car;
}
}
bufIn.close();
in.close();
} catch (Exception e) {
e.printStackTrace();
result = failed;
}
return result;
} //END
Regards,
--
Benaiad
RE: help with sms-service and sqlbox
Put bearerbox-port = 13005 (the sqlbox port) in group = smsbox. From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of mac...@fastermail.com Sent: Tuesday, 05 October, 2010 13:14 To: users@kannel.org Subject: help with sms-service and sqlbox Hey fellows my kannel server keeps telling me that it can not fetch content even when i specified the directives required in the get-url as you can see below.Then i have installed sqlbox on my fedora 13 but what baffles me is when i send the messages using the httpd interface nothing is recorded in the table sent_sms even if the message is successfully sent.But when i do a manual send in the database with the insert command on the mysql database the messages are sent and stored in the database.Any idea what i should to do in order for the messages to be recorded in the database when i send using the http interface. I defined the table message with fields msg,sender and time and wrote a script that was supposed to insert the values into these fields specified by the incomming message.Could you correct me if am wrong because in my understanding %a,%t and %p are variables for message,time and phone number respectively.Hence i used msg,time and sender as my variables for my php script that was required to insert the messages into the table defined. The smskannel and sqlbox are successfully starting but there are in two seperate configurations but are both in the same directory. smskannel configuration file group = core admin-port = 13000 smsbox-port = 13001 admin-password = camcom status-password = camcom #admin-deny-ip = #admin-allow-ip = #log-file = /tmp/kannel.log #log-level = 0 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 #unified-prefix = +358,00358,0;+,00 #access-log = /tmp/access.log #store-file = kannel.store #ssl-server-cert-file = cert.pem #ssl-server-key-file = key.pem #ssl-certkey-file = mycertandprivkeyfile.pem dlr-storage = mysql #group = smsc #smsc = fake #smsc-id = FAKE #port = 2 #connect-allow-ip = 127.0.0.1 group = smsc smsc = at modemtype = auto device = /dev/ttyUSB0 my-number = 0888959802 log-level = 0 sim-buffering = true group = smsbox bearerbox-host = localhost sendsms-port = 13013 sendsms-chars = 0123456789 global-sender = 0888959802 access-log = /home/camcom/kannel.access log-file = /home/camcom/smsbox.log log-level = 0 #sendsms-chars = 0123456789 +- #log-file = /tmp/smsbox.log #access-log = /tmp/access.log group = sendsms-user username = camcom password = camcom max-messages = 2 concatenation = true group = sms-service keyword = default #text = You asked nothing and I did it! get-url = http://127.0.0.1:80/var/www/html/receive.php?msg=%atime=%tsender=%p; max-messages = 1 concatenation = true #group = sms-service #keyword = default #text = No service specified group = mysql-connection id = mydlr host = localhost username = root password = camcom database = dlr # max count of connections that will be opened for dbpool #default is 1 #max-connections = 1 group = dlr-db id = mydlr table = dlr field-smsc = smsc field-timestamp = ts field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxc group = modems id = huawei_e160 name = huawei_e160 detect-string = huawei init-string = ATZ init-string = ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 init-string = AT+CNMI= 2,0,0,2,0 message-storage = sm speed = 9600 sqlbox configuration 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 = group = mysql-connection id = sqlbox-db host = localhost username = root password = camcom database = dlr max-connections = 1
RE: DLR Callback Unexpected Error with Clickatell
What is your smsc config? E.g. if it says: port = 8060, you need to point the dlr-url to this port. == Rene -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Alvaro Cornejo Sent: Wednesday, 06 October, 2010 15:54 To: Gjergji Guri Cc: users@kannel.org Subject: Re: DLR Callback Unexpected Error with Clickatell I think you are mixing things ...cgi-bin/sendsms is for sending MT messages therefore it needs a minimal set of arguments to send the MT or SMS Messages. At least destination number and message, in its own format as per the user guide. the dlr-url that clickatell needs to call is an script of your own that wil process it accordingly to your needs. You can not send a dlr to the cgi-bin/sendsms message since kannel will try to send it as an sms message. Regards Alvaro |--- --| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com On Wed, Oct 6, 2010 at 2:13 AM, Gjergji Guri gjergji.g...@facilization.com wrote: Hi everyone, We had a problem to set the dlr callback URL using Clicktell portal for a new user account yesterday. I was not able to set the Delivery URL in the configuration Clickatell using their web site for a new account. When setting the value of the Enable SMS Status Notification (MT Callback) to http://OurRealIP:13015/cgi-bin/sendsms that points to our Kannel server, were getting an error message saying Clickatell was unable to verify the URL specified. Reason code: HTTP (400) : Bad Request. We then tried to set the Delivery URL for another Clickatell account for which we were succesfully receiving DLR untill 5 minutes ago, but again the request was not succesfull and the bb log was showing the following lines 2010-10-06 00:33:58 [2121] [6] DEBUG: HTTP[clickatell]: Got request `/cgi-bin/sendsms' 2010-10-06 00:33:58 [2121] [6] DEBUG: HTTP[clickatell]: Received a request 2010-10-06 00:33:58 [2121] [6] ERROR: HTTP[clickatell]: Insufficient args. 2010-10-06 00:33:58 [2121] [6] DEBUG: HTTP[clickatell]: Sending reply `Insufficient arguments, rejected.'. 2010-10-06 00:33:58 [2121] [6] DEBUG: HTTP: Resetting HTTPClient for `196.5.254.33'. 2010-10-06 00:33:58 [2121] [6] DEBUG: HTTP[clickatell]: Destroying client information 2010-10-06 00:33:59 [2121] [1] DEBUG: HTTP: Destroying HTTPClient area 0x9430a40. I raised an issue with Clickatell immediatelly as we did not make any changes at our end and I still do not have an answer. Does anyone have any clue about what my be the reason? Regards, Gjergji
RE: sms - dlr bounding
You have a quote mismatch in that INSERT statement. -Original Message- From: dorian [mailto:doria...@o2.pl] Sent: Thursday, 07 October, 2010 08:32 To: Rene Kluwen Cc: 'Alejandro Guerrieri'; users@kannel.org Subject: Re: sms - dlr bounding Rene, Thanks a lot a lot for the advice. Recently I've found some time to test your idea. At the first glance it looked like great solution. I've used the following INSERT statement (php syntax) INSERT INTO send_sms (momt, sender, receiver, msgdata, sms_type, dlr_mask, dlr_url) VALUES ( 'MT', '8765', '.$phone_nr.', '.$txt.', 2, 31,'.$id); where $id contained unique id (but not url). For a moment it worked as expected. But now no DLRs are registered in the sms_sent table although I see the it is sent back from smsc. Any idea? I do not understand why for the first trials the DLRs has been stored into the table but now they are not. Dorian The thing that you might be looking for: If -instead of using smsbox- you use sqlbox to send messages, then you can set dlr-url to whatever you want. It doesn't necessarily have to be a http url. After that, you get your DLR's in the sent_sms table with the value you passed as drl-url. But since sqlbox doesn't call any http requests, as opposed to smsbox it just stays there in the table with boxc_id the same as you defined as sqlbox-id. Judging from your emails, I think this is what you want. == Rene -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of dorian Sent: Friday, 17 September, 2010 11:33 To: Alejandro Guerrieri Cc: users@kannel.org Subject: Re: sms - dlr bounding Well. I know the difference between fork and pthread_create. Anyway the http client work (even if it is thread not a process) is waste of time for me. Additionally I am forced to have working http server also which also do a silly work for me (taking CPU time and RAM). I am trying to find out the way to have dlr report but not to be forced to run http server since dlr reply is handled with sqlbox and it is enough for me. (on condition that I am able to bound sms with dlr) Dorian, Kannel uses threads. It doesn't fork. There's a _huge_ difference in terms of cost between a thread and fork. Using exec is a very bad idea in terms of performance and security. Regards, Alex On Fri, Sep 17, 2010 at 10:59 AM, dorian doria...@o2.pl mailto:doria...@o2.pl wrote: 1. See DEBUG line. Even if it is thread it takes time and RAM to create, the thread running take time preparing http request, my http server waste time to handle the request etc. 2. I need dlr feedback On Fri, 2010-09-17 at 09:26, dorian wrote: Right. But for http connection the kannel's clients is forked (at least it looks like according to the logs: 'DEBUG: HTTP: Creating HTTPClient'). Such fork is almost the same as exec'ing external process. How do you know it is fork? It could be thread or even simple function call. So I prefer exec my script rather than kannel's http client. This way the are no resources consumed by http server and the time needed for http request compose and parse is saved. In case of sms reception I have a chance to do that - there is exec config keyword. But dlr has to be handled via http. What is more - since sqlbox do the database registration without my intervention I do not need any drl handler. But not to have errors in kannel log I am forced to use http server. And having similar exec config parameter against dlr-url I could try to use dummy script like /bin/false or something like this which for sure would be faster. Better solution could be not to request delivery report when sending message and then there is no need for dlr handling at all. Hi, The exec script is another process started each time and is more expensive than attempting to fetch a dlr-url. The http server, initially takes up some resources (memory) but it remains constant and CPU utilization is overall lower. That's the whole purpose of the dlr-url. To get your dlrs in a databse in the format that you want. BR, Nikos - Original Message - From: dorian doria...@o2.pl mailto:doria...@o2.pl To: Alvaro Cornejo cornejo.alv...@gmail.com mailto:cornejo.alv...@gmail.com Cc: users@kannel.org mailto:users@kannel.org Sent: Friday, September 17, 2010 1:06 AM Subject: Re: sms - dlr bounding There is nothing magical in sqlbox. It sits between bearerbox and smsbox and it just records data in the database. Each message = 1 record in the table independetly if the message is
Re: sms - dlr bounding
Thanks, but it doesn't mater. It is probably the result that after copying I've manually edited the statement to make it more clear: to show that the dlr_url is non-url unique string. And your note is a little bit off-topic. The subject is that no DLR's records appears in the sent_sms table. You have a quote mismatch in that INSERT statement. -Original Message- From: dorian [mailto:doria...@o2.pl] Sent: Thursday, 07 October, 2010 08:32 To: Rene Kluwen Cc: 'Alejandro Guerrieri'; users@kannel.org Subject: Re: sms - dlr bounding Rene, Thanks a lot a lot for the advice. Recently I've found some time to test your idea. At the first glance it looked like great solution. I've used the following INSERT statement (php syntax) INSERT INTO send_sms (momt, sender, receiver, msgdata, sms_type, dlr_mask, dlr_url) VALUES ( 'MT', '8765', '.$phone_nr.', '.$txt.', 2, 31,'.$id); where $id contained unique id (but not url). For a moment it worked as expected. But now no DLRs are registered in the sms_sent table although I see the it is sent back from smsc. Any idea? I do not understand why for the first trials the DLRs has been stored into the table but now they are not. Dorian The thing that you might be looking for: If -instead of using smsbox- you use sqlbox to send messages, then you can set dlr-url to whatever you want. It doesn't necessarily have to be a http url. After that, you get your DLR's in the sent_sms table with the value you passed as drl-url. But since sqlbox doesn't call any http requests, as opposed to smsbox it just stays there in the table with boxc_id the same as you defined as sqlbox-id. Judging from your emails, I think this is what you want. == Rene -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of dorian Sent: Friday, 17 September, 2010 11:33 To: Alejandro Guerrieri Cc: users@kannel.org Subject: Re: sms - dlr bounding Well. I know the difference between fork and pthread_create. Anyway the http client work (even if it is thread not a process) is waste of time for me. Additionally I am forced to have working http server also which also do a silly work for me (taking CPU time and RAM). I am trying to find out the way to have dlr report but not to be forced to run http server since dlr reply is handled with sqlbox and it is enough for me. (on condition that I am able to bound sms with dlr) Dorian, Kannel uses threads. It doesn't fork. There's a _huge_ difference in terms of cost between a thread and fork. Using exec is a very bad idea in terms of performance and security. Regards, Alex On Fri, Sep 17, 2010 at 10:59 AM, dorian doria...@o2.pl mailto:doria...@o2.pl wrote: 1. See DEBUG line. Even if it is thread it takes time and RAM to create, the thread running take time preparing http request, my http server waste time to handle the request etc. 2. I need dlr feedback On Fri, 2010-09-17 at 09:26, dorian wrote: Right. But for http connection the kannel's clients is forked (at least it looks like according to the logs: 'DEBUG: HTTP: Creating HTTPClient'). Such fork is almost the same as exec'ing external process. How do you know it is fork? It could be thread or even simple function call. So I prefer exec my script rather than kannel's http client. This way the are no resources consumed by http server and the time needed for http request compose and parse is saved. In case of sms reception I have a chance to do that - there is exec config keyword. But dlr has to be handled via http. What is more - since sqlbox do the database registration without my intervention I do not need any drl handler. But not to have errors in kannel log I am forced to use http server. And having similar exec config parameter against dlr-url I could try to use dummy script like /bin/false or something like this which for sure would be faster. Better solution could be not to request delivery report when sending message and then there is no need for dlr handling at all. Hi, The exec script is another process started each time and is more expensive than attempting to fetch a dlr-url. The http server, initially takes up some resources (memory) but it remains constant and CPU utilization is overall lower. That's the whole purpose of the dlr-url. To get your dlrs in a databse in the format that you want. BR, Nikos - Original Message - From: dorian doria...@o2.pl mailto:doria...@o2.pl To: Alvaro Cornejo cornejo.alv...@gmail.com mailto:cornejo.alv...@gmail.com Cc: users@kannel.org
Re: kannel performance
This is not bb access log, but smsbox access log. It doesn't prove anyting, except that you have sent twice the same SMS. BR, Nikos - Original Message - From: dafodil neo.tu...@yahoo.com To: users@kannel.org Sent: Saturday, October 09, 2010 10:17 AM Subject: Re: kannel performance Hi Nikkos, Thanks again for ur time and support. I wil try with spool and fakesmsc and get back to you. but as usggested by you i had serious look at the logs and what makes sense to inform u is bellow findings. i m sending sms through http as bellow http://$kannelHost:$kannelPort/cgi-bin/sendsms?dlr=1dlr-mask=31dlr-url=$durlusername=$userNamepassword=$userPasswordfrom=$fromto=$totext=$msgsmsc=putty where $userName = daf; and $userPassword = daf; how ever in bearerbox access.log i see the folowing.for some numbers it adds send-SMS request added 2 times.and for other only once. bellow is an example where it is trying 2 times. 2010-10-06 12:13:21 send-SMS request added - sender:daf:daffodil 77.91.205.191 target:351919582869 request: 'kannel is a beautifull world 2010-10-06 12:12:43' 2010-10-06 12:13:21 send-SMS request added - sender:tester:daffodil 77.91.205.230 target:351919582869 request: 'kannel is a beautifull world 2010-10-06 12:12:43' and u can see my config as bellow group=sendsms-user username=daf password=daf user-allow-ip= *.*.*.* # SMSC HTTP group = smsc smsc = http msg-id-type=0x01 smsc-id = C system-type = kannel smsc-username = tester smsc-password = foobar port = 13015 connect-allow-ip = *.*.*.* send-url = http://daf.com:13013/cgi-bin/sendsms; # SMSC SMPP group = smsc smsc=smpp smsc-id=putty host=213.30.43.217 port=7677 transceiver-mode=true alt-charset=ISO-8859-1 msg-id-type=0x01 system-type=putty2 service-type=12664 address-range= max-pending-submits=10 smsc-username=putty smsc-password=putty12664 connect-allow-ip=*.*.*.* dest-addr-npi=1 dest-addr-ton=1 flow-control=0 log-file=/var/log/kannel/smsc.log log-level=3 wait-ack=120 wait-ack-expire=0x02 throughput=100 window=10 validityperiod = 10 Br Daf Nikos Balkanas wrote: Hi, 1) Test sending 1 sms using fakesmsc, as to avoid costs. Check storage status at end. 2) Spool is generally faster and more real-time than file for storage. Depends on fs parameters. 3) Resubmission is a problem, since it implies that smsc is not sending ACKs back. However, since you have specified to wait for an ACK indefinitely, it shouldn't resend the same sms again. I am assuming you are using the SMPP smsc. Try on sending a few SMS (~5), comment out log-file in smsc group and turn bb logs to maximum detail. Watch for anything unusual, especially ACKs. Post relevant portions if you get any problems. BR, Nikos - Original Message - From: dafodil neo.tu...@yahoo.com To: users@kannel.org Sent: Friday, October 08, 2010 8:44 PM Subject: Re: kannel performance Hi nikkos, just to add more operator says that kannel is senindg submit_sm for same number multiple times. Br daf Nikos Balkanas wrote: Hi, I don't think it is practical to set log-level to 0 for 10k SMS :-( How does it behave when sending just a few messages? Try changing store-type to spool. Describe test conditions. Were all of your smsc active during tests? BR, Nikos - Original Message - From: Willy Mularto sangpr...@gmail.com To: dafodil neo.tu...@yahoo.com Cc: users@kannel.org Sent: Friday, October 08, 2010 5:55 PM Subject: Re: kannel performance It would be helpful if you provide us your detailed log. Please set log-level to 0. sangprabv sangpr...@gmail.com http://www.petitiononline.com/froyo/ On Oct 8, 2010, at 6:54 PM, dafodil wrote: Hi List, Good Day. While stress testing with kannel i found the follwing.i was trying to send 10 k sms through HTTP/sendsms. storage internal queued grows to 230. kannel.store size keeps growing and now it seems to be 480,630,358. now i find a kannel.store.new is created with size more than 2000. my configuration are as bellow.I feel i have some wrong configuration. my provider does not have any problem and supports more than 100 sms/sec. my bearerbox size keeps growing.can any one suggest or guide me where i m wrong. all sms are not reaching smsc provider. group = core admin-port=13000 admin-password=xxx status-password=xxx sms-resend-retry = 1 sms-resend-freq = 120 admin-allow-ip=*.*.*.* log-level= 3 log-file = /var/log/kannel/bearerbox.log smsbox-port=13001 wapbox-port=13002 wdp-interface-name=* store-file=/var/log/kannel/kannel.store # SMSC FAKE group = smsc smsc-id = A smsc = fake port = 1 connect-allow-ip = *.*.*.* # SMSC SMPP group = smsc smsc=smpp smsc-id= host=222.22.22.222 port=7677 transceiver-mode=true alt-charset=ISO-8859-1 msg-id-type=0x01 system-type=xxx service-type=xxx address-range= max-pending-submits=10 smsc-username=xxx smsc-password=x connect-allow-ip=*.*.*.* dest-addr-npi=1 dest-addr-ton=1 flow-control=0 log-file=/var/log/kannel/mylog.log log-level=3
