Switching to VoIP

This is the Title of the Book, eMatter Edition

Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.

186

|

Chapter 8: VoIP Readiness

example, if you can’t use SIP-only endpoints, which are fairly cheap and interopera-

ble, you could demonstrate how much more it will cost to implement the solution

using SCCP endpoints instead.

Training

How will your end users be trained? How will your system administrators—yourself

included—become familiar with the quirks of a VoIP network? Who will do the

training—an outside vendor or an internal expert? How much time will it take, and

how much will it cost?

Key Issues: VoIP Readiness

• The business environment, network environment, and implementation scenario

must be adequately prepared for VoIP in the enterprise.

• The more technical VoIP knowledge you—as an integrator—possess, the better

prepared you’ll be for VoIP.

• TCP/IP is the only packet networking protocol used on a VoIP network, though

VoIP networks are often connected by ATM.

• Enterprise VoIP guidelines vary by vendor, but the technology works best on

switched, high-speed LANs and WANs.

• Wireless Ethernet and VPN will work with VoIP, but not with the reliability of

switched Ethernet.

• VoIP can bring businesses gains of efficiency, productivity, and lower costs.

• Applying a cost-benefit assessment user-by-user or department-by-department is

a good way to see which workgroups in your company