Hello, we are using the RUT955 with RutOS version 00.07.02.04 and cannot get the modem to reconnect after we disable and then re-enable the modem via JSON-RPC.
Our custom application has a test feature that intentionally disables the modem in RUT955 so that we can test the attached satellite modem (attached to the WAN port of the RUT955)
To turn off the modem we send the following commands
{"method":"call","params":["855c3640bf9963d027a9b244f6a4175d","uci","set",{"match":{"disabled":0},"values":{"disabled":1},"section":"mob1s1a1","type":"interface","config":"network"}],"jsonrpc":"2.0","id":1}
{"method":"call","params":["855c3640bf9963d027a9b244f6a4175d","uci","commit",{"config":"network"}],"jsonrpc":"2.0","id":1}
{"method":"call","params":["855c3640bf9963d027a9b244f6a4175d","file","exec",{"command":"reload_config","params":null}],"jsonrpc":"2.0","id":1}
This seems to work and the modem is disabled in the WebUI, we enable the WAN and satellite modem performs its' test ok.
Then we send the following commands to re-enable the modem.
{"method":"call","params":["855c3640bf9963d027a9b244f6a4175d","uci","set",{"match":{"disabled":1},"values":{"disabled":0},"section":"mob1s1a1","type":"interface","config":"network"}],"jsonrpc":"2.0","id":1}
{"method":"call","params":["855c3640bf9963d027a9b244f6a4175d","uci","commit",{"config":"network"}],"jsonrpc":"2.0","id":1}
{"method":"call","params":["855c3640bf9963d027a9b244f6a4175d","file","exec",{"command":"reload_config","params":null}],"jsonrpc":"2.0","id":1}
After these commands, we expect the modem to re-register and then re-connect. But even though all of these commands seem to be accepted, we see no errors, and the modem shows as registered ... the modem never shows "connected" and is not sending data (as far as we know).
If we use the WebUI to disable and re-enable the modem... it works fine. The WebUI can do this...but the json-rpc cannot
I have attached the troubleshooting file