Suchen Sie etwas anderes?
The MTX-Router-Titan II, MTX-Router-Titan and MTX-Router-Titan mini devices can be configured to detect possible cases of jamming and take the appropriate action. That is, the Titan devices are capable of detecting suspect interference caused by possible GSM/GPRS inhibitors. This can be useful for some security applications. This option is not available for 4G models.
If jamming is detected, the routers can do three things: change a relay for a specific period of time that can be configured (for example to connect a light/sound signal), make a GSM call or send an SMS alert.
Remember that sending an SMS or making a GSM call is not always going to be possible given that it depends on the intensity of the jamming. If the jamming signal intensity is low (either because the intruder is getting closer or nearer), an SMS can be sent. If there is an intense level of jamming, the sending of an SMS will be impossible.
- Detection mode:
“Disabled” if we do not want to use this option
“Enabled for GPRS” if we want to activate jamming detection for GSM/GPRS networks - Sensibility: select between low, medium or high sensitivity. Better detection is achieved with high sensitivity, although some false positives could occur
- SMS: select this option if we want to send an SMS alart when a change is detected
- Call: select this option if we want to make a call as an alarm when a change is detected
- Phone numbers: we can enter up to 5 telephone numbers to make calls or send SMS alarms
- Text SMS Alarm On: if we choose to send SMS alarms, the text inputted here will be sent when the alarm is activated
- Text SMS Alarm Off: if we choose to send SMS alarms, the text inputted here will be send when the alarm is deactivated
- Logger: activate this option if we want the data to be stored in the device’s internal Logger to send it to the web platform or FTP server
ADDITIONAL NOTES
- Once the configuration is finished, click “SAVE CONFIG” to save the changes. Remember that the router should be restarted for the changes to take effect.
- Sample format of the JSON string sent when the Logger option is chosen:
{“IMEI”:”354740050367237”,”TS”:”17/02/2014 19:02:46”,”TYPE”:”JAMM”, “P”:”1234”,”VAL”:1}
Where:
- IMEI: the router’s ID number. Unique for each device
- TS: time stamp DD:MM:YYYY HH:MM:SS
- TYPE: data type. In this case digital input
- P: logger ID field (External Devices > Logger configuration)
- VAL: 1: activated/0: deactivated
Enter the “ethernet” or “modem” connection type:
For an ethernet configuration, make sure the IP parameters are compatible with server access according to the concentrator local network configuration. For an ethernet connection, the configuration must be compatible with the concentrator’s local network topology so that it can access the servers. This configuration is done from the “Networks” configuration page (see section 3.2.2.3: “Networks”).
For a modem connection, the modem configuration must be correct before a connection can be set up. This configuration is done from the “Modem” configuration page (see section 3.2.2.4: “Modem”).
The parameters for the servers to be configured are at least the following:
Therefore the following fields need to be configured: “Interface”, “Type”, “Server type”, “Address”, “Port”, “Login” and “Password”.
The other fields can be left at the default values subject to the directories having been properly created beforehand. See section 3.1.2: “Configuration files” for more details.
Wait. The concentrator will reboot using its factory configuration.
