Chateau 5g r17 ax lte attach problem

sasan_kn · May 14, 2026, 7:54am

Hi,

I am having an LTE attach problem on a MikroTik Chateau device with Quectel RG650E-EU modem.

The modem can detect and monitor LTE cells normally, signal quality is good, but it never attaches to the network.

Tested RouterOS versions:

7.19.6
7.22.3
7.23rc

Same issue on both versions.

I also changed LTE mode from QMI to MBIM, but there was no difference.

Current symptoms:

AT+CGREG? returns 0,0
AT+CREG? returns 2,0
AT+CGATT? returns 0
AT+CEER returns No cause information available
Manual attach also fails

The modem sees nearby LTE cells correctly:

/interface lte at-chat lte1 input="AT+QENG=\"servingcell\""

Example:

+QENG: "servingcell","LIMSRV","LTE","FDD",432,11,166E13F,101,1329,3,4,4,A0FD,-93,-13,-60,13,0,-,30

Neighbour cells are also visible normally.

APN configuration:

IPV4V6
APN: ipstaticb2c.mci

I also checked:

SIM is detected (CPIN: READY)
Signal is stable
LTE bands are visible
Reboot and modem reset performed
AT+CFUN=1,1 tested
usbnet mode changed/tested
MBIM and QMI both tested

Has anyone seen a similar issue with RG650E-EU or attach failures on recent RouterOS versions?

Any suggestions for deeper MME reject debugging or modem firmware recovery would be appreciated.

[admin@Chateau] > /interface lte at-chat lte1 input="AT+QENG="servingcell""
output: +QENG: "servingcell","LIMSRV","LTE","FDD",432,11,166E13F,101,1329,3,4,4,A0FD,-93,-13,-60,13,0,-,30
OK

[admin@Chateau] > /interface lte at-chat lte1 input="AT+QENG="neighbourcell""
output: +QENG: "neighbourcell intra","LTE",1329,101,-11,-92,-62,-,31,255,40,0,52
+QENG: "neighbourcell intra","LTE",1329,94,-17,-100,-70,-,23,255,40,0,52
+QENG: "neighbourcell intra","LTE",1329,264,-12,-99,-77,-,24,255,40,0,52
+QENG: "neighbourcell intra","LTE",1329,218,-18,-101,-74,-,22,255,40,0,52
+QENG: "neighbourcell intra","LTE",1329,216,-20,-106,-74,-,17,255,40,0,52
+QENG: "neighbourcell intra","LTE",1329,265,-18,-105,-77,-,18,255,40,0,52
+QENG: "neighbourcell inter","LTE",39550,-,-,-,-,-,31,6,10,10
+QENG: "neighbourcell inter","LTE",3300,101,-8,-93,-77,-,23,255,10,10
+QENG: "neighbourcell inter","LTE",3300,264,-17,-102,-77,-,23,255,10,10
+QENG: "neighbourcell inter","LTE",3300,63,-16,-103,-77,-,23,255,10,10
+QENG: "neighbourcell inter","LTE",1500,101,-9,-97,-79,-,24,255,10,10
+QENG: "neighbourcell inter","LTE",1500,264,-15,-100,-77,-,24,255,10,10
+QENG: "neighbourcell inter","LTE",1500,99,-20,-107,-79,-,24,255,10,10
+QENG: "neighbourcell inter","LTE",1500,94,-16,-103,-79,-,24,255,10,10
+QENG: "neighbourcell inter","LTE",1500,400,-14,-102,-79,-,24,255,10,10
+QENG: "neighbourcell inter","LTE",425,101,-10,-92,-73,-,22,255,10,10
+QENG: "neighbourcell inter","LTE",425,218,-20,-101,-68,-,22,255,10,10
+QENG: "neighbourcell inter","LTE",425,63,-20,-102,-73,-,22,255,10,10
+QENG: "neighbourcell inter","LTE",425,488,-20,-94,-64,-,22,255,10,10
+QENG: "neighbourcell inter","LTE",425,264,-20,-112,-80,-,22,255,10,10
+QENG: "neighbourcell inter","LTE",425,36,-20,-94,-63,-,22,255,10,10
+QENG: "neighbourcell inter","LTE",3102,101,-12,-98,-77,-,17,255,10,10
+QENG: "neighbourcell inter","LTE",3102,63,-17,-103,-77,-,17,255,10,10
+QENG: "neighbourcell inter","LTE",3102,264,-17,-105,-80,-,17,255,10,10
+QENG: "neighbourcell inter","LTE",38950,63,-14,-108,-86,-,18,255,10,10
+QENG: "neighbourcell inter","LTE",38950,95,-18,-112,-86,-,18,255,10,10
+QENG: "neighbourcell inter","LTE",38752,63,-14,-110,-85,-,0,255,10,10
+QENG: "neighbourcell inter","LTE",38752,95,-13,-109,-85,-,0,255,10,10
OK

[admin@Chateau] > /interface lte at-chat lte1 input="AT+CGREG?"
output: +CGREG: 0,0
OK

[admin@Chateau] > /interface lte at-chat lte1 input="AT+CREG?"
output: +CREG: 2,0
OK

[admin@Chateau] > /interface lte at-chat lte1 input="AT+CGATT?"
output: +CGATT: 0
OK

[admin@Chateau] > /interface lte at-chat lte1 input="AT+CGDCONT?"
output: +CGDCONT: 1,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0,,,,,,,,,,"",,,,0
+CGDCONT: 2,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0,,,,,,,,,,"",,,,0
+CGDCONT: 3,"IPV4V6","sos","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1,,,,,,,,,,"",,,,0
+CGDCONT: 4,"IPV4V6","ipstaticb2c.mci","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0,,,,,,,,,,"",,,,0
+CGDCONT: 5,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0,,,,,,,,,,"",,,,0
OK

[admin@Chateau] > /interface lte at-chat lte1 input="AT+QCFG=?"
output: +QCFG: "rrc",(0-5)
+QCFG: "hsdpacat",(6,8,10-24)
+QCFG: "hsupacat",(5,6)
+QCFG: "pdp/duplicatechk",(0,1)
+QCFG: "risignaltype",("respective","physical")
+QCFG: "lte/bandprior",(1-43),(1-43),(1-43)
+QCFG: "volte_disable",(0,1)
+QCFG: "diversity/config",(0,1),(1-8),(0)
+QCFG: "div_test_mode",(0,1)
+QCFG: "usbnet",<0-3>
+QCFG: "usbspeed",("20","311","312")
+QCFG: "data_interface",(0,1),(0,1)
+QCFG: "pcie/mode",(0,1)
+QCFG: "sms_control",(0,1),(0,1)
+QCFG: "call_control",(0,1),(0,1)
+QCFG: "netmaskset",(0,1)[,]
+QCFG: "clat",(0,1),(0,1),,(0,32,40,48,56,64,96),,(0,1),(0,1,2,4,8),(0,1),(0,1),(0,1,
2),(0,1,2)
+QCFG: "enable_gea1"[,(0,1)]
+QCFG: "dhcppktfltr",(0,1)
OK

patrikg · May 14, 2026, 8:27am

Sorry for a stupid question: Is the APN correct ?

sasan_kn · May 14, 2026, 9:20am

That’s a good question. Yes, the APN is correct, and I tested it with different SIM cards and carriers as well the results were the same. I think it’s probably not even reaching the APN layer at all.

optio · May 14, 2026, 6:08pm

Try to add debug lte topics logging, disable-enable lte interface (wait few seconds in between) and see if anything helpful is shown in logs.

PS.

When setting custom APN make sure that “Use Network APN” is unset.

sasan_kn · May 15, 2026, 6:58am

I already enabled LTE debug logging and reproduced the issue by disabling/enabling the LTE interface with a few seconds delay.

The logs show repeated deregistration and forced reconfiguration events:

"forced reconfiguration due to difficulty setting link up"
state changes from "online" to "deregistered"

Also, I am using a custom APN and “Use Network APN” is disabled.

I have already attached the supout.rif file with the debug logs included.

log.txt (39.7 KB)

optio · May 15, 2026, 8:39am

Yes, this should be reported to MT, logs doesn't show much here... This is users forum and we as regular users cannot see attached supout.rif files in support tickets since they can contain sensitive information from ROS config.