Well I’m no Linux guru either, so I get a little help. Install a web front end to do the dirty work.
From the command line do the following
wget heanet.dl.sourceforge.net/source … noarch.rpm
rpm -U webmin-1.230-1.noarch.rpm
You’ll find an icon called cron. enter the command: reboot and set the time you want it to execute
rgds
Thank you bouth. I’ll try them all.
[quote=“lonnie”]The key to any mission critical solution is redundancy.
Any electronic system based on IC’s, power supplies and circuit boards will fail… at some point. As an engineer/designer it is the basic process of matching the mean-time-to-failure to the task at hand.
Simply put, one asterisk box and one IP connection will produce a failure rate higher than many businesses can tolerate.
Simply providing single redundant asterisk boxes and IP connections you are probably at the Avaya uptime levels. (I have no data to prove this, sorry.)
The trick is to automate the redundancy.
Lonnie[/quote]
I’m not concerned about the hardware, I know how to make servers as redundant as possible, we have a hot spare standing by etc…
But what about the reliability of Asterisk?
Has it improved with version 1.2 ?
[quote]But what about the reliability of Asterisk?
Has it improved with version 1.2 ?[/quote]
1.2 was released, like, a week ago. It’s too early to tell. Wait 6 months and ask again.
I believe issues like these are best solved by using SER along with Asterisk. Users register with SER, not Asterisk. Adds tons of complexity to the equation by using SER, but definitely provides scalability and other features.
I have heard from several of my local contacts using * in a 25 user+ environment that reliability is very good. As a collective would you still feel that restarting everynight is key to keeping the system reliable and solid?