Sevt 102008 Uc500 Lab
Sevt 102008 Uc500 Lab
Sevt 102008 Uc500 Lab
Lab Topology.......................................................................................3
Lab Overview:.....................................................................................4
UC520 UC520
The value “xx” should be set to the POD number that you have (goes from 01 to 12)
WAN IP addressing:
WAN IP Address 1.1.100.xx
WAN Subnet Mask 255.255.255.0
WAN Default Router 1.1.100.254
Inbound SIP Trunk DID (PSTN Call in) Numbers (Use PSTN phone to test)
Auto attendant 4085xx1200
Extension 1 (201) 4085xx1201
Extension 2 (202) 4085xx1202
VoiceMail 4085xx1209
In the lab documents, ‘xx’ refers to your Pod number. For example, if you are seated at POD01, you
would replace all instances of ‘xx’ in the lab documents with ‘01’.
Some of the labs may require you to partner with another pod to demonstrate certain features of the
system. This is usually to emulate an analog PSTN connection for the lab environment. Normally, you
would plug trunks from the PSTN into the FXO ports and analog devices (such as fax machines) into the
FXS ports. Please be sure and coordinate with the team seated at your ‘buddy’ pod so that you are both
working on roughly the same portion of a lab and can complete the verification steps successfully.
One of the labs requires an analog phone for completion. There is only a single analog phone for each
pair of Pods. Please share the phone between yourselves and your ‘buddy’ pod.
There are two Ethernet cables at each pod. These are both ‘broadband internet’ connections (emulating
the internet). One of these is for the UC500 WAN port, the other is used during the VPN lab to connect
your laptop. Either cable will work for either connection – there is no difference between them.
All of the software needed on your laptops to complete the lab is available for download from
http://zed.cisco.com/confluence/display/VOICE/SEVT-2008-Fall. Please copy all of this software to your
hard drive before the lab begins so you will have it when needed. This software will include the Cisco
Configuration Assistant (CCA) and Cisco IP Communicator (CIPC).
Please read items in RED very closely. These are notes / tips that will make the lab go much more
smoothly.
Lab1: Basic feature lab
Introduction:
The UC520 supports two voice system configuration types – PBX type and Keysystem type. This lab
focuses on the PBX system configuration. A typical PBX system involves an Auto Attendant that handles
incoming calls from a PSTN line (eg. Analog FXO trunks) and transfers the caller to one of the internal
extensions. Outbound local/LD/international calls are routed out through the PSTN line. In addition to
this, local extensions have voicemail boxes where callers can leave messages.
Objective:
The main objective of this lab is to configure the PBX system, voicemail and Auto Attendant features.
These features will be configured using Cisco Configuration Assistant (CCA). After completion of this
lab – you will be able to setup the SBCS system as a PBX, place calls between extensions, setup SIP
Trunk on the UC520 to a Service Provider (Lab Simulation), place calls in & out to the PSTN via the SIP
trunk.
Topology:
UC520
CCA
PSTN
Setup steps:
Be sure to turn off your wireless adaptor before completing the labs to avoid routing issues. The
only network connection from your laptop should be to the UC500 / lab network.
1. Be sure your UC500 system is powered up and plug one of the cables into the WAN port to port
11 on the catalyst switch.
2. At your pod, unplug a 7970 phone from the Catalyst switch (Skinny from the back row). Go to
the network configuration and make sure that the “Alternate TFTP” option is set to “No”. Once
verified plug in the 7970 IP Phone into the UC520 Power Over Ethernet (POE) ports. Also plug
in the 524 IP Phone into the UC520 PoE port. It may take a few minutes for the IP Phones to
upgrade their firmware and register to the UC500.
3. Connect your laptop to the back of an IP phone or to a POE port on the UC500. Verify that you
get an IP address assigned to the laptop.
4. After both 7970 and 524 have registered to the UC500, install and launch Cisco IP
Communicator (CIPC) SoftPhone on your laptop.
a. After launching CIPC, a Preferences Screen will appear (Right click on the CIPC to view
preferences if it does not appear). Now configure specific TFTP server on the network tab
as the UC520 IP address (192.168.10.1).
5. Ensure that all the phones register to the UC520 and receive an extension. Verify the extensions
as 201, 202 and 203 (CIPC)
6. Place a call between 201 & 202 – answer the call, place on HOLD and check if the Music on
Hold (MOH) works.
7. Place a call between 201 and CIPC (x203). Answer the call and place on hold on the IP
Communicator and note that the music plays to the IP phone. Take the call off hold and place it
on hold on the IP phone. Note that the IP Communicator only hears a hold tone and not the
MoH source.
8. Install Cisco Configuration Assistant (CCA) on your laptop.
9. Connect your laptop to one of the UC520 Ethernet ports or the Ethernet connection on the back
of an IP phone (if not already connected) & launch CCA.
10. On Launching CCA, a Connect window will appear. Click on “Create community” and click on
OK.
o Once discovery is complete (this may take a few minutes), click ‘OK’ to view the topology. The
progress for discovery can be seen at the bottom of the screen.
o Check the topology to ensure all the phones show up. You may or may not see the CIPC device,
depending on where your laptop is plugged in. If it is plugged into POE port of the UC520, the
CIPC will show up. If the laptop is plugged into the back of an IP phone, the CIPC will not show
up. The ‘PSTN_GW’ device showing is the 2821 that we are using to simulate the Internet and
SIP trunk provider.
11. Launch CCA, connect to the created community and enter the username and password
(cisco/cisco) and let it discover the network and connected devices. Now launch CIPC and make
sure it gets extension 203 (x203)
12. Check the topology to ensure all the connected phones are showing up. Unplug any lines that
are connected to the FXO ports on the PODs.
13. Click on “Configure -> Telephony -> Voice” on the left navigation bar or click on the Phone
icon on the top menu bar. Select “UC520” for hostname and click OK. Wait until the “Refresh”
and “Apply” buttons are enabled before making any changes. In this lab,, we will configure the
various tabs - “Device”, “System”, “Dialplan”, “AA & Voicemail”, “SIP Trunking” “Voice
Features”, and “Users”.
Note: The pull-down menu assists by showing the existing extensions on the system. In addition, you
can configure any number by overwriting “None”
22. Click on “ok” button at the bottom of the screen and observe the progress bar. Click OK when
the “Configuration successfully sent to UC520” message pops up. It may take several minutes
for the configuration to be applied to the UC500.
Note: This step is required for SIP trunk lab to function properly.
13. Call outbound from x202 to the PSTN by dialing the below patterns (there may be a slight delay in
getting the calls setup)
a. 911 (emergency call)
b. 9911 (emergency call)
c. 97771000 (local call)
d. 916507772000 (long distance call) – this should fail in
theory. However, there is a limitation with using the Generic
SIP Trunk provider pulldown where COR does not apply.
14. Call outbound from x201 to the PSTN by dialing the below patterns
a. 916507772000
b. 915102221234 (calls to 510 areacode should fail based on
blocked patterns)
c. 9011441234512345 (international call)
15. From CIPC, dial 501 to test the hunt-group functionality. The call should hunt to 201 and 202 and
should invoke the Auto Attendant on no answer.
16. From 524, dial 502 – the call should hunt to 301 and 203. It will then go to the GDM for 502.
Leave a message in the GDM and using CIPC ensure that the GDM messages can be checked.
This lab will focus on configuring some advanced features using CCA, CME/CUE GUI, and CLI.
Features configured in this lab include
a) Phone features - Monitor buttons, Overlays, Shared dns and Label
b) System features – Incoming call handling
1. Launch the “Voice” configuration page on CCA and go to the “Users” tab.
2. Select the more option for aip and set button 4 type as share and extension as 275 and click on ok
3. Select the more option for bip and set button 3 type as share and extension as 275 and click on ok
4. Select the more option for cip and set button 5 type as share and extension as 275 and click on ok
5. Then click on Apply at the bottom of the Voice configuration page.
6. Once the changes are applied, check both IP Phones for ext 275.
7. Verify the functionality – From cip make a call to 275 and ensure that both IP Phones ring.
- Answer the call on bip. When the shared line is in use by another phone, the CP-500 LED turns red
- On bip, place the call. When the shared line is in on hold by another phone, the CP-500 LED blinks red.
- On aip, press button 3 (ext 275) to resume the call. When the shared line is picked up, the CP-500 LED
turns solid green
1. Launch the “Voice” configuration page on CCA and go to the “Users” tab
2. Select the more option for cip. On button 4, select the type as Normal and specify the extension as 261.
On button 5, select the type as Normal and specify the extension as 262
3. Configure the following labels:
Button 1: 203_Primary
Button 2: No changes
Button 3: Shared_ext_275
Button 4: 261_SecondLine
Button 5: 262_ThirdLine
4. Click on ok for the “more” page and then click on Apply at the bottom of the Voice config page.
5. Verify the functionality – check the IP Communicator for the appropriate display of labels.
1. Launch the “Voice” configuration page on CCA and go to the “DialPlan” tab
2. Under the “Incoming Call Handling” section, select “Custom Configuration” for FXO trunks and then
click on “Configure” button.
3. Click on OK on the FXO port configuration window and then click on Apply at the bottom of the Voice
config page.
4. Verify the functionality. Use an analog cable to connect the FXO port on your UC500 to the FXS port
on the next pod’s UC500 (you may have to increase the CFNA timer on the FXS ports using CCA).
Follow the steps below to setup prompts for Auto Attendant. There are 2 ways to setup prompts, you can
either use “Sound Recorder” utility on windows and or you could setup a “prompt management”
system.
The other way to record prompt for Auto Attendant script is to use the “Prompt Management” script on
CUE. For this we will use the CUE Web GUI. The configuration steps are divided into 3 main sections.
StepB2: Click on the user aip. A “User Profile” window that displays all the parameters for a ip will pop
up. On this window, set the PIN number to 789, and click on Apply icon.
StepB3: Click on Groups tab, notice that the list contains IMAPgrp. Click on "Subscribe as member".
StepB4: In the “Find” window, enter "Administrator" for Group ID and click on Find. Check the Group
ID "Administrators" and click on "Select row(s)". Ensure aip shows as a member of administrator group
and close the “User Profile” window.
If you recorded the prompt using “Prompt Management”, then you need to first refresh the voice window.
You can refresh the voice window either by hitting the refresh icon on top left corner. Or you can close
and re-launch the voice window. Once the window is refreshed, you can select the prompt from the
“Menu Prompt” pull-down menu.
To verify the functionality try calling the your AA number from PSTN 4085xx1200 and make sure
you hear the prompt recorded earlier.
Note: If you do not hear the prompt, you may need to remove access-list from the CUE
interface. The CLI for removing the access-list is listed below:
config t
interface Integrated-Service-Engine0/0
Cisco Unified Communications Technical Training
Page 30 of 31
no ip access-group 100 in
end