VOIP within a Network

Foris Kuang
Period 3/4

Purpose
The purpose of this lab is to teach us students how to send up IP Phones in an
enterprise network but for now on a basic level so that one can call within a lan and
not outside. This is commonly seen in schools and hotels. This is a way for us to get
that experience. We also learn how to use Call Manager and set up NTP on the
router in order to make this work. Overall we, the students get a better grasp of
learning how to set up VOIP.

Background Information
VoIP
VoIP, more commonly known as voice over IP is a technology that allows voice to be
communicated over IP networks like the Internet. A common example of this is
Skype and hotels. VoIP not only allows one to make calls to other phones, but also
allows one to call within your own network, mobile, and international numbers. VoIP
works by translating your voice into packets like UDP packets, or a protocol that
does not check whether or not all the information has been gained before it sends it
out in order to make sure you are hearing the voice in real time. These packets are
sent via the internet or through your IP address that is given to you by the router.
This allows people to make calls with "WiFi" nowadays.

Cisco Unified Call Manager

In order to implement VoIP, you need a way of setting it up and managing the
numbers and devices that you employ, Cisco Unified Call Manager is that program.
It is a "IP-telephony processing system." It has the capabilities of hosting huge
enterprise networks with up to tens of thousands of users. It basically allows you to
determine what numbers are going to be assigned to each phone, manage each
phone device on the network, determine whether you want to have the entire
enterprise have the same voicemail/ringtone and etc. Basically, if you want to set
up VoIP you want to use a program that is able to process IP telephones and
manage them in a simple structure.

Lab Summary
For this lab my partner and I will set up a router with NTP and DHCP so that the
phones can receive a time and an IP address. From there we will set up and install
Cisco Unified Call Manager (CUCM) and utilize that to establish a connection
between the two phones that are connected on the same network. They will also
receive a number. Then we establish Power Over Ethernet (POE) to give power to
the phones before finally having a dial tone. From there my partner and I should be
able to call each other.

Lab Commands
Router Configurations
Command
Router(config)#interface [interface
type] [interface number]
Router(config-if)#ip address [IP
address] [netmask]
Router(config-if)#no shutdown
Router(config-if)#option [number]
[IP address of CUCM]
Router(config-if)#exit
Router(config)#ip dhcp excludedaddress [min IP address to exclude]
[max IP address to exclude]
Router(config)#ip dhcp pool [pool
name]
Router(config-pool)#default-router
[IP address of port]
Router(config-pool)#network
[network IP] [netmask]
Router(config-pool)#exit
Router(config)#ntp server [IP
address of CUCM]
Router(config)#ntp master
[number]
Router(config)#ntp maxassociations [number]

Purpose
Enters you into configuration mode for
that specific interface
Sets that port to have that IP address
Turns on the port

Exits configuration for that port

Creates a DHCP pool of addresses with

that given pool name
Sets DHCP to be enabled on the port
with the given IP address
Configures DHCP to use the IP addresses
on the given network except for those
previously deemed excluded
Exits configuration for DHCP pool
Sets the network time protocol to receive
information from the CUCM

Switch Configurations
Command
Switch(config)#interface range
[interface type] [interface number
range]
Switch(config-if-range)#no
shutdown
Switch(config-if-range)#power
inline auto
Switch(config-if-range)#exit

Purpose
Enters configuration mode for all of
those ports
Turns on the interfaces within that range
Turns on POE for the interfaces within
that range
Exits configuration for these ports

Lab Diagram

Configurations
Router Configurations
Router(config)#hostname Router
Router(config)#ip dhcp excluded-address 192.168.1.1
Router(config)#ip dhcp pool WATER
Router(config-pool)#network 192.168.1.0 255.255.255.0
Router(config-pool)#default-router 192.168.1.1
Router(config-pool)#option 150 ip 192.168.1.254
Router(config)#ntp max-associations 10
Router(config)#interface GigabitEthernet0/0
Router(config-if)#ip address 192.168.1.1 255.255.255.0
Router(config)#ntp master 1
Router(config)#ntp server 192.168.1.254
Router(config)#end

Switch Configurations
Switch(config)#hostname Switch
Switch(config)#interface FastEthernet0/2
Switch(config)#power inline auto
Switch(config)#interface FastEthernet0/3
Switch(config)#power inline auto
Switch(config)#end

Installing Cisco Unified Call Manager

Enter your Virtual Machine and create a new Virtual Machine.

Locate the ISO for CUCM

Allocate a decent amount of space for the CUCM.

Click Customize Hardware...

Allocate a decent amount of RAM

Click Network Adapter and select Bridged and Replicate physical network

connection state

Power on the Virtual Machine

Click OK until you see this screen which you then again hit OK

Click the highlighted part

Fill in the following credentials then click highlighted parts again.

Input address of router

Setting up Cisco Unified Call Manager

Type in the IP address you designated the CUCM in your set up and you should
receive the Cisco Unified Call Manager Administration page. Go to the dropdown in
Navigation and click Cisco Unified Serviciability, and you should get the screen as
follows.

Subsequently, go to the tools dropdown and click service activation. Check Cisco
CallManager and Cisco Tftp, then hit Save.

Next, go back to the dropdown and go back to the Cisco Unified CM Administration
page.

Go to System in the top left and click Cisco Unified CM

From there click the find button that is highlighted and click the first name that pops
up.

Change the default Universal Device Template to Auto-registration template as

shown.

Change the Universal Line Template as follows from none.

Set your directory range of numbers and then hit save

Click System again and this time go to the Cisco Unified CM Group

Then click Find and click the Default one.

Make sure that the CM_Manager is selected than hit save.

This pop up means that everything went correctly and hit ok.

Now all that is left is to plug in your phones and everything should work out
perfectly.

Problems
Initially my partner and I had problem with installation, to be honest this was
problem the part that deterred us the most. For one we would initially installed the
Cisco Unified Call Manager multiple times without enough memory so it wasn't able
to successfully install. After that, we would successfully install, however when we
rebooted our computers, the CUCM would suddenly fail and we would have to
reinstall, this was fixed later randomly. Then, we proceeded on to accessing the IP
address of the Cisco Unified Call Manger and multiple times we would get an error
screen. This was simply resolved by waiting a couple of minutes then we would be
able to access. The last problem we had was that some phones their protocols were
simply broken and the phone wouldn't work, this was mitigated by changing phones
until the protocol was actually working and then finally our phones would work and
we could ring and call.

Conclusion
This lab has a multitude of places where one could error. One misstep can lead to a
world of problem and basically result in your VoIP not working. Overall what needed
to be done was simply learning how to set up the Cisco Unified Call Manager, this
was the main problem as not knowing was half the battle. The second part was
learning that we needed to utilize NTP in order for it to work and learning how to
configure NTP. All in all, the main that was needed was the instructions for Cisco

Unified Call Manager which were researched because multiple sites gave false
information, and making sure that it was installed correctly, otherwise, it would
have not worked. Switch should have almost no configurations except for turning on
power over Ethernet. As a result, I now firmly believe I can handle making a call into
the "real world," also my partner and I already learned how to do ringtones because
we messed up initially thinking ringtones was part of the sign off.