Cisco Extended Care 1.0 Application
Server Installation and Administration
Guide
Software Release 1.0
November 18, 2013
Cisco Systems, Inc.
www.cisco.com
Cisco has more than 200 offices worldwide.
Addresses, phone numbers, and fax numbers
are listed on the Cisco website at
www.cisco.com/go/offices.
Text Part Number: OL-30302-01
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this
URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display
output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in
illustrative content is unintentional and coincidental.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
© 2013 Cisco Systems, Inc. All rights reserved.
C O N T E N T S
C O N T E N T S
CHAPTER
1
Introduction
1-1
Intended Audience
Overview
1-1
1-1
Not Intended for Use In Emergency or for Patient Monitoring
What is Included in this Document
1-2
Cisco Extended Care Software Components 1-2
Cisco Extended Care Application Server Components
Video Endpoints 1-2
System Requirements 1-3
For Physical Installation 1-3
For VM Installation 1-3
Getting Started 1-3
Before You Begin Installation
Using This Manual 1-4
CHAPTER
2
1-2
1-2
1-3
Installing Software for the Cisco Extended Care Application Server
Installing Cisco Extended Care Software 2-1
Verifying Installation 2-2
Setting up Network Time Protocol (NTP) 2-2
Updating the Time Zone on the Application Server
Configuring the Cisco Extended Care Proxy Server
2-1
2-3
2-3
Adding and Configuring the Connector 2-5
Adding the Connector 2-5
Configuring the Connector 2-7
Working with List Workflows 2-8
Adding an IFramePortlet 2-11
Enabling Ports for the HL7 Listener 2-13
Configuring Tenants 2-14
Configuring Text Messages in Login and Quick Connect Dialogs
Login Dialog Text Messages 2-16
Quick Connect Portal Text Messages 2-17
2-16
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
iii
Contents
CHAPTER
Configuring the Cisco Application Server
3
3-1
Logging in to the Cisco Extended Care Administration Server
Uploading Cisco Extended Care License Files
Configuring System Parameters
Configuring Regions
3-4
3-6
Configuring UC Server Groups
3-7
3-8
Configuring Meeting Resources
APPENDIX
A
Configuring Authentication
3-13
Configuring Security Policy
3-13
Configuring Splash Images
3-15
Assorted Tasks
3-2
3-4
Configuring UC Servers
Configuring Endpoints
3-1
3-11
A-1
Values to be Gathered Before Installation
Troubleshooting A-2
Incorrect Number of Licenses Displayed
APPENDIX
B
Additional Resources
APPENDIX
C
Software Compatibility
Browser Compatibility
A-1
A-2
B-1
C-1
C-1
GLOSSARY
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
iv
OL-30302-01
CH A P T E R
1
Introduction
Revised: November 18, 2013, OL-30302-01
Intended Audience
This guide is intended for an experienced Information Technology (IT) professional familiar with Linux
who will be installing the Cisco Extended Care Application Server. Specifically, the installation person
should have at least one to two years of Linux administration experience covering the following:
•
Basic Unix/Linux system administration skills
•
Ability to execute basic file and directory operations
•
Experience installing, uninstalling, and upgrading software
•
Experience with network client configuration (IP address, NTP, and DNS)
•
Starting and stopping application services
•
User management
Overview
Cisco Extended Care is a personal health and wellness collaboration platform, enabling patient
engagement and care team interactions at any time and from anywhere.
The solution provides:
•
Enhanced and efficient care coordination
•
Secure messaging
•
Appointment calendar and scheduling
•
Ability to access questionnaires
•
Real time video collaboration
•
Anywhere access to care team consults
•
Personalized content sharing
•
Video platform to drive health and wellness awareness and education
•
Open APIs to enable third party applications and environments
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
1-1
Chapter 1
Introduction
Not Intended for Use In Emergency or for Patient Monitoring
Not Intended for Use In Emergency or for Patient Monitoring
Cisco Extended Care is not intended for use in emergency situations. In the event of an emergency, call
911 or your local emergency response system. Cisco Extended Care is not for use in situations involving
real-time patient monitoring or alarming.
What is Included in this Document
The Cisco Extended Care 1.0 Application Server Installation and Administration Guide outlines the
steps and best practices for installing and configuring the Cisco Extended Care Application Server.
Cisco Extended Care Software Components
Cisco Extended Care software integrates several different software components.
Cisco Extended Care Application Server Components
The Cisco Extended Care Application Server is the data center software that manages all of the
connectivity provides various services to the end users. It is functionally comprised of the following:
•
Cisco Extended Care Application Server -This server ties together all the components of Cisco
Extended Care. Specifically, the Cisco Extended Care Application Server:
– maintains the master information about resources and manages the resources
– manages sessions and appointments
– implements patient and provider workflows
– manages the Cisco Extended Care Administrative Server, the Cisco Extended Care Portal, and
the Unified Communications (UC) servers
– interfaces with applications supporting Cisco Extended Care connectors.
•
Cisco Extended Care Provider Portal - This Portal maintains the provider login sessions, provides
the UI to the providers and interfaces to the Application Server to validate sessions.
•
Cisco Extended Care Patient Portal - This Portal maintains the patient login sessions, provides the
UI to the patients and interfaces to the Application Server to validate sessions.
•
Cisco Extended Care Administration Server- This management server is used to configure,
administer and manage the Application Server and the Portal Cisco Extended Care.
Video Endpoints
Cisco Extended Care facilitates video conferencing with the following video endpoints:
•
Cisco Desktop Collaboration Experience DX650
•
Cisco Telepresence SX20
•
Cisco Jabber Video for Telepresence (Movi)
•
Cisco Telepresence EX60/90
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
1-2
OL-30302-01
Chapter 1
Introduction
Getting Started
•
C20/C40/C60
•
Cisco Telepresence System 500
•
Cisco Telepresence System Edge 95 MXP
•
Cisco Telepresence MX200
•
Cisco IP Video Phone E20
•
Cisco Jabber for iPad
•
Cisco Jabber SDK
System Requirements
Cisco Extended Care Application Server runs on the following platform:
For Physical Installation
Processor: Two (2) multi-threaded four (4) core 2.4GHz CPUs with 12MB cache
Memory: 16 GB
Hard Disk: 500 GB HDD @ 7200
Network Interface Card: Quad Port 10/100/1Gb NIC
Optical Drive DVD±R
RAID support optional
For VM Installation
These requirements are per virtual machine instance:
Virtual Machine Version 7 or 8
Guest OS: RHEL 5 64 Bit
Virtual Processor
Number of Virtual Sockets: 2
Number of cores per virtual Socket: 2
Memory: 16 GB
Hard Disk: 100 GB
Getting Started
Before You Begin Installation
For proper operation of the Cisco Extended Care Application Server, do the following before performing
Cisco Extended Care Application Server software installation and configuration procedures.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
1-3
Chapter 1
Introduction
Getting Started
Step 1
Acquire the following values needed for installation:
•
The Fully Qualified Domain Name (FQDN) (for example, hostname.subdomain.domain.tld) of
every server and endpoint in the installation
•
IP Address of the Cisco Extended Care Application Server
•
Server Subnet Mask
•
Server Gateway Address
•
Domain Name System (DNS) Server 1 Address
•
DNS Server 2 Address
•
Domain Suffix
•
Network Time Protocol (NTP) Server 1 and Server 2 addresses local to the network
Step 2
Acquire the appropriate licences for your installation:
Step 3
Install and configure the applicable call management software. Configure the video endpoints. Refer to
Appendix B, “Additional Resources”, for information about how to install and configure these
components.
Using This Manual
There are two tasks described in this document: installation and administration.
– To install the Cisco Extended Care Application Server, proceed to Chapter 2, “Installing Cisco
Extended Care Software”.
– After the software is installed, proceed to Chapter 3, “Configuring the Cisco Application
Server”.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
1-4
OL-30302-01
CH A P T E R
2
Installing Software for the Cisco Extended Care
Application Server
Revised: November 18, 2013, OL-30302-01
Note
Refer to your server vendor’s documentation for remote management configuration.
Note
The Jabber SDK does not support CTMS 1.8 as an MCU.
Installing Cisco Extended Care Software
This section describes installing the Cisco Extended Care Application Server Software and the Cisco
Extended Care Proxy Server Software on a server or virtual machine.
Note
Step 1
This same install process is used for both the Cisco Extended Care Application Server and the Cisco
Extended Care Proxy Server. So use the following steps to install the Application Server and then repeat
them for the Proxy Server.
Boot up the server (or the virtual machine) using the appropriate disc.
As the server or virtual machine boots, you will see the following prompts:
Step 2
Click Edit in the Network Devices window.
Step 3
Check the Enable IPv4 Support check box.
Step 4
Check the Manual configuration or the DHCP radio button, depending on your infrastructure.
If selecting manual configuration, the DHCP server must provide a fixed IP address.
Step 5
Enter the IP Address and Prefix (Netmask) of the server.
Step 6
Uncheck the Enable IPv6 Support check box. (IPv6 is currently not supported.)
Step 7
Click OK.
Step 8
Enter the Hostname of the server.
Step 9
Enter the IP addresses of the Gateway, Primary DNS, and, optionally, the Secondary DNS.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
2-1
Chapter 2
Installing Software for the Cisco Extended Care Application Server
Installing Cisco Extended Care Software
Step 10
Click Next.
Step 11
Choose the applicable time zone for the server from the drop-down menu.
Step 12
Check the System Clock Uses UTC box and click Next.
Step 13
Enter the Root password for the server. (Record this root password in the Network Implementation Plan
[NIP].)
Step 14
Click Next. The installation process starts and takes several minutes to complete. Continue to Verifying
Installation.
Verifying Installation
Step 1
After the server boots up, verify that you can log into the server as a root user via ssh.
Step 2
Verify that the services are running using the following command
# service cec status
The command output for the Cisco Extended Care Application Server should be:
Apache is running.
Tomcat is running.
MySQL is running.
The command output for the Cisco Extended Care Proxy Server should be:
Proxy is running.
Step 3
Continue to Setting up Network Time Protocol (NTP), page 2-2.
Setting up Network Time Protocol (NTP)
Note
All UC related servers and the EC Application Server must be NTP synchronized. For example, if you
are using VCS and MCU with the EC Application Server, they must both be NTP synchronized.
To set up NTP, do the following:
Step 1
Use the following command to add one or more NTP servers (as described in the Network
Implementation Plan) that this server will use for synchronizing time:
addntp.sh [ip_addr_ntp_server1] (this is the IP address or host name of the first server)
Step 2
After about 15-20 minutes, verify that this server is synchronizing time with at least one NTP server
using the following command statntp.sh
The output will be similar to the following (there will be one line printed for every server):
Primary Source
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
2-2
OL-30302-01
Chapter 2
Installing Software for the Cisco Extended Care Application Server
Configuring the Cisco Extended Care Proxy Server
--------------17.151.16.20
Secondary Source(s)
----------------Discarded Source(s)
Note
Step 3
It takes about 15-20 minutes to synchronize time with a newly added NTP source.
Run the following command to verify that the date and time are correct:
date
Warning
This step is absolutely vital to ensuring that the server works correctly with the endpoints.The date,
time, and time zone should be reasonable.
Updating the Time Zone on the Application Server
If you need to update the time zone on your server follow these steps:
1.
SSH as root to the Application Server.
2.
Use vi to edit the /etc/sysconfig/clock file.
3.
Update the time zone in the file and save it.
4.
Export the tz variable. For example: export TZ=PDT, export TZ=EST, and so on. For a list of
time zones, see http://www.timeanddate.com/library/abbreviations/timezones/.
Configuring the Cisco Extended Care Proxy Server
After the Cisco Extended Care Proxy Server is installed as described in Installing Cisco Extended Care
Software, page 2-1 and NTP has been set, there are a few configuration steps required to configure the
private and global IP addresses. You will configure both the Cisco Extended Care Application Server
and the Cisco Extended Care Proxy Server.
Warning
It is critical that these parameters are entered correctly. Otherwise, the installation will not work.
Step 1
Log into the Cisco Extended Care Proxy Server.
Step 2
Enter the following command on Cisco Extended Care Proxy Server:
service cec status
You will see the following:
Proxy is running
Step 3
Enter the following command on Cisco Extended Care Proxy Server:
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
2-3
Chapter 2
Installing Software for the Cisco Extended Care Application Server
Configuring the Cisco Extended Care Proxy Server
/opt/lampp/bin/setup_proxy.sh [Extended Care Application Server-ip-address]
In Figure 2-1, the server ip address is 10.89.174.188.
Step 4
You will see the following:
+--------------------------------------+
| Cisco Extended Care Proxy Setup |
+--------------------------------------+
You are setting up Cisco Extended Care Proxy v1.0.X.XX.
Shutting down Cisco Extended Care Proxy service......................done.
Setting up Cisco Extended Care Proxy parameters......................done.
Starting Cisco Extended Care Proxy service...........................done.
Cisco Extended Care v1.0.X.XX has been setup.
Step 5
Log into the Cisco Extended Care Application Server.
Step 6
Enter the following command on Cisco Extended Care Application Server:
/opt/lampp/bin/setup_proxy.sh -1 [private-proxy-ip-address] -e [public-proxy-ip-address]
In Figure 2-1, the private proxy ip address is 10.89.174.174. (It is the proxy server address facing
the data center.) The public proxy ip address is 10.20.20.10. (It is the proxy server address facing
the public network.)
Step 7
You will see the following:
+--------------------------------------+
| Cisco Extended Care Proxy Setup |
+--------------------------------------+
You are setting up Cisco Extended Care Proxy v1.0.X.XX.
Shutting down Cisco Extended Care Tomcat service......................done.
Setting up Cisco Extended Care Proxy parameters......................done.
Starting Cisco Extended Care Tomcat service...........................done.
Cisco Extended Care Proxy v1.0.X.XX has been setup.
Step 8
Enter the following command on Cisco Extended Care Application Server:
service cecadmin status
You will see the following:
Apache is running
Tomcat is running
MySQL is running
Step 9
The Proxy server configuration is complete.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
2-4
OL-30302-01
Chapter 2
Installing Software for the Cisco Extended Care Application Server
Adding and Configuring the Connector
Adding and Configuring the Connector
Adding the Connector
Step 1
Open a browser window and enter https://[IP_address_application_server]/admin/.
Step 2
Log in using the default login values.
•
Username = sysadmin
•
Password = cisco123
Figure 2-1
Server Admin Login Screen.
When you login, the following screen appears:
Figure 2-2
Server Admin Screen.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
2-5
Chapter 2
Installing Software for the Cisco Extended Care Application Server
Adding and Configuring the Connector
Step 3
Browse to Integration > Connector. The following screen displays:
Figure 2-3
Connector Screen.
Step 4
Click Add.
Step 5
Enter the fields and select the actions as seen in the figure below (name the Connector Id as desired; in
this example the document will be using HL7 as it assumes the use of an HL7 Connector) and click Save.
Figure 2-4
Add Connector Screen.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
2-6
OL-30302-01
Chapter 2
Installing Software for the Cisco Extended Care Application Server
Adding and Configuring the Connector
Configuring the Connector
Step 1
Open a browser window and enter https://[IP_address_application_server]/hl7-connector/. The
following login screen displays:
Figure 2-5
Step 2
HL7 Connector Administration Screen
Log in using the default login values.
•
Username = sysadmin
•
Password = cisco123
Use the first section in the screen to configure authentication parameters used to communicate with
the Server. Use the second section to modify the list of HL7 specific configurations that will be
updated for each deployment environment.
Step 3
Set the Add On URL and Add On password values in the Parameters fields.
Step 4
Set the relevant values in the Connector Parameters fields to match the values used to add the connector
previously. For remaining fields in the Connector Manager Parameters and HL7 Manager Parameters
sections, use the values seen in the following figure:
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
2-7
Chapter 2
Installing Software for the Cisco Extended Care Application Server
Adding and Configuring the Connector
Figure 2-6
Step 5
HL7 Connector Parameters
When done, click Save.
Working with List Workflows
The second page in the Connector Administration UI is the workflows screen. This screen can be used
to enable or disable workflows as well as to update request/response templates.
To access it, click List Workflows. The following screen will appear:
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
2-8
OL-30302-01
Chapter 2
Installing Software for the Cisco Extended Care Application Server
Adding and Configuring the Connector
Figure 2-7
List Workflows Screen.
You can view the request and response templates by clicking on the corresponding links in the Request
Template and Response Transformer columns. Clicking on them will open a new browser page. The
template contents will appear similar to that seen following:
Figure 2-8
Template Content Example
The Response Transformer XML files will appear similar to that seen following:
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
2-9
Chapter 2
Installing Software for the Cisco Extended Care Application Server
Adding and Configuring the Connector
Figure 2-9
Response Transformer XML File Content Example
You can then choose to save the template or XML file by right clicking on the page and selecting Save
As.
To update Workflows, click on one of the workflows. A screen will display similar to the following:
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
2-10
OL-30302-01
Chapter 2
Installing Software for the Cisco Extended Care Application Server
Adding and Configuring the Connector
Figure 2-10
Update Workflow Screen
Use this screen to update the reqest/response templates, enable/disable the workflow, or use it to
add/update validation xml files for the request/response messages.
Adding an IFramePortlet
Step 1
Open a browser window and enter https://[IP_address_application_server]/admin/ and log in.
Step 2
Browse to Integration > Connector and verify that the Connector is shown as registered in the status
column.
Step 3
Browse to Integration > IFramePortlet. And enter an IFramePortlet ID and title. These can be anything
you wish.
Figure 2-11
Add IFramePortlet Screen before uploading description file
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
2-11
Chapter 2
Installing Software for the Cisco Extended Care Application Server
Adding and Configuring the Connector
Step 4
Upload the following IFramePortlet Description file (this is an XML file named as you wish):
<IFramePortletDescription>
<PortletDescription>
<Description>Default</Description>
<ExternalOnly>false</ExternalOnly>
<EmrLookUpOnly>false</EmrLookUpOnly>
<Disclaimer>Default</Disclaimer>
<Urls>
<Url>
<Type>patientMain</Type>
<FullScreenLink>true</FullScreenLink>
<Parameters>
<Parameter>
<Name>token</Name>
<Value>userAuthToken</Value>
</Parameter>
</Parameters>
</Url>
<Url>
<Type>logout</Type>
</Url>
</Urls>
</PortletDescription>
</IFramePortletDescription>
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
2-12
OL-30302-01
Chapter 2
Installing Software for the Cisco Extended Care Application Server
Adding and Configuring the Connector
Figure 2-12
Step 5
Add IFramePortlet Screen after uploading description file
Check the Enable box, set the Position to 2, set the Patient Main URL and Logout URL values (as
obtained from the Network Installation Plan or as otherwise applicable to your installation), and click
Save.
Enabling Ports for the HL7 Listener
To enable a port for the HL7 listener, doit from within the java code (HL7 connector admin) by invoking
a shell command (using ProcessBuilder) when the async mode is selected. This must be done only when
the connector manager url is localhost because the connector could be installed on a remote system.
Use the following command to enble a port for the HL7 listener:
# iptables -I INPUT 5 -p <protocol> --dport <port> -j ACCEPT
where protocol = 'tcp' (assuming mllp is being used) or any other layer 3 protocol that is being used
and port = 8881 or other custom port that needs to be opened
Please note that the '5' above indicates that this rule is to be inserted in a specific place in the firewall
because of the way Extended Care firewall rules are created (from most specific to least specific).
Also note the following when configuring the HCOS firewall with respect to the HL7 listener:
•
When enabling dual port MLLP in HL7 Connector, the HCOS firewall should allow connections to
the listening port.
•
When disabling dual port MLLP in HL7 Connector, HCOS firewall should restrict connections to
the listening port.
•
When updating port value, HCOS firewall should restrict connection to the earlier port and allow
connections to the new port.
•
By default, all unused ports will be disabled.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
2-13
Chapter 2
Installing Software for the Cisco Extended Care Application Server
Adding and Configuring the Connector
Configuring Tenants
Step 1
Browse to Configuration > Tenant and set the parameters as seen in the following figures. For Tenant
ID , Business Name, and Description, use the values from the Network Implementation Plan or as
applicable for your installation.For the Locale menu, select the date and time format according to your
location’s conventions.
Figure 2-13
Tenant Screen; Basic.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
2-14
OL-30302-01
Chapter 2
Installing Software for the Cisco Extended Care Application Server
Adding and Configuring the Connector
Figure 2-14
Tenant Screen; Locale.
Figure 2-15
Tenant Screen; Extended Care.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
2-15
Chapter 2
Installing Software for the Cisco Extended Care Application Server
Adding and Configuring the Connector
Figure 2-16
Step 2
Tenant Screen; SMTP.
Click Save.
Configuring Text Messages in Login and Quick Connect Dialogs
The Login page and Quick Connect portal both have default informational text that can be modified for
your particular installation. The files that need to be modified use the 'key=value' format.
Login Dialog Text Messages
There are two lines of text in the login page that read "Forgot your password?" and "Please call support
provider" by default. These sentences can be changed to have custom information for your users. For
example, it could have a support phone number. To configure the text messages.
Step 1
Open the following file for editing:
"/opt/lampp/tomcat/webapps/j2-admin/WEB-INF/classes/org/apache/jetspeed/portlets/security/res
ources/LoginResources_en.properties."
Step 2
Change the text values (contents after the '=' symbol) against the following keys:
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
2-16
OL-30302-01
Chapter 2
Installing Software for the Cisco Extended Care Application Server
Adding and Configuring the Connector
•
Key for "Forgot your password?" text - login.label.ForgotPassword
•
Key for "Please call support provider" text - login.label.Call
Step 3
Save the file and close.
Step 4
Changes to this file will take effect and will be seen by the patient only after a service restart. To restart
the service, use the following command:
service cec restart
Quick Connect Portal Text Messages
There are three lines of text in the Quick Connect portlet that read "If this is an emergency, hang up and
call the local emergency number," "Hours of Operations," and "(Configure hours of operation. Example
Mon-Fri 9a-5p CST)" by default.
These lines of text can be configured to provide, the local emergency number (for example, 911) as well
as the time of operation (for example, 9.00 a.m to 5.00 p.m).
Step 1
Open the following file for editing:
"/opt/lampp/tomcat/webapps/cisco-*-patient-portlets/WEB-INF/classes/messages.properties"
Step 2
Change the text values against the following keys:
•
Key for "If this is an emergency, hang up and call the local emergency number" text emergencyMessage
•
Key for "Hours of Operations" text - hoursOfOperationName
•
Key for ""(Configure hours of operation. Example Mon-Fri 9a-5p CST)" text hoursOfOperationsValue
Step 3
Save the file and close.
Step 4
Changes to this file will take effect and will be seen by the patient only after a service restart. To restart
the service, use the following command:
service cec restart
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
2-17
Chapter 2
Installing Software for the Cisco Extended Care Application Server
Adding and Configuring the Connector
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
2-18
OL-30302-01
CH A P T E R
3
Configuring the Cisco Application Server
Revised: November 18, 2013, OL-30302-01
This chapter describes how to configure the Cisco Application Server, including configuring system
parameters, adding new Endpoint information, and configuring meeting resources.
Logging in to the Cisco Extended Care Administration Server
To log in to the Cisco Extended Care Admin Server, complete the following steps.
Step 1
Open a browser window and enter https://[IP_address_application_server]/admin/.
The Cisco Extended Care Admin Login window displays, as shown in Figure 3-1.
Figure 3-1
Cisco Extended Care Server Administration Login Window
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
3-1
Chapter 3
Configuring the Cisco Application Server
Uploading Cisco Extended Care License Files
Step 2
Log in using the default login values.
•
Username = sysadmin
•
Password = cisco123
The Cisco Extended Care Admin Home screen displays. The drop-down menu under Configuration,
shown in Figure 3-2, lists all the configuration possibilities for this server. (You can optionally change
the password at any time. If you change the password, record the new password in the Network
Implementation Plan.)
Figure 3-2
Cisco Extended Care Server Admin Home Screen
Note
For any of the configuration windows, if you modify existing parameters and want to back out to what
was previously specified, do NOT click Save. Instead, click any item in any drop down menu across the
top. The parameters you modified are cleared and the new window is displayed.
Uploading Cisco Extended Care License Files
The Cisco Extended Care system can include the license files listed here. Every license file that applies
to this installation should have already been copied to the computer you are working from.
•
Server – Locks the application to a specific hardware machine (MAC address).
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
3-2
OL-30302-01
Chapter 3
Configuring the Cisco Application Server
Uploading Cisco Extended Care License Files
•
Resource – Controls the maximum number of endpoints.
For each file, do the following to upload the file into Cisco Extended Care.
Step 1
Figure 3-3
Choose Upload License File from the Configuration drop down menu. The Upload License File window
displays, as shown in Figure 3-3.
Upload License Files
Step 2
Browse to the location where you copied the license file you want to upload. Select the file. Click
Upload.
Step 3
Repeat steps 1 and 2 for every license file.
To view license files that have already been uploaded, click on the license file name.
To view license details, click License Information from the Configuration drop down menu. The
License Information window displays, as shown in Figure 3-4.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
3-3
Chapter 3
Configuring the Cisco Application Server
Configuring System Parameters
Figure 3-4
License Details
Configuring System Parameters
These parameters should be left with their default values. Do not configure the system parameters unless
Cisco personnel direct you to do so.
Configuring Regions
By default, all endpoints managed by a single instance of Cisco Extended Care belong to the default
region. If you have multiple call control regions (separate UC resources) you can add regions. This
allows you to later add Endpoint Computers to the appropriate region corresponding to the desired UC
resource, as described in Configuring Endpoints, page 3-8.
To configure the regions for this Cisco Extended Care Server, complete the following steps:
Step 1
Figure 3-5
From the Configuration drop down menu, choose Regions. The Region window displays, as shown in
Figure 3-5.
Regions
Step 2
To add a Region, click Add. The Add Region window displays as shown in Figure 3-6.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
3-4
OL-30302-01
Chapter 3
Configuring the Cisco Application Server
Configuring Regions
Figure 3-6
Add Region Window
Step 3
Enter a Region Id that is unique for this instance of Cisco Extended Care. The region ID can contain only
letters, numbers, underscore (_) and dash (-).
Step 4
Enter a Region name. The name can use any characters.
Step 5
Click Save.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
3-5
Chapter 3
Configuring the Cisco Application Server
Configuring UC Servers
Configuring UC Servers
Cisco Extended Care supports three types of unified communications (UC) servers:
•
CUCM
•
VCS Control
•
VCS Expressway
Unified communications servers are required for video conferencing but the UC servers are not required
to be Cisco UC servers. To list the configured UC servers for this Cisco Extended Care Application
Server, choose UC Servers in the Configuration drop down menu. The UC Server window displays as
shown in Figure 3-7.
Figure 3-7
UC Server Window
To modify the configuration for a UC server, click on the UC Server Id.
To add a UC Server, click Add. The Add UC Server window displays as shown in Figure 3-8. Choose
the UC server model, clicking either CUCM, VCS Control, or VCS Expressway and enter the
appropriate values for all the fields. Note that the fields may vary depending on which server model you
choose. Click Save.
Figure 3-8
Add UC Server
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
3-6
OL-30302-01
Chapter 3
Configuring the Cisco Application Server
Configuring UC Server Groups
Configuring UC Server Groups
Cisco Extended Care allows you to configure UC Server Groups. These groups enable you to specify a
group of UC Servers that can be used by an endpoint to establish Telepresence conferences. To make a
telepresence call on behalf of an endpoint, the Cisco Extended Care Application Server will attempt to
reach any of the servers in the group.
Note
You cannot mix CUCM servers, TMS servers, and VCS servers in the same UC Server Group. Therefore,
create separate groups for CUCM servers, TMS servers, and VCS servers.
When creating UC Server Groups:
•
Configure all UC Servers before you configure UC Server Groups. You can add UC Servers to a UC
Server Group, but you cannot specify a UC Server Group when configuring a UC Server.
•
The default UC Server group is empty until you add servers to it. Therefore, during installation, you
must click on default in the list of UC Server Groups and select servers to add to the default group.
•
When endpoints are configured, they are associated with a UC Server Group. If no UC Server Group
is specified, the endpoint will use the default UC Server Group.
The UC Server Group window displays as shown in Figure 3-9.
Figure 3-9
UC Server Group Window
To modify the configuration for a UC server, click on the UC Server Group Id.
To add a UC Server, click Add. The Add UC Server Group window displays as shown in Figure 3-10.
Specify the UC server group ID, UC Server Group Description, and click on the check box of every UC
server you included in this group. Click Save.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
3-7
Chapter 3
Configuring the Cisco Application Server
Configuring Endpoints
Figure 3-10
Add UC Server Group
Configuring Endpoints
For the Application Server to manage video calls, you must configure the Telepresence attributes of the
video endpoint. To do this, complete the following steps.
Step 1
Figure 3-11
Choose Endpoints from the Configuration drop-down menu. The Cisco Extended Care Endpoints
Window displays, as shown in Figure 3-11.
Cisco Extended Care Endpoints Window
Step 2
Click the Add button. The Add Endpoint screen displays, as shown in Figure 3-12.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
3-8
OL-30302-01
Chapter 3
Configuring the Cisco Application Server
Configuring Endpoints
Figure 3-12
Add Endpoint Menu - Basic Configurations
Step 3
Step 4
Enter applicable information in the fields as specified in the Network Implementation Plan, Endpoints
tab.
a.
The Endpoint Id must be unique among all endpoints communicating within a tenant. It can include
any alphanumeric characters, underscores or dashes.
b.
The Endpoint Name (Location) will appear on the provider’s Ready Appointments window, so the
location name should be something meaningful and unique (such as Molina clinic or Mayo Cardiac
Telemedicine Room.) There are no restrictions on the characters of the Endpoint Location.
c.
Select the Endpoint Type. Choose from Patient, Provider, or API as needed.
d.
Specify the Region. The default region includes all the meeting resources configured to this Cisco
Extended Care Application Server.
e.
Select the OS Type. Choose from Windows, Mac, or iPhone/iPad as needed.
Click Unified Communications and enter the applicable information in the fields as specified in the
Network Implementation Plan, Endpoints tab.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
3-9
Chapter 3
Configuring the Cisco Application Server
Configuring Endpoints
Figure 3-13
Step 5
Add Endpoint Menu - Unified Communications
a.
Choose the video endpoint type from the list. The dropdown menu lists the compatible video
endpoints. If you specify Others, then the support defaults to Manual Dial.
b.
Manual Dial is for support only. Do not check this box unless you are supporting a problem or
instructed to do so by a Cisco representative. It can be modified during support and then set back to
its original setting.
c.
Check the Outside Enterprise box if this is a Provider endpoint outside of the enterprise network
and the Providers at this endpoint need the ability to receive video calls from an endpoint inside the
enterprise network.
d.
Enter the phone number for this video endpoint/codec.
e.
Enter the Video Endpoint Host Name, IP Address, Access ID, and Password.
f.
Specify the UC Server Group. The default is all the UC Servers configured for this Cisco Extended
Care Application Server. (The default UC Server Group should not contain both VCS and CUCM
servers.)
Click Save.
The system message “Successfully added Endpoint <Endpoint Id>” displays.
Step 6
Note
Repeat Steps 2-5for all required endpoints.
If you need to edit information for an existing endpoint, click on the Endpoint Id. If you need to delete
an endpoint, check the box to the left of the designated Endpoint ID in the Endpoints Window and click
Delete.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
3-10
OL-30302-01
Chapter 3
Configuring the Cisco Application Server
Configuring Meeting Resources
Configuring Meeting Resources
You will need to configure meeting resources only if you have a multi-tenant envirionment.To list the
configured meeting resouces, choose Meeting Resources from the Configuration dropdown menu. The
Meeting Resources window will appear similar to that shown in Figure 3-14.
Figure 3-14
Meeting Resources
Step 1
Figure 3-15
To add a Meeting Resource, click Add. The Add Meeting Resource window displays as shown in
Figure 3-15.
Adding Meeting Resources
Step 2
To add the meeting resources information, enter applicable information into the fields as listed in
Table 3-1.
Table 3-1
Meeting Resource Configuration
Parameter
Description
Bridge Type
Choose CTMS, MSE 8710, MSE 8510 or Codian
MCU.
Version
Indicate the version number of the bridge.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
3-11
Chapter 3
Configuring the Cisco Application Server
Configuring Meeting Resources
Step 3
Note
Parameter
Description
Meeting Resource Id
Access number configured in CTMS.
Region
If this enterprise uses regions, specify the region
for this meeting resource. Otherwise, leave it as
default.
Interop Enabled
If the Interoperability License is installed and this
bridge type will interoperate with another bridge
type, check this box. This box cannot be checked
if Codian MCU is chosen.
Peer Bridge Type
This is automatically filled in.
Peer Meeting Resource Id
Access number configured for the peer bridge.
Click Save.
To edit a meeting resource, click on its Meeting Resource Id. To delete a meeting resource, check the
box next to the Meeting Resource Id and then click Delete.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
3-12
OL-30302-01
Chapter 3
Configuring the Cisco Application Server
Configuring Authentication
Configuring Authentication
Cisco Extended Care users can be authenticated in several ways. Only Dedicated authentication is
supported with a customer install.
Dedicated means that the end users are authenticated against a directory dedicated to Cisco
Extended Care.
To configure the authentication to be used for Cisco Extended Care, complete the following steps:
Figure 3-16
Step 1
Choose Authentication from the Configuration drop down menu. The Authentication window displays,
as shown in Figure 3-16.
Step 2
Choose Dedicated.
Authentication
Step 3
Click Save.
Configuring Security Policy
To configure the security policy to be used by this enterprise, complete the following steps:
Step 1
From the Configuration drop-down menu, choose Security Policy. The Security Policy window
displays, as shown in Figure 3-17.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
3-13
Chapter 3
Configuring the Cisco Application Server
Configuring Security Policy
Figure 3-17
Security Policy
Step 2
Configure the policy as described below:
a.
Check Enabled if you want to force a password change on the first login.
b.
Check Enabled if you want to disable an account if the user does not log in for a certain number of
days. If enabled, specify the inactivity period. The inactivity days can range from 1 to 730.
c.
Check Enabled if you want passwords to expire after a certain number of days. If enabled, specify
the expiration period. The expiration days can range from 1 to 999.
d.
Check Enabled if you want to require strong passwords. If enabled, specify the minimum password
length and the minimum number of character types. The length of strong passwords can be between
1 and 15 characters with a minimum of character types ranging from 1 to 4.
e.
Check Enabled if you want to prevent password reuse. If enabled, specify the number of saved
passwords (a number between 1 and 20).
f.
The number of saved passwords can be between 1 and 20.
g.
Check Enabled if you want to lockout (that is, automatically log out) a user for PC inactivity during
a session. If enabled, specify the inactivity warning time and logout time.
– The Inactivity Warning is a warning message that appears on an EC PC after a specified number
of minutes of no activity (pressing enter, clicking a mouse key, etc.,) during a session. The time
between activity and when the inactivity warning message appears can be set from 1 to 999
minutes.
– The Logout time is the amount of time AFTER the Inactivity Warning before the end user is
logged off. It can be between 1 and 60 minutes.
Step 3
When complete, click Save.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
3-14
OL-30302-01
Chapter 3
Configuring the Cisco Application Server
Configuring Splash Images
Configuring Splash Images
Complete the following steps to configure the following splash images that appear in the Extended Care
UI. These can be of any image file type that a Web browser would support:
Step 1
Figure 3-18
Patient Portal Login Splash - This is the image that the patient sees when they login.
•
Patient Portal Home Splash - This is the image that the patient sees after logging in.
•
Patient Portal Header Splash - This is the image at the top of the page as it appears on all Patient
Portal windows.
From the Configuration drop-down menu, choose Extended Care Images. The Extended Care Images
window displays, as shown in Figure 3-18.
Extended Care Images
Step 2
Figure 3-19
•
Click Add.
Adding Extended Care Images
Step 3
Specify the Name, Image, Alternate Text and Type. Then click Save.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
3-15
Chapter 3
Configuring the Cisco Application Server
Configuring Splash Images
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
3-16
OL-30302-01
A P P E N D I X
A
Assorted Tasks
Revised: November 18, 2013, OL-30302-01
Values to be Gathered Before Installation
Table A-1 describes the information that must be gathered to complete the installation.
Table A-1
Information to Obtain Before Installation
Task
Value(s)
Obtain the following:
- Fully Qualified Domain Names
(FQDNs) for Cisco Extended Care
Application Server
- Domain Name System (DNS) Server 1
Address
- DNS Server 2 Address
- Domain Suffix
IP Addresses of Application Server
Server Subnet Mask
Server Gateway Address
Network Time Protocol (NTP) Server 1 and
Server 2 Addresses
Prescription header and footer, if applicable
(for E-Pen)
Applicable licenses for this installation
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
A-1
Appendix A
Assorted Tasks
Troubleshooting
Troubleshooting
Incorrect Number of Licenses Displayed
During very heavy loads, the Cisco Extended Care Admin Home screen may indicate a greater number
of end user licenses in use than is actually the case. To resolve this issue, you must restart the service
connecting the endpoints as follows:
Step 1
Open a command shell on the Application Server and logon as root.
Step 2
Type the command service cec restart and press Enter.
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
A-2
OL-30302-01
A P P E N D I X
B
Additional Resources
Revised: November 18, 2013, OL-30302-01
The Cisco Extended Care Application Server Installation and Administration Guide does not include
details on configuring unified communication and video components. Use the following tables, which
include links to supporting documentation, as guidelines for the configuration process.
a.
Refer to Table B-1 to install and configure CUCM, VCS, or TMS.
Table B-1
Installing and Configuring CUCM, VCS, or TMS
Job Aid
Document URL
Installing Cisco Unified Communications http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/in
Manager
stall/7_1_2/install/cmins712.html
Cisco TelePresence Video
Communication Server Getting Started
http://www.cisco.com/en/US/products/ps11337/prod_install
ation_guides_list.html
Cisco TelePresence Video
Communication Server configuration
guides
http://www.cisco.com/en/US/products/ps11337/products_in
stallation_and_configuration_guides_list.html
Cisco VCS Expressway Starter Pack
Deployment Guide
http://www.cisco.com/en/US/docs/telepresence/infrastructur
e/vcs/config_guide/Cisco_VCS_Expressway_Starter_Pack_
Deployment_Guide_X7-0.pdf
Basic Cisco VCS Configuration: Cisco
http://www.cisco.com/en/US/docs/telepresence/infrastructur
VCS Control with Cisco VCS Expressway e/vcs/config_guide/Cisco_VCS_Basic_Configuration_Cisco
X5.2
_VCS_Control_with_Cisco_VCS_Expressway_Deployment
_Guide_X5.pdf
Cisco TMS Provisioning Deployment
Guide
http://www.cisco.com/en/US/docs/telepresence/infrastruc
ture/tms/config_guide/Cisco_TMS_Provisioning_Deplo
yment_Guide_13-0.pdf
Cisco TelePresence Movi Administrator
Guide
http://www.cisco.com/en/US/docs/telepresence/endpoint/m
ovi/admin_guide/Movi_Administrator_Guide_4-2.pdf
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
B-1
Appendix B
b.
Additional Resources
Refer to Table B-2 to configure a TelePresence endpoint (such as CTS-500).
Table B-2
Configuring TelePresence Endpoints in CUCM
Step
Document URL
1.
Configure CUCM for TelePresence
endpoint.
http://www.cisco.com/en/US/partner/docs/telepresence/cu
cm_cts/cucm_cts_admin_book/guide/cucm_cts_admin_con
fig.html
2.
Create a Session Initiation Protocol
(SIP) trunk to integrate a
TelePresence endpoint and CUCM.
http://www.cisco.com/en/US/docs/telepresence/multipoint_
switch/1_6/admin/dh_cucm_6.html#wp1043391
3.
Create an application user in CUCM. http://www.cisco.com/en/US/docs/telepresence/cucm_cts/c
ucm_cts_admin_book/guide/cucm_cts_admin_inst.html#w
p1089052
Tip: Refer to this document to configure CUCM for all
TelePresence endpoints in the Cisco Extended Care
software.
4.
Configure CUCM for CTMS.
c.
Refer Table B-3 to configure the Cisco Unified IP Video Phone 7895G, if applicable.
Table B-3
http://www.cisco.com/en/US/docs/telepresence/multipoint_
switch/1_6/admin/dh_cucm_6.html
Configuring the Cisco Unified IP Video Phone 7895G
Job Aid
Document URL
CUCM Administration Guide (See
chapter “Cisco IP Phone
Configuration.”)
http://www.cisco.com/en/US/docs/voice_ip_comm
/cucm/admin/5_0_1/ccmcfg/bccm.pdf
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
B-2
OL-30302-01
A P P E N D I X
C
Software Compatibility
Revised: November 18, 2013, OL-30302-01
Browser Compatibility
The following table (continued on the next page) lists the browsers and their level of support in Cisco
Extended Care. Fully supported means the relevant components have been completely tested on these
browsers and are certified to work. Compatible means the relevant browser components have been
functionally tested on these browsers at a high level, but exhaustive testing has not been done.
Table C-1
Browser Compatibility by Operating System and User Type
Patient
Platform
Browser Name
Browser Version
Support Level
Windows 7
Internet Explorer
8
Fully Supported
Internet Explorer
9
Fully Supported
Chrome
26
Fully Supported
Firefox
23.0.1
Fully Supported
Internet Explorer
10
Fully Supported
Chrome
26
Fully Supported
Safari
6.03
Fully Supported
Chrome
26
Compatible
Safari
6.03
Fully Supported
Chrome
26
Not supported
Windows 8
Mac OS 10.8.4
iPad iOS 6.1.3
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
C-1
Appendix C
Software Compatibility
Browser Compatibility
Provider
Windows 7
Internet Explorer
8
Fully Supported
Internet Explorer
9
Fully Supported
Chrome
26
Fully Supported
Firefox
23.0.1
Fully Supported
Windows 8
Internet Explorer
10
Fully Supported
Mac OS 10.8.4
Safari
6.0.3
Fully Supported
iPad iOS 6.1.3
Safari
6.03
Fully Supported
Chrome
26
Not supported
Internet Explorer
8
Fully Supported
Internet Explorer
9
Fully Supported
Firefox
23.0.1
Fully Supported
Administrator
Windows 7
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
C-2
OL-30302-01
G L O S S A RY
Revised: November 18, 2013, OL-30302-01
B
Business Entity
In Cisco Extended Care, refers to the resources (patient and provider endpoints and users) managed by
a single Cisco Application Server.
C
Cisco Extended Care The application used by the installation team to configure, administer and manage the Extended Care
Administration
Application Server.
Cisco Extended Care The Cisco Extended Care component that maintains the master information of resources and manages
Application Server
conferences, sessions and appointments. The Application Server interfaces with Admin, Portal, and the
Unified Communications (UC) servers.
Cisco Extended Care The orderable software that includes the Cisco Extended Care Application Server, Cisco Portal, and
Application Server
Cisco Administration.
Cisco Portal
The master portal that interfaces with the Application Server. It maintains the portal login sessions and
provides interface for the Application Server to validate sessions.
Cisco Extended Care Cisco Extended Care is a software-defined platform that facilitates patients connecting with healthcare
Software
professionals in a telehealth environment.
Cisco TelePresence
Video
Communication
Server
A video server that provides Session Initiation Protocol (SIP) proxy and call control as well as H.323
gatekeeper services for video endpoints. The Cisco VCS Control application connects all
infrastructure, management, and endpoints and is critical to interoperability with unified
communications and IP telephony networks and voice-over-IP (VoIP) endpoints.
Cisco Unified
Communications
Manager
The application that extends enterprise telephony features and capabilities to packet telephony network
endpoints, such as IP phones and multimedia applications. Open telephony application interfaces make
possible services, such as multimedia conferencing and interactive multimedia response systems.
CTMS
See Cisco TelePresence Multipoint Switch.
CUCM
See Cisco Unified Communications Manager.
CUVC
Cisco Unified Video Communications
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
OL-30302-01
GL-1
Glossary
H
In Cisco Extended Care, refers to a software delivery model in which the Cisco Extended Care software
and associated client data reside in a central location managed by a hosting service and accessed by
clients using a web browser.
Hosted
P
Provider
A medical professional who provides medical consultation in a Cisco Extended Care environment.
Provider Endpoint
A computer from which the end user logged in as a provider and that acts as that provider’s associated
video endpoint.
T
TeleHealth
The delivery of health-related services and information via telecommunications technologies.
Telehealth is an expansion of telemedicine, and unlike telemedicine (which more narrowly focuses on
the curative aspect) it encompasses preventive, promotive and curative aspects.
U
UC
Unified Communications
User Profile
Your User Profile determines which screens you see, and which functions you can perform. User IDs
are configured so that users with a particular role (or roles) see only the screens and options appropriate
to that job description. Any given user can have from one to five roles, or User Profiles, within one User
ID. The Site Administrator configures the User IDs.
V
VCS
Video Communication Server
Cisco Extended Care 1.0 Application Server Installation and Administration Guide
GL-2
OL-30302-01