CIBER Batch
CIBER records are made up of files called batches. For each SID-SID combination, the Clearinghouse Service creates a header record (record type 01), selects all the usage for the SID-SID combination, writes the record, saves the batch summary, and creates a trailer record (record type 98). These header and trailer records contain the call detail information necessary to process it as an outcollect.
TAP records contain two batches – a Transfer Batch and a Notification Batch. A Transfer Batch contains a listing of all calls made by roaming partner subscribers. A Notification Batch is (simply a message? ) sent to a roaming partner if there is no usage to send. The Transfer batches are created with a common file naming scheme. Each name contains the TADIG code for the sending and receiving PMN as well as the file sequence number. These files include the GSM call detail information in TAP format that is needed to process these as outcollects.
For both CIBER batch and TAP batch records, the system finds the appropriate Roaming Agreement and applies the correct charge. If a Daily Access Charge is associated with the Roaming Agreement, this is added to the file for each day that each subscriber uses your service.
Note:
A subscriber might be charged twice for the daily access charge if one of his records has been recycled and not fixed before Outcollect process is started. To avoid overcharging a roaming subscriber, be sure to rectify all recycled records before Outcollect is performed.