AMA-V16

InformationDescription of Output Data P30308-X2058-K160-03-7617

Description of Output Data for Postprocessing AMA for subscriber charging PSTN- and TFS service-subscriber

Information

Description of Output Data

The document comprises a total of 234 pages. All pages have issue number 03.

2

P30308-X2058-K160-03-7617

Table of Contents

0 General Information

7

0.1 Status information...............................................................................................7 0.2 History ..................................................................................................................7 0.3 References ...........................................................................................................7 0.4 Terms and Abbreviations ...................................................................................9 0.5 Key Word / Descriptor....................................................................................... 11 0.6 List of figures and tables .................................................................................. 11

1 Introduction

13

1.1 Overview of the document ............................................................................... 14 1.2 Scope.................................................................................................................. 14 1.3 Terminology....................................................................................................... 15

2 Description of the File Format

19

2.1 Overview of AMA storage and transfer possibilities...................................... 19 2.2 File format on CP disk ...................................................................................... 20 2.3 File format on MP disk ...................................................................................... 21 2.4 File format on MTD or MOD .............................................................................. 21

3 Remarks on the File Contents 4 Data Record Description

23 25

4.1 AMA Record....................................................................................................... 25 4.2 System and Filler Records ............................................................................... 28 4.3 General Record Coding Details........................................................................ 284.3.1 Coding of binary fields....................................................................................................28 4.3.2 Coding of packed digits fields .......................................................................................29 4.3.3 Coding of character fields ..............................................................................................29

5 Data Field Description

31

5.1 AMA Record....................................................................................................... 315.1.1 Fixed Part (Header) .............................................................................................................31 5.1.2 Data Packages.....................................................................................................................42 5.1.2.1 Package 100: Date / Time / Duration ..............................................................................42 5.1.2.2 Package 101: Partner Directory Number .......................................................................44 5.1.2.3 Package 102: Service Info...............................................................................................46 5.1.2.4 Package 103: Charge Units For Connection .................................................................51 5.1.2.5 Package 104: Charge Units For Facility Usage.............................................................51 5.1.2.6 Package 105: Trunk Identification Incoming.................................................................53 5.1.2.7 Package 106: Trunk Identification Outgoing.................................................................54 5.1.2.8 Package 107: Trunk Identification Incoming (CIC Format)..........................................55 5.1.2.9 Package 108: Trunk Identification Outgoing (CIC Format)..........................................56 5.1.2.10 Package 110: Connection Identification Number .......................................................57 5.1.2.11 Package 111: Facilities Used By Owner ......................................................................58 5.1.2.12 Package 112: Facilities Used By Partner.....................................................................61

P30308-X2058-K160-03-7617

3

Table of Contents

5.1.2.13 Package 113: Facility Input ...........................................................................................62 5.1.2.14 Package 116: Date / Time ..............................................................................................66 5.1.2.15 Package 118: Digit String..............................................................................................67 5.1.2.16 Package 120: Calling Party Category...........................................................................68 5.1.2.17 Package 122: Zone.........................................................................................................69 5.1.2.18 Package 125: Account Code.........................................................................................73 5.1.2.19 Package 128: New Destination .....................................................................................74 5.1.2.20 Package 130: Traffic Quality Data ................................................................................76 5.1.2.21 Package 134: Durations Before Answer......................................................................79 5.1.2.22 Package 135: Chargeband ............................................................................................80 5.1.2.23 Package 136: UUS3 Counters.......................................................................................82 5.1.2.24 Package 138: B Meter Pulses .......................................................................................83 5.1.2.25 Package 139: Release Indication .................................................................................83 5.1.2.26 Package 142: Calling Party Number.............................................................................84 5.1.2.27 Package 143: IP/SN Charge Data .................................................................................87 5.1.2.28 Package 145: Billing CAC .............................................................................................89 5.1.2.29 Package 146: Third Party Number................................................................................94 5.1.2.30 Package 147: Tariff Info.................................................................................................98 5.1.2.31 Package 148: CAC New Destination ..........................................................................108 5.1.2.32 Package 149: Global Call Reference..........................................................................109 5.1.2.33 Package 150: Audit Trail .............................................................................................111 5.1.2.34 Package 151: Business Group Identification............................................................113 5.1.2.35 Package 152: Centrex Numbers .................................................................................113 5.1.2.36 Package 153: Received Called Party Number...........................................................117 5.1.2.37 Package 154: Additional Call Indicators....................................................................119 5.1.2.38 Package 155: Add On Tariff ........................................................................................124 5.1.2.39 Package 156: Advised Cumulated Charges ..............................................................129 5.1.2.40 Package 157: Outgoing PA Identification..................................................................130 5.1.2.41 Package 159: Additional Calling Party Number........................................................133 5.1.2.42 Package 167: Additional Numbers.............................................................................135 5.1.2.43 Package 168: Called Party Number............................................................................137 5.1.2.44 Package 170: Redirecting Number.............................................................................140 5.1.2.45 Package 171: Sent Called Party Number...................................................................143 5.1.2.46 Package 172: System Provided Number ...................................................................145 5.1.2.47 Package 178: Exchange Info.......................................................................................147 5.1.2.48 Package 179: Service Subscriber Number................................................................149 5.1.2.49 Package 183: Sent CAC...............................................................................................150 5.1.2.50 Package 184: MLPP Level ...........................................................................................151 5.1.2.51 Package 186: IN Service Key ......................................................................................153 5.1.2.52 Package 187: Received CAC.......................................................................................153 5.1.2.53 Package 191: Signalling Point Code ..........................................................................154 5.1.2.54 Package 192: Sent Calling Party Number..................................................................156 5.1.2.55 Package 193: Sent Redirecting Number....................................................................158 5.1.2.56 Package 194: Sent Calling Party Category................................................................160 5.1.2.57 Package 195: Original Calling Party Category..........................................................161 5.1.2.58 Package 196: Trunk Info..............................................................................................162 5.1.2.59 Package 198: Durations in 100 msec.........................................................................164 5.1.2.60 Package 199: Received Charge Determination Information....................................165 5.1.2.61 Package 204: Access Data..........................................................................................166 5.1.2.62 Package 205: Non Charged Facilities Used By Owner ............................................170 5.1.2.63 Package 209: Accumulated Currency Charges ........................................................171 5.1.2.64 Package 211: Additional Release Cause ...................................................................173 5.1.3 Project Specific Data Packages.......................................................................................177 5.1.3.1 Package 117: Project Specific Data .............................................................................177 5.1.3.2 Package 140: Incoming Route ID .................................................................................178 5.1.3.3 Package 141: Outgoing Route ID .................................................................................180 5.1.3.4 Package 176: ITU Calling Party Category....................................................................181 5.1.3.5 Package 177: Project Specific Service ........................................................................182 5.1.3.6 Package 181: Internet Session Info .............................................................................183 4 P30308-X2058-K160-03-7617

Table of Contents

5.2 Date Time Change Record.............................................................................. 186 5.3 Overflow Record.............................................................................................. 187 5.4 Breakdown Record.......................................................................................... 188 5.5 Filler Records .................................................................................................. 189

6 Operation Notes

191

6.1 Operating instructions for activating the AMA feature ................................ 191 6.2 Operating instructions for customizing the AMA ticket .............................. 191 6.3 Operating instructions for controlling the generation of AMA-tickets ....... 194 6.4 Hints for the Postprocessing ......................................................................... 1966.4.1 Identifying the contents of the IA.ICAMA file.................................................................196 6.4.2 Identifying the contents of one variable length AMA record .......................................196 6.4.3 Average Record length.....................................................................................................198

6.5 Delta to Previous Versions ............................................................................. 1986.5.1 Version 6.2 .........................................................................................................................198 6.5.2 Version 7.1 .........................................................................................................................199 6.5.3 Version 8 ............................................................................................................................199 6.5.4 Version 9 ............................................................................................................................199 6.5.5 Version 10 ..........................................................................................................................199 6.5.6 Version 11 ..........................................................................................................................200 6.5.7 Version 12 ..........................................................................................................................200 6.5.8 Version 13A .......................................................................................................................201 6.5.9 Version 14A .......................................................................................................................203 6.5.10 Version 15 ........................................................................................................................204 6.5.11 Version 16 ........................................................................................................................205

7 Examples

207

7.1 Fixed Part (Header) ......................................................................................... 207 7.2 Data Packages ................................................................................................. 2087.2.1 Package 100: Date / Time / Duration ...............................................................................208 7.2.2 Package 101: Partner Directory Number ........................................................................208 7.2.3 Package 102: Service Info................................................................................................208 7.2.4 Package 103: Charge Units For Connection ..................................................................209 7.2.5 Package 104: Charge Units For Facility Usage..............................................................209 7.2.6 Package 105: Trunk Identification Incoming..................................................................209 7.2.7 Package 106: Trunk Identification Outgoing..................................................................210 7.2.8 Package 107: Trunk Identification Incoming (CIC Format)...........................................210 7.2.9 Package 108: Trunk Identification Outgoing (CIC Format)...........................................210 7.2.10 Package 110: Connection Identification Number ........................................................210 7.2.11 Package 111: Facilities Used By Owner .......................................................................211 7.2.12 Package 112: Facilities Used By Partner......................................................................211 7.2.13 Package 113: Facility Input ............................................................................................211 7.2.14 Package 116: Date / Time ...............................................................................................211 7.2.15 Package 118: Digit String...............................................................................................212 7.2.16 Package 120: Calling Party Category............................................................................212 7.2.17 Package 122: Zone..........................................................................................................212 7.2.18 Package 125: Account Code..........................................................................................213 7.2.19 Package 128: New Destination ......................................................................................213 7.2.20 Package 130: Traffic Quality Data .................................................................................213 7.2.21 Package 134: Durations Before Answer.......................................................................214 7.2.22 Package 135: Chargeband .............................................................................................214 7.2.23 Package 136: UUS3 Counters........................................................................................214 7.2.24 Package 138: B Meter Pulses ........................................................................................215

P30308-X2058-K160-03-7617

5

Table of Contents

7.2.25 Package 139: Release Indication ..................................................................................215 7.2.26 Package 142: Calling Party Number..............................................................................215 7.2.27 Package 143: IP/SN Charge Data ..................................................................................216 7.2.28 Package 145: Billing CAC ..............................................................................................216 7.2.29 Package 146: Third Party Number.................................................................................216 7.2.30 Package 147: Tariff Info..................................................................................................216 7.2.31 Package 148: CAC New Destination .............................................................................219 7.2.32 Package 149: Global Call Reference.............................................................................219 7.2.33 Package 150: Audit Trail ................................................................................................220 7.2.34 Package 151: Business Group Identification...............................................................221 7.2.35 Package 152: Centrex Numbers ....................................................................................221 7.2.36 Package 153: Received Called Party Number..............................................................222 7.2.37 Package 154: Additional Call Indicators.......................................................................222 7.2.38 Package 155: Add On Tariff ...........................................................................................222 7.2.39 Package 156: Advised Cumulated Charges .................................................................223 7.2.40 Package 157: Outgoing PA Identification.....................................................................224 7.2.41 Package 159: Additional Calling Party Number...........................................................224 7.2.42 Package 167: Additional Numbers ................................................................................224 7.2.43 Package 168: Called Party Number...............................................................................225 7.2.44 Package 170: Redirecting Number................................................................................226 7.2.45 Package 171: Sent Called Party Number......................................................................226 7.2.46 Package 172: System Provided Number ......................................................................226 7.2.47 Package 178: Exchange Info..........................................................................................227 7.2.48 Package 179: Service Subscriber Number...................................................................227 7.2.49 Package 183: Sent CAC..................................................................................................227 7.2.50 Package 184: MLPP Level ..............................................................................................228 7.2.51 Package 186 : IN Service Key ........................................................................................228 7.2.52 Package 187: Received CAC..........................................................................................228 7.2.53 Package 191 : Signalling Point Code ............................................................................229 7.2.54 Package 192 : Sent Calling Party Number....................................................................229 7.2.55 Package 193 : Sent Redirecting Number......................................................................229 7.2.56 Package 194 : Sent Calling Party Category..................................................................230 7.2.57 Package 195 : Original Calling Party Category............................................................230 7.2.58 Package 196 : Trunk Info................................................................................................230 7.2.59 Package 198 : Durations in 100 msec...........................................................................231 7.2.60 Package 199 : Received Charge Determination Information......................................232 7.2.61 Package 204: Access Data.............................................................................................232 7.2.62 Package 205: Non Charged Facilities Used By Owner ...............................................233 7.2.63 Package 209: Accumulated Currency Charges ...........................................................233 7.2.64 Package 211: Additional Release Cause ......................................................................234

6

P30308-X2058-K160-03-7617

General Information

0 General Information0.1 Status informationThe document comprises a total of 234 pages. All pages have issue number 03.

0.2 HistoryIssue 01 02 Date Reason for the publication/change

18.09.2002 First release Customer document !corresponds to Developer Document issue 03 23.12.2002 Flag F45 (Fallback occurred) in package 154 (Additional Call Indicators) is only relevant for DNOBS. In package 204 (Access Data), the field Number A-side in subpackage 3 (DLU / V5.2 Number A-Side) and the field Number B-Side in subpackage 4 (DLU / V5.2 Number B-Side) have a length of 2 instead of 1 byte.

03

Error correction in example of package 198 (Durations in 100 msec). 13.02.2003 In case of Call Forwarding, and in case the presence of the packages 153 (Received Called Party Number) and 187 (Received CAC) is administered, the AMA ticket for the second leg will only contain the package 187 (Received CAC) and not the package 153 (Received Called Party Number). The same is valid for the AMA ticket generated for the recall after CCBS or CCNR. Package 187 (Received CAC) is built independent of the CAC used for routing. The description of package 209 (Accumulated Currency Charges) is enhanced with a remark concerning intermediate charging. In the description of package 120 (Calling Party Category), the postprocessing remark concerning the presence of this package is not only relevant for LAMA, but also for CAMA.

Table 1: Document History

0.3 References/1/ /2/ /3/ /4/ Description of output data P30308-X3228-K160-*-7617 AMA for Operator Input Description of output data P30308-X1438-K160-**-7617 AMA for Operator Service System Description of output data P30308-X5114-K160-*-7617 AMA for Intelligent Networks (IN) calls Description of output data P30308-X6800-K160-*-7617 AMA for Inter Administration Charging7

P30308-X2058-K160-03-7617

General Information

/5/ /6/ /7/ /8/ /9/

/10/

Volume Description of Output Data on Magneto Optical Disk (MOD) P30305-X317-K10-*-7618 CML V16 ITU-T Q.850 Usage of Cause and Location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part ITU-T Q.763 Formats and Codes of the ISDN User part of Signalling System No. 7 An Arithmetic Checksum for Serial Transmissions John G. Fletscher IEEE Transaction on communications vol.com-30, no. 1 January 1982, pages 247..251 Description of Output Data P30309-A2814-K160-*-7617 (specific) Detailed Call Record Registration

8

P30308-X2058-K160-03-7617

General Information

0.4 Terms and AbbreviationsAAA ACC ACM ADMOSS ANM AMA AMAIO AOCRG APM APS CAC CAMA CCBS CCNR CDR CENTREX CIC CML CONN CP CPE CRG CRGE CRGA CRGT CT CTX DDI DEB DEBNC DLU DN DNOBS DSL EOF FAI FAIO FAIS FAU FTAM GCR HTML HOP IACAMA IAM IN INA INAP IP/SN IP Authentication, Authorization & Accounting Automatic Congestion Control Address Complete Message Advanced Multifunctional Operator Service System Answer Message Automatic Message Accounting AMA Immediate Output on the Operation and Maintenance (OAM) terminal or on an external device via an X.25 link(Hot Billing) Add-on Charging Information Application Transport Mechanism Application Program System Carrier Access Code Centralized AMA Call Completion on Busy Subscriber Call Completion on No Reply Call Detail Record Centralized Office Exchange Service Circuit Identification Code Command Manual Connection Coordination Processor Customer Premises Equipment Charge Information Charging Extended Charging Acknowledgement Information Charging Tariff Information Call Transfer Centrex Direct Dialling In Detailed Billing Detailed Billing Next Call Digital Line Unit Directory Number Directory Number Observation Digital Subscriber Line End Of File Facility Input Facility input by operator Facility input by subscriber Facility Usage File Transfer, Access and Management Global Call Reference Hypertext Mark up Language Hot Operation Protocol Interadministration Charging with AMA Initial Address Message Intelligent Network IN AMA IN Application Part Intelligent Peripheral / Service Node Internet Protocol

P30308-X2058-K160-03-7617

9

General Information

ISCI ISDN ISUP LAC LAMA LFB LGC LTG LSB_HI LSB_LO LSN MASET MCE MCI MFC MG MLHG MLPP MML MOB MOD MP MSN MTD NADI NAPA NI NI NPI OAM ODAGEN O:IAM OMT OPN PA PCM PDN PIN PM PoP PSTN RID RSCI RCS REV RSU SAM SAS SCI SCLS SCP SHG SLMD SN

Internet Subscriber Controlled Input Integrated Service Digital Network ISDN User Part Local Area Code Local AMA Look-ahead for busy (ITU definition concerning MLPP) Large Conference Call Line Trunk Group Least Significant Byte on the highest Address Least Significant Byte on the lowest Address Line Service Number Manager Secretary and Team Service Multi Carrier Environment Malicious Call Identification Multiple Frequency Code Media Gateway Multi Line Hunting Group Multi-Level Precedence and Preemption Man Machine Language Meter Observation Magneto-Optical Device Main Processor Multiple Subscriber Number Magnetic Tape Device Nature of Address Information National Parameter Network Identity (ITU definition concerning MLPP) Network Indicator (in relation with Signalling Point Code) Numbering Plan Indicator Operation and Maintenance Online Database Generation Order: Initial Address Message Operation and Maintenance Terminal Operator Number Primary Rate Access Pulse Code Modulation Pilot Directory Number Personal Identification Number Packet Manager Point of Presence Public Switched Telephone Network Record Identifier Remote Subscriber Controlled Input Reverse Charging Service (specific feature) Reverse Charging according to ITU-T specifications Q.736 and Q.956 Remote Switching Unit Sequential Access Method Standalone Service Subscriber Controlled Input or Send Charging Information Subscriber Credit Limit Supervision Service Control Point Subscriber Hunting Group Subscriber Line Module Digital Switching Network

10

P30308-X2058-K160-03-7617

General Information

SPC SSP TDP TFS TGRP TNS TPC TRK ID TRST TUP UUS VoIP VMS VOL

Signalling Point Code Service Switching Point Trigger Detection Point Toll Free Service Trunk Group Transit Network Selection (ISUP Parameter) Three Party Conference Call Trunk Identification Traffic Structure Measurement Telephone User Part User to User Signalling Voice over IP Voice Mail Service Volume

0.5 Key Word / DescriptorAMA Ticket Charging DEB

0.6 List of figures and tablesFigure 1: Use of PA slave as inter-connection ............................................................................16 Figure 2: A- and B-side of a call ..................................................................................................17 Figure 3: Structure of the AMA files ............................................................................................19 Figure 4: Possibilities for AMA storage and transfer ...................................................................20 Figure 5: Format of the AMA record............................................................................................25 Figure 6: Example of (Fixed Part) Flags in tickets generated at the end of a Three Party Call. .35 Figure 7: Intermediate charging for FAU tickets..........................................................................38 Figure 8: Appearance of value PM B-Channel in package 102 (Service Info) ............................49 Figure 9: Appearance of value PM D-Channel in package 102 (Service Info)............................49 Figure 10: Appearance of value PM Bd-Channel in package 102 (Service Info) ........................50 Figure 11: Use of package 104 (Charge Units for Facility Usage) ..............................................52 Figure 12: Partner Facility in case of multiple diversion ..............................................................62 Figure 13: Package 122 (Zone) in case of internal traffic (in the same local area) .....................70 Figure 14: Zone = 0 in package 122 (Zone)................................................................................70 Figure 15: Zoning in higher exchange, analog trunk ...................................................................71 Figure 16: Zoning in higher exchange, ISUP trunk .....................................................................71 Figure 17: Example of a dialled account code ............................................................................73 Figure 18: Use of ISUP CRG message.......................................................................................80 Figure 19: Transport of Chargeband information for IN calls ......................................................81 Figure 20: Receipt of Chargeband during call.............................................................................81 Figure 21: Charging concept for IP/SN (terminating IP/SN calls)................................................88 Figure 22: Provision of Billing CAC in case of Reselling .............................................................91 Figure 23: Third Party Number in case of A-side Call Transfer...................................................96 Figure 24: Third Party Number in case of B-side transfer ...........................................................97 Figure 25: Receipt of Tariff info before Answer (call duration < intermediate timer) .................105 Figure 26: Examples of intermediate Charging in case Tariff Info is received ..........................107 Figure 27: Checksum algorithm ................................................................................................112 Figure 28: Intercom Numbers in case of Group Dialling ...........................................................115P30308-X2058-K160-03-7617 11

General Information

Figure 29: Intercom Numbers in case of Location Dialling........................................................116 Figure 30: Illustration of Additional Call Indicators ....................................................................122 Figure 31: Charging during RSU Standalone............................................................................124 Figure 32: Example of ADD ON Tariff during a call...................................................................128 Figure 33: Example of two ADD ON Tariffs during a call ..........................................................128 Figure 34: Example of the use of package 157.........................................................................132 Figure 35: AMA Tickets in case of Call Diversion .....................................................................141 Figure 36: AMA Tickets in case of Multiple Call Diversion ........................................................142 Figure 37: AMA Ticket in case of SIP - PSTN Interworking ......................................................150 Figure 38: RSU configuration ....................................................................................................169 Table 1: Document History............................................................................................................7 Table 2: Overview of AMA record types......................................................................................14 Table 3: Terminology for different kinds of tickets.......................................................................15 Table 4 : Overview of the Data Packages ...................................................................................27 Table 5 : Overview of the Project Specific Data Packages .........................................................27 Table 6: Layout of the Fixed Part of the AMA record based on Record Owner Type .................31 Table 7: Layout of the Fixed Part of the AMA record based on Record Owner DN ....................31 Table 8: Overview of the Flags in the Fixed Part of the AMA Record .........................................32 Table 9: Values of Record Sequence..........................................................................................33 Table 10: Values of Charge Status .............................................................................................33 Table 11: Values of Record Owner Type ....................................................................................33 Table 12: Possible combinations of Flags in the Fixed Part of the AMA Record ........................37 Table 13: Values of Facilities Used By Partner ...........................................................................61 Table 14: Values of Facilities Input Actions.................................................................................63 Table 15: Values of Facilities Input Flags....................................................................................63 Table 16: Layout of the ISUP Charge Information message.......................................................80 Table 17: Layout of GCR...........................................................................................................109 Table 18: Overview of the Flags in package 154 (Additional Call Indicators) ...........................120 Table 19: Overview of EXTNSD values and the controlled packages ......................................193 Table 20: Overview of ALTNSD values and the controlled packages.......................................193 Table 21: Overview of Record Identifiers ..................................................................................196 Table 22: Examples for AMA Record length .............................................................................198

12

P30308-X2058-K160-03-7617

Introduction

1 IntroductionAMA (Automatic Message Accounting) is a subscriber charging method by means of tickets: all information that is or could be relevant for charging is registered in a ticket. The generated tickets are stored in a file on exchange disk, from where they are transferred to a remote Billing Center. In this Billing Center, the tickets are used to calculate the charges to be paid by the subscribers. Charging with AMA is also denoted as offline charging. It is an alternative for Metering, which is also denoted as online charging. When Metering is used, charge units are calculated inside the exchange, and accumulated on subscriber meters. The meter contents are transferred to a remote Billing Center, where the charge units are directly converted to the invoices to be paid by the subscriber. A combination of AMA and Metering is also possible by including in the AMA records the amount of online charge units generated within the exchange. Depending on the application, there are several kinds of AMA records, which are stored in the corresponding record file (e.g. AMA records for subscriber charging are stored in the IA.ICAMA file and AMA records for interadministration charging in the IA.ICIAR file). The exchange provides also the possibility to generate only one ticket for different applications. This feature is denoted as CDR (Call Detail Record). By administration, it can be specified for which applications the tickets are merged. Following applications can be specified for the CDR feature: Subscriber Charging Interadministration Charging Directory Number Observation (DNOBS) Traffic Structure Measurement (TRST) Those CDR records are stored in one file IA.ICCDR, or in two files IA.ICCDR1 and IA.ICCDR2. More details about this CDR feature can be found in /10/. Table 2 shows the different types of AMA records for the respective applications, and the files in which these records are stored on the disk of the exchange.

P30308-X2058-K160-03-7617

13

Introduction

CDR feature not active (separate records for AMA and IACAMA) AMA records for subscriber charging AMA for automatic calls (CONN) AMA for Subscriber Controlled input (SCI or FAIS) AMA for Facility Usage (FAU) AMA for Operator Input of Facilities (FAIO) () AMA for Operator Assisted calls (ADMOSS) () stored in one file IA.ICIAR resp. in two files IA.ICIAR1 and IA.ICIAR2 stored in file IA.ICAMA stored in file IA.ICINA stored in file IA.ICAMA

CDR feature active (one common record for AMA and IACAMA) stored in one file IA.ICCDR resp. in two files IA.ICCDR1 and IA.ICCDR2

AMA records for Inter Administration Charging (IACAMA) ()

AMA records for charging of the TFS service subscriber AMA records for charging of the IN service subscriber ()

stored in file IA.ICINA

() not described in this document. For a description of the AMA records for operator input (via MML) and for ADMOSS-calls, refer to /1/ and /2/. For a description of IN Service Subscriber tickets and Inter Administration Charging tickets, refer to /3/ and /4/.

Table 2: Overview of AMA record types

1.1 Overview of the documentChapter 2 gives a description of the structure of the file IA.ICAMA resp. IA.ICCDR(1/2). Chapter 3 gives an overview of the logical information that is collected in the AMA tickets. Chapter 4 describes the structure of one AMA record. Chapter 5 contains a detailed description of all fields in the AMA records. For each field, the syntax and a functional description are given, completed with operational and post processing remarks. Chapter 6 gives a short overview of the operational handling necessary for activating the AMA feature and controlling the contents of the IA.ICAMA file. Also some hints for the Postprocessing are included. Finally, delta descriptions to previous versions are given. Chapter 7 provides an example for all parts of the ticket.

1.2 ScopeThis document describes the contents of the AMA tickets. The CDR feature is only mentioned for clarification; a comprehensive description can be found in /10/. A detailed description of the AMA functionality can also be found in /10/.

14

P30308-X2058-K160-03-7617

Introduction

1.3 Terminology Throughout the document, the term AMA refers to the method of collecting tickets for the charging of automatic calls, Subscriber Controlled Input, Facility Usage and for the charging of the TFS Service Subscriber. Collecting tickets for Operator Input of Facilities (via MML) is denoted with OPERAMA and for Operator Assisted Calls with ADMOSS-AMA. For the charging of the IN service subscriber, the term IN AMA is used. IACAMA refers to Interadministration Charging with AMA. CAMA (Centralized AMA) refers to AMA in a transit or end exchange (the term centralized refers to the fact that the AMA tickets are generated at a central location for calls originating in different exchanges). LAMA (Local AMA) refers to AMA in the local exchange, i.e. the exchange where the subscriber to be charged is located. When not otherwise specified, AMA refers to both CAMA and LAMA. DEB (Detailed Billing) is a feature assigned to a subscriber, PBX or PBX line, which leads to the generation of AMA tickets (for all calls, for the next call or dependent on the traffic type). These AMA tickets are marked extra with the indication DEB. The term record in this document refers to the AMA records, the CDR records, the System records and the filler records. The term " CDR record" or CDR refers to the Call Detail Record, which is a common record for different applications (refer to /10/). The terms AMA ticket, ticket, AMA record and CDR all refer to the variable length record. Remark the difference between an AMA record and a file record of the file IA.ICAMA or IA.ICCDR(1/2) file(s): such a file-record has a fixed length of 2, 4 or 8 Kbytes. The variable length AMA records are grouped together in one such fixed length file record, possibly with a filler record at the end (refer to /10/ for a detailed description). When referring to such a fixed length file-record of 2, 4, or 8 Kbytes, the term file record or data block is used. The following terminology is used for the different kinds of tickets:AMA/CDR tickets for Automatic calls Interadministration charging (only relevant in case CDR is activated) Subscriber controlled input Facility usage Operator assisted calls Charging of TFS subscriber Terminology Connection tickets or CONN tickets Connection tickets or CONN tickets SCI tickets FAU tickets ADMOSS tickets TFS tickets

Table 3: Terminology for different kinds of tickets The term System record refers to the following records that can be collected together with the AMA or CDR records in the data blocks of the IA.ICAMA or IA.ICCDR(1/2) file: Date/Time Change record Overflow record Breakdown record

P30308-X2058-K160-03-7617

15

Introduction

The terms Postprocessing and Billing Center refer both to the entity outside the exchange, which receives the tickets after having issued a transfer command, and which calculates the charges to be paid by the subscribers based on these tickets. The term craftsperson refers to the person or persons, which enter the MML-commands in the exchange. The term "zoning" is used to indicate the digit analysis in the exchange, which is done in order to determine a "zone based on a.o. the dialled digits. The zone in the exchange reflects basically the distance dependency of the charging (other parameters, like the Originating Mark of the A-party can be used additionally to determine the zone). To a zone, time dependent tariffs can be assigned. At a certain time only one tariff is applied. The term Voice over IP (VoIP) is used when voice calls are set up using IP as a transmission medium. Unless otherwise specified, the term subscriber does not only refer to analog and ISDN subscribers but also to analog and ISDN PBXs, coinboxes, subscribers connected to V5.1 and V5.2 interfaces, .... In this sense, it is opposed against the term trunk, which is used to denote the inter-connection (analog, TUP, ISUP, ...) between two exchanges. Remark that a PA (Primary Rate Access) connection is administered in the exchange as a PBX; a PA is therefore not denoted as trunk, even when it is used as inter-connection between two exchanges. A PA used as inter-connection is denoted as PA-Slave. A typical use of PASlave is the inter-connection between two exchanges of different network operators via a subscriber interface.Primary access Operator 1switch switch switch switch

border between two operators Operator 2

gatewayswitch

gatewayswitch

switch

When both gateways are EWSD exchanges, the PA connection is administered in both exchanges as a PBX.

Figure 1: Use of PA slave as inter-connection The notation H is used for the hexadecimal notation. Example: H84 is equivalent to the decimal value 132. The A-side and B-side of a call refer only to the exchange, which is currently considered for the ticket generation (e.g. in case of CAMA tickets, the A-side is the trunk on which the seizure arrives in the exchange generating the CAMA ticket). A-party and B-party denote the respective parties in the call.

16

P30308-X2058-K160-03-7617

Introduction

switch

switch

switch

A-party B-side A-side = origin A-side B-side A-side B-side = destination

B-party

Figure 2: A- and B-side of a call General remark concerning MML commands At many locations in this document, MML commands are mentioned. These MML commands do not tend to be complete; they are just meant to clarify the relation between AMA and administration. When e.g. only a create command (CR ..) is mentioned to administer a particular information field, it is quite possible that also the corresponding modification command (MOD...) can be used. Parameters that have to be replaced by real values are written between < >. For a detailed syntax description of each MML-command, refer to /6/.

P30308-X2058-K160-03-7617

17

Description of the File Format

2 Description of the File Format2.1 Overview of AMA storage and transfer possibilitiesThe possibilities of AMA data storage depend on the used architecture. When only a Coordination Processor (CP) is available, AMA data are stored in the cyclic file IA.ICAMA (resp. IA.ICCDR, IA.ICCDR1 or IA.ICCDR2) on disk. Copies can be taken on tape or on MOD (Magneto Optical Device). The transfer is done with FTAM or with the Siemens specific Hot Operation transfer protocol (HOP) (see /10/). When an architecture is used with a Coordination and a Main Processor (MP), AMA data can either be stored on a cyclic file on CP disk, or in a series of SAM files on MP disk. In the latter case, copies can only be taken on MOD. File transfer is done with TCP/IP or with HOP. For the transfer with TCP/IP, the Billing Center can chose between a one file view or multiple file view. In case a one file view is chosen, the Billing Center accesses the SAM File Array as whole. For the transfer of the available data, only one FTP GET command has to be issued. In case of a multiple file view, the Billing Center accesses each SAM file separately. In order to transfer the data, an FTP GET command has to be issued for each SAM file, which has not yet been transferred. From a data processing point of view, the cyclic file on CP disk and the SAM files on MP disk have fixed length records of 2, 4 or 8 Kbytes (the actual value can be administered). One such file record contains several variable length AMA records, possibly completed with a filler record.File Record x File Record x + 1 ... File Record n

AMA or System Records

Filler


Filler


Filler

Figure 3: Structure of the AMA files Before AMA data are stored on disk, they are buffered in main memory. Buffering is described in detail in /10/. This buffering takes place on the CP. In case the AMA records are stored on SAM files on the MP disk, the buffers are transported from the CP to the MP.

P30308-X2058-K160-03-7617

19


CP Buffers

MP

cyclic file SAM files

MOD

FTAM/X.25 HOP

TCP/IP HOP

Figure 4: Possibilities for AMA storage and transfer

2.2 File format on CP diskThe cyclic file on CP disk has following characteristics: File records can be written continuously into the file. When the maximum file size is reached, the oldest stored file records are overwritten, on condition the area on disk where these oldest records are stored has been marked as "overwriting allowed". This can be done by the craftsperson after transfer of the stored file records (i.e. only the transferred records can be overwritten). The file contains a header with control information. This control information contains e.g.: the write pointer, which marks the position in the cyclic file where the next file record has to be written to. pointers that mark the beginning and end of the copy area. The copy area is that part of the cyclic file, which has been transferred, but has not yet been released for overwriting. Each time a new transfer is issued on the cyclic file, the contents of the copy area is transferred again. the number of times the copy area has been transferred. For a detailed description of cyclic file handling in the exchange, refer to /10/.

20

P30308-X2058-K160-03-7617


2.3 File format on MP diskThe SAM files merely contain the AMA records, organized in file records of fixed length. They do not contain any control information. The SAM files on MP disk are organized in a so called SAM File Array (SAMAR). This SAMAR is separately administered. Administration data for the SAMAR are e.g. the SAMAR name, the number of SAM files in the SAM File Array, the size of each file, the size of each record in a SAM file, and the type of transfer (one file view, or multiple file view). These data are stored in Non Discardable memory; a part of the data are replicated in a Master File on disk for safety reasons. The data related to each SAM file are stored in the so called Application Specific Attributes of the SAM files. These are part of the catalog information (the catalog is an area on disk, where information about the files stored on disk is kept). Important Application Specific Attributes are the SAM file status (information whether the file is empty, currently open for writing, closed but not yet copied, copied, or released for overwriting) and the transfer indicator in case of a one file view (the transfer indicator is the counterpart of the read and write point for cyclic file; refer to /10/)

2.4 File format on MTD or MODIn case of a transparent copy from the IA.ICAMA resp. IA.ICCDR(1/2) file to a Magnetic Tape Device (MTD) or to a Magneto-Optical Device (MOD), the file on MTD or MOD has the same structure as the one on disk, i.e. fixed length data blocks of 2, 4 or 8 Kbytes containing the individual AMA records with variable length. The information on MTD is organized according to international standards (DIN 66029, May 79 and ISO 1001-1979). Refer to /5/ for a detailed description of MTD organization, Volume Labels and MTD Marks. Following parameters are AMA specific: File Identifier The AMA file on MTD is recommended to be identified by the name IA.ICAMA.XXXXXXXX resp. IA.ICCDR.XXXXXXXX, IA.ICCDR1.XXXXXXXX or IA.ICCDR2.XXXXXXXX, where the positions XXXXXXXX identify the exchange. The file name is entered with the MML command used to copy the AMA disk file on MTD or MOD. Block Length The Block Length is equal to the File Record Size, i.e. 2, 4 or 8 Kbytes. File Record Size 2, 4 or 8 Kbytes. File Record Format Fixed (F)

P30308-X2058-K160-03-7617

21

Remarks on the File Contents

3 Remarks on the File ContentsFollowing records can be present in the IA.ICAMA file: AMA records There are different kinds of AMA records, according to the application. In the IA.ICAMA file, following kinds of AMA records can be present: AMA records for automatic calls (CONN ticket) AMA records for Subscriber Controlled Input (SCI tickets) AMA records for Facility Usage (FAU tickets) AMA records for Operator Input of Facilities (FAIO tickets) AMA records for Operator Assisted calls (ADMOSS tickets) AMA records for charging of the TFS service subscriber (TFS tickets) FAIO and ADMOSS tickets are not further considered, because they are subject of an own description (refer to /1/ and /2/). All tickets described in this document (CONN, SCI, FAU and TFS tickets) have a variable length structure, which is composed out of a Fixed Part and one or more data packages. Refer to /10/ for a detailed description. System Records These records are used to register some switch events that are important for charging: Date/Time/Change record to register the change of time in the switch Breakdown Record to register a recovery in the switch Overflow Record to register the fact that tickets have been lost due to overflow conditions in the switch Filler Records These are used to fill out the 2, 4 or 8 Kbytes data block in the IA.ICAMA file. System and Filler records are described in detail in chapter 5.2 and following.

P30308-X2058-K160-03-7617

23

Data Record Description

4 Data Record Description4.1 AMA RecordAn AMA Record consists out of two main parts: a fixed part, with a fixed structure a variable part, which contains several data packagesFixed Part Package 1 Package 2 Data Variable Part Package ID (Length)

Package n - 1 Package n

Figure 5: Format of the AMA record Fixed Part The Fixed Part is the "header" of the record and contains several standard fields. For a detailed description of the respective fields, refer to Chapter 5.1.1. Variable part: data packages The Fixed Part is followed by several data packages. The presence of a data package depends on several criteria: collection is or is not activated by the craftsperson e.g. package 105 (Trunk Identification) the data item is or is not relevant for the call e.g. package 102 (Service Info) for analog calls the value of the data item is or is not the default value e.g. package 120 (Category) in case the category = "subscriber" The first field of each data package contains the package identification. This is a unique number. Each package has its own layout. In most of the data packages, the package length is indicated at the second byte. Following table gives an overview of the data packages relevant for the different types of AMA Records. For a detailed description of the data packages, and the conditions under which the data packages are collected, refer to Chapter 5.1.2.

P30308-X2058-K160-03-7617

25


Package Identification 100 101 102 103 104 105 106 107 108 110 111 112 113 116 118 120 122 125 128 130 134 135 136 138 139 142 143 145 146 147 148 149 150 151 152 153 154 Date / Time / Duration Partner Directory Number Service Info Charge Units For Connection Charge Units For FAU Trunk Id Incoming Trunk Id Outgoing Trunk Id Incoming with CIC Trunk Id Outgoing with CIC Connection Identification Facilities Used By Owner Facilities Used By Partner Facility Input Date / Time Digit String Calling Party Category Zone Account Code New Destination Traffic Quality Data Durations before Answer Chargeband UUS3 Counters B Meter Pulses Release Indication Calling Party Number IP/SN Charge Data Billing CAC Third Party Number Tariff Info CAC New Destination Global Call Reference Audit Trail Business Group Identification Centrex Numbers Received Called Party Number Additional Call Indicators

Package Length fixed variable fixed fixed fixed fixed fixed fixed fixed fixed variable variable fixed fixed variable fixed fixed variable variable fixed fixed fixed fixed fixed fixed 11 bytes calculated 4 bytes 4 bytes 3 bytes 9 bytes 9 bytes 10 bytes 10 bytes on byte 2 on byte 2 on byte 2 on byte 2 8 bytes calculated 2 bytes 3 bytes on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2

variable on byte 2 variable variable variable variable variable variable fixed fixed variable variable variable on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2

opt opt [opt] opt [opt] [opt] [opt] [opt] [opt] [opt] [x] [opt] opt [x] opt [x] [opt] [opt] [opt] [opt] [x] opt opt [x] [opt] [x] [opt] [opt] [opt] [opt] [opt] opt [opt] [opt] [opt] [opt]

[opt] opt [opt] x x [x] [x] [x] [opt] [x] [opt] [opt] [opt] opt [opt] [opt] [opt] [opt]

[opt] [opt] [opt] [opt] x [x] [x] [x] [x] [x] [opt] [opt] [opt] [opt] opt [opt] [opt] [opt] [opt]

26

P30308-X2058-K160-03-7617

FAU by A-party FAU by B-party TFS [opt] [opt] [opt] [opt] x [x] [x] [x] [x] [opt] [opt] opt [opt] [opt] [opt] opt opt opt [opt] [opt] [opt] [opt] [opt] opt opt x [opt] opt [x] [opt] [opt] opt [opt]

CONN (FAU) SCI


155 156 157 159 167 168 170 171 172 178 179 183 184 186 187 191 192 193 194 195 196 198 199 204 205 209 211

Add On Tariff Advised Cumulated Charges Outgoing Pa Identification Additional Calling Party Number Additional Numbers Called Party Number Redirecting Number Sent Called Party Number System Provided Number Exchange Info Service Subscriber Number Sent CAC MLPP Level In Service Key Received CAC Signalling Point Code Sent Calling Party Number Sent Redirecting Number Sent Calling Party Category Original Calling Party Category Trunk Info Durations In 100 msec Received Charge Determination Info Access Data Non Charged Facilities Used by Owner Accumulated Currency Charges Additional Release Cause

variable fixed variable variable variable variable variable variable variable variable variable variable variable fixed variable fixed variable variable variable variable variable variable fixed variable

on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2

variable on byte 2 variable on byte 2 variable on byte 2

[opt] [opt] [opt] [opt] [opt] x [x] [opt] [x] opt [opt] [opt] [opt] [opt] [opt] opt [opt] [opt] [opt] [opt] [opt] opt [x] [opt] [opt]

[opt] [opt] [x] opt opt [opt] -

[opt] [opt] [x] [x] opt opt [opt] [opt] [opt] opt

[opt] [x] [x] opt opt [opt] [opt] [opt] opt

[opt] [x] opt x opt opt opt [x] [opt] opt

[opt] opt opt

Table 4 : Overview of the Data PackagesFAU by A-party FAU by B-party * * * -

CONN (FAU)

117 140 141 176 177 181

Project Specific Data Incoming Route Id Outgoing Route Id ITU Calling Party Category Project Specific Service Internet Session Info

variable variable variable fixed fixed variable

on byte 2 on byte 2 on byte 2 on byte 2 on byte 2 on byte 2

* * * * * *

* * * -

* * * -

Table 5 : Overview of the Project Specific Data Packages

P30308-X2058-K160-03-7617

TFS * 27

Package Identification

Package Length

SCI


Symbol Explanationx [x] Data package is always collected in all tickets for the call. Data package is not always collected; i.e. the data package is only collected when certain conditions are fulfilled. The collection of the package is not administrable. Optional data package, i.e. the collection of the data package depends on the administration by the craftsperson by means of the MML-command ENTR CDTDAT. The collection of the data package depends only on the administration, i.e. if the collection of the data package is administered, the package is always collected in all tickets for the call. Optional data package, which depends not only on the administration by means of MMLcommand ENTR CDTDAT, but also on other conditions. Data package not relevant and therefore not collected. Data package is collected on a project specific basis; i.e. the collection of this package is not part of the common functionality.

opt

[opt] *

4.2 System and Filler RecordsSystem records (Data/Time Change, Breakdown and Overflow) have a fixed length of 32 byte. Filler records have three formats: the Record Identifier H80 is used as Filler record to fill in one byte the Record Identifier H81 is used as Filler record to fill in several bytes the Record Identifier H00 is used as Filler record to fill in 32 bytes The exact layout of the System and Filler Records is described in Chapter 5.2 and following.

4.3 General Record Coding Details4.3.1 Coding of binary fields Binary fields are stored in LSB_LO format; i.e. the least significant byte of the binary number is stored at the lower memory location. EXAMPLE: Storage of a binary integer in a 3-byte field Integer = 250 (H'FA = H'0000FA)byte 1 byte 2 byte 3 Bit position 76543210 11111010 00000000 00000000 Bit position 76543210 11101000 00000011 00000000 or FA 00 00 value = 250 = HFA value = 0 = H00 value = 0 = H00

Integer = 1000 (H'3E8 = H'0003E8)byte 1 byte 2 byte 3 or E8 03 00 value = 232 = HE8 value = 3 = H03 value = 0 = H00

28

P30308-X2058-K160-03-7617


4.3.2 Coding of packed digits fields The expression packed digit means that two digits are packed into one byte. The digits on odd positions of a digit string are stored into the high order part of a byte. The digits on even positions of a digit string are stored into the low order part of a byte. The first digit of the string is stored in the first byte of the digit field. Examples: 1) Digit String of 6 digits: 123456 (e.g. Called Party 1 2...6)Bit position 7 6 5 4 3 2 1 0 1 2 3 4 5 6 Bit position 7 6 5 4 3 2 1 0 1 2 3 4 5 6 7 (*) byte 1 of the digit field byte 2 of the digit field byte 3 of the digit field

2) Digit String of 7 digits: 1234567 (e.g. Called Party 1 2...7)byte 1 of the digit field byte 2 of the digit field byte 3 of the digit field byte 4 of the digit field

(*): The value of the low order part of byte 4 is undefined. Remark that all the digit fields have a corresponding length field that indicates the number of digits.

4.3.3 Coding of character fields Character fields are coded in ISO-7-Bit-Code. The first character is stored at the lower memory location of the field. Trailing bytes are filled up with spaces. Example: Store MUNICH in a character field that has a length of 8 bytes.Bit position 7 6 5 4 3 2 1 0 4 D 5 5 4 E 4 9 4 3 4 8 2 0 2 0

M U N I C H space space

byte 1 of the character field byte 2 of the character field byte 3 of the character field byte 4 of the character field byte 5 of the character field byte 6 of the character field byte 7 of the character field byte 8 of the character field

P30308-X2058-K160-03-7617

29

Data Field Description

5 Data Field Description5.1 AMA Record5.1.1 Fixed Part (Header) A) Syntax descriptionField No 1 2 3 Byte Pos 1 2 4 Field Name 3 2 1 0 6 5 (bytes) 7 4 1 Record Identifier 2 Record Length Reserved F18 F17 F16 F15 F14 F13 n.a. F11 3Length

Remarks binary; fixed value 132 (H84) binary; total length of AMA record refer to Table 8 for a description of the

n.a. F27 n.a. F25 F24 F23 F22 F21 Flags F38 F37 res. F35 F34 F33 n.a. n.a.

4

binary; refer to Table 9 and Table 10 for a description of the fields Record Sequence and Charge Status 5 8 1 Record Owner Type binary; refer to Table 11 for a description of the field Record Owner Type Legend: n.a. not applicable, which means that the flag is not relevant for AMA, but is in use for another kind of record (MOB, IN AMA, OPERAMA) res. reserved

7

1

Record Sequence

Charge Status

Table 6: Layout of the Fixed Part of the AMA record based on Record Owner TypeField No 1 2 3 Byte Pos 1 2 4 Field Name 6 5 4 3 2 1 0 (bytes) 7 1 Record Identifier 2 Record Length Reserved F18 F17 F16 F15 F14 F13 n.a. F11 3Length n.a. F27 n.a. F25 F24 F23 F22 F21 F38 F37 res. F35 F34 F33 n.a. n.a.

Remarks binary; fixed value 132 (H84) binary; total length of AMA record refer to Table 8 for a description of the Flags

4

binary; refer to Table 9 and Table 10 for a description of the fields Record Sequence and Charge Status 5 8 1 LAC Length Owner ID Length binary 6 9 n Local Area Code (LAC) + Directory Packed digits Number (DN) Legend: n.a. not applicable, which means that the flag is not relevant for AMA, but is in use for another kind of record (MOB, IN AMA, OPERAMA) res. reserved

7

1

Record Sequence

Charge Status

Table 7: Layout of the Fixed Part of the AMA record based on Record Owner DN

P30308-X2058-K160-03-7617

31


Description of Field No 3:Flags Flag F11 F13 F14 F15 F16 F17 F18 F21 F22 F23 F24 F25 F27 F33 F34 F35 F37 Value 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 Meaning Relevance of flags for Conn. SCI FAU TFS x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x

NoNo

Detailed Billing Detailed Billing

F38 Legend:

AMA Connection / FAIS AMA Connection / FAIS Connection No Connection Facility Usage No Facility Usage Facility Input by Subscriber No Facility Input by Subscriber AMA FAU No AMA FAU Record Owner Type in Fixed Part Record Owner DN in Fixed Part Centrex Intercom No Centrex Intercom TFS Subscriber No TFS Subscriber Ticket for LGC/TPC/CT Controller No Ticket for LGC/TPC/CT Controller Analog Subscriber No Analog Subscriber ISDN Subscriber No ISDN Subscriber RSU SAS No RSU SAS No Answer Answer AMA Immediate Output No AMA Immediate Output AMA Immediate Output Successful AMA Immediate Output Not Successful Sequence Number in package 150 (Audit Trail) No Sequence Number in package 150 (Audit Trail) Checksum in package 150 (Audit Trail) No Checksum in package 150 (Audit Trail) x: flag is relevant -: flag is not relevant

x

x

x

x

Table 8: Overview of the Flags in the Fixed Part of the AMA Record

32

P30308-X2058-K160-03-7617


Description of Field No 4: Record SequenceValue 0 1 2 3 4 5 6 15 Meaning not used single first intermediate intermediate reserved final reserved

Table 9: Values of Record Sequence Charge StatusValue 0 1 2 3 4 15 Meaning undefined charge no charge charge transfer to B-side reserved

Table 10: Values of Charge Status Description of Field No 5: Record Owner TypeValue 0 1-141 142 143-167 168 169 170 171 172 173-178 179 180-255 Meaning not available reserved Calling Party Number reserved Called Party Number reserved Redirecting Number reserved System Provided Number reserved Service Subscriber Number reserved

Table 11: Values of Record Owner Type B) Functional description Record Identifier The Record Identifier 132 (H84) identifies AMA records for automatic calls, Subscriber Controlled Input, Facility Usage, and TFS service subscriber. In case the CDR feature is active, the Record identifier 132 (H84) also identifies IACAMA records. For a complete list of all possible record identifiers that can be present in the IA.ICAMA file, refer to Chapter 6.4.1.

P30308-X2058-K160-03-7617

33


Record Length The Record Length refers to the total number of bytes in the AMA record, i.e. including Fixed Part and all packages. For an estimation of the average length of the AMA record, refer to Chapter 6.4.3. Flags Flag F11: Detailed Billing Flag F11 = 1 indicates that DEB was administered for the subscriber or PBX line that made the call or was requested by the subscriber or PBX line at call setup (DEB Next Call). The flag is also set when the call belongs to a certain traffic class with DEB. Remarks: It is quite possible that Flag F11 (DEB) and F13 (AMA) are both set. This indicates that during the set up of the call, the subscriber feature DEB was encountered (subscriber/PBX data) as well as the recording AMA (based on the called party number). It is quite possible that Flag F11 (DEB) is set together with F17 (AMA FAU). This indicates that a subscriber/PBX with DEB has used a facility for which AMA was required Flag F11 can never be set in CAMA tickets, since CAMA tickets are either generated by AMA based on the called party number, or by AMA assigned to the incoming trunk. Flag F11 is never set in TFS tickets Flag F11 set in the FAIS and FAU tickets indicates that the Facility Input or the Facility Usage was made by a subscriber or PBX with DEB Flag F13: AMA Connection / FAIS Flag F13 has a double use: In case of an AMA ticket for Facility Input, recognizable by Flag F16 (Facility Input) being set, this flag indicates that as charging method for the facility input, AMA was assigned. In case of an AMA ticket for an automatic call, the flag indicates that the recording AMA was encountered during the set up of the call. AMA could have been found as a result of digit analysis, or as semi permanent data on an incoming trunk. Remark: Flag F13 is never set for FAU tickets (the equivalent for FAU tickets is Flag F17). Flags F14, F15, and F16: Connection / Facility Usage / Facility Input by Subscriber These flags indicate whether the ticket is used for charging of: a real speech connection (F14 set) the usage of a facility (F15 set) a facility input by a subscriber (F16 set) Remark: Flag F16 (Facility Input) cannot be set together with F14 (Connection) or F15 (FAU) Flag F15 (FAU) is set as soon as package 111 (Facilities Used by Owner) is registered in the ticket. This is done when a chargeable facility is used during the call. An FAU is chargeable when AMA or/and Metering has been assigned to it. Note however that when the FAU is only charged with Metering, the FAU will be registered in connection tickets charged with DEB (on condition the mark DEBFA is set with ENTR CDTDAT), but not in Connection tickets charged with AMA. Consider the following example: the connection is charged with DEB, the FAU with metering. In the AMA ticket, the flag F15 will be set, indicating that the AMA ticket is also used to register a chargeable Facility Usage. Flag F15 (FAU) does not relate to package 112 (Facilities Used by Partner): when only Facilities Used By Partner are present in the ticket, flag F15 will not be set.

34

P30308-X2058-K160-03-7617


Flag F15 (FAU) set and flag F14 (Connection) not set indicates that the AMA ticket is only used for charging of the Facility Usage. A typical example of such a separate FAU AMA ticket is the ticket for the LGC/TPC/CT Controller.AMA-Ticket :A-B2 Fixed Part :

B2-party : LAC=089, DN = 444444

F11 = 1 (DEB) F13 = 0 (no AMA for connection) F14 = 1 (Connection) F15 = 1 (Facility Usage)

FAU-Ticket for TPC usage Fixed Part :

F11 = 1 (DEB) F13 = 0 (no AMA for connection) F14 = 0 (no Connection) F15 = 1 (Facility Usage) F23 = 1 (TPC controller) A-party : LAC=089, DN = 123456AMA-Ticket :A-B1 Fixed Part :

B1-party : LAC=089, DN = 333333

F11 = 1 (DEB) F13 = 1 (AMA for connection) F14 = 1 (Connection) F15 = 1 (Facility Usage)

Admin on A-side: CR FAUCHA : FAU = CONF3, BILLING=METERING, METPULS=5; ENTR CDTDAT : MARKS = DEBFA; MOD SUB : LAC = 089, DN= 123456,CHRG=DEB, COS=CONF3; CR ZOPT : CODE=33,BILLING=AMA,ZONO=2; CR ZOPT : CODE=44,BILLING=METERING,ZONO=3;

Figure 6: Example of (Fixed Part) Flags in tickets generated at the end of a Three Party Call. Flag F17: AMA FAU This flag indicates that the FAU is charged with AMA. Flag F18: Record Owner Type This flag indicates that the owner of the AMA ticket is identified by means of a reference to the respective data package that contains the DN of the Record Owner. The Reference is stored in the Fixed Part of the ticket (field 5: Record Owner Type). Remark that in case of common CDR records (collected in the file(s) IA.ICCDR(1)(2)), the Record Owner Type can have the value not available (= 0). This will be the case if the CDR record is generated for IACAMA only. Upon request by the craftsperson (by means of ENTR CDTDAT: EXTNSD=RECOWNER), the owner of the AMA ticket can be identified by his DN stored in the Fixed Part of the AMA ticket (fields 5 and following). In this case Flag F18 is set to not available (=0). Flag F21: Centrex Intercom This flag indicates that the ticket is made for a Centrex intercom call. Remarks: This flag can also be present in an AMA ticket for facility input. This is the case when the access code for the facility input is defined in the Centrex specific digit translator. The flag is not relevant for a FAU ticket. More detailed information about the Centrex intercom call (whether it is a local or remote intercom call) is registered in package 154 (Additional Call Indicators).P30308-X2058-K160-03-7617 35


Flag F22: TFS subscriber This flag indicates that the AMA ticket is made for the Toll Free Service Subscriber. More information about TFS can be found in /10/. Flag F23: Ticket for LGC/TPC/Call Transfer controller This flag indicates the extra AMA ticket that is generated in case of a Three Party Conference, Large Conference or Call Transfer. Flag F24: Analog subscriber This flag indicates that the A-party is an analog subscriber. In case of Call Diversion, the Flag F24 in the AMA ticket for the second leg refers to the diverting party. Remarks: This flag is not relevant (i.e. it is never set) for CAMA tickets. This flag is not relevant for TFS subscribers. Flag F25: ISDN subscriber This flag indicates that the A-party is an ISDN subscriber. In case of Call Diversion, the Flag F24 in the AMA ticket for the second leg refers to the diverting party. Remarks: This flag is also relevant for CAMA tickets. However, it could be that due to signalling restrictions (analog trunks between the A-party and the CAMA exchange), the flag is not set, although the A-party was an ISDN subscriber. Remark that in this case the flag F24 is also not set. This flag is not relevant for TFS subscribers. Flag F27: RSU SAS This flag can only be set when the subscriber is connected to an RSU (Remote Switching Unit). It indicates that the call is either started during SAS (Standalone Service) or that SAS situation has occurred during the call. Remarks: Flag F55 in package 154 (Additional Call Indicators) gives additional information over the RSU SAS situation. Flag F33: No Answer This flag indicates that the call has not been answered. Remarks: a call is treated as successful as soon as Answer has been received. Flag F34: AMA Immediate Output This flag indicates that the AMA ticket was requested to be put out immediately on the OMT or on an external device via a X25 link (Real Time Hot Billing; refer to /10/ for more information). Flag F35: AMA Immediate Output Successful This flag indicates that the AMA ticket was requested to be put out immediately on the OMT or on an external device via a X25 link (Real Time Hot Billing; refer to /10/ for more information), and that the output was successful.

36

P30308-X2058-K160-03-7617


Flag F37: Sequence Number in package 150 (Audit Trail) This flag indicates that the Sequence Number is located at the following position: end of record - 6 bytes. Flag F38: Checksum in package 150 (Audit Trail) This flag indicates that the Checksum is located at the two last bytes of the record. Combination of Flags The following table contains all possible combinations of the flags F11, F13, F14, F15, F16, F17.FLAG Ticket type F11 DEB F13 AMAConn AMASCI 1 1 0 1 1 0 1 1 1 0 0 0 0 0 F14 Conn F15 FAU F16 SCI F17 AMAFAU Remarks

SCI

0 1 1 0 1 1

0 0 0 1 1 1 1 1 1 1 1 0 0 0

0 0 0 0 0 0 1 1 1 1 1 1 1 1

1 1 1 0 0 0 0 0 0 0 0 0 0 0

0 0 0 0 0 0 0 1 1 0 1 1 1 0

CONN without FAU

SCI charged with AMA SCI charged with AMA SCI charged with Metering or SCI charge free CONN charged with AMA CONN charged with AMA CONN charged with METERING or CONN charge free CONN charged with AMA, FAU charged with Metering CONN and FAU charged with AMA CONN and FAU charged with AMA CONN charged with METERING or CONN charge free, FAU charged with Metering CONN charged with Metering or CONN charge free, FAU charged with AMA FAU charged with AMA FAU charged with AMA FAU charged with Metering

CONN with FAU

1 0 1 1 1

FAU

0 1 1

Table 12: Possible combinations of Flags in the Fixed Part of the AMA Record Record Sequence The Record Sequence is related to intermediate charging: when only one ticket is generated for a call, the Record Sequence of this ticket = single. When more than one ticket is generated for the same call, the generated tickets will have as Record Sequence: first intermediate intermediate -final. The Record Sequence intermediate can be absent when only 2 tickets are generated, or is repeated when more than 3 tickets are generated for the same call. Remarks: In SCI tickets, the Record Sequence is always single. When a Facility Usage, chargeable with AMA, is activated in the middle of a call, and the connection is not to be charged with tickets, the first generated FAU ticket will have Record Sequence single or first intermediate. Record Sequence "single" is used when the conversation duration is less than the intermediate time duration. Record Sequence "first intermediate" is used when the conversation duration is greater than the intermediate timeP30308-X2058-K160-03-7617 37


duration and the FAU has been activated before the intermediate time duration elapses. The latter case is illustrated in the following example for the facility usage Terminal Portability.FAU-Ticket : Fixed Part : Sequence Info = first int. Package 101 : not present Package 100 : Duration = t4 - t2 (1800 sec) Package 111 : Own FAU Term. Port. FAU-Ticket : Fixed Part : Sequence Info = last Package 101 : not present: Package 100 : Duration = t5 - t4 Package 111 : Own FAU Term. Port.

time t1 Answer t2 intermediate charging t3 t4 intermediate charging subscriber uses Terminal Portability feature t5 Release

Figure 7: Intermediate charging for FAU tickets in case of TPC, LGC or CT calls, the first generated FAU-ticket for the TPC/LGC/CT controller will have as Record Sequence single (when the three party conference, large conference, respectively call transfer duration is less than the intermediate time duration) or first intermediate (when the three party or large conference duration is greater than the intermediate time duration). tickets related to the same call all have the same package 110 (Connection Identification), or, when Global Call Reference is activated, the same package 149 (Global Call Reference). Charge Status For answered calls, the Charge Status is normally charge. Only in the following cases, the Charge Status is no charge: in case of an internal call (A- and B-party connected to the same exchange), if the B-party has the feature NOCHARGE (parameter NOCHARG in the CR SUB/PBX commands) in case of a call going out over an ISUP trunk, when the Backward Call Indicator no charge is set in the ISUP backward messages ACM (Address Complete) or ANM (Answer) in case a call is made to a charge free announcement in case of an IN call, when the Send Charging Info INAP message indicates no charge in case the charges are taken over by the B-party after a Reverse Charging request (conform ITU-T Q.736 and Q.956 specifications; for a description of this service, refer to /10/) initiated by the A-party, the Charge Status in the AMA tickets generated for the A-party indicates no charge.

38

P30308-X2058-K160-03-7617


For not answered calls, the Charge Status can have following values: If the call is released before the (project specific) criteria for call attempt are fulfilled, the Charge Status is set to undefined. If the call is released after the criteria for call attempt are fulfilled, the Charge Status is set to no charge in following cases: non-zero call attempt charges are administered and the B-party is connected to the same exchange and has the NOCHARGE feature non-zero call attempt charges are administered and the ISUP ACM Message has been received with Backward Call Indicator no charge non-zero call attempt charges are administered and the B-party is a non-chargeable announcement no call attempt charges are administered, but the mark ATTNOCHA (charging of charge free call attempts) is set with the command ENTR CDTDAT If the call is released after the criteria for call attempt charging are fulfilled, the Charge Status is set to charge in case non-zero call attempt charges are administered and none of the above mentioned criteria for no charge are fulfilled. A special case is the value charge transfer to B-side, which can only be present in the AMA ticket generated for the Reverse Charging Service (RCS). Refer to /10/ for a description of this service. Remarks: It is also possible to make calls free of charge by suppressing the Answer signal. This is in fact the only possibility in case analog trunks, which are not able to send the indication no charge, are present on the call path. For such unanswered calls, no AMA tickets are generated, unless AMA for unsuccessful calls is administered. In this case, AMA tickets for unanswered calls are detected by the Postprocessing based on Flag F33 (No Answer). The charge status is not relevant for facility usage: the mere presence of the FAU marks in the ticket implies that these FAUs are chargeable. By means of the flag F17 (AMA-FAU) it can be derived whether the charging of the FAU is to be done based on the AMA ticket or based on FAU charge units, which have been added on the subscribers counter. Record Owner Type The Record Owner Type indicates by means of a reference to the corresponding data package, which DN is to be considered as record owner of the AMA ticket. The Record Owner Type refers to either: the Calling Party Number, in case the AMA tickets are generated for a calling party (non-PBX) to charge a Connection, a Facility Input and/or a Facility Usage the Redirecting Number, in case the AMA tickets are generated for the redirecting party (non-PBX) of a diverted call or a the second leg of a CTX Dial In call. the System Provided Number, in case the AMA tickets are generated on the B-side of a call. in case the AMA tickets are generated on the A-side of a call for a PBX subscriber, whom is to be identified either by means of the Pilot Directory Number or by means of the Line Service Number (i.e. the Directory Number of the PBX line). in case the AMA tickets are generated for the following types of SCIs: Remote SCI, SCI performed for a (/another) target MSN, SCI for all Numbers, ISCI.

P30308-X2058-K160-03-7617

39


the Called Party Number, in case the AMA tickets are generated for a Wake Up call. the Service Subscriber Number, in case the AMA tickets are generated for the TFS subscriber, the Service Subscriber Number contains the TFS account number, which is generated (project specifically) based on the TFS service number, an account number prefix and exchange digits. in case of SIP-PSTN interworking, the Service Subscriber contains the URL of the calling SIP subscriber (refer to the description of package 179 for more information). Remark: If a CAMA Ticket is generated on an incoming trunk and the calling party number is not signalled over this trunk (e.g. analog trunks), the package 142 (Calling Party Number) is not provided and the Record Owner Type is set to undefined (0). Record Owner The Record Owner is only stored in the Fixed Part of the AMA tickets (fields 5 and following), when the craftsperson has requested it by means of ENTR CDTDAT: EXTNSD=RECOWNER. The Record Owner consists of the fields LAC Length, Owner ID Length and the Directory Number including the LAC, if this LAC is present. The Owner ID Length includes the LAC digits. The LAC Length has a maximum value of 6. The Directory Number contains at most 31 digits (including LAC). Whether or not the national or international prefix digits are included can be controlled by the craftsperson via MML-command ENTR CDTDAT. Remark: Hexadecimal digits (A till F) can be present. The Directory Number identifies either the number of the A subscriber as present in the exchange, in case an AMA record is generated for this subscriber on the A-side of a call. the number of the B subscriber as present in the database, in case an AMA record is generated for this subscriber on the B-side of the call (AMA records on the B-side of the call are generated in case of Facility Usage on the B-side, in case of IP/SN calls and in case of Reverse Charging). the inter-office signalled calling party number (if present), in case an AMA record is generated on an incoming trunk in a transit or terminating exchange. the account number in case of TFS. This account number is generated (project-specific) based on the TFS service number, an account number prefix and exchange digits. Remarks: In CAMA tickets and in TFS AMA tickets, the LAC Length is always equal to 0, because the number of area code digits is not signalled via trunk, except in case the CAMA ticket is generated on an incoming trunk with a LAC. When the A-party is a PBX, the Record Owner in the LAMA ticket is either the Pilot Directory Number or the Line Service Number (i.e. the Directory Number of the PBX line). The Record Owner in the CAMA ticket is always the Calling Party Number. Refer to the description of package 142 (Calling Party Number) for more information. In case the A subscriber has the Multiple Subscriber Number (MSN) feature, the Record Owner contains the number, which has been signalled as calling party number, on condition this number has been recognized by the exchange as one of the MSN numbers. Otherwise, the default number from the database is taken as Record Owner. Exception: in case an MSN subscriber performs an SCI for all numbers, the Record Owner contains the default MSN (not the signalled MSN).40 P30308-X2058-K160-03-7617


In case the A-party is a Centrex subscriber, the Record Owner contains the public DN, not the intercom number. C) Operating remarks The command ENTR CDTDAT:EXTNSD=RECOWNER; defines the layout of the Fixed Part of the AMA ticket. If the Extra Data Item is not requested, the Fixed Part contains the Record Owner Type; if the Extra Data Item is requested, the Fixed Part contains the Record Owner DN. Inclusion of the national or international prefix digits in the Record Owner DN (stored in the Fixed Part of the AMA ticket), is controlled with ENTR CDTDAT:EXTNSD=PFXNATIN. Remark that the parameter PFXNATIN is only relevant in combination with the parameter RECOWNER. The commands CR FAUCHA:FAC=,BILLING=AMA; or MOD CHRGFEA:DN=, LAC=, COS=FAUAMA; makes the FAU chargeable with AMA and will lead to the setting of flag F17 (AMA FAU). When the FAU is charged only with Metering, i.e. CR FAUCHA:FAC=, BILLING=METERING; or MOD CHRGFEA: DN=, LAC=, COS=FAUAMA is NOT entered, the Flag F17 (AMA FAU) is not set. However, when DEB tickets are made for the connection, the facility is used and the DEBFA flag (ENTR CDTDAT: MARKS=DEBFA) is set, the FAU will appear in the ticket and the flag F15 (Facility Usage) will be set. Call Attempt charges are administered via the parameters PLSATT (call attempt charges in pulse format) or CNYATT (call attempt charges in currency format) in the ENTR TAR command. An announcement is normally free of charge, unless it is made chargeable via the command CR ANGRP: TGNO = , GCOS = CHARGABL; The Record Owner in case of PBX calls is administered with the parameter CHRG = AMAPDN (Record Owner is the Pilot Directory Number), CHRG = AMALSN (Record Owner is the Line Service Number) or CHRG = AMASGN (Record Owner is the signalled Number) in the CR PBXLN command. A LAC can be assigned to a trunk group via the command CRTGRP: TGNO = , LAC = ; D) Postprocessing remarks An important difference between LAMA and CAMA records is the fact that in CAMA records, the field LAC Length of the DN identifying the Record Owner is always equal 0 (except the incoming trunk has a LAC). In case the LAC is not part of the DN (parameter LACPNO=NO in the ENTR DNATT command), the LAC is not present in the ticket. In case the immediate output of AMA ticket is used as charging method, the flag F35 (AMA Immediate

AMA-V16

Documents

Transcript of AMA-V16