CUCME-CUE Lab 2 – Baltimore Basic CUCME System Setup

Now that there is basic IP connectivity between Baltimore and New York, as outlined in CUCME-CUE Lab 1, this next series of lab tasks will involve setting up the SCCP-based Baltimore CUCME system.

Baltimore Basic CUCME System Setup Prerequisites

Prior to configuring the CUCME phone tasks, the router requires the specific CUCME files to be installed on the router flash. If this task hasn’t been previously completed, now is the time to so. There are a couple of ways to accomplish this prerequisite. The processes and procedures for installing the CUCME files on the router flash are described in the Installing and Upgrading Cisco Unified CME Software chapter of the Cisco Unified Communications Manager Express System Administrator Guide.

One option is to download the appropriate CUCME ZIP file, which for the lab is cme-124-22T2.zip. The next step would be to extract the ZIP to a directory on your TFTP or FTP server. Once that is complete, you can extract cme-full-7.0.0.1.tar on the router via TFTP or FTP. This process installs all of the CUCME files, including all SCCP phone loads, ringtones, GUI files, and BACD scripts. This procedure also places all of the CUCME files on the router flash into a hierarchical directory structure, which is nice. However, this option uses the largest amount of space on your router flash, since it installs all CUCME files, such as phone loads for phones which you may not be using in your lab.

The second option is to only load and extract the necessary CUCME files necessary to complete this lab. For my Baltimore router and accompanying IP Phones, this includes the following TAR files:

cme-gui-7.0.0.1.tar
cmterm-7942_7962-sccp.8-3-3S.tar
ringtone.tar

While this option uses far less flash space, it also extracts each tar files to the root of flash. Depending on the number of files on your flash, this could become unwieldy. Therefore, I first create a directory for each tar file on the flash. Then, I extract each tar file to the appropriate flash directory. For example, below is the output for creating the “ringtones” directory, followed by extracting files to that directory. Please note, this procedure will later require the use of the alias command when serving these files on the router’s TFTP server.

Baltimore#mkdir flash:ringtones
Create directory filename [ringtones]?
Created dir flash:ringtones

Baltimore#dir flash:
Directory of flash:/

1 -rw- 58816728 Dec 19 2008 17:31:38 -05:00 c2800nm-adventerprisek9_ivs_li-mz.124-22.T.bin
2 drw- 0 Oct 24 2008 23:28:00 -04:00 gui
31 drw- 0 Oct 24 2008 23:25:16 -04:00 phone
64 -rw- 660 Oct 25 2008 00:26:44 -04:00 vlan.dat
66 drw- 0 Dec 31 2008 09:48:32 -05:00 ringtones

127909888 bytes total (61579264 bytes free)

Baltimore#archive tar /xtract ftp://10.1.1.33/ringtone.tar flash:/ringtones
Loading ringtone.tar
extracting Analog1.raw (8160 bytes)!
extracting Analog2.raw (8160 bytes)
extracting AreYouThere.raw (5280 bytes)
extracting AreYouThereF.raw (5040 bytes)
extracting Bass.raw (8160 bytes)
extracting CallBack.raw (12240 bytes)
extracting Chime.raw (16040 bytes)
extracting Classic1.raw (8160 bytes)
extracting Classic2.raw (16080 bytes)
extracting ClockShop.raw (10800 bytes)
extracting DistinctiveRingList.xml (2823 bytes)
extracting Drums1.raw (9600 bytes)
extracting Drums2.raw (13440 bytes)
extracting FilmScore.raw (15840 bytes)
extracting HarpSynth.raw (16080 bytes)
extracting Jamaica.raw (8160 bytes)
extracting KotoEffect.raw (16080 bytes)
extracting MusicBox.raw (12720 bytes)
extracting Piano1.raw (8160 bytes)
extracting Piano2.raw (15360 bytes)
extracting Pop.raw (9360 bytes)
extracting Pulse1.raw (7200 bytes)
extracting Ring1.raw (4000 bytes)
extracting Ring2.raw (4000 bytes)!
extracting Ring3.raw (4000 bytes)
extracting Ring4.raw (4000 bytes)
extracting Ring5.raw (4000 bytes)
extracting Ring6.raw (4000 bytes)
extracting Ring7.raw (4000 bytes)
extracting RingList.xml (495 bytes)
extracting Sax1.raw (10800 bytes)
extracting Sax2.raw (14160 bytes)
extracting Vibe.raw (16080 bytes)
[OK - 326144/4096 bytes]

Lab 2.1 – Baltimore Basic CUCME Setup Tasks
1. Setup the CUCME System Parameters on the Baltimore router. You may not use the CUCME setup utility or any sort of auto registration process.
2. Configure the Baltimore Phones to update their phone loads.
3. The CUCME service should be configure to support the appropriate localization, time-zone, a 12 hour time format, and a Month-Day-Year format.
4. Create an appropriate E.164 dial-pattern.
5. Each phone and should also be able to customize their ringtones beyond the default chirp ringtone.
6. Anticipate the need to transfer calls between Baltimore and New York
7. Enable the wideband codec by default for all phones.
8. Create the appropriate GUI Administrator parameters
9. Create GUI access for Fuzzy Dunlop with parameters separate from the Administrator.
10. Phone should have a message or display that indicates “Ballplayers, LLC Baltimore”.
11. Each user’s phone should also display his/her name and full E.164 number.
12. Configure the phone extensions based on the diagram depicted in CUCME-CUE Labs – Background.
13. Arliss Michaels, as the Baltimore Branch Manager, requires the ability to make up to eight simultaneous calls on his extension. However, only two incoming calls may be accepted. Arliss also requires a 6-button phone.
14. All other users require the ability to have caller-id, transfer calls, and place conference calls. However, these other users should not be able to have more than two calls per line appearance.

Lab 2.2 – Baltimore Basic CUCME Setup Verification
1. One of the first tasks is to configure the Baltimore router to act as a TFTP server for the phone loads, configuration files, and ringtones. As described above in the Baltimore Basic CUCME System Setup Prerequisites section, because the various files have been placed in a hierarchical structure in the flash, it is necessary to configure some of the TFTP commands with the alias option. This is especially applicable to the phone load and ringtones components. A sample out is below, truncated for brevity.

Baltimore#sh run
Building configuration...
!
!output omitted!
!
!comment: ringtones configured with alias!
!
tftp-server flash:ringtones/Analog1.raw alias Analog1.raw
tftp-server flash:ringtones/Analog2.raw alias Analog1.raw
tftp-server flash:ringtones/AreYouThere.raw alias AreYouThere.raw
tftp-server flash:ringtones/AreYouThereF.raw alias AreYouThereF.raw
!
!comment: gui commands do not require alias, refer to readme file with the CUCME files!
!
tftp-server flash:gui/admin_user.html
tftp-server flash:gui/admin_user.js
!
!comment: phone load commands with alias!
!
tftp-server flash:phone/7942-7962/apps42.8-3-2-27.sbn alias apps42.8-3-2-27.sbn
tftp-server flash:phone/7942-7962/cnu42.8-3-2-27.sbn alias cnu42.8-3-2-27.sbn
tftp-server flash:phone/7942-7962/cvm42sccp.8-3-2-27.sbn alias cvm42sccp.8-3-2-27.sbn
tftp-server flash:phone/7942-7962/dsp42.8-3-2-27.sbn alias dsp42.8-3-2-27.sbn
tftp-server flash:phone/7942-7962/jar42sccp.8-3-2-27.sbn alias jar42sccp.8-3-2-27.sbn
tftp-server flash:phone/7942-7962/SCCP42.8-3-3S.loads alias SCCP42.8-3-3S.loads
tftp-server flash:phone/7942-7962/term42.default.loads alias term42.default.loads
tftp-server flash:phone/7942-7962/term62.default.loads alias term62.default.loads
!output omitted!

2. You can verify the telephony-service parameters either via a “show telephony-service” command or, of course, “show run”. The “show telephony-service” will provide you with more details on the default parameters which may or may not show in the running-config, such as the network-locale, user-locale, and date-format, depending on the exact configuration.

Below is the output for the “show run begin telephony-service”. Pay particular attention to some of the require tasks, such as the G.722 codec, system message, transfer requirements, and dial-plan.

Baltimore#sh run begin telephony-service
telephony-service
em logout 0:0 0:0 0:0
codec g722-64
max-ephones 42
max-dn 144
ip source-address 10.1.12.1 port 2000
service phone g722CodecSupport 2
service phone handsetWidebandEnable 1
service phone headsetWidebandEnable 0
service phone handsetWidebandUIControl 0
system message Ballplayers, LLC Baltimore
load 7942 SCCP42.8-3-3S
load 7962 SCCP42.8-3-3S
time-zone 12
dialplan-pattern 1 41055510.. extension-length 4
max-conferences 8 gain -6
web admin system name Cisco123 password Cisco123
web admin customer name Fuzzy password Dunlop
transfer-system full-consult
transfer-pattern 1...
transfer-pattern 2...
create cnf-files version-stamp 7960 Dec 31 2008 12:12:51
!

3. The configuration setup for the phones and directory numbers is fairly straight forward. All lines have been configured as dual-lines, with the exception of Arliss Michaels, who has an octal-line. Also pay attention to how Arliss’s phone has been configured to support the requirement to support eight outbound calls, but all incoming calls after a second call are diverted.

Baltimore#sh run begin ephone-dn 1 dual-line
ephone-dn 1 dual-line
number 1001
label Cal Ripken 1001
description 410-555-1001
name Cal Ripken
!
!
ephone-dn 2 dual-line
number 1002
label Nick Markakis 1002
description 410-555-1002
!
!
ephone-dn 3 dual-line
number 1003
label Joe Flacco 1003
description 410-555-1003
name Joe Flacco
!
!
ephone-dn 4 dual-line
number 1004
label Todd Heap
description 410-555-1005
name Todd Heap
!
!
ephone-dn 5 octo-line
number 1005
label Arliss Michaels
description 410-555-1005
name Arliss Michaels
!
!
ephone 1
device-security-mode none
description Cal Ripken
mac-address 0021.D8BA.23A1
codec g722-64
type 7942
button 1:1
!
!
!
ephone 2
device-security-mode none
description Nick Markakis
mac-address 0000.0000.1111
codec g722-64
type 7942
button 1:2
!
!
!
ephone 3
device-security-mode none
description Joe Flacco
mac-address 0023.331A.EDCC
codec g722-64
type 7942
button 1:3
!
!
!
ephone 4
device-security-mode none
description Todd Heap
mac-address 0000.0000.2222
codec g722-64
type 7942
button 1:4
!
!
!
ephone 5
device-security-mode none
description Arliss Michaels
mac-address 001F.CAE9.2CCE
busy-trigger-per-button 2
codec g722-64
type 7962
button 1:5
!

4. Finally, a “show ephone registered” will verify that your real IP Phones have registered with CUCME. And of course, placing a few phone calls will also verify a proper configuration.

Baltimore#sh ephone registered

ephone-1[2] Mac:0021.D8BA.23A1 TCP socket:[2] activeLine:0 REGISTERED in SCCP ver 12/9
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0 caps:12
IP:10.1.12.20 50965 7942 keepalive 42 max_line 2
button 1: dn 1 number 1001 CH1 IDLE CH2 IDLE
Preferred Codec: g722-64

ephone-3[0] Mac:0023.331A.EDCC TCP socket:[3] activeLine:0 REGISTERED in SCCP ver 12/9
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0 caps:12
IP:10.1.12.16 53114 7942 keepalive 41 max_line 2
button 1: dn 3 number 1003 CH1 IDLE CH2 IDLE
Preferred Codec: g722-64

ephone-5[4] Mac:001F.CAE9.2CCE TCP socket:[1] activeLine:0 REGISTERED in SCCP ver 12/9
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0 caps:12 privacy:1
IP:10.1.12.18 49758 7962 keepalive 41 max_line 6

CUCME-CUE Lab 2 Wrap-up
The next series of labs will tackle the configuration of CUCME on the New York router. However, the configuration will be based on SIP phones, which presents some different challenges and limitations.

References:
Au, Danelle, et. al. (2005). Cisco IP Communications Express: CallManager Express with Cisco Unity Express. Indianapolis: Cisco Press.

Cisco Systems. Cisco Unified Communications Manager Express System Administrator Guide. Available online.