RE: HTTPClient
Hi Thanks for the reply, but I find that msg-id-type does not work on version 1.4.3. No matter what the value for msg-id-type is set, the message ID is always written into the sql table as 0, so when the deliver_sm is received it is also convert to a 0 resulting in the first entry found in the mysql table being updated. I have tried all formats msg-id-type = 0x01 or 1 or 01 , even tried closing them in quotes. Also tried all possible 0x00, 0x01, 0x02 and 0x03. Regards Melvin From: Willy Mularto [mailto:sangpr...@gmail.com] Sent: 29 September 2014 03:53 AM To: Melvin Oberem Cc: kannel users@kannel.org Subject: Re: HTTPClient msg-id-type is your answer. Check user guide ;) Willy Mularto SMS Gateway, Content Provider, Mobile Solution Specialist M: +62811923464, +62818923464 PIN BBM: 74924429 On Sep 27, 2014, at 4:18 AM, Melvin Oberem obere...@telkomsa.net wrote: Hi I have been having problems with DLR reports because of submit_sm_resp being in hex and DLR deiver_sms being in decimal. I have been using kannel version 1.4.1 for many years without problems, but have now moved to a new SMSC, which the DLR conversion cannot be changed on the SMSC, and needs to be done on application. The DLR fix was patched in version 1.4.3 which I have tried to see if the msg-id-type configs work, but I am experiencing the following problem with version 1.4.3, the HTTPClient is created and immediately Destroyed, if coming in from a different server. I works if sent to the application on the same server. 2014-09-26 22:28:42 [14746] [2] DEBUG: HTTP: Creating HTTPClient for `10.101.101.10'. 2014-09-26 22:28:42 [14746] [2] DEBUG: HTTP: Created HTTPClient area d9248. 2014-09-26 22:28:42 [14746] [3] DEBUG: HTTP: Destroying HTTPClient area d9248. 2014-09-26 22:28:42 [14746] [3] DEBUG: HTTP: Destroying HTTPClient for `10.101.101.10'. I am using the same settings as per version 1.4.1 which works perfectly as per below. 2014-09-26 22:34:52 [17806] [2] DEBUG: HTTP: Creating HTTPClient for `10.101.101.10. 2014-09-26 22:34:52 [17806] [2] DEBUG: HTTP: Created HTTPClient area d6ec0. 2014-09-26 22:34:52 [17806] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 10.101.101.10 2014-09-26 22:34:52 [17806] [3] INFO: sendsms used by test 2014-09-26 22:34:52 [17806] [3] INFO: sendsms sender:test:08 (10.101.101.10) to:0812345678 msg:test 2014-09-26 22:34:52 [17806] [3] DEBUG: message length 4, sending 1 messages 2014-09-26 22:34:52 [17806] [3] DEBUG: Status: 202 Answer: Sent. 2014-09-26 22:34:52 [17806] [3] DEBUG: HTTP: Destroying HTTPClient area d6ec0. 2014-09-26 22:34:52 [17806] [3] DEBUG: HTTP: Destroying HTTPClient for `10.101.101.10. Has anybody seen this before and maybe have an answer. Regards Melvin
Re: Message identifier for returning DLR
Hi,
My DLRs are being buffered at Kannel and not hitting the URL specified in
dlr_url paratmeter in SQLBOX while sending SMS. Can someone please help to
figure out what's wrong? I am using following statement:
INSERT INTO `kannel`.`send_sms`
(momt,charset,coding,sender,receiver,msgdata,smsc_id,sms_type,dlr_mask,dlr_url)
VALUES ('MT','','','03xxyyy','03aabbb','Hello. This is test DLR
message.','my-smsc','2','63','
http://127.0.0.1/testdlr/dlr.php?dlrid=3status=%d')
The DLR is received by kannel/bearerbox successfully but kannel status
window shows it as buffered. It never hits the URL specified.
Is there some CGI parameter I am missing? The dlr.php file is on the right
path specified in the URL.
Regards,
Hamza
On Fri, Jun 13, 2014 at 11:41 PM, [Digital^Dude] ® millennium@gmail.com
wrote:
In your sendsms url just append dlr-url e.g.
http://kannel.host.com:/sendsms.cgi?user...dlr-mask=xdlr-url=[url
encoded form of url]
As you receive a dlr response, this dlr-url will be hit. Assuming your
dlr-url was the following:
http://another.host.com/myapi.py?status=%dmID=123tStamp=
You can grep for mID=123 and view its status in the web server logs of
another.host.com
Re: HTTPClient
Please dump the log-level to 0 and share us. Willy Mularto SMS Gateway, Content Provider, Mobile Solution Specialist M: +62811923464, +62818923464 PIN BBM: 74924429 On Sep 30, 2014, at 1:18 AM, Melvin Oberem obere...@telkomsa.net wrote: Hi Thanks for the reply, but I find that “msg-id-type” does not work on version 1.4.3. No matter what the value for msg-id-type is set, the message ID is always written into the sql table as “0”, so when the deliver_sm is received it is also convert to a “0” resulting in the first entry found in the mysql table being updated. I have tried all formats msg-id-type = 0x01 or 1 or 01 , even tried closing them in quotes. Also tried all possible 0x00, 0x01, 0x02 and 0x03. Regards Melvin From: Willy Mularto [mailto:sangpr...@gmail.com] Sent: 29 September 2014 03:53 AM To: Melvin Oberem Cc: kannel users@kannel.org Subject: Re: HTTPClient msg-id-type is your answer. Check user guide ;) Willy Mularto SMS Gateway, Content Provider, Mobile Solution Specialist M: +62811923464, +62818923464 PIN BBM: 74924429 On Sep 27, 2014, at 4:18 AM, Melvin Oberem obere...@telkomsa.net wrote: Hi I have been having problems with DLR reports because of submit_sm_resp being in hex and DLR deiver_sms being in decimal. I have been using kannel version 1.4.1 for many years without problems, but have now moved to a new SMSC, which the DLR conversion cannot be changed on the SMSC, and needs to be done on application. The DLR fix was patched in version 1.4.3 which I have tried to see if the msg-id-type configs work, but I am experiencing the following problem with version 1.4.3, the HTTPClient is created and immediately Destroyed, if coming in from a different server. I works if sent to the application on the same server. 2014-09-26 22:28:42 [14746] [2] DEBUG: HTTP: Creating HTTPClient for `10.101.101.10'. 2014-09-26 22:28:42 [14746] [2] DEBUG: HTTP: Created HTTPClient area d9248. 2014-09-26 22:28:42 [14746] [3] DEBUG: HTTP: Destroying HTTPClient area d9248. 2014-09-26 22:28:42 [14746] [3] DEBUG: HTTP: Destroying HTTPClient for `10.101.101.10'. I am using the same settings as per version 1.4.1 which works perfectly as per below. 2014-09-26 22:34:52 [17806] [2] DEBUG: HTTP: Creating HTTPClient for `10.101.101.10. 2014-09-26 22:34:52 [17806] [2] DEBUG: HTTP: Created HTTPClient area d6ec0. 2014-09-26 22:34:52 [17806] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 10.101.101.10 2014-09-26 22:34:52 [17806] [3] INFO: sendsms used by test 2014-09-26 22:34:52 [17806] [3] INFO: sendsms sender:test:08 (10.101.101.10) to:0812345678 msg:test 2014-09-26 22:34:52 [17806] [3] DEBUG: message length 4, sending 1 messages 2014-09-26 22:34:52 [17806] [3] DEBUG: Status: 202 Answer: Sent. 2014-09-26 22:34:52 [17806] [3] DEBUG: HTTP: Destroying HTTPClient area d6ec0. 2014-09-26 22:34:52 [17806] [3] DEBUG: HTTP: Destroying HTTPClient for `10.101.101.10. Has anybody seen this before and maybe have an answer. Regards Melvin
Fwd: getting max 10 tps from single smpp session
Hi, I am Rajeev, I am using Kannel from past 2 years. I am having 2 servers of kannel with following specs: Kannel bearerbox version `svn-r5106'. Build `Sep 30 2014 01:09:31', compiler `4.4.7 20120313 (Red Hat 4.4.7-4)'. System Linux, release 2.6.32-431.20.3.el6.x86_64, version #1 SMP Thu Jun 19 21:14:45 UTC 2014, machine x86_64. Hostname xx.x, IP xxx.xxx.xxx.xxx. Libxml version 2.7.6. Using OpenSSL 1.0.1e-fips 11 Feb 2013. Compiled with MySQL 5.5.38, using MySQL 5.5.38. Using native malloc. 1. at Digital Ocean VPS(SINGLE CORE 512 MB RAM 20GB HDD) 2. My Office Premises (hp proliant Intel® Xeon® E3-1220 v2 (4 core, 3.4 GHz, 8MB), 1TB 4 GB RAM. My Problem: VPS is giving me a total of 150 tps with 4 sessions. But my office server is giving me max 30 tps with (4 sessions above). Max 10 tps from each session. I installed kannel on as many as 6 diff servers in vps, there I am getting 150 tps at any vps. But I am restricted to 10 tps per session max 30tps from my office server. kannel config, version, mysql all are same in all machines. Kannel config: group = core admin-port = 13000 smsbox-port = 13001 admin-password = 12345 #status-password = foo #admin-deny-ip = #admin-allow-ip = log-file = /var/log/kannel/log.log log-level = 2 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 #unified-prefix = +358,00358,0;+,00 #access-log = /tmp/access.log #store-file = /var/log/kannel/kannel.store #store-type=file #store-location=/var/log/kannel/kannelspool #ssl-server-cert-file = cert.pem #ssl-server-key-file = key.pem #ssl-certkey-file = mycertandprivkeyfile.pem dlr-storage=mysql store-type = spool store-location = /var/log/kannel/spool/ smsbox-max-pending=1 #- # SMSC CONNECTIONS ##aman promo sid trx 1 group = smsc smsc = smpp smsc-id = amanps host=00 port = transceiver-mode = true #receive-port= smsc-username=abcd smsc-password=abcd system-type=VMA #system-id=9 allowed-smsc-id = 111222 #denied-smsc-id = 2;4;5;6;7;8;9;10 enquire-link-interval=120 #reconnect-delay = 10 validityperiod = 32123 interface-version=34 max-pending-submits=1 #- # 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=smsbox1 bearerbox-host = 127.0.0.1 sendsms-port = 13013 global-sender = 13013 #sendsms-chars = 0123456789 +- #log-file = /tmp/smsbox.log #log-level = 0 #access-log = /tmp/access.log #mysql connection group = mysql-connection id = sqlbox-db host = 00 username = kannel password = kannel database =kannel max-connections = 5 # DLR SETUP #mysql connection group = mysql-connection id = mydlr host = x username = kannel password = kannel database = kannel max-connections = 5 group = dlr-db id = mydlr table=smpp_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 Please help me in this issue. Thanks.
