ATT DEFINITY Communications System Generic 3 Instructions Manual

							Do Not Disturb
Issue  3   March 1996
3-677
If invalid entries are made (such as 32 for the deactivate time) or if system 
conditions (such as all voice synthesis ports busy) prevent entry of a Do 
Not Disturb request, the system informs the user to dial the attendant or 
front desk assistance.
nButton Access
If a voice terminal has a Do Not Disturb button, the user can press the 
assigned button to activate the feature. The handset may be on-hook or 
off-hook; voice prompting is not required. The user must press the button 
a second time to deactivate the feature.
The lamp  associated with the Do Not Disturb button lights when the 
feature is activated and remains lighted until the feature is deactivated.  
An automatic deactivate time is not p rovid e d through button access.
Feature Activation by Attendant
The attendant (or authorized front d esk user) can activate Do Not Disturb for a 
user or a group of users.  (The assigned COR determines which users are in the 
group.)  The attendant presses the Do Not Disturb — Extension or the Do Not 
Disturb  — Group button.  After pressing the Extension button, the attendant 
enters an extension number; after pressing the Group button, the attendant 
enters an appropriate COR number.
System prompts appear on the display to direct the attendant on what 
information to enter, and a displayed message notifies the attendant when the 
request is confirme d.  If a Do Not Disturb request is denied, a displayed 
message, including a reason for the denial, informs the attendant.
The attendant can cancel a Do Not Disturb request by activating the feature, 
entering the desired extension numb er or group COR number, and pressing the 
Delete button.
Activation of Do Not Disturb Through a PMS
The system provides an interface to a PMS.  This interface can allow activation 
and d eactivation of controlled restrictions.  Activation of Do Not Disturb through a 
PMS is similar to that of Termination Restriction.  A scheduled deactivate time is 
not specified.
Audit Trail Reports
The system keeps an audit trail record of all voice terminals that are in the Do Not 
Disturb  mo de and that have Termination Restriction activated.  The System 
Manager or other d elegated administration personnel can request a listing of this 
information to be displayed at a terminal or to be printed at a designated printer.
The following reports can be administered for printing on a daily basis: 
						

							Feature Descriptions
3-678Issue  3   March 1996 
nDo Not Disturb Status Report — This report lists all extension numbers 
with Do Not Disturb active.  The specified Do Not Disturb deactivate time 
for each extension numb er is also listed.
nDo Not Disturb Plus COR Status Report — This report lists all extension 
numbers as defined above, plus a list of those extension numbers whose 
Controlled Restriction level is Termination Restriction.  (Termination 
Restriction is activated by the attendant for a specific extension or COR.  
A deactivate time is not associated with Termination Restriction.)
Audit trail records do not include Do Not Disturb information for extensions that 
are both termination and Outward  Restricted.
Considerations
The Do Not Disturb feature lessens the attendant’s work load since each voice 
terminal user can activate the feature.  Also, through the voice messages 
supplied by the system, the user is assured that his or her request is confirmed.
The Do Not Disturb deactivate time may be requested using standard time or 
military time.  If standard time is entered, the system will prompt the user to enter 
a.m. or p.m.
A front d esk user must have console permission COS in order to activate this 
feature.
The number of available speech synthesis ports is the only limit on the number of 
voice terminal users receiving voice prompting at the same time.
Interactions
The following features interact with the Do Not Disturb feature.
nAutomatic Callback
Do Not Disturb does not block an Automatic Callback call.  Return calls 
will terminate at a voice terminal in the normal way.
nAutomatic Wakeup
An Automatic Wakeup call d eactivates Do Not Disturb  and alerts the g uest 
at the specified time.
nCall Coverage
If a point in a coverage path has Do Not Disturb active, calls covering to 
that coverage point extension still alert that extension unless it has 
controlled restriction termination activated. When the feature is set to 
“coverage” and a station d oes not have a coverage, the calls are route d to 
the attendant. 
						

							Do Not Disturb
Issue  3   March 1996
3-679
nCall Forwarding All Calls
If Do Not Disturb  is active at the forwarding extension, the caller will 
receive intercept treatment. If Do Not Disturb  is active at the forwarded-to 
extension, the call alerts the forwarded-to extension.
nControlled Restriction
When a station has total controlled restriction, it cannot receive or place 
any calls. However, it can receive a call if another station has an auto-icom 
button pointing to the controlled restriction station.
nInternal Automatic Answer (IAA)
Activation of the Do Not Disturb feature preempts IAA at the called voice 
terminal.
nPMS Interface
Check-Out from either a PMS or the switch automatically deactivates Do 
Not Disturb for the sp ecified extension numb er.
Administration
Do Not Disturb is administered by the System Manager.  The following items 
require administration:
nFeature A c cess Code (one code can be used to activate and deactivate 
Do Not Disturb)
nDo Not Disturb button (per voice terminal, optional)
nDo Not Disturb — Extension b utton (per attendant console or front d esk 
terminal)
nDo Not Disturb — Group button (per attendant console or front desk 
terminal)
nIntercept treatment for call attemp ts to a terminal with Do Not Disturb 
active — Choice is one of the following: intercept tone, record ed 
announcement, coverage, or attendant
Hardware and Software Requirements
Requires a TN725 Speech Synthesis circuit pack if voice prompting is used.  
Each circ uit pack has four ports to provide voice promp ting.
No a d ditional software is required. 
						

							Feature Descriptions
3-680Issue  3   March 1996 
3
E1 Trunk Service
Feature Availability
This feature is available with G3i-Global, G3V2, and later releases.
Description
Provides the same service as DS1 Trunk Service at 2.048 mb ps rate and with 32 
channels. See the DS1 Trunk Service feature. 
						

							EIA Interface
Issue  3   March 1996
3-681
EIA Interface
Feature Availability
This feature is available with all Generic 3 releases.
Description
Provides an alternative for host connections and analog voice terminal users who 
use simple data terminals or Personal Comp uters (PCs) which emulate simp le 
data terminals. Also for interconnection between an EIA-232 comp atible DTE and 
the system.   However, it is not for use with PCs using PC communications 
packages. The EIA Interface consists of a Data Line circuit pack port and an 
ADU.
The EIA Interfa c e supports speeds of LOW, 300, 1200, 2400, 9600, and 19200 
bps.
A data line port d iffers from a data module in that the functions (options) are set 
in the system rather than at the physical hardware. The user does not have 
physical access to the d ata line port, but has access to all data module related 
functions; that is, the user can examine and change such items as speed, parity, 
and so on, via a menu-driven selection mode at the DTE, if permitted by the 
administrator. Also, the Management Terminal can be used to examine and 
change the functions.
A data line p ort in conjunction with an ADU can b e used to connect the system to 
the ISN. The ISN consists of p a cket data switches that support data calls 
between d ata endpoints. Data line ports provide the most economical access to 
the ISN. Available ADUs are the Z3A1, Z3A2, Z3A3, and Z3A4.
DCE may also be connected to a data line port by use of a null modem.
Considerations
The system’s EIA Interface support offers a c onvenient and lower-cost alternative 
for host connections and for analog users with simp le data terminals. DTEs can 
connect directly to a Data Line circuit pack which functions as a data module 
connected to a Digital Line p ort. Since the user does not have p hysical access to 
the data mo dule, all relate d data module options are setta ble from the DTE. With 
a density of eight data line p orts per circuit pack, each port p rovides connections 
of user’s asynchronous EIA-232 compatible DTE.
There is no limit to the numb er of Data Line circuit packs the system can support, 
subject to slot availability and the system limit of digital data endpoints.
Flow control signaling is not  provided. 
						

							Feature Descriptions
3-682Issue  3   March 1996 
Interactions
The following features interact with the EIA Interface feature.
nData Terminal Dialing
Data Terminal (Keyboard) Dialing permission must be granted before 
Keyb oard Dialing can be accessed.
Access to ISN endpoints requires two-stage dialing, the first stage 
consisting of  dialing a hunt group extension number to access ISN, then 
the second stage consisting of an ISN a d dress.
Administration
EIA Interface support is assigned on a per-data terminal basis by the System 
Manager. The  following items  require a dministration:
nData Line circuit pack — Assign a vacant p ort, port options, and 
permissions on the circuit pack to the associated DTE.
nData Extension buttons — Assign Data Extension buttons to 
multi-appearance voice terminals.
The following permissions can be administered on a data line port to allow DTEs 
to be used.
nKeyb oard Dialing (KYBD) — Must be set to allow data endpoints to 
receive and send text d uring data call origination or termination. Text 
prompts are p rovid e d.
nConfiguration — Must be set to allow DTEs to change their data module 
options; that is, examine and change options, such as speed, from the 
DTE. Keyboard Dialing permission must be granted first.
nBusy-Out — Should be set for DTEs that are memb ers of a hunt group, 
and to allow busy out (when DTE turns power off) so that calls will not 
terminate on that DTE.
The following options can be examined and changed from the DTE if the 
configuration permission has been granted:
nSpeed — All speeds (up to 19.2 kb ps) at which the DTE can operate are 
selectable, including Autoadjust. Autoadjust is the c a pability of the data 
line port to d etermine what sp eed and parity the associated DTE is 
transmitting at and match it for terminal dialing and/or text feedback 
purposes.
nParity — All c hoices of parity (even, odd, mark, or s pace) c an b e selected.
nPermit Mismatch — The EIA Interface may be operated at a different 
transmission speed rate than the rate of the far end data module. This 
allows for calls between digital endpoints with different speeds without 
changing the speed of the DTE. 
						

							EIA Interface
Issue  3   March 1996
3-683
nDial Echoing — Can be set to echo typed characters back to the DTE 
during dialing.
nDisconnect — Set the signal to indicate disconnect. Choices are one 
break greater than two seconds or two breaks within one second.
nAnswer Text — Can b e selected when DTE is an intelligent device to allow 
text messages to be delivered to the DTE from the system when a call is 
being answered; also, applies to text generated b y the data line circuit. 
The following call progress messages may b e answered:
— INCOMING CALL
— PLE A SE A NSW ER
— TRANSFER
— FOR WA RDED
— A NSW ER ED
— ABANDONED
— DISCONNECTED
— OTHE R E N D
nConnected Indication — Can b e set to allow the text ‘‘CONNECTED 
SPEED= XXXX’’ to be sent to the DTE when the data call has been 
established.
nOther Characteristic s — The Data Line circ uit always o perates in 
automatic answer (p rovided the DTE is on), asynchronous, and full duplex 
modes. The ‘‘Loss of Carrier Disconnect’’ is set to off; that is, the Data Line 
circuit, unlike other data modules, does not disconnect upon loss of EIA 
updates in the previous four seconds.
Hardware and Software Requirements
One TN726 Data Line circ uit pack is required for each eight EIA interfaces 
provided. One ADU is required for each port on the circ uit pack.
No a d ditional software is required. 
						

							Feature Descriptions
3-684Issue  3   March 1996 
Emergency Access to the Attendant
Feature Availability
This feature is available with all Generic 3 releases.
Description
Provides for emergency calls to be placed to an attendant. These calls can be 
placed automatically by the system or c an b e d ialed b y system users. Such calls 
can receive priority handling by the attendant.
Emergency calls to the attendant can be placed in the following ways:
nAutomatically by the system
If a voice terminal has been assigned the Off-Hook Alert option via COS, 
and if that voice terminal is left off-hook until the intercept timeout occurs, 
the (administrable) off-hook alerting timer is starte d.  If the station is still 
off-hook when the off-hook alerting timer expires,  an emergency call is 
automatically placed to the attendant.
nDial access by a system user
A system voice terminal user can place an emerg ency call to the 
attendant by dialing the Emergency Access to the Attendant feature 
access code.
When an emergency call is placed, one of the available attendant consoles 
receives visual and audible notification of the call. However, if all attendants are 
busy, the call enters a unique queue for emergency calls. This queue allows 
attendants to handle emergency calls separately from other calls. If the queue is 
full, the call, if administered to do so, can be redirected to another extension.
An emergency call causes the following to occur:
nThe system selects the first available console to receive the call, even if 
the call first entered the emergency queue.
nThe Emergency tone alerts the selected attendant and the lamp 
associated with the Emerg ency button, if assigned, lights at that attendant 
console. If the console is an older console (does not have emergency tone 
capability), normal ringing is heard and the d isplay flashes.
nWhen the call arrives at an available console, the attendant display shows 
the following:
— The call appearance that received the call
— The calling party identification 
						

							Emergency Access to the Attendant
Issue  3   March 1996
3-685
— The calling party extension number
— The number of emergency calls remaining in queue
An attendant can place a normal call on hold in order to receive an emergency 
call.
An audit record is created for each emergency call event. This record  includes 
the following:
nThe extension number and name where the call was originate d
nThe extension number of the attendant or attendant g roup that answered 
the call
nThe time the call was originated
nOne of the following known call results:
— Call Completed
Call answered at attendant or LDN night extension.
— Queue Full
Emergency access queue is full; tries to redirect call to an 
emergency access redirection extension.
— No Attd
No active attendants are available to receive the emergency call; 
tries to redirect the call to an emergency access redirection 
extension.
— Redirected Answered
Call answered by emergency access redirection extension.
— No Redirection Ext.
Could not redirect call to emerg ency access redirection extension 
because none are administered.
— Attd Night Service
System is in night service. Will try to redirect call to attendant night 
service.
— Call Abandoned
Caller drops call before it was answered. Call was either waiting in 
the attendant emerg ency queue, ringing at an attendant console, or 
ringing at the LDN night extension.
— Redirected Ab andoned
Caller drops call before it was answered. Call had previously been 
redirected to the emergency access redirection extension. 
						

							Feature Descriptions
3-686Issue  3   March 1996 
The emergency audit records are used to generate an Emergency Access 
A ctivity Report. This report summarizes each emergency access call that was 
attempted d uring the past 24 hours. This report can be scheduled for printing 
once a day at a designated printer. Also, if the system has a journal printer, 
Emergency Access to the Attendant events are printed as they occur.
The System Manager can monitor emergency access call events by displaying 
them at the administration terminal. The command for listing emerg ency call 
events is list emergency. Also, a from and to time option can be used with the 
command. For example, if the command  list emergency from 8:00 a.m. to 
12:00 p.m. was entered, all emergency call events are p rinted at a designated 
printer.
Considerations
Emergency Access to the Attendant provides a way for users to quickly and 
easily get in touch with an attendant. This results in more efficient call handling 
for users.
When the emergency queue is full, any overflow should be redirected to an 
extension number or another queue.
The Emergency button on the console has no function other than to provide a 
visual indication of an incoming emergency call.
The unique Emergency tone cannot be silenced except by answering the 
emergency call.
The system should have at least one day and one night attendant (or night 
service station) for this feature to be useful at all times of the d ay.
Interactions
The following features interact with the Emerg ency Access to the Attendant 
feature.
nCAS 
If the system is a branch location and if CAS is in effect, an emergency 
call is rerouted to the  branch attendant group. If the b ranch does not have 
an attendant or if the branch is not in CAS Backup Service, the call is 
denied.
If the Branch PBX is in CAS Backup Service, an emergency call routes to 
the backup position and is be treated the same as any other 
non-emergency call.