|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. Please login or register. |
Sat May 18, 2024 21:21 |
Page: 1
| Keywords: Mode: All keywords (AND) |
|
Mon Nov 16, 2009 14:40
|
Kulma:
Sorry, I had not noticed this from your first post even though I should have. You have not defined incoming = yes (or incoming = high) for the modem. This is why smstools does not try to read the messages. The log in your latest post says: "Will only send messages.", which is not clear enough :(. It also talks about check_memory_method, which is not relevant when messages are not read. The next version will fix this later message.
The patch is only needed when using GMGL. You could use CPMS for memory checking.
The feature pdu_from_file will work after incoming = yes is defined.
Hey,
Guess what? It really works! :D
But to be honest, this is also pretty embarassing as I thought I had carefully read the configuration documentation and the sms tools log files... :oops:
(The log entry informing about the "message only" mode just nicely splits with 80 character wide textmode so that it's really easy to miss)
But anyway, thanks for the help!
|
|
Mon Nov 16, 2009 11:51
|
Kulma: Okay,
As I said earlier i wasn't quite sure how the AT message receiving is exactly supposed to work. I guess it makes things whole lot easier if no reports from modem via AT are required in incoming messages.
With Minicom, when you are not running smsd, and surely have at least one message received in the memory of a device, what is the response for a command AT+CPMS? ?
There should be count 1 or more listed, is there?
First I deleted the modem memory with AT+CMGD=0,4, and it returned OK. Now AT+CPMS gives:
+CPMS: "SM",0,30,"SM",0,30,"SM",0,30
After sending sms to the modem AT+CPMS? gives:
+CPMS: "SM",1,30,"SM",1,30,"SM",1,30
When there is for example 1,20 listed, a command AT+CMGR=1 or AT+CMGR=0 should work and read the message. Did you get any error message with those commands?
AT+CMGR=1 gives now OK and AT+CMGR=0:
+CMGR: 0,,47
07915***rest of the message in PDU***************************************************
Ok, but there is a bug in the smsd with this method and value, check this post for details if necessary (if default check_memory_method really does not work).
Tried to modify it according to the thread replies, and it compiled nicely:
--- smsd.c.orig 2009-11-16 13:06:36.000000000 +0200
+++ smsd.c 2009-11-16 13:08:37.000000000 +0200
@@ -1940,7 +1940,9 @@
break;
}
- if ((mnumber = atoi(p +6)) <= 0)
+ //if ((mnumber = atoi(p +6)) <= 0)
+ mnumber = strtol(p +6, NULL, 0);
+ if (errno == EINVAL || mnumber < 0)
{
errorstr = "Invalid message number";
break;
I did a tiny test and let sms tools run while sending sms to the modem. After that I tried sending sms using the outgoing queue. The test was done with following configuration:
devices = GSM_MOKKULA1
logfile = /var/log/smsd.log
loglevel = 7
outgoing = /var/spool/sms/outgoing
checked = /var/spool/sms/checked
failed = /var/spool/sms/failed
incoming = /var/spool/sms/incoming
[GSM_MOKKULA1]
device = /dev/ttyUSB0
baudrate = 115200
memory_start = 0
Here's the log file of the test (with possibly sensitive data masked out):
2009-11-16 10:39:22,2, smsd: Smsd v3.1.5 started.
2009-11-16 10:39:22,2, smsd: Running as root:root.
2009-11-16 10:39:22,7, smsd: Running startup_check (shell): /tmp/smsd_script.MFPr1o /tmp/smsd_data.mFlkIN
2009-11-16 10:39:22,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0
2009-11-16 10:39:22,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2009-11-16 10:39:22,2, smsd: Running in terminal mode.
2009-11-16 10:39:22,5, smsd: Outgoing file checker has started. PID: 20105.
2009-11-16 10:39:22,5, GSM_MOKKULA1: Modem handler 0 has started. PID: 20107. Will only send messages.
2009-11-16 10:39:22,5, GSM_MOKKULA1: Using check_memory_method 1: CPMS is used.
2009-11-16 10:39:22,6, GSM_MOKKULA1: Checking if modem is ready
2009-11-16 10:39:22,7, GSM_MOKKULA1: -> AT
2009-11-16 10:39:22,7, GSM_MOKKULA1: Command is sent, waiting for the answer
2009-11-16 10:39:23,7, GSM_MOKKULA1: <- OK
2009-11-16 10:39:23,6, GSM_MOKKULA1: Pre-initializing modem
2009-11-16 10:39:23,7, GSM_MOKKULA1: -> ATE0+CMEE=1
2009-11-16 10:39:23,7, GSM_MOKKULA1: Command is sent, waiting for the answer
2009-11-16 10:39:23,7, GSM_MOKKULA1: <- OK
2009-11-16 10:39:23,6, GSM_MOKKULA1: Checking if modem needs PIN
2009-11-16 10:39:23,7, GSM_MOKKULA1: -> AT+CPIN?
2009-11-16 10:39:23,7, GSM_MOKKULA1: Command is sent, waiting for the answer
2009-11-16 10:39:24,7, GSM_MOKKULA1: <- +CPIN: READY OK
2009-11-16 10:39:24,7, GSM_MOKKULA1: -> AT+CSQ
2009-11-16 10:39:24,7, GSM_MOKKULA1: Command is sent, waiting for the answer
2009-11-16 10:39:24,7, GSM_MOKKULA1: <- +CSQ: 9,99 OK
2009-11-16 10:39:24,6, GSM_MOKKULA1: Checking if Modem is registered to the network
2009-11-16 10:39:24,7, GSM_MOKKULA1: -> AT+CREG?
2009-11-16 10:39:24,7, GSM_MOKKULA1: Command is sent, waiting for the answer
2009-11-16 10:39:25,7, GSM_MOKKULA1: <- +CREG: 0,1 OK
2009-11-16 10:39:25,6, GSM_MOKKULA1: Modem is registered to the network
2009-11-16 10:39:25,6, GSM_MOKKULA1: Selecting PDU mode
2009-11-16 10:39:25,7, GSM_MOKKULA1: -> AT+CMGF=0
2009-11-16 10:39:25,7, GSM_MOKKULA1: Command is sent, waiting for the answer
2009-11-16 10:39:25,7, GSM_MOKKULA1: <- OK
2009-11-16 10:39:25,7, GSM_MOKKULA1: -> AT+CIMI
2009-11-16 10:39:25,7, GSM_MOKKULA1: Command is sent, waiting for the answer
2009-11-16 10:39:26,7, GSM_MOKKULA1: <- *************** OK
2009-11-16 10:39:26,7, GSM_MOKKULA1: -> AT+CGSN
2009-11-16 10:39:26,7, GSM_MOKKULA1: Command is sent, waiting for the answer
2009-11-16 10:39:26,7, GSM_MOKKULA1: <- *************** OK
2009-11-16 10:39:26,5, GSM_MOKKULA1: CGSN: ***************
2009-11-16 10:39:26,5, GSM_MOKKULA1: IMSI: ***************
2009-11-16 10:39:26,6, GSM_MOKKULA1: Checking if reading of messages is supported
2009-11-16 10:39:26,7, GSM_MOKKULA1: -> AT+CPMS?
2009-11-16 10:39:26,7, GSM_MOKKULA1: Command is sent, waiting for the answer
2009-11-16 10:39:27,7, GSM_MOKKULA1: <- +CPMS: "SM",0,30,"SM",0,30,"SM",0,30 OK
2009-11-16 10:39:27,5, GSM_MOKKULA1: Waiting for messages to send...
2009-11-16 10:50:43,5, smsd: Moved file /var/spool/sms/outgoing/viesti3 to /var/spool/sms/checked
2009-11-16 10:50:44,6, GSM_MOKKULA1: I have to send 1 short message for /var/spool/sms/checked/viesti3
2009-11-16 10:50:44,6, GSM_MOKKULA1: Sending SMS from to ************
2009-11-16 10:50:44,6, GSM_MOKKULA1: Checking if modem is ready
2009-11-16 10:50:44,7, GSM_MOKKULA1: -> AT
2009-11-16 10:50:44,7, GSM_MOKKULA1: Command is sent, waiting for the answer
2009-11-16 10:50:45,7, GSM_MOKKULA1: <- OK
2009-11-16 10:50:45,6, GSM_MOKKULA1: Pre-initializing modem
2009-11-16 10:50:45,7, GSM_MOKKULA1: -> ATE0+CMEE=1
2009-11-16 10:50:45,7, GSM_MOKKULA1: Command is sent, waiting for the answer
2009-11-16 10:50:45,7, GSM_MOKKULA1: <- OK
2009-11-16 10:50:45,7, GSM_MOKKULA1: -> AT+CSQ
2009-11-16 10:50:45,7, GSM_MOKKULA1: Command is sent, waiting for the answer
2009-11-16 10:50:46,7, GSM_MOKKULA1: <- +CSQ: 9,99 OK
2009-11-16 10:50:46,6, GSM_MOKKULA1: Checking if Modem is registered to the network
2009-11-16 10:50:46,7, GSM_MOKKULA1: -> AT+CREG?
2009-11-16 10:50:46,7, GSM_MOKKULA1: Command is sent, waiting for the answer
2009-11-16 10:50:46,7, GSM_MOKKULA1: <- +CREG: 0,1 OK
2009-11-16 10:50:46,6, GSM_MOKKULA1: Modem is registered to the network
2009-11-16 10:50:46,6, GSM_MOKKULA1: Selecting PDU mode
2009-11-16 10:50:46,7, GSM_MOKKULA1: -> AT+CMGF=0
2009-11-16 10:50:46,7, GSM_MOKKULA1: Command is sent, waiting for the answer
2009-11-16 10:50:47,7, GSM_MOKKULA1: <- OK
2009-11-16 10:50:47,7, GSM_MOKKULA1: -> AT+CMGS=104
2009-11-16 10:50:47,7, GSM_MOKKULA1: Command is sent, waiting for the answer
2009-11-16 10:50:47,7, GSM_MOKKULA1: <- >
2009-11-16 10:50:47,7, GSM_MOKKULA1: -> ******************************************************************************************************************************************************************************************************************.
2009-11-16 10:50:48,7, GSM_MOKKULA1: Command is sent, waiting for the answer
2009-11-16 10:50:49,7, GSM_MOKKULA1: <- +CMGS: 7 OK
2009-11-16 10:50:49,5, GSM_MOKKULA1: SMS sent, Message_id: 7, To: ************, sending time 5 sec.
2009-11-16 10:50:49,6, GSM_MOKKULA1: Deleted file /var/spool/sms/checked/viesti3
I sent the sms to the modem between the 10:39 and 10:50 and smstools didn't respond to it in any manner. However the message I sent from smstools worked very nicely as seen in log.
I'll check this later. After smsd got more methods for checking and reading a memory, this feature was limited to methods 0 and 1 only, and should work with those methods unless there is a bug...
What do you mean with "pointing"?
Ehh, I guess just using a filename instead of directory as the syntax seems to hint that one can either use directory or plain file for pdu_from_file setting:
pdu_from_file = filename / directoryname/
At least I know the setting is checked as if I give a bogus directory the smstools will exit with error:
pdu_from_file directory /var/spool/pdutest_bogus cannot be opened.
There was 1 major problem found.
You have a manual (of AT command set) for this device? I did not find it with fast googling. If you like, you could sent it to me via email.
Well, to be honest i don't have manual for the device either. Closest thing I could find was "Huawei GTM900 Wireless Module AT Command Reference". At least the basic commands I tested worked as documented there but I have no idea of the overall accuracy of it in case of E169 though. (so maybe I shouldn't have referred it as a "manual" but instead as "some related Huawei documentation")
With your smsd.conf shown in the post, I think that receiving should work without init string. Can you show a piece of the log when there is a message but smsd cannot read it? You can use Private tags to protect your data, if necessary.
It really starts to seem more and more like smstools wouldn't even try to read the messages. As it can be seen from the logs it doesn't react or even give any errors on arrival of a message. I really wonder if this is "check the cables" type of a problem after all...
|
|
Fri Nov 13, 2009 11:28
|
Kulma: Operating system name and version: Mandriva 2009.1
Version of smsd: 3.1.5
Smsd installed from: sources (with libmm for stats)
Name and model of a modem / phone: Huawei E169
Interface: USB
Hello,
I'm doing a little project related to sms-gateway running on linux and sms tools seems the right tool for the job. However i've run into some problems with my Huawei gsm/gprs modem. The modem is detected by kernel and gives three serial usb ttys to /dev/ttyUSB0 - 2. By using minicom serial application i've been able to send and read received messages just fine.
Yesterday I started to experiment with smstools3 and the configuration and setting a simple test enviroment was quite easy. Sending messages works very nicely but then i realized that it doesn't react to received sms messages at all.
First i suspect that there is something wrong with the modem settings, but then again, as this is pretty much the first time i'm dealing with a gsm device using AT commands i'm not fully sure how it's supposed to work.
**** AT and Modem **********************
The default settings seem to be fine as the modem uses SM as AT+CPMS message storage and all the rest of init commands seem to be ok as well. The new message indicator AT+CNMI might be one culprit as it's set to 0,0,0,0,0 by default. I've tried numerous combinations like 2,1,0,1,0 / 1,1,0,2,0 / 1,1,0,0,1 and so on. AT+CNMI=? gives a result: (0,1,2),(0,1,2,3),(0,2),(0,1,2),(0,1).
The second value of +CNMI as 1 seems to be related to what i'm looking for: "1: If SMS-DELIVER is stored into ME/TA, indication of the memory location is routed to 1 the TE using unsolicited result code: +CMTI: <mem>,<index>".
However, despite the CNMI settings the modem seems to be keeping sms messages as its own knowledge. I can't get any kind notification from received sms even when using minicom. Listing "REC UNREAD" (or 0 in pdu mode) messages with AT+CMGL works.
I wonder if AT+CNMA has something to do with this as it doesn't quite work as it should according to manual. All the AT+CNMA, AT+CNMA?, AT+CNMA=n (0-2) commands give me "+CMS ERROR 500" (unknown error) in pdu mode. AT+CNMA=? gives: (0,1,2) and in text mode AT+CNMA gives "OK" but the rest is same.
I've also tried to adjust AT+CSMP as the default was: ,,0,0 to 17,167,0,0 / 49,167,0,0 without any difference.
**** SMS Tools *************************
Okay, here's my tiny smsd.conf file:
devices = GSM_MOKKULA1
logfile = /var/log/smsd.log
loglevel = 7
outgoing = /var/spool/sms/outgoing
checked = /var/spool/sms/checked
failed = /var/spool/sms/failed
incoming = /var/spool/sms/incoming
[GSM_MOKKULA1]
#2,1,0,2,0
init = AT+CNMI=1,1,0,0,1;+CSMP=49,167,0,0
device = /dev/ttyUSB0
baudrate = 115200
#check_memory_method = 1
memory_start = 0
#pdu_from_file = /var/spool/sms/pdutest
It seems that the memory slots start from 0 as AT+CMGL lists the first entry as 0. I've tried all the memory check methods without any result. The part which makes me worried is that I tried pdu_from_file with memory check 0 / 1 and it didn't seem to work. The files in pdutest folder aren't handled and it doesn't do anything even if I point it to a file. It's quite strange as sending messages works fine like i mentioned earlier.
I presume that the other memory check methods would use some kind of polling mechanism, but as i haven't yet studied the sources carefully i'm not sure (C isn't quite my strongest point).
****************************************
I've tried to search info concerning the modem and AT configuration but no tweaks/tricks that i've tried have worked so far.
And thanks for all the help in advance.
|
Page: 1
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
