Carrier aggregation info not shown with RUTX_R_00.07.23.5 on RUTX50

drakidis · June 12, 2026, 2:56pm

Hello,

After upgrading my RUTX50 to RUTX_R_00.07.23.5 the Status → Network → Mobile page no longer displays Carrier aggregation information. What I am seeing in the page is that carrier aggregation is inactive and I only see the primary band. The secondary bands are not visible.

But from command line:

admin@Teltonika-RUTX50:~$ gsmctl -A ‘AT+QCAINFO’
+QCAINFO: “PCC”,3194,50,“LTE BAND 7”,1,276,-94,-16,-61,2
+QCAINFO: “SCC”,1700,100,“LTE BAND 3”,1,276,-88,-15,-64,0,0,-,-
+QCAINFO: “SCC”,3050,100,“LTE BAND 7”,1,276,-97,-13,-72,3,0,-,-
+QCAINFO: “SCC”,6400,50,“LTE BAND 20”,1,276,-82,-20,-52,-6,0,-,-
+QCAINFO: “SCC”,634080,12,“NR5G BAND 78”,427

admin@Teltonika-RUTX50:~$

I can tell that I have carrier aggregation also by doing a speed test. It is fast enough to say that carrier aggregation is active.

Please check why the Mobile page on the GUI thinks it is inactive.

Some more findings:

admin@Teltonika-RUTX50:~$ gsmctl -A ‘AT+QCAINFO’
+QCAINFO: “PCC”,3050,100,“LTE BAND 7”,1,276,-92,-12,-59,2
+QCAINFO: “SCC”,1700,100,“LTE BAND 3”,1,276,-86,-12,-65,-1,0,-,-
+QCAINFO: “SCC”,1871,75,“LTE BAND 3”,1,276,-87,-12,-66,0,0,-,-
+QCAINFO: “SCC”,6400,50,“LTE BAND 20”,1,276,-83,-19,-55,-6,0,-,-
+QCAINFO: “SCC”,634080,12,“NR5G BAND 78”,427

So although modem is ok and uses carrier aggregation, gsmctl does not correctly interpret this and thinks the secondary bands are inactive. It seems like a libgsm.so problem.

Teknology · June 12, 2026, 3:22pm

Yes I’ve have the same problem with latest 7.23.5 firmware.

And now 5G SA not working

drakidis · June 12, 2026, 3:38pm

One more finding. I am not actually seeing the primary band on the Mobile page. I am just seeing a band sometimes it coincides with the primary sometimes not.

drakidis · June 13, 2026, 4:46am

Maybe as in the carrier aggregation case it appears not working on the page but on the modem level it may be ok.

I wonder is this community forum the right place to report these issues?

fortel · June 13, 2026, 10:04am

While investigating slow speeds that started about 2-3 weeks ago, I noticed that carrier aggregation is also marked as “inactive” and my modem temperature was quite high.

I’m using an OTD500 and I’m located in Athens Greece.

More details in my thread here:

drakidis · June 13, 2026, 6:00pm

At least temperature seems normal on RUTX50. I am also in Athens.

anon13159616 · June 16, 2026, 6:42am

Hello, @drakidis!

Thank you for your post!

We were able to recreate the issue on our side and have forwarded the information to our RnD team for further investigation.

We will let you know once we have something to report.

Kind regards,
Laura.

dabrmar · June 16, 2026, 12:27pm

RUTX50 RUTX_R_00.07.23.6 - problem still exists.

walter66 · June 20, 2026, 10:02am

Same here, using RUTX50 RUTX_R_00.07.23.6

walter66 · June 21, 2026, 9:04am

wait a min…after few hours carrier aggregation went on and console is showing correctly bands. Same firmware, nothing has been changed.

drakidis · June 21, 2026, 10:16am

What is the output of the following commands?

gsmctl -A ‘AT+QCAINFO’

gsmctl -G

walter66 · June 21, 2026, 10:44am

The first returns:

+QCAINFO: “PCC”,100,100,“LTE BAND 1”,1,404,-100,-14,-64,-1

+QCAINFO: “SCC”,638016,10,“NR5G BAND 78”,28

The second returns:

CA 0

Primary: 1 | Frequency: 100 | Bandwidth: 20 | Band: LTE_B1 | Cell st: registered

PCID: 404 | RSRP: -100 | RSRQ: -15 | RSSI: -64 | RSSNR: -4

CA 1

Primary: 0 | Frequency: 638016 | Bandwidth: 80 | Band: 5G_N78 | Cell st: unknown

PCID: -1 | RSRP: -1 | RSRQ: -1 | RSSI: -1

walter66 · June 21, 2026, 11:32am

As additional comment…installed 07.23.6 and CA went away from console. Only main band visible. Despite that throughput was >130Mb. Command line tool reporting normal connection and CA.

After a night CA and bands reappeared in the web console, without any modification

drakidis · June 21, 2026, 2:30pm

It seems that you have at least on the example you showed a much simpler carrier aggregation scheme than 5e one I have with only one secondary band. Who knows maybe the problem appears on occasion on more complex carrier aggregation schemes. Anyway, as the Teltonika person above mentioned, the issue is in R&D now, so let’s see what they will say.

anon13159616 · June 26, 2026, 8:41am

Hello!

Our R&D team has investigated the issue and found the root cause.

We do sincerely apologize for any inconvenience this may have caused.

The fix will be available with a new firmware, which will be 7.24.

We appreciate your patience and support.

Kind regards,
Laura.

drakidis · June 26, 2026, 9:55am

Thank you,

As I am just curious, can you please say a few things about the root cause? Was the problem in a .so file, in the web page itself or elsewhere?

Thank you in advance

anon13159616 · June 26, 2026, 11:51am

Hello, @drakidis!

Thank you for your response.

Here is a comment from our R&D team:

We had this issue, where we were having segmentation faults on gsmd while updating cache values (that’s where carrier aggregation data lives).

To fix that, we added some validation checks before updating, like checking if the variable that holds the new data isn’t empty, and so on. So when we update any value in the cache, we send the length of the datatype (how many bytes are needed to store a single value of that data type).

For JSON, this wasn’t needed and was defined as 0. So JSON data didn’t pass these new validation checks because its length was 0, and it never updated the cache.

In reality, carrier aggregation worked, but only WebUI showed incorrect data.

We hope this answers your questions.

Kind regards,
Laura.

akwe-xavante · June 26, 2026, 1:25pm

New firmware fixing the issue is now available: A new firmware is now available, and the issue has been fixed.

You can wait until the router lets you know, or you can download it from here and manually install it early: https://wiki.teltonika-networks.com/view/RUTX50_Firmware_Downloads