Really, what I would do is to set up a daily restart point when there is no or very little activity, something like running nightly:
asterisk -rx "stop when convenient" and then having the monitoring script restart it immediately. Do you need to unload the zaptel modules as well or is restarting Asterisk enough? l. PS. one of the things I like less about asterisk is that every time you have a different piece of iron connected to a PBX, you end up patching zaptel and recompiling. so all ot of time you find yourself wondering if the patch will be successful with the latest zaptel version or not.... :-( On Tue, 29 Jan 2008 07:24:49 +0100, Mark Greene <[EMAIL PROTECTED]> wrote: > So here is my setup. > > Hardware: > Intel P3 1.2 Ghz > 1 GB RAM > 36 GB Drives Mirrored > > Software: > CentOS 5 > 2.6.18 Kernel > > Asterisk 1.4.14 > Zaptel 1.4.7 (redfone) > LIbpri 1.4.2 > -- Loway Research - Home of QueueMetrics http://queuemetrics.com _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
