Cannot send/receive SMS on Metro Unlimited with GL-X3000

Router
1

I have activated a Metro by T-Mobile physical SIM, on the Metro Unlimited 5G plan. The IMEI on the GL-X3000 is set to an unused IMEI from an unlocked Metro-compatible iPhone SE 2022. 5G data is working with no problem, however, SMS is not. The first time I powered on the GL-X3000 with the SIM present, I received 4 text messages. However, it has never received text messages afterwards. I can send/receive SMS if the SIM is moved to the iPhone. However, Metro requires that a 2-factor text be sent to the phone number associated with the SIM, with no way to turn off 2-factor or change the 2-factor number/method. Therefore, the inability to receive text messages via the GL-X3000 is very annoying, as it's required to manage the Metro account. Does anyone know what might be wrong?

I was on the latest stable firmware, and upgraded to the latest beta firmware to see if the issue was resolved (it wasn't). More details:

Firmware: 0704release2
Module version: RM520NGLAAR03A03M4G

Cellular settings:
Protocol: QCM
APN: fast.t-mobile.com (does not work with fast.metropcs.com either)
TTL: 65
HL: 65 (IPv6 is not enabled)
MTU: blank (optional)
Authentication: NONE

3

Hi, can you send text message from the router? Is it possible to share your device to GL.iNet via Goodcloud to check?

4

I am unable to send or receive text messages from the router. Please send me a PM when you are able and I will send you the connection details! I cannot initiate PMs right now.

5

Hello all,

Through additional troubleshooting I was able to come to a suitable solution myself. It appears that with my Metro by T-Mobile SIM, I cannot send/receive text messages when on 5G Standalone (SA). This DOES work on 5G SA when the SIM is plugged into my iPhone, but doesn't work on 5G SA on the GL-X3000.

I used band masking in 'block' mode to block all 5G SA bands, which forces the modem to use 5G NSA. I can now send/receive SMS messages without issue. I get the same speeds on 5G NSA as I did on 5G SA, so this solution is suitable for me. When future modem updates release, I'll test unblocking 5G SA to see if the issue has been resolved, but for now I'll continue using 5G NSA.

7

Hello,

Do you still have the unlimited metro plan on this device? I planning on using a byod for this device. How much gigs of data do you use per month and what speed do you normally get after the 35gigs? Would this device also work with the USB cable connection to phone and detect the data as phone data and not hotspot?

8

I have exactly the same problem. use T-Mobile line. needed to disable 5G SA bands to have SMS working. unfortunately, I can’t leave it like that, as once reboot, sim card won’t register network anymore. Needed to re-enable 5G SA band to get it registered to network.

Hope there will be a fix to the problem

9

I’m seeing a similar issue on a Spitz AX with T-Mobile (not Metro), running firmware 4.8.3 (latest stable as of now).

On 5G, I can send SMS but cannot receive them. Moving the SIM to a phone works fine, so it doesn’t appear to be an account issue.

What worked for me was forcing the router to use 4G using Band Masking:

Steps:

  1. Log in to the router’s web interface

  2. Go to the Internet tab

  3. Under Cellular, click SIM Card Settings (if you’re currently on 5G)

  4. Click Advanced

  5. Enable Band Masking

  6. Set Masking Mode to Open

  7. Click Select under LTE Bands

  8. Click Select All, then close the window

  9. Click Apply

  10. Wait a few minutes for the router to reconnect

After this, the router should connect on 4G and SMS receiving should start working.

Notes:

  • To go back to 5G, disable Band Masking

  • When back on 5G, SMS receiving stops working again

  • This seems related to the 5G SA issue mentioned above, but in my case forcing full LTE (not just NSA) was the only reliable fix

  • This is a good temporary workaround if you need to receive something like a 2FA code

Hopefully this helps someone else and gets fixed in a future firmware or modem update.

1 Like
10

Yep, that's a standard issue ... and a pretty sad one :frowning:
But more a providers issue than a device one, I would say.