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 a 
Charging Event Report 
before any other event 
report is sent that 
references the second leg 
of the call.
2. Called number is not 
consistent with the called 
number in call-control 
events.
Adjunct releases call.
3P Selective DropParty_id 2
DISCONNECT sent to 
network.
Return Result=ACK
RELEASE received from 
the network with final 
charge. A charge of 69 is 
received.Charging Event Call_id C2
Party_id 2
Charging_number A2
Called_number A1
Trunk Group=15
Trunk Member=1
Type of charge=final
charge value=69Final charge is reported. 
Application may decide to 
distribute charges to D1’s 
department.
ECS clears call record.
3P Call EndedCall_id C2
cause=normal clearing
Action/OperationNotification Association
(Trunk Group) Make Call Association Comments 
						

							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
             orig_addr 2
          return_ack=yes
ECS accepts and 
acknowledges.
3P Make Call Proceed             Party id 1
Station D1 goes off hook.
ECS recognizes dialed 
number as an address.Call is routed to an 
ISDN Trunk Group 
providing AOC-D.
Far end answers.
Connected Event Call_id C1
          Party_id 2
         trunk group_id T1
called_number #####
connected_number #####From ISDN 
CONNECT ?

Note: Calling and 
called number 
information not 
available from 
network.
ECS receives first charge 
update from ISDN FACility 
message.
Charging Eventcall_id C2
Party_id 2
Charging_number D1
Called_number A1
Trunk Group=15
Trunk Member=1
Type of charge=intermediate
charge value=156Application 
accumulates charge 
towards station D1’s 
department.
ECS receives second 
charge update from ISDN 
FACility message.
Charging Eventcall_id C2
Party_id 2
Charging_number D1
Called_number A1
Trunk Group=15
Trunk Member=1
Type of charge=intermediate
charge value=179Application 
accumulates charge 
and determines 
station D1’s 
department is 
over-budget.
(Continued on next page) 
						

							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 received as 
the final charge.
ECS acknowledges 3P 
Clear Call Request.
Return Result=ACK
Action/OperationNotification Association
(Trunk Group) Make Call Association Comments 
						

							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 the call. Alternatively, the application can use the Call_id 
reference provided with the Charging Event Report and match it with the Call_id 
of other ASAI associations in order to divide the charges according to the time 
spent on the conference by each participant. The network in this example is 
France VN4.
Before the events shown in the table, Station D1 added the two trunks to call C2, 
and called station D1 on call C1. Call C2 is on hold, about to be conferenced with 
call C1. The parties on call C2 are: Party ID 1=Station D1, Party ID 2 = called 
number A1 on trunk T1 (group 15, member 1), Party ID 3 = called number A2 on 
trunk T2 (group 600, member 31). The Party IDs for call C1 are Party ID 1 = 
Station D1, Party ID 2 = Station D2.
Action/
OperationEvent Notification 
Association 
(Trunk Group) Domain Control D1 Domain Control D2 Comments
Adjunct 
requests 
Domain 
(station) control 
on D1 & D2.3P Domain Control Request            Domain D13P Domain Control Request            Domain D2Adjunct requests 
control over 
stations D1 and 
D2. 
ECS accepts 
and 
acknowledges.
Return Result = ACKCall_id C1, Party ID 1
Call_ id C2, Party id 1
call_state=held
call_state=connectedReturn Result = ACKCall_id C1, Party ID 2
call_state=connectedThe ACK 
notifiies the 
adjunct that 
multiple calls are 
already in 
progress.
ECS receives 
charge update 
from ISDN-PRI 
INFORMATION 
message. For 
Party_id 2, 
charge value 
78659.
Charging Eventcall_id C2
Party_id 2
Charging_number D1
Called_number A1
Trunk Group=15
Trunk Member=1
Type of charge=intermediate
charge value=78659Station D1 
conferenced an 
outgoing trunk 
(15/1) earlier 
and is 
considered the 
controlling 
number.
Station D1 
presses 
conference 
button.
(Continued on next page) 
						

							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
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 A14-party 
conference is 
established. 
Party ids 2 and 3 
are trunks 
receiving 
charge advice 
that D1 
conferenced 
earlier into Call_
id C2. Charging 
Events for call 
C2 have 
already been 
sent and logged 
by the 
application.
ECS receives 
charge update 
from ISDN-PRI 
INFORMATION 
message. For 
Party_id 2, 
charge value 
80214.
Charging EventCall_id C2
Party_id 2
Charging_number D1
Called_number A1
Trunk Group=15
Type of charge=intermediate
charge value=80214
ECS receives 
charge update 
from ISDN -PRI 
INFORMATION 
message. For 
Party_id 3, 
charge value 
420.
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=420Since D1 
originally added 
this trunk 
(600/31), D1 is 
considered the 
charging 
number.
Station D1 
drops.
Drop EventCall_id C2
Party_id 1Drop EventCall_id C2
Party_id 1Station D1 is no 
longer on the 
call. Even 
though CDR 
Call Splitting is 
enabled, D1 
continues to 
receive 
charges. This is 
because the call 
still has three or 
more parties. No 
split charge is 
output at this 
time.
(Continued on next page)
Action/
OperationEvent Notification 
Association 
(Trunk Group) Domain Control D1 Domain Control D2 Comments 
						

							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 left.
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=84768ECS sends final 
charge 
associated with 
party_id 2. This 
charge goes to 
station D1.
Charging EventCall_id C2
Charging_number D1
Called_number A2
Trunk Group=600
Trunk Member=31
Type of charge=split
charge value=440ECS sends split 
charge. This 
charge goes to 
station D1. The 
party ID is not 
sent when CDR 
Call Splitting 
generates a 
split charge 
event.
ECS receives 
charge update 
from ISDN-PRI 
INFORMATION 
message for 
Party_id 3, 
charge value 
460.
Charging EventCall_id C2
party _id 3
Charging_number D2
Called_number A2
Trunk Group=600
Trunk Member=31
Type of charge=intermediate
charge value=20Call splitting 
has left D2 as 
the charging 
party. Amount 
of charge is 
adjusted 
downward by 
the amount 
charged to D1 
in the split 
charge event.
Action/
OperationEvent Notification 
Association 
(Trunk Group) Domain Control D1 Domain Control D2 Comments 
						

							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 Handling Treatment Table and is subsequently routed over another 
ISDN trunk group receiving Charge Advice.
Action/OperationNotification Association 
(Trunk Group) Comments
Incoming call on an ISDN trunk group 
is processed using the Incoming Call 
Handling Treatment Table.
An entry in the incoming Call 
Handling Treatment Table matches 
the service of the incoming call 
NSF IE. The called number is deleted 
and a new number is inserted.The new routing number for the call is 
processed using ARS analysis. ECS 
determines the routing pattern and 
selects the outgoing trunk group 
based on preference and trunk 
availability.
The call is routed as an outgoing call 
to an ISDN trunk group that is 
enabled for Charge Advice during the 
call.
The far end answers.
Note: Application will not receive 
notification of answer on far end.
The network sends the first charge 
advice message.Charging Eventcall_id C2
Party_id 2
Charging_number=T1
Called_number A1
Trunk Group=45
Trunk Member=5
Type of charge=intermediate
charge value=407The charging number, T1, is the 
Trunk Access Code (TAC) of the 
incoming trunk. This indicates that no 
local extension is on the call, and the 
ISDN-PRI calling number is 
unavailable.
The network sends the final charge 
advice message in RELEASE.
Charging Eventcall_id C2
Party_id 2
Charging_number=T1
Called_number A1
Trunk Group=45
Trunk Member=5
Type of charge=final
charge value=679Note: Application will not receive 
notification that the call is complete, 
other than the final charge associated 
with the 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
by the Switch Comments
REG [CRV=123, FIE(Invoke,
Inv_id=1, 3P Domain Control,
domain=extension 85046)]AP Requests Domain
Control of Station
85046
FAC [CRV=123, FIE(Return
Result, Inv_id=1,
3P Domain Control,
call_id=45, party_id=2,
call_state=alerting)]Domain Control Granted
for Station 85046
(One Call Alerting)
FAC [CRV=123, FIE(Invoke,
Inv_id=3, 3P Selective Drop,
call_id=45)]AP Requests to
Drop Station 85046
FAC [CRV=123, FIE(Return
Error, Inv_id=3,
3P Selective Drop,
cause=request not compatible
with call state)]Request Denied
(Call in the Alerting
State)
FAC [CRV=123, FIE(Invoke,
Inv_id=5, 3P Reconnect,
call_id=45)]AP Requests to
Connect to Call
FAC [CRV=123, FIE(Return
Error, Inv_id=5,
3P Reconnect,
cause=request not compatible
with call state)]Request Denied
(Call in the Alerting
State)
FAC [CRV=123, FIE(Invoke,
Inv_id=2, Event Report,
call_id=45,
event=call redirected)]Call Redirection
Event Report
(Call Goes to Coverage)
(Continued on next page) 
						

							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, FIE(Return
Result, Inv_id=1)]
 Domain Control Granted
for Station 67
(No Calls Present)
FAC [CRV=13, FIE(Invoke,
Inv_id=3, 3P Auto Dial,
called number=75602)]AP Requests Auto Dial
Call to Station 75602
FAC [CRV=13, FIE(Invoke,
Inv_id=2, Event Report,
call_id=76, party_id=1
event=call initiated)]Call Initiated
Event Report
(Station 67 Goes
Off-Hook)
FAC [CRV=13, FIE(Invoke,
Inv_id=4, Event Report,
call_id=76, party_id=1,
calling number=67,
called number=75602,
event=call originated)]Call originated
FAC [CRV=13, FIE(Invoke,
Inv_id=6, Event Report,
call_id=76, party_id=2,
event=drop,
connected number=#####,
cause=network congestion)]Drop Event Report
(Network Disconnects)
FAC [CRV=13, FIE(Invoke,
Inv_id=8, Event Report,
call_id=76, party_id=1,
event=drop,
connected number=67,
cause=normal clearing)]Drop Event Report
Station 67 Disconnects
(Call Terminates)