|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. The forum is currently read-only, but will open soon. |
Thu Mar 13, 2025 17:44 |
Page: 1
| Keywords: Mode: All keywords (AND) |
|
Tue Feb 24, 2015 12:29
|
astrakid: Linux:
3.1.15:
Smsd installed from: sources
Name and model of a modem: LAN modem (internal ip2serial)
Interface: LAN
I amobserving that the first gateway is more used than the second one.
Is there any reason why? Usually the same type of SMS is sent, and often 2 physical SMS (because of more than 160 characters used). Nevertheless overall the amount should be increasing balanced for both gateways, which is not the case. Both gateways are running, if one is crashing sms server tools is restarted immediately.
Any hints?
regards,
astrakid
|
|
Mon Feb 09, 2015 10:10
|
astrakid: Unfortunately I don't think so.
I am running on this version for two years now and have a stability issue since then (one of two gateway is crashing reguarly). I have to handle this behaviour with help of nagios to restart sms server tools to get the issue resolved.
regards,
astrakid
|
|
Tue May 13, 2014 07:02
|
astrakid: Operating system name and version: RHEL 6.5
Version of smsd: 3.1.15
Smsd installed from: package repository
Name and model of a modem / phone: 2x Ehernet-GSM-GPRS-Modem-G2403RJ
Interface: Ethernet
Hi,
I am using two GSM-IP-Modems (same model). Unfortunately sms server tools is sending most of the SMS via the first configured one. Why does this happen and how can I avoid this?
Kind regards,
astrakid
|
|
Mon Dec 02, 2013 07:57
|
astrakid: Operating system name and version: RHEL 2.6.32-358.23.2.el6.x86_64
Version of smsd: 3.1.15
Smsd installed from: sources
Name and model of a modem / phone: Ethernet GSM GPRS Modem G2403RJ
Interface: IP
I have smsd 3.1.15 running with two GSM-Gateways attached via IP.
On a regular basis one gateway crashes, the logs showing comparable entries:
GSM_IP_2: PIN handling: expected READY, modem answered +CPI: READY
GSM_IP_2: Modem handler 1 terminated abnormally. PID: 9074.
GSM_IP_1: PIN handling: expected READY, modem answered +CPIN READY
GSM_IP_1: Modem handler 0 terminated abnormally. PID: 9073.
Obviously the first message seems to be incomplete, but I don't know, why this happens. Nevertheless the second message seems to be complete, but is not understood by sms server tools.
After a restart of sms server tools the gateways are working fine again.
Is there a way to debug the error?
regards,
astrakid
|
|
Wed Jun 05, 2013 15:18
|
astrakid: Hi,
I found out, that stats are written if an sms has been rejected!
Anyone knows why? Or is there a chance to force smsservertools to write statistics always?
regards,
astrakid
|
|
Fri May 31, 2013 10:16
|
astrakid: great, good starting point.
sendsms is not working? any error messages?
I did it always via smsd by a simple textfile which was copied to /....../outgoing - then smsd checks the file and processes it.
that worked fine for me.
regards,
astrakid
|
|
Fri May 31, 2013 09:39
|
astrakid: ok. good luck.
maybe this link helps you further:
http://www.developershome.com/sms/cpmsCommand.asp
if you like we can get into a direct discussion via mail.
regards,
astrakid
|
|
Fri May 31, 2013 07:25
|
astrakid: hi,
I checked my old logs again and i am quite sure that after changing the parameter to "incoming = 0" changed the behaviour.
I couldn't find any further CPMS-messages in the logs later on even after a restart of smsd and sms were sent successfully.
regards,
astrakid
|
|
Fri May 31, 2013 06:40
|
astrakid: hi,
i had a look into former log_files when using a usb-modem.
CPMS seems to be used, but concerning logs I guess they are only necessary for incoming SMS...f
2013-02-25 14:58:10,5, GSM_USB: Modem handler 0 has started. PID: 7110.
2013-02-25 14:58:10,5, GSM_USB: Using check_memory_method 1: CPMS is used.
2013-02-25 14:58:10,6, GSM_USB: Checking device for incoming SMS
2013-02-25 14:58:10,6, GSM_USB: Checking if modem is ready
2013-02-25 14:58:10,7, GSM_USB: -> AT
2013-02-25 14:58:10,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:11,7, GSM_USB: <- OK
2013-02-25 14:58:11,6, GSM_USB: Pre-initializing modem
2013-02-25 14:58:11,7, GSM_USB: -> ATE0+CMEE=1;+CREG=2
2013-02-25 14:58:11,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:11,5, smsd: Moved file /home/sms/.sms/outgoing/20130225_145807_smsgw.out.9Qdn36 to /home/sms/.sms/checked
2013-02-25 14:58:11,7, GSM_USB: <- OK
2013-02-25 14:58:11,6, GSM_USB: Checking if modem needs PIN
2013-02-25 14:58:11,7, GSM_USB: -> AT+CPIN?
2013-02-25 14:58:11,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:12,5, smsd: Moved file /home/sms/.sms/outgoing/20130225_145807_smsgw.out.Lkt0iC to /home/sms/.sms/checked
2013-02-25 14:58:12,7, GSM_USB: <- +CPIN: READY OK
2013-02-25 14:58:12,7, GSM_USB: -> AT+CSQ
2013-02-25 14:58:12,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:12,7, GSM_USB: <- +CSQ: 14,99 OK
2013-02-25 14:58:12,6, GSM_USB: Signal Strength Indicator: (14,99) -85 dBm (Workable), Bit Error Rate: not known or not detectable
2013-02-25 14:58:12,6, GSM_USB: Checking if Modem is registered to the network
2013-02-25 14:58:12,7, GSM_USB: -> AT+CREG?
2013-02-25 14:58:12,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:13,7, GSM_USB: <- +CREG: 2,1, 1690, FF20 OK
2013-02-25 14:58:13,6, GSM_USB: Modem is registered to the network
2013-02-25 14:58:13,6, GSM_USB: Location area code: 1690, Cell ID: FF20
2013-02-25 14:58:13,7, GSM_USB: -> AT+CSQ
2013-02-25 14:58:13,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:13,7, GSM_USB: <- +CSQ: 14,99 OK
2013-02-25 14:58:13,6, GSM_USB: Signal Strength Indicator: (14,99) -85 dBm (Workable), Bit Error Rate: not known or not detectable
2013-02-25 14:58:13,6, GSM_USB: Selecting PDU mode
2013-02-25 14:58:13,7, GSM_USB: -> AT+CMGF=0
2013-02-25 14:58:13,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:14,7, GSM_USB: <- OK
2013-02-25 14:58:14,6, GSM_USB: Changing SMSC
2013-02-25 14:58:14,7, GSM_USB: -> AT+CSCA="+491710760000"
2013-02-25 14:58:14,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:14,7, GSM_USB: <- OK
2013-02-25 14:58:14,7, GSM_USB: -> AT+CIMI
2013-02-25 14:58:14,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:15,7, GSM_USB: <- 262019035069075 OK
2013-02-25 14:58:15,7, GSM_USB: -> AT+CGSN
2013-02-25 14:58:15,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:15,7, GSM_USB: <- 351000033114367 OK
2013-02-25 14:58:15,5, GSM_USB: CGSN: 351000033114367
2013-02-25 14:58:15,5, GSM_USB: IMSI: 262009000069075
2013-02-25 14:58:15,6, GSM_USB: Checking if reading of messages is supported
2013-02-25 14:58:15,7, GSM_USB: -> AT+CPMS?
2013-02-25 14:58:15,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:16,7, GSM_USB: <- +CPMS: "SM",0,15,"SM",0,15,"SM",0,15 OK
2013-02-25 14:58:16,6, GSM_USB: Checking memory size
2013-02-25 14:58:16,7, GSM_USB: -> AT+CPMS?
2013-02-25 14:58:16,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:16,7, GSM_USB: <- +CPMS: "SM",0,15,"SM",0,15,"SM",0,15 OK
2013-02-25 14:58:16,6, GSM_USB: Used memory is 0 of 15
2013-02-25 14:58:16,6, GSM_USB: No SMS received
2013-02-25 14:58:16,6, GSM_USB: I have to send 1 short message for /home/sms/.sms/checked/20130225_145807_smsgw.out.9Qdn36
2013-02-25 14:58:16,6, GSM_USB: Sending SMS from root@sms-test.domain (root) to ************
2013-02-25 14:58:16,6, GSM_USB: Checking if modem is ready
2013-02-25 14:58:16,7, GSM_USB: -> AT
2013-02-25 14:58:16,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:17,7, GSM_USB: <- OK
2013-02-25 14:58:17,6, GSM_USB: Pre-initializing modem
2013-02-25 14:58:17,7, GSM_USB: -> ATE0+CMEE=1;+CREG=2
2013-02-25 14:58:17,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:17,7, GSM_USB: <- OK
2013-02-25 14:58:17,6, GSM_USB: Checking if modem needs PIN
2013-02-25 14:58:17,7, GSM_USB: -> AT+CPIN?
2013-02-25 14:58:17,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:18,7, GSM_USB: <- +CPIN: READY OK
2013-02-25 14:58:18,7, GSM_USB: -> AT+CSQ
2013-02-25 14:58:18,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:18,7, GSM_USB: <- +CSQ: 14,99 OK
2013-02-25 14:58:18,6, GSM_USB: Signal Strength Indicator: (14,99) -85 dBm (Workable), Bit Error Rate: not known or not detectable
2013-02-25 14:58:18,6, GSM_USB: Checking if Modem is registered to the network
2013-02-25 14:58:18,7, GSM_USB: -> AT+CREG?
2013-02-25 14:58:18,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:19,7, GSM_USB: <- +CREG: 2,1, 1690, FF20 OK
2013-02-25 14:58:19,6, GSM_USB: Modem is registered to the network
2013-02-25 14:58:19,6, GSM_USB: Selecting PDU mode
2013-02-25 14:58:19,7, GSM_USB: -> AT+CMGF=0
2013-02-25 14:58:19,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:19,7, GSM_USB: <- OK
2013-02-25 14:58:19,6, GSM_USB: Changing SMSC
2013-02-25 14:58:19,7, GSM_USB: -> AT+CSCA="+491710760000"
2013-02-25 14:58:19,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:20,7, GSM_USB: <- OK
2013-02-25 14:58:20,7, GSM_USB: -> AT+CMGS=21
2013-02-25 14:58:20,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:20,7, GSM_USB: <- >
2013-02-25 14:58:20,7, GSM_USB: -> 0011000C90940140000000000FF07E1705821168B01^Z
2013-02-25 14:58:20,7, GSM_USB: Command is sent, waiting for the answer
2013-02-25 14:58:22,7, GSM_USB: <- +CMGS: 137 OK
2013-02-25 14:58:22,5, GSM_USB: SMS sent, Message_id: 137, To: ************, sending time 6 sec.
=>
|
|
Wed May 29, 2013 13:32
|
astrakid: correct, but before i was using an usb-stick and didn't have to use any special init-strings.
regards,
astrakid
|
|
Wed May 29, 2013 13:00
|
astrakid: quite simple:
devices = GSM_IP_1
incoming = /opt/sms/data/incoming
outgoing = /opt/sms/data/outgoing
checked = /opt/sms/data/checked
failed = /opt/sms/data/failed
sent = /opt/sms/data/sent
logfile = /opt/sms/logs/smsd.log
loglevel = 6
user = sms
group = sms
blockafter = 3
blocktime = 30
errorsleeptime = 10
[GSM_IP_1]
device = @<ip-adresse>
baudrate = 115200
pin = XXXX
incoming = no
trust_spool = no
check_network = 2
message_limit = 360
message_count_clear = 180
keep_open = no
|
|
Wed May 29, 2013 11:23
|
astrakid: hi,
from my logs i guess it have to be these commands:
2013-05-28 14:49:47,7, GSM_IP_2: -> AT
2013-05-28 14:49:47,7, GSM_IP_2: Command is sent, waiting for the answer
2013-05-28 14:49:47,7, GSM_IP_2: <- OK
2013-05-28 14:49:47,6, GSM_IP_2: Pre-initializing modem
2013-05-28 14:49:47,7, GSM_IP_2: -> ATE0+CMEE=1;+CREG=2
2013-05-28 14:49:47,7, GSM_IP_2: Command is sent, waiting for the answer
2013-05-28 14:49:48,7, GSM_IP_2: <- OK +CREG: 1,"1637","EFE1"
2013-05-28 14:49:48,6, GSM_IP_2: Checking if modem needs PIN
2013-05-28 14:49:48,7, GSM_IP_2: -> AT+CPIN?
2013-05-28 14:49:48,7, GSM_IP_2: Command is sent, waiting for the answer
2013-05-28 14:49:48,7, GSM_IP_2: <- +CPIN: READY
2013-05-28 14:49:48,7, GSM_IP_2: -> AT+CSQ
2013-05-28 14:49:48,7, GSM_IP_2: Command is sent, waiting for the answer
2013-05-28 14:49:49,7, GSM_IP_2: <- +CSQ: 22,0 OK
2013-05-28 14:49:49,6, GSM_IP_2: Signal Strength Indicator: (22,0) -69 dBm (Excellent), Bit Error Rate: less than 0.2 %
2013-05-28 14:49:49,6, GSM_IP_2: Checking if Modem is registered to the network
2013-05-28 14:49:49,7, GSM_IP_2: -> AT+CREG?
2013-05-28 14:49:49,7, GSM_IP_2: Command is sent, waiting for the answer
2013-05-28 14:49:49,7, GSM_IP_2: <- +CREG: 2,1,"1637","EFE1" OK
2013-05-28 14:49:49,6, GSM_IP_2: Modem is registered to the network
2013-05-28 14:49:49,6, GSM_IP_2: Selecting PDU mode
2013-05-28 14:49:49,7, GSM_IP_2: -> AT+CMGF=0
2013-05-28 14:49:49,7, GSM_IP_2: Command is sent, waiting for the answer
2013-05-28 14:49:50,7, GSM_IP_2: <- OK
2013-05-28 14:49:50,7, GSM_IP_2: -> AT+CMGS=41
2013-05-28 14:49:50,7, GSM_IP_2: Command is sent, waiting for the answer
2013-05-28 14:49:50,7, GSM_IP_2: <- >
2013-05-28 14:49:50,7, GSM_IP_2: -> 0011000C919471[12 numbers]FF1EF4F29C0E7287C768503B3C9F97150AE213E47C5241D22294990D01^Z
2013-05-28 14:49:50,7, GSM_IP_2: Command is sent, waiting for the answer
2013-05-28 14:49:53,7, GSM_IP_2: <- +CMGS: 129 OK
=> the string for sending an sms seems to be somehow crypted...
|
|
Wed May 29, 2013 10:12
|
astrakid: hi,
i am not sure, but i guess you have to use the pc-suite-mode. when using filetransfer you are only able to you the mass-storage-part of the phone i think...
regards,
astrakid
|
|
Wed May 29, 2013 09:57
|
astrakid: have a look at minicom. with this tool you can execute at-commands and other things.
regards,
astrakid
|
|
Mon May 27, 2013 13:51
|
astrakid: Hi,
I have installed sms server tools 3 on a CentOS server which is working very stable.
We bought cheap IP-GSM-Gateways from
http://www.mcm-control.com/epages/es122015.sf/de_DE/?ObjectPath=/Shops/es122015_mcm-control/Categories/%22GSM%20Modems%22
After some problems at initial configuration they are now working quite good. Comparing to other devices which are much more expensive we are quite confident with them.
kind regards,
astrakid
|
|
Wed May 22, 2013 09:52
|
astrakid: CentOS 6:
latest version 3.1.15:
Smsd installed from: sources
MCM control GSM GPRS Modem G2403J:
Interface: IP G2403RJ
Hi,
I am not able to get statistics anymore.Extract from smsd.conf:
[sms@dogfitsmtst33 config]$ cat smsd.conf
devices = GSM_IP_1,GSM_IP_2
incoming = /opt/smsservertools3/data/incoming
outgoing = /opt/smsservertools3/data/outgoing
checked = /opt/smsservertools3/data/checked
failed = /opt/smsservertools3/data/failed
sent = /opt/smsservertools3/data/sent
stats = /opt/smsservertools3/stats
logfile = /opt/smsservertools3/logs/smsd.log
loglevel = 9
whitelist = /opt/smsservertools3/config/whitelist
stats_interval = 60
stats_no_zeroes = yes
status_interval = 1
status_include_counters = yes
status_signal_quality = yes
[...]
Directories do exist:
[sms@dogfitsmtst33 smsservertools3]$ ls -l
insgesamt 24
drwxr-xr-x 2 sms sms 4096 17. Mai 15:59 bin
drwxr-xr-x 2 sms sms 4096 22. Mai 11:35 config
drwxr-xr-x 9 sms sms 4096 27. Feb 14:34 data
drwxr-xr-x 2 sms sms 4096 22. Mai 11:34 logs
-rw-r--r-- 1 sms sms 6 22. Mai 11:36 smsd.pid
drwxrwxr-x 2 sms sms 4096 22. Mai 11:36 stats
sms is running as user "sms". other logs are written.
Counters are written as well, and temporarely stat-file also:
[sms@dogfitsmtst33 stats]$ pwd
/opt/smsservertools3/stats
[sms@dogfitsmtst33 stats]$ ls -l
insgesamt 12
-rw-r--r-- 1 sms sms 13 22. Mai 11:49 GSM_IP_1.counter
-rw-r--r-- 1 sms sms 13 22. Mai 11:49 GSM_IP_2.counter
-rw-rw-r-- 1 sms sms 3104 22. Mai 11:49 stats.tmp
What am I missing?
kind regards,
astrakid
|
|
Wed May 22, 2013 06:30
|
astrakid: Problem solved.
There is a timeout-parameter inside the gateways - when disabled, everything works fine. when enabled (parameter set in minutes) the gateway cuts the connection. sms server tools need a restart to reestablish the connection again.
kind regards,
astrakid
|
|
Tue May 21, 2013 08:46
|
astrakid: CentOS 6:
latest version 3.1.15:
Smsd installed from: sources
MCM control GSM GPRS Modem G2403J:
Interface: IP
Hi,
my GSM-IP-modems are getting stuck after some time. If there is no activity for a special duration and then an sms has to be sent, the modem is not reacting anymore:
2013-05-21 08:51:55,6, GSM_IP_1: I have to send 1 short message for /opt/smsservertools3/data/checked/20130521_085149_smsgw.out.DCdfNG
2013-05-21 08:51:55,6, GSM_IP_1: Sending SMS from to 4917********
2013-05-21 08:51:55,6, GSM_IP_1: Checking if modem is ready
2013-05-21 08:51:55,7, GSM_IP_1: -> AT
Waiting for now 90 minutes didn't solves it.
The sms-processes are not ok as well I guess:
sms 15790 1 0 May17 ? 00:00:08 /opt/smsservertools3/bin/smsd -n MAINPROCESS -p/opt/smsservertools3/smsd.pid -i/opt/smsservertools3/smsd.working -c/opt/smsservertools3/config/smsd.conf -l/opt/smsservertools3/logs/smsd.log
sms 15792 15790 0 May17 ? 00:00:09 [smsd] <defunct>
sms 15793 15790 0 May17 ? 00:00:10 /opt/smsservertools3/bin/smsd -n GSM_IP_2___ -p/opt/smsservertools3/smsd.pid -i/opt/smsservertools3/smsd.working -c/opt/smsservertools3/config/smsd.conf -l/opt/smsservertools3/logs/smsd.log
r
Is there a way to get more information to narrow down this issue? Or any hint how to solve this immediately?
Kind regards,
astrakid
|
|
Tue May 14, 2013 12:13
|
astrakid: hi,
unbelievable - after unplugging power and replugging it is working...
I encountered, that sometimes it is necessary to power off the device again to get it working.
regards,
astrakid
|
|
Mon May 13, 2013 15:43
|
astrakid: Hi,
with loglevel 9 I get the following additional information:
Checking if modem is ready
-> AT
Command is sent, waiting for the answer
put_command expected (OK)|(ERROR), timeout occurred. 1.
<-
->
Command is sent, waiting for the answer
put_command expected (OK)|(ERROR), timeout occurred. 2.
[...]
Any hint?
I don't know how to debug a moedm via TCP/IP...
regards,
astrakid
|
|
Mon May 13, 2013 15:10
|
astrakid: CentOS 5.8:
latest version 3.1.15:
Smsd installed from: sources
MCM control GSM GPRS Modem G2403J:
Interface: IP
we just bought this IP-GSM-Modem, which we want to work with smsd.
Now I'm afraid i can't get it to work - I suspect some issues in the configuration of the device itself.
Here the link to the device (german language)
http://www.mcm-control.com/Ehernet-GSM-GPRS-Modem-G2403RJ
The configuration is done via ds-manager:
http://docs.tibbo.com/soism/index.html?ds_manager.htm
but there are a lot of entries i don't know what to set. As result I get in smsd at startup the message "Modem is not ready to answer commands".
Any hint at which srew I have to drive?
kind regards,
astrakid
|
|
Tue Apr 09, 2013 11:23
|
astrakid: Hi,
there are several ways to accomplish this.
At least you have to parse the mail for the necessary content, usually the original-to and the body (maybe the subject as well).
you have to extract these information from the mail (i did it by using formail and a modified version of "email2sms" delivered by smsservertools) and put it into the outgoing-folder.
regards,
astrakid
|
|
Tue Mar 19, 2013 13:06
|
astrakid: ok.
thanks vevertheless.
kind regards,
astrakid
|
|
Mon Mar 18, 2013 07:16
|
astrakid: ups, that is awkward... I assumed that sendsms is a binary without looking into it. very stupid from me.
is it possible to include the config file within sendsms, so taht in case of another change in sms-config file sendsms is aware of the change automatically?
kind regards and thanks!
astrakid
|
|
Fri Mar 15, 2013 13:07
|
astrakid: Hi,
i have an issue regarding sendsms - smsd is running with different configuration for folders - i put all below /opt/sms.
but when I create an outgoing sms via sendsms, it is ignoring this configuration and putting the file into /var/spool/sms/outgoing.
From my point of view this is a bug... Or am I missing something?
regards,
astrakid
|
Page: 1
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
