Why does Kannel not use sar_total_segments and sar_segment_seqnum when sending concatenated sms?
Hi I was looking through the logs and saw that Kannel sends concatenated SMSs using UDH in the Short Message fields. From reading the SMPP spec I was under the impression that the same thing could be achieved by using sar_total_segments and sar_segment_seqnum. Did I misinterpret the spec or does Kannel not use these fields for another reason such as unreliable implementation on the receiving SMSC. Regards,
Re: DLR mysql not supported
The user guide was not meant to be distro specific. Glad to here you finally got it working. Cheers! On 1/12/11, atulra...@gmail.com atulra...@gmail.com wrote: It worked with Yum groupistall MySQL Database Yum install mysql-devel And ./configure --with-mysql I don't know why these things are not in user guide Thanks all Atul Sent from my BlackBerry® wireless device -Original Message- From: Rene Kluwen rene.klu...@chimit.nl Sender: users-boun...@kannel.org Date: Tue, 11 Jan 2011 20:51:53 To: 'Alejandro Guerrieri'alejandro.guerri...@gmail.com; 'Kazi M'm.a.a.z.k.a@gmail.com Cc: users@kannel.org Subject: RE: DLR mysql not supported I remember I had to upgrade my mysql to 5.0 or something like that, time ago. From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Alejandro Guerrieri Sent: Tuesday, 11 January, 2011 18:04 To: Kazi M Cc: users@kannel.org Subject: Re: DLR mysql not supported It should work perfectly fine with any mysql version, as long as you have the proper packages and client libraries in place. Regards, Alex On Tue, Jan 11, 2011 at 2:20 PM, Kazi M m.a.a.z.k.a@gmail.com wrote: Dear Atul , if after installing the devel package ... the problems still persists then try downloading lower versions of mysql i m using 4.22 Atul Rastogi wrote: I am running gateway150 with centos 5.5 in test setup while trying to setup for DLR storage I am getting message DLR storage type mysql not supported when running ./bearerbox -v 1 smskannel.conf file contains following and dlr-storage = mysql in core group group = mysql-connection id = mydlr host = localhost username = root database = dlr max-connections = 1 group = dlr-db id = mydlr table = dlr field-smsc = smsc field-timestamp = ts field-destination = destination field-source = source field-url = url field-mask = mask field-status = status field-boxc-id = boxc Pl help Thanks Atul -- View this message in context: http://old.nabble.com/DLR-mysql-not-supported-tp30628434p30643513.html Sent from the Kannel - User mailing list archive at Nabble.com. -- Sent from my mobile device Mfawa Alfred Onen M.Sc Telecoms, B.Eng Elect/Elect, CCNA, RHCE(in view) System Administrator Department of Computer Science, Bingham University. E-Mail: systemad...@binghamuni.edu.ng Phone1: +234 805 944 3154 Phone2: +234 803 079 6088
RE: [SOLVED] Change the log level of an smpp smsc group
Hi All, I confirm that the log-level http command resets the log level of all log files defined in the configuration, without restarting anything. That is exactly what I want. Unfortunately, the UG is not very specific on that. Thanks a lot for your help. TSHIMANGA Minkoka VAS Manager È +243 814443113 • + 243 815560341 ext. 0583 • +243 813010373 • tshimanga.mink...@vodacom.cdmailto:tshimanga.mink...@vodacom.cd [cid:image003.jpg@01CBB31B.8281E1B0] From: Alejandro Guerrieri [mailto:alejandro.guerri...@gmail.com] Sent: Thursday 13 January 2011 08:31 To: Tshimanga Minkoka Cc: Rapture; users@kannel.org Subject: Re: Change the log level of an smpp smsc group The stop-smsc and start-smsc can be performed without restarting kannel, it will only reconnect the given smsc. Regards, -- Alex Guerrieri On 13/01/2011, at 07:58, Tshimanga Minkoka tshimanga.mink...@vodacom.cdmailto:tshimanga.mink...@vodacom.cd wrote: Hi Rapture, Sorry I had to specify that I needed it on the fly, without restarting kannel. Alex have answered specifying that the http command changes all the log levels (SMSCs included). I will give it a try, and feedback. Thanks to all. TSHIMANGA Minkoka VAS Manager È +243 814443113 • + 243 815560341 ext. 0583 • +243 813010373 • tshimanga.mink...@vodacom.cdmailto:tshimanga.mink...@vodacom.cd image001.jpg From: Rapture [mailto:supp...@ims.co.ke] Sent: Wednesday 12 January 2011 17:25 To: Tshimanga Minkoka; users@kannel.orgmailto:users@kannel.org Subject: RE: Change the log level of an smpp smsc group Hi, You need to modify the variable log-level in the group smsc and set it to the desired level. This you do per smcs Check user guide: log-level number 0..5 Minimum level of log-file events logged. 0 is for ’debug’, 1 ’info’,2 ’warning, 3 ’error’ and 4’panic’ From: users-boun...@kannel.orgmailto:users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Tshimanga Minkoka Sent: Wednesday, January 12, 2011 7:16 PM To: users@kannel.orgmailto:users@kannel.org Subject: Change the log level of an smpp smsc group Dear, How can I change the log level of an smpp smsc group? The HTTP administration command loglevel seems to only act on bearbox logging. Do I need to modify the configuration file, stop the smsc and then restart it? TIA. TSHIMANGA Minkoka VAS Manager È +243 814443113 • + 243 815560341 ext. 0583 • +243 813010373 • tshimanga.mink...@vodacom.cdmailto:tshimanga.mink...@vodacom.cd image004.jpg inline: image003.jpg
Re: [SOLVED] Change the log level of an smpp smsc group
loglevel: Set Kannel log-level of log-files while running. This allows you to change the current log-level of the log-files on the fly. Looks perfectly clear to me... Regards, Alex On Thu, Jan 13, 2011 at 12:15 PM, Tshimanga Minkoka tshimanga.mink...@vodacom.cd wrote: Hi All, I confirm that the log-level http command resets the log level of all log files defined in the configuration, without restarting anything. That is exactly what I want. Unfortunately, the UG is not very specific on that. Thanks a lot for your help. *TSHIMANGA Minkoka* *VAS Manager* *È** **+243 814443113* *(** **+* *243 815560341 ext. 0583* *2** **+243 813010373* *: **tshimanga.mink...@vodacom.cd* *From:* Alejandro Guerrieri [mailto:alejandro.guerri...@gmail.com] *Sent:* Thursday 13 January 2011 08:31 *To:* Tshimanga Minkoka *Cc:* Rapture; users@kannel.org *Subject:* Re: Change the log level of an smpp smsc group The stop-smsc and start-smsc can be performed without restarting kannel, it will only reconnect the given smsc. Regards, -- Alex Guerrieri On 13/01/2011, at 07:58, Tshimanga Minkoka tshimanga.mink...@vodacom.cd wrote: Hi Rapture, Sorry I had to specify that I needed it on the fly, without restarting kannel. Alex have answered specifying that the http command changes all the log levels (SMSCs included). I will give it a try, and feedback. Thanks to all. *TSHIMANGA Minkoka* *VAS Manager* *È** **+243 814443113* *(** **+* *243 815560341 ext. 0583* *2** **+243 813010373* *: **tshimanga.mink...@vodacom.cd* image001.jpg *From:* Rapture [mailto:supp...@ims.co.ke] *Sent:* Wednesday 12 January 2011 17:25 *To:* Tshimanga Minkoka; users@kannel.org *Subject:* RE: Change the log level of an smpp smsc group Hi, You need to modify the variable log-level in the group smsc and set it to the desired level. This you do per smcs Check user guide: log-level number 0..5 Minimum level of log-file events logged. 0 is for ’debug’, 1 ’info’,2 ’warning, 3 ’error’ and 4’panic’ *From:* users-boun...@kannel.org [mailto:users-boun...@kannel.org] *On Behalf Of *Tshimanga Minkoka *Sent:* Wednesday, January 12, 2011 7:16 PM *To:* users@kannel.org *Subject:* Change the log level of an smpp smsc group Dear, How can I change the log level of an smpp smsc group? The HTTP administration command loglevel seems to only act on bearbox logging. Do I need to modify the configuration file, stop the smsc and then restart it? TIA. *TSHIMANGA Minkoka* *VAS Manager* *È** **+243 814443113* *(** **+* *243 815560341 ext. 0583* *2** **+243 813010373* *: **tshimanga.mink...@vodacom.cd* image004.jpg
Re: Kannel sending sms but not receiving
Thanks Alvaro, I have changed my conf file to the one below but no change. I am still not receiving sms group = core admin-port = 13000 admin-password = foo status-password = foo_status smsbox-port = 13001 log-file = /var/log/kannel/kannel.log log-level = 0 access-log = /var/log/kannel/kannel.access group = smsc smsc = at modemtype = huawei device=/dev/ttyUSB1 log-file = /var/log/kannel/modems.log log-level = 0 group = modems id = huawei name = huawei detect-string = huawei init-string = ATZ init-string = ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 init-string = AT+CNMI= 2,0,0,2,0;+CMEE=1 group = smsbox bearerbox-host = localhost sendsms-port = 13013 sendsms-chars = 0123456789 global-sender = 123456 access-log = /var/log/kannel/kannel.access log-file = /var/log/kannel/smsbox.log log-level = 0 group = sendsms-user username=agile password=agile max-messages = 10 concatenation = true #default service group = sms-service keyword = default text = test response group = sms-service keyword =.* get-url = http://192.168.1.1/smsscript.php?phone=%ptext=%a; *my modems log* 2011-01-13 10:13:11 [18262] [6] INFO: AT2[/dev/ttyUSB1]: trying to use speed 9600 from modem definition 2011-01-13 10:13:11 [18262] [6] INFO: AT2[/dev/ttyUSB1]: opening device 2011-01-13 10:13:11 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: device opened. Telnet mode = 0 2011-01-13 10:13:11 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: device opened 2011-01-13 10:13:11 [18262] [6] INFO: AT2[/dev/ttyUSB1]: speed set to 9600 2011-01-13 10:13:11 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ^M 2011-01-13 10:13:13 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- AT^M 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:14 [18262] [6] INFO: AT2[/dev/ttyUSB1]: Closing device 2011-01-13 10:13:14 [18262] [6] INFO: AT2[/dev/ttyUSB1]: speed is 9600 2011-01-13 10:13:14 [18262] [6] INFO: AT2[/dev/ttyUSB1]: opening device 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: device opened. Telnet mode = 0 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: device opened 2011-01-13 10:13:14 [18262] [6] INFO: AT2[/dev/ttyUSB1]: Logging in 2011-01-13 10:13:14 [18262] [6] INFO: AT2[/dev/ttyUSB1]: init device 2011-01-13 10:13:14 [18262] [6] INFO: AT2[/dev/ttyUSB1]: speed set to 9600 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ATZ^M 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- AT^M 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- AT 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ATF^M 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ATF 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ATE0^M 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ATE0 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- AT+IFC=2,2^M 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- AT+CPIN?^M 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- +CPIN: READY 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- AT+CMGF=0^M 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- AT+CSMS=?^M 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- AT+CNMI= 2,0,0,2,0;+CMEE=1^M 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- +CSMS: (0-1) 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:15 [18262] [6] INFO: AT2[/dev/ttyUSB1]: AT SMSC successfully opened. 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ^BOOT:33948656,0,0,0,75 2011-01-13 10:13:45 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ^BOOT:33948656,0,0,0,75 2011-01-13 10:14:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ^BOOT:33948656,0,0,0,75 2011-01-13 10:14:45 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ^BOOT:33948656,0,0,0,75 2011-01-13 10:15:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ^BOOT:33948656,0,0,0,75 2011-01-13 10:15:45 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ^BOOT:33948656,0,0,0,75 2011-01-13 10:16:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ^BOOT:33948656,0,0,0,75
Re: Kannel sending sms but not receiving
Thanks Joseph. I am forwarding the incoming messages to a database using the php script. I am already running the logs at level 0, but I can't see the messages On Thu, Jan 13, 2011 at 4:54 PM, Joseph Koech kipponthe...@gmail.comwrote: Mutuku, Your configuration looks ok. May I know where you are trying to forward the incoming messages? I see you have included a get-url parameter that should submit the incoming smses to a certain application. You can trying running the logs at level 0 and see what happens when an incoming message is received. On Thu, Jan 13, 2011 at 12:55 AM, Mutuku Ndeti jnmut...@gmail.com wrote: Thanks Alvaro, I have changed my conf file to the one below but no change. I am still not receiving sms group = core admin-port = 13000 admin-password = foo status-password = foo_status smsbox-port = 13001 log-file = /var/log/kannel/kannel.log log-level = 0 access-log = /var/log/kannel/kannel.access group = smsc smsc = at modemtype = huawei device=/dev/ttyUSB1 log-file = /var/log/kannel/modems.log log-level = 0 group = modems id = huawei name = huawei detect-string = huawei init-string = ATZ init-string = ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 init-string = AT+CNMI= 2,0,0,2,0;+CMEE=1 group = smsbox bearerbox-host = localhost sendsms-port = 13013 sendsms-chars = 0123456789 global-sender = 123456 access-log = /var/log/kannel/kannel.access log-file = /var/log/kannel/smsbox.log log-level = 0 group = sendsms-user username=agile password=agile max-messages = 10 concatenation = true #default service group = sms-service keyword = default text = test response group = sms-service keyword =.* get-url = http://192.168.1.1/smsscript.php?phone=%ptext=%a; my modems log 2011-01-13 10:13:11 [18262] [6] INFO: AT2[/dev/ttyUSB1]: trying to use speed 9600 from modem definition 2011-01-13 10:13:11 [18262] [6] INFO: AT2[/dev/ttyUSB1]: opening device 2011-01-13 10:13:11 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: device opened. Telnet mode = 0 2011-01-13 10:13:11 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: device opened 2011-01-13 10:13:11 [18262] [6] INFO: AT2[/dev/ttyUSB1]: speed set to 9600 2011-01-13 10:13:11 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ^M 2011-01-13 10:13:13 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- AT^M 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:14 [18262] [6] INFO: AT2[/dev/ttyUSB1]: Closing device 2011-01-13 10:13:14 [18262] [6] INFO: AT2[/dev/ttyUSB1]: speed is 9600 2011-01-13 10:13:14 [18262] [6] INFO: AT2[/dev/ttyUSB1]: opening device 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: device opened. Telnet mode = 0 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: device opened 2011-01-13 10:13:14 [18262] [6] INFO: AT2[/dev/ttyUSB1]: Logging in 2011-01-13 10:13:14 [18262] [6] INFO: AT2[/dev/ttyUSB1]: init device 2011-01-13 10:13:14 [18262] [6] INFO: AT2[/dev/ttyUSB1]: speed set to 9600 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ATZ^M 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- AT^M 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- AT 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ATF^M 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ATF 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:14 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ATE0^M 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ATE0 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- AT+IFC=2,2^M 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- AT+CPIN?^M 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- +CPIN: READY 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- AT+CMGF=0^M 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- AT+CSMS=?^M 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- AT+CNMI= 2,0,0,2,0;+CMEE=1^M 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- +CSMS: (0-1) 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:15 [18262] [6] INFO: AT2[/dev/ttyUSB1]: AT SMSC successfully opened. 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- OK 2011-01-13 10:13:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ^BOOT:33948656,0,0,0,75 2011-01-13 10:13:45 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: -- ^BOOT:33948656,0,0,0,75 2011-01-13 10:14:15 [18262] [6] DEBUG: AT2[/dev/ttyUSB1]: --
Re: smsc gsm encoding
for those to whom this was not obvious like to me, not specifying alt-charset parameter makes kannel communicate with smsc in gms encoding (which is the default encoding meant by kannel documentation but not mentioned anywhere). unfortunatelly, it does not work if your message length is more than 160 characters, in such case, the message is split and both parts are sent as binary data and not encoded to gsm encoding. miroslav Dne 5.1.2011 11:06, Miroslav Šulc napsal(a): hi, i went through documentation and did not see answer for my question, so asking here. i have configured smsc connection in bearerbox config. the connection works fine, but atm i use iso-8859-1 encoding. i'd like to switch to gsm (7 bit) encoding but from the documentation it is not clear to me whether that encoding is supported and how to configure it. thanks for any help. miroslav
Re: Kannel sending sms but not receiving
I think the issue is that kannel is not receiving the smses, becuause I cannot see them on the log files I am not sure what is wrong with my conf.