[astridevcon-2007] Agenda Planning: Phase 1

[Steven Sokol]

> I'll open the discussions with this then... anyone have additional or
> alternative suggestions for formats and/or topics?

Here are a few topics that seem to keep coming up on my end of things.
 Obviously having an additional 4 daily topics won't work, but perhaps
we can create working groups or task forces or something?


1) Management/Provisioning

How do we best manage adds/moves/changes/deletes?  Is there some way
to improve the Asterisk Realtime Architecture (ARA), integrated it
with the Manager interface, and provide a single, logical,
really-real-time means of managing an Asterisk system that NEVER
requires the PBX be re-started in order for a change to be applied?
(This overlaps with the clustering/scalability topic.)

2) Endpoint Integration

While not a core service of Asterisk, one of the biggest customer
complaints is the lack of support for endpoint discover and
auto-provisioning.  (Pingtel just beat us out in an comparison and
review in Network World mostly because it does a better job of
integrating with phones.)  Can we work up a standard means of
discovering and configuring some of the most popular phones?

3) User Model

This overlaps with the security topic a good deal.  The primary means
of integrating user desktops with Asterisk is using the manager API.
Unfortunately, the manager's internal security model doesn't provide
any easy way to manage access on a granular level.  How can we improve
it to allow for multiple classes of end-users and administrators?  Can
we take the Users.conf concept and expand it to provide better
services to Asterisk users?

4) Onboard & Offboard AstDB

Let's use SQLite3 in place of the current AstDB and configure the DB
functions, applications, CLI commands, and manager commands so that
they can use either the onboard SQLite database or a remote RDBMS --
seamlessly.  SQLite can also serve as a CDR storage mechanism and can
run readily on embedded systems.