In this section:

Accounting File Version Change

The CAM version of SBC Core release 12.00.00 is 103.00.00.

For more information, refer to the section Billing Introduction.

CAM Field Changes

New Accounting Record Fields in Release 12.00.00

Refer to the following pages for details:

SBX-113574 CNF SIPREC Support

The recording CDRs are updated to print GUID.

The following fields are added in the Recording CDR:

  • Global Unique ID (GUID)
  • nodeName
  • podName
  • containerID

For additional information, refer to: CDR Field Descriptions

SBX-118127 Ingress Identity Headers Received and Egress Identity Headers Sent CDR fields

Fields added to the STOP and ATTEMPT Records

The CDR fields "Ingress Identity Headers Received" and "Egress Identity Headers signed/sent" are added to the STOP and ATTEMPT CDR records. The ingress identity headers string is sent from the SIPSG/CC to CAM. Refer to the SBC 12.0 SBC Core Billing Guide for additional details.


ASCII AccountingStreaming Accounting
Field NameMax LengthTypeStartStopAttemptIntermediateIDType
Ingress Identity Headers Received2402StringNA299216NANANA
Egress Identity Headers sent2402StringNA300217NANANA
Raw CDR Field String Format

A maximum of nine decoded and restructured Identity Headers separated by commas:

<shaken>,<rph>,<rcd>,<div1>,<div2>,<div3>,<div4>,<div5>,<other>

If the egress side has some of the same Identity headers as the Ingress, then, the value "dup" shall be filled in those places: - <shaken>,<rph>,dup,<div1>,,,,, Here the value 3rd Identity is a duplicate, and fields 5,6,7,8 and 9 are empty so they are left blank separated by commas.

Decoded CDR Field Format

The CDRs for the ATTEMPT and STOP records appear as shown below.

<field_num>Ingress Identity Headers Received:

<field_num>.1:  Shaken Identity Header :  "{alg:ES256;ppt:shaken;typ:passport;x5u:https://crpartner.ccid.neustar.biz/ccid/authn/v2/certs/49.162};{attest:A;dest:{tn:[16308868697]};iat:1657635705;orig:{tn:13123804509};origid:8cff85d8-cec7-11eb-a0c7-9b2f7a7ed381}"

<field_num>.2:  RPH Identity Header     :   

<field_num>.3:  RCD Identity Header     :   

<field_num>.4:  Div1 Identity Header    :   

<field_num>.5:  Div2 Identity Header    :   

<field_num>.6:  Div3 Identity Header    :   

<field_num>.7:  Div4 Identity Header    :   

<field_num>.8:  Div5 Identity Header    :   

<field_num>.9:  Other Identity Header  :



<field_num>Egress Identity Headers sent:

<field_num>.1:  Shaken Identity Header :  "dup"

<field_num>.2:  RPH Identity Header     :   

<field_num>.3:  RCD Identity Header     :   

<field_num>.4:  Div1 Identity Header    :   "{alg:ES256;ppt:div;typ:passport;x5u:https://cr.ccid.neustar.biz/ccid/authn/v2/certs/11342.10182;dest:{tn:[19796900952]};div:{tn:1303519796900952};iat:1657636662;orig:{tn:18777216504}}"

<field_num>.5:  Div2 Identity Header    :   

<field_num>.6:  Div3 Identity Header    :   

<field_num>.7:  Div4 Identity Header    :   

<field_num>.8:  Div5 Identity Header    :   

<field_num>.9:  Other Identity Header  :

The field_num is the next available number in these records.

Field 216 of ATTEMPT record and Field 299 of STOP record is now populated with Ingress Identity Headers Received.  Field 217 of ATTEMPT record and Field 300 of STOP record is now populated with Egress Identity Headers Sent. These are populated by the decoded identity headers in the received and outgoing INVITE respectively. Each of these fields is a comma separated string and can hold up to nine identity headers. There is no maximum for individual sub fields but the maximum length of the overall field is 2400 characters.

The ATTEMPT record appears as shown below:

Example - Fields in ATTEMPT Record
216: Ingress Identity Headers Received:

216.1:  Shaken Identity Header :  "{alg:ES256;ppt:shaken;typ:passport;x5u:https://crpartner.ccid.neustar.biz/ccid/authn/v2/certs/49.162};{attest:A;dest:{tn:[16308868697]};iat:1657635705;orig:{tn:13123804509};origid:8cff85d8-cec7-11eb-a0c7-9b2f7a7ed381}"

216.2:  RPH Identity Header     :   

216.3:  RCD Identity Header     :   

216.4:  Div1 Identity Header    :   

216.5:  Div2 Identity Header    :   

216.6:  Div3 Identity Header    :   

216.7:  Div4 Identity Header    :   

216.8:  Div5 Identity Header    :   

216.9:  Other Identity Header    : 



217: Egress Identity Headers sent:

217.1:  Shaken Identity Header :  "dup"

217.2:  RPH Identity Header     :   

217.3:  RCD Identity Header     :   

217.4:  Div1 Identity Header    :   "{alg:ES256;ppt:div;typ:passport;x5u:https://cr.ccid.neustar.biz/ccid/authn/v2/certs/11342.10182;dest:{tn:[19796900952]};div:{tn:1303519796900952};iat:1657636662;orig:{tn:18777216504}}"

217.5:  Div2 Identity Header    :   

217.6:  Div3 Identity Header    :   

217.7:  Div4 Identity Header    :   

217.8:  Div5 Identity Header    : 

217.9:  Other Identity Header    :

SBX-113004 3xx contact information CDR field

Field 186 of the ATTEMPT record is now populated with information from the contact headers in the 3xx message being relayed.

This field has up to 10 subfields. Each subfield contains one contact information received in the 3xx SIP message. The maximum length allowed for each contact 129 characters. The sub-field is a string and is a mix of IP address and names. The information is only populated when the SIP trunk group control support3xxRlyContactsInCdr is enabled.

Sub field

Name

Length

1Contact10-129 characters
2Contact20-129 characters
3Contact30-129 characters
4Contact40-129 characters
5Contact50-129 characters
6Contact60-129 characters
7Contact70-129 characters
8Contact80-129 characters
9Contact90-129 characters
10Contact100-129 characters

SBX-124408 CDR file footer naming convention changed in 12.0 to YYYMMDD HHMMSS.