This topic describes how to set up most system parameters
of an INTUITY AUDIX system. This topic assumes you know basic INTUITY
AUDIX commands and navigation, such as logging in and out of the system,
the command prompt function and usage, and how to move from field to
field within a screen or page. If you are not familiar with INTUITY
AUDIX system basics, read Getting Started
before you continue.
Note: Administration Checklists
contains a checklist of initial administrative tasks you can use
as a guide for performing AUDIX system administration.
Your INTUITY AUDIX system comes with default system limits.
These limits consist primarily of maximum capacities for such items
as stored messages and message-delivery lists. You can change system
limits at any time on the System-Parameters Limits
screen to define system capacities.
Note: You must use
the sa login to change data on the System-Parameters Limits screen.
Voice messaging administrators who use the vm login can view only
the data on this screen.
Use the Change Extensions screen
to move a series of extension numbers from one block of numbers to another
instead of changing each number individually. You can use this screen
to move a single extension from one number to another or to change the
length of every extension number in your system.
The Change Extensions screen affects many other settings on the
local AUDIX system and on remote networked AUDIX systems. Use
this screen only after you carefully plan the changes you want
to make.
Guidelines
for Using the Change Extensions Screen
Consider the following
guidelines before you change extension numbers:
Use the change machine
command to change extension length on a remote machine.
To move numbers on the
local machine:
This screen can move
all of the covering extensions in a given range of numbers. However,
it does not change references to the local system in networked systems.
If the system you want to change
is networked to other INTUITY AUDIX systems, you must also change
the extension length for this machine in all connected systems.
Ports on the system with
local subscribers whose extensions are to be changed are disabled
while you make the necessary changes. Therefore, plan to make the
changes when traffic is slow.
To change automated attendant
extensions:
This screen does notchange the extensions for automated attendants. If you use
this screen to change an extension, and an automated attendant is
set up to call that extension, follow the procedures in Automated
Attendant and Bulletin Boards to change the automated attendant
extension.
Changing
a Block of Extensions (and Changing the Length of the Extensions)
To change the length of
local extension numbers, you must first make changes to the S8300 Media
Server itself, and then make changes in AUDIX administration.
AUDIX Changes
To change the extension length
in AUDIX administration:
At the enter command: prompt,
enter change machine machine_name, wheremachine_name
is the name of the machine on which you plan to change or add extensions.
The system displays the
new extension length in theExtension Length:field on the Machine Profile screen.
Note the ranges of extension numbers in theStart Ext.andEnd
Ext.fields before you make any modifications.
Tip: If you have
a system printer, print a copy of the extension assignments
before you continue.
If you are updating
a remote machine, enter the new extension length in theExtension
Length:field.
Re-enter the prefixes and the start and end
extensions as you want them when the conversion is completed.
Press F3 (Enter) to save the information
in the system database.
The cursor returns to
the command line and the system displays the message:
Command Successfully
Completed.
At the enter command: prompt,
enter change extensions.
In the
Machine Name: field, enter the name of the INTUITY AUDIX machine
for which you are changing extension numbers.
In the Change extensions beginning with:
field and the Ending with: field, enter the boundaries
of the extension numbers you are changing. That is, enter two numbers:
the beginning (smallest affected) extension number and the ending
(largest affected) extension number.
In the To new extension beginning with:
field, enter the beginning number of the new block of numbers
to which the extensions named in Step
9 are to be changed.
All other fields are display fields.
Press F3 (Enter) to initiate the process.
The system does one of the following:
Fills in theEnding with:field and asks you to confirm your intent. The system then
validates that all extensions in the new extension range are unused
and available. This validation process can take between 1 and 2
minutes.
Fills in theEnding
with:field and displays the messageSubscriber
Already Exists. In this case, you have specified a range
of numbers that includes at least one number that is already assigned.
The system does not permit the Change Extensions screen to delete
an existing number in the course of adding another. If you see theSubscriber Already Existsmessage,
do the following:
Press F1 (Cancel) to exit this
screen.
Type list extensions
at the command line. Use the resulting list to determine whether
the local machine already has extensions assigned in the range
you want to use.
Type list address ranges at the
command line. Use the resulting Address Ranges list to determine
which remote machine already has extensions in the range you
want to use. If you want further information about the extensions
on a remote machine, type list remote-extensions machine-name
at the command line.
Use the information from Steps b and
c as a basis to reconsider the target range of numbers. Once
you have worked out new number ranges, return to Step
1 of this procedure to assign them.
Press F3 (Enter) again.
The system fills in the display fields as
it works. When the process is finished, the cursor returns to the
command line, and the system displays the following message:
Command Successfully
Completed.
If for some reason you must press F1
(Cancel) during this operation, the system will have already made
some changes. Recover as follows:
Note the numbers shown
in the display fields. They indicate approximately how many changes
were made.
Tip: If you have
a system printer, print a copy of the extensions.
At the command line,
enter list extensions to find exactly which numbers were
changed and which were not.
Plan what needs to be
done to recover, whether it is changing the remaining extensions
or returning changed extensions back to their original assignments.
Use the change extensions command to change extension numbers
as necessary.
Connect, one at a time, to each remote machine with which the local
machine is networked. On each remote machine, complete Step
1 through Step 14 by using the
name of the original local machine in fields that call for a machine
name.
The network ports of the machine on which the local subscriber's
extension length was changed must remain busied out until the
change is administered on all remote systems.
At the enter command: prompt,
enter change machine machine_name, wheremachine_name
is the name of the machine on which you plan to change or add extensions.
In the Machine Name: field, enter
the name of the AUDIX machine for which you are changingextension
numbers for local subscribers. This is the only system on which you
perform this procedure.
In the Change extensions beginning with:
field and the Ending with: field, enter the boundaries
of the extension numbers you are changing. That is, enter two numbers:
the beginning (smallest affected) extension number and the ending
(largest affected) extension number.
In the To new extension beginning with:
field, enter the beginning number of the new block of numbers
to which the extensions named in Step
11 are to be moved.
All other fields are read-only fields.
Press F3 (Enter) to initiate the process.
The system does one of the following:
Fills in theEnding
with:field and asks you to confirm your intent.
The system then validates that all extensions in the new extension
range are unused and available. This validation process can take
between 1 and 2 minutes.
Fills in theEnding
with:field and displays the messageSubscriber Already Exists. In this case, you
have specified a range of numbers that includes at least one number
that is already assigned. The system does not permit the Change
Extensions screen to delete an existing number in the course of
adding another. If you see theSubscriber Already
Existsmessage, continue with the following
steps:
Press F1 (Cancel)
to exit this screen.
Type list extensions
at the command line. Use the resulting list to determine whether
the local machine already has extensions assigned in the range
you want to use.
Type list address ranges
at the command line. Use the resulting Address Ranges list to
determine which remote machine already has extensions in the
range you want to use. If you want further information about
the extensions on a remote machine, type list remote-extensions
machine-name at the command line.
Use the information from
Steps b and c as a basis to reconsider the target range of numbers.
Once you have worked out new number ranges, return to Step
1 of this procedure to assign them.
Press F3 (Enter) again.
The system fills in the display fields as
it works. When it is finished, the cursor returns to the command
line, and the system displays the following message:
Command Successfully Completed.
If for some reason you must press F1
(Cancel) during this operation, the system will have already made
some changes. Recover as follows:
Note the numbers shown in the display
fields. They indicate approximately how many changes were made.
Tip: If you have
a system printer, enter print list extensions to obtain
a copy of the extensions.
At the command line, enter list extensions
to find exactly which numbers were changed and which were not.
Plan what needs to be done to recover, whether
it is changing the remaining extensions or returning changed extensions
back to their original assignments. Use the change extensions
command to change extension numbers as necessary.
Release the voice ports on the local system.
See Releasing Channels for more information.
The local system automatically updates any
remote system with the extension number changes.
Note: If a remote
system is not administered to receive automatic updates, you
must make the extension changes manually on the system. Contact
the system administrator for the remote machine to follow
Step 1 through Step
16.
Defining
Basic Features and Parameters
The INTUITY AUDIX system
comes with default login parameters and default system time limits.
Also, certain features that must be activated globally for all subscribers
(for example, Multiple Personal Greetings) are either activated or not
activated by default. You might want to change some of these parameters
or to activate or deactivate features as the needs of system subscribers
change.
Note: You must use the sa login to change data on this
screen. Voice messaging administrators who use the vm login can
view only the data on this screen
Press F3 (Enter) to save the information
in the system database.
The cursor returns to the command line,
and the system displays the message:
Command Successfully Completed.
Enter exit or another administrative
command at theenter command: prompt.
Controlling Call Transfers
This topic describes how to add or deny transfers
to certain numbers out of the AUDIX system and how to enable transfers
to others.
Factors to consider when
planning Call Transfer Controls
The Transfer Security pages give you control
over call transfers and use of the pages helps to prevent toll fraud.
Use these pages to specify extensions to which a caller is permitted
to transfer.
Callers cannot transfer to numbers expressly denied. For example,
you may want to forbid call transfer to numbers beginning with 9 if
this number accesses an outside line.
Denied numbers override numbers not specified on these pages. Allowed
numbersoverride numbers specifically denied. For example:
If you used the Add Denied Transfer Numbers
page to�...
and you used the Add Allowed Transfer Numbers
page to�...
then a caller can�...
deny all numbers
allow numbers in the range from 2000 to 5999
transfer out of the AUDIX system by dialing
any 4-digit number that starts with 2 to 5.
deny all numbers
allow a specific number
transfer only to that number, for example,
a remote field office.
Use the Add Allowed Transfer Numbers page to specify
permitted transfer numbers. The purpose of allowed transfer numbers
is to specify numbers that would otherwise be denied because they are
included on the list of denied transfer numbers.
If the Denied Transfer Numbers contains the entry "all,"
transfers are allowed only to those numbers that appear on the Display
Allowed Transfer Numbers page.
If the Denied Transfer Numbers does not contain the entry "all,"
all transfers are allowed.
Enter a starting extension in the From
field and an ending extension in theTofield to allow a range of numbers. Most administrators choose
to deny all transfers as described in Denying
Call Transfers, and then use this page to specify the few numbers
or classes of numbers that do not affect system security.
For example, enter 4000 in theFromfield and 5999 in theTofield to allow 4-digit transfers to any numbers between 4000
and 5999.
Enter all in the From
and To fields to allow all transfers.
Note: No two allowed
transfer entries can overlap each other. For example, you cannot
make an entry to allow transfer numbers between 4000 and 5999
and then make another entry to allow transfer numbers between
5000 and 6999. Instead, enter one range of from 4000 to 6999.
Click Save to save the information
in the system database, and continue entering ranges of numbers until
you have allowed the necessary numbers.
To confirm that your entries will have the
correct accumulated effect, you can display the ranges together:
Click Back to return to the Call Transfer
page.
Select Display Allowed Numbers to
view the extension ranges you have selected.
Verify that all the extensions you want
to allow are included in the displayed ranges.
Deleting Allowed Transfer Numbers
Use the Delete Allowed Transfer Numbers page to
remove entries from the allowed transfer numbers database. The purpose
of allowed transfer numbers is to specify numbers that would otherwise
be denied due to the list of denied transfer numbers.
If the Denied Transfer Numbers contains the entry "all,"
transfers are allowed only to those numbers that appear on the Display
Allowed Transfer Numbers page.
If the Denied Transfer Numbers does not contain the entry "all,"
all transfers are allowed.
Enter all in theFromfield to deny all transfers. Most administrators choose
to deny all transfers, and then allow a few numbers or classes
of numbers that do not affect system security.
Enter a starting extension in the From
field and an ending extension in the To field
to deny a range of numbers.
For example, enter 4000 in theFromfield and 5999 in theTofield to restrict 4-digit
transfers to any numbers between 4000 and 5999.
Note: No two restricting
entries can overlap each other. For example, you cannot enter
a restriction to any numbers between 4000 and 5999 then enter
another restriction between 5000 and 6999. Instead, enter one
range of 4000 to 6999.
When you finish entering transfer number
information, click Save to save the information in the system
database.
To confirm that your entries will have the
correct accumulated effect, you can display the ranges together:
Click Back on your browser to return
to the Call Transfer page.
Select Display Denied Numbers to
view the extension ranges you have selected.
Verify that all the extensions you want
to deny are included in the displayed ranges.
Deleting
Denied Transfer Numbers
You can delete entries from the denied transfers
numbers database.
The INTUITY AUDIX system
plays a warning message to subscribers when their mailboxes are full.
The system has default thresholds that determine when mailboxes get
full. You can change these thresholds as the use of your system changes.
Note: You must use the sa login
to change data on this screen. Voice messaging administrators who
use the vm login can view only the data on this screen.
Press F3 (Enter) to save the information
in the system database.
The cursor returns to the command line,
and the system displays the message:
Command Successfully Completed.
Enter exit or another administrative
command at theenter command: prompt.
Setting Up Community
Sending Restrictions
A community is
group of subscribers to whom you have assigned some type of calling
restrictions. The administration of communities enables you to further
define the allowed call destinations of your subscribers.
You create a community to prevent members from:
Sending mail to other groups
Receiving mail from other groups
For example, imagine that you have just set
up two communities. Community 1 cannot send messages to international
communities. Therefore, you assign the subscribers who cannot have international
access to Community 1. Community 2 has international access. Therefore,
you assign the international machines and the individuals who are permitted
to access international numbers to Community 2.
Then you administer the communities so that
Community 1 is restricted from sending messages to Community 2. This
process tells the INTUITY AUDIX system which subscribers can and cannot
access international destinations.
Once you have administered all communities
here, you can assign individual subscribers to the desired community
that use the Subscriber screen. You can also assign machines to communities
that are using the Machine Profile screen and the change machine
machine_name command.
Note: You must use the sa login to change data on this
screen. Voice messaging administrators who use the vm login can
view only the data on this screen.
To set up sending restrictions between communities:
Press F3 (Enter) to save the information
in the system database.
The cursor returns to the command line,
and the system displays the message:
Command Successfully Completed.
Enter exit or
another administrative command at the enter command:
prompt.
Setting
Up Outcalling
The Outcalling feature
allows a subscriber to tell the INTUITY AUDIX system to place a call
to a specified number when the subscriber receives new messages. Use
the System-Parameters Outcalling screen to administer the system-related
outcalling parameters.
Security Risk!
Use of the outcalling feature greatly increases the risk of toll
fraud. You must specify a maximum number of outcalling digits that
is as small as possible. You also need to take precautions by placing
additional restrictions on the INTUITY AUDIX outcalling ports, other
INTUITY AUDIX ports, trunk access codes, and so on. See Improving
Outcalling Security for more information.
Note: You must use the sa login to change data on this
screen. Voice messaging administrators who use the vm login can
only view the data on this screen.
Press F3 (Enter) to save the information
in the system database.
The cursor returns to the command line,
and the system displays the message:
Command Successfully Completed.
Enter exit or another administrative
command at theenter command: prompt.
Note: After you have set up outcalling, you must also
assign outcalling permission to each subscriber you want to be
able to use the feature. See Adding, Changing,
and Removing Subscribers for more information.
Broadcast
Messages
A broadcast mailbox allows
subscribers to send broadcast messages or login announcements. You must
set up a specific broadcast mailbox to store the broadcast messages.
When subscribers listen to a broadcast message or login announcement,
the system actually retrieves it from the broadcast mailbox. Likewise,
when subscribers record and send broadcast messages, they store them
in the broadcast mailbox. The broadcast mailbox can contain a maximum
of 16 broadcast messages and 1 login announcement.
Type the name of the broadcast mailboxin the Name: field.
Type the extension of the broadcast message
in the Extension: field. Use an extension that is not
administered on the switch.
Type the Class of Service name or number
you want for this broadcast mailboxin the COS: field.
Type 0in the Switch
Number: field. The zero means that the broadcast mailbox has
a voice messaging mailbox but does not have an extension on the switch.
Type yin the Broadcast
Mailbox? field. The "y" identifies this mailbox as
a broadcast mailbox.
Note: You can
enter data in the Broadcast Mailbox? field only
by using the add subscriber command. You cannot change
a broadcast mailbox to a regular subscriber mailbox or vice-versa
through the change subscriber command. To change the
broadcast mailbox, you must remove the current broadcast mailbox
and add a new one.
Enter the maximum number of days that you
want any particular broadcast message to be active in your system
in the Incoming Mailbox, Retention Times (days) field.
Enter the same number of days for New, Old,
and Unopened.
Enter the maximum number of seconds of mailbox
space for the broadcast mailbox in the Mailbox Size, Maximum
field. A valid entry is a number from 0 to 32767.
Be sure you enter enough time for all the
messages you believe your system will need to store at one time.
Note that the maximum message length for a broadcast message varies,
depending on the maximum message length administered for the specific
subscriber who is creating a broadcast message.
Press F3 (Enter) to save the mailbox
information to the system database.
The cursor returns to the command line,
and the system displays the message:
Command Successfully Completed.
Enter exit or another administrative
command at theenter command: prompt.
Creating
a Broadcast Message
A broadcast message is
a message that you send to all messaging subscribers on your AUDIX system.
It is treated as a new message and is presented before normal messages.
Broadcast messages are useful for company announcements or emergency
announcements.
You create and send a broadcast message normally,
except you do not address it. Instead, you mark the message as a broadcast
message. You cannot send a broadcast message to subscribers on other
systems or at other locations.
Guidelines for Broadcast
Messages
Message notification turns
on subscribers' message-waiting indicators when the message arrives.
Turn on message notification only in emergencies. The system slows down
significantly when many subscribers simultaneously try to get a broadcast
message.
Administer the broadcast mailbox so that the
system deletes the message from the broadcast mailbox when the message
expires.
With a 2-day default expiration, subscribers
can receive the message for up to 3 days, that is, during the day you
send it and the next 2 days. After the third day, the message can no
longer be accessed.
If the broadcast mailbox already has 16 active
broadcast messages, your message is immediately categorized as nondeliverable.
If a subscriber cannot mark a message as
broadcast, the subscriber does not currently have permission to
send broadcast messages. To allow a subscriber to send broadcast
messages, go to the Subscriber screen, page
2 and enter voice in the Broadcast: field.
(OPTIONAL) Press any of the following:
1
Make private. (Press 1 again to undo.)
3
Schedule delivery.
4
File a copy.
Note: A broadcast message cannot also
be a priority message.
(OPTIONAL) Press * M to access the
following additional options:
1
Turn on message notification. (Press 1
again to undo.)
2
Change the message expiration from the
2-day default:
Enter numbers
for the month and day of expiration. For example, press
1 0 0 8 for October 8.
NOTE: The month can consist of either 1 or 2
digits. The day must consist of 2 digits.
Press #
to save the expiration date or press 2 to start
over.
#
Approve additional options.
Press # to approve your message.
Sending
Login Announcements
A login announcement is
a voice mail message that automatically plays to each subscriber when
the subscriber logs into his or her mailbox.
Guidelines
for Login Announcements
Login announcements have
the following special characteristics. They:
Do not turn on message-waiting indicators.
Therefore, do not use login announcements for emergencies.
Are not put in subscribers' mailboxes. Subscribers
cannot delete, save, replay, or forward login announcements. Thus,
the only way to replay login announcements is to log in again.
Can be active only one at a time.
Are delivered to subscribers at remote locations
as normal messages.
Do not activate outcalling.
Do not show up on TeleTypewriter (TTY) systems.
Therefore, a hearing-impaired subscriber who uses only TTY for messaging
does not see them. Send TTY subscribers a mail message from a TTY
instead.
Go to all subscribers of the system. Therefore,
be sure to record all login announcements in all languages used.
Record, edit, and address the message as
if it were a normal voice mail message.
Press 9 to mark the message as a login
announcement.
If a subscriber cannot mark a message as
a login announcement, that subscriber does not currently have permission
to send login announcements. To allow a subscriber to send login
announcements, go to the Subscriber screen,
page 2 and enter login in the Broadcast: field.
If the broadcast mailbox already holds
a login announcement that is not yet expired, the AUDIX system informs
broadcasters that new login announcements are nondeliverable.
Note: A login
announcement cannot also be marked as a private or priority
message.
(OPTIONAL) Press:
3
Schedule delivery.
4
File a copy.
(OPTIONAL) Press * M to access the
following additional options:
1
To turn off dial-though capability. (Press
1 again to undo.)
Note: Turning
off dial-through ensures that subscribers hear the entire
announcement when logging in.
2
Change the message expiration from the
2-day default:
Enter numbers
for the month and day of expiration. For example, press
1 0 0 8 for October 8.
NOTE: The month can consist of 1 or 2 digits.
The day must consist of 2 digits.
Press #
to save the expiration date or press 2 again
to start over.