Hardware Phones with Software VPN and the Future of CCIE Voice v3 Product Development

Mark Snow, Voice and Security CCIE instructor/developer for IPexpert recently posted the following article on the IPexpert Blog.  Check it out below if you are a Voice candidate!

"Any of you who have been studying for your CCIE Voice for any time now, know the importance of having phones to test your calls with. In the past, with the v2 exam, this was not too much of a problem because of the wonderful product called IPBlue (the only SCCP-based softphone client on the market). With it you could test all of the needed calls, XML display functions such as Services, Softkeys, and Line appearances.

Approximately 1 year ago when we began internal preparation meetings for what we knew would become the new v3 Voice blueprint, we knew that the older 7960 phone models wouldn’t do. In fact, they are largely incapable of performing (and thus testing) approximately 25-30% of the newer functions listed in the blueprint for the v3 Voice Lab Exam (Even much more so on the SIP side of phones, but SCCP has quite a few large features as well that can’t be tested without newer model phones) (For only a partial list, take a look at the CUCM SRND pg 819). 30% is an overall huge percentage of things for you to not be able to study and test for, before reaching your actual lab exam. It’s much more than a failing percentage. So it quickly becomes obvious that this is simply an unacceptable amount of testable content for us not to cover. We would be much more than remiss in not providing you with a test platform for such testable topics, we would be dreadfully in violation of our duties to fully prepare you for the CCIE Voice 3.0 Exam. It should be noted that to date (as of this penning), none of the other vendors claiming to teach or develop for the new v3.0 Voice Lab Exam has anything except 7960 phones in their online racks and in their classrooms. We simply don’t understand how they are claiming to prepare people. The simple fact is that they are leaving out this 25-30% in their self-study workbooks and in their classroom instruction.

To that end, we decided upon, and procured long ago, newer 7962 model phones for our classrooms. We decided on 7962’s vs 7961’s simply for the fact that they can perform one additional feature that the 7961 models could not, and could be tested.

All of that brings me to this statement, for all future development IPexpert does, and all future workbooks or labs to be released (including the remainder of Volume 1 next week!!), we will focus all of our labs and testing around the 7962 phone primarily. This allows us as developers to test everything in hardware instead of software, ensuring that 100% like-functionality will occur from our labs and solutions to your actual experience sitting the CCIE Voice Lab Exam.

So the good news is two-fold:

So for item #1: IPBlue now (in this next week actually) supports the 7962 phone type! However, while that is great news, they only supports the SCCP protocol, and from the blueprint we easily see at the top that we will need to know and be able to test both the SCCP and SIP protocols for both the CUCM and CUCME cluster types.

So our layout for the 5 phones that you will need to own either in hardware or in softphone fashion to test our self-study products with are:

  • (Qty 1) Cisco 7960 IP Phone (or any other model above a 7960 for that matter) running the SCCP protocol load is needed for your PSTN site. An IPBlue VTGO-Lite softphone will suffice in the case that you don’t have a hardware phone available to you.
  • (Qty 1) Cisco 7962 IP Phone running the SIP protocol load is needed for your HQ site Phone 2 (Phone 1 is physically located back at our Proctor Labs Data Center). A Cisco CIPC softphone will suffice in the case that you don’t have a hardware phone available to you.
  • (Qty 2) Cisco 7962 IP Phones running the SCCP protocol load are needed for your BR1 site Phone 2, and BR2 site Phone 3 (BR1 Phone 1 and BR2 Phone 1 & 2 are all physically located back at our Proctor Labs Data Center. IPBlue VTGO-Lite softphones will suffice in the case that you don’t have hardware phones available to you.
  • (Qty 1) Cisco 7960 IP Phone (or any other model above a 7960 for that matter) running the SIP protocol load is needed for your BR2 site Phone 4. A Couterpath X-Lite softphone will suffice in the case that you don’t have a hardware phone available to you.
  • By the way, if you can’t procure hardware 7962 phone models, 7961’s should suffice quite well. The only thing they can’t test is the G722 protocol - which shouldn’t be too big of a problem. They do support all of the other needed features necessary to prepare you for the actual lab exam.

For item #2: Here are simple directions on how you can easily use Cisco Hardware IP Phones with your Cisco Software IPSec VPN Client:

  1. When you have a rack session (or if you simply want to test your VPN - you can use our Demo Voice vRack), using your Cisco IPSec VPN Soft Client - connect to Proctor Labs via your wireless network interface, and simply ensure that VPN works properly (that you have it setup properly - btw we give you a PCF file to import when you log into any vRack including the demo vRack), and that you can ping what you should be able to ping.
  2. Setup ICS so that your Ethernet shares your WiFi connection. Your WiFi NIC will be the one connected to the internet and thus where your Cisco VPN Client will connect to Proctor Labs through. Your Ethernet will attach either to a 802.3af powered switch which has connected to it all of your hardware phones (all in one VLAN for ease of setup); or else if you don’t have a 802.3af switch then you can connect one of the phones’ “Switch” ethernet ports directly to your laptop/desktop Ethernet port, and then daisy-chain all of the other hardware phones that you have together - making sure that phone 2’s “Switch” port connects to phone 1’s ”PC” port, and so on and so on. These can all be straight-through ethernet cables that you use. Then you will need to power all 5 phones with individual power cubes, bearing in mind that any 7960 phones (PSTN and BR2 Phone 2) only need 6.3W of juice, but that the 7962 phones will need 15.4W, so your power cube size may vary.  (Link to setup ICS on a Mac running 10.5) (Link to setup ICS on Windows Vista) (Link to setup ICS on Windows XP)
  3. From the Settings Button: Set all of your phones to Static IP Addressing, making sure that they are all on the same IP Subnet as your Mac/PC Ethernet port is statically set to, set your Default Gateway to the IP Address statically assigned to your Mac/PC Ethernet port, and then statically point TFTP to the following addresses (you do not need to turn on “Alternate TFTP” since that is only when you are running DHCP, and here you are not): Regardless of vRack (Pod) that you rent from Proctor Labs - For the 2 phones (HQ Ph2 & BR1 Ph2) pointed to the CUCM Cluster: TFTP = 10.10.210.10 ; For the 2 phones (BR2 Ph3 & BR2 Ph4) pointed to the CUCME Cluster: TFTP = 10.10.110.3 ; For the 1 phone (7960 PSTN) pointed to the PSTN Cluster: TFTP = 10.10.100.2.

That should be it. When you have your vRack session, and you have connected your Cisco VPN Client to the Proctor Labs vRack, and you have taken care of any necessary infrastructure configuration/troubleshooting steps, as well as phone configuration/MAC address changes/TFTP/CCM Services activated and running - all pointed out to you by your Lab scenario, you will now be able to register those hardware phones to your CUCM, CUCME, and PSTN CUCME respectively - no switch needed!

We hope that this blog post has been informative, and certainly welcome any comments related to either of these two topics!

Cheers,

Mark"

 

What did you think of this article?




Trackbacks
  • No trackbacks exist for this entry.
Comments
  • No comments exist for this entry.
Leave a comment

Submitted comments will be subject to moderation before being displayed.

 Enter the above security code (required)

 Name

 Email (will not be published)

 Website

Your comment is 0 characters limited to 3000 characters.