IT guide for Vocollect Voice Systems

VOCOLLECT VOICE SYSTEM:
IT OVERVIEW
Basics for IT Administrators Who
Work with Vocollect Voice-Directed
Systems

Technical Publications and Education
June 2004

II

Copyright © 2004 Vocollect, Inc. All rights reserved.

This document is a basic guide and reference for IT professionals responsible
for maintaining and updating Vocollect voice-directed systems.

Vocollect Voice System: IT Overview, version 3.

Published by Vocollect, Inc.
703 Rodi Road
Pittsburgh, PA 15235
(412) 829-8145
fax (412) 829-0972
http://www.vocollect.com

Printed in the United States of America

June 2004

Talkman® is a registered trademark of Vocollect, Inc.

All other trademarks are the property of their respective owners.

The information in this manual has been carefully checked and is believed to
be accurate. However, Vocollect assumes no responsibility for any inaccuracies
that may be contained in this guide. In no event will Vocollect be liable for
direct, indirect, special, exemplary, incidental, or consequential damages
resulting from any defect or omission in this guide, even if advised of the
possibility of such damages.

In the interest of product development, Vocollect reserves the right to make
improvements in this guide and the products it describes at any time, without
notice or obligation.

This document is intended only for Vocollect representatives and customers and may contain confidential, privileged, or proprietary
material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by
persons or entities other than the intended audiences is prohibited.

VOCOLLECT VOICE SYSTEM: IT OVERVIEW

III

Contents
OVERVIEW...................................................................................................................... 4
WEP USAGE: GENERAL CONSIDERATIONS ...................................................................... 5

SYSTEM ARCHITECTURE .......................................................................................... 6

VOICE SYSTEM COMPONENTS .............................................................................. 10

TALKMAN MANAGEMENT SOFTWARE FILES .................................................. 11
TASK FILES ..................................................................................................................... 13
APPLICATION FILES ........................................................................................................ 14
FILE TRANSFER CODES.................................................................................................... 15
TERMINAL .BIN FILES ..................................................................................................... 20

FTP SERVER.................................................................................................................. 23
RECOMMENDED FILE/DIRECTORY PERMISSION PROCEDURES .......................................... 23
Network Ports: Examples .......................................................................................... 24

VOICELINK ................................................................................................................... 25
PROGRAM FILES ............................................................................................................. 27
Server Applications.................................................................................................... 27
Database.................................................................................................................... 27
Process Tools............................................................................................................. 28
Security Manager ...................................................................................................... 29
Talkman VoiceLink Groups ............................................................................................................................. 29

COMMON FILES DIRECTORY .......................................................................................... 32
Server Applications.................................................................................................... 32
Process Tools............................................................................................................. 33
Security Manager ...................................................................................................... 34
LOG FILES ...................................................................................................................... 34
TASK FILES .................................................................................................................... 34

VOICE SYSTEM MANAGEMENT RECOMMENDATIONS................................. 35

REFERENCES................................................................................................................ 36


4

Overview
The Talkman T2 system is compatible with real-time or batch-
mode warehouse management systems.

During normal operation, the average packet size is less than 100
bytes. However, loading operator voice templates requires much
more bandwidth. It is important to have higher available
bandwidth near the terminal charger assemblies where the
Talkman terminals are stored to adequately support loading
operator voice templates. The maximum available bandwidth
should be utilized for access points located where the Talkman
terminals are stored in order to facilitate loading voice templates.

Once order selection has begun, network traffic activity is typically
very high due to the frequency of data transmissions between the
Talkman terminal and the WMS.

When observing Talkman system data rates with a wireless
network analyzer, the majority of the network traffic generated is
typically seen between 2.0 to 5.5 MB rates. An 802.11b wireless
network analyzer has shown that in most WLAN environments,
network traffic at 11MB is rarely seen coming from the Talkman
terminals. The minimum recommended bandwidth requirement for
the Talkman system is a rate of 2MB for the order selection
process.

Using lower data rates from within the access point configuration
is preferred in order to avoid rate negotiation delays; however, data
rate fallback should be allowed to some extent. For example,
during troubleshooting at one particular installation, access point
data rates were set at 5.5 – 11MB and data errors were well over
50 percent. When the data rates were dropped to 2.0 – 5.5MB, the
data errors dropped to less than 10 percent. This same observation
was made at several sites that were analyzed to correct existing
WLAN issues with the Talkman system. In most instances, a data
rate set to the 2.0 – 5.5MB option is preferable. Setting the data
rate at 2.0MB only or to an auto-negotiated rate range of 1.0 –
11MB may produce undesirable results, but all configurations
should be evaluated for each unique installation. Data retry rates,
CRC errors, and background noise should be evaluated to
determine the best configuration for each specific site.


5

It is important to note that the Talkman terminal does not require
high data throughput rates. However, there may be instances
when other devices or future applications will require higher data
rates and place a greater demand on the WLAN. It is important to
consider other hand-held devices that are or will be used onsite
and evaluate the performance of all wireless devices as
configuration changes are made.

The Talkman system currently supports WEP encryption
technology for many radio card-access point combinations. As
customer requirements drive the direction and scope of wireless
security, the requirements for the Talkman system may change.

WEP Usage: General
Considerations
• Never enter a mix of 40-bit (10 hexadecimal digits) and 128-bit (26
hexadecimal digits) keys in the access point or in the terminal
parameters at one time. WEP requires that all keys be either 40-
bit or 128-bit in both the access point and in the terminal.
• All four access point WEP keys should be defined when WEP is
being used.
• When configuring multiple access points for WEP, all affected
access points should be equivalently configured with regard to
their encryption method, authentication type, and WEP keys. If
these settings are not the same across all access points, terminals
may be prohibited from roaming to a more desirable access point.

For details, see the release notes for the version of code at your
site and Talkman Management Software Online Help.


6

System Architecture
Vocollect systems include hardware components that generate or
affect warehouse network traffic. These components vary,
depending on whether a site uses a batch warehouse management
system (WMS) or a direct interface.

Sites using a batch WMS require the following hardware
components:
• Talkman T2 terminal(s)
• an FTP server
• Voice database server/Talkman Management Software
Workstation(s)
• a host running VISocketODBC
• an MS SQL Server

Network traffic at customer sites may vary widely depending upon
the configuration of these workstations and servers. For example, if
the FTP server resided on the Terminal Manager Workstation, the
network traffic between these components would be eliminated.
Network traffic estimates for customer sites should be modified to
reflect the system architecture specific to that customer.
Note: The WMS is shown as part of the system architecture, but
it is not provided by or maintained by Vocollect. Network traffic
related to a WMS is not estimated and will vary from customer
site to customer site. The illustration shows Talkman VoiceLink,
but the architecture is the same when Talkman Management
Software and another Vocollect product such as QuickPick are
used.


7


8


9

Note: Gray circles in the diagram above indicate independent
WMS activities.


10

Voice System Components
Components of Vocollect’s voice system include:
• Talkman Management Software: this suite includes terminal code,
Terminal Manager, Operator Manager, Template Manager,
Terminal Configuration Manager and Firmware Loader.

Terminal code, Terminal Manager, Terminal Configuration
Manager and Firmware Loader all support the Talkman terminal
and simplify terminal management.

Operator Manager is the application used to create and manage
information about Talkman terminal operators. Files created in
Operator Manager include the operator’s name and password as
well as operator templates. (A template is an utterance that the
operator has trained the terminal to recognize.) Template Manager
is an application that can be used to merge and compress all the
templates in an operator’s file into a single file that is downloaded
to the terminal in a single FTP transaction.
• VISocketODBC is a Windows NT®32-bit application that enables
Talkman terminals to write output data records (ODRs) and to
create lookup tables (LUTs) from an ODBC-compliant database.
VISocketODBC communicates with Talkman terminals over a
socket and with the database(s) through the host computer's
ODBC layer.
• A task is a program that enables the terminal, the terminal
operator and the host to exchange and process information.
• Additional applications and graphical user interfaces, depending
on the site. Talkman VoiceLink, for example, includes client
application programs, a set of database tables and procedures,
and a graphical user interface (GUI).


11

Talkman Management
Software Files
Talkman Management Software installs the following in
C:Program FilesVocollect (default) or the location specified.
:Talkman Management Software
Applications
Executables
Name Size
DispMgr.exe 44KB
Marconi.exe 71KB
oggdec.exe 152KB
oggenc.exe 1036KB
OperMgr.exe 544KB
sox.exe 575KB
Tbuilder.exe 299KB (installs only if special
license key is purchased)
TermCfgMgr.exe 76KB
Tmgr.exe 908KB
TmgrDebug.exe 36KB
TplMgr.exe 244KB
vaffer.exe 44KB
DLLs (application extension)
FWLoad.dll 148KB
license.dll 28KB
Merge.dll 212KB
mVersion.dll 28KB
Compiled HTML help files
VocollectHelpTalkman 1,275KB
ManagementSoftware.chm
ReleaseNotes.chm 136KB


12

Icons
DispMgr.ico; group.ico; 1 to 3KB each
OperMgr.ico; Tbuilger.ico;
TermConfgMgr.ico;
Tmgr.ico; TmgrDebug.ico;
TplMgr.ico
Other
Ctrls.def 1KB DEF file
DevelopersGuide.pdf 2,788KB Adobe Acrobat
Document
LaunchReleaseNotes.bat 1 KB MS-DOS batch file
ogg_header 3KB file
Phonetic.fil 1KB FIL file
Tbuilder.htlp 276KB help file
TemplateFTP.ocx 48KB ActiveX Control
Firmware
config.bat 1KB MS-DOS batch file
config.comd 1KB Windows NT Command
config.fls 1KB FLS file
config.vrg 19 KB VRG file
writecom.exe 40KN application
WriteSock.exe 36KB application
Version-specific .bbi file ~ 130 KB BBI file
(ZEUnnn.nnn.bbi)
Version-language .ffi file ~4,700KB FFI file
(ZEUnnn.nnn.xx_XX_n.ffi)
ziggie.exe 40KB application
Firmware These are the files to be loaded
• boot block (.bbi file) onto the terminal’s flash
memory
• configuration block (.cci
file)
• flash files (.ffi files)
• radio files (.rri files)


13

Task files
Task files are stored in the FTP root directory in a Vocollect-
specific directory structure below the directory you select here.
Note: The directory you enter must be in the FTP server's FTP
root directory path. For instance, if the FTP server’s root
directory is c:inetpubftproot, then select that directory or a
subdirectory of that directory. If, however, you select a
subdirectory, you must create a virtual directory called
Talkman that points to that directory. Consult your FTP
server documentation for more information.

This table contains information about the files associated with a
task. Although some of these files can be opened and edited
using a text editor application, you should only make changes
to them using Talkman Task Builder.

Changes made to these files using a text editor will result in an
irreparably non-functioning task.
File
extension Description
.bak The first time you save a previously saved task, Task Builder
automatically creates a <task name>.bak file based on the <task
name>.tas file. The backup file is a copy of the previously saved
task file. Each time you save a task, the previously saved task file
overwrites the backup file.
.fbk The first time you save a previously saved task, Task Builder
automatically creates a <task name>.fbk file based on the <task
name>.fil file. The backup file is a copy of the previously saved task
phonetic file.
.fil When you save a task, a <task name>.fil is created based on a
default file, phonetic.fil, which contains the default pronunciation and
display strings for Task Builder. When you make changes to the
pronunciation and display strings in a task, the changes are made to
the <task name>.fil.
.qua When you print a task’s prompts and responses to a file (using File |
Print), Task Builder automatically creates a <task name>.qua file.
Each time you print a task’s prompts and responses to a file, Task
Builder overwrites any previously saved <task name>.qua file. This
type of file is not used to run a task.
.rcm When you save a task created in versions of Task Builder released
prior to TBR001, Task Builder automatically creates a <task
name>.rcm file. This file is required only for voice systems using the


14

DTW speech recognizer, which was replaced with the BlueStreak
speech recognizer in Talkman Management Software T2 version 1.0
and Talkman Management Software OPEN version 8.0.
.str When you print a task’s vocabulary words and data strings to a file
(using File | Print), Task Builder automatically creates a <task
name>.str file. Each time you print a task’s vocabulary words to a
file, Task Builder overwrites any previously saved <task name>.str
file. This type of file is not used to run a task.
.tas When you save a task for the first time, a <task name>.tas file is
created. A task’s .tas file is a text file that contains both the
information needed to generate the task diagram on the screen and
the information a Talkman terminal needs to run the task.
.txt When you create an FTP-type LUT, Task Builder automatically
assumes it has a .txt extension.
.vcf Not an actual Task Builder file. A .vcf file contains the configurable
parameters for the Talkman terminal. Some of the parameters in a
.vcf file affect how the terminal travels through the task. For more
information on .vcf files and configurable parameters, refer to the
Talkman online documentation at your site.

Application files
Extension Location Description Application
.bt1 C:Inetpubftproottalkman single template file Template
Manager
.mt1 C:Inetpubftproottalkman multiple template Template
files (.bt1s) for an Manager
operator, com-
pressed and merged
into a single file
.eMb C:Inetpubftproottalkmantask default file of training Task Builder
prompts for multiple-
digit utterances; can
be customized
.vog C:Inetpubftproottalkmantask lists all Terminal Terminal
Manager groups Manager
.voo C:Program file folder where Template
FilesVocollectTalkmanSoftware individual templates Manager
appsOperImages are stored
.vot C:Inetpubftproottalkmantask file defining all Template
operators in a given Manager
group w/spoken
name for each
operator


15

File transfer codes
Vocollect has created the following codes, returned when the
task encounters a .receive function on a link condition to
indicate the result of a transmission.

Code Description Details

0 TRANSFER_IN_PROGRESS Internal use only

1 TRANSFER_SUCCESS File transfer was successful

-100 TRANSFER_FAILURE File transfer failed.
Mechanism for file transfer
broke. This error should
never occur.
-101 TRANSFER_SYSTEM_ERR File transfer failed. Internal
system error such as
unable to allocate memory.
This error should happen
very infrequently, if ever.
-102 TRANSFER_LOGIN_ERR File transfer failed. Unable
to connect to remote
system. Bad socket login.
-103 TRANSFER_FILE_NOT_FOUND_ERR File transfer failed. Unable
to get file from FTP or
HTTP (future) server, file
does not exist.
-104 TRANSFER_NETWORK_NOT_AVAIL_ERR File transfer failed. No
network available. This may
happen when the radio
network is down, or the
radio is out of range.
-105 TRANSFER_TIMEOUT_ERR Socket transfer failed.
Time-out period exceeded.
-106 TRANSFER_SYSTEM_IN_STANDBY_ERR Comm received file transfer
command when terminal
was sleeping. Comm
refused to issue transfer
command because the
terminal was sleeping.
-107 TRANSFER_NO_CONNECTION_ERR File transfer failed. Socket,
connection socket, or
TELNET connection was
lost, thereby forcing


16

terminal to fail the transfer.

-108 TRANSFER_TELNET_NO_DATA_ERR TELNET transfer failed.
Terminal failed to get data
from TELENT server as
expected.
-109 TRANSFER_TELNET_NO_MATCH_ERR TELENT transfer failed.
Terminal got unrecognized
data from the TELNET
server, therefore no screen
match occurred.
-110 TRANSFER_ABORTED Socket transfer aborted by
terminal.
-111 TRANSFER_CSOCKET_FILE_ERR Continuous socket transfer
failed. Internal error. Error
should occur rarely, if ever.
-112 TRANSFER_CSOCKET_FATAL_SEND_ERR Continuous socket transfer
failed. Terminal was
unable to send data to
socket host.
-113 TRANSFER_CSOCKET_FATAL_READ_ERR Continuous socket transfer
failed. Terminal failed to
receive data from socket
host.
-114 TRANSFER_CSOCKET_OUT_OF_SYNC_ERR Continuous socket transfer
failed. Cannot complete
ODR or LUT request.
Already doing an ODR or
LUT request, and can only
do one at a time.
-115 TRANSFER_HOST_NOT_REACHABLE File transfer failed. Unable
to reach host, ping failure.
FTP, HTTP (future),
sockets, and TELNET. Also
see -104
TRANSFER_NETWORK_N
OT_AVAIL_ERR
-116 TRANSFER_CONFIRMATION_ERR Socket transfer failed. Bad
ODR confirmation byte.
-117 TRANSFER_INSUFFICIENT_FILE_MEM File transfer failed (FTP or
HTTP (future)). Not enough
memory in terminal file
system to store file.
-118 TRANSFER_FILE_SIZE_IS_ZERO FTP transfer failed. Size of
file is zero bytes, file must
contain some data.
-119 TRANSFER_FILE_SIZE_ERR File transfer failed. FTP of
voice templates only.


17

Terminal sent template to
FTP host, file size on
terminal does not match
size of FTP server. If sizes
do not match, transfer
is failed.
-120 TRANSFER_ACCESS_VIOLATION FTP transfer failed. Unable
to send file to FTP host,
terminal does not have
access privileges to write
file to FTP host.
-201 TRANSFER_TELNET_OPEN_BAD_HOST_NAME_ERR TELNET host name is
NULL or was not found in
the host file.
This error can happen if
task contains no TELENT
name or a bad TELNET
name.
-202 TRANSFER_TELNET_OPEN_CREATION_OF_SOCKET_FAIL Unable to initialize socket
ED_ERR to TELNET server. This
error should never happen.
-203 TRANSFER_TELNET_OPEN_CONNECT_FAILED_ERR TELNET tried to make a
connection to the TELNET
host. The connection failed.
This error may happen
occasionally, especially if
TELNET server is having
problems.
-204 TRANSFER_TELNET_LOST_CONNECTION_TO_HOST_ERR Had a connection to the
TELNET server, it was lost.
The connection was closed
from the server side.
-205 TRANSFER_TELNET_WRITE_TTY_ERR The TELNET client process
was not able to write data
to the pipe that feeds the
data to the VT220 process.
The pipe is full or some
other error occurred. The
VT220 process may have
crashed. This error is very
unlikely.
-206 TRANSFER_TELNET_WRITE_NET_ERR The TELNET client process
was not able to write data
to the TELNET server;
possibly the connection
was lost, closed by the
server.
-207 TRANSFER_TELNET_WRITE_TELSCAN_ERR The TELNET client process
was not able to
write telscan (special telnet


18

control sequences) data to
the TELNET server;
was lost, closed by the
server.
-209 TRANSFER_TELNET_READ_TTY_ERR The TELNET client process
was not able to read the
pipe that contains the data
that gets sent to the telnet
server. Possibly indicates
that the TELNET session
manager has crashed.
-210 TRANSFER_TELNET_READ_NET_ERR The TELNET client process
was not able to read data
from the telnet server;
was lost; closed by the
server.
-213 TRANSFER_TELNET_UNKNOWN_ERR In the client TELNET
process, a path was taken
in the software that should
never be taken. In both
cases in which this error
can occur, the software fell
through to a default case
statement in a switch
statement. In
both situations the software
should never fall through to
that default statement. This
error is extremely unlikely.
-214 TRANSFER_TELNET_MANAGER_TO_VT220_SEND_ERR The TELENT session
manager tried to send a
message to the VT220
process. The send failed,
possibly because the
VT220 process crashed.
This error is very unlikely.
-215 TRANSFER_TELNET_SOURCE_FILE_OPEN_ERR The TELNET session
manager tried to open the
file that contains the data
that is sent to the TELNET
host. The file open failed.
This error is very unlikely.
-216 TRANSFER_TELNET_MANAGER_TO_CLIENT_WRITE_ERR The TELNET session
manager was not able to
write data to the data pipe
that goes to the TELNET
client process. The pipe
may be full or something
bad has happened to the


19

client telnet process.

-217 TRANSFER_TELNET_SOURCE_FILE_READ_ERR The TELNET session
manager got a read error
when reading the file that
contains the data that gets
sent to the TELNET server.
This error very unlikely.
-218 TRANSFER_TELNET_NOT_IN_SEND_SYNCH_ERR The TELNET session
manager got a LUT request
without first getting an ODR
request. The TELNET
process is out of synch, or
in other words the TELNET
processes need to send
data to the TELNET server,
before receiving data from
the TELNET server.
-219 TRANSFER_TELNET_NOT_EXPECTING_COMMAND_ERR The TELNET process
received a TELNET
command while it was still
in the process of starting or
initializing. The session
manager should not receive
any TELNET commands
from file manager until the
TELNET
process is fully up and
executing.
-220 TRANSFER_TELNET_PMS_OR_UNEXPECTIVE_ERR The TELNET session
manager got a PMS error
or some other unknown
error. The session manager
is closing and all TELNET
processes are being closed
down.
-221 TRANSFER_TELNET_VT220_START_ERR The VT220 process failed
to start.
-222 TRANSFER_TELNET_NORMAL_SHUTDOWN Normal TELENT shutdown
message. Used internally in
the TELNET processes.
This transfer message
should never get back to
the file manager and dialog.
If it does then something
bad has happened.
-999 Not used


20

Terminal .bin files
The Terminal Manager suite uses the local files system to
preserve information entered by the user between invocations of
the application(s). Primarily, the information maintained
describes each individual terminal as well as any group
information specified by the shift supervisor.

The set of terminals known to Terminal Manager can be
determined by examining the file VocTerm.ini in the
application’s working directory (by default, C:Program
FilesVocollectTalkmanSoftwareapps). Each entry in this
file specifies the serial number of a terminal known to Terminal
Manager.

Each terminal found in the VocTerm.ini file has a
corresponding data file, <TermSerialNum>.bin, located in the
TERM subdirectory of the working directory for the application
(typically, a default of C:Program
FilesVocollectTalkmanSoftwareappsTERM is used). The
type of information stored within this file includes:
• The terminal serial number
• Name of the terminal (as assigned within Tmgr.exe)
• Name of the task currently loaded on the terminal
• The name of the operator currently using that terminal
• The terminal group to which the terminal belongs


21

The Terminal Manager suite also permits users to organize
terminals into groups. Each terminal group has a set of
properties that propagates to each of the terminals with that
group. These properties include:
• The name of the group
• The task to be loaded on each of the terminals in the group
• A set of Host definitions that allows a symbolic name to be used
within a task instead of requiring that an IP address be specified.
• A set of Service definitions that allow a symbolic name to be used
within a task, instead of requiring that a port number be specified.
• A flag to indicate if the terminal is in Supervisor mode (which
allows many operations to be performed immediately, instead of
waiting for the terminal to go off-air).

Group information is stored using a structure similar to the
terminal information. That is, an initialization file
(VocGroup.ini) is used to specify the set of groups known to
Tmgr.exe. Additional information is stored within group specific
files located in a subdirectory of the application working
directory (the GROUP subdirectory).

Therefore, for a given Terminal Manager installation, the
following describes the set of files used as persistent storage:

APP_WORKING_DIRECTORY
• VocTerm.ini
• VocGroup.ini

APP_WORKING_DIRECTORYTERM
• *.bin files (* expands to the terminal serial number)

APP_WORKING_DIRECTORYGROUP
• *.vhr (Host file - * expands to group name)
• *.vsr (Services file - * expands to group name)


22

Although the file structure described above is valid for all
Terminal Manager derivatives, use of TmgrService.exe
complicates matters significantly because multiple copies of the
files exist. That is, TmgrService.exe maintains the master copy
of these files and provides each of the clients with a copy of the
files to use locally. This copy is updated each time the Tmgr.exe
client connects to the service.

Since both the server (TmgrService.exe) and the client
(Tmgr.exe) components may be installed on the same machine,
care must be taken to ensure that there is no contention when
accessing these data files. Therefore, TmgrService.exe creates a
separate subdirectory in which all data files are stored.
Typically, this subdirectory is rooted at the working directory for
the Tmgr.exe application and is named TmgrService. (By
default, TmgrService.exe data files are placed in C:Program
FilesVocollectTalkmanSoftwareappsTmgrService.
However, this default can be overridden using the registry key
[HKEY_LOCAL_MACHINE]SoftwareVocollectTmgrTmgrS
erviceWorkingDir.)

To facilitate upgrading from an earlier [non-client/server based]
version of Tmgr.exe, TmgrService.exe supports the one-time
import of data from an alternate location. This is accomplished
through the following process:
1. During installation, a registry key (ImportDir) is initialized to
point to the location in which Tmgr.exe was installed (i.e. the
location from which the data files should be imported).
2. Upon boot up, the TmgrService.exe application will look for its
data files locally. If these data files do not exist, it reads the value
of the ImportDir key from the registry. If this registry key has a
value, TmgrService.exe will attempt to import the data files located
in that directory. The process of importing these data files has the
side effect of creating a copy in the default directory for the
TmgrService.exe application.
3. In all cases, TmgrService.exe will then delete the ImportDir key
from the registry.

Therefore, data will only be imported only once, on the first
activation of TmgrService.exe. From that point forward,
TmgrService.exe maintains a master copy, and each of the
clients contains a local, read-only copy.


23

FTP Server
Terminal Manager requires three parameters to log on and begin
communicating with the FTP server: host name or IP
address (Host), user name (Username), and password
(Password). When Terminal Manager is opened for the first time
after it is installed, a dialog box automatically displays text boxes
for entering this information.

When you change any of these settings, Terminal Manager checks
the FTP server for the existence of the support file directory
structure. If the directories do not exist, Terminal Manager creates
them.

Recommended file/directory
permission procedures
A user without administrator privileges can
• load a task
• load an operator (no access to cached data file)
• create and delete a terminal group
• move a terminal into a group
• change to and from supervisor mode
• change FTP host
• initiate a firmware load
• archive terminals to a desktop
• rename a terminal
• add notes to terminal properties
• change Display Manager host and activate Display Manager

Administrator privileges are required to
• start and stop TmgrService.exe
• save changes made within TermCfgMgr.exe
• perform actions in Template Manager (the GUI will display for
users without administrator privileges, but administrator
privileges are required to perform any actions)
• log debug information or display mode information

24

Network Ports: Examples
The following sample of a port access control list (ACL) is
specific to AironetCisco.

Assume192.168.0.0 is the network on which Terminal
Manager exists, and 192.168.12.0 is the network to which
the Talkman terminals connect.

IP access—list extended voc—sample

permit pim any any
permit igmp 192.168.0.0 0.0.0.255 224.0.0.0 0.255.255.255
permit igmp 192.168.0.0 0.0.0.255 225.0.0.0 0.255.255.255
permit tcp 192.168.12.0 0.0.0.255 192.168.0.0 0.0.0.255 range 15000 17001
permit tcp 192.168.12.0 0.0.0.255 range 15000 17001 192.168.0.0 0.0.0.255
permit tcp any 192.168.0.0 0.0.0.255 eq 8000
permit tcp any 192.168.0.0 0.0.0.255 eq 8080
permit tcp any 192.168.0.0 0.0.0.255 range 5677 5680
permit tcp any 192.168.0.0 0.0.0.255 eq 999
permit tcp any 192.168.0.0 0.0.0.255 eq 5000
permit tcp any 192.168.0.0 0.0.0.255 eq telnet
permit tcp any any eq www
permit udp any any eq bootps
permit udp any any eq bootpc
permit tcp any 192.168.0.0 0.0.0.255 eq ftp
permit tcp any 192.168.0.0 0.0.0.255 eq ftp-data
permit tcp any 192.168.0.0 0.0.0.255 eq echo
permit udp any 192.168.0.0 0.0.0.255 eq echo
permit tcp any 192.168.0.0 0.0.0.255 eq daytime

Sample VLAN Configuration:

On particular VLAN interface:

interface Vlan100
description VOC_SAMPLE

ip access-group voc-sample in

ip pim query-interval 3600
ip pim dense-mode
ip igmp last-meMber-query-interval 65535
ip igmp static-group 225.0.0.10
ip igmp query-interval 3600


25

VoiceLink
The VoiceLink installation program verifies the operating system
and service packs. If both are compatible with the Talkman
VoiceLink system, it begins the installation. Otherwise, it displays
one of these error messages:
• "Windows 2000 detected, did not detect at least Service Pack 2."
The service pack of Microsoft Windows 2000 you are running is not
compatible with this installation. You must have at least SP2.
• "Windows NT4 detected, did not detect at least Service Pack 6." The
service pack of Microsoft Windows NT 4.0 you are running is not
• "Windows XP detected, did not detect at least Service Pack 1." The
service pack of Microsoft Windows XP you are running is not
• "Windows 2000, Windows NT4, Windows XP or Windows 98 not
detected." Talkman VoiceLink does not support the detected OS
platform.

The installation will start the exit sequence or you can click Cancel
to stop.

If you try to install the server applications on a machine running
the Microsoft Windows NT operating system, you will receive this
error message: "You cannot install the Server Applications on this
machine. The Server Applications are only compatible with
Windows 2000 and Windows XP."

You will need to know the following things for a complete
installation:
• If installing with Microsoft SQL Server authentication, you must
use an account that has administrator privileges in Microsoft SQL
Server. You cannot use the viadministrator account for this
purpose, because viadministrator gets created during the
installation process.
• If installing with Microsoft SQL Server authentication, Microsoft
SQL Server and Agent services should be logged in through a
network account. Otherwise, users will never be able to send
anything to print over the network.
• Set the Microsoft SQL Server model database must use the full—
not simple—recovery model, because the Talkman VoiceLink
database requires this and will base itself on the model database.


26

• Your product identification number, a 20-digit number printed on
a label on the jewel case from your Talkman VoiceLink installation
CD, for the User Information dialog box
• The modules you want to install, for the Select Modules dialog box
• The system name, for the System Name dialog box
• The type of installation, for the Select Installation Type dialog box
• The features you want to install, for the Select Features dialog box
• The directories in which you want to install executable and
common files, for the Executable and Common Files Directories
dialog box
• The directory in which you want Talkman VoiceLink to write and
store log files, for the Log File Directory dialog box
• The directory in which you want to store tasks for Talkman
terminals, for the Task File Directory dialog box
• The directory to which you want Talkman VoiceLink to import and
export files, for the Import/Export File Directory dialog box
• The directory to which you want Talkman VoiceLink to back up the
database, for the Database Backup Directory dialog box
• The server and database you want Talkman VoiceLink to use, and
the authentication type you want to use while installing the
database, for the Database Installation Connection Properties
dialog box. To be able to print data in Talkman VoiceLink, you
must install the database on the same machine as the server
applications.
• How you want the Microsoft SQL Server jobs to log in to the
database, for the SQL Server Job Properties dialog box
• How you want the server applications to connect to the database,
for the Server Application Connection Properties dialog box. To be
able to print data in Talkman VoiceLink, you must install the
database on the same machine as the server applications.
• How you want the server applications to connect to the Microsoft
Windows NT machine, for the Server Application Login Properties
dialog box
• The ports you want the server applications to use to communicate
with the Talkman terminals, for the Server Application Settings
dialog box
• How you want the process tools to connect to the database, for the
Client Application Connection Properties dialog box
• What configurable options you want to install, for the Configurable
System Settings dialog box


27

• What regions you want to use in your system. After installation,
you must add regions to the system before it can import any data.
• How to manage the import process. Talkman VoiceLink copies the
WMS' exported data to the processing folder, an operation that
succeeds even if the file is still transferring. The import then
attempts to process the partially written file. Therefore, someone at
the customer site must ensure that the WMS exports files under a
name that Talkman VoiceLink will not import, then rename it when
the WMS export process completes, so that Talkman VoiceLink can
import it.

Program Files
Server Applications
• [C:Program Files]VocollectTalkmanVoiceLink
ServerApplicationsVVLPrintManager.exe
ServerApplicationsVVLPrintManagerConfiguration.txt
• [C:Program
Files]VocollectVISocketODBCVISocketODBC.exe
• [C:Program Files]VocollectVISocketODBC
VISocketODBCConfiguration.txt

Database
DatabaseCreateDB.txt
DatabaseDropDB.txt
DatabaseInstall.Log
DatabaseInstallFeatures.txt
DatabaseInstallInstallFeaturesSP.txt
• [C:Program
Files]VocollectTalkmanVoiceLinkDatabaseiscVocollectVoice
Link.sql
DatabaseprDeleteInstallFeatures.sql


28

DatabaseprInstallFeatures.sql
DatabaseSql.log
DatabaseUninstallInstallFeaturesSP.txt

Process Tools
ProcessToolsVIBAssignments.dll
ProcessToolsVIBAuthorizedWork.dll
ProcessToolsVIBContainers.dll
ProcessToolsVIBDeliveryLocations.dll
ProcessToolsVIBItems.dll
ProcessToolsVIBOperators.dll
ProcessToolsVIBPickContainers.dll
ProcessToolsVIBRegions.dll
ProcessToolsVIBUIAssignments.dll
ProcessToolsVIBUIAuthorizedWork.dll
ProcessToolsVIBUIContainers.dll
ProcessToolsVIBUIDelivery.dll
ProcessToolsVIBUIItems.dll
ProcessToolsVIBUILaborDetails.dll
ProcessToolsVIBUILaborHistory.dll


29

ProcessToolsVIBUILocations.dll
ProcessToolsVIBUINotifications.dll
ProcessToolsVIBUIOperators.dll
ProcessToolsVIBUIOptions.dll
ProcessToolsVIBUIPickContainers.dll
ProcessToolsVIBUIPicks.dll
ProcessToolsVIBUIPrinters.dll
ProcessToolsVIBUIRegions.dll
ProcessToolsVIBUIShorts.dll
ProcessToolsVIUIBusiness.dll
ProcessToolsVPS.exe

Security Manager
SecurityManagerSecurityManager.exe

Talkman VoiceLink Groups
Talkman VoiceLink creates three groups by default:
• VoiceLinkAdmin
Talkman VoiceLink creates the viadministrator login by
default, with a password of viadministrator. This login
belongs to the Administrator group.
• VoiceLinkSupervisor
• VoiceLinkUser

The chart that follows lists the actions that can be
performed in Talkman VoiceLink and which groups have
permission to perform the actions.


30

Action VoiceLink
Admin Supervisor User
Add authorized work types x x
Add container configurations x x
Add delivery locations x x
Add locations x x
Add items x x
Add operators x x
Add printers x x
Add values to the delivery locations list x x
Apply delivery locations to existing x x
assignments
Change assignments x x
Change container configurations x x
Change delivery locations x x
Change items x x
Change locations x x
Change operators x x
Change printers x x
Change the database x x
Change the delivery location mapping field x x
Change quantities picked x x
Change quantities to pick x x
Change variable weights x x
Change window configurations x x
Create chase assignments x x
Delete authorized work types x x
Delete container configurations x x


31

Delete delivery locations x x
Delete items x x
Delete locations x x
Delete notifications x x
Delete operators x x
Delete printers x x
Group assignments x x
Load window configurations x x x
Mark out reported shorts x x
Print chase labels x x x
Print container labels x x x
Rebuild delivery locations x x
Resequence assignments x x
Sign operators off x x
Split available assignments x x
Split in-progress assignments x x
Ungroup assignments x x
Unlock resequencing x x
View assigned shorts x x x
View assignments x x x
View assignments' operator histories x x x
View container configurations x x x
View containers x x x
View containers' histories x x x
View delivery locations x x x
View items x x x
View labor history details x x x
View labor history summaries x x x
View locations x x x


32

View marked out shorts x x x
View notifications and their details x x x
View operators x x x
View operators' authorized work types x x x
View picks x x x
View picks' histories x x x
View printers x x x
View regions x x x
View reported shorts x x x
View variable weights x x x

For details about changing user groups, see Security Manager in
Talkman VoiceLink Online Help.

Common Files Directory
By default, Talkman VoiceLink places all common files in
c:program filescommon files. To change this directory, perform
these steps:
1. In the Common Files section of the dialog box, click Browse.
The Talkman VoiceLink 1.1 Setup dialog box appears.
2. Browse to the directory where you want to place the common files.
3. Click OK.
The new directory appears in the Common Files section of the
dialog box.

Server Applications
• [C:Program FilesCommon
Files]VocollectServicesVIServiceConfiguration.exe
Files]VocollectServicesVocollectService.dll
Files]VocollectServicesVocollectServiceEx.dll
Files]VocollectTalkmanVoiceLinkVIBPrinters.dll


33

Files]VocollectTalkmanVoiceLinkVIBusiness.dll
Files]VocollectTalkmanVoiceLinkVIConnection.dll
Files]VocollectTalkmanVoiceLinkVIControls.ocx
Files]VocollectTalkmanVoiceLinkVIDatabase.dll
Files]VocollectTalkmanVoiceLinkVIDLLManager.dll
Files]VocollectTalkmanVoiceLinkVIDOptions.dll
Files]VocollectTalkmanVoiceLinkVINotifications.dll

Process Tools
Files]VocollectTalkmanVoiceLinkVIBLocations.dll
Files]VocollectTalkmanVoiceLinkVIBPicks.dll
Files]VocollectTalkmanVoiceLinkVIBPrinters.dll


34

Security Manager

Log Files
Talkman VoiceLink places all log files in c:logfiles. To change
this directory, perform these steps:
1. Click Browse.
The Talkman VoiceLink 1.1 Setup dialog box appears.
2. Browse to the directory where you want to place the log files.
3. Click OK.
The new directory appears the dialog box.

Task Files
Talkman VoiceLink stores task files in the FTP root directory. It
builds a Vocollect-specific directory structure below the directory
you select here. See Task Files.


35

Voice System Management
Recommendations
Vocollect recommends the following:
• Create backups for all operator files, including voice templates.
Store the backups in a location different from that of the original
files. This eliminates the need for operators to retrain voice
templates if the original files are deleted.
• Make sure that any changes in other parts of the system are
reviewed in relationship to voice system components.
• Schedule training sessions for users when changes affect day-to-
day procedures.
• Make sure those who work with the voice system know about
online help and other resources and how to use such reference
material.
• Make sure appropriate training is scheduled for new employees.
• Store Vocollect system CDs appropriately. Make sure that
installation key information (typically on the CD or its jewel case)
is stored.
• Create a file with the information required for installation— for
example, IP addresses and subnet masks—and update it as
needed.
• Periodically review backup, archive and recovery procedures.
• Review the release notes that accompany every Vocollect voice
system release if your site plans to install the new release. New
features are summarized in the New Release Highlights section.


36

References
For more information, see the following documents.

Online Help

All online help documents include content listings and an index
and can be searched by key words.

• Talkman Management Software Online Help — Installs with
Talkman Management Software package; separated into Software
and Hardware sections; Hardware section is accessed through
button on navigation bar. Information about Talkman OPEN
systems is accessed from topics by clicking on the Talkman OPEN
terminal image. A customer version of the T2 configurable
parameters chart is included. Accessible from any TMS application
by clicking Help menu item. Provides details on regularly
performed procedures.

• Talkman Task Builder Online Help — Installs with Talkman Task
Builder versions 2.1 and 2.2. A tutorial, Overview for Experienced
Users, is for developers who have worked with earlier versions of
the application and is a quick introduction to the new graphical
user interface. The tutorial is accessed through a button on the
navigation bar. The online help that accompanies version 2.1
includes a .pdf version of The Developer’s Guide, which can be
accessed through a button on the navigation bar and downloaded.
In the online help with version 2.2, material from The Developer’s
Guide is incorporated in the online help package. Users access the
information by clicking on a special icon displayed in the related
topic.

• QuickPick Online Help — An online help package that installs with
QuickPick and contains information about QuickPick and related
applications. This online help supplements information in
Talkman Task Builder Online Help.

• VISocketODBC Online Help — Installs with VISocketODBC and
contains specific information about using the application as a
service or in stand-alone mode. Information on how to configure
the application is included.

• VoiceLink Online Help — Installs with VoiceLink. Information
about installing the VoiceLink package can be accessed from the
Installation Wizard screens as the package is installed; click the
More Information button to see information related to the
currently displayed screen. This help package includes details on
day-to-day operations, including viewing and changing data


37

related to assignments, shorts, containers, regions and a number
of other features.

Release Notes

Release Notes are included with every Talkman Management
Software, QuickPick, VoiceLink, Talkman Task Builder and
VISocketODBC release. In 2003, Technical Publications began
issuing release notes in the same format as online help. Release
Notes published after January 2003 include a table of contents
and index and can be searched by key word. Release Notes
include a New Release Highlights section that lists new features
and changes from previous versions, limitations and general
considerations; a Previous Releases section that lists basic
information about prior releases; and an All Versions section
that provides basic information about procedures, hardware
requirements and getting help. Release Notes can be opened
from the CD used to install software and can be opened for
review from the folder to which the application or package was
installed.

Socket Interface Guide

This .pdf document is a reference for establishing a socket
interface between the Talkman terminal and the WMS. It is
available on request.

Product Inserts

Inserts that are packed with every Vocollect hardware product
shipped. These fliers include technical information, basic
information about a product’s use and maintenance, any
required regulatory compliance statements and any relevant
testing information.

Pocket Guides

One-sheet references for operators that are designed to be
folded and placed in a pocket. The guide outlines how to use the
terminal keypad to perform procedures, lists control words and
includes the basic task dialog for a sit. Pocket Guides are
created on request for any site and are low-cost, effective
training aids. Technical Publications writes the guide and sends
an electronic copy to the site engineer or senior project
manager. The electronic copy is given to the customer, who can
print or photocopy as many copies as are needed, whenever
needed.

IT guide for Vocollect Voice Systems

Recomendados

Recomendados

Mais conteúdo relacionado

Semelhante a IT guide for Vocollect Voice Systems

Semelhante a IT guide for Vocollect Voice Systems (20)

Último

Último (20)

IT guide for Vocollect Voice Systems