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

							19. User Scenarios —VDN Return Destination
Issue 6 June 1997
B-153
After the called destination disconnects from the call, the caller can remain on the 
line to be connected to the Return Destination. A sample Return Destination 
vector is as follows: 
1.Collect 16 digits after announcement 1002 (“Please enter the telephone 
number of your destination followed by # sign.”)
2. Adjunct Routing link extension XXX1
3. Wait through 6 seconds of silence
4. Disconnect after announcement 1003 (“We are sorry, but we are 
experiencing technical difficulties at this time, please try again later.”)
The caller, once connected to the Return Destination, can enter a second 
destination/phone number to connect to. The host performs the same validation 
on the destination number as in the first destination and routes the call as 
appropriate (destination entered by caller or alternate destination). Note that the 
host can also provide reports on all the destinations and times reached by each 
remote user. 
In the Return Destination vector, it is recommended that the first vector command 
give the caller the opportunity to disconnect from the call rather than immediately 
routing the call to some destination. If the call was immediately routed and then 
the caller decided to hang up, the destination the call was routed to would ring, 
alerting the called party, but no one would be on the line at the other end (this 
could be confusing to customers, and could be misinterpreted as a problem with 
the feature). Vector commands such as wait, collect after announcement, and 
announcement can provide the caller with the opportunity to disconnect before 
the call is routed. As an example, an announcement command with the recording 
“Please hang-up to end your call, or remain on the line if you wish to place another 
call” instructs the caller to disconnect, before the call is routed.  
						

							Message Scenarios
B-154Issue 6 June 1997 
20. ASAI Messaging Scenarios —
VDN Return Destination
This is a scenario where a call to a vector is routed using Adjunct Routing to an 
external destination. The host then drops the external destination and the call is 
delivered to the Return Destination for further vector processing. The scenario 
assumes that the call is being monitored by the ASAI host and that the Return 
Destination is VDN 77777. 
Messages Sent
by the HostMessages Sent
by the Switch Comments
Call Offered ER
call_id=45,
calling
number=3156778888,
called
number=9089575678,
domain=VDN 65678Incoming ISDN Call to
VDN 
— Monitoring Association
Return Destination=77777
Route Request
call_id=45,
calling number=3156778888,
called number=9089575678, 
domain=VDN 65678,
user code=(call prompt,
collected, digits=2)Switch Requests Route
Route Select
call_id=45, 
called number=8095766163, 
access code=9
user code=(tone detect, 
collect, timer=0,
digits=6789)Host Routes to 
External Destination,
and Requests a
Tone Detector
Route End
cause=normalCall Routed
Trunk Seized ER 
call_id=45, 
party_id=2,
connected number=#####,Call Seizes Outgoing
Trunk — Monitoring and 
Controlling Association
Entered Digits ER 
call_id=45, 
user code=(tone detect,
collected, timer=0,
digits=#)Digits Entered
Monitoring and
Controlling Association
(Continued on next page) 
						

							20. ASAI Messaging Scenarios — VDN Return 
Destination
Issue 6 June 1997
B-155
Take Control 
call_id=45Take Control ACK Host takes control of
call so that it can
drop trunk and have
call return for VDN
processing
3rd Party Drop 
party_id=23rd Party Drop-ACK Host Requests
Drop of Called Party
Called Party Dropped
Drop ER
call_id=45,
party_id=2
cause=normal 
connected
number=#####Called Party Dropped
— Monitoring Association 
Call Delivered to
Return Destination —
VDN 77777 (No Digit 
Collection)
Queued ER 
call_id=45,
calls in queue=2,
domain = ACD 4567,
called
number=9085766163Call Queues
Alert Event
call_id=45, 
party_id=2
calling number=3156778888,
called
number=9085766163,
connected
number=12345,
domain=Split 4567
Connect ER 
call_id=45, 
party_id=2 
calling
number=3156778888,
called
number=9085766163,
connected
number=12345,
domain=Split 4567Call Delivered to
Agent 12345 — Agent
Display for Call
Shows Nothing
(Continued on next page) Messages Sent
by the HostMessages Sent
by the Switch Comments 
						

							Message Scenarios
B-156Issue 6 June 1997 
Drop ER
call_id=45, 
party_id=2
cause=normal
connected
number=12345Called Party/Agent
Drops
Call Ended
call_id=45
cause=normalCall Terminates
Messages Sent
by the HostMessages Sent
by the Switch Comments 
						

							21. Flexible Billing
Issue 6 June 1997
B-157
21. Flexible Billing
User Scenarios — Flexible Billing
The following call sequences show typical Flexible Billing scenarios.
Call Sequence 1 shows an incoming call on an ISDN-PRI trunk delivered to 
Split A. The ISDN trunk is configured for MultiQuest service. The incoming call 
indicates in its SETUP message that Flexible Billing is supported. The call rings at 
agent 5001 and is answered. The agent requests a billing change on the call, 
setting the new rate to $10/minute. This billing change is sent over the ISDN-PRI 
trunk, and the 4ESS rejects the change. The switch sends the response to the 
ASAI adjunct. The agent requests a billing change on the call, setting the new rate 
to $5/minute. This billing change is sent over the ISDN-PRI trunk, and the 4ESS 
accepts the change. The switch sends the response to the ASAI adjunct.
Call Sequence 2 shows an incoming call on an ISDN-PRI trunk delivered to 
VDN A. The ISDN trunk is configured for MultiQuest service. The incoming call 
indicates in its SETUP message that Flexible Billing is supported. The call is 
adjunct-routed. The adjunct sees that Flexible Billing is enabled, and routes the 
call to split 1. The call rings at agent 5001 and is answered. The switch sends the 
response to the ASAI adjunct. The agent requests a billing change on the call, 
setting the new rate to $5/minute. This billing change is sent over the ISDN-PRI 
trunk, and the 4ESS accepts the change. The switch sends the response to the 
ASAI adjunct.
Call Sequence 3 shows an incoming call on an ISDN-PRI trunk delivered to 
VDN A. (This call sequence uses the same VDN as call sequence 2.) The ISDN 
trunk is configured for MultiQuest service. The incoming call indicates in its 
SETUP message that Flexible Billing is NOT supported. The call is 
adjunct-routed. The adjunct sees that Flexible Billing is NOT enabled and routes 
the call to split 2. The call rings at agent 5001 and is answered.
In Call Sequence 2, the agent knew that Flexible Billing was available on the call 
since the call routed to split 1. In Call Sequence 3, the agent knew to bill by a 
means other than Flexible Billing since the call routed to split 2. 
						

							Message Scenarios
B-158Issue 6 June 1997 
Action/OperationEvent Notification 
Split 1Set Value
(billing Change)
Call Sequence 1:
Incoming ISDN-PRI 
MultiQuest call with
Flexible BillingCall Offered
call_id=1111
called
number=9085551234 
domain=Split1
calling number=CPN/BN
Flexible Billing is enabled
Call rings at agent Alerting
call_id=1111
called
number=9085551234
calling number=CPN/BN
Agent answers call Connected
call_id=1111 
called
number=9085551234
calling number=CPN/BN
connected number=5001
party_id=2
Agent requests billing
change to $10/minute
(via adjunct)Set Value
Flexible Billing
type=new
amount=1000
Billing change is sent to
4ESS via ISDN-PRI 
trunk
4ESS rejects billing
change. PBX notifies
adjunct.Release Complete
Reject
Agent requests billing
change to $5/minute (via 
adjunct)Set Value
Flexible Billing
type=new rate
amount=500
Billing change is sent to
4ESS via ISDN-PRI 
trunk
4ESS accepts billing
change. PBX notifies
adjunct.Release Complete
Return Result
(Continued on next page) 
						

							21. Flexible Billing
Issue 6 June 1997
B-159
Action/Operation Route RequestEvent Notification
Split 1Set Value
(billing Change)
Call Sequence 2:
Incoming ISDN-PRI 
MultiQuest call with 
Flexible Billing
Adjunct Route
Request Route Request
call_id=1112
called 
number=9085551234 
domain=VDN A
calling 
number=CPN/BN 
Flexible Billing is 
enabled
Adjunct replies to 
Route RequestRoute Select
called
number=Split 1
Call is offered to 
split 1Call Offered 
call_id=1112
called
number=Split1 
domain-=Split1
calling 
number=CPN/BN 
Flexible billing is 
enabled
Call rings at agent Alerting 
call_id=1112
called 
number=9085551234 
calling 
number=CPN/BN
(Continued on next page) 
						

							Message Scenarios
B-160Issue 6 June 1997 
Action/Operation Route RequestEvent Notification
Split 1Set Value
(billing Change)
Agent answers call Connected
call_id=1112
called 
number=9085551234 
calling
number=CPN/BN
connected
number=5001
party_id=2
Agent requests
billing change
to $5/minute (via 
adjunct)Set Value
Flexible Billing
type=new rate
amount=500
Billing change is
sent to 4ESS via 
ISDN-PRI trunk 
4ESS accepts
billing change. PBX 
notifies adjunctRelease Complete
Return Result
Call Sequence 3:
Incoming ISDN-PRI 
MultiQuest call
without Flexible
Billing
Adjunct Route 
RequestRoute Request 
call_id=1112 
called 
number=9085551234 
domain=VDN A
calling
number=CPN/BN 
Flexible Billing is
disabled
Adjunct replies to 
Route RequestRoute Select 
called 
number=Split2
(Continued on next page) 
						

							21. Flexible Billing
Issue 6 June 1997
B-161
Action/Operation Route RequestEvent Notification 
Split 1Set Value
(billing Change)
Call is offered to 
split 2Call Offered 
call_id=1112 
called
number=Split1 
domain=Split1
calling
number=CPN/BN 
Flexible billing is
disabled
Call rings at agent Alerting 
call_id=1112 
called 
number=9085551234 
calling
number=CPN/BN
Agent answers call Connected 
call_id=1112
called 
number=9085551234 
calling
number=CPN/BN 
connected
number=5001
party_id=2 
						

							Message Scenarios
B-162Issue 6 June 1997 
Advice of Charge
Switch-Classified Call Receives Charging 
Information During the Call
This scenario deals with a predictive call that is directed off DEFINITY ECS to a 
German 1TR6 network. The switch-classified call options, answering machine 
detection and call classification after answer, are not enabled while CDR call 
splitting is enabled. CDR is administered to report the group extension on calls to 
hunt groups. The predictive call is placed on behalf of a hunt group (A2).
Action/OperationNotification Association
(Trunk Group) Make Call Association Comments
Adjunct requests Event 
Notification on all trunk 
groups for ISDN AOC.Event Notification RequestDomain type=TAC
Domain Value=#####This request may be made 
once after link initialization.
ECS accepts request.
Return Result=ACK
Adjunct initiates predictive 
call. (The network is German 
National ISDN 1TR6.)3P Make_Call             dest_addr A1
             orig_addr A2
            alert_dest_firstAMD is not enabled for this 
call.
Call alerts the far-end.
Alerting Event           Call_id C1
          Party_id 2
        calling_number A2
called_number A1
connected_number #####
1
The Alerting event is 
generated from the 
ISDN-PRI network and may 
not be provided over ASAI.
Far end answers.
Answer supervision 
received.
Answered EventCall_id C2
Party_id 2
called_number A1
connected_number #####
First AOC update received 
from ISDN INFORMATION 
message. 
A charge of 23 is 
received.
Note: The charging event 
report is not provided since 
the second leg of the call 
has not been merged with 
the first leg. 
Second leg of the 
switch-classified call is set 
up to hunt group A2. Agent 
at ext. D1 is available. ECS 
merges first and second legs 
of the call.
Alerting EventCall_id C2
Party_id 2
calling_number A1
called_number A2
connected number D1Agent extension D1 begins 
alerting. No split charge is 
output as the result of this 
merge.
1. In Germany, a 1TR6 network will provide connected number to the originator of the call.
(Continued on next page)