ll be endpoints (phones), a PBX (UCM, Call Manager, or the express versions of these products), and probably voicemail (Cisco Unity). In this chapter, we'll be building the design shown in Figure 30-1. This IP phone system is designed for the needs of the office of a small but successful consulting company. Any similarities to companies or persons either living or dead are purely coincidental. There are almost limitless ways in which an IP phone system can be configured. In this chapter, I will show you one way of doing things, but you can likely accomplish the same goal using different methods. As long as the client's needs are met and there are no vulnerabilities or shortcomings, the way that works is the right way. While there are cer- tainly best practices, when it comes to topics like dial plans, dial peers, and features required, every installation is different. Phone#: 1 Model: 7971G Internet User: GAD Ext: 101 Phone#: 2 Model: 7970G G1/0/1 User: Lauren Ext: 102 2811 w/CME G1/0/2 Phone#: 3 G1/0/10 G1/0/3 Model: 7960G User: Meghan Voice port 0/1/0 G1/014 Ext: 103 Phone#: 4 Model: 7970G User: Colleen Ext: 104 Figure 30-1. Small-office Cisco CME VoIP deployment I'm going to build a small-office IP telephony solution using a Cisco 2811 router. Within the router, I have UCM Express, a Cisco Unity Express AIM card (AIM-CUE), and a four-port FXO card to connect to the POTS lines. There is also a PVDM2-48 for CO- DEC conversion, but it is not needed for the design shown here. For phones, I am using a Cisco7971G, two Cisco 7970Gs, and a Cisco 7960G. The phones connect to the network via a Cisco 3750 PoE switch. Chapter 30: VolP If you're building a VoIP solution in your lab, the phones don't matter much, but if you're designing one for a customer, the phones are ev- erything. Remember, the user experiences the phone system through the phone. If the phone sucks, the system sucks as far as the customer is concerned. Little things like a backlit display and backlit line buttons make a huge difference when it comes to 