Mallformed addr
Hi, all. Just a little question. With one of the operators I'm connected I receive in core-bearbox.log (in every SMS MO) == core-bearbox.log == 2010-04-19 03:32:48 [9007] [24] WARNING: SMPP[connRX]: Mallformed addr `1213', generally expected at least 7 digits. I just a warning, but I'm curious to know if I have to add some parameter to conf file, or is a problem of that operator. I'm using smpp 3.4 with kannel 1.4.1. Regards, Rodrigo
meta-data branch
Hi, guys. Just a little question ? Is meta-data branch going to be actualized soon ? Or is it possible to add meta-data functionality to current 1.4.3 version (how) ? Regards, m
Control of messaging traffic
Hi, guys. Actually I'm migrating from an SMSC with smpp 3.4 that uses system-type (a diffentent system type per different short number) to another with smpp 3.4 that doesn't use it. So, I'm passing from a system with a lot connections to another with just 2 sockets as a limit. To start the operator gave us a traffic limit of 10sms/second (this includes sms mo, mt, and dlrs). Any further message will be discarded by operator platform. Is it possible to configure that traffic limit in the core or smsc configuration for smpp 3.4 ? I understand that I can't manage when dlrs will come, but for example we are changing dlr-mask from 31 to 19 (1:received by user + 2:not received by user + 16: not received by SMSC) Regards, Marcelo.
Re: TLV, PATCH and meta-data [solved]
Many thanks for the help. Finally, after some tries, the configuration that worked for me was: group=smpp-tlv name=MAS_APP_ID tag=0x1401 type=nulterminated length=2 group=smpp-tlv name=MAS_SVC_ID tag=0x1402 type=nulterminated length=2 group=smpp-tlv name=MAS_CONT_ID tag=0x1403 type=nulterminated length=1 group=smpp-tlv name=MAS_CONT_DESC tag=0x1404 type=nulterminated length=4 and to send the SMS MT: url = http://xx; . meta-data= . urlencode(?smpp?MAS_APP_ID=53MAS_SVC_ID=13MAS_CONT_ID=1MAS_CONT_DESC=Info); with other types (like octetstring) and sizes the values were sended without the last \00 character and sms mts were rejected by smsc. I hope this help to other people with this same issue. Regards, M On Tuesday 18 November 2008 09:27:31 Alejandro Guerrieri wrote: Marcelo, The meta-data patch has been improved since then and now it has a branch on CVS. You should checkout by running the command: cvs co -r meta-data gateway I've put a copy of Kannel's userguide with the meta-data documentation here: http://www.kannel.org/~aguerrieri/Kannel_meta-data_docs/ Regards, Alejandro Guerrieri On Tue, Nov 18, 2008 at 5:06 AM, Marcelo Aguila [EMAIL PROTECTED] wrote: Hello. I've been reading some threads of this issue and I applied the patch mentioned in http://www.kannel.org/pipermail/devel/2007-August/001156.html But, I don't understand how to use meta-data. My conf file sais: group = smpp-tlv name=MAS_APP_ID tag=0x1401 type=octetstring length=1 name=MAS_SVC_ID tag=0x1402 type=octetstring length=1 name=MAS_CONF_ID tag=0x1403 type=octetstring length=1 name=MAS_CONT_DESC tag=0x1404 type=octetstring length=4 Because operator gave me this values: MAS_APP_ID: 53 MAS_SVC_ID: 13 MAS_CONT_ID: 1 MAS_CONT_DESC: Info This values are used to the billing process in the MT message. So, my doubt is if this is the way to create the url with meta-data value to send sms mt: $md = urlencode(?smpp?MAS_APP_ID=53MAS_SVC_ID=13MAS_CONT_ID=1MAS_CONT_DESC=Info); $url = http://localhost:4000/cgi-bin/sendsms?username=...meta-data=$md;; Because, sms mts are deliverd to the phone, but no charges are made ... Regards, m
TLV, PATCH and meta-data
Hello. I've been reading some threads of this issue and I applied the patch mentioned in http://www.kannel.org/pipermail/devel/2007-August/001156.html But, I don't understand how to use meta-data. My conf file sais: group = smpp-tlv name=MAS_APP_ID tag=0x1401 type=octetstring length=1 name=MAS_SVC_ID tag=0x1402 type=octetstring length=1 name=MAS_CONF_ID tag=0x1403 type=octetstring length=1 name=MAS_CONT_DESC tag=0x1404 type=octetstring length=4 Because operator gave me this values: MAS_APP_ID: 53 MAS_SVC_ID: 13 MAS_CONT_ID: 1 MAS_CONT_DESC: Info This values are used to the billing process in the MT message. So, my doubt is if this is the way to create the url with meta-data value to send sms mt: $md = urlencode(?smpp?MAS_APP_ID=53MAS_SVC_ID=13MAS_CONT_ID=1MAS_CONT_DESC=Info); $url = http://localhost:4000/cgi-bin/sendsms?username=...meta-data=$md;; Because, sms mts are deliverd to the phone, but no charges are made ... Regards, m
dlr table is not empty
Hi, guys. We are using dlr with mysql and at the moment the system is working ok. But, since some weeks ago (probably after some new configuration) the dlr records are not deleted from this table. Is this ok ... or may be we made a mistake with kannel conf files ? Regards, rm
some times dlr never received
Hi, folks. I'm not sure if I'm doing something wrong or I just need to change the DLR management method. We are using kannel 1.4.1 with smpp 3.4. The dlr-mask we have ever used is 31 but in our experience the this operator smsc just answer with (1 or 2 or 8). Well, some times, independent of the price of sms mt (free or not), messages sent just answer dlr 8 (received by smsc) and dlr 1 or dlr 2 is never received. So, I'm not sure if sms mt was received and dlr failed, or not. With some free sms mt, just to check, after a couple of hours with no dlr I've resend the text and the process has finished succesfully (with dlr 1 or dlr 2 received). When I say resend it just the same text plus the same internal message id (managed by us). So my question is if this is a usual behavior used by other users, or if I should dig deeper to find what is happening. Regards, rm
SMS MO Cancelation
Hi, guys. I've got a doubt with this issue. We're impleting a service that sms mo has a cost and sms mt it's free. In the case of system error (for example we couldn't wrote this sms mo transaction into a database), it's possible, in kannel (operator uses smpp), to answer in some way that this sms mo doesn't be charged to the client, because we couldn't finish the transaction succesfully ? Regards, m
Re: Problems using smsbox and bearerbox
Hello. bearerbox should be up and running before smsbox starts. Probably is not the best solution, but in my kannel init script I start bearerbox then I wait for 15 seconds (sleep 15) and then I start smsbox. Regards, R On Friday February 22 2008 16:11, Alvaro Cornejo wrote: smsbox does not start automatically when you start bearerbox and/or wapbox. You should start it manually or with a init script. smsbox and wapbox should be started AFTER bearerbox. On 2/22/08, SSL Admin [EMAIL PROTECTED] wrote: Hi, im having some problem configuring kannel with GSM modem, i have it installed on a debian etch server, version 1.4.1. The problems are: - smsbox doesnt start automatically with bearerbox / wapbox - When i start smsbox and try to send a SMS, i get a message that say that the SMS is qeued and will be sent later. im using this config: group = core admin-port = 13000 smsbox-port = 13001 admin-password = 123 log-file = /var/log/kannel/kannel.log log-level = 0 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 group = smsc smsc = at modemtype = auto device=/dev/ttyACM0 my-number = 584121231231 connect-allow-ip = 127.0.0.1 log-file = /var/log/kannel/modem.log log-level = 0 group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 log-file = /var/log/kannel/smsbox.log log-level = 0 group = sendsms-user username = kanneluser password = 123 concatenation= true max-messages = 10 group = sms-service keyword = keyword-regex = .* catch-all = yes max-messages = 0 get-url = http://localhost/receive?phone=%ptext=%ahttp://localhost/receive?phone=%25ptext=%25a include = /etc/kannel/modems.conf
Re: Kannel connection recovery issues
Hi, Cyrus. I've got same behavior in my server. And I don't have any VPN, so it's something else. Have you found any fix for this. Regards, M. On Friday April 27 2007 11:28, Info wrote: It looks like some ports are not opened correctly? Or perhaps the needed ports are still not release correctly by some thread of kannel in case of the vpn issue? Regards -Original Message- From: Cyrus Patel[EMAIL PROTECTED] Sent: 26/04/07 05:20:44 To: users@kannel.orgusers@kannel.org Subject: Kannel connection recovery issues Hello, I'm having a strange issue with Kannel's recovery behaviour after the connection to the SMSC goes down. I am connected to a SMSC over a VPN connection. Unfortunately for some reason the VPN sometimes goes down and Kannel detects it and reconnects and can receive SMSs but not send them. The kannel status page shows the outgoing messages queuing up: SMS: received 130 (0 queued), sent 48 (10 queued), store size 10 The strange thing is I tried doing the test where I pulled the network cable out and reconnected it and kannel recovers fine. Kannel only seems to be stuck when the VPN goes down. Here is the sequence of events: 1.VPN goes down. Kannel detects this and tries to reconnect: 2007-04-23 18:17:00 [2791] [7] ERROR: SMPP[SMPP::5000/5000::*]: No responses from SMSC within 300 sec. Reconnecting. 2007-04-23 18:17:00 [2791] [7] ERROR: SMPP[SMPP::5000/5000::*]: Couldn't connect to SMS center (retrying in 10 seconds). 2.Kannel successfully reconnects and the enquire links are responded to fine: 2007-04-11 09:03:46 [9121] [7] DEBUG: SMPP PDU 0x86c40b0 dump: 2007-04-11 09:03:46 [9121] [7] DEBUG: type_name: enquire_link 2007-04-11 09:03:46 [9121] [7] DEBUG: command_id: 21 = 0x0015 2007-04-11 09:03:46 [9121] [7] DEBUG: command_status: 0 = 0x 2007-04-11 09:03:46 [9121] [7] DEBUG: sequence_number: 40108 = 0x9cac 2007-04-11 09:03:46 [9121] [7] DEBUG: SMPP PDU dump ends. 2007-04-11 09:03:46 [9121] [7] DEBUG: SMPP[SMPP::5000/5000::*]: Got PDU: 2007-04-11 09:03:46 [9121] [7] DEBUG: SMPP PDU 0x86c40b0 dump: 2007-04-11 09:03:46 [9121] [7] DEBUG: type_name: enquire_link_resp 2007-04-11 09:03:46 [9121] [7] DEBUG: command_id: 2147483669 = 0x8015 2007-04-11 09:03:46 [9121] [7] DEBUG: command_status: 0 = 0x 2007-04-11 09:03:46 [9121] [7] DEBUG: sequence_number: 40108 = 0x9cac 2007-04-11 09:03:46 [9121] [7] DEBUG: SMPP PDU dump ends. 3.SMSs are successfully received but not sent. Restarting kannel solves the problem. This seems to suggest that the Tx TCP connection in kannel has become stale and doesn't reconnect. But then why do the enquire-links work? I assume the tx SMSs and the enquire-links go out on the same connection? If anyone has seen this before it would be very helpful. We're a bit worried because we have to restart kannel almost daily. Thanks, Cyrus Best Regards, Cyrus Patel Senior Software Engineer TEL: +612 9499 9848 MOB: +61 413 685 795 FAX: +612 9499 9845 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Seeker Wireless is a registered trademark of Seeker Wireless Pty. Ltd., ABN 95 106 550 805. This electronic mail includes information from Seeker Wireless Pty Ltd which may be privileged or confidential. This information is for the use of the individual(s) or entity named in the greeting above. If you are not the intended recipient please be aware that any use of this information is prohibited. If you have received this electronic mail in error, please notify the sender (above) by return email.
Re: Kannel start up
smsbox needs that bearerbox is up and running, so maybe you need to add an sleep or something like that to be sure bearerbox is ok before execute smsbox. On Wednesday October 27 2010 06:43, sokha wrote: Hello everyone, I have setuped and running kannel (using binary rpm) but when I reboot my machine ,sometime , smsbox does not start. why? plz help me . My machine is OS: Linux Red Hat Enterprise Linux 4 . ---
problem with one character
Hi. I'm using kannel 1.4.1 and when I send a '_' in a SMS MO i receive a '§' (if you can't see it, it's a symbol like an S). Is there a way to configurate kannel to receive the '_' correctly ? Regards.
SMS MT Conciliation
Hello, guys. I need to conciliate for the first time with an operator. They are using SMPP v3.4 and we are using kannel 1.4.1 CVS. So, the problem is I'm using my own transaction ID in messages/dlrs, but kannel uses another transaction ID with operator. Has anybody worked on a solutions changing the source to solve this problem in the future, or has anybody got a parser to find the correlation between both IDs, from the logs ? Regards, rm
Re: Queued for later delivery (where is the problem and where I should check?)
] [8] DEBUG: data: 31 31 37 5f 37 31 36 5f 35 36 37 26 73 74 61 74 117_716_567stat 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 65 3d 38 26 6d 73 69 73 64 6e 3d 38 33 33 38 34 e=8msisdn=83384 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 34 30 31 26 41 3d 41 43 4b 25 32 46 26 74 73 3d 401A=ACK%2Fts= 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 32 30 30 36 2d 31 32 2d 30 34 2b 31 35 3a 35 31 2006-12-04+15:51 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 3a 31 38 26 6f 70 65 72 3d 32 26 73 6d 73 63 69 :18oper=2smsci 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 64 3d 53 4d 50 50 70 75 62 26 73 79 73 74 79 70 d=SMPPpubsystyp 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 65 3d 4d 53 5f 70 75 62 5f 33 36 38 36 20 48 54 e=MS_pub_3686 HT 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 54 50 2f 31 2e 31 0d 0a 48 6f 73 74 3a 20 6c 6f TP/1.1..Host: lo 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 63 61 6c 68 6f 73 74 0d 0a 55 73 65 72 2d 41 67 calhost..User-Ag 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 65 6e 74 3a 20 4b 61 6e 6e 65 6c 2f 63 76 73 2d ent: Kannel/cvs- 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 32 30 30 36 31 30 31 32 0d 0a 0d 0a 20061012 2006-12-04 12:51:18 [31491] [8] DEBUG: Octet string dump ends. 2006-12-04 12:51:18 [31491] [8] DEBUG: HTTP: Status line: HTTP/1.1 200 OK 2006-12-04 12:51:18 [31491] [8] DEBUG: HTTP: Received response: 2006-12-04 12:51:18 [31491] [8] DEBUG: Octet string at 0x647420: 2006-12-04 12:51:18 [31491] [8] DEBUG: len: 143 2006-12-04 12:51:18 [31491] [8] DEBUG: size: 1024 2006-12-04 12:51:18 [31491] [8] DEBUG: immutable: 0 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 44 61 74 65 3a 20 4d 6f 6e 2c 20 30 34 20 44 65 Date: Mon, 04 De 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 63 20 32 30 30 36 20 31 35 3a 35 31 3a 31 38 20 c 2006 15:51:18 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 47 4d 54 0d 0a 53 65 72 76 65 72 3a 20 41 70 61 GMT..Server: Apa 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 63 68 65 2f 32 2e 32 2e 30 20 28 4c 69 6e 75 78 che/2.2.0 (Linux 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 2f 53 55 53 45 29 0d 0a 58 2d 50 6f 77 65 72 65 /SUSE)..X-Powere 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 64 2d 42 79 3a 20 50 48 50 2f 35 2e 31 2e 32 0d d-By: PHP/5.1.2. 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 0a 43 6f 6e 74 65 6e 74 2d 4c 65 6e 67 74 68 3a .Content-Length: 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 20 30 0d 0a 43 6f 6e 74 65 6e 74 2d 54 79 70 650..Content-Type 2006-12-04 12:51:18 [31491] [8] DEBUG: data: 3a 20 74 65 78 74 2f 68 74 6d 6c 0d 0a 0d 0a : text/html 2006-12-04 12:51:18 [31491] [8] DEBUG: Octet string dump ends. On Thursday November 30 2006 07:13, Ben Suffolk wrote: Did you check the smsc logs as opposed to the core logs? It sounds a bit like the SMPP connection dropped out. This would not show in the main core logs, but in the smsc logs. Regards Ben On 30 Nov 2006, at 10:07, Fourat Zouari wrote: did you reolve the problem ? i've got the same issue than you. I can't reproduce it. On 11/8/06, Marcelo Aguila [EMAIL PROTECTED] wrote: Hi. I'm recently started to work with an operator that use SMPP 3.4 so I'm using kannel 1.4.1 (CVS) in a Dell PowerEdge 2950 with one intel xeon dual core processor. Since the problem started I've not touched nor reinitializing anything to see what is happening. Well, after several days of testing suddenly my logs shows that since 2006-11-02 16:55 to 2006-11-07 17:43 (for 5 days) the sendsms started to return Queued for later delivery (158 messages). So, without any intervention since 2006-11-07 17:53 until now (17 new messages), sendsms started to return Accepted for delivery I could check that first queued message was delivered to SMSC at 2006-11-03 02:41 (almost 12 hours after its creation) and the delivery to the phone was made a minute later at 2:42. Why the messages could be queued for later delivey and why the problem stopped 5 days later without any manual intervention. I'm lost because I can't find any clue in the logs (they are configured in debug mode). What could it be, a configuration problem, a communication problem with operator ? Please, any tip? M.
Re: retries in sms-service when something goes wrong.
Thanks a lot, Ben. But I still have the following doubt. The script service.cgi after a successful processing returns nothing. What HTTP response should it returns if there is a problem and a retry is needed ? Regards, M.- On Thursday November 16 2006 04:55, you wrote: Marcelo, In the group = smsbox section you want to set http-request-retry = x where x is the number of times the retry should happen (default is 0 - no retry) and set http-queue-delay = n to set the number of seconds between retries (defaults to 10 seconds) Regards Ben On 16 Nov 2006, at 03:12, Marcelo Aguila wrote: I've got the following sms-service group = sms-service keyword = default get-url=http://localhost/service.cgi?sender=%pto=%Pmsg=%asmscid= %itime=%tid=%I max-messages = 0 accept-x-kannel-headers = true concatenation = true accepted-smsc = SMPP1 So, when a sms arrives I executed service.cgi. In that script I save the data in a database in a mysql server running in another box. If the record insertion fails, for any reason, I would like to receive same request, every xx seconds, until mysql box is ok. Is it possible to do that with kannel? Regards, M.-
retries in sms-service when something goes wrong.
I've got the following sms-service group = sms-service keyword = default get-url=http://localhost/service.cgi?sender=%pto=%Pmsg=%asmscid=%itime=%tid=%I; max-messages = 0 accept-x-kannel-headers = true concatenation = true accepted-smsc = SMPP1 So, when a sms arrives I executed service.cgi. In that script I save the data in a database in a mysql server running in another box. If the record insertion fails, for any reason, I would like to receive same request, every xx seconds, until mysql box is ok. Is it possible to do that with kannel? Regards, M.-
Delivery reports... help needed
Hi. I've been testing kannel 1.4.1 and some times even I receive the SMSC delivery report very quickly (state 8), the message is succesfully received in the mobile phone but the delivery status 1 takes hours or days to be received by my system. Is there any thing that I should check in my configuration or it's a typical operator problem ? Regards, M.
Queued for later delivery (where is the problem and where I should check?)
Hi. I'm recently started to work with an operator that use SMPP 3.4 so I'm using kannel 1.4.1 (CVS) in a Dell PowerEdge 2950 with one intel xeon dual core processor. Since the problem started I've not touched nor reinitializing anything to see what is happening. Well, after several days of testing suddenly my logs shows that since 2006-11-02 16:55 to 2006-11-07 17:43 (for 5 days) the sendsms started to return Queued for later delivery (158 messages). So, without any intervention since 2006-11-07 17:53 until now (17 new messages), sendsms started to return Accepted for delivery I could check that first queued message was delivered to SMSC at 2006-11-03 02:41 (almost 12 hours after its creation) and the delivery to the phone was made a minute later at 2:42. Why the messages could be queued for later delivey and why the problem stopped 5 days later without any manual intervention. I'm lost because I can't find any clue in the logs (they are configured in debug mode). What could it be, a configuration problem, a communication problem with operator ? Please, any tip? M.
Re: Compiling upon mysql 4
Hello, Julien. I had the same problem using version 1.4.0. The solution is to rename the function list_delete for gw_list_delete (there is a patch for that) or you can start using cvs version of kannel, what is periodically actualized. Regards, M. On Friday 06 October 2006 06:41, Julien Buratto wrote: Upon compiling on fedora core 4 the rpm sources for the stable released 26/9 I'm getting gcc -D_REENTRANT=1 -I. -Igw -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -I/usr/include/libxml2 -I/usr/include/mysql -o gw/dlr_mysql.o -c gw/dlr_mysql.c In file included from /usr/include/mysql/mysql.h:62, from gw/dlr_mysql.c:74: /usr/include/mysql/my_list.h:32: error: conflicting types for ‘list_delete’ ./gwlib/list.h:179: error: previous declaration of ‘list_delete’ was here make: *** [gw/dlr_mysql.o] Error 1 Does anyone has compiled on mysql 4 ? Does anyone suggests to use mysql 3.23 ? Cheers Julien
Site down
Hello, guys. I'm in a hurry, and I really need to get kannel 1.4.1 (CVS), but the site is down. Anybody can give I hand, giving me and altenate location to download it. Regards, Marcelo
Re: site down
mmm .. your right ... now I can access the site. Since yesterday I tried from 3 different places (and ISPs). So .. good news !! On Thursday 05 October 2006 19:56, Iain Dooley wrote: i can get to the site to download the latest tarball, you can't get to kannel.org? cheers iain
