CDR Field Descriptions

Accounting Records Summary Table

The following table lists the 

 Accounting Records. Click the field name to view the description.

START

This record indicates that the call has been successfully established/connected and session has successfully started.

STOP

This record indicates that a previously established successful session has now terminated.

ATTEMPT

This record indicates that a call/session failure scenario where a call/session could not be successfully established.

INTERMEDIATE

This record captures any changes to signaling/call details during the session. For scenarios where the call duration is long, this record is also generated periodically to indicate session progress.

REBOOT

This record indicates a node reboot occurred.

SWITCHOVER

This record indicates that the node experienced a switchover that is, standby mode went to active due to a switchover initiated from the CLI or as a result of a problem on the active node.

SW_CHANGE

This record indicates an LSWU change:

• An LSWU is successfully completed.
• An LSWU is reverted.

Gateway Name

Gateway Name field (up to 23 characters).

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

Accounting ID (64 bits in HEX format).

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

Start time in System Ticks (system tick = 10 ms) - the timestamp of when Setup Request was received (Decimal number 0 - 4294967295).

Node Time Zone

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.

•     "gmt"
•     "gmt-London"
•     "gmtMinus01-Azores"
•     "gmtMinus02-MidAtlantic"
•     "gmtMinus03-BuenosAires"
•     "gmtMinus0430-Caracas"
•     "gmtMinus04-Atlantic-Canada"
•     "gmtMinus05-Bogota"
•     "gmtMinus05-Eastern-US"
•     "gmtMinus05-Indiana"
•     "gmtMinus06-Central-US"
•     "gmtMinus06-Mexico"
•     "gmtMinus06-Saskatchewan"
•     "gmtMinus07-Arizona"
•     "gmtMinus07-Mountain"
•     "gmtMinus08-Pacific-US"
•     "gmtMinus09-Alaska"
•     "gmtMinus10-Hawaii"
•     "gmtMinus11-MidwayIsland"
•     "gmtPlus01-Berlin"
•     "gmtPlus02-Athens"
•     "gmtPlus0330-Tehran"
•     "gmtPlus03-Moscow"
•     "gmtPlus0430-Kabul"
•     "gmtPlus04-AbuDhabi"
•     "gmtPlus0530-Calcutta"
•     "gmtPlus05-Islamabad"
•     "gmtPlus06-Dhaka"
•     "gmtPlus07-Bangkok"
•     "gmtPlus08-HongKong"
•     "gmtPlus0930-Adelaide"
•     "gmtPlus09-Tokyo"
•     "gmtPlus10-Guam"
•     "gmtPlus11-Magadan"
•     "gmtPlus12-Fiji"
•     "gmtPlus12-Kwajalein"

Start Time (Date)

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

In the REBOOT record, this is the date the 

 was last booted.

Start Time (Time)

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

In the REBOOT record, this is the time that the 

 was last booted.

Old Software Version

The Old Software Version field represents the 

 software running before the Live Software Upgrade occurred. This is a 14-character string using the following format:

New Software Version

The New Software Version field represents the GSX/

 software running after a Live Software Upgrade, and is a 14-character string in the following format:

Time Elapsed from Receipt of Setup Message to Policy Server/SoftSwitch Response

 [START (8) | STOP (8) | ATTEMPT (8) | INTERMEDIATE (8)]

Time Elapsed from Receipt of Setup Message to the first Policy Server/ 

 SoftSwitch Response in 10 millisecond ticks (Decimal number 0 - 4294967295).

Time Elapsed from Receipt of Setup Message to Receipt of Alerting/ProcProg

Time Elapsed from Receipt of Setup Message to Receipt of Alerting/Proc/Prog in 10 millisecond ticks (Decimal number 0 - 4294967295).

Time Elapsed from Receipt of Setup Message to Service Established

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

Intermediate Time (Date)

Intermediate Date (mm/dd/yyyy) - datestamp when Intermediate Accounting Timer expired, for example 02/06/1999.

Intermediate Time (Time)

Intermediate Time (hh:mm:ss.d) (d=deci-seconds) - timestamp when Intermediate Accounting Timer expired, for example 16:20:38.6.

Disconnect Time (Date)

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

The Disconnect Date field is not set by reading NTP time. Instead, the disconnect date stamp is calculated by adding the elapsed time between the Setup and Disconnect Messages to the Start date stamp. This indirect method ensures the difference between the Start and Disconnect Dates reflects the true duration of the call, even if the NTP server adjusted time of day during the call. See "Disconnect Time (Time)" below for an explanation and example of this method.

Disconnect Time (Time)

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

The Disconnect Time field is not set by reading NTP time. Instead, the disconnect time stamp is calculated by adding the elapsed time between the Setup and Disconnect Messages to the Start time stamp. This indirect method ensures the difference between the Start and Disconnect Times reflects the true duration of the call, even if the NTP server adjusted time of day during the call.

For example: assume a Setup Message is received at 01:00:00.0 GMT (NTP Time). Then over the next hour the NTP server rolls back NTP time by one minute. Also after exactly one hour (360000 ten-millisecond ticks) a Disconnect message is received, terminating the call. The new NTP time when this disconnect is received is 01:59:00.0 GMT (but would have been 02:00:00.0 GMT if NTP adjustment did not occur). In reality the caller spent 60 minutes on the phone, not 59. Because of the indirect disconnect time calculation described above, the GSX/

 logs disconnect time as 02:00:00.0 GMT. In summary, the disconnect time is based on the NTP start time plus elapsed time to disconnect, not the NTP disconnect time.

The elapsed time between the Setup and Disconnect Messages can be calculated by adding the "Time Elapsed from Receipt of Setup Message to Service5 Established" and "Call Service Duration" fields. The latter field measures time elapsed from service established to receipt of disconnect message.

Time Elapsed from Receipt of Disconnect to Completion of Call

Time Elapsed from Disconnect receipt to Call Termination completion in 10 millisecond ticks (Decimal number 0 - 4294967295).

Call Service Duration

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).

Call Disconnect Reason

Call Disconnect Reason (0 - 255).

The Call Termination Reason Codes are taken from the Q.931 Standard for all codes less than 128.

Codes equal to or greater than 128 are 

 Reason Codes. The Ribbon Reason Codes are never contained in messages sent to the PSTN, but are instead mapped to an appropriate Q.931 Standard code.

The Ribbon Reason Codes appear in the system event logs to give specific information about the call failure. These codes may expand in the future.

If the 

 receives a call release or call disconnect with a cause value that is not listed in the "Call Termination Reason Code" table , then that value is mapped to one of the eight Mapped To cause values listed in the  "Mapping by Cause Code Class" table below. In all cases, the Mapped To value is determined by the Class of the returned cause value as shown in the table. The Class is determined by the three high order bits of the 7-bit representation of the cause value.

For example, cause value 14 (PORTED NUMBER) may be represented as 000 1110, which is Class 000. Cause value 52 (OUTGOING CALLS BARRED) is represented as 011 0100, which is class 011. Hence, from  "Mapping by Cause Code Class" table, cause value 14 is mapped to cause value 31 (NORMAL_UNSPECIFIED) and cause value 52 is mapped to cause value 63 (SERVICE_OR_OPTION_NOT_AVAILABLE_UNSPECIFIED).

When a mapped Disconnect Code is sent to the preceding switch by the GSX/

, that Disconnect Code is also placed in either the "Call Disconnect Reason Transmitted to Egress" or the "Call Disconnect Reason Transmitted to Ingress".

ISUP Call Disconnect Code Mapping

The Call Disconnect Reason Code Mapping table provides a "single source" reference that, for each ISUP Disconnect Code received, shows the mapped Disconnect Code that is stored in the CDR that is generated by the ISUP, ISDN, H.323, and SIP services respectively. This table also shows the standard(s) that define a particular ISUP Disconnect Code.

SIP to ISUP Disconnect Code Mapping

When SIP rejection responses must be signaled to the PSTN, the mappings shown in the SIP to ISUP Disconnect Code Mapping table are recommended by RFC 3398 and implemented by Ribbon. If the SIP rejection message contains an encapsulated REL message, then the Cause Indicator (CAI) parameter in the generated REL gets set to the value of the CAI parameter received in the encapsulated REL.

Whenever a Reason Header is encountered in any SIP message (such as BYE, CANCEL, 4xx, or 5xx), the GSX/

 will use the Reason Header cause value for the Disconnect Code.

If the Reason Header is absent from the message, the ISUP Multipurpose Internet Mail Extension (Mime) cause value, if available, is used for the Disconnect Code. Otherwise stated, the GSX/

 precedence for deriving the Disconnect Code in SIP/ISUP interworking is:

• Reason Header
• ISUP Mime (if cause value is available)

This conforms to RFC 3398 recommendations. You may configure the PSX IP PROFILE object to reverse this mapping behavior, thus conforming to the Q.1912.5 recommendation.

Service Delivered

This field identifies the service delivered for VoIP/Circuit Switched Voice (up to 22 characters).

• For PSTN-to-PSTN calls, such as ISUP-to-ISUP, ISUP-to-ISDN, ISUP-to-CAS calls, this field is "Circuit Switched Voice."
• For calls involving packetized voice, such as GSX/
  Unable to show "metadata-from": No such page "_space_variables"
   gateway-to-gateway signaling, H.323, and SIP, this field is "VoIP."
• When an ATTEMPT record is generated by a blocking script, this field is set to "UNKNOWN" (since the call was not established, the Service Delivered is undefined or UNKNOWN).
• When an ATTEMPT record is generated after the GSX/
  Unable to show "metadata-from": No such page "_space_variables"
   routes the call, and then a subsequent switch disconnects the call before the call is established, this field is populated with a valid value.
• When a START, STOP, or INTERMEDIATE record is generated by a successfully established call, this field is populated with a valid value.

Call Direction

This field (up to 12 characters) defines the call direction, such as:

• PSTN-TO-IP
• PSTN-TO-PSTN
• IP-TO-PSTN
• PSTN-TO-TERM
• IP-TO-TERM
• TERM-TO-PSTN
• TERM-TO-IP
• IP-TO-IP

The first stage of a two stage call is either PSTN-TO-TERM or IP-TO-TERM. The second stage of a two stage call is either TERM-TO-PSTN or TERM-TO-IP.

This field conveys the signaling scenario for the call, including whether ingress is a PSTN signaling/IP signaling, and whether egress is PSTN signaling/IP signaling. For example, a call that has ingress signaling as ISUP and egress signaling as ISUP, Call Direction = "PSTN-TO-PSTN". For a call that has ingress signaling as H.323, and egress signaling as ISDN, Call Direction = "IP-TO-PSTN". For a call that has ingress signaling as CAS, and egress signaling as GSX/

 gateway-to-gateway protocol, Call Direction = "PSTN-TO-IP". A call that has ingress signaling as H.323, and egress signaling as GSX/ gateway-to-gateway protocol shows Call Direction = "IP-TO-IP".

When an ATTEMPT record is generated by a blocking script, this field is set to UNKNOWN (since the call is not established, Call Direction is undefined or UNKNOWN).

When an ATTEMPT record is generated after the GSX/

 routes the call, but a subsequent switch disconnected the call before the call is established, this field is populated with a valid value.

When a START, STOP, or INTERMEDIATE record is generated by a successfully established call, this field is populated with a valid value.

Service Provider

This field (up to 23 characters) is populated with the route partition ID the PSX used for routing a call.

Transit Network Selection Code

This ISUP signaling parameter field (string up to four characters, for example 0288) is populated using either the information received in the IAM (if ingress signaling is ISUP) or information returned by the PSX in a policy response. The PSX obtains information from configuration tables. If the ingress signaling group and the PSX do not provide a value for this field, this field is empty.

Calling Number

The Calling Number Address Digits are sent out on the egress signaling side, and is the end result of any digit manipulations and address translation performed by the PSX during the policy request processing on the calling number received from ingress signaling.

Called Number

The Called Number Address Digits are sent out on the egress signaling side, and is the end result of any digit manipulations and address translation performed by the PSX during the policy request processing on the called number received from ingress signaling.

Extra Called Address Digits

This field is a string not used in routing the call, and is received via Overlap Address Messages such as SAM. This field is significant when the ingress signaling protocol supports overlap addressing (for example, SAM messages in ISUP, INFO messages in ISDN), and contains any digits obtained by the GSX/

 after successfully routing the call based on digits collected before receiving overlap address signaling message.

For example, if GSX/

 receives "978-321" in the IAM, we route the call using these digits, and subsequently receive a SAM message with 1234, the accounting records contains:

• Called Number = 978-321
• Extra Called Address Digits = 1234

Number of Called Num Translations Done by This Node

This field defines the number of called number translations performed on the node (length: decimal 0-2).

This and the following fields carry information about TollFree/LNP translation performed by the PSX.

• Called Number Before Translation #1
• Translation Type 1
• Called Number Before Translation #2
• Translation Type 2

For example the called number received by the GSX/

 in the incoming IAM is 1-800-123-1234. The PSX performs toll-free translation, and the result is 617-123-1234. Subsequently, it performs LNP translation, and the result is 781-123-1000.

In this case, the following applies:

Called Number = 781-123-1000
Number of Called Num Translations Done by This Node = 2
Called Number Before Translation #1 = 1-800-123-1234
Translation Type 1 = 2
Called Number Before Translation #2 = 617-123-1234
Translation Type 2 = 1

In another example, if the called number in the incoming IAM was 617-123-1234, and the PSX performs an LNP translation, the result is 781-123-1000. Consequently, the accounting records contains:

Called Number = 781-123-1000
Number of Called Num Translations Done by This Node = 1
Called Number Before Translation #1 = 617-123-1234
Translation Type 1 = 1
Called Number Before Translation #2 – Empty
Translation Type 2 - 0

Called Number Before Translation #1

This field contains the called number before the first translation is performed, and carries information about TollFree/LNP translation performed by the PSX.

This field is empty ("") if no translations are performed, and occurs when the Translation Type 1 field is "0" (CPC_ADDR_TRANS_NONE) See "Translation Type 1" for details.

This field is also empty ("") when all of the following conditions are true:

• The dialed number is ported (an LNP query is performed).
• The SCP response to LNP query did not return an LRN (i.e. translated number).
• The Translation Type 1 field is "1" (CPC_ADDR_TRANS_LNP); that is, the LNP was the first translation attempted by the PSX.
• Translation is turned OFF via configuration.

This field is populated in an ATTEMPT record in the absence of a PSX query response if the preceding switch performs the translation and call is torn down before PSX response is received. The presence of the M bit in the received ISUP Initial Address Message (IAM) External Furnish Charging Info (FCI) message indicates that the preceding switch has performed the translation.

Translation Type 1

This field carries information about the first translation performed by the PSX:

• 0 - CPC_ADDR_TRANS_NONE (no translation performed)
• 1 - CPC_ADDR_TRANS_LNP (Local Number Portability)
• 2 - CPC_ADDR_TRANS_TOLLFREE (8xx Numbers)
• 3 - CPC_ADDR_TRANS_PRIVATE

Called Number Before Translation #2

This field contains the called number before the second translation is performed, and carries information about TollFree/LNP translation performed by the PSX.

This field is empty ("") if less than two translations are performed, and occurs when Translation Type 2 field (see "Translation Type 2") is "0" (CPC_ADDR_TRANS_NONE).

This field is also empty ("") when all of the following conditions are true:

• The dialed number is ported (an LNP query is performed).
• The SCP response to the LNP query did not return an LRN; that is, a translated number.
• The Translation Type 2 field is "1" (CPC_ADDR_TRANS_LNP); that is, the LNP is the second translation attempted by the PSX.
• Translation is turned OFF via configuration.

Translation Type 2

This field carries information about the second translation performed by the PSX:

• 0 - CPC_ADDR_TRANS_NONE (no translation performed)
• 1 - CPC_ADDR_TRANS_LNP (Local Number Portability)
• 2 - CPC_ADDR_TRANS_TOLLFREE (8xx Numbers)
• 3 - CPC_ADDR_TRANS_PRIVATE

Billing Number

This field is a string of up to 30 characters. The record is populated using the following precedence:

• If SCP returns a billing number, it takes precedence over the others.
• If billing number is present in the incoming signaling message, then it is used.
• If there is no billing number returned by SCP or in the incoming signaling message, the billing number configured against the ingress trunk on the PSX is used.

Route Label

This record is a string of up to 23 characters. The content of this record depends upon the type of call route that is returned from the PSX:

• If a normal route is returned, this field contains the ROUTING_LABEL pointed to by the route record. The Overflow and Fallback labels are not present.
• If an SCP produced route made up of Gateway Name and Trunkgroup ID (as provisioned on the PSX) is returned, this field is empty ("").
• If an SCP produced route made up of Switch ID and Trunkgroup ID (as provisioned on the PSX) is returned, this field will contain the Route Label (RL) corresponding to the first Switch ID/Trunkgroup.

The PSX supports to send RL for each route of a call in the policy response message to the SBC. The flag Enable Per Route Routing Label is added to the Feature Control Profile (FCP) entity screen. When the flag Enable Per Route Routing Label is enabled on the PSX, the PSX returns the RL for each route. The SBC stores these RLs in the CDR records for each call.

• When the flag Enable Per Route Routing Label is enabled, the CDR RL field is populated from the per-route data returned from the PSX.
• When the flag Enable Per Route Routing Label is disabled, the SBC stores the per-call routing label returned from the PSX in the CDR Routing Label field.

Route Attempt Number

The Route Attempt Number (Decimal number 0 - 65535).

Route Selected

The route selected:

• Gateway Name (up to 27 characters) Example: SBX140
• TG Name (up to 23 characters) Example: IPTG-NAV2

If Gateway Name is unknown, Gateway IP Address displays according to address type:

• IPv4 address—dotted decimal format (for example 128.1.22.233 (up to 15 characters))
• IPv6 address—eight 16-bit hexadecimal values separated by colons (for example 1280:1276:3350:2224:2222:3333:8888:1245).

Egress Local Gateway Signaling IP Address

For packet based egress trunk groups, the IPv4 or the IPv6 address can be used for egress signaling on the local 

.

• For IPv4 address type, use the dotted decimal format (for example, 128.1.22.233)
• For IPv6 address type, use the hexadecimal format (for example, 3ffe:1900:4545:3:200:f8ff:fe21:67cf (up to 39 characters)).

The local 

 generates this accounting record; the device at the far end of the packet network is the remote address.

If the egress trunk group is circuit-based, this field is empty ("").

Egress Remote Gateway Signaling IP Address

 For packet-based egress trunk groups, the IPv4 or the IPv6 address can be used for egress signaling on the far end of the packet network.

• For IPv4 address type, use the dotted decimal format (for example, 128.1.22.233)
• For IPv6 address type, use the hexadecimal format (for example, 3ffe:1900:4545:3:200:f8ff:fe21:67cf (up to 39 characters)).

The local GSX/

 generates this accounting record; the device at the far end of the packet network is the remote address. The device at this address may be another GSX/ gateway, and H.323 device, or a SIP device.

If the egress trunk group is circuit based, this field is empty ("").

Ingress Trunk Group Name

The origination gateway logs the name of the external trunk group which exists between the ingress network and the origination gateway in this field. The destination gateway logs the name of the internal IP trunk group which exists between the origination gateway and destination gateway in this field.

Ingress PSTN Circuit End Point

Ingress PSTN Circuit End Point field – Shelf (1-6):Slot (1-16):Port (1-84):DS0 (1-32):CIC (1-65535):Local Point Code (32 bit HEX format): Remote Point Code (32 bit HEX format). 

The Port range of 1-84 applies to calls that are assigned to a CNS60 or CNS71 module. 1-28 are the T1 circuits on the first T3, 29-56 are the T1 circuits on the second T3, and 57-84 are the T1 circuits on the third T3.

Ingress IP Circuit End Point

Ingress IP Circuit End Point field applies to both local and remote IP addresses.

• Local IP Address: Port (0-65535)
• Remote IP Address: Port (0-65535)

The IP address can be in IPv4 or IPv6 format. For IPv4 address type, use dotted decimal format. For example, 128.1.22.233 (up to 15 characters).

For IPv6 address type, use hexadecimal format. For example, 3ffe:1900:4545:3:200:f8ff:fe21:67cf (up to 39 characters).

The default IP address 127.0.0.0 is taken as remote IP address and the default port 5004 is taken as remote port when a NAT call is made without sending media from the endpoints.

Egress PSTN Circuit End Point

Egress PSTN Circuit End Point field – Shelf (1-6):Slot (1-16):Port (1-84):DS0 (1-32):CIC (1-65535):Local Point Code (32 bit HEX format): Remote Point Code (32 bit HEX format).

The Port range of 1-84 applies to calls that are assigned to a CNS60 or CNS71 module. 1-28 are the T1 circuits on the first T3, 29-56 are the T1 circuits on the second T3, and 57-84 are the T1 circuits on the third T3.

Egress IP Circuit End Point

Egress IP Circuit End Point field applies to both local and remote IP addresses.

• Local IP Address: Port (0-65535)
• Remote IP Address: Port (0-65535)

The IP address can be in IPv4 or IPv6 format. For IPv4 address type, use dotted decimal format. For example, 128.1.22.233 (up to 15 characters).

For IPv6 address type, use hexadecimal format. For example, 3ffe:1900:4545:3:200:f8ff:fe21:67cf (up to 39 characters).

The default IP address 127.0.0.0 is taken as remote IP address and the default port 5004 is taken as remote port when a NAT call is made without sending media from the endpoints.

Ingress Number of Audio Bytes Sent

Number of Audio Bytes Sent as recorded by the ingress DSP/NP (decimal representation of a 64 bit number: 1 - 1.844674407*10¹⁹).

Ingress Number of Audio Packets Sent

Number of Audio Packets Sent as recorded by the ingress DSP/NP (decimal representation of a 64 bit number: 1 - 1.844674407*10¹⁹).

Ingress Number of Audio Bytes Received

Number of Audio Bytes Received as recorded by the ingress DSP/NP (decimal representation of a 64 bit number: 1 - 1.844674407*10¹⁹).

Ingress Number of Audio Packets Received

Number of Audio Packets Received as recorded by the ingress DSP/NP (decimal representation of a 64 bit number: 1 - 1.844674407*10¹⁹).

Originating Line Information (OLIP)

Originating Line Information (OLIP), also known as info digits which are expressed as decimal values.

The values in the following table match ANSI T1.113 (ANSI ISUP).

Jurisdiction Information Parameter

In Local Number Portability (LNP) applications, Jurisdiction Information Parameter (JIP) provides the Local Routing Number (LRN) assigned to the originating number, which is then used to determine proper billing for the call (string up to 15 characters).

Carrier Code

The carrier identification code (up to five characters) of the carrier used for carrying the call on the egress trunk (for example 0288). This code is provided by the ingress signaling group from the appropriate parameters in its signaling protocol. For example, ISUP obtains it from the Carrier Identification Code parameter in an IAM message, or from the PSX in a policy response. If the ingress signaling group and the PSX do not provide a value, this field is empty.

Call Group ID

An internal identifier (up to 32 bits of hexadecimal data) bound to each call used by the GSX/

 to group calls associated to each other. Multiple calls (with different Global Call IDs) involved in transfer and redirection scenarios have the same Call Group ID.

Example: "0x0000002F" 

Script Log Data

A string that contains data logged by a 

 CPL script that was executed for the call.

Multiple variables are  logged within this field, with each variable data separated from the next variable by a configurable separator. The default value for the separator is a "/". The data for each script variable includes the variable ID and the variable value, with a ":" as the separator. For example, the data string: 

12:9786928999/108:12345
indicates data for two variables, variable ID - 12, and variable ID - 108. The value of variable 12 is 9786928999, and the value of variable 108 is 12345.

This field is applicable only if a Ribbon CPL script is executed for the call. The sub-fields within this field are all variables associated with the CPL script, and are a concatenation of the variables requested by the script to be logged. This field is populated only if a CPL script was executed for the call, and the script requested logging of script variables via the LOG SIBB in the script.

Time Elapsed from Receipt of Setup Message to Receipt of Exit Message

The time elapsed from receipt of setup message to receipt of exit message in 10 ms ticks (decimal number 0 - 4294967295).

Time Elapsed from Receipt of Setup Message to Generation of Exit Message

Time Elapsed from Receipt of Setup Message to Generation of Exit Message (EXM) in 10 ms Ticks (Decimal number 0 - 4294967295).

Calling Party Nature of Address

The type of Calling Party number (decimal value).

For more information on the nature of the address enumeration values, refer to Nature of Address Enumeration Values.

Called Party Nature of Address

The type of Called Party number (decimal value).

For more information on the nature of the address enumeration values, refer to Nature of Address Enumeration Values.

Ingress Protocol Variant Specific Data

A string of up to 1849 characters or empty with delimiters "". Whenever any ingress service group has Protocol Variant Specific Data to log, this data is logged to this field. See the following pages for specific variants:

• H.323 Signaling Sub-field Descriptions
• SIP-I Signaling Sub-field Descriptions
• SIP Variant Sub-field Descriptions
• Gateway-to-Gateway Signaling Sub-field Descriptions

Ingress Signaling Type

The ingress signaling type (decimal value).

For signaling type enumeration values, refer to Signaling Type Enumeration Values.

Egress Signaling Type

The egress signaling type (decimal value).

For signaling type enumeration values, refer to Signaling Type Enumeration Values.

Ingress Far End Switch Type

The ingress far end switch type (decimal value).

For mor information on far end  switch type, refer to Far End Switch Type Enumeration Values.

Egress Far End Switch Type

The egress far end switch type (decimal value).

For mor information on far end  switch type, refer to Far End Switch Type Enumeration Values.

Far End Ingress TG Carrier Code

The Field content depends upon whether the PSX is supporting a JAPAN variant.

If the JAPAN variant is being supported, then this field is the "Own Carrier ID" that is provisioned against the ingress trunk group, and is a string of up to five characters, for example "0288".

If a Non-JAPAN variant is being supported, then this field is the Carrier Code of the carrier that owns the Far End of the ingress trunk group. This is a string of up to 5 characters.

The "Trunk Ownership Fields in START/STOP Records" figure illustrates a typical PSTN-to-PSTN network in which the local GSX/

 is writing accounting records to its NFS (DSI Level 0) file system. This figure depicts the Carrier Identification Codes that are contained in the Carrier Code of the Carrier that Owns the Far End of the Ingress/Egress Trunk Group fields.

 

Field content depends upon whether the PSX is supporting a JAPAN variant.

This field is a string of up to five characters, and is populated using the following precedence:

• If a Non-JAPAN PSX variant is being supported, and the SCP returns digits within the AMADigitsDialedWC, and if the Context Identifier Digits within the AMADigitsDialedWC are "003", then these (SCP returned) digits are placed in the record.
• If a Non-JAPAN PSX variant is being supported and the above conditions are not true, then the Carrier Code of the Carrier that owns the Far End of the egress trunk group is placed in the record. See Figure A – 2, "Trunk Ownership Fields in START/STOP Records" for more explanation about this Carrier Code.
• If a JAPAN PSX variant is being supported, then the "Own Carrier ID" that is provisioned against the egress trunk group is placed in this record.

In all cases, a string of up to five characters is placed in this record (for example "0288").

Calling Party Category

The Calling Party Category (CPC) field is a hexadecimal value between 0x00 and 0xff. All letters are lower case and leading zeros are always displayed. The length is always four characters, two for the "0x" and two more for the CPC value.

The Calling Party Category Enumeration Values table lists the valid CPC hex values.

Dialed Number

On the ingress GSX/

, this is the actual dialed number contained in the incoming setup message (IAM) received by the GSX/ from the ingress signaling group before any digit manipulation or address translations are performed by the ERE.

On the egress GSX/

, this is the called number from the Gateway-to-Gateway signaling message, and contains digit manipulations performed by the ERE.

Carrier Selection Information

The ISUP Carrier Selection Information parameter (decimal value) populated either by the ingress ISUP SG or by the PSX in a policy response. If neither the ingress ISUP SG or PSX supplies this field, it takes a value of "0".

The following table lists the valid decimal values.

Table8: Carrier Selection Information Enumeration Values 

Called Number Numbering Plan

A decimal value indicating the numbering plan type used for the called number representation. It could be one of ISDN/DATA/TELEX/PRIVATE. The numbering plan for the called number is provided by the ingress signaling group (based on parameters obtained in its signaling messages, or using defaults appropriate to the protocol type), or provided by the PSX in the PSX in the policy response (if it provides a called number in the policy response).

The Numbering Plan Indicator (NPI) range includes ISUP Reserve/Spare values. The block of ISUP NPI enumerations (0 to 7) is appended to the existing 

 enumerations of 0-7. The combined NPI valid decimal value range is shown in the below table.

NPI values less than "8" are interpreted as Ribbon NPIs. Values greater than "7" are ISUP (Spare/Reserve) NPIs, to be derived by subtracting "8" from the record value. For example, a record value of "10" is an ISUP 2 NPI (10-8).

ISUP NPIs which map to a 

 NPI are generated without any offset.

Generic Address Parameter

This field is the original called number if LNP is performed by a switch preceding the GSX/

. This field is applicable only if the ingress signaling group is ISUP, and if the IAM indicates that LNP translation was performed by a switch preceding the GSX/ . In this case, the field contains the contents of the ISUP Generic Address Parameter (GAP) digits which contain the called number before the LNP translation is done by the prior switch, as per ISUP protocol.

Disconnect Initiator

This field (decimal in range 0-4) identifies how the initiator session is closed:

• 0 - INTERNAL

Released internally by the call control entity in the GSX

, due either to some error in the processing of the call or to a release initiated by a party on the peer call in a multiparty feature such as ISDN Two B-Channel Transfer or SS7 Release Link Trunking.

• 1 - CALLING PARTY

Released by the ingress signaling group.

• 2 - CALLED PARTY

Released by the egress signaling group.

• 3 - INTERNAL EARLY

Released internally by GSX/

 at early call attempt stage. Applies only to the ATTEMPT record.

• 4 - CALLING PARTY EARLY

Released by the calling party at an early call attempt stage. Applies only to the ATTEMPT record.

EARLY disconnects may occur before a PSX Policy Request is sent or a PSX Policy Response is received due to an incomplete setup message or a setup message immediately followed by a disconnect from the calling party.

Call Release and/or SIP Response Codes

ATTEMPT records

The following table describes the mapping of CDR field numbers and their call disconnect reasons for ATTEMPT records.

STOP records

The following table describes the mapping of CDR field numbers and their call disconnect reasons for STOP records.

Ingress Number of Packets Recorded as Lost

The number of packets recorded as a lost packet by the ingress DSP/NP. This field is a decimal representation of a 32-bit number (applicable to RTCP statistics for VoIP calls only).

Egress Packets Lost

The number of packets recorded as a lost packet by the egress DSP/NP. This field is a decimal representation of a 32-bit number (applicable to RTCP statistics for VoIP calls only).

Ingress Interarrival Packet Jitter

The maximum interarrival packet jitter time (in millisecond) recorded by the ingress DSP/NP. This field is a decimal representation of a 16-bit number, hence must be in the range 0-65535 (This is applicable to RTCP statistics for VoIP calls only).

Ingress Last Measurement for Latency

The last measurement for latency (in milliseconds) as recorded by the ingress DSP. This field is a decimal representation of a 16-bit number, hence must be in the range 0-65535 (applicable to RTCP statistics for VoIP calls only).

Egress Trunk Group Name

This field is applicable for IP-PSTN, PSTN-PSTN, PSTN-IP, and IP-IP calls. (String up to 23 characters.)

The origination gateway logs the name of the internal IP trunk group which exists between the destination gateway and the origination gateway in this field. The destination gateway logs the name of the external trunk group which exists between the destination gateway and the egress network in this field.

Egress Protocol Variant Specific Data

The egress service group protocol variant-specific data. This field is a string of up to 1849 characters, or empty with delimiters "". Whenever any egress service group has protocol variant-specific data to log, the data is logged to this field. See the following pages for specific variants:

• H.323 Signaling Sub-field Descriptions
• Release Link Trunking Sub-Fields
• SIP-I Signaling Sub-field Descriptions
• SIP Variant Sub-field Descriptions
• Gateway-to-Gateway Signaling Sub-field Descriptions

Incoming Calling Number

This field represents the calling number presented to the 

 prior to any digit manipulation or translation by the PSX/ERE. In other words, it is the Calling Number in the Incoming Signaling Message (IAM/SETUP etc.) to the  translation.

Intermediate Record Reason

This field indicates the reason the Intermediate Record is generated:

• 0 - (PERIODIC) The intermediate accounting interval expired for this call, a normal event.
• 1 - (MTP_PAUSE_EVENT) An SS7 Server link failure occurred.
• 2 - (SS7_CONNECTION_FAILURE) The connection to the SGX was lost.
• 3 - (MALICIOUS CALL TRACE) A Malicious Call Trace was initiated (BT-IUP only).
• 4 - (Telcordia Long Duration) The call was active, and had been active for a time which is more than the configured threshold value, at the specified Telcordia Long Duration Generation Time.

AMA Call Type

The Automatic Message Accounting (AMA) Call Type field (also known as AMA Call Code) is provided by the 

 PSX and determines how the call is billed, such as Flat Rate, Local Measured, EAS, etc. If AMA Call Type is not available, this field is empty (""). (3-digit decimal number in the range 000-999, with leading zeroes always present.)

Message Billing Index (MBI)

This field is determined from the class of service of the calling subscriber together with the office to which his call is directed, and constitutes the basis for determining the charging rate on bulk billed calls where the called number is not recorded in AMA field.

This field is provided by the 

 PSX. If MBI is not available, this field is empty (""). (3-digit decimal number in the range 000-999, with leading zeroes always present.)

Originating LATA

The Originating Local Access and Transport Area (LATA) field. A LATA is a geographical area defined by the FCC within which a local telephone company may offer telecommunications services.The Originating LATA is provided by the 

 PSX in the Policy Response. (3-character string.)

Route Index Used

This field signifies which route in the policy response was used for this call. If no routes were successful, then this field is empty (""). The policy response can only hold from 1 to 10 routes. See also Cumulative Route Index.

The Route Index can be combined with the Routing Label (see  Route Label) to determine the chosen route.

Calling Party Number Presentation Restriction

This field (decimal number, 0-4) indicates the calling party number Presentation Restriction using one of the values below:

• 0 - INVALID
• 1 - ALLOWED
• 2 - RESTRICTED
• 3 - NUMBER_UNAVAILABLE
• 4 - SPARE

Incoming ISUP Charge Number

This field is extracted from the ISDN User Part (ISUP) Initial Address Message (IAM) received on an SS7 trunk. If the number is not available this field is empty (""). (String up to 30 characters.)

Incoming ISUP Charge Number NOA

The Incoming ISUP Charge Number Nature of Address (NOA) field (decimal number in the range 0-255).

Dialed Number NOA

The Dialed Number Nature of Address (NOA) field. (Decimal number from 0-255.)

Ingress Codec Type

This field defines the Ingress Codec type, and consists of a string with a maximum of six characters (the two colons in the field are included in this count) in the following format. If audio encoding is not applicable, this field is set to "0".

<networkType>:<codecType>:<audioEncoding>

 Examples:

• A G.711 packet call with aLaw encoding will be displayed as: “P:1:2”

• A T.38, version 0 call will be displayed as: “P:6:0”

• A T.38, version 3 call will be displayed as: “P:6:3”

See the table for a listing of Ingress Codec Type sub-field variables.

Egress Codec Type

This field defines the Egress Codec Type, and consists of a string with a maximum of six characters (the two colons in the field are included in this count) in the following format.

<networkType>:<codecType>:<audioEncoding>

Examples:

• A G.711 packet call with aLaw encoding will be displayed as: “P:1:2”

• A T.38, version 0 call will be displayed as: “P:6:0”

• A T.38, version 3 call will be displayed as: “P:6:3”

See the table for a listing of Egress Codec Type sub-field variables.

Ingress RTP Packetization Time

Decimal value indicating the duration of RTP packets in milliseconds, as recorded by the DSP in the resource chain on the ingress leg of the call. If no DSP resources are allocated on the ingress leg of the call, then this field is empty ("").

SBC Call ID

This field, assigned by the GSX/

, uniquely identifies a call within a single  and hence is equivalent to the 's internally assigned Global Call ID (GCID). This value is unique for this call within a , but will vary from  to . Use the Gateway-to-Gateway Handle to uniquely identify a call across multiple s. (32-bit hexadecimal value, prefixed by "0x", such as 0x89ABCDEF.)

Terminated with Script Execution

This field (decimal, 0-1) identifies whether or not a script was executed before terminating the call. Possible values:

• 0 – the call was terminated without executing a script.
• 1 – the PSX returned a script executed by the GSX/
  Unable to show "metadata-from": No such page "_space_variables"
   before terminating the call; the call was not routed.

Originator Echo Cancellation

This field (decimal, 0-1) identifies whether or not the GSX/

 performed echo cancellation on the ingress leg of this call. Possible values:

• 0 – GSX/
  Unable to show "metadata-from": No such page "_space_variables"
   did not perform echo cancellation on ingress leg of call.
• 1 – GSX/
  Unable to show "metadata-from": No such page "_space_variables"
   performed echo cancellation on ingress leg of call.

This applies only to PSTN to IP and PSTN to PSTN calls. If the call is IP to PSTN, this field is empty ("").

Terminator Echo Cancellation

This field indicates if GSX/

 performed echo cancellation on the egress leg of this call as follows:

• 0 – GSX/
  Unable to show "metadata-from": No such page "_space_variables"
   did not perform echo cancellation on egress leg of call.
• 1 – GSX/
  Unable to show "metadata-from": No such page "_space_variables"
   performed echo cancellation on egress leg of call.

This field applies only to IP to PSTN and PSTN to PSTN calls. If the call is PSTN to IP, this field is empty ("").

Charge Flag

The Charge Indicator values provisioned on the PSX. These values apply to the Ingress Trunk Group and are shown in the table below.

AMA Service Logic Identification

This field (AMAslpID) is used in an Advanced Intelligent Network (AIN) environment to record the identification of the service logic in the Service Control Point (SCP). (fixed 9-digit decimal number, with any leading zeroes present).

The table below describes the AMAslpID values. The PSX provides this data in Binary Coded Decimal (BCD) format, and the GSX/

 software converts these strings to the fixed 9-character fields described below. If the BCD string contains more than 9 digits, the converted string is truncated. The terminating sign nibble in the BCD string (typically 0xC) is not present in the AMAslpID field.

If this data is unavailable, this field is empty ("").

See GR-1100-CORE, Section 2 for more detail about this native data.

AMA BAF Module

The Billing Automatic Message Accounting Format (BAF) module is used to record a variety of billing information. The first three characters represent the Module Code Identification that, in turn, specifies how to interpret the remaining characters. See the below table for these codes.

The remaining characters are defined in Section 1.4 "Data Fields" of the Telcordia Technologies Generic Requirements (GR-1100-CORE) Issue 4. Refer to that document for all definitions.

A string of 4-256 hexadecimal characters. If the BAF Module is unavailable, this field is empty ("").

The BAF Module Names table lists each valid BAF Module code and name as published in Telcordia Technologies Generic Requirements (GR-1100-CORE) Issue 4. The Telcordia document defines BAF Module names.

AMA Set Hex AB Indication

AMA Set Hex AB Indicator:

• "1" - AMA BAF Module contains a known or suspected error.
• "0" - AMA BAF Module contains no known errors.
• "" - (empty) AMA BAF Module is not present.

Service Feature ID

This field is a BAF parameter indicating a customer's originating or terminating line characteristics. This indication may be used by an accounting application to assess applicable tariffs to determine the price for services rendered.

This ID, if available, is provided by PSX/ERE as a fixed 3-digit decimal number. If no data is available, this field is left empty ("").

The GSX/

 passes this data to the accounting record unchanged. The terminating sign nibble (typically hexadecimal C) is not propagated to the accounting record.

The Service Feature IDs table lists valid Service Feature IDs.

FE Parameter

An optional parameter in backwards call control messages (ACM, CPG, ANM, and Gateway-to-Gateway signaling).

If the egress GSX/

 is the terminating switch, then the GSX/ generates this parameter. Otherwise, the downstream legacy switch generates this parameter, and then the GSX/ logs and forwards it to the accounting record.

If the FE Parameter is not present, this field is left empty ("").

The record is generated in one of two formats:

• Short Form—16 hexadecimal characters representing 8 bytes of binary data.
• Long Form—20 hexadecimal characters representing 10 bytes of binary data.

The Parameter Length field of the record designates whether the record is the Short Form or the Long Form.

The following tables depict each of these forms.

The Answer Type and Completion Code (manner by which the call was terminated) are 4-bit values, depicted in the following table.

Example:

The FE Parameter record below:
"0xFE0812BC0A006745DF03"
...is generated by the following FE Parameter subfield values:

Format = Long Form
Completion Code = Treated Call (1)
Answer Type = Software Answer, voice detected (2)
Final Trunk Group ID = 0xABC
Final Switch ID = 0x3DF
Final Trunk Member = 0x4567 

Satellite Indicator

Satellite Indicator (SAT):

• "1" - A satellite trunk was used.
• "0" - No satellite trunk was used, or a non-ISUP signaling variant such as ISDN or CAS was used.

This value is extracted from the Nature of Connection Indicator.

PSX Billing Information

The following figure displays a high level view of the PSX Billing Information field within an accounting record. This field contains billing data generated by the PSX that is encoded in bytes represented as hexadecimal characters (00 to FF). This variable length field may contain up to 128 bytes of binary data (represented by 256 hexadecimal characters).
Every subfield in the PSX Billing Info field is provisioned on the PSX and placed into the 

 accounting record. Therefore, the results reflect particular PSX provisioning of the PSX Billing Info entity. Take this into consideration when viewing the example representations at the end of this section. Do not expect similar results in your records unless you provision each PSX Billing Info subfield in the same manner.

The PSX Billing Info field is divided into four portions:

• Header
• Common
• Route Specific Tag
• Route Specific Data

Each portion is a series of one or more subfields.

The Billing File Info Header contains a unique 16 bit value.

The Common and Route Specific Tag portions are comprised of subfields that consist of a unique Tag, a Tag Data Length Indicator, and Data for that Tag (or value). In any of these subfields, the one byte Tag Data Length Indicator could be zero, resulting in a zero length value.

The Route Specific Data portion is comprised of subfields of Tag Data Length Indicator and Data for that Tag (or value), for each Tag, for each route. In this portion, the Tags themselves were defined in the Route Specific Tag portion and hence are not present in the subfields.

This subfield detail is depicted below:

Billing Info Variant

This field contains a two byte Billing Information Variant. This subfield is provisioned on the PSX. This field is always occupied by four hexadecimal characters representing two bytes of binary data. A user provisioned Billing Information Variant of 0000 is depicted below.

Tag, Length, and Tag Data

The Billing information Variant Data table lists the Tags, Tag Data lengths, and Tag Data descriptions that apply to the Billing Information Variants. In this table, the Max Length is the value provisioned in the PSX Billing Info entity. The Max Length value is always less than or equal to the Max Length Limit value, which is hard coded into the entity.

As mentioned previously, every Tag/Length/Value subfield and Route Specific Length/Value must be provisioned in the Billing Info entity on the PSX in order to be present in any accounting record. Furthermore, the Billing Info Profile ID that is provisioned on PSX must be associated with the (ingress) trunk group entity, also on the PSX. See the "PSX Policy Server Provisioning Guide" for these procedures.

When the length of the data that contains integer or hex digits is an odd number, the most significant byte will have a leading "0".

When the length of the data that contains BCD digits is an odd number, the most significant byte will have a leading "F".

The SCP may return certain values more than once. If this is the case, the corresponding subfield is populated in the PSX Billing Info field once per SCP reply. Data from each reply is appended to the end of Common Portion field, so the first occurrence of a subfield corresponds with the first SCP reply, the next occurrence with the second reply, and so on. The following SCP subfields may be populated more than once in PSX Billing Info field:

• 0002 – SCP Pin Digits
• 0006 – SCP returned Supp Dig
• 0007 – SCP Call Info
• 0008 – SCP Bill

Example 1

The following PSX Billing Info field is defined in the following table.

00000005000001010603E903F60389000901F1000B03F978580004022345000A01F1000D03F97869000E0100000F010000100A4D696C696E6473204269000C03F60346001304F46089800FA0040FA10FA20100010F01000109010001090100010901000109

Example 2

The PSX Billing Information record below

000100010101000203F1234500030120000403022345000501990006029876000701000008045678EF9A03E905978555121200070122

Originating TDM Trunk Group Type

This field is supplied by the PSX, after customer specific provisioning. If this field is not provisioned on the PSX, it is left empty ("").

For more information on the TDM Trunk Group Type, refer to TDM Trunk Group Type Enumeration Values.

Terminating TDM Trunk Group Type

This field is supplied by the PSX, after customer specific provisioning. If this field is not provisioned on the PSX, it is left empty ("").

For more information on the TDM Trunk Group Type, refer to TDM Trunk Group Type Enumeration Values.

Ingress Trunk Member Number

Ingress Trunk Member Number. The ingress trunk member number that was provisioned on the GSX/ 

  circuit endpoint.

This field takes the decimal values 0-65534. If this field was not provisioned, or was subsequently UNSET for this circuit, it is left empty ("").

If the ingress trunk group is an IP trunk group, this value is always set to 1.

Egress Trunk Group ID

Egress Trunk Group ID. The egress trunk group ID on the egress GSX/SBC. The content of this field will differ from the corresponding field in the FE Parameter record whenever the final switch is not the same as the egress GSX/

.

This field is supplied by the PSX, taking the decimal values 0 - 4095. If this field is not provisioned on the PSX, it is left empty ("").

This field is supplied to the GSX/

 by the PSX as a 13-character string terminated by a NULL character (""). Therefore, future PSX releases may supply Trunk Group IDs outside the above specified range.

Egress Switch ID

Egress Switch ID. The egress switch ID on the egress GSX/

. The content of this field will differ from the corresponding field in the FE Parameter record whenever the final switch is not the same as the egress GSX/SBC.

This field is supplied by the PSX, taking the decimal values 0 - 1023. If this field is not provisioned on the PSX, it is left empty ("").

This field is supplied to the GSX/

 by the PSX as a 9-character string terminated by a NULL character (""). Therefore, future PSX releases may supply Trunk Group IDs outside the above specified range.

Ingress Local ATM Address

ATM address of the local physical port attached to the ATM network on the ingress leg of the call.

Because this field is not currently supported, it is always empty ("").

Ingress Remote ATM Address

ATM address of the remote physical port attached to the ATM network on the ingress leg of the call.

Because this field is not currently supported, it is always empty ("").

Egress Local ATM Address

ATM address of the local physical port attached to the ATM network on the egress leg of the call.

Because this field is not currently supported, it is always empty ("").

Egress Remote ATM Address

ATM address of the remote physical port attached to the ATM network on the egress leg of the call.

Because this field is not currently supported, it is always empty ("").

Policy Response Call Type

The PSX call type, based on the results of the digit analyses performed by the PSX, which is then used as part of the route selection process.

The call type enumeration permits 31 predefined (Ribbon) values [0-30] and 31 user defined values [1001-1031] as shown in the following table.

Outgoing Route Identification

The outgoing trunk group number for calls that overflow from one gateway to another via a Singapore Inter-Gateway Circuit (IGC) trunk. The GSX/

 extracts this decimal value (0-65536) from the optional "Outgoing Route Identification (ORI)" parameter in the ISUP Address Complete Message (ACM).

If GSX/

 is not deployed in a Singapore network, the field is left empty ("").

Outgoing Message Identification

The type of route that was selected from a GSX/

 deployed in a Singapore network. The GSX/ will extract this value from the optional "Outgoing Route Identification (ORI)" parameter in the ISUP Address Complete Message (ACM).

The following table lists these routes types.

If the ORI is not present, the GSX/ 

 will generate and populate the Outgoing Message Identification according to the Network Indicator as follows:

• If the Network Indicator is set to "2" (National 1), then the Outgoing Message Identification is set to "0" (National Route).
• If the Network Indicator is set to "0" (International) and the GSX/
  Unable to show "metadata-from": No such page "_space_variables"
   is a transit exchange, then the Outgoing Message Identification is set to "1" (Transit Route).
• If the Network Indicator is set to "0" (International) and the GSX/
  Unable to show "metadata-from": No such page "_space_variables"
   is not a transit exchange, then the Outgoing Message Identification is set to "2" (Terminating Route).

If GSX/

 is not deployed in a Singapore network, the field is left empty ("").

Incoming Route Identification

The incoming trunk group number on a GSX/

 deployed in a Singapore network. The GSX/ will extract this value from the optional "Incoming Route Identification (IRI)" parameter in the ISUP Initial Address Message (IAM).

If the IRI is not present or if GSX/

 is not deployed in a Singapore network, then this field contains the ingress trunk ID/Number that is configured on the PSX.

Calling Name

The calling party's name in text.

The ANSI SS7 specification defines this field as up to 15 characters of name information coded in IA5 format. The GSX/

 passes this 15-character string to the PSX in Policy Request message. The PSX returns a Calling Name in the Policy Response that is either the same or a new Calling Name. New Calling Names provided by the PSX may be up to 24 characters. Hence the maximum length of this string is 26 characters (24-character string plus delimiting double quotes "").
The following transformations may be applied to this string:

• Non-printable IA5 characters (1..31 and 127) are displayed as white space (blanks).
• Commas are displayed as is (because the delimiters are the double quotes).
• Double quotes are displayed as single quotes.

If the Calling Name is unknown, or not provided, then the field is left blank without displaying the double quotes as depicted in the last example above.

Calling Name Type

The Calling Name Type delivered in the PSX Policy Response.

If Calling Name data is not available, this field is left empty ("").

Incoming Calling Party Numbering Plan

This field represents the Calling Party Numbering Plan received in the incoming setup message. For ISUP calls this value is extracted from the optional Calling Party Number parameter in the Initial Address Message (IAM). For SIP calls, this value is extracted from the FROM header.

The value logged to the CDR does not comply to the standard ISUP enumeration. This decimal value (range 0-15) must be interpreted according to the below table.

Outgoing Calling Party Numbering Plan

The GSX/

 sends the "Incoming Calling Party Numbering Plan" to the PSX in the Policy Request message. As part of the routing process the PSX may manipulate the Calling Party Numbering Plan. This possibly modified value is then sent back to the GSX/ where it is used in outgoing signaling messages. This value is logged as the "Outgoing Calling Party Numbering Plan".

The value logged to the CDR does not comply to the standard ISUP enumeration. This decimal value (range 0-15) must be interpreted according to Table 43.

Calling Party Business Group ID

START-91, STOP-110, ATTEMPT-101, INTERMEDIATE-91

This value represents the Business Group ID of the calling party. The GSX/

 receives this value in the SIP INCOMING INVITE message.

This decimal value is in the range 0 to 4294967295. If this data is not present or unknown, then a one "1" (Public Business Group) is logged.

SIP is the only protocol which supports Business Group IDs. For all other protocols (ISUP, H323, etc.) this field is logged as "1".

Called Party Business Group ID

This value represents the Business Group ID of the called party. The GSX/

 receives this value in the SIP INCOMING INVITE message. This value is then sent to the PSX in the Policy Request message. As part of the routing process the PSX may modify this value and return it in the Policy Response. The GSX/ logs the value supplied by the PSX, not the value received in the SIP INCOMING INVITE message.

This decimal value is in the range 0 to 4294967295. If this data is not present or unknown, then a one "1" (Public Business Group) is logged.

SIP is the only protocol which supports Business Group IDs. For all other protocols (ISUP, H323, etc.) this field is logged as "1".

Calling Party Public Presence Directory Number

The Calling Party Public Presence Directory Number (PPDN) is an optional SIP parameter which is propagated as the calling number when a call goes into the Public PSTN. If the SIP INCOMING INVITE message's Remote Party ID header contains id-context=ppdn, then the Remote Party ID is interpreted and logged as the Calling PPDN.

This string is up to 30 characters.

If the id-context is not PPDN or if the ingress protocol is not SIP, then this field is empty ("").

Elapsed Time from Receipt of Setup Message to Last Call Routing Attempt

Carriers bill each other based on Carrier Elapsed Time (as opposed to Customer Elapsed Time). Carrier Elapsed time is defined as the Carrier Connect Time to call disconnect time. Telcordia GR-508-CORE defines Carrier Connect Time as:

 "The time when first wink is received from a carrier for Feature Group D (FGD) calls. For Feature Group B (FGB) calls, carrier connect time is the time when carrier off-hook is detected."

The closest the GSX/

 can get to recording the actual carrier connect time is to capture when the IAM for the selected route was sent. The selected route is always the final route attempted. The GSX/ will capture and log the "Time Elapsed from Receipt of Setup Message to Last Call Routing Attempt".

This field contains that elapsed time in 10 millisecond ticks. If no routing attempts were made, then this field is left empty ("").

Billing Number NOA

The incoming ISUP IAM message may contain an optional "Charge Number" parameter. This parameter contains a nature of address (NOA) indicator for the charge number. The GSX/

 logs this value. See Incoming ISUP Charge Number NOA.

The GSX/

 also sends this incoming value to the PSX in the Policy Request message. As part of the routing process the PSX may override this value with the Billing Number NOA provisioned for the ingress trunk group. The PSX returns this possibly modified NOA to the GSX/ in the Policy Response message. The GSX/ uses this returned value in outgoing signaling messages and logs it to this field, the "Billing Number NOA".

This field takes a decimal value in the range 1 to 255. If Billing Number NOA is unknown, then this field is left empty ("").

Incoming Calling Number NOA

START-96 STOP-115 ATTEMPT-107 INTERMEDIATE-98

The incoming ISUP IAM message may contain an optional "Calling Number" parameter. This parameter contains a nature of address (NOA) indicator for the calling number. The GSX/

 logs this NOA in this field.

This field takes a decimal value in the range 1 to 255. If an Incoming Calling Number NOA is not received, then this field is left empty ("").

Egress Trunk Member Number

The Trunk Member used by the egress trunk group for this call. This number uniquely identifies the channel used for this call. The Trunk Member object can be configured for ISDN, ISUP and CAS service groups.

This field takes a decimal value in the range 0 to 65535. If the Trunk Member for the ISDN, ISUP, or CAS egress trunk group is not configured, then this field is left empty ("").

If the egress trunk group is an IP trunk group, this value is always set to "1".

Selected Route Type

This field identifies the destination gateway's type, such as GSX/

 Gateway, SIP Proxy Server, ASX Gateway, etc. See the table for a the definition of each valid type. See "Route Selected" for additional destination gateway information that is logged.

This field takes a decimal value in the range 0-8. For terminating records, this field is left empty ("").

Telcordia Long Duration Record Type

A decimal value indicating what type of Telcordia record is being represented:

Time Elapsed from Previous Record

Specifies the elapsed time, in 10 millisecond ticks, from the previous record for this call to this record. The previous record is either a START record, or an INTERMEDIATE record. This record is either an INTERMEDIATE record or a STOP record.

If intermediate record mode is interval, this value is approximately 100 times the configured intermediate interval. The interval range of 5 seconds to 24 hours results in a field range of 500 - 8,640,000 milliseconds.

If intermediate record mode is Telcordia, the first Telcordia record range is from 8,640,000 milliseconds (24 hours) to 17,279,999 milliseconds (48 hours minus 10 milliseconds). The continuation Telcordia record range for STOP records is 0 milliseconds (call disconnected immediately following a long duration record generation) to 4,294,967,295 milliseconds. INTERMEDIATE Telcordia continuation records will always show 4,294,967,295 milliseconds in this field.

Cumulative Route Index

This decimal value reflects the overall route index used to route this call, counting all prior policy responses. This index can be combined with the Routing Label (see Route Label) to determine the chosen route.

A related field, "Route Index Used", is an index into the most recent policy response.

For example, assume the RL contains 28 routes, and the 25th route succeeds. The first policy response contains 10 routes, none of which succeed. The second policy response also contain 10 routes, again none succeed. The final policy response contains 8 routes, of which the 5th one succeeds. In this case "Route Index Used" is 5 and "Cumulative Route Index Used" is 25.

The range of this value is 1-65535. This field is empty ("") if no routes are chosen to route this call.

Call Disconnect Reason Transmitted to Ingress

This value represents the disconnect reason (or cause code) sent by the local GSX/ 

 to the ingress network (that is, toward the calling party). If the ingress network is another GSX/, then this field will contain the disconnect reason sent by this local GSX/ to that remote GSX/. This disconnect reason is not necessarily the same value the remote GSX/ sends to its ingress network. The transmitted reason is derived from the Release Message (REL) and not from other messages, such as ACM. If the release was initiated by the calling party, this field is empty ("").

If the actual disconnect reason (received from egress or internally generated) is not defined by the ingress signaling protocol, then the reason is mapped to a reason which is defined before being sent. If the call is in a connected state, then the only valid message the

generates is BYE. The status code presented in this field is not sent on the wire.

Call Disconnect Reason Transmitted to Egress

This value represents the disconnect reason (or cause code) sent by the local GSX/

 to the egress network (i.e., toward the called party). If the egress network is another GSX/, then this field contains the disconnect reason sent by this local GSX/ to the remote GSX/. This disconnect reason is not necessarily the same value the remote GSX/ sends to its egress network. The transmitted reason is derived from the Release Message (REL) and not from other messages, such as ACM. If the release was initiated by the called party, then this field is empty ("").

If the actual disconnect reason (received from ingress or internally generated) is not defined by the egress signaling protocol, then the reason is mapped to a reason which is defined before being sent. If the call is in the connected state then the only valid message the SBC can generate is BYE, the status code which is presented in this field will not be sent on the wire.

ISDN PRI Calling Party Subaddress

This string identifies the calling party subaddress associated with a call's origin. Although ISDN document Q.931E specifies that Calling Party Subaddress may contain up to 40 characters, this field is limited to 30 characters on GSX/

.

Outgoing Trunk Group Number in EXM

The Outgoing Trunk Group Number (OTGN) is an optional parameter in the Exit Message (EXM), and is a string of up to six digits. If an EXM is received containing an OTGN, then this field is populated with that value. If an EXM is generated by the GSX/

, then the OTGN in the EXM is taken from the Service Group Profile and that value is also written to this field. Otherwise, this field is empty ("").

Ingress Local Gateway Signaling IP Address

For packet based ingress trunk groups, the IPv4 or IPv6 address used for ingress signaling on the local GSX/

. The IPv4 address is in dotted decimal format, for example 128.1.22.233 and IPv6 address in hexadecimal/colon format, for example fd00:21:445:128::7880. (the local GSX/ generates this accounting record; the device at the far end of the packet network is the remote address).

If the ingress trunk group is circuit based, this field is empty ("").

Ingress Remote Gateway Signaling IP Address

For packet based ingress trunk groups, the IPv4 or IPv6 address is used for ingress signaling on the far end of the packet network. The IPv4 address is in dotted decimal format, for example 128.1.22.233 and IPv6 address in hexadecimal/colon format, for example fd00:21:445:128::7880. (the local GSX/

 generates this accounting record; the device at the far end of the packet network is the remote address.) The device at this address may be another GSX/ gateway, an H.323 device, or a SIP device.

If the ingress trunk group is circuit based, this field is empty ("").

Record Sequence Number

 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).

This number starts at zero and increments by one each time a new record is written. The software maintains only one sequence regardless of the record type. When the sequence number reaches its maximum configured value, either 65535 or 4294967295, it wraps to zero and begins incrementing again (for example 65534, 65535, 0, 1, 2...). The incrementing continues through file roll-overs.

A sequence number of zero occurs only on a reboot (switchover), or a natural wraparound. (A natural wraparound sequence is 65534, 65535, 0, 1, 2 and so on.)

This field is intended to help reconcile billing records after events which may result in lost accounting records.

Transmission Medium Requirement (TMR)

This field is a fixed parameter in the ITU ISUP Initial Address Message (IAM).

For ISUP calls, this information is populated from the TMR parameter, if it is present. If the TMR parameter is absent, this information is populated from the USI parameter. The TMR parameter is mandatory in ITU and the USI parameter is mandatory in ANSI. Because the TMR parameter or the USI parameter is always present, this field is always populated.

 For CAS ingress calls, this field is populated from the capabilities set in the circuit service profile as follows:

• If value = circuitModeData, then T1 channels are set to CPC_TG_TRANSFER_CAP_RESTRICTED. E1 channels are set to CPC_TG_TRANSFER_CAP_RESTRICTED if type is restricted, or to CPC_TG_TRANSFER_CAP_UNRESTRICTED if type is unrestricted.
• If value = voiceOnly, then T1 and E1 channels are set to CPC_TG_TRANSFER_CAP_SPEECH.
• If value = voiceorCircuitModeData, then T1 and E1 channels are set to CPC_TG_TRANSFER_CAP_3_1KHZ_AUDIO.

For incoming SIP calls, if the incoming INVITE has PSTN parameters, then the value of this field is taken from those PSTN headers. If an incoming SIP call is received without PSTN parameters, the default value CPC_TG_TRANSFER_CAP_3_1KHZ_AUDIO is placed into this field. For outgoing SIP calls, if Include PSTN Parameters is enabled in the PSX IP Signaling Profile, then these parameters are included in the SIP headers. Otherwise they are not included in outgoing INVITE.

The decimal value in range 0-255 must be interpreted according to the following table:

Information Transfer Rate (ITR)

For ISUP calls, the User Service Information (USI) parameter is mandatory for ANSI, and optional for ITU. The five least significant bits of the second octet in this parameter contain the Information Transfer Rate. If the USI is present, this field is populated according to the ISUP values in the table below. If the USI is absent, then this field is always populated with the value CPC_TG_TRANSFER_RATE_64KBITS.

For CAS ingress calls, this field is always CPC_TG_TRANSFER_RATE_64KBITS.

For SIP ingress calls, if the incoming INVITE has PSTN parameters, then the value of this field is taken from those PSTN headers. If an incoming SIP call is received without PSTN parameters, the default value CPC_TG_TRANSFER_RATE_64KBITS is placed into this field. For outgoing SIP calls, if includePstnParameters is enabled in the PSX IP Signaling Profile, then these parameters are included in the SIP headers. Otherwise they are not included in outgoing INVITE.
This decimal value in the range 0-31 must be interpreted according to the table below . Note that these values do not correspond to the ISUP Q.931 definitions.

• This value does not comply with Q.931

User Service Information (USI) User Information Layer 1

The User Service Information (USI) parameter is optional in the ISUP IAM. The five least significant bits of the third octet in this parameter contain the User Information Layer 1 (UIL1) Protocol. If the USI is not present in the IAM, or if the ingress service group is not ISUP, then this field is empty ("").

This decimal value (range 0-31) must be interpreted according to the below table.

Unrecognized Raw ISUP Calling Party Category

This field contains the actual (raw) value of the calling party category if this value is not recognized by this GSX/ 

, otherwise this field is empty ("").

If present, the decimal value of this field is in the range 0-255.

Egress RLT Feature Specific Data

The Egress Release Link Trunking (RLT) Feature Specific Data field is populated only when SS7 Release Link Trunking occurs on the egress leg of the call, otherwise this field is empty ("").

A Facility Request Message (FAR) is sent backward from the Redirecting Node to the call-originating node (Pivot Node) to request activation of an RLT service.

Any call that is bridged or redirected creates two accounting records: one for the initial call (AR) and one for the bridged or redirected call (BR). The table below presents the CDR logging scenarios for original, bridged, and redirected calls.

If more than one RLT (redirecting or bridging) occurs on the egress leg of the call, then only the data for the last RLT is present. When bridging occurs, the redirect Sub-Fields are empty (""). Similarly, when redirect occurs, the bridging Sub-Fields are empty (""). This field is a maximum of 598 characters, including all comma separators and the double quotation mark delimiters ("").

The Release Link Trunking Sub-Fields page provide additional explanation about certain Sub-Fields.

Example RLTs:

Redirecting:
"RLT,30,0:4000123456,0:3000123456,1:2000123456,0:1000123456,0:123456,1:0000123456,2:BADC,3:ABCD0102,3330,0:8005551212,1:8005551212,2:0850552121,3:0850552121,7864351112,7865550017,2146809413,19,0,8637,0,,,,,,,,,,"

Bridging:
"RLT,30,0:4000123456,0:3000123456,1:2000123456,0:1000123456,0:123456,1:0000123456,2:BADC,3:ABCD0102,7491,,,,,,,,,,,,2:48656C6C6F,0:2200123456,0:3300123456,0:4400123456,9785550000,9785551212,00070004:050505,0,15123,2033"

Two B-Channel Transfer Feature Specific Data

This field is populated only when a Two B-Channel Transfer occurs, otherwise this field is empty ("").

If one transfer occurs, then the first three Sub-Fields are populated. If a second transfer occurs, an additional Sub-Field is populated that indicates the time of that transfer. Unpopulated Sub-Fields are empty (""). This field is a maximum of 72 characters, including all comma separators and the double quotation mark delimiters (""). The following table describes the field format.

Example:

"TBCT,2,523,1179"

This string indicates two transfers occurring at 5.23 and 11.79 seconds after the call was established.

Calling Party Business Unit

This field contains the Business Unit ID (or Sub-Group ID) of the Calling Party. This data is supplied by the PSX in the Policy Response. If Business Unit data is not available for the call, this field is empty ("").

If present, the decimal value of this field is in the range 0-4294967295.

Called Party Business Unit

This field contains the Business Unit ID (or Sub-Group ID) of the Called Party. This data is supplied by the PSX in the Policy Response. If Business Unit data is not available for the call, this field is empty ("").

If present, the decimal value of this field is in the range 0-4294967295.

Redirection Feature Specific Data

This field captures the redirection information that happens to a call before it is processed by the GSX/SBC. This information is supplied by the originating network in the call setup message (the ISUP IAM message or the SIP INVITE message). This field does not refer to redirects performed internally by the GSX/SBC or PSX.

This field format is similar to the "Egress RLT Feature Specific Data" and the "Two B-Channel Transfer Feature Specific Data".

Field format is described in the below table.

Redirect Reason Codes

Redirecting Address Presentation Restriction Codes

Redirecting Numbering Plan Codes

Redirecting NoA Codes

When the ingress protocol is SIP, all diversion headers present in the incoming SIP INVITE message are used to populate Redirection Feature Specific Data. The GSX/

 maps the SIP diversion headers into ISUP parameters. The name-addr of the top-most Diversion header is used to set the ISUP Redirecting Number. The diversion-reason of the top-most Diversion header is used to set the ISUP Redirecting Reason.

When multiple Diversion headers are present, the name-addr of the bottom-most Diversion header is used to set the ISUP Original Redirecting Number, and the diversion-reason of the bottom-most Diversion header is used to set the ISUP Original Redirecting Reason. The ISUP Redirect counter is set equal to the sum of the counters of all Diversion headers in the SIP message.

A diversion header that does not explicitly specify a diversion-counter tag counts as "1". If no redirect occurs, then the entire "Redirection Feature Specific Data" field is empty ("").

Example Redirection Feature Specific Data Field:

"REDI,11,3971912318,3971912315,1,2,10,0,10,6,01793601618,2,19"

Ingress RLT Feature Specific Data

The Ingress RLT (Release Link Trunking) Feature Specific Data field is populated only when SS7 Release Link Trunking occurs on the ingress leg of the call, otherwise this field is empty ("").

A Facility Request Message (FAR) is sent backward from the Redirecting Node to the call-originating node (Pivot Node) to request activation of an RLT service.

Any call bridged or redirected creates two accounting records: one for initial call (AR) and one for bridged or redirected call (BR). Table Encoding Data Detail presents the CDR logging scenarios for original, bridged, and redirected calls.

If more than one RLT (redirecting or bridging) occurs on ingress leg of the call, only the data for the last RLT is present. When bridging occurs, the redirect Sub-Fields are empty (""). Similarly, when redirect occurs, bridging Sub-Fields are empty ("").

This field is a maximum of 598 characters, including all comma separators and the double quotation mark delimiters (""). Table USI User Information Layer 1 describes the field format. Table Release Link Trunking Failure provides additional explanation about certain SubFields.

PSX Index

This field, which is configured on the GSX/

, contains the index of the PSX that routed the call. The decimal value of this field is 0-10, as shown below:

Use the ADMIN command to see the names of PSX 1 (left column) and PSX 2 (right column).

The names and indexes of the configured PSXs are recorded in the system event log at PSX creation time. An example of such an entry is:

119 06112004 194858.00001:1.01.MAJOR .DS : PSX created, name: boston, index: 2

PSX Congestion Level

This field contains the enumerated congestion level value sent to the GSX/SBC by the PSX in the Policy Response. These enumeration are listed below. If no PSX was involved in routing the call or if congestion control was disabled, then this field is empty ("").

PSX Processing Time

This field contains the time in milliseconds that used by PSX to process a Policy Request. This value contributes to the policy response time. If no PSX is involved in routing the call or if no PSX transaction took place, then this field is empty ("").

If present, the decimal value of this field is in the range 0-65535.

Script Name

This field contains the file name (string of up to 23 characters) of a script executed on behalf of a call. If more than one script is executed, this field contains the name of the last script that executed.

If no script was executed on behalf of this call, this field is empty ("").

Ingress External Accounting Data

This field, consisting of an ASCII string with the delimiters "", contains external accounting data from the ingress leg of the call, similar to the "Ingress Protocol Variant Specific Data". This string takes the form:
"<protocol identifier>,<external accounting data>"

The maximum length of the field, including the delimiters, is 150.

Because accounting strings from external entities can contain characters to corrupt a CDR record, the GSX/

 software performs the following character substitutions:

• all control characters, such as <CR>, <DEL>, <ESC>, and so on, are converted to space (" ")
• double quote (") is converted to single quote (')

Egress External Accounting Data

This field, consisting of an ASCII string with the delimiters "", contains external accounting data from the egress leg of the call, similar to the "Egress Protocol Variant Specific Data". This string takes the form:
"<protocol identifier>,<external accounting data>"

The maximum length of the field, including the delimiters, is 150.

See "Ingress External Accounting Data"  for explanation field.

Egress RTP Packetization Time

Egress Number of Audio Bytes Sent

Number of Audio Bytes Sent as recorded by the egress DSP/NP (decimal representation of a 64 bit number: 1 - 1.844674407*10¹⁹).

Egress Number of Audio Packets Sent

Number of Audio Packets Sent as recorded by the egress DSP/NP (decimal representation of a 64 bit number: 1 - 1.844674407*10¹⁹).

Egress Number of Audio Bytes Received

Number of Audio Bytes Received as recorded by the egress DSP/NP (decimal representation of a 64 bit number: 1 - 1.844674407*10¹⁹).

Egress Number of Audio Packets Received

Number of Audio Packets Received as recorded by the egress DSP/NP (decimal representation of a 64 bit number: 1 - 1.844674407*10¹⁹).

Egress Interarrival Packet Jitter

The maximum interarrival packet jitter time (in millisecond) recorded by the egress DSP/NP. This field is a decimal representation of a 16-bit number, hence must be in the range 0-65535 (This is applicable to RTCP statistics for VoIP calls only).

Egress Last Measurement for Latency

The last measurement for latency (in milliseconds) as recorded by the egress DSP. This field is a decimal representation of a 16-bit number, hence must be in the range 0-65535 (applicable to RTCP statistics for VoIP calls only).

Ingress Maximum Packet Outage

This field contains a decimal value up to 10 digits, and logs the maximum duration between received packets, in milliseconds, on ingress side of the call.

Egress Maximum Packet Outage

This field contains a decimal value up to 10 digits, and logs the maximum duration between received packets, in milliseconds, on egress side of the call.

Ingress Packet Playout Buffer Quality

This field summarizes the DSP media quality for the most recent 31 time intervals of the ingress leg of the call. The default time interval is 20,000 milliseconds or 20 seconds. Customize this time interval via the CLI:

The playout buffer quality is averaged over this interval and then quantized into one of four discrete levels characterized by the bit patterns:

• 00 = GOOD
• 01 = ACCEPTABLE
• 10 = POOR
• 11 = UNACCEPTABLE

Data for the most recent 31 time intervals is recorded. These 62 bits of data (31 intervals x 2 bits/interval) are represented in CDR as a 16-character hexadecimal value. An end of data token (bit pattern 11) is used to indicate start of valid data. All data to the left of the token is invalid, while all data to the right is valid.

This field contains 16 hexadecimal characters without the "0x" prefix. Hex characters "A" through "F" are capitalized. If a DSP resource was not used for the ingress leg of the call, this field is empty ("").

The table below presents several example field values and the explanation of each.

Egress Packet Playout Buffer Quality

This field summarizes the DSP media quality for the most recent 31 time intervals of the egress leg of the call.

This field contains 16 hexadecimal characters without the "0x" prefix. Hex characters "A" through "F" are capitalized. If a DSP resource was not used for the egress leg of the call, this field is empty ("").

See Ingress Packet Playout Buffer Quality   for a full explanation of this field.

Answer Supervision Type

This field specifies the answer type detected when ANSWER SUPERVISION is enabled for the call.

You can configure ANSWER SUPERVISION for all signaling prototypes except GSX/

Gateway-to-Gateway signaling

When ANSWER SUPERVISION is enabled, one of the four scenarios below establishes the answer type:

• Called party answers the call (causing a return of the ANM message), before the answer supervision timer expires. An answer type of HARDWARE is presented in the START, INTERMEDIATE, and STOP records.
• Calling or called party disconnects the call (causing a return of the REL message), before the answer supervision timer expires. An answer type of HARDWARE is presented in the ATTEMPT record.
• The answer supervision timer expires and the call is disconnected before the called party answers the call (causing a return of the REL message). An answer type of SOFTWARE is presented in the ATTEMPT record.
• The answer supervision timer expires, after which the call is answered (causing a return of the ANM message). An answer type of SOFTWARE is presented in the START, INTERMEDIATE, and STOP records.

If ANSWER SUPERVISION is disabled, an answer type of empty (""), is presented in all records.

This field takes a decimal value in the range 1-2, or remains empty (""), as summarized in the following table:

Ingress SIP REFER-Replaces Feature Specific Data

This field contains Feature Specific Data for a SIP REFER (Blind Transfer) or SIP Replaces (Attended Transfer) operation is performed on the ingress leg of a SIP to SIP call.

SIP REFER data is populated if a 'SIP REFER' request is received. SIP REPLACES data is populated if a 'SIP INVITE with Replaces' or 'SIP REFER with Replaces' header message is received. If the SIP REFER or SIP REPLACES operation is absent on this leg of the call, this field is empty ("").

The maximum length of this field is 81 characters, including all commas and double quotes ("").

The format of the SIP REFER Feature Specific Data field is:

 "SREF,<number of subfields>,<TimeFromInviteToRefer>,<transferor's number>,<new transfer target number>"
Inspect the CDR of the B>C call to determine whether the SIP REFER is successful:

• if successful, this field is present in a START/STOP record
• if not successful, this field is present in an ATTEMPT record

SIP REFER

The format of the SIP REFER Feature Specific Data field is:

 "SREF,<number of subfields>,<TimeFromInviteToRefer>,<transferer's number>,<new transfer target number>"

 The following table details each of these subfields.

Inspect the CDR of the B>C call to determine whether the SIP Refer is successful:

• if successful, this field is present in a START/STOP record
• if not successful, this field is present in an ATTEMPT record

The example string:

"SREF,3,523,7817771111,9787771111"

indicates that a SIP Refer by party B (7817771111) to party C (9787771111) is received 5.23 seconds after receiving the setup message (INVITE).

SIP INVITE with Replaces

The format of the SIP Replaces Feature Specific Data field is:

 "SREPL,<number of subfields>,<Time>,<opLeg>,<legId>,<peerCallGcid>, <peerCallLegId>"

The following table details each of these subfields.

The example string:

"SREPL,5,625,1,0,0x00060001,0"
indicates INVITE with REPLACES was received 6.25 seconds after the initial setup (INVITE) message. This call's ingress leg Replaces the peer (GCID x00060001) call's ingress leg.

SIP REFER with Replaces 
The format of the SIP REFER with Replaces Feature Specific Data field is:
"SREFREPL,<number of subfields>,<Time>,<opLeg>,<legId>,<peerCallGcid>, <peerCallLegId>"

The following table details each of these subfields.

The example string:

"SREFREPL,5,750,1,0,0x00080002,0"

indicates REFER with REPLACES was received 7.50 seconds after the initial setup (INVITE) message. This call's ingress leg Replaces the peer (GCID x00080002) call's ingress leg.

Egress SIP REFER-Replaces Feature Specific Data

This field contains Feature Specific Data for a SIP REFER (Blind Transfer) or SIP Replaces (Attended Transfer) operation is performed on the egress leg of a SIP to SIP call.

SIP REFER data is populated if a 'SIP REFER' request is received. SIP REPLACES data is populated if a 'SIP INVITE with Replaces' or 'SIP REFER with Replaces' header message is received. If the SIP REFER or SIP REPLACES operation is absent on this leg of the call, this field is empty ("").

The maximum length of this field is 81 characters, including all commas and double quotes ("").

See "Ingress SIP REFER-Replaces Feature Specific Data" above for details about each of subfield of SIP REFER, SIP INVITE with Replaces, and SIP REFER with Replaces feature-specific data fields.

Network Transfer Feature Specific Data

This field is populated when a Network Transfer occurs.

The format of the field is:
"NWXF,<number of subfields>,<Speed Dial Digits>,<RefTod>, <NTCallType>"

The following table details each of these subfields.

The maximum length of this field is 54 characters, including all commas and double quotes ("").

The example string:

"NWXF,3,100,18007817788,25" indicates that Network Transfer of type "Network Transfer Courtesy" is initiated by "18007817788" by dialing speed dial digits "100".

Call Condition

This field provides the criteria for determining the AMA call type value for billing records. This value is generated by the PSX and based on the type of call along with other network information such as terminating call, inter-network call, intra-network call, etc. This two-digit decimal field takes a value from 0-39, that maps to the call conditions described in the Call Condition Criteria table.

Toll Indicator

This field provides the toll indication for the call. This value is generated by the PSX. This two- digit decimal field takes a value from 0-64, that maps to the toll indicators described in the table.

Generic Number (Number)

This field contains the digits from the Generic Number "number" subfield, and is located in ISUP signaling messages received at the gateway, such as IAM, SGM, etc. This string is up to 30 characters. If no "number" was included in ISUP messages associated with this call, then this field is empty ("").

 An example of this field is:
"01793601014"

Generic Number (Presentation Restriction Indicator)

This one-decimal digit field provides the Presentation Restriction Indication for the Generic Number "number" subfield described above. This field is presented in ISUP signaling messages received at the gateway, such as IAM, SGM, etc. and takes the values enumerated in the following table.

Generic Number (Numbering Plan)

This two-digit field provides the numbering plan for the Generic Number "number" subfield (above) and is located in ISUP signaling messages received at gateway, such as IAM, SGM, etc. This field takes the values enumerated in  the following table:

Generic Number (Nature of Address)

This three-digit field provides the Nature of Address for the generic number "number" subfield described above. This field is presented in ISUP signaling messages received at the gateway, such as IAM, SGM, etc., and takes the values enumerated in the Generic Number NOA Values table.

Generic Number (Type)

This two-digit field indicates the type of the Generic Number "number" subfield, and is presented in ISUP signaling messages received at the gateway, such as IAM, SGM, etc. The generic number "type" depends on the ISUP variant that is in effect. The 'Generic Number Type Values table enumerates the valid types for particular variants.

Final ATTEMPT Indicator

This one-digit decimal field indicates whether this is the final record written for a call. This field applies only to the ATTEMPT record and takes the values enumerated in the following table:

Originating Trunk Type

This is a one-byte hexadecimal field without a leading "0x". This field is either empty ("") or contains the hex code representing the originating trunk type. This field is associated with the corresponding field of the trunk group screen on the PSX, and takes the values enumerated in the following table.

Terminating Trunk Type

A one-byte hex field without leading "0x" that takes values enumerated in the  Final ATTEMPT indicator table. Field is either empty ("") or contains hex code representing terminating trunk type, and is associated with corresponding field of PSX trunk group screen.

Remote GSX/SBC Billing Indicator

This one-digit decimal field indicates whether a CDR record contains billing information from the destination GSX/

 for GSX/-GSX/ calls. This field is present when "Populate Remote GW Info" feature is enabled on ingress GSX/, and is empty when the feature is disabled. This field always takes one of the values enumerated in the following table.

Extra Disconnect Reason

This four-digit decimal field details the GSX/

 internal disconnect reason associated with the existing fields, "Call Disconnect Reason Transmitted to Ingress"  and "Call Disconnect Reason Transmitted to Egress" , when a call attempt fails.

This field is populated when a call is released before invoking call control in the GSX/

 software. The underlying ISUP cause value 41 (TEMPORARY FAILURE) typically causes this field to be populated, but other ISUP cause values could also cause this entry (see Call Termination Reason Codes).

This field occurs only in ATTEMPT records when both of the following conditions are met. Otherwise, this field is empty ("").

• ACCOUNTING EARLY ATTEMPT records are enabled.
• Additional call disconnect information is available

The Extra Disconnect Reason Codes table details the contents of this field.

VPN Calling Private Presence Number

 This field contains the VPN private presence number for VPN originated calls, and is populated from the PSX policy response. This field is only populated under following conditions:

• For VPN originated calls; empty ("") for all other calls.
• If private presence number is configured on the PSX; otherwise empty.

This field contains a string of up to 30 characters, or is empty. An example of this field is "8189".

VPN Calling Public Presence Number

This field contains the VPN public presence number for VPN originated calls in E-164 format. This field is populated from the PSX policy response. This field is only populated under following conditions:

• For VPN originated calls; empty ("") for all other calls.
• If private presence number is configured on the PSX; otherwise empty.

This field contains a string of up to 30 characters, or is empty. An example of this field is:
"19786543210, 441793123456"

External Furnish Charging Info

This field contains up to 400 bytes of binary data (represented by up to 800 hexadecimal characters) generated by the PSX. The External Furnish Charging Info (FCI) data comes from external source such as a Service Control Point (SCP), a Global System for Mobile Communication (GSM), or a Service Control Function (SCF). This FCI field is only present while some external service populates the data for a call involving Customized Application of Mobile Enhanced Logic (CAMEL) services.

The PSX passes the FCI field to GSX/

SBC, and GSX/ passes it back for subsequent Policy Requests. Each byte of FCI data received by the GSX/ is represented as two hexadecimal characters (00 to FF) in CDR. The table "External Furnish Charging Info Sub-Fields",  displays a high level view of FCI Field within an accounting record. The binary format of the "External Furnish Charging Info" data encoded for the Camel Application Part (CAP) variant is shown in the table "CAP Specific Data Format", below:

 FCI data is divided into three portions:

• FCI Variant ID
• FCI Leg Count
• FCI Variant Specific Data

The FCI Variant ID contains a single byte FCI Variant ID value. This value is used to determine the format of the rest of the data. Value 1 is defined for CAP (this is the only value currently defined for this GSX/SBC software release). In the future this FCI Variant ID may be extended to include the Intelligent Networking Application Part (INAP) and others.

The Leg Count contains a single byte count indicating how many sets of data are present. For FCI data of CAP, there is one set of data per Leg ID. For example, if FCI data is only present for leg 1, then the Leg Count is set to 1. If FCI data is present for leg 1 and leg 2, then the Leg Count is set to "2".

For CAP variant specific data, each set of FCI data contains three sub-fields, Leg ID, Data Length, and Data. The Leg ID field determines the call leg. For CAP this is either 1 or 2. The Data Length field determines the variable length of the FCI data. The FCI data can be up to 160 bytes per leg. The actual FCI Data field contains the binary data as received by PSX from the external sources.

Ingress Policing Discards

This 20-digit decimal field contains the number of ingress packets discarded due to policing. If no ingress packets are discarded by policers, this field is empty ("").

Egress Policing Discards

This 20-digit decimal field contains the number of egress packets discarded due to policing. If no egress packets are discarded by policers, this field is empty ("").

Announcement ID

This five-digit decimal field contains the announcement ID of the last announcement played by the GSX/SBC for the call. If no announcement is played, this field is empty ("").

Source Information

This field describes the Source Information type for the call, based on the ISUP signaling received at the gateway, or from information received from the PSX. This two-digit decimal field takes a value of 0-15, enumerated in Table 79 . If no source information is received, this field is empty ("").

Partition ID

This four-digit decimal field describes the Partition used based on the ISUP signaling received at the gateway, or from information received from the PSX.

This field takes a decimal value in the range 0 to 4095. If no partition ID information is received, this field is empty ("").

Network ID

This five-digit decimal field describes the Network used based on ISUP signaling received at the gateway, or from information received from the PSX.

This field takes a decimal value in the range 0 to 32767. If no network information is received, this field is empty ("").

NCOS

This five-digit decimal field describes the N Class of Service (NCOS) for this call, based on the ISUP signaling received at the gateway, or from information received from the PSX.

This field takes a decimal value in the range 0 to 65535. If no NCOS information is received, this field is empty ("").

Ingress SRTP

This seven-character field displays the Crypto information used for setting up RTP and RTCP for the ingress leg. If Secure RTP is configured and used on the call, each field will contain four (4) sub-fields indicating the RTP authentication and encryption values and the RTCP authentication and encryption values selected. Each subfield is separated by ":". If regular RTP is used, the field is left blank.

The possible values for RTP and RTCP Authentication sub-fields are listed in the following table. The possible values for RTP and RTCP Encryption sub-fields are listed in the "Values for RTP and RTCP Encryption Sub-Field" table.

The sub-field string:
"1:0:1:0"
indicates SHA1_80 authenticated SRTP, unencrypted SRTP, and SHA1_80 authenticated SRTCP, unencrypted SRTCP.

Egress SRTP

This seven-character field displays the Crypto information used for setting up RTP and RTCP for the egress leg. If Secure RTP is configured and used on the call, each field will contain four (4) sub-fields indicating the RTP authentication and encryption values and the RTCP authentication and encryption values selected. Each subfield is separated by ":". If regular RTP is used, the field is left blank. The possible values for RTP and RTCP Authentication sub-fields are listed in Table 76. The possible values for RTP and RTCP Encryption sub-fields are listed in the below table-.

 The sub-field string:
"1:0:1:0"
indicates SHA1_80 authenticated SRTP, unencrypted SRTP, and SHA1_80 authenticated SRTP, unencrypted SRTP.

ISDN Access Indicator from the Forward Call Indicator

This field contains an enumerator describing the ISDN Access Indicator value from the Forward Call Indicator parameter. The Forward Call Indicator parameter is an optional parameter in incoming signaling messages such as IAM (ISUP), SETUP (ISDN), and INVITE (SIP). This field is either one decimal digit or empty (""). The defined enumerations are:

Call Disconnect Location

This field contains an enumeration that describes the Location value from the Cause Indicator parameter in the release message. The Cause Indicator parameter is an optional parameter in call disconnect signaling messages such as REL (ISUP) and DISCONNECT (ISDN). When the call is released by the network, this field will contain the Location value from the Cause Indicator parameter received by the 

.

 When the 

 initiates the release, this field will contain the Location value in the Cause Indicator parameter generated by the . This field is 1-2 decimal digits or empty (""). The following table lists the defined enumerations.

* Not currently supported by 

. But if received, it is mapped to the ENUMERATION.

Call Disconnect Location Transmitted to Ingress

This field contains an enumeration describing the Location value from the Cause Indicator parameter in the release message sent to the ingress network. The Cause Indicator parameter is an optional parameter in call disconnect signaling messages such as REL (ISUP) and DISCONNECT (ISDN). This field is 1-2 decimal digits or empty ("").

The defined enumerations are shown in the table, "Location Value from Cause Indicator Parameter".

Call Disconnect Location Transmitted to Egress

This field contains an enumeration describing the Location value from the Cause Indicator parameter in the release message sent to the egress network. The Cause Indicator parameter is an optional parameter in call disconnect signaling messages such as REL (ISUP) and DISCONNECT (ISDN). This field is 1-2 decimal digits or empty ("").

The defined enumerations are shown in the table "Location Value from Cause Indicator Parameter".

Network Call Reference - Call Identity

This field contains an enumeration describing the Call Identity from ISUP Network Call Reference parameter. The Network Call Reference parameter is an optional signaling parameter. This field is up to eight decimal digits or empty ("").

Network Call Reference - Signaling Point Code

This field contains an enumeration describing the Signalling Point Code from the optional ISUP Network Call Reference parameter. This field is up to five decimal digits or empty ("").

Ingress ISUP MIME Protocol Variant Specific Data

The ingress ISUP MIME Protocol Variant Specific Data. A string with delimiters "" or empty. The string has multiple sub-fields separated by a comma (,). An empty sub-field is represented by either two consecutive commas (,,) or by comma-space-comma (, ,). Whenever any ingress service group has ISUP MIME Protocol Variant Specific Data to log, this data is logged to this field.

An example of this field is:
"JAPAN,0,0, ,,,,...,0x04"

See the following for the Ingress ISUP MIME Protocol Variant Specific Data:

• Japan ISUP Variant Sub-field Descriptions

Egress ISUP MIME Protocol Variant Specific Data

The egress ISUP MIME Protocol Variant Specific Data. A string with delimiters "" or empty. The string has multiple sub-fields separated by a comma (,). An empty sub-field is represented by either two consecutive commas (,,) or by comma-space-comma (, ,). Whenever any egress service group has ISUP MIME Protocol Variant Specific Data to log, this data is logged to this field.

An example of this field is:
"JAPAN,0,0, ,,,,...,0x04"

See the following for the Egress ISUP MIME Protocol Variant Specific Data:

• Japan ISUP Variant Sub-field Descriptions

Modem Tone Type

This field represents the types of detected Modem tones in a call. If no modem is detected, this field is empty. The following table lists the possible Modem tone types.

Modem Tone Signal Level

The field represents the power level of Modem Tone Signal. The value returned is in -dBm0 with a range from 0 to 36 where 0 represents the strongest signal and 36 the weakest signal. If no modem is detected, this field is empty.

Video Codec Data

This field displays the Video Codec Data and contains four subfields separated by commas. The maximum length of this field is 512 characters, including all commas and double quotes (""). If the video codec data is not present, then there is only a single comma separator for the data.

The Video Bandwidth subfields are empty in START/INTERMEDIATE records. The Video Call Duration subfields are empty in START/INTERMEDIATE/ATTEMPT records.

The format of the Video Codec Data field is:

 "Bandwidth,Duration,<localIpAddr>:<localIpPort>/<remoteIpAddr>:<remoteIpPort>,<localIpAddr>:<localIpPort>/<remoteIpAddr>:<remoteIpPort>"

An example of this field is:
"64,250,10.1.1.1:40/10.1.1.2:80,10.1.1.1:40/10.1.1.2:80"

The following table details each of the subfields. 

Video Codec Statistics

Displays statistical data related to the Video Codec feature with up to 14 subfields () separated by a comma (,). The maximum length of this field is 512 characters, including all commas and double quotes ("").

Each subfield contains a decimal value between 0 - 4294967295.

An example of this field is:
"60,10,500,2100,2,0,100,5,500,10,0,0,0,"

SVS Customer

The Customer field indicates the Trunk Group Number received in the Route Information K-ISUP parameter used to identify the ingress carrier. Decimal value 1 to 4 digits or empty.

Call to Test PSX

The Call to Test PSX field indicates if a call is for a Test PSX, and is determined based on the Calling Party Number. Boolean field with the following usage:

• Empty – Normal call.
• 1 – Call is determined to be a Test Call and routed to the Test PSX.

PSX Overlap Route Requests

The PSX Overlap Route Requests field indicates the number of routing requests sent to the PSX by the GSX/

 for each call when the Called Party Number (CdPN) was not complete. This field is only populated for Overlap calls and is applicable to all protocols (ISUP, BT-IUP, SIP, SIP-I, ISDN, H.323, and CAS). Decimal value, 1 to 2 decimal characters or empty.

Call Setup Delay

The Call Setup Delay field indicates the setup latencies of Key Performance Indicators (KPI) for the purpose of troubleshooting and monitoring and contains decimal-value sub-fields separated by commas (,). The maximum length of this field is 21 characters, including all commas and double quotes (""). 
Subfields:

• Request Latency – (1-3 digits, or empty) Latency in milliseconds between the last INVITE receipt from the upstream element and dispatch to the downstream element (not counting retransmissions) before the first non-100 and non-484 response is received from the downstream element.
• Downstream Latency – (1-5 digits, or empty) Latency in milliseconds between the last INVITE dispatch to the downstream element (not counting retransmissions) and the first non-100 and non-484 response receipt from the downstream element.
• Response Latency – (1-3 digits, or empty) Latency in milliseconds between the first non-100 and non-484 response receipt from the downstream element and dispatch to the upstream element.
• Total Latency – (1-5 digits, or emptyP Latency in milliseconds between the last INVITE receipt from the upstream element (not counting retransmissions) and the first non-100 and non-484 response dispatch to upstream element.

An example of a Call Setup Delay field is:
"88,931,19,983"

Overload Status

This field (decimal, 1-3 digits, or empty) indicates the congestion level for monitored resources on the node or server that processes this call.

• Single digit values (0 through 3) indicate the System/Node Congestion Level.
• Two or three digit values indicate the server slot number and the Server Congestion Level. For example:
• A value of "91" indicates Server Slot 9, Congestion level 1
• A value of "151" indicates Server Slot 15, Congestion level 1

The Congestion Levels are as follows:
0 - No Congestion
1 - System Machine Congestion (MC) Level one congestion 
2 - System Machine Congestion (MC) Level two congestion
3 - System Machine Congestion (MC) Level three congestion 

Ingress DSP Data

The Ingress DSP data field is used to report Ingress DSP Data to assist in troubleshooting and monitoring. Each bit indicates a setting where Bit 0 is LSB and bit 15 is MSB. An example of this field is: "12FF".

Egress DSP Data

The Egress DSP data field is used for reporting Egress DSP Data to assist in troubleshooting and monitoring, where each bit indicates a setting. An example of this field is: "12FF".
For details on Bit fields and Bit values, see the tables in "Ingress DSP Data" section above.

Call Recorded Indicator

This field is populated for populated for SIPrec and NICE-based call recording. NICE Systems using their forwarding based protocol (based on the SIP forwarding extension) provide a mechanism for recording calls. SBC 9000 acts as a forwarding capable device which routes the content of an active call to a recording system. When a call is tapped an indication is provided in the "STOP" CDR field for that call along with the transmit and receive RTP stream IP address and port.

This field specifies whether the NICE Systems recording feature is enabled or disabled. It can accept "Yes" or empty. The length of this field can be up to 3 characters.

Call Recorded RTP Tx IP Address

This field is populated for populated for SIPrec and NICE-based call recording. This field contains the RTP transmitting IP address if the NICE Systems recording feature is enabled. If the NICE systems recording feature is not enabled, then this field is empty. The length of this field can be up to 39 characters. IP address can be in IPv4 or IPv6 format. For IPv4 address type, use the dotted decimal format (for example, 128.1.22.233) and for IPv6 address type, use the hexadecimal format (for example, 3ffe:1900:4545:3:200:f8ff:fe21:67cf (up to 39 characters)).

Call Recorded RTP Tx Port Number

This field is populated for populated for SIPrec and NICE-based call recording.This field contains the RTP transmitting port number if the NICE Systems recording feature is enabled. If the NICE systems recording feature is not enabled, then this field is empty. The length of this field can be up to 5 characters.

Call Recorded RTP Rv IP Address

This field is populated for populated for SIPrec and NICE-based call recording. This field contains the RTP receiving IP address if the NICE Systems recording feature is enabled.  If the NICE systems recording feature is not enabled, then this field is empty. The length of this field can be up to 39 characters. IP address can be in IPv4 or IPv6 format. For IPv4 address type, use the dotted decimal format (for example, 128.1.22.233) and for IPv6 address type, use the hexadecimal format (for example, 3ffe:1900:4545:3:200:f8ff:fe21:67cf (up to 39 characters)).

Call Recorded RTP Rv Port Number

This field is populated for populated for SIPrec and NICE-based call recording. This field contains the RTP receiving port number if the NICE Systems recording feature is enabled. If the NICE systems recording feature is not enabled, then this field is empty. The length of this field can be up to 5 characters.

MLPP Precedence Level

This field indicates the precedence level of the call. The values are:

• 0 – FLASH OVERRIDE (highest)
• 1 – FLASH
• 2 – IMMEDIATE
• 3 – PRIORITY
• 4 – ROUTINE.

Global Charge Reference (GCR)

This field is a 20-byte array used for Call Data Record (CDR) correlation. Each byte contains two ASCII characters. ISUP Signaling profile flag GCR is supported on ingress or egress side.

Example: 456f1c000300000025180000

Ingress Inbound R-Factor

This decimal field displays the R-Factor of the inbound RTP stream for the ingress trunk group.

The length of this field is up to two places.

Ingress Outbound R-Factor

This decimal field displays the R-Factor of the outbound RTP stream for the ingress trunk group.

The length of this field is up to two places.

Egress Inbound R-Factor

This decimal field displays the R-Factor of the inbound RTP stream for the egress trunk group.

The length of this field is up to two places.

Egress Outbound R-Factor

This decimal field displays the R-Factor of the outbound RTP stream for the egress trunk group.

The length of this field is up to two places.

Media Stream Data

This field provides the data for all core audio, video, and text streams.

This compound field shows transport-related information, such as:

• Media type (Information about streams that were once part of the call but were removed by the time the call is completed may not be recorded.)
  
• Local and Remote IP and Port
• SRTP encryption and authentication algorithms
• Bandwidth reserved on the interface
  

Example:

Media Stream Stats

This field provides the statistics for all core audio, video, and text streams.

Example:

Transcode Indicator

Transcode Indicator is a Boolean value to indicate whether transcoded is used. A value of “1” indicates transcoding between the two call legs and "0" means no transcoding.

HD Codec Rate

HD Codec Rate is a decimal value field to hold the HD codec rate per leg. 

Remote Audio RTCP Learned Metrics

 Remote RTCP statistics are populated in STOP CDR for both pass-through and transcoded calls based on the following conditions, as applicable:

• For Pass-through calls, RTCP termination is enabled on only one leg.
• For Transcoded calls, remote statistics is populated for the call leg which has RTCP enabled.

This feature is supported in the following call scenarios: 

• SIP
• H323
• SIP-I
• Gw-Gw (with above protocols)
• IPv4
• IPv6

Remote Ingress Audio RTCP Learned Metrics

The Remote Ingress Audio RTCP Learned Metrics field indicates statistics received from Ingress endpoint in SR/RR RTCP Packet. The maximum length of this field is 1024 characters, including all commas and double quotes (""). 
Subfields:

• Ingress Packets Sent - Received as part of RTCP Packet from Ingress. It is the total number of RTP data packets transmitted by the sender since starting transmission up until the time this SR packet was generated.
• Ingress Octets Sent - Received as part of RTCP Packet from Ingress. It is the total number of payload octets (i.e., not including header or padding) transmitted in RTP data packets by the sender since starting transmission up until the time this SR packet was generated.
• Ingress SSRC - Received as part of RTCP Packet from Ingress. It is the identifier of the source to which the information in this reception report block pertains.
• Ingress Fraction Lost - Received as part of RTCP Packet from Ingress. It is the fraction of RTP data packets from source SSRC_n lost since the previous SR or RR packet was sent and expressed as a fixed point number with the binary point at the left edge of the field.
• Ingress Interarrival Jitter - Received as part of RTCP Packet from Ingress. It is an estimate of the statistical variance of the RTP data packet inter-arrival time measured in timestamp units and expressed as an unsigned integer
• Ingress Cumulative Number of Packet Lost - Received as part of RTCP Packet from Ingress. It is the total number of RTP data packets from source SSRC_n that have been lost since the beginning of reception.
• Ingress Extended Highest Sequence Number - Received as part of RTCP Packet from Ingress. It is the highest sequence number received in an RTP data packet from source SSRC_n.
• Ingress Round Trip Time  - This field is not received as part of RTCP Packet from Ingress. It is calculated using available RTCP statistics.

An example of a Remote Ingress Audio RTCP Learned Metrics field is: "137,71200,0x452272d,0,0,0,28853,193".

Remote Egress Audio RTCP Learned Metrics

 The Remote Egress Audio RTCP Learned Metrics field indicates statistics received from Egress endpoint in SR/RR RTCP Packet. The maximum length of this field is 1024 characters, including all commas and double quotes (""). 
Subfields:

 Egress Packets Sent - Received as part of RTCP Packet from Egress. It is the total number of RTP data packets transmitted by the sender since starting transmission up until the time this SR packet was generated.

• Egress Octets Sent - Received as part of RTCP Packet from Egress. It is the total number of payload octets (i.e., not including header or padding) transmitted in RTP data packets by the sender since starting transmission up until the time this SR packet was generated.
• Egress SSRC - Received as part of RTCP Packet from Egress. It is the identifier of the source to which the information in this reception report block pertains.
• Egress Fraction Lost - Received as part of RTCP Packet from Egress. It is the fraction of RTP data packets from source SSRC_n lost since the previous SR or RR packet was sent and expressed as a fixed point number with the binary point at the left edge of the field.
• Egress Interarrival Jitter - Received as part of RTCP Packet from Egress. It is an estimate of the statistical variance of the RTP data packet inter-arrival time measured in timestamp units and expressed as an unsigned integer.
• Egress Cumulative Number of Packet Lost - Received as part of RTCP Packet from Egress. It is the total number of RTP data packets from source SSRC_n that have been lost since the beginning of reception.
• Egress Extended Highest Sequence Number - Received as part of RTCP Packet from Egress. It is the highest sequence number received in an RTP data packet from source SSRC_n.
• Egress Round Trip Time  - This field is not received as part of RTCP Packet from Egress. It is calculated using available RTCP statistics.

 An example of a Remote Egress Audio RTCP Learned Metrics field is: "137,71200,0x452272d,0,0,0,28853,193".

Final Route Label

This record is a string of up to 23 characters. The content of this record depends upon the Populate Primary and Final Routing Label ID in Billing CDR flag that is provisioned in the PSX and whether route hopping is enabled in the PSX.

When a call involves route hopping, the PSX refers the route table for routing labels, one for each level of hopping.

If the route hopping is enabled along with the Populate Primary and Final Routing Label ID in Billing CDR  flag in the PSX, then the SBC receives the following two route label IDs from the PSX:

1. Primary Route Label ID—the CDR field is populated as Route Label Field; this contains the primary routing label.
2. Final Route Label ID—the CDR field is populated as Final Route Label; this contains the last hopped primary routing label.

If the Populate Primary and Final Routing Label ID in Billing CDR  flag is disabled in PSX, then the SBC receives a single route label ID from PSX and the following cases hold good:

1. The Populate Final Routing Label ID in Billing CDR  flag is enabled and the route hopping is enabled in PSX—in this case, the CDR field is populated as Route Label Field; this contains the last hopped primary routing label.
2. The Populate Final Routing Label ID in Billing CDR  flag is enabled and the route hopping is disabled in PSX—in this case, the CDR field is populated as Route Label Field; this contains the primary routing label.
3. The Populate Final Routing Label ID in Billing CDR  flag is disabled and the route hopping is either enabled or disabled in PSX—in this case, the CDR field is populated as Route Label Field; this contains the primary routing label.

In all the cases mentioned above, the CDR field Final Route Label is empty (“”) when the SBC receives a single route label ID from the PSX.

MTA Information

SBC Call Data Record (CDRs) support storing Major Trading Area (MTA) information in CDRs. MTA is a boundary that segments a country for telecommunication licensing and consists of several Basic Trading Areas (BTAs). PSX can route the call based on MTA of calling and called parties. This record is a string, which may contain up to 49 characters. The content of this record depends upon the feature control profile and NPA NXX configuration in PSX.

If PSX determines MTA for calling and called parties, then PSX returns this information to SBC. Otherwise, the CDR field MTA Information is empty (“”).

This field is formatted as a quoted string of four comma-separated values. The values include; Origination Primary MTA, Origination Secondary MTA, Destination Primary MTA, and Destination Secondary MTA. For example,  ...,"18,11,08,11"....

The following table provides the MTA stream accounting information:

VBR Billing Data

SBC Call Data Record (CDRs) support storing Value Based Routing (VBR) information in CDRs.

The following fields are used to populate VBR details in SBC CDRs:

• VBR Common Billing Data
• VBR Route Billing Data

The following table provides the VBR stream accounting information:

VBR Common Billing Data

This record is a string of 256 characters. SBC receives the VBR Billing Information in the policy response and writes it to CDR. 

This field is optional and is populated when the PSX returns the VBR Route. 

The PSX captures the following common or global VBR information and sends it in the policy response:

• Destination
• Country Code
• Customer Id
• Offer Id
• Sell/Offer Price

The Sell/Offer price is present, if an Offer rate sheet is configured on the selected offer. SBC includes this data in the VBR Common Billing Data.

VBR Route Billing Data

This record is a string of 256 characters. For every route that is part of VBR routing label, the billing information is captured as per route data in the policy/trigger response by PSX and is sent to SBC. SBC treats it as opaque data and writes it to CDR. This field is optional. This is populated when the PSX returns a VBR Route.

For every route (routing label route) within a policy response, the following information is captured:

• Vendor ID
• Cost
• Jurisdiction

The Vendor Id represents the vendor who owns the Trunk Group. The cost is derived from active vendor rate sheet. The jurisdiction represents the jurisdiction associated with the selected rate sheet entry of the vendor. This may vary from vendor to vendor. For non VBR routes, this AVP will be empty. A maximum of 10 routes is considered for VBR Billing data purposes.

Access Network Charging Information

SBC includes the access-network-charging-info parameter received through PCRF over the Rx or Gx interfaces in the P-charging-vector header field in the first request or response originated by UE. When the charging information is available in SBC after the local resource reservation is complete, UE traverses the SBC. If P-CSCF receives Access Network Charging Information from PCRF server, P-CSCF sends Access Network Charging Information in the CAM records.

The format for Access Network Charging Information is "Character string, Max length 130".

Example: ggsn=10.10.0.1; auth-token=0;pdp-info=pdp-item=uniqueNum;pdp-dig=no;gcid=gcIdValue;flow-id=({0,0})

Access Transfer Specific Data

The location records for Access Transfer Specific Data are START, STOP, ATTEMPT, and INTERMEDIATE.

The following table details each of the sub-fields of Access Transfer Specific Data:

Emergency Indicator

The "Emergency Indicator" indicates the IMS session as an IMS emergency session or IMS registration. This covers both INVITE and REGISTER messages.

The format for Emergency Indicator is "Boolean of max length 1".

Ingress Dtls-Srtp: Dtls-Srtp status info

The "Ingress Dtls-Srtp: Dtls-Srtp status info" indicates if the DTLS negotiation in the corresponding stream is successfully completed, the value is enabled or disabled for an ingress call.

The supported values are:

• Empty (dtls disabled)
• 1 (dtls termination)
• 2 (dtls relay)

Egress Dtls-Srtp: Dtls-Srtp status info

The "Egress Dtls-Srtp: Dtls-Srtp status info" indicates if the DTLS negotiation in the corresponding stream is successfully completed, the value is enabled or disabled for an egress call.

The supported values are:

• Empty (dtls disabled)
• 1 (dtls termination)
• 2 (dtls relay)

UE Roaming Status

The format for UE Roming Staus is as follows:

Ingress Signaled Session Bandwidth in kbps

Prints the session bandwidth value signaled by Ingress EP.

Ingress Rx Computed Session Bandwidth in kbps

Computed using the traffic received from Ingress Peer (session) for the call duration that is,

Computed Rx Session Bandwidth = Sum of all received bytes for call adjusted to Link value/Call Duration.

Ingress Tx Computed Session Bandwidth in kbps

Computed using the traffic sent to Ingress Peer (session) for the call duration that is,

Computed Tx Session Bandwidth = Sum of all transmitted bytes for call leg adjusted to Link value/Call Duration.

Ingress Configured Bandwidth Reduction Factor

Prints the reduction factor configured in the Ingress PSP, used for this call.

Ingress Estimated Bandwidth Reduction Factor

Represents the factor that is resulted in the measured bandwidth for the ingress relative to the allocated bandwidth. That is,

Estimated Reduction Factor = 1 - (Maximum of Send and Received Computed Bandwidth/Signaled Bandwidth).

Egress Signaled Session Bandwidth in kbps

Prints the session bandwidth value signaled by Egress EP.

Egress Rx Computed Session Bandwidth in kbps

Computed using traffic received from Egress Peer (session) for the call duration that is,

Computed Rx Session Bandwidth = Sum of all received bytes for call adjusted to Link value/Call Duration.

Egress Tx Computed Session Bandwidth in kbps

Computed using traffic sent to Egress Peer (session) for the call duration that is,

Computed Tx Session Bandwidth = Sum of all transmitted bytes for call leg adjusted to Link value/Call Duration.

Egress Configured Bandwidth Reduction Factor

Prints the reduction factor configured in the Egress PSP, used for this call.

Egress Estimated Bandwidth Reduction Factor

Represent the factor that would have resulted in the measured bandwidth for the egress relative to the allocated bandwidth. That is,

Estimated Reduction Factor = 1 - (Maximum of Send and Received Computed Bandwidth / Signaled Bandwidth)

Additional Media Stream Statistics

Additional Media Stream Statistics is a string field and contains additional sub-fields. The sub-fields are comma separated values, which are included in the string.

The following table decribes the sub-fields for Additional Media Stream Statistics:

For more information, refer to Additional Media Stream Statistics Sub-fields for Audio Encoding for a description of the ingress codecParams1 and egress codec Params1 sub-fields.

Ingress Zone Name

This field provides the name of the Ingress zone.

Egress Zone Name

This field provides the name of the Egress zone.

Ingress Zone Id

This field provides the ID of the Ingress zone.

Egress Zone Id

This field provides the ID of the Egress zone.

Video Cac

The media type (Video) and CAC level (TG/zone/Shared...) of  a video stream that pruned because the configured video threshold limit is reached is included as a new CAM field called "Video Cac". This field includes the media type (video) and the CAC level  (TG, ZN, SH, EP....). This CAM field includes the following values, as applicable, when the video threshold level is reached:

• ZN-Video
• SH-Video
• TG-Video
• EP-Video

Ingress IP Prefix Found TG Name

The CDR includes "Ingress Trunk Group Name" field for both the ingress IPTG found with prefix match and the IPTG determined based on the SIP Message Manipulation (SMM). If SMM is not used to determine the ingress IPTG, the relevant CDR field is empty.

• If the ingress Trunk Group is configured using SMM and applied for a call:
  Ingress Trunk Group Name: TG Name configured using SMM
  Ingress IP Prefix Found TG Name: IPTG found with prefix match

• If the ingress Trunk Group is not configured using SMM or not applied for a call:
  Ingress Trunk Group Name: IPTG found with prefix match
  Ingress IP Prefix Found TG Name: empty

Transcode Resource Type

This field indicates the type of transcoder (Media Resource Function (MRF) or a TSBC) used for the call.

MRF Information

This field Stores MRF related information.

This field contains two sub-fields:

• Signaling IP
• Signaling PORT

Forking Call Parent GCID

This field binds all the forked calls initiated by one incoming call.

Call Recorder 1 RTP Tx Ip address

First Forking recorder Tx IP Address.

Call Recorder 1 RTP Tx Port Number

First Forking recorder Tx port number.

Call Recorder 1 RTP Rx IP address

First Forking recorder Rx IP Address.

Call Recorder 1 RTP Rx Port Number

First Forking recorder Rx Port Number.

Call Recorder 2 RTP Tx Ip address

Second Forking recorder Tx IP Address.

Call Recorder 2 RTP Tx Port Number

Second Forking recorder Tx port number.

Call Recorder 2 RTP Rx IP address

Second Forking recorder Rx IP Address.

Call Recorder 2 RTP Rx Port Number

Second Forking recorder Rx port number.

Call Recorder 3 RTP Tx Ip address

Third Forking recorder Tx IP Address.

Call Recorder 3 RTP Tx Port Number

Third Forking recorder Tx port number.

Call Recorder 3 RTP Rx IP address

Third Forking recorder Rx IP Address.

Call Recorder 3 RTP Rx Port Number

Third Forking recorder Rx port number.

SO-SBC

This field is added to the CAM records to indicate that the call was in a SO-SBC mode.

The SO-SBC field is a string field indicating the used signaling mode (global, onAnswer, onPolicyRsp....). The default is signaling only not set and this field will be empty.

The following are the proposed string values:

• SO-g - indicates signaling only on global mode.
• SO-p  - indicates signaling only on policy response.
• SO-a - indicates signaling only on answer.

Audio Stream Statistics

The following table lists the attributes for audio stream statistics:

 

Audio Stream RTCP-XR Voice Metric Statistics

The following table lists the attributes for audio stream RTCP-XR voice metric statistics.

Media Stream SRTP Statistics

The following table lists the attributes for media stream SRTP statistics:

DSP insertion/rejection reason

Reason for a DSP resource’s inclusion in a media flow, or for its rejection upon request.

The reason include the following:

• Transcoding
• Transrating
• DTMF
• SilenceSuppression
• Rejected codec not configured
• Rejected codec unlicensed. The DSP Rejection reason is set to "Rejected codec unlicensed" in the following cases:
  • The SBC doesn't have DSP.
  • The SBC has DSP but codec licenses are absent.
  • The SBC has DSP and codec licenses but transcoding is not enabled for the codecs.

In any of the above cases, if Passthru is possible and if the call is successful, then the DSP Rejection reason is updated after a successful offer answer.

• Rejected unrelated to DSP
• No DSP inserted

DSP insertion/rejection reason is in both the STOP record and ATTEMPT record.

Call Established Time

The SBC calculates the Call Established Time using the following fields stored in the CDR records:

• Start Time (Date) of the call from field number 6
• Start Time (Time) of the call from field number 7
• Ticks from Setup Msg to Service Est from field number 10 in START and STOP Records and INTERMEDIATE records from field number 9
  
  

You must use this field when indexing route specific fields within the PSX Billing Info Field. See "PSX Billing Information".

Over Flow Packets Count

The Over Flow Packet Count field includes the count of overflow packets that are beyond the limit allowed by the policy control.

The count is per stream for both ingress and egress leg separately that are displayed as sub-field.
The maximum length of each sub-field ingress or egress over Flow Packet Count is 20.
Depending upon number of streams, the size of “Over Flow Packets Count” may vary

The field is generated for STOP CDR (field number 284), as this information is available only after the call is terminated.

The format of the subfields is as follows:

 

ingress overFlowPacketsCount1

egress overFlowPacketsCount1

ingress overFlowPacketsCount2

egress overFlowPacketsCount2

ingress overFlowPacketsCount3

egress overFlowPacketsCount3

ingress overFlowPacketsCount4

egress overFlowPacketsCount4

ingress overFlowPacketsCount5

egress overFlowPacketsCount5

ingress overFlowPacketsCount6

egress overFlowPacketsCount6

Ingress Trunk Group for PSX Routing

By default, the SBC selects the ingress trunk group for an incoming SIP request based on its source IP address and port. Using SIP Message Manipulation (SMM) operations and SIP Param Based Action profiles, the SBC supports a feature to select a new ingress trunk group. Secondary trunk group selection enables applying trunk group policies and profiles on a more granular basis in subsequent processing of the session.

If a new ingress trunk group is chosen using this feature, the existing CDR field Ingress Trunk Group Name is populated with the new trunk group name and this field contains the original ingress trunk group that was selected based on the source IP/port and sent to the PSX for policy information prior to the change to the new ingress trunk group. If a new trunk group is not selected, both the "Ingress Trunk Group Name" field and this field contain the same value.

T140 Information

 This field is populated if generateRtcpForT140IfNotReceived is enabled. For call modify scenarios, this field is populated based on the monitoring outcome of the last mid-call update. the SBC is provisioned to monitor RTCP for T140 stream. If RTCP is not received within monitoring interval, then the SBC moves to generate mode. The possible values are Relay (if RTCP is relayed by the SBC) or Generate (if RTCP is generated by the SBC).

Remote T140 RTCP Learned Metrics

This field displays the remote RTCP Learned metrics, and shall be populated when RTCP is relayed by the SBC and when generateRtcpForT140IfNotReceived is enabled.

Beep Tone Inserted

This field indicates if a beep tone is played for the recorded call.

Possible values:

• 0 – No
• 1 – Yes

Direction of Beep Tone

This field specifies the direction of the beep tone.

Possible values:

• 1 – Ingress
• 2 – Egress
• 3 – Both

Start Time (Local)

Local timestamp when Setup Request was received.

Disconnect Time (Local)

Local timestamp when a Disconnect Request was received for the call.

Intermediate Time (Local)

Local timestamp when the Intermediate Accounting Timer expired.

Call Established Time (Local)

Local timestamp when the call was established.

CAC Fail Info

Provides CAC usage failure information. Provides CAC failure details, like level of CAC and type of CAC, and location. Records reason text and Q.850 code in CDRs. The field 212 CAC Fail Info is added to the Attempt record of the CDR.

CAC Fail Info Sub-fields

212.1 CAC Level

Possible values:

• Trunk Group
• Zone
• End Point

212.2 CAC Type

Possible values:

• Call Limit
• Ingress Call Limit
• Egress Call Limit
• Ingress Call Rate
• Egress Call Rate

212.3 Cause Text

Example: TG Call Rate exceeded.

212.4 Q850 Code

Example: 120.

Media IPSec Information

The 295. Media IPSec Information field added to the STOP record captures the following Media IPsec Information:

Total Size: 7+32+32 = 71 characters + 2 quotes "" + 2 commas between 1,2,3 fields = 71+4 = 75 characters.

VTP Information

Indicates that ingress and/or egress leg are VTP.