Teltonika

How the Edge Controller integrates with Teltonika Routers

Overview

This page focuses on specic configuration and wiring for Teltonika routers.

Please see the Giraffe Cloud page for how the router integrates with the platform.

Remote shutdown

The open collector output on the router's 4 pin connector is normally connected to the Edge Controller. The router can then be used to remotely switch the entire Edge Controller off, leaving just the router running.

GPS

The Edge Controller can obtain it's GPS position from the Teltonika router.

Auto Reboot

We recommend setting up an auto reboot of the router if a ping to 8.8.8.8 and 8.8.4.4 persistently fail.

SMS Commands

We highly recommend configuring SMS commands to control the router. This will allow you to reconfigure the router even if the internet connectivity is not working.

Firmware version

The Edge Controller can support V7 Teltonika firmware by using the HTTP API.

Technically it should work with any router running firmware 00.07.06 or later but the older versions of firmware are very buggy. We recommend running the latest supported firmware. No support can be offered for older versions of Teltonika firmware.

We previously supported both v6 (Teltonika legacy UI) UBUS API and v7 (00.07.x new UI) UBUS API. However, V7 is now deprecated in favour of the new Teltonika HTTP API and V6 has been entirely removed from Edge Controller firmware v3.8 and later.

  • If you have a router attached to a system in Giraffe Cloud, the HTTP API will be used by default.

  • If you do not have a router linked to a system, but a router is defined in the Edge Controller definition, the V7 UBUS API will be used by default.

You. can override the above by defining the version in the config.json (please talk with Giraffe Support):

// config.json
"teltonika_version": 7 | "http"

You used to be able to define 6 to make it work with legacy Teltonika UI. However, this ability has been removed in firmware 3.8 onwards.

Firmware 00.07.0 / 00.07.1

If you have a router running 00.07.0.x / 00.07.1.x firmware, we highly recommend upgrading them because they were awful.

However, if you want the Edge Controller to be able to connect to them, you need to SSH into the router and edit the /etc/config/rpcd file.

In the file (vi is available), you need to find the following lines and put a # at the beginning of them.

list read '!superuser'
list write '!superuser'

When you have finished, it will look something like this:

config rpcd
        option socket '/var/run/ubus/ubus.sock'
        option timeout '200'

config login
        option username 'admin'
        option password '$p$root'
        option group 'root'
#       list read '!superuser'
        list read '*'
#       list write '!superuser'
        list write '*'

config superuser
        option username 'admin'
        option password '$p$root'
        list read '*'
        list write '*'

config group 'root'
        option target_write 'allow'
        option target_read 'allow'
        list write '*'
        list read '*'

config group 'admin'
        option target_write 'allow'
        option target_read 'deny'
        list write '*'
        list read 'system/multiusers/users_configuration'
        list read 'system/backup'
        list read 'system/flashops'
        list read 'system/cli'
        list read 'system/wizard'
        list read 'system/uscripts'

config group 'user'
        option target_write 'allow'
        option target_read 'deny'
        list write 'system/multiusers/change_password'
        list read 'system/multiusers/users_configuration'
        list read 'system/flashops'
        list read 'system/backup'
        list read 'system/admin/access_control'
        list read 'system/cli'
        list read 'system/uscripts'
        list read 'services/packages'
        list read 'network'
        list read 'system/wizard'
        list read 'services/mobile_utilities/sms/send'

...

Last updated