| Keywords: Mode: All keywords (AND) |
|
Fri Feb 11, 2011 11:47
|
mattym: The other has the same problem, but only every couple of days/weeks... so it's not so bad. I like that solution better keke. Thanks!
|
|
Fri Feb 11, 2011 09:58
|
mattym: I have to issue a AT+CFUN=1 to it, the modem then takes around 10s to reset and start network registration again.
Unfortunately it's the network reception which is a bit dodgy not the modem :-( I have one with a different aerial that is behaving much better. So i'll probably get another aerial for this one. :-D
|
|
Thu Feb 10, 2011 22:19
|
mattym: Would smstools still have the modem open though when I parse the stats file for trouble and then do something?
A modem that automatically gets registration again after two minutes would be good! :D
I'll see about parsing the stats file just in case you change the behaviour in the next version :D
Thanks for the help Keke
Matt
|
|
Thu Feb 10, 2011 14:20
|
mattym: Yes I looked at status monitor, I could use that, just means I have to have a cron job or something to parse it, which is fine, just another piece of glue :-).
I like the idea of the heartbeat just sending network registration OK/NOT OK. For me this would cover my corner cases for monitoring.
heartbeat to say network is registered, modem OK
alarmhandler to notify when things are broke then fixed
eventhandler to notify when SMS sent/failed etc.
I've noticed smstools seems to halt when executing the alarmhandler script. So for now i'm using that to reset the modem then sleep for 60s. Seems to work as smstools logging starts again after 60 seconds :-)
|
|
Thu Feb 10, 2011 13:42
|
mattym: Ah, that explains it. I couldn't see that from reading the docs. I presumed smstools always halts to run regular_run at the specified interval.
I was using regular_run to reset a modem if creg? returns 0,2. This is because a modem I have only tries for two minutes to gain network registration. After this period it just sits there! :-S
So I used regular_run to check creg? and then issue a reset if network registration was lost.
I could use the alarmhandler, but I believe this will clash with smsdtools trying to access the modem. I could do with either smstools issuing the reset for me, but only on loss of network registration. Or a way to get sole access to the modem from a script.
|
|
Thu Feb 10, 2011 13:35
|
mattym: I was thinking of:
heartbeat_sec = 60
heatbeat_script = /etc/script.sh
Using the script I can ping a monitoring app or similar to say everything is okay. I prefer this approach then just using the alarmhandler where it's either broke then fixed (with your patch).
I understand the eventhandler to be used for events (sending SMS etc.)
Alarmhandler to be used for when something goes wrong, and with your patch could also be used to say when something is fixed. But a continual message to say everything is okay would be cool.
Thanks,
Matt
|
|
Thu Feb 10, 2011 13:09
|
mattym: Operating system name and version: CentOS 5.5
Version of smsd: 3.1.14
Smsd installed from: sources
Name and model of a modem / phone: Wavecom Fast GO Plus
Interface: serial
I seem to see a problem where my regular_run script is not running when registration is lost and I get a lot of:
2011-02-10 11:59:44,5, WAVECOM: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 99. TIME
2011-02-10 11:59:46,5, WAVECOM: Signal Strength Indicator: not present of not measurable, Bit Error Rate: not known or not detectable
I expect these lines to pause when regular_run runs because regular run takes ownership of the modem?
Thanks,
Matt
|
|
Thu Feb 10, 2011 13:05
|
mattym: Very cool. It would be great if this was a regular heartbeat, so say ever 1 or 2 minutes I could set this to run an eventhandler script or similar.
|
|
Thu Feb 10, 2011 13:03
|
|
|
|
Thu Feb 10, 2011 11:44
|
mattym: Operating system name and version: CentOS 5.5
Version of smsd: 3.1.14
Smsd installed from: sources
Name and model of a modem: Wavecom Fast GO Plus
Interface: serial
Hi!
Sometimes when the modem loses network I get this in the logs:
2011-02-10 11:42:20,5, WAVECOM: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 64. TIME
2011-02-10 11:42:22,5, WAVECOM: Signal Strength Indicator: not present of not measurable, Bit Error Rate: not known or not detectable
How can I control the WAITING 1 SEC time? I've tried errorsleeptime and delaytime but neither seem to work. I'd like to increase it to say 10s.
Thanks,
Matt
|
|
Thu Jan 27, 2011 15:28
|
mattym: Operating system name and version: CentOS 5.5
Version of smsd: 3.1.14
Smsd installed from: sources
Name and model of a modem / phone: Wavecom Fastrack Go Plus
Interface: serial
Hi,
Using the eventhandler i've got smstools to notify my monitoring application when a message is sent,received, or failed.
Using the alarmhandler i've got smstools to notify my monitoring application when there is a problem with the modem, such as it can't connect or it loses network registration.
I'm not always receiving or sending messages, so I could do with a way for smstools to notify my monitoring application when network registration is restored and currently active on an interval basis.
I really don't want to parse the logfiles, so currently I think I can do this by using regular_run and connect to the modem my self to run +CREG? but it would be cool if smstools would generate an event or alarm handle on reconnection/network registration.
Thanks,
Matt
|
|
Wed Aug 18, 2010 13:48
|
mattym: Thanks for the quick reply. I'll remember that the next time when testing with Ubuntu.
|
|
Wed Aug 18, 2010 13:28
|
mattym: As an update i've just got this modem working under CentOS 5.5 x86_64 with smsd tools Smsd v3.0.10 from epel repo.
|
|
Wed Aug 18, 2010 13:15
|
mattym: Operating system name and version: Ubuntu 10.4 64
Version of smsd: 3.1.6
Smsd installed from: package repository
Name and model of a modem / phone: Wavecom Fastrack Go
Interface: serial
GSM modem works fine in minicom with hardware flow control on, 115200,8N1, /dev/ttyS0 - I can send sms messages okay with minicom.
/etc/smsd.conf
[WAVECOM]
device = /dev/ttyS0
incoming = no
mode = new
rtscts = yes
baudrate = 115200
read_timeout = 5
When starting smsd I get the following in the log file.
2010-08-18 14:08:37,5, WAVECOM: Modem handler 0 has started. PID: 19356. Will only send messages.
2010-08-18 14:08:37,5, WAVECOM: Using check_memory_method 1: CPMS is used.
2010-08-18 14:08:37,6, WAVECOM: Checking if modem is ready
2010-08-18 14:08:37,7, WAVECOM: -> AT
2010-08-18 14:08:37,7, WAVECOM: Command is sent, waiting for the answer
2010-08-18 14:08:37,7, WAVECOM: <- O
*2010-08-18 14:08:37,7, WAVECOM: ->
2010-08-18 14:08:38,7, WAVECOM: Command is sent, waiting for the answer
2010-08-18 14:08:43,7, WAVECOM: put_command expected (OK)|(ERROR), timeout occurred. 1.
* looks like this line it is sending some garbage it's a little square character.
Any ideas?
Thanks,
Matt
|
