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....

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...

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...

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...

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...

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...

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...

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...

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,...