ATT DEFINITY Communications System Generic 3 Instructions Manual

							Queue Status  Indications
Issue  3   March 1996
3-987
In addition to the Oldest Queued Time b utton(s),  the Oldest Queued Time 
status indication can be provided by an auxiliary q ueue warning lamp. 
This lamp  can be installed at any location convenient  to the split agents. 
When the Oldest Queued Time warning threshold is reached,  the auxiliary 
queue warning lamp  lights steadily.
Each Numb er of Queued Calls and Oldest Queued Time b utton is associated 
with a  specific split. Display-equipped voice terminals and consoles can display  
queue status information for a sp lit by pressing the Oldest Queued Time or 
Number of Queued Calls button. The same information is d isplayed no matter 
which of the two buttons is pressed. The split name (or extension if name is not 
assigned), OQT, and Number of Queued Calls are displayed for five seconds 
unless the disp laying terminal or console receives an incoming call or the display 
is put into another mode.  Otherwise, at the end of five seconds, the display 
returns to its previous condition. If the display has two lines, the queue status 
information is displayed on the second line.
In a ddition to providing queue status information for splits, the Queue Status 
Indications feature can be used to provide status information for attendant 
groups or other hunt group types (DDC and UCD). The feature works the same 
with attendant g roups as it does with s plits, except the button names are d ifferent 
and the display shows ‘‘OPERATOR’’ instead of the sp lit name or extension, and 
all status information applies to the attendant group queue. The  attendant 
buttons are the (Attendant group’s Queued Time) (AQT) and the Attendant 
group’s Queued Calls (AQC) b uttons.
Considerations
The Queue Status  Indications feature allows split agents, split supervisors, and 
attendants to monitor queue activity. This information is extremely useful in that it 
allows the agents, supervisors, and attendants to better manage their time.
An NQC, OQT, AQC, and/or AQT button can be assigned to any multifunction 
voice terminal or console.
Interactions
The following features interact with the Queue Status Indications feature.
nAttendant Display and Voice Terminal Display
The timer and the queue status information may be displayed at the same 
time. When this happens, the timer o c cupies the last eight disp lay 
positions  and the number of queued calls is not displayed. This applies 
only to one-line displays. With a two-line disp lay, the timer is displayed on 
the first line and the q ueue status information is displayed on the second 
line. 
						

							Feature Descriptions
3-988Issue  3   March 1996 
nMove Ag ent From CMS
When the CMS is used to move an agent from one sp lit to another, all sp lit 
associated buttons (including NQC and OQT buttons) become associated 
with the new split. 
Administration
The Queue Status  Indications feature is administered by the System Manager. 
The following items require administration:
nButtons:
— NQC (Number of Queued Calls)
— OQT (Oldest Queued Time)
— AQT (Attendant Queued Time)
— AQC (Attendant Queued Calls)
nNQC warning threshold (per sp lit or attendant group)
nOQT warning threshold (0 to 999 seconds) (per split or attendant group)
nPort number assigned to auxiliary queue warning lamp (per split)
Hardware and Software Requirements
Each auxiliary queue warning lamp requires one port on a TN742, TN746B 
(A-law), or TN769 Analog Line circuit  pack. A beehive-type lamp may be used as 
an  auxiliary queue warning lamp. This lamp is available from the Custom Work 
Group. The lamp operates on ringing voltage and can be mounted at a location 
convenient to the group. A ‘‘lamp ed’’ b utton on a multiline set is required for the 
NQC/OQT/AQT or AQC buttons.
No a d ditional software is required. 
						

							R2-MFC Signaling
Issue  3   March 1996
3-989
3
R2-MFC Signaling
Feature Availability
This feature is available with G3i-Global and G3V2 and later releases.
Description
Multifrequency Compelled (MFC) signaling is a form of numb er signaling similar 
to Dual-Tone MultiFrequency (DTMF) in that tones convey the dialed number.
With MFC, the origination and destination switch exchange call progress tones 
that have sp e cific meanings a ccording to the MFC protocol. R2-MFC is a version 
of M FC re c om men d e d  b y the C CITT  f or signaling between a central office (CO) 
and a PBX over analog or digital CO, DID, or Tie trunks.
With R2-MFC administration, care must be taken to identify the origination switch 
and the destination switch. The switch where the call is made is the origination 
switch; the switch where the call is answered is the destination switch. The 
origination switch creates 
forward signals; the d estination switch creates 
backward signals. Forward signals are c lassified as group I and group II signals. 
Backward signals are classified as group A and group B signals. Group I and 
group A signals comprise the b asic signaling set, while more elaborate signaling 
schemes require group II and group B capabilities.
Considerations
The R2-MFC s i gnaling c an be used in CO, DID, DIOD, and TIE trunks. Both 
non-group II signaling and group II signaling are supported on incoming R2-MFC 
calls. The group II signaling protocol has an extra signal which provides the 
caller c ategory information. Only g roup II signaling is supported on outgoing R2- 
MFC calls. Tandem R2-MFC trunk calls are also supported. That is, an incoming 
group II R2-MFC call can route to either a group II R2-MFC trunk or a non-group 
II R2-MFC trunk after all address signals are collected from the incoming R2-MFC 
trunk.
ANI (Automatic number identification) is supported on both incoming (G3V4 and 
later releases only) and outgoing R2-MFC calls. When ANI is collected on an 
incoming R2-MFC call, it is disp layed on the terminal and recorded in the Call 
Detail Re cording (CDR) record. On a tandem R2-MFC call, if ANI is requested on 
an outgoing R2-MFC call, then collected ANI from the incoming trunk is sent out. 
						

							Feature Descriptions
3-990Issue  3   March 1996 
Interactions
nASAI
ANI collected from incoming R2-MFC calls is not passed to the ASAI 
interface.
nARS 
For outgoing R2-MFC calls, the number of digits to be collected from  a 
station and to be outpulsed is based on the ARS translation.
nCall Coverage
The incoming R2-MFC call may be redirected to coverage  according to 
the coverage criteria assigned for external calls.
nCall Detail Recording (CDR)
If ANI is collected on incoming R2-MFC calls, it is recorded on the CDR 
record.
nCall Forwarding
If the called station has the Call Forwarding feature activated, the 
incoming R2-MFC call is forwarded to the designated destination.
nCall Pickup
Incoming R2-MFC c alls c an b e answered by Call Pickup (if  Call  Pickup is 
assigned to the station being rung by an incoming R2-MFC call).
nCall Redirection
Calls will be redirected if any of the following are active: Call Forward ing, 
Call Coverage, Send All Calls, or Night Service and the call is redirected 
to a station other than the one indicated by the R2-MFC signals received 
from the CO.  For incoming group II R2-MFC calls, the backward  signal 
B.X sent by the PBX will corresp ond to the status of the terminating 
endpoint after redirection.
nCall Vectorin g
ANI collected from incoming R2-MFC calls cannot be used for routing on 
vector calls.
nCall Waiting
If this feature is activated on an analog station,  and only one call is active 
at the analog station and an incoming group II R2-MFC  call  terminates at 
the  analog station, then status of the analog station is treated as idle and 
the corresponding B.X signal for the ringing is sent to the CO.
nDID No Answer Timer
The DID NO Answer timer is applied to R2-MFC DID calls. 
						

							R2-MFC Signaling
Issue  3   March 1996
3-991
nDisplay Feature
When the display feature is provided, incoming R2-MFC calls will  be 
identified. If ANI is received on incoming R2-MFC calls, then the caller 
number is displayed. If the display feature is activated on the trunk group, 
the display is up dated after the outgoing R2-MFC call is answered.
nIS D N
If ANI is collected on incoming R2-MFC calls, it is sent out on ISDN 
outgoing trunk calls. If an incoming ISDN call is tandemed out to an 
outgoing R2-MFC trunk and ANI is requested on the outgoing R2-MFC 
trunk, ANI from the ISDN call is sent out.
nLDN and Multiple LDNs
R2-MFC DID calls to LDN numbers should be route d to a LDN extension 
with unique identification of each LDN.
nMalicious Call Trac e
ANI collected from incoming R2-MFC calls is not recorded on malicious 
call trace records.
nNight Service
If night service is activated, R2-MFC DID calls route to a designated night 
extension.
nNight Service No Answer Timer
If a R2-MFC DID c all is routed to the night service destination and the  c all 
is not answered, the R2-MFC DID call will be dropped when the Night 
Service no answer timer is expired.
nSend All Calls
If this feature is activated, the incoming R2-MFC  call  is  immediately 
redirected to coverage.
Administration
Group I, g roup II, group A, and group B signal meanings, and the values for the 
timers used for MFC signalling, can be administered.
MFC Signaling  is  initially assigned on a per-system basis by an AT&T service 
technician. When the R2-MFC Signaling feature is activated, the following items 
are administered by either the System Manager or the Service Technician:
nSystem Parameters Multifrequency —  The following protocols are 
specified:
— Incoming call type (options are group II call type and non-group II 
call type; non-group II call type is the d efault)
— Outgoing call type call (options are group II call type and blank; 
blank is the default) 
						

							Feature Descriptions
3-992Issue  3   March 1996 
The MF DID Intercept Treatment and the request incoming ANI are also 
selected.
nTrunk groups — The trunk groups used with MF Signaling are specified.
The system manager administers the following MFC Signaling options:
nTrunk Group — Select the trunk groups to use with MF signaling
nSystem Parameter MultiFreq  — Test call extension
nSystem Parameter MultiFreq  — Select MFC Interdigit Timer
nSignal meanings for each of these call types are  administrable.
Hardware and Software Requirements
A TN744 v7 or later Call Classifier circ uit pack or a TN2182 Tone Clock circuit 
pack is required as are analog/d i gital CO/DIOD//DID/TIE trunks. 
						

							Recall Signaling
Issue  3   March 1996
3-993
Recall Signaling
Feature Availability
This feature is available with all Generic 3 releases.
Description
Allows the user of an analog station to place a call on hold and consult with 
another party or activate a feature. After consulting with that third party, the user 
can conference the third party with the original p arty by another recall signal, or 
return to the original party b y p ressing Recall twice or b y flashing the switchhook 
twice. (Dig ital stations have similar functionality using their ‘‘Hold’’ and 
‘‘Conference’’ buttons.)
The recall signaling can be accomplished by pressing the flashhook, using a 
Ground Key on a Rotary or DTMF station, or b y using the Recall Button on a 
DTMF station.
Considerations
Use of the flashhook for recall signaling may at times place calls on hold when 
the user of the analog station intended the p revious call to be drop ped before 
dialing the third party.
Administration
The length of the time  during which the system recognizes the press of the 
flashhook as recall signaling is administrable. (Administration of Recall Signaling 
is available on G3i-Global, G3V2, and later releases only.)  Administrators may 
also choose not to administer recall signaling at all. In a d dition, the recall 
signaling can be disabled for particular analog stations.
Hardware and Software Requirements
Some earlier hardware versions of the Analog Line Board do not support the 
administration of the length of the flashhook and disa bling the feature. 
						

							Feature Descriptions
3-994Issue  3   March 1996 
Recent Change History
Feature Availability
This feature is available with all Generic 3 releases.
Description
Allows the user to view or print a history report of the most recent administration 
and maintenance changes.  In G3V4 and later releases, the Recent Change 
History Report also lists each time a user logs in or off the system. The report may 
be used for diagnostic, information, or se curity purposes. 
The system maintains a log in a software buffer of the most recent administration 
and maintenance commands. The log is called the transaction log. Commands 
must be ‘‘data affecting’’ and successfully entered to be saved in the transaction 
log.  The ‘‘data affecting’’ commands are called data commands.
The transa ction log can be displayed or printed as a history report by entering 
the list history or list history print command at the  Management Terminal, or a 
remote terminal. The report can be generated  by any login with Display Admin 
and Maint Data p ermissions.
Commands
A command is made up of multiple words, typed on a Management Terminal 
keyboard, that instruct the system to do a task.  The system command structure 
is ma de up of an Action, O bject, and Qualifier format.
The first command word entered is the action. It specifies the o peration to be 
performed (add, display, change, remove, and so on).
The second command word entered is the object. It sp ecifies the specific object 
to b e operated on (station, trunk group, hunt group, and so on).
The third command  word entered is the qualifier. The Qualifier is one or more 
words or digits used to further identify or complete the Object. Depending on the 
Object used, a Qualifier may or may not b e used. Some commands do not have 
a qualifier, such as the Dial Plan and Feature Access Codes.
Data Commands
With the exception of login and logout, only those a dministration and 
maintenance commands that change the data state associated with any object 
and qualifier are maintained in the transaction log. The commands that change 
data are called data commands. 
						

							Recent Change History
Issue  3   March 1996
3-995
For exam ple, the change station 3600 command would change the state of the 
translation data and so would be classified as a data command and entered in 
the log.  However, the command display station 3600 would not change the 
state of the translation d ata and would not be entered in the log.
The following are the commands that are classified as data commands and are 
saved in the transaction log:
nadd, change, remove, duplicate
nbackup
nbusyout, release
ncancel
nclear
nconfigure
nenable, disable
nformat
nmark
nrecycle
nrefresh
nrestart
nsave
nset, reset
nstart
ntest
nupgrade
nwp (write physical)
The following are the commands that are not classified as d ata commands and 
are not saved in the transaction log:
ncopy
ndownload
nget
nlist, display, status
nload, restore
nmonitor
nrp (read physical)
nupload 
						

							Feature Descriptions
3-996Issue  3   March 1996 
Transaction Log and History Report
Associated data is saved in the transaction log for every data command. This 
data is:
nDate, time
nPort, login
nAction, object, qualifier
A history report of the transaction log data can be disp layed or printed by the 
system administrator by entering the list history or list history print command. 
The data commands are displayed or printed in last in, first out order.
An examp le of a recent change history report is shown in Screen 3-34.
Screen 3-34. Transaction Log
The following is a brief description of the report entries:
nDate of Translation Loaded — The time and date that the translation is 
saved on tape. When a translation is saved on tape, by entering the save 
translation command, the time and date of the save is logg e d on the 
tape. Whenever the system is cold started or rebooted, the transaction log 
is load e d from the tape and the time and date are included on the Recent 
History Report; for example, ‘‘9:53 pm Wed Jul 13, 1994.’’
nDate — The date the data command was entered; for examp le, 07/18.
nTime — The time the data command was entered; for example, 12:34.
   
HISTORY 
                   Date of  Loaded Translation: 9:53pm Wed Jul 13, 1994 
Date   Time    Port  Login   Actn   Object        Qualifier 
     
07/18  12:34   EPN   scust   logf  
07/18  12:23   EPN   cust    cha    dialplan 
07/16  09:44  EPN ncust   rel    station       504 
07/16  09:22 EPN  ncust   busy   station       504 
07/15  15:25 EPN  cust    cha    station       507 
07/15  15:19 NET  cust    cha    system-param  features 
07/15  15:18  NET  inads  dup    station  20001 start 30001 call count 8 
07/15  15:16  EPN  cust    add    station       507 
07/15  15:15 EPN  ncust   logn
07/15  15:09 NET  cust    add    station       505 
07/15  15:06 NET  cust    cha    station       504 
07/15  15:04 EPN  cust    add    station       504 
07/15  15:02 NET  cust    add    station       503 
07/15  15:01 NET  cust    add    station       502 
07/15  14:56 NET  cust    add    station       501 
07/15  14:23 EPN  cust    cha    dialplan