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. Sun May 19, 2024 21:50
SMSTools3 Community » Help and support Bottom

[outdated] sms can not work

  This topic is locked

Page:  1

Author Post
Member
Registered:
Nov 2009
Location: China
Operating system name and version: FreeBSD 7.2 Release
Version of smsd: 3.1.5
Smsd installed from: Ports
Name and model of a modem / phone: wavecom M1206B
Interface: serial / USB / some adapter...serial

and my logfile is as follow

2009-11-22 18:38:57,2, smsd: Smsd v3.1.5 started.
2009-11-22 18:38:57,2, smsd: Running as uucp:uucp.
2009-11-22 18:38:57,7, smsd: Running startup_check (shell): /tmp/smsd_script.QXHcll /tmp/smsd_data.Giz1dW
2009-11-22 18:38:57,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0
2009-11-22 18:38:57,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2009-11-22 18:38:57,5, smsd: Outgoing file checker has started. PID: 907.
2009-11-22 18:38:57,5, GSM1: Modem handler 0 has started. PID: 910.
2009-11-22 18:38:57,5, GSM1: Using check_memory_method 1: CPMS is used.
2009-11-22 18:38:57,6, GSM1: Checking device for incoming SMS
2009-11-22 18:38:57,6, GSM1: Checking if modem is ready
2009-11-22 18:38:58,7, GSM1: -> AT
2009-11-22 18:38:58,7, GSM1: Command is sent, waiting for the answer
2009-11-22 18:39:03,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 1.
......
2009-11-22 18:41:14,7, GSM1: <-
2009-11-22 18:41:14,7, GSM1: -> AT
2009-11-22 18:41:14,7, GSM1: Command is sent, waiting for the answer
2009-11-22 18:41:19,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 25.
2009-11-22 18:41:19,7, GSM1: <-
2009-11-22 18:41:20,7, GSM1: -> .

Could someone kindly point out what wrong with it
thanks a lot


« Last edit by schtd on Mon Nov 23, 2009 11:23, 176 months ago. »
Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
First check that you are using correct serial port and check the cable and connectors.

Communication speed defaults to 115200 and this modem should support it. However, there was said "Automatic bit rate (300 to 38,400 bits / s)" which probably means that you could try with baudrate = 38400 or baudrate = 19200 in the modem section of smsd.conf file.

Member
Registered:
Nov 2009
Location: China
Topic owner
this is my smsd.conf

devices = GSM1
logfile = /var/log/smsd.log
loglevel = 7
receive_before_send = no

[GSM1]
init=AT
device = /dev/cuad0
baudrate = 9600
send_delay = 0

I've set low speed before i post my log file

Member
Registered:
Nov 2009
Location: China
Topic owner
for on my pc it displayed that send -> AT^M & -> ^Z^M
so i add init = AT in my smsd.conf
I don't familier with AT code


Thank you for your answer

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
Just verified that /dev/cuad0 is correct setting in FreeBSD 7.2 for the first serial port and smsd 3.1.5 runs properly.

Did you get some error messages when running without send_delay = 0 setting?

You do not need to use "init=AT", it has no meaning.

I think that your cable (and/or modem) is broken. Can you test the communication with some other cable, or with current cable in another machine?

You could also try with a setting rtscts = no, but probably it does not help.

Member
Registered:
Nov 2009
Location: China
Topic owner
my modem & cable can work with another sms software on windows XP

and without or with "send_delay = 0" seems no difference


thanks for your reponse

Member
Registered:
Nov 2009
Location: China
Topic owner
this is the test result on the other system

ver is 020925
start init GSM Modem
AT
ok
ATE0
ok
ATI
Wavecom Modem Multiband 900E 1800 ok
AT+CMGF = 0
ok
AT+CNMI=2,1
ok
AT+CSCA
+CSCA "+8613800210500",1450K
GSM Modem is initialized

and i've sended a sm successfully

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
schtd wrote
this is the test result on the other system

On Windows XP?

If so, can you on FreeBSD verify that the port is working with some another software, like a terminal program?

You could also check that the port has correct attributes ( ls -l /dev/cuad0 ).

It looks like I cannot resolve this issue :(. Because smsd runs correctly on my test machine, with the same OS and even when running as uucp:uucp, something must be broken. :(

Member
Registered:
Nov 2009
Location: China
Topic owner
this is the result of :
#ls -l /dev/cuad0
crw-rw---- 1 uucp dialer 0, 49 Nov 23 21:11 /dev/cuad0

Member
Registered:
Nov 2009
Location: China
Topic owner
And could you tell me how to use terminal program testing com port?

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
The port looks correct.

You can use cu -l /dev/cuad0 for testing. Type some AT commands, like ATI, AT+CREG?, AT+CPMS? followed by enter.

More details for cu can be found from here.

Member
Registered:
Nov 2009
Location: China
Topic owner
I've used cu -l /dev/cuad0 before

it displayed

Connected
AT
ok
...


it always display "AT ok" quickly and I hardly have enough time to type commands

ATI
WAVECOM Modem
Multiband 900E 1800

AT+CREG
Error

AT+CPMS
Error

What's wrong with it ?

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
schtd wrote
it always display "AT ok" quickly and I hardly have enough time to type commands

Repeatedly? Some other process is running and communicates with this device?

The answer should be OK in uppercase.

Commands AT+CREG? and AT+CPMS? need ? at the end.

Member
Registered:
Nov 2009
Location: China
Topic owner
the result is:

at+creg?
+creg:0,1

at+cpms?
+cpms:"sm",0,25,"sm",0,25




You are so kind

Member
Registered:
Nov 2009
Location: China
Topic owner
My question is if I need add init config script in the smsd.conf.

i've seen that with "at+cpms? " others have three memories ,but there are only two memories in my case.
in the XP case, with "at+cmgf?",displayed :"+cmgf=0",which means ASCII mode.
but in FreeBSD box,displayed "+cmgf=1"
are these configures affect the result and how to change it?
i've add " init=at+cmgf="0" " in the smsd.conf ,but with cu -l commands,it still show "+cmgf=1" and can not send sms.
Why this?


waiting for your answer.

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
First things first ;). Did you get communication on FreeBSD to working? If so, what was the reason for the failure? Another process, or? Perhaps some process is searching for modems? If you receive "AT ok" quickly and repeatedly, there must be some reason for this. It's very interesting to know if you have resolved this, as I do not have this issue on my FreeBSD machine.

If your device is listing only two memories, there are no more memories accessible. Usually there is no need to change the memory.

CMGF=0 means PDU mode, which is only mode supported by smsd. This is because ASCII mode is too limited and in many cases PDU mode is still required even if ASCII mode is tried to use as a primary mode. Do not try to change this mode using init string, it will have no effect.

Member
Registered:
Nov 2009
Location: China
Topic owner
i still can not send sms on my FreeBSD box
i think it was smsd which iterated sending AT^M & Z^M, that can be find in my smsd.log

2009-11-22 18:38:57,2, smsd: Smsd v3.1.5 started.
2009-11-22 18:38:57,2, smsd: Running as uucp:uucp.
2009-11-22 18:38:57,7, smsd: Running startup_check (shell): /tmp/smsd_script.QXHcll /tmp/smsd_data.Giz1dW
2009-11-22 18:38:57,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0
2009-11-22 18:38:57,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2009-11-22 18:38:57,5, smsd: Outgoing file checker has started. PID: 907.
2009-11-22 18:38:57,5, GSM1: Modem handler 0 has started. PID: 910.
2009-11-22 18:38:57,5, GSM1: Using check_memory_method 1: CPMS is used.
2009-11-22 18:38:57,6, GSM1: Checking device for incoming SMS
2009-11-22 18:38:57,6, GSM1: Checking if modem is ready
2009-11-22 18:38:58,7, GSM1: -> AT
2009-11-22 18:38:58,7, GSM1: Command is sent, waiting for the answer
2009-11-22 18:39:03,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 1.
......
2009-11-22 18:41:14,7, GSM1: <-
2009-11-22 18:41:14,7, GSM1: -> AT
2009-11-22 18:41:14,7, GSM1: Command is sent, waiting for the answer
2009-11-22 18:41:19,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 25.
2009-11-22 18:41:19,7, GSM1: <-
2009-11-22 18:41:20,7, GSM1: -> .

as in my FreeBSD box it was displayed :
->AT^M
Command is sent, waiting for the answer
put_command expected (OK)|(ERROR), timeout occurred. 1
<-
.->^Z^M
Command is sent, waiting for the answer
put_command expected (OK)|(ERROR), timeout occurred. 2
<-
........

and i stop smsd, there will not display any more
:roll:

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
keke wrote
schtd wrote
it always display "AT ok" quickly and I hardly have enough time to type commands

Repeatedly? Some other process is running and communicates with this device?

So, have you checked if there is other process running and using your device? At least you should try lsof /dev/cuad0.

As Smsd does not send AT repeatedly, it must be some other process. Perhaps some PPP or GPRS, just a guess.

schtd wrote
i think it was smsd which iterated sending AT^M & Z^M, that can be find in my smsd.log

Yes, smsd processes are only processes which write to the smsd.log.

schtd wrote
and i stop smsd, there will not display any more

Sure, because smsd was stopped...


When smsd is stopped, and you connect to the modem using cu -l /dev/cuad0, there still is some traffic like "AT ok", right? In the normal case there should be nothing traffic.

If you have another serial port than cuad0 (hopefully you have), please try with it. Hopefully it work better, at least with no strange traffic.

  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.