Specific cellular tower connectivity issue

Hello,

I have a very specific issue. It only occurs when I am connected to a particular cellular tower in my area. This issue does NOT occur when connected to other cellular towers in my area.

I tried to contact Particle support, but their support page for connectivity issues just shows me the status website so I guess this should be posted here.

If I publish a variable, say a counter that counts every 1 second.
If I then turn on my Boron, it connects to the cellular network and picks a tower.
If I continuously read that counter variable every few seconds, all is good.

If I stop reading that counter variable for about 20 seconds and then start again, I am no longer able to read it via the Particle console or an API call.
If the Boron then publishes a value, that will be successful, and then I am able to read that counter variable again.
If I stop reading the counter variable again for about 20 seconds and then start again, I am no longer able to read it via the Particle console or an API call.

This is the cellular tower in question:

{
"device": {
"network": {
"cellular": {
"radio_access_technology": "LTE",
"operator": "Rogers AT&T Wireless",
"cell_global_identity": {
"mobile_country_code": 302,
"mobile_network_code": "720",
"location_area_code": 23015,
"cell_id": 17115002
}
},
"signal": {
"at": "LTE Cat-M1",
"strength": 72.5,
"strength_units": "%",
"strengthv": -86,
"strengthv_units": "dBm",
"strengthv_type": "RSRP",
"quality": 75,
"quality_units": "%",
"qualityv": -8.5,
"qualityv_units": "dB",
"qualityv_type": "RSRQ"
},
"connection": {
"status": "connected",
"error": 0,
"disconnects": 0,
"attempts": 1,
"disconnect_reason": "unknown"
}
},
"cloud": {
"connection": {
"status": "connected",
"error": 0,
"attempts": 1,
"disconnects": 0,
"disconnect_reason": "none"
},
"coap": {
"transmit": 164,
"retransmit": 1,
"unack": 0,
"round_trip": 310
},
"publish": {
"rate_limited": 0
}
},
"power": {
"battery": {
"charge": 92.31,
"state": "charged"
},
"source": "USB host"
},
"system": {
"uptime": 833,
"memory": {
"used": 107272,
"total": 142928
}
}
},
"service": {
"device": {
"status": "ok"
},
"cloud": {
"uptime": 808,
"publish": {
"sent": 15
}
},
"coap": {
"round_trip": 624
}
}
}

After these logging messages occur following a .publish() call, I am able to read the counter variable until I stop doing so for about 20 seconds.

0000087918 [comm.coap] TRACE: Sending CoAP message
0000087919 [comm.coap] TRACE: CON POST /e/cb_event size=376 token= id=29
0000088291 [comm.coap] TRACE: Received CoAP message
0000088292 [comm.coap] TRACE: ACK 0.00 size=4 token= id=29

Seems like a problem worth escalating with the network provider but I need some extra information to be sure. I sent you a DM.

Thanks.

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.