Page History

...

 

...

The

...

Spacevars

...

0

...

Back to Table of Contents

Back to IP Multimedia Subsystem (IMS)

Back to SBC as P-CSCF

Back to P-Headers

series4

 supports P-The SBC supports P-Charging-Function-Addresses header as part of P-CSCF functionality. This header carries the charging function information.

...

SBC Provisioning

• As a P-CSCF, SBC ignores the

  Spacevars
  0 product

   ignores and removes P-Charging-Function-Addresses, if present, when it receives any request/response from UE or when it sends any  requestrequest/response to UE.
• As a P-CSCF, SBC the

  Spacevars
  0 product

   stores the values received in P-Charging-Function-Addresses header in a request or response from  IMS the IMS core in the initial dialog-establishing request or a stand-alone transaction.
  
  Storing of P-Charging-Function-Addresses is controlled by a provisioning flag (storePChargingFuncAddr) associated with Ingress TG with respect to Request and Response message (Core side).

• As a P-CSCF, SBC inserts the

  Spacevars
  0 product

   inserts previously saved P-Charging-Function-Addresses headers before forwarding the message to IMS core  when when it receives any request or response from UE.
  
  Insertion of P-Charging-Function-Addresses is controlled by a provisioning flag (addPChargingFuncAddr) associated with Egress TG with respect to Request and Response message (Core side).

CDR Processing

The SBC saves

Spacevars
0 product

 saves the P-Charging-Function-Addresses header with the ccf-value and ecf values to the CDR in ingress and egress protocol specific variants fields. The P-Charging-Function-Addresses header is not received or created for INVITE. P-CSCF stores the P-Charging-Function-Addresses header in 200 OK response for REGISTER, and then adds this stored value in the outgoing INVITE towards the IMS Core.