no-smsc = false [Default] Is this a bug?
Dear Kannel users, I tested phone with kannel, and find a strange behaviour: If the no-smsc clause in modems.conf is explicitly set to false, which is default, kannel will NO pre-fix 00 to the string it send to phone. I have this line in my modem.conf no-smsc = false [Default] And Kannel send this string to phone: 2011-01-13 15:28:47 [8114] [6] DEBUG: AT2[/dev/ttyACM0]: -- 1100088118327409A707F4F29C9E769F01 Note that the string is not prefixed with '00', which means use default smsc number from SIM card. The phone returns error on this string. After I comment off the above no-smsc clause in conf file, kannel will pre fix '00' to the string and phone will send sms out as expected. However, Kannel user manual said no-smsc default value is false, which is same as the no-smsc clause in conf file. So someone please check if the clause is parsed correctly. I am still not able to receive sms. Will probe further, and may post here again. Helen
Re: no-smsc = false [Default] Is this a bug?
I am using Kannel 1.4.3: 2011-01-14 17:27:52 [7450] [0] DEBUG: Kannel smsbox version `1.4.3'. Build `Dec 27 2010 16:55:34', compiler `4.1.2 20070925 (Red Hat 4.1.2-27)'. System Linux, release 2.6.23.17-88.fc7, version #1 SMP Thu May 15 00:35:10 EDT 2008, machine i686. smskannel.conf as follow: # # THIS IS A SAMPLE CONFIGURATION FOR SMS KANNEL # # This basic version is used for system testing. It expects 'fakesmsc' to # send messages which are replied with simple fixed text message. # It is run like this: # # 1% gw/bearerbox gw/smskannel.conf # 2% gw/smsbox gw/smskannel.conf # 3% test/fakesmsc -i 0.1 -m 100 123 345 text nop # # ..all 3 commands in separate shells (or screen sessions) # Note that you can run them in different machines but have to # add certain command line argument and configuration variables then # # # For any modifications to this file, see Kannel User Guide # If that does not help, see Kannel web page (http://www.kannel.org) and # various online help and mailing list archives # # Notes on those who base their configuration on this: # 1) check security issues! (allowed IPs, passwords and ports) # 2) groups cannot have empty rows inside them! # 3) read the user guide # # Kalle Marjola for Kannel project 2001, 2004 #- # CORE # # There is only one core group and it sets all basic settings # of the bearerbox (and system). You should take extra notes on # configuration variables like 'store-file' (or 'store-dir'), # 'admin-allow-ip' and 'access.log' group = core admin-port = 13000 smsbox-port = 13001 admin-password = bar #status-password = foo #admin-deny-ip = #admin-allow-ip = #log-file = /tmp/kannel.log #log-level = 0 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 #unified-prefix = +358,00358,0;+,00 #access-log = /tmp/access.log #store-file = kannel.store #ssl-server-cert-file = cert.pem #ssl-server-key-file = key.pem #ssl-certkey-file = mycertandprivkeyfile.pem #- # SMSC CONNECTIONS # # SMSC connections are created in bearerbox and they handle SMSC specific # protocol and message relying. You need these to actually receive and send # messages to handset, but can use GSM modems as virtual SMSCs # This is a fake smsc connection, _only_ used to test the system and services. # It really cannot relay messages to actual handsets! #group = smsc #smsc = fake #smsc-id = FAKE #port = 1 #connect-allow-ip = 127.0.0.1 group = smsc smsc = at modemtype = moto device=/dev/ttyACM0 my-number = 123123123123 connect-allow-ip = 127.0.0.1 log-level = 0 #- # SMSBOX SETUP # # Smsbox(es) do higher-level SMS handling after they have been received from # SMS centers by bearerbox, or before they are given to bearerbox for delivery group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 global-sender = 13013 sendsms-chars = 0123456789 +- #log-file = /tmp/smsbox.log log-level = 0 #access-log = /tmp/access.log #- # SEND-SMS USERS # # These users are used when Kannel smsbox sendsms interface is used to # send PUSH sms messages, i.e. calling URL like # http://kannel.machine:13013/cgi-bin/sendsms?username=testerpassword=foobar... group = sendsms-user username = tester password = foobar #user-deny-ip = #user-allow-ip = concatenation= true max-messages = 10 #- # SERVICES # # These are 'responses' to sms PULL messages, i.e. messages arriving from # handsets. The response is based on message content. Only one sms-service is # applied, using the first one to match. group = sms-service #keyword = default keyword-regex = .* catch-all = yes max-messages = 0 get-url = http://localhost/~xx #text = default sms service no url #group = sms-service #keyword = nop #text = You asked nothing and I did it! # There should be always a 'default' service. This service is used when no # other 'sms-service' is applied. #group = sms-service #keyword = default #text = No service specified include = /usr/local/kannel/modems.conf modems.conf as follow: # Modems configuration # # Example and default values # # group = modems # id = my-id # name = my-name # detect-string = MODEM # detect-string2 = [Default] # init-string = AT+CNMI=1,2,0,0,0 [Default] # speed = 9600 [Default] # enable-hwhs = AT+IFC=2,2 [Default] # need-sleep = false [Default] # no-pin = false [Default] # no-smsc = false [Default] # sendline-sleep = 100 [Default, miliseconds] # keepalive-cmd = AT [Default] # broken = false [Default] # message-storage = SM # enable-mms = false [Default] # If modemtype=auto, try everyone and defaults to this one group = modems id = generic name = Generic Modem group = modems id = moto name = 'motorola phone' #init-string = AT+CGDCONT=1 # init-string = ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 # detect-string = MODEM # detect-string2 = [Default] init-string = AT+CNMI=3,2,0,0,0 # speed
Re: Kannel sending sms but not receiving
Hi You need to make yor modem pass MO messages to kannel in order to have kannel place them in the DB. For this to happen, you need to configure your phone/modem with CNMI command. try with AR+CNMI? to see if the command is accepted by your modem and see the possible values. Then test with different values. another option is to tell kannel to seek for the MO in the modem/phone. For this use sim-buffering in modem config. Read UG for more details Regards Alvaro |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com On Fri, Jan 14, 2011 at 12:00 AM, Mutuku Ndeti jnmut...@gmail.com wrote: 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.
Re: Kannel sending sms but not receiving
sorry for the typho is AT+CNMI? not AR+CNMI? |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com On Fri, Jan 14, 2011 at 8:20 AM, Alvaro Cornejo cornejo.alv...@gmail.com wrote: Hi You need to make yor modem pass MO messages to kannel in order to have kannel place them in the DB. For this to happen, you need to configure your phone/modem with CNMI command. try with AR+CNMI? to see if the command is accepted by your modem and see the possible values. Then test with different values. another option is to tell kannel to seek for the MO in the modem/phone. For this use sim-buffering in modem config. Read UG for more details Regards Alvaro |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com On Fri, Jan 14, 2011 at 12:00 AM, Mutuku Ndeti jnmut...@gmail.com wrote: 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.
ESME Client not connecting to OpenSmppbox
Hello everyone, I have installed opensmppbox on a centOS server and have configured it with a client, but the client is not able to connect. When the client tries to connect it gives SMSC rejected login to transmit, code 0x000d (Bind Failed). Couldn't connect to SMS center (retrying in 10 seconds). On the server side, it gives this error, Invalid SMPP PDU received. Server Bearerbox log 2011-01-15 13:07:37 [26155] [5] INFO: Client connected from 127.0.0.1 2011-01-15 13:07:37 [26155] [5] DEBUG: Started thread 45 (gw/bb_boxc.c:function) 2011-01-15 13:07:37 [26155] [45] DEBUG: Thread 45 (gw/bb_boxc.c:function) maps to pid 26155. 2011-01-15 13:07:37 [26155] [45] DEBUG: Started thread 46 (gw/bb_boxc.c:boxc_sender) 2011-01-15 13:07:37 [26155] [46] DEBUG: Thread 46 (gw/bb_boxc.c:boxc_sender) maps to pid 26155. 2011-01-15 13:07:40 [26155] [45] INFO: Connection closed by the box 127.0.0.1 2011-01-15 13:07:40 [26155] [46] DEBUG: send_msg: sending msg to box: 127.0.0.1 2011-01-15 13:07:40 [26155] [46] DEBUG: Thread 46 (gw/bb_boxc.c:boxc_sender) terminates. 2011-01-15 13:07:40 [26155] [45] DEBUG: Thread 45 (gw/bb_boxc.c:function) terminates. 2011-01-15 13:07:48 [26155] [5] INFO: Client connected from 127.0.0.1 2011-01-15 13:07:48 [26155] [5] DEBUG: Started thread 47 (gw/bb_boxc.c:function) 2011-01-15 13:07:48 [26155] [47] DEBUG: Thread 47 (gw/bb_boxc.c:function) maps to pid 26155. 2011-01-15 13:07:48 [26155] [47] DEBUG: Started thread 48 (gw/bb_boxc.c:boxc_sender) 2011-01-15 13:07:48 [26155] [48] DEBUG: Thread 48 (gw/bb_boxc.c:boxc_sender) maps to pid 26155. 2011-01-15 13:07:51 [26155] [47] INFO: Connection closed by the box 127.0.0.1 2011-01-15 13:07:51 [26155] [48] DEBUG: send_msg: sending msg to box: 127.0.0.1 2011-01-15 13:07:51 [26155] [48] DEBUG: Thread 48 (gw/bb_boxc.c:boxc_sender) terminates. 2011-01-15 13:07:51 [26155] [47] DEBUG: Thread 47 (gw/bb_boxc.c:function) terminates. 2011-01-15 13:07:59 [26155] [5] INFO: Client connected from 127.0.0.1 2011-01-15 13:07:59 [26155] [5] DEBUG: Started thread 49 (gw/bb_boxc.c:function) 2011-01-15 13:07:59 [26155] [49] DEBUG: Thread 49 (gw/bb_boxc.c:function) maps to pid 26155. 2011-01-15 13:07:59 [26155] [49] DEBUG: Started thread 50 (gw/bb_boxc.c:boxc_sender) 2011-01-15 13:07:59 [26155] [50] DEBUG: Thread 50 (gw/bb_boxc.c:boxc_sender) maps to pid 26155. 2011-01-15 13:08:02 [26155] [49] INFO: Connection closed by the box 127.0.0.1 2011-01-15 13:08:02 [26155] [50] DEBUG: send_msg: sending msg to box: 127.0.0.1 2011-01-15 13:08:02 [26155] [50] DEBUG: Thread 50 (gw/bb_boxc.c:boxc_sender) terminates. 2011-01-15 13:08:02 [26155] [49] DEBUG: Thread 49 (gw/bb_boxc.c:function) terminates. Server Opensmppbox log 2011-01-15 13:06:40 [28249] [25] INFO: Client connected from 40.100.0.000 2011-01-15 13:06:40 [28249] [25] DEBUG: Connecting to 127.0.0.1 2011-01-15 13:06:40 [28249] [25] INFO: Connected to bearerbox at localhost port 13001. 2011-01-15 13:06:40 [28249] [25] DEBUG: Started thread 26 (opensmppbox.c:smpp_to_bearerbox) 2011-01-15 13:06:40 [28249] [26] DEBUG: Thread 26 (opensmppbox.c:smpp_to_bearerbox) maps to pid 28249. 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP[opensmppbox]: Got PDU: 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP PDU 0x4ea0170 dump: 2011-01-15 13:06:41 [28249] [26] DEBUG: type_name: bind_transceiver 2011-01-15 13:06:41 [28249] [26] DEBUG: command_id: 9 = 0x0009 2011-01-15 13:06:41 [28249] [26] DEBUG: command_status: 0 = 0x 2011-01-15 13:06:41 [28249] [26] DEBUG: sequence_number: 13 = 0x000d 2011-01-15 13:06:41 [28249] [26] DEBUG: system_id: 12345 2011-01-15 13:06:41 [28249] [26] DEBUG: password: 12345 2011-01-15 13:06:41 [28249] [26] DEBUG: system_type: vma 2011-01-15 13:06:41 [28249] [26] DEBUG: interface_version: 52 = 0x0034 2011-01-15 13:06:41 [28249] [26] DEBUG: addr_ton: 0 = 0x 2011-01-15 13:06:41 [28249] [26] DEBUG: addr_npi: 1 = 0x0001 2011-01-15 13:06:41 [28249] [26] DEBUG: address_range: NULL 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP PDU dump ends. 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP[opensmppbox]: Sending PDU: 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP PDU 0x4ea38a0 dump: 2011-01-15 13:06:41 [28249] [26] DEBUG: type_name: bind_transceiver_resp 2011-01-15 13:06:41 [28249] [26] DEBUG: command_id: 2147483657 = 0x8009 2011-01-15 13:06:41 [28249] [26] DEBUG: command_status: 13 = 0x000d 2011-01-15 13:06:41 [28249] [26] DEBUG: sequence_number: 13 = 0x000d 2011-01-15 13:06:41 [28249] [26] DEBUG: system_id: NULL 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP PDU dump ends. 2011-01-15 13:06:42 [28249] [26] ERROR: Invalid SMPP PDU received. 2011-01-15 13:06:42 [28249] [26] DEBUG: Thread 26 (opensmppbox.c:smpp_to_bearerbox) terminates. 2011-01-15 13:06:43 [28249] [25] DEBUG: Thread 25 (opensmppbox.c:function) terminates. Client bearerbox log 2011-01-14 14:19:13 [20507] [6] DEBUG: SMPP[ukserver]: Sending PDU: 2011-01-14 14:19:13 [20507] [6] DEBUG: SMPP PDU
RE: ESME Client not connecting to OpenSmppbox
In /etc/smpplogin.txt, try: 1234512345vma *.*.*.* == Rene From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of David Ige: Cellulant Sent: Friday, 14 January, 2011 14:54 To: users@kannel.org Subject: ESME Client not connecting to OpenSmppbox Hello everyone, I have installed opensmppbox on a centOS server and have configured it with a client, but the client is not able to connect. When the client tries to connect it gives SMSC rejected login to transmit, code 0x000d (Bind Failed). Couldn't connect to SMS center (retrying in 10 seconds). On the server side, it gives this error, Invalid SMPP PDU received. Server Bearerbox log 2011-01-15 13:07:37 [26155] [5] INFO: Client connected from 127.0.0.1 2011-01-15 13:07:37 [26155] [5] DEBUG: Started thread 45 (gw/bb_boxc.c:function) 2011-01-15 13:07:37 [26155] [45] DEBUG: Thread 45 (gw/bb_boxc.c:function) maps to pid 26155. 2011-01-15 13:07:37 [26155] [45] DEBUG: Started thread 46 (gw/bb_boxc.c:boxc_sender) 2011-01-15 13:07:37 [26155] [46] DEBUG: Thread 46 (gw/bb_boxc.c:boxc_sender) maps to pid 26155. 2011-01-15 13:07:40 [26155] [45] INFO: Connection closed by the box 127.0.0.1 2011-01-15 13:07:40 [26155] [46] DEBUG: send_msg: sending msg to box: 127.0.0.1 2011-01-15 13:07:40 [26155] [46] DEBUG: Thread 46 (gw/bb_boxc.c:boxc_sender) terminates. 2011-01-15 13:07:40 [26155] [45] DEBUG: Thread 45 (gw/bb_boxc.c:function) terminates. 2011-01-15 13:07:48 [26155] [5] INFO: Client connected from 127.0.0.1 2011-01-15 13:07:48 [26155] [5] DEBUG: Started thread 47 (gw/bb_boxc.c:function) 2011-01-15 13:07:48 [26155] [47] DEBUG: Thread 47 (gw/bb_boxc.c:function) maps to pid 26155. 2011-01-15 13:07:48 [26155] [47] DEBUG: Started thread 48 (gw/bb_boxc.c:boxc_sender) 2011-01-15 13:07:48 [26155] [48] DEBUG: Thread 48 (gw/bb_boxc.c:boxc_sender) maps to pid 26155. 2011-01-15 13:07:51 [26155] [47] INFO: Connection closed by the box 127.0.0.1 2011-01-15 13:07:51 [26155] [48] DEBUG: send_msg: sending msg to box: 127.0.0.1 2011-01-15 13:07:51 [26155] [48] DEBUG: Thread 48 (gw/bb_boxc.c:boxc_sender) terminates. 2011-01-15 13:07:51 [26155] [47] DEBUG: Thread 47 (gw/bb_boxc.c:function) terminates. 2011-01-15 13:07:59 [26155] [5] INFO: Client connected from 127.0.0.1 2011-01-15 13:07:59 [26155] [5] DEBUG: Started thread 49 (gw/bb_boxc.c:function) 2011-01-15 13:07:59 [26155] [49] DEBUG: Thread 49 (gw/bb_boxc.c:function) maps to pid 26155. 2011-01-15 13:07:59 [26155] [49] DEBUG: Started thread 50 (gw/bb_boxc.c:boxc_sender) 2011-01-15 13:07:59 [26155] [50] DEBUG: Thread 50 (gw/bb_boxc.c:boxc_sender) maps to pid 26155. 2011-01-15 13:08:02 [26155] [49] INFO: Connection closed by the box 127.0.0.1 2011-01-15 13:08:02 [26155] [50] DEBUG: send_msg: sending msg to box: 127.0.0.1 2011-01-15 13:08:02 [26155] [50] DEBUG: Thread 50 (gw/bb_boxc.c:boxc_sender) terminates. 2011-01-15 13:08:02 [26155] [49] DEBUG: Thread 49 (gw/bb_boxc.c:function) terminates. Server Opensmppbox log 2011-01-15 13:06:40 [28249] [25] INFO: Client connected from 40.100.0.000 2011-01-15 13:06:40 [28249] [25] DEBUG: Connecting to 127.0.0.1 2011-01-15 13:06:40 [28249] [25] INFO: Connected to bearerbox at localhost port 13001. 2011-01-15 13:06:40 [28249] [25] DEBUG: Started thread 26 (opensmppbox.c:smpp_to_bearerbox) 2011-01-15 13:06:40 [28249] [26] DEBUG: Thread 26 (opensmppbox.c:smpp_to_bearerbox) maps to pid 28249. 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP[opensmppbox]: Got PDU: 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP PDU 0x4ea0170 dump: 2011-01-15 13:06:41 [28249] [26] DEBUG: type_name: bind_transceiver 2011-01-15 13:06:41 [28249] [26] DEBUG: command_id: 9 = 0x0009 2011-01-15 13:06:41 [28249] [26] DEBUG: command_status: 0 = 0x 2011-01-15 13:06:41 [28249] [26] DEBUG: sequence_number: 13 = 0x000d 2011-01-15 13:06:41 [28249] [26] DEBUG: system_id: 12345 2011-01-15 13:06:41 [28249] [26] DEBUG: password: 12345 2011-01-15 13:06:41 [28249] [26] DEBUG: system_type: vma 2011-01-15 13:06:41 [28249] [26] DEBUG: interface_version: 52 = 0x0034 2011-01-15 13:06:41 [28249] [26] DEBUG: addr_ton: 0 = 0x 2011-01-15 13:06:41 [28249] [26] DEBUG: addr_npi: 1 = 0x0001 2011-01-15 13:06:41 [28249] [26] DEBUG: address_range: NULL 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP PDU dump ends. 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP[opensmppbox]: Sending PDU: 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP PDU 0x4ea38a0 dump: 2011-01-15 13:06:41 [28249] [26] DEBUG: type_name: bind_transceiver_resp 2011-01-15 13:06:41 [28249] [26] DEBUG: command_id: 2147483657 = 0x8009 2011-01-15 13:06:41 [28249] [26] DEBUG: command_status: 13 = 0x000d 2011-01-15 13:06:41 [28249] [26] DEBUG: sequence_number: 13 = 0x000d 2011-01-15 13:06:41 [28249] [26] DEBUG: system_id: NULL 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP PDU dump ends. 2011-01-15 13:06:42 [28249] [26] ERROR: Invalid SMPP PDU received. 2011-01-15 13:06:42 [28249]
