WIKIABOUT

FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

Most popular tags

rut955 rut240 rut950 rutx11 rms vpn to openvpn wifi not sms trb140 firmware connection - ipsec on rutx12 rutx09 modbus
We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.

RUT955 -- 00.07.03.xx -- "ubus call sim change" issue with prepaid-sim

0 votes
452 views 17 comments
by anonymous
Dear Teltonika-Team,

I checked all 07.xx.xx versions, and since 00.07.03 the command "ubus call sim change" is switching to sim2 but no "connect" possible anymore. I freshly installed different firmwares and until 00.07.02.7 this command/switch is working well, so that sim2 gets "connected" state.

This is pretty simple to reproduce, please test.

Thx for help,
Rainer

1 Answer

0 votes
by anonymous

Hello,

  

I've tested it, and 10-15 seconds after running the command I was able to use the SIM2 for mobile data just fine on RUT955.

I'd like you to reproduce the issue with the newest available firmware, run the command and after 5 minutes navigate to System → Administration → Troubleshoot and generate a troubleshoot file. It can be attached to the original post and will only be visible to Teltonika moderators.

Awaiting your response!

  

Best regards,
DaumantasG

by anonymous

Thx for answer. I have fresh installation with newest firmware (00.07.03.2) - same issue:

Test-Situation was:
1) Fresh router start (defaultsim=sim1, no auto-switch-rules enabled)
2) In this test now I sync ntp to BrowserTime to be sure my issue it not a time-issue (but issue is also without this step)
3) After some time I do "ubus call sim change" to sim2 (timestamp = 10:39:39 [UTC+1])
4) In GUI I see "Failed to load mobile data" and some time later sim2 is switching back to sim1 (but auto-switching is disabled).
5) After some time on sim1, I do switch-command to sim2 again (timestamp = 10:42:22 [UTC+1]) - but then the state "disconnected" lasts for ever

I did upload of troubleshoot.

Doing these simple steps on firmware before 07.03.xx is working fine.

Thx for help, 
BR Rainer

by anonymous

Hello,

  

Thank you for the information.

Could you try running a command ubus call mobifd.modem0 reload after the switch to the second SIM and see if that helps?

  

Best regards,
DaumantasG

by anonymous
No, this command reported "state = ok" but did not changed anything, sim2 still hanging.

So, I did "ubus call sim change" again to switch to sim1 and again to switch back to sim2, but same issue:

In the WebUI I see that:

a) no atenna dBm is measured
b) disconnected
c) and "State" of sim2 does not provide any "provider data"

Looks like modem is not trying to find provider or even more do not use modem at all.

Booting with defaultsim=sim2 immediately leads to proper work/connected.
by anonymous
Thank you for the information.

I'd like to organize a remote session for troubleshooting. I'll message you with the details via a private message.

Best regards,
DaumantasG
by anonymous
Answered. It would be fine you could go via RMS.

The same issue happens if I simple set the defaultsim-flag:

sim2 connects, if it is set as defaultsim and the router is rebooted; so sim2 is working in general;

sim2 connects, if sim1 is set as defaultsim, the router is rebooted and after reboot the defaultsim is set to sim2 (in this case I get the message "failed to load mobile data" but sim2 works);

Setting the defaultsim-flag more than one times sim2 will never go into connected mode (even more, as mentioned above: no dBM and no provider-data can be found).
by anonymous

Hello,

  

RMS is fine as long as the router has a secondary WAN source with higher priority, as when I'll perform a SIM Switch it will loose connection and will be unreachable for me.

Send me the RMS link for CLI and another for WebUI via a private message. Do not forget to include the router password as well.

Thank you!

  

Best regards,
DaumantasG

by anonymous

Hi,

since there was no answer on sending my RMS-links to you, I proceeded to test and found out: 

...that the issue (after an "ubus call sim change" sim2 shows "disconnected" for ever, or even more sim2 shows no provider and no dB-antenna power) is NOT, if sim1 is not inserted. So everything is fine if sim1 is missing.

Just if the sim1-card is inserted AND if this card is empty (it is a typical data-prepaid-card from https://prepaid-global.com/ or so) then the modem (or whatever) is corrupted and sim2 does also mo more work.

So an empty data-prepaid-sim-card seems somehow corrupting something.

Unfortunately only a reboot helps to get sim2 working (a modem-reboot does NOT help).

This below is the content in log, when modem switches to sim2 (after sim1 was not able to connect since data was empty):

Mon Jan 23 17:19:16 2023 daemon.info mobifd: [gsm.modem0] Config reload initiated

Mon Jan 23 17:19:17 2023 daemon.info mobifd: [gsm.modem0] Failed to get SIM PIN state

Mon Jan 23 17:19:17 2023 daemon.info mobifd: [gsm.modem0] Reloading modem

Mon Jan 23 17:19:28 2023 daemon.info mobifd: [gsm.modem0] Init "ue usage" modem reboot prevention triggered. Settings likely not set

Mon Jan 23 17:19:30 2023 daemon.info mobifd: [gsm.modem0] SMS storage: me

Mon Jan 23 17:19:30 2023 daemon.info mobifd: [gsm.modem0] APN 'IMS' isn't prepared for PDP 2, preparing it

Mon Jan 23 17:19:31 2023 daemon.info mobifd: [gsm.modem0] APN 'IMS' was successfully prepared for PDP 2

Mon Jan 23 17:19:31 2023 daemon.info mobifd: [gsm.modem0] APN 'web.vodafone.de' isn't prepared for PDP 1, preparing it

Mon Jan 23 17:19:32 2023 daemon.info mobifd: [gsm.modem0] APN 'web.vodafone.de' was successfully prepared for PDP 1

Mon Jan 23 17:19:32 2023 daemon.info mobifd: [gsm.modem0] Attempting to establish connection to operator with 5 seconds of timeout

Mon Jan 23 17:19:32 2023 daemon.info mobifd: [gsm.modem0] Scanning operators. Modem will not respond for a while

Mon Jan 23 17:19:32 2023 daemon.err mobifd: [gsm.modem0] Failed to scan operators

Mon Jan 23 17:19:32 2023 daemon.err mobifd: [gsm.modem0] No valid operators found

Mon Jan 23 17:19:35 2023 kern.info kernel: Changing to SIM2: unable to establish data connection

Mon Jan 23 17:19:37 2023 daemon.notice wpa_supplicant[4678]: wlan0: WPA: Group rekeying completed with 3c:a6:2f:5e:6b:67 [GTK=CCMP]

Mon Jan 23 17:19:37 2023 daemon.info mobifd: [gsm.modem0] Attempting to establish connection to operator with 10 seconds of timeout

Mon Jan 23 17:19:37 2023 daemon.info mobifd: [gsm.modem0] Scanning operators. Modem will not respond for a while

Mon Jan 23 17:19:37 2023 daemon.err mobifd: [gsm.modem0] Failed to scan operators

Mon Jan 23 17:19:37 2023 daemon.err mobifd: [gsm.modem0] No valid operators found

Mon Jan 23 17:19:47 2023 daemon.info mobifd: [gsm.modem0] Attempting to establish connection to operator with 15 seconds of timeout

Mon Jan 23 17:19:47 2023 daemon.info mobifd: [gsm.modem0] Scanning operators. Modem will not respond for a while

Mon Jan 23 17:19:47 2023 daemon.err mobifd: [gsm.modem0] Failed to scan operators

Mon Jan 23 17:19:47 2023 daemon.err mobifd: [gsm.modem0] No valid operators found

Mon Jan 23 17:20:02 2023 daemon.info mobifd: [gsm.modem0] Attempting to establish connection to operator with 30 seconds of timeout

Mon Jan 23 17:20:02 2023 daemon.info mobifd: [gsm.modem0] Scanning operators. Modem will not respond for a while

by anonymous

Hello,

Could you clarify where you sent the RMS links? I have not received any messages from you via private message.

As for the modem freezing up, that is most likely caused by this log message:

daemon.info mobifd: [gsm.modem0] Scanning operators. Modem will not respond for a while

It is constantly scanning for operators, because:

daemon.err mobifd: [gsm.modem0] No valid operators found

Could you double-check if the prepaid-global SIM card can connect to any of the operators in your area? Perhaps you have set up a carrier whitelist/blacklist?

Also, are you sure, that APN web.vodafone.de is the correct one for the global SIM?

Best regards,
DaumantasG

by anonymous

Hi,

I directly press reply-to-all 2,5h after I got your mail to respond with RMS-data - and I saw mail was sent out. Anyhow, RMS-links of course are no more valid and Modem was needed to be used again.

I have now better/more detailed/accurate testing for you:

Situation:

SIM1=Prepaid-SIM (with empty data-volume).
SIM2=Contract-SIM (working well around the clock).

After Router-Start, SIM1 goes to "connected" (and gets an IP) - but since data-volume is empty, no ping is working anymore to internet - but that's fine, and this just happens when an prepaid-sim goes out of data.

An "ubus call sim change" at "Tue Jan 24 14:45:13" switches to sim2, and sim2 is working well.
An "ubus call sim change" switches to sim1, and sim1 throws the logoutput in attached logfile mob.txt.
...read logfile...
An "ubus call sim change" at "Tue Jan 24 14:47:27" switches to sim2 again, BUT sim2 is no more working well, see the logoutput in attached logfile mob.txt.
...read logfile...

Btw: The last line in the log shows a switch back to sim1 because of data-fail-rule in sim2-config (after ~5min timeout).

Thx for any help,
Rainer
by anonymous

One more thing to try could be to reinstall the firmware using the bootloader method. This completely wipes the device and might help solve the issue. Keep in mind, that v7.3.3 of RutOS is out, which addresses some WiFi-related issues some users experienced on RUT9 devices.

Otherwise, a modem update might be needed. If the bootloader method does not help, contact me via the private message and I'll send you the details.

Best regards,
DaumantasG

by anonymous

Hi, I cannot use bootloader to install firmware, since my bootloader is the legacy one (and the update-process tells me the same).

Where I can find bootloader which support RUTOS7 (I have product code "RUT955T03XXX") ?

Thx for help, 
Best regards, Rainer

by anonymous

Hello,

  

You'll first need to upgrade to RUT9XX_R_00.06.09.2 using the bootloader, and then from the legacy RutOS (not the bootloader) update to RUT9_R_00.07.03.3 without keeping settings. Let me know how it goes.

  

Best regards,
DaumantasG

by anonymous

I did as you mentioned (all fresh, no old settings).

Same issue!

Tests:
a) Reboot to the default sim1: Sim1 is working well. But an "ubus call sim change" should change to sim2 but it never connects to any Provider/APN.
b) Reboot to the default sim2: Sim2 is working well. But an "ubus call sim change" should change to sim1 but it never connects to any Provider/APN.

What could we do now? Modem-Update?

(btw: after a "gsmctl --reboot" I got the WebUI message "Failed to load mobil data")

Thx for any help,
BR Rainer

# Typical messages according to issue above are:
...

Mon Jan 30 14:00:36 2023 daemon.info mobifd: [gsm.modem0] APN 'web.vodafone.de' isn't prepared for PDP 1, preparing it
Mon Jan 30 14:00:37 2023 daemon.info mobifd: [gsm.modem0] APN 'web.vodafone.de' was successfully prepared for PDP 1
Mon Jan 30 14:00:37 2023 daemon.info mobifd: [gsm.modem0] Attempting to establish connection to operator with 5 seconds of timeout
Mon Jan 30 14:00:47 2023 daemon.info mobifd: [gsm.modem0] APN '' isn't prepared for PDP 1, preparing it
Mon Jan 30 14:00:47 2023 daemon.info mobifd: [gsm.modem0] APN '' was successfully prepared for PDP 1
Mon Jan 30 14:00:47 2023 daemon.info mobifd: [gsm.modem0] Attempting to establish connection to operator with 5 seconds of timeout
Mon Jan 30 14:00:57 2023 daemon.info mobifd: [gsm.modem0] APN 'home.vodafone.de' isn't prepared for PDP 1, preparing it
Mon Jan 30 14:00:57 2023 daemon.info mobifd: [gsm.modem0] APN 'home.vodafone.de' was successfully prepared for PDP 1
Mon Jan 30 14:00:57 2023 daemon.info mobifd: [gsm.modem0] Attempting to establish connection to operator with 5 seconds of timeout
Mon Jan 30 14:01:07 2023 daemon.info mobifd: [gsm.modem0] APN 'web.vodafone.de' isn't prepared for PDP 1, preparing it
Mon Jan 30 14:01:08 2023 daemon.info mobifd: [gsm.modem0] APN 'web.vodafone.de' was successfully prepared for PDP 1
Mon Jan 30 14:01:08 2023 daemon.info mobifd: [gsm.modem0] Attempting to establish connection to operator with 10 seconds of timeout
Mon Jan 30 14:01:28 2023 daemon.info mobifd: [gsm.modem0] APN '' isn't prepared for PDP 1, preparing it
Mon Jan 30 14:01:28 2023 daemon.info mobifd: [gsm.modem0] APN '' was successfully prepared for PDP 1
Mon Jan 30 14:01:28 2023 daemon.info mobifd: [gsm.modem0] Attempting to establish connection to operator with 10 seconds of timeout
Mon Jan 30 14:01:48 2023 daemon.info mobifd: [gsm.modem0] APN 'home.vodafone.de' isn't prepared for PDP 1, preparing it
Mon Jan 30 14:01:48 2023 daemon.info mobifd: [gsm.modem0] APN 'home.vodafone.de' was successfully prepared for PDP 1
...

by anonymous
I've sent you a private message.

Best regards,
DaumantasG
by anonymous

Thx for detailed info about modem-update - it worked with exit code 0.

Afterwards I was able to switch a few times between sim1 and sim2.
But suddenly a switch hangs endless and either logread -f does not show anything anymore or I see endless repearting below messages (but WebUI seems still working):

...
Tue Jan 31 21:13:46 2023 daemon.err mobifd: [gsm.modem0] Failed to get information about all PDP contexts
Tue Jan 31 21:13:46 2023 daemon.info mobifd: [gsm.modem0] APN '' isn't prepared for PDP 1, preparing it
Tue Jan 31 21:13:46 2023 daemon.err mobifd: [gsm.modem0] Failed to set PDP 1 context
Tue Jan 31 21:13:46 2023 daemon.err mobifd: [gsm.modem0] Failed to insert '' APN
Tue Jan 31 21:13:46 2023 daemon.info mobifd: Failed to prepare connection for "gsm.modem0". Waiting 0 seconds
Tue Jan 31 21:13:46 2023 daemon.err mobifd: [gsm.modem0] Failed to get information about all PDP contexts
Tue Jan 31 21:13:46 2023 daemon.info mobifd: [gsm.modem0] APN '' isn't prepared for PDP 1, preparing it
Tue Jan 31 21:13:46 2023 daemon.err mobifd: [gsm.modem0] Failed to set PDP 1 context
Tue Jan 31 21:13:46 2023 daemon.err mobifd: [gsm.modem0] Failed to insert '' APN
Tue Jan 31 21:13:46 2023 daemon.info mobifd: Failed to prepare connection for "gsm.modem0". Waiting 0 seconds
Tue Jan 31 21:13:46 2023 daemon.err mobifd: [gsm.modem0] Failed to get information about all PDP contexts
Tue Jan 31 21:13:46 2023 daemon.info mobifd: [gsm.modem0] APN '' isn't prepared for PDP 1, preparing it
Tue Jan 31 21:13:46 2023 daemon.err mobifd: [gsm.modem0] Failed to set PDP 1 context
Tue Jan 31 21:13:46 2023 daemon.err mobifd: [gsm.modem0] Failed to insert '' APN
Tue Jan 31 21:13:46 2023 daemon.info mobifd: Failed to prepare connection for "gsm.modem0". Waiting 0 seconds
Tue Jan 31 21:13:46 2023 daemon.err mobifd: [gsm.modem0] Failed to get information about all PDP contexts
Tue Jan 31 21:13:46 2023 daemon.info mobifd: [gsm.modem0] APN '' isn't prepared for PDP 1, preparing it
Tue Jan 31 21:13:47 2023 daemon.err mobifd: [gsm.modem0] Failed to set PDP 1 context
Tue Jan 31 21:13:47 2023 daemon.err mobifd: [gsm.modem0] Failed to insert '' APN
Tue Jan 31 21:13:47 2023 daemon.info mobifd: Failed to prepare connection for "gsm.modem0". Waiting 0 seconds
...

Btw: While modem-fw update I got some of these  bad-block-messages, maybe this could be a/the problem?

[004.971]: <erase PAGES_PER_BLOCK="64" SECTOR_SIZE_IN_BYTES="2048" num_partition_sectors="29696" physical_partition_number="0" start_sector="120576"    />[004.973]: <log value="start_sector = 120576 and num_partition_sectors =0x7400)"/>
[005.478]: <log value="Skipping:        bad block 0x8b0"/>
[005.661]: <response value="ACK" />

With new modem-fw it's possible each time when a sim-switch is hanging to release again by "gsmctl --reboot".

by anonymous

Hello,

  

Flash on your device seems to pass all checks, so it should not be an issue.

I'd like you to generate one last troubleshoot file, and I'll contact our RnD team.

For now, if you have frequent SIM switches, I'd recommend configuring ping reboot (Services → Auto Reboot → Ping/Wget Reboot). Set it to reboot the modem if the connection is lost.

  

Best regards,
DaumantasG

by anonymous

Thx, in my scenario a hanging modem could only be avoided if every "ubus call sim change" have a prefixed "gsmctl --reboot; sleep 10".

Rebooting modem mostly releases a modem-hang - BUT it does not reset the timer for the sim-switch rules.
But an "ubus call sim change" or a modem-restart an already started sim-switch-rule does NOT stoppt/reset sim-switch-timer for this sim-slot - so the timer continues and fires a failover despite sim has been already switched by "ubus call sim change" (message in logger is: "SIM switch in progress. Triggered by data_fail rule").

I disabled now sim-switching at all and implemented own checks that reset the timer each time an "ubus call sim change" happens.

BR Rainer