Posts Tagged ‘edsonvuma’


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, 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


Posted: June 23, 2014 in Uncategorized
Tags: , ,


Hi, Guys.

Hope you all are feeling all right.

It’s been a long time since I made my last publication.

Well this delay was because I was digging and practicing more and more…in order to give you guys truly good articles and let you feel the good about stepping into the VoIP world.

I was practicing about Cisco Unified Communications Manager (CUCM), Cisco Unified Communications Manager Express (CUCME), Cisco Unity Connection (CUC), CUCM IM & Presence (CUCMIMP), Cisco Unified Contact Center Express (CUCCX), Cisco Jabber, Cisco Unified Prime Provisioning and other Cisco Products.

There will be more content coming up in videos and articles (more articles than videos…I guess 🙂 )

So, this is it Ladies and Gents….thanks for the attention you give to this blog and thanks for the feedback too.

Please, don’t forget the motto: “Everyone teach one”



Cisco Learning Network Store

Warm regards,

Edson Vuma