Lucent1 PDF

Lucent Gateway Platform
Billing and Traffic Collection Guide
Part Number 255-400-403R3.8

Issue 5, January 9, 2004
Software Version 3.8
Copyright 2005 Lucent Technologies

All Rights Reserved
Copyright 2005 by Lucent Technologies. All Rights Reserved.
This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any
entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts, or licensing, without the express written
consent of the Customer Training and Information Products organization and the business management owner of the material.
For permission to reproduce or distribute, please contact the following:
Product Development Manager 1 888-LTINFO6 (domestic)

1-317-322-6848 (international)
Notice
Every effort has been made to ensure that the information in this document was complete and accurate at the time of printing. However,
information is subject to change.
Mandatory customer information
Trademarks
All trademarks and service marks specified herein are owned by their respective companies.
Ordering information
The order number of this document is 255-400-403R3.8.
Support
Technical support
Please contact your Lucent Technologies Local Customer Support Team (LCS) for technical questions about the information in this document.
Information product support
To comment on this information product online, go to http://www.lucent-info.com/comments or email your comments to comments@lucent.com.
Billing and Traffic Collection Guide Issue 5, January 9, 2004
Manual Contents
1. Contents of this Manual
This volume contains descriptions of the applications for capturing billing and traffic
statistical information as well as procedures for installing and updating these
applications.
Release Notes can be obtained by contacting Telica Technical Services at 888-440-

8354 or 888-440-TELI.
Following is a listing of the tabs and documents of this manual. Documents are
listed by name followed with its section number and its issue number and date on the
same line.
Contents 150-050-100 Issue 5, Jan. 9, 2004

About This Guide 150-100-000 Issue 2, May 13, 2003
1. Pro Billing
PlexView Pro Billing System 150-200-100 Issue 2, May 13, 2003
2. ASCII Billing
PlexView ASCII Billing Server 150-200-200 Issue 2, Dec. 19, 2003
3. AMA Lite
AMA Lite Billing Servers 150-200-300 Issue 2, Oct. 10, 2003
4. Traffic Collection
PlexView Traffic Collection Application 150-200-400 Issue 3, Dec. 12, 2003
5. Billing and Traffic System
PlexView Billing and Traffic System 150-200-500 Issue 4, Jan. 9, 2004
6. ASCII Billing Reports
ASCII Billing Reports 150-300-100 Issue 5, Jan. 9, 2004
7. AMA Lite Reports
AMA Lite Reports 150-300-200 Issue 2, Jan. 9, 2004
8. Traffic Statistics Reports
Traffic Statistics Reports 150-300-300 Issue 3, Jan. 9, 2004
Telica, Inc.
9. Procedures
Task Oriented Practices (TOPS) 150-500-100 Issue 2, May 13, 2003
Procedures Checklist 150-500-200 Issue 4, Jan. 9, 2004
Provisioning Task Index List 150-500-300 Issue 2, Jan. 9, 2004
Detailed Level Procedures 150-500-400
10. Acronyms
Acronyms 150-800-000 Issue 3, Nov. 14, 2003
Appendix
Appendix A – Release Causes 150-900-000 Issue 1, Mar. 28, 2003
Index
Index 150-900-900 Issue 3, Jan. 9, 2004
Telica, Inc.
Contents
1. PlexView Pro Billing System ........................................................1-1

1.1 Scope ........................................................................................................1-1
1.2 Overview ..................................................................................................1-1
1.3 PlexView Pro Billing System Requirements ...........................................1-2
1.4 Automatic Message Accounting Data Networking System..................... 1-2
1.5 PlexView AMA Billing Module ..............................................................1-2
2. PlexView ASCII Billing Server (ABS).........................................2-1

2.1 Introduction ..............................................................................................2-1
2.2 Features .................................................................................................... 2-2
2.3 How the Transfer Works ..........................................................................2-2
2.4 Configuration and Operation....................................................................2-8
3. PlexView AMA Lite.......................................................................3-1

3.1 Introduction ..............................................................................................3-1
3.2 Features .................................................................................................... 3-2
4. PlexView Traffic Collection Application (TCA).........................4-1

4.1 Introduction ..............................................................................................4-1
4.2 Features .................................................................................................... 4-2
4.3 How Statistical Information is Generated ................................................4-3
4.4 Installation and Configuration................................................................4-14
5. PlexView Billing and Traffic System ...........................................5-1

5.1 Introduction ..............................................................................................5-2
5.2 Features .................................................................................................... 5-3
5.4 Provisioning for the Billing and Traffic System ......................................5-6
Contents Issue 5, January 9, 2004
6. ASCII Billing Reports .....................................................................6-1

6.1 Introduction ..............................................................................................6-2
6.2 CDR and ABS Formats ............................................................................6-2
6.3 ASCII-Format Master Record Field Descriptions ...................................6-9
6.4 Module Inclusion Rules .........................................................................6-60
6.5 Module Number 164 ..............................................................................6-69
6.6 Call Types, Structure Codes, and Modules ............................................6-72
6.7 Configuration and Operation..................................................................6-73
7. AMA Lite Reports ...........................................................................7-1

7.1 Introduction ..............................................................................................7-2
7.2 CDR and AMA Lite Formats ................................................................... 7-2
7.3 Module Inclusion Rules ...........................................................................7-8
7.4 Module Number 164 ..............................................................................7-16
7.5 Call Types, Structure Codes, and Modules ............................................7-19
7.6 Configuration and Operation..................................................................7-20
8. Traffic Statistics Reports ................................................................8-1

8.1 Introduction ..............................................................................................8-1
8.2 Types of Statistics and Reports ................................................................8-2
8.3 Installation and Configuration................................................................8-29
9. TOP Procedures...............................................................................9-1
9.1 Task Oriented Practices (TOPS) ..............................................................9-1
9.2 Procedures Checklist ................................................................................9-3
9.3 Provisioning Task Index List ...................................................................9-5
Telica, Inc ii
List of Figures
Figure 1-1. AMADNS Architecture................................................................................1-2
Figure 1-2. PlexView AMA Billing................................................................................1-3
Figure 2-1. PlexView ASCII Billing Conversion Details ...............................................2-3
Figure 3-1. PlexView AMA Billing Conversion Details ................................................3-3
Figure 4-1. PlexView TCA Statistics Retrieval Process .................................................4-4
Figure 5-1. The Plexus and the Billing and Traffic System............................................5-4
Figure 5-2. Traffic Collection Application .....................................................................5-5
Figure 6-1. Long Duration Call Sample........................................................................6-63
Figure 7-1. Long Duration Call Sample........................................................................7-10
Figure 9-1. Craft-port Login Screen..............................................................................9-43
List of Tables
Table 2-A. Sample abs.conf File.....................................................................................2-4
Table 3-A. Sample ama.conf File....................................................................................3-4
Table 4-A. Sample tsds.conf File ....................................................................................4-5
Table 4-B. Sample tsaa_<prefix>.conf File ...................................................................4-8
Table 5-A. plexusDc.ini File ...........................................................................................5-7
Table 5-B. Sample tsaa_<prefix>.conf File ...............................................................5-27
Table 6-A. ABS-supported AMA Call Types.................................................................6-3
Table 6-B. List of Fields in the Master Record...............................................................6-4
Table 6-C. Call Types Supported by the Plexus 9000 ..................................................6-10
Table 6-D. Structure Codes...........................................................................................6-11
Table 6-E. Module Numbers and Descriptions.............................................................6-60
Table 6-F. Call Forwarding Module 164 Population Chart ..........................................6-71
Table 6-G. Call Types, Modules and Structure Code 0625 .........................................6-74
Table 7-A. Call Types Supported by the Plexus 9000 ....................................................7-3
Table 7-B. Structure Codes .............................................................................................7-4
Table 7-C. Header of AMA Lite Record.........................................................................7-5
Table 7-D. Fields in the AMA Lite Record ....................................................................7-5
Table 7-E. List of Fields in the Master Record ...............................................................7-6
Table 7-F. Module Numbers and Descriptions ...............................................................7-8
Table 7-G. Call Types, Modules and Structure Code 0625 .........................................7-21
Table 7-H. Plexus 9000 AMA Record Mapping to Telcordia GR-1100 ......................7-25
Table 9-A. Sample abs.conf File.....................................................................................9-9
Table 9-B. abs.conf File ................................................................................................9-14
Table 9-C. Sample abs.conf File ...................................................................................9-19
Table 9-D. Sample ama.conf File..................................................................................9-23
Table 9-E . ama.conf File ..............................................................................................9-28
Table-9-F. ama.conf File...............................................................................................9-34
Table 9-G. Sample tsds.conf File ..................................................................................9-61
Table 9-H. Sample tsaa_<prefix>.conf File.................................................................9-62
iii Telica, Inc

Contents Issue 5, January 9, 2004
Table 9-I. S99PLXStats File ..........................................................................................9-63

Table 9-J. Display of Package Add...............................................................................9-63
Table 9-K. tsds.conf File ...............................................................................................9-68
Table 9-L. tsaa.conf File ...............................................................................................9-69
Table 9-M. tsds.conf File...............................................................................................9-79
Table 9-N. tsaa.conf File...............................................................................................9-80
Table 9-O. Display of Package Add..............................................................................9-81
Table 9-P. MAIN Entity Configuration Section of PlexusDC.ini File .........................9-92
Table 9-Q. Receiver Entity Configuration Section of PlexusDC.ini File .....................9-93
Table 9-R. Billing Entity Configuration Section of PlexusDC.ini File ........................9-93
Table 9-S. Output Options Section of PlexusDC.ini File ............................................9-95
Table 9-T. ASCII/BAF (AMA Lite) File Parameters Section of PlexusDC.ini File ....9-96
Table 9-U. PlexView Pro Parameters Section of PlexusDC.ini File ............................9-96
Table 9-V. ASCII and BAF Push Configuration ..........................................................9-97
Table 9-W. Statistics Entity Configuration Section of PlexusDC.ini File....................9-98
Table 9-X. S99PlexDC File (partial).............................................................................9-99
Table 9-Y. PlexusDc.ini File.......................................................................................9-104
Table 9-Z. S99PlexDC File (partial) ...........................................................................9-108
Table 9-AA. Display of Package Add.........................................................................9-108
Table 9-BB. S99PlexDC File (partial) ..........................................................................9-76
Table 9-CC. PlexusDc.ini File ......................................................................................9-81
Table 9-DD. S99PlexDC File (partial)..........................................................................9-86
Table 9-EE. Display of Package Add............................................................................9-87
Telica, Inc iv
Billing and Traffic Collection Guide Section 150-100-000
About This Guide

The Billing and Traffic Collection Guide describes PlexView Pro Billing,
ASCII Billing Server (ABS), AMA Lite and the Traffic Collection
Application (TCA) as well the Billing and Traffic System (BTS). It also
provides procedures to install and upgrade these applications on a Sun
server.
Architecture Prior to System Software Version 3.8

The Plexus handles billing and traffic collection differently depending
upon the system software version running on the switch. For a Plexus
with a version of software earlier than version 3.8 (i.e., 1.4 (aka 3.1.1.4),
3.5, 4.3 (aka 3.4.3)) two raw call detail records (CDRs) are generated for
every call and formatted in AMA like objects and written to a circular
buffer for billing on the switch. Traffic CDRs are formatted into their own
version and written to another circular buffer. On the Plexus, Generating
system to Data server Interface (GDI) transmitters are running. They read
the circular files and transmit the data over a TCP/IP connection to the
appropriate server (ABS, AMA Lite or PlexView Pro Billing and TCA)
where the data is collected by a GDI receiver and formatted into billing or
traffic data. Billing information could only be used by one server.
Architecture for System Software Version 3.8 or Higher

For a Plexus with software version 3.8 or greater, one CDR will be
generated for both billing and traffic and formatting of the CDR is not
done on the Plexus. Raw CDRs are transmitted in real time if the
connection to Billing and Traffic System (BTS) server is available. If a
BTS is not available, the CDRs are written to a circular buffer on the
Plexus.
At the BTS, a GDI receiver collects the data from the Plexus and
multiplexes the same CDR into a traffic collection handler and a billing
handler. Traffic collection CDRs will be formatted and maintained in
memory or disk file depending on the nature of the stats data. Billing
CDRs are formatted into AMA like objects. For ASCII billing, CDRs are
formatted and written by the billing handler and for PlexView Pro Billing,
data is written to a circular buffer and then sent to the Pro Billing Data
Server.
v Telica, Inc
Introduction Issue 2, May 13, 2003
Audience
This document is for system administrators, craft personnel, and operators
responsible for gathering billing and/or traffic statistics on one or more
associated servers and Plexus 9000 switches. It is assumed that you have
a working knowledge Unix and of the operations of a Sun server.
Part Number
The part number for the guide is PN-79-6021.
Related Documentation
Table A provides a listing and a description of all documentation, printed
and CD-ROM, available for the Plexus 9000.
Table A. Documentation
Part Manual Title Description
Number
79-6002 Plexus 9000 Installation and Contains Plexus 9000 installation and
Operations Manual provisioning procedures.
79-6003 Plexus 9000 TL1 Commands Provides a listing and description of all
Reference Guide the TL1 commands needed to provision
the Plexus 9000.
79-6004 Plexus 9000 Planning and Provides information regarding the items
Engineering Guide necessary for designing a Plexus 9000
installation site. These include such
things as: hardware specifications,
cabling requirements, cabling
schematics, floor plan requirements,
environmental requirements, and power
requirements. It also includes hardware
descriptions of chassis and modules.
79-6005 Plexus 9000 Core Consists of the Installation and
Documentation Set Operations Manual (79-6002); the TL1
Commands Reference Guide (79-6003);
and the Planning and Engineering Guide
(79-6004).
79-6006 Plexus 9000 Install and TL1 Consists of the Installation and
Documentation Set Operations Manual (79-6002) and the
TL1 Commands Reference Guide
(79-6003).
79-6007 Plexus 9000 Customer Contains the manuals and release notes
Documentation CD-ROM of the core documentation set in Adobe
Acrobat PDF format.
Telica, Inc vi

Number
79-6008 PlexView Pro Billing System Explains the procedures necessary to
User Guide operate, administer, and maintain the
Billing System.
79-6009 PlexView Pro Billing System Contains the Billing System manual in
User Guide CD-ROM Adobe Acrobat PDF format.
79-6010 PlexView Element Explains how to use the EMS to
Management System (EMS) provision and control the Plexus 9000.
User Guide
79-6011 PlexView Element Provides procedures for installing the
Management System EMS software on a Sun workstation. In
Installation Guide printed form, is bound with the
PlexView EMS User Guide.
79-6012 PlexView EMS Documentation Consists of the PlexView EMS User
CD-ROM Guide (79-6010), the PlexView EMS
Installation Guide (79-6011), and the
PlexView EMS Release Notes.
79-6014 Plexus 9000 Media Gateway Contains installation and provisioning
Installation and Operations procedures.
Manual
79-6015 Plexus 9000 Media Gateway Provides information regarding the items
Planning and Engineering necessary for designing a Plexus 9000
Guide Media Gateway installation site. These
include such things as: hardware
specifications, cabling requirements,
cabling schematics, floor plan
requirements, environmental
requirements, and power requirements.
It also includes hardware descriptions of
chassis and modules.
79-6016 Plexus 9000 Media Gateway Provides a listing and description of all
TL1 Commands Reference the TL1 commands needed to provision
Guide the Plexus 9000 Media Gateway.
79-6017 Plexus 9000 Media Gateway Contains the Plexus 9000 Media
Customer Documentation CD- Gateway manuals and release notes of
ROM core documentation set in Adobe
Acrobat PDF format.
79-6018 Plexus 9000 Media Gateway Consists of the Media Gateway
Core Documentation Set Installation and Operations Manual
(79-6014), the Media Gateway Planning
and Engineering Guide(79-6015), and
the Media Gateway TL1 Commands
Reference Guide (79-6016).
vii Telica, Inc


Number
79-6022 Maintenance and Provides information about maintaining
Troubleshooting Guide a Plexus, alarm tables and procedures for
maintaining and troubleshooting alarms.
79-6026 Billing and Traffic Collection Contains the Billing and Traffic
CD-ROM Collection Guide and release notes in
Adobe Acrobat PDF format.
Manual Organization
The title page of this guide displays the part number, issue number and
date, and release number. The Manual Contents follow the title page, and
list the various sections in the manual, and the issue number and date for
each document in a section. Comparing manual contents from one version
to the next enables you to quickly identify what has changed and what has
remained the same.
This Billing and Traffic Statistics Guide contains information about billing
and traffic applications. Billing and Traffic System (BTS), Traffic
Collection Application (TCA), ASCII Billing System (ABS) and AMA
Lite release notes can be obtained by contacting your sales engineer or
technical services personnel. Release notes contain a list of changes and
enhancements since the previous version.
This guide is organized into the following sections:

• The Introduction contains a description of this guide.
• PlexView Pro Billing System
• PlexView ASCII Billing Server
• PlexView AMA Lite
• PlexView Traffic Collection Application (TCA)
• PlexView Billing and Traffic System (BTS)
• TOP Procedures
• Acronyms
• Appendix – Release Causes
• Index
Telica, Inc viii

Using the CD-ROM

Like many manuals today, this one has a CD-ROM that may be inserted in
a pocket on the back of the binder cover or it may also be part of the
CD-ROM inserted in the Installation and Operation Manual. When
inserted into a drive, the CD-ROM will automatically open to the main
menu page. From this page, you can select the Guide.
When using the Guide you can move to different areas using the
bookmarks on the left side of the page. Clicking on the + sign in front of a
topic will expand it, clicking on the – sign will minimize it. Table of
Contents information in blue font will also move you to that identified
topic. Titles in blue font will return to the first page of the Guide.
Clicking on the title of the first page will return you to the Main Menu
page.
Conventions Used in This Guide

This guide uses the following conventions, when appropriate:
Convention Indicates
Courier new Command syntax
Italics Book titles, new terms, file names, emphasized
text
Angle brackets < > Parameter delimiters
Square brackes [ ] Optional parameters
ix Telica, Inc
NOTES:
Telica, Inc x
1. PlexView Pro Billing System
1.1 Scope ....................................................................................................................1-1
1.2 Overview ..............................................................................................................1-1
1.3 PlexView Pro Billing System Requirements .......................................................1-2
1.4 Automatic Message Accounting Data Networking System................................. 1-2
1.5 PlexView AMA Billing Module ..........................................................................1-2
1.5.1 Plexus 9000 Generating System...............................................................1-3
1.5.2 Data Server...............................................................................................1-4
1.5.3 Data Processing and Management System (DPMS) ...............................1-4
Note: To avoid local time synchronization problems, Telica strongly

recommends setting the Plexus system clock to use GMT.
1.1 Scope
This section describes the PlexView Pro Billing System (PPBS) available
from Telica to generate accurate call detail records (CDRs) in critical
revenue-generating environments. The PlexView ASCII Billing Server
(ABS), which also runs on a Sun computer platform, is described in
PlexView ASCII Billing Server (ABS), Section 110-220-150, of this
manual.
1.2 Overview
The PlexView Pro Billing System (PPBS) is a software package available
from Telica to work as an extension of the Plexus 9000 to generate
accurate call detail records (CDR) in critical revenue-generating
environments with non-stop, non-drop performance. It interoperates with
third party billing management systems from Lucent and others, and
supports the verification and viewing of historical records and files. The
PlexView Pro Billing System supports the AMADNS (automatic message
accounting data networking system) architecture.
PlexView Pro Billing System Issue 2, May 13, 2003
1.3 PlexView Pro Billing System Requirements

The PlexView Pro Billing System is available either as a standalone
application, as a branch of the PlexView Billing and Traffic System (BTS)
or with the PlexView Element Management System (EMS) and requires
the following:
• Sun Solaris 7 or 8 System with 256MB memory and a 10/100
Ethernet card. The minimum recommended system is the
Sun Ultra 10.
• Plexus 9000 running software version Release 2.1 or greater.
Procedures to operate, administer and maintain the PlexView Pro Billing
System are available in PlexView Pro Billing System Installation and
Operation Manual. Procedures allow customization to meet many billing
configuration options and support new AMA structure codes and module
formats.
1.4 Automatic Message Accounting Data Networking System

Automatic Message Accounting (AMA) is the process of measuring and
accounting for the use of switch network resources by customers and
carriers. The AMADNS architecture is illustrated in Figure 1-1. Data that
is generated during the process must be moved from generation points
(e.g., Plexus 9000) to application points (e.g., Billing Systems). During
the transfer the data must be processed and managed. This is done by the
Data Server and the Data Processing and Management System (DPMS).
Generating Data Data Processing Application

System Server and Management System
System
P269-AA
01-08-01
Figure 1-1. AMADNS Architecture
1.5 PlexView AMA Billing Module

The PlexView Pro Billing System is the intermediary between the Plexus
9000 and the Data Processing and Management System (DPMS). It acts
as the Data Server that receives generates call detail records (CDRs) and
formats them into Bellcore AMA Format (BAF) records for the DPMS.
Figure 1-2 illustrates the PlexView Pro Billing architecture.
1-2 Telica, Inc.

Sun
Work
Station
CDRs BAF Files

Plexus 9000 FTP
TCP/IP
Active
Data Processing Billing
PlexView Billing and Management
Standby Module Application
System
Sun Server
Circular
Buffer
Memory Switch Data
Collection DDI_Client
Interface
ry
y
ar
ma
nd
Pri
co
Se
P345-AA
01-08-01 Formatter File
Interface Storage
Figure 1-2. PlexView AMA Billing
1.5.1 Plexus 9000 Generating System

The generating system is the Plexus 9000 that generates CDRs and
transmits them to the data server through the Ethernet ports and network
using TCP/IP every 5 seconds. The generating system may also be
referred to as a billing source, a network element or a switch.
If the Plexus fails over to the standby System Processor, it immediately

begins transmitting records. If communication between the Plexus and the
PlexView Billing Module and Sun workstation is lost, the Plexus keeps
records in a circular buffer while continually trying to reestablish
communication. When communication is restored, the Plexus will request
the last sequence number from the billing module workstation and then it
will send all stored records.
Telica, Inc. 1-3

PlexView Pro Billing System Issue 2, May 13, 2003
1.5.2 Data Server

The data server receives CDRs from the Plexus 9000 and completes the
following:
• Formats the CDRs in the Automatic Message Accounting Data
Network System (AMADNS) format so they can be sent to the
Data Processing and Management System (DPMS).
• Stores the formatted AMADNS records until they are transmitted
to the DPMS.
• Sends the primary AMADNS records when scheduled or as soon
as they are formatted and ready and stores a copy as a secondary
file.
• Transmits secondary AMADNS billing records when requested.
1.5.3 Data Processing and Management System (DPMS)

The DPMS is any system that processes AMADNS billing records. It
might also be referred to as a billing entity, a host collector or a client or
billing application. The Plexview Billing Module can communicate with
DPMSs available from Lucent, TeleSciences, CGI, AceComm, MetaPath
and Ericson/HP.
1-4 Telica, Inc.

2. PlexView ASCII Billing Server (ABS)
2.1 Introduction ..........................................................................................................2-1

2.2 Features ................................................................................................................2-2
2.3 How the Transfer Works ......................................................................................2-2
2.3.1 ABS Verification of Plexus 9000 IP Address .......................................... 2-3
2.3.2 Fields of the abs.conf File ........................................................................2-5
2.3.3 Plexus 9000 and ABS Connection ...........................................................2-7
2.3.4 ABS Receipt of CDR ...............................................................................2-7
2.3.5 Transfer of Information............................................................................2-8
2.4 Configuration and Operation................................................................................2-8

2.1 Introduction
The PlexView ASCII Billing Server (ABS), which runs on a Sun
computer platform, works with the Plexus 9000 switch to convert Call
Detail Records (CDRs) to an ASCII record format. The Plexus 9000
sends a CDR for each attempted call over TCP/IP to the ABS. The ABS
then extracts the information from the CDR and writes it to a master
ASCII record format, storing the record on the Sun server. Each record is
appended to an active file over a previously configured amount of time not
exceeding 24 hours. At the expiration of the configured time period, the
active file with its collection of call records is saved on the Sun server, and
a new active file for storing records is opened. The customer can retrieve
the stored file and, because of comma-delimited fields, import it into
another application, such as Excel, for post-processing and bill creation.
Note: When importing stored file into an Excel spreadsheet, leading zeros
and tenths of seconds may be truncated.
For a description of the master ASCII record and its fields, refer to ASCII
Billing Reports section of this manual.
PlexView ASCII Billing Server Issue 2, December 19, 2003
2.2 Features
The PlexView ABS offers these features:
• Ability to capture CDRs and convert them to ASCII format.
• Accurate and continuous capturing and storing of ASCII
records in the event of failover. The ABS supports the ability of
the Plexus 9000 to fail over to the standby system processor by
maintaining a standby connection and continuing to add records to
the appropriate data files. This ensures accurate and continuous
capturing and storing of ASCII billing records on an external Sun
platform even in the event of a Plexus 9000 system processor
failure.
• Maintains statistical information. The ABS maintains various
statistics for each connected client; specifically, total number of
received octets, number of received CDRs, number of out-of-order
sequence numbers, number of header errors, number of transmitted
octets, number of transmitted last-sequence records, number of
times reached wrap-around, number of times write failed, and
number of times read failed. These statistics are outputted to the
prefix.log file when the connection drops between the ABS and the
Plexus 9000.
• No loss of records in the event of a short-term communications

failure. The Plexus also has a 616 MB circular buffer that holds
up to 4.5 million records, or calls, ensuring that you lose no
records should there be a short-term communications failure.
2.3 How the Transfer Works

The Plexus 9000, in conjunction with the ABS, completes the following
steps to successfully transfer a CDR to the ABS:
• Plexus 9000 attempts to send a CDR for a completed call to the
ABS
• ABS verifies the authenticity of the Plexus 9000 IP address
from which the CDR is being sent
• ABS accepts the connection and creates a connection control
block
• ABS opens an ASCII CDR file
• ABS sends the Plexus 9000 the last received sequence number,
thus beginning the transfer of information
• ABS receives CDRs and converts them to an ASCII-format
master record
2-2 Telica, Inc.

Refer to Figure 2-1 for an illustrated example of the ABS conversion

process.
Signaling
Process
GDI (CDRs)
TCP/IP
Active
PlexView
Standby ASCII Billing
Call Module
Detail
Records
Sun Server
TM
Circular Allows ASCII files to be written

Buffer once a day, hourly, or every x
minutes (configurable).
Memory The customer is responsible for

managing file space and for any
postprocessing of ASCII records.
GDI
Switch
Interface
616MB
Disk
Master
Buffer Record P505-AA
12-12-02
ASCII
ASCII
File
Converter
Storage
Figure 2-1. PlexView ASCII Billing Conversion Details
2.3.1 ABS Verification of Plexus 9000 IP Address

The Plexus 9000 uses the TCP/IP connection between the ABS and the
Plexus 9000 switches to send CDRs to the ABS. In order to make this
connection, the Plexus 9000 IP address or name needs to be previously
configured into the ABS configuration file (abs.conf). Refer to Table 2-A
for a sample of the abs.conf file. The fields that may require changes are
shown in boldface type. Refer to the procedures section of this manual
and DLP-502 for instructions to edit this file. The procedures for
provisioning the Plexus 9000 for the ASCII Billing application are found
in the Plexus 9000 Installation and Operation Manual and NTP-018.
The ABS can then “listen” on the configured port (defaults to port 1983),
verifying a match between the Plexus 9000 IP address and the IP address
contained within the abs.conf file. When the IP addresses match, the
connection is made.
Telica, Inc. 2-3

Table 2-A. Sample abs.conf File

# FileName: abs.conf
# Telica ASCII Billing Server configuration environment
#
# Server TCP listen Port number and working directory
SERVER_PORT 1983
# Working Directory - contains data, connection info and log files

DATA_DIR data
# ASCII Billing file writing/creation frequency in minutes

# Must be integer interval of minutes within 24 hours. Intervals are
# always based on an initial start time of Midnight.
# Defaults to 24 Hours (60min * 24hr = 1440 min)
# Valid values = 5-1440
FREQUENCY 1440
# Uncomment the following line to have raw CDR records from the switch
# archived with the same frequency as AMA data files. The archive
# files use the same name, but the extension is .dat
# The value define the number of days an archive file is left on the
# system before it is automatically deleted.
# WARNING: This may require a VERY large disk!
# ARCHIVE 31
# Client switches (usually SPA/SPB pairs use the same prefix but it is
# not a requirement)
# Prefix may be followed by TZ and/or SensorID/OfficeID.
#
# TZ specifies the client's time zone.Clients which have the
# same prefix should be in the same time zone. Time zone is used to
# calculate the time in the file names.
# For detailed description of the rules for defining TZ,
# See environ(5) for a description of the TZ environment variable.
# TZ values used in US:
# EST5EDT (Eastern Time, Daylight Savings Time applies)
# CST6CDT (Central Time, Daylight Savings Time applies)
# PST8PDT (Pacific Time, Daylight Savings Time applies)
# MST7MDT (Mountain Time, Daylight Savings Time applies)
#
# If the configured TZ is invalid, then GMT, if no TZ is provided
# then server's time zone is used for time calculations.
#
# SensorID/OfficeID will override
# the AMA Sensor ID and/or Recording Office ID sent from the switch.
# Valid SensorID/OfficeID values = 000000-999999
# Plexus-9000 host processors (name or doted IP address)
# CLIENT name or IP File Prefix
# ------ ---------- -----------
CLIENT bostonSPA Boston TZ=EST5EDT
CLIENT bostonSPB Boston TZ=EST5EDT
CLIENT sfoSPA SanFrancisco

CLIENT sfoSPB SanFrancisco
2-4 Telica, Inc.

CLIENT denverSPA DenverA TZ=MST7MDT SensorID=123456

CLIENT denverSPB DenverB TZ=MST7MDT OfficeID=789012
CLIENT 10.0.0.26 Marlboro SensorID=345678:OfficeID=901234
CLIENT 10.0.0.27 Marlboro

Note: There can be up to sixteen (16) CLIENT entries for connection to up to eight (8)
Plexus 9000 switches. Delete extra CLIENT entries.
2.3.2 Fields of the abs.conf File
SERVER_PORT
The TCP server port is 1983 and does not need to be changed. This is the
port of the server that receives the CDRs.
DATA_DIR
The working directory for data, connection information and log files is
data and does not need to be changed. In the sample, it is set to “data”
which is the default.
FREQUENCY
The frequency that files are sent to the server may be changed. The
default is 1440 minutes, which is the maximum interval and is equal to
one day or 24-hours. The start time is midnight. The smallest interval is
five minutes.
ARCHIVE
The ARCHIVE field (new as of version 2-0-0-5) defines the number of
days raw (binary) CDR files are available on the server before they are
deleted. The maximum number of days is 62. The larger the number, the
more disk space is required.
To use the ARCHIVE field, it first must be uncommented by removing the

“#” at the beginning of the ARCHIVE line and then the value for the
number of days to keep file must be entered. If ARCHIVE is set to 0, then
files are not archived. The file name of the archived file is the same as the
ASCII Billing file, but has an extension of “.dat”.
The archived files can be formatted as ASCII Billing files by running

TelicaAbsSrvr in formatter mode. This allows regeneration of ASCII
billing files by using the archived files, in case of a corruption of the
Billing files. To run the TelicaAbsSrvr in formatter mode , it must be
started with “-F” flag. The abs.conf file is not used while running in
formatter mode so all the necessary parameters must be given from the
command line. The format of the command is as follows:
Telica, Inc. 2-5

TelicaAbsSrvr -F <prefix> <input_dir> <output_dir> [<start_datetime>]
The prefix, input_dir and output_dir parameters are all mandatory. Prefix
is the prefix as defined in the abs.conf file. The input_dir parameter is the
directory where the “.dat” files are stored. The output_dir parameter is the
directory where the output files are written.
The start_datetime parameter is optional and if it is not entered, the

formatter starts with the oldest .dat file in the input directory. This
parameter is the date/time as contained in the file name of the first file to
be formatted and is in the format of yyyymmdd_hhmm.
CLIENT
Client names or IP addresses of the switch must also be entered. The
client can be IP address or the name, obtained from DNS lookup. The IP
addresses are the addresses of the Plexus SPs that were assigned with the
ED-CHASSIS-EQPT TL1 command. Each SP must have a client entry.
File Prefix
The prefix field is set to a prefix name for the files of CDRs. Each pair of
SPs from a switch should share the same prefix.
Time Zone
This field is the time zone of the switch. The time stamp in the billing
record file name reflects the time zone of the switch. Configuring the time
zone, however, is optional; if it is not configured, the server’s local time
zone is used for that switch. Validation of the time zone is not done by the
Billing Server, but rather by the system time functions (localtime, ctime,
for example). If the configured time zone is invalid, then the results are
calculated in GMT. Switches using the same prefixes must be in the same
time zone.
When switching from Standard Time to Daylight savings (moving the

clock ahead), the 12:00 PM file is written out as 1:00 PM, so that it looks
like a gap in the files. When switching between Daylight Savings Time
and Standard Time, one minute is added to the time stamp of the file name
to create a unique file name during that one-hour period. Date and time
must be set up correctly on both the Sun server and the switch for this
feature to work correctly.
Time Zone values used in US are as follows:

EST5EDT (Eastern Time, Daylight Savings Time applies)
CST6CDT (Central Time, Daylight Savings Time applies)
PST8PDT (Pacific Time, Daylight Savings Time applies)
MST7MDT (Mountain Time, Daylight Savings Time applies)
2-6 Telica, Inc.

SensorID and OfficeID

The prefix or time zone may be followed by the SensorID and/or OfficeID
fields. These are optional fields that will override the AMA Sensor ID
and/or Recording Office ID sent from the switch. Valid values are
between 000000 and 999999 Plexus.
2.3.3 Plexus 9000 and ABS Connection

After the Plexus 9000 IP address is verified by the ABS, the ABS accepts
the connection and creates a connection control block. The connection
control block keeps the client’s information, such as IP address, name, and
connection statistics, for example.
2.3.4 ABS Receipt of CDR

The ABS opens the ASCII CDR file once the control block is established.
The file naming convention for the opened CDR file is
prefix_yyyymmdd_hhmm.txt where prefix is obtained from the ABS
configuration file (abs.conf), and yyyymmdd_hhmm represents the file
creation date and time.
The prefix enables you to associate a single data file with multiple clients,
such as SP-A or SP-B, where SP-B is a standby for SP-A. This means that
you can configure two platforms for redundancy. This then enables you to
put CDR data into the files with the same prefix in case of failover.
Prefix_Data Directory Files

All CDRs, when renamed according to the prefix_yyyymmdd_hhmm.txt
convention, are stored in a configured directory, DATA_DIR specified in
abs.conf file, on the ABS. Refer to Table 2-A for a sample of the abs.conf
file.
When the CDRs are received, a maintenance file, abs.conn, is also created
in the DATA_DIR directory specified in abs.conf file. The maintenance
file contains the Plexus 9000 connection information, such as last received
sequence number and SP-A/SP-B IP addresses.
The abs.log file contains log information, such as which client has
established a connection, what time the server started, and error
information. The file is limited to 700K. When the file reaches the limit,
it renames the file to abs.log_old and opens a new log file.
Telica, Inc. 2-7

2.3.5 Transfer of Information

When the ABS verifies the IP address and responds to the Plexus 9000, it
sends a single packet containing the last received sequence number. The
first time this process takes place, the number used in the packet is
designed to force the Plexus 9000 to begin the sequencing with the
number 0 (zero). Thereafter, the ABS checks the sequence numbers,
discarding the record and dropping the TCP connection if a non-sequential
number is detected. This causes the Plexus 9000 to experience a
resynchronization, thus re-establishing the connection. The ABS then
sends the last successfully received sequence number, and expects the
Plexus 9000 to retransmit based on the last received sequence number. If
the Plexus is unable to retransmit, the ABS accepts the record and logs an
error, indicating the number of lost records, in the abs.log file.
2.4 Configuration and Operation

To use the ABS successfully with the Plexus 9000, you must first meet
specific ABS server platform requirements and then configure the ABS on
the Sun server to communicate with the Plexus 9000, and configure the
Plexus 9000 to communicate with the ABS. The procedures for installing
and configuring the ABS application on an ASCII Billing Server are found
in the Procedures section of this guide. Procedures for provisioning the
Plexus 9000 for ASCII Billing are found in the Plexus 9000 Installation
and Operation Manual.
2-8 Telica, Inc.

3. PlexView AMA Lite
3.1 Introduction ..........................................................................................................3-1
3.1.1 PlexView AMA Lite Server Requirements..............................................3-2
3.1.2 Plexus 9000 Software Requirements........................................................3-2
3.2 Features ................................................................................................................3-2
3.3.1 AMA Lite Verification of Plexus 9000 IP Address .................................3-4
3.3.2 Fields of the ama.conf File.......................................................................3-5
3.3.3 Plexus 9000 and AMA Lite Connection ..................................................3-8
3.3.4 AMA Lite Receipt of CDR ......................................................................3-8
3.3.5 Transfer of Information............................................................................3-9
3.3.6 AMA Lite Reports....................................................................................3-9
To avoid local time synchronization problems, Telica strongly recommends

setting the Plexus system clock to use GMT.
3.1 Introduction
The PlexView Automatic Message Accounting (AMA) Lite application,
which runs on a Sun computer platform, works with the Plexus 9000
switch to convert Call Detail Records (CDRs) from Billing Automatic
Message Accounting (AMA) Format (BAF) records to an AMA record
format.
The Plexus 9000 sends a CDR for each attempted call over TCP/IP to the
AMA Lite server. AMA Lite then extracts the information from the CDR
and writes it to a master AMA record format, storing the record on the Sun
server. Each record is appended to an active file over a previously
configured amount of time not exceeding 24 hours. At the expiration of
the configured time period, the active file with its collection of call records
is saved on the Sun server, and a new active file for storing records is
opened.
For a description of the master AMA record and its fields, refer to the
AMA Lite Reports section of this manual
PlexView AMA Lite Issue 2, October 10, 2003
3.1.1 PlexView AMA Lite Server Requirements

AMA Lite is designed to run on a Sun Solaris platform. The minimum
recommended hardware configuration for PlexView is a Sun Solaris
platform with a 400 MHz CPU, 512 Mbytes of memory, 20 Gbytes of
hard disk space (SCSI disk drives are recommended) and a 100 MB
Ethernet connection. Since AMA Lite is capturing critical billing data, to
avoid the loss of data due to a disk crash, Telica recommends having
multiple disk drives and configuring disk mirroring software, such as Sun
Solstice and Veritas.
3.1.2 Plexus 9000 Software Requirements

Contact Telica Technical Services at 1-888-440-8354 regarding the
specifics of managing Plexus switches running versions of Plexus 9000
software. Information provided in this document may not apply to some
versions of AMA Lite.
3.2 Features
The AMA Lite application offers these features:
• Ability to capture CDRs and convert them to AMA Lite
format.
• Accurate and continuous capturing and storing of AMA Lite
records in the event of failover. AMA Lite supports the ability of
the Plexus 9000 to fail over to the standby system processor by
maintaining a standby connection and continuing to add records to
the appropriate data files. This ensures accurate and continuous
capturing and storing of AMA Lite billing records on an external
Sun platform even in the event of a Plexus 9000 system processor
failure.
• Maintenance of statistical information. AMA Lite maintains
various statistics for each connected client; specifically, total
number of received octets, number of received CDRs, number of
out-of-order sequence numbers, number of header errors, number
of transmitted octets, number of transmitted last-sequence records,
number of times reached wrap-around, number of times write
failed, and number of times read failed. These statistics are
outputted to the prefix.log file when the connection drops between
the AMA Lite and the Plexus 9000.
• No loss of records in the event of a communications failure. If
there is a loss of communication between the Plexus 9000 and the
AMA Lite server, the Plexus processor will switch to the standby
processor. The Plexus also has a 500 MB circular buffer that holds
up to 2.5 million records, or calls, ensuring that you lose no
records should there be a communications failure.
3-2 Telica, Inc.


The Plexus 9000, in conjunction with the AMA Lite, completes the
following steps to successfully transfer a CDR to the AMA Lite server:
• Plexus 9000 attempts to send a CDR for a completed call to the
AMA Lite server
• AMA Lite verifies the authenticity of the Plexus 9000 IP address
from which the CDR is being sent
• AMA Lite accepts the connection and creates a connection control
block
• AMA Lite opens an AMA CDR file
• AMA Lite sends the Plexus 9000 the last received sequence
number, thus beginning the transfer of information
• AMA Lite receives CDRs and converts them to an AMA-format
master record
Refer to Figure 3-1 for an illustrated example of the AMA Lite conversion
process.
Signaling
Process
GDI (CDRs)
TCP/IP
Active
PlexView
Standby AMA Lite
Call Application
Detail
Records
Sun Server
TM
Circular Allows AMA Lite files to be

Buffer written once a day,
hourly, or every x minutes
(configurable).
Memory
The customer is responsible for
managing file space and for any
GDI postprocessing of records.
Switch
Interface
500MB
Disk
Master
Buffer Record
AMA Lite File

Formatter Storage
P924-AA
09-24-02
Figure 3-1. PlexView AMA Billing Conversion Details
Telica, Inc. 3-3

3.3.1 AMA Lite Verification of Plexus 9000 IP Address

The Plexus 9000 uses the TCP/IP connection between the AMA Lite and
the Plexus 9000 switches to send CDRs to the AMA Lite server. In order
to make this connection, the Plexus 9000 IP address or name needs to be
previously configured into the AMA Lite configuration file (ama.conf).
Refer to Table 3-A for a sample of the ama.conf file. Refer to the
Procedures section of this guide to configure the AMA server. Procedures
for provisioning the Plexus 9000 for billing and AMA Lite are found in
the Plexus 9000 Installation and Operation Manual.
The AMA Lite application can then “listen” on the configured port (or
defaults to port 1983), verifying a match between the Plexus 9000 IP
address and the IP address contained within the ama.conf file. When the
IP addresses match, the connection is made.
Table 3-A. Sample ama.conf File

# FileName: ama.conf
# Telica AMA Billing Server configuration environment
#
SERVER_PORT 1983

DATA_DIR ama_data
# AMA Billing file writing/creation frequency in minutes

FREQUENCY 1440
# Uncomment the following line to have AMA data file that have
# accumulated zero records deleted when we rotate filenames to
# the next collection interval every FREQUENCY minutes.
PURGENULLDATA True
# Uncomment the following line to have raw CDR records from the switch
# archived with the same frequency as AMA data files. The archive
# files use the same name, but the extension is .dat
# ARCHIVE 31
# Client switches (usually SPA/SPB pairs use the same prefix but it is
# not a requirement)
#
# same prefix should be in the same time zone.Time zone is used to
3-4 Telica, Inc.

# calculate the time in the header records and in the file names.
#

#
# Plexus-9000 host processors (name or dotted IP address)

# ------ ---------- -----------



3.3.2 Fields of the ama.conf File
SERVER_PORT
The TCP server port is 1983 and does not need to be changed. This is the
port of the server that receives the CDRs.
DATA_DIR
The working directory for data, connection information and log files must
be established. In the sample, it is set to “data” which is the default.
FREQUENCY
The frequency that files are sent to the server must also be established.
The default is 1440 minutes, which is the maximum interval and is equal
to one day or 24-hours. The start time is midnight. The smallest interval is
five minutes.
Telica, Inc. 3-5

PURGENULLDATA True
The PURGENULLDATA True field allows files with zero (0) records to
be deleted when the line is uncommented by removing the “#” at the
beginning of the line. Files that are saved then have at least one record.
ARCHIVE
The ARCHIVE field defines the number of days an archived file is
available on the server before it is deleted. The maximum number of days
is 62 and the default is 0. The larger the number, the more disk space is
required.
To use the ARCHIVE field, it first must be uncommented by removing the

“#” at the beginning of the line and then the value for the number of days
to keep file must be entered. If ARCHIVE is set to 0, then files are not
archived. If ARCHIVE is set a value other than 0, then CDR records from
the switch are archived at the same frequency as the AMA Billing files
and for the number of days specified. The file name of the archived file is
the same as the AMA Billing file, but has an extension of “.dat”.
The archived files can be formatted as AMA Billing files by running

TelicaAMASrvr in formatter mode. This allows regeneration of AMA
billing files by using the archived files, in case of a corruption of the
Billing files. To run the TelicaAMASrvr in formatter mode , it must be
started with “-F” flag. The ama.conf file is not used while running in
formatter mode so all the necessary parameters must be given from the
command line. The format of the command is as follows:
TelicaAMASrvr -F <prefix> <input_dir> <output_dir>
[<start_datetime>]
The prefix, input_dir and output_dir parameters are all mandatory. Prefix
is the prefix or name of the “.dat” files. The input_dir parameter is the
directory where the “.dat” files are stored. The output_dir parameter is the
directory where the output files are written.
The start_datetime parameter is optional and if it is entered, the formatter

starts with the oldest .dat file. This parameter is the date and time of the
first file to be formatted and is in the format of yyyymmdd_hhmm.
To read the AMA files you must have an application for viewing AMA
files. If you do not have an application, please call Telica Technical
Services at 888-440-8354 or 508-485-5739 for assistance.
3-6 Telica, Inc.

CLIENT
Client names or IP addresses of the switch must also be entered. The
client can be IP address or the name, obtained from DNS lookup. The IP
address is the addresses of the Plexus SPs that were assigned with the
ED-CHASSIS-EQPT TL1 command.
File Prefix
The prefix field is set to a prefix name for the files of CDRs.
Time Zone
The time stamp in the billing record file names and header records reflects
the time zone of the switch. Configuring the time zone, however, is
optional; if it is not configured, the server’s local time zone is used for that
switch. Validation of the time zone is not done by the Billing Server, but
rather by the system time functions (localtime, ctime, for example). If the
configured time zone is invalid, then the results are calculated in GMT.
Switches using the same prefixes must be in the same time zone.
When switching from Standard Time to Daylight savings (moving the

clock ahead), the 12:00 PM file is written out as 1:00 PM, so that it looks
like a gap in the files. When switching between Daylight Savings Time
and Standard Time, one minute is added to the time stamp of the file name
to create a unique file name during that one-hour period. Date and time
must be set up correctly on both the Sun server and the switch for this
feature to work correctly. Below are some of the Time Zone values used in
US:
EST5EDT (Eastern Time, Daylight Savings Time applies)
CST6CDT (Central Time, Daylight Savings Time applies)
PST8PDT (Pacific Time, Daylight Savings Time applies)
MST7MDT (Mountain Time, Daylight Savings Time applies)
SensorID and OfficeID

The prefix may be followed by an the SensorID and OfficeID fields which
are optional fields that will override the AMA Sensor ID and/or Recording
Office ID sent from the switch. Valid values are between 000000 and
999999 Plexus.
Telica, Inc. 3-7

3.3.3 Plexus 9000 and AMA Lite Connection

After the AMA Lite server verifies the Plexus’ 9000 IP address, the AMA
Lite server accepts the connection and creates a connection control block.
The connection control block keeps the client’s information, such as IP
address, name, and connection statistics, for example.
3.3.4 AMA Lite Receipt of CDR

The AMA Lite application opens the AMA CDR file once the control
block is established. The file naming convention for the opened CDR file
is prefix_yyyymmdd_hhmm.ama where prefix is obtained from the AMA
Lite configuration file (ama.conf), and yyyymmdd_hhmm represents the
file creation date and time
The prefix enables you to associate a single data file with multiple clients,
such as SP-A or SP-B, where SP-B is a standby for SP-A. This means that
you can configure two platforms for redundancy. This then enables you to
put CDR data into the same file in case of failover.
All CDRs, when renamed according to the prefix_yyyymmdd_hhmm.ama

convention, are stored in a pre-configured directory, prefix_data, on the
AMA Lite server. These can be converted to a readable format with the
dump_dms_ama tool which is shipped the the AMA Lite software.
When the CDRs are received, a maintenance file, prefix_conn.info, is also

created in the prefix_data directory. The maintenance file contains the
Plexus 9000 connection information, such as last received sequence
number and SP-A/SP-B IP addresses.
The prefix.log file contains log information, such as which client has
established a connection, what time the server started, and error
information. The file is limited to 700K. When the file reaches the limit,
it renames the file to prefix.old and opens a new log file.
Refer to Table 3-A for a sample of the ama.conf file.
3-8 Telica, Inc.

3.3.5 Transfer of Information

When the AMA Lite verifies the IP address and responds to the Plexus
9000, it sends a single packet containing the last received sequence
number. The first time this process takes place, the number used in the
packet is designed to force the Plexus 9000 to begin the sequencing with
the number 0 (zero). Thereafter, the AMA Lite checks the sequence
numbers, discarding the record and dropping the TCP connection if a non-
sequential number is detected. This causes the Plexus 9000 to experience
a resynchronization, thus re-establishing the connection. The AMA Lite
then sends the last successfully received sequence number, and expects the
Plexus 9000 to retransmit based on the last received sequence number. If
the Plexus is unable to retransmit, the AMA Lite accepts the record and
generates an alarm indicating the number of lost records. The alarm is
sent to the prefix.log file.
3.3.6 AMA Lite Reports

For details regarding AMA Lite reporting, refer to the AMA Lite Reports
section of this manual.
Telica, Inc. 3-9

NOTES:
3-10 Telica, Inc.

4. PlexView Traffic Collection Application (TCA)
4.1 Introduction ..........................................................................................................4-1

4.2 Features ................................................................................................................4-2
4.3 How Statistical Information is Generated ............................................................4-3
4.3.1 Telica Statistical Data Server (TSDS) Application..................................4-4
4.3.2 Telica Statistical Analysis Application (TSAA) ......................................4-6
4.3.2.1 The tsaa.conf File.........................................................................4-7
4.3.2.2 The tsaa_<pid>.log File ............................................................4-13
4.3.2.3 Erlang B......................................................................................4-13
4.3.3 Reporting................................................................................................ 4-14
4.4 Installation and Configuration............................................................................4-14
4.4.1 TCA Server Platform Requirements ......................................................4-14
4.4.2 Configuration Procedure ........................................................................4-14
4.1 Introduction
The PlexView Traffic Collection Application (TCA) works in
conjunction with the Plexus 9000 to capture information about every call,
and to process that information into statistical data. The statistical data is
tracked for busy hour information, peg counts, trunk group hold time, and
traffic Centum Call Seconds (CCS).
Up to eight Plexus 9000 switches can use the TCP/IP protocol to send a
Call Detail Record (CDR) for each attempted call to the TCA via the
Telica Statistical Data Server (TSDS). The TSDS stores this information
in binary format on the TCA server.
Note: For more information regarding the TSDS, refer to 4.3.1 in this
document.
The Telica Statistical Analysis Application (TSAA) then extracts the

necessary information from the CDR and updates the call statistics and
traffic measurements accordingly, writing it to output text files, and
storing it on the TCA (Sun®) server.
Note: For more information regarding the TSAA, refer to 4.3.2 in this
document.
PlexView Traffic Collection Application (TCA) Issue 3, December 12, 2003
Because of comma-delimited fields, you can retrieve the stored files and
import them into another application, such as Excel, for post-processing
and report creation.
The PlexView TCA runs on a Sun computer platform and is available as a

stand-alone application or with the PlexView Element Management
System (EMS).
Note: The server on which you plan to run the TCA can also be the same
server on which you run the PlexView EMS and/or the PlexView ASCII
Billing Server (ABS), although this is not the recommended
architecture. In any case, the server on which you choose to run the TCA
is referred to as the TCA server.
4.2 Features
The PlexView TCA offers these features:
• Ability to extract call statistics and traffic measurements from

CDRs and convert them to ASCII format.
• Accurate and continuous capturing and storing of statistical
information in the event of SP failover. The TCA supports the
ability of the Plexus 9000 to fail over to the standby system
processor by maintaining a standby connection and continuing to
add records to the appropriate data files. This ensures accurate and
continuous capturing and storing of traffic statistics on an external
Sun platform.
• Captures statistics into various types. The TCA captures the
statistics into five file types: busy hour data, peg counts, traffic
Centum Call Seconds (CCS), trunk group hold time reports, and
Call Detail Records (CDRs). The busy hour statistics file captures
the busiest hour information on a daily basis. The peg counts
statistics file contains summarized statistical call data in 5-minute,
1-hour, and 24-hour records. The traffic report captures CCS data
and call peg counts per trunk group (SS7, BICC, CAS) and per
isdn interface on a configurable time (15 minute, 30 minute, or 1
hour) basis. The trunk group hold time report displays the average
hold time for each trunk group on a 5-minute basis. The CDR files
are produced every 5 minutes and contain a record for each call or
call attempt.
4-2 Telica, Inc.

• No loss of records in the event of a short duration

communications failure. Not only does the TCA continue
working in standby mode, but it also has a circular buffer that
holds up to 3.0 million records, ensuring that you lose no records
(over a period of time and depending on call volume) should there
be a communications failure.
• TCA automatic restart. TCA will automatically restart when the
Sun server is rebooted if the S99PLXStats file is installed in the
/etc/rc3.d directory.
• Multiple tsaa.conf files can be started. This requires copying the
tsaa.conf file with multiple names and modifying a line in the
S99PLXStats file.
• Dates in file names have been changed from MMDDYY to
YYYYMMDD to allow easier sorting.
4.3 How Statistical Information is Generated

The Plexus 9000, in conjunction with the TCA, completes the following
steps to retrieve statistical information from a call record:
1. On the Plexus 9000, call control generates a call record under one
of these conditions:
- Call ends after being successfully established
- Call cannot be established (not answered, busy, no route)
- Call has been established for more than 15 minutes (long call
duration)
2. The Statistics client filters unnecessary information from the call
record, producing a record containing only pertinent information.
3. On the Sun server side, the Sun workstation is configured to
request the call record to be sent to the statistics client module,
using the TCP/IP protocol.
4. The TelicaStatsSrvr application on the client module retrieves and
stores the call records in local binary files, accessible on the
network.
5. The tsaa application reads the binary files and performs all the
statistical calculations, depending on the needs of the customer.
6. The result of the analysis application is stored in user-readable text
files (ASCII), ready for further analysis.
Telica, Inc. 4-3

See Figure 4-1 for an illustrated example of the statistics retrieval process.
Signaling
Process
CDRs ASCII Files

TCP/IP FTP
Active
PlexView Traffic
Standby Traffic Mgmt Data Collector Capacity
Module and Eng
Call
Records App
TM Sun Server
Circular
Buffer Track Daily
Busy Hour Files FTP
X# of Statistics
Records Memory
(Configurable)
Track
Switch Call
Interface Daily
Statistics Files
Virtual (Receives (Peg Count)
N groups of CDRs) P506-AA
X# of above Memory 12-10-01
records (Disk)
(Configurable)
Track
Traffic (CCS) Hourly
Statistics Files
Track Trunk
Group Hold- Daily
Time Output Files
Figure 4-1. PlexView TCA Statistics Retrieval Process
4.3.1 Telica Statistical Data Server (TSDS) Application

The TSDS can handle connections to multiple Plexus 9000 switches, using
a TCP/IP socket base connection between the Plexus and the TCA server.
Generated CDRs flow from each Plexus 9000 to the TCA server.
When the TSDS runs its TelicaStatsSrvr process, it creates the tsds_data
directory (DATA_DIR directory set in tsds.conf file). This directory
contains the following generated files:
• tsds.log – This file contains log information, such as time the
server started, which client has established a connection, and error
information. This file is limited by size (700K). When the size
reaches the limit, it copies the file into tsds.log_OLD and begins a
new tsds.log file.
• tsds.conn – This binary file contains connection information about
the clients, such as last received sequence number and IP address.
In case the server goes down for maintenance or the process exited
because of a major error condition, upon reconnection with the
client, the server will know which CDR record to request next.
4-4 Telica, Inc.

• prefix_STATS_yyyymmdd.dat – This is the binary file created by

TSDS. Prefix is the client prefix configured in tsds.conf file. This
file is created when a valid client establishes a connection. The file
is closed at midnight around 12:15 a.m. and a new file is created to
reflect the next-day time stamp. The information in the file can be
displayed on a Sun terminal by typing the following:
od –X XXX_yyyymmddhhmm.dat | more
Table 4-A displays a sample of the tsds.conf file. The file is read upon
TCA server startup, containing keywords followed by parameter values.
The changes you will make to this file are shown in boldface type. You
must save the configuration before exiting.
Table 4-A. Sample tsds.conf File

# FileName: tsds.conf
# Telica Stats Server configuration environment
#
SERVER_PORT 10000

# DATA_DIR tsds_data
# Client switches (usually SPA/SPB pairs use the same prefix)

# Key IP-or Host Prefix

# ===== ========== ========
CLIENT <SP-A IP or Hostname> <boston>
CLIENT <SP-B IP or Hostname> <boston>
CLIENT See Note below.
Plexus 9000 switches.
Telica, Inc. 4-5

Fields:
SERVER_PORT
The Server_Port is the TCP connection port number. There is no need to
change.
DATA_DIR
The Data_Dir is the directory that keeps the statistics data, log, and
connection files. This directory need not exist beforehand. It will be
created when TelicaStatsSrvr is started. There is no need to change from
the default.
CLIENT
The Client field consists of the IP address or host name and a prefix.
IP or Host
The IP or Host field specifies the IP addresses or host names of the SP and
are provided by the customer.
Prefix
The Prefix field must be the same for both SP-A and SP-B. The chosen
Prefix name will be used to identify and correlate the statistics data files
that are generated by your switch. It is recommended that the prefix name
is also used to provide a unique name for the tsaa.conf files so that each
switch has its own file. The Prefix name (boston) shown in the sample
tsds.conf file is only an example.
4.3.2 Telica Statistical Analysis Application (TSAA)

The TSAA is a stand-alone application that runs on a Sun workstation. It
interfaces with the TSDS, which generates CDRs in binary files. The
TSAA parses this data and generates peg count records and calculates
busy hour information in text formats.
The TSAA executable and configuration files reside in the same directory
as the TSDS. It is automatically started when the S99PLXStats script is
run.
Once the TSAA is operational, the application generates peg counts, CCS,
holdtime and busy hour information as determined by the
tsaa_<prefix>.conf file. The application creates directories specified in
the tsaa_<prefix>.conf file, for its output and log files. The log file is:
tsaa_<pid>.log
with “pid” meaning process ID.
4-6 Telica, Inc.

4.3.2.1 The tsaa.conf File

The tsaa.conf file is included in a .tar file on the installation CD and stores
all configuration information. The file is read upon TCA server startup,
containing keywords followed by parameter values. If traffic statistics are
being gathered from multiple switches, there must also be multiple
tsaa.conf files. The installation procedure recommends that you copy and
name the files in the format of tsaa_<prefix>.conf. The prefix was
established when editing the tsds.conf file.
The fields that require changes are shown in boldface type. Other fields
may also be changed. If you enter a configuration point value beyond a
valid range, default values are used. You must save the configuration
before exiting. A sample of the tsaa_<prefix>.conf file is shown in
Table 4-B.
Fields:
Prefix
This field indicates the prefix that is unique for a switch and was
established in the PlexusDC.ini or tsds.conf file.
Input Directory
This field specifies the directory containing the binary files generated from
the TelicaStatsServer. It must be identical to the value specified in the
Statistics entity configuration section of the PlexusDC.ini file or the
DATA_DIR parameter of the tsds.conf file. The default name is
tsds_data.
Output Directory
This field specifies the name of the output directory for statistics data files.
This name should be changed to tsaa_<prefix>.
Log Directory
This field specifies the name of the output directory for all log files. The
name should be changed to tsaa_<prefix>/log. It must be identical to the
value specified in the Statistics entity configuration section of the
PlexusDC.ini file
Percent Blocking
This field indicates the value used in the calculation of Erlang B,
specifying the acceptable number of failure of calls due to an insufficient
number of lines available. The minimum is 0; the maximum is 1; and the
default is 0.01. Refer to section 4.3.2.3 for a description of Erlang B.
Telica, Inc. 4-7

Table 4-B. Sample tsaa_<prefix>.conf File

# FileName: *tsaa.conf
#
# This file contains the configuration information for the
# Telica Statistical Analysis Application (TSAA), and should be
# modified by authorized personnel only.
#
Prefix: boston
Input Directory: tsds_data
Output Directory: tsaa_boston
Log Directory: tsaa_boston/log
Percent Blocking: 0.01
Peg Count Report: 1
ASR Report: 1
Hold Time Report: 1
SS7 Trkgrp CCS Report: 3
Intfcgrp CCS Report: 3
CAS Trkgrp CCS Report: 3
BICC Trkgrp CCS Report: 3
SIP Trkgrp CCS Report: 3
GR303 Intfcgrp CCS Report: 3
CAS Intfcgrp CCS Report: 3
ASCII CDR Report: 1
Detailed Peg Report: 1
Calculate DN Peg Count: 1
Busy Hour Granularity: 30
CCS Granularity Period: 4
Peg Count Granularity Period: 4
ASR Granularity Period: 4
Hold Time Granularity Period: 4
Input Storage Duration: 30
Output Storage Duration: 30
FTP to EMS: 0
FTP Transfer Interval: 60
EMS IP Address: 127.0.0.1
EMS Username: anonymous
EMS Password: boston
EMS Output Directory: /tsaa_data
Peg Count Report

This field specifies whether or not to report Peg Counts.
0 = Do not report Peg Counts.
1 = Report Peg Counts. This is the default value.
4-8 Telica, Inc.

ASR Report
This field specifies whether or not to report the Answer to Seizure Ratio
(ASR).
0 = Do not report ASR.
1 = Report ASR. This is the default value.
Hold Time Report

This field specifies whether or not to report trunk group average hold time.
0 = Do not report average hold time.
1 = Report the average hold time. This is the default value.
SS7 Trkgrp CCS Report

This field specifies the format for the SS7 trunk group CCS reporting.
0 = Reporting is disabled.
1 = Report only, space-delimited format.
2 = Report only, comma-delimited format.
3 = Report both space-delimited and comma-delimited formats.
This is the default value.
Intfcgrp CCS Report

This field specifies the format for the interface group CCS reporting.
CAS Trkgrp CCS Report

This field specifies the format for the CAS trunk group reporting.
BICC Trkgrp CCS Report

This field specifies the format for the BICC trunk group reporting.
Telica, Inc. 4-9

SIP Trkgrp CCS Report

This field specifies the format for the SIP trunk group reporting.
GR303 Intfcgrp CCS Report

This field specifies the format for the GR303 interface group CCS
reporting.
CAS Intfcgrp CCS Report

This field specifies the format for the CAS interface group CCS reporting.
This is the default value
ASCII CDR Report

This field enables or disables ASCII CDR reporting every five minutes.
1 = Only Call Release CDRs are printed. This is the default value
2 = Both Long Duration and Release CDRs are printed.
Detailed Peg Report

This field enables or disables detailed peg reporting.
0 = Detailed reporting is disabled. Pegged for the state of the call.
1 = Detailed reporting is enabled. Pegged for the release cause
codes. This is the default value
Calculate DN Peg Count

This field enables or disables the calculation of Directory Number (DN)
peg counts.
0 = Do not calculate DN Peg Counts.
1 = Calculate DN Peg Counts. This is the default value.
4-10 Telica, Inc.

Busy Hour Granularity

This field specifies the granularity of the busy hour calculation. Units are
in minutes. Valid range is 0, 5, 30 and 60 and the default is 30.
0 = Disable.
5 = 5 minutes.
30 = 30 minutes - This is the default value.
60 = 60 minutes or 1 hour.
CCS Granularity Period

This field specifies the granularity of how often the files are written to
disk. The values are 2, 3 and 4.
2 = Created every 15 minutes
4 = Created every hour. This is the default value
Peg Count Granularity Period

disk. The values are 2, 3, 4 and 5.
4 = Created every hour. This is the default value.
5 = Created once a day
ASR Granularity Period

This field specifies the granularity of how often Answer to Seizure Ratio
(ASR) files are written to disk. The values are 2, 3, 4 and 5.
2 = Created every 15 minutes.
5 = Created once a day.
Hold Time Granularity Period

disk. Values are 2, 4 and 5.
Telica, Inc. 4-11

Input Storage Duration

This field specifies the number of days to store input files. Values are 0 to
180.
0 = File should be removed next day. (Not recommended).
30 days is the default value.
If tsaa is configured to ftp files, even if the files are older than “Input
Storage Duration” they are not removed, if they have not been ftped yet.
Output Storage Duration

This field specifies number of days to store files. Values are 0 to 180.
If tsaa is configured to ftp files, even if the files are older than “Output
Note: The following fields refer to files that are FTPed to the EMS server
FTP to EMS
This field specifies whether or not to FTP to Element Management System
(EMS).
0 = Do not FTP to EMS.
1 = FTP to EMS
FTP Transfer Interval

This field specifies the interval between FTPs to EMS. Values are 30 to
900 seconds. The default value is every 60 seconds.
EMS IP Address:
This field specifies the IP address of the EMS server.
EMS Username:
This field specifies the username for EMS.
EMS Password:
This field specifies the password for EMS.
EMS Output Directory:

This field specifies the output directory on the EMS server (full path).
This directory needs to already exist and the EMS user must have read and
write permission to the directory.
4-12 Telica, Inc.

4.3.2.2 The tsaa_<pid>.log File

This file stores the TCA current activity by the process ID (PID).
Common activities are peg counts, busy hour calculations, CCS reporting,
hold time calculating and rolling of logs, but error codes and other
debugging information are also reported in the file.
4.3.2.3 Erlang B
Erlang and Erlang B calculations are used in the creation of busy hour call
reports (refer to Traffic Statistics Reports section of this manual). The
report specifies the number of Erlangs and circuits and the circuit usage
percentage.
An Erlang is a unit of telecommunications traffic measurement. Strictly

speaking, an Erlang represents the continuous use of one voice path. In
practice, it is used to describe the total traffic volume of one hour. For
example, if a group of users made 30 calls in one hour, and each call had
an average call duration of 5 minutes, then the number of Erlangs this
represents is worked out as follows:
Minutes of traffic in the hour = number of calls x duration
Minutes of traffic in the hour = 30 x 5
Minutes of traffic in the hour = 150
Hours of traffic in the hour = 150 / 60
Hours of traffic in the hour = 2.5
Traffic figure = 2.5 Erlangs
The Erlang B traffic model is used by telephone system designers to

estimate the number of lines required for PSTN connections or private
wire connections. The three variables involved are Busy Hour Traffic
(BHT), Blocking and Lines:
Busy Hour Traffic (in Erlangs) is the number of hours of call traffic
there are during the busiest hour of operation of a telephone
system.
Blocking is the failure of calls due to an insufficient number of
lines being available. For example, 0.03 mean 3 calls blocked per
100 calls attempted.
Lines is the number of lines in a circuit.
Telica, Inc. 4-13

The Erlang B algorithm is as follows:
where a is the busy hour traffic in Erlangs, c is the number of lines, and
B(c,a) is the blockage. The application uses this equation to determine c.
The model assumes that all blocked calls are immediately cleared.
4.3.3 Reporting
The TCA generates several reports. Refer to Traffic Statistics Reports
section of this manual for reporting details.
4.4 Installation and Configuration

To use the TCA successfully with the Plexus 9000, you must first meet
specific TCA platform requirements, listed in 4.4.1. You must then install
and configure the TCA on the Sun server and establish communications
between the TCA and the Plexus 9000.
4.4.1 TCA Server Platform Requirements

The TCA supports the Plexus 9000, release 3.1.1.1 or greater, and must
meet these prerequisites:
• Sun Solaris™ 2.7 or 2.8 with 500 MB memory and a 10/100
Ethernet card
• Sun server with a minimum of a 400 Mhz processor
4.4.2 Configuration Procedure

Configuration procedure for gathering statistics can be found in DLP-521
or DLP-522 of this manual. Procedures for provisioning the Plexus 9000
for gathering statistics can be found in the Plexus 9000 Installation and
Operation Manual.
4-14 Telica, Inc.

5. PlexView Billing and Traffic System
5.1 Introduction ..........................................................................................................5-2

5.2 Features ................................................................................................................5-3
5.4 Provisioning for the Billing and Traffic System ..................................................5-6
5.4.1 The plexusDc.ini File ...............................................................................5-6
5.1.1.1 Data Collector Main Entity Configuration.................................5-11
5.1.1.2 Receiver Entity Configuration ...................................................5-13
5.1.1.3 Billing Entity Configuration ......................................................5-14
5.1.1.4 Billing Output Options ...............................................................5-21
5.1.1.5 ASCII and AMA Lite (BAF) File Parameters ...........................5-22
5.1.1.6 PlexView Pro Billing (Billdats) Parameters...............................5-23
5.1.1.7 ASCII and BAF Push Entity Configuration...............................5-24
5.1.1.8 Statistics Entity Configuration ...................................................5-25
5.4.2 The tsaa.conf File...................................................................................5-26
5.4.3 The tsaa_<pid>.log File ........................................................................5-32
5.4.4 Erlang B..................................................................................................5-33

Note: The plexusDc.ini and tsaa.conf files may differ from your files
depending upon the version of software. This document lists the files as they
were at the date of this document.
PlexView Billing and Traffic System Issue 4, January 9, 2004
5.1 Introduction
The PlexView Billing and Traffic System (BTS), which runs on a Sun
computer platform, works with the Plexus 9000 switch to receive raw data
Call Detail Records (CDRs). The Plexus must be running software 3.8 or
greater.
As each call is placed through a Plexus switch, the Plexus takes a snapshot
of the call state and saves it in a CDR. Because the CDR contains raw call
data stored in a proprietary format, it is not very useful as is and further
processing is required to convert the CDR into a format that can be used
by off-switch billing and statistics systems.
The Plexus 9000 saves one raw data CDR for each attempted call and
sends it over TCP/IP to the BTS. The BTS has the responsibility of
processing CDRs and interfacing with billing and traffic collection
systems allowing the Plexus to be able to use more of its resources for
processing calls.
In earlier software versions of the Plexus, two raw CDRs were generated
for every call. Then Billing CDRs were formatted into AMA like objects
and written to a circular file on the switch and Traffic Collection CDRs
were formatted into their format and written to another circular file. Two
instances of a GDI transmitter were running to read the circular files and
transmit the data over a TCP/IP connection to the appropriate server where
a GDI receiver collected the data and formatted into the correct output.
Processing and interfacing with the billing and traffic collection systems
occurred in the Plexus using valuable resources.
The BTS receives CDR records from the Plexus via the Data Collector or
GDI Receiver. The Data Collector establishes connections to one or more
Plexus switches and receives a stream of CDRs from each one. The CDRs
are parsed to determine if they should be forwarded to ASCII billing,
AMA Lite, PlexView Pro billing or Traffic collection.
5-2 Telica, Inc.

5.2 Features
The PlexView Billing and Traffic System offers these features.
• One CDR is generated in the Plexus for both billing and traffic
collection.
• CDR formatting occurs in the BTS allowing the Plexus more
resources for processing calls.
• The Data Collector or GDI receiver of the BTS collects the
data from the Plexus and multiplexes the same CDR into a
traffic collection handler and a billing handler.
• Any combination of billing reporting (ASCII Billing, AMA
Lite or PlexView Pro Billing) can be used.
• Accurate and continuous capturing and storing of records in the
event of failover. The BTS supports the ability of the Plexus
9000 to fail over to the standby system processor by
maintaining a standby connection and continuing to add
records. This ensures accurate and continuous capturing and
storing of records in the event of a Plexus system processor
failure.
• No loss of records in the event of a short-term communication
failure. The Plexus has a circular buffer of approximately
2 gigabytes ensuring no records are lost if there is a short-term
communication failure.
• Traffic application will automatically restart when the Sun
server is rebooted if the S99PLexDC file is installed in the
/etc/rc3.d directory.
• Can collect CDRs from multiple Plexus switches.
• Provides the infrastructure for other data interfaces (i.e., fraud
system, NTM or NTP).
Telica, Inc. 5-3


Billing and traffic collection CDRs are combined and sent as one CDR to
the Billing and Traffic System via the GDI protocol over a TCP/IP
connection. The information needed to complete the formatting (e.g.
subscriber specifics) for billing or traffic collection is part of the CDR sent
to the Data Collector. The GDI receiver/Data Collector in the BTS will
forward the CDR to the interested entities (i.e., ASCII billing, AMA Lite,
Pro Billing or Traffic Collection) based on the configuration information.
Refer to Figure 5-1 for an illustration of the Plexus and the Billing and
Traffic System.
Sun Hardware Platform with Solaris OS
ASCII ASCII
Billing Files
Billing GDI AMA

AMA AMA
Formatter Pro Billing
Trans
AMA AMA
Lite Lite
CDRs Files
TCP/IP
Data Traffic
Active Traffic
Collector/ Statistics Collection
GDI Receiver App
Standby
NetMinder NetMinder
NTM NTM
TM (Future) OSS
Raw NetMinder NetMinder

CDRs NTP NTP
P983-AA
(Future) OSS
05-01-03
Figure 5-1. The Plexus and the Billing and Traffic System
If the connection exists between the Plexus and the BTS, the switch will
send the data at 5-second intervals or sooner it the buffer fills.
Data can be output in several forms depending on the Data Collector

configuration. ASCII Billing will take the CDRs from the GDI
Receiver/Mux/Data Collector and generate ASCII output files using the
current ASCII Billing format; AMA Lite will convert Call Detail Records
(CDRs) to an AMA record format.
5-4 Telica, Inc.

For a PlexView Pro Billing configuration, data is written in BAF format to

a circular buffer file, and another GDI transmitter entity will be started on
the BTS to send the data to the PlexView Pro Billing application. The
dotted circle around AMA Pro Billing in the illustration indicates that the
application can run on the BTS server or on a separate server.
Traffic statistics are sent to the Traffic Collection Application and the
Telica Statistical Analysis Application (TSAA) as shown in Figure 5-2.
The statistical data is tracked for peg counts, busy hour information, traffic
Centum Call Seconds (CSS) and trunk group hold time.
Traffic Collection Application
Track Call
Statistics
Files
(Peg Counts)
Traffic
DATs
Statistics
Track
Busy Hour Daily
Statistics Files
TSAA
ASCII Files
Data/
Conf
PlexView
FTP
Track EMS
Traffic (CCS) Files
Statistics
Track
Raw
Avg Trunk Files
CDRs
Hold Time
P984-AA
05-01-03
Figure 5-2. Traffic Collection Application
Telica, Inc. 5-5

5.4 Provisioning for the Billing and Traffic System

The Plexus 9000 uses the TCP/IP connection between the BTS and the
Plexus 9000 switches to send CDRs to the BTS. IP addresses of the BTS
for the Plexus are provisioned using the ENT-DATASERVER-HOSTCFG
command. Billing and Traffic Collection are enabled in the Plexus using
the ED-BILLSYS and ED-TRAFFICSTATS commands respectively.
In order to make this connection, the Plexus 9000 IP address or name

needs to be previously configured into the configuration file
(plexusDc.ini). If the BTS will be collecting CDRs from multiple Plexus
switches, a directory for each switch should be created (i.e., <plexusDCn>
where n is a unique number or <SwitchName>). A copy of the
plexusDc.ini must be copied into each directory and edited. For traffic
reporting, a copy of the tsaa.conf file is also copied into each directory and
it must also be edited.
5.4.1 The plexusDc.ini File

In order to make this connection, the Plexus 9000 IP address or name
needs to be previously configured into the configuration file
(plexusDc.ini). Refer to Table 5-A for a sample of the plexusDc.ini file.
Refer to the procedures section of this manual and DLP-541 for
instructions to edit this file.
If the BTS is collecting billing and/or traffic data from multiple Plexus
switches, you must have a plexusDc.ini file and a unique directory for
each Plexus. It is suggested that you name the directory as plexusDcn
where n is a unique number or SwitchName with the SwitchName being
the name or TID of the Plexus.
Lines that begin with # (pound sign) are commented lines. The
commented lines may also contain default values. If you wish to change a
default value, it is suggested that that you insert a line with the changed
value. For example, if you wanted to change the LogPath, then you would
insert a line after the DebugPort=2361 line and enter LogPath=<new
value>.
5-6 Telica, Inc.

Table 5-A. plexusDc.ini File

# Template TelicaPlexusDc configuration file.
# $Id: plexusDc_template.ini,v 1.11.2.17 2003/12/03 21:53:58 ggaus Exp $
#
# The parameter comment blocks document the default settings if the
# parameter is not defined in this file.
#
# Parameter names are not case sensitive, but the "=" MUST follow the
# name with no intervening space.
#
#NOTE: actual parameter lines can NOT include comments on the end
##############################
#Data Collector MAIN Entity Configuration
##############################
[DataCollectorConfig]
# Prefix= <none> prefix for various output files (ascii, baf, stats)
# MaxLogQueue= 16384 max trace entries allow on queue before dropping
# MaxFileSize= 10485760 max size in bytes of any single trace file
# MaxFileCount= 6 max old trace log files retained
# LogPath= ./logs directory for trace log files
# LogFilename= dcLog base name of trace log files
# DebugPort= <none> telnet debug port into DataCollector
# DebugBindIp= 0.0.0.0 (INADDR_ANY) override BindIp for debug port only.
# BindIp= 0.0.0.0 (INADDR_ANY) default local bind IP(i/f) for all
# TCP listen and connect calls (allows DC bind
# to system alias IP). Other sections in the ini
# will default to this value if their individual
# BindIp is not defined.
# Timezone= <system> USE ONLY IF SERVER and SWITCH timezones DON'T MATCH
# Timezone is used to calculate file names, file
# rollover times, and some billing fields.
# See end of file for description.
Prefix= SwitchName
##############################
#Receiver Entity Configuration
##############################
[ReceiverConfig]
# GdiPort= 1986 IP port to listen on for GDI connections

# GdiHost= mgcId host/IP mgcId is a unique integer (1-63)
#
# ArchiveDays= 0
# ArchiveInterval= 720 720 minutes = 12 hour (limit 5 - 1440)
# ArchivePath= <DataCollectConfig:LogPath>
# ArchivePrefix= <DataCollectConfig:Prefix>
# ArchivePurgeNull= 1 purge null files
GdiHost= 1 SPA_address
GdiHost= 2 SPB_address
#################################
# Billing entity configuration
#################################
[BillingConfig]
Telica, Inc. 5-7

# AMA Record Formatting Parameters

# --------------------------------
# SensorType= 195 Sensor Type

# SensorId= 0 Sensor Id - If non-zero, it overrides the
# switch Id sent from the switch.
# RecOfficeType= 195 Recording Office Type
# RecOfficeId= 999999 Recording Office Id
#
# DAAMAGen= 1 Directory Assistance AMA Generation
# IntraLATAAMAGen= 1 Intra LATA AMA Generation
# FraudAMAGen= 0 Fraud AMA Generation
# FraudCallType= 800 Call Type for Fraud Calls - Valid values are
# from 800 to 999.
#
# OrigNumberModuleGen= 0 Orig Number Module 164 Generation
# 0 - Use GR-1100 generation rules
# 1 - Generate 164 Module for all
# originating numbers
# TermNumberModuleGen= 0 Term Number Module 164 Generation
# 1 - Generate 164 Module for international
# terminating numbers
# DialedDigitsModuleGen= 0 Dialed Digits Module Generation (Module 101)
# OutpulseDigitsModuleGen= 0 Outpulse Digits Module Generation
# (Module 40)
# TrunkIdModuleGen= 1 Trunk Id Module Generation
# 0 – Disable trunk id module generation
# 1 – Generate Module 104
# 2 – Generate Module 167 (Large trunks)
# SipCallIdModuleGen= 0 SIP Call Id Module Generation (Module 198)
# CallIdModuleGen= 0 Call Id Module Generation (Module 611)
# ReleaseCauseModuleGen= 0 Release Cause Module Generation
# (Module 616)
# QoSModuleGen= 0 Quality of Service Module Generation
# (Module 264)
# SeqNumModuleGen= 0 Sequence Number Module Generation
# (Module 611 and 616)
# CallSeqModuleCntxt= 90000 Call Sequence Number Module Context
# RecordSeqModuleCntxt= 80 Record Sequence Number Module Context
# FinalTrunkModuleGen= 0 Final Trunk Module Generation (Module 611)
# FinalTrunkModuleCntxt= 90010 Final Trunk Module Context
# TDMRsrcModuleGen= 0 TDM Resource Module Generation (Module 611)
# OrigTDMRsrcModuleCntxt= 90020 Orig TDM Resource Module Context
# TermTDMRsrcModuleCntxt= 90021 Term TDM Resource Module Context
# PktRsrcModuleGen= 0 Packet Resource Module Generation
# (Module 613)
# OrigPktRsrcModuleCntxt= 90030 Orig Packet Resource Module Context
# TermPktRsrcModuleCntxt= 90031 Term Packet Resource Module Context
# PhysicalModuleGen= 0 Physical Interface Module Generation
# (Module 612)
# PhysicalModuleCntxt= 90040 Physical Interface Module Context
# PrefixModuleGen= 0 Prefix Module Generation (Module 616)
# DialedPrefixModuleCntxt= 81 Dialed Prefix Module Context
# CalledPrefixModuleCntxt= 82 Called Prefix Module Context
# TreatmentModuleGen= 0 Call Treatment Module Generation
# (Module 198)
# TreatmentModuleCntxt= 90050 Call Treatment Module Context
#
5-8 Telica, Inc.

# 211CallType= 0 Call Types for N11 Calls - Valid values are from
# 311CallType= 0 zero to 999. The value zero disables AMA generation.
# 411CallType= 9
# 511CallType= 0
# 611CallType= 0
# 711CallType= 0
# 811CallType= 0
# 911CallType= 0
# Output Options
# --------------
# Enable ASCII output 0 - Disable 1 - Enable

# Enable ASCII push 0 - Disable 1 - Enable
# (see section AsciiPush)
ASCIIEnabled= 1
ASCIIPush= 0
# Enable BAF output (AMA Lite) 0 - Disable 1 - Enable

# Enable BAF push 0 - Disable 1 - Enable
# (see section BafPush)
BAFEnabled= 0
BAFPush= 0
# Enable PlexView Pro output 0 - Disable 1 - Enable

ProBillEnabled= 0
# ASCII/BAF file parameters

# -------------------------
# Note: These parameters are relevant only if ASCII or

# BAF (AMA Lite) output is enabled
# Directory for ASCII output files

ASCIIDir= ./Bill_data/ascii
# Directory for BAF output files

BAFDir= ./Bill_data/baf
# Time BAF and ASCII output files are open for writing (minutes)
FileInterval= 120
# Purge empty BAF and ASCII files

# 0 - Do not purge
# 1 - Purge
PurgeNull= 0
# PlexView Pro Parameters

# -----------------------
# Note: These parameters are relevant only if PlexView Pro output is enabled
#
# GDIDir= ./Bill_data/proBill Directory for PlexView Pro data record buffer
Telica, Inc. 5-9

##########################
# ProBilling configuration
##########################
[ProBillingConfig]
# gdiRecordSize= 128 Average size of BAF records in bytes

# gdiMiniRecs= 1024 Number of records to be held in shared memory
# gdiMiniInWhole= 4000 Number of gdiMiniRecs to be stored in disk buffer
# (total records = gdiMiniRecs * gdiMiniInWhole)
# gdiPsPort= 1983 port that ProBilling is listening on
# gdiPsRaoHost= <none> Revenue Accounting Host (ProBilling Server)
# or 0 to 4 instances of
# gdiPsHost= <none> ProBilling Server hostname/IP
#gdiPsRaoHost= localhost
#################################
# AsciiPush entity configuration
#################################
# Configure FTP push of ASCII billing files to remote server
[AsciiPush]
# ArchiveDays= 7 Number of days to retain files that have been pushed

# DestinationDir= Destination directory on FTP server for files
# Passive= 1 Use FTP passive transfer (0/1 F/T)
# Host= FTP server hostname/IP
# User= FTP server login id
# Password= FTP server login password
#################################
# BafPush entity configuration
#################################
# Configure FTP push of BAF (AMA Lite) billing files to remote server
[BafPush]

#################################
# Statistics entity configuration
#################################
[StatisticsConfig]
# TypeOf740If= 4 4=TSAA statistics data fed to tsaa reporter

# 8=NONE
# LogPath= ./stats_log Path for statistics log file (future)
# TsdsPath= ./tsds_data Path for TSDS .dat files (for TSAA input)
5-10 Telica, Inc.

############INFORMATION#######################################################
# Timezone Info, [DataCollectorConfig] section
# For detailed description of the rules for defining Timezone,
# see the description of the TZ environment variable in environ(5).
#
# US/Alaska US/Central US/Hawaii US/Pacific
# US/Aleutian US/East-Indiana US/Michigan US/Pacific-New
# US/Arizona US/Eastern US/Mountain US/Samoa
#
# The Timezone adjusts the time offset from GMT and the rules for
# daylight savings time (if applicable).
#
# If the configured Timezone is invalid, then use GMT, if no Timezone
# is provided then server's time zone is used for time calculations.
5.1.1.1 Data Collector Main Entity Configuration

The following portion of the plexusDC<_prefix>.ini file indicates the
main entity configuration.
##############################
#Data Collector MAIN Entity Configuration
##############################
[DataCollectorConfig]
# Prefix= <none> prefix for various output files (ascii, baf, stats)
# MaxLogQueue= 16384 max trace entries allow on queue before dropping
# MaxFileSize= 10485760 max size in bytes of any single trace file
# MaxFileCount= 6 max old trace log files retained
# LogPath= ./logs directory for trace log files
# LogFilename= dcLog base name of trace log files
# DebugPort= <none> telnet debug port into DataCollector
# DebugBindIp= 0.0.0.0 (INADDR_ANY) override BindIp for debug port only.
# BindIp= 0.0.0.0 (INADDR_ANY) default local bind IP(i/f) for all
# TCP listen and connect calls (allows DC bind
# to system alias IP). Other sections in the ini
# will default to this value if their individual
# BindIp is not defined.
# Timezone= <system> USE ONLY IF SERVER and SWITCH timezones DON'T MATCH
# Timezone is used to calculate file names, file
# rollover times, and some billing fields.
# See end of file for description.
Prefix= SwitchName
MaxLogQueue
This field is the maximum number of entries on the queue before entries
are dropped. The default size of 16384 entries does not need to be
changed.
Telica, Inc. 5-11

MaxFileSize
This field is the maximum size of any trace file in bytes. The default size
of 10485760 does not need to be changed.
MaxFileCount
This field indicates the maximum number of old log files that are retained
on the disk. The default size of 6 does not need to be changed.
LogPath
This field indicates the name of the directory and its path of where the logs
are stored. The default is ./logs.
LogFilename
This field indicates the base name of log files and does not need to be
changed from the default.
DebugPort
The field indicates the telnet debug port into Data Collector. It has been
set to 2361.
DebugBindip
This field indicates the override IP address of the Plexus for debug only.
The default is 0.0.0.0 so that TCP can listen and connect calls (allows DC
bind to system alias IP).
Bindip
This field indicates the IP address of the Plexus. The default is 0.0.0.0 so
that TCP can listen and connect calls (allows DC bind to system alias IP).
Other sections in the plexusDC<_prefix>.ini file will default to this value
if their individual BindIp is not defined.
Timezone
This field is used if the server and switch time zones do not match. It is
used to calculate file names, file rollover times, and some billing fields.
Prefix
This field is used to assign the switch name.
5-12 Telica, Inc.

5.1.1.2 Receiver Entity Configuration

receiver configuration.
##############################
#Receiver Entity Configuration
##############################
[ReceiverConfig]
# GdiPort= 1986 IP port to listen on for GDI connections

# GdiHost= mgcId host/IP mgcId is a unique integer (1-63)
#
# ArchiveDays= 0
# ArchiveInterval= 720 720 minutes = 12 hour (limit 5 - 1440)
# ArchivePath= <DataCollectConfig:LogPath>
# ArchivePrefix= <DataCollectConfig:Prefix>
# ArchivePurgeNull= 1 purge null files
GdiHost= 1 SPA_address
GdiHost= 2 SPB_address
GDIPort
The GDI (Generating system to Data server Interface) server port is 1986
and does not need to be changed. This is the port of the server that
receives the CDRs.
GDIHost
GDIHost is the mgcId and the IP address or name of each the switch’s
system processors. The mgcId indicates the unique media gateway
controller identification which a number from 1 to 63. The defaults are 1
and 2. If the Data Collector is collecting information from multiple
Plexus, there will be multiple plexusDC<_prefix>.ini files and at this time
the GDI host can be 1 and 2 in each of those files. The host/IP is the IP
address or name of the system processor. These fields must be changed so
are inserted with no comment indicator at the end of this section.
ArchiveDays
This field indicates the number of days to hold archive files before
deleting. The default value of 0 disables this feature.
ArchiveInterval
This field indicates how often the files will be archived. The range is 5 to
1440 minutes and the default is 720 minutes or 12 hours.
ArchivePath
This field indicates the path for archived files.
Telica, Inc. 5-13

ArchivePrefix
This field indicates the prefix for archived files.
ArchivePurgeNull
This field indicates whether or not null files will be purged. A value of 0
indicates that they will not be purged and the default value of 1 indicates
that they will be purged.
5.1.1.3 Billing Entity Configuration

configuration for billing. The billing configuration fields for Plexus
running a software version earlier than 3.8 were provisioned in the Plexus
with the ED-BILLSYS command.
#################################
# Billing entity configuration
#################################
[BillingConfig]
# AMA Record Formatting Parameters

# --------------------------------
# SensorType= 195 Sensor Type

# SensorId= 0 Sensor Id - If non-zero, it overrides the
# switch Id sent from the switch.
# RecOfficeType= 195 Recording Office Type
# RecOfficeId= 999999 Recording Office Id
#
# DAAMAGen= 1 Directory Assistance AMA Generation
# IntraLATAAMAGen= 1 Intra LATA AMA Generation
# FraudAMAGen= 0 Fraud AMA Generation
# FraudCallType= 800 Call Type for Fraud Calls - Valid values are
# from 800 to 999.
#
# OrigNumberModuleGen= 0 Orig Number Module 164 Generation

# originating numbers
# TermNumberModuleGen= 0 Term Number Module 164 Generation
# 1 - Generate 164 Module for international
# DialedDigitsModuleGen= 0 Dialed Digits Module Generation (Module 101)
# OutpulseDigitsModuleGen= 0 Outpulse Digits Module Generation
# (Module 40)
# TrunkIdModuleGen= 1 Trunk Id Module Generation
# 0 – Disable trunk id module generation
# 1 – Generate Module 104
# 2 – Generate Module 167 (Large trunks)
# SipCallIdModuleGen= 0 SIP Call Id Module Generation (Module 198)
# CallIdModuleGen= 0 Call Id Module Generation (Module 611)
5-14 Telica, Inc.

# ReleaseCauseModuleGen= 0 Release Cause Module Generation

# (Module 616)
# QoSModuleGen= 0 Quality of Service Module Generation
# (Module 264)
# SeqNumModuleGen= 0 Sequence Number Module Generation

# (Module 611 and 616)
# CallSeqModuleCntxt= 90000 Call Sequence Number Module Context
# RecordSeqModuleCntxt= 80 Record Sequence Number Module Context
# FinalTrunkModuleGen= 0 Final Trunk Module Generation (Module 611)
# FinalTrunkModuleCntxt= 90010 Final Trunk Module Context
# TDMRsrcModuleGen= 0 TDM Resource Module Generation (Module 611)
# OrigTDMRsrcModuleCntxt= 90020 Orig TDM Resource Module Context
# TermTDMRsrcModuleCntxt= 90021 Term TDM Resource Module Context
# PktRsrcModuleGen= 0 Packet Resource Module Generation
# (Module 613)
# OrigPktRsrcModuleCntxt= 90030 Orig Packet Resource Module Context
# TermPktRsrcModuleCntxt= 90031 Term Packet Resource Module Context
# PhysicalModuleGen= 0 Physical Interface Module Generation
# (Module 612)
# PhysicalModuleCntxt= 90040 Physical Interface Module Context
# PrefixModuleGen= 0 Prefix Module Generation (Module 616)
# DialedPrefixModuleCntxt= 81 Dialed Prefix Module Context
# CalledPrefixModuleCntxt= 82 Called Prefix Module Context
# TreatmentModuleGen= 0 Call Treatment Module Generation
# (Module 198)
# TreatmentModuleCntxt= 90050 Call Treatment Module Context
#
# 211CallType= 0 Call Types for N11 Calls - Valid values are from
# 311CallType= 0 zero to 999. The value zero disables AMA generation.
# 411CallType= 9
# 511CallType= 0
# 611CallType= 0
# 711CallType= 0
# 811CallType= 0
# 911CallType= 0
AMA Record Formatting Parameters

SensorType
This field identifies the type of switch in the billing office. The factory
default of sensorType is 195 and currently is the only acceptable value,
indicating that the switch is the Plexus 9000.
SensorId
The sensor ID identifies the local switching element that generates the
billing records. A value of 0 (the factory default) indicates that the
parameter is not applicable. Valid values are 0 to 999999. The default is
0 and should be changed.
RecordingOfficeType
The RecOfficeType field identifies the type of switch in the billing office.
The factory default is 195 and currently the only acceptable value,
indicating that the switch is the Plexus 9000.
Telica, Inc. 5-15

RecordingOfficeID
The RecOfficeId field identifies the billing office. A value of 0 (the
factory default) indicates that the parameter is not applicable. Valid
values are 0 to 999999. The default is 999999 and can be changed.
Directory Assistance AMA Generation

The DAAMAGen field indicates whether call detail record processing for
directory assist calls is set to be in service or out of service. The default is
1 or enabled. Values are:
0 = Disable
1 = Enable
IntraLATA AMA Generation

The IntraLATAAMAGen field identifies the default IntraLATA call type.
Call processing determines the call type when intralataCallType is set to
zero. The default is 1 or enabled. Values are:
0 = Disable
1 = Enable
Fraud AMA Generation

The FraudAMAGen field identifies whether a CDR will be generated for
the beginning of a fraud call. The default is 0 or disabled. Values are:
0 = Disable
1 = Enable
Call Type for Fraud Calls

The FraudCallType field identifies the call type to be used for fraud calls.
The default is 800, can be a value from 800 to 999, which are the call
types that are not administered by Telcordia.
Originating Number Module Generation

The OrigNumberModuleGen field identifies whether GR-1100 generation
rules will be used or whether all module 164 originating number
information for fields 133 to 137 will be generated. The default is 0.
0 = Use GR-1100 generation rules
1 = Generate 164 Module for all originating numbers
5-16 Telica, Inc.

Terminating Number Module Generation

The TermNumberModuleGen field identifies whether GR-1100 generation
rules will be used, whether module 164 will be used for terriginating
international numbers or whether all module 164 terminating number
information for fields 113 to 117 will be generated. The default is 0.
0 = Use GR-1100 generation rules
1 = Generate 164 Module for all international terminating numbers
2 = Generate 164 Module for all terminating numbers
Dialed Digit Module Generation (Module 101)

The DialedDigitsModuleGen field identifies whether dialed digits for
fields 156 to 158 will be generated. The default is 0 or disabled. Values
are:
0 = Disable
1 = Enable
Outpulse Digits Module Generation (Module 40)

The OutpulseDigitsModuleGen field identifies whether outpulse digits for
fields 168 and 169 will be generated. The default is 0 or disabled. Values
are:
0 = Disable
1 = Enable
Trunk Id Module Generation (Module 104)

The TrunkIdModuleGen field enables or disables Module 104 or Module
167 (for large trunks), which captures trunk identification. When enabled
the trunk group, as well as the particular trunk within the trunk group, is
identified in fields 64 to 69 of the ASCII or AMA Lite billing report. The
default is 1 or generate Module 104. Values are:
0 – Disable trunk id module generation

1 – Generate Module 104
2 – Generate Module 167 (Large trunks)
SIP Call Id Module Generation (Module 198)

The SipCallIdModuleGen enables or disables inserting an ASCII string for
a SIP called or calling party number. The default is 1 or enabled. Values
are:
0 = Disable
1 = Enable
Telica, Inc. 5-17

Call Id Module Generation (Module 611)

The CallIdModuleGen field enables or disables the generation of a unique
identification number that matches a number used in traffic statistics
reports. The call identifier is generated by the switch so call IDs are
unique only among calls from a particular switch. The default is 0 or
disabled. Values are:
0 = Disable
1 = Enable
Release Cause Module Generation (Module 616)

The ReleaseCauseModuleGen field identifies whether the release cause
module 616 will be generated for fields 170 and 172. The default is 0 or
disabled. The default is 0 or disabled. Values are:
0 = Disable
1 = Enable
Quality of Service (Qos) Module Generation (Module 264)

The QosModuleGen field identifies whether the release cause module 616
will be generated for fields 186 to 201. The default is 0 or disabled.
Values are:
0 = Disable
1 = Enable
Sequence Number Module Generation (Module 611 and 616)

Unique call sequence numbers are generated for each billing record sent
from the Plexus 9000 to the BTS. The call sequence number is captured
in AMA Module 611. For cases where multiple records are generated
from one billing record sent from the switch (i.e. Call Forwarding), the
BTS includes an additional record sequence number. Additional record
sequence number fields will only be included on subsequent billing
records. The record sequence numbers will be captured in AMA Module
616.
The SeqNumModuleGen field enables or disables the generation of

sequence numbers with module 611 and 616. The default is 0 or disabled.
Values are:
0 = Disable
1 = Enable
Call Sequence Number Module Context

The CallSeqModuleCntxt field identifies module 611 as a sequence
number module. The default is 90000. Values are 90000 to 99998.
5-18 Telica, Inc.

Record Sequence Number Module Context

The RecordSeqModuleCntxt identifies module 616 as a sequence number
module. The default is 80.
Final Trunk Module Generation (Module 611)

The FinalTrunkModuleGen field enables or disables the generation of
final trunks with module 611. The default is 0 or disabled. Values are:
0 = Disable
1 = Enable
Final Trunk Module Context

The FinalTrunkModuleCntxt field identifies module 611 as a final trunk
module. The default is 90010. Values are 90000 to 99998.
TDM Resource Module Generation (Module 611)

The TDMRsrcModuleGen field identifies whether module 611 TDM
resources will or will not be generated. The default is 0 or disabled.
Values are:
0 = Disable
1 = Enable
Originating TDM Resource Module Context

The OrigTDMRsrcModuleCntxt field identifies the context number. The
default value is 90020. Values are 90000 to 99998.
Terminating TDM Resource Module Context

The TermTDMRsrcModuleCntxt field identifies the context number. The
default value is 90021. Values are 90000 to 99998.
Packet Resource Module Generation (Module 613)

The PktRsrcModuleGen field identifies whether module 613 packet
resource information will be generated. The default is 0 or disabled.
Values are:
0 = Disable
1 = Enable
Originating Packet Resource Module Context

The OrigPktRsrcModuleCntxt field identifies the originating context
number. The default value is 90030. Values are 90000 to 99998.
Terminating Packet Resource Module Context

The TermPktRsrcModuleCntxt field identifies the terminating context
number. The default value is 90031. Values are 90000 to 99998.
Telica, Inc. 5-19

Physical Interface Module Generation (Module 612)

The PhysicalModuleGen field enables or disables the appending of non-
standard module 612 to all billing records for physical circuit
identification. The default is 0 or disabled. Values are:
0 = Disable
1 = Enable
Physical Interface Module Context

The PhysicalModuleCntxt field identifies the context inserted into module
612 when the value of append612 is “enabled”. The factory default is
90040. Values are 90000 to 99998.
Prefix Module Generation (Module 616)

The PrefixModuleGen field identifies whether module 616 for fields 163
and 164 will be generated. The default is 0 or disabled. Values are:
0 = Disable
1 = Enable
Dialed Prefix Module Context

The DialedPrefixCntxt field identifies the dialed prefix context number.
The default value is 81.
CalledPrefix Module Context

The CalledPrefixModuleCntxt field identifies the called prefix context
number. The default value is 82.
Treatment Module Generation

The TreatmentModuleGen field identifies whether module 198 fields will
be generated. The default is 0 or disabled. Values are:
0 = Disable
1 = Enable
Treatment Module Context

The TreatmentModuleCntxt field identifies the treatment context. The
factory default is 90050. Values are 90000 to 99998.
Call Types for N11 Calls

These fields assign a call type for N11 calls. The values can be 0 to 999.
Values of 1 to 799 are administered by Telcordia. The default value for
all call types, except 411, is 0 that disables AMA generation. 411 call
type has a default of “9” which is the Telcordia call type for 411 calls.
5-20 Telica, Inc.

5.1.1.4 Billing Output Options

configuration for enabling or disabling output options. Outputs can be any
combination.
# Output Options
# --------------
# Enable ASCII output 0 - Disable 1 - Enable

# Enable ASCII push 0 - Disable 1 - Enable
# (see section AsciiPush)
ASCIIEnabled= 1
ASCIIPush= 0
# Enable BAF output (AMA Lite) 0 - Disable 1 - Enable

# Enable BAF push 0 - Disable 1 - Enable
# (see section BafPush)
BAFEnabled= 0
BAFPush= 0
# Enable PlexView Pro output 0 - Disable 1 - Enable

ProBillEnabled= 0
Enable ASCII Output

The ASCIIEnabled field enables or disables the generation of ASCII
Billing System records. Default is 1 or enable. Values are:
0 = Disable
1 = Enable
Enable ASCII Push

The ASCIIPush field enables or disables whether files will be FTPed to
another server. The default is 0 or disabled. Values are:
0 = Disable
1 = Enable
Enable BAF output (AMA Lite)

The BAFEnabled field enables or disables the generation of AMA Lite
records. Default is 0 or disable. Values are:
0 = Disable
1 = Enable
Telica, Inc. 5-21

Enable BAF Push

The BAFPush field enables or disables whether files will be FTPed to
another server. The default is 0 or disabled. Values are:
0 = Disable
1 = Enable
Enable PlexView Pro Output

The ProBillingEnabled field enables or disables the generation of Billdats
records for the PlexView Pro Billing System. Default is 0 or disable.
Values are:
0 = Disable
1 = Enable
5.1.1.5 ASCII and AMA Lite (BAF) File Parameters

configuration for ASCII billing or AMA Lite (BAF) file parameters.
These parameters are only relevant if either ASCII billing or AMA Lite
was enabled.
# ASCII/BAF file parameters

# -------------------------
# Note: These parameters are relevant only if ASCII or

# BAF (AMA Lite) output is enabled
# Directory for ASCII output files

ASCIIDir= ./Bill_data/ascii
# Directory for BAF output files

BAFDir= ./Bill_data/baf
# Time BAF and ASCII output files are open for writing (minutes)
FileInterval= 120
# Purge empty BAF and ASCII files

# 0 - Do not purge
# 1 - Purge
PurgeNull= 0
Directory for ASCII output files

The ASCIIDir field identifies the working directory for data, connection
information and log files of the ASCII Billing System. The default is
./Bill_data/ascii and does not need to be changed.
5-22 Telica, Inc.

Directory for BAF output files

The BAFDir field identifies the working directory for data, connection
information and log files of AMA Lite billing. The default is
./Bill_data/baf and does not need to be changed.
Time BAF and ASCII output files are open for writing (minutes)
The FileInterval field indicates the interval or frequency that files are sent
to the server. The default is 120 minutes. The minimum is five minutes
and the maximum interval is 1440 minutes, which is equal to one day or
24-hours. The start time is midnight.
Purge empty BAF and ASCII files

The PurgeNull field allows files with zero (0) records to be deleted when
it is equal to 1. Files that are saved then have at least one record. The
default is 0 or do not purge. Values are:
0 = Do not purge
1 = Purge
5.1.1.6 PlexView Pro Billing (Billdats) Parameters

These parameters in the following fields are relevant only if PlexView Pro
output is enabled.
# PlexView Pro Parameters

# -----------------------
# Note: These parameters are relevant only if PlexView Pro output is enabled
#
# GDIDir= ./Bill_data/proBill Directory for PlexView Pro data record buffer
##########################
# ProBilling configuration
##########################
[ProBillingConfig]
# gdiRecordSize= 128 Average size of BAF records in bytes

# gdiMiniRecs= 1024 Number of records to be held in shared memory
# gdiMiniInWhole= 4000 Number of gdiMiniRecs to be stored in disk buffer
# (total records = gdiMiniRecs * gdiMiniInWhole)
# gdiPsPort= 1983 port that ProBilling is listening on
# gdiPsRaoHost= <none> Revenue Accounting Host (ProBilling Server)
# or 0 to 4 instances of
# gdiPsHost= <none> ProBilling Server hostname/IP
#gdiPsRaoHost= localhost
Telica, Inc. 5-23

Directory for PlexView Pro Data Files

The GDIDir field identifies the directory for data, connection information
and log files for the PlexView Pro Billing application. The default is
/Bill_data/proBill and does not need to be changed.
Average Record Size (bytes)

The gdiRecordSize field indicates the average record size and the default
is 128 bytes.
Number of Records to be Held in Shared Memory

The gdiMiniRecs field indicates the number of records to be held in shared
memory and the default is 1024 record.
Number of Records to be Stored in Disk Buffer

The gdiMiniInWhole field indicates the number of records to be stored in
the disk buffer and the default is 4000 records.
Revenue Accounting Host

The gdiPsRaoHost field identifies the ProBilling server revenue
accounting host with a name or an IP address or there can be up to 4
instances of gdiPsHost.
5.1.1.7 ASCII and BAF Push Entity Configuration
#################################
# AsciiPush entity configuration
#################################
# Configure FTP push of ASCII billing files to remote server
[AsciiPush]

#################################
# BafPush entity configuration
#################################
# Configure FTP push of BAF (AMA Lite) billing files to remote server
[BafPush]

5-24 Telica, Inc.

ASCII and BAF (AMA Lite) files can be FTPed to remote servers. The
configuration of the push entity specifies the name of the server, the
username and password.
Archive Days
This field indicates the number of to retain files that have been pushed
before deleting them from the BTS server. The default is 7 days.
Destination Directory
This field indicates the output directory on the server (full path).
This directory needs to already exist and the user must have read and write
permission to the directory.
Passive
This field indicates whether to use FTP passive transfer. Passive transfers
are typically used when there is a firewall involved. The default is 1 or
enable passive transfers. Values are:
0 = Disable
1 = Enable
Host
This field is the name or IP address of the server to which the files will be
FTPed.
User
This field is the username that is used when FTPing the ASCII or BAF
files.
Password
This field is the password that is used when FTPing the ASCII or BAF
files.
5.1.1.8 Statistics Entity Configuration

configuration for Traffic Collection or statistics file parameters.
#################################
# Statistics entity configuration
#################################
[StatisticsConfig]
# TypeOf740If= 4 4=TSAA statistics data fed to tsaa reporter

# 8=NONE
# LogPath= ./stats_log Path for statistics log file (future)
# TsdsPath= ./tsds_data Path for TSDS .dat files (for TSAA input)
Telica, Inc. 5-25

TypeOf740If
This field enables the collection of traffic statistics data. If you wish to
disable the traffic collection application, you should insert
TypeOf740IF=8 after TsdsPath line.
LogPath
This field indicates the directory that keeps the statistics data, log, and
connection files. The default is “./stats_log” and there is no need to
change from the default.
TdsPath
the TelicaStatsServer. The default path is ./tsds_data.
5.4.2 The tsaa.conf File

The TCA is a stand-alone application that runs on Sun server. It interfaces
with the BTS, which generates CDRs in binary files. The TCA parses this
data and generates peg count records and calculates busy hour information
in text formats.
The TCA configuration file named tsaa.conf resides in the same directory
as the plexusDC<prefix>.ini file. It is automatically started when the
S99PLXStats script is run.
Once the TCA is operational, the application generates peg counts, CCS,
holdtime and busy hour information as determined by the
tsaa_<prefix>.conf file. The application creates directories specified in
the tsaa_<prefix>.conf file, for its output and log files. The log file is:
tsaa_<pid>.log
with “pid” meaning process ID.
The changes you must make to this file are shown in boldface type. Other
lines may also be changed. If you enter a configuration point value
beyond a valid range, default values are used. You must save the
configuration before exiting. A sample of the tsaa_<prefix>.conf file is
shown in Table 5-B.
5-26 Telica, Inc.

Table 5-B. Sample tsaa_<prefix>.conf File

# FileName: *tsaa.conf
#
# This file contains the configuration information for the
# Telica Statistical Analysis Application (TSAA), and should be
# modified by authorized personnel only.
#
Prefix: boston
Input Directory: tsds_data
Output Directory: tsaa_boston
Log Directory: tsaa_boston/log
Percent Blocking: 0.01
Peg Count Report: 1
ASR Report: 1
Hold Time Report: 1
SS7 Trkgrp CCS Report: 3
Intfcgrp CCS Report: 3
CAS Trkgrp CCS Report: 3
BICC Trkgrp CCS Report: 3
SIP Trkgrp CCS Report: 3
GR303 Intfcgrp CCS Report: 3
CAS Intfcgrp CCS Report: 3
ASCII CDR Report: 1
Detailed Peg Report: 1
Calculate DN Peg Count: 1
Busy Hour Granularity: 30
CCS Granularity Period: 4
Peg Count Granularity Period: 4
ASR Granularity Period: 4
Hold Time Granularity Period: 4
Input Storage Duration: 30
Output Storage Duration: 30
FTP to EMS: 0
FTP Transfer Interval: 60
EMS IP Address: 127.0.0.1
EMS Username: anonymous
EMS Password: boston
EMS Output Directory: /tsaa_data
Fields:
Prefix
This field indicates the prefix that is unique for a switch and was
established in the PlexusDC.ini or tsds.conf file.
Telica, Inc. 5-27

Input Directory
the TelicaStatsServer. It must be identical to the value specified in the
Statistics entity configuration section of the PlexusDC.ini file or the
DATA_DIR parameter of the tsds.conf file. The default name is
tsds_data.
Output Directory
This field specifies the name of the output directory for statistics data files.
This name should be changed to tsaa_<prefix>.
Log Directory
This field specifies the name of the output directory for all log files. The
name should be changed to tsaa_<prefix>/log. It must be identical to the
value specified in the Statistics entity configuration section of the
PlexusDC.ini file
Percent Blocking
This field indicates the value used in the calculation of Erlang B,
specifying the acceptable number of failure of calls due to an insufficient
number of lines available. The minimum is 0; the maximum is 1; and the
default is 0.01. Refer to section 5.4.4 for a description of Erlang B.
Peg Count Report

This field specifies whether or not to report Peg Counts.
0 = Do not report Peg Counts.
1 = Report Peg Counts. This is the default value.
ASR Report
This field specifies whether or not to report the Answer to Seizure Ratio
(ASR).
0 = Do not report ASR.
1 = Report ASR. This is the default value.
Hold Time Report

This field specifies whether or not to report trunk group average hold time.
0 = Do not report average hold time.
1 = Report the average hold time. This is the default value.
5-28 Telica, Inc.

SS7 Trkgrp CCS Report

This field specifies the format for the SS7 trunk group CCS reporting.
Intfcgrp CCS Report

This field specifies the format for the interface group CCS reporting.
CAS Trkgrp CCS Report

This field specifies the format for the CAS trunk group reporting.
BICC Trkgrp CCS Report

This field specifies the format for the BICC trunk group reporting.
SIP Trkgrp CCS Report

This field specifies the format for the SIP trunk group reporting.
Telica, Inc. 5-29

GR303 Intfcgrp CCS Report

This field specifies the format for the GR303 interface group CCS
reporting.
CAS Intfcgrp CCS Report

This field specifies the format for the CAS interface group CCS reporting.
This is the default value
ASCII CDR Report

This field enables or disables ASCII CDR reporting every five minutes.
1 = Only Call Release CDRs are printed. This is the default value
2 = Both Long Duration and Release CDRs are printed.
Detailed Peg Report

This field enables or disables detailed peg reporting.
0 = Detailed reporting is disabled. Pegged for the state of the call.
1 = Detailed reporting is enabled. Pegged for the release cause
codes. This is the default value
Calculate DN Peg Count

This field enables or disables the calculation of Directory Number (DN)
peg counts.
0 = Do not calculate DN Peg Counts.
1 = Calculate DN Peg Counts. This is the default value.
Busy Hour Granularity

This field specifies the granularity of the busy hour calculation. Units are
in minutes. Valid range is 0, 5, 30 and 60 and the default is 30.
0 = Disable.
5 = 5 minutes.
30 = 30 minutes - This is the default value.
60 = 60 minutes or 1 hour.
5-30 Telica, Inc.

CCS Granularity Period

disk. The values are 2, 3 and 4.
4 = Created every hour. This is the default value
Peg Count Granularity Period

disk. The values are 2, 3, 4 and 5.
ASR Granularity Period

This field specifies the granularity of how often Answer to Seizure Ratio
(ASR) files are written to disk. The values are 2, 3, 4 and 5.
5 = Created once a day.
Hold Time Granularity Period

disk. Values are 2, 4 and 5.
Input Storage Duration

This field specifies the number of days to store input files. Values are 0 to
180.
If tsaa is configured to ftp files, even if the files are older than “Input
Telica, Inc. 5-31

Output Storage Duration

This field specifies number of days to store files. Values are 0 to 180.
If tsaa is configured to ftp files, even if the files are older than “Output
Note: The following fields refer to files that are FTPed to the EMS
server
FTP to EMS
This field specifies whether or not to FTP to Element Management System
(EMS).
0 = Do not FTP to EMS.
1 = FTP to EMS
FTP Transfer Interval

This field specifies the interval between FTPs to EMS. Values are 30 to
900 seconds. The default value is every 60 seconds.
EMS IP Address:
This field specifies the IP address of the EMS server.
EMS Username:
This field specifies the username for EMS.
EMS Password:
This field specifies the password for EMS.
EMS Output Directory:

This field specifies the output directory on the EMS server (full path).
This directory needs to already exist and the EMS user must have read and
write permission to the directory.
5.4.3 The tsaa_<pid>.log File

This file stores the TSAA current activity by the process ID (PID).
Common activities are peg counts, busy hour calculations, CCS reporting,
hold time calculating and rolling of logs, but error codes and other
debugging information are also reported in the file.
5-32 Telica, Inc.

5.4.4 Erlang B
Erlang and Erlang B calculations are used in the creation of busy hour call
reports. The report specifies the number of Erlangs and circuits and the
circuit usage percentage.
An Erlang is a unit of telecommunications traffic measurement. Strictly

speaking, an Erlang represents the continuous use of one voice path. In
practice, it is used to describe the total traffic volume of one hour. For
example, if a group of users made 30 calls in one hour, and each call had
an average call duration of 5 minutes, then the number of Erlangs this
represents is worked out as follows:
Minutes of traffic in the hour = number of calls x duration
Minutes of traffic in the hour = 30 x 5
Minutes of traffic in the hour = 150
Hours of traffic in the hour = 150 / 60
Hours of traffic in the hour = 2.5
Traffic figure = 2.5 Erlangs
The Erlang B traffic model is used by telephone system designers to

estimate the number of lines required for PSTN connections or private
wire connections. The three variables involved are Busy Hour Traffic
(BHT), Blocking and Lines:
Busy Hour Traffic (in Erlangs) is the number of hours of call traffic
there are during the busiest hour of operation of a telephone
system.
Blocking is the failure of calls due to an insufficient number of
lines being available. For example, 0.03 mean 3 calls blocked per
100 calls attempted.
Lines is the number of lines in a circuit.
Telica, Inc. 5-33

The Erlang B algorithm is as follows:
where a is the busy hour traffic in Erlangs, c is the number of lines, and
B(c,a) is the blockage. The application uses this equation to determine c.
The model assumes that all blocked calls are immediately cleared.
5-34 Telica, Inc.

6. ASCII Billing Reports
6.1 Introduction ..........................................................................................................6-2

6.2 CDR and ABS Formats ........................................................................................6-2
6.2.1 CDR Data Prior to Conversion.................................................................6-2
6.2.2 ASCII Files After Conversion..................................................................6-4
6.3 ASCII-Format Master Record Field Descriptions ...............................................6-9
6.4 Module Inclusion Rules .....................................................................................6-60
6.4.1 Module 021, Carrier Access – Originating ............................................6-61
6.4.2 Module 022, Long Duration Connection ...............................................6-61
6.4.3 Module 025, Circuit Release Module ....................................................6-65
6.4.4 Module 027, Business Customer ID Module .........................................6-65
6.4.5 Module 029, Alternate Billing Number Module....................................6-66
6.4.6 Module 040, Digits Module ...................................................................6-66
6.4.7 Module 049, Calling Name/Number Delivery Module .........................6-66
6.4.8 Module 68, Called Directory Number (DN) Descriptor ........................6-67
6.4.9 Module 101, Digits Dialed Module........................................................6-67
6.4.10 Module 102, Authorization Code Module ............................................. 6-67
6.4.11 Module 103, Account Code/Customer Dialed Account Recording
(CDAR) Module ....................................................................................6-67
6.4.12 Module 104, Trunk Identification Module.............................................6-68
6.4.13 Module 105, Message Detail Recording (MDR) ...................................6-68
6.4.14 Module 164, E.164/X.121 Number Module ..........................................6-68
6.4.15 Module 198, Flex Module......................................................................6-68
6.4.16 Module 264, Quality of Service (QoS) (NDGR) ...................................6-68
6.4.17 Module 306, Originating Line Information Parameter (OLIP)..............6-68
6.4.18 Module 611, Generic Module ................................................................6-68
6.4.19 Module 612, Generic Module: Two Digits String Format.....................6-69
6.4.20 Module 613, Generic Module: Three Digits String Format...................6-69
6.4.21 Module 616, 5 Digit Information Module..............................................6-69
6.4.22 Module 719, Local Number Portability (LNP) Core Module................6-69
6.4.23 Module 720, Local Number Portability (LNP) Module.........................6-69
6.5 Module Number 164 ..........................................................................................6-69
6.5.1 E.164 Numbering Plan ...........................................................................6-71
6.5.2 X.121 Numbering Plan...........................................................................6-72
6.6 Call Types, Structure Codes, and Modules ........................................................6-72
6.7 Configuration and Operation..............................................................................6-73

ASCII Billing Reports Issue 5, January 9, 2003
6.1 Introduction
The PlexView ASCII Billing Server (ABS) or the Billing and Traffic
System (BTS) convert Call Detail Records (CDRs) to an ASCII record
format. The number of fields supported is determined by the version of
ABS or BTS. For detailed information about ABS and BTS, please refer
to those sections of this manual. This section will only describe the
reports generated by either ABS or BTS.
Note: When importing stored file into an Excel spreadsheet, leading zeros
and tenths of seconds may be truncated.
For a description of the master ASCII record and its fields, refer to section
6.2.2, ASCII Files After Conversion.
6.2 CDR and ABS Formats

The Plexus 9000 sends the CDR data at least every five seconds from the
circular buffer. After delivery to ABS or BTS, the data records are
converted to ASCII and saved into ASCII files.
6.2.1 CDR Data Prior to Conversion

The Plexus 9000 CDRs support the Billing Automatic Message
Accounting Format (BAF) call types and structures, and are based on
Telcordia’s AMA architecture (GR-1100). Currently, the ABS and BTS
applications support the following AMA call types from the switch. These
call types are listed in Table 6-A.
Each CDR is appended with a header that consists of a 4-byte sequence

number and a 2-byte record length. The length field represents the size of
the data and does not include the header size. The Plexus 9000 runs a
process that captures CDRs into memory using a circular buffer that can
be configured to save data.
The ABS or BTS converts the received CDR data into ASCII. The data
field information transferred from the CDR to the ASCII master record is
determined by the call type, the structure code, and the module, if
applicable. For example, call type 110 supports structure code 0625 and
modules 021, 104, 164 and 720. Refer to Table 6-G at the end of this
chapter for a listing of all call types and the structure codes and modules
supported by each.
6-2 Telica, Inc.

Table 6-A. ABS-supported AMA Call Types

Call Type Description
001 Detailed Message Rate, Timed, w/ MBI (MRTD)
002 Message Rate, Timed, w/ MBI (MRT)
003 Detailed Message Rate, Untimed, w/ MBI (MRD)
004 Message Rate, Untimed, w/ MBI. (MR)
006 Station Paid
009 411 Directory Assistance
031 Call Forwarding
033 555 – Directory Assistance
036 Terminating Study Record
047 Default Advanced Intelligent Network (AIN)
067 Originating Study Record
074 Free Call
088 Non-Directory Assistance 555 Call
110 Inter-LATA station paid
119 Terminating Access record
123 CLASS Feature Activation
141 InterExchange Carrier (IC/IXC) Number Service
142 Local Exchange Carrier (LEC) Number Service
159 Message Detail Recording (MDR) Data
264 Calling Identity Delivery Record
330 CLASS Feature
710 Originating Toll AMA Recording (Vendor Specific)
720 Connecting Network Access Incoming Record
721 Default Local Number Portability (LNP)
Therefore, all information in the data fields generated by this call type and
its structure code and modules is transferred to the ASCII master record.
In this example, modules 021, 104, 164 and 720 are supported by the call
type. This does not mean that each module is included in every CDR of
this type. Each module is included in the CDR and sent to the ABS or
BTS, based on certain conditions of the call. For a description of when the
modules and their associated data items are included, refer to Section 6.4,
Module Inclusion Rules.
Telica, Inc. 6-3

6.2.2 ASCII Files After Conversion

ASCII files are saved as comma-delimited ASCII text with a line feed,
which indicates the end of the record. If any field within the master record
has no associated data, the ABS or BTS will still represent the field’s
position with commas. For example, if the master record contained six
fields and two of those fields had no data populated, the record might look
as follows:
6178873341,,002010,,002020,1245
Although the default for saving ASCII files is 24 hours, you can configure
the frequency with which files are saved in minutes.
All converted CDR information is captured in an ASCII master record.

This master record contains the fields listed in Table 6-B. Refer to
Section 6.3, ASCII-Format Master Record Field Descriptions for a
description of each field listed in the ASCII master record.
Table 6-B. List of Fields in the Master Record

GR-1100 Maximum Format
Field Description Table # # of Char. (see Note.)
1 Call Type 1 3 ###
2 Structure Code 0 4 ####
3 Sensor Type 2 3 ###
4 Sensor Identification 3 6 ######
5 Recording Office Type 4 3 ###
6 Recording Office Identification 5 6 ######
7 Connect Date 6 10 MM-DD-YYYY
8 Timing Indicator 7 5 #####
9 Study Indicator 8 7 #######
10 Called Party Off-hook Indicator 9 1 #
Service Observed/Traffic Sampled
11 10 1 #
Indicator
12 Operator Action 11 1 #
13 Service Feature 12 3 ###
14 Originating NPA 13 3 ###
15 Originating Number 14 7 #######
16 Overseas (International Call) Indicator 15 1 #
Terminating (Destination) Number Plan
17 16 5 #####
Area
18 Terminating (Destination) Number 17 7 #######
19 Connect Time 18 10 HH:MM:SS.T
20 Elapsed Time 19 9 #########
21 IC/INC Prefix 5 5 CCCCO
22 Carrier Connect Date 6 10 MM-DD-YYYY
23 Carrier Connect Time 18 10 HH:MM:SS.T
24 Carrier Elapsed Time 19 9 #########
25 IC/INC Call Event Status 58 2 ##
26 Trunk Group Number 83 5 STTTT
27 IC/INC Routing Indicator 59 1 #
6-4 Telica, Inc.


28 Dialing and Pre-subscription Indicator 85 1 #
29 ANI/CPN Indicator 60 1 #
30 Dialed NPA 13 3 ###
31 Dialed Number 14 7 #######
32 Numbering Plan Area 13 3 ###
33 Directory Number 14 7 #######
34 WATS Indicator 28 1 #
35 WATS Band or Message Billing Index 29 3 ###
36 WATS Administration 30 4 ####
37 Completion Indicator 280 3 ###
38 Service Logic Identification 77 9 #########
Revenue Accounting Office (RAO)
39 46 3 ###
Number
40 Local Access Transport Area (LATA) 197 3 ###
41 Data Capabilities Indicator 41 3 ###
42 Information Transfer Rate Indicator 42 3 ###
43 Terminating Company 56 3 ###
44 Usage Count 130 5 #####
45 Module 21 – IC/INC Prefix 57 5 CCCCO
46 Module 21 – Carrier Access Date 6 10 MM-DD-YYYY
47 Module 21 – Carrier Access Time 18 9 HH:MM:SS.T
48 Module 21 – Elapsed Time 19 9 #########
49 Module 21 – IC/INC Call Event Status 58 2 ##
50 Module 21 – Trunk Group Number 83 5 STTTT
51 Module 21 – Routing Indicator 59 1 #
Module 21 – Dialing and Pre-
52 85 1 #
subscription Indicator
53 Module 21 – ANI/CPN Indicator 60 1 #
54 Module 22 – Present Date 6 10 MM-DD-YYYY
55 Module 22 – Present Time 18 10 HH:MM:SS.T
56 Module 25 – Circuit Date 6 10 MM-DD-YYYY
57 Module 25 – Circuit Time 18 10 HH:MM:SS.T
Module 27 – Business Customer ID 87
58 10 ##########
(Reserved) (char. 2-11)
87
59 Module 27 – Context ID (Orig/Term) 1 #
(char. 1)
60 Module 29 – Alternate Billing Number 138 11 N##########
61 Module 40 – Digits Identifier 78 3 ###
62 Module 40 – Digits 32 33 24 ##...##
63 Module 40 – Significant Digits 55 3 ###
Module 104 – Incoming Routing 244
64 1 #
Indicator (char. 1)
Module 104 – Incoming Trunk Group 244
65 4 ####
Number (char. 2-5)
Module 104 – Incoming Trunk Member 244
66 4 ####
Number (char. 6-9)
Module 104 – Outgoing Routing 244
67 1 #
Indicator (char. 1)
Module 104 – Outgoing Trunk Group 244
68 4 ####
Number (char. 2-5)
Module 104 – Outgoing Trunk Member 244
69 4 ####
Number (char. 6-9)
Telica, Inc. 6-5


70 Module 164 – ChN Number Identity 76 1 1 or 4
Module 164 – ChN Number Plan 165
71 1 #
Indicator (char. 1)
Module 164 – ChN Country Code or 165
72 4 ####
Data Network Identification Code (char. 2-5)
73 Module 164 – ChN Significant Digits 55 3 ###
74 Module 164 – Charge Number (ChN) 126 15 ###############
237
75 Module 611 – Significant Digits 2 15
(char. 6-7)
Module 611 – Final Switch, Trunk SSSTTTTTTMMMM
76 126 15
Group Number, Trunk Member Number MM
733
77 Module 720 – Orig Location Type 3 ###
(char 1-3)
78 Module 720 – Orig Party Identifier 730 3 001
Module 720 – Orig Location Routing
79 731 10 ##########
Number (LRN)
Module 720 – Orig Service Provider 732
80 8 ########
Identity
733
81 Module 720 – Orig Location 12 ############
(char 4-15)
Module 720 – Orig Supporting
82 734 7 SQQ0000
Information
83 Module 049 - Count of name only 803 5 #####
84 Module 049 - Count of number only 803 5 #####
85 Module 102 - Authorization Code 126 15 ###############
86 Module 103 - Account Code 126 15 ###############
87
87 Module 105 - MDR Customer Id context 1 #
(char. 1)
87
88 Module 105 - MDR Customer Id 10 ##########
(char. 2-11)
246
89 Module 105 - Originating Fac Type 2 ##
(char. 2-3)
246
90 Module 105 - Terminating Fac Type 2 ##
(char. 4-5)
91 CLASS Feature Code 415 3 ###
92 CLASS Functions 330 3 ###
93 CLASS Feature Status 331 3 ###
94 Deactivation date 6 10 MM-DD-YYYY
95 Deactivation time 18 10 HH:MM:SS.T
96 Call Count - Info Delivered 803 5 #####
Call Count - Info
97 803 5 #####
Anonymous/Unavailable
98 Screening List Size - SCF SCA 802 3 ###
99 Screening List Size – SCR 802 3 ###
100 Screening List Size - DR CW 802 3 ###
101 Module 40_2 - Digits Identifier 78 3 ###
102 Module 40_2 – Digits 32, 33 24 ##...##
103 Module 40_2 - Significant Digits 55 3 ###
105 Module 40_3 - Digits 32, 33 24 ##...##
6-6 Telica, Inc.


108 Module 40_4 - Digits 32,33 24 ##...##
111 Module 40_5 – Digits 32,33 24 ##...##
113 Module 164 – Term Number Identity 76 1 2
Module 164 – Term Number Plan 165
114 1 #
Indicator (char. 1)
Module 164 – Term Country Code or 165
115 4 ####
DNIC (char. 2-5)
116 Module 164 – Term Significant Digits 55 3 ###
117 Module 164 – Term Number 126 15 ###############
118 Module 164 – CPN Number Identity 76 1 3 or 5
Module 164 – CPN Number Plan 165
119 1 #
Indicator (char. 1)
Module 164 – CPN Country Code or 165
120 4 ####
DNIC (char. 2-5)
121 Module 164 – CPN Significant Digits 55 3 ###
Module 164 – Calling Party Number
122 126 15 ###############
(CPN)
123 Module 164 – RN Number Identity 76 1 6
Module 164 – RN Number Plan 165
124 1 #
Indicator (char. 1)
Module 164 – RN Country Code or 165
125 4 ####
DNIC (char. 2-5)
126 Module 164 – RN Significant Digits 55 3 ###
127 Module 164 – Redirecting Number (RN) 126 15 ###############
128 Module 164 – OCN Number Identity 76 1 7
Module 164 – OCN Number Plan 165
129 1 #
Indicator (char. 1)
Module 164 – OCN Country Code or 165
130 4 ####
DNIC (char. 2-5)
131 Module 164 – OCN Significant Digits 55 3 ###
Module 164 – Original Called Number
132 126 15 ###############
(OCN)
133 Module 164 – Billing Number Identity 76 1 8
Module 164 – Billing Number Plan 165
134 1 #
Indicator (char. 1)
Module 164 – Billing Country Code or 165
135 4 ####
DNIC (char. 2-5)
136 Module 164 – Billing Significant Digits 55 3 ###
137 Module 164 – Billing Number 126 15 ###############
138 Module 306 - OLIP 421 3 ###
237
139 Module 612 - Significant Digits 2 30
(char. 6-7)
140 Module 612 – Orig Physical 126 15 TTCCSS0OO331100
141 Module 612 – Term Physical 126 15 TTCCSS0OO331100
733
142 Module 720 – Term Location Type 3 ###
(char 1-3)
143 Module 720 – Term Party Identifier 730 3 002
Module 720 – Term Location Routing
144 731 10 ##########
Number (LRN)
Telica, Inc. 6-7


Module 720 – Term Service Provider
145 732 8 ########
Identity
733
146 Module 720 – Term Location 12 ############
(char 4-15)
Module 720 – Term Supporting
147 734 7 SQQ0000
Information
148 Unused
237
(char. 6-7)
150 Module 611 – Call Id 126 15 00000##########
151 Module 198 – Module Descriptor 575 5 00010
152 Module 198 – Orig SIP Call Id - 32 Variable length
153 Module 198 – Module Descriptor 575 5 00011
154 Module 198 – Term SIP Call Id - 32 Variable length
155 Module 68 – Called DN Description 70 3 ###
155 Module 68 – Called DN Description 70 3 ###
156 Module 101 - Significant Digits 55 3 ###
157 Module 101 - Digits Dialed 32, 33 24 ##…##
158 Module 101 – Access Code 803 5 #####
237
(char. 6-7)
160 Module 611 – Call Sequence Number 126 15 00000##########
569
(char. 3)
Module 616 – Record Sequence
162 803 5 000##
Number
569
(char. 3)
164 Module 616 - Dialed Prefix Indicator 803 5 0000#
569
(char. 3)
166 Module 616 - Called Prefix Digits 803 5 0000#
167 Module 40 – Digits Identifier 78 3 005
168 Module 40 – Outpulse Digits 32, 33 24 ##…##
169 Module 40 – Significant Digits 55 3 ###
569
(char. 3)
Module 616 – Release Originator,
171 803 5 OCRRR
Category, Cause Indicator
172 Module 198 – Module Descriptor 575 5 #####
173 Module 198 – Release Treatment - 10 Variable length
237
(char. 6-7)
Module 611 – Orig Echo Indicator, NLP
175 126 15 000000ENDDDDDDD
Indicator, DSP
237
(char. 6-7)
Module 611 – Term Echo Indicator NLP
177 126 15 000000ENDDDDDDD
Indicator, DSP
237
(char. 6-7)
179 Module 613 – Orig Local IP Address 126 15 000############
6-8 Telica, Inc.


180 Module 613 – Orig Remote IP Address 126 15 000############
Module 613 – Orig Local/Remote Port,
181 126 15 00LLLLLRRRRRCCF
Codec, Fax Indicator
237
(char. 6-7)
183 Module 613 – Term Local IP Address 126 15 000############
184 Module 613 – Term Remote IP Address 126 15 000############
Module 613 – Term Local/Remote Port,
185 126 15 00LLLLLRRRRRCCF
Codec, Fax Indicator
Module 264 – Orig Release Cause
186 411 4 CRRR
Indicator
187 Module 264 – Orig Packets Sent 807 13 #############
188 Module 264 – Orig Packets Received 807 13 #############
189 Module 264 – Orig Packets Lost 807 13 #############
190 Module 264 – Orig Octets Sent 807 13 #############
191 Module 264 – Orig Octets Received 807 13 #############
192 Module 264 – Orig Jitter 802 3 ###
193 Module 264 – Orig Latency 802 3 ###
Module 264 – Term Release Cause
194 411 4 CRRR
Indicator
195 Module 264 – Term Packets Sent 807 13 #############
196 Module 264 – Term Packets Received 807 13 #############
197 Module 264 – Term Packets Lost 807 13 #############
198 Module 264 – Term Octets Sent 807 13 #############
199 Module 264 – Term Octets Received 807 13 #############
200 Module 264 – Term Jitter 802 3 ###
201 Module 264 – Term Latency 802 3 ###
Note: Format characters: #=Numeric, In MM-DD-YYYY - M=Month, D=Day, Y=Year; in
HH:MM:SS.T - H=Hours, M=Minutes, S=Seconds, T=Tenth of sec. For all others, refer to field
descriptions.
6.3 ASCII-Format Master Record Field Descriptions

This section contains a description of all fields making up the ASCII-
format master record. For appended module fields (letters ss –dddd in this
section), specific module inclusion conditions must first be met. Module
inclusion requirements are provided in Section 6.4, Module Inclusion
Rules.
1. Call Type
The Call Type field defines the type of call that occurred. Based on the
type of call, different fields within the master record are populated. Refer
to Section 6.6, Call Types, Structure Codes, and Modules, for a list of the
data fields that can be populated per call types, structure code and
module(s).
Telica, Inc. 6-9

Call types 000 – 799 are administered by Telcordia for uniformity of the
network/accounting interface.
Call types 800 – 999 are not administered by Telcordia. They are reserved
for use by the carrier.
The Call Type field is a maximum of three numeric characters. Table 6-C
identifies the various call types supported by the Plexus 9000. The table
also provides the associated structure codes and modules that are defined
in Telcordia’s GR-1000 specification. If Automatic Message Accounting
(AMA) information is not being used by the associated billing application,
the structure code and module information can be ignored.
2. Structure Code
The Structure Code is a four-character numeric field. Each structure code
points to a set of predefined fields in Section 3 of Telcordia’s GR-1100
documentation. If AMA information is not being used by the associated
billing application, the structure code information can be ignored. The
Plexus supports the AMA structure codes as listed in Table 6-D.
Table 6-C. Call Types Supported by the Plexus 9000

Call Structure
Type Call Type Name Code Module
001 Detailed Message Rate, Timed, w/ MBI 0020 022
002 Message Rate, Timed, w/ MBI. 0020 022
003 Detailed Message Rate, Untimed, w/ MBI. 0020 022
004 Message Rate, Untimed, w/ MBI. 0020 022
006 Station Paid 0001 021, 022, 720
009 411 Directory Assistance 0028 022
031 Call Forwarding 0096, 0614 022
033 555 - Directory Assistance 0028 022
036 Terminating Study Record 0079 022
047 Default Advanced Intelligent Network 0220 021, 022, 025, 027,
(AIN) 029, 040, 104, 164
067 Default Advanced Intelligent Network 0001 021, 022, 720
(AIN)
074 Free Call 0001 022
088 Non-Directory Assistance 555 Call 0001 021, 022, 720
110 Inter-LATA station paid 0625 022, 104, 164
119 Terminating Access record 0625 022, 104, 164
123 CLASS Feature Activation 1030 022
141 InterExchange Carrier (IC/IXC) Number 0360 022
Service
6-10 Telica, Inc.

Call Structure
142 Local Exchange Carrier (LEC) Number 0364 022
Service
159 Message Detail Recording (MDR) Data 0001, 0079, 102, 103, 105
0500
264 Calling Identity Delivery Record 0110
330 CLASS Feature 110, 1030 49
710 Originating Toll AMA Recording (Vendor 0625 022, 104, 164
Specific)
720 Connecting Network Access Incoming 0625 022, 104, 164, 720
Record
721 Default Local Number Portability (LNP) 0500 022, 104, 164, 720
3. Sensor Type
The Sensor Type field identifies the type of switch by a three-character
number assigned by Telcordia. Plexus 9000 is Sensor Type = 195. If
AMA information is not being used by the associated billing application,
the Sensor Type information can be ignored.
Table 6-D. Structure Codes
Structure Code List Call Types
0001 006, 067, 074, 088
0020 001, 002, 003, 004
0028 009, 033
0079 036
0110 264, 330
0220 047, 159
0360 141
0364 142
0500 721
0625 110, 119, 710, 720
1030 123, 330
4. Sensor Identification
The Sensor Identification field is a six-character numeric field. Characters
1-6 specify a six-digit sensor identification code. This code identifies the
sensor that generated or formatted the BAF record that contains the code.
Telica, Inc. 6-11

The sensor identification code is specified by a carrier and is assigned by a

carrier through translation procedures, except for code “999999”. The
“999999” code indicates the sensor is a vendor’s working model of a
switching system that generates AMA test tapes. All records on an AMA
test tape have this sensor identification code.
If AMA information is not being used by the associated billing

application, the Sensor Identification code information can be ignored.
5. Recording Office Type

The Recording Office Type is a three-digit numeric code. The code
identifies the type of office that writes the BAF data to a physical medium
on which it will be transported to a Revenue Accounting Office (RAO) for
processing. The recording office type code may be different from the
sensor type code identified in the Sensor Type field.
The term “recording office” refers to the first system or device that
captures a BAF record on an archival medium that is intended for
transport of the record to, or storage of the record within, an RAO.
The Plexus 9000’s recording office type = 195.

application, the Recording Office Type information can be ignored.
6. Recording Office Identification

The Recording Office Identification field is a six-character numeric field.
Characters 1-6 specify a six-digit recording office identification code.
This code identifies the recording office that first created an archival
image of the BAF record that contains the code. The recording office
identification code is specified by a Carrier and is assigned by a Carrier
through translation procedures, except for “999999”. The “999999” code
indicates the sensor is a vendor’s working model of a switching system
that generates AMA test tapes. All records on an AMA test tape have this
recording office identification code.

application, the Recording Office Identification information can be
ignored.
7. Connect Date
The Connect Date indicates the date that Plexus received answer
supervision indicating a completed call. The ten-character field represents
the month, day, and year as follows:
MM-DD-YYYY.
6-12 Telica, Inc.

8. Timing Indicator
The Timing Indicator is a five-digit numeric field. Valid values are:
Chars Meaning
digit 1 Timing Guard Flag
0 = Default value
1 = Time Release Disconnect
4 = Unanswered Call Release – Answer Timer Expiry
6 = The call is forcibly released.
digit 2 Short Called Party Off-Hook Indicator
0 = Default value
1 = Short called party off-hook detected
2 = Under minimum chargeable (UMCD)
3 = SST&UMCD (At disconnect with SST)
4 = SST (Not at disconnect, No SST)
digit 3 Long Duration/Service Party Capability Indicator
0 = Default value
1 = Start of long duration call (for service capability status:
Activation)
2 = Continuation of long duration call
3 = Service capability status: Deactivation
digit 4 Charge Guard Indicator
0 = Default value
1 = Charge guard (conversation elapsed time)
2 = Message Register Not Stroked or trunk not seized
3 = Charge guard and Mess Reg. Not Stroked
4 = Charge guard (elapsed time from carrier connect)
5 = Charge guard (elapsed time and elapsed time from
carrier connect)
digit 5 Time Stamp Error Indicator
0 = Default value
1 = Possible Time Stamp Error (conversation connect)
2 = Possible time stamp error (carrier connect)
3 = Possible time stamp error (carrier and carrier connect)
4 = Time Change Rating Discrepancy
Telica, Inc. 6-13

9. Study Indicator
Study Indicator is a seven-character numeric field. This field is used in
conjunction with billing studies.
Chars Meaning
digit 1 Study Type A
0 = Default value
1 = Point To Point
2 = Subscriber Line Usage Study (SLUS)
3 = Point-to-Point and SLUS (Operator Services Position
System [OSPS] value)
4-9 = Study Dependent (OSPS value)
digit 2 Study Type B
0 = Default value
1 = Complaint observed
2 = Network completion
3 = Complaint observed and network completion
digit 3 --------
0 = Default value
1 = Validation test
2 = Study generated record
3 = Validation test and study generated record
4-9 = Study dependent (OSPS value)
digit 4 Test Call Indicator
0 = Default value
1 = Test call
2 = Network Specific Facility (NSF)
3 = NSF and Test Call
digit 5 LEC-settable
0 = Default value
2 = Called directory number not marked anonymous
3 = Called directory number marked anonymous
4 = Calling Party Marked Anonymous, Called Party
Marked Not Anonymous
5 = Calling and Called Party Marked Anonymous
digit 6 Originating and Terminating Number Indicator

0 = Default value
1 = No originating number
3 = No terminating number
4 = No originating and terminating numbers
5 = No terminating North American Number Plan (NANP)
station number
6-14 Telica, Inc.

6 = No originating NANP station number

7 = No originating and terminating NANP station numbers
8-9 = Study dependent
digit 7 Operator Services System Indicator
0 = Default value
2 = No Automatic Message Accounting (AMA) call
(Operator Services System)
3 = Holding Time Study
4 = Expanded 4 digits
7 = Corrected 7 digits
8 = Corrected undetermined number of digits
9 = More than 7 digits seen. No correction
10. Called Party Off-hook Indicator

Called Party Off-hook Indicator is a one-character numeric field. Value 0
indicates called party off-hook is detected on the call, regardless of the
duration of the called party off-hook interval. Valid values:
0 = Called party off-hook detected
1 = Called party off-hook not detected
9 = Unknown
11. Service Observed/Traffic Sampled Indicator

The Service Observed/Traffic Sampled Indicator is a one-character
numeric field. Service observing and/or traffic sampling is applied to a
call if a Carrier activates this feature in the Plexus. Currently, only Local
Number Portability (LNP) and 800 Service calls activate this indicator.
Valid values:
0 = Default value
1 = Service observed
2 = Traffic sampled
3 = Service observed and traffic sampled
4 = Not Service Observed, Not Traffic Sampled, message detailed
recorded
5 = Service Observed, Not Traffic Sampled, message detail
recorded
6 = Not Service Observed, Traffic Sampled, Message Detail
Recorded (MDR)
7 = Service observed, traffic sampled, message detail recorded
Telica, Inc. 6-15

12. Operator Action

The Operator Action Indicator is a one-character numeric field. This field
indicates whether the operator identifies the originating number and
whether the operator dials the number. For example, value “0” indicates
the call is identified automatically and is customer dialed. Valid values:
0 = Automatically identified, customer-dialed call
1 = Automatically identified, operator-dialed call involving an
Operator Services System
2 = Operator-identified, customer-dialed call
3 = Operator- identified, operator-dialed call involving an Operator
Services System
4 = Customer Dialed, Number Identification Failure (Billing Data
Transmitter [BDT])
5 = Operator Dialed, Number Identification Failure (Billing Data
Transmitter [BDT])
6 = Customer Dialed, Identification failure Automatic Number
Identification (ANI) (Billing Data Transmitter [BDT])
7 = Operator Dialed, Identification Failure Automatic Number
Identification (ANI) (Billing Data Transmitter [BDT])
13. Service Feature

The Service Feature is a three-digit numeric field. It indicates a service
used during the call. The Plexus 9000 supports the following service
values:
001 = Local Exchange Carrier (LEC)-owned standard interface
public line
010 = Three-Way Calling
012 = Call Forwarding
014 = Call Forwarding Busy Line or Call Forwarding Don’t
Answer
14. Originating NPA

This Originating NPA is a three-digit numeric field that identifies the
Numbering Plan Area. This field is coordinated with the use of the
Originating Number field.
15. Originating Number

The Originating Number is a seven-character numeric field. The first
three characters represent the NXX and the last four characters (XXXX)
represent the station number.
6-16 Telica, Inc.

The following paragraphs describe requirements for populating the

originating number. This field is coordinated with the use of the
Originating Numbering Plan Area (NPA) field above.
When the NPA, NXX, and station number of the originating line are
available, the system does the following:
Populates the NPA in characters 1-3 of the Originating NPA field.
Populates the NXX in characters 1-3 of the Originating Number
field.
Populates the station number in characters 4-7 of the Originating
Number field.
When only the NPA and the three digits corresponding to the NXX of the
originating number are available for a call (e.g., a call requiring Operator
Number Identification), the system does the following:
Populates the NPA in characters 1-3 of the Originating NPA field.
Populates the NXX in characters 1-3 of the Originating Number
field.
Populates “0000” in characters 4-7 of the Originating Number
field.
Flags that the originating station number is not known or applicable to the
call by setting character 6 of the Study Indicator field to “6”.
When the originating number is not available and no error condition

exists, the system does the following:
Populates “0” in each of the character positions (excluding the sign
character) of the Originating NPA field. For a particular toll-free
service call scenario, the NPA may be available, but the originating
number may not (see TR-NWT-000533). In this case, the NPA
populates the Originating NPA field.
Populates “0” in each of the character positions (excluding the sign
character) of the Originating Number field.
Flags that the originating number is not available (and no errors
exist) by setting character 6 of the Study Indicator field to “1”.
When the originating number to be recorded in the originating number

fields exceeds 10 digits, it should populate Module 164. A description of
Module 164 is described in section 7, Module Number 164.
Telica, Inc. 6-17

The Originating Number field together with the Originating NPA field
may be populated with a billing number. Billing numbers are LEC-
assigned and may or may not be consistent with the North American
Numbering Plan (NANP). Non-NANP billing numbers may vary from 1
to 10 digits. The Originating NPA and Number fields are treated as one
concatenated field and the non-NANP billing number populates this
concatenated field right justified and padded with zeros as necessary.
16. Overseas (International Call) Indicator

The Overseas (International Call) Indicator is used with the Terminating
NPA and Terminating Number fields. The Terminating number is the
number the switch uses to route a call. The following list contains the
valid values:
0 = Numbering Plan Area (NPA) dialed by the customer or
provided by another network element (non-international call)
1 = NPA determined by the network element (non-international
call)
2 = Non-North American Numbering Plan (NANP) terminating
number (non-international)
3 = 7-digit international number
8 = 12-digit (or greater) international number
17. Terminating (Destination) Number Plan Area

The Terminating NPA is a five-character numeric field. The Terminating
NPA and Terminating Number are used to route the call. These numbers
are not necessarily the dialed numbers.
Chars Meaning
digits 1-2 International Expander Positions
digits 3-5 Numbering Plan Area
18. Terminating (Destination) Number

The Terminating Number is a seven-character numeric field that
represents the NXX and the station number (XXXX) that is being called.
Chars Meaning
1-3 NXX
4-7 Station Number
6-18 Telica, Inc.

19. Connect Time

The Connect Time is a ten-character field. It provides the hour, minute,
seconds, and tenth of second to indicate the time of day of the called party
going off-hook. The format of this field is HH:MM:SS.T where H=hours,
M= minutes, S = seconds, and T = tenth of seconds.
20. Elapsed Time

The Elapsed Time is a nine-character numeric field. The Elapsed Time
provides a count in tenth of seconds from when the call went off-hook to
the end of the call.
21. IC/INC Prefix

The Inter-exchange Carrier/International Carrier Identification (IC/INC)
Prefix is a five-character numeric field in the format of “CCCCO”. This
field in an Automatic Message Accounting (AMA) record identifies the
IC/INC that transports the call. The Carrier Identification Code (CIC) in
this field represents either a domestic IC or an INC. If a domestic carrier
delivers the call to an INC, the INC’s code is recorded.
Characters 1-4 represent the IC/INC Identification - Characters 1-4

(CCCC) contain the four-digit CIC. These characters are zero when
the CIC is “0000” or when the switch has no valid CIC to populate
these characters.
Character 5 (O) represent an Operator Involvement and can have the

following values:
0 = The Carrier Identification Code (CIC) is a Feature Group D
(FGD) identity, and an IC/INC operator system is involved.
1 = The CIC is an FGD identity, the call is dialed direct, and no
IC/INC operator system is involved.
2 = The CIC is an FGD identity, and IC/INC operator system
involvement cannot be determined.
7 = The CIC is unknown, and an IC/INC operator system is
involved
8 = The CIC is unknown, the call is dialed direct, and no
IC/INC operator system is involved.
9 = The CIC is unknown, and IC/INC operator system
involvement cannot be determined.
22. Carrier Connect Date

The Carrier Connect Date indicates the date that Plexus received the Initial
Address Message (IAM) from the signaling network. The ten-character
field represents the month, day, and year as follows: MM-DD-YYYY.
Telica, Inc. 6-19

23. Carrier Connect Time

The Carrier Connect Time is a ten-character field. It provides the hour,
minute, seconds, and tenth of second to indicate the time of day that the
switch received the Initial Address Message (IAM). The format of this
field is HH:MM:SS.T where H=hours, M= minutes, S = seconds, and
T = tenth of seconds.
24. Carrier Elapsed Time

The Carrier Elapsed Time is a nine-character numeric field. The Elapsed
Time provides a count in tenth of seconds that indicates the duration time
from the carrier connect time until a Release Message (REL) is received or
sent by the originating network.
25. IC/INC Call Event Status

The IC/INC Call Event Status is a maximum of two digits with leading
zeros suppressed. This field provides information about events occurring
in calls involving ICs or INCs. The information describes how far a call
progressed before terminating and identifies the conditions associated with
the call’s termination. The following describes the values and their
meaning:
Broadband Integrated Services Digital Network User Part (BISUP) calls
Originating Carrier Network

− “00”indicates the Switched Virtual Connection (SVC) is
cleared before the BISUP IAM is sent from the Originating
Broadband Switching System.
− “01” indicates the BISUP IAM is sent.
− “02” indicates the BISUP IAM Acknowledge (IAA) is
received.
− “03” indicates the BISUP IAM Reject (IAR) is received.
− “04” indicates the BISUP Exit Message (EXM) is received
(when referring to the originating BSS) or “04” indicates the
BISUP EXM is sent (when referring to the intermediate BSS).
− “07” indicates the BISUP Address Complete Message (ACM)
is received.
− “10” indicates the BISUP Answer Message (ANM) is received.
Terminating Carrier Network

− “01” indicates the BISUP IAM is received.
− “10” indicates the BISUP ANM or DSS2 CONNECT is
received.
6-20 Telica, Inc.

Cellular Mobile Carrier (CMC) Calls

− "00" indicates a wink is not received.
− "01" indicates a wink is received.
− "10" indicates a Called Party Off-Hook indication is received.

− "01" indicates trunk is seized.
− "05" indicates Operator Services Signaling (Type 1 only).
− "06" indicates call terminated due to network management.
− "08" indicates invalid called NXX.
− "09" indicates all other failures in which the call cannot be
completed to the terminating office.
− "10" indicates a Called Party Off-Hook indication is received.
Multifrequency (MF) Calls
− "00" indicates the call is abandoned or released before receipt

of the carrier connect wink by the originating Exchange
Carrier’s (EC’s) End Office (EO) for an originating exchange
access call, and before trunk seizure at the terminating EC’s
EO for a terminating exchange access call.
− "01" indicates the carrier connect wink is received from the
carrier by the originating EC’s EO for originating exchange
access records, and that trunk seizure occurred at the
terminating EC’s EO.
− "02" indicates the customer abandons the call before
completing the dialing. This value only applies to originating
exchange access calls.
− "03" indicates the call failed or is abandoned after the second
start dial wink is received from trunks utilizing INC signaling.
− "04" indicates a timeout occurred waiting for an
acknowledgment wink. It may also indicate that an off-hook
indication instead of an acknowledgment wink is received from
the IC/INC.
− "05" indicates disconnect occurred after the originating EC’s
EO received the IC/INC off-hook. For operator services or
CAMA signaling, this value applies after the called number is
transmitted and an ANI request off-hook signal is received
from the IC/INC.
− "06" (terminating access only) indicates the call disconnects in
the terminating network due to a network management
procedure. This occurs before called party off-hook but after
terminating trunk seizure.
Telica, Inc. 6-21

− "07" indicates the call is abandoned or failed after an

acknowledgment wink is received from the IC/INC by the
originating EC’s EO. This only occurs in the originating
network.
− "08" (terminating access only) indicates the terminating end of
the call either did not recognize the called NXX or that the
NXX received is not valid in the terminating network
− "09" (terminating access only) indicates the call cannot be set
up to the terminating office in the terminating network. This
value is used to cover all failures at the terminating end except
those failures indicated by values "06" and "08".
− "10" indicates the receipt of called party off-hook in the
originating network and the occurrence of called party off-hook
in the terminating network.
− "11" indicates timeout occurred waiting for the receipt of the
second start dial wink from the carrier for calls utilizing INC
signaling. This only occurs in the originating network.
− "12" indicates timeout occurred waiting for an off-hook ANI
request signal from the IC/INC, after the called number was
transmitted in calls utilizing operator services or CAMA
signaling. This only occurs in the originating network.
− "13" indicates an off-hook rather than a second start dial wink
is received by the EC’s EO for calls utilizing INC signaling.
This only occurs in the originating network.
Signaling System 7 (SS7) Calls (direct connections and/or connections via

an AT)
Calls connected directly to IC

− “00” indicates the call is abandoned or released before the IAM
is sent by the originating EC’s EO.
− “01” indicates the call is abandoned or released after the IAM
is sent by the originating EC’s EO.
− “06” (terminating access only) indicates the call disconnects in
the IAM is received.
− “07” indicates the call is abandoned or released after the ACM
is received by the originating EC’s EO.
− “08” (terminating access only) indicates the terminating end of
NXX received is not valid in the terminating network.
− “09” (terminating access only) indicates the call cannot be set
up to the terminating office in the terminating network.
− “10” indicates the call is abandoned or released after the ANM
6-22 Telica, Inc.

Calls Connected to an IC via an AT

− “00” indicates the call is abandoned or released before the IAM
is sent by the originating EC’s EO or before the EXM is
received by the originating EC’s EO from the EC’s AT.
− “01” indicates the call is abandoned or released after the EXM
is received by the originating EC’s EO from the EC’s AT.
− “04” indicates a timeout occurs after the EXM is received by
the originating EC’s EO from the EC’s AT.
− “06” (terminating access only) indicates the call disconnects in
the IAM is received
− “07” indicates the call is abandoned or released after the ACM
− “08” (terminating access only) indicates the terminating end of
NXX received is not valid in the terminating network.
− “09” (terminating access only) indicates the call cannot be set
up to the terminating office in the terminating network.
− “10” indicates the call is abandoned or released after the ANM
Interim Interswitch Signaling Protocol (IISP) Calls

− "00" indicates the Switched Virtual Connection (SVC) is
cleared before the IISP SETUP message is sent from the
Originating Broadband Switching System (BSS).
− "01" indicates the IISP SETUP message is sent.
− "02" indicates the IISP CALL PROCEEDING (CALL PROC)
message is received.
− "07" indicates the IISP ALERT message is received..
− "10" indicates the IISP CONNECT (CONN) message is
received.
− "14" indicates a CONNECTION ACKNOWLEDGE (CONN
ACK) message is sent.

− "01" indicates the IISP SETUP message is received.
− "10" indicates the IISP CONNECT (CONN) or DSS2
CONNECT is received.
− "14" indicates a CONNECTION ACKNOWLEDGE (CONN
ACK) message is sent.
Telica, Inc. 6-23

Private Network-Network Interface (PNNI) Calls

cleared before the PNNI SETUP message is sent from the
Originating Broadband Switching System (BSS).
− "01" indicates the PNNI SETUP message is sent.
− "02" indicates the PNNI CALL PROCEEDING (CALL
PROC) message is received.
− "07" indicates the PNNI ALERT message is received.
− "10" indicates the PNNI CONNECT (CONN) message is
received.
− "14" indicates a PNNI CONNECTION ACKNOWLEDGE
(CONN ACK) message is sent.

− "10" indicates the PNNI CONNECT (CONN) message is
received.
ATM Inter-Network Interface (AINI) Calls

cleared before the AINI SETUP message is sent by the
Broadband Switching System (BSS).
− "01" indicates the AINI SETUP is sent by the BSS.
− "02" indicates the AINI CALL PROC message was received
by the BSS..
− "07" indicates the AINI ALERT message was received by the
BSS.
− "10" indicates the AINI CONNECT message was received by
the BSS.

− -"01" indicates the AINI SETUP message is received.
26. Trunk Group Number

The Trunk Group Number is a five-character numeric field in the format
of “STTTT.” This field provides the outgoing Trunk Group Number
(TGN) for originating calls and the incoming TGN for terminating calls.
6-24 Telica, Inc.

Character 1 (S) = Trunk Group Signaling Type Indicator as

follows:
1 = Non-Signaling System 7 (SS7) direct trunk group
number
2 = Non-SS7 from Interexchange Carrier (IC) to Access
Tandem (AT) and non-SS7 from AT to End Office
(EO)
3 = SS7 direct trunk group number
4 = SS7 from IC to AT and SS7 from AT to EO
5 = Non-SS7 from IC to AT and SS7 from AT to EO
6 = SS7 from IC to AT and non-SS7 from AT to EO
(terminating only)
9 = Signaling type not specified
Characters 2-5 (TTTT) = Trunk Group Number
27. IC/INC Routing Indicator

The IC/INC Routing Indicator is a one-character numeric field. This field
indicates whether direct or tandem routing was used to deliver traffic to an
IC/INC from the end office or from an IC/INC to an end office. Valid
values for this indicator are:
0 = Direct
1 = Tandem
2 = Competitive Access Provider (CAP) direct from end office
3 = CAP direct from Access Provider (AP) tandem
4 = Tandem signaling to Tandem Switch Provider (TSP) - CAP
trunks
5 = Tandem from another Local Exchange Carrier’s (LEC's) end
office (LEC to LEC Interconnection)
The conditions for recording values for originating calls are as follows:
“0” indicates the call is routed to the IC/INC directly from the
originating Equal Access End Office (EAEO).
“1” indicates the call is routed to the IC/INC via an Access
Tandem (AT) from the originating EAEO.
The conditions for recording values for terminating calls are as follows:
“0” indicates the call is routed from the IC/INC directly to the
terminating EAEO.
“1” indicates the call is routed from the IC/INC via an AT to the
terminating EAEO.
Telica, Inc. 6-25

28. Dialing and Presubscription Indicator

The Dialing and Presubscription Indicator is a one-character field. This
field indicates three things to an accounting office. The first is whether
the end user dialed a Carrier Access Code (CAC) to select a particular
IC/INC for the call. The second is whether the station being used is
presubscribed to the IC/INC to the IC/INC transporting the call. The third
is whether the IC/INC involved in the call has a service arrangement with
the Local Exchange Carrier (LEC) to receive a special Key Pulse (KP)
signal that indicates whether the station is presubscribed to the IC/INC.
The CAC is the dialing pattern used by the customer to access a particular
IC/INC. The dialing pattern of the CAC is currently 101XXXX or
10XXX (permissive to year 2001) for Feature Group D (FGD) and
950-XXXX for Feature Group B (FGB). (Telica currently does not
support FGB).
Within the CAC, the Xs, which range from 0-9, represent a Carrier
Identification Code (CIC). The CIC is placed into the IC/INC Identity
Code field. The CIC identifies the IC/INC that was selected by the
customer for the call.
The CAC is dialed by the customer only to access a particular IC/INC.

Feature Group D (FGD) customers need not dial this code to access a
presubscribed IC/INC. However, the CAC may have to be dialed on intra-
network and cut-through calls.
For FGD, the CAC alone may not be enough to properly route a call.
Other network access digits, such as 1+ or 0+, may have to be dialed after
the CAC to access various switching network functions.
Value “0” applies when recording occurs at a tandem, and when the dialed
digits are not known. Values “1”, “2”, and “4 – 9” are associated with
FGD service while value “3” is associated with FGB service.
The following describes each valid value for the Dialing and
Presubscription Indicator:
0 = Dialed digits cannot be determined (No indication CAC dialed:
presubscription status cannot be determined: no presubscription
indication forwarded to IC/INC
1 = Carrier Access Code (CAC) not dialed, customer
presubscribed, not presubscription indication arrangement with
IC/INC
2 = CAC dialed, customer not presubscribed, no presubscription
indication arrangement with IC/INC
3 = 950-XXXX dialed
6-26 Telica, Inc.

4 = CAC not dialed, customer presubscribed, presubscription

5 = CAC dialed, customer not presubscribed, presubscription
indication arrangement with IC/INC. (Customer “not
presubscribed” indication provided to IC/INC.)
6 = CAC dialed, customer presubscribed, presubscription
7 = CAC dialed, customer presubscribed, no presubscritpion
8 = No CAC dialed; station not presubscribed; no presubscription
9 = No indication CAC dialed; station presubscribed;
presubscription indication forwarded to IC/INC
29. ANI/CPN Indicator

The ANI Calling Party Number (CPN) Indicator is a one-character field.
This field indicates whether ANI and/or the CPN are provided for the call.
Only ANI is provided in non- SS7 calls. Both ANI and CPN may be
provided in SS7 calls. Valid values for this field are:
0 = Neither ANI nor CPN provided
1 = ANI provided
2 = CPN provided
3 = Both ANI and CPN provided
30. Dialed NPA

The Dialed NPA field is a three-character field. This field is the dialed
NPA.
31. Dialed Number

The Dialed Number is a seven-character field represented as NXX-
XXXX.
32. Numbering Plan Area

The NPA field is a three-character field. This field represents the
originating NPA and it is only used with a billing study record.
33. Directory Number

The Directory Number is a seven-character field represented as NXX-
XXXX. This field represents the originating number and it is only used
with a billing study record.
Telica, Inc. 6-27

34. WATS Indicator

The WATS Indicator is a one-character field. This field indicates
measured time Wide Area Telecommunications Service (WATS) when its
value is “2”. Valid values for this field are:
0 = Default
2 = Measured Time
35. WATS Band or Message Billing Index

The WATS band or Message Billing Index (MBI) is a three-character
field. This field is populated with the Wide Area Telecommunications
Service (WATS) band or MBI, which are mutually exclusive. The WATS
band identifies the geographical area to which a WATS customer makes
calls via dedicated access lines. The MBI indicates the specific local
measured service provided for the call to the Revenue Accounting Office
(RAO).
For WATS calls (Call Type Code 007, and 068), Characters 1-3 make up
the WATS band. For message rate calls (Call Type Code 001 through
004), Characters 1-3 make up the MBI, which ranges from 000-999.
It is a carrier’s responsibility to set the translation-settable MBI codes in

the Plexus.
36. WATS Administration

The WATS Administration field is four characters. The first character is a
constant 0 and the other four characters contain the pseudo-trunk number
for WATS lines that use simulated facilities. Use of the pseudo-trunk
number is intended to enable customers to engineer their WATS better.
The pseudo-trunk number may range from 0000-9999.
37. Completion Indicator

The Completion Indicator is a three-character field. This field contains the
status of a call. The following codes indicate the supported statuses:
001 = Completed: Connected - Indicates the call is successfully
completed (i.e., conversation between calling and called
parties occurs). Each of the other values in this field is
recorded as appropriate for calls that do not complete.
002 = Not completed: Billing failure
003 = Not completed: Setup Restrictions Table
004 = Not completed: Person requested on person-to-person call
not available
005 = Not completed: No circuits. Indicates all circuits are in use
and the call cannot be completed.
6-28 Telica, Inc.

006 = Not completed:Indicates the called party does not go off-

hook.
007 = Not completed: Busy. Indicates the called line is busy.
007 = Not completed: Busy
008 = Not completed: No answer supervision returned
009 = Advanced Intelligent Network (AIN) pre-final route record –
final call disposition completed
010 = AIN pre-final route record - disposition not completed
011 = AIN Service Control Point (SCP)-requested release time
(disconnect message received)
012 = Not completed: Network Failure
013 = Not completed: Caller Aborted
014 = AIN pre-final route - NEL follows - "Limited
Implementation"*
015 = Not completed: Call sent to treatment
018 = Release To Pivot (RTP) Operator Services System (OSS)
Redirected
031 = Answered with Charge (per R2/Telephone User Part (TUP)
signaling) (Vendor Specific)
035 = Answered without Charge (per R2/TUP signaling) (Vendor
Specific)
040 = Service Control Point (SCP) initiated Vertical Service Code
– call disposition not provided
060 = Record closed because subsequent non-Specific Digits
String (SDS) record exists and has call elapsed time (if any)
999 = Unknown
38. Service Logic Identification

The Service Logic Identification is a nine-character field. This field is
used in an AIN environment. It records an identification of the service
logic in the SCP that was used.
000000000 - 899999999 = Local Exchange Carrier (LEC)-
assignable
900000000 = Advanced Intelligent Network (AIN) default routing
invoked
999999999 = Unknown
39. Revenue Accounting Office (RAO) Number

The RAO is a three-character field that is populated with a three-digit
ROA number 000-999. This number identifies the RAO that services the
account identified by the billing number located elsewhere in the record.
Telcordia assigns the RAO numbers.
Telica, Inc. 6-29

One example for the use of this field is as follows:

- The RAO number is returned from the Line Information
Database (LIDB) or billing validation database for queries that
return an “Accepted”, “Verify” or “PIN Match” response.
40. Local Access Transport Area (LATA)

The LATA is a three-character field. This field indicates the numerical
identifier of a Local Access and Transport Area (LATA).
41. Data Capabilities Indicator

The Data Capabilities Indicator is a three-character field that uses
three-digit code to specify data capabilities. Values are:
000 = Unknown - Indicates the switch cannot determine whether
the call is a data-only Public Switched Digital Service
(PSDS) call or an alternate voice/data PSDS call.
003 = Data only
008 = Alternate voice/data
009 = Unidirectional data transfer
010 = Bidirectional data transfer
42. Information Transfer Rate Indicator

The Information Transfer Rate Indicator is a three-character field. This
field indicates the information transfer rate of a call.
000 = Unknown transfer rate
001 = 1536 kilobits/second (kbps) clear
002 = 1536 kbps restricted
003 = 384 kbps clear
005 = 64 kbps clear
008 = 56 kbps
6-30 Telica, Inc.


43. Terminating Company

The Terminating Company is a three-character field. This field indicates
whether the terminating company involved in the call is a LEC or an
independent company, and whether the call is interstate or intrastate.
Terminating company values are:

000 = Not used
001 = Company unknown, interstate
002 = Company unknown, intrastate
011 = LEC, interstate
012 = LEC, intrastate
021 = Independent, interstate
022 = Independent, intrastate
44. Usage Count

The Usage Count is a five-digit numeric field. This field indicates the
number of times an event occurs. This field is used for capturing billing
study information.
45. Module 21 – IC/INC Prefix

The Inter-exchange Carrier/International Carrier Identification (IC/INC)
Prefix is a five-character numeric field in the format of “CCCCO.”
- Characters 1-4 (CCCC) represent the IC/INC Identification
- Character 5 (O) represents an Operator Involvement Indicator.
Refer to Field 21 for values and descriptions.
This field in an AMA record identifies the IC/INC that transports the call.
The CIC in this field represents either a domestic IC or an INC. If a
domestic carrier delivers the call to an INC, the INC’s code is recorded.
46. Module 021 – Carrier Access Date

The Carrier Access Date indicates the date that Plexus received the IAM
from the signaling network. The ten-character field represents the month,
day, and year as follows: MM-DD-YYYY.
Telica, Inc. 6-31

47. Module 021 – Carrier Access Time

The Carrier Connect Time is a ten-character field. It provides the hour,
minute, seconds, and tenth of second to indicate the time of day that the
switch received the IAM. The format of this field is HH:MM:SS.T where
H=hours, M= minutes, S = seconds, and T = tenth of seconds.
48. Module 021 – Carrier Elapsed Time

The Carrier Elapsed Time is a nine-character numeric field. The Elapsed
Time provides a count in tenth of seconds from when the switch received
the IAM from signaling network.
49. Module 021 – IC/INC Call Event Status

The IC/INC Call Event Status is a maximum of two digits. This field
provides information about events occurring in calls involving ICs or
INCs. The information describes how far a call progressed before
terminating and identifies the conditions associated with the call’s
termination. Refer to Field 25 for description of values and their meaning.
50. Module 021 – Trunk Group Number

The Trunk Group Number is a five-character numeric field in the format
of “STTTT.” This field provides the outgoing Trunk Group Number
(TGN) for originating calls and the incoming TGN for terminating calls.
Refer to Field 26 for description of values and their meaning.
51. Module 021 – Routing Indicator

The IC/INC Routing Indicator is a one-character numeric field. This field
indicates whether direct or tandem routing was used to deliver traffic to an
IC/INC from the end office or from an IC/INC to an end office. Refer to
Field 27 for description of values and their meaning.
52. Module 021 – Dialing and Presubscription Indicator

The Dialing and Presubscription Indicator is a one-character field. Refer
to Field 28 for description of values and their meaning.
6-32 Telica, Inc.

53. Module 021 – ANI/CPN Indicator

The ANI/CPN Indicator is a one-character field. This field indicates
whether ANI and/or the CPN are provided for the call. Only ANI is
provided in non-SS7 calls. Both ANI and CPN may be provided in SS7
calls. Valid values for this field are:
0 = Neither ANI nor CPN provided
1 = ANI provided
2 = CPN provided
3 = Both ANI and CPN provided
54. Module 022 – Present Date

The Present Date indicates the date the record was formed for a long
duration call. The ten-character field represents the month, day, and year
as follows: MM-DD-YYYY.
55. Module 022 – Present Time

The Present Time is a ten-character field. It provides the hour, minute,
seconds, and tenth of second to indicate the time the record was formed
for a long duration call. The format of this field is HH:MM:SS.T where
H=hours, M= minutes, S = seconds, and T = tenth of seconds.
56. Module 025 – Circuit Date

The Circuit Date indicates the date that Plexus received answer
supervision indicating a completed call. The ten-character field represents
the month, day, and year as follows: MM-DD-YYYY.
57. Module 025 – Circuit Time

The Circuit Time is a ten-character field. It provides the hour, minute,
seconds, and tenth of second to indicate the time of day of the called party
going off-hook. The format of this field is HH:MM:SS.T where H=hours,
M= minutes, S = seconds, and T = tenth of seconds.
58. Module 027 – Business Customer ID

The Business Customer ID is a ten-character field that contains the
customer identification number. This number uniquely identifies records
for a single customer or for customers who are members of a customer
group. The information in this field is populated by the data returned from
a SCP query.
Telica, Inc. 6-33

59. Module 027 – Context ID (Orig/Term)

The Context ID is a one-character numeric field that provides the context
of the Business Customer ID above. Valid values for the Context ID are:
0 = Default
1 = Originating customer’s ID
2 = Terminating customer’s ID
3 = Originating and terminating customer’s ID
60. Module 029 – Alternate Billing Number

The Alternate Billing Number (ABN) is an eleven-digit numeric field.
The first character is the Network Element Indicator and the values are:
0 = Zero constant
1 = Service Control Point (SCP)-based Alternate Billing Number
2 = Switch-based Alternate Billing Number
The other digits provide the ABN when the ABN option is used. For
originating calls, this option is provisioned on a per subscriber basis. For
terminating calls, the ABN is provided in the IAM of the SS7 protocol.
Currently Module 029 is not supported.
61. Module 040 – Digits Identifier

The Digits Identifier field is a three-digit numeric field. This field
identifies the type of information represented by the digits recorded in the
Digits 1 field for an Advanced Intelligent Network (AIN) call. The Digits
1 field that follows can record up to 24 numbers
Valid values for the Digits Identifier field are:

001 = Authorization code
002 = Account code
003 = Access code
004 = Digits dialed
005 = Outpulse number
006 = International calling party identification
011 = Non-international calling party ID greater than 12 digits
012 = Incoming terminating number greater than 12 digits
300-998 = LEC-assigned
999 = Unknown
6-34 Telica, Inc.

62. Module 040 – Digits

The Digits field contains 24-numeric characters. This field includes the
Digits 1 and Digits 2 field defined in the AMA definition of module 40.
The field captures the dialed digits. If there are unused digits in either
field, the most significant digits are right justified and the unused digits
are filled with “0s”.
63. Module 040 – Significant Digits

The Significant Digits field identifies the number of significant digits
associated with the Digits 1 field.
64. Module 104 – Incoming Routing Indicator

The Incoming Routing Indicator is a one-character numeric field. The
field describes how the traffic is generally routed over the identified trunk
group in Local Service Provider Identification (LSPI)-recording scenarios.
Valid values for this field are:

1 = Direct – Incoming different network [Local Service Provider
Identification – Switch Owner (LSPI-SO)] interconnecting at
far-end.
2 = Direct – Outgoing different network (LSPI-SO)
interconnecting at far-end.
3 = Direct – Incoming same network (LSPI-SO) interconnecting at
far-end.
4 = Direct – Outgoing same network (LSPI-SO) interconnecting at
far-end.
5 = Tandem – Incoming different network (LSPI-SO)
6 = Tandem – Outgoing different network (LSPI-SO)
7 = Tandem – Incoming same network (LSPI-SO) interconnecting
at far-end.
8 = Tandem – Outgoing same network (LSPI-SO) interconnecting
at far-end.
65. Module 104 – Incoming Trunk Group Number

Incoming Trunk Group Number (TGN) is a four-character numeric field.
This field provides the incoming TGN for terminating calls.
66. Module 104 – Incoming Trunk Group Member Number

Incoming Trunk Member Number is a four-character numeric field that
indicates the particular trunk within the group.
Telica, Inc. 6-35

67. Module 104 – Outgoing Routing Indicator

The Outgoing Routing Indicator is a one-character numeric field. The
field describes how the traffic is generally routed over the identified trunk
group in Local Service Provider Identification (LSPI)-recording scenarios.
Valid values for this field are:

1 = Direct – Incoming different network [Local Service Provider
Identification – Switch Owner (LSPI-SO)] interconnecting at
far-end.
2 = Direct – Outgoing different network (LSPI-SO)
3 = Direct – Incoming same network (LSPI-SO) interconnecting at
far-end.
4 = Direct – Outgoing same network (LSPI-SO) interconnecting at
far-end.
5 = Tandem – Incoming different network (LSPI-SO)
6 = Tandem – Outgoing different network (LSPI-SO)
7 = Tandem – Incoming same network (LSPI-SO) interconnecting
at far-end.
8 = Tandem – Outgoing same network (LSPI-SO) interconnecting
at far-end.
68. Module 104 – Outgoing Trunk Group Number

Outgoing TGN is a four-character numeric field. This field provides the
outgoing TGN for terminating calls.
69. Module 104 – Outgoing Trunk Group Member Number

Outgoing TGMN is a four-character numeric field that indicates the
particular trunk within the group.
70. Module 164 – ChN Number Identity

Charge Number (ChN) Number Identity is a one-character numeric field.
This field identifies whether the number (or address) is an originating
number or terminating number. If originating ANI and Calling Party
Number (CPN) are the same number, value 1 should be used. If the
originating CPN or ANI number is private, then the appropriate value
should be used. The possible values for this field are:
1 = Originating Automatic Number Identification (ANI) (source)
4 = Private Originating ANI
6-36 Telica, Inc.

71. Module 164 – ChN Number Plan Indicator

Charge Number (ChN) Number Plan indicator is a one-character numeric
field that supports the following values:
0 = E.164 number for which country code length cannot be
determined
1 = E.164 number with 1-digit country code
4 = X.121 number which indicates a 4-digit Data Network
Identification Code
Refer to section 6.5, Module Number 164 for a more detailed description
of this module.
72. Module 164 – ChN Country Code or Data Network Identification

Code
The Charge Number (ChN) Country Code or Data Network Identification
Code (DNIC) field is a four-digit field that identifies the Country Code or
the DNIC.
Refer to section 6.5, Module Number 164, for a more detailed description
of this module.
73. Module 164 – ChN Significant Digits

The Charge Number (ChN) Significant Digits field is a maximum of
three-digits and indicates the number of significant digits in the next field -
Number.
of this module.
74. Module 164 – Charge Number (ChN)

The Charge Number field is a maximum of fifteen digits and, as noted
above, is preceded by the number of significant digits contained in this
field. In Module 164, this field contains the originating or terminating
number that is too long to be recorded in the structure associated with the
call. For an E.164 number, this field contains the National (Significant)
Number [N(S)N] (a maximum of 14 digits). For an X.121 number, this
field contains the Network Terminal Number (NTN) (a maximum of 10
digits).
of this module.
Telica, Inc. 6-37


The Significant Digits field contains two characters and is always 15, that
indicates there are fifteen significant digits in Digits String(s).
76. Module 611 – Final Switch, Trunk Group Number, Trunk Member
Number
The Final Switch, Trunk Group Number, Trunk Member Number field is a
15-digit field in the format of SSSTTTTTTMMMMMM where:
SSS = Switch Identification

TTTTTT = Trunk Group
MMMMMM = Trunk Member
77. Module 720 – Orig Location Type

The Origination (Orig) Location Type field contains up to 3 digits. Its
value determines the interpretation of ASCII field 81. Values are:
006 = 6-Digit Geographic Unit Building Block (GUBB)
100 = Signaling Point Code
78. Module 720 – Orig Party Identifier

The Origination (Orig) Party Identifier field is a three-digit numeric field.
This field identifies the directory number reference of the party within this
module. This field is always “001” to indicate originating party number.
79. Module 720 – Orig Location Routing Number (LRN)

The Origination (Orig) Location Routing Number (LRN) is a 10 character
numeric field. This field identifies the switching entity (LRN) that
provides service to the party identified in the Party Identifier field. The
source of the LRN is identified in the LRN Source Indicator of the
Supporting Information field.
Some LRN sources may provide the LRN in terms of an NPA-NXX sextet
followed by a four-digit pseudo-line number. Other sources may provide
the LRN in terms of an NPA-NXX sextet only. In this case, the 4 right
most (least significant) digits (the “line number” digits) of the LRN in this
table are 0-filled. The LRN Source Indicator of the Supporting
Information field may be used to distinguish between these cases.
6-38 Telica, Inc.

If an LRN is not available due to an error encountered in querying an LNP

database, each of the 10 character positions will be populated with “9s”
and the appropriate Query Status Indicator shall be set in the Supporting
Information field. If this field is not used or is not applicable, each of the
10 character positions shall be populated with “0s”.
80. Module 720 – Orig Service Provider Identity

The Origination (Orig) Service Provider Identity is an eight-character
numeric field. If used this field identifies the entity that provides service
to the party identified in the Party Identifier field. If this field is not used
or is not applicable, each of the eight characters will be populated with
“0s”.
81. Module 720 – Orig Location

The Origination (Orig) Location component is 12 digits. This field is
populated by data returned from a Service Control Point (SCP) query. Its
interpretation depends on the value in Location Type (field 77)
The Location Type has two possible values:

006 = 6-digit Geographic Unit Building Block (GUBB)
100 = Signaling Point Code (SPC)
When the Location type component represents an SPC, the 12 digits of the
Location field are parsed as follows:
Characters 1-3 = 0
Characters 4-6 = Network ID
Characters 7-9 = Network cluster
Characters 10-12= Cluster member
When the Location type field represents the six-digit GUBB for Local
Number Portability, the 12 digits of the Location field are parsed as
follows:
Characters 1-6 = The GUBB, which is in the format of an NPA-
NXX
Characters 7-12 = 0
82. Module 720 – Orig Supporting Information

The Origination (Orig) Supporting Information field is a seven-character
numeric field in the format of “SQQ0000.” This field is used in Module
720 to provide information in support of interpreting and parsing the
Location Routing Number field and the Location field.
Telica, Inc. 6-39

Character 1 (S) of this field represents the Location Routing Number

Source Indicator. Valid values are:
1 = LNP database
2 = Switching system data
3 = Incoming signaling
The next two characters (QQ) represent the Query Status Indicator. Valid
values are:
01 = Successful Query
09 = No query done
99 = Query unsuccessful, reason unknown
83. Module 049 - Count of Name Only

Count of Name Only is a maximum five-character field that counts the
number of times a calling name appears in the information delivered to the
customer. For each count, an "anonymous" or "unavailable" indication is
sent in place of the calling number. This field is appended to Structure
0110 when CLASS Feature Code field is "087". The value “087” indicates
that a customer has both Calling Number Delivery (CND) and Calling
Name Delivery (CNAM).
84. Module 049 - Count of Number Only

The Count of Number-Only field is a maximum five-character field and
only counts the number of times a calling number appears in the
information delivered to the customer. For each count, an "anonymous"
or "unavailable" indication is sent in place of the calling name.
85. Module 102 – Authorization Code

The Authorization Code is a maximum fifteen-digit field and is used to
provide Message Recording Detail (MDR). If an authorization code is
received on a call using the Authorization Codes for the Automatic
Flexible Routing (AFR) feature, this field is equal to the Authorization
Code digits. This field can be up to 15 digits. If the dialed Authorization
Code exceeds 15 digits, only the first 15 digits dialed are used; if the code
contains less than 15 digits, it is truncated.
6-40 Telica, Inc.

86. Module 103 – Account Code

This module contains an account code or Customer-Dialed Account
Recording (CDAR) information, maximum of 15 characters. If both the
account and CDAR features are used on the same call, the account code
information populates the module, not the CDAR information. Account
code information is similar to CDAR information except for the point in
the customer’s dialing pattern when the account code/CDAR information
is provided.
87. Module 105 – MDR Customer ID Context

The Message Detail Recording (MDR) customer ID Context field is one
character and identifies the customer as originating, terminating or both.
Values are:
0 = Default
1 = Originating customer’s ID
2 = Terminating customer’s ID
3 = Originating and terminating customer’s ID
88. Module 105 – MDR Customer ID

The Message Detail Recording (MDR) Customer ID field is a maximum
ten digits and contains the MDR customer identification number of the
MDR customer for whom the MDR data is intended.
89. Module 105 – Originating FAC Type

The Originating FAC (Facilities) Type field is maximum two digits and
identifies the type of originating (incoming) facilities used on the call.
This field may not be supported and will be “0” indicating that the facility
type is not known.
0 = Not known
1 = On-network colocated line
2 = On-network colocated attendant
3 = On-network trunk (physical private facility)
4 = On-network trunk (virtual private facility)
5 = Off-network colocated line
6 = Off-network trunk (public network facility)
7 = On-network foreign exchange
8 = Other on-network facility
9 = Other off-network facility
Telica, Inc. 6-41

90. Module 105 – Terminating FAC Type

The Terminating FAC (Facilities) Type field is maximum two digits and
identifies the terminating (outgoing) facilities used on the call. This field
may not be supported and will be “0” indicating that the facility type is not
known.
0 = Not known
1 = On-network co-located line
2 = On-network co-located attendant
3 = On-network trunk (physical private facility)
4 = On-network trunk (virtual private facility)
5 = Off-network co-located line
6 = Off-network trunk (public network facility)
7 = On-network foreign exchange
8 = Other on-network facility
9 = Other off-network facility
91. CLASS Feature Codes

CLASS Feature Codes is a maximum three-digit field that indicates the
CLASS feature that is involved in the call or aggregate recording interval.
The following values are used:

032 = Automatic Recall (AR) reactivation: Delayed processing
resulting in attempted call setup
033 = Automatic Callback (AC) reactivation: Delayed processing
resulting in attempted call setup
038 = AR reactivation: Delayed processing ended by customer
deactivation or extended by reactivation
039 = AC reactivation: Delayed processing ended by customer
057 = Anonymous Call Rejection: Activation
058 = Anonymous Call Rejection: Deactivation
060 = AR activation: Immediate processing resulting in attempted
call setup or busy tone
061 = AC activation: Immediate processing resulting in attempted
call setup or busy tone
062 = AR activation: Delayed processing resulting in attempted
call setup
063 = AC activation: Delayed processing resulting in attempted
call setup
068 = AR activation: Delayed processing ended by customer
069 = AC activation: Delayed processing ended by customer
070 = Customer-Originated Trace (COT) activation
075 = Calling Number Delivery Blocking (CNDB) activation
6-42 Telica, Inc.

085 = Calling Identity Delivery and Suppression (CIDS)

086 = Calling Name Delivery Blocking (CNDB)
095 = AR two-level activation: First-level completion
92. CLASS Functions

CLASS Functions is a maximum three-digit field that indicates the status
of the CLASS Screening List (SL) features (i.e., Selective Call
Forwarding (SCF), Selective Call Rejection (SCR), Distinctive Ringing/
Call Waiting (DRCW), and the analogous features when provided in an
Integrated Services Digital Network (ISDN) context) and any change to
the SL at the end of a screening list editing session. Values are as follows:
0 = None of the following values apply
1 = Active
2 = Inactive
3 = Delete
4 = Create active
5 = Create inactive
6 = Session aborted
93. CLASS Feature Status

CLASS Feature Status is a maximum three-digit field that indicates the
status of SCF, SCR and DRCW. Values are as follows:
0 = None of the following values apply
1 = Selective Call Forwarding (SCF) active
2 = Selective Call Rejection (SCR) active
3 = SCF and SCR active
4 = Distinctive Ringing/Call Waiting (DRCW) active
5 = SCF and DRCW active
6 = SCR and DRCW active
7 = SCF, SCR, and DRCW active
10 = SASCF active (Vendor Specific)
12 = SASCF & SCR active (Vendor Specific)
14 = SASCF & SDA active (Vendor Specific)
16 = SASCF, SCR & SDA active (Vendor Specific)
20 = SCF list exists (Vendor Specific)
22 = SCF and SCR lists exist (Vendor Specific)
24 = SCF and DRCW lists exist (Vendor Specific)
26 = SCF, SCR, and DRCW lists exist (Vendor Specific)
94. Deactivation Date

The Deactivation Date indicates the date that Plexus a deactivated CLASS
feature. The ten-character field represents the month, day, and year as
follows: MM-DD-YYYY.
Telica, Inc. 6-43

95. Deactivation Time

The Deactivation Time is a ten-character field. It provides the hour,
minute, seconds, and tenth of second to indicate the time of day of the
deactivation of a CLASS feature. The format of this field is
HH:MM:SS.T where H=hours, M= minutes, S = seconds, and T = tenth of
seconds.
96. Call Count – Info Delivered

The Call Count is a maximum five-digit numeric field. The Call Count -
Information Delivered field counts the number of times that both a calling
name and calling number appear in the information delivered to the
customer.
97. Call Count – Info Anonymous/Unavailable

The Call Count - Information Anonymous/Unavailable field is a
maximum five-digit field that counts the number of times that both a
calling name and calling number do not appear in the information
delivered to the customer. For each count, "anonymous" or "unavailable"
indications are sent in place of the calling name and calling number.
98. Screening List Size – SCF SCA

The Screening List Size - Selective Call Forwarding (SCF) Selective Call
Acceptance (SCA) field is a three-digit field that indicates the size of the
list for SCF SCA.
99. Screening List Size – SCR

The Screening List Size - Selective Call Rejection (SCR) field is a
three-digit field that indicates the size of the list for SCR.
100. Screening List Size – DR CW

The Screening List Size - Distinctive Ringing Call Waiting (DR CW) field
is a three-digit field that indicates the size of the list for DR CW.
101. Module 40_2 - Digits Identifier

This field is a three-digit field and identifies the type of information
represented by the digits recorded in the Digits Dialed fields for an
Advanced Intelligent Network (AIN) call. Refer to Field 61 for a
complete description.
6-44 Telica, Inc.

102. Module 40_2 – Digits

This field is a 24-digit field and contains numeric strings of dialed digits.
Refer to Field 62 for a complete description.
103. Module 40_2 - Significant Digits

This field is a maximum three-digit field and indicates the number of
significant digits in the next field(s). Refer to Field 63 for a complete
description.



description.



description.
Telica, Inc. 6-45




description.
113. Module 164 – Term Number Identity

The Terminating (Term) Number Identity field is a one-character numeric
field that identifies that the number (or address) is a terminating number.
It is always a “2”.
114. Module 164 – Term Number Plan Indicator

The Terminating (Term) Number Plan indicator is a one-character
numeric field. Refer to Field 71 for a complete description.
115. Module 164 – Term Country Code or Data Network Identification

Code
The Terminating (Term) Country Code or Data Network Identification
Code (DNIC) field is a four-digit field that identifies the Country Code or
the DNIC. Refer to Field 72 for a complete description.
116. Module 164 – Term Significant Digits

The Terminating (Term) Significant Digits field is a maximum of three-
digits and indicates the number of significant digits in the next field -
Number. Refer to Field 73 for a complete description.
117. Module 164 – Term Number

The Terminating (Term) Number field is a maximum of fifteen digits.
6-46 Telica, Inc.

118. Module 164 – CPN Number Identity

The Calling Party Number (CPN) Number Identity is a one-character
numeric field that identifies whether the number (or address) is an
originating number or terminating number. The possible values for this
field are:
3 = Originating Calling Party Number (CPN)
5= Private Originating CPN
119. Module 164 – CPN Number Plan Indicator

The Calling Party Number (CPN) Number Plan indicator is a one-
character numeric field. Refer to Field 71 for a complete description.
120. Module 164 – CPN Country Code or Data Network Identification

Code
The Calling Party Number (CPN) Country Code or Data Network
Identification Code (DNIC) field is a four-digit field that identifies the
Country Code or the DNIC. Refer to Field 72 for a complete description.
121. Module 164 – CPN Significant Digits

The Calling Party Number (CPN) Significant Digits field is a maximum of
122. Module 164 – Calling Party Number (CPN)

The Calling Party Number (CPN) field is a maximum of fifteen digits.
123. Module 164 – RN Number Identity

The Redirecting Number (RN) Number Identity is a one-character
originating number or terminating number. The only value for this field
is:
6 = Redirecting Number (RN)
124. Module 164 – RNNumber Plan Indicator

The Redirecting Number (RN) Number Plan indicator is a one-character
numeric field. Refer to Field 71 for a complete description.
Telica, Inc. 6-47

125. Module 164 – RN Country Code or Data Network Identification Code

The Redirecting Number (RN) Country Code or Data Network
126. Module 164 – RN Significant Digits

The Redirecting Number (RN) Significant Digits field is a maximum of
127. Module 164 – Redirecting Number (RN)

The Redirecting Number (RN) field is a maximum of fifteen digits. Refer
to Field 74 for a complete description.
128. Module 164 – OCN Number Identity

The Original Called Number (OCN) Number Identity is a one-character
originating number or terminating number. The value for this field is:
7 = Original Called Number (OCN)
129. Module 164 – OCN Number Plan Indicator

The Original Called Number (OCN) Number Plan indicator is a one-
character numeric field. Refer to Field 71 for a complete description.
130. Module 164 – OCN Country Code or Data Network Identification

Code
The Original Called Number (OCN) Country Code or Data Network
131. Module 164 – OCN Significant Digits

The Original Called Number (OCN) Significant Digits field is a maximum
of three-digits and indicates the number of significant digits in the next
field - Number. Refer to Field 73 for a complete description.
132. Module 164 – Original Called Number

The Original Called Number (OCN) field is a maximum of fifteen digits.
6-48 Telica, Inc.

133. Module 164 – Billing Number Identity

The Billing Number Identity is a one-character numeric field that
identifies whether the number (or address) is an originating number or
terminating number. The value for this field s:
8 = Provisioned Billing Number
134. Module 164 – Billing Number Plan Indicator

The Billing Number indicator is a one-character numeric field. Refer to
Field 71 for a complete description.
135. Module 164 – Billing Country Code or Data Network Identification

Code
The Billing Number Country Code or Data Network Identification Code
(DNIC) field is a four-digit field that identifies the Country Code or the
DNIC. Refer to Field 72 for a complete description.
136. Module 164 – Billing Significant Digits

The Billing Number Significant Digits field is a maximum of three-digits
and indicates the number of significant digits in the next field - Number.
137. Module 164 – Billing Number

The Billing Number field is a maximum of fifteen digits. Refer to Field
74 for a complete description.
138. Module 306 - OLIP

The Originating Line Information Parameter (OLIP) field is three
characters and records the originating line information parameter (or
Automatic Number Identification [ANI]) that identifies the class of service
of the originating line. It can also be used to record a unique class of
service that can identify various services offered by Local Exchange
Carriers (LECs). The possible values for this field are as follows:
Telica, Inc. 6-49

Binary BCD Description

00000000 00 Plain Old Telephone Service (POTS)
00000001 01 Multiparty line (more than 2)
00000010 02 ANI failure
00000110 06 Station Level Rating
00000111 07 Special operator handling required
00010100 20 Automatic Identified Outward Dialing
(AIOD)
00010111 23 coin or non-coin on calls using database
access
00011000 24 800 service call
00011001 25 800 service call from a pay station
00011011 27 coin
00011101 29 prison/inmate service
00011110 30 intercept (blank)
00011111 31 intercept (trouble)
00100000 32 intercept (regular)
00100010 34 telco operator handled call
00100100 36 CPE
00101000 40 to 00110001 (49) unrestricted use - locally
determined by carrier
00110100 52 OUTward Wide Area Telecommunications
Service (OUTWATS)
00111100 60 TRS
00111101 61 cellular/wireless PCS (type 1)
00111110 62 cellular/wireless PCS (type 2)
00111111 63 cellular/wireless PCS (roaming)
01000010 66 TRS
01000011 67 TRS
01000110 70 private paystations
01011101 93 access for private virtual network types of
service
139. Module 612 - Significant Digits

This field is a maximum two-digit field that indicates the number of
significant digits in the Digits field(s). It is always 30.
140. Module 612 – Orig Physical

This field is a fifteen-digit string identifying the originating physical
resource used by the call. The string is formatted as follows as
TTCCSS0OO33110 where TT is the front IOM board type as identified in
the following table.
6-50 Telica, Inc.

00 UNKNOWN
01 DS1 (89-0360)
02 DS3 (89-0365)
03
04 Octal DS3 (89-0382)
05 Octal DS3 (89-0398)
06 ATM DS3 (89-0409)
07 Octal DS3
08 ENA (89-0390)
09 Voice Server (VOP8) (89-0388)
11 OC12
12 VOIP
13 STS DS3
14 STS or DS3
15 PNA (89-0393)
16
17
18 Triple DS3 (410)
19 Octal DS3 (411)
CC - The switch (chassis) number. Currently is always 01.

SS - The slot number (00 to 17).
0 - Unused. Will be 0.
OO - The OC3. Non-zero on OC3 boards.
33 - The DS3. Non-zero on OC3 and DS3 boards.
11 - The DS1.
00 - The DS0.
Note that only TDM board types are supported. For non-TDM boards
only TTCCSS are populated. The remaining fields are zero.
141. Module 612 – Term Physical

Terminating physical resource, formatted the same as in the previous
description.
142. Module 720 – Term Location Type

Refer to Field 77 for a complete description of location type.
143. Module 720 – Term Party Identifier

The Terminating Party Identifier field is a three-digit numeric field. This
field identifies the directory number reference of the party within this
module. This field is always “002” to indicate terminating party number.
Telica, Inc. 6-51

144. Module 720 – Term Location Routing Number (LRN)

The Terminating Location Routing Number (LRN) is a 10 character
numeric field. This field identifies the switching entity (LRN) that
provides service to the party identified in the Party Identifier field. The
source of the LRN is identified in the LRN Source Indicator of the
Supporting Information field. Refer to Field 79 for a complete
description.
145. Module 720 – Term Service Provider Identity

The Terminating Service Provider Identity is an eight-character numeric
field. Refer to Field 80 for a complete description.
146. Module 720 – Term Location

The Terminating Location component is 12 digits. This field is populated
by data returned from a Service Control Point (SCP) query. Its
interpretation depends on the value in Location Type (field 77). Refer to
Field 81 for a complete description.
147. Module 720 – Term Supporting Information

The Terminating Supporting Information field is a seven-character
numeric field in the format of “SQQ0000.” This field is used in Module
720 to provide information in support of interpreting and parsing the
Location Routing Number field and the Location field. Refer to Field 82
for a complete description.
148. Unused
This field is a maximum of two digits field that indicates the number of
significant digits in the Digits field. It is always “10.”
150. Module 611 – Call ID

This field is a 15-digit string that contains a call identifier. The call
identifier is generated by the switch so call IDs are unique only among
calls from a particular switch. The first five digits are always “00000.”
151. Module 198 – Module Descriptor

This field identifies the type of data in the data field. The value is always:
00010” = Originating SIP Call Id
6-52 Telica, Inc.

152. Module 198 – Orig SIP Call Id

This field is a digit string of up to 32 digits that contains the SIP call
identifier associated with a call originating from or terminating to a SIP
interface.

This field identifies the type of data in the data field. The value is always:
00011 = Terminating SIP Call Id
154. Module 198 - Term SIP Call Id

This field is a digit string of up to 32 digits that contains the SIP call
identifier associated with a call originating from or terminating to a SIP
interface.
155. Module 68 – Called DN Description

This field indicates the called Directory Number (DN) needs some special
handling in billing situations. Values are as follows:
001 = Called directory number marked anonymous
006 = Called directory number not marked anonymous

This field is a three-digit field that indicates the number of significant
digits in the Digits Dialed field.
157. Module 101 - Digits Dialed

This field contains a numeric string of digits dialed.
158. Module 101 – Access Code

This field contains a 5-digit number from 0-99999 that identifies the
access code.

This field is a two-digit field that indicates the number of significant digits
in the Call Sequence Number field. It is always “10.”
160. Module 611 – Call Sequence Number

This field is five digits and identifies the call sequence number.
Telica, Inc. 6-53


This field is a one-digit field that indicates the number of significant digits
in the Record Sequence field. It is always “2.”
162. Module 616 – Record Sequence Number

This field is five-digit field that identifies the record sequence number. It
is in the format of “0000#.”

in the Dialed – Prefix Digits field. It is always “1.”
164. Module 616 - Dialed – Prefix Digits

This field is five-digit field that identifies the prefix digits of the dialed
number. It is always prefaced with “0000.” Values of the significant digit
(fifth digit) are:
0 = None
1 = 0 Prefix
2 = 01 Prefix
3 = 011 Prefix
4 = 1 Prefix
5 = 00 Prefix
6 = 101 Prefix.

in the Called – Prefix Digits field. It will always be “1.”
166. Module 616 - Called – Prefix Digits

This field is five-digit field that identifies the prefix digits of the called
number. It is always prefaced with “0000.” Values of the significant digit
(fifth digit) are:
0 = None
1 = 0 Prefix
2 = 01 Prefix
3 = 011 Prefix
4 = 1 Prefix
5 = 00 Prefix
6 = 101 Prefix.
6-54 Telica, Inc.

167. Module 40 – Digits Identifier

The Digits Identifier field is a three-digit numeric field. This field
identifies the type of information represented by the digits recorded in the
Field 168. The value for the Digits Identifier field is always 005
indicating the next field is the Outpulse number.
168. Module 40 – Outpulse Digits

The Outpulse Digits field contains 24-numeric characters. This field
includes the Digits 1 and Digits 2 field defined in the AMA definition of
module 40. The field captures the outpulse digits. If there are unused
digits in either field, the most significant digits are right justified and the
unused digits are filled with “0s”.

The Significant Digits field identifies the number of significant digits
associated with Field 168.

The Significant Digits field identifies the number of significant digits in
the next field. The value is always 5.
171. Module 616 – Release Originator, Category, Cause Indicator

The Release Originator, Category, Cause Indicator field is five-digits in
the format of “OCRRR.” The first digit (O) indicates who releases the
call. Values are:
1 = Release initiated by the incoming interface.
2 = Release initiated by the outgoing interface.
3 = Release initiated internally (by the stack)
The “C” indicates the Cause Category and the values can be:
0 = International Telecommunications Union (ITU) standard
2 = National
3 = Network specific
“RRR” indicates the release cause indication. Refer to Appendix A for a

complete list.
Telica, Inc. 6-55


The Module Descriptor field is a five-digit field describing the next field.
The value that appears in this field 172 is configurable by the customer. It
is set in the BTS configuration (.ini) file. Since module 198 can be used
for different purposes, the Module Descriptor (Table 575) identifies what
the Module is being used for. In the case of fields 172 and 173, Module
198 is being used for Release Treatment.
173. Module 198 – Release Treatment

The Release Treatment field has a maximum of ten characters and
indicates the last release treatment for the call.

175. Module 611 – Orig Echo Indicator, NLP Indicator, DSP

The Originating Echo Indicator, NLP Indicator, DSP field is in the format
of “000000ENDDDDDDD.” The number of digits is actually 15 with six
leading zeros. The first significant digit is indicated with “E” for the
Originating Echo Indicator. Values are:
0 = No echo cancellation was required on the call or was not
applicable (for packet side connection).
1 = Echo cancellation was used on the call.
2 = Echo cancellation was requested for the call, but no resources
were available.
3 = Echo cancellation was requested, applied, and later dropped for
a fax/modem type call.
The second significant digit is indicated with “N” for the NLP (Non-
Linear Processing). Values are
0 = No NLP was required on the call.
1 = NLP was used on the call.
2 = NLP was requested for the call, but no resources were
available.
3= NLP was requested, applied, and later dropped for a fax/modem
type call.
The “DDDDDDD” is represented as follows:

First D = Failover occurred and values are “0” or “1.”
Second and third D = IOM used and values are “1” through “17.”
Fourth and fifth D = Processor and values are “1” through “8.”
Sixth and seventh D = DSP and values are “1” through “6”
6-56 Telica, Inc.


177. Module 611 – Term Echo Indicator NLP Indicator, DSP

The Terminating Echo Indicator, NLP Indicator and DSP field is in the
format of “000000ENDDDDDDD.” The number of digits is actually 15
with six leading zeros. The first significant digit is indicated with “E” for
the Originating Echo Indicator and the second significant digit is indicated
with “N” for the NLP (Non-Linear Processing). Refer to Field 175 for
details.

the next three fields. The value is always 45.
179. Module 613 – Orig Local IP Address

The Originating Local IP Address field is a 15-digit field with three
leading zeros. The remaining twelve digits indicate the local IP address.
180. Module 613 – Orig Remote IP Address

The Originating Remote IP Address field is a 15-digit field with three
leading zeros. The remaining twelve digits indicate the remote IP address.
181. Module 613 – Orig Local/Remote Port, Codec, Fax Indicator

The Originating Local/Remote Port, Codec, and Fax Indicator field is a
15-digit field in the format of 00LLLLLRRRRRCCF. “LLLLL” are the
digits for the local IP port, “RRRRR” are the digits for the remote IP port,
“CC” are the digits for the Codec. Values for the Codec can be:
0 = G723
1 = G726-16
2 = G726-24
3 = G726-32
4 = G729
5 = G729a
6 = PCMU
7 = PCMA
8 = X-NSE
9 - X-CCD
10 = Telephone Event
11 = Cisco Clear Channel
Telica, Inc. 6-57

12 = Clear Mode
99 = Unknown
“F” is the Fax indicator digit. Values are:

0 = Call did not utilize fax/modem. Currently only value used.
1 = Call used fax/modem.
0 = Call used T.38.

the next three fields. The value is always 45.
183. Module 613 – Term Local IP Address

The Terminating Local IP Address field is a 15-digit field with three
leading zeros. The remaining twelve digits indicate the local IP address.
184. Module 613 – Term Remote IP Address

The Terminating Remote IP Address field is a 15-digit field with three
leading zeros. The remaining twelve digits indicate the remote IP address.
185. Module 613 – Term Local/Remote Port, Codec, Fax Indicator

The Terminating Local/Remote Port, Codec, and Fax Indicator field is a
15-digit field in the format of 00LLLLLRRRRRCCF. “LLLLL” are the
digits for the local port, “RRRRR” are the digits for the remote port, “CC”
are the digits for the Codec and “F” is the Fax indicator digit. Refer to
Field 181 for Codec values.
186. Module 264 – Orig Release Cause Indicator

The Originating Release Cause Indicator field is a 4-digit field in the
format of “CRRR.” The “C” indicates the Cause Category and the values
can be:
2 = National
complete list.
187. Module 264 – Orig Packets Sent

The Originating Packets Sent field is a 13-digit field that identifies the
number of packets sent.
6-58 Telica, Inc.

188. Module 264 – Orig Packets Received

The Originating Packets Received field is a 13-digit field that identifies
the number of packets received.
189. Module 264 – Orig Packets Lost

The Originating Packets Lost field is a 13-digit field that identifies the
number of packets lost.
190. Module 264 – Orig Octets Sent

The Originating Octets Sent field is a 13-digit field that identifies the
number of octets sent.
191. Module 264 – Orig Octets Received

The Originating Octets Received field is a 13-digit field that identifies the
number of octets.
192. Module 264 – Orig Jitter

The Originating Jitter field is a 3-digit field indicating the jitter. This field
is currently not supported.
193. Module 264 – Orig Latency

The Originating Latency field is a 3-digit field indicating the latency. This
field is currently not supported.
194. Module 264 – Term Release Cause Indicator

The Terminating Release Cause Indicator field is a 4-digit field in the
format of “CRRR.” The “C” indicates the Cause Category and the values
can be:
2 = National

complete list.
195. Module 264 – Term Packets Sent

The Terminating Packets Sent field is a 13-digit field that identifies the
number of packets sent.
Telica, Inc. 6-59

196. Module 264 – Term Packets Received

The Terminating Packets Received field is a 13-digit field that identifies
the number of packets received.
197. Module 264 – Term Packets Lost

The Terminating Packets Lost field is a 13-digit field that identifies the
number of packets lost.
198. Module 264 – Term Octets Sent

The Terminating Octets Sent field is a 13-digit field that identifies the
number of octets sent.
199. Module 264 – Term Octets Received

The Terminating Octets Received field is a 13-digit field that identifies the
number of octets
200. Module 264 – Term Jitter

The Terminating Jitter field is a 3-digit field indicating the jitter. This
field is currently not supported.
201. Module 264 – Term Latency

The Terminating Latency field is a 3-digit field indicating the latency.
This field is currently not supported.
6.4 Module Inclusion Rules

This section contains the module inclusion rules that must be met in order
for the data fields of a specific module to be appended to the ASCII
Billing Server master record. The modules supported by the ASCII
Billing Server are listed in Table 6-E.
Table 6-E. Module Numbers and Descriptions
Module Description
021 Carrier Access – Originating
022 Long Duration Connection
025 Circuit Release Module
027 Business Customer ID Module
029 Alternate Billing Number Module
040 Digits Module
049 Calling Name/Number Delivery Module
068 Called Directory Number (DN) Descriptor
101 Digits Dialed Module
102 Authorization Code Module
6-60 Telica, Inc.

Module Description
103 Account Code/Customer Dialed Account Recording (CDAR)
Module
104 Trunk Identification Module
105 Message Detail Recording (MDR)
164 E.164/X.121 Number Module
198 Flex Module
264 Quality of Service (QoS) (NDGR)
306 Originating Line Information Parameter (OLIP)
611 Generic Module
612 Generic Module: Two Digits String Format
613 Generic Module: Three Digits String Format
616 5 Digit Information Module
719 Local Number Portability Core Module
720 Local Number Portability (LNP) Module (NDGR)
6.4.1 Module 021, Carrier Access – Originating

This module contains fields necessary to identify originating
Interexchange Carrier/International Carrier (IC/INC) access, including
carrier identification and the elapsed time of the carrier’s access to the
Local Access and Transport Area (LATA) network. However, in certain
situations, the Automatic Number Identification/Calling Party Number
(ANI/CPN) indicator is needed for the terminating end of a call (as in an
SS7 Environment), and this module may be used to identify terminating
IC/INC access.
6.4.2 Module 022, Long Duration Connection

This module contains fields necessary for time stamping long duration
connection records. Present date and present time refer to the moment
when the long duration connection is output or to the moment of
disconnect.
A long duration connection is an intra-network or inter-network call on

which, at a scheduled record generation time, both calling and called
parties remain off-hook ("connected" for carrier timing) and the elapsed
time and/or carrier elapsed time of the call already exceeds 1440 minutes
(24 hours).
For intra-network calls, the requirements for long duration connection

processing are as follows:
1. First record of a long duration connection must be generated at

the first scheduled record generation time after the elapsed time
of the call exceeds 1440 minutes.
Telica, Inc. 6-61

2. First record must be generated as a conventional record that

must contain the Connect Date, Connect Time, and Elapsed
Time fields, except the Timing Indicator field must contain a
“1” in character 3, indicating the start of a long duration
connection.
3. Elapsed time reported in the first record must equal the interval
from call connect time to the time when the record is
generated.
4. Determine inaccuracy compensation and the variable
inaccuracy allowance must be applied to duration time
determination made for the Elapsed Time field in the first
record.
5. Continuation record must be generated at each record
generation time that occurs between the time a call’s first
record is made and call disconnect.
6. Continuation record of a long duration connection must contain
Connect Date and Connect Time fields and a Long Duration
Connection Module.
7. Timing Indicator field of a continuation record must contain a
“2” in character 3, indicating a continuation record.
8. Elapsed time reported in a continuation record must be the
interval from the time when the previous record was generated
to either the time the current record is generated or the time the
call disconnects.
Record generation requirements for long duration connections are shown

in Figure 6-1.
6-62 Telica, Inc.

G1 G2 G3 Gk
Cell
Connect Disconnect
Elapsed Time > 24 hours
Actual time Long duration call "Continuation" "Continuation" "Continuation"

of call recognized. First record output. record outpu for record outpu for
connect record computed. Duration covers G to G . G to disconnect.
k-1 k k
computed Duration covers interval G2 to G3 .
and stored interval from call
pending connect to G2
disconnect. including
determinate
inaccuracy
compensation and P504-AA
variable inaccuracy 12-06-01
allowance.
Key: G denotes the scheduled record generation time.
Figure 6-1. Long Duration Call Sample
For inter-network calls, the requirements for intra-network calls apply.

The following requirements for carrier elapsed time recording also apply.
1. Long duration connection requirements (1 – 8 above) must be
applied to inter-network calls.
2. First record of a long duration connection for an inter-network
call must be generated at the first scheduled record generation
time after the carrier elapsed time (instead of elapsed time) of
the connection exceeds 1440 minutes.
3. First record for an inter-network call must be generated as a
conventional record that must contain Carrier Connect Date,
Carrier Connect Time, and Carrier Elapsed Time fields, except
the Timing Indicator field must contain a “1” in character 3,
indicating a start of a long duration connection.
4. Carrier Elapsed Time field of the first record for an inter-
network call must be equal to the interval from carrier connect
time to the time when the record is generated.
Telica, Inc. 6-63

5. Determinate inaccuracy compensation and the variable

determination made for the Carrier Elapsed Time field in the
first record for an inter-network call.
6. Continuation record of a long duration connection for an inter-
network call must contain Carrier Connect Date and Carrier
Connect Time fields which must include the date and time of
the original call set up, and Long Duration Connection Module
(Present Day and Present Time fields).
7. Timing Indicator field of a continuation record for an inter-
network call must contain a “2” in character 3, indicating a
continuation record.
8. Carrier Elapsed Time field for a continuation record for an
inter-network call must be the interval from the time when the
previous record was generated to either the time the current
record is generated or the time the call disconnects.
Forward changes in time (for example, 11:30 p.m. to 12:30 a.m. of the
next day with midnight as the record generation time) and backward
changes in time (for example, 12:30 a.m. to 11:30 p.m. of the preceding
day), can span record generation time.
When a forward change in time spans a record generation time, the switch
must generate all records that already have an elapsed time (or carrier
elapsed time) exceeding 1440 minutes. Also, the switch must generate all
continuation records that would have occurred at the spanned record
generation time.
An exception occurs when the forward change in time that spans a record
generation time follows a backward change in time that spanned the same
record generation time. In this case, records should not be generated.
When a backward change in time spans a record generation time, the
switch must not generate any first and continuation records at the record
generation time following the time change.
AMA data should be generated for a long duration connection as

described in the following example.
A call originates at 8:00 p.m. on day 1 and disconnects at 2:00 p.m. on

day 4. The time designated by the LEC for record generation each day is
3:00 a.m. At 3:00 a.m. on the second day, no record is generated because
the elapsed time is still less than 1440 minutes. Three records should be
generated as follows:
6-64 Telica, Inc.

1. The first record is generated at 3:01:10 a.m. on the third day,

with an elapsed time of 1861 minutes, 10 seconds. The record
is generated after the scheduled record generation time due to
processing or scheduling delays in the switch.
2. The first continuation record is generated at 3:02:00 a.m. on the
fourth day with an elapsed time of 1440 minutes, 50 seconds,
which is the interval from 3:01:10 a.m. of the third day to
3:02:00 a.m. of the fourth day. Again, the switch had
processing or scheduling delays, causing the record to be
generated after the scheduled record generation time.
3. The second continuation record is generated at disconnect at
2:00:00 p.m. on the fourth day with an elapsed time of 658
minutes, 0 seconds.
6.4.3 Module 025, Circuit Release Module

This module contains the fields necessary to identify the date and time of
circuit (or trunk) release.
If this module is included in a BAF record format generated for intra-

network calls on which the called party off-hook is not detected, the
Circuit Date and Time fields indicate the date and time of circuit (or trunk)
release. The Called Party Off-Hook Indicator field contains a “1”
(indicating called party off-hook is not detected). The Elapsed Time field
is set to “0” and the Connect Date and Time fields indicate the time of
circuit (or trunk) seizure.
This module is not used with carrier access calls, nor should it be used
with Operator Services System (OSS) calls.
6.4.4 Module 027, Business Customer ID Module

This module is included in a record when, as a result of the service, the
record must contain a business customer identification. The Business
Customer Identification is populated in the Business Customer
Identification field (right-justified) and unused characters are populated
with zeroes.
This module can be used, for example, with Private Virtual Network
(PVN) calls. The Business Customer ID module is included in the BAF
record if the response message from the Service Control Point (SCP)
contains a Business Customer Identification number. If a Business
Customer Identification number is not included in the response message,
the Business Customer Identification Module is not included in the record.
Telica, Inc. 6-65

In an AIN BAF record, the Business Customer ID Module is recorded

instead of this module when the response message from the SCP to the
SSP contains an AMA sequence number parameter in addition to the
AMA Business Customer ID parameter.
6.4.5 Module 029, Alternate Billing Number Module

This module is included in a BAF record when an alternate billing number
is needed. This billing number populates the Alternate Billing Number
field, is right-justified, and unused characters are populated with zeroes.
This module can be used, for example, with PVN calls. The Alternate
Billing Number module is only included in the BAF record for a PVN call
if the response message from the SCP contains a billing number.
In an AIN BAF record, the Alternate Billing Module is recorded instead of

this module when the response message from the SCP to the SSP contains
an AMA Sequence Number parameter in addition to the AMA Alternate
Billing Number parameter.
6.4.6 Module 040, Digits Module

This module is used to record digits used during an AIN call. Up to 24
significant digits can be recorded. This module is only appended to
Structure Codes 0220 and 0221, and it may be repeated in the same AMA
record.
The Digits Module is recorded instead of this module when recording

SCP-provided digits and the response message from the SCP to the SSP
also contains an AMA Sequence Number parameter.
6.4.7 Module 049, Calling Name/Number Delivery Module

This module provides the Count of Name-Only and Count of Number-
Only fields. The Count of Name-Only field counts the number of times a
calling name appears in the information delivered to the customer. For
each count, an "anonymous" or "unavailable" indication is sent in place of
the calling number. - The Count of Number-Only Deliveries field counts
the number of times a calling number appears in the information delivered
to the customer. For each count, an "anonymous" or "unavailable"
indication is sent in place of the calling name.
6-66 Telica, Inc.

6.4.8 Module 68, Called Directory Number (DN) Descriptor

This module contains one field that describes the special billing potential
of the called Directory Number (DN). If the called DN requires special
treatment by the Revenue Accounting Office (RAO) in the billing process,
this module will be appended to the Automatic Message Accounting
(AMA) data structure normally generated for that call. Examples of
features that use this module are the CLASS features Automatic Callback
(AC) and Automatic Recall (AR).
6.4.9 Module 101, Digits Dialed Module

This module is currently used in Message Detail Recording (MDR).
When the actual number to which the call is routed differs from the
number dialed by the originator of the call (as seen at the switching system
at which the MDR data record is generated), the actual digits received on
the originating facility populate the digits dialed fields. The Access Code
for private network calls (i.e., Tie Trunk calls) contains the digits dialed to
indicate the particular type of call (e.g., a code dialed for Wide Area
Telecommunications Service (WATS) access). The dialed Access Code is
right-justified in Table 803 and unused characters are filled with zeros. For
public network calls dialed using prefix digits for access to the public
network (i.e., "dial 9" calls), the prefix digits dialed before the public
directory number populate the Access Code field, are right-justified, and
unused characters are filled with zeros.
6.4.10 Module 102, Authorization Code Module

This module is used to provide Message Recording Detail (MDR). If an
authorization code is received on a call using the Authorization Codes for
the Automatic Flexible Routing (AFR) feature, the Authorization Code
digits populate Table 126. If the dialed Authorization Code exceeds 15
digits, only the first 15 digits dialed populate this field. If the code
contains fewer than 15 digits, it is right-justified, and unused characters
are filled with zeros.
6.4.11 Module 103, Account Code/Customer Dialed Account Recording (CDAR)

Module
This module contains account code or Customer-Dialed Account
Recording (CDAR) information. If both the account and CDAR features
are used on the same call, the account code information populates the
module, not the CDAR information. Account code information is similar
to CDAR information except for the point in the customer dialing pattern
when the account code/CDAR information is provided.
Telica, Inc. 6-67

6.4.12 Module 104, Trunk Identification Module

This module captures trunk identification information for incoming and
outgoing calls. Module 104 appears when a trunk-side connection occurs.
For example, if a call originates from a PRI and routes out over an SS7
trunk, one module 104 will appear on the record with the SS7 trunk
information. If the call is switched from one SS7 trunk to another SS7
trunk, two module 104s will appear on the record with the incoming and
outgoing trunk information. If a call originates PRI and terminates via
PRI from the same switch, no module 104 appears on the record.
6.4.13 Module 105, Message Detail Recording (MDR)

This module is included in every Message Detail Recording (MDR)
record. The MDR customer for whom the MDR data is intended is
uniquely identified in Table 87. The facility types in Table 246 are
recorded from the perspective of the switch that is creating the MDR data
record.
6.4.14 Module 164, E.164/X.121 Number Module

This module provides the means to record lengthy numbers that cannot be
recorded in the structure applicable to the call. Refer to section 6.5,
Module Number 164 for details concerning module 164.
6.4.15 Module 198, Flex Module

This module is used to hold a field that has a variable length. Table 575 is
a context identifier (i.e., originating address, terminating address) that
defines the tables that follow Table 575.
6.4.16 Module 264, Quality of Service (QoS) (NDGR)

Module Code 264 is used to record the Network Latency and Inter-arrival
jitter that are associated with Quality of Service (QoS). It includes the release
cause indicator, the number of packets sent, the number of packets
received, the number of packets lost, the number of octets sent, the
number of octets received, the inter-arrival jitter and the amount of
network latency.
6.4.17 Module 306, Originating Line Information Parameter (OLIP)

This module identifies the class of service of the originating line. It can
also be used to record a unique class of service that can identify various
services offered by Local Exchange Carriers (LECs).
6.4.18 Module 611, Generic Module

This is a generic, general-purpose module. The Generic Context Identifier
field (Table 237) defines the parsing rules and the type of data to be stored
in the Digits String field (Table 126).
6-68 Telica, Inc.

6.4.19 Module 612, Generic Module: Two Digits String Format

This module is a generic, general-purpose module used when the
requirements of the application fit the format of this layout. The Generic
Context Identifier field, (Table 237) defines the number of characters in
the Digits String 1 (Table 126) and Digits String 2 (Table 126) fields. The
Digits String fields identify the IOM typeand slot.
6.4.20 Module 613, Generic Module: Three Digits String Format

Context Identifier field (Table 237) defines the number of digits to be
stored in the Digits String 1 (Table 126), Digits String 2 (Table 126) fields
and Digits String 3 (Table 126). The Digit String 1 and 2 fields are used
to identify IP addresses and Digit String 3 is used to identify the local and
remote ports, the Codec and the Fax indicator.
6.4.21 Module 616, 5 Digit Information Module

This module is a general purpose, vendor specific, 5 digit information
module.
6.4.22 Module 719, Local Number Portability (LNP) Core Module

This module provides the LRN when applicable for calls in the LNP
environment. Module 719 is now obsolete. Telica has replaced it with
Module 720.
6.4.23 Module 720, Local Number Portability (LNP) Module

This module is used to convey information pertinent to rating and billing
of calls to and/or from ported numbers in environments with LNP.
6.5 Module Number 164

Module 164 (also know as E.164/X.121 Number Module ) is appended to
provide additional information about the telephone numbers associated
with the call gathered from the CDR, only if the CDR call type and call
conditions dictate that Module 164 needs to be appended to the CDR.
More specifically, Module 164 will be appended to the ASCII record

being generated when one or more of the following conditions occur:
− The originating number to be recorded in the originating
number field (defined in section 8.3.1, R1-50) exceeds 10
digits. If it is 10 or fewer digits (not including incoming
international calls), it is recorded in the originating number
fields of the structure and the module is not appended.
Telica, Inc. 6-69

− The terminating number to be recorded in the terminating

number fields (section 83.1, R1-50) exceeds 12 digits. If it is
12 or fewer digits, it is recorded in the terminating number
− The Call is forwarded
− The Calling Party Number is different than the Charge Number
− The Trunk Group is provisioned with a Billing Number
Although it is unlikely, it is possible to have all the conditions occur in

one call. Based on the population rules for Module 164, this would
require a maximum of 6 module 164s.
Telica’s Module 164 contain the following ordered list of fields:

− Module Code
− Number Identify
− Country Code or Data Network Identification Code
− Significant Digits in the Next Field(s)
− Number
Call Forwarding Rules for Populating Module 164
A call can be forwarded from one to five times on one dialed call. Each
time the call is forwarded, module 164 is used to capture information
about the call that would otherwise be lost. For example, A calls B and, B
forwards the call to C, when B receives the bill for the B to C leg of the
call, B would like to know that it was a forwarded call and who originated
it. To provide this data, a Module 164 is appended with the Calling Party
Number and the Service Feature Field (defined above) populated with a
“12” to indicate that the call was forwarded.
Since a CDR may be generated for each individual subscriber at the

forwarded leg of the call, the CDR needs to capture different information
at each leg. Table 6-F shows the various legs of a call that has been
forwarded several times and the information that may be populated by
signaling for each leg. The Plexus 9000 will use this information to
populate multiple module 164s as indicated in the chart. The table also
illustrates how the modules will be populated if there is a billing number
override associated with the subscriber or the associated trunk group used
for the call.
6-70 Telica, Inc.

6.5.1 E.164 Numbering Plan

The E.164 numbering plan, as derived from ITU-T Recommendation
E.164 and TR-TSY-000448, defines the currently used structure of an
international telephone number. According to Recommendation E.164,
such numbers follow the CC+N(S)N format where:
CC= Country Code – Identifies the destination country and can vary
between 1 and 3 digits.
N(S)N = National (Significant) Number – Identifies the destination

termination, and the maximum N(S)N length is 11 digits.
CC+N(S)N = maximum of 12 digits.
Table 6-F. Call Forwarding Module 164 Population Chart

Leg
Signaling A -> B B -> C C -> D D -> E E -> F
CPN (Calling Party Number) A A A A A
ChN (Charge Number) B C D E
RN (Redirecting Number} B C D
OCN (Original Called Number) B B
CN (Called (terminating) Number) B C D E F
SFC (Service Feature Code (BAF 0 12 12 12 12
Table 12))
CDR
Orig A B C D E
Term B C D E F
Module 164 A A A A
Module 164 B C D
Module 164 B B
Module 164
CDR w/BN override

Orig BN BN BN BN BN
Term B C D E F
Module 164 A B C D E
Module 164 A A A A
Module 164 B C D
Module 164 B B
Note: The letter in each cell indicates the value that should be assigned to each
variable for a particular leg. For instance, the Redirecting Number (RN) should be
assigned B's number for C -> D leg. Empty cells indicate that the variable is not set to
a valid value and should be marked as 'Not present'.
Telica, Inc. 6-71

The above applies until “Time T” (year-end 1996). After that, CC+N(S)N
will be a maximum of 15 digits, which results in a maximum N(S)N of 14
digits since no changes are planned for the structure of a CC.
The North American Numbering Plan (NAPN) is the numbering plan

currently used in the United States. It meets the requirements set forth in
the ITU-T Recommendation E.164.
6.5.2 X.121 Numbering Plan

The International Numbering Plan for Public Data Networks (PDNs) is
documented in ITU-T-Recommendation X.121. An international
/internetwork data number consists of the Data Network Identification
Code (DNIC) followed by the Network Terminal Number (NTN). The
DNIC consists of a three-digit Data Country Code (DCC) followed by a
network digit. DCCs are ITU-T administered; however, they are not the
same country codes specified in Recommendation E.164. The DCC
identifies a country; the network digit identifies a specific data network
within the country identified by the DCC. The DCC in conjunction with
the network digit can identify up to ten PDNs. Multiple DCCs may be
assigned to a country where more than ten PDNs exist. Recommendation
X.121 specifies a maximum length of ten digits for the NTN. No
minimum NTN length is specified. The format of the NTN is determined
by the network provider that is identified by the DNC. Although the most
commonly discussed usage of the X.121 numbering plan is in connection
with packet data networks, the plan is also applicable to circuit-switched
data networks that may choose to use it. X.121 numbers are included in
the E.164/X.121 Number Module (Module Code 164) to cover the
possibility of a future increase in length of NTN.
6.6 Call Types, Structure Codes, and Modules

A call type, together with a call type code, represents the
service/technology provided to a customer or carrier. The call type code
in a BAF record provides guidance to accounting systems for processing
the record. Call types are determined by the type of service.
A structure is a set of eight common data fields, followed by a group of

fields required by the type of service or technology for which the data are
recorded. Each structure is a unique, ordered set of fields identified by a
structure code (the third data field in the ASCII master record). Every
BAF structure contains a common set of eight data fields. Structure codes
are determined by call type.
6-72 Telica, Inc.

In Table 6-G, all data fields for each particular structure code are listed.
The eight common data fields, common to every structure code, are listed,
but they will not be included in the Structure Code Fields column in
Table 6-G. Therefore, a structure code listed in Table 6-G contains all
data fields listed in the Structure Code Fields column for that structure
code, as well as the eight common data fields provided in the following
list. The letter appearing beside most entries listed identifies which field
description to reference in the lettered list in section 5, ASCII-Format
Master Record Field Descriptions, of this document.
The eight common data fields shared by most structure codes are:
− Record Descriptor Word

− Hexadecimal Identifier
− Structure Code (b)
− Call Type (a)
− Sensor Type (c)
− Sensor Identification (d)
− Recording Office Type (e)
− Recording Office Identification (f)
Modules are predefined sets of data fields that may be appended to a

structure according to the service/technology rendered, or to report
information connected with specific conditions. Modules are often
referred to by their module code number. Modules have fixed names that
indicate the meaning of the data they contain or the service or capability
for which they are used. They are determined by the call type and the
conditions of the call. Modules are appended to the end of the record,
after the structure code fields.
Use the letter listed next to the field in Table 6-G to cross-reference
against the field definitions provided in section 6.3, ASCII-Format Master
Record Field Descriptions.

To use the ABS or BTS successfully with the Plexus 9000, you must first
meet specific ABS or BTS server platform requirements and then
configure the ABS or BTS on the Sun server to communicate with the
Plexus 9000, and configure the Plexus 9000 to communicate with the
ABS. The procedures for installing and configuring the ABS or BTS
application on a Server are found in the Procedures section of this guide.
Procedures for provisioning the Plexus 9000 for Billing are found in the
Plexus 9000 Installation and Operation Manual.
Telica, Inc. 6-73

Table 6-G. Call Types, Modules and Structure Code 0625
Call Types, Modules and Structure Code 0625 (5 pages)
Call Call Type Name Mod. Module Fields and Field Ref. # Structure Code Fields Calling Pattern
Type for Sect. 6 (Based on Call Type)
110 Inter-LATA 021, 021 - Module Code ID, Eight common data fields, 1+NXX+ XXXX,
Station Paid 104, IC/INC Prefix, Connect Date (g), 0-,
164, Carrier Access Date (tt), Timing Indicator (h), 0+NXX+ XXXX,
720 Carrier Access Time (uu), Study Indicator (i), 1+ NPA+555+ 1212,
Elapsed Time (vv), Called Party Off-hook Indicator (j), 101XXXX+ 0+…,
IC/INC Call Event Status (ww), Service Observed/Traffic Sampled (k), 101XXXX+00-,
Trunk Group Number (xx), Operator Action (l), 101XXXX+ 0/1+…
Routing Indicator (yy), Service Feature (m), (originating),
Dialing and Presubscription Indicator (zz), Originating NPA (n), 101XXXX+ 01/011+…
ANI/CPN Indicator (aaa) Originating Number (o), (orig),
104 – Module Code ID, Overseas (International Call) Indicator (p), 01/011+7 to 18-digit,
Trunk ID Terminating NPA (q), 800 call (non-SSP),
164 – Module Code, Terminating Number (r), 1+500+7-digits,
Number Identity (rrr), Connect Time (s), 1+700+7-digits,
Country Code or Data Network ID Code (ttt), Elapsed Time (t), 1+900+7-digits
Significant Digits in Next Field(s) (uuu), IC/INC Prefix (u),
Number (vvv) Carrier Connect Date (v),
720 – Module Code ID, Carrier Connect Time (w),
Party ID (zzz), IC/INC Call Event Status (y),
Location Routing Number (LRN) (xxx), Trunk Group Number (z),
Service Provider Identity (bbbb), Routing Indicator (aa),
Location (cccc), Dialing and Presubscription Indicator (bb),
Supporting Information (dddd) ANI/CPN Indicator (cc)
119 Terminating 021, 021 - Module Code ID, Eight common data fields, Terminating exchange
Access Record 104, IC/INC Prefix, Connect Date (g),
164, Carrier Access Date (tt), Timing Indicator (h),
720 Carrier Access Time (uu), Study Indicator (i),
Elapsed Time (vv), Called Party Off-hook Indicator (j),
IC/INC Call Event Status (ww), Service Observed/Traffic Sampled (k),
Trunk Group Number (xx), Operator Action (l),
Routing Indicator (yy), Service Feature (m),
Dialing and Presubscription Indicator (zz), Originating NPA (n),
ANI/CPN Indicator (aaa) Originating Number (o),
104 – Module Code ID, Overseas (International Call) Indicator (p),
Trunk ID Terminating NPA (q),
164 – Module Code, Terminating Number (r),
Number Identity (rrr), Connect Time (s),
Country Code or Data Network ID Code (ttt), Elapsed Time (t),
710 Originating Toll Eight common data fields,
AMA Recording Connect Date (g),
(Vendor Specific) Timing Indicator (h),
Study Indicator (i),
Called Party Off-hook Indicator (j),
Service Observed/Traffic Sampled (k),
Operator Action (l),
Service Feature (m),
Originating NPA (n),
Originating Number (o),
Overseas (International Call) Indicator (p),
Terminating NPA (q),
Terminating Number (r),
Connect Time (s),
Elapsed Time (t),
IC/INC Prefix (u),
Carrier Connect Date (v),
Carrier Connect Time (w),
IC/INC Call Event Status (y),
Trunk Group Number (z),
Routing Indicator (aa),
Dialing and Presubscription Indicator (bb),
ANI/CPN Indicator (cc)
720 Connecting 021, 021 - Module Code ID, Eight common data fields,
Network Access 104, IC/INC Prefix, Connect Date (g),
Incoming Record 164, Carrier Access Date (tt), Timing Indicator (h),
7. AMA Lite Reports
7.1 Introduction ..........................................................................................................7-2
7.2 CDR and AMA Lite Formats ............................................................................... 7-2
7.2.1 CDR Data Prior to Conversion.................................................................7-2
7.2.2 AMA Files After Conversion...................................................................7-4
7.3 Module Inclusion Rules .......................................................................................7-8
7.3.1 Module 021, Carrier Access – Originating ..............................................7-8
7.3.2 Module 022, Long Duration Connection .................................................7-9
7.3.3 Module 025, Circuit Release Module ....................................................7-12
7.3.4 Module 027, Business Customer ID Module .........................................7-12
7.3.5 Module 029, Alternate Billing Number Module....................................7-13
7.3.6 Module 040, Digits Module ...................................................................7-13
7.3.7 Module 049, Calling Name/Number Delivery Module .........................7-13
7.3.8 Module 68, Called Directory Number (DN) Descriptor ........................7-14
7.3.9 Module 101, Digits Dialed Module........................................................7-14
7.3.10 Module 102, Authorization Code Module ............................................. 7-14
7.3.11 Module 103, Account Code/Customer Dialed Account Recording
(CDAR) Module.....................................................................................7-14
7.3.12 Module 104, Trunk Identification Module.............................................7-15
7.3.13 Module 105, Message Detail Recording (MDR) ...................................7-15
7.3.14 Module 164, E.164/X.121 Number Module ..........................................7-15
7.3.15 Module 198, Flex Module......................................................................7-15
7.3.16 Module 264, Quality of Service (QoS) (NDGR) ...................................7-15
7.3.17 Module 306, Originating Line Information Parameter (OLIP)..............7-15
7.3.18 Module 611, Generic Module ................................................................7-15
7.3.19 Module 612, Generic Module: Two Digits String Format.....................7-16
7.3.20 Module 613, Generic Module: Three Digits String Format...................7-16
7.3.21 Module 616, 5 Digit Information Module..............................................7-16
7.3.22 Module 719, Local Number Portability (LNP) Core Module................7-16
7.3.23 Module 720, Local Number Portability (LNP) Module.........................7-16
7.4 Module Number 164 ..........................................................................................7-16
7.4.1 E.164 Numbering Plan ...........................................................................7-17
7.4.2 X.121 Numbering Plan...........................................................................7-18
7.4.3 Generation of Module 164 .....................................................................7-18
7.5 Call Types, Structure Codes, and Modules ........................................................7-19
7.6 Configuration and Operation..............................................................................7-20
To avoid local time synchronization problems, Telica strongly recommends

setting the Plexus system clock to use GMT.
AMA Lite Reports Issue 2, January 12, 2004
7.1 Introduction
The PlexView Automatic Message Accounting (AMA) Lite application
and the PlexView Billing and Traffic System (BTS) works with the
Plexus 9000 switch to convert Call Detail Records (CDRs to an AMA
record format. For more detail about AMA Lite or BTS, refer to these
sections of this manual.
7.2 CDR and AMA Lite Formats

The Plexus 9000 sends the server the CDR data every five seconds from
the circular buffer, where they are converted to AMA files via the
converter. After delivery to server, the data records are formatted to AMA
and saved into AMA files.
7.2.1 CDR Data Prior to Conversion

The Plexus 9000 CDRs support the Billing Automatic Message
Accounting Format (BAF) call types and structures, and are based on
Telcordia’s AMA architecture (GR-1100). Currently, the AMA Lite and
BTS applications supports the AMA call types from the switch that are
listed in Table 7-A.
The AMA Lite billing and BTS applications follow the AMA record
formatting rules as defined in Telcordia’s GR-1100. Generally, based on
dialing pattern or type of call (i.e. 800 service) and connection type (i.e.
access tandem to end office, end office to access tandem, access tandem to
IXC, etc.), a call type is determined. Using the call type, the Plexus 9000
will map the call to an underlying structure code, which is a four-character
numeric field. Refer to Table 7-A for a listing of all call types and the
structure codes and modules supported by each. Refer to Table 7-B for a
list of the structure codes and the associated call types.
In GR-1100, the structure codes define the group of fields that will be
provided for this call and, for each field, GR-1100 provides a table number
that further defines the content of the field. In addition, depending on the
specific conditions of the call, the Plexus 9000 will append modules that
will provide additional information (i.e. on long duration calls module 22
is appended). Again, GR-1100 documents the group of fields contained
within each module and provides a table number that further defines the
content of each field.
7-2 Telica, Inc.

Table 7-A. Call Types Supported by the Plexus 9000

Call Structure
001 Detailed Message Rate, Timed, w/ MBI. 0020 022
002 Message Rate, Timed, w/ MBI. 0020 022
003 Detailed Message Rate, Untimed, w/ MBI. 0020 022
004 Message Rate, Untimed, w/ MBI. 0020 022
006 Station Paid 0001 021, 022, 720
009 411 Directory Assistance 0028 022
031 Call Forwarding 0096, 0614 022
033 555 – Directory Assistance 0028 022
036 Terminating Study Record 0079 022
037 Terminating SLUs Overflow Counts 9003
047 Default Advanced Intelligent Network 0220 021, 022, 025, 027,
(AIN) 029, 040, 104, 164
067 Default Advanced Intelligent Network 0001 021, 022, 720
(AIN)
074 Free Call 0001 022
088 Non-Directory Assistance 555 Call 0001 021, 022, 720
110 Inter-LATA station paid 0625 022, 104, 164
119 Terminating Access record 0625 022, 104, 164
123 CLASS Feature Activation 1030 022
141 InterExchange Carrier (IC/IXC) Number 0360 022
Service
142 Local Exchange Carrier (LEC) Number 0364 022
Service
159 Message Detail Recording (MDR) Data 0001, 0079, 102, 103, 105
0500
264 Calling Identity Delivery Record 0110
330 CLASS Feature 110, 1030 49
710 Originating Toll AMA Recording (Vendor 0625 022, 104, 164
Specific)
720 Connecting Network Access Incoming 0625 022, 104, 164, 720
Record
721 Default Local Number Portability (LNP) 0500 022, 104, 164, 720
Telica, Inc. 7-3

Table 7-B. Structure Codes

Structure Code Call Types
0001 006, 067, 074, 088
0020 001, 002, 003, 004
0028 009, 033
0079 036
0110 264, 330
0220 047, 159
0360 141
0364 142
0500 721
0625 110, 119, 710, 720
1030 123, 330
7.2.2 AMA Files After Conversion

The default for saving AMA files is 24 hours, but you can configure the
frequency with which files are saved in minutes. The file is also available
on the server for a configurable number of days before it is deleted. The
maximum number of days is 62. The larger the number, the more disk
space is required. The frequency and the archive parameters are
provisioned in the ama.conf file.
All converted CDR information is captured in an AMA master record.

Each record is pre-pended with a proprietary header. Refer to Table 7-C
for the fields in the header.
Refer to GR-1100 CORE, Billing Automatic Message Accounting Format

(BAF) Generic Requirements for value descriptions of the fields or to the
comparable fields listed in the PlexView ASCII Billing Server (ABS)
chapter of this guide.
7-4 Telica, Inc.

Table 7-C. Header of AMA Lite Record

Field Description Table
* * * *STRUCTURE CODE 9999* * * * header record
recDes Defines length of record header. 000
hexId Identifies number of errors in header. 00
structCode The structure code is always 9999C and may be 0
prefaced with a “0” or a “4”. “0” indicates that no
modules are attached; “4” indicates that modules
are attached.
callType This is always call type 999C. 1
version Identifies version number in the format of 803
MMMmm, where M is the major release number
and m is the minor.
create_date Identifies creation date. 6
create_time Identifies creation time. 18
close_date Identifies the date when the file is closed. If file 6
was not properly closed, it will be “FFFFFC”.
close_time Identifies the time when the file is closed. If file 18
was not properly closed, it will be “FFFFFFFC”
records Identifies the number of records when file is 805
closed. If file was not properly closed, it will be
“FFFFFFFFFC”
Table 7-D. Fields in the AMA Lite Record

GR-1100
Field Description Table # # of Char.
* * * *STRUCTURE CODE 0625* * * *
recDes
hexId
structCode
callType
sensorType 2 4
sensorId 3 8
rcrdOfficeType 4 4
rcrdOfficeId 5 8
date 6 6
timingInd 7 6
studyInd 8 8
answerInd 9 2
servObsrvdTrafSampled 10 2
operatorAction 11 2
serviceFeature 12 4
origNPA 13 4
origNumber 14 8
overseasInd 15 2
termNPA 16 6
termNumber 17 8
answerTime 18 8
elapsedTime 19 10
icIncPrefix 57 6
Telica, Inc. 7-5

GR-1100
carrierConnectDate 6 6
carrierConnectTime 18 8
carrierElapsedTime 19 10
icIncCallEventStatus 58 4
trunkGroupNumber 83 6
routingIndicator 59 2
dialingInd 85 2
aniInd 60 2
* * * *MODULE 104* * * *
moduleCode 4
trunkIdentNumber 10
* * * *MODULE 164* * * *
moduleCode 4
numberIdentity 2
countryCodeOrDNIC 6
sigDigitsInNext 4
digits 16
* * * *TERMINATOR MODULE CODE zero * * * *
The master record contains the fields listed in Table 7-E. Refer to GR-
1100 CORE, Billing Automatic Message Accounting Format (BAF)
Generic Requirements for value descriptions of the fields or to the
comparable fields listed in the PlexView ASCII Billing Server (ABS)
chapter of this guide.
Table 7-E. List of Fields in the Master Record

GR-1100
Sensor Type 2 4
Sensor Previous Output Ind
Sensor Identification 3 8
Recording Office Type 4 4
Recording Office Previous Output Ind
Recording Office Identification 5 8
Connect Date [3] 6 6
Connect Time 18 8
Timing Indicator [3] 7 6
Study Indicator[7] 8 8
Called Party Off-Hook Indicator 9 2
Service Observed/Traffic Sampled 10 2
Operator Action 11 2
Service Feature 12 4
Originating NPA [2] 13 4
Originating Number [4] 14 8
Dialed NPA [2] 13 4
Dialed Number [4] 14 8
Destination Overseas (International Call) Indicator 15 2
Destination Number Plan Area (NPA) [3] 16 6
7-6 Telica, Inc.

GR-1100
Destination Number [4] 17 8
Elapsed Time 19 10
IC/INC Prefix [3] 57 6
Carrier Connect Date [3] 6 6
Carrier Connect Time [4] 18 8
Carrier Elapsed Time 19 10
IC/INC Call Event Status 58 4
trunkGroupSigTypeInd
Trunk Group Number 83 6
Routing Indicator 59 2
Dialing And Presubscription Indicator 85 2
ANI/CPN Indicator 60 2
Revenue Accounting Office (RAO) Number 46 4
Local Access Transport Area (LATA) 197 4
WATS Indicator 28 2
Wats Band or Message billing Index 29 4
WATS Administration 30 6
Data Capabilities Indicator 41 4
Information Transfer Rate Indicator 42 4
Terminating Company 56 4
Completion Indicator 280 4
Service Logic Identification [5] 77 10
Numbering Plan Area (NPA) 13 4
Directory Number 14 8
Usage count 130 6
Date 6 6
Time 18 8
Class Feature Code 415 4
Call Count -Information delivered 803 6
Call Count -Information Anonymous/Unavailable 803 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
CLASS Functions 330 4
CLASS Feature status 331 4
Screening list size of selective call forwarding or
802 4
selective call acceptance
screening list size of selective call rejection 802 4
screening list size for distinctive ringing/call waiting 802 4
forward to overseas Indicator 15 2
forward to NPA 16 6
forward Number 17 8
activation date 18 8
activation time 18 8
deactivation date 6 6
deactivation time 18 8
Telica, Inc. 7-7

7.3 Module Inclusion Rules

This section contains the module inclusion rules that must be met in order
for the data fields of a specific module to be appended to the AMA Billing
Server master record. The modules supported by the AMA Billing Server
are listed in Table 7-F.
Table 7-F. Module Numbers and Descriptions

Module Description
021 Carrier Access – Originating
022 Long Duration Connection
025 Circuit Release Module
027 Business Customer ID Module
029 Alternate Billing Number Module
040 Digits Module
049 Calling Name/Number Delivery Module
068 Called Directory Number (DN) Descriptor
101 Digits Dialed Module
102 Authorization Code Module
103 Account Code/Customer Dialed Account Recording (CDAR)
Module
104 Trunk Identification Module
105 Message Detail Recording (MDR)
164 E.164/X.121 Number Module
198 Flex Module
264 Quality of Service (QoS) (NDGR)
306 Originating Line Information Parameter (OLIP)
611 Generic Module
612 Generic Module: Two Digits String Format
613 Generic Module: Three Digits String Format
616 5 Digit Information Module
719 Local Number Portability Core Module
720 Local Number Portability (LNP) Module (NDGR)
7.3.1 Module 021, Carrier Access – Originating

This module contains fields necessary to identify originating
Interexchange Carrier/International Carrier (IC/INC) access, including
carrier identification and the elapsed time of the carrier’s access to the
Local Access and Transport Area (LATA) network. However, in certain
situations, the Automatic Number Identification/Calling Party Number
(ANI/CPN) indicator is needed for the terminating end of a call (as in an
SS7 Environment), and this module may be used to identify terminating
IC/INC access.
7-8 Telica, Inc.

7.3.2 Module 022, Long Duration Connection

This module contains fields necessary for time stamping long duration
connection records. Present date and present time refer to the moment
when the long duration connection is output or to the moment of
disconnect.
A long duration connection is an intra-network or inter-network call on

which, at a scheduled record generation time, both calling and called
parties remain off-hook ("connected" for carrier timing) and the elapsed
time and/or carrier elapsed time of the call already exceeds 1440 minutes
(24 hours).
For intra-network calls, the requirements for long duration connection

processing are as follows:
1. First record of a long duration connection must be generated at

the first scheduled record generation time after the elapsed time
of the call exceeds 1440 minutes.
2. First record must be generated as a conventional record that
must contain the Connect Date, Connect Time, and Elapsed
Time fields, except the Timing Indicator field must contain a
“1” in character 3, indicating the start of a long duration
connection.
3. Elapsed time reported in the first record must equal the interval
from call connect time to the time when the record is
generated.
4. Determine inaccuracy compensation and the variable
determination made for the Elapsed Time field in the first
record.
5. Continuation record must be generated at each record
generation time that occurs between the time that a call’s first
record is made and the call disconnects.
6. Continuation record of a long duration connection must contain
Connect Date and Connect Time fields and a Long Duration
Connection Module.
7. Timing Indicator field of a continuation record must contain a
“2” in character 3, indicating a continuation record.
8. Elapsed time reported in a continuation record must be the
interval from the time when the previous record was generated
to either the time the current record is generated or the time the
call disconnects.
Telica, Inc. 7-9

Record generation requirements for long duration connections are shown

in Figure 7-1.
G1 G2 G3 Gk
Cell
Connect Disconnect
Elapsed Time > 24 hours
Actual time Long duration call "Continuation" "Continuation" "Continuation"

of call recognized. First record output. record outpu for record outpu for
connect record computed. Duration covers G to G . G to disconnect.
computed Duration covers interval G2 to G3 . k-1 k k
and stored interval from call
pending connect to G2
disconnect. including
determinate
inaccuracy
compensation and P504-AA
variable inaccuracy 12-06-01
allowance.
Key: G denotes the scheduled record generation time.
Figure 7-1. Long Duration Call Sample
For inter-network calls, the requirements for intra-network calls apply.

The following requirements for carrier elapsed time recording also apply.
1. Long duration connection requirements (1 – 8 above) must be
applied to inter-network calls.
2. First record of a long duration connection for an inter-network
call must be generated at the first scheduled record generation
time after the carrier elapsed time (instead of elapsed time) of
the connection exceeds 1440 minutes.
3. First record for an inter-network call must be generated as a
conventional record that must contain Carrier Connect Date,
Carrier Connect Time, and Carrier Elapsed Time fields, except
the Timing Indicator field must contain a “1” in character 3,
indicating a start of a long duration connection.
4. Carrier Elapsed Time field of the first record for an inter-
network call must be equal to the interval from carrier connect
time to the time when the record is generated.
7-10 Telica, Inc.

5. Determinate inaccuracy compensation and the variable

determination made for the Carrier Elapsed Time field in the
first record for an inter-network call.
6. Continuation record of a long duration connection for an inter-
network call must contain Carrier Connect Date and Carrier
Connect Time fields which must include the date and time of
the original call set up, and Long Duration Connection Module
(Present Day and Present Time fields).
7. Timing Indicator field of a continuation record for an inter-
network call must contain a “2” in character 3, indicating a
continuation record.
8. Carrier Elapsed Time field for a continuation record for an
inter-network call must be the interval from the time when the
previous record was generated to either the time the current
record is generated or the time the call disconnects.
Forward changes in time (for example, 11:30 p.m. to 12:30 a.m. of the
next day with midnight as the record generation time) and backward
changes in time (for example, 12:30 a.m. to 11:30 p.m. of the preceding
day), can span record generation time.
When a forward change in time spans a record generation time, the switch
must generate all records that already have an elapsed time (or carrier
elapsed time) exceeding 1440 minutes. Also, the switch must generate all
continuation records that would have occurred at the spanned record
generation time.
An exception occurs when the forward change in time that spans a record
generation time follows a backward change in time that spanned the same
record generation time. In this case, records should not be generated.
When a backward change in time spans a record generation time, the
switch must not generate any first and continuation records at the record
generation time following the time change.
AMA data should be generated for a long duration connection as

described in the following example.
A call originates at 8:00 p.m. on day 1 and disconnects at 2:00 p.m. on day
4. The time designated by the LEC for record generation each day is 3:00
a.m. At 3:00 a.m. on the second day, no record is generated because the
elapsed time is still less than 1440 minutes. Three records should be
generated as follows:
Telica, Inc. 7-11

1. The first record is generated at 3:01:10 a.m. on the third day,

with an elapsed time of 1861 minutes, 10 seconds. The record
is generated after the scheduled record generation time due to
processing or scheduling delays in the switch.
2. The first continuation record is generated at 3:02:00 a.m. on the
fourth day with an elapsed time of 1440 minutes, 50 seconds,
which is the interval from 3:01:10 a.m. of the third day to
3:02:00 a.m. of the fourth day. Again, the switch had
processing or scheduling delays, causing the record to be
generated after the scheduled record generation time.
3. The second continuation record is generated at disconnect at
2:00:00 p.m. on the fourth day with an elapsed time of 658
minutes, 0 seconds.
7.3.3 Module 025, Circuit Release Module

This module contains the fields necessary to identify the date and time of
circuit (or trunk) release.
If this module is included in a BAF record format generated for intra-

network calls on which the called party off-hook is not detected, the
Circuit Date and Time fields indicate the date and time of circuit (or trunk)
release. The Called Party Off-Hook Indicator field contains a “1”
(indicating called party off-hook is not detected). The Elapsed Time field
is set to “0” and the Connect Date and Time fields indicate the time of
circuit (or trunk) seizure.
This module is not used with carrier access calls, nor should it be used
with Operator Services System (OSS) calls.
7.3.4 Module 027, Business Customer ID Module

This module is included in a record when, as a result of the service, the
record must contain a business customer identification. The Business
Customer Identification is populated in the Business Customer
Identification field (right-justified) and unused characters are populated
with zeroes.
This module can be used, for example, with Private Virtual Network
(PVN) calls. The Business Customer ID module is included in the BAF
record if the response message from the Service Control Point (SCP)
contains a Business Customer Identification number. If a Business
Customer Identification number is not included in the response message,
the Business Customer Identification Module is not included in the record.
7-12 Telica, Inc.

In an AIN BAF record, the Business Customer ID Module is recorded

instead of this module when the response message from the SCP to the
SSP contains an AMA sequence number parameter in addition to the
AMA Business Customer ID parameter.
7.3.5 Module 029, Alternate Billing Number Module

This module is included in a BAF record when an alternate billing number
is needed. This billing number populates the Alternate Billing Number
field, is right-justified, and unused characters are populated with zeroes.
This module can be used, for example, with PVN calls. The Alternate
Billing Number module is only included in the BAF record for a PVN call
if the response message from the SCP contains a billing number.
In an AIN BAF record, the Alternate Billing Module is recorded instead of

this module when the response message from the SCP to the SSP contains
an AMA Sequence Number parameter in addition to the AMA Alternate
Billing Number parameter.
7.3.6 Module 040, Digits Module

This module is used to record digits used during an AIN call. Up to 24
significant digits can be recorded. This module is only appended to
Structure Codes 0220 and 0221, and it may be repeated in the same AMA
record.
The Digits Module is recorded instead of this module when recording

SCP-provided digits and the response message from the SCP to the SSP
also contains an AMA Sequence Number parameter.
7.3.7 Module 049, Calling Name/Number Delivery Module

This module provides the Count of Name-Only and Count of Number-
Only fields. The Count of Name-Only field counts the number of times a
calling name appears in the information delivered to the customer. For
each count, an "anonymous" or "unavailable" indication is sent in place of
the calling number. - The Count of Number-Only Deliveries field counts
the number of times a calling number appears in the information delivered
to the customer. For each count, an "anonymous" or "unavailable"
indication is sent in place of the calling name.
Telica, Inc. 7-13

7.3.8 Module 68, Called Directory Number (DN) Descriptor

This module contains one field that describes the special billing potential
of the called Directory Number (DN). If the called DN requires special
treatment by the Revenue Accounting Office (RAO) in the billing process,
this module will be appended to the Automatic Message Accounting
(AMA) data structure normally generated for that call. Examples of
features that use this module are the CLASS features Automatic Callback
(AC) and Automatic Recall (AR).
7.3.9 Module 101, Digits Dialed Module

This module is currently used in Message Detail Recording (MDR).
When the actual number to which the call is routed differs from the
number dialed by the originator of the call (as seen at the switching system
at which the MDR data record is generated), the actual digits received on
the originating facility populate the digits dialed fields. The Access Code
for private network calls (i.e., Tie Trunk calls) contains the digits dialed to
indicate the particular type of call (e.g., a code dialed for Wide Area
Telecommunications Service (WATS) access). The dialed Access Code is
right-justified in Table 803 and unused characters are filled with zeros. For
public network calls dialed using prefix digits for access to the public
network (i.e., "dial 9" calls), the prefix digits dialed before the public
directory number populate the Access Code field, are right-justified, and
unused characters are filled with zeros.
7.3.10 Module 102, Authorization Code Module

This module is used to provide Message Recording Detail (MDR). If an
authorization code is received on a call using the Authorization Codes for
the Automatic Flexible Routing (AFR) feature, the Authorization Code
digits populate Table 126. If the dialed Authorization Code exceeds 15
digits, only the first 15 digits dialed populate this field. If the code
contains fewer than 15 digits, it is right-justified, and unused characters
are filled with zeros.
7.3.11 Module 103, Account Code/Customer Dialed Account Recording (CDAR)

Module
This module contains account code or Customer-Dialed Account
Recording (CDAR) information. If both the account and CDAR features
are used on the same call, the account code information populates the
module, not the CDAR information. Account code information is similar
to CDAR information except for the point in the customer dialing pattern
when the account code/CDAR information is provided.
7-14 Telica, Inc.

7.3.12 Module 104, Trunk Identification Module

This module captures trunk identification information for incoming and
outgoing calls. Module 104 appears when a trunk-side connection occurs.
For example, if a call originates from a PRI and routes out over an SS7
trunk, one module 104 will appear on the record with the SS7 trunk
information. If the call is switched from one SS7 trunk to another SS7
trunk, two module 104s will appear on the record with the incoming and
outgoing trunk information. If a call originates PRI and terminates via
PRI from the same switch, no module 104 appears on the record.
7.3.13 Module 105, Message Detail Recording (MDR)

This module is included in every Message Detail Recording (MDR)
record. The MDR customer for whom the MDR data is intended is
uniquely identified in Table 87. The facility types in Table 246 are
recorded from the perspective of the switch that is creating the MDR data
record.
7.3.14 Module 164, E.164/X.121 Number Module

This module provides the means to record lengthy numbers that cannot be
recorded in the structure applicable to the call. Refer to section 7.4,
Module Number 164, for details concerning module 164.
7.3.15 Module 198, Flex Module

This module is used to hold a field that has a variable length. Table 575 is
a context identifier (i.e., originating address, terminating address) that
defines the tables that follow Table 575.
7.3.16 Module 264, Quality of Service (QoS) (NDGR)

Module Code 264 is used to record the Network Latency and Inter-arrival
jitter that are associated with Quality of Service (QoS). It includes the release
cause indicator, the number of packets sent, the number of packets
received, the number of packets lost, the number of octets sent, the
number of octets received, the inter-arrival jitter and the amount of
network latency.
7.3.17 Module 306, Originating Line Information Parameter (OLIP)

This module identifies the class of service of the originating line. It can
also be used to record a unique class of service that can identify various
services offered by Local Exchange Carriers (LECs).
7.3.18 Module 611, Generic Module

This is a generic, general-purpose module. The Generic Context Identifier
field (Table 237) defines the parsing rules and the type of data to be stored
in the Digits String field (Table 126).
Telica, Inc. 7-15

7.3.19 Module 612, Generic Module: Two Digits String Format

Context Identifier field, (Table 237) defines the number of characters in
the Digits String 1 (Table 126) and Digits String 2 (Table 126) fields. The
Digits String fields identify the IOM typeand slot.
7.3.20 Module 613, Generic Module: Three Digits String Format

Context Identifier field (Table 237) defines the number of digits to be
stored in the Digits String 1 (Table 126), Digits String 2 (Table 126) fields
and Digits String 3 (Table 126). The Digit String 1 and 2 fields are used
to identify IP addresses and Digit String 3 is used to identify the local and
remote ports, the Codec and the Fax indicator.
7.3.21 Module 616, 5 Digit Information Module

This module is a general purpose, vendor specific, 5 digit information
module.
7.3.22 Module 719, Local Number Portability (LNP) Core Module

This module provides the LRN when applicable for calls in the LNP
environment. Module 719 is now obsolete. Telica has replaced it with
Module 720.
7.3.23 Module 720, Local Number Portability (LNP) Module

This module is used to convey information pertinent to rating and billing
of calls to and/or from ported numbers in environments with LNP.
7.4 Module Number 164

The E.164/X.121 Number Module (Module Code 164) defines specific
information gathered from the CDR, only if the CDR call type and call
conditions dictate that Module 164 needs to be appended to the CDR.
The term call is used in this section to indicate a subscriber’s access

to a system that potentially causes generation of a BAF record.
Calls could be, for example, Plain Old Telephone Service (POTS)
calls or data link access to a computer.
7-16 Telica, Inc.

Specifically, Module 164 and its associated BAF tables (fields) enable the
AMA Billing Server to record longer length addresses. The module is
appended to the CDR in accordance with the BAF data structures when
conditions of the call require recording longer length addresses than the
structures can accommodate. The current international E. 164 number
format records numbers of up to 12 digits. The module includes X.121 in
case it is necessary to record long length data network addresses.
Module 164 must be appended to the BAF structure being generated when
either (or both) of the following conditions are met:

number field (defined in section 8.3.1, R1-50) exceeds 10
digits. If it is 10 or fewer digits (not including incoming
international calls), it is recorded in the originating number

number fields (section 83.1, R1-50) exceeds 12 digits. If it is
12 or fewer digits, it is recorded in the terminating number
Module 164 must contain the following ordered list of fields:
− Module Code
− Number Identify
− Country Code or Data Network Identification Code
− Significant Digits in the Next Field(s)
− Number
7.4.1 E.164 Numbering Plan

The E.164 numbering plan, as derived from ITU-T Recommendation
E.164 and TR-TSY-000448, defines the currently used structure of an
international telephone number. According to Recommendation E.164,
such numbers follow the CC+N(S)N format where:
CC= Country Code – Identifies the destination country and can

vary between 1 and 3 digits.
N(S)N = National (Significant) Number – Identifies the destination

termination, and the maximum N(S)N length is 11 digits.
CC+N(S)N = maximum of 12 digits.
The above applies until “Time T” (year-end 1996). After that, CC+N(S)N
will be a maximum of 15 digits, which results in a maximum N(S)N of 14
digits since no changes are planned for the structure of a CC.
Telica, Inc. 7-17

The North American Numbering Plan (NAPN) is the numbering plan

currently used in the United States. It meets the requirements set forth in
the ITU-T Recommendation E.164.
7.4.2 X.121 Numbering Plan

The International Numbering Plan for Public Data Networks (PDNs) is
documented in ITU-T-Recommendation X.121. An international
/internetwork data number consists of the Data Network Identification
Code (DNIC) followed by the Network Terminal Number (NTN). The
DNIC consists of a three-digit Data Country Code (DCC) followed by a
network digit. DCCs are ITU-T administered; however, they are not the
same country codes specified in Recommendation E.164. The DCC
identifies a country; the network digit identifies a specific data network
within the country identified by the DCC. The DCC in conjunction with
the network digit can identify up to ten PDNs. Multiple DCCs may be
assigned to a country where more than ten PDNs exist. Recommendation
X.121 specifies a maximum length of ten digits for the NTN. No
minimum NTN length is specified. The format of the NTN is determined
by the network provider that is identified by the DNC. Although the most
commonly discussed usage of the X.121 numbering plan is in connection
with packet data networks, the plan is also applicable to circuit-switched
data networks that may choose to use it. X.121 numbers are included in
the E.164/X.121 Number Module (Module Code 164) to cover the
possibility of a future increase in length of NTN.
7.4.3 Generation of Module 164

Module 164 is used when the originating and/or terminating number
contains too many digits to record in the BAF structure associated with the
call. Module 164 is also used when the system cannot determine the
Country Code form the originating number information, regardless of the
length of the originating number. The module only records one number,
so if both originating and terminating number contain too many digits for
conventional recording, two modules should be appended – one for the
originating number and one for the terminating number.
The Network Element (NE) generates Module 164 and appends it to the
BAF structure generated for a call when the following conditions exist:

number fields exceeds 10 digits. The originating number fields
this requirement refers to are BAF Tables 13, 14, 172 and 173,
listed in GR-1100-CORE.
7-18 Telica, Inc.

− The originating number to be recorded is for an incoming

international call. Module 164 is used regardless of the length
of this number.

number fields exceeds 12 digits. The terminating number
fields this requirement refers to are BAF tables 15, 16, 17, 174,
and 175, listed in GR-1100-CORE.
7.5 Call Types, Structure Codes, and Modules

A call type, together with a call type code, represents the
service/technology provided to a customer or carrier. The call type code
in a BAF record provides guidance to accounting systems for processing
the record. Call types are determined by the type of service.
A structure is a set of eight common data fields, followed by a group of

fields required by the type of service or technology for which the data are
recorded. Each structure is a unique, ordered set of fields identified by a
structure code (the third data field in the AMA master record). Every
BAF structure contains a common set of eight data fields. Structure codes
are determined by call type.
In Table 7-G, all data fields for each particular structure code are listed.
The eight common data fields, common to every structure code, are listed,
but they will not be included in the Structure Code Fields column in
Table 7-G. Therefore, a structure code listed in Table 7-G contains all
data fields listed in the Structure Code Fields column for that structure
code, as well as the eight common data fields provided in the following
list. The letter appearing beside most entries listed identifies which field
description to reference in the lettered list in section 5, AMA-Format
Master Record Field Descriptions, of this document.
The eight common data fields shared by most structure codes are:
− Record Descriptor Word

− Hexadecimal Identifier
− Structure Code (b)
− Call Type (a)
− Sensor Type (c)
− Sensor Identification (d)
− Recording Office Type (e)
− Recording Office Identification (f)
Telica, Inc. 7-19

Modules are predefined sets of data fields that may be appended to a

structure according to the service/technology rendered, or to report
information connected with specific conditions. Modules are often
referred to by their code number. Modules have fixed names that indicate
the meaning of the data they contain or the service or capability for which
they are used. They are determined by the call type and the conditions of
the call. Modules are appended to the end of the record, after the structure
code fields.

To use the AMA Lite or BTS successfully with the Plexus 9000, you must
first meet specific AMA Lite server platform requirements and then
configure the AMA Lite or BTS on the Sun server to communicate with
the Plexus 9000, and configure the Plexus 9000 to communicate with the
AMA Lite or BTS. The procedures (NTP-031) for configuring the billing
and the Plexus 9000 are found in volume 2 of the Plexus 9000 Installation
and Operation Manual.
7-20 Telica, Inc.

Table 7-G. Call Types, Modules and Structure Code 0625
110 Inter-LATA 021, 021 - Module Code ID, Eight common data fields, 1+NXX+ XXXX,
Station Paid 104, IC/INC Prefix, Connect Date (g), 0-,
164, Carrier Access Date (tt), Timing Indicator (h), 0+NXX+ XXXX,
720 Carrier Access Time (uu), Study Indicator (i), 1+ NPA+555+ 1212,
Elapsed Time (vv), Called Party Off-hook Indicator (j), 101XXXX+ 0+…,
IC/INC Call Event Status (ww), Service Observed/Traffic Sampled (k), 101XXXX+00-,
Trunk Group Number (xx), Operator Action (l), 101XXXX+ 0/1+…
Routing Indicator (yy), Service Feature (m), (originating),
Dialing and Presubscription Indicator (zz), Originating NPA (n), 101XXXX+ 01/011+…
ANI/CPN Indicator (aaa) Originating Number (o), (orig),
104 – Module Code ID, Overseas (International Call) Indicator (p), 01/011+7 to 18-digit,
Trunk ID Terminating NPA (q), 800 call (non-SSP),
164 – Module Code, Terminating Number (r), 1+500+7-digits,
Number Identity (rrr), Connect Time (s), 1+700+7-digits,
Country Code or Data Network ID Code (ttt), Elapsed Time (t), 1+900+7-digits
7-21
119 Terminating 021, 021 - Module Code ID, Eight common data fields, Terminating exchange
Access Record 104, IC/INC Prefix, Connect Date (g),
164, Carrier Access Date (tt), Timing Indicator (h),
7-22
710 Originating Toll Eight common data fields,
AMA Recording Connect Date (g),
(Vendor Specific) Timing Indicator (h),
Study Indicator (i),
Called Party Off-hook Indicator (j),
Service Observed/Traffic Sampled (k),
Operator Action (l),
Service Feature (m),
Originating NPA (n),
Originating Number (o),
Overseas (International Call) Indicator (p),
Terminating NPA (q),
Terminating Number (r),
Connect Time (s),
Elapsed Time (t),
IC/INC Prefix (u),
Carrier Connect Date (v),
Carrier Connect Time (w),
IC/INC Call Event Status (y),
Trunk Group Number (z),
Routing Indicator (aa),
Dialing and Presubscription Indicator (bb),
ANI/CPN Indicator (cc)
7-23
720 Connecting 021, 021 - Module Code ID, Eight common data fields,
Network Access 104, IC/INC Prefix, Connect Date (g),
Incoming Record 164, Carrier Access Date (tt), Timing Indicator (h),
7-24
Table 7-H. Plexus 9000 AMA Record Mapping to Telcordia GR-1100
# table Structure Code
Field Description
Char. # 0001 0020 0027 0028 0079 0220 0360 0364 0500 0625 0631 0645 0653 0656 0664 9003 0110 1030 0614 0096
Record Descriptor Word 000 X X X X X X X X X X X X X X X X X X X X
Hexadecimal Identifier 2 00 X X X X X X X X X X X X X X X X X X X X
Structure Code 6 0 X X X X X X X X X X X X X X X X X X X X
Call Type Code 4 1 X X X X X X X X X X X X X X X X X X X X
Sensor Type 4 2 X X X X X X X X X X X X X X X X X X X X
Sensor Previous Output Ind
Sensor Identification 8 3 X X X X X X X X X X X X X X X X X X X X
Recording Office Type 4 4 X X X X X X X X X X X X X X X X X X X X
Recording Office Previous
Output Ind
Recording Office Identification 8 5 X X X X X X X X X X X X X X X X X X X X
Connect Date [3] 6 6 X X X X X X X X X X X X X X X X X X X
Connect Time 8 18 X X X X X X X X X X X X X X X X X X X
Timing Indicator [3] 6 7 X X X X X X X X X X X X X X X X
Study Indicator[7] 8 8 X X X X X X X X X X X X X X X X
Called Party Off-Hook
2 9 X X X X X X X X X X X X X X
Indicator
Service Observed/Traffic
2 10 X X X X X X X X X X X X
Sampled
Operator Action 2 11 X X X X X X X X X X X X X
Service Feature 4 12 X X X X X X X X X X X X X X X X
Originating NPA [2] 4 13 X X X X X X X X X X X
Originating Number [4] 8 14 X X X X X X X X X X X
Dialed NPA [2] 4 13 X X
Dialed Number [4] 8 14 X X
Destination Overseas
2 15 X X X X X X X X X X X
(International Call) Indicator
Destination Number Plan
6 16 X X X X X X X X X X X X X
Area (NPA) [3]
Destination Number [4] 8 17 X X X X X X X X X X X X X
Elapsed Time 10 19 X X X X X X X X X X X X X X X X
IC/INC Prefix [3] 6 57 X X X X X X X
Carrier Connect Date [3] 6 6 X X X X X X
7-25
Field Description
Char. # 0001 0020 0027 0028 0079 0220 0360 0364 0500 0625 0631 0645 0653 0656 0664 9003 0110 1030 0614 0096
Carrier Connect Time [4] 8 18 X X X X X X
Carrier Elapsed Time 10 19 X X X X X X
IC/INC Call Event Status 4 58 X X X X X X
trunkGroupSigTypeInd
Trunk Group Number 6 83 X X X X X X X
Routing Indicator 2 59 X X X X X X X
Dialing And Presubscription
2 85 X X X X
Indicator
ANI/CPN Indicator 2 60 X X X X
Revenue Accounting Office
4 46 X X
(RAO) Number
Local Access Transport Area
4 197 X X
(LATA)
WATS Indicator 2 28 X X
Wats Band or Message billing
4 29 X X
Index
WATS Administration 6 30 X X
Data Capabilities Indicator 4 41 X
Information Transfer Rate
4 42 X
Indicator
Terminating Company 4 56 X
Completion Indicator 4 280 X
Service Logic Identification [5] 10 77 X
Numbering Plan Area (NPA) 4 13 X X
Directory Number 8 14 X X
Usage count 6 130 X
Date 6 6 X X
Time 8 18 X X
Class Feature Code 4 415 X X X
Call Count -Information
6 803 X
delivered
Call Count -Information
6 803 X
Anonymous/Unavailable
Activating NPA 4 13 X X X
Activating Number 8 14 X X X
Far-end Overseas indicator 2 15 X
7-26 Telica, Inc.

Field Description
Char. # 0001 0020 0027 0028 0079 0220 0360 0364 0500 0625 0631 0645 0653 0656 0664 9003 0110 1030 0614 0096
Far-end NPA 6 16 X
Far-end Number 8 17 X
CLASS Functions 4 330 X
CLASS Feature status 4 331 X
Screening list size of selective
call forwarding or selective 4 802 X
call acceptance
screening list size of selective
4 802 X
call rejection
screening list size for
4 802 X
distinctive ringing/call waiting
forward to overseas Indicator 2 15 X X
forward to NPA 6 16 X X
forward Number 8 17 X X
activation date 8 18
activation time 8 18
deactivation date 6 6 X
deactivation time 8 18 X
7-27
7-28 Telica, Inc.
8. Traffic Statistics Reports
8.1 Introduction ..........................................................................................................8-1

8.2 Types of Statistics and Reports ............................................................................8-2
8.2.1 Types of Statistics ....................................................................................8-2
8.2.2 Types of Reports ......................................................................................8-3
8.2.2.1 Busy Hour ....................................................................................8-3
8.2.2.2 Peg Counts....................................................................................8-5
8.2.2.3 Trunk Group Hold Time ............................................................8-10
8.2.2.4 Traffic Centum Call Seconds (CCS)..........................................8-11
8.2.2.5 ASCII CDR Report ....................................................................8-22
8.2.2.6 ASR Report ................................................................................8-27
8.3 Installation and Configuration............................................................................8-29
8.3.1 Platform Requirements...........................................................................8-29
8.3.1.1 TCA Server Platform Requirements ..........................................8-29
8.3.1.2 BTS Server Platform Requirements...........................................8-29
8.3.2 Configuration .........................................................................................8-29
8.3.2.1 TCA............................................................................................8-29
8.3.2.2 BTS.............................................................................................8-30
8.1 Introduction
The PlexView Traffic Collection Application (TCA) and the PlexView
Billing and Traffic System (BTS) work in conjunction with the Plexus
9000 to capture information about every call, and to process that
information into statistical data. The statistical data is tracked for busy
hour information, peg counts, trunk group hold time, and traffic Centum
Call Seconds (CCS).
Up to eight Plexus 9000 switches can use the TCP/IP protocol to send a
Call Detail Record (CDR) for each attempted call to the BTS or to the
TCA via the Telica Statistical Data Server (TSDS). The TSDS stores this
information in binary format on the TCA server.
The Telica Statistical Analysis Application (TSAA) then extracts the

necessary information from the CDR and updates the call statistics and
traffic measurements accordingly, writing it to output text files, and
storing it on the server. The TSAA also works with the Billing and Traffic
System for Plexus software version 3.8 or greater.
Traffic Statistics Reports Issue 3, January 9, 2003
8.2 Types of Statistics and Reports

The Plexus 9000 provides two methods in which to retrieve statistics:
• Internally, by use of TL1 commands, for statistics maintained on
the Plexus.
• Externally, via automatic processing, from per call records that are
sent from the Plexus to an adjoining TCA application.
Each day a new output directory - STATS_yyyymmdd – is created under

tsaa output directory. And five subdirectories – CDR, BusyHour,
CCSReport, HoldTime and PegCount- are created for each report type.
(i.e., tsaa_<prefix>/Stats_20020301/ Busyhour/). Each report file is
created at the end of their Granularity period (configured in
tsaa_<prefix>.conf file), except Busy Hour report. Busy Hour report is
created at the beginning of next day (15 past midnight).
At any time during the process, you can open a previously existing peg
count, busy hour, traffic CCS, trunk group hold-time, or CDR file to view
and analyze the associated data.
8.2.1 Types of Statistics

Detailed statistics are available with the TCA and include:
• Peg counts of calls on each ISDN interface, directory number
(DN), and trunk group number
• Peg count of resulting call state (answered, ringing, busy, not
completed)
• Peg count of incoming and outgoing calls
• Number of provisioned circuits
• Busy Call Hour for each ISDN interface, directory number, and
trunk group number
• Erlang B calculations for each ISDN interface, directory number,
and trunk group number
• Average hold time for each trunk group
8-2 Telica, Inc.

8.2.2 Types of Reports

The TCA captures the statistics into these five types of files:
• Busy hour information
• Peg counts
• Trunk group hold time
• Traffic CCS
− By Trunk Group
− By ISDN Interface
− By GR303 Interface
− By CAS Trunk Group
− By SIP Trunk Group
− By BICC Trunk Group
• ASCII CDR reports
8.2.2.1 Busy Hour
8.2.2.1.1 Busy Hour Report

Busy hour information is necessary for sizing your trunk groups and ISDN
interfaces. The PlexView TCA captures busy hour records that contain
utilization expressed in Erlangs; trunk justification based on usage of the
group (Erlang B algorithm); and utilization expressed as a decimal. Busy
hour information is calculated to a 30-minute level of granularity, which is
the recommended and default setting. Busy hour reporting can be disabled
by setting Busy Hour Granularity to “0” in the tsaa_<prefix>.conf.file.
Busy hour parameters are captured based on the following criteria:

• All incoming trunks to a Plexus 9000 (daily usage of the system)
• Trunks groups (SIP, CAS, BICC and SS7) ))
• ISDN and GR303 interfaces
• Directory numbers (Optional) This is not supported in version
2.0.0.61 and above.
For each item listed above, the following information is calculated:

• Utilization expressed in Erlangs
• Trunk justification based on usage on the group (Erlang B
algorithm)
• Utilization expressed as a decimal
Telica, Inc. 8-3

8.2.2.1.2 Busy Hour Output

The Busy Hour file contains all the busy hour information for the day.
The naming convention for the file is:
<prefix>_STATS_BUSY_HOUR_yyyymmdd.txt
where <prefix> is the prefix defined in the tsaa_<prefix>.conf file, and
yyyymmddhhmm is the reported year/month/day. The format for this file
is:
version,month,day,year,hour,min,record_type,value,name,erlangs,
circuits,utilization
A sample of what the output would actually look like is provided below.
Field descriptions follow.
Sample Output (generated by Plexus 9000):
Boston_STATS_BUSY_HOUR_200201032200.txt
1.0,2,13,2001,15,55,4,1,NONAME,14.21,23,0.6180
1.0,2,13,2001,15,55,5,1234554321,NONAME,14.21,23,0.5922
1.0,2,13,2001,15,55,6,1,boston,14.21,23,0.5922
1.0,2,13,2001,0,0,7,0,NONAME,14.21,23,0.5922
Fields:
version Specifies the version of the application on the Plexus.
month, day, year, hour, min Describes the date and time of the record.
record_type Has the following values:
4 = busy hour info – ISDN interface
5 = busy hour info – directory number
6 = busy hour info – SS7 trunk group
7 = busy hour info – system (over the course of an entire
day, during non-busy hours, for the entire system)
8 = busy hour info – CAS trunk group
9 = busy hour info – BICC trunk group
10 = busy hour info – CAS interface
value The record_type’s value (i.e., ISDN interface ID, trunk
group number, etc.).
name The name of the trunk group for SS7 and CAS trunk
groups, name of the interface for CAS interface,
“NONAME” for ISDN, directory number, and system.
erlangs The Erlang calculation (refer to Traffic Collection
Application section of this manual for details).
circuits The number of circuits
utilization The decimal percentage of circuit usage (usage in minutes
divided by total number of circuits multiplied by 60).
8-4 Telica, Inc.

8.2.2.2 Peg Counts
8.2.2.2.1 Peg Counts Report

To further monitor call delivery, TCA updates peg counts to capture the
disposition of every call per trunk group (SS7, SIP, BICC and CAS, ISDN
and GR303) interfaces and outgoing directory number. The disposition
identifies if the call was answered, ringing (no answer), busy, not
completed or in-coming.
Detailed peg count reports are generated if the “Detailed Peg Report”
value in the tsaa_<prefix>.conf file is set to “1.” When peg count reports
are not detailed, the state field will show states. When peg count reports
are detailed, the state field will show cause codes. In addition, statistics
for the circuit state will be included in each peg count record and will
provide the number of circuits provisioned for traffic. This is calculated
when the record is produced.
Based on the configuration, files can be produced on one of the following

intervals:
• Every 15 minutes
• Every 1 hour
• Every 24 hours
The following information is calculated for every record when the non-
detailed output option is chosen:
ISDN Directory Trunk

Interface Number (route) Group
Incoming Answered
Ringing
Busy
Not completed
In Progress
Outgoing Answered
Ringing
Busy
Not completed
In Progress
Circuit Total Circuits
States Provisioned
Telica, Inc. 8-5

8.2.2.2.2 Peg Counts Output

Peg counts are reported for every ISDN interface, directory number, trunk
group and cause code in the system. The naming convention for the file
is:
<prefix>_STATS_PEG_COUNT_yyyymmddhhmm.txt
yyyymmddhhmm is the reported year/month/day/hour/minute.
The format for this file is:
version,month,day,year,hour,min,record_type,type_id,mode,state,
medium,value,peg_count,circuits

Boston_STATS_PEG_COUNT_200201032200.txt
1.0,3,7,2002,0,0,1,1,2,16,1,4001,48,671
1.0,3,7,2002,0,0,1,2,2,16,1,5084800001,48,671
1.0,3,7,2002,0,0,1,3,1,16,1,599,48,24
1.0,3,7,2002,0,5,1,1,2,16,1,4001,45,671
1.0,3,7,2002,0,5,1,2,2,16,1,5084800001,45,671
1.0,3,7,2002,0,5,1,3,1,16,1,599,45,24
Fields:
month, day, year, hour, min Describes the start date and time of the five-
minute reporting interval of the record.
1 = peg count – 5 min period
2 = peg count – 1 hour period
type _id Has the following values:
1 = ISDN interface
2 = directory number
3 = SS7 trunk group
4 = CAS trunk group
5 = SIP trunk group
6 = CAS interface
7 = GR303 interface
8 = BICC trunk group
8-6 Telica, Inc.

mode Has the following values:

1 = incoming
2 = outgoing
state Has the following values if the “Detailed Peg Report” value
in the tsaa_<prefix>.conf file is set to “0” (Detailed
reporting is disabled).
State Values when Detailed reporting is disabled
0 in progress
16 Answered
17 Busy
18 Ringing
999 not connected
Has the following values (cause codes) if the “Detailed Peg

Report” value in the tsaa_<prefix>.conf file is set to “1”
(Detailed reporting is enabled).
SS7 Cause Codes when Detailed reporting is enabled

0 in progress
1 unassigned number
2 no route to transit network
3 no route to destination
4 send special infomation tone
5 misdialed trunk prefix
16 normal call clearing
17 user busy
18 no user response
19 no answer (user alerted )
21 call rejected
22 number changed
23 unallocated destination number
24 unknown business group
25 exchange routing error
26 Misrouted call to a Ported Number
27 destination out of order
28 Address incomplete
29 facility rejected
31 normal unspecified
34 no circuit/channel available
38 network out of order
41 Temporary failure
42 Switch equipment congestion
44 requested circuit/channel unavailable
Telica, Inc. 8-7

SS7 Cause Codes when Detailed reporting is enabled

47 resources unavailable, unspecified
43 user information discarded
45 Preemption
46 precedence call blocked
47 Preemption
50 requested facility not subscribed
51 call type incompatible with service request
54 call blocked due to group restrictions
55 incoming calls barred within CUG
57 bearer capability not authorized
58 bearer capability not available
63 Service or option unavailable
65 bearer capability not implemented
69 requested facility not implemented
70 only restricted digital bear cap is avail*/
79 service or option not implemented
87 Called User Not member of CUG
88 incompatible destination
91 invalid transit network selection
95 invalid message, unspecified
81 invalid call reference value
97 msg type is non-existent or not implemented
99 Param. non-existant, or not impl., discard
110 Param. non-existant, or not impl., discard message
102 timeout recovery
103 Param. non-existant, or not impl. pass along
111 protocol error, unspecified
100 invalid parameter contents
127 interworking unspecified
ISDN Cause Codes when Detailed reporting is enabled

0 in progress
1 unassigned number
2 no route to transit network
3 no route to destination
6 channel unacceptable
7 call awarded and being delivered
9 prefix 1 dialed in error
16 normal call clearing
17 user busy
18 no user response
19 no answer (user alerted )
21 call rejected
8-8 Telica, Inc.


22 number changed
24 number unassigned
26 non selected User clearing
27 destination out of order
28 invalid number format
29 facility rejected
30 response to STATUS ENQUIRY
31 normal unspecified
34 no circuit/channel available
35 call queued
38 network out of order
41 Temporary failure
42 Switch equipment congestion
43 access info discarded
44 requested circuit/channel unavailable
47 resources unavailable, unspecified
49 Quality of Service unavailable
50 requested facility not subscribed
52 outgoing calls barred
54 incoming calls barred
57 bearer capability not authorized
58 bearer capability not available
59 call restriction
60 terminal call redirection rejected
62 unathorized service
63 Service or option unavailable
65 bearer capability not implemented
66 channel type not implemented
69 requested facility not implemented
70 only restricted digital bear cap is avail.
79 service or option not implemented
81 invalid call reference
82 channel does not exist
83 susp. call exists, call id is invalid
84 call identity is in use
85 no call suspended
86 call id'd has been cleared
88 incompatible destination
91 invalid transit network selection
92 invalid facility parameter
95 invalid message, unspecified
96 mandatory info element is missing
97 msg type is non-existent or not implemented
98 msg type invalid in call state or not implemented
Telica, Inc. 8-9


99 info element non-existent or not implemented
100 invalid info element
101 msg type not compatible with call state
102 recovery on timer expiry
103 mssg recvd with mand info elmt of incorrect
length
111 protocol error, unspecified
112 protocol discriminator error
113 bearer service not available
114 end-to-end info transfer impossible
126 entering conversation mode
127 Interworkingpecified
medium Has the following values:

1 = digital
2 = analog
value Type_id’s value (i.e. trunk group #, ISDN Interface, or
Directory Number)
peg_count The number of peg counts for the value.
circuits The number of provisioned circuits for the value. This is
not valid for Directory Number or SIP.
8.2.2.3 Trunk Group Hold Time
8.2.2.3.1 Trunk Group Hold Time Report

This report is generated every fifteen-minutes, every hour or every twenty-
four hours as is the Peg Count report. It displays the average hold time for
each trunk group.
For a description and sample of Trunk Group Hold Time output, refer to
8.2.2.3.2.
8.2.2.3.2 Trunk Group Hold Time Output

This report displays the average hold time for all trunks within the trunk
group. The naming convention for the Trunk Group Hold Time is:
<prefix>_STATS_HOLD_TIME_yyyymmddhhmm.txt

yyyymmddhhmm is the reported year/month/day/hour/minute. The format
for the Trunk Group Hold Time output is:
version,month, day,year,hour,min,value,hold_time
8-10 Telica, Inc.


Boston_STATS_HOLD_TIME_021301.txt
1.0,9,4,2001,10,20,1,20
1.0,9,4,2001,10,25,1,5
1.0,9,4,2001,10,30,1,6
1.0,9,4,2001,10,35,1,19
1.0,9,4,2001,10,40,1,101
1.0,9,4,2001,10,45,1,543
1.0,9,4,2001,10,50,1,66
1.0,9,4,2001,10,55,1,22
1.0,9,4,2001,15,55,1,1
1.0,9,4,2001,16,0,1,27
1.0,9,4,2001,16,5,1,43
1.0,9,4,2001,16,10,1,18
1.0,9,4,2001,16,15,1,1
1.0,9,4,2001,16,20,1,21
Fields:
version Specifies the version of the application on the
Plexus.
month, day, year, hour, min Describes the date and time of the record.
value Trunkgroup ID.
hold_time The average hold time for the value (in seconds).
8.2.2.4 Traffic Centum Call Seconds (CCS)
8.2.2.4.1 Traffic CCS Report

The following criteria is used for data collection to generate traffic reports
for Trunk Groups and ISDN Interfaces:
• Operational measurements/traffic statistics are gathered on a real-
time basis, at the DS0 level.
• Traffic statistics are consolidated for a specific trunk group.
• Reports are generated as specified in the tsaa_<prefix>.conf file
and are accessible through an automated polling process. A time
stamp is placed on the report, indicative of local time.
• Each report indicates trunks in service, trunks that are in a
maintenance busy (or “busied-out”) status, and total trunks
included on the trunk group.
Note: All time period criteria used to generate Traffic CCS reports are based
on the Plexus 9000 clock, not the Sun server clock.
Telica, Inc. 8-11

8.2.2.4.2 Traffic CCS Output

The traffic report is generated as specified in the tsaa_<prefix>.conf file.
The report format parameter the “conf” file determines the output for this
report. The options and naming conventions for the files are space-
delimited with header and comma-delimited with header.
Space-delimited with header
There are five types of space-delimited with header files:

atsm_<prefix>.yyyymmddhhmm.txt
castg_<prefix>.yyyymmddhhmm.txt
pri_<prefix>.yyyymmddhhmm.txt
siptg_<prefix>.yyyymmddhhmm.txt
gr3_<prefix>.yyyymmddhhmm.txt
bicctg_<prefix>.yyyymmddhhmm.txt
casif_<prefix>.yyyymmddhhmm.txt
Prefix is the hostname; yyyy is the year; mm is the month within the
year; dd is the day of the month; hh is the hour of the day; and mm is the
minute of the hour.
Samples of what the outputs would actually look like are provided on
following pages. Field descriptions follow.
Sample of atsm, bicctg and castg Space-delimited with Header Report:

Format is common for atsm_<prefix>.yyyymmddhhmm.txt,
bicctg_<prefix>.yyyymmddhhmm.txt and
castg_<prefix>.yyyymmddhhmm.txt
BOSTON 03/04/2002 17:15:00

Start 05/21/2002 23:00:00 Stop 05/22/2002 00:00:00
TGPNUM TGPNAM TOTTRK AVLTRK MNTTRK PRECUTTRK INCCNT
OUTCNT TOTCNT OFLCNT INCCCS OUTCCS TOTCCS
1 TRUNKGROUP1 36 24 12 12 0 2053 2053 1540 0 414 414
2 TRUNKGROUP2 12 12 0 0 0 1547 1547 0 0 310 310
3 trkgrp3 48 48 0 0 3600 0 3600 0 724 0 724
Fields for atsm, bicctg and castg Space-delimited Reports:

Switch Name Name of the switch
Start/Stop On-the-hour start and stop times.
TGPNUM Trunk group number.
TGPNAM Trunk group name
8-12 Telica, Inc.

TOTTRK Total trunks available (All provisioned trunks including

those that have not been turned up for service and those
that are in a maintenance state.).
AVLTRK Available trunks (All “cut” trunks (in-service and out-of-
service) but not including “pre-cut”. Supported in releases
3.1.1.3X and 3.6 or greater.
MNTTRK Maintenance trunks (Trunks in a maintenance state either
by an operator or abnormal circumstances). Supported in
releases 3.1.1.3X and 3.6 or greater.
PRECUTTRK Number of trunks that are precut (trunks not turned up
for service). Supported in releases 3.1.1.3X and 3.6 or
greater.
INCCNT Incoming peg count – indicates the number of times the
trunk was seized.
OUTCNT Outgoing peg count – indicates the number of times the
trunk was seized attempted to terminate.
TOTCNT Total peg count – sum of INCCNGT and OUTCNT.
OFLCNT Overflow count – the number of outgoing calls that
overflowed from this trunk group to alternate trunk groups
because all trunks of this group were busy. Supported in
INCCCS Incoming CCS.
OUTCCS Outgoing CCS.
TOTCCS Total CCS – sum of INCCCS and OUTCCS.
Sample pri Space-delimited with Header Report:
BOSTON 03/04/2002 17:15:00

Start 05/21/2002 23:00:00 Stop 05/22/2002 00:00:00
INTFCNUM TOTCIRC AVLCIRC NUMLINK INCCNT OUTCNT TOTCNT
INCCCS OUTCCS TOTCCS
1 23 23 1 0 1832 1832 0 372 372
2 23 23 1 1832 0 1832 372 0 372
4 23 23 1 0 0 0 0 0 0
5 23 23 1 0 0 0 0 0 0
10 23 23 1 0 0 0 0 0 0
13 23 23 1 0 0 0 0 0 0
14 23 23 1 0 0 0 0 0 0
15 23 23 1 0 0 0 0 0 0
Telica, Inc. 8-13

Fields for pri Space-delimited Reports:

INTFCNUM Interface number.
TOTCIRC Total circuits (All provisioned circuits including those that
have not been turned up for service and those that are in a
maintenance state.).
AVLCIRC Circuits available
NUMLINK Number of links
trunk was seized.
TOTCNT Total peg count – sum of INCCNGT and OUTCNT.
Sample of sip Space-delimited with Header Report:
BOSTON 12/06/2002 16:15:50

Start 12/06/2002 15:00:00 Stop 12/06/2002 16:00:00
TGPNUM INCCNT OUTCNT TOTCNT INCCCS OUTCCS TOTCCS
13 0 1 1 0 1 1
180 1 0 1 1 0 1
2001 0 1 1 0 1 1
Fields for sip Space-delimited Reports:

TGPNUM Trunk group number.
trunk was seized.
TOTCNT Total peg countP – sum of INCCNGT and OUTCNT.
8-14 Telica, Inc.

Sample gr3 Space-delimited with Header Report:
BOSTON 03/04/2002 17:15:00

Start 05/21/2002 23:00:00 Stop 05/22/2002 00:00:00
INTFCNUM TOTCRV MNTCRV TOTDS0 MNTDS0 OFLCNT INCCNT OUTCNT
TOTCNT INCCCS OUTCCS TOTCCS
1 4 0 92 48 0 0 0 0 0 0 0
2 0 0 0 0 0 0 0 0 0 0 0
Fields for gr3 Space-delimited Reports:

TOTCRV Total CRVs (All provisioned CRVs including those that
MNTCRV CRVs in maintenance state
TOTDS0 Total bearer channels (DS0s)
MNTDS0 DS0s in maintenance state.
OFLCNT Overflow count – the number of outgoing calls that
overflowed from this GR303 interface to alternate route
because all DS0s of this interface were not idle.
trunk was seized.
TOTCNT Total peg count – sum of INCCNGT and OUTCNT
INCCS Incoming CCS.
OUTCCS Outgoing CCS
TOTCCS Total CCS – sum of INCCCS and OUTCCS
Sample casif Space-delimited with Header Report:
BOSTON 03/04/2002 17:15:00

Start 05/21/2002 23:00:00 Stop 05/22/2002 00:00:00
INTFCNUM INTFCNAME TOTLINE INCCNT OUTCNT TOTCNT INCCCS
OUTCCS TOTCCS
1 CASIF1 4 10 0 10 20 0 20
11 CASIF2 1 1 0 1 1 0 1
Telica, Inc. 8-15

Fields for casif Space-delimited Reports:

INTFCNAME Interface name
TOTLINE Total CAS lines (All provisioned CAS lines)
trunk was seized.
TOTCNT Total peg count – sum of INCCNGT and OUTCNT
INCCS Incoming CCS.
OUTCCS Outgoing CCS
TOTCCS Total CCS – sum of INCCCS and OUTCCS
Comma-delimited with header

There are five types of comma-delimited with header files:
ccs_atsm_<prefix>.yyyymmddhhmm.txt
ccs_castg_<prefix>.yyyymmddhhmm.txt
ccs_pri_<prefix>.yyyymmddhhmm.txt
ccs_siptg_<prefix>.yyyymmddhhmm.txt
ccs_gr3_<prefix>.yyyymmddhhmm.txt
ccs_bicctg_<prefix>.yyyymmddhhmm.txt
ccs_casif_<prefix>.yyyymmddhhmm.txt
Prefix is the hostname; yyyy is the year; mm is the month within the
year; dd is the day of the month; hh is the hour of the day; and mm is the
minute of the hour.
Format of ccs_atsm_<prefix> , ccs_bicctg_<prefix> or

ccs_castg_<prefix> reports is:
switchname,startmonth,startday,startyear,starthour,start
minute,period(in minutes),endmonth,endday,endyear,
endhour,endminute,tgpnum,tgpnam,tottrk,avltrk,mainttrk,
precuttrk,inccnt,outcnt,totcnt,oflcnt,incccs,outccs,
totccs
8-16 Telica, Inc.

Sample of ccs_atsm Comma-delimited with Header Report:
BOSTON,5,21,2002,23,0,60,5,22,2002,0,0,1,TRUNKGROUP1,36,
24,12,12,0,2053,2053,1540,0,414,414
BOSTON,5,21,2002,23,0,60,5,22,2002,0,0,2,TRUNKGROUP2,12,
12,0,0,0,1547,1547,0,0,310,310
BOSTON,5,21,2002,23,0,60,5,22,2002,0,0,3,trkgrp3,48,48,
0,0,3600,0,3600,0,724,0,724
Fields for ccs_ atsm, ccs_bicctg and ccs_castg Comma-delimited

Reports:
switch name Name of the switch
startmonth, startday, startyear, starthour, startminute
The starting month, day, year, hour and minute of report.
period Period in minutes
endmonth, endday, endyear, endhour, endminute
The ending month, day, year, hour and minute of report.
tgpnum Trunk group number.
tgpnam Trunk group name
tottrk Total trunks configured (All provisioned trunks including
those that have not been turned up for service and those
that are in a maintenance state.).
avltrk Available trunks (All “cut” trunks (in-service and out-of-
service) but not including “pre-cut”. Supported in releases
3.1.1.3X and 3.6 or greater.
mainttrk Maintenance trunks (Trunks in a maintenance state either
by an operator or abnormal circumstances). Supported in
precuttrk Number of trunks that are precut (trunks not turned up for
service). Supported in releases 3.1.1.3X and 3.6 or greater.
inccnt Incoming peg count – indicates the number of times the
trunk was seized.
outcnt Outgoing peg count – indicates the number of times the
totcnt Total peg count – sum of INCCNGT and OUTCNT.
oflcnt Overflow count – the number of outgoing calls that
overflowed from this trunk group to alternate trunk groups
because all trunks of this group were busy. Supported in
Telica, Inc. 8-17

incccs Incoming CCS.

outccs Outgoing CCS.
totccs Total CCS – sum of INCCCS and OUTCCS.
Format of ccs_pri_<prefix>.yyyymmddhhmm.txt is:

endhour,endminute,intfcnum,totcirc,avlcirc,numlink,
inccnt,outcnt,totcnt,incccs,outccs,totccs
Sample of ccs_pri Comma-delimited with Header Report:
BOSTON,5,21,2002,23,0,60,5,22,2002,0,0,1,23,23,1,0,1832,
1832,0,372,372
BOSTON,5,21,2002,23,0,60,5,22,2002,0,0,2,23,23,1,1832,0,
1832,372,0,372
BOSTON,5,21,2002,23,0,60,5,22,2002,0,0,4,23,23,1,0,0,0,
0,0,0
BOSTON,5,21,2002,23,0,60,5,22,2002,0,0,5,23,23,1,0,0,0,
0,0,0
BOSTON,5,21,2002,23,0,60,5,22,2002,0,0,10,23,23,1,0,0,
0,0,0,0
BOSTON,5,21,2002,23,0,60,5,22,2002,0,0,13,23,23,1,0,0,
0,0,0,0
BOSTON,5,21,2002,23,0,60,5,22,2002,0,0,14,23,23,1,0,0,
0,0,0,0
Fields for ccs_pri Comma-delimited Reports:

intfcnum Interface number.
totcirc Total circuits (All provisioned circuits including those that
avlcirc Circuits available
numlink Number of links
trunk was seized.
8-18 Telica, Inc.


Format of ccs_siptg_<prefix> reports is:

endhour,endminute,tgpnum,inccnt,outcnt,totcnt,incccs,
outccs,totccs
Sample of ccs_siptg Comma-delimited with Header Report:

BOSTON,12,6,2002,15,0,60,12,6,2002,16,0,13,0,1,1,0,1,1
BOSTON,12,6,2002,15,0,60,12,6,2002,16,0,180,1,0,1,1,0,1
Fields for ccs_siptg Comma-delimited Reports:

trunk was seized.
Format of ccs_gr3_<prefix>.yyyymmddhhmm.txt is:

endhour,endminute,intfcnum,totcrv,mntcrv,totds0,mntds0,o
flcnt,inccnt,outcnt,totcnt,incccs,outccs,totccs
Telica, Inc. 8-19

Sample of ccs_gr3 Comma-delimited with Header Report:
BOSTON,4,4,2003,11,30,15,4,4,2003,11,45,1,4,0,92,48,0,0,0,
0,0,0,0
BOSTON,4,4,2003,11,30,15,4,4,2003,11,45,2,0,0,0,0,0,0,0,0,
0,0,0
Fields for ccs_gr3 Comma-delimited Reports:

totcrv Total crvs (All provisioned crvs including those that have
not been turned up for service and those that are in a
mntcrv Crvs in maintenance state
totds0 Total bearer channels (DS0s)
mntds0 DS0s in maintenance state.
oflcnt Overflow count – the number of outgoing calls that
overflowed from this GR303 interface to alternate route
because all DS0s of this interface were not idle.
trunk was seized.
totcnt Total peg count – sum of INCCNGT and OUTCNT
inccs Incoming CCS.
outccs Outgoing CCS
totccs Total CCS – sum of INCCCS and OUTCCS
Format of ccs_siptg_<prefix> reports is:

endhour,endminute,tgpnum,inccnt,outcnt,totcnt,incccs,
outccs,totccs
8-20 Telica, Inc.

Sample of ccs_siptg Comma-delimited with Header Report:

BOSTON,12,6,2002,15,0,60,12,6,2002,16,0,13,0,1,1,0,1,1
BOSTON,12,6,2002,15,0,60,12,6,2002,16,0,180,1,0,1,1,0,1
Fields for ccs_siptg Comma-delimited Reports:

trunk was seized.
Format of ccs_casif_<prefix>.yyyymmddhhmm.txt is:

endhour,endminute,intfcnum,intfcname,totline,
inccnt,outcnt,totcnt,incccs,outccs,totccs
Sample of ccs_casif Comma-delimited with Header Report:
BOSTON,4,4,2003,11,30,15,4,4,2003,11,45,1,CASIF1,4,10,0,10,
20,0,20
BOSTON,4,4,2003,11,30,15,4,4,2003,11,45,11,CASIF2,1,1,0,1,1
,0,1
Fields for ccs_casif Comma-delimited Reports:

Telica, Inc. 8-21

intfcname Interface name.

totline Total CAS lines (All provisioned CAS lines).
trunk was seized.
totcnt Total peg count – sum of INCCNGT and OUTCNT
inccs Incoming CCS.
outccs Outgoing CCS
totccs Total CCS – sum of INCCCS and OUTCCS
8.2.2.5 ASCII CDR Report

If this option is turned on, then every 5 minutes an ASCII CDR file is
created and CDRs of the calls are written in these files. The naming
convention for the file is;
<prefix>_ STATS_CDR_ yyyymmddhhmm.txt
where prefix is the hostname; yyyy is the year; mm is the month within
the year; dd is the day of the month; hh is the hour of the day; and mm is
the minute of the hour.
A sample of what the output would actually look like and field
descriptions follow.
Sample Output
3,118,57,4,33,0,11-08-2002,15:13:45.00,47,6175551000,31055510000,16,0,1,
11-08-2002,15:13:49.00,11-08-2002,15:13:46.00,37,11-08-2002,15:13:49.00,
boston1,boston2,0,197379,0,9084446666,,020117000010101,010108000000101,
2222,4,31055510000
3,118,69,4,33,0,11-08-2002,15:13:58.00,48,6175551000,31055510000,16,0,1,
11-08-2002,15:14:02.00,11-08-2002,15:13:59.00,38,11-08-2002,15:14:02.00,
boston1,boston2,0,97379,0,9084446666,,020117000010101,010108000000101,2222
,6,31055510000
8-22 Telica, Inc.

Fields:
Incoming Interface: Has the following values:
0 = Invalid or No interface
1 = ISDN interface
3 = SS7 trunk group
4 = CAS trunk group
5 = SIP trunk group
6 = CAS Line
7 = GR303 interface
999 = Valid interface but not known by TSAA.
Incoming Interface id:
ISDN interface ID for ISDN interface,
GR303 interface ID for GR303 interface
Trunk group number for SS7
Trunk group number for CAS
Trunk group number for BICC
Trunk group number for SIP Trunk groups.
Interface id for CAS Interface
Incoming CIC:
0 = (not used) for ISDN,CAS Interface
CIC for SS7 Trunk Group
CRV for GR303 interface
CAS Trunk Group
SIP Trunk Group
BICC Trunk Group
CAS Line
Outgoing Interface: Has the following values;

0 = Invalid or No interface
1 = ISDN interface
3 = SS7 trunk group
4 = CAS trunk group
5 = SIP trunk group
6 = CAS Line
7 = GR303 interface
8 = BICC interface
999 = Valid interface but not known by TSAA
Telica, Inc. 8-23

Outgoing Interface id:

ISDN interface ID for ISDN interface
GR303 interface ID for GR303 interface
Trunk group number for SS7
Trunk group number for CAS
Trunk group number for BICC
Trunk group number for SIP Trunk groups.
Interface id for CAS Interface
Outgoing CIC:
0 = (not used) for ISDN,CAS Interface
CIC for SS7 Trunk Group
CRV for GR303 interface
CAS Trunk Group
SIP Trunk Group
BICC Trunk Group
CAS Line.
Carrier Connect Date: Carrier Connection date of the call.

Carrier Connect Time: Carrier Connection time of the call.
Carrier Duration: Total carrier duration of the call if it’s released,
current carrier duration of the call if it’s in progress (long
duration CDRs) in tenths of a second.
Calling Party Number
Called Party Number
Release cause: Release cause of the call if the call is released.0 for in
progress calls(long duration CDRs).
Off Hook Indicator: Has the following values:

0 = Call is answered
1 = Call is not answered.
9 = Unknown
Release Originator: Has the following values;

1 = Release initiated by the incoming interface.
2 = Release initiated by the outgoing interface.
3 = Release initiated internally (by the stack)
8-24 Telica, Inc.

Carrier Release Date: Carrier Release date of the call if the call is
released. If the call is in progress, it’s 00-00-0000.
Carrier Release Time: Carrier Release time of the call if the call is
released. If the call is in progress, it’s 00:00:00.00.
Conversation Connect Date: Conversation Connection date of the call, if
the call is answered. If the call is not answered, it’s 00-00-
0000.
Conversation Connect Time: Conversation Connection time of the call,
if the call is answered. If the call is not answered it’s
00:00:00.00.
Conversation Duration: Total conversation duration of the call if it’s
answered and released, current conversation duration of the
call if it’s in progress (long duration CDRs) in tenths of a
second. If the call is not answered, it’s 0.
Conversation Release Date: Conversation Release date of the call if the
call is answered and released. If the call is not answered or
if it’s in progress, it’s 00-00-0000.
Conversation Release Time: Conversation Release time of the call if the
call is answered and released. If the call is not answered or
if it’s in progress, it’s 00:00:00.00.
Incoming Trunk Group Name: “NONAME” if the interface doesn’t
have a name.
Outgoing Trunk Group Name: “NONAME” if the interface doesn’t
have a name.
International Indicator: Has the following values;
0 = Call is a domestic call.
1 = Call is an international call.
Originating Point Code:
Destination Point Code:
Charge Number:
Country Code: Represents a country code
Telica, Inc. 8-25

Incoming Physical Port: This field is a fifteen-digit string identifying the

originating physical resource used by the call. The string is
formatted as follows:
TTCCSS0OO331100 where:
TT - The front IOM board type as identified in following

table.
CC - The switch (chassis) number. Currently is always 01.
XX - The slot number (00 to 17).
0 - Unused. Will be 0.
OO - The OC3. Non-zero on OC3 boards.
33 - The DS3. Non-zero on OC3 and DS3 boards.
11 - The DS1.
00 - The DS0.
00 UNKNOWN
01 DS1 (89-0360)
02 DS3 (89-0365)
03
04 Octal DS3 (89-0382)
05 Octal DS3 (89-0398)
06 ATM DS3 (89-0409)
07 Octal DS3
08 ENA (89-0390)
11 OC12
12 VOIP
13 STS DS3
14 STS or DS3
15 PNA (89-0393)
16
17
18 Triple DS3 (410)
19 Octal DS3 (411)
Note that only TDM board types are supported. For

non-TDM boards only BBSSss are populated. The
remaining fields are zero.
Outgoing Physical Port: Terminating physical resource, formatted as in

the previous description.
8-26 Telica, Inc.

Carrier: 4 digit carrier code.

Call Id: The unique callId value available from call control.
Dialed Number: Dialed number
8.2.2.6 ASR Report

Answer to Seizure Ratio (ASR) reports are generated if the “ASR Report”
value in the tsaa_<prefix>.conf file is set to “1.”
Based on the configuration, files can be produced on one of the following

intervals:
• Every 1 hour
• Every 24 hours
8.2.2.6.1 ASR Output

ASRs are reported for every ISDN, and CAS interfaces, SS7, CAS, BICC,
and SIP trunk groups The naming convention for the file is:
<prefix>_ASR_yyyymmddhhmm.txt
yyyymmddhhmm is the reported year/month/day/hour/minute.
The format for this file is:
version,month,day,year,hour,min,record_type,type_id,value,
answered_incoming,answered_outgoing,answered_total,
seizure_incoming,seizure_outgoing,seizure_total,ASR

Boston_STATS_ASR_200211082000.txt
1.0,11,8,2003,20,50,1,3,661,0,1,1,0,1,1,1.00
1.0,11,8,2003,20,50,1,3,662,0,1,1,0,1,1,1.00
1.0,11,8,2003,20,50,1,3,663,0,1,1,0,1,1,1.00
1.0,11,8,2003,20,50,1,3,664,0,1,1,0,1,1,1.00
1.0,11,8,2003,20,50,1,3,665,0,1,1,0,1,1,1.00
1.0,11,8,2003,20,50,1,3,666,0,1,1,0,1,1,1.00
1.0,11,8,2003,20,50,1,3,667,0,1,1,0,1,1,1.00
1.0,11,8,2003,20,55,1,3,551,1,0,1,11,0,11,0.09
1.0,11,8,2003,20,55,1,3,552,1,0,1,12,0,12,0.08
1.0,11,8,2003,20,55,1,3,553,1,0,1,13,0,13,0.08
1.0,11,8,2003,20,55,1,3,554,1,0,1,13,0,13,0.08
1.0,11,8,2003,20,55,1,3,555,1,0,1,11,0,11,0.09
1.0,11,8,2003,20,55,1,3,556,1,0,1,10,0,10,0.10
1.0,11,8,2003,20,55,1,3,557,1,0,1,4,0,4,0.25
Telica, Inc. 8-27

1.0,11,8,2003,20,55,1,3,661,0,1,1,0,1,1,1.00
1.0,11,8,2003,20,55,1,3,662,0,1,1,0,1,1,1.00
1.0,11,8,2003,20,55,1,3,663,0,1,1,0,1,1,1.00
1.0,11,8,2003,20,55,1,3,664,0,1,1,0,1,1,1.00
1.0,11,8,2003,20,55,1,3,665,0,1,1,0,1,1,1.00
1.0,11,8,2003,20,55,1,3,666,0,1,1,0,1,1,1.00
1.0,11,8,2003,20,55,1,3,667,0,1,1,0,1,1,1.00
1.0,11,8,2003,20,30,4,3,551,3,0,3,15,0,15,0.20
1.0,11,8,2003,20,30,4,3,552,3,0,3,16,0,16,0.19
1.0,11,8,2003,20,30,4,3,553,3,0,3,17,0,17,0.18
1.0,11,8,2003,20,30,4,3,554,3,0,3,17,0,17,0.18
1.0,11,8,2003,20,30,4,3,555,3,0,3,15,0,15,0.20
1.0,11,8,2003,20,30,4,3,556,3,0,3,14,0,14,0.21
Fields:
month, day, year, hour, min Describes the start date and time of the
reporting interval of the record.
type _id Has the following values:
1 = ISDN interface
2 = directory number
3 = trunk group
4 = CAS trunk group
5 = SIP trunk group
6 = CAS interface
7 = GR303 interface
value Type_id’s value (i.e. trunk group #, ISDN Interface)

answered_incoming Total number of answered incoming calls in the
period.
answered_outgoing Total number of answered outgoing calls in he
period.
answered_total Total number of answered calls in the period
(answered_incoming + answered_outgoing)
8-28 Telica, Inc.

seizure_incoming Total number of seizures for the incoming calls in the

period.
seizure_outgoing Total number of seizures for the outgoing calls in he
period.
answered_total Total number of seizures in the period
(seizure_incoming + seizure_outgoing)
ASR Answer to Seizure Ratio of the period. Calculated with the

formula; (answered_total / seizure_total)
8.3 Installation and Configuration

To use the BTS or TCA successfully with the Plexus 9000, you must first
meet specific platform requirements, listed in 8.3.1. You must then install
and configure the BTS or TCA on the Sun server and establish
communications between the BTS or TCA and the Plexus 9000.
8.3.1 Platform Requirements
8.3.1.1 TCA Server Platform Requirements

The TCA supports the Plexus 9000, release 3.1.1.1 or greater, and must
meet these prerequisites:
• Sun Solaris™ 2.7 or 2.8 with 500 MB memory and a 10/100
Ethernet card
8.3.1.2 BTS Server Platform Requirements

The BTS supports the Plexus 9000, release 3.8 or greater, and must meet
these prerequisites:
• Sun Sparc with 256 MB memory and a 10/100 MB Ethernet card
and Ethernet connection
8.3.2 Configuration
8.3.2.1 TCA
Configuration procedure for gathering statistics using the TCA can be
found in DLP-541 or DLP-542 of this manual. Procedures for
provisioning the Plexus 9000 for gathering statistics can be found in the
Telica, Inc. 8-29

8.3.2.2 BTS
Configuration procedure for gathering statistics using the BTS and TSAA
can be found in DLP-541 of this manual. Procedures for provisioning the
Plexus 9000 for gathering statistics can be found in the Plexus 9000
Installation and Operation Manual.
8-30 Telica, Inc.

Section 150-500-100 TNG-893
Issue 2, May 13, 2003
9. TOP Procedures
9.1 Task Oriented Practices (TOPS)
9.1.1 Scope ......................................................................................................................... 9-1

9.1.2 Overview ................................................................................................................... 9-1
9.1.3 How To Use This TOP Section................................................................................. 9-2
9.1.1 Scope
This section describes Task Oriented Practices (TOPs) and how to use the
procedures.
9.1.2 Overview
The Installation, Configuration and Testing section of this manual is
written in the TOP style and complies with AT&T 000-100-115 Issue 3
February 1984. The Task Oriented Practices (TOPs) section includes the
following:
• TOP Documentation References
• Task Index Lists (IXLs)
• Detailed Level Procedures (DLPs)
• Checklist (CKL)
The procedures give you all the step-by-step instructions you need to do
your job or task. The instructions are given in the order they must be
done. Failure to follow the instructions in order may cause service
interruptions.
Regardless of your work experience, TOPs can be a useful tool in doing

your job. If you have done a particular job many times, TOPs serve as a
reminder for those instructions you cannot recall. If you have never done
a particular job, or do it infrequently, TOPs give you step-by-step
instructions.
Detailed Level Procedures: These tasks enable you to install

applications, to provision it for operation, and to test it after it is installed.
Telica, Inc. 9-1

TNG-893 Section 150-500-100
Issue 2, May 13, 2003
9.1.3 How To Use This TOP Section

To find the instructions for performing installation and provisioning, you
must complete the following steps.
1. Find the job in the Task Index (IXL-001) in the "FIND YOUR
JOB IN THE LIST BELOW" column. Then find the procedure
number for that job in the "THEN GO TO" column. The tasks of
IXL-001 are listed by application.
2. Go to the referenced procedure (for example: DLP-501 - Install
and Provision the ASCII Billing System) to find detailed
instructions on how to perform the task. The procedure will give
you step-by-step instructions to do that item.
3. All DLPs are located in the following the IXL.
4. If assistance is required after completing all applicable TOP
procedures, contact Telica Technical Support at 888-440-8354 or
508-485-5739.
9-2 Telica, Inc.

Issue 4, January 9, 2004 Checklist
Section 150-500-200
9.2 Procedures Checklist
ISSUE &
DLP TITLE NAME DATE
IXL-001 Provisioning Task Index List 2, 01/09/04
DLP-501 Install and Provision the ASCII Billing System 2, 05/13/03

DLP-502 Edit Configuration Files for ASCII Billing 2, 05/13/03
DLP-503 Upgrade the ASCII Billing Application 2, 05/13/03
DLP-511 Install and Provision AMA Lite Application 2, 05/13/03

DLP-512 Edit Configuration Files for AMA Lite 2, 05/13/03
DLP-513 Upgrade the AMA Lite Application 2, 05/13/03
DLP-514 Create and Read AMA file 2, 05/13/03
DLP-515 Disable ports for Security 2, 05/13/03
DLP-516 Create and Read AMA file When using BTS 1, 11/07/03
DLP-521 Install and Provision Traffic Collection Application 4, 01/09/04

DLP-522 Edit Configuration Files for Traffic Collection 3, 01/09/04
DLP-523 Upgrade the Traffic Collection Application 4, 01/09/04
DLP-531 Install the PlexView Pro AMA Billing Application 3, 09/25/03
DLP-541 Install the PlexView Billing and Traffic System 3, 01/09/04

DLP-542 Upgrade the Billing and Traffic System 2, 01/09/04
Telica, Inc. 9-3

Checklist Issue 4, January 9, 2004
Section 150-500-200
NOTES:
9-4 Telica, Inc.

Section 150-500-300 IXL-001
Issue 2, January 9, 2004
9.3 Provisioning Task Index List
Note: DLPs are found in numerical order after this list.
FIND YOUR JOB IN THE LIST BELOW THEN GO TO

ASCII Billing (ABS)
Install and Provision the ASCII Billing System ..............................................DLP-501
Edit Configuration Files for ASCII Billing ......................................................DLP-502
Upgrade the ASCII Billing Application ........................................................... DLP-503
AMA LITE
Install and Provision AMA Lite Application ...................................................DLP-511
Edit Configuration Files for AMA Lite ............................................................ DLP-512
Upgrade the AMA Lite Application ................................................................. DLP-513
Create and Read AMA file................................................................................ DLP-514
Disable ports for Security.................................................................................. DLP-515
Create and Read AMA file When Using BTS ..................................................DLP-516
Traffic Collection Application (TCA)

Install and Provision Traffic Collection Application ....................................... DLP-521
Edit Configuration Files for Traffic Collection ................................................ DLP-522
Upgrade the Traffic Collection Application ..................................................... DLP-523
PlexView Pro AMA Billing

Install the PlexView Pro AMA Billing Application ........................................ DLP-531
Telica, Inc. 9-5

IXL-001 Issue 2, January 9, 2004
Section 150-500-300
FIND YOUR JOB IN THE LIST BELOW THEN GO TO

PlexView Billing and Traffic System
Install the PlexView Billing and Traffic System .............................................. DLP-541
Upgrade the Billing and Traffic System............................................................ DLP-542
9-6 Telica, Inc.

Section 150-500-400 DLP-501
Issue 2, May 13, 2003
DLP-501 - INSTALL AND PROVISION THE ASCII BILLING

SYSTEM
SUMMARY: This procedure provides instructions for installing and configuring the
ABS application on the ABS Sun server. It also provides steps to verify that the
application has started properly.
This procedure assumes that the server to run the ABS application has already been
installed on the same network as the Plexus and is configured with sufficient disk space.
Knowledge of UNIX and the vi command or other text editor is also required. If you
have questions regarding vi, please contact Telica Technical Services at 1-888-440-8354.
Procedures for provisioning the Plexus for billing are found in the Plexus 9000
Note 1: To avoid local time synchronization problems, Telica strongly

recommends setting both the Plexus and the ABS server system clock to
GMT. For assistance, please contact Telica Technical Services at 1-888-
440-8354.
Note 2: Users of the ABS application are responsible for managing file
space and for any post-processing of ASCII billing records on the ABS
server.
Caution: When using the ASCII Billing System, it is possible to fill the
server's data directory to a point where the 'ls' command will not display
the contents of the data directory. To prevent this from happening, Telica
suggests that the previous month's data files be removed from the data
directory during the first week of a new month.
Step 1. The ASCII Billing Server (ABS) supports the Plexus 9000, release 1.3
(3.1.1.1), 3.5 and 4.3 (3.4.3) or earlier, and must meet these prerequisites:
• Sun Solaris™ 7 or 8 with 256 MB memory and a 10/100 Ethernet
card
• Sun Ultra™ 10 or Sun Netra™ X1 at a minimum
Telica, Inc. 9-7

DLP-501 Section 150-500-400
Issue 2, May 13, 2003
Step 2. Log into the ABS server as root after obtaining the username and password.
Step 3. Once logged onto the ABS server, create the ABS base directory in opt/. Do
this by typing:
↵
mkdir /opt/PlexViewABS↵
Step 4. Change to the PlexView ABS directory by typing:
↵
cd /opt/PlexViewABS↵
Note: In the following steps, the correct version number should be substituted
for x-x-x-x.
Step 5. Obtain a copy of the latest AsciiBilling_SunOS_X-X-X-X.tar file from a system

CD or from Telica Technical Services (1-888-440-8354) and copy this
file to the PlexViewAbs directory on the ABS server.
Note: The tar file will extract directly into /opt/PlexViewABS.
Step 6. Untar the AsciiBilling_SunOs_X-X-X-X.tar file by substituting the correct

version number for x-x-x-x and typing:
↵
tar -xvf AsciiBilling_SunOS_X-X-X-X.tar↵
Step 7. Using vi or any available text editor, edit the newly created configuration file
template. Refer to Table 9-A for an example of the abs.conf file. The only
fields that should be modified are highlighted in bold in the sample abs.conf
file as shown in . If using vi, type:
↵
vi abs.conf↵
Step 8. Change the DATA_DIR field if required.

Step 9. Change the frequency of creating/writing billing files if required. The range is
from 5 to 1440 minutes.
Step 10. If billing files will be archived, remove the comment symbol (#) at the
beginning of the line and set the number of days for saving archived files.
If ARCHIVE is set to a value other than 0, then raw CDR records from the
switch are archived with the same frequency as the ASCII Billing files. The file
name of the raw file is the same with the ASCII Billing file, but the extension is
“.dat”. The ARCHIVE value defines the number of days a .dat file is left on the
system before it is automatically deleted. The maximum number of days is 62.
9-8 Telica, Inc.

Section 150-500-400 DLP-501
Issue 2, May 13, 2003
Table 9-A. Sample abs.conf File

#
SERVER_PORT 1983

DATA_DIR data

FREQUENCY 1440
# Uncomment the following line to have raw CDR records from the
# switch archived with the same frequency as AMA data files.
# The archive files use the same name, but the extension is .dat
# ARCHIVE 31
# Client switches (usually SPA/SPB pairs use the same prefix but it
# is not a requirement)
#
#
#
# ------ ---------- -----------

Telica, Inc. 9-9

DLP-501 Section 150-500-400
Issue 2, May 13, 2003


Step 11. Enter the IP addresses or names of the Client’s SPs that will send billing files to
the server. IP addresses are the addresses set on each Plexus with the
ED-CHASSIS-EQPT TL1 command. Names are obtained using DNS lookup.
Delete extra CLIENT entries.
Step 12. Enter the prefix name for the files to be received from each switch. Typically
the prefix is the same for both SPs of a Plexus.
Step 13. Have all the Clients and Prefixes required been entered?
If YES, then continue to the next step.
If NO, then go to Step 11.
Step 14. The TZ (time zone), SensorID and Office/ID fields are optional fields. If
required, enter the values for the SensorID and Office/ID which will override
the AMA Sensor ID and/or Recording Office ID sent from the switch. Valid
SensorID/OfficeID values between 000000 and 999999.
Step 15. Copy the S99PLXAbs file into the /etc/rc3.d directory by typing:
↵
cp –p S99PLXAbs /etc/rc3.d↵
Step 16. Change directories by typing:
cd ↵
/etc/rc3.d↵
Step 17. Start the S99PLXAbs program by typing:
↵
./S99PLXAbs start↵
Step 18. Verify that the billing process has started by typing:
↵
ps –ef | grep TelicaAbsSrvr↵
Step 19. Change to the directory defined by “DATA_DIR” in the abs.conf file by typing
the following and substituting the correct name for <DATA_DIR>:
↵
cd /opt/PlexViewABS/<DATA_DIR>↵
9-10 Telica, Inc.

Section 150-500-400 DLP-501
Issue 2, May 13, 2003
Step 20. Verify that a log file and connection info file have been created (abs.log and
abs.conn) by typing:
↵
ls -l↵
Step 21. If provisioning for billing must be completed at the Plexus 9000, refer to the
Plexus 9000 Installation and Operation Manual and NTP-018.
Step 22. Generate calls to or from any of the subscribers provisioned on the Plexus.
Note: ASCII text files of billing records, <PREFIX>_yyyymmdd_time.txt, are

created in accordance to the frequency defined in the abs.conf file. These text
files contains comma-delimited billing records.
abs.log contains information regarding the connections (new connections, lost

connections, error messages).
Abs.conn contains the IP address of all connecting switches in hexadecimal

code.
Step 23. Ensure you are in the correct directory by typing the following and substituting
the correct name for <DATA_DIR>:
↵
cd /opt/PlexViewABS/data↵
Step 24. List the name(s) of the <PREFIX>_yyyymmdd_time.txt files by typing:
↵
ls –l *.txt↵
Step 25. Do you want to view a <PREFIX>_yyyymmdd_time.txt file?

If YES, then view file by typing the following substituting the correct
name of the file:
↵
more <PREFIX>_yyyymmdd_time.txt↵
Step 26. Do you want to view another file?

If YES, then Step 25.
If NO, then continue to the next step.
Telica, Inc. 9-11

DLP-501 Section 150-500-400
Issue 2, May 13, 2003
Step 27. Do you want to view the abs.conn file?

If YES, then view file by typing the following:
↵
od –x abs.conn↵
Step 28. Do you want to view the abs.log file?

↵
more abs.log↵
Step 29. Do you want to logout of the ABS server at this time?
If YES, then logout by typing exit↵ ↵

Step 30. YOU HAVE COMPLETED THIS PROCEDURE.
9-12 Telica, Inc.

Section 150-500-400 DLP-502
Issue 2, May 13, 2003
DLP-502 - EDIT CONFIGURATION FILES FOR ASCII BILLING
SUMMARY: This procedure provides the steps to edit the configuration files for the
ASCII Billing Server (ABS) application.
Procedures for provisioning the Plexus for the ABS are found in the Plexus 9000
Step 31. Log into the ABS (ASCII Billing Server) server after obtaining the username
and password of the chosen ABS server. Write access is required if the
checked file requires changes.
Step 32. Once logged onto the ABS server, type:
↵
cd /opt/PlexViewABS↵
Step 33. Using vi or any available text editor, add new switches (IP address or host name
and prefix) or make other required changes. Refer to Table 9-B for a sample
file. Remember to save the *.conf files before exiting. Type:
↵
vi abs.conf↵
Telica, Inc. 9-13

DLP-502 Section 150-500-400
Issue 2, May 13, 2003
Table 9-B. abs.conf File

#
SERVER_PORT 1983

DATA_DIR data

FREQUENCY 1440
# ARCHIVE 31
#
#
#
# ------ ---------- -----------

9-14 Telica, Inc.

Section 150-500-400 DLP-502
Issue 2, May 13, 2003


Step 34. Stop the ABS Server by typing the following:
↵
/etc/rc3.d/S99PLXAbs stop↵
Step 35. Start the ABS Server by typing the following:
↵
/etc/rc3.d/S99PLXAbs start↵
Step 36. Determine the process ID by typing the following:
↵
ps –e –o pid –o args | grep TelicaAbsSrvr↵
Response: 1234 TelicaABsSrvr
Comment: 1234 in the preceding response is the pid number which is

used in the following step.
Step 37. Stop the ABS Server by typing the following:
↵
kill XXXX↵
Comment: Substitute the pid number of the preceding response for

XXXX (i.e., kill 1234).
Step 38. Restart the TelicaAbsSrvr program by typing :
↵
./TelicaAbsSrvr abs.conf↵
Step 39. Logout of the ABS server by typing:
↵
exit↵
Telica, Inc. 9-15

DLP-502 Section 150-500-400
Issue 2, May 13, 2003
NOTES:
9-16 Telica, Inc.

Section 150-500-400 DLP-503
Issue 2, May 13, 2003
DLP-503 - UPGRADE THE ASCII BILLING APPLICATION
SUMMARY: This procedure provides instructions for upgrading the ASCII Billing
Server (ABS) application on a Sun server.
Knowledge of UNIX and vi command or other text editor is also required. If you have
questions regarding vi, please contact Telica Technical Services at 1-888-440-8354.
Procedures for provisioning the Plexus for the ABS are found in the Plexus 9000

recommends setting both the Plexus and the server system clock to GMT.
For assistance, please contact Telica Technical Services at 1-888-440-8354.
Note 2: Users of the applications are responsible for managing file space
and for any post-processing of records on the server.
Step 1. The ASCII Billing System (ABS) supports the Plexus 9000, release 3.1.0.0 or
greater, and must meet these prerequisites:
• Sun Solaris™ 7 or 8 with 256 MB memory and a 10/100 Ethernet card
Step 2. Log into the ABS server after obtaining the username and password.
Step 3. Once logged onto the server, create the upgrade directory in opt/ if it does not
already exist. Do this by typing:
↵
mkdir /opt/PlexViewABS/upgrade↵
Step 4. Change to the upgrade directory by typing the following appropriate command:
↵
cd /opt/PlexViewABS/upgrade↵
Telica, Inc. 9-17

DLP-503 Section 150-500-400
Issue 2, May 13, 2003
In the following steps, the correct version number should be substituted for x-
x-x-x.
Step 5. Obtain a copy of the latest AsciiBilling_SunOS_X-X-X-X.tar from a system CD

or from Telica Technical Services (1-888-440-8354) and copy this file to the
“upgrade” directory on the server.
The tar file will extract directly into /opt/PlexViewABS/upgrade or
/opt/PlexViewAMA/upgrade directory
Step 6. Untar the AsciiBilling_SunOs_X-X-X-X.tar file by substituting the correct

version number for x-x-x-x and typing:
↵
tar -xvf AsciiBilling_SunOS_X-X-X-X.tar↵
Step 7. Compare the new abs.conf file in the upgrade directory with the existing
abs.conf file. A sample of the file is shown in Table 9-C. Sample abs.conf File
found at the end of this procedure. Does the existing abs.conf file require any
changes?
Step 8. Using vi or any available text editor, make the appropriate changes and save. If
using vi, type:
↵
vi abs.conf↵
Step 9. Stop the S99PLXAbs or S99PLXAma program by typing the following

appropriate command:
↵
/etc/rc3.d/S99PLXAbs stop↵
Step 10. Move following file by typing:
↵
mv Version.txt ..↵
Step 11. Move TelicaAbsSrvr file by typing:
↵
mv TelicaAbsSrvr..↵
Step 12. If the S99PLXAbs file is different from existing, copy it into the /etc/rc3.d
directory by typing:
↵
cp –p S99PLXAbs /etc/rc3.d↵
9-18 Telica, Inc.

Section 150-500-400 DLP-503
Issue 2, May 13, 2003
Step 13. Start the S99PLXAbs program by typing:
↵
/etc/rc3.d/S99PLXAbs start↵
↵
ps –ef | grep Tel↵
Step 15. Change to the directory defined by “DATA_DIR” in the abs.conf file by typing
the following and substituting the correct name for <DATA_DIR>:
↵
cd /opt/PlexViewABS/data↵
Step 16. Tail the log file to verify connection to switch by typing:
↵
tail abs.log↵
Step 17. Do you want to logout of the server at this time?

Table 9-C. Sample abs.conf File

#
SERVER_PORT 1983

DATA_DIR data

FREQUENCY 1440
Telica, Inc. 9-19

DLP-503 Section 150-500-400
Issue 2, May 13, 2003

# ARCHIVE 31
#
#
#
# ------ ---------- -----------



9-20 Telica, Inc.

Section 150-500-400 DLP-511
Issue 2, May 13, 2003
DLP-511 - INSTALL AND PROVISION AMA LITE APPLICATION
SUMMARY: This procedure provides instructions for installing and configuring the
AMA Lite application on the Sun server. It also provides steps to verify that the
application has started properly.
This procedure assumes that the server to run the AMA Lite application has already been
installed on the same network as the Plexus and is configured with sufficient disk space.
Procedures for provisioning the Plexus for the AMA Lite are found in the Plexus 9000

recommends setting both the Plexus and the AMA Lite server system clock
to GMT. For assistance, please contact Telica Technical Services at 1-888-
440-8354.
Note 2: Users of the AMA Lite application are responsible for managing
file space and for any post-processing of ASCII billing records on the AMA
Lite server.
Caution: When using the AMA Lite application, it is possible to fill the
Step 1. The AMA Lite application supports the Plexus 9000, release 1.3 (3.1.1.1), 3.5
and 4.3 (3.4.3) or greater, and must meet these prerequisites:
card
Telica, Inc. 9-21

DLP-511 Section 150-500-400
Issue 2, May 13, 2003
Step 2. Log into the AMA Lite server as root after obtaining the username and
password.
Step 3. Once logged onto the AMA Lite server, create the AMA Lite base directory in
opt/. Do this by typing:
↵
mkdir /opt/PlexViewAMA↵
Step 4. Change to the PlexView AMA directory by typing:
↵
cd /opt/PlexViewAMA↵
Note: In the following steps, the correct version number should be substituted
for x-x-x-x.
Step 5. Obtain a copy of the latest PLXsAMA_Billing_SunOS_X-X-X-X.tar file from a

system CD or from Telica Technical Services (1-888-440-8354) and copy this
file to the PlexViewAMA directory on the AMA Lite server.
Note: The tar file will extract directly into /opt/PlexViewAMA.
Step 6. Untar the PLXsAMA_Billing_SunOS_X-X-X-X.tar file by substituting the

correct version number for x-x-x-x and typing:
↵
tar -xvf PLXsAMA_Billing_SunOS_X-X-X-X.tar↵
Step 7. Using vi or any available text editor, edit the newly created configuration file
template. Refer to Table 9-D for an example of the ama.conf file. The only
fields that should be modified are highlighted in bold in the sample ama.conf
file as shown in . If using vi, type:
↵
vi ama.conf↵
Step 8. Change the frequency of creating/writing billing files if required. The range is
from 5 to 1440 minutes.
Step 9. If AMA data files that have accumulated will be deleted, remove the comment
symbol (#) at the beginning of the “PURGENULLDATA” True line
9-22 Telica, Inc.

Section 150-500-400 DLP-511
Issue 2, May 13, 2003
Table 9-D. Sample ama.conf File

# Telica AMA Billing Server configuration environment
#
SERVER_PORT 1983

DATA_DIR ama_data

# Must be integer interval of minutes within 24 hours.
# Intervals are always based on an initial start time of Midnight.
FREQUENCY 1440
# accumulated zero records deleted when we rotate filenames to
# the next collection interval every FREQUENCY minutes.
PURGENULLDATA True
# ARCHIVE 31
#
# same prefix should be in the same time zone.Time zone is used to
# calculate the time in the header records and in the file names.
#

#
Telica, Inc. 9-23

DLP-511 Section 150-500-400
Issue 2, May 13, 2003

# ------ ---------- -----------



Step 10. If billing files will be archived, remove the comment symbol (#) at the
beginning of the line and set the number of days for saving archived files.
If ARCHIVE is set to a value other than 0, then raw CDR records from the
switch are archived with the same frequency as the ASCII Billing files. The file
name of the raw file is the same with the ASCII Billing file, but the extension is
“.dat”. The ARCHIVE value defines the number of days a .dat file is left on the
system before it is automatically deleted. The maximum number of days is 62.
Step 11. Enter the IP addresses or names of the Client’s SPs that will send billing files to
the server. IP addresses are the addresses set on each Plexus with the
ED-CHASSIS-EQPT TL1 command. Names are obtained using DNS lookup.
Delete extra CLIENT entries.
Step 12. Enter the prefix name for the files to be received from each switch. Typically
the prefix is the same for both SPs of a Plexus.
Step 13. Have all the Clients and Prefixes required been entered?
Step 14. The TZ (time zone), SensorID and Office/ID fields are optional fields. If
required, enter the values for the SensorID and Office/ID which will override
the AMA Sensor ID and/or Recording Office ID sent from the switch. Valid
SensorID/OfficeID values between 000000 and 999999.
Step 15. Copy the S99PLXsAma file into the /etc/rc3.d directory by typing:
↵
cp –p S99PLXsAma /etc/rc3.d↵
9-24 Telica, Inc.

Section 150-500-400 DLP-511
Issue 2, May 13, 2003
Step 16. Start the S99PLXsAma program by typing:
↵
/etc/rc3.d/S99PLXsAma start↵
↵
ps –ef | grep TelicaAmaSrvr↵
Step 18. Change to the directory defined by “DATA_DIR” in the ama.conf file by
typing the following and substituting the correct name for <DATA_DIR>:
↵
cd /opt/PlexViewAMA/ama_data↵
Step 19. Verify that a log file and connection info file have been created (ama.log and
ama.conn) by typing:
↵
ls –l ama.*↵
Step 20. If provisioning for billing must be completed at the Plexus 9000, refer to the
Plexus 9000 Installation and Operation Manual and NTP-018.
Step 21. Generate calls to or from any of the subscribers provisioned on the Plexus.
Note: AMA binary files of billing records, <PREFIX>_yyyymmdd_time.ama,

are created in accordance to the frequency defined in the ama.conf file. These
are binary ama records.
ama.log contains information regarding the connections (new connections, lost

connections, error messages).
Step 22. Do you want to view the ama.log file?

↵
more ama.log↵
Step 23. Do you want to logout of the AMA Lite server at this time?

Telica, Inc. 9-25

DLP-511 Section 150-500-400
Issue 2, May 13, 2003
NOTES:
9-26 Telica, Inc.

Section 150-500-400 DLP-512
Issue 2, May 13, 2003
DLP-512 - EDIT CONFIGURATION FILES FOR AMA LITE
SUMMARY: This procedure provides the steps to edit the configuration files for
AMA Lite.
Procedures for provisioning the Plexus for the AMA Lite are found in the Plexus 9000
password of the chosen AMA Lite server. Write access is required if the
checked file requires changes.
Step 2. Once logged onto the AMA Lite server, type:
↵
cd /opt/PlexViewAma↵
Step 3. Using vi or any available text editor, add new switches (IP address or host name
and prefix) as shown in Table 9-E. Remember to save the .conf files before
exiting. Type:
↵
vi ama.conf↵
Telica, Inc. 9-27

DLP-512 Section 150-500-400
Issue 2, May 13, 2003
Table 9-E . ama.conf File

# Telica Billing Server configuration environment
#
SERVER_PORT 1983

DATA_DIR ama_data

# Must be integer interval of minutes within 24 hours. Intervals
# are always based on an initial start time of Midnight.
FREQUENCY 1440
# accumulated zero records deleted when we rotate filenames to the
# next collection interval every FREQUENCY minutes.
# PURGENULLDATA True
# ARCHIVE 0
# The prefix may be followed by an optional field that will override

# ------ ---------- -----------
CLIENT bostonSPA Boston
CLIENT bostonSPB Boston

CLIENT denverSPA DenverA SensorID=123456

CLIENT denverSPB DenverB OfficeID=789012

CLIENT See Note below.
9-28 Telica, Inc.

Section 150-500-400 DLP-512
Issue 2, May 13, 2003
Step 4. Stop the AMA Lite Server by typing the following:
↵
/etc/rc3.d/S99PLXsAma stop↵
Step 5. Start the AMA Lite Server by typing the following:
↵
/etc/rc3.d/S99PLXsAma start↵
Step 6. Verify process is running by typing the following:
↵
ps –ef | grep TelicaAmaSrvr↵
Step 7. Logout of the AMA Lite server by typing:
↵
exit↵
Telica, Inc. 9-29

DLP-512 Section 150-500-400
Issue 2, May 13, 2003
NOTES:
9-30 Telica, Inc.

Section 150-500-400 DLP-513
Issue 2, May 13, 2003
DLP-513 - UPGRADE THE AMA LITE APPLICATION
SUMMARY: This procedure provides instructions for upgrading the AMA Lite
application on a Sun server.
Knowledge of vi or other text editor is also required. If you have questions regarding vi,
please contact Telica Technical Services at 1-888-440-8354.
Procedures for provisioning the Plexus for the AMA Lite application are found in the

recommends setting both the Plexus and the server system clock to GMT.
For assistance, please contact Telica Technical Services at 1-888-440-8354.
Note 2: Users of the applications are responsible for managing file space
and for any post-processing of records on the server.
Step 1. The AMA Lite application supports the Plexus 9000, release 3.1.0.0 or greater,
and must meet these prerequisites:
card
password.
Step 3. Once logged onto the server, create the upgrade directory in opt/ if it does not
already exist. Do this by typing:
↵
mkdir /opt/PlexViewAMA/upgrade↵
Step 4. Change to the upgrade directory by typing the following command:
↵.
cd /opt/PlexViewAMA/upgrade↵
Telica, Inc. 9-31

Lucent1 PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

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

Lucent1 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Lucent Gateway Platform

Billing and Traffic Collection Guide

Part Number 255-400-403R3.8

Copyright 2005 Lucent Technologies

For permission to reproduce or distribute, please contact the following:

Product Development Manager 1 888-LTINFO6 (domestic)

Mandatory customer information

The order number of this document is 255-400-403R3.8.

Information product support

Release Notes can be obtained by contacting Telica Technical Services at 888-440-

Contents 150-050-100 Issue 5, Jan. 9, 2004

1. PlexView Pro Billing System ........................................................1-1

2. PlexView ASCII Billing Server (ABS).........................................2-1

3. PlexView AMA Lite.......................................................................3-1

4. PlexView Traffic Collection Application (TCA).........................4-1

5. PlexView Billing and Traffic System ...........................................5-1

6. ASCII Billing Reports .....................................................................6-1

7. AMA Lite Reports ...........................................................................7-1

8. Traffic Statistics Reports ................................................................8-1

iii Telica, Inc

Table 9-I. S99PLXStats File ..........................................................................................9-63

About This Guide

Architecture Prior to System Software Version 3.8

Architecture for System Software Version 3.8 or Higher

Part Manual Title Description

vii Telica, Inc

Part Manual Title Description

This guide is organized into the following sections:

Telica, Inc viii

Using the CD-ROM

Conventions Used in This Guide

Note: To avoid local time synchronization problems, Telica strongly

1.3 PlexView Pro Billing System Requirements

1.4 Automatic Message Accounting Data Networking System

Generating Data Data Processing Application

Figure 1-1. AMADNS Architecture

1.5 PlexView AMA Billing Module

1-2 Telica, Inc.

CDRs BAF Files

Figure 1-2. PlexView AMA Billing

1.5.1 Plexus 9000 Generating System

If the Plexus fails over to the standby System Processor, it immediately

Telica, Inc. 1-3

1.5.2 Data Server

1.5.3 Data Processing and Management System (DPMS)

1-4 Telica, Inc.

2.1 Introduction ..........................................................................................................2-1

Note: To avoid local time synchronization problems, Telica strongly

• No loss of records in the event of a short-term communications

2.3 How the Transfer Works

2-2 Telica, Inc.

Refer to Figure 2-1 for an illustrated example of the ABS conversion

Circular Allows ASCII files to be written

Memory The customer is responsible for

Figure 2-1. PlexView ASCII Billing Conversion Details

2.3.1 ABS Verification of Plexus 9000 IP Address

Telica, Inc. 2-3

Table 2-A. Sample abs.conf File

# Working Directory - contains data, connection info and log files

# ASCII Billing file writing/creation frequency in minutes

CLIENT sfoSPA SanFrancisco

2-4 Telica, Inc.

CLIENT denverSPA DenverA TZ=MST7MDT SensorID=123456