Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 2

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • createPChargingVector at IP Signaling Profile
  • storePChargingVector at IP Signaling Profile
  • pChargingVectorHeader transparency flag at IP Signaling Profile
  • interOperatorId flag at Trunk Group

P-CSCF will never does not transparently pass a P-Charging-Vector header received from UE in any request to IMS core. P-CSCF will create creates a new P-Charging-Vector header for each request (REGISTER, INVITE & , and OOD non-INVITE) containing a unique "icid-value" and "icid-generated-at" parameters and insert the same in the outgoing request towards the core.

SBC retains the same "icid-value" (which was 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.

...