> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/transportation/configuration/add-a-transportation-gateway-to-command/transportation-gateway-dual-sim-support.md).

# Transportation Gateway Dual-SIM Support

Learn how the Verkada KGX61 Ruggedized Transportation Gateway supports dual-SIM functionality

Each Verkada Transportation gateway has two SIM slots with an automatic failover mechanism.

## How dual SIM functionality works

By default, the KGX61-HW comes with 2 SIM slots:

* Slot 1 (Primary by default)
* Slot 2 (Secondary by default)

Every KGX61-HW comes with a Verkada data SIM inserted in **Slot 2**. This SIM card is used for the optional [Verkada data plan](/transportation/cellular-data-options/verkada-data-plan.md).

Customers bringing their own data plan can insert their SIM card into **Slot 1,** which will act as the primary SIM, while keeping the Verkada SIM in **Slot 2**. In the event that the customer-provided SIM fails, the KGX61-HW will fall back to the Verkada SIM, which helps ensure the gateway is always reachable.

Customers can also insert their own SIM cards in both slots and choose which one is the primary. Regardless of configuration, the KGX61-HW behaves according to the following state machine.

## SIM failover

The KGX61 has a state machine that constantly monitors the SIM activity on the LTE modem, as follows:

<div align="left" data-with-frame="true"><img src="https://3615485688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5H765ijhDtsUdXyNltrP%2Fuploads%2Fb9EPmwSJoh6NzKAHFAoN%2F74da46b9c514e7bc393eaf12ca7b97f87767eee7.png?alt=media&amp;token=53819812-a700-4685-82f3-bb06122e885b" alt=""></div>

{% stepper %}
{% step %}
**Start—The state machine is triggered when the device boots.**
{% endstep %}

{% step %}
**Primary (monitor)—The general-purpose input/output (GPIO) pin on the LTE modem detects when a SIM has been inserted into the primary slot.**

* The GC31 attempts to connect via the primary SIM and pings a backend server every few seconds.
* If a number of those pings fail consecutively, the state machine triggers the failover to the secondary.
  {% endstep %}

{% step %}
**Primary (fail)—Trigger occurs if the primary SIM fails to ping the server multiple times. The device fails over to the secondary SIM.**
{% endstep %}

{% step %}
**Auto retry — The device will automatically switch to the primary SIM 15 minutes after losing connection. If that fails, it will retry after 30 minutes, then again after 1 hour. It will continue retrying hourly for 24 hours, then once every 24 hours until it reconnects.**
{% endstep %}

{% step %}
**Manual retry — Once the secondary SIM is active, the user needs to manually switch back to the primary SIM if they wish to connect through the primary.**
{% endstep %}

{% step %}
**Secondary (fail)—Trigger occurs if a secondary SIM fails to ping the server multiple times. The state machine reverts back to the Start phase.**
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/transportation/configuration/add-a-transportation-gateway-to-command/transportation-gateway-dual-sim-support.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.