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.

...

borderColorgreen
bgColortransparent
borderWidth2

Back to Table of Contents

Back to IP Multimedia Subsystem (IMS)

Back to SBC as P-CSCF

...

 

The P-Charge-Info header conveys billing information about a party's call session, such as the billing identifier associated with the call.

The SBC suppor

Spacevars
0product
 supports P-Charge-Info header as per "draft-york-sipping-p-charge-info-08" and "draft-york-sipping-p-charge-info-10" standards with SIP to SIP, SIP-I to SIP, SIP to SIP-I and GW to GW call scenarios. When interworking with SIP mime, the Charge Number field in ISUP is used to map to/from P-Charge-Info header. This feature is supported by the ERE and external PSX.

...

  • To use the P-Charge-Info header and its attributes, you must first set includeChargeInformation flag to "includePChargeInfo".
  • To transparently pass P-Charge-Info header between SIP networks in SIP INVITE message, enable the 'pChargeInfoTransparency' flag.
Note
SBC The
Spacevars
0product
is not fully compliant to "draft-york-sipping-p-charge-info-10." NPI in P-Charge-Info header cannot have numeric value, and NOA can only be in decimal format.

For Egress IP Attribute configuration details, see the following pagesrefer to:

...