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

							15. User to User Information (UUI)
Issue 6 June 1997
B-143
Call Ended
call_id=5678
cause=normal
Call Ended
call_id=9000
cause=normal
Call Sequence 2:
Incoming Call to Switch ACall Offered
call_id=1235
called 
number=1235678914 
domain=VDN1
calling number=CPN/BN
Digits Collected by Call 
Prompting
Switch Request Route
for CallRoute Request
call_id=1235
called
number=1235678914
calling number=CPN/BN 
domain=VDN0
collected digits=001
Host Provides Route Route Select
called number=VDN2
UUI=info2
Call Routed Route End
cause=normal
Call Queues Queued
call_id=1235
calls in queue=y
called number=VDN2
domain=ACD SplitA
Call Intraflows to
Switch B (VDN 3 is the
LAI VDN)Call Offered
call_id=9000
called number=VDN3
calling number=CPN/BN 
domain=VDN3
LAI info=LAI info
UUI=info2
Call Denied by the
Switch BDrop
call_id=1235
connected number=#####
party_id=2Call Ended
call_id=9001
cause=normal
(Continued on next page) Action/OperationHost A — Event
Notification VDN 1Host B — Event
Notification VDN 4 
						

							Message Scenarios
B-144Issue 6 June 1997 
Call Delivered to Agent Alerting
call_id=1235
called
number=1235678914
calling number=CPN/BN
connected
number=agentA
domain=ACD SplitA
party_id=2
UUI=info2
Call Connected to Agent Connected
call_id=1235
called
number=1235678914
calling number=CPN/BN
connected
number=agentA
party_id=2
Agent Drops Drop
call_id=1235
connected
number=agentA
party_id=2
Call Terminates Call Ended
call_id=1235
cause=normal
(Continued on next page) Action/OperationHost A — Event
Notification VDN 1Host B — Event
Notification VDN 4 
						

							15. User to User Information (UUI)
Issue 6 June 1997
B-145
Action/OperationHost A — Event
Notification VDN 1Host B — Event
Notification VDN 4
Call Sequence 3:
Incoming Call to
Switch ACall Offered
call_id=1236
called
number=1235678914 
domain=VDN1
calling number=CPN/BN 
UUI=info0
Switch Request Route
for CallRoute Request
call_id=1236
called
number=1235678914
calling number=CPN/BN 
domain=VDN0
UUI=info0
Host Provides Route Route Select
called number=VDN3
UUI=info3
Call Routed Route End
cause=normal
Call Enters Switch B Call Offered
call_id=9002
called number=VDN3
calling number=CPN/BN 
domain=VDN3
UUI=info3
Call Delivered to VRU Alerting call_id=1236
called number=VDN3
calling number=CPN/BN 
connected number=##### 
UUI=info3Alerting 
call_id=9002
called number=VDN3
calling number=CPN/BN 
connected number=VRU
PORT2
party_id=2
domain=ACD SplitB UUI=info3
Call Connected to VRU Port Connected
call_id=1236
called number=VDN3
calling number=CPN/BN 
connected number=##### 
party_id=2Connected
call_id=9002
called number=VDN3
calling number=CPN/BN 
connected number=VRU
PORT2
party_id=2
(Continued on next page) 
						

							Message Scenarios
B-146Issue 6 June 1997 
VRU is disconnected 3rd Party Drop
call_id=9002
party_id=1
UUI=info4
Call Disconnected
(Switch B) Drop
call_id=1236
connected number=#####
party_id=2
UUI=info43rd Drop-ACK 
Call Ended
call_id=9002
cause=normal
Call Delivered to Return 
VDN 11Call Offered 
call_id=1236
called
number=1235678914 
domain=VDN11
calling number=CPN/BN 
UUI=info4
Host Drops Call 3rd Party Drop
call_id=1236
party_id=1
UUI=info5
Caller Disconnected 3rd Party Drop-ACK
Drop call_id=1236
connected number=#####
party_id=1
UUI=info5
Call Terminates Call Ended
call_id=1236
cause=normal
Action/OperationHost A — Event
Notification VDN 1Host B — Event
Notification VDN 4 
						

							16. User Scenarios — Connected IE for non-ISDN 
Trunks
Issue 6 June 1997
B-147
16. User Scenarios — Connected IE for
non-ISDN Trunks
Table B-1 shows the Event Reports provided for a monitored call that is routed 
over an outgoing non-ISDN trunk. The incoming call also uses a non-ISDN trunk 
and is directed to a VDN/vector that routes the call to an external number.
.
Table B-1. Incoming Call Routed to External Destination Example
Operation  Event Report
Incoming Call Call Offered
call_id=45
trunk group=102
called number=65678
domain=VDN 65678
Call Routed to 
External Destination
Non-ISDN Trunk Seized Trunk Seized
call_id=45 
party_id=2
called number=#####
Call Connected
Answer Supervision
Received from the NetworkConnect 
call_id=45
party_id=2
trunk group=102
called number=##### 
connected number=##### 
cause=normal
Called Party Drops Drop
call_id=45
party_id=2
cause=normal
connected number=#####
Call Terminates Call Ended
call_id=45
cause=normal 
						

							Message Scenarios
B-148Issue 6 June 1997 
17. User Scenarios — ASAI-Provided
Dial-Ahead Digits 
This is a simple scenario in which the host provides dial-ahead digits via a Route 
Select. After the dial-ahead digits are stored by the switch, the digits are collected 
using call prompting vector commands. The scenario also shows the ASAI Event 
Reports sent to a monitoring host.
Messages Sent
by the HostMessages Sent
by the Switch Comments
Call Offered ER
call_id=45,
calling number=3156778888, 
called number=5678, 
domain=VDN 65678Incoming ISDN Call to
VDN Vector Executed (VDN 
65678): 
1. Collect 1 digit 
2. Adjunct Routing 
3. Wait 4 secs
Route Request
call_id=45, 
calling number=3156778888, 
called number=5678, 
domain=VDN 65678,
user code=(call
prompt,
collected, digits=2)Switch Requests
Route
Route Select 
call_id=45,
called number=null,
user code=(cdp,
collected,
digits=123)Host Provides 3 Digits & Invalid 
Route
Route End
cause=invalid numberVector Execution
Continues:
4. Collect 1 Digit 
5. Goto step 8 if
digits=1 
6. Goto to step 9 if 
digits=2
7. Goto vector 111 if
uncond 
8. Route to 61123 if
uncond 
9. Route to 64444 if
uncond
(Continued on next page) 
						

							17. User Scenarios — ASAI-Provided Dial-Ahead Digits
Issue 6 June 1997
B-149
Route Request
call_id=45,
calling number=3156778888, 
called number=5678, 
domain=VDN 61123,
user code=(call prompt, 
collected, digits=23)Switch Requests
Another Route
Vector Executed (VDN
61123):
1. Collect 2 Digits
2. Adjunct Route 
3. Wait 4 secs
Route Select 
call_id=45,
called number=69990,
user code=(cdp,
collected,digits=6789)Host Routes
to VDN 69990
Route End
cause= normalCall Routed
VDN 69990 Executed: 
1. Collect 4 Digits
2. Queue to 55555 
3. Announcement
Alerting ER 
call_id=45, 
party_id=2,
calling number=3156778888, 
called number=5678, 
connected number=7777, 
domain=Split 55555Call Delivered to
Agent 7777
Connect ER
call_id=45
party_id=2,
calling
number=3156778888,
called number=5678,
connected
number=7777Agent 7777 Answers
Call
Agent Display for
Call Prompting Digits
Shows 6789
Drop ER
call_id=45, 
party_id=1, 
connected number=##### 
cause=normalCalling Party Drops
Call Ended
call_id=45
cause=normalCall Terminates
Messages Sent
by the HostMessages Sent
by the Switch Comments 
						

							Message Scenarios
B-150Issue 6 June 1997 
18. User Scenarios — ASAI-Requested
Digit Collection 
This is a sample scenario for an incoming ISDN call routed via Adjunct Routing to 
an external destination. The user has subscribed to receive 4-digit DNIS numbers. 
As part of the route, the host requests collecting 3 digits from the caller. 
Messages Sent
by the HostMessages Sent
by the Switch Comments
Call Offered ER
call_id=45, 
calling
number=3156778888,
called number=5678, 
domain=VDN 65678Incoming ISDN Call to 
VDN 
Vector Executed:
1. Collect 1 digit 
2. Adjunct Routing 
3. Wait 4 secs
Route Request 
call_id=45,
calling
number=3156778888,
called number=5678, 
domain=VDN 65678,
user code=(call
prompt,
collected, digits=2)Switch Requests
Route
Route Select
call_id=45,
called number=84154422800, 
party_id=1
user code=(tone detect,
collect, timer=0,
digits=3),
event=connectHost Routes to
External Destination,
Requests Tone
Detector for Caller
Party,
Disconnect Upon
Answer
Route End
cause=normalCall Routed
Trunk Seized ER 
call_id=45,
party_id=2,
connected number=#####,Route Call Over
Non-ISDN Trunk
(Continued on next page) 
						

							18. User Scenarios — ASAI-Requested Digit Collection
Issue 6 June 1997
B-151
Messages Sent
by the HostMessages Sent 
by the Switch Comments
Entered Digits ER
call_id=45,
user code=(tone
detect,
collected, no timer,
digits=4*#)Digits Entered
Connect ER
call_id=45, 
party_id=2 calling 
number=3156778888,
called number=5678,
connected
number=#####,
cause=network
connectCall Answered
by Destination
Drop ER 
call_id=45,
party_id=1
cause=normal
connected
number=#####Calling Party Drops
Call Ended
call_id=45
cause=normalCall Terminates 
						

							Message Scenarios
B-152Issue 6 June 1997 
19. User Scenarios —VDN Return
Destination
A customer may use the VDN Return Destination feature to provide a more 
flexible remote access feature together with host-based call security. The remote 
user/caller does not have to call back into the switch when multiple destinations 
need to be reached, nor does the caller have to enter his/her identification every 
time a new destination is desired. For example, a customer can program the 
following vector that is accessed by dialing a VDN that has a Return Destination 
administered.
1.Collect 8 digits after announcement 1001 (“Please enter your identification 
number and password followed by # sign.”)
2. Adjunct Routing link extension XXX1
3. Wait through 6 seconds of silence
4. Collect 16 digits after announcement 1002 (“Please enter the telephone 
number of your destination followed by # sign.”)
5. Adjunct Routing link extension XXX1
6. Wait through 6 seconds of silence
7. Disconnect after announcement 1003 (“We are sorry, but we are 
experiencing technical difficulties at this time, please try again later.”)
In this scenario, a remote caller calls into the switch by dialing the VDN 
administered with the Return Destination. The vector executed prompts the caller 
to enter an identification number and a password that is passed, via the adjunct 
routing vector command, to the host for validation. The host can keep track of 
invalid attempts or decide to de-activate or activate certain identification numbers 
based on customer set criteria. 
After the host-based security is passed (the host sends an Abort to cancel the 
switch Route request; otherwise, the host routes the call to an exception 
destination/VDN), the switch collects digits for the destination the caller wants to 
reach (vector step 4 above). The host receives the number entered by the caller 
(vector step 5 above) and validates the entered number to check if the caller is 
allowed to reach the specified destination. If so, the host routes the call to the 
desired (dialed) destination. 
If the host security is not passed, the host routes the call to an appropriate 
alternate destination (for example, announcement with security violation 
message) and logs the invalid call attempt. If the host is not available, the call is 
disconnected after an announcement (vector step 7 above).