Key System US provides this document "as is," with no representations or warranties, either explicit or
implied, including but not limited to the implied warranties of merchantability, title, or fitness for a
particular purpose.
Key System US reserves the right to make changes in product software, hardware, or documentation at
any time, with no obligation to inform any persons or entities of such changes. Every attempt has been
made to ensure the accuracy of this document. However, Key System US assumes no responsibility for
any losses, whether electronic, financial, or other, that might accrue from inadvertent inaccuracies that
the software or documentation might contain.
Some states or jurisdictions do not allow disclaimer of explicit or implicit warranties in certain
situations. Therefore, this statement might not apply to you.
limited by the license or agreement. One copy of the software may be made for archival purposes.
Making any other copies of the software, without prior written permission from Key System US, is
prohibited by copyright laws, and constitutes a punishable violation of those laws.
The contents of this document may not be duplicated by any means, whether electronic, graphic, or
mechanical, including, but not limited to, photocopying, recording, taping, or information recording
and retrieval systems, for any purpose but the original purchaser's personal use, without prior written
permission of Key System US.
Trademark Information
Atlas, Atlas AVM and Atlas IIE are registered trademarks of KS Telecom.
CO/Session is a registered of Triton Technologies, Inc.
Dialogic is a registered trademark of Dialogic Corporation.
MS-DOS is a registered trademark of Microsoft Corporation.
QEMM is a registered trademark of Quarterdeck Office Systems.
Rhetorex is a trademark of Rhetorex, Inc.
GammaFax is a trademark of GammaLink.
Key System US
4910 Dyer Blvd., West Palm Beach, Florida 33407
Table of Contents
Chapter 1: Overview of Installation and Integration
About this Manual.......................................................................... 1-1
Evaluating the Customer ................................................................ 1-2
Figure 9-9: The Telephone System and............................................................. 9-18
Figure 9-10: The Telephone System and Rhetorex Channel Parameters Panels. 9-25
Figure 9-11: The Sequences and Message Waiting............................................ 9-31
Figure 9-12: Valid Characters for the Sequences Panel..................................... 9-32
Figure 9-13: The Control Panel ......................................................................... 9-33
Figure 9-14: The Tone Termination (Dialogic Only) and.................................. 9-34
Figure 9-15: The Integration and In-Band Supervision Panels ........................... 9-36
Figure 9-16: The In-Band Signaling Control Panel............................................ 9-37
Figure 9-17: The Integration Data Packet Screens............................................. 9-38
viii Atlas AVM Installer’s Manual
This Page Intentionally Left Blank.
Overview of Installation and
Integration
About this Manual
The purpose of this manual is to guide you through the installation and
integration of your Atlas AVM system. This manual is intended for use by
certified Atlas AVM installers who are proficient in DOS, telephony, and
voice processing.
The chapters in this manual are as follows:
•Chapter 1 gives a brief description of each chapter, provides a
summary of installation, and explains the conventions used in this
manual.
•Chapter 2 is a quick guide to installation for experienced
installers.
•Chapter 3 describes evaluating the customer’s voice processing
needs and capabilities.
•Chapter 4 offers an overview of the Atlas AVM installation and
integration process.
•Chapter 5 tells how to plan the basic design of an Atlas AVM
system.
•Chapter 6 describes the functions of voice boards in your Atlas
AVM system and tells which models of the Dialogic and Rhetorex
boards can be used.
•Chapter 7 gives general guidelines and recommendations for
building an Atlas AVM system.
•Chapter 8 gives suggestions for connecting Atlas AVM to your
telephone system.
•Chapter 9 tells how to program the Atlas AVM integration
screens.
•Chapter 10 explains how to add fax capability in your Atlas
AVM system.
1
1-2 Atlas AVM Installer’s Manual
☞
•Chapter 11 covers the system administration issues that need to
be addressed as part of the installation process.
•Chapter 12 discusses the final steps required to make the system
operational.
• Glossary
• Index
Conventions
This manual uses the following conventions:
CONVENTIONKEY INFORMATION
lowercase xindicates a variable in a file,
ALL CAPSindicates a file or directory
<italics>indicates a variable or place
version, etc.
holder
Boxes➞Renumber
< >indicates a keyboard command
Lowercase boldused for commands or data to be
Note:Information that is vital to the
Tip:A shortcut or helpful hint
Caution:Possible damage to equipment
Evaluating the Customer
Before installing an Atlas AVM system, you need to gather information
about the prospective customer. This will help you assess what that
customer needs to build a voicemail system.
example of a ‘path’ that a user can
follow to get to a particular screen
or field.
entry such as <Enter>
typed at the keyboard
success of a process
1.
Collect pertinent information about the company.
Overview of Installation and Integration 1-3
2. Decide which telephony features and applications the customer desires
such as:
• Voicemail
• Auto attendant
• Audiotext
• AMIS-Analog Networking
• Fax
3.
Determine whether the customer can or does meet the hardware and
software requirements. (See Chapter 9, “Building the System.”)
4.
Use the Customer Engineering Form in Chapter 3, “Evaluating the
Customer,” as you compile information about the customer.
Gathering Integration Information
In an Atlas AVM system, integration means enabling communication
between Atlas AVM and a specific telephone system.
Telephone systems differ, and Atlas AVM must be programmed to
communicate with the customer’s specific telephone system. To
accomplish this you need to gather information about the customer’s
telephone system.
1.
Collect the telephone system information suggested on the Integration
Form found in Chapter 4, “Integration Investigation.” This includes:
• Manufacturer, model, and software version
• Name of the person who maintains and services the
telephone system
• Necessary hardware for voice messaging
• Information about telephone system operations
• Data packet information
Resources for doing this include the Atlas Telephone System
Compatibility Listing, the customer’s interconnect, the telephone
system manufacturer, and the telephone system documentation.
2.
Gather any other needed information through on-site testing.
3.
If you have affirmed that Atlas AVM can integrate acceptably with the
customer’s telephone system, save the information you have compiled
for later use in the installation/integration process.
1-4 Atlas AVM Installer’s Manual
Designing the Basic System
Planning the Design
You will need to draw up a basic design from the information you have
obtained from the customer. This will lay the groundwork for the system
and help you determine sizing issues (see “Sizing the System” below).
With the customer, you can help make decisions about how the overall
system will work. The following steps will help you do this.
1.
Design how the Auto Attendant will handle calls. This includes:
• Designing greetings which can be set for different times
(business hours vs. non-business hours), days and ports
• Designing the options available for transferring from the
Auto Attendant
☞
Note
Customizing and
programming boxes is
explained in the Atlas
AVM System
Administrator’s
2. Plan audiotext boxes in addition to the Auto Attendant. This includes:
• Determining the total number of audiotext boxes
• Planning audio menus
• Mapping the levels of audiotext boxes
3. Determine the number of voicemail, etc. boxes needed.
Sizing the System
After you have calculated the number of audiotext and voicemail boxes
required for an Atlas AVM system, you also need to determine the number
of voice board ports and the amount of disk storage required.
For worksheets and information regarding sizing, see Chapter 5,
“Designing the Atlas AVM System.”
Building the System
Keep in mind the following as you build your Atlas AVM system:
1.
Software requirements
• Atlas AVM installation disks
• DOS 5.0 or later, 6.2 recommended
• Fax Driver Disk (optional—available from Key System US)
• CO/Session 7.0 or later
2. Hardware requirements
• Minimum hardware specifications (memory for CPU and ports)
• Suggested hardware configuration
• Recommended hard drive size
• Voice boards to handle number of ports required for the system
For information on system requirements, see Chapter 9, “Building the
System.”
Installing Voice Boards
You need to consider the following:
1.
Familiarize yourself with the voice boards Atlas AVM supports. You
can help the customer decide which voice boards to buy based on the
number of ports required, the number of available slots, and the cost
of different boards.
Overview of Installation and Integration 1-5
2.
Prior to installing voice boards, determine the following for your
system (Atlas AVM will suggest defaults during Atlas AVM
installation):
• I/O port address
• Hardware interrupt
• Base memory
3. Use the Rhetorex utility SHOWJUMP or the Dialogic voice board
documentation to determine the jumper settings for the I/O port
address before installing the voice boards. You can do this during or
after installation of the Atlas AVM software.
4.
Finally, physically connect the voice board(s) to the telephone system
using a telephone line. Determine the correct jack connection for the
voice board and make sure it matches the telephone jack connections
on the wall.
For information on setting up and installing voice boards, see Chapters 6,
7, and 8.
Installing Atlas AVM
The following steps are required for installing Atlas AVM:
2.
Make sure DOS is running.
1-6 Atlas AVM Installer’s Manual
3. Install the voice board(s).
4.
Attach the hardware lock.
5.
Install the Atlas AVM disks.
6.
Install and configure CO/Session (optional).
7.
Create a VXNIGHT.BAT file (optional).
8.
Reboot the system.
For information on installing the Atlas AVM software, see Chapter 10.
Connecting Atlas AVM to a Telephone System
Determine the type of integration desired and what will be needed to complete
the connection.
For information on Connecting Atlas AVM to a Telephone System, see
Chapter 11.
Integrating with the Telephone System
This process involves taking the information you have collected and
inputting it into the Atlas AVM installation screens.
1.
Refer to the Integration Form you filled out earlier as you program the
Atlas AVM integration screens and parameters.
2.
Plan to test the integration after you have completed “System
Administration Procedures” below.
For instructions on programming the Atlas AVM integration screens, see
Chapter 12.
Installing and Configuring Fax (Optional)
Fax capability is an add-on feature that must be purchased separately.
Install and configure a GammaFax MLCP-4/AEB board, and install and
configure the fax drivers provided by Key System US.
For more information, see Chapter 13, “Fax Installation.”
System Administration Considerations
Overview of Installation and Integration 1-7
Now that Atlas AVM is installed and integrated with the telephone
system, you need to instruct or assist the system administrator in the
following areas:
1.
Configuring system boxes—voicemail, audiotext, etc.
2.
Recording the audio portion of company greetings and other audiotext
boxes.
3.
Testing the system.
• System design
• Integration with the telephone system
(For detailed administration information, see the Atlas AVM System
Administrator’s Manual.)
4.
Training users on how to use the Atlas AVM telephone interface (can
be done by the installer or the system administrator).
The Atlas AVM Pocket Reference Guide provides information on
using the telephone interface. Atlas AVM also provides a tutorial
over the telephone when box owners first set up their voicemail boxes.
Finalizing the Installation
Now that you have Atlas AVM installed, configured, and tested, you can
take the final steps necessary to make the system operational. These steps,
called the final cut over, include:
1.
Connecting single line extensions to Atlas AVM.
2.
Programming Atlas AVM lines at the telephone switch.
3.
Organizing lines going to Atlas AVM into a hunt group.
4.
Forwarding trunk calls (outside calls) to Atlas AVM.
5.
Programming telephone handsets.
Some of these steps may require the expertise of the customer’s telephone
interconnect.
1-8 Atlas AVM Installer’s Manual
This Page Intentionally Left Blank
Quick Installation Guide
This chapter is an abbreviated version of Chapter 10, “Installing Atlas
AVM.” For more detailed installation information, see Chapter 10.
What is Atlas AVM?
Atlas AVM is a DOS-based voice processing system that provides a suite
of telephony features, as well as the means of integrating with a telephone
switch.
Installation Procedure
Briefly, installing and setting up Atlas AVM involves the following:
2
1.
Installing and setting up your voice boards.
2.
Installing and configuring CO/Session to allow remote maintenance.
3.
Installing the Atlas AVM disks and configuring your voice boards.
4.
(optional) Creating a VXNIGHT.BAT file, a custom batch file Atlas
AVM runs daily at 4:00 AM.
5.
Integrating with the specific telephone system, if necessary, through
the Atlas AVM installation screens.
6.
Using the Atlas AVM System Administrator’s Manual to set up Atlas
AVM system parameters.
2-2 Atlas AVM Installer’s Manual
Installation Steps
Step 1: Equipment Inventory
Verify that you have all the needed equipment and software to complete a
total installation of the Atlas AVM voice processing system:
• A computer equipped with the hardware listed in Step 2 below
• DOS (version 5.0 minimum, 6.2 or later preferred)
• Atlas AVM installation package:
- Installation disks
- Hardware lock
- Atlas AVM System Administrator’s Manual
- Atlas AVM Installer’s Manual
- Atlas AVM User Guide pamphlets (25 copies)
• Dialogic or Rhetorex voice board(s)
• Miscellaneous telephone equipment for connecting to the
telephone system.
Step 2: Verify Hardware Requirements
Certain hardware specifications and configurations are required before a
PC can be utilized for Atlas AVM voice processing.
Component4-12 Port System16-20 Port System24 Port System
CPU
RAM
Bus
Speed
Hard drive
BIOS
Power
supply
386, 486, or Pentium486DX to Pentium486DX4 to Pentium
4 MB8 MB12 MB
ISAISAISA
25-66 MHz or higher33-66 MHz or higher66 MHz or higher
IDE or SCSIIDE or SCSIIDE or SCSI
AMIBIOSAMIBIOSAMIBIOS
200 watt UL approved250 watt UL approved300 watt UL approved
Figure 2 -1: Minimum Hardware Specifications
Step 3: Voice Board Setup and Installation
Install your voice boards. Information on installing voice boards is
provided in Chapters 7 and 8.
Quick Installation Guide 2-3
Step 4: Attach the Hardware Lock
Attach the hardware lock you received with your installation disks to
LPT1.
Step 5: Have DOS running
You need DOS version 5.0 or later.
Step 6: Load the Atlas AVM Disks
In this step you will load the Atlas AVM software, load the voice board
drivers, install QEMM, and configure your voice board.
The following disks are included in your Atlas AVM installation package:
Engine Disk 1
Engine Disk 2
Switch Integration Disk
Rhetorex Driver Disk
Dialogic Driver Disk 1
Dialogic Driver Disk 2
System Prompts Disk 1
System Prompts Disk 2
System Prompts Disk 3
QEMM Disk 1
QEMM Disk 2
Fax Driver Disk (if you have purchased the optional fax capability)
To begin installing, insert Engine Disk 1. Use a: install. Follow the prompts.
For a complete guide to all the installation screens, see Chapter 10,
“Installing Atlas AVM.”
Step 7: Create VXNIGHT.BAT (Optional)
Daily at 4:00 A.M. Atlas AVM offers the option of running a batch file of
your own making. For Atlas AVM to run this file, it must be named
VXNIGHT.BAT and must be located in the Atlas directory.
You can use your custom VXNIGHT.BAT file to perform automated tasks
related to your Atlas AVM system. For example, the following would
back up and then reboot/purge your Atlas AVM system:
xcopy c:\Atlas\*.* /e/s/v g:\
c:\coldboot.com
2-4 Atlas AVM Installer’s Manual
Step 8: Install CO/Session
CO/Session allows remote maintenance of Atlas AVM, and also will
allow Key System US technical support personnel to access your Atlas
AVM system if you need assistance.
For more information, see Step 6, “Setting Up CO/Session,” in Chapter
10.
Step 9: Install Fax Capability (Optional)
You can purchase optional fax capability for your Atlas AVM system. For
more information, see Chapter 13, “Fax Installation.”
Step 10: Reboot the System to Verify all Settings
Reboot your system and look for error messages.
Your Atlas AVM system is now running on system defaults. If your
system is working with the default telephone system settings, refer to the
Atlas AVM System Administrator’s Manual for information on port setup
and programming system boxes (audiotext, voicemail, etc.).
If your system is not working with the defaults, see Chapter12,
“Integration with the Telephone System,” for information on interfacing
with your specific telephone system.
Evaluating the Customer
When you meet with customers who are interested in Atlas AVM,
determine what their companies need to build a voicemail system.
Evaluating customers’ situations and determining their needs will help
you guide them in developing an Atlas AVM system. The final decisions
should be based on considerations such as:
• Type of telephone system
• Telephony needs of the customer
• Cost of implementing everything required
Some customers may have telephone systems that do not have voicemail
capability, especially if they have older, smaller systems. If that is the
case, the customer will need to upgrade the telephone system in order to
have voicemail. Atlas AVM requires only basic voicemail capabilities
from the telephone system.
3
Gathering Information
Begin the evaluation process by collecting information about the
prospective customer and recording it on a form such as the Customer
Engineering Form given in this chapter. Use this as the basis for building
a file on the customer.
The Customer Engineering Form
Some of the information you need to gather relates to your role as a
salesperson; other parts relate to your role as an Atlas AVM installer.
Use the descriptions below as you fill out the Customer Engineering form.
3-2 Atlas AVM Installer’s Manual
Company Information
Record the company name and address, the name of your contact person at
the company, and also the person who will make the final decisions about
purchasing an Atlas AVM system.
Site Information
Determine the approximate number of people who will be using voicemail
and make an estimate of how many boxes this system will need. This will
help you get a rough estimate of the size and cost of the Atlas AVM
system.
Find out how many telephone lines there are from the central office to the
company so you will know if additional lines will be required.
Telephone System Information
Collect information about the telephone system, including the
manufacturer, model number, and what software version is running. You
may need to get some of this information from the company’s interconnect
(telephone maintenance person).
Make a record of the name, address, and telephone number of the
company’s interconnect. The interconnect’s knowledge about the
telephone system can benefit you throughout the sales and installation
process.
Telephony Applications/Features Desired
Find out if the company wants its voicemail system to have an Auto
Attendant, voicemail, audiotext boxes, fax boxes or a combination of
these features.
Customer Engineering Form
Company Information
1. Company name
2. Company informationAddress
Phone
Fax
3. Contact personName
Phone
4. Final decision-makerName
Phone
Site Information
5. Number of employees who will use the Atlas AVM system
6. Estimated number of boxes
Voicemail boxes (boxes for voicemail users)
Auto Attendant boxes (boxes for company greetings)
Audiotext boxes (boxes providing information)
7. Number of lines from central office
Evaluating the Customer 3-3
Estimated total number of boxes
Telephone system Information
8. Telephone system manufacturer
9. Telephone system model
10. Telephone system software version
11. Interconnect companyName
Address
Telephone
Telephony Applications/ Features Desired
12. Voicemail
13. Auto Attendant
14. Audiotext
Yes / No
Yes / No
Yes / No
3-4 Atlas AVM Installer’s Manual
This Page Intentionally Left Blank.
Integration Investigation
During the integration investigation, you will determine if Atlas AVM can
be integrated with the customer’s telephone system and what voicemail
features will be available.
Integration Requirements
Atlas AVM requires the following basic features from a telephone system
in order to have voicemail:
• Necessary software version for voicemail
The telephone system software may need to be upgraded if it is
not a voicemail capable version.
4
• Single-line extensions
The voice boards in Atlas AVM are analog boards and need
single-line analog extensions. The user’s telephone does not need
this type of extension, only the lines going into Atlas AVM.
• Ringing capability on the single-line extensions
The telephone system must have ringing capability because the
voice boards and voice board drivers used in Atlas AVM require
the use of ringing as their method of notification.
• End-to-end DTMF
The Atlas AVM system sends and receives address information
for calls in the form of DTMF (Dual Tone Multi-Frequency)
signals. The phrase ‘end to end’ refers to the ability of a device to
both send and receive DTMF signals.
The following section, “Investigation Steps,” gives some possible ideas
for bringing a system that lacks some of the necessary requirements up to
standard.
4-2 Atlas AVM Installer’s Manual
Investigation Steps
The information required to determine if successful integration is possible
can be obtained from the telephone system’s documentation or
manufacturer, the customer’s interconnect vendor, or through on-site
testing. (Some methods of on-site testing are covered in the AtlasCertified Network Telephony Engineer Course Manual.)
As you gather the integration information listed in the following steps,
enter the data in the corresponding sections of the Integration Form
beginning on Page 4-7.
1.
Document general information about the customer and the telephone
system.
2.
Find out if the telephone system software supports voicemail.
You will probably need to consult the company’s telephone
representative to find out what software version is installed on the
telephone system, and what features this software has.
3.
Find out if the telephone system has the necessary hardware for
voicemail.
Locate single line extensions
If the customer has a fax machine or modem lines that go through
the telephone system, those are single line extensions. Find out
how many single lines there are.
If there are currently no single line extensions, you can add a
single line card (SLC) to the telephone system. These are also
called industry standard telephone cards (IST), or off-premise
extension cards (OPX).
Check for ringing on single line extensions
Dial a single line extension from another single line extension to
see if you hear ringing over the telephone.
The voice boards and their drivers used in Atlas AVM necessitate
the use of ringing as the method of notification. Therefore, the
telephone system has to have ringing capability on the extensions
going to Atlas AVM.
If the telephone system does not currently have ringing capability,
you can add a ‘ring generator’ card.
Check for end-to-end DTMF
• Attendant console
• Single line handset
• Digital handset
Integration Investigation 4-3
The voice boards in the Atlas AVM machine, being analog
devices, necessitate the use of DTMF as the method of receiving
control information.
If the telephone system cannot provide DTMF on the extensions
going to Atlas AVM, then an additional DTMF generator board
must be added to the telephone system.
4.
Find out how the telephone system operates concerning the following:
• hunt groups
• disconnects
• supervised transfers
• event signaling
• off-premise transfers
5.
Make a list of equipment or software that needs to be upgraded.
6.
Obtain information about the data packets that are sent by the
telephone system.
You can gather this information from the customer’s interconnect
or from the telephone system vendor. If you cannot collect this
information through these avenues, or you want to confirm the
information you have collected, you will need to use a digit
grabber. For an example of how to use a digit grabber, see Page
4-16.
You will enter the data packet information you have gathered
when you are ready to program the Atlas AVM integration screens
covered inChapter 12, “Integrating With the Telephone System.”
You do not need to input every data packet into Atlas AVM—
only the ones that will be relevant for Atlas AVM operations.
These would include such packets as ‘forward, busy,’ ‘forward, no
answer,’ ‘retrieve message,’ and possibly a ‘disconnect.’
Read the information in the next section, “Understanding Data
Packets,” before you fill out the data packet portion of the
Integration Form.
Understanding Data Packets
The data packet investigation involves the following three parts:
• Events and Packet Identifiers
• Packet Formats
• Atlas AVM Packet Definitions
4-4 Atlas AVM Installer’s Manual
Manual
Events and Data Packet Identifiers
☞
Note
Contact your telephone
system installer or
manufacturer for the
correct codes to use in
defining types of calls
in the integration data
packets. If this is not
possible, you may be
able to recreate the call
type and monitor it on
the Diagnostic Trace
screen. (See the Atlas
AVM System
Administrator’s
You must learn the ‘events’ the telephone system sends data packets on
and their corresponding ‘packet identifiers’ (i.e. the code used to denote
that event).
Example:
Forward, busy2
Forward, no answer3
Retrieve message4
Disconnect7
EventPacket Identifier
☞
Note
The telephone
system may not send
a data packet for
each of the Atlas
AVM data packet
definitions.
Data Packet Formats
You must learn the packet format of the data packets. This involves
knowing what part of the data stream pertains to such things as the packet
identifier, the called party extension, the calling party extension, and
possibly other information.
Example:
The telephone system could send a string of digits to Atlas AVM
that communicates the called party extension and the packet
identifier:
1332
Atlas AVM must know what the packet format is in order to
understand this communication. Since there is no standard default
packet format, Atlas AVM does not know whether the packet
identifier is ‘1’ and the called party extension is ‘332,’ or if the
called party extension is ‘133’ and the packet identifier is ‘2.’
However, if we tell Atlas AVM what positions in the data packet
relate to what information, then Atlas AVM can understand this
data packet.
Integration Investigation 4-5
If the called party was ‘133,’ and the packet identifier was ‘2’ (for
example, a forward busy), then the packet format would be:
Called Party Offset (position):0
Called Party Length:3
Atlas AVM Definition of a Data Packet
For every data packet that you input into Atlas AVM, you must tell Atlas
AVM how it should ‘define’ that packet. The following section contains
the current possible data packet definitions and how Atlas AVM acts for
each definition.
Atlas AVM Data Packet Definitions
Direct to Box
The call goes directly to a box owner’s mailbox, without ringing the
extension, based on the ‘called party’ information. Atlas AVM plays the
box owner’s personal greeting without any additional prompts.
Forwarded
Atlas AVM plays the following prompt:
“<Name of box owner> is not available to take your call.”
Atlas AVM then sends this call to the box number of the ‘called party’
and carries out whatever is in the Busy Option field (e.g., Take
Message, Alternate Extension, Caller Options).
Atlas AVM plays the following prompt:
“I’m sorry, that extension is busy.”
Atlas AVM then sends this call to the box number of the ‘called party’
and carries out whatever is in the Busy Option field (e.g., Take
Message, Alternate Extension, Caller Options).
4-6 Atlas AVM Installer’s Manual
Forwarded No Answer
Atlas AVM plays the following prompt:
“I’m sorry, that extension does not answer.”
Atlas AVM then sends this call to the box number of the ‘called party’
and carries out whatever is in the No Answer Option field (e.g., Take
Message, Alternate Extension, Caller Options).
Retrieve Message
Atlas AVM recognizes the caller as a box owner, sends the call to a box
based on the ‘called party’ information, and then asks for the passcode
for that box.
Trunk
Atlas AVM recognizes the call as being a ‘trunk’ call. This means that
the Trunk Port field on the Integration Data Packet Parameters screen is
valid. Atlas AVM plays the port greeting or Auto Attendant for outside
calls that are identified as the trunk listed in the Trunk Port field.
The Integration Form
The Integration Form, found on the next page, can be used by the Atlas
AVM installer to help determine if a telephone switch can be integrated
with, and to document the details of that integration.
If the particular telephone system in question is listed in the AtlasTelephone System Compatibility Integration Listings, use this form just
for your own records.
Loading...
+ 102 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.