Unity Connection-CUCME Lab 7 – Baltimore CUE

This lab will revisit setting up CUE in Baltimore for eventual integration with Unity Connection via VPIM. It will be very similar to CUCME-CUE Lab 8.


Unity Connection Lab 7.1 – Baltimore CUE Tasks

1. Configure the Baltimore CUCME router to interface with CUE, using IP address 10.1.12.3/24.

2. Use extension 1999 as the voicemail pilot.

3, Use 8000 and 8001 for MWI.

4. Create voicemail users and mailboxes via the CUE CLI.

5. Mailboxes should be limited in size to accommodate up to 50 users on a AIM-CUE.

6. Make sure that messages can be forward via either dial by name or by extension.

7. Provision the system for GUI access.


Unity Connection Lab 7.2 – Baltimore CUE Verification

Since the tasks here are almost identical to CUCME-CUE Lab 8, please refer to that previous post for help on answers. Note, the Baltimore dial plan for Arliss Michaels and Cal Ripken is slightly different, refer to Unity Connection-CUCME Scenario Background.


Unity Connection Lab 7.3 – Baltimore CUE Wrap-up

The original intention for this lab was to stage Baltimore and then integrate with Unity Connection via VPIM. However, after some thought, I am not sure this is applicable for the CCIE Voice Lab. During the CCIE Voice Techtorial and Cisco Live 2009, the present suggested that the CCIE Voice lab would not have a DNS server. Based on some initial research for VPIM integration, DNS is a requirement. Therefore, one could infer that VPIM would not be tested in the Voice Lab.

That said, I will spend some time pretesting VPIM integration between Baltimore CUE and Unity Connection. If this testing consumes too much time and integration with DNS, I may abort and move on to some other items.

CUCME-CUE Lab 10 – CUCME-CUE Misc Items

In this final CUCME-CUE Lab, Fuzzy Dunlop has asked you to fine tune the Baltimore and New York Unified Communications Express Solution.

CUCME-CUE Lab 10.1 –CUCME-CUE Misc Items Tasks

1. Nick Markakis has a new 7962 IP Phone. With all these line appearances, Nick has requested the ability to monitor the presence of Arliss Michaels, Cal Ripken, and Joe Flacco. Configure Baltimore to support this Presence mandate.

2. All users in both Baltimore and New York should be able to monitor phone presence status via the local directory. Users should also be able to remotely monitor presence status.

3. Eli Manning would like the ability to intercom Ari. However, he does not want Ari to intercom him.

4. Configure ext. 1000 as the Auto Attendant, using the system default AA. When a user requests the Operator via the AA, both Ari and Arliss should receive the call.

5. When an internal user dials “0”, calls should ring simultaneous at Ari and Arliss.

6. Ensure that when external caller dial each branch office’s main number, 410-555-1000 for Baltimore, and 212-555-2000, that the numbers are routed to the AA.

7. Ensure that both Arlis and Ari have administrative privileges on CUE and can modify the system via the TUI using extension 1990.

8. Fuzzy Dunlop has asked that you block any 900, 976, or 1010 calls.

CUCME-CUE Lab 10.2 –CUCME-CUE Misc Items Verification

1. Configuring Presence for SCCP phones in Baltimore is very similar to the process discussed for the SIP phones discussed in Lab 6. First, enable the appropriate presence parameter globally. Next, configure Nick Markakis to monitor Arliss Michaels, Cal Ripken, and Joe Flacco.

!
sip-ua
presence enable
!
presence
max-subscription 144
!
ephone-dn 1 dual-line
number 1001
label Cal Ripken 1001
allow watch
!
!repeat for ephone-dn 2-5!
!
ephone 2
device-security-mode none
description Nick Markakis
blf-speed-dial 2 1001 label "Cal Ripken" device
blf-speed-dial 3 1003 label "Joe Flacco" device
blf-speed-dial 4 1005 label "Arliss Michaels" device
blf-speed-dial 5 2005 label "Ari Gold" device


2. In order to allow all users to view presence status via the local directory, additional modifications are required on both the New York and Baltimore routers. First, there are some additional configuration parameters required under the global “presence” command. Secondly, the “presence call-list” command needs to be added to both the SCCP and SIP phone configuration.

Baltimore#sh run
!
presence
sccp blf-speed-dial retry-interval 90 limit 15
presence call-list
server 10.1.22.1
max-subscription 144
watcher all
allow subscribe
!
ephone 1
description Cal Ripken
presence call-list
!
! repeat for all SCCP phones !


NewYork#sh run
!
presence
sccp blf-speed-dial retry-interval 90 limit 15
presence call-list
server 10.1.12.1
max-subscription 144
watcher all
allow subscribe
!
!
voice register pool 1
presence call-list
description 212-555-2001
!
! repeat for all SIP Phones !

A comment/observation… It appears that only one SIP Presence Server can be added to the CUCME configuration. This effectively limits SIP Presence monitoring between only two CUCME location, unless of course a centralized Presence Server, such as CUPS, is integrated as part of the solution.


3. In an attempt to revisit SIP intercom, I believe that I may have come up with “hybrid” solution. The first part of the solution is to create a voice register dn that auto-answers.

!
voice register dn 6
number 2905
auto-answer
label Intercom from Eli
!

Next, this dn is associated with the Ari Gold SIP Phone.

!
voice register pool 5
number 1 dn 5
number 2 dn 1
number 3 dn 6
!

Finally, a speed dial button for Eli’s phone is created, which in essence creates the “intercom”.

!
voice register pool 3
number 1 dn 3
description 212-555-2003
speed-dial 1 2905 label "Intercom to Ari"
!

4. Meeting the requirements for the Auto Attendant described in tasks 4 – 6 require a number of configuration changes on both the Baltimore and New York CUCME routers and the CUE.

Under CUE, a group delivery mailbox needs to be created, as well mapping which number will ring the operator when a user presses “0” in the auto attendant. For purposes of the configuration, “0” for the operator will be mapped to extension 1100, which will later be associated with a hunt group in CUCME. As for the AA itself and purposes of this exercise, I’ve opted for the default AA in CUE.

baltimore-cue# sh run

groupname Operator create

groupname Operator member amichaels
groupname Operator member agold
groupname Operator phonenumber "1100"

ccn application autoattendant aa
description "autoattendant"
enabled
maxsessions 4
script "aa.aef"
parameter "busClosedPrompt" "AABusinessClosed.wav"
parameter "holidayPrompt" "AAHolidayPrompt.wav"
parameter "welcomePrompt" "AAWelcome.wav"
parameter "disconnectAfterMenu" "false"
parameter "dialByFirstName" "false"
parameter "allowExternalTransfers" "false"
parameter "MaxRetry" "3"
parameter "dialByExtnAnytime" "false"
parameter "busOpenPrompt" "AABusinessOpen.wav"
parameter "businessSchedule" "systemschedule"
parameter "dialByExtnAnytimeInputLength" "4"
parameter "operExtn" "1100"
end application

voicemail mailbox owner "Operator" size 720
description "Operator Mailbox"
zerooutnumber "1000"
end mailbox

Next, in Baltimore, create a parallel hunt group to ring both Ari and Arliss at the same time. Voice hunt-groups allow you to include SIP trunks, something that ephone-hunt groups do not allow. Note, the timeout needs to be tweaked so that the call is sent to the group mail box 1100 prior to being sent to either the Ari or Arliss mailbox.

Baltimore#sh run
!
voice hunt-group 2 parallel
final 1999
list 1005,2005
timeout 20
pilot 1100
!

Next, two additional voip dial-peers are added to Baltimore to allow access to the AA. Note, for external users, a translation profile must be associated with the inbound E.164 number from the PSTN. A modification to the existing voice translation rule is sufficient.

Baltimore#sh run
!
voice translation-rule 2
rule 1 /4105551999/ /1999/
rule 2 /4105551000/ /1000/
!
!
voice translation-profile to-cue
translate called 2
!
!
dial-peer voice 1997 voip
destination-pattern 1000
session protocol sipv2
session target ipv4:10.1.12.3
dtmf-relay rtp-nte
codec g711ulaw
no vad
!
dial-peer voice 1996 voip
mailbox-selection orig-called-num
description VM-AA-PSTN
translation-profile outgoing to-cue
destination-pattern 4105551000
session protocol sipv2
session target ipv4:10.1.12.3
dtmf-relay rtp-nte
codec g711ulaw
no vad
!

For users in New York, the CUCME changes are similar. Two dial-peers are created, one with a destination-pattern of 1000 pointing to Baltimore and the other with a destination-pattern of 212-555-2000, with an associated translation-profile and also pointing to Baltimore.

NewYork#sh run
!
voice translation-rule 2
rule 1 /2125552000/ /1000/
!
!
voice translation-profile outgoing-to-cue
translate called 2
!
!
dial-peer voice 1997 voip
destination-pattern 1000
b2bua
session protocol sipv2
session target ipv4:10.1.12.3
dtmf-relay rtp-nte
codec g711ulaw
no vad
!
dial-peer voice 1996 voip
mailbox-selection orig-called-num
description AA
translation-profile outgoing outgoing-to-cue
destination-pattern 2125552000
b2bua
session protocol sipv2
session target ipv4:10.1.12.3
dtmf-relay rtp-nte
codec g711ulaw
no vad
!


5. The process to enable users to dial “0” and have both Ari and Arliss ring is different for each router.

In Baltimore, we’ll modify the existing translation rule from lab 4, which enabled user who dial HELP to ring the analog security phone. In this instance, add a second rule to translate 0 to the 1100 pilot.

Baltimore#sh run
!
translation-rule 1
Rule 0 ^4357 1611
Rule 1 ^0 1100

In New York, since the phones are SIP, new voice translation rule and translation-profile are created. This translation profile is then applied to a new voip dial-peer pointing to Baltimore and the Baltimore hunt-group, which in-turn, rings both Ari and Arliss.

NewYork#sh run
!
voice translation-rule 3
rule 1 /0/ /1100/
!
!
voice translation-profile operator
translate called 3
!
!
dial-peer voice 1004 voip
translation-profile outgoing operator
destination-pattern 0
session protocol sipv2
session target ipv4:172.16.1.1
dtmf-relay rtp-nte
codec g722-64
no vad
!


6. Granting Arliss and Ari administrative privileges on CUE is as simple as adding each user to the Administrators group and adding a SIP phone number for prompt management.

groupname Administrators member amichaels
groupname Administrators member agold

ccn trigger sip phonenumber 1990
application "promptmgmt"
enabled
maxsessions 1
end trigger


7. The simplest way to restrict callers from dialing 976, 900, and 1010 number is to add a 24 x 7 call-blocking restriction to the telephony service on each router.

telephony-service
after-hours block pattern 1 9900 7-24
after-hours block pattern 2 9976 7-24
after-hours block pattern 3 91010 7-24

When testing this on both routers, I observed a difference in behavior between SCCP and SIP phones. On SCCP phones, once a pattern matched, such as 9-976, the user receives a fast busy tone. On SIP phones, rather than a receiving a fast-busy, the attempted call is simply dropped.


CUCME-CUE Lab 10.3 –CUCME-CUE Misc Items Wrap-up

This lab will likely conclude the CUCME-CUE labs, even though many Advanced CUE features such as IMAP, IVR, Live Record, and custom AA scripting were not covered. I am a bit torn on which topic to tackle next. My original intention was to continue to “build-out” Ballplayers, LLC as a true company might expand. Namely, I was going to stick with CUCME as the call processing, add a third CUCME site, and replace CUE with Unity Connection as a centralized integrated messaging solution. However, I am now gravitating toward jumping right to centralized call processing, Unified Communications Manager 7.0.

Each of these labs usually requires me a few days or even weeks of after-work-hours research and configuration. I will post the final configs for the Baltimore CUCME, New York CUCME, and Baltimore CUE in the coming days. Regardless of the direction that I ultimately decide upon, there will likely be a gap in posting for a few weeks. I am going to build a Microsoft 2003 Domain Controller with a simple AD to support which ever direction I take. I also plan to begin focusing a bit more on properly installing both Unity Connection and UCM in VMWare ESX 3.5, that way I am ready to roll in whichever direction I ultimately take.


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

Cisco Systems. Cisco Unity Express Voice-Mail and Auto-Attendant CLI Administrator Guide for 3.0 and Later Versions. Available online.

CUCME-CUE Lab 8 – Initial CUE Setup & Baltimore Messaging

Now that the CUCME systems for Baltimore and New York are functioning and employees can communicate with each other, Fuzzy Dunlop has given you the go ahead to implement voice messaging. However, due to the recession, funds are tight. As a result, Fuzzy has only given you the budget to purchase a single Cisco Unity Express AIM card to support both locations.

This lab will focus on the initial setup for CUE on the Baltimore 2811, as well as setting up basic voicemail for the Baltimore users. This lab and subsequent CUE labs are based on CUE 7.0. If you need to update you CUE image, excellent, well described instructions are outlined in the Cisco Unity Express 7.0 Installation and Upgrade Guide.

CUCME-CUE Lab 8.1 – Initial CUE Setup & Baltimore Messaging Tasks

1. Configure the Baltimore CUCME router to interface with CUE. Use extension 1999 as the voicemail pilot.

2. The IP Address for CUE should come from the voice subnet.

3. Use 8000 and 8001 for MWI.

4. Create voicemail users and mailboxes via the CUE CLI.

5. Mailboxes should be limited in size to accommodate up to 50 users on a AIM-CUE.

6. Make sure that messages can be forward via either dial by name or by extension.

7. Provision the system for GUI access.


CUCME-CUE Lab 8.2 – Initial CUE Setup & Baltimore Messaging Verification

1. Before you can begin configuring the CUE, you need to make some configuration modifications to the CUCME. A dial-peer needs to be created pointing to CUE. Next, the voicemail pilot needs to be added under the telephony-service. MWI is then created via an ephone-dn. Finally, call-forwarding needs to be provisioned for each user.

The details regarding the initial configuration parameters are covered in Configuring System Components chapter of the Cisco Unity Express Voice-Mail and Auto-Attendant CLI Administrator Guide for 3.0 and Later Versions.

Below are the configuration changes.

Baltimore#
!
dial-peer voice 1999 voip
destination-pattern 1999
session protocol sipv2
session target ipv4:10.1.12.3
dtmf-relay sip-notify
codec g711ulaw
!
telephony-service
voicemail 1999
!
!
ephone-dn 14
number 8000....
mwi on
!
!
ephone-dn 15
number 8001....
mwi off
!
ephone-dn 1 dual-line
call-forward busy 1999
call-forward noan 1999 timeout 4
!repeat for ephone-dns 2-5!
!
!
ephone 1
username "cripken" password null
!repeat for ephones 2-5!
!

2. Next step is to enable IP connectivity to the CUE. This requires some additional configuration on the CUCME side of the equation.

Baltimore#
!
interface Service-Engine0/0
ip unnumbered GigabitEthernet1/0.12
service-module ip address 10.1.12.3 255.255.255.0
service-module ip default-gateway 10.1.12.1
!

Once you’ve finished the above, you can session into the service-engine (CUE AIM).

Baltimore#service-module service-Engine 0/0 se
Baltimore#service-module service-Engine 0/0 session
Trying 10.1.12.1, 2194 ... Open
baltimore-cue#
baltimore-cue#

In the example above, I had previously logged into the CUE. If you haven’t yet done so, you will need to complete some basic CUE initialization tasks. Unfortunately, I was unable to find a concise document online that clearly articulates this initialization wizard. It is touched upon here. However, Chapter 11 of the IP Telephony Using CallManager Express Lab Portfolio covers it very well.


3. Now that there is connectivity between CUCME and CUE, users and mailboxes can now be created. Unfortunately, due to the way the CUE CLI functions, you have to create users in a somewhat disjointed fashion. The first step is to create the user and his/her phone numbers under configuration mode.

baltimore-cue(config)# username cripken create
baltimore-cue(config)# username cripken phonenumber 1001
baltimore-cue(config)# username cripken phonenumberE164 4105551001

Next, you need to create the mailbox for the use. However, per the requirement above, the configuration must support up to 50 users, thereby limiting the mailbox size to 720 seconds.

baltimore-cue(config)# voicemail mailbox owner "cripken" size 720
baltimore-cue(config-mailbox)#
baltimore-cue(config-mailbox)# description "cripken mailbox"
baltimore-cue(config-mailbox)# end mailbox

In order to facilitate the dial by name requirement, you must exit configuration mode and then modify the users their full first and last names.

baltimore-cue# username cripken fullname first Cal
baltimore-cue# username cripken fullname last Ripken

Finally, you can verify the user and the associate mailbox by issuing the “show user detail username NAME” and “show voicemail detail mailbox NAME” commands

baltimore-cue# show user detail username cripken
Username: cripken
Full Name: Cal Ripken
First Name: Cal
Last Name: Ripken
Nickname: Cal Ripken
Phone: 1001
Phone(E.164): 4105551001
Fax:
Email:
Epage:
Language: systemDefault
GroupMember:
GroupOwner:
Privileges:

baltimore-cue# show voicemail detail mailbox cripken
Owner: /sw/local/users/cripken
Type: Personal
Description: cripken mailbox
Busy state: idle
Enabled: true
Allow login without pin: no
Mailbox Size (seconds): 720
Message Size (seconds): 240
Play Tutorial: false
Fax Enabled: true
Space Used (seconds): 0
Total Message Count: 0
New Message Count: 0
Saved Message Count: 0
Future Message Count: 0
Deleted Message Count: 0
Fax Message Count: 0
Expiration (days): 30
Greeting: standard
Zero Out Number:
Created/Last Accessed: Feb 27 2009 17:47:37 EST


4. The final requirements on CUE involve configuration for communicating with CUCME and passing MWI. First, configure SIP to reach CUCME.

ccn subsystem sip
gateway address "10.1.12.1"
end subsystem

Next, the SIP trigger for the voicemail pilot, 1999, must be added to the system.

ccn trigger sip phonenumber 1999
application "voicemail"
enabled
maxsessions 4
end trigger

Finally, MWI must be enabled.

ccn application ciscomwiapplication aa
description "ciscomwiapplication"
parameter "strMWI_OFF_DN" "8001"
parameter "strMWI_ON_DN" "8000"

CUCME-CUE Lab 8.3 – Initial CUE Setup & Baltimore Wrap Up

CUCME and CUE has now been properly configured to interoperate. The best way to test the configuration is to place calls between phones and leave message. However, prior to this, each mailbox will require completion of the TUI setup wizard. Looking ahead, I will explore what it takes to have CUE support remote users, specifically the New York CUCME.

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

Cisco Systems. Cisco Unity Express 7.0 Installation and Upgrade Guide. Available online.

Cisco Systems. Cisco Unity Express 7.0 Release Notes. Available online.

Cisco Systems. Cisco Unity Express Voice-Mail and Auto-Attendant CLI Administrator Guide for 3.0 and Later Versions. Available online.

Schmidt, Cheryl A., and Friend, Ernie (2007). IP Telephony Using CallManager Express Lab Portfolio. Indianapolis: Cisco Press.

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.