@Pat, thanks for the logs. I see something similar as in jibel's: registration is suddenly dropped and then re-established after a few seconds. Sequence is (1: registered, 0: non-registered, 2: searching):
08-25 21:31:13.108 2160 2169 D AT : AT< +CREG: 1,"1B48","07EF7DA3",6,0,0
08-25 21:34:34.482 2160 2169 D AT : AT< +CREG: 0,"FFFF","0FFFFFFF",0,0,0
08-25 21:34:34.489 2160 2169 D AT : AT< +CREG: 2,"FFFF","0FFFFFFF",0,0,0
08-25 21:34:53.145 2160 2169 D AT : AT< +CREG: 1,"1779","00007DA3",3,0,0
08-25 21:35:06.616 2160 2169 D AT : AT< +CREG: 1,"1B48","07EF7DA3",6,0,0
I checked that there are no suspicious AT commands triggered from our side, so this looks like a modem firmware bug. There is a small chance that we need to set some configuration to avoid this though.
@Pat, thanks for the logs. I see something similar as in jibel's: registration is suddenly dropped and then re-established after a few seconds. Sequence is (1: registered, 0: non-registered, 2: searching):
08-25 21:31:13.108 2160 2169 D AT : AT< +CREG: 1,"1B48" ,"07EF7DA3" ,6,0,0 ,"0FFFFFFF" ,0,0,0 ,"0FFFFFFF" ,0,0,0 ,"00007DA3" ,3,0,0 ,"07EF7DA3" ,6,0,0
08-25 21:34:34.482 2160 2169 D AT : AT< +CREG: 0,"FFFF"
08-25 21:34:34.489 2160 2169 D AT : AT< +CREG: 2,"FFFF"
08-25 21:34:53.145 2160 2169 D AT : AT< +CREG: 1,"1779"
08-25 21:35:06.616 2160 2169 D AT : AT< +CREG: 1,"1B48"
I checked that there are no suspicious AT commands triggered from our side, so this looks like a modem firmware bug. There is a small chance that we need to set some configuration to avoid this though.