This is the flip side of the coin–the other half of IP telephony and the systems administration dilemma. It’s for the guys like me who enter the arena knowing how to configure, operate and administer a server, with some server-level operating system on it, and who are handy with the tools of that OS. We are adept at building open-source software from the C source files and issuing commands to run the software. It’s for those of us who arrogantly look at software like Asterisk or FreeSWITCH and think, “Piece of cake. Install the build tools,
make, edit a config file and done! I’ve done it a million times!”
- the whole realm of telephony hardware, including endpoints and interfaces to analog and digital telephone networks;
- networking protocols, including some fairly complicated quality-of-service configurations and NAT/firewall workarounds if you’re in such an environment;
- phone company lingo, so that you can order the right service from a provider to connect you to the outside world;
- technical voice services areas like call routing and dial plans, so that your phone system is actually usable (by your business or family);
- business functions, so that you can get the call records into the hands of the people who are going to charge the users for their usage.
And, because I am sure I am forgetting a number of other areas, I’ll tack on “and much more.”