The AVPs used by Sentinel VoLTE in the Accounting request are described.

Sentinel VoLTE SIP Service population of Accounting Request

The Accounting Request message is defined according to IETF RFC 6733, and the diameter Rf interface is defined in 3GPP TS 32.299. Sentinel products use the definition in 3GPP TS 32.299 v12.11.0 for ACR.

This table indicates the top-level AVPs inside an ACR request and how the Sentinel SIP service populates them.

AVP Name Specification reference Included in CDR Included in ACR Comments

Service-Context-Id

IETF RFC 4006 and refined by 3GPP TS 32.299 v12.11.0 section 7.1.12

Yes

Yes

For MMTel the value is set to 12.32275@3gpp.org. For SCC the value is set to 12.32260@3gpp.org, even though SCC does not perform online charging. These values include the "Release", "service-context" and "domain" portions. For the Sentinel SS7 service the value is set to session@opencloud.com.

User-Name

IETF RFC 6733

Yes

Yes

Set in Sentinel VoLTE to the IMS Private Identifier for the served user if the served user is IMS registered.

Session-Id

IETF RFC 6733

Yes

Yes

The Session-Id optional part is set to the Call-ID of the initial request for the Session

Origin-Host

IETF RFC 6733

No

Yes

Resource Adaptor entity configuration defines the value to be used for this AVP

Origin-Realm

IETF RFC 6733

No

Yes

Resource Adaptor entity configuration defines the value to be used for this AVP

Destination-Realm

IETF RFC 6733

No

Yes

This is set in Sentinel configuration, when selecting a CDF to use for the Session

Accounting-Record-Type

IETF RFC 6733

Yes

Yes

Accounting-Record-Number

IETF RFC 6733

Yes

Yes

Acct-Application-Id

IETF RFC 6733

No

Yes

Set to the value 4L

Vendor-Specific-Application-Id

IETF RFC 6733

No

No

## in volte documentation

User-Name

IETF RFC 6733

Yes

Yes

This contains the Private Id from registration data

Destination-Host

IETF RFC 6733

No

No

Accounting-Sub-Session-Id

IETF RFC 6733

No

No

Acct-Session-Id

IETF RFC 6733

No

No

Acct-Multi-Session-Id

IETF RFC 6733

No

No

Acct-Interim-Interval

IETF RFC 6733

Yes

Yes

Accounting-Realtime-Required

IETF RFC 6733

No

No

Origin-State-Id

IETF RFC 6733

No

No

Event-Timestamp

IETF RFC 6733

No

Yes

Proxy-Info

IETF RFC 6733

No

No

Route-Record

IETF RFC 6733

No

No

## in volte documentation

Service-Context-Id

IETF RFC 4006

Yes

Yes

Service-Information

3GPP TS 32.299

No

Yes

Refer to Populated AVPs in the Service-Information AVP

The BNF for the ACR message according to 32.299 v12.11.0 section 6.2.2 is

<ACR> ::= < Diameter Header: 271, REQ, PXY >
           < Session-Id >
           { Origin-Host }
           { Origin-Realm }
           { Destination-Realm }
           { Accounting-Record-Type }
           { Accounting-Record-Number }
           [ Acct-Application-Id ]
           [ Vendor-Specific-Application-Id ]   // not used in 3GPP
           [ User-Name ]
           [ Destination-Host ]
           [ Accounting-Sub-Session-Id ]        // not used in 3GPP
           [ Acct-Session-Id ]                  // not used in 3GPP
           [ Acct-Multi-Session-Id ]            // not used in 3GPP
           [ Acct-Interim-Interval ]
           [ Accounting-Realtime-Required ]     // not used in 3GPP
           [ Origin-State-Id ]
           [ Event-Timestamp ]
         * [ Proxy-Info ]
         * [ Route-Record ]
           [ Service-Context-Id ]
           [ Service-Information ]
         * [ AVP ]
Previous page Next page
Sentinel VoLTE Version 4.0.0