Thank you for your feedback. This has led me to create a work-around in my Linux installations:
- Jami can be controlled from the command line so…
- create a script which kills jami, waits some seconds, then restarts Jami, and…
- create a cron job to run this every 20 minutes
20 minutes appears to be the optimum timing; much longer and Jami is more often offline, much less and Jami becomes awkward to use. This comes close (but not 100%) to keeping Jami online permanently. However, it isn’t a very convenient method.
I also created an “Issue” for the developers here, which they have already picked up on - good service!