SMS Server Tools 3
 Menu
Basic information:
Additional information:
Support:
Get SMS Server Tools 3:
Additional Options

 Sponsored links

 Search
Custom Search

 Visitor locations
 
 SMS Server Tools 3 Community
Welcome, Guest. The forum is currently read-only, but will open soon. Thu Sep 04, 2025 15:51
SMSTools3 Community » Search Bottom

Page:  1

Keywords:
Mode: All keywords (AND)
stephan: Hi Keke, got me, thank you! I was looking at the file in vi only, it didn't occur to me to do a hex dump, and the different behavior with the Alphabet apparently was a red herring in my analysis. I can confirm that there was a trailing 0a which didn't play a role with the 8 bit charset but apparently does with UTF type messages. When I remove the trailing 0a with sed it's working as expected, so please consider this report done. I appreciate your reply and assistance! Stephan
stephan: Update: the problem appears to be in the spot where SMSTools computes the PDU representation of the message. As soon as Alphabet: UTF8 ist present, there is the excess linefeed in the PDU string, as I can check with http://www.rednaxela.net/pdu.php (Not posting the messages here as I have tested with true phone numbers that cannot be obfuscated in the PDU but this should now be easy to reproduce.)
stephan: Operating system name and version: Linux Debian 10 Version of smsd: 3.1.21 Smsd installed from: sources Name and model of a modem / phone: SIMCOM SIM7600G Interface: USB Hi there, I noticed that as soon as I send a message with Alphabet: UTF8, the SMS will have an additional newline at the end when received on the other side. This file (------ indicates the boundary) shows the problem: ----------------------------------------------- To: 00491709xxxxxx Alphabet: UTF8 Flash: no To_TOA: International TEST ------------------------------------------------- As soon as I remove the "Alphabet: UTF8" line, the SMS is received as expected. My goal is to make UTF work (for non-ASCII language support), and at the same time have a correct transmission for such cases. Any help appreciated! Stephan /etc/smsd.conf: devices = GSM0 outgoing = /var/spool/sms/outgoing checked = /var/spool/sms/checked incoming = /var/spool/sms/incoming 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 stats_interval = 0 stats_no_zeroes = yes status_include_counters = no ignore_outgoing_priority = yes loglevel = 6 receive_before_send = no autosplit = 3 validity = 255 decode_unicode_text = no hangup_incoming_call = yes date_filename = 2 ignore_exec_output = yes eventhandler = /opt/braintower/sms-gateway/scripts/eventhandler.sh blockafter = 3 blocktime = 3600 notifier = yes delaytime = 0 [GSM0] device = /dev/gsm0 device = /dev/gsm0 signal_quality_ber_ignore = yes init = AT+CPMS="ME","ME","ME" init2 = AT+CNMI=2,0,0,2,1 cmgl_value = 4 check_memory_method = 1 keep_open = yes report = disabled report_device_details = yes check_network = yes memory_start = 0 mode = new incoming = yes baudrate = 115200 regular_run_post_run = /opt/braintower/sms-gateway/scripts/smstools_regular_run.sh regular_run_cmdfile = /var/spool/sms/regular_run.cmdfile regular_run_interval = 60 regular_run_statfile = /var/log/smstools/smsd_stats/statfile pin = ignore

Page:  1

SMSTools3 Community » Search Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.