# How to Troubleshoot No Cellular Events Scenario?

A common issue in IoT deployments is when a device fails to attach to the cellular network. A cellular device must first complete signaling registration to connect to the network before establishing a data session for communication.&#x20;

Monogoto Hub and Advanced Console can assist diagnosing whether a device is attempting to connect and where it may be failing.

## Step 1: Check for signaling events in the Monogoto hub

The Monogoto Hub captures all network signaling events, which can be viewed on the Things page for each SIM.

1. Navigate to your SIM in the Things section.
2. Open the Events tab.
3. If no recent events are listed (e.g., no HSS\_ULR, HSS\_ULA, CREATE\_SESSION, etc.), this strongly indicates that the device is not attempting to attach to the network.

{% hint style="info" %}
You may see events such as MODIFY\_SUBSCRIBER and MODIFY\_SUBSCRIBER\_RESULT—these are provisioning-related and not part of the device's network signaling. You can ignore these for connectivity troubleshooting.
{% endhint %}

<figure><img src="/files/RdOlSuoqLBxYFqLs0hLR" alt=""><figcaption></figcaption></figure>

## Step 2: Download a signaling PCAP from the advanced console

For more detailed troubleshooting, use the Advanced Console to download a signaling PCAP (packet capture) for the SIM in question.

1. Go to the advanced console.
2. Select the subscriber or device ID.
3. Define a timeframe when the device was expected to be online.
4. Click to download signaling PCAP. &#x20;

{% hint style="info" %}
&#x20;A timeframe is required before the signaling PCAP will be available.
{% endhint %}

<figure><img src="/files/Wq6PZCILt09PI7o8S5eV" alt=""><figcaption></figcaption></figure>

5. If the SIM has signaling events a PCAP will download automatically. When you open you will see information similar to the below picture:

<figure><img src="/files/C7pgOeOQDwBSeakZIDi4" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If you see the message “Failed to download PCAP file: Signaling events not found” that means the device hasn’t attempted to attach during the timeframe.
{% endhint %}

<figure><img src="/files/VH96poSfuup0qwBwcQkT" alt=""><figcaption></figcaption></figure>

### What it means if there are no events?

If no signaling events appear in the Monogoto Hub and no signaling packets are captured from the Advanced Console, then:

* The device is likely not in coverage or powered off
* There may be a configuration issue (e.g., modem not initialized, incorrect network settings).

## Step 3: Isolate the problem

To rule out issues with the SIM or network availability:

1. Insert the Monogoto SIM into an unlocked smartphone.
2. Observe whether the phone shows network bars and connects (even if roaming).
3. If the SIM works in the phone, then coverage is available, and the SIM is functioning. In that case, the issue likely lies in the device configuration or modem behavior.
4. If the SIM does not work in the phone, contact Monogoto support to verify the SIM status and provisioning.

### Recommended AT commands to run when no signaling is seen

| AT Command  | Purpose                                            | Example Response                           | What It Tells You?                                                                                    |
| ----------- | -------------------------------------------------- | ------------------------------------------ | ----------------------------------------------------------------------------------------------------- |
| AT+CPIN?    | Checks if the SIM is inserted and ready.           | +CPIN: READY                               | If response is SIM PIN, SIM PUK, or SIM NOT INSERTED, the SIM is not usable yet.                      |
| AT+CSQ      | Checks signal strength.                            | +CSQ: 15,99                                | The first number (0–31) is signal strength; ≥10 is typically required. A value of 99 means no signal. |
| AT+COPS?    | Checks current operator/network registration.      | +COPS: 0,0,"Operator",9                    | If the device is not registered, it will return an empty string or indicate deregistration.           |
| AT+CREG?    | Checks network registration status on 2G/3G.       | +CREG: 0,5                                 | A value of  5 means registered; 0 means not registered; 2 means searching.                            |
| AT+CGREG?   | Checks GPRS (packet data) registration.            | +CGREG: 0,1                                | Same codes as CREG;  5 is registered for data.                                                        |
| AT+CEREG?   | Checks LTE network registration.                   | +CEREG:  0,5                               | Required for LTE Cat-M/NB-IoT; 1 = home network, 5 = roaming.                                         |
| AT+CGDCONT? | Lists current PDP context settings (includes APN). | +CGDCONT: 1,"IP","data.mono","0.0.0.0",0,0 | Verifies if the correct APN is set.                                                                   |
| AT+CFUN?    | Checks modem functionality mode.                   | +CFUN: 1                                   | 1 = full functionality; 0 = minimum (radio off); 4 = airplane mode.                                   |

If you have questions or need further assistance, don’t hesitate to reach out to the Monogoto support team. We’re here to help you troubleshoot, optimize your setup, and ensure your IoT deployment runs smoothly. We're always happy to assist!<br>


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://docs.monogoto.io/faq/how-to-troubleshoot-no-cellular-events-scenario.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
