Lucent Technologies DEFINITY Enterprise Communications Server Release 5, CallVisor, ASAI Protocol Reference Instructions Manual

							Common Capabilities
Issue 6  June 1997
2-5
Call-Related Event Reports
The event reports in this section show that further call control is possible within 
the Call Control and Domain (Station) Control associations. Also, the ECS may 
send additional event reports.
1. Charging Event Reports are only sent on the Notification association associated with all
trunk groups. They are not sent on Split or VDN Notification associations.
Table 2-1. Use of Event Reports in Associations
Event ReportDomain 
(Station)
Control Call Control NotificationDomain
 (Split)
Control
Alerting yes yes yes no
Answered yes yes no no
Busy/Unavailable yes yes yes no 
Call Conferenced yes yes yes no
Call Ended (FACility) 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
Charging no no yes
1no
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
Reconnected yes yes yes no
Reorder/Denial yes yes yes no
Trunk Seized yes yes yes no 
						

							Messaging Sequences and ASAI
2-6Issue 6  June 1997 
Alerting Event Report
The ECS sends the adjunct a FACility message. Note that within a Domain 
(Station) Control Association, this event is sent for both incoming calls alerting at 
the controlled extension and also for far-end alerting for calls originating at the 
controlled extension.
The message contains an invoke FIE with:
Operation Value = Event Report, 
an “alerting” event (Specific Event IE), 
a party_id (Party ID IE), 
the calling number (Calling Number IE or Trunk Identifier IE), 
the called number (Called Number IE), 
[the number that is alerting if that party is local (Connected Number IE)], 
[the reason for redirection] (Cause IE), 
[the split that has distributed the call to an alerting agent, if any (Domain IE)], 
a call_id (Call Identity IE), 
[a cause value (Cause IE)],
[User-to-User Information] (User-User IE), and
[originating line information] (Originating Line IE).
The Alerting Event Report contains one of the following values for the Calling 
Number IE or Trunk identifier IE:
(For incoming calls:)
nAn on-PBX extension passed in the Calling Number IE 
nAn off-PBX CPN/BN passed in the Calling Number IE 
nThe group number of the incoming trunk passed in the Trunk Identifier IE 
(For outgoing calls:)
nAn on-PBX extension originating the call
NOTE:
A Switch-Classified call (destination alerting first option) appears as an 
incoming call to the ACD agent. Thus, the Alerting Event Report for the 
agent and the Call Offered to Domain Event Report will contain the external 
number as the “caller” and the split or VDN extension as the “called” 
number. 
For coding, see ‘‘Alerting Event Report’’ on page 5-3 of Chapter 5, “Byte Level 
Messages.”
Answered Event Report
The ECS sends this event report when either the destination answers or the call 
classifier detects SIT administrated for answer treatment. The ECS sends the 
adjunct a FACility message with an invoke FIE containing: 
						

							Common Capabilities
Issue 6  June 1997
2-7
Operation Value = Event Report, 
an “answer” event (Specific Event IE), 
a call_id (Call Identity IE), 
[the answering number] (Connected Number IE), 
the dialed number (Called Number IE), 
a party_id (Party ID IE), and 
the tone the classifier detected (Cause IE).
For coding, see ‘‘Answered Event Report’’ on page 5-6 of Chapter 5, “Byte Level 
Messages.”
Call Conferenced Event Report
When a local party on a monitored (or controlled) call uses a voice instrument 
(set) to conference another party onto the call, or when another association 
conferences two calls for a party, the ECS sends the Call Conferenced Event 
Report to the monitoring (controlling) association(s).
The ECS sends the adjunct a FACility message with an invoke FIE containing:
Operation Value = Event Report, 
a “conferenced” event (Specific Event IE), 
the call_id for the resulting conference call after
the conference operation (Call Identity IE)
1,
the call_id of the other call before the conference operation 
(Call Identity IE), 
the conferencing party’s number (Calling Number IE), 
the conferenced party’s number (Called Number IE), 
a list of up to six old party identifiers for the parties on the 
call (Old Party ID IE) 
a list of up to six party identifiers for the parties on the   
call (Party ID IE), and 
a list of up to six extensions of the parties on the call   
(Connected Number IE). 
For coding, see ‘‘Call Conferenced Event Report’’ on page 5-9 of Chapter 5, “Byte 
Level Messages.”
1. This is always one of the call_ids of the two calls being merged. 
						

							Messaging Sequences and ASAI
2-8Issue 6  June 1997 
Call Initiated Event Report
The ECS sends the Call Initiated Event Report when a domain-controlled 
extension goes off-hook and receives dial tone.
This event is only sent within Domain (Station) Control associations.
The ECS sends the adjunct a FACility message with an invoke FIE containing:
Operation Value = Event Report, 
a call_id (Call Identity IE), 
a party_id of the extension initiating the call (Party ID IE), and 
a “call initiated” event (Specific Event).
For coding, see ‘‘Call Initiated Event Report’’ on page 5-11 of Chapter 5, “Byte 
Level Messages.”
Call Offered to Domain Event Report
The ECS sends a FACility message with an invoke FIE containing:
Operation Value = Event Report, 
call offered event (Specific Event IE), 
a call identifier that refers to this call   
in any ASAI association (Call Identity IE), 
the calling number (Calling Party Number IE or Trunk Identification IE)
2, 
the called number (Called Party Number IE), 
[Split or VDN number] (Domain IE), 
[Lookahead Interflow information] (Lookahead Interflow IE),
3 
[digits collected by the ECS call prompting unit] (User Code IE), 
[User-to-User Information] (User-User IE), 
[Flexible Billing] (Feature IE), and
[originating line information] (Originating Line IE). 
For coding, see ‘‘Call Offered to Domain Event Report’’ on page 5-12 of Chapter 
5, “Byte Level Messages.”
NOTE:
A Switch-Classified call (destination alerting first option) appears as an 
incoming call to the ACD agent. Thus, the Alerting Event Report for the 
agent and the Call Offered to Domain Event Report will contain the external 
number as the “caller” and the split or VDN extension as the “called” 
number.
2. The ECS supplies the data that the network has passed to the ECS with the incoming call: 
CPN, or BN, but not both. The Calling Party IE is present when the calling number is 
known; it is mutually exclusive with the Trunk Identification IE, which is present when the 
number is not known. This is described in the Alerting Event Report section. 
3. The ECS passes incoming Lookahead Interflow IE from incoming PRI calls with the first 
call offered event report for the incoming call. 
						

							Common Capabilities
Issue 6  June 1997
2-9
Call Originated Event Report
The ECS sends the adjunct a FACility message with an invoke FIE containing:
Operation Value=Event Report, 
a “call originated” event (Specific Event IE), 
a call_id (Call Identity IE), 
a party_id (Party Identifier IE),
the connected number (Connected number IE) 
the calling number (Calling number IE), and 
a dialed number (Called Number IE), and 
[User-to-User Information] (User-User IE).
For coding, see ‘‘Call Originated Event Report’’ on page 5-15 of Chapter 5, “Byte 
Level Messages.”
Call Redirected Event Report
The ECS sends this event report when a call leaves a monitored Automatic Call 
Distribution (ACD) split, monitored Vector Directory Number (VDN), or controlled 
extension. The ECS sends the adjunct a FACility message with an invoke FIE 
containing:
Operation Value = Event Report, 
a “call redirected” event (Specific Event IE), and 
the call_id of the call (Call Identity IE).
For coding, see ‘‘Call Redirected Event Report’’ on page 5-17 of Chapter 5, “Byte 
Level Messages.”
Call Transferred Event Report
When a local party on an adjunct-monitored (or adjunct-controlled) call uses a 
voice instrument to transfer the call to another party, or when another association 
transfers a call on behalf of a party, the ECS sends the Call Transferred Event 
Report to the monitoring (controlling) adjunct(s).
The ECS sends the adjunct a FACility message with an invoke FIE containing:
Operation Value = Event Report, 
a “transfer” event (Specific Event IE), 
the call_id of the resulting transferred call (Call Identity IE), 
the other call_id before the transfer (Call Identity IE), 
the transferring party’s number (Calling Number IE), 
the transferred party’s number (Called Number IE), 
a list of up to six old party identifiers for the parties on the     
call (Old Party ID IE), 
a list of up to six party identifiers for the parties on the   
call (Party ID IE), and 
						

							Messaging Sequences and ASAI
2-10Issue 6  June 1997 
a list of up to six extensions of the parties on the   
call (Connected Number IE).
For coding, see ‘‘Call Transferred Event Report’’ on page 5-18 of Chapter 5, “Byte 
Level Messages.”
Charging Event Report
The ECS sends this event report when an ISDN-PRI trunk sends charge advice 
for an outbound call placed on that trunk. This event report is only sent over the 
Notification association for the domain of all trunk groups.
The ECS sends the adjunct a FACility message with an invoke FIE containing:
Operation Value = Event Report, 
a “charging” event (Specific Event IE),
a call_id (Call Identity IE), 
the called number (Called Number IE),
the charging number (Calling Number IE),
the trunk group and member (Trunk ID IE),
type of charge (Data Item IE),
charge amount (Data Item IE)
[party ID of trunk] (Party ID IE),
[reason for error] (Cause IE).
For coding, see ‘‘Charging Event Report’’ on page 5-20 of Chapter 5, “Byte Level 
Messages.”
Connected Event Report
The ECS sends the adjunct a FACility message with an invoke FIE containing:
Operation Value = Event Report, 
a “connected” event (Specific Event IE), 
a party_id (Party ID IE), 
a call_id (Call Identity IE), 
the calling number (Calling Number IE or Trunk ID IE), 
the dialed number (Called Number IE), 
cause giving type of answer supervision (Cause IE), and 
[the number that actually answered the call if that party is local]   
(Connected Number IE)
[originating line information] (Originating Line IE).
For coding, see ‘‘Connected Event Report’’ on page 5-22 of Chapter 5, “Byte 
Level Messages.”
NOTE:
A Switch-Classified call (destination alerting first option) appears as an 
incoming call to the ACD agent. Thus, the Alerting and Connected Event 
Reports for the agent and the Call Offered to Domain Event Report will  
						

							Common Capabilities
Issue 6  June 1997
2-11
contain the external number as the “caller” and the split or VDN extension as 
the “called” number.
Cut-Through Event Report
The ECS maps a Primary Rate Interface (PRI) PROGress message to an ASAI 
Cut-Through Event Report for nonswitch-classified calls. A PRI network may send 
the ECS a PROGress message for a variety of reasons contained in a Progress 
Indicator (within the PROGress message). The ECS forwards the Progress 
Indicator to the adjunct in the cut-through event.
The ECS sends the adjunct a FACility message with an invoke FIE containing:
Operation Value = Event Report, 
a “cut through” event (Specific Event IE), 
a party_id (Party ID IE), 
the progress information from the ISDN network    
(Progress Indicator IE), and 
a call_id (Call Identity IE).
For coding, see ‘‘Cut-Through Event Report’’ on page 5-24 of Chapter 5, “Byte 
Level Messages.”
Disconnect/Drop Event Report
The ECS sends the Disconnect/Drop Event Report when a party drops from a 
multiparty call. The ECS does not send this event report for the last party on the 
call since doing so would be redundant with sending Call Ended. The ECS does 
send it for the last party dropped on domain-controlled associations.
The ECS sends the adjunct a FACility message with an invoke FIE containing:
Operation Value = Event Report, 
a “party dropped from call” event (Specific Event IE), 
a party_id (Party ID IE), 
[the number of the party that dropped if local] (Connected Number IE), 
a call_id (Call Identity IE), 
[the tone a classifier detected if the classifier reports a drop] (Cause IE), and
[User-to-User Information (User-User IE)].
For coding, see ‘‘Disconnect/Drop Event Report’’ on page 5-25 of Chapter 5, 
“Byte Level Messages.”
Entered Digits Event Report
The ECS sends an Entered Digits Event Report to the adjunct when the ECS has 
collected the number of digits previously requested. The ECS sends the adjunct a 
FACility message with an invoke FIE containing:
Operation Value = Event Report, 
an “entered digits” event (Specific Event IE),  
						

							Messaging Sequences and ASAI
2-12Issue 6  June 1997 
the call_id for the call (Call Identity IE), and 
the digit(s) entered (User Entered Code IE).
For coding, see ‘‘Entered Digits Event Report’’ on page 5-27 of Chapter 5, “Byte 
Level Messages.”
Hold Event Report
The ECS sends the Hold Event Report when a local party on a monitored call puts 
the call on hold. Within a Domain (Station) Control association this means that the 
ECS sends the Hold Event Report for not only the controlled extension, but for all 
the local endpoints on calls that are present at the controlled extension.
The ECS sends the adjunct a FACility message with the invoke FIE containing:
Operation Value = Event Report, 
a “party held call” event (Specific Event IE), 
a party_id (Party ID IE), 
the extension number of the party that held (Connected Number IE), and 
a call_id (Call Identity IE).
For coding, see ‘‘Hold Event Report’’ on page 5-28 of Chapter 5, “Byte Level 
Messages.”
Queued Event Report
The ECS sends the adjunct a FACility message with an invoke FIE containing:
Operation Value = Event Report, 
a “call queued” event (Specific Event IE), 
a split identifier (Domain IE), 
the number of calls now in the queue (Counter IE), 
the dialed number (Called Party Number IE), and 
a call_id (Call Identity IE).
For coding, see ‘‘Queued Event Report’’ on page 5-33 of Chapter 5, “Byte Level 
Messages.”
Reconnected Event Report
The ECS sends the Reconnect Event Report when a local party on a monitored 
call reconnects to a held call. Within a Domain (Station) Control association this 
means that the ECS sends the Reconnected Event Report for not only the 
controlled extension, but for all the local endpoints on calls that are present at the 
controlled extension.The ECS sends the adjunct a FACility message with an 
invoke FIE containing:
Operation Value = Event Report, 
a “party reconnected to call” event (Specific Event IE), 
a party_id (Party ID IE), 
the extension number of the party that reconnected    
						

							Common Capabilities
Issue 6  June 1997
2-13
(Connected Number IE), and 
a call_id (Call Identity IE).
For coding, see ‘‘Reconnected Event Report’’ on page 5-35 of Chapter 5, “Byte 
Level Messages.”
Trunk Seized Event Report
The ECS sends a Trunk Seized Event Report to the adjunct when a 
nonswitch-classified call leaves the ECS on a non-PRI facility. The application 
may only receive Connected and Dropped Event Reports for the far-end party, 
following the Trunk Seized Event Report. The ECS sends the Trunk Seized Event 
Report, for example, when the destination for a Third Party Make Call capability is 
off the ECS, the call uses a non-PRI trunk, and the call is manually classified; or 
when an incoming call is transferred or forwarded to a remote endpoint over a 
non-PRI facility.
The ECS sends the adjunct a FACility message with an invoke FIE containing:
Operation Value = Event Report, 
a “trunk seized” event (Specific Event IE), 
a party_id (Party ID IE), 
the dialed number (Called Number IE), and 
a call_id (Call Identity IE).
For coding, see ‘‘Trunk Seized Event Report’’ on page 5-37 of Chapter 5, “Byte 
Level Messages.”
Call-Related Event Reports When Ending
Adjunct Control
The ECS sends the event reports described in this section within Call Control 
associations, extension control associations, and notification associations.
When sent for Call control, these event reports imply that limited further adjunct 
call control is possible. Subsequent to “busy” and “reorder,” the adjunct can still 
send a Third Party Drop or a Third Party Clear call. “Busy” and “reorder” events do 
not terminate the extension control association.
Busy and Reorder Event Reports are followed by a Call Ended Event Report for 
call control and event notification associations when the ECS frees the resources 
associated with the call.
Busy/Unavailable Event Report
The ECS sends the adjunct a FACility message with an invoke FIE containing:
Operation Value = Event Report, 
a “busy” event (Specific Event IE), 
the call_id for the call (Call Identity IE),  
						

							Messaging Sequences and ASAI
2-14Issue 6  June 1997 
a cause (Cause IE), and 
the called number (Called Number IE).
For coding, see ‘‘Busy/Unavailable Event Report’’ on page 5-8 of Chapter 5, “Byte 
Level Messages.”
Reorder/Denial Event Report
The ECS sends the adjunct a FACility message with an invoke FIE containing:
Operation Value = Event Report, 
a “denial” event (Specific Event IE), 
the call_id for the call (Call Identity IE), 
the called number (Called Number IE), and 
a cause (cause IE).
For coding, see ‘‘Reorder/Denial Event Report’’ on page 5-36 of Chapter 5, “Byte 
Level Messages.”
Call Ended
The ECS sends the Call Ended Event Report when it frees the internal ECS 
resources associated with a controlled/monitored call (for example, the call has 
terminated). The ECS sends Call Ended in a RELease COMplete on a Call 
Control association so that the association is terminated. For coding, see ‘‘Third 
Party Call Ended — Association Terminates’’ on page 5-66 of Chapter 5, “Byte 
Level Messages.” 
The ECS sends the Call Ended operation in a FACility message for a notification 
association so that the association continues. For coding, see ‘‘Notification: Call 
Ended — Association Continues’’ on page 5-102 of Chapter 5, “Byte Level 
Messages.” The ECS sends the adjunct a RELease COMplete or FACility 
message with an invoke FIE containing:
Operation Value = Third Party Call Ended, 
the call_id of the call (Call Identity IE), and 
a cause (Cause IE).
The cause generally indicates that the call terminated normally, or that the call 
terminated as a result of a transfer operation.Example causes: classifier not available trunks not available
  split queue full encountered vector busy step
  split has no logged-in agents