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

Advice of Charge
Issue 6 June 1997
B-163
D1 answers.Connected EventCall_id C2
Party_id 2
calling_number A1
called_number A2
connected_number D1Agent D1 and far-end begin 
conversation.
Second AOC update arrives 
from the network. A charge 
of 46 is received.
Charging Eventcall_id C2
Party_id 2
Charging_number A2
Called_number A1
Trunk Group=15
Trunk Member=1
Type of charge=intermediate
charge value=46ECS will send the charge 
value received in the 
second update from the 
network.
Notes:
1. ECS may send...

Message Scenarios
B-164Issue 6 June 1997 
User-Classified Call, Charge Information
The following scenario involves a user-classified call placed over a trunk facility 
that connects to a European Telecommunications Standards Institute (ETSI) 
network. The ETSI network provides Advice of Charge (AOC-D) during the call.
Action/OperationNotification Association
(Trunk Group) Make Call Association Comments
Adjunct initiates 
user-classified call to 
German ETSI network.3P Make_Call             dest_addr A1...

Advice of Charge
Issue 6 June 1997
B-165
Adjunct releases call.3P Clear CallApplication takes 
action to correct 
over-budget problem.
DISCONNECT sent to 
network.
RELEASE received from 
network 
without final 
charge.Charging Eventcall_id C2
Party_id 2
Charging_number D1
Called_number A1
Trunk Group=15
Trunk Member=1
Type of charge=final
charge value=179
cause=CS3/38ECS indicates that 
charge information is 
not received in first 
clearing message 
from the network and 
includes the last valid 
amount...

Message Scenarios
B-166Issue 6 June 1997 
Conference Call in Progress, Multiple Outgoing 
Trunks
The following scenario represents a conference call involving multiple internal 
parties and multiple outgoing trunks receiving charge advice from the network. In 
this scenario, the CDR Call Splitting option is enabled, as well as the 
trunk-to-trunk transfer option. The adjunct application can use the charging 
number information provided within Charging Event Reports as a means of 
distributing the cost of...

Advice of Charge
Issue 6 June 1997
B-167
ECS completes 
the conference.Call Conferenced EventOther_call_id C1
Resulting _Call_id C2
Party_id 1
Party_id 2
Party_id 3
Party_id 4
old_party_id=reslt call 1
old_party_id=reslt call 2
old_party_id=reslt call 3
old_party_id=othercall 2
connected_number D1
connected _number #####
connected_number #####
connected_number D2
connected_number #####
calling_number D1
called_number A1Call Conferenced EventOther_call_id C1
Resulting _Call_id C2
Party_id 1
Party_id 2...

Message Scenarios
B-168Issue 6 June 1997 
ECS receives 
update from 
ISDN-PRI 
INFORMATION 
message, For 
Party_id 3, 
charge value 
440.Charging EventCall_id C2
Party_id 3
Charging_number D1
Called_number A2
Trunk Group=600
Trunk Member=31
Type of charge=intermediate
charge value=440D1 is charging 
number. 
ISDN-PRI 
DISCONNECT 
received with 
charge value 
84768. (Party_
id drops from 
call.)
Drop EventCall_id C2
Party_id 2Party_id 2 
drops. Now the 
call is split, since 
there are only 
two parties...

Advice of Charge
Issue 6 June 1997
B-169
World-Class Routing (ARS/AAR), Incoming Call 
Routed over Outgoing ISDN Trunk Group, 
Charge Information Provided during the Call
The following scenario describes a single case in which event reports are 
received on the Charge of Advice Notification Association and not on any other 
notification, call-control, or domain-control association. In particular, this scenario 
involves an incoming call that is processed in the ISDN-PRI Trunk Group’s 
Incoming Call...

Message Scenarios
B-170Issue 6 June 1997 
22. Miscellaneous Cases
This section presents unsuccessful ASAI capability requests including common 
error cases. 
Unsuccessful Requests for Domain
(Station) Control
This scenario shows an ISDN PRI incoming call to station 85046. The adjunct 
processor requests to drop an alerting call, reconnect to an alerting call, and 
answer a non-existent call. Station 85046 is domain-controlled by the adjunct 
processor
Messages Sent by the 
Adjunct ProcessorMessages Sent...

22. Miscellaneous Cases
Issue 6 June 1997
B-171
FAC [CRV=123, FIE(Invoke,
Inv_id=7, 3P Answer,
call_id=45)]AP Requests to
Connect to Call
FAC [CRV=123, FIE(Return
Error, Inv_id=7,
3P Answer,
cause=invalid number)]Request Denied
(Call not Present)
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the Switch Comments 

Message Scenarios
B-172Issue 6 June 1997 
ISDN Network Congestion
This scenario shows a call from station 67 to an external destination (75602) 
using ISDN PRI facilities. The network disconnects the call with a cause (network 
congestion). The adjunct processor requests Domain_Control for station 67.
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the Switch Comments
REG [CRV=13, FIE(Invoke,
Inv_id=1, 3P Domain Control,
domain=extension 67)]AP Requests Domain
Control of Station 67
FAC [CRV=13,...