Lab 5-1: Basic Manual Phone Configuration Using the CLI – Packet Tracer

Figure 5-1. Topology Diagram

Equipment Required

This lab uses the following equipment:

 Cisco router with voice IOS
 Switch that supports voice VLANs
 Completed Packet Tracer Lab 3-2 file
 Two or more IP Phones (desk phone or soft phone on PC or Windows VM). Remember
that you will need a power source such as a PoE switch or power brick to use the
physical phones.

Learning Objectives

Upon completion of this lab, you will be able to

 Configure telephony services in CUCME
 Manually register phones
 Place phone calls between two phones in the same system

Scenario
Pod
/ DHCP
Rac Host DHCP Pool Default Option
k Name VLAN Name VLAN# IP Address Exclusion DHCP Pool Router 150
1 RTRPod1 Management 11 10.11.0.1/24        
    Data 10 10.10.0.1/24 10.10.0.1-10 10.10.0.0/24 10.10.0.1 10.10.0.1
    Voice 15 10.15.0.1/24 10.15.0.1-10 10.15.0.0/24 10.15.0.1 10.15.0.1
  SWPod1   11 10.11.0.2/24     10.11.0.1  

Phone Extensions (Ephone-dn) - x5010 to x5039

Shiny Objects Inc. (SOI) wants to establish internal calls using the new system. These
instructions refer to the Pod Addressing Table in Appendix A to determine the phone numbers,
IP addresses, and VLAN numbers used for your pod. Wherever an x is shown, substitute the
pod number. For this Packet Tracer lab we are using Pod 1.

Task 1: Load Prior Configuration

Lab 5-1: Basic Manual Phone Configuration Using the CLI – Packet Tracer

This lab is based on the configuration from either Lab 3-2. If necessary, load the configuration
for both the switch and router. However, do NOT connect the phones to the switch until later.
Connect a PC to the switch and verify that it can ping the router and switch management
addresses. Troubleshoot if necessary.
Task 2: Configure Telephony-Service

Telephony-service configuration mode is where settings that impact the entire CUCME system
are configured. There are three settings that must be configured (four in older versions of
CUCME) before phones can register, and one optional setting that avoids common phone
registration mistakes.

Step 2-1: Disable Auto Phone Registration

Note
Disabling autoregistration of phones is an optional step. However, allowing phones to
autoregister can cause problems if MAC addresses are entered incorrectly. Disabling
autoregistration eliminates this problem.

Versions of CUCME prior to 4.0 (IOS Release 12.4(9)T) don’t have this command, so if you are
using an earlier version, make sure to double-check the MAC addresses of the phones when
registering them.

RtrPodx(config)# telephony-service
RtrPodx(config-telephony)# no auto-reg-ephone

Step 2-2: Establish the Maximum Number of Phones Allowed to Register

Before any IP phones can register with the system, the maximum number allowed to register
must be set. The upper limit of the maximum is dependent on the model of the router; the higher
the model number, the more IP Phones CUCME will support. While it might seem best to set the
number to the maximum a given router will support, each reservation consumes resources on
the router; thus it is better to set the number at slightly above the currently expected number of
phones. (The maximum should also be set no higher than the number of licenses purchased.) It
can be increased later (up to the maximum supported by the router model) without disrupting
operations.

Discover the maximum number of phones that your CUCME router will support by using the
question mark (?) with the max-ephones command:

RtrPodx(config-telephony)# max-ephones ?

What is the maximum number of phones your system can register? ____42___________

Now set the maximum number of phones to five:

RtrPodx(config-telephony)# max-ephones 5

Step 2-3: Establish the Maximum Number of Directory Numbers (Phone Numbers)

Before any phones can register with the system, the maximum number of directory numbers
Lab 5-1: Basic Manual Phone Configuration Using the CLI – Packet Tracer

must also be set. The upper limit of the maximum is dependent on the model of the router, but it
will be higher than the number of phones. (If you consider that directory numbers will be used
for intercoms, paging, voicemail numbers, and so on, you can see why there are more numbers
allowed than phones.) Again, each directory number will consume resources on the router; thus
it is better to set the number at slightly above the currently expected number of directory
numbers needed. As with the phones, it can always be increased later (up to the maximum
supported by the router model) without disrupting operations.

Discover the maximum number of directory numbers your CUCME router will support by using
the question mark (?) with the max-dn command:

RtrPodx(config-telephony)# max-dn ?

What is the maximum number of directory numbers your system can support? ____144______

Now set the maximum number of directory numbers to ten:

RtrPodx(config-telephony)# max-dn 10

Step 2-4: Set the IP Address Used by CUCME

Before any phones can register with the system, CUCME needs to know the IP address used to
receive requests and respond to IP Phones. The ip source-address command tells the system
the IP address to use. By default, TCP port 2000 is used, but it can be specified with the port
option. Any valid IP address on the router can be used, but the address of the voice VLAN
interface is the best choice in this case. Remember that wherever an x is shown, substitute the
pod number.

Note
The best option for the source address is a loopback address, as loopback interfaces are
always up. Using a physical interface (or subinterface) address could cause the system to stop
responding if that interface is down, even if phones are connected to other interfaces that are
up. However, in this configuration, if the interface is down, all phones are disconnected, so a
loopback is not necessary.

RtrPodx(config-telephony)# ip source-address 10.x5.0.1

Tip:
Older CUCME versions might require you to add the port 2000 option to the end of the
command. Do not use on Cisco 2800 Series Routers.

Troubleshooting:
If phones do not load, remove ip source-address 10.x5.0.1 command and re-add command.
No ip source-address 10.x5.0.1 port 2000
ip source-address 10.x5.0.1

Tip:
It is normal to receive %IPPHONE-6-REG_ALARM since auto phone registration has been
disabled. Power off the phones until the ephone is configured if the messages are annoying.
Lab 5-1: Basic Manual Phone Configuration Using the CLI – Packet Tracer

Step 2-5: Create the Default Template Files

With newer versions of CUCME, the system will automatically create the default template files
for the phones after all required options are entered. A message will say

Updating CNF files

CNF files update complete

On older versions of CUCME, it might be necessary to create the template files manually using
the create cnf-files command in telephony-service mode.

RtrPodx(config-telephony)# create cnf-files

Tip
Sometimes, if a change is made in the Telephony Services section of the config, and the
changes do not show on the phones, using the no create cnf-files and then the create cnf-
files commands to manually re-create the template files (followed by restarting the phones) will
fix the problem.

RtrPodx(config-telephony)# end

Task 3: Configuring Directory Numbers

A directory number (phone number) is represented in Cisco configs as an ephone-dn. (Think

directory number.) Ephone-dns can be single-line, dual-line, and as of CUCME 4.1, octo-line.
The distinction is in the number of simultaneous audio channels (lines) usable per phone button.
For example, call waiting and transferring a caller to a third party need two audio channels. (The
call transfer needs one channel for the original caller and another to establish the connection to
the third party.) For this reason, most desk phones will use dual-line dns. The single-line dn is
used for features like intercoms and paging, where dual-lines are not needed. Octo-line dns
have eight audio channels per button. You might wonder, “Why not just make them all octo
lines?” Each line created consumes resources on the router, so it is best to allocate the correct
number of lines to each directory number. Be aware that you cannot later change the number of
lines on a dn. To change the number of lines, you have to use the no command to remove the
entire dn and then re-create it. Note: Packet Tracer only supports the use of single-line dn.

Step 3-1: Create an Ephone-dn

The ephone-dns are created in global configuration mode, and each dn is assigned a tag
number. The tag number has to be less than the max-dn configured in telephony service, so
usually you start with 1.

RtrPodx(config)# ephone-dn 1
*Sep 9 18:30:43.451: %LINK-3-UPDOWN: Interface ephone_dsp DN 1.1, changed state to up

RtrPodx(config-ephone-dn)# number <first_extension_assigned_to_your_pod>

For example, Pod 1 would use number 5010

Lab 5-1: Basic Manual Phone Configuration Using the CLI – Packet Tracer

Tip
If you make an ephone-dn with an incorrect number of lines (for example, single-line when you
wanted dual- line), you have to remove the ephone-dn using the no ephone-dn number
command and re-create it.

Step 3-2: Repeat to Create the Next Three Phone Numbers

Create three more numbers so that there are more to assign for the phones.

RtrPodx(config-ephone-dn)# ephone-dn 2
RtrPodx(config-ephone-dn)# number <second_extension_assigned_to_your_pod>
RtrPodx(config-ephone-dn)# ephone-dn 3
RtrPodx(config-ephone-dn)# number <third_extension_assigned_to_your_pod>
RtrPodx(config-ephone-dn)# ephone-dn 4
RtrPodx(config-ephone-dn)# number <fourth_extension_assigned_to_your_pod>
RtrPodx(config-ephone-dn)# exit

Task 4: Manually Configure an Ephone and Associate the First Directory Number

In a traditional analog or PBX phone system, a directory number (phone number) is associated
with a wall jack. Any phone plugged into a wall jack will have the phone number assigned to that
jack. Move the phone to another wall jack and the number on the phone changes (unless the
line in the jack is manually changed). However, with IP Phones, the phone is identified by the
MAC address assigned to it, so it does not matter where in the network the phone is located. As
long as the phone can reach the Call Agent, it will be have the same directory numbers.
CUCME uses the ephone to connect directory numbers (ephone-dns) to the MAC address of
the phone.

Step 4-1: Get the MAC Address of the First Phone

There are three main ways to get the MAC address of a phone:

From the box of the IP Phone: The outside of the box has both the printed MAC address and
a bar code. The bar code makes it easier to scan and enter related information (such as
extension and username) for bulk importing.

From the back of the IP Phone: (Soft phones use the MAC address of the PC.) Turn the
phone over and find the bar code with 12 hex digits. This method can also benefit from using a
bar-code scanner to capture the MAC address for bulk import.

From the screen of the IP Phone: Press the Settings button and then navigate to Network
Settings to show the MAC address. (The disadvantage of this option is that it requires the phone
to be powered on.) Don’t use this method if autoregistration in CUCME is still enabled.

Packet Tracer: Finding the MAC address in Packet Tracer can be challenging, but there are
multiple ways. Hovering over the phone will display the MAC associated with the correct Voice
VLAN. Verify the MAC address in the switch MAC Address Tables, or check the DHCP Bindings
(IP to MAC Address) on the DHCP server.

No matter which method you use, when entering a MAC address into the router, you need to
Lab 5-1: Basic Manual Phone Configuration Using the CLI – Packet Tracer

enter it in the format of three groups of four hex numbers, separated by periods. Thus, a phone
with MAC address 1234567890ab would be entered as 1234.5678.90ab in the ephone
configuration.

What is the MAC address of the first phone? __________________

Step 4-2: Create an Ephone and Assign the MAC Address

Just like the ephone-dns, the ephone requires a tag number that must be less than the max-
ephone number defined in telephony- service. After entering config-ephone mode, the mac-
address command is mandatory before any other command can be issued.

Note
If your CUCME version does not support the no auto-reg-ephone command in telephony-
service, double- check that the MAC address entered matches the phone. If it is not correct, the
phone will autoregister, but not show in the config or get a phone number assigned.

RtrPodx(config)# ephone 1
RtrPodx(config-ephone)# mac-address <mac_address_of_your_first_phone>
For example, a phone with mac address 1234567890ab would use mac-address
1234.5678.90ab.

Step 4-3: Assign the First Directory Number to the First Button on the Phone

The next step is to associate one of the ephone-dns to the ephone. Most Cisco phone models
are capable of having more than one line assigned to them, and they use line buttons on the
phone for the caller to select the line to use. (See Figure 5-2.)
Lab 5-1: Basic Manual Phone Configuration Using the CLI – Packet Tracer

Figure 5-2. Buttons on a Cisco IP Phone

There are many options when assigning an ephone-dn to a button. The most common option is
to use the colon (:) to connect the physical button on the phone to the ephone-dn. Use the
question mark (?) to see the options:

RtrPodx(config-ephone)# button ?
LINE button-index:dn-index pairs example 1:2 2:5
Configuration line:button with separator feature options:
: normal phone lines
example button 1:2 2:5
s silent ring, ringer muted, call waiting beep muted
example button 1s2 2s5
b silent ring, ringer muted, call waiting beep not muted
example button 1b2 2b5
f feature ring
example button 1f2 2f5
see also 'no dnd feature-ring'
<output omitted>
RtrPodx(config-ephone)# button 1:1
RtrPodx(config-ephone)# end

The button 1:1 command in the example ties the first line button to the extension assigned to
the first ephone-dn. If the command had been button 1:2, the first line button would have the
extension assigned to the second ephone-dn. Likewise, if the command had been button 5:3,
the fifth line button (counting down the display) would have the extension assigned to the third
Lab 5-1: Basic Manual Phone Configuration Using the CLI – Packet Tracer

ephone-dn. Note: Packet Tracer only supports the use of one button, button 1.

Step 4-4: Assign the Ephone Model Type

For the router to properly recognize the features on each type of phone, it is necessary to tag
each ephone with the model. For example, the directory on the phone will not work without a
phone type assigned. Handily, the show ephone attempted- registrations command will
display the model as well as the MAC address. Note: The Cisco IP Communicator uses the
type CIPC for the command.

RtrPodx(config-ephone)# do show ephone attempted-registrations

Attempting Mac address:

Num Mac Address DateTime DeviceType

-----------------------------------------------------------------------------
1 001D.705E.ABF 20:04:37 CDT Sun Jan 1 7962
2 0021.A084.F3A223:56:44 CDT Sun Jan 1 7975
-----------------------------------------------------------------------------
Num Mac Address DateTime DeviceType

RtrPodx(config-ephone)# type <model_of_your_phone>

For example, if ephone 1 is a 7962, use type 7962

Step 4-5: Connect the First Phone to the Switch

Note
Do not connect other phones at this time.

If using a physical phone, connect the cable from the SW port to the switch. If using a soft
phone, make sure that the computer is connected to the switch and start the software. The
phone should go through the bootup process and register with CUCME. On the router, you will
see a registration status message. In this output, a Cisco phone with MAC address
0022.555e.ef47 and IP address 10.115.0.11 has registered to ephone 1:

RtrPodx#
*Sep 7 21:55:15.119: %IPPHONE-6-REG_ALARM: 25: Name=SEP0022555EEF47 Load= SCCP42.8-
4-2S Last=Initialized
*Sep 7 21:55:15.147: %IPPHONE-6-REGISTER: ephone-1:SEP0022555EEF47 IP:10.115.0.11
Socket:1 DeviceType:Phone has registered.

The phone will then display the number assigned to ephone-dn 1 on the display. If you lift the
phone handset, you should hear a dial tone.

Note
If the phone does not register, start troubleshooting using the IP Phone Registration process as
a guide. Use the Settings button on the phone to view the networking settings.
Questions to ask:

 Is the phone (for physical phones) in a port with the voice VLAN active and assigned?
Lab 5-1: Basic Manual Phone Configuration Using the CLI – Packet Tracer

(Soft phones will be in the data VLAN.)

 Is the phone (or PC in the case of soft phones) getting an IP address from DHCP? Use
the show ip dhcp binding command to verify.
 Is the DHCP option 150 set to an IP address on the router? (For soft phones that don’t
register, make sure
 that the option 150 was included in the Data DHCP pool. If necessary, assign the IP
address of the Call Agent in the soft phone manually.)
 Are all the required telephony-service items entered and the cnf-files created, as shown
in Steps 2-1 to 2-5? Use the show run command to verify that the required commands
are entered.
 Has the phone previously registered to a CUCM version 8.0 or later system? If so, the
phone wants to keep the previous registration and might refuse to register to CUCME.
To clear the prior registration settings, see the notes in the hardware section of the
Introduction.
If you are still encountering registration problems, try using Wireshark as demonstrated in Lab
5-4 to see where to troubleshoot.

Task 5: Manually Configure a Second Phone

In CUCME, there is an easier way to get the MAC addresses and register a few phones, if you
have the no auto-reg-ephone command in telephony-service. With autoregistration disabled,
you can connect the phone and the phone registration will fail. This allows you to use the show
ephone attempted-registrations command to get the information.

Note
If your CUCME version does not support the no auto-reg-ephone command in telephony-
service, skip Step 5-1 and repeat Steps 4-1 and 4-2 for the second IP Phone. Then, proceed to
Step 5-2.
Step 5-1: Connect the Second Phone to the Switch
Connect the second phone to the switch. A message will display on the router console showing
a registration alarm. The MAC address is displayed in the output of the alarm, but it is not in the
right format. Use the show ephone attempted-registrations command to obtain the MAC
address in the right format. In the following example, a Cisco 7975 Phone with MAC address
0022.555D.928A attempted to register, but there is no matching ephone config. The output of
the show ephone attempted-registrations command not only gives the MAC address in the
right format, but it also shows the model type of the phone (which is useful to have, as shown in
Lab 5-2).

RtrPodx#
*Sep 7 22:13:59.770: %IPPHONE-6-REG_ALARM: 25: Name=SEP0022555D928A Load=
SCCP75.8-4-2S Last=Initialized

RtrPodx# show ephone attempted-registrations

Attempting Mac address:

Num Mac Address DateTime DeviceType

Lab 5-1: Basic Manual Phone Configuration Using the CLI – Packet Tracer

-----------------------------------------------------------------------------

1 0022.555D.928A 17:16:53 cdt Wed Sep 7 2011 7975

-----------------------------------------------------------------------------
Num Mac Address DateTime DeviceType

You can now copy and paste the MAC address information:

RtrPodx# config t
RtrPodx(config)# ephone 2
RtrPodx(config-ephone)# mac-address <mac_address_listed_in_output>
Step 5-2: Assign the Second Directory Numbers to the Second Phone

Assuming that the second phone has more than one line button, you can assign more than one
ephone-dn. The line buttons can be assigned as separate commands, or they can be assigned
together as one command. In this output, we assign the first line button to the extension
assigned to ephone-dn 2 and the second line button to the extension assigned to ephone-dn 1
(the same directory assigned to ephone 1 button 1).

RtrPodx(config-ephone)# button 1:2

On real equipment, you might find that the phone has already registered before you type the
button command and it does not show any extensions on the phone display. While in config-
ephone mode, you can use either the restart or reset command to update the phone. The
phone will unregister and then reregister.

RtrPodx(config-ephone)# restart !Not Supported in Packet Tracer

restarting 0022.555D.928A
RtrPodx(config-ephone)#
*Sep 7 22:34:36.674: %IPPHONE-6-UNREGISTER_NORMAL: ephone-
2:SEP0022555D928A IP:10.115.0.12 Socket:5 DeviceType:Phone has unregistered normally.
RtrPodx(config-ephone)#
*Sep 7 22:34:38.438: %IPPHONE-6-REG_ALARM: 23: Name=SEP0022555D928A Load=
SCCP75.8-4-2S Last=Reset-Restart
*Sep 7 22:34:38.466: %IPPHONE-6-REGISTER: ephone-2:SEP0022555D928A
IP:10.115.0.12 Socket:6 DeviceType:Phone has registered.

Note
The restart command tells the phone to update the configuration. The reset command tells the
phone to completely reboot, including the full power-up boot process. One hint to remember
which does which: The shorter the command, the longer it takes the phone to be back in
service.

Step 5-3: Make a Call

Place a call from the first phone to the directory number assigned on ephone-dn 2 (second
extension for your pod). When you call from one phone to the other, the display on the ringing
phone will show the extension that is called/calling.
Lab 5-1: Basic Manual Phone Configuration Using the CLI – Packet Tracer

Unlike an analog home phone, where someone can pick up another extension and join the
conversation, only one phone can use an ephone-dn at a time.

Step 5-4: Verify the Phone Status Using the Show Ephone

You can verify the phone status using the show ephone command. In this output, the directory
number and extensions are assigned to line buttons 1. Notice there is a channel 1 (CH1) and
channel 2 (CH2) status of IDLE for both dns, as the ephone-dns were created as dual-line and
the phone is not in use.

RtrPodx# show ephone

ephone-1[0] Mac:0022.555E.EF47 TCP socket:[1] activeLine:0 whisperLine:0
REGISTERED in SCCP ver 20/12 max_streams=5
mediaActive:0 whisper_mediaActive:0 startMedia:0 offhook:0 ringing:0 reset:0 reset_sent:0
paging 0 debug:0 caps:12
IP:10.115.0.11 52497 7962 keepalive 60 max_line 6 available_line 6 button 1: dn 1
number 5330 CH1 IDLE CH2 IDLE shared button 2: dn 4 number 5333 CH1
IDLE CH2 IDLE
Preferred Codec: g711ulaw
<output omitted>

Now place a call from line button 1 on the second phone to the extension assigned to button 2
of the first phone (extension 5333 in this example), and while the phone is ringing, run the
command again. You will notice the status of button 2 CH1 is now RINGING, and at the end of
the ephone-1 output, it shows that a call is ringing on line 2.

RtrPodx# show ephone

ephone-1[0] Mac:0022.555E.EF47 TCP socket:[1] activeLine:0 whisperLine:0
REGISTERED in SCCP ver 20/12 max_streams=5
mediaActive:0 whisper_mediaActive:0 startMedia:0 offhook:0 ringing:1 reset:0 reset_sent:0
paging 0 debug:0 caps:12
IP:10.115.0.11 52497 7962 keepalive 121 max_line 6 available_line 6

button 1: dn 1 number 5330 CH1 IDLE

button 2: dn 4 number 5333 CH1 RINGING
Preferred Codec: g711ulaw
call ringing on line 2
<output omitted>

Answer the call and run the command again. The status now shows the call as CONNECTED
and the IP addresses of both phones. There are also statistics about the packets of the voice
conversation.

RtrPodx# show ephone

ephone-1[0] Mac: 0022.555E.EF47 TCP socket:[1] activeLine:2 whisperLine:0
REGISTERED
in SCCP ver 20/12 max_streams=5
mediaActive:1 whisper_mediaActive:0 startMedia:1 offhook:1 ringing:0 reset:0 reset_sent:0
paging 0 debug:0 caps:12
IP:10.115.0.11 52497 7962 keepalive 127 max_line 6 available_line 6 button 1: dn 1
number 5330 CH1 IDLE CH2 IDLE shared button 2: dn 4 number 5333 CH1
Lab 5-1: Basic Manual Phone Configuration Using the CLI – Packet Tracer

CONNECTED CH2 IDLE

Preferred Codec: g711ulaw
Active Call on DN 4 chan 1 :5333 10.115.0.11 20168 to 10.115.0.12 23234 via
10.115.0.11
G711Ulaw64k 160 bytes no vad
Tx Pkts 710 bytes 122120 Rx Pkts 709 bytes 121948 Lost 0
Jitter 0 Latency 0 callingDn 2 calledDn -1

<output omitted>

Step 5-5: Save Configuration files and Packet Tracer File for the Next Lab

The next lab shows configuring beyond the basics required to make two phones ring. Save the
Packet Tracer file and the configuration of the router and switches for the next lab.

Updated 4/27/2021