Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c86e9b2550016ec54396b5000a8a00a0c86820e56901685f374974002d, userName='null'}
JIRAIDAUTHSBX-112201122714
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cdec0ad48a00a0c881f4f91201823e0fa3e20048, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb1f0553, userName='null'}
REV2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c90701ea8a00a02355cd1c2f0155cd26cc650806, userName='null'}

The following fields are populated in the Recording CDR. As this is generated for each SRS separately, the SBC does not add recorder(s) information here.

Info
titleNote

The SBC generates timestamps in the local time format in the ACT files for any of the fields that were previously in the GMT time format.


Field
Length
Type
Record number
Comment
RECORDING9Characters1The string "RECORDING" indicating this is a Recording-CDR
Gateway Name23Characters2

If parameter loading is turned on, then the previously configured node name will appear in the REBOOT and SWITCHOVER records.

If parameter loading is turned off or Node Name object is never configured, this value is "None" in the REBOOT and SWITCHOVER records.

Accounting ID1864-Bit Hex3This identifier occurs in each record, and combined with the Gateway Name field uniquely identifies the call accounting information on a network basis for an extended period of time. In a REBOOT record, this is the accounting ID of the first call attempted on the GSX.
Start Time in System Ticks10Decimal4Start time in System Ticks (system tick = 10 ms) - the timestamp of when INVITE is sent out (Decimal number 0 - 4294967295).

Node Time Zone

23

Characters

5

This field can include any of the strings shown in the Time Zone section.

This page lists some GMT-based time zones, but it is possible to have any of the time zones shown in the Time Zone list.

Record Sequence Number10Decimal6

 The sequence number of this record relative to other records in the file. Depending upon how the parameter is configured, this is either:

  • a 16-bit sequence number from 0 to 65535 (5 characters maximum), or
  • a 32-bit sequence number from 0 to 4294967295 (10 characters maximum).

CS Call GCID

10

32 Bit Hex

7

Global call identifier of the communication session (CS). See CDR Field Descriptions

CS Call ID256string8SIP Call ID as received/sent by the target
Recording leg1Decimal9

The leg of the CS that is being recorded.

SIPSG_LEG_EGRESS = 0
SIPSG_LEG_INGRESS = 1

Recording Initiation1Decimal10

SIPSG_REC_TRIGGER_PSX = 1
SIPSG_REC_TRIGGER_CLI = 2

Start Time (Date)

10

mm/dd/yyyy

11Start Date (mm/dd/yyyy) - date stamp when Setup Request was sent. This value is provided by NTP

Start Time (Time)

10

hh:mm:ss.d

12Start Time (hh:mm:ss.d) (d=deci-seconds) - timestamp when Setup Request was sent, for example 16:20:38.6. This value is provided by NTP.

Time Elapsed from Sending Setup Message to 
Service Established

10

Decimal

13Time Elapsed from Transmission of Setup Message to Service Established (Receipt of Answer and Completion of Cut-through) in 10 millisecond ticks (Decimal number 0 - 4294967295).

Disconnect Time (Date)

10

mm/dd/yyyy

14Disconnect Date (mm/dd/yyyy) - date stamp when Disconnect Request was received.

Disconnect Time (Time)

10

hh:mm:ss.d

15Disconnect Time (hh:mm:ss.d) (d=deci-seconds) - time stamp when Disconnect Request was received, for example 16:20:38.6.

Disconnect Initiator

1

Decimal

16

See CDR Field Descriptions.

All values are applicable - Calling is SBC and Called is SRS

Additional value: 5: Recording terminated by CLI command


CPC_DISC_INTERNAL = 0u, /* 0 - Call released by GSX due to internal failures */
CPC_DISC_CALLING_PARTY, /* 1 - Call Released by Calling Party - NTWK originated */
CPC_DISC_CALLED_PARTY, /* 2 - Call Released by Called Party - NTWK originated */
CPC_DISC_INTERNAL_EARLY, /* 3 - Call Released by SG/FE due to internal failures
before involving CC in the call */
CPC_DISC_CALLING_PARTY_EARLY, /* 4 - Call Released by Calling Party before involving CC
in the call */
CPC_DISC_RECORDING_VIA_CLI /* 5 - Recording Via CLI*/

Call Disconnect Reason

3

Decimal

17

Recording session disconnection reason

SIPSG_REC_REL_BYE_FROM_RECORDER = 1
SIPSG_REC_REL_CALL_LEG_RELEASE = 2
SIPSG_REC_REL_INTERNAL = 3
SIPSG_REC_REL_CLEANUP = 4

Call Service Duration

10

Decimal

18Call Service Duration in 10 millisecond ticks. This count is initiated when the answer message is received and continues to increment until one leg of the call is released (Decimal number 0 - 4294967295).

Local Gateway Signaling IP Address

39

Dotted Decimal

19

SBC's local IP address used in the recording session (RS). See CDR Field Descriptions.

Remote Gateway Signaling IP Address

39

Dotted Decimal

20

SRS IP address used in the RS.

Format: See CDR Field Descriptions.

SIPREC Trunk Group Name

23

Characters

21

SIPREC TG name used for this call.

Format:See CDR Field Descriptions.

Egress Zone Name23String22SIPREC TG Zone name

Protocol Variant Specific Data

3129

Characters

23

See CDR Field Descriptions.

Only the fields corresponding to the SIP headers exchanged with the SRS are populated.

Media Stream Data Tx & Rx

(see Notes on Media Stream below)

2944 (includes double quotes at begin/end)Characters24

For this release only one stream is filled.

Format: See CDR Field Descriptions.

Media Stream Stats Tx & Rx

(see Notes on Media Stream below)

1414Characters25

For this release only one stream is filled.

Note: To reduce the size of CDRs, the SBC metadata captures only the callData body of the metadata XML. The remaining information in the metadata can be derived from other fields of this CDR.

Format: See CDR Field Descriptions.

Media Stream SRTP Statistics Tx & Rx

(see Notes on Media Stream below)

151Characters26

For this release only one stream is filled.

Format: See CDR Field Descriptions.

Metadata2047char27

Dump of the CallData in Metadata sent to SRS.
Note: To reduce the size of CDRs, the SBC metadata captures only the callData body of the metadata XML. The remaining information in the metadata can be derived from other fields of this CDR.

This is the metadata sent in the INVITE.

Note: BYE has different metadata and is ignored. GCID in metadata is not added in this field as there is a separate field for it.

SIPREC Recorder FQDN63String28FQDN of the session recording server (SRS) used in this call.
Start Time (Local)21Characters29mm/dd/yyyy hh:mm:ss.d  Local date and time stamp when Setup Request was sent. Refer to CDR Field Descriptions.
Disconnect Time (Local)21Characters30mm/dd/yyyy hh:mm:ss.d  Local date and time stamp when Disconnect Request was received. Refer to CDR Field Descriptions.
GUID128String31

The Global Unique Identifier (GUID) for calls that is unique across multiple SBCs (active-active SBCs).

Example: 10d873b3-4c36-43b4-aced-0dbca7034926609b7600000d00

Node Name256String32

This field represents the Kubernetes specific Node name on which the Pod generating the CDR is running. Refer to CDR Field Descriptions.

Example: worker-1.rco-ocp-prg1.lab.rbbn.com

Pod Name256String33

Represents the Kubernetes specific Pod name generating the CDR. Refer to CDR Field Descriptions.

Example: upgradetest-sc-f6c86dd7f-n6hn5

Container ID256String34

Represents the Kubernetes specific Container ID inside the pod generating the CDR. Refer to CDR Field Descriptions.

Example: aa790891c55c2a4c23f7a28275a1304e96585e1862bf7f060616cddc5e64b4f9


Info
titleNotes on Media Stream
  • In a recording session, the SRS does not send any media or feedback (RTCP) about the media. The following fields are applicable in this CDR, the rest are listed as 0.
    • Number of Streams = always 1 (audio) for this release
    • mediaType1 = audio
    • streamIndex1 = 1
    • Ingress packetSent1 (statistics of the Rx stream)
    • Ingress octetSent1 (statistics of the Rx stream)
    • Ingress packetDiscarded1 (policy discarded) (statistics of the Rx stream)
    • Egress packetSent1 (statistics of the Tx stream)
    • Egress octetSent1 (statistics of the Tx stream)
    • Egress packetDiscarded1 (statistics of the Tx stream)
  • Packet stats are only for packets transmitted from the SBC marked separately for each SRS stream.
  • In media stream data and statistics, the information and statistics for the Rx stream (packets from the target peer to SBC forked to --> SRS stream1) are captured in the Ingress portion, the information and statistics for the Tx stream (packets from SBC to target peer forked to SRS stream 2) are captured in the Egress portion.


Info
titleNote

The "Metadata" field in RECORDING CDR contains the dump of the updated SIPREC Metadata XML that was sent to the SRS for metaDataSource set to "fromLatest". The latest (most recent) metadata information sent towards the SRS is logged onto the RECORDING CDR.