Steps to VoIP success: Considerations for a premise-based VoIP product

Opinion
Sep 13, 20062 mins

* Sage advice from a hosted VoIP provider

Picking up where we left off last time with VoIP deployment advice from Dan Hoffman, president and CEO of hosted VoIP provider M5 Networks, today we’ll pass on his thoughts on what to consider when evaluating a premise-based VoIP product, such as an IP-PBX or a VoIP-enabled router.

First, Hoffman recommends that the “people readiness” assessment for a premise-based product (which should accompany the requisite network readiness assessment) needs to consider how the company staff will manage the voice application, servers, hardware and software updates, and the requisite security updates.

Second, he advises those considering an IP-PBX or similar hardware to make sure the phone equipment and management systems are compatible with their data network equipment.

Third, Hoffman suggests that potential buyers should make sure the product is “bullet-proof” by checking the reliability of the hardware and software features. His bias is against “PC-based” hardware, operating system or applications software that isn’t specified or supplied by an experienced telecom equipment supplier unless the telecom manager is comfortable with managing all the pitfalls that a PC architecture can bring.

Finally, he recommends that potential buyers understand the scope of the project that brings VoIP into the office. For example, the business case and project plans should account for:

* The time needed to manage a cut-over from legacy to VoIP systems.

* The daily job of system administration.

* Being the prime point of contact for solving carrier facilities issues.

* User training.

* How to make sure the appropriate directory assistance and 911 requirements are met.

* Defining how the more advanced VoIP features will be designed and deployed, including time for user and support staff training.

After all, Hoffman observes (and we agree) – voice isn’t just another data application.