|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. The forum is currently read-only, but will open soon. |
Fri Aug 29, 2025 21:14 |
Page: 1
| Keywords: Mode: All keywords (AND) |
|
Fri Jul 16, 2010 16:12
|
tokie:
Sorry, but I don't understand;
Count the number of whole SMS already does in /var/spool/sms/stats/Siemens.counter;
Correct?
Yes, but this file contains number of parts sent, not number of SMS. For example single SMS can contain 3 parts and in this case that counter is incremented with 3.
For example, if using a SIM which has 1000 SMS ( = parts ) / month -contract, this counter can be used to detect when the limit is used. Smsd does not clear this counter, which means that every month smsd should be stopped and counter should be cleared manually.
Only for information, I try many sms(my system send always same kind of sms) and the counter is incremented with 1 each sms!! :lol:
Everything is possible ;).
Absolutely right! :twisted:
The next script does it. In this case, STORAGE defines a directory.
Works perfectly!! :mrgreen:
Thank you very much!!
Now, I try to log all in sql database.
Next time!!
|
|
Fri Jul 16, 2010 09:49
|
tokie:
If you have SQL database available, and use eventhandler to store messages into it ( example ), you can see counts from the database.
Thank you for this
This example will count the number of whole SMS, not number of parts. If you need to count number of parts, you have to set store_sent_pdu = yes, and count how many PDU's are in the message file, and apply this as an increment to the counter.
Sorry, but I don't understand;
Count the number of whole SMS already does in /var/spool/sms/stats/Siemens.counter;
Correct?
I only need to know how many sms my Smsd (with only one phone) sent to each phone number;
for example:
/var/spool/sms/stats/Siemens.counter
39333xxxxxx --> 14
39333yyyyyyy --> 4
or else:
/var/spool/sms/stats/Siemens/39333xxxxxx.counter
14
/var/spool/sms/stats/Siemens/39333yyyyyyy.counter
4
It's possibile?? :roll:
|
|
Thu Jul 15, 2010 16:46
|
tokie: Operating system name and version: Debian 5.0.4
Version of smsd: 3-3.1.5
Smsd installed from: sources
Name and model of a modem / phone: Siemens S35
Interface: serial
Hi to all,
I would like to know if it's possible to make(or how to set) a
counter to see how many sms my smstool's box sent to same
phone number.
Tks
Tokie
|
|
Wed Nov 18, 2009 08:08
|
tokie:
Therefore should I use cs_convert = yes or nothing???
Yes. ;)
The setting cs_convert defaults to yes and applies for both outgoing and incoming messages.
You see correct characters because you only used US-ASCII. Digits, letters and some other characters are the same in GSM alphabet, but some characters are not. For example, @ is zero in GSM alphabet. There are also escaped characters, in extended character set. See GSM 03.38 character set for more details.
The built in conversion table is made with ISO-8859-15, which seems to be used in Italy too.
Ok! you're right!!
I tried to send this message:" Il servizio è già attivo" from Sms server with special characters like "è" and "à" and the result, on my celluar phone is the following:
"Il servizio C( giC attivo" (note also the space, is not my mistake!!)
I'll try without "cs_convert".
|
|
Tue Nov 17, 2009 16:28
|
tokie:
Ok :)
By the way, why are you using cs_convert = no setting? This setting does not have an effect when you are sending or receiving Unicode messages, but normal SMS files are using GSM alphabet with cs_convert disabled. You have to manually convert your locale (which is what?) to GSM alphabet and vice versa.
Do you see some incorrect characters with internal ISO alphabet conversion? If so, please describe it so I can think if an additional character set table should be created. It's not a big job. For example the next version will have a table for ISO-8859-7 which is Greek alphabet.
If you mean in incoming message, I don't have incorrect characters!
This is a incoming message:
From: 393*********
From_TOA: 91 international, ISDN/telephone
From_SMSC: 3939*******
Sent: 09-11-16 19:23:57
Received: 09-11-16 19:24:32
Subject: Siemens
Modem: Siemens
IMSI: *****************
Report: yes
Alphabet: GSM
Length: 8
Try
Therefore should I use cs_convert = yes or nothing???
|
|
Tue Nov 17, 2009 10:52
|
tokie:
The process list is correct.
How many times you have tried and noticed the hanging? When hanging happens, you stop the smsd but also disconnect the adapter to get it working again? Do you need to reset the phone?
:oops: :oops: :oops: Sorry, sorry, sorry.
I fix the problem(i hope): my phone is discharged!!! :lol: :lol:
I'm sorry but I work remotely and I could not know if it was discharged :lol: :mrgreen:
Some adapters work better with baudrate 115200, but in your case the phone does not support this speed. Can you try without the adapter, using a traditional RS232 port? Some times "real" RS232 ports work better than adapters.
I tried without the adapter, but don't work.
This is my smsd.conf:
devices = Siemens
failed = /var/spool/sms/failed
sent = /var/spool/sms/sent
logfile = /var/log/smsd.log
loglevel = 7
stats = /var/spool/sms/stats
stats_interval = 3600
stats_no_zeroes = yes
[Siemens]
#init = AT&F
init = AT+CPMS="SM"
device = /dev/ttyUSB0
incoming = 2
memory_start = 1
baudrate = 19200
cs_convert = no
smsc = 393359609600
rtscts = no
When I connect directly on RS-232 I change device in device = /dev/ttyS0
I tried also a lower baudrate but don't work.
If you do not have real RS-232 port, you could try to set rtscts = no, but this setting is not good in the normal usage. You can also try a lower baudrate, like 9600.
If I set rtscts = yes don't work: error message: Modem is not clear to send
:lol: :oops: :lol: Sorry, sorry, sorry and sorry again!!!
|
|
Tue Nov 17, 2009 08:45
|
tokie:
Sorry, but I have no answer for this issue right now.
Some things I would like to confirm:
Before updating, you was running 3.1.3 with the same device and with the same USB-RS232 adapter? And it never hanged in this way?
Sorry, I explained badly: I never update! I always had the same version 3.1.5.
Before fix the problem (with the solved post above mentioned, but with the version 3.1.5) don't work, with the following error in log:
Siemens: -> AT
Siemens: Command is sent, waiting for the answer
Siemens: put_command expected (OK)|(ERROR), timeout occurred. 7.
Siemens: <-
Siemens: ->
Siemens: Command is sent, waiting for the answer
Siemens: put_command expected (OK)|(ERROR), timeout occurred. 8.
Does this hanging always happen after a SMS is received, or does it happen randomly? If you run for example 30 minutes without receiving any SMS, there are no troubles?
I received the SMS and, I think randomly, after 2 minutes it's hanging!!
But after it's never worked.
After receiving the SMS there was no problems, belonging to the error of the index of memory (2009-11-16 19:24:31,7, Siemens: <- +CMS ERROR: 321 (Invalid memory index)) that I have already corrected.
Surely you are not running more than one daemon simultaneously (in the ps -efj list, there should be two smsd processes, one "mainprocess" and one "modem process", nothing more)?
This is the answer:
Sms:~# ps -efj | grep sms
root 19307 19303 19307 19303 0 09:34 pts/1 00:00:00 tail -F /var/log/smsd.log
root 19317 1 19317 19317 0 09:35 ? 00:00:00 /usr/local/bin/smsd MAINPROCESS -p/var/run/smsd.pid -i/var/run/smsd.working -l/var/log/smsd.log
root 19319 19317 19317 19317 0 09:35 ? 00:00:00 /usr/local/bin/smsd Siemens____ -p/var/run/smsd.pid -i/var/run/smsd.working -l/var/log/smsd.log
root 19328 19286 19327 19286 0 09:36 pts/0 00:00:00 grep sms
It's wrong??
;) Tks in advance for help me!!
|
|
Mon Nov 16, 2009 18:53
|
tokie: Operating system name and version: Debian Linux 5.0
Version of smsd: 3.1.5
Smsd installed from: package repository
Name and model of a modem / phone: Siemens S53
Interface: Serial adapter Usb-to-rs232
Hi,
I had a problem like in the following post:
[solved] 3.1.3 works, but 3.1.5 makes trouble
I had fix problem changed the baudrate to 19200.
All works.
After, I tried to send a message and smstools works fine, stored message in incoming.
All ok.
After 2 minutes, it's stop to work: without changes!!
I post my tail -F /var/log/smsd.log
2009-11-16 19:24:12,7, Siemens: -> AT+CPMS="SM"
2009-11-16 19:24:12,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:12,7, Siemens: <- +CPMS: 0,30,0,30,0,30 OK
2009-11-16 19:24:13,7, Siemens: -> AT+CSQ
2009-11-16 19:24:13,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:13,7, Siemens: <- +CSQ: 8,99 OK
2009-11-16 19:24:13,6, Siemens: Checking if Modem is registered to the network
2009-11-16 19:24:13,7, Siemens: -> AT+CREG?
2009-11-16 19:24:13,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:14,7, Siemens: <- +CREG: 0,1,"50D7","72D3" OK
2009-11-16 19:24:14,6, Siemens: Modem is registered to the network
2009-11-16 19:24:14,6, Siemens: Selecting PDU mode
2009-11-16 19:24:14,7, Siemens: -> AT+CMGF=0
2009-11-16 19:24:14,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:14,7, Siemens: <- OK
2009-11-16 19:24:14,6, Siemens: Changing SMSC
2009-11-16 19:24:14,7, Siemens: -> AT+CSCA="+393359609600"
2009-11-16 19:24:14,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:15,7, Siemens: <- OK
2009-11-16 19:24:15,6, Siemens: Checking memory size
2009-11-16 19:24:15,7, Siemens: -> AT+CPMS?
2009-11-16 19:24:15,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:15,7, Siemens: <- +CPMS: "SM",0,30,"SM",0,30,"SM",0,30 OK
2009-11-16 19:24:15,6, Siemens: Used memory is 0 of 30
2009-11-16 19:24:15,6, Siemens: No SMS received
2009-11-16 19:24:25,6, Siemens: Checking device for incoming SMS
2009-11-16 19:24:25,6, Siemens: Checking if modem is ready
2009-11-16 19:24:26,7, Siemens: -> AT
2009-11-16 19:24:26,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:26,7, Siemens: <- OK
2009-11-16 19:24:26,6, Siemens: Pre-initializing modem
2009-11-16 19:24:26,7, Siemens: -> ATE0+CMEE=1
2009-11-16 19:24:26,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:26,7, Siemens: <- OK
2009-11-16 19:24:26,6, Siemens: Initializing modem
2009-11-16 19:24:27,7, Siemens: -> AT+CPMS="SM"
2009-11-16 19:24:27,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:27,7, Siemens: <- +CPMS: 0,30,0,30,0,30 OK
2009-11-16 19:24:27,7, Siemens: -> AT+CSQ
2009-11-16 19:24:27,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:28,7, Siemens: <- +CSQ: 9,0 OK
2009-11-16 19:24:28,6, Siemens: Checking if Modem is registered to the network
2009-11-16 19:24:28,7, Siemens: -> AT+CREG?
2009-11-16 19:24:28,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:28,7, Siemens: <- +CREG: 0,1,"50D7","72D3" OK
2009-11-16 19:24:28,6, Siemens: Modem is registered to the network
2009-11-16 19:24:28,6, Siemens: Selecting PDU mode
2009-11-16 19:24:28,7, Siemens: -> AT+CMGF=0
2009-11-16 19:24:29,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:29,7, Siemens: <- OK
2009-11-16 19:24:29,6, Siemens: Changing SMSC
2009-11-16 19:24:29,7, Siemens: -> AT+CSCA="+393359609600"
2009-11-16 19:24:29,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:29,7, Siemens: <- OK
2009-11-16 19:24:29,6, Siemens: Checking memory size
2009-11-16 19:24:30,7, Siemens: -> AT+CPMS?
2009-11-16 19:24:30,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:30,7, Siemens: <- +CPMS: "SM",1,30,"SM",1,30,"SM",1,30 OK
2009-11-16 19:24:30,6, Siemens: Used memory is 1 of 30
2009-11-16 19:24:30,6, Siemens: Trying to get stored message 0
2009-11-16 19:24:30,7, Siemens: -> AT+CMGR=0
2009-11-16 19:24:30,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:31,7, Siemens: <- +CMS ERROR: 321 (Invalid memory index)
2009-11-16 19:24:31,6, Siemens: Trying to get stored message 1
2009-11-16 19:24:31,7, Siemens: -> AT+CMGR=1
2009-11-16 19:24:31,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:32,7, Siemens: <- +CMGR: 0,,26 ( PDU REMOVED) OK
2009-11-16 19:24:32,5, Siemens: SMS received, From: 39392996XXXX
2009-11-16 19:24:32,6, Siemens: Wrote an incoming message file: /var/spool/sms/incoming/Siemens.Rav4YM
2009-11-16 19:24:32,6, Siemens: Deleting message 1
2009-11-16 19:24:32,7, Siemens: -> AT+CMGD=1
2009-11-16 19:24:32,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:33,7, Siemens: <- OK
2009-11-16 19:24:33,6, Siemens: Checking device for incoming SMS
2009-11-16 19:24:33,6, Siemens: Checking memory size
2009-11-16 19:24:33,7, Siemens: -> AT+CPMS?
2009-11-16 19:24:33,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:24:34,7, Siemens: <- +CPMS: "SM",0,30,"SM",0,30,"SM",0,30 OK
2009-11-16 19:24:34,6, Siemens: Used memory is 0 of 30
2009-11-16 19:24:34,6, Siemens: No SMS received
^C
Sms:~# tail -F /var/log/smsd.log
2009-11-16 19:26:13,7, Siemens: -> AT
2009-11-16 19:26:13,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:26:18,7, Siemens: put_command expected (OK)|(ERROR), timeout occurred. 7.
2009-11-16 19:26:18,7, Siemens: <-
2009-11-16 19:26:18,7, Siemens: ->
2009-11-16 19:26:18,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:26:23,7, Siemens: put_command expected (OK)|(ERROR), timeout occurred. 8.
2009-11-16 19:26:23,7, Siemens: <-
2009-11-16 19:26:23,7, Siemens: -> AT
2009-11-16 19:26:23,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:26:28,7, Siemens: put_command expected (OK)|(ERROR), timeout occurred. 9.
2009-11-16 19:26:28,7, Siemens: <-
2009-11-16 19:26:28,7, Siemens: ->
2009-11-16 19:26:28,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:26:33,7, Siemens: put_command expected (OK)|(ERROR), timeout occurred. 10.
2009-11-16 19:26:33,7, Siemens: <-
2009-11-16 19:26:34,7, Siemens: -> AT
2009-11-16 19:26:34,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:26:39,7, Siemens: put_command expected (OK)|(ERROR), timeout occurred. 11.
2009-11-16 19:26:39,7, Siemens: <-
2009-11-16 19:26:39,7, Siemens: ->
2009-11-16 19:26:39,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:26:44,7, Siemens: put_command expected (OK)|(ERROR), timeout occurred. 12.
2009-11-16 19:26:44,7, Siemens: <-
2009-11-16 19:26:44,7, Siemens: -> AT
2009-11-16 19:26:44,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:26:49,7, Siemens: put_command expected (OK)|(ERROR), timeout occurred. 13.
2009-11-16 19:26:49,7, Siemens: <-
2009-11-16 19:26:49,2, smsd: Smsd mainprocess is awaiting the termination of all modem handlers. PID: 18258.
2009-11-16 19:26:49,7, Siemens: ->
2009-11-16 19:26:49,7, Siemens: Command is sent, waiting for the answer
2009-11-16 19:26:54,7, Siemens: put_command expected (OK)|(ERROR), timeout occurred. 14.
2009-11-16 19:26:54,7, Siemens: <-
Why this??
Can anybody help me???
|
Page: 1
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
