CAPPS
Integrating Cisco Unified Communications Applications (CAPPS) v8.0 Remote Lab Administration Guide
Contents 1.
Overview ....................................................................................................................... 4
2.
Course Version .............................................................................................................. 4
3.
Remote Lab Topology ................................................................................................... 5
4.
Remote Lab Description ................................................................................................ 6
5.
Classroom Router Configuration .................................................................................. 8
6.
Local Classroom Description ......................................................................................... 8
7.
Classroom PC requirement ........................................................................................... 9
8.
Cisco Unified Communications Manager/CUC/CUPS Setup ....................................... 10
9.
PSTN Setup .................................................................................................................. 11
10.
Configuration .............................................................................................................. 12 10.1. Remote Router configuration ......................................................................... 12 10.2. Remote switch Configuration ......................................................................... 14
11.
Firmware Files for IP Phones ...................................................................................... 17
12.
Software’s Folder ........................................................................................................ 17
13.
Lab Exercise Tips ......................................................................................................... 17 13.1. Lab 2-1: Integrating Cisco Unity Connection with Cisco Unified Communications Manager .............................................................................. 17 13.2. Lab 2-2: Configuring Cisco Unity Connection System Settings. ...................... 18 13.3. Lab 2-4: Implementing Cisco Unity Connection Call Management ................ 18 13.4. Lab 2-5: Configuring Cisco Unity Connection Users ....................................... 19 13.5. Lab 2-6: Troubleshooting Cisco Unity Connection (Optional) ........................ 19 13.6. Lab 3-1: Integrating Cisco Unity Express with Cisco Unified Communications Manager Express ................................................................ 21 13.7. Lab 3-2: Configure Cisco Unity Express System Settings ................................ 21 13.8. Lab 3-3: Configuring Cisco Unity Express Users ............................................. 21 13.9. Lab 3-5: Troubleshooting Cisco Unity Express (Optional) .............................. 22 13.10. Lab 4-1: Implementing VPIM in Cisco Unity Connection and Cisco Unity Express ............................................................................................................ 23 13.11. Lab 5-1: Implementing Cisco Unified Presence with Cisco Unified Communications Manager.............................................................................. 23 13.12. Lab 5-2: Configuring Cisco Unified Presence Features and Implementing Cisco Unified Personal Communicator ........................................................... 25
© 2010, Global Knowledge
Remote Lab Administration Guide
Page 2 of 27
13.13. Lab 5-3: Troubleshooting and Verifying Cisco Unified Presence Components (Optional) .................................................................................. 25 14.
Remote Lab Support ................................................................................................... 27
3 of 27 Integrating Cisco Unified Communications Applications (CAPPS) v8.0
© 2010, Global Knowledge.
1.
Overview Integrating Cisco Unified Communications Applications (CAPPS) v8.0 teaches learners the integration options of Cisco Unified Presence, Cisco Unity Express, and Cisco Unity Connection. It describes voice messaging deployment scenarios, Cisco Unified Presence features, and troubleshooting mechanisms as well as Cisco Unified Presence and Cisco Unified Personal Communicator integration options with Cisco Unified Communications Manager.
2.
Course Version This is the original release of the course named Integrating Cisco Unified Communications Applications (CAPPS) v8.0.
© 2010, Global Knowledge
Remote Lab Administration Guide
Page 4 of 27
3.
Remote Lab Topology The Lab topology diagram for the CAPPS v8.0 Remote Lab is based on topology mentioned in Cisco Lab Guide.
Each Pod consists of a HQ network and a BR network The HQ network consists of the following components
1 Cisco Unified Communications Manager Server
1 HQ Gateway 2811 ISR with 1 MFTE1 and 1 Serial WAN Interface Card.
1 Student PC
1 Active Directory Server
1 Cisco Unity Connection Server
1 Cisco Unified Presence Server
The BR network consists of
1 BR 2811 ISR with 1 2MFTT1/E1 module and 1 Serial WAN Interface Card
1 Student PC
(Please note that the E1 module is inserted in Slot 0 and WIC-2T is inserted in Slot 1 of the ISR Router in both HQ and Branch Network) 5 of 27 Integrating Cisco Unified Communications Applications (CAPPS) v8.0
© 2010, Global Knowledge.
4.
Remote Lab Description The remote lab network is divided into two.
Data Network
Voice Network
The remote lab Data Network is accessed via http to the following location. http://rlabs3.globalknowledge.ae
Login using the credentials provided in the access details email from Remote Lab Support Team. (In case you don’t have the relevant RDC client software or required version, you will be redirected to Microsoft site for installation of the software).
Once logged in, click on the pod icon that you have been assigned to. You will be prompted again for the username/password, use the same credentials you provided during the initial authentication.
At this point a new window opens up the lab topology for this lab. You can gain access to the desktops/consoles of the different devices in the lab by simply clicking (left Click) the device that you would like to access.
Once a device is clicked, a new tab is added to the lab interface which gives access to the clicked device.
Access to PC’s/Servers in the lab is multiple while the console connections are exclusive. If you are unable to access the console of a particular device you can always clear the console lines to that device by selecting Clear line of the device option obtained by right clicking the (tab name)/(device from topology) .
Depending on the type of device you are connected to, further general administrative tasks listed below can be carried out by right clicking the respective Server/PC/Device from the topology/tab name.
For Devices
Close console connection to the device Change font of the terminal Clear line of the device Power Management
For Server/Client PC’s Send Ctrl Alt Del to Server/PC Close console connection to Server/PC Power Management
© 2010, Global Knowledge
Remote Lab Administration Guide
Page 6 of 27
A helpful tips section is also provided towards the bottom right corner of the topology that lists the Known issues/work around that the remote lab developer has come across during the preparation of this lab.
Following are the list of devices that are accessible from the Student topology for this lab.
HQ Router Student PC (HQ Data Network) BR Router Student PC (BR Data Network) Helpful Tips
Following are the list of devices that are accessible from the Student topology for this lab. PSTN Router Helpful Tips
All the tasks will be carried out from these machines as required by the respective lab. All the software/tools required for executing the labs are present on the respective machines. The Voice Network is tunneled into the classroom by means of an L2TP IPSEC VPN tunnel. The classroom will require some equipment to support this. The equipments require for setting up this connection is mentioned Section 6 of this Guide.
7 of 27 Integrating Cisco Unified Communications Applications (CAPPS) v8.0
© 2010, Global Knowledge.
5.
Classroom Router Configuration You will need the following parameters from the Remote Lab Admin before configuring the classroom router: Pre-shared Authentication key The configs for the classroom router is provided in the Configuration section.
6.
Local Classroom Description Each Rack consists of 2 Pods and each rack can accommodate 4 delegates. You will require the following equipments in the Classroom per Rack.
6 IP Phones (7960/7961/7965)
2 Windows Workstation (for browsing Data network of the lab via the internet)
2 IP Phones (7960/7961/7965) / 2 Windows Workstation with IP Communicator Software installed (For PSTN Phone)
The Classroom will have common infrastructure, which is listed below:
Cisco 18xx or 28xx router with IPSEC image Catalyst 3550 or 3560 POE Switch
The VPN Termination box at our end is capable of NAT Traversal. In case of NAT/PAT devices in between the classroom router and our VPN Concentrator, kindly ensure the Router is upgraded to version adventerprisek9-ivs_mz 12.4(10) or above for connecting to the Remote Lab.
All Phone simulating PCs and Phones must be directly connected to a POE switch. Each student PC/Phones must belong to the VLAN associated with each pod. The Fa 0/0 interface of the IPSEC router is connected to the switch. The Fa 0/1 interface of the IPSEC Router is connected to an Internet-accessible network. The configs for the classroom switch and Router is provided in the Configuration section.
© 2010, Global Knowledge
Remote Lab Administration Guide
Page 8 of 27
7.
Classroom PC requirement All the tasks will be carried out through HTTP/RDP connection to the remote labs from the Classroom PCs. The classroom should be equipped with Laptop/PC per pod with either Windows XP or Windows Vista. No other operation system is supported at this moment. DESCRIPTION Student Laptop/PC (per Pod)
QTY. 1
Windows XP*/Vista with latest Service Pack Windows RDP Client 6.1 *Windows 2003 or any other Windows 64 bit OS is not supported for connecting to the remote lab In case you are behind firewall, please ensure that Ports TCP/80 and TCP/443 are permitted from the classroom to the following remote lab websites. rlabs1.globalknowledge.ae rlabs2.globalknowledge.ae rlabs3.globalknowledge.ae Note: The underlying protocols used in communication with the Remote labs are HTTP (TCP/80) and RDP (TCP/3389). RDP port (3389) is forwarded to port 443 to permit access to Remote Labs from most of the classroom environments behind firewall with stringent policies. The underlying protocol is still RDP but running on port 443 instead of the standard port 3389. If you are behind an application layer firewall, which inspects traffic on layer 7 and looks in to RFC compliance of the protocols, then RDP protocol would not function over port 443. You need to ensure that Application Layer firewalling is disabled for traffic to remote labs.
9 of 27 Integrating Cisco Unified Communications Applications (CAPPS) v8.0
© 2010, Global Knowledge.
8.
Cisco Unified Communications Manager/CUC/CUPS Setup The IP addressing for the Call Manager is as per the Lab Guide and is listed below for your reference. Cisco Unified Communications Manager
Host name: CUCM1-x (x is the pod number)
IP: 10.x.1.1 (x is the pod number)
Mask: 255.255.255.0
Gateway: 10.x.1.101 (x is the pod number)
Administrator ID: admin
Administrator password: adpass1
Database Security Password: secpass1
NTP Server: 10.x.1.101
Security password: secpass1
Application user username: cucmadmin
Application user password: cucmpass1
Cisco Unity Connection
Host name: CiscoUm1 (x is the pod number)
IP: 10.x.1.3 (x is the pod number)
Mask: 255.255.255.0
Gateway: 10.x.1.101 (x is the pod number)
Administrator ID: admin
Administrator password: adpass1
Database Security Password: secpass1
NTP Server: 10.x.1.101
Security password: secpass1
Application user username: cucmadmin
Application user password: cucmpass1
Cisco Unified Communications Manager
© 2010, Global Knowledge
Host name: CUP1 (x is the pod number)
IP: 10.x.1.4 (x is the pod number)
Mask: 255.255.255.0
Gateway: 10.x.1.101 (x is the pod number)
Remote Lab Administration Guide
Page 10 of 27
9.
Administrator ID: admin
Administrator password: adpass1
Database Security Password: secpass1
NTP Server: 10.x.1.101
Security password: secpass1
Application user username: cucmadmin
Application user password: cucmpass1
PSTN Setup The PSTN cabling is mentioned below: Device Name
Interface
HQ-1
E1 0/0/0
HQ-1
S0/0/0
BR-1
E1 0/0/0
BR-1
S0/0/0
HQ-2
E1 0/0/0
HQ-2
S0/0/0
BR-2
E1 0/0/0
BR-2
S0/0/0
To Device
To Interface E1 0/0/0 S0/2/0 E1 0/0/1
PSTN
S0/2/1 E1 0/1/0 S0/3/0 E1 0/1/1 S0/3/1
The PSTN configuration already has dummy mac-addresses of 0000.0000.00001 and 0000.0000.0002 configured on ephone 1 and ephone 2 respectively. If you are using IP Phones instead of IP communicator then these mac-address will need to be replaced with the original mac-addresses of the IP Phones. The instructor Pod provides access to the console of the PSTN router. The telnet and enable passwords for the PSTN Router are as below
Telnet Password Enable Password cisco cisco123
11 of 27 Integrating Cisco Unified Communications Applications (CAPPS) v8.0
© 2010, Global Knowledge.
10.
Configuration 10.1.
Remote Router configuration The following sample configuration needs to be configured on the remote router. ! hostname Classroom-LTR ! pseudowire-class ToRemoteLab encapsulation l2tpv3 ip local interface Loopback0 ip pmtu ! ! username cisco privilege 15 password 0 cisco ! crypto isakmp policy 1 hash md5 authentication pre-share crypto isakmp key typekeyhere address 80.227.100.110 (Please refer to Lab Admin’s mail for pre-shared key) crypto isakmp nat keepalive 5 ! ! crypto ipsec transform-set voice-set esp-null esp-md5-hmac ! crypto map voice-map 1 ipsec-isakmp set peer 80.227.100.110 set transform-set voice-set match address 101 ! interface Loopback0 ip address 2.1.1.2 255.255.255.255 ! interface FastEthernet0/0 no ip address duplex auto speed auto ! interface FastEthernet0/0.112 encapsulation dot1Q 112 no snmp trap link-status no cdp enable xconnect 2.1.1.1 112 pw-class ToRemoteLab ! interface FastEthernet0/0.114 encapsulation dot1Q 114 no snmp trap link-status no cdp enable xconnect 2.1.1.1 114 pw-class ToRemoteLab ! interface FastEthernet0/0.119 encapsulation dot1Q 119 no snmp trap link-status no cdp enable xconnect 2.1.1.1 119 pw-class ToRemoteLab ! interface FastEthernet0/0.122 encapsulation dot1Q 122 no snmp trap link-status no cdp enable xconnect 2.1.1.1 122 pw-class ToRemoteLab ! interface FastEthernet0/0.124
© 2010, Global Knowledge
Remote Lab Administration Guide
Page 12 of 27
encapsulation dot1Q 124 no snmp trap link-status no cdp enable xconnect 2.1.1.1 124 pw-class ToRemoteLab
! interface FastEthernet0/0.129 encapsulation dot1Q 129 no snmp trap link-status no cdp enable xconnect 2.1.1.1 129 pw-class ToRemoteLab ! interface FastEthernet0/0.212 encapsulation dot1Q 212 no snmp trap link-status no cdp enable xconnect 2.1.1.1 212 pw-class ToRemoteLab ! interface FastEthernet0/0.214 encapsulation dot1Q 214 no snmp trap link-status no cdp enable xconnect 2.1.1.1 214 pw-class ToRemoteLab ! interface FastEthernet0/0.219 encapsulation dot1Q 219 no snmp trap link-status no cdp enable xconnect 2.1.1.1 219 pw-class ToRemoteLab ! interface FastEthernet0/0.222 encapsulation dot1Q 222 no snmp trap link-status no cdp enable xconnect 2.1.1.1 222 pw-class ToRemoteLab ! interface FastEthernet0/0.224 encapsulation dot1Q 224 no snmp trap link-status no cdp enable xconnect 2.1.1.1 224 pw-class ToRemoteLab ! interface FastEthernet0/0.229 encapsulation dot1Q 229 no snmp trap link-status no cdp enable xconnect 2.1.1.1 229 pw-class ToRemoteLab ! interface FastEthernet0/1 ip address type-ip-here duplex auto speed auto crypto map voice-map ! iproute 0.0.0.0 0.0.0.0 type-gateway-ip-here ! access-list 101 permit ip host 2.1.1.2 host 2.1.1.1 ! IOS Note :. The VPN Termination box at our end is capable of NAT Traversal. In case of NAT/PAT devices in between the classroom router and our VPN Concentrator, kindly ensure the Router is upgraded to version 12.4(10)T or above for connecting to the Remote Lab.
13 of 27 Integrating Cisco Unified Communications Applications (CAPPS) v8.0
© 2010, Global Knowledge.
10.2.
Remote switch Configuration Depending on the type of switch create vlans 112,114 and 119 for Rack1-Pod 1, 122,124 and 129 for Rack1-Pod 2 and so on as required for the different Racks and assign it to the respective ports on the switch. Make sure these ports are all access ports. Configure port 24 as trunk port and it should be connected to interface fastEthernet0/0 of the Class remote router. The student PCs/IP Phones should be connected to ports configured as part of their respective vlans. A Sample configuration for 2 Racks on a catalyst 3550 is shown below: hostname Classroom-SW ! no spanning-tree vlan 1-1005 ! enable password cisco vlan vlan vlan vlan vlan vlan vlan vlan
112,114,119 122,124,129 212,214,219 222,224,229 312,314,319 322,324,329 412,414,419 422,424,429
! interface FastEthernet0/1 description Rack1 Pod1 HQ Phone1-1 switchport access vlan 112 switchport mode access spanning-tree portfast ! interface FastEthernet0/2 description Rack1 Pod1 HQ Phone2-1 switchport access vlan 112 switchport mode access spanning-tree portfast ! interface FastEthernet0/3 description Rack1 Pod1 BR Phone3-1 switchport access vlan 114 switchport mode access spanning-tree portfast ! interface FastEthernet0/4 description Rack1 Pod1 PSTN Phone switchport access vlan 119 switchport mode access spanning-tree portfast ! interface FastEthernet0/5 description Rack1 Pod2 HQ Phone1-1 switchport access vlan 122 switchport mode access spanning-tree portfast ! interface FastEthernet0/6
© 2010, Global Knowledge
Remote Lab Administration Guide
Page 14 of 27
description Rack1 Pod2 HQ Phone2-1 switchport access vlan 122 switchport mode access spanning-tree portfast
! interface FastEthernet0/7 description Rack1 Pod2 BR Phone3-1 switchport access vlan 124 switchport mode access spanning-tree portfast ! interface FastEthernet0/8 description Rack1 Pod2 PSTN Phone switchport access vlan 129 switchport mode access spanning-tree portfast ! interface FastEthernet0/9 description Rack2 Pod1 HQ Phone1-1 switchport access vlan 212 switchport mode access spanning-tree portfast ! interface FastEthernet0/10 description Rack2 Pod1 HQ Phone2-1 switchport access vlan 212 switchport mode access spanning-tree portfast ! interface FastEthernet0/11 description Rack2 Pod1 BR Phone3-1 switchport access vlan 214 switchport mode access spanning-tree portfast ! interface FastEthernet0/12 description Rack2 Pod1 PSTN Phone switchport access vlan 219 switchport mode access spanning-tree portfast ! interface FastEthernet0/13 description Rack2 Pod2 HQ Phone1-1 switchport access vlan 222 switchport mode access spanning-tree portfast ! interface FastEthernet0/14 description Rack2 Pod2 HQ Phone2-1 switchport access vlan 222 switchport mode access spanning-tree portfast ! interface FastEthernet0/15 description Rack2 Pod2 BR Phone3-1 switchport access vlan 224 switchport mode access spanning-tree portfast ! interface FastEthernet0/16 description Rack2 Pod2 PSTN Phone switchport access vlan 229 switchport mode access spanning-tree portfast ! !
15 of 27 Integrating Cisco Unified Communications Applications (CAPPS) v8.0
© 2010, Global Knowledge.
interface FastEthernet0/24 description Connected to Classroom-LTR-Fa0/0 switchport trunk encapsulation dot1q switchport mode trunk ! Line vty 0 4 login password cisco ! end
© 2010, Global Knowledge
Remote Lab Administration Guide
Page 16 of 27
11. Firmware Files for IP Phones Firmware files for the following phones are loaded in to the flash of the Branch and PSTN Routers in the Remote Lab. If you are using a different model of Phone than the one’s specified below then you may request the remote lab support team to upload the required files to the flash of the respective device by sending them an email. o Cisco IP Phone 7960 o Cisco IP Phone 7961G o Cisco IP Phone 7965G
12. Software’s Folder All software’s required to carry out the lab exercises in this lab are placed on the desktop of the student PC’s under the folder CAPPS. This folder contains the following software
Cisco Unified Personal Communicator
13. Lab Exercise Tips 13.1.
Lab 2-1: Integrating Cisco Unity Connection with Cisco Unified Communications Manager Common Issues If the students have problems with call routing to Cisco Unity Connection, check if the correct voice mail profiles are assigned to the directory numbers.
After configuring and saving the SIP phone system configuration, make sure that the check box Register with SIP Server is check. If the SIP integration does not accept voice messages, this might resolve the issue.
Changes on a SIP trunk to Cisco Unity Connection require a reset and apply the configuration.
Check if the Cisco Unity Connection Administrator password needs to be renewed after a certain time frame counting from the installation time. Make sure that the students write the new password down. If the administrator password is lost or forgotten, you might reset the password via the CLI.
17 of 27 Integrating Cisco Unified Communications Applications (CAPPS) v8.0
© 2010, Global Knowledge.
13.2.
Lab 2-2: Configuring Cisco Unity Connection System Settings. Common Issues
13.3.
When delivering remote trainings, the time zone of the Cisco Unity Connection server might not be the time zone where the class is delivered. Students might dynamically adjust the specified times in the lab guide for the schedule to do the schedule some testing.
The first LDAP synchronization requires 5 minutes even if only two users exist. Do no cancel the process. Subsequent synchronizations are done within seconds.
Lab 2-4: Implementing Cisco Unity Connection Call Management Instructor Notes Since four directory numbers are set up to use the call routing with different rules, make sure that students configure the correct voice mail profile and call routing rules, before testing. If the forwarded number is not send over the SIP trunk, check the box Redirecting Diversion Header Delivery – Inbound and Redirecting Diversion Header Delivery – Outbound on the SIP trunk pointing to Cisco Unity Connection. Without these boxes being checked, the forwarded number is stripped. Task 4, Step 6 – Since Audio is not supported over RDP between the Remote lab and customer location, an audio controller is not installed on the Remote lab Student PC’s. For this reason the students will not be able to record/play any messages using the Media Master applet provided by the browser. The students will need to login to the phones to be able to record/change greeting messages.
Common Issues
Task 1, Step 18 – the announcement that Arvin Sloane is not available is sometimes not working for the first call. Retest, for the second call the expected announcement is played. In Task 4, the dial plan implementation is used. Misconfigurations in the previous lab 2-3 might lead to issues in the testing procedure. For the interview handler recordings are required to play the questions to the caller. Java problems might lead to empty or no recordings. Without a
© 2010, Global Knowledge
Remote Lab Administration Guide
Page 18 of 27
recording the question is not played, with no recording at all the interview handler might not be dialable.
13.4.
Lab 2-5: Configuring Cisco Unity Connection Users Instructor Notes When configuring a private distribution list the browser logs in as the end user via Cisco PCA. If changes are not reflected and the users cannot be selected or found, close the browser and go back to Edit > Private Distribution Lists for the relevant user. Task 7, Step 8 – During our testing it was noted that it took a while before the users were listed. Log off and re-login helped in this instance
Common Issues
13.5.
When importing users, the template is sometimes not selected by the students. This may lead to users being in a wrong partition or similar issues, which impacts the testing procedure.
Lab 2-6: Troubleshooting Cisco Unity Connection (Optional) Instructor Notes Trouble Tickets will need to be inserted into the lab equipments by the Instructor prior to starting this lab. Carry out the steps below to insert appropriate tickets.
Trouble Ticket 1: Message Buttons Are Not Working Step 1 In Cisco Unity Connection, go to the Attempt Sign In direct call routing rule and change the Conversation parameter in the Send Caller to area to Attempt Forward and save.
Trouble Ticket 2: Messages Cannot Be Left Step 2 In Cisco Unity Connection, go to the user John Doe (2001) and edit the Standard greeting settings. Select Hang Up in the After Greeting Call Action field and save. Step 3 For the user Jane White (2002), set the message action for voice mail to Reject the Message and save.
19 of 27 Integrating Cisco Unified Communications Applications (CAPPS) v8.0
© 2010, Global Knowledge.
Step 4 On Cisco Unified Communications Manager, go the SIP trunk configuration and uncheck the box: Redirecting Diversion Header Delivery - Outbound. Save and apply. This disables receiving voice mail on 3001 and 3003. Step 5 In Cisco Unity Connection, create a new partition RB. Go to the user David Gray (3003) and change the partition to RB and save.
Trouble Ticket 3: MWI Is Not Working Step 6 On Cisco Unified Communications Manager Administration, go the MWI On directory number and set the calling search space to . Step 7 On Cisco Unity Connection Administration, go to the SCCP port called PhoneSystem-1-001 and uncheck the box Send MWI requests and save. Step 8 Go to the SCCP port group called PhoneSystem-1 and uncheck the box Enable Message Waiting Indicators and save. Step 9 Go to the user Michael Black and edit the MWI. Select MWI-1 and uncheck the box Enabled and save.
Trouble Ticket 4: HQ Directory Call Handler Is Not Working Step 10 In Cisco Unity Connection, go to the HQ directory handler and change Last Name, First Name to First Name, Last Name and save.
Trouble Ticket 5: Alternate Number Is Not Recognized Step 11 In Cisco Unified Communications Manager Administration, go to translation pattern 1201201.XXXX. For the Calling Party Transformations value, add Prefix Digits (Outgoing Calls): + and save.
© 2010, Global Knowledge
Remote Lab Administration Guide
Page 20 of 27
13.6.
Lab 3-1: Integrating Cisco Unity Express with Cisco Unified Communications Manager Express Instructor Notes Task 1, Step 6 – The students need to configure FastEthernet0/0.yx4 instead of GigabitEthernet as the Branch router uses FastEthernet ports.
13.7.
Lab 3-2: Configure Cisco Unity Express System Settings Instructor Notes If the Cisco Unity Express GUI does not show the apply button, close the page and browse again to that configuration page. Task 1, Step 20 – Since Audio is not supported over RDP between the Remote lab and customer location, an audio controller is not installed on the Remote lab Student PC’s. For this reason the students will not be able to record/play any messages using the Media Master applet provided by the browser. The students will need to login to the phones to be able to record/change greeting messages.
Common Issues Since the time schedule only allows configuration slots of 30 minutes, the testing might have to be done after that time frame (for open and closed) or the students simply switch the schedule configuration and test again.
13.8.
Lab 3-3: Configuring Cisco Unity Express Users Instructor Notes Task 5, Step 8 – If the phones registered with Cisco Unified Communications Manager Express do not show the service when pressing the services button, verify that the phone load is a Cisco Unified Communications Manager Express phone load. A Cisco Unified Communications Manager phone load might prevent showing the phone services list. Enter the following command on the branch router if the Services url is not being displayed on the Branch Phone. ip http server
21 of 27 Integrating Cisco Unified Communications Applications (CAPPS) v8.0
© 2010, Global Knowledge.
13.9.
Lab 3-5: Troubleshooting Cisco Unity Express (Optional) Instructor Notes Trouble Tickets will need to be inserted into the lab equipments by the Instructor prior to starting this lab. Carry out the steps below to insert appropriate tickets.
Trouble Ticket 1: SIP Integration Is Not Working Step 17 In Cisco Unified Communications Manager Express, modify the route to Cisco Unity Express with the wrong IP address. Remove the route to 10.x.4.3 and add a route to 10.x.4.102 as follows: no ip route 10.1.4.3 255.255.255.255 Internal-ServiceModule0/0 ip route 10.1.4.102 255.255.255.255 Internal-ServiceModule0/0
Step 18 In Cisco Unified Communications Manager Express, modify the Cisco Unity Express dial peer with the wrong IP address and codec as follows: dial-peer voice 2500 voip session target ipv4:10.1.4.33 codec g711alaw
Trouble Ticket 2: Subscriber and Mailbox Issues Are Reported Step 15 In Cisco Unity Express, go to the Voice Mail > Mailboxes window. Select Mailbox Owner mblack. Uncheck the Enabled check box and click Apply. Step 16 In Cisco Unity Express, go to the Configure > Groups window. Select the SalesManager group. Uncheck the vm-imap check box and click Apply.
Trouble Ticket 3: MWI Is Not Working Step 12 In Cisco Unity Express, go to the Voice Mail > Message Waiting Indicators > Settings window. Uncheck the Outcalling check box and click Apply. Step 13 In Cisco Unified Communications Manager Express, modify the MWI ephone-dns to remove the dots in the number command as follows:
© 2010, Global Knowledge
Remote Lab Administration Guide
Page 22 of 27
ephone-dn 39 number 2511 ephone-dn 40 number 2512
Step 14 In Cisco Unity Express, configure the wrong SIP gateway hostname field to 10.x.4.102 as follows: service-module internal-Service-Module 0/0 session configure terminal ccn subsystem sip gateway address 10.x.4.12
13.10. Lab 4-1: Implementing VPIM in Cisco Unity Connection and Cisco Unity Express Common Issues
If students forget to configure the local location ID on Cisco Unity Express VPIM will not work.
After the SMTP server changes the services, Connection Conversation Manager and Connection Message Transfer Agent need to be restarted. Also if VPIM is not working and you did some changes, restarting both services might resolve the issue.
13.11. Lab 5-1: Implementing Cisco Unified Presence with Cisco Unified Communications Manager Instructor Notes With the default installation Cisco Unified Presence runs in an evaluation mode. In evaluation mode, a Cisco Unified Personal Communicator in softphone mode can be registered with Cisco Unified Communications Manager but calls cannot be made. Also, all users that are configured in Cisco Unified Communications Manager are synchronized with Cisco Unified Presence without enabling the presence capabilities. The Cisco Unified Presence troubleshooter might help you to identify issues in the integration. The students have to reconfigure the user IDs in Cisco Unified Communications Manager to avoid supplicated users when configure intercluster peering. That implies that the users in Cisco Unity Connection also need to be modified in the later labs.
23 of 27 Integrating Cisco Unified Communications Applications (CAPPS) v8.0
© 2010, Global Knowledge.
Common Issues
Students are not able to change the domain name. Carry out the steps below before you can change the domain name of the Presence server. From the Navigation Pane of the Presence Server Select Cisco Unified Serviceability On the Window that appears Select Tools-> Control Center – Network Services and stop the following Services o Cisco UP Presence Engine Database o Cisco UP XCP Router From the Navigation Administration
Pane
select
Cisco
Unified
Presence
Select System -> Cluster Topology -> Settings. In the Domain Name Text box you can change the domain name to required name as per the Lab guide. Once changed ensure to restart the two services that was turned off earlier.
When configuring the Inter-cluster Peer to the neighbor pod, both Cisco Unified Presence servers need to be in the same domain podp.com.
When adding users from the neighbor pod, the users might disappear after some seconds in Cisco Unified Personal Communicator. Test this behavior with the Cisco Unified Presence version you might install in the lab.
© 2010, Global Knowledge
Remote Lab Administration Guide
Page 24 of 27
13.12. Lab 5-2: Configuring Cisco Unified Presence Features and Implementing Cisco Unified Personal Communicator Instructor Notes Task4, Step 26 – After logging in Cisco Unified Personal Communicator should display “ Use my 2001 for audio”
Common Issues When configuring the LDAP profile, the students might not replace the x in the search context, which leads to the issue that no contacts can be found on the Active Directory server.
13.13. Lab 5-3: Troubleshooting and Verifying Cisco Unified Presence Components (Optional) Instructor Notes Trouble Tickets will need to be inserted into the lab equipments by the Instructor prior to starting this lab. Carry out the steps below to insert appropriate tickets.
Trouble Ticket 1: Presence Status Is Not Updating Step 19 In Cisco Unified Communications Manager, go to the SIP Trunk Security Profile and uncheck the Accept Presence Subscription check box. Step 20 In Cisco Unified Communications Manager, go to the SIP trunk and set the Destination Address to 10.x.1.3. Step 21 In Cisco Unified Communications Manager, restart the Cisco CallManager service. If you do not restart this service, the presence status changes are still working.
Trouble Ticket 2: Resolve Cisco IP Phone Messenger Issues Step 22 In Cisco Unified Presence, go to Presence > Settings and uncheck the Enable CUPC 7 and IPPM Instant Messaging (clusterwide) check box. Step 23 In Cisco Unified Communications Manager, go to the end user Jane and associate the device 2001.
25 of 27 Integrating Cisco Unified Communications Applications (CAPPS) v8.0
© 2010, Global Knowledge.
Step 24 Restart the IP phone 2001. If you do not restart the IP phone, the Cisco IP Phone Messenger issue will not arise.
Trouble Ticket 3: Resolve LDAP Server and Voice Messaging Issues Step 25 In Cisco Unified Presence, go to Applications > Cisco Unified Personal Communicator > LDAP Profile and modify the Search Context. Remove the x in cn=Users, dc=podx, dc=com. Step 26 In Cisco Unity Connection, go to the class of service Voice Mail User COS. Uncheck the following boxes and save the changes:
Trouble Ticket 4: Resolve Desk Phone Control Issues
Step 27 In Cisco Unified Communications Manager, go to the device HQ Phone 2 and uncheck the Allow Control of Device from CTI check box. Step 28 Go to the directory number 2001 via the HQ Phone 1 configuration and uncheck the Allow Control of Device from CTI check box for the directory number only. Step 29 In Cisco Unified Presence, go to Application > Cisco Unified Personal Communicator > CTI Gateway Server and select the TCP gateway. Change the Hostname from 10.x.1.1 to CUCM1-x
© 2010, Global Knowledge
Remote Lab Administration Guide
Page 26 of 27
14. Remote Lab Support
Please note that our primary form of support is through email. Our email id is
[email protected]
In order to have an interactive communication with the instructors, we are also available on MSN and our MSN id is
[email protected].
In case you cannot find us on MSN, please send us an email and we will login in MSN at the earliest for you.
27 of 27 Integrating Cisco Unified Communications Applications (CAPPS) v8.0
© 2010, Global Knowledge.
