-
Billing Guide
-
Preface
-
Chapter 1: Operational Procedures
-
Chapter 2: Feature Server Derived Call Data
-
Appendix A: Call Detail Block File Fields
-
Appendix B Call Termination Cause Codes:
-
Appendix C: Example Call Detail Block File
-
Appendix D: Time Zone Mapping Table
-
Billing Guide Delta Document for Releases 3.5.x and 4.5
-
Feedback
Table Of Contents
Call Detail Block File Fields 4.5.1
Call Detail Block File Fields 4.5.1
Revised: March 11, 2009, OL-4486-12Revision history for this appendix:
December 14, 2006
(Changes for BTS Release 4.5.1)
Call Detail Block field 109 — changed Field Description based on change between Release 4.5 and Release 4.5.1.
Call Detail Block field 143 — changed "From" to "To".
November 3, 2006
(Changes for BTS Release 4.5.1)
Call Detail Block File field 1 — added Potential Value of 55 = WAKE_UP.
Call Detail Block File field 19 — changed Max Field Size to 12-17.
Call Detail Block File field 20 — changed Max Field Size to 12-17.
Call Detail Block File field 40 — removed Centrex group.
Call Detail Block File field 29 — added Potential Value of 69 = WAKE UP CALL.
Call Detail Block File field 164 — updated to show differences between BTS Releases 4.5 and 4.5.1.
Call Detail Block File fields 171-174 — added.
November 2006
(Corrections)
Corrected Detail Block File field 92 and 101 to include more Data Source information.
Corrected Detail Block File field 92 to include more Potential Value information.
Corrected Detail Block File field 132 additional content to Field Description.
Updated Call Detail Block File field 164 to show differences between BTS Releases 4.5 and 4.5.1.
October 2006
(Correction)
Corrected the Call Detail Block File field 150 and 151 values.
September 2006
(Changes for BTS Release 4.5.1)
Changed the Call Detail Block File field 166 values.
April 2005
Updated Table A-1,Call Detail Block Field Descriptions with Release 4.5 information.
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) for retention purposes. The Cisco 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 via the File Transfer Protocol (FTP).
This appendix illustrates the format of each field in a Call Detail Block (CDB), the order in which it occurs, the possible values for the individual fields and the meaning of the data within the field where applicable. The delimiters used to separate fields within a record or records within a file can be any one of the following:
•
semi-colon ";"
•
•
•
•
Note
The CDB field and record separators are defined in the platform.cfg file that is read at initialization time. The platform.cfg file associated with the BDMS platform must be updated for changes to take affect; however, the file cannot be changed without a system restart. Both active and standby BDMS platforms must be restarted to pick up any change of delimiters.
The [ProcessParameter] block to update is "ProcName=BMG." The parameter to update is "Args." To change the field delimiter you must update the "-FD" option. To change the record delimiter you must update the "-RD" option. Both of the BDMS computing platforms must be restarted to pick up this change of delimiters.
Caution
The steps to follow are:
1. Stop the platform on the EMS.
2. Change the platform.cfg on the EMS.
3. Flush the old billing records from the EMS before starting the platform.
4. Start the platform. All new billing records now use the new format.
Table A-1 provides information detailing the information contained in the fields in the output files transmitted from the Element Management System (EMS) on the Cisco BTS 10200 Softswitch.
Table A-1 Call Detail Block Field Descriptions
1
(BTS Release 4.5.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
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 4.5, it is possible to provision the Destination table with any one of the following:
•
•
•
•
Alternatively, it is possible to provision the following (one pair per DEST-ID):
call-type=EMG; call-subtype=AMBULANCE
call-type=EMG; call-subtype=FIRE
call-type=EMG; call-subtype=POLICE
call-type=EMG; call-subtype=NONE (default)
For service providers in the U.S., it is typical to provision the Destination table with call-type=EMG for the digit string 911, and call-subtype=NONE (default), because 911 is a central dispatch point for all emergency, ambulance, fire, and police calls.
1
(BTS Release 4.5.1) (continued)
Call Type
Numeric
29=BLV
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
* - not used in NANP areas
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.
Caution
1
(BTS Release 4.5.0)
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
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 4.5, it is possible to provision the Destination table with any one of the following:
call-type=EMG
call-type=AMBULANCE
call-type=FIRE
call-type=POLICE
Alternatively, it is possible to provision the following (one pair per DEST-ID):
call-type=EMG; call-subtype=AMBULANCE
call-type=EMG; call-subtype=FIRE
call-type=EMG; call-subtype=POLICE
call-type=EMG; call-subtype=NONE (default)
For service providers in the U.S., it is typical to provision the Destination table with call-type=EMG for the digit string 911, and call-subtype=NONE (default), because 911 is a central dispatch point for all emergency, ambulance, fire, and police calls.
1
(BTS Release 4.5.0) (continued)
Call Type
Numeric
29=BLV
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
* - not used in NANP areas
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.
Caution
2
Signal Start Time
Numeric
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:00h.
Dynamic run time data from the system clock.
Time starts on receipt of an MGCP NTFY, SS7 IAM or SIP SETUP. If the value is NULL, timestamp is ignored.
3
Signal Stop Time
Numeric
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1, 1970 0:00:00h.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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
(BTS Release 4.5.1 only)
Call Elapsed Time
String
12-17
(DDDDD):HH:MM:SS
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.
2) 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 the first time. Then every 60 minutes, BLG checks again and again.19
(BTS Release 4.5.0 only)
Call Elapsed Time
String
11
(DDDDD):HH:MM:SS
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.
2) 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 the first time. Then every 60 minutes, BLG checks again and again.20
(BTS Release 4.5.1 only)
Interconnect Elapsed Time
String
12-17
(DDDDD):HH:MM:SS
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 is NULL, then no data was captured for this record.
20
(BTS Release 4.5.0 only)
Interconnect Elapsed Time
String
11
(DDDDD):HH:MM:SS
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 is NULL, then no data was captured for this record.
21
Originating QOS Time
Numeric
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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 is NULL—then the associated Originating QOS parameters are to be ignored.
22
Terminating QOS Time
Numeric
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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 is 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 this field is 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 is NULL, then no data was 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 is 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 if an LNP query is launched or not. In addition, for inbound SS7 calls 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 making an LNP dip.
This field is populated with the received LRN if one is presented for inbound calls to the reporting Cisco BTS 10200 for called numbers that are homed on the Cisco BTS 10200.
The Ported Office Code table is typically populated via 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 was 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 when dialed by a subscriber that is homed on the Cisco BTS 10200 Softswitch.
MGCP NTFY, SS7 IAM, ISDN SETUP, SIP INVITE or H.323 SETUP, for example.
This field contains the actual digits dialed by the originator of the call. The field only contains digits dialed in the first stage of the call when dialed by a subscriber that is homed on the Cisco BTS 10200. 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
(BTS Release 4.5.1 only)
Service Type 1
Numeric
1 = CALL_BLOCK (not used)
2 = CALL_FORWARD_UNCONDITIONAL
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.
3 = CALL_WAITING
4 = REPEAT_CALL
5 = RETURN_CALL
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
(BTS Release 4.5.1 only)
(continued)Service Type 1
Numeric
29 = CALL_WAITING_WITH_CALLER_IDENTITY30 = 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
Class name of the first service invoked in call. If this field is a value of ZERO, then no data was captured for this record.
41 = SELECTIVE_CALL_REJECTION
42 = SELECTIVE_CALL_FORWARDING
43 = SELECTIVE_CALL_ACCEPTANCE
44 = AUTOMATIC_CALLBACK
45 = AUTO_RECALL
29
(BTS Release 4.5.1 only)
(continued)Service Type 1
Numeric
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 (not used)
61 = REFER
62 = CALL FORWARD COMBINATION
63 = NO SOLICITATION ANNOUNCEMENT
29
(BTS Release 4.5.1 only)
(continued)Service Type 1
Numeric
64 = PRIVACY SCREENING
65 = VOICE MAIL
66 = VOICE MAIL ACCESS
67 = LCD PREPAID
68 = LCD POSTPAID
69 = WAKE UP CALL
29
(BTS Release 4.5.0 only)
Service Type 1
Numeric
1 = CALL_BLOCK (not used)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.
2 = CALL_FORWARD_UNCONDITIONAL
3 = CALL_WAITING
4 = REPEAT_CALL
5 = RETURN_CALL
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
29
(BTS Release 4.5.0 only) (continued)
Service Type 1
Numeric
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
29
(BTS Release 4.5.0 only) (continued)
Service Type 1
Numeric
40= BUSY_LINE_ VERIFICATIONClass name of the first service invoked in call. If this field is a value of ZERO, then no data was captured for this record.
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 (not used)
61 = 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
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 1
String
30
See Chapter 2, "Feature Server Derived Call Data"for specifics on feature data.
Internal FCP message sent from the feature server to call processing.
Feature specific data provided by the associated Feature Server for the Service Type 1 of a call. If this field is NULL, then no data was captured for this record.
33
Feature Data 2
String
30
See Chapter 2, "Feature Server Derived Call Data" for specifics on feature data.
Internal FCP message sent from the feature server to call processing.
Feature specific data provided by the associated Feature Server for the Service Type 2 of a call. If this field is NULL, then no data was captured for this record.
34
Feature Data 3
String
30
See Chapter 2, "Feature Server Derived Call Data" for specifics on feature data.
Internal FCP message sent from the feature server to call processing.
Feature specific data provided by the associated Feature Server for the 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
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 a value of NULL, then no data was captured for this record.
38
Database Query Result Code1
Numeric
1 = SUCCESS
2 = FAILUREInternal FCP message sent from the feature server to call processing.
Indication of the disposition of the first database query for the call. If this field is a value of NULL, then no data was captured for this record.
39
Database Query
String
128
For CNAM_SCP: Caller's Name or P (private) or O (out of area)
For TOLL_FREE_SCP and TOLL_FREE_LOCAL: original called digits or new called digits returned
For LNP: original called DN or new LRN (ANSI w/LNP profile=LRN)
For LNP: original called DN or concatenated RN plus DN (non-ANSI w/LNP profile=PREFIX-METHOD)
For LNP: original called DN or RN (non-ANSI w/LNP profile=SEPARATE-RN)
Internal FCP message sent from the feature server to call processing.
Directory number, RN and/or NAME returned from the first database query for the call. If this field is NULL, then no data was captured for this record.
CAVEAT: If this field contains a character that coincides with the character specified as the field or record delimiter for the Cisco BTS 10200 billing records, it is replaced with a SPACE character to ensure the integrity of the billing data.
40
(BTS Release 4.5.1 only)
Multiline hunt 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 was captured for this record.
40
(BTS Release 4.5.0 only)
MLH Centrex Group Name
String
16
ASCII characters
Subscriber:: CtxgId or Subscriber:: MlhgId
Identity of the multi-line hunt group (MLHG) or Centrex group that this call is associated with. If this field is NULL, then no data was captured for this record.
41
Called Party Off Hook Indicator
Numeric
0 = NO
1 = YESSS7 ANM, MGCP Offhook NTFY, ISDN ACK, for example.
Indication that the terminating party went off-hook. If this field is NULL, then no data was captured for this record.
42
Called Party Short Off Hook Indicator
Numeric
0 = NO
1 = YESn/a
An indication that the called party was off hook for less than two 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 Operations, Maintenance, and Troubleshooting Guide.
Release indications are both internally and externally detected— dynamic runtime data.
The reason the call was released. If this field is a value of NULL, then no data was captured for this record.
44
Operator Action
Numeric
0 = AUTO_ IDENTIFIED_
CUSTOMER_ DIALED1 = AUTO_ IDENTIFIED_
OPERATOR_ DIALED2 = OPER_ DENTIFIED_
CUSTOMER_ DIALED3 = OPER_ IDENTIFIED_
OPERATOR_ DIALEDOperator action with respect to the originating party:
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 indicative 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 indicative of an Announcement Trunk.
47
Originating Trunk Number
Numeric
32 bit unsigned integer in the range of 1- 99999999
TrunkGroup::Id
Identity of the originating trunk. It is recommended the upper end of this range be limited to 9999 when converting these records to BAF AMA format for compatibility.
If this field is a value of NULL, then no data was captured for this record.
48
Terminating Trunk Number
Numeric
32 bit unsigned integer in the range of 1- 99999999
TrunkGroup::Id
Identity of the terminating trunk. It is recommended the upper end of this range be limited to 9999 when converting these records to BAF AMA format for compatibility.
If this field is a value of NULL, then no data was captured for this record.
49
Outgoing Trunk Number
Numeric
16 bit unsigned integer
SS7 EXM
The outgoing trunk is on the network facing side of the access tandem. When a call is terminated to the access tandem it is over a generic trunk group and the TNS is passed, and, based on the TNS, the access tandem will select the trunk for routing, for example 0288 will select an AT&T trunk. The access tandem then sends an exit message back with the trunk number from the network facing side. That is the number that appears in this field.
50
Carrier Identification Code
String
5
DIGITS
SS7 IAM or Subscriber::PICn or dialed digits for casual dialing scenarios.
Identification of the carrier that transported the call, either an inter-exchange carrier or an international carrier. This value is typically 3- or 4-digits, not necessarily 5-digits. If this field is NULL, then no data was captured for this record.
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 via 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_
INVOLVED1 = CIC_FGD_OPERATOR_ NOT_INVOLVED
2 = CIC_FGD_OPERATOR_
INVOLVED_UNKNOWN7 = CIC_UNKNOWN_ OPERATOR_INVOLVED
8 = CIC_UNKNOWN_ OPERATOR_NOT_ INVOLVED
9 = CIC_UNKNOWN_ OPERATOR_INVOLVED_ UNKNOWN
Dialed digits.
Describes operator involvement: FGD CIC with (1) operator involvement, (2) dialed direct with no operator, (3) with undetermined operator involvement, or unknown CIC with
(1) operator involvement,
(2) dialed direct with no operator, or
(3) 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 release before IAM is sent by originating EC = 15
Call is abandoned or release after IAM is received by originating EC = 20
Dynamic call data.
Indication of how far a call has progressed before terminating 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 via 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 is supported. Values 1, 2, 3, and 4 are reserved for future use.
57
Orig Quality of Service Packets Sent
Numeric
32 bit unsigned value
MGCP DLCX ACK.
Number of packets sent over bearer path for duration of call reported by media gateway.
If this field is NULL, then no data was captured for this record.
58
Orig Quality of Service Packets received
Numeric
32 bit unsigned value
MGCP DLCX ACK.
Number of packets received over bearer path for duration of call reported by media gateway.
If this field is NULL, then no data was captured for this record.
59
Orig Quality of Service Octets Sent
Numeric
32 bit unsigned value
MGCP DLCX ACK.
Number of octets sent over bearer path for duration of call reported by media gateway.
If this field is NULL, then no data was captured for this record.
60
Orig Quality of Service Octets Received
Numeric
32 bit unsigned value
MGCP DLCX ACK.
Number of octets received over bearer path for duration of call reported by media gateway.
If this field is NULL, then no data was captured for this record.
61
Orig Quality of Service Packets Lost
Numeric
32 bit unsigned value
MGCP DLCX ACK.
Number of packets lost over bearer path for duration of call reported by media gateway.
If this field is NULL, then no data was captured for this record.
62
Orig Quality of Service Jitter
Numeric
32 bit unsigned value
MGCP DLCX ACK.
Amount of jitter over bearer path for duration of call reported by media gateway.
If this field is NULL, then no data was captured for this record.
63
Orig Quality of Service Average Latency
Numeric
32 bit unsigned value
MGCP DLCX ACK.
Average latency over bearer path for duration of call reported by media gateway.
If this field is NULL, then no data was captured for this record.
64
Term Quality of Service Packets Sent
Numeric
32 bit unsigned value
MGCP DLCX ACK.
Number of packets sent over bearer path for duration of call reported by media gateway.
If this field is NULL, then no data was captured for this record.
65
Term Quality of Service Packets received
Numeric
32 bit unsigned value
MGCP DLCX ACK.
Number of packets received over bearer path for duration of call reported by media gateway.
If this field is NULL, then no data was captured for this record.
66
Term Quality of Service Octets Sent
Numeric
32 bit unsigned value
MGCP DLCX ACK.
Number of octets sent over bearer path for duration of call reported by media gateway.
If this field is NULL, then no data was captured for this record.
67
Term Quality of Service Octets Received
Numeric
32 bit unsigned value
MGCP DLCX ACK.
Number of octets received over bearer path for duration of call reported by media gateway.
If this field is NULL, then no data was captured for this record.
68
Term Quality of Service Packets Lost
Numeric
32 bit unsigned value
MGCP DLCX ACK.
Number of packets lost over bearer path for duration of call reported by media gateway.
If this field is NULL, then no data was captured for this record.
69
Term Quality of Service Jitter
Numeric
32 bit unsigned value
MGCP DLCX ACK.
Amount of jitter over bearer path for duration of call reported by media gateway.
If this field is NULL, then no data was captured for this record.
70
Term Quality of Service Average Latency
Numeric
32 bit unsigned value
MGCP DLCX ACK.
Average latency over bearer path for duration of call reported by media gateway.
If this field is NULL, then no data was captured for this record.
71
Operator Involvement
Numeric
0 = NO, 1 = YES
Dialed digits.
Determines if operator is involved in the call for 0-, 0+, or 01+.
If this field is NULL, then no data was captured for this record.
72
Casual Dialing
Numeric
0 = NO, 1 = YES
Dialed digits.
Determines whether it is a casual call (CIC) or PIC call.
If this field is NULL, then no data was captured for this record.
73
Connection Type
Numeric
0 = IP
1 = HAIRPIN
3 = ATM SVC
4 = ATM PVCDialed digits.
Type of connection the gateway is making, so the reader of the record knows why the QoS parameters are different then expected. For example, if a Hairpin connection is used, then the QoS will be zeros.
This field currently only contains a value of 0 or 1. This field can be derived from either the Originating or Terminating endpoint. If it is returned from one of the endpoints, then that is what is presented in this field; if it 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 contains a value of NULL, then no data was captured for this record.
74
Packet Time
Numeric
8 bit unsigned value
MGCP DLCX ACK.
Packetization period for voice sampling. This field can be derived from either the Originating or Terminating endpoint. If it is returned from one of the endpoints, then that is what is presented in this field. If it 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 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 that is what is presented in this field. If it 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 if 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 that is what is presented in this field. If it 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.
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 can be derived from either the Originating or Terminating endpoint. If it is returned from one of the endpoints, then that is what is presented in this field. If it 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 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_RECORD3 = 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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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. Any call scenario that results in multiple call records being generated by the Cisco BTS 10200, each will contain 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 BTS 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 JIP of the originating switch for calls inbound to the Cisco BTS 10200. The JIP is populated with the value received in the 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 into 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 into 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 Call Agent on which CDB is created. If this field is NULL, then no data was captured for this record.
87
Originating POP Time Zone
Numeric
Refer to Appendix D, "Time Zone Mapping Table" for the potential values.
Pop::Timezone, Timezone::Id
This is the point of presence that the originating subscriber on the Cisco BTS 10200 is provisioned into. This field provides information on the locale to which the subscriber is a member. This information can also be leveraged for partitioning subscribers on a single Cisco BTS 10200 into multiple business entities for billing purposes. If this field is NULL, then the timestamps within this record are based on the local time zone.
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 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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
If the value is NULL, the timestamp is to be ignored.
Dynamic run time data from the system clock.
Time of day terminating number was dialed for originating half of call.
This field is populated only for calls over an H.323 network.
96
Originating H323 Voice Quality
Numeric
This field is not populated for this release.
Various H.323 messages.
Quality of voice connection for originating side of call. This is a decimal number from the ICPIF table of G.113.
97
Originating H323 Subscriber
Numeric
This field is not populated for this release.
Various H.323 messages.
Subscriber T1/CAS signaling information from originating side of call.
98
Originating H323 Gateway Id
String
16
Alphanumeric characters.
Various H.323 messages.
For incoming calls from an H.323 network, this field will contain the h323-id of the originating (peer) H.323 gateway/endpoint. If this parameter is not available in the incoming H.323 call, the Cisco BTS 10200 will populate this field with local h323-id from the H.323-GW that received the call. For incoming calls from non-H.323 networks, this field is NULL.
This field is only populated for calls over an H.323 network. If this field is NULL, no data was captured for this record.
99
Originating H323 Gatekeeper Id
String
16
Alphanumeric characters.
Various H.323 messages.
The hostname of the originating primary gatekeeper for the call.
This field is only populated for calls over an H.323 network. If this field is NULL, no data was captured for this record.
100
Terminating H323 Call Origin
Numeric
0 = NULL
1 = ANSWER
2 = ORIGINATEVarious H.323 messages.
ANSWER indicates the call terminated on the reporting gateway.
ORIGINATE indicates the call was outbound from the reporting gateway for the terminating half of the call.
This field is only populated for calls over an H.323 network. If this field is a value of NULL, no data was captured for this record.
101
Terminating H323 Call Type
Numeric
1 = VOIP
2 = TELEPHONY3 = VIDEO
Bearer Capability field of incoming SETUP messages and the VIDEO_SUPP field in the H323-TG-PROFILE and H323-TERM-PROFILE tables.
Indication of the protocol family used on the terminating leg of the call.
This field is only populated for calls over an H.323 network. If this field is a value of NULL, no data was captured for this record
102
Terminating H323 Conference Id
String
32
Alphanumeric characters.
Various H.323 messages.
A unique identifier generated by the terminating PSTN gateway for each unique call scenario within a given call context.
This field is only populated for calls over an H.323 network. If this field is NULL, no data was captured for this record.
103
Terminating H323 Remote Address
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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 no 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
(BTS Release 4.5.1, MR1 only)
Orig Type
Numeric
0 = ON NET
1 = OFF NET
Dialed digits.
Indicates whether call was originated by a subscriber homed on the reporting Cisco BTS 10200 Softswitch.
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 in ound 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 other local application server.
110
Term Type
Numeric
0 = ON NET
1 = OFF NET
Dialed digits.
Indication of whether call was terminated by subscriber homed on the reporting Cisco BTS 10200 Softswitch.
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 finding a 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 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 will be 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 IZCT (Intra Zone Clear Token) 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 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 form 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 into 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.
If this field is NULL, then no data was 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 via SIP if it is over 64 characters in length.
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 Cisco BTS 10200 Softswitch.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
Dynamic run time data from the system clock.
Time the 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 is 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
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)
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.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
If the value is NULL, the timestamp is to be 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 is 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
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 is 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)
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 is 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
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 is 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 is 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 is 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 is 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 GOOD3 = OF—MODEM FAILURE
MGCP NTFY
Indicates result of performing pre-authorization on a NAS-based call.
If this field is a value of NULL, no data was captured for this record.
132
Fax Indicator
Numeric
0 = NOT FAX
1 = FAX ONLY
2 = VOICE AND FAX
Internally generated by call processing.
Indication of whether the call involved any fax transmissions. The value "Voice & Fax" indicates at least one fax was sent or received.
This field contains a zero when operating in an MGW to MGW controlled mode. When a fax is sent under MGW control, if an indication of the fax transmission is not sent to the call agent, this field is set to 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.
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.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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
32 bit unsigned value in GMT epoch time format. The number of seconds since Jan 1,1970 0:00:00h.
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 is provisioned on. This field provides information on the locale of which the subscriber is a member. This information can also be leveraged for partitioning subscribers on a single BTS 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 Cisco BTS 10200 is provisioned on. This field provides information on the locale of which the subscriber is a member. This information can also be leveraged for partitioning subscribers on a single Cisco 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 Appendix D, "Time Zone Mapping Table" for the potential values.
Pop::Timezone, Timezone::Id
This is the point of presence that the originating subscriber on the Cisco BTS 10200 is provisioned into. This field provides information on the locale to which the subscriber is a member. This information can also be leveraged for partitioning subscribers on a single Cisco BTS 10200 into multiple business entities for billing purposes. LOCAL can be used if the POP is the same time zone as the reporting Cisco BTS 10200.
If this field contains a value of ZERO, then the timestamps within this record are based on the local time zone.
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, it is used; otherwise, the Cisco BTS 10200 internally generates it.
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 will always be in the length of 32 characters. If this field is NULL, no data was captured for this record.
143
(BTS Release 4.5.1, MR1 only)
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 "To" field on the terminating side for all outgoing SIP calls.
This field is populated only for SIP calls. 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 via 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. 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 is 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 is 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)
This field is always zero in this release.
n/a
The codec used to transport the RTP traffic. The value in this field is pulled from the provisioning of the Cisco BTS 10200 Softswitch, not from the actual SDP message.
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
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 via 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.
This is a future field for Release 5.0. 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. 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. 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 originating 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 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.
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
(BTS Release 4.5.1 only)
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
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>.
164
(BTS Release 4.5.1 only) (continued)
Call Subtype
Numeric
LB_TEST = 7
NLB_TEST = 8
RAILWAYS = 10
TIME = 11
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 value 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 value set in the Call Agent Configuration table.
164
(BTS Release 4.5.0 only)
Call Subtype
Numeric
TEST-CALL subtypes:
NCT-LINE-TEST = 14
NCT-TRUNK-TEST = 15
NLB-LINE-TEST = 16
NLB-TRUNK-TEST = 17
TEST-ROUTE = 18
EMG subtypes:
AMBULANCE = 1
FIRE = 2
POLICE = 3
INFO subtypes:
AIRLINES = 20
RAILWAYS = 21
TIME = 22
TRAFFIC = 23
TW (Time&Weather) = 24
WEATHER = 25
Destination:: CallSubtype
This defines the call based on the Call-Type field. In Release 4.5, only CallType= TEST-CALL populates this field. If the field contains a NULL, it is 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>.
NLB-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 value set in the Call Agent Configuration table.
164
(BTS Release 4.5.0 only)
(continued)Call Subtype
Numeric
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 value 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 7th 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:
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.
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.
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 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 or 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:
•
•
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 Ported NoA.
If this field is NULL, then no data was captured for this record.
171
(BTS Release 4.5.1 only)
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. If this field is NULL, then no data was captured for this record.
172
(BTS Release 4.5.1 only)
Unassigned
NA
ISUP Variants
This is an expansion field not used at this time but is allocated for additional ISUP variants.
173
(BTS Release 4.5.1 only)
Centrex Group
String
16
Up to a 16- character group name
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
(BTS Release 4.5.1 only)
Country Code
String
3
Numeric Characters
Intl_dial_plan:Padded_cc
3 numeric characters Automatically generated by ems if not provisioned
If 1 digic 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
