Jack,
I have a limited knowledge of how to do it, because I have worked with Cisco techs and watched them do it, and I work with them remotely all the time, and I have a pretty good understanding of how it works. I think I mentioned in the past that I handle PBX's on large offshore drilling rigs. We do Packet based (Eithernet)connections to the rigs, voice and data, the voice is dropped to a T-1 or analog interface on the router (depending)and then into the PBX.
IP/Eithernet voice communications works just like the Internet. Basically it works like sending a letter, You have a receptient address and a sender address on the envelope (packet), You hand that off, it goes to a distribution center (router), it is then loaded on a carrier (internet- Satelite,etc.)then sent to another distribution center (far-end router),delivered to the receptient (T-1 interface), which then opens/reads the letter, acts on the information contained,ie: causes a phone to ring! Everything is contained in the packets!
Cisco routers are accessed via telnet over IP remotely, or a craft interface locally( all password protected, of course).
The interface is like using the old MS-DOS, Unix, or Linux, or in your case "Monitor". You have to know the command structure like "show Interface" and then be able to understand and act upon what you see.
The testing capabilities are in the software of the router, you just need a tech that understands it, and knows how to use it. Same for Programming, too!
It is not something you could could learn in a "Cisco for Dummies" or "Legend/Magic for Dummies" book (if there were any).
Now, you must excuse me, I have to get up at 3 am. to catch a bird to go 150 miles out in the Gulf, A Legend Processor died today, and I have to go perform CPR.
