Cisco dCloud

Collaboration Specialist Training v2 - Cisco Endpoints

Last Updated: 18-JUNE-2018

About This Lab

This Cisco Endpoints lab includes:

• Requirements

• About This Solution

• Topology

• Get Started

• Scenario 1: DX70/80 Android to CE Conversion

• Scenario 2: Cisco IP Phone 8800 Series Enhanced Line Mode

• Scenario 3: In-Room Control with Touch 10

• Appendix A: CE-on-DX Additional Material

• Appendix B: 88xx Series Additional Material

• Appendix C: CE-on-DX Factory Reset

• Appendix D: Converting CE back to Android

Requirements
There are three distinct sections of this lab, each with their own endpoints. The table below shows the requirements to run all three
of these in their entirety.

Table 1. Requirements

Required Optional

● Router, registered and configured for Cisco dCloud ● None

● Laptop with Cisco AnyConnect®
● Two 88XX IP Phones
● DX70 or DX80
● An SX or MX endpoint running CE8.2.1 or later with a Touch 10

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 1 of 48
 Cisco dCloud

About This Solution

This lab is comprised of three sections that will explore the following topics:

• DX70/80 Android to CE Conversion

• Cisco IP Phone 8800 Series: Enhanced Line Mode

• In-Room Control on Touch 10 lab

Bonus Material and Appendices:

• Appendix A: Bonus material (optional) for CE-on-DX

• Appendix B: Bonus Material (optional) for 88xx

• Appendix C: CE-on-DX Factory Reset

• Appendix D: Converting CE back to the Android Operating System

Each section may be completed on its own. If completing the DX Android to CE Conversion and the desire to return the CE-on-DX
to Android please refer to the Appendices at the end of this guide.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 2 of 48
 Cisco dCloud

Table of Contents
COLLABORATION SPECIALIST TRAINING 2: ENDPOINTS LAB ................................................................................. 1
DX70/80 ANDROID TO CE CONVERSION .............................................................................................................. 5
ABOUT THIS SOLUTION ...................................................................................................................................................... 5
ABOUT THIS DEMONSTRATION............................................................................................................................................ 5
Resources ................................................................................................................................................................. 5
Limitations ............................................................................................................................................................... 6
REQUIREMENTS ................................................................................................................................................................ 6
TOPOLOGY....................................................................................................................................................................... 6
GET STARTED ................................................................................................................................................................... 7
SCENARIO 1. DX70/80 ANDROID TO CE CONVERSION ................................................................................................... 8
Self-Provision the DX ................................................................................................................................................................................ 9
Convert from Android to CE ..................................................................................................................................................................... 9
SCENARIO 2. REGISTERING CE-ON-DX TO CUCM ........................................................................................................11
SCENARIO 3. CE-ON-DX QUICK FEATURE OVERVIEW ....................................................................................................14
Enable Web Access and SSH for DX ........................................................................................................................................................ 14
Set Admin Password for DX on the Web-UI ............................................................................................................................................ 14
Web-UI Fundamentals ............................................................................................................................................................................ 14
TMS Phone Books ................................................................................................................................................................................... 16

CISCO IP PHONE 8800 SERIES: ENHANCED LINE MODE ........................................................................................19

ABOUT THIS SOLUTION ....................................................................................................................................................19
ABOUT THIS DEMONSTRATION..........................................................................................................................................19
Resources ...............................................................................................................................................................20
Limitations .............................................................................................................................................................20
REQUIREMENTS ..............................................................................................................................................................20
SCENARIO 1. UNDERSTANDING SESSION LINE MODE (QUICK REVIEW).............................................................................21
Self-Provision the 88XX ........................................................................................................................................................................... 22
SCENARIO 2. ENABLING ENHANCED LINE MODE...........................................................................................................25
Simplified New Call UI............................................................................................................................................................................. 29
SCENARIO 3. BEST PRACTICE CONSIDERATIONS ............................................................................................................30
IN-ROOM CONTROL ON TOUCH 10 LAB ..............................................................................................................32
ABOUT THIS SOLUTION ....................................................................................................................................................32
Introduction ...........................................................................................................................................................32
Definition of terms .................................................................................................................................................33
ABOUT THIS LAB .............................................................................................................................................................34
Resources ...............................................................................................................................................................34
Limitations .............................................................................................................................................................34
Customization Options ...........................................................................................................................................34
REQUIREMENTS ..............................................................................................................................................................34
SCENARIO 1. CONFIGURE IN-ROOM CONTROLS ............................................................................................................35
Steps .......................................................................................................................................................................35
APPENDICES ......................................................................................................................................................41
APPENDIX A. BONUS MATERIAL (OPTIONAL) FOR CE-ON-DX .........................................................................................42
Backup and Restore the DX .................................................................................................................................................................... 42
Far End Camera Control (Requires an SX or MX device) ......................................................................................................................... 42
APPENDIX B. BONUS MATERIAL (OPTIONAL) FOR 88XX .................................................................................................44

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 3 of 48
 Cisco dCloud

On-Premise PRT Reporting .....................................................................................................................................44

Control Default Wallpaper .....................................................................................................................................44
New Background Image .......................................................................................................................................................................... 45
Restart the TFTP service ......................................................................................................................................................................... 45
APPENDIX C. CE-ON-DX FACTORY RESET ....................................................................................................................46
APPENDIX D. CONVERTING CE BACK TO ANDROID ........................................................................................................47

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 4 of 48
 Cisco dCloud

DX70/80 Android to CE Conversion

Last Updated: 30-September-2016

About This Solution

The Cisco® DX70 and DX80 are next-generation collaboration devices, supporting audio and video communication. They deliver
powerful, always-on, highly secure and integrated unified communications, high-definition (HD) video, and support for cloud
services. The IT administrator can now migrate from Android-based firmware to CE (Collaboration Endpoint) software. CE
software on the DX offer many new features such TMS One-Button-to-Push (OBTP),TMS PhoneBooks, Far-End-Camera-Control
(FECC), VCS-Registration, H.323/H263, full Web-UI support, and Webex Teams registration. In addition, CE running on DX aligns
the DX user experience with both the SX and MX series room based endpoints for a consistent end user experience.

About This Demonstration

This preconfigured CE on DX demonstration includes:

• Scenario 1: Cisco DX70/80 Android to CE Conversion

• Scenario 2: Registering CE-on-DX to CUCM

• Scenario 3: CE-on-DX quick feature overview

Resources
For more information:

• Step-by-Step conversion guide: http://www.cisco.com/c/dam/en/us/td/docs/telepresence/endpoint/ce82/dx80-dx70-convert-

between-CE-android-based-software.pdf

• Release notes: http://www.cisco.com/c/dam/en/us/td/docs/telepresence/endpoint/software/ce8/release-notes/ce-software-

release-notes-ce8.pdf

• Admin Guide: http://www.cisco.com/c/dam/en/us/td/docs/telepresence/endpoint/ce82/dx70-dx80-

administrator-guide-ce82.pdf

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 5 of 48
 Cisco dCloud

Limitations
The following limitations apply to CE-on-DX software version CE8.2:

• The DX650 cannot be migrated to CE.

• Wireless LAN is not currently available on CE-on-DX CE8.2. On roadmap.

• Bluetooth Headsets are not currently supported on CE-on-DX. On roadmap.

• Anyconnect VPN is not supported on CE-on-DX. MRA is the supported remote connectivity solution.

• For full list of caveats please see CE-on-DX release notes

Requirements
The table below outlines the requirements for this preconfigured demonstration.

Table 2. Requirements

Required Optional

● Router, registered and configured for Cisco dCloud ● MRA

● Laptop
● DX70 or DX80
● Cisco 8800 series IP Phone

Topology
This content includes preconfigured users and components to illustrate the scripted scenarios and features of the solution. Most
components are fully configurable with predefined administrative user accounts. You can see the IP address and user account
credentials to use to access a component by clicking the component icon in the Topology menu of your active session and in the
scenario steps that require their use.

Figure 1. dCloud Topology

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 6 of 48
 Cisco dCloud

Table 3. Preconfigured User Information

User Name User ID Password Endpoint Devices Phone Extension

Anita Perez aperez C1sco12345 8800 Series Phone +1 408 555 6017 6017

Charles Holland cholland C1sco12345 DX +1 408 555 6018 6018

Get Started
BEFORE PRESENTING

Cisco dCloud strongly recommends that you perform the tasks in this document with an active session before presenting in front
of a live audience. This will allow you to become familiar with the structure of the document and content.

It may be necessary to schedule a new session after following this guide in order to reset the environment to its original
configuration.

PREPARATION IS KEY TO A SUCCESSFUL PRESENTATION.

Follow the steps to schedule a session of the content and configure your presentation environment.

1. Browse to dcloud.cisco.com, choose the location closest to you, and log in with your Cisco.com credentials.

2. Register and configure your router if this is the first time you will use the router with dCloud. [Show Me How]

3. Schedule a session. [Show Me How]

4. Test your connection. [Show Me How]

5. Verify that the status of your session is Active in My Dashboard > My Sessions.

NOTE: It may take up to 30 minutes for your session to become active.

6. Click View to open the active session.

7. For best performance, connect to the workstation with Cisco AnyConnect VPN [Show Me How] and the local RDP client on
your laptop [Show Me How]

• Workstation 1: 198.18.133.36, Username: cholland, Password: C1sco12345

NOTE: You can also connect to the workstation using the Cisco dCloud Remote Desktop client [Show Me How]. The dCloud
Remote Desktop client works best for accessing an active session with minimal interaction. However, many users experience
connection and performance issues with this method.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 7 of 48
 Cisco dCloud

Scenario 1. DX70/80 Android to CE Conversion

In this scenario, you will manually convert a DX running Android-based firmware to CE. It is important to understand that CE-on-DX
requires a brand new CUCM device type. Therefore, the latest CUCM device packs (pre-installed in this lab) are required or
otherwise the CE-on-DX will not register to CUCM. The CUCM minimum requirements for CE-on-DX are CUCM 9.1.2, 10.5.2,
11.0, or 11.5.

Figure 2. Example of the new CE-on-DX device type in CUCM. The old DX Android-based device type on the left just says “Cisco DX” whereas
the new CE-on-DX device type on the right says “Cisco TelePresence DX”

NOTE: It is highly recommended to install the device packs onto CUCM well in advanced of the endpoint firmware upgrade.
Otherwise, the CE-on-DX will be unable to register to CUCM. Device pack installation for a new device type requires a cluster wide
reboot for CUCM 9.1.2, 10.5.2, and 11.0.

NOTE: There may be situations where Android-based firmware is required on the DX instead of CE. DX will start shipping from the
factory with CE pre-installed and some customers might require Android-based firmware. Instructions are included in the
Appendix of this guide for converting from CE-on-DX to Android.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 8 of 48
 Cisco dCloud

Self-Provision the DX

1. The DX should register with a 4-digit directory number of 110X. Tap the Call icon, dial 1111, and then enter 6018 as the self-
provisioning ID followed by the # key in order for the device to self-provision as user cholland.

2. When prompted to, enter the PIN 1234. Wait for the device to reboot.

NOTE: When performing step 1 above, if the IVR fails with a fast/busy tone (due to CST lab network bandwidth limitations), then
skip to step 4 below and continue with the lab.

3. The DX will self-provision as Charles Holland and reboot.

NOTE: Normally, a DX running Android-based firmware does not auto-register to Unified CM if self-provisioning is enabled on
Unified CM. Instead, it can use LDAP credentials. If your screen says “Get Started” and prompts for LDAP credentials, then type
cholland into the User name box and C1sco12345 into the Password box and tap Sign in. A new device will be created in
Unified CM and automatically register the DX as Charles Holland.

Convert from Android to CE

4. On the DX Android-based endpoint, validate the version of software running on the DX. Check the Settings > About Device >
Active Load. Is it 10.2.5.207 or higher?

NOTE: The prerequisite for the CE migration to work is that the DX Android-based endpoint must be running a minimum of
10.2.5.207 or higher. Older versions of DX Android-based endpoints must first be upgraded to 10.2.5.207 or higher as 10.2.5.207
is the minimum intermediary “CE Ready” firmware.

5. Using your web browser log into CUCM at IP address 198.18.133.3. Click Cisco Unified Communications Manager link.
Credentials: administrator/dCloud123!

NOTE: If you are unable to connect to CUCM make sure your laptop is plugged into the RJ-45 cable connected to the PC port of
the 8800 series or DX. Also, make sure you disable wireless on your laptop so that traffic from your laptop is routed through the
RJ-45 cable. From your laptop, validate you can ping the CUCM at address 198.18.133.3.

6. Navigate to Device > Phone.

7. Locate your DX. For the search criteria use Device Type / contains / DX and then click Find.

8. Click the Device Name of your DX.

9. Type the following in the “Phone Load Name” section:

a. For DX70 type: sipdx70.ce821.rel.loads

b. For DX80 type: sipdx80.ce821.rel.loads

Figure 3. Cisco DX device page – Phone Load name

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 9 of 48
 Cisco dCloud

10. Click Save, OK, Apply Config, and then OK again.

NOTE: In the figure below, step A and step B have already been performed for you in the interests of time.

For step B, the file cmterm-synergy-ce8_2_1_no_defaults.cop.sgn has already been uploaded to the dCloud CUCM. This file
contains both the DX70 and DX80 firmware *.loads files necessary to convert an Android-based DX to CE.

You just performed Step C above by manually specifying the *.loads file. Step D will be performed later in the lab after the Android-
to-CE upgrade is complete.

Figure 4. Overview of the Process for Manual Migration of Android to CE using CUCM

NOTE: The “no defaults” in the file name of the firmware cop file cmterm-synergy-ce8_2_1_no_defaults.cop.sgn, means that
CUCM will not prepopulate the device defaults [under CUCM>Device>Device Settings>Device Defaults] so as to prevent an
accidental upgrade of all DX Android-based endpoints to CE within an enterprise.

11. Validate that the DX upgrade process has begun by looking at the CUCM “Download Status” on the DX phone page. Please
refresh the page to see updated status.

NOTE: The download and upgrade of CE to the DX using the dCloud normally takes approximately 15 to 20 minutes. However,
due to varying bandwidth conditions at a given site, the upgrade process might take longer.

This concludes this scenario.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 10 of 48
 Cisco dCloud

Scenario 2. Registering CE-on-DX to CUCM

In this scenario, you will register CE-on-DX to CUCM. Since CE-on-DX requires a new device type in CUCM, you must first
remove the old Android-based device-type in CUCM. Removal of the old device-type is required because CUCM prohibits
duplicate MAC addresses in its database.

NOTE: Do not attempt registering the CE-on-DX to CUCM without first removing the old Android-based device using the
same MAC address or CUCM will reject the registration. If you see the following error on your CE-on-DX when trying to register
to CUCM, the three most likely reasons are (a) duplicate MAC addresses in the CUCM database; (b) the device pack was not
installed; or (c) the CUCM was not rebooted after the installation of the device pack.

Figure 5. SIP Registration Failure

1. After the DX has upgraded to CE, find the old DX and delete it from CUCM. Do not perform this step if the DX is still running
Android or still downloading CE software from CUCM.

Figure 6. Delete old Android-based DX device-type

NOTE: Later in this lab, we will use CUCM self-provisioning to add the directory number for Charles Holland to the CE-on-DX. An
alternative manual migration technique (not covered in this lab but listed here for reference) is first to create a Bulk Administration
 Phone  Phone Template for the Cisco Telepresence DX. Then, you rename the MAC address of the Android-based device to
a dummy MAC (instead of deleting the old “Cisco DX” device), and then choose “Migrate Phone” on upper right side of the device
page where it says “Related Links” and choose the Cisco TelePresence DX template. The advantage of this technique is it will
migrate basic device settings (such as the directory number) and automatically delete the old device type, all without the use of
CUCM self-provisioning.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 11 of 48
 Cisco dCloud

2. After the deletion of the old device-type, allow the CE-on-DX to auto-register to CUCM. To do this, tap on the Get started icon
on the Welcome screen, then tap Other services.

Figure 7. Choose a call service

3. When you see Cisco UCM, accept the auto-detection of the TFTP server to allow it to register to CUCM. Tap Activate. You
should see an “Activated” message when successful. If you do not see a TFTP server address populated, type 198.18.133.3
after choosing Cisco UCM.

Figure 8. Other Services

4. The DX should register with a 4-digit directory number. Tap the Call icon, then dial 1111, and enter 6018 as the self-
provisioning ID followed by the # key in order for the device to self-provision as user cholland. Enter PIN 1234 when prompted.
Wait for the device to reset.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 12 of 48
 Cisco dCloud

5. After reset, validate your home screen on the CE-on-DX is assigned to the user Charles Holland as shown in the figure below.

Figure 9. Display of home screen with user Charles Holland

This concludes this scenario.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 13 of 48
 Cisco dCloud

Scenario 3. CE-on-DX Quick Feature Overview

In this scenario, you will learn some of the key features of CE-on-DX such as FECC, the Web-UI, and TMS support.

Enable Web Access and SSH for DX

1. On CUCM navigate to Device > Phone.

2. Find your DX. For the search criteria use Device Type / contains / DX and then click Find.

3. Click the Device Name of your DX.

4. Scroll down to Web Access. Choose HTTP+HTTPS.

5. Scroll down to SSH Access. Choose Enabled.

6. Scroll down to Admin Username and Password. For Admin password type cisco (all lowercase).

7. Click Save, OK, Apply Config, and then OK.

Set Admin Password for DX on the Web-UI

8. On CUCM (or on the DX device itself) find the IP address of the DX.

9. Open a new tab on your web browser and enter the IP address of the Web-UI of the DX.

10. Login as admin with no password.

11. Navigate to Security > Users.

12. Choose admin.

13. Where it says, change passphrase.

a. Enter cisco for passphrase (all lowercase).

b. Enter cisco to repeat passphrase.

14. Click change passphrase.

15. Log back into the DX admin page with the new credentials.

Web-UI Fundamentals

16. Go to the DX Web-UI on your web browser.

17. Click the Call Control menu.

18. From the DX call the 4 digit directory number of the 88xx phone on the right side of the desk. Answer the call then hang up.

19. Choose the Recents tab.

20. Highlight the directory number of the 88xx.

21. Choose “Add to local contacts”.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 14 of 48
 Cisco dCloud

22. On the Web-UI click the “Setup” menu and then choose “Local Contacts” from the drop down menu.

23. Choose the 8800 directory number, then click “Edit Contact” and change the name to 8800 and click Save.

24. On the DX touch screen, tap the call icon, then choose Directory.

25. Tap on the “Local Contacts” folder and validate that 8800 appears.

26. On the Web-UI, click “Setup” menu then “Personalization”.

27. For wallpaper, choose “None” and validate the screen changes. Now change it back to Auto.

28. Under “Setup” click “Status” and validate Uptime, Software Display Name / Release Date / Version, and under State validate
the Camera Lid state.

29. Under Setup > Configuration, click Conference, go to Auto Answer, and turn Mode and Mute to “On”. Click Save.

30. On the 8800, call the DX and validate it auto-answers and the mic is muted. End the call.

NOTE: For production environments, you must set Auto-Answer using CUCM. If you only use the Web-UI, it will eventually revert
to auto-answer off.

31. On Web-UI, under Setup>Configuration>Conference, change the MaxTransmitCallRate to 500. Click Save. Start a call with
the 8800 on the right side of the desk.

32. On Web-UI, click “Call Control” and under Participants click the information icon as shown below.

Figure 10. Participants - Call Status icon

33. Scroll down and validate the Outgoing Video channel rate is less than 500Kbps. What is the resolution? Validate the
Incoming Video is still greater than 1000Kbps. On the Web-UI click “Disconnect all”.

NOTE: Adjusting the Outgoing Video rate can be useful to change for people who work at home when the ISP throttles the
upstream bandwidth.

34. On the Web-UI click Security tab, then “Access PIN.” Enter 1234 and then “Set PIN”.

35. On the DX touch screen access the settings icon on the top left, then “System Information”, then “Settings”. Enter PIN and
leave this screen up on the DX.

36. On the Web-UI click “Maintenance”, User Interface Screenshots, Take Screenshot of OSD.

37. On the Web-UI click Maintenance, Diagnostics. Is anything red?

38. Now click Maintenance > Call logs. Is this information correct? What is the earliest call?

NOTE: The Maintenance menu will also allow you to perform administrative tasks such as remotely restarting the DX or to do a
factory reset.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 15 of 48
 Cisco dCloud

TMS Phone Books

1. From a supported browser navigate to TMS via http://198.18.133.158/tms. Alternatively, from Wkst1 launch Firefox and
using the menus navigate to Collaboration Admin Links > Cisco TelePresence Management Suite.

2. If presented with This Connection is Untrusted click I Understand the Risks.

3. Click Add Exception….

4. Click to Confirm Security Exception.

5. Login with username/password: administrator/C1sco12345.

NOTE: TMS 15.3 is required to support CE on DX

6. From the menus navigate to Systems > Navigator.

7. Under the Folder view click Infrastructure.

8. Click on ucm1.dcloud.cisco.com.

9. Click the Settings tab and then click on the Force Refresh button (as shown below).

Figure 11. Force Refresh

10. Once the page has refreshed, click the Managed Systems tab. Verify the DX shows up in red as shown in the figure below.

NOTE: It might take several minutes for the system to import new endpoints.

Figure 12. New endpoints

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 16 of 48
 Cisco dCloud

11. Now click the Endpoints folder.

12. Choose Add Systems.

13. Choose Add from Unified CM or TMS tab.

14. Check the box next to Charles Holland DX.

15. Click Next at the bottom of the screen.

16. Click the box next to the endpoint and add endpoint. If you see “Wrong System Settings”, just choose “Add System Despite
Warnings”.

Figure 13. TMS Add Result

17. Choose the newly added Charles Holland endpoint under the endpoints folder.

18. Click Phone Book tab.

19. Highlight Cisco dCloud and move this to the Phone Books Set on System.

20. Click Save.

21. On the DX tap the Call button and then the Directory button. It should resemble the default Cisco UDS directory below:

Figure 14. Non-TMS Phonebook

22. Now go into CUCM and add TMS phone book support. On CUCM find your DX.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 17 of 48
 Cisco dCloud

23. On CUCM on the DX device page, scroll down to Alternative Phonebook Server Type and click TMS.

24. For Alternate Phonebook Server Address type the following:

http://198.18.133.158/tms/public/external/phonebook/phonebookservice.asmx

25. Click Save. OK. Apply Config. OK.

26. On the DX tap the Call button and then the Directory button. It should now reflect the TMS phonebooks as shown below:

Figure 15. TMS Phonebook

This concludes this scenario and section of the lab.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 18 of 48
 Cisco dCloud

Cisco IP Phone 8800 Series: Enhanced Line Mode

Last Updated: 09-January-2017

About This Solution

This lab will explore a new feature in the Cisco 8800 series called Enhanced Line Mode available for the 8811, 8841, 8845, 8851,
8861, and 8865. This new feature in phone firmware 11.5 provides the ability to enable all 10-line keys on the Cisco 8800 as
programmable line keys (PLKs). The PLKs can be a mix of lines keys or functions such as speed dials. Historically, only 5-line
keys were available. This lab will compare and contrast the default experience versus the new Enhanced Line Mode in order to
determine the best solution for any given environment.

Figure 16. Session Line Mode [the default] versus Enhanced Line Mode

The Cisco 8845 and 8865 are video phones that are also able to run Enhanced Line Mode. The 8865 is at the high end of the
8800 series spectrum in terms of features and functionality. The Cisco 8865 features include:

• 720p HD video

• Two USB ports for charging smartphones or tablets

• Intelligent Proximity for telephony for integration with your mobile device

• 802.11a/b/g/n/ac Wireless LAN

About This Demonstration

This lab includes:

• Scenario 1: Understanding Session Line Mode

• Scenario 2: Enabling Enhanced Line Mode

• Scenario 3: Best Practice Considerations

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 19 of 48
 Cisco dCloud

Resources
For more information:

• Release notes detailing Enhanced Line Mode considerations:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/8800-series/firmware/releasenotes/p881_b_cisco-ip-phone-
8800-series.html#reference_C0581B37033CCE5B7DB882BC338DC886

• Admin Guide for 8800 series: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/8800-

series/english/adminguide/P881_BK_C136782F_00_cisco-ip-phone-8800_series.html

Limitations
The following are some of the limitations that apply to Enhanced Line Mode in 11.5 firmware:

• KEM support

• Smartphone (Bluetooth) proximity

• CME

• Call Park

• Right to Left locale support

• Please refer to 11.5 phone firmware release notes for a complete listing of the limitations.

Requirements
The table below outlines the requirements for this preconfigured demonstration.

Table 4. Requirements

Required Optional
● Router, registered and configured for Cisco dCloud ● VPN
● Laptop
● 8811, 8841, 8845, 8851, 8861, or 8865

Table 5. Preconfigured User Information

User Name User ID Password Endpoint Devices Phone Extension

Anita Perez aperez C1sco12345 Endpoint Devices +1 408 555 6017 6017
Charles Holland cholland C1sco12345 8800 Series Phone +1 408 555 6018 6018

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 20 of 48
 Cisco dCloud

Scenario 1. Understanding Session Line Mode (Quick Review)

With the introduction of the feature Enhanced Line Mode on the Cisco IP Phone 8800 series, it is necessary to introduce the term
Session Line Mode in order to understand the default behavior versus the new behavior. In short, Session Line Mode is what the
phone runs when it is not in Enhanced Line Mode. By default, the Cisco 8811, 8841, 8845, 8851, 8861, and 8865 run Session Line
Mode by default even after they have been upgraded to 11.5 firmware or higher. The administrator must take action after the
firmware upgrade and explicitly enable the phone to run Enhanced Line Mode using a new CUCM parameter.

NOTE: The end user has no ability to enable Enhanced Line Mode from the phone itself.

Since Enhanced Line Mode allows the phone to use all 10-line keys, it is tempting to enable it for all deployments. However, before
enabling Enhanced Line Mode in a production environment it is important to understand that Session Line Mode is the Cisco
recommendation for high call volume environments or for busy boss/admin scenarios. When Session Line Mode is properly
configured, the phone will display all call “sessions” on the right hand side of the screen to provide easy management of calls.

NOTE: The 8961 and 9900 series phones run only Session Line Mode and cannot be configured for Enhanced Line Mode.

You should carefully review the functionality of both Session Line Mode and Enhanced Line Mode in order to determine the best
solution for a given environment. This section will quickly review Session Line Mode best practices so that you understand how it
is different from Enhanced Line Mode.

Figure 17. Session Line Mode Best Practices

CST 2015 11.x lab from last year explores basic and advanced 88xx phone features. This lab will not duplicate the content from
last year. If you have not yet taken the CST 2015 11.x lab from last year on 88xx series and are interested in learning more, please
find the lab below and take this later to explore more features of the 88xx series. CST 2016 provides an executive summary
(review) of Session Line Mode best practices in a multi-line environment.

NOTE: Many post-deployment customer issues are a result of under-configuration of Session Line Mode. This best practice
summary is intended to help you avoid under-configuration issues for the 8800 series as well as the 8961 and 9900 models.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 21 of 48
 Cisco dCloud

Self-Provision the 88XX

1. Self-provision the 8800 for Anita Perez as follows:

a. On the 8800 series phone dial 1111 or use the Speed Dial that is programmed to dial 1111.

b. Follow the voice prompts and when prompted for the self-provisioning identification number enter 6017 followed by
the # button.

c. Press the # button once more to confirm.

d. Enter the PIN 1234 and press # when prompted.

e. The 8800 will now reboot and be assigned to Anita.

2. Use your laptop and a supported browser to connect to CUCM. Alternatively, if you choose to use a remote PC in dCloud, you
can use these steps:

a. Create an RDP connection to Workstation 1 (198.18.133.36).

b. Login with Username: dcloud\cholland and Password: C1sco12345.

c. Open Firefox and navigate to Collaboration Admin Links > Cisco Unified Communication Manager.

d. Click the Cisco Unified Communications Manager link.

e. Login with Username: administrator and Password: dCloud123!

3. From the main menus navigate to Device > Phone.

4. For the search criteria use Device Type / contains / 88 and then click Find.

Figure 3. Search criteria

5. Click the Device Name (Line) link for your device that is registered.

6. Under Association click Line [2] – Add a new DN.

7. For Directory Number enter 7017.

8. Click on a blank area on the page to refresh the page.

9. Change the Route Partition to Prime-DN-PT and click on a blank area again.

10. Change the Calling Search Space to Prime-CSS.

11. Scroll down toward the bottom of the page to the Line 2 on Device section and enter x7017 for Line Text Label.

12. Click Save, Apply Config, and then OK.

13. Return to main phone configuration and click Modify Button Items.

14. Move Line2 from Unassigned Associated Items to Associated Items and click Save, and then Close button.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 22 of 48
 Cisco dCloud

Figure 18. Reorder Phone Button Configuration

15. Verify your phone has re-registered with the new second line as shown in the figure below.

Figure 19. Secondary Line Display

16. Now enable Session Line Mode best practices by enabling the first of two features. On the phone configuration page, use Find
(Ctrl+F) to locate the setting Show All Calls on the Primary Line toward the bottom of the page. Change the drop-down list
box to Enabled.

17. Now enable the second feature. Find (Ctrl+F) the setting Revert to All Calls towards the bottom of the page. Change the
drop-down list box to Enabled and verify the Override checkbox is checked.

Figure 20. Show All Calls on Primary Line parameter and Revert to All Calls.

18. Click Save, OK, Apply Config, and then OK again.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 23 of 48
 Cisco dCloud

NOTE: Show All Calls on the Primary Line means you will see an unfiltered view of all calls across all lines even when the
primary line is in focus. Revert to All Calls allows the phone to return to the primary line after a call is ended on a non-primary line.

19. Choose line 7017 by pushing the left button associated to that line. Does the phone go off-hook? No, it simply puts the line in
focus so that only the sessions for that line are displayed on the right. (As we will see in the next section, Enhanced Line Mode
changes this behavior and is one of the major differences between Session Line Mode and Enhanced Line Mode).

20. Now choose Anita’s line and call the DX at 6018. Answer the call and leave the call up. (Mute the DX).

21. The call is answered in full screen. Click any key on the left side and then choose the line button 2 (x7017). Then choose
New Call, and call the directory number of the 8800 phone on the right side of your desk. Answer the call and leave the call
up. (Mute the second 8800).

22. Click Anita’s line to show the call list. You should now see both the DX call and the second 8800 call listed as “sessions” on
the right-hand side of the display even though the primary line is selected. The “All Calls” functionality allows the primary line
to see the call on line 2 even though line 2 is not in focus.

Figure 21. Show All Calls on Primary Line

In a high call volume or boss/admin environment, seeing all the calls displayed on the right hand side might be preferred over
Enhanced Line Mode. As we will see in the next section, in Enhanced Line Mode there is no combined or aggregated listing of all
calls on all lines displayed as a list of “sessions.”

23. From Anita’s line, resume the call to the DX, and then end the call to the DX. Now choose line 7017, resume the call to the
second 8800, and then end the call to the second 8800. Does the focus change back to Anita’s line? Yes, because Revert to
All Calls is enabled.

This concludes this scenario.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 24 of 48
 Cisco dCloud

Scenario 2. Enabling Enhanced Line Mode

In this scenario, you will enable Enhanced Line Mode on the phone.

NOTE: In the interests of time, the minimum firmware and device packs have already been installed on the dCloud CUCM.
However, outside of this lab if the environment does not meet both of the requirements below, then Enhanced Line Mode will not
be enabled:

A. Run the minimum phone firmware version of 11.5 on 8811, 8841, 8845, 8851, 8861, or 8865.

B. Install the latest CUCM device pack to enable the feature. The latest CUCM device pack containing the Enhanced
Line Mode parameter was published on July 2016. Enhanced Line Mode is supported on CUCM 9.1.2, 10.5.2, 11.0.1,
and 11.5. Out of these four versions of CUCM, only CUCM 11.5 has this parameter native, and the other CUCM
versions require the latest device pack.

1. On your 8800 series device page, scroll to the bottom and find “Line Mode.” Change the drop-down list box to Enhanced Line
Mode and verify the Override checkbox is checked.

Figure 22. Line Mode setting

2. Click Save, OK, Apply Config, and then OK again. The phone should now reboot into Enhanced Line Mode (ELM).

3. Validate visually that your phone is in Enhanced Line Mode (see figure below). The easiest way to identify if the phone is in
ELM, the new call icon and the clock icons are missing. (These are located on buttons 6 and 7 in Session Line Mode.) If the
icons are still there, as shown in the left figure below, then the phone is still in Session Line Mode. If they are no longer there
then the phone is in Enhanced Line Mode.

Figure 23. Session Line Mode versus Enhanced Line Mode (At-A-Glance) with minimal configuration

4. Click button 2 for line 7017. What happens? How is this different from Session Line Mode?

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 25 of 48
 Cisco dCloud

5. On the CUCM device page, validate that you see 10 lines available for use. It should resemble the figure below.

Figure 24. 10 Lines available in Enhanced Line Mode

NOTE: If you do not see 10-lines displayed on the 8800 series phone after enabling Enhanced Line Mode, or if you wish to
customize the template, you must create a 10-key Phone Button Template and apply it to the phone.

Figure 25. Custom Phone Button Template Creation (for reference)

6. Create a new Speed Dial on line 6 using the “Modify Button Items” on the CUCM device page. Then from the phone device
page click on “Add a new speed dial” and make this the directory number of the 8800 on the right side of the desk. Call the line
label “8800”.

Figure 26. Create a speed dial on line 6

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 26 of 48
 Cisco dCloud

NOTE: If you are unable to configure the speed dial exactly as shown in the figure above, try selecting one or more of the “None”
entries and then using the arrows that look like this move these to the “Disassociate These Items” window. You should now

be able to move the “Add a new SD” over from the right window to the left window. Now use up/down arrow to move the speed
dial so that is appears as shown in the figure above.

7. Click the speed dial on line 6 and validate it works. Your device should now resemble the figure below.

Figure 27. Speed dial on programmable line key 6

8. On button 7, just under the 8800 speed dial, create a new line 3 using “Modify Button Items”.

9. Save the changes.

10. Under Association Information click Line [3] – Add a new DN.

Figure 28. Create a new Directory Number on Line 7

11. For Directory Number enter 7018.

12. Click on a blank area in the page to refresh the page.

13. Change the Route Partition to Prime-DN-PT and click on a blank area again.

14. For Calling Search Space choose Prime-CSS.

15. Scroll down toward the bottom of the page to the Line 7 on Device section and enter x7018 for Line Text Label.

16. Click Save, Apply Config, OK.

17. On the phone, press Line button 7. (Notice how it also goes off-hook immediately). Your device should resemble the figure
below. When you press line 7 and hang up, what line is in focus?

NOTE: Revert to primary line is enabled by default in Enhanced Line Mode and is unrelated to the prior Session Line Mode setting.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 27 of 48
 Cisco dCloud

Figure 29. Directory number on line 7

NOTE: The ability to click a line button and have it go off-hook immediately is not possible in Session Line Mode on the 8800. This
new behavior is consistent with legacy TDM (Time-Division Multiplexing) phones and key systems. This behavior is also consistent
with both the 7800 and 7900 series phones.

18. Place a call on Line 7017 to DX. (Answer then mute the DX).

19. Now put that call on hold from the 8800 with the Pause/Hold button. From the same line (x7017), press “New Call” and call the
8800 on the right side of the desk. (Mute phone). Now put the second 8800 on hold from Anita’s 8800 using the Pause/Hold
button on Anita’s phone. Notice that the icon on the line x7017 oscillates from with the number “2”. See figure below.

Figure 30. Line Key Icon Behavior

20. Press the line key button for 7017. You can see that all the calls for that line appear. Toggle back to the DX and resume.

Figure 31. Toggling between lines in Enhanced Line Mode

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 28 of 48
 Cisco dCloud

NOTE: You can think of the “sessions” as being anchored to lines in Enhanced Line Mode. You access the “sessions” per line by
clicking on that line key. The ability to see all sessions at a glance like in Session Line Mode is not possible in Enhanced Line
Mode.

21. Hang up all calls.

Simplified New Call UI

1. Simplified New Call UI within Enhanced Line Mode provides the ability to remove the pop-up you see when you go off-hook.
The reason why this feature has value to some customers is that it better emulates a 7900 series environment. This feature is
disabled by default because enabling it turns off predictive dialing. Nevertheless, the feature is there should you need it.

Figure 32. Simplified New UI: Before and After

2. On CUCM on the 88xx device page, find (Ctrl+F) the setting Simplified New Call UI toward the bottom of the page.

3. Change the drop-down list box to Enabled and verify the Override box is checked. Save, OK, Apply Config, and then OK.

Figure 33.

4. On the 8800 go off-hook on any line.

5. Validate the absence of the New call pop-up window. Type the digits for the DX 6018 and place a call. Hang up.

Figure 34. Validation of Simplified New Call UI

This concludes this scenario.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 29 of 48
 Cisco dCloud

Scenario 3. Best Practice Considerations

In this scenario, you will understand when to choose Session Line Mode versus Enhanced Line Mode. In the previous section, you
looked at the benefits of Enhanced Line Mode such as the ability to use all 10-line keys, TDM-like behavior, and easy call
management. In this section, we will look at situations that might be better suited with Session Line Mode. We will also look at the
strengths and weaknesses (deployment considerations) of each mode.

1. Consider the following Enhanced Line Mode scenario. The line for Anita has 2 calls, line x7017 has 3 calls, and line x7018 has
2 calls. In order to know who is on a given line at any point in time, an administrative assistance might have to click each line
to find the specific caller because he cannot see all the sessions at a glance. In the figure below, although there are 7 calls in
progress, it is not possible to see all 7 calls in one listing. Instead, you have to click on each respective button to see the
sessions for that line.

Figure 35. Multiple calls on multiples lines in Enhanced Line Mode

2. By contrast, the exact same calls above are represented below on an 8800 series phone in Session Line Mode with a KEM.
As you can see in the figure below, all the calls for all the lines are listed on the right-hand side of the phone. The first two calls
are displayed for line one (Anita) with the session number on the far left indicating two calls on Anita’s line. Likewise, the next
three calls are on line two (x7017) with the session number on the far left indicating three calls on line x7017.

NOTE: The full listing of all seven calls (inclusive of those on the KEM) will not fit on the display below. Therefore, you must use
the navigation key on the center of the phone to scroll down so that you can see all of the calls in progress.

Figure 36. Multiple calls on multiple lines in Session Line Mode (using a KEM)

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 30 of 48
 Cisco dCloud

Best Practices Feature Comparison

The chart below indicates best practice features based upon the mode selected.

Figure 37. Best Practices Matrix – Session Line Mode Features compared with Enhanced Line Mode

Deciding Upon Session Line Mode versus Enhanced Line Mode

The chart below indicates the best mode to choose based upon a given environment.

Figure 38. Which Mode to Choose

Which Mode to Choose?

3. Think of some current or recent phone projects you have worked on. Based upon the two figures above, what is the best mode
for the environment? Would it make sense to provide a hybrid deployment with boss/admin running Session Line Mode, and
everyone else in the organization running Enhanced Line Mode?

This concludes this scenario and section of the lab.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 31 of 48
 Cisco dCloud

In-Room Control on Touch 10 Lab

Last Updated: 10-January-2016

About This Solution

Introduction
With In-Room Control you can add custom elements to the Touch 10 user interface. Such user interface extensions may be
controls for lights or blinds, or other peripherals controlled by external control systems.

Since both the Cisco video system and the other peripherals are now controlled from the Touch 10 user interface, you will get a
consistent user experience throughout the meeting room.

Figure 39. In-room control architecture

You can also add content sensitive controls appearing only when in a call and/or only outside calls. This means that altogether you
have three sets of panels at your disposal:

• Global panel has its entry icon in the status bar at the top of the Touch 10 display. Once established, this entry icon
is visible at all times.

• Homescreen panel has its entry icon located to the right of the buttons appearing along the bottom of the Touch 10
display. This entry icon is visible outside calls only.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 32 of 48
 Cisco dCloud

• In-Call panel has its entry icon located to the right of the buttons appearing along the bottom of the Touch 10 display.
This entry icon is visible when in a call only.

Figure 40. Example of Global and Homescreen in-room control panels on Touch 10. Any In-Call panel icons existing will be visible during calls
only

Definition of terms
Video system. Video system or codec in the Cisco TelePresence MX Series or SX Series running Collaboration Endpoint
Software, version CE8.2.1 or later. Sometimes referred to as video device.

Control system. Third-party control system with hardware drivers for peripherals, for example Crestron, AMX, Apple HomeKit, or
Android.

Touch 10. Our touch-based control device for the MX Series and SX Series video systems. Full product name: Cisco
TelePresence Touch 10. Also known as Touch 10 controller, or Touch 10 user interface.

In-room control panel. A GUI Panel on the Touch 10 with controls for third-party peripherals in the room. The panel opens when
you tap the corresponding in-room control icon in the status bar on Touch 10.

In-room control editor. Our easy to use drag-and-drop editor for making in-room control panels. xAPI. The bidirectional API of the
video system. The xAPI allows third-party applications to interface with and interact with the video system, and vice versa.

Widget. User interface element, for example buttons, sliders, and text fields, that you can use to build an in-room control panel for
Touch 10.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 33 of 48
 Cisco dCloud

About This Lab

This In-room controls lab includes:

• Scenario 1: Configure In-room controls

Resources
For more information:

• Visit the Cisco dCloud help page: https://dcloud-cms.cisco.com/help.

• Access all available Cisco dCloud content: https://dcloud.cisco.com.

• Contact the Technical Lead or the Business Development Manager for your region: https://dcloud-cms.cisco.com/help/dcloud-
collaboration-contacts.

• API guides: http://www.cisco.com/c/en/us/support/collaboration-endpoints/telepresence-quick-set-series/products-command-

reference-list.html

• In-room controls guide: http://www.cisco.com/c/dam/en/us/td/docs/telepresence/endpoint/ce82/sx-mx-in-room-control-guide-

ce82.pdf

Limitations
In this lab there is no control system so it will not be possible to perform real actions using any widget, instead some of these
widgets will be simulated.

Customization Options
After running through the lab, it is encouraged to create your own widgets to experiment with the in-room control editor and with the
user interfaces that can be configured.

Requirements
The table below outlines the requirements for this preconfigured lab.

Table 6. Requirements

Required Optional

● Router, registered and configured for Cisco dCloud

● Laptop with a web browser
● An SX or MX endpoint running CE8.2.1 or later with a Touch 10

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 34 of 48
 Cisco dCloud

Scenario 1. Configure In-room controls

Steps
1. Determine the IP address of the video system using either the Touch 10 or navigate to the upper left corner of the home
screen using the remote control and press OK. Then navigate to Settings and press OK.

2. Using a web browser, connect to the web interface of the video system.

3. Sign in to the video system's web interface with the administrator credentials. The default credentials are admin and a blank
password.

4. Using the menus navigate to Security > Users and then click Add new user….

5. Enter the username RoomControl, leave only the RoomControl role ticked, untick Require passphrase change on next
user sign in and enter the passphrase cisco.

6. Click Create user to create the new user account.

NOTE: A user with the RoomControl role can create in-room controls. The user has access to the In-room control editor and
corresponding development tools.

7. Signout of the video system by clicking the user icon in the top right and side and click Signout

8. Sign in using the newly created RoomControl account with the password cisco.

NOTE: The login is case sensitive. If you are unable to sign in, make sure the login is spelled exactly as RoomControl

9. Notice that now all options are removed from the web interface bar, only Integration remains. Click Launch Editor. If a panel
is shown with buttons configured delete the panel using the trashcan icon in the bottom right corner. Repeat this for any other
configured panels (the Create icons shown in Figure 40. will read Edit wherever a panel has already been created) and then
click Export > To codec in order to remove the configuration.

NOTE: You can launch the editor from the video system’s web interface. If an in-room control panel already has been created on
the Touch 10, this will automatically load into the editor, ready to act as a starting point for your design. When you push a new
panel to the video system, you will immediately see the result on the Touch 10.

This lab uses the editor connected to the video system, there are two places you can download an offline editor from:

• Download from http://www.cisco.com/go/in-room-control-docs

• Or, sign in to a video system’s web interface with administrator credentials, navigate to Integration > In-Room Control, and click
Download Editor.

If you choose to download the offline editor, extract the files from the downloaded zip-file. Retain the folder structure.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 35 of 48
 Cisco dCloud

Figure 41. In-room control editor workflows when launched from the video system’s web interface

10. Click Create under Homescreen (Figure 41. ) to create a blank in-room control panel in the editor. This panel will be
accessible from the bottom of the Touch 10 when not in a call (see Figure 39. ).

Figure 42. In-room control editor overview

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 36 of 48
 Cisco dCloud

11. Familiarize yourself with the options available in the editor, it is a drag and drop interface.

NOTE: What you see in the editor's design panel is similar to how the in-room control panel will appear on the Touch 10 (see
Figure 42. ).

An in-room control panel is arranged in pages. Each page consists of one or more rows, which you can populate with text and user
interface elements known as widgets.

Widgets are arranged in a four-column grid. The widgets are placed into the grid according to the following rules:

• A widget fills between one and four columns depending on its size.

• Rows are right-aligned.

• If you add more widgets than fits in one line, widgets wrap to a new line within the same row.

How you use the user interface elements for your meeting room is up to you. You can, for example, create panels with preset
buttons for lights and blinds, or support for more complex scenarios such as controls for many microphones in a large meeting
room.

Figure 43. Editor panel overview

12. Configure the panel as shown in Table 6.

Table 7. Homescreen panel initial configuration

Setting Label

Panel name Lights & Blinds

Page name Lights & Blinds

Row name Lights

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 37 of 48
 Cisco dCloud

13. Drag and drop a Slider widget into the newly named Lights row.

14. Click on the slider to highlight the widget and configure its Widget ID as lights_slider.

15. The panel should now be configured as shown in the figure below.

Figure 44. Lights & Blinds panel initial configuration

16. Save the configured panel to the codec by clicking Export > To codec.

17. Your Touch 10 should now show a new icon. (It will be a light bulb if you did not click anything else in the initial panel
configuration).

18. Open a terminal and log in to the codec using SSH and the same RoomControl credentials as used earlier. Enter the
command xfeedback register event/UserInterface/Extensions/Event.

NOTE: If the RoomControl credentials do not work please use the admin credentials.

NOTE: If you do not have a SSH terminal client like Putty on your laptop, then RDP to 198.18.133.36 as cholland/C1sco12345 and
launch Putty from the desktop. Then, using Putty, SSH to the IP address of the SX.

NOTE: The Feedback commands are used to specify what parts of the configuration and status hierarchies to monitor. Feedback
is only issued on the RS-232, Telnet or SSH session for which it is specified. If you are connecting to the codec with multiple
sessions, you have to define feedback individually for each session.

In-room control events are available in two versions from the terminal.

• UserInterface Extensions Event - suited for terminal output mode

• UserInterface Extensions Widget - suited for XML output mode

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 38 of 48
 Cisco dCloud

19. On your Touch 10 click the button at the bottom right of the screen, then adjust the slider bar on the panel. On your terminal
window you will see the events output and the “lights_slider” value change as the slider is moved.

20. Using the web browser open a new tab and login as an admin, navigate back to Integration > In Room Control >
Development Tools a new session showing a log will appear. Adjust the slider on the Touch 10 again and observe the
changes taking place on the log. This can be a helpful tool to use rather than having to create a terminal session for testing
purposes.

21. Repeat steps 8-11, adding the following widgets from the General tab:

Table 8. Widget Table

Row label Widget 1 Type – Widget ID Widget 2 Type – Widget ID

Lights (already configured) Slider – lights_slider (already configured) On / off – lights_toggle

Projector On / off – projector_power N/A

Blinds Presets 3 Options – blinds_preset N/A

Option names: Open, 50/50, Closed
Group IDs: 0, 50, 100

Blinds Manual Up / down - blinds N/A

22. The final configuration should be identical the figure below.

Figure 45. Lights & Blinds panel final configuration

23. Save the configured panel to the codec by clicking Export > To codec.

24. Start a new web browser session and log onto the codec this time with the admin credentials.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 39 of 48
 Cisco dCloud

25. Navigate to Integration > In-Room Control and click Launch Editor.

26. In the bottom left of the screen there is a Cisco logo, double click the logo and a new menu option called Labs appears, see
Figure 45.

Figure 46. Labs menu item

27. Click Labs > Room to open a hidden simulator. Use the newly configured buttons on the Touch 10 to adjust the lights, blinds
and projector and observe the changes reflected in the simulator, terminal and developer tool log.

28. In the simulator click the three lines icon in the top left corner to open a menu. Click Load config and then OK. Your Touch
10 now has a new panel called Room on the homescreen panel next to Lights & Blinds and there is a new global panel in
the top right hand corner with a thermometer icon. View both panels to give you an idea of what other things are possible with
in-room controls.

29. Return to the in-room control editor and create a new In-Call panel. Add your own controls (you can also add Icons (available
in the top right corner next to the General widgets)).

30. Make a call and observe that the new panel appears on the Touch 10.

31. Design some controls you think could be useful for customers, for instance you could create a controller for a video playback
device such as an Apple TV or Blu-ray player, control a document camera, control complex microphone areas with zoned
audio, etc. Think about where these panels would be best suited, should they be in-call only or only out of call and what icon
would be best for that panel.

This concludes this scenario, section, as well as the lab.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 40 of 48
 Cisco dCloud

Appendices
Contained within is Bonus material as well as instructions on converting CE-on-DX to Android.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 41 of 48
 Cisco dCloud

Appendix A. Bonus Material (optional) for CE-on-DX

Content in Appendix A is considered Bonus material and may be completed at the end of the Endpoints lab.

Backup and Restore the DX

1. On the DX, create a backup.

2. On the DX in the web-UI go to Maintenance > Backup and Restore.

3. Click take Backup.

4. Save this to your laptop.

5. Using the Web-UI, factory reset the DX. Wait for the DX to reboot.

6. After reboot, on the DX Web-UI, restore the backup. After you see applied successfully, you may need to reboot the device
using maintenance > restart if the device does not re-register to CUCM.

7. On the DX, return to the Web-UI and change the admin password to cisco.

Far End Camera Control (Requires an SX or MX device)

8. Determine the directory number of the SX.

9. On the CE-on-DX, place a call to the SX using the SX directory number.

10. Answer the call on the SX.

11. Touch the DX screen and on the top right of the screen on the DX, tap the roster icon as shown in the figure below.

Figure 47. CE-on-DX Roster icon

12. Choose the SX. You should now see a new fly-out menu with a camera icon allowing you to control the far end.

Figure 48. FECC controls

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 42 of 48
 Cisco dCloud

13. Use the controls to maneuver and zoom the SX camera on the far end.

Figure 49. Far End Cameral Control

This concludes this Appendix.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 43 of 48
 Cisco dCloud

Appendix B. Bonus Material (optional) for 88xx

Content in Appendix B is considered bonus material and may be completed at the end of the Endpoints lab.

On-Premise PRT Reporting

Initially this feature only worked over MRA. Now the feature works both on-premise or off-premise.

1. On the Unified CM Administration page navigate to Device > Device Settings > Common Phone Profile and click Find.

2. Click the Standard Common Phone Profile link.

3. Find (Ctrl+F) Customer support upload URL in the Product Specific Configuration Layout.

4. Enter http://198.18.133.37/prt_upload.php and check the Override box.

5. Reset the phone.

6. On the 8800 press the Applications button.

7. Choose Phone information.

8. Press the softkey button for Report problem.

9. Choose (3) Problem description.

10. Choose a problem description from the list by number or using the Navigation cluster button.

11. Press the softkey button for Select.

12. Press the softkey button for Submit.

13. The 8800 will now gather the logs and upload them to the Workstation 2 web server. You can view the logs in the PRT folder
on Workstation 2.

14. After a successful submission press the softkey button for OK.

15. Create an RDP connection to Workstation 2 (198.18.133.37).

16. Login with Username: dcloud\aperez and Password: C1sco12345.

17. On the Desktop, there is a folder called PRT. This is where the incoming problem reports will go. Open the PRT folder and
find the problem report.

Control Default Wallpaper

This feature allows you to administratively push wallpaper, such as a corporate logo, from Unified CM without any end user
interaction required to make the wallpaper the default. In addition, this feature locks the wallpaper in place so that the end user
cannot change it. This feature is available for the 8811/41/45/51/61/65. It was first introduced on the 7900 series running
9.3(1)SR4 or later; and the 8961 and 9900 series running 9.3(1) or later.

This feature requires no manipulation of the List.xml file. This significantly reduces the administrative complexity. The key
requirement for 8811/41/45/51/61/65 is that the background image be exactly 800x480 to match the physical screen dimensions of
the 8800 phone. The 8961/9900 by contrast uses 640x480.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 44 of 48
 Cisco dCloud

In this lab, we will push a background image called cisco1.png to the 8800 phone. The cisco1.png we have already created for you
and is located on the Workstation 1 desktop (198.18.1.36 user cholland/C1sco12345) in a folder called CST.

New Background Image

1. Return to the Unified CM administration session.

2. From the Navigation drop-down list box choose Cisco Unified OS Administration and click Go.

3. Login with Username: administrator and Password: dCloud123!.

4. Navigate to Software Upgrades > TFTP File Management.

5. Click Upload File.

6. Click Browse and choose the cisco1.png file from the Desktop.

7. For Directory, enter Desktops/800x480x24.

8. Click Upload File.

9. Click Close after the file uploads.

Restart the TFTP service

10. From the Navigation drop-down list box choose Cisco Unified Serviceability and click Go.

11. Login with Username: administrator and Password: dCloud123!.

12. Navigate to Tools > Control Center – Feature Services.

13. From the Server drop down list choose cucm1.dcloud.cisco.com—CUCM Voice/Video and click Go.

14. Choose the radio button next to Cisco Tftp.

15. Click Restart and then OK.

16. Wait for the page to refresh.

17. Change the Navigation drop-down list box to Cisco Unified CM Administration and click Go.

18. Navigate to Device > Device Settings > Common Phone Profile and click Find.

19. Click the Standard Common Phone Profile link.

20. Uncheck the box next to Enable End User Access to Phone Background Image Setting.

21. Find (Ctrl+F) the setting Background Image.

22. Enter cisco1.png in the box and verify the Override check box is checked.

23. Click Save, Apply Config, OK. Reset, Reset, and then Close. The newly applied wallpaper should appear after the phone
registers. If it does not appear, navigate to the phone device page click the Reset button and then click Restart.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 45 of 48
 Cisco dCloud

Appendix C. CE-on-DX Factory Reset

In the following, you will learn how to factory reset the CE-on-DX.

1. On CE-on-DX click the icon on the top left of the screen to go into settings.

Figure 50. Access settings

2. Click Settings and then choose Reset system.

3. The device will reboot and be ready for the next lab.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 46 of 48
 Cisco dCloud

Appendix D. Converting CE back to Android

Complete the following to return the CE-on-DX to the Android operating system. Both files mentioned below are available on CCO.
Download both, or the latest versions available, and copy these files to a USB drive.

CAUTION: Only complete these steps if necessary. If your DX was already on CE please do not downgrade it to Android.

In the following, you will learn how to roll back the DX from CE to Android.

NOTE: There are two ways to roll back. The first is a CUCM-centric method. The second is uploading a *.pkg to the Web-UI on
CE. The second method is quick and easy and preferred for this lab.

Factory resetting the CE on DX requires a two step down grade as outlined in the following steps.

1. Determine the IP address of your DX.

2. Using your web browser, navigate to the Web-UI of the CE-on-DX.

3. Navigate to Maintenance > Software Upgrade.

4. Click Choose File. Browse to the USB drive and find s52040ce8_2_1.pkg. Install this software.

5. After step 4 is complete and the device has rebooted, navigate to Maintenance > Software Upgrade.

6. Click Choose File. Browse to the USB drive and find dx70.ce8.2.0-syn208.rel.pkg. Install this software *.pkg file to rollback
CE-on-DX to Android.

7. Wait for the system to convert from CE to Android

NOTE: In a production environment, you would need to delete the old “Cisco TelePresence DX” device-type in CUCM that
corresponds to the MAC address of your CE-on-DX or else the Android-based DX will not register.

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 47 of 48
 Cisco dCloud

© 2018 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 48 of 48