RINST PDF Amanda Work Group Installation 2 7 Xx

Work_group_install_7-xx Work_group_install_7-xx

User Manual: PDF T E X T F I L E S

Open the PDF directly: View PDF PDF.
Page Count: 376 [warning: Documents this large are best viewed by clicking the View PDF Link!]

Installing
AmAndA@Work.Group/
DOS
Version 7.xx
Installer’s Guide Edition 12/01/01
ii Installing Amanda@Work.Group/DOS
Copyright and Trademark Notices
Copyright 1992–2002 The Amanda Company. All Rights Reserved. This
guide and the software described herein are copyrighted with all rights
reserved. No part of this publication may be reproduced, transmitted, stored
in a retrieval system, or translated into any language in any form by any
means without the prior written permission of The Amanda Company.
Amanda and Amanda@ are registered trademarks and sales trademarks of
The Amanda Company. Other brand names and product names mentioned in
this manual are trademarks or registered trademarks of their respective
owners.
Limited Warranty on Software
The Amanda Company warrants the media on which the software is recorded
to be free from defects in materials and faulty workmanship for a period of
90 days from the date the software is delivered. If a defect in the media
should occur during this period, you may return the media to The Amanda
Company and The Amanda Company will replace the media without charge.
THE AMANDA COMPANY MAKES NO WARRANTIES (OTHER
THAN THOSE SET FORTH ABOVE) TO ANY PERSON OR ENTITY
WITH RESPECT TO THE PRODUCT OR ANY DERIVATIVES
THEREOF OR ANY SERVICES OR LICENSES AND DISCLAIMS ALL
IMPLIED WARRANTIES, INCLUDING WITHOUT LIMITATION
WARRANTIES OF MERCHANTABILITY, PERFORMANCE,
NONINFRINGEMENT, AND FITNESS FOR A PARTICULAR
PURPOSE. THE AMANDA COMPANY WILL NOT BE LIABLE FOR
ANY BUG, ERROR, OMISSION, DEFECT, DEFICIENCY, OR
NONCONFORMITY IN ANY SOFTWARE. THE SOFTWARE IS
LICENSED “AS IS,” AND THE PURCHASER ASSUMES THE ENTIRE
RISK AS TO ITS QUALITY AND PERFORMANCE.
IN NO EVENT AND NOTWITHSTANDING ANY DOCUMENT,
REPRESENTATION, OR OTHERWISE, SHALL THE AMANDA
COMPANY BE LIABLE TO YOU FOR DIRECT, INDIRECT, SPECIAL,
INCIDENTAL, CONTINGENT, OR CONSEQUENTIAL DAMAGES,
iii
INCLUDING DAMAGES FROM LOSS OR CORRUPTION OF DATA,
INTERRUPTED USE, LOST PROFITS, COST OF PROCURING
SUBSTITUTE GOODS, TECHNOLOGY OR SERVICES, EVEN IF THE
AMANDA COMPANY OR AN AUTHORIZED AMANDA COMPANY
DEALER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES. YOU AGREE THAT THE AMANDA COMPANY’S
LIABILITY ARISING OUT OF CONTRACT, NEGLIGENCE, STRICT
LIABILITY, WARRANTY, OR OTHER LEGAL OR EQUITABLE
THEORY SHALL NOT EXCEED ANY AMOUNTS PAID BY YOU FOR
THIS PRODUCT. Any written or oral information or advice given by
Amanda Company dealers, distributors, agents, or employees will in no way
increase the scope of this warranty, nor may you rely on such oral or written
communication. Some states do not allow the exclusion or limitation of
implied warranties or liability for incidental or consequential damages, so
the above limitation or exclusion may not apply to you. This warranty gives
you specific legal rights, and you may also have other rights which vary
from state to state. This Agreement shall be governed by the laws of the
State of California without regard to the conflicts of laws or provisions
thereof.
Fraudulent Usage Advisory
Although the Amanda software is designed to resist fraudulent usage,
including unauthorized access to a long distance network, no product,
including the Amanda software, is able to prevent such unauthorized usage.
The Amanda software is likewise unable to prevent such uses as may
constitute an invasion of privacy or other tort. THE AMANDA COMPANY
MAKES NO EXPRESS OR IMPLIED WARRANTY AGAINST
UNLAWFUL OR UNAUTHORIZED USE OF YOUR AMANDA
SYSTEM OR ITS CAPABILITIES AND HEREBY DISCLAIMS ALL
LIABILITY ARISING FROM SUCH USE. YOU AGREE TO
INDEMNIFY, DEFEND, AND HOLD THE AMANDA COMPANY
HARMLESS FOR ANY UNAUTHORIZED OR FRAUDULENT USE OF
YOUR LICENSED AMANDA SOFTWARE.
THE AMANDA COMPANY
13765 ALTON PARKWAY, UNIT F
IRVINE, CA 92618
TELEPHONE (949) 859–6279 FAX (949) 859–4380
iv Installing Amanda@Work.Group/DOS
Conventions
This manual uses the following terminology and conventions:
Assumptions
This guide is written for an installer who is familiar with PCs and
understands telephone switching systems. It assumes that you know
something about the following:
• How to safely open a personal computer to install or remove boards.
For example, the computer must be turned off while you are install-
ing and removing boards.
• Computer terms, such as serial port, parallel port, and DOS prompt.
• How to identify basic components of a personal computer, for exam-
ple, motherboard, I/O controller, video card, I/O ports, modem, and
so forth.
• How to connect the monitor, keyboard, and power to the computer.
• How to use DOS commands, such as CD, TYPE, COPY, and EDIT.
Amanda The name by which this manual refers to the
Amanda@Work.Group/DOS system to make
reading about the system easier. Because of
the name Amanda, the system is also referred
to as “she.”
caller Someone who calls into Amanda. A caller of-
ten obtains information, leaves a message for
someone, and/or provides information. Be-
cause Amanda is referred to as “she,” callers
and users are referred to as “he.”
user Someone with an extension that Amanda
transfers calls to and/or stores messages for. A
user can access Amanda to play, delete, and
send messages as well as set personal options
such as Do Not Disturb.
fixed-space type This guide displays information that you must
type and messages from Amanda in fixed-
space type.
v
• How to get to the CMOS settings and make changes.
• Telephony terms, such as station side, CO, single-line, hunt group,
pilot number, pickup group, coverage path, hookflash, call forward
ring-no-answer, call forward busy, DTMF, and tone patterns.
• The difference between RJ-11 and RJ-14 connectors.
• The difference between the functions of the telephone switching sys-
tem and Amanda.
• How to use a butt set or line monitor to observe test calls.
If you are unfamiliar with any of the above, please consider attending one of
our regularly scheduled training seminars. Please contact our sales
department for more information on dates and cost.
Depending on how you purchased our product or what voice boards you are
installing, parts of this guide may not pertain to you. For example, if you
purchased a turnkey solution comprised of Amanda preloaded onto a PC,
you can skip all sections regarding the system requirements and the
installation of the voice boards and Amanda software.
vi Installing Amanda@Work.Group/DOS
Contents
Copyright and Trademark Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
Limited Warranty on Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
Fraudulent Usage Advisory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iv
Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iv
Chapter 1:
Introducing Amanda. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Environmental Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Electrical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
General Uses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Purpose of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Customer Service and Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
End User Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
System Administration Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Installation Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Application Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Chapter 2:
Installing RDSP/x32 Boards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Configuring RDSP/x32 Voice Boards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
ShowJump Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Installing Voice Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Connecting Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
viii Installing Amanda@Work.Group/DOS
Chapter 3:
Installing RDSP/RTNI Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Installation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Configuring an RDSP/x000 Voice Board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Understanding MVIP Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Configuring MVIP Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Configuring the MVIP Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Configuring the Base I/O Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Configuring an RTNI-xATI Voice Board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Configuring the MVIP Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Configuring the Base I/O Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Configuring the Line Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Physical Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
ShowJump Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Installing the Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Installing the MVIP Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Configuring Amanda to Use the ATI Board . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Chapter 4:
Other Cards and Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Installing a LAN Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Using a UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Chapter 5:
Installing Amanda Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Running the Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Updating Amanda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Chapter 6:
Running the Setup Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Running Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Chapter 7:
Defining Dial Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Defining Dial Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Chapter 8:
Defining Tone Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Using this Chapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
ix
Using GetTones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Using AccuCall Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Chapter 9:
Defining Integration Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Using the Trace File for Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Setting Up the Trace File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Creating Test Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Running the Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Reading the Trace File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Adding Integration Strings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Using Character Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Running Integration Helper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Placing Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Forward from Ring No Answer Example. . . . . . . . . . . . . . . . . . . . . . . . . . 87
Direct Call Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Forward from Busy Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Chapter 10:
Configuring Amanda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Using This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Using the Questionnaire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Configuring a New Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Selecting a Type of Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Using Default and Recommended
Mailboxes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Chapter 11:
Faxing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Using This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Using a Fax Modem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Suggested Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Detecting a Fax Machine Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Modifying the PCPM Tone Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Creating the Hot Box Mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Setting the Hot Box Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Sending Faxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
x Installing Amanda@Work.Group/DOS
Chapter 12:
Using Serial Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Serial Integration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Bellcore Standard SMDI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
NEC 2000 and NEC 2400. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
AT&T System 75 or Definity-G3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Ericsson MD-110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Generic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Chapter 13:
Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Configuring Types of Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Telephone Line Options Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Sharing Amanda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Using the box_grt Configuration Option . . . . . . . . . . . . . . . . . . . . . . . . . 156
Using Incoming Trunk Call and CO Line IDs. . . . . . . . . . . . . . . . . . . . . 157
Using Multiple Employee Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Using Multiple Direct Messaging Mailboxes . . . . . . . . . . . . . . . . . . . . . 166
Chapter 14:
Accessing Amanda Remotely. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Accessing Amanda from Another Computer . . . . . . . . . . . . . . . . . . . . . . . . . 167
Setting Up Amanda’s Computer as a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Setting Up the Remote Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Connecting by Null Modem Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Connecting by Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Chapter 17:
Installing the Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Installing from Various Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Installing from a File Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Installing from a Floppy Drive on Windows 3.11 . . . . . . . . . . . . . . . . . . 176
Installing from a Floppy Drive on Windows 95 . . . . . . . . . . . . . . . . . . . 177
Adding Client Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Reviewing Client Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Chapter 18:
Configuration Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
General Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Fax Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
xi
Hot Box Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Network Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Outdial Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Per Port Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Serial Port Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
SMDI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
T1/DID Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Appendix A:
Troubleshooting Amanda. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
New Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Resetting a Port from the Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
What to Do When… . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Amanda Does Not Transfer the Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Caller Doesn’t Hear the Busy Message or RNA Greeting . . . . . . . . . . . . 240
Notification Does Not Work Correctly. . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Host/Remote Programs Do Not Work . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Message: RDSP Not Located at Any Interrupt Vector . . . . . . . . . . . . . . 242
System Halts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Appendix B:
Troubleshooting the Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
NIC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Common Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
xii Installing Amanda@Work.Group/DOS
Chapter 1:
Introducing Amanda
Requirements
At a minimum, the PC on which you install Amanda must have:
• MS-DOS version 6.22 in the directory C:\DOS.
• A 486SX processor running at a minimum of 25MHz.
• A VGA card.
• A minimum of 4MB of RAM.
• A minimum of 640K of conventional memory.
• A 3.5-inch, 1.44MB floppy disk drive and appropriate controller.
• An IDE hard disk drive with an access time of less than 14ms and
appropriate IDE controller.
• No LPT2 port (if disabled, it must be non-interfering).
• No devices at addresses 300, 301, 302, 303, 304, or 305.
• No devices using IRQ5 (other than the data modem).
• No devices using IRQ7 (other than the LPT1 port). (This IRQ will
be used by your voice boards.)
• To operate Amanda as Voice Server over a network, you must have
an NE2000 or compatible LAN adapter, configured to use IRQ 10 at
address 340H.
• To operate Amanda as Voice Server with more than one client, you
need a Client Connection Bank (CCB) to activate additional clients.
NOTE:Within the CMOS settings, all adapter ROM shadowing
should be disabled except for system ROM shadowing at
address F000.
2 Installing Amanda@Work.Group/DOS
Amanda can run with any of the following voice boards:
• Brooktrout 232, 432, 2132, and 4132 voice boards
• A Brooktrout RDSP/RTNI two-board combination consisting of:
- The Digital Signal Processors (DSPs) provided by an RDSP/x000
voice board
- An analog telephony interface using the Brooktrout RTNI-xATI
board
Some PCs are incompatible with Amanda. If you see the error “rdsp not
located” or find that Amanda appears to come up but the boards do not
answer, check your CONFIG.SYS file for the following line:
X=ED00-EDFF
This line indicates that your PC is NOT compatible with Amanda.
Environmental Requirements
• Locate the unit in an area free of excess moisture, dust, corrosive
gases, and chemicals.
• Install Amanda securely on a table or desk at least 2 feet (.6 meters)
above the floor.
• Use a properly grounded electrical outlet which is not controlled by
a switch.
• Ensure that the operating temperature is 40 to 95 degrees Fahrenheit
(2 to 35 degrees Centigrade), away from direct sunlight.
• Ensure that the humidity is 15% to 90%, noncondensing.
• For proper ventilation and servicing of the unit, provide at least 1
foot (0.3 meters) clearance on all sides and above the unit.
Electrical Requirements
• 90 to 130 VAC, 50 to 60 Hz, 3-prong outlet with separate ground,
separately fused at 15 amps.
• Outlet not controlled by an on/off switch.
• Use of electrical line conditioning equipment such as a surge protec-
tor and an uninterruptible power supply (UPS) is strongly recom-
mended.
• Grounding to comply with Underwriters Laboratories (UL) 1459.
Chapter 1: Introducing Amanda 3
General Uses
Amanda@Work.Group/DOS is an automated attendant and voice processing
system designed especially for ease of use and flexibility. As a PC-based
product, Amanda takes advantage of the technical innovations in the
personal computer market. In addition, Amanda’s standard hardware
components can be repaired or replaced by any PC service company. The
computer on which Amanda is installed must be used only for Amanda.
Depending on what lines from your PBX are connected to Amanda and
when calls are sent to Amanda to be processed, Amanda can serve you or
your customer in a variety of ways.
Configured as a primary attendant: Amanda answers all your incoming
calls on the lines you designate and allows the callers to direct their calls to a
specific person or department without being placed on indefinite hold. If a
specific person is unavailable, Amanda can take a private message for that
person without missing any details.
In this case, the telephone switching system sends all incoming calls to
Amanda.
Configured as a secondary attendant: Amanda assists your regular
operator when call volume is heavy, allowing callers to direct their own calls
or hold for the operator. Some companies provide specific incoming lines for
Amanda as a backdoor attendant for calls from vendors, family members,
friends, and special clients who prefer to have Amanda process their calls.
In this case, the telephone switching system sends incoming calls to Amanda
only when the regular operator’s extension is busy or not answered.
Configured as an off-duty attendant: Amanda provides 24-hour access to
your company and its employees when an operator is unavailable.
In this case, the telephone switching system sends all incoming calls to
Amanda while the office is closed.
4 Installing Amanda@Work.Group/DOS
Configured as a voice messaging center: Amanda takes messages and
allows users to send, store, and forward messages, increasing productivity
and enhancing inter-office communication.
In this case, the telephone switching system transfers any incoming call to
Amanda if the extension being called is busy or not answering.
Configured as an information system: Amanda provides answers to your
callers’ most frequently asked questions (so you can avoid costly
interruptions and provide a higher level of customer service 24 hours a day).
Information such as your address, available hours, directions to your offices,
and so forth, might be better handled by Amanda. Amanda’s serial ports can
access databases and other information stored in other computers, allowing
Amanda to give callers information on account balances, train schedules, and
so forth.
In this case, the telephone switching system or even an operator can send
incoming calls to Amanda. Then automatically, or if selected, Amanda plays
out the requested information.
Purpose of This Guide
This guide explains how to set up Amanda@Work.Group/DOS for the first
time. This guide covers:
• Connecting and configuring Amanda to work with your telephone
switching system
• Configuring Amanda to provide the voice mail services that the
owner selects
Chapter 1: Introducing Amanda 5
Customer Service and Support
The Amanda Company provides customer service and support Monday
through Friday from 8:00 A.M. to 8:00 P.M. Eastern Time, except holidays.
Customer Support:
(800) 800–9822
For sales, contact The Amanda Company at the East Coast office.
Dealer Sales:
Telephone: (800) 410-2745
Distribution Sales:
Telephone: (800) 410-2745
International Sales:
Telephone: (203) 744-3600
International Support:
Telephone: (203) 744-0860
Web Site:
http://www.taa.com
End User Support
End user support covers the actual usage of Amanda through the telephone,
such as picking up messages, sending messages, changing greetings, and
using distribution lists. Registered Amanda sites receive free end user
support for the life of their systems. Be sure to send in your registration card!
System Administration Support
System administration support covers the configuration of Amanda; such as
setting up mailboxes, programming notification, scheduling automatic
changes, and creating reports. Registered Amanda sites receive free system
administration support for up to six months after the installation. Be sure to
send in your registration card!
6 Installing Amanda@Work.Group/DOS
Installation Support
Installation support covers the initial connection of Amanda to a telephone
switching system as well as solutions to problems that occur when the
system is reconfigured or Amanda is upgraded.
The Amanda Company now offers installation support to any dealer who
buys a turnkey system.
Qualified Amanda marketing partners and solution providers, who are in
good standing, receive installation support for any system.
Application Support
Application support covers extended features that can be added to Amanda
using Amanda’s powerful Token Programming Language. The Amanda
Company can write custom applications for you. All Amanda Solution
Providers, who are in good standing, receive application support. Please
contact your Amanda sales representative for more information.
Chapter 2:
Installing RDSP/x32 Boards
Installation Checklist
Follow this checklist or use it to verify that you have completed all the
necessary steps for connecting Amanda to the telephone switching system.
Be sure to…
1. Install properly addressed voice boards
2. Install Amanda software without errors
3. Connect the line cords from voice boards to the telephone switching
system
4. Program the telephone switching system for voice mail integration
5. Test each voice board port for answering
6. Run Setup to define dial codes
7. Run Setup to obtain tone patterns
8. Run Setup to define telephone switching system integration patterns
9. Run Setup to define Amanda system configuration options
8 Installing Amanda@Work.Group/DOS
Configuring RDSP/x32 Voice Boards
Amanda recognizes each installed voice board by its unique address. The
first voice board has address 300; the second, address 301; the third, address
302, etc. To set a voice board’s address, you must configure the pins on the
voice board correctly using shorting jumpers. Voice boards are normally
shipped with address 300 (board 1) when you receive them. You should
check the address and change it, if necessary.
If you look at the voice board with the 4-wire (RJ-14) jacks to the right, the
10 sets of pins are in a row along the top of long voice boards (models 4132
and 2132) or along the bottom of short voice boards (models 432 and 232).
The jumper positions are numbered from 0 to 9 from left to right on the long
boards. On the short boards, they are labeled as powers of 2 (1, 2, 4, 8, 16,
32, …). However, use our tables as though both boards were numbered 0 to 9
from left to right.
Chapter 2: Installing RDSP/x32 Boards 9
The following table shows how to set the shorting jumpers for each possible
voice board in Amanda.
Closed means that two pins are covered/connected by the shorting jumper,
and Open means that the two pins are not covered/connected by the shorting
jumper. In the diagrams in this chapter, the blacked out pin positions
represent closed positions.
TIP:Installers often place shorting jumpers over only one pin
when the position is Open. This does not connect the pins,
but it does prevent losing jumpers.
Notice that the jumper positions numbered 3 through 7 are always closed
and that the jumper positions numbered 8 and 9 are always open. You will
change only the leftmost three jumper positions (those numbered 0, 1, and 2
in the table).
Hex Leftmost Jumper Positions Rightmost
Board Address 0123456789
1300 Closed Closed Closed Closed Closed Closed Closed Closed Open Open
2301 Open Closed Closed Closed Closed Closed Closed Closed Open Open
3302 Closed Open Closed Closed Closed Closed Closed Closed Open Open
4303 Open Open Closed Closed Closed Closed Closed Closed Open Open
5304 Closed Closed Open Closed Closed Closed Closed Closed Open Open
6305 Open Closed Open Closed Closed Closed Closed Closed Open Open
10 Installing Amanda@Work.Group/DOS
The next table show the jumper positions graphically.
CAUTION:Do not add or remove shorting jumpers while power is ap-
plied to the board.
A Graphical View
Board Hex
Address Jumper Positions
1300
2301
3302
4303
5304
6305
Chapter 2: Installing RDSP/x32 Boards 11
ShowJump Utility
Brooktrout provides the ShowJump utility which also shows how to
configure the jumpers on various types of Brooktrout boards. On Amanda,
this utility is stored in the C:\PLATFORM directory.
To use ShowJump:
1. At a DOS prompt, type:
C:\PLATFORM\SHOWJUMP
The Brooktrout Board Jumper Configuration Utility Screen displays the
jumper configuration for hex address 300 on boards 2108 and 4108
(which Amanda does not support).
2. Press Page Down until the board you are interested in is displayed.
3. Then type the hex address and press Enter.
The jumper configuration for the displayed board changes to fit the
address that you entered.
4. Press Esc to exit.
Installing Voice Boards
After making sure the address for the voice board is correct, you can install
it.
To install the voice board:
1. If this is a new installation, go to step 2. Otherwise, shut down Amanda
and turn off the computer:
a. Press Alt+S (if Amanda is running as a standalone) or s (if
Amanda is running as a voice server).
b. Type in the password. (The default is AMandA with only the
first two and the last letter capitalized.)
c. Press Enter.
12 Installing Amanda@Work.Group/DOS
d. Press Y (to confirm the shutdown).
e. Press Y again (to reconfirm).
f. After the DOS prompt C:\AMANDA> appears, turn off the
power.
2. Remove the computer cover and locate an available slot. A full length
slot is needed for models 2132 and 4132.
3. Remove the back slot cover and install the voice board. If there is a rear
card guide, slide the end of the voice board into it properly.
4. Close the computer cover and turn on the power.
CAUTION:Use an ESD-safe station while configuring and install-
ing your board. Otherwise, static discharge may dam-
age your board. (ESD stands for electrostatic
discharge.)
Connecting Ports
You create a port by connecting a telephone line to a voice board. Amanda
can support from 2 to 24 ports. On a Brooktrout voice board with two
connectors, the top connector represents the first two ports and the bottom
connector represents the second two ports for a total of four ports per board.
Each connector on a voice board is an RJ-14 modular jack. The inner pair is
one port, and the outer pair is the other port.
Chapter 2: Installing RDSP/x32 Boards 13
Ports are numbered consecutively from 1 to 24. Port 1 is connected to the
lowest addressed voice board (usually address 300). Each connector on the
voice board is linked to your telephone switching system by a standard 4-
wire line cord to a standard RJ-14 modular jack which should represent two
analog (single-line) extensions.
14 Installing Amanda@Work.Group/DOS
The above diagram shows the back of Amanda.
432
Modem
Voice Ports
VGA Card
COM1
COM2
1/2
3/4
Chapter 2: Installing RDSP/x32 Boards 15
The above diagram shows how the telephones, telephone switching system,
and Amanda are connected.
Voice Ports
1 & 2
Voice Ports
3 & 4
Phone Switch
Telephone
tline-R.cad
16 Installing Amanda@Work.Group/DOS
Chapter 3:
Installing RDSP/RTNI Boards
Installation Checklist
The RDSP/RTNI two-board combination puts all the Digital Signal
Processors (DSPs, specialized CPUs) on one board and provides an analog
telephony interface with the other.
You must configure and install each of the following:
• An RDSP/x000 (that is RDSP/4000, RDSP/8000, RDSP/12000,
RDSP/16000, RDSP/24000) board that provides the DSPs.
• An RTNI-xATI (that is RTNI-4ATI, RTNI-8ATI, RTNI-12ATI,
RTNI-16ATI, RTNI-24ATI) board that provides an analog telepho-
ny interface.
You must connect the interface board to the RDSP/x000 board using the
MVIP bus cable, which will transfer voice data between the two boards. The
connector cable for this is supplied with the board set. Since the RDSP/x000
board does not provide its own clock, it also receives timing information
from the bus.
In addition, you must connect the RTNI board to the telephone network.
Follow this checklist or use it to verify that you have completed all the
necessary steps for connecting Amanda to the telephone switching system.
18 Installing Amanda@Work.Group/DOS
NOTE:The GetTones and AccuCall Plus utilities cannot define
dial codes while the RDSP/RTNI two-board combination is
installed. The utilities do not know how to make MVIP
connections to the DSP resource in order to dial. The only
solution is to use a 232 or 432 voice board while you define
the tones. Then you replace the 232 or 432 voice board with
the ATI board combination.
Be sure to…
1. Configure an RDSP/x000 board:
a. Configure MVIP Streams
b. Configure the MVIP Termination
c. Configure the Base I/O Port
2. Configure an RTNI-xATI board:
a. Configure the MVIP Termination
b. Configure the Base I/O Port
c. Configure the Line Interface
3. Configure an RTNI-2T1 board:
a. Configure the Base I/O Port
b. Configure the IRQ Jumpers
c. Configure the Line Interface
4. Install the boards
5. Install the MVIP cable
6. Install Amanda software without errors
7. Connect the line cords from the voice boards to the telephone switching
system
8. Test each voice board port for answering
9. Run Setup to define dial codes
10. Program the telephone switching system for voice mail integration
Chapter 3: Installing RDSP/RTNI Boards 19
11. Run Setup to obtain tone patterns
12. Run Setup to define telephone switching system integration patterns
13. Run Setup to define Amanda system configuration options
Requirements
Before installing the RDSP/x000 board, verify that the host system meets
each of the following requirements:
• Bus speed is 8 MHz with 0 wait states or 10 MHz with 1 wait state
• Can provide +5v 3.0 A power to the RDSP/x000 board
These requirements are in addition to those for the system.
Configuring an RDSP/x000 Voice Board
The following figure shows the locations of the jumper blocks and
connectors on the RDSP/x000 board. The tables below it describe those
jumper blocks and connectors and show how to jumper the RDSP/x000
board for use with Amanda.
Later sections of this chapter offer more detailed explanations about how to
jumper this board.
20 Installing Amanda@Work.Group/DOS
The RDSP/x000 Board
Jumper Block and Connector Information
Closed means that two pins are covered/connected by the shorting jumper,
and Open means that the two pins are not covered/connected by the shorting
Table 1: Jumper Positions for Use with Amanda
Label Type Description 12345678
W1 Jumper
block DSi MVIP
stream Open Open Open Open Open Open Closed Open
W2 Jumper
block DSo MVIP
stream Open Open Open Open Open Open Closed Open
W3 Jumper
block Base I/O
port Closed Closed Closed Closed Closed Open Open
W4 Jumper
block MVIP ter-
mination Closed Closed
J2 Connector MVIP bus
J2
W1
W2
W3
2
140
39
W4
Chapter 3: Installing RDSP/RTNI Boards 21
jumper. In the diagrams in this chapter, the blacked out pin positions
represent closed positions.
TIP:Installers often place shorting jumpers over only one pin
when the position is Open. This does not connect the pins,
but it does prevent losing jumpers.
Understanding MVIP Streams
MVIP is a standard protocol for connecting PC resources. The MVIP bus
provides both physical and logical half-duplex internal connections for up to
512 resources.
The MVIP bus is segmented into 8 bidirectional serial data streams, each
composed of a pair of unidirectional streams. Each unidirectional stream can
carry 2.048 megabits of data per second, partitioned by Time Division
Multiplexing into 32 64-kilobits-per-second (Kb/sec.) time slots. A single
MVIP time slot has sufficient bandwidth to do either of the following:
• Carry PCM voice data
• Be a 64 Kb/sec. pipe for data communications
Numbering schemes for both streams and time slots start with 0. An MVIP
board is configured to use one of the eight streams on the bus. The port
associated with each time slot is made up of two half-duplex connections.
W1
W2 W4
W3
22 Installing Amanda@Work.Group/DOS
During configuration, each resource on the board is mapped to a discrete
time slot of the stream.
For example, the stream on an RDSP/24000 board automatically maps time
slots 1, 9, 17, and 25 to RDSP resources to 1, 2, 3, and 4, respectively. The
port associated with Time Slot 4 has two halves: the input designated DSi4,
and the output DSo4. The network interface board is the point of reference
for input and output.
Configuring MVIP Streams
Each RDSP/x000 board uses two MVIP streams: one for receiving and one
for transmitting. The RDSP/x000 board can receive on one of the DSi
streams (DSi0 through DSi7) and can transmit on one of the DSo streams
(DSo0 through DSo7). Each RDSP/x000 board is factory-configured to use
streams DSi6 and DSo6. The Amanda Company recommends that you keep
these settings.
The DSi stream jumper block consists of a pin position for each DSi stream.
If you look at the board with the bracket on your right, the leftmost pin
position corresponds to DSi0, the next pin position corresponds to DSi1, and
so on. The rightmost pin position corresponds to DSi7.
The DSo stream jumper block has the same construction as the DSi stream
jumper block with the leftmost pin position corresponding to DSo0 and the
rightmost pin position corresponding to DSo7.
To configure the DSi and DSo streams:
1. Find the jumper block for the DSi and DSo streams on the board.
The jumper block for the DSi MVIP stream is labeled W1. It is below
the MVIP connector if the bracket is to your right.
The jumper block for the DSo MVIP stream is labeled W2. It is below
the MVIP connector and the W1 block if the bracket is to your right.
Chapter 3: Installing RDSP/RTNI Boards 23
2. The settings should be as shown below:
3. Only the second to last pin position should be closed with a shorting
jumper.
CAUTION:Do not add or remove shorting jumpers while power is
applied to the board.
Configuring the MVIP Termination
Each RDSP/x000 can terminate the C2 MVIP and C4 MVIP bus signals. In a
series of boards that are on an MVIP bus, the boards at both ends must
terminate C2 and C4 while the other boards must not terminate the signals.
For example, the following figure shows three boards on an MVIP bus. The
left and right boards must terminate the MVIP bus signals while the middle
board must not. Each RDSP/x000 is configured at the factory to terminate
both C2 and C4.
W1
W2
24 Installing Amanda@Work.Group/DOS
The MVIP termination block consists of two pin positions, one for the C2
and one for the C4. If you look at the board with the bracket on your right,
the pin position on the left corresponds to C4 and the pin position on the right
corresponds to C2. The Amanda Company assumes that you are installing
only one RDSP/x000 board and, therefore, that it should terminate both
signals.
To terminate both MVIP bus signals:
1. Find the MVIP termination block on the board.
It is labeled W4 and is below the MVIP connector at the right of the W1
block if the bracket is to your right.
2. For use with Amanda, close both signals’ pin positions using shorting
jumpers (as shown below).
CAUTION:Do not add or remove shorting jumpers while power is
applied to the board.
W4
Chapter 3: Installing RDSP/RTNI Boards 25
Configuring the Base I/O Port
Each RDSP/x000 uses 47 I/O ports in addition to its base I/O port. Seven of
these additional I/O ports are contiguous to the base I/O port. For example, if
the RDSP/x000’s base I/O port is 300H, then the seven contiguous I/O ports
are 301H, 302H, 303H, 304H, 305H, 306H and 307H. The RDSP/x000 also
uses five additional I/O ports offset from the base I/O port and each of its
seven contiguous I/O ports:
• I/O port plus 400H
• I/O port plus 800H
• I/O port plus C00H
• I/O port plus 1000H
• I/O port plus FC00H
Each RDSP/x000 board is factory-configured to use base I/O port 300H. If
you are installing more than one RDSP/x000 board, you need to change the
base I/O ports so that each board has a unique base I/O port. If you are
installing only one RDSP/x000 board, you need to change its base I/O port
only if there is an I/O port conflict with another device.
Each RDSP/x000 must use a base I/O port in the range 0000H through
3FFH. The Amanda Company assumes that you are installing only one
RDSP board and recommends that you use base I/O port 300H.
To configure the base I/O port:
1. Find the jumper block for the base I/O port.
It is labeled W3 and is below the W2 block if the bracket is to your
right.
2. Set W3 for use with Amanda as shown below.
Close the five positions on the left using shorting jumpers and open the
two positions on the right.
W3
26 Installing Amanda@Work.Group/DOS
CAUTION:Do not add or remove shorting jumpers while power is
applied to the board.
Configuring an RTNI-xATI Voice Board
An RTNI-xATI board’s main function is connecting any line resource with
any other line or MVIP resource. This is commonly called switching. Your
RTNI-xATI board provides Analog-to-MVIP switching. The line resource
for your ATI board is analog, but only digital PCM signals can be switched,
so the board must convert the incoming analog signal to PCM prior to
switching. This conversion is made by the board’s loop start module which
links the MVIP bus and a trunk line. Amanda uses only the linking function
and not the switching function of MVIP.
The following figure shows the locations of the jumper blocks and
connectors on the RTNI-xATI board. The tables below it describe those
jumper blocks and connectors. They also show how to jumper the RTNI-
xATI board for use with Amanda.
Hex Jumper positions
Row Address 0123456
1300 Closed Closed Closed Closed Closed Open Open
Chapter 3: Installing RDSP/RTNI Boards 27
Closed means that two pins are covered/connected by the shorting jumper,
and Open means that the two pins are not covered/connected by the shorting
jumper.
Label Type Description Jumper
Settings
Jumpers EJ10 Jumper block Base I/O Address Open
Open
Closed
Closed
Closed
Closed
Open
Closed
Closed
Closed
W1 Jumper block MVIP Termination Closed
W2 Jumper block MVIP Termination Closed
Connectors J1 Connector MVIP bus
J4 Connector Telephony Cable
EJ10 W1
W2
28 Installing Amanda@Work.Group/DOS
Configuring the MVIP Termination
The MVIP termination block consists of two pin positions, one for the C2
and one for the C4. The top pin position (labeled W1) corresponds to C4 and
the next pin position (labeled W2) corresponds to C2.
You should close both pin positions. The Amanda Company assumes that
you are installing only one RTNI-xATI board along with an RDSP/x000
board. In this case, this board should terminate both signals.
To terminate both MVIP bus signals:
1. Find the MVIP termination block on the board.
One pin position is labeled W1 and the other is labeled W2. They are
located just below the J1 connector with the bracket on your right.
2. For use with Amanda, close both signals’ pin positions using shorting
jumpers (as shown below).
CAUTION:Do not add or remove shorting jumpers while power is
applied to the board.
Configuring the Base I/O Port
Each voice board must have a unique base I/O port. Each RTNI-xATI board
is factory-configured to use base I/O port 308H. It uses the base I/O port and
three others, calculated as offsets of the base I/O port. These I/O ports are:
• Base I/O port
• Base I/O port plus 400H
• Base I/O port plus 800H
• Base I/O port plus C00H
W1
W2
Chapter 3: Installing RDSP/RTNI Boards 29
For example, if the RTNI-xATI board’s base I/O port is 308H, then the ATI
board uses the following I/O ports:
• 308H
• 708H
•A08H
•E08H
If you are installing only one RTNI-xATI board, you must change its base I/
O port only if another device in the computer has the same I/O port. The
Amanda Company recommends that you use 308H.
To set the base I/O port:
1. Locate the base I/O port jumper block.
It is labeled EJ10.
2. For use with Amanda, set the jumpers as shown below.
CAUTION:Do not add or remove shorting jumpers while power is
applied to the board.
Configuring the Line Interface
The line interface configuration of your RTNI-xATI board determines which
CO provisions it requires. You must match the line connection to your line
interface module configuration as follows:
EJ10
30 Installing Amanda@Work.Group/DOS
Interface Type: 2-Wire Loop Start
USOC Jack Connector: RJ21X
REN/Service Code: X.XB
Facility Interface Code: 02LS2
The Loop Start module links your MVIP bus and a telephone line from your
CO or PBX. For a loop start, you alert your CO to an outbound call by
connecting the tip to the ring, thereby closing the loop and allowing current
to flow.
Physical Connections
After you have installed the board (as explained in “Installing the Boards” on
page 32), use the cable supplied with the RTNI-xATI board to connect the
Amanda system to the telephone network. Connect the 62-pin connector to
the RTNI-xATI board and the Amphenol 50-pin connector to a 66 Block.
Pinout Table for Amphenol 50-pin Connector
Pin Description-Color code Pin Description-Color code
26 T1: Channel 1 Tip-white/blue 13 R13: Channel 13 Ring-green/black
1R1: Channel 1 Ring-blue/white 39 T14: Channel 14 Tip-black/brown
27 T2: Channel 2 Tip-white/orange 14 R14: Channel 14 Ring-brown/black
2R2: Channel 2 Ring-orange/white 40 T15: Channel 15 Tip-black/gray
28 T3: Channel 3 Tip-white/green 15 R15: Channel 15 Ring-gray/black
3R3: Channel 3 Ring-green/white 41 T16: Channel 16 Tip-blue/yellow
29 T4: Channel 4 Tip-white/brown 16 R16: Channel 16 Ring-yellow/blue
4R4: Channel 4 Ring-brown/white 42 T17: Channel 17 Tip-yellow/orange
30 T5: Channel 5 Tip-white/gray 17 R17: Channel 17 Ring-orange/yellow
Chapter 3: Installing RDSP/RTNI Boards 31
ShowJump Utility
Brooktrout provides the ShowJump utility which also shows how to
configure the jumpers on various types of Brooktrout boards. On Amanda,
this utility is stored in the C:\PLATFORM directory.
5R5: Channel 5 Ring-gray/white 43 T18: Channel 18 Tip-yellow/green
31 T6: Channel 6 Tip-red/blue 18 R18: Channel 18 Ring-green/yellow
6R6: Channel 6 Ring-blue/red 44 T19: Channel 19 Tip-yellow/brown
32 T7: Channel 7 Tip-red/orange 19 R19: Channel 19 Ring-brown/yellow
7R7: Channel 7 Ring-orange/red 45 T20: Channel 20 Tip-yellow/gray
33 T8: Channel 8 Tip-red/green 20 R20: Channel 20 Ring-gray/yellow
8R8: Channel 8 Ring-green/red 46 T21: Channel 21 Tip-violet/blue
34 T9: Channel 9 Tip-red/brown 21 R21: Channel 21 Ring-blue/violet
9R9: Channel 9 Ring-brown/red 47 T22: Channel 22 Tip-violet/orange
35 T10: Channel 10 Tip-red/gray 22 R22: Channel 22 Ring-orange/violet
10 R10: Channel 10 Ring-gray/red 48 T23: Channel 23 Tip-violet/green
36 T11: Channel 11 Tip-black/blue 23 R23: Channel 23 Ring-green/violet
11 R11: Channel 11 Ring-blue/black 49 T24: Channel 24 Tip-violet/brown
37 T12: Channel 12 Tip-black/orange 24 R24: Channel 24 Ring-brown/violet
12 R12: Channel 12 Ring-orange/ black 50 Analog Ground-violet/gray
38 T13: Channel 13 Tip-black/ green 25 BAT-: Negative battery terminal-gray/ violet
Pinout Table for Amphenol 50-pin Connector (Con-
Pin Description-Color code Pin Description-Color code
32 Installing Amanda@Work.Group/DOS
To use ShowJump:
1. At a DOS prompt, type:
C:\PLATFORM\SHOWJUMP
The Brooktrout Board Jumper Configuration Utility Screen displays the
jumper configuration for hex address 300 on boards 2108 and 4108.
2. Press Down Page until the board you are interested in is displayed.
3. Then type the hex address and press Enter.
The jumper configuration for the displayed board changes to fit the
address that you entered.
4. Press Esc to exit.
Installing the Boards
Use the following procedure to install one or more RDSP/RTNI boards.
To install the board:
1. If this is a new installation, go to step 2. Otherwise, shut down Amanda
and turn off the computer:
a. Press Alt+S (if Amanda is running as a standalone) or s (if
Amanda is running as a voice server).
b. Type in the password. (The default is AMandA with only the
first two and the last letter capitalized.)
c. Press Enter.
d. Press Y (to confirm the shutdown).
e. Press Y again (to reconfirm).
f. After the DOS prompt C:\AMANDA> appears, turn off the
power.
2. Remove the cover.
3. Locate free bus slots that have 16-bit-compatible, ISA bus edge connec-
tors.
Chapter 3: Installing RDSP/RTNI Boards 33
4. Carefully align the boards with the slot and firmly seat the boards into
the computer.
5. Use a bracket screw to securely fasten the boards’ brackets.
The bracket provides grounding for the board.
6. Turn the computer back on.
7. From the C:> DOS prompt, follow the installation instructions in
“Chapter 5: Installing Amanda Software.”
CAUTION:Use an ESD-safe station while configuring and install-
ing your board. Otherwise, static discharge may dam-
age your board.
Installing the MVIP Cable
After installing an RDSP/x000 board you need to connect the MVIP bus
cable to each board.
This 40-pin MVIP-compliant connector is at the top of the board if you look
at the board with the bracket to your right. Use the MVIP connector to
connect the RDSP/x000 board to a telephone network interface board.
If your MVIP connector cable has more than two connector positions, use
the two end-positions for this installation.
Configuring Amanda to Use the ATI Board
There are a couple of Amanda’s configuration options that must be set
correctly when you are using an RTNI-xATI voice board. See “Running
Setup” on page 49 for information about using the Setup utility to set or
check these advanced configuration options.
The configuration option ati_mode must be set to true. Then Amanda makes
the connections needed for the ATI board.
34 Installing Amanda@Work.Group/DOS
Be aware that RTNI-xATI voice boards cannot detect rotary. If you use an
RTNI-xATI voice board, you must leave the rotary configuration option set
to false.
Chapter 4:
Other Cards and Devices
Installing a LAN Card
To use Amanda as a voice server, you must install a LAN card, also called a
network interface card (NIC). The card must be NE2000 compatible.
If you have any problems with the installation and you purchased the NIC
from The Amanda Company, please contact Customer Service.
To install a LAN card:
1. Configure the card.
If you purchased your LAN card from The Amanda Company, it is pre-
configured for IRQ 10, I/O address 340H, and is to be used with
unshielded twisted pair (UTP) cable. These are the default settings.
If you purchase another LAN card, use this IRQ and address. Follow
that LAN card’s instructions for installation.
NOTE:Addresses 300 through 305 are not available for the LAN
card. See “Chapter 2: Installing RDSP/x32 Boards” and
“Chapter 3: Installing RDSP/RTNI Boards” for more infor-
mation.
2. If this is a new installation, go to step 3. Otherwise, shut down Amanda
and turn off the computer:
a. Press Alt+S (if Amanda is running as a standalone) or s (if
Amanda is running as a voice server).
36 Installing Amanda@Work.Group/DOS
b. Type in the password. (The default is AMandA with only the
first two and the last letter capitalized.)
c. Press Enter.
d. Press Y (to confirm the shutdown).
e. Press Y again (to reconfirm).
f. After the DOS prompt C:\AMANDA> appears, turn off the
power.
3. Remove the computer cover and locate an available slot.
4. Remove the back slot cover and install the LAN card. If there is a rear
card guide, slide the end of the LAN card into it properly.
CAUTION:When installing your LAN card, you must be careful
about electrostatic discharges (ESD). Use an ESD-safe
environment, a wrist guard, and so on. Otherwise, stat-
ic discharge may damage your card.
5. Connect the LAN card to the rest of the network.
The Amanda Voice Server sends and receives NetBEUI commands, and
can be part of any network that supports NetBIOS over NetBEUI.
6. Reassemble the computer and restart it by turning the power switch on.
Using a UPS
The Amanda Company strongly recommends the installation of an
uninterrupted power supply (UPS) with every Amanda system. It provides
clean power to Amanda and keeps the probability of a computer lockup (and
the resulting loss of data or even loss of the system) as low as possible.
According to some reports, power problems are the primary reason why
computers lose data (45.3%). The next closest cause is storm damage at
9.4%. (Human error and sabotage rank eighth with 3.2%.)
Chapter 4: Other Cards and Devices 37
According to a Bell Laboratories study entitled “The Quality of US
Commercial AC Power,” the main categories of AC power irregularities
across the nation are sags (or brownouts), power surges, blackouts, and
overvoltages. The best solution is a UPS, which can handle 99.3% of these
power problems.
A UPS is a special type of AC power line conditioner. When compared to
the other devices available, such as surge suppressors, filters, isolation
transformers, tap changing regulators, and voltage regulating transformers,
the UPS is rated highest by Bell Laboratories and is relatively inexpensive.
The cost of installing a UPS is nominal when compared to the cost of
repairing a damaged Amanda system or compared to the loss of confidence
from callers and internal Amanda users.
For more information about what causes power irregularities and what
damage they can do to Amanda, call to be faxed Technical Note 10, “The
Importance of a UPS.”
38 Installing Amanda@Work.Group/DOS
Chapter 5:
Installing Amanda Software
Running the Installation Program
Install Amanda software only after you have:
• Installed the voice boards.
• (Voice server only) Installed an NE2000-compatible Ethernet LAN
card.
Follow the installation checklist that is in the chapter that explains how to
configure the voice boards you use:
• “Chapter 2: Installing RDSP/x32 Boards”
• “Chapter 3: Installing RDSP/RTNI Boards”
If you are installing Amanda as a voice server, have your MS Workgroup
Add-on for DOS disk at hand.
To start the Amanda installation program:
1. Insert the disk labeled “Amanda@Work.Group/DOS, Installation Disk 1
of 5” into a floppy disk drive.
2. From the DOS prompt C:\>, type the command:
A:\INSTALL
(If the disk is in drive B:, use B:\INSTALL B:.)
Then press Enter.
40 Installing Amanda@Work.Group/DOS
You see a screen similar to the following:
Correct operation of an Amanda Call Processing system depends on accurate
time and date settings in the computer. To assure correct operation,
please verify these now. Here are the present time and date:
Current time is 3:13:04.99p
Current date is Tue 01-14-1997
Are these values correct[N,Y]?
3. Type Y for Yes or N for No.
If you type Y, proceed to step 4.
If you type N, you are prompted for a new date and time, similar to what
is shown below.
a. Type a new date then press Enter or just press Enter to keep the
current date.
b. Type a new time then press Enter or just press Enter to keep the
current time.
Please correct the Time and/or Date now.
Current date is Tue 01-14-1997
Enter new date (mm-dd-yy): 01-14-97
Current time is 3:14:36.11p
Enter new time:
Chapter 5: Installing Amanda Software 41
Information similar to the following appears on the screen.
This program installs or un-installs Amanda@Work.Group/DOS
Version 7.xx Revision X on your computer system.
You may press the [Esc] key at any time to stop
the installation.
PLEASE NOTE: This installation stores backup copies of any files
that it overwrites on your hard disk. If after
installing you wish to revert to your previous
system, run this install program again and select
the "Un-install ..." option.
Press [Esc] to quit, any other key to continue ...
4. Press any key on the keyboard to continue.
An installation, reinstallation, or an update menu appears.
INSTALLATION MENU
Select the type of installation that you want to be performed.
Use the arrow keys to make a selection; then press Enter.
Install Amanda@Work.Group/DOS Version 7.xx Revision X
Test the configuration of this system only
Exit this installation program now
42 Installing Amanda@Work.Group/DOS
REINSTALLATION MENU
Amanda@Work.Group/DOS Version 7.xx Revision X is already
installed on this machine.
Select the action that you want to be performed.
Use the arrow keys to make a selection; then press Enter.
Re-install Amanda@Work.Group/DOS Version 7.xx Revision X
Un-install the existing Amanda@Work.Group/DOS 7.xx Revision X system
Test configuration of this machine only
Exit this installation program now
UPDATE MENU
Amanda@Work.Group/DOS Version 7.xx Revision X using RH-RDSP
style boards appears to be installed on this machine.
Select the type of installation that you want to be performed.
Use the arrow keys to make a selection; then press Enter.
Update existing Amanda@Work.Group/DOS 7.xx Rev. X
Test configuration of this machine only
Exit this installation program now
5. In any case, select the first option on the menu then press Enter.
If this is a new installation, go to step 6. Otherwise, go to step 7.
Chapter 5: Installing Amanda Software 43
6. You see a screen similar to the following:
Since this a first time installation, Amanda@Work.Group/DOS needs to know
if this system uses Brooktrout RDSP/x32 or RDSP/x000 with RTNI-xATI
style boards. Make this choice very carefully since this choice is
PERMANENT!
Select the Brooktrout board type for this installation from the list.
Use the arrow keys to make a selection; then press Enter.
Brooktrout RDSP/x32 style two or four port boards
Brooktrout RDSP/x000 with RTNI-xATI style boards
I am not sure; stop so I can find out first
Use the arrow keys to select the appropriate style of Brooktrout voice
board then press Enter.
7. The next screen asks whether you are installing Amanda as a standalone
system or as a voice server.
44 Installing Amanda@Work.Group/DOS
Amanda@Work.Group/DOS can be installed as a networked Voice Server,
integrated with a local area network (LAN), or as a stand-alone system.
If you elect the Voice Server installation, you must have a properly set
NE2000 compatible Ethernet LAN adaptor installed in this machine prior to
installing this software.
[If you install the LAN adaptor, it MUST be set for IRQ 10 and I/O
address 340, AND you MUST have your MS WORKGROUP ADD-ON FOR DOS disk]
Select the type of configuration that you want to be performed.
Use the arrow keys to make a selection; then press Enter.
No LAN card. Configure Stand-alone system.
The LAN card is installed. Configure Voice Server system.
Exit. I need to install the LAN card first.
If you plan to use Amanda client software to configure Amanda and
allow users to access messages from their computers as well as their
telephones, you need to install Amanda as a voice server, select the sec-
ond option “The LAN card is installed. Configure Voice Server system.”
If you plan to configure Amanda from this computer and allow users to
access messages only from their telephones, select the first option “No
LAN card. Configure Stand-alone system.”
8. The next few screens display information about your computer and the
installation. Follow the directions on the screen.
If everything is OK, the installation can continue. Otherwise, the instal-
lation stops.
The first screen of the following examples appears only for new installa-
tions. If you are installing Amanda as a standalone system, some screens
will have less information than the examples.
Chapter 5: Installing Amanda Software 45
Since this is a new installation, a new CONFIG.SYS file will be
created; you do not need to take any action yourself.
Press [Esc] to quit, any other key to continue ...
Checking your computer for the proper components and conflicts .
. .
Verifying computer processor type . . . OK
Verifying the video adaptor type . . . . OK
Verifying total amount of memory . . . . OK
Verifying total conventional memory. . . OK
Verifying operating system version . . . OK
Verifying sufficient free disk space . . OK
Press [Esc] to quit, any other key to continue ...
46 Installing Amanda@Work.Group/DOS
Please note that you have the following additional components . . .
Serial port COM1 at address : 1016
Serial port COM2 at address : 760
Serial port COM3 at address : 744
Parallel port LPT1 at address: 888
Video Adaptor Card type : VGA (Video Graphics Array)
Video Monitor Display type : Color
Available disk space : 176295936
Press [Esc] to quit, any other key to continue ...
Your original installation of Amanda@Work.Group/DOS 7.xx Revision X
is nearly finished.
The system will next reboot and the initial memory configuration
will begin.
Next, the network portion of the Voice Server will be installed.
Finally, since this is a new installation, the SETUP program will
run automatically to create a configuration file with all default
values for you. Last, the system will reboot again and Amanda
will be started.
REMOVE INSTALLATION "DISK 5 of 5" FROM DISK DRIVE.
Press any key to continue ...
If the installation proceeds, you will be asked to insert each of the five
installation disks into your floppy disk drive in order.
Chapter 5: Installing Amanda Software 47
If you selected a networked Voice Server installation, you will also be
asked to install the MS-NETWORK files required to connect your
Amanda@Work.Group/DOS Voice Server to the network. You will be
asked to remove the disk labeled “Microsoft Workgroup Add-On for
MS-DOS, Disk 1 - Setup” from its sealed envelope and insert it in your
floppy disk drive.
Opening the sealed envelope indicates your acceptance of the Microsoft
software license terms shown on the inside cover of the User’s Guide
for Microsoft WORKGROUP ADD-ON MS-DOS included in your pack-
age.
During the installation process, your computer will reboot once or
twice.
9. Follow the directions on the screens. Eventually, a screen informs you
that “This completes the installation….”
NOTE:If this is an upgrade or a reinstallation, the installation pro-
gram does not update your existing CONFIG.SYS file.
However, it suggests that you change your CONFIG.SYS
to work better with Amanda.
It recommends that you reset the DOS environment mem-
ory size to an amount based on the information you provid-
ed about ports during the installation.
For example, if the program suggests a setting of 346, you
should add or change the /E parameter in your SHELL
statement. It might look like the following:
SHELL=C:\COMMAND.COM /E:346 /P
The installation program also suggests that you remove the
EMS memory limit allocated for your memory manager (if
that manager is EMM386.EXE).
For example, suppose the DEVICE statement for
EMM386.EXE is similar to the following:
DEVICE=C:\DOS\EMM386.EXE 272 …
You remove the 272. The EMS memory limit is the only
solitary number in the DEVICE statement.
10. Set up Amanda to work with your telephone switching system and
according to your voice mail preferences.
Use the next few chapters to define dial codes, define tone and integra-
tion patterns, and set Amanda’s configuration options.
48 Installing Amanda@Work.Group/DOS
Updating Amanda
If you are upgrading Amanda software, the installation screens are somewhat
different from the new installation described above. Follow the directions on
the screen, and the installation process should go smoothly.
If the installation program recommends changes to your CONFIG.SYS file,
you need to make these changes yourself. The installation program does
NOT create a new CONFIG.SYS file for you because commands you added
or changed to run your system could be replaced.
If you installed Amanda as a standalone only, change C:\CONFIG.SYS, the
CONFIG.SYS file in the root directory.
If you installed Amanda as a voice server, make the recommended changes
to both C:\AMANDA\DOSMODE\CONFIG.SYS and
C:\AMANDA\NETMODE\CONFIG.SYS. Depending on the mode in which
you run Amanda, the CONFIG.SYS file (and other files) are copied to the
root directory (C:\) from either C:\AMANDA\DOSMODE or
C:\AMANDA\NETMODE. Changing the CONFIG.SYS in the root
directory only is like not changing the file at all because it will be replaced
every time you start Amanda.
Chapter 6:
Running the Setup Utility
Running Setup
You must configure Amanda to work properly with your telephone
switching system and to let Amanda know your customer’s voice mail and
other preferences. The Amanda Company provides the Setup utility to make
configuring Amanda easier.
You run Setup to configure dial codes, tone patterns, DTMF integration
patterns, and Amanda’s system configuration options.
To run Setup:
1. If Amanda is running, shut down the Amanda system.
a. Press Alt+S (if Amanda is running as a standalone) or s (if
Amanda is running as a voice server).
b. Type in the password. (The default is AMandA with only the
first two and the last letter capitalized.)
c. Press Enter.
d. Press Y (to confirm the shutdown).
e. Press Y again (to reconfirm).
2. Change to the AMANDA directory—unless you are there already. At
the DOS prompt, type:
CD C:\AMANDA
Then press Enter.
50 Installing Amanda@Work.Group/DOS
3. Now that the DOS prompt reads C:\AMANDA, type:
SETUP
Then press Enter.
The Amanda@Work.Group/DOS Configuration Utility menu appears.
4. From this menu, you define the following for your telephone switching
system and Amanda. Each is described in one of the next few chapters:
• Telephone System Dial Codes
• Telephone System Tone Patterns
• System Integration Patterns
• System Configuration Options
System Configuration Options contains two sections:
General Configuration Displays dialog boxes that guide you through
the options that are most often changed, wheth-
er they appear in the INSTALL.CFG file or the
default template for mailboxes (normally mail-
box 997).
These dialog boxes are explained in “Chapter
10: Configuring Amanda.”
Advanced Configuration Allows you to change any configuration setting
in INSTALL.CFG. The options are divided
into categories to make it easier to locate the
options you need to change. The options are pa-
rameter lists. Each option is explained in
“Chapter 18: Configuration Reference.”
Chapter 7:
Defining Dial Codes
Defining Dial Codes
To communicate with the telephone switching system, Amanda must know
the switching system’s dial codes. Most Amanda systems are connected to
only one switching system, but you can connect your system to two.
By default, the 1001.PBX file is used to store dial codes. You can change
this if you choose. However The Amanda Company has reserved the
numeric names from 1002 to 2001, so do not use any number in that range as
the name of your file.
As part of a new installation, the file 1001.PBX is created for you based on
the Panasonic KX-T308/616/1232 telephone switching system. If you are
upgrading your Amanda system, the file you used for dial codes in the past
will be renamed to 1001 (and 2001 if two switches are used). Also, the Setup
utility may not know what switching system your dial codes file is based on.
The names of the switching systems appear in the .PBX files containing
codes for these systems and are displayed by the Setup utility. Yours may be
based on an older version of Amanda that did not have the switching system
names in the files. If so, yours may be identified by Setup as “not defined.”
NOTE:Instead of using Setup, you can edit your .PBX file in the
C:\AMANDA\PBX.DB directory using the JOVE utility.
See “Chapter 12: Utilities,” in Administering Aman-
da@Work.Group/DOS for information about JOVE.
52 Installing Amanda@Work.Group/DOS
To define dial codes:
1. Run Setup as explained in “Running Setup” on page 49.
2. From the Configuration Utility menu, press 1 to select Telephone Sys-
tem Dial Codes.
The Telephone Switch Type screen lists 1001.PBX and 2001.PBX along
with the names of the switching systems they are based on or identifies
the switching system as not defined.
3. From the Telephone Switch Type screen, do one of the following:
• If the telephone switching system is the correct one (or if the tele-
phone switching system is the one you have used in the past—even
though it is identified as not defined):
• Select the file to be edited then press Enter.
Setup displays the dial codes and their descriptions.
• If the telephone switching system is not the one listed:
a. Select one of the .PBX files.
b. Press F2 to display a list of switching systems.
c. Use the arrow keys to select the name of your system or the
name of a system which has codes similar to yours then
press Enter.
d. Press Enter again to display the dial codes and their descrip-
tions.
Chapter 7: Defining Dial Codes 53
4. To change any dial codes that do not apply to your system:
a. Use the following Dial Codes Table to understand each of the
codes displayed on the screen.
b. Use the Up Arrow, Down Arrow, Tab, or Enter keys to select
the code you want to change.
c. Type the new code over the current code (if there is one).
(You can also use Backspace, Delete, spacebar, and the Right
Arrow and Left Arrow keys to edit the code.)
d. When you are finished, press F10 to save your changes.
(To return to the Telephone System Dial Codes screen without sav-
ing your changes, press Esc.)
e. Repeat steps A through D for any other codes to be changed.
5. When you have finished defining the dial codes, press Esc to return to
the Amanda Configuration Utility menu.
Dial Codes Table
Dial Code Label Description
What to dial to put the call-
er on transfer hold: The code Amanda dials to ask the telephone switching system to put the
caller on transfer hold before she transfers a caller to an extension.
Usually, this code is “F-” (a hookflash followed by a half-second pause).
This may need to be changed to “F--” (a hookflash followed by a one-
second pause) or “F,” (a hookflash followed by a two-second pause) for
telephone switching systems that are slow to provide a transfer dial tone
after a hookflash. (Don’t use the quotation marks in the dial code.)
If tmo_dtwait is greater than 0, the number of dashes set for this option
is irrelevant. Use the value 0 for tmo_dtwait for faster call processing.
For more information about tmo_dtwait, see “What to dial to put the call-
er on transfer hold:” on page 53.
If you are editing C:\AMANDA\PBX.DB\1001.PBX instead of using
Setup, this is the dl_dtwait option.
54 Installing Amanda@Work.Group/DOS
What to dial when there is
no transfer dial tone: The code Amanda dials to return to the caller if both of the following are
true:
You configure Amanda to wait for a transfer dial tone before transferring
a call to an extension
There is no transfer dial tone
In this case, Amanda treats the attempted transfer as though the exten-
sion was busy.
Some telephone switching systems use “F-”, others use “-”. (Don’t use
the quotation marks in the dial code.)
If you are editing C:\AMANDA\PBX.DB\1001.PBX instead of using
Setup, this is the dl_ndtret option.
What to dial to return to
the caller after ring no an-
swer:
During supervised transfers, if the extension rings the specified number
of times but is not answered, Amanda dials this code to ask the telephone
switching system to reconnect the caller to Amanda. (See the question-
naire in “Chapter 10: Configuring Amanda” for more information about
configuring the number of rings.)
Usually, this code is “F-”. (Don’t use the quotation marks in the dial
code.)
If you are editing C:\AMANDA\PBX.DB\1001.PBX instead of using
Setup, this is the dl_rnaret option.
What to dial to return to
the caller after busy: During supervised transfers, Amanda dials this code to ask the telephone
switching system to reconnect the caller to Amanda if the extension is
busy.
Usually, this code is “F-”. (Don’t use the quotation marks in the dial
code.)
If you are editing C:\AMANDA\PBX.DB\1001.PBX instead of using
Setup, this is the dl_bsyret option.
Dial Codes Table (Continued)
Dial Code Label Description
Chapter 7: Defining Dial Codes 55
What to dial after a call
screening reject: The code Amanda dials to reconnect to the caller if all of the following
are true:
Amanda is performing a supervised transfer
Call screening is ON
The user at the extension that was called rejects the caller
In this case, Amanda plays the mailbox’s current greeting.
Usually, this code is “F-”. (Don’t use the quotation marks in the dial
code.)
If you are editing C:\AMANDA\PBX.DB\1001.PBX instead of using
Setup, this is the dl_hupret option.
What to dial to connect a
caller to an extension: During supervised transfers, Amanda dials this code to complete the call
transfer after detecting an answer at the called extension. If call screen-
ing is ON, Amanda dials this code only after the user at the extension ac-
cepts the call.
Usually, this code is “H” (for Hang up). (Don’t use the quotation marks
in the dial code.)
If you are editing C:\AMANDA\PBX.DB\1001.PBX instead of using
Setup, this is the dl_connect option.
What to dial before the
mailbox extension: If Amanda needs to dial something after dial tone detection, but before
dialing the extension number, enter that code here.
Usually this is left blank.
If you are editing C:\AMANDA\PBX.DB\1001.PBX instead of using
Setup, this is the dl_prefix option.
What to dial after the mail-
box extension: If Amanda needs to dial something after dialing the extension number,
enter that code here.
Don’t use an “H” for a blind transfer here because this setting is global.
Sometimes you need “1-” to bypass the hands-free answer feature (voice
announce) on some telephone systems. (Don’t use the quotation marks
in the dial code.)
If you are editing C:\AMANDA\PBX.DB\1001.PBX instead of using
Setup, this is the dl_suffix option.
Dial Codes Table (Continued)
Dial Code Label Description
56 Installing Amanda@Work.Group/DOS
What to dial on each port
after the system starts: If you want Amanda to dial some initialization codes when she first
starts up, define those codes here. For example, you may want to remove
call forwarding on the ports.
Usually this is left blank.
If you are editing C:\AMANDA\PBX.DB\1001.PBX instead of using
Setup, this is the dl_init option.
What to dial on each port
before shutdown: If you want Amanda to dial certain codes when she shuts down, define
those codes here. For example, enabling call forwarding on the ports lets
a live operator take the calls when Amanda shuts down.
Usually this is left blank.
If you are editing C:\AMANDA\PBX.DB\1001.PBX instead of using
Setup, this is the dl_stop option.
What to dial when a port
goes off-hook: If Amanda must dial some special codes as she goes off-hook to enable
a special feature, define those special codes here. For example, you may
enable special types of SMDI integration over a serial port.
Usually this is left blank.
If you are editing C:\AMANDA\PBX.DB\1001.PBX instead of using
Setup, this is the dl_pickup option.
What to dial to create or
record a conference call: Controls how to do a conference call when the called party answers the
telephone.
You provide the digits used to conference the caller, called party, and
Amanda (for example, “*3”). (Don’t use the quotation marks in the dial
code.) If your telephone switching system does not have this capability,
leave it blank.
For example, if the Extension field for a mailbox contains 127KM,
Amanda dials 127. When an answer is detected, Amanda dials the con-
ference dial code (such as “*3”) which conferences the caller, the called
party, and Amanda. Instead of hanging up when she connects the two
parties, Amanda records the conversation as a message in mailbox 127.
If you are editing C:\AMANDA\PBX.DB\1001.PBX instead of using
Setup, this is the dl_conference option.
Dial Codes Table (Continued)
Dial Code Label Description
Chapter 7: Defining Dial Codes 57
Number of seconds to wait
for dial tone detection: This is the number of seconds Amanda waits for your telephone switch-
ing system to provide a continuous dial tone for one full second. If your
system has few DTMF receivers or intercom paths for call transfers, one
may not be immediately available for Amanda to transfer a call. In this
case, this number should be greater than 0.
Use 0 when Amanda does not wait for a dial tone (as when the telephone
switching system returns stutter dial tone or silence on a transfer). A
good value is 4 (seconds) when she does wait for a dial tone. The range
is 0–127.
If you are editing C:\AMANDA\PBX.DB\1001.PBX instead of using
Setup, this is the tmo_dtwait option.
Number of 1/100 seconds
to use for Flash time: Determines how long Amanda remains on-hook while performing a
hookflash. The value is in hundredths of seconds.
The usual value is 55 (just over half a second).
When set too short, the hookflash does not happen; when set too long, it
hangs up.
If you are editing C:\AMANDA\PBX.DB\1001.PBX instead of using
Setup, this is the flashtm option.
Which DTMF tone to lis-
ten to for hangup detec-
tion:
If your telephone switching system plays a specific DTMF tone or se-
quence of tones when a caller hangs up (to make hangup detection fast-
er), enter that DTMF digit here.
If your telephone switching system has this capability, the code is usual-
ly the letter “d” which represents DTMF D. This may be a sequence of
DTMF digits rather than a single DTMF digit. The maximum length is
10 characters. If your system does not support this feature, leave it blank.
If you are editing C:\AMANDA\PBX.DB\1001.PBX instead of using
Setup, this is the dt_hangup option.
What to dial to turn on the
message waiting indicator: If your telephone switching system has message waiting indicators, enter
the code needed to turn the indicator on.
What to dial to turn off the
message waiting indicator: If your telephone switching system has message waiting indicators, enter
the code needed to turn the indicator off.
Dial Codes Table (Continued)
Dial Code Label Description
58 Installing Amanda@Work.Group/DOS
Chapter 8:
Defining Tone Patterns
Using this Chapter
You can use either GetTones, an Amanda Company utility, AccuCall Plus, a
Brooktrout utility, to define tone patterns. Both are explained in this chapter.
Neither work with the RDSP/RTNI two-board combination. These utilities
do not know how to make MVIP connections to the DSP resource in order to
dial. The only solution is to use a 232 or 432 voice board while you define
the tones. Then you replace the 232 or 432 voice board with the ATI board
combination.
Using GetTones
Amanda must recognize telephone switching system tone patterns when
performing supervised transfers. The Setup utility runs another utility,
named GetTones, to “learn” the tone patterns for ringing, busy, hang-up, and
reorder (also called fast busy).
Before running the GetTones utility, you must have satisfied all of the
following requirements:
• Define the dial codes. See “Chapter 7: Defining Dial Codes.”
• Connect ports 1 and 2 (the top RJ-14 jack of the first Brooktrout
board) to valid, working single-line extensions on the telephone
switching system.
• Know the extension number to which port 1 is connected.
• Verify that the extension to which port 1 is connected is not in any
hunt group, and does not have any call forwarding programmed.
60 Installing Amanda@Work.Group/DOS
• Verify that the extension to which port 2 is connected has outside
line access and can dial a test telephone number that is answered and
does not hang up after answering (time or weather lines are good
choices to call).
• Define a non-Amanda extension that has a telephone connected, is
not forwarded, and will not be answered. This becomes your Ring
No Answer (RNA) test station.
To define telephone switching system tone patterns:
1. Make sure that you have satisfied all the above requirements.
2. Run Setup as explained in “Running Setup” on page 49.
3. From the Configuration Utility menu, press 2 to select Telephone Sys-
tem Tone Patterns.
The GetTones for Brooktrout Voice Boards screen appears.
4. By default, the output file has the same name as your .PBX file. How-
ever, it ends with the extension .TON.
Chapter 8: Defining Tone Patterns 61
5. Enter the outdial code, port 1’s station number, the reorder code, and the
RNA station number. Use the Up Arrow, Down Arrow, Tab, or Enter
key to move from one entry to the next.
6. Press F4 to run GetTones.
GetTones obtains the ring, busy, reorder, and hangup patterns of the
telephone switching system. Messages appear on your screen as the util-
ity gets and tests these patterns.
outdial code Type the outside line access and telephone
numbers for a connection to test for tone pat-
terns (such as the time or weather number). For
example:
9,5551111
Then press Enter.
port 1 station number Type the extension for a standalone (no call
hunting or forwarding) single-line (analog) ex-
tension connected to port 1.
Then press Enter.
reorder code Type any dial code that generates a reorder tone
pattern on the telephone switching system.
Typically, invalid extension numbers work
well, for example, 555 generally works. If not,
try 444 or 777 or any number that generates a
fast busy tone pattern.
Then press Enter.
Ring No Answer
station number Type a non-Amanda extension that has a tele-
phone connected and is not answered or call
forwarded. If voice-announce or call-announce
is enabled, remember to enter the extension
plus the additional digit or digits that force the
extension to ring. For example, if the RNA test
station is 112, type:
1121-
Then press Enter.
62 Installing Amanda@Work.Group/DOS
NOTE:If you have problems with the GetTones utility, such as not
getting good patterns or not being able to verify a tone pat-
tern, try using AccuCall Plus, a Brooktrout utility that also
captures tone patterns. See “Using AccuCall Plus” on
page 62.
Using AccuCall Plus
The C:\AMANDA\PBX.DB\1001.TON file defines the tone patterns that the
telephone switching system returns to Amanda. Amanda recognizes these
tones and uses her knowledge of them when she transfers calls. AccuCall
Plus is a Brooktrout utility that allows you to set up ring, busy, reorder/fast
busy/error, and special tone (such as a fax CNG tone) definitions.
This section is primarily for running tests that create new .TON files. If your
telephone switching system performs inband signaling integration, you may
not need the Ring No Answer (RNA) or ringback pattern.
You might edit an existing file to adjust the cadence or the percentage of
variation. For example, suppose a ring is usually one second on followed by
three seconds off. However, sometimes it is a bit shorter or longer. You may
want to increase the percentage of variation to allow for the differences. If
the busy and reorder tones are very similar, you might need to reduce the
percentage of variation to differentiate between them.
Amanda must be shut down before you run AccuCall Plus.
To run AccuCall Plus:
1. If Amanda is running, shut down the Amanda system:
a. Press Alt+S (if Amanda is running as a standalone) or s (if
Amanda is running as a voice server).
b. Type in the password. (The default is AMandA with only the
first two and the last letter capitalized.)
c. Press Enter.
d. Press Y (to confirm the shutdown).
e. Press Y again (to reconfirm).
Chapter 8: Defining Tone Patterns 63
When the C:\AMANDA prompt appears, you can start running Accu-
Call Plus.
2. Change directory to C:\ACCUCALL by typing:
cd c:\accucall
3. Press Enter.
4. You can create a new 1001.TON file or edit an existing file.
To create a new 1001.TON file, run AccuCall by typing:
accucall
To edit an existing 1001.TON file, run AccuCall by typing:
accucall C:\AMANDA\PBX.DB\1001.TON
5. Press Enter.
The AccuCall Plus main screen has several options. The list of function
keys at the bottom of the screen indicate which keys go with each
option.
64 Installing Amanda@Work.Group/DOS
6. Select “AUTO RUN” by pressing F6.
Chapter 8: Defining Tone Patterns 65
To define the Ring No Answer (RNA) tone pattern:
1. Type a telephone number for an extension in the Phone No. field. This
extension number must not be forwarded, not in a hunt group, not in
hands free/speaker phone mode, and not be answered by anyone.
2. Type 3 in the Verification Count field. This is the number of times you
want to run the test.
3. Type 10 in the Minimum Cycles field. This is the number of rings Accu-
Call Plus will listen to before completing the test cycle.
4. Select Full (the default) as the value for the Frequency Range field.
The possible values are:
Full (300 Hz to 1700 Hz)
High (800 Hz to 1700 Hz)
This is the range of frequencies that AccuCall Plus listens to.
5. The Frequencies Detected Window displays the frequencies detected by
AccuCall Plus to characterize the tone.
6. The Cadence Detected Window displays the cadence that AccuCall Plus
detected to characterize the tone. (This is displayed as a horizontal bar
graph.)
7. Press F9 to begin the test.
8. After AccuCall Plus has determined the system tone pattern, you can
customize the tone description using the Edit Tones box:
Name: Example: Panasonic Double Ring
Type: Ring1 if single ring, single pause
Ring2 if double ring, single pause
Terminating: NO
Cadence: NO
Frequency1: Determined by test
Frequency2: Determined by test
66 Installing Amanda@Work.Group/DOS
PCPM Code: 8 (always for ring tones)
Quick Count: None
On Time: Determined by test
On Max Variation: Determined by test
On Min Variation: Determined by test
Off Time: Determined by test
Off Max Variation: Determined by test
Off Min Variation: Determined by test
9. Save the tone by pressing F8 (twice).
10. From the main screen, press F3 to go to the Filters screen. The Unde-
fined Tone Frequencies box on the right side of the screen lists any
undefined frequencies that were found by the test.
11. Add these frequencies to the Filter table on the left side. Write each fre-
quency in the Filter table, replacing the word “none” with the frequency.
12. Then press F10 to save this information and return to the main screen.
NOTE:All the listed frequencies must be at least 40 Hz apart
so Amanda can distinguish them.
To define the Busy tone pattern:
1. Fill in the telephone number for an extension that is offhook and
connected to either another internal extension or to an outside line.
2. Type 3 in the Verification Count field. This is the number of times you
want to run the test.
3. Type 10 in the Minimum Cycles field. This is the number of rings Accu-
Call Plus will listen to before completing the test cycle.
Chapter 8: Defining Tone Patterns 67
4. Select Full (the default) as the value for the Frequency Range field.
The possible values are:
Full (300 Hz to 1700 Hz)
High (800 Hz to 1700 Hz)
This is the range of frequencies that AccuCall Plus listens to.
5. The Frequencies Detected Window displays the frequencies detected by
AccuCall Plus to characterize the tone.
6. The Cadence Detected Window displays the cadence that AccuCall Plus
detected to characterize the tone. (This is displayed as a horizontal bar
graph.)
7. Press F9 to begin the test.
8. After AccuCall Plus has determined the system tone pattern, you can
customize the tone description using the Edit Tones box:
Name: Example: Panasonic Busy
Type: Busy1 if regular busy cadence
Busy2 if double busy cadence
Terminating: YES (always)
Cadence: NO
Frequency1: Determined by test
Frequency2: Determined by test
PCPM Code: 7 (always for busy tones)
Quick Count: None
On Time: Determined by test
On Max Variation: Determined by test
On Min Variation: Determined by test
Off Time: Determined by test
Off Max Variation: Determined by test
Off Min Variation: Determined by test
68 Installing Amanda@Work.Group/DOS
NOTE:A normal single busy tone is approximately 500 msec
on and 500 msec off.
9. Save the tone by pressing F8 (twice).
10. Press F8 to add the tone.
11. From the main screen, press F3 to go to the Filters screen. The Unde-
fined Tone Frequencies box on the right side of the screen lists any
undefined frequencies that were found by the test.
12. Add these frequencies to the Filter table on the left side. Write each fre-
quency in the Filter table, replacing the word “none” with the frequency.
Make sure that the busy frequencies are listed in the first four positions
in the table (these positions are for terminating tones). When a tone is a
terminating tone, Amanda does not wait for it to be repeated before tak-
ing control of the call.
13. Then press F10 to save this information and return to the main screen.
To define the Reorder/Fast Busy/Error tone pattern:
1. Type a telephone number for an invalid extension in the Phone No. field.
This extension number must return the reorder tone. For example, you
might use 777 or 888. Test this tone from a single-line telephone before
you run this test.
2. Type 3 in the Verification Count field. This is the number of times you
want to run the test.
3. Type 10 in the Minimum Cycles field. This is the number of rings Accu-
Call Plus will listen to before completing the test cycle.
4. Select Full (the default) as the value for the Frequency Range field.
The possible values are:
Full (300 Hz to 1700 Hz)
High (800 Hz to 1700 Hz)
This is the range of frequencies that AccuCall Plus listens to.
Chapter 8: Defining Tone Patterns 69
5. The Frequencies Detected Window displays the frequencies detected by
AccuCall Plus to characterize the tone.
6. The Cadence Detected Window displays the cadence that AccuCall Plus
detected to characterize the tone. (This is displayed as a horizontal bar
graph.)
7. Press F9 to begin the test.
8. After AccuCall Plus has determined the system tone pattern, you can
customize the tone description using the Edit Tones box:
Name: Example: Panasonic Reorder Tone
Type: Busy if normal reorder
Terminating: YES
Cadence: NO
Frequency1: Determined by test
Frequency2: Determined by test
PCPM Code: 7 (always for busy tones)
Quick Count: None
On Time: Determined by test
On Max Variation: Determined by test
On Min Variation: Determined by test
Off Time: Determined by test
Off Max Variation: Determined by test
Off Min Variation: Determined by test
9. Save the tone by pressing F8 (twice).
10. From the main screen, press F3 to go to the Filters screen. The Unde-
fined Tone Frequencies box on the right side of the screen lists any
undefined frequencies that were found by the test.
70 Installing Amanda@Work.Group/DOS
11. Add these frequencies to the Filter table on the left side. Write each fre-
quency in the Filter table, replacing the word “none” with the frequency.
Make sure that the reorder frequencies are listed in the first four posi-
tions in the table (these positions are for terminating tones).
12. Then press F10 to save this information and return to the main screen.
To finish AccuCall Plus:
1. Press F7 to save the tone file.
2. Type the file name C:\AMANDA\PBX.DB\1001.TON.
3. Press F8 to save the file.
AccuCall Plus will not allow you to save to file unless you have defined
all the filters. It will also refuse to save to file if any two frequencies are
within 40Hz of each other.
If you have two frequencies that are closer than 40Hz, the best strategy
is to select a value that is between them and then go back to edit every
tone pattern that contains the two frequencies and replace them with that
value. To edit tones press <F8> from the main menu.
4. Exit the AccuCall Plus program by pressing F10.
Chapter 9:
Defining Integration Patterns
Using the Trace File for Integration
If your telephone switching system supports DTMF integration (also called
inband integration), you can:
1. Perform tests that add integration information to the TRACE.OUT file.
2. Convert that information to a set of integration strings.
3. Add the integration strings to the 1001.PBX file in the
C:\AMANDA\PBX.DB directory using the Setup or JOVE utilities.
NOTE:See “Chapter 12: Utilities,” in Administering Aman-
da@Work.Place for information about JOVE.
Depending on the telephone switching system you selected when you
defined dial codes (see “Defining Dial Codes” on page 51), some of the
integration patterns might be already filled in. Many telephone switching
systems are programmable, so existing patterns on the System Integration
Patterns screen may still need modification.
Make sure you define dial codes before performing the procedures in this
chapter. Otherwise you will overwrite all the integration information as the
Setup utility creates the 1001.PBX file for you using The Amanda
Company’s predefined .PBX file for the PBX that you select.
72 Installing Amanda@Work.Group/DOS
Setting Up the Trace File
To check that trace files are being created:
1. If Amanda is running, shut down the Amanda system.
2. At the DOS prompt, type the following to go to the root directory:
CD\
3. Then press Enter.
4. Edit the Amanda.bat file by typing:
JOVE AMANDA.BAT
5. Then press Enter.
The JOVE editor appears on the screen. Towards the bottom of the page
is a line that starts RAMANDA. You are ready to proceed if the line
reads:
RAMANDA /t5 /s1300 %1 %2 %3
If not, edit the line so that it is identical to this line.
6. To save and close the file, press the four following key combinations in
order:
Ctrl+X
Ctrl+S
Ctrl+X
Ctrl+C
7. At the DOS prompt, change directories to the pbx database by typing:
CD\AMANDA\PBX.DB
Then press Enter.
8. Edit the Pbx file by typing:
JOVE 1001.PBX
9. Then press Enter.
Chapter 9: Defining Integration Patterns 73
10. Press Page Down display the lower portion of the file where the integra-
tion (if any) is displayed.
11. Use Down Arrow to move the cursor to the bottom of the file to a blank
line.
12. Type the following:
integration 10 ‘rrrrrrrrrr’
This new integration string will capture up to 10 digits of In Band Sig-
naling that will be displayed in the trace file for later inclusion in
1001.PBX.
13. To save and close the file, press the four following key combinations in
order:
Ctrl+X
Ctrl+S
Ctrl+X
Ctrl+C
14. At the DOS prompt, type:
CD\
15. Then press Enter.
16. Start Amanda by typing:
AMANDA
17. Then press Enter.
Creating Test Patterns
After enabling the Trace capability and restarting Amanda, the telephone
switching system must be programmed to perform the following
capabilities:
• Select an extension that forwards on Ring No Answer to Amanda.
• Select another extension that forwards to the above extension on
Ring No Answer.
74 Installing Amanda@Work.Group/DOS
• Select a third extension that forwards on Busy to Amanda.
• Select a fourth extension that forwards to the third extension on
Busy.
• Select a fifth extension that forwards all calls to Amanda.
• If applicable, create a hunt group that will forward back to Amanda
if the hunt group is busy or rings without answer.
• Create a Direct Inward Line by having an outside CO trunk line ring
at an extension that will forward on Ring No Answer and Busy to
Amanda. Tests 5 and 6 below do not have CO line identification en-
abled. Tests 7 and 8 do.
Running the Tests
To run the tests:
1. Start Amanda by typing the following at the DOS prompt:
amanda
2. Then press Enter.
Test 1
• Place a call to the extension that forwards on Ring No Answer to
Amanda. Once Amanda has received the forwarded call, hang up.
Test 2
• Place a call to the second extension that is forwarded to the first ex-
tension. When Amanda has received the call, hang up.
Test 3
• Place a call to the third extension that forwards on Busy to Amanda.
Make sure that the extension is offhook and connected to another ex-
tension or outside line. Once Amanda has received the busy forward-
ed call, hang up.
Chapter 9: Defining Integration Patterns 75
Test 4
• Place a call to the fourth extension that is busy forwarded to the third
extension. Make sure that both extensions are offhook and either
connected to each other, or to outside lines. Once Amanda has re-
ceived the busy forwarded call, hang up.
Test 5
• Call in on the CO line that is directed to an extension that is forward-
ed to Amanda on Ring No Answer. Make sure that CO Line ID is
disabled. Once Amanda receives the call, hang up.
Test 6
• Call in on the CO line that is directed to an extension that is forward-
ed to Amanda on Busy. Make sure that the CO Line ID is disabled.
Once Amanda receives the call, hang up.
Test 7
• Repeat test 5 with CO Line ID enabled.
Test 8
• Repeat test 6 with CO Line ID enabled.
Test 9
• Call directly into Amanda from any extension. When Amanda an-
swers the call, hang up.
Reading the Trace File
To read the trace file:
1. Shut down Amanda.
2. At the C:\AMANDA> prompt, type:
JOVE TRACE.OUT
76 Installing Amanda@Work.Group/DOS
3. Then press Enter.
The first line should read similar to:
Oct 09 15:51:00 Begin trace of Amanda…
4. Press Ctrl+S to perform a search.
5. Type the following search text:
Using dtmf
6. Then press Enter.
The JOVE editor searches for the first call’s integration string. The cur-
sor should move to the trace line that reads similar to:
Oct 09 15:53:00 ichan01: Using dtmf data:
#123
The # sign indicates a Ring No Answer forwarded call, and the 123 (for
example) is the extension that forwarded the call to Amanda. These dig-
its could be any combination of DTMF digits. For example, the AT&T
Partner sends:
#03##123#
The #03## is the Ring No Answer code, and the 123# is the extension
number that forwarded. Different telephone switching systems (and
often different models) send different digits.
7. WRITE DOWN THE INTEGRATION INFORMATION FOR THIS
CALL.
8. Press Ctrl+S again.
9. Keep the same search string by just pressing Enter.
You should progress to the next call’s digits.
10. WRITE DOWN THE INTEGRATION INFORMATION FOR THIS
CALL.
Chapter 9: Defining Integration Patterns 77
11. Repeat steps 8 through 10 until all 9 integration stings have been
recorded. Some of the strings may be identical (although the extension
may be different if you tested from different stations).
12. To return to the C:\Amanda> prompt, press the following key combina-
tions:
Ctrl+X
Ctrl+C
To decide what integration strings to add to 1001.PBX:
1. Look at the integration string from Test 1. This represents a Ring No
Answer call that forwarded to Amanda. Locate the characters that match
the extension number that forwarded. On your notepad, rewrite the
string so that the extension number is replaced by the lower case letter
r’s. For example, if your string was “#123”, then your new string would
be “#rrr”. In the case of the Partner example, the “#03##123# would be
changed to “#03##rrr#.
NOTE:You may have 2, 3, 4 or more digits in your extension
numbers. The number of r’s will match the number of
digits in your extension dial plan.
2. Go to the integration string for Test 2. It may be similar to the one
above, or it may contain a more complex string that has both the first
and second extensions listed. If the string is identical to the previous
string (for example, #03##123#), draw a line through it on your note-
pad.
If both extensions are listed, determine which number was the first
extension (originally called) and which was the second extension. If
your string looks similar to “#122123”, then the 122 was the second
extension, and 123 was the first extension. On your string, replace the
first extension with the lower case r’s and the first extension with lower
case s’s. Our example would look like “#sssrrr”. The Partner would
change from “#03##122#123#” to #03##sss#rrr#”.
3. The integration string from Test 3 may be identical to the string from
Test 1 (except for the extension number). If so, draw a line through it.
78 Installing Amanda@Work.Group/DOS
If not, then your switch sends a unique busy forwarded integration to
Amanda. For example, the string may look like “*123”. The “*” denotes
a busy forwarded call, and the “123” is the extension that forwarded.
Replace the “123” with lower case b’s. Your string would now look like
“*bbb”.
4. The integration string from Test 4 may be identical to the one from Test
3. If so, draw a line through it.
If not, then identify the first extension number and replace the number
with lower case b’s. Identify the second extension number and replace
the number with lower case s’s. Your string may have looked like
“*122123” and should now look like “*sssbbb”.
5. The integration string from Test 5 is to differentiate a trunk based call
from a station based transfer if the switch offers this level of differentia-
tion. If this string is identical to string one or three, draw a line through
it.
If not, evaluate the new string to see what other information was sent in
addition to “123” which is the forwarding extension. If the integration
string contains the trunk ID number (even though it is supposed to be
disabled), replace the numbers with either x’s (if the trunk ID is insignif-
icant).
6. Repeat step 5 for the string from Test 6, but replace the extension num-
ber with b’s rather than r’s.
7. Repeat step 5 for Test 7. If the string is identical to the one from Test 5,
draw a line through it.
8. Repeat step 5 for Test 8, but replace the extension number with b’s
rather than r’s. If the string is identical to the one from Test 6, draw a
line through it.
9. Test 9 captures the signaling for a direct call into voice mail. The inte-
gration string probably includes a prefix (usually 1 digit—but it could be
several digits) and the extension number of the calling user. Replace the
extension number with e’s.
Chapter 9: Defining Integration Patterns 79
10. It is extremely important that there are no duplicate integration patterns.
To make sure that each pattern is different, list them on a piece of paper,
then rewrite them changing all character codes to zeros. What is left are
dial code masks which must all be different. For example, using the fol-
lowing dial codes: 1***eee, #02#sss#rrr#, and #03##rrr#, the
dial code masks are 1***000, #02#000#000#, and #03##000#,
which are all different. If any dial code masks are the same, you must
modify the duplicates or delete them.
Adding Integration Strings
You can define integration patterns using either one of the following:
• The Setup utility
• The JOVE editor to edit 1001.PBX.
To define DTMF integration patterns using the Setup utility:
1. Run Setup as explained in “Running Setup” on page 49.
2. From the Configuration Utility menu, press 3 to select Telephone Sys-
tem Integration Patterns.
The Telephone Switch Type screen appears.
3. From the Telephone Switch Type screen, select the name of your .PBX
file then press Enter.
80 Installing Amanda@Work.Group/DOS
The Integration Patterns screen appears. Its first line tells the name and
code (a number between 1001 and 2001) for your switching system (if
they appear in the .PBX file). The following example shows a Toshiba
model.
4. Type a number of tenths of seconds in the Timeout box.
A value of 0 prevents integration. Any other value is the amount of time
that Amanda will wait for information from the telephone switching sys-
tem. A suggested value for this timeout is 10 (which equals 1 second). In
some cases you may need a value of 15 or 20.
Depending on the telephone switching system you selected when you
defined dial codes (see “Defining Dial Codes” on page 51), some of the
integration patterns might be already filled in.
NOTE:To move from the timeout field to the integration pat-
terns and vice versa, press Ctrl+Home.
5. Many telephone switching systems are programmable, so existing pat-
terns on the System Integration Patterns screen may still need modifica-
tion.
Chapter 9: Defining Integration Patterns 81
Do one or more of the following:
• Verify that the existing patterns are accurate by checking the man-
ual for your telephone switching system.
• Edit the existing patterns manually. (Select one, use the arrow keys
to move around, and type over anything that needs to be changed.)
For example, if the Ring No Answer pattern is #6rr, the rr stands for
any two-digit extension. If the #6 is accurate, but you plan to have
three or four-digit extension numbers, you must do some editing.
For three-digit numbers, change the Ring No Answer pattern to
#6rrr instead of #6rr. (See “Using Character Codes” on page 82 for
more information about rrr and other codes.)
• Delete a pattern by deleting all the characters in it.
To add integration strings to 1001.PBX using JOVE:
1. At the prompt, type:
CD PBX.DB
2. Then press Enter.
3. Type:
JOVE 1001.PBX
4. Then press Enter. This is the same file we edited earlier.
5. Press Down Arrow until you select the line that reads:
integration 10 ‘rrrrrrrrrr’
6. Press Delete to remove this line.
7. Take the integration strings you created in the previous procedure. Type
each one on a separate line in 1001.PBX. For example:
integration 10 ‘#03##rrr#
integration 10 ‘#03##sss#rrr#
integration 10 ‘#00#ee#
82 Installing Amanda@Work.Group/DOS
NOTE:The 10 is a suggested value for the timeout. 10 equals
1 second. Any other value is the amount of time that
Amanda will wait for information from the telephone
switching system. In some cases you may need a value
of 15 or 20. A value of 0 prevents integration.
These are in addition to the dial codes and any other integration strings
that may have been in the original file. Enter them at the end of the file.
Do not duplicate lines, but do remove any lines that are inaccurate.
8. To save and close the file, press the four following key combinations in
order:
Ctrl+X
Ctrl+S
Ctrl+X
Ctrl+C
To restart Amanda:
1. At the DOS prompt, type:
CD\
2. Then press Enter.
3. Type:
AMANDA
4. Then press Enter.
Using Character Codes
You must modify the DTMF patterns so that the integration patterns become
general (not specific to extensions 111 and 127). Call states and extension
information are defined by using one of the character codes shown below.
Each character code represents a call state, the position of the extension
number in the pattern, and the number of digits in the extension. When
inband signaling strings come from the telephone switching system, Amanda
compares them to the defined integration patterns and decides how to handle
the calls.
Chapter 9: Defining Integration Patterns 83
The character codes in the integration patterns are defined as follows:
Code Description
bBusy call state
When bbb (or bbbb) appears in the integration pattern, Amanda checks
the Busy Chain. If the Busy Chain is blank, she plays the custom busy
message for mailbox bbb (or bbbb) or the system busy message.
cANI or Caller ID digits
When a string of c’s appears in the integration pattern, Amanda stores the
DTMF characters at those locations in the port variable %H. With token
programming the %H can be used to identify callers and so forth.
eDirect dial call state (used to access a mailbox directly by Amanda asking
for a security code)
When eee (or eeee) appears in the integration pattern, Amanda assumes
the caller wants to log in to mailbox eee (or eeee) and asks for the security
code.
iImmediate record call state (plays the record tone and starts recording a
message)
When iii (or iiii) appears in the integration pattern, Amanda begins re-
cording a message for mailbox iii (or iiii) without playing a prompt first.
rRing-no-answer call state that indicates who the call was for and that it
was not answered
When rrr (or rrrr) appears in the integration pattern, Amanda checks the
Ring No Answer (RNA) Chain. If the RNA Chain is blank, she plays the
current greeting for mailbox rrr (or rrrr) or the system greeting.
See the configuration option “integration_greeting” on page 196 for in-
formation about how the system greeting can be played when an integrat-
ed call has both the rrr and sss (or rrrr and ssss) fields set.
sInformation regarding where the call came from (for handling message
replies)
If sss (or ssss) is found in the integration pattern along with b’s or r’s,
Amanda recognizes mailbox sss as the sender of the message—if one is
left.
TIP:When using s’s, the integration requires User IDs for all tele-
phones, even those in the file room and lobby.
84 Installing Amanda@Work.Group/DOS
Realize that the character codes you use define not only the placement of the
extension information in the pattern, but also the call state, that is, Ring No
Answer, Busy, Direct, and so forth. Therefore, you can control Amanda’s
behavior based upon your specific requirements. For example, if your
customer does not wish to allow for Busy call states, then modify the
integration character codes and replace the b’s with r’s.
Some telephone switching systems have timing problems that cause the first
DTMF digit to be missed. In such cases, it is useful to add integration
patterns that are variations of the current patterns. For example, you might
add a second pattern for Direct calls (1***eee in our example) as ***eee.
These are identical—except the first digit is missing in the second pattern.
You can also try reducing the delay time (Delay option on SMDI tab in Setup
utility).
Never remove leading digits from a pattern if they differentiate this pattern
from another or if they are “active” digits (such as r’s and b’s).
tTrunk call or CO line ID; this can also be used for dynamic port alloca-
tion
When ttt (or tttt) appears in the integration pattern, Amanda processes
mailbox ttt (or tttt) normally. Whenever a call comes in on trunk line 3,
for example, mailbox 3 is processed. If trunk lines 1 to 20 support two
companies that share an Amanda system, mailbox’s 1–10 can have
@G(990) in their Extension fields—causing Amanda to play one compa-
ny’s greeting. mailbox’s 11–20 can have @G(880) in their Extension
fields—causing Amanda to play the other company’s greeting.
xWild card that matches anything (use this carefully)
For example 6xxxx would match every inband signaling string that had
a 6 followed by four other characters.
Code Description
Chapter 9: Defining Integration Patterns 85
Running Integration Helper
If you know that your telephone switching system supports DTMF
integration, the Integration Helper utility also allows you to determine the
integration patterns.
Before running the Integration Helper be sure that you:
• Enable your telephone switching system for voice mail integration.
• Program a test extension for call coverage, or call forwarding on
Ring No Answer and Busy, to Amanda. The following procedure as-
sumes that this extension is 111, but it can be any extension.
• Make another extension available for placing test calls. The follow-
ing procedure assumes that this extension is 127.
To run Integration Helper:
1. Press F4 to run the Integration Helper utility.
The following appears on the screen:
Integration Helper—Waiting for a call on any
port…To abort press ESC…
2. Place sample calls by calling from the available extension (127) to your
test extension (111). Use these calls to generate DTMF tones so Integra-
tion Helper can capture them. You can capture Ring No Answer, Busy,
and Direct call codes—using extensions and CO trunk lines. See “Plac-
ing Test Calls” on page 86.
3. As a code is captured, it appears on the Edit Integration Pattern screen.
You see the captured pattern on two lines, one that is for display only
and the other which you edit. For example, you need to replace exten-
sion numbers with patterns such as rrr for ring no answer. (See “Using
Character Codes” on page 82 for more information.)
4. When you have finished, press Esc to return to the System Integration
Patterns screen. The screen should be filled with the captured DTMF
digits (per your edits) and the descriptions of those codes.
86 Installing Amanda@Work.Group/DOS
Placing Test Calls
You can place test calls of the following types:
Available extension (127) calls the test extension (111) for Ring No
Answer:
After a Ring No Answer condition occurs, the call should be forwarded to
the Integration Helper program which answers the call and captures the
DTMF digits played by the telephone switching system. You define what
type of test call you made.
Available extension (127) calls the test extension (111) while the test
extension is Busy:
Verify that the test extension (111) has been call forwarded Busy to the
single-line ports you have programmed for Amanda. Make the test extension
(111) Busy. From the available extension (127), call the test extension (111).
The test extension (111) should forward to the single-line ports immediately
after the Integration Helper captures the DTMF digits (if any).
Test extension (111) calls directly to Integration Helper:
From the test extension (111), call the single-line ports. Integration Helper
captures the DTMF digits (if any). Note that some telephone switching
systems use different codes depending upon whether this direct call was
made by dialing an extension or by pressing a message light. You should run
both tests if you suspect this to be true of your system.
Available extension (127) using a CO line calls in and rings the test
extension (111) for Ring No Answer:
From the available extension (127), select an outside CO line and call in to
where you are installing Amanda. When the receptionist answers, ask to be
blind transferred to the test extension (111), which should forward to the
Integration Helper after a certain number of rings.
Chapter 9: Defining Integration Patterns 87
Available extension (127) using a CO line calls in while the test extension
(111) is Busy:
Make the test extension (111) busy. From the available extension (127),
select an outside CO line and call the company where you are installing
Amanda. When the receptionist answers, ask to be blind transferred to the
test extension (111), which should forward to the Integration Helper
immediately.
Forward from Ring No Answer Example
You may have two patterns labeled “Forward from Ring No Answer.” Both
should contain the extension number (111) that was call forwarded to the
Integration Helper. This is the extension that did not answer. One of the
patterns may contain the available extension number you called from (127).
For example, suppose the integration patterns were:
#02#127#111#
and
#03##111
You replace the digits of the test extension (111, the extension that did not
answer) with r’s and the digits of the telephone from which the call was
made, 127, with s’s:
#02#sss#rrr#
and
#03##rrr
88 Installing Amanda@Work.Group/DOS
This takes care of extensions that have exactly three digits (such as 111 and
127). To handle four-digit extensions, for example, you would have used:
#02#ssss#rrrr#
and
#03##rrrr
Direct Call Example
As a result of the Direct test call, one pattern should be labeled “Direct
call…” and contain the extension number for the telephone from which you
called (111).
Replace the extension number with e’s. For example, change:
1***111
to:
1***eee
This takes care of extensions that have exactly three digits (such as 111 and
127). To handle four-digit extensions, for example, you would have used:
1***eeee
Forward from Busy Example
For patterns labeled “Forward from Busy,” you replace the extension number
that was busy with b’s. If there is a pattern that contains the extension from
which the call was made, replace the extension number with s’s.
Chapter 10:
Configuring Amanda
Using This Chapter
This chapter contains a questionnaire that helps you determine exactly how
your customer needs his Amanda system to be set up. It also guides you as
you configure an Amanda system for the first time. Fortunately, The
Amanda Company has configured Amanda so that over 90% of the
configuration options need no change whatsoever.
For a complete list of the configuration options, see “Chapter 18:
Configuration Reference.”
Using the Questionnaire
Use this “First Use” questionnaire to find out how your customers prefer to
use their Amanda system. Use the results as you run Setup, selection 4, to set
configuration options, and as you create the mailbox template (usually
mailbox 997). Then create mailboxes for users. It comes in both a standalone
and voice server version because setting up mailboxes is different in
Amanda Administrator.
Question Column
The questions address:
• How Amanda handles all callers.
• How Amanda interacts with most users. You assign new users the
options that give them an initial, usable mailbox configuration. After
90 Installing Amanda@Work.Group/DOS
each mailbox has been created, the System Administrator can
change these options, and the users themselves can change some op-
tions.
• System Administration issues.
During your interview with the client, you will use the Question and Circle
Response columns in this questionnaire to select the Amanda features for
this site.
Location Column
You will use the Location and Action columns to implement these features
on Amanda. The Location column uses this symbol → to separate the choices
you must make at each menu level to select the feature from the correct
Amanda screen. For example, “In the Setup utility, select System
Configuration Options→General Configuration→Incoming Calls” means “In
the Setup utility, first select Configuration Options, then select General
Configuration, then select Incoming Calls.”
In the voice server version of the questionnaire, questions 10, 12-23, and 25
(for Amanda Administrator), the Location column directs you to the default
mailbox template (usually 997) that you use to set up new mailboxes. The
Location column directions assume that you are already logged on to
Amanda Administrator and are displaying the Mailbox window. If not, use
one of the following procedures to display the default mailbox template.
To display the Mailbox window (if you are not logged onto Amanda
Administrator):
1. Start Amanda Administrator.
The Administrator Logon dialog box appears.
2. Enter your password in the Logon dialog box.
The mailbox List dialog box appears.
3. Enter 997 (or the mailbox for the default template).
The Mailbox window displays template 997.
Chapter 10: Configuring Amanda 91
To display the Mailbox window (if you are already logged onto Amanda
Administrator but displaying another window):
1. Click the Mailbox menu and select mailbox.
The mailbox List dialog box appears.
2. Enter 997 (or the mailbox for the default template).
The Mailbox window displays template 997.
The Location column includes the name of the configuration option (also
called a parameter) for each feature. The current options and their settings
are stored on the Amanda server in C:\AMANDA\INSTALL.CFG. You can
view them using the Setup utility. From Setup, select System Configuration
Options→Advanced Configuration→General.
Standalone Questionnaire
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
1) Amanda normally says “Please
hold while I try that extension for
you” as she transfers a call. This fea-
ture can be turned off.
Do you want Amanda to say “Please
hold….?”
YES In the Setup utility, select
System Configuration
Options→General
Configuration→
Incoming Calls.
Set the Amanda Says “Please Hold
While…” check box to T for True,
which is the default.
NO Amanda parameter is
please_hold
Set the Amanda Says “Please Hold
While…” check box to F for False
You can also bypass this message for
individual mailboxes using the Token
Programming Language (although
only blind transfers are supported).
2) Do you want Amanda to verify
that a caller is still on the telephone
before transferring the call to an op-
erator?
(Amanda asks the caller to “Say yes
at the tone” before transferring the
call.)
YES In the Setup utility, select
System Configuration
Options→General
Configuration→
Incoming Calls.
Set the Amanda Says “Please Say
‘Yes’…” check box to T for True.
NO Amanda parameter is
dtmf_gate
Set the Amanda Says “Please Say
‘Yes’…” check box to F for False,
which is the default.
92 Installing Amanda@Work.Group/DOS
3) Do you want callers to be able to
hold for busy extensions? YES In the Setup utility, select
System Configuration
Options→General
Configuration→
Incoming Calls.
Amanda parameter is
cancel_busy_hold
Set the Caller Can Hold check box to
T for True, which is the default.
NO Set the Caller Can Hold check box to
F for False.
4) If YES to 3, do you want active
or inactive hold?
On active hold, the caller is prompt-
ed to press * to remain on hold.
On inactive hold, the caller takes no
action to stay on hold.
(800 numbers benefit from using ac-
tive hold, because the caller cannot
leave the telephone unattended.)
ACTIVE In the Setup utility, select
System Configuration
Options→General
Configuration→
Incoming Calls.
Amanda parameter is
active_hold
Set the Active Hold check box to T for
True, which is the default.
INACTIVE Set the Active Hold check box to F for
False.
5) Do you want direct messages to
play the Name/Extension recording
instead of the mailbox’s greeting?
(A direct message is left in a user’s
mail box without attempting to ring
that user. By default, Amanda plays
the mailbox’s greeting. The Name/
Ext recording is shorter than the
mailbox’s greeting.)
YES In the Setup utility, select
System Configuration
Options→General
Configuration→
Incoming Calls.
Amanda parameter is
short_direct_send
Select the Play User’s Name and Ex-
tension Recording option.
NO Select the Play User’s Greeting option
(which is the default).
6) Do you want Amanda to answer
all incoming calls or only answer
when the operator cannot get to the
phone within a certain number of
rings?
(This decision can vary from port to
port.)
ALL CALLS In the Setup utility, select
System Configuration
Options→Advanced
Configuration→
Per Port.
Amanda parameter is
n_rings
Set N_RINGS to 1 for each port.
This is a per port setting. The default is
one ring on each port.
(Amanda is being set up as a primary
attendant.)
AFTER x
RINGS
What is x?
Set N_RINGS to x for each port,
where x in the number of rings. This is
a per port setting.
(Amanda is being set up as a second-
ary attendant.)
Standalone Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
Chapter 10: Configuring Amanda 93
7) Do you want callers who use the
company directory (411) to press *
to transfer to the mailbox being de-
scribed?
YES Global settings parameter
is tmo_dir_
transfer.
Set tmo_dir_transfer a number greater
than 0. The default is 2.
NO Set tmo_dir_transfer to 0.
8a) Do you want users and callers to
be able to listen to, rerecord, or can-
cel messages and greetings that they
create?
YES In the Setup utility, select
System Configuration
Options→General
Configuration→
Messages.
Amanda parameter is
end_rec_menu
record_menu
Set the Allow Listening To… check
box to T for True, which is the default.
NO Set the Allow Listening To… check
box to F for False.
8b) Do you want users and callers to
hear a prompt before they start re-
cording or just the beep?
The prompt is “Begin recording at
the tone. Finish by pressing # or
hanging up.”
PROMPT and
BEEP In the Setup utility, select
System Configuration
Options→Advanced
Configuration→
General.
Amanda parameters are
begin_rec_prompt
record_menu
Set begin_rec_prompt to T for
True, which is the default. Set
record_menu to T for True, which
is the default.
BEEP ONLY Set begin_rec_prompt to F for
False. Set record_menu to T for
True, which is the default.
9) When users listen to messages,
Amanda normally plays the messag-
es in chronological order.
Do you want users to hear urgent
messages first?
YES In the Setup utility, select
System Configuration
Options→General
Configuration→
Messages.
Amanda parameter is
urgent_to_front
Set the Urgent Messages First check
box to T for True, which is the default.
NO Set the Urgent Messages First check
box to F for False.
10) When a user listens to messag-
es, should Amanda start with his
first new (unheard) message or the
first message in his message list
(whether heard or unheard)?
NEXT NEW
MESSAGE In the Setup utility, select
System Configuration
Options→General
Configuration→
Messages.
Amanda parameter is
play_new_first
Set the Play Next New Message check
box to T for True.
FIRST MES-
SAGE IN
LIST
Set the Play Next New Message check
box to F for False, which is the default.
Standalone Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
94 Installing Amanda@Work.Group/DOS
11) What time stamp should a for-
warded message have? You can use
the time the message was recorded
or the time the message was for-
warded.
(When you use the time that the
message was recorded, the person
receiving the forwarded message
may think delivery was slow and be
confused—unless the person for-
warding the message adds a com-
ment.)
TIME RE-
CORDED In the Setup utility, select
System Configuration
Options→General
Configuration→
Messages.
Amanda parameter is
timestamp_
forwards
Select the Time Originally Recorded
option, which is the default.
TIME FOR-
WARDED Select the Time Forwarded option.
12) Do you want Amanda to tell the
user the date and time a message
was recorded before playing the
message?
This option can be modified for each
user.
YES In Amanda, select Users
menu, then enter 997 in
mailbox.
Set the D/T option to YES.
NO Set the D/T option to NO.
NOTE:A user can always get the
message date/time by press-
ing 74 during the message
even if this option is set to
NO.
13) If YES to 12, do you want
Amanda to say ‘today’ and ‘yester-
day’ instead of the exact date? This
option is set for all users.
YES In the Setup utility, select
System Configuration
Options→General
Configuration→
Messages.
Amanda parameter is
abbreviate_dates
Select the Amanda Says “Today” And
“Yesterday” For Dates option, (which
is the default).
NO Select the Amanda Always Says Full
Date option.
14) How many times should the
telephone ring before Amanda de-
cides the user is unavailable?
(After these rings, Amanda takes a
message, reroutes the call, or does
whatever she is configured to do for
Ring No Answer.)
1 2 3
4 5 6
7 8 9
In Amanda, select Users
menu, then enter 997 in
mailbox.
Set the Set Maximum Rings value to
the circled number. The current de-
fault is 0, which means 4 rings.
CAUTION: If you are using the U to-
ken in Extension fields (to perform a
partially supervised transfer), Maxi-
mum Rings must be set to 1.
15) Do you want users to be able to
turn Do Not Disturb on and off? YES In Amanda, select Users
menu, then enter 997 in
mailbox.
Set Do Not Disturb’s Lock to OFF.
NO Set Do Not Disturb’s Lock to ON.
Standalone Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
Chapter 10: Configuring Amanda 95
16) Do you want Do Not Disturb
initially ON or initially OFF? ON In Amanda, select Users
menu, then enter 997 in
mailbox.
Set Do Not Disturb to ON.
OFF Set Do Not Disturb to OFF.
17) Do you want users to be able to
turn call screening on and off?
(Call screening allows users to ac-
cept or reject calls based on who is
calling.)
YES In Amanda, select Users
menu, then enter 997 in
mailbox.
Set Screen Calls’ Lock to OFF.
NO Set Screen Calls’ Lock to ON.
18) Do you want call screening ini-
tially ON or initially OFF? ON In Amanda, select Users
menu, then enter 997 in
mailbox.
Set Screen Calls to ON.
OFF Set Screen Calls to OFF.
19) Do you want callers to leave
messages for the users they call? YES In Amanda, select Users
menu, then enter 997 in
mailbox.
Set Store Messages to YES.
Set Store Messages’s Max to a number
of seconds for each message.
NO Set Store Messages to NO;
make sure Copy Messages To is blank.
20) Do you want everyone to use
the same greeting (and in the same
voice) when the telephone is not an-
swered?
(NO allows each user to create his
own greeting.)
YES In Amanda, select Users
menu, then enter 997 in
mailbox.
Set Current Greeting’s Max to 0.
NO Set Current Greeting to 0;
set Current Greeting’s Max to a num-
ber of seconds for each user’s record-
ing.
Each user should record a greeting and
a Name/Extension recording. Until a
user records these, the system greeting
and Name/Extension recording are
used. When the user records Greeting
1, the Current Greeting setting chang-
es from 0 to 1 automatically. The user
may also control what greeting is used.
(Amanda@Work.Group/DOS pro-
vides 7 greetings per mailbox.)
Standalone Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
96 Installing Amanda@Work.Group/DOS
21) If YES to 20, do you want to use
Amanda’s system greeting or a
company-wide custom greeting
when a telephone is not answered?
(The system greeting is “Please
leave a message for” followed by
the system or custom Name/Exten-
sion recording.)
SYSTEM In Amanda, select Users
menu, then enter 997 in
mailbox.
Set Current Greeting to 0, which is the
default.
CUSTOM Set Current Greeting to 1. Record a
greeting for some mailbox (e.g., 445),
then use DOS to copy it (e.g.,
C:\VMB.DB\5\445\GRT1.VOX)
as GRT1.VOX for each mailbox as-
signed to a user. For 3-digit extensions
that start with 2, use:
COPY custom_grt
C:\VMB.DB\?\2??\GRT1.VOX
For 4-digit extensions that end with 5,
use:
COPY custom_grt
C:\VMB.DB\?\4???\GRT1.VOX
(Here, custom_grt is
C:\VMB.DB\5\445\GRT1.VOX.)
Update the mailbox template (997) be-
fore you create the other mailboxes.
Use the COPY command shown
above after the IDs have been created.
22) If callers are permitted to hold
when a user extension is BUSY (see
Question 3), do you want everyone
to use the same greeting (and in the
same voice)?
(NO allows each user to create his
own busy greeting.)
YES In Amanda, select Users
menu, then enter 997 in
mailbox.
Set Busy Message’s Max to 0.
NO Set Busy Message’s Max to a number
greater than zero, such as 45.
Each user should record a busy greet-
ing. Until a user records his busy
greeting, the system busy greeting is
used. The user may also control what
busy greeting is used.
Standalone Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
Chapter 10: Configuring Amanda 97
23) If YES to 22, do you want to use
Amanda’s system busy greeting or a
custom busy greeting?
(The system busy greeting explains
to the caller how to hold for the ex-
tension. If the caller presses *,
Amanda plays music, then retries
the extension. If it is still busy,
Amanda changes the prompt: the
caller can hold, enter another exten-
sion, or leave a message.)
SYSTEM In Amanda, select Users
menu, then enter 997 in
mailbox.
Set Busy Message to SYS.
CUSTOM Set Busy Message to CUS. Record the
busy message for a mailbox (e.g.,
445), then use DOS to copy that mes-
sage (e.g., C:\VMB.DB\5\445
\BUSY.VOX) as BUSY.VOX for
each user’s mailbox. For 3-digit exten-
sions that start with 2, use:
COPY custom_bsy
C:\VMB.DB\?\2??\BUSY.VOX
For 4-digit extensions that end with 5,
use:
COPY custom_bsy
C:\VMB.DB\?\4???\BUSY.VOX
(Here, custom_bsy is
C:\VMB.DB\5\445\BUSY.VOX.)
Update the mailbox template (997) be-
fore you create the other mailboxes.
Use the COPY command shown
above after the IDs have been created.
24) Do you want Amanda to let the
user know who the call is for?
(This is primarily for people who
answer calls for more than one per-
son or share a telephone.)
YES In Amanda, select Users
menu, then enter 997 in
mailbox.
Set ID Call? to YES.
NO Set ID Call? to NO.
25) If YES to 24, do you want
Amanda to let the user accept or re-
ject the call based on who it is for?
YES In Amanda, select Users
menu, then enter 997 in
mailbox.
Set Screen Calls to ON and ID Call? to
YES.
NO Use the settings already specified for
Screen Calls and ID Call? in questions
17, 18, and 24.
26) If YES to 25, do you want users
to hear:
• Both who is calling and who
the call is for.
• Only who the call is for.
BOTH In the Setup utility, select
System Configuration
Options→Advanced
Configuration→
General (Settings).
Amanda parameter is
modified_call_
screening
Set modified_call_
screening to F for False.
ONLY WHO
CALL IS FOR Set modified_call_
screening to T for True.
Standalone Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
98 Installing Amanda@Work.Group/DOS
27) Do you want to use a system or
custom Name/Extension recording?
(The system recording says the
mailbox number instead of the us-
er’s name. For example, if the user’s
mailbox is 143, Amanda says “For
mailbox 1-4-3.”)
NOTE: It is a good idea to have
someone with a good voice
make a Name/Extension
recording for each user, so
Amanda identifies users
by name on the first day,
even if you allow custom
name/ extension record-
ing.
SYSTEM In Amanda, select Users
menu, then enter 997 in
mailbox.
Set Name/Ext to NO. The users cannot
make recordings.
CUSTOM Set Name/Ext. to YES. Each user
should make a recording. Until a user
makes his recording, the system re-
cording is used.
28) Do you want to log information
about messages? If YES, the
MSG.LOG file will store:
• The date and time every mes-
sage is received
• The date and time every mail-
box is checked for messages
along with the DTMF the user
entered
YES In the Setup utility, select
System Configuration
Options→General
Configuration→
Messages.
The Amanda parameter is
msg_log
Set the Log Info About Messages
check box to T for True.
NO Set the Log Info About Messages
check box to F for False, which is the
default.
29) Do you want to log information
about accesses to mailboxes? If
YES, the USER.LOG file will store
the date, time, and mailbox when
any mailbox is accessed by DTMF.
This file can be analyzed for call
distributions and accesses by dates,
days, and times.
YES In the Setup utility, select
System Configuration
Options→General
Configuration→
Messages.
The Amanda parameter is
user_log
Set the Log Info About User Access
check box to T for True.
NO Set the Log Info About User Access
check box to F for False, which is the
default.
30) What password does the admin-
istrator want to use for Amanda?
(You may not want to write this
down, but be sure that it gets reset.
The default is AMandA with the
first two and the last letter capital-
ized.)
Write pass-
word here. In the Setup utility, select
System Configuration
Options→General
Configuration→
Password.
Amanda parameter is
password
Enter a password which contains no
more than eight letters. Passwords are
case-sensitive.
Standalone Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
Chapter 10: Configuring Amanda 99
31) What language should Amanda
use for prompts, such as “Please
hold…?”
(You can offer information in more
than one language, ask for details.)
ENGLISH
SPANISH
In the Setup utility, select
System Configuration
Options→General
Configuration→
General Defaults.
Amanda parameter is
prompt_file
Press F2 and select a language from
the drop down list in the Language list
box. ENGLISH is the default. If you
do not select English, you must also
install the prompts for the language.
32) Will Amanda be connected to a
printer so that you can print reports? YES In the Setup utility, select
System Configuration
Options→General
Configuration→
General Defaults.
Amanda parameter is
lpt_port
Set the Printer Attached To LPT value
to 1.
NO Set the Printer Attached To LPT value
to 0, which is the default.
33) Do you want to shut down
Amanda for disk maintenance and/
or tape backups?
YES In the Setup utility, select
System Configuration
Options→General
Configuration→
General Defaults.
Amanda parameter is
shutdown
Set the Shutdown For Maintenance
And Backups check box to T for True.
NO Set the Shutdown For Maintenance
And Backups check box to F for False.
34) If YES to 33), do you want
Amanda to shutdown once a week
or everyday?
WEEKLY
Write a day
and a time.
In the Setup utility, select
System Configuration
Options→General
Configuration→
General Defaults.
Amanda parameter is
shutdown
Select the Once A Week On [TUE] At
[01:30] option. The default is Tuesday
at 1:30 A.M.. You can specify a differ-
ent day from the TUE drop down list
box. You can enter a different time in
the 01:30 text box. Time value uses the
24-hour format (HHMM).
DAILY
Write down
the time.
Select the Everyday at <HHMM> op-
tion and enter the time at HHMM, us-
ing the 24-hour format.
35) What words do you want the
screen saver to display on the
Amanda computer?
(Write the words. The default is
“Buy more Amandas.")
Write a phrase. In the Setup utility, select
System Configuration
Options→General
Configuration→
General Defaults.
Amanda parameter is
advertising
At the Screen Saver Phrase text box,
enter the phrase. Recommended
length is up to 30 characters, but max-
imum length is 80.
Standalone Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
100 Installing Amanda@Work.Group/DOS
36) When users don’t delete mes-
sages, they accumulate. Do you
want to get rid of messages that have
been listened to and have been
around for a long time?
Be aware that deleted messages are
gone forever.
YES In the Setup utility, select
System Configuration
Options→Advanced
Configuration→
General (Settings).
Amanda parameter is
purge
See Action for Question 37.
NO Set Amanda parameter purge
to 0,
which is the default.
37) If YES to 36, write a number of
days (from 1 to 99) after which a
message that has been heard should
be deleted.
Write a num-
ber (1-99). In the Setup utility, select
System Configuration
Options→Advanced
Configuration→
General (Settings).
Amanda parameter is
purge
Set purge to x, where x is the num-
ber of days (1-90) after being heard
that a message is purged.
Standalone Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
Chapter 10: Configuring Amanda 101
37) Do you want to use the hold
music provided by The Amanda
Company or hold music and mes-
sages of your own?
The Amanda
Company N/A Amanda plays C:\AMAN-
DA\HOLD.VOX by default.
YOUR OWN There is no config option or mailbox
field for this.
To rerecord HOLD.VOX:
1. Shut down Amanda.
2. At the DOS prompt (C:\AMAN-
DA), type:
COPY HOLD.VOX MU-
SIC.VOX
so you can use this file later. If
you already have a MU-
SIC.VOX file, use another
name.
3. Restart Amanda.
4. Using the telephone, log in to
the system administrator mail-
box (999), select 8 for the Sys-
tem Administration menu, then
3 to record the busy-hold music.
5. Make your recording. It be-
comes the file C:\AMAN-
DA\HOLD.VOX and is played
by Amanda to callers on hold.
6. If you create HOLD0.VOX,
HOLD1.VOX, etc. Amanda
plays them after HOLD.VOX if
the extension remains busy.
Each one is created as
HOLD.VOX, and must be
changed to HOLDx.VOX with a
DOS command:
COPY HOLD.VOX
HOLDx.VOX
Do the recording for the real
HOLD.VOX (the first music/
message the caller hears) last.
Standalone Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
102 Installing Amanda@Work.Group/DOS
Voice Server Questionnaire
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
1) Amanda normally says “Please
hold while I try that extension” as
she transfers a call. This feature can
be turned off.
Do you want Amanda to say “Please
hold….?”
YES In the Setup utility, select
System Configuration
Options→General
Configuration→
Incoming Calls.
Amanda parameter is
please_hold
Set the Amanda Says “Please Hold
While…” check box to T for True,
which is the default.
NO Set the Amanda Says “Please Hold
While…” check box to F for False
You can also bypass this message for
individual mailboxes using the Token
Programming Language (although
only blind transfers are supported).
2) Do you want Amanda to verify
that a caller is still on the telephone
before transferring the call to an op-
erator?
(Amanda asks the caller to “Say yes
at the tone” before transferring the
call.)
YES In the Setup utility, select
System Configuration
Options→General
Configuration→
Incoming Calls.
Amanda parameter is
dtmf_gate
Set the Amanda Says “Please Say
‘Yes’…” check box to T for True,
which is the default.
NO Set the Amanda Says “Please Say
‘Yes’…” check box to F for False.
3) Do you want callers to be able to
hold for busy extensions? YES In the Setup utility, select
System Configuration
Options→General
Configuration→
Incoming Calls.
Amanda parameter is
cancel_busy_hold
Set the Caller Can Hold check box to
T for True, which is the default.
NO Set the Caller Can Hold check box to
F for False.
4) If YES to 3, do you want active
or inactive hold?
On active hold, the caller is prompt-
ed to press * to remain on hold.
On inactive hold, the caller takes no
action to stay on hold.
(800 numbers benefit from using ac-
tive hold, because the caller cannot
leave the telephone unattended.)
ACTIVE In the Setup utility, select
System Configuration
Options→General
Configuration→
Incoming Calls.
Amanda parameter is
active_hold
Set the Active Hold check box to T for
True, which is the default.
INACTIVE Set the Active Hold check box to F for
False.
Chapter 10: Configuring Amanda 103
5) Do you want direct messages to
play the Name/Extension recording
instead of the mailbox’s greeting?
(A direct message is left in a user’s
mail box without attempting to ring
that user. By default, Amanda plays
the mailbox’s greeting. The Name/
Ext recording is shorter than the
mailbox’s greeting.)
YES In the Setup utility, select
System Configuration
Options→General
Configuration→
Incoming Calls.
Amanda parameter is
short_direct_
send
Select the Play User’s Name and Ex-
tension Recording option.
NO Select the Play User’s Greeting option
(which is the default).
6) Do you want Amanda to answer
all incoming calls or only answer
when the operator cannot get to the
phone within a certain number of
rings?
(This decision can vary from port to
port.)
ALL CALLS In the Setup utility, select
System Configuration
Options→Advanced
Configuration→
Per Port.
Amanda parameter is
n_rings
Set N_RINGS to 1 for each port.
This is a per port setting. The default is
one ring on each port.
(Amanda is being set up as a primary
attendant.)
AFTER x
RINGS
What is x?
Set N_RINGS to x for each port,
where x in the number of rings. This is
a per port setting.
(Amanda is being set up as a second-
ary attendant.)
7a) Do you want users and callers
to be able to listen to, rerecord, or
cancel messages and greetings that
they create?
YES In the Setup utility, select
System Configuration
Options→General
Configuration→
Messages.
Amanda parameter is
end_rec_menu
record_menu
Set the Allow Listening To… check
box to T for True, which is the default.
NO Set the Allow Listening To… check
box to F for False.
7b) Do you want users and callers
to hear a prompt before they start re-
cording or just the beep?
The prompt is “Begin recording at
the tone. Finish by pressing # or
hanging up.”
PROMPT and
BEEP In the Setup utility, select
System Configuration
Options→Advanced
Configuration→
General.
Amanda parameters are
begin_rec_prompt
record_menu
Set begin_rec_prompt to T for
True, which is the default. Set
record_menu to T for True, which
is the default.
BEEP ONLY Set begin_rec_prompt to F for
False. Set record_menu to T for
True, which is the default..
Voice Server Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
104 Installing Amanda@Work.Group/DOS
8) When a user listens to messages,
should Amanda start with his first
new (unheard) message or the first
message in his message list (wheth-
er heard or unheard)?
NEXT NEW
MESSAGE In the Setup utility, select
System Configuration
Options→General
Configuration→
Messages.
Amanda parameter is
play_new_first
Set the Play Next New Message check
box to T for True.
FIRST MES-
SAGE IN
LIST
Set the Play Next New Message check
box to F for False, which is the default.
9) What time stamp should a for-
warded message have? You can use
the time the message was recorded
or the time the message was for-
warded.
(When you use the time that the
message was recorded, the person
receiving the forwarded
message may think delivery was
slow and be confused—unless the
person forwarding the message adds
a comment.)
TIME RE-
CORDED In the Setup utility, select
System Configuration
Options→General
Configuration→
Messages.
Amanda parameter is
timestamp_
forwards
Select the Time Originally Recorded
option, which is the default.
TIME FOR-
WARDED Select the Time Forwarded option.
10) Do you want Amanda to tell the
user the date and time a message
was recorded before playing the
message?
This option can be modified for each
user.
YES From the Mailbox win-
dow in Amanda Adminis-
trator, click the
button after the mailbox
box. Enter 997 in the
mailbox List dialog box
that appears.
From the Options group box, select the
Play Date & Time check box.
NO From the Options group box, clear the
Play Date & Time check box.
NOTE:A user can always get the
message date/time by press-
ing 74 during the message
even if this option is set to
NO.
11) If YES to 10, do you want
Amanda to say ‘today’ and ‘yester-
day’ instead of the exact date? This
option is set for all users.
YES In the Setup utility, select
System Configuration
Options→General
Configuration→
Messages.
Amanda parameter is
abbreviate_dates
Select the Amanda Says “Today” And
“Yesterday” For Dates option, (which
is the default).
NO Select the Amanda Always Says Full
Date option.
Voice Server Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
Chapter 10: Configuring Amanda 105
12) How many times should the
telephone ring before Amanda de-
cides the user is unavailable?
(After these rings, Amanda takes a
message, reroutes the call, or does
whatever she is configured to do for
Ring No Answer.)
1 2 3
4 5 6
7 8 9
From the Mailbox win-
dow in Amanda Adminis-
trator, click the
button after the mailbox
box. Enter
997 in the mailbox List di-
alog box that appears.
In the Options group box, the current
default for Adjust Maximum Rings is
0, which means 4 rings.
If the circled number is not 4, select
the Adjust Maximum Rings check box
and enter the circled number into the
text box.
CAUTION: If you are using the U to-
ken in Extension fields (to perform a
partially supervised transfer), Maxi-
mum Rings must be set to 1.
13) Do you want users to be able to
turn Do Not Disturb on and off? YES From the Mailbox win-
dow in Amanda Adminis-
trator, click the
button after the mailbox
box. Enter 997 in the
mailbox List dialog box
that appears.
From the Options group box, clear the
Do Not Disturb Lock check box.
NO From the Options group box, select the
Do Not Disturb Lock check box.
14) Do you want Do Not Disturb
initially ON or initially OFF? ON From the Mailbox win-
dow in Amanda Adminis-
trator, click the
button after the mailbox
box. Enter 997 in the
mailbox List dialog box
that appears.
From the Options group box, select the
Do Not Disturb check box.
OFF From the Options group box, clear the
Do Not Disturb check box.
15) Do you want users to be able to
turn call screening on and off?
(Call screening allows users to ac-
cept or reject calls based on who is
calling.)
YES From the Mailbox win-
dow in Amanda Adminis-
trator, click the
button after the mailbox
box. Enter 997 in the
mailbox List dialog box
that appears.
From the Options group box, clear the
Call Screening Lock check box.
NO From the Options group box, select the
Call Screening Lock check box.
Voice Server Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
106 Installing Amanda@Work.Group/DOS
16) Do you want call screening ini-
tially ON or initially OFF? ON From the Mailbox win-
dow in Amanda Adminis-
trator, click the
button after the mailbox
box. Enter
997 in the mailbox List di-
alog box that appears.
From the Options group box, select the
Call Screening check box.
OFF From the Options group box, clear the
Call Screening check box.
17) Do you want callers to be able
to leave messages for the users they
call?
YES From the Mailbox win-
dow in Amanda Adminis-
trator, click the
button after the mailbox
box. Enter 997 in the
mailbox List dialog box
that appears.
From the Messages group box, select
the Store check box and enter number
of seconds for each message into the
Maximum Length text box.
NO From the Messages group box, clear
the Store check box.
If the Copy Messages To text box has
a mailbox different from none, do the
following:
1 Select the Copy Messages To
check box.
2 Type none in the Copy Messages
To text box.
3 Clear the Copy Messages To
checkbox.
18) Do you want everyone to use
the same greeting (and in the same
voice) when the telephone is not an-
swered?
(NO allows each user to create his
own greeting.)
YES From the Mailbox win-
dow in Amanda Adminis-
trator, click the
button after the mailbox
box. Enter 997 in the
mailbox List dialog box
that appears.
From the Personal Greetings group
box, select the RNA Lock check box.
NO From the Personal Greetings group
box, clear the RNA Lock check box.
Each user should record a greeting and
a Name/Extension recording. Until a
user records these, the system greeting
and Name/Extension recording are
used. When the user records Greeting
1, the Current Greeting setting chang-
es from 0 to 1 automatically. The user
may also control what greeting is used.
(Amanda@Work.Group/DOS pro-
vides 7 greetings per mailbox.)
Voice Server Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
Chapter 10: Configuring Amanda 107
19) If YES to 18, do you want to use
Amanda’s system greeting or a
company-wide custom greeting
when a telephone is not answered?
(The system greeting is "Please
leave a message for" followed by
the system or custom Name/Exten-
sion recording.)
SYSTEM From the Mailbox win-
dow in Amanda Adminis-
trator, click the
button after the mailbox
box. Enter 997 in the
mailbox List dialog box
that appears.
From the Personal Greetings group
box, click the button after the
RNA box.
The Greeting List dialog box appears.
Select System and click OK.
From the Greeting List dialog box that
appears, select System.
CUSTOM From the Personal Greetings group
box, click the button after the
RNA box. When the Greeting List di-
alog box appears, select 1.
In the corresponding Max. Length text
box, enter the number of seconds for
the custom recording.
To create a company-wide custom
greeting, record a greeting for some
mailbox (e.g., 445), then use DOS on
the Amanda server after shutdown to
copy it (e.g., C:\VMB.DB\5\445
\GRT1.VOX) as GRT1.VOX for each
mailbox assigned to a user. For 3-digit
extensions that start with 2, use:
COPY custom_grt
C:\VMB.DB\?\2??\GRT1.VOX
For 4-digit extensions that start with 4,
use:
COPY custom_grt
C:\VMB.DB\?\4???\GRT1.VOX
(Here, custom_grt is
C:\VMB.DB\5\445\GRT1.VOX.)
Update the mailbox template (997) be-
fore you create the other mailboxes.
Use the COPY command shown
above after the IDs have been created.
Voice Server Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
108 Installing Amanda@Work.Group/DOS
20) If callers are permitted to hold
when a user extension is BUSY (see
question 3), do you want everyone
to use the same greeting (and in the
same voice)?(NO allows each user
to create his own busy greeting.)
YES From the Mailbox win-
dow in Amanda Adminis-
trator, click the
button after the mailbox
box. Enter 997 in the
mailbox List dialog box
that appears.
From the Personal Greetings group
box, select the Custom Busy Lock
check box.
NO From the Personal Greetings group
box, clear the Custom Busy Lock
check box. Set the Custom Busy Max.
Length to a number greater than zero,
such as 45.
Each user should record a busy greet-
ing. Until a user records his busy
greeting, the system busy greeting is
used. The user may also control what
busy greeting is used.
21) If YES to 20, do you want to use
Amanda’s system busy greeting or a
custom busy greeting?
(The system busy greeting explains
to the caller how to hold for the ex-
tension. If the caller presses *,
Amanda plays music, then retries
the extension. If it is still busy,
Amanda changes the prompt: the
caller can hold, enter another exten-
sion, or leave a message.)
SYSTEM From the Mailbox win-
dow in Amanda Adminis-
trator, click the
button after the mailbox
box. Enter 997 in the
mailbox List dialog box
that appears.
From the Personal Greetings group
box, clear the Custom Busy check box.
CUSTOM From the Personal Greetings group
box, select the Custom Busy check
box. Record the busy message for a
mailbox (e.g., 445), then use DOS on
the Amanda server after shutdown to
copy that message (e.g.,
C:\VMB.DB\5\445
\BUSY.VOX) as BUSY.VOX for
each user’s mailbox. For 3-digit exten-
sions that start with 2, use:
COPY custom_bsy
C:\VMB.DB\?\2??\BUSY.VOX
For 4-digit extensions that start with 4,
use:
COPY custom_bsy
C:\VMB.DB\?\4???\BUSY.VOX
(Here, custom_bsy is
C:\VMB.DB\5\445\BUSY.VOX.)
Update the mailbox template (997) be-
fore you create the other mailboxes.
Use the COPY command shown
above after the IDs have been created.
Voice Server Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
Chapter 10: Configuring Amanda 109
22) Do you want Amanda to let the
user know who the call is for?
(This is primarily for people who
answer calls for more than one per-
son or share a telephone.)
YES From the Mailbox win-
dow in Amanda Adminis-
trator, click the
button after the mailbox
box. Enter 997 in the
mailbox List dialog box
that appears.
From the Options group box, select the
Identify Called Party check box.
NO From the Options group box, clear the
Identify Called Party check box.
23) If YES to 22, do you want
Amanda to let the user accept or re-
ject the call based on who it is for?
YES From the Mailbox win-
dow in Amanda Adminis-
trator, click the
button after the mailbox
box. Enter 997 in the
mailbox List dialog box
that appears.
From the Options group box, select the
Call Screening check box.
NO Use the settings already specified for
Screen Calls and ID Call? in questions
15, 16, and 22.
24) If YES to 23, do you want users
to hear:
• Both who is calling and who
the call is for.
•Only who the call is for.
BOTH In the Setup utility, select
System Configuration
Options→Advanced
Configuration→ General
(Settings).
Amanda parameter is
modified_call_
screening
Set modified_call_
screening to F for False.
ONLY WHO
CALL IS FOR Set modified_call_
screening to T for True.
25) Do you want to use a system or
custom Name/Extension recording?
(The system recording says the
mailbox number instead of the us-
er’s name. For example, if the user’s
mailbox is 143, Amanda says “For
mailbox 1-4-3.”)
NOTE:It is a good idea to have
someone with a good
voice make a Name/Ex-
tension recording for
each user, so Amanda
identifies users by name
on the first day, even if
you allow custom name/
extension recording.
SYSTEM From the Mailbox win-
dow in Amanda Adminis-
trator, click the
button after the mailbox
box. Enter 997 in the
mailbox List dialog box
that appears.
From the Options group box, clear the
Record Name & Extension check box.
CUSTOM From the Options group box, select the
Record Name & Extension check box.
Each user should make a recording.
Until a user makes his recording, the
system recording is used.
Voice Server Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
110 Installing Amanda@Work.Group/DOS
26) Do you want to log information
about messages? If YES, the
MSG.LOG file will store:
• The date and time every mes-
sage is received
• The date and time every mail-
box is checked for messages
along with the DTMF the user
entered
YES In the Setup utility, select
System Configuration
Options→General
Configuration→
Messages.
The Amanda parameter is
msg_log
Set the Log Info About Messages
check box to T for True.
NO Set the Log Info About Messages
check box to F for False, which is the
default.
27) Do you want to log information
about accesses to mailboxes? If
YES, the USER.LOG file will store
the date, time, and mailbox when
any mailbox is accessed by DTMF.
This file can be analyzed for call
distributions and accesses by dates,
days, and times.
YES In the Setup utility, select
System Configuration
Options→General
Configuration→
Messages.
The Amanda parameter is
user_log
Set the Log Info About User Access
check box to T for True.
NO Set the Log Info About User Access
check box to F for False, which is the
default.
28) What password does the admin-
istrator want to use for Amanda?
(You may not want to write this
down, but be sure that it gets reset.
The default is AMandA with the
first two and the last letter capital-
ized.)
Write pass-
word here. In the Setup utility, select
System Configuration
Options→General
Configuration→
Password.
Amanda parameter is
password
Enter a password which contains no
more than eight letters. Passwords are
case-sensitive.
29) What language should Amanda
use for prompts, such as “Please
hold…?”
(You can offer information in more
than one language, ask for details.)
ENGLISH
SPANISH
In the Setup utility, select
System Configuration
Options→General
Configuration→
General Defaults.
Amanda parameter is
prompt_file
Press F2 and select a language from
the drop down list in the Language list
box. ENGLISH is the default. If you
do not select English, you must also
install the prompts for the language.
30) Will Amanda be connected to a
printer so that you can print reports? YES In the Setup utility, select
System Configuration
Options→General
Configuration→
General Defaults.
Amanda parameter is
lpt_port
Set the Printer Attached To LPT value
to 1.
NO Set the Printer Attached To LPT value
to 0, which is the default.
Voice Server Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
Chapter 10: Configuring Amanda 111
31) Do you want to shut down
Amanda for disk maintenance and/
or tape backups?
YES In the Setup utility, select
System Configuration
Options→General
Configuration→
General Defaults.
Amanda parameter is
shutdown
Set the Shutdown For Maintenance
And Backups check box to T for True.
NO Set the Shutdown For Maintenance
And Backups check box to F for False.
32) If YES to 31), do you want
Amanda to shutdown once a week
or everyday?
WEEKLY
Write a day
and a time.
In the Setup utility, select
System Configuration
Options→General
Configuration→
General Defaults.
Amanda parameter is
shutdown
Select the Once A Week On [TUE] At
[01:30] option. The default is Tuesday
at 1:30 A.M.. You can specify a differ-
ent day from the TUE drop down list
box. You can enter a different time in
the 01:30 text box. Time value uses the
24-hour format (HHMM).
DAILY
Write down
the time.
Select the Everyday at <HHMM> op-
tion and enter the time at HHMM, us-
ing the 24-hour format.
33) What words do you want the
screen saver to display on the
Amanda computer?
(Write the words. The default is
“Buy more Amandas.")
Write a
phrase. In the Setup utility, select
System Configuration
Options→General
Configuration→
General Defaults.
Amanda parameter is
advertising
At the Screen Saver Phrase text box,
enter the phrase. Recommended
length is up to 30 characters, but max-
imum length is 80.
34) When users don’t delete mes-
sages, they accumulate. Do you
want to get rid of messages that have
been listened to and have been
around for a long time?
Be aware that deleted messages are
gone forever.
YES In the Setup utility, select
System Configuration
Options→Advanced
Configuration→
General.
Amanda parameter is
purge
See Action for Question 35.
NO Set Amanda parameter purge
to 0,
which is the default.
35) If YES to 34, write a number of
days (from 1 to 99) after which a
message that has been heard should
be deleted.
Write a num-
ber (1-99). In the Setup utility, select
System Configuration
Options→Advanced
Configuration→
General.
Amanda parameter is
purge
Set purge to x, where x is the num-
ber of days (1-90) after being heard
that a message is purged.
Voice Server Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
112 Installing Amanda@Work.Group/DOS
36) Do you want to use the hold
music provided by The Amanda
Company or hold music and mes-
sages of your own?
The Amanda
Company N/A Amanda plays C:\AMAN-
DA\HOLD.VOX by default.
YOUR OWN There is no config option or mailbox
field for this.
To rerecord HOLD.VOX:
1. Shut down Amanda.
2. At the DOS prompt (C:\AMAN-
DA), type:
COPY HOLD.VOX MU-
SIC.VOX
so you can use this file later. If
you already have a MUSIC.VOX
file, use another name.
3. Restart Amanda.
4. Using the telephone, log in to the
system administrator mailbox
(999), select 8 for the System Ad-
ministration menu, then 3 to
record the busy-hold music.
5. Make your recording. It becomes
the file C:\AMAN-
DA\HOLD.VOX and is played
by Amanda to callers on hold.
6. If you create HOLD0.VOX,
HOLD1.VOX, etc. Amanda
plays them after HOLD.VOX if
the extension remains busy. Each
one is created as HOLD.VOX,
and must be changed to
HOLDx.VOX with a DOS
command:
COPY HOLD.VOX
HOLDx.VOX
Do the recording for the real
HOLD.VOX (the first music/
message the caller hears) last.
Voice Server Questionnaire (Continued)
Question Circle
Response Location and Amanda
Parameter (if applica-
ble) Action
Chapter 10: Configuring Amanda 113
Configuring a New Installation
Amanda has over 200 configuration options. They are what make Amanda
so powerful and flexible. You will probably leave over 90% of those options
set to their default settings. However, armed with the answers to the First
Use Questionnaire, you should review the most commonly changed options
(those in the General Configuration section of the Setup utility).
To set a new Amanda system’s general configuration options:
1. Run Setup as explained in “Chapter 6: Running the Setup Utility.”
The Work.Group/DOS Configuration Utility screen appears.
2. To select System Configuration Options, press 4.
The System Configuration menu appears.
3. To select General Configuration, press Enter.
The General Configuration menu provides easy access to the configura-
tion options you are most likely to change.
4. Press I for Incoming Calls.
The Incoming Calls screen appears.
Options with bracketed settings [T] or [F] are like Windows check
boxes. Using T for True is like checking a check box. Using F for False
is like clearing a check box. Pressing the space bar toggles between T
and F. Sometimes one check box is dependent on your selection for an
earlier check box. For example, in the Incoming Calls screen, if you do
not allow the caller to hold, the setting for active hold is ignored.
Options with settings that are in parentheses (*) or ( ) are like Windows
option buttons. You make a selection from the group of options by typ-
ing an asterisk in front of any one of the options. (Typing a space
removes an asterisk from one option; if there are only two options, the
asterisk automatically moves to the other option.)
114 Installing Amanda@Work.Group/DOS
5. For each check box, select T for True or F for False.
Type an asterisk (*) to select an option button.
(Press F1 for help with any setting you aren’t sure about.)
6. Press F10 to save your settings and Esc to return to the General Config-
uration screen.
7. Press M for Messages.
Chapter 10: Configuring Amanda 115
The Managing Messages screen appears.
8. For each check box, select T for True or F for False.
Type an asterisk (*) to select an option button.
(Press F1 for help with any setting you aren’t sure about.)
9. Press F10 to save your settings and Esc to return to the General Config-
uration screen.
10. Press P for Password.
The Password screen appears. Current Password is display-only.
11. Type the new password for Amanda in the Enter New Password text
box.
116 Installing Amanda@Work.Group/DOS
12. Press F10 to save your settings and Esc to return to the General Config-
uration screen.
13. Press G for General Defaults.
The General Defaults screen appears.
Language is an example of a list. Pressing F2 displays a list of choices
from which you select the language to be used.
Sometimes options are dependent on your selection for other options.
For example, in the General Defaults screen, only if you select the
Restricted option button can you access the Port text box and type the
number of the port to which notification is restricted. Likewise, only if
you select the Shutdown For Maintenance And Backups check box is it
important what days or time the shutdown occurs.
For more information about notification, see “Selecting a Type of Noti-
fication” on page 118.
14. For check boxes, select T for True or F for False.
Type an asterisk (*) to select an option button.
Select the day of the week from a list.
Type numbers for the ports and times.
Chapter 10: Configuring Amanda 117
Type a phrase for the screen saver.
Press F1 for help with any setting you aren’t sure about.
15. Press F10 to save your settings and Esc to return to the General Config-
uration screen.
16. If you have installed Amanda as a Voice Server, press Esc to return to
the System Configuration menu.
17. Press A for Advanced Configuration.
18. Press N for Network.
The Network Configuration screen appears.
Press F1 for help with the settings. Type in the appropriate numbers and
strings. If you type a space, the Setup utility interprets it as a zero.
NOTE:To set the client_activation_key and n_clients, see “Adding
Client Connections” on page 178. When n_clients is 0, you
have only one client. This allows you to run Amanda Ad-
ministrator to control Amanda Voice Server. Both
client_activation_key and the n_clients are read-only. You
cannot edit these two using the Setup utility.
118 Installing Amanda@Work.Group/DOS
Selecting a Type of Notification
Many telephones have message lights (also called message waiting lights) to
let users know that they have unheard messages. You use notification records
to turn the lights on and off. You can also notify users about waiting
messages by paging them, calling their extensions, or calling them at an
outside number.
Part of installing Amanda is selecting the type of notification:
•Roving
• Dedicated
• Restricted
With roving notification, Amanda tries to use the last port in the hunt group
(for example, port 4 on a 4-port system) for notification. If the last port is
busy, Amanda tries the second-to-last port (for example, port 3), and so forth.
If, on your telephone switching system, the port that turns on the message
light must also turn it off, you must have only one port perform notification
(control voice notify, message lights, paging, and so forth). You must use
dedicated or restricted notification, rather than the default roving
notification.
With dedicated notification, one port is used:
• Only for notification
BUT that port
•Cannot take incoming calls
Dedicated notification eliminates glare (the collisions between incoming
calls and notifications). However, you have one less port for receiving calls.
With restricted notification, one port is used:
• Only for notification
AND that port
•Can take incoming calls
Chapter 10: Configuring Amanda 119
With restricted notification, glare can still occur. However, all your ports can
be used for receiving calls.
See Administering Amanda@Work.Group/DOS for more information on
notification records.
If you are using JOVE to edit INSTALL.CFG, for roving notification, set
both n_ochan and notify_restriction to 0. For dedicated notification, set
n_ochan to 1 and notify_restriction to 0. For restricted notification, set
n_ochan to 0 and notify_restriction to a specific port number.
NOTE:When using roving or restricted notification, program your
phone system to have the ports in a linear hunt group (not
a circular hunt group). In a linear hunt group, port 1 always
rings first, port 2 rings only if port 1 is busy, and port 3 only
rings if port 1 and port 2 are both busy. Then when Aman-
da’s last port rings, all the other ports must be busy.
If a caller hears DTMF and then a hangup instead of the
company greeting, a collision has occurred.
Using Default and Recommended
Mailboxes
The following is a complete list of the default (and recommended)
mailboxes in case you need to change (or set) them. If two departments share
an Amanda system, you might use these mailboxes for one department and
create another set for the other department. (For more information about
sharing an Amanda system, see “Sharing Amanda” on page 155.) If you
intend to use the defaults, don’t overwrite these mailboxes when you create
new mailboxes for employees.
120 Installing Amanda@Work.Group/DOS
Default and Recommended mailboxes
Mailbox Configuration
Option Purpose
0(no option) Mailbox for operator or receptionist. Mailbox 0 has been created for
you.
By default, this mailbox has Do Not Disturb locked OFF, call screen-
ing locked OFF, Greeting 0 as the current greeting, 999 in the Done
Chain, stores messages, and is set to ring six times.
8(no option) Mailbox that acts as a shortcut to mailbox 998. Mailbox 8
makes it easier to send callers directly to voice mail. Live op-
erators press transfer, call Amanda, dial 8# followed by the
mailbox number, and hang up. The caller goes directly to voice
mail.
411 box_idx Mailbox for employee directory. Mailbox 411 has been created for
you.
By default, this mailbox has Do Not Disturb locked ON, call screening
locked OFF, Greeting 1 as the current greeting, an empty Done Chain,
and does not store messages.
990 box_grt Mailbox for Company Greeting. Mailbox 990 has been created for
you.
By default, this mailbox has Do Not Disturb locked ON, call screening
locked OFF, Greeting 1 as the current greeting, 991 in the Done Chain,
and does not store messages.
991 (no option) Mailbox for Caller Instructions. Mailbox 991 has been created for you.
By default, this mailbox has Do Not Disturb locked ON, call screening
locked OFF, Greeting 1 as the current greeting, 0 in the Done Chain,
and does not store messages.
Chapter 10: Configuring Amanda 121
994 hot_box Mailbox for use with PCPM codes. For example, you can set up a
hot_box to detect calls from modems. The mailbox 994 is recommend-
ed but has not been created for you. As you create a hot box mailbox,
make sure that the mailbox does NOT store messages and that Do Not
Disturb is off. In addition, the Extension field must transfer the caller
to the fax machine or whatever device is to be used by this box.
In most cases, only one hot_box is defined to detect fax tones and the
remainder are unused. However, you cannot separate these for compa-
nies or departments that share Amanda.
995 future_delivery Mailbox that stores messages to be delivered at some time in the future.
Mailbox 995 has been created for you.
By default, this mailbox has Do Not Disturb locked ON, call screening
locked OFF, Greeting 0 as the current greeting, nothing in the Done
Chain, and stores messages.
You don’t need to (and cannot) separate these for companies or depart-
ments that share Amanda.
996 guest_defaults Mailbox which is the template for all new guest mailboxes.Mailbox
996 has been created for you.
By default, this mailbox has Do Not Disturb OFF, call screening OFF,
Greeting 0 as the current greeting, nothing in the Done Chain, and
stores messages.
You cannot separate these for companies or departments that share
Amanda.
997 defaults_box Mailbox which is the template for all new mailboxes. Mailbox 997 has
been created for you.
You cannot separate these for companies or departments that share
Amanda.
998 box_snd Mailbox for direct messaging. Mailbox 998 has been created for you.
By default, this mailbox has Do Not Disturb locked ON, call screening
locked OFF, an empty Done Chain, and does not store messages.
Default and Recommended mailboxes (Continued)
Mailbox Configuration
Option Purpose
122 Installing Amanda@Work.Group/DOS
999 (no option) Mailbox for system administration and for a quick hangup. Mailbox
999 has been created for you.
You cannot separate these for companies or departments that share
Amanda.
By default, this mailbox has Do Not Disturb locked OFF, call screen-
ing locked OFF, an empty Done Chain, and an H in the Extension field.
Never change or delete this mailbox.
Default and Recommended mailboxes (Continued)
Mailbox Configuration
Option Purpose
Chapter 11:
Faxing
Using This Chapter
This chapter:
• Explains how to set up a fax modem for use with Amanda. This ap-
plies to any voice board supported by Amanda and applies to both
Amanda Standalone and Amanda Voice Server.
• Explains how to detect a fax machine automatically.
• Provides an overview of Amanda Fax, a fax driver for sending faxes
from any Windows application that can print. Amanda Fax is a client
of Amanda Voice Server. It cannot be used with Amanda Standal-
one.
Using a Fax Modem
You can use a fax modem on any Amanda@Work.Group/DOS system.
The fax modem used in Amanda may be internal or external as long as it
meets all of the following requirements:
• Class 2 or Class 2.0 compliant. (Be aware that Class 2 is different
from Class 2.0.)
• Internal fax modems must have a UART 16550 serial interface, and
external fax modems must be connected to UART 16550 serial
ports.
124 Installing Amanda@Work.Group/DOS
The MSD.EXE program in DOS can verify whether or not your PC has these
high speed serial ports. So can IS16550. (The syntax is IS16550 /x where x is
the number of the COM port.)
NOTE:If you have a Class 2 modem, the default configuration set-
tings for fax options should work well with your modem. If
you have a Class 2.0 modem, change the setting for
fax_send_reverse to F for False.
You must configure the fax modem for one of the following:
We recommend using COM1 and/or COM2 for fax modems. This port must
be dedicated to the fax modem.
NOTE:If you have a turnkey Amanda system, it comes with an in-
ternal modem which uses COM4 and IRQ5. This is used
only by the host software on the Amanda computer that al-
lows you to control Amanda from a remote site using the re-
mote program. None of Amanda’s configuration options
have anything to do with this modem, but the fax modem
cannot be set to COM4 or IRQ5. Even if your system is not
a turnkey system, we recommend that you install an inter-
nal data modem using the same COM port and IRQ so you
can contact Amanda remotely. If you ever need customer
support from The Amanda Company, this modem will
make it possible to solve your problem much more quickly.
See “Chapter 14: Accessing Amanda Remotely” for more
information about host and remote software.
To configure a fax modem for Amanda:
1. Run the Setup utility.
2. From the Work.Group/DOS Configuration Utility menu, select System
Configuration Options or press 4.
3. From the System Configuration menu, press A for Advanced Configura-
tion.
COM1 with IRQ4 and no other devices on COM1 or using IRQ4
COM2 with IRQ3 and no other devices on COM2 or using IRQ3
COM3 with IRQ11 and no other devices on COM3 or using IRQ11
Chapter 11: Faxing 125
4. From the Advanced Configuration menu, press S for Serial.
The Serial Port Definition dialog box appears.
(If you type a space, the Setup utility interprets it as a zero.)
5. Change:
serial_portn 0
To:
serial_portn y
The option maps Amanda's logical port to a physical port on the PC.
The n is the number of the logical serial port and the y is the physical
serial port (for example, COM1). It is best to make n and y the same
number. For example, map logical port 2 to COM2.
6. Modify the baudn, databitsn, stopbitsn, and parityn to
match the correct values for the serial integration link you are receiving.
The n is the number you used for n in step 5.
126 Installing Amanda@Work.Group/DOS
7. Press F10 to save your changes.
The Save All Data? dialog box appears.
8. Press Y for Yes.
9. From the Advanced Configuration menu, press F for Fax.
The Fax Configuration screen appears.
(If you type a space, the Setup utility interprets it as a zero.)
10. (Skip this step if you dial 9 to access an outside line.) In the Fax section
on Advanced Configuration, change:
fax_dl_init 9,
To:
fax_dl_init n
replace n with the outside access code for the telephone switching sys-
tem. (Adding a comma causes a 2-second pause.)
11. (Skip this step if you have a Zoom modem.) Change:
fax_flow_control &K3
Chapter 11: Faxing 127
For Aceex modems, use:
fax_flow_control \Q3 X3 &K3
For Practical Peripherals modems, use:
fax_flow_control X3 &K3
This option has the Class 2 command for the type of flow control used
by your fax modem.
12. Change:
fax_id
To:
fax_id fax
where fax is a number or a name used to identify your fax modem (for
example, 'FAXA')
13. Many older Class 2 fax modems need a string of leading digits ‘1111’
for their fax_id. By default, Amanda adds these digits.
However, if they appear on the receiving fax machine, change:
fax_id_pad T
To:
fax_id_pad F
14. Change:
faxn
To:
faxn ext
where n is the number for the logical serial port and ext is the extension
number where the fax modem is connected on the telephone switching
system (this must be a single line extension).
15. This defines the maximum number of digits for a local extension. This
is used when the “72” Fax retrieve command is selected so that
fax_dl_init (usually ‘9,’) will be applied only for outside calls.
128 Installing Amanda@Work.Group/DOS
Change:
max_local_extension 6
To:
max_local_extension n
where n is the maximum number of digits in a telephone extension on
your telephone switching system.
NOTE:You don’t need to change the default values for the other
serial port and fax configuration options.
To use the fax modem effectively, you must also use tokens
to program the Extension fields for one or more mailbox.
For more information, see the sections on one and two-call
faxbacks in “Chapter 11: Programming Examples,” in
Administering Amanda@Work.Group/DOS.
Suggested Settings
The following modems have been used with Amanda with the following
settings. This is not a comprehensive list, and many other modems work with
Amanda. The following settings are not even guaranteed to work with your
modem (even if your modem is one of those listed) because modem
manufactures produce a variety of models and change their firmware from
time to time. However, you may want to try them.
Zoom Modems
fax_flow_control &K3
fax_dl_init -
Aceex Modems
fax_flow_control \Q3 &K3
Practical Peripherals Modems
fax_flow_control X3 &K3
Chapter 11: Faxing 129
SmartOne 1442 Faxmodems
fax_flow_control &K4
fax_direct_connect H1O0
fax_receive_reverse T
fax_reset &D3
fax_send_reverse F
Boca modem M144EW
fax_flow_control &K3
Detecting a Fax Machine Automatically
Amanda can detect and accept incoming faxes automatically.
To automatically detect and accept an incoming fax:
• The fax connect tone must be in the PCPM tone table.
The tone information is stored in C:\AMANDA\PBX.DB\1001.TON.
The tone must be one of the first four tones or frequencies defined, and
it must be marked as a terminating tone. The PCPM code associated
with the tone must be in the range 12-21.
• A mailbox (usually 994) must be set up to process faxes. To learn
how to create and program that mailbox, see Administering Aman-
da@Work.Group/DOS.
• That mailbox must be specified in the hot_box configuration option.
Modifying the PCPM Tone Table
To modify the tone table for Brooktrout voice boards:
1. Run AccuCall Plus.
For more information about AccuCall Plus, see “Using AccuCall Plus”
on page 62.
130 Installing Amanda@Work.Group/DOS
2. To detect a FAX tone, use the following:
All other values can remain at their defaults.
NOTE:Remember to insert the FREQ1 value of 1100 into the filter
table in one of the first four positions. Only frequencies in
the first four positions are used for terminating tones.
Creating the Hot Box Mailbox
The Amanda Company recommends using mailbox 994 as the first hot_box,
but you can use any valid mailbox. Use the Users screen of Amanda
Standalone or the mailbox window of Amanda Administrator to create the
mailbox that will process the PCPM tone. See Administering
Amanda@Work.Group/DOS for information about creating mailboxes.
NAME: FAX CNG TONE
TYPE: OTHER
TERMINATING: YES
CADENCE: NO
FREQ1: 1100
FREQ2: NONE
PCPMCODE: 12 (12 through 21 are acceptable)
QUICKCOUNT: 400
ON TIME: 528
OFF TIME: 2976
Chapter 11: Faxing 131
Scenario #1: Blind transfer to fax machine
After calling Amanda, the caller presses the Start button on his fax machine
during the Company greeting (or some other greeting). Amanda recognizes
the tone and processes mailbox 994. mailbox 994 performs a blind transfer
to the fax machine. The Extension field for mailbox 994 must contain the
extension connected to the fax machine followed by an H (hangup).
Example Extension field:
1000H
where extension 1000 is connected to the fax machine
Scenario #2: Fax message left for user (who can view the fax using
Amanda Messenger)
The caller dials a user and presses the Start button on his fax machine during
the user’s greeting. Amanda recognizes the tone and processes mailbox 994.
mailbox 994 tells Amanda to create a fax message for the user who was
called. The Extension field for mailbox 994 contains tokens similar to the
following:
Example Extension field:
@J(%P,’’,’%X%F-H’)
which translates as the following:
@ Indicates to Amanda that she is to perform token programming
J() token Command that allows a fax to be received as a file or as a
message for a mailbox
%P Indicates that the owner of the most recently processed mailbox
is to receive the fax message
’’ Makes Amanda wait until a call rings into a fax port
%X System variable that contains the codes needed to transfer dial
tone on the current port
%F The extension of the fax port being used
-H A hangup (after pausing a half second to complete a blind
transfer)
132 Installing Amanda@Work.Group/DOS
Setting the Hot Box Options
You must let Amanda know the mailbox that will process the PCPM tone by
setting the hot_box configuration option.
To designate a mailbox to accept incoming faxes:
1. Run the Setup utility. At the DOS prompt, from the directory
C:\AMANDA, type:
SETUP
Then press Enter.
2. From the main menu, press 4.
The System Configuration Options menu appears.
3. From the System Configuration menu, type:
A
(for Advanced Configuration).
4. From the Advanced Configuration menu, type:
H
(for Hot Boxes).
5. Select the number that corresponds to the PCPM code.
6. Type the mailbox number next to the code.
Your typing replaces previous setting (by default -1 for no mailbox).
7. Press F10 to save.
Chapter 11: Faxing 133
Sending Faxes
If you are using Amanda as a voice server, you can install Amanda’s fax
driver—Amanda Fax. You can use Amanda Fax from any Windows
application that has a Print command. You can send documents,
spreadsheets, pictures, or anything else that the application can print. You
can:
• Fax an item to another location via Amanda Voice Server’s fax mo-
dem.
• Create a fax message to be mailed to users on your Amanda system.
• Save the item as a file that can be:
- Sent later as a fax via Amanda Voice Server’s fax modem.
For example, if you copy this file to Amanda Server using Amanda
Monitor, you can fax it to callers.
- Imported as a fax message.
To fax documents via Amanda Voice Server or create fax messages to be
sent via Amanda Messenger, you need a fax modem attached to and properly
configured for use with your Amanda Voice Server.
In all cases, you need Amanda Fax installed on each workstation from which
faxes will originate.
For details about installing and using Amanda Fax, see
Amanda@Work.Group/DOS Workstation Features. For details about
faxbacks, see the “Programming Examples” chapter in Administering
Amanda@Work.Group/DOS.
134 Installing Amanda@Work.Group/DOS
Chapter 12:
Using Serial Integration
Serial Integration Overview
Serial integration is a type of digital integration in which the telephone
switching system uses the computer’s serial port to communicate to
Amanda. A data line from the central office or telephone switching system
sends information and instructions (about the caller and called party) to your
on-site voice mail box.
For example, the telephone switching system can tell Amanda why the call
was transferred to Amanda, which extension the call is or was intended to go
to, and possible which extension the call is coming from. If you call Amanda
from an internal extension, Amanda recognizes you and asks only for your
security code. This makes getting your messages faster.
Amanda can support the following types of serial integration on Brooktrout
voice boards:
• Bellcore Standard
• NEC 2000 and NEC 2400
• AT&T System 75 or Definity-G3
• Generic which can apply to other types of serial integration when the
options are set correctly
NOTE:The Amanda Company recommends using a user’s tele-
phone extension number as his mailbox in all cases, but,
with digital integration, this one-to-one correspondence is
required.
136 Installing Amanda@Work.Group/DOS
Bellcore Standard SMDI
This section covers serial integration for any telephone switching system that
uses Bellcore Standard Simplified Message Desk Interface (SMDI). For
example, Centrex, Northern Telecom SL-1 with a VoiceBridge, and Fujitsu
F-9600 use SMDI.
To modify configuration options for use with Bellcore Standard SMDI:
1. Choose an available serial port on the computer. The serial port you use
must be COM1, COM2, COM3, or COM4.
Whatever serial port you use, make sure nothing else is configured to
use that port or the IRQ (hardware interrupt) configured for use with that
port.
2. Run Setup as explained in “Chapter 6: Running the Setup Utility.”
NOTE:As an alternative, you can use the JOVE utility to access the
configuration options in C:\AMANDA\INSTALL.CFG.
3. From the Work.Group/DOS Configuration Utility menu, select System
Configuration Options. You press 4.
4. From the System Configuration menu, press A for Advanced Configura-
tion.
5. From the Advanced Configuration menu, press S for Serial.
The Serial Port Definition dialog box appears.
(If you type a space, the Setup utility interprets it as a zero.)
Chapter 12: Using Serial Integration 137
6. Change:
serial_portn 0
To:
serial_portn y
The option maps Amanda's logical port to a physical port on the PC.
The n is the number of the logical serial port and the y is the physical
serial port (for example, COM1). It is best to make n and y the same
number. For example, use serial_port1 1 or serial_port2 2,
and so forth.
7. Modify the baudn, databitsn, stopbitsn, and parityn to
match the correct values for a serial integration link you are receiving.
The n is the number you used for n in step 6.
8. Press F10 to save your changes.
The Save All Data? dialog box appears.
138 Installing Amanda@Work.Group/DOS
9. Press Y for Yes.
10. From the Advanced Configuration menu, press I for SMDI.
The SMDI Configuration screen appears.
(If you type a space, the Setup utility interprets it as a zero.)
11. In the SMDI section of Advanced Configuration, change
smdi_port 0
To:
smdi_port n
where n is the number for n in step 6.
12. Verify that the smdi_type option is:
smdi_type 'smdi'
Change it if necessary.
13. Modify smdi_base_port 1 if the first port on the telephone switch-
ing system is not identified as the logical port 1. For example, some tele-
phone switching systems use the port’s extension or another logical
terminal number to identify the port.
Chapter 12: Using Serial Integration 139
The first port may be extension 241, with the second port 242, etc.
These numbers must be consecutive. For example, if the first or base
port is 241, you use smdi_base_port 241.
14. You can also set smdi_pretimeout n, where n is the maximum
number of seconds that an SMDI packet can precede the forwarded call.
The default is 50.
15. You can also set smdi_delay n, where n is the number of tenths of
seconds that Amanda waits after the call is answered before looking for
integration information. This allows more than one packet to be sent to a
port per telephone call. Amanda uses the last (most recent) packet. The
default is 0. The range is 0 to 255.
16. Press F10 to save your changes.
The Save All Data? dialog box appears.
17. Press Y for Yes.
NOTE:The smdi_max, smdi_start, smdi_stop, and smdi_term con-
figuration options do not apply to telephone switching sys-
tems that use Bellcore Standard SMDI.
You must also modify your C:\AMANDA\PBX.DB\1001.PBX file to
include the SMDI information. Using the Amanda Setup utility (selection 3)
or the JOVE utility, verify that your integration lines are as follows. When
using Setup, type 30 in the Timeout field. (30 equals 30 tenths of seconds or
a total of 3 seconds.) Then enter the integration strings in the column for the
extension plan your system uses. Use an <available> entry for each string
you are adding. (See “Using Character Codes” on page 82 for more
information about the codes such as rrr or rrrr.)
4-digit Extension Plan 3-digit Extension Plan
Forward no answer Axxxrrrr0000000 Axxxxrrr0000000
Forward no answer Bxxxbbbb0000000 Bxxxxbbb0000000
Forward no answer Nxxxrrrr0000000 Nxxxxrrr0000000
Forward no answer Axxxrrrrxxxssss Axxxxrrrxxxxsss
Forward busy Bxxxbbbbxxxssss Bxxxxbbbxxxxsss
140 Installing Amanda@Work.Group/DOS
If you are using the JOVE utility, the integration timeout precedes each
integration string as follows. This example is only for 4-digit station plans.
NOTE:To modify the above for another digit plan, use the appro-
priate number of r's, b's, s's, e's, and x's. Also, while 30 is
used in the example (causing Amanda to timeout after 3
seconds if the packet has not been received), you may use
some other number. The number is in tenths of seconds.
To program the message waiting lights, use the following in the Method field
of the two notification records used for Light ON and Light OFF:
Forward busy Nxxxrrrrxxxssss Nxxxxrrrxxxxsss
Direct station access Dxxxxxxxxxxeeee Dxxxxxxxxxxxeee
4-digit Station Plan
integration 20 'Axxxrrrr0000000'
integration 20 'Bxxxbbbb0000000'
integration 20 'Nxxxrrrr0000000'
integration 20 'Axxxrrrrxxxssss'
integration 20 'Bxxxbbbbxxxssss'
integration 20 'Nxxxrrrrxxxssss'
integration 20 'Dxxxxxxxxxxeeee'
4-digit Station Plan
Light ON: @S(1,'OP:MWI 000%U!\D')
Light OFF: @S(1,'RMV:MWI 000%U!\D')
3-digit Station Plan
Light ON: @S(1,'OP:MWI 0000%U!\D')
Light OFF: @S(1,'RMV:MWI 0000%U!\D')
Chapter 12: Using Serial Integration 141
NOTE:The message codes above are for a 4-digit and 3-digit sta-
tion plan. To modify to another digit plan, use the appropri-
ate number of 0's. These examples use logical serial port 1;
for other ports, the 1’s would have to be replaced.
NEC 2000 and NEC 2400
This section covers serial integration for NEC 2000 and NEC 2400 systems.
To set configuration options for serial integration on NEC 2000 or NEC
2400:
1. Follow steps 1 through 11 in the Bellcore Standard SDMI procedure “To
modify configuration options for use with Bellcore Standard SMDI:” in
the “Bellcore Standard SMDI” section.
2. Change the smdi_type option to:
smdi_type 'necmci'
3. Modify smdi_base_port 1 if the first port on the telephone switch-
ing system is not identified as the logical port 1. For example, some tele-
phone switching systems use the port’s extension or another logical
terminal number to identify the port. The first port may be extension
241, with the second port 242, etc. These numbers must be consecu-
tive. For example, if the first or base port is 241, you use
smdi_base_port 241.
4. You can also set smdi_pretimeout x, where x is the maximum
number of seconds that a packet can precede the forwarded call. Start
with 50, the default, but you may need to experiment to determine the
best setting. On the NEC 2000, one solution provider reports that 15 is a
good setting.
5. Set smdi_start option to the number that indicates the position in the
integration packet sent by the telephone switching system where the
field containing the port number starts. Start counting positions in the
packet with the number 1. The default is 8.
smdi_start 8
142 Installing Amanda@Work.Group/DOS
6. Set the smdi_stop option to the number that indicates the position in the
integration packet sent by the telephone switching system where the
field containing the port number ends. Start counting positions in the
packet with the number 1. The default is 11.
smdi_stop 11
7. You can also set smdi_delay x, where x is a number of tenths of sec-
onds. Amanda waits that long after the call is answered before looking
for integration information. This allows more than one packet to be sent
to a port per telephone call. Amanda uses the last (most recent) packet.
The default is 0.
NOTE:The smdi_max and smdi_term configuration options
do not apply to NEC telephone switching systems.
You must also modify your C:\AMANDA\PBX.DB\1001.PBX file to
include the SMDI information. Using the Amanda Setup utility (selection 3)
or the JOVE utility, verify that your integration lines are as follows. When
using Setup, type 20 in the Timeout field. (20 equals 20 tenths of seconds or
a total of 2 seconds.) Then enter the integration strings in the column for the
station plan your system uses. Use an <available> entry for each string you
are adding. (See “Using Character Codes” on page 82 for more information
about the codes such as rrr or rrrr.)
4-Digit Station Plan 3-Digit Station Plan
Forward no answer: 40xxxssssxxxxxrrrrxx 40xxxsssxxxxxxrrrxxx
Forward busy: 41xxxssssxxxxxbbbbxx 41xxxsssxxxxxxbbbxxx
Forward all: 42xxxssssxxxxxrrrrxx 42xxxsssxxxxxxrrrxxx
Direct station access: 43xxxeeeexxxxxxxxxxx 43xxxeeexxxxxxxxxxxx
Direct station access
from trunk: 432xxttttxxxxxxxxxxx 432xxtttxxxxxxxxxxxx
Chapter 12: Using Serial Integration 143
If you are using the JOVE utility, the integration timeout precedes each
integration string as follows. This example is only for 4-digit station plans.
NOTE:To modify the above for another digit plan, use the appro-
priate number of r’s, b’s, s’s, e’s, and x’s. In the example,
20 is used (causing Amanda to timeout after 2 seconds if
the packet has not been received) because it works for all
serial integration. The number is in tenths of seconds.
To program the message waiting lights for NEC 2000, use the following in
the Method field of the two notification records used for Light ON and Light
OFF:
To program the message waiting lights for NEC 2400 IMG, use the
following in the Method field of the two notification records used for Light
ON and Light OFF:
NOTE:These examples uses logical serial port 1; for other ports, the
1’s would have to be replaced.
4-Digit Station Plan
integration 20 '40xxxssssxxxxxrrrrxx'
integration 20 '41xxxssssxxxxxbbbbxx'
integration 20 '42xxxssssxxxxxrrrrxx'
integration 20 '43xxxeeeexxxxxxxxxxx'
integration 20 '432xxttttxxxxxxxxxxx'
Light ON: @S(1,’\002’)S(1,’0!A1’)S(1,’%U’)S(1,’\003’)
Light OFF: @S(1,’\002’)S(1,’0!A5’)S(1,’%U’)S(1,’\003’)
Light ON: @S(1,’\002’)S(1,’0!B2’)S(1,’%U’)
S(1,’0000000001’)S(1,’\003’)
Light OFF: @S(1,’\002’)S(1,’0!B6’)S(1,’%U’)
S(1,’0000000001’)S(1,’\003’)
144 Installing Amanda@Work.Group/DOS
AT&T System 75 or Definity-G3
If you use AT&T System 75 or Definity-G3 (smdi_type s75), call Amanda
Company customer support team for more information. Call to be faxed
Technical Note 14, “Serial Integration for System 75 and Definity-G3.”
To set configuration options for use with System 75 and Definity-G3:
1. Follow steps 1 through 11 in the Bellcore Standard SDMI procedure “To
modify configuration options for use with Bellcore Standard SMDI:” in
the “Bellcore Standard SMDI” section.
2. Change the smdi_type option to:
smdi_type 's75'
NOTE:Type 's75' with a lower case 's'. This option is case sensitive.
3. Modify smdi_base_port 1 if the first port on the telephone switch-
ing system is not 1. For example, some telephone switching systems use
the port’s extension or another logical terminal number to identify the
port. The first port may be extension 210, with the second port 211, etc.
(These numbers must be consecutive.) For example, if the first or base
port is 210, you use smdi_base_port 210.
4. You can also set smdi_delay x, where x is a number of tenths of sec-
onds causes Amanda to wait that long after the call is answered before
looking for integration information. This allows more than one packet to
be sent to a port per telephone call. Amanda uses the last (most recent)
packet. The default is 0.
5. Press F10 to save your changes.
The Save All Data? dialog box appears.
6. Press Y for Yes.
NOTE:The smdi_max, smdi_pretimeout, smdi_start, smdi_stop,
and smdi_term configuration options do not apply to
AT&T System 75 and Definity-G3 telephone switching
systems.
Chapter 12: Using Serial Integration 145
You must modify your C:\AMANDA\PDX.DB\1001.PBX file to properly
integrate the 7404D set information. Using either the Amanda Setup utility
or the JOVE utility, verify that your integration lines are:
integration 10 'xxxxxxxxxxxxxx*xxxxxxxxxxxxxxxxrrr D'
integration 10 'xxxxxxxxxxxxsssxxxxxxxxxxxxxxxxrrr D'
integration 10 'xxxxxxxxxxxxxx*xxxxAxxxxxxxxxxxrrr C'
integration 10 'xxxxxxxxxxxxeeexxxxAxxxxxxxxxxxxxx C'
integration 10 'xxxxxxxxxxxxxx*xxxxxxxxxxxxxxxxbbb B'
integration 10 'xxxxxxxxxxxxsssxxxxxxxxxxxxxxxxbbb B'
integration 10 'xxxxxxxxxxxxxx*xxxxxxxxxxxxxxxxrrr S'
integration 10 'xxxxxxxxxxxxsssxxxxxxxxxxxxxxxxrrr S'
integration 10 'xxxxxxxxxxxxxx*xxxxxxxxxxxxxxxxrrr x'
integration 10 'xxxxxxxxxxxxsssxxxxxxxxxxxxxxxxrrr x'
NOTE:The integration lines above are for a three (3) digit station
plan. When you have a mixed dialing plan, (for example, 3
and 4 digit extensions) you must have integration strings to
handle ALL possible combinations.
To modify to another digit plan, use the appropriate num-
ber of r’s, b’s, s’s, e’s, and x’s. The proper integration lines
vary depending on your System 75 software release, digital
telephone set model, and the data cartridge that you use in
the digital set. If you experience problems with the integra-
tion strings defined above, run option 3 in the Setup utility
(Integration Helper) to assist you, or contact Amanda Com-
pany customer support.
Also, you need to defined the telephones system dial code “What to dial
when a port goes off-hook” with the code you defined above in FEATURE
ACCESS CODE Call Pickup Access Code.
Finally, you must create mailboxes for each extension number where
Amanda’s ports are connected. The parameters must be defined as follows:
Extension: @G(990)
Do Not Disturb: OFF LOCK: ON
Store Messages? NO
Chains RNA: 990
Chains Busy: 990
146 Installing Amanda@Work.Group/DOS
Mailbox 990 is the default Company Greeting mailbox. If you have
redefined the Company Greeting mailbox for any of the ports, use that
mailbox instead of 990.
NOTE:The examples use %U (for mailbox), but you may prefer
%E (for Extension field) or %V (for Variable field). You
can use %E when the Extension field contains only the ex-
tension number. (For example, if the Extension field con-
tains an H for a blind transfer or starts with a @, %E is
unusable.) You can use %U only if the mailbox is the same
as the extension number. If you use %V, the Variable field
in the notification record must contain the extension num-
ber.
The *4 and #4 are the AT&T default values, often left as the standard, but
fully configurable. Watch out for dialplan conflicts if you change them
because the conflicts can slow down system operation if a needed wait for
dial timeout (that is, a four-digit speedial code) has the same first few digits
as the message waiting light feature.
Ericsson MD-110
This section covers serial integration for the Ericsson MD-110 system.
To set configuration options for serial integration on Ericsson MD-110:
1. Follow steps 1 through 11 in the Bellcore Standard SDMI procedure “To
modify configuration options for use with Bellcore Standard SMDI:” in
the “Bellcore Standard SMDI” section.
2. Change the smdi_type option to:
smdi_type 'md110'
Light ON: *4%U
Light OFF: #4%U
Chapter 12: Using Serial Integration 147
3. Modify smdi_base_port 1 if the first port on the telephone switch-
ing system is not identified as the logical port 1. For example, some tele-
phone switching systems use the port’s extension or another logical
terminal number to identify the port. The first port may be extension
241, with the second port 242, etc. These numbers must be consecu-
tive. For example, if the first or base port is 241, you use
smdi_base_port 241.
4. You can also set smdi_pretimeout x, where x is the maximum
number of seconds that a packet can precede the forwarded call. Start
with 50, the default, but you may need to experiment to determine the
best setting.
5. Set the smdi_start option to the number of digits in your extension plan.
For example, the following indicates that you have three-digit exten-
sions.
smdi_start 3
6. (Optional) Set the smdi_stop option to the number of digits in your port
number information that the telephone switching system will send. This
number will usually be 2.
smdi_stop 2
7. You can also set smdi_delay x, where x is a number of tenths of
seconds. Amanda waits that long after the call is answered before look-
ing for integration information. This allows more than one packet to be
sent to a port per telephone call. Amanda uses the last (most recent)
packet. The default is 0.
NOTE:The smdi_max and smdi_term configuration options
do not apply to Ericsson MD-110 telephone switching
systems.
You must also modify your C:\AMANDA\PBX.DB\1001.PBX file to
include the SMDI information. Using the Amanda Setup utility (selection 3)
or the JOVE utility, verify that your integration lines are as follows. When
using Setup, type 10 in the Timeout field. (10 equals 10 tenths of seconds or
a total of 1 second.) Then enter the integration strings in the column for the
station plan your system uses.
148 Installing Amanda@Work.Group/DOS
Use an <available> entry for each string you are adding. (See “Using
Character Codes” on page 82 for more information about the codes such as
rrr or rrrr.)
If you are using the JOVE utility, the integration timeout precedes each
integration string as follows. This example is only for 4-digit station plans.
4-Digit Station Plan 3-Digit Station Plan
Forward no answer: 80rrrrxx 80rrrxx
Direct station access: 81eeeexx 81eeexx
Direct station access: 82eeeexx 82eeexx
Forward no answer: 83ssssrrrrxx 83sssrrrxx
Forward no answer: 85rrrrxx 85rrrxx
Forward no answer: 86rrrrxx 86rrrxx
Forward no answer: 91ssssrrrrxx 91sssrrrxx
Forward busy:92ssssbbbbxx 91sssbbbxx
Forward no answer: 94rrrrxx 94rrrxx
Forward busy:95bbbbxx 95bbbxx
3-Digit Station Plan
integration 10 '80rrrxx'
integration 10 '81eeexx'
integration 10 '82eeexx'
integration 10 '83sssrrrxx'
integration 10 '85rrrxx'
integration 10 '86rrrxx'
integration 10 '91sssrrrxx'
integration 10 '92sssbbbxx'
Chapter 12: Using Serial Integration 149
NOTE:The number of x’s in the above strings is equal to the value
of smdi_stop, while the number of r’s, e’s, b’s, and s’s is
equal to the value of smdi_start. To modify the above for
another digit plan, use the appropriate number of r’s, b’s,
s’s, e’s, and x’s. In the example, 10 is used (causing
Amanda to timeout after 1 second if the packet has not been
received) because it works for all serial integration. The
number is in tenths of seconds.
To program the message waiting lights for NEC 2000, use the following in
the Method field of the two notification records used for Light ON and Light
OFF:
\B represents Ctrl+B, the start of transmission (STX) character. %E should
be the same number of digits and smdi_start specifies.
NOTE:These examples uses logical serial port 3; for other ports, the
3’s would have to be replaced.
Generic
This section covers a generic serial integration. It is designed for any
telephone switching system using serial integration other than those that:
• Use Bellcore Standard SMDI
• Are NEC 2000 or NEC 2400 systems
• Are AT&T System 75 or Definity-G3 systems
integration 10 '94rrrxx'
integration 10 '95bbbxx'
Light ON: @S(3,’\B06%E01\N’)
Light OFF: @S(3,’\B07%E01\N’)
150 Installing Amanda@Work.Group/DOS
To set configuration options for generic serial integration:
1. Follow steps 1 through 11 in the Bellcore Standard SDMI procedure “To
modify configuration options for use with Bellcore Standard SMDI,” in
the “Bellcore Standard SDMI” section.
2. Change the smdi_type option to:
To:
smdi_type 'generic'
3. Modify smdi_base_port 1 if the first port on the telephone switch-
ing system is not identified as the logical port 1. For example, some tele-
phone switching systems use the port’s extension or another logical
terminal number to identify the port. The first port may be extension
241, with the second port 242, etc. These numbers must be consecu-
tive. For example, if the first or base port is 241, you use
smdi_base_port 241.
4. You can also set smdi_pretimeout n, where n is the maximum
number of seconds that an SMDI packet can precede the forwarded call.
The default is 50.
5. You must set smdi_start n, where n is the position in the integra-
tion packet sent by the telephone switching system where the field con-
taining the port number starts. Start counting positions in the packet with
the number 1. The default is 8.
6. You must set smdi_stop n, where n is the position in the integration
packet sent by the telephone switching system where the field contain-
ing the port number ends. Start counting positions in the packet with the
number 1. The default is 11.
7. You must set smdi_max n, where n is the maximum number of char-
acters expected/accepted per packet. The default is 143.
8. You must set smdi_term n, where n is the termination character set
(if there is one). Leave this option empty if the packets are terminated
only by receiving smdi_max characters.
Chapter 12: Using Serial Integration 151
9. You can also set smdi_delay n, where n is the number of tenths of
seconds that Amanda waits after the call is answered before looking for
integration information. This allows more than one packet to be sent to a
port per telephone call. Amanda uses the last (most recent) packet. The
default is 0. The range is 0 to 255.
You must also modify the system integration patterns (stored in
C:\AMANDA\PBX.DB\1001.PBX) using the Amanda Setup utility
(selection 3) or the JOVE utility. You may need to write appropriate
notification records to turn message lights on and off. Consult your PBX
manual for this information.
152 Installing Amanda@Work.Group/DOS
Chapter 13:
Miscellaneous
Configuring Types of Lines
Most people connect Amanda to standard analog lines known as loop start
lines that indicate a new call by sending an AC voltage to the telephone
ringer.
You can also connect Amanda to Direct Inward Dialing (DID) lines with an
appropriate DID interface unit. Amanda assumes that you have a DID
interface unit, such as Exacom DID-200 Series, that processes a hookflash as
battery reversal.
When you use DID, Amanda receives the last few digits of the dialed
number. Those digits are used as (or modified by programming to be) the
internal extension. Then the caller does not have to enter an extension.
Use the following Telephone Line Options Diagram to determine what
configuration settings you need.
CAUTION:The configuration option ring_mode is a global set-
ting. If any lines into Amanda are loopstart (such as
those that perform notification records), ring_mode
must be true.
154 Installing Amanda@Work.Group/DOS
Telephone Line Options Diagrams
Chapter 13: Miscellaneous 155
Sharing Amanda
Sometimes more than one company or department share an Amanda system.
Specific ports are assigned to specific groups. For example, on a two-port
system shared by two companies, one company receives calls on port 1 and
another on port 2. This affects the configuration options that determine
which mailbox is used for:
156 Installing Amanda@Work.Group/DOS
• The company or initial greeting that callers hear when they call one
of the companies.
• The caller instructions greeting for each company.
The mailbox/extension for each company when 0 is dialed for the opera-
tor needs to be included in the menu for this mailbox.
• The employee directory that contains the names of all the users as
they appear in the Directory Name 1 and Directory Name 2 fields.
• The direct message mailbox that allows you to record a message for
a mailbox without having to transfer to that extension. You hear ei-
ther the mailbox’s greeting or the name and extension recording (de-
pending on the setting for the short_direct_send configuration
option). For example, you can leave a message for someone that you
know is out of the office or not to be disturbed.
When multiple companies share an Amanda system, they divide the ports
between them by doing either of the following:
• Dedicating each port to a specific company greeting using the
box_grt configuration option.
• Identifying the incoming CO lines with the Amanda mailbox that has
the same ID number. (To use this method, the telephone switching
system must send some sort of CO line ID number.)
This tenant services feature is based on dynamic port allocation, which
means that any Amanda port can receive the calls for any company shar-
ing the Amanda system. This eliminates the need for dedicating ports to
each company.
Using the box_grt Configuration Option
Typically, you dedicate each port to a specific company greeting using the
box_grt configuration option.
To use the box_grt:
• In the Per Port section of Advanced Configuration, change the mail-
box for the company greeting on a per port basis.
Suppose the first company uses ports 1 and 2, and the second company
uses ports 3 and 4. Then box_grt for ports 1 and 2 might be set to mail-
box 990, while box_grt for ports 3 and 4 might be set to mailbox 880.
Chapter 13: Miscellaneous 157
Using Incoming Trunk Call and CO Line IDs
Most telephone switching systems use three or four digit numbers to identify
a trunk call or CO line. You can use these IDs for dynamic port allocation by
doing all of the following:
• Adding the appropriate integration string to the 1001.pbx (and/or
2001.pbx) file.
Depending on the number of digits in the ID, you use ttt or tttt in your
integration string.
To capture the inband signalling information you need for the integra-
tion string, you need to use one of the following:
- A digit grabber/line monitor
- A dummy integration string
Then you edit the trace.out file to see the actual characters sent.
• Creating mailboxes that match the IDs.
The Extension field of each mailbox must direct the call to the appropri-
ate company greeting.
To create the appropriate integration string using a digit grabber:
1. Place a trunk call into Amanda over a CO line (for example CO line
701).
2. Write down the exact character string sent (as reported by the digit grab-
ber).
For example, it might be #01##701#.
158 Installing Amanda@Work.Group/DOS
3. Run the Setup utility as explained in “Running Setup” on page 49.
4. From the Configuration Utility menu, press 3 to select Telephone Sys-
tem Integration Patterns.
The Telephone Switch Type screen appears.
5. From the Telephone Switch Type screen, select the name of your .PBX
file then press Enter.
The Integration Patterns screen appears. Its first line tells the name and
code (1001 or 2001) for your switching system (if they appear in the
.PBX file).
NOTE:To move from the timeout field to the integration pat-
terns and vice versa, press Page Up or Page Down.
6. Press Down Arrow until the next <available> line is selected.
7. Type #01##ttt#.
The ttt represents the actual CO line ID number, in this example, 701.
8. Press Down Arrow again.
The description should read “:Direct call from CO trunk.”
9. Press F10 to save, then Esc to return to the C:\Amanda prompt.
10. Next you must create a mailbox with the same ID number. See “To pro-
gram Amanda:” on page 160.
Chapter 13: Miscellaneous 159
To create the appropriate integration string using a dummy integration
string:
1. Perform steps 3 through 6 in the previous procedure (“To create the
appropriate integration string using a digit grabber:”).
2. Type cccccccccccccc.
Be sure to use at least as many c’s as you can expect in the inband signal
to be captured.
3. Press Down Arrow
The Description should read “Unknown/Invalid integration.”
4. Press F10 to save, then Esc to return to the C:\AMANDA prompt.
5. Start Amanda.
6. Place a trunk call into Amanda over a CO line (for example CO line
701).
7. After the call is answered, hang up.
8. Shut down Amanda.
a. Press Alt+S (if Amanda is running as a standalone) or s (if
Amanda is running as a voice server).
b. Type in the password. (The default is AMandA with only the
first two and the last letter capitalized.)
c. Press Enter.
d. Press Y (to confirm the shutdown).
e. Press Y again (to reconfirm).
9. At the C:\AMANDA prompt, type:
edit trace.out
10. Press Enter.
11. Press Page Down or search for RING.
In the next few lines of the trace file are the actual inband digits.
160 Installing Amanda@Work.Group/DOS
12. Write down the inband digits.
13. Press Ctrl+X then Ctrl+C to return to the C:\AMANDA prompt.
14. Return to the Setup utility and replace the string of c’s with the correct
digits—except for the CO line ID which you replace with t’s.
To program Amanda:
1. Create mailboxes that match the CO Line IDs, for example, mailboxes
701, 702, 703, etc.
2. For each of these mailboxes:
• Under Options, Do Not Disturb must be locked OFF
• Under Messages, Store needs to be OFF
Chapter 13: Miscellaneous 161
The figures below show mailbox 701 as an example.
162 Installing Amanda@Work.Group/DOS
The Users Screen
Save Auto Delete Notify Table Copy Esc/EXIT PgDn/NEXT PgUp/PREV Users
Mailbox: 701 Comment: Security Code:
Extension: @G(990)
Dir Name 1: Dir Name 2: Read-Only:
Basic Options Chains Groups
Maximum Rings: 0 (default is 4) Done: 1: 1
Do Not Disturb: OFF Lock: ON RNA: 2: 0
Screen Calls? OFF Lock: OFF Busy: 3: 0
Store Messages? NO Max: 180 sec Delay: 04: 0
Copy Messages To: Menus
Message Volume: 0Guests: -1 1: 2: 3:
Current Greeting: 0Max: 45 sec4:5:6:
Busy Message? SYS Max: 45 sec7:8:9:
ID Call? NO D/T? YES Name/Ext? YES 0:
Created: NEVER Conn Secs: 0 Statistics Started: NEVER
Saved: NEVER User Secs: 0 Calls: 0 Last: NEVER
Messages Transfers: 0 Last: NEVER
Current: 0, 0 new ( 0 sec) Logins: 0 Last: NEVER
Maximum: 0 Total: 0 Notifies: 0 Last: NEVER
3. Create a token string in the Extension field that will play the greeting for
the company that uses that CO Line.
For example, if Company A uses LINE701 and LINE702 and its com-
pany greeting is Greeting 1 for mailbox 990 (the default Company
Greeting mailbox), then both mailbox 701 and mailbox 702 should have
the following in their Extension fields:
@G(990)
This token string tells Amanda to play Greeting 1 from mailbox 990
when a call comes in on LINE701 or LINE702.
Chapter 13: Miscellaneous 163
Similarly, if Company B uses LINE703 and LINE704 and its company
greeting is Greeting 1 for mailbox 890, then both mailbox 703 and mail-
box 704 should have the following in their Extension fields:
@G(890)
TIP:If later Company A decides it needs only one line and
Company B is happy to pay for three lines, you can
switch LINE702 to Company B by changing the Ex-
tension field in mailbox 702 to:
@G(890)
4. The Company Greetings mailboxes (990 and 890 in this example) have
the following settings:
• Under Options, Do Not Disturb must be locked ON
• Under Messages, Store needs to be OFF
• The Done Chain should contain the number of the Caller Instruc-
tions mailbox (whose greeting is “Press 1 for technical support;
press 2 for …”)
For example, if Company A uses the default Company Greeting
mailbox (990) and the default Caller Instructions mailbox (991),
mailbox 990 should look like the mailbox in the figures below.
5. Record the greetings for each company using your telephone or Amanda
Messenger.
164 Installing Amanda@Work.Group/DOS
The following figures show how this looks in Amanda Administrator
and Amanda standalone.
Chapter 13: Miscellaneous 165
The Users Screen
Save Auto Delete Notify Table Copy Esc/EXIT PgDn/NEXT PgUp/PREV Users
Mailbox: 990 Comment: Security Code:
Extension:
Dir Name 1: Dir Name 2: Read-Only:
Basic Options Chains Groups
Maximum Rings: 0 (default is 4) Done: 991 1: 1
Do Not Disturb: ON Lock: ON RNA: 2: 0
Screen Calls? OFF Lock: ON Busy: 3: 0
Store Messages? NO Max: 180 sec Delay: 04: 0
Copy Messages To: Menus
Message Volume: 0Guests: -1 1: 2: 3:
Current Greeting: 0Max: 45 sec4:5:6:
Busy Message? SYS Max: 45 sec7:8:9:
ID Call? NO D/T? YES Name/Ext? YES 0:
Created: NEVER Conn Secs: 0 Statistics Started: NEVER
Saved: NEVER User Secs: 0 Calls: 0 Last: NEVER
Messages Transfers: 0 Last: NEVER
Current: 0, 0 new ( 0 sec) Logins: 0 Last: NEVER
Maximum: 0 Total: 0 Notifies: 0 Last: NEVER
Using Multiple Employee Directories
To have different employee directories:
• In the Per Port section of Advanced Configuration, change the mail-
box for the employee directory on a per port basis.
For example, for a four-port Amanda system shared by two companies,
box_idx for ports 1 and 2 might be set to mailbox 411, while box_grt for
ports 3 and 4 might be set to mailbox 311.
166 Installing Amanda@Work.Group/DOS
Using Multiple Direct Messaging Mailboxes
To use different mailboxes for direct messaging:
• In the Per Port section of Advanced Configuration, change the mail-
box for the direct messaging on a per port basis.
For example, for a four-port Amanda system shared by two companies,
box_snd for ports 1 and 2 might be set to mailbox 998, while box_grt for
ports 3 and 4 might be set to mailbox 888.
Chapter 14:
Accessing Amanda Remotely
Accessing Amanda from Another Computer
You can control and configure Amanda@Work.Group/DOS remotely from
another computer using the Host and Remote programs. Host runs on
Amanda (server or standalone) and Remote runs on the computer that is
accessing Amanda remotely. You also need either a null modem cable to
connect the computers or a modem on each computer.
These programs allow the remote computer’s monitor and keyboard to take
over for Amanda’s monitor and keyboard. For example, you can run Setup
and other programs on Amanda’s computer while sitting at the remote
computer. You should see whatever is (or would be) visible on Amanda’s
monitor, and you can use Amanda as though you were operating her
keyboard.
There are two versions of the Host program: HOST.COM 2.0 and
HOST.COM 3.0. The Host programs are both DOS programs. Your new
Amanda@Work.Group/DOS system comes with HOST.COM 3.0.
There are also two versions of the Remote program: REMOTE.COM, a
DOS program which is in the C:\AMANDA directory on your Amanda
system, and WINREM.EXE, a 32-bit application sold separately by The
Amanda Company.
REMOTE.COM is a DOS program. It can be run from Windows when
Windows is in DOS mode. (REMOTE.COM does not run in a DOS box.)
168 Installing Amanda@Work.Group/DOS
WINREM.EXE runs in either Windows 95 or Windows NT. It has many
more features than REMOTE.COM. For example, it allows you to copy files
from the host computer to the remote computer and vice versa.
WinRem is not shipped with Amanda@Work.Group/DOS, but works with
Amanda@Work.Group/DOS. Contact your sales representative for more
information.
NOTE:DOS programs that use graphics and pop-up decision win-
dows may not be controllable or appear correctly on the
screen while you are using either Remote program. Exam-
ples are Edit, MSD, Scandisk, and Defrag (when run in in-
teractive, rather than batch, mode).
Never use Edit remotely. When you press Alt+X to close
the file, you become disconnected. Use JOVE instead.
Host Program Remote Program Compatibility Issues
HOST.COM
(Host 2.0—found on
older systems)
REMOTE.COM
(also called Remote
2.0)
Designed to be used
together. You cannot
transfer files with this
combination.
WINREM.EXE
(also called WinRem
1.0)
Compatible, but
HOST.COM does not
support the file trans-
fer feature of
WINREM.EXE
HOST.COM
(Host 3.0—found on
Amanda@Work.
Group systems start-
ing with version 6.15)
The file name is the
same for both Host
2.0 and 3.0.
REMOTE.COM
(also called Remote
2.0)
Compatible, but
REMOTE.COM does
not offer a file transfer
feature
WINREM.EXE
(also called WinRem
1.0)
Designed to be used
together. You can
transfer files with this
combination.
Chapter 14: Accessing Amanda Remotely 169
Setting Up Amanda’s Computer as a Host
It is a good idea to run the Host program automatically whenever Amanda’s
computer starts. The AUTOEXEC.BAT file already contains lines that you
can use for this purpose.
However, you must remove the REM at the beginning of two lines in the
AUTOEXEC.BAT: the line that contains the HOST command and the line
above it that starts REM ECHO…. You might also have to change the
number of the COM port to be used by the null modem cable or by the
modem in Amanda’s computer. If the line is missing, add it as the first line of
the AUTOEXEC.BAT file.
Then reboot the computer to load the Host program.
The line for the null modem cable is:
REM LH HOST /2 /f /n >>%LOGN%
This lines for the modem and null modem cabled can be explained as
follows:
REM Indicates that the line is currently ignored. Remove the
REM to use the line.
LH HOST Tells the computer to load this program in high memory.
/2 The 2 is for COM2. You can change this number to the
number of the COM port the null modem cable or modem
will use.
/f Indicates that the cable or modem is faster than 2400 bps.
/n Indicates that a null modem cable will be connected to
both computers.
>>%LOGN% Sends information about loading the Host program to ei-
ther the C:\BOOTLOG file or to the screen, depending
whether your AUTOEXEC.BAT file contains the line
SET LOGN=C:\BOOTLOG or the line SET
LOGN=CON:
170 Installing Amanda@Work.Group/DOS
The line for the modem is:
REM LH HOST /4 >>%LOGN%
Use the list above (for the null modem) to understand each part of this line.
Change the /4 to the number of the COM port used by the modem on
Amanda’s computer, and add a /f if your modem can handle data speeds of
higher than 2400 bps.
Setting Up the Remote Computer
The remote computer must have a copy of the Remote program. Then you
can run the Remote program from that computer (for example, a
notebook).You can copy REMOTE.COM from C:\AMANDA to a floppy
disk using the following command at the DOS prompt:
copy c:\amanda\remote.com a:\remote.com
(Your floppy disk drive may be b: rather than a:.) Then you can insert the
floppy disk into the remote computer and copy the file to that computer.
If Amanda is running as a standalone, you can copy the file using the Alt+F
(Filecopy) command from the Main screen. Simply answer the Copy From:
and Copy To: prompts.
Chapter 14: Accessing Amanda Remotely 171
Connecting by Null Modem Cable
To connect over a null modem cable:
1. Attach one end of the null modem cable to the correct serial port (for
example, COM2) on Amanda’s computer and to a serial port on the
remote computer.
2. Turn on both computers.
3. From the remote computer, use the following command to start the
Remote program.
remote /x /n /f
where x is 1 or 2, depending on what COM port the cable is connected
to on the remote computer. For COM1, you can use /1 or nothing at all
because COM1 is the default.
You execute the command from the directory in which the Remote pro-
gram is stored or you add the path name to the command. For example,
if the program is stored on your hard drive in the UTIL directory on
your C: drive, C:\UTIL\REMOTE would replace REMOTE in the com-
mand. If the computer runs a version of Windows, run the command
while the computer is in DOS mode. (Remote may not run in a DOS
box.)
4. Press Enter.
The following appears on the screen:
Remote Version 2.0
You can run Setup and other programs on Amanda’s computer while sit-
ting at the remote computer. (If the screen is blank because of Amanda’s
screen saver, press the spacebar to exit the screen saver.)
5. To end the Remote session, press Alt+X.
The program asks you to confirm your decision to exit by typing Y.
The remote computer disconnects from Amanda.
172 Installing Amanda@Work.Group/DOS
Connecting by Modem
To connect via data modem, both Amanda’s computer and the computer that
will be accessing Amanda remotely must be running and have a modem that
is connected to both a serial port and a telephone line. The data modem must
be connected to either a dedicated telephone number (this works best) or its
own telephone system station.
The Host program can use COM1 through COM4. The Amanda Company
recommends that Amanda’s computer use one of the following for the data
modem:
COM1 with IRQ4 and not other devices on COM1 or using IRQ4
COM2 with IRQ3 and not other devices on COM2 or using IRQ3
COM3 with IRQ11 and not other devices on COM3 or using IRQ11
COM4 with IRQ5 and not other devices on COM4 or using IRQ5
The Remote program works only with COM1 or COM2, with industry
standard IRQ and I/O port addressing. That is:
COM1 with IRQ4 and not other devices on COM1 or using IRQ4
COM2 with IRQ3 and not other devices on COM2 or using IRQ3
To control Amanda via modem:
1. Use the following command to start the Remote program:
remote /x
where x is 1 or 2, depending on what COM port the cable is connected
to on the remote computer. (For COM1, you can use /1 or nothing at all
because COM1 is the default.)
You execute the command from the directory in which the Remote pro-
gram is stored or you add the path name to the command. For example,
if the program is stored on your hard drive in the UTIL directory on your
C: drive, C:\UTIL\REMOTE would replace REMOTE in the command.
Chapter 14: Accessing Amanda Remotely 173
If the computer runs a version of Windows, run the command while the
computer is in DOS mode. (Remote may not run in a DOS box.)
2. Press Enter.
The following appears on the screen:
Remote Version 2.0
Enter phone number:
3. Type the telephone number for Amanda, then press Enter.
For example, if both modems are on the station side of the telephone
switching system, you might use 9,17147530414,,,,,102 where the com-
mas are two-second pauses and the 102 is for mailbox 102. In this
example, the Extension field for mailbox 102 would have to be 102H to
achieve a blind transfer to extension 102.
Enter password: appears on the screen.
4. Type JENNIFER in uppercase letters, then press Enter.
You can run Setup and other programs on Amanda’s computer while sit-
ting at the remote computer. (If the screen is blank because of Amanda’s
screen saver, press the spacebar to exit the screen saver.)
5. When you have finished, type Alt+X to end the connection.
The program asks you to confirm your decision to exit by typing Y.
The remote computer disconnects from Amanda.
174 Installing Amanda@Work.Group/DOS
Chapter 15:
Programming Amanda
Using Tokens
The Token Programming Language allows you to write programs for
Amanda. These programs consist of tokens entered in Extension fields
(defined per mailbox using Amanda Administrator’s Mailbox window or
Amanda Standalone’s Users screen) and/or in Method fields (defined per
mailbox using Amanda Administrator’s Notify window or Amanda
Standalone’s Notify Screen). This section describes the language and
introduces you to common programming terms. Understanding these terms
can help you understand any programming language.
A token is a sequence of one or more characters that represents an action that
Amanda can perform. The tokens that you use most often are simple and
perform routine actions such as dialing an extension. However, a program
can be much more complicated than that.
With the Token Programming Language, you can use tokens to do either of
the following:
• Enhance Amanda’s normal processing of the Extension and Method
fields. Normally, she uses Programmed Call Progress Monitoring
(PCPM).
In this case, you add the tokens where appropriate within the field.
For example, 147H is a sequence of four tokens that tells Amanda to
dial the DTMF digits 147 (for extension 147) and then hang up. Notice
that the tokens are not separated by spaces (or any other characters).
You write tokens one right after the other.
176 Installing Amanda@Work.Group
• Stop Amanda’s normal processing of the fields and tell her what to
do.
In this case, the first character in the field is @. Then you add the tokens
that tell Amanda what to do.
For example,
@R(G1,%S1)
assigns the DTMF digits entered by the caller to a variable named %S1.
This starts with an @ to indicate that you are NOT processing this
Extension field normally.
Normal processing for the Extension field: Amanda plays “Please hold
while I try that extension,” puts the caller on transfer hold, then evaluates the
tokens in the field. Unless told to do otherwise, she listens for call progress
tones and an answer.
The @ stops Amanda from performing the dial code that puts a caller on
transfer hold (also known as the dl_dtwait dial code). As explained in
Installing Amanda@Work.Group, you use the Setup utility (selection 1) to
set or view the dial codes. The codes are stored in
C:\AMANDA\PBX.DB\1001.PBX, which you can view or edit using the
JOVE utility.
Normal processing of the Notify Method field: Amanda tries to access a
port for an outbound notification call. The @ stops Amanda from going off-
hook.
When most people think of a program, they think of a series of lines, each of
which contains a single action or command. The Token Programming
Language is similar, but each line become the contents of a different field,
using the Extension field of a mailbox.
If the program contains only a few lines, sometimes you can use just one
Extension or Method field for the entire program. However, when you need
more fields, you use the Extension fields from additional mailboxes. Even if
a Method field must be extended, you extend it to the Extension field in
another mailbox.
Chapter 15: Programming Amanda 177
You use additional fields for any of the following reasons:
• The logic of the program branches or repeats. You use a G() com-
mand or I() command to create the branch or loop. See “Flow of
Control: Branching and Looping” on page 188 for more details.
• The length of the string of tokens exceeds 65 characters, so you are
forced to continue in another field. You use a G() command to ex-
tend the token string to a new Extension field.
Mailbox Settings
If you are using a mailbox’s Extension field for token programming, you
must use all of the following settings:
• Do Not Disturb must be off. Amanda ignores the Extension field al-
together if Do Not Disturb is on.
• Call screening must be off.
Success and Failure
Amanda evaluates tokens from left to right. If Amanda performs a token
successfully, she goes on to the next token.
When all the tokens have been performed successfully in an Extension field,
Amanda goes to the RNA Chain field. If the RNA field is blank, she goes to
the Done Chain field for the company greeting mailbox (usually mailbox
990).
When all the tokens have been performed successfully in the Notify Method
field, Amanda goes to the next Notify Method field (if there is one). If there
are no more Notify Method fields, Amanda goes to the Done Chain field for
the current mailbox.
If the token is unrecognized (because of a syntax error or a typographical
error) or fails, Amanda immediately goes to the Done Chain field without
processing the rest of the tokens in the field. If the last successful token gives
Amanda an invalid mailbox, she processes the Done Chain field for the
mailbox associated with the current port because she cannot locate a Done
Chain field for the invalid mailbox. (The mailbox associated with the port is
usually 990, the Company Greeting mailbox.)
178 Installing Amanda@Work.Group
For a literal or system variable, there is no such thing as failure. The token
always succeeds. Some tokens define almost any behavior as successful. For
example, you can have Amanda spell an empty string. Amanda doesn’t say
anything, but no failure occurs either.
Tracing Token Execution
Amanda’s trace files can let you know where and how a token program is
failing. This is an invaluable debugging tool.
Amanda creates trace files as she runs, because the following trace command
should be in the AUTOEXEC.BAT file.
amanda /t5 /s1300
Like the default trace command, this command creates
C:\AMANDA\TRACE.OUT file and limits its size to the last 1.3MB of data.
(A file this size will fit on a 3 1/2-inch floppy disk.) What is different about
this command is that it writes to the trace file every 10 lines. In this way, if
Amanda crashes while running your token program, no more than ten lines
of trace information can be lost. You can use /t with a number less than 10 if
you need to, but it will slow down the system.
You can also display trace information on-screen.
To display trace information for a standalone system:
1. Press Ctrl+Home.
2. Press Alt+T.
Pressing any key stops the display. On-screen traces are stored by default in
C:\AMANDA\SCREEN.OUT. To change the name of this file, use the Setup
utility to change the setting for the configuration option screen_save.
To display trace information on Amanda Voice Server:
•Press T.
Chapter 15: Programming Amanda 179
Press O to stop the display. On-screen traces for Amanda Voice Server are
not stored in a file. You can create trace files using Amanda Monitor. For
details, see Administering Amanda@Work.Group. You can use Amanda
Monitor to display on-screen traces as well.
Kinds of Tokens
Tokens fall into the following categories:
• Literals
•Variables
• Commands
Literals
A literal is an exact value such as the whole numbers 4 or 1144. Notice that
you do not use commas within numbers. You use 1144—not 1,144.
The DTMF digits and most single-character tokens are literals. For example,
the comma (,) that causes a pause is a literal.
Another type of literal is the string. In the Token Programming Language (as
in most programming languages), a string is a sequences of characters. For
example, JAMES DOLE is a 10-character string that starts with the letter J
and ends with the letter E. To clearly show where a string begins and ends,
programming languages require delimiters (characters that enclose the
string, but are not part of it. In the Token Programming Language, you use
single or double quotation marks as string delimiters. So JAMES DOLE
becomes 'JAMES DOLE' or "JAMES DOLE".
"9," is a string that Amanda might dial for an outside line. It consists of the
DTMF digit 9 followed by the comma for a pause.
A string that has no characters is called the empty string. It often occurs in
programming and is written as '' or "".
If you use one kind of quotation mark within a string, you should use the
other kind as the string’s delimiters: "Amanda's" or 'Do not use " (the double
quotation character)'.
180 Installing Amanda@Work.Group
Variables
Each variable is the name of a storage location within the computer that can
store a string or a -hole number. After you store something in a variable, you
can use that variable’s name instead of typing the string or the number. This
is useful because:
• Amanda’s variables have simple names (no more than four charac-
ters) and save you typing time. (You are less likely to make a mistake
typing a short variable name than a long string.)
• You can change the contents of the storage location and still use the
same variable.
• Amanda can perform the same set of tokens over and over again with
different values because the tokens use the variables rather than the
values. For example, if you change the telephone number stored as a
variable, Amanda dials the new number without you having to
change any tokens.
The Token Programming Language has system, port, and global variables.
Each of them starts with a percent sign (%).
System variables are controlled by Amanda. For example, %D contains the
amount of available disk space, and %C contains the number of the port
currently in use.
Port variables are controlled by you. Their names range from %S0 to %S19.
Port variables provide 20 locations in which to store information on a per-
port basis. The %S0 accessed by Amanda while using one port is not the
same location as the %S0 accessed by Amanda while using another port.
Global variables are also controlled by you. Their names range from %G0 to
%G9. These 10 locations are used by all the ports. The %G2 accessed by
Amanda while using one port is exactly the same location as the %G2
accessed by Amanda while using another port.
Chapter 15: Programming Amanda 181
Assignment
You control port and global variables. For example, you can assign numbers
or strings to them and later change those numbers or strings. For example,
you might assign the value of 65 to %G4 and the value "Amanda" to %S9.
Assigning a value to a variable copies that value to the variable’s storage
location.
Initially, each port and global variable has the empty string as its value.
Assignment is done in the Token Programming Language using the
assignment command, which starts with the equal sign (=). When the
variable contains a number, you can add to that number or subtract from it
using the command that starts with a plus sign (+).
For example, =(%S1,24) puts the number 24 in the variable named %S1.
+(%S1,15) adds 15 to the 24 in %S1 and then stores the sum 39 in %S1.
+(%S1,-10) subtracts 10 from the 39 in %S1 and then stores the difference
29 in %S1.
Commands
Commands are more complex than literals and variables. Commands
perform actions. For example, a command may tell Amanda to play a
particular message or go to another mailbox.
Each command has a name followed by a series of parts called parameters.
Some parameters contain information that Amanda needs to perform the
command. Others contain information that Amanda obtains for you as she
performs the command. Each parameter is a literal, variable, or another
command.
The parameters are delimited (surrounded) by parentheses and separated by
commas. For example, P(M8) tells Amanda to play message number 8. The
command name is P, and its only parameter is M8, which is surrounded by
parentheses.
182 Installing Amanda@Work.Group
The command P(0745,T) tells Amanda to say the number 0745 as a time. It
also has the command name P, but it has two parameters: the number 0745
and the literal T.
Chapter 15: Programming Amanda 183
When a command is referred to by name in this guide, the parentheses
appear after the command’s name. For example, the command named P is
referred to as the P() command, which is read as “the P command.”
Parameters
Parameters can be required or optional. The syntax places brackets […]
around optional parameters.
Parameters can also be for input or for output. Input parameters provide the
information that Amanda needs in order to perform the action that you
requested. For example, Amanda might need the name of the file in which to
store a fax or the telephone number for a pager. You supply the input
parameters and make sure that the information in them is correct. Input
parameters can be literals, variables, or other commands.
Output parameters are parameters that store information you asked Amanda
for. Output parameters are always variables because Amanda must store the
information you requested in a storage location. Usually one command asks
for the information, Amanda stores the information in a variable, and
another command uses that variable. For example, you might use the V()
command to retrieve a telephone number from a file. If the output parameter
for the telephone number is %S5, Amanda stores the telephone number in
the variable %S5. Then you use %S5 in a T() command to send a fax using
that telephone number.
The syntax in the guide does not indicate which parameters are input and
which are output. This is clear from the descriptions of the command and
parameters.
When a string is used as a parameter, you don’t always need the quotation
marks, because the commas and parentheses serve as delimiters. You must
use the quotation marks when a variable is part (but not all) of the string. For
example, if %S0 is MARY and %S5 is HU, the string "MARY HU" can be
used as a parameter with or without quotation marks, but the strings "%S0
HU", "%S0 %S5", and "%S0 %S5" must have quotation marks. Most
programming languages do not allow you to put variables within strings. The
Token Programming Language allows this, but it only checks for variables
184 Installing Amanda@Work.Group
within a string if you delimit that string with quotation marks. You cannot
use a number from 0 to 9 after %S1 in a string because Amanda assumes that
you meant the variable %S10 or %S11, etc.
Most system variables do not have parameters. However, a couple of system
variables have parameters that affect the contents of that system variable. For
example, to use %I, the system variable that retrieves data from specific
fields of specific messages, you use parameters to indicate which field,
message number, and mailbox you want the data from.
Syntax
The exact sequence of characters for each token is defined by its syntax, so
you have to learn to read syntax. The following table shows the conventions
used in this guide. They are similar to the syntax conventions used for other
programming languages.
For example, the following is the syntax for %I:
Syntax:
%I(field,msg_no[,mailbox])
Syntax Convention Meaning
bold Bold is used for characters that must be
used by you exactly as they appear—if
you use them at all.
italics Italics are used for characters that you
must replace with real strings, numbers,
variables, or other commands.
[ ] The syntax inside the brackets is optional.
If you don’t use this syntax, its default is
used.
{ } The syntax inside braces can be repeated.
Chapter 15: Programming Amanda 185
%I() has three parameters: field, msg_no and mailbox.
Because the %I and parentheses are bold, you know that you have to include
them in the command. The commas are bold, but the one in front of mailbox
is inside brackets […], which surround optional parts of the syntax. If you
use the bracketed part of the syntax, you must use the comma.
186 Installing Amanda@Work.Group
Because field is italicized, you know that it is a place holder for information
that you must provide. Field can be any one of the following fields
associated with messages:
D for the Date field
T for the Time field
F for the From field
Because msg_no is also italicized, you know that it is a place holder for
information that you must provide. For example, to find out the date for
message number 8, you replace msg_no with the number 8. Because mailbox
is inside brackets, you replace it only if you use that part of the syntax. For
example, you may want to delete a message belonging to mailbox 151.
Whenever a parameter is optional, such as mailbox, it has a default. A default
is the value that is used for the parameter whenever the parameter is missing.
The default for mailbox is the current mailbox.
Using the syntax, you can create any number of %I() commands. For
example, %I(D,8) provides the date for message 8 for the current mailbox,
and %I(T,6,151) provides the time for message 6 for mailbox 151.
Both the Extension and Notify Method fields can contain up to 65 characters.
If you need more than 65 characters for your program, you use:
• A command that reads additional tokens from a file
• The G() command to tell Amanda to go to the Extension field for an-
other mailbox and process the tokens she finds there
Chapter 15: Programming Amanda 187
Files and Directories
This section points out what you need to know about files and file names
when using the Token Programming Language. It assumes that you already
know the following and other facts about files and directories:
• DOS files are stored in directories.
• The complete name for a file starts with the root directory (usually
C:), lists the subdirectories leading to the file, and ends with the
name of the file, each of which is separated by a backslash (\).
When you use a DOS file name as a parameter, you must replace each
backslash (\) found in the name with either two backslashes (\\) or one
forward slash (/). For example, C:\AMANDA\FOOBAR.TXT must become
either C:\\AMANDA\\FOOBAR.TXT or C:/AMANDA/FOOBAR.TXT.
You can use variable names as parts of the file name. For example, if %S1 is
C:, and %S2 is Amanda, you can use "%S1\\%S2\\FOOBAR.TXT".
Amanda can read text files (also called ASCII files) as well as files in dBase
format. The former have file names that usually end with .TXT, and the latter
have file names that end with .DBF. Amanda can read from, write to, and
search files that contain database records. A record is a way to group pieces
of information. For example, your name and address is a record in a database
for any company that sends you supplies. The individual parts of your name
and address are fields of that record. In a database, another name for a record
is a row, and another name for a field is a column.
Sample Address Record:
First Name: MARY Last Name: HU
Street Address: 28291 HOOVER ST.
City: WINTER FALLS State: MI
Zip: 48444
188 Installing Amanda@Work.Group
Text files that contain database records should have commas separating each
field of each record and a carriage return/linefeed separating one record from
another. (A carriage return/linefeed is the pair of ASCII characters placed in
a file when you press Enter on your keyboard.)
Sample Address Record as a line in a text file:
MARY,HU,28291 HOOVER ST.,WINTER FALLS,MI,48444
When Amanda reads records from a text file, you tell her the number of the
fields you want to read or change the data in. The fields are numbered
starting with 1. In our example, First Name is 1, and Last Name is 2.
dBase files are created using dBase, a database software product. For dBase
files, you tell Amanda the name of the field instead of its number. When
Amanda reads data from a dBase file, she deletes any spaces at the end of the
data as she stores the data into a variable. For example, if the field contains
"MARY ", Amanda reads only "MARY".
Flow of Control: Branching and Looping
When programming Amanda, you often type the tokens for a program in
more than one field. This is not because you have exceeded the 65-character
limit for the Extension or Notify Method field, but because you want to
control the flow of token processing. For example, the only way to have
Amanda perform different actions based on the value of a variable, is to put
the tokens for one set of actions in another Extension field.
The commands that control the flow of tokens are:
• The I() command which compares two values. (Notice that this is not
the same as the %I() command/system variable discussed earlier in
this chapter.) This command is similar to the If command or If state-
ment in other programming languages. It is used to branch in either
of two directions, depending on whether the comparison is true or
false. If the comparison is true, Amanda goes to another mailbox’s
Extension field and processes the tokens there. If the comparison is
false (for example, %S1 is not equal to the empty string), Amanda
continues processing tokens where she is.
Chapter 15: Programming Amanda 189
For example, I(%S1,=,'',101) can be read as “If the variable %S1 equals
the empty string, go to mailbox 101. If not, go to the next token in this
mailbox.” I(%G0,>,5,2000) can be read as “If the variable %G0 is
greater than 5, go to mailbox 2000. If not, go to the next token in this
mailbox.”
• The G() command which tells Amanda to go to another mailbox’s
Extension field right now. (Notice that this is not the same as the
%G0 through %G9 global variables.) There is no comparison
made—just an immediate branch to a new mailbox.
For example, G(2000) can be read as “Go immediately to mailbox
2000.”
A loop is the name given to a set of tokens that are repeated. For example, if
the last token in the Extension field for mailbox 151 is G(151), Amanda
returns to the beginning of the Extension field for mailbox 151. This forms a
loop. It forms an infinite loop unless Amanda can branch to another
mailbox’s Extension field before performing the G() command. Sometimes
you want an infinite loop, but usually an I() command appears within the
loop (somewhere between the beginning of the loop and the G() command)
and allows Amanda a way out of the loop.
For example, if you want Amanda to process the tokens for 151 exactly three
times, you use a variable as a counter. You add 1 to the variable every time
through the loop and branch when the I() command determines that the
variable is equal to 3.
If you want Amanda to process the tokens for 151 until a certain value is
entered by the caller, you store the caller’s input in a variable and use the I()
command to branch when the variable finally contains the value you are
waiting for.
The examples in this section shows a loop in which Amanda repeats the
tokens in one Extension field over and over—until stopped. You can make
more complicated loops. For example, you can use the G() command to go
from mailbox 151 to mailbox 152 to mailbox 153, before returning to
mailbox 151. This is still a loop because eventually Amanda returns to
mailbox 151. It is just a longer, more complicated loop than the earlier
examples.
190 Installing Amanda@Work.Group
T1 Lines
If you are using a T1 line, the only tokens you can use are:
• Any DTMF digit (0–9, A, B, C, D, # , *)
• Any system, port, or global variable (any token that starts with %)
•E
•F
•P
•W
Examples
This section provides practical examples using some of the available tokens.
Customizing the Employee Directory
The default operation of the employee directory minimizes the work you
have to do as a system administrator. All you have to do is put values in the
Dir Name 1 and Dir Name 2 fields for each employee’s mailbox. A little
extra work on your part can make it easier for the caller to use the employee
directory.
Application
This example explains how to streamline the functionality of the employee
directory (by default, mailbox 411) so that the caller does not have to dial the
extension.
The default use of the employee directory:
1. A caller enters 411 for the employee directory.
2. The caller enters three digits representing the first three letters in either
the first or last name of the person he wants to call.
Chapter 15: Programming Amanda 191
3. Amanda reads the extension for each person whose name matches the
digits.
4. The caller dials the correct extension.
The customized use of the employee directory:
1. A caller enters 411 for the employee directory.
2. The caller enters three digits representing the first three letters in either
the first or last name of the person he wants to call.
3. If more than one employee matches the digits, Amanda asks the caller to
choose.
For example, Amanda might say “For Steve Smith, press 1; for Stella
Clark, press 2.”
4. Amanda dials the extension.
Translating to Amanda’s Tokens
This example shows the use of the G() command, which stops Amanda from
processing the current mailbox and goes directly to the specified mailbox. It
also illustrates the M() command that causes Amanda to play a greeting and
wait for a single-digit number from the menu as a response.
To customize the employee directory:
1. Make a list of everyone’s first and last names (as they will appear in the
Dir Name 1 and Dir Name 2 fields in their mailboxes).
Example:
Steve Forest mailbox 105
JoAnn Johnson mailbox 106
Bob Knapp mailbox 107
192 Installing Amanda@Work.Group
2. Determine what three digits would match each name:
Example:
Steve Forest mailbox 105
783 367
JoAnn Johnson mailbox 106
562 564
Bob Knapp mailbox 107
262 562
3. Create mailboxes for each of the sets of three-digits.
Example:
Create mailboxes 783, 367, 562, 564, and 262.
4. For each of these mailboxes, make sure that:
Do Not Disturb is locked OFF. (Do Not Disturb: OFF Lock: ON)
Call screening is locked OFF. (Screen Calls? OFF Lock: ON)
5. Fill in the Extension fields for mailboxes that only match one of the
employees with @G(employee_mailbox)
Example:
Because 783 and 367 match Steve Forest, the Extension fields for mail-
box 783 and mailbox 367 should be:
@G(105)
Because 564 matches JoAnn Johnson, the Extension field for mailbox
564 should be:
@G(106)
Because 262 matches Bob Knapp, the Extension field for mailbox 262
should be:
@G(107)
or
@P(G1)P(N,107)G(107)
Chapter 15: Programming Amanda 193
6. For mailboxes that match more than one of the employees:
a. Record G1 (Greeting 1) as “For first matching name, press 1;
for second matching name, press 2; …” substituting the real
names of employees for the italicized words.
b. In the Menus fields, put the mailbox for the first matching name
in 1; the mailbox for the second in 2, and so forth.
c. In the Extension field, puts:
@M(G1,1,30)
This command causes Amanda to play Greeting 1 and waits for the
caller to enter a digit indicating a choice from the menu. If the caller
does not enter a digit within 30 seconds, Greeting 1 repeats.
Example:
Because 562 matches both JoAnn Johnson and Bob Knapp, the Menus
for mailbox 562 would be:
1106
2107
The greeting would be:
“For JoAnn Johnson, press 1; for Bob Knapp, press 2.”
TIPS:To make this better yet, use:
@P(G1)P(N,employee_mailbox)G(employee_m
ailbox)
instead of:
@G(employee_mailbox)
Record a Greeting 1 for each of the new mailboxes that
says “You are being transferred to” after which Amanda
plays the Name and Extension recording for the employ-
ee’s mailbox. For mailbox 564 in the example, this would
look like:
@P(G1)P(N,106)G(106)
The P() command plays greetings and so forth. In this case,
the first P() command plays Greeting 1; the second plays
the Name and Extension recording.
If the matching digits conflict with existing mailboxes (for
example, 564 matches JoAnn Johnson, but it is already the
mailbox for another employee), use 99564 or some other
variation that does not conflict with employee mailboxes.
194 Installing Amanda@Work.Group
When more than one employee matches the digits that the
caller enters, you can add 9 to the menu (with mailbox 411)
and append the greeting to end with: “…press 9 to return to
the employee directory.” Then, if the caller doesn’t want
any of the people mentioned in the greeting, he can try an-
other name.
Token Reference
This section contains two tables, each of which lists all of the tokens in the
Token Programming Language:
•A quick token reference table, which lists each token by its func-
tion or purpose. The functions are in alphabetical order so that you
can easily find all the tokens that perform similar functions. For ex-
ample, the J() and T() commands both deal with faxes so they are
grouped under Fax. This table provides only the syntax for each to-
ken. For a full description of the token, you must look in the alpha-
betical reference.
•An alphabetical token reference table, which lists the tokens in al-
phabetical order based on the first letter in the token’s name. For ex-
ample, %I and I are found under I. Tokens whose names do not
contain a letter are listed in ASCII order before the letters. This table
provides complete descriptions and examples of each token.
Quick Token Reference
Function/Purpose of Token Syntax
absolute value P[repetition](number,N[,hangup])
Add +(variable[,value])
ANI (Automatic Number
Identification) %H
Append, file |(file)
Assignment =(variable,value[,start,end])
Boards, serial numbers %B1 %B2 %B3
%B4 %B5 %B6
Chapter 15: Programming Amanda 195
Caller hang-up H(mailbox)
Caller ID %H
Comment %F(field[,mailbox])
Condition I(value,operator,value,mailbox)
Conference call ext_noKM
Creating message notification file X[(file)]
Currency P[repetition](amount,currency[,hangup])
Current connect time %T
Current date in American format %Y
Current port number %C
Current time %Z
Current mailbox P[repetition] (U[,mailbox[,hangup]])
%U
Current mailbox’s Extension field %E
Date %I(field,msg_no[,mailbox])
P[repetition](date,D[,hangup])
%Y
Days of week %W
Deleting file Y[(file)]
Deleting, message KD(msg_no[,mailbox])
Dial (pulse dial) ~
Dial codes F
Quick Token Reference (Continued)
Function/Purpose of Token Syntax
196 Installing Amanda@Work.Group
dial tone %X
dial tone, wait for W(n,T[,mailbox])
Directory Name field %F(field[,mailbox])
Disk space %D
P[repetition](D)
Dollars P[repetition](amount,currency[,hangup])
DTMF digits P[repetition](DTMF)
P[repetition](R)
0123
4567
89AB
CD*#
DTMF for relay paging P[repetition] (R)
%R
DTMF, save caller’s entry R(greeting[#mailbox],variable
[,timeout[,timeout2]])
Earth recall E
Exit for caller hang up H(mailbox)
Exit for mailbox [ext_no]H
Extension field ext_no
@
%E
*Extensions, partially supervised transfer U-ext_no
Quick Token Reference (Continued)
Function/Purpose of Token Syntax
Chapter 15: Programming Amanda 197
Fax, incremental <(phone_no)
>(file)
Fax, initialization %A
Fax, receive J(file_or_box,phone_no[,tokens])
Fax, send T(file,phone_no[,tokens])
Fields, process extension or Notify field as
tokens @
Fields, returns number of characters in a
string LEN[string]
Fields, values in mailbox record %F(field [,mailbox])
Fields, Variable field in notification
record %V
Fields, Extension %E
Fields, information %I(field,msg_no[,mailbox])
Files, append |(file)
Files, as indicators X[(file)]
Y[(file)]
Z[(file)]
Files, delete record KV(file,field,value)
Files, from recordings KR(file_or_box[,recording_info])
Files, import {file}
Quick Token Reference (Continued)
Function/Purpose of Token Syntax
198 Installing Amanda@Work.Group
Files, read {file}
V(file,field,value{,field,variable}[,n]
[(file)
N(file,field,value{,field,variable})
Files, search ?(line,file,mailbox)
Files, voice P[repetition](X,file[,hangup])
Files, write ](file)
N(file,field,value{,field,variable})
Francs P[repetition](amount,currency[,hangup])
Free disk space P[repetition] (D)
%D
Frequency KB(frequency,msecs)
From %I(field,msg_no[,mailbox])
Goto G(mailbox)
Greeting P[repetition](greeting[,mailbox[,hangup]])
Hang-up [ext_no]H
O(time)
Hang-up, cleanup H(mailbox)
Hang-up, partially supervised U-ext_no
Hookflash E
F
O(time)
Quick Token Reference (Continued)
Function/Purpose of Token Syntax
Chapter 15: Programming Amanda 199
If I(value,operator,value,mailbox)
Import, file {file}
Information mailboxes M(greeting[#mailbox],repetition,delay)
IVR %I(field,msg_no [,mailbox])
Languages, change L(file)
Length LEN[string]
Letters and spaces P[repetition](A,string[,hangup])
LIGHT.ON
See also message waiting indicators. X[(file)]
Y[(file)]
Z[(file)]
Menu M(greeting[#mailbox],repetition,delay)
Messages %I(field,msg_no[,mailbox])
Messages, by number P[repetition](Mn[,mailbox[,hangup]])
Messages, delete KD(msg_no[,mailbox])
Messages, from recordings KR(file_or_box[,recording_info])
Messages, number %M[(mailbox)]
Messages, number of new %N
Messages, record and send to mailing
list KJ(mailbox,list_number[,sender])
Messages, total P[repetition](M[,mailbox[,hangup]])
Message count, total for mailbox %M[(mailbox)]
P[repetition] (M[,mailbox[,hangup]])
Quick Token Reference (Continued)
Function/Purpose of Token Syntax
200 Installing Amanda@Work.Group
Message count, new for current user %N
Message waiting indicator, creating X[(file)]
Message waiting indicator, deleting Y[(file)]
Message waiting indicator, testing for Z[(file)]
Message waiting indicators, on/off KA(on_off)
Money P[repetition](amount,currency[,hangup])
Name and extension P[repetition](U[,mailbox[,hangup]])
P[repetition](N[,mailbox[,hangup]])
Notification record, Method field @
Notification record, Variable field P[repetition] (V)
%V
Notify, relay paging P[repetition] (R)
%R
Number P[repetition] (number,N[,hangup])
P[repetition] (V)
On-hook O(time)
Pager P[repetition] (R)
%R
%V
Pager, wait for W(n,P[,mailbox[,hangup]])
Partial supervised transfer U-ext_no
Quick Token Reference (Continued)
Function/Purpose of Token Syntax
Chapter 15: Programming Amanda 201
Pauses -
,
W(n)
Pesos P[repetition](amount,P[,hangup])
Playing, absolute value P[repetition](number,N[,hangup])
Playing, currency P[repetition](amount,currency[,hangup])
Playing, date P[repetition](date,D[,hangup])
Playing, disk space P[repetition](D)
Playing, DTMF digits P[repetition](R)
P[repetition](DTMF)
Playing, greeting P[repetition](greeting[,mailbox[,hangup]])
Playing, menu M(greeting[#mailbox],repetition,delay)
Playing, messages P[repetition](Mn[,mailbox[,hangup]])
Playing, money P[repetition](amount,currency[,hangup])
Playing, name and extension P[repetition](N[,mailbox[,hangup]])
P[repetition](U[,mailbox[,hangup]])
Playing, number P[repetition](number,N[,hangup])
Playing, number of messages P[repetition](M[,mailbox[,hangup]])
Playing, prompt P[repetition](prompt_no,V[,hangup])
Playing, spelling P[repetition](A,string[,hangup])
Playing, time P[repetition](time,T[,hangup])
Playing, Variable field P[repetition](V)
Quick Token Reference (Continued)
Function/Purpose of Token Syntax
202 Installing Amanda@Work.Group
Playing, voice file P[repetition](X,file[,hangup])
Ports S(port,[string,[variable],[termination],
[length],[timeout])
Ports, change volume ^(volume_change)
Port, current connect time %T
Port number, current %C
Port, transfer code for current %X
Previous mailbox %P
Prompt P[repetition] (prompt_no,V[,hangup])
L(file)
Pulse dial ~
Questions and answers Q({greeting[#mailbox][,E]})
Read, file {file}
N(file,field,value{,field,variable})
V(file,field,value{,field,variable}[,n]
Recordings, stored as messages or files KR(file_or_box[,recording_info])
Records, delete KV(file,field,value)
Remote computers S(port,[string,[variable],[termination],
[length],[timeout])
Rings, wait for number of W(n,event [,mailbox])
Rotary training KT(Gn)
Quick Token Reference (Continued)
Function/Purpose of Token Syntax
Chapter 15: Programming Amanda 203
Search, file ?(line,file,mailbox)
N(file,field,value{,field,variable})
V(file,field,value{,field,variable}[,n]
KV(file,field,value)
Search, string KI(target,source,variable)
Security code KC(mailbox,variable)
KL(mailbox,security_code)
KP(mailbox,security_code)
Serial port access S(port,[string,[variable],[termination],
[length],[timeout])
Set Name %F(field[,mailbox])
Shutdown KS[(errorlevel)]
Sound volume, change ^(volume_change)
Space %D
P[repetition](D)
Spell P[repetition](A,string[,hangup])
String, search KI(target,source,variable)
Strings, length LEN[string]
Subtract +(variable[,value])
Testing for message notification file Z[(file)]
Time %I(field,msg_no[,mailbox])
P[repetition](time,T[,hangup])
Quick Token Reference (Continued)
Function/Purpose of Token Syntax
204 Installing Amanda@Work.Group
Time, connect time %T
Time, current %Z
Timed break recall ~
Tokens, processing @
Tones 012
345
678
9AB
CD*#
Total messages P[repetition] (M[,mailbox[,hangup]])
Transfer code for current port %X
Transfer, unsupervised (blind) [ext_no]H
Transfer, supervised ext_no
ext_noKM
Transferring to specified mailbox G(mailbox)
Mailbox access KC(mailbox,variable)
KL(mailbox,security_code)
KP(mailbox,security_code)
Mailbox, current %U
Mailbox, Extension field of current %E
Mailbox, new message count %N
Mailbox, playing Name/Extension record-
ing P[repetition] (U[,mailbox[,hangup]])
Mailbox, previous %P
Quick Token Reference (Continued)
Function/Purpose of Token Syntax
Chapter 15: Programming Amanda 205
Mailbox, total message count %M[(mailbox)]
Mailbox, value of field %F(field [,mailbox])
Variable field P[repetition](V)
%V
Variables [(file)
](file)
|(file)
+(variable[,value])
=(variable,value[,start,end])
%G0 %G1 %G2 %G3 %G4
%G5 %G6 %G7 %G8 %G9
%S0 %S1 %S2 %S3
%S4 %S5 %S6 %S7
%S8 %S9 %S10 %S11
%S12 %S13 %S14 %S15
%S16 %S17 %S18 %S19
Variables, shift K<(x[,value])
Voice boards, serial numbers %B1 %B2 %B3
%B4 %B5 %B6
Voice form Q({greeting[#mailbox][,E]})
Voice, wait for W(n,V[,mailbox])
Volume change for port ^(volume_change)
Waiting, for a number of tenths of a sec-
ond W(n)
Waiting, for dial tone, pager, voice W(n,event [,mailbox])
Quick Token Reference (Continued)
Function/Purpose of Token Syntax
206 Installing Amanda@Work.Group
Weekday %W
Write, file ](file)
N(file,field,value{,field,variable})
Alphabetical Token Reference
Token Syntax Description
-Literal that pauses processing for .5 (one-half) second.
, Literal that pauses for 2 seconds. Used when dialing an extension or to introduce a
pause before processing the next token.
NOTE:Be careful not to confuse this comma with the separator found in com-
mands and records.
?(line,file,
mailbox) Command that searches the specified file (line by line) for the specified line. The
line must match an entire line within the file. If the line is found, processing con-
tinues at the specified mailbox. If the line is not found, processing continues with
the next token.
line The string or variable to be matched as a line in the file. No line in
the file should exceed 143 characters.
file A string or variable containing a valid DOS file name for the text file
to be searched. Use the complete path to the file unless the file is in
C:\AMANDA. There is no limit to the number of lines in the file.
mailbox A valid mailbox or a variable containing a mailbox.
Example:
?(%S9,C:\\AMANDA\\FOOBAR.TXT,247)
causes Amanda to search FOOBAR.TXT for a line that matches the characters in
%S9. If a line is found, Amanda continues processing at mailbox 247.
Failure: Invalid mailbox
Quick Token Reference (Continued)
Function/Purpose of Token Syntax
Chapter 15: Programming Amanda 207
@Literal that causes Amanda to process the Extension or Notify Method field as a set
of tokens instead of processing the field normally.
Normal processing for the Extension field: Amanda plays “Please hold while I
try that extension,” puts the caller on transfer hold, then evaluates the tokens in the
field. The @ stops Amanda from performing the dial code that puts a caller on
transfer hold (also known as the dl_dtwait dial code). As explained in Installing
Amanda@Work.Group, you use the Setup utility (selection 1) to set or view the dial
codes. The codes are stored in C:\AMANDA\PBX.DB\1001.PBX, which you can
view or edit using the JOVE utility.
Normal processing of the Notify Method field: Amanda tries to access a port for
an outbound notification call. The @ stops Amanda from going off-hook.
Alphabetical Token Reference (Continued)
Token Syntax Description
208 Installing Amanda@Work.Group
[(file) Command that reads the first line in the specified file as the first ten port variables
(%S0-%S9). The 10 values in the file must be comma delimited. The first value is
%S0, the second is %S1, etc. The quotation marks used to delimit strings do not
appear in the file, but the commas that separate them from the other variables do.
For example, empty strings take up no space in the file.
This command is usually used with the ]() command to keep track of what the port
is doing. You read the variables using the [() command, update them, and then write
them to the file once more using the ]() command.
Read with the [() command and write with the ]() command within the same field
to avoid potential simultaneous access errors caused by another port accessing the
file.
If the file does not exist, Amanda just goes on to the next token.
file A string or variable containing a valid DOS file name for the text file
to be read. No line in the file should exceed 143 characters. There is
no limit to the number of lines. When you specify a file name, its full
path is required unless the file is stored in the directory for the cur-
rent mailbox. For example, if you use [(file) with only a file name,
and the mailbox number is 101, your file must be located in the
C:\VMB.DB\1\101 directory or the file cannot be found.
Example:
[(C:\\AMANDA\\FOOBAR.TXT)
places the following line in FOOBAR.TXT
,,,10,,,,5,9,555
In this case %S0, %S1, %S2, %S4, %S5, and %S6 were empty strings.
To count the number of calls, etc. processed by a particular port (or all ports), read
the variables, add 1 to the contents of the one that stores the count, and write the
variables back to the file.
[(C:\\AMANDA\\FOOBAR.TXT)+(%S4)]
(C:\\AMANDA\\FOOBAR.TXT)
If you are counting all ports, use the same file for all ports. If you are counting per
port, use a different file for each port.
Failure: Does not fail
\\ Backslash, the actual "\" character. Can be used in strings.
Failure: Does not fail
\A Attention, which is a bell sound (Ctrl+G). Can be used in strings.
Failure: Does not fail
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 209
\B Ctrl+B. Added for Ericsson MD-110 serial integration. For the MD-110,
Ctrl+B is the Start of Transmission (STX) character. Can be used in
strings.
Example:
@S(3,"\B06%Emm\N")
which controls message waiting indicators.
Failure: Does not fail
\N Newline (Ctrl+J). Can be used in strings.
Failure: Does not fail
\R Return (Ctrl+M). Can be used in strings.
Failure: Does not fail
\T TAB (Ctrl+I). Can be used in strings.
Failure: Does not fail
](file) Command that writes the values of the first 10 port variables (%S0–%S9) to the
specified file. The values are comma-separated and terminated by a carriage return/
linefeed. Usually used in conjunction with the [() command which reads the %S
variables.
file A string or variable containing a valid DOS file name for the text file
to be read. No line in the file should exceed 143 characters. There is
no limit to the number of lines. When you specify a file name, its full
path is required unless the file is stored in the directory for the cur-
rent mailbox. For example, if you use ](file) with only a file name,
and the mailbox number is 101, your file must be located in the
C:\VMB.DB\1\101 directory or the file cannot be found.
Example:
See the [() command.
Failure: The file is read-only
Insufficient disk space to save file
Alphabetical Token Reference (Continued)
Token Syntax Description
210 Installing Amanda@Work.Group
^(volume_change) Command that changes the volume of the current port.
volume_change Amount to increase or decrease the current volume. Use a
positive number to increase the volume and a negative
number to decrease the volume. Use the minus sign for
negative numbers, but omit the plus sign for positive
numbers. Amanda gives you a volume as close as possi-
ble to what you ask for.
The volume on Rhetorex voice boards ranges from -8
(softest) to +8 (loudest). Initially, the volume is set to 0,
but that is not necessarily its current value. If the value is
+8 and you apply a change of -16, the volume’s value
goes to -8. If the value is 0 and you apply a change of -16,
the value of the volume goes to -8 and an error appears in
the trace file.
For tAA voice boards, the volume ranges from 1 (the soft-
est) to 9 (the loudest). Initially, the volume is set to 5, but
that is not necessarily its current value. If the volume is 5,
and you apply a change of 4, the volume goes to 9. If you
apply a change of 6, the volume goes to 9 and Amanda
ignores the fact that you asked for more volume than was
available.
Example:
^(8)
raises the volume of the port to its loudest.
Failure: Does not fail
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 211
{file}Command that reads Amanda tokens from an external file. This allows you to ex-
ceed the 65-character limit in the Extension and Notify Method fields. If the file
does not exist, Amanda just goes on to the next token.
file A string or variable containing a valid DOS file name. Use the com-
plete path to the file unless the file is in C:\AMANDA. The file must
be a text file containing valid Amanda tokens. No line in the file
should exceed 143 characters. There is no limit to the number of
lines in the file.
NOTE Since the entire file is read and since white space is ignored, you can
make the file easier to read by putting one token per line. (White space is
tabs, spaces, and carriage return/linefeeds.)
Example:
{C:\\AMANDA\\RELAY.TXT}
causes Amanda to process the tokens in RELAY.TXT.
Failure: Does not fail
The failure of any token within the file causes the rest of the file to be ignored.
Then Amanda executes the token after the {} token or the RNA chain if there
is no token after the {} token.
|(file) Command that appends the first ten %S port variables (%S0–%S9) to the specified
file. If the file does not exist, Amanda creates it. The values are comma-separated
and terminated by a carriage return/linefeed.
file A string or variable containing a valid DOS file name for a text file.
Use the complete path to the file unless the file is in C:\AMANDA.
Example:
|(C:\\AMANDA\\PORTVARS.TXT)
causes Amanda to add a line to PORTVARS.TXT. You can use this to add a line
to PORTVARS.TXT every time the port you are tracing changes the value of a
variable. Later you can review the file.
Failure: The file is read-only
Insufficient disk space to save file
~Literal that pulse dials the digit 1 to effect a timed break recall.
Alphabetical Token Reference (Continued)
Token Syntax Description
212 Installing Amanda@Work.Group
+(variable
[,value]) Command that allows you to add a number to or subtract a number from the value
stored in a variable. Usually used to set limits and control programming loops.
variable One of port or global variables.
value Optional. A number or variable. The default is 1.
Example:
+(%S7,-1)
subtracts 1 from the value stored in %S7.
+(%G6)
adds 1 to the value stored in %G6.
Failure: Does not fail
<(phone_no) Command that allows a caller to request and transmit multiple fax documents with
one call. It must be used in conjunction with the >() command. To fax multiple doc-
uments, you initiate the process with this command and, as the caller requests fax-
es, you add the file for the requested document using the >() command. The fax is
sent automatically after the caller hangs up.
phone_no String, number, or variable containing the DTMF digits to be di-
aled.
This command is used only in Extension fields.
Example:
<(9,7144525570)>(C:\\AMANDA\\PRICES.TXT)>
(C:\\AMANDA\\OPTIONS.TXT)>(C:\\AMANDA\\OPTIONS.TXT)
causes Amanda to call (714)452–5570 (after dialing 9 for an outside line and paus-
ing). Then Amanda faxes two files. Duplicate files are ignored.
Failure: Does not fail
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 213
=(variable,value
[,start,end]) Command that gives the specified variable the specified value. Use start and end
to assign only part of the string (a substring) to the variable.
variable One of the port or global variables.
value A string, number, or variable.
start Optional. The starting character position to copy from value. The
default is to copy the entire string.
end Optional, but must be used if start is used. The last character posi-
tion to copy from value.
Examples:
=(%S1,"FRENCH")
Gives %S1 the value of "FRENCH"
=(%S1,"FRENCH",3,4)
Gives %S1 the value of "EN".
If %S2 is the telephone number 7530414,
=(%S1,%S2,1,3)
extracts the prefix 753 from %S2 and assigns it to %S1
If %S3 is 1 and S4 is 1,
=(%S1,"MARY",%S3,%S4)
%S1 is assigned "M".
>(file) Before using this command, you start incremental faxing with the <() command.
Even if the same file is used with the >() command more than once (per incremental
fax), it is faxed only once.
file A string or variable containing a valid DOS file name for the text file
to be transmitted. Use the complete path to the file unless the file is
in C:\AMANDA.
This command is used only in Extension fields.
Example:
See the <() command.
Failure: Does not fail
01
23
45
67
89
AB
CD
*#
Literal that plays the DTMF tone corresponding to the specified digit: 0–9, A–D,
*, or #
Alphabetical Token Reference (Continued)
Token Syntax Description
214 Installing Amanda@Work.Group
%A System variable containing the value of the fax_dl_init configuration setting.
Example:
If %A is "9,", a 9 followed by a pause is needed to access an outside telephone line.
%B1 %B2
%B3 %B4
%B5 %B6
System variable that contains the serial number of the corresponding voice board.
%B1 is voice board 1, %B2 is voice board 2, etc.
%C System variable that contains the port number. Each port has its own %C. For ex-
ample, if the current caller is on Port 3, %C contains a 3.
%D System variable that contains the percentage of free disk space. Example:
I(%D,<,20,171)
causes Amanda to transfer to mailbox 171. In this case, 171 would have Do Not
Disturb ON and Store Messages NO. The caller would hear a greeting that plays a
warning about disk space being low. The Done Chain field would have something
like mailbox 999, the greeting for which is “Thank you for calling. Good-bye.”
%E System variable that contains the contents of the current mailbox’s Extension field.
Each port has its own %E. An Extension field can contain up to 65 characters.
Example:
P(A,%E)
causes Amanda to say the characters in the Extension field.
See the P() command for more information.
ELiteral that performs an earth recall. This is used in place of the hookflash on some
telephone switching systems.
ext_no Series of DTMF digits that indicate an extension number. When these are the first
characters in an Extension field (that is, the Extension field does not start with @),
Amanda performs a supervised transfer as shown in Administering Aman-
da@Work.Group.
Example:
378
causes Amanda to call extension 378 and supervise the call.
Failure: Invalid extension number
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 215
%F(field
[,mailbox]) System variable that contains the value of the specified field for the specified mail-
box. Each port has its own %F.
field One of the following numbers or a variable containing that number:
1for the Directory Name 1 field
2for the Directory Name 2 field
3for the Comment field (if your system uses Rhetorex voice
boards) or for the Set Name field (if your system is connected
to a Norstar KSU)
mailbox Optional. Any valid mailbox or a variable containing a mailbox. The
default is the current mailbox.
Example:
%F(3,126)
assigns the string from the Comment or Set Name field for mailbox 126 to %F.
Failure: Invalid mailbox
FLiteral that performs a hookflash. The duration of the hookflash is specified in the
telephone switching system dial codes section of the Setup utility. See also recall.
Failure: Does not fail
%G0 %G1
%G2 %G3
%G4 %G5
%G6 %G7
%G8 %G9
The Amanda system has 10 global variables (%G0–%G9). Initially, each variable
is equal to the empty string. The values of %G0–%G9 are the same no matter what
port is current.
If Port 1 changes %G1, then all other ports immediately see the new value for %G1.
Each variable can contain a string of up to 143 characters.
When the system is shut down, the values of %G0–%G9 are lost. They cannot be
stored using the [(), ](), or |() commands.
See also %S0–%S9.
Example:
+(%G0)
adds one to the current value of %G0.
=(%G2,555)
assigns the mailbox 555 to %G2.
G(%G2)
causes Amanda to go to the Extension field for mailbox 555.
Failure: Invalid variable name (such as %G52)
Alphabetical Token Reference (Continued)
Token Syntax Description
216 Installing Amanda@Work.Group
G(mailbox) Command that controls processing. Amanda continues standard processing at the
specified mailbox’s Extension field (as shown in Administering Aman-
da@Work.Group).
mailbox A valid mailbox or a variable containing a mailbox.
NOTE:If you use the G() command in a Notify Method field, remember that the
telephone port is still in Notify mode and cannot transfer a call. There-
fore, the Extension field that you go to should start with an @.
Example:
G(176)
causes Amanda to go to the Extension field for mailbox 176.
Failure: Invalid mailbox
%H System variable that contains the empty string unless your 1001.PBX file (in the
C:\PBX.DB directory) is set up for ANI or (in the future) Caller ID digits. Each port
has its own %H.
Example:
If 1001.PBX contains:
integration 10 'Cxxxxxxxccccccc'
and the packet 'C00000007530414' arrives, %H contains the number 7530414 as
long as the port that received the call is active.
[ext_no]HCommand that performs a hang-up. With an extension number, it performs an un-
supervised transfer before hanging up. This H() command ends the processing of
tokens for the current Extension or Notify Method field.
If you use an unsupervised transfer in the mailbox’s Extension field, make sure that
Call Screening is locked off. If Call Screening is on for an supervised call, the caller
is screened but that recording is not played to the user.
ext_no Series of DTMF digits that indicate an extension number.
Example:
151H
causes Amanda to transfer the call to extension 151 and hang up (without wait-
ing for a voice or busy signal) when Amanda is processing a call.
Failure: Invalid extension number
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 217
H(mailbox) Command that performs exit routines when a caller hangs up. It specifies the mail-
box to be processed if a hang-up condition is detected while processing the current
set of tokens. (Processing these tokens can take Amanda to more than one mail-
box.)
mailbox A valid mailbox or a variable containing a mailbox.
This command is used only in Extension fields.
Example:
H(614)
causes Amanda to go to mailbox 614 when a caller hangs up. Because you are
tracking the number of hang ups, the Extension field for mailbox 614 has tokens
that add one to the variable with which you are counting the hang-ups, for example,
+(%G4).
Failure: Invalid mailbox
Alphabetical Token Reference (Continued)
Token Syntax Description
218 Installing Amanda@Work.Group
%I(field,msg_no
[,mailbox]) System variable that contains the data from the specified field of the specified mes-
sage. Each port has its own %I. This lets you extract specific information from a
message. For example, you might use %I in a notification record.
field One of the following:
Dfor the Date field
Tfor the Time field
Ffor the From field
msg_no The number of an existing message. You cannot use a variable con-
taining that number.
mailbox Optional. Any valid mailbox or a variable containing a mailbox. The
default is the current mailbox.
NOTE:If a message is from an outside caller, the From field of that message is
equal to -1. If the message is from a caller who is logged on to Amanda,
the From field contains the caller’s mailbox.
Examples:
P(%I(D,5),D)
plays the date of message 5 in the current mailbox.
P(%I(T,5),T)
plays the time of message 5 in the current mailbox.
P(%I(D,5,212),D)
plays the date of message 5 of mailbox 212.
P(%I(F,5,212),U)
plays the Name/Extension recording of the mailbox who sent message 5 of mailbox
212.
See the P() command for more information.
Failure: Invalid mailbox
Invalid message number
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 219
I(value,operator,
value,mailbox) Command that allows you to control processing based on a condition. If the speci-
fied values and operator create a condition that is true, Amanda continues process-
ing at the specified mailbox. If the condition is false, the next token after this
command is executed.
value Any string, number, or variable.
operator One of the following symbols:
>greater than
<less than
=equal
!not equal
mailbox Any valid mailbox or a variable containing a mailbox.
Examples:
I("111",<,"222",1000)
continue processing at mailbox 1000.
I("111",>,"222",1000)
continue processing at the next token.
I(%S1,=,"1234",2000)
continue at mailbox 2000 only if %S1 contains the value 1234.
I(%S1,=,"IVR",2000)
continue at mailbox 2000 only if %S1contains the value "IVR".
NOTE:When using the I() command in a Notify Method field, remember that the
telephone port is still in Notify mode and cannot transfer a call. Therefore,
the Extension field that you go to should start with an @.
Failure: Invalid mailbox
If there is a problem with a condition, it is considered false rather than a failure
Alphabetical Token Reference (Continued)
Token Syntax Description
220 Installing Amanda@Work.Group
J(file_or_box,
phone_no
[,tokens])
Command that allows a fax to be received as a file (for later transmission with the
T() command) or as a message for a mailbox.
Before using this command, make sure the configuration settings for the physical
serial port have been defined.
file_or_box A string or variable indicating where the fax is to be stored. It contains
either a mailbox indicating whose message it is or a valid DOS file
name for a text file. Use the complete path to the file unless the file is
in C:\AMANDA.
phone_no The telephone number for the fax device that sends the transmission or
a variable containing that number.
Use the empty string to make Amanda wait until a call rings into the
appropriate fax port. (When not in a variable, the empty string must
appear in this command as a pair of double quotation marks—even
though some commands allow you to omit them.)
tokens Optional. A string or variable that defines the actions Amanda takes to
connect the call to the fax port.
This command is used only in Extension fields.
Example:
J(123,"","P(G1)%X%F-H")
sets up a personal fax mail mailbox. In this case, mailbox 123 receives a fax as a
message and P(G1) plays a greeting such as “Start your fax machine at the tone.”
The following tokens allow for one-call fax transmission:
%X The system variable that contains the codes needed to get the transfer
dial tone on the current port
%F The extension of the fax port being used
-H A hang-up (after pausing a half second to complete an unsupervised
transfer)
J("C:\\FAXES\\FAX1","")
makes Amanda set up one of her fax modems to wait for a call and accept a fax
called C:\FAXES\FAX1. You can use this to fax files to your own Amanda system.
For example, if you print a text file that contains information for customers and
then fax it to Amanda, Amanda can fax that information out to customers using the
T() command.
Failure: Invalid mailbox
Fax modem not configured properly
Physical port not available
Logical port not configured properly
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 221
K<(x[,value]) Command that shifts the values of the %S variables to the left or right.
xA number (ranging from 0 to 20). When the number is positive, the shift
is to the left. When negative, the shift is to the right.
value Optional. The data to be placed in the %S variables left empty by the
shift. The default is to perform a circular shift, leaving no variables empty
because the value from %S0 moves to %S19, or vice versa, for every
shift.
Examples:
K<(1)
shifts the contents of %S0 through %S19 to the left by one location. The contents
of %S19 moves to %S18, the contents of %S18 moves to %S17, etc. The contents
of %S0 moves to %S19 because this is a circular shift. None of the previous values
are lost. They are only relocated.
K<(-3,"JOHN DOE")
shifts the contents of %S0 through %S19 to the right three locations, then replaces
each of the first three values (%S0, %S1, and %S2) with the string "JOHN DOE".
The last three values (%S17, %S18, and %S19) are lost.
K<(20,"")
is a quick way to clear all variables, replacing them with the empty string.
Failure: Does not fail
KA(on_off) Command that dials the PBX parameter dl_light_on or dl_light_off specified in the
telephone system dial codes.
on_off 1 or 0 to indicate whether the message waiting indicator is turned on
or off.
When the value is1, the message waiting indicator is turned on as
Amanda dials the codes for “What to dial to set the message waiting
indicator on” (the dl_light_on parameter).
When the value is0, the message waiting indicator is turned off as
Amanda dials the codes for “What to dial to set the message waiting
indicator off” (the dl_light_off parameter).
Most of the popular telephone systems have specified values that turn the message
waiting indicator on and off. If these values are not pre-defined for your system,
you can set them using Amanda’s Setup utility.
Example:
KA(1)
causes Amanda to dial the string specified in the dial codes for "What to
dial to set the message waiting indictor on."
Failure: Does not fail
Alphabetical Token Reference (Continued)
Token Syntax Description
222 Installing Amanda@Work.Group
KB(frequency,
msecs) Command that plays a certain frequency for a certain time period (defined in mil-
liseconds).
frequency A number of Hz. For example, the only frequencies supported by the
Rhetorex driver are those roughly within the range 300–3000 Hz.
msecs A number of milliseconds. The range is 1–6553.
Example:
KB(350,2000)
plays the frequency 350 Hz for two seconds.
Failure: Does not fail
KC(mailbox,
variable) Command that compares the security code for the specified mailbox with the con-
tents of a variable. If there is a match, the command is successful. For callers who
do not know the security code, Amanda continues processing using the mailbox in
the Done Chain field.
mailbox Any valid mailbox or a variable containing a mailbox.
variable The port or global variable whose contents are matched against the se-
curity code of mailbox.
Example:
R(G1,%S1)KC(212,%S1)KL(%S1)
assigns the DTMF digits entered by the caller to %S1, compares %S1 with the se-
curity access code of mailbox 212, and takes the appropriate action.
After the caller passes the security check, the KL() command allows the caller to
log on to the mailbox. See also the KL() command.
Failure: Invalid mailbox
Invalid security code
Security codes do not match
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 223
KD(msg_no
[,mailbox] [,1]) Command that deletes a message from the specified or current mailbox. Using this
command cancels any pending Notify actions for the specified message automati-
cally.
msg_no A number or a variable containing a number.
mailbox Optional. Any valid mailbox or a variable containing a mailbox. The de-
fault is the current mailbox.
1Optional. When used, if the specified message does not exist, Amanda
says, "Sorry, I’m unable to do that at this time."
Examples:
KD(5)
deletes message 5 of the current mailbox.
KD(10,212,1)
deletes message 10 of mailbox 212. If message 10 does not exist, Amanda lets you
know she was unable to do that and process the Done chain because the command
failed.
Failure: Invalid mailbox
Invalid message number
KI(target,source,
variable) Command that searches one string (called the source string) to see if it contains a
copy of another string (called the target string).
target A string or a variable containing the string to be searched for inside the
source.
source A string or a variable containing the string to search.
variable The port or global variable to which the KI() command assigns one of the
following:
• Zero if the target is not found in the source.
• The number of the position within the source string at which the
copy of the target string starts.
Examples:
KI("UL","PAUL INCE",%S1)
is a successful search and assigns the value 3 to %S1
KI("ULL","PAUL INCE",%S1)
fails and assigns the value 0 to %S1
KI(%S0,%S1,%S2)
means if a copy of %S0 is found within %S1, %S2 is assigned its character posi-
tion. If %S0 is not found, %S2 is assigned the value 0.
Failure: Does not fail
Alphabetical Token Reference (Continued)
Token Syntax Description
224 Installing Amanda@Work.Group
KJ(mailbox,
list_number
[,sender])
Allows a caller to record a message that, when saved, is sent to a list of
users.
mailbox Any valid mailbox or a variable containing a mailbox.
list_number Any valid list number (1–8 or 10–30). If the mailbox number is 999,
then the list number is for a system list rather than a user list.
sender Optional. Provides a sender for the message or treats the message as
though it were from outside the Amanda system.
When 0, the message is treated as a message from outside the Amanda
system. Amanda does not identify the sender. This is the default.
When 1, the Message From field contains the number of the mailbox
containing this token. Amanda plays the name and extension
recording for that mailbox’s owner when identifying the sender.
Example:
KJ(128,5)
causes Amanda to record a message and then send it to the users on
mailing list 5 for mailbox 128.
Failure: Invalid mailbox or list number or out of disk space
KL(mailbox,
security_code) Command that logs the current caller on to the specified mailbox. The caller is at
the top level menu (the menu that says “Press 1 to play your messages....”).
mailbox Any valid mailbox or a variable containing a mailbox.
security_code The security code for the specified mailbox.
Example:
R(G1,%S1)R(G2,%S2)P(G5)P(%S1,N)KL(%S1,%S2)
Greeting 1 says, “Please enter the mailbox you wish to log into.” After the caller
enters the mailbox, Amanda assigns it to %S1. Greeting 2 says, “Please enter the
mailbox’s security code.” After the caller enters the code, Amanda assigns it to
%S2. Next Amanda plays Greeting 5, “You are logging into mailbox”, followed by
the mailbox. KL(%S1,%S2) attempts to log the caller into the specified mailbox
using the specified security code.
Failure: Invalid mailbox
Invalid security code
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 225
ext_noKM Command that tells Amanda to do a supervised transfer to the specified extension,
create a conference call for the caller and the user at the extension (using the
dl_conference configuration setting), and record the call until detecting a hang-up
or #. Amanda then makes the recording a message for the user.
ext_no Series of DTMF digits that indicate an extension number.
Example:
128KM
causes Amanda to transfer the call (if she is processing a call) to extension 128,
starts a conference call, and records the conference call as a message for mailbox
128.
Failure: Invalid extension number
KP(mailbox,
security_code) Command that sets the security code for the specified mailbox.
mailbox Any valid mailbox or a variable containing a mailbox.
security_code String of DTMF digits that indicate the new security code for the
specified mailbox.
Example:
KP(128,”5404”)
causes Amanda to change the security code for mailbox 128 to 5404.
Failure: Invalid mailbox
mailbox is locked or read-only
Security code is an empty string, contains invalid characters, or exceeds limit set
by the configuration option security_min_length. You set this option using the Set-
up utility.
Alphabetical Token Reference (Continued)
Token Syntax Description
226 Installing Amanda@Work.Group
KR(file_or_box
[,recording_info])
Command that makes a recording and stores it as either a file or a message for the
specified mailbox.
file_or_box A string or variable indicating where the recording is to be stored.
It contains either a mailbox indicating whose message it is or a val-
id DOS file name. Use the complete path to the file unless the file
is in C:\AMANDA.
recording_info A number from 0 to 3 indicating whether the caller hears a beep (to
start recording) and the post record menu. The default is 1.
0 No beep; no post record menu.
1 Beep; no post record menu.
2 Beep; post record menu.
3 No beep; post record menu.
Examples:
KR(212)
makes the recorded response a new message for mailbox 212.
KR("C:\\MSG.VOX")
stores the response in the MSG.VOX file in the root directory. In both cases, the
caller hears the beep for recording but no post record menu.
NOTE:When using the KR() command, be sure to ask the caller to leave a
message. A suggested example is:
P(G1)KR(212)
Greeting 1 says, “Please leave a message at the tone. Finish by press-
ing # or hanging up.”
Failure: Invalid mailbox
Unable to create file
KS[(errorlevel)] Command that starts a system shutdown immediately.
errorlevel Optional. Specifies the exit code (a DOS errorlevel) at which the sys-
tem exits. The default exit code (errorlevel) is zero.
This command is used only in Extension fields.
Example:
KS(3)
immediately shuts down the system, exiting with the errorlevel set to 3. The error-
level can be used by another program or a DOS batch file to determine what action
should be taken next.
Failure: Does not fail
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 227
KT(Gn)Command for rotary training. Amanda plays the specified greeting. The greeting
should tell the caller to press or dial 0 (zero). If the caller presses DTMF 0,
Amanda sets the port to detect only DTMF digits and proceeds. If the caller dials
rotary 0, Amanda learns it and sets the port to detect only rotary digits.
This feature requires Rhetorex's Vantage VPS voice board with Rotary on Board.
GnThe greeting (n is replaced by 1-7) to indicate which greeting is to be
played.
Example:
KT(G3)
plays greeting 3 for rotary training.
Failure: Does not fail
KV(file,field,
value) Command that finds and deletes the first record in the specified file that has the
specified value in the specified field.
file A string or variable containing a valid DOS file name for the text or DBF
file. Use the complete path to the file unless the file is in C:\AMANDA.
No line in the file should exceed 143 characters. There is no limit to the
number of lines in the file.
field A number, string, or variable that indicates the number or name of a field.
value A string or variable that contains the data to be compared with the con-
tents of the specified field.
Example:
KV("C:\\LISTS\\PHONE.LST",4,"STEVE BRUCE")
searches for the first record in the PHONE.LST file that contains the value STEVE
BRUCE in field 4. If found, the entire record is deleted. If not found, no record is
deleted (but the command is still successful).
Failure: The file is read-only
Insufficient disk space to save file
File is not the correct format (text file containing comma-separated fields and car-
riage return/linefeed separated records or .DBF file)
Alphabetical Token Reference (Continued)
Token Syntax Description
228 Installing Amanda@Work.Group
L(file) Command that immediately changes the system prompts to use the specified
Amanda system language file. This changes the system prompts, but the greetings
of the individual mailboxes might need to be recorded by the users in the new lan-
guage.
file A string or variable containing the name of a valid Amanda system lan-
guage file (minus the .IDX extension and the DOS path). Amanda knows
that the system language file names end in .IDX and are located in the
Amanda directory.
Examples:
L(ENGLISH)
changes the prompts to those found in ENGLISH.IDX (if your system has a
Rhetorex voice board) or ENGLISH.BDX (if your system is connected to
a Norstar KSU) in the C:\AMANDA directory.
L(MEXICAN)
changes the prompts to those found in MEXICAN.IDX (if your system has a
Rhetorex voice board) or MEXICAN.BDX (if your system is connected to
a Norstar KSU) in the C:\AMANDA directory.
Failure: Does not fail (If you specify a file that doesn’t exist or is not a prompt
file, Amanda uses the current prompt file.)
LEN[string] Assumes the value of the total number of characters within a string or digits within
a number.
string Any string, number, or variable.
NOTE:The brackets in this syntax are bold. The brackets are a required part of
the syntax whenever you use LEN. Be careful not to confuse them with
the non-bold brackets that indicate that the syntax within the brackets is
optional.
Example:
LEN[7145551212]
assumes the value 10.
I(LEN[%S1],=,4,%S1)
checks the length of the DTMF entry stored in %S1 because all extensions have 4
digits. If %S1 contains a mailbox, Amanda goes to that mailbox. See the I() com-
mand for more information.
Failure: Does not fail
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 229
%M[(mailbox)] Command that returns the total number of messages for the specified or current
mailbox. Each port has its own %M.
mailbox Optional. A valid mailbox or a variable containing a mailbox. The default
is the current mailbox.
Example:
%M(321)
contains the number of messages stored for mailbox 321.
Failure: Invalid mailbox
M(greeting
[#mailbox],
repetition,delay)
When Amanda processes this command, she plays the specified greeting and waits
for a single DTMF digit to be pressed by the caller. Amanda immediately finds the
matching menu selection and continues processing at the specified mailbox. This
eliminates the normal delay for determining that a DTMF entry has been complet-
ed.
greeting One of the seven mailbox greetings (G1–G7). This greeting should be
a menu from which the caller is to make a selection.
mailbox Optional. Any valid mailbox. The default is the current mailbox.
repetition The number of times to play the greeting.
delay The amount of time (in tenths of seconds) to wait before repeating the
greeting.
This command is used only in Extension fields.
Examples:
M(G1,2,20)
Amanda plays Greeting 1 twice, pausing for two seconds before repeating it. If the
caller presses a DTMF digit, Amanda stops the greeting and uses the caller’s digit
to process the menu.
If the caller makes no selection at all, Amanda continues processing at the next to-
ken.
If the caller makes an invalid selection, Amanda restarts the M() command.
If the caller makes a valid selection (for example 5), Amanda immediately contin-
ues processing at the mailbox specified in the Menu field 5.
M(G1#111,2,30)
plays Greeting 1 from mailbox 111. If there is no response from the caller, Amanda
plays Greeting 1 again after a 3 second pause. If there is still no response, Amanda
executes the next token in the Extension field.
Failure: Invalid mailbox
Alphabetical Token Reference (Continued)
Token Syntax Description
230 Installing Amanda@Work.Group
%N System variable that contains the number of new messages for the current mailbox.
Each port has its own %N.
Example:
P(%N,N)
causes Amanda to say the number of new messages as a number.
N(file,field,value
{,field,variable})Command that searches the specified file for all the records that match the specified
value. This command changes the values in up to 8 fields in each matching record
using the values stored in the specified variables. If no matching records are found,
Amanda continues processing the next token. See also the V() command.
file A string or variable containing a valid DOS file name for the text or DBF
file. Use the complete path to the file unless the file is in C:\AMANDA.
No line in the file should exceed 143 characters. There is no limit to the
number of lines in the file.
field A number, string, or variable that indicates the number or name of a field.
The first field indicates what field to compare with value; the additional
(up to 8) fields indicate what fields to change. Each field is changed to the
value of its corresponding variable. (.DBF files have field names; text
files have field numbers.)
value A string or variable that contains the data to be compared with the con-
tents of the specified field.
variable One of port or global variables.
Example:
N("C:\\LISTS\\PHONE.LST",1,"RYAN GIGGS",3,%S1,2,%S2)
finds all records in the file "PHONE.LST" that have "RYAN GIGGS" in the first
field and replace the contents of field 2 with the value of %S2 and the contents of
field 3 with the value of %S1. Numbers are used for the fields because
PHONE.LST is a text file.
Failure: Specified file does not exist
Value of field not found within the file
O(time) Command that makes Amanda go on-hook for the specified amount of time. De-
pending upon the value used, you can cause a hookflash or a hang-up. This is par-
ticularly useful for generating an intermediate hang-up condition during token
processing without terminating the actual continued token processing. See also the
H() command.
time A number in tenths of seconds or a variable containing that number.
Example:
O(20)
causes Amanda to go on-hook for two seconds.
Failure: Does not fail
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 231
%P System variable that contains the previous mailbox, that is, the last mailbox access-
ed before the current mailbox. Each port has its own %P. See also %U (current
mailbox).
Example:
While accessing mailbox 990, %U is 990. Then a caller enters 222 and is trans-
ferred to that extension. As mailbox 222 is accessed, %U becomes 222, and %P be-
comes 990.
P[repetition]
(date,D
[,hangup])
Command that tells Amanda to say the specified number as a date.
repetition The number of times to repeat the date. The default is 1.
date A number in either of the following formats: MMDDYY (which
assumes the year 19YY,) or MMDDYYYY. For dates after 1999, you
must use MMDDYYYY.
Despite this format, the date is read in the order that most speakers of
the prompt language (specified using the Setup utility) expect to hear
it. If the year is the current year, Amanda does not read the year.
hangup Optional. The number 1 or 0 indicating how to process a hangup. The
1 means that the processing of this token ends. 0 means that the
processing of this token ends, the string of tokens is aborted, and the
channel hangs up so that it can wait for a new call.
Example:
P(06261994,D)
causes Amanda to say "June twenty-sixth, nineteen ninety-four"
Failure: Does not fail
Alphabetical Token Reference (Continued)
Token Syntax Description
232 Installing Amanda@Work.Group
P[repetition]
(amount,
currency
[,hangup])
Command that tells Amanda to say the specified number as an amount of
money.
repetition The number of times to repeat amount. The default is 1.
amount A number from 0 to 999 million.
currency Use one of the following:
$For dollars and cents.
FFor francs and centimes.
PFor pesos and centavos.
hangup Optional. The number 1 or 0 indicating how to process a hangup. The
1 means that the processing of this token ends. 0 means that the
processing of this token ends, the string of tokens is aborted, and the
channel hangs up so that it can wait for a new call.
Example:
P(06261994,$)
cause Amanda to say "Sixty-two thousand six hundred nineteen dollars
and ninety-four cents"
The monetary terms are always available, regardless of the system
language.
P[repetition]
(number,N
[,hangup])
Command that tells Amanda to say the absolute value of the number.
repetition The number of times to repeat absolute value. The default is 1.
number A number or variable representing a number from 0 to 999 million.
hangup Optional. The number 1 or 0 indicating how to process a hangup. The
1 means that the processing of this token ends. 0 means that the
processing of this token ends, the string of tokens is aborted, and the
channel hangs up so that it can wait for a new call.
NOTE:Use a condition to test whether the number is positive or negative. Use
a greeting that says “negative” or “minus” to handle negative
numbers.
Examples:
Suppose that %S1 contains -1234 and G1 contains the recording
“negative,” then
I(%S1,>,0,1001)P(G1)P(%S1,N)
causes Amanda to say “negative one thousand two hundred thirty-four”.
(mailbox 1001’s Extension field would not include the greeting—just the
command, P(%S1,N))
P(06261994,N)
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 233
P[repetition]
(time,T
[,hangup])
Command that tells Amanda to say the specified number as a time of day.
repetition The number of times to repeat the contents of the port variable. The
default is 1.
time A number or variable containing a number that specifies a time in the
24-hour HHMM format. However, Amanda says the time in a 12-hour
format, followed by A.M. or P.M.
hangup Optional. The number 1 or 0 indicating how to process a hangup. The
1 means that the processing of this token ends. 0 means that the
processing of this token ends, the string of tokens is aborted, and the
channel hangs up so that it can wait for a new call.
Example:
P(1826,T)
causes Amanda to say “Six, twenty-six P.M.”
Failure: Does not fail
P[repetition]
(A,string
[,hangup])
Command that tells Amanda to say the characters in the specified string.
For a space, Amanda says the word “space”.
repetition The number of times to repeat the contents of the string. The default
is 1.
string A string of letters from the alphabet and spaces.
hangup Optional. The number 1 or 0 indicating how to process a hangup. The
1 means that the processing of this token ends. 0 means that the
processing of this token ends, the string of tokens is aborted, and the
channel hangs up so that it can wait for a new call.
Example:
P(A,"GEORGE BEST")
causes Amanda to say “G,” “E,” “O,” “R,” “G,” “E,” “space,” “B,” “E,”
“S,” “T.”
Failure: Does not fail
P[repetition](D)
Command that tells Amanda to say the percentage of remaining disk space.
repetition The number of times to repeat the percentage of disk space. The
default is 1.
Examples:
P(D)
causes Amanda to say “The percentage of free disk space is” followed by
the percentage as a number, e.g., forty-two.
Failure: Does not fail
Alphabetical Token Reference (Continued)
Token Syntax Description
234 Installing Amanda@Work.Group
P[repetition]
(greeting
[,mailbox
[,hangup]])
Command that tells Amanda to play the specified greeting for the specified
or current mailbox.
repetition The number of times to repeat the greeting. The default is 1.
greeting One of the seven mailbox greetings (G1–G7).
mailbox Optional. Any valid mailbox or a variable containing a mailbox. The
default is the current mailbox.
hangup Optional. The number 1 or 0 indicating how to process a hangup. The
1 means that the processing of this token ends. 0 means that the
processing of this token ends, the string of tokens is aborted, and the
channel hangs up so that it can wait for a new call.
Example:
P(G1)
causes Amanda to play Greeting 1 for the current mailbox.
Failure: Invalid mailbox
P[repetition]
(M[,mailbox
[,hangup]])
Command that tells Amanda to say the total number of messages for the
specified or current mailbox.
Using this command cancels any pending Notify actions for the specified
message automatically.
When this command plays a message that is marked with Receipt
Verification, the verification message’s From field contains the mailbox
which executed this command.
repetition The number of times to repeat the number of messages. The default is
1.
mailbox Optional. Any valid mailbox or a variable containing a mailbox. The
default is the current mailbox.
hangup Optional. The number 1 or 0 indicating how to process a hangup. The
1 means that the processing of this token ends. 0 means that the
processing of this token ends, the string of tokens is aborted, and the
channel hangs up so that it can wait for a new call.
Example:
P(M,212)
causes Amanda to say the total number of messages for mailbox 212.
Failure: Invalid mailbox
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 235
P[repetition]
(Mn[,mailbox
[,hangup]])
Command that tells Amanda to play the message with the specified
number for the specified or current mailbox.
repetition The number of times to repeat the message. The default is 1.
nThe number of the message to be played.
mailbox Optional. Any valid mailbox or a variable containing a mailbox. The
default is the current mailbox.
hangup Optional. The number 1 or 0 indicating how to process a hangup. The
1 means that the processing of this token ends. 0 means that the
processing of this token ends, the string of tokens is aborted, and the
channel hangs up so that it can wait for a new call.
Example:
P3(M1,212)
causes Amanda to play message 1 for mailbox 212 three times.
Failure: Invalid mailbox
P[repetition]
(MN[,mailbox
[,hangup]])
Command that tells Amanda to play all new messages for the specified or
current mailbox.
repetition The number of times to repeat the message. The default is 1.
mailbox Optional. Any valid mailbox or a variable containing a mailbox. The
default is the current mailbox.
hangup Optional. The number 1 or 0 indicating how to process a hangup. The
1 means that the processing of this token ends. 0 means that the
processing of this token ends, the string of tokens is aborted, and the
channel hangs up so that it can wait for a new call.
Example:
P(MN)
causes Amanda to play the new messages for the current mailbox.
Failure: Invalid mailbox
Alphabetical Token Reference (Continued)
Token Syntax Description
236 Installing Amanda@Work.Group
P[repetition]
(N[,mailbox
[,hangup]])
Command that tells Amanda to play the Name/Extension recording of the
specified or current mailbox. If there is no recording, nothing is played.
See also
P[repetition](U[,mailbox]).
repetition The number of times to repeat the Name/Extension recording. The
default is 1.
mailbox Optional. Any valid mailbox or a variable containing a mailbox. The
default is the current mailbox.
hangup Optional. The number 1 or 0 indicating how to process a hangup. The
1 means that the processing of this token ends. 0 means that the
processing of this token ends, the string of tokens is aborted, and the
channel hangs up so that it can wait for a new call.
Example:
P(N)
causes Amanda to play the Name/Extension recording for the current
mailbox.
Failure: Invalid mailbox
P[repetition]
(DTMF) Command that tells Amanda to say a number as DTMF digits. This is
usually used for repeating the number corresponding to the DTMF tones
entered by a caller.
repetition The number of times to repeat the DTMF digits. The default is 1.
DTMF A number or variable containing a series of DTMF digits.
Example:
P(%S5)
causes Amanda to say the DTMF digits in %S5. For example, if %S5
contains the number 411, Amanda says 4–1–1 instead of four hundred
eleven.
Failure: Does not fail
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 237
P[repetition]
(prompt_no,V
[,hangup])
Command that tells Amanda to look for the specified prompt number in the
current system language file. Then Amanda plays the prompt associated
with that number.
repetition The number of times to repeat the prompt. The default is 1.
prompt_no The number or variable containing the number for the prompt. The
current range is from 1 to 477. (For some languages, some of the
prompt numbers reference blank messages.)
hangup Optional. The number 1 or 0 indicating how to process a hangup. The
1 means that the processing of this token ends. 0 means that the
processing of this token ends, the string of tokens is aborted, and the
channel hangs up so that it can wait for a new call.
Example:
P2(15,V)
causes Amanda to play prompt number 15 twice.
Failure: Does not fail
P[repetition](R)
Command that tells Amanda to say the DTMF digits entered by a caller
who requested relay paging notification. (These digits are stored in %R.)
This command can be used in either field, but makes the most sense when
used in a Notify Method field.
repetition The number of times to repeat the DTMF digits. The default is 1.
Example:
P(R)
causes Amanda to say the DTMF digits stored in the system variable %R.
You can also use:
P(%R)
Failure: Does not fail
Alphabetical Token Reference (Continued)
Token Syntax Description
238 Installing Amanda@Work.Group
P[repetition]
(U[,mailbox
[,hangup]])
Command that tells Amanda to play the Name/Extension recording of the
specified or current mailbox. If there is no recording, Amanda says
“mailbox,” followed by the digits for the mailbox. See also
P[repetition](N[,mailbox]).
repetition The number of times to repeat the Name/Extension recording. The
default is 1.
mailbox Optional. Any valid mailbox or a variable containing a mailbox. The
default is the current mailbox.
hangup Optional. The number 1 or 0 indicating how to process a hangup. The
1 means that the processing of this token ends. 0 means that the
processing of this token ends, the string of tokens is aborted, and the
channel hangs up so that it can wait for a new call.
Example:
P(U)
causes Amanda to play the Name/Extension recording for the current
mailbox. If it doesn’t exist, Amanda says the digits for the mailbox.
Failure: Invalid mailbox
P[repetition](V)
Command that tells Amanda to say the digits in the Variable field of the
Notification record.
repetition The number of times to repeat the contents of the Variable field. The
default is 1.
Example:
P2(V)
causes Amanda to say the digits in the Variable field twice. The following
also works:
P2(%V)
Failure: Does not fail
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 239
Q({greeting
[#mailbox][,E]}) Command that allows you to ask a caller a series of questions and store all the call-
er’s responses as a single message for the current mailbox. Each question is record-
ed as a greeting which Amanda plays back with a tone. Then Amanda records a
response and goes on to the next question. Up to 20 questions are allowed. To ask
more than 7 questions (after using Greetings 1 to 7 for the current mailbox) you can
use greetings from other mailboxes by specifying which mailbox’s greeting to ac-
cess with a # sign followed by the mailbox, e.g., G7#123 would use greeting 7 from
mailbox 123. You use the Q() command to create voice forms or implement some
IVR applications.
This command is used only in Extension fields.
greeting One of the seven mailbox greetings (G1–G7).
mailbox Optional. Any valid mailbox. The default is the current mailbox.
EGives the caller the opportunity to edit (review, rerecord, append, or can-
cel) the previous group of answers.
If additional token language processing is required after the caller has hung up, use
the H token as part of the token string.
Examples:
Q(G1,G2,G3,G4,G5,G6,G7,G1#9000,G2#9000)
causes Amanda to ask 9 questions recorded in the specified greetings, record 9 re-
sponses, and store the responses as one message for the current mailbox, regardless
of what mailbox’s provide the greetings.
Q(G1,G2,G3,E)
records three answers from the caller and then gives the caller an opportunity to re-
view those answers as if they were one message. When editing, a menu gives the
caller the options of re-recording, appending to or canceling the answers of that
group.
Q(G1,G2,E,G3,G4,E)
asks the caller two questions and then allows the caller to edit those answers. Once
the caller presses 9 to save, Amanda asks the next two questions and then allows
the caller to edit the second group of answers.
NOTE:While editing, pressing 4 to cancel erases all the previous answers (not
just those in the group being edited) and restarts the Q() command.
Failure: Invalid mailbox
Invalid greeting
Alphabetical Token Reference (Continued)
Token Syntax Description
240 Installing Amanda@Work.Group
%R System variable (the relay variable) that contains the DTMF digits entered by the
caller who requested relay paging notification. Each port has its own %R. For more
information, see Administering Amanda@Work.Group. This is primarily used to
send up to 16 digits of information to a user’s pager/beeper.
This token is used only in Notify Method fields.
Example:
9,%VW(9,V)P(U)P(R)
causes Amanda to call someone at home and say the telephone number and other
information in the relay variable.
R(greeting
[#mailbox],
variable
[,timeout1
[,timeout2]])
Command that plays a greeting from the current or specified mailbox and
stores the caller’s DTMF entry as a number in the specified variable. The
greeting is interrupted as soon as the first DTMF tone is entered. If there
is no DTMF entry or if the timeout occurs, the variable is set to the empty
string.
greeting One of the seven mailbox greetings (G1–G7).
mailbox Optional. Any valid mailbox. The default is the current mailbox.
variable One of the port or global variables.
timeout1 A number from 0 to 10500 that represents the time in tenths of seconds
to wait for the first DTMF digit after playing the greeting. The default is
1.2 seconds.
timeout2 A number from 0 to 10500 that represents the time in tenths of seconds
to wait between additional DTMF digits (after the first). The default is the
value of the configuration option tmo_dtmf.
Example:
R(G1,%S6,20)
stores a telephone number entered by a caller for later use. Greeting 1 is
“Enter your telephone number, finish by pressing the # sign.” The caller’s
entry is stored as a number in the port variable %S6. Amanda waits two
seconds after the greeting before deciding that the caller is not going to en-
ter a telephone number.
R(G1#111,%S1)
plays Greeting 1 of mailbox 111. The DTMF digits entered by the caller
become the value of %S1.
Failure: Invalid mailbox
Invalid greeting
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 241
%S0 %S1
%S2 %S3
%S4 %S5
%S6 %S7
%S8 %S9
%S10 %S11
%S12 %S13
%S14 %S15
%S16 %S17
%S18 %S19
Each telephone port has its own set of 20 %S variables where you can store, mod-
ify, or retrieve information. One port’s %S1 is not the same as another port’s %S1.
If Port 1 changes %S1, it does not change the value of Port 2’s %S1. Initially, each
variable is equal to the empty string. Each variable can contain a string of up to 143
characters.
See also %G0–%G9.
NOTE:The [(), ](), and |() commands can be used only with %S0 through %S9.
The variables %S10 through %S19 cannot be read from, written to, or ap-
pended to any DOS file.
Example:
+(%S0,5)
adds five to the current value of %S0.
=(%S12,714)
assigns the area code 714 to %S12.
I(%S12=714,555)
causes Amanda to go to the Extension field for mailbox 555 because the condition
is true (%S12 does equal 714).
Failure: Invalid variable name (such as %S52)
Alphabetical Token Reference (Continued)
Token Syntax Description
242 Installing Amanda@Work.Group
S(port,[string],
[variable],
[termination],
[length],[time-
out])
Command that gives Amanda access to other computers via the serial ports. Aman-
da can send a string to and/or receive a string from the remote computer. When re-
ceiving, Amanda terminates the connection when the first of the following occurs:
• Amanda receives the specified termination string
• She receives the maximum number of characters
• A timeout occurs
When sending, Amanda terminates the connection after the string is sent.
Before using this command, make sure the configuration settings for the physical
serial port have been defined.
port The number for or a variable containing the number for the logical se-
rial port (1,2,3,4) mapped onto a physical COM port by the configura-
tion option serial_port1, serial_port2, serial_port3, or serial_port4.
string Optional. A string or variable containing the characters to send to the
specified serial port. It can contain alphanumeric characters as wells as
variables and the following special characters:
\A Attention, which is a bell sound (Ctrl+G)
\N Newline (Ctrl+J)
\R Return (Ctrl+M)
\T TAB (Ctrl+I)
\\ Backslash, the actual "\" character.
The default is to send no string to the serial port.
variable Optional. The port or global variable that stores the response.
The default is not to store a response.
termination Optional. A string or variable that defines the characters that, when
read, stop Amanda from reading the serial port. This can use the same
special characters as string. The default is "\R\N", the carriage return/
linefeed pair that usually end a line in a text file. The terminating char-
acter, if any, does not become part of variable.
length Optional. A number or a variable containing a number. Its absolute
value defines the maximum number of characters to receive over the
serial port. The default is -143. Use a positive value for length when
you are receiving a packet of characters, you know its exact size, and
you want the command to fail if fewer characters are received. Use a
negative number otherwise.
timeout Optional. A number or variable that defines the maximum time, in sec-
onds, that Amanda should wait for the first character and also between
characters being received on the serial port. The default is the setting
for the configuration option tmo_serial.
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 243
S token continued Example:
S(2,%S3,%S4,,,50)
both sends and receives. The command uses COM port 2. %S3 stores the string to
be sent. %S4 stores the string that is received. Amanda waits a half second for the
first character and between characters.
S(2,%S3)
only sends. The command uses COM port 2. %S3 stores the string to be sent. This
command has non-standard syntax. Because all the parameters after the string to be
sent are not being used, this command does not need the additional commas.
S(2,,%S4,,,50)
only receives. The command uses COM port 2. %S4 stores the string that is re-
ceived. Amanda waits a half second for the first character and between characters.
Failure: Physical port not available
Logical port not configured properly
If a timeout stops Amanda from receiving information before the maximum num-
ber of characters is received and the length is a positive number, Amanda considers
the command a failure.
%T System variable that contains the current connect time, the number of seconds that
the current port/call has been active. Each port has its own %T.
Examples:
P(%T,N)
causes Amanda to say the amount of connect time as a number. See the P() com-
mand for more information.
Alphabetical Token Reference (Continued)
Token Syntax Description
244 Installing Amanda@Work.Group
T(file,phone_no
[,tokens]) Command that sends faxes to either a specified telephone number or to a connected
call. Before using this command, be sure at least one fax modem is installed and
configured on Amanda.
Before using this command, make sure the configuration settings for the physical
serial port have been defined.
file The file name of the fax you wish to transmit. It can be any valid DOS
file name. Use the complete path to the file unless the file is in
C:\AMANDA.
phone_no The telephone number (or a variable containing that number) for the fax
device that accepts the transmission. Use the empty string to make
Amanda wait for a call to ring into the fax port.
tokens Optional. A string or variable that defines the actions Amanda takes to
connect the call to the fax port. For more information, please see the ex-
ample for the J() command.
This command is used only in Extension fields.
Examples:
T(C:/FAXES/NEWINFO.FAX,%G6)
allows the user to request a fax and have the supplier of that fax send it to the pro-
vided telephone number. This is commonly called a “two-call fax back”. NEWIN-
FO.FAX is the name of the file, and %G6 contains the fax telephone number.
T(C:/FAXES/NEWINFO.FAX,"",%S5)
allows the user to request a fax and have it sent as part of the current call. This is
commonly called a “one-call fax on demand”. NEWINFO.FAX is the name of the
file, and %S5 provides the tokens that connect the call to the FAX port.
Failure: Fax modem not configured properly
Physical port not available
Logical port not configured properly
%U System variable that contains the current mailbox number. Each port has its own
%U. See also %P.
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 245
U-ext_no Command that performs partially supervised transfers. Amanda does not transfer
the call if she detects a busy signal. To use the U token, the setting for Maximum
Rings for the mailbox must be set to 1.
ext_no Series of DTMF digits that indicate an extension number.
This command is used only in Extension fields.
Example:
U-144
causes Amanda to call extension 144 (if Amanda is processing a call). If the exten-
sion rings, she transfers the call and hangs up. If the extension is busy, Amanda lets
the caller know that.
Failure: Does not fail
%V System variable that contains the value of the Variable field in the current Notifi-
cation record. Each port has its own %V.
This token is used only in Notify Method fields.
Example:
If the only difference in a Notification template for mailboxes is the pager/beeper
telephone number that Amanda should call, %V can store that number.
9,%VW(3,P)%U*%M*%N#
causes Amanda to call the user and play the number of messages.
Alphabetical Token Reference (Continued)
Token Syntax Description
246 Installing Amanda@Work.Group
V(file,field,
value{,field,
variable}[,n])
Command that searches the specified file for the nth record that has the
specified value in the specified field. It retrieves values from up to 8 other
fields in that record, putting the retrieved values in the specified variables.
See also the N() command.
file A string or variable containing a valid DOS file name for the text or .DBF
file. Use the complete path to the file unless the file is in C:\AMANDA.
No line in the file should exceed 143 characters. There is no limit to the
number of lines in the file.
field A number, string, or variable that indicates the number or name of a field.
The first field indicates what field to compare with value; the additional
(up to 8) fields indicate what fields to copy into the corresponding vari-
ables. (.DBF files have field names; text files have field numbers.)
value A string or variable that contains the data to be compared with the con-
tents of the specified field.
variable One of port or global variables.
n(Optional) This parameter can be used only with ASCII files. A number
indicating which matching record to use. For example, if n is 3, the first
two matching records are ignored and data is taken from the third match-
ing record.
Amanda identifies n because, when it is used, there is an even number of
parameters instead of an odd number.
Example:
V("C:\\LISTS\\PHONE.LST",1,"JOHN",3,%S1,2,%S2)
searches the file PHONE.LST for the first record that has the value JOHN
in field 1. If the search is successful, the value in field 3 of that record is
stored in %S1 and the value in field 2 is stored in %S2.
Failure: If no record is found
Invalid file
Invalid field
%W System variable that contains the day of the week (1 is Sunday, and 7 is Saturday).
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 247
W(n,[event
[,mailbox]]) Command that tells Amanda to:
• Wait a number of tenths of a second
• Wait for an event, such as a dial tone or another appropriate
answer. If the event does not occur, Amanda goes to the spec-
ified mailbox.
nWithout an event parameter (P, V, or T), a number of tenths of a second.
For dial tone (T), the number of seconds.
For pager (P) and voice (V), the number of rings to wait before continu-
ing. If n is 0 for pager or voice, the 0 is replaced with the value of rmt_rna,
a configuration option that you define using the Setup utility.
event The event that Amanda waits for:
PA pager answer
VA voice answer
TThe dial tone
mailbox Any valid mailbox or a variable containing a mailbox. Specifies the mail-
box to which control should be transferred if the event does not occur.
Examples:
W(3)
makes Amanda pause for 3 tenths of a second
W(3,P)
makes Amanda wait up to three rings for a paging/beeping system to answer. Use
this to confirm that the paging company answered before playing the DTMF digits
to be displayed on the pager.
W(4,V,111)
makes Amanda wait up to four rings for a voice. If a voice is detected, processing
continues with the next token. Otherwise, control is transferred to mailbox 111.
Failure: Invalid mailbox
Event does not occur and no mailbox is specified
%X System variable that contains the codes needed to get the transfer dial tone on the
current port. Each port has its own %X. This is the setting of the dl-dtwait config-
uration option (usually F-).
Alphabetical Token Reference (Continued)
Token Syntax Description
248 Installing Amanda@Work.Group
X[(file)] Command that creates the specified file or LIGHT.ON. Used in conjunction with
the Y() and Z() commands, this command can control Amanda’s processing of to-
kens.
file A string or variable containing a valid DOS file name for a text file. The
default is to create the file LIGHT.ON in the mailbox’s directory.
Example:
A user’s message waiting indicator toggles on and off. For the first message,
Amanda should turn the indicator on. The indicator should be left on for the second
and later messages (until they are all listened to). So you use:
•Z() to check whether the indicator is on or not (if LIGHT.ON exists, the indi-
cator is on).
•X() to create the LIGHT.ON file when a message arrives and the indicator is
not on.
•Y() to delete LIGHT.ON when the indicator is turned off because the user has
listened to all the messages.
Failure: Does not fail
%Y System variable that contains the current date in American format: MMDDYYYY.
Example:
P(%Y,D)
causes Amanda to say the current date (contained in %Y) as a date.
See the P() command for more information.
Y[(file)] Command that deletes the specified file or LIGHT.ON.
file A string or variable containing a valid DOS file name for a text file. The
default is to delete the file LIGHT.ON in the mailbox’s directory.
Example:
Y(C:\\AMANDA\\FOOBAR.TXT)
causes Amanda to delete FOOBAR.TXT.
See also the X() command.
Failure: Does not fail
%Z System variable that contains the current time in 24-hour format: HHMM.
Example:
P(%Z,T)
causes Amanda to say the current time (contained in %Z) as a time.
See the P() command for more information.
Alphabetical Token Reference (Continued)
Token Syntax Description
Chapter 15: Programming Amanda 249
Troubleshooting
Check for the following mistakes:
1. Did you start the string of tokens without @ when you wanted Amanda
to perform a hookflash or PCPM?
2. Did you start the string of tokens with @ when Amanda should NOT
perform a hookflash or PCPM?
3. If the tokens are in an Extension field, did you forget that both Do Not
Disturb and Call Screening must be OFF?
4. Did you check the trace file for information about what went wrong?
TIP:Remember that when a string of tokens in an Extension
field fails, Amanda goes to the mailbox specified in the
Done Chain for that mailbox. If you are testing a program
and are not sure which strings of tokens fails, use different
mailboxes in the Done Chain fields to help you. For exam-
ple, if you do not know which of two strings fails, you
might put mailbox 4000 in one Done Chain and mailbox
4001 in the other. If you use
@P(G1, your_personal_mailbox)
in the Extension field for 4000 and use
Z[(file)] Command that tests for the existence of the specified file or LIGHT.ON. If the file
is there, Amanda immediately stops processing the rest of the tokens for this mail-
box. Otherwise, the next token is executed.
file A string or variable containing a valid DOS file name for a text file. The
default is to delete the file LIGHT.ON in the mailbox’s directory.
Example:
Z()X()
causes Amanda to check for LIGHT.ON. If it is not there, the X() command causes
Amanda to create it.
See also the X() command.
Failure: Does not fail
Alphabetical Token Reference (Continued)
Token Syntax Description
250 Installing Amanda@Work.Group
@P(G2, your_personal_mailbox)
in the Extension field for 4001, then you know which string
fails based on which of your personal greetings Amanda
plays.
Chapter 16:
Programming Examples
System Paging of a User for Special Callers
This example illustrates inter-mixing tokens with Amanda’s standard call
processing.
Application
This application creates a special mailbox (for example, 611) for family,
friends, or special customers. When callers access this mailbox, Amanda
pages you over the telephone paging system in your office. After letting you
know that you have an important call, Amanda transfers that call to your
extension through a “backdoor” even if your regular extension mailbox (for
example, 111) might have its Do Not Disturb setting ON. The steps required
to implement this feature might be summarized as follows:
1. Put the caller on hold.
2. Access the telephone switching system paging feature.
3. Say something such as “There is an important call for David.”
4. Transfer the call to a “backdoor” mailbox that rings the extension.
248 Installing Amanda@Work.Group
Translating to Amanda’s Tokens
This could be translated into Amanda tokens as follows:
1. Dial the code for putting the caller on Transfer Hold (which is normal
processing if the first character is not an @ sign).
2. Dial the telephone switching system paging access code, for example,
33* (if that is your system’s code for a system page.)
3. Play a greeting that you have already recorded such as “There is an
important call for David” using the P() token.
4. Dial the code for retrieving the caller from Transfer Hold and then trans-
fer the caller to a “backdoor” mailbox that rings the extension. For
example, to retrieve the caller you use %X and to access the “backdoor”
mailbox use the G() token.
Result
The final result might be:
33*P(G1)%XG(6111)
where G1 for the current mailbox has the “important call for David”
recording and mailbox 6111 transfers the call to the extension 111 by having
111 in its Extension field with Do Not Disturb set to OFF and its Lock ON.
Switching and Maintaining Languages
This example illustrates how you can completely over-ride Amanda’s
standard processing.
Amanda has the ability to support multiple languages simultaneously on any
port. The only requirements are that you install an alternative language
prompt file and you configure the mailboxes to allow a caller to change to
the alternate language. Additionally, you can control which mailboxes a
caller has access to when they select a specific language.
Chapter 16: Programming Examples 249
Application
Let’s start by allowing a caller to select outgoing greetings in a different
language. When a call is answered by Amanda, processing begins at the
Company Greeting mailbox (which is 990 by default.) After the greeting is
played, processing (by default) continues at mailbox 991 which plays the
caller Instructions. During either the Greeting (990) or the Instructions (991)
you can give the caller the option to press a digit to hear the Instructions in a
different language. When the caller enters the language digit, Amanda
should then be configured to access another mailbox that contains the proper
Instructions using the Token Programming Language.
The following diagram helps illustrate this:
This now gives your callers the option to hear their instructions in the
language of their choice (realize that you can have additional language
selections as additional menu choices). However, after the caller selects
Spanish by pressing 1, when they access a mailbox, Amanda still says in
English, “Please hold while I try that extension.” We have changed which
language instructions a caller hears, but we still have not changed which
250 Installing Amanda@Work.Group
language system prompts the caller hears. To change the system prompts to
another language we must use tokens (and of course have installed the
appropriate language prompts).
Using Amanda’s Tokens
The token to change system prompts is L(). To change to the Mexican
Spanish system prompts, use L(MEXICAN) provided that the Mexican
Spanish system prompts file resides in the Amanda directory and is named
MEXICAN.IDX (if your system has a Rhetorex voice board) or
MEXICAN.BDX (if your system is connected to a Norstar KSU).
(Argentinian Spanish is ARGENTIN.IDX or ARGENTIN.BDX.)
To accomplish this, we could use another mailbox that changes the system
prompts to Mexican and then continues processing wit the Spanish Caller
Instructions as follows:
mailbox 980’s Extension field contains the tokens @L(MEXICAN)G(981)
which causes Amanda to:
1. Not put the caller on transfer hold
2. Change the system prompts to the file "MEXICAN"
3. Continue processing at mailbox 981.
Chapter 16: Programming Examples 251
NOTE:There are several ways this same activity could have been
accomplished. For example, instead of using the G(981) to-
ken, mailbox’s RNA Chain could have had 981 in it. (We
use the RNA Chain, since Amanda returns Ring No An-
swer after successfully performing the tokens in the Exten-
sion field).
Another Consideration
This works for most situations. However, there is one final consideration.
What happens if the caller enters an invalid extension or choice? By
definition, an invalid mailbox has no Done Chain. As a result, Amanda
defaults to using the Done Chain of the Company Greeting mailbox on that
port.
The following diagram illustrates this:
The result is that a caller, who has selected Spanish and entered an invalid
mailbox, eventually ends up at the English Instruction mailbox!
252 Installing Amanda@Work.Group
To have callers always access the proper language Instruction mailbox, you
can add a control structure to Amanda. In this example, we might perform
the following:
1. If an alternate language is selected, remember which language was
selected.
2. Before playing the default Instruction mailbox, determine which lan-
guage Instruction mailbox should play and continue processing at that
mailbox.
Using Amanda’s Tokens
This could be accomplished with tokens as follows:
1. To remember that a specific language was selected, we could use a
storage (variable) token such as %S1 to have a value that represents the
language. To assign %S1 a value, we use the =() token. For example,
=(%S1,"MEXICAN") stores the value "MEXICAN" into %S1.
2. To determine which language Instruction mailbox to access, we could
use the I() token, often called the If token, which allows Amanda to con-
tinue processing at the correct mailbox. For example, I(%S1,=,"MEXI-
CAN",981) checks the value of %S1 for "MEXICAN" and if it matched,
then continues processing at mailbox 981 (the Spanish Caller Instruc-
tions mailbox in this example). Finally, to make sure that this occurs
before playing the default Instruction mailbox (in this example mailbox
991) we need to insert this control mailbox between the Company
Greeting mailbox (990) and the Instruction mailbox (991) as shown in
the next diagram.
Chapter 16: Programming Examples 253
This configuration now changes Amanda’s standard processing and keeps
the caller connected to the correct language Instruction mailbox. It works
because whenever a new call is answered, Amanda initializes the %S tokens
to "" (the empty string). Therefore, if the caller never presses 1 for Spanish,
then %S1 is never set to the value "MEXICAN" and control is always passed
on to mailbox 991 from mailbox 992.
Order Shipment Information
This example illustrates how you can interact with data files to retrieve
useful information that is given to callers by request.
254 Installing Amanda@Work.Group
Application
The application is as follows:
1. Ask the caller to enter an order number (let’s assume that it is five
digits).
2. Determine whether or not the corresponding order has shipped.
3. If the order has not shipped, inform the caller. Otherwise, tell the caller
the date the order was shipped.
In order for Amanda to determine an order’s shipped status and its ship date,
she needs to retrieve information from some source. One possible way she
can obtain the data is by using the serial, S(), token to request it from another
computer. An alternative solution is to access the information by looking in a
file on Amanda’s hard disk (or alternatively, a network server). For this
example, we use the second implementation and assume that the following
files exist on Amanda’s hard disk in the root directory:
SHIPPED - An ASCII text file with order numbers that have been shipped
(one per line), for example:
11111
22222
33333
12345
SHIPDATE - An ASCII text file where each line contains an order number
and its ship date separated by a comma (one per line), for example:
11111,06301994
22222,07011994
33333,07061994
12345,07121994
Chapter 16: Programming Examples 255
Translating to Amanda’s Tokens:
1. To ask the caller for an order number, use R(G1,%S1,20) where Greeting
1 has the recording “Please enter the five-digit order number now.”
After the caller enters the order number, Amanda can perform some
additional checking. For example, to determine if a five-digit order
number was entered, use I(LEN[%S1],!,5,mailbox). If the number of
digits stored in %S1 is not equal to 5, Amanda continues processing
with mailbox mailbox.
2. To determine whether or not the order shipped, you examine the file
SHIPPED to find out if it contains the caller’s order number. Use
?(%S1,C:\\SHIPPED,mailbox)to find out whether or not a string (%S1),
which contains the order number, is in a file SHIPPED. If it is, Amanda
continues processing with mailbox mailbox.
3. If the order number is not in the file SHIPPED, Amanda continues pro-
cessing at the token after the ?() token. Therefore, to tell the caller that
an order has not shipped, you use P(G1) where Greeting 1 plays, “Sorry,
but your order has not yet shipped, please call back tomorrow.” To tell
the caller the order’s ship date, first determine that date using
V(C:\\SHIPDATE,1,%S1,2,%S2), which scans the first column of the
file SHIPDATE for the value in %S1. After finding the first match,
Amanda stores the value in the second column as %S2. Then you use
P(G1)P(%S2,D) to tell the caller the date. Here Greeting 1 plays, “Your
order was shipped on.”
Summary
To summarize the above, the mailbox settings and tokens are as follows:
mailbox Extension/Recording Done
Chain
2000 @R(G1,%S1,20) I(LEN[%S1],!,5,2001)G(2002)
2001 “Your order number must be five digits. Good-bye.” 999
2002 @?(%S1,SHIPPED,2003)P(G1) 999
2003 @V(SHIPDATE,1,%S1,2,%S2) P(G1)P(%S2,D) 999
256 Installing Amanda@Work.Group
One-call and Two-call Faxbacks
You can use fax files and the token programming language to perform one-
call and two-call faxbacks. Most of this functionality is preconfigured for
you inside Amanda using specific mailboxes.
A one-call faxback is a call from a fax machine so that a document can be
faxed to the caller at that fax machine. Unless you have a toll-free telephone
line, the faxing is at the caller’s expense.
A two-call faxback requires two calls. Someone calls from his telephone,
indicates what documents to fax, and leaves his fax number. Amanda calls
the fax machine and sends the documents. This second call is at your
expense, so you may want to do two-call faxbacks only in your area code or
under other special circumstances.
You must have already installed and configured an appropriate fax modem
for Amanda before the following examples can work.
Sending Faxes to Amanda
Before you can send faxes from Amanda, the data to be faxed must be stored
on the hard drive. Because Amanda uses a proprietary fax format, you must
fax the data to her. You can set up a mailbox to do both of the following:
• Receive the data that you fax to Amanda
• Store the faxes with numbered names in the C:\FAX directory, from
which they can be used in one-call and two-call faxbacks
You can also create the documents to be faxed using Amanda Fax. Copy
those documents to Amanda using Amanda Monitor or the FileCopy
command on Amanda Standalone’s Main screen. For more information
about Amanda Fax, see Using Amanda@Work.Group Workstation Features.
Chapter 16: Programming Examples 257
If you decide to use a fax machine and a mailbox, the mailbox that performs
these tasks must have:
Extension Field: @R(G1,%S1,30)J(“C:/FAX/
%S1”,””,”%X%FH”)G(999)
DND: OFF
Screen Calls: OFF
Store Messages: YES
Greeting 1: Please enter the number of the fax that you are sending
new.
%S1 must not be used in any other application.
%X must be defined in 1001.PBX.
%F must be the extension that is physically connected to the fax modem
and must be set in the install.cfg file, the file controlled by the Setup
utility.
Do not enter more than eight digits in response to this greeting (because
of DOS naming conventions). The number you enter becomes the name
of the file. For example, if you type in 32, the fax is stored as
C:\FAX\32.
NOTE:You must have created the C:\FAX directory previous-
ly. Amanda does not create this directory for you.
One-call Faxback
To set up a one-call faxback, you need to use one mailbox for each
document. If you have no more than ten documents, you need only one
mailbox for the greeting that supplies the menu of available documents.
The following example assumes that you have three documents and uses
only four mailboxes. The documents are named TECH1, TECH2, and
TECH3 to represent technical reports #1 through #3. They are stored in
C:\FAX. It uses mailboxes 92000 to 92003, but you can use any mailboxes.
258 Installing Amanda@Work.Group
Mailbox 92000 contains the menu. It should have the following settings and
greetings:
Extension Field: blank
DND: ON
Store Messages: NO
Greeting 1: If you are calling from your fax machine, please press
the number corresponding to the technical report you
are interested in. For report #1 on SMDI, press 1. For
report #2 on Service Plans, press 2. For report #3 on
Upgrading Voice Boards, press 3.
Menu 1: 92001
Menu 2: 92002
Menu 3: 92003
Mailbox 92001’s Extension field contains the tokens that send technical
report #1.
Extension Field: @T('C:/FAX/TECH1','','P(G1)%X%FH')
DND: OFF
Store Messages: NO
Greeting 1: Please press the start button on your fax machine at the
tone.
Mailbox 92002’s Extension field contains the tokens that send technical
report #2.
Extension Field: @T('C:/FAX/TECH2,'','P(G1)%X%FH')
DND: OFF
Store Messages: NO
Greeting 1: Please press the start button on your fax machine at the
tone.
Mailbox 92003’s Extension field contains the tokens that send technical
report #3.
Extension Field: @T('C:/FAX/TECH3,'','P(G1)%X%FH')
DND: OFF
Store Messages: NO
Greeting 1: Please press the start button on your fax machine at the
tone.
Chapter 16: Programming Examples 259
NOTE:All the quotation marks in these token examples are single
quotation marks (although double quotation marks can be
used). Forward slashes are used (although double back-
ward slashes \\ can also be used with this token).
Two-call Faxback
This example allows the caller to select one or more fax documents, and
leave his fax number. The steps are as follows:
1. Request the fax area code (this is to determine whether or not to set up
for long distance dialing).
2. Confirm the area code. If it is not confirmed, go back to step 1.
3. Request the fax telephone number.
4. Confirm the telephone number. If it is not confirmed, go back to step 3.
5. Give the caller the fax document selections and allow him to make more
than one selection. In this example, the documents are named TECH1,
TECH2, and TECH3 to represent technical reports #1 through #3. The
files are stored in C:\FAX.
Mailbox 1000’s Extension field is programmed to ask the caller for his area
code and store the DTMF tones entered by the caller as the variable %S1.
Next it says the numbers that were entered by the caller so the caller can
confirm, reenter, or exit the faxback routine.
Extension Field: @R(G1,%S1,20)P(G2)P(%S1)M(G3,2,30)
DND: OFF
Store Messages: NO
Greeting 1: Please enter the area code of your fax machine now.
Greeting 2: You entered area code:
Greeting 3: If this area code is correct, press 1 now.
If this area code is not correct and you want to re-enter
it, press 2 now.
If you do NOT want to have documents faxed to you,
press 3 to exit.
Menu 1: 1001
260 Installing Amanda@Work.Group
Menu 2: 1000
Menu 3: 991
Mailbox 1001’s Extension field contains the tokens that determine whether
or not the entered area code is local (assuming that the local area code is
714). If the area code is not local, it stores the long distance dialing digit '1' in
the variable %S0.
Extension Field: @I(%S1,=,'714',1002)=(%S0,'1')G(1003)
DND: OFF
Store Messages: NO
If the area code is local, mailbox 1002’s Extension field sets both the long
distance dialing string and the area code string to '' (the empty string).
Extension Field: @=(%S0,'')=(%S1,'')G(1003)
DND: OFF
Store Messages: NO
Mailbox 1003’s Extension field contains the tokens that request the fax
telephone number and stores it in the variable %S2.
Extension Field: @R(G1,%S2,40)P(G2)P(%S2)M(G3,2,30)
DND: OFF
Store Messages: NO
Greeting 1: Please enter the telephone number for your fax ma-
chine now.
Greeting 2: You entered the fax telephone number:
Greeting 3: If this fax telephone number is correct, press 1 now.
If this number is not correct and you want to re-enter it,
press 2 now.
If you do NOT want to have documents faxed to you,
press 3 to exit.
Menu 1: 1004
Menu 2: 1003
Menu 3: 991
Chapter 16: Programming Examples 261
Mailbox 1004 contains a menu that lists the available documents. It should
have the following settings and greetings:
Extension Field: @<('9,%S0%S1%S2')M(G1,2,30)
DND: OFF
Store Messages: NO
Greeting 1: Please press the number corresponding to the technical
report you are interested in. For report #1 on SMDI,
press 1. For report #2 on Service Plans, press 2. For re-
port #3 on Upgrading Voice Boards, press 3.
Menu 1: 10041
Menu 2: 10042
Menu 3: 10043
Mailbox 10041’s Extension field contains the tokens that send technical
report #1.
Extension Field: @P(G1)>('C:/FAX/TECH1')G(1005)
DND: OFF
Store Messages: NO
Greeting 1: The technical report on SMDI will be faxed to you.
Mailbox 10042’s Extension field contains the tokens that send technical
report #2.
Extension Field: @P(G1)>('C:/FAX/TECH2')G(1005)
DND: OFF
Store Messages: NO
Greeting 1: The technical report on service plans will be faxed to
you.
Mailbox 10043’s Extension field contains the tokens that send technical
report #3.
Extension Field: @P(G1)>('C:/FAX/TECH3')G(1005)
DND: OFF
Store Messages: NO
Greeting 1: The technical report on upgrading voice boards will be
faxed to you.
262 Installing Amanda@Work.Group
Mailbox 1005 allows the caller to select another document to be faxed or to
end the call (Menu 2 goes to 999). You might prefer to have Menu 2 return to
the caller instructions mailbox 991.
Extension Field: blank
DND: ON
Store Messages: NO
Greeting 1: To request an additional document, press 1; to exit,
press 2.
Menu 1: 1004
Menu 2: 999
NOTE:All the quotation marks in these token examples are single
quotation marks (although double quotation marks can be
used). Forward slashes are used (although double backward
slashes \\ can also be used with this token).
IVR and Voice Form Applications
This section provides guidelines for writing effective IVR (Interactive Voice
Response) and voice form applications. It also provides examples of how to
use Amanda’s menus, greetings, and messages as well as the Q(), M(), R(),
and P() commands from Amanda’s Token Programming Language.
Before you start, determine whether your application will be used by
infrequent users, expert users, or both.
You might need to design a training mode (which explains the choices—
perhaps using a different voice for the explanations) and an expert mode
(which offers minimal explanation).
Consider using short-cut options that allow expert users to access
information more quickly.
Also think about the average user’s vocabulary and familiarity with similar
systems as well as the type of telephone he will use and the location from
which he will probably call. For example, don’t use technical terms with
non-technical users. If you expect users to call from pay telephones, the
noise around them might make voice response a poor choice.
Chapter 16: Programming Examples 263
Making the User Comfortable
To make users feel that they are in control of the application rather than at
the mercy of it, the greetings should perform the following tasks in order:
1. Identify the company or service so that the user can determine whether
he has placed his call correctly.
2. Identify the application as non-human so that the user does not expect
human interaction.
For example, avoid personal pronouns in phrases. Use “Please enter the
number” rather than “tell me the number.”
3. If necessary, separate callers using touch-tone telephones from those
using dial-pulse telephones.
Use something similar to “If you are calling from a touch-tone phone,
please press 1 now. Otherwise, please remain on the line. An attendant
will help you.”
4. Early on the first menu, offer the user access to a human attendant.
5. Offer access to a human attendant and call termination on each menu
level.
6. Customize the greetings for the user.
For example, if the user has only three of the five services you offer,
never offer him the option of adding the services that he already has or
the option of canceling the services that he does not have.
Using Greetings
The greetings used in your application will fall into the following categories:
• Menus that list options from which the users make selections
• Requests for responses
• Informational—providing answers to users’ requests or other user
feedback
264 Installing Amanda@Work.Group
Using Menus
As you create your menus, do the following:
• Find logical topics for menus
• Offer topics in order: most likely to be selected to least likely. Make
an exception to this rule when the topic itself contains a number.
For example, use “To order the Series 3, press 3” rather than “To order
the Series 3, press 1”—even when your most popular sales item is Series
3.
• Limit the number of options on each menu. If a menu contains more
than eight options (including reaching an attendant, returning to pre-
vious menu, and exiting), break this menu into submenus.
Word your menus carefully using the following suggestions:
• State the result before the action.
For example, use “For Accounts Payable, press 1” rather than “Press 1
for Accounts Payable.”
• Be consistent from option to option and menu to menu.
For example, use “Please make your selection now” on each menu level
to indicate that all the menu options have been offered.
• Use “Press” for a single-digit response or “Enter” for multi-digit re-
sponse.
• Say the number on a key rather than a letter on that key—even if the
letter is more significant.
For example, say “Press 3” rather than “Press F.”
Making Requests
Requests to users fall into the following categories:
• Request for single-digit response (such as 1 for Yes or 2 for No)
• Request for multi-digit response such as a telephone or credit card
number
• Group of questions that comprise a voice form
For example, you might ask the user a series of questions, the answers to
which are essentially the fields on a paper form. These voice responses
are saved as messages.
Chapter 16: Programming Examples 265
For single-digit responses, you can use a greeting as a menu.
For multi-digit responses, you can use the R() command to convert the
DTMF tones to an ASCII number.
For voice forms, you can use the Q() command to save the responses for up
to 20 questions as a message.
Word your requests carefully using the following suggestions:
• Use consistent wording.
For example, use “Please” to indicate that a request is coming.
• Make it clear what type of input is expected from the user (keypad
input or voice response).
For example, use “At the tone, please say your last name” or “On your
touch-tone phone, please enter the letters of your last name.”
• Use “Press” for single choice, “Enter” for data, and “Say” for voice
response.
For voice response, end the request with “now” or start it with “At
the tone, please say…”—whichever is appropriate.
Providing Information and Feedback
Be sure to provide some type of feedback for every user action and allow
users to reverse unintended operations. For example, you can:
• Repeat the data provided by the user.
For example, you can use the P() command to play the telephone num-
ber stored by the R() command or use the Q() command to give the
caller the opportunity to edit (review, rerecord, append, or cancel)
answers to questions on a voice form.
• Request confirmation.
• Play a greeting that indicates that the application has moved on to
the next step.
266 Installing Amanda@Work.Group
• Repeat the current greeting when there is no response. If there is still
no response, provide a message explaining what is happening and ei-
ther connect the call to an attendant or disconnect it.
• Play an error message, status message, or tone.
Status messages, such has “We are still processing your order” should
play after the first two seconds and then every seven to ten seconds.
For an error message, provide a retry greeting (and perhaps suggest a
remedy) before repeating the current greeting. Be sure to notify the user
when returning to the main menu or transferring the user to an attendant
after an error.
Word your informational greetings carefully using the following
suggestions:
• Don’t say Standard Time unless you do not shift to Daylight Savings
Time.
For example, on the west coast, say “Pacific Time.”
• Be brief. When that is impossible, allow the user to listen to the
greeting again.
• When providing a telephone number, always repeat it.
• Eliminate unnecessary words.
For example, use “Please press 1 ‘Yes’ or 2 for ‘No’” rather than “Please
press the key with the 1 on it for ‘Yes’ or the key with the 2 on it for
‘No’.”
• When pairing opposite phrases, use words that sound differently.
For example, avoid pairing Turn On and Turn Off because they sound so
much alike.
• Don’t use open-ended or ambiguous questions.
For example, use “Do you have your account number?” rather than
“Have your account number ready.”
• Be polite, non-judgmental, and avoid humor.
For example, use “That password is invalid” rather than “You entered
the password incorrectly.”
Chapter 16: Programming Examples 267
Using the Telephone Keypad
If the users enter their choices via the telephone keypad, follow these
guidelines:
• Assign keys consistently. This is especially true for Delete and other
destructive options.
For example, don’t use 3 for Delete on one menu and Save on another.
• Offer alternates to * and # keys because those keys might be dis-
abled.
• Use keys 1 and 2 for the most frequently selected options. Users ex-
pect to use the 1 and 2 keys most often.
• Avoid using keys 1, 2, 5, and 8 as destructive options.
You might want to avoid 5 and 8 entirely as they are the most error-
prone key choices. (These two keys are the only ones with a key in each
direction.)
• Use the rows and columns of the keypad effectively.
• Use the left column for actions that precede or are lower than others.
• Use the right column for actions that follow or are higher than oth-
ers.
For example use a number in the left column to lower a volume and the
corresponding number in the right column to incrmase a volume.
• Consider using a key in the top row as a response to a greeting that
says “Go to the top” and a key in the bottom row in response to “Go
to the bottom.”
268 Installing Amanda@Work.Group
Choosing Tokens
A number of commands from the Token Programming Language make IVR
easier and voice forms possible.
To present a menu for your caller, you can use:
• The menu fields associated with the mailbox. The mailbox allows
the caller to enter either a one-digit response to the menu or another
mailbox. Amanda waits long enough to be sure that the caller has fin-
ished. (For this method, turn Do Not Disturb ON.)
• The M() command. In this case, Amanda waits for only one digit. It
is faster that using menu fields, but it does not allow the caller to en-
ter a mailbox with more than one digit. (For this method, turn Do Not
Disturb OFF.)
To convert the DTMF (or touch) tones entered by the caller into a number,
use:
• The R() command, which stores a number in a variable.
To play a greeting or play back the number stored by the R() command, use:
• The P() command. This command has many variations. See the “To-
ken Reference” on page 194 for details.
To play up to 20 questions (from greetings) and store the answers as a single
message, use:
• The Q() command, which also allows the caller to edit the responses.
Using Tokens
This example describes parts of an application that records consumer
reactions to sample products. For example, hair stylists may be mailed
information about a line of new hair care products.
If interested, a stylist can call an 800 number to request a sample of one of
them. The sample is mailed along with product literature and a test ID that
uniquely identifies the stylist with the product.
Chapter 16: Programming Examples 269
After using the product, the stylist calls again to answer a series of questions.
For services rendered, the stylist is mailed a small fee or a free case of the
product.
Later, the survey company analyzes the data and reports back to the
manufacturer. The application has two parts:
• Gathering information about a potential tester, such as name, ad-
dress, telephone number, and the product to be sent
• Quizzing the testers about the product
The tester information part (explained in “Gathering Testing Information” on
page 270) uses:
• Menus using the M() command and 0 to reach a live attendant at any
time.
• The P() command to play a general greeting.
• The R() command to request a telephone number, convert the DTMF
tones entered by the stylist, and store the telephone number in a vari-
able.
• The |() command (that’s the pipe command or vertical bar com-
mand) to add data about the stylist to a database file.
• A series of greetings that ask for the parts of an address. The Q()
command plays the greetings and allows the stylist to edit the re-
sponses before they are saved as a message.
The quiz part (not explained) uses:
• Menus using the M() command, using 0 to reach a live attendant at
any time.
• The R() command to request the test ID, convert the DTMF tones
entered by the stylist, and store the ID in a variable.
• The N() command to look up the test ID in a database file. The da-
tabase determines what set of questions to ask the stylist. It also con-
tains a field indicating how many calls have come in using this test
ID. Only one call should come in for each ID. If a stylist never calls
in, an employee can call that person. If a stylist calls more than once
(hoping for extra free cases of the product or whatever), an employ-
ee talks to the stylist personally, assuming some error has occurred.
• The Q() command to play a series of questions (greetings), allows
the stylist to edit the responses, and stores the set of responses as a
message.
270 Installing Amanda@Work.Group
Gathering Testing Information
Mailbox 880 handles all calls coming in on the 800 number and immediately
passes the call to the caller instructions mailbox 881 (via the Done Chain).
Mailbox 881 has:
Extension Field: @M(G1,2,30)G(0)
Amanda plays the menu in Greeting 1. If there is no re-
sponse from the caller, Amanda plays Greeting 1 again
after a three-second pause. If there is still no response,
Amanda executes the next token in the Extension field
(which goes to the operator).
DND: OFF
Store Messages: NO
Greeting 1: To become one of our testers, press 1. If you are al-
ready one of our testers and you want to answer a prod-
uct questionnaire, press 2….
Menu 1: 1000
Menu 2: 2000
Menu 0: 0
Mailbox 1000 has:
Extension Field: @P(G1)Q(G2,G3,G4,G5,G6,G7,
G1#1001,E)R(G2#1001,%S1,30)G(1001)
Amanda plays Greeting 1 from mailbox 1000 to wel-
come the tester and to give an overview of the process.
Then Amanda asks for the stylist’s mailing address us-
ing a series of greetings and recording the answers as
one message.
Next Amanda asks for a telephone number and stores
it as a variable (%S1).
(It would be a good idea to play this number back to the
stylist and allow reentry, but this example does not do
that. See how this is done in “Two-call Faxback” on
page 259.)
Finally, the call is transferred to mailbox 1001.
DND: OFF
Store Messages: YES
Chapter 16: Programming Examples 271
Greeting 1: Welcome to….
Greeting 2: Please say your last name now.
Greeting 3: Please say your first name and middle
initial now.
Greeting 4: Please say the name of your business
now.
Greeting 5: Please say your street address now.
Greeting 6: Please say your zip code now.
Greeting 7: Please say the name of your city now.
Greeting 1 of mailbox 1001: Please say the name of your state now.
Greeting 2 of mailbox 1001: Please use your telephone keypad to en-
ter a daytime telephone number where
we can reach you if necessary. Please
start now.
Mailbox 1001 has:
Extension Field: @=(%S2,%M(1000))M(G3,2,30)G(0)
%M[1000] is the number of messages stored in mail-
box 1000. Amanda stores this number in a variable
(%S2). This message number becomes associated with
the stylist for the duration of the survey.
Then Amanda plays the menu in Greeting 3. If there is
no response from the caller, Amanda plays Greeting 3
again after a three-second pause. If there is still no re-
sponse, Amanda executes the next token in the Exten-
sion field (which goes to the operator).
NOTE:Using the message number to uniquely identify
the tester works only because no messages will be
deleted from mailbox 1000 until after the survey.
If you will have more messages than disk space,
keep a number in another file. Read the number
using the [() command, increment it by one with
the +() command, and write the new number (for
the next tester) back to the file using the ]() com-
mand.
DND: OFF
Store Messages: NO
272 Installing Amanda@Work.Group
Greeting 3: Please select one of the following products….
Menu 1: 1002
Menu 2: 1003
… other menu options …
Menu 0: 0
Mailboxes 1002, 1003, … have:
Extension Field: @=(%S3,%S2)+(10000,%S3)
|(C:\\TESTERS\\TESTX.TXT)P(G1)G(999)
Next Amanda makes a copy (%S3) of the message
number (which identifies the stylist) and adds 10000
(or some other product differentiating number) to it.
This becomes the test ID.
Then Amanda appends the stylist’s telephone number
(%S1), message number (%S2), and product number
(%S3) to a database file (C:\TESTERS\TESTX.TXT).
Finally, Amanda plays Greeting 1 from the current
mailbox and hangs up. (It would be a good idea to have
the user verify that the stylist did indeed want this
product or return to mailbox 1001, but this example
does not do that. You would play a greeting naming the
product and ask the stylist to confirm, similar to recon-
firming the telephone number in Example 4.)
DND: OFF
Store Messages: NO
Greeting 3: Thank you for agreeing to test product such-and-such.
You will be receiving…within 10 days. Please try the
product and call this system again to answer a few
questions about it….
Chapter 17:
Installing the Clients
Installing from Various Platforms
Now that the Amanda Voice Server is up and running properly, you may
enable each workstation to access Amanda@Work.Group/DOS by loading
the Amanda Clients.
You can install the Amanda Clients by going from desk to desk with the
installation disks, or you can copy the software onto a network file server
and then install it on each workstation from the file server.
There are two client installation disks. One contains the installation files for
the user clients: Amanda Messenger, Amanda Dialer, and Amanda Fax. For
more information about these clients, see Amanda@Work.Group/DOS
Workstation Features.
The other installation disk contains the installation files for the administrator
clients: Amanda Administrator and Amanda Monitor. For more information
about these clients, see Administering Amanda@Work.Group/DOS.
NOTE:The Amanda Company recommends that you install only
the User client programs onto the network file server. As an
extra level of security, the Administration client programs
should be installed only from the installation disk to autho-
rized system administration personnel.
176 Installing Amanda@Work.Group/DOS
Installing from a File Server
To copy the users’ client files to the file server:
1. Insert the Amanda@Work.Group/DOS Users disk into the floppy drive.
2. Create a directory to store these files on the network drive using File
Manager or Windows Explorer.
3. Copy the contents of the floppy drive to that directory.
You may need to contact your network system administrator for assis-
tance.
To install the users’ client files from the file server:
1. If any previously installed Amanda Clients are running, close them.
2. Access the network drive.
3. Open the directory where the clients are stored.
4. Double-click SETUP.EXE.
5. Follow the directions on the screen.
Installing from a Floppy Drive on Windows 3.11
To install either user or administrator clients:
1. If any previously installed Amanda Clients are running, close them.
2. Insert the appropriate Amanda@Work.Group/DOS installation disk into
the floppy drive.
3. From the Program Manager, select File and then Run.
4. At the Command Line, type A:SETUP then click OK.
Chapter 17: Installing the Clients 177
5. Follow the directions given by the setup program to finish the installa-
tion process.
Unless modified by the installer, the directory C:\AMACLNTS stores
the clients.
After the installation, an Amanda icon appears in Program Manager.
The Amanda group displays all the clients installed on this workstation.
Installing from a Floppy Drive on Windows 95
To install either user or administrator clients:
1. If any previously installed Amanda Clients are running, close them.
2. Insert the appropriate Amanda@Work.Group/DOS installation disk into
the floppy drive.
3. Select the Start button and then select Run.
4. At the Command Line, type A:SETUP then click OK.
5. Follow the directions given by the setup program to finish the installa-
tion process.
Unless modified by the installer, the directory C:\AMACLNTS contains
the clients.
The Amanda group of clients appears in the Programs section of the
Start menu. The Amanda group contains all the clients installed on this
workstation.
178 Installing Amanda@Work.Group/DOS
Adding Client Connections
Now that users have the Amanda@Work.Group/DOS clients, you must add
the appropriate number of Client Connections to the Amanda Voice Server.
Only one client connection comes with Amanda Voice Server. If you add no
client connections, only one client can access the voice server at a time.
Adding client connections requires a Client Connection Bank (CCB) with at
least as many connections as you wish to install at this site.
432
To Printer Port
CCB
Modem
Voice Board
VGA Card
COM1
COM2
Chapter 17: Installing the Clients 179
To add client connections:
1. If Amanda is running, shut down the Amanda system and turn the
computer off.
a. Press Alt+S (if Amanda is running as a standalone) or s (if
Amanda is running as a voice server).
b. Type in the password. (The default is AMandA with only the
first two and the last letter capitalized.)
c. Press Enter.
d. Press Y (to confirm the shutdown).
e. Press Y again (to reconfirm).
f. When you reach the DOS prompt C:\AMANDA>, turn the com-
puter off.
2. Next, attach the CCB to the parallel port on the back of Amanda Voice
Server.
The CCB contains a number of Client Connections, some (or all) of
which can be transferred to this Voice Server.
3. Turn Amanda Voice Server on.
During the start up process, the system asks:
Do you want to run Amanda@Work.Group/DOS? Press Y or N
4. Press Y for Yes.
Amanda detects the CCB and asks for the number of connections to be
added to this Voice Server.
5. Enter the requested number and follow the prompts to turn off the com-
puter and remove the CCB.
6. After removing the CCB, turn Amanda Voice Server back on.
7. During the start up process, the system asks:
Do you want to run Amanda@Work.Group/DOS? Press Y or N
180 Installing Amanda@Work.Group/DOS
8. Press Y for Yes.
9. This brings Amanda Voice Server and the appropriate number of client
connections online.
Reviewing Client Connections
Each time a user logs onto Amanda Messenger or Amanda Dialer, or the
system administrator logs onto Amanda Administrator or Monitor, he
acquires a client connection. When he logs off, the client connection is
returned to the pool and is available for the next person who logs on. As
more users are added to Amanda, some users may not be able to log on
because all client connections are in use.
To display the maximum number of clients Amanda is configured for:
1. Run Amanda Monitor.
2. On the File menu, click Copy….
The Copy dialog box appears.
Chapter 17: Installing the Clients 181
3. Type C:\AMANDA\INSTALL.CFG.
4. Select the Voice Server option button to indicate the location of the file.
5. Indicate the name and location of the file to be created.
If the file is on your workstation (or network), you can click Browse…
to locate the file.
6. Select the Local option button to indicate the location of the new file.
7. Click Copy.
If the file already exists, the Confirm File Replace dialog box appears.
8. Do one of the following:
• To replace the existing file, click Yes.
• To preserve the existing file, click No and type a unique name for
your file in the Copy dialog box.
9. When “File copy completed” appears at the bottom of the Copy dialog
box, click Cancel.
10. View the file using a text editor.
The value for n_clients is the maximum number of clients the Amanda
server currently accepts. Do not edit this value and recopy install.cfg to
the voice server. Changing this value will corrupt the file.
182 Installing Amanda@Work.Group/DOS
Chapter 18:
Configuration Reference
General Options
Configuration Option Description
abbreviate_dates Controls how Amanda says the date for a message dated today or yesterday.
True or False. The default is True.
When True, Amanda says “today” or “yesterday” instead of the actual date, for ex-
ample, “November 27th , 1996.”
When False, Amanda says only the actual date, such as “November 27th , 1996.”
The default appears in install.cfg as:
set abbreviate_dates true
abbreviate_greeting Allows you to shorten the system greeting.
True or False. The default is False.
When True, Amanda says, “Please leave a message at the tone.” This is the short-
ened version of the system greeting.
When False, Amanda says, “Please leave a message for” followed by the name and
extension recording. This is the usual default version of the system greeting.
The default appears in install.cfg as:
set abbreviate_greeting false
activation_key A number you receive from your Amanda Company sales representative to activate
your system. You must set this option if one or more of your voice boards were not
purchased from The Amanda Company.
If you change or add a board later, you need another activation key because the key
is based on the serial numbers for all of the boards and the total number of ports.
The default is 0, which means there is no activation key.
The default appears in install.cfg as:
set activation_key 0
184 Installing Amanda@Work.Group/DOS
active_hold When the extension is busy, the caller can hold for the called party—actively or in-
actively.
True or False. The default is True.
When True, Amanda is set up for active hold. The caller must continually indicate
that he wants to remain on hold. Failure to continue to press * when prompted indi-
cates that the caller is no longer interested in holding. If he doesn’t enter another ex-
tension, he is asked for a message. Active hold is best for 800 numbers, support
lines, or when Amanda is used as an Automatic Call Distribution (ACD) device. It
prevents a caller from pressing * to go on hold and staying on hold indefinitely with-
out further interaction. The caller presses * to go on hold and must press * periodi-
cally to stay on hold.
When False, Amanda is set up for inactive hold. The caller indicates that he wants
to be on hold only once. If the caller does nothing, Amanda retries the extension
until it is no longer busy. The caller can also enter another extension or press * to
leave a message. In this case, the user uses * to go on hold and * to leave a message.
See also auto_queue.
The default appears in install.cfg as:
set active_hold true
adpcm_hq Sets the sampling rate for outgoing greetings. The higher the sampling rate, the bet-
ter the sound quality, but also the more disk space used.
24, 32, or 64. The default (and recommended value) is 64.
NOTE:If you change this on an active system, all previously recorded outgoing
greetings need to be re-recorded.
The default appears in install.cfg as:
set adpcm_hq 64
adpcm_nq Sets the sampling rate for incoming messages. The higher the sampling rate, the bet-
ter the sound quality, but also the more disk space used.
24, 32, or 64. The default (and recommended value) is 32.
NOTE: If you change this on an active system, you should have users delete all
their messages first.
The default appears in install.cfg as:
set adpcm_nq 32
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 185
adpcm_pq Sets the sampling rate for the system prompt file. This is set to the sampling rate at
which the system prompt file was recorded.
24, 32, or 64. Correctly set by default.
NOTE:Do not change this unless you have installed the appropriate system prompt
file.
The default appears in install.cfg as:
set adpcm_pq x
where x is the correct setting for your prompt files.
advertising Displays a text string at different locations on the Main screen after the screen saver
starts up. (This option does not apply to Amanda voice server.)
Use any text string ranging from 0 to 79 characters. The recommended length is less
than 30 characters so your message is easy to read and fits on the screen at most lo-
cations. 'Buy more AMandAs!' is the default.
See also tmo_blank.
The default appears in install.cfg as:
set advertising 'Buy more Amandas!'
ati_mode Allows Amanda to be used with a Brooktrout x000 board and an ATI board. An ATI
board requires a version 7.x Brooktrout driver.
True or False. The default is false.
When True, Amanda makes the connections needed for the ATI board.
When False, Amanda does not make the ATI connections.
The default appears in install.cfg as:
set ati_mode false
CAUTION:RTNI-xATI voice boards cannot detect rotary. If you use an RTNI-
xATI voice board, you must leave the rotary configuration option set to
false.
General Options (Continued)
Configuration Option Description
186 Installing Amanda@Work.Group/DOS
auto_queue Designed for callers with rotary telephones so that they can be put “on hold” without
having to press *.
True or False. The default is False.
If True and if active_hold is False, callers are automatically put “on hold” when they
reach a busy extension. A custom busy message must explain what’s going on so
that callers are aware that they are “on hold” and that they can dial other exten-
sions—if they prefer.
The default appears in install.cfg as:
set auto_queue false
auto_report The name of a previously saved report file in the RPT.DB subdirectory within the
AMANDA directory which can be executed and printed once each day. When not
set, no auto reporting is done.
Use the name of a report file with the extension .RPT. The default is an empty string
which means that no report file is executed.
To use this feature, verify the following:
• A printer with a parallel interface must be connected to Amanda
• The parameter lpt_port must be set to 1, indicating the port to
which the printer is attached
• The printer must be online and have enough paper
See also auto_report_time and lpt_port.
The default appears in install.cfg as:
set auto_report ''
auto_report_time The time of day at which the report is to be printed (when auto_report is not an emp-
ty string).
A time of day in 24-hour MMHH format. The default is 0745 (7:45 a.m.).
See also auto_report and lpt_port.
The default appears in install.cfg as:
set auto_report_time 0745
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 187
begin_rec_prompt When record_menu is True, this option controls whether the caller hears Amanda
prompts or only a beep when recording a message. This option has no effect on the
post-record menu. If the caller presses #, the post-record menu indicates how to re-
record, append to, or save a recording.
True or False. The default is True.
When True, Amanda plays, “Begin recording at the tone, finish by pressing # or
hanging up” before the beep.
When False, the caller hears only a beep.
See also record_menu and end_rec_menu.
The default appears in install.cfg as:
set begin_rec_prompt true
busycycles Minimum number of non-ringback cycles necessary before the Brooktrout driver
notifies Amanda that the extension is busy.
The default is 2 cycles. The range is 0 to 20. 0 means do not change the current
Brooktrout setting (which is also 2 cycles).
The default appears in install.cfg as:
set busycycles 2
ca_file The file (in the C:\AMANDA directory) which stores call accounting (SMDR) data
that comes from the port in ca_port. The data is collected from the telephone switch-
ing system, stored while Amanda runs, and then (after a shutdown) read by a call
accounting package that analyzes and manipulates the data.
Use any filename. The default is 'SMDR.DAT'.
See also ca_port.
The default appears in install.cfg as:
set ca_file 'SMDR.DAT'
ca_port The number for the logical serial port that will read SMDR data from the switch
while Amanda is running. The data is stored in the file specified by ca_file unless
the number is 0, in which case no SMDR data is read.
Use 0, 1, 2, 3, or 4. The default is 0.
See also ca_file.
The default appears in install.cfg as:
set ca_port 0
General Options (Continued)
Configuration Option Description
188 Installing Amanda@Work.Group/DOS
cancel_busy_hold Determines whether callers can hold for a busy extension.
True or False. The default is False.
When True, busy becomes equivalent to Ring No Answer (RNA). That means that
the caller cannot hold for a busy extension and can only leave a message once RNA
or BUSY is the state of the called extension (assuming the mailbox accepts messag-
es).
When False, the caller can press * to hold for a busy extension.
The default appears in install.cfg as:
set cancel_busy_hold false
clock_sync Controls whether Amanda resynchronizes the DOS software clock with the PC
hardware clock.
True or False. The default is True.
When True, Amanda resynchronizes.
When False, Amanda does not resynchronize. Turn this off if you have another util-
ity that controls the PC clock.
The default appears in install.cfg as:
set clock_sync true
cmt_maxlen Sets the total number of seconds allowed for recording a List Comment. The user
can record a comment while creating a mailing list or later. It names or describes the
contents of the list.
Number of seconds. The range is from 1 to 99. The default is 10.
The default appears in install.cfg as:
set cmt_maxlen 10
connect_tone When an answer is detected and Amanda is not identifying the called party for the
current mailbox, this option determines whether Amanda plays a beep. (On the Stan-
dalone system, the mailbox’s ID Call? field is set to NO, and on the Administrator
client, the mailbox’s Identify Called Party check box is cleared.)
True or False. The default is True.
When True, Amanda plays the beep.
When False, there is no beep.
The default appears in install.cfg as:
set connect_tone true
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 189
create_locked Controls whether or not new mailboxes are locked when the mailbox template (usu-
ally mailbox 997) is locked. The administrator (using mailbox 999 and the tele-
phone) can lock the template (and other mailboxes) using one of the system
administration options. This prevents callers from logging into the mailbox tem-
plate.
True or False. The default is False.
When True, new mailboxes created from the template are initially locked if the tem-
plate is locked.
When False, new mailboxes are not locked. This means that they can be logged into
via the telephone immediately after they are created.
The default appears in install.cfg as:
set create_locked false
db_locking Makes Amanda lock each record in a file as it is accessed. No other port or program
can access that record of that file. This is used within the context of using tokens to
read and write to ASCII or dBase files.
The value is 0 or 1. The default is 0.
When 0, Amanda does not perform record locking.
When 1, Amanda attempts to perform record locking which will fail unless
SHARE.EXE, a DOS program (not licensed via The Amanda Company), is running.
This program is usually loaded by the CONFIG.SYS or AUTOEXEC.BAT file.
The default appears in install.cfg as:
set db_locking 0
defaults_box Indicates what mailbox to use as a template when creating a new mailbox. The con-
tents of most fields, all notification records, and all automatic scheduling records are
copied from the template to the new mailbox. The Comment and Directory Name
fields are not copied. The Extension field is copied only if it begins with an @
(which indicates token programming).
If the Security Code field of the default mailbox is blank, the security codes for new
mailboxes are their mailbox numbers. Otherwise, the security codes for all new
mailboxes are the same as that of the template mailbox. The Security Code field al-
ways appears blank. You must fill it with spaces if you want it to actually be blank.
Use any valid mailbox. The default is 997.
See also guest_defaults.
The default appears in install.cfg as:
set defaults_box 997
General Options (Continued)
Configuration Option Description
190 Installing Amanda@Work.Group/DOS
diskwarn When Amanda has only the specified percentage of disk space left, she executes
Disk notification record (if there is one) for mailbox 999. The notification record
may call you at home, call your extension, call your pager, and so forth. For exam-
ple, use 20 to have Amanda notify you when the remaining disk space falls below
20.
Number (for a percentage). The range is from 1 to 99. The default is 20.
See also tmo_disk.
The default appears in install.cfg as:
set diskwarn 20
dl_pickup_on_ring When an inbound ring is detected and Amanda goes off-hook, this option deter-
mines whether Amanda dials the code specified by the dl_pickup parameter in the
1001.PBX file or the current dial codes file for that port.
True or False. The default is False.
When True, Amanda dials the code.
When False, Amanda does not dial the code.
The default appears in install.cfg as:
set dl_pickup_on_ring false
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 191
dtmf_action
dtmf_busy
dtmf_dnd
dtmf_ring
dtmf_xfer
tmo_xfer
The dtmf_action, dtmf_busy, dtmf_dnd, dtmf_ring, dtmf_xfer, and
tmo_xfer, parameters are required only for telephone switching systems,
such as Comdial DXP and Panasonic KXT-D, that can send DTMF tones in
place of PCPM tones.
For Comdial DXP, The Amanda Company recommends dtmf_action=1,
dtmf_busy='2', dtmf_dnd='3', and dtmf_xfer='1'. (It sends nothing for a
ring—dtmf_ring=''.) tmo_xfer=50 and tmo_rna=25 have been recommend-
ed.
For Panasonic KXT-D, The Amanda Company recommends
dtmf_action=1, dtmf_ring='1', dtmf_busy='2', dtmf_dnd='4', dtmf_xfer='5',
and tmo_xfer=20.
tmo_xfer is the number of tenths of seconds that Amanda waits to read a
sequence of DTMF digits from the port prior to doing PCPM. The range is
0 to 255. The default is 0, which disables this and the following parameters.
(If this parameter is blank, the default is used.)
If the tmo_xfer timeout is greater than 0, Amanda waits for digits until the
timeout occurs.
The digits the system might read are:
dtmf_xfer This sequence of digits means that the extension has been
answered. Amanda releases the call. The default is an emp-
ty string (no digit).
NOTE:The telephone switching system should
bring the call back to the port if this digit
is sent when the phone is ringing rather
than actually answered.
CAUTION:When using call screening, be aware that
this will play the caller's name and compa-
ny as well as the call screening menu to a
ringing tone.
dtmf_dnd This sequence of digits means that the extension is in Do
Not Disturb mode. Amanda treats the call as though it were
not answered (RNA). The default is an empty string (no
digit).
dtmf_busy This sequence of digits means that the extension is busy so
Amanda performs no PCPM. The default is an empty
General Options (Continued)
Configuration Option Description
192 Installing Amanda@Work.Group/DOS
(cont.)
dtmf_action
dtmf_busy
dtmf_dnd
dtmf_ring
dtmf_xfer
tmo_xfer
dtmf_ring This sequence of digits causes Amanda to stop waiting or
to extend her wait, depending on the value of dtmf_action.
The default is an empty string (no digit).
no digit If Amanda reads no sequence of digits before the tmo_xfer
timeout occurs, the system stops waiting or extends her
wait, depending on the value of dtmf_action.
The dtmf_action parameter determines what Amanda does if the system re-
ceives the digits specified in dtmf_ring or if the timeout specified by
tmo_xfer occurs before the digits arrive.
When 0 (the default), Amanda performs normal PCPM.
When 1, Amanda continues to wait for the digits. The system waits 6 sec-
onds for each of the rings specified for a Ring No Answer (RNA). For ex-
ample, if the mailbox has 4 rings for RNA, Amanda waits 24 seconds. Then
the system decides that the call is not answered.
For COMDIAL, see also dtmf_dt.
The defaults appear in install.cfg as:
set dtmf_action 0
set dtmf_busy ''
set dtmf_dnd ''
set dtmf_ring ''
set dtmf_xfer ''
set tmo_xfer 10
dtmf_before_ring Controls whether Amanda clears the voice board’s DTMF buffer when a ring is de-
tected. Clearing the buffer gets rid of digits left over from a previous call.
True or False. The default is False.
When True, the buffer is not cleared. Make sure the telephone switching system can
send DTMF before a ring prior to changing this to True.
When False, Amanda clears the buffer when a ring is detected. You must use False
for Brooktrout 2132 and 4132 because they cannot detect DTMF while on-hook.
The default appears in install.cfg as:
set dtmf_before_ring false
dtmf_busy This option is required only for telephone switching systems, such as Comdial DXP
and Panasonic KXT-D, that can send DTMF tones in place of PCPM tones. See also
dtmf_action.
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 193
dtmf_dnd This option is required only for telephone switching systems, such as Comdial DXP
and Panasonic KXT-D, that can send DTMF tones in place of PCPM tones. See also
dtmf_action.
dtmf_detect How long a DTMF tone must play for Amanda to recognize that it has occurred.
Number from 2 to 6, each representing 16 ms. (For example, 3 equals 48 ms or .048
seconds.) The default is 0.
Zero means to use the default. The default is 3 (.048 seconds).
When non-zero, both Brooktrout’s DTMFDetect and DTMFDelay channel parame-
ters are set to that value.
The default appears in install.cfg as:
set dtmf_detect 0
dtmf_dly Controls the amount of time between DTMF tones when Amanda is dialing.
Number of hundredths of seconds. The value is 0 or a number from 3 to 19. The de-
fault is 10 (which is 100 milliseconds).
Using a value of 0 makes it country-dependent (50ms in the US, 80ms in the UK).
When non-zero, the specified time is used.
The default appears in install.cfg as:
set dtmf_dly 10
dtmf_dt The string of DTMF digits received instead of a dial tone. For example, COMDIAL
sends a '1'.
The string can be any length. The default is an empty string which means that Aman-
da waits for the dial tone.
If dtmf_dt is not an empty string, and if tmo_dtwait (the dial code that determines
how long to wait for a dial tone or its equivalent) is > 0, Amanda dials dl_dtwait (the
dial code that puts the caller on transfer hold) and then waits for the dtmf_dt digits
to come from the switch.
If Amanda receives fewer digits or if the digits do not match dtmf_dt, Amanda as-
sumes the extension is busy. If Amanda receives the expected digits, she proceeds
with the call. As soon as Amanda receives the correct number of digits, she stops
waiting regardless of the value of tmo_dtwait. Therefore, it should be safe to make
tmo_dtwait substantially larger than the actual time expected.
The default appears in install.cfg as:
set dtmf_dt ''
General Options (Continued)
Configuration Option Description
194 Installing Amanda@Work.Group/DOS
dtmf_gate Verifies that the caller is still on the line before transferring him to the operator. This
applies only if the mailbox (usually the operator) specified in the Done Chain for the
Caller Instructions mailbox has Do Not Disturb turned off.
True or False. The default is False.
When True, Amanda verifies that the caller is still on the line after playing the Caller
Instructions and not hearing any DTMF. Amanda asks the caller to “Say ‘yes’ at the
tone” before transferring the call. For example, on telephone switching systems that
do not have disconnect supervision, this can prevent the transfer of a call to the op-
erator or prevent the replaying of a menu when the caller has hung up.
When False, Amanda transfers the call without verifying that the caller is still on the
line.
The default appears in install.cfg as:
set dtmf_gate false
dtmf_on Controls how long Amanda plays each DTMF tone.
Number in hundredths of seconds. The range is from 10 to 90. The default is 20 (.2
seconds).
The default appears in install.cfg as:
set dtmf_on 20
dtmf_ring This option is required only for telephone switching systems, such as Comdial DXP
and Panasonic KXT-D, that can send DTMF tones in place of PCPM tones. See also
dtmf_action.
dtmf_xfer This option is required only for telephone switching systems, such as Comdial DXP
and Panasonic KXT-D, that can send DTMF tones in place of PCPM tones. See also
dtmf_action.
end_rec_menu When record_menu is True, this option determines whether the caller hears the post-
record menu that allows callers or users to review or re-record their messages or
greetings.
True or False. The default is True.
When True, the caller or user hears the menu.
When False, the caller or user does not hear the menu.
The default appears in install.cfg as:
set end_rec_menu true
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 195
exit_digit Defines one additional DTMF tone that causes Amanda to stop during recordings
(whether greetings or messages) and play the post-record menu.
The range is from 0 to 9 and also includes * and #. The default is '#'. Remember that
the # key always causes Amanda to stop recording, even when it is not the value of
exit_digit.
The default appears in install.cfg as:
set exit_digit '#'
exit_to_0 Allows a caller to leave a message and talk to the operator afterwards.
True or False. The default is True.
When True, the caller can press 0 after recording a message and is transferred to
mailbox 0.
When False, Amanda records the DTMF 0 as part of the message unless 0 is defined
as an exit digit (see exit_digit).
NOTE:Regardless of the setting for exit_to_0, a caller can press 0 during the “Be-
gin recording at the tone...” prompt and go to mailbox 0 immediately. If the
caller presses any other key (1-9, #, *), Amanda stops the prompt, plays the
beep, and starts recording the message.
The default appears in install.cfg as:
set exit_to_0 true
future_delivery Specifies the mailbox that stores messages to be delivered in the future. This mail-
box must be able to store messages.
The default is 995, but you can use any valid mailbox. -1 means no mailbox has been
assigned.
The default appears in install.cfg as:
set future_delivery 995
gain_loud Controls the volume of the custom busy message.
Number. The range is from -8 to 8 and the default is 0.
The default appears in install.cfg as:
set gain_loud 0
gain_norm The initial volume for all ports.
Number. The range is from -8 to 8 and the default is 0.
The default appears in install.cfg as:
set gain_norm 0
General Options (Continued)
Configuration Option Description
196 Installing Amanda@Work.Group/DOS
guest_defaults The mailbox to use as a template when creating a new guest mailbox.
The default is 996, but you can use any valid mailbox. -1 means no mailbox has been
assigned.
See also defaults_box which explains what fields are copied.
The default appears in install.cfg as:
set guest_defaults 996
guest_min The starting mailbox for guest mailboxes. If this value is 90000, the first guest mail-
box is 90000. The second is 90001, and so forth.
See also guest_max. Guest_max must be larger than guest_min.
Any valid mailbox. The default is 90000.
The default appears in install.cfg as:
set guest_min 90000
guest_max The last mailbox for guest mailboxes. If this value is 90199, the highest possible
number for a guest mailbox is 90199. Along with the guest_min, you limit the num-
ber of guest mailboxes that Amanda can create. Guest_max must be larger than
guest_min.
A valid mailbox. The default is 90199.
The default appears in install.cfg as:
set guest_max 90199
integration_greeting Determines what greeting plays for integrated calls that have both rrr and sss (or rrrr
and ssss) fields set. (The r’s indicate the number of digits in the extension of the user
who was called but did not answer. The s’s indicate the number of digits in the ex-
tension of the user who made the call. See “Using Character Codes” on page 82 for
more information.)
True or False. The default is True.
When True, Amanda plays the RNA greeting for the mailbox identified by rrr.
When False, Amanda plays the system greeting.
In either case, a message is taken for rrr from sss.
The default appears in install.cfg as:
set integration_greeting true
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 197
integration_term A one-character string containing the character that terminates DTMF input. The de-
fault is the empty string. When Amanda sees the character that matches
integration_term, she terminates the integration input.
This can be used to speed up slow systems. The terminating character is not removed
from the input, so be sure that your integration patterns include it or allow for it.
The default appears in install.cfg as:
set integration_term ''
irq The IRQ over which the voice board communicates with the Amanda system.
The default is 7. The range is 0-15, but do not change this setting unless instructed
to by an Amanda Company employee. Most IRQs are unavailable because they are
used by PC components.
The default appears in install.cfg as:
set irq 7
lcoff The minimum necessary duration of loop current off before the voice board driver
recognizes that the loop current is off. Corresponds to the Brooktrout global param-
eter LcOff.
Number of hundredths of seconds (from 1 to 6553) or the number -1 or 0. For exam-
ple 10 is .1 second. The default is -1.
When 0, the voice board’s default is used. The default is .1 seconds.
When -1, there is no wait.
The default appears in install.cfg as:
set lcoff -1
lcvalid The length of time that the voice board driver ignores loop current transition events
(on, off, and drop) after starting PCPM. Corresponds to the Brooktrout channel pa-
rameter LcValid.
Number of hundredths of seconds (from 1 to 255) or the number -1 or 0. For example
10 is .1 second. The default is 0.
When 0, the voice board’s default is used. The default is 4 seconds.
When -1, this option is disabled and no events are ignored.
The default appears in install.cfg as:
set lcvalid 0
General Options (Continued)
Configuration Option Description
198 Installing Amanda@Work.Group/DOS
lcwait The minimum time after dialing a digit string before the voice board driver decides
the loop current drop is an answer. Corresponds to the Brooktrout channel parameter
LcWait.
Number of hundredths of seconds (from 1 to 255) or the number -1 or 0. For example
10 is .1 second. The default is 0.
When 0, the voice board’s default is used. The default is 100 ms (.1 seconds).
When -1, this option is disabled and there is no minimum time.
The default appears in install.cfg as:
set lcwait 0
list_delay When a message is sent to a list, this is the delay between deliveries to mailboxes on
the list. It has no effect on direct messaging or future deliveries. Slowing down the
delivery rate makes sending to long lists less likely to slow down the system.
Number of tenths of a second. The default is 10 (which is 1 second). The range is 0
to 255.
The default appears in install.cfg as:
set list_delay 10
lognam The name of the file to be used as the system log file. It is stored in the C:\AMANDA
directory. This log file contains start-up information, any execution error informa-
tion, DOS errors, disk errors, system actions, and shutdown information.
The default filename is 'AMANDA.LOG'.
NOTE:Since this file grows (slowly), archive or delete it once or twice a year when
you perform preventative maintenance.
The default appears in install.cfg as:
set lognam 'AMANDA.LOG'
lpt_port Number of the printer port to which a printer is attached to Amanda.
The default is 0, which means that no printer is attached.
While a printer can be attached to LPT ports 1, 2, or 3, use 1 for best results and at-
tach the printer to LPT1.
If you use a non-zero value, but no printer is attached, Amanda halts.
See also auto_report and auto_report_time.
The default appears in install.cfg as:
set lpt_port 0
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 199
max_chain Controls the number of digits the caller can enter for a mailbox.
For example, if you have a three-digit extension plan, setting this parameter
to 3 allows Amanda to transfer to the mailbox immediately after three digits
have been dialed, instead of waiting for a timeout or the # terminator.
The default is 8, the largest number allowed in Amanda@Large.Office.
The default appears in install.cfg as:
set max_chain 8
max_dl_inits The number of ports that can go off-hook simultaneously and dial the telephone
switching system initialization code.
The range is from 1 to the number of ports defined for Amanda. The default is 2.
The PBX file option dl_init (What to dial on each port after the system starts) works
on the ports specified here.
The default appears in install.cfg as:
set max_dl_inits 2
max_ports Number of ports in use on the Amanda system. This option needs to be set when the
number of ports available is greater than the number of ports in use. For example, if
you have a four-port voice board but are currently using only three ports, set this op-
tion to 3 to ensure that Amanda does not try to use the fourth port.
The default is 24. The range is 1-24. If you are using all the ports that your voice
boards can support, it is OK to have a number here that is greater than the number
of ports you have.
The default appears in install.cfg as:
set max_ports 24
max_prompt The number of times Amanda repeats menu options before hanging up on a user who
is logged in to a mailbox.
Number from 1 to 9. The default is 2.
The default appears in install.cfg as:
set max_prompt 2
General Options (Continued)
Configuration Option Description
200 Installing Amanda@Work.Group/DOS
minmsg Amanda requires a minimum length for recorded messages. If a message is shorter
than this, it is not saved. The most common reason for changing this parameter is
when the Q() token is used and short answers are expected. If so, you should change
this to 1 (0.1 seconds.) Otherwise, using a setting that is small results in an increased
number of messages that contain only a hangup sound.
Number of tenths of seconds. The default is 10 (1 sec.).The range is 0 to 65535.
The default appears in install.cfg as:
set minmsg 10
minoff Minimum amount of time necessary for an inbound ring’s off period.
Number of tenths of seconds. The default is 5 (.5 second). The range is 1-655.
The default appears in install.cfg as:
set minoff 5
minring Minimum amount of time necessary for an inbound ring’s on period.
Number of tenths of seconds.
The default is 0 which tells Amanda to use the voice board's default (which is 2 for
Denmark or Holland and 3 elsewhere). Otherwise, the range is 1-655.
The default appears in install.cfg as:
set minring 0
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 201
modified_call_
screening When a mailbox has both call screening and called party identification on, this op-
tion controls whether Amanda announces only the name and extension of the called
party or both that and the name and company of the caller. This is usually used only
when more than one mailbox calls the same extension.
When call screening is on, Amanda plays the Call Screening menu when the tele-
phone is answered. Then the person who answers can accept some calls and reject
others based on the information that he hears. Amanda treats the rejected calls as
Ring No Answers.
Do not use Call Screening (modified or not) with a mailbox that performs unsuper-
vised (blind) transfers. These transfers have an H in the Extension field (for exam-
ple, 127H). When the call is unsupervised, no recording is played to the user.
True or False. The default is True.
When True, the person who answers hears the called party’s name and extension re-
cording. Amanda does not ask the caller for a “name and company.”
When False, the person who answers hears both the caller’s name and company and
the called party’s name and extension recording.
The following is an example where John (mailbox 111) and Mary (mailbox 112)
share Extension 100. John is at lunch, and Mary is answering all calls at Extension
100.
The caller enters 111 trying to reach John.
Amanda rings Extension 100 and Mary answers.
Amanda says, “This call is for John, Extension 111. To accept this call, press 1. To
reject this call press 2 and hang up….” Mary presses 2. The caller hears John’s cur-
rent greeting.
NOTE:If a user wants Amanda to announce only for the caller’s name and compa-
ny, ID Call? should be NO (on Amanda standalone) or the Identify Called
Party check box should be cleared (in Amanda Administrator for Amanda
Voice Server).
The default appears in install.cfg as:
set modified_call_screening true
General Options (Continued)
Configuration Option Description
202 Installing Amanda@Work.Group/DOS
msg_log Amanda creates the specified file in the C:\AMANDA directory and logs:
The date and time every message is received
The date and time every mailbox is checked for messages along with the DTMF the
user entered.
The default is no filename, which means no log is written to. We recommend using
'MSG.LOG'.
See also user_log.
The default appears in install.cfg as:
set msg_log ''
n_ochan Allows you to dedicate ports to notification. The default is 0 (no dedicated ports). A
positive integer n dedicates the first n ports.
For example, when n_ochan is 2, ports 1 and 2 are dedicated and do not answer in-
coming calls. When using dedicated notification, be sure to direct incoming calls to
ports 3 and up (in this case).
Dedicated notification eliminates the notification collision (known as glare) caused
when Amanda inadvertently begins a notification on a port receiving an incoming
call. However, you can no longer use the port for incoming calls.
When 0, Amanda does either roving or restricted notification (depending on the val-
ue of notify_restriction). With roving notification, Amanda starts with the last port
in the hunt group and works backwards until she locates an idle port. Restricted no-
tification uses only one port, usually the last port in the hunt group. However, that
port is not dedicated to notification. The port can still receive calls.
NOTE:When using roving or restricted notification, program the ports to be in a
linear hunt group (not a circular hunt group).
The default appears in install.cfg as:
set n_ochan 0
nam_maxlen The maximum number of seconds to allow for recording a mailbox’s name and ex-
tension. Amanda plays the name and extension recording to provide callers with in-
formation from the employee directory and to identify who is being called.
A number of seconds. The range is from 1 to 99. The default is 5.
See also box_idx and modified_call_screening.
The default appears in install.cfg as:
set nam_maxlen 5
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 203
new_send Determines whether a user can send a message to more than one user, when those
users are not part of a single list.
True or False. The default is True.
When True, a user can send a message to several mailboxes “on the fly.” When the
user presses 4 to send a new message, then 1 to select a mailbox destination, Aman-
da asks for the “next mailbox or the # sign to finish.” When the user presses 3 to
send, or 5 to send with verification, the message is sent to every mailbox that was
entered.
When False, the user can send a message only to one mailbox or to a previously cre-
ated list of mailboxes.
The default appears in install.cfg as:
set new_send true
non_relay_ok Normally a caller presses ## to end the greeting and leave a message. With this op-
tion, the caller can simply press # (unless the mailbox does relay paging which is
activated by the #).
True or False. The default is False.
When True and the mailbox does not have a relay paging notification record, press-
ing # takes the caller to the end of the greeting.
When False, the caller must press ## to end the greeting.
The default appears in install.cfg as:
set non_relay_ok false
notify_restriction If you specify a port, Amanda restricts notification to that port. However, the port
still takes incoming calls.
Use any port number or 0. 0, the default, means that roving or dedicated notification
is being used instead of restricted notification. You typically use the last port in the
linear hunt group.
You must use this option if you install Amanda on a telephone switching system that
requires the same port to turn message lights both on and off. In this case, roving
notification could cause a message light to come on and stay on.
Restricted notification does not eliminate the possibility of notification collisions
(known as glare).
If notify_restriction is set to an invalid value, Amanda detects that during startup,
resets notify_restriction to the highest port number, and logs that fact. See also
n_ochan.
The default appears in install.cfg as:
set notify_restriction 0
General Options (Continued)
Configuration Option Description
204 Installing Amanda@Work.Group/DOS
off_dly Amount of time after a line goes off-hook before the voice board notifies Amanda
that the line is off-hook.
Number of hundredths of seconds. The default is 50 (.5 sec.). The range is 1-6553.
The numbers 0 and -1 have special meanings.
When 0, Amanda uses the voice board's default (which is also 50).
When -1, there is no delay.
The default appears in install.cfg as:
set off_dly 50
partial_q_ok Determines what messages are saved when the Q() command is used to get answers
from a caller.
True or False. The default is False.
When True, Amanda saves a message even if the caller hangs up before answering
all the questions.
When False, Amanda does not save a message using the Q() command unless all the
questions have been answered.
The default appears in install.cfg as:
set partial_q_ok false
password Sets the Amanda password. The password is case-sensitive, so uppercase letters are
different from lowercase letters. That means that AMandA, Amanda, and amanda
all represent different passwords.
Use a text string with a maximum length is 8 characters. The default is AMandA.
If you use the null string (that is, no password), you must use a dealer password to
operate and shut down Amanda.
The default appears in install.cfg as:
set password 'AMandA'
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 205
PBX This option is described here in case you decide to change it by editing install.cfg.
(However, setting this option is not recommended.) The PBX option (not to be con-
fused with the pbx option) does not appear in the General Configuration section of
the Setup utility because Setup makes changes to this option automatically. This op-
tion indicates a number for a PBX and a name for its .PBX and .TON files.
Setup assigns the number 1 to your first PBX and the number 2 to your second (if
you have a second PBX).
Setup automatically assigns a name (up to 8 characters) to the .PBX and .TON files
that Amanda uses with your telephone switching system. By default, Setup uses
1001 for the first PBX and 2001 for the second. You can use any name in install.cfg,
but it is best to use the defaults. If you must change this option, use a number greater
than 2001 or a non-numeric name.
Amanda's Setup utility provides a list of PBXs. When you select your first telephone
switching system, information about that switch’s known dial codes, integration pat-
terns, and so forth is automatically copied to 1001.PBX. When you select the sec-
ond, information bout that switch is copied to 2001.PBX.
Then you modify those files to suit your needs.
If you run Setup or Diag to discover tone patterns, the patterns are stored in
1001.TON and 2001.TON respectively.
See also pbx in the Per Port section.
The defaults (which do not start with the word set) appear in install.cfg as:
PBX 1 1001
play_from When playing your messages, this option controls whether Amanda identifies the
Amanda user who sent (or forwarded) each message.
True or False. The default is False.
When True, Amanda indicates who sent an internal message before she plays the
message. She plays the name and extension recording for the sender (if it exists). She
says the mailbox number (for example, mailbox 1-4-7) when there is no recording.
When False, Amanda only plays the message.
The default appears in install.cfg as:
set play_from false
General Options (Continued)
Configuration Option Description
206 Installing Amanda@Work.Group/DOS
play_new_first Determines what message is played next when the user has logged on to his mailbox
to play messages.
True or False. The default is False.
When True, pressing 1 plays the next new message and pressing 75 plays the mes-
sages in order, regardless of whether they have been heard.
When False, pressing 1 plays the messages in order and pressing 75 plays the next
new message.
See also urgent_to_front which affects the order of the mailbox’s message.
The default appears in install.cfg as:
set play_new_first true
play_skip The number of seconds to rewind or skip forward during message playback when a
* (rewind) or # (skip forward) is pressed.
The range is from 1 to 99. The default is 5.
The default appears in install.cfg as:
set play_skip 5
please_hold Controls the use of the “Please hold” prompt.
True or False. The default is True.
When True, Amanda says “Please hold while I try that extension” before transfer-
ring a caller.
When False, Amanda says nothing and immediately puts the caller on transfer hold.
The default appears in install.cfg as:
set please_hold true
product_activation_
key A number you receive from your Amanda Company sales representative to
activate your system. If one or more of your voice boards were not pur-
chased from The Amanda Company, you must also set activation_key. See
“activation_key” on page 183.
If you change the first board in your system, you need another product ac-
tivation key because the key is based on the serial number for the first
Amanda Company board.
The default is 0, which means there is no product activation key.
The default appears in install.cfg as:
set product_activation_key 0
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 207
prompt_file Specifies the language that Amanda uses when a call first comes in on a given port.
ENGLISH or SPANISH. The default is ENGLISH.
You can change the prompt file for that port “on the fly” using the L() command
from the Token Programming Language. Amanda can also change the language
prompts for that port based on the DTMF sent by the telephone switching system or
the central office.
The ENGLISH.IDX file contains the English prompts. SPANISH.IDX is also avail-
able. Please contact your Amanda Marketing Partner, Solution Provider, or sales
representative for more information and pricing.
The default appears in install.cfg as:
set prompt_file 'ENGLISH'
purge Controls how long messages that have been heard are stored before they are purged.
Number of days. The range is from 0 to 99. The default is 0.
If 0, no messages are purged.
Otherwise, messages that have been heard are purged after the specified number of
days. When users log in, Amanda tells them how many messages will be purged
when they exit message mode. This number is the number of heard messages that
have been stored longer than the number of days you specify here.
NOTE:Once a message is purged, there is no way to retrieve it.
The default appears in install.cfg as:
set purge 0
ramdisk Name of the ram drive (if any) used for temporary files.
The default is the C drive. The range is a single uppercase character from C to Z.
Before you change this make sure that you have set up a ram drive using the RAM-
DRIVE.SYS program from DOS.
The default appears in install.cfg as:
set ramdisk 'C:'
General Options (Continued)
Configuration Option Description
208 Installing Amanda@Work.Group/DOS
range1
range2
range3
range4
If you have a range key (for example range1_key for range1 or range2_key for
range2), you can activate 10000 mailboxes. Ranges and range keys are used for
third-party applications that program a range of mailboxes to perform certain func-
tions using the Token Programming Language. For more information, contact your
Amanda Company sales representative.
You set this option to the first number in the mailbox range. This number must be a
multiple of 10000.
The default is 10000 for range1, 20000 for range2, 30000 for range3, and 40000 for
range4.
See also range1_key, range2_key, range3_key, and range4_key.
The defaults appear in install.cfg as:
set range1 10000
set range2 20000
set range3 30000
set range4 40000
range1_key
range2_key
range3_key
range4_key
If you buy a third-party application that was customized for Amanda using the To-
ken Programming Language, you import the mailboxes programmed for that appli-
cation with the import utility.
Then, to activate that application, you set one of these options to the activation key
(or range key) that allows Amanda to use those mailboxes. For more information,
contact your Amanda Company sales representative.
The default is 0, which means there is no key.
See also range1, range2, range3, and range4, the options that you set to the first of
the mailboxes that correspond to the range key.
The defaults appear in install.cfg as:
set range1_key 0
set range2_key 0
set range3_key 0
set range4_key 0
recall_delay Amount of time the voice board waits after an earth recall (used in place of a hook-
flash on some telephone switching systems).
Number of hundredths of seconds. 0 tells Amanda to use the voice board's default
(which is 15 for Denmark or Holland and 50 elsewhere). Otherwise, the range is 1-
6553.
The default appears in install.cfg as:
set recall_delay 0
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 209
record_menu Controls Amanda’s use of prompts and menus before and after recordings.
True or False. The default is True.
When True, Amanda checks the values of begin_rec_prompt and end_rec_menu to
determine what to say.
When False, Amanda does not prompt the caller to leave a message at the tone nor
the user to record a greeting at the tone. She also does not play the post-record menu
that allows the caller or user to review and re-record.
The default appears in install.cfg as:
set record_menu true
recursive_deletes Controls whether Amanda deletes the guest mailboxes that were created for
a mailbox at the same time the mailbox is deleted.
True or False. The default is False.
When True, when Amanda deletes a mailbox, the guest mailboxes that were
created for that mailbox are also deleted. This deletion is recursive.
When False, only the mailbox is deleted. Its guest mailboxes remain avail-
able for use.
The default appears in install.cfg as:
set recursive_deletes false
rmt_rna In a notification record, when using W(0,P) or W(0,V) to wait for a pager or voice
answer, the number for this option replaces the 0 and provides the number of remote
rings that Amanda must hear before she decides that there is no answer.
The default is 4. The range is 1 to 9.
The default appears in install.cfg as:
set rmt_rna 4
General Options (Continued)
Configuration Option Description
210 Installing Amanda@Work.Group/DOS
rotary Controls the detection of rotary digits.
True or False. The default is False.
When True, Amanda detects rotary digits.
When False, Amanda does not detect rotary digits.
NOTE:Only rotary digits 3(9 and 0 are currently detected on the Brooktrout 2132
and 4132 boards. Therefore, if you plan to use this feature, make sure that
all your mailboxes exclude the digits 1 or 2. Also, there are no * and # signs
on rotary phones, therefore setting this to True introduces additional delays
when the system detects the dialed number. For full rotary detection, please
contact your Amanda Sales Representative for other options.
NOTE:The Brooktrout 232 and 432 boards do not support rotary detection. If ro-
tary detection is required, use Brooktrout 2132 and 4132 boards.
NOTE:The 727 Brooktrout drivers (shipped with Amanda version 6.02) does not
support rotary. You can switch to the 537 drivers. First save VOICEC-
NF.EXE as VOICECNF.727 and RHETDRV.EXE as RHETDRV.727.
Then copy VOICECNF.537 to VOICECNF.EXE and RHETDRV.537 to
RHETDRV.EXE. These files are in C:\PLATFORM.
The default appears in install.cfg as:
set rotary false
screen_save The file in the C:\AMANDA directory in which screen traces are saved. Whenever
you use screen trace, the data is saved to the designated file. Otherwise, the data ap-
pears only on the screen.
The default filename is SCREEN.OUT.
The default appears in install.cfg as:
set screen_save 'screen.out'
sec_code_display Controls whether security codes are visible from the User screen on Amanda stan-
dalone and from Amanda Administrator.
True or False. The default is False.
When True, the security codes are visible.
When False, they are replaced by asterisks.
The default appears in install.cfg as:
set sec_code_display false
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 211
security_min_length The minimum length of a user’s security code (when changed by a user over the tele-
phone or when using Amanda Messenger). This does not affect the length of security
codes that are entered from Amanda standalone or from Amanda Administrator. The
administrator can use any password of 8 or fewer characters.
A number from 1 to 8. The default is 1.
The default appears in install.cfg as:
set security_min_length 1
short_direct_send The direct message mailbox (usually 998) is for leaving messages for any Amanda
user. It does not ring that user’s extension. After entering 998, the caller is asked for
the destination mailbox then leaves his message.
This option controls how Amanda identifies the user before the message is left. This
confirms that the caller entered the mailbox that he intended to.
True or False. The default is False.
When True, the caller hears “You entered” followed by the name and extension re-
cording for the user—if there is one. Amanda says the mailbox number (for exam-
ple, mailbox 1-4-7) when there is no recording.
When False, the caller hears the mailbox’s current greeting (which can be skipped
by pressing # twice).
The default appears in install.cfg as:
set short_direct_send false
shutdown The day and time that Amanda performs her weekly automatic shutdown for disk
maintenance and/or tape backup.
A day of the week followed by a space and a time of day. The default is '2 130'
(Tuesday, at 1:30 a.m.).
For the day of the week, 0 means Sunday, 1 is Monday, ..., 6 is Saturday, and -1 is
everyday.
The time is in the 24-hour format. For example, 9:30 p.m. is 2130 without the colon
(:).
The default appears in install.cfg as:
set shutdown '2 130'
General Options (Continued)
Configuration Option Description
212 Installing Amanda@Work.Group/DOS
tape_length When a user selects 1, 7, 8 (for continuous play) from the top level menu, this option
indicates how long Amanda will play messages continuously (with a beep between
them). Usually this is equal to the length of one side of a tape. It allows users to ar-
chive their messages. Users can record the messages on tape using a microphone if
the telephone does not have a jack for this purpose.
Number of minutes from 1 to 99. The default is 30.
The default appears in install.cfg as:
set tape_length 30
timestamp_forwards Controls the date and time given to a forwarded message.
True or False. The default is True.
When True, the date and time tell when the message was forwarded. This can pre-
vent messages from appearing to be delayed when they are forwarded without ex-
planatory prefixes.
When False, the date and time tell when the message was first recorded.
The default appears in install.cfg as:
set timestamp_forwards true
tmo_blank Controls how long Amanda waits after the last keystroke before blanking the Main
screen (to prevent screen burn-in). Amanda blanks the screen only if the Main screen
is displayed. A value of 0 stops Amanda from ever blanking the screen. (This option
does not apply to Amanda voice server.)
Number of minutes. The range is 0 to 99. The default is 5.
See also advertising.
The default appears in install.cfg as:
set tmo_blank 5
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 213
tmo_dir_transfer Controls whether the caller hears the 411 directory information prompt with
the instructions about how to be transferred to an extension. If the value is
0, the prompt is not played. If you use a number greater than 0, Amanda
waits that number of seconds for a response from the caller. The default is 2.
The prompt after each match is: “To be transferred to this extension, press
*. Otherwise, press # to continue.”
If you are selecting a recipient for voice mail, the prompt is: “To select this
extension, press *. Otherwise, press # to continue.”
When there are no more matching directory entries, the prompt is: “To
search the directory again, press *. Otherwise, press #.”
The default appears in install.cfg as:
set tmo_dir_transfer 2
tmo_disk Controls how often Amanda checks for low disk space. Amanda also checks for low
disk space when she starts up.
Number of minutes. The range is 0 to 255. The default is 60.
See also diskwarn.
The default appears in install.cfg as:
set tmo_disk 60
tmo_dtmf The amount of time Amanda waits after a DTMF digit before deciding the caller has
finished the entry. (If the caller presses #, Amanda immediately recognizes this as
the end of a DTMF entry.)
Number of tenths of seconds (from 1 to 255). The default is 12 (1.2 seconds).
The default appears in install.cfg as:
set tmo_dtmf 12
tmo_hold Determines how long Amanda waits after a caller presses * to hold for an extension
that is busy before trying to transfer the call again. This is only used when the file
C:\AMANDA\HOLD.VOX, which Amanda normally plays for callers on hold, is
missing. Usually Amanda tries to transfer the call after playing the file.
Number of seconds. The default is 20. The range is 0 to 255.
NOTE:You can record over HOLD.VOX using the system administration menu
from the system administration mailbox (mailbox 999.) You may want to
save the original first.
The default appears in install.cfg as:
set tmo_hold 20
General Options (Continued)
Configuration Option Description
214 Installing Amanda@Work.Group/DOS
tmo_idle Number of seconds of inactivity after which Amanda decides that the port is idle.
The default is 0. The range is 0-999.
When greater than 0, Amanda goes off-hook and back on-hook after deciding that
the port is idle. This is necessary when a telephone system does not release a station
that is connected to Amanda even after Amanda has gone on-hook (a rare occur-
rence).
When 0, Amanda does not go off-hook and back on-hook if a port is idle.
The default appears in install.cfg as:
set tmo_idle 0
tmo_integrate During inband integration, this option causes Amanda to wait the specified number
of seconds for the first digit to arrive. Then the seconds in the timeout period (spec-
ified in the .pbx file) begin. After the first digit arrives, Amanda continues to read
digits until the timeout period ends.
The range is 0 to 255. The default is 0.
The default appears in install.cfg as:
set tmo_integrate 0
tmo_menu The amount of time Amanda waits before repeating a menu when no selection is
made.
Number of tenths of seconds from 1 to 99. The default is 20 (2.0 seconds).
The default appears in install.cfg as:
set tmo_menu 20
tmo_pickup The minimum amount of time Amanda waits between an on-hook and off-hook
event.
Number of tenths of seconds from 1 to 99. The default is 20 (2.0 seconds).
The default appears in install.cfg as:
set tmo_pickup 20
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 215
tmo_rna For some PBXs, Amanda assumes that the called party is not going to answer the
telephone if there is no answer after a certain length of time. The amount of time she
waits is the product of this setting times the maximum number of rings for a Ring
No Answer. (The maximum number of rings is set per mailbox using the Maximum
Rings field for Amanda Standalone or the Adjust Maximum Rings text box in
Amanda Administrator.)
This setting is in tenths of seconds and is the estimated length of time it takes for a
ring. The default is 60 (which is an estimated six seconds per ring). The range is 0
to 65535.
The defaults appear in install.cfg as:
set tmo_rna 40
tmo_serial Number of seconds to wait for a response from a peripheral device connected to one
of Amanda’s serial ports.
When communicating with peripheral devices through a serial port, Amanda needs
a timeout value so she doesn't wait forever for a response.
Number of seconds from 1 to 999. The default is 2.
The default appears in install.cfg as:
set tmo_serial 2
tmo_silence The maximum seconds of silence before Amanda decides that the caller or user is
finished recording a message or greeting.
The post record menu plays if the record_menu option is True. The caller can press
3 to append the message if he was just pausing too long.
If the number is 0, Amanda does not use silence to determine completion.
Number of seconds from 0 to 255. The default is 5.
The default appears in install.cfg as:
set tmo_silence 5
tmo_sound The maximum seconds of continuous sound/dial tone before Amanda decides that
the caller or user is finished recording a message or greeting and has hung up. If the
number is 0, Amanda does not use sound/dial tone to determine completion.
Number of seconds from 0 to 255. The default is 5.
The default appears in install.cfg as:
set tmo_sound 5
General Options (Continued)
Configuration Option Description
216 Installing Amanda@Work.Group/DOS
tmo_xfer This option is required only for telephone switching systems, such as Comdial DXP
and Panasonic KXT-D, that can send DTMF tones in place of PCPM tones. See also
dtmf_action.
The default appears in install.cfg as:
set tmo_xfer 20
tokens_available Lists the tokens available to program with. Depending on the type of Amanda sys-
tem you have, you may not be able to use all the tokens in the list.
You can make additional restrictions by deleting tokens that your system can use
from the list. For example, deleting the G token makes it impossible to program a
move from one mailbox to another via tokens.
The default is 'GIJLMNOPQRSTUVW<>+-?=|[]{^@'
The default appears in install.cfg as:
set tokens_available 'GIJLMNOPQRSTUVW<>+-?=|[]{^@'
use_tutorial Controls whether Amanda uses the tutorial for setting up mailboxes when
users use the telephone user interface for the first time.
True or False. The default is True.
When True, Amanda suggests that the user use the tutorial to set up his or
her mailbox. Amanda continues to make this suggestion until the mailbox
has been set up.
When False, Amanda does not suggest that the user use the tutorial.
Regardless of the setting, Amanda retains information about who has and
hasn’t set up mailboxes so that anytime this configuration parameter is set
to True, Amanda behaves correctly.
The default appears in install.cfg as:
set use_tutorial true
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 217
urgent_to_front Controls the priority of urgent messages. This is not supported in Aman-
da@Work.Group/DOS when the server is enabled.
True or False. The default is True.
When True, Amanda places urgent messages in front of other messages (new and
old) for a mailbox. The user cannot press 4 to wrap from the first to the last message.
He must listen to the urgent messages first.
When False, urgent messages are mixed in with other messages in the order that they
were received.
See also play_new_first.
The default appears in install.cfg as:
set urgent_to_front true
use_pvc Controls whether Amanda uses the positive voice control feature available on the
Brooktrout voice board.
True or False. The default is True.
When True, Amanda detects a human voice faster, but there is a greater chance of
identifying an unanswered call as answered and ending her supervision of the call
too soon.
When False, Amanda may take more time to detect an answer during supervised
transfers, but false answer detects are less likely.
See also voice_analysis_length.
The default appears in install.cfg as:
set use_pvc true
use_tutorial Controls whether Amanda uses the tutorial for setting up mailboxes when
users use the telephone user interface for the first time.
True or False. The default is True.
When True, Amanda suggests that the user use the tutorial to set up his or
her mailbox. Amanda continues to make this suggestion until the mailbox
has been set up.
When False, Amanda does not suggest that the user use the tutorial.
Regardless of the setting, Amanda retains information about who has and
hasn’t set up mailboxes so that anytime this configuration parameter is set
to True, Amanda behaves correctly.
The default appears in install.cfg as:
set use_tutorial true
General Options (Continued)
Configuration Option Description
218 Installing Amanda@Work.Group/DOS
user_log If you provide a file name, Amanda creates that file and logs:
The date, time, and mailbox when any mailbox is accessed by DTMF. For example,
whenever a caller enters a mailbox, that information is logged.
The file can be analyzed later for call distribution and access to mailboxes by date,
day, and time.
The default is to not log data (because no file name is provided). We recommend
using 'USER.LOG'.
See also msg_log.
The default appears in install.cfg as:
set user_log ''
voice_analysis_
length When positive voice control is used, this option specifies how long a noise must con-
tinue before Amanda decides that it is a voice answer and not just a glitch.
Number of hundredths of seconds. The range is from 1 to 6553. The suggested range
is 1 to 100. The default is 19.
NOTE: The default (.19 seconds) appears to eliminate false answer detection on
Panasonic and Samsung telephone switching systems, allowing them to
work with the 5.54 Brooktrout driver.
See also use_pvc.
The default appears in install.cfg as:
set voice_analysis_length 19
General Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 219
Fax Options
Configuration Option Description
fax_direct_
connect The string to send (after "AT") to the fax modem to make it connect to a ringing tele-
phone, play the CNG tone, and send the fax. Use a maximum of 20 characters. This
option defaults to 'H1O0' which some Zoom modems require.
NOTE:The value of H1O0 contains four distinct characters: alphabetic H, numer-
ic one, alphabetic O, and numeric zero.
The default appears in install.cfg as:
set fax_direct_connect 'H1O0'
fax_dl_init When a user is listening to messages over the telephone and discovers that he has a
fax message, he dials 72 to send the message to a fax machine followed by the tele-
phone number for the fax machine. Amanda dials this option before she dials the fax
machine's number. Usually, it is the dial code for accessing an outside line. The de-
fault is '9,'. Use a maximum of 20 characters.
The default appears in install.cfg as:
set fax_dl_init '9,'
fax_flow_control Defines the Class 2 command to set the type of flow control for the fax modem. The
default is '&K3'. Use a maximum of 20 characters.
For Use
Rockwell-based fax modems &K3
Aceex modems \Q3 X3 &K3
Practical Peripherals modems X3 &K3
Zoom modems &K3
Smart One 1442 modems &K4
Boca modem M144EW &K3
The default appears in install.cfg as:
set fax_flow_control '&K3'
fax_id Identifies your fax modem. Use the company name or the telephone number of your
fax machine. Use a maximum of 20 characters.
By default, no identification is provided. When two faxes connect, they exchange
and then display each other’s identifying strings.
The default appears in install.cfg as:
set fax_id ''
220 Installing Amanda@Work.Group/DOS
fax_id_pad Controls whether '1111' is added to the front of the fax_id. Many older fax modems
need some extra characters as padding. Otherwise, part of the identifying string is
cut off.
True or False. The default is True, but if '1111' appears on the receiving fax machine,
change this option to False (so no padding characters are added).
The default appears in install.cfg as:
set fax_id_pad true
fax_init String sent to initialize a fax modem (give it a known starting state). The default is
'&F0E0'. Use a maximum of 20 characters.
Some modems require "&F" rather than "&F0". The "E0" insures that the modem is
in non-echo mode, because the command that puts the modem into Class 2 or Class
2.0 mode expects the fax modem to be in non-echo mode first.
The default appears in install.cfg as:
set fax_init '&FE0'
fax_log Use this option to log data about files (not messages) that are faxed. Amanda creates
a log file in the C:\AMANDA directory and logs:
• The names of the files that were faxed
• The telephone numbers to which the files were sent
By default, no filename is used and no log is written. Use a maximum of 20 charac-
ters. We recommend using 'FAX.LOG'.
The default appears in install.cfg as:
set fax_log ''
fax_max_retries Defines the maximum number of times, after the first, to retry sending a fax file if it
is unsuccessful. This is used only when sending the fax in two-call mode (where the
caller enters a fax telephone number and the fax modem sends the file to that num-
ber).
The range is 0 to 9. The default is 1.
The default appears in install.cfg as:
set fax_max_retries 1
Fax Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 221
fax_receive_reverse True or False. Depends solely on the fax modem you are using. For most Rockwell-
chipset-based Class 2 modems, this parameter should be True. For most other mo-
dems (including Class 2.0), it should be False.
If set incorrectly, received faxes cannot be retransmitted or viewed at all. Setting it
to True reverses the bits within each received byte, correcting for an oddity in the
Rockwell firmware.
The default appears in install.cfg as:
set fax_receive_reverse false
fax_receive_speed The maximum speed for receiving faxes.
The value can be '0', '1', '3'. Use '0' for 2400 bps, '1' for 4800 bps, and '3' for 9600 bps.
Normally a value of '3' works for 486 CPUs at 25MHz or higher (and is the default).
If you experience data loss on your faxes, lower this setting.
The default appears in install.cfg as:
set fax_receive_speed '3'
fax_requeue_
interval Defines the number of minutes to wait between retries.
The range is 1 to 99. The default is 5.
See also max_retries.
The default appears in install.cfg as:
set fax_requeue_interval 5
fax_reset Defines the reset command to send to your fax modem when DTR (Data Terminal
Ready) is dropped. For most Rockwell-based fax modems, it should be '&D3', which
is the default.
Possible values: See your fax modem manual. Use a maximum of 20 characters.
The default appears in install.cfg as:
set fax_reset '&D3'
fax_send_reverse True or False, depends solely on your Class 2 or Class 2.0 fax modem. For most fax
modems, this option should be False.
The default appears in install.cfg as:
set fax_send_reverse false
Fax Options (Continued)
Configuration Option Description
222 Installing Amanda@Work.Group/DOS
fax_send_speed The maximum speed that Amanda uses to send faxes.
The value can be '0', '1', '3'. Use '0' for 2400, '1' for 4800, and '3' for 9600 bps. Nor-
mally a value of '3' works for 486 CPUs at 25MHz or higher (and is the default), but
it depends on your computer.
If you experience data loss on your faxes, lower this setting.
The default appears in install.cfg as:
set fax_send_speed '3'
fax_start_char Controls whether the system waits for the start character or not.
True or False. The default is False.
When True, Amanda waits for the character.
When False, Amanda does not wait.
Early drafts of the CCITT Class 2 Specification require that, when sending a fax, the
sender wait for the fax modem to send a control character indicating that it is ready
for the data to begin. Some modems lose data if the computer starts sending before
the fax modem indicates that it's ready to receive. Unfortunately, not all Class 2 fax
modems send the start character.
The default appears in install.cfg as:
set fax_start_char false
fax1
fax2
fax3
fax4
Use these options to define the station, or extension, number to which your fax mo-
dem is connected. For example, if the first fax modem is connected to extension 101,
set fax1 to '101'.
By default, no extension is set for a fax modem. Use a maximum of 7 digits.
The defaults appear in install.cfg as:
set faxn ''
where n is logical serial port 1, 2, 3, or 4. See serial_portn.
max_local_
extension The maximum number of digits that can be considered an extension number.
The default number is 6. The range is 1 to 6.
Users (at the message menu) can send fax messages they have received to a fax ma-
chine by entering 72 then a fax machine’s telephone number. Amanda applies
fax_dl_init (usually '9' for an outside line) if the telephone number entered by the
user has more digits than max_local_extension.
The default appears in install.cfg as:
set max_local_extension 6
Fax Options (Continued)
Configuration Option Description
Chapter 18: Configuration Reference 223
Hot Box Options
Configuration Option Description
hot_box Defines the mailboxes to which Amanda goes when she detects special PCPM tones.
You can have up to 10 hot_boxes. For example, you can configure a hot_box to de-
tect connections from TDD machines for deaf communications.
In most cases, only one hot_box is defined to detect fax tones and the remainder are
unused.
You provide a mailbox next to the corresponding PCPM code (12 to 21). The default
mailbox is -1, which means no mailbox. We recommend using 994 as the first
hot_box mailbox, but you can use any valid mailbox.
NOTE:To add a specific tone to the tone table, it must be one of the first four tones
defined, and it must be marked as a terminating tone. Call to be faxed Tech-
nical Note 8, “Special Tone Detection.”
The defaults appear in install.cfg as:
set hot_box -1 n
where n is either -1 or the PCPM code minus 12. (For example, for PCPM code 12,
you use 12-12 which is 0. The range for n is from -1 to 9.)
224 Installing Amanda@Work.Group/DOS
Network Options
Configuration Option Description
client_activation_
key Activation key that validates the value specified by n_clients. It is normally gener-
ated automatically as the client connections are installed. If you change or add a
board later, you need another activation key because the key is based on the serial
number for the first board. The first board is based on its low I/O port number (the
first Brooktrout board is usually 300H). Get the key from your Amanda Company
sales representative.
The default is 0, which means there is no client activation key.
See also n_clients.
The default appears in install.cfg as:
set client_activation_key 0
dialer_max_port Specifies the highest Amanda telephone port to be considered for use when Amanda
Dialer dials a number. The range is 0 to the highest port number available.
The default is 0. When dialer_min_port and dialer_max_port are both 0, Amanda
uses all ports.
The default appears in install.cfg as:
set dialer_max_port 0
dialer_min_port Specifies the lowest Amanda telephone port to be considered for use when Amanda
Dialer dials a number. The range is 0 to the highest port number available.
The default is 0. When dialer_min_port and dialer_max_port are both 0, Amanda
uses all ports.
The default appears in install.cfg as:
set dialer_min_port 0
dir_format Determines how names associated with mailboxes in the employee directory are for-
matted for the client applications. “%1” expands to the “Directory Name 1” field,
“%2” to the “Directory Name 2” field, and “%c” to the “Comment” field. Other
characters (such as space) are taken literally. The most common value is '%1 %2'.
The default is '%1 %2'.
The default appears in install.cfg as:
set dir_format '%1 %2'
Chapter 18: Configuration Reference 225
multiple_clients Controls whether multiple connections (logons) are allowed from the same mailbox.
The default is 3.The range is from 1 to 3. When 1, only one connection is allowed
per mailbox. When 2, only one connection is allowed per mailbox, with the excep-
tion of the special mailbox 999, which can connect multiple times. When 3, any
mailbox can connect multiple times.
The default appears in install.cfg as:
set multiple_clients 3
n_clients Along with client_activation_key, controls the number of client connections
(logons) that can simultaneously connect to the Amanda@Work.Group/DOS serv-
er. This is normally set automatically when the client connections are installed into
the server.
The default is 0, which means 1 client. The range is from 0 to 99 (99 is 100 clients).
The default appears in install.cfg as:
set n_clients 0
service_name The server's NETBIOS name.
The default is 'AMANDASERVER'.
The default appears in install.cfg as:
set service_name 'AMANDASERVER'
tmo_call_screening The number of seconds that Amanda waits for the user to accept or reject a call. This
applies to call screening and to waiting call processing.
The default is 30. The range is 0 to 255.
The default appears in install.cfg as:
set tmo_call_screening 30
Network Options (Continued)
Configuration Option Description
226 Installing Amanda@Work.Group/DOS
Outdial Options
Configuration Option Description
box_outdial Controls special mailbox options.
You provide a mailbox for each telephone digit that becomes a special mailbox op-
tion.
While logged into a mailbox, a user presses 7 to reach special options, then a digit,
0-9, depending on what you specify here. Then Amanda executes the tokens in the
extension field of the mailbox you specify for that digit.
Setting the mailbox to -1 disables that special mailbox option. For example, to allow
users to press 7 then 5 to call for the time of day, you might type 149 next to the digit
5. In this case, 149’s Extension field should contain the telephone number Amanda
dials for the weather (perhaps 9,8531212). Later, users log into their mailboxes and
press 75 for the current time. Afterwards they continue other mailbox options.
The defaults appear in install.cfg as:
set box_outdial -1 x
where x is a digit from 0 to 9
CAUTION:If you use box_outdial to give users an outside line, you might want to
use telephone lines that are toll restricted.
Chapter 18: Configuration Reference 227
Per Port Options
Configuration Option Description
box_grt Determines what greeting the caller hears first. This is set per Amanda telephone
port by assigning a mailbox to the port. Greeting 1 for that mailbox is the greeting
that the caller hears. By default, all ports are assigned 990, the Company Greeting
mailbox.
The defaults appear in install.cfg as:
set box_grt 990 n
where 990 is a mailbox and
where n is a port number from 1 to 24.
box_idx Sets the mailbox for the employee directory. This is set per Amanda telephone port
by assigning a mailbox to the port. The employee directory contains the names of all
the users as they appear in the Dir Name 1 and Dir Name 2 fields (on the Users
screen of the Standalone) or Directory Name 1 or Directory Name 2 (in the mailbox
window in Amanda Administrator).
The default is 411 for every port.
For example, to use one employee directory for the ports 1 and 2, another for port 3,
and a third for port 4, set box_idx to 411 for ports 1 and 2, 511 for port 3, and 611
for port 4.
NOTE:Callers use their telephone pad to spell the names of the users they want to
reach. Amanda plays the name and extension recording for every user that
matches. If there is no name and extension recording, Amanda says “mail-
box” and the number of that mailbox. Digits 7 and 9 should be used for let-
ters Q and Z respectively.
The default appears in install.cfg as:
set box_idx 411 n
where 411 is a mailbox and
where n is a port number from 1 to 24.
For reference purposes, the per port options are listed here in alphabetical order. In the Setup utility,
they are listed: pbx, box_grt, box_idx, box_snd, n_rings, and hangup_supervision.
228 Installing Amanda@Work.Group/DOS
box_snd Indicates what mailbox serves as the direct message mailbox. This is set per Amanda
telephone port by assigning a mailbox to the port. The direct message mailbox al-
lows you to leave a message for a mailbox without processing the mailbox. Amanda
does not execute the Extension field’s tokens or play a greeting. For example, an op-
erator can use the direct message mailbox to transfer callers directly to a user’s voice
mail.
The default is 998 for all ports.
The default appears in install.cfg as:
set box_snd 998 n
where 998 is a mailbox and
where n is a port number from 1 to 24.
hangup_supervision Allows you to use hangup supervision. This is set per Amanda telephone port.
True or False. The default is True.
Use True if your telephone switching system supports Loop Current Drop for
hangup supervision on the specified port. Even if it doesn’t, using True usually has
no negative effect.
Use False if you notice call transfer problems such as disconnects during three-way
conferences. However, if the problems persists, return to True.
The default appears in install.cfg as:
set hangup_supervision true n
where n is a port number from 1 to 24.
Per Port Options (Continued)
Configuration Option Description
For reference purposes, the per port options are listed here in alphabetical order. In the Setup utility,
they are listed: pbx, box_grt, box_idx, box_snd, n_rings, and hangup_supervision.
Chapter 18: Configuration Reference 229
n_rings Sets the number of rings that Amanda waits before answering a call on a given port.
To have port 7 answer after the second ring use n_rings 2 for port 7. This is
useful for those telephone switching systems that do not allow incoming lines to ring
in a station hunt group or do not provide delayed ringing. Also, it may be used to set
up backup answering for a secondary attendant operation.
The rings range from 0 to 9.
NOTE:There is a side-effect. When users want to pickup their messages, they must
wait the specified number of rings before Amanda answers.
The default appears in install.cfg as:
set n_rings 1 n
where 1 is the number or rings and
where n is a port number from 1 to 24.
pbx Indicates which Amanda telephone ports are connected to which PBXs. You pro-
vide the PBX's number (usually 1 or 2).
The defaults appear in install.cfg as:
set pbx 1 n
where 1 is the PBX number and
where n is a port number from 1 to 24.
Per Port Options (Continued)
Configuration Option Description
For reference purposes, the per port options are listed here in alphabetical order. In the Setup utility,
they are listed: pbx, box_grt, box_idx, box_snd, n_rings, and hangup_supervision.
230 Installing Amanda@Work.Group/DOS
Serial Port Options
Configuration Option Description
baud1
baud2
baud3
baud4
The bps (bits per second) for the logical serial port with the same number. For ex-
ample, baud1 gives the bps for serial_port1. (Serial_port1 can be mapped to any
COM port.)
Possible values: Any valid bps rate. The default is 19200.
The defaults appear in install.cfg as:
set baudn 19200
where n is the logical serial port 1, 2, 3, or 4.
databits1
databits2
databits3
databits4
The number of data bits for the logical serial port with the same number. For exam-
ple, databits1 gives the number of data bits for the COM port defined as serial_port1.
(Serial_port1 can be mapped to any COM port.)
Possible values are 7 or 8. The default is 8.
The defaults appear in install.cfg as:
set databitsn 8
where n is the logical serial port 1, 2, 3, or 4.
parity1
parity2
parity3
parity4
The parity for the logical serial port with the same number. For example, parity1
gives the parity for serial_port1. (Serial_port1 can be mapped to any COM port.)
Possible values are none, even, odd, mark, or space. The default is none.
The defaults appear in install.cfg as:
set parityn none
where n is the logical serial port 1, 2, 3, or 4.
Chapter 18: Configuration Reference 231
serial_port1
serial_port2
serial_port3
serial_port4
To communicate with peripheral devices connected to COM/RS232 ports, Amanda
needs to know which ports are connected.
This option matches the serial ports as Amanda knows them (called the logical serial
ports) to the actual COM1, COM2, COM3, and COM4 ports on the computer (called
the physical serial ports).
Possible values are 0 through 4. The default is 0, which means that the port is not
connected.
Only after this matching can Amanda communicate with devices, such as SMDI in-
terfaces, connected to her COM ports. For example, serial_port1 2 matches
serial_ port1 (Amanda’s first logical serial port) to the physical COM port 2 of the
PC. However, it is less confusing to use serial_port1 1, matching logical and
physical ports with the same number.
The defaults appear in install.cfg as:
set serial_portn 0
where n is the logical serial port 1, 2, 3, or 4.
stopbits1
stopbits2
stopbits3
stopbits4
The number of stop bits for the logical serial port with the same number. For exam-
ple, stopbits1 gives the number of stop bits for serial_port1. (Serial_port1 can be
mapped to any COM port.)
Possible values are 1 and 2. The default is 1.
The defaults appear in install.cfg as:
set stopbitsn 1
where n is the logical serial port 1, 2, 3, or 4.
Serial Port Options (Continued)
Configuration Option Description
232 Installing Amanda@Work.Group/DOS
SMDI Options
Configuration Option Description
smdi_activation_key A number you receive from your Amanda Company sales representative to allow
your system to use SMDI.
If you change or add a board later, you need another activation key because the key
is based on the serial numbers for the boards and the number of ports.
The default is 0, which means there is no smdi activation key.
The default appears in install.cfg as:
set smdi_activation_key 0
smdi_base_port Use this option to identify Amanda’s first voice mail port. The first voice mail port
is identified as logical port 1, with every successive port having a sequential logical
port number.
These numbers must be consecutive. The number for the second port must be one
more than the number for the first port, and so on.
The default number is 1. The range is 0 to 32000.
The default appears in install.cfg as:
set smdi_base_port 1
smdi_delay The time that Amanda waits after the phone rings and is answered, before looking
at the integration information (if any).
Use a number of tenths of seconds or 0. The default is 0. The range is 0-255. This
option does not apply to inband integration.
When non-zero, Amanda waits the specified time. This allows more than one string
to be sent to a given port per telephone call. The number should allow enough time
for all the strings to arrive, forcing Amanda to use only the last (most recent) one.
(The integration time specified in the 1001.PBX configuration file can be zero or
near zero, because Amanda has already waited for smdi_delay time to pass.)
For example, if smdi_delay is set to 30 (3 seconds), it is OK to use a pattern such as
integration 1 '...', which designates a 0.1-second integration timeout because Aman-
da waits 3 seconds for the last packet to be received.
The default appears in install.cfg as:
set smdi_delay 0
smdi_max The maximum number of characters expected in a generic SMDI packet.
The default is 143. The range is from 1 to 143. Use this when smdi_type is 'generic'.
The default appears in install.cfg as:
set smdi_max 143
Chapter 18: Configuration Reference 233
smdi_port The logical serial port (represented by serial_portn) to use for SMDI integration.
The port should already have been configured as a serial port using the options in
the Serial section of Advanced Configuration.
The range is 0 to 4. The default is 0 (no serial port used).
The default appears in install.cfg as:
set smdi_port 0
smdi_pretimeout The maximum number of seconds that an SMDI packet can precede the forwarded
call.
The default is 50. The range is from 1 to 99. Use this when the smdi_type is 'smdi',
'necmci', or 'generic'.
The default appears in install.cfg as:
set smdi_pretimeout 50
smdi_start The position in the integration packet sent by the telephone switching system where
the field containing the port number begins. The first position in the packet is num-
ber 1.
Use this option when smdi_type is 'necmci' or 'generic'.
The default is 8. The range is 0-65535.
The default appears in install.cfg as:
set smdi_start 8
smdi_stop The position in the integration packet sent by the telephone switching system where
the field containing the port number ends. The first position in the packet is number
1.
Use this option when smdi_type is 'necmci' or 'generic'.
The default is 11. The range is 0-65535.
The default appears in install.cfg as:
set smdi_stop 11
SMDI Options (Continued)
234 Installing Amanda@Work.Group/DOS
smdi_term Used only when smdi_type is 'generic'. The terminating characters (if any) which
define the end of a generic SMDI packet. You can include the following “escape”
sequences (similar to those used in strings within tokens)
Sequence Meaning
\n newline (carriage return followed by a linefeed)
\r carriage return
\j linefeed
\a attention
\d end of transmission
\\ backslash
\t tab
\digits The digits must represent the octal number for any character in the range
0 to 377 (That is 0 to 255 decimal). For example, to include the ASCII
character A (which is 101 in octal), you use \101.
When this option is not set, packets end only when smdi_max characters have been
received.
The default is an empty string, which means that packets end only when smdi_max
characters have been received.
The default appears in install.cfg as:
set smdi_term ''
smdi_type Indicates which SMDI integration protocol Amanda is to use.
For Bellcore Standard, use 'smdi'.
For AT&T System 75 or Definity-G3, use 's75'.
For NEC 2000 Message Center Interface use 'necmci'.
For Ericsson M-110 use 'md110'.
For the generic driver, use 'generic'.
The default appears in install.cfg as:
set smdi_type 'smdi'
SMDI Options (Continued)
Chapter 18: Configuration Reference 235
T1/DID Options
Configuration Option Description
did_dtmf Indicates what kind of integration digits Amanda reads when did_mode is True.
True or False. The default is True.
When True, Amanda expects either MF or DTMF digits.
When False, she expects the digits as pulse.
See also did_mf and did_mode.
The default appears in install.cfg as:
set did_dtmf true
did_mf Determines what kind of integration digits Amanda reads when did_dtmf is True
and did_mode is True. Otherwise, Amanda ignores this option.
True or False. The default is False.
When True, Amanda expects MF digits.
When False, Amanda expects DTMF digits.
See also did_dtmf and did_mode.
The default appears in install.cfg as:
set did_mf false
did_mode Indicates whether Amanda is using DID.
True or False. The default is False.
When True, Amanda expects a DID interface (such as EXACOM) that processes a
hookflash as battery reversal.
When False, Amanda does not expect a DID interface.
The default appears in install.cfg as:
set did_mode false
n_ani The number of Automatic Number Identification (ANI) digits to be read by Amanda
between the first and second wink in a 2-wink T1 environment.
The default is 0. The range is 0-255.
In a 2-wink T1 environment, Amanda may receive more digits than the Brooktrout
buffer can hold. So Amanda reads up to n_ani digits between the first and second
winks and starts processing them as part of the regular inband integration. After the
second wink, Amanda reads the remaining digits.
See also t1_mode and n_winks.
The default appears in install.cfg as:
set n_ani 0
236 Installing Amanda@Work.Group/DOS
n_winks If t1_mode is True, tells whether the environment is an immediate (0-wink), 1-wink,
or 2-wink environment.
Number from 0 to 2. The default is 1. When 2, you need to set n_ani.
See also t1_mode and n_ani.
The default appears in install.cfg as:
set n_winks 1
ring_mode Indicates whether Amanda expects a loop start or a DID interface line.
True or False. The default is True.
When True, Amanda expects a loop start line, and new calls are indicated by ring
voltage.
When False, Amanda expects a DID interface line, and new calls are indicated by
loop current.
The default appears in install.cfg as:
set ring_mode true
t1_mode Indicates whether Amanda is to use a T1 line.
True or False. The default is False.
When True, Amanda expects a T1 line and can process it using a Brooktrout 24000
board.
When False, Amanda does not expect a T1 line.
The default appears in install.cfg as:
set t1_mode false
T1/DID Options (Continued)
Configuration Option Description
Appendix A:
Troubleshooting Amanda
New Problems
Solving a problem often requires sending annotated trace files to The
Amanda Company. Amanda Company customer service representatives
need to know what happened, what SHOULD HAVE happened, what time,
and so on. The trace files need to go to the right people in a timely manner. If
a line connected to Amanda goes out of service, The Amanda Company
needs trace information on the last activity on that line. Submit trace files to
a place accessible to everyone even if the customer service representative
you have been working with is out of the office: customer.support@taa.com.
Resetting a Port from the Main Screen
Amanda standalone uses the Main screen primarily to display information
about the system. However, Amanda also allows you to reset a port from the
Main screen so that the system does not have to be completely shut down.
This is a hidden feature, so that people will not accidentally make a port idle.
No dialog box appears on the screen.
If you are using the server version of Amanda, the same feature is available
within the Monitor client which is usually used by the system administrator.
Ports are represented by two digits. Port 1 is 01, port 5 is 05, port 13 is 13,
and so forth.
238 Installing Amanda@Work.Group/DOS
To reset a specific port (make it go IDLE), do the following:
1. Press Ctrl+Home.
2. Press Alt+P.
3. Enter the two-digit port number.
This forces a hangup on the specified port.
CAUTION:Anyone using the port being reset is disconnected
without warning.
What to Do When…
This section explains what to do when:
• Amanda does not transfer the call
• The caller doesn’t hear the Busy or RNA Greeting
• Notification does not work correctly
• The Host/Remote programs do not work
• You see the message: RDSP Not Located at any Interrupt Vector
Amanda Does Not Transfer the Call
If Amanda does not transfer the call, one of the following may be causing the
problem.
Problem: The mailbox has Do Not Disturb turned ON.
Solution: If ON, no transfer is attempted and the caller immediately hears the cur-
rent greeting of the mailbox. Check the mailbox you are calling to make
sure Do Not Disturb is OFF.
Problem: The dial codes are incorrect.
Solution: Run the Setup utility, selection 1, to verify that the dial codes are correct
for the telephone switching system Amanda is connected to.
NOTE:The telephone switching system dial codes should be in the
system’s manual.
Appendix A: Troubleshooting Amanda 239
Problem: The telephone switching system returns stutter dial tone on a trans-
fer hookflash.
Solution: If stutter dial tone is returned, change the value of the Number of seconds
to wait for dial tone detection option to 0 seconds. (Run the Setup utility,
selection 1.)
Problem: The telephone switching system does not return dial tone on a trans-
fer hookflash—and it is supposed to.
Solution: Do one or more of the following:
• Check your single line station card to see if it is operating properly
• Use a buttset or single line telephone to verify that the switch is not
giving dial tone to the ports
• Check to see that you have enough Touch Tone Receivers (TTRs,
also called DTMF receivers)
Problem: Token programming is being used and a hookflash has not been en-
tered in the Extension field.
Solution: Review the tokens and insert a hookflash where needed. When the Ex-
tension field starts with @, a F- or %X will not enable PCPM. Amanda
does not listen for call progress tones. The W() token can be used to listen
for voice.
Problem: An additional hookflash is needed because the transfer involves both
Centrex lines and a telephone switching system.
Solution: Include another F- in the Dial code to put a caller on transfer hold option
(also known as dl_dtwait). (Run the Setup utility, selection 1.)
Problem: The call progress tones are not correct.
Solution: You should use GetTones or AccuCall Plus to correct the call progress
tones. See “Defining Dial Codes” on page 51 or “Using AccuCall Plus”
on page 62.
Problem: There may be insufficient intercom paths on older analog telephone
switching systems.
Solution: Check your telephone switching system’s intercom path capability to see
if additional hardware will add more intercom paths.
240 Installing Amanda@Work.Group/DOS
Caller Doesn’t Hear the Busy Message or RNA Greeting
If the caller does not hear a busy or RNA (ring no answer) greeting, one of
the following may be causing the problem.
Problem: Amanda is unable to recognize a busy or RNA tone.
Solution: Rerun GetTones or AccuCall Plus to requalify the tones Amanda is lis-
tening for. See “Defining Dial Codes” on page 51 or “Using AccuCall
Plus” on page 62.
Problem: Amanda is doing blind transfers rather than supervised transfers.
Solution: Check the Extension field of the mailbox you are calling and the What to
dial AFTER dialing the mailbox extension option (also known as
dl_suffix) to see if an H has been added. (Run the Setup utility, selection
1.) If the integration codes are unique, blind transfers are OK, but the sta-
tions must be forwarded back to Amanda.
Problem: The U token (used to indicate a partially supervised transfer) is un-
recognized, so the call is not processed correctly.
Solution: Remove the U token and place the call again to see if the greeting can be
heard or look at the trace file to see which token within the extension field
is failing.
Problem: The integration patterns are incorrect.
Solution: Run a trace on the system to see if the integration strings coming across
the port match the ones Amanda is expecting. (Run the Setup utility, se-
lection 3.)
Problem: The Busy and Ring No Answer integration patterns are identical, so
Amanda treats both types of calls the same.
Solution: Remove one of the integration strings by running the Setup utility, selec-
tion 3. Integration strings include:busy ('bbbb')
ring no answer ('rrrr')
NOTE:This prevents the caller from hearing one of the two greet-
ings. You should remove the busy integration string (the
one including the b’s).
Problem: The Busy chain or RNA chain sends the call to another mailbox.
Solution: Check the mailbox you are calling to be sure the Busy and RNA chains
are empty.
Appendix A: Troubleshooting Amanda 241
Notification Does Not Work Correctly
If notification does not work correctly, one of the following may be causing
the problem.
If using roving notification, make sure that all single line ports connected to
the voice board ports get dial tone when they go off-hook and also program
the phone system to grant all Amanda ports outside dial tone, when a 9 or
some other code is dialed.
If using dedicated or restricted notification, make sure that the designated
port has the attributes stated in the above paragraph.
Problem: H in Notify Method field.
Solution: Check to see that the dial string in the Notify Method field for the mail-
box does not contain an H.
Problem: Using %E in a Method field
Solution: You cannot use %E in a notification Method field unless the Extension
field contains only the extension number. To insert an extension number
into a Method field when you cannot use %E, do one of the following:
• Use %U instead of %E if the extension number and the mailbox
number are the same
• Put the extension number in the Variable field in the notification
record and use %V in the Method field
Problem: Timing problems (pager with voice greeting, Amanda not waiting
for dial tone).
Solution: Call the pager and count the seconds and/or rings it takes to respond. Use
the W token to wait an appropriate time and/or number of rings.
Problem: Wrong code for message waiting lights.
Solution: Check your telephone switching system manual to verify that the codes
for turning on a message waiting light from a single line extension are
correct. Test by using a single-line telephone or sending both on and off
strings.
Problem: Wrong type of notification record.
Solution: Be sure you selected the right type for the notification record. For exam-
ple, the notification record that turns the message light off must have the
type PICKUP.
Problem: Max Times is set for 0.
Solution: Make the value in the Max Times field in the Notify record greater than
zero.
242 Installing Amanda@Work.Group/DOS
Host/Remote Programs Do Not Work
If the Host and Remote programs do not work, one of the following may be
causing the problem. See “Chapter 14: Accessing Amanda Remotely.”
Problem: Both modems used have a bps higher than 2400.
Solution: Make sure you use /f on the command line if both modems are faster than
2400 bps (bits per second).
Problem: Host is not loaded in the AUTOEXEC.BAT file or has not been load-
ed manually.
Solution: Check your AUTOEXEC.BAT to see if “rem” is in front of
LH HOST /4 statement. Or type LH HOST /x with the COM port x at the
DOS prompt (C:\).
Problem: Host is installed on the wrong COM port.
Solution: Check what COM port your modem is using and change the LH HOST
statement to use that port number.
Be sure that the host program is not using the same COM port as any other
process, such as SMDI or your fax modem.
Problem: An internal modem is being used and there is an IRQ or a COM port
conflict with the computer’s controller card.
Solution: Check your computer’s controller card and verify that your modem’s
COM port is disabled on the controller card.
Problem: Remote is installed on a COM port other than COM 1 or 2.
Solution: To use the Remote program, the modem must use only COM 1 or COM
2. Verify that the modem is set for one of these ports. Then run the remote
program designating the correct port.
Problem: Other communications software is still running.
Solution: Remove all other remote software from the computer’s AUTOEX-
EC.BAT file and do not load any other remote software manually.
Message: RDSP Not Located at Any Interrupt Vector
If you see the RDSP Not Located at any Interrupt Vector message, one of the
following may be causing the problem.
Problem: The CMOS settings are incompatible.
Solution: Make sure the CMOS settings disable all adapter ROM shadowing or
shadow RAM, except for the F000 (hexadecimal) segment/system ROM
shadow.
Appendix A: Troubleshooting Amanda 243
Problem: The Exclusion statement in CONFIG.SYS is incorrect.
Solution: Back up your existing CONFIG.SYS, AUTOEXEC.BAT, and \PLAT-
FORM\CONFIG files.
Then try to rerun, from the C:\ prompt, 1STTIME.BAT to reconfigure your
PC’s memory.
Problem: There is a conflict between the settings in the CONFIG.SYS and
\PLATFORM\CONFIG files.
Solution: Check to see that the dualport statement in the \PLATFORM\CONFIG
file matches the first two characters in the exclusion (X=) statement in
the CONFIG.SYS file.
NOTE:Reboot after making any changes in the CONFIG.SYS file,
AUTOEXEC.BAT file, or \PLATFORM\CONFIG file.
Problem: RHETDRV.EXE and VOICECNF.EXE files are not the same ver-
sion.
Solution: As installed, RHETDRV.EXE and VOICECNF.EXE are Version 7.27.
Each earlier version has the file extension that matches its version num-
ber. For example, RHETDRV.554 means Brooktrout driver version 5.54.
Problem: The Brooktrout board is not installed or properly seated in the PC.
Solution: Turn the power off and check that the board is properly seated in its slot
on the motherboard.
System Halts
Problem: The 727 Brooktrout driver is installed and the rotary configuration
option is set to true.
Solution: The 727 Brooktrout driver (shipped with Amanda version 6.02) does not
support rotary. You can switch to the 537 drivers. First save VOICEC-
NF.EXE as VOICECNF.727 and RHETDRV.EXE as RHETDRV.727.
Then copy VOICECNF.537 to VOICECNF.EXE and RHETDRV.537 to
RHETDRV.EXE. These files are in C:\PLATFORM.
Problem: The lpt_port option is set to a non-zero number but no printer is at-
tached.
Solution: Run Setup as explained in “Chapter 6: Running the Setup Utility.” Select
System Configuration Options, then General Configuration, then Gener-
al Defaults. Change x in “Printer attached to LPT [x]” to zero if no printer
is attached.
Problem: The host is loaded on a non-existent COM port.
Solution: Check to see that the internal modem has not been removed.
244 Installing Amanda@Work.Group/DOS
Appendix B:
Troubleshooting the Clients
NIC Configuration
If you purchase a NIC other than the preconfigured NIC from The Amanda
Company, you may have to run the Setup program for that NIC. The
Amanda Company’s default settings for its NIC are:
•IRQ 10
• I/O 340
• Unshielded Twisted Pair (UTP) (10BASE T)
Addresses 300 through 305 are not available for the NIC. The voice boards
in the system will be using this range (300-305.) If there is a conflict with
configuring the I/O address, please remove the voice boards for the duration
of the configuration process. Set the I/O for 340 and then reinstall the voice
boards.
If you must use settings other than the default settings, you will need to edit
your PROTOCOL.INI and reconfigure your system accordingly.
246 Installing Amanda@Work.Group/DOS
Common Error Messages
Problem: NetBIOS Not Available
Solution: The protocol required to run the Amanda Clients is NetBIOS.
To define the NetBIOS protocol in Windows 3.11:
1. From the Program Manager, select Network.
2. Select Network Setup.
3. Select Drivers.
4. Highlight Microsoft NetBEUI.
5. Select Set as Default Protocol.
6. Close this window and continue exiting until you are told to restart Win-
dows.
7. Select Restart Windows to have your changes take effect.
To define the NetBIOS protocol in Windows 95:
1. Select My Computer.
2. Select Control Panel.
3. Select Network.
4. Highlight NetBEUI→NE2000.
5. Select Properties.
6. Select the Advanced tab.
7. Enable This Protocol to be default.
Appendix B: Troubleshooting the Clients 247
Problem: Server not available.
Solution: The most likely solutions are:
• The computer on which the server runs needs to be turned on
• The server may not be enabled
However, if the problem is not so easily resolved, check (on the client
workstation) for how NetBEUI is latched. (See the preceding problem for
how to view network settings.) If NetBEUI is displayed more than once,
select the one that is NOT latched to NE2000. It is most likely latched to a
Dial Up Adaptor or similar setting. Disable this so that the client finds the
server on the network instead of looking at the Adaptor first.
Problem: Server did not respond in allotted time.
The voice server is busy. This may cause a disconnection from the voice
server.
Solution: Exit the program and try again later.
Problem: Not enough resources (memory) available.
Too many applications running.
Solution: Start by closing some of the applications you are running and try again.
If that doesn’t work, completely exit and restart Windows.
Problem: Connection with Server closed.
The voice server is shutting down.
Too many network conflicts.
Other applications may be taking too much processing time for this
application to respond in the allotted amount of time.
Solution: Exit the program and try again later.
Problem: Session (connection with server) has ended abnormally.
The voice server is shutting down.
Too many network conflicts.
Other applications may be taking too much processing time for this
application to respond in the allotted amount of time.
Solution: Exit the program and try again later.
Problem: Client Connection unavailable.
Solution: Not enough Client Connections activated on the Amanda Voice Server.
To review or change the number of clients, see “Adding Client Connec-
tions” on page 178 and “Reviewing Client Connections” on page 180.
Please contact your Amanda Company representative for a new CCB.
248 Installing Amanda@Work.Group/DOS
Problem: Server did not respond in allotted time.
No connection with Server with current session number.
Session number out of range.
Connection with Server closed.
Server is unavailable.
Session (connection with server) has ended abnormally.
Solution: The server and client were never connected or have become disconnect-
ed. You need to log back on to Amanda Voice Server. Amanda Admin-
istrator, Amanda Monitor, and Amanda Messenger have Log On…
commands on their first menus.
Symbols
#end greeting 203
end of DTMF entry 213
%E token 241
%U token 241
%V token 241
Numerics
0 120
1001.PBX 51, 71
adding integration patterns
81
411 120, 227
prompt for transfer 213
8 120
990 120
991 120
994 121
995 121
996 121
997 121
998 121
998 shortcut
mailbox 120
999 122
A
abbreviate_dates 183
abbreviate_greeting 183
abbreviating
dates 183
system greeting 183
accessing
Amanda remotely 167
AccuCall Plus 62
tone patterns 62
Accucall Plus 239, 240
activating
Amanda 183, 206
mailboxes 208
SMDI 232
activation key 224
activation_key 183
active_hold 184
addressing
RDSP/x000 voice boards
19
RDSP/x32 voice boards 8
RTNI-xATI voice boards
26
ShowJump utility 11, 31
adpcm_hq 184
adpcm_nq 184
adpcm_pq 185
advertising 185
Amanda
accessed from another
computer 167
configuring 113
installing 39
protecting 36
shutdown 49, 211
uninstalling 39
updating 39
Amanda Dialer
maximum port number
224
minimum port number
224
Amanda upgrades 48
Amanda Voice Server modes
48
analog
telephone switching sys-
tems 239
ANI 235
character code 83
answering
beeps 188
applications
using mailboxes and to-
kens 208
assumptions iv
AT&T System 75 234
serial integration 144
ati_mode 185
attendant
automated 3
off-duty 3
primary 3
secondary 3
Index
250 Installing Amanda@Work.Group
auto_queue 186
auto_report 186
auto_report_time 186
AUTOEXEC.BAT
load Host program 242
automated attendant 3
Automatic Number Identifica-
tion 235
B
bcharacter code 83
base I/O ports 25, 28
baudn 230
beeps
connection 188
for recording 187
begin_rec_prompt 187
Bellcore Standard 136, 234
blind transfers 240
box_grt 120, 227
box_idx 120, 227
box_outdial 226
box_snd 121, 165, 166, 228
bps 230
bps rates
modem 242
Brooktrout
voice board 217
buses
MVIP 23, 28
Busy 66
busyactive hold 184
character code 83
dial code 54
dl_bsyret 54
no holding 188
Rhetorex notification op-
tion 187
time between transfer at-
tempts 213
treated as Ring No Answer
188
Busy chain 240
busy extensions 186
busy message 240
volume 195
busycycles 187
C
ccharacter code 83
ca_file 187
ca_port 187
cables
connecting computers 171
call accounting 187
call screening 201
client timeout 225
dial code 55
dl_hupret 55
caller
character code 83
caller ID
character code 83
caller instructions
mailboxes 120
callers
still on line 194
calling
operator after message
195
callsnot transferred 238
transferred after number of
digits 199
cancel_busy_hold 188
CCB 179
center
voice messaging 4
changing
CONFIG.SYS 48
character codes
integration patterns 82
characters
DTMF terminator 197
in SMDI packet 232
terminating SMDI packet
234
checking
disk space 213
clearing
DTMF buffer 192
Client Connection Bank 179
client_activation_key 224
clients
activation key 224
adding connections 178
call screening timeout 225
displaying connections
180
information in employee
directory 224
installing 175
number of connections
225
reviewing connections
180
clock_sync 188
clocks
synchronizing 188
CMOS settings
incompatible 242
cmt_maxlen 188
codes
character 82
Index 251
PCPM 121, 191, 197,
223
COM port
conflict 242
communications software 242
companies
sharing Amanda 155
company greetings
mailboxes 120
per port 156
conference call
dial code 56
dl_conference 56
CONFIG.SYS 243
changing 48
configuration
defining dial codes 51
defining DTMF integra-
tion patterns 71
defining tone patterns 59
configuring
Amanda 113
incoming calls 113
language 116
messages 114
notification 116
passwords 115
printers 116
RDSP/x000 voice boards
19
RDSP/x32 voice boards 8
RTNI-xATI voice boards
26
screen saver 116
shutdown 116
voice server 117
connect
dial code 55
dl_connect 55
connect_tone 188
connecting
beeps 188
computers by cable 171
computers by modem 172
ports 12, 30
connections
number available for cli-
ents 225
conventions iv
copyright ii
create_locked 189
creating
mailboxes 189
custom busy message
volume 195
customer support 5
D
database records
locking 189
databitsn 230
dates
abbreviated 183
forwarded messages 212
said by Amanda 183
db_locking 189
dealer sales 5
dedicated notification 118,
202
defaults
guest mailboxes 196
mailboxes 119, 189
defaults_box 121, 189
defining
dial codes 51
tone patterns 59
Definity-G3 234
serial integration 144
delay
after DTMF entry 213
before integration 232
between disk space checks
213
between DTMF tones 193
between menu repetitions
214
between messages when
delivering list
198
between on-hook and off-
hook events 214
between SMDI packet and
call 233
end of recording detected
215
hold between transfer at-
tempts 213
screen saver starts 212
waiting for peripheral 215
deleting
mailboxes 209
messages 207
deliveries
in future 121
delivering
message in future 195
departments
sharing Amanda 155
detecting
DTMF tones 193
fax machines automatical-
ly 129
dial codes
busy 54
call screening 55
connect 55
defining 51
252 Installing Amanda@Work.Group
dial tone detection 57
dl_bsyret 54
dl_conference 56
dl_connect 55
dl_dtwait 53
dl_hangup 57
dl_hupret 55
dl_init 56
dl_ndtret 54
dl_pickup 56
dl_prefix 55
dl_rnaret 54
dl_stop 56
dl_suffix 55
flash time 57
flashtm 57
hangup detection 57
incorrect 238
kinds of 53
message waiting indicators
57
off hook 56
prefix 55
ring no answer 54
suffix 55
system shutdown 56
system startup 56
tmo_dtwait 57
transfer dial tone 54
transfer hold 53
dial tone 193
not returned 239
stutter 239
when recording 215
dial tone detection
dial code 57
Dialer
maximum port number
224
minimum port number
224
dialer_max_port 224
dialer_min_port 224
dialtone detection
tmo_dtwait 57
DID 153, 235
did_dtmf 154, 155, 235
did_mf 154, 155, 235
did_mode 154, 155, 235
digits
DTMF 191, 195
dir_format 224
direct dial
character code 83
direct messages 211, 228
direct messaging
mailbox 121
per port 166
directory
employee 227
disk space
checking 213
warning 190
diskwarn 190
displaying
security codes 210
distribution sales 5
dl_bsyret 54
dl_conference 56
dl_connect 55
dl_dtwait 53, 239
dl_hangup 57
dl_hupret 55
dl_init 56
dl_ndtret 54
dl_pickup 56
configuration setting for
190
dl_pickup_on_ring 190
dl_prefix 55
dl_rnaret 54
dl_stop 56
dl_suffix 55, 240
Do Not Disturb 238
documents
faxing 133
DOS clock
synchronizing 188
DOSMODE 48
drivers
Rhetorex 218
DTMF 191
cleared from buffer 192
time between tones 193
time tones played 194
timeouts 214
tone detection 193
tones 191
waiting for 191
DTMF entry
ending 213
DTMF integration
trace files 72
DTMF integration patterns
adding 81
defining 71
testing 73
trace files 75
DTMF termination character
197
dtmf_action 191
dtmf_before_ring 192
dtmf_busy 191
dtmf_detect 193
dtmf_dly 193
dtmf_dnd 191
dtmf_dt 193
Index 253
dtmf_gate 194
dtmf_on 194
dtmf_ring 191
dtmf_xfer 191
E
echaracter code 83
earth recall 208
employee directories
mailboxes 120
per port 165
employee directory 227
client information 224
end user
support 5
end_rec_menu 194
ending
DTMF entry 213
DTMF input 197
recording 215
English 207
Ericsson MD-110
serial integration 146
Error Message
NetBIOS not available
246
Server not available 247
EXACOM 235
exit_digit 195
exit_to_0 195
extensions
busy 186
number of digits 199
F
fax machines
detecting automatically
129
fax modems
using 123
fax_direct_connect 219
fax_dl_init 219
fax_flow_control 219
fax_id 219
fax_id_pad 220
fax_init 220
fax_log 220
fax_max_retries 220
fax_receive_reverse 221
fax_receive_speed 221
fax_requeue_interval 221
fax_reset 221
fax_send_reverse 221
fax_send_speed 222
fax_start_char 222
faxes
incoming 223
sending 133
faxing
documents 133
hot box mailboxes 130
hot boxes 132
faxn 222
filescall accounting 187
screen traces 210
system logs 198
temporary 207
trace 237
First Use Questionnaire 89
flash time
dial code 57
flashtm 57
flashtm 57
future
delivering messages 195
future delivery 121
mailbox 121
future_delivery 121, 195
G
gain_loud 195
gain_norm 195
generic
serial integration 149
GetTones utility 59
greetings 240
ended with # 203
integrated calls 196
per port 227
recording 209
sampling rates 184
guest mailboxes
deleting 209
guest_defaults 121, 196
guest_max 196
guest_min 196
guests
mailbox defaults 196
maximum mailbox 196
minimum mailbox 196
guide
purpose 4
H
H token 241
hang up
mailbox 122
hanging up
on user 199
supervised 228
hangup detection
dial code 57
dl_hangup 57
hangup_supervision 228
hangups
supervised 228
hardware interrupts 197
holdactive 184
254 Installing Amanda@Work.Group
disabled 188
please hold prompt 206
time between transfer at-
tempts 213
HOLD.VOX
missing 213
hookflash 239
host computers
setting up 169
Host program 242
HOST.COM 167
hot box 223
hot box mailboxes 130
hot boxes 132
hot_box 121, 223
I
icharacter code 83
idle ports 214
ignoring
loop current 197
immediate record
character code 83
in band integration patterns
adding 81
inband integration
trace files 72
waiting periods 214
inband integration patterns
defining 71
testing 73
trace files 75
incoming
faxes 223
incoming calls
configuring 113
information system 4
initialization
dl_init 56
installation
support 6
installation checklist
RDSP/RTNI voice boards
17
RDSP/x32 voice boards 7
installing
Amanda 39
clients 175
LAN cards 35
MVIP cable 33
RDSP/RTNI voice boards
32
RDSP/x32 voice boards
11
integration 135
Bellcore Standard 136
Definity-G3 144
DTMF digits 235
Ericsson MD-110 146
generic 149
greetings 196
MF digits 235
NEC 2000/2400 141
pulse 235
SMDI 136
System 75 144
waiting 232
Integration Helper 85
integration patterns 240
adding 81
character codes 82
defining 71
Integration Helper 85
test calls 86
testing 73
trace files 75
integration_greeting 196
integration_term 197
international sales 5
international support 5
interrupts
hardware 197
irq 197
IRQ conflict 242
IVR 204
J
JOVE 51, 71
jumpers
RDSP/x000 voice boards
20
RDSP/x32 voice boards 9
RTNI-xATI voice boards
27
K
keysactivating Amanda 206
keys, activating Amanda 183
keys, activating range of mail-
boxes 208
keys, activating SMDI 232
keys, activation 224
L
LAN cards
installing 35
language
configuring 116
prompts 207
lcoff 197
lcvalid 197
lcwait 198
length
messages 200
Name and Extension re-
cording 202
ring 215
Index 255
security codes 211
lights
message 118
off 57
on 57
line interface
RTNI-xATI boards 29
linesloop start 236
lines, t1 235, 236
list comment
recording 188
list_delay 198
locking
database records 189
log files 198
logging
mailbox information 218
mailboxes 202
messages 202
system information 198
logical
serial port 233
serial ports 231
lognam 198
logons
multiple 225
loop current 236
drop 198
ignoring 197
off 197
loop start 153
loop start line 236
lpt_port 198
LPT1 198
M
mailbox log 218
mailboxes
activating 208
caller instructions 120
company greetings 120
created as read-only 189
default 119
default templates 189
deleting 209
direct messaging 121
employee directories 120
future delivery 121
guest default template 196
guest defaults 121
hang up 122
hot box 121
hot boxes 130
logging information 218
maximum for guest 196
messages from other users
205
minimum for guest 196
multiple logons from cli-
ents 225
number of digits 199
operators 120
PCPM 121
sending messages to 203
templates 121
manual
purpose 4
Max Times
notification 241
max_chain 199
max_dl_inits 199
max_local_extension 222
max_ports 199
max_prompt 199
maximum
characters in SMDI packet
232
maximum time
Name and Extension re-
cording 202
recording a list comment
188
maximums
number of ports 199
ports for Dialer 224
MD-110
serial integration 146
menus
port-recording 209
post-recording 194
recording 209
repeated 199
repeating 214
message lights 118
message log 202
message waiting indicators
dial codes 57
off 57
on 57
messages
automatic deletion 207
configuring 114
continuous play time 212
deleting 207
delivered in future 121
delivery in future 195
direct 121, 211, 228
forwarding date/time 212
left by other users 205
light on/off 241
log 202
minimum length 200
order 206
play new first 206
purging 207
recording 194, 209
256 Installing Amanda@Work.Group
reviewing 194
rewind time 206
sampling rates 184
saving 200
sending 203
skip forward time 206
storing voice responses
204
urgent 217
messaging center 4
minimum length
security codes 211
minimum time
DTMF tone detection 193
ignoring loop current 197
loop current drop 198
loop current off 197
messages 200
minimums
ports for Dialer 224
ring’s off period 200
ring’s on period 200
minmsg 200
minoff 200
minring 200
modems
bps rate 242
connecting computers 172
modes
Amanda Voice Server 48
modified_call_screening 201
msg_log 202
multiple_clients 225
MVIP streams 21
configuring 22
MVIP termination 23, 28
N
n_ani 235
n_clients 225
n_ochan 202
n_rings 229
n_winks 236
nam_maxlen 202
names
server 225
NEC 2000 234
serial integration 141
NEC 2400
serial integration 141
NEC MCI 234
NETMODE 48
network cards
installing 35
new installation
configuring 113
new_send 203
NIC cards
installing 35
NIC Configuration 245
non_relay_ok 203
notification
configuring 116
dedicated 118, 202
Max Times 241
restricted 118, 203
roving 118
Type 241
notification records
Ring No Answer 209
Notify Max Times 241
Notify Type 241
notify_restriction 203
O
off ring time 200
off hook
dial code 56
dl_pickup 56
off_dly 204
off-duty attendant 3
off-hook 204, 214
on ring time 200
on hold 186
on-hook 214
operator
after message 195
operators
mailboxes 120
options
special 226
P
packet
terminating characters
234
pager
problems with 241
parityn 230
partial_q_ok 204
partially supervised transfers
240
passwords 204, 210
configuring 115
patterns
integration 240
tone 239, 240
PBX 205
pbx 229
PBX.DB 51, 71
PBXs
ports for 229
using more than one 205
PC clock
synchronizing 188
PCPM 191, 197, 223
mailbox for 121
Index 257
peripheral
waiting for 215
physical
serial ports 230
play_from 205
play_new_first 206
play_skip 206
please_hold 206
port call accounting 187
resetting 237
SMDI 232, 233
port number
SMDI 233
ports
base I/O 25, 28
bps 230
COM1-COM4 231
company greetings 156
connecting 12, 30
data bits 230
direct messaging 166,
228
employee directories 165
greetings 227
idle 214
in use 199
initial volume 195
LPT 198
maximum 199
maximum for Amanda Di-
aler 224
message lights 118
minimum for Amanda Di-
aler 224
parity 230
printer 198
resetting 237
rings before answering
229
simultaneously off-hook
199
stop bits 231
using different PBXs 229
positive voice control 216,
217
time 218
post-record menu 194, 209
power conditioning 36
prefix
dial code 55
dl_prefix 55
primary attendant 3
printer
LPT port 198
printers
configuring 116
problems
new 237
product_activation_key 206
programming
special options 226
programs
Host/Remote 242
prompt
transferring caller to user’s
mailbox during
411 213
prompt_file 207
prompts
for recording 187
language 207
recording 209
sampling rates 185
protecting
Amanda 36
pulse 153
purge 207
purging
messages 207
purposes
Amanda 3
Q
questionnaire
first use 89
standalone version 91
voice server version 102
R
rcharacter code 83
ramdisk 207
rangex 208
rangex_key 208
RDSP 243
RDSP Not Located 242
RDSP/RTNI voice boards
installation checklist 17
RDSP/x000 boards
base I/O ports 25
requirements 19
RDSP/x000 voice boards
installing 32
installing MVIP cable 33
MVIPbuses 23
RDSP/x32
connecting ports 12
RDSP/x32 voice boards
installation checklist 7
read-only
mailboxes 189
recall
earth 208
recall_delay 208
receptionists
mailboxes 120
258 Installing Amanda@Work.Group
recognizing
loop current drop 198
loop current off 197
record
character code 83
record menu 209
record_menu 209
recording
dial tone 215
greetings 209
list comment 188
messages 194, 209
silence 215
stop 195, 215
records
locking 189
recursive_deletes 209
remote access
Amanda 167
remote computers
setting up 170
Remote program 242
REMOTE.COM 167
Reorder 68
repeating
menus 199, 214
reports
automatic 186
daily 186
requirements 1
RDSP/x000 voice boards
19
resetting
port 237
restricted notification 118
reviewing
messages 194
RHETDRV.EXE 243
Rhetorex
AccuCall Plus utility 62
busy notification 187
driver 218
options and defaults 193,
197, 198, 210
voice board 216, 217
voice board problem 243
voice boards 59
ring off period 200
on period 200
ring length 215
Ring No Answer 65
notification records 209
ring no answer
dial code 54
dl_rnaret 54
ring voltage 236
ring_mode 154, 155, 236
ring-no-answer
character code 83
rings
before answering port 229
rmt_rna 209
RNA chain 240
RNA greeting
played for integrated call
196
rotary 186, 210
digit detection 210
roving notification 118
RTNI-2T1 voice boards
installing 32
installing MVIP cable 33
RTNI-xATI
Amphenol 50-pin connec-
tor 30
connecting ports 30
MVIPbuses 28
RTNI-xATI boards
base I/O ports 28
line interface 29
RTNI-xATI voice boards
installing 32
installing MVIP cable 33
running
Setup 49
S
scharacter code 83
salesdealers 5
distribution 5
international 5
sampling rates
greetings 184
incoming messages 184
prompts 185
saving
messages 200
screen output 210
screen blanker 185
screen output
tracing 210
screen saver 185
configuring 116
starting 212
screen_save 210
screening
for caller 201
sec_code_display 210
secondary attendant 3
security codes
displaying 210
minimum length 211
security_min_length 211
Index 259
sending
faxes 133
messages 203
serial integration 135
Bellcore Standard 136
Definity-G3 144
Ericsson MD-110 146
generic 149
NEC 2000/2400 141
SMDI 136
System 75 144
serial ports
bps 230
COM1-COM4 231
data bits 230
logical 233
parity 230
physical 231
stop bits 231
serial_portn 231
servers
NETBIOS name 225
service 5
service_name 225
setting up
host computers 169
remote computers 170
Setup
defining dial codes 51
defining tone patterns 59
Setup utility 49
running 49
sharing Amanda 155
short_direct_send 211
shortening
system greeting 183
ShowJump 11, 31
shutdown 211
Amanda 49
configuring 116
dl_stop 56
shutting down 211
silence
when recording 215
SMDI 136
base port 232
characters in packet 232
integration 232
port 233
port number 233
terminating characters
234
time packet can precede
call 233
type 234
smdi_activation_key 232
smdi_base_port 232
smdi_delay 232
smdi_max 232
smdi_port 233
smdi_pretimeout 233
smdi_start 233
smdi_stop 233
smdi_term 234
smdi_type 234
SMDR 187
Software
installation 39
software upgrades 48
space
warning 190
Spanish 207
special
options 226
starting
screen saver 212
startup
dl_init 56
stopbitsn 231
stopping
recording 195, 215
streams
MVIP 21
MVIP configuration 22
stutter dial tone 239
suffix
dial code 55
dl_suffix 55
supervised transfer
please hold 206
supervised transfers 240
supervising
hangups 228
support 5
end user 5
installation 6
international 5
system administration 5
Token Programming Lan-
guage 6
synchronizing
DOS and PC clocks 188
system
log files 198
password 204
shutdown 49, 211
voice processing 3
System 75
serial integration 144
system administration
support 5
system dial codes
defining 51
system greeting
played for integrated call
196
shortening 183
260 Installing Amanda@Work.Group
system initialization
dl_init 56
system integration patterns
character codes 82
Integration Helper 85
test calls 86
system shutdown
dial code 56
dl_stop 56
system startup
dial code 56
dl_init 56
system tone patterns
defining 59
T
tcharacter code 84
T1 153
t1 lines 235, 236
t1_mode 236
tape_length 212
telephone lines
kinds 153
telephone switching systems
analog 239
templates
guest mailboxes 121, 196
mailboxes 121, 189
temporary
files 207
terminating
DTMF input 197
test calls
integration patterns 86
testing
inband integration patterns
73
timeafter DTMF entry 213
automatic reports 186
before integration 232
between disk space checks
213
between DTMF tones 193
between menu repetitions
214
between messages when
delivering list
198
between on-hook and off-
hook events 214
between SMDI packet and
call 233
continuous message play
212
DTMF tone detection 193
DTMF tones played 194
end of recording detected
215
for positive voice control
218
forwarded messages 212
hold between transfer at-
tempts 213
ignoring loop current 197
loop current drop 198
loop current off 197
messages 200
Name and Extension re-
cording 202
port is idle 214
recording a list comment
188
rewinding 206
screen saver starts 212
skipping forward 206
storing messages 207
wait for DTMF digit 191
waiting for peripheral 215
timeout
inband integration 214
timeouts
call screening 225
timers
tmo_blank 212
tmo_disk 213
tmo_dtmf 213
tmo_idle 214
tmo_menu 214
tmo_pickup 214
tmo_serial 215
tmo_silence 215
tmo_sound 215
tmo_xfer 191
timestamp
forwarded messages 212
timestamp_forwards 212
tmo_blank 212
tmo_call_screening 225
tmo_dir_transfer 213
tmo_disk 213
tmo_dtmf 213
tmo_dtwait 57
tmo_hold 213
tmo_idle 214
tmo_integrate 214
tmo_menu 214
tmo_pickup 214
tmo_rna 215
tmo_serial 215
tmo_silence 215
tmo_sound 215
tmo_xfer 191
today 183
Token Programming Language
support 6
tokens_available 216
Index 261
tone patterns 239, 240
AccuCall Plus 62
defining 59
running GetTones 59
tones
DTMF 191, 192, 193,
194, 195
for recording 187
PCPM 121, 197, 223
trace files 237
DTMF integration 72
inband integration 72
inband integration patterns
75
tracing
screen output 210
trademarks ii
transfer dial tone
dial code 54
dl_ndtret 54
transfer hold
dial code 53
dl_dtwait 53
please hold 206
transferring
blind 240
busy-hold time 213
call 238
from 411 to user’s mailbox
213
partially supervised 240
supervised 240
Troubleshooting
error messages 247
NIC Configuration 245
trunk
character code 84
Type
notification 241
typeSMDI 234
U
U token 240
uninstalling
Amanda 39
uninterrupted power supply 36
updating
Amanda 39, 48
upgrading
Amanda 48
UPS 36
urgent messages 217
urgent_to_front 217
use_pvc 217
use_tutorial 216, 217
user_log 218
users
messages for other users
205
usesAmanda 3
fraudulent iii
information system 4
off-duty attendant 3
primary attendant 3
secondary attendant 3
voice messaging center 4
using
fax modems 123
utilities
GetTones 59
Host/Remote 242
Setup 49
ShowJump 11, 31
V
verifying
caller still on line 194
voice board
problem 243
voice boards
addressing RDSP/x000
voice boards 19
addressing RDSP/x32
voice boards 8
addressing RTNI-xATI
boards 26
Brooktrout 217
clearing DTMF buffer
192
configuring RDSP/x000
voice boards 19
configuring RDSP/x32
voice boards 8
configuring RTNI-xATI
boards 26
installing MVIP cable 33
installing RDSP/RTNI
voice boards 32
installing RDSP/x32 voice
boards 11
jumpers for RDSP/x000
voice boards 20
jumpers for RDSP/x32
voice boards 9
jumpers for RTNI-xATI
voice boards 27
problem 243
Rhetorex 59, 62, 216,
217
voice boards, not from The
Amanda Company
183, 206, 232
voice control 216, 217
time 218
voice forms 204
262 Installing Amanda@Work.Group
voice mail
mailbox 120
voice messaging center 4
voice processing system 3
voice responses, storing 204
voice server
configuring 117
questionnaire 102
voice_analysis_length 218
VOICECNF.EXE 243
volume
custom busy message 195
initial 195
W
W token 241
waiting
before integration 232
for DTMF 191
for peripheral 215
warning
disk space 190
warranty ii
web site 5
wild card
character code 84
winks, t1 lines 236
X
xcharacter code 84
Y
yesterday 183

Navigation menu