My advice is that this isn't something for the faint of heart. The resident IT guy is just as uninformed as you are. They want it, and in many cases they insist upon it, but they don't have a clue. This is such a massive undertaking for a situation the size of yours, Rhonda. I know that you are trying to do the right thing in helping out, but this is a situation that is way over your and your boss' head. There are more variables than Wisconsin has cheese.
I've been known to bash IP, but only because the people who are hocking it are perhaps the least qualified to understand how the telephone industry works. This big 'savings' is quickly dissolved when the resident rocket scientist who installs it has all of your local calls going out of Galveston, TX. Until two months go by, and when you get the bill for massive long distance calling, you assume that all is good. That genius gets fired for his dyslexic entry of your local area code, yet you get stuck with getting it resolved.
Please, please, please don't take any responsibility for this project. IP networking basically puts a local CG in the position of understanding inter-office and national/international toll issues. I really doubt that they understand this part of the equation. I guarantee that if they are successful in achieving dial tone at a distant station that they consider it to be a success.
That is my advice, albeit not what you wanted to hear.
