> Functionality: > 1. For now - just basic extension creatian/ modification > 2. IVR's > 3. Personal Extension modification - let usrs change forwarding, call > routing, vmail passord, email, etc. > 4. CDR's in some way or form > 5. Ring groups/call routing, etc. > >
I think you should build your interface separate from the underlying functionality. As Callweaver and Asterisk diverge you will need some kind of abstraction to perform similar functions on both platforms. We have (ambiguous) plans to create an API in the future to manage CallWeaver from. We also have plans to remove/replace the CLI when this occurs. I was thinking about a management GUI just the other day. If I were to starting now, I would use an MVC kind of approach. I would also plan for use on small web servers/embedded web servers where possible. Once you have an attractive interface and some limited functionality (say, thorought the manager interface), and hopefully a robust abstraction layer, I think people will want to help. In the CallWeaver world configuration storage is a can of worms, as is the API. It would seem most everyone does not like what we have now, but we don't have concensus on how to replace it. Design for the future, that's my humble opinion. -Nate _______________________________________________ Openpbx-users mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-users
