Sentinel IP-SM-GW 3.0.0 :: Sentinel IP Short Message Gateway Administration guide

Detecting Online Charging

The OC-Charging-Result AVP in a CDR or ACR indicates whether online (Diameter Ro) charging was used for a session. This may be used to determine if further action is needed when processing CDRs offline.

An OC-Charging-Result value of -1 means that online charging was not used for the session.
Otherwise the value is set to the Diameter Result-Code AVP value.

Populated AVPs in the Multiple-Services-Credit-Control AVP

The Multiple-Services-Credit-Control AVP is of type grouped, and is defined in RFC 4006. Section 7.1.4 of 3GPP TS 32.299 defines it with additional 3GPP specific parameters and states some IETF parameters are not used in the 3GPP.

AVP Name Specification reference Included in CDR Included in CCR Included in ACR Comments

AVP Name	Specification reference	Included in CDR	Included in CCR	Included in ACR	Comments
Requested-Service-Unit	IETF RFC 4006	No	Yes	No	Used in the CCR. The CDR represents this information in the OC-Session-Counter AVP
Used-Service-Unit	IETF RFC 4006 and 3GPP TS 32.299	No	Yes	No	Used in the CCR according to Populated AVPs in the Used-Service-Unit AVP. The CDR represents this information in the OC-Session-Counter AVP
Service-Identifier	IETF RFC 4006	Yes	Yes	Yes	For Originating attempts the AVP has the value `1`. For Forwarded attempts the AVP has the value `2`. For Terminating attempts the AVP has the value `3`. For Network Initiated attempts the AVP has the value `4`. For Immediate Event Charging the AVP has the value `50`.
Rating-Group	IETF RFC 4006 and 3GPP TS 32.299 v12.11.0 section 7.1.10	No	Yes	No	This AVP is set according to Session Counters and the `ratingGroup` session state field.
Reporting-Reason	3GPP TS 32.299 v12.11.0 section 7.2.175	No	Yes	No
Trigger	3GPP TS 32.299 v12.11.0 section 7.2.235	No	No	No
PS-Furnish-Charging-Information	3GPP TS 32.299 v12.11.0 section 7.2.157	No	No	No
Refund-Information	3GPP TS 32.299 v12.11.0 section 7.2.171	No	No	No
AF-Correlation-Information	3GPP TS 32.299 v12.11.0 section 7.2.11	No	No	No
Envelope	3GPP TS 32.299 v12.11.0 section 7.2.59	No	No	No
Envelope-Reporting	3GPP TS 32.299 v12.11.0 section 7.2.61	No	No	No
Time-Quota-Mechanism	3GPP TS 32.299 v12.11.0 section 7.2.228	No	No	No
Service-Specific-Info	3GPP TS 32.299 v12.11.0 section 7.2.195	No	No	No
QoS-Information	3GPP TS 29.212	No	No	No

Requested-Service-Unit

IETF RFC 4006

No

Yes

No

Used in the CCR. The CDR represents this information in the OC-Session-Counter AVP

Used-Service-Unit

IETF RFC 4006 and 3GPP TS 32.299

No

Yes

No

Used in the CCR according to Populated AVPs in the Used-Service-Unit AVP. The CDR represents this information in the OC-Session-Counter AVP

Service-Identifier

IETF RFC 4006

Yes

For Originating attempts the AVP has the value 1. For Forwarded attempts the AVP has the value 2. For Terminating attempts the AVP has the value 3. For Network Initiated attempts the AVP has the value 4. For Immediate Event Charging the AVP has the value 50.

Rating-Group

IETF RFC 4006 and 3GPP TS 32.299 v12.11.0 section 7.1.10

No

Yes

No

This AVP is set according to Session Counters and the ratingGroup session state field.

Reporting-Reason

3GPP TS 32.299 v12.11.0 section 7.2.175

No

Yes

No

Trigger

3GPP TS 32.299 v12.11.0 section 7.2.235

No

PS-Furnish-Charging-Information

3GPP TS 32.299 v12.11.0 section 7.2.157

No

Refund-Information

3GPP TS 32.299 v12.11.0 section 7.2.171

No

AF-Correlation-Information

3GPP TS 32.299 v12.11.0 section 7.2.11

No

Envelope

3GPP TS 32.299 v12.11.0 section 7.2.59

No

Envelope-Reporting

3GPP TS 32.299 v12.11.0 section 7.2.61

No

Time-Quota-Mechanism

3GPP TS 32.299 v12.11.0 section 7.2.228

No

Service-Specific-Info

3GPP TS 32.299 v12.11.0 section 7.2.195

No

QoS-Information

3GPP TS 29.212

No

The BNF grammar for this AVP in 32.299 v12.11.0 is as follows:

<Multiple-Services-Credit-Control> ::=	   < AVP Header: 456 >

    [ Granted-Service-Unit ]   // not used in CCR
    [ Requested-Service-Unit ]
  * [ Used-Service-Unit ]
    [ Tariff-Change-Usage ]    // not used in 3GPP
  * [ Service-Identifier ]
    [ Rating-Group ]
  * [ G-S-U-Pool-Reference ]   // not used in CCR
    [ Validity-Time ]          // not used in CCR
    [ Result-Code ]            // not used in CCR
    [ Final-Unit-Indication ]  // not used in CCR
    [ Time-Quota-Threshold ]   // not used in CCR
    [ Volume-Quota-Threshold ] // not used in CCR
    [ Unit-Quota-Threshold ]   // not used in CCR
    [ Quota-Holding-Time ]     // not used in CCR
    [ Quota-Consumption-Time ] // not used in CCR
  * [ Reporting-Reason ]
    [ Trigger ]
    [ PS-Furnish-Charging-Information ]
    [ Refund-Information ]
  * [ AF-Correlation-Information]
  * [ Envelope ]
    [ Envelope-Reporting ]
    [ Time-Quota-Mechanism ]
  * [ Service-Specific-Info ]
    [ QoS-Information ]
  * [ AVP ]                    // not used in 3GPP

Populated AVPs in the Used-Service-Unit AVP

The Used-Service-Unit AVP is defined in IETF RFC 4006, and then its BNF is modified slightly in 3GPP TS 32.299 section 7.1.9.

AVP Name	Specification reference	Included in CDR	Included in CCR	Included in ACR	Comments
Reporting-Reason	3GPP TS 32.299 v12.11.0 section 7.2.175	No	No	No
Tariff-Change-Usage	IETF RFC 4006	No	No	No
CC-Time	IETF RFC 4006	No	Yes	No	Used by default as the unit type for SIP Sessions
CC-Money	IETF RFC 4006	No	No typically	No	Not used out-of-the-box for Sentinel SIP
CC-Total-Octets	IETF RFC 4006	No	Not typically	No	Not used out-of-the-box for Sentinel SIP
CC-Input-Octets	IETF RFC 4006	No	Not typically	No	Not used out-of-the-box for Sentinel SIP
CC-Output-Octets	IETF RFC 4006	No	Not typically	No	Not used out-of-the-box for Sentinel SIP

AVP Name

Specification reference

Included in CDR

Included in CCR

Included in ACR

Comments

Reporting-Reason

3GPP TS 32.299 v12.11.0 section 7.2.175

No

Tariff-Change-Usage

IETF RFC 4006

No

CC-Time

IETF RFC 4006

No

Yes

No

Used by default as the unit type for SIP Sessions

CC-Money

IETF RFC 4006

No

No typically

No

Not used out-of-the-box for Sentinel SIP

CC-Total-Octets

IETF RFC 4006

No

Not typically

No

Not used out-of-the-box for Sentinel SIP

CC-Input-Octets

IETF RFC 4006

No

Not typically

No

Not used out-of-the-box for Sentinel SIP

CC-Output-Octets

IETF RFC 4006

No

Not typically

No

Not used out-of-the-box for Sentinel SIP

The 3GPP definition (in v12.11.0) is

<Used-Service-Unit> ::=	   < AVP Header: 446 >
    [ Reporting-Reason ]
    [ Tariff-Change-Usage ]
    [ CC-Time ]
    [ CC-Money ]    // not used in 3GPP
    [ CC-Total-Octets ]
    [ CC-Input-Octets ]
    [ CC-Output-Octets ]
    [ CC-Service-Specific-Units ]
   *[ Event-Charging-TimeStamp ]
   *[ AVP ]        // not used in 3GPP

Populated AVPs in the Service-Information AVP

The Service-Information AVP is defined in 3GPP TS 32.299 v12.11.0. It is a grouped AVP. This table lists the AVPs grouped within Service-Information and how the product populates them.

AVP Name	Specification reference	Included in CDR	Included in CCR	Included in ACR	Comments
SMS-Information	32.299 v12.11.0 section 7.2.211	Yes	Yes	Yes	Refer to Populated AVPs in the SMS-Information AVP
MMTel-Information	32.299 v12.11.0 section 7.2.111	Yes	Yes	Yes	The Sentinel VoLTE product populates this AVP
Subscription-Id	IETF RFC 4006	Yes	No	Yes	3GPP TS 32.299 v12.11.0 states that it should be set on the Rf interface, not the Ro interface (see section 7.2.149)
AoC-Information	32.299 v12.11.0 section 7.2.15	No	No	No	Sentinel does not implement the advice of charge service out-of-the-box
PS-Information	32.299 v12.11.0 section 7.2.158	No	No	Yes	PS-Information AVP contains EPC layer information. It is only added in ACRs as a means of sending the IMEI in the User-Equipment-Information AVP.
IMS-Information	32.299 v12.11.0 section 7.2.77	Yes	Yes	Yes	See the IMS-Information table for further details
MMS-Information	32.299 v12.11.0 section 7.2.110	No	No	No	Sentinel does not implement any MMS node roles out-of-the-box
LCS-Information	32.299 v12.11.0 section 7.2.89	No	No	No
PoC-Information	32.299 v12.11.0 section 7.2.144	No	No	No	Sentinel does not implement the PoC service out-of-the-box
MBMS-Information	32.299 v12.11.0 section 7.2.99	No	No	No	Sentinel does not implement the MBMS service out-of-the-box
SMS-Information	32.299 v12.11.0 section 7.2.211	No	No	No	Sentinel does not implement the SMS service out-of-the-box
VCS-Information	32.299 v12.11.0 section 7.2.242A	No	No	No
MMTel-Information	32.299 v12.11.0 section 7.2.111	Yes	Yes	Yes
ProSe-Information	32.299 v12.11.0 section 7.2.154I	No	No	No
Service-Generic-Information	32.299 v12.11.0 section 7.2.191	No	No	No
IM-Information	32.299 v12.11.0 section 7.2.69	No	No	No	Sentinel does not implement IM services out-of-the-box
DCD-Information	32.299 v12.11.0 section 7.2.50	No	No	No

AVP Name

Specification reference

Included in CDR

Included in CCR

Included in ACR

Comments

SMS-Information

32.299 v12.11.0 section 7.2.211

Yes

Refer to Populated AVPs in the SMS-Information AVP

MMTel-Information

32.299 v12.11.0 section 7.2.111

Yes

The Sentinel VoLTE product populates this AVP

Subscription-Id

IETF RFC 4006

Yes

No

Yes

3GPP TS 32.299 v12.11.0 states that it should be set on the Rf interface, not the Ro interface (see section 7.2.149)

AoC-Information

32.299 v12.11.0 section 7.2.15

No

Sentinel does not implement the advice of charge service out-of-the-box

PS-Information

32.299 v12.11.0 section 7.2.158

No

Yes

PS-Information AVP contains EPC layer information. It is only added in ACRs as a means of sending the IMEI in the User-Equipment-Information AVP.

IMS-Information

32.299 v12.11.0 section 7.2.77

Yes

See the IMS-Information table for further details

MMS-Information

32.299 v12.11.0 section 7.2.110

No

Sentinel does not implement any MMS node roles out-of-the-box

LCS-Information

32.299 v12.11.0 section 7.2.89

No

PoC-Information

32.299 v12.11.0 section 7.2.144

No

Sentinel does not implement the PoC service out-of-the-box

MBMS-Information

32.299 v12.11.0 section 7.2.99

No

Sentinel does not implement the MBMS service out-of-the-box

SMS-Information

32.299 v12.11.0 section 7.2.211

No

Sentinel does not implement the SMS service out-of-the-box

VCS-Information

32.299 v12.11.0 section 7.2.242A

No

MMTel-Information

32.299 v12.11.0 section 7.2.111

Yes

ProSe-Information

32.299 v12.11.0 section 7.2.154I

No

Service-Generic-Information

32.299 v12.11.0 section 7.2.191

No

IM-Information

32.299 v12.11.0 section 7.2.69

No

Sentinel does not implement IM services out-of-the-box

DCD-Information

32.299 v12.11.0 section 7.2.50

No

The BNF for the AVP is defined in section 7.2.149. It is as follows:

Service-Information :: = 	< AVP Header: 873>

  * [ Subscription-Id ]
    [ AoC-Information ]
    [ PS-Information ]
    [ IMS-Information ]
    [ MMS-Information ]
    [ LCS-Information ]
    [ PoC-Information ]
    [ MBMS-Information ]
    [ SMS-Information ]
    [ VCS-Information ]
    [ MMTel-Information ]
    [ ProSe-Information ]
    [ Service-Generic-Information ]
    [ IM-Information ]
    [ DCD-Information ]

Populated AVPs in the SMS-Information AVP

The SMS-Information AVP is a grouped AVP. It is defined in 32.299 v12.11.0 section 7.2.211.

AVP Name Specification reference Included in CDR Included in CCR Comments

AVP Name	Specification reference	Included in CDR	Included in CCR	Comments
SMS-Node	32.299 v12.11.0 section 7.2.212	No	Yes	`IP_SM_GW(1)`
Client-Address	32.299 v12.11.0 section 7.2.41	No	Yes	Configured IPSMGW GT address
Data-Coding-Scheme	32.299 v12.11.0 section 7.2.49	No	Yes	The `dataCodingSheme` portion of the MT_ForwardSM’s `SMS-DELIVER` TPDU
SM-User-Data-Header	32.299 v12.11.0 section 7.2.210	No	Yes	The `userDataHeader` portion of the MT_ForwardSM’s `SMS-DELIVER` TPDU
SM-Status	32.299 v12.11.0 section 7.2.209	No	Yes	The single octet `TP-Status` field of the MT_ForwardSM’s `SMS-STATUS-REPORT` TPDU
SM-Discharge-Time	32.299 v12.11.0 section 7.2.206	No	Yes	The `TP-Discharge-Time` field of the MT_ForwardSM’s `SMS-STATUS-REPORT` TPDU
Originator-Interface	32.299 v12.11.0 section 7.2.126	No	Yes	Refer to Populated AVPs in the Originator-Interface AVP
Originator-Received-Address	32.299 v12.11.0 section 7.2.127	Yes	Yes	Refer to Populated AVPs in the Originator-Received-Address AVP
Recipient-Info	32.299 v12.11.0 section 7.2.168	Yes	Yes	Refer to Populated AVPs in the Recipient-Info AVP

SMS-Node

32.299 v12.11.0 section 7.2.212

No

Yes

IP_SM_GW(1)

Client-Address

32.299 v12.11.0 section 7.2.41

No

Yes

Configured IPSMGW GT address

Data-Coding-Scheme

32.299 v12.11.0 section 7.2.49

No

Yes

The dataCodingSheme portion of the MT_ForwardSM’s SMS-DELIVER TPDU

SM-User-Data-Header

32.299 v12.11.0 section 7.2.210

No

Yes

The userDataHeader portion of the MT_ForwardSM’s SMS-DELIVER TPDU

SM-Status

32.299 v12.11.0 section 7.2.209

No

Yes

The single octet TP-Status field of the MT_ForwardSM’s SMS-STATUS-REPORT TPDU

SM-Discharge-Time

32.299 v12.11.0 section 7.2.206

No

Yes

The TP-Discharge-Time field of the MT_ForwardSM’s SMS-STATUS-REPORT TPDU

Originator-Interface

32.299 v12.11.0 section 7.2.126

No

Yes

Refer to Populated AVPs in the Originator-Interface AVP

Originator-Received-Address

32.299 v12.11.0 section 7.2.127

Yes

Refer to Populated AVPs in the Originator-Received-Address AVP

Recipient-Info

32.299 v12.11.0 section 7.2.168

Yes

Refer to Populated AVPs in the Recipient-Info AVP

It has the following ABNF grammar:

SMS-Information :: =   < AVP Header: 2000>
    [ SMS-Node ]
    [ Client-Address ]
    [ Originator-SCCP-Address ]
    [ SMSC-Address]
    [ Data-Coding-Scheme ]
    [ SM-Discharge-Time ]
    [ SM-Message-Type ]
    [ Originator-Interface ]
    [ SM-Protocol-ID ]
    [ Reply-Path-Requested ]
    [ SM-Status ]
    [ SM-User-Data-Header ]
    [ Number-Of-Messages-Sent ]
  * [ Recipient-Info ]
    [ Originator-Received-Address ]
    [ SM-Service-Type ]

Populated AVPs in the Originator-Interface AVP

The Originator-Interface AVP is a grouped AVP. It is defined in 3GPP TS 32.299 v12.11.0 section 7.2.126.

AVP Name Specification reference Included in CDR Included in CCR Comments

AVP Name	Specification reference	Included in CDR	Included in CCR	Comments
Interface-Id	32.299 v12.11.0 section 7.2.71	Yes	Yes	`"SCCP Address=<SMSC SCCP Address>"`
Interface-Port	32.299 v12.11.0 section 7.2.72	No	Yes	`"SSN=<SMSC SCCP Address SSN>"`
Interface-Text	32.299 v12.11.0 section 7.2.73	No	Yes	`"IP-SM-GW/GSM MAP"`
Interface-Type	32.299 v12.11.0 section 7.2.74	No	Yes	`MOBILE_TERMINATING(2)`

Interface-Id

32.299 v12.11.0 section 7.2.71

Yes

"SCCP Address=<SMSC SCCP Address>"

Interface-Port

32.299 v12.11.0 section 7.2.72

No

Yes

"SSN=<SMSC SCCP Address SSN>"

Interface-Text

32.299 v12.11.0 section 7.2.73

No

Yes

"IP-SM-GW/GSM MAP"

Interface-Type

32.299 v12.11.0 section 7.2.74

No

Yes

MOBILE_TERMINATING(2)

It has the following ABNF grammar:

Originator-Interface: =   < AVP Header: 2009>
    [ Interface-Id ]
    [ Interface-Text ]
    [ Interface-Port ]
    [ Interface-Type ]

Populated AVPs in the Originator-Received-Address AVP

The Originator-Received-Address AVP is a grouped AVP. It is defined in 3GPP TS 32.299 v12.11.0 section 7.2.127.

AVP Name Specification reference Included in CDR Included in CCR Comments

AVP Name	Specification reference	Included in CDR	Included in CCR	Comments
Address-Type	32.299 v12.11.0 section 7.2.9	Yes	Yes	`MSISDN (1)`
Address-Data	32.299 v12.11.0 section 7.2.7	Yes	Yes	For MT case: The `OriginatingAddress` portion of the MT_ForwardSM’s `SMS-DELIVER` TPDU, For MO case: The MSISDN of the served user
Address-Domain	32.299 v12.11.0 section 7.2.8	No	No	Not used

Address-Type

32.299 v12.11.0 section 7.2.9

Yes

MSISDN (1)

Address-Data

32.299 v12.11.0 section 7.2.7

Yes

For MT case: The OriginatingAddress portion of the MT_ForwardSM’s SMS-DELIVER TPDU, For MO case: The MSISDN of the served user

Address-Domain

32.299 v12.11.0 section 7.2.8

No

Not used

It has the following ABNF grammar:

Originator-Received-Address ::= < AVP Header: 2027>
    [ Address-Type ]
    [ Address-Data ]
    [ Address-Domain ]

Populated AVPs in the Recipient-Info AVP

The Recipient-Info AVP is a grouped AVP. It is defined in 3GPP TS 32.299 v12.11.0 section 7.2.168.

AVP Name	Specification reference	Included in CDR	Included in CCR	Comments
Recipient-Address	32.299 v12.11.0 section 7.2.167	Yes	Yes	Refer to Populated AVPs in the Recipient-Address AVP

AVP Name

Specification reference

Included in CDR

Included in CCR

Comments

Recipient-Address

32.299 v12.11.0 section 7.2.167

Yes

Refer to Populated AVPs in the Recipient-Address AVP

It has the following ABNF grammar:

Recipient-Info :: = < AVP Header: 2026 >
    [ Destination-Interface ]
  * [ Recipient-Address ]
  * [ Recipient-Received-Address ]
    [ Recipient-SCCP-Address ]
    [ SM-Protocol-ID ]

Populated AVPs in the Recipient-Address AVP

The Recipient-Address AVP is a grouped AVP. It is defined in 3GPP TS 32.299 v12.11.0 section 7.2.167.

AVP Name Specification reference Included in CDR Included in CCR Comments

AVP Name	Specification reference	Included in CDR	Included in CCR	Comments
Address-Type	32.299 v12.11.0 section 7.2.9	Yes	Yes	In the MO Submission case this is always `MSISDN`
Address-Data	32.299 v12.11.0 section 7.2.7	Yes	Yes	In the MO Submission case this is taken from the `Address` part of the `DestinationAddress` portion of the MO_ForwardSM’s `SMS-SUBMIT` TPDU

Address-Type

32.299 v12.11.0 section 7.2.9

Yes

In the MO Submission case this is always MSISDN

Address-Data

32.299 v12.11.0 section 7.2.7

Yes

In the MO Submission case this is taken from the Address part of the DestinationAddress portion of the MO_ForwardSM’s SMS-SUBMIT TPDU

It has the following ABNF grammar:

Recipient-Address :: = 	< AVP Header: 1201 >
    [ Address-Type ]
    [ Address-Data ]
    [ Address-Domain ]
    [ Addressee-Type ]

Populated AVPs in the IMS-Information AVP

The IMS-Information AVP is defined in 3GPP TS 32.299 v12.11.0. It is a grouped AVP. This table lists the AVPs grouped within IMS-Information and how the product populates them.

AVP Name Specification reference Included in CDR Included in CCR Included in ACR Comments

AVP Name	Specification reference	Included in CDR	Included in CCR	Included in ACR	Comments
Event-Type	32.299 v12.11.0 section 7.2.65	Yes	Yes	Yes
Role-Of-Node	32.299 v12.11.0 section 7.2.177	Yes	Yes	Yes	Sessions with sescase of `orig` and `orig_cdiv` are in `ORIGINATING_ROLE`
Node-Functionality	32.299 v12.11.0 section 7.2.113	Yes	Yes	Yes	Set to value `6` as `AS`
User-Session-Id	32.299 v12.11.0 section 7.2.242	Yes	Yes	Yes	Set to the Call-Id for the initial request
Outgoing-Session-Id	32.299 v12.11.0 section 7.2.128A	No	No	No
Session-Priority	29.229	Yes	Yes	Yes	Set to value `2`
Calling-Party-Address	32.299 v12.11.0 section 7.2.33	Yes	Yes	Yes
Called-Party-Address	32.299 v12.11.0 section 7.2.32	Yes	Yes	Yes
Called-Asserted-Identity	32.299 v12.11.0 section 7.2.31	Yes	Yes	Yes
Number-Portability-Routing-Information	32.299 v12.11.0 section 7.2.120	No	No	No
Carrier-Select-Routing-Information	32.299 v12.11.0 section 7.2.34	No	No	No
Alternate-Charged-Party-Address	32.299 v12.11.0 section 7.2.12	No	No	No
Requested-Party-Address	32.299 v12.11.0 section 7.2.176	Yes	Yes	Yes	This field is only included if different from the `Called-Party-Address`
Associated-URI	32.299 v12.11.0 section 7.2.26	No	No	No
Application-Server-Information	32.299 v12.11.0 section 7.2.24	No	No	No
Inter-Operator-Identifier	32.299 v12.11.0 section 7.2.80	Yes	Yes	Yes
Transit-IOI-List	32.299 v12.11.0 section 7.2.233B	No	No	No
IMS-Charging-Identifier	32.299 v12.11.0 section 7.2.75	Yes	Yes	Yes
SDP-Session-Description	32.299 v12.11.0 section 7.2.184	Yes	Yes	Yes
SDP-Media-Component	32.299 v12.11.0 section 7.2.180	Yes	Yes	Yes
Served-Party-IP-Address	32.299 v12.11.0 section 7.2.187	No	No	No
Server-Capabilities	29.229	No	No	No
Trunk-Group-ID	32.299 v12.11.0 section 7.2.237	No	No	No
Bearer-Service	32.299 v12.11.0 section 7.2.30	No	No	No
Service-Id	32.299 v12.11.0 section 7.2.190	No	No	No
Service-Specific-Info	32.299 v12.11.0 section 7.2.195	No	No	No
Message-Body	32.299 v12.11.0 section 7.2.103	No	No	No
Cause-Code	32.299 v12.11.0 section 7.2.35	Yes	Yes	Yes
Reason-Header	32.299 v12.11.0 section 7.2.164A	No	No	No
Access-Network-Information	32.299 v12.11.0 section 7.2.1	Yes	Yes	Yes	The first value in the SIP P-Access-Network-Info header is included as the value for this AVP
Early-Media-Description	32.299 v12.11.0 section 7.2.58	Yes	Yes	Yes	The most recent Early Media offer/answer is included
IMS-Communication-Service-Identifier	32.299 v12.11.0 section 7.2.76	Yes	Yes	Yes
IMS-Application-Reference-Identifier	32.299 v12.11.0 section 7.2.74A	No	No	No
Online-Charging-Flag	32.299 v12.11.0 section 7.2.122	No	No	No
Real-Time-Tariff-Information	32.299 v12.11.0 section 7.2.164	No	No	No
Account-Expiration	32.299 v12.11.0 section 7.2.2	No	No	No
Initial-IMS-Charging-Identifier	32.299 v12.11.0 section 7.2.79A	No	No	No
NNI-Information	32.299 v12.11.0 section 7.2.112A	No	No	No
From-Address	32.299 v12.11.0 section 7.2.67A	No	No	No
IMS-Emergency-Indicator	32.299 v12.11.0 section 7.2.76A	No	No	No
IMS-Visited-Network-Identifier	32.299 v12.11.0 section 7.2.77A	No	No	No
Access-Transfer-Information	32.299 v12.11.0 section 7.2.1A	No	No	No
Related-IMS-Charging-Identifier	32.299 v12.11.0 section 7.2.171B	No	No	No
Related-IMS-Charging-Identifier-Node	32.299 v12.11.0 section 7.2.171C	No	No	No
Route-Header-Received	32.299 v12.11.0 section 7.2.177A	No	No	No
Route-Header-Transmitted	32.299 v12.11.0 section 7.2.177B	No	No	No
Instance-Id	32.299 v12.11.0 section 7.2.70A	No	No	No
TAD-Identifier	32.299 v12.11.0 section 7.2.219A	No	No	No

Event-Type

32.299 v12.11.0 section 7.2.65

Yes

Role-Of-Node

32.299 v12.11.0 section 7.2.177

Yes

Sessions with sescase of orig and orig_cdiv are in ORIGINATING_ROLE

Node-Functionality

32.299 v12.11.0 section 7.2.113

Yes

Set to value 6 as AS

User-Session-Id

32.299 v12.11.0 section 7.2.242

Yes

Set to the Call-Id for the initial request

Outgoing-Session-Id

32.299 v12.11.0 section 7.2.128A

No

Session-Priority

29.229

Yes

Set to value 2

Calling-Party-Address

32.299 v12.11.0 section 7.2.33

Yes

Called-Party-Address

32.299 v12.11.0 section 7.2.32

Yes

Called-Asserted-Identity

32.299 v12.11.0 section 7.2.31

Yes

Number-Portability-Routing-Information

32.299 v12.11.0 section 7.2.120

No

Carrier-Select-Routing-Information

32.299 v12.11.0 section 7.2.34

No

Alternate-Charged-Party-Address

32.299 v12.11.0 section 7.2.12

No

Requested-Party-Address

32.299 v12.11.0 section 7.2.176

Yes

This field is only included if different from the Called-Party-Address

Associated-URI

32.299 v12.11.0 section 7.2.26

No

Application-Server-Information

32.299 v12.11.0 section 7.2.24

No

Inter-Operator-Identifier

32.299 v12.11.0 section 7.2.80

Yes

Transit-IOI-List

32.299 v12.11.0 section 7.2.233B

No

IMS-Charging-Identifier

32.299 v12.11.0 section 7.2.75

Yes

SDP-Session-Description

32.299 v12.11.0 section 7.2.184

Yes

SDP-Media-Component

32.299 v12.11.0 section 7.2.180

Yes

Served-Party-IP-Address

32.299 v12.11.0 section 7.2.187

No

Server-Capabilities

29.229

No

Trunk-Group-ID

32.299 v12.11.0 section 7.2.237

No

Bearer-Service

32.299 v12.11.0 section 7.2.30

No

Service-Id

32.299 v12.11.0 section 7.2.190

No

Service-Specific-Info

32.299 v12.11.0 section 7.2.195

No

Message-Body

32.299 v12.11.0 section 7.2.103

No

Cause-Code

32.299 v12.11.0 section 7.2.35

Yes

Reason-Header

32.299 v12.11.0 section 7.2.164A

No

Access-Network-Information

32.299 v12.11.0 section 7.2.1

Yes

The first value in the SIP P-Access-Network-Info header is included as the value for this AVP

Early-Media-Description

32.299 v12.11.0 section 7.2.58

Yes

The most recent Early Media offer/answer is included

IMS-Communication-Service-Identifier

32.299 v12.11.0 section 7.2.76

Yes

IMS-Application-Reference-Identifier

32.299 v12.11.0 section 7.2.74A

No

Online-Charging-Flag

32.299 v12.11.0 section 7.2.122

No

Real-Time-Tariff-Information

32.299 v12.11.0 section 7.2.164

No

Account-Expiration

32.299 v12.11.0 section 7.2.2

No

Initial-IMS-Charging-Identifier

32.299 v12.11.0 section 7.2.79A

No

NNI-Information

32.299 v12.11.0 section 7.2.112A

No

From-Address

32.299 v12.11.0 section 7.2.67A

No

IMS-Emergency-Indicator

32.299 v12.11.0 section 7.2.76A

No

IMS-Visited-Network-Identifier

32.299 v12.11.0 section 7.2.77A

No

Access-Transfer-Information

32.299 v12.11.0 section 7.2.1A

No

Related-IMS-Charging-Identifier

32.299 v12.11.0 section 7.2.171B

No

Related-IMS-Charging-Identifier-Node

32.299 v12.11.0 section 7.2.171C

No

Route-Header-Received

32.299 v12.11.0 section 7.2.177A

No

Route-Header-Transmitted

32.299 v12.11.0 section 7.2.177B

No

Instance-Id

32.299 v12.11.0 section 7.2.70A

No

TAD-Identifier

32.299 v12.11.0 section 7.2.219A

No

The BNF syntax for the IMS-Information AVP according to 3GPP TS 32.299 v12.11.0 is as follows

    IMS-Information :: =        < AVP Header: 876>
    [ Event-Type ]
    [ Role-Of-Node ]
    { Node-Functionality }
    [ User-Session-Id ]
    [ Outgoing-Session-Id ]
    [ Session-Priority ]
 *  [ Calling-Party-Address ]
    [ Called-Party-Address ]
 *  [ Called-Asserted-Identity ]
    [ Number-Portability-Routing-Information ]
    [ Carrier-Select-Routing-Information ]
    [ Alternate-Charged-Party-Address ]
 *  [ Requested-Party-Address ]
 *  [ Associated-URI ]
    [ Time-Stamps ]
 *  [ Application-Server-Information ]
 *  [ Inter-Operator-Identifier ]
 *  [ Transit-IOI-List ]
    [ IMS-Charging-Identifier ]
 *  [ SDP-Session-Description ]
 *  [ SDP-Media-Component ]
    [ Served-Party-IP-Address ]
    [ Server-Capabilities ]
    [ Trunk-Group-ID ]
    [ Bearer-Service ]
    [ Service-Id ]
 *  [ Service-Specific-Info ]
 *  [ Message-Body ]
    [ Cause-Code ]
 *  [ Reason-Header ]
 *  [ Access-Network-Information ]
 *  [ Early-Media-Description ]
    [ IMS-Communication-Service-Identifier ]
    [ IMS-Application-Reference-Identifier ]
    [ Online-Charging-Flag ]
    [ Real-Time-Tariff-Information ]
    [ Account-Expiration ]
    [ Initial-IMS-Charging-Identifier ]
  * [ NNI-Information ]
    [ From-Address ]
    [ IMS-Emergency-Indicator ]
    [ IMS-Visited-Network-Identifier ]
 *  [ Access-Transfer-Information ]
    [ Related-IMS-Charging-Identifier ]
    [ Related-IMS-Charging-Identifier-Node ]
    [ Route-Header-Received ]
    [ Route-Header-Transmitted ]
    [ Instance-Id ]
    [TAD-Identifier]

Additional populated AVPs

This table lists additional standard AVPs that appear at the top level of a CDR or CCR instead of their standard place in a grouped AVP.

AVP Name	Specification reference	Included in CDR	Included in CCR	Comments
PDP-Address	32.299 v12.11.0 section 7.2.137	No	Yes	Destination IPCAN address of SIP message

AVP Name

Specification reference

Included in CDR

Included in CCR

Comments

PDP-Address

32.299 v12.11.0 section 7.2.137

No

Yes

Destination IPCAN address of SIP message

Populated OpenCloud AVPs

The population of OpenCloud AVPs is described here. The definition of OpenCloud AVPs is provided in Sentinel AVP definitions. ACRs are not used by Sentinel IPSMGW.

AVP Name	Specification reference	Included in CDR	Included in CCR	Included in ACR	Comments
OC-Sentinel-Selection-Key	OC-Sentinel-Selection-Key	Yes	No	Yes	n/a
OC-Play-Announcement-Id	OC-Play-Announcement-Id	Yes	No	Yes	n/a
OC-Call-Type	OC-Call-Type	Yes	No	Yes	Role-Of-Node AVP has similar meaning on the Ro interface
OC-Service-Type	OC-Service-Type	Yes	No	Yes	n/a
OC-Charging-Result	OC-Charging-Result	Yes	No	Yes
OC-OCS-Session-Id	OC-OCS-Session-Id	Yes	No	Yes	This is the session ID in Ro
OC-OCS-Session-Termination-Cause	OC-OCS-Session-Termination-Cause	Yes	No	Yes
OC-Sentinel-Error	OC-Sentinel-Error	Yes	No	Yes
OC-Charging-Instance	OC-Charging-Instance	Yes	No	Yes
OC-Event-Id	OC-Event-Id	Yes	No	Yes
OC-Call-Id	OC-Call-Id	Yes	No	Yes	The Ro Session Id optional part includes the SIP Call ID
OC-End-Session-Cause	OC-End-Session-Cause	Yes	No	Yes
OC-Start-Time	OC-Start-Time	Yes	No	Yes
OC-End-Time	OC-End-Time	Yes	No	Yes
OC-Session-Start-Time	OC-Session-Start-Time	Yes	No	Yes
OC-Session-Established-Time	OC-Session-Established-Time	Yes	No	Yes	Included if an INVITE session is answered
OC-Session-End-Time	OC-Session-End-Time	Yes	No	Yes
OC-Session-Counter	OC-Session-Counter	Yes	No	Yes
OC-Interim-CDR-Trigger	OC-Interim-CDR-Trigger	Yes	No	Yes
OC-Access-Network-MCC-MNC	OC-Access-Network-MCC-MNC	Yes	Yes	Yes
OC-Visited-Network-MCC-MNC	OC-Visited-Network-MCC-MNC	Yes	Yes	Yes
OC-IMSI-MCC-MNC	OC-IMSI-MCC-MNC	Yes	Yes	Yes
OC-SM-Message-Type	OC-SM-Message-Type	Yes	Yes	n/a	n/a
OC-Plan-Id	OC-Plan-Id	Yes	No	n/a	n/a
OC-Submit-Report-Type	OC-Submit-Report-Type	Yes	No	n/a	n/a
OC-MT-Correlated-Id	OC-MT-Correlated-Id	Yes	No	n/a	n/a
OC-MT-PS-Delivery-Result	OC-MT-PS-Delivery-Result	Yes	No	n/a	n/a
OC-MT-CS-Delivery-Result	OC-MT-CS-Delivery-Result	Yes	No	n/a	n/a
OC-IMPU	OC-IMPU	Yes	No	n/a	n/a

AVP Name

Specification reference

Included in CDR

Included in CCR

Included in ACR

Comments

OC-Sentinel-Selection-Key

Yes

No

Yes

n/a

OC-Play-Announcement-Id

Yes

No

Yes

n/a

OC-Call-Type

Yes

No

Yes

Role-Of-Node AVP has similar meaning on the Ro interface

OC-Service-Type

Yes

No

Yes

n/a

OC-Charging-Result

Yes

No

Yes

OC-OCS-Session-Id

Yes

No

Yes

This is the session ID in Ro

OC-OCS-Session-Termination-Cause

Yes

No

Yes

OC-Sentinel-Error

Yes

No

Yes

OC-Charging-Instance

Yes

No

Yes

OC-Event-Id

Yes

No

Yes

OC-Call-Id

Yes

No

Yes

The Ro Session Id optional part includes the SIP Call ID

OC-End-Session-Cause

Yes

No

Yes

OC-Start-Time

Yes

No

Yes

OC-End-Time

Yes

No

Yes

OC-Session-Start-Time

Yes

No

Yes

OC-Session-Established-Time

Yes

No

Yes

Included if an INVITE session is answered

OC-Session-End-Time

Yes

No

Yes

OC-Session-Counter

Yes

No

Yes

OC-Interim-CDR-Trigger

Yes

No

Yes

OC-Access-Network-MCC-MNC

Yes

OC-Visited-Network-MCC-MNC

Yes

OC-IMSI-MCC-MNC

Yes

OC-SM-Message-Type

Yes

n/a

OC-Plan-Id

Yes

No

n/a

OC-Submit-Report-Type

Yes

No

n/a

OC-MT-Correlated-Id

Yes

No

n/a

OC-MT-PS-Delivery-Result

Yes

No

n/a

OC-MT-CS-Delivery-Result

Yes

No

n/a

OC-IMPU

Yes

No

n/a

Charging Content AVPs

Detecting Online Charging

Populated AVPs in the Multiple-Services-Credit-Control AVP

Populated AVPs in the Used-Service-Unit AVP

Populated AVPs in the Service-Information AVP

Populated AVPs in the SMS-Information AVP

Populated AVPs in the Originator-Interface AVP

Populated AVPs in the Originator-Received-Address AVP

Populated AVPs in the Recipient-Info AVP

Populated AVPs in the Recipient-Address AVP

Populated AVPs in the IMS-Information AVP

Additional populated AVPs

Populated OpenCloud AVPs