Hi everyone! I have decided that I ought to fully document our Inter-Tel configuration. This comes partly as a response to a sense that I need to re-orient myself to how it's configured every time I do anything. I'm no phone tech (as my previous postings no doubt make painfully obvious) so I lack the type of background that would permit simply looking at DB Studio and "just knowing" how it works. There is strong likelihood I can offload the responsiblity to our IT department, but not by just tossing it over the wall. Everyone over there knows less about it than I do, and it's our lifeblood, because we do phone support for our customers. But it really is outside of the career direction I am trying to go, so its somewhat of a ball and chain for me. We do have a tech we use whenever the changes we need are more complicated than I'm capable of handling, but I have to be the interface to him. The IT department wisely won't take this beast on, unless the handoff is clean, because everything about it is outside their current expertise and we're alway short-handed. I don't blame them, if I'd realized what I was in for when it first became mine, I might have said the same!
That said, does anyone have any recommendations for how to document what's built in the DB Studio so that it doesn't require a phone tech to understand it, but wouldn't give a phone tech fits just looking at it?
We have lots of STAR stuff, and day/night mode done by STAR, and IP phones, and applications that route incoming calls through a series of hunt groups before dumping in voicemails which are routed to email. We have emergency overnight services that use Cascades to route the notification.
:read: <-- that's me, offering a complete document on this to my IT department.
This is them, telling me what they think of taking this over right now
I thought I'd begin really simply with a list of hardware components we have, then the available information sources on the thing (where are the user manuals, where does the software live, and finally sneak up on explaining how the thing actually is configured to work and fill that section with a liberal supply of screen shots.
Any better ideas for documenting the DESIGN of the implementation?
