All posts
AIS-140IndiaTraccarFleet

AIS-140 and Traccar: run your own fleet platform on the same device

Nov 18, 20265 min read

If you run buses, taxis or national permit trucks in India, you already know about AIS-140. Vehicles in these categories must carry a certified vehicle location tracking device (VLTD) with an emergency button, and that device reports to your state's transport backend.

What many fleet owners don't realise is that the same device can also feed your own tracking platform. The government server is there for compliance and emergency response. Your platform is where you actually manage the fleet: live tracking, trip reports, idling, overspeed, geofences, customer access.

This post explains how that works with Traccar.

What AIS-140 asks for

In short, an AIS-140 device:

  • Is type approved by a testing agency such as ARAI or ICAT
  • Has one or more emergency (panic) buttons
  • Sends position and alert data to the state backend set up by the transport department
  • Is registered against the vehicle by the device supplier

Which vehicles need it, and from when, is enforced by each state. Public service vehicles and national permit goods vehicles are the main categories. Always check the current rules with your state transport department.

The important point: certification belongs to the device. Traccar, or any other fleet software, does not replace the certified device or the state registration. It runs alongside them.

One device, two servers

Most AIS-140 devices support more than one server address. Suppliers call it different things: secondary IP, IP2, backup server, or "private server". The idea is the same:

Server Who uses it What for
Primary (state backend) Transport department, police Compliance, emergency response
Secondary (your Traccar) You and your customers Fleet management, reports, alerts

The device keeps sending to the state backend exactly as before, and sends a copy to your server.

Ask your device supplier how to set the secondary server on your model. On some devices it's an SMS command, on others a setting in the supplier's configuration tool. Don't change the primary server: that's the compliance link.

Which protocol and port

Traccar listens on a separate port for each device protocol. For AIS-140 devices commonly used in India:

Device Traccar protocol Port
Devices using the AIS-140 standard message format its 5179
TranSync AIS 140 transync 5247
iTriangle devices aquila 5089
Atlanta Systems devices l100 5112

You can check any model on our supported GPS devices list, which covers more than 2,000 trackers.

On your server, open the port in the firewall, for example:

sudo ufw allow 5179/tcp

Then point the device's secondary server at your domain or IP and that port.

Add the device in Traccar

  1. In Traccar, add a new device.
  2. Enter the device identifier. For most AIS-140 devices this is the IMEI.
  3. If positions don't appear, check the Traccar log:
tail -f /opt/traccar/logs/tracker-server.log

A line saying Unknown device followed by a number means data is arriving, but the identifier in Traccar doesn't match. Copy that number into the device settings in Traccar.

No line at all means the data isn't reaching your server: check the secondary server address, the port and the firewall.

Panic button alerts in your control room

When someone presses the emergency button, the device sends an alert to the state backend. If the device also reports to your Traccar server, that alert arrives as an SOS alarm too.

In Traccar, create a notification:

  • Type: Alarm
  • Alarms: SOS
  • Channels: web, push notification to your mobile app, email or SMS

Now your own control room sees the alert, with the vehicle's position, at the same moment. For school buses and staff transport, that matters.

What you get on your own platform

With the data flowing into Traccar, you can:

  • See live positions of every bus, truck and taxi
  • Run trip, stop and summary reports for any day or month
  • Get alerts for overspeed, idling, geofence entry and exit (depots, warehouses, schools)
  • Give customers or schools their own logins that show only their vehicles
  • Add branded Android and iOS apps for drivers, managers and parents

And if you're a GPS dealer, you can run this as your own business: the same platform serves many transport operators, each with their own logins.

Common questions

Can I use the same Traccar server for non-AIS-140 vehicles? Yes. Private cars, company vans and bikes can use any supported tracker, such as Concox, Teltonika or Coban, on the same platform.

Will adding a secondary server affect compliance? It shouldn't, as long as the primary server stays untouched. Confirm with your device supplier that your model supports a secondary server without changing the government link.

Does Traccar show the emergency button state? Yes, as an SOS alarm on the position, which you can turn into notifications and reports.

Summary

  1. Keep the AIS-140 device's primary server pointed at the state backend.
  2. Set the secondary server to your Traccar domain and the right port.
  3. Add the device by IMEI and check the log if it doesn't appear.
  4. Create SOS alarm notifications for your control room.

Want this set up for your fleet or your customers? See the AIS-140 GPS tracking platform service, or start with the $249 white-label Traccar platform.

Keep reading

Need help with your Traccar server?

I offer Traccar setup and maintenance, GPS tracking apps and Flutter development.