Filter
Top Products
5-5
Cisco Billing and Measurements Server User’s Guide
OL-3351-01
Chapter 5 Configuring BAMS for BAF Output
Exception and Special Processing
(244)TrunkID : 380030234c
Module 104 (Trunk ID)
(244)TrunkID : 680042113c
Module 000 (Final Module)
============================== End of BAF Record =========================
Exception and Special Processing
Overriding Call Types
In some cases, a carrier might want to override a call type. Some examples include:
• Calls between a subset of NPA-NXXs in two different zones being treated differently from all other
NPA-NXXs in the same zones
• InterLATA calls being treated as intraLATA calls for record-generation purposes
Use the RATE-EXC tag ID to override the default call-type classification. For more information, see the
“RATE-EXC Tag ID” section on page 4-16.
Processing 7-Digit Numbers
If only 7 digits are populated in the calling and called numbers, the system acts as if each incoming trunk
group visible to BAMS has a default NPA and prefixes this NPA to each 7-digit number. The full
NPA-NXX is required for BAMS to perform the zone analysis. Each trunk has a default originating and
terminating NPA, defined in the orgnpa and trmnpa fields, in the Trunk Group table. These fields are
used only if the incoming number is 7 digits.
Processing Toll-Free Calls
A toll-free call can be identified if its dialed number prefix is contained in the Tollfree table. The default
toll-free prefixes are: 800, 877, 888, 1800, 1877, and 1888. Toll-free calls have their own call-type
category. A zone analysis is still performed, but the call type is overridden with the toll-free call type.
Processing International Calls
Records for international calls are processed like all other records, using zone analysis. Based on the
default case, international numbers are classified as interLATA calls.
Processing LNP Calls
Local number portability (LNP) calls are processed like all other records, using zone analysis. The only
special processing involved is the propagation of BAF module 720. This module is generated in response
to the presence of the lnp_dip field in the CDB.