Has anyone considered the idea of splitting the sip registration information in a realtime database from the actual configuration of the peers?
I mean, instead of having a table full of the configuration information (i.e. name, regexten, secret, etc) and registration information (i.e. ipaddr, fullcontact, etc), you have separate tables with their own information. This way, you can have separate tables with config information, and use a view for the actual compiled configuration, instead of how it is now, where there may be repeating info all over the database. Does any of that make sense? -- Aaron Daniel
signature.asc
Description: OpenPGP digital signature
_______________________________________________ --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
