|
|
||||||||||||||||||||
| Home > VoIP models and services: Complete guide | |
| Learning Guide: |
|
||
Table of contents:
VoIP: Getting down to basics With traditional (layer 2) voice, each location had to have its own PBX or key system and voice services were tied to that location. Every time a user moved, an administrator had to come in and reconfigure the PBX to move it around. Users were tied to specific desks. At the IP layer (layer 3), the call control or IP PBX, can live anywhere on the network. The IP PBX can be across the office, across town or across the globe, very much like any other client-server application. Also, since it operates at the IP layer, companies can use their data network or even the Internet to transmit voice, avoiding the toll charges that exist on today's PSTN. There are both benefits and challenges to VoIP (see below); however, the more VoIP evolves, the benefits will start to outweigh the challenges.
Benefits:
Challenges:
VoIP training, testing and budgeting Historically, voice and data have existed on two separate networks. With an IP network, voice and data coexist on the same network, thus increasing the management complexity. Introducing richer, bandwidth-draining applications only convolutes matters more. It means that telecom managers have to learn how data networks function and network managers will need to become familiar with telcomm operations. For this reason, training should be a big part of the overall implementation. A migration process will need to be put in place, and most importantly, a training budget needs to be established. One of the most common mistakes organizations make is not budgeting in everything from the beginning to end of deployment. Before many IT organizations deploying VoIP realize, the cost of implementation has spiraled beyond their initial budget. Another crucial error made in many implementations is the lack of pre-assessment testing. Many have underestimated the importance of testing and have paid for it by having to fix problems in a production environment, which is much more expensive than troubleshooting in pre-production. Actively testing the service, voice quality and equipment can save managers a great deal of headaches and downtime. Testing must be done in the pre-assessment stage, and should also be viewed as an on-going procedure throughout the deployment.
Types of VoIP
Hosted VoIP Hosted services normally have fewer features than an enterprise class IP PBX. Most enterprise vendors build their solutions based on a standard called SIP (session initiation protocol), and then add new features by creating proprietary extensions. Because a softswitch hosts voice for multiple companies, the vendors normally follow the SIP standard exclusively meaning that they will lack the proprietary, pre-standard features. The majorities of service providers today provide a hosted VoIP service offering for those businesses who do not want to deal with the challenges of managing an IP PBX system and leave that to their service providers.
Managed VoIP One of the many challenges still surrounding managed services is security. Many businesses are still not comfortable handing all control over to their service provider. Another challenge that has emerged recently is the complexity of managing several different providers. Forty-two percent of enterprises prefer to consolidate their vendors, which would provide a single point of contact or a single "throat to choke" in the event of a failure. Enterprises looking to implement managed VoIP should look to service providers who are partnered with systems integrators that can provide a single point of contact.
Pure IP PBX The downside of deploying an IP PBX is that the systems need to be "hot cut" over (moving from the legacy PBX to the IP PBX with no significant loss of service). Interoperability between the old system and the new system is often a problem. An example: users are often unable to forward voice mails from a traditional PBX from one vendor to an IP PBX from another manufacturer.
Hybrid IP PBX While in concept, hybrid does seem appealing, it can lengthen the migration cycle. Hybrid requires touching every PBX, and when the company wants to move to a pure IP system, it requires visiting every location again. In essence, companies would do twice the amount of work of moving to a pure IP system. Also, most hybrid systems do not provide the same level of application integration as a pure IP system.
VoIP deployment models
Managed IP PBX
Hybrid IP
Other VoIP business models To be competitive in the market, Skype has been seeking partnerships for a comprehensive security solution that can provide a more appealing product for enterprise markets. While Skype still has a long way to go to play competitively in the enterprise market, it certainly has the means to do so at a rapid pace.
Vonage
Yahoo
Jajah Selecting the right VoIP model When assessing which one of these models to go with, first you have to assess the real needs of the business.
Any one of the traditional IP PBX equipment vendors can help guide you in choosing the right solution for your business. Cisco, Avaya, Nortel, 3COM and Mitel all have comprehensive VoIP solutions tailored for the enterprise market. These vendors partner with the systems integrators who help to deploy and manage these networks. However, traditional equipment vendors are not the only players in this sandbox anymore. Emerging players such as Skype, Vonage, Yahoo and Jajah all provide alternatives to traditional voice services. While these vendors sell mostly to the consumer market, it's just a matter of time before they begin to make traction in the enterprise.
Deploying VoIP: Five things every CIO should know
About the author: Before joining Yankee Group, Kerravala was a senior engineer and technical project manager for Greenwich Technology Partners, a leading network infrastructure and engineering consulting firm. Prior to that, he was a vice president of IT for Ferris, Baker Watts, a mid-Atlantic based brokerage firm, acting as both a lead engineer and project manager deploying corporate-wide technical solutions to support the firm's business units. Kerravala's first task at FBW was to roll out a new frame relay infrastructure with connections to branch offices, service providers, vendors and the stock exchange. Kerravala was also an engineer and technical project manager for Alex. Brown & Sons, responsible for the technology related to the equity trading desks. Kerravala obtained a B.S. degree in physics and mathematics from the University of Victoria (Canada). He is also certified by Citrix and NetScout.
'); // -->
|
|
|||||||||||||||||||||||||
| About Us | Contact Us | For Advertisers | For Business Partners | Site Index | RSS |
|
|
|
|||||||