Hi everyone !

We're taking up a project using your software. It's really cool, but a a bug is still bothering us : every space following a special character is deleted on the received SMS.

For example, this mail :
"Foo content é ç à à "

will end up like this :
"Foo content éçàà"

Our users being French, this is a problem...
Our version is up to date, by the way.

Any help would be very welcome !

Was this problematic SMS sent by smsd, or by another device or service?

Did you have loglevel = 7 in the smsd.conf, so received PDU can be seen in the smsd.log?

For the next test you could use a global settings:
store_received_pdu = 3
store_sent_pdu = 3

so the PDU can taken from the message file.

I need to see that PDU, and also you could show the smsd.conf.

Hi keke, thanks for your reply !

I have
loglevel = 7
store_received_pdu = 1

Her is the smsd.conf content :

# # /etc/smsd.conf # # Description: Main configuration file for the smsd # devices = GSM1 outgoing = /var/spool/sms/outgoing checked = /var/spool/sms/checked incoming = /var/spool/sms/incoming logfile = /var/log/smstools/smsd.log infofile = /var/run/smstools/smsd.working pidfile = /var/run/smstools/smsd.pid outgoing = /var/spool/sms/outgoing checked = /var/spool/sms/checked failed = /var/spool/sms/failed incoming = /var/spool/sms/incoming sent = /var/spool/sms/sent stats = /var/log/smstools/smsd_stats # loglevel = 7 # delaytime = 10 errorsleeptime = 10 #blocktime = 3600 #stats = /var/log/smsd_stats #stats_interval = 3600 #stats_no_zeroes = no #checkhandler = /usr/local/bin/smscheck #checkhandler = /usr/local/bin/checkhandler-utf-8 receive_before_send = no # autosplit 0=no 1=yes 2=with text numbers 3=concatenated autosplit = 3 # autosplit = 0 # store_received_pdu 0=no, 1=unsupported, 2=unsupported and 8bit, 3=all # store_received_pdu = 1 # validity = 255 # decode_unicode_text = no # internal_combine = no # You can specify here an external program that is started whenever an alarm occurs. # alarmhandler = /path/to/an/alarmhandler/script # Specifies what levels start an alarmhandler. You can use value between 2 and 5. # alarmlevel = 4 # eventhandler = @EVENTHANDLER@ # # A decommenter si OK eventhandler = /usr/local/bin/mysmsd #blacklist = /etc/smstools/blacklist #whitelist = /etc/smstools/whitelist #[queues] # Commented lines are examples for germany # D1 = /var/spool/sms/D1 # D2 = /var/spool/sms/D2 # O2 = /var/spool/sms/O2 # EPLUS = /var/spool/sms/EPLUS # QUAM = /var/sppol/sms/QUAM # MOBILCOM = /var/spool/sms/MOBILCOM #OTHER = /var/spool/sms/OTHER #[provider] # Commented lines are examples for germany # D1 = 49160, 49170, 49171, 49175, 49151 # D2 = 491520, 49162, 49172, 49173, 49174 # O2 = 49176, 49179, 49159 # EPLUS = 49163, 49177, 49178, 49157 # QUAM = 49150 # MOBILCOM = 49156 #OTHER = 0,1,2,3,4,5,6,7,8,9 #[GSM1] # init = ATE0+CPMS="SM"+CNMI=2,0,0,2,1 # # Windows: /dev/com1, Solaris: /dev/cua/a, Linux /dev/ttyS0 # device = /dev/ttyS0 # incoming = yes # queues = OTHER # You don't need a PIN for mobile phones # pin = 1111 # mode = new # smsc = 491722270000 # baudrate = 19200 # rtscts = yes # cs_convert = yes # report = no # memory_start = 1 # primary_memory = memory name # secondary_memory = memory name # secondary_memory_max = number # pdu_from_file = /var/spool/sms/GSM1-PDU # sending_disabled = no # decode_unicode_text = no # internal_combine = no # #[GSM2] #init = ATE0 # Windows: /dev/com2, Solaris: /dev/cua/b, Linux /dev/ttyS1 #device = /dev/ttyS1 #incoming = yes #queues = OTHER #You don't need a PIN for mobile phones #pin = 2222 #mode = new #smsc = 491710760000 #baudrate = 19200 #rtscts = yes #cs_convert = yes #report = no #memory_start = 1 #primary_memory = memory name #secondary_memory = memory name #secondary_memory_max = number #pdu_from_file = /var/spool/sms/GSM2-PDU #sending_disabled = no #decode_unicode_text = no #internal_combine = no [GSM1] init = ATE0 mode = new device = /dev/ttyS0 incoming = no pin = 0000 #pin = 7297 baudrate = 115200 #[GSM1] #init = ATE0 #device = /dev/ttyS0 #incoming = no ##queues = OTHER ## You don't need a PIN for mobile phones ##pin = 0000 #pin = 7297 ##mode = new ## smsc = 491722270000 #baudrate = 115200 ##rtscts = yes ##cs_convert = yes ## report = no ## memory_start = 1 ## primary_memory = memory name ## secondary_memory = memory name ## secondary_memory_max = number ## pdu_from_file = /var/spool/sms/GSM1-PDU ## sending_disabled = no

I'm not sure about what the PDU is, would the last log help ? here it is :
2017-08-06 06:49:12,2, smsd: Smsd v3.1.15 started. 2017-08-06 06:49:12,2, smsd: Running as smsd:dialout. 2017-08-06 06:49:12,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.WQUTZQ /tmp/smsd_data.3g9mjx 2017-08-06 06:49:12,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0) 2017-08-06 06:49:12,4, smsd: File mode creation mask: 022 (0644, rw-r--r--). 2017-08-06 06:49:12,5, smsd: Outgoing file checker has started. PID: 1895. 2017-08-06 06:49:12,7, smsd: All PID's: 1895,1896 2017-08-06 06:49:12,5, GSM1: Modem handler 0 has started. PID: 1896. Will only send messages. 2017-08-06 06:49:12,6, GSM1: Checking if modem is ready 2017-08-06 06:49:12,7, GSM1: -> AT 2017-08-06 06:49:12,7, GSM1: Command is sent, waiting for the answer 2017-08-06 06:49:12,7, GSM1: <- OK 2017-08-06 06:49:12,6, GSM1: Pre-initializing modem 2017-08-06 06:49:12,7, GSM1: -> ATE0+CMEE=1;+CREG=2 2017-08-06 06:49:12,7, GSM1: Command is sent, waiting for the answer 2017-08-06 06:49:13,7, GSM1: <- OK 2017-08-06 06:49:13,6, GSM1: Checking if modem needs PIN 2017-08-06 06:49:13,7, GSM1: -> AT+CPIN? 2017-08-06 06:49:13,7, GSM1: Command is sent, waiting for the answer 2017-08-06 06:49:13,7, GSM1: <- +CPIN: READY OK 2017-08-06 06:49:13,6, GSM1: Initializing modem 2017-08-06 06:49:13,7, GSM1: -> ATE0 2017-08-06 06:49:13,7, GSM1: Command is sent, waiting for the answer 2017-08-06 06:49:14,7, GSM1: <- OK 2017-08-06 06:49:14,7, GSM1: -> AT+CSQ 2017-08-06 06:49:14,7, GSM1: Command is sent, waiting for the answer 2017-08-06 06:49:14,7, GSM1: <- +CSQ: 15,99 OK 2017-08-06 06:49:14,6, GSM1: Signal Strength Indicator: (15,99) -83 dBm (Good), Bit Error Rate: not known or not detectable 2017-08-06 06:49:14,6, GSM1: Checking if Modem is registered to the network 2017-08-06 06:49:14,7, GSM1: -> AT+CREG? 2017-08-06 06:49:14,7, GSM1: Command is sent, waiting for the answer 2017-08-06 06:49:15,7, GSM1: <- +CREG: 2,1,"67A6","46B5" OK 2017-08-06 06:49:15,6, GSM1: Modem is registered to the network 2017-08-06 06:49:15,6, GSM1: Location area code: 67A6, Cell ID: 46B5 2017-08-06 06:49:15,7, GSM1: -> AT+CSQ 2017-08-06 06:49:15,7, GSM1: Command is sent, waiting for the answer 2017-08-06 06:49:15,7, GSM1: <- +CSQ: 15,99 OK 2017-08-06 06:49:15,6, GSM1: Signal Strength Indicator: (15,99) -83 dBm (Good), Bit Error Rate: not known or not detectable 2017-08-06 06:49:15,6, GSM1: Selecting PDU mode 2017-08-06 06:49:15,7, GSM1: -> AT+CMGF=0 2017-08-06 06:49:15,7, GSM1: Command is sent, waiting for the answer 2017-08-06 06:49:16,7, GSM1: <- OK 2017-08-06 06:49:16,7, GSM1: -> AT+CIMI 2017-08-06 06:49:16,7, GSM1: Command is sent, waiting for the answer 2017-08-06 06:49:16,7, GSM1: <- 208101385644412 OK 2017-08-06 06:49:16,7, GSM1: -> AT+CGSN 2017-08-06 06:49:16,7, GSM1: Command is sent, waiting for the answer 2017-08-06 06:49:17,7, GSM1: <- 356613021123989 OK 2017-08-06 06:49:17,5, GSM1: CGSN: 356613021123989 2017-08-06 06:49:17,5, GSM1: IMSI: 208101385644412 2017-08-06 06:49:17,5, GSM1: Waiting for messages to send...

I hope this makes sense

Hi keke !

Sorry for the delay.
We tried another test with the recommended parameters, here's what stands out of the log file :

Modem: GSM1 Sent: 17-08-23 09:35:32 IMSI: 208101385644412 PDU: 0011000B913366926037F30000FF18D4E2940A6A818CEF3768FC76D3CB6E3AA890F8FF41 TEST - Foo content ▒▒▒▒

Does this mean anything to you ?

How do you create outgoing files?

You could test once again, with the original text:
"Foo content é ç à à "

Create the file with editor, and show the result.

We create outgoing files directly via Putty, to send them to the server.

We just figured out what was wrong : a program called mailtoSMS was supressing spaces after the mail was sent but before being received by SMStools.

We commented the function in charge of 'deleting space after non-word special characters', and it all went well.

Other special chars are still removed (like ô) or replaced (ç by Ç), but we learnt on one of your topic that they are not part of the GSM alphabet, so there's nothing we can do about it.

Thank you for your replies, and have a good day