Skip to content
This repository has been archived by the owner on Aug 13, 2022. It is now read-only.

Commit

Permalink
added mentions for the DevNet Sandboxes
Browse files Browse the repository at this point in the history
  • Loading branch information
ObjectIsAdvantag committed Jun 7, 2018
1 parent af241b0 commit 8858a0c
Show file tree
Hide file tree
Showing 3 changed files with 8 additions and 4 deletions.
2 changes: 2 additions & 0 deletions labs/collab-xapi-branding/1.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,8 @@ In this lab, you’ll learn to add your own logo and custom message to a Cisco c
* Running _Cisco TelePresence CE v9.2_ or higher version of software
* Registered to the Cisco Webex cloud platform, or to an on-premise Cisco Unified Communications Manager (CUCM) or Cisco Video Control Server (VCS)

Alternatively, you can use one of the [RoomKit Sandboxes](https://github.com/CiscoDevNet/awesome-xapi#sandboxes) offered to DevNet community members.

* Admin credentials to your device, if it's on-premise registered. If cloud-registered, you'll need admin access to the [Control Hub](https://admin.webex.com/login) of the organization of your device

* Laptop with local or VPN IP connectivity to your device, and the following software tools, recommended:
Expand Down
2 changes: 1 addition & 1 deletion labs/collab-xapi-controls/1.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Finally, if your device supports JavaScript macros, you will deploy and test the
* To complete this lab, you will need a Cisco Collaboration device (typically a DX, SX, MX or Roomkit series) that supports software version CE9.2 or later.
>Note that the screenshots for this lab have been created with a DX80 running CE9.3
Alternatively, you can use one of the [RoomKit Sandboxes](https://devnetsandbox.cisco.com/RM/Diagram/Index/a01c15fc-af6e-497a-92ef-138e06cad308?diagramType=Topology) offered to DevNet community members.
Alternatively, you can use one of the [RoomKit Sandboxes](https://github.com/CiscoDevNet/awesome-xapi#sandboxes) offered to DevNet community members.

* **We recommend that you complete the [Introduction to xAPI](https://learninglabs.cisco.com/lab/collab-xapi-intro/step/1) learning lab, as we will assume you are familiar with your decice's admin interface and xAPI programming.**

Expand Down
8 changes: 5 additions & 3 deletions labs/collab-xapi-intro/1.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,8 @@ To make it concrete, we’ll illustrate xAPI and CE customization by showing how
- Running the _Cisco Collaboration Endpoint CE v9.2+_ version of software
- Registered to the Cisco Webex cloud platform, or to an on-premises Cisco Unified Communications Manager (CUCM) or Cisco Video Control Server (VCS)

Alternatively, you can use one of the [RoomKit Sandboxes](https://github.com/CiscoDevNet/awesome-xapi#sandboxes) offered to DevNet community members.

* Admin credentials to your device, if it's on-premise registered. If cloud-registered, you need admin access to the [Control Hub](https://admin.webex.com/login) of the organization of your device

* Laptop with local or VPN IP connectivity to your device, and the following software tools, recommended:
Expand All @@ -41,7 +43,7 @@ The exact set of customization and API features and supported devices vary depen

### In-Room Controls and Macros

Back in January 2017, CE9 introduced customizable **in-room controls**. In-room controls let you add custom user interface elements to the Touch10 display used to control Room devices (as well as the on-screen control interface of the DX Series.) Such user interface extensions can control in-room lighting, blinds, video switches, or other peripherals. These user interface extensions can be bi-directionally integrated with additional external control systems (e.g. AMX/Crestron) via xAPI.
Back in January 2017, CE9.2 introduced customizable **in-room controls**. In-room controls let you add custom user interface elements to the Touch10 display used to control Room devices (as well as the on-screen control interface of the DX Series.) Such user interface extensions can control in-room lighting, blinds, video switches, or other peripherals. These user interface extensions can be bi-directionally integrated with additional external control systems (e.g. AMX/Crestron) via xAPI.

In November 2017, CE9.2.1 took the customization possibilities further, with the introduction of **branding** and **halfwake** display features, while also introducing a powerful **macro** engine. Macros provide a JavaScript run-time environment on board the Collaboration device itself, where code that can automate or change parts of the video endpoint behavior can run - avoiding the need to deploy a separate application server. Since both the device itself and any connected peripherals can be controlled from the Touch10 or DX series user interface, users get a consistent experience throughout the meeting room.

Expand All @@ -65,7 +67,7 @@ For more details about installation, configuration and extensibility via xAPI, r
Note that these guides primarily apply to on-premise registered devices - only a subset of the features described in these guides is available for cloud-registered devices. We’ll cover some of these differences in the next sections. For now, note that you’ll find additional documentation for cloud-registered devices at [Collaboration Help](https://collaborationhelp.cisco.com/article/en-us/jkhs20).


## Find Your Room Device's API Guide
## Find your device's API Documentation

Let’s now get a full description of the available access methods and how to use the xAPI for your device:

Expand All @@ -77,4 +79,4 @@ Let’s now get a full description of the available access methods and how to us

3. Look for the _About the API_ entry in the table of contents, and click it.

Congrats, you've discovered your device's xAPI documentation!
Congrats, you've accessed the documentation for your device's version of the xAPI!

0 comments on commit 8858a0c

Please sign in to comment.