ATT DEFINITY Communications System Generic 3V4 Instructions Manual

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Reconnected Event Report
This event report is generated under the following circumstances:
When an on-PBX station connects to a call that has been previously
placed on hold.  Reconnecting to a held call can be done either manually
at the station (by reselecting the active call appearance or switch hook
flash) or via a Third Party Reconnect capability.
NOTE:
An association requesting Third Party Reconnect capability (the
association over which the capability was requested) receives an
acknowledgement and does not receive a Reconnected Event
Report.  Event reports are sent over the other associations
monitoring and/or controlling the call.
Report Items
The following is a list of items provided with this report:
Connected
Party numberThe extension that has been reconnected to the call
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.
Party_idThe switch-assigned identifier that uniquely identifies a party
on a call.  The switch provides the identifier and the adjunct
should retain it for future operations.  The party identifier is
unique within the call_id.
3-40  Issue 4  September 1995 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Reorder/Denial Event Report
The Reorder/Denial Event Report is generated:
When a call is trying to terminate to an on-PBX destination but the
destination specified is inconsistent with the dial plan, has failed the ``class
of restriction check, or inter-digit timeout has occurred
When a call encounters a step in vector processing that causes the denial
treatment to be applied to the originator
When a direct-agent call is placed to a destination agent who is not a
member of the specified split
In a non-EAS environment, when a direct-agent call is placed to a
destination agent who is not logged in
In an EAS environment, when a direct-agent call is placed to a logical
agent ID that doesnt have a coverage path and is not logged in
Report Items
The following is a list of items provided with this report:
Called Party
numberIf the destination is inconsistent with the dial plan, the default
extension value is sent (*****).
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.
CauseContains the reason for the reorder and/or denial
For this event report, any and all standard ISDN/PRI cause
values are valid and are passed intact from the network to the
adjunct.  However, the following cause values are also
explicitly sent from the switch:
Call rejected (CS0/21)
Invalid number (CS0/28)
Outgoing calls barred (CS0/52)
Incompatible destination (CS0/88)
ASAI-specific cause values for this report are: Agent not
member of split (CS3/11) and Agent not logged in (CS3/15).
Both cause values are for direct-agent calls.
Issue 4  September 1995  
3-41 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Trunk Seized Event Report
The Trunk Seized Event Report is sent as follows:
When a call is placed to an off-PBX destination and a non-PRI trunk is
seized
When a call is redirected to an off-PBX destination and a non-PRI trunk is
seized
A Trunk Seized Event Report is 
not generated for outbound calls that use
ISDN-PRI facilities, or for the destination of a switch-classified call.
Report Items
The following is a list of items provided with this report:
Called Party
numberAlways the default trunk value (#####)
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.
Party_idThe switch-assigned identifier that uniquely identifies a party
on a call.  The switch provides the identifier and the adjunct
should retain it for future operations.  The party identifier is
unique within the call_id.
3-42  Issue 4  September 1995 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Use of Event Reports in Associationsbbbbbbbbbbbbbbb
The following table shows the type of association(s) over which various event
reports can be sent.
Table 3-1.  Use of Event Reports in Associations
bbbbbbbbbbbbbbbbbbbbb
Domain Domain
Event (Station) (Split)
Report Control Call Control Notification Control
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Alerting YES YES YES NO
Answered YES YES NO NO
Busy/Unavailable YES YES YES NO
Call Conferenced YES YES YES NO
Call Ended NO NO YES NO
Call Initiated YES NO NO NO
Call Offered to Domain NO NO YES NO
Call Originated YES NO NO NO
Call Redirected YES NO YES NO
Call Transferred YES YES YES NO
Connected YES YES YES NO
Cut-Through YES YES YES NO
Disconnect/Drop YES YES YES NO
Entered Digits NO YES YES NO
Hold YES YES YES NO
Login NO NO NO YES
Logout NO NO NO YES
Queued YES YES YES NO
Reconnect YES YES YES NO
Reorder/Denial YES YES YES NO
Trunk Seized YES YES YES NOc c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
  
Issue 4  September 1995  
3-43 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Event Reporting for Merging Two Callsbbbbbbbbbbbbbbb
This section covers the rules for sending events when two calls with different
characteristics are merged for a transfer or a conference.  For the purpose of
these rules, it does not matter how the calls were merged (manually or via the
Third Party Merge capability).
Call merging rules are as follows:
1. Merging two Call-Controlled calls
A Third Party Call Ended capability is sent for the call identifier that
has been released as a result of the merge on the association that
is controlling the call.
The Call Transferred or Call Conferenced Event Report is sent over
the association controlling the resulting call identifier.
Subsequent event reports for the merged call are sent over the Call
Control association controlling the resulting call identifier.
2. Merging two monitored calls (Event Notification is active)
A Call Ended Event Report is sent over the association monitoring
the call for the call identifier that has been dropped.
The Call Transferred or Call Conferenced Event Reports are sent to
the association monitoring the resulting call identifier.
Subsequent event reports are sent over the Event Notification
association monitoring the resulting call identifier.
3. Merging one Call-Controlled call with a nonmonitored or controlled (Event
Notification or Call Control are not active) call
The Call Transferred or Call Conferenced Event Reports are sent
over the Third Party Call Control association.  This association
continues to report subsequent events for the remaining call.
4. Merging one monitored call (Event Notification active) with a nonmonitored
or controlled (Event Notification and Third Party Call Control are not
active) call
The Call Transferred or Call Conferenced Event Reports are sent
over the Event Notification association.
Subsequent event reports are sent over the Event Notification
association of the monitored call.  In the case where the resulting
call is the nonmonitored call, the Call Conferenced or Call
Transferred Event Report is the very first event the adjunct
receives with a new call identifier.  If the resulting call identifier is
from the Call-Controlled call, the adjunct receives the Call
Conferenced or the Call Transferred Event Report(s).
5. Merging one Call Control association and one monitoring association
Both associations are retained and continue to provide subsequent
event reports for the resultant call.
3-44  Issue 4  September 1995 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
The Event Notification association could receive a Call Ended
Event report for the call that has been released as a result of the
merge.  This only occurs if the call being released is a monitored
call.
Both associations receive a Call Conferenced or Call Transferred
Event Report.
6. Merging two calls with Domain (Station) Control extensions
Subsequent event reports for the resulting call are provided for the
Domain (Station) Control associations for extensions remaining on
the call.
A Call Conferenced or Call Transferred Event report is provided to
add Domain Control associations.
7. Merging one Domain (Station) Control and one Third Party Call Control
association
All subsequent event reports for the resultant call are provided to
both associations.
8. Merging two calls, one of which is not monitored or controlled, and the
other containing only Domain (Station) Control extension(s)
Subsequent event reports are provided for the Domain (Station)
Control association for the extensions remaining on the resultant
call.
9. Merging two calls with a combination of a Domain (Station) Control
association and an Event Notification association
The Event Notification association could receive a Call Ended
Event report for the call that has been released as a result of the
merge.  This only occurs if the call being released is a monitored
call.
A Call Conferenced or Call Transferred Event report is provided to
the Event Notification association and the Domain (station) Control
association.
Subsequent event reports for the call are provided over the Event
Notification association.
10. Merging two calls with a combination of Call Control, Event Notification,
and Domain (Station) Control associations (but only one call control and
only one Event Notification association between the two calls).  Items 5, 7,
and 9 apply to this case.
Issue 4  September 1995  
3-45 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
For G3V3 and later, the Multiple Monitors feature impacts transfer and
conference situations as follows:
If the resultant call (after the conference or transfer) has ANY notification
associations active, the switch sends further Event Reports over the
associations that were active for the resultant call. The switch also sends
the Call Ended Event Report over the notification associations for the
other call.
Scenario 1: Call-1 has notification associations A1, A2.  Call-2 has
notification association A3.  Call-2 is the resultant call.
After the merge (transfer, in this case) events are sent as follows:
A1: Call Ended
A2: Call Ended
A3: Call Transferred, further-events
If the resultant call (after the conference or transfer) has NO notification
associations active, the switch sends further Event Reports for the
notification associations that were active for the other call. The Call Ended
event is not sent over any notification associations.
Scenario 2: Call-1 has notification associations A1, A2.  Call-2 has NO
notification associations.  Call-2 is the resultant call.
After the merge (transfer, in this case), events are sent as follows:
A1: Call Transferred,  further-events
A2: Call Transferred,  further-events
3-46  Issue 4  September 1995 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Table 3-2 provides a summary of the call merging rules described above.
Table 3-2.  Call Merge Summary
bbbbbbbbbbbbbbbbbbbbb
Call Resultant Conf/Xfer Event Call Ended Event
Characteristics Association(s) Sent to: Sent to:
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
1. Call-Ctl & Call-Ctl* Ctl Assoc Resultant Assoc Other Ctl Assoc
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
2. Monitored & Monitored Monitored Resultant Assoc Other Monitored Assoc
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
3. Call-Ctl & non-Ctl & non-Monitored Call-Ctl Call-Ctl Assoc -
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
4. Monitored & non-Ctl/non-Monitored Monitored Monitored Monitored
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
5. Call-Ctl & Monitored Both Both Monitored
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
6. Dom-Ctl & Dom-Ctl** Both Both -
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
7. Dom-Ctl & Call-Ctl** Both Both -
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
8. non-Ctl non-Monitored Dom-Ctl Dom-Ctl Dom-Ctl -
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
9. Dom-Ctl & Monitored Both Both Monitored
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
10. Monitored/Ctl/Dom-Ctl All All -c c c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c c c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c c c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
* Allowed via Third Party Merge on Call Control
** Allowed on a Third Party Merge of a Domain (Station) Control Association
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Rules for Merging Two Calls with UUI
Information
bbbbbbbbbbbbbbb
1. In transfer and conference scenarios in which UUI is associated with both
calls, the UUI associated with the resulting call is kept for the new call.
2. In transfer and conference scenarios in which UUI is associated with
either one of the two calls, the UUI is associated with the resulting call.
3. If a call with UUI is held to initiate a transfer or conference, and the
second call is placed without UUI, then the following occurs: If the event is
sent before the two calls are merged by the completion of the conference
or transfer, an event report or ISDN message sent about the second call
will not include UUI.
Issue 4  September 1995  
3-47 
						

							Event Reporting and U-Abort Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
U-ABORTbbbbbbbb
This capability is used by both the adjunct and the switch to inform the other that
an association is abnormally ending.  It is shown here but may be used in all
capability groups at any time during an association.
Information Flowbbbbbbbbbbbbbbb
The U-Abort ends the association and no response is possible.
U-Abort Parametersbbbbbbbbbbbbbbb
The switch may issue one of the following reasons as the cause for ending the
association: |
Error in vector/host not responding (CS0/102) |
Either the vector is incorrecly programmed or the host has not responded |
to the route request in a timely manner. |
Protocol error (CS0/111) |
The Q.932 protocol has been violated. |
Call merge attempt failed (CS0/98) |
An attempt was made to merge two calls that were not controlled. |
Error in association (CS3/87) |
The switch software audits found something wrong and the switch is |
taking steps to correct the association. |
NOTE:
For more information regarding protocol errors and a complete list of
reason codes (cause values), see the 
AT&T DEFINITY Communications
System Generic 3 CallVisor ASAI Protocol Reference
, 555-230-221.
3-48  Issue 4  September 1995 
						

							bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbb
ASAI and Call Control
4
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
This chapter describes the Call Control Capability Group.1 The capabilities in this
group are categorized by their functions: initiating, controlling, and terminating.
The adjunct uses these capabilities to set up (place), take control of, monitor, or
end a call on the switch.
Third Party Make CallThis initiating capability enables the adjunct to set
up a call on behalf of an on-PBX station.  The four
types of controlled calls supported by this
capability are as follows:
 Switch-classified
 User-classified (with or without priority)
 Direct-agent
 Supervisor-assist
 Third Party
 Take Control
This initiating capability enables the adjunct to
take control of a call that is already in progress to
perform additional call control functions when
needed.
 Third Party
 Selective HoldThis controlling capability enables the adjunct to
place the controlled call on hold at the specified
station.
aaaaaaaaaaaaaaaaaaa
1. Capability groups are analogous to the Application Service Elements (ASEs) described in the 
AT&T
Adjunct/Switch Application Interface (ASAI) Specification.
Issue 4  September 1995  4-1