OK, I'll upload log in few minutes. Meanwhile, another thing (although, I'm not sure if it is a bug, or a feature ) - selecting "send reply messages on" 'battery status' and ''slide open'', result in (after reboot) message containing battery status /indicating that slide was open even though SIM *wasn't* replaced by one with different IMSI. Which, I think, kill purpose of this command.
Requested log: ...
// edit Another minor mistake (?) in SMSCON editor - On tab "general", under "Mobile number of contact" (aka masternumber) is: Code: *will change on first command AFAIU, it's not true - masternumber doesn't change, SMS is just sent twice.
*will change on first command
Also, another observation - after testing sms message, I got *two* messages with "test message", and also *two* messages with fatal error - hence the feeling of being spammed. In fact, it's only 4 messages instead of 1 (no irony, just trying to be specific).
+feature upgrade request: Allowing to start (remotely) reverse ssh is great option, but, AFAIK, now it works only with ssh connection with password authentication. could You, please, implement authorisation via public key - preferably, located @ configurable (from SMSCON editor) path? The idea is, to create special private/public key part, only for using it with SMSCON. normally, sane usage of public key authentication on mobile device require locking it with password - so, no way to use it remotely, as there is no one on the device to write password - but, special pubkey without password just for SMSCON (thus, creating connection with limited access), would be nice to have. /Estel