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

							2. Notification Associations
Issue 6 June 1997
B-13
External Call to VDN Routed to Station
This scenario shows the call flow for an incoming ISDN PRI call to VDN 5678 that 
is routed via the Adjunct Route vector command to station 3001 (Figure B-6). 
Station 3001 does not answer the call and the call redirects to station 4003, 
maintaining a simulated bridged appearance at station 3001. Station 3001 
answers the call causing the call to be disconnected from station 4003.
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-6. Call Flow for Incoming Call to VDN Routed to Station
DEFINITY ECS
VDN 5678
Vector A
1. Collect Digits
2. Adjunct Routing
3. Wait 4 Seconds
4. Route to 0 Incoming Call
call_id=3
x4003
x3001Stations 
						

							Message Scenarios
B-14Issue 6 June 1997 
Messages Sent by the 
Adjunct Processor Messages Sent by the ECS Comments
FAC [CRV=98, FIE(Invoke,
Inv_id=2, Event Report,
call_id=3,
event=call offered,
calling number=2015661234,
called number=2015765678,
domain=VDN 5678)]Call Offered to
VDN 5678
REG [CRV=13, FIE(Invoke,
Inv_id=4, Route,
call_id=3,
calling number=2015661234, 
called number=2015765678,
domain=VDN 5678,
user code=322058)]Route Request
FAC [CRV=13, FIE(Invoke,
Inv_id=3, Route Select,
called number=3001)]Route to Station
3001
REL COMP [CRV=13, FIE(Invoke,
Inv_id=6, Route End,
cause=normal)]Call Routed
FAC [CRV=98, FIE(Invoke,
Inv_id=4, Event Report,
call_id=3, party_id=2,
event=alerting,
calling number=2015661234, 
called number=2015765678,
connected number=3001)]Alerting Event Report
(Call Alerts Station
3001)
FAC [CRV=98, FIE(Invoke,
Inv_id=6, Event Report,
call_id=3, party_id=8,
event=alerting,
calling number=2015661234, 
called number=2015765678,
connected number=4003)]Alerting Event Report
(Call Alerts Station
4003)
(Continued on next page) 
						

							2. Notification Associations
Issue 6 June 1997
B-15
Messages Sent by the 
Adjunct Processor Messages Sent by the ECS Comments
FAC [CRV=98, FIE(Invoke,
Inv_id=8, Event Report,
call_id=3, party_id=2,
event=connected,
calling number=2015661234,
called number=2015765678,
connected number=3001)]Connected Event Report
(Call Answered at
Station 3001)
FAC [CRV=98, FIE(Invoke,
Inv_id=12, Event Report,
call_id=3, party_id=1,
event=drop,
connected number=#####,
cause=normal clearing)]Drop Event Report
(Calling Party Drops)
FAC [CRV=98, FIE(Invoke,
Inv_id=14, Call Ended,
call_id=3,
cause=normal clearing)]Call Terminates 
						

							Message Scenarios
B-16Issue 6 June 1997 
External Call to VDN Routed to Announcement
Extension
This scenario shows the call flow for a non-ISDN incoming call to VDN 5678 
routed via the Adjunct Route vector command to announcement extension 3002 
(Figure B-7).
VDN 5678 has Event Notification active as presented in the initialization scenario. 
The ASAI messages generated by the Adjunct Routing vector command are also 
shown.
Figure B-7. Call Flow for Incoming Call to VDN Routed to Announcement
DEFINITY ECS
Vector A
1. Collect Digits
2. Adjunct Routing
3. Wait 4 SecondsIntegrated
Announcement VDN 5678 Incoming Call
call_id=90
4. Route to 0
3002 
						

							2. Notification Associations
Issue 6 June 1997
B-17
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the ECS Comments
FAC [CRV=98, FIE(Invoke,
Inv_id=2, Event Report,
call_id=90,
event=call offered,
trunk group number=102
called number=5678,
domain=VDN 5678)]Call Offered to
VDN 5678
REG [CRV=13, FIE(Invoke,
Inv_id=4, Route,
call_id=90,
trunk group number=102
called number=5678,
domain=VDN 5678,
user code=322058)]Route Request
FAC [CRV=13, FIE(Invoke, 
Inv_id=90, Route Select,
called number=3002)]Route to Announcement
Extension 3002
REL COMP [CRV=13, FIE(Invoke, 
Inv_id=6, Route End, 
cause=normal)]Call Routed
FAC [CRV=98, FIE(Invoke,
Inv_id=4, Event Report,
call_id=90, party_id=2,
event=alerting,
Trunk Group number=102
called number=5678,
connected number=3002)]Alerting Event Report —
Call Queues to
Announcement 3002
FAC [CRV=98, FIE(Invoke,
Inv_id=6, Event Report,
call_id=90, party_id=2,
event=connected,
Trunk Group number=102
called number=5678,
connected number=3002)]Connected Event Report —
Call Connected to
Announcement
FAC [CRV=98, FIE(Invoke,
Inv_id=8, Event Report,
call_id=90, party_id=2,
event=drop,
connected number=3002,
cause=normal clearing)]Drop Event Report —
Announcement Disconnects
FAC [CRV=98, FIE(Invoke,
Inv_id=10, Call Ended,
call_id=90,
cause=normal clearing)]Call Terminates 
						

							Message Scenarios
B-18Issue 6 June 1997 
External Call to ACD Split
This scenario shows the call flow for an incoming ISDN PRI call to ACD split 3456 
(Figure B-8). The agent at station 4534 answers the call. ACD Split 3456 has 
Event Notification active as presented in the initialization scenario. 
Figure B-8. Call Flow for Incoming Call to ACD Split
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the ECS Comments
FAC [CRV=102, FIE(Invoke,
Inv_id=2, Event Report,
call_id=54,
event=call offered,
calling number=2125437890, 
called number=9085763456, 
domain=ACD Split 3456)]Call Offered to
ACD Split 3456
FAC [CRV=102, FIE(Invoke,
Inv_id=4, Event Report,
call_id=54, event=queued
called number=9085763456,
calls in queue=2,
domain=ACD Split 3456)]Queued Event Report
(Call Queues to ACD Split 
3456)
FAC [CRV=102, FIE(Invoke,
Inv_id=6, Event Report,
call_id=54, party_id=2,
event=alerting,
calling number=2125437890,
called number=9085763456,
connected number=4534,
domain=ACD Split 3456)]Alerting Event Report
(Call Delivered to
Agent 4534)
(Continued on next page)
DEFINITY ECS
ACD Split
3456 Incoming Call
call_id=54
x4534Agent
Extension 
						

							2. Notification Associations
Issue 6 June 1997
B-19
FAC [CRV=102, FIE(Invoke,
Inv_id=8, Event Report,
call_id=54, party_id=2,
event=connected,
calling number=2125437890, 
called number=9085763456,
connected number=4534)]Connected Event Report
(Call Connected to
Agent 4534)
FAC [CRV=102, FIE(Invoke,
Inv_id=10, Event Report,
call_id=54, party_id=2,
event=drop,
connected number=4534,
cause=normal clearing)]Drop Event Report
(Agent Disconnects)
FAC [CRV=102, FIE(Invoke,
Inv_id=12, Call Ended,
call_id=54,
cause=normal clearing)]Call Terminates
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the ECS Comments 
						

							Message Scenarios
B-20Issue 6 June 1997 
3. Adjunct Routing Associations
This section presents sample Adjunct Routing scenarios. Additional Adjunct 
Routing scenarios are presented in the “Notification Associations” section earlier 
in this appendix.
Call to VDN Routed Directly to ACD Agent
This scenario shows the call flow for an incoming ISDN PRI call to VDN 8905 
routed via the Adjunct Routing vector command to a specific ACD agent (station 
3567) (see Figure B-9). The first attempt for a route fails because the specified 
ACD agent is not logged into the ACD Split.The adjunct processor reroutes the 
call to ACD agent 4534. The second route delivers the call to the ACD agent. The 
call queues for the agent and the caller drops before the agent answers the call.
The adjunct processor does not have Event Notification active for VDN 8905. 
Event Notification for ACD Split 3456 is active as presented in the initialization 
scenario. Note that Domain Control for the ACD station would have provided event 
reports for the call.
The adjunct processor receives the Adjunct Routing requests.
Figure B-9. Call Flow for Incoming Call to VDN Routed to Specific ACD Agent
DEFINITY ECS
Vector R
1. Adjunct Routing
2. Wait 4 Seconds
3. Adjunct RoutingACD Split
3456 VDN 8905 Incoming Call
call_id=72
x4534 4. Wait 4 SecondsAgent
Extension
5. Busy 
						

							3. Adjunct Routing Associations
Issue 6 June 1997
B-21
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the ECS Comments
REG [CRV=66, FIE(Invoke,
Inv_id=2, Route,
call_id=16,
calling number=8097670313,
called number=9085768905,
domain=VDN 8905)]Route Request
FAC [CRV=66, FIE(Invoke,
Inv_id=3, Route Select,
called number=3567,
domain=ACD Split 3456,
direct agent call=yes)]Route Directly to
ACD Agent 3567 on
Split 3456
REL COMP [CRV=66, FIE(Invoke,
Inv_id=4, Route End,
cause=agent not logged in)]Route Failed
REG [CRV=68, FIE(Invoke,
Inv_id=2, Route,
call_id=16,
calling number=8097670313,
called number=9085768905,
domain=VDN 8905)]Route Request
FAC [CRV=66, FIE(Invoke,
Inv_id=3, Route Select,
called number=4534,
domain=ACD Split 3456,
direct agent call=yes)]Route Directly to
ACD Agent 4534 on
Split 3456
REL COMP [CRV=66, FIE(Invoke,
Inv_id=4, Route End,
cause=normal)]Call Routed
FAC [CRV=102, FIE(Invoke,
Inv_id=6, Event Report,
call_id=16, party_id=2,
event=alerting,
calling number=8097670313,
called number=9085768905,
connected number=4534,
domain=ACD Split 3456)]Alerting Event Report 
(Call Delivered to
Agent 4534)
FAC [CRV=102, FIE(Invoke,
Inv_id=8, Event Report,
call_id=16, party_id=1,
event=drop,
connected number=#####,
cause=normal clearing)]Drop Event Report 
(Caller Disconnects)
(Continued on next page) 
						

							Message Scenarios
B-22Issue 6 June 1997 
FAC[CRV=102, FIE(Invoke,
Inv_id=10, Call Ended,
call_id=16,
cause = normal clearing)] Call Terminates
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the ECS Comments