Re: Can Kannel Act as an SMSC
Kok Jeng Loh wrote: Kannel serve as an SMSC and accept CIMD2 from an app server. It will send SMS via a mobile phone attached to it. The important point is can Kannel behave as a CIMD2 server? (For that matter, SMPP, etc. too) No. Kannel can only be a CIMD2 client. It cannot act as a server for SMPP, EMI/UCP, or any of the other SMSC protocols that it understands. However, in a broader sense, Kannel does act as something of an SMSC that speaks HTTP. -- True compassion is more than throwing a coin to a beggar. It demands of our humanity that if we live in a society that produces beggars, we are morally commanded to restructure that society. http://stormwyrm.blogspot.com/
ERROR: SMPP[my_smsc] Unknown clenup action defined 1d.
Dear All I found this error and don't understand the meaning of it, any idea? ERROR: SMPP[my_smsc] Unknown clenup action defined 1d.
Decoding a sms message
Hi all, I'm trying to send wap-cir messages through Kannel. This is done through the PPG with something like this POST /cgi-bin/wap-push.cgi HTTP/1.0 Content-Type: multipart/related; type=application/xml; boundary=EndOfOneEntity User-Agent: Java1.4.2_05 Host: pn.attwireless.net:9002 Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection: Keep-Alive Content-Length: 502 --EndOfOneEntity Content-Type: application/xml; charset=UTF-8 ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id=1031290fab11944511621/WV Push address address-value=WAPPUSH=+4523229536/[EMAIL PROTECTED]/ /push-message /pap --EndOfOneEntity Content-Type: application/vnd.wv.csp.cir X-WAP-Application-Id: x-wap-application:wv.ua WVCI 1.1 QGNUNEUAUK --EndOfOneEntity-- The smsc is set to 'emi'. In bearerbox-access.log this is logged: 2005-09-23 12:20:48 Sent SMS [SMSC:smsc333] [SVC:ppg] [ACT:] [BINF:] [from:1234] [to:+45] [flags:-1:1:-1:-1:0] [msg:120:0006316170706C 69636174696F6E2F766E642E77762E6373702E63697200A96C6962772D7065726C2F352E3639008DC4C3935741502D4170706C69636174696F6E2D49643A20782D7761702D 6170706C69636174696F6E3A77762E75610D0A0D0A5756434920312E312051474E554E455541554B0D0A] [udh:7:0605040B8423F0] Can anyone point me to a document that will help me decode/understand the binary(?) message above? Kind regards, Morten
Re: Decoding a sms message
Hi Morten, The UDH (user data header) looks like it is in the format expected by Nokia phones. Nokia Smart Messaging is discussed here: http://www.forum.nokia.com/html_reader/main/1,4997,2452,00.html If you aren't sending to a Nokia then this might explain why you see a problem. The msg parameter is encoded in ASCII, presented as a hex string. Split the string into 2 character chunks and these will be the ascii values of various characters. The first two characters are unprintable ones, after that we have text that starts, [31] [61] [70] [70] which translates to 1app, and so on. Guides to ASCII and tools to help translate it are common enough to find online. Yours, Toby Wright The smsc is set to 'emi'. In bearerbox-access.log this is logged: 2005-09-23 12:20:48 Sent SMS [SMSC:smsc333] [SVC:ppg] [ACT:] [BINF:] [from:1234] [to:+45] [flags:-1:1:-1:-1:0] [msg:120:0006316170706C 69636174696F6E2F766E642E77762E6373702E63697200A96C6962772D7065726C2F352E3639008DC4C3935741502D4170706C69636174696F6E2D49643A20782D7761702D 6170706C69636174696F6E3A77762E75610D0A0D0A5756434920312E312051474E554E455541554B0D0A] [udh:7:0605040B8423F0] Can anyone point me to a document that will help me decode/understand the binary(?) message above? Kind regards, Morten -- Toby WrightEmbrace Mobile +44-1865-811197 http://www.embracemobile.com
DLR: storage type defined as 'mysql', but no MySQL support build in!
Hello, I have KAnnel configured as a working SMS gateway but I does not remember DLRs in memory internal so I decided to sotre the externally. But I constantly got this message: DLR: storage type defined as 'mysql', but no MySQL support build in! I did a ./configure --with-mysql=/usr --enable-mysql Output: Configuring DB support ... checking whether to compile with MySQL support... searching in /usr checking for /usr/include/mysql/mysql.h... (cached) yes checking for mysql/mysql.h... (cached) yes checking for mysql/mysql_com.h... (cached) yes checking for mysql/mysql_version.h... (cached) yes checking for mysql_init in -lmysqlclient... (cached) yes checking whether to compile with MySQL support... yes checking whether to compile with LibSDB support... disabled This all looks good to me, but is keeps giving the same error after a make and make install. Can anyone point me to some directions? Thanks, Boudewijn van Breukelen
RE: storage type defined as 'mysql', but no MySQL support build in!
Do you have a group = mysql as well as a group = dlr-db in your kannel.conf? Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of B. van Breukelen Sent: maandag 3 oktober 2005 16:50 To: users@kannel.org Subject: DLR: storage type defined as 'mysql', but no MySQL support build in! Hello, I have KAnnel configured as a working SMS gateway but I does not remember DLRs in memory internal so I decided to sotre the externally. But I constantly got this message: DLR: storage type defined as 'mysql', but no MySQL support build in! I did a ./configure --with-mysql=/usr --enable-mysql Output: Configuring DB support ... checking whether to compile with MySQL support... searching in /usr checking for /usr/include/mysql/mysql.h... (cached) yes checking for mysql/mysql.h... (cached) yes checking for mysql/mysql_com.h... (cached) yes checking for mysql/mysql_version.h... (cached) yes checking for mysql_init in -lmysqlclient... (cached) yes checking whether to compile with MySQL support... yes checking whether to compile with LibSDB support... disabled This all looks good to me, but is keeps giving the same error after a make and make install. Can anyone point me to some directions? Thanks, Boudewijn van Breukelen
Black list functionality
Dear List, I'm trying to use the black-list functionality for Kannel, but I'm having some problemas: 1. If I use the black-list directive on the core group, it works as expected (I mean: it REJECTS messages) but I cannot use the black-list group to send a custom message to the rejected addressess. 2. If I use the black-list directive on the sms-service or smsbox group, it just gets ignored and the messages pass as if there's not black-list directive. My kannel.conf highlights: group = core admin-port = 13010 smsbox-port = 13011 wapbox-port = 13012 wdp-interface-name = * admin-password = 12345 status-password = 54321 dlr-storage = internal admin-allow-ip = 127.0.0.1; box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1; access-log = /var/log/kannel/access.log log-file = /var/log/kannel/kannel.log log-level = 2 store-file = /home/kannel/kannel.store #If I put the black-list here it DISCARDS messages but no notification is being sent to the client #black-list = http://my.url.com/bl/blacklist.txt ... group = sqlbox id = mydlr smsbox-id = sqlbox bearerbox-host = 127.0.0.1 smsbox-port = 13015 smsbox-port-ssl = false sql-log-table = sent_sms sql-insert-table = send_sms log-file = /var/log/kannel/sqlbox.log log-level = 2 ... group = smsbox bearerbox-host = localhost sendsms-port = 13013 log-file = /var/log/kannel/smsbox.log access-log = /var/log/kannel/access.log log-level = 2 http-request-retry = 5 #If I put the black-list directive here it gets ignored #black-list = http://my.url.com/bl/blacklist.txt ... group = sms-service keyword = default post-url = http://my.url.com/inbound.php?from=%pto=%Pmsg=lm%20%adate=%tsmsc=%i; accepted-smsc = smsc1;smsc2; #If I put the black-list directive here it gets ignored #black-list = http://my.url.com/bl/blacklist.txt max-messages = 0 group = sms-service keyword = black-list text = You are denied, go away! accepted-smsc = smsc1;smsc2; max-messages = 1 BTW, I'm using Kannel 1.4.0 patched with SQLBox on CentOS 3.3. Thank you in advance, -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/
Re: Can Kannel Act as an SMSC
On Mon, 2005-10-03 at 14:37 +0800, Rafael 'Dido' Sevilla wrote: No. Kannel can only be a CIMD2 client. It cannot act as a server for SMPP, EMI/UCP, or any of the other SMSC protocols that it understands. However, in a broader sense, Kannel does act as something of an SMSC that speaks HTTP. I think we should add this to FAQ. -- .O. ..O Enver ALTIN | http://skyblue.gen.tr/ OOO Software developer @ Parkyeri | http://www.parkyeri.com/ signature.asc Description: This is a digitally signed message part
