On Sun, 2004-02-29 at 09:18, Olle E. Johansson wrote: > > Olle's chan_sip2 introduces a 3rd possibility: > > Using templates & autocreate peers for the majority of user options & > > storing just the passwords in the MYSQL database. > Combining this with MYSQL_FRIENDS, storing template= settings in a database > would be very powerful.
funnily enough, the application I'm writing at the moment has template= in the database :) However, I still need more per-user settings than is possible with MySQL_FRIENDS My own list of things that I need storing per user: extension shortname (for a mapping.conf that redirects [EMAIL PROTECTED] to an extension) fullname (for CallerID) email (for voicemail) accountcode pickupgroup template language calldiversion dnd Note that mapping.conf & calldiversion/dnd need to modify files #included within extensions.conf as well as the user definitions. So I'd need a MYSQL_EXTENSIONS kind of functionality as well :/ All seems to be working nicely now, but I'm worried about getting time to 'restart when convenient' on a busy system - users won't want their calldiversion/dnd settings to only take effect overnight. I guess I need to implement this with astdb instead of MySQL, since this can be queried direct within the dialplan. Would be lovely to have dbget/dbput routines for MySQL as well as just db1! Fran. _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users