Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Add_docset_workflow
slagisettypkothandaramanbscoggins
AUTH1bscoggins
DEV1
LDEV1bscoggins
SVT1
LSVT1

 

Noprint
Panel
borderColorgreen
bgColortransparent
borderWidth2

Back to Table of Contents

Back to IP Multimedia Subsystem (IMS)

Back to SBC as P-CSCF

Back to P-Headers

...

SBC retains the same "icid-value" (which was is generated during the first egressed INVITE) during the Crankback/Redirected (3xx) call in the P-Charging-Vector header in an egressed INVITE. When the flag , storeICID, is enabled, all the CDRs (ATTEMPT/START/STOP) contains the same ICID value for Crankback/Redirected call in protocol specific string as well as in the original call records.

This is achieved by:

  • Disabling pChargingVectorHeader transparency flag at the IP Signaling Profile attached with the TG, towards the IMS Core side.
  • Enabling createPChargingVector flag at the IP Signaling Profile attached with the TG, towards the IMS Core side.
  • Disabling storePChargingVector flag at the IP Signaling Profile attached with the TG, towards the UE.

...

The

Spacevars
0product
acting as IBCF transparently passes the PCV received in any request from the P-CSCF to the IMS Core. Also, IBCF adds the stored PCV in the response to UE. This is achieved using the following configuration:

  • Enabling pChargingVectorHeader transparency flag in the IP Signaling Profile attached with the TG, towards the IMS Core side.
  • Disabling createPChargingVector flag in the IP Signaling Profile attached with the TG, towards the IMS Core side.
  • Enabling the storePChargingVector flag in the IP Signaling Profile attached with the TG, both towards the UE side and IMS Core side.

...