 that you've answered a call, but it's for Barbie Browneyes in Marketing. You've been looking for an excuse to talk to her for months, and here is your chance. You forward the call to her extension, she answers the phone, and you exchange pleasantries. After listening to her angelic voice for a bit, you tell her that you have a call for her. When you hang up, the original call is transferred to her extension. You've introduced the caller to her with your soothing baritone, prac- tically guaranteeing another conversation with Barbie the next time you meet. You may also hear this referred to as an announced, attended, or warm transfer. In our telephony configuration, we have the following options: 1-PBX(config-telephony)#transfer-system ? blind Perform blind call transfers (without consultation) with single phone line using Cisco proprietary method full-blind Perform call transfers without consultation using H.450.2 or SIP REFER standard methods full-consult Perform H.450.2/SIP call transfers with consultation using second phone line if available, fallback to full-blind if second line unavailable. This is the recommended mode for most systems. See also 'supplementary-service' commands under 'voice service voip' and dial-peer. local-consult Perform call transfers with local consultation using second phone line if available, fallback to blind for non-local consultation/transfer target. Uses Cisco proprietary method. I tend to like the full-consult method because it behaves the way that most users expect it to. Yeah, sometimes you have to talk to the Doodleputzes of the world, but it's worth it in the long run when you have to forward a call to Barbie: Small-Office VolP Example R1-PBX(config-telephony)#transfer-system full-consult Dial Plan Dial plans can be simple, or they can be ridiculously complicated. Try to keep yours as simple and as logical as possible. This example will be very simple, since I have only four phones. Each user will have an extension, numbered from 101 upward. Since there are only four people i