Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual
Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual
Have a look at the manual Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
![Page 137
ASAI Library Functions
Issue 3 May 1998
4-15
Figure 4-9. Sample Code — Testing the Event Notification Capabilities
1 /*
2 * :set tabstop=4 shiftwidth=4
3 *
4 * usage: entest acd|vec []
5 * entest signal01 acd 9999
6 * # receive reports from acd domain
7 * entest signal01 vec 9999 10
8 * # receive 10 reports from vector domain
9 */
10
11 #include
12 #include
13 #include
14...](http://img.usermanuals.tech/thumb/3002/85233/w64_definity-ecs-r6-callvisor-pc-asai-installation-and-reference_d-136.png "Page 137
ASAI Library Functions
Issue 3 May 1998
4-15
Figure 4-9. Sample Code — Testing the Event Notification Capabilities
1 /*
2 * :set tabstop=4 shiftwidth=4
3 *
4 * usage: entest acd|vec []
5 * entest signal01 acd 9999
6 * # receive reports from acd domain
7 * entest signal01 vec 9999 10
8 * # receive 10 reports from vector domain
9 */
10
11 #include
12 #include
13 #include
14...")
![Page 138
ASAI Library Functions
4-16Issue 3 May 1998
Figure 4-9. Sample Code — Testing the Event Notification Capabilities — Continued
46 en.cv_info.domain_ext = argv[3];
47 }
48 else
49 {
50 goto usage;
51 }
52 if ((fd = asai_open(/dev/asai/asai, 0)) < 0)
53 {
54 asai_errval(asai_open(dev/asai/asai) failed:);
55 exit(-asai_errno);
56 }
57 if (asai_set_env(fd, C_NODE_ID, argv[1]) < 0)
58 {
59...](http://img.usermanuals.tech/thumb/3002/85233/w64_definity-ecs-r6-callvisor-pc-asai-installation-and-reference_d-137.png "Page 138
ASAI Library Functions
4-16Issue 3 May 1998
Figure 4-9. Sample Code — Testing the Event Notification Capabilities — Continued
46 en.cv_info.domain_ext = argv[3];
47 }
48 else
49 {
50 goto usage;
51 }
52 if ((fd = asai_open(/dev/asai/asai, 0)) < 0)
53 {
54 asai_errval(asai_open(dev/asai/asai) failed:);
55 exit(-asai_errno);
56 }
57 if (asai_set_env(fd, C_NODE_ID, argv[1]) < 0)
58 {
59...")
![Page 139
ASAI Library Functions
Issue 3 May 1998
4-17
Figure 4-9. Sample Code — Testing the Event Notification Capabilities — Continued
91 }
92 else if (rsp.asai_common.capability==C_EN_CONF &&
93 rsp.asai_common.primitive_type==C_NEG_ACK)
94 {
95 printf( cause:%s
, \
96 causes[rsp.en_rsp.en_nak.cause_value]);
97 exit(2);
98 }
99 printf(
);
100
101 for (;cnt--;)
102 {
103 if (asai_rcv(fd, &rsp,...](http://img.usermanuals.tech/thumb/3002/85233/w64_definity-ecs-r6-callvisor-pc-asai-installation-and-reference_d-138.png "Page 139
ASAI Library Functions
Issue 3 May 1998
4-17
Figure 4-9. Sample Code — Testing the Event Notification Capabilities — Continued
91 }
92 else if (rsp.asai_common.capability==C_EN_CONF &&
93 rsp.asai_common.primitive_type==C_NEG_ACK)
94 {
95 printf( cause:%s
, \
96 causes[rsp.en_rsp.en_nak.cause_value]);
97 exit(2);
98 }
99 printf(
);
100
101 for (;cnt--;)
102 {
103 if (asai_rcv(fd, &rsp,...")
![Page 140
ASAI Library Functions
4-18Issue 3 May 1998
Figure 4-9. Sample Code — Testing the Event Notification Capabilities — Continued
136 break;
137 default:
138 printf( Unexpected capability \
139 causes abort!
);
140 exit(4);
141 }
142 }
143
144 en.en_common.asai_common.capability = C_EN_CAN;
145
146 printf(Sent: C_EN_CAN (C_REQUEST) on clid 0
);
147 if (asai_send(fd, &en,...](http://img.usermanuals.tech/thumb/3002/85233/w64_definity-ecs-r6-callvisor-pc-asai-installation-and-reference_d-139.png "Page 140
ASAI Library Functions
4-18Issue 3 May 1998
Figure 4-9. Sample Code — Testing the Event Notification Capabilities — Continued
136 break;
137 default:
138 printf( Unexpected capability \
139 causes abort!
);
140 exit(4);
141 }
142 }
143
144 en.en_common.asai_common.capability = C_EN_CAN;
145
146 printf(Sent: C_EN_CAN (C_REQUEST) on clid 0
);
147 if (asai_send(fd, &en,...")
Issue 3 May 19985-1 5 ASAI Capabilities This chapter contains all the ASAI application service elements and provides the details of all the capabilities that comprise each ASE. These application service elements are: nEvent Notification and Event Reports nThird Party Call Control Capabilities nSet Value nValue Query nRequest Feature nAdjunct Routing nMaintenance nAbort Capabilities
ASAI Capabilities 5-2Issue 3 May 1998 Event Notification The Event Notification capability group provides capabilities for a client to obtain information related to specific events that are monitored by the server. For example, an application can monitor the progress of calls arriving at an ACD split. Based on the event information received, the client can take various actions by invoking other ASEs, such as Third Party Take Control.The Event Notification ASE provides capabilities for the following: nInitiating event notification nEvent Notification Request nTerminating event notification nEvent Notification Cancel nEvent Notification End nEvent Notification Stop Call Notification nEvent Reports In addition, the two Abort capabilities can be considered part of the Event Notification ASE; Abort capabilities are described in ‘‘Abort Capabilities’’ on page 5-51. The server only accepts requests for event reports on domains that are directly associated with it. The following domains are supported: nACD split nVDN nTA C
ASAI Capabilities Issue 3 May 1998 5-3 Event Notification Request Description The Event Notification Request capability allows the client to request the server to begin reporting certain events. After the server acknowledges the request, the client receives event reports each time an event occurs. The client does not have to be a party to any of these events. A client can have several instances of Event Notification active at the same time and a single event can be reported for more than one ASE instance. In such cases, the client receives separate event reports. The client invokes this capability by issuing a C_EN_REQ to which the server responds with a C_EN_CONF. If the acknowledgement is positive, the client starts to receive event reports and continues to receive them until one of the following terminates the association: nThe client sends Event Notification Cancel nThe server sends Event Notification End nThe client receives an Abort capability Request/Indication Parameters Domain — The domain over which notifications are requested. Domain consists of: nDomain Type — ACD split, VDN, or TAC nDomain Value — The specific domain, within domain type, that is to be the subject of reports Notes The client can request notification only for domains directly associated with the server. Only one domain can be included per request.
ASAI Capabilities 5-4Issue 3 May 1998 Event Notification End Description The server sends the Event Notification End capability if it can no longer provide the requested service. The client receives no further event reports on the specified association identifier. The ASE is terminated. The server invokes this capability by sending a C_EN_END. Notes Notification must have been initiated through the Event Notification Request capability.
ASAI Capabilities Issue 3 May 1998 5-5 Event Notification Cancel Description The Event Notification Cancel capability allows the client to request cancellation of event reports for a specified domain. The client invokes this capability by sending a C_EN_CAN, to which the server responds with a C_EN_CAN_CONF. If the confirmation is positive, the ASE instance is terminated. If the confirmation is negative, the client continues to receive event reports and can reissue the Event Notification Cancel capability. Notes Event notification must have been initiated by an Event Notification Request.
ASAI Capabilities 5-6Issue 3 May 1998 Event Notification Stop Call Notification Description The Event Notification Stop Call Notification capability allows the client to request the server to stop sending event reports for a specified call. The server continues to send event reports for other calls with the specified association identifier. The client invokes this capability by sending a C_EN_SCN to which the server responds with a C_EN_SCN_CONF. If the server is able to terminate event reporting for the specified call, the client no longer receives the associated event reports. If the server cannot terminate event reporting for the call, or if the call does not exist, the server issues a negative acknowledgement, and the client continues to receive any event reports associated with the call (if it exists). Request/Indication Parameter nCall Identifier — The call for which no further event reports are desired. Notes Only one call identifier can be specified in each Stop Call Notification request.
ASAI Capabilities Issue 3 May 1998 5-7 Event Report Description The Event Report capability is used by the server to report call-related events. An event applies to one of the following: nA party on a call nMultiple parties on a call nA call independent of parties nA particular ECS entity (ACD agents) independent of any call The list below shows which events can apply to each of the groups shown. Events are related to states, more specifically to state transitions. A state is associated with each call and with each party to that call. A party to several calls can be in different states on each call and different parties to the same call can be in different states. The states are: nnull nseized nalerting nactive nheld Event reports are issued for state transitions; that is when a party or a call for which reports have been requested moves from one state to another.Party Multi. Parties Call Sw. Entity AlertingCall conf’d Call ended Logout Answered Call transf’d Call offered Login Busy to domain Connected Queued Charge Cut-through Reorder/Denial Drop Call initiated Hold Call redirected Reconnected Trunk SeizedCall Originated
ASAI Capabilities 5-8Issue 3 May 1998 Table 5-1. Valid Event Item Combinations Event Items Reported Calling Party No.Called Party No . Connected Party No.Call IdNew Call IdParty IdParty_Id List Alerting I I I A A Answered I I A A Busy/Unavailable I A I Connected I I A A Cut-Through/Progress A A Disconnect/Drop I A I Hold I A A Reconnected I A A Trunk Seized I A A Call Conferenced I I I A I A Call Transferred I I I A I A Call Redirected A Call Ended A Call Offered to Domain I I A Call Initiated A I Call Originated A A A A Queued I A Reorder/Denial I I Logout Login Key: A: item always provided in event report. I: item may be provided in event report.
ASAI Capabilities Issue 3 May 1998 5-9 Table 5-1. Valid Event-Item Combinations — Continued Event Items Reported Calls In Queue CauseUser Entered InfoLookahead Interflow Info DomainRedirection Number AlertingII Answered I Busy/Unavailable I ConnectedI Cut-Through/Progress Disconnect/Drop I Hold Reconnected Trunk Seized Call Conferenced Call Transferred Call RedirectedII Call Ended A Call Offered to Domain I I I I Call Initiated Call Originated Queued I Reorder/Denial I Logout Login Key: A: item always provided in event report. I: item may be provided in event report.
ASAI Capabilities 5-10Issue 3 May 1998 Table 5-1. Valid Event-Item Combinations — Continued Event Items Reported Extension Extension ListTrunk Group NumberWo r k FlowProgress Indicator UUI oli ucid Alerting I I I I Answered Busy/Unavailable Alerting Answered Busy/Unavailable Charge A A ConnectedII Cut-Through/Progress I Disconnect/Drop Hold Reconnected Trunk Seized I Call Conferenced I I Call Transferred I I Call Redirected Call Ended Call Offered to Domain I I I I Call InitiatedI Queued Reorder/Denial Logout A Key: A: item always provided in event report. I: item may be provided in event report.