IntegrationGuideTacera - Web Devices February 13, 2014Austco Communication Systems Pty Ltd40 O'Malley St, Osborne Park, Western Australia 6017Phone: +61 8 9244 4499Fax: +61 8 9244 4727Web: www.austco.com
©Copyright Austco Communication Systems 2013All rights reserved.Reproduction, adaptation, or translation without prior written permission isprohibited, except as allowed under the copyright laws.WarrantyThe information contained in this document is subject to change withoutnotice.Austco Communication Systems makes no warranty of any kind withregard to this material, including, but not limited to, the implied warrantiesof merchantability and fitness for a particular purpose.Austco Communication Systems shall not be liable for errors containedherein or for incidental or consequential damages in connection with thefurnishing, performance or use of this material.Doc Version TACERA-WEBDEVICES-V3.1
ContentsChapter 1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Chapter 2 What are Web Devices? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Chapter 3 Tacera Supported Handsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Chapter 4 Who Should Read This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Chapter 5 Tacera - Web Devices Integration Guide Organization . . . . . . . . . . 7 Contacting Austco Technical Support . . . . . . . . . . . . . . . . . . . . . . . 7 Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Web Devices Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Installation Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Tacera Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 10 Infrastructure Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 SIP Registration Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . 10 Handset IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Installing the Web Devices Application . . . . . . . . . . . . . . . . . . . . . 12 Web Devices and Tacera Configuration . . . . . . . . . . . . . . . . . . . . . 17 Configuring Web Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Configuring the Handsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 SpectraLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Set Username and Password . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Configuration of Telephony Services. . . . . . . . . . . . . . . . . . . . . 21 Set Server Root URL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Set Application URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Enable Vibration and Sound Notification . . . . . . . . . . . . . . . . . . 23 Cisco 79xx Handset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Set Username and Password . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Enable Vibration and Sound Notification . . . . . . . . . . . . . . . . . . 25 DHCP Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Cisco CallManager Configuration . . . . . . . . . . . . . . . . . . . . . . . 26 Cisco Unified CallManager Express Configuration . . . . . . . . . 26 Cisco Unified CallManager Configuration . . . . . . . . . . . . . . . . 26 Configuring Tacera . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Asterisk Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Configuring the Site File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Configuring the Tacera GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Web Diagnostic Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Test Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Call Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Call Accept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Austco February 13, 2014 1
Contents Tacera Call Suppress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Call Manual Escalation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Call Timer Escalation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Call Resend. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Click to Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Unsolicited Text Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Appendix A Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492 February 13, 2014 Contents
PREFACE 1 Tacera supports integration with web devices such as text- messaging phones, using HTTP transport. This chapter includes an introduction to web devices, the types and models of web devices that Tacera supports, and naming conventions used in this guide.Austco February 13, 2014 3
What are Web Devices? Tacera What are Web Devices? Web devices are those that are capable of receiving information (primarily messages) transmitted over an IP network, via HTTP protocol, and act as both client and server. Examples are text-messaging phones that can receive push-messages (HTTP requests) and possess soft-key buttons or key-pad buttons that when pressed send out HTTP requests to implement custom commands. A web device need not necessarily be a mobile device. Figure 1-1 Tacera-Web Device integration4 February 13, 2014 Chapter 1: Preface
Integration Guide Tacera Supported Handsets Tacera Supported Handsets Many renowned brands such as Cisco, SpectraLink, Ascom, and Aastra supply IP phones and handsets to the health care industry. Though each one of the devices is unique, they have the following things in common to develop a common behaviour across them: • voice calls • writable display to show alarm details • soft-keys or buttons that can communicate commands back to Tacera Here is a list of the handsets that are supported by the Tacera Web Devices application: Figure 1-2 Tacera supported handsets Manufacturer Names Handset Models SpectraLink 8440 SpectraLink 8450 Cisco 7925G Cisco 8961Austco February 13, 2014 5
Naming Conventions Tacera6 Naming Conventions Here are the naming conventions that are widely used in Tacera technical documents: Table 1 Tacera naming conventions Product Codes Functional/Other Names of Products IP-CCT IPnet Router, Room Controller, Callpoint Controller, IP-CCT Controller, IPnet Controller IP-ACS-100/IP-ACS-110 IP Connect Server, ACS-100/ACS-110, Tacera Server IPC-Tacera Tacera GUI, Tacera Software IP-TSNS Touch Screen Nurse Station running the Tacera Graphical User Interface (GUI) IP-CPS, IP-CPG, IP-ODL, IP- IPnet devices ZTS, IP-IN8, IP-OPT8, IP-RLY, IP-TJ The Product Codes are assigned to the products by Austco. The products are sometimes referred by short names or by names based on the functions they perform and those names are listed under Functional/ Other Names of Products. Here are some terminologies, which are widely used while describing the various components of the Tacera product family: IP-ACS-100/IP-ACS-110: Hardware appliance that runs the IP Connect software and platform software. Note The Tacera IP-ACS-110 is the replacement of IP-ACS-100. Webmin: a web-based interface for system administration for Unix. Using any browser that supports tables and forms (and Java for the File Manager module), you can open Webmin to setup user accounts, Apache, DNS, file sharing and so on. CallManager: Cisco Unified Communications manager (CallManager), the core of the Cisco collaboration portfolio infrastructure, is a unified communications call control platform, which provides services such as session management, voice, video, messaging, mobility, and web conferencing. Note Tacera supports Cisco Unified Communications Manager (CUCM) 8.5 or later. Platform: Operating Systems, along with services required to run Tacera. Eg: Linux OS + [DNS server, DHCP, Time, Asterisk, Postgresql] Suite: The Tacera package that includes IP Connect,Tacera User Interface, and Site Config software Who Should Read This Guide The Tacera Integration Guide is intended for the Austco trained professionals who install and configure the Tacera Web Devices application, Tacera GUI, and the handsets, according to the requirements of clients at hospitals and aged care facilities. February 13, 2014 Chapter 1: Preface
Integration Guide Tacera - Web Devices Integration Guide Organization Tacera - Web Devices Integration Guide Organization The Tacera - Web Devices Integration Guide is organized into the following chapters: Chapter 1, Preface, introduces web devices and the Tacera supported handsets, defines this guide’s purpose, describes the guide’s organization and provides information on contacting Austco Support. Chapter 2, Web Devices Installation, provides information about uploading the Tacera web devices application to the Tomcat server of the IP Connect. Chapter 3, Web Devices and Tacera Configuration, provides information on how to configure the web devices and the Tacera system so that they work in integration with each other. Chapter 4, Diagnostics, details how to identify problems with the Tacera - Web Devices integration using a specific web diagnostic page. Chapter 5, Use Cases, details the various functions that can be performed with the Web Devices and the Tacera system. Appendix A Glossary contains the definitions of domain-specific terms used in this guide. Index contains an alphabetical listing of topics covered in this guide, along with references to locations where you can find related information. Contacting Austco Technical Support While configuring the Tacera WebDevices application, if you don’t find your questions answered in this guide, please contact Austco Support either on phone +61-8-92444499, or via e-mail [email protected]. If you have any questions concerning software licenses or maintenance agreements, please contact Austco Sales at [email protected]. Related Documentation IPC Tacera User’s Guide - details how to use the Tacera General User Interface (GUI), which is the software application for Tacera staff stations. Tacera Configuration Guide - provides the information necessary for understanding and modifying the IP Connect Configuration properties files and defines how certain features function through a range of configuration options.Austco February 13, 2014 7
Related Documentation Tacera8 February 13, 2014 Chapter 1: Preface
WEB DEVICES 2INSTALLATION Installing web devices involves using Webmin to upload the application to the Tomcat server of the IP Connect. Having prior experience with Tacera and SpectraLink, or Cisco handsets greatly helps with the installation process.Austco February 13, 2014 9
Installation Pre-requisites Tacera Installation Pre-requisites Before you install the web devices application, review the following installation pre-requisites: Tacera Software Requirements You need the following Tacera software, which you can download from the Austco reseller’s download page: • Tacera IP-ACS-110 platform 3 or later • Tacera IP Connect 3.1.x or later • Tacera Nurse Station GUI 3.1.x or later • Tacera IP Connect Site Configuration 3.1.x or later • Tacera Web Devices tacera.module.webdevices.tar Infrastructure Requirements Make sure the following infrastructure requirements are met: • A wireless network compatible with the handsets is deployed and configured. • IP connectivity is established between Tacera and wireless network. • Cisco CallManager is deployed and configured in case of Cisco handsets. • All necessary VLANs and other infrastructure are done. • Handsets are configured. • Handset registration to PBX is completed. • Handsets are successfully connected to the wireless network. SIP Registration Requirements An external PBX is often present at the site handling all telephony. When available, this PBX can be used for handset registration. In small sites where handsets are used only for patient calls, then registration to IP- ACS-110 Asterisk can be used, thereby avoiding the need for an external PBX. When an external PBX is used, then a SIP trunk between the PBX and Asterisk is required, when telephony calls from handsets to bedside IP- TALKTWO is required.10 February 13, 2014 Chapter 2: Web Devices
Integration Guide Installation Pre-requisites Cisco handsets may require Cisco CallManager on the PBX - refer to Cisco documentation. Figure 2-1 Tacera-Web Devices network Handset IP Addresses It is recommended to use static or reserved IP addresses. If DHCP is to be used then Tacera must resolve IP Addresses from the PABX or soft switch where the handsets register. Currently Cisco CallManager and Tacera internal asterisk PBX are the only PABX supported for address resolution. If other PABX is used then static IP addresses must be used.Austco February 13, 2014 11
Installing the Web Devices Application Tacera Installing the Web Devices Application To install the Web Devices application: 1 Login to Webmin: a From a PC connected to the IP Connect Server, open a web browser, preferably, Internet Explorer (9.0 or newer). b Type in “<IP Connect Server address>:10000” (i.e. 10.1.1.250:10000) in the address bar and press Enter. The Webmin page should appear and means that the IP Connect Server is up and running. Figure 2-2 Webmin login page c Login using your Username and Password. 2 On the modules pane, click Upload Download Files. Figure 2-3 Webmin landing page12 February 13, 2014 Chapter 2: Web Devices
Integration Guide Installing the Web Devices Application 3 Click . On the Upload File window, browse for the downloaded web devices tar file and click Upload. Figure 2-4 Uploading webdevices application via webmin Warning Make sure that the Tomcat server is enabled - on the modules pane of Webmin, go to ToolBox > Manage Tomcat server. From the drop- down list, select enable and click Execute. 4 Go back to Tool box > Upgrade or install an ACS110 Platform module. Click , next to ACS110 archive.Austco February 13, 2014 13
Installing the Web Devices Application Tacera 5 On the Choose File.. window, select the webdevices application file that you recently uploaded and click Ok. Figure 2-5 Choose File.. window 6 Click Execute. The web application is unpacked and copied to tomcat webapps folder and tomcat is restarted to deploy the application. Figure 2-6 Execute command14 February 13, 2014 Chapter 2: Web Devices
Integration Guide Installing the Web Devices Application 7 On the modules pane, click Monitoring to double-check that the webapp server has a green tick as shown below. Figure 2-7 System and server statusAustco February 13, 2014 15
Installing the Web Devices Application Tacera16 February 13, 2014 Chapter 2: Web Devices
WEB DEVICES 3AND TACERACONFIGURATION Configuration involves the actual integration of web devices with Tacera. The web devices application installed in the Tomcat server is customised via webmin while Tacera configuration is performed in the Tacera GUI (Graphical User Interface). The handsets also need certain customisation changes, which may be well explained in the respective user documents.Austco February 13, 2014 17
Configuring Web Devices Tacera Configuring Web Devices Configuring Web Devices involves editing the webdevices.properties file and restarting the Tomcat server to take effect. Here are the detailed steps: 1 Go to ToolBox and click Tacera WebDevices configuration Edit. The following table lists the webdevices’ property parameters, default values and their descriptions: Figure 3-1 Web Devices propertiesParameters Default Values Descriptiontomcat.ipaddress 10.1.1.250tomcat.port 8080 Tomcat IP addressacs.ipaddresses 10.1.1.250 Polycom Tomcat portspectralink8400.user 456spectralink8400.password Supports multiple ACS/IPConnect. For each ACSspectralink8400.location.depth -2 provide an IP address. The IP addresses must be a comma (,) separated list (i.ecisco79xx.user tacera acs.ipaddresses=IP_A, IP_B, IP_C).cisco79xx.password taceracisco79xx.location.depth Eg: acs.ipaddresses=192.168.5.221, -2 192.168.5.222, 192.168.5.223cisco79xx.vibrate.on Username for the SpectraLink phonescisco79xx.ringtone.on truecisco79xx.ringtone true Password for the SpectraLink phones Chime.raw Mention the number of levels that have to be included in the location name. • a positive value means you skip N nodes from root and display the rest • negative value means you include N nodes from leaf • zero means you start from root and display all levels Eg: if location is A.B.C.D (with A the root and D the leaf), then: -2 shows C.D -1 shows D 0 shows A.B.C.D 1 shows B.C.D 2 shows C.D Username for the Cisco phones Password for the Cisco phones Mention the number of levels that have to be included in the location name. • a positive value means you skip N nodes from root and display the rest • negative value means you include N nodes from leaf • zero means you start from root and display all levels Set the vibration on/off for the Cisco phones Set the ringtone on/off for the Cisco phones Fill in the ringtone sound clip name of the Cisco phones18 February 13, 2014 Chapter 3: Web Devices and Tacera Configuration
Integration Guide Configuring Web DevicesParameters Default Values Descriptionasterisk.resolve.phone.ipaddress false • If the Spectralink phones use static IP, setasterisk.ipaddress asterisk.resolve.phone.ipaddress=false 10.1.1.250 • If the SpectraLink phones are registered and DHCP is used, then for each Asterisk, setasterisk.port 5038 asterisk.resolve.phone.ipaddress=trueasterisk.user xcare If the SpectraLink phones use DHCP, set the ipaddress to the Asterisk IP Address that theasterisk.password asterisk phones are registered with.callmanager.resolve.phone.ipaddress false If you use multiple Asterisks, then set a comma separated list with each Asterisk IP address —callmanager.ipaddress ipaddresscallmanager.port 8443 E.g. In case of three ACS-110s with IP Addressescallmanager.user username IP_A, IP_B, and IP_C, if you want to activate thecallmanager.password password IP address resolution using Asterisk in the ACS-callmanager.https true 110 with IP_A and the ACS-110 with IP_B, while disabling it in the ACS-110 with IP_C, then youautodialextensioncalltype Patient Call must set: asterisk.ipaddress=IP_A, IP_B Asterisk port You don’t specify this for a disabled Asterisk. Asterisk username You don’t specify this for a disabled Asterisk. Asterisk password You don’t specify this for a disabled Asterisk. • If Cisco phones use static IP, set false • If Cisco phones are registered and DHCP is used, set true Cisco CallManager IP Address Cisco CallManager port Cisco CallManager username Cisco CallManager password set https true/false to enable/disable use of HTTPS set the call types that have to support auto dial. This feature force the device to make a call when it acknowledges (presses Accept) an alarm of the specified call type. The call types must be a comma (,) separated list. E.g: autodialextensioncalltype=Patient Call, Staff Assist, Code BlueAustco February 13, 2014 19
Configuring Web Devices Tacera Figure 3-2 Editing the web devices configuration file 2 Click Save. 3 Go to Tool Box > Manage Tomcat server, select restart, and click Execute.20 February 13, 2014 Chapter 3: Web Devices and Tacera Configuration
Integration Guide Configuring the Handsets Configuring the Handsets Refer to manufacturer instructions on how to configure the handsets. SpectraLink Configuration must either be set in phone using the browser interface or the ftp configuration. Set Username and Password From the phone menu, navigate to Settings > Basic Settings > Login Credentials.... The User: and Password: must be set the same as in webdevices.properties spectralink8400.user and spectralink8400.password. Figure 3-3 webdevices.properties file Configuration of Telephony Services To enable telephony services, the handset must be registered to the Tacera Asterisk. To configure telephony: 1 From the phone menu, navigate to Settings > Advanced Settings. 2 Enter Password. 3 Go to Administration Settings... > Line Configuration... > Line 1.... 4 Enter Display Name: and Address:, if they are not set before. Note Display Name is the name that displays when you make a call. It is the name that identifies the handset, for example, Admin Phone. Address is the extension number, for example, 2004.Austco February 13, 2014 21
Configuring the Handsets Tacera 5 Scroll down and go to SIP Protocol... > Server1. 6 Enter the following details: • Address: <<address of Tacera Asterisk>> e.g: 192.168.200.27 • Port: <<port number>> e.g: 5060 • Register: Yes • Transport: Naptr 7 Press OK on the handset. 8 Press the Home button to go back to the phone menu. 9 Navigate to Settings > Advanced Settings. 10 Enter Password. 11 Go to Administration Settings... > Call Server Configuration... > SIP... > SIP Outbound Proxy... 12 Enter the following details: • Address: <<address of Tacera Asterisk>> e.g: 192.168.200.27 • Port: <<port number>> e.g: 5060 • Transport: Naptr 13 Press OK on the handset. Set Server Root URL To set up the server root URL: 1 Using a browser on your computer, open the Polycom Spectralink configuration web page by typing http://<phone ip address> in the address bar. 2 Navigate to Settings > Applications. 3 Expand the Push option. From the Allow Push Messages drop- down list, select All. 4 Set the Application Server Root URL to Tomcat server IP address and port. If redundancy is used, then it must be the virtual IP address. The port, by default, is 8080. For example: http://192.168.1.172:8080. 5 Enter User Name and Password. Click Save. Figure 3-4 Setting the server root url22 February 13, 2014 Chapter 3: Web Devices and Tacera Configuration
Integration Guide Configuring the Handsets Set Application URL To set up Tacera as a handset application where you can see the active calls and messages: 1 Using a browser on your computer, open the Polycom Spectralink configuration web page. 2 Navigate to Settings > Applications > Configure URLs. 3 On the Application URL text-box, enter http://<ip address of the IP Connect server with webdevices installed>:8080/ tacera.module.webdevices/spectralink8400/ showalarms?extension=<phone extension number>. Example: http://192.168.200.142:8080/tacera.module.webdevices/ spectralink8400/showalarms?extension=2004 Figure 3-5 Configure URL 4 On the Application Name text-box, enter tacera. 5 Click Save. 6 From the phone menu, go to Applications. You may find Tacera as an application. Opening the Tacera application displays the current alarms and notifications. Enable Vibration and Sound Notification Warning The alert is only for Normal profile. Selecting Silent or other profiles may inhibit alert. To enable audible sound and vibration when message arrives: 1 Using a browser on your computer, open the Polycom Spectralink configuration web page. 2 Navigate to Utilities > Import & Export Configuration. 3 Export Configuration File (select All Configuration, click Export, and save it as a text file). 4 If you don’t have Notepad++ installed, download Notepad++. Right- click the configuration file and click Edit with Notepad++.Austco February 13, 2014 23
Configuring the Handsets Tacera 5 Add the following lines to the file: apps.push.alertSound=\"1\" np.normal.alert.positiveConfirm.vibration=\"1\" np.normal.alert.positiveConfirm.tonePattern=\"instantMessage\" Note If you use a SpectraLink phone with software version 4.3 or later, then replace apps.push.alertSound in the above code snippet with the following lines, in order to make the phone ring and vibrate on application alarm: np.normal.alert.apiPush.tonePattern=\"instantMessage\" np.normal.alert.apiPush.vibration=\"1\" 6 Save file. 7 Go back to Polycom Spectralink configuration web page and click Utilities > Import & Export Configuration. Figure 3-6 Import & Export Configuration 8 Select Import Configuration file (select the edited file) and click import.24 February 13, 2014 Chapter 3: Web Devices and Tacera Configuration
Integration Guide Configuring the Handsets Cisco 79xx Handset Tacera settings follow CallManager. Set Username and Password The username and the password in the Cisco CallManager must be set the same as in webdevices.properties cisco79xx.user and cisco79xx.password. Figure 3-7 webdevices.properties file Enable Vibration and Sound Notification Set the webdevices.properties cisco79xx.vibrate.on=true to enable vibration and the cisco79xx.ringtone.on=true to enable sound notifications. By default these options are enabled. DHCP Operation While it is recommended that static or reserved IP Addresses are used, it is possible for the phones to use dynamic DHCP under the following conditions: The phone must be registered to Asterisk or CallManager.Austco February 13, 2014 25
Configuring the Handsets Tacera Cisco CallManager Configuration Cisco Unified CallManager Express Configuration Caution As of now the Tacera Web Devices implementation supports only Cisco Unified Communications Manager Express (CUCME) configured with web devices’ static IP addresses. To configure CUCME, the user must type in commands so it is advised that the installer should have knowledge of the Cisco Unified Call Manager Express. The CUCME System Administrator Guide provides useful information and it is available at http://www.cisco.com/en/US/docs/ voice_ip_comm/cucme/admin/configuration/guide/cmeadm.html. Here are the CUCME configuration steps: 1 To define a phone user account, follow the instructions in the Using Cisco IOS Software Commands to Define a Phone User Account (page 524) section of the CUCME System Administrator Guide. Perform the steps 1-5 for every phone, in order to set them all with the same username/password. 2 To define authentication for XML access, follow the instructions in the Authentication for XML Access (page 1645) section of the CUCME System Administrator Guide. Perform the steps 1-5. 3 Follow the instructions in the Configuring Cisco Unified CME for Extension Mobility (page 1109) section of the CUCME System Administrator Guide. Perform the steps 1-10. • Set url authentication to http://CME_IP_ADDRESS/CCMCIP/ authenticate.jsp • Set service phone webAccess 1 • Set authentication credential Cisco Unified CallManager Configuration Following are some screenshots of a typical Cisco Unified Call Manager (CUCM) configuration that works with Tacera. The Web Devices application is being run with an application user tacera.26 February 13, 2014 Chapter 3: Web Devices and Tacera Configuration
Integration Guide Configuring the Handsets Login to CUCM and from the menu, select Device > Phone. You see a list with the phones registered in the CUCM. Note The following illustrations are examples only. Figure 3-8 List showing all registered phones in CUCM The last 3 phones in Figure 3-8 are those that are configured to work with Tacera Web Devices. The IP addresses of the phones are displayed in the IP Address column. Configuration of one of the phones is illustrated here as an example. If you click on one of the phones’ Device Name, CUCM displays the associated phone configuration, as shown in Figure 3-9 to Figure 3-11. Figure 3-9 Phone configuration 1/3Austco February 13, 2014 27
Configuring the Handsets Tacera Figure 3-10 Phone configuration 2/3 Figure 3-11 Phone configuration 3/3 To perform the application user configuration, go to User Manager > Application User, and click on the preferred User ID (e.g: tacera). This is an important step for the correct configuration.28 February 13, 2014 Chapter 3: Web Devices and Tacera Configuration
Integration Guide Configuring the Handsets Figure 3-12 Application user configuration Figure 3-13 Tacera user configuration 1/2Austco February 13, 2014 29
Configuring the Handsets Tacera In Figure 3-13, you can see the tacera user id, password, and controlled devices that are registered under tacera. All these information are mandatory to create a valid application user tacera. This way, when the user/password credentials are used to send messages to the phones, they are properly authenticated and the messages are not rejected. Figure 3-14 Tacera user configuration 2/2 The final step is to configure the CUCM to allow full web access. Navigate to System > Enterprise Phone Configuration. From the drop-down list corresponding to Web Access, select enabled, and also select the Override Common Settings check-box, as shown in Figure 3-15. Figure 3-15 Application Web Access Configuration30 February 13, 2014 Chapter 3: Web Devices and Tacera Configuration
Integration Guide Configuring Tacera Configuring TaceraNote Asterisk Changes To set up the web devices for If the pre-assigned dial plan and extensions are used, then the asterisk do messaging, you can not require any changes. If Tacera has extensions, or click to call is use either the Site required, but Asterisk is not the phone PABX, then SIP trunk must be Configuration established between Asterisk and external PABX. application or the GUI application. Configuring the Site File Here are the Site Configuration steps to set up the web devices for messaging: 1 Open the IP Connect Site Configuration application. 2 Go to File > Download from an IP Connect Server. Choose the StandAlone connection option, enter the Server Address, click Test Connection. 3 Once the connection is successful, click Download. The site file that is currently on the IP Connect Server loads on the Site Configuration. 4 Go to Devices > Other Devices. Click Cisco or Aastra Text Phone Devices or SpectraLink NetLink 80XX Devices. 5 Add the Device Name and the Phone Number [extension;IP address], as shown in the following example. Figure 3-16 IP Connect Site Configuration: Device PropertiesAustco February 13, 2014 31
Configuring Tacera Tacera For information about editing the message and assigning devices to contacts, refer to the Tacera Configuration Guide (Chapter 4: Site Configuration). Configuring the Tacera GUI Here are the GUI configuration steps to set up the web devices for messaging: 1 Open Tacera GUI. Go to Settings > Devices Configuration. 2 Add your mobile devices, SpectraLink and/or Cisco - Click New. On the Device Editor dialog-box, select the device type from the drop- down list, and enter the Device Name and Phone Number. Figure 3-17 Device Editor dialog-box 3 Device Name is the name you assign for the device. 4 Phone Number is the extension number of the device, should be same as handset. Note If static IP address is used then enter Phone Number as <extension>;<IPAddress> for example 5733;10.1.1.22 5 Select Auto-generate Contact(s) to automatically create contact(s) associated with the device. 6 Select Send Call Resets to send a cancel message to the device when the call is cancelled (from the callpoint). 7 To create multiple devices of the same type: a Select the number from the Bulk Create list. b Click Bulk Create. A confirmation message appears.32 February 13, 2014 Chapter 3: Web Devices and Tacera Configuration
Integration Guide Configuring Tacera c Click Yes. The Edit Bulk Devices dialog-box appears. Edit the auto-generated information for each device. Figure 3-18 Edit Bulk Devices dialog-box d Click Update to save your changes before adding information for the next device in the list. e Repeat for all added devices. Click OK. 8 Repeat step 2 to step 7 for all other devices. 9 Go back to Settings and click Contacts Configuration. 10 Select the contact you want to assign the web devices to, and click Edit.Austco February 13, 2014 33
Configuring Tacera Tacera 11 Assign the web devices to the contact - On the Contact Editor dialog-box, select from Available Devices and click Assign. Figure 3-19 Contact Editor dialog-box 12 Click OK. 13 Go to Roster, assign shifts to the contacts and click Save. 14 Go to Call Assignment.34 February 13, 2014 Chapter 3: Web Devices and Tacera Configuration
Integration Guide Configuring Tacera 15 Select location node, Contacts, Priorities, and Notifications. Figure 3-20 Call Assignment 16 Click Save All.Austco February 13, 2014 35
Configuring Tacera Tacera36 February 13, 2014 Chapter 3: Web Devices and Tacera Configuration
DIAGNOSTICS 4 There is a web diagnostic page that helps with identifying problems related to the integrated function of Tacera and web devices. It is recommended to test the features and functionalities before the final deployment.Austco February 13, 2014 37
Web Diagnostic Page Tacera Web Diagnostic Page The web diagnostic page lists the following: • a table showing a row per active call that is to be notified to at least one phone • a table per notified phone listing phone details and a row for each call notified to a particular phone The web page can be accessed using the following url: http://<serverIPAddress>:8080/tacera.module.webdevices/test/alarmlist where serverIPaddress is the IP address of the web server hosting the web devices application. Figure 4-1 Web Diagnostic Page Active Alarm Message delivery status if active=false, the device does not receive any messages if active=true, the device receives messages38 February 13, 2014 Chapter 4: Diagnostics
Integration Guide Test Alarm Test Alarm Use the following table to test the integrated functions of Tacera and web devices. Table 1 Testing alarmsStep Expected ResultActivate a call point in the location covered by the All phones covering the location should display thedevices callActivate more than one call The phone should display all alarms based on priorityNavigate up/down call list using left/right button for Text should be selected for the in-focus alarmSpectraLink and up/down button for Cisco phonesPress soft-key Accept The alarm list of the accepting phone will briefly display the accepted message and then the call list is updated. All other phones will stop displaying this alarm.Press soft-key Suppress The in-focus alarm will no longer be shown on this phone, but will remain on other phones if present.Press soft-key Escalate Alarm is escalated. If a new phone is on the escalation level, then this phone will receive this alarm for the first time.Press soft-key View More details of the alarm are shownIn View, if there is an extension for the call, it will be Extension is calleddisplayed.SpectraLink - Using navigation Left/Right ensureextension is in-focus. Then press OK on navigation.Cisco - Select the dial option and press Ok.Austco February 13, 2014 39
Test Alarm Tacera40 February 13, 2014 Chapter 4: Diagnostics
USE CASES 5 After installing and configuring the web devices application, Tacera and the handsets, the devices are ready to use. This chapter describes the various functions associated with the Tacera-Web Devices integration.Austco February 13, 2014 41
Call Alert Tacera Call Alert Here is how the call alert functionality works: 1 Patient/Staff presses a Tacera call button. 2 Tacera sends a detailed message to the devices associated with the call. 3 The device user is alerted of a message arrival. 4 After viewing the message, the device user can: • Do nothing • Accept call • Escalate call • Suppress call • View details which are explained in the following sections. Note For a particular device, if multiple calls arrive at the same time, Tacera prioritises the calls and sends message to the device, showing all the calls. Call Accept Here is how the call accept functionality works: 1 When the device user decides to accept a call, Accept has to be pressed. 2 Once the user presses Accept, Tacera identifies that call as accepted. 3 Tacera updates the other phones - the accepted call is removed from the active calls’ list (or call messages) of the phones. 4 Tacera also updates the phone that acknowledged the call. Note If the incoming call location has an extension and that call type is configured to automatically dial that extension, then Tacera, besides accepting the call, establishes voice communication (telephone call) between the device and the patient. To configure a call type to be automatically dialed to its extension, set that call type for autodialextensioncalltype parameter, when you edit the webdevices.properties file. See “Configuring Web Devices” on page 18.42 February 13, 2014 Chapter 5: Use Cases
Integration Guide Call Suppress Call Suppress The device user may choose to suppress a call, if the call is of no importance or it is of low priority to the user. Here is how the call suppress functionality works: 1 The device user presses Suppress. 2 Tacera removes this call from being shown on that phone. 3 Tacera then updates the phone - the suppressed call is removed from the active calls’ list (or call messages) of the phone. Note Call escalation releases suppression from all the devices. Call Manual Escalation The device user may choose to manually escalate a call, provided the call has not been cancelled yet. Here is how the manual escalation functionality works: 1 The device-user presses Escalate. 2 Tacera performs the following actions: a escalates the call to the next-level b un-accepts suppressed calls c removes any phone call suppression d selects all phones from the next notification level and adds it to the set from all previous notification levels e messages all phones in the set, including the previously acknowledged phone Call Timer Escalation Call timer escalation is automatically enabled when a call has not been cancelled and escalation timer expires, causing the call to be escalated to the next notification level. When auto-escalation is enabled, Tacera performs the following functions: 1 un-accepts the call if it was accepted 2 removes any phone call suppression 3 selects all phones from the next notification level and adds it to the set from all previous notification levels 4 sends message to all phones in the set, including the previously acknowledged phoneAustco February 13, 2014 43
Call Resend Tacera Call Resend Call resend is automatically enabled when a call has not been cancelled and resend timer expires, causing the call to be resent. When resend is enabled, Tacera performs the following functions: 1 ignores resend, if the call has been acknowledged 2 don’t send message to phones that have suppressed the call 3 selects all phones in current notification levels and send message Click to Call The device user may decide to make a voice call to the extension identified in the call details. You may call that extension just like you make an ordinary call, pressing OK (SpectraLink phones) or Enter (Cisco phones) button. Call need not be accepted to do this. Figure 5-1 Press Enter to dial extension Enter button SpectraLink Cisco If the user presses Accept to acknowledge the call, which has an extension available, a voice call is established automatically. However, this depends on the configuration for that call type.44 February 13, 2014 Chapter 5: Use Cases
Integration Guide Unsolicited Text Message Unsolicited Text Message Note This is a future functionality. The Tacera Nurse Station user may send a text-message to a contact who is mapped to this device, provided the Nurse Station has Comms enabled. Here is how the text-message function works: 1 The Nurse Station user selects contact to send message to. 2 The Nurse Station user enters a text-message and send to the contact. 3 Tacera identifies the devices to be notified. 4 The text-message is sent to those devices.Austco February 13, 2014 45
Unsolicited Text Message Tacera46 February 13, 2014 Chapter 5: Use Cases
Appendix AGlossaryTerm DefinitionAsterisk Asterisk is an open source framework for building communications applications. Asterisk turns an ordinary computer into a communications server. Asterisk powers IP PBX systems, VoIP gateways, conference servers and other custom solutions.DHCP DHCP is a protocol that assigns unique IP addresses to devices, then releases and renews these addresses as devices leave and re-join the network.DNS DNS is an abbreviation for Domain Name System, a system for naming computers and network services that is organized into a hierarchy of domains. DNS naming is used in TCP/ IP networks, such as the Internet, to locate computers and services through user-friendly names. When a user enters a DNS name in an application, DNS services can resolve the name to other information associated with the name, such as an IP address.HTTP Short for HyperText Transfer Protocol, the underlying protocol used by the World Wide Web. HTTP defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands.PABX Short for Private Automated Branch Exchange, this telephone network is commonly used by callcentres and other organizations. PABX allows a single access number to offer multiple lines to outside callers while providing a range of external lines to internal callers or staff.PBX Short for private branch exchange, a private telephone network used within an enterprise. Users of the PBX share a certain number of outside lines for making telephone calls external to the PBX.SIP Short for Session Initiation Protocol, it is an application-layer control protocol; a signalling protocol for Internet Telephony. SIP can establish sessions for features such as audio/ videoconferencing, interactive gaming, and call forwarding to be deployed over IP networks, thus enabling service providers to integrate basic IP telephony services with Web, e-mail, and chat services.SIP Trunk A SIP trunk is a direct connection between your organization and an ITSP. It enables you to extend VoIP telephony beyond your organization’s firewall without the need for an IP-PSTN gateway. Additionally, SIP trunks can carry instant messages, multimedia conferences, user presence information, Enhanced 9-1-1 (E9-1-1) emergency calls, and other SIP-based, real- time communications services.Unified Unified communications (UC) is the integration of real-time communication services such asCommunications instant messaging (chat), presence information, telephony (including IP telephony), video conferencing, data sharing (including web connected electronic white boards aka IWB's or Interactive White Boards), call control and speech recognition with non-real-time communication services such as unified messaging (integrated voicemail, e-mail, SMS and fax). UC is not necessarily a single product, but a set of products that provides a consistent unified user interface and user experience across multiple devices and media types.VLAN Short for virtual LAN, a network of computers that behave as if they are connected to the same wire even though they may actually be physically located on different segments of a LAN.Austco February 13, 2014 47
Glossary Tacera48 February 13, 2014 Glossary
Search
