ATT DEFINITY Communications System Generic 3V4 Instructions Manual

							bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
   
						

							bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbb
Event Reporting and U-Abort
Capabilities
3
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Introductionbbbbbbbb
Common capabilities are those capabilities used by more than one capability
group.  There are two common capabilities: Event Reporting and U-Abort (User
Abort).
This chapter describes these capabilities and the capability groups where they
are present.
Event Reporting
CapabilityThis capability is used by the switch to send call-related
information to an adjunct. For example, if a user makes a call
from his or her telephone, event reports are sent to an adjunct
regarding the call, provided that event reporting has been
requested for this particular telephone or call.
NOTE:
Event reporting does not generate screen-formatted or
hardcopy reports.  Event reporting, for the purposes of
ASAI, simply means that call information is provided to
an adjunct by the switch.  Event Reports are
``informational only.  To control a call, an application
must use call control capabilities.
U-Abort
CapabilityThis capability notifies either the switch or the adjunct that
processing for the association is ending abnormally.  For
example, when switch resources are not available to place a
call, as requested by the adjunct, a U-Abort is returned.
Issue 4  September 1995  
3-1 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Event Reportsbbbbbbbb
Capability Groups and Event Reportingbbbbbbbbbbbbbbb
The Event Reporting capability can be invoked from the following capability
groups:
Call Control Capability Group
Domain (Station or ACD Split) Control Capability Group
Notification Capability Group
See Chapters 4, 5, and 6, respectively, for discussions of these capability
groups.
An administrable option called ``Event Minimization is available for each ASAI
link.  This option may be used when event reports would normally be sent on
multiple associations, but the adjunct does not need to see more than one.
Typically, these event reports are identical except for the association they are
sent over (for example, call control, domain control, active notification).  Some
applications discard duplicate events, so in this case, there is no point in sending
them across the ASAI link.  When enabled, this option allows only a single such
event to be sent.  The selection of the association on which the event will be sent
is based on association precedence as follows: active notification (if enabled),
call control (if enabled), domain control (if enabled).
The Station form is used to change this option.  The new option settings take
effect the next time the ASAI link is activated.
Call-Related Event Reportingbbbbbbbbbbbbbbb
The adjunct receives call-related event reports from the switch for the following
call types:
Controlled Calls Ð Calls controlled by the adjunct via the Call Control
Capability Group
Domain-Controlled Calls Ð Calls controlled by the adjunct via the Domain
(in other words, station) Call Control Capability Group
Monitored Calls Ð Calls for which the adjunct has requested event reports
via the Notification Capability Group
NOTE:
When calls are controlled in some way by the first two capability groups
listed above, event reports are provided to the adjunct.  Call monitoring
(Event Notification) does not have to be invoked separately via the
Notification Capability Group in order for event reports to be generated.
3-2  Issue 4  September 1995 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Non-Call-Related Event Reportingbbbbbbbbbbbbbbb
The event reports mentioned previously were all related to a specific call.  An
event report that is not directly related to a specific call can also be generated.
When an agent logs out of a split/skill that is under Domain (ACD split) Control, a
Logout Event Report is generated.  Starting with G3V4, a Login Event Report is
generated when an agent logs into this type of split.  These reports are
discussed in detail later in this section.
Information Flowbbbbbbbbbbbbbbb
The adjunct does not respond to event reports.  (An adjunct is not required to
send a response when an Event Report is received.)
Parametersbbbbbbbbbbbbbbb
event_name[mandatory]  Specifies the event being reported
item_value_list[optional] Contains a list of items and their values for the
event being reported
Event Reports and Corresponding Itemsbbbbbbbbbbbbbbb
Every event report issued by the Generic 3 switch contains pieces of information
that, individually, are called items.  Item combinations contain information about
the specific event being reported.  The following table presents the different
event reports and the corresponding items available to the Event Reporting
capability.
In general, event reports are not sent for split or vector announcements or
attendant group 0.
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Event Report Items Provided with Each Event Report
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Calling Party number (CPN/BN) or
Trunk Group number and Trunk Group Member number
Ð only provided if the Calling Party number is unavailable
Called Party number (originally dialed number)
Cause
Connected Party number (alerting number)
Call_id
Party_id Alerting
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb c c c
c
c c c
c
c
c c c
c
c
c c c
c
c c c
c
c c c
c
c
c c c
c
c
c c c
c
Issue 4  September 1995  
3-3 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Event Report Items Provided with Each Event Report
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Domain (ACD split associated with the call Ð if any)
User to User Information (UUI)
Reason for Redirection Alerting, contd.
Called Party number
Connected Party number (answering party number)
Call_id
Party_id
Cause  (Special Information Tone [SIT] or Answering
Machine Detection [AMD] Ð if any) Answered
Called Party number (busy number)
Call_id
Cause Busy/Unavailable
Calling Party number (conference initiator party number)
Called Party Number (newly added party number)
Other Call_id
Resulting Call_id
Party_id List (up to six party_ids)
Extension List (up to six extensions) Call Conferenced
Call_id
Cause Call Ended
Call_id
Party_id Call Initiated
Calling Party number (CPN/BN) or
Trunk Group number and Trunk Group Member number
Ð only provided if the Calling Party number is unavailable Call Offered to Domain
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb c c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
3-4  Issue 4  September 1995 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Event Report Items Provided with Each Event Report
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Call Offered to Domain,
contd.
Called Party number (DNIS)
Call_id
Item indicator (User-Entered Information  Ð contains up to
16 digits from the most recent Collect Digits vector step)
Lookahead Interflow Information
Domain (ACD split or VDN)
User to User Information (UUI)
Flexible Billing
Call_id
Party_id
Calling Party number
Called Party number
Party extension Call Originated
Call_id Call Redirected
Calling Party Number (transfer initiator party number)
Called Party Number (transferred party number)
Other Call_id
Resulting Call_id
Party_id List (up to six party_ids)
Extension List (up to six extensions) Call Transferred
Calling Party number (CPN/BN) or
Trunk Group number and Trunk Group Member number
Ð only provided if the Calling Party number is unavailable
Called Party number (DNIS)
Connected Party number
Call_id Connected
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
Issue 4  September 1995  
3-5 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Event Report Items Provided with Each Event Report
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Party_id
Cause Connected, contd.
Call_id
Party_id
Progress Indicator Cut-Through
Connected Party number (dropped number)
Call_id
Party_id
Cause
User to User Information (UUI) Disconnect/Drop
Digits Entered Digits
Connected Party number (number that placed the
call on hold)
Call_id
Party_id Hold
Work Mode
Agent Physical Extension
Agent Logical Extension Login
Agent Physical Extension
Agent Logical Extension Logout
Called Party number (DNIS)
Call_id
Calls in Queue
Domain (ACD split) Queued
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
3-6  Issue 4  September 1995 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Event Report Items Provided with Each Event Report
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Connected Party number (number that reconnected to the
call)
Call_id
Party_id Reconnected
Called Party number (default unknown)
Call_id
Cause Reorder/Denial
Called Party Number
Call_id
Party_id Trunk Seized
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
Issue 4  September 1995  
3-7 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Alerting Event Report
The switch sends the Alerting Event Report for monitored, controlled, and
domain-controlled calls when the following events occur:
The originator of a switch-classified call1 is an on-PBX station, and ringing
or zip tone is started.
When a call is redirected to an off-PBX station and the ISDN ALERTing
message is received from an ISDN-PRI facility.
When a switch-classified call is trying to reach an off-PBX station, and the
call classifier detects either precise, imprecise, or special ringing.
When a switch-classified or user-classified call is placed to an off-PBX
station, and the ALERTing message is received from the ISDN-PRI
facility.
NOTE:
When a classifier and an ISDN-PRI facility both report alerting on a
switch-classified call, then the first occurrence generates an Alerting
Event Report; succeeding reports are not reported by the switch.
Consecutive Alerting Event Reports are possible in the following cases:
A station is alerted first and the call goes to coverage; an Alerting Event
Report is generated each time a new station is alerted.
A principal and its bridging users are alerted; an Alerting Event Report is
generated for the principal and for each bridged station alerted.
A call is alerting a Terminating Extension Group (TEG); one report is sent
for each TEG member alerted.
A call is alerting a Personal Central Office Line (PCOL); one report is sent
for each PCOL member alerted.
A call is alerting a coverage/answer point; one report is sent for each
alerting member of the coverage answer group.
A call is alerting a principal with SAC active; one report is sent for the
principal and one or more are sent for the coverage points.
The Alerting Event Report is 
not sent for calls that connect to announcements as
a result of ACD split forced announcement or announcement vector commands.
When an already queued ASAI-monitored call reaches a converse vector step,
the ALERTing message sent to the ASAI host will include an optional cause
(CS3/23) to inform the ASAI host that the call has not been de-queued.
aaaaaaaaaaaaaaaaaaa
1.  Switch-classified and user-classified calls are a type  of  Third Party  Make Call.  See Chapter 4,  ``Call Control
Capability Group for a detailed discussion.
3-8  Issue 4  September 1995 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Report Items
The following is a list of items provided with this report:
Calling Party
number
For outgoing calls over PRI facilities Ð ``calling
number from the ISDN SETUP message.
For outgoing calls over non-PRI facilities or on-PBX
calls Ð locally originating extension.
For incoming call over PRI facilities Ð ``calling number
from the ISDN SETUP message.
For incoming calls over non-PRI facilities, the calling
party number is generally 
not provided.  In this case,
the Trunk Group number is provided instead.
For calls originated at a bridged call appearance Ð the
principals extension.
For incoming DCS calls, if the DCS calling party
information is available to the switch (if a station with a
display gets it), this information is also made available
to ASAI.  Otherwise, the calling party information is
provided as the default.
Trunk Group
number/Trunk
Group Member
number
The Trunk Group number and Trunk Group Member
number are only provided if the Calling Party number is
unavailable.
Called Party
number (DNIS)
For outgoing calls over PRI facilities, the called number
as in the SETUP message.
For outgoing calls over non-PRI facilities, the called
number is the default trunk value (#####).
For incoming calls over PRI facilities, the called number
is the one provided in the SETUP message.
For incoming calls over PRI facilities to a VDN that
does lookahead interflow on calls, if the lookahead
interflow attempt fails, the called number provided is
the principal extension of the dialed number.  If the
interflow attempt is successful, the Called Party
number is provided as the default.
For incoming calls over non-PRI facilities, the called
number is the principal extension (may be a group
[TEG, hunt group, VDN] extension)
2
aaaaaaaaaaaaaaaaaaa
2.  If the switch is administered to modify the DNIS digits, then the modified DNIS string is passed.
Issue 4  September 1995  3-9