Must be an early spring coming, stuff just keeps coming to mind.
I would like to see something similar to design patterns in software for
telephony. It would be a collection of common scenarios, and how to
implement them in various softswitches. Is there a spot for this already?
For example, I was considering my home system again, and how it's in fact
_very_ annoying to have extensions, and what I really want is a key
system. The "pattern" I'd like to implement is:
1) Support for simultaneous calling; max N lines (where N is likely 3
for my home)
2) Shared line appearance / single button support for "barging" in on a
call when passing it over to someone else; none of this putting the
call on hold first, or transferring to another extension. I want zero
button warm transfers.
3) Elimination of the infinite missed calls
After writing this, I'm realizing this is probably Jim & Leif's "Asterisk
Cookbook" -- but I still want a searchable wiki, and I want vanilla
asterisk, FreePBX/Trixbox/Elastix, FreeSWITCH, and Yate. And a pony.
--
| It ain't what you don't know that gets you into trouble. It's what
| you know for sure that just ain't so. -- Mark Twain
|
| Network: http://www.linkedin.com/in/spditner
| http://facebook.com/people/Simon-P-Ditner/776370031
| http://twitter.com/spditner
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
