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 51

Common Capabilities
Issue 6  June 1997
2-15
Non-Call Related Event Reports
Logout Event Report
The ECS sends the Logout Event Report on a Domain (Split) Control Association.
The ECS sends a FACility message with an invoke FIE containing:
Operation Value = Event Report 
a logout event (Specific Event IE) 
the split (Domain IE), 
the agent’s physical extension
4 (Domain IE), 
[the agent’s logical extension4] (Domain IE), and
[reason code5] (Domain IE).
For coding, see ‘‘Logout Event Report — Domain (ACD...

Page 52

Messaging Sequences and ASAI
2-16Issue 6  June 1997 
Third Party Control Associations
The ECS provides three types of Third Party control associations:
1. Call Control, which monitors and controls all parties on a specified call
2. Third Party Domain (Station) Control, which monitors all calls at a specific 
station and allows control of the station only
3. Third Party Domain (ACD Split) Control, which monitors logout events for 
all agents in a given split
These control capability groups encompass call...

Page 53

Call Control Association
Issue 6  June 1997
2-17
These procedures provide descriptions of the messaging procedures.
Call Control Association
A Call Control association allows an adjunct to control all the endpoints on a call 
using those Call Control capabilities shown in Table 2-2. Call control includes: 
establishing a call, taking control of an existing call, controlling a call, and the call 
feedback (event reports) that the ECS provides about a controlled call.
Initiating a Call Control Association...

Page 54

Messaging Sequences and ASAI
2-18Issue 6  June 1997 
The ECS terminates a Call Control association in two ways:
1. If the call terminates and the ECS frees call-associated resources, then the 
ECS invokes the Call Ended capability. For coding, see ‘‘Third Party Call 
Ended — Association Terminates’’ on page 5-66 of Chapter 5, “Byte Level 
Messages.”
2. An internal ECS audit detects that ECS resources are allocated for Call 
Control of a call that no longer exists. If the ECS detects that such an...

Page 55

Call Control Association
Issue 6  June 1997
2-19
destination address (Called Party IE), 
[Service Circuit = call classifier] (Service Circuit IE), 
[number of rings before destination “no-answer” classification] 
(Call options IE), 
[alerting order] (Call options IE), 
[priority] (Call options IE), 
[supervisor assist flag] (Call options IE), 
[trunk access code or ARS/AAR digits] (Domain IE), 
[trunk access code] (Domain IE), 
[direct agent call flag] (Call Options IE), 
[answer machine detection] (Call...

Page 56

Messaging Sequences and ASAI
2-20Issue 6  June 1997 
Third Party Take Control —
Initiating Procedure
The adjunct uses this capability to take control of a call for future Call Control 
operations. The adjunct must have learned about the call, which could have been 
initiated manually, from an event report or query. The event reports and certain 
query responses include a call identifier that the adjunct may later use as a 
parameter in a Third Party Take Control request to create a new Call Control...

Page 57

Call Control Association
Issue 6  June 1997
2-21
Third Party Relinquish Control — 
Terminating Procedure
Third Party Relinquish Control terminates the association but does not disconnect 
the call. The association is terminated and the ECS stops sending the adjunct call 
feedback for the call. The ECS denies a relinquish control request for a 
switch-classified call in the process of being classified.
To relinquish control, the following messaging takes place:
1. The Adjunct sends a FACility message...

Page 58

Messaging Sequences and ASAI
2-22Issue 6  June 1997 
Domain (Station) Control Procedure
The Domain (Station) Control allows an adjunct to:
1. Monitor call-related events for all calls present at a specific station 
extension
2. Perform call control activity for that station extension (and only that station 
extension)
3. Initiate calls outbound from the station extension (and only that station 
extension)
The adjunct uses the Domain (Station) Control Request capability to initiate the 
association. While...

Page 59

Domain (Station) Control Procedure
Issue 6  June 1997
2-23
2. If the ECS accepts the Domain Control request, the contents of the 
acknowledgement depend on whether the domain control association is for 
a station or split:
nStation control acknowledgement:
a FACility message containing a return result FIE with:
the invoke-id in the control request, 
Operation Value = Third Party Domain (Station) Control, and
parameters containing a list of: 
[call_ids (Call Identifier IE)], 
[party_id of the principal’s...

Page 60

Messaging Sequences and ASAI
2-24Issue 6  June 1997 
Operation Value = Domain Control Ended, and 
a cause (Cause IE).
For coding, see ‘‘switch Ends Domain (Station) Control Association’’ on page 5-94 
of Chapter 5, “Byte Level Messages.”
Auto Dial Procedure
The adjunct can use the Auto Dial procedure over an existing Domain (Station) 
Control association to begin an outbound call for the controlled extension. The 
ECS reports event reports for the call within the existing Domain (Station) Control...
Start reading Lucent Technologies DEFINITY Enterprise Communications Server Release 5, CallVisor, ASAI Protocol Reference Instructions Manual

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

All Lucent Technologies manuals