CS1500 AMA System

NTP 297-4102-124
Carrier Voice over IP

Communication Server 1500
Automatic Message Accounting System
For Release 02.00i Draft February 2009
February 2009 04.01 NTP 297-4102-124
For CS 1500
Copyright 2009 Nortel,
All Rights Reserved
Printed in the United States of America.
Nortel Publications: NTP 297-4102-124
Status: Draft
For Release 02.00i
Issue: 04.01
Date: February 2009
NTP 297-4102-124 04.01 February 2009
For CS 1500
ii
Publication history
Issue Date Rating For Release
01.01 J anuary 2008 Preliminary 01.00i
01.02 March 2008 Standard 01.00i
01.01 J une 2008 Standard 01.10i
03.01 October 2008 Draft 01.20i
03.02 December 2008 Standard 01.20i
04.01 February 2009 Draft 02.00i
February 2009 04.01 NTP 297-4102-124
For CS 1500
-iii
Contents
1 Introduction1-1
General description 1-1
LAMA / CAMA capability 1-1
AMA system capacity and reliability 1-1
Administration and maintenance 1-2
2 Hardware Description and Transfer Data Format
2-1
Hardware configuration 2-1
.Integrated Billing Storage and Retrieval (IBSR) format 2-2
Downstream processing 2-3
IBSR file header 2-4
3 AMA system characteristics and operation3-1
Processing of AMA Call Data 3-1
Call detail recording 3-3
AMA recording system 3-4
No-charge state 3-4
Usage sensitive billing 3-8
Data transmittal to downstream processing center 3-8
4 AMA system administration4-1
Introduction 4-1
Data modification order OAMP Programs 4-1
AMA system summary 4-3
Recording AMA data 4-5
AMA System Data Modification Orders 4-6
5 AMA system maintenance5-1
Introduction 5-1
Alarms 5-1
Trouble clearing 5-1
6 AMA record types6-1
Processing of AMA call data 6-1
Call types 6-1
AMA record types 6-1
Special studies 6-3
NTP 297-4102-124 04.01 February 2009
For CS 1500
-iv
7 ISDN(PRI) AMA7-1
ISDN PRI AMA recording (Bellcore format only) 7-1
8 Bellcore AMA record format8-1
Introduction 8-1
BAF Records CS1500 With/Without Module 8-1
Layout of BAF records: 8-2
Packed signed decimal encoding 8-3
Records in the charging data set 8-4
Data fields within records 8-7
Fields used only for call records 8-8
9 Bellcore structure codes9-1
Introduction 9-1
10 Index10-i
February 2009 04.01 NTP 297-4102-124
For CS 1500
1-1
Section 1: Introduction
1General description
The Automatic Message Accounting (AMA) system automatically collects and
records billing information on calls served by the CS 1500.
The AMA system consists of:
hardware components for collecting and storing AMA data
software instructions to control the processing of AMA call information,
including call classifying and collecting, formatting, and storing AMA
data
a method of operation using redundant recording systems to ensure reliable
capture and security of the raw AMA data which, in turn, is periodically
sent to a downstream processing facility for conversion to the operating
company's billing format.
1LAMA / CAMA capability
A CS 1500 switch equipped with the AMA system can function as either a Local
Automatic Message Accounting (LAMA) office or as a Centralized Automatic
Message Accounting (CAMA) office.
LAMA
As a LAMA office, the switch records locally originated, subscriber-dialed calls only.
Call recording is performed on an Automatic Number Identification (ANI) basis.
CAMA
As a CAMA office, the switch records locally originated calls an non-coin toll calls
originating in subtending class 5 offices. Call recording is performed on either an ANI
basis. .
1AMA system capacity and reliability
The AMA system can accommodate over 12,500 simultaneous calls requiring AMA
recording. Call-timing resolution is 1 second. The system is designed to provide
99.99% data capture reliability.
NTP 297-4102-124 04.01 February 2009
For CS 1500
1-2 Introduction
Storage capacity
The Core Controller (NT6T10) hard disk drive stores 28.6 million AMA records
1Administration and maintenance
Administrative control of the AMA system is provided through data modification
order (DMO) OAMP Programs. The OAMP Programs allow the user to manipulate
data specifying criteria for AMA call classification, billing treatment for each call
type, and AMA system data.
For a more detailed discussion of the DMO OAMP Programs relating to the AMA
system, see the section entitled, AMA System Administration in this NTP.
The administration and provisioning OAMP programs are described in NTP 297-
4102-311, Data Modification Manual. Refer to this NTP whenever a reference like
"DN (STN)", "CNFG prompting sequence", or "in TRNS" are made. This is also
referred to as the "DMO" OAMP group and "DMO" message classification.
Routine maintenance and trouble clearing procedures
Trouble clearing procedures and maintenance related activities of the AMA system
are described in the section entitled, AMA System Maintenance in this NTP.
February 2009 04.01 NTP 297-4102-124
For CS 1500
2-1
Section 2: Hardware Description and
Transfer Data Format
2Hardware configuration
The AMA system uses the Integrated Billing Storage and Retrieval configuration.
The Core Controller (NT6T10) Hard Disk Drives collect the records for the CS 1500
Data Server.
NTP 297-4102-124 04.01 February 2009
For CS 1500
2-2 Hardware Description and Transfer Data Format
2.Integrated Billing Storage and Retrieval (IBSR) format
The medium used to record data in the BAF format is the Core Controller Hard Disk
Drive. The data is recorded in directories on both HD1 and HD2. All AMA data is
located in the IBSR directory. Files that have not yet been transmitted to the AMA
collector are located in the primary subdirectory. Files that have been transmitted are
located in the secondary subdirectory. Within each primary and secondary
subdirectories the files are further organized into standard, test, and error files. Each
file contains header information followed by BAF formatted Billing Records
Figure 2-1: Directory tree of IBSR files
ibsr
/
/ \
primary
/ \
secondary
/ \ \
/ \
standard
error
test
\
/
/
standard
error
test
Hardware Description and Transfer Data Format 2-3
February 2009 04.01 NTP 297-4102-124
For CS 1500
2Downstream processing
Facilities for IBSR billing
The AMA data stored on the CS 1500 Data Server must be sent to a downstream
processing facility that can process the AMA data into billing information for the
operating company.
The downstream processing facility may include the ability to FTP into the CS 1500
when the AMA files are pulled from the CS 1500 Data Server. The downstream
facility may also allow the CS 1500 to FTP the AMA data information to the AMA
collector when the AMA billing data is sent according to its configured schedule. At
least one of these methods must be available to transfer AMA records to the AMA
collector.
IBSR file content
Each IBSR file has a file header describing the file which is followed by billing
records as shown in Figure 2-3.
Figure 2-2: IBSR file
File Header
BAF Record
BAF Record
BAF Record
BAF Record
File Header
Billing Records
NTP 297-4102-124 04.01 February 2009
For CS 1500
2IBSR file header
The IBSR file header format is shown in Figure 2-4 and described in Table 2-D.
Figure 2-3: IBSR File header format
High-order Bit Low-order Bit
Byte 7 6 5 4 3 2 1 0
1 File Header Length
2 Source Component Identification Number
3 Source Component Type Source Component Identification Number
4 Destination Component Identification Number
5 Destination Component Type Destination Component Identification Number
6 File Type Data Format Type
7 Field Suppression
Type
File Priority Level Restart
Status
Pri/Sec
Status
Record
Source
Info Type
8-9 File Sequence Number
10 File Creation Type
11 File Creation Date File Creation Time
12-13 File Creation Date
14 File Last Modification Time
15 File Last Modification Date File Last Modification Time
16-17 File Last Modification Date
18-21 File Length
22-24 Number of Records in File
25 Record Source Type
26 Record Source Identification Number Record Source Type
27-28 Record Source Identification Number
February 2009 04.01 NTP 297-4102-124
For CS 1500
Table 2-A:
IBSR File Header definitions
Header Format Field Description of Field Names
File Header Length The size of the file header. This is always set to 28.
Source Component
Identification Number
Unique 4-digit identifier of the office generating the AMA data.
Source Component Type Identifies the type of office generating the AMA data. This is always a
Data Server type.
Destination Component
Identification Number
Unique 4-digit identifier of the site receiving the AMA data from the CS
1500.
Destination Component Type Identifies the type of office generating the AMA data. This value is
always set to DPMS type.
File Type Indicates the type of data contained in within the AMA DNS file. The
possible types are Standard, Error, and Test data.
Data Format Type Indicates the format of the data contained in the file. This is always
BAF data type.
Field Suppression Type Indicates the type of BAF record suppression used on the data in the
AMADNS file. Possible suppression types are no suppression, two-
field suppression, and four-field suppression. Default setting is no
suppression.
File Priority Level Indicates priority of file. Not currently used. Will always be set to 2
(Default Level).
File Sequence Number Restart
Status
Indicates whether the file sequence numbering was restarted for some
reason.
Primary/Secondary Status Indicates whether the file is a primary or secondary file.
Record Source Information
Type
Indicates the generating system type that created the file. This is
always Traditional sensor information.
File Sequence Number Indicates order in which file was created.
File Creation Time Indicates the time of day the file was created.
File Creation Date Indicates the date the file was created.
File Last Modification Time Indicates the time of day the file was last modified.
File Last Modification Date Indicates the date the file was last modified.
File Length Indicates the size of the file (in bytes) not including the file header.
Number of Records in File Indicates the number of BAF records that are in the file.
Record Source Type Indicates the type of component that created the AMA records. A 0
indicates that the Record Source Identification Number is traditional
sensor information (e.g., from BAF records). A 1 indicates that the
information is a AMADNS Source Component ID Number.
Record Source Identification
Number
A 6 digit number in the traditional or AMADNS-specific format.
NTP 297-4102-124 04.01 February 2009
For CS 1500
Record structure
Each record consists of the following elements:
record descriptor word-The first two bytes contain (in binary) the length of
the record; the second two bytes are zeros.
hexadecimal identifier-One byte long, its value is Hex AA if there is no fill
character in the rest of the record; its value is Hex AB if there is any fill
character.
structure code-This defines the structure of the rest of the record data. For
each structure code, there is a unique sequence of data fields. The data
fields always appear in a defined order; that is, if field A precedes field B
in one structure code, then it will precede field B in all structure codes.
the remainder of the record data-encoded as Packed Signed Decimal
Numbers
Packed signed decimal encoding
Each piece of record data (except the record descriptor word and the hexadecimal
identifier) is recorded as a packed signed decimal number. A given piece of record
data corresponds to an individual data field, such as a structure code, call-type code,
and so on. A packed signed decimal number consists of binary coded decimals
(BCDs) followed by a four-bit sign character. Each data field, therefore, fills up entire
eight-bit bytes. For each data field, the most-significant BCD appears in the left half
of the first byte, and the sign character appears as the right half of the last byte.
There are two sign characters: a positive sign and a negative sign. The positive sign
is coded as Hex C and is appended to a field that contains no fill character (Hex F).
The negative sign is coded as hex D and is appended to a field that contains
incomplete or incorrect data and at least one fill character. A field that is intentionally
not used has a fill character in every position, including the field's sign position.
February 2009 04.01 NTP 297-4102-124
For CS 1500
For the complete list of BCD codes, see Table 2-B.
Table 2-B:
BCD encoding
Data Code in hexadecimal
0 0
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9
Positive sign C
Negative sign D
Fill character F
NTP 297-4102-124 04.01 February 2009
For CS 1500
February 2009 04.01 NTP 297-4102-124
For CS 1500
3-1
Section 3: AMA system characteristics
and operation
3Processing of AMA Call Data
The AMA system provides automatic recording of AMA information in detailed
format. Detailed AMA and administrative information is provided through call detail
recording (CDR), which uses call processing software and billing registers to record
the data. CDR data is written to both Core Controller Hard Disk Drives.
Charge determination
When a subscriber goes off-hook at a station, the switching system examines the data
associated with that station's directory number to determine its class of service (COS)
(flat rate, message rate, or coin rate) and thousands group (THGP). The THGP data
are used to determine the Rate Center (RC) in which the call is originating. The RC
data will be used to determine if the call is toll or local.
As the subscriber dials, digit translation of the called party address information
begins. During the translations process, the system determines the THGP of the called
party (for intra-exchange calls) or the Destination (DEST) of the call (for inter-
exchange calls). The Toll Region (TR) associated with the THGP of the called party
or the DEST is then used to select the appropriate Message Rate Treatment Index
(MRTI). On the basis of this information, the system determines whether the call is
billable or free of charge.
If the call is free of charge, it is completed to the destination without further
involvement of the AMA system.
NTP 297-4102-124 04.01 February 2009
For CS 1500
3-2 AMA system characteristics and operation
Call classification
Call classification occurs at the end of digit translation and is based on one or more of
the following:
type of prefix digit(s) dialed-DDD access digits, etc.
translation through a call type action statement in prefix translation-used
with the digit substitution (DSUB) action statement to specify a call as an
OUTWATS (OWAT) call
the results of a toll test in screening-The test uses the call originator's local
calling area and the call terminator's toll region to determine whether a call
is toll or toll-free.
the call type specified for routes-At the end of translation, any call not
terminating on a line within the office terminates on a route. Where
applicable, the route data specify what type(s) of AMA call are carried by
the route.
Billing control
After a call is marked as an AMA call of a particular type, call processing consults a
billing-control table to determine whether the call is:
billable and, if so, the billing treatment to be given that call type
message rate and whether it is timed or untimed
a special study call and, if so, what type (Traffic Sampled Study,
Subscriber Line Usage Study, etc.)
MDR and, if so, the type of MDR required
There is a separate AMA billing-control table entry maintained for each AMA call
type.
Calling number identification
After call-processing determines a call is billable, the calling party directory number
is collected using either Automatic Number Identification (ANI) in the CS 1500 or the
call is routed to an Operator Service Center for Operator Number Identification (ONI)
and billing at the Operator Service Center.
ANI (LAMA and CAMA)
The ANI sequence is initiated for incoming (CAMA) calls when the incoming trunk
group data indicates an ANI spill. For locally originated (LAMA) calls from non-ONI
subscribers, the calling number is obtained directly from the subscriber's station data.
AMA system characteristics and operation 3-3
February 2009 04.01 NTP 297-4102-124
For CS 1500
A billing register is seized and linked to the call-register/device-register list for the
call. The billing register stores the calling party number and other data required to
make a record of an AMA call. For LAMA calls, the calling number is obtained
directly from the calling party's station data. For CAMA calls, an ANI-request signal
is sent over the incoming CAMA trunk to the subtending office. The signal may be
either a wink or a continuous off-hook. After receiving the calling party digits, the call
is routed or terminated according to the called digits. The billing register remains
linked to the register list for the duration of the call.
Note: If the call is an untimed message-rate call, the AMA record is
completed on answer and the billing register released.
3Call detail recording
Call detail recording (CDR) uses the call processing software to provide detailed
charging and administrative information. CDR may be used in a Local or Transit
Exchange to record information for coin or non-coin billable calls.
Call detail recording operation
CDR operates as described in this section under the heading AMA system
operation. During initial call processing, the called party's TR or DEST is used to
select the appropriate MRTI. A maximum of 64 TRs may be defined in an exchange,
and one or more TRs may be assigned to an MRTI. The MRTI specifies call
treatment, that is, the Message Billing Index (MBI) to be used and whether the call is
untimed (fixed charge) or timed. A maximum of 62 MRTIs may be assigned to an
exchange. The TR is used to determine if a timed call will be charged the local or toll
rate.
Data storage
As indicated in the description of charging operation, charging data are stored in a
billing register. When a billable AMA call disconnects, the contents of the billing
register are transferred to a data buffer in protected Call Store which holds up to 48
AMA data entries. The data contained in the buffer is reformatted into an IBSR data
entry.
When the buffer is full of IBSR AMA data, the data block is transferred to the CS
1500 Data Server. The CS 1500 Data Server will then write the AMA data to the Core
Controller Hard Disk Drives for storage until they are transferred via FTP to the AMA
collector.
NTP 297-4102-124 04.01 February 2009
For CS 1500
3AMA recording system
The CS 1500 Data Server AMA system provides full redundancy to ensure the
capture and preservation of billing data.
IBSR redundancy
The CS 1500 Data Server will write the billing data to both Hard Disk Drives. If one
of the Hard Disk Drives is unavailable, the data will be written to the other Hard Disk
Drive and copied to the unavailable disk when it become available. If both Hard Disk
Drives are unavailable, the CS 1500 Data Server will buffer the data until one or both
of the Hard Disk Drives becomes available. The CS 1500 Data Server can buffer up
to 8 MB of billing data.
3No-charge state
During the following abnormal conditions, the system enters a no-charge state:
System Reload
System Reset
Time-of-Day (TOD) clock faults (i.e., AMA system down)
No billing registers available
When the system is in a no-charge state, special treatment is required for billable calls.
The paragraphs that follow describe the various special treatments that are given to
subscriber and coin line calls that originate before or during a no-charge state initiated
by each of the abnormal conditions listed above.
System Reload
Most calls that are connected before the System Reload retain their speech paths, but
all other call information, including billing registers, is lost. The special treatments for
calls that originated before the System Reload are:
Subscriber Call. Because of the loss of the billing register associated with
the call, the entire call is free of charge. The only exception is a Long-
Duration Call (LDC) originated by a subscriber. Because the charging
record of a subscriber line involved in an LDC is updated daily at
midnight, any portion of an LDC up to the midnight immediately
preceding the System Reload is billed normally. The portion of an LDC
from the last midnight update to disconnect is free of charge
Coin Line Call. Because the appropriate billing register associated with a
coin line is updated upon the collection of credit, all periods up to and
including the period during which the System Reload occurs are charged
normally. The loss of the call's billing register, however, requires that the
rest of the call be free of charge
February 2009 04.01 NTP 297-4102-124
For CS 1500
The system automatically exits the no-charge state upon completion of the System
Reload, except under the following conditions:
First System Reload. After the System Reload that occurs when the system
is first placed in service, the system will remain in a no-charge state until
the TOD clocks are set via the appropriate Resident Commands. For these
commands, see the Resident Commands section in the NTP entitled
Maintenance Diagnostic Input Manual (297-4102-506)
Double TOD Clock Faults. If both TOD clocks are faulty upon completion
of the System Reload, the system will remain in a no-charge state until at
least one of the TOD clocks is manually cleared of faults, tested, and reset.
For more information, see below under the subheading TOD Clock
Faults
System Reset
A System Reset lasts approximately 10 to 30 seconds. During this time, no calls can
be originated and routed, but any signals sent to the switching system (such as on-
hooks and off-hooks) are detected and then processed after the System Reset.
System Reset normally does not result in a loss of billing registers. Billing registers
are reattached to the established billable calls after System Reset. For charging on a
given call to continue after System Reset, that call must have had a billing register
before System Reset.
The special treatments for established calls that have billing registers attached at the
time of an System Reset are:
Subscriber Call. The portion of a subscriber call that occurs during System
Reset is free of charge, including that portion of a call that is disconnected
by the subscriber during System Reset. Normal charging continues
immediately after System Reset. A subscriber can be undercharged by up
to 2 seconds for the complete call. This can occur because every 2 seconds
the system saves the value of the clocks that are used to calculate
conversation time. These clocks are tested and zeroed during System
Reset.
Coin Line Call. The portion of a coin line call that occurs during System
Reset is free of charge, including that portion of a call that is disconnected
by the subscriber during System Reset.
In some rare instances, System Reset is triggered either by a special type of memory
fault or by a Data Modification Order (DMO) change that requires reallocation of
system memory. In these instances, billing registers are lost. Should this type of loss
occur, the treatments given to subscriber and coin line calls are the same as those
given to calls affected by a System Reload (see above).
NTP 297-4102-124 04.01 February 2009
For CS 1500
The system automatically exits the no-charge state upon completion of the System
Reset, except when both TOD clocks are faulty. If this occurs, the system will remain
in a no-charge state until at least one of the TOD clocks is manually cleared of faults,
tested, and reset. For more information, see below under the subheading TOD Clock
Faults.
TOD clock faults
The system has three clock sources: one calendar-clock source (the software clock)
and two calendar/time-counter clock sources, which are called the Time-of-Day
(TOD) clocks. The system periodically checks to ensure that the software-clock
calendar and the two TOD-clock calendars agree and that the two TOD-clock time
counters agree. The TOD-clock time counters are used in determining conversation
time for subscriber calls.
In order to charge subscriber calls, the system must have at least one correctly
functioning TOD clock. If the system determines that one TOD clock is faulty, a
minor alarm message is displayed at the maintenance terminal(s), and the system uses
the other TOD clock for subscriber charging. If the system finds that the other TOD
clock is faulty before the first TOD clock is repaired and returned to service, then a
major alarm message is displayed at the maintenance terminal(s), and the system
enters a no-charge state. Such a double TOD-clock fault is extremely rare, since it
requires that double hardware, software, or hardware/software faults occur within a
very short period of time.
A double TOD-clock fault does not, in itself, prevent subscribers from originating
calls. Thus, the special treatments differ for calls that originated before the no-charge
state and those that originate during the no-charge state. The special treatments are:
Subscriber Call Originated Before No-Charge State. A subscriber call that
originated before the system entered the no-charge state is completely free
of charge. The only exception is a Long Duration Call (LDC) originated by
a subscriber. Because the billing register of a subscriber line involved in an
LDC is updated daily at midnight, any portion of an LDC up to the
midnight immediately preceding the second TOD clock fault is billed
normally. The portion of an LDC from the last midnight update to
disconnect is free of charge
Subscriber Call Originating During No-Charge State. The operating
company can specify the charging treatment to be given to each type of
subscriber call that originates during a no-charge state. The options that
can be specified via DMO are:
- Allow the call to proceed completely free of charge. (If a call is allowed to begin
free of charge, then no billing register is attached to the call; thus, charging cannot
begin after restoral of a TOD clock)
- Specify a route (for example, Busy Tone) to be taken by such calls
February 2009 04.01 NTP 297-4102-124
For CS 1500
- Specify that the call be routed on the same route used for ANI-fail (ANIF)
calls
Coin Line Call Originated Before No-Charge State. The portion of this
type of call that occurred before the system entered the no-charge state is
charged normally. Because a different timing source is used for coin
collection pulsing, the system can continue coin line charging during this
type of no-charge state. However, loss of the TOD clocks means that the
accuracy of the calendar time that is used to determine the applicable tariff
rate cannot be guaranteed. Thus, the portion that occurred during the no-
charge state and up to disconnect is charged at the minimum tariff rate
Coin Line Call Originating During No-Charge State. For the reasons stated
above, the entire call is charged at the minimum tariff rate
The system automatically exits a no-charge state caused by a double TOD clock fault
when operating company personnel have:
Started OAMP Program Control Equipment Diagnostic (CED) and
successfully busied, tested, and returned to service one of the TOD clocks
Set the correct date and time on the TOD clock via the appropriate
Resident Commands
Started Alarm OAMP Program (ALO) and cleared the major alarm
condition
The commands necessary to perform these actions are explained in the NTP entitled
Maintenance Diagnostic Input Manual (297-4102-506). A step-by-step procedure for
repairing TOD clock faults is contained in the NTP entitled Maintenance and Test
Manual (297-4102-511).
No billing registers available
If a billing register cannot be attached to a billable call because all available billing
registers are being used by active calls, the system enters a no-charge state. Such an
occurrence is extremely rare, since there should be at least as many billing registers
as there are available call registers. However, because billable calls using various
calling features (Call Forwarding, usage-sensitive billing features) require more than
one billing register, a no-charge state caused by the unavailability of billing registers
is theoretically possible.
An impending no-charge state caused by the unavailability of billing registers is
indicated by a message displayed at the maintenance terminal(s) reporting that the low
percentage threshold for billing register availability has been passed. (This threshold
is specified in CNFG (BUFF); see the NTP entitled Data Modification Manual [297-
4102-311].)
NTP 297-4102-124 04.01 February 2009
For CS 1500
Repeated no-charge states caused by the unavailability of billing registers indicate
that more billing registers should be allocated in the system. This operation is
performed in CNFG (AMA) (see the NTP entitled Data Modification Manual [297-
4102-311]). The number of billing registers allocated in the system should be a
function of the percentage of the number of billable calls expected in the traffic load
at a given time.
The unavailability of billing registers does not, in itself, affect call originations. Thus,
the special treatments differ for calls that originated before the no-charge state and
those that originate during the no-charge state. The special treatments are:
Subscriber Call Originated Before No-Charge State. Charged normally
Subscriber Call Originating During No-Charge State. The operating
company can specify the charging treatment to be given to each type of
subscriber call that originates during a no-charge state. The options that
can be specified via DMO are:
- Allow the call to proceed completely free of charge. (If a call is allowed to
begin free of charge, then no billing register is attached to the call, and one
cannot be added to an established call; thus, normal charging for such a call
cannot begin after a billing register becomes available)
- Specify a route (for example, Busy Tone) to be taken by such calls
- Specify that the call be routed on the same route used for ANI-fail (ANIF)
calls
Coin Line Call Originated Before No-Charge State. Charged normally
Coin Line Call Originating During No-Charge State. Charged normally,
but no billing register is attached
The system automatically exits the no-charge state when one or more billing registers
become available to service a billable call origination.
3Usage sensitive billing
Usage sensitive billing (USB) provides the ability to charge subscribers for specific
actions related to custom calling features and CLASS features. The office must first
be configured with usage sensitive features.
3 Data transmittal to downstream processing center
Detailed or bulk charging data must be sent to the downstream processing center for
conversion into the actual bills that are sent to subscribers. IBSR billing data is
transferred via FTP to the downstream processing center.
For information on downstream processing and the format used to record charging
data, see the section entitled Hardware Description and Transfer Data Format.
February 2009 04.01 NTP 297-4102-124
For CS 1500
4-1
Section 4: AMA system administration
4Introduction
This section describes the AMA system operation and corresponding Data
Modification Order (DMO) OAMP Programs used for administrative control of the
AMA system.
4Data modification order OAMP Programs
The paragraphs that follow describe the various Data Modification Order (DMO)
OAMP Programs that provide administrative control of the operational parameters of
the AMA system. These OAMP Programs allow the user to manipulate data that
specify:
Criteria for billable call classification
AMA treatment for each call type
Other data related to the AMA system
For the actual prompting sequences used to modify the parameters of the AMA
system operation that are discussed in this section, see the NTP entitled Data
Modification Manual (297-4102-311).
NTP 297-4102-124 04.01 February 2009
For CS 1500
4-2 AMA system administration
Figure 4-1: AMA system administration
Terminating
Line
DN(STN)
THGP(THGP)
AREA(RTP)
AMA(MRTI)
Translations
Originating
Line
THGP(THGP)
CNFG(AMA)
RTP COS TR
RC
IT/IP/ITRS
OT/OP/OTRS
BILLING
RATE
MRTI
ROUT(DEST)
Incoming
Trunk or
TG(TG)
or
Outgoing
Trunk
RC RTP COS
CDR AMA(MTU)
AMA system administration 4-3
February 2009 04.01 NTP 297-4102-124
For CS 1500
4AMA system summary
This summary follows, in greater detail, the AMA system operation summarized in
figure 4-1.
Charge determination
As the subscriber dials, digit translation of the called party begins. During the
translations process, the system determines the THGP of the called party (for intra-
exchange calls) or the Destination (DEST) of the call (for inter-exchange calls). The
Toll Region (TR) associated with the THGP or the DEST is then used to select the
appropriate Message Rate Treatment Index (MRTI). A call's charge rate is determined
after the subscriber dials a sufficient number of digits to allow call translations to
identify the termination.
After call translation, the system examines the data associated with a calling station's
directory number to determine its class of service (COS) (flat rate, message rate, or
coin rate) and thousands group (THGP). The THGP data are used to determine the
Rate Center (RC) in which the call is originating.
Figure 4-2 shows the AMA charge determination structure of OAMP Programs DN,
THGP and AREA. In this example originating subscriber DN 555-1234, is assigned
Rate Center 3, with message-rate residential service and Rate Treatment Package 1.
NTP 297-4102-124 04.01 February 2009
For CS 1500
Figure 4-2: Charge Determination
DN(STN)
555-1234
THGP
(RC3)
AREA(RTP)
555-1
RC0 RC1 RCx RCx RCx RCx RC60 RC61
RTP0 RTP1 RTP2 RTP3
LOCL TR
MRTI
FR MR MB COIN
February 2009 04.01 NTP 297-4102-124
For CS 1500
Call classification
If the call is billable, the called number must be classified, based on one or more of
the following:
Type of prefix digit(s) dialed: DDD access digits, etc.
Translation through a call type action statement in prefix translation:
used with the digit substitution (DSUB) action statement to specify the
type of call.
The results of a toll test in screening: the test uses the call originator's
local calling area and the call terminator's toll region to determine whether
a call is toll or toll-free.
The call type specified for routes: at the end of translation, any call that
does not terminate on a line within the exchange terminates on a route.
Where applicable, the route data specify what type(s) of billable call are
carried by the route.
After call-processing determines that a call is billable, the calling party directory
number is collected using either Automatic Number Identification (ANI) in the CS
1500 .
ANI (locally originated and subtending local exchange calls)
ANI is a method used to identify a calling station for billing purposes and is used for
locally originated calls from non-ONI subscribers. The ANI sequence is initiated for
calls from a subtending Local Exchange when the incoming trunk group data
indicates an ANI spill. ANI automatically forwards the billing number to the AMA
subsystem.
A billing register is seized and linked to the call register for the call. The billing
register stores the calling number and other data required to make a record of a billable
call. For locally originated calls, the calling number is obtained directly from the
calling party's station data. For subtending Local Exchange calls, an ANI request
signal is sent over the incoming trunk to the subtending exchange. The signal may be
either a wink or a continuous off-hook. For ISUP trunks, this information may be
included in the IAM message or requested by an INR. After receiving the calling
digits, the call is routed or terminated according to the called digits. The billing
register remains linked to the call register for the duration of the call.
Note: If the call is an untimed message-rate call, the AMA record is
completed on answer and the billing register released.
4Recording AMA data
After the call is answered, (when the off-hook signal of the called party is received by
the CS 1500), the answer time and date and associated AMA data are recorded in the
billing register associated with the call. The method used for calculating AMA data is
Call Detail Recording (CDR).
NTP 297-4102-124 04.01 February 2009
For CS 1500
Call detail recording operation
Call detail recording (CDR) uses the call processing software to provide detailed
AMA and administrative information. CDR may be used in a Local or Transit
Exchange to record information for coin or non-coin billable calls.
A terminating party's TR (toll region) is used to determine if a timed call placed from
the originating party should be charged local or toll rate. During initial call
processing, the called party's TR is determined differently for inter-exchange calls
and for intra-exchange calls. For inter-exchange calls, the TR is determined from the
DEST defined for a terminator routing out of the CS 1500. For intra-exchange calls,
the TR is determined from the terminating line's THGP. A maximum of 64 TRs may
be defined. One or more TRs may be assigned to a MRTI. The MRTI specifies call
treatment, that is, the Message Billing Index (MBI) to be used and whether the call is
untimed (fixed charge) or timed. A maximum of 62 MRTIs may be assigned to an
exchange.
4AMA System Data Modification Orders
The data modification orders (DMO) listed in this section are also referenced in figure
4-1.
Directory number (DN)
Line origination billing administration starts at the originating subscriber's station.
Billing information is first derived from data defined by DN (STN). This data
provides the originating subscriber's rate treatment package (RTP) number and class
of service (COS). An RTP contains data regarding the caller's local calling area, COS
and message billing index. RTPs are contained in Rate Centers (RC) (defined in
AREA (RTP/RC)).
Thousands group (THGP)
OAMP Program THGP is the second OAMP Program accessed during line
origination AMA administration. A thousands group is the first four digits of the
subscriber's five- to seven-digit directory number. THGP defines the originating
subscriber's RC and the terminating subscriber's Toll Region (TOLL). RCs are
defined in AREA (RC). An RC is an attribute of the originating line or incoming
trunk. The switching system uses the RC to determine the originator's location and
contains the RTP used to define the originator's billing characteristics. Each
thousands group (THGP) and each incoming trunk group (INC) in the system is
assigned to an RC. It is used by the switching system to determine whether a call
should be given local or toll treatment. The terminating TOLL is an attribute of the
destination of the call. The switching system uses TOLL to determine whether a call
should be given local or extended local treatment.
A maximum of 64 TRs can be defined. Each thousands group (THGP) in the system
and each destination (DEST) outside the system are assigned to a toll region.
February 2009 04.01 NTP 297-4102-124
For CS 1500
Area (AREA)
OAMP Program Area defines call originator and call terminator characteristics. These
characteristics include the subscriber's rate center (RC), rate treatment package
(RTP), and toll region (TR). Each CS 1500 system can service up to 62 RCs. Each RC
can support up to four RTPs for each of the following class of service types: Coin, Flat
rate, Message-rate residential, and Message-rate business. This permits up to 16 RTPs
to be defined for each RC.
An RTP is an attribute of the originating line or incoming trunk. The RTP defines the
originator's rate treatment for calls to destinations in any of the Toll Regions (TRs)
(see note). The originator's RTP is checked to determine the call class of service
(Coin, Flat rate, Message-rate residential, and Message-rate business). For Flat rate
calls, TRs that can receive toll-free calls are specified. For Message-rate and Coin
calls, the MRTI and applicable TRs are specified.
For incoming trunk groups, the class of service (MR, FR) is derived by the traffic
class setting. Combined toll/local and CAMA trunk groups are treated as message rate
and all other trunk groups are treated as flat rate.
The message rate treatment index (MRTI) is used by the AMA system to determine
billing. Multiple TRs can be assigned to each MRTI. The MRTI defines the Message
Billing Index (MBI) code to be used for Regional Accounting Office accounting,
allows message rate treatment for calls without MBI, and indicates whether the call is
timed or untimed (fixed-charge). A maximum of 62 MRTIs can be defined in the
switching system. Each TR is associated with an MRTI. Each MRTI contains one to
three rate periods. A TR assignment to a flat rate (FR) COS prevents AMA from
billing the flat rate call made to that TR. If no TR assignment exist, AMA bills FR
calls made to all TRs.
Note: OAMP Program THGP abbreviates Toll Region as TOLL, while
OAMP Program AREA abbreviates Toll Region as TR.
Translations (TRNS)
OAMP Program Translations (TRNS) is used to define the tests and resulting actions
that are in the address, prefix, and screening translators. The information in these
translators is used to determine the path of a call. Prefix and screening translators have
tests and actions that pertain to the AMA system.
Prefix translator (PRFX) prompting sequence
This prompting sequence contains a test to determine the originator's Rate Center and
an action that will direct the call based on the AMA call type.
Screening translator (SCRN) prompting sequence
This prompting sequence contains tests to determine the originator's call type (coin or
message rate) and Rate Center, whether the originator's station has the toll denial
feature, and if the call is a toll call.
NTP 297-4102-124 04.01 February 2009
For CS 1500
Automatic message accounting (AMA)
OAMP Program Automatic Message Accounting (AMA) defines system data that is
used in the processing of billable calls. This data is initially entered (or changed at a
later time) using the prompting sequences in AMA, which are described in the
paragraphs that follow.
Message rate treatment index (MRTI) prompting sequence
This prompting sequence is used to configure the Message Rate Treatment Index that
was specified earlier in the billing cycle through AREA (RTP). For each MRTI, the
call treatment is defined to indicate whether a Message Billing Index (MBI) should
be associated with the call. An MRTI must be defined to provide an index into the
Message Billing Indices; that is, to assign the appropriate MBI code to be used for
Regional Accounting Office (RAO) accounting. An MRTI also defines whether the
call is to be timed (charge units may be calculated continuously for the duration of the
call) or untimed (a fixed charge is associated with the call); and allows for message-
rate treatment of calls if the RAO does not have MBI.
Configuration record (CNFG)
The Configuration Record (CNFG) contains data that pertain to AMA system
equipment, as well as system data that are used in the processing of billable calls.
These data are initially entered or changed at a later time through the Configuration
Record prompting sequences that are described in the following paragraphs.
Automatic message accounting (AMA) prompting sequence
This prompting sequence is used to specify the following parameters:
Whether or not the switching system is to record AMA data and, if so, the
billing method or methods and the types of calls for which they will be
used
The type of exchange (local or transit)
The number of billing registers that are to be allocated to handle billable
calls originated by all subscribers
The Sensor Identification number
A determination if bulk billing is required for message-rate business
billing
For transit (CAMA) office, the code used by the CAMA operator to report
trouble
Suppression Method when saving records to disk
Call processing (CP) prompting sequence
This prompting sequence specifies the following information that is used in call
processing and affects the AMA system configuration:
The total number of Rate Centers served by the switching system
February 2009 04.01 NTP 297-4102-124
For CS 1500
Generic condition (GCON) prompting sequence
This prompting sequence specifies the treatment given to billable calls when the call-
processing logic detects one of the following conditions (listed in alphabetical order):
AMA Down (AMAD) - A record of the call cannot be made because the
charge recording system is malfunctioning
Automatic Number Identification Failure (ANIF) - The ANI test has failed
to identify the calling number
No Billing Register (NBR) - A record of the call cannot be made because
no billing register is available
Integrated Billing Storage and Retrieval (IBSR) system
prompting sequence
This prompting sequence is used to specify the following parameters:
The CS 1500 Data Server Component ID Code
Data Processing Management System Component ID code
Record Source Identification Type
The maximum file size in bytes
The maximum file size in records
Minor alarm time age limit
Major alarm time age limit
FTP minor alarm authentication threshold
FTP major alarm authentication threshold
Error record minor alarm threshold
Error record major alarm threshold
File transfer mode (PUSH/PULL)
The primary IP address to use when AMA files are transferred to the AMA
collector via a schedule
The TCP port for the FTP control session in the AMA collector when using
the primary IP address
The directory path to where the AMA files should be located when they are
transferred using the primary IP address to the AMA collector via a
schedule
The User ID to use when FTPing AMA files to the primary IP address
The password to use when logging into the AMA collector when FTPing
AMA files to the primary IP address
NTP 297-4102-124 04.01 February 2009
For CS 1500
The alternate IP address to use when AMA files are transferred to the
AMA collector via a schedule
The TCP port for the FTP control session in the AMA collector when using
the alternate IP address
The directory path to where the AMA files should be located when they are
transferred using the alternate IP address to the AMA collector via a
schedule
The User ID to use when FTPing AMA files to the alternate IP address
The password to use when logging into the AMA collector when FTPing
AMA files to the alternate IP address
The number of times to retry the transfer of an AMA file to the AMA
collector
The amount of time that should be waited between attempts to transfer an
AMA file to the AMA collector
The level of alarm (catastrophic, major, minor, none) that should be raised
if an AMA file cannot be transferred to the AMA collector
Up to 24 schedule times for the CS 1500 Data Server to transfer AMA data
to the AMA collector
Office data query (ODQ)
OAMP Program Office (Exchange) Data Query (ODQ) is used to obtain a list of
specific types of exchange data.
Counts (CNTS) prompting sequence
This prompting sequence is used to list the number of stations with one or more
specified options.
Directory number (DN) prompting sequence
This prompting sequence is used to list the directory numbers and associated data for
those directory numbers that have one or more specified options.
Storage (STOR) prompting sequence
This prompting sequence is used to list the amount of disk storage used and available
to the system for storing billing data for the IBSR and TGMU configured systems.
Route (ROUT)
OAMP Program ROUT is used to define call routing.
Connection (BCON/CONN/DCON) prompting sequence
These prompting sequences are used to establish and maintain dedicated,
semipermanent connections.
February 2009 04.01 NTP 297-4102-124
For CS 1500
Destination (DEST/TR) prompting sequence
These prompting sequences are used to define the called number's Toll Region (TR).
Route (BRTE/ROUT/RSEL) prompting sequence
These prompting sequences are used to define individual routes.
Trunk group (TG)
The Trunk Group (TG) prompting sequence within OAMP Program TG is used to
define the characteristics of incoming, outgoing, and two-way trunk groups. The
following AMA system parameters are defined for incoming and two-way trunk
groups:
The Rate Center (RC) and Rate Treatment Package (RTP) that are
associated with the trunk group (these are used to indicate to the AMA
system which AMA table is to be applied to calls over the trunk)
The trunk group traffic class, which pertains to the distance between the
two exchanges
The Local Exchange codes that can be used for incoming AMA traffic
For outgoing trunk groups, the trunk group traffic class, which pertains to the distance
between the two exchanges, is the only AMA parameter defined by prompting
sequence TG.
The Trunk Group (TG) prompting sequence is also used to define whether the Trunk
Group Member Usage (TGMU) data records should be generated for the trunk group.
This parameter is defined for incoming, outgoing, and two-way trunk groups.
NTP 297-4102-124 04.01 February 2009
For CS 1500
February 2009 04.01 NTP 297-4102-124
For CS 1500
5-1
Section 5: AMA system maintenance
5Introduction
This section describes the maintenance-related activities associated with the AMA
system. These activities include:
Alarms
Trouble clearing
5Alarms
The system activates alarms and displays alarm messages for the following AMA
system conditions:
A memory fault that affects Protected Call Store
The system detects a fault in the inactive Core Controller Real Time Clock
Hard Disk Drive faults.
IBSR file age exceeds limit.
Number of IBSR error records exceeds limit.
Space used by primary IBSR file exceeds limit.
CS 1500 Data Server not available.
5Trouble clearing
The primary aids to operating company personnel in analyzing and clearing troubles
in the charge recording system are two diagnostic programs: Common Equipment
Diagnostic (CED) and Input/Output Diagnostic (IOD).
Common equipment diagnostic (CED)
If the Real Time Clock (RTC) on the active Core Controller is found faulty, the Core
Controller will switch to the "good" redundant Core Controller and report the fault.
The Common Equipment Diagnostic (CED) OAMP Program is used to test the RTC
on the inactive Core Controller. Core Controllers are switched routinely so that
complete inactive testing can be completed on both Core Controllers.
NTP 297-4102-124 04.01 February 2009
For CS 1500
5-2 AMA system maintenance
Trouble messages
Troubles detected by CED, IOD, or the CS 1500 Data Server are indicated by
messages printed out at a maintenance terminal in the form CEDxxx, IODxxx,
DMONxxx, or IBSRxxx where xxx is a variable representing any one of a series of
unique numeric codes and the specific trouble-clearing procedures associated with
each code, each of which indicates a specific trouble in the system. For the meanings
of these codes, and the specific trouble-clearing procedures associated with each
code, see the Output Message Manual.
February 2009 04.01 NTP 297-4102-124
For CS 1500
6-1
Section 6: AMA record types
6Processing of AMA call data
In a CS 1500 switch equipped with the AMA recording system, call-processing
software examines each call and determines whether it is an AMA call and, if so,
which of the types of AMA call it is.
6Call types
During call processing, a call is identified by its call type. After a billable call is
disconnected, the data in the associated billing register are reformatted into an AMA
billing entry. The reformatted call information contains a call-type code, which
identifies the call.
6AMA record types
AMA records include miscellaneous and statistical entries (used for administrative
purposes) and AMA call entries (used to record details of billable calls).
Long-duration call AMA records
For each call in progress beyond a second midnight, at the second midnight and at
each subsequent midnight until the call is taken down, a Long-Duration Call (LDC)
record is generated. If an LDC disconnects after the second midnight but before it has
been recorded as the start of an LDC, the call is recorded as a single record, indicating
it is an LDC record.
The LDC record is not generated promptly at midnight but is generated within the
hour after midnight (that is, between midnight and 1:00 AM). The possibility of up to
a one-hour delay is due to the length of time required by the system to audit all in-
progress calls in order to determine which, if any, are LDCs.
Each LDC record has a structure code indicating it is for an LDC. An LDC record
contains all the information found in a normal AMA call record, with the following
differences:
The record includes the present-date and present-time fields, which
contain the date and time at midnight.
NTP 297-4102-124 04.01 February 2009
For CS 1500
6-2 AMA record types
The connect-date and connect-time fields always contain the original
connect date and time at which the call was first put up.
For the first LDC record of a call, the elapsed-time field contains the
elapsed time between the connect time and the second midnight. For each
subsequent LDC record, the elapsed-time field contains the elapsed time
between two successive midnights. The occurrence of midnight is
determined by the CS 1500 switch through its time-of-day clock.
The time-indicator field identifies a particular LDC record as the start, the
continuation, or the end of an LDC.
An LDC record is written onto the recording medium immediately after it is created.A
final LDC record is created when the LDC disconnects; the present date and time are
the disconnect date and time, the elapsed time is time between the generation of the
previous LDC record and the disconnect, and the timing indicator signals the end of
an LDC.
Usage-sensitive custom calling feature AMA records
Usage-sensitive features are billed on a per-use basis. If a billing register is not
available when a usage-sensitive feature is requested, the request can be processed
normally (with no AMA record of its use) or denied, depending upon the generic
configuration and the operating company's option.
Miscellaneous and statistical AMA records
The miscellaneous and statistical records made by the AMA system include the
following:
Time-Change Record - Records a manual time or date change
Date Record - Written every day at midnight to record the new date
Identification Record - Records the occurrence of one of the following:
- emergency recording-medium (disk) transfer - The record is written on the
disk activated by the transfer.
- manual recording-medium (disk) transfer - One record is written on the
deactivated disk and one on the activated disk.
- System Software Reload - System Reload is a program providing automatic
recovery from severe system faults. It effects recovery by loading all
programs and office data from the primary system disk into system memory.
The occurrence of a System Reload may result in a partial loss of AMA data
insofar as the billing information for any AMA calls in progress is lost. A
System Reload also causes the loss of any AMA records for completed calls
not written on the disk: that is, the data collected is at the billing register or
the call store buffer state. The record for a System Reload is written on the
currently active disk.
AMA record types 6-3
February 2009 04.01 NTP 297-4102-124
For CS 1500
- System Reset recovery from system software faults. The program
reconfigures the system around the fault and rebuilds transient call data.
AMA data are not affected by the occurrence of a System Reset. The record
is written on the currently active disk.
INWATS Overflow Count - This record is written every night at 11:50 PM
from a billing register incremented each time a call to an INWATS hunt
group is overflowed to busy tone or recorded announcement. If LAMA
goes down before or during the generation of INWATS overflow count
records, the process will be aborted, no more counters will be reset (thus,
counts will continue to accumulate), and a maintenance terminal message
will be printed to report the condition. When this occurs, LAMA record
generation will be delayed, but no information will be lost. The DN
reported to LAMA for the hunt group is that of the first DN assigned to the
hunt group, unless the DN has Special Party Billing, in which case that
number is used. If an INWATS hunt group has not been assigned any DNs,
no overflow record will be generated for the group.
Originating Feature Group A Overflow Count - This record is written
every night at 11:50 PM from a billing register incremented each time an
Originating Feature Group A call is overflowed to busy tone or recorded
announcement
MDR Modules - These modules are appended to the AMA record. At the
Revenue Accounting Office (RAO), the AMA record is processed for
billing and then processed for MDR. The extra data contained in the MDR
modules is used to produce the MDR record.
6Special studies
Four special studies are available as an optional feature package for AMA recording.
If the feature is enabled, any or all of the four studies may be specified as a station
option through DN (STN) (see NTP 297-4102-311, Data Modification Manual).
Traffic sampled study (TRAF)
The Traffic Sampled Study (TRAF) is used by division of revenue for coin lines, to
provide data for billing and usage reports and other special applications. Originating
answered and unanswered calls from stations marked for this study require billing
registers and create AMA records with the TRAF indicator marked. They contain, as
do the other studies, normal toll-like billing details. The study only indicator on the
record is marked and the specified call type (TRAF) is inserted.
NTP 297-4102-124 04.01 February 2009
For CS 1500
6-4 AMA record types
Subscriber Line Usage Study (SLUS)
The Subscriber Line Usage Study (SLUS) determines measured service tariffs and
evaluates tariff effects. Originating calls from stations marked with this study create
AMA records, whether the calls are billable or nonbillable, answered or unanswered.
These AMA records are uniquely marked for SLUS. Nonbillable, but recordable,
calls (such as free and local calls) generate AMA records with study only indicator
marked. MDR, ISUS, and ISTS call type have priority over SLUS and TSLS call
types. The study only indicator is marked in each record.
The following types of nonanswer-supervision calls are included in SLUS:
calls reaching a busy tone
calls reaching an overflow tone
intercepted calls
calls reaching a recorded announcement
calls to free numbers (free-terminating calls)
February 2009 04.01 NTP 297-4102-124
For CS 1500
7-1
Section 7: ISDN(PRI) AMA
7 ISDN PRI AMA recording (Bellcore format only)
Billing for PRI functions in a manner similar to billing for line trunks - on a station,
rather than trunk group, basis. Unlike normal trunk originations, for which the trunk
group number is stored in the AMA record, line trunk originations are treated as line
originations for billing purposes.
Determination of billing numbers
Billing numbers in an AMA record made for a call from the PRI to the public network
are determined as follows, according to the setting of the per-interface Billing
Number Selection (BNS) parameter:
calling party number (CPN) preferred as billing number. If the user-
provided number passed screening, this number is recorded. Otherwise, if
only a network-provided number is given, or if the user-provided number
failed screening or was not screened, then the network-provided number
(default DN) is recorded.
user-provided not-screened (UPNS) CPN preferred as billing number. If a
UPNS number is sent in the calling party number information element, this
number is recorded. The default DN is also indicated and recorded in
module 164, which is appended to the AMA record. If only a network-
provided number is given, then the default DN is recorded.
special billing number. For a call with a special billing number, the special
billing number is recorded. If the CPN is available, it is indicated and
recorded in Module 164 (E.164/X.121 Number module), which is
appended to the AMA record.
Bearer call type / Bearer capability
The Bearer call type (voice or circuit-mode data) and the Bearer capability (speech,
3.1kHz audio, 56 kbps data, or 64 kbps data) are recorded in AMA records made for
calls originating from the PRI interface. They are normally not recorded in AMA
records for calls terminating to the PRI except for INWATS AMA records and for
terminating call records that record the usage of calling party subaddress.
NTP 297-4102-124 04.01 February 2009
For CS 1500
7-2 ISDN(PRI) AMA
Signaling services per interface
Usage of the following signaling capabilities can be recorded in an AMA record:
called party subaddress
calling party subaddress
high-layer compatibility
low-layer compatibility
When accepted by the cs 1500 switch, called party subaddress, high-layer
compatibility, and low-layer compatibility are billed to the calling party upon delivery
of this information to the terminating interface; calling party subaddress is billed to
the called party upon delivery of this information to the terminating interface. The
signaling capabilities that are normally billable to the calling party are also potentially
billable to INWATS users and are recorded at the terminating switching system.
Interworking conditions
Interworking situations encountered by the call are indicated in the AMA records for
ISDN calls. For PRI to BRI calls, BRI to PRI calls, and PRI to PRI calls when no
interworking in the private network occurs, no interworking is indicated in the
AMA record. For PRI to POTS calls, PRI to ISUP calls with non-ISDN backward call
indicators, and INWATS calls (using forward call indicators) terminating at the PRI,
and for PRI to PRI calls when interworking occurs in the private network (for
example, in the Class II equipment), interworking is indicated in the AMA record.
Calling Number Identification Services
Number provision and number screening
Billing for number provision and number screening features is on a flat-rate basis.
Number privacy feature
Detailed AMA records are generated on a per-call basis for calls originating from a
PRI if the PRI subscribes to the usage-sensitive calling number delivery blocking
(UCNB) parameter, if the AMA call type parameter in the AMA billing control table
indicates that billing information for the CNB feature is to be recorded, and under
either of the following conditions:
the class II equipment signals a privacy indicator value of presentation
allowed when the interface is subscribed to calling party presentation not
allowed
prohibited when the interface is subscribed to calling party presentation
allowed
The detailed record generated for the UCNB feature contains the date and time of the
call, bearer call type, billing number, and an indication that the calling PRI interface's
calling party presentation subscription has been changed on that call.
ISDN(PRI) AMA 7-3
February 2009 04.01 NTP 297-4102-124
For CS 1500
Name and number privacy feature
Detailed AMA records are generated on a per-call basis for calls originating from a
PRI if the PRI subscribes to the usage-sensitive calling identity delivery and
suppression (UCID) feature, if the AMA call type parameter in the AMA billing
control table indicates that billing information for the CIDS feature is to be recorded,
and under either of the following conditions:
allowed when the interface is subscribed to calling party presentation not
allowed
prohibited when the interface is subscribed to calling party presentation
allowed
The detailed record generated for the UCID feature contains the date and time of the
call, bearer call type, billing number, and an indication that the calling PRI interface's
calling party presentation subscription has been changed on that call.
Calling Number Delivery
Each CND record contains the called directory number and bearer call type, and
separate daily counts of the calling party number availability, unavailability, or
privacy indication.
NTP 297-4102-124 04.01 February 2009
For CS 1500
7-4 ISDN(PRI) AMA
February 2009 04.01 NTP 297-4102-124
For CS 1500
8-1
Section 8: Bellcore AMA record format
8Introduction
This section describes the Bellcore Automatic Message Accounting (AMA) format,
that complies with the technical requirements set forth in the Bellcore documents,
Bellcore Automatic Message Accounting Format (BAF) Requirements (NWT-
001100) and Automatic Message Accounting (TR-TSY-000508).
8BAF Records CS1500 With/Without Module
The general CS1500 of a BAF record is displayed as follows:
Basic Record
Add on Module (Optional)
Final Module
NTP 297-4102-124 04.01 February 2009
For CS 1500
8-2 Bellcore AMA record format
8Layout of BAF records:
A common set of data fields is required in all BAF records: Record Descriptor Word,
Hexadecimal Identifier, CS1500 Code, Call code (Call Type), Sensor Type, Sensor
Identification, Recording Office Type, Recording Office Identificationl
An optional set of data fields is Module. The Module Fields are linked one by one,
and used as additional Billing Service information. For ISDN, Module 164, and e.c..
BAF Record with CS1500 Only BAF Record with CS1500
and Modules
Record Descriptor Word Record Descriptor Word
Hexadecimal Identifier Hexadecimal Identifier
CS1500 Code (0)XXXX CS1500 Code (4)XXXX
Call Code (Call Type) Call Code (Call Type)
Sensor Type Sensor Type
Sensor ID Sensor ID
Recording Office Type Recording Office Type
Recording Office ID Recording Office ID
Other Data Fields Other Data Fields
Module Code
Moduel Data Fields
Moduel 000
Bellcore AMA record format 8-3
February 2009 04.01 NTP 297-4102-124
For CS 1500
8Packed signed decimal encoding
Each piece of record data (except the Record Descriptor Word and the Hexadecimal
Identifier) is recorded as a packed signed decimal number. A given piece of record
data corresponds to an individual data field, such as a CS1500 code, call-type code,
and so on. A packed signed decimal number consists of Binary Coded Decimals
(BCDs) followed by a four-bit sign character. Each data field, therefore, fills up entire
eight-bit bytes. For each data field, the most-significant BCD appears in the left half
of the first byte, and the sign character appears as the right half of the last byte.
There are two sign characters: a positive sign and a negative sign. The positive sign
is coded as Hex C and is appended to a field that contains no fill character (Hex F).
The negative sign is coded as hex D and is appended to a field with at least one fill
character.For the complete list of BCD codes.
Table 8-A: BCD encoding
Data Code in hexadecimal
0 0
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9
Positive sign C
Negative sign D
Fill character F
NTP 297-4102-124 04.01 February 2009
For CS 1500
8Records in the charging data set
There are three general categories of charging records in the charging data set:
Call records, which are generated as a result of calls
Statistical records, such as Time-Change records
Miscellaneous records, such as Media-Change and End-of-Recording
records.
Call records
CS 1500 generates charging records of the following call types (in alphabetical order):
Direct Distance Dialing (DDD)
Directory Assistance, Local (DAL)
Directory Assistance, Toll (DAT)
International Direct Distance Dialing (IDDD)
INWATS (IWAT)
OUTWATS (OWAT)
Subscriber Line Usage Study (SLUS)
Timed Message Rate, Message Business (TMSG)
Traffic Sampled Study (TRAF)
Untimed Message Rate, Message Business (UMSG)
For more detailed descriptions of the available call types, see Table 9-B .
Each call type is associated with a unique call-type code and is recorded under a
corresponding set of structure codes. The structure code for a given call depends on
specified parameters or conditions, such as if the call was answered, or if the call is a
long duration call. Table 10-A, Bellcore Structure Codes", displays the recordable
call types, their corresponding call-type codes, structure codes, and the specified
parameters.
Note: All OUTWATS calls are recorded as call-type code 068. Station
detail is not recorded on OUTWATS calls.
Traffic Sampled Study (TRAF)The types of calls currently recorded by the switch are
listed in Table 10-A. There is a single entry per chargeable call, except for Long
Duration calls. The multiple records for this call type are described under the heading
Long Duration Calls".
February 2009 04.01 NTP 297-4102-124
For CS 1500
Table 8-B: Call Type description,numbers
Call Type
and Mnemonic
Explanation Call Type
Number
Direct Distance
Dialing (DDD)
Locally originated, subscriber-dialed, station-
to-station toll calls.
3
Directory Assistance,
Local (DAL)
Local calls to the operating company's
directory-assistance service.
14
Directory Assistance,
Toll (DAT)
Toll calls to the operating company's directory-
assistance service (e.g., 1+NPA+555-1212).
15
International Direct
Distance Dialing
(IDDD)
Locally originated, subscriber-dialed, station-
to-station, international toll calls.
4
INWATS (IWAT) Inward Wide Area Telephone Service may be
recorded for monthly hours and message
counts.
NA
OUTWATS (OWAT) Outward Wide Area Telephone Service may
be recorded for either full-time or measured-
time rates.
NA
Subscriber Line
Usage Study (SLUS)
Locally originated billable, nonbillable,
answered or unanswered calls may be
recorded for lines lines marked for this study.
Such calls will generate AMA records, but they
are labeled so that no bill will be generated.
(For more detail, see below under the heading
Special Studies.")
10
Timed Message Rate,
Message Business
(TMSG)
Locally originated, message rate or message
business, non toll calls that require timing.
12
Traffic Sampled Study
(TRAF)
Locally originated coin calls (answered and
unanswered) may be recorded for division of
revenue and usage reports. (For more detail,
see below under the heading Special
Studies.")
11
Untimed Message
Rate, Message
Business (UMSG)
Locally originated, message rate or message
business, non toll calls that do not require
timing.
13
- end of table -
NTP 297-4102-124 04.01 February 2009
For CS 1500
Statistical records
The CS1500 charging system generates the following types of statistical records:
Time-Change Records
INWATS Overflow Counts
Time-change records
Generated whenever a clock change occurs. Recorded as call-type code 042, structure
code 09000. (See Section 10, Bellcore Structure Codes" for more detail.)
Miscellaneous records
The following are the types of miscellaneous records generated by the CS1500
charging system:
Media-Change records
End-of-Recording records
Data-Initialization records.
Call Type
All three types of miscellaneous record (Media-Change, End-of-Recording, and Data-
Initialization records) use call-type code 092.
Generic Issue
A five-digit field in which the first three digits contain the generic version number and
the last two contain the issue number. Both the version and issue numbers are listed
in the Configuration Record. The user may query the exchange configuration record
to determine which generic version is used in the CS1500. The procedure for making
this query is contained in the NTP entitled Data Modification Manual.
Type of Tracer
The Media-Change record contains 007 in this field; the End-of-Recording record has
008 recorded in this field; the Data-Initialization record contains 009.
Sequence Number
For any logical data set, the sequence numbers shown in the Media-Change and End-
of-Recording records should be the same. The sequence number can range from 1
through 999, and is incremented for each new logical data set. The sequence number
is a 1 under the following circumstances:
after initial system start-up
when the count rolls over from 999
after an outage affecting protected Call Store (that is, that destroys
unrecorded charging data).
February 2009 04.01 NTP 297-4102-124
For CS 1500
Record Count
This field shows the total number of records in the logical data set, including any
Media-Change, End-of-Recording, and Data-Initialization records.
Block Count
Shows the total number of blocks in the data set, including the blocks that contain
other records.
8Data fields within records
The following paragraphs explain the contents of each type of data field.
Fields common to all records
The following fields are common to all records (only one of the four fields connected
with Data Table 6 [Date, Date of Answer, Carrier-Connect Date, and Present Date]
will be found in any given record):
Call-Type Code (Data Table 1)-This code indicates the call-type in the record.
Sensor Type (Data Table 2)-This field always contains a 029 code, which indicates
the record is from a CS1500.
Sensor Identification (Data Table 3)-The number recorded in this field is
copied from the Configuration Record of the CS1500 exchange and
specifically identifies the CS1500. This number is specified by the
operating company.
Recording Exchange Type (Data Table 4)This field always contains a 029
code, which indicates the record is from a CS1500.
Recording Exchange Identification (Data Table 5) (This field contains the
same number as the Sensor Identification field (Data Table 3) above.
Date (Data Table 6)-The year (1 digit), the month (two digits), and the day
(two digits) the record was made.
Date of Answer (Data Table 6)-The year (1 digit), the month (two digits),
and the day (two digits) the call was answered. In the case of test calls, this
field contains the date on which the test facility was seized. For
unanswered calls and calls utilizing CAMA signaling or Operator Service
signaling with no acknowledgment wink returned, this field contains the
date on which the trunk was seized.
Present Date (Data Table 6)-The year (1 digit), the month (two digits), and
the day (two digits) a Long-Duration Call (LDC) record is formed. For the
last LDC record of a call, this field contains the disconnect time.
NTP 297-4102-124 04.01 February 2009
For CS 1500
8Fields used only for call records
The following field are used only for call records; not all fields appear in all call
records:
Circuit Date (Data Table 9-B)Contains- a record of the circuit-release date.
Timing Indicator (Data Table 7)-Indicate whether a timed-release
disconnect occurred. Flags also indicate the progress of a Long-Duration
Call and charge-guard conditions. (Charge guard indicates the call was
rebuilt after a system initialization, and the elapsed time [and/or time from
carrier connect] is recorded up to the point of system initialization.)
Calls of a duration Under Minimum Chargeable Duration (UMCD), before
the application of the timing allowance, are not recorded. Calls of a
duration not UMCD, after the timing allowance is applied, are recorded.
Study Indicator (Data Table 8)-Indicates the studies in effect at the sensor
(the CS1500). A third character of 2, indicates the record would not have
been made had the study not been in effect.
Answer (Data Table 9)-A 0 indicates the call was answered; a 1 indicates
it was unanswered.
Service Observed, Traffic Sampled (Data Table 10)-Indicates Service
Observed and/or Traffic Sampled calls.
Operator Action (Data Table 11)-A 0 is recorded in this field by the
CS1500 since all CS1500s are Class 5 offices and, therefore, do not
perform any operator functions.
Service Feature (Data Table 12)`Used to indicate service features of the
recorded call. Recordable service features include:
Call Forwarding
Automatic Wake Up Service
Metering for Fixed Price Services
Enquiry Calls
Three-Way (Conference) Calling
Prepay coin on a line included in a Traffic Sampled Study
Hotel/Motel
Hotel/Motel Remote Register
Originating Numbering Plan Area (Data Table 13)-Records the NPA of the
originating number.
Originating Number (Data Table 14)-The originating directory (or billing)
number is recorded.
February 2009 04.01 NTP 297-4102-124
For CS 1500
For INWATS entries, these fields contain the number of the party to be billed (in such
a case, the terminating party).
Overseas Indicator (Data Table 15)-Indicates whether or not the call is an
overseas call. If it is not, the CS1500 indicates whether or not the called
NPA was automatically derived by the CS1500 (that is, it was the HNPA
of the calling party).
When an overseas call is recorded, the dialed digits may appear (depending
upon the number of digits dialed) in both the Terminating NPA (Data Table
16) and Terminating Number (Data Table 17) fields. The recorded number
is always right adjusted in these two fields and padded with zeros (if
necessary) in the most-significant digits. For example, an 11-digit
overseas number has one zero padding character in the first BCD character
of the terminating NPA field. This is followed by the four most-significant
digits of the dialed number. The terminating number field contains the
seven remaining digits.
Terminating Numbering Plan Area (Data Table 16)-For calls within the
country, the first two characters are zeros. Characters three through five
contain the called NPA. For overseas calls, see the explanation of the
Overseas Indicator (Data Table 15) field. If an NPA is not dialed, the
HNPA of the calling party is inserted by the CS1500
Terminating Number (Data Table 17)-For calls within the country, this
field contains the five- to seven-digit terminating number. For overseas
calls, see the explanation of the Overseas Indicator (Data Table 15) field.
For calls within the country, the CS1500 records the digits as they are
dialed and as they are substituted during digit translation. If this happens
to be a ten-digit number, then the first three are recorded as the terminating
NPA and the next seven are recorded as the terminating number. If,
however, it happens to be other than a ten-digit or a seven-digit number,
the digits are right-justified and padded with zeroes.
For an N11 Terminating Feature Group A, the N11 is set in the NPA field
and the DN field is padded with zeroes.
Answer Time (Data Table 18)-Records the hour (two-digits), minutes (two-
digits), seconds (two-digits) and tenth of a second (one digit) the call was
answered. For test calls, this field records the time the test facility was
seized. When Operator Services signaling is used (with no
acknowledgment wink return), zeroes are recorded.
If the call is unanswered, or if CAMA signaling is used, this field records the time the
trunk was seized.
Time (Data Table 18)?Indicates the time the record was made.
NTP 297-4102-124 04.01 February 2009
For CS 1500
Present Time (Data Table 18)-For the intermediate Long-Duration Call
(LDC) records, the first seven characters indicate the midnight time (that
is, 0000 and the new date). For the last LDC record of an LDC call, these
seven characters indicate the disconnect time.
Circuit Time (Data Table 18)-Contains a record of the circuit-release time.
Elapsed Time (Data Table 19)-The first character is padding (0). The next
eight characters record the elapsed time from answer until disconnect in
minutes (five digits), seconds (two digits), and tenths of a second (one
digit). For test calls, this field records the elapsed time from seizure of the
test facility until disconnect. (For calls to a test panel, disconnect is the
time the test panel is released.)
For unanswered calls and calls that use CAMA or Operator Services signaling (with
no acknowledgment return), this field contains zeros. For a Long-Duration Call, the
sum of the contents of this field for all relevant records yields the total elapsed time
from answer to disconnect (less any timing allowances).
Elapsed Time from Carrier-Connect (Data Table 19)-The first character is
padding (0). The next eight characters record the elapsed time from the
carrier-connect time until disconnect in minutes (five digits), seconds (two
digits), and tenths of a second (one digit).
For test calls, this field records the elapsed time from seizure of the test facility until
disconnect. (For calls to a test panel, disconnect is the time the test panel is released.)
For a Long-Duration Call, the sum of the contents of this field for all relevant records
yields the total elapsed time from answer to disconnect (less any timing allowances).
Trunk Network Number (Data Table 20)-A number identifying the
outgoing trunk used for the call. This number is the physical address (bay,
shelf, pack position, unit [bspu]) of the trunk.
Circuit Time (Data Table 26)-This field records the time of day of either
trunk seizure or release.
WATS Indicator (Data Table 28)-This field differentiates between full
business day (a 1 is recorded) and measured time (a 2 is recorded) WATS.
WATS Band or Type Indicator (Data Table 29)-This field records the
WATS band or Message Billing Index (MBI), which are mutually
exclusive.
Type of Tracer (Data Table 40)-A number that identifies the type of tracer
record used: media-change, end-of-recording, or data initialization.
Routing Indicator (Data Table 59)-A first character 0 indicates direct call
(that is, calls from an end exchange not passing through an Access Tandem
or calls from stations connected directly to the Access Tandem); a first
character of 1 indicates tandem calls.
February 2009 04.01 NTP 297-4102-124
For CS 1500
ANI Indicator (Data Table 60)-A 0 indicates call types not provided
Automatic Number Identification (ANI). A 1 indicates call types normally
provided ANI.
Trunk-Group Number (Data Table 83)-The first character of this field is
padding (0). The next four characters indicate the trunk group utilized by
the call.
AMA Sequence Number (Data Table 140)-The first character is padding.
The next four characters can have a value in the range 0000 through 9999,
indicating the vintage number of an charging transmitter. The transmitter
manufacturer determines this number, identifying only the software
release or the total set of switching system and transmitter hardware and
software currently in use.
Number Recording (Data Tables B.1 through B.5 [Data Tables 801
through 805])When a number must be recorded and no explanation of it
is necessary (or the explanation is unavailable), a reference is made to
Tables B.1 through B.5 (Tables 801 through 805). These tables show the
fields numbers can be recorded. Note every field contains an odd number
of digits followed by a sign character.
Audit Flag (Data Table C.147)-The first character indicates the validity of
the data for auditing purposes. The second character is a sign character.
Data tables (Table 9-A) lists the Data Table numbers and the names of the
corresponding Data Fields applying to charging recording in the CS1500;
they are arranged in alphanumerical order by data table number.
Following Table 9-B are tabular summaries of the contents of the various
Data Tables.
Timing considerations
Elapsed-time calculation
The elapsed-time field and the nearest-event time fields (connect time,
circuit time, etc.) are recorded to the nearest tenth of a second, by the
elapsed time clock. Because the elapsed-time clock is separate from the
time-of-day clock, it is not affected by time changes. The CS1500 adjusts
the connect time on all in-progress, recordable calls by the same change
that is made to the time-of-day clock.
Elapsed-time calculation for long-duration calls
Because the time-of-day clock is used to schedule the generation of Long-
Duration Call (LDC) records, it is affected by time changes (that is, there
will not be exactly 24 hours between midnights" if the time-of-day clock
has been changed during a given 24-hour period).
NTP 297-4102-124 04.01 February 2009
For CS 1500
Because elapsed time is calculated with the elapsed-time clock, which is
not affected by clock changes, the Elapsed-Time field always contains the
actual elapsed time between successive LDC record generations. This
allows the operating company to add up the successive elapsed times for
billing purposes without making allowance for intervening time
adjustments.
Thus, for Long-Duration Calls, the sum of the elapsed times will equal the
disconnect time in the last record minus the connect time in the first record,
provided that no time changes have taken place during the call.
Accuracy of the elapsed-time clock
The accuracy of the elapsed-time clock is identical to that of the time-of-
day clock. If the CS1500 is synchronized with a master clock via a digital
carrier, the accuracy of the elapsed-time clock equals that of the digital
network. If the CS1500 is not slaved to a master clock, the accuracy of the
elapsed-time clock is within ten parts per million (roughly 1 second per 30
hours).
Timing allowance for hardware delays
The CS1500 attempts to meet the standard of (recorded duration + 0) =
actual duration, but to ensure that a subscriber is never overbilled because
of hardware delays, a 0.2-second allowance is subtracted from the elapsed
time of every recordable call.
Table 8-C: Data table numbers for CS1500
Table Number Data Field
1 Call Types
2 Sensor Type
3 Sensor Identification
4 Recording Exchange Type
5 Recording Exchange Identification
6 Date of Answer
Circuit Date
Present Date
7 Timing Indicator
8 Study Indicator
9 Answer Indicator
10 Service Observed, Traffic Sampled
11 Operator Action
February 2009 04.01 NTP 297-4102-124
For CS 1500
12 Service Feature
13 Originating Numbering Plan Area (NPA)
14 Originating Number
15 Overseas Indicator
16 Terminating Numbering Plan Area (NPA)
17 Terminating Number
18 Answer Time
Carrier-Connect Time
Time
Present Time
Circuit Time
19 Elapsed Time
20 Trunk Network Number (TNN)
26 Circuit Time
28 WATS Indicator
29 WATS Band or Type (Message Billing Index)
40 Type of Tracer
46 RAO Number
57 Inter-LATA Carrier/International Carrier Prefix
58 Inter-LATA Carrier/International Carrier Call Event Status
59 Routing Indicator
60 ANI Indicator
83 Trunk Group Number
85 Dialing Indicator
87 Business Customer Identification
88 Module Code
128 Overflow Peg Count
138 Alternate Billing Number
140 AMA (Charging) Format Sequence Number
197 Local Access Transport Area
NTP 297-4102-124 04.01 February 2009
For CS 1500
235 Call Completion Code
236 Business Feature Code
238 Automatic Route Selection Pattern
239 Facility Restriction Level
243 Incoming/Outgoing Facility Type
244 Incoming/Outgoing Trunk Facility Identification
245 Queue Elapsed Time
B.1 (801) One-Digit Number
B.2 (802) Three-Digit Number
B.3 (803) Five-Digit Number
B.4 (804) Seven-Digit Number
B.5 (805) Nine-Digit Number
C.147 Audit Flag
Table 8-D: Data table 1 - call types (CS1500)
Number of
BCD
Character
Call Code Meaning / Contents
1-3 001 Detailed Message Rate, Timed, Message Billing Index (MBI)
1-3 002 Message Rate, Timed, Message Billing Index (MBI)
1-3 003 Detailed Message Rate, Untimed, No Message Billing Index (MBI)
1-3 004 Message Rate, Untimed, Message Billing Index (MBI)
1-3 005 Detailed Message Rate, Timed, No Message Billing Index (MBI)
1-3 006 Station Paid, DDD and IDDD (except Bezeq)
1-3 007 IDDD for Bezeq
1-3 008 INWATS, Terminating Entry
1-3 009 Directory Assistance, Local
1-3 011 Feature Activation
February 2009 04.01 NTP 297-4102-124
For CS 1500
1-3 033 Directory Assistance, Toll
1-3 042 Time Change
1-3 067 Flat Rate
1-3 068 OUTWATS (Billing number, without WATS band)
1-3 071 INWATS Overflow Counts
1-3 090 Sensor Tracer
1-3 092 End of Recording, Media Change, or Data Initialization
1-3 159 Business Group Features (MDR Free Call)
4 NA SIGN (hex C)
Table 8-E: Data table 2 - sensor type (CS1500)
Number of
BCD
Character
Possible
Value(s)
Meaning
1-3 029 CS1500
4 hex C SIGN
Table 8-F: Data table 3 - sensor identification
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0 Padding
2-7 Identification Code
8 hex C SIGN
Table 8-D: Data table 1 - call types (CS1500)
Number of
BCD
Character
Call Code Meaning / Contents
NTP 297-4102-124 04.01 February 2009
For CS 1500
Table 8-G: Data table 4 - recording office type
Number of
BCD
Character
Possible
Value(s)
Meaning
1-3 029 CS1500
4 hex C SIGN
Table 8-H: Data table 5 - recording exchange identification
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0 Padding
2-7 Identification Code
8 hex C SIGN
Table 8-I: Data table 6 - date
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0-9 Last digit of current year
2-3 01-12 Month
4-5 01-31 Day
6 hex C SIGN
Table 8-J: Data table 7 - timing indicator
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0 Not Timed-Release Disconnect
1 Timed-Release Disconnect
3 Single-Time Line (missing connect or disconnect time)
2 0 Padding
February 2009 04.01 NTP 297-4102-124
For CS 1500
3 0 Not a Long Duration Call
1 Start of a Long Duration Call (or activation)
2 Continuation of a Long Duration Call (or still active)
3 End of a Long Duration Call (or deactivation)
5 Complete Long Duration Call record, disconnected before first record
was output (or activation and deactivation in one day).
4 0 Not Charge Guard
1 Charge Guard (elapsed time)
4 Charge Guard (elapsed time from carrier connect)
5 Charge Guard (elapsed time and elapsed time from carrier connect)
5 0 No time-stamp error
1 Possible time-stamp error (answer)
2 Possible time-stamp error (carrier connect)
3 Possible time-stamp error (answer and carrier connect)
6 hex C SIGN
Table 8-K: Data table 8 - study indicator
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0 Not Subscriber Line Usage Study (SLUS)
2 Subscriber Line Usage Study (SLUS)
2 0 Not complaint observed (individual observed for VSS)
1 Complaint observed
3 0 Not study-generated
2 Study-generated record
4 0 Padding
1 Test call
Table 8-J: Data table 7 - timing indicator
Number of
BCD
Character
Possible
Value(s)
Meaning
NTP 297-4102-124 04.01 February 2009
For CS 1500
5 0 Padding
6 0 Padding
1 No calling number
3 No called number
4 No calling number and no called number
7 0 Padding
8 hex C SIGN
Table 8-L: Data table 9 - answer indicator
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0 Answered
1
2
3
Unanswered
Unused
Feature Activation, not an answered call
2 hex C SIGN
Table 8-M: Data table 10 - service observed, traffic sampled
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0 Not Service Observed, not Traffic Sampled
1 Service Observed, not Traffic Sampled
2 Not Service Observed, Traffic Sampled
3 Service Observed, Traffic Sampled
2 hex C SIGN
Table 8-K: Data table 8 - study indicator
Number of
BCD
Character
Possible
Value(s)
Meaning
February 2009 04.01 NTP 297-4102-124
For CS 1500
Table 8-N: Data table 11 - operator action
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0 No operator action
2 hex C SIGN
Table 8-O: Data table 12 - service features
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0 Padding
2-3 00 Other (Including Ring Back Price, DAL/DAT)
01 Prepay coin
02 Hotel/Motel
03 Not used
04 Postpay coin
05 Not used
06 Not used
07 Not used
08 INWATS (for Common Channel Interoffice Signaling [CCIS] originating
entry only)
09 Not used
10 Three-Way (Conference) Calling and Enquiry Call (Note 1)
11 Automatic Wake Up Service (Note 1)
12 Call Forwarding (terminating leg or flat rate) (Note 1)
13 Hotel/Motel Remote Register, MTR and fixed price service (Note 1)
20 Short Speed Call/Long Speed Call (Note 2)
30 Automatic Call (Note 2)
40 Warm Line - ALTO (Note 2)
50 Three-way Call (Note 2)
70 Call forwardinng - CFW/CFD/CFB/RCFA (Note 2)
NTP 297-4102-124 04.01 February 2009
For CS 1500
Note 1: The service feature is used for all markets except Bezeq.
Note 2: For Bezeq only.
90 Call Forwarding to Voice Mail - CFB/CFD (Note 2)
4 hex C SIGN
Table 8-P: Data table 13 - originating numbering plan area (NPA)
Number of
BCD
Character
Possible
Value(s)
Meaning
1-3 0-9 Numbering Plan Area (NPA)
4 hex C SIGN
Table 8-Q: Data table 14 - originating number
Number of
BCD
Character
Possible
Value(s)
Meaning
1-3 0-9 NNX digits (ABC digits)
4-7 0-9 Four-digit number (DEFG digits)
8 hex C SIGN
Table 8-R: Data table 15 - overseas indicator - Not in use
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0 Not an overseas call (Numbering Plan Area [NPA] dialed)
1 Not an overseas call (Numbering Plan Area [NPA] not dialed, but
derived by CS1500)
2 Less than 7-digit overseas number
3 7-digit overseas number
Table 8-O: Data table 12 - service features
Number of
BCD
Character
Possible
Value(s)
Meaning
February 2009 04.01 NTP 297-4102-124
For CS 1500
2 hex C SIGN
Table 8-S: Data table 16 - terminating numbering plan area (NPA) - Not in use
Number of
BCD
Character
Possible
Value(s)
Meaning
1-2 0-9 Overseas expander positions
3-5 0-9 Terminating Numbering Plan Area (NPA)
6 hex C SIGN
Table 8-T: Date table 17 - terminating number
Number of
BCD
Character
Possible
Value(s)
Meaning
1-15 0-9 Called number digits
8 hex C SIGN
Table 8-U: Data table 18 - time
Number of
BCD
Character
Possible
Value(s)
Meaning
1-2 00-23 Hours
3-4 00-59 Minutes
5-6 00-59 Seconds
Table 8-R: Data table 15 - overseas indicator - Not in use
Number of
BCD
Character
Possible
Value(s)
Meaning
NTP 297-4102-124 04.01 February 2009
For CS 1500
Note: On attempts, zeros are recorded for minutes, seconds, and tenths
of a second.
Note: The trunk network number (TNN) is only displayed when a special
study is in effect, or when the CS1500 is configured so that the outgoing
trunk group number is included in the charging data printout (see prompt
AMAT in Overlay CNFG, prompting sequence SYS).
7 00-9 Tenths of a second
8 hex C SIGN
Table 8-V: Data table 19 - elapsed time
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0 Padding
2-6 00000-
99999
Minutes
7-8 00-59 Seconds
9 0-9 Tenths of a second
10 hex C SIGN
Table 8-W: Data table 20 - trunk network number (TNN)
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0 Padding
2-4 000-
999
Trunk Group Number
5-7 00-59 Trunk Member Number
8 hex C SIGN
Table 8-U: Data table 18 - time
Number of
BCD
Character
Possible
Value(s)
Meaning
February 2009 04.01 NTP 297-4102-124
For CS 1500
Table 8-X: Data table 26 - circuit time (CS1500)
Number of
BCD
Character
Possible
Value(s)
Meaning
1-2 0- 23 Hours
3-4 0 - 59 Minutes
5-6 0 - 59 Seconds
7 0 - 9 Tenths of seconds
8 hex C SIGN
Table 8-Y: Data table 28 - WATS indicator
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0 This character not used
1 Full Business Day
2 Measured Time
2 hex C SIGN
Table 8-Z: Data table 29 - WATS band or type indicator (MBI)
Number of
BCD
Character
Possible
Value(s)
Meaning
1-3 Type Indicator (Message Billing Index [MBI])
4 hex C SIGN
NTP 297-4102-124 04.01 February 2009
For CS 1500
Table 8-AA: Data table 40 - type of tracer
Number of
BCD
Character
Possible
Value(s)
Meaning
1-3 007 Media-Change record
008 End-of-Recording record
009 Data-Initialization record
4 hex C SIGN
Table 8-AB: Data table 55 - Significant digits in next field(s)
Number of
BCD
Character
Possible
Value(s)
Meaning
1-3 0-9 Number of significant digits in next field(s)
4 hex C SIGN
Table 8-AC: Data table 59 - routing indicator
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0 Direct
1 Tandem
2 hex C SIGN
February 2009 04.01 NTP 297-4102-124
For CS 1500
Table 8-AD: Table 6 - A E: Data table 76 - Number identity
Number of
BCD
Character
Possible
Value(s)
Meaning
1 2 Terminating (destination)
2 hex C SIGN
Table 8-AE: Data table 83 - trunk group number
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0 Padding
2-5 Trunk Group Number
6 hex C SIGN
Table 8-AF: :Data table 88 - Module code
Number of
BCD
Character
Possible
Value(s)
Meaning
1-3 000-999 3-digit Module Code
4 hex C SIGN
NTP 297-4102-124 04.01 February 2009
For CS 1500
Table 8-AG: Data table 126 - Digits
Number of
BCD
Character
Possible
Value(s)
Meaning
1-15 0-9 Digits
16 hex C SIGN
Table 8-AH: Data table 140 - AMA (charging) format sequence number
Number of
BCD
Character
Possible
Value(s)
Meaning
1 Overflow count
2-5 0000-
9999
Vintage number used by an AMA Transmitter. Its use is determined by
the transmitter's manufacturer. It may identify only the transmitter's
software release or the total set of switching system and transmitter
hardware and software currently in use.
6 hex C SIGN
Table 8-AI: Data table 164 - Country Code
Number of
BCD
Character
Possible
Value(s)
Meaning
0 Module Code
2 Number Identity
3 Country Code
6 Significant Digits in Next Field(s)
8 Number
February 2009 04.01 NTP 297-4102-124
For CS 1500
Note: Used for Redirection calls included in Module 116 Chap_9
Note: Used for calls routing depends upon DNs definition, ISUP CPC
(Calling Party Category), SIP CPC or R2 category receiving and the
needed code changes in order to support it.
Table 8-AJ: Data table 165 - Country Code or DNIC
Number of
BCD
Character
Possible
Value(s)
Meaning
1-5 Most significant digits of the destination number (including all prefixes),
right justified and padded with F.
6 Hex C/D Field integrity
Table 8-AK: Data table 169 - Call Redirection/Deflection Indicator
Number of
BCD
Character
Possible
Value(s)
Meaning
1 1 Redirection
2 2 Notification not provided
3-5 005 Redirection Indicator-CFB
006 Redirection Indicator-CFD
007 Redirection Indicator-CFD
008 Redirection Indicator-CFGD
009 Redirection Indicator-Call Pickup
3-5 016 Unknown
10 C SIGN
Table 8-AL: Data Table 206
CPC
Number of BCD Character Possible Value(s) Meaning
1-3 0-9
0
1
Calling Category 1-10
Calling Category 10
Calling Category 1
6 hex C SIGN
NTP 297-4102-124 04.01 February 2009
For CS 1500
Table 8-AM: Data table 244 - Trunk identification
Number of
BCD
Character
Possible
Value(s)
Meaning
1 003 Incoming TG
004 Incoming LTG
005 Outgoining LTG
006 Outgoining LTG
2-5 0001-
0063
Trunk Group Number
6-9 0001-
9999
Trunk Member Number
10 hex C SIGN
Table 8-AN: Data table 280 - Call Completion Code
Number of
BCD
Character
Possible
Value(s)
Meaning
1-3 000-999 Call Completion Code
001 Completed: Answered
006 Not completed: Ringing
007 Not completed: Busy
008 Not completed: No answer supervision
016 Not completed: Other treatment
017 Not completed: abnormal
030 In progress: Long duration
4 C SIGN
February 2009 04.01 NTP 297-4102-124
For CS 1500
Note: Data Table 338, 339 are included in Module 130(Chap_8) used
for rejected call recording. Three Termination Cause tables , Table 8-AQ
describes Termination Cause value for calls treated locally, Table 8-AR
describes ISUP Termination Cause value for calls trated externally and 8-
AS describes SIP Termination Cause value for calls trated externally .
Table 8-AO: Data table 338 - Facility Release Cause
Number of
BCD
Character
Possible
Value(s)
Meaning
1 002 Called Party
2 000 Not Completed
3-5 500-995 Termination Causes Table
6 hex C SIGN
Table 8-AP: Data table 339 - Call Characteristic
Number of
BCD
Character
Possible
Value(s)
Meaning
1-3 004 Treated Locally
005 Treated Externally
4 hex C SIGN
Table 8-AQ: Numerical Treatment Mappings
Number Treatment Description
500 UNDT Undetermined Treatment
501 PRDI Partial dial
502 BDIG Bad digit
503 SFWR Software error
504 PMSG Permanent signal
505 BUSY Line busy
506 NTBK Network block
NTP 297-4102-124 04.01 February 2009
For CS 1500
507 VCCO Vacant office code
508 VCDN Vacant directory number
509 OVFL Overflow
510 OSUS Originating suspended
511 NOCO no coin
512 DTTO dial tone timeout
513 RGTO ring timeout
514 BDTA bad data
515 REV1 Revertive 1
516 REV2 Revertive 2
517 DNT deny terminating
518 DNO deny originating
519 BSRG bad station ringer
520 NRSC no resources
521 SFUN software unassigned
522 DNIC directory number intercept
523 TKER signaling error
524 ANIF Any ANI fail detedted
525 MAN manual line
526 DNCH directory number changed
527 ROVD ringing overload
528 LFLT line faulty
529 TSUS terminate on suspended
530 BVRF Bad verification call condition. Conference circuit is unavailable
531 NBR no billing register
532 AMAD AMA system down
533 IWTD INWATS denied
534 NCPS CPSC not available
February 2009 04.01 NTP 297-4102-124
For CS 1500
535 COPT CAMA operator trouble
536 CSBK CAMA suspension blocked
537 NOCH no channel
538 DACK deny alarm-checking access (ACKA)
539 DLER dialing error
540 DDST deny dial speed test
541 EORG emergency origination tone
542 NDLC No Data Link Controller (DLC)
543 NIOI NO IOI DLC
544 BUFL IOI BUFFER FULL
545 AWSR Switch is performing an automatic wake-up service call.
546 AWSV Invalid or too few military-time digits are entered by the
subscriber for automatic wake-up service
547 BOOK The operator console is used to route a booked (reserved) call
548 RECL An operator who has connected a call through an operator
console must be recalled.
549 OBSY operator console busy
550 OPIC Operator intercept. A call has been placed to a directory
number that is operator intercepted.
551 CLBR Originating call is barred because the Outgoing Call Barring
feature is activated.
552 APOS successful customer calling control action
553 ANEG unsuccessful attempt to access a system resource for a
customer calling control
554 QPOS Successful customer calling query.
555 QNEG Unsuccessful customer calling query.
556 CTTO caller waiting tone (CWTT) time-out has occurred
557 CORQ CLASS Automatic Recall/Automatic Call Back (AR/ACB)
request is confirmed
558 AATD AR/ACB request cannot be processed due to temporary
difficulty
NTP 297-4102-124 04.01 February 2009
For CS 1500
559 TEBA AR/ACB terminating station becomes busy again, after the
calling party receives special raring
560 CLAS CLASS resource is unavailable.
561 ARCB AR is not available due to caller number delivery blocking.
562 DARA double AR activation is completed
563 DACR ACB deactivation request is confirmed
564 SP ISDN speech bearer
565 3AU ISDN 3.1 KHz audio bearer capability is not supported by the
terminating party
566 64C ISDN 64 kbps circuit mode data bearer capability is not
supported by the terminating party
567 CREJ ISDN Call rejected cause
568 ISBY ISUP busy condition
569 ISOF ISUP overflow
570 DNRP directory number replaced
571 FNAL CLASS or business group feature is not configured in the switch
or not permitted by the subscriber's station options.
572 ACRD ABB request denied
573 CFA1 ANNS CODE 01
578 DARR AR deactivation request is confirmed
579 AWSP AWS POSITIVE
580 AWSN AWS NEGATIVE
581 SMUP SMLTNS UPDATE
582 DNDR CEPT Do Not Disturb subscriber option (DND)
583 IDFR Immediate Diversion to a Fixed Number subscriber option (IDF)
584 CICB CEPT Incoming Call Barring subscriber feature (CICB)
February 2009 04.01 NTP 297-4102-124
For CS 1500
Numerical Treatment Mappings Tabel used for rejected call recording, when Treated Locally in Data Table 339, relating to Module 130 (see Chap_8
585 FTRM ISDN PRI call fails to terminate due to a time-out, call rejection,
or protocol error
586 CBSY circuit requested by the SCP is not idle
Table 8-AR: CCITT Specified Cause Indicators Mapping for Table 338
Description Decimal Value
Unallocated Number 1 501
No Route To Transit Network 2 502
No Route To Destination 3 503
Send Special Info Tone 4 504
Misdialed Trunk Prefix 5 505
Normal Call Clearing 16 516
User Busy 17 517
No User Responding 18 518
No Answer From User 19 519
Call Rejected 21 521
Number Changed 22 522
Translations Failure 25 525
Call Awarded Estalished Chanel 26 526
Destination Out Of sevice 27 527
Address Incomplete 28 528
Facility Rejected 29 529
Apply Locally 30 530
Normal Unspecified 31 531
No Circuit Available 34 534
Network Out Of Order 38 538
Temporary Failure 41 541
Switching Equipment Congetion 42 542
NTP 297-4102-124 04.01 February 2009
For CS 1500
User Info Discarded 43 543
Required Channel Unavailable 44 544
Preemption 45 545
No Preempt Circuit Available 46 546
Resource Unavailable - Unspecified 47 547
Requested Facility Not Subscribed 50 550
Outgoing Calls Barred 51 551
Incompatible agents 52 552
Incoming Calls Barred Within CUG 55 555
BC Not Authorized 57 557
BC Not Presently Available 58 558
Service Not Available - Unspecified 63 563
BC Not Implemented 65 565
Channel Type Not Implemented 66 566
Requested Facility Not Implemented 69 569
Restricted BC Information 70 570
Service Not Implemented - Unspecified 79 579
Invalid Call Ref Value 81 581
User Not Member Of CUG 87 587
Incompatible Destination 88 588
Invalid Transit Network Selection 91 591
Invalid Message 95 595
Unknown Message 97 597
Parm Non-Existent - Discarded 99 599
Invalid Parm Contents 100 600
Timer Expiry 102 602
Parm Non-Existent - Passed On 103 603
Protocol Error 111 611
February 2009 04.01 NTP 297-4102-124
For CS 1500
Interworking Unspecified 127 627
Table 8-AS: SIP responses to termiantion cause
mapping
Description SIP-T RFC 3398 Value Mapping for table 338
SIP bad request 400 N/a
SIP unauthorized 401 N/a
SIP payment required 402 N/a
SIP forbidden 403 521
SIP not found 404 526
SIP method not allowed 405 N/a
SIP not acceptable 406 N/a
SIP proxy authorization request 407 N/a
SIP request timeout 408 518
SIP conflict 409 N/a
SIP gone 410 522
SIP length required 411 N/a
SIP requested entity too long 413 N/a
SIP request URI too long 414 N/a
SIP unsupported media type 415 N/a
SIP unsupported URI scheme 416 N/a
SIP bad extension 420 N/a
SIP extension required 421 N/a
SIP interval too brief 423 N/a
SIP temporary unavailable 480 531
SIP trans not exist 481 N/a
SIP loop detected 482 N/a
SIP too many hops 483 N/a
NTP 297-4102-124 04.01 February 2009
For CS 1500
SIP address incomplete 484 528
SIP ambiguous 485 N/a
SIP busy here 486 517
SIP request terminated 487 500
SIP not accepted here 488 565
SIP server internal error 500 502
SIP not implemented 501 529
SIP bad gateway 502 527
SIP service unavailable 503 534
SIP service timeout 504 602
SIP version not supported 505 N/a
SIP message too large 513 N/a
SIP busy everywhere 600 517
SIP decline 603 531
SIP not exist anywhere 604 501
SIP global not acceptable 606 531
Table 8-AS: SIP responses to termiantion cause
mapping
Description SIP-T RFC 3398 Value Mapping for table 338
February 2009 04.01 NTP 297-4102-124
For CS 1500
Table 8-AT: Data table 411 - Release Cause Indicator
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0 No interworking encountered
2 0 ITU-T
3 Network specific
3-5 001 Unallocated (unassigned)number
*
016 Normal clearing
017 User Busy
*
018 No user busy
*
019 User alerting, no answer
*
021 Call rejected
*
022 Number changed
*
027 Destination out of order
*
028 Invalid number format
*
029 Facility rejected
*
031 Normal unspecified
*
034 Circuit/Channel congestion
*
041 Temporary failure
*
042 Switching equipment congestion
*
043 Access information discarded
*
044 Requested channel no available
*
047 Resource unavailable, unspecified
*
050 Requested facility not subscribed
*
NTP 297-4102-124 04.01 February 2009
For CS 1500
* - future use, in case we have non answered calls recorded on AMA.
057 Bearer capability not authorized
*
063 Service or option not available
*
065 Bearer capability not implemented
*
088 Incompatible destination
*
095 Invalid message, unspecified
*
096 Mandatory information element missing
*
101 Message not compatible with call state
*
102 Recovery on timer expiring
*
111 Protocol error, unspecified
*
127 Interworking, unspecified
*
Interworking specific
004 Vacant code
*
043 User information discard
*
102 Timer expiring
Table 8-AU: Data table 412 - Bearer Capability/Call Code
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0 Bearer Call Code - general
2-3 01 Circuit mode speech
02 Circuit mode 3.1 khz. Audio
03 Circuit mode unrestricted 64 kbps digital
Table 8-AT: Data table 411 - Release Cause Indicator
Number of
BCD
Character
Possible
Value(s)
Meaning
February 2009 04.01 NTP 297-4102-124
For CS 1500
99 Unknown
Table 8-AV: Data table 413 - Signaling or Supplementary Service Capabilities
Number of
BCD
Character
Possible
Value(s)
Meaning
1 Calling number identification (CNI) delivery.
1 Neither network-provided delivered use - provided number
delivered, not applicable, or not recorded.
2 Network-provided number delivered user-provided
number delivered
3 Network-provided number not delivered user-provided
number delivered
2 Calling party subaddress delivery
1 Feature not used or not recorded
2 Feature used
3 Called party subaddress delivery
*
2 Feature used
4 Low layer compatibility information delivery.
*
2 Feature used
5 High layer compatibility information delivery.
*
2 Feature used
6 User-to-User Information Fast/ Select
2 Feature used, presumed delivered
3 Feature used, but not delivered
NTP 297-4102-124 04.01 February 2009
For CS 1500
7 1-4 Automatic callback - activation
8 1-5 Automatic callback - resolution
9 1-2 ISDN flexible calling
10 Call Waiting Originating
2 Feature used
11 Dial Call Waiting
2 Feature used
12-15 0 Reserved
Table 8-AW: Data table B.1 (data table 801) - one-digit number
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0-9 One-digit number
2 hex C SIGN
Table 8-AX: Data table B.2 (data table 802) - three-digit number
Number of
BCD
Character
Possible
Value(s)
Meaning
1-3 Three-digit number
4 hex C SIGN
Table 8-AV: Data table 413 - Signaling or Supplementary Service Capabilities
Number of
BCD
Character
Possible
Value(s)
Meaning
February 2009 04.01 NTP 297-4102-124
For CS 1500
Table 8-AY: Data table B.3 (data table 803) - five-digit number
Number of
BCD
Character
Possible
Value(s)
Meaning
1-5 Five-digit number
6 hex C SIGN
Table 8-AZ: Data table B.4 (data table 804) - seven-digit number
Number of
BCD
Character
Possible
Value(s)
Meaning
1-7 0000000 -
9999999
24 bit Sequence number
8 hex C SIGN
Table 8-BA: Data table B.5 (data table 805) - nine-digit number
Number of
BCD
Character
Possible
Value(s)
Meaning
1-9 Nine-digit number
10 hex C SIGN
NTP 297-4102-124 04.01 February 2009
For CS 1500
Table 8-BB: Data table C.147 - audit flag
Number of
BCD
Character
Possible
Value(s)
Meaning
1 0 All data are valid for audit.
1 Some SPCS data are not valid for audit.
2 Some transmitter data are not valid for audit.
3 Some SPCS and transmitter data are not valid for audit.
4 Some recording-exchange data are not valid for audit.
5 Some recording-exchange and SPCS data are not valid for audit.
6 Some recording-exchange and transmitter data are not valid for audit.
7 Some recording-exchange, SPCS, and transmitter data are not valid for
audit.
2 hex C SIGN
February 2009 04.01 NTP 297-4102-124
For CS 1500
9-1
Section 9: Bellcore structure codes
9Introduction
This section describes the Bellcore Automatic Message Accounting (AMA) format,
that complies the technical requirements set forth in the Bellcore documents, Bellcore
Automatic Message Accounting Format (BAF) Requirements (NWT-001100) and
Automatic Message Accounting (TR-TSY-000508).
Note: The information contained in this section is subject to change
without notice, since Nortel reserves the right to make changes in
equipment design or components as progress in engineering or
manufacturing methods may warrant.
Table 9-A: Structure codes per call type
Call
Type
Codes
Call Type Condition Structure
Codes
001 Detailed Message
Rate, Timed, MBI
Answered, LDC, TNN, MDR 50120
Answered, LDC, TNN, No MDR 10120
Answered, LDC, No TNN, MDR 40120
Answered, LDC, No TNN, No MDR 00120
Answered, No LDC, TNN, MDR 50020
Answered, No LDC, TNN, No MDR 10020
Answered, No LDC, No TNN, MDR 40020
Answered, No LDC, No TNN, No MDR 00020
Unanswered, TNN, MDR 50021
Unanswered, TNN, No MDR 10021
Unanswered, No TNN, MDR 40021
NTP 297-4102-124 04.01 February 2009
For CS 1500
9-2 Bellcore structure codes
Unanswered, No TNN, No MDR 00021
002 Message Rate,
Timed, MBI
Rate, Untimed, MBI
004 Message Rate,
Untimed, MBI
Rate, Timed, No MBI
Call
Type
Codes
Codes
Bellcore structure codes 9-3
February 2009 04.01 NTP 297-4102-124
For CS 1500
006 Station Paid, DDD
and IDDD (except
Bezeq)
007 IDDD (for Bezeq only) Answered, LDC, TNN, MDR 50101
Call
Type
Codes
Codes
NTP 297-4102-124 04.01 February 2009
For CS 1500
008 INWATS Answered, LDC, No TNN, No MDR 00179
009 Directory Assistance
(Local)
011 Feature Activation Answered, No LDC, No TNN, No MDR
Answered, No LDC, No TNN, MDR
00671
40671
033 Directory Assistance
(Toll)
Call
Type
Codes
Codes
February 2009 04.01 NTP 297-4102-124
For CS 1500
067 Flat Rate Answered, LDC, TNN, MDR 50101
068 OUTWATS Answered, LDC, TNN, No MDR 10177
Call
Type
Codes
Codes
NTP 297-4102-124 04.01 February 2009
For CS 1500
Note: Abbreviations: MBI, message billing index; TNN, trunk network
number; LDC, long duration call; MDR, message detailed recording
119 Terminating Access
Record
Table 9-B: Structure code 00001
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Sensor Identification 3 8
Recording Exchange Type 4 4
Recording Exchange Identification 5 8
Date 6 6
Timing Indicator 7 6
Study Indicator 8 8
Answer 9 2
Service Observed, Traffic Sampled 10 2
Operator Action 11 2
Service Feature 12 4
Originating NPA 13 4
Call
Type
Codes
Codes
February 2009 04.01 NTP 297-4102-124
For CS 1500
Originating Number 14 8
Terminating Number 17 16
Connect Time 18 8
Elapsed time 19 10
Table 9-C: Structure code 00002
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
Elapsed Time 19 10
Circuit Date 6 6
Circuit Time 18 8
Table 9-B: Structure code 00001
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
-end of table-
Table 9-D: Structure code 00015
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
Elapsed Time 19 10
WATS Indicator 28 2
WATS Band or Type Indicator 29 4
Table 9-C: Structure code 00002
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Table 9-E: Structure code 00016
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
Elapsed Time 19 10
WATS Indicator 28 2
Circuit Date 6 6
Circuit Time 18 8
Table 9-F: Structure code 00019
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
NTP 297-4102-124 04.01 February 2009
For CS 1500
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
WATS Indicator 28 2
Table 9-G: Structure code 00020
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Table 9-F: Structure code 00019
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Connect Time 18 8
Elapsed Time 19 10
WATS Indicator 28 2
- end of table -
Table 9-H: Structure code 00021
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Table 9-G: Structure code 00020
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Overseas Indicator 15 2
Terminating NPA 16 6
Connect Time 18 8
Elapsed Time 19 10
WATS Indicator 28 2
Circuit Date 6 6
Circuit Time 18 8
- end of table -
Table 9-I: Structure code 00024
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Table 9-H: Structure code 00021
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Connect Time 18 8
WATS Indicator 28 2
Table 9-J: Structure code 00028
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
Table 9-I: Structure code 00024
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Elapsed Time 19 10
Table 9-K: Structure code 00068
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
Circuit Date 6 6
Circuit Time 19 10
Table 9-L: Structure code 00077
Information Data
Table
Number of
Characters
Call Type 1 4
Table 9-J: Structure code 00028
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
Elapsed Time 19 10
WATS Indicator 28 2
Table 9-M: Structure code 00078
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
NTP 297-4102-124 04.01 February 2009
For CS 1500
Connect Time 18 8
Elapsed Time 19 10
WATS Indicator 28 2
Circuit Date 6 6
Circuit Time 18 8
- end of table -
Table 9-N: Structure code 00079
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Table 9-M: Structure code 00078
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Connect Time 18 8
Elapsed Time 19 10
Table 9-O: Structure code 00087
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
WATS Indicator 28 2
Table 9-N: Structure code 00079
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Circuit Date 6 6
Circuit Time 18 8
- end of table -
Table 9-P: Structure code 00096
Information Data
Table
Number of
Characters
Record Descriptor Word 000 8
Hexadecimal Identifier 00 2
Structure Code 0 6
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Connect Time 18 8
Elapsed Time 19 10
Present Date 6 6
Table 9-O: Structure code 00087
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Present Time 18 8
- end of table -
Table 9-Q: Structure code 00101
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 16
Elapsed Time 19 10
Present Date 6 6
Present Time 18 6
- end of table -
Table 9-P: Structure code 00096
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Table 9-R: Structure code 00110
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
CLASS Feature Code 415 4
Date 6 6
Time 18 8
NPA 13 4
Directory Number 14 8
Count of Calling Information Delivered B.3 6
Count of Unavailable and Private Calling Information B.3 6
- end of table -
Table 9-S: Structure code 00115
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
February 2009 04.01 NTP 297-4102-124
For CS 1500
Connect Time 18 8
Elapsed Time 19 10
WATS Indicator 28 2
Present Date 6 6
Present Time 18 8
- end of table -
Table 9-T: Structure code 00120
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Table 9-S: Structure code 00115
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Connect Time 18 8
Elapsed Time 19 10
WATS Indicator 28 2
Present Date 6 6
Present Time 18 8
- end of table -
Table 9-U: Structure code 00128
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Table 9-T: Structure code 00120
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Connect Time 18 8
Present Date 6 6
Present Time 18 8
- end of table -
Table 9-V: Structure code 00140
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor type 2 4
Sensor identification 3 8
Recording office type 4 4
Recording office identification 5 8
Date of answer 6 6
Timing indicator 7 6
Study indicator 8 8
Answer indicator 9 2
Service observed, traffic sampled 10 2
Operator action 11 2
Service feature 12 4
Originating number 14 8
Terminating number 17 16
Answer time 18 8
Elapsed time 19 10
IC / INC prefix 57 6
Table 9-U: Structure code 00128
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Carrier connect date 6 6
Carrier connect time 18 8
Carrier elapsed time 19 10
IC / INC call event status 58 4
Trunk group number 83 6
Routing indicator 59 2
Dialing indicator 85 2
IC / INC ANI indicator 60 2
Coins collected 158 4
Coin deposit trouble indicator 159 4
- end of table -
Table 9-W: Structure code 00141
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor type 2 4
Sensor identification 3 8
Recording office type 4 4
Recording office identification 5 8
Date of answer 6 6
Timing indicator 7 6
Study indicator 8 8
Answer indicator 9 2
Service observed, traffic sampled 10 2
Operator action 11 2
Service feature 12 4
Table 9-V: Structure code 00140
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Originating number 14 8
Terminating number 17 16
Answer time 18 8
Elapsed time 19 10
IC / INC prefix 57 6
Carrier connect date 6 6
Carrier connect time 18 8
Carrier elapsed time 19 10
IC / INC call event status 58 4
Trunk group number 83 6
Routing indicator 59 2
Dialing indicator 85 2
IC / INC ANI indicator 60 2
Present date 6 6
Present time 18 8
Coins collected 158 4
Coin deposit trouble indicator 159 4
Table 9-X: Structure code 00177
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Table 9-W: Structure code 00141
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
Elapsed Time 19 10
WATS Indicator 28 2
Present Date 6 6
Present Time 18 8
- end of table -
Table 9-Y: Structure code 00179
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
February 2009 04.01 NTP 297-4102-124
For CS 1500
Connect Time 18 8
Elapsed Time 19 10
Present Date 6 6
Present Time 18 8
- end of table -
Table 9-Z: Structure code 00360
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date of Answer 6 6
Study Indicator 8 8
Answer Indicator 9 2
Dialed NPA 13 4
Dialed Number 14 8
Destination Overseas Indicator 15 2
Destination NPA 16 6
Destination Number 17 8
NTP 297-4102-124 04.01 February 2009
For CS 1500
Answer Time 18 8
Elapsed Time 19 10
IC/INC Prefix 57 6
Carrier Connect Date 6 6
Carrier Connect Time 18 8
Elapsed Time From Carrier Connect 19 10
IC/INC Call Event Status 58 4
Trunk Group Number 83 6
Routing Indicator 59 2
Dialing Indicator 85 2
ANI Indicator 60 2
Customer's RAO Number 46 4
Originating LATA 197 4
Table 9-AA: Structure code 00362
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date of Answer 6 6
Study Indicator 8 8
Table 9-Z: Structure code 00360
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Dialed NPA 13 4
Dialed Number 14 8
Answer Time 18 8
Elapsed Time 19 10
IC/INC Prefix 57 6
ANI Indicator 60 2
Present Date 6 6
Present Time 18 8
- end of table -
Table 9-AA: Structure code 00362
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Table 9-AB: Structure code 00363
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date of Answer 6 6
Study Indicator 8 8
Dialed NPA 13 4
Dialed Number 14 8
Answer Time 18 8
Elapsed Time 19 10
IC/INC Prefix 57 6
February 2009 04.01 NTP 297-4102-124
For CS 1500
ANI Indicator 60 2
Alternate Billing Number 138 12
Present Date 6 6
Present Time 18 8
- end of table -
Table 9-AC: Structure code 00364
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date of Answer 6 6
Study Indicator 8 8
Table 9-AB: Structure code 00363
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Dialed NPA 13 4
Dialed Number 14 8
Answer Time 18 8
Elapsed Time 19 10
- end of table -
Table 9-AD: Structure code 00365
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date of Answer 6 6
Study Indicator 8 8
Table 9-AC: Structure code 00364
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Dialed NPA 13 4
Dialed Number 14 8
Answer Time 18 8
Elapsed Time 19 10
- end of table -
Table 9-AD: Structure code 00365
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Table 9-AE: Structure code 00366
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date of Answer 6 6
Study Indicator 8 8
Dialed NPA 13 4
Dialed Number 14 8
Answer Time 18 8
Elapsed Time 19 10
Present Date 6 6
Present Time 18 8
- end of table -
February 2009 04.01 NTP 297-4102-124
For CS 1500
Table 9-AF: Structure code 00367
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date of Answer 6 6
Study Indicator 8 8
Dialed NPA 13 4
Dialed Number 14 8
Answer Time 18 8
Elapsed Time 19 10
Present Date 6 6
Present Time 18 8
NTP 297-4102-124 04.01 February 2009
For CS 1500
Table 9-AG: Structure code 00368
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date of Answer 6 6
Study Indicator 8 8
Dialed NPA 13 4
Dialed Number 14 8
Answer Time 18 8
Elapsed Time 19 10
Circuit Date 6 6
Circuit Time 26 8
- end of table -
February 2009 04.01 NTP 297-4102-124
For CS 1500
Table 9-AH: Structure code 00369
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date of Answer 6 6
Study Indicator 8 8
Dialed NPA 13 4
Dialed Number 14 8
Answer Time 18 8
Elapsed Time 19 10
Circuit Date 6 6
Circuit Time 26 8
- end of table -
NTP 297-4102-124 04.01 February 2009
For CS 1500
Table 9-AI: Structure code 00614
Information Data
Table
Number of
Characters
Structure Code 0 6
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Connect Time 18 8
- end of table -
Table 9-AJ: Structure code 00625
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
February 2009 04.01 NTP 297-4102-124
For CS 1500
Date of Answer 6 6
Study Indicator 8 8
Answer Time 18 8
Elapsed Time 19 10
Inter-LATA Carrier/International Carrier Prefix 57 6
Inter-LATA Carrier/International Carrier Call Event
Status
58 4
ANI Indicator 60 2
- end of table -
Table 9-AJ: Structure code 00625
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Table 9-AK: Structure code 00627
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date of Answer 6 6
Study Indicator 8 8
Answer Time 18 8
Elapsed Time 19 10
Carrier Connect Data 6 6
Status
58 4
February 2009 04.01 NTP 297-4102-124
For CS 1500
ANI Indicator 60 2
Present Date 6 6
Present Time 18 8
- end of table -
Table 9-AL: Structure code 00637 or 00629
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date of Answer 6 6
Study Indicator 8 8
Answer Time 18 8
Elapsed Time 19 10
Table 9-AK: Structure code 00627
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Carrier-Connect Date 6 6
Carrier-Connect Time 18 8
Status
58 4
ANI Indicator 60 2
WATS Indicator 28 2
WATS Band or Type Indicator

29 4
- end of table -
Table 9-AM: Structure code 00641 or 00633
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date of Answer 6 6
Study Indicator 8 8
Table 9-AL: Structure code 00637 or 00629
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Answer Time 18 8
Elapsed Time 19 10
Status
58 4
ANI Indicator 60 2
WATS Indicator 28 2
Present Date 6 6
Present Time 18 8
- end of table -
Table 9-AM: Structure code 00641 or 00633
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Table 9-AN: Structure code 00653
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date of Answer 6 6
Study Indicator 8 8
Answer Time 18 8
Elapsed Time 19 10
Status
58 4
- end of table -
February 2009 04.01 NTP 297-4102-124
For CS 1500
Table 9-AO: Structure code 00654
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date of Answer 6 6
Study Indicator 8 8
Answer Time 18 8
Elapsed Time 19 10
Status
58 4
Present Date 6 6
Present Time 18 8
NTP 297-4102-124 04.01 February 2009
For CS 1500
Table 9-AP: Structure code 00655
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Time 18 8
Overflow Peg Count 128 6
Overflow Prefix 128 6
- end of table -
Table 9-AQ: Structure code 00671
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
February 2009 04.01 NTP 297-4102-124
For CS 1500
Study Indicator 8 8
Answer 9 2
Time 18 8
- end of table -
Table 9-AR: Structure code 01030
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Activating NPA 13 4
Activating Number 14 8
Far-end Overseas Indicator 15 2
Far-end NPA 16 6
Far-end Number 17 8
Time 18 8
Elapsed Time 19 10
Table 9-AQ: Structure code 00671
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
CLASS Functions 330 4
CLASS Status 331 4
Screen List Size for SCF/SCA B.2 4
Screen List Size for SCR B.2 4
Screen List Size for SDR B.2 4
- end of table -
Table 9-AS: Structure code 09003
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Time 18 8
NPA Number 14 8
Usage Count B.3 6
NPA Number 14 8
Usage Count B.3 6
NPA Number 14 8
Usage Count B.3 6
Table 9-AR: Structure code 01030
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
NPA Number 14 8
Usage Count B.3 6
NPA Number 14 8
Usage Count B.3 6
- end of table -
Table 9-AT: Structure code 09013
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Time 18 8
Generic Issue B.3 6
Type of Tracer 40 4
Sequence Number B.2 4
- end of table -
Table 9-AU: Structure code 09014
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Table 9-AS: Structure code 09003
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Date 6 6
Time 18 8
Generic Issue B.3 6
Type of Tracer 40 4
Sequence Number B.2 4
Record Count B.4 8
Block Count B.3 6
- end of table -
Table 9-AV: Structure code 09036
Information Data
Table
Number of
Characters
Structure Code 0 6
Call Type 1 4
Date Tape Recording Started 6 6
Time Tape Recording Started 18 8
Collector Program Generic Number 120 6
Type of Tracer 40 4
Tape Sequence Number C.1 4
Tape Transport Number C.71 2
- end of table -
February 2009 04.01 NTP 297-4102-124
For CS 1500
Table 9-AW: Structure code 09037
Information Data
Table
Number of
Characters
Structure Code 0 6
Call Type 1 4
Date Tape Recording Completed 6 6
Time Tape Recording Completed 18 8
Program Generic Number 120 6
Type of Tracer 40 4
Tape Sequence Number C.1 4
Tape Transport Number C.71 2
Count of Records C.3 8
Count of Blocks C.2 6
Count of Collector Logical Data Sets C.146 6
Table 9-AX: Structure code 09053
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Time 18 8
NTP 297-4102-124 04.01 February 2009
For CS 1500
AMA Sequence Number 140 6
Type of Tracer 40 4
Audibility Flag C.147 2
Number of Billing Registers Obtained 804 8
Number of Billing Registers to Process 804 8
Number of Billing Registers Processed 804 8
Number of Billing Registers Active 804 8
Total Number of Lost Billing Registers 804 8
Number of AMA Call Records sent to HSO 804 8
Number of AMA Call Records Received 804 8
- end of table -
Table 9-AY: Structure code 09054
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Time 18 8
Type of Tracer 40 4
Number of Billing Registers Obtained 804 8
Number of Billing Registers to Process 804 8
Table 9-AX: Structure code 09053
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Number of Billing Registers Processed 804 8
Number of Billing Registers Active 804 8
Total Number of Lost Billing Registers 804 8
Number of AMA Call Records Received 804 8
- end of table -
Table 9-AZ: Structure code 09055
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Time 18 8
Type of Tracer 40 4
1st Hour Lost Calls 802 4
2nd Hour Lost Calls 802 4
3rd Hour Lost Calls 802 4
4th Hour Lost Calls 802 4
Table 9-AY: Structure code 09054
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
21st Hour Lost Calls 802 4
22nd Hour Lost Calls 802 4
23rd Hour Lost Calls 802 4
Total Processed in Last 24-Hour Period 804 8
- end of table -
Table 9-BA: Structure code 09056
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Table 9-AZ: Structure code 09055
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Date 6 6
Time 18 8
Type of Tracer 40 4
Number of Billing Registers Backed-up 804 8
Number of Billing Registers Retrieved 804 8
Total Number of Lost Backed-up Calls 804 8
- end of table -
Table 9-BB: Structure code 10001
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Table 9-BA: Structure code 09056
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Connect Time 18 8
Elapsed Time 19 10
Trunk Network Number 20 8
- end of table -
Table 9-BC: Structure code 10002
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Table 9-BB: Structure code 10001
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Connect Time 18 8
Elapsed Time 19 10
Circuit Date 6 6
Circuit Time 18 8
- end of table -
Table 9-BD: Structure code 10015
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
Table 9-BC: Structure code 10002
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Elapsed Time 19 10
WATS Indicator 28 2
- end of table -
Table 9-BE: Structure code 10016
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
Elapsed Time 19 10
WATS Indicator 28 2
Table 9-BD: Structure code 10015
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Circuit Date 6 6
Circuit Time 18 8
- end of table -
Table 9-BF: Structure code 10019
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
WATS Indicator 28 2
- end of table -
Table 9-BE: Structure code 10016
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Table 9-BG: Structure code 10020
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
Elapsed Time 19 10
WATS Indicator 28 2
- end of table -
February 2009 04.01 NTP 297-4102-124
For CS 1500
Table 9-BH: Structure code 10021
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
Elapsed Time 19 10
WATS Indicator 28 2
Circuit Date 6 6
Circuit Time 18 8
- end of table -
NTP 297-4102-124 04.01 February 2009
For CS 1500
Table 9-BI: Structure code 10024
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
WATS Indicator 28 2
- end of table -
Table 9-BJ: Structure code 10028
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
February 2009 04.01 NTP 297-4102-124
For CS 1500
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
- end of table -
Table 9-BK: Structure code 10068
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Table 9-BJ: Structure code 10028
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Connect Time 18 8
Circuit Date 6 6
Circuit Time 18 8
- end of table -
Table 9-BL: Structure code 10077
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Table 9-BK: Structure code 10068
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Connect Time 18 8
Elapsed Time 19 10
WATS Indicator 28 2
- end of table -
Table 9-BM: Structure code 10078
Information Data
Table
Number of
Characters
Call Type 1 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Table 9-BL: Structure code 10077
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Connect Time 18 8
Elapsed Time 19 10
WATS Indicator 28 2
Circuit Date 6 6
Circuit Time 18 8
- end of table -
Table 9-BM: Structure code 10078
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Table 9-BN: Structure code 10079
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
Elapsed Time 19 10
- end of table -
Table 9-BO: Structure code 10080
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
NTP 297-4102-124 04.01 February 2009
For CS 1500
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
Elapsed Time 19 10
Circuit Date 6 6
Circuit Time 18 8
- end of table -
Table 9-BO: Structure code 10080
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Table 9-BP: Structure code 10087
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
WATS Indicator 28 2
Circuit Date 6 6
Circuit Time 18 8
- end of table -
NTP 297-4102-124 04.01 February 2009
For CS 1500
Table 9-BQ: Structure code 10101
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
Elapsed Time 19 10
Present Date 6 6
Present Time 18 8
- end of table -
February 2009 04.01 NTP 297-4102-124
For CS 1500
Table 9-BR: Structure code 10115
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
Elapsed Time 19 10
WATS Indicator 28 2
Present Date 6 6
Present Time 18 8
- end of table -
NTP 297-4102-124 04.01 February 2009
For CS 1500
Table 9-BS: Structure code 10120
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
Elapsed Time 19 10
WATS Indicator 28 2
Present Date 6 6
Present Time 18 8
- end of table -
February 2009 04.01 NTP 297-4102-124
For CS 1500
Table 9-BT: Structure code 10128
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect Time 18 8
Present Date 6 6
Present Time 18 8
- end of table -
Table 9-BU: Structure code 10177
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
NTP 297-4102-124 04.01 February 2009
For CS 1500
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect time 18 8
Elapsed Time 19 10
WATS Indicator 28 2
Present Date 6 6
Present Time 18 8
- end of table -
Table 9-BV: Structure code 10179
Information Data
Table
Number of
Characters
Call Type 1 4
Sensor Type 2 4
Table 9-BU: Structure code 10177
Information Data
Table
Number of
Characters
February 2009 04.01 NTP 297-4102-124
For CS 1500
Modules
Date 6 6
Study Indicator 8 8
Answer 9 2
Connect time 18 8
Elapsed Time 19 10
Present Date 6 6
Present Time 18 8
- end of table -
Module Explanation Table
000 Last appended module CF
042 Global Sequence number CA
043 Unique Sequence number CA
070 Used for ISDN with features CA
071 Used for ISDN without features CB
087 Used for CPC Calling Party Category CC
101 Digits Dialed Module CD
Table 9-BV: Structure code 10179
Information Data
Table
Number of
Characters
NTP 297-4102-124 04.01 February 2009
For CS 1500
Note: Bellcore requires that the last appended module will be appended
by a FINAL module (MODULE CODE 000)
104 Outgoing Trunk Identification CD
105 Completion Code CD
116 Redirection Information CD
130 Reject Information CD
164 Used for Called Number more than 15 digit length. CE
181 Incoming Trunk Identification CD
Table 9-BW: Module Code 000 - Final Module
Information Table Number of
Characters
Byte
Offset
Module Code Identification (000C) 88 4 0
Total no. of bytes 2
Table 9-BX:
Module code 42 -Global Sequence number
Information Data
Table
Number of
Characters
Module Code 88 4
Seven-Digit Number 804 8
Table 9-BY:
Module code 43 -Unique Sequence number
Information Data
Table
Number of
Characters
Module Code 88 4
Seven-Digit Number 804 8
Table 9-BZ: Module Code 070 - ISDN call with features
Characters
Byte
Offset
Module Code Identification 88 4 0
Bearer Capability/Call Code 412 4 2
Network Interworking 410 2 4
February 2009 04.01 NTP 297-4102-124
For CS 1500
Note: Used for calls routing depends upon Incoming TG CLI, DNs
definition, ISUP CPC (Calling Party Category) or R2 category receiving
and the needed code changes in order to support it
Note: More than 18 digits.
Signaling or Supplementary Service Capability 413 16 8
Release Cause Indicator 411 6 8
Table 9-CA: Module Code 071 Basic ISDN call
Characters
Byte
Offset
Module Code Identification 88 4 0
Bearer Capability/Call Code 412 4 2
Network Interworking 410 2 4
Release Cause Indicator 411 6 5
Table 9-CB:
Module code 087 -CPC (CAT)
Information Data
Table
Number of
Characters
Module Code 88 4
Directory Number Description 206 4
Table 9-CC:
Module code 101 - Digits Dialed Module
Information Data
Table
Number of
Characters
Module Code 88 4
Significant Digits in Next Fields 55 4
Digits Dialed 1 32 12
Digits Dialed 2 33 14
Access Code 803 6
NTP 297-4102-124 04.01 February 2009
For CS 1500
Note: Used to provide ability to capture the call Complrtion
Note: Used to provide ability to capture Redirection Calls
Note: Used to provide Treatment Characteristic and Termination Cause
to CDR in case of call rejected
Table 9-CD:
Module code 104 -Outgoing Trunk Identification
Information Data
Table
Number of
Characters
Module Code 88 4
Trunk identification 244 10
Table 9-CE:
Module code 105 -Completion Code
Information Data
Table
Number of
Characters
Module Code 88 4
Completion Indicator 280 4
Table 9-CF:
Module code 116 -Redirection Information
Information Data
Table
Number of
Characters
Module Code 88 4
Call Redirection/Deflection Indicator 169 6
Significant Digits in Next Field 55 4
Digits 1 126 16
Digits 2 126 16
Table 9-CG:
Module code 130 -Reject Information
Information Data
Table
Number of
Characters
Module Code 88 4
Facility Release Code 338 6
Call Characteristic 339 4
Table 9-CH: Module Code 164 - Number
Characters
Byte
Offset
February 2009 04.01 NTP 297-4102-124
For CS 1500
Note: This module provides the means to record lengthy numbers that
cannot be recorded in the structure applicable to the call (called number
that is more than 15 digits).If more than 15 digits are dialed, the
Terminating Number field will be populated with the 15 most significant
digits. The extra digits will be populated in an appended module, changing
the BAF record.
Module Code Identification (164C) 88 4 0
Number Code Identity (2C) 76 2 2
Country Code or DNIC 165 6 3
Significant Digits in Next Field 55 4 6
Digits 126 16 8
Table 9-CI:
Module code 181 -Incoming Trunk Identification
Information Data
Table
Number of
Characters
Module Code 88 4
Trunk identification 244 10
NTP 297-4102-124 04.01 February 2009
For CS 1500
February 2009 04.01 NTP 297-4102-124
For CS 1500
10-1
A
Automatic Message Accounting
administration 1
Administration and maintenance 2
alarm conditions 1
call detail recording 3
Data storage 3
call types
description 1
Generic 406.22 and later 400-Series generics
1
capacity and reliability 1
Data Modification 6
AMA 8
AREA 7
CNFG 8
DN 6
ODQ 10
ROUT 10
TG 11
THGP 6
TRNS 7
data transmission and processing 8
general description 1
maintenance 1
no-charge conditions 4
Initialization 5
No billing registers 7
SYSLOAD 4
TOD clock faults 6
operation 1
Billing control 2
Call classification 2
Calling number identification 2
Charge determination 1
pulse rate determination 4
record types 1
Long-duration 1
miscellaneous and statistical 2
usage-sensitive custom calling feature 2
Recording
operation 6
recording system 4
required hardware 1
special studies
TRAF 3
structure codes
Generic 406.22 and later 400-Series generics
per call type 1
Generic 406.22 and later Series generics
table 1
system summary 3
Call classification 5
trouble clearing 1
CED 1
Trouble messages 2
usage sensitive billing 8
C
Centralized Automatic Message Accounting
I
Integrated Billing Storage and Retrieval
Downstream processing 3
feature description 2
file content 3
file header 4
Integrated Services Digital Network
BRI
AMA recording 1
primary rate interface
Section 10: Index
10-2 Index
NTP 297-4102-12404.01 February 2009
For CS 1500
AMA recording
Bearer 1
billing numbers 1
Calling Number Identification Services 2
Interworking 2
Signaling services 2
INWATS Overflow
feature description 3
L
Local Automatic Message Accounting
Copyright 2009
Nortel, All Rights Reserved
NTP number: NTP 297-4102-124
Status: Draft
For Release 02.00i
Issue: 04.01
Date: February 2009

CS1500 AMA System

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

CS1500 AMA System

Hochgeladen von

Copyright:

Verfügbare Formate

NTP 297-4102-124

Carrier Voice over IP

Das könnte Ihnen auch gefallen