Titan – Tacacs+

/in /by

If an external Tacacs+ server is needed for the authentication of the HTTP and Telnet services, we need to configure in this section.

  • Server: Tacacs+ server IP address or DNS
  • Port: Tacacs+ tap port (default 49)
  • Key: encryption password
  • Service http: activate this box in case we want the access to the Titan router via HTTP to use the Tacacs+ authentication service
  • Service console: activate this box in case we want the access to the Titan router via Telnet (remote console) to use Tacacs+ authentication

ADDITIONAL NOTES

  • Once configured click on the “SAVE CONFIG” button to save changes. Restart the router so changes apply
  • Note the Titan router will allow us to use the username and password assigned to the user “admin” locally, so if the router does not have Internet connectivity (operator change, etc.) it can have a way to enter the router. Save the “admin” local password securely

Titan – MQTT

/in /by

Titan routers can work as basic MQTT broker or as MQTT client. Configuring the Titan router as MQTT client it can send the data gathered in the Logger (sensor data, modbus equipment, …) via MQTT. This section should be properly configured if we select send via MQTT in the Logger section.

Other: MQTT broker

  • Enabled:
  • Anonym user:
  • User:
  • Password:

Other: MQTT client:

  • Enabled: select to enable the MQTT client service
  • Username: leave blank if we are not using it
  • Password: leave blank if we are not using it
  • ID: device identification field
  • QoS: quality of service (0, 1, 2)
  • KeepAlive: in seconds (300 recommended)
  • Persistence: select in case we want data to be persistent
  • AT Topic: Titan router topic 1. AT commands sent to this topic will be executed in the router
  • AT Topic 2: Titan router topic 2. AT commands sent to this topic will be executed in the router
  • AT Topic 3: Titan router topic 3. AT commands sent to this topic will be executed in the router
  • AT Topic Rest: MQTT ansours to AT commands received by the Titan router will be sent to this topic also via MQTT

ADDITIONAL NOTES

  • Once configured click on the “SAVE CONFIG” button to save changes. Restart the router so changes apply
  • Note we can enter the text [IMEI] instead of the IMEI number. That is, if the IMEI is 012345678912345, we could either enter the topic /012345678912345/TEST or /[IMEI]/TEST

Titan – HTTPS

/in /by

Titan mini router allows we to enable HTTPS in the configuration environment if necessary.

  • Enabled: enables the HTTPs service (certificates are generated automatically after the restart

ADDITIONAL NOTES

  • Once the configuration is finished press the “SAVE CONFIG” button to save the changes. Remember to restart our router for the new changes to take effect.
  • When we try to connect to the Titan router via HTTPS our browser will probably show we a warning message regarding the self-signed digital certificate. It is completely normal.

Titan – Movement Detector

/in /by

The Titan mini routers contain a movement detection system that allows we to send SMS alarms, make telephone calls or change a relay upon detecting movement.

  • Accelerometer mode: this option activates the movement detection system with different sensitivity modes
  • SMS: this option activates the sending of SMS messages in the event of detected movement
  • Call: this option activates the telephone call option in the even of detected movement
  • Phone numbers: list of numbers (separated by semi-colon) to which SMS messages will be sent and phone calls will be made
  • Text SMS Alarm On: Text of the SMS alarm
  • Pause between alarms: this field indicates the time (in minutes) between alarms. For example, a value of 60 means that no alarms or calls will be made for an hour after the last message was sent or the last call was made.

ADDITIONAL NOTES

  • Once the configuration is complete, press the “SAVE CONFIG” button to save the changes. Remember that the router should be reset in order for the changes to take effect.