How about setting profiles?<br>An admin account may have access to every single tab in the GUI, while an user account can just access some selected (by http.conf?) tabs.<br><br>-- <br>Alvaro Oliver<br><br><div><span class="gmail_quote">
2007/4/13, Brandon Kruse <<a href="mailto:bkruse@digium.com">bkruse@digium.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>I totally agree,<br><br>If you guys want to start working on the GUI, go for it.<br><br>I would love to get more community members involved, this discussion<br>alone is priceless, slowly defining exactly what the user wants and
<br>what would be awesome.<br><br>The provisioning stuff, we will see. Alot of things must be integrated<br>into asterisk as well, we will see.<br><br>I like where the discussion is going though, keep it up!<br><br>-brandon
<br><br><br><br>Facundo Ameal wrote:<br>> Steven,<br>> It would be wonderful to have every feature you are talking about.<br>> I 'll try to help in improving the GUI. Count on me.<br>><br>> Greets.<br>
><br>> On 4/13/07, Tzafrir Cohen <<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.com</a>> wrote:<br>>> On Fri, Apr 13, 2007 at 11:28:03AM -0500, Steven Sokol wrote:<br>>> > On 4/13/07, Andrew Latham <
<a href="mailto:lathama@lathama.com">lathama@lathama.com</a>> wrote:<br>>> > >Would a provisioning middle-ware be the better option. A system<br>>> described<br>>> > >below.<br>>> > >
<br>>> > >Stations = MAC address<br>>> > >Extensions = Stations<br>>> > ><br>>> > >1. Station starts up and asks for DHCP<br>>> > >2. DHCP gives TFTP or CONFIG server per MAC (lots of work here)
<br>>> > >3. TFTP or HTTP configs to the phones with correct settings (magic)<br>>> > >3.1 TFTP or HTTP system ask the manager interface for info for<br>>> extension<br>>> > >3.2 TFTP or HTTP configs created and sent to Stations
<br>>> > >4. Station registers<br>>> > ><br>>> ><br>>> > Possibly, but here's my goal in narrative form:<br>>> ><br>>> > A user downloads/builds (or buys) an Asterisk with the GUI. The
<br>>> > README tells him to go and install all of his phones (Polycom, Snom,<br>>> > Linksys, Cisco, Grandstream, etc.), then run the discovery wizard.<br>>> > The discovery tool does the following:
<br>>><br>>> The idea with provisioning is automating. If it is not automatable<br>>> (scriptable), then it remains a non-useful GUI feature.<br>>><br>>> ><br>>> > 1) scans the LAN and finds devices.
<br>>><br>>> How?<br>>><br>>> For Cisco phones: using cdpr?<br>>><br>>> What other method? scan UDP port 5060 over the LAN?<br>>><br>>> > 2) Identifies them by either a SIP options response (using the User
<br>>> > Agent value) or simply by a MAC that fits within a known range for a<br>>> > given manufacturer (is this data available?)<br>>> > 3) adds the devices to a list (conf file, database, etc.) of known
<br>>> > endpoints.<br>>> ><br>>> > The system then builds a "guest" account for each of the newly<br>>> > discovered devices. The device uses the MAC address to craft a config
<br>>> > file for the phone (to be downloaded via HTTP or TFTP) or uses<br>>> > something like CURL to post a basic config to the phone. The system<br>>> > also creates a PEER entry in Asterisk (using
users.conf?) that points<br>>> > to a [guest] or [unknown] context.<br>>> ><br>>> > This basic configuration allows the phone to dial 911, dial inside<br>>> > extensions and to access the provisioning extension: the administrator
<br>>> > can dial an extension, log in using an ID and PIN and feed Asterisk<br>>> > the new extension number for the phone via DTMF.<br>>> ><br>>> > In a VERY simple system that's really all that needs to happen.
<br>>> > Asterisk will update the users.conf entry for the device and move it<br>>> > to the [inside] or [users] or [default] context and that's that. But<br>>> > wait, that's not all....
<br>>> ><br>>> > In a truly integrated system the user would be able to log into an<br>>> > AJAM-powered portal that allows them to control their system features<br>>> > (i.e. features configured on Asterisk using the AstDB, etc.) but they
<br>>> > would ALSO be able to manage the buttons on their phone from the same<br>>> > GUI. They could set busy-lamp fields (BLFs), configure phone<br>>> > features, etc. all from their portal page.
<br>>> ><br>>> > One thing that I would like to try to overcome is the dependence on<br>>> > the DHCP->TFPT->HTTP chain. In some cases the PBX administrator<br>>> > simply won't be able to control the DHCP options system in order to
<br>>> > configure the TFTP option to point to the Asterisk system. If we can<br>>> > build a basic "push" system that can update the TFTP and/or HTTP<br>>> > provisioning address on the most common brands of phone, we can avoid
<br>>> > having to manage the DHCP process or server.<br>>><br>>> Is there any decent "dynamic" tftp daemon?<br>>><br>>> Be that by the way of proxying content to a nearby httpd.
<br>>><br>>> --<br>>> Tzafrir Cohen<br>>> icq#16849755 <a href="mailto:jabber:tzafrir@jabber.org">jabber:tzafrir@jabber.org</a><br>>> +972-50-7952406 mailto:
<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.com</a><br>>> <a href="http://www.xorcom.com">http://www.xorcom.com</a> <a href="http://iax:guest@local.xorcom.com/tzafrir">iax:guest@local.xorcom.com/tzafrir
</a><br>>> _______________________________________________<br>>> --Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br>>><br>>> asterisk-gui mailing list<br>>> To UNSUBSCRIBE or update options visit:
<br>>> <a href="http://lists.digium.com/mailman/listinfo/asterisk-gui">http://lists.digium.com/mailman/listinfo/asterisk-gui</a><br>>><br>><br>><br><br>_______________________________________________<br>
--Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br><br>asterisk-gui mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-gui">
http://lists.digium.com/mailman/listinfo/asterisk-gui</a><br></blockquote></div><br><br clear="all"><br><br>