← Back to the map

Onboarding a GH5200

Pointing a Teltonika tracker at this server with the Teltonika Configurator, then pairing it with your phone so the rings and the alarm apply to it.

What you need

A Teltonika GH5200, charged.
A micro-SIM with a mobile data allowance, already activated. The tracker sends over mobile data, not Wi-Fi, so it needs its own connection.
A USB cable and a Windows PC running the Teltonika Configurator. The Configurator is Windows-only; the pairing at the end is done on your phone.
The APN for your SIM's network. Your provider publishes it — it is not something this server can tell you.

Connect the tracker

Insert the SIM, plug the tracker into the PC over USB and open the Configurator. It should find the device and load its current configuration. The left-hand menu is how you move between sections; everything below lives in GPRS apart from the last step.

Turn on mobile data

In GPRS › GPRS Settings:

GPRS Context	`Enable`
APN	whatever your SIM provider specifies
APN Username / Password	usually blank — only fill these if your provider gives them
Authentication	`Normal (PAP)` unless your provider asks for CHAP

Without this the tracker has no route to anything and will never appear, however correct the server settings are.

Point it at this server

In GPRS › Server Settings. These two values are read live from the server you are reading this page on, so they are always the right ones:

Domain …

Port …

Protocol	`TCP`
Encryption	`None`

Protocol must be TCP, and Encryption must be None. On UDP nothing arrives at all — the server only listens on TCP, so there is no error and no rejected connection, just a tracker that never shows up. And the AVL port is raw TCP with no TLS in front of it, so TLS/DTLS fails the handshake.

Enter the domain on its own, with no https:// and no trailing slash. The map is served over HTTPS on 443; the tracker talks a different protocol on a different port and knows nothing about either.

Second Server Settings can stay on Disable — there is no backup server to send to.

Check the records settings

Still under GPRS, in Records Settings:

ACK Type	`TCP/IP` — this server acknowledges each batch with the number of records it accepted, which is the standard TCP/IP acknowledgement
Sort By	`Newest` is a good default. It decides the order a backlog is flushed in after a period offline; the server takes the newest fix by device timestamp either way, so the pin never jumps backwards
Timeouts	the defaults are fine

Save to the device

Write the configuration to the tracker, then unplug it and let it find the network. The first connection can take a minute or two while it registers on the mobile network and gets a GNSS fix. Outdoors with a view of the sky is much faster than indoors.

Confirm it is reporting

Open the map. The tracker appears in the Devices list by its IMEI as soon as it completes the handshake and sends a position. A green dot means it is connected and recently heard from.

If it never appears, the server has not heard from it at all — see troubleshooting below.

Pair it with your phone

On the phone that will be carrying the alarm, open the map and:

Tap Share my location and allow the permission. The rings are drawn around you, so nothing can be judged until the phone is sharing.
Find the tracker in the Devices list and tap the ⊕ beside it. It moves up into Watching.
Tap the ✎ to give it a name. The name is what the alarm banner says, which beats reading fifteen digits in a hurry.
Adjust the three ring distances if the defaults do not suit. They apply to every device you are watching.

The pairing is remembered by that browser and re-sent automatically whenever it reconnects. Pairing from a different phone or browser is a separate pairing — there are no accounts here.

The alarm needs sound to be useful, so the first tap on Share my location is also what unlocks audio. Check your phone is not on silent.

If it does not appear

Working from the most common cause down:

Symptom	Usual cause
Never appears at all	Protocol set to `UDP`, or Encryption set to `TLS/DTLS`. Both fail silently. Check these first.
Never appears, protocol is right	No mobile data: wrong APN, SIM not activated, or no data allowance. Confirm the SIM works in a phone.
Appears, then goes grey	Patchy mobile coverage. The tracker reconnects on its own and backfills.
Paired but no rings	The phone is not sharing its location. The rings centre on you.
Zone flickers while nothing moves	Expected at short ring distances. A phone's own fix is routinely 5–15 m out, so at tight radii the zone is partly reporting GPS error rather than movement.