Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies DEFINITY Enterprise Communications Server Release 5, CallVisor, ASAI Protocol Reference Instructions Manual
Lucent Technologies DEFINITY Enterprise Communications Server Release 5, CallVisor, ASAI Protocol Reference Instructions Manual
Here you can view all the pages of manual Lucent Technologies DEFINITY Enterprise Communications Server Release 5, CallVisor, ASAI Protocol Reference Instructions Manual. The Lucent Technologies manuals for Communications System are available online for free. You can easily download all the documents as PDF.
Page 41
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...
Page 42
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...
Page 43
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...
Page 44
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...
Page 45
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...
Page 46
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...
Page 47
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...
Page 48
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...
Page 49
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...
Page 50
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...