Table Of Contents
Call Detail Block File Fields
Revised: January 5, 2009, OL-15338-05The Cisco BTS 10200 system stores the raw call detail blocks (CDBs) in a flat file ASCII-based format on the persistent store associated with the Bulk Data Management System (BDMS). The BTS 10200 stores a minimum of 10 megabytes of billing records in a circular file implementation. This data is subsequently sent to the specified remote accounting office or billing server or mediation device by the File Transfer Protocol (FTP).
This chapter illustrates the format of each field in a Call Detail Block (CDB), the order in which the field occurs, the possible values for the individual fields, and the meaning of the data within the field where applicable. The delimiters used to separate fields within a record or records within a file can be any one of the following:
•
semi-colon ";"
•
•
•
•
Note
The CDB field and record separators are defined in the platform.cfg file that is read at initialization time. The platform.cfg file associated with the BDMS platform must be updated for changes to take effect; however, the file cannot be changed without a system restart. Both active and standby BDMS platforms must be restarted for changes in delimiters to be picked up.
The ProcessParameter block to update is ProcName=BMG. The parameter to update is Args. To change the field delimiter you must update the -FD option. To change the record delimiter you must update the -RD option. Both of the BDMS computing platforms must be restarted to pick up this change of delimiters.
Caution
The steps to follow are
1. Stop the platform on the EMS.
2. Change the platform.cfg on the EMS.
3. Flush the old billing records from the EMS before starting the platform.
4. Start the platform. All new billing records now use the new format.
Table 4-1 provides information about the fields in the output files transmitted from the Element Management System (EMS) on the BTS 10200.
Table 4-1 Call Detail Block Field Descriptions
1
Call Type
Numeric
0=NULL
1=TEST-CALL
2=INTL
3=LOCAL
4=TOLL
5=INTERLATA
6=TANDEM
7=EMG
8=NON-EMG
9=DA
10=DA-TOLL
11=REPAIR
12=RELAY
13=BUSINESS
14=TOLL-FREE
15=900
16=500
17=700
18=976
19=VACANT
20=PCS
21=INVALID
22=NONE
23=LRN
24=EXTENSION
25=CUT-THRU
26=OPERATOR
27=CARRIER- OPERATOR
28=OPERATOR-ASSISTED
29=BLV
Destination: CallType or derived based on the dialing pattern—for example: 0-, 00 calls OR SpecialCallType:: CallType or LSA table for determining LOCAL or LATA table used for determining TOLL and INTERLATA of CallType = NATIONAL in Destination table.
The nature of the call, which indicates the type of accounting processing to apply to it. Call Type NULL is used for any calls that do not progress to the point where a lookup in the Destination table occurs, or if routing is not needed—as in cases of feature activation or deactivation.
In Release 6.0.x, there is a new parameter, CALLTYPE-OPER-CALL-CDR in the ca-config table. For additional information, see "Operator Call Type in Field 1" section.
In Release 5.0, the system reports the data in Field 1 (Call Type) of the call detail block (CDB) when the user dials a call to the operator (0 or 00) or a call involving an operator (0+ or 01+). For additional information on the data in Field 1, see "Release 5.0.x Behavior" section.
30=SPEED-DIAL
31=NATIONAL
32= TW
33=INFO
34=PREMIUM
35=ATTENDANT
36=NAS
37=POLICE*
38=FIRE*
39=AMBULANCE*
40=TIME*
41=WEATHER*
42=TRAFFIC*
43=LOOPBACK_TEST (Deprecated)
44=INTL_OPERATOR
45=NATL_OPERATOR
46=AIRLINES*
47=RAILWAYS*
48=SERVICE_CODE
49=INTL_WORLD_ZONE_1
50=CALLING_ NUMBER_ANNC
51=DA_INTERLATA
52=DA_INTL
53=UNIV_ACCESS_NUM
54=MOBILE
55=WAKE_UP
56=AS
* - not used in NANP areas
2
Signal Start Time
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
Time starts on receipt of an MGCP NTFY, SS7 IAM or SIP SETUP.
3
Signal Stop Time
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
Time stops on the last of the following signaling events:
1.
2.
3.
4
Interconnect Start Time
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
Time starts on commitment of bandwidth between the IP/ATM and PSTN networks.
5
Interconnect Stop Time
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
Time stops on release of bandwidth between the IP/ATM and PSTN networks.
6
Call Connect Time
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
Time starts on receipt of an MGCP NTFY indicating off-hook, or SS7 ANS, or answer indication from the media gateway for an operator services trunk.
7
Call Answer Time
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
Upon both parties being off-hook for at least 2 seconds. Currently the Cisco BTS 10200 does not support Short Supervisory Transitions, so the contents of this field and field #6 are identical.
8
Call Disconnect Time
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
Time starts on receipt of an MGCP NTFY indicating on-hook of the calling party, or expiration of the call-continuation timer, an SS7 REL, or an indication from the media gateway that the operator services trunk has disconnected.
9
Database Query Time1
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
The time the first database query response was received for this call.
10
Service Instance Time1
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
The time the instance of Service Type 1 occurred.
11
Service Instance Time2
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
The time the instance of Service Type 2 occurred.
12
Service Instance Time3
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
The time the instance of Service Type 3 occurred.
13
Service Activation Time1
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
The time the activation of Service Type 1 occurred.
14
Service Activation Time2
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
The time the activation of Service Type 2 occurred.
15
Service Activation Time3
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
The time the activation of Service Type 3 occurred.
16
Service Deactivation Time1
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
The time the deactivation of Service Type 1 occurred.
17
Service Deactivation Time2
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
The time the deactivation of Service Type 2 occurred.
18
Service Deactivation Time3
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
The time the deactivation of Service Type 3 occurred.
19
Call Elapsed Time
String
12-17
(dddd):hh:mm:ss.mmm
Calculated value.
The duration that the voice path was established. The days (ddddd) portion of this field is optional and variable in length depending on the number of days the calls has been connected. If this field is NULL, then no data was captured for this record.
RecordGenTime is an optional parameter. It gives the time of day at which the first time BLG should check to see whether any long-during billing records need to be generated. If it is not specified, it defaults to midnight.
LongDurationAllowance is an optional parameter. It gives the length of time, in minutes, that a call must have been in the answered state at the time when records are generated, in order for a long -duration record to be generated for it. It is also the interval of record generated time. After RecordGenTime generates billing records for the first time, every LongDurationAllowance minutes interval BLG checks to see whether any long-during billing records need to be generated. If it is not specified, it defaults to 1,440 minutes (24 hours).
For example, if RecordGenTime is 12:00:00, LongDurationAllowance is 60.
At 12:00:00, BLG checks the long-duration call for the first time. It then checks the call every 60 minutes thereafter.20
Interconnect Elapsed Time
String
12-17
(dddd):hh:mm:ss.mmm
Calculated value.
The duration that bandwidth was established with another carrier. The days (ddddd) portion of this field is optional and variable in length depending on the number of days the calls has been connected. If this field contains NULL, then no data was captured for this record.
21
Originating QOS Time
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
Receipt of the MGCP DLCX ACK message. The time the originating side quality of service measurements were collected. This information is collected on a best effort basis and will not be present if the QoS collection timeout is exceeded. If this field contains NULL, then the associated Originating QOS parameters are to be ignored.
22
Terminating QOS Time
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
Receipt of the MGCP DLCX ACK message. The time the terminating side quality of service measurements were collected. This information is collected on a best effort basis and will not be present if the QoS collection timeout is exceeded. If this field contains NULL, then the associated Terminating QOS parameters are to be ignored.
23
Originating Number
String
64
DIGITS
Subscriber::DN1, ISDN SETUP, SS7 IAM, or SIP INVITE, for example.
This field contains the calling party number after it has gone through the complete translation process on the Cisco BTS 10200 including any possible overriding. If the originator of a SIP field contains the tel-number in the From field between the ":" and the "@" characters if the PAI flag is not set. If the PAI flag is set, this field contains the tel-num from the P-Asserted-Identity field between the ":" and the "@" characters.
If this field contains NULL, then no data was captured for this field.
24
Terminating Number
String
64
DIGITS
Subscriber::DN1, ISDN SETUP, SS7 IAM, or SIP INVITE, for example.
The directory number of the terminating party. For outbound LNP calls, this field contains the dialed DN. For calls inbound to the Cisco BTS 10200, this field will contain DN of the terminating subscriber. If this field contains NULL, then no data is captured for this record.
25
Charge Number
String
64
DIGITS
Subscriber:: BillingDn or FCP Message.
Directory number of the billable party. For Mexican ISUP scenarios this field is populated with the tarrification number. If this field contains NULL, then no data was captured for this record.
26
Location Routing Number
String
64
DIGITS
LNP Query or SS7 IAM.
The location routing number of the switch where the directory number is ported to.
The Cisco BTS 10200 does an LNP query on outbound calls if the called number is addressed in the Ported Office Code table. This field is then populated with the LRN obtained from doing the LNP query as long as the returned LRN is not equal to the LRN of the reporting Cisco BTS 10200.
For calls that are inbound to the Cisco BTS 10200, if the called number is addressed by the Ported Office Code table and the LNP-TRIGGER flag is set (meaning the reporting Cisco BTS 10200 is the recipient switch), then a query to the DN2SUBSCRIBER table determines if an LNP query is performed or not.
For inbound calls that are addressed by the Ported Office Code table but the Cisco BTS 10200 is not the recipient switch, then the service-id assigned to the incoming trunk group determines whether an LNP query is launched or not. In addition, for inbound SS7calls, the M-bit in the IAM is checked to see if an LNP query has already been performed—if not—then the Ported Office Code table is queried before conducting a LNP dip.
This field is populated with the received LRN, if one is presented for inbound calls to the reporting Cisco BTS 10200 for the called numbers that are homed on the Cisco BTS 10200.
The Ported Office Code table is typically populated by LERG updates received by the service provider.
26 (continued)
Location Routing Number
String
64
DIGITS
LNP Query or SS7 IAM.
If an LRN is returned from an LNP query, it is used in routing the call, otherwise the dialed digits are used to route the call.
The Cisco BTS 10200 only makes one attempt per call to query the LNP database. If the query fails, the call is routed as if the dialed number is not ported.
If this field is NULL, then no data was captured for this record.
27
Dialed Digits
String
64
DIGITS
This field contains the actual digits dialed by the originator of the call. This field only contains digits dialed in the first stage of the call if the person dialing is a subscriber who is homed on the BTS 10200.
MGCP NTFY, SS7 IAM, ISDN SETUP, SIP INVITE or H.323 SETUP, for example.
This field is intended for basic troubleshooting purposes only. If the call is terminating to this Cisco BTS 10200 from a subscriber homed elsewhere, then this field will contain the information in the ieCldPartyNum field. In this case, the digits stored may have been manipulated after the originator dialed.
Due to the fact that this field only contains the 1st stage digits, the collection of digits will cease once the media gateway on the originating side of the call sends the initial digits, which is digit map based in the gateway. Once a match to the digit map is accomplished, the digits are packaged up and sent to the Cisco BTS 10200 in the appropriate NCS/MGCP message which triggers the Signaling Start event within the Cisco BTS 10200 for that call.
If this field is NULL, then no data was captured for this record.
28
Forwarding Number
String
64
DIGITS
SS7 IAM or original dialed number.
Directory number that is forwarding the call to another subscriber's DN. This field is populated only in the call forwarding instance record leg, not in the normal call leg that terminated to the forwarding number. If this field is NULL, then no data was captured for this record.
29
Service Type 1
Numeric
1 = CALL_BLOCK (not used)
2 = CALL_ FORWARD_UNCONDITIONAL
3 = CALL_
WAITING4 = REPEAT_
CALL5 = RETURN_
CALLInternal FCP message sent from the feature server to call processing.
Class type name of the first service invoked in call. If this field is NULL, then no data was captured for this record.
Service Types that are greater than 200 are reported as AS SERVICE_XXX, where XXX is the value of the service type stored in the CDR. This is done to provide App-Server-Specific Service Types.
6 = CALL_HOLD
7 = THREE_WAY_CALL
8 = CALL_TRANSFER
9 = CALLING_NUMBER_DELIVERY
10 = CALLING_NUMBER_DELIVERY_BLOCK
11 = CALL_FORWARD_BUSY
12 = CLASS_OF_SERVICE
13= CALLING_NAME_DELIVERY (not used)
14 = CALL_FORWARD_NO_ANSWER
15 = AIN_HANDLING (not used)
16 = 911_HANDLING
17 = CUSTOM_DIALING_PLAN
18 = CALLING_ID_DELIVERY_BLOCK_PERM (not used)
19 = SFG_INCOMING
20 = SFG_OUTGOING
21 = CANCELLED_CALL_WAITING
22 = USER_SENSITIVE_3WAY_CALL
23 = TOLL_FREE (not used)
24 = ACCT_CODE
25 = AUTH_CODE
26 = LOCAL_NUMBER_PORTABILITY (not used)
27 = CALLING_IDENTITY_DELIVERY_SUSPENSION
28 = CALLING_NAME_DELIVERY_BLOCKING
29 = CALL_WAITING_WITH_CALLER_IDENTITY
30 = ANONYMOUS_CALL_REJECTION
31 = TOLL_FREE_CALL (not used)
32 = CUSTOMER_ORIGINATED_TRACE
33 = CALL_PARK
34 = CALL_PARK_RETRIEVAL
35 = CALL_PARK_REOFFERED
36 = DIRECTED_CALL_PICKUP WITH BARGE-IN
37 = DIRECTED_CALL_PICKUP WITHOUT BARGE-IN
38 = HOTLINE
39 = WARMLINE
40= BUSY_LINE_ VERIFICATION
41 = SELECTIVE_CALL_REJECTION
42 = SELECTIVE_CALL_FORWARDING
43 = SELECTIVE_CALL_ACCEPTANCE
44 = AUTOMATIC_CALLBACK
45 = AUTO_RECALL
46 = SPEED_CALLING
47 = DO_NOT_DISTURB
48 = REMOTE_ACTIVATION OF CALL_FORWARDING
49 = REMOTE_ACTIVATION OF CALL_FORWARDING PIN
50 = DRCW DISTINCTIVE_RING_CALL_WAITING
51 = SCREENING_LIST_EDIT SCF
52 = SCREENING_LIST_EDIT SCA
53 = SCREENING_LIST_EDIT SCR
54 = SCREENING_LIST_EDIT DRCW
55 = REJECT_CALLER
56 = CALL WAITING DELUXE
57 = THREE WAY CALL DELUXE
58 = OUTGOING CALL BARRING
59 = HOTLINE VARIABLE
60 = CNAM SCP QUERY
61 = SIP REFER
62 = CALL FORWARD COMBINATION
63 = NO SOLICITATION ANNOUNCEMENT
64 = PRIVACY SCREENING
65 = VOICE MAIL
66 = VOICE MAIL ACCESS
67 = LCD PREPAID
68 = LCD POSTPAID
69= MULTIPLE DIRECTORY NUMBER
70=SIP REPLACE
71=CALL FORWARD REDIRECT
72=OFF HOOK TRIGGER
73=TERM ATTMP TRIGGER
74=OCNA
75=SEAS
76=ENUM
77=ENUM LNP
78=TMB
79=GMB
EMERGENCY_CALL_BACK = 80
TAS_MODE = 81
HOSTAGE_NEGOTIATION = 82
CALL_FORWARD_NOT_REACHABLE = 83
AS_SERVICE_XXX, When XXX greater than 200
30
Service Type 2
Numeric
(Same as Service Type 1 above)
Internal FCP message sent from the feature server to call processing.
The class type name of the second service invoked within the call.
31
Service Type 3
Numeric
(Same as Service Type 1 above)
Internal FCP message sent from the feature server to call processing.
The class type name of the third service invoked within the call.
32
Feature Data One1
String
130
See Chapter 3, "Feature Server-Derived Call Data" for specifics on feature data.
Internal FCP message sent from the feature server to call processing.
The first datum of feature specific data provided by the associated Feature Server for Service Type 1 of a call. If this field is NULL, then no data was captured for this record.
33
Feature Data One2
String
130
See Chapter 3, "Feature Server-Derived Call Data" for specifics on feature data.
Internal FCP message sent from the feature server to call processing.
The first datum of feature specific data provided by the associated Feature Server for Service Type 2 of a call. If this field is NULL, then no data was captured for this record.
34
Feature Data One 3
String
130
See Chapter 3, "Feature Server-Derived Call Data" for specifics on feature data.
Internal FCP message sent from the feature server to call processing.
The first datum of feature specific data provided by the associated Feature Server for Service Type 3 of a call. If this field is NULL, then no data was captured for this record.
35
Authorization Code
String
25
DIGITS
Internal FCP message sent from the feature server to call processing.
Authorization code information. If this field is NULL, then no data was captured for this record.
36
Account Code
String
15
DIGITS
Internal FCP message sent from the feature server to call processing.
Account code information. If this field is NULL, no data was captured for this record.
37
Database Query Type1
Numeric
1 = TOLL_FREE_ SCP
2 = TOLL_FREE_ LOCAL
3 = LNP
4 = CNAM_SCP
5 = ENUM
6 = ENUM LNP
Internal FCP message sent from the feature server to call processing.
Indicator of the specific type of 800 or LNP query performed on the first database query for the call. If this field is NULL value, then no data was captured for this record.
38
Database Query Result Code1
Numeric
1 = SUCCESS
2 = FAILUREInternal FCP message sent from the feature server to call processing.
Indication of the disposition of the first database query for the call. If this field is a value of NULL, then no data was captured for this record.
39
Database Query
String
128
For CNAM_SCP: Caller's Name or P (private) or O (out of area)
For TOLL_FREE_SCP and TOLL_FREE_LOCAL: original called digits or new called digits returned
For LNP: original called DN or new LRN (ANSI w/LNP profile=LRN)
For LNP: original called DN or concatenated RN plus DN (non-ANSI w/LNP profile=PREFIX-METHOD)
For LNP: original called DN or RN (non-ANSI w/LNP profile=SEPARATE-RN)
For ENUM: AOR or domain name
For ENUM LNP: new LRN
Internal FCP message sent from the feature server to call processing.
Directory number, RN and/or NAME returned from the first database query for the call. If this field is NULL, then no data was captured for this record.
Caveat: If this field contains a character that coincides with the character specified as the field or record delimiter for the Cisco BTS 10200 billing records, it is replaced with a SPACE character to ensure the integrity of the billing data.
40
MLH Group
String
16
Up to a 16-character group name
Subscriber::MlhgId
The multi-line hunt group that this call is associated with. If this field is null, then no data is captured for this record.
41
Called Party Off Hook Indicator
Numeric
0 = NO
1 = YESSS7 ANM, MGCP Offhook NTFY, ISDN ACK, for example.
Indication that the terminating party went off-hook. If this field is NULL, then no data was captured for this record.
42
Called Party Short Off Hook Indicator
Numeric
0 = NO
1 = YESn/a
An indication that the called party was off hook for less than 2 seconds. This field is currently not supported on the Cisco BTS 10200, and will always be populated with a value of NULL.
43
Call Termination Cause
Numeric
See Appendix C, "Release Cause Codes," in the Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.x.
Release indications are both internally and externally detected— dynamic runtime data.
The reason the call was released. If this field is a value of NULL, then no data was captured for this record.
44
Operator Action
Numeric
0 = AUTO_ IDENTIFIED_
CUSTOMER_ DIALED1 = AUTO_ IDENTIFIED_
OPERATOR_ DIALED2 = OPER_ DENTIFIED_
CUSTOMER_ DIALED3 = OPER_ IDENTIFIED_
OPERATOR_ DIALEDOperator action with respect to the originating party:
•
customer dialed (0) or operator dialed (1)
or•
customer dialed (2) or operator dialed (3)If this field is NULL, then no data was captured for this record.
45
Originating Signaling
TypeNumeric
0 = MGCP or SIP LINE
1 = SS7
2 = ISDN
3 = CAS
4 = MGCP
5 = SIP
6 = H323
TrunkGroup:: TGType
This denotes the trunk type of the originator. The value of MGCP TRUNK is indicates of an Announcement Trunk.
46
Termination Signaling Type
Numeric
0 = MGCP or SIP LINE
1 = SS7
2 = ISDN
3 = CAS
4 = MGCP
5 = SIP
6 = H323
TrunkGroup:: TGType
This denotes the trunk type of the originator. The value of MGCP TRUNK is indicates of an Announcement Trunk.
47
Originating Trunk Number
Numeric
32 bit unsigned integer in the range of 1-99999999
TrunkGroup::Id
Identity of the originating trunk. It is recommended the upper end of this range be limited to 9999 when converting these records to BAF AMA format for compatibility.
If this field is a value of NULL, then no data was captured for this record.
48
Terminating Trunk Number
Numeric
32 bit unsigned integer in the range of 1- 99999999
TrunkGroup::Id
Identity of the terminating trunk. It is recommended the upper end of this range be limited to 9999 when converting these records to BAF AMA format for compatibility.
If this field is a value of NULL, then no data was captured for this record.
49
Outgoing Trunk Number
Numeric
16 bit unsigned integer
SS7 EXM
The outgoing trunk is on the network facing side of the access tandem. When a call is terminated to the access tandem it is over a generic trunk group and the TNS is passed. Based on the TNS, the access tandem will select the trunk for routing. For example, 0288 will select an AT&T trunk. The access tandem then sends an exit message back with the trunk number from the network facing side. That is the number that appears in this field.
50
Carrier Identification Code
String
5
DIGITS
SS7 IAM or Subscriber::PICn or dialed digits for casual dialing scenarios.
Identification of the carrier that transported the call, either an inter-exchange carrier or an international carrier. This value is typically 3 or 4 digits, not necessarily 5 digits. If this field is NULL, then no data was captured for this record.
For a toll-free call, if the returned SCP message contains the carrier ID, the billing record show the carrier ID.
51
Originating Circuit Identifier
16 bit unsigned integer in the range of 0-16383
Trunk::Id
This field is used to represent the Circuit Id of Inc ISUP trunk. If this field is a value of NULL, then no data was captured for this record.
52
Terminating Circuit Identifier
Numeric
16 bit unsigned integer in the range of 0 - 16383
Trunk::Id
This field is used to represent the Circuit Id of Outgoing ISUP trunk. If this field is a value of NULL, then no data was captured for this record.
53
PIC Source
Numeric
1 = PIC_DIALED
2 = PIC_DEFAULT
Dialed digits.
Indication of how the carrier's access code was entered—dialed or by PIC. If this field is a value of NULL, then no data was captured for this record.
54
Inter
exchange carrier or international carrier indicatorNumeric
0 = CIC_FGD_OPERATOR_
INVOLVED1 = CIC_FGD_OPERATOR_ NOT_INVOLVED
2 = CIC_FGD_OPERATOR_
INVOLVED_UNKNOWN7 = CIC_UNKNOWN_ OPERATOR_INVOLVED
8 = CIC_UNKNOWN_ OPERATOR_NOT_ INVOLVED
9 = CIC_UNKNOWN_ OPERATOR_INVOLVED_ UNKNOWN
Dialed digits.
Describes operator involvement: FGD CIC with:
1.
2.
3.
–
–
–
This field is applicable only in calls interconnected to other carriers.
If this field is NULL, then no data was captured for this record.
55
Inter-
exchange carrier or international carrier Event Status IndicatorNumeric
Call is abandoned or released before IAM is sent by originating EC = 15
Call is abandoned or released after IAM is received by originating EC = 20
Dynamic call data.
Indication of how far a call has progressed before termination when an IC/INC is involved.
This field is only applicable to SS7 calls that are interconnected to another carrier. If this field is a value of NULL, then no data was captured for this record.
56
Inter-
exchange carrier or international carrier Routing IndicatorNumeric
0 = DIRECT
1= TANDEM
2 = CAP_ENDOFFICE
3 = CAP_TANDEM
4 = TANDEM_TSP
Hard coded.
Describes how the call was routed to/from the IC/INC: EAEO direct to IC/INC, or EAEO by AT to INC/IC, or CAP direct from EO, or CAP direct from AP tandem.
This field is only applicable in calls that are interconnected to other carriers.
Currently only the value of 0 is supported. Values 1, 2, 3, and 4 are reserved for future use.
57
QoS Orig Local Packets Sent
Numeric
0-999,999,999
MGCP DLCX ACK, DLCX
The total number of RTP data packets transmitted by the originating end point since transmission was started.
If this field is NULL, then no data was captured for this record.
58
QoS Orig Packets received
Numeric
0-999,999,999
MGCP DLCX ACK, DLCX
The total number of RTP data packets received by the originating end point since reception was started.
If this field is NULL, then no data was captured for this record.
59
QoS Orig Local Octets Sent
Numeric
0-999,999,999
MGCP dLCX ACK, DLCX
The total number of payload octets transmitted in RTP data packets by the originating endpoint since starting transmission. This count does not include headers or padding. This count can be used to estimate the average payload rate.
If this field is NULL, then no data was captured for this record.
60
QoS Orig Octets Received
Numeric
0-999,999,999
MGCP DLCX ACK, DLCX
The total number of payload octets received in RTP data packets by the originating endpoint since starting reception. This count does not include headers or padding. This count can be used to estimate the average payload rate.
If this field is NULL, then no data was captured for this record.
61
QoS Orig Local Packets Lost
Numeric
0-999,999,999
MGCP DLCX ACK, DLCX
The total number of RTP data packets that have been lost since the beginning of reception by the originating endpoint. This number is defined as the number of packets expected less the number of packets actually received, where the number of packets received includes any which are late or duplicates. The packets that arrive late are not counted as lost and the loss may be negative if they are duplicates. The number of packets expected is defined as the extended last sequence number received less the initial sequence number received.
If this field is NULL, then no data was captured for this record.
62
Qos Orig Local Average Inter-arrival Jitter
Numeric
0-999,999,999
MGCP DLCX ACK, DLCX
This is an estimate of the average statistical variance of the RTP data packet inter-arrival time measured in timestamp units and expressed as an unsigned integer by the originating endpoint. The inter-arrival jitter is defined as the mean deviation (smoothed absolute value) of the difference in packet spacing at the receiver compared to the sender for a pair of packets. This is equivalent to the difference between a packet's RTP timestamp and the receiver's clock at the time arrival. The value is calculated in terms of 125 microsend ticks and converted to milliseconds for storage in the CDR.
If this field is NULL, then no data was captured for this record.
63
QoS Orig Average Transmission Delay
Numeric
0-999,999,999
MGCP DLCX ACK, DLCX
The average network transmission delay as measured from the RTP interface of the originating endpoint. The boundaries of this interface include:
•
•
•
This is the Average Latency field from previous releases. A value of zero indicates that this calculation was not supported by the originating endpoint.
If this field is NULL, then no data was captured for this record.
64
QoS Term Local Packets Sent
Numeric
0-999,999,999
MGCP DLCX ACK, DLCX
The total number of RTP data packets transmitted by the terminating end point since transmission was started.
If this field is NULL, then no data was captured for this record.
65
QoS Term Packets received
Numeric
0-999,999,999
MGCP DLCX ACK, DLCX
The total number of RTP data packets received by the terminating end point since starting reception.
If this field is NULL, then no data was captured for this record.
66
QoS Term Local Octets Sent
Numeric
0-999,999,999
MGCP DLCX ACK, DLCX
The total number of payload octets transmitted in RTP data packets by the terminating endpoint since transmission was started. This count does not include headers or padding but can be used to estimate the average payload rate.
If this field is NULL, then no data was captured for this record.
67
QoS Term Octets Received
Numeric
0-999,999,999
MGCP DLCX ACK, DLCX
The total number of payload octets received in RTP data packets by the terminating endpoint since reception was started. This count does not include headers or padding but can be used to estimate the average payload rate.
If this field is NULL, then no data was captured for this record.
68
QoS Term Local Packets Lost
Numeric
0-999,999,999
MGCP DLCX ACK, DLCX
The total number of RTP data packets that have been lost since the beginning of reception by the terminating endpoint. This number is defined as the number of packets expected less the number of packets actually received, where the number of packets received includes any which are late or duplicates. The packets that arrive late are not counted as lost and the loss may be negative if there are duplicates. The number of packets expected is defined as the extended last sequence number received less the initial sequence number received.
If this field is NULL, then no data was captured for this record.
69
QoS Term Local Average Inter-arrival Jitter
Numeric
0-999,999,999
MGCP DLCX ACK, DLCX
This is an estimate of the average statistical variance of the RTP data packet inter-arrival time measured in timestamp units and expressed as an unsigned integer by the terminating endpoint. The inter-arrival jitter is defined as the mean deviation (smoothed absolute value) of the difference in packet spacing at the receiver compared to the sender for a pair of packets. This is equivalent to the difference between a packet's RTP timestamp and the receiver's clock at the time arrival. The value is calculated in terms of 125 microsend ticks and converted to milliseconds for storage in the CDR.
If this field is NULL, then no data was captured for this record.
70
QoS Term Average Transmission Delay
Numeric
0-999,999,999
MGCP DLCX ACK, DLCX
The average network transmission delay as measured from the RTP interface of the terminating endpoint. The boundaries of this interface include:
•
•
•
This is the Average Latency field from previous releases. A value of 0 (zero) indicates that this calculation was not supported by the originating endpoint.
If this field is NULL, then no data was captured for this record.
71
Operator Involvement
Numeric
0 = NO, 1 = YES
Dialed digits
Determines if operator is involved in the call for 0-, 0+, or 01+.
If this field is NULL, then no data was captured for this record.
72
Casual Dialing
Numeric
0 = NO, 1 = YES
Dialed digits
Determines whether it is a casual call (CIC) or PIC call.
If this field is NULL, then no data was captured for this record.
73
Connection Type
Numeric
0 = IP
1 = HAIRPIN
3 = ATM SVC
4 = ATM PVCDialed digits
Type of connection the gateway is making, so the reader of the record knows why the QoS parameters are different then expected. For example, if a Hairpin connection is used, then the QoS will be zeros.
This field currently only contains a value of 0 or 1. This field can be derived from either the Originating or Terminating endpoint. If it is returned from one of the endpoints, then that the value is presented in this field; if it is not returned by either endpoint, then this field contains a NULL. If the same value is returned by both endpoints, then the value from the originating endpoint is used. If this field contains a value of NULL, then no data was captured for this record.
74
Packet Time
Numeric
8 bit unsigned value
MGCP DLCX ACK
Packetization period for voice sampling. This field can be derived from either the Originating or Terminating endpoint. If it is returned from one of the endpoints, then the value is presented in this field. If it is not returned by either endpoint, then this field contains a NULL. If the same value is returned by both endpoints, then the value from the originating endpoint is used. If this field contains a value of NULL, then no data was captured for this record.
75
Silence Suppression
Numeric
0 = NO, 1 = YES
MGCP DLCX ACK
Indicates if silence suppression is enabled or not. This field can be derived from either the Originating or Terminating endpoint. If it is returned from one of the endpoints, then the value is presented in this field. If the same value is not returned by either endpoint, then this field contains a NULL. If a value is returned by both endpoints, then the value from the originating endpoint is used.
If this field is NULL, then no data was captured for this record.
76
Echo Cancellation
Numeric
0 = NO, 1 = YES
MGCP DLCX ACK
Indicates whether echo cancellation at far end is enabled or not.
This field can be derived from either the Originating or Terminating endpoint. If it is returned from one of the endpoints, then the value is presented in this field. If it is not returned by either endpoint, then this field contains a NULL. If the same value is returned by both endpoints, then the value from the originating endpoint is used.
If this field is NULL, then no data was captured for this record.
77
Codec Type
Numeric
1= PCMU G711
2 = PCMA G711
3 = G729A
4 = G729B
5 = G729E
6 = G729
7 = G726-40
8 = G726-32
9 = G726-24
10 = G726-16
11 = G728
12 = G723-H
13 = G723A-H
14 = G723-L
15 = G723A-L
16 = G723
MGCP DLCX ACK
Codec used to transport RTP traffic.
This field is produced internally by BTS 10200 and is the perception of the Codec used in the call.
If this field is a value of NULL, then no data was captured for this record.
78
Interstate Indicator
Numeric
0 = NO, 1 = YES
Destination::
Intrastate or LATA::Id
Indicates whether call crossed a state boundary or not.
If this field is NULL, then no data was captured for this record.
79
Record Type
Numeric
0 = NORMAL_
RECORD1 = FIRST_LONG_ DURN_RECORD
2 = CONTINUATION_
LONG_DURN_
RECORD3 = LAST_LONG_
DURN _RECORD4 = INVALID_RECORD
Dynamic run time data
Indicates whether record is involved in long duration call accounting or not.
If this field is NULL, then no data was captured for this record.
80
Timer Indicator
Numeric
32-bit unsigned value
0 (for normal call)
1, 2, 3, 4, 5,..(for long duration call)
Dynamic run time data
Indication of the sequence number of the long duration record. If the record is of a normal call, the value of this field is 0. For the long duration record, the value of this field indicates the sequence number. If this field contains a value of NULL, then no data was captured for this record.
81
Present Time
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
The time the continuation record was created. This field is only populated for long duration calls. If this field contains a value of NULL, then no data was captured for this record.
82
Overall Correlation Identifier
String
25
Alphanumeric characters
System generated.
This field is unique on a per call scenario basis, not on a per record basis. If a call scenario results in the Cisco BTS 10200 generating multiple call records, each record contains the same value in this field. The main use at this time is within the real time Event Message billing stream that is supported by the Cisco BTS 10200 for PacketCable compliancy and for correlation of multiple record call scenarios. This field should always be populated.
83
JIP
String
10
Alphanumeric characters
Pop::Jip or TrunkGroup::Jip or SS7 IAM
This field contains the Jurisdiction Information Parameter (JIP) of the originating switch for calls inbound to the Cisco BTS 10200. The JIP is populated with the value received in the Initial Address Message (SS7) (IAM) if available, or the value provisioned into the Trunk Group table of the inbound trunk group for the call. If the JIP is not provisioned in the Trunk Group table and not received in the IAM, then the field contains a NULL.
84
Originating CLLI
String
11
Alphanumeric characters
TrunkGroup::Clli
The CLLI of the switch the call originated from. The CLLI is provisioned in the trunk group that was used to deliver the call to the Cisco BTS 10200.
If this field is NULL, then no data was captured for this record.
85
Terminating CLLI
String
11
Alphanumeric characters
TrunkGroup::Clli
The CLLI of the switch the call was terminated to. The CLLI is provisioned in the trunk group that was used to deliver the call to the terminating switch. If this field is NULL, then no data was captured for this record.
86
Call Agent Id
String
8
Alphanumeric characters
CallAgent::Id
Identifies the Call Agent on which Call Detail Block (CDB) is created. If this field is NULL, then no data was captured for this record.
87
Originating POP Time Zone
Numeric
Refer to Appendix B, "Time Zone Mapping Table" for the potential values.
Pop::Timezone, Timezone::Id
This is the point of presence time zone of the originating Point Of Presence (POP). This field provides information on the locale of which the POP is a member. This information can also be leveraged for partitioning subscribers on a single BTS 10200 into multiple business entities for billing purposes.
A zero value (0) indicates LOCAL BTS 10200 time zone.
A NULL indicates no value captured for this field.
88
Service Usage Sensitive 1
Numeric
0 = FALSE, 1 = TRUE
This field is applicable only if Service Type 1 field is populated.
Internal FCP message sent from the feature server to call processing.
Indication of whether first service usage within the call context was usage sensitive or not.
If this field is NULL, then no data was captured for this record.
89
Service Usage Sensitive 2
Numeric
0 = FALSE, 1 = TRUE
This field is applicable only if Service Type 2 field is populated.
Internal FCP message sent from the feature server to call processing.
Indication of whether second service usage within the call context was usage sensitive or not.
If this field is NULL, then no data was captured for this record.
90
Service Usage Sensitive 3
Numeric
0 = FALSE, 1 = TRUE
This field is applicable only if Service Type 3 field is populated.
Internal FCP message sent from the feature server to call processing.
Indication of whether third service usage within the call context was usage sensitive or not.
If this field is NULL, then no data was captured for this record.
91
Originating H323 Call Origin
Numeric
0 = NULL
1 = ANSWER
2 = ORIGINATE
Various H.323 messages
ANSWER indicates call terminated on reporting gateway.
ORIGINATE indicates call was outbound from reporting gateway for originating half of call.
This field is populated only for calls over an H.323 network. If this field is a value of NULL, no data was captured for this record.
92
Originating H323 Call Type
Numeric
1 = VOIP
2 = TELEPHONY
3 = VIDEO
Bearer Capability field of incoming SETUP messages and the VIDEO_SUPP field in the H323-TG-PROFILE and H323-TERM-
PROFILE tablesValue indicates protocol family used on originating leg of the call.
This field is populated only for calls over an H.323 network. If this field is a value of NULL, no data was captured for this record.
93
Originating H323 Conference Id
String
32
Alphanumeric characters
Various H.323 messages
Unique identifier generated by originating Public Switched Telephone Network (PSTN) gateway for each unique call scenario within a given call context.
This field is populated only for calls over an H.323 network. If this field is NULL, no data was captured for this record.
94
Originating H323 Remote Address
String
16
Alphanumeric characters
Various H.323 messages
IP address of originating remote gateway.
This field is populated only for calls over an H.323 network. If this field is NULL, no data was captured for this record.
95
Originating H323 Time Day
Numeric
128-bit unsigned value in total 64-bit seconds and 64-bit milliseconds in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:000h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock
Time of day terminating number was dialed for originating half of call.
This field is populated only for calls over an H.323 network.
96
Originating H323 Voice Quality
Numeric
This field is not populated for this release
Various H.323 messages
Quality of voice connection for originating side of call. This is a decimal number from the ICPIF table of G.113.
97
Originating H323 Subscriber
Numeric
This field is not populated for this release
Various H.323 messages
Subscriber T1/CAS signaling information from originating side of call.
98
Originating H323 Gateway Id
String
16
Alphanumeric characters
Various H.323 messages
For incoming calls from an H.323 network, this field will contain the h323-id of the originating (peer) H.323 gateway/endpoint. If this parameter is not available in the incoming H.323 call, the Cisco BTS 10200 will populate this field with local h323-id from the H.323-GW that received the call. For incoming calls from non-H.323 networks, this field is NULL.
This field is only populated for calls over an H.323 network. If this field is NULL, no data was captured for this record.
99
Originating H323 Gatekeeper Id
String
16
Alphanumeric characters
Various H.323 messages
The hostname of the originating primary gatekeeper for the call.
This field is only populated for calls over an H.323 network. If this field is NULL, no data was captured for this record.
100
Terminating H323 Call Origin
Numeric
0 = NULL
1 = ANSWER
2 = ORIGINATEVarious H.323 messages
ANSWER indicates the call terminated on the reporting gateway.
ORIGINATE indicates the call was outbound from the reporting gateway for the terminating half of the call.
This field is only populated for calls over an H.323 network. If this field is a value of NULL, no data was captured for this record.
101
Terminating H323 Call Type
Numeric
1 = VOIP
2 = TELEPHONY3 = VIDEO
Bearer Capability field of incoming SETUP messages and the VIDEO_SUPP field in the H323-TG-PROFILE and H323-TERM-PROFILE tables.
Indication of the protocol family used on the terminating leg of the call.
This field is only populated for calls over an H.323 network. If this field is a value of NULL, no data was captured for this record
102
Terminating H323 Conference Id
String
32
Alphanumeric characters
Various H.323 messages
A unique identifier generated by the terminating PSTN gateway for each unique call scenario within a given call context.
This field is only populated for calls over an H.323 network. If this field is NULL, no data was captured for this record.
103
Terminating H323 Remote Address <
