CDR Field Descriptions

Accounting Records Summary Table

The following table lists the SBC 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 - the timestamp of when Setup Request was received (Decimal number 0 - 4294967295).

Node Time Zone

Node Time Zone (up to 23 characters).

This field must be occupied by one of the following strings:

• "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) - GMT date stamp when Setup Request was received. This value is provided by NTP.

In the REBOOT record, this is the date the SBC was last booted.

Start Time (Time)

Start Time (hh:mm:ss.d) (d=deci-seconds) - GMT 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 SBC was last booted.

Old Software Version

The Old Software Version field represents the SBC 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/SBC software running after a Live Software Upgrade, and is a 14-character string in the following format:2:

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/ Sonus 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) - GMT datestamp when Intermediate Accounting Timer expired, for example 02/06/1999.

Intermediate Time (Time)

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

Disconnect Time (Date)

Disconnect Date (mm/dd/yyyy) - GMT 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) - GMT 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/SBC 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 Sonus Reason Codes. The Sonus Reason Codes are never contained in messages sent to the PSTN, but are instead mapped to an appropriate Q.931 Standard code.

The Sonus 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 GSX/SBC 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/SBC, 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 Mappings

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 Sonus. 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/SBC 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/SBC 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/SBC 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/SBC 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/SBC gateway-to-gateway protocol, Call Direction = "PSTN-TO-IP". A call that has ingress signaling as H.323, and egress signaling as GSX/SBC 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/SBC 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/SBC after successfully routing the call based on digits collected before receiving overlap address signaling message.

For example, if GSX/SBC 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/SBC 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 1 - 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 SBC.

• 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 SBC 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/SBC 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/SBC 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.

Example Trunk Groups

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/SBC 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 Sonus CPL script that was executed for the call.

Multiple variables may be logged within this field, with each variable data separated from the next variable by a configurable separator. The default value for the separator is slash . 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 Sonus 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).

Called Party Nature of Address

The type of Called Party number (decimal value).

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

Ingress Signaling Type

The ingress signaling type (decimal value).

Egress Signaling Type

The egress signaling type (decimal value).

Ingress Far End Switch Type

The ingress far end switch type (decimal value).

Egress Far End Switch Type

The egress far end switch type (decimal value).

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/SBC 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.

Trunk Ownership Fields in START/STOP Records

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/SBC, this is the actual dialed number contained in the incoming setup message (IAM) received by the GSX/SBC from the ingress signaling group before any digit manipulation or address translations are performed by the ERE.

On the egress GSX/SBC, 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 Sonus 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 Sonus 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 Sonus 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/SBC. 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/ SBC. 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 GSXSBC, 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/SBC 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 (in millisecond) recorded by the ingress DSP/NP.  This field is the decimal representation of a 16-bit number, and accepts values 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.

Figure XXX illustrates the basic call flow between the Ingress trunk group, SBC and Egress trunk group.

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:

• BT-IUP Variant Sub-field Descriptions
• Country-Specific Sub-Fields
  • Argentina Signaling Sub-field Descriptions
  • India Signaling Sub-field Descriptions
  • Japan ISUP Variant Sub-field Descriptions
  • Portugal ONI Signaling Sub-field Descriptions
  • Slovak ISUP Signaling Sub-field Descriptions
  • UK ISUP Signaling Sub-field Descriptions
• 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 SBC 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 SBC 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 Sonus 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 Sonus 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 Sonus 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/SBC, uniquely identifies a call within a single SBC and hence is equivalent to the SBC's internally assigned Global Call ID (GCID). This value is unique for this call within a SBC, but will vary from SBC to SBC. Use the Gateway-to-Gateway Handle to uniquely identify a call across multiple SBCs. (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/SBC before terminating the call; the call was not routed.

Originator Echo Cancellation

This field (decimal, 0-1) identifies whether or not the GSX/SBC performed echo cancellation on the ingress leg of this call. Possible values:

• 0 – GSX/SBC did not perform echo cancellation on ingress leg of call.
• 1 – GSX/SBC 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/SBC performed echo cancellation on the egress leg of this call as follows:

• 0 – GSX/SBC did not perform echo cancellation on egress leg of call.
• 1 – GSX/SBC 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/SBC 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/SBC 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/SBC is the terminating switch, then the GSX/SBC generates this parameter. Otherwise, the downstream legacy switch generates this parameter, and then the GSX/SBC 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 SBC 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

PSX Billing Info Field Diagram

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

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

Terminating TDM Trunk Group Type

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

Ingress Trunk Member Number

Ingress Trunk Member Number. The ingress trunk member number that was provisioned on the GSX/ SBC  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/SBC.

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/SBC 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/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/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/SBC 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 (Sonus) 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/SBC extracts this decimal value (0-65536) from the optional "Outgoing Route Identification (ORI)" parameter in the ISUP Address Complete Message (ACM).

If GSX/SBC 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/SBC deployed in a Singapore network. The GSX/SBC 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/ SBC 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/SBC 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/SBC is not a transit exchange, then the Outgoing Message Identification is set to "2" (Terminating Route).

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

Incoming Route Identification

The incoming trunk group number on a GSX/SBC deployed in a Singapore network. The GSX/SBC 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/SBC 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 acharacters of name information coded in IA5 format. The GSX/SBC 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/SBC 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/SBC 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/SBC 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/SBC 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/SBC 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/SBC 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/SBC 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/SBC logs this value. See Incoming ISUP Charge Number NOA.

The GSX/SBC 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/SBC in the Policy Response message. The GSX/SBC 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/SBC logs this NOA in this field.

his 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/SBC 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 ("").