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

							14. VDN in Coverage Path Interactions
Issue 6 June 1997
B-133
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the Switch Comments
FAC [CRV=98, FIE(Invoke,
Inv_id=2, Event Report,
call_id=37,
event=call offered,
calling number=9085669660, 
called number=5678, 
domain=VDN 5678)]Call Offered
to VDN 5678
REG [CRV=93, FIE(Invoke,
Inv_id=4, Route,
calling number=9085669660, 
called number=5678)]Route Request
FAC [CRV=93, FIE(Invoke,
Inv_id=7, Route Select,
called number=5700)]Route to
VDN 5700
REL COMP [CRV=93, FIE
(Invoke,Inv_id=6, Route End,
cause=normal)]Call Routed
FAC [CRV=98, FIE(Invoke,
Inv_id=98, Event Report,
call_id=37,
event=call offered,
calling number=9085669660,
called number=5678,
domain=VDN 5700)]Call Offered to
VDN 5700
FAC [CRV=98, FIE(Invoke,
Queued Event Report
Inv_id=12, Event Report,
call_id=37, event=queued,
calls in queue=21,
domain=3459)]Call Queues to ACD
Split 3459
FAC [CRV=98, FIE(Invoke,
Queued Event Report
Inv_id=12, Event Report,
call_id=37, event=queued,
calls in queue=2,
domain=3460)]Call Queues to ACD
Split 3460
(Continued on next page) 
						

							Message Scenarios
B-134Issue 6 June 1997 
FAC [CRV=98, FIE(Invoke,
Inv_id=14, Event Report,
call_id=37, party_id=2,
event=alerting,
calling number=9085669660, 
called number=5678,
connected number=4566,
domain=3460)]Alerting Event Report
(Call Delivered to
Agent 4566)
FAC [CRV=98, FIE(Invoke,
Inv_id=16, Event Report,
call_id=37, party_id=2,
event=connected,
calling number=9085669660,
called number=5678,
connected number=4566)]Connected Event Report
(Call Connected
to Agent 4566)
FAC [CRV=98, FIE(Invoke,
Inv_id=18, Event Report,
call_id=37, party_id=2,
event=drop, cause=normal,
connected number=4566)]Drop Event Report
(Agent disconnects)
FAC [CRV=98, FIE(Invoke,
Inv_id=20, Call Ended,
call_id=37, cause=normal)]Call Terminates
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the Switch Comments 
						

							14. VDN in Coverage Path Interactions
Issue 6 June 1997
B-135
Outgoing Call over Non-ISDN Trunk
This section presents the call flow for an outgoing call over a non-ISDN trunk. 
Station 1234 initiates this preview dialing call (see Figure B-47).
Note that a Trunk Seized Event Report is generated when the switch places the 
call over a non-ISDN trunk. Furthermore, no Alerting or Connected Event Reports 
follow a Trunk Seized Event Report. The only event report that may be generated 
for the destination is a Dropped Event Report. 
Figure B-47. Outgoing Call over Non-ISDN Trunk
DEFINITY ECS
call_id=80
x1234
External Endpoint
(non-ISDN Trunk) 
						

							Message Scenarios
B-136Issue 6 June 1997 
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the Switch Comments
REG [CRV=96, FIE(Invoke,
Inv_id=3, 3P Make Call,
called number=99085766362
calling number=1234)]AP Requests Make Call
from Station 1234 to
External Destination
FAC [CRV=96, FIE(Invoke,
Inv_id=4, Event Report,
call_id=80, party_id=2,
event=trunk seized,
called number=#####)]Trunk Seized
Event Report
(Off-premises Call
over non-ISDN trunk)
FAC [CRV=96, FIE(Invoke,
Inv_id=6, Event Report,
call_id=80, party_id=1,
event=hold,
connected number=1234)]Hold Event Report
(Station 1234 goes
on Hold)
FAC [CRV=96, FIE(Invoke,
Inv_id=5, 3P Selective Reconnect,
party_id=1)]AP Requests Reconnect
FAC [(CRV=96, FIE(Return
Result, Inv_id=5)]Call Reconnected
FAC [(CRV=96, FIE(Invoke,
Inv_id=8, Event Report,
call_id=80, party_id=2,
event=drop,
connected number=#####)]Drop Event Report
for External Destination
REL COMP [(CRV=96, 
FIE (Invoke,
Inv_id=4, Call Ended,
call_id=80,
cause=normal clearing)]Call Terminated 
						

							14. VDN in Coverage Path Interactions
Issue 6 June 1997
B-137
Outgoing Call over ISDN Trunk that Results in
an ISDN Progress Message
This section presents the call flow for an outgoing call over an ISDN trunk that 
traverses one or more non-ISDN networks before it reaches its destination. 
Station 4567 initiates an outgoing call to an external destination. Station 4567 has 
Domain Control active and uses the Auto Dial capability to initiate the call
(see Figure B-48).
When a call leaves the ISDN network, an ISDN PROGress message is sent from 
the PRI network to the switch and subsequently to the ASAI Adjunct Processor. 
The switch sends the contents of the PROGress message in a Cut-Through Event 
Report.   Multiple PROGress messages may be sent for a call; each one is 
mapped into a Cut-Through Event Report. 
For a call that has resulted in a Cut-Through Event Report being generated, the 
Alerting Event Report is optional. A Connected and/or Drop Event Report is 
always sent as long as the call utilizes the ISDN facilities.
Figure B-48. Call Flow for Outgoing ISDN Call that Traverses a Non-ISDN Network
DEFINITY ECS
call_id=60
x4567
non-ISDN
NetworkExternal Endpoint
(ISDN Trunk) 
						

							Message Scenarios
B-138Issue 6 June 1997 
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the Switch Comments
FAC [CRV=30, FIE(Invoke,
Inv_id=4, event report,
call_id=60, party_id=1,
event=call initiated)]Call Initiated Event
(Station 4567 goes 
off-hook)
FAC [CRV=30, FIE(Invoke,
Inv_id=5, 3P Auto Dial,
called number=99085766362)]AP Requests Auto Dial
for Station 4567
FAC [CRV=30, FIE(Invoke,
Inv_id=6, Event Report,
call_id=60, party_id=1, 
calling number=4567,
called number=99085766362,
event=call originated)]Call Originated
FAC [CRV=30, FIE(Invoke,
Inv_id=10, Event Report,
call_id=60, party_id=2,
event=cut-through
Location=public network
serving local user,
progress=in-band info
now available)]Cut-Through Event
Report (Contains the
Progress Indicator IE)
FAC [CRV=30, FIE(Invoke,
Inv_id=8, Event Report,
call_id=60, party_id=2,
event=connected,
calling number=4567,
called number=99085766362,
connected number=9085766362)]ISDN Connect
FAC [CRV=30, FIE(Invoke,
Inv_id=6, Event Report,
call_id=60, party_id=2,
event=drop,
connected=#####,
cause=normal clearing)](External Destination
Drops)
FAC [CRV=30, FIE(Invoke,
Inv_id=4, Event Report,
call_id=60, party_id=1,
event=drop,
connected=4567,
cause=normal clearing)](Station 4567 Drops)  
						

							15. User to User Information (UUI)
Issue 6 June 1997
B-139
15. User to User Information (UUI)
User Scenarios — User to User Information
Figure B-49 shows a typical distributed call configuration. An ASAI host is 
connected to each of the switches and calls are delivered to either switch. The 
applications running on the ASAI hosts are not connected to each other.
Figure B-49. Distributed ACD Configuration
ISDN PRI
Non PRI
VRU Port1VDN11
VDN0
VDN2
VDN1
VRU Split1
ACD SplitAASAI ASAI
AdjunctASAI
AdjunctASAIVDN3
VDN4
ACD SplitB
VRU Port2
AgentA AgentB Switch A Switch B
ISDN PRI
AB 
						

							Message Scenarios
B-140Issue 6 June 1997 
The following call sequences show typical UUI scenarios. Call Sequence 1 shows 
an incoming non-ISDN PRI call to Switch A, delivered to VDN1. VDN1 delivers the 
call to VRU Port1 in VRU Split1. After the caller terminates the VRU session, the 
ASAI host transfers the call to VDN2 for further processing. The ASAI host 
includes UUI in the 3rd Party Make Call used to start the transfer. While the call is 
in VDN2, the call interflows to Switch B. The call is accepted at Switch B and an 
announcement is played while the call waits in queue for ACD Split B.
Call Sequence 2 shows an incoming ISDN PRI call to Switch A, delivered to 
VDN1. VDN1 contains a collect digits vector step followed by an adjunct routing 
vector step. The host routes the call, including UUI information, to VDN2 that tries 
to interflow the call to Switch B. Switch B does not accept the call and the call 
connects to Agent A in Switch A.
Call Sequence 3 shows an incoming ISDN PRI call to Switch A, delivered to 
VDN1. The incoming ISDN call contains UUI data. While in VDN1, the call is 
routed to VDN3 in Switch B including UUI information. Switch B connects the call 
to VRU Port2. After the VRU terminates the caller session, the ASAI host drops 
the call, including UUI information, back to Switch A. When the trunk to Switch B 
drops, the call is directed to VDN11. The host on Switch A drops the call including 
UUI information in the request. 
						

							15. User to User Information (UUI)
Issue 6 June 1997
B-141
Action/OperationHost A — Event
Notification VDN 1Host B — Event
Notification VDN 4
Call Sequence 1:
Incoming Call to Switch ACall Offered
call_id=1234
called number=VDN1 
domain=VDN1
trunk group=AAA
Call Delivered to VRU Alerting
call_id=1234
called number=VDN1
connected number=VRU
PORT
domain=VRU Split1 trunk 
group=AAA
party_id=2
Call Connected to VRU Connected
call_id=1234
called number=VDN1
connected number=VRU
PORT1
trunk group=AAA
party_id=2
VRU Places Call on Hold Hold
call_id=1234
connected number=VRU
PORT1
party_id=2
VRU Requests new call 3rd Party Make Call
calling number=VRU
PORT1
called number=VDN2
UUI=info1
VRU Transfers Call to 
VDN2Call Transferred
resulting call_id=5678
other call_id=1234
called number=VDN2
calling number=VRU
PORT1
connected
number=#####
party_id=1
old party_id=1
Call Queues Queued
call_id=5678
calls in queue=n
called number=VDN2
domain=ACD SplitA
(Continued on next page) 
						

							Message Scenarios
B-142Issue 6 June 1997 
Call Intraflows to
Switch B (VDN 3 is the
LAI VDN; VDN 4 is
the VDN used
for accepted calls)Call Offered
call_id=9000
called number=VDN3
calling number
domain=VDN4
LAI info=LAI info
UUI=info1
Call Queues to Split Queued
call_id=9000
calls in queue=1
called number=VDN3
domain=ACD SplitB
Call Connects to 
AnnouncementConnected
call_id=5678
called number=VDN3
trunk group=AAA
party_id=2
Call Delivered to Agent Alerting
call_id=9000
called number=VDN3
calling number
connected 
number=agentB
domain=ACD SplitB
party_id=2
UUI=info1
Call Connected to Agent Connected
call_id=9000
called number=VDN3
calling number
connected
number=agentB
party_id=2
Caller Drops Drop
call_id=5678
connected number=#####
party_id=1
Agent B Disconnects Drop
call_id=9000
connected
number=agentB
party_id=2
(Continued on next page) Action/OperationHost A — Event
Notification VDN 1Host B — Event
Notification VDN 4