|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. The forum is currently read-only, but will open soon. |
Fri Mar 14, 2025 10:52 |
Page: 1 2 Next
| Keywords: Mode: All keywords (AND) |
|
Tue Oct 11, 2011 20:07
|
aschneck: I'm not sure. Format of number is correct. But there where several files in parallel to be transferred and I'm not sure whether such couldnt be sent (found no one in the error folder)
|
|
Tue Oct 11, 2011 17:09
|
aschneck: Hmmm..., I havent set up a SMSC in the config (never done it before, with none of my modems), so I think the SIM decided which will be used. I'll ask the provider for the SMSC, but to beware misunderstanding. I can send SMS using this modem, only get this message some times.
|
|
Tue Oct 11, 2011 12:54
|
aschneck: SLES11 SP1:
3.1.14:
Smsd installed from: sources
Name and model of a modem / phone: Multitech LAN Modem
Interface: network
Hi,
if I get this error sending a sms, does it mean there is an error on the remote site, or do I have a local problem, e.g. with my modem / sim card ?
The modem answer was not OK: +CMS ERROR: 28 (Unindentified subscriber)
Axel
|
|
Fri Oct 07, 2011 18:09
|
aschneck: As I know it isn't possible. Because we also want to send only at day times (for another reason) I set up 2 cron jobs, one for starting at the morning and one for stopping at the evening the sms daemon.
Axel
|
|
Wed Sep 07, 2011 07:57
|
aschneck: Operating system name and version: SLES10 SP3
Version of smsd: 3.1.14
Smsd installed from: sources
Name and model of a modem / phone: Multitech MTCBA-G2-EN2-ED-EU
Interface: LAN
Hi, using the above system I get sometimes (2-3 times daily) this error message in the logfile:
GSMLAN1: put_command expected (OK)|(ERROR), timeout occurred. 1
What does this mean and are there actions needed, like restart daemon or modem?
cheers,
Axel
|
|
Wed Jul 27, 2011 13:20
|
|
|
|
Wed Jul 27, 2011 05:46
|
aschneck: Hi,
this system sents sms like short letters (but no spam) to changing customer numbers, so I cannot say if we ever sent succsessful messages to such failed numbers.
It's hard to find out, because I have to archive and check logfiles.
( PRIVATE BLOCK )
Axel
|
|
Tue Jul 26, 2011 09:38
|
aschneck: Operating system name and version: SLES10 SP3 64Bit
Version of smsd: 3.1.14
Smsd installed from: sources
Name and model of a modem / phone: MTCBA-G2-EN2-ED-EU
Interface: LAN
Sometimes I get errors like following in the system; are these errors local errors or remote? If these errors are local what might be the right action?
I'm not sure what the reason might be, what I should do over the alarm handler (restart smsd?) and how it might be possible to prevent such errors?
2011-07-15 08:10:39,6, GSMLAN1: Checking if Modem is registered to the network
2011-07-15 08:10:39,7, GSMLAN1: -> AT+CREG?
2011-07-15 08:10:39,7, GSMLAN1: Command is sent, waiting for the answer
2011-07-15 08:10:39,7, GSMLAN1: <- +CREG: 2,1,"0741","8F49" OK
2011-07-15 08:10:39,6, GSMLAN1: Modem is registered to the network
2011-07-15 08:10:39,7, GSMLAN1: -> AT+CMGS=140
2011-07-15 08:10:39,7, GSMLAN1: Command is sent, waiting for the answer
2011-07-15 08:10:40,7, GSMLAN1: <- >
2011-07-15 08:10:40,7, GSMLAN1: -> 001..........<long line>
2011-07-15 08:10:40,7, GSMLAN1: Command is sent, waiting for the answer
2011-07-15 08:10:43,7, GSMLAN1: <- +CMS ERROR: 21 (Short message transfer rejected)
2011-07-15 08:10:43,3, GSMLAN1: The modem answer was not OK: +CMS ERROR: 21 (Short message transfer rejected)
2011-07-15 08:10:43,7, GSMLAN1: Running alarmhandler: /usr/hfg/script/root/smsalert.sh ALARM 2011-07-15 08:10:43 3 GSMLAN1 "The modem answer was not OK: +CMS ERROR: 21 (Short message transfer rejected)"
2011-07-15 08:10:44,7, GSMLAN1: Done: alarmhandler, execution time 1 sec., status: 0 (0)
Axel
|
|
Tue Feb 01, 2011 16:33
|
aschneck: Operating system name and version: SLES10 SP3
Version of smsd: 3.1.14
Smsd installed from: sources
Name and model of a modem / phone: MTCBA-G-EN-F4-ED-EU (Modem with Accessory Kit) MultiModem GPRS Class 10, Quad Band (Ethernet)
Interface: TCP/IP
Have sometimes (on two servers) the same problem. It seems to be that the daemon after writing some errors will stop working with the modem.
See error log entries at bottom. At the top of these lines you see the first errors that called the alarm handler. I have a monitoring script that will restart the daemon in this case, so there was the first daemon restart right after the first lines.
After these messages (dont know how fast after) smsd stops talking to the modem but still move new files from outgoing to checked folder.
Doing a ps -ef|grep smsd |grep -v grep will show not only a line showing the running daemon but also a line containing:
[smsd] <defunct>
which means there was a broken task...
I have to restart sms daemon than to get it working again.
But I have no idea what maybe the cause...
error-log:
2011-01-27 13:36:36,7, GSMLAN1: Command is sent, waiting for the answer
2011-01-27 13:36:36,7, GSMLAN1: <- +CMS ERROR: 512 (MM establishment failure / weak signal, loosing connection)
2011-01-27 13:36:36,3, GSMLAN1: The modem answer was not OK: +CMS ERROR: 512 (MM establishment failure / weak signal, loosing connection)
2011-01-27 13:36:36,7, GSMLAN1: Running alarmhandler: /usr/ksp/script/root/smsalert.sh ALARM 2011-01-27 13:36:36 3 GSMLAN1 "The modem answer was not OK: +CMS ERROR: 512 (MM establishment failure / weak signal, loosing connection)"
2011-01-27 13:36:36,7, GSMLAN1: Done: alarmhandler, execution time 0 sec., status: 0 (0)
2011-01-27 13:36:36,3, GSMLAN1: Exec: alarmhandler said something:
2011-01-27 13:36:36,3, GSMLAN1: ! ALARM 2011-01-27 13:36:36 3 GSMLAN1 The modem answer was not OK: +CMS ERROR: 512 (MM establishment failure / weak signal, loosing connection)
2011-01-27 13:36:36,5, GSMLAN1: Waiting 10 sec. before retrying
2011-01-27 13:36:46,6, GSMLAN1: Checking if modem is ready
2011-01-27 13:36:48,5, GSMLAN1: Everything ok now.
2011-01-27 13:40:16,5, smsd: Outgoing file checker has started. PID: 16081.
2011-01-27 13:40:16,5, smsd: Everything ok now.
2011-01-27 15:02:30,7, GSMLAN1: -> AT
2011-01-27 15:02:30,7, GSMLAN1: Command is sent, waiting for the answer
2011-01-27 15:02:35,7, GSMLAN1: put_command expected (OK)|(ERROR), timeout occurred. 1.
2011-01-27 15:02:35,7, GSMLAN1: <-
2011-01-27 15:02:35,7, GSMLAN1: -> .
2011-01-27 15:02:35,7, GSMLAN1: Command is sent, waiting for the answer
2011-01-27 15:02:40,7, GSMLAN1: put_command expected (OK)|(ERROR), timeout occurred. 2.
2011-01-27 15:02:40,7, GSMLAN1: <-
2011-01-27 15:02:41,7, GSMLAN1: -> AT
2011-01-27 15:02:41,7, GSMLAN1: Command is sent, waiting for the answer
2011-01-27 15:02:46,7, GSMLAN1: put_command expected (OK)|(ERROR), timeout occurred. 3.
2011-01-27 15:02:46,7, GSMLAN1: <-
2011-01-27 15:02:46,7, GSMLAN1: -> .
2011-01-27 15:02:46,7, GSMLAN1: Command is sent, waiting for the answer
2011-01-27 15:02:51,7, GSMLAN1: put_command expected (OK)|(ERROR), timeout occurred. 4.
2011-01-27 15:02:51,7, GSMLAN1: <-
2011-01-27 15:02:51,7, GSMLAN1: -> AT
2011-01-27 15:02:51,7, GSMLAN1: Command is sent, waiting for the answer
2011-01-27 15:02:57,7, GSMLAN1: put_command expected (OK)|(ERROR), timeout occurred. 5.
2011-01-27 15:02:57,7, GSMLAN1: <-
2011-01-27 15:02:57,7, GSMLAN1: -> .
2011-01-27 15:02:57,7, GSMLAN1: Command is sent, waiting for the answer
2011-01-27 15:03:02,7, GSMLAN1: put_command expected (OK)|(ERROR), timeout occurred. 6.
2011-01-27 15:03:02,7, GSMLAN1: <-
2011-01-27 15:03:02,7, GSMLAN1: -> AT
2011-01-27 15:03:02,7, GSMLAN1: Command is sent, waiting for the answer
2011-01-27 15:03:07,7, GSMLAN1: put_command expected (OK)|(ERROR), timeout occurred. 7.
2011-01-27 15:03:07,7, GSMLAN1: <-
2011-01-27 15:03:08,7, GSMLAN1: -> .
2011-01-27 15:03:08,7, GSMLAN1: Command is sent, waiting for the answer
2011-01-27 15:03:13,7, GSMLAN1: put_command expected (OK)|(ERROR), timeout occurred. 8.
2011-01-27 15:03:13,7, GSMLAN1: <-
2011-01-27 15:03:13,7, GSMLAN1: -> AT
2011-01-27 15:03:13,7, GSMLAN1: Command is sent, waiting for the answer
2011-01-27 15:03:18,7, GSMLAN1: put_command expected (OK)|(ERROR), timeout occurred. 9.
2011-01-27 15:03:18,7, GSMLAN1: <-
2011-01-27 15:03:18,7, GSMLAN1: -> .
2011-01-27 15:03:18,7, GSMLAN1: Command is sent, waiting for the answer
2011-01-27 15:03:24,7, GSMLAN1: put_command expected (OK)|(ERROR), timeout occurred. 10.
2011-01-27 15:03:24,7, GSMLAN1: <-
2011-01-27 15:07:24,7, GSMLAN1: -> AT
2011-01-27 15:07:24,7, GSMLAN1: Command is sent, waiting for the answer
2011-01-27 15:07:29,7, GSMLAN1: put_command expected (OK)|(ERROR), timeout occurred. 1.
2011-01-27 15:07:29,7, GSMLAN1: <-
2011-01-27 15:07:29,7, GSMLAN1: -> .
2011-01-27 15:07:29,7, GSMLAN1: Command is sent, waiting for the answer
2011-01-27 15:07:35,7, GSMLAN1: put_command expected (OK)|(ERROR), timeout occurred. 2.
2011-01-27 15:07:35,7, GSMLAN1: <-
Axel
|
|
Tue Feb 01, 2011 15:47
|
aschneck: Operating system name and version: SLES10SP3
Version of smsd: 3.1.14
Name and model of a modem / phone: Network Device
Hi,
ist it possible to restrict the times when SMSD will send out sms?
We like to send only between special hours, like 08:00 - 20:00
So, could this be done in configuration?
Sure, I can stop the whole daemon, but it would be better if I can do it in config, so I dont have to stop also my several monitoring functions that will check for a running and working sms daemon. :lol:
Best Regards,
Axel
|
|
Tue Nov 16, 2010 17:45
|
aschneck: yep, the term CPU-intensive was a theoretical, dont know how to better explain what I mean that it normally would be better, to filter at the first step :-)
OK, so I'll procede with my already started 'job' to try to find out which error I should alert and which not :mrgreen:
The main reason behind these question is / was to find out at what errors I have to try to restart the daemon or check the modem.
|
|
Tue Nov 16, 2010 17:39
|
aschneck: oops, I'm so sorry, using the current one :-)
3.1.14
|
|
Tue Nov 16, 2010 14:34
|
aschneck: Thanks, I'll try it.
Only have to find a time-window for stopping the server :-)
|
|
Tue Nov 16, 2010 14:32
|
aschneck: Sorry, hope that is not a too stupid question :roll:
Is this an error talking about a local problem or does it only mean that the remote site rejectetd sms receiving?
GSMLAN1: The modem answer was not OK: +CMS ERROR: 21 (Short message transfer rejected)
If it is a local error (getting it while bulk sending), should / can I put any parameters in my config to avoid?
Axel
|
|
Tue Nov 16, 2010 14:20
|
aschneck: Is it possible to configure the alarm handler that the alarm handler-Script will only be called on local errors?
For example, if dialing and everything local works, but the remote site rejects receiving SMS, I do not need an alarm handler generated Mail (using a bash script called by the alarm handler). But if an error occurs that depends on my site, eg, modem doesnt work, I need an email.
Maybe I misread the docu, but I couldnt find something about.
Sure, I can filter remote errors in my script using grep, but therefore I have to know which errors are local and which remote & it needs more 'cpu time' if calling everytime the shell script and filtering rather then generate no alarm.
Axel
|
|
Tue Nov 16, 2010 14:15
|
aschneck: Maybe I missed to find it in the 'docu'?
Seems to be that tools will do retries on send failures:
---------------------
2010-11-15 15:52:57,3, GSMLAN1: The modem answer was not OK: +CMS ERROR: 21+CMTI: "SM",20 (Short message transfer rejected)
2010-11-15 15:52:57,5, GSMLAN1: Waiting 10 sec. before retrying
----------------------
If we submit bulk sms most of such reject will mean that the used SMS will not accept SMS, so retries are not needed.
Is it possible to disable such retries?
Axel
|
|
Mon Sep 20, 2010 20:59
|
aschneck: Hi Alexander, sorry I dont know your Gateway. I was only writing about using GSM Network devices in general and the one I'm using. Port 5000 is the Port I configured (in this case it's also the default) for my device in it's web interface configuration. If possible I would help, but I dont know this Gateway. My understanding is that sms server tools needs exclusive access to the network device using a socks connection.
|
|
Mon Sep 20, 2010 20:41
|
aschneck: I've got it from the docu :-)
Here is an example file:
devices = GSMLAN1
logfile = /var/log/smsd.log
loglevel = 7
failed = /var/spool/sms/failed
report = /var/spool/sms/report
sent = /var/spool/sms/sent
stats = /var/spool/sms/stats
#errorsleeptime = 20
#store_received_pdu = 3
date_filename = 1
[GSMLAN1]
device = @192.168.15.2:5000
incoming = yes
device_open_alarm_after = 5
socket_connection_alarm_after = 5
|
|
Mon Sep 20, 2010 20:23
|
aschneck: Yes, using network GSM devices is working well. I do it with a Multitech MTCBA-G-EN-F4-ED-EU for example. :D
cu,
Axel
|
|
Fri Aug 13, 2010 09:44
|
|
|
|
Fri Aug 13, 2010 09:17
|
aschneck: Hi, I have one more question using network GSM,
Is it possible to use one Network GSM Module from two sms daemons on different servers?
If configuring only on for incoming=yes?
Axel
|
|
Fri Aug 13, 2010 07:44
|
aschneck: Good Morning,
yep, but you are also very fast in respondig!
If needed/wanted I can post all settings I made anywhere here?
But the most important I already wrote.
Also you can 'remind' me if someone other in the future will ask; if I can help, I'll do
cu,
Axel :lol:
|
|
Thu Aug 12, 2010 15:28
|
aschneck: Yippiheiho :P
I've got it working.
In the ModemSetup I had to choose one mor option.
As you wrote first telnet have to be disabled.
But in the IP Setup the function "Raw Dialout" has to be ENABLED.
Also AutoDialout has to be ENABLED.
cu,
Axel
|
|
Thu Aug 12, 2010 15:05
|
aschneck: Bought a MTCBA-G-EN-F4-ED-EU and got it today. Just installed it into network. Put a Vodafone SIM into. Connected manually using telnet <ip> 5000, logged in. Send a AT+CPIN?, got back "ready" and the TR LED went to status on (is still on). Sent a SMS manually with AT+CMGS="<nr>" <CR>thisisatest<CTRL-Z>
Got an +CMGS: 9 and OK
Got the SMS on my mobile phone.
Then I tried to con´figure server tools.
Added another device, called it gsmlan1 with the following lines:
[GSMLAN1]
device = @10.0.0.16:5000
incoming = yes
read_timeout = 20
device_open_alarm_after = 5
socket_connection_alarm_after = 5
Restarting daemon and monitoring the smsd.log shows that the daemon tries to connect.
But it seems to be that connecting using sockets the feedback is another (or nearly nothing).
See lines like these in the log:
2010-08-12 17:02:37,3, GSMLAN1: Unexpected input: ▒▒▒▒ ▒▒#▒▒'
2010-08-12 17:02:37,7, GSMLAN1: -> AT
2010-08-12 17:02:37,7, GSMLAN1: Command is sent, waiting for the answer
2010-08-12 17:02:57,7, GSMLAN1: put_command expected (OK)|(ERROR), timeout occurred. 1.
2010-08-12 17:02:57,7, GSMLAN1: <-
2010-08-12 17:02:58,7, GSMLAN1: ->
So, I think I need some special init-strings or else in the device config. But I dont know which one and device documentation doesnt help.
Any hints?
Please :mrgreen:
Axel
|
|
Tue Aug 10, 2010 12:51
|
aschneck: OK, I'll search for a reseller in germany.
This one for example:
http://de.futureelectronics.com/de/Search.aspx?dsNav=Ntk:PartNumberSearch%7cMTCBA%2f-G%7c1%7c,Ny:True,Nea:True
Do you think this one will work:
http://de.futureelectronics.com/de/technologies/semiconductors/wireless-rf/rf-modules-solutions/proprietary/Seiten/9737883-MTCBA-G-EN-F4.aspx
And smsservertools can be configured to use such device over tcp/ip?
Could find examples here (maybe I missed them...)
Axel
|
Page: 1 2 Next
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
