Re: [Asterisk-Users] Web UI - Best practices?
On Wed, Jun 14, 2006 at 10:48:35PM -0700, Mike Fedyk wrote: Tzafrir Cohen wrote: On Wed, Jun 14, 2006 at 11:51:06AM -0400, Mike wrote: Hi, I'm stuck writing a Web GUI because nothing out there is exactly what I need. I'm not writing something as extensive as what _is_ out there, but just something that allows users to change where their calls are forwarded and other small things like that. What I wanted to know is what is recommended by those you successfully wrote their own UI : 1) Modifying the config directly in the Asterisk RealTime DB and and use Asterisk Realtime? This seems like the obvious choice, but I have a bad feeling about this method...especially with respect to future changes I would make to my UI or that the Asterisk dev team would make to their own tables / code Non-static real time mean that your PBX becomes non-functional if the DB server has a problem (or is even a bit loaded). Why is it that more people haven't turned to LDAP to solve this problem? It is optimized for a light write and heavy read workload that seems perfectly suited for use in a PBX dial plan. It is lightweight for a large enterprise environment. Not for a single stand-alone machine. OpenLDAP and just works are two different things in my own memory. And your setup still depends on the availbility of another server/service. BTW: I forgot to mention another option: using '#exec' in the config files to regenerate the relevant parts on reload. This can save you most of the permissions problems. You only need to permit the web interface to do an 'extensions reload' (through sudo or whatever), but the cost of that reload is now higher. -- Tzafrir Cohen sip:[EMAIL PROTECTED] icq#16849755 iax:[EMAIL PROTECTED] +972-50-7952406 [EMAIL PROTECTED] http://www.xorcom.com ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] Web UI - Best practices?
Hi, I'm stuck writing a Web GUI because nothing out there is exactly what I need. I'm not writing something as extensive as what _is_ out there, but just something that allows users to change where their calls are forwarded and other small things like that. What I wanted to know is what is recommended by those you successfully wrote their own UI : 1) Modifying the config directly in the AsteriskRealTime DB and and use Asterisk Realtime?This seems like the obvious choice, but I have a bad feeling about this method...especially with respect to future changes I would make to my UI or that the Asterisk dev team would make to their own tables / code 2) Using custom tables I make up myself, and querying that DB with the MySQL commanddirectly in the .conf files (or Realtime asterisk for that matter)(http://www.voip-info.org/wiki/index.php?page=Asterisk+cmd+MYSQL) ? Any input is appreciated...I really don't want to start on the wrong foot. Option 2 looks better (less dependent onAsterisk not changing from version to version) butI feel it'll make a mess out of the code. While Option 1 looks like it'llbe messybecause I have to adapt to the Realtime DB format in my PHP code, but at least the Asteriskcode will be clean. Really, opinons based on anecdotes would help me. Regards, Mike ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Web UI - Best practices?
On Wed, Jun 14, 2006 at 11:51:06AM -0400, Mike wrote: Hi, I'm stuck writing a Web GUI because nothing out there is exactly what I need. I'm not writing something as extensive as what _is_ out there, but just something that allows users to change where their calls are forwarded and other small things like that. What I wanted to know is what is recommended by those you successfully wrote their own UI : 1) Modifying the config directly in the Asterisk RealTime DB and and use Asterisk Realtime? This seems like the obvious choice, but I have a bad feeling about this method...especially with respect to future changes I would make to my UI or that the Asterisk dev team would make to their own tables / code Non-static real time mean that your PBX becomes non-functional if the DB server has a problem (or is even a bit loaded). Something quite similar to static real-time is to have the UI (re)write a small portion of the dialplan that will be included, and have it initiate an 'extentions reload' on any change. 2) Using custom tables I make up myself, and querying that DB with the MySQL command directly in the .conf files (or Realtime asterisk for that matter)(http://www.voip-info.org/wiki/index.php?page=Asterisk+cmd+MYSQL) ? This has basically the same weakness of non-static real-time: overhead and dependence at the time of the call. Any input is appreciated...I really don't want to start on the wrong foot. Option 2 looks better (less dependent on Asterisk not changing from version to version) It is basically the same. Unless you want to make something that is quite generic (if you do, you might as well stick with an existing UI that pays with complexity as the price for generity) you'll probably want to use some nice local features and use a customized dialplan. but I feel it'll make a mess out of the code. While Option 1 looks like it'll be messy because I have to adapt to the Realtime DB format in my PHP code, but at least the Asterisk code will be clean. Really, opinons based on anecdotes would help me. -- Tzafrir Cohen sip:[EMAIL PROTECTED] icq#16849755 iax:[EMAIL PROTECTED] +972-50-7952406 [EMAIL PROTECTED] http://www.xorcom.com ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Web UI - Best practices?
On 11:51, Wed 14 Jun 06, Mike wrote: Hi, I'm stuck writing a Web GUI because nothing out there is exactly what I need. I'm not writing something as extensive as what _is_ out there, but just something that allows users to change where their calls are forwarded and other small things like that. What I wanted to know is what is recommended by those you successfully wrote their own UI : 1) Modifying the config directly in the Asterisk RealTime DB and and use Asterisk Realtime? This seems like the obvious choice, but I have a bad feeling about this method...especially with respect to future changes I would make to my UI or that the Asterisk dev team would make to their own tables / code 2) Using custom tables I make up myself, and querying that DB with the MySQL command directly in the .conf files (or Realtime asterisk for that matter)(http://www.voip-info.org/wiki/index.php?page=Asterisk+cmd+MYSQL) ? I went for option 3: WebUI writes stuff to db, and some script generates static extensions.conf for the server. I did not create something functional yet, but the design/planning docs are ready. -- Michiel van Baak [EMAIL PROTECTED] http://michiel.vanbaak.eu GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x71C946BD Why is it drug addicts and computer afficionados are both called users? ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Web UI - Best practices?
Michiel van Baak wrote: On 11:51, Wed 14 Jun 06, Mike wrote: Hi, I'm stuck writing a Web GUI because nothing out there is exactly what I need. I'm not writing something as extensive as what _is_ out there, but just something that allows users to change where their calls are forwarded and other small things like that. What I wanted to know is what is recommended by those you successfully wrote their own UI : 1) Modifying the config directly in the Asterisk RealTime DB and and use Asterisk Realtime? This seems like the obvious choice, but I have a bad feeling about this method...especially with respect to future changes I would make to my UI or that the Asterisk dev team would make to their own tables / code 2) Using custom tables I make up myself, and querying that DB with the MySQL command directly in the .conf files (or Realtime asterisk for that matter)(http://www.voip-info.org/wiki/index.php?page=Asterisk+cmd+MYSQL) ? I went for option 3: WebUI writes stuff to db, and some script generates static extensions.conf for the server. I did not create something functional yet, but the design/planning docs are ready. IMO, option 3 is the best bet. As you pointed out, writing to * RealTime DB puts you in harm's way w/ respect to future development, as well as operational dependency on the db. Option 2 also has the same external dependency. With option 3 your UI is abstracted from asterisk .conf files and if the db is unavailable for any reason * will not be affected. Looking further out, any changes to * dial plan syntax will only need to be implented in your db-.conf conversion script. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Web UI - Best practices?
Tzafrir Cohen wrote: On Wed, Jun 14, 2006 at 11:51:06AM -0400, Mike wrote: Hi, I'm stuck writing a Web GUI because nothing out there is exactly what I need. I'm not writing something as extensive as what _is_ out there, but just something that allows users to change where their calls are forwarded and other small things like that. What I wanted to know is what is recommended by those you successfully wrote their own UI : 1) Modifying the config directly in the Asterisk RealTime DB and and use Asterisk Realtime? This seems like the obvious choice, but I have a bad feeling about this method...especially with respect to future changes I would make to my UI or that the Asterisk dev team would make to their own tables / code Non-static real time mean that your PBX becomes non-functional if the DB server has a problem (or is even a bit loaded). Why is it that more people haven't turned to LDAP to solve this problem? It is optimized for a light write and heavy read workload that seems perfectly suited for use in a PBX dial plan. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
