Re: [Astlinux-users] would astlinux users pay for a central remotegui tool ?

[Paul Davidson]

Date: Mon, 30 Oct 2006 08:12:53 -0800
From: "canuck15" < [EMAIL PROTECTED]>
Subject: Re: [Astlinux-users] would astlinux users pay for a central
        remotegui       tool ?
To: "'Discussion of AstLinux - Asterisk on Compact Flash'"
        < [EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain;       charset="us-ascii"

I want all the functionality of freepbx on astlinux.  It does everything I
could ever want a GUI to do.  It does NOT have to run on the astlinux box
though.  Like I have said before, IPManager was perfect.  It ran on a
windows PC and automatically connected by SSH and reloaded the dialplan
after the update.  IMHO that is a perfect solution for astlinux.

-----Original Message-----
From: Barry Fawthrop [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 30, 2006 4:04 AM
To: Discussion of AstLinux - Asterisk on Compact Flash
Subject: Re: [Astlinux-users] would astlinux users pay for a central
remotegui tool ?

Hi All

Someone care to put down some specs.
I'm willing to develop it and support the AstLinux Community.
If we want to draw up some specs I'll get started.

Barry

Just because opinions matter, I would disagree that this is the direction that astlinux should go in.  (not that anyone has to listen to me..).  My view of astlinux is that it fits remarkably well in the SMB space, and in home deployments.  Those environments are the least predictable in terms of infrastructure and environment- making it critical in my view that everything related to astlinux has to be installed with the astlinux image.  Keeping it lean is important- so adding extra, off-distro tools, while they could present some advantages as deployments get larger, distract from my own personal myopic view of what astlinux is best suited for. 
<quasi political rant on>
We as a community should be looking to make VoIP, especially open source VoIP, highly accessible to our end user community.  Anything and everything we can do to further that goal is a bonus- it keeps us employed for custom solutions, and keeps people thinking of OSS VoIP as a friendly, usable solution.  We need to take off our 'linux admin hats' for a while, sit in the user's chair, and forget that we know what's going on under the covers.
</quasi political rant on>

This mindset is leading me closer to work on a php-based administrative/configuration tool, under the Messenger family.  The first public beta of Messenger-VM should be out this week- it's only a vague beginning.  The next release I'm planning will make architectural changes and begin preparation for this tool.  So far, no one is being real vocal about features lists.. here's what I'm thinking:
- Smart, author-agnostic editing of the core config files for extensions, trunks, and voicemail.
- Basic editing for the more off-track configuration files.
- Provisioning modules for existing phone modules- but an open architecture for additional modules to be written without pain.
- Extension and trunk status display (near-realtime)

That's my starter.  Obviously, the first point is the roughest- pulling it off requires more than a little black magic.  I am also playing with the last item, but running into some walls with the way php is currently compiled.  Any chance of adding shared memory and semaphores into the next build?  And/or php4.4.4, And/or a different web server?  I'd like to know, as I start attacking some of this.

-pbd

_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.kriscompanies.com
http://lists.kriscompanies.com/mailman/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to [EMAIL 
PROTECTED]