Comments inline:
Do you want everyone to know where everyone is calling? I could see mgmt/owners having an issue with this in a normal business environment! Look Mr. Gate$ at extention 666 made 500 calls to Mr Devil last week, I wonder what deals they are making ;)
This would have to be controled by that particular company's policy.. at least the facility will be there..
Doesn't this just display the config files for editing? I wouldn't want to put this as an internet reachable service without https. Heck if I'm just editing a file, why not just vi/vim/emacs/your-fav-editor from an ssh session ( lots of java ssh applets for this/ ssh clients )?
Yes it does just display the conf files but it is far simpler (and usually easier) to simply open a web broswer (authenticate) and edit the files.. Access security will have to be built but network security is again the choice of the admin.. if its only used on a LAN and his users are not to awake then plain text is fine.. :)
I don't think so, could be built as a subset of the PHPconfig functions..
User Self Service would seem to mean replacing the PHPconfig anyway...
Good point..
Make sure to think about limits for call forwarding. Should I be able to forward to a number in some other country?
Authentication/Authorization is a tough slippery slope... LDAP, NIS, NIS+, flatfile, database you get the picture.
I would assume based on the nature of the program the authentication would be DB based..
Both good ideas.. :)
You may want to think about Webadmin as a control frontend and build with that in mind...
Maybe CDR exports from the GUI (csv)? In GUI Archiving mechanism for "old" records? ( record retention policy )
later..
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
