user manual

5-10
Cisco Billing and Measurements Server User’s Guide
OL-3351-01
Chapter 5 Configuring BAMS for BAF Output
Call Area Provisioning Example
Assumptions Used in This Example
In Figure 5-1, some origination points can call to any point within the metropolitan area, with no toll
charged. A call type is determined by BAMS as a relationship between zones. BAMS can be configured
to specify that a certain call type produces, or does not produce, a billing record. Obviously, the
downstream billing system can determine which records are billable and which are informational only.
Keep in mind the following general information about the metropolitan area shown in Figure 5-1:
• There are three LATAs, labeled 1, 2, and 3.
• Any zone that is adjacent to another zone within the same LATA is marked as FLAT.
• Calls that cross LATAs are marked as interLATA.
• A call that originates and terminates in zones that are not adjacent, but that are in the same LATA,
is designated as MESSAGE to indicate a banded billing rate.
From the North American Bell System, the concept of LATAs is a traditional boundary concept that is
supported by BAMS. These are geographic regions, defined by NPANXX containment. BAF output
sometimes requires LATA assignment for certain record types. Because BAMS is not geared toward
local exchange routing guide (LERG) data, a downstream system could use the LATA designation for
other purposes.
LERG data is not resident on BAMS.