I've isolated most of the problems I've been experiencing with Asterisk to my hardware (improper vendor implementation of the PCI bus).

I've also discovered that running multiple lines (as would happen during a "live" conference) chews up a lot of bandwidth and CPU. It appears to be about 200MHz of CPU and 128Kbps per call. (This is running the 'meeting room' application w/2 callers). Note that these numbers occur when using ztdummy. (If others have conflicting info, I'd like to hear it.)

However, due to other commitments, I've run out of time to work on this project - until at least September 2008. Any volunteers?

That sounds like a great idea! I'd like the ability to turn on recordings, although we may want to use another podcasting network to distribute the audio rather than imposing on MV's generous hosting of our server.

That sounds like a great idea! I'd like the ability to turn on recordings, although we may want to use another podcasting network to distribute the audio rather than imposing on MV's generous hosting of our server.

My current plan is to install Asterisk on the GNHLUG server, and set up a few "meeting rooms" that people can call into and listen/talk with other people also dialed into it. The various chapter chairs will be given "management" access codes.

Technologies

Comments and Discussion

My current plan is to install Asterisk on the GNHLUG server, and set up a few "meeting rooms" that people can call into and listen/talk with other people also dialed into it. The various chapter chairs will be given "management" access codes.

I might turn on recording too - depending on available disk space.

This will allow people to remotely join in a meeting while its happening, and store the audio portion for posterity.