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

							3. Adjunct Routing Associations
Issue 6 June 1997
B-23
Call to VDN Routed to External Destination
This scenario shows the call flow for an incoming call to VDN 201 routed via the 
Adjunct Routing vector command to VDN 405 (see Figure B-10). At VDN 405, the 
call is routed via another Adjunct Routing vector command to an external 
destination. The adjunct processor does not have Event Notification active for 
VDNs 201 and 405.   The adjunct processor receives the Adjunct Routing 
requests.
Figure B-10. Call Flow for Incoming Call to VDN Routed to External 
Destination
DEFINITY ECS
VDN 201
Vector D
1. Adjunct Routing
VDN 405Vector E
1. Adjunct Routing
2. Wait 4 Seconds
3. Busy
4.  Incoming Call
call_id=31
2. Wait 4 Seconds
3. Busy Outgoing Call 
						

							Message Scenarios
B-24Issue 6 June 1997 
Messages Sent by the
Adjunct ProcessorMessages Sent
by the ECS Comments
REG [CRV=23, FIE(Invoke
Inv_id=4, Route
call_id=31,
trunk group number=560,
called number=201,
trunk group member=11,
domain=VDN 201)]Route Request
FAC [CRV=23, FIE(Invoke,
Inv_id=3, Route Select,
called number=405)]Route to
VDN 405
REL COMP [CRV=23,FIE(Invoke,
Inv_id=6, Route End,
cause=normal)]Call Routed
REG [CRV=56, FIE(Invoke,
Inv_id=4, Route,
call_id=31,
trunk group number=560,
called number=201,
trunk group member=11,
domain=VDN 405)]Route Request
FAC [CRV=56, FIE(Invoke,
Inv_id=3, Route Select,
dest_route_select=9,
called number=14157894567)]Route to External
Destination
REL COMP [CRV=56, FIE(Invoke,
Inv_id=6, Route End,
cause=normal)]Call Routed 
						

							3. Adjunct Routing Associations
Issue 6 June 1997
B-25
Call Routed Based on II-Digits
This scenario shows how an incoming call is treated based on the value of the 
Information Indicator (II) Digits (see Figure B-11). These digits indicate the type of 
telephone that the call was placed from. The following example shows how a 
company offering emergency roadside assistance handles calls from cellular or 
pay telephones differently than calls from wired telephones. Known numbers of 
current customers may also be handled differently, at the adjunct’s discretion.
Skill 1 (extension 70001) consists of people trained to deal with roadside 
problems (understand the problem, dispatch appropriate help, instruct the caller 
appropriately). Skill 2 (extension 70002) consists of agents with general training, 
who troubleshoot problems whenever they can, but who will also dispatch the call 
to an appropriate expert when necessary.
Figure B-11. Call Flow for Incoming Call Based on II-Digits
Call Sequence 1:
An incoming call on an ISDN-PRI trunk is delivered to VDN 8000. The ISDN trunk 
is configured to provide II-Digits along with CPN/BN. The II-Digits indicate that the 
call was placed from a cellular phone. The adjunct decides to route the call to 
skill 1, and to make it a priority call to speed its handling.
Call Sequence 2:
An incoming call on an ISDN-PRI trunk is delivered to VDN 8000. The ISDN trunk 
is configured to provide II-Digits along with CPN/BN. The II-Digits indicate that the 
call was placed from a normal wired phone. The adjunct decides to route the call 
to skill 2, and to make it a non-priority call.
DEFINITY ECS
VDN 8000 Vector R
1. adjunct route
2. wait 4 seconds
3. queue to main skill 2
4. . . . Incoming Call 
						

							Message Scenarios
B-26Issue 6 June 1997 
Call Sequence 3:
An incoming call on and ISDN-PRI trunk is delivered to VDN 8000. The ISDN 
trunk is configured to provide II-Digits along with CPN/BN. The II-Digits indicate 
that the call was placed from a normal wired phone. The calling number indicates 
that this call is from a preferred customer. The adjunct decides to route the call to 
skill 2, but to make it a priority call
.
Call Sequence 1:
Messages Sent by the
Adjunct ProcessorMessages Sent
by the ECS Comments
REGister [CRV=72,
FIE(Invoke, Inv_id=2, 
Route, call_id=1111,
domain=VDN 8000
Calling_Number=9085551234,
II_Digits=61)]Route Request
FAC [CRV=23,
FIE(Invoke,
Inv_id=3, 
Call_ID=1111,
Called number=70001
call_option=priority)]Route Select
REL COMP [CRV=72,
FIE(Invoke,Inv_id=4,
Route End,
cause=normal)]Call Routed
Call Sequence 2:
Messages Sent by the
Adjunct ProcessorMessages Sent
by the ECS Comments
REG [CRV=74, 
FIE(Invoke,Inv_id=2, 
Route, call_id=1112,
Call ID =1112
domain=VDN 8000,
Calling_Number=9085551235,
II_Digits=00)]Route Request
FAC [CRV=74,
FIE(Invoke,
Inv_id=3, 
Call_ID=1112,
Called number=70002
call_option=priority)]Route Select
REL COMP [CRV=74,
FIE(Invoke,Inv_id=4,
Route End,
cause=normal)]Call Routed
(Continued on next page) 
						

							3. Adjunct Routing Associations
Issue 6 June 1997
B-27
Call Sequence 3:
Messages Sent by the
Adjunct ProcessorMessages Sent
by the ECS Comments
REGister [CRV=76,
FIE(Invoke, Inv_id=2, 
Route, call_id=1113,
domain=VDN 8000
Calling_Number=9085551780,
II-Digits=00)]Route Request
FAC [CRV=76,
FIE(Invoke,
Inv_id=3, 
Call_ID=1113,
Called number=70002
call_option=priority)]Route Select
REL COMP [CRV=76,
FIE(Invoke,Inv_id=4,
Route End,
cause=normal)]Call Routed 
						

							Message Scenarios
B-28Issue 6 June 1997 
ISDN Information Received with Incoming Call
This scenario describes how II-Digits, UUI and CINFO information are received 
with an incoming call over an ISDN trunk. It is assumed that the link version was 
negotiated at V2 or later.
Figure B-12 shows how an incoming call to VDN 5678 is routed to extension 3456 
based on the information received with the call. 
Figure B-12. Call Flow for Incoming Call to VDN Routed to ACD Split
Messages Sent by the
Adjunct ProcessorMessages Sent by
the ECS Comments
FAC [CRV=98, FIE(Invoke,
Inv_id=26, Event Report,
call_id=37,
event=call offered,
calling number=2015666379, 
called number=9085765678, 
II Digits=5, UUI=98765421,
domain=VDN 5678)]Call Offered event provided
UUI and II Digits.
REG [CRV=93, FIE(Invoke,
Inv_id=4, Route,
call_id=37,
calling number=2015666379, 
called number=9085765678,
user code (CINFO) =123,
II Digits = 5, UUI=987654321)]Route Request provides 
CINFO which was collected 
during the Collect step
FAC [CRV=93, FIE(Invoke,
Inv_id=7, Route Select,
called number=3456)]
REL COMP [CRV=93, FIE(Invoke,
Inv_id=6, Route End,
cause=normal)]
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 
						

							4. Call Control Associations
Issue 6 June 1997
B-29
4. Call Control Associations
This section presents several scenarios for Call Control capabilities. It also 
provides the Event Reports received over Call Control associations.
Third Party Make Call to ACD Split 3456
This scenario shows the call flow for a Third_Party_Make_Call from extension 
6097 to ACD split 3456 (see Figure B-13). The call is cleared by a Third_Party_
Clear_Call request after it queues into ACD split 3456. Event Notification for ACD 
Split 3456 is active as presented in the initialization scenario.
Figure B-13. Call Flow for Third_Party_Make_Call to ACD 
DEFINITY ECS
ACD Split
3456
x6097call_id=90 
						

							Message Scenarios
B-30Issue 6 June 1997 
Messages Sent by the
Adjunct ProcessorMessages Sent
by the ECS Comments
REG [CRV=65, FIE(Invoke, 
Inv_id=1, 3P Make Call,
called number-3456, 
calling number=6097)]AP Requests Make Call 
from Station 6097 to ACD 
Split 3456
FAC [CRV=102, FIE(Invoke,
Inv_id=2, Event Report,
call_id=90,
event=call offered,
calling number=6097 
called number=3456
domain=ACD Split 3456)]Call Offered 
Event Report —
Notification Association
FAC [CRV=65, FIE(Invoke, 
Inv_id=2, Event Report,
call_id=90, event=queued,
called number=3456,
calls in queue=1,
domain=ACD Split 3456)]Queued Event Report
(Call Queues to
ACD Split 3456) —
3P Make Call Association
FAC [CRV=102, FIE(Invoke,
Inv_id=4, Event Report,
call_id=90, event=queued,
called number=3456,
calls in queue=1,
domain=ACD Split 3456)]Queued Event Report
(C al l  Queues to
ACD Split 3456) —
Notification Association
FAC [CRV=65. FIE(Invoke Inv_
id=3, 3P Clear Call,
call_id=90)]AP Requests Clear Call — 
3P Make Call Association
REL COMP [CRV=65,FIE(Return
Result, Inv_id=3)]Call Cleared 
3P Make Call 
Association Ended
FAC [CRV=102, FIE(Invoke
Inv_id=6,Call Ended,
call_id=90,
cause=normal clearing)]Call Terminated
(Because of Clear Request) —
Notification
Association 
						

							4. Call Control Associations
Issue 6 June 1997
B-31
Third Party Merge
This scenario shows the call flow and event reports for a conference operation 
performed by the adjunct processor via Third Party Call Control capabilities (See 
Figure B-14). Station 6022 initiates two Third_Party_Make_Calls to external 
destinations and conferences the called destinations using Third_Party_Merge. 
Both ISDN and non-ISDN facilities (trunks) are used in this scenario.
Figure B-14. Call Flow for Third_Party_Merge
DEFINITY ECS
call_id=48
x6022 call_id=52 Non-ISDN Trunk
949-1106
ISDN Trunk
949-7890 
						

							Message Scenarios
B-32Issue 6 June 1997 
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the ECS Comments
REG [CRV=81, FIE(Invoke, 
Inv_id=1,
3P Make Call,
called number=9491106,
calling number=6022,
dest_route_select=9)]AP Requests Make Call
from Station 6022 to 
External Destination
FAC [CRV=81, FIE(Invoke,
Inv_id=2, Event Report,
call_id=48, party_id=2,
event=trunk seized,
called number=#####)]Trunk Seized
Event Report
(Off-premises Call)
FAC [CRV=81, FIE(Invoke,
Inv_id=3, 3P Selective Hold, 
party_id=1)]AP Requests Hold
FAC [CRV=81, FIE(Return
Result, Inv_id=3)]Call Placed On
Hold
REG [CRV=80, FIE(Invoke,
Inv_id=1, 3P Make Call,
called number=99497890,
calling number=6022)]AP Requests Make Call
from Station 6022 to 
External Destination
FAC [CRV=80, FIE(Invoke,
Inv_id=2, Event Report,
call_id=52, party_id=2,
event=alerting,
calling number=9085766022,
called number=2019497890,
connected number=#####)]Alerting Event Report
(ISDN PRI Trunk
Used)
FAC [CRV=80, FIE(Invoke,
Inv_id=4, Event Report,
call_id=52, party_id=2,
event=connected,
calling number=9085766022
called number=2019497890,
connected number=2019493456)]Connected Event Report
(ISDN Provides
Connected Party)
(Continued on next page)