100% found this document useful (1 vote)

956 views234 pages

AMA Output Data for Subscriber Charging

Q: Analyze how AMA ticket generation for Centrex intercom calls can impact facility input charges, with reference to relevant flags.

Centrex intercom calls utilize package-specific flags, such as F21 for Centrex intercom and optionally F22 and F23 to denote TFS subscribers and controller conditions. Flag F21 in AMA tickets, tied to Centrex-specific access codes, affects input charges by linking facility usage directly with intercom call identifiers. Consequently, facility charges reflect the Centrex infrastructure nuances, as managed by the AMA in tracking specific flag conditions that categorize and bill intercom calls .

Q: What role does the package length play in the ambiguity of address indicator settings, and how does this complexity affect ticket generation?

Package length plays a crucial role in the ambiguity of address indicator settings within telecom package management. The length of the package is typically indicated at byte 2 and is essential for the accurate processing and rejection of irrelevant packages during postprocessing . Some packages have fixed lengths, while others have lengths that need to be calculated, adding complexity to ticket generation . This complexity is compounded by the need to determine whether the package inclusion is necessary, for example, based on service type or customer-specific settings . The ambiguity in determining package length leads to complications in processing that can affect the generation of call tickets, especially when multiple conditions, such as the presence of certain features or project-specific requirements, dictate the mandatory attributes of a package . This multifaceted nature often requires customized postprocessing to ensure accurate ticket generation .

Q: How does the Subpackage Number in binary format influence the identification of PCM trunk channels and what impact does this have on AMA record processing?

The Subpackage Number in binary format is used to identify PCM trunk channels by specifying the CIC (Circuit Identification Code) PCM Number and the CIC Channel Number, both of which are represented in binary form. The CIC PCM Number ranges from 0 to 681 for DIU24 and 0 to 511 for DIU30, and the CIC Channel Number ranges from 0 to 23 or 0 to 31 depending on the trunk type . These elements enable precise identification of both the trunk and the specific channel in use on the PCM trunk, facilitating the accurate processing of Automatic Message Accounting (AMA) records by ensuring that incoming and outgoing trunk channels are correctly logged and charged . The CIC format is critical for identifying trunk connections in AMA tickets, allowing for tracking of call routes and billing accuracy within digital exchanges .

Q: What is the significance of packaging address codes in AMA tickets and how does this affect the processing of connection and FAU tickets?

Packaging address codes in AMA tickets are crucial for determining the ownership and responsibility for different types of telecommunications charges. The Record Owner Type within an AMA ticket defines the record’s ownership based on specific data packages. This can be based on the calling party number, redirecting party number, or system-provided number, depending on the context of the call or service . This identification affects how connection and FAU (Facility Usage) tickets are processed by indicating which subscriber or service is responsible for charges, particularly when facilities are used or connections are diverted . In essence, these address codes ensure accurate billing and accountability for calls and facility usage, enabling correct charge allocation for connection and FAU tickets . Without precise packaging of address codes, proper billing and charge assessment in telecommunication systems would be compromised, as it would be challenging to allocate costs accurately based on the activity and usage recorded in AMA tickets ."}

Q: What key role does the Flag F11 play in the AMA billing system, and how does its presence relate to other flags such as F13 and F17?

Flag F11 indicates that Detailed Billing (DEB) is set for the subscriber or PBX line making the call, often alongside Flag F13, which indicates AMA Connection, or Flag F17, which indicates AMA Facility Usage (FAU) is involved . The presence of F11 in combination with F17 shows that a subscriber/PBX with DEB has used a facility for which AMA was required . F13 is related to AMA tickets for Facility Input or automatic calls and doesn't appear in FAU tickets, whereas F17 signifies FAU charged with AMA. Hence, F11's relation to F13 and F17 helps delineate how different billing mechanisms are applied based on DEB and AMA requirements in the billing system ."}

Q: Evaluate the impact of Service Subscriber Numbers in AMA records with respect to diverse telecom services.

Service Subscriber Numbers in AMA records have a significant impact on diverse telecom services by providing a means to uniquely identify and charge subscribers for different services used. They play a crucial role in charging for TFS (Telephony Feature Service) subscribers, where the Service Subscriber Number includes the TFS account number, formed from the TFS service number, an account number prefix, and exchange digits . This ensures accurate billing based on specific services utilized by subscribers. Additionally, AMA records also capture information about internal and administrative services for ISDN subscribers, ensuring the authorization alignment with subscribed services . Furthermore, these numbers help manage detailed billing by setting flags that indicate when detailed billing or specific service usage (such as facility usage or operator-assisted calls) should be logged and charged .

Q: How does the Record Owner Type field in AMA configurations determine the identification of the ticket owner, and what impact does this have on CDR records?

The Record Owner Type field in AMA configurations determines the identification of the ticket owner by indicating which Directory Number (DN) should be considered as the record owner in the AMA ticket. This could be the Calling Party Number for calls generated by a non-PBX subscriber, the Redirecting Number for diverted calls, or the System Provided Number for PBX subscribers, among other identifications . The Record Owner DN is stored in the Fixed Part of the AMA ticket, and the details can include the Local Area Code (LAC) and the Directory Number . This setting affects CDR records as the identification influences whether the Record Owner is set or left undefined, impacting how charges are attributed and reductions in ambiguities in ticket processing ."}

Q: What challenges are associated with the diverse values of the Nature of Address Indicator (NADI), and how does it differentiate between types of subscriber numbers?

The Nature of Address Indicator (NADI) values present challenges in distinguishing subscriber numbers due to the diversity and overlap within its definitions. NADI differentiates types of numbers as follows: '1' indicates a subscriber number, '3' is for significant national numbers, and '4' is for international numbers . The ambiguity arises because values from '5-111' are spare, '112-126' are reserved for national use, and '127' is marked as spare, which can lead to difficulties in uniform implementation and misidentification of number types .

Q: Explain the purpose and significance of flag F13 for AMA tickets and the difference in its application between automatic calls and facility inputs.

Flag F13, in AMA tickets, serves two purposes: it indicates AMA involvement during automatic calls setup and marks Facility Input instances. For automatic calls, F13 shows that AMA recording occurred due to digit analysis or semi-permanent data on an incoming trunk. For Facility Input, recognized by F16, F13 reveals AMA as the charging method . For automatic calls, it signals that an AMA recording was encountered during setup, differentiating it from manual inputs where F13 marks Facility Input charging with AMA . Importantly, F13 is not set for Facility Usage (FAU) tickets, for which Flag F17 is used instead .

Q: Describe how the FLAG F15 is operationally distinct in handling Facility Usage in AMA tickets and under what conditions it is set.

Flag F15 in AMA tickets identifies when a chargeable Facility Usage occurs, set when package 111 (Facilities Used by Owner) registers in the ticket. This happens during chargeable facility use during a call, distinguishable from connections (F14) or facility inputs (F16). If the facility is only charged via Metering, F15 indicates its inclusion in AMA ticket records, particularly when DEB marks are present. However, it does not apply to facilities used by partners (package 112).

This 234-page document provides a detailed description of output data formats for postprocessing accounting and billing of telephone calls for subscribers. It describes the file formats for data storage on different systems and defines over 50 data packages that specify fields for call details like date, time, phone numbers involved, services used, charges, and other metadata. The document serves as a reference for understanding the raw call record data.

Uploaded by

Manoj Kumar Singh

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

100% found this document useful (1 vote)

956 views234 pages

AMA Output Data for Subscriber Charging

Uploaded by

Manoj Kumar Singh

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

Information

Description 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.

P30308-X2058-K160-03-7617

Table of Contents

0 General Information

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

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

2 Description of the File Format

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........................................................................ 28
4.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

5.1 AMA Record....................................................................................................... 31

5.1.1 Fixed Part (Header) .............................................................................................................31 5.1.2 Data Packages.....................................................................................................................42 [Link] Package 100: Date / Time / Duration ..............................................................................42 [Link] Package 101: Partner Directory Number .......................................................................44 [Link] Package 102: Service Info...............................................................................................46 [Link] Package 103: Charge Units For Connection .................................................................51 [Link] Package 104: Charge Units For Facility Usage.............................................................51 [Link] Package 105: Trunk Identification Incoming.................................................................53 [Link] Package 106: Trunk Identification Outgoing.................................................................54 [Link] Package 107: Trunk Identification Incoming (CIC Format)..........................................55 [Link] Package 108: Trunk Identification Outgoing (CIC Format)..........................................56 [Link] Package 110: Connection Identification Number .......................................................57 [Link] Package 111: Facilities Used By Owner ......................................................................58 [Link] Package 112: Facilities Used By Partner.....................................................................61

P30308-X2058-K160-03-7617

Table of Contents

[Link] Package 113: Facility Input ...........................................................................................62 [Link] Package 116: Date / Time ..............................................................................................66 [Link] Package 118: Digit String..............................................................................................67 [Link] Package 120: Calling Party Category...........................................................................68 [Link] Package 122: Zone.........................................................................................................69 [Link] Package 125: Account Code.........................................................................................73 [Link] Package 128: New Destination .....................................................................................74 [Link] Package 130: Traffic Quality Data ................................................................................76 [Link] Package 134: Durations Before Answer......................................................................79 [Link] Package 135: Chargeband ............................................................................................80 [Link] Package 136: UUS3 Counters.......................................................................................82 [Link] Package 138: B Meter Pulses .......................................................................................83 [Link] Package 139: Release Indication .................................................................................83 [Link] Package 142: Calling Party Number.............................................................................84 [Link] Package 143: IP/SN Charge Data .................................................................................87 [Link] Package 145: Billing CAC .............................................................................................89 [Link] Package 146: Third Party Number................................................................................94 [Link] Package 147: Tariff Info.................................................................................................98 [Link] Package 148: CAC New Destination ..........................................................................108 [Link] Package 149: Global Call Reference..........................................................................109 [Link] Package 150: Audit Trail .............................................................................................111 [Link] Package 151: Business Group Identification............................................................113 [Link] Package 152: Centrex Numbers .................................................................................113 [Link] Package 153: Received Called Party Number...........................................................117 [Link] Package 154: Additional Call Indicators....................................................................119 [Link] Package 155: Add On Tariff ........................................................................................124 [Link] Package 156: Advised Cumulated Charges ..............................................................129 [Link] Package 157: Outgoing PA Identification..................................................................130 [Link] Package 159: Additional Calling Party Number........................................................133 [Link] Package 167: Additional Numbers.............................................................................135 [Link] Package 168: Called Party Number............................................................................137 [Link] Package 170: Redirecting Number.............................................................................140 [Link] Package 171: Sent Called Party Number...................................................................143 [Link] Package 172: System Provided Number ...................................................................145 [Link] Package 178: Exchange Info.......................................................................................147 [Link] Package 179: Service Subscriber Number................................................................149 [Link] Package 183: Sent CAC...............................................................................................150 [Link] Package 184: MLPP Level ...........................................................................................151 [Link] Package 186: IN Service Key ......................................................................................153 [Link] Package 187: Received CAC.......................................................................................153 [Link] Package 191: Signalling Point Code ..........................................................................154 [Link] Package 192: Sent Calling Party Number..................................................................156 [Link] Package 193: Sent Redirecting Number....................................................................158 [Link] Package 194: Sent Calling Party Category................................................................160 [Link] Package 195: Original Calling Party Category..........................................................161 [Link] Package 196: Trunk Info..............................................................................................162 [Link] Package 198: Durations in 100 msec.........................................................................164 [Link] Package 199: Received Charge Determination Information....................................165 [Link] Package 204: Access Data..........................................................................................166 [Link] Package 205: Non Charged Facilities Used By Owner ............................................170 [Link] Package 209: Accumulated Currency Charges ........................................................171 [Link] Package 211: Additional Release Cause ...................................................................173 5.1.3 Project Specific Data Packages.......................................................................................177 [Link] Package 117: Project Specific Data .............................................................................177 [Link] Package 140: Incoming Route ID .................................................................................178 [Link] Package 141: Outgoing Route ID .................................................................................180 [Link] Package 176: ITU Calling Party Category....................................................................181 [Link] Package 177: Project Specific Service ........................................................................182 [Link] 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 ......................................................................... 196
6.4.1 Identifying the contents of the [Link] 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 ............................................................................. 198

6.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 ................................................................................................. 208
7.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

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

P30308-X2058-K160-03-7617

General Information

0 General Information
0.1 Status information
The document comprises a total of 234 pages. All pages have issue number 03.

0.2 History
Issue 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.

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 Charging
7

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 [Link]-30, no. 1 January 1982, pages 247..251 Description of Output Data P30309-A2814-K160-*-7617 (specific) Detailed Call Record Registration

P30308-X2058-K160-03-7617

General Information

0.4 Terms and Abbreviations

AAA 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

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

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 / Descriptor

AMA Ticket Charging DEB

0.6 List of figures and tables

Figure 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 ...........................................................115
P30308-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

P30308-X2058-K160-03-7617

Introduction

1 Introduction
AMA (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 [Link] file and AMA records for interadministration charging in the [Link] 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 [Link], 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

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 [Link] resp. in two files IA.ICIAR1 and IA.ICIAR2 stored in file [Link] stored in file [Link] stored in file [Link]

CDR feature active (one common record for AMA and IACAMA) stored in one file [Link] 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 [Link]

() 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 document

Chapter 2 gives a description of the structure of the file [Link] resp. [Link](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 [Link] 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 Scope
This 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/.

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 [Link] or [Link](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 [Link] or [Link](1/2) file: Date/Time Change record Overflow record Breakdown record

P30308-X2058-K160-03-7617

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 1
switch switch switch switch

border between two operators Operator 2

gateway
switch

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.

P30308-X2058-K160-03-7617

Introduction

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

Description of the File Format

2 Description of the File Format

2.1 Overview of AMA storage and transfer possibilities
The 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 [Link] (resp. [Link], 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

AMA or System Records

Filler

AMA or System Records

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

Description of the File Format

CP Buffers

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 disk

The 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/.

P30308-X2058-K160-03-7617

Description of the File Format

2.3 File format on MP disk

The 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 MOD

In case of a transparent copy from the [Link] resp. [Link](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 [Link] resp. [Link], [Link] or [Link], 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

Remarks on the File Contents

3 Remarks on the File Contents

Following records can be present in the [Link] file: AMA records There are different kinds of AMA records, according to the application. In the [Link] 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 [Link] file. System and Filler records are described in detail in chapter 5.2 and following.

P30308-X2058-K160-03-7617

Data Record Description

4 Data Record Description

4.1 AMA Record
An AMA Record consists out of two main parts: a fixed part, with a fixed structure a variable part, which contains several data packages
Fixed 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

Data Record Description

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]

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

Data Record Description

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 Packages

FAU 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

Data Record Description

Symbol Explanation
x [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 Records

System 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 Details

4.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

P30308-X2058-K160-03-7617

Data Record Description

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

Data Field Description

5 Data Field Description

5.1 AMA Record
5.1.1 Fixed Part (Header) A) Syntax description
Field 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 3
Length

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.

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

Record Sequence

Charge Status

Table 6: Layout of the Fixed Part of the AMA record based on Record Owner Type
Field 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 3
Length 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

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

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

Data Field Description

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

No
No

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

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

P30308-X2058-K160-03-7617

Data Field Description

Description of Field No 4: Record Sequence

Value 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 Status

Value 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 Type
Value 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 [Link] file, refer to Chapter 6.4.1.

P30308-X2058-K160-03-7617

Data Field Description

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.

P30308-X2058-K160-03-7617

Data Field Description

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 = 123456
AMA-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) [Link](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

Data Field Description

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.

P30308-X2058-K160-03-7617

Data Field Description

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 time
P30308-X2058-K160-03-7617 37

Data Field Description

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.

P30308-X2058-K160-03-7617

Data Field Description

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

Data Field Description

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

Data Field Description

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=<FAU>,BILLING=AMA; or MOD CHRGFEA:DN=<dn>, LAC=<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=<FAU>, BILLING=METERING; or MOD CHRGFEA: DN=<dn>, LAC=<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 = <announcement group>, 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 = <trunk group>, LAC = <area code>; 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 Output successful) can be used to avoid double charging by neglecting tickets with the flag F35 = 1. In case AMA tickets for unsuccessful calls are required, Flag F33 (No Answer) must be used to detect tickets for unsuccessful calls. A call duration = 0 (in package 100 (Date / time / Duration) or in package 198 (Durations in 100 ms)) is not sufficient to decide that the call has not been answered: since the duration has an accuracy of one second or 100 ms, it is possible that the call duration for an answered call equals zero. The flag F37 (Sequence Number in package 150 (Audit Trail) can be used to quickly determine whether the Sequence Number is present in the ticket. When present, the Sequence Number is located at the end of the record - 6 bytes (the two last bytes are occupied by the checksum; the previous 4 are the Sequence Number). The end of the record
P30308-X2058-K160-03-7617 41

Data Field Description

can quickly be located by using the record length, which is always stored at byte 2 and 3 of the ticket. The flag F38 (Checksum in package 150 (Audit Trail) can be used to quickly determine whether the Checksum is present in the ticket. When present, the Checksum is located at the two last bytes of the record. Not used (reserved or not applicable) flags have random values, i.e. they do not have a fixed value 0. 5.1.2 Data Packages

[Link] Package 100: Date / Time / Duration A) Syntax description

Field Byte Length Field Name 6 5 3 2 1 No Pos (bytes) 7 4 1 1 1 Package Number 2 Date / Time 2 1 year 3 1 month 4 1 day 5 1 hour 6 1 minutes 7 1 seconds 3 8 1 F7 F6 res tenths of seconds 4 9 3 Duration Remarks 0 binary; fixed value 100 (H64) binary; value 0-99 (H00 - H63) binary; value 1-12 (H01 - H0C) binary; value 1-31 (H01 - H1F) binary; value 0-23 (H00 - H17) binary; value 0-59 (H00 - H3B) binary; value 0-59 (H00 - H3B) refer to description of Flags below binary

Description of Field No 3:
Flags Flag F0 F6 F7 Value 0 1 0 1 0 1 Meaning year between 1900 and 1999 year starting from 2000 begin date time end date time time secure time insecure

P30308-X2058-K160-03-7617

Data Field Description

B) Functional description For answered calls, this package contains the date, time and the duration of the call part to which the ticket refers. For not answered calls, the duration is measured from seizure to release, but is set to zero in case the package 134 (Durations Before Answer) is present. The date/time is either the date/time of seizure (Flag F6 = 0) or the date/time of release (flag F6 = 1). Either this package or package 116 (Date / Time) with/without package 198 (Durations in 100 msec) is present in the ticket. More information about the presence of these two packages can be found at the description of package 116 (Date / Time) and package 198 (Durations in 100 msec) below. Remarks: The call duration never exceeds the value as indicated by the intermediate timer T114, (all administrable timer values in the exchange are indicated by a running number; see also Operating remarks). This timer has a value between 15 minutes and 9 hours. When the call lasts longer than the duration indicated by T114, an intermediate ticket is generated (intermediate tickets are characterized by a Sequence Info = First Intermediate or Intermediate). It is however quite possible, that in intermediate tickets the value is less than the value indicated by T114. This is because there are other occasions for the generation of intermediate tickets. They are described in /10/. The duration has an accuracy of 1 second. This implies that a duration of 0 seconds is possible, in exceptional cases. Time insecure means that the date/time indication is not guaranteed to be completely accurate. A typical case where the time is insecure is at the start of the APS, when the time is entered with the command ENTR TIME, but has not yet been adjusted with MOD TIME. C) Operating remarks The choice between begin or end date/time is made via command ENTR CDTDAT: ALTNSD = RANSWTIM; The intermediate timer T114 is administered via command: MOD TIOUT: TIMER = T114, TIMVAL=<hours-minutes-seconds-milliseconds>; D) Postprocessing remarks This package has a fixed length of 11 bytes. The package length is not included in the package itself. A possible use of the flag F7 (time secure/insecure) is to charge the subscriber with the lowest tariff when this flag is set. Remark that inside the exchange, the lowest tariff is applied for metering when the time is found to be insecure.

P30308-X2058-K160-03-7617

Data Field Description

[Link] Package 101: Partner Directory Number A) Syntax description

Field No 1 2 3 Byte Pos 1 2 3
Length

(bytes) 1 1 N

Field Name 3 2 1 7 6 5 4 Package Number reserved Number of Digits Digit (i) Digit (i + 1)

Remarks 0 binary; fixed value 101 (H65) binary; range (0:31) packed digits, values (H0:HF)

Digit (i): i is incremented every next byte as follows: i=1,3,....,2n-1

B) Functional description This package is only present in Connection and TFS tickets, when the package has been activated by the craftsperson. When the ticket is generated on the originating side of the call (in case of LAMA), this package contains the called party directory number, with which the call to the called party is set up. This number is equal to the digits dialled by the subscriber, or sent by the subscriber terminal as dialled digits, with following exceptions: when a service code is dialled before the B-party Number. The package contains only the B-party number, not the service code. Examples: when an Account Code is dialled, or when the access code for DEB Next Call is dialled before the B-party number. when the dialled digits are translated into a long number according to a Supplementary Service. In this case, the long number is provided by the exchange database. Package 101 contains the long number. These cases are: when the A-subscriber uses abbreviated dialling when the A-subscriber uses Voice Mail Service (VMS) when the A-subscriber uses the hotline or the hotline delayed feature when a Centrex subscriber dials an intercom number or a CTX access code when a Carrier Access Code has been dialled before the actual B-party number. The Carrier Access Code is stripped off and provided in package 145 (Billing CAC). Refer also to the description of package 153 (Received Called Party Number). When the ticket is generated on the terminating side of the call, this package contains the directory number of the A-party. A ticket generated on the terminating side of the call, containing this package, is only possible in case of a connection to an IP / SN (Intelligent Peripheral / Service Node). Refer to the description of package 143 (IP/SN Charge Data). in case of REV (Reverse Charging according to ITU-T Q.736 and Q.956) In case of CAMA tickets, package 101 (Partner Directory Number) contains the digits as they have been received over the trunk as called party digits (in case of ISUP trunks, the called party digits are contained in the IAM message), except when the digits contain a Carrier Access Code. This Carrier Access Code is stripped off, and provided in package 145 (Billing CAC). Remark that in case of IN calls, and in case of Number Portability, the received called party digits depend on the location of the switch, where the CAMA ticket is generated. In case the switch is located behind the number translation point, the called party digits contain the translated digits. In case the ticket is generated in the number translation point, or in a

P30308-X2058-K160-03-7617

Data Field Description

preceding switch, package 101 (Partner Directory Number) contains the digits before number translation. In case of TFS tickets, package 101 (Partner Directory Number) contains the destination number determined in the TFS exchange based on the dialled digits. Remarks: The package may contain a Directory Number, which is equal to the Directory Number stored in one of the following packages: package 168 (Called Party Number) (if the ticket is generated on the A-side of the call or on the diverting side of a diverted call) package 142 (Calling Party Number) (if the ticket is generated on the B-side of the call) package 170 (Redirecting Number) (if the ticket is generated on the diverted to-side of a diverted call or of the second leg of a "CTX Dial IN" call) package 128 (New Destination) (if the ticket is generated for a TFS subscriber) In case the Partner Directory Number is not equal to the dialled digits or the digits received over trunk, the received / dialled digits are included in the AMA ticket in package 153 (Received Called Party Number), on condition the generation of this package is triggered with ENTR CDTDAT. When the ticket is generated on the A-side of the call, the dialled national or international prefix is included in the Partner Directory Number. When the ticket is generated on the Bside of the call, the national or international prefix is not included. In case of an IN call, package 101 (Partner Directory Number) contains the IN service number, i.e. the number with which the IN service is accessed. The directory number of the physical B-party is collected in package 128 (New Destination). FAU tickets do not contain this package. The digits contained in this package are not necessarily equal to the digits sent out over a trunk to the next exchange. Inside the exchange, the dialled digits can be converted to other digits. The digits used to determine the outgoing trunk in the own switch can again be modified before they are sent out as called line digits over this trunk to the next exchange. In case the Partner Directory Number is not equal to the digits sent out over a trunk to the next exchange, the sent out digits are included in the AMA ticket in package 171 (Sent Called Party Number), on condition the generation of this package is triggered with ENTR CDTDAT. C) Operating remarks The inclusion of the package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = RECOWNER; which triggers at the same time the choice of layout for the Fixed Part of the AMA ticket (inclusion of Record Owner DN instead of Record Owner Type). Conversion of the dialled digits to other digits is done via the parameters NEWCODE or CONVCODE in the command CR DEST. With these converted digits, the routing (the exchange process to find a destination based on the digit information) is performed again. CR DEST: DEST = <destination>, CONVCODE = <converted digits>; CR DEST: DEST = <destination>, NEWCODE = <converted digits>; Modification of the digits before they are sent out over a trunk as called line digits is done with the parameters DICON and SSDI in the MML command CR ROUTE: ROUTE = <route>, DEST = <destination>, TGNO = <trunk group name>, DICON = <digit converting code>, SSDI = <starting position for sending out dialled digits>;

P30308-X2058-K160-03-7617

Data Field Description

D) Postprocessing remarks The package is only present in the AMA tickets when explicitly requested by the operator that the V12 interface concerning the Record Owner DN and Partner DN is restored. The information stored in this package is additional to the information stored in one of the following packages: package 128 (New Destination) package 142 (Calling Party Number) package 168 (Called Party Number) package 170 (Redirecting Number) When inclusion in the AMA ticket is requested, this package is always present in the Connection and TFS tickets and never present in FAU and SCI tickets. The package length is not included in the package itself. The package length has to be calculated in the following way: package length in bytes = 2 + [integral part of the division (Number of Digits + 1) / 2] [Link] Package 102: Service Info

A) Syntax description
Field No 1 2 3 4 Byte Pos 1 2 3 4 Length (bytes) 1 1 1 1 Field Name 7 6 5 4 Package Number Service Indicator Remarks 3 2 1 0 binary; fixed value 102 (H66) binary; refer to description of Service Indicator below binary; refer to description of Additional Information below Flag F1: 0: Bluebook 1: Redbook

Additional Information reserved F1

P30308-X2058-K160-03-7617

Data Field Description

Description of Field No 2:
Service Indicator Value 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Meaning reserved CM (Circuit Mode) Speech CM Unrestricted Digital Info CM 3.1 kHz Audio CM 7 kHz Audio CM Service 06 CM Service 07 Unknown Bearer Service PM (Packet Mode) B-Channel PM D-Channel PM BD-Channel Telephony ISDN 3.1 kHz Telephony ISDN 7 kHz Telefax Group 2\3 Telefax Group 4 Teletex 62 kBit/s Videotex Videotelephone SERV19 SERV20 SERV21 SERV22 SERV23 SERV24 SERV25 SERV26 SERV27 Semi-permanent Connection Non Voice Group Voice Group All Service Group

Description of Field No 3: Additional Information Project specific; additional information octet for Redbook subscribers. B) Functional description This package contains the Service as defined in the exchange. This package is only collected when the AMA ticket is generated for an ISDN subscriber. The Service is determined in the exchange in the following way: Based on Bearer Capability, High Layer Compatibility and Low Layer Compatibility information received from the ISDN subscriber, an internal service is built, which has a range from 1 to 18. This internal service is mapped onto an administrative service, which has a range from 1 to 31. This administrative service is used to check whether the subscriber has the authorization for this service, by comparing this administrative service with the services administered to the subscriber. Remark that the mapping table between internal and administrative service can be modified on project specific basis. It is e.g. possible that a project uses only the administrative services for Non Voice Group (29) and Voice Group (30).

P30308-X2058-K160-03-7617

Data Field Description

In the Connection tickets, the internal service is registered in this package; in the SCI tickets, the administrative service is registered in this package. Remarks: In case of Local Subscriber Controlled Input, the package is only present in case of a service dependent SCI. In case of Remote SCI, the package is only present in case of a service dependent SCI, with the additional condition that a service had been specified by the Remote Subscriber during the SCI. This package is also provided in CAMA tickets, on condition ISUP is present all the way between the origin and the CAMA exchange. The package is not provided in the AMA tickets generated for Wake up Calls. In case a fallback to a lower quality service occurs during call set up, the package contains the actually used service, and not the original service with which the A-party has set up the connection. The table above lists all values, which are possible in the exchange. The actual values, which can appear in the AMA tickets, depend however of project specific settings. Service 10 (PM D-channel) will in praxis never be present in an AMA ticket. The other Packet Mode services 9 and 11 are only present under limited circumstances. The following gives a description of the handling of the Packet Mode services: PM (Packet Mode) B-Channel (value 9) This value is used when a B-channel service is requested. A B-channel service means that the Packet Data are transmitted over a B-channel from the end-user to the DLU (Digital Line Unit: peripheral processor to which analog and ISDN subscribers are connected). From the DLU to the Packet Handler, either a Nailed up Connection or a Switched Connection is present. An AMA ticket can only arise for a switched connection between DLU and Packet Handler. In this case, the service will indicate PM B-channel. Remark however, that the AMA-ticket has no information at all about the packet data, which are transmitted over the switched connection. For the exchange, this is totally transparent. Registration of these data is performed in the Packet Handler. For a nailed-up connection, no AMA ticket is generated.

P30308-X2058-K160-03-7617

Data Field Description

possible generation of AMA ticket (only in case of switched connection) Switching Network in CP B-channel Connection to End User DLU 64 kbit channel
NUC or switched connection

LTGB

64 kbit channel

NUC or switched connection

64 kbit channel

LTG

64 kbit channel NUC or switched connection

Connection to Packet Handler

NUC or switched connection

Figure 8: Appearance of value PM B-Channel in package 102 (Service Info) PM D-Channel (value 10) A D-channel service means that the Packet Data are transmitted over the D-channel from the end user to the DLU. In the DLU (more precise, the SLMD inside the DLU), these Dchannel Packet Data are multiplexed onto a 64 kBit channel. These 64 kBit channels are always nailed up connections, for which in general no AMA tickets are generated. That implies that the service PM D-channel will never turn up in an AMA ticket.
Switching Network in CP D-channel Connection to End User DLU 64 kbit channel
NUC

LTGB

64 kbit channel NUC

LTG

64 kbit channel NUC

Connection to Packet Handler

Figure 9: Appearance of value PM D-Channel in package 102 (Service Info)

P30308-X2058-K160-03-7617

Data Field Description

PM Bd-Channel (value 11) This value is used for the connection from Packet Handler to Frame Handler. A Frame Handler is a concentrator in THE EXCHANGE, which decreases the number of channels between THE EXCHANGE and Packet Handler. A Frame Handler concentrates D-channel Packet Data onto a limited number of 64 kBit channels between the Frame Handler and the Packet Handler. These 64 kBit channels are called Bd-channels. These are either switched or nailed up connections. In case of switched connections, the Packet Handler always initiates the connection, that means the Frame Handler is always B-side from a Call Processing (set up of the switched connection) point of view. For this connection, the service Bd Channel is used. It is theoretically possible to generate an AMA-ticket for this connection, but this AMA-ticket would not have any relevance for the end user.
Switching Network in CP D-channel Connection to End User DLU 64 kbit channel
NUC

LTGB

64 kbit channel NUC

Frame Handler

Connection to Packet Handler

64 kbit channel NUC or switched connection

LTG

64 kbit channel NUC or switched connection

Figure 10: Appearance of value PM Bd-Channel in package 102 (Service Info) C) Operating remarks This package is available in the ticket by default. The package can however be administered: the presence of the package is canceled by the MML command CAN CDTDAT: EXTNSD = SERVINFO. The mapping between internal and administrative service can be administered with the command MOD CALLPOPT. D) Postprocessing remarks This package has a fixed length of 4 bytes. This length is not included in the package itself.

P30308-X2058-K160-03-7617

Data Field Description

[Link] Package 103: Charge Units For Connection A) Syntax description

Field No 1 2 Byte Pos 1 2 Field Name 6 5 (bytes) 7 4 1 Package Number 3 Call Charge Units
Length

Remarks 3 2 1 0 binary; fixed value 103 (H67) binary

B) Functional description This package contains the total amount of charge units that apply for the call, respectively for the SCI. FAU-charges are not included. In case of intermediate charging, the charge units are counted per registered call part (i.e. the charge units are reset after every intermediate registration). Remarks: When during the registration period the number of call charge units exceeds 65535, intermediate charging is performed. No differentiation is made between charge units, which are generated in the own exchange and the charge units which are received from a higher exchange. The package is available in originating, transit and end exchanges. The package can contain zero call charge units, i.e. when the charge status equals "no charge". C) Operating remarks The inclusion of the package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = CHARGES; which triggers at the same time the inclusion of the package 122 (Zone), package 104 (Charge Units for Facility Usage) and package 135 (Chargeband). D) Postprocessing remarks This package has a fixed length of 4 bytes. The package length is not included in the package itself. [Link] Package 104: Charge Units For Facility Usage A) Syntax description
Field No 1 2 Byte Pos 1 2 Field Name 6 5 (bytes) 7 4 1 Package Number 2 FAU Charge Units
Length

Remarks 3 2 1 0 binary; fixed value 104 (H68) binary

B) Functional description This package contains the sum of the applied charge units for all facilities which have been used during the call or call part, and which have been administered as chargeable.

P30308-X2058-K160-03-7617

Data Field Description

Remarks: The collection of FAU Charge Units is independent of the charge status of the connection: charge status equal to no charge does not imply that FAU Charge Units are equal to zero. When an FAU is used during a connection, the FAU charge units will only appear in the first intermediate ticket after the facility has been activated. When for the used FAU's no FAU charge units have been administered, the package can contain zero FAU charge units. In case of Three Party Conference and Large Conference, the FAU charge units only appear in the separate FAU tickets for the TPC or LGC usage. In case of Call Transfer, the FAU charge units only appear in the separate FAU ticket for Call Transfer invocation. When an FAU is repeatedly used, the FAU charge units appear in the FAU ticket for the repeated use. Example: Subscriber uses Terminal Portability feature. Terminal Portability has been administered as chargeable with metering: CR FAUCHA: FAC = TERMPORT, BILLING = METERING, METPULS = 5; Call is charged with AMA.
AMA Ticket : Fixed Part : Record Sequence = first int. Package 100 : Duration = t3 - t1 (1800 sec) Package 111 : Own FAU Term. Port. Package 104 : FAU Charge Units (5) AMA Ticket : Fixed Part : Record Sequence = interm. Package 100 : Duration = t4 - t3 (1800 sec) Package 111 : Own FAU Term. Port. Package 104 : FAU Charge Units (0) FAU-Ticket for repeated use Fixed Part : Record Sequence = single Package 101: not present Package 116 (Date/time) instead of Date/time/Duration Package 111 : Own FAU Term. Port. Package 104 : FAU Charge Units (5) AMA Ticket : Fixed Part : Record Sequence = last Package 100 : Duration = t5-t4 Package 111 : Own FAU Term. Port. Package 104 : FAU Charge Units (0)

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

Figure 11: Use of package 104 (Charge Units for Facility Usage)

P30308-X2058-K160-03-7617

Data Field Description

C) Operating remarks Making an FAU chargeable is done by the MML command CR FAUCHA or MOD CHRGFEA. The charge units for an FAU are indicated by the parameter METPULS in the MML command CR FAUCHA. The inclusion of this package in the AMA ticket is controlled by the command ENTR CDTDAT: EXTNSD = CHARGES; which triggers at the same time the inclusion of the package 122 (Zone), package 135 (Chargeband) and package 103 (Charge Units for Connection). D) Postprocessing remarks This package has a fixed length of 3 bytes. The package length is not included in the package itself. [Link] Package 105: Trunk Identification Incoming A) Syntax description
Field No 1 2 3 Byte Pos 1 2 8
Length

(bytes) 1 6 2

Field Name 7 6 5 3 4 Package Number Trunk Group Number Trunk Number

Remarks 2 1 0 binary; fixed value 105 (H69) char, max. 6 binary; range 1 - 16383

B) Functional description This package is only present in Connection and TFS tickets, when following conditions are fulfilled: the package has been activated by the craftsperson the A-side of the call is a trunk (i.e. the package is only present in CAMA tickets) Remarks: the AMA-ticket generated on an incoming PA-Slave connection is considered as a LAMA ticket, and hence will never contain this package. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = RECTRID; which triggers at the same time the collection of package 106 (Trunk Identification Outgoing) and package 157 (Outgoing PA Identification). When additionally, the command ENTR CDTDAT: ALTNSD = RECTRCIC; is executed, package 107 (Trunk Identification Incoming in CIC Format) and package 108 (Trunk Identification Outgoing in CIC Format) are generated instead of package 105 (Trunk Identification Incoming) and package 106 (Trunk Identification Outgoing). When additionally, the command ENTR CDTDAT: ALTNSD = TGNA; is executed, package 196 (Trunk Info) is generated instead of package 105 (Trunk Identification Incoming) and package 106 (Trunk Identification Outgoing).

P30308-X2058-K160-03-7617

Data Field Description

The Trunk Group Number corresponds to the parameter TGNO or TGN2 in the CR TGRP command. As default, TGNO is taken as Trunk Group Number. The use of TGN2 as Trunk Group Number is triggered by the command ENTR CDTDAT: ALTNSD = TGN2; The Trunk Number corresponds to the parameter LNO in the CR TGRP command. D) Postprocessing remarks This package has a fixed length of 9 bytes. The package length is not included in the package itself. The presence of this package or package 107 (Trunk Identification Incoming in CIC Format) can be used to distinguish a CAMA ticket from an A-sided LAMA ticket. [Link] Package 106: Trunk Identification Outgoing A) Syntax description
Field No 1 2 3 Byte Pos 1 2 8
Length

(bytes) 1 6 2

Field Name 3 7 6 5 4 Package Number Trunk Group Number Trunk Number

Remarks 2 1 0 binary; fixed value 106 (H6A) char, max. 6 binary; range 1 - 16383

B) Functional description This package is only present in Connection and TFS tickets, when following conditions are fulfilled: the package has been activated by the craftsperson the B-side of the call is a trunk (i.e. the call is not terminating in the own exchange, but routed to another one) or an announcement Remarks: In case the call is unsuccessful because all trunks of the outgoing trunk group are busy, package 106 (Trunk Identification Outgoing) and package 108 (Trunk Identification Outgoing in CIC Format) are not provided. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = RECTRID; which triggers at the same time, the collection of package 105 (Trunk Identification Incoming) and package 157 (Outgoing PA Identification). When additionally, the command ENTR CDTDAT: ALTNSD = RECTRCIC; is executed, package 107 (Trunk Identification Incoming in CIC Format) and package 108 (Trunk Identification Outgoing in CIC Format) are generated instead of package 105 (Trunk Identification Incoming) and package 106 (Trunk Identification Outgoing). When additionally, the command ENTR CDTDAT: ALTNSD = TGNA; is executed, package 196 (Trunk Info) is generated instead of package 105 (Trunk Identification Incoming) and package 106 (Trunk Identification Outgoing).

P30308-X2058-K160-03-7617

Data Field Description

The Trunk Group Number corresponds to the parameter TGNO or TGN2 in the CR TGRP command. As default, TGNO is taken as Trunk Group Number. The use of TGN2 as Trunk Group Number is triggered by the command ENTR CDTDAT: ALTNSD = TGN2; The Trunk Number corresponds to the parameter LNO in the CR TGRP command. D) Postprocessing remarks This package has a fixed length of 9 bytes. The package length is not included in the package itself. [Link] Package 107: Trunk Identification Incoming (CIC Format) A) Syntax description
Field No 1 2 3 4 Byte Pos 1 2 8 10
Length

(bytes) 1 6 2 1

Field Name 3 7 6 5 4 Package Number Trunk Group Number CIC PCM Number CIC Channel Number

Remarks 2 1 0 binary; fixed value 107 (H6B) char, max. 6 binary range 0-681 range 0-511 (DIU24) (DIU 30) binary range 0-23 range 0-31

B) Functional description When administered by the craftsperson, this package is generated under the same circumstances as described under package 105 (Trunk Identification Incoming), but instead of that package, i.e. package 107 (Trunk Identification Incoming in CIC Format) is only present in Connection and TFS tickets, when following conditions are fulfilled: the package has been activated by the craftsperson the A-side of the call is a trunk (i.e. this package is only present in CAMA tickets) The CIC format indicates that the trunk is identified with the number of the PCM (Pulse Code Modulation) trunk, and the number of the channel on this PCM trunk. Remarks: the AMA-ticket generated on an incoming PA-Slave connection is considered as a LAMA ticket, and hence will never contain this package. In case the CIC format is not relevant for the trunk group (this is e.g. the case for analog trunk groups), package 105 will be provided instead of package 107. C) Operating remarks The inclusion of this package instead of package 105 (Trunk Identification Incoming) in the AMA ticket is controlled via command ENTR CDTDAT: ALTNSD = RECTRCIC; which triggers at the same time, the inclusion of package 108 (Trunk Identification Outgoing in CIC Format) instead of package 106 (Trunk Identification Outgoing) (prerequisite is ENTR CDTDAT: EXTNSD = RECTRID). When additionally, the command ENTR CDTDAT: ALTNSD = TGNA; is executed, package 196 (Trunk Info) is generated instead of package 107 (Trunk Identification Incoming in CIC Format) and package 108 (Trunk Identification Outgoing in CIC Format).

P30308-X2058-K160-03-7617

Data Field Description

The Trunk Group Number corresponds to the parameter TGNO or TGN2 in the CR TGRP command. As default, TGNO is taken as Trunk Group Number. The use of TGN2 as Trunk Group Number is triggered by the command ENTR CDTDAT: ALTNSD = TGN2; D) Postprocessing remarks This package has a fixed length of 10 bytes. The package length is not included in the package itself. The presence of this package or package 105 (Trunk Identification Incoming) can be used to distinguish a CAMA ticket from an A-sided LAMA ticket. [Link] Package 108: Trunk Identification Outgoing (CIC Format) A) Syntax description
Field No 1 2 3 4 Byte Pos 1 2 8 10
Length

(bytes) 1 6 2 1

Field Name 3 7 6 5 4 Package Number Trunk Group Number CIC PCM Number CIC Channel Number

Remarks 2 1 0 binary; fixed value 108 (H6C) char, max. 6 binary range 0-681 range 0-511 (DIU24) (DIU 30) binary range 0-23 range 0-31

B) Functional description When administered by the craftsperson, this package is generated under the same circumstances as described under package 106 (Trunk Identification Outgoing), but instead of that package, i.e. package 108 (Trunk Identification Outgoing in CIC Format) is only present in Connection and TFS tickets, when following conditions are fulfilled: the package has been activated by the craftsperson the B-side of the call is a trunk (i.e. the call is not terminating in the own exchange, but routed to another one) The CIC format indicates that the trunk is identified with the number of the PCM (Pulse Code Modulation) trunk, and the number of the channel on this PCM trunk. Remarks: In case the CIC format is not relevant for the trunk group (this is e.g. the case for analog trunk groups and for announcements), package 106 will be provided instead of package 108. In case the call is unsuccessful because all trunks of the outgoing trunk group are busy, package 106 (Trunk Identification Outgoing) and package 108 (Trunk Identification Outgoing in CIC Format) are not provided. C) Operating remarks The inclusion of this package instead of package 106 (Trunk Identification Outgoing) in the AMA ticket is controlled via command ENTR CDTDAT: ALTNSD = RECTRCIC; which triggers at the same time, the inclusion of package 107 (Trunk Identification Incoming in CIC Format) instead of package 105 (Trunk Identification Incoming) (prerequisite is ENTR CDTDAT: EXTNSD = RECTRID).

P30308-X2058-K160-03-7617

Data Field Description

When additionally, the command ENTR CDTDAT: ALTNSD = TGNA; is executed, package 196 (Trunk Info) is generated instead of package 107 (Trunk Identification Incoming in CIC Format) and package 108 (Trunk Identification Outgoing in CIC Format). The Trunk Group Number corresponds to the parameter TGNO or TGN2 in the CR TGRP command. As default, TGNO is taken as Trunk Group Number. The use of TGN2 as Trunk Group Number is triggered by the command ENTR CDTDAT: ALTNSD = TGN2; D) Postprocessing remarks This package has a fixed length of 10 bytes. The package length is not included in the package itself. [Link] Package 110: Connection Identification Number A) Syntax description
Field No 1 2 3 Byte Pos 1 2 3
Length

(bytes) 1 1 4

Field Name 7 6 5 3 2 4 Package Number Package Length Connection Identification

Remarks 1 0 binary; fixed value 110 (H6E) binary; fixed value 6 (H06) binary

B) Functional description The Connection Identification is a unique identification for one call, that means: at one point of time, all different calls in one exchange have a different Connection ID all tickets for one call (AMA tickets, MOB (Meter Observation) tickets, IACAMA tickets, IN AMA tickets, all intermediate tickets) get the same Connection ID, independent whether these tickets are generated on the A- or B-side of the call (e.g. AMA tickets generated on the A-side of the call, and MOB terminating tickets, generated on the B-side of the same call have the same Connection ID). it is guaranteed that the same Connection ID will not appear again after at least 1 day. This estimation is based on the highest possible traffic in a configuration with a maximum of 2000 LTGs. In case of normal traffic, the same Connection ID will appear again after a much longer period. Remarks: In case of Call Forwarding, each leg A-B1 and B1-B2 is considered as a separate call, and hence gets a different Connection Id. In case of Three Party Conference, the separate FAU ticket for the conference usage gets the same Connection ID as one of the legs. The implementation is such that one of the legs is considered as the master, which is not only responsible for generating the ticket for the leg, but also the separate FAU ticket for the conference usage. Since this master leg uses the same internal call data resources, the same Connection ID appears. In case of Large Conference, the separate FAU ticket for the conference usage gets an own Connection ID, which is different from the Connection IDs of all the conference legs. The implementation is such, that for Large Conference, an internal connection is made to a conference hardware unit. This internal connection is treated like a separate call and therefore a separate Connection ID is generated.

P30308-X2058-K160-03-7617

Data Field Description

In case of Call Transfer, the separate FAU tickets for Call Transfer usage, contain the same Connection ID as one of the legs for the same reasons as described for Three Party Conference. The Connection ID is not signalled to other exchanges. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via the command ENTR CDTDAT: EXTNSD = CONNID; Remark that EXTNSD = CONNID is set by default, i.e. the package is collected without entering the above-mentioned command. When the command ENTR CDTDAT: EXTNSD = GCR; is entered, package 149 (Global Call Reference) is built instead of this package. D) Postprocessing remarks This package has a fixed length of 6 bytes. The package length is however included in the package itself, to permit extensions of the Connection ID in later versions, without great impact on Postprocessing. In FAU tickets, neither this nor package 149 (Global Call Reference) is present, when the Functional Protocol is used to request, interrogate, or cancel the CCBS and CCNR feature In SCI tickets, neither this nor package 149 (Global Call Reference) is present, when the Functional Protocol is used. In ISCI tickets, neither this nor package 149 (Global Call Reference) is present. [Link] Package 111: Facilities Used By Owner

A) Syntax description
Field No 1 2 3 Byte Pos 1 2 3 Length (bytes) 1 1 n Field Name 7 6 5 4 Package Number Package Length Facility 1 : Facility n Remarks 3 2 1 0 binary; fixed value 111 (H6F) total length of package binary; value between 3 (1 facility collected) and 10 (8 facilities collected) binary refer to description of field Facility below

Description of Field No 3:
Facility Value 1 2 3 4 5 6 7 8 9 10 58 Meaning three party conference call diversion immediate call diversion conditional call diversion don't answer call diversion busy Semi Permanent connection active abbreviated dialling hotline delayed hotline immediate AOC on request at beginning of the call Abbreviation used in CR FAUCHA CONF3 DIVI DIVCD DIVDA DIVBY SPCONN ABBD HOTLDEL HOTLIMM AOC1C P30308-X2058-K160-03-7617

Data Field Description

11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66

AOC on request during the call AOC on request at the end of the call call diversion unconditional to announcement call diversion uncond. to individual announcement call diversion unconditional to operator call hold CLIR on request CLIR suspension on request COLR on request COLR suspension on request CUG explicit outgoing access large conference malicious call identification (MCI) all calls malicious call identification (MCI) on request reserved (for project specific variant of MCI) subaddressing terminal portability user to user signalling 1 wake up call casual wake up call daily enquiry partial rerouting call completion to busy subscriber - request call completion to busy subscriber - interrogation call completion to busy subscriber - cancel verbal announcement of charges next call user to user signalling 3 call diversion to short announcement equipment call deflection CCBS call overflow DDI PBX voice mail service retrieval DIVI to VMS (voice mail service) DIVBY to VMS (voice mail service) DIVDA to VMS (voice mail service) wake up call on specific days call diversion with parallel ringing automatic recall automatic recall announcement attendant barge in user to user signalling 2 suspension of traffic restriction next call CCNR request CCNR cancel CCNR interrogation CCNR call call transfer A call transfer B DIVI with screening call completion on internet busy immediate call completion on internet busy user controlled voice over internet reverse charge at setup request reverse charge at setup accept reserved anonymous call rejection

AOC2C AOC3C DIVA DIVIA DIVOP CALLHOLD CLIRREQ CLIRSUSP COLRREQ COLRSUSP CUGOGREQ CONFL MCIIMM MCIREQ SADTRANS TERMPORT UTUSIG CACO DACO ENQUIRY PR CCBSREQ CCBSINT CCBSCAN VACNC UTUSIG3 DIVSAE DIVCDE CCBSCALL PBXOVFLW VMSQUERY DIVIVMS DIVBYVMS DIVDAVMS SACO DIVIP AR ARANN ATNBI UTUSIG2 TRARSUSP CCNRREQ CCNRCAN CCNRINT CCNRCALL CTAS CT DIVIS CCIBI CCIBU VOI RCREQS RCACCS ACREJ 59

P30308-X2058-K160-03-7617

Data Field Description

67 68 69 70 71 72 73 74 75 76 77 78 79 80 81-255

test message call diversion exchange controlled immediate call diversion exchange controlled busy call diversion exchange controlled no reply voice data protection call diversion on all lines disturbed connect with rerouting and recall call diversion on busy with screening call diversion on no answer with screening call diversion teleworker Call diversion immediate on PABX DDI extension Yearly alarm call order Announced diversion Diversion for logged out reserved

TESTREQ DECI DECBY DECDA VDP DIVALD CRR DIVBS DIVDS DIVITW DIVEI YACO DIVANN DIVLO

Table 13: Values for Facilities Used By Owner B) Functional description This package contains the chargeable facilities, which have been used by the record owner during the call. Up to 8 facilities can be collected for one call. This package is only relevant for Connection and FAU tickets. For a general description of the Facility Usage Charging concept, refer to /10/. Remarks: When a 9th chargeable facility would be used, the call is released. Most facilities can only be used after Answer signal has been received, or are only treated as chargeable as soon as the Answer signal is received (e.g. Abbreviated Dialling). Other facilities are immediately chargeable as soon as they are activated (e.g. UUS1). Such facilities give rise to AMA tickets for unanswered calls, although the flag AMA for unsuccessful calls is not set. The facility Subadressing is registered in AMA-tickets on the B-side of the call, although the facility is in fact used by the A-party. A from the system initiated Wake Up call is charged by means of FAU-charging, i.e. FAU tickets are generated for the subscriber that is woken up. C) Operating remarks Facility Usages are made chargeable with the MML-command CR FAUCHA: FAC = <facility>, BILLING = AMA; or CR FAUCHA: FAC = <facility>, BILLING = METERING, METPULS = <FAU charge units>; and ENTR CDTDAT: MARKS = DEBFA or MOD CHRGFEA: DN = <dn>, LAC = <lac>, COS = FAUAMA;

P30308-X2058-K160-03-7617

Data Field Description

D) Postprocessing remarks In order to count the number of times a particular facility has been used, the number of FAU or AMA tickets with this FAU and with Sequence Info = Single or Last have to be counted. Reason: as soon as a Facility is used, it appears in all subsequent intermediate records; each additional time the facility is used, an FAU ticket for repeated use is generated. Such a repeated use FAU ticket has always Sequence Info = Single. FAU tickets for repeated use are characterized by the presence of package 116 (Date / Time) instead of package 100 (Date / Time / Duration). The presence of package 116 (Date / Time) is however not sufficient to decide on FAU tickets for repeated use, since this package is also used for other Facility Usages. This package has a variable length. The length in bytes is stored on byte 2 of the package. [Link] Package 112: Facilities Used By Partner A) Syntax description
Field No 1 2 3 Byte Pos 1 2 3 Field Name 6 5 (bytes) 7 4 1 Package Number 1 Package Length
Length

Remarks 3 2 1 0 binary; fixed value 112 (H70) total length of package binary; value between 3 (1 partner facility) and 6 (4 partner facilities) binary refer to the Facility description below

Facility 1 : Facility n

Description of Field No 3:
Facility Value 1 2 3 4 5 39 Meaning partner of a conference call diversion immediate call diversion conditional call diversion don't answer call diversion busy call deflection

Table 14: Values of Facilities Used By Partner B) Functional description This field contains the facilities that have been used by the destination subscriber during the call. Up to 4 partner facilities can be collected for one call. Partner facilities are only registered at the originating side of the call. When the destination subscriber resides in another exchange, the Partner Facility registered at the originating side of the call is based on ISUP notifications in the Call Progress ISUP message and in the address complete ISUP message. Only the Partner Facilities, which are represented by such a notification, can be registered in the ticket at the originating side. Remarks: In case of multiple call diversion, the Partner Facility is only registered at the originating side of the call, and only once (only the first call diversion is registered as Partner Facility).

P30308-X2058-K160-03-7617

Data Field Description

AMA-Ticket for B1-sub : Package 111 : DIVI Package 112 : not present

B1 diverting to B2

AMA-Ticket for B2-sub : Package 111 : DIVI Package 112 : not present

AMA-Ticket for A-sub : Package 111 : Package 112 DIVI

switch

switch switch

switch

B2 diverting to B3

Admin in all exchanges: ENTR CDTDAT : EXTNSD = FAUPRTNR; CR FAUCHA : FAC = DIVI, BILLING = AMA;

Figure 12: Partner Facility in case of multiple diversion C) Operating remarks

The inclusion of package 112 in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = FAUPRTNR; Remark that EXTNSD = FAUPRTNR is set by default, i.e. without entering the parameter EXTNSD = FAUPRTNER within the ENTR CDTDAT command, package 112 will be collected.

D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. [Link] Package 113: Facility Input A) Syntax description
Field No 1 2 3 4 Byte Pos 1 2 3 4
Length

(bytes) 1 1 1 1

Field Name 7 6 5 4 Package Number Package Length F1 F2 Action Facility

Remarks 3 2 1 0 binary; fixed value 113 (H71) binary; fixed value 4 (H04) binary; refer to description below binary; refer to description below

P30308-X2058-K160-03-7617

Data Field Description

Description of Field No 3:
Action Value 1 2 3 4 5 6 7 8 9 10 11 Meaning activate deactivate enter data delete data interrogate assign remove reserved reserved delete next delete all

Table 15: Values of Facilities Input Actions This field contains the kind of modification that has been done (activate, enter data etc.) by the subscriber by means of a Subscriber Controlled Input
Flags Flag F1 F2 Value 0 1 0 1 Meaning Facility Input for one number Facility Input for all numbers Local SCI Remote SCI

Table 16: Values of Facilities Input Flags Description of Field No 4:

Facility Value 1 2 3 4 5 6 7 8 9 10 11 12-19 20 21 22 23 24 25-28 29 30-31 Meaning abbreviated dialling 5 abbreviated dialling 10 abbreviated dialling 20 abbreviated dialling 30 abbreviated dialling 40 abbreviated dialling 50 abbreviated dialling 60 abbreviated dialling 70 abbreviated dialling 80 abbreviated dialling 90 abbreviated dialling 100 reserved alarm call casual reserved alarm call daily reserved call deflection reserved carrier access code reserved Abbreviation FAICHA ABBD5 ABBD10 ABBD20 ABBD30 ABBD40 ABBD50 ABBD60 ABBD70 ABBD80 ABBD90 ABBD100 CACO DACO DIVCDE CAC used in CR

P30308-X2058-K160-03-7617

Data Field Description

32 33 34-36 37 38 39-48 49 50-51 52 53-55 56 57-65 66 67 68-70 71 72 73 74 75 76 77 78 79 80-81 82 83 84 85 86 87 88 89 90 91 93

94
95 96 97 98 99 100 101 102 103 104-105 106 107-108 109 110 111-113 114 115 116-120

traffic restriction class screening list for originating calls reserved call waiting general facility reset reserved wake up call on specific days reserved Calling Line ID restriction reserved B party not allowed to collect charges for incoming call reserved detailed billing traffic class dependent called line ID restriction reserved neutral SCI 1 neutral SCI 2 neutral SCI 3 neutral SCI 4 screening list diversion screening list terminating screening list selective ringing or call waiting general reset of all screening lists call diversion with screening reserved call completion immediate on internet busy call completion user controlled on internet busy hotline delayed reserved call diversion conditional call diversion to short announcement equipment call diversion do not disturb call diversion on busy call waiting on internet busy call diversion don't answer call diversion to announcement diversion immediate to VMS diversion on busy to VMS diversion on no answer to VMS call diversion to answer service call diversion to operator on no reply call diversion to operator unconditional call diversion immediate reserved call diversion with parallel ringing call diversion general reserved rejection of forwarded calls reserved keyword anonymous call rejection reserved malicious call identification on request malicious call identification immediate reserved

TRACL SCLSTO CW GFRESET SACO CLIR NOCOLC DEBCL CALR NSCI1 NSCI2 NSCI3 NSCI4 SCLSTDIV SCLSTT SCLSTRCW SCLST DIVIS CCIBI CCIBU HOTLDEL DIVCD DIVSAE DIVND DIVBY CWIB DIVDA DIVA DIVIVMS DIVBYVMS DIVDAVMS DIVTA DIVOPD DIVOP DIVI DIVIP DIVGEN REJDIV KEYWORD ACREJ MCIREQ MCIIMM

P30308-X2058-K160-03-7617

Data Field Description

121 122 123 124 125 126 127-133 134 135 136 137-138 139 140 141-143 144 145 146 147 148 149-151 152 153 154 155 156 157-159 160 161-162 163 164 165 166 169 170-177 178 178-226 227 228 229 230-247 248 249-255

attendant position make busy attendant group make busy attendant night service attendant camp on attendant logon diversion timer reserved feature subscription reserved diversion conditional to voice mail reserved calling line ID presentation restriction stop hunt reserved call waiting deluxe reserved incoming call barring screening list call waiting call transfer connections reserved automatic turn on call diversion on busy with screening call diversion on no answer with screening substitute ringing profile reserved teleworker reserved Subscriber credit limit Call diversion immediate on PABX DDI extension Screening list for Kick Out Yearly alarm call order Announced diversion Reserved Diversion for logged out Reserved call diversion to individual announcement voice data protection subscriber controlled input restrictions reserved connected line ID restriction reserved

PMB GMB NS ACO ATNLOGON TIMDIV FEATSUB DIVCDVMS CNIR STH CWDELUXE TRACLT SCLSTCW CTC ATO DIVBS DIVDS SUBST RNGPRF TW SCLIM DIVEI SCLSTKO YACO DIVANN DIVLO DIVIA VDP RSTSCI COLR

Table 17: Values for Facilities Administered by Subscriber Input (FAIS) B) Functional description This package is collected in SCI tickets, to describe the facility input for which the ticket has been made. The flags F1 and F2 are not relevant in case of ISCI.

P30308-X2058-K160-03-7617

Data Field Description

C) Operating remarks The facility input is made chargeable for all subscribers via the command CR FAICHA: FAC = <facility input>, BILLING = AMA; or For a specified subscriber all facility Inputs are made chargeable via the command MOD CHRGFEA: DN = <dn>, LAC = <lac>, COS = FAIAMA; D) Postprocessing remarks The package has a fixed length of 4 bytes. The package length is included on byte 2 in the package itself. [Link] Package 116: Date / Time A) Syntax description
Field Byte Length Field Name 6 5 3 2 1 No Pos (bytes) 7 4 1 1 1 Package Number 2 Date / Time 2 1 Year 3 1 Month 4 1 Day 5 1 Hour 6 1 Minutes 7 1 Seconds 3 8 1 F7 F6 res tenths of seconds Remarks 0 binary; fixed value 116 (H74) binary; value 0-99 (H00 - H63) binary; value 1-12 (H01 - H0C) binary; value 1-31 (H01 - H1F) binary; value 0-23 (H00 - H17) binary; value 0-59 (H00 - H3B) binary; value 0-59 (H00 - H3B) refer to description of Flags below

Description of Field No 3:
Flags Flag F0 F6 F7 Value 0 1 0 1 0 1 Meaning year between 1900 and 1999 year starting from 2000 begin date time end date time time secure time insecure

Flag F6 is only relevant in case of connection-tickets with refined durations (package 198 (Durations in 100 msec). B) Functional description This package replaces package 100 (Date / Time / Duration): in case of SCI tickets if the FAU-ticket is generated to indicate a repeated use of the FAU in FAU tickets if the used FAU is equal to CCBSREQ (call completion to busy subscriber request), CCBSINT (CCBS interrogation) or CCBSCAN (CCBS cancel) in FAU tickets if the used FAU is equal to CCNRREQ (call completion to subscriber no reply request), CCNRINT (CCNR interrogation) or CCNRCAN (CCNR cancel) in FAU tickets if the used FAU is equal to ACREJ (Anonymous Call Rejection).

P30308-X2058-K160-03-7617

Data Field Description

in FAU tickets if the used FAU is equal to TESTREQ (test message) in case for AMA the duration registration is defined with the refined granularity. C) Operating remarks This package is not explicitly administrable. It is implicitly administrable in case of refined duration registration. In that case, the package is registered together with the package 198 (Durations in 100 msec). D) Postprocessing remarks This package has a fixed length of 8 bytes. This length is not included in the package itself. [Link] Package 118: Digit String A) Syntax description
Field No 1 2 3 Byte Pos 1 2 3
Length

(bytes) 1 1 n

Field Name 7 6 5 4 Package Number Number of Digits Digit (i)

Remarks 3 2 1 0 binary; fixed value 118 (H76) binary; range (0:31) packed digits, values (H0:HF)

Digit (i + 1)

Digit (i): i is incremented every next byte as follows: i=1,3,....,2n-1

B) Functional description This package is used to store the digits, which are entered by the subscriber via Stimulus protocol, in order to perform a Subscriber Controlled Input. In case the subscriber uses the Functional protocol to perform the Subscriber Controlled Input, this package contains the data entered by the subscriber. In most cases, the digits entered by the subscriber are equal to the dialled digits. In some cases however, the dialled digits differ from the digit string needed for the Subscriber Controlled Input. Examples are the use of Abbreviated Dialling for the Subscriber Controlled Input, the dialling of the code for DEB Next Call in front of the digit string for SCI, or the dialling of an Account code in front of the digit string for SCI. In case of activation/deactivation of a screening list for a particular Call Forwarding Type, the Call Forwarding Type for which the list is activated or deactivated is indicated by means of an additional data digit in this package. The additional data digit is defined as follows:
Additional Digit for Call Forwarding Type Value 0 1 2 3 4 5 Meaning Call Forwarding Immediate Call Forwarding on Subscriber busy Call Forwarding on no answer Call Forwarding to Voice Mail Immediate Call Forwarding to Voice Mail on busy Call Forwarding to Voice Mail on no answer

In case of an SCI ticket for implicitly deactivated Call Forwarding, the data package is not generated. In case of ISCI, the data package is not generated.

P30308-X2058-K160-03-7617

Data Field Description

Remark: When the digit string contains a PIN (Personal Identification Number) or a keyword, this PIN or keyword is blended out by means of hexadecimal B digits.

C) Operating remarks This package is not administrable D) Postprocessing remarks In most cases, this package contains hexadecimal digits. The package length has to be calculated in the following way: package length in bytes = 2 + [integral part of the division (( Number of Digits + 1) / 2)] [Link] Package 120: Calling Party Category A) Syntax description
Field No 1 2 Byte Pos 1 2 Field Name 6 5 3 (bytes) 7 4 1 Package Number 1 Calling Party Category
Length

Remarks 2 1 0 binary; fixed value 120 (H78) refer to description below

Description of Field No 2:
Calling Party Category Value 0 1 2 3 4 5 6 7 8 9 10 11-15 Meaning undefined subscriber priority subscriber test equipment coin box operator national data transmission national subscriber or operator international w/o forward transfer data transmission international priority subscriber international operator international with forward transfer reserved for project specific applications

B) Functional description This package contains detailed information about the calling party. Remarks: This information is available in the originating exchange, and in transit- or end- exchanges, which have been reached via MFC and ISUP trunks. The category is registered with the MFC coding. In case of ISUP, the ISUP category is mapped into the MFC-Coded category. The package is not available in the AMA tickets generated for Wake up Calls. In the AMA tickets generated for the redirecting party (in case of Call Forwarding or CTX Dial IN call ), this package contains the category of the original calling party (not the category of the redirecting party or the CTX dial in point).

P30308-X2058-K160-03-7617

Data Field Description

In case of RSCI, this package contains the category of the calling party, not the category of the subscriber for whom the SCI is done. Also when the ticket is generated on the B-side of the call, this package contains the category of the calling party. C) Operating remarks This package is not administrable. D) Postprocessing remarks This package has a fixed length of 2 bytes. This length is not included in the package itself. This package will always be present in case the calling party is not a normal subscriber, i.e. package 120 will be present if and only if the category is different from 1 (and 0, which is undefined). [Link] Package 122: Zone A) Syntax description
Field No 1 2 Byte Pos 1 2 Field Name 6 5 (bytes) 7 4 1 Package Number 2 Zone
Length

Remarks 3 2 1 0 binary; fixed value 122 (H7A) binary; range between 0 and 511, with 255 as default value

B) Functional description In this package, the zone is collected. The zone is an exchange internal datum, which is used during the determination of online charging. The zone is assigned to the combination of dialled digits (or part of dialled digits), and origination dependencies. This zone represents basically the distance dependency of the call charges. By extension, the zone can also be made dependent of other criteria, like e.g. the category of the subscriber. In case of IN calls, the zone can be determined based on digits delivered from the SCP. To a zone, a tariff is coupled, which represents the time dependencies of the call charges. A zone equal 0 means that no online charges are registered for this call or call part (during the call, a zone = 0 can be changed to a zone different from 0; see further) A zone equal 127 indicates that the zone is not determined in the own but in another exchange. When a Chargeband is received from a higher exchange or from the SCP, this Chargeband is always mapped to a zone, which overwrites the zone currently present for the connection. In this case, and under the assumption that the craftsperson has activated the inclusion of the zone package in the AMA ticket, both packages Zone and Chargeband will be present in the ticket. It is possible that a Chargeband is received during the call, i.e. after the Answer signal has been received. In this case, first an intermediate ticket is generated with the old zone (and possibly the Chargeband); at the end of the call or at the next intermediate ticket, both the new zone and Chargeband will be present in the ticket. Refer also to the description of package 135 (Chargeband). Following figures illustrate the use of package 122.
P30308-X2058-K160-03-7617 69

Data Field Description

AMA-Ticket : Package 103 : charge units Package 122 : 10 Package 135 : not present

A-subscriber dials 2525357

switch

Subscriber with DN = 089 2449355

Subscriber with DN = 089 2525357

Admin : ENTR CDTDAT : EXTNSD = CHARGES; CR ZOPT : CODE = 252, ZONO = 10,BILLING = AMA; (further tariff administration is not considered)

Figure 13: Package 122 (Zone) in case of internal traffic (in the same local area)

AMA-Ticket : Package 103 : 0 Package 122 : 0 Package 135 : not present

A-subscriber dials 2525357

switch

Subscriber with DN = 089 2449355

Subscriber with DN = 089 2525357

Admin : ENTR CDTDAT : EXTNSD = CHARGES; CR ZOPT : CODE = 252, ZOCHA = NOPULSE, BILLING = AMA; (further tariff administration is not considered)

Figure 14: Zone = 0 in package 122 (Zone)

P30308-X2058-K160-03-7617

Data Field Description

AMA-Ticket : Package 103 : meter pulses received over trunk Package 122 : 127 Package 135 : not present

A-subscriber dials 090 2525357

switch

Meterpulses

switch

Subscriber with DN = 089 2449355

analog trunk

Subscriber with DN = 090 2525357

Admin : In originating exchange : ENTR CDTDAT : EXTNSD = CHARGES; CR ZOPT : CODE = 090, ZOCHA = ZONINHI, BILLING = AMA; (further tariff administration is not considered)

Figure 15: Zoning in higher exchange, analog trunk

AMA-Ticket : Package 103 : charge units corresponding to zone = 20 Package 122 : 20 Package 135 : 50

A-subscriber dials 090 2525357

Originating exchange : mapping of chargeband = 50 to zone = 20

switch

Terminating exchange : determination of zone = 10 and mapping to chargeband = 50

switch

Chargeband ISUP trunk

Subscriber with DN = 089 2449355

Subscriber with DN = 090 2525357

Admin : In originating exchange : ENTR CDTDAT : EXTNSD = CHARGES; CR ZOPT : CODE = 090, ZOCHA = ZONINHI, BILLING = AMA; (further tariff administration is not considered) MOD ZOINF : ZONO = 20, CHBNO = 50; In terminating exchange : Routing administration is assumed to be such that the LAC = 090 is not sent over ISUP CR ZOPT : CODE = 252, ZONO = 10, BILLING = METERING; MOD ZOINF : ZONO = 10, CHBNO = 50;

Figure 16: Zoning in higher exchange, ISUP trunk

P30308-X2058-K160-03-7617

Data Field Description

Remarks: The zone is an exchange internal notion; the Chargeband on the other hand, is a standardized notion (Chargeband is part of the ISUP Charging Message). The package is not present in the AMA tickets generated for IP/SN C) Operating remarks The inclusion of this package is triggered via the command ENTR CDTDAT: EXTNSD = CHARGES; which triggers at the same time the inclusion of package 103 (Charge Units for Connection), package 104 (Charge Units for Facility Usage) and package 135 (Chargeband). Determination of the zone in the own exchange is done via command CR ZOPT: CODE = <digits>, ZONO = <zone number>, BILLING = <metering or AMA>; The MML command CR ZOPT: CODE = <digits>, ZOCHA = NOPULSE, BILLING = <metering or AMA>; gives rise to Zone = 0 in package 122. The MML command CR ZOPT: CODE = <digits>, ZOCHA = ZONINHI, BILLING = <metering or AMA>; gives rise to Zone = 127 in package 122, as long as no Chargeband is received. The mapping between zone and Chargeband is done via the command MOD ZOINF: ZONO = <zone number>, CHBNO = <Chargeband number> D) Postprocessing remarks This package has a fixed length of 3 bytes. This length is not included in the package itself.

P30308-X2058-K160-03-7617

Data Field Description

[Link] Package 125: Account Code A) Syntax description

Field No 1 2 3 4 5 Byte Pos 1 2 3 4 5
Length

(bytes) 1 1 1 1 n

Field Name 7 6 5 4 Package Number Package Length reserved Number of Digits Digit (i)

Remarks 3 2 1 0 binary; fixed value 125 (H7D) binary; total length of package F1 = 0: default account code F1 = 1: dialled account code binary; range (0:24) packed digits, values (0:HF)

Digit (i + 1)

Digit (i): i is incremented every next byte as follows: i=1,3,....,2n-1

B) Functional description This package contains the default or the dialled account code. An account code is an additional digit string, which permits to split up the invoices to be paid by the record owner. The account code can be dialled explicitly, or a default value can be assigned to the subscriber. The use of a default account code is however only foreseen for Centrex subscribers, Centrex PBXs and Centrex PBX lines. When no Account code is assigned to a Centrex PBX line, the Account code assigned to the Centrex PBX is valid, if present. The dialled account code has priority over the default account code. A dialled account code is entered by means of a separate access code, followed by the destination number. This access code and the account code itself are part of the Package 153 (Received Called Party Number), if this package is present, but are not part of package 168 (Called Party Number) (resp. package 101 (Partner Directory Number)).
AMA-Ticket : Fixed part : Record Owner Type = Calling Party Package 142 (Calling Party Nr) : 89 2449355, NADI=national Package 168 (Called Party Nr) : 2525357, NADI=subscriber Package 125 : F1 = 1 (dialled account code) NO OF DIGITS = 4 DIGITS = 3456

switch

Subscriber with DN = 089 2449355

A-subscriber dials 993456*2525357

Admin : ENTR SCFEA : FEAT=USE-ARNO, CODE=*99;

Subscriber with DN = 089 2525357

Figure 17: Example of a dialled account code

P30308-X2058-K160-03-7617

Data Field Description

Remarks: This package is not available in CAMA tickets C) Operating remarks The package is not administrable; as soon as an account code is used, either default or dialled, the package is included in the AMA ticket. For the Subscriber Controlled Use of the account code, following commands are necessary: ENTR SCFEA: FEAT = USE-ARNO, CODE = <access code, e.g. *99>; A default account code for a Centrex subscriber is administered with the command ENTR CXSUB: LAC = <local area code>, DN = <directory number>, CXGRP = <Centrex group>, COSDAT = ARNO-<account code digits>; D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. [Link] Package 128: New Destination A) Syntax description
Field No 1 2 3 4 5 6 Byte Pos 1 2 3 4 5 6
Length

(bytes) 1 1 1 1 1 n

Field Name 7 6 5 3 2 1 0 4 Package Number Package Length res NADI (of New Destination) res NPI res Reason reserved Number of Digits Digit (i) Digit (i + 1)

Remarks binary; fixed value 128 (H80) binary; total length of package binary; refer to description binary; refer to description binary; range (0:31) packed digits, values (0:HF)

Digit (i): i is incremented every next byte as follows: i=1,3,....,2n-1

Description of Field No 3:
NADI (Nature of Address Indicator) (according to /8/) Value 0 1 2 3 4 5-111 112-126 127 Meaning spare (NADI not received or could not be determined) subscriber number unknown significant national number international number spare reserved for national use spare

P30308-X2058-K160-03-7617

Data Field Description

Description of Field No 4: NPI

NPI (Numbering Plan Indicator) (according to /8/) Value 0 1 2 3 4 5-6 7 Meaning spare ISDN (telephony) numbering plan spare data numbering plan telex numbering plan reserved for national use spare

Description of Field No 4: Reason for New Destination

Reason for New Destination Value 0 1 2 3 Meaning spare Toll Free Service IN spare

B) Functional description This package contains: the destination digits determined in the TFS exchange in case of a TFS call the destination digits as returned from the SCP (Service Control Point) in case of an IN call. an indication whether the call was a TFS or an IN call. The package is always included in the TFS tickets generated for the TFS subscriber. The package is only included in the AMA tickets generated for the calling line (in case of an IN- or TFS-call) when requested by the craftsperson. Remarks: The New Destination Digits are stored without national or international prefix digits included in the digit string. The NADI indicates whether the DN is a subscriber, a national or an international number. One IN call can consist of several call parts to different destinations, e.g. connection to different announcements before connection to the desired destination, follow-on (new call is set up to another destination without the calling line going on hook), rerouting when the destination cannot be reached. As a consequence, the New Destination Digits can change during the call. In each (intermediate) ticket, the actual new destination digits are stored. In case of IN, it is possible that the DN stored as New Destination Digits does not correspond exactly with what the SCP has provided, due to possible digit conversion. This digit conversion is controlled by the INAP parameter Cut & Paste" Since the new destination digits cannot be signalled over trunk, the package can only be present in the AMA tickets for the Calling Line: In case of an IN call, when the SSP (Service Switching Point, i.e. the switch that has the access to the SCP) is equal to the registering exchange (i.e. the exchange where the AMA tickets for the Calling Line are generated). In case of a TFS call, when the CAMA ticket for the Calling Line is generated in the TFS exchange.

P30308-X2058-K160-03-7617

Data Field Description

C) Operating remarks The inclusion of the package in the AMA ticket of the Calling Line is controlled via command ENTR CDTDAT: EXTNSD = NEWDEST; D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. [Link] Package 130: Traffic Quality Data A) Syntax description
Field No 1 2 3 4 Byte Pos 1 2 3 5
Length

(bytes) 1 1 2 1

Field Name 7 6 5 3 2 1 4 Package Number Package Length Cause Value res Coding res Location Standard

Remarks 0 binary; fixed value 130 (H82) binary; fixed value 5 (H05) binary; refer to description binary; refer to description

Description of Field No 3:
Cause Value Value 1 2 3 4 5 6 7 8 9 16 17 18 19 20 21 22 25 26 27 28 29 30 31 34 38 39 40 41 42 43 Meaning Unallocated (unassigned) number No route to specific transit network No route to destination Send special information tone Misdialled trunk prefix Channel unacceptable Call awarded and being delivered in an established channel Preemption Preemption - circuit reserved for reuse Normal call clearing User busy No user responding No answer from user (user alerted) Subscriber absent Call rejected Number changed Exchange routing error Non-selected user clearing Destination out of order Invalid number format Facility rejected Response to Status Enquiry Normal, unspecified No circuit/channel available Network out of order Permanent frame mode connection out-of-service Permanent frame mode connection operational Temporary failure Switching equipment congestion Access information discarded

P30308-X2058-K160-03-7617

Data Field Description

44 46 47 49 50 53 55 57 58 62 63 65 66 69 70 79 81 82 83 84 85 86 87 88 90 91 95 96 97 98 99 100 101 102 103 110 111 127

Requested circuit/channel not available Precedence call blocked Resources unavailable, unspecified Quality of service unavailable Request facility not subscribed Outgoing calls barred within CUG Incoming calls barred within CUG Bearer capability not authorized Bearer capability not presently available Inconsistency in designated outgoing access information, and subscriber class Service or option not available, unspecified Bearer capability not implemented Channel type not implemented Requested facility not implemented Only restricted digital information bearer capability is available Service or option not implemented, unspecified Invalid call reference value Identified channel does not exist A suspended call exists, but this call identity does not Call identity in use No call suspended Call having the requested call identity has been cleared User not member of CUG Incompatible destination Non-existing CUG Invalid transit network selection Invalid message, unspecified Mandatory information element is missing Message type non-existing or not implemented Message not compatible with call state or message type non-existent or not implemented Information element non-existent or not implemented Invalid information element contents Message not compatible with call state Recovery on timer expiry Parameter non existent or not implemented - passed on Message with unrecognized parameter discarded Protocol error, unspecified Interworking, unspecified

The values 0-127 contain the possible Cause values according to ITU-T (Q.850), on condition the Coding Standard is equal 0, indicating ITU Coding Standard The values greater than 127 have a project specific meaning

P30308-X2058-K160-03-7617

Data Field Description

Description of Field No 4:
Location Value 0 1 2 3 4 5 6 7 8-9 10 11-15 Meaning User Private network serving the local user Public network serving the local user Transit network Public network serving the remote user Private network serving the remote user reserve International network reserve Network beyond interworking point reserve

The values are the possible Location values according to ITU-T (Q.931)

Coding Standard Value 0 1 2 3 Meaning ITU standard reserved international standard national standard standard specific to identified location

B) Functional description Cause, Location and Coding Standard are standardized notions, described in /7/. Cause and Location describe the location and the reason why the call is released; the Coding Standard indicates the Standard which is used for the coding of the Cause (when the Cause is generated in the exchange and no project specific changes regarding the Cause/Location are implemented, the Coding Standard is equal to 0). Remarks: The Cause cannot be used to distinct between answered and unanswered calls: a normal call release by the originator of the call is indicated by Cause = 16 (Normal Call Clearing), independent whether the answer signal has been received or not. C) Operating remarks The inclusion of the package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = TRAFQUAL; Remark that EXTNSD = TRAFQUAL is set by default, i.e. the package is collected without entering the command mentioned above. D) Postprocessing remarks This package has a fixed length of 5 bytes. The package length is included on byte 2 in the package itself. The package is only provided at the end of the call, i.e. in the single or last ticket of the call.

P30308-X2058-K160-03-7617

Data Field Description

[Link] Package 134: Durations Before Answer A) Syntax description

Field No 1 2 3 Byte Pos 1 2 3 5 Field Name 3 2 1 0 6 5 (bytes) 7 4 1 Package Number 1 Package Length Durations Before Answer 2 duration from dial tone till address complete 2 duration from address complete till answer
Length

Remarks binary; fixed value 134 (H86) binary; fixed value 6 binary binary

B) Functional description Durations Before Answer has two components: the time interval between seizure and receipt of the address complete signal from the Bside. When however the call is disconnected before address complete has been received, the time interval between seizure and release of the call is registered. the time interval between the receipt of address complete signal and receipt of the answer signal from the B-side. When the call is disconnected before answer is received, the time interval between address complete and disconnect of the call is registered. Remarks: for tickets generated in the originating exchange, the time of seizure is equal to the time when the A-party receives dial tone. for tickets generated in the transit or terminating exchange, the time of seizure is equal to the time when the IAM is received.

C) Operating remarks The inclusion of the package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = DURBANS; Note that in case of refined durations (EXTNSD = REFINDUR), this package is not registered. Instead the durations before answer are then registered within the package 198 (Durations in 100 msec). D) Postprocessing remarks When activated by the craftsperson, the package is present in tickets with Record Sequence equal to single or first intermediate. The value Duration from Address Complete till Answer being zero indicates that the address complete signal has not been received. For unanswered calls (Flag F33 = 1 in the Fixed Part (Header) of the AMA ticket), the duration in package 100 (Date / Time / Duration) is 0 if the package 134 (Durations Before Answer) is present. This package has a fixed length of 6 bytes. The package length is included on byte 2 in the package itself.

P30308-X2058-K160-03-7617

Data Field Description

[Link] Package 135: Chargeband A) Syntax description

Field No 1 2 3 4 Byte Pos 1 2 3 5
Length

(bytes) 1 1 2 1

Field Name 7 6 5 4 Package Number Package Length Chargeband reserved

Remarks 3 2 1 0 binary; fixed value 135 (H87) binary; fixed value 5 binary; range 0 - 511 F1 = 0: no Chargeband message, F1 = 1: Chargeband message received

B) Functional description The Chargeband is a part of the ISUP CRG (Charge Information) Message as mentioned in the ITU document /8/. In this ITU specification, the format of this message is not specified, but indicated as subject of national specification. In the exchange, this CRG message is coded in the following way:
Parameter Message type Charge Band number Number of Charge Units End of optional parameters Type fixed optional optional optional Length (octets) 1 3 3 1

Table 18: Layout of the ISUP Charge Information message Remark that the CRG message contains Charge Units instead of a Charge Band Number in case an analog trunk was present on the call path between origin and destination. In this case, the package 135 (Chargeband) will not be provided in the AMA ticket.
switch

analog meter pulses CRG message

switch

AMA-Ticket without package 135

CRG message

switch

ISUP trunk

analog trunk

ISUP trunk

AMA-Ticket with package 135

Figure 18: Use of ISUP CRG message In case of IN calls, usually the messages CRGE (Charging Extended) and CRGA (Charging Extended Acknowledgement) are used for transport over ISUP. In contradiction to the CRG message, the CRGE message can be received after answer. In case of IN calls, Chargeband information can also be received from the SCP with the SCI (Send Charging Information) INAP message. In case the AMA ticket is not generated in the SSP, the CRGE message is used for further transport of the Chargeband information.

P30308-X2058-K160-03-7617

Data Field Description

SCP
INAP SCI message
switch

CRGE

switch

CRGE
switch

CRGA CRGA

switch

SSP

Figure 19: Transport of Chargeband information for IN calls The flag Chargeband Message Received indicates that a Chargeband has been received, and that this Chargeband appears for the first time in a ticket for the call. In case a Chargeband is received during the call (this is only possible in case a CRGE message is used), an intermediate ticket is generated, with either no Chargeband, or in case a Chargeband was already received, this old Chargeband. In the next ticket after receipt of the Chargeband, the new Chargeband is included, and the flag Chargeband Message Received is set on 1. In the following ticket, the new Chargeband is still included, but the flag Chargeband Message Received is not set anymore.
Admin : CR ZOPT : CODE = <dialled digits>, ZONO = 10, TKZOINF = YES, BILLING = AMA; MOD ZOINF : ZONO = 20, CHBNO = 30; AMA-Ticket : intermediate charging at receipt of chargeband Package 100 : t2-t1 Package 122: 10 Package 135: not present AMA-Ticket : intermediate charging because of long duration Package 100 : t3-t2 (1800 sec) Package 122: 20 Package 135: chargeband = 30 Flag F1 = 1 AMA-Ticket : intermediate charging because of long duration Package 100 : t4-t3 (1800 sec) Package 122: 20 Package 135: chargeband = 30 Flag F1 = 0 AMA-Ticket : last ticket at release Package 100 : t5-t4 Package 122: 20 Package 135: chargeband = 30 Flag F1 = 0 time t5

Answer chargeband = 30 received

intermediate charging

Release

Figure 20: Receipt of Chargeband during call Remarks: In case a Chargeband is received during the call (this is only possible in case CRGE / CRGA is used), this Chargeband comes immediately into effect, i.e. the new tariff according to the new Chargeband is immediately applied.

P30308-X2058-K160-03-7617

Data Field Description

The received Chargeband can come from a higher exchange, or, in case of an IN call, from the SCP, with the INAP SCI (Send Charging Information) message. C) Operating remarks The inclusion of this package is triggered via the command ENTR CDTDAT: EXTNSD = CHARGES; which triggers at the same time the inclusion of package 103 (Charge Units for Connection), package 104 (Charge Units for Facility Usage) and package 122 (Zone). In order to permit a Chargeband to be received during the call, the parameter TKZOINF has to be set on YES in the command CR ZOPT: CR ZOPT: CODE = <digits>, ZONO = <zone number>, BILLING = <metering or AMA>, TKZOINF = YES; The translation of a Chargeband into a zone is done via command: MOD ZOINF: ZONO = <zone>, CHBNO = <Chargeband>; D) Postprocessing remarks This package has a fixed length of 5 bytes. The package length is included on byte 2 in the package itself. [Link] Package 136: UUS3 Counters A) Syntax description
Field No 1 2 3 4 Byte Pos 1 2 3 5
Length

(bytes) 1 1 2 2

Field Name 7 6 5 3 2 4 Package Number Package Length UUS3 Messages Received UUS3 Messages Sent

Remarks 1 0 binary; fixed value 136 (H88) binary; fixed value 6 binary; range 0 - 65535 binary; range 0 - 65535

B) Functional description User to User Signalling 3 is a feature which permits to exchange D-channel messages transparently between two ISDN end users. Either the origin or the destination subscriber can activate the feature. After the partner has confirmed, UUS3 messages can be exchanged. This package contains the number of received, respectively the number of sent UUS3 messages. Remarks: Even when the destination subscriber activates the feature, the number of UUS3 messages is registered on the A-side of the call. In case of Reverse Charging (according to ITU-Q standard), the number of UUS3 messages is registered on the B-side of the call independent on who activated the feature (A-party or B-party). C) Operating remarks This package is indirectly administrable: with the command CR FAUCHA: FAC = UTUSIG3, BILLING = <metering or AMA>; the UUS3 facility is made chargeable. As soon as this feature is used and UUS3 messages are exchanged, the package is present containing the number of exchanged messages. D) Postprocessing remarks
82 P30308-X2058-K160-03-7617

Data Field Description

This package has a fixed length of 6 bytes. The package length is included on byte 2 in the package itself. This package will always be present together with package 111 (Facilities Used by Owner) containing the mark UTUSIG3. [Link] Package 138: B Meter Pulses A) Syntax description
Field No 1 2 3 Byte Pos 1 2 3
Length

(bytes) 1 1 2

Field Name 7 6 5 4 Package Number Package Length B Meter Pulses

Remarks 3 2 1 0 binary, fixed value 138 (H8A) binary, fixed value 4 binary

B) Functional description This package contains the total amount of charge units that are received from a higher exchange. In case of intermediate charging, the charge units are counted per registered call part (i.e. the charge units are reset after every intermediate registration). The B Meter Pulses are included in the Charge Units for Connection, stored in package 103 (Charge Units for Connection), except when the B Meter Pulses have to be suppressed upon request by the craftsperson. C) Operating remarks the inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: REC = AMA, EXTNSD = BMETPULS; Suppression of the B Meter Pulses is controlled via the parameter TRMETSUP in the command CR ROUTE: ROUTE=<route>, DEST=<destination>, TGNO=<trunk group number>, LNDES = TRMETSUP; D) Postprocessing remarks This package has a fixed length of 4 bytes. The package length is included on byte 2 in the package itself. [Link] Package 139: Release Indication A) Syntax description
Field No 1 2 3 Byte Pos 1 2 3
Length

(bytes) 1 1 1

Field Name 7 6 5 4 Package Number Package Length reserved

Remarks 3 2 1 0 binary; fixed value 139 (H8B) binary; fixed value 3 (H03) Release binary; refer to the description of Indication Release Indication

P30308-X2058-K160-03-7617

Data Field Description

Description of Field No 3:
Release Indication Value 0 1 2 3 Meaning spare call release initiated by A-party call release initiated by SSP or the network call release initiated by B-party

B) Functional description This package indicates which party in the call has initiated the release. The values call release initiated by A-party and call release initiated by B-party indicate that the A-party, respectively the B-party has gone On Hook first. Going On Hook is determined based on the Cause Value, stored in package 130 (Traffic Quality Data), i.e. when the Cause Value indicates no failure (Cause Value=0), Normal Call Clearing (Cause Value=16) or Normal, unspecified (Cause Value=31). This package is only collected in case of answered calls. The value call release initiated by SSP or Network indicates: that the call is released by the SSP or the SCP, in case of an IN-call or that the call is released by the Network (i.e. not released by A- or B-party going On-Hook)

C) Operating remarks The inclusion of package 139 in the AMA tickets is controlled via command ENTR CDTDAT: EXTNSD=RELIND;

D) Postprocessing remarks This package has a fixed length of 3 bytes. The package length is included on byte 2 in the package itself

[Link] Package 142: Calling Party Number A) Syntax description

Field No 1 2 3 4 5 6 Byte Pos 1 2 3 4 5 6
Length

(bytes) 1 1 1 1 1 n

Field Name 7 6 5 3 2 1 0 4 Package Number Package Length res NADI res NPI [Link]. Screening LAC Length Number of Digits Digit (i) Digit (i + 1)

Remarks binary; fixed value 142 (H8E) binary; total length of package binary; refer to description binary; refer to description binary packed digits, values (0:HF)

Digit (i): i is incremented every next byte as follows: i=1,3,....,2n-1

P30308-X2058-K160-03-7617

Data Field Description

Description of Field No 4:
NPI (Numbering Plan Indicator) (according to /8/) Value 0 1 2 3 4 5-6 7 Meaning spare ISDN (telephony) numbering plan spare data numbering plan telex numbering plan reserved for national use spare

Presentation Indicator (according to /8/) Value 0 1 2 3 Meaning presentation allowed presentation restricted address not available (national use) spare

Screening Indicator (according to /8/) Value 0 1 2 3 Meaning reserved for user provided, not verified user provided, verified and passed reserved for user provided, verified and failed network provided

Description of Field No 5:
Field Part Number of Digits LAC Length Meaning Range between 0-31 Total length of Calling Party Number, including LAC Range between 0-7

P30308-X2058-K160-03-7617

Data Field Description

B) Functional description The presence of this package is not administrable, except in case of Call Forwarding and Remote Subscriber Controlled input where the craftsperson must request the package by means of ENTR CDTDAT, in order to obtain the original calling party in this package. This package contains the DN identifying the calling party. The DN has either been provided by the network, has been signalled by the subscriber or has been received via trunk. When the AMA ticket is generated in the originating exchange (LAMA ticket), the package contains the number that results from the screening of the signalled calling party number (i.e. the number that is provided in the D-channel SETUP message as calling line number). The screening of the signalled calling party leads to the following contents of the package: in case the ISDN subscriber or PBX has the no screening of calling line special option, the package is provided with the signalled calling party number. in case the ISDN subscriber or PBX has the no screening option, the package will contain a default number. In case of PBX, this default number is either the Operator Number, when an Operator Number has been assigned to the PBX, or the Pilot Directory Number. in case the ISDN subscriber or PBX has the screening option, the screening can be successful or unsuccessful. Successful screening means that - in case of an ISDN subscriber, the signalled calling party corresponds with the DN that is assigned to the access - in case the ISDN subscriber has the Multiple Subscriber Number feature (MSN), the signalled calling party corresponds with one of the Multiple Subscriber Numbers that is assigned to the access. - in case of a PBX subscriber, the signalled calling party has been identified as being DDI digits, or as PDN without LAC + DDI digits or as PDN with LAC + DDI digits. In case the screening is not successful, the package is provided with the default number as is the case when the ISDN subscriber or PBX has the no-screening option. When no calling party number has been signalled by the subscriber (e.g. in case of an analog subscriber), the network provides the DN that is assigned to the access as calling party number. In case of analog PBX, the calling party number is determined based on the setting of the ANIPDN/ANILSN/ANIOPN parameter. In CAMA tickets, the package contains the inter-office signalled calling party (in case of ISUP, this is the calling party number as provided in the IAM message). Remarks: The screening is also possible for PBX which are connected to the exchange via MFCR2 trunks. The national or international prefix digits (e.g. 0 or 00) are never present in the package. In case the calling party is an ISDN 1TR6 (Redbook) subscriber, the subscriber can signal his DN including the terminating discriminating digit. In the LAMA tickets, this terminating discriminating digit is not stored as part of the DN in the package. In the CAMA tickets the DN as received via trunk is stored (i.e. the DN is stored in the way the subscriber has signalled it). When the DN has been signalled via trunk, the LAC Length is equal to 0, because the number of area code digits is not signalled via trunk. AMA tickets are - in principal - only generated when an Owner of the Record is available. In case of CAMA, due to signalling restrictions, it can occur that no Owner, i.e. no Calling Party Number, is available. In such a case, the connection is normally released. However upon

P30308-X2058-K160-03-7617

Data Field Description

request by the operator/project (MML controlled) the call may still be set up. In this case CAMA tickets are generated with no Calling Party Number at all. In case an ISDN MSN subscriber performs a Subscriber Controlled Input for another MSN of the same access, the SCI ticket does not contain this package. The MSN for which the SCI is performed (and who is to be charged for the SCI-action), is stored in package 172 (System Provided Number). Refer to the description of package 170 (Redirecting Number) for examples of Calling Party Number in case of Call Diversion, resp. Multiple Call Diversion or CTX Dial IN . In case of ISCI, this package contains the DN with which the subscriber has logged into the ISCI server. In this case, the DN is not screened by the system. C) Operating remarks The inclusion of this package in the AMA ticket in case of Call Forwarding or Remote SCI is controlled via command ENTR CDTDAT: EXTNSD = OCLGDN; The screening / no screening option is administered via the parameter NOSCCLIP in the CR and MOD SUB/PBX commands. The no screening of calling line special is administered via the parameter NOSCCLS in the CR and MOD SUB/PBX commands. For an analog PBX, the calling party number is determined via the command CR PBXLN: LAC = <lac>, DN = <dn>, COS = ANILSN or ANIPDN or ANIOPN; The operator number is administered via the parameter OPN in the command CR PBX. The operator number is composed out of the PDN + further digits. To avoid that the connection is forced released when no calling party number has been received via an incoming trunk, the following MML command must be entered: CR INC: INCEPT = ANIF, INRES = IGNORE; D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. [Link] Package 143: IP/SN Charge Data A) Syntax description
Field No 1 2 3 Byte Pos 1 2 3
Length

(bytes) 1 1 n

Field Name 7 6 5 4 Package Number Package Length Data

Remarks 3 2 1 0 binary; fixed value 143 (H8F) binary; total length of package char, max. 20 bytes

P30308-X2058-K160-03-7617

Data Field Description

B) Functional description An IP/SN (Intelligent Peripheral/Service Node) is able to offer additional services to the calling line (like e.g. Voice/Fax Mail). From the point of view of the exchange, an IP/SN is a normal PBX, connected via DSS1. The service deployment is completely handled by the IP/SN without active participation of the exchange. The IP/SN is able to send charge information via the DSS1 D-channel. This charge information will be copied transparently into this package in the AMA ticket. An IP/SN can receive terminating calls, and make originating calls itself. The exchange offers following charging concept for originating and terminating IP/SN calls: terminating IP/SN calls A DEB ticket will be generated on the B-side of the call. The Record Owner is the Pilot Directory Number of the IP/SN PBX, stored in package 172 (System Provided Number). The number of the calling line is stored in package 142 (Calling Party Number) (and eventually also in package 101 (Partner Directory Number) when so requested). When the IP/SN sends charging information via the D-Channel Facility message, an intermediate DEB ticket is built with this package containing the charge information from this Facility message. The charging of the originating subscriber is done with the common exchange methods (AMA or metering).
DEB-Ticket : Record Owner Type = System Provided Nr Package 172 (System Provided Nbr) : 89888, NADI=national Package 142 (Calling Party Nr.) : 892525357, NADI=national Package 143 : contents of Facility message LAC=089, DN=888
IP/SN PBX

switch

D-channel Facility message

subscriber with LAC = 089, DN = 2525357

Admin : CR PBX : DN= 888, LAC = 089, TYPE = IP, CHRG = DEB&IPCHRG;

Figure 21: Charging concept for IP/SN (terminating IP/SN calls) originating IP/SN calls The IP/SN makes on request of the calling line, a connection to another subscriber. This connection is charged with DEB. The Record Owner is the Pilot Directory Number of the IP/SN PBX, stored in package 172 (System Provided Number); the number of the called subscriber is stored in package 168 (Called Party Number) (and eventually also in package 101 (Partner Directory Number) when so requested). When the IP/SN sends charging information via the D-Channel Facility message, an intermediate DEB ticket is built with this package containing the charge information from this Facility message.

P30308-X2058-K160-03-7617

Data Field Description

Remarks: A DEB ticket for a terminating IP/SN call is an example of a DEB ticket generated on the Bside of the call. During one call, at most 10 IP/SN charge messages are allowed. Further charge messages are rejected. C) Operating remarks The package is not administrable. As soon as IP/SN charge data are received, the package will be built. An IP/SN PBX is administered via the command: CR PBX: DN= <pilot directory number>, LAC = <local area code>, TYPE = IP, CHRG = DEB&IPCHRG; D) Postprocessing remarks The content of this package is project specific. The total package length (in bytes) is located at the second byte of the package. [Link] Package 145: Billing CAC A) Syntax description
Field No 1 2 3 4 Byte Pos 1 2 3 4
Length

(bytes) 1 1 1 n

Field Name 7 6 5 3 2 1 0 4 Package Number Package Length CAC Type Number Number of of Prefix CAC Digits Digits Digit (i) Digit (i+1)

Remarks binary; fixed value 145 (H91) binary; total length of package refer to description packed digits, value (0:HF), including prefix digits

Digit (i): i is incremented every next byte as follows: i=1,3,....,2n-1

Description of Field No 3:
CAC Type Value 0 1 2 3 4-7 Meaning CAC type not available Call by call selected Preselected Call by call selection of preselected Spare

Field Part Number of CAC Digits Number of Prefix Digits

Meaning Range 0 7 Total length of the CAC (inclusive prefix) Range 0 3

P30308-X2058-K160-03-7617

Data Field Description

B) Functional description The CAC in this package identifies the network operator, which is responsible for the charging of the call. Originating exchange When the subscriber dials a CAC before he dials the destination digits, and if a CAC is required to reach the destination, package 145 is filled up with the dialled CAC. The CAC Type is set on Call by call selected. When the subscriber does not dial a CAC, but he has a CAC preselected, and if a CAC is required to reach the destination, package 145 is filled up with the preselected CAC. The CAC Type is set on Preselected. When the subscriber dials his own preselected CAC, and if a CAC is required to reach the destination, package 145 is provided with this CAC and the CAC Type is set on Call by call selection of preselected. When no CAC is necessary to reach the destination, package 145 is not provided, unless the presence of the Billing CAC is required by MML (ENTR CDTDAT: ALTNSD=OWNCAC). In this case, package 145 is filled up with the own carrier code (the CAC of the operator to which the exchange belongs) and the CAC Type is set on Preselected. Transit exchange Independent whether the CAC is received as own ISUP parameter (Transit Network Selection) or as part of the called party digits, the package 145 (Billing CAC) is filled up with the CAC digits, in case the CAC is necessary for routing. The CAC Type in package 145 equals the received MCE (Multi Carrier Environment; ISUP parameter for transport of the CAC Type). When no MCE is received, the value is set on spare. When only an MCE is received, package 145 will contain the CAC Type corresponding to this received MCE, together with the CAC of the own network, independent whether the CAC is necessary to reach the destination or not. When neither TNS (Transit Network Selection; ISUP parameter for transport of the CAC) nor MCE is received, package 145 will not be present, unless the presence of the Billing CAC is required by MML (ENTR CDTDAT: ALTNSD=OWNCAC). When a so-called transit subscriber is created in the carrier exchange with a preselected CAC, this CAC will be provided in package 145. A transit subscriber with a CAC different from the CAC of the own network is used in case of reselling: the carrier network resells a part of his resources to another carrier. In the following figure, a reselling configuration is shown, where Operator B resells a part of his resources to Operator C and to Operator D. A subscriber residing in a network of another operator, has subscribed to Operator C. The call is first routed to Operator B (based on the preselected CAC of the A subscriber). In the exchange of Operator B, it is detected that the subscriber belongs to Operator C, and the Billing CAC of this Operator is provided in the AMA ticket generated in the exchange of Operator B.

P30308-X2058-K160-03-7617

Data Field Description

border between
AMA Ticket with Billing CAC = CAC from Operator C

Reselling Operator B

Local Operator A

Operator C

switch

A subscriber has preselected CAC = Operator B

Operator D

Figure 22: Provision of Billing CAC in case of Reselling The field CAC Type describes which kind of CAC has been used. Following CAC types are defined: CAC type not available This value is only provided when the call arrives over a trunk, a CAC has been signalled over this trunk, however without a CAC type, and this CAC is used for routing Call by call selected This value is provided when the subscriber has dialled a CAC, and this CAC is also necessary for routing. Preselected This value is provided, when the subscriber has not dialled a CAC, a CAC is necessary for routing and one of the following conditions are fulfilled: the subscriber has a default CAC assigned (max. 2 default CACs can be assigned to a subscriber) a Centrex subscriber dials a digit string which is defined as a Centrex code point, with a CAC included in it a Centrex subscriber belongs to a Centrex Group with a 1 or 2 preselected CACs Call by call selection of preselected This value is provided when the subscriber dials his own default CAC. Whether a default or dialled CAC is to be used for routing or not is controlled by the craftsperson via the MML command CR CACCPT. A CAC can be composed out of a Carrier Prefix and a Carrier Code. When all CACs in the own network start with the same digits, these digits can be defined as a Carrier Prefix. This Carrier Prefix can get a project specific treatment (e.g. cut off before sending over ISUP).

P30308-X2058-K160-03-7617

Data Field Description

Remarks: A preselected CAC can be administered: at subscriber/PBX level (1 or 2 preselected CACs can be administered) at Centrex Group level (1 or 2 preselected CACs can be administered) at Centrex Code Point level (this CAC will be used for routing to the destination, assigned to the Centrex Code Point) at Centrex DN level (this CAC will be used for routing to the destination, assigned to the Centrex intercom number) When a CAC is necessary to reach the destination, and the subscriber has neither dialled a CAC, nor has a CAC preselected, one of the network default CACs is taken, i.e. one of the two values which has been administered for the whole exchange (EXCCAC1 or EXCCAC2). This CAC is not considered as a Billing CAC, and hence, will not appear in package 145. If required by the craftsperson, this CAC is provided in package 183 (Sent CAC). A CAC can also be assigned to an incoming trunk group. Even when such a CAC is used to reach the destination, this CAC is not considered as a Billing CAC, and hence, will not appear in package 145. If required by the craftsperson, this CAC is provided in package 183 (Sent CAC). A CAC can be part of the new destination digits, determined during digit conversion (routing digits are converted to other digits, and these digits contain a CAC). Even when such a CAC is used to reach the destination, this CAC is not considered as a Billing CAC, and hence, will not appear in package 145. If required by the craftsperson, this CAC is provided in package 183 (Sent CAC). By default, the CAC does not specify the NADI, i.e. the NADI is determined by the called party number. It can however be specified that the CAC determines the NADI. A Centrex specific access code can be defined, to allow dialling a CAC by a Centrex subscriber. The definition of the Billing CAC (package 145) as being the identification of the network operator, which is responsible for the charging of the call, does not apply in case of an IN call. Details about CAC information for IN calls can be found in /10/. C) Operating remarks The package is also provided in tickets for unsuccessful calls. The inclusion of this package in the AMA ticket is controlled via the command ENTR CDTDAT: EXTNSD = CAC; Remark that EXTNSD = CAC is set by default, i.e. without entering the parameter EXTNSD = CAC within the ENTR CDTDAT command, the package will be collected. The inclusion of this package in the AMA ticket is also controlled via the command ENTR CDTDAT: ALTNSD = OWNCAC; If this command is entered, the package will always be present, even when no CAC is necessary to reach the destination. The field CAC Type in the package can be controlled with the command ENTR CDTDAT: ALTNSD = CACTYPE; If this command is entered, the package will contain the values compatible with former versions. The mapping is done as follows:

P30308-X2058-K160-03-7617

Data Field Description

CAC Type (0) (1) (2) (3) Spare Call by call selected Preselected Call by call selection of preselected

alternative CAC Type (0) (3) (2) (6) CAC Type not available Subscriber dialled and used Subscriber default Subscriber dialled and default

The carrier access code is entered in the exchange via command CR/MOD CAC which does the following: creates the carrier access code (parameter CAC) defines a name for the carrier code (parameter CARRIER) decides whether this carrier access code is the carrier access code belonging to this exchange (parameter OWNCAC) decides whether this carrier access code is the default exchange carrier access code 1 or 2 (parameter EXCCAC1 respectively EXCCAC2) decides whether the own carrier of the exchange must be ignored for routing and zoning (parameter ROWNCAC) Making a default or dialled CAC necessary for routing (or not) is administered via command CR CACCPT. This command performs the following actions: specifies the carrier code for which carrier access code handling is to be entered (parameter CODE) specifies for the specified destination code which preselected carrier, CAC1 or CAC2, must be taken (parameter DEFCAC) specifies whether the dialled and/or the default CAC must be taken/ ignored or intercepted for the destination code (parameters CACGHDI, CACGHPS, CACGHUC). The Carrier Prefix is administered via the command ENTR DNATT: PFXCAC = <CAC prefix>; A CAC (max. 2 default CACs are possible) is assigned to a subscriber/PBX via CR SUB/PBX/PBXLN: DN = <directory number>, LAC = <local area code>, COSDAT = CAC1-<carrier access code>, COSDAT = CAC2-<carrier access code>; A CAC on Centrex Group Level is administered with the command CR CXGRP: CXGRP = <Centrex Group>, COSDAT = CAC1 - <preselected Carrier Access Code 1>, CAC2 = <preselected Carrier Access Code 2>; A CAC on Centrex Code Point Level is administered with the command CR CXGRP: CXGRP = <Centrex Group>, CXCODE = <Access Code>, TRATYP = <traffic type>, DEST = <destination>, CAC = <Carrier Access Code>; A CAC on Centrex DN Level is administered with the command CR CXDN: CXGRP = <Centrex Group>, CXDN = <Centrex intercom number>, DN = <public number>, CAC = <Carrier Access Code>; D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package.

P30308-X2058-K160-03-7617

Data Field Description

[Link] Package 146: Third Party Number A) Syntax description

Field Byte Length Field Name Remarks 3 2 1 0 6 5 No Pos (bytes) 7 4 1 1 1 Package Number binary; fixed value 146 (H92) 2 2 1 Package Length binary; total length of package 3 3 1 reserved Third Party Type binary; refer to description 4 4 1 res res F6 F5 F4 F3 F2 F1 flags; refer to description 5 5 1 res NADI (of third party) binary; refer to description 6 6 1 res NPI reserved binary; refer to description 7 7 1 Number of Digits binary; range (0:31) 8 8 n Digit (i) Digit (i+1) packed digits, value (0:HF) Digit (i): I is incremented every next byte as follows: i=1,3,....,2n-1

Description of Field No 3:
Third party type Value 0 1 2 3 15 Meaning Reserved Call Transfer Partner Not applicable Reserved

Description of Field No 4:
Flags Flag Meaning F1 Local intercom call F2 Remote intercom call F3 Intra charging site call F4 Inter charging site call F5 Public call F6 Public business call This field is only relevant in case the Third Party Type indicates Call Transfer Partner. In this case, the flags are the Call Indicators of the other leg in the transferred call (compare with the Call Indicators for the own leg in package 154 (Additional Call Indicators)).

Description of Field No 5:
NADI (Nature of Address Indicator) (according to /8/) Value Meaning 0 spare (NADI not received or could not be determined) 1 subscriber number 2 unknown 3 significant national number 4 international number 5-111 spare 112-126 reserved for national use 127 spare

P30308-X2058-K160-03-7617

Data Field Description

Description of Field No 6:
NPI (Numbering Plan Indicator) (according to /8/) Value 0 1 2 3 4 5-6 7 Meaning spare ISDN (telephony) numbering plan spare data numbering plan telex numbering plan reserved for national use spare

B) Functional description In case of Call Transfer, this package is present in the tickets generated for the controller who transfers the call, and contains the DN of the other partner in the transferred call. The flags F1 till F6 contain additional call indicators with information about the type of CTX call of the other call leg.

P30308-X2058-K160-03-7617

Data Field Description

In the following figures, the contents of the package in case of A-side, respectively B-side call transfer are shown.
First intermediate AMA Ticket for A - B connection (at the moment of Call Transfer) Record Owner Type = Calling Party Package 142 (Calling Party Nr) : 902521861, NADI=national Package 168 (Called Party Nr) : 892525357, NADI=national Package 146 : not present Package 111 : not present First intermediate AMA Ticket for A - C connection (at the moment of Call Transfer) Record Owner Type = Calling Party Package 142 (Calling Party Nr) : 902521861, NADI=national Package 168 (Called Party Nr) : 912526678, NADI=national Package 146 : not present Package 111 : not present

switch

A-subscriber with LAC = 090, DN = 2521861

switch

B-subscriber with LAC = 089, DN = 2525357

A-subscriber calls B A-subscriber calls C A subscriber transfers call

C-subscriber with LAC = 091, DN = 2526678

AMA Ticket for A - B connection (at the End of the Call) Record Owner Type = Calling Party Package 142 (Calling Party Nr) : 902521861, NADI=national Package 168 (Called Party Nr) : 892525357, NADI=national Package 146 (Third Party) : 912526678, NADI=national Package 111 : Own FAU = CTAS

Single FAU Ticket for usage of Call Transfer (at the End of the Call) Fixed Part: F23 = 1 (Ticket for Call Transfer Controller) Record Owner Type= Calling Party Package 142 (Calling Party Nr) : 90 2521861, NADI=national Package 168 : not present Package 100 (Date/Time/Duration) Package 111 : Own FAU = CTAS

AMA Ticket for A - C connection (at the End of the Call) Record Owner Type = Calling Party Package 142 (Calling Party Nr) : 902521861, NADI=national Package 168 (Called Party Nr) : 912526678, NADI=national Package 146 (Third Party) : 892525357, NADI=national Package 111 : Own FAU = CTAS

Figure 23: Third Party Number in case of A-side Call Transfer

P30308-X2058-K160-03-7617

Data Field Description

First intermediate AMA Ticket for B - C connection (at the moment of Call Transfer) Record Owner Type = Calling Party Package 142 (Calling Party Nr) : 89 2525357, NADI=national Package 168 (Called Party Nr) : 912526678, NADI=national Package 146 : not present Package 111 : not present
switch

AMA Ticket for A - B connection (at the End of the Call) Record Owner Type = Calling Party Package 142 (Calling Party Nr) : 90 2521861, NADI=national Package 168 (Called Party Nr) : 892525357, NADI=national Package 146 : not present
A-subscriber with LAC = 090, DN = 2521861

A-subscriber calls B B-subscriber calls C B subscriber transfers call

switch

B-subscriber with LAC = 089, DN = 2525357

C-subscriber with LAC = 091, DN = 2526678

Single FAU Ticket for usage of Call Transfer (at the End of the Call) Fixed Part: F23 = 1 (Ticket for Call Transfer Controller) Record Owner Type = Calling Party Package 142 (Calling Party Nr) : 89 2525357, NADI=national Package 168 : not present Package 100 (Date/Time/Duration) Package 111 : Own FAU = CT

AMA Ticket for B - C connection (at the End of the Call) Record Owner Type = Calling Party Package 142 (Calling Party Nr) : 89 2525357, NADI=national Package 168 (Called Party Nr) : 912526678, NADI=national Package 146 (Third Party) : 902521861, NADI=national (on condition this number has been signalled) Package 111 : Own FAU = CT

Figure 24: Third Party Number in case of B-side transfer Remarks: In case the ticket is generated for a Centrex subscriber, the package always contains a public DN, not an intercom number. In case of B-side Call Transfer, the CTX call indicator "Public business call" of the other leg is not provided. A special case is Call Transfer in ringing state (the call is transferred before the C-subscriber answers), and the C-subscriber does not answer at all. Assuming B-side transfer and assuming that no AMA tickets for unsuccessful calls are generated, an FAU ticket for the usage of Call Transfer is generated for the leg from B to C, besides the FAU Ticket for the usage of Call Transfer. The two tickets differ only in the fact that in the last ticket, the flag F23 (Call Transfer controller) is set. For both tickets, flag F33 in the Fixed Part indicates no answer. The reason is, that Call Transfer is one of the features, which is immediately considered as used (refer to /10/ for more information). For the leg from B to C, the facility usage for Call Transfer has to be registered. Normally, this registration is done by marking the FAU in package 111 in the AMA ticket for the connection (see figure above). Since however the call

P30308-X2058-K160-03-7617

Data Field Description

is unsuccessful and no AMA tickets for unsuccessful calls are generated, an FAU ticket is generated without connection data. This means e.g. that package 168 (Called Party Number) is not present, conform the table in chapter 4.1. The flag F14 (Connection) in the Fixed Part of the AMA ticket is also not set. This ticket is purely meant for the registration of the Facility Usage Call Transfer for the leg B C. It is generated independent from the separate FAU ticket for usage of Call Transfer. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = THRDPRTY; D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. [Link] Package 147: Tariff Info A) Syntax description This package is composed out of a Fixed Part, followed by one or more optional subpackages. The presence of the subpackages is indicated by validity indicators. The subpackages themselves also have a variable structure with a Fixed Part and one or more subpackages. In the subpackages, the field numbers and byte positions are indicated with a +, indicating that this field number and byte position are relative. 0. Fixed Part:
Field No 1 2 3 4 5 Byte Pos 1 2 3 4 5
Length

(bytes) 1 1 1 1 n

Field Name 7 6 5 3 2 4 Package Number Package Length Control & Validity Indicators Currency Tariff Info Subpackages

Remarks 1 0 binary; fixed value 147 (H93) binary; total length of package flags binary refer to description

Description of Field No 3:
Control & Validity Indicators Bit 0 1 2 3 4 5 6 7 Value 0 1 0 1 Meaning Current Tariff not present Current Tariff present Next Tariff not present Next Tariff present Reserved Reserved Reserved Do not restart charging Restart charging Tariffs only for display and supervision Tariffs for charging Pulse Format Currency Format

0 1 0 1 0 1

P30308-X2058-K160-03-7617

Data Field Description

Bits 0 and 1 are validity indicators: they indicate whether the optional subpackages for Current Tariff and Next Tariff are present or not. Remark that the subpackages in the ticket appear in the same order as the validity indicators (the order of the validity indicators is according to their bit position). Example: when bit 0 (Current Tariff) and bit 1 (Next Tariff) are set, first the Current Tariff subpackage will appear in the ticket, followed by the Next Tariff subpackage. There are two layouts for the Current Tariff subpackage and the Next Tariff subpackage: a layout for tariff information in pulse format, and a layout for tariff information in currency format. Which layout is taken is indicated by bit 7. Remark that when the Current Tariff and Next Tariff subpackage are present, they are both in pulse format or both in currency format; a mixture is not allowed. Bit 5 indicates whether a new current tariff must be started immediately (i.e. unconditionally) or whether it should be treated as a normal tariff switch for the current time. Bit 6 indicates whether the tariff is to be used for charging or only for display. The latter is e.g. the case, when the charges are registered in a transit exchange, and the tariff information in the originating exchange must only be used for Advice of Charge. Description of Field No 4: Currency
No Indication Australian Dollar Austrian Schilling Belgian Franc British Pound Czech Krona Danish Krone Dutch Guilder Euro Finnish Markka French Franc German Mark Greek Drachma (0-00) (1-01) (2-02) (3-03) (4-04) (5-05) (6-06) (7-07) (8-08) (9-09) (10-0A) (11-0B) (12-0C) (13-0D) (14-0E) (15-0F) (16-10) (17-11) (18-12) (19-13) (20-14) (21-15) (22-16) (23-17) (24-18) (25-19) (26-1A) (27-1B)

Hungarian Florint
Irish Punt Italian Lira Japanese Yen Luxembourgian Franc Norwegian Krone Polish Sloti Portugese Escudo Russian Roubel Slovak Krona Spanish Peseta Swedish Krona Swiss Franc Turkish Lira US Dollar

P30308-X2058-K160-03-7617

Data Field Description

1. Subpackage Current Tariff in Pulse Format

Field No +1 Byte Pos Field Name 6 5 3 2 1 0 (bytes) 7 4 Time (24 h) indicator when the next tariff was received 1 reserved Hours 1 reserved Minutes 1 reserved Seconds 1 Acknowledgement status 6 Originator identification 1 Tariff Control & Validity Indicators
Length

Remarks

+2 +3 +4

+1 +2 +3 +4 +5 +11

binary; value 0-23 (H00-H17) binary; value 0-59 (H00-H3B) binary; value 0-59 (H00-H3B) binary; refer to description binary; refer to description binary; refer to description

Description of Field No +2:

Acknowledgment status Value 0 1 2 3 4 5-255 Meaning Waiting for acknowledgment Positively acknowledged Negatively acknowledged Received but not sent In transit exchange receved and relayed transparently Reserved

Bit 0 indicates that the tariff has been sent, but the receiver did not yet sent the acknowledgement. Bit 1 resp 2 indicates that the sent tariff has been positively resp negatively aknowledged by the receiver. Bit 3 indicates that the Charge Generation / Registration Point positively received the tariff and did not sent the tariff backwards because the receiving point is the Originating Line Exchange or an Interworking point where in backwards direction the signalling does not support the sending of the ISUP charging messages. Bit 4 indicates the tariff has been received by a transit exchange that relays the ISUP messages transparently (without checking the tariff). This bit is relevant only if in this exchange the tariff is registered only for the interadministrative charging IACAMA. Description of Field No +3:Originator ID
Field No 1 2 3 Byte Pos 1 2 4
Length

(bits) 10 14 24

Field Name 7 6 5 3 2 4 National regulation authority Network ID Node Id

Remarks 1 0 Binary; range 0:1023 binary; range 0:16383 Binary; range 0: 16777215

100

P30308-X2058-K160-03-7617

Data Field Description

Description of Field No +4:

Tariff Control & Validity Indicators Bit 0 1 2 3 4 5 6 7 Value 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 Meaning Call Attempt Charges not present Call Attempt Charges present Call Setup Charges not present Call Setup Charges present Communication Charge #1 not present Communication Charge #1 present Communication Charge #2 not present Communication Charge #2 present Communication Charge #3 not present Communication Charge #3 present Communication Charge #4 not present Communication Charge #4 present No One time charge One time charge Cyclic communication charge sequence Non-cyclic sequence

This is a Boolean value at the (currency) tariff level package that indicates whether the currency tariff contains a minimum communication charge (i.e. whether the first sub-tariff is periodic or specifies a one-time charge) 1.1.
Field No +1

Subpackage Call Attempt Charges of Subpackage Current Tariff

Byte Pos +1 Field Name 6 5 3 2 (bytes) 7 4 1 Call Attempt Charge Pulses
Length

Remarks 1 0 binary

1.2.
Field No +1

Subpackage Call Setup Charges of Subpackage Current Tariff

Byte Pos +1 Length Field Name 3 2 6 5 (bytes) 7 4 1 Call Setup Charge Pulses Remarks 1 0 binary

1.3.
Field No +1 +2 +3

Subpackage Communication Charge #1 of Subpackage Current Tariff

Byte Pos +1 +2 +4 Length (bytes) 1 2 2 Field Name 7 6 5 3 2 4 Pulse Units Charge Unit Time Interval Count Duration Remarks 1 0 binary refer to description refer to description

Charge Unit Time Interval: Binary coded with a range from 0 to 35997. It begins with 200 milliseconds and continues with steps of 50 milliseconds.

P30308-X2058-K160-03-7617

101

Data Field Description

Examples:
Charge Unit Time Interval 0 1 2 ... 35997 Meaning no periodic metering 200 msec 250 msec 30 minutes

Count Duration: Indicates for how long the communication charge component is valid. Examples:
Count Duration 0 1 2 ... 3600 Meaning Unlimited 1 second 2 seconds 1 hour

1.4.

Subpackage Communication Charge #2 of Subpackage Current Tariff

This subpackage has the same structure as the previous one (Communication Charge #1). The presence of this subpackage is only possible when the subpackage for Communication Charge #1 is present. 1.5. Subpackage Communication Charge #3 of Subpackage Current Tariff

This subpackage has the same structure as the subpackage for Communication Charge #1. The presence of this subpackage is only possible when the subpackages for Communication Charge #1, Communication Charge #2 and Communication Charge #3 are present. 2. Subpackage Next Tariff in Pulse Format
Byte Pos Field Name 6 5 3 2 1 0 (bytes) 7 4 Time (24 h) indicator when the next tariff was received 1 reserved Hours 1 reserved Minutes 1 reserved Seconds 1 Acknowledgement status 6 Originator identification 1 Switch over time 1 Tariff Control & Validity Indicators
Length

Field No +1

Remarks

+2 +3 +4 +5

+1 +2 +3 +4 +5 +11 +12

binary; value 0-23 (H00-H17) binary; value 0-59 (H00-H3B) binary; value 0-59 (H00-H3B) refer to description above binary; refer to description binary; refer to description refer to description above

102

P30308-X2058-K160-03-7617

Data Field Description

Description of Field No +1, +2, +3 and +5: The fields hours, minutes, seconds, Acknowledgement status, Originator Identification and Tariff Control & Validity Indicators have the same structure and meaning as for the Current Tariff in Pulse Format. Description of Field No +4: This time is the Greenwich Mean Time (GMT) at which the next tariff has to become active. It is represented in steps of 15 minutes. The coding is the following:
Switch over time Value 0 1 2 3 4 . 96 97 - 255 Meaning Spare 0 hour 15 minutes 0 hour 30 minutes 0 hour 45 minutes 1 hour 0 minutes 24 hour 0 minutes Spare

The same subpackages (Call Attempt, Call Setup, Communication Charges, ...) can be present as in the case of Current Tariff. 3. Subpackage Current Tariff in Currency Format

The package has the same structure as the package for the Current Tariff in Pulse Format; only the subpackages for Call Attempt, Call Setup and Communication Charges are different. 3.1.
Field No +1 +2

Subpackage Call Attempt and Call Setup Charges

Byte Pos +1 +2 Field Name 6 5 (bytes) 7 1 Scale 3 Factor
Length

Remarks

0 ref. description ref. description

Description of Field No +1: Scale The actual value of the currency Scale is given by 10x, where x is the value stored in the package. Remark that the negative values (-7 till -1) are coded in one byte as a complement of 256. Examples:
Scale Scale -7 -6 -5 -4 -3 -2 -1 0 1 2 3 Value 249 250 251 252 253 254 255 0 1 2 3 Meaning 0.0000001 0.000001 0.00001 0.0001 0.001 0.01 0.1 1 10 100 1000

P30308-X2058-K160-03-7617

103

Data Field Description

Description of Field No +2: Factor Integer between 0 and 999999; 0 indicates no charge. 3.2.
Field No +1 +2 +3

Subpackage Communication Charges

Byte Pos +1 +2 +5
Length

(bytes) 1 3 2

Field Name 7 6 5 4 Scale Factor Count Duration

Remarks 3 2 1 0 integer between -7 and 3 ref. above binary

Subpackage Next Tariff in Currency Format

The package has the same structure as the package for the Next Tariff in Pulse Format; only the subpackages for Call Attempt, Call Setup and Communication Charges are different. See previous package. B) Functional description This package contains the tariff information as received from a higher exchange (an exchange in the call path from the actual exchange up to the destination), or as sent to the lower exchange (an exchange in the call path from the actual exchange down to the origin). Tariff information can be expressed in pulse or in currency format. A Tariff Info in pulse format indicates a number of pulses and a time interval after which those pulses have to be counted. Example: 1 pulse each 10 seconds. The time interval can be omitted; in this case only a number of pulses have to be applied. A tariff info in currency format gives directly a price per second (except for Call Attempt and Call Setup Charges where it is a time independent price). The price is expressed as a scale and a factor. Example: a price of 0.003 is expressed with a factor of 3 and a scale of -3. One Tariff can have following components: Call Attempt charges These charges apply only for unsuccessful calls and as soon as a call attempt is detected. Call Attempt charges are not time dependent. In pulse format, they are expressed as a number of pulses without time interval, In currency format, they are expressed with a scale and factor, but the price is in this case time independent. Call Setup charges These charges apply only for successful calls at the moment the Answer signal is received. Call Setup charges are not time dependent. In pulse format, they are expressed as a number of pulses without time interval, In currency format, they are expressed with a scale and factor, but the price is in this case time independent. 1 to 4 Communication Charges These charges apply during conversation, i.e. after Answer. For each Communication Charge, a duration can be specified, which indicates how long one Communication Charge has to be applied. Example: the first 10 minutes after Answer, a tariff of 1 pulse per 10 seconds has to be applied; after these 10 minutes, a tariff of 1 pulse per 20 seconds has to be applied. In this case, two Communication Charges are defined (pulse format is assumed): one with a Count Duration of 600 seconds, Pulse Units = 1 and Charge Unit Time Interval = 197 (steps of 50 milliseconds)

104

P30308-X2058-K160-03-7617

Data Field Description

a second one with a Count Duration of 0 (unlimited), Pulse Units = 1 and Charge unit Time Interval = 397 (steps of 50 milliseconds) In the exchange, an active and a passive tariff are maintained. The active tariff is the one, which is currently being applied for the call. The passive tariff is the one which will become active at a future point of time (e.g. at 6.00 p.m.). The presence of the passive tariff allows an immediate switch over (switch from active to passive tariff) during the call. The Tariff Info package can contain a Current and/or a Next Tariff. When received before Answer, the Current Tariff is the one, which will become active at the moment Answer is received; the Next Tariff will be kept in the exchange as the passive one. The Next Tariff contains always the absolute Switch Over Time, i.e. the time at which the Next Tariff has to become active or has become active (see further for the latter case). When received during the call, the received Current Tariff will become immediately the active tariff. The presence of a Tariff Info package with Current and Next Tariff does not imply that at the moment the ticket is generated, the Current Tariff was the active one. Reason: at tariff switch over time, intermediate charging is not necessarily done (for intermediate charging, see further). This is possible because the switch over time is an absolute time indication. It is therefore very well possible, that the Next Tariff in the AMA ticket was the active one inside the exchange at the moment the ticket was generated. This is illustrated in Figure 25.

Figure 25: Receipt of Tariff info before Answer (call duration < intermediate timer) For intermediate charging at receipt of Tariff Information and at tariff switch over time, following algorithm applies: Intermediate charging is done when old tariff information, which is not yet registered in tickets, is overwritten with new information. This is illustrated in following figures:

P30308-X2058-K160-03-7617

105

Data Field Description

106

P30308-X2058-K160-03-7617

Data Field Description

Figure 26: Examples of intermediate Charging in case Tariff Info is received The Acknowledgement Status has the following meaning: Waiting for Acknowledgement This value is only relevant for CAMA, not for LAMA tickets. It indicates that the CAMA exchange has sent the tariff to the originating exchange only for the purpose of Advice of Charge, and that the call was released before the acknowledgement was received. Remark that during the waiting time for an acknowledgement, package 147 is not registered in the ticket. Positively acknowledged This value indicates that the Tariff Info is positively acknowledged by the receiving exchange. It is relevant for Tariff Info that was sent to a lower exchange, and also for Tariff Info, which is received. Remark that received Tariff Info is only registered in tickets when this information is positively acknowledged. Negatively acknowledged This value is only relevant for tickets with Tariff Info that was sent to a lower exchange. Remark that received Tariff Info is only registered in tickets when this information is positively acknowledged. Received but not sent This value is only relevant for CAMA tickets in a transit exchange. It indicates that tariff information was received from the destination side and positively acknowledged, but a relay to the lower exchanges was not possible because of signalling restrictions, or because the incoming trunk group did not have the authorization for sending tariff information (missing parameter SENDTAR in the CR TGRP command). Remarks: Call Attempt and Call Setup Charges in Tariff Information received after answer are ignored. The package can be present together with the flag no charge. The flag no charge has the priority.

P30308-X2058-K160-03-7617

107

Data Field Description

C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = CALLTAR; The parameter GCOS = SENDTAR in the CR TGRP command gives the incoming ISUP trunk group the authorization to send the tariff information to a lower exchange. The parameter GCOS = CURRTAR (only possible in combination with GCOS=SENDTAR) in the CR TGRP command indicates that the Tariffs are in currency format. When the parameter is not entered, the tariffs are in pulse format. The parameter TKZOINF = YES in the CR ZOPT command gives the authorization to receive Tariff Information during the call. D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. [Link] Package 148: CAC New Destination A) Syntax description
Field No 1 2 3 4 Byte Pos 1 2 3 4
Length

(bytes) 1 1 1 n

Field Name 7 6 5 4 Package Number Package Length Reserved Digit (i)

Remarks 3 2 1 0 binary; fixed value 148 (H94) binary; total length of package binary; range 0 7 Total length of CAC packed digits, value (0:HF), including prefix digits

Val Number of

Digits
Digit (i+1)

Digit (i): I is incremented every next byte as follows: i=1,3,....,2n-1

Description of Field No 3 (Val):

Validation Value 0 1 Meaning CAC New Destination is not used to reach the destination CAC New Destination is used to reach the destination

B) Functional description This package contains the Carrier Access Code, which is returned from the SCP as part of the destination digits in case of an IN-call. The validation bit indicates whether the CAC received from the SCP is really used for further routing or not. It is e.g. possible that CAC digits are received from the SCP, but that no CAC digits are necessary to reach the destination (no command CR CACCPT is entered for the destination digits received from the SCP). In this case, the validation bit will not be set. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = CAC and ENTR CDTDAT: EXTNSD = NEWDEST.

108

P30308-X2058-K160-03-7617

Data Field Description

Remark that EXTNSD = CAC is already set by default, so normally the 2nd command will be sufficient. D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. The presence of this package does not guarantee that the call is routed to the network operator, indicated by the Carrier Access Code. [Link] Package 149: Global Call Reference A) Syntax description
Field No 1 2 3 Byte Pos 1 2 3
Length

(bytes) 1 1 1

Field Name 7 6 5 4 Package Number Package Length reserved

Remarks 3 2 1 0 binary; fixed value 149 (H95) binary; total length of package F1 = 1: Global Call Ref received (via ISUP) F1 = 0: Global Call Ref generated in own exchange binary; refer to description

Global Call Reference

B) Functional description The Global Call Reference (GCR) is meant to be a unique identification for all kinds of tickets generated in the own and in different exchanges for the same call. A GCR should be generated in the originating exchange, and passed on to all following exchanges via ISUP, such that it can be provided in all tickets generated on the call path. The transport of the GCR via ISUP has been standardized by ITU-T and by ETSI (DEN 300 356-1 V4). When activated by the craftsperson, the GCR is handled in the following way: in the exchange which receives a GCR via ISUP, the charging tickets will collect this GCR in the tickets and the Flag F1 set on 1. The GCR will also be sent via ISUP to the next exchange. A GCR of max. 20 bytes can be received. in the originating exchange, or in the transit exchange when no GCR has been received, the GCR will be built according to ITU-T and ETSI in the following way:
Global Call Reference Byte position in package 4 5 8 9 12 13 Length 1 3 1 3 1 4 Meaning Network Id Length Network Id Node Id length Node Id Call Reference length Call Reference

Table 19: Layout of GCR In this case, the flag F1 will be set on 0, indicating that the GCR has been generated in the own exchange.

P30308-X2058-K160-03-7617

109

Data Field Description

The Network Id is provided in the same way as the Originator Id in package 147: Description of Network Id
Field No 1 2 Byte Pos 1 2
Length

(bits) 10 14

Field Name 7 6 5 3 2 4 National regulation authority Network ID

Remarks 1 0 Binary; range 0:1023 binary; range 0:16383

The Node Id is a 3 byte value, which is provided with the SPC of the own switch. The Call Reference is the provided in the same way as the Connection Id in package 110 (Connection Identification Number). Remarks: When in a transit exchange a GCR has been received, but the craftsperson has not activated the registration of the GCR in the AMA tickets, this received GCR will be transported to the next exchange (assuming ISUP adaptations for GCR transport). When in a transit exchange, no GCR has been received, the GCR generated in the own exchange will be sent to the next exchange (assuming ISUP adaptations). For Call Forwarding, Three Party, Large Conference and Call Transfer, the same remarks are valid as for the package 110 (Connection Identification). The Global Call Reference can be provided by the SCP (Service Control Point) in case the SCP initiates a call by sending an InitialCallAttempt operation. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = GCR; When activated, it replaces the package 110 (Connection Identification). D) Postprocessing remarks This package and package 110 (Connection Identification) are never available at the same time. In FAU tickets, neither this nor package 110 (Connection Identification) are present when the Functional Protocol is used to request, interrogate, or cancel the CCBS and CCNR feature In SCI tickets, neither this nor package 110 (Connection Identification) are present when the Functional Protocol is used. Also in ISCI tickets, neither this nor package 110 (Connection Identification) are present. The total package length (in bytes) is located at the second byte of the package. A maximum package length of 23 bytes is possible (a GCR received over ISUP can have a max. length of 20 bytes).

110

P30308-X2058-K160-03-7617

Data Field Description

[Link] Package 150: Audit Trail A) Syntax description

Field No 1 2 3 4 5 Byte Pos 1 2 3 7 8
Length

(bytes) 1 1 4 1 1

Field Name 3 7 6 5 4 Package Number Package Length Sequence Number Checksum Value 1 Checksum Value 2

Remarks 2 1 0 binary; fixed value 150 (H96) binary; fixed value 08 (H08) binary binary binary

B) Functional description This package is gathered (when activated) to detect loss or corruption of tickets during transfer and Postprocessing. The package contains two different kinds of information: a Sequence Number and a Checksum. They can be activated separately by the craftsperson. Sequence Number The Sequence Number is a 4-byte running counter, which is incremented by one, each time a ticket is buffered (tickets are buffered in main memory before they are written to disk). That means, the Sequence Number reflects the order in which tickets are buffered and at the same time, the order in which tickets are written into the AMA file on disk. The Sequence Number is only reset to zero, in case of recovery with initialization of transient data (this includes initial system start), and in case the Sequence Number rolls over from [Link] to 0. When the craftsperson has only activated the Checksum, this package will be present with Sequence Number equal 0. Remark however, that the Sequence Number is continuously incremented inside the exchange. Remarks: A Sequence Number is not provided in the system tickets (breakdown, overflow, date/time change), and is not incremented when a system ticket is generated. A roll-over of the Sequence Number is not reported The Sequence Number is not reset to zero, when the AMA feature is cancelled (MML command CAN IAFEAT) and activated again (ACT IAFEAT). That means, the Sequence Number can only be treated as a relative, not as an absolute number. The Sequence Number is written in the AMA ticket after the execution of an eventual immediate output to the OMT (AMAIO). The Sequence Number is written in the AMA ticket only when the feature (EXTNSD=SEQUENCE) is active at the time the ticket is generated (=buffered). Gaps in the Sequence Number of the tickets stored in the [Link] file or [Link](1/2) file(s) can appear when the feature (EXTNSD=SEQUENCE) is not always active and/or when a recovery with initialization of the transient data has occurred. When a change to another version is performed, the Sequence Number starts with the initial value zero. Checksum When activated by the craftsperson, the exchange will calculate a checksum over the AMA ticket, with the algorithm as described in /9/. The algorithm results in a 2-byte checksum, which is always located at the end of the ticket. The algorithm is such that the receiving side (the Postprocessing) has to execute following algorithm to control whether the bit integrity is kept:

P30308-X2058-K160-03-7617

111

Data Field Description

CHECKSUM_VALUE_1 = 0 CHECKSUM_VALUE_2 = 0 DO FOR i = 1 TO last byte of ticket CHECKSUM_VALUE_1 = (CHECKSUM_VALUE_1 + byte i of ticket) modulo 256 CHECKSUM_VALUE_2 = (CHECKSUM_VALUE_1 + CHECKSUM_VALUE_2) modulo 256 END DO FOR

Figure 27: Checksum algorithm The result should be that both CHECKSUM_VALUE_1 = 0 and CHECKSUM_VALUE_2 = 0. If not, at least one of the bits in the AMA ticket has been corrupted. When the craftsperson has only activated the Sequence Number, this package will be present with CHECKSUM_VALUE_1 and CHECKSUM_VALUE_2 equal 0. Remarks: A Checksum is not provided in the system tickets (breakdown, overflow, date/time change) The Checksum modulo 256 guarantees that each 1 bit corruption is detected. Bit corrections are not possible. For a complete description of the quality of this algorithm, refer to /9/. Important note: Because of the rather large number of calculations, the use of the Checksum has a considerable negative impact on the call throughput of the exchange. C) Operating remarks The inclusion of package 150 in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = SEQUENCE and/or ENTR CDTDAT: EXTNSD = CHECKSUM; D) Postprocessing remarks This package has a fixed length of 8 bytes. The length is included on byte 2 in the package. When present, this package is always the last package of the ticket The Sequence Number and Checksum can be activated separately. In order to permit the Postprocessing to quickly know whether the Sequence Number and/or Checksum are really present in the ticket, the flags F37 and F38 in the Fixed Part (Header) of the AMA ticket can be checked. When F37 and/or F38 is set, the Sequence Number and/or Checksum can quickly be located by using the Record Length which is always located at the second and third byte of the ticket. The Sequence Number is located at the end of the record - 5 bytes; the Checksum is located at the two last bytes of the record. The Checksum can be used to check whether the contents of the AMA ticket has not been corrupted between the moment of buffering in the exchange, and the moment of processing the tickets in the Postprocessing.

112

P30308-X2058-K160-03-7617

Data Field Description

[Link] Package 151: Business Group Identification A) Syntax description

Field No 1 2 3 Byte Pos 1 2 3
Length

(bytes) 1 1 3

Field Name 3 7 6 5 4 Package Number Package Length Business Group ID

Remarks 2 1 0 binary; fixed value 151 (H97) binary; fixed value 05 (H05) binary

B) Functional description The Business Group is an additional identification of the Centrex Group. It is possible to give Centrex Groups in different exchanges the same Business Group ID, which offers e.g. the possibility to group the bills for the different Centrex Groups according to this unique Business Group ID. Remarks: The Business Group ID is not available in CAMA tickets. When the tickets are generated on the terminating side, this package contains the Business Group Id of the B-party (available in package 172 (System Provided Number)). C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = BGID; The Business Group ID is administered via the command CR CXGRP: CXGRP = <Centrex Group ID>, COSDAT = BGID-<Business Group ID>; D) Postprocessing remarks This package has a fixed length of 5 bytes. This length is included on byte 2 in the package. [Link] Package 152: Centrex Numbers A) Syntax description
Field No 1 2 3 4 5 x x+1 Byte Pos 1 2 3 4 5 ...
Length

(bytes) 1 1 1 1 n

Field Name 7 6 5 4 Package Number Package Length reserved Number of Digits Digit (i) ...

Remarks 3 2 1 0 binary; fixed value 152 (H98) binary; total length of package binary; flags; refer to description binary; range (0:15) packed digits; refer to description

Digit (i + 1)

Digit (i): I is incremented every next byte as follows: i=1,3,....,2n-1

P30308-X2058-K160-03-7617

113

Data Field Description

Description of Field No 3:
Flags Flag F0 F1 F2 F3 Value 1 0 1 0 1 0 1 0 Meaning Calling party intercom digits are stored no Calling party intercom digits are stored Called party intercom digits are stored no Called party intercom digits are stored Redirecting party intercom digits are stored no Redirecting party intercom digits are stored Access Code is stored no Access Code is stored

Remark: Fields 4 and 5 are repeated if more than one number is available. Description of Field No 5: Digits This field contains the Calling party intercom digits, the Redirecting party intercom digits, the Called party intercom digits and/or the Access Code digits. The Redirecting party intercom digits are only available in case of Call Forwarding or a CTX Dial IN call. In this case, no Calling party intercom digits are present. The Access Code digits are stored, when an Access Code has been used by the calling party. The numbers are stored in the same order as the validity bits. The lower digit is stored in the upper nibble of a byte. In case of an odd number of digits, the last nibble is a spare one to complete the full byte. B) Functional description This package contains the Centrex intercom numbers for the calling line, the redirecting party (in case of Call Forwarding or CTX Dial IN), and/or for the called line. It can also contain the access code that has been used by the calling party. The intercom digits are the short numbers that are only valid inside one Centrex Group. Remarks: Only the normal feature access codes (e.g. Public Network Access Code, Location Dialling Access Code) are written in the package; the custom calling feature access codes (e.g. Account Code) are not provided. In case of Group Dialling, the Called party intercom digits are only provided, in case both A and B-party belong to the same Business Group. The Group Dialling feature facilitates the administration when intercom dialling is required between subscribers residing in different exchanges. Remark that the Group Dialling Access Code is not part of the Called Party Intercom number.

114

P30308-X2058-K160-03-7617

Data Field Description

AMA-Ticket : In case Centrex Group 10 and 20 belong to the same Business Group Package 152 : Calling Party Intercom: 249 Called Party Intercom : 340 In case Centrex Group 10 and 20 do not belong to the same Business Group Package 152 : Calling Party Intercom: 249 Called Party Intercom : -

Centrex Group 10

Mapping of Group Dialling Acces Code 88 to Centrex public number 08997531

switch switch

Centrex Group 20 with public number 08997531

A-subscriber with intercom number = 249 dials 88 340

Admin : In originating exchange : CR CXCPT:CXGRP=10, CXCODE=88, TRATYP=GRPDIAL, NEWCODE=08997531,COLDIG=3; In terminating exchange : CR CXGRP:CXGRP=20, DNDAT=089-97531;

Subscriber with intercom number = 340

Figure 28: Intercom Numbers in case of Group Dialling In case of Location Dialling, the Called party intercom digits are only provided, in case both A and B-party belong to the same Business Group and the Location Access Code is marked as internal. With the Location Dialling feature, a simple access code can be dialled to reach members of a PBX which belongs to a Centrex Group. Remark that the Location Dialling Access Code is not part of the Called Party Intercom number.

P30308-X2058-K160-03-7617

115

Data Field Description

AMA-Ticket : Package 152 : Calling Party Intercom: 249 Called Party Intercom : 450

Subscriber with intercom number = 249 dials 99 450

switch

Centrex Group 10 Subscriber with DDI number = 450

PBX

PBX with PDN = 089722

Admin : CR CXCPT:CXGRP=10, CXCODE=99, TRATYP=LOCDIAL, NEWCODE=089722-INT, COLDIG=3,

Figure 29: Intercom Numbers in case of Location Dialling In case of Abbreviated Dialling, package 152 contains the Called party intercom number, not the abbreviated number. In case of the "CTX Dial In" feature, the redirecting intercom number is filled up with the number 00 00 00 0 as "virtual" redirecting party intercom number. The dialled CTX group DN is registered in the package 170 (Redirecting Number ). The package is not available in a CAMA ticket. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = CTXNO; Group Dialling is administered in the following way: CR CXCPT: CXGRP = <Centrex Group Id>, CXCODE = <access code>, TRATYP = GRPDIAL, NEWCODE = <public number assigned to the Centrex Group>, COLDIG = <number of digits to be dialled after the access code>; Location Dialling, marked as internal call is administered in the following way: CR CXCPT: CXGRP = <Centrex Group Id>, CXCODE = <access code>, TRATYP = LOCDIAL, NEWCODE = <Pilot Directory Number>-INT, COLDIG = <number of digits to be dialled after the access code>; Location Dialling, marked as external call is administered in the following way: CR CXCPT: CXGRP = <Centrex Group Id>, CXCODE = <access code>, TRATYP = LOCDIAL, NEWCODE = <Pilot Directory Number>-EXT, COLDIG = <number of digits to be dialled after the access code>; A Business Group is assigned to a Centrex Group in the following way: CR CXGRP: CXGRP = <Centrex Group Id>, COSDAT = BGID-<digits>;

116

P30308-X2058-K160-03-7617

Data Field Description

D) Postprocessing remarks The package length is included on byte 2 in the package itself. [Link] Package 153: Received Called Party Number A) Syntax description
Field No 1 2 3 4 5 6 Byte Pos 1 2 3 4 5 6
Length

(bytes) 1 1 1 1 1 n

Field Name 3 2 1 7 6 5 4 Package Number Package Length res NADI res NPI reserved Number of Digits Number of

Remarks 0 binary; fixed value 153 (H99) binary; total length of package binary; refer to description binary; refer to description binary packed digits, values (0:HF)

CAC Digits
Digit (i) Digit (i + 1) Digit (i): i is incremented every next byte as follows: i=1,3,....,2n-1

Description of Field No 5:
Field Part Number of Digits Meaning Range between 0-31 Total length of Received Called Party Number, including CAC Digits Range between 0-7

Number of CAC Digits

P30308-X2058-K160-03-7617

117

Data Field Description

Functional description This package contains the digits as dialled by the subscriber, or sent by the subscriber terminal as dialled digits or as have been received via trunk. The digit string can start with CAC digits; in this case, the Number of CAC Digits will be different from zero. The package is provided in Connection and FAU tickets in following cases: when the Received Called Party Number differs from: the called party number, as stored in package 168 (Called Party Number) or in package 101 (Partner Directory Number) (when activated by the craftsperson) (in case of PSTN non-intercom calls). This happens in following cases: when a service code is dialled before the B-party Number. The package contains all dialled digits, including the dialled service code; package 168 (Called Party Number) or package 101 (Partner Directory Number) contain only the Bparty number. Example: when an Account Code is dialled, or when the access code for DEB Next Call is dialled before the B-party number. when the dialled digits are translated into a long number according to a Supplementary Service. In this case, the long number is provided by the exchange database. The package contains the dialled digits; package 168 (Called Party Number) or package 101 (Partner Directory Number) the long number. These cases are: when the A-subscriber uses abbreviated dialling when the A-subscriber uses Voice Mail Service when a Centrex subscriber dials an intercom number Remark: when the A-subscriber uses the hotline or the hotline delayed feature, the package is not provided, except for ISDN subscribers using the functional protocol, where the digits are contained in the D-channel Setup message. when a Carrier Access Code has been dialled before the actual B-party Number or when the Carrier Access Code has been signalled via trunk as part of the Called Party Number. The package contains the dialled or signalled digits, package 168 (Called Party Number) or package 101 (Partner Directory Number) contain only the B-party number. The Carrier Access Code is stripped off and provided in package 145 (Billing CAC). the called intercom number, as stored in package 152 (Centrex Numbers) (in case of an intercom call). when an intercom number is dialled, and the collection of package 152 (Centrex Numbers) is not required. In this case, this package contains the intercom number. The package is provided in SCI tickets in case the dialled digits differ from the package 118 (Digit String) needed for the Subscriber Controlled Input. Examples are the use of abbreviated dialling for the Subscriber Controlled Input, the dialling of the code for DEB Next Call in front of the digit string for SCI, the dialling of an Account code in front of the digit string for SCI, or Remote SCI without User Interactive Dialog. In the last case, the dialled digits differ from the digit string for the SCI, by the presence of the own Directory Number: all digits which are entered after dialling the Service Number for Remote SCI (this is the number which is used to access the Remote SCI service) are registered as dialled digits; the first number entered after the Service Number is the Directory Number for which the Remote SCI has to be done.

118

P30308-X2058-K160-03-7617

Data Field Description

Remarks: When the dialled digits contain a PIN (Personal Identification Number) or a keyword, this PIN or keyword is blended out by means of hexadecimal B digits. When e.g. the subscribers dials *22*1234*2525357# in order to activate Call Diversion with keyword 1234, this package will contain the string *22******2525357#. The package is not available in tickets generated on the B-side of the call or in case of FAU by the B-party. The package is not available in tickets generated for the second leg of a Call Forwarding, nor in the tickets generated for the recall after CCBS or CCNR. The Received Called Party Number is considered equal with the Called Party Number or the Digit String, when functionally the same DN is stored, independent of the way the DN is represented (i.e. in a format without national/international prefix digits or in a format with national/international prefix digits). B) Operating remarks The inclusion of the package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = CLDRCVD; C) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. [Link] Package 154: Additional Call Indicators A) Syntax description
Field No 1 2 3 4 5 6 7 Byte Pos 1 2 3 4 5 6 7
Length

(bytes) 1 1 1 1 1 1 1

Field Name 7 6 5 4 Package Number Package Length

F18 F28 F38 n.a. res. n.a. F27 F37 n.a. res. n.a. F26 n.a. n.a. F56 F15 F25 n.a. n.a. F55

Remarks 3 2 1 0 binary; fixed value 154 (H9A) binary; total length of package flags res. reserved for future applications n.a. not applicable, i.e. relevant for another kind of record, or project specific meaning

F14 F24 F34 F44 n.a.

n.a. F23 n.a. F43 n.a.

F12 F22 n.a. F42 n.a.

F11 F21 n.a. F41 n.a.

P30308-X2058-K160-03-7617

119

Data Field Description

Description of Field No 3:
Flags Flag F11 F12 F14 F15 F18 F21 F22 F23 F24 F25 F26 F27 F28 F34 F37 F38 F41 F42 F43 F44 F55 F56 Value 1 1 1 1 1 1 Meaning CTX subscriber CTX attendant International call Voice over internet Reverse charging Local intercom call Remote intercom call Intra charging site call Inter charging site call Public call Public business call Second leg of a Dial In call Call from authorized subscriber International transit call SCLS released call Subscriber under test MASET normal call MASET direct call Master to Slave CTX call Call via Master CTX group Call started during RSU SAS IP Dial In traffic Relevance of flags for Conn. SCI FAU 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 TFS -

1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Legend:

x: flag is relevant -: flag is not relevant

Table 20: Overview of the Flags in package 154 (Additional Call Indicators) B) Functional description These flags have the following meaning: F11 This flag indicates that the calling line is a Centrex subscriber. F12 This flag indicates that the calling line is a Centrex attendant. F14 This flag is set in following cases: the call comes in over an international trunk group (an international trunk group is administered by the parameter GCOS = INTLTRK in the CR TGRP command) the received MFC category indicates international (values 7, 8, 9, 10 of the Category) received calling party number is an international number (NADI = international) incoming international call in O:IAM (bit in Forward Call Indicator) The flag is only set in CAMA tickets. F15 This flag indicates that the call is set up via Internet. The flag can be set in the local, transit and end exchanges. F18
120 P30308-X2058-K160-03-7617

Data Field Description

This flag indicates that for this call reverse charging (according to ITU-T Q.736 and Q.956) applies. The flag can be set in the local, transit and end exchanges, and is present in the tickets on the A-side as well as on the B-side of the call. F21 This flag is only relevant for Centrex subscribers. It indicates that the call is a Local Intercom call, i.e. a call between two members of the same Centrex Group. F22 This flag is only relevant for Centrex subscribers. It indicates that the call is a Remote Intercom call, i.e. a call between two members of a different Centrex Group. F23 This flag is only relevant for Centrex subscribers. It indicates that the call is an Intra Charging Site call, i.e. a call between two Centrex subscribers whose Charging Site has the same number. A Charging Site is a subdivision of one Centrex Group (administered via COSDAT = CHSITE-<charging site> in the CR CXSUB and CXPBX commands). Remark that F23 can also be set when A- and B-party belong to a different Centrex group. F24 This flag is only relevant for Centrex subscribers. It indicates that the call is an Inter Charging Site call, i.e. a call between two members of a different Charging Site. Remark that all Centrex members have a Charging Site assigned (if not explicitly administered, the Charging Site = 1). That means, as soon as a call is made between two Centrex members, either Flag F23 or F24 is set. F25 This flag is only relevant for Centrex subscribers. It indicates that the call is a Public Call. A Public Call is detected by an own access code (administered with the command CXCPT). Remark that when F25 is set, none of the flags F21, F22, F23, F24, F26 can be set. F26 This flag is only relevant for Centrex subscribers. It indicates that the call is a Public Business Call. A Public Business Call is detected by an own access code (administered with the command CXCPT). Remark that this flag is independent of the destination, i.e. the destination can be a public or a Centrex subscriber. Remark that when F26 is set, none of the flags F21, F22, F23, F24 can be set. Moreover, either F25 or F26 is set; not both of them. F27 This flag indicates that the ticket is generated for the second leg of a so called "Centrex Dial In call". Centrex Dial In is a feature which enables subscribers to dial into a Centrex group via a so called Centrex Master Group DN and to use the complete Centrex dialling plan, which implies that remote intercom and public destinations can be reached. For charging purposes, such a call is split up into two legs, one leg from the calling subscriber to the Centrex Dial In point (to be charged for the calling line) and a second leg from the dial in point to destination. This second leg is charged to the Centrex Master Group by registering the dialled group DN in the package Redirecting Number, and indicating this package as record owner. If the Centrex Dial In call is used to reach a local member of the Centrex group, there is only one leg to be charged, namely from the calling line to the Centrex Dial In point. F28 Authorized Subscribers are subscribers of another network (other fixed or mobile network provider) which are authorized to act like the Centrex subscribers of a special Centrex group, and hence use the complete Centrex dialling plan. In order to reach the Centrex Group, the authorized subscribers have to dial the Centrex Dial In number (refer to the description of

P30308-X2058-K160-03-7617

121

Data Field Description

Flag F27). In the Centrex Group, a screening is performed to check whether the calling subscriber is an authorized subscriber or not. Remark that in this case, flag F27 is not set. The following figure illustrates the use of the flags for Centrex subscribers:
(6)
*1 0852 555

(7)

EXCHANGE 1 Centrex Group 1 Business Group 1

(1)
Chrg Site 1

*2 0852 555

EXCHANGE 2

Centrex Group 4 Business Group 1

(4)

(2)
Chrg Site 2 Chrg Site 1 (default Chrg Site)

(5)
Chrg Site 2

(3)

Chrg Site 3

Centrex Group 2 Business Group 1

Centrex Group 3 Business Group 3

From point of view of Centrex Group 1 1 : local intercom, intra charging site call 2 : local intercom, inter charging site call 3 : remote intercom, inter charging site call 4, 5 : remote intercom, intra charging site call : public call (on condition *1 has been administered as public network access code) : public business call (on condition *2 has been administered as public business access code)

Figure 30: Illustration of Additional Call Indicators F34 This flag indicates an international transit call. F37 This flag indicates that the call has been released because the Subscriber Credit Limit has been exceeded. F38 This flag indicates that the call has been setup by a V5.1 subscriber which has been set in the state "under test" (he can setup calls but calls terminated to his access are rejected).

122

P30308-X2058-K160-03-7617

Data Field Description

F41 This flag indicates that a normal call or a subscriber controlled input has originated from an access with the MASET (Manager Secretary and Team Service) feature. A MASET is a group of maximum 16 ISDN stations within one Centrex Group, with typical features. When e.g. a call is set up to one of the stations of the MASET, the other ISDN stations of the group will be notified of this by blinking lamps. Remark: this flag and flag F42 are mutually exclusive. F42 This flag indicates that a direct call has originated from an access with the MASET feature. A direct call is a call from a MASET terminal, whereby only the called party is notified (the lamps on the other MASET terminals will not blink). Remark: this flag and flag F41 are mutually exclusive. F43 This flag is used for the Centrex Master/Slave solution, to mark the connection from Master to Slave (the Slave is also denoted as Satellite Group). The Master/Slave solution has been introduced in order to offer Centex features area wide, in case exchanges of other manufacturers are not able to offer the feature set from the Siemens exchange. Therefore, the Siemens exchange acts as Master for such exchanges, which means that a call from a Centrex subscriber connected to such an exchange is first routed to the Master exchange. Also for reaching an subscriber of such a Slave exchange, a Master Group is passed. The flag F43 can be used by the Postprocessing to suppress the charging for the terminating leg (Master to Slave); in case the charging is done based on the ticket generated in Master A (the originating side). F43 can only be set together with F44. F44 This flag is used for the Centrex Master/Slave solution. It indicates that a call has been made via the Centrex Master Group or via a Centrex Sub Master Group. It is set for incoming (Slave to Master) calls as well as for outgoing (Master to Slave) calls. F44 is mutually exclusive with F27 and F28. F55 This flag indicates that call is started during RSU Standalone Service. When a subscriber is connected to a Remote Switching Unit (RSU) and the connection between the RSU and the central exchange breaks down, the call can be set up by the RSU, without participation of the Coordination Processor. The generated tickets for such a call are buffered in the RSU. When the connection between the RSU and the central exchange is restored, the buffered tickets are sent to the Coordination Processor, where they are stored on disk. This flag can only be present when the flag F27 in the Fixed Part is set. In case F27 in the Fixed Part is set and F55 is not set, the call has been started before the Standalone Service occurred.
A LTG
RTI HTI

Interface trunk

switch

LTG B

In case the Interface trunk between RTI and HTI breaks down, the RTI can set up a call between A or B, or can keep an existing call between A and B alive.

P30308-X2058-K160-03-7617

123

Data Field Description

Figure 31: Charging during RSU Standalone F56 This flag indicates that the call has been routed to an IP gateway. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = CALLIND; D) Postprocessing remarks The package has a fixed length of 6 bytes. The package length is included on byte 2 in the package itself. The not relevant flags can have a significant value. When the inclusion of this package is administered, the package will not be present, in case none of the relevant flags is set, even when some of the non relevant flags are set. [Link] Package 155: Add On Tariff A) Syntax description This package is composed out of a Fixed Part, followed by one or more optional subpackages. The presence of the subpackages is indicated by validity indicators. The subpackages themselves also have a variable structure with a Fixed Part and one or more subpackages. In the subpackages, the field numbers and byte positions are indicated with a +, indicating that this field number and byte position are relative. 0. Fixed Part:
Field No 1 2 3 4 5 Byte Pos 1 2 3 4 5
Length

(bytes) 1 1 1 1 n

Field Name 7 6 5 3 2 1 4 Package Number Package Length Control & Validity Indicators Currency Add On Tariff Info Subpackages

Remarks 0 binary; fixed value 155 (H9B) binary; total length of package binary; refer to description below binary refer to description

124

P30308-X2058-K160-03-7617

Data Field Description

Description of Field No 3:
Control & Validity Indicators Bit 0 1 2 3 4 5 6 7 Value Meaning 0 1 Received Add On Tariff not present Received Add On Tariff present reserved Reserved Reserved Reserved Reserved Tariff only for display and supervision Tariff for charging Pulse Format Currency Format

0 1 0 1

Bit 0 is a validity indicators: it indicate whether the optional subpackages for Received Add On Tariff is present or not. Remark that the subpackages in the ticket appear in the same order as the validity indicators (the order of the validity indicators is according to their bit position). There are 2 layouts for the Received Add On Tariff subpackage: a layout for tariff information in pulse format, and a layout for tariff information in currency format. Which layout is taken is indicated by bit 7. Bit 6 indicates whether the tariff is to be used for charging or only for display. The latter is e.g. the case, when the charges are registered in a transit exchange, and the tariff information in the originating exchange must only be used for Advice of Charge. Description of Field No 4: Currency
No Indication Australian Dollar Austrian Schilling Belgian Franc British Pound Czech Krona Danish Krone Dutch Guilder Euro Finnish Markka French Franc German Mark Greek Drachma (0-00) (1-01) (2-02) (3-03) (4-04) (5-05) (6-06) (7-07) (8-08) (9-09) (10-0A) (11-0B) (12-0C) (13-0D) (14-0E) (15-0F) (16-10) (17-11) (18-12) (19-13) (20-14) (21-15) (22-16) (23-17) (24-18) (25-19) (26-1A) (27-1B)

P30308-X2058-K160-03-7617

125

Data Field Description

1. Subpackage Received Add On Tariff in Pulse Format

Field No +1 Byte Pos Field Name 6 5 3 2 1 0 (bytes) 7 4 Time (24 h) Indicator when the Add On Tariff was received 1 reserved hours 1 reserved minutes 1 reserved seconds 1 Acknowledgement Status
Length

Remarks

+2 +3 +4

+1 +2 +3 +4 +5 +11

binary; value 0-23 (H00 - H17) binary; value 0-59 (H00 - H3B) binary; value 0-59 (H00 - H3B)

refer to description of field Acknowledgement Status

Binary; refer to description binary

6 2

Originator identification Received Add On Charge Pulses

Description of Field No +2:

Acknowledgement status Value 0 1 2 3 4 5-255 Meaning Waiting for acknowledgement Positively acknowledged Negatively acknowledged Received but not sent In transit exchange received and relayed transparently Reserved

Bit 0 indicates that the tariff has been sent, but the receiver did not yet sent the acknowledgement. Bit 1 resp 2 indicates that the sent tariff has been positively resp negatively acknowledged by the receiver. Bit 3 indicates that the Charge Generation / Registration Point positively received the tariff and did not sent the tariff backwards because the receiving point is the Originating Line Exchange or an Interworking point where in backwards direction the signalling does not support the sending of the ISUP charging messages. Bit 4 indicates the tariff has been received by a transit exchange, which relays the ISUP messages transparently (without checking the tariff). This bit is relevant only if in this exchange the tariff is registered only for the interadministrative charging IACAMA. Description of Field No +3:Originator ID
Field No 1 2 3 Byte Pos 1 2 4
Length

(bits) 10 14 24

Field Name 7 6 5 3 2 4 National regulation authority Network ID Node Id

Remarks 1 0 Binary; range 0:1023 binary; range 0:16383 Binary; range 0: 16777215

126

P30308-X2058-K160-03-7617

Data Field Description

2. Subpackage Received Add On Tariff in Currency Format

Field No +1 Byte Pos Length Field Name 6 5 3 2 1 0 (bytes) 7 4 Time (24 h) Indicator when the Add On Tariff was received 1 reserved hours 1 reserved minutes 1 reserved seconds 1 Acknowledgement Status 6 1 3 Originator identification Scale Factor Remarks

+2 +3 +4 +5

+1 +2 +3 +4 +5 +11 +12

binary; value 0-23 (H00 - H17) binary; value 0-59 (H00 - H3B) binary; value 0-59 (H00 - H3B)

refer to description of field Acknowledgement Status above

Binary; refer to description binary; indicating a scale between -7 and +3 binary; value 0-999999

The fields hours, minutes, seconds and Acknowledgement Status have the same structure and meaning as for the Received Add On Tariff in Pulse Format. Description of Field No +4: Scale The value of the currency scale is given by 10x, where x is the value stored in the package. Remark that the negative values (-7 till -1) are coded in one byte as a complement of 256. Examples:
Scale Scale -7 -6 -5 -4 -3 -2 -1 0 1 2 3 Value 249 250 251 252 253 254 255 0 1 2 3 Meaning 0.0000001 0.000001 0.00001 0.0001 0.001 0.01 0.1 1 10 100 1000

Description of Field No +5: Factor Integer between 0 and 999999; 0 indicates no charge. B) Functional description This package contains a one-time tariff applied for IN services, i.e. Add On Tariff Information can only be received in case of an IN call. Add On Tariff Information is generated in the SCP. The Add On Tariff Information can be expressed in pulse or in currency format. An Add On Tariff Information in pulse format indicates the number of pulses to be counted. In case of Add On Tariff in pulse format, the charge units are also presented in package 103 (Charge Units for Connection), on condition that this package has been activated by the craftsperson.

P30308-X2058-K160-03-7617

127

Data Field Description

An Add On Tariff Information in currency format gives directly a price for the used service. The price is expressed as a scale and a factor. Example: a price of 0.003 is expressed with a factor of 3 and a scale of -3. When an Add On Tariff is received during a call, this package is provided in the (next) first AMA ticket (first intermediate/intermediate/final ticket in case of long duration call or in the single ticket in case of short duration call) that is generated for this call. When during the same call, a second Add On Tariff is received, an intermediate AMA ticket is generated containing the first received Add On Tariff. This is illustrated in the following figures:
IACAMA-Ticket : Sequence : First Interm. package 155 : Rec. Add On Tariff = Tar1 IACAMA-Ticket : Sequence : Final package 155 not present

time

Answer Add On Tariff Tar1 received

Intermediate charging because of long duration

Release

Figure 32: Example of ADD ON Tariff during a call

IACAMA-Ticket : Sequence : First Interm. Package 155 : Recvd Add On Tariff = Tar1 IACAMA-Ticket : Sequence : Final Package 155 : Recvd Add On Tariff = Tar2

time

Answer Add On Tariff Tar1 received Add On Tariff Tar2 received

Release

Figure 33: Example of two ADD ON Tariffs during a call Remarks: Add On Tariff can only be received after Answer. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = ADDTAR;

128

P30308-X2058-K160-03-7617

Data Field Description

D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. [Link] Package 156: Advised Cumulated Charges A) Syntax description
Field No 1 2 3 4 5 Byte Pos 1 2 3 4 7
Length

(bytes) 1 1 1 3 1

Field Name 3 2 1 0 7 6 5 4 Package Number Package Length n.a. F7 Type of Control Flags Advise Advised Cumulated Currency Units or Pulses Advised Cumulated Charges Multiplier

Remarks binary; fixed value 156 (H9C) binary; fixed value 7 binary; refer to description n.a. not applicable binary binary; only relevant in case of currency (see Control Flags)

Description of Field No 3:
Flag Flag F7 Value Meaning 0 1 Currency Advice of Charge Counter has not overflowed during the call Currency Advice of Charge Counter has overflowed during the call

Type of Advice Value Meaning 0 1 2 3 No Advice Home Metering ISDN Advice Of Charge Verbal Announcement Next Call

Control Flags Flag 0 1 2 3 Value Meaning 0 1 0 1 0 1 FAU charges not included FAU charges included Connection charges not included Connection charges included Type of Units = meter pulses Type of Units = currency reserve

P30308-X2058-K160-03-7617

129

Data Field Description

Description of Field No 5:
Advised Cumulated Charges Multiplier Value Meaning 0 1 2 3 4 5 6 multiplication with 0.001 multiplication with 0.01 multiplication with 0.1 multiplication with 1 multiplication with 10 multiplication with 100 multiplication with 1000

B) Functional description This package contains the accumulated advised charges, i.e. the charges that are sent to the calling line as advice of charge information. The package is only built in case the Advice of Charge is required in currency format. Remarks: This package, when activated by the craftsperson, is only present in the last or single ticket of the call. The package is only built in case the Type of Units = currency. If during the call, the type of units or the multiplier for the units is changed by administration, the package is not built. If the Currency Advice of Charge Counter has overflowed during the call, the charges indicated in the package are not complete. This package is not present in SCI tickets, FAU tickets and TFS tickets. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = ADVCUMCH; D) Postprocessing remarks The package has a fixed length of 7 bytes. The package length is included on byte 2 in the package itself. [Link] Package 157: Outgoing PA Identification A) Syntax description
Field No 1 2 2 3 Byte Pos 1 2 3 4
Length

(bytes) 1 1 1 n

Field Name 7 6 5 3 2 1 4 Package Number Package Length LAC Length Number of Digits Digit (i) Digit (i + 1)

Remarks 0 binary; fixed value 157 (H9D) binary; total length of package binary packed digits, values (0:HF)

Digit (i): i is incremented every next byte as follows: i=1,3,....,2n-1

130

P30308-X2058-K160-03-7617

Data Field Description

Description of Field No 2:
Field Part Number of Digits LAC Length Meaning Range between 0-31 Total length of Outgoing PA identification, including LAC Range between 0-7

B) Functional description When activated by the craftsperson, this package is provided in A-side AMA tickets when the Bside of the call is a PBX that has been configured as a gateway PBX. It contains the Pilot Directory Number of this PBX, or the Operator Number of this PBX, in case OPN is required as additional number (EXTNSD = PBXOPN in ENTR CDTDAT). The Number of Digits includes the LAC digits. Remarks: In case the call originates on a gateway PBX, the incoming PBX identification is not provided explicitly, since this identification is present as Record Owner, stored in package 172 (System Provided Number), or as Record Owner DN in the fixed part of the AMA ticket when so requested by the craftsperson. The identification of the gateway PBX can not be taken from the package 168 (Called Party Number) (or from package 101 (Partner Directory Number), when Partner DN is requested by the craftsperson) for the following two reasons: The PBX Overflow feature permits the call to be routed to another PBX, in case the first PBX to which the call is offered is not able to accept the call. Package 168 (Called Party Number) contains only the number of the first PBX; the directory number of the second PBX to which the call is routed can be present in package 171 (Sent Called Party Number) when administered by the craftsperson. In a typical configuration, the Pilot Directory Number of the gateway PBX is not dialled by the calling party, and hence not contained in package 168 (Called Party Number) (subscribers can be prevented to dial the PDN of a gateway PBX, by adding hexadecimal digits to this PDN). The PDN will be put in front of the dialled digits by digit conversion (parameter CONVCODE in the CR DEST command) in the switch. With these converted digits, the call is routed to the gateway PBX. The parameter SSDI (Start Sending Digits) in the CR PBX command can be used to cut off the PDN in the called party digits, which are sent over the PBX to the other network. A special type of gateway PBX is the PA-Slave. A PA-Slave is typically used for the interconnection between two exchanges of different network operators via subscriber interface (refer to /10/ for more information).

P30308-X2058-K160-03-7617

131

Data Field Description

AMA-Ticket : Package 168 (Called Party Nr) : 892525357, NADI=national Package 157 : LAC LENGTH = 2 NO OF DIGITS = 5 DIGITS : 90A00 089 2525357 converted into A00 089 22525357 call is routed to PBX with DN = A00

border between two operators

A-subscriber dials 089 2525357

switch

called party number : 089 2525357 (SSDI = 4 cuts of the previously added A00)

switch

Subscriber with DN = 090 2449355

PA-Slave with LAC = 090 and PDN = A00;

Subscriber with DN = 089 2525357

Admin : ENTR CDTDAT : EXTNSD = RECTRID; CR DEST : CODE = 089, CONVCODE = +A00XXX; CR PBX:LAC=090, DN=A00, TYPE=PASLAVE, COS=GATEWAY&DDI, SSDI=4;

Figure 34: Example of the use of package 157 This package is neither present in SCI tickets, nor in FAU tickets. Being always national, the NADI is not registered. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = RECTRID; A PBX is marked as a gateway PBX with the command: MOD PBX: DN = <dn>, LAC = <lac>, COS = GATEWAY; The OPN is registered instead of the PDN in package 157, in case an OPN is present and the command ENTR CDTDAT: EXTNSD = PBXOPN; is entered. D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. When each interconnect PBX is administered as gateway PBX, the presence of this package can be used to distinct calls that are routed to another operator.

132

P30308-X2058-K160-03-7617

Data Field Description

[Link] Package 159: Additional Calling Party Number A) Syntax description

Field No 1 2 3 4 5 6 Byte Pos 1 2 3 4 5 6
Length

(bytes) 1 1 1 1 1 n

Field Name 3 2 1 0 7 6 5 4 Package Number Package Length res NADI res NPI [Link]. Screening reserved Number of Digits Digit (i) Digit (i + 1)

Remarks binary; fixed value 159 (H9F) binary; total length of package binary; refer to description binary; refer to description binary packed digits, values (0:HF)

Digit (i): i is incremented every next byte as follows: i=1,3,....,2n-1

Description of Field No 3:
NADI (Nature of Address Indicator) (according to /8/) Value Meaning 0 spare (NADI not received or could not be determined) 1 subscriber number 2 unknown 3 significant national number 4 international number 5-111 spare 112-126 reserved for national use 127 spare

Description of Field No 4:
NPI (Numbering Plan Indicator) (according to /8/) Value Meaning 0 spare 1 ISDN (telephony) numbering plan 2 spare 3 data numbering plan 4 telex numbering plan 5-6 reserved for national use 7 spare

Presentation Indicator (according to /8/) Value Meaning 0 presentation allowed 1 presentation restricted 2 address not available (national use) 3 spare

Screening Indicator (according to /8/) Value Meaning 0 reserved for user provided, not verified 1 user provided, verified and passed 2 reserved for user provided, verified and failed 3 network provided

P30308-X2058-K160-03-7617

133

Data Field Description

B) Functional description This package contains an additional DN identifying the calling party. The DN is signalled via ISUP to higher exchanges as a Generic Number (type additional calling party number). The Additional Calling Party Number contains mostly a not screened DN. When the Calling Party is a CTX subscriber, the Additional Calling Party contains the Calling Party Intercom Number (on condition that no public Additional Calling Party Number is already available). The Calling Party Intercom number is only present in the CAMA tickets in this package, when the signalling via ISUP of the Intercom DN has been requested by the craftsperson (MML-controlled). In case of calls setup from a Teleworker, package 159 contains: the company number + intercom number, in case of external calls accessed via public business access code (= business call) the intercom digits, in case of intercom calls (to other Centrex members) or in case of external calls accessed via the public access code (= private call). Teleworking is a feature based on Centrex. It gives a company member, working at home, the possibility to reach other company members via intercom dialling, and to receive calls via his intercom number at the company. The Teleworker may be physically connected to another exchange as the company. In case of IN calls and in case the SCP has provided a Calling Party Number, this number is stored in the package. Remarks: The package is not available in B-party FAU tickets. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = ADDCLGDN; The Calling Party Intercom number is signalled over ISUP if requested via command: CR CXGRP: CXGRP = <CTX group>, COS = DLVCXDN; D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package.

134

P30308-X2058-K160-03-7617

Data Field Description

[Link] Package 167: Additional Numbers A) Syntax description

Field No 1 2 3 4 5 6 7 8 x x+1 Byte Pos 1 2 3 4 5 6 7 8 ...
Length

(bytes) 1 1 1 1 1 1 1 n

Field Name 3 2 1 0 7 6 5 4 Package Number Package Length Number of Additional Number Strings Number Qualifier Number Type res NADI res NPI reserved reserved Number of Digits Digit (i) Digit (i + 1) ...

Remarks binary; fixed value 167 (HA7) binary; total length of package binary, refer to description binary; refer to description binary; refer to description binary; refer to description binary packed digits, values (0:HF)

Digit (i): i is incremented every next byte as follows: i=1,3,....,2n-1

Description of Field No 3: Number of Additional Number Strings This field indicates how many Additional Numbers the package contains. An Additional Number String is defined from Field 4 onwards, i.e. Field 4 and following bytes are repeated as many times as is indicated by number of additional number strings. Maximum 5 Additional Numbers can be stored in this package. Description of Field No 4:
Number Qualifier Value 0 1 2 3 4 5 6 7-15 Meaning Undefined Calling Party Redirecting Party Called Party SCI Served User Connected Party not applicable spare

Number Type Value 0 1 2 3 4 5 6-11 12-15 Meaning Undefined not applicable PBX Pilot DN not applicable PBX Operator DN Default MSN / Primary DN not applicable Spare

Values, which are marked as not applicable are not relevant for this package, or have a project specific meaning.

P30308-X2058-K160-03-7617

135

Data Field Description

Description of Field No 5:
NADI (Nature of Address Indicator) (according to /8/) Value 0 1 2 3 4 5-111 112-126 127 Meaning spare (NADI not received or could not be determined) subscriber number unknown significant national number international number spare reserved for national use spare

B) Functional description This package contains either the PBX Operator DN in case of PBX subscribers, on condition a PBX Operator DN is present, and the craftsperson has requested the inclusion of the PBX Operator DN in the AMA tickets. the Default MSN, on condition the craftsperson has requested the inclusion of the Default MSN in the AMA tickets, and: for ISDN subscribers with the feature Multiple Subscriber Number, a default MSN has been administered for analog subscribers with enhanced ringing, a primary DN has been administered the SHG PDN in case of SHG members (in this case, Number Type = PBX Pilot DN is used) on condition AMASHG is not set. Remark that the craftsperson has no possibility to request the inclusion of the SHG PDN in the package 167. Remarks: The PBX Operator DN and the Default MSN are stored as a national significant number (i.e. the NADI is always set to significant national number). The PBX Operator DN and the Default MSN are only available in the LAMA tickets (i.e. they are not available in the CAMA tickets). The assignment of a default MSN to an ISDN access with Multiple Subscriber DN is not obligatory. When no default MSN has been defined, this package is not available.

136

P30308-X2058-K160-03-7617

Data Field Description

C) Operating remarks The inclusion of this package in the AMA ticket is controlled via MML command ENTR CDTDAT: EXTNSD = PBXOPN; (for PBX) ENTR CDTDAT: EXTNSD = DEFMSN; (for ISDN MSN or analog subscriber with Secondary DN) The operator number is administered via the parameter OPN in the command CR PBX. The operator number is composed out of the PDN + further digits. In case of ISDN MSN the Default MSN is administered via the parameter DEFDN in the command MOD SLNACC or via the parameter COS=MSNDEFDN in the command CR SUB. In case of analog subscriber, a subscriber number is considered to be the default MSN when the parameter COS = PRIMDN is set for this number in the CR SUB command. The default MSN is provided automatically to the first MSN, in case the default MSN is set mandatory via MML command MOD CALLPOPT: MDMSN = MANDAT; Apart from the Additional Numbers that can be administered by the craftsperson, project specific Additional Numbers can be contained in this package. The package is then provided when a project specific Additional Number is available.

D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. [Link] Package 168: Called Party Number A) Syntax description
Field No 1 2 3 4 5 6 Byte Pos 1 2 3 4 5 6
Length

(bytes) 1 1 1 1 1 n

Field Name 7 6 5 3 2 1 4 Package Number Package Length res NADI res NPI reserved LAC Length Number of Digits Digit (i) Digit (i + 1)

Remarks 0 binary; fixed value 168 (HA8) binary; total length of package binary; refer to description binary; refer to description binary packed digits, values (0:HF)

Digit (i): i is incremented every next byte as follows: i=1,3,....,2n-1

P30308-X2058-K160-03-7617

137

Data Field Description

Description of Field No 5:
Field Part Number of Digits LAC Length Meaning Range between 0-31 Total length of Called Party Number, including LAC Range between 0-7

B) Functional description The presence of this package is not administrable. When the ticket is generated on the originating side of the call (in case of LAMA), this package contains the called party directory number, with which the call to the called party is set up. This number is equal to the digits dialled by the subscriber, or sent by the subscriber terminal as dialled digits, with following exceptions: when a service code is dialled before the B-party Number The package contains only the B-party number, not the service code. Examples: when an Account Code is dialled, or when the access code for DEB Next Call is dialled before the B-party number. when the dialled digits are translated into a long number according to a Supplementary Service. In this case, the long number is provided by the exchange database. Package 168 contains the long number. These cases are: when the A-subscriber uses abbreviated dialling when the A-subscriber uses Voice Mail Service (VMS) when the A-subscriber uses the hotline or the hotline delayed feature when a Centrex subscriber dials an intercom number or a CTX access code when a Carrier Access Code has been dialled before the actual B-party number. The Carrier Access Code is stripped off and provided in package 145 (Billing CAC). Refer also to the description of package 153 (Received Called Party Number). When the ticket is generated on the terminating side of the call, e.g. in case of B-party FAU, the package is not present. Instead, the DN of the B-party is stored in package 172 (System Provided Number). There is one exception: in case of Wake Up calls, the DN of the subscriber to be woken up is stored in the FAU AMA ticket in the package as Called Party Number. In case of CAMA tickets, this package contains the digits as they have been received over the trunk as called party digits (in case of ISUP trunks, the called party digits are contained in the IAM message), except when the digits contain a Carrier Access Code. This Carrier Access Code is stripped off, and provided in package 145 (Billing CAC).

138

P30308-X2058-K160-03-7617

Data Field Description

Remark that in case of IN calls, and in case of Number Portability, the received called party digits depend on the location of the switch, where the CAMA ticket is generated. In case the switch is located behind the number translation point, the called party digits contain the translated digits. In case the ticket is generated in the number translation point, or in a preceding switch, package 168 (Called Part Number) contains the digits before number translation. Remarks: The national or international prefix digits (e.g. 0 or 00) are never present in the package. The LAC Length is only provided when the DN of the Called Party is part of the DN volume of the switch where the AMA ticket is generated and when the Called Party is a national significant number. When the LAC Length is not available, the length is set to zero. In A-side FAU tickets, the package is not available. In case the Called Party Number is not equal to the dialled digits or the digits received over trunk, the received/dialled digits are included in the AMA ticket in package 153 (Received Called Party Number), on condition the generation of this package is triggered with ENTR CDTDAT. In case of an IN call, package 168 (Called Party Number) contains the IN service number, i.e. the number with which the IN service is accessed. The directory number of the physical B-party is collected in package 128 (New Destination). The digits contained in this package are not necessarily equal to the digits sent out over a trunk to the next exchange. Inside the exchange, the dialled/received digits can be converted to other digits. The digits used to determine the outgoing trunk in the own switch can again be modified before they are sent out as called line digits over this trunk to the next exchange. In case the Called Party Number is not equal to the digits sent out over a trunk to the next exchange, the sent out digits are included in the AMA ticket in package 171 (Sent Called Party Number), on condition the generation of this package is triggered with ENTR CDTDAT. C) Operating remarks Conversion of the dialled digits to other digits is done via the parameters NEWCODE or CONVCODE in the command CR DEST. With these converted digits, the routing (the exchange process to find a destination based on the digit information) is performed again. CR DEST: DEST = <destination>, CONVCODE = <converted digits>; CR DEST: DEST = <destination>, NEWCODE = <converted digits>; Modification of the digits before they are sent out over a trunk as called line digits is done with the parameters DICON and SSDI in the MML command CR ROUTE: ROUTE = <route>, DEST = <destination>, TGNO = <trunk group name>, DICON = <digit converting code>, SSDI = <starting position for sending out dialled digits>; D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package.

P30308-X2058-K160-03-7617

139

Data Field Description

[Link] Package 170: Redirecting Number A) Syntax description

Field No 1 2 3 4 5 6 Byte Pos 1 2 3 4 5 6
Length

(bytes) 1 1 1 1 1 n

Field Name 3 2 1 0 7 6 5 4 Package Number Package Length res NADI (of redirecting party) res NPI [Link]. reserve d LAC Length Number of Digits Digit (i) Digit (i + 1)

Remarks binary; fixed value 170 (HAA) binary; total length of package binary; refer to description binary; refer to description binary packed digits, values (0:HF)

Digit (i): I is incremented every next byte as follows: i=1,3,....,2n-1

Presentation Indicator (according to /8/) Value 0 1 2 3 Meaning presentation allowed presentation restricted address not available (national use) spare

Description of Field No 5:
Field Part Number of Digits LAC Length Meaning Range between 0-31 Total length of Redirecting Number, including LAC Range between 0-7

140

P30308-X2058-K160-03-7617

Data Field Description

B) Functional description The presence of this package is not administrable. The package is however only available in case of Call Diversion to store the DN of the diverting party or for the Centrex Dial In feature. The diverting party number stored in the package is provided by the network or has been received via trunk. In case of partial rerouting, the redirecting number is signalled by the PBX. In this case, the signalled DN is screened by the exchange (as is the case for Calling Party, refer to description of package 142 (Calling Party Number) for details about screening). In case of CFW on the DDI extension in the switch, the redirecting number contains the PDN + DDI extension number. In case of the Centrex Dial In feature, the redirecting number contains the dialled group DN. Remarks: The national or international prefix digits (e.g. 0 or 00) are never present in this package. If the package is present in the ticket, the package 142 (Calling Party Number) is normally not available, unless the presence of this package is triggered with the command ENTR CDTDAT: EXTNSD=OGLCDN;. In this case, package 142 (Calling Party Number) contains the original calling party number. When a CAMA ticket is generated for the forwarding call leg, the CAMA ticket only contains this package when the signalling supports the identification of the redirecting party (i.e. in case of ISUP as separate field, in case of MFC by means of a special category)
AMA Ticket : Record Owner Type = Redirecting Number Package 170 (Redirecting Number) : 912521861, NADI=national Package 168 (Called Party) : 912526678, NADI=national Package 111 (Own FAU) : DIVI Package 142 (Calling Party) : 892525357, NADI=national

switch

B1 subscriber with LAC = 091, DN = 2521861

switch

A subscriber with LAC = 089, DN = 2525357 Dailled digits : 0912521861

B2 subscriber with LAC = 091, DN = 2526678

Figure 35: AMA Tickets in case of Call Diversion

P30308-X2058-K160-03-7617

141

Data Field Description

AMA Ticket : Record Owner Type = Redirecting Number Package 170 (Redirecting Number) : 912521861, NADI=national Package 168 (Called Party) : 912526678, NADI=national Package 111 (Own FAU) : DIVI Package 142 (Calling Party) : 892525357, NADI=national

switch

B1 subscriber with LAC = 091, DN = 2521861

switch

A subscriber with LAC = 089, DN = 2525357 Dailled digits : 0912521861

switch

B2 subscriber with LAC = 091, DN = 2526678

AMA Ticket : Record Owner Type = Redirecting Party Package 170 (Redirecting Number) : 912526678, NADI=national Package 168 (Called Party) : 912449336, NADI=national Package 111 (Own FAU) : DIVI Package 142 (Calling Party) : 892525357, NADI=national

switch

B3 subscriber with LAC = 091, DN = 2449336

Figure 36: AMA Tickets in case of Multiple Call Diversion C) Operating remarks This package is not administrable. D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package.

142

P30308-X2058-K160-03-7617

Data Field Description

[Link] Package 171: Sent Called Party Number A) Syntax description

Field No 1 2 3 4 5 6 Byte Pos 1 2 3 4 5 6
Length

(bytes) 1 1 1 1 1 n

Field Name 3 2 1 7 6 5 4 Package Number Package Length res NADI res NPI reserved Number of Digits Number of

Remarks 0 binary; fixed value 171 (HAB) binary; total length of package binary; refer to description binary; refer to description Binary packed digits, values (0:HF)

CAC Digits
Digit (i) Digit (i + 1) Digit (i): i is incremented every next byte as follows: i=1,3,....,2n-1

Description of Field No 5:
Field Part Number of Digits Meaning Range between 0-31 Total length of Sent Called Party Number, including CAC Digits Range between 0-7

Number of CAC Digits

B) Functional description This package contains the DN equal to the digits sent out over a trunk to the next exchange as Called Party digits or, in case of terminating traffic, as would be sent out over a trunk. The digit string can start with CAC digits; in this case, the Number of CAC Digits will be different from zero.

P30308-X2058-K160-03-7617

143

Data Field Description

This package is only present in Connection tickets under the following conditions: the package has been activated by the craftsperson. the sent out DN differs from the DN stored in package 168 (Called Party Number) or in package 128 (New Destination). the AMA ticket is generated for a call for which ACM (Address Complete Message) has been received. Remarks: The Sent Called Party Number differs from the Called Party Number or the New Destination Number because the Called Party Number or New Destination Number may be converted to other digits before they are sent out as called line digits over a trunk to the next exchange. One typical example is Number Portability in the switch where the AMA ticket is generated, using a switch internal database to find out the routing number (the number identifying the physical location of the B subscriber). It is also possible to use an IN solution for Number Portability; in this case, the routing number is provided in package 128 (New Destination). The Sent Called Party Number is considered equal with the Called Party Number or the New Destination, when functionally the same DN is stored, independent of the way the DN is represented (i.e. in a format without national/international prefix digits or in a format with national/international prefix digits). The national or international prefix digits (e.g. 0 or 00) are never present in package 171. C) Operating remarks The inclusion of the package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = CLDSENT; Conversion of the Called Party Number or New Destination Number to other digits is done via the parameters NEWCODE or CONVCODE in the command CR DEST. With these converted digits, the routing (the exchange process to find a destination based on the digit information) is performed again. CR DEST: DEST = <destination>, CONVCODE = <converted digits>; CR DEST: DEST = <destination>, NEWCODE = <converted digits>; Modification of the digits before they are sent out over a trunk as called line digits is done with the parameters DICON and SSDI in the MML command CR ROUTE: ROUTE = <route>, DEST = <destination>, TGNO = <trunk group name>, DICON = <digit converting code>, SSDI = <starting position for sending out dialled digits>; D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package.

144

P30308-X2058-K160-03-7617

Data Field Description

[Link] Package 172: System Provided Number A) Syntax description

Field No 1 2 3 4 5 6 7 Byte Pos 1 2 3 4 5 6 7
Length

(bytes) 1 1 1 1 1 1 n

Field Name 3 2 1 0 7 6 5 4 Package Number Package Length Number Qualifier Number Type res. NADI res. NPI reserved LAC Length Number of Digits Digit (i) Digit (i + 1)

Remarks binary; fixed value 172 (HAC) binary; total length of package binary; refer to description binary; refer to description binary; refer to description binary packed digits, values (0:HF)

Digit (i): I is incremented every next byte as follows: i=1,3,....,2n-1

Description of Field No 3:
Number Qualifier Value 0 1 2 3 4 5 6 7-15 Meaning Undefined Calling Party Redirecting Party Called Party SCI Served User Connected Party Internet SCI Served User spare

Number Type Value 0 1 2 3 4 5 6 7 8 9 10 11 12-15 Meaning Undefined Subscriber DN PBX Pilot DN PBX Line DN not applicable Default MSN / Primary DN Non Default MSN not applicable not applicable not applicable not applicable Authorization Code Reference Number spare

P30308-X2058-K160-03-7617

145

Data Field Description

Description of Field No 4:
NADI (Nature of Address Indicator) (according to /8/) Value 0 1 2 3 4 5-111 112-126 127 Meaning spare (NADI not received or could not be determined) subscriber number unknown significant national number international number spare reserved for national use spare

Description of Field No 5:
NPI (Numbering Plan Indicator) (according to /8/) Value 0 1 2 3 4 5-6 7 Meaning spare ISDN (telephony) numbering plan spare data numbering plan telex numbering plan reserved for national use spare

Description of Field No 6:
Field Part Number of Digits LAC Length Meaning Range between 0-31 Total length of System Provided Number, including LAC Range between 0-7

B) Functional description The presence of this package is not administrable. The package System Provided Number contains a DN provided by the network to be used for charging. The package is provided in following cases: in all Connection and FAU tickets generated on the B-side of the call in Connection and FAU tickets generated on the A-side of the call, in case the call is originated from a PBX/MLHG. The package contains the PBX Pilot DN or PBX Line DN. in case of Remote SCI to store the DN for whom the SCI is performed, resp. the PBX Pilot DN or PBX Line DN in case the Remote SCI is performed for a PBX subscriber. in case of SCI for (an other) target MSN to store the MSN for whom the SCI is performed. in case of SCI for All Numbers to store the default MSN. in case of SCI, originated by a PBX line. When the SCI is performed for a PBX feature, the package contains the PBX Pilot DN, otherwise, i.e. when the SCI is performed for the PBX line, the package contains the PBX Pilot DN or LSN, depending on the setting of AMAPDN/AMALSN. in case of SCI originated by a member of an SHG with the FEATSHG set (i.e. feature set of the SHG is valid). The package contains the SHG Pilot DN. In case FEATSHG is not set, package 172 is not provided. in case of ISCI. The package contains the director number, for which the ISCI is performed.
146 P30308-X2058-K160-03-7617

Data Field Description

in case of a remote access to a network whereby the access is authenticated by means of an authorization code. In this case the package contains the authorization code reference number. Remarks: When no Default MSN has been assigned to the subscriber who performs an SCI for All Numbers, the first assigned DN is provided in the package. The Number Type indicates non default MSN. In case of Remote SCI, the DN from where the SCI is performed is stored in the package 142 (Calling Party Number), on condition the package has been activated by the craftsperson. In case of ISCI, the DN with which the subscriber has logged into the ISCI server is stored in the package 142 (Calling Party Number). The national or international prefix digits (e.g. 0 or 00) are never present in this package. C) Operating remarks The DN that is stored in the AMA tickets in case of PBX/MLHG is administered with the parameter CHRG=AMAPDN (DN to be stored is the Pilot Directory Number) or CHRG=AMALSN (DN to be stored is the Line Service Number) in the CR PBXLN command. In case CHRG=AMASGN (AMA on the signalled number) is specified, the package 172 (System Provided Number) will be provided, but the Record Owner Type will point to the package 142 (Calling Party Number) or 170 (Redirecting Number). The Reference Number that is stored in the AMA tickets in case of remote access to a network is administered with CR SUB: LAC=<lac>, DN=<dn>, CAT=TXS; D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. [Link] Package 178: Exchange Info A) Syntax description
Field No 1 2 3 4 4+i 5+i Byte Pos 1 2 3 4 4+i 5+i
Length

(bytes) 1 1 1 1 1 n

Field Name 7 6 5 4 Package Number Package Length reserved Version ID reserved Exchange ID

Remarks 3 2 1 0 binary; fixed value 178 (HB2) binary; total length of package VA1 VA0 binary; validity bits; refer to description binary; range (1:99) Exchange ID Length binary; range (0:11) char; max. 11 bytes

Note: i = 0 if Version ID not present in the package i = 1 if Version ID present in the package

P30308-X2058-K160-03-7617

147

Data Field Description

Description of Field No 3: The validity bits indicate whether the Version ID and/or the Exchange ID are stored in the package. When one of the items is not stored in the package, the corresponding fields/bytes are not present.
Validity Bits Flag VA0 VA1 Value Meaning 1 0 1 0 Version ID is stored no Version ID is stored Exchange ID is stored no Exchange ID is stored

B) Functional description This package contains the Version ID and/or the Exchange ID. The Version ID defines by means of a unique, by the operator-defined number, the version of the AMA or CDR record. The Exchange ID is identified either by means of a Name or by means of an Identification Number (IDNO). Remarks: The identification of the Exchange by means of the Exchange ID is provided when: so requested by the operator (via ENTR CDTDAT: ALTNSD=EXCHIDNO) an IDNO has been administered (via ENTR EXCHID, parameter IDNO) When no EXCH-IDNO is available, the Exchange Name is provided as default. C) Operating remarks The inclusion of the package in the AMA or CDR ticket is controlled via commands ENTR CDTDAT: EXTNSD = VERSID, VERSID=nn; (where nn defines the value of the Version ID) ENTR CDTDAT: EXTNSD = EXCHNAME; ENTR CDTDAT: ALTNSD = EXCHIDNO; The Name or Identification Number of the Exchange is entered with the command ENTR EXCHID: NAME = <1-5 characters> [,IDNO=<1-11 characters>]; If the CDR feature is activated, the Version ID entered with the command ENTR CDTDAT: EXTNSD = VERSID, VERSID=nn; must be equal for REC=AMA and for REC=IACAMA, unless the extra data item is only activated for one of the two recordings.

D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package.

148

P30308-X2058-K160-03-7617

Data Field Description

[Link] Package 179: Service Subscriber Number A) Syntax description

Field No 1 2 3 4 5 6 Byte Pos 1 2 3 4 5 6
Length

(bytes) 1 1 1 1 1 n

binary; fixed value 179 (HB3) binary; total length of package Service Subscriber binary; refer to description of Service Number Qualifier Subscriber Number Qualifier not applicable binary; relevant for IN AMA Coding Number of Digits or binary; refer to description of Coding Number of Bytes Digits (packed) or Characters packed digits or characters

Field Name 7 6 5 4 Package Number Package Length reserved

Remarks 3 2 1 0

Description of Field No 3:
Service Subscriber Number Qualifier Value 0 1 2 3 4 5-15 Meaning undefined not applicable TFS service subscriber not applicable SIP subscriber reserved

Description of Field No 5:
Coding Value 0 1 2-3 Meaning Service subscriber number coded as packed digits Service subscriber number coded as character string reserved

B) Functional description In case the ticket is generated to charge the TFS subscriber, this package contains the TFS account number. This account number is generated (project-specifically) based on the TFS service number, an account number prefix and exchange digits. The package is also used to register the SIP URL (Uniform Resource Locator) in case of interworking between SIP and PSTN. In case a SIP Multi-media user initiates a voice call to a PSTN subscriber, the SIP server will forward the request to the Call Feature Server, where a PSTN call is set up. The A-side of the call is a trunk. The CAMA ticket which is possibly generated on this incoming trunk port will contain the package 179 (Service Subscriber) if administered with ENTR CDTDAT and if the SIP URL is present.

P30308-X2058-K160-03-7617

149

Data Field Description

CAMA Ticket : Record Owner Type = Service Subscriber Package 179 (Service Subscriber): +49-89-722-63251@[Link] Package 168 (Called Party) : 912521861, NADI=national

SIP user with URL +49-89-722-63251@[Link] Dailled digits : 0912521861

Call Feature Server SIP Multi-media user SIP Proxy / Redirect Server
MGCP SS7

STP

Switch

PSTN
IP Core VoIP GW

Figure 37: AMA Ticket in case of SIP - PSTN Interworking Remark: The TFS account number is stored as packed digits (i.e. Coding is 0). C) Operating remarks The inclusion of the package in the TFS AMA ticket is not administrable. In case of SIP-PSTN interworking, the inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = SSN; D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. [Link] Package 183: Sent CAC A) Syntax description
Field No 1 2 3 4 Byte Pos 1 2 3 4
Length

(bytes) 1 1 1 n

Field Name 7 6 5 4 Package Number Package Length Reserved Digit (i)

Remarks 3 2 1 0 binary; fixed value 183 (HB7) binary; total length of package binary; range 0 - 7

packed digits, value (0:HF), including prefix digits Digit (i): I is incremented every next byte as follows: i=1,3,....,2n-1

Number of CAC Digits Digit (i + 1)

150

P30308-X2058-K160-03-7617

Data Field Description

B) Functional description The CAC digits can be transported in the IAM ISUP message in two different ways, depending on the trunk group characteristics. The CAC can be embedded in the called party number (as prefix before the called party digits), or the CAC can be transported in an own parameter TNS (Transit Network Selection). In case the CAC is embedded in the called party number, the CAC will be visible in package 171 (Sent Called Party Number). In case the CAC is transported in the TNS parameter, the CAC is stored in package 183 (Sent CAC). Remark however, that the TNS parameter does not contain the CAC prefix digits. In following cases, the difference between the Sent CAC and the Billing CAC is more than the prefix digits: A CAC has been determined as necessary for the routing (command CR CACCPT), but during further digit processing, this CAC is substituted by another one. It has been determined that a CAC is necessary for a certain destination, but the subscriber has not dialled a CAC, and has no CAC preselected. In this case, the exchange default CAC is taken. A CAC is assigned to a trunk group, no CAC has been received, and a CAC is necessary for routing.

C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = CAC and ENTR CDTDAT: EXTNSD = CLDSENT; Remark that EXTNSD = CAC is already set by default, so normally the 2nd command will be sufficient. The transport of the CAC in the TNS parameter is controlled by the command: CR TGRP: TGNO= <trunk group>, GCOS = CACTNSC; D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. [Link] Package 184: MLPP Level A) Syntax description
Field No 1 2 3 4 5 Byte Pos 1 2 3 4 6
Length

(bytes) 1 1 1 2 3

Field Name 7 6 5 3 2 1 0 4 Package Number Package Length res. LFB res. Precedence Level

Remarks binary; fixed value 184 (HB8) binary; total length of package binary; refer to description sp. = spare packed digits, value (0:9) binary

Network Identity Digit (i)

Network Identity Digit (i + 1)

MLPP service domain

Digit (i): i is incremented every next byte as follows: i=1,3

P30308-X2058-K160-03-7617

151

Data Field Description

Description of Field No 3:
Precedence Level Value 0 1 2 3 4 Meaning Flash override (highest priority) Flash Immediate Priority Routine (lowest priority)

LFB (Look-ahead for busy) (not supported) Value 2 Meaning LFB not allowed

Functional description This package contains information for the Multi-Level Precedence and Preemption feature, which is defined in ITU recommendation Q735. With this feature, a maximum Precedence level can be assigned to a subscriber. When setting up a call, the subscriber can choose by subscriber controlled input one Precedence level for this call, up to the maximum level that has been assigned to him. From this moment on, the call has got a Precedence level. When a call with a Precedence level reaches a busy B-subscriber, it is checked whether this B-subscriber belongs to the same network (indicated by the Network Identity digits) and the same MLPP service domain within this network whether this B-subscriber is subscribed to the MLPP service whether the Precedence level of the B-subscriber is lower than the Precedence level of the call

When all these conditions are fulfilled, the call is pre-empted, that means, the call of the Bsubscriber is forced released, and the call with the Precedence level is set up to the Bsubscriber. Preemption also works when busy network resources are met. In this case, the resources with the lowest priority are released. Remarks: Package 184 is only provided in case the both A- and B-subscriber have been subscribed to the MLPP feature, and if they both belong to the same network and domain. Under these conditions, the package can also be present if the A-subscriber did not indicate an MLPP level; in this case, the lowest Precedence level (Routine) is provided. The Network Identity is coded as packed digits. The first digit of this field is coded as 0, followed by the Telephony Country Code digits. The MLPP Service Domain is administered by the network provider. It is a binary coded value of up to 8 digits (range 0:16,777,214). B) Operating remarks This package is included in the AMA ticket if both an MLPP level has been determined for the call and the package is requested by the craftsperson via the command ENTR CDTDAT: EXTNSD=MLPP;

152

P30308-X2058-K160-03-7617

Data Field Description

C) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. [Link] Package 186: IN Service Key A) Syntax description
Field No 1 2 3 Byte Pos 1 2 3
Length

(bytes) 1 1 4

Field Name 7 6 5 4 Package Number Package Length IN Service Key

Remarks 3 2 1 0 binary; fixed value 186 (HBA) binary; total length of package binary; range 0 H7F FF FF FF

B) Functional description The IN Service Key identifies the requested IN Service. This information is sent to the SCP, where it is used to address the correct application or Service Logic Program. Based on this IN Service, the SCP may derive a new IN Service, which is registered in the IN AMA record as IN Service Indicator. The IN Service Key is taken out of the SSPs internal Trigger Data Base and is available at the trigger detection points 1, 2 ,3, 4, 5, 6, 12, 13 and 14. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = INSERVK; D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. The presence of this package can be used to determine whether the AMA ticket has been generated for an IN call, with the restriction that only IN services with unconditional triggers are registered. [Link] Package 187: Received CAC A) Syntax description
Field No 1 2 3 4 Byte Pos 1 2 3 4
Length

(bytes) 1 1 1 n

Field Name 7 6 5 4 Package Number Package Length Reserved Digit (i)

Remarks 3 2 1 0 binary; fixed value 187 (HBB) binary; total length of package of binary; range 0 - 7 packed digits, value (0:HF), including prefix digits

Number CAC Digits Digit (i + 1)

Digit (i): i is incremented every next byte as follows: i=1,3,....,2n-1

P30308-X2058-K160-03-7617

153

Data Field Description

B) Functional description In the originating exchange, the CAC digits dialled by the subscriber will appear in package 153. The package 187 will only be present in following cases: The subscriber dials an abbreviated number and the long number behind this abbreviated number contains a CAC. The subscriber dials a code before dialling a CAC (this is e.g. the case when the subscriber dials the code for DEB Next Call) The call is forwarded and the call forwarding number contains a CAC. In the AMA ticket for the second leg of the forwarded call, only the package 187 (Received CAC) will be present; the package 153 (Received Called Party Number) will not be present. A recall is initiated after CCBS or CCNR. The AMA ticket generated for the recall will only contain the package 187 (Received CAC); the package 153 (Received Called Party Number) will not be present. In the transit exchange, the CAC digits, which are embedded in the called party digits, are indicated as such in package 153. A received TNS will be stored in package 187. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = CAC and ENTR CDTDAT: EXTNSD = CLDRCVD. Remark that EXTNSD = CAC is already set by default, so normally the 2nd command will be sufficient. The transport of the CAC in the TNS parameter is controlled by the command: CR TGRP: TGNO= <trunk group>, GCOS = CACTNSC; D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. [Link] Package 191: Signalling Point Code A) Syntax description
Field No 1 2 3 4 Byte Pos 1 2 3 4
Length

(bytes) 1 1 1 3

Field Name 7 6 5 4 Package Number Package Length Network Number

Remarks 3 2 1 0 binary; fixed value 191 (HBF) binary; fixed value 6 Network binary; refer to description Indicator binary

Signalling Point Code

Description of Field No 3 : Network Indicator Value Meaning 0 International 0 1 International 1 2 National 0 3 National 1 Description of Field No 3 : Network Number The Network Number has a range from 1 to 32, and is used in case up to 32 different ISUP networks are maintained in the switch, each having its own addressing plan. This is only possible when a configuration with a SSNC is used.
154 P30308-X2058-K160-03-7617

Data Field Description

The Network Number is physically associated to the signalling links and is only switch internally used to differentiate between the different networks.

P30308-X2058-K160-03-7617

155

Data Field Description

B) Functional description This field contains the Signalling Point Code of the switch, which consists of 2 or 3 bytes according to the related SPC length in the network. If the length is 2 bytes, only 14 bits are relevant; the bits 6 and 7 of the second byte and the complete third byte are spare. The SPC is part of the office data and depends on the network indicator (NI), which is port dependent. In case the network indicator cannot be determined (e.g. when the AMA ticket is generated for a subscriber), the value National 0 is taken. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT : EXTNSD = SPC; The Signalling Point Code of the own switch is administered with the command CR C7OP: SPC = <Signalling Point Code>, NETIND = <Network Indicator>, STPI = <Signalling Transfer Point indicator>; The Network Indicator on trunk group level is administered via command: ENTR C7TGREL: TGNO = <trunk group>, DPC = <destination point code>, NETIND = <network indicator>; D) Postprocessing remarks The total package length (in byte) is located at the second byte of the package. The value is always 6, even when the SPC has only a length of 14 bits. [Link] Package 192: Sent Calling Party Number A) Syntax description
Field No 1 2 3 4 5 6 Byte Pos 1 2 3 4 5 6
Length

(bytes) 1 1 1 1 1 n

Field Name 7 6 5 4 Package Number Package Length res. NADI res. NPI LAC Length Digit (i)

Remarks 3 2 1 0

binary; fixed value 192 (HC0) binary; total length of package binary; refer to description [Link] Screening binary; refer to description . Number of Digits binary Digit (i + 1) packed digits, values (0:HF)

Digit (i): i is incremented every next byte as follows: i=1,3,....,2n-1

156

P30308-X2058-K160-03-7617

Data Field Description

Presentation Indicator (according to /8/) Value 0 1 2 3 Meaning presentation allowed presentation restricted address not available (national use) spare

Description of Field No 5:
Field Part Number of Digits LAC Length Meaning Range between 0-31 Total length of Sent Calling Party Number, including LAC Range between 0-7

B) Functional description This package contains the DN equal to the Calling Line digits sent out over a trunk to the next exchange or, in case of terminating traffic, as would be sent out over a trunk. This package is only present in Connection tickets under the following conditions: the package has been activated by the craftsperson. package 142 (Calling Party Number) is either not present or package 142 is present and the Sent Calling Party Number differs from the DN stored in package 142. the AMA ticket is generated for a call for which ACM (Address Complete Message) has been received. The calling party number has been sent (condition not relevant for terminating traffic). Remarks: The Sent Calling Party Number can differ from the Calling Party Number because the Calling Party Number can be converted to another format (e.g. from national into international format).

P30308-X2058-K160-03-7617

157

Data Field Description

The Sent Calling Party Number is considered equal with the Calling Party Number, when functionally the same DN is stored, independent of the way the DN is represented (i.e. in a format without national/international prefix digits or in a format with national/international prefix digits). The national or international prefix digits (e.g. 0 or 00) are never present in package 192. In case the package 142 (Calling Party Number) is not present in the ticket, the package 192 will always be provided when requested and when relevant. This is the case for Call Diversion when the extra data item OCLGDN in the ENTR CDTDAT command has not been set. Package 142 is also not present in case of Remote SCI and SCI for Kick out (refer to /10/) when OCLGDN is not set, but in these last two cases, the Sent Calling Party Number is not relevant. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = CLGSENT; D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. [Link] Package 193: Sent Redirecting Number A) Syntax description
Field No 1 2 3 4 5 6 Byte Pos 1 2 3 4 5 6
Length

(bytes) 1 1 1 1 1 n

Field Name 7 6 5 3 2 1 4 Package Number Package Length res. NADI res. NPI reserved LAC Length Number of Digits Digit (i) Digit (i + 1)

Remarks 0 binary; fixed value 193 (HC1) binary; total length of package binary; refer to description binary; refer to description binary packed digits, values (0:HF)

Digit (i): i is incremented every next byte as follows: i=1,3,....,2n-1

158

P30308-X2058-K160-03-7617

Data Field Description

Description of Field No 5:
Field Part Number of Digits LAC Length Meaning Range between 0-31 Total length of Sent Redirecting Number, including LAC Range between 0-7

B) Functional description This package contains the DN equal to the Redirecting digits sent out over a trunk to the next exchange or, in case of terminating traffic, as would be sent out over a trunk. This package is only present in Connection tickets under the following conditions: the package has been activated by the craftsperson. package 170 (Redirecting Number) is present and the Sent Redirecting Number differs from the DN stored in package 170. the AMA ticket is generated for a call for which ACM (Address Complete Message) has been received. The redirecting number has been sent (condition not relevant for terminating traffic). Remarks: The Sent Redirecting Number can differ from the Redirecting Number because the Redirecting Number can be converted to another format (e.g. from national into international format). The Sent Redirecting Number is considered equal with the Redirecting Number, when functionally the same DN is stored, independent of the way the DN is represented (i.e. in a format without national/international prefix digits or in a format with national/international prefix digits). The national or international prefix digits (e.g. 0 or 00) are never present in package 193. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = REDSENT; D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package.

P30308-X2058-K160-03-7617

159

Data Field Description

[Link] Package 194: Sent Calling Party Category A) Syntax description

Field No 1 2 3 Byte Pos 1 2 3
Length

(bytes) 1 1 1

Field Name 3 2 7 6 5 4 Package Number Package Length Sent Calling Party Category

Remarks 1 0 binary; fixed value 194 (HC2) binary; total length of package refer to description below

B) Functional description This package contains the Calling Party Category sent out over a trunk to the next exchange or, in case of terminating traffic, as would be sent out over a trunk. This package is only present in Connection tickets under the following conditions: the package has been activated by the craftsperson. either package 120 (Calling Party Category) is not present and the Sent Calling Party Category is different from 1 (and 0, which is undefined) or package 120 is present and the Sent Calling Party Category is different from package 120 the AMA ticket is generated for a call for which ACM (Address Complete Message) has been received. The calling party category has been sent (condition not relevant for terminating traffic). Remarks: The Sent Calling Party Category can differ from the Calling Party Category for the following reasons: in case of a test call, the category to be sent out can be changed into test equipment a category priority subscriber can be changed into normal subscriber in case the outgoing ISUP does not allow the feature priority service a category operator can be changed into normal subscriber in case the outgoing ISUP does not allow the feature trunk offering In contradiction to package 120, package 194 can contain the value 1 (subscriber).

160

P30308-X2058-K160-03-7617

Data Field Description

C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = CATSENT; D) Postprocessing remarks This package has a fixed length of 3 bytes. The package length is included on byte 2 in the package itself. [Link] Package 195: Original Calling Party Category A) Syntax description
Field No 1 2 3 Byte Pos 1 2 3
Length

(bytes) 1 1 1

Field Name 7 6 5 3 2 1 4 Package Number Package Length Original Calling Party Category

Remarks 0 binary; fixed value 195 (HC3) binary; total length of package refer to description below

B) Functional description This package contains the Calling Party Category as was originally received over trunk, or was originally set up in case the A-side was a subscriber. This package is only present in Connection tickets under the following conditions: the package has been activated by the craftsperson. either package 120 (Calling Party Category) is not present and the Original Calling Party Category is different from 1 or package 120 is present and the Original Calling Party Category is different from package 120

P30308-X2058-K160-03-7617

161

Data Field Description

Remarks: The Original Calling Party Category can differ from the Calling Party Category in following cases: in case of an IN call, when the SCP provides the SSP with another Calling Line Number and another Calling Party Category. in case an unknown category is received In contradiction to package 120, package 195 can contain the value 1 (subscriber). In contradiction to package 194, package 195 can contain the value 0 (undefined) C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = CATRCVD; D) Postprocessing remarks This package has a fixed length of 3 bytes. The package length is included on byte 2 in the package itself. [Link] Package 196: Trunk Info A) Syntax description
Field No 1 2 3 Byte Pos 1 2 3
Length

(bytes) 1 1 n

Field Name 7 6 5 3 2 4 Package Number Package Length Trunk Info Subpackages

Remarks 1 0 binary; fixed value 196 (HC4) binary; total length of package binary; max. 34 bytes filled up with subpackages

1. Subpackage Trunk Id incoming

Field No +1 +2 +3 +4 Byte Pos 1 2 3 15 Length (bytes) 1 1 12 2 Field Name 7 6 5 3 4 Subpackage Number Subpackage Length Trunk Group Name Trunk Number Remarks 2 1 0 binary; fixed value 1 (H01) binary; total length of subpackage 12 characters binary, range 0 - 16383

2. Subpackage Trunk Id outgoing

Field No +1 +2 +3 +4 Byte Pos 1 2 3 15
Length

(bytes) 1 1 12 2

Field Name 7 6 5 3 4 Subpackage Number Subpackage Length Trunk Group Name Trunk Number

Remarks 2 1 0 binary; fixed value 2 (H02) binary; total length of subpackage 12 characters binary, range 0 - 16383

162

P30308-X2058-K160-03-7617

Data Field Description

3. Subpackage Trunk Id with CIC incoming

Field No +1 +2 +3 +4 +5 Byte Pos 1 2 3 15 17 Length (bytes) 1 1 12 2 1 Field Name 7 6 5 3 4 Subpackage Number Subpackage Length Trunk Group Name CIC PCM Number CIC Channel Number Remarks 2 1 0 binary; fixed value 03 (H03) binary; total length of subpackage char, max. 12 binary range 0range 0681 511 (DIU (DIU24) 30) binary range 0-24 range 0-31

4. Subpackage Trunk Id with CIC outgoing

Field No +1 +2 +3 +4 +5 Byte Pos 1 2 3 15 17
Length

(bytes) 1 1 12 2 1

Field Name 3 7 6 5 4 Subpackage Number Subpackage Length Trunk Group Name CIC PCM Number CIC Channel Number

Remarks 2 1 0 binary; fixed value 04 (H04) binary; total length of subpackage char, max. 12 binary range 0range 0681 511 (DIU (DIU24) 30) binary range 0-24 range 0-31

B) Functional description When administered by the crafts person, package 196 is generated under the same circumstances as described under package 105/107 (Trunk Identification Incoming) and package 106/108 (Trunk Identification Outgoing) and instead of these packages. The CIC format indicates that the trunk is identified with the number of the PCM (Pulse Code Modulation) trunk, and the number of the channel on this PCM trunk. C) Operating remarks The inclusion of this package 196 with only the subpackages 01 and 02 instead of package 105 and 106 in the AMA ticket is controlled via command ENTR CDTDAT: ALTNSD = TGNA; (prerequisite is ENTR CDTDAT: EXTNSD = RECTRID). The inclusion of this package 196 with only the subpackages 03 and 04 instead of package 107 and 108 in the AMA ticket is controlled via command ENTR CDTDAT: ALTNSD = TGNA&RECTRCIC; (prerequisite is ENTR CDTDAT: EXTNSD = RECTRID). D) Postprocessing remarks The total package length (in byte) is located at the second byte of the package.

P30308-X2058-K160-03-7617

163

Data Field Description

[Link] Package 198: Durations in 100 msec A) Syntax description

Field No 1 2 3 Byte Pos 1 2 3
Length

(bytes) 1 1 n

Field Name 3 2 7 6 5 4 Package Number Package Length Durations Subpackages

Remarks 1 0 binary; fixed value 198 (HC6) binary; total length of package binary; max. 13 bytes filled up with subpackages

1. Subpackage Call Duration

Field No +1 +2 +3 Byte Pos 1 2 3 Length (bytes) 1 1 3 Field Name 7 6 5 3 4 Subpackage Number Subpackage Length Call Duration Remarks 2 1 0 binary; fixed value 1 (H01) binary; total length of subpackage binary

2. Subpackage Durations Before Answer

Field No +1 +2 +3 +4 Byte Pos 1 2 3 6
Length

(bytes) 1 1 3 3

Field Name 7 6 5 3 2 1 0 4 Subpackage Number Subpackage Length Duration from dialtone till address complete Duration from address complete till answer or till the start indication of UI or till release of the unanswered connection

Remarks binary; fixed value 2 (H02) binary; total length of subpackage Binary; Binary

B) Functional description When administered by the crafts person, package 198 is generated under the same circumstances as described under package 100 (Date/Time/Duration) and package 134 (Duration Before Answer). This package registers the duration with a granularity of 100 msec (e.g. 500 msec is registered as binary value 5); the packages 100 and 134 register the duration with a granularity of seconds. The package 198 is registered together with package 116 (Date/Time) and instead of the packages 100 and 134. The duration has an accuracy of 100 msec. This implies that a duration of 0 ms is possible, in exceptional cases. C) Operating remarks The inclusion of this package 198 and package 116 (Date/Time) in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = REFINDUR; (not set by default). The inclusion of the subpackage 02 (Durations Before Answer) in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = DURBANS.

164

P30308-X2058-K160-03-7617

Data Field Description

In case the common CDR registration is defined, the operator is advised to define the same granularity for all applications of the CDR. If different, the granularity defined for AMA has the priority. D) Postprocessing remarks The total package length (in byte) is located at the second byte of the package. [Link] Package 199: Received Charge Determination Information A) Syntax description
Field No 1 2 3 Byte Pos 1 2 3 Field Name 3 6 5 (bytes) 7 4 1 Package Number 1 Package Length 1 reserved
Length

Remarks 2 1 0 binary; fixed value 199 (HC7) binary; fixed value 3 (H03) CDI binary; refer to description

Description of Field No 3:
CDI (Charge determination info) Value 0 1 Meaning charge not yet determined charge already determined

B) Functional description The package will only be present in case the A-side is an ISUP trunk. The package will contain the received information, independent whether this received information is used or not. When e.g. the parameter CONZON is received on a trunk group which is marked with UNZON (unconditionally zoned), the ticket will contain this parameter despite of the fact that the CONZON parameter will be ignored for the further processing. The inclusion of this parameter will not be made administrable (i.e. no new value in the ENTR CDTDAT command). As soon as the parameter is received (which is only possible with the ISUP variants which sustain the new parameter), the info is included in the tickets. C) Operating remarks The package is not administrable; as soon as the information is received over trunk, the package is included in the AMA ticket. D) Postprocessing remarks This package has a fixed length of 3 bytes. The package length is included on byte 2 in the package itself

P30308-X2058-K160-03-7617

165

Data Field Description

[Link] Package 204: Access Data A) Syntax description

Field No 1 2 3 Byte Pos. 1 2 3
Length

(bytes) 1 1 n

Field Name 7 6 5 4 Package Number Package Length Subpackages

Remarks 3 2 1 0 binary; fixed value 204 (HCC) binary; total length of package refer to description of the subpackages

1. Subpackage Terminal Type

Field No +1 +2 +3 Byte Pos. +1 +2 +3
Length

(bytes) 1 1 1

Field Name 7 6 5 3 4 Subpackage Number Subpackage Length Terminal Type

Remarks 2 1 0 binary; fixed value 1 (H01) binary; total length of subpackage binary; see table below

Terminal Type Value 0 1 2 3 4 5 6 7 8 9 10 Meaning undefined analog subscriber analog PBX ISDN subscriber ISDN PBX PA ISDN PBX BA Coinbox H.323 subscriber with reduced feature set H.323 subscriber with full feature set H.323 PBX Pure H.323 subscriber

2. Subpackage Operation Mode

Field No +1 +2 +3 Byte Pos. +1 +2 +3
Length

(bytes) 1 1 1

Field Name 7 6 5 3 2 1 0 4 Subpackage Number Subpackage Length Opmode B-side Opmode A-side

Remarks binary; fixed value 2 (H02) binary; total length of subpackage binary; see table below

Opmode A-side / B-side Value 0 1 2 3 Meaning Not available Incoming Outgoing Bothway

166

P30308-X2058-K160-03-7617

Data Field Description

3. Subpackage DLU / V5.2 Number A-side

Field No +1 +2 +3 Byte Pos. +1 +2 +3
Length

(bytes) 1 1 2

Field Name 7 6 5 3 4 Subpackage Number Subpackage Length Number A-side

Remarks 2 1 0 binary; fixed value 3 (H03) binary; total length of subpackage binary

4. Subpackage DLU / V5.2 Number B-side

Field No +1 +2 +3 Byte Pos. +1 +2 +3
Length

(bytes) 1 1 2

Field Name 7 6 5 3 4 Subpackage Number Subpackage Length Number B-side

Remarks 2 1 0 binary; fixed value 4 (H04) binary; total length of subpackage binary

5. Subpackage Port Address of A-Side

Field No +1 +2 +3 +4 +5 +6 +7 Byte Pos. +1 +2 +3 +4 +6 +7 +8
Length

(bytes) 1 1 1 2 1 1 1

Field Name 7 6 5 3 2 1 0 4 Subpackage Number Subpackage Length reserve Port Type Address part a reserve reserve Address part b reserve Address part c res Address part d

Remarks binary; fixed value 5 (H05) binary; total length of subpackage binary; see table below binary binary binary binary

Port Type Value 0 1 2 3-15 Meaning LTG DLU V5.2 Interface reserve

Address part a The content depends on the Port Type: Port Type Content LTG DLU V52IF LTG set (Time Stage Group) DLU number V5.2 Interface number Value Range 0 31 10 2550 6000 8999

P30308-X2058-K160-03-7617

167

Data Field Description

Address part b The content depends on the Port Type: Port Type Content LTG DLU V52IF LTG number DLU shelf number Extension Unit 1 Value Range 1 63 07 0

Address part c The content depends on the Port Type: Port Type Content LTG DLU V52IF Line Trunk Unit DLU module number V5IF port digits 1 Value Range 07 0 15 0 20

Address part d The content depends on the Port Type: Port Type Content LTG DLU V52IF Channel Number DLU circuit number V5.2 port digits 2 Value Range 0 31 0 15 0 99

6. Subpackage Path Selection Type

Field No +1 +2 +3 Byte Pos. +1 +2 +3
Length

(bytes) 1 1 1

Field Name 7 6 5 3 4 Subpackage Number Subpackage Length Path selection

Remarks 2 1 0 binary; fixed value 6 (H06) binary; total length of subpackage binary; see table below

Path selection Type Value 0 1 2 3 4 5 6 Meaning Undefined SN path SN path interface trunk Sidedoor trunk Intra-RSU Sidedoor to Sidedoor trunk Sidedoor to Interface trunk

168

P30308-X2058-K160-03-7617

Data Field Description

B) Functional description This package contains several kinds of semipermanent data: the subpackage 01 (Terminal Type) is only relevant in case the A-side is a subscriber, and specifies the kind of subscriber which has initiated the call. the subpackage 02 (Operation Mode) is only relevant in case the A- or B-side is a trunk. It indicates whether the A- or B-side trunk belongs to an incoming, an outgoing or a bothway trunk group. This subpackage is not relevant for announcement groups. the subpackage 03 (DLU / V5.2 Number A-side) is only relevant in case the A-side is a subscriber. The DLU Number has a range from 10 to 2550 and is always a multiple of 10. The V5.2 number has a range from 6000 to 8999. the subpackage 04 (DLU / V5.2 Number B-side) is only relevant in case the B-side is a subscriber. the subpackage 05 (Port Address of A-side or B-side in case of terminating DNOBS records) is always present when requested by the craftsperson via MML command ENTR CDTDAT. Subpackage 06 does not contain semipermanent data, but indicates which kind of switching has been performed between A- and B-side. Several values in this package refer to a configuration with an RSU (Remote Switching Unit). An RSU consists of LTGs and associated periphery, which are located at a remote site. The RSU also contains RTI (Remote Timeslot Interchange) equipment; the counterpart at the host switch side is the HTI (Host Timeslot Interchange) equipment. The following picture gives an overview of an RSU configuration.
LTG LTG LTG
RTI

sidedoor trunk
TTI

LTG

Interface trunk Interface trunk sidedoor trunk

switch
HTI

Interface trunk
LTG

HTI

RTI

LTG

Figure 38: RSU configuration The Path Selection is not available in tickets, which have been generated during RSU SAS (Standalone Service). More information about RSU can be found in /10/. C) Operating remarks The package itself is not controlled by MML; only the subpackages are controlled by the MML command ENTR CDTDAT.

P30308-X2058-K160-03-7617

169

Data Field Description

The inclusion of subpackage 01 (Terminal Type) is controlled via the command ENTR CDTDAT: EXTNSD = TERMTYPE; The inclusion of subpackage 02 (Operation Mode) is controlled via the command ENTR CDTDAT: EXTNSD = OPMODE; The inclusion of subpackages 03 and 04 (DLU / V5.2 number) is controlled via the command ENTR CDTDAT: EXTNSD = DLUV52; The inclusion of subpackage 05 (Port Address) is controlled via the command ENTR CDTDAT: EXTNSD = PORTADR; The inclusion of subpackage 06 (Path Selection Type) is controlled via the command ENTR CDTDAT: EXTNSD = PATHSEL; D) Postprocessing remarks The total package length (in bytes) is located at the second byte of the package. The package will only be present when the inclusion of at least one of the subpackages has been required by administration (ENTR CDTDAT) and at least one of these ordered subpackages is relevant for the call. [Link] Package 205: Non Charged Facilities Used By Owner A) Syntax description
Field No 1 2 3 Byte Pos 1 2 3 Field Name 6 5 (bytes) 7 4 1 Package Number 1 Package Length
Length

Remarks 3 2 1 0 binary; fixed value 205 (HCD) total length of package binary; value between 3 (1 facility collected) and 10 (8 facilities collected) binary refer to description of field Facility in package 111 (Facilities Used by Owner)

Facility 1 : Facility n

B) Functional description This package contains the facilities, which have been used by the record owner during the call, and which are not marked as chargeable. Up to 8 facilities can be collected for one call. This package is only relevant for Connection and FAU tickets. For a general description of the Facility Usage Charging concept, refer to /10/. Remarks: A Facility is not marked as chargeable either because the command CR FAUCHA has not been entered for this Facility, or because the Answer signal has not yet been received.

170

P30308-X2058-K160-03-7617

Data Field Description

C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = FAUNONCH; Facility Usages are made chargeable with the MML-command CR FAUCHA: FAC = <facility>, BILLING = AMA; or CR FAUCHA: FAC = <facility>, BILLING = METERING, METPULS = <FAU charge units>; and ENTR CDTDAT: MARKS = DEBFA or MOD CHRGFEA: DN = <dn>, LAC = <lac>, COS = FAUAMA; D) Postprocessing remarks In contradiction to the charged Facilities, there is no concept for the registration of repeated use of non-charged Facilities. This package has a variable length. The length in bytes is stored on byte 2 of the package. [Link] Package 209: Accumulated Currency Charges A) Syntax description
Field No 1 2 3 4 5 Byte Pos 1 2 3 4 7
Length

(bytes) 1 1 1 3 1

Field Name 7 6 5 4 Package Number Package Length Scale Factor Currency

Remarks 3 2 1 0 binary; fixed value 209 (HD1) binary; fixed value 7 ref. description ref. description ref. description

Description of Field No 3: Scale The actual value of the currency Scale is given by 10x, where x is the value stored in the package. Remark that the negative values (-7 till -1) are coded in one byte as a complement of 256. Examples:
Scale Scale -7 -6 -5 -4 -3 -2 -1 0 1 2 3 Value 249 250 251 252 253 254 255 0 1 2 3 Meaning 0.0000001 0.000001 0.00001 0.0001 0.001 0.01 0.1 1 10 100 1000

P30308-X2058-K160-03-7617

171

Data Field Description

Description of Field No 4: Factor Integer between 0 and 999999; 0 indicates no charge. Description of Field No 5: Currency
No Indication Australian Dollar Austrian Schilling Belgian Franc British Pound Czech Krona Danish Krone Dutch Guilder Euro Finnish Markka French Franc German Mark Greek Drachma (0-00) (1-01) (2-02) (3-03) (4-04) (5-05) (6-06) (7-07) (8-08) (9-09) (10-0A) (11-0B) (12-0C) (13-0D) (14-0E) (15-0F) (16-10) (17-11) (18-12) (19-13) (20-14) (21-15) (22-16) (23-17) (24-18) (25-19) (26-1A) (27-1B)

B) Functional description This package contains the accumulated charges in currency format. This package is the counterpart of package 103 (Charge Units For Connection): if both packages are required by the craftsperson via ENTR CDTDAT, either package 103 or package 209 will be present in the AMA ticket, depending on the fact whether the tariff has been administered in pulses or in currency. This package is relevant for both analog and ISDN subscribers. Remarks: If both package 156 (Advised Cumulated Charges) and package 209 (Accumulated Currency Charges) are required by the craftsperson, package 156 will never be built. Package 209 will be built instead, under condition the tariff for the call has been administered in currency. In case the accumulated charges reach the maximum value, no intermediate charging is done, and the value is kept on its maximum. This package is not present in SCI tickets, FAU tickets and TFS tickets. C) Operating remarks The inclusion of this package in the AMA ticket is controlled via command ENTR CDTDAT: EXTNSD = ACCURCHG;

172

P30308-X2058-K160-03-7617

Data Field Description

D) Postprocessing remarks The package has a fixed length of 7 bytes. The package length is included on byte 2 in the package itself. [Link] Package 211: Additional Release Cause A) Syntax description
Field No 1 2 3 Byte Pos. 1 2 3
Length

(bytes) 1 1 n

Field Name 7 6 5 4 Package Number Package Length Subpackages

Remarks 3 2 1 0 binary; fixed value 211 (HD3) binary; total length of package refer to description of the subpackages

1. Subpackage Call Result

Field No +1 +2 +3 Byte Pos. +1 +2 +3
Length

(bytes) 1 1 1

Field Name 7 6 5 3 4 Subpackage Number Subpackage Length Call Result

Remarks 2 1 0 binary; fixed value 1 (H01) binary; total length of subpackage binary; see table below

Call Result Value 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Meaning Not further specified Call Result Successful, answered call Congestion Subscriber busy No answer from subscriber Inter-digit time ended Incomplete dialling Call released at own switch because of Trunk Reservation at last route Call released at own switch because of Leaky Bucket or Call Gapping Call released at own switch because of Skip or Cancel To at last route Call released at own switch because of internal overload Call released at own switch because of Automatic Congestion Control Call released at foreign switch because of All Trunks Busy or other congestion reasons Seizure with no dial Special incomplete dialling Not applicable Not applicable Not applicable Not applicable Unsuccessful SCI Successful SCI Not applicable

P30308-X2058-K160-03-7617

173

Data Field Description

2. Subpackage Media Gateway Result

Field No +1 +2 +3 Byte Pos. +1 +2 +3
Length

(bytes) 1 1 2

Field Name 7 6 5 3 4 Subpackage Number Subpackage Length Media Gateway Result

Remarks 2 1 0 binary; fixed value 2 (H02) binary; total length of subpackage binary; see table below

Media Gateway Result Value 0 400 401 402 403 406 410 411 412 421 422 430 431 432 433 440 441 442 443 444 445 446 447 448 450 451 452 453 454 455 456 471 500 501 502 Meaning Success Bad Request Protocol Error Unauthorized Syntax Error in Transaction Version Not Supported Incorrect identifier The transaction refers to an unknown Context ID No Context IDs available Unknown action or illegal combination of actions Syntax Error in Action Unknown Termination ID No Termination ID matched a wildcard Out of Termination IDs or No Termination ID available Termination ID is already in a Context Unsupported or unknown Package Missing Remote Descriptor Syntax Error in Command Unsupported or Unknown Command Unsupported or Unknown Descriptor Unsupported or Unknown Property Unsupported or Unknown Parameter Descriptor not legal in this command Descriptor appears twice in a command No such property in this package No such event in this package No such signal in this package No such statistic in this package No such parameter value in this package Parameter illegal in this Descriptor Parameter or Property appears twice in this Descriptor Implied Add for Multiplex failure Internal Gateway Error Not Implemented Not ready

174

P30308-X2058-K160-03-7617

Data Field Description

Media Gateway Result Value 503 504 505 510 512 513 514 515 517 518 519 520 521 526 529 530 531 581 1000 1001 1002 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 Meaning Service Unavailable Command Received from unauthorized entity Command Received before Restart Response Insufficient resources Media Gateway unequipped to detect requested Event Media Gateway unequipped to generate requested Signals Media Gateway cannot send the specified announcement Unsupported Media Type Unsupported or invalid mode Event buffer full Out of space to store digit map Media Gateway does not have a digit map Termination is "Service Changing" Insufficient bandwidth Internal hardware failure Temporary Network failure Permanent Network failure Does not exist Endpoint redirected to another Call Agent CAS signaling protocol error Failure of a grouping of trunks (e.g. facility failure) MG Not Known MCU Protocol Error MG Protocol Error PCU Tag Mismatch MG Timeout Invalid Transition PM SW Error PM Resource Error Invalid LTG Invalid Port ID Invalid MG Index Invalid MG Name Invalid Endpoint ID Invalid PCM Type Invalid Protocol PM General Error PM Prev. Path Conn. Failure PM MG Out of Service MG Transaction Already in Progress

P30308-X2058-K160-03-7617

175

Data Field Description

B) Functional description The Call Result provides some specific information about the status of the call, which can not be derived from the package 130 (Traffic Quality Data). Remarks: The value 19 (Unsuccessful SCI) is in fact not relevant for AMA, since AMA tickets are only generated for successful SCI. The value 19 can only be present, when the Call Result is generated in tickets for other applications (Traffic Structure Measurement and Directory Number Observation). The values 7, 8, 9 and 11 are related to Network Management Controls. If the control Cancel To is created on an outgoing or bothway trunk group, a certain percentage of the traffic to this trunk group is prohibited. The control Skip forces a percentage of the traffic to overflow to another trunk group. Leaky Bucket reduces traffic according an administrable throughput rate of calls; reduction takes only place if a certain threshold of calls is exceeded in a given time interval. The Call Gapping control mechanism reduces the traffic to a destination time based. The Automatic Congestion Control (ACC) mechanism enables an exchange to reduce traffic to a congested neighbouring exchange. The traffic is reduced based on two congestion levels sent in the ISUP release message backwards from the congested exchange. Trunk Reservation reserves a number of trunks for traffic, which fulfills certain criteria. The value 3 (Subscriber busy) corresponds to Cause 17 (User Busy). Value 4 (No answer from subscriber) corresponds to the Causes 18 (No user responding), 19 (No answer from user) or 20 (Subscriber absent), but there are some additional cases where value 4 is registered. When e.g. the call is abandoned during ringing, the Cause will be 16 (Normal Call Clearing), but the Call Result will be 4 (No Answer). The value 5 indicates that the call is released by the calling subscriber before the B-party was reached, but after the routing logic in the CP has been run through. Value 14 (Special incomplete dialling) is registered when at least one digit has been dialled (when no digit is dialled, value 13 is registered), but the call is released before even the routing logic in the CP has been run through. It is possible that Flag F33 in the Fixed Part indicates that the call is answered, while the Call Result indicated No Answer. The reason therefore is the fact that a call can be composed out of several, more or less independent parts. An example is an IN call, where the calling line can reach different destinations without going on hook. In the AMA ticket, the Flag F33 will be set as soon as an Answer signal has been received. The Call Result refers however to the last call part. When during an IN call, the first destination could be successfully reached, but the second destination not, Flag F33 will indicate Answer and the Call Result No Answer. The Media Gateway Result provides detailed information for an VoIP call, which is unsuccessful due to errors detected in the MG (Media Gateway) or the PM (Packet Manager). This information can only be present in a SURPASS configuration. In such a configuration, the call processing, including the generation of AMA records, is performed by the Call Feature Server.

176

P30308-X2058-K160-03-7617

Data Field Description

C) Operating remarks The inclusion of package 211 in the AMA ticket is controlled via following commands ENTR CDTDAT: EXTNSD = ADDRELC; D) Postprocessing remarks This package has a variable length. The length in bytes is stored on byte 2 of the package. In the AMA ticket, only the subpackage Call Result can be present. The package is only provided at the end of the call, i.e. in the single or last ticket of the call. 5.1.3 Project Specific Data Packages

[Link] Package 117: Project Specific Data A) Syntax description

Field No 1 2 3 Byte Pos 1 2 3
Length

(bytes) 1 1 n

Field Name 7 6 5 4 Package Number Package Length Data

Remarks 3 2 1 0 binary; fixed value 117 (H75) binary; total length of package binary; max. 32 bytes

B) Functional description This package is used to collect charging information for late features, i.e. features that are implemented for one specific project for one specific exchange version, after the common functionality of this exchange version has been fixed. At most 32 bytes of data can be contained in this package. C) Operating remarks This package is not administrable. When the LTG (the peripheral processor) provides project specific charging data, these will be transparently taken over into the AMA ticket. D) Postprocessing remarks The collection of this package is project specific, and thus, the package is collected only if agreed upon between the customer and Siemens AG. The total package length (in bytes) is located at the second byte of the package.

P30308-X2058-K160-03-7617

177

Data Field Description

[Link] Package 140: Incoming Route ID A) Syntax description

Field No 1 2 3 4 Byte Pos 1 2 3 4
Length

(bytes) 1 1 1 n

Field Name 7 6 5 4 Package Number Package Length Reserve F4 F3

Remarks 3 2 1 0

binary; fixed value 140 (H8C) binary; total length of package F2 F1 Route binary; refer to description of field Indication Route Indication Incoming Route ID Subpackages refer to description

Description of Field No 3:
Route Indication Value 0 1 2 3 Meaning National Route Transit Route Terminating Route No Indication

Flags Flag F1 F2 F3 F4 Value Meaning 0 1 0 1 0 1 0 1 Trunk Group Name / Exchange ID not valid Trunk Group Name / Exchange ID valid Trunk Group Line / Customer ID not valid Trunk Group Line / Customer ID valid Previous Operator Name not valid Previous Operator Name valid Customer Info not valid Customer Info valid

The flags F1, F2, F3 and F4 are validity indicators: they indicate whether the optional subpackages for Trunk Group Name/Exchange ID, Trunk Group Line/Customer ID, Previous Operator Name and Customer Info are present or not. Remark that the subpackages in the ticket appear in the same order as the validity indicators (the order of the validity indicators is according to their bit position). Example: When flag F1 (Trunk Group Name/Exchange ID) and flag F3 (Previous Operator Name) are set, first the Trunk Group Name/Exchange ID subpackage will appear in the ticket, followed by the Previous Operator Name subpackage. The Trunk Group Name, Exchange ID and Trunk Group Line have a fixed length. The previous Operator Name has a variable length, indicated by the Length of Previous Operator Name (maximum 16 characters).

178

P30308-X2058-K160-03-7617

Data Field Description

Description of Field No 4: 1. Subpackage Trunk Group Name / Exchange ID

Field No +1 Byte Pos +1 Field Name 3 2 1 0 6 5 (bytes) 7 4 6 Trunk Group Name or Exchange ID
Length

Remarks Character, max. 6

2. Subpackage Trunk Group Line / Customer ID

Field No +1 Byte Pos +1 Length Field Name 3 2 1 6 5 (bytes) 7 4 2 Trunk Group Line or Customer ID Remarks 0 binary; range 0 - 65535

3. Subpackage Previous Operator Name

Field No +1 +2 Byte Pos +1 +2 Length (bytes) 1 n Field Name 3 2 7 6 5 4 Length of Subpackage Previous Operator Name Remarks 1 0 Binary Character, max. 16

4. Subpackage Customer Info

Field No +1 +2 +3 Byte Pos +1 +2 +3
Length

(bytes) 1 1 2

Field Name 3 2 7 6 5 4 Length of Subpackage n.a res res SB NC IC Customer Number

Remarks 1 0 Binary CZ CR Binary Binary, range 0 - 65535

Description of Field No 2 of subpackage Customer Info:

Flags Flag CR CZ IC NC SB res/n.a. Value Meaning 0 1 0 1 0 1 0 1 0 1 Customer Routing not valid Customer Routing valid Customer Zoning not valid Customer Zoning valid International Carrier Routing not valid International Carrier valid National Carrier not valid National Carrier valid Suppress Code Blocking not valid Suppress Code Blocking valid Reserved / not applicable

B) Functional description This package contains an identification (by means of trunk identification / exchange ID / customer ID / previous operator name) of the exchange where the call entered the own network. The contents of this package are project specific, i.e. the contents of the subpackages 1, 2, 3 and 4 and the presence of each subpackage is defined project specifically. Project specific signalling of the information between exchanges is a prerequisite. The subpackage 4 (Customer Info) is specific for Interadministration charging, and thus only relevant in case the CDR feature is active.
P30308-X2058-K160-03-7617 179

Data Field Description

C) Operating remarks This package is not administrable. When the LTG (the peripheral processor) provides the Incoming Route Identification, this will be transparently taken over into the AMA ticket. D) Postprocessing remarks The collection of this package is project specific, and thus, the package is collected only if agreed upon between the customer and Siemens AG. The total package length (in bytes) is located at the second byte of the package. [Link] Package 141: Outgoing Route ID A) Syntax description
Field No 1 2 3 4 5 Byte Pos 1 2 3 4 10
Length

(bytes) 1 1 1 6 2

Field Name 7 6 5 4 Package Number Package Length Reserved Trunk Group Name Trunk Group Line

Remarks 3 2 1 0 binary; fixed value 141 (H8D) binary; total length of package Route binary; refer to description of field Indication Route Indication char, max. 6 binary; range 0 - 65535

Description of Field No 3:
Route Indication Value 0 1 2 3 Meaning National Route Transit Route Terminating Route No Indication

B) Functional description The package Outgoing Route Identification contains the identification of the trunk (connected to another administration / carrier) where the call leaves the own network. This outgoing trunk can be connected to another exchange than the one where the AMA tickets are generated. Project specific signalling of the information between exchanges is imperative.

C) Operating remarks This package is not administrable. When the LTG (the peripheral processor) provides the Outgoing Route Identification, this will be transparently taken over into the AMA ticket. D) Postprocessing remarks The collection of this package is project specific, and thus, the package is collected only if agreed upon between the customer and Siemens AG. The total package length (in bytes) is located at the second byte of the package.

180

P30308-X2058-K160-03-7617

Data Field Description

[Link] Package 176: ITU Calling Party Category A) Syntax description

Field No 1 2 3 Byte Pos 1 2 3
Length

(bytes) 1 1 1

Field Name 3 2 7 6 5 4 Package Number Package Length ITU Calling Party Category

Remarks 1 0 binary; fixed value 176 (HB0) binary, fixed value 3 (H03) binary

Description of Field No 3:
ITU Calling Party Category Value 0 1 2 3 4 5 6-8 9 10 11 12 13 14 15 16-223 224-254 255 Meaning Calling partys category unknown Operator, language French Operator, language English Operator, language German Operator, language Russian Operator, language Spanish reserved Operator with trunk offering Ordinary calling subscriber Calling subscriber with priority Data call Test call reserved Payphone reserved reserved for national use reserved

B) Functional description The package contains a one-byte value, which contains the calling party category as specified for the national signalling. The value set is project specific. C) Operating remarks This package is not administrable. When the LTG (the peripheral processor) provides the ITU Calling Party Category, this will be transparently taken over into the AMA ticket. D) Postprocessing remarks The collection of this package is project specific, and thus, the package is collected only if agreed upon between the customer and Siemens AG. The package has a fixed length of 3 bytes. The package length is included on byte 2 in the package itself.

P30308-X2058-K160-03-7617

181

Data Field Description

[Link] Package 177: Project Specific Service A) Syntax description

Field No 1 2 3 4 Byte Pos 1 2 3 4
Length

(bytes) 1 1 1 1

Field Name 7 6 5 4 Package Number Package Length Tele Service Bearer Capability

Remarks 3 2 1 0 binary; fixed value 177 (HB1) binary, fixed value 4 (H04) binary; refer to description field binary; refer to description field

Description of Field No 3:
Teleservice Value 0 1 2 3 4 5 6 7 Meaning not applicable telephony 3.1 kHz teleservice telephony 7 kHz teleservice telefax 4 teleservice teletex teleservice videotex teleservice mixed mode teleservice video telephony teleservice

Description of Field No 4:
Bearer Service Value 1 2 3 4 5 6 7 8 9 10 Meaning circuit mode, 64kbps unrestricted, 8 kHz structured bearer service category circuit mode, 64kbps, 8 kHz structured bearer service category for speech circuit mode, 64kbps, 8 kHz structured bearer service category for 3.1kHz audio package mode, ISDN virtual call and permanent virtual circuit bearer services provided by the B-channel of the user user signalling bearer service circuit mode, 64kbps unrestricted digital information with tone or announcement (7khz audio), 8 kHz structured bearer service category circuit mode, 2x64kbps unrestricted, 8 kHz structured bearer service category circuit mode, 384kbps unrestricted, 8 kHz structured bearer service category circuit mode, 1536kbps unrestricted, 8 kHz structured bearer service category circuit mode, 1920kbps unrestricted, 8 kHz structured bearer service category

B) Functional description The package contains a project specific definition of the Service. The package is only relevant when the AMA ticket is generated for an ISDN subscriber. C) Operating remarks This package is not administrable. When the LTG (the peripheral processor) provides the project specific service, this will be transparently taken over into the AMA ticket.

182

P30308-X2058-K160-03-7617

Data Field Description

D) Postprocessing remarks The collection of this package is project specific, and thus, the package is collected only if agreed upon between the customer and Siemens AG. The package has a fixed length of 4 bytes. The package length is included on byte 2 in the package itself. [Link] Package 181: Internet Session Info A) Syntax description
Field No 1 2 3 Byte Pos 1 2 3
Length

(bytes) 1 1 n

Field Name 3 2 1 7 6 5 4 Package Number Package Length Internet Session Subpackages

Remarks 0 binary; fixed value 181 (HB5) binary; total length of package binary; max. 46 bytes filled up with subpackages

1. Subpackage Account Status

Field No +1 +2 +3 Byte Pos 1 2 3 Length (bytes) 1 1 1 Field Name 3 7 6 5 4 Subpackage Number Subpackage Length Account Status Remarks 2 1 0 binary; fixed value 40 (H28) binary; total length of subpackage binary; refer to description of Account Status

Description of Field No +3:

Account Status Value 0 1 2 3 4-6 7 8 9-255 Meaning reserved Start Stop Interim update reserved Accounting on Accounting off Reserved

2. Subpackage Session ID
Field No +1 +2 +3 Byte Pos 1 2 3
Length

(bytes) 1 1 5

Field Name 7 6 5 3 4 Subpackage Number Subpackage Length Session ID

Remarks 2 1 0 binary; fixed value 44 (H2C) binary; total length of subpackage characters

P30308-X2058-K160-03-7617

183

Data Field Description

3. Subpackage Session Duration

Field No +1 +2 +3 Byte Pos 1 2 3 Length (bytes) 1 1 4 Field Name 7 6 5 3 4 Subpackage Number Subpackage Length Duration Remarks 2 1 0 binary; fixed value 46 (H2E) binary; total length of subpackage binary

4. Subpackage Incoming IP Packages

Field No +1 +2 +3 Byte Pos 1 2 3
Length

(bytes) 1 1 4

Field Name 7 6 5 3 4 Subpackage Number Subpackage Length Number Of Packages

Remarks 2 1 0 binary; fixed value 47 (H2F) binary; total length of subpackage binary

5. Subpackage Outgoing IP Packages

Field No +1 +2 +3 Byte Pos 1 2 3 Length (bytes) 1 1 4 Field Name 7 6 5 3 4 Subpackage Number Subpackage Length Number of Packages Remarks 2 1 0 binary; fixed value 48 (H30) binary; total length of subpackage binary

6. Subpackage Terminate Cause

Field No +1 +2 +3 Byte Pos 1 2 3 Length (bytes) 1 1 1 Field Name 7 6 5 3 4 Subpackage Number Subpackage Length Terminate Cause Remarks 2 1 0 binary; fixed value 49 (H31) binary; total length of subpackage binary; refer to description of Terminate Cause

184

P30308-X2058-K160-03-7617

Data Field Description

Description of Field No +3:

Account Status Value 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19-255 Meaning Reserved user request lost carrier lost service idle timeout session timeout administrative reset administrative reboot port error Network Access Server error Network Access Server request Network Access Server reboot port unneeded port preempted port suspended service unavailable Callback user error host request Reserved

7. Subpackage Originating IP Address

Field No +1 +2 +3 Byte Pos 1 2 3
Length

(bytes) 1 1 4

Field Name 7 6 5 3 4 Subpackage Number Subpackage Length Originating IP Address

Remarks 2 1 0 binary; fixed value 8 (H8) binary; total length of subpackage binary

B) Functional description This package is provided in case of Internet Volume Charging in the Low Bit Rate Internet AMA tickets. The package contains data relating to the Internet session. The subpackage Session Duration has an accuracy of 1 second. This implies that a duration of 0 seconds is possible, in exceptional cases. C) Operating remarks The inclusion of this package in the ticket cannot be administered. D) Postprocessing remarks The collection of this package is project specific, and thus, the package is collected only if agreed upon between the customer and Siemens AG. The total package length (in byte) is located at the second byte of the package. The package is only provided at the end of the call, i.e. in the single or last ticket of the call.

P30308-X2058-K160-03-7617

185

Data Field Description

5.2 Date Time Change Record

A) Syntax description
Field No. 1 2 3 4 5 6 7 Byte Pos 1 2-7 8 9 10 11 12 - 32
Length

(bytes) 1 6 1 1 1 1 21

Field Name Record Identifier Date / Time Correction Reason Correction Sign Delta Seconds Delta Minutes Reserved

Remarks binary; fixed value 1 binary binary binary binary binary

Description of Field No 1: Record Identifier This field identifies the type of AMA Record. In case of "Date-Time Change Record", the value is 1. Description of Field No 2: Date / Time
new Date / Time Bit Position Byte 1 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Bit 7 Bits 0-6 Bits 0-7 Bits 0-7 Bits 0-7 Bits 0-7 Bits 0-7 Meaning time secure year month day hour minutes seconds (0 = yes, 1=no) right aligned right aligned right aligned right aligned right aligned right aligned binary binary binary binary binary binary value range 0-99 value range 1-12 value range 1-31 value range 0-23 value range 0-59 value range 0-59

Description of Field No 3: Correction Reason

Correction Reason of date/time correction Value 0 1 2 Meaning Correct time Adjust time of the exchange processor clock Correct season Switch from/to daylight saving time Enter time Set the exchange processor clock to an initial value

Description of Field No 4: Correction Sign

Correction Sign for direction of date/time correction Value 0 1 2 Meaning none plus (forward) minus (backward)

186

P30308-X2058-K160-03-7617

Data Field Description

Description of Field No 5: Delta Seconds

Delta Seconds Value Meaning 0-59 Adjustment in seconds of the exchange processor clock after a "correct time" command (via MML-command MOD TIME). The value is zero if the correction reason is "enter time"

Description of Field No 6: Delta Minutes

Delta Minutes Value Meaning 0-120 Adjustment in minutes of the exchange processor clock after a "corr season" command (via MML-command MOD TIME). The value is zero if the correction reason is "enter time"

B) Functional description This record is generated when the time in the exchange is changed due to time correction (i.e. seconds), or daylight savings time correction (i.e. minutes). Time changes are done with the MML-command MOD TIME. Remark: If minutes and seconds are changed in one MML-command, two records are generated: one for the minutes change and one for the seconds change. C) Operating remarks The inclusion of this package in the AMA file is controlled via command ACT IAOPT: SPREC = DTC; D) Postprocessing remarks This package has a fixed length of 32 bytes. The package length is not included in the package itself.

5.3 Overflow Record

A) Syntax description
Field No. 1 2 3 4 5 Byte Pos 1 2-7 8 - 13 14 - 17 18 - 32
Length

(bytes) 1 6 6 4 15

Field Name Record Identifier Date Time Of Overflow Start Date Time Of Overflow End Number Of Lost Records Reserved

Remarks binary; fixed value 3 binary binary binary binary

Description of Field No 1: Record Identifier This field identifies the type of AMA Record. In case of "Overflow Record", the value is 3. Description of Field No 2 and 3: Date / Time of Overflow Start / End Refer to 5.2, Date Time Change Record, description of Field No 2.

P30308-X2058-K160-03-7617

187

Data Field Description

Description of Field No 4: Number of Lost Records

Number of Lost Records Value Meaning 0 - H7FFFFFFF Each time an AMA record is lost because of lack of buffer memory, the counter "Number of lost Records" is incremented.

B) Functional description This record is generated in case generated AMA records can not be buffered because the buffers are full (e.g. because the disk is not available). As soon as the buffers become available again, the generated Overflow record is buffered itself. C) Operating remarks The inclusion of this package in the AMA file is controlled via command ACT IAOPT: SPREC = OVF; D) Postprocessing remarks This package has a fixed length of 32 bytes. The package length is not included in the package itself.

5.4 Breakdown Record

A) Syntax description
Field No. 1 2 3 4 5 Byte Pos 1 2-7 8 - 13 14 15 - 32
Length

(bytes) 1 6 6 1 18

Field Name Record Identifier Reserved Date Time Of Recovery Recovery Level Reserved

Remarks binary; fixed value 2 binary binary binary binary

Description of Field No 1: Record Identifier This field identifies the type of AMA Record. In case of "Breakdown Record", the value is 2. Description of Field No 3: Date / Time of Recovery Refer to 5.2, Date Time Change Record, description of Field No 2. Description of Field No 4: Recovery Level
Recovery Level Value Meaning 0 not used 1 Recovery level 1_1 2 Recovery level 1_2 3 Recovery level 1_3 4 Recovery level 2_1 5 Recovery level 2_2

188

P30308-X2058-K160-03-7617

Data Field Description

B) Functional description This record is generated in case a recovery takes place in the exchange. C) Operating remarks The inclusion of this package in the AMA file is controlled via command ACT IAOPT: SPREC = BRD; D) Postprocessing remarks This package has a fixed length of 32 bytes. The package length is not included in the package itself.

5.5 Filler Records

Format of Filler Records to fill one or two bytes:
Field Byte No. Pos 1 1
Length Field Name (bytes) 1 Record Identifier

Remarks binary; fixed value 128 = H80

Format of Filler Records to fill more than two bytes:

Field No. 1 2 3 Byte Pos 1 2-3 4 Length (bytes) 1 2 n Field Name Record Identifier Record Length (N + 3) Filler Bytes Remarks binary; fixed value 129 = H81 binary value 0

Format of Filler Records to fill 32 bytes:

Field No. 1 2 Byte Pos 1 2-32 Length Field Name (bytes) 1 Record Identifier 31 Filler Bytes Remarks binary; fixed value 0 = H00 value 0

Description of Field Filler Bytes In the Filler record to fill more than 2 bytes (RID=129) and to fill 32 bytes, the FILLER BYTES contain the value 0. The maximum record length is the rest of 2, 4 or 8 Kbytes, according to the parameter FILRECSZ in the ACT IAFEAT command, because each data block contains at least one connection ticket or FAU ticket or SCI ticket or TFS ticket or Date Time Change record or Overflow record or Breakdown record. 32 bytes filler records (Record Identifier = 0) are used to fill up a data block when the area to be filled up equals 32 bytes or is a multiple of 32 bytes. In the other cases the filler byte records with Record Identifier 128 or 129 are used.

P30308-X2058-K160-03-7617

189

Operation Notes

6 Operation Notes
6.1 Operating instructions for activating the AMA feature
With the MML-command
ACT IAFEAT: TYPE = AMA, SIZE =

<size of cyclic file [Link]>, FILRECSZ = <size of file record>;

the AMA-feature is activated, i.e. buffers are created in main memory the cyclic file [Link] is created on disk For a detailed description of buffer handling and cyclic file handling in the exchange, refer to /10/. With the MML-command
CAN IAFEAT: TYPE = AMA;

the AMA feature is deactivated, that means tickets are no longer buffered and the cyclic file [Link] is closed. Remarks: Deactivation and re-activation do not affect the copy area (the area which has been transferred and not yet released, refer to /10/ for detailed information). The cyclic file is not deleted at feature deactivation. When the AMA feature is activated again, and the cyclic file [Link] is already present, the file is re-opened.

6.2 Operating instructions for customizing the AMA ticket

With the MML-command
ENTR CDTDAT: REC = AMA, EXTNSD =

<extra data>, ALTNSD = <alternative data>;

the contents of the AMA-ticket can be controlled (the control function of ENTR CDTDAT for other kinds of tickets is not considered). Extra Data The parameter EXTNSD controls the inclusion of additional packages in the AMA ticket. The following table gives an overview of all possibilities. Remark however that in many cases, there are additional criteria for the presence of a package in the AMA ticket. Refer to Chapter 4.1 for an overview, and to Chapter 5.1.2 for a detailed description of all additional criteria.
Parameter EXTNSD ACCURCHG ADDCLGDN ADDRELC ADDTAR ADVCUMCH BGID BMETPULS Controlled Packages package 209 (Accumulated Currency Charges) package 159 (Additional Calling Party Number) package 211 (Additional Release Cause) package 155 (Add On Tariff) package 156 (Advised Cumulated Charges) package 151 (Business Group Identification) package 138 (B Meter Pulses)

P30308-X2058-K160-03-7617

191

Operation Notes

CAC

CALLIND CALLTAR CATRCVD CATSENT CHARGES

CHECKSUM CLDRCVD CLDSENT CLGSENT CONNID CTXNO DEFMSN DLUV52 DURBANS EXCHNAME FAUNONCH FAUPRTNR GCR INSERVK MLPP NEWDEST OCLGDN OPMODE PATHSEL PBXOPN

PFXNATIN PORTADR RECOWNER RECTRID

REDSENT REFINDUR RELIND 192

package 145 (Billing CAC) package 148 (CAC New Destination) package 183 (Sent CAC) package 187 (Received CAC) package 154 (Additional Call Indicators) package 147 (Tariff Info) package 195 (Original Calling Party Category) package 194 (Sent Calling Party Category) package 103 (Charge Units for Connection) package 104 (Charge Units for Facility Usage) package 122 (Zone) package 135 (Chargeband) checksum values in package 150 (Audit Trail) package 153 (Received Called Party Number) package 187 (Received CAC) package 171 (Sent Called Party Number) package 183 (Sent CAC) package 192 (Sent Calling Party Number) package 110 (Connection Identification) package 152 (Centrex Numbers) Default MSN in package 167 (Additional Numbers) subpackages 3 and 4 in package 204 (Access Data) package 134 (Durations Before Answer) Exchange Name in package 178 (Exchange Info) package 205 (Non Charged Facilities Used by Owner) package 112 (Facilities Used by Partner) package 149 (Global Call Reference) package 186 (IN Service Key) package 184 (MLPP Level) package 128 (New Destination) package 142 (Calling Party Number) subpackage 2 in package 204 (Access Data) subpackage 6 in package 204 (Access Data) PBX Operator Number in package 167 (Additional Numbers), and in package 157 (Outgoing PA Identification) on condition the presence of package 157 is already triggered with RECTRID Record Owner DN with national/international Prefix digits included (Only in combination with RECOWNER) subpackage 5 in package 204 (Access Data) Record Owner DN in Fixed Part (Header) package 101 (Partner Directory Number) package 157 (Outgoing PA Identification) and [(package 105 (Trunk Identification Incoming) and package 106 (Trunk Identification Outgoing)) or (package 107 (Trunk Identification Incoming in CIC Format) and package 108 (Trunk Identification Outgoing in CIC Format))] package 193 (Sent Redirecting Number) package 198 (Duration in 100 msec) and package 116 (Date / Time) instead of package 100 (Date / Time / Duration) package 139 (Release Indication) P30308-X2058-K160-03-7617

Operation Notes

SEQUENCE SERVINFO SPC SSN TERMTYPE THRDPRTY TRAFQUAL VERSID

Sequence Number in package 150 (Audit Trail) Package 102 (Service Info) package 191 (Signalling Point Code) package 179 (Service Subscriber Number) subpackage 1 in package 204 (Access Data) package 146 (Third Party Number) package 130 (Traffic Quality Data) Version ID in package 178 (Exchange Info)

Table 21: Overview of EXTNSD values and the controlled packages Remarks: CAC (Carrier Access Code), CONNID (Connection Identification), FAUPRTNR (Facilities used by Partner) and TRAFQUAL (Traffic Quality Data) are set by default, i.e. without explicit activation of these packages with ENTR CDTDAT, these packages are collected. The presence of the package 148 (CAC New Destination) depends on two settings: EXTNSD = CAC and EXTNSD = NEWDEST. The presence of the packages 183 (Sent CAC) and 187 (Received CAC) depend on two settings: EXTNSD = CAC and EXTNSD = CLDSET respectively CLDRCVD. Alternative Data The parameter ALTNSD controls the appearance of alternative data in the AMA ticket. There are following possibilities:
Parameter ALTNSD CACTYPE Controlled Packages The CAC Type in package 145 (Billing CAC) is provided with the value range as defined in former versions. The new values are mapped on the old range as described in the package. Exchange ID Number in package 178 (Exchange Info) instead of Exchange ID Name. If no Exchange ID Number is present, the Exchange ID Name is provided. Package 145 (Billing CAC) is generated with the own CAC if no other CAC was valid. Begin data/time in package 100 (Date / Time / Duration) instead of end date/time. Package 107 (Trunk Identification Incoming in CIC Format) and package 108 (Trunk Identification Outgoing in CIC Format) instead of package 105 (Trunk Identification Incoming) and package 106 (Trunk Identification Outgoing), however only when the CIC format is relevant for the trunk group. . Package 196 (Trunk Info) instead of packages 105, 106, 107 and 108 Second trunk group identification (according to parameter TGN2 in the CR TGRP command) instead of first trunk group identification (according to parameter TGNO in the CR TGRP command) in the package 105 (Trunk Identification Incoming), package 106 (Trunk Identification Outgoing), package 107 (Trunk Identification Incoming in CIC Format) and package 108 (Trunk Identification Outgoing in CIC Format).

EXCHIDNO OWNCAC RANSWTIM RECTRCIC

TGNA TGN2

Table 22: Overview of ALTNSD values and the controlled packages

P30308-X2058-K160-03-7617

193

Operation Notes

6.3 Operating instructions for controlling the generation of AMA-tickets

Following flags control the generation of AMA-tickets AMA for unsuccessful calls This flag is set with the MML-command
ENTR CDTDAT: MARKS = UCALLAMA;

or
MOD CHRGFEA: DN =

<dn>, LAC = <lac>, COS = UCALLAMA

If this flag is set and charging has to be done with AMA, an AMA ticket will be generated, independent whether the call is answered or not, and independent whether call attempt charges have been administered or not. Remarks: If the flag is not set, AMA tickets for unanswered calls are generated, in case the call attempt criteria are fulfilled (see further) and the call attempts have been administered as chargeable. Under these circumstances, AMA tickets are generated even when the charge status has been determined on no charge. the call attempt criteria are fulfilled, call attempts have not been administered as chargeable, but the flag AMA for charge free call attempts is set (see further). The check whether call attempt criteria are fulfilled is project specific. Decision criteria are the call progress (e.g. whether or not a destination has been reached) the port type of the calling line (an APS parameter controls whether call attempt charging is only relevant for analog subscriber, only relevant for ISDN subscriber, relevant for both, or not relevant at all) the cause of the call release (e.g. all trunk busy is not considered as call attempt) Making the call attempts chargeable is done via the parameters PLSATT (call attempt charges in pulse format) or CNYATT (call attempt charges in currency format) in the ENTR TAR command This flag is not relevant for DEB tickets. AMA tickets for unsuccessful calls are only generated after the call has been set up (AMA is determined during analysis of the called party digits), unless an APS-parameter is set, which triggers the generation of an AMA ticket as soon one digit is received. AMA for charge free call attempts This flag is set with the MML-command
ENTR CDTDAT: MARKS = ATTNOCHA;

This flag triggers the generation of AMA tickets when: during the setup of the call, it has been determined that the charging has to be done with AMA, the call attempt criteria are fulfilled, but the call attempts are not administered as chargeable Remarks: In contradiction to the flag UCALLAMA, this flag is relevant for DEB. AMA Immediate Output for Subscriber Facility Input
194 P30308-X2058-K160-03-7617

Operation Notes

This flag is set with the MML-command

ENTR CDTDAT: MARKS = AMASFAI;

When this flag is set, the AMA immediate Output (AMAIO) feature does not only apply to Connection tickets but also to SCI tickets. When a subscriber has the AMAIO feature, the Connection tickets as well as the SCI tickets are immediately displayed at the OMT (Operation and Maintenance Terminal) as soon as they are generated. This control is not applicable for Hot Billing. Centrex FAU Charging This flag is set with the MML-command
ENTR CDTDAT: MARKS = CTXFAU;

When this flag is set, the Facility Usage charging concept also applies for Centrex subscribers. When this flag is set, chargeable FAUs used by a Centrex subscriber will be marked in the Connection tickets for this subscriber and/or FAU tickets are generated. Charging of SCI for Centrex This flag is set with the MML-command
ENTR CDTDAT: MARKS = CXSFAICH;

When this flag is set, the SCI charging concept also applies for Centrex subscribers. When this flag is set, SCI tickets will be generated for the Centrex subscriber who makes a chargeable Subscriber Controlled Input. DEB for Facility Input and Usage This flag is set with the MML-command
ENTR CDTDAT: MARKS = DEBFA;

When this flag is set, DEB tickets for Facility Usage and Subscriber Controlled Input are generated for a subscriber with the DEB feature.

P30308-X2058-K160-03-7617

195

Operation Notes

6.4 Hints for the Postprocessing

6.4.1 Identifying the contents of the [Link] file Following records can be present in the [Link] file:
Record ID 0 (H00) 1 (H01) 2 (H02) 3 (H03) 122 (H7A) 123 (H7B) 124 (H7C) 128 (H80) 129 (H81) 132 (H84) Record Length fixed 32 bytes fixed 32 bytes, not stored in the record fixed 32 bytes, not stored in the record fixed 32 bytes, not stored in the record fixed 64 bytes fixed 64 bytes fixed 64 bytes fixed 1 byte variable, located at the second byte variable, located at the second byte variable, located at the second byte 64 + (contents from bit 0 to 6 of byte 46 x 32) 64 + (contents from bit 0 to 6 of byte 46 x 32) 64 + (contents from bit 0 to 6 of byte 46 x 32) Description Filler Record for 32 bytes Date/time Change Record Breakdown Record Overflow Record AMA ADMOSS basic, final AMA ADMOSS basic, single AMA ADMOSS basic, intermediate Filler Record one byte Filler Record to store more than two bytes variable length AMA record for automatic calls, subscriber controlled input, facility usage, and TFS service subscriber variable length AMA record for operator input of facilities AMA ADMOSS extended, final AMA ADMOSS extended, single AMA ADMOSS extended, intermediate

133 (H85) 250 (HFA) 251 (HFB) 252 (HFC)

Table 23: Overview of Record Identifiers Depending on the administration of the switch, some of these records will not be present. When e.g. only AMA for automatic calls is administered (no System Records, no ADMOSS Records, no AMA for operator input of facilities), only the records with record id = 128 (filler 1 byte), 129 (filler more than one byte), and 132 (variable length AMA record) will be present. It is however a safe method to consider all possible values. 6.4.2 Identifying the contents of one variable length AMA record The treatment of Data Packages by the Postprocessing must be designed in such a way that Data Packages which are not used in a project can be rejected as described below. With every future exchange version, new data packages may be introduced because of new AMA related features. New features may be implemented in the exchange common for all projects, although the feature is only required by one or a limited number of projects. Therefore,
196 P30308-X2058-K160-03-7617

Operation Notes

new data packages may be collected in AMA records in a project that does not evaluate these packages in the Postprocessing. To solve this problem of compatibility, new data packages that are project specific and of which the collection can not be activated by MML-commands, are always provided with a length indication stored in byte 2 of the package. In this way, Postprocessing can be designed to reject data packages with a package number not relevant for the project and address a further data package by adding the length stored in byte 2. Remarks : Packages for which the collection is activated by MML are considered to be required in the project. The layout and length of such a package must be considered by Postprocessing. Packages that form a standard part of the ticket (refer to Chapter 4.1) must also be considered by Postprocessing. Such packages can: have no length indication, i.e. the package has a fixed length have the package length written on byte 2 of the package have a length indication on byte 2. In such cases the package length must be calculated according to the formulas listed with the package description. The Chapter 5.1.2 indicates for each package: whether the package has a fixed or a variable length whether the package contains the package length on byte 2 or whether the package length must be calculated.

P30308-X2058-K160-03-7617

197

Operation Notes

6.4.3 Average Record length The average length of the AMA/CDR record depends on the operational settings for the layout of the AMA/CDR record, on the kind of traffic (local, analog, ISDN), on the frequency of using features (Account Code, FAU, etc.). The following table gives some typical examples
Conditions analog subscriber; fixed numbering plan with 7 digits; 7 dialled digits; length of Local Area Code = 3; only standard data registered; no intermediate charging AMA/CDR data Fixed Part: Package 100 Package 110 Package 130 Package 142 Package 168 Total length: ISDN subscriber; fixed numbering plan with 7 digits, 10 dialled digits (area code included); length of Local Area Code = 3; Charge Units and Zone included; no Chargeband received; no intermediate charging Fixed Part Package 100 Package 102 Package 103 Package 110 Package 122 Package 130 Package 142 Package 168 Total length: Analog subscriber; fixed numbering plan with 7 digits; 7 dialled digits; length of Local Area Code = 3; only standard data registered; no intermediate charging, Record Owner DN in Fixed Part (Header)and package 101 (Partner Directory Number) requested Fixed Part Package 100 Package 101 Package 110 Package 130 Package 142 Package 168 Total length: Record length (bytes) 8 11 6 5 9 9 48 8 11 4 4 6 3 5 9 10 60 13 11 6 6 5 9 9 59

Table 24: Examples for AMA Record length

6.5 Delta to Previous Versions

This chapter describes for each exchange version, the changes against the previous version. A distinction is made between new and changed information in the AMA ticket. Changes, which are not downward compatible, are especially marked. Changes are considered as not downward compatible when Postprocessing needs to be changed to access the same information as in the previous version. Extensions of the packages 111 (Facilities Used by Owner), 112 (Facilities Used by Partner) and 113 (Facility Input) with new facility values are available from version 15 on. 6.5.1 Version 6.2 New package 120 (Calling Party Category)

198

P30308-X2058-K160-03-7617

Operation Notes

6.5.2 Version 7.1 New flag AMA FAU in Fixed Part (Header) flag ZONE_ACK in Fixed Part (Header) Changes the total number of FAUs (Owner + Partner) in package 111 (Facilities Used by Owner) and package 112 (Facilities Used by Partner) is incremented from 4 to 8. 6.5.3 Version 8 New package 125 (Account Code) package 130 (Traffic Quality Data) Changes package 122 (Zone): the length of the field Zone is incremented from 1 to 2 not compatible with previous versions: the total length of the package has become 3 bytes instead of 2, and the length of the package is not included in the package itself !. 6.5.4 Version 9 New package 134 (Durations before Answer) package 135 (Chargeband) package 136 (UUS3 Counters) Changes package 130 (Traffic Quality Data): the cause is extended from 7 bits to 2 bytes not compatible with previous versions: the field Location is located on byte 5 instead of byte 4 !. package 110 (Connection Identification Number): the fields Speech Channel and Processor Number are replaced by a 3 byte field without separate components (the total length remains the same) the total number of own FAUs in package 111 (Facilities Used by Owner) and partner FAUs in package 112 (Facilities Used by Partner) is incremented from 8 to 12. new flag FAIS unsuccessful (F28) in Fixed Part (Header) of AMA ticket Call Failure Type is no longer built and replaced by package 130 (Traffic Quality Data) not compatible with previous versions ! 6.5.5 Version 10 Changes package 113 (Facility Input): new flag FAI for all numbers package 135 (Chargeband): new flag Chargeband Message received

P30308-X2058-K160-03-7617

199

Operation Notes

6.5.6 Version 11 New package 142 (DDI number) package 143 (IP/SN Charge Data) package 145 (Billing CAC) package 146 (Third Party Number); this data package is only used for Call Transfer package 147 (Tariff Info) Changes package 110 (Connection Identification Number) field Connection ID is extended from 3 to 4 bytes package is also built for FAI and FAU tickets package 113 (Facility Input): new flag Remote SCI package 125 (Account Code): new flag Dialled account code 6.5.7 Version 12 New package 128 (New Destination) package 142 (Calling Party Number) instead of DDI number package 148 (CAC New Destination) package 149 (Global Call Reference) package 150 (Audit Trail) package 151 (Business Group Identification) package 152 (Centrex Numbers) package 153 (Dialled Digits) package 154 (Additional Call Indicators) package 156 (Advised Cumulated Charges) new flags in Fixed Part (Header): Analog Subscriber (F24) ISDN Subscriber (F25) Sequence Number present (F37) Checksum present (F38) Changes package 130 (Traffic Quality Data): Coding Standard added package 146 (Third Party Number): Additional Info added and collected in more cases not compatible with previous versions ! package 147 (Tariff Info): contents completely changes not compatible with previous versions ! package 100 (Date / Time / Duration): Duration is set on 0 in case the call is not answered package 102 (Service Info): also provided in case of Remote SCI Connection Identification is the same on A- and B-side of the call package 105 (Trunk Identification Incoming), package 106 (Trunk identification Outgoing), package 107 (Trunk Identification Incoming in CIC Format) and package 108 (Trunk Identification Outgoing in CIC Format) are also relevant for DEB

200

P30308-X2058-K160-03-7617

Operation Notes

Administration: following packages can be activated by the craftsperson: package 112 (Facilities used by Partner) package 130 (Traffic Quality Data) package 110 (Connection Identification Number) package 145 (Billing CAC) and package 148 (CAC New Destination) 6.5.8 Version 13A New package 139 (Release Indication) package 155 (Add On Tariff) package 159 (Additional Calling Party Number) package 167 (Additional Numbers) package 168 (Called Party Number) package 170 (Redirecting Number) package 171 (Sent Called Party Number) package 172 (System Provided Number) package 178 (Exchange Info) package 179 (Service Subscriber Number) Changes Fixed Part (Header) New Flag F18 (Record Owner Type) has been introduced 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. Instead of the Record Owner DN, the Record Owner Type is provided The Record Owner Type refers to one of the following numbers (packages): 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 Redirecting Number, in case the AMA tickets are generated for the redirecting party (non-PBX) of a diverted call System Provided Number in case the AMA tickets are generated 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 cases the AMA tickets are generated for the following types of SCIs: Remote SCI, SCI performed for a (/another) target MSN, SCI for all numbers for a subscriber of which the signalled Calling Party Number is not available, e.g. in case of Remote Subscriber Controlled Input, ... in case the AMA tickets are generated for the B-party in the connection (e.g. IP/SN call) or when the B-party uses a chargeable Facility. Called Party Number in case the AMA tickets are generated for a Wake Up call. Service Subscriber Number, in case the AMA tickets are generated for the TFS subscriber. In this case the Service Subscriber Number contains the TFS account number which is generated (project specific) based on the TFS number, an account number prefix and exchange digits.

P30308-X2058-K160-03-7617

201

Operation Notes

Upon request by the craftsperson (by means of ENTR CDTDAT: EXTNSD=RECOWNER), the owner of the AMA ticket (as was defined in <V13A) can be stored in the fixed part of the AMA ticket (fields 5 and following). not compatible with previous versions ! The value 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) initiated by the A-party, the Charge Status in the AMA tickets generated for the A-party indicates no charge. Packages Package 100 (Date / Time / Duration): a new Flag F0 has been introduced This flag is set to 0 for years between 1900 and 1999 and on 1 for years starting from 2000. Package 101 (Partner Directory Number): The presence of the data package is administrable In previous versions, the package 101 was always available. From Version 13A on the presence of this package must be requested by the craftsperson via MML command ENTR CDTDAT: EXTNSD = RECOWNER; Package 116 (Date / Time): a new Flag F0 has been introduced This flag is set on 0 for years between 1900 and 1999 and on 1 for years starting from 2000. Package 128 (New Destination): new layout The field Package Length has been introduced not compatible with previous versions ! The fields NADI and NPI have been added not compatible with previous versions ! Package New Destination is also built in case of TFS In case of TFS calls, this package contains the destination digits determined in the TFS exchange based on the dialled digits. not compatible with previous versions !

Package 142 (Calling Party Number): Presentation Indicator and Screening Indicator Presentation Indicator and Screening Indicator have been introduced. The package contains the LAC Length In CAMA tickets, the LAC Length is always equal to 0, because the number of area code digits is not signalled via trunk. The presence of the package is not administrable, except in case of Call Forwarding and Remote Subscriber Controlled Input In case of Call Forwarding and Remote SCI, the craftsperson must request this package by means of ENTR CDTDAT (EXTNSD=OCLGDN), in order to obtain the original calling party in package 142. In case of Call Forwarding, this package contains the original Calling Party, whereas in versions <V13A, this package contained the redirecting number and the original Calling Party was stored in Data Package 146 (Third Party). In case of Remote SCI, this package contains the DN of the subscriber from where the Remote SCI is performed, whereas in versions <V13A, this DN was stored in Data Package 146 (Third Party). not compatible with previous versions ! The package is not only provided for ISDN PBX, but also for normal analog and ISDN subscribers and analog PBX subscribers. not compatible with previous versions !

202

P30308-X2058-K160-03-7617

Operation Notes

Package 146 (Third Party Number) The fields NADI and NPI have been introduced Nature of Address Indicator and Numbering Plan Indicator have been introduced. not compatible with previous versions ! The package is no longer used to store the Calling Party in case of Call Forwarding and Remote SCI not compatible with previous versions ! Package 152 (Centrex Numbers) Introduction of a new validity bit VA2 To indicate the presence of the Redirecting party intercom number (in case of Call Forwarding) Introduction of the Redirecting Party Intercom Number In case of Call Forwarding, the Redirecting Party Intercom Number is provided, whereas in versions before Version 13A, the Redirecting Party Intercom Number was stored as Calling Party Intercom Number. not compatible with previous versions !

Package 153 (Received Called Party Number) the data package replaces the former data package Dialled Digits with same Package Number the fields NADI and NPI have been introduced not compatible with previous versions ! the data package is also provided in CAMA tickets, where it contains the called party number as has been received via trunk.

Package 154 (Additional Call Indicators) New flag: F15 This flag indicates that the call is set up via Internet. The flag can be set in the local, transit and end exchanges. New flag: F18 This flag indicates that for this call reverse charging (according to ITU-T Q.736 and Q.956) applies. The flag can be set in the local, transit and end exchanges. Extra byte for Flags which are presently reserved (except flags F31, F32, F33 which are valid for the IACAMA records)

Package 156 (Advised Cumulated Charges) Introduction of the flag: F7 This flag indicates whether the Currency Advice of Charge Counter has overflowed or not. Package 117 (Project Specific Data) At most 32 bytes of data can be contained in this package, instead of 10 bytes. 6.5.9 Version 14A New package 119 (Transmission Medium Requirement): only for CDR package 138 (B Meter Pulses) package 182 (Operation Connection Duration): only for CDR package 183 (Sent CAC) package 184 (MLPP Level) package 185 (Kind of Traffic) package 187 (Received CAC)

P30308-X2058-K160-03-7617

203

Operation Notes

Changes In case of Call Transfer, the FAU tickets generated for the usage of the Call Transfer contain a time and a duration; they are not generated anymore at the moment of call transfer, but at the end of the call, respectively at the next intermediate charging after the call transfer. Package 140 (Incoming Route Id): The project specific package has a new layout. In the reserved part of the 3rd field, 3 new validity flags are defined. These flags refer to the presence of subpackages. The new definition makes the project specific use of the package more transparent. Package 145 (Billing CAC) The layout of the package has not changed, but the CAC Type field is redefined not compatible with previous versions ! It is however possible to fall back to the original values of the CAC Type field by means of ALTNSD = CACTYPE in the ENTR CDTDAT command. Package 145 is only built, in case the CAC in this package really identifies the operator, which is responsible for the charging of the call. In former versions, the package was also built under other circumstances, e.g. when a CAC was dialled, but not used. not compatible with previous versions ! Package 148 (CAC New Destination): The layout of this package has changed. The fields CAC Type and Number of Prefix Digits are no longer provided. not compatible with previous versions ! Package 152 (Centrex Numbers): In the reserved part of the 3rd field, an additional validity flag has been defined. The flag indicates if the new optional field for the Access Code is available. Package 153 (Received Called Party Number): The reserved space of the 5th field is now filled out with the number of CAC digits. Package 154 (Additional Call Indicators): The length of this package has been extended to 6 bytes. Package 167 (Additional Numbers): Some spare values of the fields Number Type and Number Qualifier have got a specific definition. Package 171 (Sent Called Party Number): The reserved space of the 5th field is filled with the number of CAC digits. Package 172 (System Provided Number): The Number Type field has changed: Authorization Code Reference Number has been added. The Number Qualifier field has changed: Internet SCI Served User has been added. 6.5.10 Version 15 New package 186 (IN Service Key) package 191 (Signalling Point Code) package 192 (Sent Calling Party Number) package 193 (Sent Redirecting Number)
204 P30308-X2058-K160-03-7617

Operation Notes

package 194 (Sent Calling Party Category) package 195 (Original Calling Party Category) package 196 (Trunk Info) package 198 (Durations in 100 msec) package 199 (Received Charge Determination Information)

Changes The presence of package 102 (Service Info) is administrable with ENTR CDTDAT. The maximum range of the trunk number is enhanced. The value can be up to 16383 (old range was 4095). This change is relevant for the packages 105: Trunk Identification Incoming and the packages 106: Trunk Identification Outgoing. Package 111 (Facilities Used By Owner) has the following new value: 77 = Call diversion immediate on PABX DDI extension (DIVEI) Package 113 (Facility Input) has the following new values: 163 = Subscriber credit limit (SCLIM) 164 = Call diversion immediate on PABX DDI extension (DIVEI) 165 = Screening list for Kick Out (SCLSTKO) Flag F7 (Begin/End date time) in package 116 (Date/Time) relevant in case of refined durations. The Sent and Received CAC are not suppressed anymore when they are equal to the Billing CAC in package 145. Package 147 (Tariff Info) has now also a currency indication, an originator identification, a restart charging indication and a one time charge indication; the subpackage operator data is removed not compatible with previous versions ! New flag in package 148 (CAC New Destination) to mark the New Destination as relevant for routing. New call indicators in package 154 Additional Call Indicators: F27 = Second leg of Dial In call (CTX) F28 = Call from Authorized Subscriber (CTX) F38 = Subscriber under test Package 155 (Add On Tariff) has now also a currency indication and an originator identification; the subpackage operator data is removed not compatible with previous versions ! Package 179 (Service Subscriber) has got a length of 6 bits instead of 5 for the Number of Digits / Number of Bytes Project specific package 140 with the signalled trunk group name in the field "Previous Operator Name". 6.5.11 Version 16 New package 204 (Access Data) package 205 (Non Charged Facilities Used by Owner) package 209 (Accumulated Currency Charges) package 211 (Additional Release Cause)

P30308-X2058-K160-03-7617

205

Operation Notes

Changes Fixed Part (Header) New Flag F27 (Call started before or during RSU Stand Alone Service) has been introduced. Packages The package 100 (Date /Time / Duration) and 116 (Date / Time) contain the tenths of seconds. The package 128 (New Destination) contains the indication TFS or IN call on bit positions which were reserved in earlier versions. The package 154 has been extended with 1 byte, in order to store several additional flags. Following new flags have been introduced: F43: Master to Slave CTX call F44: Call via Master CTX group F45: Fallback occurred F55: Call started during RSU SAS F56: IP Dial in traffic The package 154 is not built anymore, in case none of the relevant bits in this package has the value 1. Package 111 (Facilities Used By Owner) has the following new values: 78 = Yearly alarm call order (YACO) 79 = Announced diversion (DIVANN) 80 = Diversion for logged out (DIVLO) Package 113 (Facility Input) has the following new values: 166 = Yearly alarm call order (YACO) 169 = Announced diversion (DIVANN) 178 = Diversion for logged out (DIVLO) The term Global Charge Reference has been replaced by Global Call Reference throughout the document. The package 149 is called now Global Call Reference. The Global Call Reference in the package 149 (Global Call Reference) has another layout when it is set up by the own exchange. The package 145 (Billing CAC) is also generated for unsuccessful calls. The package 191 (Signalling Point Code) contains the Network Number, on bit positions, which were reserved in earlier versions. A new screening option (NOSCCLS: No Screening of Calling Line Special) has been introduced, which affects the contents of package 142 (Calling Party Number). The parameter AMASGN has been introduced for PBX charging. The package 179 (Service Subscriber Number) is also built in case of SIP-PSTN interworking.

206

P30308-X2058-K160-03-7617

Examples

7 Examples
7.1 Fixed Part (Header)
Fixed Part based on Record Owner Type RECORD IDENTIFIER RECORD LENGTH
FLAGS Variable length AMA Record (132 = H84) 52 = H34 AMA (F13) CONNECTION (F14) ISDN (F25) Single (H01) Charge (H01) Calling Party Number (142 = H8E) Field Name 3 2 4 Contents (hexadecimal) 1 0

RECORD SEQUENCE
CHARGE STATUS RECORD OWNER TYPE Field Byte Length No Pos (bytes) 1 1 1 2 2 2 3 4 3

4 5

7 8

1 1

RECORD IDENTIFIER RECORD LENGTH Reserved F18 F17 F16 F15 F14 F13 F12 F11 n.a. res. n.a. F25 F24 F23 F22 F21 F38 F37 res. F35 F34 F33 n.a. n.a. RECORD SEQ. CHARGE STATUS RECORD OWNER TYPE

Upper half byte 8

3 0 8 1 0 1 8

Lower half byte

4 4 0 C 0 0 1 E

Fixed Part based on Record Owner DN RECORD IDENTIFIER RECORD LENGTH

FLAGS Variable length AMA Record (132 = H84) 75 = H4B AMA (F13) CONNECTION (F14) ISDN (F25) SEQUENCE (F37) CHECKSUM (F38) Single (H01) Charge (H01) 1 8 92449306 Field Name 4 3 2 Contents (hexadecimal) 1 0

RECORD SEQUENCE
CHARGE STATUS LAC LENGTH OWNER ID LENGTH RECORD OWNER Field Byte Length No Pos (bytes) 1 1 1 2 2 2 3 4 3

Upper half byte

8 4 0 0 1 C 1 2 9 4 9 0

Lower half byte

4 B 0 C 0 0 1 8 2 4 3 6

4 5 6

7 8 9

1 1 4

RECORD IDENTIFIER RECORD LENGTH Reserved F18 F17 F16 F15 F14 F13 F12 F11 n.a. res. n.a. F25 F24 F23 F22 F21 F38 F37 res. F35 F34 F33 n.a. n.a. RECORD SEQ. CHARGE STATUS LAC LENGTH OWNER ID LENGTH LOCAL AREA CODE (LAC) + DIRECTORY NUMBER (DN)

P30308-X2058-K160-03-7617

207

Examples

7.2 Data Packages

7.2.1 Package 100: Date / Time / Duration PACKAGE NUMBER YEAR MONTH
DAY 100 = H64 2002 (02 + Flag F0 = 1) JULY = 7 15 = H0F 15 = H0F 12 = H0C 11 = H0B Flag F7 = 1 Flag F8 = 0 111 seconds = H6F Field Name 6 5 4 3 2 1 PACKAGE NUMBER (100) DATE / TIME Year month day hour minutes seconds F7 reserved DURATION Contents (hexadecimal) 0

HOUR
MINUTES SECONDS END DATE/TIME TIME SECURE DURATION Field Byte Length No Pos (bytes) 7 1 1 1 2 2 1 3 1 4 1 5 1 6 1 7 1 3 8 1 F8 4 9 3

Upper half byte

6 0 0 0 0 0 0 4 6 0 0

Lower half byte

4 2 7 F F C B 1 F 0 0

7.2.2 Package 101: Partner Directory Number PACKAGE NUMBER PARTNER DN

Field No 1 2 3 Byte Length Pos (bytes) 1 1 2 1 3 4 101 = H65 92449305

Field Name 6 5 4 3 2 1 0 PACKAGE NUMBER (101) reserved NO OF DIGITS DIGIT (i) DIGIT (i + 1)

Contents (hexadecimal)

Upper half byte

6 0 9 4 9 0

Lower half byte

5 8 2 4 3 5

7.2.3 Package 102: Service Info PACKAGE NUMBER SERVICE INDICATOR Bluebook
102 = H66 Telephony ISDN 3.1 kHz (12 = H0C) Flag F1 = 0

208

P30308-X2058-K160-03-7617

Examples

Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 1 4 4 1

Field Name 6 5 4 3 2 1 0 PACKAGE NUMBER (102) SERVICE INDICATOR ADDITIONAL INFORMATION reserved F1

Contents (hexadecimal)

Upper half byte

6 0 0 0

Lower half byte

6 C 0 0

7.2.4 Package 103: Charge Units For Connection PACKAGE NUMBER CALL CHARGE UNITS
Field Byte Length No Pos (bytes) 1 1 1 2 2 3 103 = H67 5

Field Name 6 5 4 3 2 1 PACKAGE NUMBER (103) CALL CHARGE UNITS

Contents (hexadecimal) 0

Upper half byte

6 0 0 0

Lower half byte

7 5 0 0

7.2.5 Package 104: Charge Units For Facility Usage PACKAGE NUMBER FAU CHARGE UNITS
Field Byte Length No Pos (bytes) 1 1 1 2 2 2 104 = H68 11 = H0B

Field Name 6 5 4 3 2 1 PACKAGE NUMBER (104) FAU CHARGE UNITS

Contents (hexadecimal) 0

Upper half byte

6 0 0

Lower half byte

8 B 0

7.2.6 Package 105: Trunk Identification Incoming PACKAGE NUMBER TRUNK GROUP NUMBER TRUNK NUMBER
Field Byte Length No Pos (bytes) 1 1 1 2 2 6 105 = H69 ABC12 (A = H41; B = H42; C = H43; 1 = H31; 2 = H32; blank = H20) 422 = H1A6

Field Name 6 5 4 3 2 1 PACKAGE NUMBER (105) TRUNK GROUP NUMBER

Contents (hexadecimal) 0

Upper half byte

6 4 4 4 3 3 2 A 0

Lower half byte

9 1 2 3 1 2 0 6 1

TRUNK NUMBER

P30308-X2058-K160-03-7617

209

Examples

7.2.7 Package 106: Trunk Identification Outgoing Refer to the example for package 105. 7.2.8 Package 107: Trunk Identification Incoming (CIC Format) PACKAGE NUMBER TRUNK GROUP NUMBER CIC PCM NUMBER CIC CHANNEL NUMBER
Field Byte Length No Pos (bytes) 1 1 1 2 2 6 107 = H6B ABC12 (A = H41; B = H42; C = H43; 1 = H31; 2 = H32; blank = H20) 406 = H196 5

Field Name 6 5 4 3 2 1 PACKAGE NUMBER (107) TRUNK GROUP NUMBER

Contents (hexadecimal) 0

Upper half byte

6 4 4 4 3 3 2 9 0 0

Lower half byte

B 1 2 3 1 2 0 6 1 5

3 4

8 10

2 1

CIC PCM NUMBER CIC CHANNEL NUMBER

7.2.9 Package 108: Trunk Identification Outgoing (CIC Format) Refer to the example for package 107 above. 7.2.10 Package 110: Connection Identification Number PACKAGE NUMBER CONNECTION ID
Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 4 110 = H6E H01060000

Field Name 6 5 4 3 2 1 0 PACKAGE NUMBER (110) PACKAGE LENGTH CONNECTION IDENTIFICATION

Contents (hexadecimal)

Upper half byte

6 0 0 0 0 0

Lower half byte

E 6 1 6 0 0

210

P30308-X2058-K160-03-7617

Examples

7.2.11 Package 111: Facilities Used By Owner PACKAGE NUMBER FACILITY

Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 1 111 = H6F Abbreviated Dialling (7)

Field Name 6 5 4 3 2 1 PACKAGE NUMBER (111) PACKAGE LENGTH FACILITY 1

Contents (hexadecimal) 0

Upper half byte

6 0 0

Lower half byte

F 3 7

7.2.12 Package 112: Facilities Used By Partner Refer to the example for package 111. 7.2.13 Package 113: Facility Input PACKAGE NUMBER ACTION FACILITY FACILITY INPUT NUMBERS REMOTE SCI
Field Byte Length No Pos (bytes) 7 1 1 1 2 2 1 3 3 1 F1 4 4 1 113 = H71 Enter Data (3) Call Diversion Immediate(100 = H64) Flag F1 = 1 Flag F2 = 1 Field Name 6 5 4 3 2 1 PACKAGE NUMBER (113) PACKAGE LENGTH F2 ACTION FACILITY Contents (hexadecimal) 0

FOR

ALL

Upper half byte

7 0 C 6

Lower half byte

1 4 3 4

7.2.14 Package 116: Date / Time PACKAGE NUMBER YEAR MONTH

DAY 116 = H74 92 = H5C FEBRUARY = 02 15 = H0F 17 = H11 45 = H2D 20 = H14 Flag F7 = 0 Flag F8 = 0

HOUR
MINUTES SECONDS BEGIN DATE / TIME TIME SECURE

P30308-X2058-K160-03-7617

211

Examples

Field Byte Length No Pos (bytes) 7 1 1 1 2 2 1 3 1 4 1 5 1 6 1 7 1 3 8 1 F8

Field Name 6 5 4 3 2 1 PACKAGE NUMBER (116) DATE / TIME Year Month Day Hour Minutes Seconds F7 Reserved

Contents (hexadecimal) 0

Upper half byte

7 5 0 0 1 2 1 0

Lower half byte

4 C 2 F 1 D 4 0

7.2.15 Package 118: Digit String PACKAGE NUMBER DIGIT STRING

Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 6 118 = H76 *51*7*3456#

Field Name 6 5 4 3 2 1 0 PACKAGE NUMBER (118) NO OF DIGITS DIGIT (i) DIGIT (i + 1)

Contents (hexadecimal)

Upper half byte

7 0 B 1 7 3 5 C

Lower half byte

6 B 5 B B 4 6

7.2.16 Package 120: Calling Party Category

120 = H78 PACKAGE NUMBER CALLING PARTY Priority subscriber (2) CATEGORY Field Byte Length No Pos (bytes) 1 1 1 2 2 1 Field Name 6 5 4 3 2 1 0 PACKAGE NUMBER (120) CALLING PARTY CATEGORY Contents (hexadecimal)

Upper half byte

7 0

Lower half byte

8 2

7.2.17 Package 122: Zone PACKAGE NUMBER ZONE

Field Byte Length No Pos (bytes) 1 1 1 2 2 2 122 = H7A 101 = H65

Field Name 6 5 4 3 2 1 PACKAGE NUMBER (122) ZONE

Contents (hexadecimal) 0

Upper half byte

7 6 0

Lower half byte

A 5 0

212

P30308-X2058-K160-03-7617

Examples

7.2.18 Package 125: Account Code PACKAGE NUMBER ACCOUNT CODE DIALLED ACCOUNT CODE
Field Byte No Pos 1 1 2 2 3 3 4 4 5 5 Length (bytes) 1 1 1 1 3 125 = H7D 43210 Flag F1 = 1

Field Name 6 5 4 3 2 1 0 PACKAGE NUMBER (125) PACKAGE LENGTH reserved F1 NO OF DIGITS DIGIT (i) DIGIT (i + 1)

Contents (hexadecimal)

Upper half byte

7 0 0 0 4 2 0

Lower half byte

D 7 1 5 3 1

7.2.19 Package 128: New Destination PACKAGE NUMBER NADI NPI NEW DESTINATION DIGITS
128 = H80 Significant national number (3) ISDN Numbering Plan (1) 633301

Field Byte Length Field Name 6 5 4 3 2 1 0 No Pos (bytes) 7 1 1 1 PACKAGE NUMBER (128) 2 2 1 PACKAGE LENGTH 3 3 1 res NADI (of New Destination) 4 4 1 res NPI Reserved 5 5 1 reserved NO OF DIGITS 6 6 3 DIGIT (i + 1) DIGIT (i)

Contents (hexadecimal)

Upper half byte

8 0 0 1 0 6 3 0

Lower half byte

0 8 3 0 6 3 3 1

7.2.20 Package 130: Traffic Quality Data PACKAGE NUMBER CAUSE VALUE CODING STANDARD LOCATION
Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 2 4 5 1 130 = H82 Normal call clearing (16 = H10) ITU standard (0) Public network serving the remote user (4)

Field Name 6 5 4 3 2 1 PACKAGE NUMBER (130) PACKAGE LENGTH CAUSE VALUE

CODING STAND.

Contents (hexadecimal) 0

Upper half byte

8 0 1 0 0

Lower half byte

2 5 0 0 4

res

LOCATION

P30308-X2058-K160-03-7617

213

Examples

7.2.21 Package 134: Durations Before Answer PACKAGE NUMBER DURATION DIALTONE TILL ADDRESS COMPLETE DURATION ADDRESS COMPLETE TILL ANSWER
Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 2 5 2 Field Name 6 5 4 3 2 1 0 PACKAGE NUMBER (134) PACKAGE LENGTH DURATIONS BEFORE ANSWER duration from dial tone till address complete duration from address complete till answer 134 = H86 10 = H0A 73 = H49

Contents (hexadecimal)

Upper half byte

8 0 0 0 4 0

Lower half byte

6 6 A 0 9 0

7.2.22 Package 135: Chargeband PACKAGE NUMBER CHARGEBAND CHARGEBAND RECEIVED

Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 2 4 5 1 135 = H87 219 = HDB Flag F1 = 1

MESSAGE

Field Name 6 5 4 3 2 1 PACKAGE NUMBER (135) PACKAGE LENGTH CHARGEBAND reserved

Upper half byte

Contents (hexadecimal) Lower half byte 8 7 0 5 D B 0 0 0 1

7.2.23 Package 136: UUS3 Counters PACKAGE NUMBER UUS3 MESSAGES RECEIVED UUS3 MESSAGES SENT
Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 2 4 5 2 136 = H88 3284 = HCD4 109 = H6D

Field Name 6 5 4 3 2 1 PACKAGE NUMBER (135) PACKAGE LENGTH UUS3 MSG RECEIVED UUS3 MSG SENT

Contents (hexadecimal) 0

Upper half byte

8 0 D 0 6 0

Lower half byte

8 6 4 C D 0

214

P30308-X2058-K160-03-7617

Examples

7.2.24 Package 138: B Meter Pulses PACKAGE NUMBER B Meter Pulses

Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 2 138 = H8A 11 = H0B

Field Name 5 4 3 2 1 PACKAGE NUMBER PACKAGE LENGTH B Meter Pulses

Contents (hexadecimal) 0

Upper half byte

8 0 0 0

Lower half byte

A 4 B 0

7.2.25 Package 139: Release Indication PACKAGE NUMBER RELEASE INDICATION

Field Byte Length No Pos (bytes) 1 2 3 1 2 3 1 1 1 139 = H8B Call Release initiated by B-party (3)

Field Name 4 3 2

Contents (hexadecimal) 1 0

Upper half byte

8 0 0

Lower half byte

B 3 3

PACKAGE NUMBER (139) PACKAGE LENGTH RELEASE Reserved

INDIC.

7.2.26 Package 142: Calling Party Number PACKAGE NUMBER NADI NPI PRESENTATION INDICATOR SCREENING INDICATOR LAC LENGTH CALLING PARTY DIGITS
142 = H8E Significant national number (3) ISDN Numbering Plan (1) Presentation allowed (0) User provided, verified and passed (1) 1 92449306 Contents (hexadecimal)

Field Byte Length Field Name 6 5 4 3 2 1 0 No Pos (bytes) 7 1 1 1 PACKAGE NUMBER (142) 2 2 1 PACKAGE LENGTH Res 3 3 1 NADI (of calling party) Res NPI (calling) Pres. Ind. Screening 4 4 1 LAC LENGTH NO OF DIGITS 5 5 1 6 6 4 DIGIT (i) DIGIT (i + 1)

Upper half byte

8 0 0 1 2 9 4 9 0

Lower half byte

E 9 3 1 8 2 4 3 6

P30308-X2058-K160-03-7617

215

Examples

7.2.27 Package 143: IP/SN Charge Data The contents of this packages are project specific. 7.2.28 Package 145: Billing CAC PACKAGE NUMBER CAC TYPE NUMBER OF PREFIX DIGITS CAC DIGITS
Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 1 4 4 3 145 = H91 Preselected CAC (2) 2 43210

Field Name 5 4 3 2 1 0 PACKAGE NUMBER PACKAGE LENGTH CAC TYPE PREFIX NO OF DIG DIGIT (i) DIGIT (i+1) 6

Contents (hexadecimal)

Upper half byte

9 0 5 4 2 0

Lower half byte

1 6 5 3 1

7.2.29 Package 146: Third Party Number PACKAGE NUMBER THIRD PARTY TYPE NADI NPI THIRD PARTY DIGITS
146 = H92 Call Transfer Partner (1) Significant national number (3) ISDN Numbering Plan (1) 56741235

Field Byte Length Field Name 6 5 4 3 2 1 0 No Pos (bytes) 7 1 1 1 PACKAGE NUMBER (146) 2 2 1 PACKAGE LENGTH 3 3 1 reserved 3rd PARTY TYPE 4 4 1 F6 F5 F4 F3 F2 F1 5 5 1 res NADI (of third party) 6 6 1 res NPI reserved 7 7 1 NO OF DIGITS 8 8 4 DIGIT (i) DIGIT (i+1)

Contents (hexadecimal)

Upper half byte

9 0

Lower half byte

2 B 1 0 3 0 8 6 4 2 5

0 0 0
1 0 5 7 1 3

7.2.30 Package 147: Tariff Info PACKAGE NUMBER CURRENCY FORMAT CURRENT TARIFF PRESENT NEXT TARIFF PRESENT TARIFFS FOR CHARGING CURRENCY
147 = H93 Validity Indicator 7 Validity Indicator 0 Validity Indicator 1 Validity Indicator 6 Belgian Franc = 3

216

P30308-X2058-K160-03-7617

Examples

Current Tariff (in currency format): RECEIVING TIME ACKNOWLEDGEMENT STATUS ORIGINATOR IDENTIFICATION CALL ATTEMPT CHARGES PRESENT CALL SETUP CHARGES PRESENT COMMUNICATION CHARGES PRESENT NON-CYCLIC SEQUENCE CALL ATTEMPT SCALE CALL ATTEMPT FACTOR CALL SETUP SCALE CALL SETUP FACTOR COMMUNICATION CHARGE SCALE COMMUNICATION CHARGE FACTOR COMMUNICATION CHARGE COUNT DURATION Next Tariff (in currency format): RECEIVING TIME ACKNOWLEDGEMENT STATUS ORIGINATOR IDENTIFICATION SWITCH OVER TIME CALL ATTEMPT CHARGES PRESENT CALL SETUP CHARGES PRESENT COMMUNICATION CHARGES PRESENT CYCLIC SEQUENCE CALL ATTEMPT SCALE CALL ATTEMPT FACTOR CALL SETUP SCALE CALL SETUP FACTOR COMMUNICATION CHARGE SCALE COMMUNICATION CHARGE FACTOR COMMUNICATION CHARGE COUNT DURATION

[Link] Positively acknowledged (1) National regulation authority = 1 Network ID = 8 Node Id = 9 Validity Indicator 0 Validity Indicator 1 Validity Indicator 2 Validity Indicator 7 10 (represented by value 1) 60 = H00003C 10 (represented by value 1) 60 = H00003C 10 (represented by value 1) 60 = H00003C 60 = H003C

[Link] Positively acknowledged (1) National regulation authority = 1 Network ID = 8 Node Id = 9 [Link] represented by value 30 = H1E Validity Indicator 0 Validity Indicator 1 Validity Indicator 2 Validity Indicator 7 = 0 10 (represented by value 1) 60 = H00003C 10 (represented by value 1) 60 = H00003C 10 (represented by value 1) 50 = H000032 60 = H003C

P30308-X2058-K160-03-7617

217

Examples

Field Byte Length Field Name 6 5 4 3 2 1 0 No Pos (bytes) 7 1 1 1 PACKAGE NUMBER (147) 2 2 1 PACKAGE LENGTH 3 3 1 CONTROL & VALIDITY INDICATORS
4 4 1 CURRENCY

Contents (hexadecimal)

Upper half byte

9 2 C
0

Lower half byte

3 A 3
3

5 5 6 7 8
9

6
7

1 1 1 1
7

Current Tariff Time (24 h) indicator when the current tariff was received Reserved Hours Reserved Minutes Reserved Seconds Acknowledgment status
Originator Identification

0 0 0 0
0 2 0 0 0 0 0

2 2 2 1
1 0 0 9 0 0 0

8 9 10 11 12 13 14 15

16 17 18

1 1 3 1 3 1 3 2

Tariff Control & Validity Indicators Scale Call Attempt Current Tariff

Factor Call Attempt Current Tariff

Scale Call Setup Current Tariff

21 22

Factor Call Setup Current Tariff

Scale Communication Charge Current Tariff

25 26

8 0 3 0 0 0 3 0 0 0 3 0 0 3 0

7 1 C 0 0 1 C 0 0 1 C 0 0 C 0

Factor Communication Charge Current Tariff Count Duration Communication Charge Current Tariff
Next Tariff Time (24 h) indicator when the next tariff was received Reserved Hours reserved Minutes reserved Seconds Acknowledgment status
Originator Identification

16
31 32 33 34 35

17
18

1 1 1 1
7

0 0 0 0
0 2 0 0 0 0 0

2 2 2 1
1 0 0 9 0 0 0

19 20 21 22 23

42 43 44 45

1 1 1 3 1

Switch over time Tariff Control & Validity Indicators Scale Call Attempt Current Tariff

Factor Call Attempt Current Tariff

Scale Call Setup Current Tariff

1 8 0 3 0 0 0

E 7 1 C 0 0 1

218

P30308-X2058-K160-03-7617

Examples

Field Byte Length 49 3 24 25 26 27

52 53

Field Name

Factor Call Setup Current Tariff

Scale Communication Charge Current Tariff

Contents (hexadecimal) 3 C 0 3 0 0 3 0 1 2 0 0 C 0

1 3 2

Factor Communication Charge Current Tariff Count Duration Communication Charge Current Tariff

7.2.31 Package 148: CAC New Destination PACKAGE NUMBER NUMBER OF DIGITS VALIDATION CAC DIGITS
Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 1 4 4 3 148 = H94 5 CAC New Destination used to reach destination (1) 43210

Field Name 5 4 3 2 1 0 PACKAGE NUMBER PACKAGE LENGTH VAL NO OF DIG reserved DIGIT (i) DIGIT (i+1) 6

Contents (hexadecimal)

Upper half byte

9 0 D 4 2 0

Lower half byte

4 6 5 3 1

7.2.32 Package 149: Global Call Reference PACKAGE NUMBER GLOBAL CALL REFERENCE RECEIVED GLOBAL CALL REFERENCE
Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 1 4 4 n 149 = H95 Flag F1 = 1

H00010203040506
Contents (hexadecimal)

Field Name 6 5 4 3 2 1 0 PACKAGE NUMBER (149) PACKAGE LENGTH reserved F1 GLOBAL CALL REFERENCE

Upper half byte

9 0 0 0 0 0 0 0 0 0

Lower half byte

5 A 1 0 1 2 3 4 5 6

P30308-X2058-K160-03-7617

219

Examples

7.2.33 Package 150: Audit Trail First Ticket Hexadecimal contents: 8437008C10C0118E 8E0903112892449306 6462070F0F032E406F0000 661E0100 6E0600000000 8F0903060210060704 960801000000548D
Logical contents:

RECORD SEQUENCE FLAGS SEQUENCE CHECKSUM

RECORD OWNER TYPE CALLING_PARTY_NR DATE_TIME_DURATION SERVICE_INFO CONNECTION_ID IP/SN_CHARGE_DATA AUDIT_TRAIL

: Single CHARGE STATUS: Charge : AMA CONNECTION ISDN

: Calling Party Number : 92449306, NADI = Sign. national nr, NPI = ISDN Presentation indicator = Presentation allowed Screening = User provided, verified and passed : 1998-07-15 [Link] End D/T Secure 111 Sec : Voice Group, Blue : H'00000000 : H'03060210060704 : Sequence nr = H'00000001 Checksum1 = 84, Checksum2 = 141 Field Name 6 5 4 3 2 1 PACKAGE NUMBER (150) PACKAGE LENGTH SEQUENCE NUMBER Contents (hexadecimal) 0 9 0 0 0 0 0 5 8

Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 4

Lower half byte

6 8 1 0 0 0 4 D

4 5

7 8

1 1

CHECKSUM VALUE 1 CHECKSUM VALUE 2

Second Ticket
Hexadecimal contents: 843F00A410C011AC AC0A4103106808912500 7462070F10033640 661D0100 6E0600000000 71048301 760892449305 8E0903112892449306 9608020000000F99 Logical contents:

RECORD SEQUENCE
FLAGS RECORD OWNER TYPE SYSTEM_PROVIDED_NR DATE_TIME SERVICE_INFO CONNECTION_ID FACILITY_INPUT DIGIT_DATA CALLING_PARTY_NR AUDIT_TRAIL

: Single CHARGE STATUS: Charge

: AMA FAIS ISDN SEQUENCE CHECKSUM : System Provided Number : 08912500, NADI = Sign. national nr, NPI = ISDN Number qualifier = SCI Served User, Number type = Subscriber DN : 1998-07-15 [Link] End D/T Secure : Non Voice Group, Blue : H'00000000 : ACTION = Enter Data , FACILITY = ABBD5 FACILITY INPUT for all numbers : 92449305 : 92449306, NADI = Sign. national nr, NPI = ISDN Presentation indicator = Presentation allowed Screening = User provided, verified and passed : Sequence nr = H'00000002 Checksum1 = 15, Checksum2 = 153

220

P30308-X2058-K160-03-7617

Examples

Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 4

Field Name 6 5 4 3 2 1 PACKAGE NUMBER (150) PACKAGE LENGTH SEQUENCE NUMBER

Contents (hexadecimal) 0 9 0 0 0 0 0 0 9

Lower half byte

6 8 2 0 0 0 F 9

4 5

7 8

1 1

CHECKSUM VALUE 1 CHECKSUM VALUE 2

7.2.34 Package 151: Business Group Identification PACKAGE NUMBER BUSINESS GROUP ID
Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 3 151 = H97 H000102

Field Name 6 5 4 3 2 1 PACKAGE NUMBER (151) PACKAGE LENGTH BUSINESS GROUP ID

Contents (hexadecimal) 0

Upper half byte

9 0 0 0 0

Lower half byte

7 5 0 1 2

7.2.35 Package 152: Centrex Numbers PACKAGE NUMBER CALLING PARTY INTERCOM DIGITS CALLED PARTY INTERCOM DIGITS REDIRECTING INTERCOM DIGITS
Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 1 4 4 1 5 5 4 152 = H98 56741235 56746789 56743300

Field Name 5 4 3 2 1 0 PACKAGE NUMBER PACKAGE LENGTH Reserved F3 F2 F1 F0 NO OF DIGITS DIGIT (i) DIGIT (i + 1) 6

Contents (hexadecimal)

Upper half byte

9 1 0 0 5 7 1 3 0 5 7 6 8 0 5 7 3 0

Lower half byte

8 2 7 8 6 4 2 5 8 6 4 7 9 8 6 4 3 0

6 7

9 10

1 4

NO OF DIGITS DIGIT (i) DIGIT (i + 1)

8 9

14 15

1 4

NO OF DIGITS DIGIT (i) DIGIT (i + 1)

P30308-X2058-K160-03-7617

221

Examples

7.2.36 Package 153: Received Called Party Number PACKAGE NUMBER NADI NPI RECEIVED CALLED PARTY NUMBER
153 = H99 Significant national number (3) ISDN Numbering Plan (1) 01020, no CAC digits included

Field Byte Length Field Name 6 5 4 3 2 1 0 No Pos (bytes) 7 1 1 1 PACKAGE NUMBER 2 2 1 PACKAGE LENGTH 3 3 1 res NADI (of received called party) 4 4 1 res NPI reserved Number of 5 5 1 Number of Digits
CAC Digits

Contents (hexadecimal)

Upper half byte

9 0 0 1 0 0 0 0

Lower half byte

9 8 3 0 5 1 2

DIGIT (i)

DIGIT (i + 1)

7.2.37 Package 154: Additional Call Indicators PACKAGE NUMBER CENTREX SUBSCRIBER INTERNATIONAL CALL
Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 1 4 4 1 5 5 1 6 6 1 7 7 1 154 = H9A Flag F11 Flag F14

Field Name 6 5 4 3 2 1 PACKAGE NUMBER (154) PACKAGE LENGTH

n.a. res. F37 res. res. n.a. F26 n.a. res. F56 F15 F25 n.a. F45 F55 F14 F24 F34 F44 n.a. n.a. F23 n.a. F43 n.a. F12 F22 n.a. F42 n.a.

Contents (hexadecimal) 0

Upper half byte

9 0 0 0 0 0 0

Lower half byte

A 6 9 0 0 0 0

F18 res. F38 res. res.

F11 F21 n.a. F41 n.a.

7.2.38 Package 155: Add On Tariff PACKAGE NUMBER CURRENCY FORMAT RECEIVED ADD ON TARIFF PRESENT TARIFF ONLY FOR DISPLAY CURRENCY
155 = H9B Validity Indicator 7 Validity Indicator 0 Validity Indicator 6 not set Belgian Franc = 3

222

P30308-X2058-K160-03-7617

Examples

Received Add On Tariff: RECEIVING TIME ACKNOWLEDGEMENT STATUS ORIGINATOR IDENTIFICATION SCALE FACTOR

[Link] Positively acknowledged (1) National regulation authority = 1 Network ID = 8 Node Id = 9 10 (represented by value 1) 60 = H00003C

Field Name Field Byte Length 6 5 4 3 2 1 0 No Pos (bytes) 7 1 1 1 PACKAGE NUMBER (155) 2 2 1 PACKAGE LENGTH 3 3 1 CONTROL & VALIDITY INDICATORS
4 4 1 CURRENCY

Contents (hexadecimal)

Upper half byte

9 0 8
0

Lower half byte

B B 1
3

5 5 6 7 8
9

6
7

1 1 1 1
7

Add On Tariff Time (24 h) indicator when the current tariff was received Reserved Hours Reserved Minutes Reserved Seconds Acknowledgment status
Originator Identification

0 0 0 0
0 2 0 0 0 0 0

2 2 2 1
1 0 0 9 0 0 0

8 9

16 17

1 3

Scale Factor

0 3 0 0

1 C 0 0

7.2.39 Package 156: Advised Cumulated Charges PACKAGE NUMBER TYPE OF ADVICE ADVISED CHARGES CONTROL FLAGS ADVISED UNITS MULTIPLIER
156 = H9C ISDN Advice of Charge (2) FAU charges not included; Connection charges included; Type of Units = meter pulses 3 Factor 10 (represented by value 4)

Field Byte Length Field Name 6 5 4 3 2 1 0 No Pos (bytes) 7 1 1 1 PACKAGE NUMBER (156) 2 2 1 PACKAGE LENGTH 3 3 1 res F7 Type of ADV_CHRGS_ Advice CONTROL 4 4 3 ADVISED CUM CURRENCY UNITS 5 7 1 ADVISED CUM CHARGES MULTIPLIER

Contents (hexadecimal)

Upper half byte

9 0 2 0 0 0 0

Lower half byte

C 7 2 3 0 0 4

P30308-X2058-K160-03-7617

223

Examples

7.2.40 Package 157: Outgoing PA Identification PACKAGE NUMBER LAC LENGTH PA IDENTIFICATION
Field No 1 2 2 3 Byte Pos 1 2 2 3
Length

157 = H9D 1 92525357

(bytes) 1 1 1 n

Field Name 7 6 5 4 3 2 1 PACKAGE NUMBER (157) PACKAGE LENGTH LAC Length No Of Digits DIGIT (i) DIGIT (i + 1)

Contents (hexadecimal) 0

Upper half byte

9 0 2 9 5 5 5

Lower half byte

D 7 8 2 2 3 7

7.2.41 Package 159: Additional Calling Party Number PACKAGE NUMBER NADI NPI PRESENTATION INDICATOR SCREENING INDICATOR ADDITIONAL CALLING PARTY DIGITS
159 = H9F Significant national number (3) ISDN Numbering Plan (1) Presentation allowed (0) User provided, verified and passed (1) 01020

Field Byte Length Field Name Contents (hexadecimal) 6 5 4 3 2 1 0 No Pos (bytes) 7 Upper half byte Lower half byte 1 1 1 PACKAGE NUMBER (159) 9 F 2 2 1 PACKAGE LENGTH 0 8 3 3 1 Res NADI (of calling party) 0 3 4 4 1 Res NPI (calling) [Link]. Screening 1 1 5 5 1 Reserved NO OF DIGITS 0 5 6 6 3 DIGIT (i) DIGIT (i + 1) 0 1 0 2 0

7.2.42 Package 167: Additional Numbers PACKAGE NUMBER NUMBER OF ADDITIONAL NUMBERS First number NUMBER QUALIFIER NUMBER TYPE NADI NPI ADDITIONAL NUMBER DIGITS
167 = HA7 2

Calling Party (1) Default MSN (5) Significant national number (3) ISDN Numbering Plan (1) 21575362

224

P30308-X2058-K160-03-7617

Examples

Second number NUMBER QUALIFIER NUMBER TYPE NADI NPI ADDITIONAL NUMBER DIGITS

Calling Party (1) PBX Operator DN (4) Significant national number (3) ISDN Numbering Plan (1) 897501230

Field Byte Length Field Name 6 5 4 3 2 1 0 No Pos (bytes) 7 1 1 1 PACKAGE NUMBER (167) 2 2 1 PACKAGE LENGTH NUMBER OF ADDITIONAL NUMBER STRINGS 3 3 1 NUMBER QUALIFIER NUMBER TYPE 4 4 1 5 5 1 res NADI (of Additional Number) 6 6 1 res NPI reserved 7 7 1 reserved NO OF DIGITS 8 8 4 DIGIT (i) DIGIT (i + 1)

Contents (hexadecimal)

Upper half byte

A 1 0 1 0 1 0 2 5 5 6 1 0 1 0 8 7 0 2 0

Lower half byte

7 4 2 5 3 0 8 1 7 3 2 4 3 0 9 9 5 1 3

9 10 11 12 13

12 13 14 15 16

1 1 1 1 4

NUMBER QUALIFIER

NUMBER TYPE

res NADI (of Additional Number) res NPI reserved reserved NO OF DIGITS DIGIT (i) DIGIT (i + 1)

7.2.43 Package 168: Called Party Number PACKAGE NUMBER NADI NPI LAC LENGTH CALLED PARTY DIGITS
168 = HA8 Significant national number (3) ISDN Numbering Plan (1) 1 92449306 Contents (hexadecimal)

Field Byte Length Field Name 6 5 4 3 2 1 0 No Pos (bytes) 7 1 1 1 PACKAGE NUMBER (168) 2 2 1 PACKAGE LENGTH 3 3 1 res NADI (of called party) 4 4 1 res NPI (called) reserved LAC LENGTH NO OF DIGITS 5 5 1 6 6 4 DIGIT (i) DIGIT (i + 1)

Upper half byte

A 0 0 1 2 9 4 9 0

Lower half byte

8 9 3 0 8 2 4 3 6

P30308-X2058-K160-03-7617

225

Examples

7.2.44 Package 170: Redirecting Number Refer to the example of package 142. 7.2.45 Package 171: Sent Called Party Number PACKAGE NUMBER NADI NPI SENT CALLED PARTY DIGITS
171 = HAB Significant national number (3) ISDN Numbering Plan (1) 37761566, no CAC digits included Contents (hexadecimal)

Field Byte Length Field Name 6 5 4 3 2 1 0 No Pos (bytes) 7 1 1 1 PACKAGE NUMBER (171) 2 2 1 PACKAGE LENGTH 3 3 1 res NADI (of sent called party) 4 4 1 res NPI reserved Number of 5 5 1 Number of Digits
CAC Digits

Upper half byte

A 0 0 1 0 3 7 1 6

Lower half byte

B 9 3 0 8 7 6 5 6

DIGIT (i)

DIGIT (i + 1)

7.2.46 Package 172: System Provided Number PACKAGE NUMBER NUMBER QUALIFIER NUMBER TYPE NADI NPI LAC LENGTH SYSTEM PROVIDED NUMBER
172 = HAC Calling Party (1) PBX Pilot DN (2) Significant national number (3) ISDN Numbering Plan (1) 2 89750

Field Name Field Byte Length 6 5 4 3 2 1 0 No Pos (bytes) 7 1 1 1 PACKAGE NUMBER (172) 2 2 1 PACKAGE LENGTH NUMBER QUALIFIER NUMBER TYPE 3 3 1 4 4 1 res NADI 5 5 1 res NPI reserved LAC LENGTH NO OF DIGITS 6 6 1 7 7 3 DIGIT (i) DIGIT (i + 1)

Contents (hexadecimal)

Upper half byte

A 0 1 0 1 4 8 7 0

Lower half byte

C 9 2 3 0 5 9 5

226

P30308-X2058-K160-03-7617

Examples

7.2.47 Package 178: Exchange Info PACKAGE NUMBER VERSION ID EXCHANGE ID

Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 1 4 4 1 5 5 1 6 6 6 178 = HB2 22 = H16 BERLIN

Field Name 6 5 4 3 2 1 PACKAGE NUMBER (178) PACKAGE LENGTH VA1 reserved VERSION ID reserved EXCH ID LENGTH EXCHANGE ID

Contents (hexadecimal) 0

Upper half byte

B 0 0 1 0 4 4 5 4 4 4

Lower half byte

2 B 3 6 6 2 5 2 C 9 E

VA0

7.2.48 Package 179: Service Subscriber Number PACKAGE NUMBER SERVICE SUBSCRIBER QUALIFIER TFS SUBSCRIBER DIGITS
Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 1 4 5 6 4 5 6 1 1 3 179 = HB3 TFS service subscriber (2) 53971

Field Name 6 5 4 3 2 1 0 PACKAGE NUMBER (179) PACKAGE LENGTH reserved SERV. SUB. NR. QUALIFIER Reserved

Contents (hexadecimal)

Upper half byte

B 0 0 0 0 5 9 1

Lower half byte

3 8 2 0 5 3 7

CODING

NO OF DIGITS or NUMBER OF BYTES DIGITS (packed) or CHARACTERS

7.2.49 Package 183: Sent CAC PACKAGE NUMBER NUMBER OF DIGITS CAC DIGITS
183 = HB7 5 43

P30308-X2058-K160-03-7617

227

Examples

Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 1 4 4 3

Field Name 5 4 3 2 1 0 PACKAGE NUMBER PACKAGE LENGTH Reserved NO OF DIG DIGIT (i) DIGIT (i+1) 6

Contents (hexadecimal)

Upper half byte

B 0 0 4

Lower half byte

7 4 2 3

7.2.50 Package 184: MLPP Level PACKAGE NUMBER Precedence Level

184 = HB8 priority (3) Contents (hexadecimal)

Field Name Field Byte Length 6 5 4 3 2 1 0 No Pos (bytes) 7 1 1 1 PACKAGE NUMBER 2 2 1 PACKAGE LENGTH 3 3 1 sp. LFB sp. Precedence Level st 4 4 1 NI Digit 2nd NI Digit 2 rd 3 NI Digit 4th NI Digit 5 6 3 MLPP service domain

Upper half byte

B 0 0 0 0 0 0 0

Lower half byte

8 8 3 0 0 0 0 0

7.2.51 Package 186 : IN Service Key PACKAGE NUMBER IN Service Key

Field No 1 2 3 Byte Pos 1 2 3 Length (bytes) 1 1 1

186 = HBA 6

Field Name 7 6 5 4 3 PACKAGE NUMBER PACKAGE LENGTH IN Service Key

Contents (hexadecimal) Upper half byte Lower half byte B 8 0 6 6 0 0 0 0 0 0 0

7.2.52 Package 187: Received CAC PACKAGE NUMBER NUMBER OF DIGITS CAC DIGITS
Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 1 4 4 3 187 = HBB 5 43210

Field Name 5 4 3 2 1 0 PACKAGE NUMBER PACKAGE LENGTH Reserved NO OF DIG DIGIT (i) DIGIT (i+1) 6

Contents (hexadecimal)

Upper half byte

B 0 0 4 2 0

Lower half byte

B 6 5 3 1

228

P30308-X2058-K160-03-7617

Examples

7.2.53 Package 191 : Signalling Point Code PACKAGE NUMBER NETWORK INDICATOR SIGNALLING POINT CODE
Field No 1 2 3 4 Byte Pos 1 2 3 4 Length (bytes) 1 1 1 3

191 = HBF National 0 = 2 1234 = H4D2

Field Name 7 6 5 4 3 2 PACKAGE NUMBER (191) PACKAGE LENGTH

Res SIGNALLING POINT CODE

Network Indicator

Contents (hexadecimal) Upper half byte Lower half byte B F 0 9 0 2 D 0 0 2 4 0

7.2.54 Package 192 : Sent Calling Party Number PACKAGE NUMBER NADI NPI PRESENTATION INDICATOR SCREENING INDICATOR LAC LENGTH CALLING PARTY DIGITS
Field No 1 2 3 4 5 6 Byte Pos 1 2 3 4 5 6 Length (bytes) 1 1 1 1 1 4

192= HC0 Significant national number (3) ISDN Numbering Plan (1) Presentation allowed (0) User provided, verified and passed (1) 1 92449306

Field Name Contents (hexadecimal) 7 6 5 4 3 2 1 0 Upper half byte Lower half byte PACKAGE NUMBER (192) C 0 PACKAGE LENGTH 0 9 Res NADI (of calling party) 0 3 Res NPI (calling) Pres. Screening 1 1 Ind. LAC LENGTH NO OF DIGITS 2 8 2 DIGIT (i) DIGIT (i + 1) 9 4 4 3 9 6 0

7.2.55 Package 193 : Sent Redirecting Number PACKAGE NUMBER NADI NPI LAC LENGTH CALLING PARTY DIGITS
193 = HC1 Significant national number (3) ISDN Numbering Plan (1) 1 92449306

P30308-X2058-K160-03-7617

229

Examples

Field No 1 2 3 4 5 6

Byte Pos 1 2 3 4 5 6

Length (bytes) 1 1 1 1 1 4

Field Name 7 6 5 4 3 2 1 PACKAGE NUMBER (193) PACKAGE LENGTH Res NADI (of calling party) Res NPI (calling) Reserved LAC LENGTH NO OF DIGITS DIGIT (i) DIGIT (i + 1)

Contents (hexadecimal) Upper half byte Lower half byte C 1 0 9 0 3 1 0 2 8 2 9 4 4 3 9 6 0

7.2.56 Package 194 : Sent Calling Party Category PACKAGE NUMBER SENT CALLING PARTY CATEGORY
Field No 1 2 3 Byte Pos 1 2 3 Length (bytes) 1 1 1

194 = HC2 Priority subscriber (2)

Field Name 7 6 5 4 3 2 1 0 PACKAGE NUMBER (194) PACKAGE LENGTH SENT CALLING PARTY CATEGORY

Contents (hexadecimal) Upper half byte Lower half byte C 2 0 3 0 2

7.2.57 Package 195 : Original Calling Party Category PACKAGE NUMBER ORIGINAL CALLING PARTY CATEGORY
Field No 1 2 3 Byte Pos 1 2 3 Length (bytes) 1 1 1

195 = HC3 Priority subscriber (2)

Field Name 7 6 5 4 3 2 1 0 PACKAGE NUMBER (195) PACKAGE LENGTH ORIGINAL CALLING PARTY CATEGORY

Contents (hexadecimal) Upper half byte Lower half byte C 3 0 3 0 2

7.2.58 Package 196 : Trunk Info PACKAGE NUMBER INCOMING TRUNK NAME INCOMING TRUNK NUMBER OUTGOING TRUNK NAME OUTGOING TRUNK NUMBER
196 = HC4 BRUGGE (B = H42, R = H52, U = H55, G = H48, E = H45) 422 = H1A6 BRUSSEL (S = H53, L = H4C) 12 = HC

230

P30308-X2058-K160-03-7617

Examples

Field No 1 2 3 4 5

Byte Pos 1 2 3 4 5

Length (bytes) 1 1 1 1 12

Field Name 7 6 5 4 3 2 1 0 PACKAGE NUMBER (196) PACKAGE LENGTH SUBPACKAGE NUMBER (INCOMING) SUBPACKAGE LENGTH TRUNK NAME

6 7 8 9

17 19 20 21

2 1 1 12

TRUNK NUMBER SUBPACKAGE NUMBER (OUTGOING) SUBPACKAGE LENGTH TRUNK NAME

TRUNK NUMBER

Contents (hexadecimal) Upper half byte Lower half byte C 4 2 2 0 1 0 E 2 4 2 5 5 5 8 4 8 4 5 4 0 0 0 0 0 0 0 0 0 0 0 0 A 6 0 1 0 2 0 E 2 4 2 5 5 5 3 5 3 5 5 4 C 4 0 0 0 0 0 0 0 0 0 0 0 C 0 0

7.2.59 Package 198 : Durations in 100 msec PACKAGE NUMBER CALL DURATION DURATION DIALTONE ACM DURATION ACM ANSWER
198 = HC6 1100 msec 2300 msec 12700 msec

P30308-X2058-K160-03-7617

231

Examples

Field No 1 2 3 4 5 7 8 9

Byte Pos 1 2 3 4 5 8 9 10

Length (bytes) 1 1 1 1 3 1 1 3 3

Field Name 7 6 5 4 3 2 1 PACKAGE NUMBER (198) PACKAGE LENGTH SUBPACKAGE NUMBER (CALL) SUBPACKAGE LENGTH CALL DURATION

SUBPACKAGE NUMBER (DURBANS) SUBPACKAGE LENGTH DURATION DIALTONE TILL ADDRESS COMPLETE DURATION ADDRESS COMPLETE TILL ANSWER

Contents (hexadecimal) Upper half byte Lower half byte C 6 0 F 0 1 0 5 B 0 0 0 0 0 0 2 0 8 7 1 0 0 0 0 F 7 0 0 0 0

7.2.60 Package 199 : Received Charge Determination Information PACKAGE NUMBER CDI
Field No 1 2 3 Byte Pos 1 2 3

199 = HC7 Charge already determined

Length Field Name 6 5 4 3 2 (bytes) 7 1 PACKAGE NUMBER (199) 1 PACKAGE LENGTH 1

Contents (hexadecimal) Upper half byte Lower half byte C 7 0 3 CDI 0 1 0

7.2.61 Package 204: Access Data PACKAGE NUMBER Terminal Type DLU Number A-side Port Type Port Address A-side
204 = HCC analog subscriber (1) 30 =H1E DLU (1) 30-0-0-0

232

P30308-X2058-K160-03-7617

Examples

Field No 1 2 3 4 5 6 7 8 9 10 11 12 13 14 13

Byte Pos 1 2 3 4 5 6 7 8 10 11 12 13 15 16 15

Length (bytes) 1 1 1 1 1 1 1 2 1 1 1 2 1 1 1

Field Name 7 6 5 4 3 2 1 0 PACKAGE NUMBER (204) PACKAGE LENGTH SUBPACKAGE NUMBER (TERMINAL TYPE) SUBPACKAGE LENGTH TERMINAL TYPE SUBPACKAGE NUMBER (DLU NUMBER A-SIDE)) SUBPACKAGE LENGTH DLU NUMBER A-SIDE SUBPACKAGE NUMBER (PORT ADDRESS A-SIDE) SUBPACKAGE LENGTH PORT TYPE ADDRESS PART A (DLU NUMBER) ADDRESS PART B (DLU SHELF NUMBER) ADDRESS PART C (DLU MODULE NUMBER) ADDRESS PART B

Contents (hexadecimal) Upper half byte Lower half byte C C 1 1 0 1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 3 1 3 4 E 0 5 8 1 E 0 0 0 0

7.2.62 Package 205: Non Charged Facilities Used By Owner PACKAGE NUMBER FACILITY
Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 1 205 = HCD Abbreviated Dialling (7)

Field Name 6 5 4 3 2 1 PACKAGE NUMBER (205) PACKAGE LENGTH FACILITY 1

Contents (hexadecimal) 0

Upper half byte

C 0 0

Lower half byte

D 3 7

7.2.63 Package 209: Accumulated Currency Charges PACKAGE NUMBER SCALE FACTOR CURRENCY
Field Byte Length No Pos (bytes) 1 1 1 2 2 1 3 3 1 4 4 3 5 7 1 209= HD1 10 (represented by value 1) 5 Euro (8)

Field Name 6 5 4 3 2 1 PACKAGE NUMBER (156) PACKAGE LENGTH SCALE FACTOR CURRENCY

Contents (hexadecimal) 0

Upper half byte

D 0 0 0 0 0 0

Lower half byte

1 7 1 5 0 0 8

P30308-X2058-K160-03-7617

233

Examples

7.2.64 Package 211: Additional Release Cause PACKAGE NUMBER Call Result
Field No 1 2 3 4 5 Byte Pos 1 2 3 4 5 Length (bytes) 1 1 1 1 1

211 = HD3 Successful, answered call (1)

Field Name 7 6 5 4 3 2 1 0 PACKAGE NUMBER (204) PACKAGE LENGTH SUBPACKAGE NUMBER (CALL RESULT) SUBPACKAGE LENGTH CALL RESULT

Contents (hexadecimal) Upper half byte Lower half byte D 3 0 5 0 1 0 3 0 1

234

P30308-X2058-K160-03-7617

Common questions