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

							1. Initialization
Issue 6 June 1997
B-3
1. Initialization
This section presents a sample ASAI initialization procedure. The adjunct 
processor initializes the link and requests Event Notification for VDN 5678 and 
ACD split 3456. This sample initialization procedure is referred to by some of the 
scenarios presented in subsequent sections.
Messages Sent by
the Adjunct ProcessorMessages Sent by
the ECS Comments
REST (CRV=global,
Restart Indicator=all
interfaces)Restart ASAI Interface
REST ACK [CRV=global,
Restart Indicator=all
interfaces]ASAI Interface Restarted
REG[CRV=7F FIE(Invoke,
Inv_id=1
Heartbeat)]
RELCOMP[CRV=7f,FIE
(Return Result,
Inv_id=1)]
REG [CRV=98, FIE(Invoke,
Inv_id=1,
Event Notification Request
domain=VDN 5678)]Notification Request
for VDN 5678
FAC [CRV=98, FIE(Return
Result, Inv_id=1)]Notification Accepted
REG [CRV=102, FIE(Invoke, 
Inv_id=3,
Event Notification Request,
domain=ACD split 3456)]Notification Request
for ACD split 3456
FAC [CRV=102, FIE(Return
Result, Inv_id=3)]Notification Accepted 
						

							Message Scenarios
B-4Issue 6 June 1997 
2. Notification Associations
This section illustrates the Event Reports provided by calls entering different 
notification domains. Figure B-2 shows the Vector Directory Numbers (VDNs), 
vectors, ACD splits, and agent extensions used for the message scenarios 
presented in this section. VDNs 5678, 5690, and 7656 point to vectors A, B, and 
C, respectively. Only the most relevant vector commands (that is, Adjunct Routing 
and Queue to Main) are shown. ACD splits 3459 and 3460 are vector-controlled. 
ACD split 3456 is not vector-controlled. (In reality, this is not possible on the same 
ECS.) The ACD agents at extensions 4534 and 3567 are logged into ACD split 
3456. The ACD agent at extension 4566 is logged into ACD split 3460. There are 
no available agents for ACD split 3459.
VDN 5678 and ACD split 3456 are monitored by the adjunct processor as 
presented in the initialization scenario. VDN 7656 is monitored by another adjunct 
processor not shown in these scenarios. VDN 5690 is not monitored.
Figure B-2. Relationship Among VDNs, ACD Splits, and Stations
Trunks Trunks
DEFINITY ECS
ACD Split
x4534Agent
Extensions
3456 VDN 5678
Vector A
1. Collect Digits
x3567
ACD Split
3459
ACD Split
3460
x4566 VDN 5690
Vector B
1. Queue to Main
Split 3459
2. Queue to Main
VDN 7656Vector C
1.
2. Adjunct Routing
3. Wait 4 Seconds
4. Route to 0
Split 3460
3. Stop
2.
3.  
						

							2. Notification Associations
Issue 6 June 1997
B-5
External Call to VDN Routed to ACD Split
This scenario shows the call flow for an incoming ISDN PRI call to VDN 5678 that 
is routed via the Adjunct Routing vector command to ACD Split 3456 (Figure B-3). 
The agent at extension 4534 answers the call. 
Event Notification for VDN 5678 and ACD Split 3456 is active as presented in the 
initialization scenario. The ASAI messages generated by the Adjunct Routing 
vector command are shown also.
Figure B-3. Call Flow for Incoming Call to VDN Routed to ACD Split
DEFINITY ECS
Vector A
1. Collect Digits
2. Adjunct Routing
3. Wait 4 SecondsACD Split
3456 VDN 5678 Incoming Call
call_id=37
x4534
4. Route to 0Agent
Extension 
						

							Message Scenarios
B-6Issue 6 June 1997 
Messages Sent by the
Adjunct ProcessorMessages Sent by
the ECS Comments
FAC [CRV=98, FIE(Invoke,
Inv_id=2, Event Report,
call_id=37,
event=call offered,
calling number=2015666379, 
called number=9085765678, 
domain=VDN 5678)]Call Offered
to VDN 5678
REG [CRV=93, FIE(Invoke,
Inv_id=4, Route,
call_id=37,
calling number=2015666379, 
called number=9085765678,
user code=11569037,
domain=VDN 5678)]Route Request
FAC [CRV=93, FIE(Invoke,
Inv_id=7, Route Select,
called number=3456)]Route to
ACD Split 3456
REL COMP [CRV=93, FIE(Invoke,
Inv_id=6, Route End,
cause=normal)]Call Routed
FAC [CRV=98, FIE(Invoke,
Inv_id=8, Event Report,
call_id=37,
event=call redirected)]Notification for Call
Terminated over
VDN Association
FAC [CRV=102, FIE(Invoke,
Inv_id=10, Event Report,
call_id=37,
event=call offered,
calling number=2015666379,
called number=9085765678,
user code=11569037,
domain=ACD Split 3456)]Call Offered to
ACD Split 3456
FAC [CRV=102, FIE(Invoke,
Inv_id=12, Event Report,
call_id=37, event=queued,
called number=9085765678,
calls in queue=2,
domain=ACD Split 3456)]Queued Event Report
(Queued in ACD
Split 3456)
(Continued on next page) 
						

							2. Notification Associations
Issue 6 June 1997
B-7
FAC [CRV=102, FIE(Invoke,
Inv_id=14, Event Report,
call_id=37, party_id=2,
event=alerting,
calling number=2015666379, 
called number=9085765678,
connected number=4534,
domain=ACD Split 3456)]Alerting Event Report
(Call Delivered to
Agent 4534)
FAC [CRV=102, FIE(Invoke,
Inv_id=16, Event Report,
call_id=37, party_id=2,
event=connected,
calling number=2015666379,
called number=9085765678,
connected number=4534)]Connected Event Report
(Call Connected
to Agent 4534)
FAC [CRV=102, FIE(Invoke,
Inv_id=18, Event Report,
call_id=37, party_id=2,
event=drop,
connected number=4534,
cause=normal clearing)]Drop Event Report
(Agent disconnects)
FAC [CRV=102, FIE(Invoke,
Inv_id=20, Call Ended, 
call_id=37,
cause=normal clearing)]Call Terminates
Messages Sent by the
Adjunct ProcessorMessages Sent by
the ECS Comments 
						

							Message Scenarios
B-8Issue 6 June 1997 
External Call to Monitored VDN Routed to
Non-Monitored VDN
This scenario shows the call flow for an incoming ISDN PRI call to VDN 5678 that 
is routed via the Adjunct Routing vector command to VDN 5690 (Figure B-4). The 
call queues to two ACD splits, ACD split 3459 and 3460. The agent at 
extension 4566 and logged into ACD split 3460 answers the call. 
Event Notification for VDN 5678 is active as presented in the initialization 
scenario. The ASAI messages generated by the Adjunct Routing vector command 
are shown also.
Figure B-4. Call Flow for Incoming Call to VDN Delivered to Agent
DEFINITY ECSAgent
Extension
VDN 5678
Vector A
1. Collect Digits
ACD Split
3459
ACD Split
3460
x4566 VDN 5690
Vector B
1. Queue to Main
Split 3459
2. Queue to Main
2. Adjunct Routing
3. Wait 4 Seconds
4. Route to 0
Split 3460
3. Stop
Incoming Call
call_id=58 
						

							2. Notification Associations
Issue 6 June 1997
B-9
Messages Sent by the
Adjunct ProcessorMessages Sent by
the ECS Comments
FAC [CRV=98,FIE(Invoke,
Inv_id=2, Event Report,
call_id=58
event=call offered,
calling number=2015663569,
called number=9085765678
domain=VDN 5678)]Call Offered to VDN Event 
Report
REG [CRV=93, FIE(Invoke,
Inv_id=4, Route,
call_id=58,
calling number=2015663569, 
called number=9085765678,
user code=34569058,
domain=VDN 5678)]Route Request
FAC [CRV=93, FIE(Invoke,
Inv_id=3, Route Select,
called number=5690)]Route to VDN 5690
REL COMP [CRV=93, FIE(Invoke,
Inv_id=6, Route End,
cause=normal)]Call Routed
FAC [CRV=98, FIE(Invoke,
Inv_id=8, Event Report,
call_id=58, event=queued,
called number=9085765678,
calls in queue=2,
domain=ACD Split 3459)]Queued Event Report 
for ACD 3459
FAC [CRV=98, FIE(Invoke,
Inv_id=10, Event Report,
call_id=58, event=queued,
called number=9085765678,
calls in queue=3,
domain=ACD Split 3460)]Queued Event Report 
for ACD 3460
(Continued on next page) 
						

							Message Scenarios
B-10Issue 6 June 1997 
Messages Sent by the
Adjunct ProcessorMessages Sent by
the ECS Comments
FAC [CRV=98, FIE(Invoke,
Inv_id=12, Event Report,
call_id=58, party_id=2,
event=alerting,
calling number=2015663569, 
called number=9085765678,
connected number=4566,
domain= ACD Split 3460)]Alerting Event Report
(Call Delivered to
Agent 4566)
FAC [CRV=98, FIE(Invoke,
Inv_id=14, Event Report,
call_id=58, party_id=2,
event=connected,
calling number=2015663569,
called number=9085765678,
connected number=4566)]Connected Event Report
(Call Connected to
Agent)
FAC [CRV=98, FIE(Invoke,
Inv_id=16, Event Report,
call_id=58, party_id=2,
event=drop,
connected number=4566,
cause=normal clearing)]Drop Event Report
(Agent Disconnects)
FAC [CRV=98, FIE (Invoke,
Inv_id=18, Call Ended,
call_id=58,
cause=normal clearing)]Call Terminates 
						

							2. Notification Associations
Issue 6 June 1997
B-11
External Call to VDN Routed to Monitored VDN
This scenario shows the call flow for an incoming ISDN PRI call to VDN 5678 that 
is routed via the Adjunct Routing vector command to VDN 7656 (Figure B-5). 
VDN 7656 is monitored by a different adjunct not shown in these scenarios. Event 
Notification from VDN 5678 is active as presented in the initialization scenario. 
The ASAI messages generated by the Adjunct Routing vector command are 
shown also.
Figure B-5. Call Flow for Incoming Call to VDN Routed to Another VDN
DEFINITY ECS
VDN 5678
Vector A
1. Collect Digits
VDN 7656Vector C
1.
2. Adjunct Routing
3. Wait 4 Seconds
4. Route to 0 Incoming Call
call_id=39
2.
3.  
						

							Message Scenarios
B-12Issue 6 June 1997 
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the ECS Comments
FAC [CRV=98, FIE(Invoke,
Inv_id=2, Event Report,
call_id=39,
event=call offered,
calling number=6157856399, 
called number=9089575678,
domain=VDN 5678)]Call Offered 
to VDN 5678
REG [CRV=93, FIE(Invoke,
Inv_id=2, Route,
call_id=39,
calling number=2015766399, 
called number=2015765678,
user code=00569039,
domain=VDN 5678)]Route Request
FAC [CRV=93, FIE(Invoke, 
Inv_id=3, Route Select,
called number=7656)]Route Call to
VDN 7656
REL COMP [CRV=93, FIE(Invoke,
Inv_id=4, 
Route End, cause=normal)]Call Routed
FAC [CRV=98, FIE(Invoke,
Inv_id=4, Event Report,
call_id=39,
event=call redirected)]
 Notification for
Call terminated
(VDN 7656 monitored
by another AP
Association)