The OpenGTS protocol
OpenGTS is not a device either: it is an <strong>open-source tracking platform</strong>, the first one built for fleets, written in Java with a MySQL database. It ships its own format, OpenDMTP, which is why it shows up as a protocol.
The device reports to the OpenGTS server. If a customer arrives from there, <strong>the hardware does not need replacing</strong>: you change the address it reports to, as in any migration.
Build the configuration command
Receive this protocol on your own platform
No server to set up and nothing to program: the platform already reads this protocol. You add the brand and the domain.
See how becoming a distributor worksIMEI lookupDevice identification tool. We do not perform unlocking, carrier release or mobile blacklist checks, and we are not affiliated with the GSMA.
Where the data comes fromPublic mobile TAC database (MIT licence, Copyright (c) 2026 Moaz Ebrahem), TAC codes published by Teltonika on its official wiki, and the protocol observed on devices connected to the Appogio platform. We publish no full IMEI and no customer data.
Frequently asked questions
Is OpenGTS a device?
No. It is an open-source tracking platform, written in Java with a MySQL database. It ships its own format, OpenDMTP, which is why it appears in the protocol list.
If a customer comes from OpenGTS, do their devices have to be replaced?
No. You change the address they report to and the same units carry on. It is the cheapest migration there is.
Is running OpenGTS cheaper than paying for a platform?
The licence is free; running it is not. It needs Java, MySQL, a web server and someone to administer Linux, and the project has been dormant for years. Almost everyone who arrives from there is tired of administering their own server.