I am using 0.9.6 Regards Kamal Mann ________________________________ From: sip [mailto:sip@arcdiv.com] Sent: Tuesday, September 26, 2006 4:31 PM To: Mann, Kamal; Serusers(a)lists.iptel.org Cc: serusers-bounces(a)lists.iptel.org Subject: Re: [Serusers] Database description What version of SER? N. On Tue, 26 Sep 2006 12:40:05 +0200, Kamal.Mann wrote why each table is populated. This will enable me to make projections on how much data will be stored in the database in the coming days & what is the use of each n every table. Is there any current discussion going in or any document??

Hi, Can somebody tell me how to configure SER to support for ipv6.I am using ser version 0.9.x. Regards, Jayasree ----- Original Message ----- From: sip To: Kamal.Mann(a)t-systems.com ; Serusers(a)lists.iptel.org Cc: serusers-bounces(a)lists.iptel.org Sent: Tuesday, September 26, 2006 4:31 PM Subject: Re: [Serusers] Database description What version of SER? N. On Tue, 26 Sep 2006 12:40:05 +0200, Kamal.Mann wrote ------------------------------------------------------------------------------ _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail immediately and permanently delete the message and any attachments.

Fast overview....of SER's tables: *acc* acounting purpouses. If you are using acc modules, transactions will be logged here. *active_sessions* used by SERWEB to know current active sessions, not sure if it's populated via acc *admin_privileges* used by SERWEB to set permissions to the web interface *aliases* used by the lookup("aliases") call and usually populated via serctl. It contains the aliases :P *calls_forwarding* Not sure but used by SERWEB(?) when you configure call forward... *config* SERWEB stuff *domain* Table used in multi-domain setups since it contains the domains that will return true for the calls of the module domain. *event* ????SERWEB *grp* Table used in the is_user_in calls to check which groups the users belogns to. *location* table containing the current maping of the registrar module, which stores here the entries with save() config calls. *missed_calls* acc logs here missed calls to be shown via SERWEB *pending* acc logs here pending calls to be shown via SERWEB *phonebook* SERWEB stuff. Used whenever users set their phonebook via the web interface... *preferences_types* ???? *reserved* ?????? *server_monitoring* SERWEB *server_monitoring_agg* SERWEB *silo* table storing IM for non-registered users... *speed_dial* table containing the speeddial module mapings. Required for sd_lookup() calls. It can be populated via SERWEB. *subscriber* Table containing "customers" (username/password) used in auth_db calls such as {www|proxy}_authorize. Populated via serctl|SERWEB *trusted* Table containing the "IPs" which SER setup has to trust. Used by permission module, this table is required for allow_trusted and so calls.. *uri* Used by the uri_db module...check_to() and related.. *usr_preferences* apv_ops module *version* Internal SER table containg the version of the rest of tables to avoid incompatibility problems between different SER versions and DB backends.. Hope someone can confirm what I've written and expand the info... Samuel. 2006/10/3, Nick Hoffman <nick.hoffman(a)voxpak.com>om>: