morning im trying to make an lte fail over script for sxt lte rb version 7.13 and need to get active sim slot. if i set a variable :cursim [/interface lte settings get sim slot]
:if ($cursim=a) do={:log info message=“sim a”}
:if ($cursim=b) do={:log info message=“sim b”}
print
both logs show sim a even after switching to sim b
what could i be doing wrong thanks
Post the full script, where you set the variable
Sometimes there may be a short delay between switching the SIM card and reading its active status.
Here is a good reference for dual sim scripts: https://wiki.mikrotik.com/wiki/Dual_SIM_Application
I have Ltap LTE6 Kit, with newest 7.14.3 firmware.
I want to use the “Dual SIM failover” script (https://wiki.mikrotik.com/wiki/Dual_SIM_Application), but it’s not working.
The status of the active card cannot be queried.
“/system routerboard sim get sim-slot” is old command for v 6
i try “/interface lte settings get sim-slot”, “/interface lte get sim-slot” empty result.
When i manually swich card 2 to card 3 or vica-verse is working with this command:
“/interface lte settings set sim-slot=2”
“/interface lte settings set sim-slot=3”
Can you help me or is anyone using this with version 7?
Actually, there is an updated article for ROSv7 here: https://help.mikrotik.com/docs/display/ROS/Dual+SIM+Application
Thanks but help please. Where can I find the “get slim-slot” command for 7 on this page?
Unfortunately, I can’t find it, in the example there are also those for v6.
As I mentioned, the “set sim-slot works”, but the current status “get sim-slot” does not.
Maybe something has changed in 7.14.3, the command on v7 should be:
http://forum.mikrotik.com/t/r11e-lte-configuration-help/138222/1
/interface/lte/settings/get sim-slot
I downgraded to 7.11 in several steps (this is the factory version) and upgraded to 7.15rc3, but the situation is the same in every case.
/interface/lte/settings/get sim-slot is empty query.
I don’t know if it could be related to the firmware version of the LTE card. It’s also the latest version.
Did you find a fix for this? I have the same issue