Navigation
Records in this category
- Which database is used internally by the system?
- Which web server is used internally by the system?
- Where are custom scripts stored?
- Which programming languages are supported?
- Is it possible to have root access on the server?
- How can vmware ESX Server be monitored?
- I need to change the outgoing mail server on the monitor system, where do I change that?
- How do I add new templates to op5 Monitor performance graphs?
- How do I setup op5 Monitor in a distributed monitoring environment?
- How do I integrate Nilex into op5 Monitor?
- How do I implement network monitoring in a good way with op5 Monitor?
- How do I integrate op5 LogServer with op5 monitor?
- Is it possible to have a sound alarm from monitor in to my browser when alerts occurs?
- How do I monitor things like raid controlers, physical memory, fans and other hardware of my op5 server?
- I like to write my own plugin, how is this supposed to be done?
- How do I use op5 Monitor to monitor Citrix?
- How do I setup commands and services for the door sensors?
- How do I perform https checks against websites using NTLM-authentication?
- Are there any op5 Monitor apps for Android or iPhone?
- How do I use op5 Monitor REST API?
- How do I troubleshoot the GSM Modem / GSM Gateway / GSM Terminal?
Tags
Monitor
How do I troubleshoot the GSM Modem / GSM Gateway / GSM Terminal?
Prerequisites
Use 2G / GSM instead of 3G. The 3G network is less reliable and isn't currently supported by op5.
Recommendations
Connect the modem directly to the op5 Monitor server instead of using a Ethernet over Serial solution. This will guarantee that notifications can be sent even if the local network goes down.
Troubleshooting Steps
- Try send a SMS to yourself:
sendsms 46733333333 'Test'
It usually takes a couple of minutes to reach your mobile.
Note that, if you send the SMS in another country than Sweden, change the 46 prefix. - Check that the SMS daemon is running:
service smsd status
You should get the following with one or two random PID numbers at the end:
smsd is running with pid: 2550 2544. - Use a mobile phone to check the signal strength. Make sure you are using 2G / GSM instead of 3G. Preferably use a simple 2G mobile phone instead of 3G enabled phone to make sure you are not using 3G.
- Check how often the modem is blinking. It should blink once every third seconds. Please read the "Overview of LED Operating Status" below for details.
- Check the SMS daemon log error messages by running this:
grep -i "error" /var/log/smsd.log
If you find an error line like this:
2011-12-08 13:42:56,3, GSM1: Error: Modem is not registered to the network
This could be three different problems:
The GSM signal is too weak.
The SIM card is missing.
The PIN code is incorrect or isn't configured.
Overview of LED Operating Status
| Operating Status | The Green LED is |
| Power down | Off |
| Not registered to the GSM net (missing SIM card, and/or incorrect PIN code, and/or too weak GSM signal) | Blinking once every second |
| Standby (registered to the GSM net) | Blinking fast every third seconds |
| Sleep mode (power save mode and registered to the GSM net) | Off |
| Talk mode | On |
Tags: -
Related entries:
- What support is there for monitoring Secure Gateway?
- Which are the hardware specifications for op5 Appliance servers?
- Can I connect the SMS modem to a USB port?
- HowTo test SMS-Modem using minicom.
Last update: 2012-04-20 08:20
Author: Support Team
Revision: 1.10
You cannot comment on this entry


