Billing Guide, Release 6.0.3

Operator Call Type in Field 1

Call Detail Block File Fields

Revised: August 10, 2011, OL-24995-01

The 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 ";"

•vertical bar "|"

•linefeed

•comma ","

•caret "^".

Note The same character (value) cannot be used as both a field delimiter and a record delimiter. Different delimiters must be used to separate fields within a record and records within a file.

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

Once the delimiters are changed and the BDMSs are restarted, any billing files created with different delimiters are inaccessible by the billing query command. An example of an actual call detail block FTP file containing one CDB is shown in Chapter 2 "Example of a Call Detail Block File."
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
Field Number	Common Name	Field Type	Field Size*	Potential Values	Data Source	Field Description
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.1, 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. MGCP DLCX receipt. 2. Transmission/receipt of an RLC. 3. Transmission/receipt of last signaling message to/from a peer CMS/MGC.
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_ WAITING 4 = REPEAT_ CALL 5 = RETURN_ CALL	Internal 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.
29	Service Type 1	Numeric		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 SINGLE_NUMBER_REACH = 84 LONG_DUR_CUTOFF = 85 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 = FAILURE	Internal 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 Returned Data1	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. NOTE: When there is no RN in ENUM LNP response, then LRN should be treated as the original dialed DN. 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 = YES	SS7 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 = YES	n/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.3.	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_ DIALED 1 = AUTO_ IDENTIFIED_ OPERATOR_ DIALED 2 = OPER_ DENTIFIED_ CUSTOMER_ DIALED 3 = OPER_ IDENTIFIED_ OPERATOR_ DIALED		Operator action with respect to the originating party: •automatically identified— customer dialed (0) or operator dialed (1) or •operator identified— customer dialed (2) or operator dialed (3) If this field is NULL, then no data was captured for this record.
45	Originating 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.
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	1. SS7 EXM 2. Outgoing SIP INVITE message with Req-URI containing the tgrp user parameter.	1. 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. 2. Represents the tgrp value that is sent in the outgoing invite, when TGRP routing takes place.
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 indicator	Numeric		0 = CIC_FGD_OPERATOR_ INVOLVED 1 = CIC_FGD_OPERATOR_ NOT_INVOLVED 2 = CIC_FGD_OPERATOR_ INVOLVED_UNKNOWN 7 = 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. Operator involvement 2. Dialed direct with no operator. 3. With undetermined operator involvement, or unknown CIC with : –Operator involvement –Dialed direct with no operator, or –Undetermined operator involvement 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 Indicator	Numeric		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 Indicator	Numeric		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 values of 0 and 1 are supported. Values 2, 3, and 4 are reserved for future use. In general, the rule for setting the routing indicator is: •if carrier-id field in trunk-grp is NOT NULL, then the call is set as direct interconnect (ROUTING_INDICATOR _DIRECT 0) •if carrier-id field in trunk-grp is NULL, then the call is set as a non- direct interconnect (ROUTING_INDICATOR _TANDEM 1)
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: •multiplexing/demultiplexing multiple RTP packets into or out of a single UDP packet •all subsequent handling of transmission and reception of UDP frames •network delays and peer processing up to the peer's RTP interface. 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: •Multiplexing/demultiplexing multiple RTP packets into or out of a single UDP packet •All subsequent handling of transmission and reception of UDP frames •Network delays and peer processing up to the peer's RTP interface 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 PVC	Dialed 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		16 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_ RECORD 1 = FIRST_LONG_ DURN_RECORD 2 = CONTINUATION_ LONG_DURN_ RECORD 3 = LAST_LONG_ DURN _RECORD 4 = 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 "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 tables	Value 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 = ORIGINATE	Various 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 = TELEPHONY 3 = 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	String	16	Alphanumeric characters	Various H.323 messages	The IP address of the terminating remote gateway. This field is only populated for calls over an H.323 network. If this field is NULL, no data was captured for this record.
104	Terminating 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	The time of day that the terminating number was dialed for the terminating half of the call. This field is populated only for calls over an H.323 network.
105	Terminating H323 Voice Quality	Numeric		This field is not populated for this release	Various H.323 messages	The quality of voice connection for the terminating side of the call. This is a decimal number from the ICPIF table of G.113. If this field is a value of NULL, no data was captured for record.
106	Terminating H323 Subscriber	Numeric		This field is not populated for this release.	Various H.323 messages	Subscriber T1/CAS signaling information from terminating side of call. If this field is a value of NULL, no data was captured for this record.
107	Terminating H323 Gateway Id	String	16	Alphanumeric characters	Various H.323 messages	For outgoing calls from Cisco BTS 10200 and terminating to an H.323 network, this field will contain h323-Id of the terminating (peer) H.323 gateway/endpoint if available in backward Call signaling message. If this parameter is not available from terminating H.323 Gateway/endpoint, Cisco BTS 10200 will populate the local h323-id from H323-GW, which is used to send out the call. For outgoing calls to non H.323 network, this field is NULL. This field is populated only for calls over an H.323 network. If this field is NULL, no data was captured for this record.
108	Terminating H323 Gatekeeper Id	String	16	Alphanumeric characters	Various H.323 messages	The symbolic host name assigned to the terminating primary gatekeeper for the call. This field is populated only for calls over an H.323 network. If this field is NULL, no data was captured for this record.
109	Orig Type	Numeric		0 = INTRASWITCH 1 = INTERSWITCH	Dialed digits	Indicates whether call was originated by a subscriber homed on the reporting BTS 10200. If a MAIN-SUB-ID is provisioned on the inbound TG, this field is set to ON-NET. If the MAIN-SUB-ID is NULL on the inbound TG, this field is set to OFF-NET. A MAIN-SUB-ID is typically associated with a trunk group from a PBX, voicemail server, or another local application server.
110	Term Type	Numeric		0 = INTRASWITCH 1 = INTERSWITCH	Dialed digits	Indication of whether call was terminated by subscriber homed on the reporting BTS 10200.
111	Source Service Provider Id	String	16	Alphanumeric characters	TrunkGroup::Spid or Carrier::Spid or TechPrefix::Spid	This field contains the network provided or Service Provider Identifier configured for incoming calls to the Cisco BTS 10200. For incoming calls from the PSTN network, this field contains the service provider ID value after it finds the matching entry in the CARRIER table for the TNS/CIP parameter against the Carrier ID. For incoming calls from an H.323 network, this field contains the value in the field circuitInfo.destinationCircuitId (H323v4) or the Service Provider ID derived from tech-prefix received in the SETUP message. When this parameter does not exist in the SETUP message, the service provider ID configured for the incoming trunk group is used to populate this field. When source based routing is enabled, the Cisco BTS 10200 selects the trunk group based on the source IP address and circuitInfo.sourceCircuitId field from the SETUP message received. When the circuitInfo.destinationCircuitId does not match the service provider ID configured on the incoming trunk group, the call is routed using the default route. If this field is NULL, then no data was captured for this record.
112	Destination Service Provider Id	String	16	Alphanumeric characters	TrunkGroup::Spid or Carrier::Spid or TechPrefix::Spid	This field contains the identifier of the destination service provider which is used to route the call. For outgoing calls to an H.323 network, this field is populated with destinationCarrierId from the Intra Zone Clear Token (IZCT) parameter of the ACF message returned by the outgoing Gatekeeper. If this value is not received from the Gatekeeper, the value provisioned in the service provider ID of the outgoing trunk group is used. For outgoing calls to the Public Switched Telephone Network (PSTN) network, this field is populated with a value of the service provider ID provisioned in the outgoing trunk group. If this field is NULL, then no data was captured for this record.
113	Source Carrier Id	String	4	Numeric characters	TrunkGroup:: CarrierId or SS7 IAM	This field contains a 4-digit value from the Transit Network Selection (TNS) or Carrier Identification code Parameter (CIP) parameter of the IAM/SETUP message received from the PSTN network. If TNS or CIP is not received, this field is populated with the Carrier ID field provisioned in the incoming trunk group. This field is only applicable to tandem call scenarios. If this field is NULL, then no data was captured for this record.
114	Destination Carrier Id	String	4	Numeric characters	TrunkGroup:: CarrierId or SS7 IAM	This field contains the 4-digit carrier ID of the outgoing trunk group used to route the call. For calls routed to the PSTN network, this field contains the value provisioned in the Carrier ID field of the trunk group table. If this field is NULL, then no data was captured for this record.
115	Originating SIP Username	String	64	Alphanumeric characters	Originating SIP INVITE message	The username value of the From field on the originating side for all incoming SIP calls. This field is populated only for SIP calls. The value for the field is specified between the ":" and "@" characters. If this field is NULL, no data is captured for this record.
116	Originating SIP Call Id	String	64	Alphanumeric characters	Originating SIP INVITE message	SIP Call Id header field. This field is a truncation of SIP Call Id header field received through SIP if it is over 64 characters in length. This value for this field appears after the ":". This field is populated only for SIP calls. If this field is NULL, no data was captured for this record.
117	Originating SIP Adjacent Hop Address	String	16	Alphanumeric characters	Originating SIP INVITE message	IP address of last proxy that forwarded calls inbound to BTS 10200. IP address of proxy to which outbound calls from the Cisco BTS 10200 are forwarded. This field is only populated for SIP calls. If this field is NULL, no data was captured for this record.
118	Database Query Time 2	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, then the timestamp is ignored.	Dynamic run time data from the system clock	The time at which second database query response was received for this call. If the value is NULL, timestamp is ignored.
119	Database Query Result Code 2	Numeric		1 = SUCCESS 2 = FAILURE	Internal FCP message sent from the feature server to call processing	Indicates disposition of the second database query for call. If this field has a value of NULL, no data was captured for this record.
120	Database Query Type2	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	Indicates specific type of 800 or LNP query performed on second database query for call. If this field is a value of NULL, no data was captured for this record.
121	Database Query Returned Data 2	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	The directory number, RN, and/or NAME returned from the second database query for the call. If field is NULL, no data was captured for this record. NOTE: When there is no RN in ENUM LNP response, then LRN should be treated as the original dialed DN. Caveat: If this field is found to contain a character coinciding 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.
122	Database Query Time 3	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, then the timestamp is ignored.	Dynamic run time data from the system clock	The time the third database query response was received for this call.
123	Database Query Result Code 3	Numeric		1 = SUCCESS 2 = FAILURE	Internal FCP message sent from the feature server to call processing	Indicates disposition of third database query for call. If this field has a value of NULL, no data was captured for this record.
124	Database Query Type 3	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	Indicates specific type of 800 or LNP query performed on the third database query for the call. If this field has a value of NULL, no data was captured for this record.
125	Database Query Returned Data 3	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 third database query for call. If this field is NULL, 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.
126	Service Result Code1	Numeric		1 = SUCCESS 2 = FAILURE 3 = ANI INVALID 4 = ANI BLOCKED 5 = CASUAL CALLS NOT ALLOWED 6 = II SCREENING REJECT 7 = BW SCREENING REJECT 8 = COS RESTRICTED 9 = 2L-ACT ABANDONED VOICE BACK DN 10 = 2l_ACT CONNECTED ANONYMOUS DN 11 = COS INTERNAL ERROR 12 = CALL BLOCKED 13 = RESULT UNKNOWN 14 = USER ABANDONED 15 = INVALID PIN 16 = PIN BLOCKED 17 = TEMP DISC BLOCKED 18 = VALID	Internal FCP message sent from the feature server to call processing	Indicates disposition of first service activation, service deactivation, or service instance within the call context. This field is applicable only if the Service Type 1 field is populated. If this field has a value of NULL, no data was captured for this record.
126 (continued)	Service Result Code1	Numeric		19 = ABANDON WHILE ANNOUNCE 20 = INSUFFICIENT QUOTA 21 = MEDIATION REQUIRED 22=Billing Info Season Suspend Call Blocked
127	Service Result Code2	Numeric		(Same as Service Result Code 1)	Internal FCP message sent from the feature server to call processing	Indicates disposition of second service activation, service deactivation, or service instance within the call context. This field is applicable only if the Service Type 2 field is populated. If this field has a value of NULL, no data was captured for this record
128	Service Result Code3	Numeric		(Same as Service Result Code 1)	Internal FCP message sent from the feature server to call processing	Indicates disposition of third service activation, service deactivation, or service instance within the call context. This field is applicable only if the Service Type 3 field is populated. If this field has a value of NULL, no data was captured for this record
129	NAS Error Code	Numeric		800 = ISP PORT LIMIT OVERRUN 801 = NO MODEMS AVAILABLE 802 = CALLING NUMBER UNACCEPTABLE 803 = CALLED NUMBER UNACCEPTABLE	Internally generated by call processing	Specific error code explaining reason that this NAS call could not be completed. If this field has a value of NULL, no data was captured for this record.
130	NAS DLCX Reason	Numeric		801 = USER REQUEST 802 = LOST CARRIER 803 = LOST SERVICE 804 = IDLE TIMEOUT 805 = SESSION TIMEOUT 806 = ADMIN RESET 807 = ADMIN REBOOT 808 = PORT ERROR 809 = NAS ERROR 810 = NAS REQUEST 811 = NAS REBOOT 812 = PORT UN-NEEDED 813 = PORT PRE-EMPTED 814 = PORT SUSPENDED 815 = SERVICE UNAVAILABLE 816 = CALLBACK 817 = USER ERROR 818 = HOST REQUEST	MGCP DLCX	Reason code returned in the DLCX message for NAS calls. If this field has a value of NULL, no data was captured for this record.
131	NAS Pre-Authorization Result	Numeric		0 = NULL 1 = AU —EVERYTHING IS OK 2 = AX—CGN/CDN NUMBERS ARE NOT GOOD 3 = OF—MODEM FAILURE	MGCP NTFY	Indicates result of performing pre-authorization on a NAS-based call. If this field has a value of NULL, no data was captured for this record.
132	Fax Indicator	Numeric		0 = VOICE ONLY 1 = VOICE AND FAX	Internally generated by call processing	Indicates whether the call involved any fax transmissions. This field contains a 0 if operation is in an mgw-to-mgw controlled mode. When a fax is sent under mgw control but no indication of the fax transmission is sent to the call agent, then this field is set to 0 (zero). If this field contains a value of NULL, then no data was captured for this record.
133	Fax Pages Sent	Numeric		Value provided by fax component	MGCP DLCX ACK, DLCX	The number of fax pages that were sent during this call. If the Fax Indicator field is set to NULL, then this field is ignored. This field is only populated by the Cisco BTS 10200 for calls that use the MGCP, NCS or TGCP interface.
134	Fax Pages Received	Numeric		Value provided by fax component	MGCP DLCX ACK, DLCX	The number of fax pages that were received during this call. If the Fax Indicator field is set to NULL, then field is ignored. This field is only populated by the Cisco BTS 10200 for calls that use the MGCP, NCS or TGCP interface.
135	Service Interrogation Time 1	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 interrogation of Service Type 1 occurred. This field is only used when the Service Interrogation capabilities of various features are deployed. Typically these are only supported in Asia-Pacific regions.
136	Service Interrogation Time 2	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 interrogation of Service Type 2 occurred. This field is only used when the Service Interrogation capabilities of various features are deployed. Typically these are only supported in Asia-Pacific regions.
137	Service Interrogation Time 3	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 interrogation of Service Type 3 occurred. This field is only used when the Service Interrogation capabilities of various features are deployed. Typically these are only supported in Asia-Pacific regions.
138	Originating Pop Id	String	16	Alphanumeric characters	SubscriberProfile:: PopId	This is the point of presence that the originating subscriber on the BTS 10200 is provisioned into. This field provides information on the locale where the subscriber is a member. For LINE type termination, the pop index is populated from the calling party's subscriber profile pop id. For TRUNK_CLASS termination, the pop index is populated from the trunk-group pop index. This information can also be leveraged for partitioning subscribers on a single BTS 10200 into multiple business entities for billing purposes. If this field is NULL, no data was captured for this record.
139	Terminating Pop Id	String	16	Alphanumeric characters	SubscriberProfile:: PopId	This is the point of presence that the terminating subscriber on the BTS 10200 is provisioned into. This field provides information on the locale where the subscriber is a member. For LINE type termination, the pop index is populated from the called party's subscriber profile pop id. For TRUNK_CLASS termination, the pop index is populated from the trunk-group attached pop index. This information can also be leveraged for partitioning subscribers on a single BTS 10200 into multiple business entities for billing purposes. If this field is NULL, no data was captured for this record.
140	Terminating POP Time Zone	Numeric		Refer to "Time Zone Mapping Table" for the potential values.	Pop::Timezone, Timezone::Id	This is the point of presence time zone that the terminating POP is provisioned into. This field provides information on the locale where the terminating 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. If this field contains a value of ZERO, then the timestamps within this record are based on the local time zone. A NULL indicates no value captured for this field.
141	Dial Plan Id	String	16	Alphanumeric characters	SubscriberProfile:: DialPlanId	Dial plan used for call routing purposes by originating subscriber on Cisco BTS 10200. The dial plan defines valid digit patterns for the subscriber in addition to routing based on the dialed digits. If this field is NULL, no data was captured for this record.
142	GTD Global Call Indicator	String	32	Alphanumeric characters including hyphens.	If incoming GTD contains GCI, the GCI is used; otherwise, the Cisco BTS 10200 internally generates a GCI.	GTD Global Call Identification field populated only for H.323 calls with GTD enabled. The Cisco BTS 10200 will use the GCI format consistent with the IOS GTD implementation, which is in the form of a 16-character ASCII representation of a UTC timestamp followed by a 4-character ASCII representation of the clock sequence, plus a 12-character ASCII representation of the MAC address This field is always 32 characters long. If this field is NULL, no data was captured for this record.
143	Terminating SIP Username	String	64	Alphanumeric characters.	Incoming 18x or 200 SIP message to outgoing (outbound) initial SIP INVITE message.	The username value of the From field on the terminating side for all outgoing SIP calls. This field is populated only for SIP calls. The value for the field is specified between the ":" and "@" characters. If this field is NULL, no data was captured for this record.
144	Terminating SIP Call Id	String	64	Alphanumeric characters.	Incoming 18x or 200 SIP message to outgoing (outbound) initial SIP INVITE message.	The SIP Call ID header field. This field is a truncation of the SIP Call ID header field received through SIP if it is over 64 characters in length. This field is populated only for outgoing SIP calls. If this field is NULL, no data was captured for this record.
145	Terminating SIP Adjacent Hop Address	String	16	Alphanumeric characters	Incoming 18x or 200 SIP message to outgoing (outbound) initial SIP INVITE message.	The IP address of the proxy or SIP User Agent that the call is sent to for calls outbound from the Cisco BTS 10200. This field is only populated for outgoing SIP calls. The value for the field after "." If this field is NULL, then no data was captured for this record.
146	Originating SIP Type	Numeric		1 = SUBSCRIBER 2 = SIP 3 = SIP-T 4 = CMSS	Combination of Incoming initial SIP INVITE message and provisioning (TrunkGroup, TrunkGroupProfile, Subscriber).	The type of SIP call on the inbound side. This field is only populated for SIP originations. If this field has a value of NULL, no data was captured for this record.
147	Terminating SIP Call Type	Numeric		1 = SUBSCRIBER 2 = SIP 3 = SIP-T 4 = CMSS	Based on dynamic data; the outbound SIP call type is based on routing.	The type of SIP call on the outbound side. This field is only populated for SIP terminations. If this field has a value of NULL, no data was captured for this record.
148	Originating H.323 Network Provider Id	String	16	Alphanumeric characters.	H.323 ACF	This field contains the value contained in the IZCT source zone parameter of the ACF message for the outgoing call leg. If this field is NULL, then no data was captured for this record.
149	Destination H.323 Network Provider Id	String	16	Alphanumeric characters.	H.323 ACF	This field contains the identifier of the destination service provider which is used by external route servers to route the call to the final destination. This field is only applicable for outgoing calls to an H.323 network. This field contains the IntermediateCarrierId field from the IZCT parameter of the ACF message received from the outgoing Gatekeeper. If this field is NULL, then no data was captured for this record.
150	Video Codec	Numeric		0 = None (future) 1 = H.261 (future) 2 = H.263 (future) 3 = H.264 (future)	n/a	The codec used to transport the RTP traffic. The value in this field is pulled from the provisioning of the BTS 10200, not from the actual SDP message. This field is always 0 (zero) in this release.
151	Original Originating Number	String	64	DIGITS	SETUP Message	This field contains the calling number received in the SETUP Message after digit manipulation is performed but before any overriding occurs, such as overwriting with a billing DN. If this field is NULL, then no data was captured for this field.
152	Calling Party Category	Numeric		0 = Unknown 9 = National Operator 10 = Ordinary Subscriber 11 = Subscriber w/Priority 12 = Voice Band Data 13 = Test Call 15 = Pay Phone 246 = Translated Number 249 = Line Test Desk 250 = Interception Operator 251 = Immediate Charge Info	SS7 IAM message.	The Calling Party Category value that was received in the SS7 IAM. If this field is NULL, then no data was captured for this record.
153	Called Party Category Indicator	Numeric		0 = No Indication 1 = Ordinary Subscriber 2 = Payphone	SS7 BCI field.	The Called Party Category Indicator value is derived from the FE bits of the Backward Call Indicator received through SS7. If this field is NULL, then no data was captured for this record.
154	Called Party Ported In Indicator	Numeric		0 = No 1 = Yes	Subscriber:: Ported-In	Indication of whether or not the Called Number (for terminating records) is ported into the reporting Cisco BTS 10200. If this field is NULL, then no data was captured for this record.
155	Calling Party Ported In Indicator	Numeric		0 = No 1 = Yes	Subscriber:: Ported-In	Indication of whether or not the Called Number (for terminating records) is ported into the reporting Cisco BTS 10200. If this field is NULL, then no data was captured for this record.
156	Billing Rate Indicator	Numeric		1 = Flat Rate 1 2 = Flat Rate 2 3 = Measured Rate 1 4 = Measured Rate 2	Subscriber:: Billing-Type	The type of SIP call on the inbound side. This field is only populated for SIP originations. If this field contains a value of NULL, then no data was captured for this record.
157	Account Id	String	20	Alphanumeric characters.	Subscriber:: Account	The account ID that the subscriber is associated with. If this field is NULL, then no data was captured for this record. It will always contain NULL in this release.
158	Originating End Point TSAP Address	String	64	DNS or IP Address	Mgw::TSAP- Address or TrunkGroup:: Softsw-TSAP- Address or H323-Term::TSAP-Address	The IP address or DNS for the originating endpoint. For an on-net call, this is the TSAP Address of the IAD, SIP phone, ATA, or MTA. This address is indicative of the signaling address for the originating endpoint, which can be different from the bearer (RTP) address. For an off-net call, this is the IP address of the trunking gateway. This information is useful for generating usage reports on a per gateway basis or in troubleshooting errors encountered during a call. If this field is NULL, then no data was captured for this record.
159	Terminating End Point TSAP Address	String	64	DNS or IP Address	Mgw::TSAP- Address or TrunkGroup:: Softsw-TSAP- Address or H323-Term::TSAP-Address	The IP address or DNS for the originating endpoint. For an on-net call, this is the TSAP Address of the IAD, SIP phone, ATA, or MTA. This address is indicative of the signaling address for the originating endpoint - which can be different from the bearer (RTP) address. For an off-net call, this is the IP address of the trunking gateway. This information is useful for generating usage reports on a per gateway basis or in troubleshooting errors encountered during a call. If this field is NULL, then no data was captured for this record.
160	Originating CMTS Id	String	64	Alphanumeric characters.	Aggregation::TSAP-Address	The IP address or DNS of the aggregation router on the originating side of the call for on-net originators. If this field is NULL, then no data was captured for this record.
161	Terminating CMTS Id	String	64	Alphanumeric characters.	Aggregation::TSAP-Address	The IP address or DNS of the aggregation router on the terminating side of the call for on-net originators. If this field is NULL, then no data was captured for this record.
162	Originating Fiber Node Id	String	20	Alphanumeric characters.	Mgw::Fiber-Node	The name of the fiber node that the originating MTA is assigned to. An HCF fiber node sits between the CMTS and MTA with each MTA assigned to a particular fiber node. One or more fiber nodes are assigned to a given CMTS. If this field is NULL, then no data was captured for this record.
163	Terminating Fiber Node Id	String	20	Alphanumeric characters.	Mgw::Fiber-Node	The name of the fiber node that the terminating MTA is assigned to. An HCF fiber node sits between the CMTS and MTA with each MTA assigned to a particular fiber node. One or more fiber nodes are assigned to a given CMTS. If this field is NULL, then no data was captured for this record.
164	Call Subtype	Numeric		TEST-CALL subtypes: NONE = 0 NCT_LINE_TEST = 15 NCT_TRUNK_ TEST = 16 NLB_LINE_TEST = 17 NLB_TRUNK_ TEST = 18 TEST_ROUTE = 19 EMG subtypes: AMBULANCE = 2 FIRE = 6 POLICE = 9 INFO subtypes: AIRLINES = 1 ANALOG = 3 DIGITAL = 4 DYNAMIC = 5 LB_TEST = 7 NLB_TEST = 8 RAILWAYS = 10 TIME = 11	Destination:: CallSubtype	This field further defines the call based on the Call-Type field. In this release, only CallType=TEST-CALL, EMG, or INFO causes this field to be populated. If this field contains a NULL, then it should be ignored. NCT-LINE-TEST is a Network Continuity Test call on a subscriber line. The calling party number format is <test-prefix><DN> NCT-TRUNK-TEST is a Network Continuity Test call on a trunking endpoint. The calling party number format is <test-prefix><TG><TM>. The number of digits in the trunk group number and trunk member number is determined based on test-trunk- grp-digits and test-trunk-member- digits value set in the Call Agent Configuration table. NLB-LINE-TEST is a Network Loopback Test call using a network loop connection on the terminating endpoint. The calling party number format is <test-prefix><DN>.
	Call Subtype	Numeric		TRAFFIC = 12 TW(Time&Weather) =13 WEATHER = 14		LB-TRUNK-TEST is a Network Loopback Test call on a trunking endpoint. The calling party number is in the format <test-prefix><TG><TM>. The number of digits in the trunk group number and trunk member number is determined based on test-trunk-grp-digits and test-trunk-member- digits values set in the Call Agent Configuration table. TEST-ROUTE routes the test call based on <DN>. The calling party number is in the format <test-prefix><TG><TM>. The number of digits in the trunk group number and trunk member number is determined based on test-trunk-grp-digits and test-trunk-member-digits values set in the Call Agent Configuration table.
165	Sensor Id	String	6	Numeric characters.	Pop::SensorId	The field contains 6 numeric characters defined in the POP Table Sensor ID field. The first character contains a value of 0 if the record was not previously output to a downstream system (primary data), a 1 if the record was previously output (secondary data), or a 2 if the record was output but not confirmed. The 2nd through 6th characters contain a 6 digit identification code assigned by the service provider of the sensor that generated or formatted the billing record. The values can range from 000000 to 999998. 999999 is reserved for sensors that output only AMA test tapes. The POP table contains the 6 characters that represent the actual Sensor ID; the Cisco BTS 10200 does not support the 1st character as stated in GR-1100. The sensor ID is chosen based on the following factors: •Offnet to Onnet call: Use the POP index for the originating party (incoming trunk group's POP). •Onnet to Offnet call: Use the POP index for the originating subscriber on that Cisco BTS 10200 (subscriber's associated POP). •Onnet to Onnet call (same POP on same Cisco BTS 10200): Use the POP index for the originating subscriber.
165	Sensor Id	String				•Onnet to Onnet call (different POPs on same Cisco BTS 10200): Use the POP index for the originating subscriber. •Onnet to Onnet call (different Cisco BTS 10200s): Use the POP index for the originating subscriber homed on the reporting Cisco BTS 10200. If this field is NULL, no data was captured for this record.
166	Originating International Indicator	Numeric		1 = No 2 = Yes (call is international in origin)	Signaling parameters	This field indicates if the call terminating to this Cisco BTS 10200 originated internationally. NO indicates the call is domestic in origin. This field is only populated for incoming SS7 calls. A value of NULL indicates that information was not gathered for this field. This field indicates if the call terminating to this Cisco BTS 10200 was originated internationally or not. A value of NO indicates the call was domestic in origin. This field is only populated for incoming SS7 calls. A value of NULL indicates that information was not gathered for this field.
167	Originating Calling Name	String	15	Null character, "PRIVATE," "OUT OF AREA," "Name string returned from CNAM query"	CNAM Query	The calling name for the originating party of this call terminating on the Cisco BTS 10200 as returned from the CNAM database query. The strings for PRIVATE and OUT OF AREA are mapped internally in the Cisco BTS 10200 and presented in a format compliant with GR-1188 in this field. If this field is NULL, then no data was captured for this record.
168	Originating Privacy Indicator	Numeric		1 = NONE, 2 = NAME 3 = FULL	Signaling parameters	The privacy indicator for the originating party of this call on the Cisco BTS 10200. The field is used for both originating and terminating calls. The field is derived from the appropriate signaling fields as the call terminates to this Cisco BTS 10200. A value of NONE indicates that both calling name and number are displayed—there is no restriction; a value of NAME indicates just the calling number is displayed (name privacy is active); and a value of FULL indicates neither the number nor the name is displayed to the terminating subscriber (full privacy) on the Cisco BTS 10200. This is only applicable to subscribers on the Cisco BTS 10200 that have calling name and/or calling number as a feature, assigned to them. If this field is NULL, then no data was captured for this record.
169	Originating Called Party Ported NoA	Numeric		1 = Concatenated RN with DN 2 = Separate RN		For an incoming trunk call, if the received Called Party Number has a Nature of Address (NoA) indicating ported number, then one of the following values is provided. Otherwise, the value is NULL. These fields are only applicable for ITU-based Local Number Portability (LNP) when LNP Profile LNP-DB-TYPE=RN. Values: •WITH RN—Indicates the digits are a Routing Number (RN), or concatenated RN + DN, depending on country specific requirements. •WITHOUT RN—Indicates the digits are for a ported DN, but with no RN present.
170	Terminating Called Party Ported NoA	Numeric		1 = Concatenated RN with DN 2 = Separate RN		For a call terminating to a Cisco BTS 10200 subscriber, or outgoing trunk call, when LNP Profile LNP-DB-TYPE=RN and the final called party number (after digit translation and manipulation) nature of address indicates ported number, then this field is present and is set to one of the values shown above for Originating Called Party Ported NoA. If this field is NULL, then no data was captured for this record.
171	Charging Information	Numeric		Number of metered or pulsed charge units or Charge Band number. This is a dual purpose field.	ISUP ITX messages	The number of metered or pulsed billing units recorded for this call. This is initially only used in conjunction with French and Polish ISUP. No value is recorded in this field for calls that are transiting the BTS 10200. The BTS 10200 acts as a CGP node based on the AOC Enabled property associated with the outgoing trunk groups. The property's "enabled" or "disabled" status determines whether the received CRG message in the backward direction should be validated. If this field is NULL, then no data was captured for this record.
172 (Cisco BTS 10200 Release 4.5.1, MR1 only)	Originating Line Information	Numeric		0-99	Subscriber Profile::Oli SS7 IAM message	The Originating Line Information value is received in the SS7 IAM. For subscriber originated calls, the OLI specified in the subscriber-profile record is put into the billing record.
173	Centrex Group	String	16	A group name of up to 16 characters.	Subscriber:CtxgId	Identity of the Centrex group that this call is associated with. If this field is NULL, then no data was captured for this record.
174	Country Code	String	3	Numeric Characters	Intl_dial_plan:Padded_cc	Three numeric characters Automatically generated by EMS is not provisioned: •If 1 digit cc, pad cc with 2 zeros (2 becomes 002) •If 2 digit cc, pad cc with 1 zero (44 becomes 044). •If 3 digit cc, no padding required, copy as is. •If cc > 3 digits, copy the 1st 3 digits here.
175	Feature Data Two 1	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 second datum of feature specific data provided by the associated feature server for the Service Type 2 of a given call. If this field is NULL, then no data is captured for this record.
176	Feature Data Two 2	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 second datum of feature specific data provided by the associated feature server for the Service Type 2 of a given call. If this field is NULL, then no data is captured for this record.
177	Feature Data Two 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 second datum of feature specific data provided by the associated feature server for the Service Type 2 of a given call. If this field is NULL, then no data is captured for this record.
178	Feature Data Three1	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 third datum of feature specific data provided by the associated feature server for the Service Type 2 of a given call. If this field is NULL, then no data is captured for this record.
179	Feature Data Three 2	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 third datum of feature specific data provided by the associated feature server for the Service Type 2 of a given call. If this field is NULL, then no data is captured for this record.
180	Feature Data Three 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 third datum of feature specific data provided by the associated feature server for the Service Type 2 of a given call. If this field is NULL, then no data is captured for this record.
181	Qos Orig Average Network Packet Round Trip Delay	Numeric		0, 1-65,535	MGCP DLCX ACK, DLCX	The average network packet round- trip delay as measured from the RTP interface of the originating endpoint. The boundaries of this interface include: •Multiplexing/demultiplexing multiple RTP packets into or out of a single UDP packet •All subsequent handling of transmission and reception of UDP frames in addition to the network delays and peer processing up to the peer's RTP interface A value of zero indicates that this calculation was not supported by the originating endpoint. If this field contains a value of NULL, then no data is captured for this record
182	Qos Term Average Network Packet Round Trip Delay	Numeric		0, 1-65,535	MGCP DLCX ACK, DLCX	The average network packet round- trip delay as measured from the RTP inerface of the terminating endpoint. The boundaries of this interface include: •Multiplexing/demultiplexing multiple RTP packets into or out of a single UDP packet •All subsequent handling of transmission and reception of UDP frames in addition to the network delays and peer processing up to the peer's RTP interface A value of zero indicates that this calculation was not supported by the originating endpoint. If this field contains a value of NULL, then no data is captured for this record
183	Qos Orig Codec Framesize	Numeric		0, 1-65,535	MGCP DLCX ACK, DLCX	The codec frame size in bytes that is used by the originating endpoint. If this field contains a value of NULL, then no data is captured for this record.
184	Qos Term Codec Framesize	Numeric		0, 1-65,535	MGCP DLCX ACK, DLCX	The codec frame size in bytes that is used by the terminating endpoint. If this field contains a value of NULL, then no data is captured for this record.
185	Qos Orig Dead Connection Detection	Numeric		1 = Dead Connection Detected, 2= No Dead Connection Detected	MGCP DLCX ACK, DLCX	Indicates whether the dead connection timer expired either at the beginning of the call or during non-silence receiver states. This metric is reported by the originating endpoint. If this field contains a value of NULL, then no data is captured for this record.
186	Qos Term Dead Connection Detection	Numeric		1 = Dead Connection Detected, 2= No Dead Connection Detected	MGCP DLCX ACK, DLCX	Indicates whether the dead connection timer expired either at the beginning of the call or during non-silence receiver states. This metric is reported by the terminating endpoint. If this field contains a value of NULL, then no data is captured for this record.
187	Qos Orig Concealed Seconds	Numeric		0-65,535	MGCP DLCX ACK, DLCX	Contains the number of elapsed seconds reported by the originating endpoint during which some concealment event has occurred. Concealment invents are defined as any action when 1-50 ms of missing audio information is accounted for in the RTP stream. If this field contains a value of NULL, then no data is captured for this record.
188	Qos Term Concealed Seconds	Numeric		0-65,535	MGCP DLCX ACK, DLCX	Contains the number of elapsed seconds reported by the terminating endpoint during which some concealment event has occurred. A concealment event is defined as any action when 1-50 ms of missing audio information is accounted for in the RTP stream. If this field contains a value of NULL, then no data is captured for this record.
189	Qos Orig Severely Concealed Seconds	Numeric		0-65,535	MGCP DLCX ACK, DLCX	Contains the number of elapsed seconds reported by the originating endpoint during which some severe concealment event has occurred. A severe concealment event is defined as any action when >50 ms of missing audio information is accounted for in the RTP stream. If this field contains a value of NULL, then no data is captured for this record.
190	Qos Term Severely Concealed Seconds	Numeric		0-65,535	MGCP DLCX ACK, DLCX	Contains the number of elapsed seconds reported by the terminating endpoint during which some severe concealment event has occurred. A severe concealment event is defined as any action when >50 ms of missing audio information is accounted for in the RTP stream. If this field contains a value of NULL, then no data is captured for this record.
191	Qos Orig Mos LQK	Numeric		10-50	MGCP DLCX ACK, DLCX	Contains the computed average MOS score for the listening quality of the call based on the K-factor at the originating endpoint. The K-factor is a clarity of MOS-LQ (listening quality) estimator. It is a predicted MOS score based entirely on impairments due to frame loss and codec. The K-factor does not include any impairments due to delay or channel factors. On a per call basis, only the K-factor or the R-factor is reported, but not both. If this field contains a value of NULL, then no data is captured for this record. A value of 127 indicates that information was collected but the endpoint is stating that this metric is not available for this call.
192	Qos Term Mos LQK	Numeric		10-50	MGCP DLCX ACK, DLCX	Contains the computed average MOS score for the listening quality of the call based on the K-factor at the terminating endpoint. The K-factor is a clarity of MOS-LQ (listening quality) estimator. It is a predicted MOS score based entirely on impairments due to frame loss and codec. The K-factor does not include an impairments due to delay or channel factors. On a per call basis, only the K-factor or the R-factor is reported, but not both. If this field contains a value of NULL, then no data is captured for this record. A value of 127 indicates that information was collected but the endpoint is stating that this metric is not available for this call.
193	Qos Orig Local Total Packet Loss Rate	Numeric		0-255	MGCP DLCX ACK, DLCX	Represents the total number of packets sent or expected minus the total number of packets received divided by the total number of packets sent or expected. The total packet loss ratio is equivalent to the average of the interval packet loss ratio. This is the ratio calculated by the originating endpoint. The value represented in this field is the number of 1/256ths of loss that occurred. For example, a value of 12 indicates that 12/256 of the packets over the duration of the call were lost. If this field contains a value of NULL, then no data is captured for this record.
194	Qos Term Local Total Packet Loss Rate	Numeric		0-255	MGCP DLCX ACK, DLCX	Represents the total number of packets sent or expected minus the total number of packets received divided by the total number of packets sent or expected. The total packet loss ratio is equivalent to the average of the interval packet loss ratio. This is the ratio calculated by the terminating endpoint. The value represented in this field is the number of 1/256ths of loss that occurred. For example, a value of 12 indicates that 12/256 of the packets over the duration of the call was lost. If this field contains a value of NULL, then no data is captured for this record.
195	Qos Orig Local End System Delay	Numeric		0,1-65,535	MGCP DLCX ACK, DLCX	The average end system delay at the originating endpoint is the sum of the accumulated send delay plus the accumulated received delay expressed in milliseconds. The end system fixed delay is computed based on codec selection, frame size, number of frames per packet, and typical or expected nominal queuing delays. This number will vary from endpoint to endpoint based on the specific endpoint's implementation details. A value of zero is present if the endpoint does not support the calculation of this metric. If this field contains a value of NULL, then no data is captured for this record.
196	Qos Term Local End System Delay	Numeric		0,1-65,535	MGCP DLCX ACK, DLCX	The average end system delay at the terminating endpoint is the sum of the accumulated send delay plus the accumulated received delay expressed in milliseconds. The end system fixed delay is computed based on codec selection, frame size, number of frames per packet, and typical or expected nominal queuing delays. This number will vary from endpoint to endpoint based on the specific endpoint's implementation details. A value of zero is present if the endpoint does not support the calculation of this metric. If this field contains a value of NULL, then no data is captured for this record.
197	Qos Orig Local Cummulative Packet Discard Count	Numeric		0-255	MGCP DLCX ACK, DLCX	Represents the number of packets discarded by the originating endpoint since the inception of the call. Packets are considered discarded if they arrive too late to be played out or too early to be buffered. Packets received which are duplicates of previously received packets and hence are discarded, are not counted. If this field contains a value of NULL, then no data is captured for this record.
198	Qos Term Local Cummulative Packet Discard Count	Numeric		0-255	MGCP DLCX ACK, DLCX	Represents the number of packets discarded by the terminating endpoint divided since the inception of the call. Packets are considered discarded if they arrive too late to be played out or too early to be buffered. Duplicates of previously received packets are discarded and are not counted. If this field contains a value of NULL, then no data is captured for this record.
199	Qos Orig Local Mos R Factor	Numeric		0-100,127	MGCP DLCX ACK, DLCX	This is a configured MOS R-factor value reported by the originating endpoint. The R-factor is based on ITU-T g.107 which was developed primarily for network planning. The MOS R-factor has three basic components: •A fudge factor which depends on the equipment and codec used. It is constant for the connection. •The delay impairment factor which depends on real time round-trip delay and echo. •A component that depends on real time packet loss. A value of 127 indicates that information was collected but the endpoint is stating that this metric is not available for this call. If this field contains a value of NULL, then no data is captured for this record
200	Qos Term Local Mos R Factor	Numeric		0-100,127	MGCP DLCX ACK, DLCX	This is a configured MOS R-factor value reported by the terminating endpoint. The R-factor is based on ITU-T g.107 which was developed primarily for network planning. The MOS R-factor has three basic components: •A fudge factor which depends on the equipment and codec used. It is constant for the connection. •The delay impairment factor which depends on real time round trip delay and echo. •A component that depends on real time packet loss. A value of 127 indicates that information was collected but the endpoint is stating that this metric is not available for this call. If this field contains a value of NULL, then no data is captured for this record.
201	Qos Orig Local Mos LQR	Numeric		10-50,127	MGCP DLCX ACK, DLCX	This is the estimated receiving and listening quality MOS value reported by the originating endpoint. The nominal range of MOS score is 0 - 5. Before being expressed in MGCP, the MOS scored is multiplied by 10 and any fractional part is truncated. This parameter is computed from the start of metrics collection. A value of 127 indicates that information was collected but the endpoint is stating that this metric is not available for this call. If this field contains a value of NULL, then no data is captured for this record.
202	Qos Term Local Mos LQR	Numeric		10-50,127	MGCP DLCX ACK, DLCX	This is the estimated receiving and listening quality MOS value reported by the terminating endpoint. The nominal range of MOS score is 0 - 5. Before being expressed in MGCP, the MOS scored is multiplied by 10 and any fractional part is truncated. This parameter is computed from the start of metrics collection. A value of 127 indicates that information was collected but the endpoint is stating that this metric is not available for this call. If this field contains a value of NULL, then no data is captured for this record.
203	Qos Orig Local Jitter Buffer Mode	Numeric		0=unknown 1=reserved 2=non-adaptive 3=adaptive	MGCP DLCX ACK, DLCX	The jitter buffer mode configuration of the originating endpoint. If this field contains a value of NULL, then no data is captured for this record.
204	Qos Term Local Jitter Buffer Mode	Numeric		0=unknown 1=reserved 2=non-adaptive 3=adaptive	MGCP DLCX ACK, DLCX	The jitter buffer mode configuration of the terminating endpoint. If this field contains a value of NULL, then no data is captured for this record.
205	Qos Orig Local Rtp Ip Address	String		Dotted Decimal IP Address	MGCP DLCX ACK, DLCX	The IP address of the originating endpoint from a bearer (RTP) perspective. If this field contains a value of NULL, then no data is captured for this record.
206	Qos Term Local Rtp Ip Address	String		Dotted Decimal IP Address	MGCP DLCX ACK, DLCX	The IP address of the terminating endpoint from a bearer (RTP) perspective. If this field contains a value of NULL, then no data is captured for this record.
207	Qos Orig Local Rtp Port	Numeric		1-65535	MGCP DLCX ACK, DLCX	The rtp port used by the originating endpoint. If this field contains a value of NULL, then no data is captured for this record.
208	Qos Term Local Rtp Port	Numeric		1-65535	MGCP DLCX ACK, DLCX	The rtp port used by the terminating endpoint. If this field contains a value of NULL, then no data is captured for this record.
209	Qos Orig Local Address Type	Numeric		IPV4=0 IPV6=1	MGCP DLCX ACK, DLCX	The address type (version 4 or 6) of the originating endpoint. If this field contains a value of NULL, then no data is captured for this record.
210	Qos Term Local Address Type	Numeric		IPV4=0 IPV6=1	MGCP DLCX ACK, DLCX	The address type (version 4 or 6) of the terminating endpoint. If this field contains a value of NULL, then no data is captured for this record.
211	Qos Orig 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, DLCX	The negotiated codec used by the originating endpoint. If this field contains a value of NULL, then no data is captured for this record.
212	Qos Term 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, DLCX	The negotiated codec used by the terminating endpoint. If this field contains a value of NULL, then no data is captured for this record.
213	Qos Orig R factor LQ	Numeric		0-120,127	MGCP DLCX ACK, DLCX	R factor (listening quality) parameter collected from the originating endpoint involved in the call. This value represents the listening quality of the RTP session calculated as per ITU-T Recommendation G.107. The parameter is computed from the start of metrics computation. If this field contains a value of NULL, then no data is captured for this record.
214	Qos Term R factor LQ	Numeric		0-120,127	MGCP DLCX ACK, DLCX	R factor (listening quality) parameter collected from the terminating endpoint involved in the call. This value represents the listening quality of the RTP session calculated as per ITU-T Recommendation G.107. The parameter is computed from the start of metrics computation. If this field contains a value of NULL, then no data is captured for this record.
215	Dqos Orig Buffer Size	Numeric		32 bit IEEE floating point number	DQOS GATESPEC - Token Bucket Size field	The buffer size used by the originating endpoint as reported in the Dqos Gatespec message's Token Bucket Size field. If this field contains a value of NULL, then no data is captured for this record.
216	Dqos Term Buffer Size	Numeric		32 bit IEEE floating point number	DQOS GATESPEC - Token Bucket Size field	The buffer size used by the terminating endpoint as reported in the Dqos Gatespec message's Token Bucket Size field. If this field contains a value of NULL, then no data is captured for this record.
217	Dqos Orig Packet Size	Numeric		32 bit integer	DQOS GATESPEC - Maximum Packet Size field	The maximum packet size reported by the originating endpoint as reported in the Dqos Gatespec message's Maximum Packet Size field. If this field contains a value of NULL, then no data is captured for this record.
218	Dqos Term Packet Size	Numeric		32 bit integer	DQOS GATESPEC - Maximum Packet Size field	The maximum packet size reported by the terminating endpoint as reported in the Dqos Gatespec message's Maximum Packet Size field. If this field contains a value of NULL, then no data is captured for this record.
219	Dqos Orig Speech Size	Numeric		32 bit integer	DQOS GATESPEC - Maximum Packet Size field	The speech size reported by the originating endpoint. For voice calls, this is the same as the Dqos Gatespec message's Maximum Packet Size field. If this field contains a value of NULL, then no data is captured for this record.
220	Dqos Term Speech Size	Numeric		32 bit integer	DQOS GATESPEC - Maximum Packet Size field	The speech size reported by the terminating endpoint. For voice calls, this is the same as the Dqos Gatespec message's Maximum Packet Size field. If this field contains a value of NULL, then no data is captured for this record.
221	Dqos Orig Bandwidth	Numeric		32 bit IEEE floating point number	DQOS GATESPEC - Rate field	The allocated bandwidth reported by the originating endpoint as reported in the Dqos Gatespec message's Rate field. If this field contains a value of NULL, then no data is captured for this record.
222	Dqos Term Bandwidth	Numeric		32 bit IEEE floating point number	DQOS GATESPEC	The allocated bandwidth reported by the terminating endpoint as reported in the Dqos Gatespec message's Rate field. If this field contains a value of NULL, then no data is captured for this record.
223	Orig CAC Type	Numeric		1=DQOS 2=PCMM_COPS 3=NONE	Qos::ClientType	The type of admission control used for the originating side of the call. The type of admission control to be used for the call half can be determined from the provisioned value in the CLIENT-TYPE field of the QOS table. This field is set to NONE if BTS 10200 does not use the Admission Control mechanism for the originating call because of an error scenario, for example, a provisioning errors or the connection to CMTS/Policy Server is down. If this field contains a value of NULL, then no data is captured for this record.
224	Term CAC Type	Numeric		1=DQOS 2=PCMM_COPS 3=NONE	Qos::ClientType	The type of admission control used for the terminating side of the call. The type of admission control to be used for the call half can be determined from the provisioned value in the CLIENT-TYPE field of the QOS table. This field is set to NONE if BTS 10200 does not use the Admission Control mechanism for terminating call arising due to an error scenario such as provisioning errors or the connection to CMTS/Policy Server is down. If this field contains a value of NULL, then no data is captured for this record.
225	Modem Indicator	Numeric		0=FALSE 1=TRUE	MgwProfile::ModemToneSupp and TGCP/NCS NTFY message	This is an indication of whether or not the call used a modem. This field is populated based on the setting in the media gateway profile table and if an up-speed fax is sent during the call. This is only applicable to TGCP and NCS controlled end point. If this field contains a value of NULL, then no data is captured for this record.
226	TDD Indicator	Numeric		0=FALSE 1=TRUE	MgwProfile::TddToneSupp and TGCP/NCS NTFY message	This is an indication of whether or not the call used a TDD relay device. This field is populated based on the setting in the media gateway profile table and if triggered by the appropriate NTFY event during the call. This is only applicable to TGCP and NCS controlled end point. If this field contains a value of NULL, then no data is captured for this record.
227	CTRAC Id	Numeric		Unsigned 32 bit integer	System Generated	This is a unique identifier generated by the BTS 10200 on a per call basis. The scope of this identifier does not extend beyond a single BTS 10200 instance. The value is used for troubleshooting purposes to correlate between the CDR and the associated trace statements produced by the system on a per call basis. If this field contains a value of 0, then no data is captured for this record.
228	Originating NE Type	Numeric		1=CMS 3=MGC	CallAgentProfile:: CMS-Id or CallAgentProfile:: MGC-Id	This field indicates the type of network element that is reporting the originating side call detail record. If this field contains a value of NULL, then no data is captured for this record. For a SIP based call, the types supported are: •Voice Mail - CMS •SIP subscriber - CMS •CMSS TG - MGC •Non-CMSS TG - CMS
229	Terminating NE Type	Numeric		1=CMS 3=MGC	CallAgentProfile::CMS-Id or CallAgentProfile::MGC-Id	This field indicates the type of network element that is reporting the terminating side call detail record If this field contains a value of NULL, then no data is captured for this record. For a SIP based call, the types supported are: •Voice Mail - CMS •SIP subscriber - CMS •CMSS TG - MGC •Non-CMSS TG - CMS
230	Originating BCID	ASCII	40	The format of this field is: Timestamp converted to ascii concatenated to ElementId concatenated to TimeZone concatenated to EventCounter converted to ascii. Each of these fields is separated by an underscore resulting in: TimeStamp_ElementId_TimeZone_EventCounter	System Generated	This field is system-generated by the Event Messaging (EM) billing subsystem if it is used in conjunction with post call billing. This field is populated by the originating side of the call. It is used to correlate the billing information within a network element and/or between network elements in a PacketCable compliant deployment. If this field contains a value of NULL, then no data is captured for this record.
231	Terminating BCID	ASCII	40	The format of this field is: Timestamp converted to ascii concatenated to ElementId concatenated to TimeZone concatenated to EventCounter converted to ascii. Each of these fields is separated by an underscore resulting in: TimeStamp_ElementId_TimeZone_EventCounter	System Generated	This field is system-generated by the Event Messaging (EM) billing subsystem if it is used in conjunction with post call billing. This field is populated by the terminating side of the call. It is used to correlate billing information within a network element and/or between network elements in a PacketCable compliant deployment. If this field contains a value of NULL, then no data is captured for this record.
232	SIP Originating Context Id	ASCII	64		SIP INVITE - Context-id field	Contains the originating side context id received in the SIP INVITE message. This is used to correlate calls made to application servers as part of origination side SIP trigger processing.
233	SIP Terminating Context Id	ASCII	64		SIP INVITE - Context-id field	Contains the terminating side context id received in the SIP INVITE message. This is used to correlate calls made to application servers as part of termination side SIP trigger processing.
234	Qos Orig Remote Packets Sent	Numeric		0- 4,294,967,295	MGCP DLCX ACK, DLCX	The total number of RTP data packets transmitted by the originating end point since starting transmission. If this field contains a value of NULL, then no data is captured for this record.
235	Qos Term Remote Packets Sent	Numeric		0- 4,294,967,295	MGCP DLCX ACK, DLCX	The total number of RTP data packets transmitted by the terminating end point since starting transmission. If this field contains a value of NULL, then no data is captured for this record.
236	Qos Orig Remote Octets Sent	Numeric		0- 4,294,967,295	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 contains a value of NULL, then no data is captured for this record.
237	Qos Term Remote Octets Sent	Numeric		0- 4,294,967,295	MGCP DLCX ACK, DLCX	The total number of payload octets transmitted in RTP data packets by the terminating 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 contains a value of NULL, then no data is captured for this record.
238	Qos Orig Remote Packets Lost	Numeric		0-16,717,215	MGCP DLCX ACK	The total number of RTP data packets from the terminating endpoint 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 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 contains a value of NULL, then no data is captured for this record.
239	Qos Term Remote Packets Lost	Numeric		0-16,717,215	MGCP DLCX ACK	The total number of RTP data packets from the originating endpoint 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 contains a value of NULL, then no data is captured for this record.
240	Qos Orig Remote Average Inter-arrival Jitter	Numeric		0-536,870,912	MGCP DLCX ACK, DLCX	This is an estimate of the average statistical variance of the RTP data packet interarrival time, measured in timestamp units and expressed as an unsigned integer by the originating endpoint. The inter-arrival jitter is defined as the mean debytion (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 of arrival. The value is calculated in terms of 125 microsecond ticks and converted to milliseconds for storage in the CDR. If this field contains a value of NULL, then no data is captured for this record.
241	Qos Term Remote Average Inter-arrival Jitter	Numeric		0-536,870,912	MGCP DLCX ACK, DLCX	This is an estimate of the average statistical variance of the RTP data packet interarrival time, measured in timestamp units and expressed as an unsigned integer by the terminating endpoint. The interarrival jitter is defined to be 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 of arrival. The value is calculated in terms of 125 microsend ticks and converted to milliseconds for storage in the CDR. If this field contains a value of NULL, then no data is captured for this record.
242	Qos Orig Local External Mos R Factor	Numeric		0-100	MGCP DLCX, DLCX ACK	A value (XSR) representing the effects of any call segment carried over a network segment external to the one on which the endpoint resides. It is calculated according to ITU-T Recommendation G.107.
243	Qos Term Local External Mos R Factor	Numeric		0-100	MGCP DLCX, DLCX ACK	A value (XSR) representing the effects of any call segment carried over a network segment external to the one on which the endpoint resides. It is calculated according to ITU-T Recommendation G.107.
244	Qos Orig Local Estimated MOS-CQ	Numeric		0-50	MGCP DLCX, DLCX ACK	An estimated receiving end Conversational Quality MOS. The nominal range of MOS scores is 0-5. Before being expressed in MGCP, the MOS score is multiplied by 10 and any fractional part is truncated.
245	Qos Term Local Estimated MOS-CQ	Numeric		0-50	MGCP DLCX, DLCX ACK	An estimated receiving end Conversational Quality MOS. The nominal range of MOS scores is 0-5. Before being expressed in MGCP, the MOS score is multiplied by 10 and any fractional part is truncated.
246	Qos Orig Local Minimum gap threshold	Numeric		1-255	MGCP DLCX, DLCX ACK	The gap/burst transition threshold. The recommended value is 16.
247	Qos Term Local Minimum gap threshold	Numeric		1-255	MGCP DLCX, DLCX ACK	The gap/burst transition threshold. The recommended value is 16.
248	QoS Orig Local Packet loss concealment type	Numeric		0=UNSPECIFIED 1=DISABLED 2=ENHANCED 3=STANDARD	MGCP DLCX, DLCX ACK	The type of packet loss concealment algorithm in use.
249	QoS Term Local Packet loss concealment type	Numeric		0=UNSPECIFIED 1=DISABLED 2=ENHANCED 3=STANDARD	MGCP DLCX, DLCX ACK	The type of packet loss concealment algorithm in use.
250	Qos Orig Local Jitter buffer rate	Numeric		0-15	MGCP DLCX, DLCX ACK	The jitter buffer adjustment rate (JBR).
251	Qos Term Local Jitter buffer rate	Numeric		0-15	MGCP DLCX, DLCX ACK	The jitter buffer adjustment rate (JBR).
252	Qos Orig Local Nominal Jitter buffer delay	Numeric		0-65535	MGCP DLCX, DLCX ACK	Current nominal delay (JBN) in milliseconds that corresponds to the nominal jitter buffer delay for packets that arrive exactly on time.
253	Qos Term Local Nominal Jitter buffer delay	Numeric		0-65535	MGCP DLCX, DLCX ACK	Current nominal delay (JBN) in milliseconds that corresponds to the nominal jitter buffer delay for packets that arrive exactly on time.
254	Qos Orig Local Maximum jitter buffer delay	Numeric		0-65535	MGCP DLCX, DLCX ACK	Current maximum delay (JBM) in milliseconds that corresponds to the earliest arriving packet that would not be discarded. In simple queue implementations, this might correspond to the nominal jitter buffer delay. In adaptive jitter buffer implementations, this value can vary dynamically up to the absolute maximum jitter buffer delay.
255	Qos Term Local Maximum jitter buffer delay	Numeric		0-65535	MGCP DLCX, DLCX ACK	Current maximum delay (JBM) in milliseconds that corresponds to the earliest arriving packet that would not be discarded. In simple queue implementations, this might correspond to the nominal jitter buffer delay. In adaptive jitter buffer implementations, this value can vary dynamically up to the absolute maximum jitter buffer delay.
256	Qos Orig Local Absolute maximum jitter buffer delay	Numeric		0-65535	MGCP DLCX, DLCX ACK	Absolute maximum delay (JBS) in milliseconds that an adaptive jitter buffer can reach under worst case conditions. For fixed jitter buffers, this must be set to the maximum jitter buffer delay.
257	Qos Term Local Absolute maximum jitter buffer delay	Numeric		0-65535	MGCP DLCX, DLCX ACK	Absolute maximum delay (JBS) in milliseconds that an adaptive jitter buffer can reach under worst case conditions. For fixed jitter buffers, this must be set to the maximum jitter buffer delay.
258	ServiceStatus1	Numeric		0-4		The defined values related to ServiceType1 are: •INSTANCE(1) •ACTIVATION (2) •DEACTIVATION (3) •INTERROGATION (4) •FORWARDED(5)
259	ServiceStatus2	Numeric		0-4		The defined values related to ServiceType2 are: •INSTANCE(1) •ACTIVATION (2) •DEACTIVATION (3) •INTERROGATION (4) •FORWARDED(5)
260	ServiceStatus3	Numeric		0-4		The defined values related to ServiceType3 are: •INSTANCE(1) •ACTIVATION (2) •DEACTIVATION (3) •INTERROGATION (4) •FORWARDED(5)
261	EnumRouteUsed	Numeric		0=No 1=Yes		This flag is set if the call is routed by means of the domain2route table/default domain when a positive ENUM response is received.
262	Gateway KeepAlive FailureTime	Numeric		A maximum 128 bit unsigned value in total. Seconds are expressed in GMT epoch time format - the number of seconds since Jan 01, 1970 0:00:00.000h. This is followed by a decimal point (.), with 3 digits for the millisecond value. If the value is NULL, the timestamp is to be ignored	Dynamic run time data from the system clock	Time that the call was up with a Gateway Keep Alive Failure condition present.
263	IMS Charging Identifier (ICID)	String	32	Alphanumeric	The charging vector may be filled in during the establishment of a dialog. The information inside the charging vector can be filled in by multiple network entities and retrieved by multiple network entities.	The ICID is a charging value that identifies a dialog or a transaction outside a dialog. It is used to correlate charging records.
264	NENA_V6_CALLING_PARTY	String	64	Digits	Incoming SIP INVITE on NENA V4 interface	This field is populated from the FROM header of the V4 invite.
265	NENA V6 Called Party	String	64	Digits	Incoming SIP INVITE on NENA V4 interface	This field is populated from the TO header in the V4 invite.
266	NENA V4 ESQK	String	64	Digits	Incoming SIP INVITE on NENA V4 interface.	This field is populated from the P-Asserted-ID parameter in the V4 invite.
267	NENA V4 ESRN	String	64	Digits	Incoming SIP INVITE on NENA V4 interface.	This field is populated from the Req-URI in the V4 invite.
268	Incoming Trunk Context	String	64	Alphanumeric	Incoming SIP INVITE message with Req-URI containing the trunk-context user parameter.	Represents the trunk-context value that is received in incoming invite.
269	Outgoing Trunk Context	String	64	Alphanumeric	Outgoing SIP INVITE message with Req-URI containing trunk-context user parameter.	Represents the trunk-context value that is sent in the outgoing invite, when TGRP routing takes place.

Operator Call Type in Field 1

Release 6.0.1 Behavior

In Release 6.0.1, there is a new parameter, CALLTYPE-OPER-CALL-CDR in the ca-config table. If it is set to N (the default value), the system populates billing Field 1 just as it did for Release 5.0 (above). However, if you provision CALLTYPE-OPER-CALL-CDR=Y, the system treats the call in the following way:


User dials 0	The billing call type is shown as 26, OPERATOR (same as in Release 5.0).
User dials 00	The billing call type is shown as 27, CARRIER-OPERATOR (same as in Release 5.0).
User dials 0+	The billing call type is shown as 28, OPERATOR-ASSISTED.
User dials 01+	The billing call type is shown as 44, INTL-OPERATOR.

Release 5.0.x Behavior

In Release 5.0.x, the system reports the following 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+):


User dials 0	The billing call type is shown as 26, OPERATOR.
User dials 00	The billing call type is shown as 27, CARRIER-OPERATOR.
User dials 0+	The billing call type depends on the type of call dialed following the 0+. For example •If the call is 0+ and the call has call-type=INTERLATA in the destination table, the billing call type is shown as 5, INTERLATA. •If the call is 0+ and the call has call-type=TOLL in the destination table, the billing call type is shown as 4, TOLL. •If the call is 0+ and the call has call-type=NATIONAL in the destination table, the billing call type is shown as 31, NATIONAL. •If the call is 0+ and the call has call-type=NAT_OPR in the destination table, the billing call type is shown as 45, NATL_OPERATOR.
User dials 01+	The billing call type depends on the type of call dialed following the 01+. For any call type following the 01+, the call-type provisioned in the destination table is the call type reported in Field 1 of the CDB.

Bias-Free Language

Book Title

Billing Guide, Release 6.0.3

Chapter Title

Chapter 4: Call Detail Block File Fields

Results

Chapter: Chapter 4: Call Detail Block File Fields

Call Detail Block File Fields

Operator Call Type in Field 1

Release 6.0.1 Behavior

Release 5.0.x Behavior

Was this Document Helpful?

Contact Cisco