asterisk users - Jan 2007 - two level administration tool for Asterisk

Dear Sirs,

I'm looking for a tool which can do the following:

1) higher level of administration, only one person, it can create
"domain"s
and per-domain administration accounts

2) lower level of administration, many persons, each can add new extensions
and change passwords with their domains.

somewhat similar to asterisk2billing, but with privilege separated into
"domains".
we want to sell VoIP for organizations and we want the possibility for every
organisation to manage their extensions. Everything within single Asterisk
installation.

Cheers,
Kate
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20070112/1a506893/attachment.htm

Kate Kretz wrote:
> Dear Sirs,
> 
> I'm looking for a tool which can do the following:
> 
> 1) higher level of administration, only one person, it can create 
> "domain"s and per-domain administration accounts
> 
> 2) lower level of administration, many persons, each can add new 
> extensions and change passwords with their domains.
> 
> somewhat similar to asterisk2billing, but with privilege separated into 
> "domains".
> we want to sell VoIP for organizations and we want the possibility for 
> every organisation to manage their extensions. Everything within single 
> Asterisk installation.
> 
Funny.  I was speaking to the person who originally peaked my interest 
in Asterisk today about the same thing.  My first thought was to map 
"companies", "tenants", etc to individual .conf or .ael
files.  Like:

#include "/etc/asterisk/tenants/tenant_name_or_id.conf"

 From there, each "tenant" conf can include its own necessary and 
additional .conf references.

Then I would have to find a way to distinguish each tenant's calls in 
the initial leg of the call into the system.

I'm just musing out load and would also appreciate some input on this 
subject as well.


-- 

Warm Regards,

Lee

I worked on something like this about a year ago.  It was a multi
tenant web gui that virtualized pretty much everything from extensions
to sip/iax users to voicemail.  What I found that worked fairly well
was to use a prefix for everything user specific with a format that
could easily be parsed.  I used a double underscore followed by a
username followed by a double underscore for the prefix, it worked
pretty well.  I had a couple of functions that would add the prefix
when writing the configuration to a database, and strip it when
displaying everything on the web.  I used a database schema for
storing the configuration data and when it was updated it would write
out the static asterisk files.

The configuration files get a bit more difficult to read, but the
upside is that users could define whatever names they want for things
like extensions and mailboxes without any naming clashes.