DO NOT SHARE THESE DOCS WITH CUSTOMERS!
This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.
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.
Note
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 |
|---|---|---|---|---|
| RECORDING | 9 | Characters | 1 | The string "RECORDING" indicating this is a Recording-CDR |
| Gateway Name | 23 | Characters | 2 | 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 ID | 18 | 64-Bit Hex | 3 | This 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 Ticks | 10 | Decimal | 4 | Start time in System Ticks (system tick = 10 ms) - the timestamp of when INVITE is sent out (Decimal number 0 - 4294967295). |
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 Number | 10 | Decimal | 6 | The sequence number of this record relative to other records in the file. Depending upon how the parameter is configured, this is either:
|
10 | 32 Bit Hex | 7 | Global call identifier of the communication session (CS). See CDR Field Descriptions | |
| CS Call ID | 256 | string | 8 | SIP Call ID as received/sent by the target |
| Recording leg | 1 | Decimal | 9 | The leg of the CS that is being recorded. SIPSG_LEG_EGRESS = 0 |
| Recording Initiation | 1 | Decimal | 10 | SIPSG_REC_TRIGGER_PSX = 1 |
10 | mm/dd/yyyy | 11 | Start Date (mm/dd/yyyy) - date stamp when Setup Request was sent. This value is provided by NTP | |
10 | hh:mm:ss.d | 12 | Start 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 | 10 | Decimal | 13 | Time 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). |
10 | mm/dd/yyyy | 14 | Disconnect Date (mm/dd/yyyy) - date stamp when Disconnect Request was received. | |
10 | hh:mm:ss.d | 15 | Disconnect Time (hh:mm:ss.d) (d=deci-seconds) - time stamp when Disconnect Request was received, for example 16:20:38.6. | |
1 | Decimal | 16 | 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 */ | |
3 | Decimal | 17 | Recording session disconnection reason SIPSG_REC_REL_BYE_FROM_RECORDER = 1 | |
10 | Decimal | 18 | Call 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). | |
39 | Dotted Decimal | 19 | SBC's local IP address used in the recording session (RS). See CDR Field Descriptions. | |
39 | Dotted Decimal | 20 | SRS IP address used in the RS. Format: See CDR Field Descriptions. | |
23 | Characters | 21 | SIPREC TG name used for this call. Format:See CDR Field Descriptions. | |
| Egress Zone Name | 23 | String | 22 | SIPREC TG Zone name |
3129 | Characters | 23 | 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) | Characters | 24 | For this release only one stream is filled. Format: See CDR Field Descriptions. |
Media Stream Stats Tx & Rx (see Notes on Media Stream below) | 1414 | Characters | 25 | For this release only one stream is filled. Note: To reduce the size of CDRs, the SBC metadata captures only the Format: See CDR Field Descriptions. |
Media Stream SRTP Statistics Tx & Rx (see Notes on Media Stream below) | 151 | Characters | 26 | For this release only one stream is filled. Format: See CDR Field Descriptions. |
| Metadata | 2047 | char | 27 | Dump of the CallData in Metadata sent to SRS. 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 FQDN | 63 | String | 28 | FQDN of the session recording server (SRS) used in this call. |
| Start Time (Local) | 21 | Characters | 29 | mm/dd/yyyy hh:mm:ss.d Local date and time stamp when Setup Request was sent. Refer to CDR Field Descriptions. |
| Disconnect Time (Local) | 21 | Characters | 30 | mm/dd/yyyy hh:mm:ss.d Local date and time stamp when Disconnect Request was received. Refer to CDR Field Descriptions. |
Notes 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.
Note
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.
Overview
Content Tools