5.1.3 Subsystem level CDR parameters
32.2983GPPCharging Data Record (CDR) parameter descriptionCharging managementRelease 18Telecommunication managementTS
5.1.3.0 General
This subclause contains the description of the CDR parameters that are specific to the subsystem level CDR types.
This comprises the CDR types from the CN IM subsystem (TS 32.260 [20]).
5.1.3.1 IMS CDR parameters
5.1.3.1.0 Introduction
This clause contains the description of each field of the IMS CDRs specified in TS 32.260 [20].
5.1.3.1.1 Access Correlation ID
This field holds the charging identifier of the access network.
It includes the following fields:
– GPRS Charging ID defined in clause 5.1.3.1.18
– Access Network Charging Identifier: Includes the charging ID for other access networks.
5.1.3.1.2 Access Network Information
Holds the content of one of the SIP P-header "P-Access-Network-Info". In SIP, as per RFC 7315 [404], the content of the "P-Access-Network-Info" header is known as the access-net-spec. When multiple access-net-spec values are transported in a single P-Access-Network-Info header in comma-separated format, then only one access-net-spec value is included.
For access types and access classes associated to 3GPP accesses:
– For GERAN access, the cgi-3gpp field contains the CGI;
– For UTRAN access, the utran-cell-id-3gpp field contains the LAI and CI, and the utran-sai-3gpp field contains the SAI;
– For E-UTRAN access, the utran-cell-id-3gpp field contains the TAI and ECGI;
– For NR access, the utran-cell-id-3gpp field contains the TAI and NCI.
The SIP "P-Access-Network-Info" header syntax is specified in TS 24.229 [210] clause 7.2A.4.
For access types and access classes associated to trusted WLAN access: the i-wlan-node-id field contains the BSSID, and when available, the operator-specific-GI field contains the Geographical Identifier.
For access types and access classes associated to untrusted WLAN access, the i-wlan-node-id field contains the BSSID, and UE local IP address, ePDG IP Address, and TCP source port, UDP source port are contained in corresponding dedicated fields.
5.1.3.1.2aA Access Transfer Type
This field indicates the type of access transfer performed for IMS service continuity, for instance PS-to-PS in case of SRVCC.
5.1.3.1.2A Additional Access Network Information
Holds the content of an additional SIP P-header "P-Access-Network-Info" when it is available. In SIP, as per RFC 7315 [404], the content of the "P-Access-Network-Info" header is known as the access-net-spec. When multiple access-net-spec values are transported in a single P-Access-Network-Info header in comma-separated format, then only one access-net-spec value is included.
5.1.3.1.3 Alternate Charged Party Address
Holds the address of an alternate charged party determined by an AS at IMS session initiation.
5.1.3.1.3A AoC Information
AoC information is the AoC related Charging information transferred to the CDF, as defined in TS 32.280 [21].
5.1.3.1.4 Application Provided Called Parties
Holds a list of the Called party address(es), if the address(es) are determined by an AS (SIP URL, E.164…).
5.1.3.1.5 Application Servers Information
This is a grouped CDR field containing the fields: "Application Server Involved", "Application Provided Called Parties" and “Status”.
5.1.3.1.6 Application Servers involved
Holds the ASs (if any) identified by the SIP URLs.
5.1.3.1.7 Void
5.1.3.1.8 Bearer Service
Holds the used bearer service for the PSTN leg.
5.1.3.1.9 Called Party Address
In the context of an end-to-end SIP transaction (except for SIP REGISTER and SIP SUBSCRIBE transactions) this field holds the address of the party (Public User ID or Public Service ID) to whom the SIP transaction is posted. The Called Party Address shall be populated with the SIP URI (according to RFC3261 [401]) or Tel URI (according to RFC3966 [402]) contained in the outgoing Request-URI of the request (e.g. after ENUM query or after AS interaction). Called Party Address could also be populated with an URN (according to RFC5031 [407]) for an emergency SIP session.
For a registration procedure this field holds the party (Public User ID) to be registered. In this case, the Called Party Address field is obtained from the "To" SIP header of the SIP request. For a subscription procedure this field holds the address of the resource for which the originator wants to receive notifications of change of states. In this case, the Called Party Address field is obtained from the outgoing Request-URI of the SIP request.
5.1.3.1.10 Carrier Select Routing
This item holds information on carrier select routing, received by S-CSCF during ENUM/DNS processes.
The parameter corresponds to the CarrierSelectRoutingInformation AVP.
5.1.3.1.11 Cause for Record Closing
This field contains a reason for the release of the CDR including the following:
- normal release: end of session;
- partial record generation: time (duration) limit, maximum number of changes in charging conditions (e.g. maximum number in ‘List of Message Bodies’ exceeded) or service change (e.g. change in media components, Access Transfer);
- abnormal termination;
- management intervention (request due to O&M reasons).
- CCF initiated record closure;
A more detailed reason may be found in the Service Reason Return Code field.
5.1.3.1.11A Cellular Network Information
Holds the content of one SIP header "Cellular-Network-Info". As per TS 24.299 [210], a User Agent (UA) supporting one or more cellular radio access technology (e.g. E-UTRAN) but using a non-cellular IP-CAN to access the IM CN subsystem can use this header field to relay information to its service provider about the radio cell identity of the cellular radio access network on which the UE most recently camped.
5.1.3.1.12 Content Disposition
This sub-field of Message Bodies holds the content disposition of the message body inside the SIP signalling, Content-disposition header field equal to "render", indicates that "the body part should be displayed or otherwise rendered to the user". Content disposition values are: session, render, inline, icon, alert, attachment, etc.
5.1.3.1.13 Content Length
This sub-field of Message Bodies holds the size of the data of a message body in bytes.
5.1.3.1.14 Content Type
This sub-field of Message Bodies holds the MIME type of the message body, Examples are: application/zip, image/gif, audio/mpeg, etc.
5.1.3.1.15 Event
The Event parameter holds the content of the "Event" header defined in RFC 3265 [403],
5.1.3.1.16 Expires
The Expires parameter holds the content of the "Expires" header.
5.1.3.1.16aA FE Identifier List
This parameter holds the FE Identifier List of the P-Charging-Vector header, as received in the FE-Identifier-List AVP as defined in TS 32.299 [50].
5.1.3.1.16A From Address
This field holds the information from the SIP From Header.
5.1.3.1.17 GGSN Address
This parameter holds the control plane IP address of the GGSN, PGW or SMF that handles one or more media component(s) of a IMS session. If GPRS is used to access the IMS, the GGSN address is used together with the GPRS charging ID as the access part of the charging correlation vector. The charging correlation vector is comprised of an access part and an IMS part, which is the IMS Charging Identifier. For further information regarding the composition of the charging correlation vector refer to the appropriate clause in TS 32.240 [1].
5.1.3.1.18 GPRS Charging ID
This parameter holds the charging identifier of GPRS, EPS and 5GS access network:
– GPRS charging ID (GCID) which is generated by the GGSN for a GPRS PDP context. There is a 1:1 relationship between the GCID and the PDP context. If GPRS is used to access the IMS, the GCID is used together with the GGSN address as the access part of the charging correlation vector that is comprised of an access part and an IMS part, which is the IMS Charging Identifier.
– Charging Id which is generated by the PGW for a bearer, as specified in TS 32.251 [11].
– Charging Id which is generated by the SMF for a PDU session, as specified in TS 32.255 [15].
For further information regarding the composition of the charging correlation vector refer to the appropriate clause in TS 32.240 [1].
5.1.3.1.18A Void
5.1.3.1.19 IMS Charging Identifier
This parameter holds the IMS charging identifier (ICID) as generated by the IMS node for the SIP session/transaction. The value of the ICID parameter is identical with the ‘icid-value’ parameter defined in TS 24.229 [210]. The ‘icid-value’ is a mandatory part of the P-Charging-Vector and coded as a text-based UTF-8 charset (as are all SIP messages). For further information regarding the composition and usage of the P-Charging-Vector refer to TS 32.260 [20], TS 24.229 [210] and RFC 7315 [404].
The ICID value is globally unique across all 3GPP IMS networks for a time period of at least one month, implying that neither the node that generated this ICID nor any other IMS node reuse this value before the uniqueness period expires. The one month minimum uniqueness period counts from the time of release of the ICID, i.e. the ICID value no longer being used. This can be achieved by using node specific information, e.g. high-granularity time information and/or topology/location information. The exact method how to achieve the uniqueness requirement is an implementation issue.
At each SIP session unrelated method, both initial and subsequent (e.g., REGISTER, NOTIFY, MESSAGE etc.), a new, session unrelated ICID is generated at the first IMS network element that processes the method. This ICID value is contained in the SIP request and SIP response of that SIP transaction and shall be valid for the duration of the transaction.
At each SIP session establishment a new session specific ICID is generated at the first IMS network element that processes the session-initiating SIP INVITE message. This ICID is then used in all subsequent SIP messages for that session (e.g., SIP 200 OK, SIP (RE-)INVITE, SIP BYE etc.) until the session is terminated.
5.1.3.1.20 IMS Communication Service Identifier
This parameter holds the IMS Communication Service Identifier (ICSI) as contained in the P-Asserted-Service header of a SIP request to identify an IMS Communication Service as defined in TS 24.229 [210].
5.1.3.1.20A IMS Emergency Indicator
This field indicates the IMS session or registration is an IMS emergency session or emergency registration. This field is missing if IMS session/registration is not detected as an IMS emergency session/registration.
5.1.3.1.20B IMS Visited Network Identifier
Holds the SIP P-header "P-Visited-Network-ID". with the value according to 3GPP TS 24.229 [210].
– For the roaming architecture for voice over IMS with local breakout, the value of IMS visited network identifier is a pre-provisioned string that identifies the network of the P-CSCF at the home network.
– For the roaming architecture for voice over IMS with home routed traffic, IMS visited network identifier is a string that identifies the visited network of the UE including an indication that the P-CSCF is located in the home network.
5.1.3.1.21 Incomplete CDR Indication
This field provides additional diagnostics when the CCF detects missing ACRs.
5.1.3.1.21A Initial IMS Charging Identifier
This parameter holds the Initial IMS charging identifier (ICID) as generated by the IMS node for the initial SIP session created for IMS service continuity.
5.1.3.1.21Aa Instance Id
An Instance Id is defined as a URN generated by the device that uniquely identifies a specific device amongst all other devices. The Instance Id is transported in the sip.instance feature tag in the Contact header of a SIP request associated with the served user.
5.1.3.1.21Aaa Inter-UE Transfer
This field indicates that Inter-UE transfer has been performed for IMS service continuity and present only in that case.
5.1.3.1.21B IP Realm Default Indication
This field indicates whether the IP realm used for the SDP media component is the Default IP realm or not.
5.1.3.1.21C ISUP Cause
When session is released via ISUP, this field indicates the reason the call was released.
5.1.3.1.21Ca List of Access Network Info Change
This group field may occur several times in the CDR and each occurrence holds information on subsequent changes in one or two SIP P-header(s) "P-Access-Network-Info" together with the time the location was acquired.
Each element of the list may include the following fields:
– Access Network Information;
– Additional Access Network Information;
– Access ChangeTime.
5.1.3.1.21D List of Access Transfer Information
This grouped field may occur several times in the CDR and each occurrence holds information on a particular access transfer. The field is present only if access transfer procedure has been performed for IMS service continuity.
Each element of the list represents an access transfer and may include the following fields:
– Access Transfer Type;
– Inter-UE Transfer;
– Access Network Information;
– Additional Access Network Information;
– Subscriber Equipment Number;
– Instance Id;
– Related IMS Charging Identifier;
– Related IMS Charging Identifier Generation Node;
– Access Transfer Time.
5.1.3.1.22 List of Associated URI
The list of non-barred public user identities (SIP URIs and/or Tel URIs) associated to the public user identity under registration. The list of identities is obtained from the P-Associated-URI header of a SIP 200 OK response to a SIP REGISTER request.
5.1.3.1.23 List of Called Asserted Identity
This field holds the address or addresses (SIP URI and/or Tel URI according to RFC 3261 [401] and RFC 3966 [402] respectively) of the party (Public User ID or Public Service ID) of the finally asserted called party.
These address/addresses are obtained from the P-Asserted-Identity SIP header field of the 2xx responses corresponding to a SIP request either initiating a dialog or a standalone transaction.
This field shall be present when the P-Asserted-Identity SIP header field is available in the SIP 2xx response. In case no P-Asserted-Identity is known, this list shall include one item (of type SIP URI) with the value "unknown".
5.1.3.1.23A List of Called Identity Changes
This field holds the set of terminating identity address changes after IMS session establishment and the associated time stamp for each.
These addresses are obtained from the From SIP header field of a SIP UPDATE request or SIP RE-INVITE request.
5.1.3.1.24 List of Calling Party Address
The address or addresses (Public User ID or Public Service ID) of the party requesting a service or initiating a session. This field may hold the SIP URI (according to RFC 3261 [401]), the Tel URI (according to RFC 3966 402]) or both the SIP URI and the Tel URI of the calling party. The address is obtained from the P-Asserted-Identity header of a non-REGISTER SIP request, either initiating a dialog or a standalone transaction.
5.1.3.1.25 List of Early SDP Media Components
This is a grouped field which may occur several times in one CDR. This field describes session, media parameters and timestamps related to media components set to active according to SDP signalling exchanged during a SIP session establishment and before the final successful or unsuccessful SIP ANSWER to the initial SIP INVITE message is received. Once a media component has been set to active, subsequent status changes shall also be registered.
This field applies only to SIP session related cases, but it may be present both in event CDRs (unsuccessful session establishment) and session CDRs (successful session establishment).
The List of Early SDP Media Components contains the following elements:
- SDP Offer Timestamp;
- SDP Answer Timestamp;
- SDP Media Components;
- Media Initiator flag;
- SDP Session Description.
These fields are described in the appropriate subclause.
5.1.3.1.26 List of Inter Operator Identifiers
This list holds the identification of the pair of originating network and terminating network if exchanged via SIP signalling, as recorded in the Inter Operator Identifier (IOI) AVP as described in TS 32.299 [50]. It may occur several times in one CDR. For further information on the IOI exchange via SIP signalling please refer to TS 24.229 [210].
5.1.3.1.27 List of Message Bodies
This grouped field comprising several sub-fields describing the data that may be conveyed end-to-end in the body of a SIP MESSAGE. Since several message bodies may be exchanged via SIP-signalling, this grouped field may occur several times.
The List of Message Bodies contains the following elements:
- Content Type;
- Content Disposition;
- Content Length;
- Originator.
They are described in the appropriate subclause. Message bodies with the "Content-Type" field set to application/sdp and the "Content-Disposition" field set to session are not included in the "Message Bodies" field.
5.1.3.1.27A List of NNI Information
This grouped field comprising several sub-fields holds information about the NNI used for interconnection and roaming. This field may occur more than once in a CDR if more NNI are involved e.g. when support of transit routing is collocated with the IBCF.
The List of NNI Information contains the following elements:
– Session Direction;
– NNI Type;
– Relationship Mode;
– Neighbour Node Address.
These field elements are described in the appropriate subclause.
5.1.3.1.28 List of SDP Media Components
This is a grouped field which may occur several times in one CDR and the content should be filled as described in TS 32.260 [20] clause 5.1.3.
The field is present only in a SIP session related case.
The List of SDP Media Components contains the following elements:
– SIP Request Timestamp;
– SIP Response Timestamp;
– SDP Media Components;
– Media Initiator flag;
– SDP Session Description.
– Media Initiator Party.
The Media Initiator Party is only used for PoC charging.
These field elements are described in the appropriate subclause.
5.1.3.1.28A List of Reason Header
This parameter contains the content of the Reason-header in the SIP BYE and SIP CANCEL, and may contain multiple entries if there are multiple Reason-headers within a SIP BYE or SIP CANCEL
5.1.3.1.28B Local GW Inserted Indication
This field indicates if the local GW (TrGW, IMS-AGW) is inserted or not for the SDP media component.
5.1.3.1.29 Local Record Sequence Number
This field includes a unique record number created by this node. The number is allocated sequentially for each partial CDR (or whole CDR) including all CDR types. The number is unique within the CCF.
The field can be used e.g. to identify missing records in post processing system.
5.1.3.1.30 Media Initiator Flag
This field indicates if the called party has requested the session modification and it is present only if the initiator was the called party.
5.1.3.1.31 Media Initiator Party
This field indicates initiating party who has requested the session modification in PoC charging.
5.1.3.1.31a MS Time Zone
This field contains the ‘Time Zone’ IE provided as part of the NetLoc enhancement for an ICS user as specified in TS 23.292 [229].
5.1.3.1.31aA MSC Address
This field contains the Recommendation E.164 [308] number assigned to the MSC that produced the record. For further details concerning the structure of MSC numbers see TS 23.003 [200].
5.1.3.1.31A Neighbour Node Address
This field holds the control plane IP address of the neighbouring network contact point that handles the service request in case of interconnection and roaming.
5.1.3.1.31B NNI Type
This field indicates whether the type of used NNI is non-roaming, roaming with loopback routing, or roaming without loopback routing. The loopback indication is either sent by the S-CSCF in forward direction within the initial SIP request or sent by TRF in backward direction and received by the ATCF, AS and P-CSCF in the final SIP response.
5.1.3.1.31C Void
5.1.3.1.32 Node Address
This item holds the address of the node providing the information for the CDR. This may either be the IP address or the FQDN of the IMS node generating the accounting data. This parameter corresponds to the Origin-Host AVP.
5.1.3.1.33 Number Portability Routing
This item holds information on number portability routing, received by S-CSCF during ENUM/DNS processes.
The parameter corresponds to the NumberPortabilityRoutingInformation AVP.
5.1.3.1.33A Void
5.1.3.1.34 Online Charging Flag
This field indicates the Online Charging Request was sent based on the provided ECF address from the SIP P-header "P-Charging-Function-Addresses". The parameter corresponds to the Online-Charging-Flag AVP.
NOTE: No proof that online charging action has been taken
5.1.3.1.35 Originator
This sub-field of the "List of Message Bodies" indicates the originating party of the message body.
5.1.3.1.35A Outgoing Session ID
For a SIP session the Session-ID contains the SIP CALL ID as defined in the Session Initiation Protocol RFC 3261 [401]. When the AS acts as B2BUA, the outgoing session is identified by the Outgoing Session ID which contains the SIP CALL ID.
5.1.3.1.36 Private User ID
Holds the used Network Access Identifier of the served party according to RFC 2486 [405]. This parameter corresponds to the User-Name AVP.
5.1.3.1.37 Real Time Tariff Information
This is a field containing the real time tariff information that may be exchanged in the SIP transaction, encoded in a XML body as described in the TS 29.658 [225]. The RTTI information may be captured in the charging information and it is operator configurable as whether it is used in its original XML format or mapped on a detailed structure of parameters. The RTTI information XML schema in XML format is given in the TS 29.658 [225]. The Tariff Information structure of parameters is provided in the TS 32.280 [40].
The Real Time Tariff Information contains one of the following elements:
- Tariff XML;
- Tariff Information.
These field elements are described in the appropriate subclause.
5.1.3.1.38 Record Closure Time
A Time stamp reflecting the time the CCF closed the record.
5.1.3.1.39 Record Extensions
A set of operator/manufacturer specific extensions to the record, conditioned upon existence of an extension.
5.1.3.1.40 Record Opening Time
A time stamp reflecting the time the CCF opened this record. Present only in SIP session related case.
5.1.3.1.41 Record Sequence Number
This field contains a running sequence number employed to link the partial records generated by the CCF for a particular session (characterised with the same Charging ID and GGSN address pair). The Record Sequence Number is not present if the record is the only one produced in the CCF for a session. The Record Sequence Number starts from one (1).
5.1.3.1.42 Record Type
Identifies the type of record. The parameter is derived from the Node-Functionality AVP, defined in TS 32.299 [40].
5.1.3.1.42A Related IMS Charging Identifier
This field holds the Related IMS Charging Identifier when the session is the target access leg in an SRVCC handover. The Related IMS Charging Identifier contains the IMS charging identifier generated for the source access leg.
5.1.3.1.42B Related IMS Charging Identifier Generation Node
This field holds the identifier of the node that generated the Related IMS charging identifier.
5.1.3.1.42A Relationship Mode
This field indicates whether the other functional entity (e.g. contact point of the neighbouring network) is regarded as part of the same trust domain.
5.1.3.1.43 Requested Party Address
This field holds the address of the party (Public User ID or Public Service ID) to whom the SIP transaction was originally posted. The Requested Party Address shall be populated with the SIP URI or Tel URI (according to RFC 3261 [401] and RFC 3966 [402] respectively) contained in the incoming Request-URI of the request. Requested Party Address could also be populated with an URN (according to RFC5031 [407]) for an emergency SIP session.
This field is only present if different from the Called Party Address parameter.
5.1.3.1.44 Retransmission
This parameter, when present, indicates that information from retransmitted Diameter ACRs has been used in this CDR.
5.1.3.1.45 Role of Node
The field indicates whether the IMS node (except MRFC) is serving the Originating or the Terminating party. The role can be:
– Originating (IMS node serving the calling party);
– Terminating (IMS node serving the called party).
5.1.3.1.45A Route header received
This field contains the information in the topmost route header in a received initial SIP INVITE and non-session related SIP MESSAGE request.
5.1.3.1.45B Route header transmitted
This field contains the information in the route header representing the destination in a transmitted initial SIP INVITE and non-session SIP MESSAGE request.
5.1.3.1.46 SDP Answer Timestamp
This parameter contains the time of the response to the SDP Offer.
5.1.3.1.47 SDP Media Components
This is a grouped field comprising several sub-fields associated with one media component. Since several media components may exist for a session in parallel these sub-fields may occur several times (as much times as media are involved in the session). The sub-fields are present if medium (media) is (are) available in the SDP data which is provided in the ACR received from the IMS node.
The SDP media component contains the following elements:
– SDP media name;
– SDP media description;
– Access Correlation ID;
– Local GW Inserted indication;
– IP Realm Default indication;
– Transcoder Inserted indication.
These field elements are described in the appropriate subclause.
5.1.3.1.48 SDP Media Description:
This field holds the attributes of the media as available in the SDP data tagged with "i=", "c=","b=","k=", "a=". Only the attribute lines relevant for charging are recorded. To be recorded "SDP lines" shall be recorded in separate "SDP Media Description" fields, thus multiple occurrence of this field is possible. Always complete "SDP lines" are recorded per field.
This field corresponds to the SDP-Media-Description AVP.
Example: "c=IN IP4 134.134.157.81"
For further information on SDP please refer to RFC4566 [406].
Note: session unrelated procedures typically do not contain SDP data.
5.1.3.1.49 SDP Media Name
This field holds the name of the media as available in the SDP data tagged with "m=". Always the complete "SDP line" is recorded.
This field corresponds to the SDP-Media-Name AVP.
Example: "m=video 51372 RTP/AVP 31"
For further information on SDP please refer to RFC 4566 [406].
5.1.3.1.50 SDP Offer Timestamp
This parameter contains the time of the SDP Offer.
5.1.3.1.51 SDP Session Description
Holds the Session portion of the SDP data exchanged between the User Agents if available in the SIP transaction.
This field holds the attributes of the media as available in the session related part of the SDP data tagged with "c=" and "a=" (multiple occurrence possible). Only attribute lines relevant for charging are recorded.
The content of this field corresponds to the SDP-Session-Description AVP of the ACR message.
Note: session unrelated procedures typically do not contain SDP data.
5.1.3.1.52 SDP Type
This field identifies if the SDP media component was an SDP offer or an SDP answer.
5.1.3.1.53 Served Party IP Address
This field contains the IP address of either the calling or called party, depending on whether the P-CSCF is in touch with the calling or called network.
5.1.3.1.54 Service Delivery End Time Stamp
This field records the time at which the service delivery was terminated. It is Present only in SIP session related case.
The content of this field corresponds to the SIP-Request-Timestamp AVP of a received ACR[Stop] message indicating a session termination.
5.1.3.1.54A Service Delivery End Time Stamp Fraction
This parameter contains the milliseconds fraction in relation to Service Delivery End Time Stamp.
5.1.3.1.55 Service Delivery Start Time Stamp
This field holds the time stamp reflecting either:
– a successful session set-up: this field holds the start time of a service delivery (session related service)
– a delivery of a session unrelated service: the service delivery time stamp
– an unsuccessful session set-up and an unsuccessful session unrelated request: this field holds the time the network entity forwards the unsuccessful indication (SIP RESPONSE with error codes 3xx, 4xx, 5xx) towards the requesting User direction.
The content of this field corresponds to the SIP-Response-Timestamp AVP.
For partial CDRs this field remains unchanged.
5.1.3.1.55A Service Delivery Start Time Stamp Fraction
This parameter contains the milliseconds fraction in relation to Service Delivery Start Time Stamp.
5.1.3.1.56 Service ID
This field identifies the service the MRFC is hosting. For conferences the conference ID is used here.
5.1.3.1.57 Service Reason Return Code
Provides the returned cause code for the service request (both successful and failure). This parameter corresponds to the Cause-Code AVP.
5.1.3.1.58 Service Request Timestamp
This field contains the time stamp which indicates the time at which the service was requested (SIP Request" message) and is present for session related and session unrelated procedures. The content of this item is derived from the SIP-Request-Timestamp AVP. If the SIP-Request-Timestamp AVP is not supplied by the network entity this field is not present.
For partial CDRs this field remains unchanged.
This field is present for unsuccessful service requests if the ACR message includes the SIP-Request-Timestamp AVP.
5.1.3.1.58A Service Request Timestamp Fraction
This parameter contains the milliseconds fraction in relation to Service Request Timestamp.
5.1.3.1.58B Session Direction
This field indicates whether the NNI is used for an inbound or outbound service request on the control plane in case of interconnection and roaming.
5.1.3.1.59 Session ID
The Session identification. For a SIP session the Session-ID contains the SIP CALL ID as defined in the Session Initiation Protocol RFC 3261 [401]. When the AS acts as B2BUA, the incoming Session-ID leg is covered.
5.1.3.1.60 Session Priority
This field contains the priority level of the session. The value of the parameter is derived from Resource-Priority header field and the rules for the translation depend on operator policy described in TS 24.229[210].
5.1.3.1.61 SIP Method
Specifies the SIP-method for which the CDR is generated. Only available in session unrelated cases.
5.1.3.1.62 SIP Request Timestamp
This parameter contains the time of the SIP request (usually a (Re)Invite).
5.1.3.1.63 SIP Request Timestamp Fraction
This parameter contains the milliseconds fraction in relation to the SIP Request Timestamp.
5.1.3.1.64 SIP Response Timestamp
This parameter contains the time of the response to the SIP request. If an SDP is exchanged via SIP messages, then this parameter contains appropriately the time of SIP 200 OK acknowledging an SIP INVITE or of SIP ACK including a SDP ANSWER.
5.1.3.1.65 SIP Response Timestamp Fraction
This parameter contains the milliseconds fraction in relation to the SIP Response Timestamp.
5.1.3.1.66 S-CSCF Information
This field contains Information related to the serving CSCF, e.g. the S-CSCF capabilities upon registration event or the S-CSCF address upon the session establishment event. This field is derived from the Server-Capabilities AVP if present in the ACR received from the I-CSCF.
5.1.3.1.66A Status
Holds the abnormal status information of specific ASs (if any) when AS(s) respond 4xx/5xx or time out to S-CSCF during an IMS session.
5.1.3.1.66B TAD Identifier
This field indicates the type of access network (CS or PS) through which the session shall be terminated.
5.1.3.1.67 Tariff Information
This field holds the tariff mapped in the Tariff Information structure. The corresponding structure of the Tariff Information can be found in the TS 32.299 [50]. The formatting from real time tariff information to Tariff Information structure is described in TS 32 280 [40].
5.1.3.1.68 Tariff XML
This field holds the tariff formatted in the XML schema as specified in the TS 29.658 [225].
5.1.3.1.68A Transcoder Inserted Indication
This field indicates if a transcoder is inserted or not for the SDP media component.
5.1.3.1.68B Transit IOI List
This parameter holds the Transit-IOI List of the P-Charging-Vector header, as recorded in the Transit-IOI-List AVP as defined in TS 32.299 [50]. Multiple occurrences of this field, shall be in chronological order, i.e. the value in the SIP request is listed first. If only a value for the SIP response is available, the Transit IOI List for the SIP request shall be included with the value "unknown". For further information on the Transit IOI exchange via SIP signalling please refer to TS 24.229 [210].
5.1.3.1.69 Trunk Group ID Incoming/Outgoing
Contains the outgoing trunk group ID for an outgoing session/call or the incoming trunk group ID for an incoming session/call.
5.1.3.1.69A User Location Information
This field contains the User Location Information using PCC mechanisms as specified in TS 23.203 [203] and TS 23.503 [246] or the location retrieval via Sh interface by AS as specified in TS 29.328 [242].
5.1.3.1.70 VLR Number
This field contains the Recommendation E.164 [308] number assigned to the VLR that produced the record. For further details concerning the structure of VLR numbers see TS 23.003 [200].