hacks:open_telco
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
Previous revision | |||
— | hacks:open_telco [2015/12/12 14:31] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | =====Direction===== | ||
+ | Because of our creative user base we could design our telco around a knowledge sharing model.. All users have access to the core configuration code and overall system workflow. | ||
+ | * Open/ | ||
+ | * Percentage Based Fees, each user pays for their percentage of the overall system | ||
+ | * Full featured. | ||
+ | |||
+ | For software I am leaning towards freeswitch, which is threaded, easily cluster-able, | ||
+ | |||
+ | =====Current Development? | ||
+ | We have a Core 2, 2GB ram, ~10mbs / 4000GB transfer todo development on. It is currently running freeswitch-svn(1.5pre? | ||
+ | |||
+ | ==== Tasks ==== | ||
+ | feel you want to bring something to the table? commit to learning/ | ||
+ | |||
+ | * Understanding The basics of extension and voicemail configuration - ooze | ||
+ | * maintaining a running/ | ||
+ | | ||
+ | =====Future Development? | ||
+ | There are some initial things that should be in place before we commit to bulk ordering voip services | ||
+ | * Ability to easily add users.. shell script? web interface? | ||
+ | * Ability to formulate channel(voip line) usage statistics (per user percentage of system use) | ||
+ | * Ticket system / Bug Tracker for usage issues? | ||
+ | |||
+ | |||
+ | |||
+ | =====Security Questions===== | ||
+ | if it's an open system and any member can theoretically modify it, would there be a need for precautions to make sure no one inserted anything malicious, such as a data tracking or recording function? |
hacks/open_telco.txt · Last modified: 2015/12/12 14:31 by 127.0.0.1