FCI/SCI Messages
FCI/SCI Messages
As part of handling defined action rules for CUG handling,
error handling, billing bypass,
and Diameter Result-Code processing, a pre-configured
FurnishChargingInformation
or SendChargingInformation
message may be sent. Such messages are configured
with a name
so that they may be invoked by the applicable action rules.
Both FCI and SCI messages may only be sent along with a Connect
or Continue
operation, and therefore may
only be specified against action rules that allow the call to continue in this fashion. If more than one FCI
or SCI is selected to be sent (e.g. if both CUG handling and
Diameter Result-Code processing apply and specify such a
message, only the most recently-specified case will apply.
A sample FCI/SCI configuration might be:
<application name="<application instance name>" module="DsgScpApp">
...
<config>
...
<fcis>
<fci name="fci-x">012f000700000044000000460003642102886145ffffffffffff800800021fffffffffffffff6421700739ffffffffffffff</fci>
</fcis>
<scis>
<sci name="sci-100">300a8003016400a103800101</sci>
<sci name="sci-101">300a8003015400a103800101</sci>
</scis>
In the above, three FCI/SCI messages are defined and would have the following configuration:
Name | Data |
---|---|
fci-x |
(freeform hexadecimal data as configured) |
sci-100 |
Charging characteristics 0x0164 , party to charge 01 . |
sci-101 |
Charging characteristics 0x0165 , party to charge 01 . |
Configuration Details
Each fci
or sci
can support the following attributes:
Attribute | Type | Description |
---|---|---|
name |
String | [Required] The unique name for this FCI/SCI message. Used in rule actions to specify the message to send. |
(data) | Hexadecimal String | The hexadecimal data of the message. |