CCIE Voice Adventure begins…

So I have been delaying this for some time now. After a long talk I had with one of my friends I came to realize there’s really no reason why I should not start now.

After my mom surgery and my financial wreak I have realigned some priorities.  It’s going to be hard to work along some other responsibilities, like going back to College, VOZCO, and work but we will build up on intensity.

I don’t have any lab budget either at this time, but I’ll try to make the best with no financing for the first couple of months.

You may want to check the following link. I’ll use it as part of my scheduling.

Let the adventure begins… I’m building my tent at the base of Himalaya


CUCM: Intercluster Trunk Gatekeeper Controlled

We can configure a ICT GK controlled for distributed call processing models. The GK will perform the bandwidth and CAC management for the intercluster calls.

Is recommended to assign each cluster to it’s own zone.  In our case zones (CUCM6 and CUCM7) The main difference between how a gateway a CME or a CUCM interacts with the GK is the fact the CUCM will not register the E164 number dynamically ( the GK will not keep up with every single DN). Therefore the GK routing decisions should based upon tech-prefix and zone-prefix.

Read the rest of this entry

UCCX Integration

This video gives a quick overview of the steps to integrate UCCX and CUCM for the first time.

  • In CUCM you would like to create an application user and assign AXL permissions to it.
  • Make sure the AXL web service and CTI manager are running on the PUB.
  • Login into UCCX with the default credentials Administrator and pass: ciscocisco
  • Provide the information for the AXL account provisioned in CallManager
  • Upload the license files ( You can use the demo license included in the CD
  • Select the CTI Manager, JTAPI server and create the rmcm and jtapi user accounts on UCCX
  • Submit the changes.

More videos will come for specific features of the UCCX platform. Stay tuned.

Lab Inventory!

Hi, Unfortunately for most of us getting equipment to get hands on experience on VoIP is not as easy as we would like. There are some DSP and VIC cards that cannot be virtualized and need to be bought out of ebay or something. However for the most part GNS3 and WMWARE will be able to run the infraestructure, the CallProcessing layer and some softphones. Below you will find the list of equipment and software I will be using to power my own home lab.


1. NM2V

  • VIC 2FXS


  • VWIC1T1
  • PVDM32

3x 7960 Unified IP Phones

VMWARE Workstation 7.0

  • CUCM
  • CUPS 7.0.2
  • UCCX 7.0
  • Windows XP UE
  • Windows 2003 Server Standar Edition

CIPC 7.0

IP Blue Softphone

QoS Lab

I will be taking the Implementing QoS 642-642 exam in a couple of days from now and wanted to assemble an easy topology and integrate some of the QoS tools. I’ll take it slow as it’s the first time QoS and make it interesting at the same time.

This scenario proposes a Headquaters office and a Branch office. Phones have been getting regstered at the HQ CME (R1) just fine. However there are concerns for the QoS across the WAN since this is the first time IP phones are deployed at the BR. HTTP, HTTPS, FTP traffic to the HQ servers will compete for bandwidth with VoIP. Shapping, policying, LLQ, Fragmentation, RTP header compressiong, NBAR, will be deployed on this LAB.