IMTMTS and IMTMTRING can have different msg ID's

[JimCircadian]

Applies to version 0.12 of modem hardware. This should be protected against, as it can result in unacknowledged messages on the inbound queue endlessly spinning.

+IMTMTRING: 244,7,22
OK
AT+UNS=0
OK
AT+IMTMTS
+IMTMTS: 244,2,20 
OK
AT+IMTRB=244
Another test messageZ
OK
AT+IMTA=2
+IMTA ERROR: 1
OK
AT+IMTMTS
+IMTMTS: 244,2,20 
OK
AT+IMTRB=244
Another test messageZ
OK
AT+IMTA=7
OK
AT+IMTMTS
OK

[JimCircadian]

12:32:04                 INFO             Command sent: "AT+IMTMTS"
OK'32:04                 DEBUG            Reply received: '+IMTMTS: 244,4,95 
OK"32:04                 INFO             Response received: "+IMTMTS: 244,4,95 
12:32:04                 INFO             Command sent: "AT+IMTRB=244"
12:32:04                 INFO             Response of 101 bytes received
12:32:04                 INFO             Received MT message, outputting to /data/pyremotenode/messages/4_01122025123204.msg
12:32:04                 INFO             Command sent: "AT+IMTA=4"
OK'32:05                 DEBUG            Reply received: '+IMTA ERROR: 1
OK"32:05                 INFO             Response received: "+IMTA ERROR: 1
12:32:05                 INFO             Acknowledged IMT message ID 4
12:32:05                 DEBUG            Closing and removing modem serial connection

This error is not handled in a resilient fashion, so this will be continuously reprocessed

[JimCircadian]

This section of code needs thinking about: should we default to acknowledging the head of the FIFO queue in this case? Perhaps that is also risky, but permanently spinning is worse.

                    response = self.modem_command("AT+IMTA={}".format(mt_msg_id))
                    if response.splitlines()[-1] == "OK":
                        logging.info("Acknowledged IMT message ID {}".format(mt_msg_id))
                    ... check here the else condition, if mismatched ID, why? ...