get notify if SMSC link is online¨?
Hi guys! I need some urgent help from you all!! follow situation: is there a way the gateway can send notification in case he detects that the link to the SMSC (provider) is online again? PLIIIS HELP thanks in advance! -- GMX.ch - Schweizer FreeMail-Dienst mit über 800.000 Mitgliedern E-Mail mehr! Kostenlos: http://portal.gmx.net/de/go/chfreemail
Re: get notify if SMSC link is online�?
No. The gateway doesn't have a notification mechanism. You should use a monitoring tool that either parses logs or the HTTP admin status page. BR, Nikos - Original Message - From: Beatrice Tamburrino beatrice.tamburr...@gmx.ch To: users@kannel.org Sent: Wednesday, August 25, 2010 12:42 PM Subject: get notify if SMSC link is online¨? Hi guys! I need some urgent help from you all!! follow situation: is there a way the gateway can send notification in case he detects that the link to the SMSC (provider) is online again? PLIIIS HELP thanks in advance! -- GMX.ch - Schweizer FreeMail-Dienst mit ΓΌber 800.000 Mitgliedern E-Mail mehr! Kostenlos: http://portal.gmx.net/de/go/chfreemail
Re: get notify if SMSC link is o nline¨?
There is a kannel plugin for Nagios http://exchange.nagios.org/directory/Plugins/Others/check_kannel/details BR - Original Message - From: Beatrice Tamburrino beatrice.tamburr...@gmx.ch To: users@kannel.org Sent: Wednesday, August 25, 2010 10:42 AM Subject: get notify if SMSC link is online¨? Hi guys! I need some urgent help from you all!! follow situation: is there a way the gateway can send notification in case he detects that the link to the SMSC (provider) is online again? PLIIIS HELP thanks in advance! -- GMX.ch - Schweizer FreeMail-Dienst mit über 800.000 Mitgliedern E-Mail mehr! Kostenlos: http://portal.gmx.net/de/go/chfreemail
Re: get notify if SMSC link is online¨?
hey thank you for your feedback! Cezary, thanks for your input.. so the only way to get the information about the SMSC is through the status.xml.? right? Original-Nachricht Datum: Wed, 25 Aug 2010 11:12:40 +0100 Von: Cezary Siwek cza...@thebestisp.co.uk An: Beatrice Tamburrino beatrice.tamburr...@gmx.ch, users@kannel.org Betreff: Re: get notify if SMSC link is online¨? There is a kannel plugin for Nagios http://exchange.nagios.org/directory/Plugins/Others/check_kannel/details BR - Original Message - From: Beatrice Tamburrino beatrice.tamburr...@gmx.ch To: users@kannel.org Sent: Wednesday, August 25, 2010 10:42 AM Subject: get notify if SMSC link is online¨? Hi guys! I need some urgent help from you all!! follow situation: is there a way the gateway can send notification in case he detects that the link to the SMSC (provider) is online again? PLIIIS HELP thanks in advance! -- GMX.ch - Schweizer FreeMail-Dienst mit über 800.000 Mitgliedern E-Mail mehr! Kostenlos: http://portal.gmx.net/de/go/chfreemail -- GMX.ch - Schweizer FreeMail-Dienst mit über 800.000 Mitgliedern E-Mail mehr! Kostenlos: http://portal.gmx.net/de/go/chfreemail
Help on Kannel configuration
Hi All, I'm new user of kannel, and this is my use case; I want to use kannel server to receive sms (bulk data students' weekly performance data ) from schools in a particular locality to the Local Government education resource centre, and also from the LG resource centre to the state education resource centre. The data from each school to LG resource center is the only one that need be via sms other data transport from LG to State etc can be via wap or HTTP,because supporting infrastructure could be available at this locations. Thank you! David
RE: service works with SMPPsim and not with real smsc
Could you post your current configuration files? == Rene From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of gasmen Sent: Wednesday, 25 August, 2010 14:39 To: users@kannel.org Subject: service works with SMPPsim and not with real smsc HI all i am using kannel 1.4.3 and i am excuting servlet with group sms-service it works good and it call the servlet when i use the SMMPsim but just i change the configuration of smsc group to work with real smsc message come to the mobile phone but it didnt call the servlet ... so i am looking for your help maybe i will add some configuration the groups to start the service with the real smsc!!! thanks a lot _ View this message in context: service http://old.nabble.com/service-works-with-SMPPsim-and-not-with-real-smsc-tp2 9531805p29531805.html works with SMPPsim and not with real smsc Sent from the Kannel http://old.nabble.com/Kannel---User-f14436.html - User mailing list archive at Nabble.com.
mtbatch usage
Hello, I need instructions on how to use mtbatch for batch processing. The man page information is not enough. An example would help me understand faster. Thanks, Peter.
Re: Problem with Regular Expressions
Hi, Please post relevant smsbox logs at maximum detail (level = 0). Also post your whole configuration. BR, Nikos - Original Message - From: Cariotoglou Mike m...@singular.gr To: users@kannel.org Sent: Wednesday, August 25, 2010 8:22 PM Subject: Problem with Regular Expressions Hi, I am new to Kannel. I am using 1.4.3 on Ubuntu 10.04 Server. I am trying to set up an SMS gateway, which will connect to smsc using SMPP. before actually connecting to the smsc, I am testing locally, using fakesmsc. The problem I am having is that the keyword-regex variable does not seem to be working as documented. specifically : the SMS message I am trying to match looks like this : SLGx (no spaces at all, a single string) This configuration seems to work, although there is no SLG word in the message, assuming that word implies space-delimiters: group = sms-service name = SLG keyword = SLG text = Hi there,SLG catch-all = true although it shouldn't work, IMHO! (it should work for SLG 123, but not for SLG123, yet it does) this configuration, which is the one I want, does not work at all: group = sms-service name = SLG keyword-regex = ^SLG[0-9]+ text = Hi there,SLG catch-all = true according to my understanding of regular expressions, this should match SLG123, and NOT match SLG. it actually matches NOTHING. Could you please explain why, and, in general, how can I match a message that STARTS with a pattern, but does NOT contain any word delimiters ? Mike
Re: Help on Kannel configuration
Sure, start with kannel.conf under doc/examples. To understand it check UG. BR, Nikos - Original Message - From: ayokunle odusanya To: Nikos Balkanas Cc: david ally ; users@kannel.org Sent: Wednesday, August 25, 2010 5:14 PM Subject: Re: Help on Kannel configuration Hi, I understand how daunting the configurations parameters can be for a new user, but I'm sure you can have a sample configuration file to work with right away (in the most needed parameters) in the source files of kannel. 2010/8/25 Nikos Balkanas nbalka...@gmail.com Hi, You should start from User's guide at www.kannel.org. It has plenty of configuration examples. BR, Nikos - Original Message - From: david ally To: users@kannel.org Sent: Wednesday, August 25, 2010 3:11 PM Subject: Help on Kannel configuration Hi All, I'm new user of kannel, and this is my use case; I want to use kannel server to receive sms (bulk data students' weekly performance data ) from schools in a particular locality to the Local Government education resource centre, and also from the LG resource centre to the state education resource centre. The data from each school to LG resource center is the only one that need be via sms other data transport from LG to State etc can be via wap or HTTP,because supporting infrastructure could be available at this locations. Thank you! David -- Ayokunle Odusanya
Re: Kannel queue with same priority is unpredictable
Wow! Did you sent all these through a real SMSc? It must have costed a bundle. Use fakesmpp for the tests to avoid charges. Will need also relevant bb logs and your configuration. BR, Nikos - Original Message - From: Jason Mule To: Nikos Balkanas Cc: Alejandro Guerrieri ; users@kannel.org Sent: Wednesday, August 25, 2010 4:19 PM Subject: Re: Kannel queue with same priority is unpredictable I have reproduced this by sending 1 messages in 2 sets to simulate a large MT-Push. Please note the sequence of messages in 'smsboxaccess0.log' and compare this to 'access.log'. Messages with the string 'Message 2' were sent after messages with the string 'Message 1'. 2010/8/25 Nikos Balkanas nbalka...@gmail.com And i am saying the same thing to you: Please share relevant log entries demonstrating this. BR, Nikos - Original Message - From: Jason Mule jason.m...@gmail.com To: Nikos Balkanas nbalka...@gmail.com Cc: Alejandro Guerrieri alejandro.guerri...@gmail.com; users@kannel.org Sent: Tuesday, August 24, 2010 4:09 PM Subject: Re: Kannel queue with same priority is unpredictable Hi, I have observed that as long as there are messages in the store file en route to the SMSC, newer MTs to Kannel will be sent out before the bunch of messages in the store file. Priority is not changed for the newer messages and the messages are not retries. This is probably what the OP was referring to. 2010/7/20 Nikos Balkanas nbalka...@gmail.com: Thanks. It turns that priority queue in kannel is dtermined both by SMS priority and age of sms. I.e. if 2 sms have the same priority, the older one gets the call (FIFO). It is also implemented only in SMPP, EMI at. BR, Nikos - Original Message - From: Alejandro Guerrieri To: Nikos Balkanas Cc: Waqas Farooq ; users@kannel.org Sent: Tuesday, July 20, 2010 4:11 PM Subject: Re: Kannel queue with same priority is unpredictable That's not correct. At least on SVN for a good time now, Kannel honors priorities, being 3 the highest and 0 the lowest. That means that if you have a big queue of priority-1 messages and send one priority-2 or 3 message, it will get delivered before the rest of the queue. The priority is also passed to the SMSC by means of SMPP's priority flag, but afaik most carriers ignore ESME settings for priority so do not expect it to work. Regards, Alex 2010/7/20 Nikos Balkanas nbalka...@gmail.com Hi, Priority is not used by kannel. It is part of the SMPP spec and is passed to receiving SMSc. Queue is FIFO, subject to constraints like sms-resend-freq and sms-resend-retry. If in doubt check store-queue from http admin. BR, Nikos - Original Message - From: Waqas Farooq To: users@kannel.org Sent: Tuesday, July 20, 2010 11:48 AM Subject: Kannel queue with same priority is unpredictable Hi All, I have a very large queue with all the messages in the queue and the new incoming messages from the smsbox are with the same priority. The problem is that new messages get delivered earlier than the ones already queued. I have no idea what sort of queue it is? Is it a FIFO queue or the kannel just tries to send the messages from the smsbox directly if possible and if not then the message is queued? Please note that all the messages are at the same priority! Any help will be highly appreciated! Thanks, Waqas Hotmail: Trusted email with powerful SPAM protection. Sign up now. BR, Jason BR, Jason
Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP
Hello Nikos, Can you please explain this below Line. *2010-08-25 13:01:27 [6057] [0] INFO: DLR rerouting for smsc id vFirstDEMO disabled.* One more thing by adding *dlr-mask=31* i got the DLR but i got only below params, But i want to add a custom column, which i will add while sending message by which i could Query into this table for DLRs. id smsc timestamp destination source service url mask status boxc_id 1 vFirstDEMO -00-00 00:00:00 9216217231 anshu kannel 31 0 4 vFirstDEMO 3410267477 9781114229 anshu kannel 31 0 Regards Anshu On Tue, Aug 17, 2010 at 6:55 PM, Rene Kluwen rene.klu...@chimit.nl wrote: See this post from Nikos. -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Nikos Balkanas Sent: Monday, 16 August, 2010 22:55 To: Anshu Sah; users@kannel.org Subject: Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hi, Please post your sendsms URL and detailed bb logs of an attempt to send an MT. BR, Nikos - Original Message - From: Anshu Sah To: users@kannel.org Sent: Monday, August 16, 2010 10:39 PM Subject: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hello I am unable to receive DLR in Kannel using SMPP Connectivity., Please guide. If i am doing something wrong, Regards Anshu Configuration is below group = core admin-port = 13000 smsbox-port = 13001 admin-password = bar log-file = /projects/kannel/logs/core.log log-level = 0 #box-deny-ip = *.*.*.* #box-allow-ip = 127.0.0.1 dlr-storage = mysql access-log = /projects/kannel/logs/access.log #store-file = /projects/kannel/logs/storefile.log #dlr-storage = internal group=smsc smsc=smpp smsc-id=x host = xx port = 2345 receive-port = 2345 log-file = /projects/kannel/logs/smsc.log log-level = 0 smsc-username = x smsc-password = xxx msg-id-type = 0x01 transceiver-mode=1 system-type = 'VMA' #service-type = 'test' interface-version = 34 address-range = '' #msg-id-type = 0 group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 log-level = 0 group = sendsms-user username = kannel password = hard2guess concatenation = true max-messages = 3 #--- mysql connection group = mysql-connection id = mydlr host = localhost username = xx password = xxx database = kannel max-connections = 1 # DLR table structure group = dlr-db id = mydlr table = kannel_dlr field-smsc = smsc field-timestamp = timestamp field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxc_id LOGS [r...@splash gw]# ./bearerbox /projects/kannel/configs/x.inc 2010-08-16 13:15:49 [32566] [0] INFO: Debug_lvl = -1, log_file = none, log_lvl = 0 2010-08-16 13:15:49 [32566] [0] INFO: MYSQL: Connected to server at localhost. 2010-08-16 13:15:49 [32566] [0] INFO: MYSQL: server version 5.0.77, client version 5.0.77. 2010-08-16 13:15:49 [32566] [0] INFO: DLR using storage type: mysql 2010-08-16 13:15:49 [32566] [0] DEBUG: Kannel bearerbox version `1.4.3'. Build `Aug 15 2010 18:31:17', compiler `4.1.2 20080704 (Red Hat 4.1.2-48)'. System Linux, release 2.6.18-194.8.1.el5.028stab070.2, version #1 SMP Tue Jul 6 14:55:39 MSD 2010, machine i686. Hostname x. Libxml version 2.6.26. Using OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008. Compiled with MySQL 5.0.77, using MySQL 5.0.77. Using native malloc. 2010-08-16 13:15:49 [32566] [0] INFO: Added logfile `/projects/kannel/logs/core.log' with level `0'. 2010-08-16 13:15:49 [32566] [0] INFO: Started access logfile `/projects/kannel/logs/access.log'. 2010-08-16 13:15:49 [32566] [0] INFO: HTTP: Opening server at port 13000. 2010-08-16 13:15:49 [32566] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2010-08-16 13:15:49 [32566] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2010-08-16 13:15:49 [32566] [0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run) 2010-08-16 13:15:49 [32566] [0] DEBUG: starting smsbox connection module 2010-08-16 13:15:49 [32566] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100). 2010-08-16 13:15:49 [32566] [0] DEBUG: Started thread 4 (gw/bb_boxc.c:sms_to_smsboxes) 2010-08-16 13:15:49 [32566] [0] DEBUG: Started thread 5 (gw/bb_boxc.c:smsboxc_run) 2010-08-16 13:15:49 [32566] [0] INFO: Set SMS resend frequency to 60 seconds. 2010-08-16 13:15:49 [32566] [0] INFO: SMS resend retry set to unlimited. 2010-08-16 13:15:49 [32566] [0] DEBUG: smsbox MO concatenated message handling enabled 2010-08-16 13:15:49 [32566] [0] INFO: DLR rerouting for smsc id vFirstDEMO disabled. 2010-08-16 13:15:49 [32566] [0] INFO: Added logfile `/projects/kannel/logs/smsc.log' with level `0'. 2010-08-16 13:15:49 [32566] [0] DEBUG: Started thread 6 (gw/smsc/smsc_smpp.c:io_thread) 2010-08-16 13:15:49 [32566] [1] DEBUG: Thread 1
RE: help on mysql database
Everything should be in the users manual that is available on http://www.kannel.org/. In case you have specific questions, please post them along with your current configuration files. == Rene From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of mac...@fastermail.com Sent: Wednesday, 25 August, 2010 18:34 To: users@kannel.org Subject: help on mysql database Hi Folks I installed kannel using an rpm package on fedora core 13 but i would appreciate anyone who has had experiance of implementing kannel with mysql due to the nature of my project.Please provide me with the necessary steps that you undertook to communicate with the database server in the subject above.
RE: Problem with Regular Expressions
According to your regexp: ^SLG[0-9]+, there is not space in between SLG and the number. Shouldn't it be: ^SLG [0-9]+? (with a space). == Rene -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Cariotoglou Mike Sent: Wednesday, 25 August, 2010 19:22 To: users@kannel.org Subject: Problem with Regular Expressions Hi, I am new to Kannel. I am using 1.4.3 on Ubuntu 10.04 Server. I am trying to set up an SMS gateway, which will connect to smsc using SMPP. before actually connecting to the smsc, I am testing locally, using fakesmsc. The problem I am having is that the keyword-regex variable does not seem to be working as documented. specifically : the SMS message I am trying to match looks like this : SLGx (no spaces at all, a single string) This configuration seems to work, although there is no SLG word in the message, assuming that word implies space-delimiters: group = sms-service name = SLG keyword = SLG text = Hi there,SLG catch-all = true although it shouldn't work, IMHO! (it should work for SLG 123, but not for SLG123, yet it does) this configuration, which is the one I want, does not work at all: group = sms-service name = SLG keyword-regex = ^SLG[0-9]+ text = Hi there,SLG catch-all = true according to my understanding of regular expressions, this should match SLG123, and NOT match SLG. it actually matches NOTHING. Could you please explain why, and, in general, how can I match a message that STARTS with a pattern, but does NOT contain any word delimiters ? Mike
Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP
Hi, For info read UG about reroute-smsc. Once you reroute that, you may also want to reroute its DLRs. Since you don't, you don't need to. Just ignore it. I see you are using a DB for dlr-storage (mysql)?. This table is for internal processing only. DLR is deleted once it is matched. If you want permanent DLR storage, use your own web application, and use dlr-url. Filed timestamp is really SMSc forreign id and should be varchar(64). BR, Nikos - Original Message - From: Anshu Sah To: Rene Kluwen Cc: Nikos Balkanas ; users@kannel.org Sent: Wednesday, August 25, 2010 11:55 PM Subject: Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hello Nikos, Can you please explain this below Line. 2010-08-25 13:01:27 [6057] [0] INFO: DLR rerouting for smsc id vFirstDEMO disabled. One more thing by adding dlr-mask=31 i got the DLR but i got only below params, But i want to add a custom column, which i will add while sending message by which i could Query into this table for DLRs. id smsc timestamp destination source service url mask status boxc_id 1vFirstDEMO-00-00 00:00:009216217231anshukannel 310 4vFirstDEMO34102674779781114229anshukannel 310 Regards Anshu On Tue, Aug 17, 2010 at 6:55 PM, Rene Kluwen rene.klu...@chimit.nl wrote: See this post from Nikos. -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Nikos Balkanas Sent: Monday, 16 August, 2010 22:55 To: Anshu Sah; users@kannel.org Subject: Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hi, Please post your sendsms URL and detailed bb logs of an attempt to send an MT. BR, Nikos - Original Message - From: Anshu Sah To: users@kannel.org Sent: Monday, August 16, 2010 10:39 PM Subject: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hello I am unable to receive DLR in Kannel using SMPP Connectivity., Please guide. If i am doing something wrong, Regards Anshu Configuration is below group = core admin-port = 13000 smsbox-port = 13001 admin-password = bar log-file = /projects/kannel/logs/core.log log-level = 0 #box-deny-ip = *.*.*.* #box-allow-ip = 127.0.0.1 dlr-storage = mysql access-log = /projects/kannel/logs/access.log #store-file = /projects/kannel/logs/storefile.log #dlr-storage = internal group=smsc smsc=smpp smsc-id=x host = xx port = 2345 receive-port = 2345 log-file = /projects/kannel/logs/smsc.log log-level = 0 smsc-username = x smsc-password = xxx msg-id-type = 0x01 transceiver-mode=1 system-type = 'VMA' #service-type = 'test' interface-version = 34 address-range = '' #msg-id-type = 0 group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 log-level = 0 group = sendsms-user username = kannel password = hard2guess concatenation = true max-messages = 3 #--- mysql connection group = mysql-connection id = mydlr host = localhost username = xx password = xxx database = kannel max-connections = 1 # DLR table structure group = dlr-db id = mydlr table = kannel_dlr field-smsc = smsc field-timestamp = timestamp field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxc_id LOGS [r...@splash gw]# ./bearerbox /projects/kannel/configs/x.inc 2010-08-16 13:15:49 [32566] [0] INFO: Debug_lvl = -1, log_file = none, log_lvl = 0 2010-08-16 13:15:49 [32566] [0] INFO: MYSQL: Connected to server at localhost. 2010-08-16 13:15:49 [32566] [0] INFO: MYSQL: server version 5.0.77, client version 5.0.77. 2010-08-16 13:15:49 [32566] [0] INFO: DLR using storage type: mysql 2010-08-16 13:15:49 [32566] [0] DEBUG: Kannel bearerbox version `1.4.3'. Build `Aug 15 2010 18:31:17', compiler `4.1.2 20080704 (Red Hat 4.1.2-48)'. System Linux, release 2.6.18-194.8.1.el5.028stab070.2, version #1 SMP Tue Jul 6 14:55:39 MSD 2010, machine i686. Hostname x. Libxml version 2.6.26. Using OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008. Compiled with MySQL 5.0.77, using MySQL 5.0.77. Using native malloc. 2010-08-16 13:15:49 [32566] [0] INFO: Added logfile `/projects/kannel/logs/core.log' with level `0'. 2010-08-16 13:15:49 [32566] [0] INFO: Started access logfile `/projects/kannel/logs/access.log'. 2010-08-16 13:15:49 [32566] [0] INFO: HTTP: Opening server at port 13000. 2010-08-16 13:15:49 [32566] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2010-08-16 13:15:49 [32566] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2010-08-16 13:15:49 [32566] [0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run) 2010-08-16 13:15:49 [32566] [0] DEBUG: starting smsbox connection module 2010-08-16 13:15:49 [32566] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100). 2010-08-16 13:15:49 [32566] [0] DEBUG: Started thread 4 (gw/bb_boxc.c:sms_to_smsboxes) 2010-08-16 13:15:49 [32566] [0] DEBUG: Started thread 5 (gw/bb_boxc.c:smsboxc_run) 2010-08-16 13:15:49 [32566] [0] INFO: Set SMS resend frequency to 60
Re: How does Kannel handle DLRs from multiple binds to the same SMSC
Please post configuration. BR, Nikos - Original Message - From: brett skinner To: Users Sent: Wednesday, August 25, 2010 11:09 PM Subject: How does Kannel handle DLRs from multiple binds to the same SMSC Hi In an effort to increase through put our SMSC suggested that we created another bind to them with the exact same details. I.e. username, password, IP address and port. In our configuration file I have created a second bind with a different ID but have set both SMPP connections to use the same allowed-smsc-id. The SMSC did mention that they would load balance the DLRs across the binds and feed to which ever bind had the least traffic. Looking through the bearerbox logs I don't not see any rejected DLRs. But we are missing an unusally large number of DLRs. Were we incorrect in our assumption that Kannel would be able to match the DLRs even if the original sms went out on one bind and came back in on another bind? Regards,
RE: Kannel queue with same priority is unpredictable
If you send all of those messages at once, I don't know how priority queues behave. If priority is the same and the time that messages are sent are within the same second. What do priority queues do? == Rene -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Nikos Balkanas Sent: Wednesday, 25 August, 2010 21:47 To: Jason Mule Cc: users@kannel.org Subject: Re: Kannel queue with same priority is unpredictable Wow! Did you sent all these through a real SMSc? It must have costed a bundle. Use fakesmpp for the tests to avoid charges. Will need also relevant bb logs and your configuration. BR, Nikos - Original Message - From: Jason Mule To: Nikos Balkanas Cc: Alejandro Guerrieri ; users@kannel.org Sent: Wednesday, August 25, 2010 4:19 PM Subject: Re: Kannel queue with same priority is unpredictable I have reproduced this by sending 1 messages in 2 sets to simulate a large MT-Push. Please note the sequence of messages in 'smsboxaccess0.log' and compare this to 'access.log'. Messages with the string 'Message 2' were sent after messages with the string 'Message 1'. 2010/8/25 Nikos Balkanas nbalka...@gmail.com And i am saying the same thing to you: Please share relevant log entries demonstrating this. BR, Nikos - Original Message - From: Jason Mule jason.m...@gmail.com To: Nikos Balkanas nbalka...@gmail.com Cc: Alejandro Guerrieri alejandro.guerri...@gmail.com; users@kannel.org Sent: Tuesday, August 24, 2010 4:09 PM Subject: Re: Kannel queue with same priority is unpredictable Hi, I have observed that as long as there are messages in the store file en route to the SMSC, newer MTs to Kannel will be sent out before the bunch of messages in the store file. Priority is not changed for the newer messages and the messages are not retries. This is probably what the OP was referring to. 2010/7/20 Nikos Balkanas nbalka...@gmail.com: Thanks. It turns that priority queue in kannel is dtermined both by SMS priority and age of sms. I.e. if 2 sms have the same priority, the older one gets the call (FIFO). It is also implemented only in SMPP, EMI at. BR, Nikos - Original Message - From: Alejandro Guerrieri To: Nikos Balkanas Cc: Waqas Farooq ; users@kannel.org Sent: Tuesday, July 20, 2010 4:11 PM Subject: Re: Kannel queue with same priority is unpredictable That's not correct. At least on SVN for a good time now, Kannel honors priorities, being 3 the highest and 0 the lowest. That means that if you have a big queue of priority-1 messages and send one priority-2 or 3 message, it will get delivered before the rest of the queue. The priority is also passed to the SMSC by means of SMPP's priority flag, but afaik most carriers ignore ESME settings for priority so do not expect it to work. Regards, Alex 2010/7/20 Nikos Balkanas nbalka...@gmail.com Hi, Priority is not used by kannel. It is part of the SMPP spec and is passed to receiving SMSc. Queue is FIFO, subject to constraints like sms-resend-freq and sms-resend-retry. If in doubt check store-queue from http admin. BR, Nikos - Original Message - From: Waqas Farooq To: users@kannel.org Sent: Tuesday, July 20, 2010 11:48 AM Subject: Kannel queue with same priority is unpredictable Hi All, I have a very large queue with all the messages in the queue and the new incoming messages from the smsbox are with the same priority. The problem is that new messages get delivered earlier than the ones already queued. I have no idea what sort of queue it is? Is it a FIFO queue or the kannel just tries to send the messages from the smsbox directly if possible and if not then the message is queued? Please note that all the messages are at the same priority! Any help will be highly appreciated! Thanks, Waqas Hotmail: Trusted email with powerful SPAM protection. Sign up now. BR, Jason BR, Jason
Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP
Hello Nikos, If the DLRs which are coming to MySQL is temporary, Then i can also use DLR storage Internal, and Make a SMALL application to sense DLRs. i am confused is there any Key Or any Value by which we can compare that the coming DLR is for any specfic Message Sent. for example : While Sending SMS I get only text 0: Accepted for delivery But if i get *message ID* here while sending same *message ID* is returned as value when i get DLR, i can match DLR with Sent message easily in my table. Hope that *message ID is an Unqiue *value. Regards, Anshu 2010/8/26 Nikos Balkanas nbalka...@gmail.com Hi, For info read UG about reroute-smsc. Once you reroute that, you may also want to reroute its DLRs. Since you don't, you don't need to. Just ignore it. I see you are using a DB for dlr-storage (mysql)?. This table is for internal processing only. DLR is deleted once it is matched. If you want permanent DLR storage, use your own web application, and use dlr-url. Filed timestamp is really SMSc forreign id and should be varchar(64). BR, Nikos - Original Message - From: Anshu Sah To: Rene Kluwen Cc: Nikos Balkanas ; users@kannel.org Sent: Wednesday, August 25, 2010 11:55 PM Subject: Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hello Nikos, Can you please explain this below Line. 2010-08-25 13:01:27 [6057] [0] INFO: DLR rerouting for smsc id vFirstDEMO disabled. One more thing by adding dlr-mask=31 i got the DLR but i got only below params, But i want to add a custom column, which i will add while sending message by which i could Query into this table for DLRs. id smsc timestamp destination source service url mask status boxc_id 1vFirstDEMO-00-00 00:00:009216217231anshukannel 310 4vFirstDEMO34102674779781114229anshukannel 310 Regards Anshu On Tue, Aug 17, 2010 at 6:55 PM, Rene Kluwen rene.klu...@chimit.nl wrote: See this post from Nikos. -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Nikos Balkanas Sent: Monday, 16 August, 2010 22:55 To: Anshu Sah; users@kannel.org Subject: Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hi, Please post your sendsms URL and detailed bb logs of an attempt to send an MT. BR, Nikos - Original Message - From: Anshu Sah To: users@kannel.org Sent: Monday, August 16, 2010 10:39 PM Subject: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hello I am unable to receive DLR in Kannel using SMPP Connectivity., Please guide. If i am doing something wrong, Regards Anshu Configuration is below group = core admin-port = 13000 smsbox-port = 13001 admin-password = bar log-file = /projects/kannel/logs/core.log log-level = 0 #box-deny-ip = *.*.*.* #box-allow-ip = 127.0.0.1 dlr-storage = mysql access-log = /projects/kannel/logs/access.log #store-file = /projects/kannel/logs/storefile.log #dlr-storage = internal group=smsc smsc=smpp smsc-id=x host = xx port = 2345 receive-port = 2345 log-file = /projects/kannel/logs/smsc.log log-level = 0 smsc-username = x smsc-password = xxx msg-id-type = 0x01 transceiver-mode=1 system-type = 'VMA' #service-type = 'test' interface-version = 34 address-range = '' #msg-id-type = 0 group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 log-level = 0 group = sendsms-user username = kannel password = hard2guess concatenation = true max-messages = 3 #--- mysql connection group = mysql-connection id = mydlr host = localhost username = xx password = xxx database = kannel max-connections = 1 # DLR table structure group = dlr-db id = mydlr table = kannel_dlr field-smsc = smsc field-timestamp = timestamp field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxc_id LOGS [r...@splash gw]# ./bearerbox /projects/kannel/configs/x.inc 2010-08-16 13:15:49 [32566] [0] INFO: Debug_lvl = -1, log_file = none, log_lvl = 0 2010-08-16 13:15:49 [32566] [0] INFO: MYSQL: Connected to server at localhost. 2010-08-16 13:15:49 [32566] [0] INFO: MYSQL: server version 5.0.77, client version 5.0.77. 2010-08-16 13:15:49 [32566] [0] INFO: DLR using storage type: mysql 2010-08-16 13:15:49 [32566] [0] DEBUG: Kannel bearerbox version `1.4.3'. Build `Aug 15 2010 18:31:17', compiler `4.1.2 20080704 (Red Hat 4.1.2-48)'. System Linux, release 2.6.18-194.8.1.el5.028stab070.2, version #1 SMP Tue Jul 6 14:55:39 MSD 2010, machine i686. Hostname x. Libxml version 2.6.26. Using OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008. Compiled with MySQL 5.0.77, using MySQL 5.0.77. Using native malloc. 2010-08-16 13:15:49 [32566] [0] INFO: Added logfile `/projects/kannel/logs/core.log' with level `0'. 2010-08-16 13:15:49 [32566] [0] INFO: Started access logfile `/projects/kannel/logs/access.log'.
Re: How does Kannel handle DLRs from multiple binds to the same SMSC
You need to use an external DLR storage (DB). If you use internal DLR storage, which is in memory, each Kannel server will store the info from the DLRs originated via that server, so if the SMSC send the DLR via the other server, it won't find it. See the external DB DLR storage options here: http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN3170 On Wed, Aug 25, 2010 at 5:09 PM, brett skinner tatty.dishcl...@gmail.com wrote: Hi In an effort to increase through put our SMSC suggested that we created another bind to them with the exact same details. I.e. username, password, IP address and port. In our configuration file I have created a second bind with a different ID but have set both SMPP connections to use the same allowed-smsc-id. The SMSC did mention that they would load balance the DLRs across the binds and feed to which ever bind had the least traffic. Looking through the bearerbox logs I don't not see any rejected DLRs. But we are missing an unusally large number of DLRs. Were we incorrect in our assumption that Kannel would be able to match the DLRs even if the original sms went out on one bind and came back in on another bind? Regards,
Re: How does Kannel handle DLRs from multiple binds to the same SMSC
Also, both binds will need to use the same smsc-id, since the SQL queries that search for the DLR info use the smsc-id on its WHERE conditions. Use smsc-admin-id to control each bind individually (start/stop/etc), but specify the same smsc-id on both On Wed, Aug 25, 2010 at 6:18 PM, Juan Nin jua...@gmail.com wrote: You need to use an external DLR storage (DB). If you use internal DLR storage, which is in memory, each Kannel server will store the info from the DLRs originated via that server, so if the SMSC send the DLR via the other server, it won't find it. See the external DB DLR storage options here: http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN3170 On Wed, Aug 25, 2010 at 5:09 PM, brett skinner tatty.dishcl...@gmail.com wrote: Hi In an effort to increase through put our SMSC suggested that we created another bind to them with the exact same details. I.e. username, password, IP address and port. In our configuration file I have created a second bind with a different ID but have set both SMPP connections to use the same allowed-smsc-id. The SMSC did mention that they would load balance the DLRs across the binds and feed to which ever bind had the least traffic. Looking through the bearerbox logs I don't not see any rejected DLRs. But we are missing an unusally large number of DLRs. Were we incorrect in our assumption that Kannel would be able to match the DLRs even if the original sms went out on one bind and came back in on another bind? Regards,
RE: UNABLE TO RECEIVE DLR FROM KANNEL SMPP
If you need a unique message ID, add it to your dlr-url. E.g.: dlr-url=http://www.example.com/dlr.php?id=[MY_ID]. (urlencoded). == Rene From: an...@in.multiplesystem.net [mailto:an...@in.multiplesystem.net] On Behalf Of Anshu Sah Sent: Wednesday, 25 August, 2010 23:18 To: Nikos Balkanas Cc: Rene Kluwen; users@kannel.org Subject: Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hello Nikos, If the DLRs which are coming to MySQL is temporary, Then i can also use DLR storage Internal, and Make a SMALL application to sense DLRs. i am confused is there any Key Or any Value by which we can compare that the coming DLR is for any specfic Message Sent. for example : While Sending SMS I get only text 0: Accepted for delivery But if i get message ID here while sending same message ID is returned as value when i get DLR, i can match DLR with Sent message easily in my table. Hope that message ID is an Unqiue value. Regards, Anshu 2010/8/26 Nikos Balkanas nbalka...@gmail.com Hi, For info read UG about reroute-smsc. Once you reroute that, you may also want to reroute its DLRs. Since you don't, you don't need to. Just ignore it. I see you are using a DB for dlr-storage (mysql)?. This table is for internal processing only. DLR is deleted once it is matched. If you want permanent DLR storage, use your own web application, and use dlr-url. Filed timestamp is really SMSc forreign id and should be varchar(64). BR, Nikos - Original Message - From: Anshu Sah To: Rene Kluwen Cc: Nikos Balkanas ; users@kannel.org Sent: Wednesday, August 25, 2010 11:55 PM Subject: Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hello Nikos, Can you please explain this below Line. 2010-08-25 13:01:27 [6057] [0] INFO: DLR rerouting for smsc id vFirstDEMO disabled. One more thing by adding dlr-mask=31 i got the DLR but i got only below params, But i want to add a custom column, which i will add while sending message by which i could Query into this table for DLRs. id smsc timestamp destination source service url mask status boxc_id 1vFirstDEMO-00-00 00:00:009216217231anshukannel 310 4vFirstDEMO34102674779781114229anshukannel 310 Regards Anshu On Tue, Aug 17, 2010 at 6:55 PM, Rene Kluwen rene.klu...@chimit.nl wrote: See this post from Nikos. -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Nikos Balkanas Sent: Monday, 16 August, 2010 22:55 To: Anshu Sah; users@kannel.org Subject: Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hi, Please post your sendsms URL and detailed bb logs of an attempt to send an MT. BR, Nikos - Original Message - From: Anshu Sah To: users@kannel.org Sent: Monday, August 16, 2010 10:39 PM Subject: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hello I am unable to receive DLR in Kannel using SMPP Connectivity., Please guide. If i am doing something wrong, Regards Anshu Configuration is below group = core admin-port = 13000 smsbox-port = 13001 admin-password = bar log-file = /projects/kannel/logs/core.log log-level = 0 #box-deny-ip = *.*.*.* #box-allow-ip = 127.0.0.1 dlr-storage = mysql access-log = /projects/kannel/logs/access.log #store-file = /projects/kannel/logs/storefile.log #dlr-storage = internal group=smsc smsc=smpp smsc-id=x host = xx port = 2345 receive-port = 2345 log-file = /projects/kannel/logs/smsc.log log-level = 0 smsc-username = x smsc-password = xxx msg-id-type = 0x01 transceiver-mode=1 system-type = 'VMA' #service-type = 'test' interface-version = 34 address-range = '' #msg-id-type = 0 group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 log-level = 0 group = sendsms-user username = kannel password = hard2guess concatenation = true max-messages = 3 #--- mysql connection group = mysql-connection id = mydlr host = localhost username = xx password = xxx database = kannel max-connections = 1 # DLR table structure group = dlr-db id = mydlr table = kannel_dlr field-smsc = smsc field-timestamp = timestamp field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxc_id LOGS [r...@splash gw]# ./bearerbox /projects/kannel/configs/x.inc 2010-08-16 13:15:49 [32566] [0] INFO: Debug_lvl = -1, log_file = none, log_lvl = 0 2010-08-16 13:15:49 [32566] [0] INFO: MYSQL: Connected to server at localhost. 2010-08-16 13:15:49 [32566] [0] INFO: MYSQL: server version 5.0.77, client version 5.0.77. 2010-08-16 13:15:49 [32566] [0] INFO: DLR using storage type: mysql 2010-08-16 13:15:49 [32566] [0] DEBUG: Kannel bearerbox version `1.4.3'. Build `Aug 15 2010 18:31:17', compiler `4.1.2 20080704 (Red Hat 4.1.2-48)'. System Linux, release 2.6.18-194.8.1.el5.028stab070.2, version #1 SMP Tue Jul 6 14:55:39 MSD 2010, machine i686. Hostname x. Libxml version 2.6.26. Using OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008.
Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP
Hello rene, http://xxx.xxx.xxx.xxx:13013/cgi-bin/sendsms?username=kannelpassword=hard2guessfrom=anshuto=919781114229text=Hi+Anshu+Testing+Kanneldlr-mask=31dlr-url=http://xxx.xxx.xxx.xxx/DLR/processDLR.php?messageID=8456 But got this dlr-url saved in DB but I didn't got whether the message has been delivered or NOT and if delivered I didn't got the time of delivery by URL I got following value saved in DB id smsc timestamp destination source service url maskhttp://173.236.83.224/phpmyadmin/sql.php?db=kanneltable=kannel_dlrtoken=436569dc31a10bbc57c6a3909c72d9e8sql_query=SELECT+%2A+FROM+%60kannel_dlr%60+ORDER+BY+%60kannel_dlr%60.%60mask%60+ASC statushttp://173.236.83.224/phpmyadmin/sql.php?db=kanneltable=kannel_dlrtoken=436569dc31a10bbc57c6a3909c72d9e8sql_query=SELECT+%2A+FROM+%60kannel_dlr%60+ORDER+BY+%60kannel_dlr%60.%60status%60+ASC boxc_idhttp://173.236.83.224/phpmyadmin/sql.php?db=kanneltable=kannel_dlrtoken=436569dc31a10bbc57c6a3909c72d9e8sql_query=SELECT+%2A+FROM+%60kannel_dlr%60+ORDER+BY+%60kannel_dlr%60.%60boxc_id%60+ASC 1 vFirstDEMO 499708338 919781114229 anshu kannel http://xxx.xxx.xxx.xxx/DLR/processDLR.php 31 02 vFirstDEMO 506335868 919781114229 anshu kannel http://xxx.xxx.xxx.xxx/DLR/processDLR.php?messageID... 31 0 Regards Anshu On Thu, Aug 26, 2010 at 2:59 AM, Rene Kluwen rene.klu...@chimit.nl wrote: If you need a unique message ID, add it to your dlr-url. E.g.: dlr-url=http://www.example.com/dlr.php?id=[MY_ID]. (urlencoded). == Rene *From:* an...@in.multiplesystem.net [mailto:an...@in.multiplesystem.net] *On Behalf Of *Anshu Sah *Sent:* Wednesday, 25 August, 2010 23:18 *To:* Nikos Balkanas *Cc:* Rene Kluwen; users@kannel.org *Subject:* Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hello Nikos, If the DLRs which are coming to MySQL is temporary, Then i can also use DLR storage Internal, and Make a SMALL application to sense DLRs. i am confused is there any Key Or any Value by which we can compare that the coming DLR is for any specfic Message Sent. for example : While Sending SMS I get only text 0: Accepted for delivery But if i get *message ID* here while sending same *message ID* is returned as value when i get DLR, i can match DLR with Sent message easily in my table. Hope that *message ID is an Unqiue *value. Regards, Anshu 2010/8/26 Nikos Balkanas nbalka...@gmail.com Hi, For info read UG about reroute-smsc. Once you reroute that, you may also want to reroute its DLRs. Since you don't, you don't need to. Just ignore it. I see you are using a DB for dlr-storage (mysql)?. This table is for internal processing only. DLR is deleted once it is matched. If you want permanent DLR storage, use your own web application, and use dlr-url. Filed timestamp is really SMSc forreign id and should be varchar(64). BR, Nikos - Original Message - From: Anshu Sah To: Rene Kluwen Cc: Nikos Balkanas ; users@kannel.org Sent: Wednesday, August 25, 2010 11:55 PM Subject: Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hello Nikos, Can you please explain this below Line. 2010-08-25 13:01:27 [6057] [0] INFO: DLR rerouting for smsc id vFirstDEMO disabled. One more thing by adding dlr-mask=31 i got the DLR but i got only below params, But i want to add a custom column, which i will add while sending message by which i could Query into this table for DLRs. id smsc timestamp destination source service url mask status boxc_id 1vFirstDEMO-00-00 00:00:009216217231anshukannel 310 4vFirstDEMO34102674779781114229anshukannel 310 Regards Anshu On Tue, Aug 17, 2010 at 6:55 PM, Rene Kluwen rene.klu...@chimit.nl wrote: See this post from Nikos. -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Nikos Balkanas Sent: Monday, 16 August, 2010 22:55 To: Anshu Sah; users@kannel.org Subject: Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hi, Please post your sendsms URL and detailed bb logs of an attempt to send an MT. BR, Nikos - Original Message - From: Anshu Sah To: users@kannel.org Sent: Monday, August 16, 2010 10:39 PM Subject: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hello I am unable to receive DLR in Kannel using SMPP Connectivity., Please guide. If i am doing something wrong, Regards Anshu Configuration is below group = core admin-port = 13000 smsbox-port = 13001 admin-password = bar log-file = /projects/kannel/logs/core.log log-level = 0 #box-deny-ip = *.*.*.* #box-allow-ip = 127.0.0.1 dlr-storage = mysql access-log = /projects/kannel/logs/access.log #store-file = /projects/kannel/logs/storefile.log #dlr-storage = internal group=smsc smsc=smpp smsc-id=x host = xx port = 2345 receive-port = 2345 log-file = /projects/kannel/logs/smsc.log log-level = 0 smsc-username = x smsc-password = xxx msg-id-type = 0x01 transceiver-mode=1 system-type = 'VMA'
RE: UNABLE TO RECEIVE DLR FROM KANNEL SMPP
Use: dlr-url=http://xxx.xxx.xxx/DLR/processDLR.php?messageID=type=%dtime=%t For the complete list of excape codes, see table 6-9 in the user manual. == Rene From: an...@in.multiplesystem.net [mailto:an...@in.multiplesystem.net] On Behalf Of Anshu Sah Sent: Wednesday, 25 August, 2010 23:42 To: Rene Kluwen Cc: Nikos Balkanas; users@kannel.org Subject: Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hello rene, http://xxx.xxx.xxx.xxx:13013/cgi-bin/sendsms?username=kannel http://xxx.xxx.xxx.xxx:13013/cgi-bin/sendsms?username=kannelpassword=hard2 guessfrom=anshuto=919781114229text=Hi+Anshu+Testing+Kanneldlr-mask=31dl r-url=http://xxx.xxx.xxx.xxx/DLR/processDLR.php?messageID=8456 password=hard2guessfrom=anshuto=919781114229text=Hi+Anshu+Testing+Kannel dlr-mask=31dlr-url=http://xxx.xxx.xxx.xxx/DLR/processDLR.php?messageID=845 6 But got this dlr-url saved in DB but I didn't got whether the message has been delivered or NOT and if delivered I didn't got the time of delivery by URL I got following value saved in DB id smsc timestamp destination source service url mask http://173.236.83.224/phpmyadmin/sql.php?db=kanneltable=kannel_dlrtoken=4 36569dc31a10bbc57c6a3909c72d9e8sql_query=SELECT+%2A+FROM+%60kannel_dlr%60+O RDER+BY+%60kannel_dlr%60.%60mask%60+ASC status http://173.236.83.224/phpmyadmin/sql.php?db=kanneltable=kannel_dlrtoken=4 36569dc31a10bbc57c6a3909c72d9e8sql_query=SELECT+%2A+FROM+%60kannel_dlr%60+O RDER+BY+%60kannel_dlr%60.%60status%60+ASC boxc_id http://173.236.83.224/phpmyadmin/sql.php?db=kanneltable=kannel_dlrtoken=4 36569dc31a10bbc57c6a3909c72d9e8sql_query=SELECT+%2A+FROM+%60kannel_dlr%60+O RDER+BY+%60kannel_dlr%60.%60boxc_id%60+ASC 1 vFirstDEMO 499708338 919781114229 anshu kannel http://xxx.xxx.xxx.xxx/DLR/processDLR.php 31 0 2 vFirstDEMO 506335868 919781114229 anshu kannel http://xxx.xxx.xxx.xxx/DLR/processDLR.php?messageID... 31 0 Regards Anshu On Thu, Aug 26, 2010 at 2:59 AM, Rene Kluwen rene.klu...@chimit.nl wrote: If you need a unique message ID, add it to your dlr-url. E.g.: dlr-url=http://www.example.com/dlr.php?id=[MY_ID] http://www.example.com/dlr.php?id=%5bMY_ID%5d . (urlencoded). == Rene From: an...@in.multiplesystem.net [mailto:an...@in.multiplesystem.net] On Behalf Of Anshu Sah Sent: Wednesday, 25 August, 2010 23:18 To: Nikos Balkanas Cc: Rene Kluwen; users@kannel.org Subject: Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hello Nikos, If the DLRs which are coming to MySQL is temporary, Then i can also use DLR storage Internal, and Make a SMALL application to sense DLRs. i am confused is there any Key Or any Value by which we can compare that the coming DLR is for any specfic Message Sent. for example : While Sending SMS I get only text 0: Accepted for delivery But if i get message ID here while sending same message ID is returned as value when i get DLR, i can match DLR with Sent message easily in my table. Hope that message ID is an Unqiue value. Regards, Anshu 2010/8/26 Nikos Balkanas nbalka...@gmail.com Hi, For info read UG about reroute-smsc. Once you reroute that, you may also want to reroute its DLRs. Since you don't, you don't need to. Just ignore it. I see you are using a DB for dlr-storage (mysql)?. This table is for internal processing only. DLR is deleted once it is matched. If you want permanent DLR storage, use your own web application, and use dlr-url. Filed timestamp is really SMSc forreign id and should be varchar(64). BR, Nikos - Original Message - From: Anshu Sah To: Rene Kluwen Cc: Nikos Balkanas ; users@kannel.org Sent: Wednesday, August 25, 2010 11:55 PM Subject: Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hello Nikos, Can you please explain this below Line. 2010-08-25 13:01:27 [6057] [0] INFO: DLR rerouting for smsc id vFirstDEMO disabled. One more thing by adding dlr-mask=31 i got the DLR but i got only below params, But i want to add a custom column, which i will add while sending message by which i could Query into this table for DLRs. id smsc timestamp destination source service url mask status boxc_id 1vFirstDEMO-00-00 00:00:009216217231anshukannel 310 4vFirstDEMO34102674779781114229anshukannel 310 Regards Anshu On Tue, Aug 17, 2010 at 6:55 PM, Rene Kluwen rene.klu...@chimit.nl wrote: See this post from Nikos. -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Nikos Balkanas Sent: Monday, 16 August, 2010 22:55 To: Anshu Sah; users@kannel.org Subject: Re: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hi, Please post your sendsms URL and detailed bb logs of an attempt to send an MT. BR, Nikos - Original Message - From: Anshu Sah To: users@kannel.org Sent: Monday, August 16, 2010 10:39 PM Subject: UNABLE TO RECEIVE DLR FROM KANNEL SMPP Hello I am unable to receive DLR in Kannel using SMPP Connectivity., Please guide. If i am doing something wrong,
RE: Problem with Regular Expressions
ok, here it is : -BEGIN CONF # # Sample configuration file for Kannel bearerbox on Debian. # See the documentation for explanations of fields. # # HTTP administration is disabled by default. Make sure you set the # password if you enable it. group = core admin-port = 13000 admin-password = xx #admin-deny-ip = *.*.*.* #admin-allow-ip = wapbox-port = 13002 wdp-interface-name = * log-file = /var/log/kannel/bearerbox.log log-level = 0 #box-deny-ip = *.*.*.* #box-allow-ip = 127.0.0.1 smsbox-port = 13003 group = wapbox bearerbox-host = localhost log-file = /var/log/kannel/wapbox.log # SMSC Fake group = smsc smsc = fake host = localhost port = 13004 group = smsbox bearerbox-host = localhost sendsms-port = 13005 log-file = /var/log/kannel/smsbox.log log-level = 0 access-log = /var/log/kannel/smsbox-access.log group = sendsms-user username = test password = test default-sender = 12345 group = sms-service name = SLG #keyword = SLG keyword-regex = ^SLG[0-9]+$ text = Hi there,SLG %a %b #exec = ls -l / catch-all = true # SMS SERVICE Default # there should be default always group = sms-service keyword = default text = No service specified %a %b catch-all = true -END CONF-- BEGIN LOG-- 2010-08-26 01:17:09 [10783] [0] INFO: Added logfile `/var/log/kannel/smsbox.log' with level `0'. 2010-08-26 01:17:09 [10783] [0] INFO: Logging accesses to '/var/log/kannel/smsbox-access.log'. 2010-08-26 01:17:09 [10783] [0] INFO: Started access logfile `/var/log/kannel/smsbox-access.log'. 2010-08-26 01:17:09 [10783] [0] INFO: HTTP: Opening server at port 13005. 2010-08-26 01:17:09 [10783] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2010-08-26 01:17:09 [10783] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2010-08-26 01:17:09 [10783] [0] INFO: Set up send sms service at port 13005 2010-08-26 01:17:09 [10783] [0] DEBUG: Started thread 3 (gw/smsbox.c:sendsms_thread) 2010-08-26 01:17:09 [10783] [0] DEBUG: -- 2010-08-26 01:17:09 [10783] [0] DEBUG: Kannel smsbox version 1.4.3 starting 2010-08-26 01:17:09 [10783] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 10783. 2010-08-26 01:17:09 [10783] [3] DEBUG: Thread 3 (gw/smsbox.c:sendsms_thread) maps to pid 10783. 2010-08-26 01:17:09 [10783] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 10783. 2010-08-26 01:17:09 [10783] [0] DEBUG: dumping group (sendsms-user): 2010-08-26 01:17:09 [10783] [0] DEBUG: default-sender = 12345 2010-08-26 01:17:09 [10783] [0] DEBUG: group = sendsms-user 2010-08-26 01:17:09 [10783] [0] DEBUG: username = test 2010-08-26 01:17:09 [10783] [0] DEBUG: password = test 2010-08-26 01:17:09 [10783] [0] DEBUG: Started thread 4 (gw/smsbox.c:obey_request_thread) 2010-08-26 01:17:09 [10783] [0] DEBUG: Started thread 5 (gw/smsbox.c:url_result_thread) 2010-08-26 01:17:09 [10783] [4] DEBUG: Thread 4 (gw/smsbox.c:obey_request_thread) maps to pid 10783. 2010-08-26 01:17:09 [10783] [5] DEBUG: Thread 5 (gw/smsbox.c:url_result_thread) maps to pid 10783. 2010-08-26 01:17:09 [10783] [0] DEBUG: Started thread 6 (gw/smsbox.c:http_queue_thread) 2010-08-26 01:17:09 [10783] [6] DEBUG: Thread 6 (gw/smsbox.c:http_queue_thread) maps to pid 10783. 2010-08-26 01:17:09 [10783] [0] INFO: Connected to bearerbox at localhost port 13003. 2010-08-26 01:17:09 [10783] [0] DEBUG: Started thread 7 (gw/heartbeat.c:heartbeat_thread) 2010-08-26 01:17:09 [10783] [7] DEBUG: Thread 7 (gw/heartbeat.c:heartbeat_thread) maps to pid 10783. 2010-08-26 01:17:58 [10783] [4] DEBUG: no match found: SLG 2010-08-26 01:17:58 [10783] [4] INFO: Starting to service SLG123 from 1 to 2 2010-08-26 01:17:58 [10783] [4] DEBUG: formatted text answer: No service specified SLG123 SLG123 2010-08-26 01:17:58 [10783] [4] DEBUG: message length 34, sending 1 messages 2010-08-26 01:17:58 [10783] [0] DEBUG: Got ACK (0) of 43c761e3-1681-44f0-93f9-000ffbbd5141 2010-08-26 01:17:58 [10783] [0] DEBUG: No client - multi-send or ACK to pull-reply END LOG and, the relevant msg was, using fakesmsc in interactive mode: 1 2 text SLG123 btw, Nikos, are you Greek, as the name implies ? if so, could you perhaps give me a ring (I will send my phone number) -Original Message- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: Wednesday, August 25, 2010 10:18 PM To: Cariotoglou Mike; users@kannel.org Subject: Re: Problem with Regular Expressions Hi, Please post relevant smsbox logs at maximum detail (level = 0). Also post your whole configuration. BR, Nikos - Original Message - From: Cariotoglou Mike m...@singular.gr To: users@kannel.org Sent: Wednesday, August 25, 2010 8:22 PM Subject: Problem with Regular Expressions Hi, I am new to Kannel. I am using 1.4.3 on Ubuntu 10.04 Server. I am trying to set up an SMS gateway, which will connect to smsc using SMPP. before actually connecting to the smsc, I am testing locally, using fakesmsc. The problem I am having
Processing Batch request from Kannel
Hello Nikos Can we give XML based batch request take XML based DLR response from kannel. It will increase scalability of sending sms. Regards, Anshu
RE: Problem with Regular Expressions
From the users manual: Example 4: sms-service-configuration Please note that there are a mandatory keyword and an optional keyword-regex fields. That means that service selection can be simplified as in the following example. Suppose that some Web-content should be delivered to the mobile. Different costumers use the same service but they rely on different keywords. Whenever a sms-service is requested, Kannel first checks whether a regex has been defined, if not a literal match based on keyword is performed. If a regex is configured then the literal match is never tried. group=sms-service ... keyword=web_service keyword-regex=^(data|www|text|net)$ get-url=http://someserver.net/getContent.jsp ... Here it says that keyword is mandatory, even if it won't be evaluated because you have a keyword-regex. So in your case, your sms-service group could be: group = sms-service name = SLG keyword = SLG keyword-regex = ^SLG[0-9]+$ text = Hi there,SLG %a %b catch-all = true What happens if you use this config? == Rene -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Cariotoglou Mike Sent: Thursday, 26 August, 2010 00:23 To: Nikos Balkanas; users@kannel.org Subject: RE: Problem with Regular Expressions ok, here it is : -BEGIN CONF # # Sample configuration file for Kannel bearerbox on Debian. # See the documentation for explanations of fields. # # HTTP administration is disabled by default. Make sure you set the # password if you enable it. group = core admin-port = 13000 admin-password = xx #admin-deny-ip = *.*.*.* #admin-allow-ip = wapbox-port = 13002 wdp-interface-name = * log-file = /var/log/kannel/bearerbox.log log-level = 0 #box-deny-ip = *.*.*.* #box-allow-ip = 127.0.0.1 smsbox-port = 13003 group = wapbox bearerbox-host = localhost log-file = /var/log/kannel/wapbox.log # SMSC Fake group = smsc smsc = fake host = localhost port = 13004 group = smsbox bearerbox-host = localhost sendsms-port = 13005 log-file = /var/log/kannel/smsbox.log log-level = 0 access-log = /var/log/kannel/smsbox-access.log group = sendsms-user username = test password = test default-sender = 12345 group = sms-service name = SLG #keyword = SLG keyword-regex = ^SLG[0-9]+$ text = Hi there,SLG %a %b #exec = ls -l / catch-all = true # SMS SERVICE Default # there should be default always group = sms-service keyword = default text = No service specified %a %b catch-all = true -END CONF-- BEGIN LOG-- 2010-08-26 01:17:09 [10783] [0] INFO: Added logfile `/var/log/kannel/smsbox.log' with level `0'. 2010-08-26 01:17:09 [10783] [0] INFO: Logging accesses to '/var/log/kannel/smsbox-access.log'. 2010-08-26 01:17:09 [10783] [0] INFO: Started access logfile `/var/log/kannel/smsbox-access.log'. 2010-08-26 01:17:09 [10783] [0] INFO: HTTP: Opening server at port 13005. 2010-08-26 01:17:09 [10783] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2010-08-26 01:17:09 [10783] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2010-08-26 01:17:09 [10783] [0] INFO: Set up send sms service at port 13005 2010-08-26 01:17:09 [10783] [0] DEBUG: Started thread 3 (gw/smsbox.c:sendsms_thread) 2010-08-26 01:17:09 [10783] [0] DEBUG: -- 2010-08-26 01:17:09 [10783] [0] DEBUG: Kannel smsbox version 1.4.3 starting 2010-08-26 01:17:09 [10783] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 10783. 2010-08-26 01:17:09 [10783] [3] DEBUG: Thread 3 (gw/smsbox.c:sendsms_thread) maps to pid 10783. 2010-08-26 01:17:09 [10783] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 10783. 2010-08-26 01:17:09 [10783] [0] DEBUG: dumping group (sendsms-user): 2010-08-26 01:17:09 [10783] [0] DEBUG: default-sender = 12345 2010-08-26 01:17:09 [10783] [0] DEBUG: group = sendsms-user 2010-08-26 01:17:09 [10783] [0] DEBUG: username = test 2010-08-26 01:17:09 [10783] [0] DEBUG: password = test 2010-08-26 01:17:09 [10783] [0] DEBUG: Started thread 4 (gw/smsbox.c:obey_request_thread) 2010-08-26 01:17:09 [10783] [0] DEBUG: Started thread 5 (gw/smsbox.c:url_result_thread) 2010-08-26 01:17:09 [10783] [4] DEBUG: Thread 4 (gw/smsbox.c:obey_request_thread) maps to pid 10783. 2010-08-26 01:17:09 [10783] [5] DEBUG: Thread 5 (gw/smsbox.c:url_result_thread) maps to pid 10783. 2010-08-26 01:17:09 [10783] [0] DEBUG: Started thread 6 (gw/smsbox.c:http_queue_thread) 2010-08-26 01:17:09 [10783] [6] DEBUG: Thread 6 (gw/smsbox.c:http_queue_thread) maps to pid 10783. 2010-08-26 01:17:09 [10783] [0] INFO: Connected to bearerbox at localhost port 13003. 2010-08-26 01:17:09 [10783] [0] DEBUG: Started thread 7 (gw/heartbeat.c:heartbeat_thread) 2010-08-26 01:17:09 [10783] [7] DEBUG: Thread 7 (gw/heartbeat.c:heartbeat_thread) maps to pid 10783. 2010-08-26 01:17:58 [10783] [4] DEBUG: no match found: SLG 2010-08-26 01:17:58 [10783]
RE: Problem with Regular Expressions
it is one of the places where the doc is not up-to-date. if you try this, you will get a PANIC error, saying either keyword OR keyword-regex must be defined, but not both. at least in version 1.4.3 -Original Message- From: Rene Kluwen [mailto:rene.klu...@chimit.nl] Sent: Thursday, August 26, 2010 2:16 AM To: Cariotoglou Mike; 'Nikos Balkanas'; users@kannel.org Subject: RE: Problem with Regular Expressions From the users manual: Example 4: sms-service-configuration Please note that there are a mandatory keyword and an optional keyword-regex fields. That means that service selection can be simplified as in the following example. Suppose that some Web-content should be delivered to the mobile. Different costumers use the same service but they rely on different keywords. Whenever a sms-service is requested, Kannel first checks whether a regex has been defined, if not a literal match based on keyword is performed. If a regex is configured then the literal match is never tried. group=sms-service ... keyword=web_service keyword-regex=^(data|www|text|net)$ get-url=http://someserver.net/getContent.jsp ... Here it says that keyword is mandatory, even if it won't be evaluated because you have a keyword-regex. So in your case, your sms-service group could be: group = sms-service name = SLG keyword = SLG keyword-regex = ^SLG[0-9]+$ text = Hi there,SLG %a %b catch-all = true What happens if you use this config? == Rene -Original Message- From: Rene Kluwen [mailto:rene.klu...@chimit.nl] Sent: Thursday, August 26, 2010 2:16 AM To: Cariotoglou Mike; 'Nikos Balkanas'; users@kannel.org Subject: RE: Problem with Regular Expressions From the users manual: Example 4: sms-service-configuration Please note that there are a mandatory keyword and an optional keyword-regex fields. That means that service selection can be simplified as in the following example. Suppose that some Web-content should be delivered to the mobile. Different costumers use the same service but they rely on different keywords. Whenever a sms-service is requested, Kannel first checks whether a regex has been defined, if not a literal match based on keyword is performed. If a regex is configured then the literal match is never tried. group=sms-service ... keyword=web_service keyword-regex=^(data|www|text|net)$ get-url=http://someserver.net/getContent.jsp ... Here it says that keyword is mandatory, even if it won't be evaluated because you have a keyword-regex. So in your case, your sms-service group could be: group = sms-service name = SLG keyword = SLG keyword-regex = ^SLG[0-9]+$ text = Hi there,SLG %a %b catch-all = true What happens if you use this config? == Rene -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Cariotoglou Mike Sent: Thursday, 26 August, 2010 00:23 To: Nikos Balkanas; users@kannel.org Subject: RE: Problem with Regular Expressions ok, here it is : -BEGIN CONF # # Sample configuration file for Kannel bearerbox on Debian. # See the documentation for explanations of fields. # # HTTP administration is disabled by default. Make sure you set the # password if you enable it. group = core admin-port = 13000 admin-password = xx #admin-deny-ip = *.*.*.* #admin-allow-ip = wapbox-port = 13002 wdp-interface-name = * log-file = /var/log/kannel/bearerbox.log log-level = 0 #box-deny-ip = *.*.*.* #box-allow-ip = 127.0.0.1 smsbox-port = 13003 group = wapbox bearerbox-host = localhost log-file = /var/log/kannel/wapbox.log # SMSC Fake group = smsc smsc = fake host = localhost port = 13004 group = smsbox bearerbox-host = localhost sendsms-port = 13005 log-file = /var/log/kannel/smsbox.log log-level = 0 access-log = /var/log/kannel/smsbox-access.log group = sendsms-user username = test password = test default-sender = 12345 group = sms-service name = SLG #keyword = SLG keyword-regex = ^SLG[0-9]+$ text = Hi there,SLG %a %b #exec = ls -l / catch-all = true # SMS SERVICE Default # there should be default always group = sms-service keyword = default text = No service specified %a %b catch-all = true -END CONF-- BEGIN LOG-- 2010-08-26 01:17:09 [10783] [0] INFO: Added logfile `/var/log/kannel/smsbox.log' with level `0'. 2010-08-26 01:17:09 [10783] [0] INFO: Logging accesses to '/var/log/kannel/smsbox-access.log'. 2010-08-26 01:17:09 [10783] [0] INFO: Started access logfile `/var/log/kannel/smsbox-access.log'. 2010-08-26 01:17:09 [10783] [0] INFO: HTTP: Opening server at port 13005. 2010-08-26 01:17:09 [10783] [0]
RE: Problem with Regular Expressions
Then I don't know. Your config looks allright for the rest. - Oorspronkelijk bericht - Van: Cariotoglou Mike m...@singular.gr Verzonden: donderdag 26 augustus 2010 1:26 Aan: users@kannel.org Onderwerp: RE: Problem with Regular Expressions it is one of the places where the doc is not up-to-date. if you try this, you will get a PANIC error, saying either keyword OR keyword-regex must be defined, but not both. at least in version 1.4.3 -Original Message- From: Rene Kluwen [mailto:rene.klu...@chimit.nl] Sent: Thursday, August 26, 2010 2:16 AM To: Cariotoglou Mike; 'Nikos Balkanas'; users@kannel.org Subject: RE: Problem with Regular Expressions From the users manual: Example 4: sms-service-configuration Please note that there are a mandatory keyword and an optional keyword-regex fields. That means that service selection can be simplified as in the following example. Suppose that some Web-content should be delivered to the mobile. Different costumers use the same service but they rely on different keywords. Whenever a sms-service is requested, Kannel first checks whether a regex has been defined, if not a literal match based on keyword is performed. If a regex is configured then the literal match is never tried. group=sms-service ... keyword=web_service keyword-regex=^(data|www|text|net)$ get-url=http://someserver.net/getContent.jsp ... Here it says that keyword is mandatory, even if it won't be evaluated because you have a keyword-regex. So in your case, your sms-service group could be: group = sms-service name = SLG keyword = SLG keyword-regex = ^SLG[0-9]+$ text = Hi there,SLG %a %b catch-all = true What happens if you use this config? == Rene -Original Message- From: Rene Kluwen [mailto:rene.klu...@chimit.nl] Sent: Thursday, August 26, 2010 2:16 AM To: Cariotoglou Mike; 'Nikos Balkanas'; users@kannel.org Subject: RE: Problem with Regular Expressions From the us [Het originele bericht is niet volledig opgenomen]
Re: Problem with Regular Expressions
This is a bug in the keyword-regex. It converts all keywords to lower case, and works fine with keyword, but initializes kwyword-regex only for exact matches. Will submit patch in devel. BR, Nikos - Original Message - From: Rene Kluwen rene.klu...@chimit.nl To: Cariotoglou Mike m...@singular.gr; users@kannel.org Sent: Thursday, August 26, 2010 3:04 AM Subject: RE: Problem with Regular Expressions Then I don't know. Your config looks allright for the rest. - Oorspronkelijk bericht - Van: Cariotoglou Mike m...@singular.gr Verzonden: donderdag 26 augustus 2010 1:26 Aan: users@kannel.org Onderwerp: RE: Problem with Regular Expressions it is one of the places where the doc is not up-to-date. if you try this, you will get a PANIC error, saying either keyword OR keyword-regex must be defined, but not both. at least in version 1.4.3 -Original Message- From: Rene Kluwen [mailto:rene.klu...@chimit.nl] Sent: Thursday, August 26, 2010 2:16 AM To: Cariotoglou Mike; 'Nikos Balkanas'; users@kannel.org Subject: RE: Problem with Regular Expressions From the users manual: Example 4: sms-service-configuration Please note that there are a mandatory keyword and an optional keyword-regex fields. That means that service selection can be simplified as in the following example. Suppose that some Web-content should be delivered to the mobile. Different costumers use the same service but they rely on different keywords. Whenever a sms-service is requested, Kannel first checks whether a regex has been defined, if not a literal match based on keyword is performed. If a regex is configured then the literal match is never tried. group=sms-service ... keyword=web_service keyword-regex=^(data|www|text|net)$ get-url=http://someserver.net/getContent.jsp ... Here it says that keyword is mandatory, even if it won't be evaluated because you have a keyword-regex. So in your case, your sms-service group could be: group = sms-service name = SLG keyword = SLG keyword-regex = ^SLG[0-9]+$ text = Hi there,SLG %a %b catch-all = true What happens if you use this config? == Rene -Original Message- From: Rene Kluwen [mailto:rene.klu...@chimit.nl] Sent: Thursday, August 26, 2010 2:16 AM To: Cariotoglou Mike; 'Nikos Balkanas'; users@kannel.org Subject: RE: Problem with Regular Expressions From the us [Het originele bericht is niet volledig opgenomen]
Strange concatenated MO issue
Hello all, I have an SMSC connection to Telecom New Zealand. When I test my connection by sending a multipart text message from a handset to a shortcode I get weird text at kannel. Sending a single part text message from exactly the same handset works correctly. My long text message is: 99192939495969798Z9091929394959612345 What I receive at the get-url for the text is: text=r%C3%96.rX.r%C3%96Nr%C3%96.r%C3%96.h%C3%96.rZ.r%C3%96r%C3%96.r%C3%96.p%C3%96.r%C3%96.r%C3%86%2Cr%C3%96.%CE%A8r%C3%96.r%C3%96.r%C3%96.r%C3%86-r%C3%96.Wrr%C3%96.d3Z When I urldecode that I get (in hex, with a space between characters): c3 96 2e 72 58 2e 72 c3 96 4e 72 c3 96 2e 72 c3 96 2e 68 c3 96 2e 72 5a 2e 72 c3 96 72 c3 96 2e 72 c3 96 2e 70 c3 96 2e 72 c3 96 2e 72 c3 86 2c 72 c3 96 2e ce a8 72 c3 96 2e 72 c3 96 2e 72 c3 96 2e 72 c3 86 2d 72 c3 96 2e 57 72 72 c3 96 2e 64 33 5a Has anyone seen something similar to this and can point me at a solution (or in the direction of likely things to look at)? The initial PDU (with some information obfuscated and with some following messages) is: 2010-08-26 04:27:12 [30851] [10] DEBUG: Optional parameter tag (0x0204) 2010-08-26 04:27:12 [30851] [10] DEBUG: Optional parameter length read as 2 2010-08-26 04:27:12 [30851] [10] DEBUG: SMPP[X-XX]: Got PDU: 2010-08-26 04:27:12 [30851] [10] DEBUG: SMPP PDU 0xe0f580 dump: 2010-08-26 04:27:12 [30851] [10] DEBUG: type_name: deliver_sm 2010-08-26 04:27:12 [30851] [10] DEBUG: command_id: 5 = 0x0005 2010-08-26 04:27:12 [30851] [10] DEBUG: command_status: 0 = 0x 2010-08-26 04:27:12 [30851] [10] DEBUG: sequence_number: 351 = 0x015f 2010-08-26 04:27:12 [30851] [10] DEBUG: service_type: NULL 2010-08-26 04:27:12 [30851] [10] DEBUG: source_addr_ton: 1 = 0x0001 2010-08-26 04:27:12 [30851] [10] DEBUG: source_addr_npi: 1 = 0x0001 2010-08-26 04:27:12 [30851] [10] DEBUG: source_addr: 649 2010-08-26 04:27:12 [30851] [10] DEBUG: dest_addr_ton: 2 = 0x0002 2010-08-26 04:27:12 [30851] [10] DEBUG: dest_addr_npi: 1 = 0x0001 2010-08-26 04:27:12 [30851] [10] DEBUG: destination_addr: 2010-08-26 04:27:12 [30851] [10] DEBUG: esm_class: 64 = 0x0040 2010-08-26 04:27:12 [30851] [10] DEBUG: protocol_id: 0 = 0x 2010-08-26 04:27:12 [30851] [10] DEBUG: priority_flag: 1 = 0x0001 2010-08-26 04:27:12 [30851] [10] DEBUG: schedule_delivery_time: NULL 2010-08-26 04:27:12 [30851] [10] DEBUG: validity_period: NULL 2010-08-26 04:27:12 [30851] [10] DEBUG: registered_delivery: 0 = 0x 2010-08-26 04:27:12 [30851] [10] DEBUG: replace_if_present_flag: 0 = 0x 2010-08-26 04:27:12 [30851] [10] DEBUG: data_coding: 240 = 0x00f0 2010-08-26 04:27:12 [30851] [10] DEBUG: sm_default_msg_id: 0 = 0x 2010-08-26 04:27:12 [30851] [10] DEBUG: sm_length: 140 = 0x008c 2010-08-26 04:27:12 [30851] [10] DEBUG: short_message: 2010-08-26 04:27:12 [30851] [10] DEBUG:Octet string at 0xe0f4b0: 2010-08-26 04:27:12 [30851] [10] DEBUG: len: 140 2010-08-26 04:27:12 [30851] [10] DEBUG: size: 141 2010-08-26 04:27:12 [30851] [10] DEBUG: immutable: 0 2010-08-26 04:27:12 [30851] [10] DEBUG: data: 05 00 03 16 02 01 72 b9 5c 2e 97 cb e5 72 b9 58 ..r.\r.X 2010-08-26 04:27:12 [30851] [10] DEBUG: data: 2e 97 cb e5 72 b9 5c 4e 96 cb e5 72 b9 5c 2e 97 r.\N...r.\.. 2010-08-26 04:27:12 [30851] [10] DEBUG: data: 9b e5 72 b9 5c 2e 97 cb e5 68 b9 5c 2e 97 cb e5 ..r.\h.\ 2010-08-26 04:27:12 [30851] [10] DEBUG: data: 72 b9 5a 2e 97 cb e5 72 b9 5c ce 96 cb e5 72 b9 r.Zr.\r. 2010-08-26 04:27:12 [30851] [10] DEBUG: data: 5c 2e 97 bb e5 72 b9 5c 2e 97 cb e5 70 b9 5c 2e \r.\p.\. 2010-08-26 04:27:12 [30851] [10] DEBUG: data: 97 cb e5 72 da 5c 2e 97 cb e5 72 b9 1c 2c 97 cb ...r.\r..,.. 2010-08-26 04:27:12 [30851] [10] DEBUG: data: e5 72 b9 5c 2e 17 cb e5 72 b9 5c 2e 97 cb c9 72 .r.\r.\r 2010-08-26 04:27:12 [30851] [10] DEBUG: data: b9 5c 2e 97 cb e5 72 b3 5c 2e 97 cb e5 72 b9 1c .\r.\r.. 2010-08-26 04:27:12 [30851] [10] DEBUG: data: 2d 97 cb e5 72 b9 5c 2e 57 cb e5 72 -...r.\.W..r 2010-08-26 04:27:12 [30851] [10] DEBUG:Octet string dump ends. 2010-08-26 04:27:12 [30851] [10] DEBUG: user_message_reference: 85 = 0x0055 2010-08-26 04:27:12 [30851] [10] DEBUG: SMPP PDU dump ends. 2010-08-26 04:27:12 [30851] [10] DEBUG: SMPP[MAS01-RX]: UDH length read as 6 2010-08-26 04:27:12 [30851] [10] WARNING: Could not convert GSM (0xb9) to Unicode. 2010-08-26 04:27:12 [30851] [10] WARNING: Could not convert GSM (0x97) to Unicode. 2010-08-26 04:27:12 [30851] [10] WARNING: Could not convert GSM (0xcb) to Unicode. 2010-08-26 04:27:12 [30851] [10] WARNING: Could not convert GSM (0xe5) to Unicode. 2010-08-26 04:27:12 [30851] [10] WARNING: Could
Re: Problem with Regular Expressions
Actually this patch is stupid. Just put pattern in lower case: keyword-regex = ^slg[0-9]+$ and it will work. I will retract patch. BR, Nikos - Original Message - From: Nikos Balkanas nbalka...@gmail.com To: Rene Kluwen rene.klu...@chimit.nl; Cariotoglou Mike m...@singular.gr; users@kannel.org Sent: Thursday, August 26, 2010 7:51 AM Subject: Re: Problem with Regular Expressions This is a bug in the keyword-regex. It converts all keywords to lower case, and works fine with keyword, but initializes kwyword-regex only for exact matches. Will submit patch in devel. BR, Nikos - Original Message - From: Rene Kluwen rene.klu...@chimit.nl To: Cariotoglou Mike m...@singular.gr; users@kannel.org Sent: Thursday, August 26, 2010 3:04 AM Subject: RE: Problem with Regular Expressions Then I don't know. Your config looks allright for the rest. - Oorspronkelijk bericht - Van: Cariotoglou Mike m...@singular.gr Verzonden: donderdag 26 augustus 2010 1:26 Aan: users@kannel.org Onderwerp: RE: Problem with Regular Expressions it is one of the places where the doc is not up-to-date. if you try this, you will get a PANIC error, saying either keyword OR keyword-regex must be defined, but not both. at least in version 1.4.3 -Original Message- From: Rene Kluwen [mailto:rene.klu...@chimit.nl] Sent: Thursday, August 26, 2010 2:16 AM To: Cariotoglou Mike; 'Nikos Balkanas'; users@kannel.org Subject: RE: Problem with Regular Expressions From the users manual: Example 4: sms-service-configuration Please note that there are a mandatory keyword and an optional keyword-regex fields. That means that service selection can be simplified as in the following example. Suppose that some Web-content should be delivered to the mobile. Different costumers use the same service but they rely on different keywords. Whenever a sms-service is requested, Kannel first checks whether a regex has been defined, if not a literal match based on keyword is performed. If a regex is configured then the literal match is never tried. group=sms-service ... keyword=web_service keyword-regex=^(data|www|text|net)$ get-url=http://someserver.net/getContent.jsp ... Here it says that keyword is mandatory, even if it won't be evaluated because you have a keyword-regex. So in your case, your sms-service group could be: group = sms-service name = SLG keyword = SLG keyword-regex = ^SLG[0-9]+$ text = Hi there,SLG %a %b catch-all = true What happens if you use this config? == Rene -Original Message- From: Rene Kluwen [mailto:rene.klu...@chimit.nl] Sent: Thursday, August 26, 2010 2:16 AM To: Cariotoglou Mike; 'Nikos Balkanas'; users@kannel.org Subject: RE: Problem with Regular Expressions From the us [Het originele bericht is niet volledig opgenomen]
