This determines where the data is sent. There are also considerations
for redundancy and distributive deployment, which means collection functions
could be duplicated in various parts of the network. This means then, that the entities
providing the billing data must be aware of the charging entities supporting their part
of the network as identified by their IP addresses.
This header then provides the addresses of those entities that billing data should be
sent. The use of this information is detailed in Chapter 7.
P-CHARGING-FUNCTION-ADDRESS: ccf=192.1.5.34; ccf=191.6.4.98; ecf=192.9.3.3;
ecf=192.1.9.3
P-Charging-Vector This header is also used for IMS charging. It is inserted by a SIP
proxy (such as a CSCF) when a request or response is received. It is strictly up to local
policy as to how and when the header is inserted, but typically within an IMS architecture
this would be inserted by the gateways and each of the CSCF entities throughout
the network.
The information provided in this header is used to identify where a charging record
has been created (as identified by the address in the icid-generated-at= parameter) and
the network responsible for generating the record. The originating network is identified
in the orig-ioi= parameter.
There is also an identifier assigned for correlation purposes. This allows charging
entities to correlate this with other charging records for the same sessions.
Pages:
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177