AT&T Audix AMIS Analog - Networking

AMIS Analog Networking

585-300-512 Comcode 108413543 Issue 7 May 1999
Copyright 1999, Lucent Technologies All Rights Reserved, Printed in U.S.A.
Notice
Your Responsibility for Your System’s Security
Toll fraud is the unauthorized use of your tel ec ommunications system by an unauthorized party, for example, persons other than your com-
pany’s employees, agents, subcontractors, or persons working on your company’ s beh alf. Not e t hat t her e ma y be a ris k of toll f rau d ass oci at ed with your telecommunications system and, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services.
You and your system manager are responsible for the security of your system, such as programming and confi guring your equipment to pre­vent unauthorized use. The system manager is also responsibl e for reading all installation, instruc tion, and system administration doc u­ments provided with this pro duct in order to fully understand th e fe a­tures that can introduce risk of toll fraud and the steps that can be taken to reduce that risk. Lucent Technologies does not warrant that this product is immune fro m or will prevent unauthorized use of com­mon-carrier telecommun ic ation services or facili ti es accessed through or connected to it. Lucent Technologies will not be responsible for any charges that result from such unauthorized use.
Lucent Technologies Fraud I n tervention
If you suspect you are being victimized by toll fraud and you need technical support or assistance, call the appropriate BCS Nati ona l Cu s­tomer Care Center telephone number. Users of the MERLIN®, PART­NER®, and System 25 produc ts should call 1 800 628 2888. Users of the System 75, System 85, DEFINITY® Generic 1, 2 and 3, and DEFINITY® ECS produc ts shou ld call 1 800 643 2353. Customers outside the continental United States should contact their local Lucent representative, or call one of the above numbers in the following man­ner:
• Dial the International Access Code; for example, 011.
• Dial the co un try code for the U.S., that is, 01.
• Lastly, dial either of the telephone numbers provided above .
Lucent Technologies Web Page
The world wide web home pag e for Lucent Technologies is:
http://ww w.lucent .com
Federal Communica tions Commissi on S ta tement Part 15: Class A Statement. This equipment has been tested and
found to comply with the limits for a Class A digital device, pursua nt to Part 15 of the FCC Rules. These limits are design ed to provide rea­sonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interfer­ence to radio communications. Operation of this equipment in a resi­dential area is likely to cause harmful interference, in which case the user will be required to correct th e in te rfe re nce at his own expense.
Industry Canada (IC) Interference Information
This digital apparatus does no t exceed the Class A limits for radio noise emissions set out in the radio interference regulations of Industry Canada.
Le Présent Appareil Nomérique n’émet pas de bruits radioé le ctriques dépassant les limites applicables aux appareils numériques de la class A préscrites dans le reglement sur le brouillage radioélectrique édicté par le Industrie Canada.
Trademarks
See the preface of this docum e nt.
Ordering Information Call: Lucent Technologies BCS Publications Center
Voice 1 800 457-1235 International Voice 317 322-6791 Fax 1 800 457-1764 International Fax 317 322-6699
Write: Lucent Technologies BCS Publications Center
2855 N. Franklin Road Indianapolis, IN 46219
Order: Document No. 585-300-512
Comcode 10841354 3 Issue 7, May 1999
For additional documents, refer to the section in “About This Docu­ment” entitled “Related Resources.”
Y ou can be placed on a standing order list for this and other documents you may need. For more information on standing orders, or to be put on a list to receive fut ure i ssues of this d ocumen t, co ntac t the Luce nt Tech­nologies Publications Center.
Obtaining Products
To learn more about Lucent Technologies products and to order prod­ucts, contact Luce nt Direct, the direct-ma rket organization of Lucent Technologies Business Communications Systems. Access their web site at www.lucentdirect.com. Or call the fol lo w ing numbers: custom­ers 1 800 451 2100, account executiv es 1 888 778 1880 (voice) or 1 888 778 1881 (fax).
Warranty
Lucent Technologies provides a limited warranty on this product. Refer to the “Limited U s e S oftware License Ag reement” card provided with your package.
European Union Declaration of Conformity
The “CE” mark affixed to the equipment means that it conforms to the following directives. Lucent Technologies Business Comm unications Systems declares that DEFINITY AUDIX System equipment specified in this document conforms to the referenced European Union (EU) Directive s an d Harmonized Standards listed below: EMC Directive 89/336/EEC Low-Voltage Directive73/23/ EEC
Acknowledgment
This document was prepa re d by O M D Technical Publicati ons, Lucent Technologies, Denver, CO. and Columbus, OH.
AMIS Analog Networking
585-300-512

Contents

Contents
Contents iii About This Document ix
Purpose ix
Intended Audience ix
How This Document Is Organized x
Conventions Used xi
Related Resources xii
Trademarks and Servic e Mark s xii
How to Make Comments About This Document xiii
1 Overview 1-1
AMIS Analog Networking 1-2
AMIS One-Step and Two-Step Address ing 1-3
Issue 7
May 1999
iii
Subscriber Features 1-4
One-Step Addressing Features 1-4
Two-Step Addressing Summary 1-5 Types of Users 1-6 Feature Operation 1-7
Message Delivery 1-9
Subscriber Features 1-10 Types of Users 1-11 Feature Operation 1-12
Feature Enhancements by Release 1-14
AUDIX System Enhancements 1-14 DEFINITY AUDIX System Enhancements 1-15 Intuity System Enhancements 1-15
2 Planning and Design 2-1
Requirements 2-1
Software Requirements 2-1 Hardware Requirements 2-2 Voice Port Needs 2-2
Calculate Expected Voice Port Use 2-2
Monitor Voice Port Use 2-3
Security 2-4
AMIS Analog Networking
Contents
Network Design 2-5
Designing an AMIS Analog/Message Delivery Network 2-5
Defining Address Ranges 2-10
AMIS Prefix 2-10
Address Prefixes 2-10
Overlapping or Duplicate Ranges 2-12
Extension Ranges and Length 2-12
Dial String Interaction 2-13
Sample Network Design 2-14
Network Planning 2-16
Collect Local Machine Information 2-16 Collect Remote Machine Inform atio n 2-19 Collect Remote Subscriber Information 2-21
585-300-512
Issue 7
May 1999
iv
3 AUDIX Administration 3-1
Implementation 3-2
Task 1: Display the Local Machine 3-3 Task 2: Administer AMIS Loopback Test
Mailbox (Optional) 3-6 Task 3: Administer AMIS Analog/Message
Delivery Parameters 3-7 Task 4: Administer Outcalling Periods 3-12 Task 5: Adjust System Limits 3-14
Task 5A: Calculate New Filesystem Sizes 3-14
Task 5B: Compare the Recommended Sizes
to the Actual Sizes 3-16
Task 5C: Increase Filesystem Sizes 3-17 Task 6: Administer Retransmission Intervals 3-18 Task 7: Restart the AUDIX System 3-19 Task 8: Administer Remote Machines/Telephone
Numbers 3-20 Task 9: Record Remote Machine Names
(Optional) 3-32 Task 10: Administer Remote Subscribers
(Optional) 3-33 Task 11: Record Remote Subscriber Names
(Optional) 3-35 Task 12: Test the Connection 3-36
AMIS Analog Networking
Contents
585-300-512
Task 12A: Testing an AMIS Analog Connection 3-36
Task 12B: Testing a Message Delivery
Connection 3-37
Ongoing Administration 3-38
Educate Subscribers 3-38 Maintain the Network 3-38 Monitor Logs and Traffic Reports 3-38
4 DEFINITY AUDIX Administration 4-1
Implementation 4-2
Task 1: Verify AMIS Service 4-3 Task 2: Display the Local Machine 4-4 Task 3: Administer Loopback Test Mailbox
(Optional) 4-5 Task 4: Administer AMIS Analog/Message
Delivery Parameters 4-5
Issue 7
May 1999
v
Task 5: Administer Outcalling Periods 4-9 Task 6: Adjust System Limits 4-12 Task 7: Administer Retransmission Intervals 4-14 Task 8: Activate the Changes 4-15
Task 8A: Reboot the System (R1.0) 4-15
Task 8B: Run Audits (R2.0 and Later) 4-16 Task 9: Administer Remote Machines/Telephone
Numbers 4-17 Task 10: Record Remote Machine Names
(Optional) 4-28 Task 11: Administer Remote Subscribers
(Optional) 4-29 Task 12: Record Remote Subscriber Names
(Optional) 4-30 Task 13: Test the Connection 4-31
Task 13A: Testing an AMIS Analog Connection 4-32
Task 13B: Testing a Message Delivery
Connection 4-33
Ongoing Administration 4-33
Educate Subscribers 4-33 Maintain the Network 4-34 Monitor Logs and Traffic Reports 4-34
AMIS Analog Networking
585-300-512
Contents
5 Intuity System AMIS Administration 5-1
Checking and Activating the AMIS
Analog Networking Feature 5-3
Local Machine Administration 5-5
Check the Local Machine Administration on the Intuity Platform 5-5
Check the Local Machine Administration on the Intuity AUDIX Voice Messaging Feature Package 5-8
Administer Loopback Test Mailbox (Optional) 5-10
Administer AMIS Analog/Message
Delivery Parameters 5-11
Administer the Outcalling Periods 5-15
Adjust the System Limits 5-17
Administer Retransmission Intervals 5-19
Activate the Changes 5-21
Restart the AUDIX Voice System 5-21
Issue 7
May 1999
vi
AMIS Remote Machine Administration 5-23
Administer AMIS Remote Machines on the Intuity Platform 5-24
Administer AMIS Remote Machines on the AUDIX Voice Messaging Feature Package 5-28
Enter the Address Ranges for the Remote
Machine 5-32
Record Remote Machine Names (Optional) 5-36
Administer Remote Subscribers (Optional) 5-39
Record Remote Subscriber Names (Optional) 5-41
Test the Connection 5-42
AMIS Analog Network Connection Test 5-42 Message Delivery Connection Test 5-43
Ongoing Administration 5-44
Educating Subscrib ers 5-44 Maintain the Network 5-44 Monitor Logs and Traffic Reports 5-45 Changing Remote AMIS Machine Information on
the Intuity Platform 5-45 Changing Remote AMIS Machine Information on
the AUDIX Voice Messaging Feature Package 5-46
AMIS Analog Networking
Contents
585-300-512
Deleting Remote Machines 5-47 Renaming a Remote AMIS Machines 5-48
Administration Examples 5-50
AMIS Casual Addressing to Local Numbers Example 5-50
AMIS Pre-Administered Addressing to Specific Machines Example 5-52
AMIS Message Delivery Addressing to Local Number Exam ple 5-54
A Administration Log Entries A-1 B Administration Forms Summary B-1 C Subscriber Operation C-1
AMIS Analog Networking Examples C-1
One-Step AMIS Addressing C-1 Two-Step AMIS Analog Networking Example C-5
Message Delivery Example C-6
Issue 7
May 1999
vii
Template Letter for Using the AMIS
Analog Networking and Message Delivery Features C-9
AMIS Analog Networking C-9
Using AMIS Analog One-Step Addressing C-10
Using AMIS Analog Two-Step Addressing C-11 Message Delivery C-11
Addressing Message Delivery Messages to
Individual Recipients C-12
Addressing Message Delivery Messages to a
Number in an Administered Range C-13
ABB Abbreviations ABB-1 GL Glossary GL-1 IN Index IN-1
AMIS Analog Networking
Contents
585-300-512
Issue 7
May 1999
viii
AMIS Analog Networking

About This Document

585-300-512 Issue 7
About This Document

Purpose

May 1999
ixPurp ose
This document, planning, administering, and using the Audio Messaging Interchange Specification (AMIS) Analog Networking and Message Delivery features on the following Lucent Technologies voice messaging system:
AUDIX R1V6, R1V7, and R1V8 systems
DEFINITY AUDIX systems
Intuity systems
Information is organized and presented in a user-oriented manner and allows easy access and retrieval of the information.

Intended Audience

The document is intended for anyone who administers one or more Lucent Technologies voice messaging systems for the AMIS Analog Networking and Message Delivery features.
AMIS Analog Networking,
585-300-512, provides procedures for
AMIS Analog Networking
About This Document
585-300-512 Issue 7

How This Document Is Organized

This document is organized into the following chapters:
About This Document
This preface describes the document’s purpose, intended audiences, organization, conventions, trademarks and service marks, and related resources. This preface also explains how to make comments about the document.
Chapter 1, "Overview"
This chapter describes the AMIS Analog Networking and Message Delivery features.
Chapter 2, "Planning and Design"
This chapter contains hardware and software requirements, security issues, and network planning procedures.
Chapter 3, "AUDIX Administration"
May 1999
xHow This Document Is Organized
This chapter describes the administration and testing of the AMIS Analog Networking and Message Delivery features on an AUDIX R1V6 or later system.
Chapter 4, "DEFINITY AUDIX Administration"
This chapter describes the administration and testing of the AMIS Analog Networking and Message Delivery features on a DEFINITY AUDIX system.
Chapter 5, "Intuity System AMIS Administration"
This chapter describes the administration and testing of the AMIS Analog Networking and Message Delivery features on an Intuity system.
Appendix A, "Administration Log Entries"
This appendix provides AMIS Analog Networking and Message Delivery administration error codes and resolution procedures.
Appendix B, "Administration Forms Summary"
This appendix summarizes the forms used for Lucent Technologies voice messaging systems for AMIS Analog Networking and Message Delivery administration.
Appendix C, "Subscriber Operation"
This appendix describes the procedures subscribers would use to send AMIS Analog Networking and Message Delivery messages. The appendix includes a template letter you can customize and distribute to the subscribers to inform them about the AMIS features.
Abbreviations
This section provides a list of abbreviations and acronyms used in the document.
AMIS Analog Networking
About This Document
Glossary
The Glossary provides a definition of terms and acronyms used in the document.
Index
The Index provides an alphabetical listing of principal subjects covered in this document .

Conventions Used

The following conventions were used in this document:
Rounded boxes represent keyboard keys that you press.
For example, an instruction to press the enter key is shown as
585-300-512 Issue 7
May 1999
xiConventions Used
Press .
Square boxes represent phone pad keys that you press.
ENTER
For example, an instruction to press zero on the phone pad is shown as Press .
The word “enter” means to type a value and press .
For example, an instruction to type y and press is shown as
0
ENTER
ENTER
Enter y to continue.
Two or three keys that you press at the same time (that is, you hold down
the first key while pressing the second and/or third key) are shown as a rounded box that contains two or more words separated by hyphens. For example, an instruction to press and hold while typing the letter d is
ALT
shown as Press
Commands and text you type or enter appear in bold.
Values, instructions, and prompts that you see on the screen appear as
follows:
Variables that the system supplies or that you must supply appear in
italics
ALT-d
Press any key to continue.
.
For example, an error message including one of your filenames appears as
The file
filename
is formatted incorrectly
AMIS Analog Networking
585-300-512 Issue 7
About This Document

Related Resources

In addition to this document, you may need to reference additional documents about your voice mail system. F or a li st of documents related to your system, see the Lucent Technologies Product Publications Catalog website at www.lucent.com/enterprise/documentation.

Trademarks and Service Marks

The following trademarked products are mentioned in the books in the INTUITY library:
AT™ is a trademark of Hayes Microcomputer Products, Inc.
AUDIX® is a registered trademark of Lucent Technologies.
BT-542B™ is a trademark of BusLogic Inc.
COMSPHERE® is a registered trademark of Paradyne Corp.
CONVERSANT® is a registered trademark of Lucent Technologies.
May 1999
xiiRelated Resources
DEFINITY® is a registered trademark of Lucent Technologies in the U.S.
and throughout the world.
Dterm™ is a trademark of NEC Telephones, Inc.
Equinox™ is a trademark of Equinox Systems, Inc.
5ESS® is a registered trademark of Lucent Technologies.
INTUITY™ is a trademark of Lucent Technologies.
MD110® is a registered trademark of Ericsson, Inc.
MEGAPLEX™ is a trademark of Equinox System, Inc.
MEGAPORT™ is a trademark of Equinox Systems, Inc.
Meridian™ is a trademark of Northern Telecom Limited.
MERLIN LEGEND® is a registered trademark of Lucent Technologies.
Microcom Networking Protocol® is a registered trademark of Microcom,
Inc.
Microsoft® is a registered trademark of Microsoft Corporation.
MS® is a registered trademark of Microsoft Corporation.
MS-DOS® is a registered trademark of Microsoft Corporation.
NEAX™ is a trademark of NEC Telephone, Inc.
NEC® is a registered trademark of NEC Telephones, Inc.
Netware® is a registered trademark of Novell, Inc.
Netware® Loadable Module™ is a trademark of Novell, Inc.
AMIS Analog Networking
About This Document
NLM® is a registered trademark of Novell, Inc.
Northern Telecom® is a registered trademark of Northern Telecom
Limited.
Novell® is a registered trademark of Novell, Inc.
ORACLE™ is a trademark of Oracle Corporation.
Paradyne® is a registered trademark of Paradyne Corp.
Phillips® is a registered trademark of Phillips Screw Company.
Rolm® is a registered trademark of International Business Machines.
SL-1™ is a trademark of Northern Telecom Limited.
softFAX® is a registered trademark of VOXEM, Inc.
TMI™ is a trademark of Texas Micro Systems, Inc.
UNIX® is a registered trademark of Novell in the United States and other
countries, licensed exclusively through X/Open Company Limited.
VOXEM® is a registered trademark of VOXEM, Inc.
585-300-512 Issue 7
May 1999
xiiiHow to Make Comments About This Document
VT100™ is a trademark of Digital Equipment Corporation.
Windows™ is a trademark of Microsoft Corporation.

How to Make Comments About This Document

We are interested in your suggestions for improving this document. Please send your comments and suggestions to:
Luc ent Technologies OMD Technical Publications Room 22-2X57 11900 North Pecos Street Denver, Colorado 80234
Send email comments to:
octeltechpubs@lucent.com
AMIS Analog Networking
About This Document
585-300-512 Issue 7
May 1999
xivHow to Make Comments About This Document
AMIS Analog Networking

Overview

1
Overview
The Audio Messaging Interchange Specification (AMIS) Analog Networking feature permits subscribers to exchange voice mail messages with voice messaging systems anywhere in the world, provided those systems also have AMIS analog networking capabilities. The Message Delivery feature permits subscribers to send recorded messages to any touch-tone telephone, anywhere
in the world (including someone’s home).
585-300-512 Issue 7
May 1999
1-1
1
Both features are sold together in a single package. The AMIS Analog Networking and Message Delivery features must be activated by Lucent Technologies personnel before customers can implement them.
General considerations related to the AMIS Analog Networking and Message Delivery features include:
The
Messages are
Message Sending Restrictions
Analog Networking and/or Message Delivery calls to specified remote machines (numbers) or user communities. This helps the system administrator prevent unnecessary outcalls and control unauthorized long-distance calls. For more information about voice mail system security, refer to the appropriate administration manual for your system.
example, it takes a full minute for the local system to play a one-minute message. Because messages are transmitted over analog lines, their quality may degrade.
GBCS Products Security Handbook,
played
to the remote machine or message recipient; for
feature can be used to limit AMIS
555-025-600, or the

AMIS Analog Networking

Overview
1
The AMIS Analog Networking feature, Message Delivery feature, and
Outcalling feature all share the outcalling message-transmission queue and the outcalling ports administered for the system. The message transmission schedule administered for AMIS Analog and Message Delivery messages to be delivered must be equal to or a subset of the outcalling periods administered on the system, or the messages will not be transmitted. Further considerations for outcalling port use are covered in Chapter 2, "Planning and Design"
The maximum number of messages that can be stored in the shared AMIS/message delivery/outcalling queue is 250. If the transmission queue reaches 250 messages, no more messages are delivered to the queue until the messages in the queue are transmitted (they remain in the
sender’s outgoing mailbox in the
The AMIS Analog Networking and Message Delivery feature description, use, and operation are described in the following sections. A summary of feature enhancements between various software releases appears at the end of this chapter.
585-300-512 Issue 7
undelivered
category).
May 1999
1-2AMIS Analog Networking
AMIS Analog Networking
AMIS analog networking allows remote or disparate voice mail systems to literally “talk” to each other. Because the AMIS protocol is an industry standard, messages can be exchanged with users on Lucent Technologies voice mail systems or on systems made by vendors other than Lucent Technologies. The only restriction is that both systems have AMIS analog networking capabilities.
The AMIS Analog Networking feature is especially useful to the following customers:
AUDIX system customers who wish to exchange voice mail messages
with DEFINITY AUDIX systems, Intuity systems, or with non-Lucent Technologies voice messaging systems that cannot be digitally networked. The AUDIX system supports both digital networking and AMIS analog networking. Both types of networking may be used on the same machine.
DEFINITY AUDIX system customers who wish to exchange voice mail
messages with AUDIX systems, other DEFINITY AUDIX systems, Intuity systems, or with non-Lucent Technologies voice messaging systems. The DEFINITY AUDIX system currently relies upon AMIS analog networking for all its networking functions.
Intuity syst em customers wh o wish to ex change voice mail messages with
AUDIX systems, DEFINITY AUDIX systems, other Intuity systems, or with non-Lucent Technologies voice messaging systems. The Intuity system supports both digital networki ng and AMIS a na lo g networ king. Both t y pes of networking may be used on the same machine.
AMIS Analog Networking
Overview
1
Other considerations related to the AMIS Analog Networking feature include:
An Lucent Technologies voice mail system using AMIS analog networking
can exchange messages with capabilities as long as the remote machine is defined on the local voice mail system. AMIS messages can alternatively be sent to a administered remote machines (for example, all machines in a specific area code or all local numbers). However, system administrators should take precautions when administering a range of machines to prevent unauthorized long-distance calls or minimize excessive port use (see the
"Security" section in Chapter 2, "Planning and Design"
585-300-512 Issue 7
any
voice mail system that has AMIS analog
range
May 1999
1-3AMIS Analog Networking
of
Messages are
played
to the recipient’s system; for example, it takes one full minute for the receiving system to record a one-minute message. If the same message is being delivered to more than one recipient on the same remote machine, the local system plays the message one time for each intended recipient. Because messages are transmitted over analog lines, their quality may degrade.
The AMIS analog specification allows the local voice mail system to send
up to nine AMIS messages per call to an individual remote system. For example, if several AMIS messages have been delivered to the outcalling message queue for delivery, the local system calls the remote s ystem
once
and plays out up to nine AMIS messages during that call. If any messages beyond the first nine are left in the queue, the local system calls the remote system again to transmit any additional AMIS messages it may have qu eue d.

AMIS One-Step and Two-Step Addressing

The system administrator may administer remote AMIS voice mail systems for one-step (
The “steps” refer to the way local subscribers address messages to remote recipients. For machine’s prefix (if assigned), followed by the recipient’s mailbox ID and the key. In followed by the telephone number of the remote machine, followed by the key. They are then prompted to enter the extension (mailbox ID) for the intended recipient, followed by another .
pre-adminis tered
one-step
two-step
addressing, subscribers first enter the prefix (if assigned),
) or two-step (
addressing, subscribers typically enter the remote
#
casual
) addressing.
#
#
One-step versus two-step addressing also has implications for the system administrator. One-step addresses are easier for subscribers to enter and may take advantage of many Lucent Technologies voice mail conveniences (see the following " Subscriber Features" section). To use one-step addressing, the system administrator only needs to pre-administer the machine. However, the administrator may also wish to administer remote subscribers to allow name addressing and name voiceback.
AMIS Analog Networking
Overview
1
585-300-512 Issue 7
Two-step addressing is often easier for the system administrator to implement because only the remote voice mail system (or range of remote systems) needs to be administered. For example, a range of remote systems could be administered for two-step addressing (for instance, an entire area code or all local telephone numbers) without needing to administer each remote system individually (as must be done for one-s tep addre ssing) . SeeChapter 2, "Planning
and Design" for additional considerations when planning AMIS addressing
schemes.

Subscriber Features

Subscriber features related to AMIS analog networking are summarized below. Refer to Appendix C, "Subscriber Operation" for examples of one-step and two-step addressing. This appendix also includes a template letter that can be customized to introduce subscribers to the features available at their site.
One-Step Addressing Features
For
one-step
prefix (if assigned), followed by the recipient’s mailbox ID and the key. However, subscribers who wish to send AMIS messages to recipients on remote systems administered for one-step addressing can also take advantage of the following features.
addressing, local subscribers typically enter the remote machine’s
May 1999
1-4AMIS Analog Networking
#
Address-by-Name
name addressing
Mailing Lists:
: Local subscribers can address AMIS messages using
only
for administered remote recipients.
Local subscribers can include remote recipients on any system administered for AMIS one-step addressing in their personal mailing lists. Administered remote recipients can be included by name or telephone number; non-administered remote recipients can be included only by telephone number. (See the following "Types of Users" section for a description of administered and non-administered remote recipients.)
Name Voiceback:
Local subscribers hear the name of administered remote recipients they are addressing or looking up in a directory the system administrator has voiced-in the name of that remote recipient. Otherwise, they hear the remote mailbox ID.
Names-and-Numbers Directory:
Local subscribers can look up administered remote subscribers on systems administered for AMIS one-step addressing using the local system’s names-and-numbers directory ( ).
* *
N
only
if
AMIS Analog Networking
Overview
1
Personal Directory:
585-300-512 Issue 7
recipients on systems administered for AMIS one-step addressing. Administered remote recipients can be included by name or telephone number; non-administered remote recipients can be included only by telephone number.
Reply to Sender:
messages using the Reply to Sender feature to supply automatic addressing. This feature works for all one-step administered remote subscribers.
Two-Step Addressing Summary
Subscribers who wish to send AMIS messages to recipients on remote systems
administered for two-step addressing must enter the recipient’s address in two steps. During the first step, local subscribers enter the prefix (if assigned), followed by the telephone number of the remote machine, followed by the key. At this point they may hear the name of the remote system voiced back (if the system administrator has recorded a name for that machine or range of machines). The system then prompts subscribers to enter the extension (mailbox ID) for the intended recipient, followed by another key. Subscribers will hear the digits voiced back to confirm they entered the correct extension number (recipient name voiceback is not available on systems administered for two-step addressing).
May 1999
1-5AMIS Analog Networking
Local subscribers can assign aliases to any remote
Local subscribers can respond to incoming AMIS
#
#
The headers of AMIS analog messages delivered to recipients on two-step remote systems differ slightly from standard voice mail or one-step AMIS messages. The two-step message header first states that the message is an AMIS message. Next, the system voices (typically) the complete telephone number of the remote voice mail system, followed by the mailbox ID of the person who sent the message. The sender’s name is not voiced for two-step messages.
NOTE:
AMIS recipients on remote systems administered for AMIS two-step addressing cannot be addressed by name or included in subscribers’ mailing lists or personal directories, nor are they included in the local system’s names-and-numbers directory. The name voiceback and Reply to Sender features also are not available.
AMIS Analog Networking
Overview
1

Types of Us ers

Users of the AMIS Analog Networking feature are divided into the following groups:
Local subscribers:
Lucent Technologies voice mail system. Unless restricted through the Message Sending Restrictions feature, all local subscribers are capable of sending AMIS messages.
Remote voice mail recipients:
remote voice mail system (any system other than the local system). Remote recipients are divided as follows:
585-300-512 Issue 7
May 1999
1-6AMIS Analog Networking
Voice mail users whose mailboxes reside on the local
AMIS users whose mailboxes reside on a
Administered remote subscribers:
Those remote users who have been administered on the local voice mail system. These recipients can be addressed by name and their names, if recorded, are voiced back. Only AMIS recipients whose mailboxes reside on systems administered for AMIS one-step addressing can be administered on the local system.
Non-administered remote recipients:
Remote users who have not been administered on the local voice mail system. All users on remote systems administered for AMIS two-step addressing are non-administered remote recipients. Remote users on systems administered for AMIS one-step addressing may be administered or non-administered (the system administrator indicates whether local subscribers can send messages to non-administered remote recipients when administering each remote system).
Non-administered remote recipients are further divided as follows:
Non-verified non-administered remote recipients:
Those non-administered remote users who have been addressed in an AMIS message, but a successful delivery has not yet occurred.
Verified non-administered remote recipients:
Those remote users who have either successfully received an AMIS message delivered by the local system, or who have successfully delivered an AMIS message to the local system.
AMIS Analog Networking
Overview
1

Feature Operation

The AMIS Analog Networking feature operates as follows:
1. A local subscriber either records a new voice mail message, forwards an existing call answer or voice mail message, or retrieves a mess age saved
in the subscriber’s outgoing mailbox.
2. When prompted for the recipient’s extension, the subscriber enters one of the follo win g, depending on the type of AMIS a ddressing administered on the system:
585-300-512 Issue 7
For AMIS one-step addressing:
Subscribers enter the AMIS and/or
May 1999
1-7AMIS Analog Networking
address prefix (if assigned), followed by the remote mailbox ID (typically the extension) of the intended recipient, followed by the
#
key.
NOTE:
Administered remote recipients can alternatively be addresse d by na me (last-name- first). All recipients on remote systems administered for one-step addressing may be included in local subscribers’ mailing lists or personal directories as long as they are specified by extension number.
For AMIS two-step addressing:
— When prompted for the recipient’s extension, the subscriber
enters the AMIS and/or address prefix (if one is assigned), followed by the full telephone number of the remote voice mail system (an area code, or country code plus area code, may be necessary), followed by the key.
#
— The system prompts the subscriber for the extension
(mailbox ID) of the intended recipient on the remote system. The subscriber then enters the appropriate digits, followed by the key.
Subscribers can add other local or remote addresses, then
#
approve the message for delivery as described in the quick-reference card for their voice mail system.
NOTE:
Messages designated as messages designated as
private
priority
will not be delivered. AMIS
wi ll be de l i ver ed, bu t a ppe a r as regular messages to the remote system. Subscribers may optionally specify a time when they want the message delivered; if they do, the local system delivers the message to the AMIS transmission queue at the requested delivery time, but the message may not be transmitted until the next administered outcalling period.
AMIS Analog Networking
Overview
1
3. At the first available transmission period, the local system attempts to call the remote voice mail system as follows:
— If the message arrives during an active transmission period, the
— If a port is available but the local system for some reason cannot
4. When the remote system answers the call and is ready to record, the local voice mail system plays the message. The remote system delivers the recorded message to the appropriate recipient’s mailbox.
585-300-512 Issue 7
May 1999
1-8AMIS Analog Networking
system attempts to make the outcall immediately. If the maximum number of simultaneous outcalling resources is busy, the system tries again in one mi nute.
deliver the AMIS message, the system makes two more attempts to deliver the AMIS message. The intervals at which the system tries to deliver messages are specified by the system administrator.
NOTE:
Because AMIS analog messages are actually played to the remote system and not transmitted digitally, the remote system takes one minute to record a one-minute message. If a message is sent to more than one subscriber on the same remote system, it is played to the remote system multiple times.
5. After the message is delivered successfully, the local voice mail system updates the outgoing message status to
delivered
. If all delivery attempts fail, the local system sends a new voice mail message to the sender notifying him or her that the message was undeliverable. The message is saved in the sender’s outgoing mailbox so the subscriber can attempt to send it again if desired. The header in the outgoing mailbox contains a more detailed explanation of why the message was not deliverable.
6. The remote recipient retrieves the AMIS analog message using the same method used for any other voice mail or call answer messages they receive. The header identifies the message as an
AMIS
message (in two-step addressing only) and provides the name (for administered remote subscribers only) or the telephone number and extension of the sender.
AMIS Analog Networking
Overview
1

Message Delivery

Message Delivery is an optional feature that permits subscribers to send recorded messages to any touch-tone telephone, anywhere in the world
(including someone’s home), as long as that telephone number is in the range of allowable numbers defined by the system administrator. This feature is an extension of the AMIS Analog Networking feature and is automatically available when the AMIS feature is activated.
After a subscriber addresses a Message Delivery message, the local system places the message in the outcalling queue for delivery during the interval(s) defined by the system administrator. The system makes a total of six attempts to deliver the message. If the recipient doesn’t answer by the sixth attempt, the system sends the sender a new voice mail message informing him or her that the message was undeliver able. The messa ge is s ave d in the subs criber’s outgoing mailbox so it may be redelivered.
When the system makes a Message Delivery call to the designated number and the phone is answered, a recording states that a message is waiting and that the intended recipient should press to hear it. When the listener presses , the local system plays the message. Recipients may alternatively press to delete the message instead of listening to it (for example, if they already know what the message is about and do not wish to hear it). They may also press
D
to delete the message after listening to it, although the system automatically
deletes an accessed message after the listener hangs up.
585-300-512 Issue 7
0 0
May 1999
D
*
1-9Message Deliver y
*
The system administrato r can individually administer any telephone num bers to which Message Delivery traffic is heavy. This allows subscribers to use name addressing and hear name voiceback (if the system administrator records a name for this recipient).
The system administrator can also administer a
range
of Message Delivery telephone numbers (for example, all local phone numbers or an entire area code). In this case, individual recipients’ numbers do not need to be administered on the local voice mail system. However, system administrators should take precautions when administering a range of numbers to prevent unauthorized long-distance calls and to minimize excessive port use (see the
"Security" section in Chapter 2, "Planning and Design").
AMIS Analog Networking
Overview
1
Other considerations related to the Message Delivery feature include:
Recipients may be individually administered on the local system so
subscribers can address them by name and receive name voiceback.
However, any Message Delivery recipient can be included in subscriber’s mailing lists and personal directories if the complete telephone number is used.
585-300-512 Issue 7
May 1999
1-10Message Delivery
Messages are
minute message, an outcalling port will be busy for at least one minute.
If a Message Delivery message is sent to a remote recipient and a
non-Lucent Technologies voice mail system or an answering machine picks up the call, the recipient’s machine may record the message header. (A remote Lucent Technologies voice mail system does the header.) The remote machine is not able to record the message body because it cannot press to have the local system play out the message. However, from the header, recipients will hear either the name or number of the person who sent the message when they next pick up their messages. Meanwhile, the local system continues trying to deliver the message (up to a total of six attempts) because it did not detect a touch-tone indicating the message was received.

Subscriber Features

To send a Message Delivery message, local subscribers enter an address prefix (if one was assigned) to identify the message as a Message Delivery message. They then enter the complete telephone number for the recipient, followed by the
#
key. At this point, if the system administrator has recorded a name for the recipient, they should hear the recipient’s name voiced back. If no name has been recorded, subscribers hear the digits voiced back to confirm the telephone number they just entered.
played
to the recipient; if a recipient is listening to a one
not
record
0
Subscribers may also take advantage of the following voice mail features for sending Message Delivery messages. Refer to Appendix C, "Subscriber
Operation"
,
for examples of Message Delivery addressing. This appendix includes a template letter that can be customized to introduce subscribers to the feature.
Address-by-Name:
messages using name addressing
Local subscribers can address Message Delivery
only
for administered remote
recipients.
Mailing Lists:
Local subscribers can include any Message Delivery remote recipients in their personal mailing lists. Administered remote recipients can be included by name or extension number; non-administered remote recipients can be included only by extension number. (See the following
"Types of Users" section for a description of remote recipient types.)
AMIS Analog Networking
Overview
1
Name Voiceback:
remote recipients they are addressing or looking up in a directory the system administrator has voiced-in the name for that remote recipient. Otherwise, they hear the remote telephone number.
Names-and-Numbers Directory:
administered remote recipients using the local system’s names-and-numbers directory ( ).
Personal Directory:
Message Delivery recipients. Administered remote recipients can be included by name or extension number; non-administered remote recipients can be included only by extension number.

Types of Us ers

Users of the Message Delivery feature are divided into the following groups:
Local subscribers:
Lucent Technologies voice mail system. Unless restricted through the Message Sending Restrictions feature, all local subscribers are capable of sending Message Delivery messages.
585-300-512 Issue 7
May 1999
1-11Message Delivery
Local subscribers hear the name of administered
only
if
Local subscribers can look up
N
* *
Local subscribers can assign aliases to any remote
Voice mail users whose mailboxes reside on the local
Recipients:
Recipients
Those people who can receive Message Delivery messages.
must
have a touch-tone telephone. All Message Delivery recipients can be addressed by complete telephone number and may be included in local subscribers’ mailing lists and personal directories. Recipients are further divided as follows:
Adm ini st ered reci pients :
Those remote recipients who have been administered on the local voice mail system. These recipients can be addressed by name and their names, if recorded, are voiced back to local subscribers.
Non-administer ed recipients:
Those remote recipients who have
been administered on the local voice mail system.
not
AMIS Analog Networking
Overview
1

Feature Operation

The Message Delivery feature operates as follows:
1. A local subscriber either records a new voice mail message, forwards an existing call answer or voice mail message, or retrieves a mess age saved
in the subscriber’s outgoing mailbox.
2. When prompted for the recipient’s extension, the subscriber enters one of the following, depending on how Message Delivery recipients have been administered on the local system:
585-300-512 Issue 7
May 1999
1-12Message Delivery
— If the recipient’s number is in a valid
range
of administered telephone numbers but the recipient is not individually administered, the subscriber typically enters an address prefix (if one was assigned), followed by the full telephone number of the recipient (a country code and/or area code may be necessary), followed by the key.
#
— If the recipient is individually administered, the subscriber typically
enters an address prefix (if one was assigned), followed by as much of the recipient’s telephone number as is needed for a unique address, followed by the key. Administered recipients may
#
alternatively be addressed by name (last-name-first).
3. Subscribers can add other local or remote addresses, then approve the message for delivery as described in the quick-reference card for their voice mail system.
NOTE:
Messages designated as designated as
priority
private
will not be delivered. Messages
will be delivered, but a ppear as regular messages to the recipient. Subscribers may optionally specify a time when they want the message delivered; if they do, the system delivers the message to the outcalling transmission queue at the requested delivery time, but the message may not be transmitted until the next administered outcalling period.
4. At the first available transmission period, the system attempts to deliver the Message Delivery message as follows:
— If the message arrives during an active transmission period, the
system attempts to make the outcall immediately. If the maximum number of simultaneous outcalling resources is busy, the system tries again in one mi nute.
— If an outcalling port is available but the local system cannot deliver
the message (no one pressed ), the system makes five more
0
attempts to deliver the message. The intervals at which the system tries to deliver messages are specified by the system administrator.
AMIS Analog Networking
D
Overview
1
5. When the system makes a Message Delivery call to the designated number and the phone is answered, a recording states that a message is waiting and that the intended recipient should press to hear it. (If a non-Lucent Technologies system or answering machine answers the call, it may record this part of the message, including the name or telephone number of the sender.)
6. Listeners may take one of the following actions:
585-300-512 Issue 7
May 1999
1-13Message Delivery
0
— Listeners can press to hear the message. Afterwards, they may
press to delete the message or simply hang up (in the latter case, the system will delete the message for them).
D
*
— Listeners may press to delete the message without listening
to it (for example, if they already know what the message is about and do not wish to hear it). Pressing ensures the system will not call them again with this same message.
0
*
D
*
7. After the message is delivered successfully, the local voice mail system updates the outgoing message status to
delivered
. If all delivery attempts fail, the local system sends a new voice mail message to the sender notifying him or her that the message was undeliverable. The message is saved in the sender’s outgoing mailbox so the subscriber can attempt to send it again if desired. The header in the outgoing mailbox contains a more detailed explanation of why the message was not deliverable.
AMIS Analog Networking
Overview
1
585-300-512 Issue 7

Feature Enhancements by Release

The AMIS Analog Networking and Message Delivery features have been enhanced since their initial introduction for various Lucent Technologies voice messaging software releases. These enhancements are summarized in this section.

AUDIX System Enhancements

The AMIS Analog Networking and Message Delivery features have been enhanced since the initial AUDIX R1V6 software release as follows. Any enhancements made for a given release are carried forward to later releases.
R1V7
— The send to non-administered recipients (y/n)? field moved from
system:appearance
the
system:translation:machine:audix/amis/call
the R1V7 7:1 software release to make feature administration more flexible.
R1V7 7:2
— Several enhancements were made to the AMIS Analog Networking feature in the 7:2 software release. These changes, summarized below, are fully documented in the
7:2 Change Description,
form in AUDIX R1V6 software to the
585-306-402.
May 1999
1-14Feature Enhancements by Release
delivery form in
AUDIX R1V7 Issue 7:1 to
— A country code of “0” was added to allow the AUDIX system to
work in a mixed-vendor environment over private networks in any country.
— Any messages remaining in the outcalling queue after an initial
transmission are transmitted within 2 minutes after the first nine are sent.
— Enhanced pre-administered machine processing improved the
performance of the Reply to Sender and name voiceback features.
— Additional administration log entries and improved error messages
were added to benefit subscribers and system administrators.
R1V8
— Multiple callback numbers were added to allow more flexible AMIS operation in mixed public/private networks. Up to five callback numb er s can be speci fie d on the
analog network
form. Callback numbers are assigned to remote
system:translation:machine:
machines using the
system:translation:machine:audix/amis/call delivery
form, and may be displayed on the
list:machine
form.
AMIS Analog Networking
Overview
1
585-300-512 Issue 7

DEFINITY AUDIX System Enhancements

The AMIS Analog Networking and Message Delivery features have been enhanced since the initial DEFINITY AUDIX R 1.0 software release as follows. Any enhancements made for a given release are carried forward to later releases.
R2.0
— Several enhancements were made to the AMIS Analog Networking feature in the R2.0 software release. These changes, summarized below, are fully documented in the
1.0 to 2.0 Change Description,
— DEFINITY AUDIX R2.0 systems no longer need to be rebooted to
activate AMIS analog networking feature parameters (as was required for R1.0 systems). In R2.0 software, audits can be run to activate AMIS analog networking or message delivery administration changes.
— The same improvements made for the AUDIX R1V7 7:2 software
load were also made in DEFINITY AUDIX R2.0 software (see the previous "AUDIX System Enhancements" section for a summary).
R3.0
— Multiple callback numbers were added to allow more flexible AMIS operation in mixed public/private networks. Up to five callback numb er s can be spe cifie d on the System-Parameters Analog-Netwo rk screen. Callback numbers are assigned to remote machines using the Machine screen, and may be displayed using the List Machines screen.
May 1999
1-15Feature Enhancements by Release
DEFINITY AUDIX Release
585-300-401.

Intuity System Enhancements

The AMIS Analog Networking and Message Delivery features on the Intuity R1.0 system have the same feature set as the DEF INIT Y AUDIX R2.0 software release. The AMIS Analog Networking and Message Delivery features on the Intuity R2.0 system have the same feature set as the DEF INIT Y AUDIX R3.1 software release. For a complete description of the AMIS Analog Networking feature, search for AMIS analog networking in your Intuity documentation.
AMIS Analog Networking
Overview
1
585-300-512 Issue 7
May 1999
1-16Feature Enhancements by Release
AMIS Analog Networking

Planning and Design

2
585-300-512 Issue 7
Planning and Design
This chapter covers procedures needed to plan and design a network using the AMIS Analog Networking and/or Message Delivery features. Information includes hardware and software requirements, security considerations, and required network informatio n.
May 1999
2-1Requirements
2

Requirements

This section describes the hardware and software required to implement the AMIS Analog Networking and/or Message Delivery features on your local Lucent Technologies voice mail system. There are no switch or installation requirements other than those listed in this section.

Software Requirements

The following software is required to implement AMIS analog networking and/or message delivery:
AMIS analog networking must be enabled by authorized Lucent
Technologies personnel to use either the AMIS Analog Networking or Message Delivery feature.
The local voice mail system must be running an appropriate version of
software:
AUDIX System:
DEFINITY AUDIX System:
Intuity System:
For AMIS Analog Networking:
network must also have their AMIS analog networking capabilities activated.
Requires R1V6 or later software.
Requires R1.0 or later software.
Requires R1.0 or later software.
Any remote voice mail systems in the
AMIS Analog Networking
Planning and Design
2
585-300-512 Issue 7

Hardware Requirements

The following hardware is required to implement AMIS analog networking and/or message delivery:
For Both Features:
system to handle the additional traffic. See the following "Voice Port
Needs" section to determine if additional voice ports may be needed.
For Message Delivery:

Voice Port Needs

In order to determine if additional voice ports may be needed on your system to support the AMIS Analog Networking and/or Message Delivery features, first consider the amount of traffic (number and length of messages) you expect to occur during the
If you do not plan to use the AMIS Analog Networking and/or Message
Delivery features during the busy hour (for example, if you plan to allow messages to be transmitted only at night), you probably have enough voice ports to support this feature. However, after the feature has been activated, you may wish to verify that system performance is not affected by following the steps in the "Monitor Voice Port Use" section.
Sufficient voice ports must be installed on the local
busy hour
May 1999
2-2Requirements
The recipient must have a touch-tone telephone.
of the day.
If you plan to use the AMIS Analog Networking and/or Message Delivery
features during the busy hour, consider the impact of these features on voice-port use as follows:
— If the expected AMIS analog networking and/or message delivery
traffic is light, you probably do not need to add any voice ports to support this feature. However, after the feature has been activated, you may wish to verify that system performance is not affected by following the steps in the "Monitor Voice Port Use" section.
— If the expected AMIS analog networking and/or message delivery
traffic is heavy, do the calculations in the following section to determine the effect these features may have on system performance.
Calculate Expected Voice Port Use
If you plan to use the AMIS Analog Networking and/or Message Delivery features during the busy hour and you want to estimate the impact these features might have on your system performance, you can do the following calculations. (If you are purchasing a new voice mail system, the Lucent Technologies account team runs these calculations for you.)
1. Estimate the number of AMIS analog networking and/or message delivery messages you expect to occur during the busiest hour of the day.
AMIS Analog Networking
Planning and Design
2
2. Estimate the anticipated length of each message. Each AMIS and/or message delivery message requires an additional 45 seconds of overhead to transmit.
3. Multiply the values from Steps 1 and 2 as follows:
4. Divide the total seconds of projected port usage by 3600. This number represents the during the busy hour.
5. Add this number to the maxim um av er age number of ports in use. Refer to the following "Monitor Voice Port Use" section for the form and field needed on your system to get these values.
6. Use the table in the appropriate administration manual (see next section) to determine if the resulting grade of service (GOS) will be acceptable (refer to the following "Monitor Voice Port Use"). If not, plan to install the recommended number of additional voice ports AMIS Analog Networking or Message Delivery features.
585-300-512 Issue 7
May 1999
2-3Requirements
(# messages) (average message length + 45 seconds) = X seconds of port use
additional
port usage required to support this feature
X seconds of port use / 3600 = # additional port usage
before
implementing the
Monitor Voice Port Use
Use the following procedure to determine if additional voice ports may be needed on your system. You may use this procedure after activating the AMIS Analog Networking and/or Message Delivery features to determine their impact (if any) on system performance.
For an AUDIX System:
1. Disp la y the in the max average number of ports in use field.
2. Using the the grade of service (GOS).
3. Usin g the manual, calculate the grade of service (GOS).
For an Intuity System:
1. Display the Feature Daily Traffic form using the
feature day
Maximum Average Ports in Use
2. Calculate the grade of service (GOS). For procedures, search your Intuity documentation for grade of service (GOS).
For any of the systems, a GOS of .05 is recommended (a lower GOS is
desirable). If the GOS is greater than .05, additional voice ports should be installed. Contact your sales representative.
traffic:feature:day
AUDIX Administration,
DEF INIT Y AUDIX System — Administration
form and record the number
585-305-501, manual, calculate
, 585-300-507,
list measurements
command and record the number you see in the
field.
AMIS Analog Networking
Planning and Design
2

Security

Because the AMIS Analog Networking and/or Message Delivery features use the
switch’s analog lines to transmit messages, verify that the class of restriction (COR) assigned to the local system’s voice ports supports outcalling, or these features will not work. For example, to protect against possible toll fraud, the local system’s voice ports might be restricted from accessing 2-way or outgoing trunk groups. The COR for the voice mail system might need to be altered to allow the AMIS Analog Networking, Message Delivery, and Outcalling features to work.
However, if left completely unrestricted, the AMIS Analog Networking and/or Message Delivery features could allow local voice mail users to send messages to any valid telephone number worldwide. Consequently, the system administrator must use judgment when administering the AMIS Analog Networking and/or Message Delivery features. For example:
In order to minimize exposure to unauthorized long-distance calls, the
AMIS Analog Networking and Message Delivery features should be restricted to sending messages to remote machines or telephone numbers located in specific calling areas or at the specific destinations needed to conduct business.
585-300-512 Issue 7
May 1999
2-4Security
Additionally, the syst em administrator can use the
Restrictions
feature to limit the use of the AMIS Analog Networking and/or
Message Sending
Message Delivery features to only those subscribers who have a need to use it. The Message Sending Restrictions feature can also be used to limit AMIS Analog Networking and/or Message Delivery calls to specified remote machines (numbers) or user communities. It may be overridden for specific subscribers if needed. Refer to the feature descriptions manual for your voice mail system for more information on the Message Sending Restrictions feature.
For more information about voice mail system security, refer to the
Products Security Handbook
!
CAUTION:
, 555-025-600.
GBCS
The customer is responsible for administering their Lucent Technologies voice mail systems to prevent subscribers from sending unauthorized long-distance AMIS Analog Networking or Message Delivery messages. Remote systems can be administered so subscribers can send messages to voice mail systems anywhere in the world, only to specific countries, only to domestic systems, only to specific domestic area codes, only locally, or only to specific destinations. See the following
"Network Design"
details. The customer is also re sponsible for administering the voice mail system
and associated passwords to prevent unauthorized users from accessing subscriber mailboxes and sending unauthorized AMIS Analog Networking or Message Delivery messages.
section for
AMIS Analog Networking
Planning and Design
2
585-300-512 Issue 7

Network Design

Planning is the essential first step in implementing an AMIS analog networking and/or message delivery network. Actual network administration should not begin until the local voice mail system is running smoothly and the system administrator is familiar with all aspects of administering it.
A network coordinator should be named to manage the administration and updates for every remote system (for AMIS analog networking) or telephone number (for message delivery). This is particularly important on AMIS analog networking and/or message delivery networks where remote subscriber records must be input manually on the local machine (machine-to-machine updates are not supported over an AMIS analog/message delivery network).

Designing an AMIS Analog/Message Delivery Network

Figure 2-1 shows you a sample network that contains the following systems:
May 1999
2-5Network Design
AUDIX System:
This sample R1V8 system uses AMIS analog networking to connect with a DEFINITY AUDIX system and a set (range) of non-Lucent Technologies voice mail systems. The system uses the Message Delivery feature to connect to several other locations including all local numbers and one long-distance destination.
In this example, the AUDIX system is also digitally networked to other AUDIX or Intuity systems. These digital connections do not directly affect the AMIS analog/message delivery network ranges
cannot
be duplicated or overlap. Address ranges are discussed in
excep t
that the address
the "Defining Address Ranges" section of this chapter.
DEFINITY AUDIX System:
This system has a smaller number of subscribers. The system also connects to several Message Delivery locations including all local numbers and one long-distance site, a range of non-Lucent Technologies voice mail systems, and the AUDIX R1V8 and Intuity systems.
Intuity System:
The sample Intuity system uses AMIS analog networking to connect with a DEFINITY AUDIX system and a set (range) of non-Lucent Technologies voice mail systems. The system uses the Message Delivery feature to connect to several other locations including all local numbers and one long-distance destination.
In this example, the Intuity system is also digitally networked to other Intuity or AUDIX systems. These digital connections do not directly affect the AMIS analog/message delivery network ranges
cannot
be duplicated or overlap. Address ranges are discussed in
excep t
that the address
the"Defining Address Ranges" section of this chapter.
AMIS Analog Networking
Planning and Design
2
Non-Lucent Technologies Voice Mail Systems:
systems must have AMIS analog networking capability. The example assumes a range of other-vendor voice mail systems.
Message Delivery Destinations:
be a touch-tone telephone.
585-300-512 Issue 7
May 1999
2-6Network Design
These other-vendor
Each Message Delivery destination must
Non-Lucent Technologies
voice mail systems 2000
local subscribers
Long-distance
message delivery
1 person or number
Non-Lucent Technologies
voice mail systems 2000
local subscribers
Long-distance
message delivery
1 person or number
Digitally
networked
machines
AUDIX R1V8
2000 local subscribers
Linked to the
Intuity system through
digital networking
or
AMIS analog
networking
DEFINITY
AUDIX
500 local
subscribers
Local
message
delivery
Local
message
delivery
Non-Lucent Technologies
voice mail systems 2000
local subscribers
Long-distance
message delivery
1 person or number
cldxami2 LJK 032699
Digitally
networked
machines
Intuity system
5000 local
subscribers
Linked to the
AUDIX system
through
digital networking
AMIS analog
networking
Figure 2-1. Sample AMIS Analog/Message Delivery Network
or
Local
message
delivery
AMIS Analog Networking
Planning and Design
2
Figure 2-2 shows how the network planner decided to design the connections
between the machines (nodes or destinations) of the sample AMIS analog/message delivery network shown in Figure 2-1.
AUDIX System AMIS Connections:
and DEFINITY AUDIX system was expected to be heavy, the AUDIX system is designed to use one-step ( DEFINITY AUDIX system. Digital Networking was used for the connection to the Intuity system.
Because there is more than one non-Lucent Technologies voice mail system, the AUDIX system is designed to use two-step ( addressing for this range of systems. Because two-step addressing is used, these remote recipients machine.
585-300-512 Issue 7
May 1999
2-7Network Design
Because traffic between the AUDIX
pre-administered
cannot
be administered on the local
) addressing to the
casual
)
NOTE:
Each remote system administered for AMIS one-step addressing must have an individual machine profile administered on the local system. The one-step connection provides an easier user interface (see the "Subscriber Features" section in Chapter 1, "Overview").
DEFINITY AUDIX System AMIS Connections:
Because the system administrator is expecting to add a large number of subscribers, the network planner decided to use a two-step (
casual
) connection to the AUDIX and Intuity systems. Alternatively, the administrator could have set up a one-step (
pre-administered
) connection and left most of the
sub scribers non-a dminist ered. Because there is more than one non-Lucent Technologies voice mail
system, the DEF INITY AUDIX system is designed to use two-step ( addressing to this system.
NOTE:
Users on remote systems administered for two-step addressing
cannot
be administered on the local system, nor can local subscribers include them in subscriber-defined mailing lists or personal directories.
casual
)
AMIS Analog Networking
Planning and Design
2
Intuity System AMIS Connections:
system and the DEFINITY AUDIX system was expected to be heavy, the Intuity system is designed to use one-step ( to the DEFINITY AUDIX system. Digital Networking was used for the connection to the AUDIX system.
Because there is more than one non-Lucent Technologies voice mail system, the AUDIX system is designed to use two-step ( addressing for this range of systems. Because two-step addressing is used, these remote recipients machine.
Message Delivery Connections:
systems are designed to allow local subscribers to address Message Delivery messages to any local number. However, only a single remote destination is planned for the long-distance Message Delivery number to better prevent unauthorized long-distance phone calls.
585-300-512 Issue 7
May 1999
2-8Network Design
Because traffic between the Intuity
cannot
pre-administered
be administered on the local
) addressing
casual
)
NOTE:
Each remote system administered for AMIS one-step addressing must have an individual machine profile administered on the local system. The one-step connection provides an easier user interface (see the "Subscriber Features"
section in Chapter 1, "Overview").
Both the AUDIX and DEFINITY AUDIX
AMIS Analog Networking
Planning and Design
2
585-300-512 Issue 7
May 1999
2-9Network Design
Non-Lucent Technologies
voice mail systems 2000
local subscribers
Long-distance
message delivery
1 person or number
Specific telephone
numbers
Non-Lucent Technologies
voice mail systems 2000
local subscribers
Long-distance
message delivery
1 person or number
Specific telephone
numbers
Non-Lucent Technologies
voice mail systems 2000
local subscribers
Long-distance
message delivery
1 person or number
Specific telephone
numbers
cldxami1 LJK 032699
Digitally
networked
machines
Casual
(two-step)
number
Casual
(two-step)
number
Casual
(two-step)
number
Digitally
networked
machines
AUDIX R1V8
2000 local subscribers
Linked to the
Intuity system through
digital networking
Pre-administered
(one-step)
DEFINITY
AUDIX
500 local
subscribers
Casual
(two-step)
AMIS
Intuity system
5000 local
subscribers
Linked to the
AUDIX system
through
digital networking
Local
message
delivery
Range of local
numbers
Casual
(two-step)
AMIS
Local
message
delivery
Range of local
numbers
Pre-administered
(one-step)
Range of local
numbers
Local
message
delivery
Figure 2-2. Sample AMIS Analog Network/Message Delivery
Connections
AMIS Analog Networking
Planning and Design
2
585-300-512 Issue 7

Defining Address Ranges

All local and remote machines (including Message Delivery telephone numbers) in the AMIS analog/message delivery network work must have unique
The parts that make up a remote machine’s address are the AMIS prefix (optional), the address prefix (sometimes required), and the extension ranges (required).
For non-Lucent Technologies systems or remote destinations, you may need to call the person responsible for administering that machine to collect address information. The address ranges for Lucent Technologies voice mail systems can be displayed using the following forms:
May 1999
2-10Network Design
addresses
.
On AUDIX systems, use the
On DEFINITY AUDIX systems, use the List Address-Ranges form.
On Intuity systems, use the List Address-Ranges screen.
AMIS Prefix
An
AMIS prefix
analog networking feature. If an AMIS prefix is administered, local subscribers must always dial it as the first part of the recipient’s address whenever they address an AMIS message (the prefix signals to the system that the following digits constitute an AMIS analog networking address). Even though the AMIS prefix introduces another digit for subscribers to dial, you may wish to administer one to help subscribers distinguish between AMIS messages and other features, and to ensure that the address ranges for the AMIS analog network destinations are unique.
Address Prefixes
Address prefixes are digits subscribers dial administered) and addres s ing m e s s a ges. A ddres s pref i x es m a y be prov i de d to a l l o w su bs cr i be rs t o address remote messages in various ways and still allow the message to be delivered (for example, if the remote system can be accessed over a public private network).
system:translation:address
form.
may be defined on the same form used to implement the AMIS
after
the AMIS prefix (if one is
prior
to the recipient’s extension or phone number when
or
a
Address prefixes may be
required
in some cases to prevent extension ranges from overlapping; duplicate or overlapping ranges are not allowed on AMIS analog networking or message delivery networks (see the following "Overlapping
or Duplicate Ranges" section for details). Generally, prefixes are
not
recommended in a DCS network.
AMIS Analog Networking
Planning and Design
2
An address prefix could be any of the following, or combinations of the following:
The same numbers as the country code and area code (for example,
1 303
Kingdom).
The same numbers as the area code (NPA) and office code (for example,
614 555
The office code (NNX or NXX) if the remote system shares the same area
code (for example,
An alphanumeric code used as a mnemonic of a location or system (for
example, CB for Columbus).
585-300-512 Issue 7
within the United States, or
011 44 71
to reach London, United
May 1999
2-11Network Design
).
555
).
An RNX code if the remote system is in a private network (for example,
The AMIS prefix for AMIS address ranges only (for example,
7
). If an AMIS
8
).
prefix is defined, it must precede any other characters subscribers must dial in any other address prefixes defined for the AMIS address ranges.
A Message Delivery prefix to help subscribers distinguish between
Message Delivery messages and AMIS messages (for example, 6). A Message Delivery address prefix and AMIS prefix could be the same, or two different prefixes could be used.
In addition to the address ranges that specify the digits that
subscribers
must enter (those that begin with an AMIS prefix, if defined), the local system also requires an address range that uniquely identifies the hunt group (callback number) of the remote machine (this is the voice mail system number sent to the local machine from the remote system when incoming AMIS messages arrive). This address range is needed to identify this specific remote system to the local system. If the remote machine has a different country code, this address range must contain the complete callback number (country code, area/trunk code, and hunt group). If the remote machine has a different area or trunk code, only the area/trunk code and hunt group are needed (the country code should be omitted). If the remote system is local, only the hunt group number should appear for that machine. If the remote machine can be accessed through a private network, the network-access code and hunt group for the remote machine should appear in the address prefix list.
AMIS Analog Networking
Planning and Design
2
585-300-512 Issue 7
Overlapping or Duplicate Ranges
For all AMIS analog networking and message delivery addresses, duplicate address ranges or overlapping address ranges are
range
(or full overlap) means that the address range you have defined is already defined for another machine. An have defined is a subset of an already existing range or is overlapping another range.
overlapping range
May 1999
not
permitted. A
duplicate
means that the range you
2-12Network Design
For example, you would be assigning a range 2000-3999 when the range 2000-5999 already exists. The new range would not be allowed (you would receive an error message). You would be assigning an
overlap
the range 2000-5999 already exists. To avoid this problem, assign two new ranges instead (1000-1999 and 6000-6999). If you cannot avoid a duplicate or overlapping range, return to the" A ddress Pr e f ixe s" section and select an address prefix that will make the range of numbers unique.
Extension Ranges and Length
Every remote machine in an AMIS analog/message delivery network assigned an extension range. If you want local subscribers to access a specific remote machine or telephone number (for example, for long-distance AMIS casual systems or Message Delivery destinations), you can assign an extension
“range” of a single number (such as The length of the extension depends on the application. For example, on AMIS
one-step systems, the system dials the remote system’s telephone number for the subscriber, allowing subscribers to type fewer digits. The interaction between extension length and the the remote machine) is summarized in the next section. Generally:
For AMIS one-step (pre-administered) connections:
is typically the same length as other extensions on the switch. That is, local subscribers’ extension numbers are the same length as other extensions on the local switch, and remote subscribers’ extension numbers are the same length as other extensions on the remote switch.
subset
if you tried to assign the extension
if you tried to assign the extension range 5000-6999 when
must
be
dial string
4000
(the number the local system dials to reach
to
4000
).
The extension length
For AMIS two-step (casual) and Message Delivery connections:
The extension length indicates how many digits entered by subscribers for an AMIS or Message Delivery address are actually dialed by the local system. For example, if the extension length is 7, the local voice mail system dials the dial string followed by the last seven digits of the number a subscriber enters as an address (an AMIS prefix, if assigned, is not dialed).
AMIS Analog Networking
Planning and Design
2
Dial String Interaction
The
dial string
Delivery setup), or the entire number the local voice mail system actually dials to reach a remote machine (for a pre-administered AMIS setup). The dial string is optional on AMIS casual systems and for message delivery, but is required for AMIS one-step systems. The dial string you administer depends in part on the extension length.
For AMIS one-step (pre-administered) addressing:
required. It can be up to 65 characters long, and typically consists of the trunk-access code or dial-access code needed to reach the public or private network, followed by the complete telephone number of the remote machine. For example, the local voice mail system might dial
912015556000
If desired, pause characters may be inserted in the string to have the system pause before continuing to dial (for example, to wait for a dial
tone). A single “P” (including quotes) causes the system to pause approximately 1.5 seconds; a “P” followed by a digit from 1 to 9 causes the system to wait the specified multiple of 1.5 seconds.
585-300-512 Issue 7
May 1999
2-13Network Design
is either the first few digits dialed (for an AMIS casual or Message
A dial string is
to reach the remote system.
For AMIS two-step (casual) and Message Delivery connections:
T he dial string (if used) may be from 0 to 24 characters long. It consists of any numbers the system should add to the number subscribers dial to reach a specific address. The dial string plus the extension must be less than or equal to 29 characters. Some examples are:
— For a range of local numbers, the dial string might be 9 (or
whatever trunk-access code or dial-access code is assigned to reach the public network). For example, if the extension length is 7 and a subscriber specifies a valid 7-digit address (such as 555-6000), the local system would dial
95556000
to reach the
remote machine .
— For a range of long-distance numbers, the dial string would
normally be 91 in the United States (the trunk- or dial-access code followed by 1). For example, if the extension length is 10 and a subscriber specifies a valid 10-digit address (such as 201-555-6000), the local voice mail system would dial
912015556000
to reach the remote machine.
AMIS Analog Networking
#
Planning and Design
2
585-300-512 Issue 7
Sample Network Design
Table 2-1 summarizes the network planning information for the sample network
configuration shown in Figure 2-1 and Figure 2-2. As you study the table, use the following information to help you understand the planning information:
May 1999
2-14Network Design
Local System:
The AUDIX system
localr1
was selected as the local system in this example. Another form would be filled out for the DEFINITY AUDIX system and the Intuity system showing those systems (named
chicago
and
newyork
in the example) as the local systems, and the
AUDIX system as one of their remote voice mail connections.
One-Step AMIS Connection:
system (
amisap
(
chicago
) and the Intuity system (
) connection. The local hunt group for these ports must be either
The connection to the DEFINITY AUDIX
newyork
) is a pre-administered
listed on a separate line or included in another address range. The following list shows acceptable prefixes for subscribers to dial while addressing messages:
—7 — 7ch — 7555 —8
8ny
Two-Step AMIS Connection:
The connection to the multiple non-Lucent Technologies voice mail systems with 5-digit address ranges from 55000 to 58999 was administered for two-step ( range is named
otherven
(for
other vendor
amisac
) addressing. The entire
). To reach this set of systems, subscribers must always dial the complete voice mail system number (for example, 7555-7000), press then dial a 5-digit extension to reach a specific remote recipient.
Local Message Delivery:
All local 7-digit phone numbers are available for local subscribers to use. Subscribers must enter the address prefix 6, followed by the complete local number, to address a Message Delivery recipient.
Long-Distance Message Delivery:
In order to make it easier for local subscribers to place calls to a London office, the system administrator has placed most of the overseas telephone numbers in the dial string. Subscribers need to enter just the address prefix 6, followed by the last three digits of the intended recipient’s address, in order to send a message to London. The local system administrator has administered five members of the London office on the local machine to allow name addressing and name voiceback.
AMIS Analog Networking
585-300-512 Issue 7
May 1999
Planning and Design
2
Table 2-1. Planning Summary for AMIS Analog/Message
Delivery Network
Message
Address Ranges (up to 10)
Machine Name
localr1 5 1 n/a n/a - 30000 39999 00:00 23:59 2000 10000
Ext. Length
Default Com
Connect Typ e
Dial String
Prefix
Start Ext.
End Ext Start End Local
Transmission Schedules (up to 3)
Number of Subscribers
Adm Remote
2-15Network Design
chicago 4 1 amisap 9555
8000
newyork 4 1 amisap 9555
6000
otherven 7 1 amisac 9 7 555
localnums 7 1 calld 9 6 000
london 3 1 calld 901144
712377
555 4000 4000 00:00 23:59 500 150
7 4001 4999 7ch 4001 4999 7555 4001 4999
8 6000 6000 00:00 23:59 5000 20000
8 6001 6999 8ny 6001 6999
5000
0000
6 100 299 19:00 07:30 n/a 5
555 8999
999 9999
07:00 17:59 2000 n/a
08:00 17:30 n/a 25
AMIS Analog Networking
Planning and Design
2

Network Planning

Once you have decided on a logical scheme for implementing your network, you need to collect information on both the local and remote machines (or telephone numbers) in your network.
This section provides worksheets to help you collect and record the information needed to administer an AMIS analog networking and/or message delivery network. These completed worksheets can be used as a guide for implementing the network for your specific voice mail system when you proceed to the following chapters. The worksheets should be stored in a safe place and updated as changes to the network are made. The following information is needed to plan and design your network:
Local machine information
Remote machine information
Remote subscriber information
585-300-512 Issue 7
May 1999
2-16Network Planning

Collect Local Machine Information

Because the local machine should be up and running before you begin remote machine administration, data about the local machine can be collected simply by displaying the forms from the first few tasks as directed in the section of the administration chapter for your voice mail system.
In order to simplify remote machine administration, record this information now on Worksheet A. Refer to the administration chapter for details on using these forms.
1. Record the following information for the local machine:
Local machine name (all machine names should be unique)
Extension length (for local address ranges)
Default community (used by the Message Sending Restrictions
feature)
Address ranges (up to 10) — This includes the address prefix
(typically none), starting extension number in each range, and ending extension number in each range
On AUDIX systems, use the
audix/amis/call delivery
On DEFINITY AUDIX systems, use the Machine form.
Implementation
section in the appropriate
system:translation:machine:
form.
Implementation
On an Intuity system, refer to the AMIS Analog Machine Administration and Machine Profile screens.
AMIS Analog Networking
Planning and Design
2
2. Record the callback number or numbers (the complete telephone number the remote node uses to dial the local voice mail system).
585-300-512 Issue 7
May 1999
2-17Network Planning
NOTE:
On AUDIX R1V8 systems and DEFINITY AUDIX R3.1 systems, up to five callback numbers can be administered. This allows different nodes to use different telephone numbers to call the same AMIS machine. For example, an AMIS analog network may include some nodes accessed over the public network, and other nodes accessed over a private network. Vendors other than Lucent Technologies may also require the AMIS callback numbers to be administered in a particular way.
On AUDIX systems, use the
system:translation:analog network
form. On DEFINITY AUDIX systems, use the System-Parameters
Analog-Network form. On an Intuity system, refer to the System-Parameters Analog-Network
screen.
3. Record the local machine’s outc alling cycles (used for message
transmission; up to three cycles are allowed). On AUDIX systems, use the
system:outcalling
form.
On DEFINITY AUDIX systems, use the System-Parameters Outcalling form.
On Intuity systems, use the System-Parameters Outcalling screen.
AMIS Analog Networking
Planning and Design
2
585-300-512 Issue 7
Worksheet A: Local Machine Information
May 1999
2-18Network Planning
Machine Name (1 to 10 chars.)
Address Ranges
Prefix (0 to 21 characters) Start Extension End Extension
1.
2.
3.
4.
Ext. Length (3 to 10)
Default Commun.
Callback Number (s)
Local/Re mote
Local
Connection Typ e
1.
2.
3.
4.
5.
Outcalling Schedule
Start Time End Time
1.
2.
3.
5.
6.
7.
8.
9.
10.
AMIS Analog Networking
Planning and Design
2
585-300-512 Issue 7

Collect Remote Machine Information

Because address ranges cannot conflict (no overlaps or duplications are permitted), you need to collect information about each remote machine or telephone number you intend to administer for AMIS analog networking and/or message delivery. Usually this involves a phone call to the system administrator or individual responsible for the remote machine or telephone number you wish to add to your network.
NOTE:
This step is the most crucial phase in designing your network. If you have address range conflicts, you must assign unique prefixes to differentiate each machine. Whatever AMIS prefix and/or address prefixes you assign must be communicated to the subscriber population so subscribers can correctly address AMIS analog networking and/or message delivery messages.
The following information is required for each remote machine or message delivery number you intend to administer. Fill out a copy of Worksheet B for each remote machine .
May 1999
2-19Network Planning
Remote machine name (all machine names should be unique)
Extension length (for remote numbers or address ranges)
Default community (used by the Message Sending Restrictions feature)
Connection type — Either AMIS one-step addressing (
two-step addressing (
Message transmission cycles to the remote machine (must be equal to or
amisac
), or message delivery (
amisap
calld
), AMIS
)
a subset of the local machine’s outcalling cycles)
NOTE:
For more efficient use of system resources, you may wish to limit the times of day for sending AMIS analog networking or message delivery messages to those which are known to be less busy.
Dial string — This includes either the complete telephone number used by
the local machine to call the remote machine for AMIS pre-administered systems, or as much of the number that you wish the local machine to dial for AMIS casual or Message Delivery systems.
Address ranges (up to 10) — This includes the AMIS prefix and/or
address prefix (typically required), starting extension number in each range, and ending extension number in each range.
AMIS Analog Networking
Planning and Design
2
585-300-512 Issue 7
Worksheet B: Remote Machine Information
May 1999
2-20Network Planning
Machine Name (1 to 10 chars.)
Prefix (0 to 21 characters) Start Extension End Extension
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Ext. Length (3 to 10)
Default Commun.
Local/ Remote
Remote
Connection Typ e
Address Ranges
Transmission Schedule
1.
2.
3.
Dial StringStart Time End Time
AMIS Analog Networking
Planning and Design
2
585-300-512 Issue 7

Collect Remote Subscriber Information

Individual message delivery recipients and subscribers on remote machines administered for AMIS one-step (pre-administered) addressing may be administered on the local machine. This allows local subscribers to address messages to these recipients by name (last-name-first) and to hear name voiceback to confirm addressing (if you record a name). Subscribers on remote systems administered for two-step addressing local system.
The local system administrator must input all administered remote subscriber information and keep the information current (there is no machine-to-machine updating available for remote machines over an AMIS analog/message delivery network). For this reason, you may wish to administer only those remote subscribers expected to regularly receive messages. Record the pertinent information for these subscribers on Worksheet C.
cannot
May 1999
2-21Network Planning
be administered on the
AMIS Analog Networking
Planning and Design
2
585-300-512 Issue 7
Worksheet C: Remote Subscriber Information
May 1999
2-22Network Planning
Remote Subscriber Name (last-name-first)
Remote Machine Name(s)
Remote Extension
Default Community
AMIS Analog Networking

AUDIX Administration

3
585-300-512 Issue 7
AUDIX Administration
This chapter describes how to implement the AMIS Analog Networking and/or Message Delivery features on an AUDIX R1V6 or later system. Information is organized as follows:
May 1999
3-1
3
Implementation and testing
Ongoing administration
NOTE:
To administer AMIS analog networking on a DEFINITY AUDIX system, turn to Chapter 4, "DEFINITY AUDIX Administration" networking on an Intuity system, turn to Chapter 5, "Intuity System AMIS
Administration".
Planning is the essential first step in implementing the AMIS Analog Networking and/or Message Delivery features. Complete Chapter 2, "Planning and Design", before starting the steps in this chapter.
Network administration should not begin until the local system is running smoothly and the administrator has had some experience administering it.
!
WARNING:
To minimize unauthorized long distance calls, restrict the AMIS Analog Networking and Message Delivery features to send messages to telephone numbers located in specific calling areas or to specific destinations needed to conduct business. Additionally, use the Message Sending Restrictions feature to administer which subscribers can send AMIS analog networking and message delivery messages, and to which locations they can send messages.
To administer AMIS analog
AMIS Analog Networking
AUDIX Administration
3

Implementation

This section describes how to implement the AMIS Analog Networking and Message Delivery features on an AUDIX R1V6 or later system. Because the AMIS Analog Networking and Message Delivery features have similar administration requirements, you may want to administer them simultaneously if you plan to use both feat ures.
AUDIX administration tasks include:
1. Display the Local Machine
2. Administer AMIS Analog Networking Loopback Test Mailbox (Optional)
3. Administer AMIS Analog Networking/Message Delivery Parameters
4. Administer Outcalling Periods
5. Adjust System Limits for Subscribers
6. Administer Retransmission Intervals
7. Restart the AUDIX System
585-300-512 Issue 7
May 1999
3-2Implementation
8. Administer Remote Machines and/or Telephone Numbers
9. Record Remote Machine Names (Optional)
10. Administer Remote Subscribers (Optional)
11. Record Administered Remote Subscriber Names (Optional)
12. Test the Remote Connection
NOTE:
Not all forms used to administer these features are fully explained in this section; only the information necessary for implementing the AMIS Analog Networking and/or Message Delivery features is covered. For complete instructions for using screen forms, refer to the appropriate forms reference manual for your version of AUDIX software:
AUDIX Release 1 Version 6 Forms Reference
AUDIX Release 1 Version 7 Forms Reference
AUDIX Release 1 Version 8 Forms Reference
, 585-305-204 , 585-305-208 , 585-305-209
AMIS Analog Networking
AUDIX Administration
3
585-300-512 Issue 7

Task 1: Display the Local Machine

May 1999
3-3Implementation
Use the
system:translation:machine:audix/amis/call delivery
form to verify the administration of the local AUDIX system. The local machine is the system to which the terminal is connected. All others are considered remote machines regardless of where they are located.
1. Log into the AUDIX system as described in
AUDIX Administration,
585-305-501.
2. Type
sy tr m au
on the path line to access the
machine:audix/amis/call delivery
3. Press (F8) and the screen will populate the fields for the local
ENTER
system:translation:
form. Press .
RETURN
machine.
Figure 3-1, Local AUDIX Machine Profile (R1V8), shows a sample local
machine profile. This form looks slightly different in earlier versions of AUDIX software.
Localrl STATUS: alarms: none, logins: 1, thresholds: none
PATH: system : translation : machine : audix/amis/call delivery
machine name: localr1___ local/remote: l password: ________ ext length: 5 voiced name (y/n)? n voice id: 0 AMIS callback no.: _ (1, 2, 3, 4, or 5) default community: 1 connection type: ______ data rate: _____ channel: _ dial string:______________________________________________________________ address ranges (prefix start / end extension) warnings 1: ____________________ 52001 / 53999 2: ____________________ 55000 / 55999 3: ____________________ 57000 / 57999 4: ____________________ _________ / __________ ____________ 5: ____________________ _________ / __________ ____________ 6: ____________________ _________ / __________ ____________ 7: ____________________ _________ / __________ ____________ 9: ____________________ _________ / __________ ____________ 10: ____________________ _________ / __________ ____________
message transmission schedule (hh:mm)
1. start: __:__ end: __:__ interval: __:__ updates (y/n)? in _ out _
2. start: __:__ end: __:__ interval: __:__ network turnaround (y/n)? _
3. start: __:__ end: __:__ interval: __:__ log connect events (y/n)? _ new machine name: ______________ send to non-administered recipients (y/n)? _
Error and confirmation messages appear here.
CHANGE or RUN
ADD DELETE CLEAR
HELP
FORM
EXIT ENTERHELP FIELD
Figure 3-1. Local AUDIX Machine Profile (R1V8)
AMIS Analog Networking
AUDIX Administration
3
585-300-512 Issue 7
May 1999
3-4Implementation
4. Go through the following form fields by pressing the key, and change
TAB
any fields needed to implement the AMIS Analog Networking or Message Delivery features:
a. Machine Name
This field displays the name of the local machine (also shown on the STATUS line).
b. Local/Remote
This display-only field shows the system type.
c. Password
This field does not apply to AMIS analog networking or message delivery (it is used for digital networking only).
d. Ext Length (or extension length prior to R1V8)
This field should already be set to the correct switch-extension length used by subscribers on the local machine.
e. Voiced Name
This display-only field indicates if a machine name fragment has been recorded for the local system. Names are not normally recorded for the local system.
f. Voice ID
This display-only field shows the number associated with this
machine’s name fragment. This number is used when recording the name. The local system’s voice ID is always 0.
g. AMIS callback no.
This field was added in R1V8 software to support multiple callback numbers. It is used only for
remote
AMIS machines; on the local
machine profile, this field will be blank.
h. Default Community
The default community for users of this machine. A community contains those subscribers who are able to send voice mail messages to one another as permitted on the
restrictions
subscribers on the
subscriber:remote
Use this field and the
form. This value may be overridden for individual
subscriber:local
form.
system:sending restrictions
system:sending
or the
form to control which subscribers can send or receive AMIS analog networking or message delivery messages, either on a machine-by-machine or a number-by-number basis.
i. Connection Type (or network connection type prior to R1V8)
This field is filled in on the local machine only if digital networking is implemented.
AMIS Analog Networking
AUDIX Administration
3
j. Data Rate
k. Channel
l. Dial String
m. Address Ranges
585-300-512 Issue 7
May 1999
3-5Implementation
This field does not apply to AMIS analog networking or message delivery (it is used on the local machine only for digital networking).
This field does not apply to AMIS analog networking or message delivery (it is used on the local machine only for digital networking).
This field does not apply to the local machine.
Verify the range of extensions used on the local machine:
— The prefix field typically is not used on the local machine. — The start/end extension fields define the switch extensions
that can be used by the local system. Up to ten different ranges can be specified. The length of the start and end extensions must agree with the number shown in the ext length field (leading zeros may be required to conform to this requirement). The end extension must be equal to or greater than the start extension.
— warnings is a display-only field that indicates when a
duplicate or overlapping range is being assigned.
n. Message Transmission Schedule
These fields are used for remote machine profiles only.
o. Updates in/Updates out
These fields do not apply to AMIS analog networking or message delivery (they may be set to y on the local machine if digital networking is implemented).
p. Network Turnaround (y/n)?
This field was added in R1V7 for digital networking. This field does not apply to AMIS analog networking or message delivery (it may be set to y on the local machine if digital networking is implemented).
AMIS Analog Networking
AUDIX Administration
3
q. Log Connect Events (y/n)?
r. Send to non-administered recipients (y/n)?
585-300-512 Issue 7
May 1999
3-6Implementation
This field was added in R1V7 7:2 software for digital networking. This field does not apply to AMIS analog networking or message
delivery, but it may be set to “y” on the local machine if digital networking is implemented.
This field was moved to this form in R1V7; in AUDIX R1V6 software, it is on the
system:appearance
form. This field does not apply to AMIS analog networking or message delivery on the local machine profile; it applies only to digital networking (if implemented on the local machine).
5. If you have changed any data in the fields, press or (F1).
6. Press to exit the form.
Ctrl-z

Task 2: Administer AMIS Loopback Test Mailbox (Optional)

This task is optional for AMIS analog networking and does not apply to message delivery. The loopback test mailbox is used to test the AMIS Analog Networking feature. Any message delivered to this mailbox causes a reply to be sent to the sending mailbox.
If remote users send an AMIS message to this mailbox, the local system sends a copy of the message to the message was received. The local loopback mailbox keeps a copy of the message header in its
To administer a loopback test mailbox:
RETURN
su l
on the path line to access the subscriber:local form. Press
.
1. Type
2. Tab to the name field and type an appropriate name (such as
3. Tab to the ext field and type a valid extension for a local mailbox ID.
incoming
outgoing
mailbox.
CHANGE RUN
mailbox of the remote user to indicate the
loopback
).
4. Verify the service options are correct (for example, check the community id field). Refer to the appropriate forms reference manual for details on this form if necessary.
5. Press (F2).
6. Press to exit the form.
ADD
Ctrl-z
AMIS Analog Networking
AUDIX Administration
3
585-300-512 Issue 7

Task 3: Administer AMIS Analog/Message Delivery Parameters

In order to implement the AMIS Analog Networking or Message Delivery features, certain parameters must be administered on the
analog network
require a system restart (Task 7).
form as described in this section. Changes to this form
May 1999
3-7Implementation
system:translation:
1. Type
sy tr an
on the path line. Press .
RETURN
Figure 3-2, the system:translation:analog network form (R1V8), shows the
most current version of this form. Figure 3-3, the system:translation:analog network form (R1V6/R1V7), shows how the form appeared prior to R1V8 software.
Localrl STATUS: alarms: none, logins: 1, thresholds: none
PATH: system : translation : analog network
Callback Numbers: country area/trunk local number Default - 1: 1 : 303 : 5552000 2: ____ : _______ : _______________ 3: ____ : _______ : _______________ 4: ____ : _______ : _______________ 5: ____ : _______ : _______________
AMIS analog networking incoming allowed (y/n)? y AMIS analog networking outgoing allowed (y/n)? y
AMIS prefix: 7 AMIS protocol - use 8 minutes for incoming msg length 0 (y/n)? y
AMIS loopback test mailbox extension: 57777
Error and confirmation information appears on this line.
CHANGE or RUN
ADD DELETE CLEAR
HELP
FORM
Figure 3-2. The system: translation: analog network Form (R1V8)
EXIT ENTERHELP FIELD
AMIS Analog Networking
AUDIX Administration
3
Localrl STATUS: alarms: none, logins: 1, thresholds: none
585-300-512 Issue 7
PATH: system : translation : analog network
callback number
country code: 1 area/trunk code: 303 local number: 5552000
AMIS analog networking incoming allowed (y/n)? y
AMIS analog networking outgoing allowed (y/n)? y
AMIS prefix: 7
AMIS protocol - use 8 minutes for incoming msg length 0 (y/n)? y
AMIS loopback test mailbox extension: 57777
May 1999
3-8Implementation
Error and confirmation information appears on this line.
CHANGE or RUN
ADD DELETE CLEAR
HELP
FORM
Figure 3-3. The system: translation: analog network Form (R1V6/R1V7)
2. Go through the following form fields by pressing the key, and change
TAB
any fields needed to implement the AMIS Analog Networking or Message Delivery features:
a. Callback Numbers (or callback number prior to R1V8)
This field applies only to AMIS analog networking.
EXIT ENTERHELP FIELD
AMIS Analog Networking
AUDIX Administration
3
585-300-512 Issue 7
May 1999
3-9Implementation
Enter the complete telephone number needed for the remote
machine to call the local system. The “local number” is the hunt group number assigned to the analog voice ports. The “country” code can have a maximum of four digits, the “area/trunk” code a maximum of seven, and the “local number” a maximum of 15. However, the
complete
callback number (country code, area/trunk code, and local number) cannot exceed 15 digits. A country code and an area/trunk number are always recommended and may be required. Some examples of country codes are:
If the local system is in the United States or Canada and
uses the public network, enter a 1 for the country code. (For Rolm systems, this field may need to be left blank.)
If you are in another country, enter the appropriate country
code (such as 44 for the United Kingdom). Country codes should be listed in your local phone book.
In AUDIX R1V7 7:2 or later software, enter a country code of
0
to allow the AUDIX system to work in a mixed-vendor environment over a private network. This code may be used for mixed-vendor, private networks in any country. (In AUDIX R1V6 or R1V7 7:1 software, a country code of “0” is not allowed.)
In AUDIX R1V8 software, up to five callback numbers may be defined. This allows different nodes to use different telephone numbers to call the same AMIS machine. For example, an AMIS analog network may include some nodes accessed over the public network, and other nodes accessed over a private network. Vendors other than Lucent Technologies may also require AMIS callback numbers to be administered in a particular way. The
list:machine
form shows which callback number is associated
with each remote AMIS machine. The default callback number is “1”. If a system with a single
callback number is upgraded to run R1V8 software, the existing callback number will be placed in the default selection “1”. If an additional callback number is defined on this form and then deleted, the AMIS callback no. field on the
system:translation:machine:audix/amis/call delivery
form for any remote node that used that number will automatically be changed to show the default callback number “1”. An entry will appear in the administration log whenever callback numbers are deleted or changed (refer to Chapter A,
"Administration Log Entries", for a complete list of AMIS
administration codes).
AMIS Analog Networking
AUDIX Administration
3
b. AMIS analog networking incoming allowed
c. AMIS analog networking outgoing allowed
585-300-512 Issue 7
May 1999
3-10Implementation
This field applies only to AMIS analog networking.
Set this field to “y” if you want the local system to accept incoming AMIS analog calls. Set this field to “n” if you want the local system to refuse incoming AMIS calls.
NOTE:
If you cannot set this field to “y”, the AMIS Analog Networking feature has
not
been activated by Lucent Technologies
personnel. Contact your Lucent Technologies representative.
This field applies to
both
AMIS analog networking and message
delivery. Set this field to “y” if you want the local system subscribers to send
AMIS analog networking and/or message delivery messages. Set this field to “n” if you want to prevent subscribers from sending AMIS analog networking and/or message delivery messages.
NOTE:
If you cannot set this field to “y”, the AMIS Analog Networking feature may not have been activated by Lucent Technologies per s onn el (check with your Lucent Technologies representative). Beginning in R1V8, a callback number is also required before this field can be set to “y”.
d. AMIS prefix
This field applies only to AMIS analog networking. You may enter an AMIS prefix to identify an address as an AMIS
analog address. If the address ranges defined for AMIS one- or two-step addressing do not overlap with any previously defined address ranges, it is not necessary to define an AMIS prefix. However, if any AMIS or message delivery address ranges overlap, you may need to administer an AMIS prefix to make the AMIS addresses unique.
NOTE:
If an AMIS prefix is defined, subscribers
must
dial the AMIS prefix when addressing AMIS analog messages. The AMIS prefix
must
precede any other digits in the address prefix(es)
that subscribers dial; these are specified on the
system:
translation:machine:audix/amis/call delivery
form.
AMIS Analog Networking
AUDIX Administration
3
e. AMIS protocol—use 8 minutes for incoming msg length 0?
585-300-512 Issue 7
May 1999
3-11Implementation
This field applies only to AMIS analog networking. Some non-Lucent Technologies remote voice mail systems cannot
specify the message length and use a zero (0) in the protocol. This field enables the local system to record these incoming messages as follows:
Enter
y
for the local system to assume an incoming message of unknown length is 8 minutes long (the maximum length allowed by the AMI S protocol specification).
Enter
n
if you do
not
want the local system to assume an incoming message of unknown length is 8 minutes long. In this case, the system uses the number in the message lengths, maximum (seconds) field on the
system:limits
form; AMIS messages longer than this system limit will not be accepted.
In either case, if an incoming message’s assumed length is longer than the space currently available in a subscriber’s mailbox, delivery of the message will be aborted.
f. AMIS loopback test mailbox extension
This field applies only to AMIS analog networking. If you administered an AMIS loopback mailbox in Task 2, enter the
extension for the test mailbox in this field.
3. If you have changed any data in the fields, press or (F1).
CHANGE RUN
To activate the changes, you need to restart the system (done in Task 7).
4. Press to exit the form.
Ctrl-z
AMIS Analog Networking
AUDIX Administration
3
585-300-512 Issue 7

Task 4: Administer Outcalling Periods

The AMIS Analog Networking and Message Delivery features use the outcalling ports to deliver messages. Although outcalling periods must be administered, the Outcalling feature itself does networking or message delivery to work.
NOTE:
For more efficient use of system resources, the system administrator may wish to limit the times of day for sending AMIS analog networking or message delivery messages to those which are known to be less busy.
To administer outcalling periods and the maximum number of ports to use for AMIS analog networking and/or message delivery calls:
not
need to be active for AMIS analog
May 1999
3-12Implementation
1. Typ e
sy o
on the path line. Press .
RETURN
See Figure 3-4, the system:outcalling form, for a sample of this form.
Localrl STATUS: alarms: none, logins: 1, thresholds: none
PATH: system : outcalling
outcalling active (y/n)? n
start end interval maximum time time simultaneous (hh:mm) (hh:mm) (hh:mm) ports 1: 18:00 07:59 00:30 5 2: 08:00 17:59 00:15 2 3: __:__ __:__ __:__ ___
initial delay (mins): __ maximum number digits: __
Error and confirmation messages appear here.
CHANGE or RUN
ADD DELETE CLEAR
Figure 3-4. The system: outcalling Form
HELP
FORM
EXIT ENTERHELP FIELD
AMIS Analog Networking
AUDIX Administration
3
585-300-512 Issue 7
May 1999
3-13Implementation
2. Go through the following form fields by pressing the key, and change
TAB
any fields needed to implement the AMIS Analog Networking or Message Delivery features:
a. Outcalling active
Enter n if you want to use the AMIS Analog Networking and/or Message Delivery features and do
not
want to activate the
Outca lling feature. Enter y if you want to use the Outcalling feature
in addition to
AMIS analog networking and/or message delivery.
b. Start time/end time
Specify at least one start time and one end time to implement AMIS analog networking and/or message delivery. Up to three cycles (periods of time) may be specified. The sum of the cycles must be less than 24 hours; a cycle may span midnight, but may not overlap another cycle.
NOTE:
The AMIS analog networking and message delivery transmission times specified on the
translation:machine:audix/amis/call delivery
system:
form must be equal to or a subset of the outcalling periods specified here. Make a note of the outcalling cycle(s).
c. Interval
This field does
not
apply to AMIS analog networking or message delivery; these intervals apply only to the Outcalling feature (if activated). Use the
system:appearance
form to administer the intervals for AMIS analog networking and/or message delivery (done in Task 6).
d. Maximum simultaneous ports
Specify the maximum number of ports that may be used simultaneously for outcalling, AMIS analog networking, and/or message delivery during the specified cycle. You may need to increase this number if you were previously using the Outcalling feature and are now adding the AMIS Analog Networking and/or Message Delivery features. See the "Voice Port Needs" section in
Chapter 2, "Planning and Design"
,
for more information.
e. Initial delay
This field does
not
apply to AMIS analog networking or message
delivery; it applies only to the Outcalling feature (if activated).
f. Maximum number digits
This field does
not
apply to AMIS analog networking or message
delivery; it applies only to the Outcalling feature (if activated).
AMIS Analog Networking
AUDIX Administration
3
585-300-512 Issue 7
May 1999
3-14Implementation
3. If you have changed any data in the fields, press or (F1). To activate the changes, you need to restart the system (done in Task 7).
4. Press to exit the form.
Ctrl-z

Task 5: Adjust System Limits

For either the AMIS Analog Networking or Message Delivery features, you may have to adjust system limits to accommodate additional administered remote subscribers and/or message delivery recipients. Only remote users on systems administered for AMIS one-step addressing or message delivery recipients may be administered on the local system.
Task 5A: Calculate New Filesystem Sizes
In order to adjust system limits and filesystem sizes correctly, follow these steps:
1. Type
tr f d
on the path line to access the
Press .
RETURN
a. Press (F8) to bring up the current day’s traffic. The screen
ENTER
then populates the fields.
b. Record the number displayed in the subscribers, local field. You
might consider adding the number of local subscribers that you expect to administer over the next twelve months to the number shown on the form.
CHANGE RUN
traffic:feature:day
form.
c. Record the number of remote and non-administered remote
subscribers. This number includes remote digital networking subscribers, remote AMIS analog users, and message delivery recipients, if any are already administered. Add the number of remote subscribers you plan to administer to the total shown here.
d. Press to exit the form.
2. Type
RETURN
sy li
Ctrl-z
on the path line to access the
.
system:limits
See Figure 3-5, the system:limits form, for a sample of this form.
form. Press
AMIS Analog Networking
AUDIX Administration
3
Localrl STATUS: alarms: none, logins: 1, thresholds: none
585-300-512 Issue 7
PATH: system : limits
message lengths, maximum (seconds): ____ minimum (tenths of seconds): __
subscribers, local: 2000 administered remote: 14000
lists, total entries: _____ lists/subscriber: __ recipients/list: ___
error log entries (maximum): _____ admin log entries (maximum): ____
activity log entries (maximum): _____
messages, total in all mailboxes: ______ awaiting delivery: ______
RECOMMENDED FILESYSTEM SIZES (IN BLOCKS), BASED ON LIMITS
system data: system status: voice data : names:
May 1999
3-15Implementation
Error and confirmation information appears on this line.
CHANGE or RUN
ADD DELETE CLEAR
HELP
Figure 3-5. The system: limits Form
3. Go through the following form fields by pressing the key, and change any fields needed to implement the AMIS Analog Networking or Message Delivery features:
a. Message lengths, maximum (seconds)
If you set the amis protocol - use 8 minutes for incoming msg length
0? field to “n” on the
system:translation:analog network
form, the number in this field shows the maximum length an incoming AMIS message can be for the local system to accept it.
b. Subscribers, local
Enter the expected number of local subscribers (use the data from step 1b). The maximum number allowed is 4000.
FORM
EXIT ENTERHELP FIELD
TAB
AMIS Analog Networking
AUDIX Administration
3
c. Subscriber, administered remote
585-300-512 Issue 7
May 1999
3-16Implementation
Enter the number of administered remote subscribers that are expected for the entire network (use the data from step 1c). This number includes administered subscribers on remote digitally networked systems, administered remote users on remote systems administered for AMIS one-step addressing, and administered message delivery recipients. The maximum number allowed is
28000.
NOTE:
Do not put in a larger number than necessary. F ilesystem size requirements increase when the number of administered remote subscribers is increased. Also, if the send to
non-administered recipients field is set to “y”, setting the administered remote field to 28,000 leaves no room for nonad m ini s tered (unknown) subscribers to be ad ded.
4. If you changed any of these fields, press or (F1) to calculate new filesystem sizes.
5. Record the RECOMMENDED FILESYSTEM SIZES for the four filesystems at the bottom of the form or print this screen.
6. Press to exit the form.
Ctrl-z
Task 5B: Compare the Recommended Sizes to the Actual Sizes
To determine if the current filesystem sizes will accommodate the new system limits of subscribers, do the following:
1. Typ e
2. Tab to the volume field and type the name of the disk containing the
3. Compare the recommended filesystem sizes from the
4. Press to exit the form.
f l
on the path line to access the
RETURN
.
filesystems you want to display. (If you have more than one hard disk, you need to display this screen for each volume.)
form to the actual sizes shown on the screen. The recommended values project worst-case situations, so if the actual sizes of the filesystems are close, it is probably not necessary to change them now.
Ctrl-z
CHANGE
RUN
filesystem:list
system:limits
form. Press
— If you do
not
need to adjust filesystem sizes, go to Task 6.
— If you need to increase filesystem sizes, go to the next section.
AMIS Analog Networking
AUDIX Administration
3
585-300-512 Issue 7
Task 5C: Increase Filesystem Sizes
To increase the size of one or more filesystems, you need to shut the system down. At an appropriate time, do the following steps:
May 1999
3-17Implementation
1. Typ e sh on the path line to access the shutdown form and press .
2. Set types to “c” (camp-on) and reason to “a” (administration). Press
CHANGE RUN
3. Exit the form, then type
filesystem:detail
or (F1) and wait for a successful shutdown.
f d
on the path line to access the
form. Press .
RETURN
4. In the filesystem field, type the name of the filesystem to be increased (for example,
disk00.sd
). Press .
5. Enter the type of filesystem in the type field (for example,
ENTER
.
TAB
sdat
). Press
6. Tab to the size field and overwrite the current size with the new recommended size. Press or (F1).
7. Press to exit the form.
Ctrl-z
CHANGE RUN
If a disk doesn’t have enough free space to allow a filesystem’s size to be increased:
1. Check the other hard disks (disk00 or disk02 through disk06) for available space using the
list:volume names
form.
2. If you locate a volume with sufficient space, do a physical copy of the filesystem from the original disk to the new disk using the
filesystem:copy
form.
RETURN
NOTE:
If you cannot find available space on any of the other hard disks, consider contacting your remote maintenance service center to determine if any filesystems can be decreased in size (this may involve a fee), or make arrangements with your account team to purchase an additional hard disk.
3. Delete the original filesystem from the original disk using the
filesystem:detail
form, then increase the size of the new filesystem
to its recommended value as described in the previous section.
4. Update the location, then execute the
system:filesystems
filesystem:update configuration
form to indicate the filesystem’s new
form.
AMIS Analog Networking
AUDIX Administration
3
585-300-512 Issue 7

Task 6: Administer Retransmission Intervals

The local system makes three attempts to deliver AMIS analog networking messages and six attempts to deliver message delivery messages. If all delivery attempts fail, the sender is notified through a new voice mail message that the message could not be delivered.
NOTE:
On R1V6 systems, the send to non-administered recipients field appears on this form. See the description of this field under the
translation:machine:audix/amis/call delivery
"Task 1: Display the Local Machine" section.
To administer the intervals at which the local system should attempt to send AMIS analog networking and/or message delivery messages, follow these steps:
May 1999
3-18Implementation
system:
form in the
1. Typ e
sy ap
on the path line to access the
Press .
RETURN
system:appearance
form.
See Figure 3-6, the system:appearance form (R1V 7/R 1V 8), for a sample of this form. In R1V6, this form looked slightly different.
Localrl STATUS: alarms: none, logins: 1, thresholds: none
PATH: system : appearance
login retries: 3 consecutive invalid login attempts: 18 system guest password: _______________ minimum password length: 0 input time limits (seconds), normal: 99 wait (*W): 180 full mailbox timeout (seconds) : 5 dial tone detect (y/n)? y name recorded by subscriber (y/n)? y flash transfer delay (seconds): 2 multiple personal greetings (y/n)? y tone detect interval (l/s): l increment (l/s), rewind: s advance: s traffic collection (y/n)? y prime time (24 hour clock), start: 0800 end: 1700 end of message warning, active (y/n)? y time (seconds): 15
call transfer out of AUDIX feature (y/n)? n enhanced call transfer (y/n)? n covering
extension: ________ ‘0’ calls follow coverage (y/n)? n broadcast mailbox extension: transfer access code: _____
rescheduling increments incr1: 0__ days 0__ hrs 5__ min incr2: 0__ days 0__ hrs 15_ min incr3: 0__ days 0__ hrs 30_ min incr4: 0__ days 1__ hrs 0__ min incr5: 0__ days 2__ hrs 0__ min incr6: 0__ days 6__ hrs 0__ min incr7: 1__ days 0__ hrs 0__ min incr8: 2__ days 0__ hrs 0__ min incr9: 7__ days 0__ hrs 0__ min incr10: 14_ days 0__ hrs 0__ min
Error and confirmation messages appear here.
CHANGE or RUN
ADD DELETE CLEAR
HELP
Figure 3-6. The system: appearance Form (R1V7/R1V8)
FORM
EXIT ENTERHELP FIELD
AMIS Analog Networking
AUDIX Administration
3
2. Check the rescheduling increments near the bottom of the form. The incr1 through incr5 fields define how long the local system waits
before attempting to retransmit messages that could not be delivered on the original attempt.
For AMIS Analog Networking, the system attempts to send the message once at the specified delivery time (usually immediately). If it is not successful, it uses the intervals specified in incr1 and incr2 for its second and (if needed) third attempts. When the system has made three unsuccessful attempts, the message is marked as undeliverable and the sender is notified through a new voice mail message.
For Message Delivery, the system attempts to send the message once at the specified delivery time (usually immediately). If it is not successful, it uses the intervals specified in incr1, incr2, incr3, incr4, and incr5 for a total of six attempts (if needed). When the system has made six unsuccessful attempts, the message is marked as undeliverable and the sender is notified through a new voice mail message.
585-300-512 Issue 7
May 1999
3-19Implementation
3. If you changed any rescheduling increments, press or (F1).
4. Press to exit the form.
Ctrl-z

Task 7: Restart the AUDIX System

To activate feature changes you made during the implementation phase, you should restart the system.
NOTE:
If this is a new AMIS analog networking or message delivery system, you may want to perform Task 8 initial AMIS analog networking/message delivery implementation ensures the network is brought up cleanly.
Select an appropriate time to bring the system out of service, then do the following:
1. Type st on the path line to access the startup form. Press .
2. To restart the system, press or (F1).
3. After the system reinitializes, you have to log back in to do further administration.
CHANGE RUN
before
Task 7. A system restart at the end of
CHANGE RUN
RETURN
AMIS Analog Networking
CHANGE
AUDIX Administration
3
If the network is already running and you made minor adjustments to the previous feature forms (for example, if you change some minor parameters but did not activate or deactivate the AMIS Analog Networking, Message Delivery, or Outcalling feature), you can run the following audits to activate the changes without needing to restart the system:
585-300-512 Issue 7
May 1999
3-20Implementation
1. Type
m au f
on the path line to access the
form. Press .
RETURN
2. Tab to the Service Dispatcher field and type an x. Tab to the start field and type an x, then press or (F1) to run the audit.
CHANGE RUN
3. When the audit completes, blank out the “x” in the Service Dispatcher
field.
4. Tab to the Network Data field and type an x. Tab to the start field and type an x, then press or (F1) to run the audit.
5. Press to exit the form.
Ctrl-z
RUN

Task 8: Administer Remote Machines/Telephone Numbers

Remote Networking feature) or they can be remote telephone numbers (for the Message Delivery feature). You can administer a single remote AMIS analog voice mail system, a range of remote AMIS analog voice mail systems, a single message delivery telephone number, or a range of message delivery telephone numbers as needed.
Use the form to define remote AMIS analog voice mail systems or message delivery telephone numbers. You also use this form to make changes to a remote machine profile, or to delete (remove) a remote machine from the network.
machines
can be remote voice mail systems (for the AMIS Analog
system:translation:machine:audix/amis/call delivery
maintenance:audits:fp
The following figures show examples of different remote machine setups. Refer to your notes from Chapter 2, "Planning and Design" to determine which systems should be administered for a specific type of addressing. The forms shown are from the R1V8 software release; on earlier software loads, the forms look slightly different.
Figure 3-7, Digital Networking to a Specific Machine, shows the profile of a
remote machine named “digit” administered for digital networking. If a local system uses both digital and analog networking, the address ranges must not overlap, even though they use different transmission facilities. This figure is provided for comparison purposes.
AMIS Analog Networking
AUDIX Administration
3
Figure 3-8, AMIS Casual Addressing to Local Numbers, shows how to
administer all local 7-digit numbers for AMIS casual (two-step) addressing.
— Because an AMIS prefix “7” was administered on the
— The AMIS message transmission schedule is limited to the normal
Figure 3-9, AMIS Pre-Administered Addressing to a Specific Machine,
shows the profile of a remote system administered for AMIS pre-administ ered (one-step) add ressin g.
— The first address range is required to identify the remote system to
585-300-512 Issue 7
system:translation:analog network
form, subscribers
May 1999
3-21Implementation
must dial this prefix before the other 7 digits needed for local message addressing.
business day. The time shown is a subset of the transmission cycles specified on the
system:outcalling
form.
the local system. Because the remote machine uses the same country code as the local system, the country code was omitted. However, because the remote machine has a different area code, this code
must
appear in the address range to uniquely identify the hunt group of the remote machine. If the remote machine was in a private network, the network-access code and hunt group for the remote machine would appear in the address prefix list instead.
— The next address ranges specify the digits the local subscribers
dial to address messages to this remote machine. Each address prefix begins with the AMIS prefix “7” that was administered on the
system:translation:analog network
form. In this example, subscribers may dial the AMIS prefix and full telephone number as if they were using the public network, or they can dial just the AMIS prefix followed by the 5 digits needed to specify a remote mailbox. They could also dial the non-numeric addressing prefix “7ch” (for chic ago).
— The system administrator has blocked local subscribers from
sending messages to nonadministered remote recipients in order to control long-distance calls. The system administrator must therefore locally administer all remote recipients on this machine who need to receive AMIS messages.
AMIS Analog Networking
AUDIX Administration
3
Figure 3-10, Message Delivery Addressing to Local Numbers, shows how
585-300-512 Issue 7
to administer all local numbers for the Message Delivery feature. The
address prefix “6” has been selected to help subscribers distinguish between the AMIS Analog Networking and Message Delivery features, and to make both local address ranges unique.
Localrl STATUS: alarms: none, logins: 1, thresholds: none
PATH: system : translation : machine : audix/amis/call delivery
machine name: digit_____ local/remote: r password: remote1_ ext length: 4 voiced name (y/n)? y voice id: 2 AMIS callback no.: _ (1, 2, 3, 4, or 5) default community: 1 connection type: rs232a data rate: 1200 channel: 5 dial string: 912015556000 address ranges (prefix start / end extension) warnings 1: 201555_______________ 6000______ / 6000______ 2: _____________________ 6001______ / 6999______ 3: _____________________ __________ / __________ 4: _____________________ __________ / __________ 5: _____________________ __________ / __________ 6: _____________________ __________ / __________ 7: _____________________ __________ / __________ 8: _____________________ __________ / __________ 9: _____________________ __________ / __________ 10: ____________________ __________ / __________ message transmission schedule (hh:mm)
1. start: 18:00 end: 23:59 interval: 01:00 updates (y/n)? in y out y
2. start: __:__ end: __:__ interval: __:__ network turnaround (y/n)? y
3. start: __:__ end: __:__ interval: __:__ log connect events (y/n)? y new machine name: ______________ send to non-administered recipients (y/n)? n
May 1999
3-22Implementation
Error and confirmation information appears on this line.
CHANGE or RUN
ADD DELETE CLEAR
HELP
Figure 3-7. Digital Networking to a Specific Machine
FORM
EXIT ENTERHELP FIELD
AMIS Analog Networking
AUDIX Administration
3
Localrl STATUS: alarms: none, logins: 1, thresholds: none
585-300-512 Issue 7
PATH: system : translation : machine : audix/amis/call delivery
machine name: localnums_ local/remote: r password: ________ ext length: 7 voiced name (y/n)? y voice id: 3 AMIS callback no.: 1 (1, 2, 3, 4, or 5) default community: 1 connection type: amisac data rate: _____ channel: _ dial string: 9 address ranges (prefix start / end extension) warnings 1: 7____________________ 0000000___ / 9999999___ 2: _____________________ __________ / __________ 3: _____________________ __________ / __________ 4: _____________________ __________ / __________ 5: _____________________ __________ / __________ 6: _____________________ __________ / __________ 7: _____________________ __________ / __________ 8: _____________________ __________ / __________ 9: _____________________ __________ / __________ 10: ____________________ __________ / __________ message transmission schedule (hh:mm)
1. start: 08:00 end: 17:59 interval: __:__ updates (y/n)? in n out n
2. start: __:__ end: __:__ interval: __:__ network turnaround (y/n)? n
3. start: __:__ end: __:__ interval: __:__ log connect events (y/n)? n new machine name: ______________ send to non-administered recipients (y/n)? y
May 1999
3-23Implementation
Error and confirmation information appears on this line.
CHANGE or RUN
ADD DELETE CLEAR
HELP
Figure 3-8. AMIS Casual Addressing to Local Numbers
FORM
EXIT ENTERHELP FIELD
AMIS Analog Networking
AUDIX Administration
3
Localrl STATUS: alarms: none, logins: 1, thresholds: none
585-300-512 Issue 7
PATH: system : translation : machine : audix/amis/call delivery
machine name: chicago___ local/remote: r password: ________ ext length: 4 voiced name (y/n)? y voice id: 4 AMIS callback no.: 1 (1, 2, 3, 4, or 5) default community: 1 connection type: amisap data rate: _____ channel: _ dial string: 917082225000 address ranges (prefix start / end extension) warnings 1: 708222_______________ 5000______ / 5000______ 2: 7____________________ 5001______ / 5999______ 3: 7708222______________ 5001______ / 5999______ 4: 7ch__________________ 5001______ / 5999______ 5: _____________________ __________ / __________ 6: _____________________ __________ / __________ 7: _____________________ __________ / __________ 8: _____________________ __________ / __________ 9: _____________________ __________ / __________ 10: ____________________ __________ / __________ message transmission schedule (hh:mm)
1. start: 08:00 end: 17:59 interval: __:__ updates (y/n)? in n out n
2. start: __:__ end: __:__ interval: __:__ network turnaround (y/n)? n
3. start: __:__ end: __:__ interval: __:__ log connect events (y/n)? n new machine name: ______________ send to non-administered recipients (y/n)? n
May 1999
3-24Implementation
Error and confirmation information appears on this line.
CHANGE or RUN
ADD DELETE CLEAR
HELP
FORM
Figure 3-9. AMIS Pre-Administered Addressing to a Specific Machine
EXIT ENTERHELP FIELD
AMIS Analog Networking
AUDIX Administration
3
Localrl STATUS: alarms: none, logins: 1, thresholds: none
585-300-512 Issue 7
PATH: system : translation : machine : audix/amis/call delivery
machine name: localmd___ local/remote: r password: ________ ext length: 7 voiced name (y/n)? y voice id: 5 AMIS callback no.: 1 (1, 2, 3, 4, or 5) default community: 1 connection type: calld data rate: _____ channel: _ dial string: 9 address ranges (prefix start / end extension) warnings 1: 6____________________ 0000000___ / 9999999___ 2: _____________________ __________ / __________ 3: _____________________ __________ / __________ 4: _____________________ __________ / __________ 5: _____________________ __________ / __________ 6: _____________________ __________ / __________ 7: _____________________ __________ / __________ 8: _____________________ __________ / __________ 9: _____________________ __________ / __________ 10: ____________________ __________ / __________ message transmission schedule (hh:mm)
1. start: 08:30 end: 17:00 interval: __:__ updates (y/n)? in n out n
2. start: __:__ end: __:__ interval: __:__ network turnaround (y/n)? n
3. start: __:__ end: __:__ interval: __:__ log connect events (y/n)? n new machine name: ______________ send to non-administered recipients (y/n)? y
May 1999
3-25Implementation
Error and confirmation messages appear here.
CHANGE or RUN
ADD DELETE CLEAR
HELP
Figure 3-10. Message Delivery Addressing to Local Numbers
To add, delete, or change a remote machine profile, do the following:
1. Typ e
sy tr m au
on the path line to access the
machine:audix/amis/call delivery
form. Press .
2. In the machine name field, type the name of the remote voice mail system you plan to administer and press . If this is a new (unassigned)
ENTER
machine name, the system displays a message informing you the machine does not exist.
— To add a new machine to the network, complete the following steps.
not
A system restart is
necessary if you add one or more remote
machines to an already active network.
— To change an existing machine’s profile, complete the following
steps. A system restart is
not
necessary if you modify the profile of
a machine that is already part of the network.
— To delete a remote machine, verify that this is the correct profile you
intend to remove from the network, then press (F3). Once deleted, a machine must be re-administered to be added back to the network.
FORM
EXIT ENTERHELP FIELD
system:translation:
RETURN
DELETE
AMIS Analog Networking
AUDIX Administration
3
585-300-512 Issue 7
May 1999
3-26Implementation
3. Go through the following form fields by pressing the key, and change
TAB
any fields needed to implement the AMIS Analog Networking and/or Message Delivery features:
a. Local/remote
This display-only field shows r after the remote machine is administered.
b. Password
This field does not apply to AMIS analog networking or message delivery (it is used for digital networking only).
c. Ext length (or extension length prior to R1V8)
The extension length depends on the feature you are administering. Valid entries are the digits 3 through 10.
— For an amisac connection type (AMIS casual or two-step
addressing), this field specifies how many digits entered by subscribers for an AMIS address are actually dialed by the local system. For example, if the extension length is “7”, the local system dials the dial string (if any) followed by the last seven digits of the number a subscriber enters as the AMIS address to the remote voice mail system (
not
the remote
mailbox ID). The AMIS prefix is not dialed.
— For an amisap connection type (AMIS pre-administered or
one-step addressing), this field specifies the number of digits required to identify a remote mailbox ID (the extension length typically matches the extension length of the remote switch).
— For a calld connection type (message delivery), this field
specifies how many digits entered by subscribers for a message delivery address are actually dialed by the local system. For example, if the extension length is “10”, the local system dials the dial string (if any) followed by the last ten digits of the number a subscriber enters as a message delivery address.
d. Voiced nam e
This field indicates “n” for a new machine (a name for this machine has not yet been recorded). This field is automatically set to “y” when you record a name for this machine. To delete a name that was previously recorded, set this field to “n”. (If you delete a name using this form, you must re-record it to change the field back to “y”.)
AMIS Analog Networking
AUDIX Administration
3
e. Voice id
f. AMIS callback no.
g. Default community
585-300-512 Issue 7
May 1999
3-27Implementation
This display-only field is blank until you have successfully added this remote machine. The system then automatically assigns a number that it associates with the name fragment for this remote machine. This identifier is used when recording the name of the remote system.
This field appears on R1V8 systems only. Enter the number from 1 to 5 corresponding to the callback number for this remote AMIS machine; callback numbers are defined on the
translation:analog network
form. T h ese ex amples show t he
system:
default callback number “1”. When the local system delivers an AMIS message to this remote machine, it will use this callback number in the protocol.
The default community for users of this remote machine. A community consists of those subscribers who are able to exchange voice mail messages as permitted on the
system:sending
restrictions form. This value can be overridden for individual subscribers on the
subscriber:remote
subscriber:local
form.
or the
h. Connection type (or network connection type prior to R1V8)
This field informs the local system how to contact this remote system or number.
— Enter — Enter
amisac amisap
for AMIS casual (two-step) addressing.
for AMIS pre-administered (two-step)
addressing.
— Enter
calld
for a message delivery destination or a range of
message delivery destinations.
i. Data rate
This field does not apply to AMIS analog networking or message delivery and must be left blank (it is used for digital networking only).
j. Channel
This field does not apply to AMIS analog networking or message delivery and must be left blank (it is used for digital networking only).
AMIS Analog Networking
AUDIX Administration
3
k. Dial string
585-300-512 Issue 7
May 1999
3-28Implementation
Type the string the local system should dial in order to send messages to this remote machine. Valid entries vary for different network connection types as follows:
— amisac (optional): For an amisac connection type (AMIS
casual or two-step addressing), the dial string is optional. If used, it may be from 0 to 24 characters and consists of any numbers the system should prepend to the number subscribers dial to reach a specific address. The dial string plus the extension must be less than or equal to 29 characters.
For a range of local numbers, the dial string might be “9” (or whatever trunk-access code or dial-access code is assigned to reach the public network). For example, if the extension length is “7” and a subscriber specifies a valid 7-digit address (such as 555-6000), the local system would dial “95556000” to reach the remote machine.
For a range of long-distance numbers, the dial string would normally be “91” in the United States (the trunk- or dial-access code followed by “1”). For example, if the extension length is “10” and a subscriber specifies a valid 10-digit address (such as 201-555-6000), the local system would dial “912012225000” to reach the remote system.
— amisap (required): For an amisap connection type (AMIS
pre-administered or one-step addressing), the dial string is required. It can be up to 65 characters long, and typically consists of the trunk-access code or dial-access code needed to reach the public or private network, followed by the complete telephone number of the remote machine. For example, in Figure 3-9, AMIS Pre-Administered Addressing to a Specific Machine, the local system would dial “912012225000” to reach the remote system.
— calld (optional): For a calld connection type (message
delivery), the optional dial string is defined in the same manner as for AMIS two-step addressing (refer to the amisac description).
NOTE:
You can instruct the local system to pause for a specified length of time by entering
“P”
(including
quotes) in the dial string. A single “P” causes the system to pause approximately 1.5 seconds; a “P” followed by a digit from 1 to 9 causes the system to wait the specified amount of time. For example, if dial string is 9”P2”55560 00, the local sys tem dials 9, waits about 3 seconds, then dials 5556000.
AMIS Analog Networking
AUDIX Administration
3
l. Address ranges
585-300-512 Issue 7
May 1999
3-29Implementation
Administer the address ranges for the remote machines or individual remote telephone numbers according to the plan you worked out inChapter 2, "Planning and Design". The total address range (prefix plus extension) can be up to 24 characters long.
— Address prefix (optional): For the address prefixes you want
subscribers to dial, the first digit of the prefix field
must
match the AMIS prefix field (if you entered a prefix on the
system:translation:analog network
form). Additionally, the prefix may contain a country code and/or area code or the mnemonic for a remote location (0 to 21 alphanumeric characters may be entered). For example, if the AMIS prefix is “7”, the address prefix could be “7201”.
Generally, prefixes are
not
recommended in a DCS network. Otherwise, address prefixes are recommended to help subscribers distinguish among remote voice mail systems (the address prefix is typed by subscribers whenever they address an AMIS analog networking and/or message delivery message).
In addition to the address ranges that specify the digits that
subscribers
must enter, the local system also requires an address range that uniquely identifies the hunt group number (callback number) of the remote voice mail system. If the remote machine has a different country code, the address range must contain the country code, area/trunk code, and hunt group. If the remote machine has a different area or trunk code, only the area/trunk code and hunt group are needed (the country code should be omitted). If the remote system is local, only the hunt group number should appear for that machine. If the remote machine can be accessed through a private network, the network-access code and hunt group for the remote machine should appear in the address prefix list instead.
— Address extensions (required): Enter the numbers that
define the mailbox extensions that can be used on the remote system or the remote telephone numbers you want local subscribers to access in the start and end extension fields. Valid entries can be from 3 to 10 digits.
Up to ten different ranges can be specified. The length of the start and end extensions must agree with the number shown in the ext length field (leading zeros may be needed to conform to this requirement). The end extension must be equal to or greater than the start extension. If you specify the same number as the starting and ending extension, a unique machine or telephone number is specified (this is usually used to identify the hunt group number of a remote machine).
AMIS Analog Networking
AUDIX Administration
3
m. For a new remote profile: When you have finished entering the dial
n. Message transmission schedule
585-300-512 Issue 7
May 1999
3-30Implementation
AMIS address ranges and message delivery address ranges must be unique; they cannot overlap with digital networking address ranges or other AMIS analog networking and/or message delivery address ranges. See Chapter 2, "Planning and Design", for details.
NOTE:
The warnings field indicates when a duplicate or overlapping range is being assigned. If you get a warning message, di splay the
system:translation:address
form to check which extension numbers are in use, then refer to Chapter 2,
"Planning and Design", to select appropriate ranges.
string, press (F2) to create and save the remote machine
ADD
profile. Continue with the following fields.
Enter the hours and minutes in the start and end fields to specify one or more cycles (time periods) when the local system should attempt to send messages to this remote machine. Valid entries are times from 00:00 to 23:59.
Up to three cycles can be defined for each remote system. Cycles may be assigned to avoid toll facilities or periods of heavy traffic if desired. The total time of the cycles cannot exceed 24 hours. Cycles cannot overlap. A cycle can span across midnight.
NOTE:
The times specified must be equal to or a subset of the outcalling transmission times administered on the
system:outcalling
form or the AMIS and/or message delivery messages will never be sent. For instance, if you schedule AMIS and message delivery messages to be sent anytime during a 24-hour period (00:00 to 23:59), but outcalling periods are only scheduled from 07:00 to 18:00, the AMIS and message delivery messages will only be sent between the hours of 7:00 AM and 6:00 PM.
The interval fields on this form are used for digital networking only and do
not
apply to AMIS analog networking or message delivery; if intervals are specified here, they will be ignored. If all the outcalling ports are busy , the system retries in one minute. If an outcalling port is available, but for some reason the system cannot deliver the message, the system uses the rescheduling increments specified on the
system:appearance
form.
AMIS Analog Networking
AUDIX Administration
3
o. Updates in/updates out
p. Network turnaround (y/n)?
q. Log connect events (y/n)?
585-300-512 Issue 7
May 1999
3-31Implementation
AMIS message delivery is done in packets of 9 to satisfy the AMIS standard. Prior to R1V7 7:2, however, the system did not immediately reschedule any messages still left in the queue for immediate delivery, but waited until the next transmission interval scheduled on the
system:appearance
form. On R1V7 7:2 and later systems, any messages left in the queue are rescheduled for immediate delivery after the first 9 are transmitted. The local AMIS system calls the remote system again within 2 minutes and transmits any additional AMIS messages it may have queued.
These fields do not apply to AMIS analog networking or message delivery (they are used for digital networking only).
This field does not apply to AMIS analog networking or message
delivery and should be set to “n” (it is used for digital networking only).
This field was added in R1V7 7:2 software. It does not apply to AMIS analog networking or message delivery and should be set to “n” (it is used for digital networking only).
r. Send to non-administered recipients (y/n)?
This field was moved to this form in R1V7; in AUDIX R1V6 software, it is on the
system:appearance
form.
If this field is set to “y” (the default), when a subscriber addresses a message to a remote extension that does not map to an address known by the local system, the local system adds this potential subscriber to its data base, then sends the message to every remote system in the network for which the address is valid. If a valid remote recipient cannot be found, the subscriber record is deleted eventually by one of the system audits and the local system changes the status of the message from
undeliverable
in the sender’s outgoing voice mailbox.
undelivered
to
For AMIS one-step systems and message delivery: If this field is set to “n”, subscribers can only send messages to administered remote subscribers. If a subscriber enters a valid extension or telephone number (but one which has not been administered), the subscriber is notified that the entry is invalid.
AMIS Analog Networking
AUDIX Administration
3
585-300-512 Issue 7
May 1999
3-32Implementation
For AMIS two-step systems: This field should be set to “y” because all remote subscribers on these systems are nonadministered. However, setting the field to “n” has no effect on AUDIX R1 systems (messages are still delivered).
NOTE:
Permitting subscribers to send messages to nonadministered recipients may have a significant impact on the network, causing extra or unnecessary calls to other systems and loading the local subscriber data base with unneeded records. If the network is kept up-to-date, change this field to “n” to reduce the system load. Often, messages to nonad m ini s tered rec ipients simply indicate a misdialed numb er.
4. If you have changed any data in the fields, press or (F1). Any changes or additions to this form are put into use immediately.
5. Press to exit the form.
Ctrl-z

Task 9: Record Remote Machine Names (Optional)

The name of each remote voice mail system, telephone number, or range of machines and/or numbers may be recorded using your telephone. The local system voices these names when local subscribers address messages to this machine, or when they receive messages from remote subscribers whose names are not recorded or who are not administered.
To record remote voice mail system or telephone machine names:
1. Verify you have announcement-control permission by typing path line to access the
2. Tab to the ext field and type your extension number. Press (F8).
3. Verify the permissions, announcement field is set to “y”. If it is not, enter y now and press or (F1). Otherwise, press
to exit the form.
Ctrl-z
RETURN
l m
on the path line to access the
.
4. Type
subscriber:local
form. Press .
CHANGE RUN
list:machines
CHANGE
RUN
su l
on the
RETURN
ENTER
form. Press
5. Press (F8) to display all machines.
ENTER
6. Either print this screen, write down the voice IDs associated with each remote machine, or leave this form on the screen as you record names.
NOTE:
Some remote machine profiles are used for a
range
of machines. Either voice a name that is meaningful for all machines in the range, or do not voice a name for these profiles.
AMIS Analog Networking
9
AUDIX Administration
3
7. From a touch-tone telephone, log into the local AUDIX machine using the extension that has announcement-control permissions.
8. From the activity menu, press to perform system administration.
585-300-512 Issue 7
May 1999
3-33Implementation
9. Press to record machine names.
6
10. Using the touch-tone keypad, enter the voice ID for the first remote machine and press .
#
11. At the tone, speak the remote machine’s name.
12. Press or (as prompted) to approve the name, or press if
#
you wish to delete and re-record it.
#
*
NOTE:
An R1V8 system with the standard announcement set prompts you to press to approve names and messages, while an R1V8
#
traditional system prompts you to press for these functions. On an R1V8 system, either command will work. Prior to R1V8, only the command will work.
#
*
13. Repeat steps 10 through 12 for each remote system or telephone number name.
14. When you are finished, press to return to the activity menu, or just hang up to exit the system.

Task 10: Administer Remote Subscribers (Optional)

D
*
#
*
R
Remote subscribers on systems administered for AMIS one-step addressing or digital networking may be administered on the local system. Message Delivery recipients may also be administered on the local system. Because each remote subscriber must be manually administered on the local machine, you may wish to administer only those remote subscribers who are regular AMIS analog networking and/or message delivery recipients. This task is optional.
NOTE:
Remote users on systems administered for AMIS two-step addressing
cannot
be administered on the local system.
To administer remote subscribers on the local machine:
1. Typ e
su r
on the path line to access the
Press .
RETURN
subscriber:remote
form.
Figure 3-11, the subscriber:remote form, shows a sample of this form.
2. Fill out the form with the appropriate information for the subscriber’s name, extension, community ID, and machine name.
AMIS Analog Networking
AUDIX Administration
3
585-300-512 Issue 7
May 1999
3-34Implementation
3. Press (F2) to add this remote subscriber to the local system’s data
ADD
base.
4. Repeat these steps for as many remote subscribers as you intend to administer. When you are finished, press to exit the form.
subscriber:remote
The
form can be used to add or delete remote
Ctrl-z
subscribers, display remote subscriber profiles, and convert nonadministered remote subscribers to administered remote subscribers or vice versa (you may want to convert a remote administered subscriber to a nonadministered remote subscriber if the administered remote subscriber threshold is being approached or has been reached).
If you want to delete a large number of remote you can do so using the
Localrl STATUS: alarms: none, logins: 1, thresholds: none
PATH: subscriber : remote
name: _________________________________ ext: __________ address: ________________________ community id: __ administered indicator (y/n)? __ machine name(s) __________ __________ __________ __________ __________ __________ __________ __________ __________ __________ __________ __________ __________ __________ __________ __________
subscriber:deletion
non-administered
form.
subscribers,
voice name: non-administered type (verified/unverified/no-profile): last usage date: (PRESS ENTER TO DISPLAY SUBSCRIBER PROFILE) new name: ______________________________ new ext: _________
Error and confirmation messages appear here.
CHANGE or RUN
ADD DELETE CLEAR
HELP
Figure 3-11. The subscriber: remote Form
FORM
EXIT ENTERHELP FIELD
AMIS Analog Networking
9
3
AUDIX Administration
3
585-300-512 Issue 7

Task 11: Record Remote Subscriber Names (Optional)

If you would wish, you can record administered remote subscribers’ names. Local subscribers who address messages to these remote subscribers, or who include their addresses in mailing lists or personal directories, can then hear name voiceback to confirm that the address they entered is correct.
To record administered remote subscriber names:
May 1999
3-35Implementation
1. Typ e
l e r
on the path line to access the
Press .
RETURN
list:extension:remote
form.
2. Tab to the machine name field and type the name of the remote machine that is the host for the subscribers whose extensions are to be listed. Press
ENTER
(F8).
3. Either print this screen, write down the subscribers’ extensions, or leave this form on the screen as you record names. To page through the list, press (F8) as often as needed.
ENTER
4. From a touch-tone telephone, log into the local AUDIX machine using the extension that has announcement-control permissions.
5. From the activity menu, press to perform system administration.
6. Press to record subscribers’ names.
4
7. Using the touch-tone keypad, enter the first subscriber’s extension as it appears in the ext field on the form.
8. Speak the subscriber’s name clearly when prompted.
9. Press or (as prompted) to approve the name, or press if
#
you wish to delete and re-record it. If desir ed, you may press t o listen t o yo ur reco rding, follow ed by
#
or (as prompted) to approve it, or to delete it.
*
#
*
2
D
*
D
*
10. Repeat steps 7 through 9 for each remote subscriber name you wish to record.
#
11. When you are finished, press to return to the activity menu, or just
R
hang up to exit the system.
AMIS Analog Networking
AUDIX Administration
3
585-300-512 Issue 7

Task 12: Test the Connection

This section describes tests that check the operation of the AMIS Analog Networking and/or Message Delivery features. Use these tests as the final step in administering the AMIS Analog Networking and/or Message Delivery features, or to troubleshoot a problem with the network.
NOTE:
When you initially administer the AMIS Analog Networking, Message Delivery, and/or Outcalling features, a system restart is the best way to ensure the system is updated correctly. However, anytime you have trouble getting the network to work, you may try restarting the system as described in Task 7 to see if that corrects the problem.
Task 12A: Testing an AMIS Analog Connection
You can test the AMIS analog connection either by sending a test message to the destination machine (see the section for an example), or you can use the AMIS loopback test mailboxes (if administered).
May 1999
3-36Implementation
1. Contact the system administrator at the remote AMIS machine to:
— Get the number of the remote AMIS loopback test mailbox (if one is
administered), or an extension to send a test AMIS message to (if one is not).
— Give the remote system administrator the number of your AMIS
loopback test mailbox, and request that he or she send you a test message.
2. From your own extension, log into the local system and create an AMIS mess a ge w i t h the r e mot e m a ch i ne’ s l o o pback t e s t m ail bo x a ddres s ( o r the alternative test extension). Schedule the message for immediate delivery. (If the remote system’s loopback test mailbox receives your test message, it will send a copy of your message back to your incoming mailbox as a new voice mail message.)
3. Wait a few minutes, then check your mailbox:
— If the message could not be delivered, you will have a new voice
mail message notifying you that the message was undeliverable. Access your outgoing mailbox (press ) and play the
undeliverable
message header to find out the reason the delivery
4
attempt failed. Depending on the error message, correct the most likely problem. Verify the intended recipient’s address and administration, then return to this section to try another test.
— If the local system could successfully deliver the message, the
mess age s tatus in y our out goin g mai lbox is u pdate d to the message has not yet been delivered (it is still
deliv ered
undelivered
), check your mailbox again later to see if the status has been updated to
delivered
.
. If
AMIS Analog Networking
#
AUDIX Administration
3
585-300-512 Issue 7
4. If the remote system administrator sends an AMIS message to the local loopback test mailbox on your system, the local system sends a copy of the message to the
incoming
message was received. The loopback extension keeps a copy of the message header in its
Task 12B: Testing a Message Delivery Connection
To test a connection for the Message Delivery feature, simply send a test message to the intended recipient. If your telephone number is in the same address range as the intended recipient, you may alternatively send a test message to yourself. To test the Message Delivery feature:
mailbox of the remote user to indicate the
outgoing
mailbox.
May 1999
3-37Implementation
1. Fr om your own extension, log into the local AUDIX system and press to record a message for the intended recipient. When finished, press or
#
(as prompted) to approve it.
*
1
#
2. When the system prompts you for the extension, enter the message delivery prefix (if needed), followed by the complete telephone number needed to reach the recipient, followed by .
#
3. To approve the address and send the message immediately (at the first administered interval), press (on R1V8 systems only) or .
#
* *
#
4. Wait a few minutes, then check your mailbox:
— If the message could not be delivered, you will have a new voice
mail message notifying you that the message was undeliverable. Access your outgoing mailbox (press ) and play the
undeliverable
message header to find out the reason the delivery
4
attempt failed. Depending on the error message, correct the most likely problem. Verify the intended recipient’s address and administration, then return to this section to try another test.
— If the local system could successfully dial the recipient’s number,
the message status in your outgoing mailbox might be
accessed
, depending on whether the intended recipient has
delivered
or
answered the call. If the message has not yet been delivered (it is still
undelivered
has been updated to
), check your mailbox again later to see if the status
accessed
, indicating a successful message
delivery.
AMIS Analog Networking
AUDIX Administration
3
585-300-512 Issue 7

Ongoing Administration

Ongoing AMIS analog networking and message delivery administration and maintenance is summarized in this section.

Educate Subscribers

A primary duty of the system administrator is to inform the subscriber population of AMIS analog networking and message delivery prefixes, valid machine numbers to dial, and so on. Update and distribute the template letter for the AMIS Analog Networking and Message Delivery features that appears in Chapter C,
"Subscriber Operation"

Maintain the Network

The system administrator may need to do periodic administration of the AMIS analog networking/message delivery network as follows:
For AMIS analog networking, add and delete local and remote
subscribers and machines as necessary (see Tasks 8 through 11). These tasks do
not
require a system restart.
May 1999
3-38Ongoing Administration
For message delivery, add and delete remote telephone numbers and
subscribers as necessary (see Tasks 8 through 11). These tasks do require a system restart.
Readminister network parameters if needed (for example, if numerous
remote administered subscribers are added or if the Outcalling feature is activated). Any changes made in Task 3 require a system restart (see Task
7).
Troubleshoot any AMIS-related entries that appear in the administration
log (an “A” entry on the status line). Refer to Chapter A, "Administration
Log Entries", for a summary of AMIS analog networking and message
delivery log entries, and the problem-resolution steps for each.

Monitor Logs and Traffic Reports

Th e system administrator should display the administrati on log and traffic reports frequently to verify good service, identify possible problems, and ensure system security. Refer to the appropriate forms reference manual for a description of traffic reports and individual fields on the traffic forms (see the "Related
Resources" section in the preface).
not
AMIS Analog Networking

DEFINITY AUDIX Administration

4
585-300-512 Issue 7
DEFINITY AUDIX Administration
This chapter describes how to implement the AMIS Analog Networking and/or Message Delivery features on a DEFINITY AUDIX R1.0 or later system. Information is organized as follows:
May 1999
4-1
4
Implementation and testing
Ongoing administration
NOTE:
To administer AMI S analog networking on an AUDIX R1 system, refer to
Chapter 3, "AUDIX Administration". To administer AMIS analog networking
on an Intuity system, refer to Chapter 5, "Intuity System AMIS
Administration"
Planning is the essential first step in implementing the AMIS Analog Networking and/or Message Delivery features. Review Chapter 2, "Planning and Design", before starting the steps in this section. Network administration should not begin until the local system is running smoothly and the administrator has had some experience administering it.
!
WARNING:
In order to minimize exposure to unauthorized long distance calls, the AMIS Analog Networking and Message Delivery features should be restricted to sending messages to telephone numbers located in specific calling areas or to specific destinations needed to conduct business. Additionally, the administrator may use the Message Sending Restrictions feature to administer which subscribers can send AMIS analog networking and message delivery messages, and to which locations they can send messages.
.
AMIS Analog Networking
DEFINITY AUDIX Administration
4

Implementation

This section describes the tasks necessary to implement the AMIS Analog Networking and Message Delivery features on a DEFINITY AUDIX system. T hese machine-specific tasks must be done for each remote AMIS analog machine or message delivery telephone number. Because the AMIS Analog Networking and Message Delivery features have similar administration requirements, you may want to administer them simultaneously if you plan to use both features.
DEFINITY AUDIX administration tasks include:
1. Verify AMIS Service
2. Display the Local Machine
3. Administer AMIS Analog Loopback Test Mailbox (Optional)
4. Administer AMIS Analog Networking/Message Delivery Parameters
5. Administer Outcalling Periods
6. Adjust System Limits for Subscribers
585-300-512 Issue 7
May 1999
4-2Implementation
7. Administer Retransmission Intervals
8. Activate the Changes (Reboot or Run Audits)
9. Administer Remote Machines and/or Telephone Numbers
10. Record Remote Machine Names (Optional)
11. Administer Remote Subscribers (Optional)
12. Record Remote Subscriber Names (Optional)
13. Test the Remote Connection
NOTE:
Not all screens used to administer these features are fully explained in this section; only the information necessary for implementing the AMIS Analog Networking and/or Message Delivery features is covered. For complete instructions for using screens, refer to the appropriate forms or screens reference manual for your version of software.
AMIS Analog Networking
RETURN
DEFINITY AUDIX Administration
4
585-300-512 Issue 7

Task 1: Verify AMIS Service

You cannot administer the AMIS Analog Netwo rki ng or Message Delivery features until AMIS analog networking has been activated by Lucent Technologies personnel. To find out if AMIS service has been activated:
May 1999
4-3Implementation
1. Log into the DEFINITY AUDIX system as described in
System — Administration,
2. Enter
display system-paramete rs cust om er-o pt ions
585-300-507.
DEFINITY AUDIX
on the command
line and press . See Figure 4-1, the Display System-Parameters Customer-Options screen
for a sample of this screen. In different versions of the software, this screen looks slightly different.
3. Check the
AMIS Analog Networking?
field.
— If the field is displaying a y, AMIS service has already been
activated. Go to Task 2.
— If the field is displaying an n, AMIS service has not yet been
activated for your system. Contact your Lucent Technologies representative.
Figure 4-1. The Display System-Parameters Customer-Options Screen
AMIS Analog Networking
DEFINITY AUDIX Administration
4
585-300-512 Issue 7

Task 2: Display the Local Machine

The local system is always the system to which the terminal is connected. All others are considered remote voice mail systems regardless of where they are located.
To verify the local machine has been administered correctly:
May 1999
4-4Implementation
1. Enter
change machine
on the command line and press .
RETURN
See Figure 4-2, Local Machine Profile Screen, for a sample of this screen.
2. Check the following information on the screen, and make any corrections if nec essary:
Machine Name (this example shows the name “localda”)
Machine Type (always audix for the local machine)
Extension Length (for the local machine)
Default Community (used by the Message Sending Restrictions
feature)
Prefix (not typically used for the local machine)
Extension Ranges (must not overlap with planned AMIS/message
delivery addresses)
3. Press (F3) to save any changes and exit the screen.
ENTER
Figure 4-2. Local Machine Profile Screen
AMIS Analog Networking
DEFINITY AUDIX Administration
4
585-300-512 Issue 7

Task 3: Administer Loopback Test Mailbox (Optional)

This task is optional for the AMIS Analog Networking feature and does not apply to the Message Delivery feature. The loopback test mailbox is used to test the AMIS Analog Networking feature. Any message delivered to this mailbox causes a reply to be sent to the sending mailbox.
If a remote user sends an AMIS message to this mailbox, the local system sends a copy of the message to the message was received. The local loopback test mailbox keeps a copy of the message header in its
To administer the optional loopback test mailbox:
incoming
outgoing
mailbox.
May 1999
4-5Implementation
mailbox of the remote user to indicate the
1. Enter
add subscriber
press . For
RETURN
<subscriber-name>
<subscriber-name>
, select a name that is not defined for any other
subscriber (for example, you might use the name loopback).
2. Type an
unused
local extension in the Extension field. (You must enter this
same extension on the System-P arameters Analog-Network screen in Task
4.)
3. Administer any other local parameters that are relevant (for example, check the Community ID field).
4. Press (F3) to add the test mailbox and exit the screen.
ENTER

Task 4: Administer AMIS Analog/Message Delivery Parameters

To implement the AMIS Analog Networking or the Message Delivery parameters, you must administer certain parameters on the System-Parameters Analog-Network screen as described in this section.
NOTE:
You can access this screen only if the AMIS Analog Networking feature has been enabled by Lucent Technologies personnel. If you cannot access this screen, contact your Lucent Technologies representative.
on the command line and
To administer the AMIS Analog Networking or the Message Delivery feature parameters:
1. Enter
change system-parameters analog-network
and press .
RETURN
on the command line
Figure 4-3, the System-Parameters Analog-Network screen, shows a
recent example of this screen. Figu re 4-4, the System-Parameters Analog-Network screen (R1.0/R2.0), shows how the screen looked in earlier versions of software.
AMIS Analog Networking
DEFINITY AUDIX Administration
4
585-300-512 Issue 7
May 1999
4-6Implementation
Figure 4-3. The System-Parameters Analog-Network Screen
Figure 4-4. The System-Parameters Analog-Network Screen (R1.0/R2.0)
AMIS Analog Networking
DEFINITY AUDIX Administration
4
585-300-512 Issue 7
May 1999
4-7Implementation
2. Go through the following screen fields by pressing the or arrow keys,
TAB
and change any fields needed to implement the AMIS Analog Networking or Message Delivery features:
a. CALLBACK NUMBERS (or CALLBACK NUMBER prior to R3.0)
Enter the complete telephone number needed for the remote machine to call the local system. The Local Number is the hunt group number assigned to the analog voice ports.
The Country Code can have a maximum of four digits, the Area/Trunk Number a maximum of seven, and the Local Number a maximum of 15. However, the
complete
callback number (country code, area/trunk number, and local number) cannot exceed 15 digits. A country code and an area/trunk number are always recommended and may be required.
Some examples of country codes are:
If the local system is in the United States or Canada and
uses the public network, enter a 1 for the country code.
If you are in another country, enter the appropriate country
code (such as 44 for the United Kingdom). Country codes should be listed in your local phone book.
On DEFINITY AUDIX R2.0 or later systems,
you may enter a cou ntr y co de of 0 to allow a DEF INIT Y AUDIX system to work in a mixed-vendor environment over a private network; this code may be used for private networks in any country. (A
country code of “0” is not allowed on DEFINITY AUDIX R1.0 systems.)
On DEFINITY AUDIX R3.0 and later systems,
up to five callback numbers may be defined. This allows different nodes to use different telephone numbers to call the same AMIS machine. For example, an AMIS analog network may include some nodes accessed over the public network, and other nodes accessed over a private network. Vendors other than Lucent Technologies may also require the AMIS callback numbers to be administered in a particular way. For convenience, callback numbers that are administered on this screen are also listed on Page 2 of the Machine screen, so you can easily select the appropriate callback number you wish to use for each remote AMIS machine.
The default callback number is “1”. If a system with a single callback number is upgraded to run R3.0 or later software, the existing callback number will be placed in the default selection “1”. If an additional callback number is defined on this screen and then deleted, the Callback Number field on the Machine screen for any remote node that used that number will automatically be changed to show the default callback number “1”. An entry will appear in the administration log whenever callback numbers are deleted or changed (refer to Appendix A, "Administration Log Entries", for a complete list of AMIS administration codes).
AMIS Analog Networking
DEFINITY AUDIX Administration
4
b. AMIS Analog Networking Incoming Allowed?
c. AMIS Analog Networking Outgoing Allowed?
585-300-512 Issue 7
May 1999
4-8Implementation
This field applies only to AMIS analog networking.
Set this field to “y” if you want the local system to accept incoming AMIS analog calls. Set this field to “n” if you want the local system to refuse incoming AMIS calls.
This field applies to
both
AMIS analog networking and message
delivery. Set this field to “y” if you want the local system subscribers to send
AMIS analog networking and/or message delivery messages. Set this field to “n” if you want to prevent subscribers from sending AMIS analog networking and/or message delivery messages.
d. AMIS Prefix
This field applies only to AMIS analog networking. You may enter an AMIS prefix to identify an address as an AMIS
analog address. If the address ranges defined for AMIS one- or two-step addressing do not overlap with any previously defined address ranges, it is not necessary to define an AMIS prefix. However, if any AMIS or message delivery address ranges overlap, you may need to administer an AMIS prefix to make the AMIS addresses unique.
NOTE:
If an AMIS prefix is defined, subscribers
must
dial the AMIS prefix when addressing AMIS analog messages. The AMIS prefix
must
precede any other digits in the address prefix(es) that subscribers dial; these are specified on the Machine screen.
AMIS Analog Networking
DEFINITY AUDIX Administration
4
e. AMIS Protocol—Use 8 Minutes For Incoming Message Length 0?
585-300-512 Issue 7
May 1999
4-9Implementation
This field applies only to AMIS analog networking. Some non-Lucent Technologies remote voice mail systems cannot
specify the message length and use a zero (0) in the protocol. This field enables the local system to record these incoming messages as follows:
Enter
y
for the local system to assume an incoming message of unknown length is 8 minutes long (the maximum length allowed by the AMI S protocol specification).
Enter
n
if you do incoming message of unknown length is 8 minutes long. In this case, the system uses the number in the Message Lengths, Maximum field on the System-Parameters Limits screen; AMIS messages longer than this system limit will not be accepted.
In either case, if an incoming message’s assumed length is longer than the space currently available in a subscriber’s mailbox, delivery of the message will be aborted.
f. AMIS Loopback Test Mailbox Extension
This field applies only to AMIS analog networking. If you administered an AMIS loopback mailbox in Task 3, enter the
extension for the test mailbox in this field.
3. Press (F3) to save any changes and exit the screen.
ENTER
4. You need to reboot the system or run an audit to activate these changes (done in Task 8).

Task 5: Administer Outcalling Periods

not
want the local system to assume an
The AMIS Analog Networking and Message Delivery features use the outcalling ports to deliver messages. Although outcalling periods must be administered, the Outcalling feature itself does
not
need to be active for AMIS analog
networking or message delivery to work.
NOTE:
For more efficient use of system resources, the system administrator may wish to limit the times of day for sending AMIS analog networking or message delivery messages to those which are known to be less busy.
To administer outcalling parameters for AMIS analog networking or message delivery, do the following:
1. Enter
change system-parameters outcalling
RETURN
.
on the path line and press
AMIS Analog Networking
DEFINITY AUDIX Administration
4
See Figure 4-5, the System-Parameters Outcalling screen, for a sample of this screen .
585-300-512 Issue 7
May 1999
4-10Implementation
Figure 4-5. The System-Parameters Outcalling Screen
2. Go through the following screen fields by pressing the or arrow keys, and change any fields needed to implement the AMIS Analog Networking or Message Delivery features:
a. Outcalling Active?
Enter n if you want to use the AMIS Analog Networking and/or Message Delivery features and do Outca lling feature. Enter y if you want to use the Outcalling feature
in addition to
the AMIS analog networking and/or message delivery.
TAB
not
want to activate the
Loading...