I was expecting that Ser could be able to load some table contents in runtime like aliases, grp, subscriber and usr_preferences, so that I could use Ser in a production environment where should exist some Web interface for user and administrator management capable of altering aliases, adding or removing users, adding voicemail permissions, altering permissions for each user dialplan, adding forwarding contacts in realtime, etc. I guess I'll have to make some tests to see which function modules read data from DB in realtime and which don't. Regards, Ricardo. Andrey Kouprianov wrote: _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Thanx, I thinks I'll give it a try. Anyway, I assume that if I add aliases adapting serctl script to a web interface, everything will function well, right? Which option should be better - alias_db module from Openser or adding aliases using serctl script sintax exported to a web interface? Regards, Ricardo. sip wrote: > The ONLY information SER doesn't seem to be able to make read straight from > the DB is information about aliases (which it stores in memory and which, even > if you place into the aliases table manually, it won't read). There's an > openser module called alias_db which, if you grab from the openser-0.9.x src > tarball, will compile and work quite readily with SER 0.9.x. > > ( http://www.openser.org/pub/openser/0.9.5/src/openser-0.9.5_src.tar.gz ) > > Documentation about it can be found here: > > http://www.openser.org/docs/modules/0.9.x/alias_db.html > > Unfortunately, you can't use the same aliases table as you use for the usual > lookup("aliases") command, as they use a different structure (although, I have > to say I find the alias_db structure to make more sense, but that's a personal > thing), but there's a mysql table creation command at the bottom of the docs > for creating a table for the alias_db aliases. > > Then, in your ser.cfg, load the module and everywhere you have a > lookup("aliases"), change that to alias_db_lookup("dbaliases") > > Works like a charm. Since it's not memory-resident, it's going to be slower > than the normal aliases, but not really any slower than a normal lookup in the > DB of any of the other values you're liable to be accessing. > > N. > > > > On Tue, 12 Sep 2006 10:21:56 +0100, Ricardo Carvalho wrote > >> I was expecting that Ser could be able to load some table contents >> in runtime like aliases, grp, subscriber and usr_preferences, so >> that I could use Ser in a production environment where should exist >> some Web interface for user and administrator management capable of >> altering aliases, adding or removing users, adding voicemail >> permissions, altering permissions for each user dialplan, adding >> forwarding contacts in realtime, etc. I guess I'll have to make some >> tests to see which function modules read data from DB in realtime >> and which don't. >> >> Regards, >> Ricardo. >> >> Andrey Kouprianov wrote: >> >>> Hi, >>> >>> You certainly cannot make ser accept changes made to a configuration >>> file during runtime. Take a look for instance at apache http server or >>> should i say almost any server on Linux.. None of them allows >>> accepting configurations dynamically. :) Besides, some threads in >>> this list already discussed this issue. >>> >>> As for database, Im not sure.. But what exactly are you expecting to >>> be reloaded automatically? >>> >>> >>> Andrey. >>> _______________________________________________ >>> Serusers mailing list >>> Serusers(a)lists.iptel.org >>> http://lists.iptel.org/mailman/listinfo/serusers >>> >>> >> _______________________________________________ >> Serusers mailing list >> Serusers(a)lists.iptel.org >> http://lists.iptel.org/mailman/listinfo/serusers >> > >