In this post we’ll learn how to install Cisco IP Communicator (CIPC) inside a virtual machine. The virtualization software we will use is Oracle VM VirtualBox.
There are two steps:
- copy CIPC installation files from the host machine to the guest virtual machine,
- install the CIPC software.
Copying installation files to the virtual machine
The Cisco IP Communicator software that I have on my host machine is a Zip file. I only need to transfer it from my host machine to the virtual machine. For this, we’ll need to build a shared folder between the host machine and VirtualBox.
Shared Folders Between Host Machine And Virtual Machine In VirtualBox
In order to allow sharing of the Cisco IP Communicator file – or any other documents- between the host machine (your physical machine) and the VirtualBox machine, I needed to mount a shared folder on a Virtual Box machine.
I installed a Windows XP machine as a Virtual box. And I need to install Cisco IP Communicator on it. I need to transfer the CIPC files from the host machine to the Virtual Box.
My CIPC files are in the following folder: Z:\CCNA Voice ; Collaboration
I’ll create a shared folder in the Virtual box. To do that, go to the menu bar of the Virtual Box and select Peripherals –> Shared folders -> Shared Folders Settings
Please note that I have a French version of Windows. But the menus are in the same place, whether it’s in French, English or even Mandarin :)
In this menu, we define the folders of the host machine that we want to display as shared folders in the Virtual Box. On the left pane, click on Shared Folders. Then on the right, click on button that says Add New Shared Folders
Type the full path of the folder you want to share. This is the path as it appears on the host machine. You’ll notice that the Folder Name field is filled automatically for you. You can leave the same name or change it.
Also, I prefer to check the three check boxes, in order to make the following settings:
- read-only shared folder
- automatic mounting of the folder
- permanent configuration of the share
I’ve named my shared folder Collab. This is the name of the shared folder that will be displayed in the Virtual Box.
Restart your Virtual Box.
Once restarted, you will see the shared folder in the My Computer window:
And yest it contains the necessary files:
Now you can manipulate the files like any normal Windows shared folder.
Installing Cisco IP Communicator
The installation is a piece of cake. You extract the Zip file and follow the steps.
Using Cisco IP Communicator to test SRST feature
You can check this nice Youtube link as an introduction to configuring Cisco SRST.
Configuration on the branch1 voice gateway:
I first used my VTGO-PC phones to experiment SRST in my home lab. They did not work when the WAN failed. So I switched for an instance of Cisco IP Communicator instead.
The mini lab I used to write this section is basically composed of:
- a voice router
- Cisco IP Communicator, or CIPC
In normal situation, I mean when the WAN link is up, the phone is registered to CUCM:
I configured the voice router for SRST. Pay attention that configuring CUCME as SRST is another thing.
In my home lab, I configured the voice router with SRST (see the Youtube link I provided above). Then I configured the emulated PSTN as a Cisco Unified Border Element. I added the four possible “allow-connections” statements.
I make sure the Emulated-PSTN router is configured as CUBE properly:
I configure an appropriate dial peer for PSTN connectivity to HQ. I configured a dial peer on BR1 router to be used when the phone is in SRST mode. This dial peer matches calls to HQ DID numbers, and routes on the Emulated PSTN.
I shut down the WAN interface on branch 1:
The phone at branch 1 gets registered to the local router in SRST:
The CIPC phone displays a meaningful message:
I make a call from branch 1 to the full PSTN number of the HQ:
When the call goes from Branch 1 to the PSTN link, the call leg matches dial peer 111 on PSTN router. Then the outbound call leg matches dial peer 1717:
I still have to properly format the calling number (from branch1) to be displayed correctly on HQ phones. I could do that with voice translation rules and profiles: