Archive for the ‘Networking’ Category

Integration of CUCM with CUC

Posted: December 17, 2015 in Communications


Hi, folks

Here I am once again to deliver another chapter of our series on Cisco Unified Communications.

This article will cover the integration of Cisco Unified Communications Manager (CUCM) and Cisco Unity Connection (CUC). After this integration we will be making some real tests with our IP Phones (Cisco IP Communicators) to see if it all works.


Cisco Unified Communications Manager is an enterprise-class IP telephony call-processing system that provides traditional telephony features as well as advanced capabilities, such as mobility, presence, preference, and rich conferencing services.

Read more here.

Cisco Unity Connection is a robust unified messaging and voicemail solution that provides users with flexible message access options and IT with management simplicity.

Read more here.


On this article I won’t be showing how to install Cisco Unity Connection as it is actually the same process as installing CUCM, which we already covered.

One other thing you need to know is that CUC actually comes on the same .ISO file of CUCM.

This is what we will use on this LAB:

  • VMware Workstation version 11.1.3
  • GNS3 version 1.3.11 (for NTP Server)
  • c3725-adventerprisek9-mz.124-15.T7.bin (IOS – not iOS 🙂 – which we will use on GNS3…GNS3’s Routers don’t come with an IOS, this is why we need at least one for now)
  • Cisco Unified Communications Manager version 9.1 installed on VMware Workstation
  • Cisco Unity Connection version 9.1 installed on VMware Workstation
  • Windows Server (any version you like…I used 2012) to use Active Directory
  • Mozilla Firefox version 42.0
  • Cisco IP Communicator version



I won’t be providing any of these softwares. They can be found on the vendors sites for download. The IOS for GNS3 can be found on the Web, just make a Bing Search and you will find them.



I installed Cisco Unity Connection on VMware Workstation using these hardware specifications:

2GB of vRAM,  200GB of vDisk, 1 vNIC and 1vCPU.

The network parameters I have used so far are:

GW / VMware Network Adapter VMNet1:



Windows Server 2012:

NTP Server on Cisco Router on GNS3:



So, let’s get started.

1. CUCM: On the Cisco Unified CM Administration page, go to Advanced Features > Voice Mail > Cisco Voice Mail Port Wizard


2. First step to do is the creation of a new Voice Mail Server. Give this Voice Mail Server a proper name


3. Add Voice Mail ports to this Voice Mail Server we created. I have set two, which, for this LAB will be enough


4. Now let’s configure Device Information for Voice Mail ports. These settings will be applied to all new ports.7.PNG

5. The ports we configured (two) need Directory Numbers – DNs – to work, so, lets configure what will be our first DN for the first created port. The system will automatically assign the next available DN for the new created ports.


6. We will want to add these DN to a Line Group


Quick Quiz:

A line group allows you to designate the order in which directory numbers are chosen.


7. Let’s give a proper name for this Line Group


8. Next step is the confirmation of all we have configured so far. Confirm it by clicking on Finish


9. Once it finishes, the system will give us the summary of what was done. There are two steps missing in order to use these 2 voice mail ports we have created :

  • Add the Line Group we created to a new or existing Hunt List;
  • Assign the new or existing Hunt List to a Hunt Pilot.


10. First thing first, right? Let’s create this Hunt List. Click on Hunt List in order to open the Hunt Lists page then click on Add New


11. Give a proper name for the Hunt List then click on Save


12. After clicking on Save the system will refresh the page and give you more options to configure. Click on Add Line Group


13. Select the Line Group we created during the Cisco Voice Mail Port Wizard process and click Save.


Click Save again so that you can save the configurations we made on the Hunt List.


Quick quiz:

A Hunt List lists a set of Line groups in a specific order. A hunt list then associates with one or more hunt pilots and determines the order in which those line groups are accessed. The order controls the progress of the search for available directory numbers for incoming calls.


14. Now let’s go to the Hunt Pilot page by heading to Call Routing > Route/Hunt > Hunt Pilot


15. Click on Add New


17. Give this Hunt Pilot a Directory Number and select the Hunt List we created on our last step then click Save


Quick Quiz:

The Hunt Pilot is the number users call to reach Cisco Unity Connection.


17. Next step we are going to create our Message Waiting. Go to Advanced Features > Voice Mail > Message Waiting


18. Click Add New


19. Our first MWI will be the DN Users call to deactivate Message Waiting


20. The second MWI will be the DN Users call to activate Message Waiting


Quick Quiz:

The Message Waiting Configuration window allows you to define a message waiting on or message waiting off directory number that a directory-connected based voice-messaging system uses to determine whether to set or clear a message waiting indication for a particular Cisco Unified IP Phone.


21. Now the next thing we will create is our Voice Mail Pilot. Go to Advanced Features > Voice Mail > Voice Mail Pilot. Then click on Add New


22. Give this Voice Mail Pilot the same DN we used for Hunt Pilot (I used 2050). Don’t forget to check the checkbox in order to make this the default Voice Mail Pilot for the system


Quick Quiz:

The Voice Mail Pilot number designates the directory number that you dial to access your voice messages. Cisco Unified Communications Manager automatically dials the voice-messaging number when you press the Messages button on your phone.


23. Now go to Advanced Features > Voice Mail > Voice Mail Profile and click Add New


24. Give a proper name for this Voice Mail Profile, select the Voice Mail Pilot we created, make it the default Voice Mail Profile for the system and click Save


Quick Quiz:

The Voice Mail Profile Configuration window of Cisco Unified Communications Manager Administration allows you to define any line-related voice-messaging information. A voice-mail profile gets assigned to a directory number, not a device.


25. Now we will configure our IP Phones in order to automatically make them redirect the calls to the Voice Mail if they are not answered within a specific time.

Go to the first IP Phone and click the line we want to configure (I only have one line per IP Phone). Devices > Phones



26 Scroll down to the Call Forward and Call Pickup Settings and check the indicated checkboxes and set a ‘No Answer Ring Duration’ (I have set 10 seconds).


Do this for the second IP Phone a well.


First stage on Cisco Unified Communications Manager is done. Missing part now is on the Cisco Unity Connections Server.

If you want to take a break feel free. This article will be here waiting for you. 🙂


27. Let’s go to our Cisco Unity Connection system and replace the hostname with the proper IP address of CUC in order to avoid too much DNS dependency



28. Now let’s make some configurations in Telephony Integrations. First thing we will configure is the Phone System. Go to Telephony Integrations > Phone System and click on PhoneSystem


29. Give a proper name and click on Save


30. Now go to Port Group and click on Add New


31. Set the Device Name Prefix, MWI On and MWI Off and CUCM Server IP Address then click Save


The Device Name Prefix MUST BE EXACTLY the same we configured on Cisco Voice Mail Port.

Just a reminder of what we configured:


The MWI On Extension we configured is 2061.

The MWI Off Extension we configured is 2060.

Our CUCM Server IP Address is



When you try to save with the Voice Mail Server name you have configured, it will give an “error” saying that it must finish with “-VI”, so, add that after the Voice Mail Server Name.

32. Now go to Port and click Add New in order to create ports for this Port Group we added on the last step


33. Set the number of Ports to 2 (two), exactly as we did during Cisco Voice Mail Port Wizard, and click Save


As we can see below, we managed to create our ports:



Next steps basically are about the Users. We can create local users (within Cisco Unity Connection) or sync them with LDAP (exactly how we did on CUCM). On this LAB I will use LDAP in order to sync the Users.

34. To do so, go to the Serviceability page of Unity Connection. Go to Tools > Service Activation


35. Select the Cisco DirSync service and click Save so that the system can start it.


36. Return to the Cisco Unity Connections Administration page and go to System Settings > LDAP > LDAP Setup and enable LDAP sync. I used Microsoft Active Directory, but feel free to choose any other LDAP system available.


37. Now go to LDAP Authentication and add the authentication parameters of your LDAP Server


38. Go to LDAP Directory Configuration and configure the right LDAP parameters and click on Save. After that click  on Perform Full Sync Now


39. As we are dealing with “well protected” systems here, there are some authentication rules that are set by default. And to avoid that complexity on this LAB we will edit those Recommended Voice Mail Authentication Rules. Go to System Settings > Authentication Rules and click on Recommended Voice Mail Authentication Rule


40. Set the minimum Credential Length to 4 and uncheck for trivial passwords then click Save


41. Now go to Templates > User Templates and click on voicemailusertemplate so that we can edit some parameters, specifically the password field. For this LAB I used 1234 as the default password for the users.






If we hadn’t change the Authentication Rule we couldn’t use this 1234 password, as it is extremely simple to use.

42. Now let’s import our users to our system. Go to Users > Import Users then select LDAP Directory and click Find


43. These are the users which are synced with LDAP. Select the ones you want to import and don’t forget to set their proper extension numbers then click on Import Selected


44. Go to Users > Users so that we can confirm that our users where successfully imported into our system


In terms of configurations, we are “done”. I’m assuming you have done everything accordingly. Next step is…test if all works. 🙂


45. To test if what we did works, use the first CIPC Phone (DN 1001) and call the second CIPC (DN 1002). Wait 10 seconds (the time we configured on both DNs) without answering


46. Voila!

After 10 seconds without answer, the phone automatically redirects the call to the Voice Mail, so the caller can record his message. I have recorded the message “Everyone Teach One


When the user of CIPC 2 returns (assuming he/she was absent), he/she will check the following message on the IP Phone “You have VoiceMail” as we can see on the image below.


THIS, folks, means that our configuration works 100%.

“Obviously” you asked yourself “How will the user check his voice mail anyway?”

Simple, remember the Voice Mail directory number we configured? Exactly what your remembered…, 2050.

So, all the user have to do is to dial to this Voice Mail Number. The system will automatically ask for a PIN which is……..yes, the one we edited on the User Template, 1234, and then voila….user hears my ugly voice saying “EVERYONE TEACH ONE”.



So, this is it….its over…for now. See you on OUR next article.

Any doubts, you can post your comments below as it can be somebody else’s doubt or you can send me an

Don’t forget the motto: EVERYONE TEACH ONE

See you soon



Cisco Learning Network Store

Warm regards,

Edson Vuma



Hi there,

Here I am once again to deliver another article.

This time we will be covering the mandatory configurations in order to:

  • Integrate CUCM with Microsoft Active Directory – MS AD;
  • Register IP Phones;
  • Associate End User (synced by MS AD) with an IP Phone;

So, today’s article will be focused on the 3 tasks above described.

We will register two IP Phones (one on my laptop and another one on a Virtual Machine). We will be using Cisco IP Communicator – CIPC – as an IP Phone.

Read more about about CIPC here.

I hope you guys have completed the installation of CUCM on your environments from our previous LAB.

This is what we will use on this LAB:

  1. VMware Workstation version 11.1.3
  2. GNS3 version 1.3.11
  3. c3725-adventerprisek9-mz.124-15.T7.bin (IOS – not iOS 🙂 – which we will use on GNS3…GNS3’s Routers don’t come with an IOS, this is why we need at least one for now)
  4. CUCM version 9.1 installed on VMware
  5. Windows Server (any version you like…I used 2012) to use Active Directory
  6. Mozilla Firefox version 42.0
  7. Cisco IP Communicator version


I won’t be providing any of these software. They can be found on the vendors sites for download. The IOS for GNS3 can be found on the Web, just make a Bing Search and you will find them.



So let’s get started.

1. Select Cisco Unified Serviceability on the upper right corner drop-down menu and click “Go”


2. Now select Tools > Service Activation


3. Select the following Services to be activated, click on Save and then press OK on the pop-up warning that will appear

Cisco CallManager
Cisco CTIManager
Cisco TFTP
Cisco AXL Web Service
Cisco DirSync



Quick Quiz:

Cisco CallManager service provides software-only call processing as well as signaling and call control functionality for CUCM.

Cisco CTIManager service contains the CTI components that interface with applications. This service allows applications to monitor/control phones and virtual devices to perform call control functionality.

Cisco TFTP – Cisco Trivial File Transfer Protocol (TFTP) – service builds and serves files that are consistent with the trivial file transfer protocol, a simplified version of FTP. Cisco TFTP serves embedded component executable, ringer files, and device configuration files.

Cisco AXL Web Service allows you to modify database entries and execute stored procedures from client-based applications that use AXL.

Cisco DirSync service ensures that the Cisco Unified Communications Manager database stores all user information. If you use an integrated corporate directory, for example, Microsoft Active Directory or Netscape/iPlanet Directory, with Cisco Unified Communications Manager, the Cisco DirSync service migrates the user data to the Cisco Unified Communications Manager database. The Cisco DirSync service does not synchronize the passwords from the corporate directory.

Read more about these and other services here.


4. Now that we have activated the mandatory services to our system work, return to the Cisco Unified CM Administration Page


5. Let’s remove all the DNS dependency on our system. To do so go to System > Server then replace the hostname with the IP address you configured on your CUCM Server during the installation. Mine is (the same we did on our previous LAB)




6. There are some other configurations (Phone URL Parameters) that are still using the hostname, lets change them to the IP address. Go to System > Enterprise Parameters


You should see “cucm” (or the hostname you configured during the installation process) on the parameters. Change it to the proper IP address:


7. Now let’s make the configurations to allow our system to sync users from our MS Active Directory Server. First go to System > LDAP > LDAP System and then enable the synchronizing from LDAP Server



8. Then go to  System > LDAP > LDAP Authentication and make the proper configuration so that our System can communicate with Microsoft AD



On the distinguished name you can use something like this too:, but I have chosen to use containers.

Observation: is the IP address of my Windows Server 2012, which is my Active Directory Server.


Quick Quiz:

LDAP Manager Distinguished Name is where we indicate the user which has permissions on MS AD

LDAP password is where we put the password of the distinguished user.

LDAP User Search Base is where our System is going to search for users to be synced. If you have placed your users on a difference Organization Unit – OU, then make sure you configure the Containers correctly.


9. Now go to System > LDAP > LDAP Directory and basically we will be configuring the same things we did on LDAP Authentication

Click “Add New” then configure LDAP Configuration Name, LDAP Manager Distinguished Name, LDAP Password, LDAP User Search Base and IP Address of the LDAP Server.

After making the configuration, click on “Save” and then click on “Perform Full Sync Now




10. These are the users I have on the Organization Unit “Users” on my MS AD


11. After some seconds, go to User Management > End User and we should see there all our synced users



If you are getting 0 results hit “Find” button as it works as a “refresh”.

All right folks, we managed to finish the synchronization of CUCM with Microsoft Active Directory.


12. Now we will add all our users to the Stantard CCM End User Group so they can have access to the User Web Page. To that, Go to User Management > User Setting > Access Control Group (on older versions of CUCM the path is User Management > User Group)


13. Click on Standard CCM End User


14. Click on “Add End Users to Group


15. Select the Users and then press “Add Selected


On my LAB here, User “Kaiyden Vuma” will be the owner of the first CIPC (installed on my Laptop) and User “Raquel Raimundo” will be the owner of the second CIPC (installed on my Windows Server 2012 VM).

So, what we have to do is to associate those Users with the CIPC Phones we will be using on the LAB.

But first, we need to register those CIPC Phones on our System.

16. Go to “Preferences” on CIPC 1 (physical laptop), then configure the TFTP Server with the IP address of the CUCM, then give a proper Device Name for easy identification (you can leave it with the default name if you want to)


17. Now go to Device > Phone and then click on “Add New


18. Select “Cisco IP Communicator” and “SCCP” on both drop-down Menus on the screen


Quick Quiz:

SCCP (Skinny Client Control Protocol) is a lightweight IP-based protocol for session signaling with Cisco Unified Communications Manager.

The term “skinny” reflects that SCCP is a simple and uncomplicated (“lightweight”) protocol requiring relatively little computer processing.

Read more here.


19. Configure Device Name (which must be the same Device Name we configured on our CIPC phone), set Device Pool as Default, choose any Phone Button Template you like on Phone Button Template for your CIPC (I like the buttons of the Cisco IP Phone 7962 as it gives me 8 lines) and finally set Device Security Profile to “Cisco IP Communicator – Standard SCCP Non-Secure” and then click “Save



20. Now click on “Line 1” then give a DN (Directory Number) for this CIPC phone and hit “Save



21. After this step go ahead and restart your CIPC Phone and once it finishes restarting we should see it registered successfully


22. Follow the same steps for registering the CIPC 2 phone (I used DN 1002 on CIPC 2)


Now we have 2 things missing on today’s LAB:

  • Associate the Users with the CIPC Phones
  • Call tests between the CIPC Phones.


23. To Associate the CIPC Phones with the Users, first go the End User page (User Management > End User) then click on your first User

If you are getting 0 results hit “Find” button as it works as a “refresh”.

As I said before, the owner of my CIPC 1 Phone will be User “Kaiyden Vuma” and the owner of my CIPC 2 Phone will be User “Raquel Raimundo”.

So, I clicked on my first User and then I selected “Device Association


24. Select the desired CIPC Phone to be associated with this user and click “Save Selected


Do the same for the Second User and associate him with CIPC 2 Phone.

25. Now go to the Phones page (Devices > Phone), click on CIPC 1 Phone then click on the configured DN (which is 1001)

If you are getting 0 results hit “Find” button as it works as a “refresh”).


26. Scroll down until you find and click “Associate End Users” button


27. Select the User who is going to control this DN and click “Add Selected


Congratulations if you made it this far. Now is time to make the final tests between both CIPC phones on our physical and virtual machines.

28. Call from one phone to another




As we can see on the 2 pictures above…it WORKED!!!



So, this is it….its over…for now. See you on OUR next article.

Any doubts, you can post your comments below as it can be somebody else’s doubt or you can send me an

Don’t forget the motto: EVERYONE TEACH ONE

See you soon



Cisco Learning Network Store

Warm regards,

Edson Vuma


Hi there, long time no “see”. Hope you guys are doing great.

From now on, we will start a new series on OUR articles. We will cover the most robust calling processor: Cisco Unified Communications Manager – CUCM.

We will be using the Cisco Unified Call Manager Express – CUCME – to make integrations with CUCM, configure and administrate CUCM, integrating CUCM with other communications systems such as: Cisco Unity Connection, CUCM IM & Presence and so on.

But what is mandatory to accomplish that? Yes, it is exactly what you have thought: Installation.


So, let’s get started.

Nowadays, a lot of systems are being virtualized. Why that happens, you may ask. The main reason that happens is because of: Cost savings, Faster server provisioning, Improve disaster recovery and the list of advantages goes on and on. You can make a Google Search (why not a BING Search 🙂 ) and you will read more about virtualization.

We will be installing our CUCM on VMware. This is what I will use on this LAB:

  1. VMware Workstation v. 11.1.3
  2. GNS3 v. 1.3.11
  3. c3725-adventerprisek9-mz.124-15.T7.bin (IOS – not iOS 🙂 – which we will use on GNS3…GNS3’s Routers don’t come with an IOS, this is why we need at least one for now)
  4. CUCM .ISO file (I’m using CUCM 9.1 version)
  5. Mozilla Firefox

I won’t be providing any of these software. They can be found on the vendors sites for download. The IOS for GNS3 can be found on the Web, just make a Bing Search and you will find them.


The recommended system requirements for CUCM 9.1 virtually installed are:

2 of vCPU, 4GB of vRAM, 1x80GB of vDisk and 1 vNIC.

We are going to install it with 2GB vRAM.



Let’s start by installing our CUCM.

  1. Open VMware Workstation, press CTRL+N and choose Typical (recommended):


  1. Select the second option on the next menu: Installer disc image file (iso) and then browse and select the .ISO file:


  1. Choose Linux and select Red Hat Enterprise Linux.

Note: CUCM platform is based on Red Hat.


  1. Type a proper name for the VM



  1. Set the disk size to 80 GB and choose one of the options for how VMware will handle with the Virtual Disk.


  1. Before we click Finish, there is something we have to do on our virtual hardware, so, click on Customize Hardware:


  1. Set the memory to 2GB at least, and set the cores per processor to two (2)




It’s all set up for the installation. We can now Finish and start the VM for installation.

1. We will be asked for a Media Check, this way the system can recheck the requirements for installation so that we don’t lose time finding only later that something is missing.

I recommend you guys to choose “YES” instead of “NO”, but you are free to choose the best option for you.

Note: Mouse is not supported here, so you can use the “TAB”, “SHIFT+TAB”/”ALT+TAB” and “ENTER”/”SPACE” keys to navigate on the menu.

media check

2. Wait until you get the confirmation of the system that you are ready to go with the installation:


If you have error messages on the above screen, revise the requirements and double-check the steps to make sure you have done it in the right way.

3. Let’s select the product we want to install, which is CUCM


4. Confirm installation of CUCM


5. On the next screen you can choose either if you want to use the Setup wizard now for the configurations or you can configure later. I have selected “Proceed” with the Wizard


6. Choose “No” on the next screen as we are not going to apply any upgrade patch for now


7. Click “Continue” on the following screen and then select your Timezone:



8. Click “Continue” on the following screen for NIC Speed and Duplex, select “No” for the MTU size (we will keep the default value of MTU) and choose “No” for the DHCP as we don’t have any DHCP Server running.




9. Insert your Network Configurations, mine can be found on the following image


10. Choose “No” on the next screen as we won’t be using DNS for now


11. Add the credentials you want to use for the “ADMINISTRATOR Login*”.


12. In order to the system generate a security certificate, we will have to fill the information asked on the next screen


13. Select “Yes” on the next screen as this is our first node


14. Add your NTP Server IP Address on the next screen


15. Set the “SECURITY passwords**”


16. Select “No” on the next screen as we won’t be using SMTP for now


17. Set the “APPLICATION credentials***”



Quick Quiz:

We have seen the following on our configurations: ADMINISTRATOR Login, SECURITY Password and APPLICATION Login. What is the difference between those three?


Administrator account username and password

During installation, you must create an Administrator Account username and password to log into the following areas:

  •  Cisco Unified Operating System Administration interface
  •  Disaster Recovery System Administration interface
  •  Command Line Interface (CLI)

The Administrator login must start with an alphabetic character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores.

If you lose the Administrator password and cannot access the system, you can recover the Administrator password in Cisco Unified Communications Operating System Administration.

If you need to reset the Administrator password, use the CLI.

Application username and password

During installation, you must create an Application User user ID and password to sign into the Cisco Unified CM IM and Presence Administration interface.

If you need to reset the Application User password, use the CLI.

Security password

During installation, you must specify a system security password. This password is used to secure communication between cluster nodes. In the Post-Installation deployment wizard, which displays the first time you sign in to Cisco Unified CM IM and Presence Administration, you must reset the security password to be identical to the password used on the Cisco Unified Communications Manager (Unified CM) publisher server.

Check more at Cisco Documentation


That said:

18. Finish the Wizard



After we finish our Wizard we might get errors because of NTP Server being inaccessible.


NTP Server is required for the installation to proceed, without it we will not be able to proceed with the installation.

This is the error we get when the NTP Server is not accessible.

NTP Server Error.jpg


Quick Quiz:

NTP – Network Time Protocol

Is a networking protocol for clock synchronization between computer systems over packet-switched, variable-latency data networks.

GNS3 – Graphical Network Simulator

Is a graphical network simulator that allows you to design complex network topologies. You may run simulations or configure devices ranging from simple workstations to powerful Cisco routers.


Note: If your Virtual Machine has access to the Internet, you can use a public NTP Server. There are so many you can use, just make a Google Search and you will find them.

But, for my case, I didn’t use any public NTP Servers.

I configured a Router on GNS3 as my NTP Server and here I integrated VMware with GNS3 so that my CUCM Server can communicate with this Router:

19. Integration of VMware and GNS3

 a. First Select “Settings” of the CUCM Virtual Machine. Go to “Network Adapter” and on the “Network Connection” choose “Custom” and select one of the 2 network adapters that VMware installs on our Computers (VMNet1 and VMNet8). I have used VMNet1


b. Go to the selected network adapter through Control Panel and configure the Network parameters.

Note: Remember we used the following IP address as our GW when we were configuring CUCM network parameters? Exactly, we will be using this IP address on this network adapter


c. Open GNS3 as Administrator, press “CTRL+SHIFT+P” for Preferences, go to “IOS Routers” and click “New” so that we can add a new IOS for the Routers. Browse and select your image



d. Add your new “Router” on GNS3 and add the “Cloud” by drag-and-drop


e. “Right-Click” on the Cloud, select the Network Adapter we configured on our CUCM Virtual Machine (the same we configured on Control Panel as our GW).


f. Link your Router with the Cloud and then make the proper NTP configurations on the Router then test the connection from your Router on GNS3 to the CUCM Virtual Machine


As we can see above, I can reach the CUCM Server, all I have to do is configure this Router ( as my NTP Server and test on CUCM:


Once this is done, the system will begin the installation of CUCM.

Have in mind that this installation process takes around 2 hours to finish. The duration of the installation may depend also on your hardware.

As this takes time to finish, go relax playing a game, drink a coffee or something else you like.

I relaxed playing Age Of Empires: Castle Siege as I like this game. 🙂


Once the system finished installing, you will see a screen like this (it will be a little bit different as, unfortunately, I toke the screenshot after I have restarted the CUCM Server…but that doesn’t matter, it’s not relevant):


The above screen is the confirmation that the CUCM Virtual Machine has successfully finished installing.

We can now go to the Browser and try to access the Server. Have in mind that there are some services that take some time to start up even after the Server is up and running, so give it some minutes and try accessing.

20. Accessing to CUCM



There is a “problem” I detected once I click on “Cisco Unified Communications Manager”. Firefox gives me this “error”:

a. Firefox error


To by-pass this security check, open a “New Tab” on Firefox and go to this URL



Click on “I’ll be careful, I promise!” and on the search box, type this “security.ssl3.dhe_rsa_aes_” and you will get the following results:


By default, those values are set to “true“. Double click on both to set them to “false


No need to restart the browser and now we can click on “Cisco Unified Communications Manager”.

Type the “APPLICATION Credentials” and you are done with the installation.




So, this is it….its over…for now.

Next article will be the basic configurations on our CUCM server and we will register a couple of Phones.


Any doubts, you can post here your comments as it can be somebody else’s doubt or you can send me an

See you soon….

Don’t forget the motto: EVERYONE TEACH ONE



Cisco Learning Network Store

Warm regards,

Edson Vuma


Hi, Guys.

Hope you all are feeling all right.

So, assuming that you have successfully practiced the basic configs of VoIP and assuming that you have read the little brief about VoIP on the last article, today ( 🙂 ) we will be practicing about dial peers.

Maybe you are wondering: What’s a dial peer?

Well, dial peer (is the same as Addressable Call Endpoint) is a device (or not) that can originate or receive a call in a telephony network.

The term dial peer is sometimes used in reference to a program that matches a specific dialed sequence of digits to an addressable call endpoint.

In the VoIP world, dial peer can be categorized as either voice-network dial peer or as POTS (Plain Old Telephone Service).

Voice-network dial peers include VoIP-capable computers, routers and Gateways within a network.

POTS dial peers include traditional telephone network devices such as phone sets, cell phones and fax machines.


So, known the…basics about dial peers, let’s get to work.

Here is the topology we are going to use on our lab:




We have, for our lab (you can increase if you want), two sites: a Headquarter and a Branch.

The network scheme for the headquarter is (as shown on the picture above):

Voice VLAN: 50
Data VLAN: 10
Voice Network:
Data Network:


The network scheme for the branch is:

Voice VLAN: 20
Data VLAN: 5
Voice Network:
Data Network:


So, lets make the configs on the HQ first.

1. On the Switch:



The interface fa0/1 is the one connected to the router.

As we are going to configure more than one VLAN we must configure this interface as trunk to allow traffic of multiple VLANs.

Next step is to create these VLANs described above:


Now, we are going to assign the ports connected to the IP Phones to these VLANs (access and voice VLANs).


Typical STP convergence time is around 50 secs by default, so basically every port takes around 50 secs to initialize and be in forwarding state. This is a lot of time and is not needed to be spent on the access ports of a switch.
In our LAB, on the access ports where we have the IP Phones connected, so, this is why we configured the spanning-tree portfast command to disable the STP check.
2. We are done on the switch, now we are making some  configs on the router:
We configured both VOICE and DATA DHCP pools (for IP Phones and for PC’s).
We excluded some addresses on the pools just to don’t get any conflicts with some IPs we might use. On our LAB we only used the firsts IPs from  both networks (VOICE and DATA). But, we might want to use another one day. This is why I reserved 10.
Now, we are configuring the sub-ifs on the router:
Done this, we are now going to the telephony-service configurations.

We configured 10 maximum phones, 10 maximum phone lines, the IP address from where the telephones will be registered, the port used for the phones, the default one is 2000 (for SCCP phones) and we have set to automatically register the phones, on this case is from phone 1 to 10.

Lets configure the DNs for the IP Phones which are going to be auto registered.



Done this on the HQ, we can power up the phones and wait until they are registered.

In case you have forgotten how to power up on Packet Tracer, see below how:



After successfully registration on the HQ we are going to do the same on the Branch side.

As the explanation is already mentioned, I will only insert screenshots of commands for the branch side.




















Done this on the Branch side, we can power up the phones and wait until they are registered.


As you see, the numbering scheme on HQ and on Branch side is different:






Lets face a scenario here….Lets suppose this topology refers to a company, a “huge one” (its relative). Lets say at least 200 users on the HQ and 70 on the Branch. The users make calls from one side to another very, very often…

Can you imagine what would be the cost per month of the PSTN calls???

So this is where, in general manner, VoIP helps us saving costs and increasing productivity and collaboration.


What will be done is the configuration of dial-peer (the voice-network category).

In order to this configuration of dial-peer to work, we must ensure that both CUCME routers have connectivity for their telephony networks.

You can use serial connections, routing protocols or any other best way that suits you.

For this LAB I used static routes…
So,  first I created the /30 connection between both routers:



On the Headquater side I configured



On the Branch side I configured



NOTE: The only request here is that the telephony networks are reachable on both sides. But, for this LAB we can allow the connection on the DATA networks too.

HQ Side:



Branch Side:



We can test this connectivity…using the PC’s on our network.

Click on one PC of the Headquarter side and follow the instructions as follow (in case you don’t know, of course 🙂 ).


Desktop_HQ2. (Click on the first option – IP Configuration)


3. Do the same for all remaining PC’s even on the PC’s of the Branch side…

4. Test connection with ping…


So, having the connectivity tests successfully made…we can advance to the dial-peers configurations.

Whats next is….configure the dial-peer 🙂

On the HQ Side:



1. We can have as many dial peer as we want (there is a limitation of course 🙂 ), this one configured has the ID 1

2. destination-pattern is where we set the…destination pattern ( 🙂 ). As you might remember, the numbering scheme for the Branch Office is: x000 and for the HQ side is: x0.

You may be wondering, why we configured the destination-pattern as “.000” on the HQ side?

This was made because we expect different numbers (only on the first digit) on the same pattern.

For example:

If I dial 1000, the call will be routed to this dial-peer we configured. If I dial 2000 it will be routed to this dial-peer too (specifically this dial peer impacts the 1000, 2000, 3000, 4000, 5000, 6000, 7000, 8000 and 9000 numbers).

But, if I dial something like “1001” the call wont be routed because there is no destination-pattern configured on our router.

Take time to read a little bit of the dial-peer destination-pattern commands here.

3. session target ipv4:A.B.C.D represents the next hop for the pattern we have created. On this case, is the address of the Branch CUCME router (from HQ to Branch).


Make the reverse on the Branch side (configuring a dial-peer with a destination pattern for the HQ numbering scheme).


So this is it…that was the last step…in terms of configurations.

Taking a closer look at the numbers of our IP Phones, from HQ and Branch, respectively.



The only thing left is…TEST what we have done…(I’m shaking  🙂 ).

So, lets make this call from on site to another…






So, this is it….its over…for now.

Hope you finish successfully the configurations.

As you may know, Packet Tracer is VERY limited…only allows us to do the basics…but its a great, great, great tool to get started.


Any doubts, you can post here your comments so that anyone can see it or you can send me an email:

See you soon….

Don’t forget the motto: EVERYONE TEACH ONE

Don’t forget to share it…



Cisco Learning Network Store

Warm regards,

Edson Vuma


Despite all the warning of document all important things in work/school/self-study….there are those days which we don’t have the feeling to write….I can tell you guys..If that day passes, hardly you are going to document again. 🙂

Now, imagine you are a network admin and there is an emergency of configure equipment which you have “forgotten” the password (the right word is careless ’cause we had the chance to document but we didn’t. LOL).

So, on this article, I will show you exactly how to “recovery” (we will change it actually) the password without losing any configurations made on our device.

OK, lets get to work.

First of all, consider making this topology:









Lets focus on one device, on this case, lets use the router.


Make this configurations on it:

conf t
hostname MAIN_ROUTER
line console 0
password cisco
line vty 0 15
password cisco
enable secret cisco
!wr is the same with copy running-config startup-config

Lets assume that we have other configurations on it (IP addresses and so on). 🙂


OK, after saving what we did so far, lets pretend we have “forgotten” the password.

Hummmm….how to “recovery” it without losing ANY configuration we have?

Before that, we have to understand a little thing:

The configurations we make on a router (or switch) are always saved, on a certain address of the memory. We will have to change this address, copy the configurations and renew the password.


OK….enough of “bla bla bla” now lets get this done. 🙂

You will have to reload the device, MAKE SURE you have saved the running configurations and lets reload the device.

Just type “reload” command on the # prompt.

Proceed with reload? [confirm]
%SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload Command.

In order to change the configurations register address, we will have to break the system load and we will use some KEY COMBINATIONS on our keyboard.

On REAL DEVICES: the combination is usually CTRL+BREAK (but depends on the platform you will be using. Click here for the list of combinations)

On PACKET TRACER: the combination is CTRL+C

During the image load, after the reload command, press the combination above to break the boot. See the picture below for clarification:







We have now entered on the ROMMON mode. For those who didn’t know, rommon is a boot-loader on Cisco devices that helps to initialize the processor hardware and boot the operating system software (Cisco IOS- not iOS :))

Lets change the confreg…

By default, the configurations we make are stored on this address: 0x2102, and for this “recovery” we will have to change that.




Well, resetting after changing the confreg, we are going to be on ANOTHER, lets say: configuration process 🙂







Just type “NO”

And ATTENTION on the next step, because it will define if you will or wont lose your configuration.

Remember that our configurations are not lost, but, for now, they are not accessible (yes, we have changed the confireg, you are right if you though that :)). OK,

What we will do is to COPY those configs to the actual configuration process.

run the following command:

copy startup-config running-config

ATTENTION: DON’T run here copy running-config startup-config otherwise it will overwrite our configurations and we will lose them. 😦









As you can see, our configurations are back. Exactly the same we have made.


Now, there are 4 things to be done:

1. Renew the passwords we have “forgotten”;

2. What would happen if we changed the password and restarted the router? Would it work? Of course not, because we have changed the confreg.

So, we have to “re-change” it to the default one: 0x2102

Enter the configure terminal and just change it…





3. If we restart the router would it work now? Extremely not. We have to SAVE the configuration. 🙂






Now, reload the system in order to test what we have done so far.

Hummmmmm…..I guess you are wondering: “What about step number 4?


Well, the step 4 is to document your password in order to don’t lose it again. 🙂


Hope you finish successfully the configurations.

Any doubts, you can post here directly so that anyone can see it or send me an email:

See you next time….:)


Cisco Learning Network Store

Best regards

Edson Vuma





On this article I will describe superficially about the basic concepts that you must have in order to have the…….basic info and complete this LAB successfully . 🙂

So, Gents and Ladys…

Lest start describing what is VoIP: as the name says, VoIP is Voice over IP. Anything that allows you to communicate, I mean, to transmit your voice over the IP, or the Internet , is VoIP.

There are distinct vendors of VoIP,  however, on this tutorial, we will focus on Cisco, we will focus on the following product: Cisco Unified Call Manager Express (commonly known as CUCME)

There are Routers called ISR: Integrated Service Routers, which come with certain services and features inside it.

CUCME is one example of these features and services that are build-in the router (or are router-based).

There is a technology called PoE: Power Over Ethernet, which allows equipment to send data and power at the same time to certain devices that are PoE compatible.

So, knowing these few things, lets get to work.

Lets mount the following topology:










Pay attention that on Packet Tracer the PoE technology isn’t implemented yet. 🙂

This is why, to power on the IP Phones we will connect a power adapter to it.

As the Switch is not PoE.

See how to connect the power adapter to the IP Phone on the picture below:












So the first thing to be done is to configure the IP address of the router:

Router#configure terminal
Router(config)#interface FastEthernet0/0
Router(config-if)#ip address
Router(config-if)#no shutdown

A DHCP server is used to assign IP addresses to the IP Phones.

A TFTP server is used to allow the phones to get the firmware and certain configurations files from the router, this is done by the option 150 of the DHCP.

1. Router(config)#ip dhcp pool VOICE
2. Router(dhcp-config)#network
3. Router(dhcp-config)#default-router
4. Router(dhcp-config)#option 150 ip

CLI description:

1. Giving a name to the DHCP pool, in this case, this pool is for the phones only,

2. The network that is covered by the DHCP

3. The default router for this IP distribution

4. Configuration of the TFTP

Next step to do is to configure the Call Manager Express itself on the router,

1. Router(config)#telephony-service
2. Router(config-telephony)#max-dn 5
3. Router(config-telephony)#max-ephones 5
4. Router(config-telephony)#ip source-address port 2000
5. Router(config-telephony)#auto assign 1 to 5

CLI descrition:

1. Enters to the telephony services

2. max number of phone lines

3. max number of telephones

4. The IP of the router where the telephones will be registered and the source address where is running the DHCP and TFTP services, which will be the router itself. And the port used for the phones, the default one is 2000 (for SCCP phones)

5. is to automatically register the phones, on this case is from phone 1 to 5 (you can register the IP Phones yourself, next time I will show how to do it)

Next step is to configure the Switch, on this case, there is not too much to do, just configure a VLAN for voice traffic. We must add this VLAN to separate the data traffic from the Voice traffic. Data will be sent to the computers and voice traffic will be sent to the IP Phones.

As we configured 5 max IP Phones, so we will configure 5 interfaces of the switch to the Voice VLAN.

As you can see on the image below,







P.S.: The first interface of the switch on my scenario, is connected to my router, so we will exclude it on this VLAN configuration.

Switch(config)#int range fastEthernet 0/2-6
Switch(config-if-range)#switchport mode access
Switch(config-if-range)#switchport voice vlan 1

Despite being on the same VLAN  (data and voice), virtually the traffic will be separated. (If you wish, you can create another VLAN for the VOICE traffic)

Now is time to give numbers to the lines that will be used on the IP Phones:

P.S: We have configured 5 max IP Phones, so we will configure 5 max numbers for the lines.

Router(config)#ephone-dn 1
Router(config-ephone-dn)#number 10

Router(config)#ephone-dn 2
Router(config-ephone-dn)#number 20

Router(config)#ephone-dn 3
Router(config-ephone-dn)#number 30

Router(config)#ephone-dn 4
Router(config-ephone-dn)#number 40

Router(config)#ephone-dn 5
Router(config-ephone-dn)#number 50

Its almost there, the only confirmation we need is that the IP Phones were successfully registered on the CUCME (This process can take a while).
Hover the mouse on the IP Phone to see if it successfully received the IP address and the phone number (If not, wait a little bit more. P.S.: This process can take a while).


Once you have the confirmation, you can add the remaining 4 IP Phones on the switch, remembering that these IP Phones must be added on the same interfaces were have configured the Voice VLAN. 🙂










Make a call to test the configurations

1. Look at the pictures below:










2. Dial from one phone to another, on this case we will dial from IP Phone number 10 to IP Phone number 20 (to dial, just mark the number and click on the earphone)









To pick up the call on the other phone, just click on the earphone too and…VOILA

Hope you finish sucessfully the configurations.

Any doubts, you can post here your comments so that anyone can see it or you can send me an email:

See you next time…. 🙂


Cisco Learning Network Store

Best regards,

Edson Vuma