Voice Over Internet Protocol (VoIP)
By Mike Dailey
The convergence of voice and data has created an opportunity to optimize existing networks. Voice Over Internet Protocol (VoIP) or "voice over anything" is a byproduct of the shift toward combined voice and data transport. Does all of this convergence of voice and data sound familiar? In 1988 I had an opportunity as the VP of Telecommunication for a major retailer to be the driving force in creating a very large national fast packet T1 converged voice and data network. In its time, it was the largest fast packet T1 network of its type in the world. In the early 90s a major carrier began using the same technology as a frame relay offering. This direction validated my decision to invest in packet switched technology rather than the less efficient circuit switched T1 multiplexers. The merging of voice and data worked then for the same reason that "voice over anything" is attractive today -- Moving voice and data together in packets can be an efficient transmission medium.
Here are some questions to consider when deciding if creating a VoIP or "voice over anything" converged network is the right direction for your organization:
- In which areas do you want to apply the convergence of voice and data technology, e.g. telephones, network or switching systems?
- Would a virtual single PBX system serving many locations connected by VoIP networking be a benefit?
- Will convergence of voice and data technology provide new "added value" network capabilities or just network cost savings, e.g. computer telephony integration (CTI), virtual single system?
- What is the voice calling pattern in your organization? Are the call volumes between the network points large enough to support the VoIP investment?
- What is your current cost per minute for long distance and what will it be in a few years? How do you think this technology will impact the ability of carriers to offer much lower long distance rates in the future?
- Does your organization’s long distance voice contracts have minimum volume commitments and what will your cost be if you move some call volume to the IP network?
- Are your calls always point-to-point or do they need to be switched to multiple locations?
- What equipment needs to be added to the telephone systems for network interface?
- Does your existing IP network have quality of service (QoS) and policy controls to protect voice call quality?
- Can the voice equipment at each location determine the QoS before call setup and during calls?
- How secure are the WANs and LANs. Are they protected to prevent denial of service attacks and other network security problems?
- How secure are the computers and servers on the network? Are they protected to prevent computer worms and other disabling actions?
- What type of backup network connections will be needed?
- How will the system access the backup network before call setup and during calls?
- How will the system function in the backup mode?
- How transparent will the backup mode be to end users?
- What happens to the dialing plan in backup mode?
- How much IP network bandwidth will be needed to support the voice calls?
- What level of voice quality is required for your application?
- What IP voice compression standards are required?
- Does your network need dedicated and prioritized Permanent Virtual Connections (PVC) to support voice connections?
- What does the impact of music on hold for ACD queuing and other functions have on the proposed network?
- How does the system support analog devices, e.g. modems and fax machines?
- Will existing analog device locations and wall phones need new wiring?
- How does the interface for overhead voice paging work and how is the voice quality?
- What is needed in the network to support E911 service?
- Does the proposed IP PBX or IP telephone solution have all the telephony features you need to operate your business?
- If you currently have a high end PBX system, what are the challenges to translate the existing PBX functions to the VoIP solution?
- If you currently use call center functions, what are the challenges to translate the existing functions and call center reporting to the VoIP solution?
- How will the VoIP system be supported during power outages? Is there a central way to provide (UPS) Uninterrupted Power Supply or will the UPS system need to be distributed throughout the system, e.g. servers, wiring closets, PCs. Traditional PBX systems usually have four to eight hours of UPS and are often connected to the building emergency generator system.
- If the system is being proposed as a "turn key" system how much of the installation and training work will the vendor do?
If you require assistance with implementation of VoIP, please contact Mike or Pam Dailey at (770) 458-3411 or email pdailey@tectelsolutions.com
Note: All information contained in this article is the property of TecTel Solutions, and may not be reproduced in part or whole without thee express permission of a TecTel Solutions' Principal.