C H A P T E R 5 Configuring BAMS for BAF Output Overview This chapter describes how to configure the Cisco Billing and Measurements Server (BAMS) for Bellcore AMA (Automatic Message Accounting) Format (BAF) records. BAMS provides a mediation interface for Cisco Media Gateway Controller (MGC) systems. The purpose of BAMS is to provide enhanced data collection and processing functions, which correspond to those found in a traditional Class 4 tandem switch.
Chapter 5 Configuring BAMS for BAF Output Generating BAF Records Note Before configuring BAMS to generate billing and measurements, you should familiarize yourself with Chapters 3 to 9 of this guide. Note BAMS performs only limited data validation on the information provisioned into its tables. It is important that you enter data carefully and understand the algorithms and their implementation.
Chapter 5 Configuring BAMS for BAF Output Identifying Call Types Note The prefix of the files polled by the POL task is the input prefix for FMT, the initial processing task. Changing the parameter file-prefix1 or file-prefix2 in the Poll table automatically changes the input prefix of the FMT task. This change takes effect on the next startup of the system. 2. BAMS correlates the CDBs into a merged call structure. This is performed by the Correlation (COR) task. 3. Each call type is categorized.
Chapter 5 Configuring BAMS for BAF Output Identifying Call Types Default BAF Structure Codes and Call Types Table 5-2 defines the default BAF structure codes and call types. The table lists the call categories, call types, and answered and unanswered structure codes.
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.
Chapter 5 Configuring BAMS for BAF Output BAF Output Provisioning Example Processing Transit/Tandem Calls InterLATA calls can originate at, terminate at, or pass through the Cisco MGC generating the BAF records. Originating records are distinguished from terminating records by the appropriate use of the BAF calltype field in the Map Type table. BAMS identifies a call as an originating interLATA call if only the egress trunk group is populated.
Chapter 5 Configuring BAMS for BAF Output BAF Output Provisioning Example prov-add:RATING-TYPE:orgzone=3,trmzone=13,ratetype=”INTRALATA” prov-add:RATING-TYPE:orgzone=4,trmzone=14,ratetype=”INTERLATA” prov-add:RATING-TYPE:orgzone=5,trmzone=15,ratetype=”INTERLATA” prov-add:RATING-TYPE:orgzone=6,trmzone=16,ratetype=”FLAT” prov-add:RATING-TYPE:orgzone=7,trmzone=17,ratetype=”FLAT” prov-add:RATING-TYPE:orgzone=7,trmzone=18,ratetype=”FLAT” prov-add:MSC-PARMS:type=”baf*bin”,polled=2,alarm=5,agealarm=5,agelevel=6,
Chapter 5 Configuring BAMS for BAF Output BAF Output Provisioning Example set-nodename::name="virginia" prov-add:poll:host-name1="va-harley",rem-dir1="/opt/CiscoMGC/var/bam",file-prefix1="cdr*", file-suffix1=".bin",host-name2="va-davidson",rem-dir2="/opt/CiscoMGC/var/bam",file-prefix2 ="cdr*",file-suffix2=".
Chapter 5 Configuring BAMS for BAF Output Call Area Provisioning Example prov-add:rating-type:ORGZONE=1,TRMZONE=13,RATETYPE="MESSAGE" prov-add:rating-type:ORGZONE=1,TRMZONE=14,RATETYPE="INTRALATA" prov-add:rating-type:ORGZONE=15,TRMZONE=16,RATETYPE="INTRALATA" prov-add:RATE-EXC:orgnpanxx=516121,trmnpanxx=516112,ratetype="MESSAGE" prov-add:TOLLFREE:digits=900222 prov-add:trunkgrp:TRUNKGRP=8003,CONNECTION="D",ORGNPA=804,TRMNPA=703,circuits=3000 prov-add:trunkgrp:TRUNKGRP=8004,CONNECTION="T",ORGNPA=703,TRMNP
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.
Chapter 5 Configuring BAMS for BAF Output Call Area Provisioning Example Figure 5-1 River City Metropolitan Example Zone 1 River City VSC3000 202–344 202–345 202–261 202–268 202–333 202–334 202–335 202–223 202–224 202–225 LATA - 1 Zone 2 Zone 3 LATA - 2 LATA - 1 LATA - 2 202–767 202–768 202–769 703–621 703–622 202–878 202–879 202–880 Zone 4 LATA - 2 703–333 703–334 703–335 Zone 5 703–434 703–435 703–436 703–298 703–299 LATA - 3 Zone 7 Zone 8 LATA - 3 Zone 6 LATA - 3 703–545 703–546 70
Chapter 5 Configuring BAMS for BAF Output Call Area Provisioning Example Note Zoning provides a mechanism for differentiating between rating types (for example, flat rate and message calls).
Chapter 5 Configuring BAMS for BAF Output Call Area Provisioning Example Banded Message Rates In Figure 5-1, many zones are not adjacent to other zones. The following commands set up MESSAGE rate call types for calls from zone 6 and zone 8, which are not adjacent to each other but are in the same LATA. In the example shown in Figure 5-1, many zone relationships of this type could occur.
Chapter 5 Configuring BAMS for BAF Output Call Area Provisioning Example Configuring Toll-Free Calls Different countries have different designations for toll-free dialing. For this reason, BAMS maintains the Tollfree table for the NPANXX combinations that are considered toll free. Note Any 800, 888, or 877 NPA results in a toll-free BAF record, overriding any zone or rating type designations.
Chapter 5 Configuring BAMS for BAF Output BAF Configuration Parameters Step 1 Note Determine if the network is switched or is nailed up. For a nailed up (Cisco SC2200) connection, define the field values in the Nailed Connection table using the SIGPATH tag ID. The fields are SIGPATH, BEARCHAN, TRUNKGRP, and TRUNKNUM. SIGPATH and BEARCHAN parameters are both hex entries and should be prefixed by 0x. Step 2 Enter switch data in the Switch Information table.
Chapter 5 Configuring BAMS for BAF Output BAF Configuration Parameters Adding a New NPANXX (Zone Membership) Use the NPANXX tag ID to add new NPANXX information. Refer to the “NPANXX Tag ID” section on page 4-13 for field name descriptions and values.