ATT DEFINITY Communications System Generic 3V4 Instructions Manual

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
NOTE:
There is a special case of a switch-classified call
being offered to a split. In this case, the Calling
Party number contains the original digits (from a
switch-classified Third Party Make Call Request)
provided in the destination field.
The Trunk Group number and Trunk Group Member
number are only provided if the Calling Party number is
unavailable.
Called Party
number (DNIS)
For incoming calls over PRI facilities, the Called Party
Number as in the ISDN 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.
For incoming calls over non-PRI facilities, the Called
Party Number is the principal extension [may be a
group (TEG, PCOL, hunt group, VDN) extension
3].
NOTE:
The special case of a switch-classified call being
offered to a split, noted previously, contains the
split extension as provided in the origination field
of the Third Party Make Call Request.
User-Entered
InformationContains up to 16 digits from the most recent Collect Digits
vector step.  For more information regarding vectors, see the
DEFINITY Communications System Generic 3 Feature
Description
, 555-230-204, and the DEFINITY
Communications System Call Vectoring/EAS Guide
,
555-230-520.
Lookahead
Interflow
InformationIf present, this information is passed unchanged to the adjunct
as received by the destination switch.  If information is not
present, no information is passed.
DomainThe extension of the monitored domain.
User to User
InformationIf a call with UUI is delivered to a monitored domain (ACD
split or VDN), the switch includes the UUI stored with the call
in the Call Offered to Domain Event Report.  This applies to
UUI that originated in an ISDN PRI/BRI SETUP message; in
aaaaaaaaaaaaaaaaaaa
3.  If the switch is administered to modify the DNIS digits, then the true DNIS is not passed.
3-20  Issue 4  September 1995 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
an ISDN DISCONNECT message; or in an ASAI Route
Select, 3rd Party Make Call, or 3rd Party Auto-Dial.
Flexible BillingSpecifies that the billing rate can be changed for an incoming
900-type call.  Present if the feature is allowed for the call and
the Flexible Billing customer option is assigned to the switch.
Issue 4  September 1995  
3-21 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Call Originated Event Report (G3V4)
The Call Originated Event Report is sent to notify the adjunct that the originating
extension is attempting to establish a call.  This indication is provided to ASAI
applications monitoring the call through domain control only.  The report provides
the dialed digits.  Link version 2 must be active.  Two instances will not generate
this report: TAC dialing over an ISDN trunk, and COR restrictions.
Report Items
The following is a list of the items provided with this report:
Call_id[mandatory] This switch-assigned call identifier is used to
associate event reports to calls and identify a call the adjunct
wants to control.  The call identifier is unique within the switch.
Party_id[mandatory] The switch-assigned identifier that uniquely
identifies a party on a call; in this case, the party that
originated the call.  The switch provides the identifier and the
adjunct should retain it for future operations.  The party
identifier is unique within the call_id.
Calling Party
Number[mandatory] The number that originated the call; usually the
extension that dialed the call.  For calls originating from a
Logical Agent, this is the logical agent number of the agent
logged into the station making the call.  For calls originating
from a bridged call appearance, this is the number of the
bridged appearance where the origination occurred.
Called Party
Number[mandatory] The number that the user dialed or requested by
means of a Make Call or Auto Dial request.
4
Party
Extension[optional] The originating device. Normally, this is the same as
the calling number; however, in the case where a call is
originated from a logical agent extension, it indicates the
physical extension from which the call was made.  For calls
originating from a bridged call appearance, this is the number
of the primary extension on the phone where the call
originated.
UUI[optional] This parameter is not included.
aaaaaaaaaaaaaaaaaaa
4.  This number is represented before any digit manipulation, but does not include ARS, FAC, or TAC.  The |
contents of this IE may change in subsequent Event Reports generated for a specific call.
3-22  Issue 4  September 1995 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Cause[optional] This parameter is not included.
Issue 4  September 1995  
3-23 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Call Redirected Event Report
The Call Redirected Event Report is sent to notify the adjunct that event
reporting for a call will no longer be provided.  This event report is sent under the
circumstances detailed below.
For Monitored Calls
This event is sent when a monitored call enters a new domain that has Event
Notification active.  For example, if a call leaves one monitored domain and
enters another, a Call Redirected Event Report is sent to the association that the
call left.  The Call Offered to Domain Event Report must have been received
prior to the Call Redirected Event Report.
For G3V3 and later (Multiple Monitors feature), when an Active-Notification Call
enters an Active-Notification Domain, the switch sends a Call Redirected Event
Report over the notification association(s) that were active for the call and sends
further Event Reports over the new notification association(s).
For Controlled Calls
This event report is sent over a Domain (Station) Control association when a call
leaves the station, without the call having been dropped/disconnected.  The
Alerting Event Report must have been received prior to the call Redirected Event
Report.
When a call that had been alerting at the station leaves the station
because:
Ð One member of a coverage and/or answer group answers a call
offered to a coverage group.  In this case, all other members of the
coverage and/or answer group that were alerting for the call receive
a Call Redirected Event Report.
Ð A call has gone to AUDIX coverage and the Coverage Response
Interval (CRI) has elapsed (the principal call is redirected).
Ð Principal answers the call while the coverage point is alerting and
the coverage point is dropped from the call.
Ð Stations are members of a TEG group with no associated TEG
button (typically analog stations). |
Ð The call was redirected using the ASAI Redirect Call capability. |
However, if the Redirect Call request was sent over a domain |
control association, then that domain association receives an Ack, |
but does not receive the Call Redirected Event Report.
When the domain-controlled station is an analog phone and an alerting
call is now alerting elsewhere (gone to coverage or redirected by ASAI
Redirect Call), either:
Ð The pick-up feature is used to answer a call alerting an analog
principals station, or
3-24  Issue 4  September 1995 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Ð An analog phone call is sent to coverage due to ``no answer (the
analog sets call is redirected).
Issue 4  September 1995  
3-25 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
This event report will not be sent if the Domain (Station) Control is never
alerted or if it retains a simulated bridged appearance until the call is
dropped/disconnected.  Examples of situations when this event is not sent
are:
Bridging
Call forwarding
Calls to a TEG (multifunction set with TEG button)
Cover-All
Coverage/Busy
Incoming PCOL calls (multifunction sets)
Pick-up for multifunction set principals
This event report never follows a Connected Event Report and is always
preceded by an Alerting Event Report.
Report Items
The following is a list of the items provided with this report:
Call_idThis switch-assigned call identifier is used to associate event
reports to calls and identify a call the adjunct wants to control.
The call identifier is unique within the switch.
3-26  Issue 4  September 1995 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Call Transferred Event Report
The Call Transferred Event Report is sent under the following circumstances:
When an on-PBX station completes a transfer by pressing the ``transfer
button on the voice terminal
When the on-PBX analog set (phone) user on a monitored call goes on
hook with one active call and one call on conference/transfer hold
When the ``call park feature is used in conjunction with the ``transfer
button on the voice set
When an adjunct successfully completes a Third Party Merge request
(transfer option). The association over which the Third Party Merge
request was made only receives an acknowledgement; no Call
Transferred Event Report is sent over this association. All other
associations controlling or monitoring the resulting call (including the
Domain Control associations) receive the Call Transferred Event Report.
Report Items
The following is a list of the items provided with this report:
Calling Party
number
(controlling
party number)The controlling/transferring extension in the transfer
Called Party
Number (new
party number)The party that the call is being transferred to
If the new transferred-to party is an extension on the
local PBX, the extension is passed.
If the party transferred-to is off the PBX, then a default
value of (#####) is passed.
NOTE:
There are scenarios in which the conference operation
joins multiple parties to a call.  In these cases, the
Called Party Number is the extension for the last party
to join the call.
Other Call_idThe call identifier that ended as a result of the two calls
merging
Resulting
Call_idThe call identifier retained by the switch after the two calls are
merged
Issue 4  September 1995  
3-27 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Party_id List
(up to six
numbers)The party identifier is a number corresponding to a specific
entry number in the Extension List
Extension List
(up to six
entries)The list of all transferred extensions on the call resulting after
the transfer.  It may contain alerting extensions or group
extensions as well as default trunk values (#####) (if the call
contains off-PBX parties).
The extension consists of local extensions or group
extensions.  Group extensions are provided when the transfer
is to a group and it takes place before the call is answered by
one of the group members.
If it is an on-PBX extension and there is an internal error in
the extension, a default value of (*****) is passed.
3-28  Issue 4  September 1995 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Connected Event Report
The Connected Event Report is sent as follows:
When a switch-classified call is delivered to an on-PBX party (after having
been answered at the destination) and the on-PBX party answers the call
(picked up handset or connected after zip tone)
When a call is delivered to an on-PBX party and the on-PBX party has
answered the call (picked up handset or cut-through after zip tone)
When a call is redirected to an off-PBX destination, and the ISDN
CONNect message is received from an ISDN-PRI facility
Any time a station is connected to a call (for example, pick up on bridged
call appearance, service observing, or busy verification)
After a Trunk Seized Event Report for non-ISDN trunks
In general, this event report is not sent for split or vector announcements or
attendant group 0.
Multiple Connected Event Reports
Multiple event reports may be sent for a specific call.  For example, when a call
is first picked up by coverage, the event is sent to the active associations for the
coverage party, as well as to the active associations for all other extensions
already on the call.  If the call is then bridged onto by the principal, the
Connected Event Report is then sent to the associations for the principal, as well
as to the associations for all other extensions active on the call.  For more
information on bridging, see Chapter 12, ``Feature Interactions.
Multiple event reports may also be sent for the same extension on a call.  For
example, when a call is first picked up by a member of a bridge, TEG, or PCOL,
a Connected Event Report is generated.  If that member goes on-hook and then
off-hook again while another member of the particular group is connected on the
call, a second Connected Event Report is sent for the same extension.  This
event report is not sent for split or vector announcements or attendant group 0.
Report Items
The following is a list of items provided with this report:
Calling Party
number/Billing
number
(CPN/BN)
For outgoing calls over PRI facilities Ð ``calling
number as in the ISDN SETUP message
For incoming calls over PRI facilities Ð ``calling
number as in 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
Issue 4  September 1995  
3-29