Michael Boeding

Heres a quick calculation ## Example 1: Keep-Alive Time = 60 seconds (With TLS Overhead) ### Variables: - Payload Size per Message: 33 bytes - TLS Overhead: 40 bytes -...

Yes heres the log Im getting when it disconnects. Not sure if this is very useful ```c++ +UUMQTTC: 0,100 AT AT OK AT+UMQTTER +UMQTTER: 13,0 ```

Correct - very sure this isn't the broker. That and its AWS IoT Core so that max keep alive is 1200. Seems to be right around the 300 mark -...

Is there anyway to get more debug logs from it to see exactly what's going on? They definitely could be, I have 3 separate SIM cards im using right now...

Looks like from my logs. First attempt closed the mqtt connection after 2 minutes and 30 seconds Second attempt closed the mqtt connection after 2 minutes and 30 seconds So...

> > Is there anyway to get more debug logs from it to see exactly what's going on? > > The logging tools might need an NDA (and would certainly...

All of my SIMs are roaming SIMS btw.

I have been experimenting with some other stuff (I still need to test with your example). But while running on a non-secure self hosted mqtt broker I got this error...

I was finally able to get your example running and it looks like at 2 minutes and 30 seconds I run into a message that is ```bash +UUSOCL: 0 ```...

All great info and I'll look into some of this. AT&T seems to be a 1800 connection timeout for TCP. https://developer.att.com/technical-library/network-technologies/network-timers SuperSIM TCP seems to be fairly long also at...