SMS Server Tools 3
This site is hosted by Kekekasvi.com
 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. Please login or register. Sat May 25, 2024 10:56
SMSTools3 Community » Help and support Bottom

[solved] Can't receive nor send sms!

  This topic is locked

Page:  1

Author Post
Member
Registered:
Nov 2010
Location: Lagos, Nigeria
Operating system name and version: Ubuntu 10.04
Version of smsd: 3.1.14
Smsd installed from: Source file
Name and model of a modem / phone: Motorola v3, sony ericsson p990i
Interface: USB adapter

Am new here and I have read the manual and am yet to still get it to work. I use playsms as the interface.

Below is my configuration:

# Global configuration

devices = modem1

loglevel = 4

logfile = /var/log/sms/smstools.log

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

delaytime = 6
errorsleeptime = 12
blocktime = 180

autosplit = 3
receive_before_send = yes

# Modem configuration

# Phone settings
[modem1]
#init =AT+CNMI=2,3,2,0,0
device = /dev/ttyACM0
incoming = yes
#pin =
baudrate = 115200
smsc = +2348030000410

I have not been able to send nor recieve sms!

How do I show the error log? I have searched in the log path and there is nothing expect for the outgoing file. Can I view the status file at the command line?

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
In the smsd.conf, change
loglevel = 4
to
loglevel = 7

In the modem section, you could also add a setting report_device_details = yes. This will show some information which may be required later. The information is shown in the log right after smsd is started.

Then restart smsd, and you can use tail -100f /var/log/sms/smstools.log to see what is happening.

You could show the log here.

Member
Registered:
Nov 2010
Location: Lagos, Nigeria
Topic owner
Thanks.

Here is my log:



My conf file


Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
It seems that you did not change loglevel to 7. You could re-check and change it. Also the "device details" is only shown partially. You could stop the smsd, remove the smstools.log, and restart smsd. Then cat /var/log/sms/smstools.log and show a new log here.

However, your current log show that there are no communication errors. You could check if you can send and receive SMS manually while using SIM in ordinary phone. Also check what the phone show for the SMSC setting. In many cases it is not required that smsc is set in the configuration file and it may cause failure if the number is not correct.

Member
Registered:
Nov 2010
Location: Lagos, Nigeria
Topic owner
Thanks Keke.

I have made modifications to conf file and it is sending messages now but it doesn't retreive messages from the phone. It came up with the following error:


The conf file


Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
Ok, I see that you have removed smsc setting and it helped.

The log shown here does not contain all "device details" and other information. I need to see the log from "Modem handler ... has started ...".

Member
Registered:
Nov 2010
Location: Lagos, Nigeria
Topic owner
Here is the log output.



Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
Thanks.

First, the device says "+CME ERROR: 25 (invalid characters in text string)" to the command "ATE0+CMEE=1;+CREG=2", which likely means that CREG=2 is not supported. Later it does not report Cell ID information. Add this setting to the modem section: loglevel_lac_ci = 8. This causes that even with loglevel 7 that feature is disabled. It's not a big thing, but at least one error message is avoided from the log.

Based on the information of the device, it likely uses some higher numbers for messages than 1, 2, 3 etc. Add this setting to the modem section: check_memory_method = 31. Restart smsd, and try once again. If there are any errors in the log, show the log.

Member
Registered:
Nov 2010
Location: Lagos, Nigeria
Topic owner
Thanks again for your patience Keke.

Here is the log.
Hidden private text.



Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
Some messages does not contain SMSC number, and this causes that the checking gives an error because length of information is zero. I probably have to change this in the next version.

Try with check_memory_method = 3.

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
There are also sent messages, and smsd will not decode them. Those messages are removed from the device.

Member
Registered:
Nov 2010
Location: Lagos, Nigeria
Topic owner
Thanks keke. Its working now.

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
Great 8)

The next version will have this fix, you can apply it now if you want:

In the file smsd.c search octet2bin_check. The next line is found:

if ((pdu1 = octet2bin_check(p)) <= 0)

Change it to:

if ((pdu1 = octet2bin_check(p)) < 0)

Then save and recompile.

With this fix you can use check_memory_method 31 which is slightly faster than 3, but if you do not have lot of messages, there is no remarkable difference.

  This topic is locked

Page:  1

SMSTools3 Community » Help and support Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.