Nathan C. Smith wrote: >>From discussions and presentations at Cluecon I've put together a list of > Ideas I'm wondering if they have any value... > > I'll start with my personal one: a scheduler for OpenPBX.org. > It would have it's own .conf file and work a bit like cron. You could set > dial plan events to occur in the conf file. > The .conf file would be read at startup and timer entries would go into a > the database. Events could also be added through the dial plan and > dynamically either through the console or the manager interface. The > scheduler would check for new events - maybe every minute, or have a > configurable granularity. I see this being useful to make it easy for > people less familiar with UNIX to add scheduled events to the system. For > things like wake-up calls and other automated events. Maybe the scheduler > would run in its own thread?
It sounds like that could just use corelib/sched.c. > Tony discussed the event logger from asterisk and the issues with writing to > console. We should consider adding a buffer to record our events and then > writing events to stdout and maybe putting the buffer in it's own process. > This is to address the issue of core being held up until the message is > written. I'd like to see that done with a clean non-blocking i/o event loop. There's a poll in corelib/io.c, but the logger, cli and manager interface appear to use at least two different I/O subroutines, probably more. opbx_carefulwrite might be ok, but opbx_console_puts looks like it blocks. > We discussed a voicemail rewrite or fixes. Most people agree it is a scary > bit of code that could probably be improved on and be given more > flexibility. One example is the ability to configure what order voicemail > messages are played back in: oldest message first, or last. I'd like to see voicemail get implemented in a scripting language. (res_js or something similar). That way it can be easily customized or enhanced. Which brings up a point - res_js seems to be GPL incompatible. I noticed there's a BSD (revised) licensed ECMAscript library out. (http://www.adaptive-enterprises.com.au/~d/software/see/) Anyone interested in playing with that? > Of course CDR improvements always come up. > > Tony's discussion of freeswitch lead to some ideas about reducing how much > access modules have to core and the possibility of writing a spec for > interfacing with core in order to restrict access and decrease the > variability of modules using core. > Also the concept of core being dependent on modules is very backwards, we > should consider this as we rewrite or improve existing modules. I've been wondering about trying to find a suitable library to supplement and/or replace some of the code in the core. APR is nice, but evidently not GPL compatible. I'm looking at pjsip for a possible new sip channel, and that would drag in pjlib, which has a lot of good stuff. http://www.pjsip.org has lots of good docs. > That about wraps it up for me and what I had written down. If anyone feels > like tacking any of these, or ideas of their own just ping me. I'm interested in fixing SIP and voicemail. ---Nathan _______________________________________________ Openpbx-dev mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-dev
