SMS Server Tools 3
This site is hosted by
Basic information:
Additional information:
Get SMS Server Tools 3:
Additional Options

 Sponsored links

Custom Search

 Visitor locations
 SMS Server Tools 3 Community
Welcome, Guest. Please login or register. Mon Jun 24, 2024 13:51
SMSTools3 Community » Help and support Bottom

problem with incoming unicode multipart SMS

Login and Post Reply

Page:  1

Author Post
Aug 2016
Location: Paris, France
Operating system name and version: Debian 3.16 / GNULinux 8.5
Version of smsd: 3.1.15
Smsd installed from: apt-get
Name and model of a modem: Maestro Wireless M100 3G-XT02 (Sierra Wireless module SL8082T)
Interface: USB
application: PlaySMS

Hi guys,

I'm a new user of smstools (I was on Gammu before, but it was not compatible with our new modem) and I use it in combo with a GSM modem and also playSMS, a web interface for SMS gateways like smstools.

For now, sending SMS seems to work well, but the incoming is not working properly with multipart SMS.

To check it, I see it in the PlaySMS MySQL DB (when the SMS is in the incoming directory, it disapears from it immediatly, maybe because of playSMS reading it)

When I send a one-part SMS with alphanumerics, GSM chars or Unicode, it works mainly good (for unicode, I'm still not sure to have the exact translation of the emojis, it seems only replaced by a '=' char when I see it in phpmyadmin, but at least I received the message completly).

But when I send multi-part SMS, it's OK with alphanumerics and GSM chars, but it's not doing well with Unicode ones.

I just got some little parts, even multiple times the same little part (I sent the SMS only once) and it never succeed to make it complete.

Also, when there was an unsuccessful multi-part SMS into the modem, it seems like I'm not receiving message for at least 1 hour... When it's in this weird state, I think I'm even losing some SMS that I've sent, but that I'll never receive.

here is my actual conf (I've added all the settings that may be useful in my case, but it may be not used well):
# /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/
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
receive_before_send = yes
# autosplit 0=no 1=yes 2=with text numbers 3=concatenated
autosplit = 3
# store_received_pdu 0=no, 1=unsupported, 2=unsupported and 8bit, 3=all
store_received_pdu = 3
store_sent_pdu = 3
incoming_utf8 = yes
decode_unicode_text = yes
admin_to = 336XXXXXXXX
hangup_incoming_call = yes
internal_combine = yes
ic_purge_hours = 2
ignore_outgoing_priority = yes
log_charconv = yes

init = ATE0;+CPMS="SM","SM";+CMMS=2
device = /dev/ttyUSB2
incoming = yes
mode = new
baudrate = 115200
smsc = 33660003000
pin = ignore
#rtscts = yes
#cs_convert = yes
report = yes
sending_disabled = no
memory_start = 1
pre_init = yes
primary_memory = SM
secondary_memory = SM
secondary_memory_max = 40
check_memory_method = 5
decode_unicode_text = yes
internal_combine = yes
ms_purge_hours = 2
'smsdconf' Syntax Highlight powered by GeSHi

Thank you

Aug 2016
Location: Paris, France
Topic owner
I forgot that I got some kind of errors that I can find in smsd.log when it's in the wierd state:

May 2009
Location: Jyväskylä, Finland
As your primary_memory and secondary_memory are both the same, you could comment out those lines. The next version will disable dual memory handler in such case.

Do you still have the whole log available? I'm wondering what is there right before 2016-08-17 15:52:16, is there part 1/6 never received?

Login and Post Reply

Page:  1

SMSTools3 Community » Help and support Top

Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.