Operating system name and version: RaspberryPi2 / Debian Wheezy Raspian
Version of smsd: Smsd v3.1.14
Smsd installed from: package repository of RaspberryPi2
Name and model of a modem / phone: (USB-stick) ZTE MF636+
Interface: USB

I had previously a completely working SMSTOOLS setup in Debian Squeeze running in TuxRail SBC with Smsd v3.1.11. I am now migrating this system now into RaspberryPi 2 SBC (single board computer) and the Smsd version from RaspberryPi repo is 3.1.14. Both are basicly headless embedded ARM-based computers so I access them via ssh commandline interface only.
This ZTE MF636+ requires the usb-modeswitch package to be used to unload the default mass memory profile and turn on the serial port modem-mode and I have that installed in the new rig too. After using modeswitch, the serial ports of ZTE MF636+ /dev/ttyUSB0.../dev/ttyUSB2 appear in the system. It was the /dev/ttyUSB2 that had to be configured for smsd.

Now I am somewhat confused as I copied the /etc/smsd.conf from the old computer to the new one and also the settings of the /etc/usb-modeswitch.conf.
The /var/log/smstools/smsd.log shows that the smsd is actually communicating with the modem, but despite that I have created valid sms messages to /var/spool/sms/outgoing/.. in the right format, I cannot see any log line mentioning anything about "new outgoing message detected" or in any way about any attempt to to send that message. In the smstools conf file I certainly have sending enabled, like in the previous rig.

Here is part of the smsd.log

2012-09-22 14:23:54,6, GSM1: Checking device for incoming SMS
2012-09-22 14:23:54,6, GSM1: Checking if modem is ready
2012-09-22 14:23:54,7, GSM1: -> AT
2012-09-22 14:23:54,7, GSM1: Command is sent, waiting for the answer
2012-09-22 14:23:55,7, GSM1: <- OK
2012-09-22 14:23:55,6, GSM1: Pre-initializing modem
2012-09-22 14:23:55,7, GSM1: -> ATE0+CMEE=1;+CREG=2
2012-09-22 14:23:55,7, GSM1: Command is sent, waiting for the answer
2012-09-22 14:23:55,7, GSM1: <- OK
2012-09-22 14:23:55,6, GSM1: Initializing modem
2012-09-22 14:23:55,7, GSM1: -> ATE0+CPMS="ME"
2012-09-22 14:23:55,7, GSM1: Command is sent, waiting for the answer
2012-09-22 14:23:56,7, GSM1: <- +CPMS: 0,100,0,30,0,100 OK
2012-09-22 14:23:56,7, GSM1: -> AT+CNMI=3,1,0,0,0
2012-09-22 14:23:56,7, GSM1: Command is sent, waiting for the answer
2012-09-22 14:23:56,7, GSM1: <- OK
2012-09-22 14:23:56,7, GSM1: -> AT+CSQ
2012-09-22 14:23:56,7, GSM1: Command is sent, waiting for the answer
2012-09-22 14:23:57,7, GSM1: <- +CSQ: 15,99 OK
2012-09-22 14:23:57,6, GSM1: Signal Strength Indicator: (15,99) -83 dBm (Good), Bit Error Rate: not known or not detectable
2012-09-22 14:23:57,6, GSM1: Checking if Modem is registered to the network
2012-09-22 14:23:57,7, GSM1: -> AT+CREG?
2012-09-22 14:23:57,7, GSM1: Command is sent, waiting for the answer
2012-09-22 14:23:57,7, GSM1: <- +CREG: 2,1, CA, 14DFA5 OK
2012-09-22 14:23:57,6, GSM1: Modem is registered to the network
2012-09-22 14:23:57,6, GSM1: Selecting PDU mode
2012-09-22 14:23:57,7, GSM1: -> AT+CMGF=0
2012-09-22 14:23:57,7, GSM1: Command is sent, waiting for the answer
2012-09-22 14:23:58,3, GSM1: Unexpected input: OK
2012-09-22 14:23:58,7, GSM1: <- OK
2012-09-22 14:23:58,6, GSM1: Changing SMSC
2012-09-22 14:23:58,7, GSM1: -> AT+CSCA="+358447983500"
2012-09-22 14:23:58,7, GSM1: Command is sent, waiting for the answer
2012-09-22 14:23:59,7, GSM1: <- OK
2012-09-22 14:23:59,6, GSM1: Checking memory size
2012-09-22 14:23:59,7, GSM1: -> AT+CMGD=?
2012-09-22 14:23:59,7, GSM1: Command is sent, waiting for the answer
2012-09-22 14:24:04,7, GSM1: put_command expected (\+CMGD:.*OK)|(ERROR), timeout occurred. 1.
2012-09-22 14:24:04,7, GSM1: <- OK
2012-09-22 14:24:04,6, GSM1: Used memory is 0
2012-09-22 14:24:04,6, GSM1: No SMS received

This just goes on and looks like only checking if modem is ok and if there are any new messages received. Despite of some timeout errors the receiving side seems to work. I sent a test message and it was received into /var/spool/sms/incoming/GSM1.EZsfeU correctly.

So, the two way serial type communication works with the modem, but SMSses are not sent and no records of even trying. The message I have put under ../outgoing does not even appear into ../failed directory, which was the case in the previous rig setup. Looks just like sending would be disabled, but how?

Any idea what could be the matter? I have installed the smstools in both rigs as binary packages from repositories.

Based on the log above I noticed that my "check_memory_method=2" ( http://smstools3.kekekasvi.com/index.php?p=configure#m_check_memory_method ) is probably wrong and should be set to some other value but I think it is not playing a role here as that was wrong with the previous setup as well.

Clarification: when I mentioned "sending a test message" which was received ok, I was referring to sending a test message from my phone to this USB modem. That was received OK by the USB modem and smstools.

Unless there is somewhere already a good diagnostic log or other status info available about the smstools sending status and about beginning sending attempts (such as "New outgoing msg noticed. Selected processing: rejected|starting sending"), including that sending is disabled by a user setting, I would wish you'd add such a logging/indication feature. If only reporting failure after the sending attempt, you miss the chance to find your configuration/setup error quickly. In this case I assume I just have some critical setting wrong.

It looks like this got fixed in 3.1.15 as at least now I got sending working with the exactly same /etc/smsd.conf that it was not working with 3.1.14.
So download the newest one and build it from source unless it is already available as a binary package. See one other Help-forum post about sending problems for more detailed explanation.

OS: CENTOS (Elastix)
SMSTOOLS V.:3.1.15
Modem: Huawei E220 USB
Modem: ZTE MF636 USB

Hi, i'm getting CMS Error 500 - Unkonwn Error - Can anyone help me with this, please?

POLARLIGHT, can you publish your smsd.conf, specially the init string!

I'm thinking that i can have an error on initialization string

Here's my configuration


# Modem configuration

#[HuaweiE220]
#device = /dev/ttyUSB0
#memory_start=0
#incoming = yes
#report = yes
#smsc = +35193121314
#baudrate = 19200

[ZTE636]
device = /dev/ttyUSB1
memory_start=0
pin = 0000
incoming = high
report = yes
smsc = +351962100000
baudrate = 19200

The Huawei was commented only to see the ZTE's behavior!

hi MareAlta,

Below you can find my smsd.conf. The init-string parts seem to be:
init = ATE0+CPMS="ME"
init2 = AT+CNMI=3,1,0,0,0


--------------------------------- /etc/smsd.conf
#
# /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
receive_before_send = no
# 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 = 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@
#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 2,0,0,1,0 3,2
# by default ZTE636+ has AT+CNMI 3,1,0,0,0 which gives indcation like: +CMTI: "ME",3
init = ATE0+CPMS="ME"
init2 = AT+CNMI=3,1,0,0,0
# # Windows: /dev/com1, Solaris: /dev/cua/a, Linux /dev/ttyS0
device = /dev/ttyUSB2
incoming = yes
# queues = OTHER
# You don't need a PIN for mobile phones
# pin = ***
# mode = new
# smsc = ********
smsc = 358405202000
baudrate = 19200
check_memory_method = 2
# 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 = ****
#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 =
#device = /dev/ttyUSB2
#incoming = yes
#pin =
#baudrate = 19200

OS: CENTOS - Elastix
Playsms 0.9.9.1 & SmsTools 3.1.15
Modem: Huawei E220 & ZTE MF636

Hi Polarlight! Thanks for your quick reply!

One thing is strange!
The second init string doesn't let sms3 service start! It stop's rigth there!

init2 = AT+CNMI=3,1,0,0,0

Other things:
When the two modems are connected and the Huawei settings are commented (#) and CGSN & CIMI are exacly the same!
Why I don't undestand! If Huawei is not connected and settings are commented!

plus:
The ZTE is giving always CMS 500 - Unknown error!

I'm probably quiting to have ZTE and going to make tests with 3 Huawei E220 from diferent operators.

I'm not giving up from ZTE configuration! I'm only trying the fast and stable option!

NOTE: I could not post here putty's log, because I didn't enabled the log! Now it's on!
Thanks anyway!