CUCME-CUE Lab 4 – CUCME POTS & VoIP Dial Peers

So far, Fuzzy Dunlop is impressed with the Cisco Unified Communications Express pilot in the Baltimore and New York offices. However, he has now instructed you to configure the two CUCME routers to interface with the PSTN as well as providing VoIP calls between the two locations over the frame relay link. Your tasks are as follows below.

Lab 4.1 – CUCME POTS and VoIP Dial Peer Tasks
1. Fuzzy is a cheap CIO – he has only provisioned the PRI for twelve channels. Configure an inbound POTS dial peer to support this.
2. Both Arliss Michaels and Ari Gold require a special inbound POTS line on top of their DID number associated with the PRI circuit. In Baltimore, make sure 410-555-5001 is routed to Arliss’s phone and 212-555-6001 is routed to Ari’s phone in New York. Ensure that Arliss and Ari always know who is calling inbound on these numbers.
3. Internal users must dial “9” to place and outside call. When dialing “9”, a different dial tone should be heard on the internal phones.
4. The PRI circuits at both locations should take precedence over the POTS connections for outbound calls.
5. Outbound destination patterns should be configured in such a way to allow outbound calls to be placed as quickly as possible, without any unnecessary delay.
6. Create appropriate inbound dialing for support the DID range and dial plans depicted in the diagram in Lab 3.1.
7. The security phones depicted in the diagram in Lab 3.1 should be mapped appropriately 410-555-5002 and 212-555-6002.
8. Internal users should be able to dial “H-E-L-P” on their IP Phones, which will ring the analog security phones at each location.
9. Configure an appropriate VOIP dial peer to allow four-digit dialing over the Frame Relay link. Maintain the G.722 codec (we’ll cover transcoding in a subsequent lab).
10. Configure each CUCME to route internal four-digit dial calls out the PSTN in the event of a WAN failure. Make sure the IP path is preferred first; the PRI circuit second; the POTS lines third.
11. You may not use any sort of digit translation on the Baltimore router to achieve task #10.
12. You must use digit translation on the NY router to achieve task #10.
13. Verify calling, including routing calls to the PSTN during a WAN failure.

Lab 4.2 – CUCME POTS and VoIP Dial Peer Task Verification
Most of the tasks in the lab are fundamentally similar, and in some instances, the same, as some of the VOIP and POTS dial peer tasks in the VOIP Fundamentals Labs. Therefore, rather than repeating myself, I will cover the tasks that are either new or different from the previous VOIP Fundamentals labs.


1. When configuring the MFT on the CUCME routers, I only configure twelve (12) B-Channels. The main reason is simply to conserve DSP resources for later configuration tasks, such as transcoding and conferencing.

!
controller T1 0/0/0
cablelength short 110
pri-group timeslots 1-12,24
!

2. To accomplish the task of routing one of the inbound POTS (FXO) lines directly to either Arliss or Ari, simply configure those FXO ports as a plar obx connection. You’ll also do the same for the security phone at each location.

!
voice-port 0/1/0
connection plar opx 2005
description inbound 212-555-6001
caller-id enable
!

3. To allow secondary dial-tone for external calls, simply add the “secondary-dialtone” command under the telelphony service. However, I could not get secondary dial-tone to work on the SIP CUCME router. The CUCME Administration Guide is extremely vague as to whether SIP CUCME supports this. There is no “secondary-dialtone” equivalent command under voice register global mode.

telephony-service
secondary-dialtone 9

User error (me) perhaps? Anyone else out there get secondary dial-tone to work on their SIP CUCME router?

4. There are at least two ways to configure the “H-E-L-P” requirement. One fairly simple approached is to configure another POTS dial-peer for destination-pattern 4357 (HELP), mapping it to the FXS with the attached analog device.

A second possibility is to create a translation rule, and then map this rule to each ephone-dn. For example:

!
translation-rule 1
Rule 0 ^4357 1611
!
!
ephone-dn 1 dual-line
translate called 1

5. I added the call fallback to each router. This significantly speeds up the process of falling back to a PSTN dial-peer in the event of a VOIP/WAN link failure. Below is an output of a call being routed over the PSTN (PRI) during a WAN failure.

##Shutting down the Frame Relay link##

Baltimore(config)#int s0/2/0
Baltimore(config-if)#shut

NewYork#sh call fallback cache

Fallback Mode : Active

Type Id IP Address Codec Delay Loss ICPIF Reject Accept
---- ----- ---------- ----- ----- ---- ----- ------ ------
ICMP 1 172.16.1.1 No Codec N/A 100 N/A 0 0

1 active probes

##placing a call from 2005 to 1005##

NewYork#
Jan 15 05:03:04.578: %ISDN-6-CONNECT: Interface Serial0/0/0:11 is now connected to 4105551005 N/A
Jan 15 05:03:04.578: %ISDN-6-CONNECT: Interface Serial0/0/0:11 is now connected to 4105551005 N/A
NewYork#

6. One additional comment/observation before providing the pertinent “show run” edits for each CUCME router. I was having no luck getting the SIP phones to display their local directory numbers (NYC Router). After reviewing the various SIP XML and systems files, and comparing them against their SEP counterparts, something caught my attention.

I noticed that that the while the SEP XML and systems files where telling the SCCP phones to point to the router’s local director via HTTP, I did not observe this on the SIP CUCME router SIP XML and systems files. Therefore, under voice register global, I add a URL for the directory on the local router. This seems to have rectified the issue.

voice register global
url directory http://10.1.22.1:80/localdirectory

7. Below are the pertinent “show run” edits for the Baltimore and New York CUCME routers.

Baltimore CUCME

Baltimore#sh run
!
card type t1 0 0
!
network-clock-participate wic 0
!
isdn switch-type primary-ni
!
controller T1 0/0/0
cablelength short 110
pri-group timeslots 1-12,24
!
!
translation-rule 1
Rule 0 ^4357 1611
!
!
ip sla responder ##for the call fallback##
!
!
call fallback active
!
!
voice-port 0/0/0:23
description PRI ciruit to PSTN
!
voice-port 0/1/0
connection plar opx 1005
description inbound 410-555-5001
caller-id enable
!
voice-port 0/1/1
connection plar opx 1611
description inbound 410-555-5002
caller-id enable
!
voice-port 0/3/0
description Baltimore-Security
caller-id enable
!
voice-port 0/3/1
caller-id enable
!
!
dial-peer voice 1 pots
description outbound via pri
preference 1
destination-pattern 9[2-9].........
port 0/0/0:23
!
dial-peer voice 2 pots
description outbound via 410-555-5001
preference 2
destination-pattern 9[2-9].........
port 0/1/0
!
dial-peer voice 3 pots
description outbound via 410-555-5002
preference 2
destination-pattern 9[2-9].........
port 0/1/1
!
dial-peer voice 4 pots
description inbound PRI dial-peer
incoming called-number .
direct-inward-dial
port 0/0/0:23
!
dial-peer voice 1611 pots
description Baltimore-Security
destination-pattern 1611
port 0/3/0
!
dial-peer voice 2000 voip
description VOIP Peer to NYC
preference 1
destination-pattern 20..
monitor probe icmp-ping 172.16.1.2
session protocol sipv2
session target ipv4:172.16.1.2
dtmf-relay rtp-nte
codec g722-64
!
dial-peer voice 2001 pots
preference 2
destination-pattern 20..
port 0/0/0:23
forward-digits all
prefix 212555
!
dial-peer voice 2002 pots
preference 3
destination-pattern 20..
port 0/1/0
forward-digits all
prefix 212555
!
dial-peer voice 2003 pots
preference 3
destination-pattern 20..
port 0/1/1
forward-digits all
prefix 212555
!
!
ephone-dn 1 dual-line
number 1001
label Cal Ripken 1001
description 410-555-1001
name Cal Ripken
translate called 1
!

New York CUCME

NewYork#sh run
!
card type t1 0 0
!
network-clock-participate wic 0
!
isdn switch-type primary-ni
!
!
voice register global
url directory http://10.1.22.1:80/localdirectory
!
voice translation-rule 1
rule 1 /\(10..\)/ /410555\1/ ##for the PSTN fallback translation##
!
!
voice translation-profile prefix
translate called 1 ##for the PSTN fallback translation##
!
!
controller T1 0/0/0
cablelength short 110
pri-group timeslots 1-12,24
!
!
ip sla responder
!
call fallback active
!
!
voice-port 0/0/0:23
description PRI ciruit to PSTN
!
voice-port 0/1/0
connection plar opx 2005
description inbound 212-555-6001
caller-id enable
!
voice-port 0/1/1
connection plar opx 2611
description inbound 212-555-6002
caller-id enable
!
voice-port 0/3/0
description NewYork-Security
caller-id enable
!
voice-port 0/3/1
caller-id enable
!
ccm-manager fax protocol cisco
!
mgcp fax t38 ecm
!
!
!
dial-peer voice 1 pots
description outbound via pri
preference 1
destination-pattern 9[2-9].........
port 0/0/0:23
!
dial-peer voice 2 pots
description outbound via 212-555-6001
preference 2
destination-pattern 9[2-9].........
port 0/1/0
!
dial-peer voice 3 pots
description outbound via 212-555-6002
preference 2
destination-pattern 9[2-9].........
port 0/1/1
!
dial-peer voice 4 pots
description inbound PRI dial-peer
incoming called-number .
direct-inward-dial
port 0/0/0:23
!
dial-peer voice 2611 pots
description NewYork-Security
destination-pattern 2611
port 0/3/0
!
dial-peer voice 1000 voip
description VOIP Peer to Baltimore
preference 1
destination-pattern 10..
monitor probe icmp-ping 172.16.1.1
session protocol sipv2
session target ipv4:172.16.1.1
dtmf-relay rtp-nte
codec g722-64
!
dial-peer voice 1001 pots
translation-profile outgoing prefix
preference 2
destination-pattern 10..
port 0/0/0:23
forward-digits all
!
dial-peer voice 1002 pots
translation-profile outgoing prefix
preference 3
destination-pattern 10..
port 0/1/0
forward-digits all
!
dial-peer voice 1003 pots
translation-profile outgoing prefix
preference 3
destination-pattern 10..
port 0/1/1
forward-digits all
!
dial-peer voice 4357 pots
description NewYork-Security
destination-pattern 4357
port 0/3/0
!

CUCME-CUE Lab 3 – New York Basic CUCME System Setup

Ballplayers, LLC’s CIO, Fuzzy Dunlop, is interested in learning more about standards-based Unified Communications protocols. Since Baltimore’s CUCME configuration was based on proprietary Cisco SCCP protocol, he has instructed you to configure the New York CUCME using SIP.

New York Basic CUCME System Setup Prerequisites
If you haven’t already done so, you will need to load the appropriate CUCME files on the New York router. The tasks and options associated with this were described in CUCME-CUE Lab 2, Baltimore Basic CUCME System Setup Prerequisites.

One note, the SIP phone loads are not included in the cme-124-22T2.zip. Therefore, you will need to download these separate from CCO, place them on your FTP or TFTP server, and load them onto your router appropriately. Please refer to the Cisco Unified CME 7.0(1) Supported Firmware, Platforms, Memory, and Voice Products for the compatible SIP phone loads.

For this lab, I’ve downloaded “cmterm-7942_7962-sip.8-3-3SR2.zip”. However, since I’ve previously created a hierarchical file structure for the SCCP 7942-7962 phone loads on flash, I placed the SIP phone loads in the root of flash. Finally, since the SIP phone loads are not a TAR file, you’ll likely need to copy each file individually, rather than using the “archive tar /xtract” command.

Lab 3.1 – New York Basic CUCME Setup Tasks
1. Setup the CUCME System Parameters on the New York router. You may not use the CUCME setup utility or any sort of auto registration process.
2. Configure the New York Phones to update their SIP phone loads.
3. Configure the phone extensions based on the diagram depicted in CUCME-CUE Labs – Background.
4. Ari Gold is a huge fan of the 1986 New York Mets. Therefore, create a custom ringtone for New York based on the "hit" 1986 song, “Lets Go Mets Go”. (ah, the 1980s... - LOL)
5. Each phone and should also be able to customize their ringtones beyond the default chirp ringtone.
6. The CUCME service should be configure to support the appropriate localization, time-zone, a 12 hour time format, and a Month-Day-Year format.
7. Create an appropriate E.164 dial-pattern.
8. Anticipate the need to transfer calls between Baltimore and New York in the future.
9. Enable the wideband codec by default for all phones.
10. Create the appropriate GUI Administrator parameters
11. Create GUI access for Fuzzy Dunlop with parameters separate from the Administrator.
12. Each user’s phone should also display his/her name and full E.164 number.
13. Eliminate the possibility of “clipping” of voice between pauses in conversations.

Lab 3.2 – New York Basic CUCME Setup Verification
In my opinion, the configuration of CUCME for SIP phones is more complicated than a SCCP setup. Furthermore, a SIP CUCME configuration has far fewer features and functionality than a SCCP configuration. However, SIP is the “emerging” UC standard. And CUCME 7.1, which I was able to beta test at the Cisco Partner UCVT in October 2008, should incorporate some new SIP features to bring closer feature parity with SCCP phones & features.

Before I discuss the specific tasks, an additional note…. Unlike SCCP phones, SIP phones do not maintain a keepalive with CUCME. Additionally, you have to reissue the “create profile” command under voice register global every time you make a change to either the phone (voice register pool), the dial number (voice register dn), and/or under the voice global register. Therefore, my recommendation is while you make your initial SIP configurations:

- Either shut down the voice vlan and/or remove the phones from the CUCME switch.
- Configure all of your SIP parameters.
- Issue the necessary “upgrade” and “create profile” commands under voice register global.
- Reattach your phones and/or turn up your voice vlan.
- Reset and/or troubleshoot phones as necessary.

1. Updating the SIP Phone loads was the first challenge, thanks to inaccurate information in some Cisco documentation. First, the correct configuration to update the SIP phone images is below.

tftp-server flash:apps42.8-3-3ES2.sbn
tftp-server flash:cnu42.8-3-3ES2.sbn
tftp-server flash:cvm42sip.8-3-3ES2.sbn
tftp-server flash:dsp42.8-3-3ES2.sbn
tftp-server flash:jar42sip.8-3-3ES2.sbn
tftp-server flash:SIP42.8-3-3SR2S.loads
tftp-server flash:term42.default.loads
tftp-server flash:term62.default.loads
!
voice register global
mode cme
load 7962 SIP42.8-3-3SR2S
load 7942 SIP42.8-3-3SR2S
upgrade
create profile

Now, I’ll point out the inaccuracy, also keeping in mind that I configured much of the other SIP related parameters when I encountered this issue…

The Cisco Unified CME 7.0(1) Supported Firmware, Platforms, Memory, and Voice Products contains “Important Information about Configuring Cisco Unified IP Phone Support”, specifically, the following:

“In Cisco Unified CME 7.0(1) and later versions, use the complete filename, including the file suffix, when you configure the load command for phone firmware versions later than version 8-2-2 for all phone types.”

So, initially in the above load commands, I included the .loads suffix. However, when the phone attempted to download the SIP loads, they encountered an error attempting to load SIP42.8-3-3SR2S.loads.

After a bit of troubleshooting, I decided to remove the .loads suffix, re-issue the upgrade and create profile, and reset the phones. Unfortunately, while the phones did obtain their proper DHCP, TFTP, and CUCME information from the router, they still would not upgrade their SCCP to SIP load. After some additionally frustrating troubleshooting, I decided to reboot the router. Once the router reloaded and phone obtained the proper DHCP information, they were able to update their phone loads and register accordingly.

2. There are a few steps involved in creating a custom ringtone that is not include by default in the ringtone.tar. The first step was to find a .wav recording to “Lets Go Mets Go”, which surprisingly wasn’t too difficult. The second step is to convert the .wav to a PCM .raw format and upload it to the ringtones directory in the router. Next, you have to modify both the DistinctiveRingList.xml and the RingList.xml files. Finally, you have to remove the existing versions of these on the router, and upload these modified versions. You can find a very good posting on the proper procedures here.

3. In a nutshell, configuring CUCME to support SIP involves the following steps:

- Enabling SIP Calls in Your VoIP Network
- SIP: Setting Up Cisco Unified CME
- SIP: Creating Directory Numbers
- SIP: Assigning Directory Numbers to Phones

4. Configuring the SIP phones to uses the G.722 Wideband Codec can be a bit confusing, since it isn't very well documented on CCO in one place. Essentially, there are two components. First, you have to modify the global codec under telephony-service, the same as it was done in Baltimore. Second, you need to configure each phone (voice register pool) to use G.722 as the default codec (SIP phones default to G.729).

5. The following show commands are helpful in verifying and troubleshooting your configuration:

show voice register global (verifies the voice register global parameters)
show voice register tftp-bind (verifies the creation of the voice profiles and their tftp binding)
show voice register statistics (verifies SIP phone registration with CUCME)

6. Below is the output of the appropriate router configuration, truncated for brevity.

NewYork#sh run
!
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
sip
registrar server expires max 600 min 300
!
!
voice register global
mode cme
source-address 10.1.22.1 port 5060
load 7962 SIP42.8-3-3SR2S
load 7942 SIP42.8-3-3SR2S
timezone 12
dialplan-pattern 1 2125552... extension-length 4
create profile sync 000371836563317A
ntp-server 10.1.1.4 mode directedbroadcast
!
voice register dn 1
number 2001
name Tom Seaver
label Tom Seaver
!
voice register dn 2
number 2002
name David Wright
label David Wright
!
voice register dn 3
number 2003
name Eli Manning
label Eli Manning
!
voice register dn 4
number 2004
name Brandon Jacobs
label Brandon Jacobs
!
voice register dn 5
number 2005
name Ari Gold
label Ari Gold
!
voice register pool 1
id mac 0021.D8BA.2373
type 7942
number 1 dn 1
dtmf-relay sip-notify
description 212-555-2001
codec g722-64
no vad
!
voice register pool 2
id mac 0212.0555.2002
type 7942
number 1 dn 2
dtmf-relay sip-notify
description 212-555-2002
codec g722-64
no vad
!
voice register pool 3
id mac 0212.0555.2003
type 7942
number 1 dn 3
dtmf-relay sip-notify
description 212-555-2003
codec g722-64
no vad
!
voice register pool 4
id mac 0212.0555.2004
type 7942
number 1 dn 4
dtmf-relay sip-notify
description 212-555-2004
codec g722-64
no vad
!
voice register pool 5
id mac 0021.D8B9.BC72
type 7962
number 1 dn 5
dtmf-relay sip-notify
description 212-555-2005
codec g722-64
no vad
!
telephony-service
em logout 0:0 0:0 0:0
max-ephones 42
max-dn 144
ip source-address 10.1.22.1 port 2000
service phone g722CodecSupport 2
service phone handsetWidebandEnable 1
service phone headsetWidebandEnable 0
service phone handsetWidebandUIControl 0
system message Ballplayers, LLC New York
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 Jan 07 2009 16:21:39
!

CUCME-CUE Lab 3 Wrap-up
As I stated earlier, configuring CUCME for SIP is more complicated, with comparatively fewer features. The feature differences will become more apparent in future labs, although CUCME 7.1 may address some of the SIP phone feature loss. For example, you cannot configure a System Message on SIP phones, and the CUCME GUI is basically worthless for SIP phones.

Editorially, I found it confusing to have to configure some parameters under “voice register global” and others under “telephony-service” in order to have a working SIP CUCME router. There is probably some programming reason in IOS for having to work under two different areas, but it certainly would be nice to have all the parameters configured under one global section.

References:
Cisco Systems. Cisco Unified Communications Manager Express: SIP Implementation Guide. Available online.

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

UC500.com: Cisco Communication Manager Express, UC520, SMB VOIP reference and community. Creating Custom Ring Tones for CallManager Express. Available online.

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.

CUCME-CUE Lab 1 – Initial Configuration

CUCME-CUE Lab 1 Prerequisites
Prior to beginning the basic IP Setup for this series of CUCME-CUE labs, configure the Adtran Atlas 550 to support the simulated PSTN dial plan depicted in diagram in CUCME-CUE Labs – Background. Please refer to VOIP Fundamentals Lab 1 - PSTN Setup on how to configure the Adtran for the dial plan depicted in CUCME-CUE Scenario Background.

The CUCME-CUE labs also assume that you have the appropriate IOS files, CUCME files, and CUE files. These labs also assume that you have valid CCO access and licenses for any files that you may be downloading and installing on your lab equipment.

These labs will be based on CME 7.0(1) and IOS 12.4(22)T. If you need to upgrade the IOS refer to the Cisco Unified CME and Cisco IOS Software Version Compatibility Matrix. For now, my recommendation is not to install the CME files. I will cover that in a subsequent lab.

Tasks Lab 1.1 – Initial IP Network Setup
1. Configure the IP addressing based on the diagram in VoIP Lab 1.
2. Configure R7 to serve as the frame relay switch for WAN. Set the clocking to 512000.
3. Make sure you have an “external” NTP clocking source for your LAB. (Note, depending on your own lab, this may vary. I will discuss my configuration below.)
4. Configure the Frame Relay connection on both Baltimore and New York as a point-to-point interface.
5. Provide a loopback interface on each router.
6. Configure your LAN networks as depicted the CUCME-CUE Labs – Background posting.
7. On the Baltimore Router, the connection between the router and Ethernet Switch Module must be over a Layer 2 trunk.
8. Configure IP Services on each router to support IP Phones. Reserve the first 16-block of addresses accordingly.
9. Configure the LAN ports so that Phones receive their appropriate IP information and any PCs on those LAN ports receive their appropriate IP information.
10. Configure OSPF routing for the network. The WAN/Frame Cloud should use Area 0; Baltimore Area 1; New York Area 2.
11. The loopbacks should be placed into each area accordingly; these routes should be depicted in the route tables as /24 networks.
12. The “Out of Band” network, not part of the LAB should not be added to OSPF.
13. Test connectivity. Verify by ping devices on New York from Baltimore, and vice-versa.


Tasks Lab 1.2 – Verifying IP Network Setup
1. Below is a snippet of router config on R7, which shows the configuration of the router as a Frame Relay switch. I have also configured the router to act as an NTP Server as well as an Access Server for my lab.

!
hostname ISP
!
ip host r1 2066 10.1.1.4
ip host r2 2067 10.1.1.4
ip host r3 2068 10.1.1.4
ip host r4 2069 10.1.1.4
ip host r5 2070 10.1.1.4
ip host r6 2071 10.1.1.4
ip host s1 2072 10.1.1.4
!
frame-relay switching
!
!
interface FastEthernet0/0
ip address 10.1.1.4 255.255.255.0
duplex auto
speed auto
ntp broadcast
!
!
interface Serial0/0/0
description frame-relay link to Baltimore
no ip address
encapsulation frame-relay
no fair-queue
clock rate 512000
frame-relay lmi-type cisco
frame-relay intf-type dce
frame-relay route 102 interface Serial0/0/1 201
!
interface Serial0/0/1
description frame-relay to New York
no ip address
encapsulation frame-relay
clock rate 512000
frame-relay lmi-type cisco
frame-relay intf-type dce
frame-relay route 201 interface Serial0/0/0 102
!
line 1/0 1/15
no exec
transport input all
!
ntp master


2. Below are the configurations for the Frame Relay connectivity on both Baltimore and New York.

Baltimore#
!
interface Serial0/2/0
no ip address
encapsulation frame-relay
no fair-queue
frame-relay lmi-type cisco
!
interface Serial0/2/0.102 point-to-point
bandwidth 1544
ip address 172.16.1.1 255.255.255.252
ip ospf network point-to-point
snmp trap link-status
frame-relay interface-dlci 102
!


NewYork#
!
interface Serial0/2/0
no ip address
encapsulation frame-relay
no fair-queue
frame-relay lmi-type cisco
!
interface Serial0/2/0.201 point-to-point
bandwidth 1544
ip address 172.16.1.2 255.255.255.252
ip ospf network point-to-point
snmp trap link-status
frame-relay interface-dlci 201
!

Baltimore#ping 172.16.1.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.1.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/8 ms

NewYork#ping 172.16.1.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/8 ms


3. Configuring the EtherSwitch Service Module (NME-16ES-1G-P), as described in Task 1.1.7, presents a unique challenge. ES modules have their own processors, switching engines, software and flash memory that run independent of the host router resources. “EtherSwitch Service Module (ES) Configuration Example” is a good reference document.

The trick, or “gotchya” described above in Task 1.1.7 is to require a Layer 2 link between the router and the EtherSwitch Service Module. This requires the use of dot1q sub-interfaces on the router’s interface GigabitEthernet1/0. However, as I found, you cannot use a dot1q sub-interfaces to “session” into EtherSwitch Service Module.

For example:

!
interface GigabitEthernet1/0
no ip address
!
interface GigabitEthernet1/0.10
description Management Vlan
encapsulation dot1Q 10
ip address 10.1.10.1 255.255.255.0
!

Baltimore#service-module gigabitEthernet 1/0.10 session
^
% Invalid input detected at '^' marker.

Baltimore#service-module gigabitEthernet 1/0 session
IP address needs to be configured on interface GigabitEthernet1/0
Baltimore#

So, the trick is to first configure the interface GigabitEthernet1/0 on the router as a traditional Layer-3 routed interface, which allows you to session into the EtherSwitch Service Module.

Baltimore#
interface GigabitEthernet1/0
ip address 10.1.10.1 255.255.255.0
!
Baltimore#service-module gigabitEthernet 1/0 session
Trying 10.1.10.1, 2066 ... Open
Switch>

The next step, once you have connectivity to the EtherSwitch Service Module, is to configure the VLANs and trunk back to the router. Another important step will be to enabling telnet (or SSH) on the switch to allow access. Failure to assign a password to the VTY ports could impede your access to the EtherSwitch Service Module.

hostname Baltimore-S1
!
!
username cisco123 privilege 15 password 0 *****
!
vlan 10
name MNGMT-BMORE
!
vlan 11
name DATA-BMORE
!
vlan 12
name VOICE-BMORE
!
!
interface GigabitEthernet1/0/2
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 10-12
switchport mode trunk
!
interface Vlan1
no ip address
!
interface Vlan10
description Management Vlan
ip address 10.1.10.2 255.255.255.0
!
interface Vlan11
description Data Vlan
ip address 10.1.11.2 255.255.255.0
!
interface Vlan12
description Voice Vlan
ip address 10.1.12.2 255.255.255.0
!
ip default-gateway 10.1.10.1
ip classless
ip route 0.0.0.0 0.0.0.0 10.1.10.1
!line vty 0 4
exec-timeout 5 0
logging synchronous
login local

The final step is to remove the IP address from the interface GigabitEthernet1/0 on the router and add the appropriate dot1q sub-interfaces.

!
interface GigabitEthernet1/0
no ip address
!
interface GigabitEthernet1/0.10
description Management Vlan
encapsulation dot1Q 10
ip address 10.1.10.1 255.255.255.0
!
interface GigabitEthernet1/0.11
description Data Vlan
encapsulation dot1Q 11 native
ip address 10.1.11.1 255.255.255.0
!
interface GigabitEthernet1/0.12
description Voice Vlan
encapsulation dot1Q 12
ip address 10.1.12.1 255.255.255.0

Under the configuration abve, will only be able to telnet (or SSH) into the EtherSwitch Service Module; you will be unable to “session” into module, which presents a potential management risk. However, based on my prior CCIE lab experience, sometimes the questions do not accurately reflect “real world” configurations.

Baltimore#service-module gigabitEthernet 1/0 session
IP address needs to be configured on interface GigabitEthernet1/0
Baltimore#telnet 10.1.10.2
Trying 10.1.10.2 ... Open

User Access Verification

Username: cisco123
Password:
Baltimore-S1#


4. The configuration of the switch ports for the IP Phones is rather straight forward. Below is the output from the EtherSwitch Service Module (Baltimore):

Baltimore-S1(config)#interface range fastEthernet 1/0/1 – 3
Baltimore-S1(config-if-range)# switchport trunk encapsulation dot1q
Baltimore-S1(config-if-range)# switchport trunk native vlan 11
Baltimore-S1(config-if-range)# switchport mode trunk
Baltimore-S1(config-if-range)# switchport voice vlan 12
Baltimore-S1(config-if-range)# spanning-tree portfast


5. The IP Phones required a DHCP server to obtain their IP Addressing, Default Route, and CUCME information. Below is the configuration from New York; note the exclusion of address .1 - .15.

ip dhcp excluded-address 10.1.21.1 10.1.21.15
ip dhcp excluded-address 10.1.22.1 10.1.22.15
!
ip dhcp pool VOICE
network 10.1.22.0 255.255.255.0
option 150 ip 10.1.22.1
dns-server 4.2.2.1 4.2.2.2
default-router 10.1.22.1
domain-name ballplayersllc.com
!
ip dhcp pool DATA
network 10.1.21.0 255.255.255.0
default-router 10.1.21.1
dns-server 4.2.2.1 4.2.2.2
domain-name ballplayersllc.com
!


6. There is a fairly quick way to verify that both the IP Phones on each router are receiving their proper IP Addresses as well as confirming end-to-end IP connectivity. On each router, a “show ip dhcp binding” provides the IP addresses the phones received from DHCP. Then, from one router, ping the IP Phones on the other router. For example:

NewYork#sh ip dhcp binding
Bindings from all pools not associated with VRF:
IP address Client-ID/ Lease expiration Type
Hardware address/
User name
10.1.22.17 0100.21d8.b9bc.72 Dec 23 2008 11:44 AM Automatic
10.1.22.19 0100.21d8.ba23.73 Dec 23 2008 11:44 AM Automatic
NewYork#

Baltimore#sh ip dhcp binding
Bindings from all pools not associated with VRF:
IP address Client-ID/ Lease expiration Type
Hardware address/
User name
10.1.12.16 0100.21d8.ba23.a1 Dec 23 2008 11:44 AM Automatic
10.1.12.18 0100.2333.1aed.cc Dec 23 2008 11:46 AM Automatic
10.1.12.20 0100.1fca.e92c.ce Dec 23 2008 11:42 AM Automatic
Baltimore#
Baltimore#ping 10.1.22.17

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.22.17, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/8 ms
Baltimore#ping 10.1.22.19

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.22.19, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/8 ms
Baltimore#

NewYork#ping 10.1.12.16

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.12.16, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/12 ms
NewYork#ping 10.1.12.18

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.12.18, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/12 ms
NewYork#ping 10.1.12.20

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.12.20, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/8 ms
NewYork#


7. Finally, we’ll verify the route tables on each router.

NewYork#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is 10.1.1.1 to network 0.0.0.0

1.0.0.0/24 is subnetted, 1 subnets
O IA 1.1.1.0 [110/65] via 172.16.1.1, 00:07:32, Serial0/2/0.201
2.0.0.0/24 is subnetted, 1 subnets
C 2.2.2.0 is directly connected, Loopback0
172.16.0.0/30 is subnetted, 1 subnets
C 172.16.1.0 is directly connected, Serial0/2/0.201
10.0.0.0/24 is subnetted, 7 subnets
O IA 10.1.11.0 [110/65] via 172.16.1.1, 00:07:32, Serial0/2/0.201
O IA 10.1.10.0 [110/65] via 172.16.1.1, 00:07:32, Serial0/2/0.201
O IA 10.1.12.0 [110/65] via 172.16.1.1, 00:07:33, Serial0/2/0.201
C 10.1.1.0 is directly connected, FastEthernet0/0.1
C 10.1.22.0 is directly connected, FastEthernet0/0.22
C 10.1.21.0 is directly connected, FastEthernet0/0.21
C 10.1.20.0 is directly connected, FastEthernet0/0.20
S* 0.0.0.0/0 [1/0] via 10.1.1.1
NewYork#


Baltimore#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is 10.1.1.1 to network 0.0.0.0

1.0.0.0/24 is subnetted, 1 subnets
C 1.1.1.0 is directly connected, Loopback0
2.0.0.0/24 is subnetted, 1 subnets
O IA 2.2.2.0 [110/65] via 172.16.1.2, 00:07:51, Serial0/2/0.102
172.16.0.0/30 is subnetted, 1 subnets
C 172.16.1.0 is directly connected, Serial0/2/0.102
10.0.0.0/24 is subnetted, 7 subnets
C 10.1.11.0 is directly connected, GigabitEthernet1/0.11
C 10.1.10.0 is directly connected, GigabitEthernet1/0.10
C 10.1.12.0 is directly connected, GigabitEthernet1/0.12
C 10.1.1.0 is directly connected, FastEthernet0/0
O IA 10.1.22.0 [110/65] via 172.16.1.2, 00:07:52, Serial0/2/0.102
O IA 10.1.21.0 [110/65] via 172.16.1.2, 00:07:52, Serial0/2/0.102
O IA 10.1.20.0 [110/65] via 172.16.1.2, 00:07:53, Serial0/2/0.102
S* 0.0.0.0/0 [1/0] via 10.1.1.1
Baltimore#


8. Below are snippets from router and switch configurations for Baltimore & New York. For brevity, I have omitted parts.

Baltimore Router:
Baltimore#sh run
Building configuration...
!
!
hostname Baltimore
!
ip dhcp excluded-address 10.1.11.1 10.1.11.15
ip dhcp excluded-address 10.1.12.1 10.1.12.15
!
ip dhcp pool VOICE
network 10.1.12.0 255.255.255.0
default-router 10.1.12.1
option 150 ip 10.1.12.1
dns-server 4.2.2.1 4.2.2.2
domain-name ballplayerllc.com
!
ip dhcp pool DATA
network 10.1.11.0 255.255.255.0
default-router 10.1.11.1
dns-server 4.2.2.1 4.2.2.2
domain-name ballplayerllc.com
!
!
ip domain name ballplayerllc.com
!
!
interface Loopback0
ip address 1.1.1.1 255.255.255.0
ip ospf network point-to-point
!
interface FastEthernet0/0
ip address 10.1.1.101 255.255.255.0
description "Out of Band Management - Not Part of Lab!"
duplex auto
speed auto
!
interface Service-Engine0/0
no ip address
shutdown
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/2/0
no ip address
encapsulation frame-relay
no fair-queue
frame-relay lmi-type cisco
!
interface Serial0/2/0.102 point-to-point
bandwidth 1544
ip address 172.16.1.1 255.255.255.252
ip ospf network point-to-point
snmp trap link-status
frame-relay interface-dlci 102
!
interface Serial0/2/1
no ip address
shutdown
clock rate 2000000
!
interface GigabitEthernet1/0
no ip address
!
interface GigabitEthernet1/0.10
description MNGMT-BMORE
encapsulation dot1Q 10
ip address 10.1.10.1 255.255.255.0
!
interface GigabitEthernet1/0.11
description DATA-BMORE
encapsulation dot1Q 11 native
ip address 10.1.11.1 255.255.255.0
!
interface GigabitEthernet1/0.12
description VOICE-BMORE
encapsulation dot1Q 12
ip address 10.1.12.1 255.255.255.0
!
router ospf 1
router-id 1.1.1.1
log-adjacency-changes
passive-interface default
no passive-interface Serial0/2/0.102
network 1.1.1.0 0.0.0.255 area 1
network 10.1.10.0 0.0.0.255 area 1
network 10.1.11.0 0.0.0.255 area 1
network 10.1.12.0 0.0.0.255 area 1
network 172.16.1.0 0.0.0.3 area 0
!
!
line con 0
exec-timeout 0 0
logging synchronous
login local
line aux 0
line 66
no activation-character
no exec
transport preferred none
transport input all
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
line 194
no activation-character
no exec
transport preferred none
transport input all
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
line vty 0 4
exec-timeout 0 0
logging synchronous
login local
!
scheduler allocate 20000 1000
ntp server 10.1.1.4
end

Baltimore EtherSwitch Service Module:
Baltimore-S1#sh run
Building configuration...
!
hostname Baltimore-S1
!
!
vlan 10
name MNGMT-BMORE
!
vlan 11
name DATA-BMORE
!
vlan 12
name VOICE-BMORE
!
interface FastEthernet1/0/1
description 7962 MAC 001FCAE92CCE
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport mode trunk
switchport voice vlan 12
spanning-tree portfast
!
interface FastEthernet1/0/2
description 7942 MAC 0021D8BA23A1
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport mode trunk
switchport voice vlan 12
spanning-tree portfast
!
interface FastEthernet1/0/3
description 7942 MAC 0023331AEDCC
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport mode trunk
switchport voice vlan 12
spanning-tree portfast
!
interface FastEthernet1/0/4
!
!output omitted!
!
interface GigabitEthernet1/0/2
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 10-12
switchport mode trunk
!
interface Vlan1
no ip address
!
interface Vlan10
description Management Vlan
ip address 10.1.10.2 255.255.255.0
!
interface Vlan11
description Data Vlan
ip address 10.1.11.2 255.255.255.0
!
interface Vlan12
description Voice Vlan
ip address 10.1.12.2 255.255.255.0
!
ip default-gateway 10.1.10.1
ip classless
ip route 0.0.0.0 0.0.0.0 10.1.10.1
ip http server
!
!
line con 0
exec-timeout 5 0
logging synchronous
login local
line vty 0 4
exec-timeout 5 0
logging synchronous
login local
line vty 5 15
exec-timeout 5 0
logging synchronous
login local
!
end

New York Router:
NewYork#sh run
Building configuration...
!
hostname NewYork
!
!
ip cef
ip dhcp excluded-address 10.1.21.1 10.1.21.15
ip dhcp excluded-address 10.1.22.1 10.1.22.15
!
ip dhcp pool VOICE
network 10.1.22.0 255.255.255.0
option 150 ip 10.1.22.1
dns-server 4.2.2.1 4.2.2.2
default-router 10.1.22.1
domain-name ballplayersllc.com
!
ip dhcp pool DATA
network 10.1.21.0 255.255.255.0
default-router 10.1.21.1
dns-server 4.2.2.1 4.2.2.2
domain-name ballplayersllc.com
!
!
no ip domain lookup
ip domain name ballplayersllc.com
!
interface Loopback0
ip address 2.2.2.2 255.255.255.0
ip ospf network point-to-point
!
interface FastEthernet0/0
no ip address
duplex auto
speed auto
!
interface FastEthernet0/0.1
description "Out of Band Management - Not Part of Lab!"
encapsulation dot1Q 1
ip address 10.1.1.102 255.255.255.0
!
interface FastEthernet0/0.20
description NEWYORK-MANAGEMENT-VLAN
encapsulation dot1Q 20
ip address 10.1.20.1 255.255.255.0
!
interface FastEthernet0/0.21
description NEWYORK-DATA-VLAN
encapsulation dot1Q 21 native
ip address 10.1.21.1 255.255.255.0
!
interface FastEthernet0/0.22
description NEWYORK-VOICE-VLAN
encapsulation dot1Q 22
ip address 10.1.22.1 255.255.255.0
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/2/0
no ip address
encapsulation frame-relay
frame-relay lmi-type cisco
!
interface Serial0/2/0.201 point-to-point
bandwidth 1544
ip address 172.16.1.2 255.255.255.252
ip ospf network point-to-point
snmp trap link-status
frame-relay interface-dlci 201
!
interface Serial0/2/1
no ip address
shutdown
clock rate 2000000
!
router ospf 1
router-id 2.2.2.2
log-adjacency-changes
passive-interface default
no passive-interface Serial0/2/0.201
network 2.2.2.0 0.0.0.255 area 2
network 10.1.20.0 0.0.0.255 area 2
network 10.1.21.0 0.0.0.255 area 2
network 10.1.22.0 0.0.0.255 area 2
network 172.16.1.0 0.0.0.3 area 0
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 10.1.1.1
no ip http server
no ip http secure-server
!
line con 0
exec-timeout 15 0
logging synchronous
login local
line aux 0
line vty 0 4
exec-timeout 15 0
logging synchronous
login local
length 0
!
scheduler allocate 20000 1000
ntp server 10.1.1.4
end

New York Switch:
!
hostname NewYork-S1
!
!
interface FastEthernet1/0/2
description "Trunk to NY Router (R2)"
switchport trunk encapsulation dot1q
switchport trunk native vlan 21
switchport trunk allowed vlan 1,20-22
switchport mode trunk
spanning-tree portfast
!
!
interface FastEthernet1/0/13
description 7962 MAC 0021D8B9BC72
switchport trunk encapsulation dot1q
switchport trunk native vlan 21
switchport mode trunk
switchport voice vlan 22
spanning-tree portfast
!
interface FastEthernet1/0/14
description 7942 MAC 0021D8BA2373
switchport trunk encapsulation dot1q
switchport trunk native vlan 21
switchport mode trunk
switchport voice vlan 22
spanning-tree portfast
!
!
interface Vlan20
description MNGMT-NY
ip address 10.1.20.2 255.255.255.0
!
interface Vlan21
description DATA-NY
ip address 10.1.21.2 255.255.255.0
!
interface Vlan22
description VOICE-NY
ip address 10.1.22.2 255.255.255.0
!
!
line con 0
exec-timeout 20 0
logging synchronous
login local
line vty 0 4
exec-timeout 20 0
logging synchronous
login local
length 0
line vty 5 15
no login
!end

CUCME-CUE Labs – Background

Ballplayers, Inc. is a sports marketing firm with locations in New York City, NY and Baltimore, MD. You previously staged a VOIP Pilot at both locations for the firm’s CIO Fuzzy Dunlop. Fuzzy was extremely pleased with the results and received executive buy-in to purchase an IP based Voice Communications (Unified Communications, UC) solution for both offices.

Below is a high-level design of the proposed Cisco Unified Communications Express solution.

The equipment and logical set-up that I will be using for this series of labs is as follows.

WAN & PSTN:
PSTN Simulation on a Adtran Atlas 550.
Frame Relay Switch on a Cisco ISR 2811 with multiple WIC-2T cards. This router also acts as a terminal server for reverse telnet to the other devices in this lab.

Baltimore:
Cisco 2811 ISR with PVDM2-32, VIC2-2FXO, VWIC2-1MFT-T1/E1, WIC-2T, AIM-CUE, NME-16ES-1G-P
IOS Version: 12.4.22T, c2800nm-adventerprisek9_ivs_li-mz.124-22.T.bin (INT VOICE/VIDEO GK, IPIPGW, TDMIP GW AES, LI)
CME: 7.0(1), cme-124-20T1.zip
AIM Version 3.2.2
One 7962G IP Phone
Two 7942G IP Phone
Two “dummy/virtual” IP Phones

New York:
Cisco 2811 ISR with PVDM2-32, VIC2-2FXO, VWIC2-1MFT-T1/E1, WIC-2T
IOS Version: 12.4.22T, c2800nm-adventerprisek9_ivs_li-mz.124-22.T.bin (INT VOICE/VIDEO GK, IPIPGW, TDMIP GW AES, LI)
CME: 7.0(1), cme-124-20T1.zip
Cisco 3750-24PS
One 7962G IP Phone
One 7942G IP Phone
Three “dummy/virtual” IP Phones

IP Addressing:
Frame Cloud: 172.16.1.0/30
Baltimore Loopback0: 1.1.1.1/24
Baltimore Management VLAN 10: 10.1.10.1/24
Baltimore Data VLAN 11: 10.1.11.1/24
Baltimore Voice VLAN 12: 10.1.12.1/24
New York Loopback0: 2.2.2.2/24
New York Management VLAN 20: 10.1.20.1/24
New York Data VLAN 11: 10.1.21.1/24
New York Voice VLAN 12: 10.1.22.1/24
“Out of Band” network, not part of the LAB: 10.1.1.0/24

OSPF:
WAN: Area 0
Baltimore Networks: Area 1
New York Networks: Area 2

Voicemail:
Voicemail Pilot: 199
MWI On: 8000
MWI Off: 8001

The next posting will cover the initial configuration of the data and voice IP addressing, routing, VLANs, IP services, etc.