Yea, figured it out already - was in way to write about it here, but You were faster. Shame on me, ash on head etc. Really

I've managed to get it working - thanks for Your suggestion. I also noticed, that using *any* method of deinstallation (regular, purge, whatever) apt-get report about *not* being able to delete things in /opt/, due to "folder not empty". Still, I haven't put any files on it manually - everything there was created during installation, or by smscon/smscon-editor. As result, everything is left instact there (files created during installation also) This error occurs, when trying to "purge" - which, essentially, makes automatically purging it impossible. Need to delete everything manually.

---

I was able to use it, and daemon/startup on boot/configuring via smscon-editor works. Testing via "test" tab also. Ho ever, I noticed few glitches:

1. Prefix (commands tab) - this option seems to be non-working at all. Saving setting (with "Prefix" set) doesn't write at all to smscon config. After closing and re-opening smscon-editor, prefix field is also empty.

2. Despite testing/initializing etc being working great, I can't use sms commands, that I've set. No matter what I'm doing, SMS is received normally, and no defined action is taken by device. I use space inside my commands (checked in wiki that it's ok), and filtered out possible typos. Tried both with prefix (that seems to be non-working anyway), and without. Overall, "Wasted" many sms'es trying to test any possible scenario (including normal sms'es and flash sms'es) - to no avail.

The only thing I can think of, is that I'm using smsend - but, it should not matter, as SMS'es are received normally, saved in conversation etc.

Also, for testing purposes, number "authorized" to send sms commands, is same numer, that is currently inside my N900 - i.e. I'm sending sms'es to myself (for testing purposes). Common sense tells me that it should not matter, but, should I test it from other phone?

Any ideas greatly appreciated.

/Estel

// Edit

Another bug found - there is no setting (in smscon-editor) to disable reverse ssh possibility, but if user delete values from writeable fields (host, port etc), it's possible to save settings. Then, on next start of smscon-editor, a "Critical failure in user config" is reported, and smscon-editor refuses to start. I've fixed it, by manually editing smscon config, and adding random value to reverse ssh fields.