1. Accounting Guide
  2. CDR Attribute Reference
  3. Oracle RADIUS VSAs

Oracle RADIUS VSAs

Oracle’s vendor identification number is 9148. This number refers to the 4-octet VSA Vendor-ID field. The high-order octet is 0 and the low-order 3 octets are the SMI Network Management Private Enterprise Code of the Vendor in network byte order, defined in the Assigned Numbers RFC (http://www.faqs.org/rfcs/rfc1700.html; Reynolds, J. and J. Postel, Assigned Numbers, STD 2, RFC 1700, October 1994).

The table in this section is a dictionary of Oracle’s accounting VSAs. You can use this information to translate the Oracle VSAs in SBC RADIUS messages into human-readable form. Oracle maintains VSA dictionary definition files for the most popular RADIUS distributions; ask your Oracle account representative for details.

Grouped according to attribute function, this table contains the following sections:

  • General Flow Attributes—Overall traits of the media flow, these attributes appear in all CDRs regardless of the session’s protocol; these attribute fields are only populated if there are media flows
  • Inbound Flow Attributes—Detailed traits of the inbound media flow (including realm, remote IP address and port, and local IP address and port); these attribute fields are only populated if there are media flows
  • Outbound Flow Attributes—Detailed traits of the outbound media flow (including realm, remote IP address and port, and local IP address and port); these attribute field are only populated if there are media flows
  • Session Attributes—Information about the protocol type, ingress and egress realms used, and an identifier that links the H.323 and SIP legs of a call requiring IWF. In addition, SIP reporting includes specific information for Short Message Service (SMS) traffic, defined within the SBC as message events reported using CDR STOP records. SIP reporting also includes detail on VoLTE sessions to support management within IMS constructs.
  • QoS Attributes—RADIUS call records are instantiated by individual signaling applications on the SBC. The SBC writes the following additional parameters to the call record for QoS (Quality of Service):
    • MSRP Total Packets
    • MSRP Total Octets
    • RTP Lost packets
    • RTP Jitter
    • RTP Maximum Jitter
    • RTCP Lost packets
    • RTCP Jitter
    • RTCP Latency
    • RTCP Maximum Latency
    • RTP Total Packets
    • RTP Total Octets

    Only RADIUS Stop records contain QoS information. For non-QoS calls, the attributes appear in the record, but their values are always be zero (0). When you review the list of QoS VSAs, please note that “calling” in the attribute name means the information is sent by the calling party and called in the attribute name means the information is sent by the called party.

Examples of how this information appears in CDRs appears in Appendix B of this guide. Please note that the contents of Interim-Update messages do not depend on what events cause a Start message to be generated.

R-Factor and MOS

The SBC reports R-Factor and MOS data for the calling and called segments at the end of a session. This information appears in RADIUS CDRs, and in the Oracle VSA dictionary:

  • Acme-Calling-R-Factor (151)
  • Acme-Calling-MOS (152)
  • Acme-Called-R-Factor (153)
  • Acme-Called-MOS (154)

    Note:

    These values are reported as * 100 in order to appear as integers.

Media Flow Attributes

The SBC records media flow attributes in RADIUS CDRs, and there can be multiple flows per session. In order to distinguish between the two flows that appear for a basic session (forward and reverse), the SBC supports unique media flow attribute names.

The term flow-set represents a pair of media flows, where one is the forward flow and one is the reverse. The flow attributes described in the table below have the designation FS1 or FS2, which identifies it as either the first or the second flow-set. In addition, all non-QoS attributes have a direction indicator: F for forward, and R for reverse.

MSRP Attributes

An additional group of MSRP media flow attributes are captured in the Acme-Extended-Attributes VSA. See Oracle RADIUS Acme-Extended-Attributes VSAs for information on configuring them.

Attribute Name Attribute Description Attribute Value Attribute Value Type Messages
Acme-CDR-Sequence-Number Sequence number (that increases by 1) the SBC generates; recorded in each CDR. 59 integer Start

Interim-Update

Stop

Acme-Intermediate-Time Time interval at which periodic interim records are generated during a call. 63 string Interim-Update
Acme-Local-Time-Zone Local GMT/UTC time zone that is provisioned on the SBC. 57 string Start

Interim-Update

Stop

Acme-Firmware-Version Current software version running on the SBC. 56 string Start

Interim-Update

Stop

This table lists and describes general flow attributes.
Attribute Name Attribute Description Attribute Value Attribute Value Type Messages
Acme-FlowID_FS1_F Unique identifier for every media flow processed by the SBC, flow-set 1 forward direction.

This VSA always prefaces other flow information.

1 string Start

Interim-Update

Stop

Acme-FlowID_FS1_R Unique identifier for every media flow processed by the SBC, flow-set 1 reverse direction.

This VSA always prefaces other flow information.

78 string Start

Interim-Update

Stop

Acme-FlowID_FS2_F Unique identifier for every media flow processed by the SBC, flow-set 2 forward direction.

This VSA always prefaces other flow information.

90 string Start

Interim-Update

Stop

Acme-FlowID_FS2_R Unique identifier for every media flow processed by the SBC, flow-set 2 reverse direction.

This VSA always prefaces other flow information.

112 string Start

Interim-Update

Stop

Acme-FlowType_FS1_F Codec that describes the flow, flow-set 1 forward direction: PCMU, PCMA, G722, G726, G723, G728, G729, H261, H263, T38. 2 string Start

Interim-Update

Stop

Acme-FlowType_FS1_R Codec that describes the flow, flow-set 1 reverse direction: PCMU, PCMA, G726, G723, G728, G729, H261, H263, T38. 79 string Start

Interim-Update

Stop

Acme-FlowType_FS2_F Codec that describes the flow, flow-set 2 forward direction: PCMU, PCMA, G726, G723, G728, G729, H261, H263, T38. 91 string Start

Interim-Update

Stop

Acme-FlowType_FS2_R Codec that describes the flow, flow-set 2 reverse direction: PCMU, PCMA, G726, G723, G728, G729, H261, H263, T38. 113 string Start

Interim-Update

Stop

This table describes inbound flow attributes.
Attribute Name Attribute Description Attribute Value Attribute Value Type Messages
Acme-Flow-In-Realm_FS1_F Inbound realm identifier for flow-set 1, forward direction. 10 string Start

Interim-Update

Stop

Acme-Flow-In-Realm_FS1_R Inbound realm identifier for flow-set 1, reverse direction. 80 string Start

Interim-Update

Stop

Acme-Flow-In-Realm_FS2_F Inbound realm identifier for flow-set 2, forward direction. 92 string Start

Interim-Update

Stop

Acme-Flow-In-Realm_FS2_R Inbound realm identifier for flow-set 2, reverse direction. 114 string Start

Interim-Update

Stop

Acme-Flow-In-Src-Addr_FS1_F Inbound source address (remote) information for flow-set 1, forward direction. 11 IP address Start

Interim-Update

Stop

Acme-Flow-In-Src-Addr_FS1_R Inbound source address (remote) information for flow-set 1, reverse direction. 81 IP address Start

Interim-Update

Stop

Acme-Flow-In-Src-Addr_FS2_F Inbound source address (remote) information for flow-set 2, forward direction. 93 IP address Start

Interim-Update

Stop

Acme-Flow-In-Src-Addr_FS2_R Inbound source address (remote) information for flow-set 2, reverse direction. 115 IP address Start

Interim-Update

Stop

Acme-Flow-In-Src-Port_FS1_F Inbound source (remote) port information for flow-set 1, forward direction. 12 integer Start

Interim-Update

Stop

Acme-Flow-In-Src-Port_FS1_R Inbound source (remote) port information for flow-set 1, reverse direction. 82 integer Start

Interim-Update

Stop

Acme-Flow-In-Src-Port_FS2_F Inbound source (remote) port information for flow-set 2, forward direction. 94 integer Start

Interim-Update

Stop

Acme-Flow-In-Src-Port_FS2_R Inbound source (remote) port information for flow-set 2, reverse direction. 116 integer Start

Interim-Update

Stop

Acme-Flow-In-Dst-Addr_FS1_F Inbound destination (local) address information (the IPv4 address field value of the steering pool configuration) for flow-set 1, forward direction. 13 IP address Start

Interim-Update

Stop

Acme-Flow-In-Dst-Addr_FS1_R Inbound destination (local) address information (the IPv4 address field value of the steering pool configuration) for flow-set 1, reverse direction. 83 IP address Start

Interim-Update

Stop

Acme-Flow-In-Dst-Addr_FS2_F Inbound destination (local) address information (the IPv4 address field value of the steering pool configuration) for flow-set 2, forward direction. 95 IP address Start

Interim-Update

Stop

Acme-Flow-In-Dst-Addr_FS2_R Inbound destination (local) address information (the IPv4 address field value of the steering pool configuration) for flow-set 2, reverse direction. 117 IP address Start

Interim-Update

Stop

Acme-Flow-In-Dst-Port_FS1_F Inbound destination (local) port information (a port in the range between the start port and end port field values of the steering pool configuration) for flow-set 1, forward direction. 14 integer Start

Interim-Update

Stop

Acme-Flow-In-Dst-Port_FS1_R Inbound destination (local) port information (a port in the range between the start port and end port field values of the steering pool configuration) for flow-set 1, reverse direction. 84 integer Start

Interim-Update

Stop

Acme-Flow-In-Dst-Port_FS2_F Inbound destination (local) port information (a port in the range between the start port and end port field values of the steering pool configuration) for flow-set 2, forward direction. 96 integer Start

Interim-Update

Stop

Acme-Flow-In-Dst-Port_FS2_R Inbound destination (local) port information (a port in the range between the start port and end port field values of the steering pool configuration) for flow-set 2, reverse direction. 118 integer Start

Interim-Update

Stop

This table lists and describes outbound flow attributes.
Attribute Name Attribute Description Attribute Value Attribute Value Type Messages
Acme-Flow-Out-Realm_FS1_F Outbound realm identifier for flow-set 1, forward direction. 20 string Start

Interim-Update

Stop

Acme-Flow-Out-Realm_FS1_R Outbound realm identifier for flow-set 1, reverse direction. 85 string Start

Interim-Update

Stop

Acme-Flow-Out-Realm_FS2_F Outbound realm identifier for flow-set 2, forward direction. 97 string Start

Interim-Update

Stop

Acme-Flow-Out-Realm_FS2_R Outbound realm identifier for flow-set 2, reverse direction. 119 string Start

Interim-Update

Stop

Acme-Flow-Out-Src-Addr_FS1_F Outbound source (local) address information (the IPv4 address field value of the steering port configuration) for flow-set 1, forward direction. 21 IP address Start

Interim-Update

Stop

Acme-Flow-Out-Src-Addr_FS1_R Outbound source (local) address information (the IPv4 address field value of the steering port configuration) for flow-set 1, reverse direction. 86 IP address Start

Interim-Update

Stop

Acme-Flow-Out-Src-Addr_FS2_F Outbound source (local) address information (the IPv4 address field value of the steering port configuration) for flow-set 2, forward direction. 98 IP address Start

Interim-Update

Stop

Acme-Flow-Out-Src-Addr_FS2_R Outbound source (local) address information (the IPv4 address field value of the steering port configuration) for flow-set 2, reverse direction. 120 IP address Start

Interim-Update

Stop

Acme-Flow-Out-Src-Port_FS1_F Outbound source (local) port information for flow-set 1, forward direction (a port in the range between the start port and end port field values of the steering port configuration). 22 integer Start

Interim-Update

Stop

Acme-Flow-Out-Src-Port_FS1_R Outbound source (local) port information for flow-set 1, reverse direction (a port in the range between the start port and end port field values of the steering port configuration). 87 integer Start

Interim-Update

Stop

Acme-Flow-Out-Src-Port_FS2_F Outbound source (local) port information for flow-set 2, forward direction (a port in the range between the start port and end port field values of the steering port configuration). 99 integer Start

Interim-Update

Stop

Acme-Flow-Out-Src-Port_FS2_R Outbound source (local) port information for flow-set 2, reverse direction (a port in the range between the start port and end port field values of the steering port configuration). 121 integer Start

Interim-Update

Stop

Acme-Flow-Out-Dst-Addr_FS1_F Outbound destination (remote) address information for flow-set 1, forward direction. 23 IP address Start

Interim-Update

Stop

Acme-Flow-Out-Dst-Addr_FS1_R Outbound destination (remote) address information for flow-set 1, reverse direction. 88 IP address Start

Interim-Update

Stop

Acme-Flow-Out-Dst-Addr_FS2_F Outbound destination (remote) address information for flow-set 2, forward direction. 100 IP address Start

Interim-Update

Stop

Acme-Flow-Out-Dst-Addr_FS2_R Outbound destination (remote) address information for flow-set 2, reverse direction. 122 IP address Start

Interim-Update

Stop

Acme-Flow-Out-Dst-Port_FS1_F Outbound destination (remote) port information for flow-set 1, forward direction. 24 integer Start

Interim-Update

Stop

Acme-Flow-Out-Dst-Port_FS1_R Outbound destination (remote) port information for flow-set 1, reverse direction. 89 integer Start

Interim-Update

Stop

Acme-Flow-Out-Dst-Port_FS2_F Outbound destination (remote) port information for flow-set 2, forward direction. 101 integer Start

Interim-Update

Stop

Acme-Flow-Out-Dst-Port_FS2_R Outbound destination (remote) port information for flow-set 2, reverse direction. 123 integer Start

Interim-Update

Stop

This table lists and describes session attributes.
Attribute Name Attribute Description Attribute Value Attribute Value Type Messages
Acme-Session-Generic-Id Common ID shared by H.323 and SIP call legs of a session. This attribute is a combination of a time stamp (measured in seconds) and a monotonically increasing 16-bit integer, followed by an at-sign (@) and the MAC address of the rear interface (wancom).

This attribute is only used to correlate the H.323 and SIP legs of an interworking call/session.

This VSA is not configurable; all CDRs contain this attribute.

40 string Start

Interim-Update

Stop

Acme-Session-Ingress-CallId Call ID generated by the originating device. 3 string Start

Interim-Update

Stop

Acme-Session-Egress-CallId Call ID generated by the SBC to represent a two-way transaction. 4 string Start

Interim-Update

Stop

Acme-Session-Ingress-Realm Explicitly identifies the ingress realm, and contains the name of the ingress realm for the session. All CDRs contain this attribute.

This VSA is not configurable; all CDRs contain this attribute.

41 string Start

Interim-Update

Stop

Acme-Session-Egress-Realm Explicitly identifies the egress realm, and contains the name of the egress realm for the session. All CDRs contain this attribute.

This VSA is not configurable. All CDRs contain this attribute, but it is only populated if an egress realm is found; a call without a route does not have an egress realm.

42 string Start

Interim-Update

Stop

Acme-Session-Protocol-Type Signaling protocol used for a particular leg of a session (in the case of IWF, there may be two legs). This attribute contains the signaling protocol type; for example, SIP or H323.

This VSA is not configurable; all CDRs contain this attribute.

43 string Start

Interim-Update

Stop

Acme-Session-Charging-Vector Appears when the SBC inserts, passes, or deletes the P-Charging-Vector header (SIP).

This attribute is only populated for SIP CDRs, and is not populated if the SBC does not have P-Charging-Vector information.

54 string Start

Interim-Update

Stop

Acme-Session-Charging-Function_Address Appears when the SBC inserts, passes, or deletes the P-Charging-Function-Address.

This attribute is only populated for SIP CDRs, and is not populated if the SBC does not have P-Charging-Function-Address information.

55 string Start

Interim-Update

Stop

Acme-Session-Disposition Status of the call attempt as it progresses from being initiated (using a SIP INVITE or H.323 Setup message) to being either answered or failing to be answered. 60 integer Start

Interim-Update

Stop

Acme-Post-Dial-Delay Amount of time between session initiation and an alerting event. 58 integer Start

Interim-Update

Stop

Acme-P-Asserted-ID P-Asserted ID as described in RFC 3325. 69 string Start

Interim-Update

Stop

Acme-SIP-Diversion SIP Diversion header; communicates to the called party from whom and why a call diverted. 70 string Start

Interim-Update

Stop

Acme-Primary-Routing-Number Primary routing number and phone context (or ingress SIP Request-URI). 64 string Start

Interim-Update

Stop

Acme-Egress-Final-Routing-Number Final routing number and phone context (or egress SIP Request-URI). 134 integer Stop
Acme-Disconnect-Initiator Initiator of a call disconnect. 61 integer Stop
Acme-Disconnect-Cause Q.850 cause code value. 62 integer Stop
Acme-SIP-Status SIP status code for RFC 3326 support. 71 integer Stop
Acme-Originating-Trunk-Group Originating trunk group. 65 string Start

Interim-Update

Stop

Acme-Originating-Trunk-Context Originating trunk group context. 67 string Start

Interim-Update

Stop

Acme-Terminating-Trunk-Group Terminating trunk group. 66 string Start

Interim-Update

Stop

Acme-Terminating-Trunk-Context Terminating trunk group context. 68 string Start

Interim-Update

Stop

Acme-Ingress-Local-Addr Signaling IP address and port of the ingress SBC signaling interface. 74 string Start

Interim-Update

Stop

Acme-Ingress-Remote-Addr Signaling IP address and port of the ingress remote signaling element. 75 string Start

Interim-Update

Stop

Acme-Egress-Local-Addr Signaling IP address and port of the egress SBC signaling interface. 76 string Start

Interim-Update

Stop

Acme-Egress-Remote-Addr Signaling IP address and port of the destination signaling element. 77 string Start

Interim-Update

Stop

Acme-Session-Ingress-RPH RPH value received in the incoming call (e.g., ets.1).

Only populated for NSEP calls.

135 string Start

Interim-Update

Stop

Acme-Session-Egress-RPH RPH value sent in the outgoing call (e.g., ets.3).

Only populated for NSEP calls.

136 string Start

Interim-Update

Stop

Acme-Ingress-Network-Interface-Id To differentiate overlapping IP address spaces (with the Acme-Ingress-Vlan-Tag-Value), gives the ID of the ingress network interface. 137 string Start

Interim-Update

Stop

Acme-Ingress-Vlan-Tag-Value To differentiate overlapping IP address spaces (with the Acme-Ingress-Network-Interface-Id), gives the VLAN tag. 138 integer Start

Interim-Update

Stop

Acme-Egress-Network-Interface-Id To differentiate overlapping IP address spaces (with the Acme-Egress-Vlan-Tag-Value), gives the ID of the ingress network interface. 139 string Start

Interim-Update

Stop

Acme-Egress-Vlan-Tag-Value To differentiate overlapping IP address spaces (with the Acme-Egress-Network-Interface-Id), gives the VLAN tag. 140 integer Start

Interim-Update

Stop

Acme-Refer-Call-Transfer-Id For SIP REFER call method transfer, communicates a call has been transferred from the referer to the referree 141 string Stop
This table lists and describes QoS attributes.
Attribute Name Attribute Description Attribute Value Attribute Value Type Messages
Acme-Calling-RTCP-Packets-Lost_FS1 Total lost packets reported via Real-time Transport Protocol Control Protocol (RTCP), flow-set 1.

Populated only if QoS is enabled.

32 integer Stop
Acme-Calling-RTCP-Packets-Lost_FS2 Total lost packets reported via Real-time Transport Protocol Control Protocol (RTCP), flow-set 2.

Populated only if QoS is enabled.

104 integer Stop
Acme-Calling-RTCP-Avg-Jitter_FS1 Average jitter reported via RTCP measured in milliseconds, flow-set 1.

Populated only if QoS is enabled.

33 integer Stop
Acme-Calling-RTCP-Avg-Jitter_FS2 Average jitter reported via RTCP measured in milliseconds, flow-set 2.

Populated only if QoS is enabled.

105 integer Stop
Acme-Calling-RTCP-Avg Latency_FS1 Average latency reported by comparing the timestamps in RTCP packets for each direction of a call, flow-set 1.

Populated only if QoS is enabled.

34 integer Stop
Acme-Calling-RTCP-Avg Latency_FS2 Average latency reported by comparing the timestamps in RTCP packets for each direction of a call, flow-set 2.

Populated only if QoS is enabled.

106 integer Stop
Acme-Calling-RTCP-MaxJitter_FS1 Maximum amount of jitter value reported via RTCP measured in milliseconds, flow-set 1.

Populated only if QoS is enabled.

35 integer Stop
Acme-Calling-RTCP-MaxJitter_FS2 Maximum amount of jitter value reported via RTCP measured in milliseconds, flow-set 3.

Populated only if QoS is enabled.

107 integer Stop
Acme-Calling-RTCP-MaxLatency_FS1 Maximum latency value measured in milliseconds as observed through RTCP, flow-set 1.

Populated only if QoS is enabled.

36 integer Stop
Acme-Calling-RTCP-MaxLatency_FS2 Maximum latency value measured in milliseconds as observed through RTCP, flow-set 2.

Populated only if QoS is enabled.

108 integer Stop
Acme-Calling-Octets_FS1 Bytes of RTP traffic for this call, flow-set 1.

Populated only if QoS is enabled.

28 integer Stop
Acme-Calling-Octets_FS2 Bytes of RTP traffic for this call, flow-set 2.

Populated only if QoS is enabled.

102 integer Stop
Acme-Calling-Packets_FS1 Number of RTP Packets, received by the SBC, from the calling party, for flow-set 1

Populated only if QoS is enabled.

29 integer Stop
Acme-Calling-Packets_FS2 Number of RTP Packets, received by the SBC, from the calling party, for flow-set 2 .

Populated only if QoS is enabled.

103 integer Stop
Acme-Calling-RTP-Packets-Lost_FS1 Total RTP packets lost in flow-set 1.

Populated only if QoS is enabled.

37 integer Stop
Acme-Calling-RTP-Packets-Lost_FS2 Total RTP packets lost in flow-set 2.

Populated only if QoS is enabled.

109 integer Stop
Acme-Calling-RTP-Avg-Jitter_FS1 Total jitter measured on RTP packets in milliseconds, flow-set 1.

Populated only if QoS is enabled.

38 integer Stop
Acme-Calling-RTP-Avg-Jitter_FS2 Total jitter measured on RTP packets in milliseconds, flow-set 2.

Populated only if QoS is enabled.

110 integer Stop
Acme-Calling-RTP- MaxJitter_FS1 Maximum jitter measured on RTP packets in milliseconds, flow-set 1.

Populated only if QoS is enabled.

39 integer Stop
Acme-Calling-RTP-Avg- MaxJitter_FS2 Maximum jitter measured on RTP packets in milliseconds, flow-set 2.

Populated only if QoS is enabled.

111 integer Stop
Acme-Called-Octets_FS1 Number of Octets (8 bits) of RTP traffic, received by the SBC, from the called party, for flow-set 1.

Populated only if QoS is enabled.

44 integer Stop
Acme-Called-Octets_FS2 Number of Octets (8 bits) of RTP traffic, received by the SBC, from the called party, for flow-set 2 .

Populated only if QoS is enabled.

124 integer Stop
Acme-Called-Packets_FS1 Number of RTP Packets, received by the SBC, from the called party, for flow-set 1.

Populated only if QoS is enabled.

45 integer Stop
Acme-Called-Packets_FS2 Number of RTP Packets, received by the SBC, from the called party, for flow-set 2 .

Populated only if QoS is enabled.

125 integer Stop
Acme-Called-RTCP-Packets-Lost_FS1 Total lost packets reported via Real-time Transport Protocol Control Protocol (RTCP), flow-set 1.

Populated only if QoS is enabled.

46 integer Stop
Acme-Called-RTCP-Packets-Lost_FS2 Total lost packets reported via Real-time Transport Protocol Control Protocol (RTCP), flow-set 2.

Populated only if QoS is enabled.

126 integer Stop
Acme-Called-RTCP-Avg-Jitter_FS1 Average jitter reported via RTCP measured in milliseconds for the ingress side of the call, flow-set 1.

Populated only if QoS is enabled.

47 integer Stop
Acme-Called-RTCP-Avg-Jitter_FS2 Average jitter reported via RTCP measured in milliseconds for the ingress side of the call, flow-set 2.

Populated only if QoS is enabled.

127 integer Stop
Acme-Called-Avg-Latency_FS1 Average latency reported via RTCP measured in milliseconds for the ingress side of the call, flow-set 1.

Populated only if QoS is enabled.

48 integer Stop
Acme-Called-Avg-Latency_FS2 Average latency reported via RTCP measured in milliseconds for the ingress side of the call, flow-set 2.

Populated only if QoS is enabled.

128 integer Stop
Acme-Called-RTCP-MaxJitter_FS1 Maximum amount of jitter reported via RTCP measured in milliseconds for the ingress side of the call, flow-set 1.

Populated only if QoS is enabled.

49 integer Stop
Acme-Called-RTCP-MaxJitter_FS2 Maximum amount of jitter reported via RTCP measured in milliseconds for the ingress side of the call, flow-set 2.

Populated only if QoS is enabled.

129 integer Stop
Acme-Called-RTCP-MaxLatency_FS1 Maximum amount of latency reported via RTCP measured in milliseconds for the ingress side of the call, flow-set 1.

Populated only if QoS is enabled.

50 integer Stop
Acme-Called-RTCP-MaxLatency_FS2 Maximum amount of latency reported via RTCP measured in milliseconds for the ingress side of the call, flow-set 2.

Populated only if QoS is enabled.

130 integer Stop
Acme-Called-RTP-Packets-Lost_FS1 Total lost RTP packets for the ingress side of the call, flow-set 1.

Populated only if QoS is enabled.

51 integer Stop
Acme-Called-RTP-Packets-Lost_FS2 Total lost RTP packets for the ingress side of the call, flow-set 2.

Populated only if QoS is enabled.

131 integer Stop
Acme-Called-RTP-Avg-Jitter_FS1 Average jitter reported via RTP measured in milliseconds for the ingress side of the realm, flow-set 1.

Populated only if QoS is enabled.

52 integer Stop
Acme-Called-RTP-Avg-Jitter_FS2 Average jitter reported via RTP measured in milliseconds for the ingress side of the realm, flow-set 2.

Populated only if QoS is enabled.

132 integer Stop
Acme-Called-RTP-MaxJitter_FS1 Maximum amount of jitter reported via RTP measured in milliseconds for the ingress side of the call, flow-set1.

Populated only if QoS is enabled.

53 integer Stop
Acme-Called-RTP-MaxJitter_FS2 Maximum amount of jitter reported via RTP measured in milliseconds for the ingress side of the call, flow-set 2.

Populated only if QoS is enabled.

133 integer Stop
Acme-Calling-R-Factor QoS R-Factor calculation for the calling side of a session.

Populated only if QoS is enabled.

This value is reported as * 100 in order to appear as an integer.

151 integer Stop
Acme-Calling-MOS QoS MOS calculation for the calling side of a session.

Populated only if QoS is enabled.

This value is reported as * 100 in order to appear as an integer.

152 integer Stop
Acme-Called-R-Factor QoS R-Factor calculation for the called side of a session.

Populated only if QoS is enabled.

This value is reported as * 100 in order to appear as an integer.

153 integer Stop
Acme-Called-MOS

New in Release

QoS MOS calculation for the called side of a session.

Populated only if QoS is enabled.

This value is reported as * 100 in order to appear as an integer.

154 integer Stop
Acme-Session-Forked-Call-Id The VSA is a string value, and appears as the header-value without the header parameters from the P-Multiring-Correlator header for a session identified as part of a forked call. 171 string Stop
Acme-Flow-Calling-Media-Stop-Time_FS1 calling side’s media stop time - stream 1 231 string Start

Interim-Update

Interim-Update (error)

Stop

Acme-Flow-Called-Media-Stop-Time_FS1 called side’s media stop time - stream 1 232 string Start

Interim-Update

Interim-Update (error)

Stop

Acme-Flow-Calling-Media-Stop-Time_FS2 calling side’s media stop time - stream 2 233 string Start

Interim-Update

Interim-Update (error)

Stop

Acme-Flow-Called-Media-Stop-Time_FS2 called side’s media stop time - stream 2 234 string Start

Interim-Update

Interim-Update (error)

Stop

IPv6 Support

The following table lists the media flow attributes for IPv6 flows.

Attribute Name Attribute Description Attribute Value Attribute Value Type Messages
Acme-Flow-In-Src-IPv6_Addr_FS1_F Inbound source IPv6 address (remote) information for flow-set 1, forward direction. 155 ipv6addr Start

Interim-Update

Stop

Acme-Flow-In-Dst-IPv6_Addr_FS1_F Inbound destination (local) address information (the IPv6 address field value of the steering pool configuration) for flow-set 1, forward direction. 156 ipv6addr Start

Interim-Update

Stop

Acme-Flow-Out-Src-IPv6_Addr_FS1_F Outbound source (local) address information (the IPv6 address field value of the steering port configuration) for flow-set 1, forward direction. 157 ipv6addr Start

Interim-Update

Stop

Acme-Flow-Out-Dst-IPv6_Addr_FS1_F Outbound destination (remote) IPv6 address information for flow-set 1, forward direction. 158 ipv6addr Start

Interim-Update

Stop

Acme-Flow-In-Src-IPv6_Addr_FS1_R Inbound source IPv6 address (remote) information for flow-set 1, reverse direction. 159 ipv6addr Start

Interim-Update

Stop

Acme-Flow-In-Dst-IPv6_Addr_FS1_R Inbound destination (local) address information (the IPv6 address field value of the steering pool configuration) for flow-set 1, reverse direction. 160 ipv6addr Start

Interim-Update

Stop

Acme-Flow-Out-Src-IPv6_Addr_FS1_R Outbound source (local) address information (the IPv6 address field value of the steering port configuration) for flow-set 1, reverse direction. 161 ipv6addr Start

Interim-Update

Stop

Acme-Flow-Out-Dst-IPv6_Addr_FS1_R Outbound destination (remote) IPv6 address information for flow-set 1, reverse direction. 162 ipv6addr Start

Interim-Update

Stop

Acme-Flow-In-Src-IPv6_Addr_FS2_F Inbound source address (remote) IPv6 information for flow-set 2, forward direction. 163 ipv6addr Start

Interim-Update

Stop

Acme-Flow-In-Dst-IPv6_Addr_FS2_F Inbound destination (local) address information (the IPv6 address field value of the steering pool configuration) for flow-set 2, forward direction. 164 ipv6addr Start

Interim-Update

Stop

Acme-Flow-Out-Src-IPv6_Addr_FS2_F Outbound source (local) address information (the IPv6 address field value of the steering port configuration) for flow-set 2, forward direction. 165 ipv6addr Start

Interim-Update

Stop

Acme-Flow-Out-Dst-IPv6_Addr_FS2_F Outbound destination (remote) IPv6 address information for flow-set 2, forward direction. 166 ipv6addr Start

Interim-Update

Stop

Acme-Flow-In-Src-IPv6_Addr_FS2_R Inbound source address (remote) IPv6 address information for flow-set 2, reverse direction. 167 ipv6addr Start

Interim-Update

Stop

Acme-Flow-In-Dst-IPv6_Addr_FS2_R Inbound destination (local) address information (the IPv6 address field value of the steering pool configuration) for flow-set 2, reverse direction. 168 ipv6addr Start

Interim-Update

Stop

Acme-Flow-Out-Src-IPv6_Addr_FS2_R Outbound source (local) address information (the IPv6 address field value of the steering port configuration) for flow-set 2, reverse direction. 169 ipv6addr Start

Interim-Update

Stop

Acme-Flow-Out-Dst-IPv6_Addr_FS2_R Outbound destination (remote) IPv6 address information for flow-set 2, reverse direction. 170 ipv6addr Start

Interim-Update

Stop

Acme-Flow-Calling-Media-Stop-Time_FS1 calling side’s media stop time - stream 1 231 string Start

Interim-Update

Interim-Update (error)

Stop

Acme-Flow-Called-Media-Stop-Time_FS1 called side’s media stop time - stream 1 232 string Start

Interim-Update

Interim-Update (error)

Stop

Acme-Flow-Calling-Media-Stop-Time_FS2 calling side’s media stop time - stream 2 233 string Start

Interim-Update

Interim-Update (error)

Stop

Acme-Flow-Called-Media-Stop-Time_FS2 called side’s media stop time - stream 2 234 string Start

Interim-Update

Interim-Update (error)

Stop

Oracle VSA Values

The table below defines the possible values for several Oracle VSAs.

Oracle VSA Name Attribute Value Possible Values
Acme-PostDial-Delay 58 Unit value in milliseconds
Acme-Session-Disposition 60 0=unknown

1=call_attempt

2=ringing

3=answered

Acme-Disconnect-Initiator 61 0=UNKNOWN_DISCONNECT_INITIATOR

1=CALLING_PARTY_DISCONNECT

2=CALLED_PARTY_DISCONNECT

3=INTERNAL_DISCONNECT

Acme-Disconnect-Cause 62 34=No circuit/channel available

47=Resource unavailable

3=No route destination

31=Normal, unspecified

88=Incompatible destination

111=Interworking, unspecified

38=Network out of order

42=Switching equip congestion

28=Invalid number format

41=Temporary failure

17=User busy

16=Normal call clearing

20=Subscriber absent

31=Normal call clearing

18=Request error timeout response

55=Forbidden error response

0=No reason cause presented

Acme-SIP-Diversion 70 SIP Diversion header based on this RFC draft: draft-levy-sip-diversion-05.txt
Acme-SIP-Status 71 This is a complete list of support status codes; only a subset would be reported in a Stop record:

RESP_STATUS_TRYING 100

RESP_STATUS_RINGING 180

RESP_STATUS_FORWARD 181

RESP_STATUS_QUEUED 182

RESP_STATUS_PROGRESS 183

RESP_STATUS_OK 200

RESP_STATUS_CREATED 201

RESP_STATUS_ACCEPTED 202

RESP_STATUS_PART 206

RESP_STATUS_MAX_OK 299

RESP_STATUS_MULTIPLE 300

RESP_STATUS_MOVED 301

RESP_STATUS_MOVED_TMP 302

RESP_STATUS_USE_PROXY 305

RESP_STATUS_ALTERNATE 380

RESP_STATUS_BAD 400

RESP_STATUS_UNAUTH 401

RESP_STATUS_PAY_REQ 402

RESP_STATUS_FORBIDDEN 403

RESP_STATUS_NOT_FOUND 404

RESP_STATUS_NOT_ALLOW 405

RESP_STATUS_NOT_ACCEPT 406

RESP_STATUS_AUTH_REQ 407

RESP_STATUS_REQ_TMO 408

RESP_STATUS_CONFLICT 409

RESP_STATUS_GONE 410

RESP_STATUS_LEN_REQ 411

RESP_STATUS_TOO_BIG 413

RESP_STATUS_URI_TOO_BIG 414

RESP_STATUS_MEDIA 415

RESP_STATUS_URI_SCHEME 416

RESP_STATUS_BAD_EXT 420

RESP_STATUS_EXT_REQ 421

RESP_STATUS_TOO_SMALL 422

RESP_STATUS_TOO_BRIEF 423

RESP_STATUS_TMP_UNAVAIL 480

RESP_STATUS_NO_EXIST 481

RESP_STATUS_LOOP 482

RESP_STATUS_TOOMNY_HOPS 483

RESP_STATUS_ADDR_INCMPL 484

RESP_STATUS_AMBIGUOUS 485

RESP_STATUS_BUSY_HERE 486

RESP_STATUS_CANCELLED 487

RESP_STATUS_NOT_HERE 488

RESP_STATUS_BAD_EVENT 489

RESP_STATUS_PENDING 491

RESP_STATUS_UNDECIPH 493

RESP_STATUS_INT_ERR 500

RESP_STATUS_NOT_IMPL 501

RESP_STATUS_BAD_GTWY 502

RESP_STATUS_SVC_UNAVAIL 503

RESP_STATUS_GTWY_TMO 504

RESP_STATUS_BAD_VER 505

RESP_STATUS_MSG_TOO_BIG 513

RESP_STATUS_PRE_FAIL 580

RESP_STATUS_BUSY 600

RESP_STATUS_DECLINE 603

RESP_STATUS_DONT_EXIST 604

RESP_STATUS_NOTACCEPT 606

Authentication VSAs

The table below defines Oracle VSAs used for RADIUS authentication.

Oracle VSA Name Attribute Value Attribute Values
Acme-User-Privilege Describes at RADIUS login the privileges granted to the administrator (VSA only available with admin security license installed). Values can be:

sftpForAudit (SFTP is allowed for audit logs)

sftpForAll (SFTP is allowed for logging, and audit logs)

253
Acme-User-Class Identifies the authorization class on the SBC; used for RADIUS authentication only and does not apply to accounting. Values can be user or admin 254

RTP Traffic Reporting per Call

The SBC reports total RTP traffic counts, both received and transmitted for calls through standard accounting interfaces on stop record generation. This traffic is reported in Packets and Octets, sent and received, for flow-sets 1 and 2. The QoS feature set must be enabled to report on RTP traffic, otherwise the values will be reported as 0

These statics are captured for the following scenarios
  • RTP pass-thru sessions
  • transcoded/transrated/inband (audio) DTMF-interworked RTP sessions
  • RTP sessions where one or both call legs is encrypted (SRTP)

RTP traffic reporting does not capture MSRP B2BUA and MSRP NAT traffic.

The quick way to decipher these 16 statistics are as follows:
  • Calling/Called - call-leg the static reports on
  • Octets/Packets - counter unit for traffic
  • FS1/FS2 - flow set 1 or flow set 2
  • blank/transmitted - traffic received (blank) or transmitted by the SBC
Counter Definition RADIUS/Local CDR (VSA #) output AVP in Acme-Packet-Specific-Rf-QoS(37)
Number of Octets (8 bits) of RTP traffic, received by the SBC, from the calling party, for flow-set 1 Acme-Calling-Octets-FS1 (28) RTP-Calling-Octets-FS1 (38)
Number of RTP Packets, sent from the SBC, to the calling UA, for flow-set 1 Acme-Calling-Packets-FS1 (29) RTP-Calling-Packets-FS1(40)
Number of Octets (8 bits) of RTP traffic, sent from the SBC, to the called UA, for flow-set 1 Acme-Called-Octets-FS1 (44) RTP-Called-Octets-FS1 (62)
Number of RTP Packets, sent from the SBC, to the called UA, for flow-set 1 Acme-Called-Packets-FS1 (45) RTP-Called-Packets-FS1 (64)
Number of Octets (8 bits) of RTP traffic, received by the SBC, from the calling party, for flow-set 2 Acme-Calling-Octets-FS2 (102) RTP-Calling-Octets-FS2 (39)
Number of RTP Packets, sent from the SBC, to the calling UA, for flow-set 2 Acme-Calling-Packets-FS2 (103) RTP-Calling-Packets-FS2(41)
Number of Octets (8 bits) of RTP traffic, sent from the SBC, to the called UA, for flow-set 2 Acme-Called-Octets-FS2 (124) RTP-Called-Octets-FS2 (63)
Number of RTP Packets, sent from the SBC, to the called UA, for flow-set 2 Acme-Called-Packets-FS2 (125) RTP-Called-Packets-FS2 (65)
Number of Octets (8 bits) of RTP traffic, transmitted by the SBC, to the calling party, for flow-set 1 Acme-Calling-RTP-Octet-Transmitted-FS1 (240) RTP-Calling-Octets-Transmitted-FS1 (42)
Number of RTP Packets, transmitted by the SBC, to the calling UA, for flow-set 1 Acme-Calling-RTP-Packets-Transmitted-FS1 (241) RTP-Calling-Packets-Transmitted-FS1 (44)
Number of Octets (8 bits) of RTP traffic, transmitted by the SBC, to the called UA, for flow-set 1 Acme-Called-RTP-Octet-Transmitted-FS1 (242) RTP-Called-Octets-Transmitted-FS1 (66)
Number of RTP Packets, transmitted by the SBC, to the called UA, for flow-set 1 Acme-Called-RTP-Packets-Transmitted-FS1 (243) RTP-Called-Packets-Transmitted-FS1 (68)
Number of Octets (8 bits) of RTP traffic, transmitted by the SBC, to the calling party, for flow-set 2 Acme-Calling-RTP-Octets-Transmitted-FS2 (244) RTP-Calling-Octets-Transmitted-FS2 (43)
Number of RTP Packets, transmitted by the SBC, to the calling UA, for flow-set 2 Acme-Calling-RTP-Packets-Transmitted-FS2 (245) RTP-Calling-Packets-Transmitted-FS1 (45)
Number of Octets (8 bits) of RTP traffic, transmitted by the SBC, to the called UA, for flow-set 2 Acme-Called-RTP-Octet-Transmitted-FS2 (246) RTP-Called-Octets-Transmitted-FS2 (67)
Number of RTP Packets, transmitted by the SBC, to the called UA, for flow-set 2 Acme-Called-RTP-Packets-Transmitted-FS2 (247) RTP-Called-Packets-Transmitted-FS2 (69)

VoLTE and SMS VSAs

The SBC reports session-specific information for VoLTE calls and for Short Message Service (SMS) messages. Much of this information overlaps both session types as they address similar variables within their environments.

This table lists and describes the VoLTE and SMS attributes and includes attribute name, attribute description, attribute value, attribute value type, and messages.

Note:

See the Oracle RADIUS Acme-Extended-Attributes VSAs section for an explanation of the attribute extensions included in the tables below.
Attribute Name Attribute Description Attribute Value Attribute Value Type Messages
Acme-Access-Network-Information Extracted from Access-Network-Information field from P-Access-Network-Info headers.

For MO calls it should be the PANI headers of the outgoing INVITE (after the NPLI procedure).

For MT calls it should be the PANI headers of the outgoing 18x response (after the NPLI procedure).

248 SMS and VoLTE Start

Interim-Update

Stop

Acme-P-GW IP Address Obtained from PCRF RAR/AAA in Access-Network-Charging-Address (501) AVP. 249, ext 1 VoLTE call Start

Interim-Update

Stop

Acme-S-GW IP Address Obtained from PCRF AAA/RAR in AN-GW-Address (1050) AVP 249, ext 2 VoLTE call Start

Interim-Update

Stop

Acme-Originating-IOI Extracted from the Originating-IOI field in the P-Charging-Vector header.

For MT, MO (MESSAGE/INVITE) calls, the field is extracted from SIP reply(20X).

249, ext 3 SMS and VoLTE call Start

Interim-Update

Stop

Acme-Terminating-IOI Extracted from the Terminating-IOI field in the P-Charging-Vector header.

For MT, MO (MESSAGE/INVITE) calls, the field is extracted from SIP reply(20X).

249, ext 4 SMS and VoLTE call Start

Interim-Update

Stop

Acme-IMEI Extracted from the registration cache or Initial request.

(The Initial request takes priority.)

249, ext 5 SMS and VoLTE call Start

Interim-Update

Stop

Acme-Node-Functionality Configured with a single, global Node Functionality value. This is done in the SIP config's node functionality parameter.

However, if the node functionality parameter is also configured in a realm config, the ingress realm's node functionality value supersedes the global value.

249, ext 6 SMS and VoLTE call Start

Interim-Update

Stop

Acme-SMS Message Type Extracted from initial SIP MESSAGE. 249, ext 7 SMS

Stop

Acme-SMS Calling party number Extracted from initial SIP MESSAGE.

For MO, from the P-Asserted-Identity header

For MT, from the TP-Originating-Address

 249, ext 8 SMS

Stop

Acme-SMS Called party number Extracted from initial SIP MESSAGE.

For MO, from the TP-Destination-Address

For MT, from the To header of the SIP MESSAGE

 249, ext 9 SMS

Stop

Acme-Message Length Extracted from SIP MESSAGE field TP-User-Data-Length 249, ext 10 SMS

Stop

Acme-History-Info Extracted from History-Info sip headers, ingress interface and it taken from initial message.

In case of multiple History-Info headers, concatenated into a single header values in CDR.

250 VoLTE call Start

Interim-Update

Stop

Acme-Visited-Network-Identifier Extracted from Visited-Network-Identifier field from P-Visited-Network-Id headers.

For MO calls, the field is extracted from initial request, or from the ingress sip-interface if the PVNI is not received in the initial request.

For MT calls, the field is extracted from the initial request.

251 SMS and VoLTE call Start

Interim-Update

Stop

Acme-IMSI Extracted from the registration cache or Initial request.

(The Initial request takes priority.)

252 SMS and VoLTE call Start

Interim-Update

Stop

This information appears in RADIUS CDRs, CSV CDRs, and the Oracle VSA dictionary. The SBC reports with AVP information that is equivalent to the VSA information below.

The SBC generates SMS call records when you configure the generate-event parameter with the messages value. Fields supporting message accounting include:

  • Acme-Access-Network-Information (248)
  • Acme-Visited-Network-Identifier (251)
  • Acme-Originating-IOI (249, extension 3)
  • Acme-Terminating-IOI (249, extension 4)
  • Acme-IMSI (252)
  • Acme-IMEI (249, extension 5)
  • Acme-Node-Functionality (249, extension 6)
  • Acme-SMS Message Type (249, extension 7)
  • Acme-SMS Calling party number (249, extension 8)
  • Acme-SMS Called party number (249, extension 9)
  • Acme-Message Length (249, extension 10)
  • Acme-Timestamp

The SBC generates VoLTE call records under the same scenarios and using the same configuration as other SIP calls. Fields supporting VoLTE call accounting include:

  • Acme-Access-Network-Information (248)
  • Acme-Visited-Network-Identifier (251)
  • Acme-Originating-IOI (249, extension 3)
  • Acme-Terminating-IOI (249, extension 4)
  • Acme-IMSI (252)
  • Acme-IMEI (249, extension 5)
  • Acme-History-Info (250)
  • Acme-Node-Functionality (249, extension 6)
  • Acme-P-GW IP Address (249, extension 1)
  • Acme-S-GW IP Address (249, extension 2)

Note:

The SBC includes this same information within equivalent records managed over diameter. VSAs do not have the "Acme" prefix in their name, and the VSA identification information is specific to diameter VSAs.

Distinct VoLTE Processes

For VoLTE calls, the process for generating CDRs is the largely the same as for other calls. As described, there are additional data points included for these call types.

In addition, the list below presents additional processes reserved for VoLTE data management with which you should be familiar:

  • When there is an SRVCC event, the SBC creates a separate set of CDRs for the handover session. The SBC correlates the original and handover session using the "Generic-ID" field, which points to the Call-ID of the initial session. In addition, the SBC populates the Generic-ID field within the Initial Session CDRs (STOP), with the HO session Call-ID.
  • The SBC copies the Call id of the second INVITE (Handover INVITE) into the Generic Id into the CDR for the first INVITE (initial call) for both MO and MT call
    • For mobile originating call—When the SBC receives the 200 Ok for the BYE from UE, it inserts the Call id of second INVITE, which is generated from the MSC-S as Generic Id, into the CDR of First MO Invite (Before the handover call).
    • For mobile terminating call—When the SBC receives the 200 Ok for the BYE from UE, it inserts the Call id of the second INVITE, which is generated from the MSC-S as Generic Id, into the CDR of the first MT INVITE (before the handover call).
    • If there is a negative case, such as a BYE timeout, the SBC writes the Call id of second INVITE, which is generated from the MSC-S as the Generic Id, into the CDR of the first INVITE (before the handover call) when that corresponding call gets terminated.

Note:

The SBC performs these same processes for both RADIUS accounting when generating CDRs and Diameter accounting when generating ACRs.
Configurations to Specify VoLTE and SMS Data

You can configure the SBC to use specific data in call data records provided over RADIUS, Diameter and within local CSVs. This ensures that the specified fields

There are two configurations available for specifying VoLTE and SMS data:

  • Subscribe to IP-CAN-CHANGE events
  • Specify Inter-Operator Identifier (IOI)

Subscribe to IP-CAN-CHANGE Events

You can configure a subscription to the IP-CAN-CHANGE event using the Rx interface during the AAA/RAR exchange. To do this, you configure the ip-can-change value to the specific-action-subscription of the applicable ext-policy-config. This causes the SBC to apply the value in the AN-GW-Address AVP from the PCRF as the S-GW IP address.

Note:

If the SBC receives more than one AN-GW-Address AVP from the PCRF, it applies the value in the AN-GW-Address AVP from the PCRF. It also uses the S-GW IP address the first AVP as the S-GW IP address.

Option to Specify IOI

You configure the realm-as-ioi option in the applicable account-config to send the realm name as the IOI in diameter ACRs. If this option is not set, the SBC uses the IOI from the charging vector.

Configure this option using the syntax below. 

ORACLE(account-config)# options +realm-as-ioi

If you type options and then the option value without the plus sign, you overwrite any previously configured options. To add a new option to an options list, pre-pend the new option with a plus sign as shown in the previous example.

Configuring the ip-can-change Subscription

You use the steps below to Subscribe to IP-CAN-CHANGE events at the PCRF and apply the value in the AN-GW-Address AVP from the PCRF as the S-GW IP address.

To obtain the S-GW IP address for mobile originating and terminating scenarios and provide that data in CDRs for RADIUS, diameter and local CSVs:
  1. In Superuser mode, type configure terminal and press Enter. 
    ORACLE# configure terminal
  2. Type media-manager and press Enter. 
    ORACLE(configure)# media-manager
  3. Type ext-policy-config and press Enter. 
    ORACLE(session-router)# ext-policy-config
ORACLE(ext-policy-config)#
  4. Type specific-action-subscription, ip-can-change and press Enter. 
    ORACLE(session-router)# specific-action-subscription ip-can-change
ORACLE(ext-policy-config)#
    The specific-action-subscription accepts multiple values. When configuring 2 or more specific actions, enclose them in quotation marks, with the values separated by spaces.
  5. Save your work.

Including P-Visited Network Identifier and History-Info Headers in CDRs

You can configure the SBC to add fully compliant P-Visited Network Identifier (PVNI) and History-Info (HI) headers in CDRs. You configure this by adding the pcscf-cdr-compliance option to the account-config, specifying whether you want to include PVNI (PVNI-pref), HI (HI-pref), or both. The behavior is dependent on the type of call, including Mobile Terminating (MT) and Mobile Originating (MO), information provided by SIP, and whether you are also using an S8HR profile.

The PVNI and HI fields in CDRs may or may not contain data. When configured, the SBC performs processes to determine whether or not to add:

  • P-Visited-Network-ID to the applicable CDR field
  • History-Info to the applicable CDR field

You configure the pcscf-cdr-compliance in the applicable account-config to use these processes within your environment. 

ORACLE# configure terminal
ORACLE(configure)# session-router
ORACLE(session-router)# account-config
ORACLE(account-config)# select
ORACLE(account-config)# options +pcscf-cdr-compliance=PVNI-pref

If you save and activate this configuration, the SBC enables PVNI CDR population for MT calls. To configure for both PVNI and HI headers, configure the option with both values separated by a comma and enclosed in quotes. 

ORACLE(account-config)# options +pcscf-cdr-compliance="PVNI-pref,HI-pref"

Support for P-Visited-Network-ID Field

For MT calls, the access SBC, deployed as an A-SBC, inserts the PVNI header in CDRs based on the called party registration cache entry (MCC/MNC). If the Called party registration cache does not have a PVNI value, the A-SBC inserts the network-id value from the access side (egress realm) sip-interface configuration as the PVNI into CDRs.

For both MO and MT and when you configure it to add PVNI to CDRs, the A-SBC checks for an s8hr-profile in the same interface:

  • If there is an S8HR profile on the access sip-interface:
    • If the SBC receives an MCC/MNC from the Rx server, it creates the PVNI header using the called party registration cache entry (MCC/MNC) and adds it to the CDR.
    • If the SBC does not receive an MCC/MNC, It checks whether there is a network-id value on the access side sip-interface:
      1. If so, the SBC creates the PVNI using that network-id value.
      2. If not, the SBC uses the local-mccmnc value as the PVNI, and adds it to CDR.

        Note:

        If you have not configured the local-mccmnc value in your S8HR profile, the SBC uses the default, which is 999999.
  • If there is not an S8HR profile on the access sip-interface, the SBC checks whether there is a network-id value on the access side sip-interface. If so, the SBC uses the network-id value as the PVNI, and adds it to CDR.
  • If both the S8HR and the egress (access) network-id are not configured, the SBC checks whether the initial INVITE/MESSAGE comes from a trusted endpoint and contains a PVNI:
    • If so, the SBC relays the PVNI and add to CDR.
    • If not, the SBC leaves the PVNI field empty.

When you have set the pcscf-cdr-compliance option to include PVNI, and the SBC is acting as an I-SBC handling MO/MT calls, the SBC uses the following sequence for populating the CDR field:

  1. If configured, uses the network-id on the ingress sip-interface as PVNI.
  2. If populated and from a trusted endpoint, uses the PVNI from the initial INVITE.
  3. Leaves the PVNI field empty.

Note:

This behavior applies to the INVITE or any Re-INVITE.

Support for History-Info Field

For MO calls, if you have configured the HI option in the account-config, SBC uses the History-Info(s) received in the initial INVITE replies, including those with 181, 180 or 200 status-codes. The SBC populates the CDR with the last provisional (>100) or final (200) response containing History-Info(s). If History-Info is not available in provisional or final replies, the SBC leaves the History-Info in the CDR empty.

For MT calls, SBC extracts History-Info header(s) from the initial INVITE and adds them to the CDR. If History-Info is not available in the initial INVITE, the SBC leaves the HI field empty.

If there are multiple History-Info headers in the initial INVITE, the SBC concatenates all the history-info headers values, and without exceeding the default or configured CDR field size, adds them to the CDR.

For example, assume INVITE has three History-Info headers in the following order:
  1. HI-1 - 100 characters
  2. HI-2 - 100 characters
  3. HI-3 - 100 characters

By default, the maximum CDR field size is 246. In this case, the SBC includes the first two History-Info headers in their entirety, and truncates HI-3.

Consider the presence of the following HI headers:

  • History-Info: <sip:bob@example.com>;index=1
  • History-Info: <sip:office@example.com>;index=1.2;mp=1
  • History-Info: <sip:office@192.0.2.5>;index=1.2.1;rc=1.2

The SBC populates the History-Info CDR as follows 

<sip:bob@example.com>;index=1, <sip:office@example.com>;index=1.2;mp=1, <sip:office@192.0.2.5>;index= 1.2.1;rc=1.2

P-Asserted-ID Header Format in CDRs

The P-Asserted-ID (PAI) Header URI in CDR displays without the display name by default, even though PAI header is present along with the display-name in the SIP message. The format includes <> (angle brackets) symbol in the Acme-P-Asserted-ID. For example, Acme-P-Asserted-ID = <sip:office@example.com>. To include angle brackets symbol in the Acme-P-Asserted-ID, add an option display-name-AVP-add under account-config, so that PAI header URI in CDR, displays along with the display-name if present.

Adding the display-name-AVP-add option

To add an option display-name-AVP-add under account-config from CLI: 

ORACLE# configure terminal
ORACLE(configure)# session-router
ORACLE(session-router)# account-config
ORACLE(account-config)# options +display-name-AVP-add

If you type the option without the plus sign, you overwrite any previously configured options. To append the new option to the options list, prepend the new option with a plus sign as shown in the previous example.