Nautilus Hyosung MoniPlus2 User manual

MoniPlus2 Release 02.03.xx
Voice Guidance Configuration Guide
Ver. 2.0
©2014 Nautilus Hyosung, Inc. All Rights Reserved.

All information described in this manual is a licensed product of Nautilus Hyosung Corporation.
It is the policy of Nautilus Hyosung Corporation to improve products as new technology,
components, software, and firmware become available. Therefore Nautilus Hyosung reserves
the right to change specifications without notice.
APTRA™ is a trademark of NCR Corporation.
©2014 Nautilus Hyosung, Inc. All Rights Reserved.

MoniPlus2 Voice Guidance Configuration Guide
April 29, 2014 i
Table of Contents
1 Introduction...........................................................................................................................................1
1.1 What’s New ..................................................................................................................................1
1.2 Audience.......................................................................................................................................1
1.3 Additional References...................................................................................................................1
1.4 Required MoniPlus2 Software Version ........................................................................................2
1.5 Required Tools..............................................................................................................................2
2 Overview of a Voice Guidance Session................................................................................................3
2.1 Multiple Language Support ..........................................................................................................3
2.2 Keyboard Mapping .......................................................................................................................3
2.3 VG Volume Controls....................................................................................................................4
2.4 Increasing Timers for VG Sessions ..............................................................................................4
2.5 MoniMax ATM Hardware Restrictions........................................................................................4
2.6 Deposit Automation Screens VG Support....................................................................................4
3 VG Transaction Processing...................................................................................................................5
3.1 Transaction Request Messages .....................................................................................................5
3.2 Transaction Reply Messages.........................................................................................................5
3.3 Interactive Transaction Response Messages.................................................................................5
4 Creating the VG XML File...................................................................................................................6
4.1 Declaration Tag.............................................................................................................................6
4.2 Start and End Tags........................................................................................................................6
4.3 VG XML File Elements................................................................................................................6
4.4 <Config> Element.........................................................................................................................7
4.4.1 <afaLang> Element...............................................................................................................8
4.4.2 <LangOption> Element ........................................................................................................8
4.4.3 <afaOption> Element............................................................................................................9
4.4.4 <Config> Element Sample..................................................................................................11
4.4.5 Adding the Dynamically Built Device Orientation Scripts.................................................12
4.5 <Keyboard> Element..................................................................................................................14
4.5.1 Keyboard Attributes............................................................................................................14
4.6 <Key> Element...........................................................................................................................14
4.6.1 Key Attributes.....................................................................................................................14
4.6.2 <Keyboard> Element Sample.............................................................................................15
4.7 <Audio> Element........................................................................................................................15
4.7.1 Audio Attributes..................................................................................................................16

MoniPlus2 Voice Guidance Configuration Guide
April 29, 2014 ii
4.8 <Text> Element ..........................................................................................................................19
4.8.1 Text Attribute......................................................................................................................19
4.8.2 Embedded Text Elements ...................................................................................................19
4.8.3 Audio Element Samples......................................................................................................20
5 Sending VG Data in Authorization Messages....................................................................................22
5.1 VG Data in Transaction Reply Messages ...................................................................................22
5.1.1 Using the Screen Display Update Field..............................................................................22
5.1.2 Printer Data Fields ..............................................................................................................23
5.2 VG Data in Interactive Transaction Response Messages ...........................................................26
5.2.1 Direct Audio Text Method..................................................................................................26
5.2.2 Indirect Audio ID Method...................................................................................................27
6 Transferring the Voice Guidance XML File to the ATM...................................................................29
6.1 Locally Copying the XML File onto the ATM...........................................................................29
6.2 Downloading the VG XML File to the ATM.............................................................................29
6.2.1 Load VG XML File Message with Identifier ‘V’...............................................................29
6.2.2 Terminal Response to the Load XML File Message...........................................................30
7 Terminal Status Messages...................................................................................................................31
7.1 Specific Command Reject Message............................................................................................31
A MoniPlus2 VG XML File Elements Quick Reference .......................................................................33
B Sample MoniPlus2 VG XML File......................................................................................................35
C Index ...................................................................................................................................................44
Revision History
Version
Date
Change Summary
1.0
3/27/13
Initial Issue
2.0
4/29/14
Removed ‘state=”private” ’ attribute from all samples. The default is
private speaker vs. public speaker so this is not needed nor is it
supported. It is ignored if included.
Updated the device orientation script information on pages 12-13.
Previously the script was appended. Now its inclusion and location
are configurable through the use of the Device Orientation feature
CD.
Added instruction to create any directory that you need that does not
already exist on page 29.

MoniPlus2 Voice Guidance Configuration Guide
April 29, 2014 1
1 Introduction
This document explains how Voice Guidance (VG) has been implemented in the MoniPlus2 release
02.03.xx application and how to build a VG XML file to support the screens in your download. The
information in this document is organized into the following sections.
Section 2, Overview of a Voice Guidance Session, describes how a VG session is initiated and what is
presented to the customer.
Section 3, VG Transaction Processing, discusses possible transaction request and reply message
differences when processing VG transactions.
Section 4, Creating the VG XML File, explains the contents of the VG XML file and provides samples for
each section where appropriate.
Section 5, Sending VG Data in Authorization Messages, explains how to include VG data in transaction
reply and interactive transaction response messages.
Section 6, Transferring the Voice Guidance XML File to the ATM, explains how to locally copy or
download from host the VG XML file to an ATM.
Section 7, Terminal Status Message, includes the VG-related status messages that the ATM can send to
the host.
Appendix A, MoniPlus2 VG XML File Elements Quick Reference, contains a list and short description of
the elements and attributes used in a MoniPlus2 VG XML file.
Appendix B, Sample MoniPlus2 VG XML File, contains a sample VG XML file that includes the most
commonly used elements.
1.1 What’s New
This issue of the MoniPlus2 Voice Guidance Configuration Guide includes the following update:
•The addition of the device orientation script information is now configurable through the use of the
Device Orientation feature CD.
1.2 Audience
This document is written for host programmers who are responsible for implementing VG in their
networks and for Nautilus Hyosung Professional Services personnel who support these networks.
However, anyone interested in learning about the MoniPlus2 VG implementation would benefit from
reading selected sections of this document.
1.3 Additional References
The following document complements this one.
•MoniPlus2 NDC Terminal Programmer’s Reference manual
•MoniPlus2 Release 02.03.xx Software Installation and Configuration Guide

MoniPlus2 Voice Guidance Configuration Guide
April 29, 2014 2
1.4 Required MoniPlus2 Software Version
Your ATMs must be running MoniPlus2 version 02.03.07.xx or higher to support Voice Guidance as
explained in this document. Use the Version Info function in Supervisor to verify the version of software
running on the ATMs. The application version will be the first entry displayed in the versions list and will
be listed on the screen as shown below:
AP : V 02.03.xx.xx
The application version number is also listed on the ATM Status window as shown in the circled area on
the sample screen below.
1.5 Required Tools
Although not required, an XML editor will make creating your VG file easier.

MoniPlus2 Voice Guidance Configuration Guide
April 29, 2014 3
2 Overview of a Voice Guidance Session
A voice guided ATM session starts when a customer inserts his head jack into the socket on the ATM. If
VG is not currently available at the ATM, the customer will hear a default message stating this.
When the ATM detects a jack insertion and VG is available, the customer can be presented with options
to control certain aspects of the session if these options are included in the VG XML file. These options
include:
•Volume – the customer can raise or lower the volume level of the VG instructions
•Screen blanking – to ensure privacy, the customer can elect to have the ATM display a blank screen,
rather than the customer screens, during his session.
•Advertisements – the customer can elect to hear or skip any audio messages designated as
advertisements.
•ATM orientation – the customer can elect to hear or skip a detailed description of the location of the
devices on the ATM when an orientation script is included in the VG XML file.
If these options are not included in the VG XML file, by default the screen will be blanked, the customer
will hear ads, and only the audio associated with the Welcome screen will be voiced (no orientation
instructions will be offered). If the customer inserts his card before setting all of the option, the defaults
for the unanswered questions will be used.
After the customer has selected his session options, he is instructed to insert his card to begin a
transaction.
Each screen displayed to the customer should have an audio instruction associated with it to guide the
customer through the transaction; this includes all host replies when screen update data is typically
displayed to the customer.
2.1 Multiple Language Support
MoniPlus2 release 02.03.07.xx introduces support for multiple language voice guidance though the use of
an add-on, third-party, text-to-speech engine. The currently supported speech engine is AT& T Natural
Voice. You order this speech engine through your NH sales representative using NH Software Product ID
9929999911. There is an additional charge for this add-on package.
By default MoniPlus2 release 02.03.xx uses the built-in Microsoft text-to-speech engine. There is no
charge for this speech engine, but it supports only a single language. You must order the add-on package
to use multiple language voice guidance.
Also see the MoniMax ATM Hardware Restrictions section on page 4 for exceptions to the use of text-to-
speech engines.
2.2 Keyboard Mapping
For VG sessions, all FDKs need to be mapped to keys on the numeric keypad for each screen that
presents FDKs. This keyboard mapping is defined in the Keyboard section of the VG XML file and each
audio message can include a ‘keyboard’ attribute to associate the screen with the desired keyboard
mapping.
When a customer presses keys during a VG session, the key presses will be echoed back (voiced) to the
customer. This does not apply, however, to masked entries such as PIN entries. For masked entries, the

MoniPlus2 Voice Guidance Configuration Guide
April 29, 2014 4
customer will hear only beeps. You should include this information in your orientation script. If no
orientation script is included, this echoing information should at least be included in the audio message
defined for the Welcome screen and on screens that contain a masked entry.
More information about keyboard mapping is included in the <Keyboard> Element section on page 12.
2.3 VG Volume Controls
During transactions, a customer can change the volume of the audio by pressing the bottom left key
( - ) on the keypad. The volume control works in a circular manner. The volume will step up with each –
key press until it reaches the maximum. The next – key press will change the volume to its lowest level
and then each - key press will increase the volume until it reaches its highest level again.
Volume control instructions are included in the NH dynamic device orientation text which can optionally
be added to your own VG file. If you are not using the dynamic device orientation option, you should at
least include the volume instructions in the text for your own orientation.
2.4 Increasing Timers for VG Sessions
Some NDC timers need to be increased to accommodate the customer performing a VG transaction.
Several timers that involve customer actions, such as making a keyboard response and taking cash, have
been identified as needing an extended timer value. A parameter in the VG XML file can be included that
will add additional time to these particular timers. See the <Config> Element on page 7 for more
information this timer parameter.
After a VG session has completed, all timers are set back to their original values.
2.5 MoniMax ATM Hardware Restrictions
There are some older models of MoniMax ATMs that use a hardware text-to-speech (TTS) engine in
place of the Microsoft software text-to-speech engine. The MoniMax ATMs models that have this TTS
hardware solution are the 5100 (formerly the 9030) and the 7100T (formerly the 7040T). When the
hardware TTS engine is used on an ATM, the following restrictions apply to the VG described in this
document:
•The maximum number of time a VG message can be repeated is 10 rather than unlimited.
•There is a fixed interval of 3 seconds between audio message repeats.
•The VG volume cannot be adjusted on a 7100T only. For all other models, the volume can be
adjusted as explained in this document.
Keep these restrictions in mind if you are implementing MoniPlus2 VG on an ATM that has the hardware
TTS engine.
2.6 Deposit Automation Screens VG Support
Since the check and cash deposit screens included in MoniPlus2 are not part of the host download, but
rather provided locally in the software by NH, NH provides the VG for these screens, in both English and
Spanish. This file is not in the same format as the VG file downloaded from the host. A custom PS
engagement is currently required to make changes to this file.
Contact your NH representative for more information.

MoniPlus2 Voice Guidance Configuration Guide
April 29, 2014 5
3 VG Transaction Processing
This section discusses any differences, or possible differences, that can be included in the messages
between the ATM and the host for VG transactions. Use this information when planning how to
implement VG for your host download.
3.1 Transaction Request Messages
Voice guided transactions can optionally be identified in the transaction request message to the host.
When this feature is desired, there are two methods that can be used:
•Opcode identifier – a value can be placed in the opcode buffer to identify a VG session to the host.
The byte position and character are defined within the VG XML file. Refer to the <afaLang>
Element on page 8 for more information on this option.
•Appended character – a <, or other character, can be added to the end of the transaction request
message to identify a VG transaction to the host. Refer to the <LangOption> Element on page 8 for
more information on this option.
Verify that your host application can support the option you select before you implement either addition
to the transaction request message.
3.2 Transaction Reply Messages
You can specify an audio message to be voiced, or include dynamic data to be voiced, in your transaction
reply message. You can use the Screen Display Update field for this purpose, or you can use the printer
data field in the message. Refer to the Sending VG Data in Authorization Messages section on page 22 for
detailed information on this feature.
3.3 Interactive Transaction Response Messages
When additional information needs to be gathered from the customer, the host can send data to be voiced
in an Interactive Transaction Response (ITR). This dynamic VG data is placed in the Screen Display Data
field of the ITR message. There are two ways to use this field to send VG data to be voiced: Direct Audio
Text and Indirect Audio ID. Refer to the Sending VG Data in Authorization Messages section on page 22
for detailed information on these options.

MoniPlus2 Voice Guidance Configuration Guide
April 29, 2014 6
4 Creating the VG XML File
The VG XML file, AudioGuidanceData.xml,used with MoniPlus2 is similar to the VG XML file used
with NCR APTRA Advance NDC, although MoniPlus2 does not use all of the functions of the NCR
implementation. MoniPlus2 has tried to minimize the complexity and, therefore, has simplified the file.
This section describes the elements and attributes from the AudioGuidanceData.xml file that are used by
the MoniPlus2 application. Additional elements and attributes may be added in the future. The MoniPlus2
VG XML File Elements Quick Reference section on page 33 provides a full list and short descriptions of
these elements and attributes for your reference. The Sample MoniPlus2 VG XML File section on page 35
includes a sample of a full VG XML file.
This section also explains how device orientation instructions are automatically included in the
orientation portion of your VG file and how you can add device orientation information into any of your
instructions that involve devices, such as “Please take your cash.”
Note: The NCR APTRA Advance NDC VG XML file can be used ‘as is’ on MoniPlus2 ATMs and any
NCR VG features not supported by MoniPlus2 will simply be ignored. No schema file is currently
associated with the MoniPlus2 VG XML file, so as long as the file is valid XML, it will be used.
However, a VG XML file written to this MoniPlus2 specification may not work on an APTRA Advance
NDC because NCR validates the VG XML file against their schema file and not all elements required by
NCR are used by MoniPlus2. Refer to your NCR documentation for a list of their required elements.
4.1 Declaration Tag
The VG XML file is XML 1.0 and requires the following declaration as the first line in the file.
<?xml version="1.0" encoding="ISO-8859-1"?>
The encoding declaration is optional, but its inclusion is highly recommended.
4.2 Start and End Tags
The beginning of the VG XML document is identified by the start tag:
<x:NCRAudioGuidance xmlns:x="urn:xsdNCRAudioGuidance">
The end of the document is identified by the end tag:
</x:NCRAudioGuidance>
These tags were mandatory in previous releases, but are now optional.
4.3 VG XML File Elements
The MoniPlus2 VG XML file contains 3 types of elements:
•<Config> −defines options for the VG session.
•<Keyboard> −defines the FDK to numeric keyboard mapping.
•<Audio> −defines the audio messages associated with the screens.
Each of these elements is described in detail in the remainder of this section.