From: Matthew J. D. <mda...@se...> - 2003-07-14 19:53:55
|
Vince, This will be my first Debian install, I am in the process of downloading the seven install disks and the one update disk. Should I install everything? The debian book I got talks about having to manually mounting the CD-ROM during install. Anyone have any advice? -Matt |
From: Vince H. <lu...@ml...> - 2003-07-14 20:01:42
|
On Mon, Jul 14, 2003 at 09:53:53AM -1000, Matthew John Darnell wrote: > This will be my first Debian install, I am in the process of > downloading the seven install disks and the one update disk. > > Should I install everything? No. You only need to download/install the 1st (Woody) CD. > The debian book I got talks about having to manually mounting > the CD-ROM during install. Nope. Read http://www.debian.org/releases/stable/installmanual. > Anyone have any advice? Forget all the bad habits you picked up from using Red Hat. :) With compatible hardware, I can get a debian installation net accessible within 15 minutes and another 15 minutes to upgrade it all from stable to testing. -Vince |
From: Kevin E. <ke...@en...> - 2003-07-15 01:55:53
Attachments:
voicemail.sql
|
Ok, attached (and included in case u have problems with my attachment) is a very crude but basic sql schema for a voicemail system. I'm sure there's a million little details we need to add.... My ideas for the 'object model' are at this point pretty abstarct. Basically the way I see it is you have a menu object which is intialized with an instance of the ctserver. Each instance of the menu requires some kind kind of user (the default user being "Outside Caller"), each user has certain permission which we define. The user may navigate around the menu and will be given options that coorespond to his permissions. the tree structure of the menu would be best represented by some kind XML document that can be customized via a web interface. If i had to make objects right now, i would make the following: Voicemail::Menu -- controls navigation thru voicemail menu system Voicemail::User -- represents a user, an instance of this will be used in every instance of the Voicemail::Menu object. Voicemail::Permissions -- permission verifier Voicemail::DB -- db functions what do u guys think? when will that box be outside the firewall so we can start messing around with it.... k voicemail.sql --------------------- DROP TABLE IF EXISTS VM_Users ; -- the Vm_USERs table, holds basic info about a user CREATE TABLE VM_Users ( user_id integer auto_increment primary key, first_name varchar(100) not null, -- basic name info last_name varchar(100) not null, mi varchar(1) null, active smallint not null default 0, -- active user in the system department_id integer not null, permission_id integer not null , phone_keys integer null -- phone keys for 'lookup' feature... ) auto_increment = 100; DROP TABLE IF EXISTS VM_Greetings ; -- the VM_Greetings table, holds info about user's greetings.... CREATE TABLE VM_Greetings ( greeting_id integer auto_increment primary key , user_id integer not null, default_greeting smallint not null, greeting_wav_path varchar(200) not null ) auto_increment = 5001; DROP TABLE IF EXISTS VM_Departments ; -- the VM_Greetings table, holds info about departments.... create table VM_Departments ( department_id integer auto_increment primary key, department_name varchar(100) not null , default_user_id integer not null , -- who's mail box will it go to if it's a general inquiry? department_desc_wav_path varchar(200) ) auto_increment = 701; DROP TABLE IF EXISTS VM_Messages ; -- the VM_Messages table, holds info about all messages in the system Create table VM_Messages ( message_id integer auto_increment primary key, message_timestamp DATE not null, user_id_to integer not null , -- who's the message for? user_id_from integer not null, -- who sent the message message_wav_path integer not null, -- where is the message on the server saved_message integer not null -- is this a saved message? ) auto_increment = 10001 ; DROP TABLE IF EXISTS VM_Permissions ; -- the VM_Permissions table, holds info about User permissions Create table VM_Permissions ( permission_id integer auto_increment primary key, permission_desc varchar(200) not null ) auto_increment = 1 ; -- sample data.... -- first, the departments... INSERT INTO VM_Departments ( department_id, department_name, default_user_id , department_desc_wav_path ) values (0, 'Marketing', 0, '/var/data/makerting.wav'); -- makes department id 701 INSERT INTO VM_Departments ( department_id, department_name, default_user_id , department_desc_wav_path ) values (0, 'Tech Support', 0, '/var/data/techsupport.wav'); -- makes department id 702 INSERT INTO VM_Departments ( department_id, department_name, default_user_id , department_desc_wav_path ) values (0, 'Accounting', 0, '/var/data/accocunting.wav'); -- makes department id 703 INSERT INTO VM_Departments ( department_id, department_name, default_user_id , department_desc_wav_path ) values (0, 'Information Technology', 0, '/var/data/it.wav'); -- makes department id 703 -- let's see em SELECT * FROM VM_Departments ; -- now, how bout some permissions... INSERT INTO VM_Permissions VALUES (0, 'Annonymous/Outside Caller Permissions'); INSERT INTO VM_Permissions VALUES (0, 'Regular User Permissions'); -- permission level 2 INSERT INTO VM_Permissions VALUES (0, 'Super User Permissions'); -- permission level 3 -- let's see em SELECT * FROM VM_Permissions ; INSERT INTO VM_Users ( user_id , first_name, last_name , mi, active, department_id, permission_id, phone_keys ) VALUES (0,'Outside', 'Caller',null, 1,0,1,null); -- this is the outside caller, he'll be user_id 100 INSERT INTO VM_Users ( user_id , first_name, last_name , mi, active, department_id, permission_id, phone_keys ) VALUES (0,'Joe', 'Marketing','W', 1,701,2,627); -- marketing guy INSERT INTO VM_Users ( user_id , first_name, last_name , mi, active, department_id, permission_id, phone_keys ) VALUES (0,'Joe', 'Techsupport','W', 1,701,2,823); -- tech support genius INSERT INTO VM_Users ( user_id , first_name, last_name , mi, active, department_id, permission_id, phone_keys ) VALUES (0,'Joe', 'Accounting','W', 1,701,2,222); -- Number cruncher INSERT INTO VM_Users ( user_id , first_name, last_name , mi, active, department_id, permission_id, phone_keys ) VALUES (0,'Joe', 'InfoTech','W', 1,701,3,222); -- the IT Guru, with higher permissions SELECT * FROM VM_Users; |
From: Matthew J. D. <mda...@se...> - 2003-07-15 02:33:32
|
> Ok, attached (and included in case u have problems with my attachment) is > a very crude but basic sql schema for a voicemail system. I'm sure > there's a million little details we need to add.... > My ideas for the 'object model' are at this point pretty abstarct. > Basically the way I see it is you have a menu object which is intialized > with an instance of the ctserver. Each instance of the menu requires > some kind kind of user (the default user being "Outside Caller"), each > user has certain permission which we define. The user may navigate > around the menu and will be given options that coorespond to his > permissions. the tree structure of the menu would be best represented by > some kind XML document that can be customized via a web interface. > If i had to make objects right now, i would make the following: > > Voicemail::Menu -- controls navigation thru voicemail menu system > Voicemail::User -- represents a user, an instance of this will be used > in every instance of the Voicemail::Menu object. > Voicemail::Permissions -- permission verifier > Voicemail::DB -- db functions > > what do u guys think? when will that box be outside the firewall so we can > start messing around with it.... Kevin, I don't understand most of this, but from what I can make out it looks like a great start! I like it because it should allow us to easily change what each key does. This makes adapting to different voicemails much easier. My only reservation is that we might be biting off more than we can chew. It would be good to "do it right the first time" but I would hate for this project to die under its own weight. I can't imagine a team with more complimentary skills than we have! We will put the box outside the firewall with direct numbers on Wednesday.(I can't find a fast mirror and am still downloading the first Debian CD !?!?!) Makes me appriciate Videl. -Matt |
From: Kevin E. <ke...@en...> - 2003-07-15 07:01:19
|
yeah, i agree we shouldn't throw too much in the first version, probably, like u said, hard code a lot of things. we should probably keep the option of an XML customizable menu system til we get everything else working. Here's another thing to consider. Remember how we were looking at the web interface for that Notrel Networks voice mail system? what fields do they have there? my fields are just things i can think of. i can already see stuff i missed, like extension. k > > >> Ok, attached (and included in case u have problems with my attachment) >> is a very crude but basic sql schema for a voicemail system. I'm >> sure there's a million little details we need to add.... >> My ideas for the 'object model' are at this point pretty abstarct. >> Basically the way I see it is you have a menu object which is >> intialized with an instance of the ctserver. Each instance of the menu >> requires some kind kind of user (the default user being "Outside >> Caller"), each user has certain permission which we define. The user >> may navigate around the menu and will be given options that coorespond >> to his permissions. the tree structure of the menu would be best >> represented by some kind XML document that can be customized via a web >> interface. >> If i had to make objects right now, i would make the following: >> >> Voicemail::Menu -- controls navigation thru voicemail menu system >> Voicemail::User -- represents a user, an instance of this will be >> used >> in every instance of the Voicemail::Menu object. >> Voicemail::Permissions -- permission verifier >> Voicemail::DB -- db functions >> >> what do u guys think? when will that box be outside the firewall so we >> can start messing around with it.... > > Kevin, > > I don't understand most of this, but from what I can make out it looks > like a great start! > > I like it because it should allow us to easily change what each key > does. This makes adapting to different voicemails much easier. > > My only reservation is that we might be biting off more than we can > chew. It would be good to "do it right the first time" but I would hate > for this project to die under its own weight. > > I can't imagine a team with more complimentary skills than we have! > > We will put the box outside the firewall with direct numbers on > Wednesday.(I can't find a fast mirror and am still downloading the first > Debian CD !?!?!) Makes me appriciate Videl. > > -Matt > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Parasoft > Error proof Web apps, automate testing & more. > Download & eval WebKing and get a free book. > www.parasoft.com/bulletproofapps1 > _______________________________________________ > Linuxvm-developer mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxvm-developer |
From: Matthew J. D. <mda...@se...> - 2003-07-15 07:56:56
|
> yeah, i agree we shouldn't throw too much in the first version, probably, > like u said, hard code a lot of things. we should probably keep the option > of an XML customizable menu system til we get everything else working. > Here's another thing to consider. Remember how we were looking at the web > interface for that Notrel Networks voice mail system? what fields do they > have there? my fields are just things i can think of. i can already see > stuff i missed, like extension. If you look at the field_names_v2.csv from this page https://sourceforge.net/project/showfiles.php?group_id=59878 you can see the ones I came up with. What were you thinking about when you had department? That is a good field to have when you have a multi tennant system (more than one company sharing the same voiecmail) -Matt |
From: Vince H. <li...@ml...> - 2003-07-15 08:20:01
|
On Mon, Jul 14, 2003 at 09:56:55PM -1000, Matthew John Darnell wrote: > What were you thinking about when you had department? That is a > good field to have when you have a multi tennant system (more > than one company sharing the same voiecmail) Well, that could be a company field. -Vince |
From: Vince H. <li...@ml...> - 2003-07-15 08:29:20
|
On Mon, Jul 14, 2003 at 09:06:59PM -1000, Kevin English wrote: > yeah, i agree we shouldn't throw too much in the first version, probably, > like u said, hard code a lot of things. we should probably keep the option > of an XML customizable menu system til we get everything else working. > Here's another thing to consider. Remember how we were looking at the web > interface for that Notrel Networks voice mail system? what fields do they > have there? my fields are just things i can think of. i can already see > stuff i missed, like extension. You are going to have to sell me on having the configuration be in XML format. A minimalist approach is to store the configuration in a global hash. -Vince |