ATT DEFINITY Communications System Generic 3 Instructions Manual

							Attendant Room Status
Issue  3   March 1996
3-137
Administration
Attendant Console Form
The OCC-ROOM an d MAID-STA T buttons must b e administered on the ‘Attendant 
Console’ form.
System-Parameters Customer-Options Form
The “ Enhanced Hosp itality”  field must be enabled on the ‘System-Parameters 
Customer-Options’ form. Note that this field cannot be enabled unless the G3 
version is V3 or later. The Hospitality option must be enabled on the 
‘System-Parameters Customer-Options’ form before you can administer 
associated forms and fields. See your AT&T support representative for 
assistance with the ‘System-Parameters Customer-Options’ form.
System-Parameters Hospitality Form
The six maid state display messages should be administered on the 
‘System-Parameters Hospitality’ form. Defaults are:
 for maid status 1: ‘‘Rooms in State 1’’
 for maid status 2: ‘‘Rooms in State 2’’
 for maid status 3: ‘‘Rooms in State 3’’
 for maid status 4: ‘‘Rooms in State 4’’
 for maid status 5: ‘‘Rooms in State 5’’
 for maid status 6: ‘‘Rooms in State 6’’
‘Language Translations Property-Management’ form
Translations for d isplay messages may be administered on the ‘Language 
Translations Property-Management’ form.
Hardware and Software Requirements
You must have a DXS module to use this feature. 
						

							Feature Descriptions
3-138Issue  3   March 1996 
Attendant Serial Calling
Feature Availability
This feature is available with all G3 releases.
Description
The Attendant Serial Calling feature enables the attendant to transfer trunk calls 
that return to the same attendant position after the called party hangs up. The 
returned call may then be transferred to another station within the switch and this 
can continue to recur. This feature is particularly useful if trunks are scarce and 
Direct Inward Dialing services unavailable. This can cause an outside caller to 
have to redial often to get through to a location because trunks are so busy. 
Once callers have been able to get through to a switch attendant and have 
several calls to make to others on the switch, this feature permits them to keep 
the use of the line into the switch until all their calls are completed.
The Attendant’s display shows that the incoming call is a Serial Call. This 
information is displayed in the Call Purp ose area (far right hand side) of the 
display. The reason c o de displayed is sc.
Once the Attendant Serial Callingfeature has been activated it remains 
activated until either the trunk drops from the switch or the attendant deactivates 
the feature manually (b y depressing the Serial Call b utton). Once the attendant 
answers the serialized call the lamp associated with the serial call button is 
turned on. If that button is not administered then the feature is still activated, 
however no external indication shows that the feature is active (except the 
attendant’s display). If an attendant received a serialized call but has no serial 
call b utton then the feature cannot be d eactivated until the trunk hangs up or until 
an attendant with a serial call b utton becomes the controlling party.
If no attendants are available then the call is placed in the attendant’s priority 
queue.
Considerations
Only attendant users can activate this feature. The Attendant Serial Calling 
feature is only valid on calls that have only one trunk on the connection. Only one 
serial call button may be administered per attendant console. The Serial  Call 
button cannot be assigned to an analog or digital station. The feature can b e 
activated on a conference call as long as only one trunk is on the conference.
Interactions
The following features interact with the Attendant Serial Callin g feature: 
						

							Attendant Serial Callin g
Issue  3   March 1996
3-139
nPriority Queue: A special priority exists for serialized calls.
nCDR/Call Charging: CDR/Call Charging must consider that a single 
outgoing trunk call may have to be broken up and charged to the d ifferent 
parties that dealt with the call.
nThe Attendant Serial Calling feature only works in a DCS environment if 
the attendant who is activating the Attendant Serial Calling feature 
resides on the same node as the trunk that the attendant is currently 
connected to. In addition, the attendant must not be conferenced in with a 
DCS party when activating Serial Call since this would have two trunks on 
the connection that is not allowed for Serial Call activation.
Administration
The Serial Call button can only be administered on an attendant console on the 
“ Console Attendant” form.
Hardware/Software Requirements
No sp ecial hardware is required for this feature. 
						

							Feature Descriptions
3-140Issue  3   March 1996 
Audible Message Waiting
Feature Availability
Audible Message Waiting is available with Generic 3rV1 and all Generic V2 and 
later releases.  However, this feature may not be applicable in countries that 
restrict the characteristics of dial tones provided to users.
Description
Audible Message Waiting is typically, but not necessarily, used on voice 
terminals without message waiting lights. (Often these are analog terminals.) The 
feature places a stutter at the beginning of station d ial tone on a station that has a 
message waiting for it. The message can b e waiting in system memory (to be 
accessed via disp lay or via the voice synthesizer), PMS, MSA, or AUDIX.
Considerations
The system administrator must inform the user where to call to retrieve messages 
that can only come from one messaging system sourc e.
Interactions
None
Administration
Audible Message Waiting is first enabled on a system-wide basis on the ‘System 
Parameter Customer Op tion’ form. When turned on for the system, an additional 
field appears on the ‘Station’ form for enabling the feature on a station-by-station 
basis.
Hardware and Software Requirements
No a d ditional hardware or software is required. Requires a separate software 
right to use fee. 
						

							Audio Information Exchange (AUDIX) Interface
Issue  3   March 1996
3-141
Audio Information Exchange (AUDIX) 
Interface
Description
AUDIX is a message-handling system for recording and distributing spoken 
messages or voice mail. The system contains stored voice prompts that guide 
users when creating, sending, retrieving, answering, saving, and forward ing 
spoken messages.
NOTE:
Your administrator is urged to consult the GBCS Products Security 
Handbook,
 555-025-600, for information on measures to help secure this 
feature from p ossible toll fraud. Also see the Security Violation Notification 
(SVN) feature.
The following is a non-inclusive list of AUDIX app lications. This list d e pends on 
the type of AUDIX system you are using:
nVoice Mail — allows users to send and receive messages to and from 
their voice mail
nCall Answer — provides switch extensions answer coverage via AUDIX
nAutomated Attendant — presents callers with a voice menu of o ptions, 
then routes calls according to the keys the caller p resses
nBulletin Board — (sometimes called Information Service) plays a 
recorded message to callers
nBroadcast Message — enables an AUDIX a dministrator to send 
broadcast messages to all AUDIX users on the system
nDirectory Service — provides a directory of subscribers to the caller
The following activities are available for use b y AUDIX subscribers:
nCreate Message — Record or modify a new message, address it, 
schedule it for delivery, and save a copy (optional).
nScan Incoming Mail— Review new messages and reply or redirect them 
with an added comment, and review or delete old saved messages.
nPersonal Greeting Administration — Record  or  modify one or more 
personal greetings to b e played for callers who reach AUDIX through the 
Call Answer feature, or select the standard AUDIX greeting.
nScan Outgoing Mail— Review,  modify,  or  redirect messages scheduled 
for d elivery; check the status of delivered messages; and review, mo dify, 
redirect, or delete messages saved in the file cabinet. 
						

							Feature Descriptions
3-142Issue  3   March 1996 
nPassword and List Administration — Change user’s personal AUDIX 
password and create, modify, review, or delete mailing lists.
nAUDIX Networking — Send and receive network messages, status 
information, and administrative u pdate information to and from other 
members of the AUDIX product family.
NOTE:
Two types of networking are available: Audio Message Interchange 
Specification (AMIS) analog networking and d igital networking. AMIS 
networking is available with all AUDIX configurations; digital 
networking is available when AUDIX is configured as a system 
external to the DEFINITY  switch, as discussed below.
Several documents, quick references, and other material that fully describe how 
to use AUDIX are available through the Customer Information Center.
Several versions of AUDIX are available: the first, referred to as ‘‘DEF INI TY 
AUDIX,’’ is a system comp rised of circuit packages resident in the switch; the 
second, referred to as ‘‘AUDIX,’’ is a system that is external to the DEFINITY  
switch and connected to the switch by station lines and data links. Add itionally, 
AUDIX systems can be networked through switches or other AUDIX machines. 
Examp les of such systems are AUDIX Voice Power
™ (VP), AUDIX VP Lodging 
and AUDIX VP Auto Attendant. They rely on a data link between the AUDIX 
adjunct on the switch.
The following two sections describe only the ‘‘DEFINITY  AUDIX’’ and ‘‘AUDIX’’ 
offerings.
DEFINITY AUDIX
The DEFI NI TY AUDIX offering is a circuit package sandwich assembly that fits 
inside the DEFI NI TY s y st em  c arri er an d  requires five contiguous slots in the 
switch carrier. For a full d escription of DEFINITY AUDIX, see the following 
DEFI NI TY AUDIX documents:
nDEFI NI TY AUDIX System — System Description, 585-300-205
nDEFI NI TY AUDIX System — Feature Descriptions, 585-300-206
nDEFI NI TY AUDIX — Documentation Guid e, 585-300-011
nPlanning for DEFINITY AUDIX System, 585-300-904
nDEFI NI TY AUDIX System Installation, 585-300-111
nDEFI NI TY AUDIX System Installation Checklist, 585-300-109
nSwitch Ad ministration for DEFI NI TY AUDIX System, 585-300-509
nDEFI NI TY AUDIX System Ad ministration, 585-300-507
nDEFI NI TY AUDIX System Forms Referenc e, 585-300-207
nAUDIX Ad ministration and Data Acquisition Package, 585-302-502 
						

							Audio Information Exchange (AUDIX) Interface
Issue  3   March 1996
3-143
nAMIS Analog Networking, 585-300-512
nA Portable  Guide for Voice Messaging, 585-300-701
nVoice Messaging Quick Reference, 585-300-702
nVoice Messaging Subscriber Document Artwork, 585-300-703
nVoice Messaging Wallet Card, 585-300-704
nAUDIX Business Card Sticker, 585-304-705
nDEFI NI TY AUDIX System  Maintenance, 585-300-110
nDEFI NI TY AUDIX System Announcement Customization, 585-300-516
For details on DEFI NIT Y AU DIX , refer to the above documents.
AUDIX (external to the DEFINITY Switch)
NOTE:
This section describes AUDIX systems external to the DEFINITY switch and 
connected to the switch by station lines and a data link. Do not refer to this 
section if AUDIX is configured using circuit packages resident in the 
DEFINITY switch. For those systems, called DEFINITY AUDIX systems, see 
the previous section, entitled DEFI NI TY AUDIX.
The AUDIX offering is an interface between the DEFINITY system and an AUDIX 
consisting of up to 32 analog (voice) connections for exchange of voice 
messages, and a d ata link for status and control information exchange. An 
AUDIX adjunct is available in both one-cabinet and two-cabinet configurations. 
The one-cabinet configuration provides up to 16 ports. The two-cabinet 
configuration provides up to 32 ports. The analog port interface on the switch 
can be provided by TN742, TN746B, or TN769 circuit packs.
Up to eight AUDIX systems may be connected to a Generic 3r, or G3vs/G3s 
switch, but only one AUDIX system may be directly connected to a Generic 3i 
switch. However, all switches allow the use of AUDIX in a DCS arrangement. 
Each switch can have its own AUDIX which serves only the users connected to 
that switch; or a single AUDIX connected to the switch may serve other switches 
in a DCS network.
For a full d esc ription of AUDIX, see the following AUDIX documents:
nAUDIX Ad ministration, 585-305-501
nAUDIX Ad ministration and Data Acquisition Package, 585-302-502
nAUDIX Call Detail Recording Package, 585-305-506
nAUDIX Documentation Guide, 585-300-010
nAUDIX Feature Descriptions, 585-305-203
nAUDIX Installation, 585-305-105 
						

							Feature Descriptions
3-144Issue  3   March 1996 
nAUDIX Networking, 585-300-903
nPlanning for DEFINITY AUDIX System, 585-300-904
nAUDIX System  Desc rip tion, 585-305-201
nAUDIX Training Tape, 585-300-050
nAUDIX Upgrade Instructions, 585-302-108
nSwitch Ad ministration for AUDIX Voice Messaging, 585-305-505
Refer to the 
AUDIX Documentation Guide, 585-300-010, for the latest issue 
numbers and release-specific information.
Security Measures
Fraudulent long-distance calls may be placed through your voice mail and auto 
attendant system if proper security precautions are not implemented.
The following actions help secure your system from unauthorized use.
nFor both AUDIX and DEFINITY AUDIX:
— To help p revent exchange of information through unassigned Voice 
Mail, remove any unused or unassigned mail.
— Secure the system lines that serve AUDIX and  control where calls 
can be placed. Pay special attention to assigning restrictive COR, 
COS, and FRL to the station lines and trunks serving AUDIX. Use 
switch CDR reports to determine if the station lines connected to 
AUDIX are b eing used for calls that are normally not within your 
sphere of business.
— Change default passwords on voice mailboxes immediately after 
installation and use random numb ers for passwords.
— Require password s at least five d i gits long for user mailboxes.
— Change all system administration passwords to alphanumeric 
codes.
nFor AUDIX only:
— To help prevent having billable calls placed from unauthorized 
transfers outside of the system, turn on the Enhanced Call Transfer 
(ECT) feature. This feature is available in later AUDIX systems that 
connect to an AT&T digital switch. ECT performs call transfer over 
the data link between AUDIX and the DEFI NI TY switch. (The 
destination extensions must be administered on the switch dial 
plan.) 
						

							Audio Information Exchange (AUDIX) Interface
Issue  3   March 1996
3-145
nFor DEFINITY AUDIX only:
— The administrator determines whether to allow transfer only to 
another AUDIX subscriber or to any extension of the correct 
extension length (that is, the number of digits for extensions 
administered through the DEFI NI TY switch.) For example, you may 
be configured to support the four-digit plan, the five-digit plan, etc. 
The most secure ap proach, which is the default, is to only allow 
transfers to other AUDIX subscribers. If the administrator decides 
to allow transfers to any extension, then you should administer the 
COR on the AUDIX ports to prevent calls outside the PBX.
nBoth AUDIX and DEFI NI TY AUDIX provide a maintenance/administration 
port. To prevent unauthorized access to this port, a remote port security 
device provides an added layer of security.
Consult the 
GBCS Products Security Handbook, 555-025-600, for additional 
steps to secure your system and to o btain periodic information about security 
developments.
Considerations
For DEFINITY AUDIX, you must have five contiguous slots in the switch carrier. 
In a ddition to supporting multiple AUDIX systems, the DEFINITY  system c an 
have multiple hunt groups associated with a single AUDIX system. This allows 
partitioning of the voice ports into different hunt groups and different coverage 
paths to cover different voice ports. Thus voice ports can be reserved for 
particular users or groups of users (for example, those that use the particular 
coverage path).
The following features do not use coverage paths:
nTransfer into AUDIX with the feature access c o de or with the GOTO AUDIX 
button.
nReturn Call doesn’t use the coverage path. When a user is in message 
display mo de, and the user is displaying the message that says Call 
AUDIX, the 
CALL-DISP button is used.
For a review of  considerations related to AUDIX, see the planning documents:
nAUDIX System  Desc rip tion, (the external unit), 585-300-905.
nPlanning for DEFINITY AUDIX System, (the circuit pack system), 
585-300-904. 
						

							Feature Descriptions
3-146Issue  3   March 1996 
Interactions
The following features interact with the AUDIX Interface feature.
NOTE:
For further details about features that interact with an external AUDIX 
system, see the 
AUDIX Feature Desc riptions, 585-305-203; for further 
details about features that interact with the DEFI NI TY AUDIX system, see 
the 
DE FI NITY  A UDI X System Feature Descriptions, 585-300-206.
nAbbreviated Dialing (For AUDIX only)
The FAC for Transfer Into AUDIX may b e programmed into an abbreviated 
dialing button.
nAttendant Conference
An attendant that has sp lit a call can conference the call with AUDIX by 
dialing the Transfer Into AUDIX access code. The  attendant p resses 
Rel ea se to drop out of the conference call.
nACD (for external AUDIX only)
A hunt group can be administered as an AUDIX ACD sp lit. AUDIX traffic  
measurements are then available utilizing the ACD Call Management 
System. Login occurs when AUDIX signals the switch to make a voice port 
available for AUDIX service and logout o c curs when AUDIX signals the 
switch to disable the port.
The AUDIX a djunct and ACD CMS must b e connected to the same switch. 
If the AUDIX in the DCS feature is active, a CMS located on a switch other 
than the host switch (AUDIX location) does not provide measurements for 
the AUDIX ports.
Because AUDIX frequently takes voice ports in and out of service for 
maintenance testing, high login activity may be seen for the AUDIX sp lit in 
measurement reports.
On CMS reports that display an agent’s login identifier, AUDIX voice ports 
always show a login identifier that is the same as the extension, even if 
login identifiers are not administered on the switch.
nCall Coverage
When a coverage call successfully completes to AUDIX or is routed from a 
remote switch to the host switch because of coverage, the principal is 
dropped from the call (no temp orary bridge appearance is maintained).
Coverage calls from a remote switch that fail to reach AUDIX as a 
coverage point cannot be returned to the original coverage path on the 
remote switch.
Call Transfer Out of AUDIX interacts with Call Coverage as listed in Table 
3-11.