Message Controller R3.0-10.09.B09: Billing Interface Manual

Message Controller R3.0-10.09.
B09
Billing Interface Manual
Document Version: 1.0

Document Status: ISSUED
Release Date: 17 Dec 2018
Approved By: Tomas Majer
i
Copyright © Mavenir 2010-2018
All rights reserved. This document is protected by international copyright law and may not be reprinted, reproduced, copied or utilised in whole or in part by any means including electronic,
mechanical, or other means without the prior written consent of Mavenir.
Whilst reasonable care has been taken by Mavenir to ensure the information contained herein is reasonably accurate, Mavenir shall not, under any circumstances be liable for any loss
or damage (direct or consequential) suffered by any party as a result of the contents of this publication or the reliance of any party thereon or any inaccuracy or omission therein. The
information in this document is therefore provided on an ’as is’ basis without warranty and is subject to change without further notice and cannot be construed as a commitment by
Mavenir.
The products mentioned in this document are identified by the names, trademarks, service marks and logos of their respective companies or organisations and may not be used in any
advertising or publicity or in any other way whatsoever without the prior written consent of those companies or organisations and Mavenir.
ii
Table of Contents
Preface x
1 Introduction 1
1.1 Charging events concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.2 Charging triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 SDR formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4 SDR stream types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.4.1 Native stream types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.4.2 Legacy stream types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.5 SDR stream configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.6 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 Native SDR streams 6
2.1 Field types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.2 SDR stream fields encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3 CSV_SM stream type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4 CSV_MAP stream type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.5 CSV_SIP stream type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.6 CSV_SMPP stream type (DRAFT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.7 Field details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.7.1 TON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.7.2 NPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.7.3 SP_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.7.4 SEG_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.7.5 MSG_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.7.6 MSG_MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.7.7 MSG_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.7.8 REJECT_REASON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.7.9 REJECT_METHOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.7.10 SM_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
iii
2.7.11 A_NETWORK_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.7.12 B_NETWORK_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.7.13 A_HLR_MAP_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.7.14 B_HLR_MAP_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.7.15 MAP_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.7.16 MAP_CAUSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.7.17 SM_CONTENT_ENCODING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.7.18 MAP_OPER_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.7.19 NOTIF_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.7.20 UDH_MASK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.7.21 xCOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.7.22 MSG_FLAGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.7.23 DETECT_FLAGS(_SEG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.7.24 BILLING_DATA(_SEG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.7.25 SIGNAL_OPER_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.7.26 SIGNAL_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.7.27 CONTACT_REG_STATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.7.28 CONTACT_REG_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.7.29 STAT_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.7.30 TRACK_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.7.31 TELESERVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.7.32 ODB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.7.33 CALL_BARRING_FEATURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.7.34 NETWORK_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.7.35 LAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.7.36 PARENT_MSG_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.7.37 MAP_OPER_ORIGIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.7.38 HLR_MODIF_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.7.39 REQ_SUBS_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.7.40 BASE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.7.41 ICID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.7.42 UCID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.7.43 LRN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.7.44 SMPP_COMMAND_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.7.45 SMPP_MESSAGE_STATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
2.7.46 SMPP_COMMAND_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
2.7.47 OPER_ORIGIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
2.8 AVRO stream types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
iv
3 Legacy SDR Streams 68
3.1 MCO 2.3 CSV billing files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

3.1.1 Types of SDR parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
3.1.2 MAP SDR stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.1.3 SM SDR stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
3.1.4 Parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

3.1.4.1 Values of MAP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
3.1.4.2 Values of SM parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
3.1.4.3 Values of information flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
3.1.4.4 Values of extended information flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

3.1.4.5 Values of reasons for message rejecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
3.1.4.6 Used structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
3.1.4.7 Network types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
3.1.5 Message ID mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

3.2 Infinity SMSC billing files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
3.2.1 Stream applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
3.2.2 Optional special attribute fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
3.2.3 Custom/extension attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

3.2.4 Stream decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
3.2.5 Supported fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
3.3 Telepath fixed-length billing files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

3.3.2 Field format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
3.3.4 SMPP parameter billing_identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
3.4 SMSC V5 ASN.1 billing files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

3.4.3 ASN.1 tag values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
3.4.4 Compatibility with SMSC V5 ASN.1 CDRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
4 SDR decoding 132

4.1 CSV streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
4.2 ASN.1 streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Acronyms 139
Bibliography 144
v
List of Figures
1.1 3GPP charging reference model (TS 32.240) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 MCO charging triggers overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1 SDR encryption procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 SDR decryption procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
vi
List of Tables
2.1 SDR stream field types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Custom (extdata) field types mapping on SDR stream types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.3 Custom (extdata) field types mapping to SDR stream types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.4 CSV_SM SDR stream type fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.5 CSV_MAP SDR Stream Type Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.6 CSV_SIP SDR stream type fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.7 CSV_SMPP SDR stream type fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.8 Normalized TON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.9 Normalized NPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.10 Service points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.11 Segment types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.12 Message types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.13 Message modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.14 Message statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.15 Reject reasons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.16 Reject methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.17 SM errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.18 Network types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.19 Network types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.20 MAP errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.21 MAP causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.22 Message text encodings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

2.23 MAP operation types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.24 Requested notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.25 Class of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.26 Message flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

2.27 Detect flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.28 Billing data flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.29 Signal Operation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
vii
2.30 Signal Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.31 Contact registration state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.32 Contact registration event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.33 Teleservice identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.34 Operator determined barring flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.35 SMPP network errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.36 UCP network errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.37 GSM network errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
2.38 SMTP network errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.39 Message statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.40 MAP operation origin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.41 HLR modification request from IP-SM-GW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.42 Requested SS-info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.43 Base error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.44 DC internal errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.45 DC AKIF errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
2.46 SMPP command ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.47 SMPP message state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
2.48 Operation origin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.1 Parameter types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

3.2 Possible parameters of MAP SDR stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.3 Possible parameters of SM SDR stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
3.4 MAP_ERROR_CODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
3.5 MAP_CAUSE_OF_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
3.6 MESSAGE_MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
3.7 MSG_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
3.8 PAYLOAD_INFO_ENCODING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
3.9 PAYLOAD_INFO_SINGLE_SHIFT_TAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
3.10 PAYLOAD_INFO_LOCKING_SHIFT_TAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
3.11 MSG_ERROR_CODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
3.12 MSG_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
3.13 INFORMATION_FLAGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
3.14 INFORMATION_FLAGS_EXT_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
3.15 MSG_REJECT_REASON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
3.16 Used structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
3.17 NETWORK_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
3.18 ISMSC SDR stream type fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
3.19 Possible parameters of fixed-length billing stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
viii
3.20 Structure of billing_identification for vendor ID equal to 10000001 (0x81) . . . . . . . . . . . . . . . . . . . . . 117
3.21 SDR fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

3.22 Possible values of status field in ASN.1 and their mapping to MSG_STATUS codes (see Table 3.12). . . . . . . . 121
3.23 ASN.1 address structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
3.24 ASN.1 boolean service (boolser) structure in CallDetailRecord . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
3.25 ASN.1 boolean services (boolser) structure in NotificationRecord . . . . . . . . . . . . . . . . . . . . . . . . . 122

3.26 ASN.1 new services structure (nser) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
3.27 ASN.1 prepaid services (ppPser) structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
3.28 ASN.1 tags CallDetailRecord . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
3.29 ASN.1 tags NotificationRecord . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
ix
Preface
Purpose
The purpose of this document is to describe billing records of Message Controller (MCO) R3.0-10.09.
Audience
The target audience of this document are all Mavenir customers and engineers.
Scope
The scope of this document is to provide essential information on the creation of service detail records (SDR) by MCO and usage
of these charging event records for statistical and (postpaid) billing purposes.
The on-line (prepaid) charging interface is out of the scope of this document since MCO does not provide a standard on-line
charging interface but allows integration with any Diameter-based on-line charging interface. The integration with an on-line
charging interface and related concepts are described in [MCO_GLS_prepaid].
Organisation
This document is divided into the following chapters:

• Chapter 1 provides introduction to the charging events concept and supported SDR formats.
• Chapter 2 provides details about MCO native SDR stream types.
• Chapter 3 provides details about legacy SDR stream types implementing the compatibility with legacy MCO and other systems.
• Chapter 4 provides information on tooling available for streams decoding.
Related documentation
This manual is part of the Mavenir MCO documentation set, which is described in [MCO_DO].
Prior to integration with a statistical and/or billing system the operators must be familiar with the basic MCO concepts and the
terminology described in [MCO_OMAN].
Typographic conventions
In this document, the following typographic conventions are used:
x
Typeface/Symbol Meaning/Used for Example
Refers to a label, value, file name, directory,
The DATA directory contains...
Courier code, constant or other computer component or
This application has S_DOMAIN of value 5.
output.
Set the origAddrHandling parameter to...
Refers to parameters and configuration file
Courier In section [Routing], configure the mapping
sections.
of...
Serves as a placeholder for variable text that Use the <entity>.cfg file name for...
<courier> the user will replace as appropriate to its The SUBSCRIBE_SP(<sp>) action can be
context. used to...
Refers to a system command, process, a
Click the Close button to....
bold keyboard key, and to names of buttons,
Press Ctrl+N to open a new...
windows and options in a GUI.
Jumpstart, the installation procedure on a
Emphasises a new word or term of significance,
SUN T1.
italic and references to documentation or parts of
See the Network Ports table in NGP Operator
documentation.
Manual.
Denotes line continuation; the character should

Line continuation sign
be ignored as the user types the example, and sudo /usr/sbin/tcpdump -w /tmp/ ←-
(carriage return)
Enter should only be pressed after the last line. mco_tcpdump.cap -i any -s0
Refers the user to documentation listed in
[] [ETSI 03.38]
section Bibliography.
% Denotes a Unix regular-user prompt for C shell. % ls
# Denotes a Unix super-user prompt for any shell. # ls
Denotes an OpenVMS Digital Command

$ Language prompt. $ dir
Bridges two keystrokes that should be pressed

- If Ctrl-C does not work, use Ctrl-Alt-Del.
simultaneously.
Denotes a ’note’, a piece of text alongside the

normal text requiring extra attention. Note
Note Note that the system is usually...
Denotes a piece of text providing a tip on a Tip

process or procedure. To enable this feature at start-up, do
Tip
the following ...
xi
Typeface/Symbol Meaning/Used for Example
Denotes an important piece of information

which could affect the possibility of completing
the related task, or which could cause loss of Important
Important data or serious errors. Note that the file MUST be included...
xii
1 Introduction
1.1 Charging events concept
This document describes service detail records (SDRs) generated by MCO.
These records have to be considered charging events recording the state of processing a message at a particular point of the
message life in which a service can be applied. These points are referred to as service points (SP) and creation of an SDR is one
of the services.
Referring to 3GPP 32.240, by recording SDRs MCO implements Charging Trigger Function (CTF), see Figure 1.1. In this model
the CTF produces charging event records only while Charging Data Function (CDF) creates charging detail records (CDRs). The
CDF can apply either a one-to-one mapping between charging events and CDRs or many-to-one (or even more complex) mapping.
The Charging Gateway Function (CGF) serves as an interface to a billing domain.
Billing
CTF SDR
CDF CDR
CGF CDR
Domain
(MCO)
Figure 1.1: 3GPP charging reference model (TS 32.240)
In general, produced SDRs cannot be used directly for billing purposes. A CDF which creates CDRs from MCO SDRs must be
implemented. It can be implemented as an independent system or directly by the charging system itself.
Caution
In any case it is essential to understand the difference between an SDR and a CDR before any steps to integration of
MCO and a (post-paid) billing system are taken. Otherwise there is a risk of a mismatch between the billing system and
MCO capabilities.
1.2 Charging triggers
Message processing is a sequence of steps performed one-by-one. In this sequence there are charging triggers generated by
MCO. Based on these triggers a desired charging model can be applied in charging domain. In each of the applied charging
triggers attributes of a message are exposed to the charging domain as is expected from a charging trigger function (CTF).
MCO records charging triggers as so called "service detail records" (SDRs). Charging system can pull these records and apply
requested charging actions. SDR records can be also used by an analytics systems to visualise processes in the network.
MCO Billing Interface Manual R3.0-10.09.B09

COMMERCIAL-IN-CONFIDENCE ISSUED
Copyright © Mavenir 2010-2018 Page 1 of 144
These triggers can be also pushed towards charging system using a diameter based protocol (Ro and Rf reference points). MCO
is compliant with these reference points and can be configured to speak with vendor specific dialects (e.g. SCAP v2). It supports
various charging models like Immediate Event Charging (IEC) and Event Charging with Unit Reservation (ECUR).
In general, there is a huge number of customized charging systems in the field. There is variary in used parameters (AVPs), differ-
ent charging models and strategies applies, also triggers distribution and failover requirements use to be different (primary/backup,
active/standby).
MCO diameter charing interface is highly configurable and so far is to be able to integrate with any of the available diameter based
charging systems in the field.
This document describes basics of MCO charging triggers, and details available SDR formats and information it can contain.
Diameter based integration with a charging domain is out of the scope of this document. For details contact Mavenir representative.
Message flow
As illustrated by Figure 1.2, a message enters MCO (is submitted) through an interface specific component and leaves the system
(is delivered) through the same or a different interface component. These interface components can initiate a charging trigger per
a signal unit:
• SIP Operation - captures SIP operations received/sent by MCO
• SMPP Operation - captures SMPP commands received/sent by MCO
• MAP Operation - captures GSM MAP operations received/sent by MCO
• SRI Indication - captures MAP SRI-SM requests received by MCO
• SRI Confirmation - captures MAP SRI-SM responses received by MCO
• SRI Phishing - captures MAP SRI-SM queries detected as phishing by MCO
Message
completed
Routing CT
Per rec
KERNEL
queue
& se ssa g e
Routing Complete CT
nt
ipient
g me
e
Final CT
Per m
& se ssa g e
Per me ent
nt
Incoming CT Outgoing CT
& se g m
g me
e
TX RX
Per m
Incoming Complete CT Outgoing Complete CT

ssa g e
SRI-Indication CT Interface MAP operation CT

nal
Per s
SRI-Confirmation CT components SIP operation CT

ig
Per s
ig
nal
SRI-Phishing CT SMPP operation CT

Submission Delivery
Submission result Delivery result
MAP/SIP/SMPP/.. signalling
Figure 1.2: MCO charging triggers overview
TX components are responsible for message submission. These components can initiate charging triggers per message (or
message segment):
• Incoming - captures the message at the end of submission phase

• Incoming Complete - captures the submission response
RX components are responsible for message delivery. These components can initiate charging triggers per message (or message
segment):
• Outgoing - captures message before the delivery attempt (delivery route is known already)
• Outgoing Complete - captures message after the delivery attempt (delivery result is available)
KERNEL components are responsible for message delivery initiation, it can initiate these charging triggers per recipient queue:
• Routing - captures the routing decision when delivery of messages from a queue starts (that means not created for each
message!)
• Routing Complete - captures the routing decision result when delivery of message from a queue ends (kind of delivery result,
not created for each message!)
KERNEL component is also responsible for message completion. Message is completed (removed from MCO) once it is delivered,
or recognized(marked) as undeliverable. In that case it can initiate charging trigger per message (or message segment):
• Final - captures message at the end of its life in the MCO
Message vs. segment
Various protocols have limited size of a single message. However, devices are able to overcome these limitations and expose long
messages to user. Technically, a long message is transported as number of short messages (segments) which are reassmebled
in a device.
MCO is capable to reassemble multiple short messages (segments) into a single long message and expose such a reassembled
message as anny other in charging triggers. However, in that case it is sometimes still needed to apply charging per each segment.
Thus MCO allows to initiate charging triggers for both: individual segments as well as messages.
Integration notes
The following integration notes apply to charging of messages:

• Incoming CT and Final CT is used to see submissions and final state of a message.
• Outgoging Complete CT is used to see individual delivery attempts.
• Incoming Complete CT does not find a use for charging.
• Routing CT and Routing CT is not used for charging.
• Each message is identified by a unique message id.
• A message created inside MCO (e.g. delivery receipt) contains parent message id refering to the original message.
Note
Although charging triggers are initiated from different places in the system, all these are recorded in a single stream.
Individual charging triggers can be recognized typically by service point (SP_ID) attribute.
1.3 SDR formats
MCO produces SDRs in the CSV format.

For backward compatibility with Infinity SMSC it is also possible to write SDRs in the tab-separated-values (TSV) format (techni-
cally, this format is CSV with the tab separator and without delimiters).
For backward compatibility with Telepath IP SMSC it is also possible to write SDRs in the fixed-length billing format (technically,
this format is CSV without separators and delimiters).
For backward compatibility with SMSC V5 it is also possible to write SDRs in the ASN.1 notation.

1.4 SDR stream types
MCO is able to produce multiple SDR streams at each service point. Each stream produces records in a specific format; the list
of SDR fields (mostly deduced from message attributes) is configurable per stream.
1.4.1 Native stream types
The following SDR stream types are native for MCO R3.0:
• CSV_SM
This CSV-based SDR stream type contains records created in the Incoming, Incoming Complete, Outgoing, Outgoing Complete,
Final and Replace service points.
A message on this level is normalised and incoming/outgoing interface-agnostic.
• CSV_MAP
This CSV-based SDR stream type contains records created in the MAP Operation, Incoming SRI-SM-IND and Incoming SRI-
SM-CNF service points.
A message on this level is not a real short message (SM) but it is a GSM MAP operation.
• CSV_SIP
This CSV-based SDR stream type contains records created in the SIP Operation service point. It contains SIP signalling
messages going from or to the IP-SM-GW.
A message on this level is not a real SIP message but it is a set of parameters used for further processing.
• CSV_SMPP
This CSV-based SDR stream type contains records created in the SMPP Operation service point. It contains all SMPP protocol
specific operations going from or to an LA.
These SDR streams consist of fields which naming is consistent with naming of message attributes in RBDL.
1.4.2 Legacy stream types
The following SDR stream types are deprecated and persist due to the backward compatibility with legacy products:
• CSV_SM_23
This CSV-based SDR stream type is equivalent to the CSV_SM stream of MCO R2.3. We recommend migrating the system to
the native CSV_SM stream.
This stream is deprecated because of the number of fields with unclear/unexpected behaviour.
• CSV_MAP_23
This CSV-based SDR stream type is equivalent to the CSV_MAP stream of MCO R2.3. We recommend migrating the system
to the native CSV_MAP stream.
This stream is deprecated because of the number of fields with unclear/unexpected behaviour.
• CSV_ISMSC
This CSV-based SDR stream type mimics the Infinity SMSC billing interface. However, the 100% compatibility is not guaranteed
since the implementation of MCO differs from Infinity SMSC and some minor differences are unavoidable.
• CSV_TP
This fixed-length field stream type mimics the Telepath IP SMSC billing interface. However, the 100% compatibility is not
guaranteed since the implementation of MCO differs from Telepath IP SMSC and some minor differences are unavoidable.
• ASN1_V5
This ASN.1 stream type mimics the SMSC V5 billing interface. However, the 100% compatibility is not guaranteed since the
implementation of MCO differs from SMSC V5 and some minor differences are unavoidable.

1.5 SDR stream configuration
To show configuration of SDRs, type the following command in CML:

MCO> @sdr_conf.oam
For detailed information on SDR streams configuration, refer to [MCO_OMAN].
1.6 Limitations
Once a single CSV record exceeds 255 KB in length, the currently recorded field is truncated and the remaining fields are left
empty (filled by the <skip> text). The maximum size of a single CSV record in an SDR stream is 256 KB (hard limit).

2 Native SDR streams
This chapter describes SDR stream types native to MCO R3.0. These streams are written in the CSV format.
2.1 Field types
SDR stream field types
Each field in a stream is of a specific type; the format in which a particular field type is written can be specified. The full list of
available field types is listed in Table 2.1.
Table 2.1: SDR stream field types
Field type Description Example

INT 64-bit integer number in the decimal format 3 denotes number 3.
Number in the decimal format, denoting an element 0 denotes the first element of a specific enumeration
ENUM
from an enumeration associated with a particular field.
Number in the decimal format, 0 denotes value false
BOOL 0 denotes a bool attribute set to false.
and 1 denotes value true.
Generic address, a structure consisting of Type of 1.1.1234567890 denotes an address with TON
ADDR Number (TON), Numbering Plan Indicator (NPI) and international, NPI telephone and address
address characters/digits digits 1234567890.
SCCP address, a structure consisting of routing 1.701.8..1.1.12334567890 denotes an
indicator (RI), point code (PC), subsystem number address with RI 1, PC 701, SSN 8, empty TT, TON
S-ADDR
(SSN), translation type (TT), type of number (TON), international, NPI telephone and address digits
numbering plan indicator (NPI) and address digits 1234567890.
STRING UTF-8 encoded string TEST_LA denotes string TEST_LA.
Octet string, each octet dumped as a hexadecimal 4142434445 denotes a stream of ABCDE
O-STRING
number characters.
Bit field consisting of 64 flags in the hexadecimal 80000001800000ff denotes flag_1 to
FLAGS
format. flag_8, flag_32, flag_33 and flag_64.
UTC time stamp with seconds precision; UNIX time
T-STAMP 0 denotes January 1st 1970, 00:00:00.
as a decimal number
Addresses
TON and NPI values of address fields (ADDR and S-ADDR fields types) are not following network values which differ per protocol,
but are presented in normalized, protocol agnostic, format, see Section 2.7.1 and Section 2.7.2.
SDR stream field types formatting
Available format strings differ per field type. These strings allow changing the format in which a field of a particular type is written

into SDR, e.g. whether a number is written in decimal or hexadecimal format. The full list of available formats is provided in
Table 2.2.
Table 2.2: Custom (extdata) field types mapping on SDR stream types
Field type Format string Default format

String specifying the human-readable string format. The formatting
applies only to $custom.attributes.
INT Number in the decimal format
DATE(DEFAULT,gmt) - GMT time in format %Y%m%d%H%M%SZ.
DATE(DEFAULT,local) - Local time in format %Y%m%d%H%M%S .
ENUM N/A Number in the decimal format
BOOL N/A Number in the decimal format0 or 1
String specifying which address sub-parts are recorded and in
which order
t - TON All sub-parts as if the tna format
ADDR
was specified
n - NPI
a - address string
String specifying which address sub-parts are recorded and in
which order
r - routing indicator
p - point code
s - subsystem number All sub-parts as if the rpsTtna
S-ADDR
format was specified
T - translation type
t - GT nature of address
n - GT numbering plan indicator
a - GT address string
String specifying whether the string is recorded in hexadecimal or
human readable form and the maximum length of the output. The
string may be empty or must have one of these formats:
t|h|t<number>|h<number>|<number> where:
t
means open plain text (human readable).
Open plain text as if the t format and
STRING h maximum length of 255 characters
means hexadecimal form. was specified.
<number>
is a positive number specifying the maximum length of the
output. 0 means that the maximum length of the output is
unlimited.
Sequence of bytes, each byte is

Integer number greater or equal 0 specifying the maximum number
encoded as a hexadecimal number,
O-STRING of output bytes. 0 means that the maximum length of the output is
two characters per byte. Default
unlimited.
maximum length is 255.
String specifying which format is used for recording flags:
A hexadecimal number as if the h
FLAGS h - flags are recorded as a number in the hexadecimal format
format was specified
d - flags are recorded as a number in the decimal format

Table 2.2: (continued)
Field type Format string Default format

String specifying whether the timestamp is recorded as a number
(UNIX time) or as a human-readable string:
• DATE(DEFAULT,gmt) - GMT time in format %Y%m%d%H%M%SZ.
• DATE(DEFAULT,local) - Local time in format %Y%m%d%H%M%S .
• DATE(DEFAULT) - The same as previous (local time).
UTC time as a UNIX timestamp as if
• DATE(TIME_T) - UTC time as a UNIX timestamp 1 2 3
.
T-STAMP the DATE(TIME_T) format was
• DATE(MSEC) - Local time as a UNIX timestamp in milliseconds 4 . specified.
• DATE(MSEC,gmt) - Same as DATE(DEFAULT,gmt), but
seconds are suffixed with 3 digits denoting milliseconds.
• DATE(MSEC,local) - Same as DATE(DEFAULT,local), but
seconds are suffixed with 3 digits denoting milliseconds.
SDR stream field aliases
Each SDR stream field has a unique name and can be present only once in the fields table. When multiple occurrences are
needed, typically with different formatting, a unique alias defined as field_name#unique_custom_name can be added to the
fields table. A full alias name is then also present in the CSV file header.
Example:
To configure the A_ADDR address as separate TON ,NPI and address string values, configure the following three aliases:
sdr_conf.streams[CSV_SM].fields.add name=A_ADDR#ton format=t
sdr_conf.streams[CSV_SM].fields.add name=A_ADDR#npi format=n
sdr_conf.streams[CSV_SM].fields.add name=A_ADDR#addr format=a
Custom message fields in SDR
Custom (extdata) message fields are configurable by operator. Names of the fields are in format $<attr_group>.<attr_name>
where <attr_group> and <attr_name> can be any string containing alphanumerical characters. There are several custom
message field types. Each custom message field type is mapped to an SDR field type as defined in Table 2.3.
Table 2.3: Custom (extdata) field types mapping to SDR stream types
Custom attribute type SDR field type Example

uint8 INT See field type INT in Table 2.1.
bool BOOL See field type BOOL in Table 2.1.
string STRING See field type STRING in Table 2.1.
addr ADDR See field type ADDR in Table 2.1.
binary O-STRING See field type O-STRING in Table 2.1.
1
Number of seconds since January 1 1970.
2
Number of milliseconds since January 1 1970. Please note that the timestamp is based on the local time of the node where the record is logged.
3
Applies to those fields for which milliseconds are recorded: LOG_TIME. The timestamp for other fields is roundup with 0.999ms accuracy.
4
Number of milliseconds since January 1 1970.

Special characters in SDR
It is possible to configure MCO to omit special characters when required by the billing system.
2.2 SDR stream fields encryption
Encryption is available for native stream types and for field types: O-STRING , STRING , ADDR and S-ADDR.
MCO uses the AES encryption in the CFB mode for fields content encryption. This encrypted content is prefixed with an initial-
ization vector and then encoded into the base64 encoding. The AES encryption key is randomly generated each time when the
SDR AF configuration is reloaded. The AES encryption key is encrypted by a public RSA key with OAEP padding, encoded into
base64 and written as part of a header in the stream file. The format of the RSA public key must be PEM.
RSA Public Key
Encrypt AES Key

AES Key using
BASE64 encoding
(random on reload) RSA Public Key
(OAEP Padding)
header
Encrypt <field_value> <field_name>(ENCRYPT(<base64str>))
Init.vector using
(random + incremental) AES Key and Init.vector value
(CFB mode)
<base64str>
Concatenate
Init.vector
<field_value> BASE64 encoding
and
encrypted value
Figure 2.1: SDR encryption procedure

RSA Private Key
Decrypt AES Key

using AES Key
BASE64 decoding
RSA Private Key (decrypted from header)
(OAEP Padding)
header
<field_name>(ENCRYPT(<base64str>)) Decrypt <field_value>

using
value <field_value>
AES Key and Init.vector
(CFB mode)
<base64str>
Split on
Init.vector
BASE64 decoding Init.vector
and
encrypted value
Figure 2.2: SDR decryption procedure
Example:
The example output of csv_decode for the encrypted SM_TEXT field of the CSV_SM stream for a message containing text "Hello
world!":
$ csv_decode CSVSM_rnd-vm-13-81_20181029104439Z.csv
================== CSVSM_rnd-vm-13-81_20181029104439Z.csv - START - ==================
.
.
.
SM_TEXT(ENCRYPT(B73QwTX0ueR13H/KHfmfoGmznRIzWo9Vr8iZk3Q4Cb9kYULC1JASmwcjs8lb0A3s80QO0o+Om+ ←-
oSa3H78dLMsrLnrRRBrJKdHPoFYhFHaUZLKcw5TCQRBjhVT0BpTp81cmCd7wOuRfGTMu7cuWbhhHcs8G5bMBYpY12Wm6 ←-
/ApJguAWWMWikTL0k8aLq6+z1M3zRNvtcBx1EVIZoK6dPok/S1LYx3QvoJmXXuLdYGrMeTLlY6zoWbFEG/ ←-
glSmYw7B+BXjHXsuZqfvJYH5lR5zA2QZdbBaKeTUS2UaXvc0EC3VAsd+mmkJ+ ←-
YejfG4tI1Kp5rLF98ErYVNJpTJfZv+zJg==)): jEQoaes+APFDxAiYBbnSse4hIX1c3j94lepf2Q==
.
.
.
================== CSVSM_rnd-vm-13-81_20181029104439Z.csv - END - ====================
Tip
Use csv_decode with parameter -k to specify the path to the RSA private key to see decrypted content of encrypted
fields.
$ csv_decode CSVSM_rnd-vm-13-81_20181029104439Z.csv -k ~/private.pem

.
.
.

SM_TEXT(ENCRYPT(B73QwTX0ueR13H/KHfmfoGmznRIzWo9Vr8iZk3Q4Cb9kYULC1JASmwcjs8lb0A3s80QO0o+Om+ ←-
oSa3H78dLMsrLnrRRBrJKdHPoFYhFHaUZLKcw5TCQRBjhVT0BpTp81cmCd7wOuRfGTMu7cuWbhhHcs8G5bMBYpY12Wm6 ←-
/ApJguAWWMWikTL0k8aLq6+z1M3zRNvtcBx1EVIZoK6dPok/S1LYx3QvoJmXXuLdYGrMeTLlY6zoWbFEG/ ←-
glSmYw7B+BXjHXsuZqfvJYH5lR5zA2QZdbBaKeTUS2UaXvc0EC3VAsd+mmkJ+ ←-
YejfG4tI1Kp5rLF98ErYVNJpTJfZv+zJg==)): Hello world!
.
.
.
2.3 CSV_SM stream type
The CSV_SM stream type is used to record messages on the protocol agnostic level. The full list of all available fields within this
stream type is contained in Table 2.4; the # column is just a row number in the table.
Table 2.4: CSV_SM SDR stream type fields
# Field name Field type Description Details

1 LOG_TIME T-STAMP Time of creating the record
2 SP_ID ENUM Service point from which the record originates Section 2.7.3
Indicator whether the record is for a message or
3 SEG_TYPE ENUM Section 2.7.4
segment
Indicator whether the record is for a message or
4 MSG_TYPE ENUM Section 2.7.5
receipt
5 MSG_ID O-STRING Unique identifier of a message
Unique identifier (MSG_ID) of a related (parent)
6 MSG_PARENT_ID O-STRING message, e.g. for a notification, master message of
a segment or generated message
7 MSG_MODE ENUM Message mode Section 2.7.6
8 MSG_STATUS ENUM Status of a message Section 2.7.7
9 REJECT_REASON ENUM Reason for rejection (blocking) of a message Section 2.7.8
10 REJECT_METHOD ENUM Method used for rejection (blocking) of a message Section 2.7.9
Error code used for rejection of a message
11 SM_ERROR ENUM submission (IN/INC SP) or message delivery Section 2.7.10
(OUT/OUTC SP)
12 SUBMIT_TIME T-STAMP Date and time of a message submission
Date and time of a message expiration, i.e. the latest
13 EXPIRY_TIME T-STAMP requested date and time the message is kept in
storage and delivery attempts are made
14 DELIVERY_TIME T-STAMP Date and time of the last delivery attempt
Date and time a message accepted for delivery is
15 DONE_TIME T-STAMP
removed from the system
Priority of a message. Messages with a higher
16 PRIORITY INT priority are queued for delivery before messages
with a lower priority.
This field describes subscription of a message to
17 NOTIF_REQ FLAGS Section 2.7.19
notifications.
18 NR_DEL_ATT INT Number of delivery attempts of a message
19 NR_DEL_SUB_ATT INT Number of delivery sub-attempts of a message
Source application port of Application Port
20 UDH_SRC_PORT INT
Addressing (APA) IE of UDH


21 UDH_DST_PORT INT Destination application port of APA IE of UDH.
22 A_ADDR ADDR Originator MSISDN address
Untranslated (as submitted) originator MSISDN
23 A_UADDR ADDR
address
24 A_TADDR ADDR Translated (normalised) originator MSISDN address
25 B_ADDR ADDR Recipient MSISDN address
Untranslated (as submitted) recipient MSISDN
26 B_UADDR ADDR
address
27 B_TADDR ADDR Translated (normalised) recipient MSISDN address
28 A_IMSI ADDR Originator IMSI address
29 B_IMSI ADDR Recipient IMSI address
Originator IMSI address as received in an inbound
30 MAP_A_IMSI ADDR
operation
Recipient IMSI address as received in an inbound
31 MAP_B_IMSI ADDR
operation
Alphanumeric name of an originator/source
32 A_AIM_NAME STRING
application or interface
Alphanumeric name of a recipient/destination
33 B_AIM_NAME STRING
application or interface
34 A_NETWORK_TYPE ENUM Originator/source network type Section 2.7.11
35 B_NETWORK_TYPE ENUM Recipient/destination network type Section 2.7.12
36 A_SC ADDR MAP SC address of an inbound operation
37 B_SC ADDR MAP SC address of an outbound operation
MSC address serving an originator MSISDN as
38 A_MSC ADDR
obtained from an HLR
MSC address serving a recipient MSISDN as
39 B_MSC ADDR
SGSN address serving an originator MSISDN as
40 A_SGSN ADDR
SGSN address serving a recipient MSISDN as
41 B_SGSN ADDR
SCCP address (CgPA) of a network element
42 S_CGPA S-ADDR
initiating an inbound operation
SCCP address (CdPA) of a network element to
43 D_CDPA S-ADDR
which an outbound operation is destined.
44 D_CGPA S-ADDR
responding to an outbound operation
SCCP address (CgPA) of an HLR responding to an
45 A_HLR_CGPA S-ADDR outbound SRI-SM operation for an originator
MSISDN
46 B_HLR_CGPA S-ADDR
outbound SRI-SM operation for a recipient MSISDN
MAP error code of an outbound SRI-SM operation
47 A_HLR_MAP_ERROR ENUM Section 2.7.13
for an originator MSISDN
48 B_HLR_MAP_ERROR ENUM Section 2.7.14
for a recipient MSISDN
49 MAP_ERROR ENUM Resulting MAP error code of an inbound operation Section 2.7.15
Resulting MAP cause of failure of an inbound
50 MAP_CAUSE ENUM Section 2.7.16
operation


Network error - context of the value is given by
51 NETWORK_ERROR INT
B_NETWORK_TYPE.
52 SM_TEXT STRING Message/segment text in the UTF8 encoding
Number of human readable characters in
53 SM_TEXT_LENGTH INT
message/segment text
Message/segment content (without UDHs) recorded
54 SM_CONTENT O-STRING
in its original encoding
Message/segment content (without UDHs) size in
55 SM_CONTENT_SIZE INT
bytes
56 SM_CONTENT_ENCODING ENUM Message/segment content encoding Section 2.7.17
57 SM_UDH O-STRING UDHs of a message
58 SM_UDH_SIZE INT Size of UDHs in a message
59 SM_UDH_SEG O-STRING UDHs of a segment of a message
60 SM_UDH_SEG_SIZE INT Size of UDHs in a segment of a message
Mask indicating a (configured) set of UDH IEs
61 UDH_MASK FLAGS Section 2.7.20
matching a segment of a message
Mask indicating a (configured) set of UDH IEs
62 UDH_MASK_SEG FLAGS Section 2.7.20
matching a segment of a message
63 SM_SEGMENT_MAX INT Number of segments in a concatenated message
Sequence number of the current segment of a
64 SM_SEGMENT_CURRENT INT
concatenated message
65 SM_SEGMENT_REF INT Concatenated message reference number
66 A_COS FLAGS Class-of-Service of originator MSISDN Section 2.7.21
67 B_COS FLAGS Class-of-Service of recipient MSISDN Section 2.7.21
Class-of-Service of source transport (network
68 S_COS FLAGS Section 2.7.21
domain)
Class-of-Service of destination transport (network
69 D_COS FLAGS Section 2.7.21
domain)
Domain (MVNO) ID associated with an originator
70 A_DOMAIN INT
MSISDN
Domain (MVNO) ID associated with a recipient
71 B_DOMAIN INT
MSISDN
Domain (Network) ID associated with a source
72 S_DOMAIN INT
network element
Domain (Network) ID associated with a destination
73 D_DOMAIN INT
network element
74 MSG_FLAGS FLAGS Miscellaneous message flags Section 2.7.22
Flags indicating result per validation type applied to
75 DETECT_FLAGS FLAGS Section 2.7.23
a message
76 DETECT_FLAGS_SEG FLAGS Section 2.7.23
a segment of a message
77 RBDL_FLAGS FLAGS RBDL flags of a message
78 RBDL_FLAGS_SEG FLAGS RBDL flags of a segment
79 BILLING_DATA FLAGS On-line charging information flags of a message Section 2.7.24
On-line charging information flags of a segment of a
80 BILLING_DATA_SEG FLAGS Section 2.7.24
message
List of entries providing details of miscellaneous
81 STAT_DATA STRING Section 2.7.29
screening results
82 S_ADDR ADDR Sources (network/IP/uri) address


83 D_ADDR ADDR Destination (network/IP/uri) address
84 A_BILL_ID O-STRING Originating (ESME) billing identifier
85 S_CONS STRING Source (LA) consolidation field
86 D_CONS STRING Destination (LA) consolidation field
87 PROTOCOL_ID INT Protocol Identifier, see TP-PID in [3GPP_23.040]
A list of RBDL rule names of rules applied to the
88 TRACK_DATA STRING Section 2.7.30
message
89 TELESERVICE INT Teleservice identifier (ANSI MAP) Section 2.7.31
90 SERVICE_TYPE_ID INT (SMPP) service type ID
91 SERVICE_TYPE STRING (SMPP) service type
Reference number assigned to the message by
92 MSG_REF INT
originator party
Local (network/IP/port) address of an inbound
93 S_LADDR ADDR
operation
Local (network/IP/port) address of an outbound
94 D_LADDR ADDR
operation
Identifier of message generation template which had
95 MSG_TEMPLATE_ID INT
been used for generation of the message
96 A_USER_AGENT STRING Originator user agent header field
97 B_USER_AGENT STRING Recipient user agent header field
98 A_LASN INT Number uniquely identifying originating/source LA
99 B_LASN INT Number uniquely identifying recipient/destination LA
100 ADT_PROFILE INT Source Address translation profile ID
Importance of a message. Messages with a higher
101 IMPORTANCE INT importance are queued for delivery before messages
with a lower importance.
102 CBN ADDR Call-back number
103 A_MIN ADDR Mobile identification number related to the originator
104 B_MIN ADDR Mobile identification number related to the recipient
105 B_ESN INT Electronic serial number related to the recipient
106 ODB FLAGS Operator determined barring data Section 2.7.32
107 CALL_BARRING_FEATURES STRING List of call barring features Section 2.7.33
108 IR_PROFILE INT Intelligent retry profile ID
109 SCHEDULED_TIME T-STAMP Preferred date and time of a message delivery
Constructed IMSI address (MT correlation ID) used
110 F_IMSI ADDR
for MT-FW-SM interception
111 A_IMEI STRING Originator IMEI
112 B_IMEI STRING Recipient IMEI
Notification address to which delivery receipts are
113 N_ADDR ADDR
sent
114 SUSPEND_TIME T-STAMP Date and time till which a message is suspended
115 NR_SUSPENDED INT Number of times a message has been suspended
116 REMOTE_MSG_ID STRING Message ID returned by a remote system
117 A_LAI STRING Originator Location Area Identification Section 2.7.35
118 PARENT_MSG_STATUS ENUM Status of a parent message Section 2.7.36
119 SYSTEM_NAME STRING The deployment specific product system name


Duration of processing a message in the system, i.e.
120 DURATION INT from a submission to an SDR creation at the actual
point of the message processing (in milliseconds)
Duration of the submission phase, i.e. from a
121 A_DURATION INT submission to an SDR creation in the Incoming SP
(in milliseconds)
Duration of the (last) delivery phase, i.e. from
122 B_DURATION INT fetching from the MCO buffer to an SDR creation in
the Outgoing Complete SP (in milliseconds)
123 A_CID INT Cell ID
124 A_LAC INT Location Area Code
125 A_ROUTE INT Submission price
126 A_PRICE INT Submission route
127 BASE_ERROR ENUM Base cause of an operation failure Section 2.7.40
128 A_ICID O-STRING IMS charging identifier Section 2.7.41
129 A_UCID O-STRING Untranslated Cell-ID Section 2.7.42
130 LRN STRING Location Routing Number Section 2.7.43
Concatenated content of P-Access-Network-Info of
131 A_NPLI STRING
the IMS originator provided by network
132 A_UPLI STRING
the IMS originator provided by user
133 B_NPLI STRING
the IMS recipient provided by network
134 B_UPLI STRING
the IMS recipient provided by user
135 S_NETWORK ADDR Source network address
136 D_NETWORK ADDR Destination network address
This field contains a value of field TP-DCS as
defined in [3GPP_23.040]. When a message is AO,
137 GSM_DCS INT
this field contains a value of field data_coding as
defined in SMPP protocol specification.
Placeholder to produce an empty field in a CSV
138 EMPTY_FIELD N/A
record
Any custom attribute specified by rbdl_conf.
139 $custom.attributes CUSTOM
extdata
2.4 CSV_MAP stream type
The CSV_MAP stream type is used to record messages on the GSM MAP level. The list of all available fields of this stream type is
given in Table 2.5; the # column is just a row number in the table.
Table 2.5: CSV_MAP SDR Stream Type Fields



4 MAP_OPER_TYPE ENUM Identifier of a GSM MAP transaction Section 2.7.18
7 A_IMSI ADDR Originator IMSI address
9 MAP_A_IMSI ADDR Originator IMSI address as received in an operation
10 MAP_B_IMSI ADDR Recipient IMSI address as received in an operation
11 S_CGPA S-ADDR
initiating an operation
SCCP address (CdPA) of a network element to
12 D_CDPA S-ADDR
which an operation is destined.
13 D_CGPA S-ADDR
responding to an operation
14 A_HLR_CGPA S-ADDR outbound SRI-SM operation for an originator
MSISDN
15 B_HLR_CGPA S-ADDR
outbound SRI-SM operation for a recipient MSISDN
16 A_HLR_MAP_ERROR ENUM Section 2.7.13
for an originator MSISDN
17 B_HLR_MAP_ERROR ENUM Section 2.7.14
for a recipient MSISDN
18 A_SC ADDR MAP SC address associated with an originator
19 B_SC ADDR MAP SC address associated with an recipient
20 MAP_ERROR ENUM Resulting MAP error code of an operation Section 2.7.15
21 MAP_CAUSE ENUM Resulting MAP cause of failure of an operation Section 2.7.16
MSC address serving an originator MSISDN as
22 A_MSC ADDR
SGSN address serving an originator MSISDN as
23 A_SGSN ADDR
MSC address serving a recipient MSISDN as
24 B_MSC ADDR
SGSN address serving a recipient MSISDN as
25 B_SGSN ADDR
26 MAP_DATA_LOAD O-STRING Payload data in a GSM MAP request
27 MAP_RESP_DATA_LOAD O-STRING Payload data in a GSM MAP response
28 A_COS FLAGS Class-of-Service of originator MSISDN Section 2.7.21
29 B_COS FLAGS Class-of-Service of recipient MSISDN Section 2.7.21
Class-of-Service of source transport (network
30 S_COS FLAGS Section 2.7.21
domain)
Class-of-Service of destination transport (network
31 D_COS FLAGS Section 2.7.21
domain)
Domain (MVNO) ID associated with an originator
32 A_DOMAIN INT
MSISDN
Domain (MVNO) ID associated with a recipient
33 B_DOMAIN INT
MSISDN


Domain (Network) ID associated with a source
34 S_DOMAIN INT
network element
Domain (Network) ID associated with a destination
35 D_DOMAIN INT
network element
36 MSG_FLAGS FLAGS Miscellaneous message flags Section 2.7.22
Flags indicating validations which marked the
message as suspicious
38 DETECT_FLAGS_SEG FLAGS Section 2.7.23
a segment of a message
39 RBDL_FLAGS FLAGS RBDL flags of a message
40 RBDL_FLAGS_SEG FLAGS RBDL flags of a segment
41 REJECT_REASON ENUM Reason for rejection (blocking) of a message Section 2.7.8
42 REJECT_METHOD ENUM Method used for rejection (blocking) of a message Section 2.7.9
43 A_LAI STRING Originator Location Area Identification Section 2.7.35
44 SYSTEM_NAME STRING The deployment specific product system name
45 MAP_OPER_ORIGIN ENUM Inbound/outbound operation indicator Section 2.7.37
46 HLR_MODIF_REQ ENUM HLR modification request in an ATM operation Section 2.7.38
47 ODB FLAGS Operator determined barring data Section 2.7.32
48 CALL_BARRING_FEATURES STRING List of call barring features Section 2.7.33
49 REQ_SUBS_INFO STRING Requested subscription information Section 2.7.39
50 A_ICID O-STRING IMS charging identifier Section 2.7.41
51 A_UCID O-STRING Untranslated Cell-ID Section 2.7.42
52 LRN STRING Location Routing Number Section 2.7.43
53 B_NPLI STRING
the IMS recipient provided by network
54 B_UPLI STRING
the IMS recipient provided by user
55 SIGNAL_TYPE ENUM Signal type indicating direction of the signal Section 2.7.26
56 A_IMEI STRING ATI IMEI
57 EMPTY_FIELD N/A
record
extdata
2.5 CSV_SIP stream type
The CSV_SIP stream type is used to record messages on the SIP level. The list of all available fields of this stream type is given
in Table 2.6; the # column is just a row number in the table.
Table 2.6: CSV_SIP SDR stream type fields



3 SIGNAL_OPER_TYPE ENUM Signal operation type Section 2.7.25
4 SIGNAL_TYPE ENUM Signal type indicating direction of the signal Section 2.7.26
9 B_IMEI STRING Recipient IMEI
10 A_SC ADDR MAP SC address of an inbound operation
11 B_SC ADDR MAP SC address of an outbound operation
12 A_USER_AGENT STRING Originator user agent header field
13 B_USER_AGENT STRING Recipient user agent header field
14 S_ADDR ADDR Sources (network/IP/uri) address
15 D_ADDR ADDR Destination (network/IP/uri) address
Expired parameter of a SIP register or parsed
16 EXPIRES INT
parameter from the SIP NOTIFY XML body
State of contact registration in the IMS core. This is
17 CONTACT_REG_STATE INT parsed from the XML body of SIP NOTIFY (third Section 2.7.27
party registration).
Contact registration event parsed from the XML body
18 CONTACT_REG_EVENT INT Section 2.7.28
of SIP NOTIFY (third party registration).
19 CALL_ID STRING Call-Id from the SIP header
Miscellaneous message flags showing e.g. SMSIP
20 MSG_FLAGS FLAGS Section 2.7.22
flag
a message
22 CONTACT STRING Contact header of the SIP request
Payload data in a GSM MAP request (When
23 MAP_DATA_LOAD O-STRING decoding of 24.011 part of message fails, both
24.011 and 03.40 parts are stored here)
24 MAP_RESP_DATA_LOAD O-STRING Payload data in a GSM MAP response
25 MSG_REF INT Message reference number from layer 24011
26 SIP_RESP_CODE INT SIP response code
27 EMPTY_FIELD N/A
record
extdata
2.6 CSV_SMPP stream type (DRAFT)
The CSV_SMPP stream type is used to record operations on the SMPP level. The list of all available fields of this stream type is
given in Table 2.7; the # column is just a row number in the table.

Table 2.7: CSV_SMPP SDR stream type fields

Service point from which the record
2 SP_ID ENUM Section 2.7.3
originates
3 OPER_ORIGIN ENUM Inbound/outbound operation indicator Section 2.7.47
Identificates the application which
4 AIM_NAME STRING
processed operation
5 PDU_SIZE INT Size of PDU on the network
6 SMPP_COMMAND_ID ENUM Type of SMPP operation Section 2.7.44
7 SMPP_COMMAND_STATUS ENUM SMPP command status Section 2.7.46
8 SMPP_SEQUENCE_NUMBER INT SMPP sequence number
9 SYSTEM_ID STRING System ID
10 PASSWORD STRING Password
11 SYSTEM_TYPE STRING (SMPP) system type
12 SMPP_INTERFACE_VERSION INT SMPP interface version
13 SERVICE_TYPE STRING (SMPP) service type
16 SMPP_ESM_CLASS INT SMPP esm class
17 SMPP_PROTOCOL_ID INT SMPP protocol id
18 SMPP_PRIORITY_FLAG INT SMPP priority flag
19 SMPP_SCHEDULE_DELIVERY_TIME STRING SMPP schedule delivery time
Preferred date and time of a message
20 SCHEDULED_TIME T-STAMP
delivery
21 SMPP_VALIDITY_PERIOD STRING SMPP schedule delivery time
Date and time of a message expiration,
i.e. the latest requested date and time
22 EXPIRY_TIME T-STAMP
the message is kept in storage and
delivery attempts are made
23 SMPP_REGISTERED_DELIVERY INT SMPP registered delivery
24 SMPP_REPLACE_IF_PRESENT_FLAG INT SMPP replace if present flag
25 SMPP_DATA_CODING INT SMPP data coding
Indicates the short message to send from
26 SMPP_SM_DEFAULT_MSG_ID INT a list of pre-defined (canned) short
messages
27 SM_UDH_SIZE INT Size of UDHs in a message
28 SM_UDH O-STRING UDHs of a message
Message/segment content (without
UDHs) size in bytes or if
29 SM_CONTENT_SIZE INT
DETECT_FLAGS contains infoMalformed
then it is size of original PDU
Message/segment content (without
UDHs) recorded in its original encoding
30 SM_CONTENT O-STRING
or if DETECT_FLAGS contains
infoMalformed then it is original PDU
Number of human readable characters in
31 SM_TEXT_LENGTH INT
message/segment text
Message/segment text in the UTF8
32 SM_TEXT STRING
encoding


Flags indicating result per validation type
applied to a message
34 SMPP_MESSAGE_ID O-STRING SMPP unique identifier of a message
36 SMPP_MESSAGE_STATE ENUM SMPP message state Section 2.7.45
37 SMPP_ERROR_CODE INT SMPP error code
38 SMPP_FINAL_DATE STRING SMPP final date
Date and time a message accepted for
39 DONE_TIME T-STAMP
delivery is removed from the system
A single ESME address or a range of
40 SMPP_ESME_ADDR ADDR
ESME addresses served via session
Placeholder to produce an empty field in
41 EMPTY_FIELD N/A
a CSV record
2.7 Field details
2.7.1 TON
TON value is not following protocol specifications but is presented in a normalized way.
Table 2.8: Normalized TON
Value Name Description

0 Unknown The type of number is unknown
1 International International number
2 National National number
3 Network Network-specific number
4 Short Short/subscriber number
5 Alpha Alphanumeric number
6 Abbreviated Abbreviated number
32 Spare 1 Spare code for original value 1


64 URI Uniform Resource Identifier number
65 IP Internet Protocol (IP) number
2.7.2 NPI
NPI value is not following protocol specifications but is presented in a normalized way.
Table 2.9: Normalized NPI

0 Unknown Numbering plan is unknown
1 Telephone Telephone (ISDN / E.164) numbering plan
3 Data Data (X.121) numbering plan
4 Telex Telex (F.69) numbering plan
5 SC_specific_1 Service centre (vendor)-specific (1) numbering plan
6 E212 IMSI (E.212) numbering plan
7 SC_specific_2 Service centre (vendor)-specific (2) numbering plan
8 National National specific numbering plan
9 Private Private numbering plan
10 Ermes European radio messaging system numbering plan
14 Internet/IPv4 Internet/IPv4 numbering plan


64 TEL TEL URI numbering plan
65 SIP SIP URI numbering plan
66 Internet/IPv6 Internet/IPv6 numbering plan
67 EMAIL EMAIL URI numbering plan
2.7.3 SP_ID
This field determines the service point in which a record has been created.
Table 2.10: Service points

1 IN Incoming service point
2 INC Incoming Complete service point
3 OUT Outgoing service point
4 OUTC Outgoing Complete service point
5 FINAL Final service point
6 REPLACE Message replace service point
7 RT Routing service point
12 EVENT Service-Event service point
13 MAP_OPER MAP Operation service point
14 SRI_IND SRI Indication service point
15 SRI_CNF SRI Confirmation service point
16 RTC Routing complete service point
17 SRI_PHISHING SRI phishing detected service point
18 SIP_OPER SIP Operation service point
19 SMPP_OPER SMPP Operation service point
2.7.4 SEG_TYPE
This field determines whether a record has been created for a message or a message segment.
Table 2.11: Segment types

1 MSG Message
2 SEG Segment

2.7.5 MSG_TYPE
This field determines whether a record has been created for a message or a receipt.
Table 2.12: Message types

1 SM Message
2 RCPT Receipt (notification)
2.7.6 MSG_MODE
This field determines the message mode assigned to a message at the end of a particular service point.
Table 2.13: Message modes

1 SF Store and Forward (SMSC) message mode
2 TRANS Transactional message mode
3 SINGLE Single shot message mode
4 FDA FDA Intercept message mode
5 FDA_PROXY_EA FDA Proxy Early Ack message mode
6 MT_PROXY_EA MT Proxy Early Ack message mode
7 MT_PROXY MT Proxy message mode
8 MO_INTERCEPT MO Intercept message mode
9 MO_PROXY MO Proxy message mode
10 FDA_PROXY FDA Proxy message mode
11 MT_INTERCEPT MT Intercept message mode
2.7.7 MSG_STATUS
This field determines the status of a message at a particular service point.
Table 2.14: Message statuses

0 SUBMITTED Message has been submitted.
1 REJECTED Message has been rejected.
2 ACCEPTED Message hes been accepted.
3 BUFFERED Message has been buffered.
4 DELIVERED Message has been delivered.


5 NOT_DEL_TEMP Message has not been delivered for a temporary reason.
6 NOT_DEL_PERM Message has not been delivered for a permanent reason.
7 DELETED Message has been deleted.
8 EXPIRED Message validity period has expired.
9 HANDED_OVER Message has been handed over.
10 NOT_HANDED_OVER Message has not been handed over.
2.7.8 REJECT_REASON
This field determines the reason for blocking a message.
Table 2.15: Reject reasons

Spoofed MO message - source GT not matching MSC
1 MO_SPOOFED_GT
(message shall come from different GT)
Spoofed MO message - IMSI mismatch (message shall
2 MO_SPOOFED_IMSI
come with a different IMSI)
Spoofed MO message - failed to get originator’s data from
3 MO_SPOOFED_HLR
HLR
Faked MT message - unable to correlate with a preceding
4 MT_FAKE_NO_SRI
SRI-SM
6 SRI_PHISHING_DETECTED Indicates detection of SRI phishing
7 MT_FAKE Faked MT message - no specific reason given
8 SRI_PHISHING_BLACKLISTED Indicates SRI phishing attempt (known phisher)
9 CORRUPT_UDH Message with corrupted UDHs
Message contains an unauthorized application port in the
10 UNAUTH_APA
UDH part
Message originator belongs to a foreign operator - wrong
11 MNP
IMSI address of the originator
12 KEYWORD_MATCHED Message matched a keyword filter
13 BLACKLIST1 Message matched blacklist 1
14 BLACKLIST2 Message matched blacklist 2
15 WHITELIST1 Message did not match whitelist 1
16 WHITELIST2 Message did not match whitelist 2
17 NO_CREDIT Insufficient funds to accept a message
18 WRONG_SC_ADDRESS Message contains a wrong SC address
21 NVL_EXCEEDED Message has exceeded the network volume limit
23 FLOOD_DETECTED Message has exceeded the flood limit
Spoofed MO message - TCAP handshake expected but
35 MO_SPOOFED_TCAP
missing
36 MO_SPOOF Spoofed MO message - no specific reason given
Faked MT message - TCAP handshake expected but
37 MT_FAKE_TCAP
missing
38 ADT_ILLEGAL Message contains an illegal address


Message is a spam - based on an external content control
39 ADVANCED_CC
filter
Message is malformed - covers the structure of a received
40 MALFORMED
packet as well as unexpected values of its fields
Message with mismatch in addresses - no specific reason
41 ADDRESS_VALIDATION
given
43 MT_FAKE_HLR Faked MT message - failed to get originator’s data from HLR
44 STK_ATTACK_ATTEMPT Unauthorized message towards SIM Toolkit
45 CUSTOM_REJECT_REASON_1 Custom reject reason 1
Faked MT message - MT_FAKE_NO_SRI subreason: MT
49 MT_CORREL_ID_UNKNOWN Correlation failed as the SRI cache was not able to find an
SRI record based on MT Correlation ID.
50 MT_CORREL_INVALID Correlation failed as an SRI cache record was invalidated by
a previous MT message.
51 MT_CORREL_ID_TIMEOUT Correlation failed as an MT Correlation ID validity period in
an SRI cache record has expired.
52 MT_CORREL_NO_INTERCEPT Correlation failed as MT-SM comes to MCO, but the SRI
cache record has no interception request flag.
53 MT_CORREL_SC_ADDR_NO_MATCH Correlation failed as the SC address from MT-SM does not
match the SC address in the cache.
Faked MT message - mismatch in the country code of the
54 MT_FAKE_CC_GT_SC
source GT and SC address
55 MT_FAKE_CC_GT_MSISDN
source GT and originating MSISDN
56 MT_FAKE_CC_SC_MSISDN
SC address and originating MSISDN
Faked MT message - mismatch in the SC GT address and
57 MT_FAKE_GT
HLR responding GT
Faked MT message - mismatch in the SC MAP address and
58 MT_FAKE_SC
HLR responding GT
Spoofed MO message - mismatch in the country code of the
59 MO_SPOOFED_CC_SC_MSISDN
SC address and originating MSISDN
64 BARRING_ACTIVE Active barring - barring is active on the service
2.7.9 REJECT_METHOD
This field determines the method with which a message has been blocked. The field is empty when the message has not been
blocked.

Table 2.16: Reject methods

1 REJECT Message rejected - negativelly acknowledged
2 DROP Message dropped - positivelly acknowledged but removed
Message discarded - silently removed without
3 DISCARD
acknowledgement
2.7.10 SM_ERROR
This field determines the SM (protocol agnostic) error with which the message has been blocked. Allowed values are 0 to 51.
Table 2.17: SM errors

1 UNKNOWN_SUBSCRIBER Unknown subscriber
2 ABSENT_SUBSCRIBER_SM Absent subscriber
3 ILLEGAL_SUBSCRIBER Illegal subscriber
4 TELESERVICE_NOT_PROVISIONED Teleservice not provisioned
5 ILLEGAL_EQUIPMENT Illegal equipment
6 CALL_BARRED Call Barred
7 FACILITY_NOT_SUPPORTED Facility not supported
8 SUBSCRIBER_BUSY_FOR_MT Subsriber busy for delivery
9 DELIVERY_FAILURE Delivery failure
10 SYSTEM_FAILURE System failure
11 DATA_MISSING Data missing
12 UNEXPECTED_DATA_VALUE Unexpected data value
13 LA_NOT_CONNECTED Destination LA is not connected
14 INTER_WORKING_ERROR An interworking error
15 DC_SYSTEM_FAILURE Delivery sub-system error
16 BEARER_SERVICE_NOT_PROVISIONED The bearer service is not provisioned.
17 ATM_NOT_ALLOWED ATM is not allowed.
18 INFORMATION_NOT_AVAILABLE Failed because of failing to get information.
19 PREPAID_CANNOT_CHARGE The prepaid interface is not available.
20 PREPAID_ORIG_BLOCKED The originator has insufficient funds.
21 PREPAID_RECIP_BLOCKED The recipient has insufficient funds.
22 PREPAID_BOTH_BLOCKED Both the originator and recipient have insufficient funds.
23 BARRED_BY_APPLICATION The message is rejected by an application.
24 BARRED_BY_KEYWORD_FILTERING The message is rejected due to the keyword filtering.
25 BARRED_BY_ANTIFLOODING The message is rejected due to the anti-flooding check.
32 BILLING_ERROR Billing error
33 DELIVERY_FAILURE_MEM_CAP_EXCEED Delivery failure because of full memory
34 DELIVERY_FAILURE_EQUIP_ERR Delivery failure because of equipment error
35 DELIVERY_FAILURE_NOT_SM_EQUIP Delivery failure because of unequiped recipient
36 ORIG_ID_INVALID Originator’s id is invalid
37 RECIP_ID_INVALID Recipient’s id is invalid
38 SYSTEM_BUSY System busy


39 TIMEOUT Timeout
40 SC_ADDRESS_INVALID SC address is not valid
41 ORIG_ADDRESS_INVALID Originating address is invalid
48 RECIP_ADDRESS_INVALID Recipient address is invalid
49 SERVICE_RESTRICTED Service has been restricted
50 SERVICE_THROTTLED Service has been throttled
51 SERVICE_FAILURE Service has failed
4096 CUSTOM_1 Customer specific error 1
Note
When OAM configuration option rbdl_conf.drop_sets_error is enabled, an SM error is exposed also when a mes-
sage has been dropped in the INCOMING stage.
2.7.11 A_NETWORK_TYPE
This field determines the originator network type.
Table 2.18: Network types

1 GSM GSM - over traditional SS7/SIGTRAN
2 GSMOIP GSM - over SIP (SMS over IP)
3 SMPP SMPP - an SMPP application (content/service provider)
4 CDMA CDMA - over traditional SS7/SIGTRAN
8 GENERATED No network - generated by the system
9 ADMI ADMI - an ADMI application (service provider)
10 RCS RCS - Rich Communication Services (over IMS network)
17 UCP UCP - a UCP application (content/service provider)
18 SMTP SMTP - a Simple Mail Transfer Protocol client

2.7.12 B_NETWORK_TYPE
This field determines the recipient network type.
Table 2.19: Network types

1 GSM GSM - over traditional SS7/SIGTRAN
2 GSMOIP GSM - over SIP (SMS over IP)
3 SMPP SMPP - an SMPP application (content/service provider)
4 CDMA CDMA - over traditional SS7/SIGTRAN
8 GENERATED No network - generated by the system
9 ADMI ADMI - an ADMI application (service provider)
10 RCS RCS - Rich Communication Services (over IMS network)
17 UCP UCP - a UCP application (content/service provider)
18 SMTP SMTP - a Simple Mail Transfer Protocol client
2.7.13 A_HLR_MAP_ERROR
This field determines the MAP error resulting from an SRI-SM (HLR) query about an originating MSISDN number. The field is
empty when the query has been successful or has not been executed, see Table 2.20.
2.7.14 B_HLR_MAP_ERROR
This field determines the MAP error resulting from an SRI-SM (HLR) query about a recipient MSISDN number. The field is empty
when the query has been successful or has not been executed, see Table 2.20.
2.7.15 MAP_ERROR
This field determines the MAP error with which a message has been blocked.
Table 2.20: MAP errors

5 UNIDENTIFIED_SUBSCRIBER Unidentified subscriber
6 ABSENT_SUBSCRIBER_SM Absent subscriber SM
9 ILLEGAL_SUBSCRIBER Illegal subscriber
10 BEARER_SERVICE_NOT_PROVISIONED Bearer service not provisioned
11 TS_NOT_PROVISIONED Teleservice not provisioned
12 ILLEGAL_EQUIPMENT Illegal equipment
13 CALL_BARRED Call barred
16 ILLEGAL_SS_OPERATION Illegal SS operation
17 SS_ERROR_STATUS SS error status
18 SS_NOT_AVAILABLE SS not available
19 SS_SUBSCRIPTION_VIOL SS subscription violation


20 SS_INCOMPATIBILITY SS incompatibility
21 FACILITY_NOT_SUPPORTED Facility not supported
27 ABSENT_SUBSCRIBER Absent subscriber
31 SUBSCRIBER_BUSY_FOR_MT Subscriber busy for MT-FW-SM
32 DELIVERY_FAILURE Delivery failure
49 ATI_NOT_ALLOWED ATI not allowed
60 ATSI_NOT_ALLOWED ATSI not allowed
61 ATM_NOT_ALLOWED ATM not allowed
62 INFORMATION_NOT_AVAILABLE Information not available
1025 ADDRESS_TRANS_FAIL The SMS Destination Address is invalid.
SMS Destination Address is valid but not currently allocated
1026 ADDRESS_VACANT
to an SMS terminal.
Broadcast periodicity failure in MSC. Requested broadcast
1027 BCS_PERIODICITY_FAIL_MSC
periodicity cannot be handled by MSC.
A required terminal resource is not available to process this
1028 DEST_RESOURCE_SHORTAGE
message. SMS notification is not pending.
The destination MS-based SME is SMS capable, but is
1029 DEST_BUSY
currently engaged in a call.
The MS-based SME is no longer at the temporary SMS
1030 DEST_NO_LONGER_AT_THIS_ADDR
routing address. SMS notification is not pending.
Delivery is not currently possible, but SMS notification is
1031 DEST_OUT_OF_SERVICE
pending.
1032 ENCODING_PROBLEM The size of a parameter or field is not what is expected.
The SMS_TeleserviceIdentifier is not known, is not
1033 INVALID_TELESERVICE_ID supported or is not authorized by an addressed functional
entity.
An optional parameter that is required for a particular
1034 MISSING_EXPECTED_PARAM
function.
A parameter is missing that is mandatory for a particular
1035 MISSING_MANDATORY_PARAM
message.
A network node failed, a link failed or a required operation
1036 NETWORK_FAILURE
failed.
Network transmission failed due to lack of a network
1037 NETWORK_RESOURCE_SHORTAGE
resource shortage or link capacity.
The destination SME does not acknowledge receipt of the
1038 NO_ACKNOWLEDGEMENT
SMS delivery.
The addressed MS-based SME is known, but it does not
1039 NO_PAGE_RESPONSE
respond to a page. SMS Notification is not pending.
1040 OTHER_GENERAL_PROBLEMS Other general problems.
1041 OTHER_NETWORK_PROBLEM Other network problem.
1042 OTHER_RADIO_INTERFACE_PROB Other radio interface problem.
1043 OTHER_TERMINAL_PROBLEM Other terminal problem. SMS notification is not pending.
The MS for an MS-based SME is operating in a mode that
1044 RADIO_INTERFACE_INCOMP
does not support SMS at this time.
There is no channel available or there is radio congestion at
1045 RADIO_INTERFACE_SHORTAGE
this time.


The service is not supported by an addressed functional
1046 SERVICE_NOT_SUPPORTED
entity.
The originating MSID is not recognized, the originating
1047 SERVICE_ORIGINATION_DENIED
address is not allowed for the originating MS.
The destination is not authorized to receive this service
1048 SERVICE_TERMINATION_DENIED
message, the MC refused the message.
An OTASP or OTAPA session does not currently exist for the
1049 SESSION_NOT_ACTIVE
MS.
1050 SMS_DELIV_ON_PAGING_NOT_SUPP SMS delivery on paging channel not supported.
1051 SMS_DELIV_POSTPONED
pending.
The originating supplementary service is not known or
1052 SUPPLEMENT_SERVICE_SUPPORTED
supported.
1053 UNEXPECTED_PARAMETER_VALUE A known parameter has a known, but unexpected value.
1054 UNRECOGNIZED_PARAMETER_VALUE A known parameter has a unknown or unsupported value.
1055 UNSUPP_BS_CAPABILITY Base Station does not support this service.
The intersystem network interface required for the delivery
1056 UNSUPP_NETWORK_INTERFACE
of the received message is not supported.
The User Data size is too large for access technology,
1057 USER_DATA_SIZE_ERROR
transport network, or call mode.
1058 SMS_ACCDEN_DENIED The request cannot be honored, or the MS is unknown.
1059 SMS_ACCDEN_POSTPONED The addressed MS is known, but is currently unreachable.
1060 SMS_ACCDEN_UNAVAILABLE The addressed MS is known, but is currently unavailable.
1061 SMS_ACCDEN_INVALID The SMS TeleserviceID is invalid.
1062 ANSI_TCAP_UNKNOWN_ERROR Unknown TCAP error
1063 ANSI_TCAP_RET_ERR_UNREC_MIN Unrecognized MIN
1064 ANSI_TCAP_RET_ERR_UNREC_ESN Unrecognized ESN
1065 ANSI_TCAP_RET_ERR_ID_HLR_MISM ID/HLR mismatch
1066 ANSI_TCAP_RET_ERR_OPER_SEQ_PROBLEM
Operation sequence problem
1067 ANSI_TCAP_RET_ERR_RES_SHORT Resource shortage
1068 ANSI_TCAP_RET_ERR_OPER_NOT_SUP Operation not supported
1069 ANSI_TCAP_RET_ERR_TRUNK_UNAVAIL Trunk unavailable
1070 ANSI_TCAP_RET_ERR_PARAM_ERR Parameter error
1071 ANSI_TCAP_RET_ERR_SYS_FAIL System failure
1072 ANSI_TCAP_RET_ERR_UNREC_PARAM_VAL
Unrecognized parameter value
1073 ANSI_TCAP_RET_ERR_FEAT_INACT Feature inactive
1074 ANSI_TCAP_RET_ERR_MISS_PARAM Missing parameter
1075 ANSI_TCAP_RET_ERR_UNREC_IMSI_TMSIUnrecognized IMSI/TMSI
1076 ANSI_TCAP_RET_ERR_TMSI_VLR_MISM TMSI/VLR mismatch
1077 ANSI_TCAP_REJ_GEN_UNREC_COMP_TYPE
General problem unrecognized component type
1078 ANSI_TCAP_REJ_GEN_INCOR_COMP General problem incorrect component portion
1079 ANSI_TCAP_REJ_GEN_BAD_STRUCT_COMP
General problem incorrect component portion
1080 ANSI_TCAP_REJ_GEN_INCOR_COMP_COD
General problem incorrect component coding
1081 ANSI_TCAP_REJ_INV_DUP_INV_ID Invoke problem duplicate invocation
1082 ANSI_TCAP_REJ_INV_UNREC_OP Invoke problem unrecognized operation
1083 ANSI_TCAP_REJ_INV_INCOR_PARAM Invoke problem incorrect parameter
1084 ANSI_TCAP_REJ_INV_UNREC_COR_ID Invoke problem unrecognized correlation id


1085 ANSI_TCAP_REJ_RR_UNREC_COR_ID Return result problem unrecognized correlation id
1086 ANSI_TCAP_REJ_RR_UNEXP_RETRES Return result problem unexpected return result
1087 ANSI_TCAP_REJ_RR_INCOR_PARAM Return result problem incorrect parameter
1088 ANSI_TCAP_REJ_RE_UNREC_COR_ID Return error problem unrecognized correlation id
1089 ANSI_TCAP_REJ_RE_UNEXP_RETERR Return error problem unexpected return error
1090 ANSI_TCAP_REJ_RE_UNREC_ERROR Return error problem unrecognized error
1091 ANSI_TCAP_REJ_RE_UNEXP_ERROR Return error problem unexpected error
1092 ANSI_TCAP_REJ_RE_INCOR_PARAM Return error problem incorrect parameter
1093 ANSI_TCAP_REJ_TP_UNREC_PKG_TYPE Transaction portion problem unrecognized package type
1094 ANSI_TCAP_REJ_TP_INCOR_TP Transaction portion problem incorrect transaction portion
Transaction portion problem badly structured transaction
1095 ANSI_TCAP_REJ_TP_BAD_STRUCT_TP
portion
1096 ANSI_TCAP_REJ_TP_UNREC_TRANSID Transaction portion problem unrecognized transaction id
1097 ANSI_TCAP_REJ_TP_PERM_RELEAS_PB Transaction portion problem permission to release problem
1098 ANSI_TCAP_REJ_TP_RESOUR_UNAVAIL Transaction portion problem resource unavailable
1099 ANSI_TCAP_ABORT TCAP abort
4096 SS7_ERROR Low level SS7 error
SIP error response. Field MAP_CAUSE contains specific
24576 SIP_ERROR response code, this code is SIP response code masked with
0x6000 (24576).
2.7.16 MAP_CAUSE
This field determines the MAP cause with which a message has been blocked.
Table 2.21: MAP causes

1 ERROR Unknown MAP error.
4 SYSTEM_FAILURE_PLMN System failure with network resource PLMN
5 SYSTEM_FAILURE_HLR System failure with network resource HLR
6 SYSTEM_FAILURE_VLR System failure with network resource VLR
7 SYSTEM_FAILURE_PVLR System failure with network resource PVLR
8 SYSTEM_FAILURE_CMSC System failure with network resource controlling MSC
9 SYSTEM_FAILURE_VMSC System failure with network resource VMSC
10 SYSTEM_FAILURE_EIR System failure with network resource EIR
11 SYSTEM_FAILURE_RSS System failure with network resource RSS
14 FACILITY_NOT_SUPPORTED The facility is not supported.
16 UNKNOWN_SUBSCRIBER_IMSI Unknown subscriber with diagnostic IMSI unknown
Unknown subscriber with diagnostic GPRS subscription
17 UNKNOWN_SUBSCRIBER_GPRS
unknown


Unknown subscriber with diagnostic Number Portability
56 UNKNOWN_SUBSCRIBER_NPDB
DB mismatch
18 UNIDENTIFIED_SUBSCRIBER Unidentified subscriber
19 ILLEGAL_SUBSCRIBER Illegal subscriber; authentication on a mobile station failed
20 ILLEGAL_EQUIPMENT Illegal equipment; the IMEI check failed
21 TS_NOT_PROVISIONED Teleservice is not provisioned
22 ABSENT_SUBSCRIBER Absent subscriber
23 CALL_BARRED Call barred
24 CB_SERVICE_ACTIVE Call barred with the cause barring service active
25 CB_OPER_BARRING Call barred with cause operator barring
26 CB_UNAUTH_MSGO Call barred with an unauthorised message originator
Call barred with an unauthorised message originator and
27 CB_UNAUTH_MSGO_SERVICE_ACTIVE
cause barring service active
Call barred with an unauthorised message originator and
28 CB_UNAUTH_MSGO_OPER_BARRING
cause operator barring
29 SUBSCRIBER_BUSY The subscriber is busy for MT-SM.
The subscriber is busy for MT SMS and the GPRS
30 SUBSCRIBER_BUSY_GPRS_SUSPENDED
connection is suspended.
31 DELIVERY_FAILURE SM delivery failure
32 DELIVERY_FAILURE_MEM_CAP_EXCEED SM delivery failure when memory capacity is exceeded
33 DELIVERY_FAILURE_EQUIP_ERR SM delivery failure with an equipment protocol error
34 DELIVERY_FAILURE_NOT_SM_EQUIP SM delivery failure with equipment unable to handle SM
35 DELIVERY_FAILURE_UNKNOWN_SC SM delivery failure with an unknown SC
36 DELIVERY_FAILURE_SC_CONGESTED SM delivery failure with SC congestion
37 DELIVERY_FAILURE_INV_SME_ADDR SM delivery failure with an invalid SME address
SM delivery failure when the subscriber is no SC
38 DELIVERY_FAILURE_NO_SC_SUBS
subscriber
39 MSG_WAIT_LIST_FULL The message waiting list is full.
40 ABSENT_SUBSCRIBER_SM Absent subscriber for SM
Absent subscriber for SM with diagnostic no paging
41 ABSENT_SUBS_SM_NO_PAGE_MSC
response for MSC
42 ABSENT_SUBS_SM_IMSI_DETACH Absent subscriber for SM with diagnostic IMSI detached
Absent subscriber for SM with diagnostic roaming
43 ABSENT_SUBS_SM_ROAM_RESTRICT
restriction
Absent subscriber for SM with diagnostic deregistered in
44 ABSENT_SUBS_SM_DEREG_NON_GPRS
HLR for non-GPRS
Absent subscriber for SM with diagnostic MS purged for
45 ABSENT_SUBS_SM_PURGED_NON_GPRS
non-GPRS
Absent subscriber for SM with diagnostic no paging
46 ABSENT_SUBS_SM_NO_PAGE_SGSN
response for SGSN
47 ABSENT_SUBS_SM_GPRS_DETACH Absent subscriber for SM with diagnostic GPRS detached
48 ABSENT_SUBS_SM_DEREG_GPRS
HLR for GPRS
Absent subscriber for SM with diagnostic MS purged for
49 ABSENT_SUBS_SM_PURGED_GPRS
GPRS
Absent subscriber for SM with diagnostic an unidentified
50 ABSENT_SUBS_SM_UNIDENT_MSC
subscriber via the MSC


Absent subscriber for SM with diagnostic an unidentified
51 ABSENT_SUBS_SM_UNIDENT_SGSN
subscriber via the SGSN
52 ATM_NOT_ALLOWED ATM not allowed
53 UNEXPECTED_SUBSCRIBER Unexpected subscriber.
54 BEARER_SERVICE_NOT_PROVISIONED Bearer service not provisioned
55 INFORMATION_NOT_AVAILABLE Information not available
Absent subscriber for SM with diagnostic no response for
57 ABSENT_SUBS_SM_NO_RESP_IPSMGW
IPSMGW
58 ILLEGAL_SS_OPERATION Illegal SS operation
59 SS_SUBSCRIPTION_VIOL SS subscription violation
60 SS_ERROR_STATUS SS error status
61 SS_INCOMPATIBILITY SS incompatibility
62 SS_NOT_AVAILABLE SS not available
63 ATSI_NOT_ALLOWED ATSI not allowed
64 ABSENT_SUBS_SM_DEREG_IMS
HLR for IPSMGW
65 ATI_NOT_ALLOWED ATI not allowed
1025 ADDRESS_TRANS_FAIL The SMS Destination Address is invalid.
SMS Destination Address is valid but not currently
1026 ADDRESS_VACANT
allocated to an SMS terminal.
Broadcast periodicity failure in MSC. Requested broadcast
1027 BCS_PERIODICITY_FAIL_MSC
periodicity cannot be handled by MSC.
A required terminal resource is not available to process
1028 DEST_RESOURCE_SHORTAGE
this message. SMS notification is not pending.
The destination MS-based SME is SMS capable, but is
1029 DEST_BUSY
currently engaged in a call.
The MS-based SME is no longer at the temporary SMS
1030 DEST_NO_LONGER_AT_THIS_ADDR
routing address. SMS notification is not pending.
1031 DEST_OUT_OF_SERVICE
pending.
1032 ENCODING_PROBLEM The size of a parameter or field is not what is expected.
The SMS_TeleserviceIdentifier is not known, is not
1033 INVALID_TELESERVICE_ID supported or is not authorized by an addressed functional
entity.
An optional parameter that is required for a particular
1034 MISSING_EXPECTED_PARAM
function.
A parameter is missing that is mandatory for a particular
1035 MISSING_MANDATORY_PARAM
message.
A network node failed, a link failed or a required operation
1036 NETWORK_FAILURE
failed.
Network transmission failed due to lack of a network
1037 NETWORK_RESOURCE_SHORTAGE
resource shortage or link capacity.
The destination SME does not acknowledge receipt of the
1038 NO_ACKNOWLEDGEMENT
SMS delivery.
The addressed MS-based SME is known, but it does not
respond to a page. SMS Notification is not pending.
1040 OTHER_GENERAL_PROBLEMS Other general problems.
1041 OTHER_NETWORK_PROBLEM Other network problem.
1042 OTHER_RADIO_INTERFACE_PROB Other radio interface problem.


1043 OTHER_TERMINAL_PROBLEM Other terminal problem. SMS notification is not pending.
The MS for an MS-based SME is operating in a mode that
1044 RADIO_INTERFACE_INCOMP
does not support SMS at this time.
There is no channel available or there is radio congestion
1045 RADIO_INTERFACE_SHORTAGE
at this time.
The service is not supported by an addressed functional
1046 SERVICE_NOT_SUPPORTED
entity.
The originating MSID is not recognized, the originating
1047 SERVICE_ORIGINATION_DENIED
address is not allowed for the originating MS.
The destination is not authorized to receive this service
1048 SERVICE_TERMINATION_DENIED
message, the MC refused the message.
An OTASP or OTAPA session does not currently exist for
1049 SESSION_NOT_ACTIVE
the MS.
1050 SMS_DELIV_ON_PAGING_NOT_SUPP SMS delivery on paging channel not supported.
1051 SMS_DELIV_POSTPONED
pending.
The originating supplementary service is not known or
1052 SUPPLEMENT_SERVICE_SUPPORTED
supported.
1053 UNEXPECTED_PARAMETER_VALUE A known parameter has a known, but unexpected value.
1054 UNRECOGNIZED_PARAMETER_VALUE A known parameter has a unknown or unsupported value.
1055 UNSUPP_BS_CAPABILITY Base Station does not support this service.
The intersystem network interface required for the delivery
1056 UNSUPP_NETWORK_INTERFACE
of the received message is not supported.
The User Data size is too large for access technology,
1057 USER_DATA_SIZE_ERROR
transport network, or call mode.
1058 SMS_ACCDEN_DENIED The request cannot be honored, or the MS is unknown.
1059 SMS_ACCDEN_POSTPONED The addressed MS is known, but is currently unreachable.
1060 SMS_ACCDEN_UNAVAILABLE The addressed MS is known, but is currently unavailable.
1061 SMS_ACCDEN_INVALID The SMS TeleserviceID is invalid.
1062 ANSI_TCAP_UNKNOWN_ERROR Unknown TCAP error
1063 ANSI_TCAP_RET_ERR_UNREC_MIN Unrecognized MIN
1064 ANSI_TCAP_RET_ERR_UNREC_ESN Unrecognized ESN
1065 ANSI_TCAP_RET_ERR_ID_HLR_MISM ID/HLR mismatch
1066 ANSI_TCAP_RET_ERR_OPER_SEQ_PROBLEM Operation sequence problem
1067 ANSI_TCAP_RET_ERR_RES_SHORT Resource shortage
1068 ANSI_TCAP_RET_ERR_OPER_NOT_SUP Operation not supported
1069 ANSI_TCAP_RET_ERR_TRUNK_UNAVAIL Trunk unavailable
1070 ANSI_TCAP_RET_ERR_PARAM_ERR Parameter error
1071 ANSI_TCAP_RET_ERR_SYS_FAIL System failure
1072 ANSI_TCAP_RET_ERR_UNREC_PARAM_VAL Unrecognized parameter value
1073 ANSI_TCAP_RET_ERR_FEAT_INACT Feature inactive
1074 ANSI_TCAP_RET_ERR_MISS_PARAM Missing parameter
1075 ANSI_TCAP_RET_ERR_UNREC_IMSI_TMSI Unrecognized IMSI/TMSI
1076 ANSI_TCAP_RET_ERR_TMSI_VLR_MISM TMSI/VLR mismatch
1077 ANSI_TCAP_REJ_GEN_UNREC_COMP_TYPE General problem unrecognized component type
1078 ANSI_TCAP_REJ_GEN_INCOR_COMP General problem incorrect component portion
1079 ANSI_TCAP_REJ_GEN_BAD_STRUCT_COMP General problem incorrect component portion
1080 ANSI_TCAP_REJ_GEN_INCOR_COMP_COD General problem incorrect component coding


1081 ANSI_TCAP_REJ_INV_DUP_INV_ID Invoke problem duplicate invocation
1082 ANSI_TCAP_REJ_INV_UNREC_OP Invoke problem unrecognized operation
1083 ANSI_TCAP_REJ_INV_INCOR_PARAM Invoke problem incorrect parameter
1084 ANSI_TCAP_REJ_INV_UNREC_COR_ID Invoke problem unrecognized correlation id
1085 ANSI_TCAP_REJ_RR_UNREC_COR_ID Return result problem unrecognized correlation id
1086 ANSI_TCAP_REJ_RR_UNEXP_RETRES Return result problem unexpected return result
1087 ANSI_TCAP_REJ_RR_INCOR_PARAM Return result problem incorrect parameter
1088 ANSI_TCAP_REJ_RE_UNREC_COR_ID Return error problem unrecognized correlation id
1089 ANSI_TCAP_REJ_RE_UNEXP_RETERR Return error problem unexpected return error
1090 ANSI_TCAP_REJ_RE_UNREC_ERROR Return error problem unrecognized error
1091 ANSI_TCAP_REJ_RE_UNEXP_ERROR Return error problem unexpected error
1092 ANSI_TCAP_REJ_RE_INCOR_PARAM Return error problem incorrect parameter
1093 ANSI_TCAP_REJ_TP_UNREC_PKG_TYPE Transaction portion problem unrecognized package type
1094 ANSI_TCAP_REJ_TP_INCOR_TP Transaction portion problem incorrect transaction portion
Transaction portion problem badly structured transaction
1095 ANSI_TCAP_REJ_TP_BAD_STRUCT_TP
portion
1096 ANSI_TCAP_REJ_TP_UNREC_TRANSID Transaction portion problem unrecognized transaction id
Transaction portion problem permission to release
1097 ANSI_TCAP_REJ_TP_PERM_RELEAS_PB
problem
1098 ANSI_TCAP_REJ_TP_RESOUR_UNAVAIL Transaction portion problem resource unavailable
1099 ANSI_TCAP_ABORT TCAP abort
4096 UNKNOWN_SUBSCRIBER_NOT_HPLMN Subscriber not in Home PLMN
FDA was not executed due to an exceeded FDA licence
4097 FDA_BARRED_BY_LICENCE_LIMIT
limit
4098 CALL_BARRED_LOCAL_SCREENING Local screening barred MO submission
4099 CALL_BARRED_ROUTING Barred message routing
SCCP return cause - No translation for an address of such
4352 SCCP_NO_TRANS_ADDR_NATURE
nature
SCCP return cause - No translation for this specific
4353 SCCP_NO_TRANS_SPEC_ADDR
address
4354 SCCP_SUBSYSTEM_CONGESTION SCCP return cause - Subsystem congestion
4355 SCCP_SUBSYSTEM_FAILURE SCCP return cause - Subsystem failure
4356 SCCP_UNEQUIPPED_USER SCCP return cause - Unequipped user
4357 SCCP_MTP_FAILURE SCCP return cause - MTP failure
4358 SCCP_NETWORK_CONGESTION SCCP return cause - Network congestion
4359 SCCP_UNQUALIFIED SCCP return cause - Unqualified
4360 SCCP_ERR_MSG_TRANS SCCP return cause - Error in message transport
4361 SCCP_ERR_LOCAL_PROCESS SCCP return cause - Error in local processing
SCCP return cause - Destination cannot perform
4362 SCCP_DEST_NO_REASSEMBLY
reassembly
4363 SCCP_FAILURE SCCP return cause - SCCP failure
4364 SCCP_HOP_COUNTER_VIOLATION SCCP return cause - SCCP hop counter violation
4365 SCCP_SEGM_NOT_SUPPORT SCCP return cause - Segmentation not supported
4366 SCCP_SEGM_FAILURE SCCP return cause - Segmentation failure
4367 SCCP_ERR General SCCP error
4608 P_ERR_NO_RESPONSE_FROM_PEER MAP Provider error - no response from peer
4609 P_ERR_SERVICE_COMPLETE_FAILURE MAP Provider error -


4610 P_ERR_INVALID_RESP_RECEIVED MAP Provider error - invalid response received
4611 P_ERR_SERVICE_NOT_SUPPORTED MAP Provider error - service not supported
4612 P_ERR_MISTYPED_PARAMETER MAP Provider error - mistyped parameter
4613 P_ERR_DUPLICATE_INVOKE_ID MAP Provider error - duplicate invoke id
4614 P_ERR_RESOURCE_LIMITATION MAP Provider error - resource limitation
4615 P_ERR_INITIATING_RELEASE MAP Provider error - initiating release
4616 P_ERR_UNEXP_RES_FROM_PEER MAP Provider error - unexpected response from peer
4864 P_ABRT_ERR MAP Provider abort - error
4865 P_ABRT_MALFUNCTION MAP Provider abort - malfunction
4866 P_ABRT_DIALOG_RELEASED MAP Provider abort - dialog released
4867 P_ABRT_RESOURCE_LIMIT MAP Provider abort - resource limitation
4868 P_ABRT_ABNORMAL_DIALOG MAP Provider abort - abnormal dialog
4869 P_ABRT_INVALID_PDU MAP Provider abort - invalid PDU
5120 O_REFUSE_OUT_OF_DIALOGS MAP Open refuse - out of dialogs
5121 O_REFUSE_REASON_UNKNOWN MAP Open refuse - reason unknown
5122 O_REFUSE_REASON_INV_DEST_REF MAP Open refuse - invalid destination reference
5123 O_REFUSE_REASON_INV_SRC_REF MAP Open refuse - invalid source reference
5124 O_REFUSE_REASON_AC_NOT_SUPP MAP Open refuse - application context not supported
5125 O_REFUSE_REASON_NODE_NREACH MAP Open refuse - node not reachable
5126 O_REFUSE_REASON_VERSION_INCOMP MAP Open refuse - potential version incompatibility
5376 NOTICE_UNEXPECTED_RESULT MAP Notice - unexpected result
5377 NOTICE_UNEXPECTED_ERROR MAP Notice - unexpected error
5378 NOTICE_ABNORMAL_EVENT_RECEIVED MAP Notice - abnormal event received
5379 NOTICE_MSG_CANNOT_BE_DELIVERED MAP Notice - message cannot be delivered
5380 NOTICE_RESPONSE_REJECTED MAP Notice - response rejected
5381 NOTICE_ABNORMAL_EVENT_DETECT MAP Notice - abnormal event detected
5632 U_ABRT_ERR MAP User abort - error
5633 U_ABRT_USER_SPECIFIC_REASON MAP User abort - user specific reason
5634 U_ABRT_RES_LIMITATION MAP User abort - resource limitation
5635 U_ABRT_RES_UNAVAIL_SHORT_TERM MAP User abort - resource unavailable - short term
5636 U_ABRT_RES_UNAVAIL_LONG_TERM MAP User abort - resource unavailable - long term
5637 U_ABRT_PCANC_REASON_HANDOVER MAP User abort - process cancelation - reason handover
MAP User abort - process cancelation - radio channel
5638 U_ABRT_PCANC_RADIO_CHANNEL_RLS
release
MAP User abort - process cancelation - network path
5639 U_ABRT_PCANC_NETWORK_PATH_RLS
release
5640 U_ABRT_PCANC_CALL_RLS MAP User abort - process cancelation - call release
MAP User abort - process cancelation - associated
5641 U_ABRT_PCANC_ASSOC_PROC_FAIL
procedure failure
MAP User abort - process cancelation - tandem dialog
5642 U_ABRT_PCANC_TANDEM_DLG_RLS
release
MAP User abort - process cancelation - remote operations
5643 U_ABRT_PCANC_RMT_OPER_FAILURE
failure
SIP response codes masked with 0x6000 (24576).
24576 SIP_ERROR
Reserved range 24576 - 28671.
The request could not be understood due to malformed
24976 SIP_400_BAD_REQUEST
syntax.


The request requires user authentication. This response is
24977 SIP_401_UNAUTHORIZED
issued by UASs and registrars.
The server has definitive information that the user does
not exist at the domain specified in the Request-URI. This
24980 SIP_404_NOT_FOUND status is also returned if the domain in the Request-URI
does not match any of the domains handled by the
recipient of the request.
Couldn’t find the user in time. The server could not
produce a response within a suitable amount of time, for
24984 SIP_408_REQUEST_TIMEOUT example, if it could not determine the location of the user
in time. The client MAY repeat the request without
modifications at any later time.
24991 SIP_415_UNSUPPORTED_MEDIA_TYPE Request body in a format not supported.
25056 SIP_480_TEMPORARILY_UNAVAILABLE Callee currently unavailable.
25062 SIP_486_BUSY_HERE Callee is busy.
The response has the same meaning as 606 (Not
Acceptable), but only applies to the specific resource
25064 SIP_488_NOT_ACCEPTABLE_HERE
addressed by the Request-URI and the request may
succeed elsewhere.
The server encountered an unexpected condition that
prevented it from fulfilling the request. The client MAY
25076 SIP_500_SERVER_INTERNAL_ERROR
display the specific error condition and MAY retry the
request after several seconds.
The server is undergoing maintenance or is temporarily
overloaded and so cannot process the request. A
25079 SIP_503_SERVICE_UNAVAILABLE
Retry-After header field may specify when the client may
reattempt its request.
The server attempted to access another server in
25080 SIP_504_SERVER_TIMEOUT attempting to process the request, and did not receive a
prompt response.
All possible destinations are busy. Unlike the 486
response, this response indicates the destination knows
25176 SIP_600_BUSY_EVERYWHERE
there are no alternative destinations (such as a voicemail
server) able to accept the call.
The destination does not wish to participate in the call, or
cannot do so, and additionally the destination knows there
25179 SIP_603_DECLINE
are no alternative destinations (such as a voicemail
server) willing to accept the call.
The server has authoritative information that the
25180 SIP_604_DOES_NOT_EXIST_ANYWHERE
requested user does not exist anywhere.
The user’s agent was contacted successfully but some
aspects of the session description such as the requested
25182 SIP_606_NOT_ACCEPTABLE
media, bandwidth, or addressing style were not
acceptable.
25279 SIP_703_TIMEOUT The request timed out.

2.7.17 SM_CONTENT_ENCODING
This field determines the original encoding of a message.
Table 2.22: Message text encodings

0 UNKNOWN Unknown encoding, e.g. message is compressed
1 GSM_7_DEFAULT Default 7-bit GSM alphabet
2 DATA 8-bit data
3 UCS2 UCS2 alphabet
4 ASCII ASCII alphabet
5 ISO_8859_1 Latin 1 alphabet
6 ANSI_X3_4
7 ISO_8859_5
8 ISO_8859_8
9 ISO_2022
Default 7-bit GSM alphabet - with Turkish single/locking shift
10 GSM_7_TURKISH
table(s)
Default 7-bit GSM alphabet - with Portuguese single/locking
11 GSM_7_PORTUGUESE
shift table(s)
Default 7-bit GSM alphabet - with Spanish single/locking
12 GSM_7_SPANISH
shift table(s)
19 UTF8 UTF8 encoding
Default 7-bit GSM alphabet - with Bengali single/locking shift
22 GSM_7_BENGALI
table(s)
Default 7-bit GSM alphabet - with Gujarati single/locking
23 GSM_7_GUJARATI
shift table(s)
Default 7-bit GSM alphabet - with Hindi single/locking shift
24 GSM_7_HINDI
table(s)
Default 7-bit GSM alphabet - with Kannada single/locking
25 GSM_7_KANNADA
shift table(s)
Default 7-bit GSM alphabet - with Malayalam single/locking
26 GSM_7_MALAYALAM
shift table(s)
Default 7-bit GSM alphabet - with Oriya single/locking shift
27 GSM_7_ORIYA
table(s)
Default 7-bit GSM alphabet - with Punjabi single/locking shift
28 GSM_7_PUNJABI
table(s)
Default 7-bit GSM alphabet - with Tamil single/locking shift
29 GSM_7_TAMIL
table(s)
Default 7-bit GSM alphabet - with Telugu single/locking shift
30 GSM_7_TELUGU
table(s)
Default 7-bit GSM alphabet - with Urdu single/locking shift
31 GSM_7_URDU
table(s)
2.7.18 MAP_OPER_TYPE
This field determines the type of a GSM MAP operation being recorded.

Table 2.23: MAP operation types

1 MO_FW_SM MO-FW-SM GSM MAP operation
2 MT_FW_SM MT-FW-SM GSM MAP operation
3 ALERT_SM Alert-SM GSM MAP operation
4 SRI_SM SRI-SM GSM MAP operation
5 R_SM_DS R-SM-DS GSM MAP operation
6 RFSM READY-FOR-SM GSM MAP operation
7 ATM ATM GSM MAP operation
8 ATSI ATSI GSM MAP operation
9 ATI ATI GSM MAP operation
2.7.19 NOTIF_REQ
This field denote which notification (delivery-receipt) types are requested by originator of a message.
Table 2.24: Requested notifications
Bit/position Name Description

2 NON_DELIVERY Non-Delivery notification is requested.
3 DELIVERY (Succesfull) Delivery notification is requested.
5 BUFFERED Buffered/intermediate notification is requested.
2.7.20 UDH_MASK
This field denotes list of UDH IEs detected in a message. Single flag can denote multiple UDH IEs determined by UDH profiles.
UDH profiles are configurable in udhb_conf feature.
2.7.21 xCOS
This field denotes list of services a particular party has enabled or disabled. Meaning of flags 1-32 is predefined and/or reserved.
Flags 33-64 are free for any use.
Table 2.25: Class of service

1 INTERNATIONAL International delivery is allowed.
2 NATIONAL National delivery is allowed.
3 OWN_NETWORK Own network delivery is allowed.
4 OWN_SUBSCRIBER Own subscriber delivery is allowed.
5 DUPLICITY_CHECK Duplicity check service is requested.
6 SM_COPY Message copy service is requested.
7 CONTENT_CONTROL Content control service is requested.


8 ADMI External service server triggering is requested.
9 KEYWORD Keyword filtering is requested.
10 FREE_OF_CHARGE Message shall not be charged.
11 PREPAID Prepaid charging is requested.
12 ANTIFLOOD Antiflood detection service is requested.
2.7.22 MSG_FLAGS
This bit-field contains flags indicating miscellaneous properties of a message.
Table 2.26: Message flags

Indicates that a message has came as segmented
1 infoTcapSegmented
transaction on TCAP level.
Indicates that a message has came with
2 infoMapMMS
More-Messages-to-Send flag on MAP level.
Indicates that a message has came with priority flag set on
3 infoMapPRI
MAP level.
4 infoAppLaOrig Message originator is application (SALA, MALA).
5 infoAppLaRecip Message recipient is application (SALA, MALA).
6 infoISR Indicates an ISR message.
ISR message has been rejected by the foreign SMSC in the
7 infoISRRejectedByFSMSC
submit phase.
Message originator identity visibility restricted; recipient
8 infoCLIR
sees empty originator address.
9 infoPhishingMonitored Indicates active SRI phishing detection.
10 infoRARRApplied APPLY_RARR action successfully applied.
11 infoLASNApplied APPLY_LASN action successfully applied.
12 infoSMSIP SMSIP flag is set in registration update.
Message was acknoledged during submission phase before
13 infoImmediateAckApplied
IN trigger was fired.
14 infoActualHSSReqSent HSS request has been initiated by MCO.
Message was delivered via its own queue not recipient
15 infoProxyHighApplied
queue.
16 infoATOActualAtiSent ATI request has been initiated by MCO.
17 infoDefferedDelivery Deferred delivery has been requested for message
25 infoFlashMessage Indicates a flash message (Message Class 0).
Indicates whether submitting messages for foreign recipients
26 infoOtherOperNotAllowed
is forbidden for the originating LA.
FDA (successful or unsuccessful) has been applied to the
28 infoFdaApplied
message.
29 infoMoHandoverAck Indicates an MO handover acknowledgement.
Indicates that an SM is a home-routed message (FSG
scenario); An intercepted MT message is any inbound MT
30 infoHomeRoutedMt
message and a network intercepted MT message is any
inbound MT message which is not home-routed.


Indicates that an MSC/SGSN timestamp adjustment shall be
31 infoTzSkipLocation
omitted.
Indicates that an MS ISDN/IMSI timestamp adjustment shall
32 infoTzSkipRecipient
be omitted.
Indicates that adjustment of a TP-SCTS timestamp shall be
33 infoTzSkipScts
omitted.
Indicates that adjustment of a TP-DC timestamp shall be
34 infoTzSkipDt
omitted.
Indicates that reassembly was configured to be performed
42 infoReassemblyNotApplied
with a message but was not applied.
62 infoCLOUActualSriSent SRI request has been initiated by MCO.
63 infoATOActualAtsiSent ATSI request has been initiated by MCO.
2.7.23 DETECT_FLAGS(_SEG)
This bit-field contains flags indicating detected spam and fraud issues with a message.
Table 2.27: Detect flags

The message was detected as spoofed due to a GT
1 infoMoSpoofedGT
mismatch.
The message was detected as spoofed due to an IMSI
2 infoMoSpoofedImsi
mismatch.
The message was detected as spoofed because
3 infoMoSpoofedHLR
MAP-SRI-SM, which verifies the originator, failed.
The message was detected as a fake because MT-FW-SM
4 infoMtFakeNoSRI
was not preceded by SRI-SM.
6 infoPhishingDetected Indicates detection of SRI phishing.
7 infoMtFake Message was detected as a fake.
8 infoPhishingBlacklisted Indicates SRI phishing attempt (known phisher).
9 infoCorruptUDH UDH of the message is malformed.
The message contains an application port which is not
10 infoUnauthorizedAPA
allowed for a submitter.
11 infoMNPForeignSubscriber The originating subscriber is foreign (wrong IMSI address).
The message content contains a keyword specified in a
12 infoKeywordMatched
keyword group.
13 infoBlacklist1 The message is included in blacklist 1.
14 infoBlacklist2 The message is included in blacklist 2.
15 infoWhitelist1 The message was blacklisted by not matching whitelist 1.
16 infoWhitelist2 The message was blacklisted by not matching whitelist 2.
The charged subscriber has not sufficient credit to send a
17 infoInsufficientCredit
message.
18 infoWrongScAddress Wrong (foreign) SC address in a message.
21 infoNetwVolumeDataEx Network volume limit was exceeded.


23 infoFloodDetected Flooding was detected.
35 infoMOSpoofedTCAP Spoofed (TCAP handshake expected).
36 infoMOSpoofed Spoofed MO message (unspecified reason).
37 infoMtFakeTcap Fake MT message (TCAP handshake expected).
ADT has marked the MSISDN address as illegal (address in
38 infoADTIllegal
illegal format).
An external Content Control application indicates that illegal
39 infoContentIllegal
content has been detected in a message.
A malformed message has been received - covers the
40 infoMalformed structure of a received packet as well as unexpected values
of its fields, e.g. validity period in past, etc.
41 infoAddressValidation Indicates that validation of addresses has failed.
The message was detected as faked either because
43 infoMtFakeHLR MAP-SRI-SM, which verifies the originator, failed or due to
information from MAP-SRI-SM.
Unauthorized attempt to send a message to SIM Toolkit was
44 infoSTKAttackAttempt
detected or blocked.
The message was blocked/rejected due to custom reason
45 infoCustomRejectReason1
#1.
#2.
#3.
#4.
The MT Correlation failed as SRI cache was not able to find
49 infoMtCorrelIdUnknown
an SRI record based on MT Correlation ID.
The MT Correlation failed as an SRI cache record was
50 infoMtCorrelInvalid
invalidated by a previous MT message.
The MT Correlation failed as the MT Correlation ID validity
51 infoMtCorrelIdTimeout
period in the SRI cache record has expired.
The MT Correlation failed as an MT-SM comes to MCO, but
52 infoMtCorrelNoIntercept the SRI cache record does not have an interception request
flag.
The MT Correlation failed as the SC address from MT-SM
53 infoMtCorrelSCAddrNoMatch
does not match SC address in the cache.
The message was detected as faked due to the source GT
54 infoMTFakeCcGtSc
and SC MAP address mismatch in country code.
55 infoMTFakeCcGtMsisdn
and MSISDN mismatch in country code.
The message was detected as faked due to the SC MAP
56 infoMTFakeCcScMsisdn
address and MSISDN mismatch in country code.
The message was detected as faked due to the SC GT does
57 infoMTFakeGT
not match with originator subscriber HLR responding GT.
58 infoMTFakeSC address does not match with originator subscriber HLR
responding GT.
The message was detected as spoofed due to the SC
59 infoMOSpoofedCcScMsisdn
address and originator MSISDN mismatch in country code.
60 infoDetectedThreat Indicates possible spam or fraudulent message.


Indicates that message contains potentially malicious
61 infoDetectedMaliciousRef
reference (MSISDN, URL).
64 infoBarringActive Indicates active barring for the message.
2.7.24 BILLING_DATA(_SEG)
This bit-field contains flags related to on-line (prepaid) charging models.
Table 2.28: Billing data flags

1 ORIG_PREPAID Originator is prepaid subscriber.
2 ORIG_CHECKED Originator has been validated.
3 RECIP_PREPAID Recipient is prepaid subscriber.
4 RECIP_CHECKED Recipient has been validated.
5 CHARGED_PARTY_ORIG Originator is charged party.
6 CHARGED_PARTY_RECIP Recipient is charged party.
7 RECONCILE Message has not been charged yet.
8 NOTIF_RECONCILE Notification (receipt) has not been charged yet.
9 OPER_1_SUCCESS On-line charging operation #1 has been success
10 OPER_1_PERFORMED On-line charging operation #1 has been performed
17 TRANSACTIONAL Transactional charging
2.7.25 SIGNAL_OPER_TYPE
Signal operation type. It identifies the kind of signal going from/to $prod.
Table 2.29: Signal Operation Type

1 SIP_REGISTER SIP Register
2 SIP_NOTIFY SIP Notify
3 SIP_SUBSCRIBE SIP Subscribe
4 SIP_OPTIONS SIP Options
16 SIP_MESSAGE_SUBMIT SIP Message with SMS-SUBMIT
17 SIP_MESSAGE_SUBMIT_REPORT SIP Message with SMS-SUBMIT-REPORT
18 SIP_MESSAGE_DELIVER SIP Message with SMS-DELIVER


19 SIP_MESSAGE_DELIVER_REPORT SIP Message with SMS-DELIVER-REPORT
20 SIP_MESSAGE_SMMA SIP Message with SMS-SUBMIT-SMMA
32 SH_PNR Sh Push Notification Request
2.7.26 SIGNAL_TYPE
Signal type. It identifies direction of the signal.
Table 2.30: Signal Type

0 INDICATION Indication signal
1 RESPONSE Response signal
2 REQUEST Request signal
3 CONFIRMATION Confirmation signal
2.7.27 CONTACT_REG_STATE
State of the contact registration in the IMS core.
Table 2.31: Contact registration state

0 ACTIVE Active
1 TERMINATED Terminated
2.7.28 CONTACT_REG_EVENT
Contact registration event.
Table 2.32: Contact registration event

0 REGISTERED Registered
1 CREATED Created
2 REFRESHED Refreshed
3 SHORTENED Shortened
4 EXPIRED Expired


5 DEACTIVATED Deactivated
6 PROBATION Probation
7 UNREGISTERED Unregistered
8 REJECTED Rejected
2.7.29 STAT_DATA
This field contains a list of entries separated by a vertical bar informing about result and details of miscellaneous message
screenings.
<feature_id>;<profile_id><result><ffu>|...
2.7.30 TRACK_DATA
This field contains a list of RBDL rule names of rules applied to the message. The rule names are separated by a vertical bar as
follows:
MTFAKE_RULE_1|ADT_1.1.123*|TRACKED_RULE_1
The size of this field never exceeds 4096 ASCII characters. It can be shorter depending on the place where the RBDL rule is
applied. When there is not enough space for recording another rule name(s) in the field, the plus sign (+) is included to indicate
that more rules than recorded were applied.
MTFAKE_RULE_1|ADT_1.1.123*|TRACKED_RULE_1|...|+
Only rules marked for SDR tracking in MCO configuration are recorded.
2.7.31 TELESERVICE
This field determines the CDMA teleservice identifier.
Table 2.33: Teleservice identifier

4096 CMT-91 IS-91 Extended Protocol Enhanced Services
4097 WPT Wireless Paging Teleservice
4098 WMT Wireless Messaging Teleservice
4099 VMN Voice Mail Notification
4100 WAP Wireless Application Protocol
4101 WEMT Wireless Enhanced Messaging Teleservice
4102 SCPT Service Category Programming Teleservice
4103 CATPT Card Application Toolkit Protocol Teleservice

2.7.32 ODB
This bit field contains the Operator Determined Barring flags.
Table 2.34: Operator determined barring flags
Bit/position
Name Description
4 registrationInternationalCFBarred registrationInternationalCF-Barred
registrationInterzonalCFNotToHPLMN-
5 registrationInterzonalCFNotToHPLMNBarred
Barred
6 registrationInterzonalCFBarred registrationInterzonalCF-Barred
7 registrationCFNotToHPLMNBarred registrationCFNotToHPLMN-Barred
8 registrationAllCFBarred registrationAllCF-Barred
9 roamingOutsidePLMNCountryBarred roamingOutsidePLMN-CountryBarred
10 roamingOutsidePLMNBarred roamingOutsidePLMN-Barred
roamingOutsidePLMNICountryIC-
11 roamingOutsidePLMNICountryICCallsBarred
CallsBarred
12 roamingOutsidePLMNICCallsBarred roamingOutsidePLMNIC-CallsBarred
13 allICCallsBarred allIC-CallsBarred
14 roamingOutsidePLMNOGCallsBarred roamingOutsidePLMNOG-CallsBarred
15 roamerAccessToVPLMNAPBarred roamerAccessToVPLMN-AP-Barred
16 roamerAccessToHPLMNAPBarred roamerAccessToHPLMN-AP-Barred
17 allPacketOrientedServicesBarred allPacketOrientedServicesBarred
18 multipleECTBarred multipleECT-Barred
19 doublyChargeableECTBarred doublyChargeableECT-Barred
20 interzonalECTBarred interzonalECT-Barred
21 internationalECTBarred internationalECT-Barred
22 chargeableECTBarred chargeableECT-Barred
23 allECTBarred allECT-Barred
interzonalOGCallsAndInternationalOGCalls-
24 interzonalOGCallsAndInternationalOGCallsNotToHPLMNCountryBarred
NotToHPLMN-CountryBarred
interzonalOGCallsNotToHPLMN-
25 interzonalOGCallsNotToHPLMNCountryBarred
CountryBarred
26 interzonalOGCallsBarred interzonalOGCallsBarred
27 ssAccessBarred ss-AccessBarred
28 premiumRateEntertainementOGCallsBarred premiumRateEntertainementOGCallsBarred
29 premiumRateInformationOGCallsBarred premiumRateInformationOGCallsBarred
internationalOGCallsNotToHPLMN-
30 internationalOGCallsNotToHPLMNCountryBarred
CountryBarred
31 internationalOGCallsBarred internationalOGCallsBarred
32 allOGCallsBarred allOG-CallsBarred
2.7.33 CALL_BARRING_FEATURES
This field contains a list of call barring features obtained during service data screening of MAP field CallBarFeatureList. The
following is an example of raw data contained in the field:
010222;090118

The following is the format of data:
<ss-status><service-type><service-code>;<ss-status>...
Fields ss-status and service-code contain values of call barring features. service-type contains the type of service, and
can have the following values:
• 00 - no service code is contained in the call barring feature, service-code is not present.
• 01 - the bearer service code is present in service-code.
• 02 - the Teleservice code is present in service-code.
The services in the list are separated with ";".

The csv_decode.py tool can be used to decode the field for better readability:
CALL_BARRING_FEATURES(): ss-status:01;teleservice:22|ss-status:09;bearerService:18
2.7.34 NETWORK_ERROR
The enumeration of NETWORK_ERROR values is contained in the following tables. Enumeration table is chosen based on the
B_NETWORK_TYPE.
Note
Note that the csv_decode tool can decode the name of the value in the NETWOR_ERROR field but it does so only if the
NETWORK_ERROR field is configured after the B_NETWORK_TYPE field in the sdr_conf.streams[CSV_SM].fields
table. Otherwise, only a numeric error value is provided.
Table 2.35: SMPP network errors

0 SMPP_ROK No Error
1 SMPP_RINVMSGLEN Message Length is invalid
2 SMPP_RINVCMDLEN Command Length is invalid
3 SMPP_RINVCMDID Invalid Command ID
4 SMPP_RINVBNDSTS Incorrect BIND status for given command
5 SMPP_RALYBND ESME Already in Bound State
6 SMPP_RINVPRTFLG Invalid Priority Flag
7 SMPP_RINVREGDLVFLG Invalid Registered Delivery Flag
8 SMPP_RSYSERR System Error
10 SMPP_RINVSRCADR Invalid Source Address
11 SMPP_RINVDSTADR Invalid Destination Address
12 SMPP_RINVMSGID Message ID is invalid
13 SMPP_RBINDFAIL Bind Failed
14 SMPP_RINVPASWD Invalid Password
15 SMPP_RINVSYSID Invalid System ID
17 SMPP_RCANCELFAIL Cancel SM Failed
19 SMPP_RREPLACEFAIL Replace SM Failed
20 SMPP_RMSGQFUL Message Queue Full
21 SMPP_RINVSERTYP Invalid Service Type
25 SMPP_RADDCUSTFAIL Failed to Add Customer


26 SMPP_RDELCUSTFAIL Failed to Delete Customer
27 SMPP_RMODCUSTFAIL Failed to Modify Customer
28 SMPP_RENQCUSTFAIL Failed to Enquire Customer
29 SMPP_RINVCUSTID Invalid Customer ID
31 SMPP_RINVCUSTNAME Invalid Customer Name
33 SMPP_RINVCUSTADR Invalid Customer Address
34 SMPP_RINVADR Invalid Address
35 SMPP_RCUSTEXIST Customer Exists
36 SMPP_RCUSTNOTEXIST Customer Does Not Exist
38 SMPP_RADDDLFAIL Failed to Add DL
39 SMPP_RMODDLFAIL Failed to Modify DL
40 SMPP_RDELDLFAIL Failed to Delete DL
41 SMPP_RVIEWDLFAIL Failed to View DL
48 SMPP_RLISTDLSFAIL Failed to list DLs
49 SMPP_RPARAMRETFAIL Parameter Retrieve Failed
50 SMPP_RINVPARAM Invalid Parameter
51 SMPP_RINVNUMDESTS Invalid Number of Destinations
52 SMPP_RINVDLNAME Invalid Distribution List name
53 SMPP_RINVDLMEMBDESC Invalid DL Member Description
56 SMPP_RINVDLMEMBTYP Invalid DL Member Type
57 SMPP_RINVDLMODOPT Invalid DL Modify Option
64 SMPP_RINVDESTFLAG Destination flag is invalid (submit_multi)
66 SMPP_RINVSUBREP Invalid ’submit with replace’ request
67 SMPP_RINVESMCLASS Invalid esm_class field data
68 SMPP_RCNTSUBDL Cannot Submit to Distribution List
69 SMPP_RSUBMITFAIL submit_sm or submit_multi failed
72 SMPP_RINVSRCTON Invalid Source address TON
73 SMPP_RINVSRCNPI Invalid Source address NPI
80 SMPP_RINVDSTTON Invalid Destination address TON
81 SMPP_RINVDSTNPI Invalid Destination address NPI
83 SMPP_RINVSYSTYP Invalid system_type field
84 SMPP_RINVREPFLAG Invalid replace_if_present flag
85 SMPP_RINVNUMMSGS Invalid number of messages
Throttling error (ESME has exceeded allowed message
88 SMPP_RTHROTTLED
limits)
89 SMPP_RPROVNOTALLWD Provisioning Not Allowed
97 SMPP_RINVSCHED Invalid Scheduled Delivery Time
98 SMPP_RINVEXPIRY Invalid message validity period
99 SMPP_RINVDFTMSGID Predefined Message Invalid or not Found
100 SMPP_RX_T_APPN ESME Receiver Temporary App Error Code
101 SMPP_RX_P_APPN ESME Receiver Parmanent App Error Code
ESME Receiver Reject Message Error Code (Delete One
102 SMPP_RX_R_APPN
Message)
103 SMPP_RQUERYFAIL query_sm request failed
128 SMPP_RINVPGCUSTID Paging Customer ID Invalid No such subscriber
129 SMPP_RINVPGCUSTIDLEN Paging Customer ID length Invalid
130 SMPP_RINVCITYLEN City Length Invalid


131 SMPP_RINVSTATELEN State Length Invalid
132 SMPP_RINVZIPPREFIXLEN Zip Prefix Length Invalid
133 SMPP_RINVZIPPOSTFIXLEN Zip Postfix Length Invalid
134 SMPP_RINVMINLEN MIN Length Invalid
135 SMPP_RINVMIN MIN Invalid
136 SMPP_RINVPINLEN PIN Length Invalid
137 SMPP_RINVTERMCODELEN Terminal Code Length Invalid
138 SMPP_RINVCHANNELLEN Channel Length Invalid
139 SMPP_RINVCOVREGIONLEN Coverage Region Length Invalid
140 SMPP_RINVCAPCODELEN Cap Code Length Invalid
141 SMPP_RINVMDTLEN Message Delivery Time Length Invalid
142 SMPP_RINVPRIORMSGLEN Priority Message Length Invalid
143 SMPP_RINVPERMSGLEN Periodic Messages Length Invalid
144 SMPP_RINVPGALERTLEN Paging Alerts Length Invalid
145 SMPP_RINVSMUSERLEN Short Message User Group Length Invalid
146 SMPP_RINVRTDBLEN Real Time Data Broadcasts Length Invalid
147 SMPP_RINVREGDELLEN Registered Delivery Lenght Invalid
148 SMPP_RINVMSGDISTLEN Message Distribution Lenght Invalid
149 SMPP_RINVPRIORMSG Priority Message Length Invalid
150 SMPP_RINVMDT Message Delivery Time Invalid
151 SMPP_RINVPERMSG Periodic Messages Invalid
152 SMPP_RINVMSGDIST Message Distribution Invalid
153 SMPP_RINVPGALERT Paging Alerts Invalid
154 SMPP_RINVSMUSER Short Message User Group Invalid
155 SMPP_RINVRTDB Real Time Data Broadcasts Invalid
156 SMPP_RINVREGDEL Registered Delivery Invalid
192 SMPP_RINVOPTPARSTREAM Error in the optional part of the PDU
193 SMPP_ROPTPARNOTALLWD Optional Parameter not Allowed
194 SMPP_RINVPARLEN Invalid Parameter Length
195 SMPP_RMISSINGOPTPARAM Expected Optional Parameter missing
196 SMPP_RINVOPTPARAMVAL Invalid Optional Parameter Value
254 SMPP_RDELIVERYFAILURE Delivery Failure (data_sm_resp)
Note
The error range 0x400 - 0x4FF is reserved for vendor-specific errors.
Table 2.36: UCP network errors

0 UCP_E_OK No Error
1 UCP_E_CHK_SUM_ERR Checksum error


2 UCP_E_SYNTAX_ERR Syntax error
3 UCP_E_OPER_NOT_SUPP Operation not supported by system
4 UCP_E_OPER_NOT_ALLOWED Operation not allowed
5 UCP_E_CALL_BARRING_ACT Call barring active
6 UCP_E_ADC_INV AdC invalid
7 UCP_E_AUTH_FAIL Authentication failure
8 UCP_E_LEGIT_FAIL Legitimisation code for all calls, failure
9 UCP_E_GA_NOT_VALID GA not valid
10 UCP_E_REPET_NOT_ALLOWED Repetition not allowed
11 UCP_E_LEGIT_REP_FAIL Legitimisation code for repetition, failure
12 UCP_E_PRIO_CALL_NOT_ALLOWED Priority call not allowed
13 UCP_E_LEGIT_PRIO_FAIL Legitimisation code for priority call, failure
14 UCP_E_URG_MSG_NOT_ALLOWED Urgent message not allowed
15 UCP_E_LEGIT_URG_MSG_FAIL Legitimisation code for urgent message, failure
16 UCP_E_REV_CHARG_NOT_ALLOWED Reverse charging not allowed
17 UCP_E_LEGIT_RET_CHARG_FAIL Legitimisation code for rev. charging, failure
18 UCP_E_DEFER_DEL_NOT_ALLOWED Deferred delivery not allowed
19 UCP_E_AC_NOT_VALID New AC not valid
20 UCP_E_NEW_LEGIT_NOT_VAL New legitimisation code not valid
21 UCP_E_STD_TXT_NOT_VAL Standard text not valid
22 UCP_E_TIM_PER_NOT_VAL Time period not valid
23 UCP_E_MSG_TYPE_NOT_SUPP Message type not supported by system
24 UCP_E_MSG_TOO_LONG Message too long
25 UCP_E_REQ_STD_TXT_NOT_VAL Requested standard text not valid
26 UCP_E_MSG_TYPE_PAG_NOT_VAL Message type not valid for the pager type
27 UCP_E_MSG_NOT_FOUND Message not found in SMSC
30 UCP_E_SUBS_HANG_UP Subscriber hang up
31 UCP_E_FAX_GRP_NOT_SUPP Fax group not supported
32 UCP_E_FAX_MSG_TYPE_NOT_SUPP Fax message type not supported
33 UCP_E_ADDR_IN_LIST Address already in list
34 UCP_E_ADDR_NOT_IN_LIST Address not in list
35 UCP_E_LST_FUL List full, cannot add address to list
36 UCP_E_RPID_IN_USE RPID already in use
37 UCP_E_DEL_IN_PRGS Delivery in progress
38 UCP_E_MSG_FWD Message forwarded
39 UCP_E_XSER_FLD_TOO_LONG XSER field too long
40 UCP_E_FIELD_VAL_RNG Field value out of range
41 UCP_E_XSER_FLD_ILL_DIGI XSER field contains non-hex digits
42 UCP_E_INV_FLD_LEN Invalid field length
43 UCP_E_UNSUPP_CHARSET Unsupported character set
44 UCP_E_XSER_TPDCS_CONF XSER-TPDCS conflicts with MT parameter
45 UCP_E_UDH_TOO_LONG UDH too long
46 UCP_E_XSER_FLD_VAL_RNG XSER field value out of range
47 UCP_E_XSER_FLD_DIG_ONLY XSER field must contain digits only
48 UCP_E_XSER_FLD_TOO_SHORT XSER field too short
49 UCP_E_INV_XSER_TAG Invalid XSER tag for this message type


50 UCP_E_MND_XSER_MISS Mandatory XSER field missing or empty
51 UCP_E_XSER_ALL_FOR_LA An XSER tag allowed only for Large Accounts
52 UCP_E_INV_DCS_FOR_SIM_DATA Invalid DCS for SIM data download
53 UCP_E_SMS_PH2_LIC_REQ SMS phase 2 license required for SIM data download
54 UCP_E_NOT_LA Not a large account: use of OTOA rejected
55 UCP_E_NO_LIC_LRA No license for using of Last Resort Address
Table 2.37: GSM network errors

3 DUPLICATE_INVOKE_ID
4 NOT_A_SUPPORTED_SERVICE
5 MISTYPED_PARAMETER
6 RESOURCE_LIMITATION
7 INITIATING_RELEASE
14 UNRECOGNIZED_ERROR
15 UNEXPECTED_ERROR
46 UNEXPECTED_RESPONSE_FROM_PEER
47 SERVICE_COMPLETION_FAILURE
48 NO_RSP_FROM_PEER
49 INVALID_RSP_RECEIVED
50 NO_GTTRANS_NATURE
51 NO_GTTRANS_GLOBAL_TITLE
52 SUBSYSTEM_CONGESTED
53 SUBSYSTEM_FAILURE
54 USER_NOT_EQUIPPED
55 NETWORK_FAILURE
56 NETWORK_CONGESTED
57 UNQUALIFIED_REPORT_CAUSE
100 UNKNOWN_SUBSCRIBER
101 IMSI_UNKNOWN
102 GPRS_SUBSCRIPTION_UNKNOWN
128 TP_FCS_TELEMATIC_IW
129 TP_FCS_SM_TYPE0_UNSUPP
130 TP_FCS_REPLACE_FAILURE
143 TP_FCS_UNSPEC_PID_ERR
144 TP_FCS_DCS_UNSUPPORTED
145 TP_FCS_MSGCLASS_UNSUPP
159 TP_FCS_UNSPEC_DCS_ERR
160 TP_FCS_CMD_NOT_ACTIONED
161 TP_FCS_CMD_UNSUPPORTED
175 TP_FCS_UNSPEC_CMD_ERR
176 TP_FCS_TPDU_UNSUPPORTED
192 TP_FCS_SC_BUSY


193 TP_FCS_NO_SC_SUB
194 TP_FCS_SC_SYS_FAILURE
195 TP_FCS_INVALID_SME
196 TP_FCS_DST_SME_BARRED
197 TP_FCS_SM_REJECT_DUP
198 TP_FCS_VPF_UNSUPPORTED
199 TP_FCS_VP_UNSUPPORTED
208 TP_FCS_SIM_STORAGE_FULL
209 TP_FCS_NO_SIM_STORAGE
210 TP_FCS_ERROR_IN_MS
211 TP_FCS_MEMCAP_EXCEEDED
212 TP_FCS_SIM_APP_TOOLKIT_BUSY
213 TP_FCS_SIM_DOWNLOAD_ERROR
255 TP_FCS_UNSPECIFIED
500 UNIDENTIFIED_SUBSCRIBER
600 ABSENT_SUBSCRIBER_SM
601 NO_PAGING_RESPONSE_VIA_MSC
602 IMSI_DETACHED
603 ROAMING_RESTRICTION
604 DEREGISTERED_IN_HLR_FOR_NON_GPRS
605 MS_PURGED_FOR_NON_GPRS
606 NO_PAGING_RESPONSE_VIA_SGSN
607 GPRS_DETACHED
608 DEREGISTERED_IN_HLR_FOR_GPRS
609 MS_PURGED_FOR_GPRS
610 UNIDENTIFIED_SUBSCRIBER_VIA_MSC
611 UNIDENTIFIED_SUBSCRIBER_VIA_SGSN
900 ILLEGAL_SUBSCRIBER
1100 TELESERVICE_NOT_PROVISIONED
1110 SIM_PROTOCOL_ERROR
1200 ILLEGAL_EQUIPMENT
1300 CALL_BARRED
1301 BARRING_SERVICE_ACTIVE
1302 OPERATOR_BARRING
1400 CALL_BARRED_UNAUTH_MSG_ORIG
1500 CUG_REJECT
2100 FACILITY_NOT_SUPPORTED_ON_SRISM
2101 FACILITY_NOT_SUPPORTED_ON_FSM
2700 ABSENT_SUBSCRIBER
2701 IMSI_DETACH
2702 RESTRICTED_AREA
3100 SUBSCRIBER_BUSY_FOR_MT_SMS
3101 GPRS_CONNECTION_SUSPENDED
3200 MEMORY_CAPACITY_EXCEEDED
3201 EQUIPMENT_PROTOCOL_ERROR


3202 EQUIPMENT_NOT_SM_EQUIPPED
3203 UNKNOWN_SERVICE_CENTRE
3204 SERVICE_CENTRE_CONGESTION
3205 INVALID_SME_ADDRESS
3206 SUBSCRIBER_NOT_SC_SUBSCRIBER
3400 SYSTEM_FAILURE
3401 SYSTEM_FAILURE_WITH_NETWORK_RESOURCE
3500 DATA_MISSING
3600 UNEXPECTED_DATA_VALUE
4352 SCCP_NO_TRANS_ADDR_NATURE
4353 SCCP_NO_TRANS_SPEC_ADDR
4354 SCCP_SUBSYSTEM_CONGESTION
4355 SCCP_SUBSYSTEM_FAILURE
4356 SCCP_UNEQUIPPED_USER
4357 SCCP_MTP_FAILURE
4358 SCCP_NETWORK_CONGESTION
4359 SCCP_UNQUALIFIED
4360 SCCP_ERR_MSG_TRANS
4361 SCCP_ERR_LOCAL_PROCESS
4362 SCCP_DEST_NO_REASSEMBLY
4363 SCCP_FAILURE
4364 SCCP_HOP_COUNTER_VIOLATION
4365 SCCP_SEGM_NOT_SUPPORT
4366 SCCP_SEGM_FAILURE
4367 SCCP_ERR
4608 MAP_P_ERR_NO_RESPONSE_FROM_PEER
4609 MAP_P_ERR_SERVICE_COMPLETION_FAILURE
4610 MAP_P_ERR_INVALID_RESP_RECEIVED
4611 MAP_P_ERR_SERVICE_NOT_SUPPORTED
4612 MAP_P_ERR_MISTYPED_PARAMETER
4613 MAP_P_ERR_DUPLICATE_INVOKE_ID
4614 MAP_P_ERR_RESOURCE_LIMITATION
4615 MAP_P_ERR_INITIATING_RELEASE
4616 MAP_P_ERR_UNEXPECTED_RESPONSE_FROM_PEER
4864 MAP_P_ABRT_ERR
4865 MAP_P_ABRT_MALFUNCTION
4866 MAP_P_ABRT_DIALOG_RELEASED
4867 MAP_P_ABRT_RESOURCE_LIMIT
4868 MAP_P_ABRT_ABNORMAL_DIALOG
4869 MAP_P_ABRT_INVALID_PDU
5120 MAP_OPEN_REFUSE_OUT_OF_DIALOGS
5121 MAP_OPEN_REFUSE_REASON_UNKNOWN
5122 MAP_OPEN_REFUSE_REASON_INV_DEST_REF
5123 MAP_OPEN_REFUSE_REASON_INV_SRC_REF
5124 MAP_OPEN_REFUSE_REASON_AC_NOT_SUPP
5125 MAP_OPEN_REFUSE_REASON_NODE_NOT_REACH


5126 MAP_OPEN_REFUSE_REASON_POTENTIAL_VERSION_INCOMP
5376 MAP_NOTICE_UNEXPECTED_RESULT
5377 MAP_NOTICE_UNEXPECTED_ERROR
5378 MAP_NOTICE_ABNORMAL_EVENT_RECEIVED
5379 MAP_NOTICE_MESSAGE_CANNOT_BE_DELIVERED
5380 MAP_NOTICE_RESPONSE_REJECTED
5381 MAP_NOTICE_ABNORMAL_EVENT_DETECTED
5632 MAP_U_ABRT_ERR
5633 MAP_U_ABRT_USER_SPECIFIC_REASON
5634 MAP_U_ABRT_RESOURCE_LIMITATION
5635 MAP_U_ABRT_RESOURCE_UNAVAILABLE_SHORT_TERM
5636 MAP_U_ABRT_RESOURCE_UNAVAILABLE_LONG_TERM
5637 MAP_U_ABRT_PROC_CANCELLATION_REASON_HANDOVER
5638 MAP_U_ABRT_PROC_CANCELLATION_RADIO_CHANNEL_RELEASE
5639 MAP_U_ABRT_PROC_CANCELLATION_NETWORK_PATH_RELEASE
5640 MAP_U_ABRT_PROC_CANCELLATION_CALL_RELEASE
5641 MAP_U_ABRT_PROC_CANCELLATION_ASSOCIATED_PROCEDURE_FAILURE
5642 MAP_U_ABRT_PROC_CANCELLATION_TANDEM_DIALOG_RELEASE
5643 MAP_U_ABRT_PROC_CANCELLATION_REMOTE_OPERATIONS_FAILURE
9400 ESME2IMSI_BARRED
9401 FAKE_IMSI
9500 FDA_THROTTLING
9501 BARRED_LOCAL_SCREENING
Table 2.38: SMTP network errors

Service not available, closing transmission
421 421_SERVICE_NOT_AVAILABLE
channel
Requested mail action not taken: mailbox
450 450_MAILBOX_UNAVAILABLE
unavailable
Requested action aborted: local error in
451 451_LOCAL_ERROR_IN_PROCESSING
processing
Requested action not taken: insufficient
452 452_INSUFFICIENT_SYS_STORAGE
system storage
Server unable to accommodate
455 455_SERVER_UNABLE_TO_ACCOMMODATE_PARAMS
parameters
500 500_SYNTAX_ERROR Syntax error, command unrecognized
501 501_SYNTAX_ERROR_PARAM_ARG Syntax error in parameters or arguments
502 502_CMD_NOT_IMPL Command not implemented
503 503_BAD_SEQ_OF_CMDS Bad sequence of commands
504 504_CMD_PARAM_NOT_IMPL Command parameter not implemented
Requested action not taken: mailbox
550 550_MAILBOX_UNAVAILABLE
unavailable
551 551_USER_NOT_LOCAL User not local


Requested mail action aborted: exceeded
552 552_EXC_STORAGE_ALLOC
storage allocation
Requested action not taken: mailbox
553 553_MAILBOX_NAME_NOT_ALLOWED
name not allowed
554 554_TRANS_FAILED Transaction failed
MAIL FROM/RCPT TO parameters not
555 555_MAIL_FROM_RCPT_NOT_RECOGN_IMPL
recognized or not implemented
2.7.35 LAI
Location Area Identification in format MCC-MNC-LAC.

• MCC - 3 digits of Mobile Country Code.
• MNC - 2 or 3 digits of Mobile Network Code.
• LAC - 4 hexadecimal digits of Location Area Code.
2.7.36 PARENT_MSG_STATUS
This field determines the status of a parent message at a particular service point.
Table 2.39: Message statuses

0 SUBMITTED Message has been submitted.
1 REJECTED Message has been rejected.
2 ACCEPTED Message hes been accepted.
3 BUFFERED Message has been buffered.
4 DELIVERED Message has been delivered.
5 NOT_DEL_TEMP Message has not been delivered for a temporary reason.
6 NOT_DEL_PERM Message has not been delivered for a permanent reason.
7 DELETED Message has been deleted.
8 EXPIRED Message validity period has expired.
9 HANDED_OVER Message has been handed over.
10 NOT_HANDED_OVER Message has not been handed over.
2.7.37 MAP_OPER_ORIGIN
Inbound/outbound operation indicator.

Table 2.40: MAP operation origin

0 PLMN MAP operation initiated by PLMN
1 MCO MAP operation initiated by MCO
2.7.38 HLR_MODIF_REQ
HLR modification request for the MAP ATM operation.
Table 2.41: HLR modification request from IP-SM-GW

Update the IP-SM-GW Number stored in the HLR with
0 DEACTIVATE
status deactivated
Update the IP-SM-GW Number stored in the HLR with
1 ACTIVATE
status activated
2.7.39 REQ_SUBS_INFO
Requested subscription information in format <ss-code><service-type><service-code>:<odb>.
Table 2.42: Requested SS-info
Name Format Description

ss-code hexadecimal Supplementary service code
No service code is contained in the requested ss-info,
service-type 00
service-code is not present
01 Bearer service code is present in service-code
02 Teleservice code is present in service-code
service-code hexadecimal Teleservice or bearer service code
odb 0 ODB flags indicator is not present in the requested ss-info
1 ODB flags indicator is present in the requested ss-info
2.7.40 BASE_ERROR
A base cause of an operation failure.

It is composed of two parts: an error class (higher 16 bits) which is the interface, where the error occurred, and a specific error
code (lower 16 bits). For inbound operations, the error class (error source) is usually SM/AKIF/Internal; for outbound operations,
the error source is usually network interworking MAP/SMPP/UCP/SIP.
In the following table, a range of allowed error codes is assigned to each error class. These ranges should help to express
distinguished parts of referenced tables with error descriptions.

Table 2.43: Base error
Error class Name Error codes range Description

0x0001 - 0x00FF
0x0100 .... MAP-User Error code of a MAP operation, see Table 2.21
1 - 255
Failure cause of SUBMIT, SUBMIT-REPORT,
0x0001 - 0x2FFF
0x0300 .... GSM DELIVER, DELIVER-REPORT operations, see
1 - 12287
Table 2.37
0x0400 - 0x04FF Error code of an IS-41 operation, see
0x0400 .... IS-41
1024 - 1279 Table 2.21
0x0000 - 0x00FF
Native undefined cause error code
0 - 255
0x0001 - 0xFFFF
0x0500 .... SM Message error, see Table 2.17
1 - 65535
0x1200 - 0x1FFF Error code of a MAP dialogue operation, see
0x1000 .... MAP-non-User
4608 - 8191 Table 2.21
0x1000 - 0x1003
Message screening codes, see Table 2.21
4096 - 4099
0x1100 - 0x11FF Error code of an SCCP operation, see
0x1100 .... SCCP
4352 - 4607 Table 2.21
0x0001 - 0x01FF
0x2000 .... DC internal Internal error, see Table 2.44
1 - 511
0x0001 - 0x01FF
0x2100 .... DC AKIF AKIF error, see Table 2.45
1 - 511
0x0001 - 0x00FF
0x3000 .... UCP Error code of a UCP operation, see Table 2.36
1 - 255
0x0001 - 0xFFFF Error code of an SMPP operation, see
0x3100 .... SMPP
1 - 65535 Table 2.35
0x0001 - 0x04FF Error code of an SMTP operation, see
0x3200 .... SMTP
1 - 1279 Table 2.38
0x6000 - 0x6FFF
0x6000 .... SIP Error code of a SIP operation, see Table 2.21
24576 - 28671
Table 2.44: DC internal errors

1 P_UNKNOWN Unknown subscriber
2 P_GPRS_UNKNOWN Unknown subscriber over GPRS
5 T_UNIDENTIFIED Unidentified subscriber
9 P_ILLEGAL_SUB Illegal subscriber
11 P_PROVISION Not Provisioned service
12 P_ILLEGAL_MS Illegal equipment
13 T_BARRED Barred call
14 P_BARRED_UNAUTH_MSG_ORIG Barred unauthorized message originator
15 P_CUG CUG reject
21 T_SUPPORT Not Supported facility
22 T_SUPPORT_ROAMING Not Supported roaming
31 T_BUSY Busy subscriber
32 T_GPRS_BUSY Busy subscriber over GPRS


34 T_SYSTEM System Failure
35 T_DATA_MISSING Data Missing
36 T_UNEXPECTED_DATA Unexpected Data Value
40 T_MEMCAP Memory Capacity Exceeded
41 T_MSERROR Protocol Error in equipment
42 T_MSSUPPORT Not Supported by equipment
43 P_TYPE_ZERO_MSSUPPORT Not Supported by equipment
44 T_MSREPLACE Message Raplace Failure
45 P_MSPID Unspecific PID Error
46 P_SMCLASS_MSSUPPORT Message Class Not Supported
47 P_MSDCS DCS Error
48 P_TPDU_MSSUPPORT TPDU Not Supported
49 T_MS_SIM_FULL SIM Full
50 P_SIM_STORE_MSSUPPORT No SMS Storage in SIM
53 T_SIMTK_BUSY Busy SIM Application Toolkit
54 P_SIM_DOWNLOAD Data Download Error
60 T_ABSENT Absent subscriber
61 T_ABSENT_DETACHED Absent subscriber Detached
62 T_ABSENT_PAGEFAIL Absent subscriber Page Fail
63 T_ABSENT_RESTRICTED Absent subscriber Restricted
64 T_ABSENT_DEREGISTERED Absent subscriber Deregistered
65 T_ABSENT_PURGED Absent subscriber Purged
66 T_GPRS_PAGEFAIL Absent subscriber over GPRS Page Fail
67 T_GPRS_DETACHED Absent subscriber over GPRS Detached
Absent subscriber over GPRS
68 T_GPRS_DEREGISTERED
Deregistered
69 T_GPRS_PURGED Absent subscriber over GPRS Purged
70 T_ABSENT_UNIDENTIFIED Absent subscriber unidentified over MSC
71 T_GPRS_UNIDENTIFIED Absent subscriber unidentified over GPRS
80 T_SS7_DUPLICATE_ID Duplicated invoke id
81 T_SS7_SUPPORT Service not supported
82 T_SS7_MISTYPED_PARAM Mistyped parameter
83 T_SS7_TIMEOUT No response from the peer
84 T_SS7_RESOURCE_LIMITATION Resource limitation
85 T_SS7_INITIATING_RELEASE Initiating release
86 T_SS7_UNRECOGNISED_ERROR Unrecognised error
87 T_SS7_UNEXPECTED_ERROR Unexpected error
88 T_SS7_UNEXPECTED_RESPONSE Unexpected response from the peer
Unable to complete operation within
89 T_SS7_COMPLETION_FAILURE
timeout
90 T_SS7_INVALID_RESPONSE Invalid response received
91 T_SS7_TCAP_ERROR TCAP error
92 P_SS7_TCAP_NO_GTT_ADDR TCAP GT translation failure
93 T_SM_DATA_ERROR SM decoding problem
94 T_ESME2IMSI_BARRED Subscriber is not located in Home PLMN
95 T_FAKE_IMSI Barred by local screening


No translation for an address of such
100 P_SCCP_NOTRAN_NOA
nature
101 P_SCCP_NOTRAN_ADDR No translation for this specific address
102 T_SCCP_SS_CONG Subsystem congestion
103 T_SCCP_SS_FAIL Subsystem failure
104 P_SCCP_UNEQUIPPED Unequipped user
105 T_SCCP_MTP_FAIL MTP failure
106 T_SCCP_NW_CONG Network congestion
107 P_SCCP_UNQUALIFIED Unqualified
108 T_SCCP_MSG_TRANS Error in message transport
109 T_SCCP_LOCAL_PROC Error in local processing
110 P_SCCP_REAS_UNSUP Destination cannot perform reassembly
111 T_SCCP_FAILURE SCCP failure
112 T_SCCP_HOPC_VIOL Hop counter violation
113 P_SCCP_SEGM_UNSUP Segmentation not supported
114 P_SCCP_SEGM_FAIL Segmentation failure
120 T_ANSI_TCAP_UNKNOWN_ERROR Unknown TCAP error
121 P_ANSI_TCAP_RET_ERR_UNREC_MIN Unrecognized MIN
122 P_ANSI_TCAP_RET_ERR_UNREC_ESN Unrecognized ESN
123 P_ANSI_TCAP_RET_ERR_ID_HLR_MISMATCH ID/HLR mismatch
124 T_ANSI_TCAP_RET_ERR_OPER_SEQ_PROBLEM Operation sequence problem
125 T_ANSI_TCAP_RET_ERR_RES_SHORT Resource shortage
126 P_ANSI_TCAP_RET_ERR_OPER_NOT_SUP Operation not supported
127 T_ANSI_TCAP_RET_ERR_TRUNK_UNAVAIL Trunk unavailable
128 T_ANSI_TCAP_RET_ERR_PARAM_ERR Parameter error
129 T_ANSI_TCAP_RET_ERR_SYS_FAIL System failure
130 T_ANSI_TCAP_RET_ERR_UNREC_PARAM_VAL Unrecognized parameter value
131 T_ANSI_TCAP_RET_ERR_FEAT_INACT Feature inactive
132 T_ANSI_TCAP_RET_ERR_MISS_PARAM Missing parameter
133 T_ANSI_TCAP_RET_ERR_UNREC_IMSI_TMSI Unrecognized IMSI/TMSI
134 T_ANSI_TCAP_RET_ERR_TMSI_VLR_MISM TMSI/VLR mismatch
General problem unrecognized
135 T_ANSI_TCAP_REJ_GEN_UNREC_COMP_TYPE
component type
General problem incorrect component
136 T_ANSI_TCAP_REJ_GEN_INCOR_COMP
portion
137 T_ANSI_TCAP_REJ_GEN_BAD_STRUCT_COMP
portion
138 T_ANSI_TCAP_REJ_GEN_INCOR_COMP_COD
coding
139 T_ANSI_TCAP_REJ_INV_DUP_INV_ID Invoke problem duplicate invocation
140 T_ANSI_TCAP_REJ_INV_UNREC_OP Invoke problem unrecognized operation
141 T_ANSI_TCAP_REJ_INV_INCOR_PARAM Invoke problem incorrect parameter
Invoke problem unrecognized correlation
142 T_ANSI_TCAP_REJ_INV_UNREC_COR_ID
id
Return result problem unrecognized
143 T_ANSI_TCAP_REJ_RR_UNREC_COR_ID
correlation id


Return result problem unexpected return
144 T_ANSI_TCAP_REJ_RR_UNEXP_RETRES
result
145 T_ANSI_TCAP_REJ_RR_INCOR_PARAM Return result problem incorrect parameter
Return error problem unrecognized
146 T_ANSI_TCAP_REJ_RE_UNREC_COR_ID
correlation id
Return error problem unexpected return
147 T_ANSI_TCAP_REJ_RE_UNEXP_RETERR
error
148 T_ANSI_TCAP_REJ_RE_UNREC_ERROR Return error problem unrecognized error
149 T_ANSI_TCAP_REJ_RE_UNEXP_ERROR Return error problem unexpected error
150 T_ANSI_TCAP_REJ_RE_INCOR_PARAM Return error problem incorrect parameter
Transaction portion problem unrecognized
151 T_ANSI_TCAP_REJ_TP_UNREC_PKG_TYPE
package type
Transaction portion problem incorrect
152 T_ANSI_TCAP_REJ_TP_INCOR_TP
transaction portion
Transaction portion problem badly
153 T_ANSI_TCAP_REJ_TP_BAD_STRUCT_TP
structured transaction portion
154 T_ANSI_TCAP_REJ_TP_UNREC_TRANSID
transaction id
Transaction portion problem permission to
155 T_ANSI_TCAP_REJ_TP_PERM_RELEAS_PB
release problem
Transaction portion problem resource
156 T_ANSI_TCAP_REJ_TP_RESOUR_UNAVAIL
unavailable
157 T_ANSI_TCAP_ABORT TCAP abort
160 T_MAP_P_ERR_NO_RESPONSE_FROM_PEER MAP-P: No response from the peer
161 T_MAP_P_ERR_SERVICE_COMPLETION_FAILURE MAP-P: Service completion failure
162 T_MAP_P_ERR_INVALID_RESP_RECEIVED MAP-P: Invalid response received
163 T_MAP_P_ERR_SERVICE_NOT_SUPPORTED MAP-P: Service not supported
164 T_MAP_P_ERR_MISTYPED_PARAMETER MAP-P: Mistyped parameter
165 T_MAP_P_ERR_DUPLICATE_INVOKE_ID MAP-P: Duplicated invoke id
166 T_MAP_P_ERR_RESOURCE_LIMITATION MAP-P: Resource limitation
167 T_MAP_P_ERR_INITIATING_RELEASE MAP-P: Initiating release
MAP-P: Unexpected response from the
168 T_MAP_P_ERR_UNEXP_RESPONSE_FROM_PEER
peer
169 T_MAP_P_ABRT_ERR MAP-P-Abort: Provider reasons
170 T_MAP_P_ABRT_MALFUNCTION MAP-P-Abort: Provider malfunction
171 T_MAP_P_ABRT_DIALOG_RELEASED MAP-P-Abort: Transaction released
172 T_MAP_P_ABRT_RESOURCE_LIMIT MAP-P-Abort: Resource limitation
173 T_MAP_P_ABRT_ABNORMAL_DIALOG MAP-P-Abort: Abnormal MAP dialogue
174 T_MAP_P_ABRT_INVALID_PDU MAP-P-Abort: Invalid PDU
175 T_MAP_OPEN_REFUSE_OUT_OF_DIALOGS MAP-Open: Out of MAP dialogs
176 T_MAP_OPEN_REFUSE_REASON_UNKNOWN MAP-Open: No reason given
177 P_MAP_OPEN_REFUSE_REASON_INV_DEST_REF MAP-Open: Invalid destination reference
178 P_MAP_OPEN_REFUSE_REASON_INV_SRC_REF MAP-Open: Invalid originating reference
MAP-Open: Application context not
179 P_MAP_OPEN_REFUSE_REASON_AC_NOT_SUPP
supported
180 T_MAP_OPEN_REFUSE_REASON_NODE_NOT_REACH MAP-Open: Remote node not reachable
MAP-Open: Potential version
181 T_MAP_OPEN_REFUSE_REASON_POTEN_VER_INCOMP
incompatibility


182 T_MAP_NOTICE_UNEXPECTED_RESULT MAP-Notice: Unexpected result
183 T_MAP_NOTICE_UNEXPECTED_ERROR MAP-Notice: Unexpected error
MAP-Notice: Abnormal event received
184 T_MAP_NOTICE_ABNORMAL_EVENT_RECEIVED
from peer
MAP-Notice: Message cannot be
185 T_MAP_NOTICE_MESSAGE_CANNOT_BE_DELIVERED
delivered to peer
186 T_MAP_NOTICE_RESPONSE_REJECTED MAP-Notice: Response rejected by peer
MAP-Notice: Abnormal event detected by
187 T_MAP_NOTICE_ABNORMAL_EVENT_DETECTED
peer
188 T_MAP_U_ABRT_ERR MAP-U-Abort: Error
189 T_MAP_U_ABRT_USER_SPECIFIC_REASON MAP-U-Abort: User specific reason
190 T_MAP_U_ABRT_RES_LIMIT MAP-U-Abort: User resource limitation
MAP-U-Abort: Resource unavailable
191 T_MAP_U_ABRT_RES_UNAVAIL_SHORT_TERM
(short term)
MAP-U-Abort: Resource unavailable (long
192 T_MAP_U_ABRT_RES_UNAVAIL_LONG_TERM
term)
MAP-U-Abort: Application procedure
193 T_MAP_U_ABRT_PCANCEL_REASON_HANDOVER
cancellation (handover cancellation)
194 T_MAP_U_ABRT_PCANCEL_RADIO_CHAN_REL
cancellation (radio channel release)
195 T_MAP_U_ABRT_PCANCEL_NETWORK_PATH_REL
cancellation (network path release)
196 T_MAP_U_ABRT_PCANCEL_CALL_RELEASE
cancellation (call release)
197 T_MAP_U_ABRT_PCANCEL_ASSOC_PROC_FAIL
cancellation (associated procedure failure)
198 T_MAP_U_ABRT_PCANCEL_TAND_DIALOG_REL
cancellation (tandem dialogue released)
199 T_MAP_U_ABRT_PCANCEL_REM_OPER_FAIL
cancellation (remote operations failure)
230 APP_NW_CUSTOM_1 Custom error 1
240 APP_NW_TEMP Recipient Temporary Error
241 APP_NW_PERM Recipient Permanent Error
Message Permanent Error / Delete One
242 APP_NW_REJECT
Message
243 APP_NW_TMOUT Timeout
244 APP_NW_ERROR Unspecific
245 APP_NW_CONGEST Congested
246 APP_NW_DISC Disconnected


247 APP_NW_CONNTMOUT Connection Has Timeout
248 APP_NW_NOCONN No Connection
MO Handover: Not Supported by
251 P_MO_TYPE_ZERO_MSSUPPORT
equipment
252 T_MO_MSREPLACE MO Handover: Message Raplace Failure
253 P_MO_MSPID MO Handover: Unspecific PID Error
254 P_MO_MSDCS MO Handover: DCS Error
255 P_MO_TPDU_MSSUPPORT MO Handover: TPDU Not Supported
256 P_MO_DCSSUPPORT MO Handover: DCS not supported
MO Handover: SMS Command cannot be
257 P_MO_CMD_NOT_ACTIONED
actioned
MO Handover: SMS Command
258 P_MO_CMD_SUPPORT
unsupported
259 P_MO_CMD_ERROR MO Handover: SMS Command error
260 T_MO_SC_BUSY MO Handover: SC Busy
261 P_MO_NOT_SC_SUBSCRIBER MO Handover: Not SC Subcriber
262 P_MO_INVALID_SME MO Handover: Invalid SME Address
263 P_MO_SME_BARRED MO Handover: Destination SME Barred
MO Handover: Duplicate Message
264 P_MO_REJECT_DUP
Rejected
MO Handover: Validity Period Format
265 P_MO_VPF_SUPPORT
Unsupported
MO Handover: Validity Period
266 P_MO_VP_SUPPORT
Unsupported
MO Handover: Not Supported by
267 T_MO_MSSUPPORT
equipment
268 T_MO_SYSTEM MO Handover: System Error
269 T_MO_SS7_DUPLICATE_ID MO Handover: Duplicated invoke id
270 T_MO_SS7_SUPPORT MO Handover: Service not supported
271 T_MO_SS7_MISTYPED_PARAM MO Handover: Mistyped parameter
272 T_MO_SS7_TIMEOUT MO Handover: No response from the peer
273 T_MO_SS7_RESOURCE_LIMITATION MO Handover: Resource limitation
274 T_MO_SS7_INITIATING_RELEASE MO Handover: Initiating release
275 T_MO_SS7_UNRECOGNISED_ERROR MO Handover: Unrecognised error
276 T_MO_SS7_UNEXPECTED_ERROR MO Handover: Unexpected error
MO Handover: Unexpected response
277 T_MO_SS7_UNEXPECTED_RESPONSE
from the peer
MO Handover: Unable to complete
278 T_MO_SS7_COMPLETION_FAILURE
operation within timeout
279 T_MO_SS7_INVALID_RESPONSE MO Handover: Invalid response received
280 T_MO_SS7_TCAP_ERROR MO Handover: TCAP error
MO Handover: TCAP GT translation
281 P_MO_SS7_TCAP_NO_GTT_ADDR
failure
282 P_MO_UNKNOWN_SC MO Handover: Unknown SC Address
283 T_MO_SC_CONGESTED MO Handover: SC Congested
284 T_MO_SUPPORT MO Handover: Not Supported
285 T_MO_UNEXPECTED_DATA MO Handover: Unexpected Data Value


MO Handover: Telematic Interworking not
286 P_MO_TELEMATIC_SUPPORT
Supported
287 T_MO_FDA_THROTTLE MO Handover: FDA throttled
288 T_MO_SM_DATA_ERROR MO Handover: SM decoding problem
300 L_RECEIVER_FULL No free AKIF contexts
301 L_NO_RECEIVER Receiver not connected
303 L_NO_AIM AIM handling delivery is not available
Table 2.45: DC AKIF errors

1 INVTEXTLEN Invalid text length
2 INVMSGPRIORITY Invalid message priority
3 INVREGVAL Invalid registered value
4 INVBILLIND Invalid billing indicator
5 INVSCHED Scheduled time exceeds maximum limit
6 INVEXPIRY Expiry time is in the past or before scheduled date
7 INVROUTINGEXP Invalid routing expression
8 SRCNOTALLOW Source address is not allowed to send short messages
9 INVSRCTON Invalid source TON
10 INVSRCNPI Invalid source NPI
11 INVSRCADDRLEN Invalid source address length
12 UGRESTRICTED Interface restricted by user group
13 OCOSINVALID Source OCOS does not match the interface class of service
Destination address is not allowed to receive short
14 DSTNOTALLOW
messages
15 INVDATA Invalid data supplied to interface
16 INVDSTTON Invalid destination TON
17 INVDSTNPI Invalid destination NPI
18 INVDSTADDRLEN Invalid destination address length
19 DBERROR Database error
Destination TCOS does not match the interface class of
20 TCOSINVALID
service
21 INVALSRC Invalid source address
22 SUBMITFAIL Submit operation failed
23 GACKFAIL GACK operation failed
24 IFXFAIL IFX: operation failed
25 IFXNOCHANNEL IFX: no channel available
26 IFXNOTRIGGER IFX: no trigger present
27 IFXNOMEM IFX: message pool is full
28 IFXMSGERROR IFX: message error
29 IFXSENDERROR IFX: send message operation failed
30 IFXTIMEOUT IFX: operation timeout
31 TIMEOUT AKIF timeout
32 TRDELIVERYFAIL Transaction delivery failed


33 MSGNOTFOUND Message not found
34 INVSEARCHFLAGS Invalid search flags
37 DBEXISTS DB: message already exists
38 DBFULL DB: storage is full
39 DBNOPRIV DB: message is busy
40 THROTTLED Interface throttled
41 MT_TRAN_MSG_PENDING MT transactional message pending
42 MO_TRAN_MSG_PENDING MO transactional message pending
44 EFMS_SYNC_ERROR EFMS disk synchronization error
45 SIZE_LIMIT_EXCEEDED SME data size limit exceeded
46 UNKNOWN_HANDLE Unknown handle
47 UNKNOWN_IFX_MSG Unknown IFX message
48 SME_BUSY SME Busy
49 SME_RETRY_EINPROGRESS SME Retry in progress
50 SME_RETRY_ELIMIT_EXCEEDED SME Retry too many concurrent retries
51 INVALMSGID Invalid message ID
52 INVALDST Invalid destination address
-1 ERROR Error
2.7.41 ICID
IMS charging identifier from MAPv3 extension, see 3GPP Technical Specification 32.260.
2.7.42 UCID
Untranslated Cell-ID from MAPv3 extension, see 3GPP Technical Specification 25.401.
2.7.43 LRN
Location Routing Number. Typically obtained from an ENUM response as a part of Routing Number.
2.7.44 SMPP_COMMAND_ID
This field determines the type of an SMPP operation.
Table 2.46: SMPP command ID

This is not real SMPP command Id, it is MCO indication that
0 INVALID_DATA
some invalid data has been received
1 BIND_RECEIVER
2 BIND_TRANSMITTER
3 QUERY_SM


4 SUBMIT_SM
5 DELIVER_SM
6 UNBIND
7 REPLACE_SM
8 CANCEL_SM
9 BIND_TRANSCEIVER
11 OUTBIND
21 ENQUIRE_LINK
33 SUBMIT_MULTI
258 ALERT_NOTIFICATION
259 DATA_SM
273 BROADCAST_SM
274 QUERY_BROADCAST_SM
275 CANCEL_BROADCAST_SM
2147483
GENERIC_NACK
648
2147483
BIND_RECEIVER_RESP
649
2147483
BIND_TRANSMITTER_RESP
650
2147483
QUERY_SM_RESP
651
2147483
SUBMIT_SM_RESP
652
2147483
DELIVER_SM_RESP
653
2147483
UNBIND_RESP
654
2147483
REPLACE_SM_RESP
655
2147483
CANCEL_SM_RESP
656
2147483
BIND_TRANSCEIVER_RESP
657
2147483
ENQUIRE_LINK_RESP
669
2147483
SUBMIT_MULTI_RESP
681
2147483
DATA_SM_RESP
907
2147483
BROADCAST_SM_RESP
921
2147483
QUERY_BROADCAST_SM_RESP
922
2147483
CANCEL_BROADCAST_SM_RESP
923

2.7.45 SMPP_MESSAGE_STATE
This field determines the type of an SMPP message state.
Table 2.47: SMPP message state

0 SCHEDULED
1 ENROUTE
2 DELIVERED
3 EXPIRED
4 DELETED
5 UNDELIVERABLE
6 ACCEPTED
7 UNKNOWN
8 REJECTED
9 SKIPPED
2.7.46 SMPP_COMMAND_STATUS
This field determines the success or failure of a SMPP request. It is relevant only in the SMPP response messages and for SMPP
request messages is empty. Field value represents the SMPP network error codes, MCO known codes are listed in Table 2.35.
2.7.47 OPER_ORIGIN
This field determines the origin of operation.
Table 2.48: Operation origin

0 NETWORK Operation initiated by NETWORK
1 MCO Operation initiated by MCO
2.8 AVRO stream types
The AVRO_SM (AVRO_MAP , AVRO_SIP , AVRO_SMPP ) stream type is used for integration of MCO with Mavenir Analytics. Records
are sent directly to Analytics Kafka instead of storing them in CSV formated files. All fields available in the CSV_SM (CSV_MAP ,
CSV_SIP , AVRO_SMPP ) stream are also available in this stream type including formats and masks.
Key differences between native CSV and AVRO streams:
• The LOG_TIME field is not enforced but is currently mandatory to create a record timestamp in the Analytics database.
• Only format DATE(MSEC) can be used with T-STAMP fields.
• Records are encoded in the Avro format. There are restrictions for modification of AVRO streams. Forward and backward
compatibility of Avro schemes should be maintained. Only backward compatibility is enforced. Note that history records will not
be readable from a Kafka topic, if the currently registered Avro scheme is not backward compatible with the older records.

• Custom fields can be used. A custom field name is formated to the Avro field name character set. Field $<attr_group>.
<attr_name> will be available as field __CUSTOM_<attr_group>_<attr_name> in Analytics.
• A change of the format on SM_TEXT from STRING to O-STRING also changes the type of the Avro field from string to bytes.

3 Legacy SDR Streams
This chapter describes legacy SDR streams provided by MCO R3.0 for integration with legacy billing and statistical systems.
3.1 MCO 2.3 CSV billing files
This section describes legacy MCO R2.3 CSV billing files. The CSV SM stream type is available as CSV_SM_23 stream type and
CSV MAP stream type is available as CSV_MAP_23 stream type.
The CSV_MAP_23 SDR stream (Section 3.1.2) can be used for recording received MO-FW-SM, MT-FW-SM and SRI-SM MAP
operations. These are mapped to the following service points:
• MAP Operation service point
• Incoming SRI-SM-IND service point
• Incoming SRI-SM-CNF service point
The CSV_SM_23 SDR stream (Section 3.1.3) can be used for recording (normalised/agnostic) short messages regardless of an
originating and/or terminating interface. It is mapped on the following service points:
• Incoming service point
• Incoming Complete service point
• Routing service point
• Outgoing service point
• Outgoing Complete service point
• Final service point
Warning
A short message received from PLMN (received as an MO-FW-SM or MT-FW-SM MAP operation) and logged into the
MAP SDR stream contains decoded information up to (including) the MAP layer. Information encoded in the SMS layer
is written undecoded into the stream while the same message logged into the SM SDR stream contains also a decoded
SMS layer.
3.1.1 Types of SDR parameters
Each SDR parameter can be of one of the following types only; see Table 3.1.
Table 3.1: Parameter types
Parameter type Coding

STRING ASCII string
UTF-STRING UTF8 string
OCTET-STRING Sequence of bytes (two hexadecimal digits in each byte)
UINT8/16/32/64 Number
INT8/16/32/64 Number
BOOLEAN 0 or 1

3.1.2 MAP SDR stream
The MAP SDR stream is used for logging GSM MAP operations. A generated MAP SDR can contain fields listed in Table 3.2.
Important
The table lists all available attributes in a random order. The first column (#) denotes an attribute’s position in the table.
Whether a particular field appears in a produced SDR and on which position can be configured using the name the attribute
in the second column.
Table 3.2: Possible parameters of MAP SDR stream
Max
# Name Type Description
length
Possible values: PRE_SUBMIT,
POST_SUBMIT, PRE_DELIVERY,
1 SDR_RECORD_TYPE STRING 13
POST_DELIVERY, SRI_REQ,
SRI_RESP
2 SDR_FORMAT STRING 3 “MAP”
Unix timestamp (seconds passed since
3 SDR_LOG_TIME UINT32 14
(UTC) Jan 1 1970)
OCTET-
4 MESSAGE_ID 16 Unique identifier of a message
STRING[16]
Identifies the originating network type,
5 SDR_NETWORK_TYPE UINT8 1
see Table 3.17.
ISDN- Type of number of MSISDN related to
6 SRISM_MSISDN_RECIP_TON 1
ADDR.TON SRI-SM of the recipient, see Table 3.16.
Numbering plan indicator of MSISDN
7 SRISM_MSISDN_RECIP_NPI ISDN-ADDR.NPI 2 related to SRI-SM of the recipient, see
Table 3.16.
MSISDN related to SRI-SM of the
8 SRISM_MSISDN_ RECIP_ADDRESS UTF-STRING 512
recipient, see Table 3.16.
9 SRISM_IMSI_RECIP STRING[16] 16 IMSI related to SRI-SM of the recipient
Type of number of an MSC address
SRISM_NETW_NODE_ ISDN-
10 1 related to SRI-SM of the recipient, see
ADDR_RECIP_TON ADDR.TON
Table 3.16
Numbering plan indicator of an MSC
SRISM_NETW_NODE_
11 ISDN-ADDR.NPI 2 address related to SRI-SM of the
ADDR_RECIP_NPI
SRISM_NETW_NODE_ MSC address related to SRI-SM of the
12 UTF-STRING 512
ADDR_RECIP_ADDRESS recipient, see Table 3.16.
Type of number of an SGSN address
SRISM_SGSN_NODE_ ISDN-
13 1 related to SRI-SM of the recipient, see
ADDR_RECIP_TON ADDR.TON
Table 3.16.
Numbering plan indicator of an SGSN
SRISM_SGSN_NODE_
ADDR_RECIP_NPI
SRISM_SGSN_NODE_ SGSN address related to SRI-SM of the
15 UTF-STRING 512
ADDR_RECIP_ADDRESS recipient, see Table 3.16.

Max
length
ISDN- Type of number of an SMSC address in
16 SRISM_SC_ADDR_TON 1
ADDR.TON SRI-SM, see Table 3.16.
Numbering plan indicator of an SMSC
17 SRISM_SC_ADDR_NPI ISDN-ADDR.NPI 2
address in SRI-SM, see Table 3.16.
SMSC address in SRI-SM, see
18 SRISM_SC_ADDR_ADDRESS UTF-STRING 512
Table 3.16.
ISDN- Type of number of MSISDN related to
19 SRISM_MSISDN_ORIG_TON 1
ADDR.TON SRI-SM of the originator, see Table 3.16.
Numbering plan indicator of MSISDN
20 SRISM_MSISDN_ORIG_NPI ISDN-ADDR.NPI 2 related to SRI-SM of the originator, see
Table 3.16.
MSISDN related to SRI-SM of the
21 SRISM_MSISDN_ORIG_ADDRESS UTF-STRING 512
originator, see Table 3.16.
22 SRISM_IMSI_ORIG STRING[16] 16 IMSI related to SRI-SM of the originator
Type of number of an MSC address
SRISM_NETW_NODE_ ISDN-
23 1 related to SRI-SM of the originator, see
ADDR_ORIG_TON ADDR.TON
Table 3.16.
Numbering plan indicator of an MSC
SRISM_NETW_NODE_
ADDR_ORIG_NPI
originator, see Table 3.16
SRISM_NETW_NODE_ MSC address related to SRI-SM of the
25 UTF-STRING 512
ADDR_ORIG_ADDRESS originator, see Table 3.16.
Type of number of an SGSN address
SRISM_SGSN_NODE_ ISDN-
26 1 related to SRI-SM of the originator, see
ADDR_ORIG_TON ADDR.TON
Table 3.16.
SRISM_SGSN_NODE_
ADDR_ORIG_NPI
originator, see Table 3.16.
SRISM_SGSN_NODE_ SGSN address related to SRI-SM of the
28 UTF-STRING 512
ADDR_ORIG_ADDRESS originator, see Table 3.16.
ISDN- Type of number of the SM RP OA field in
29 MO_MSISDN_TON 1
ADDR.TON MAP-MO-FWSM, see Table 3.16.
Numbering plan indicator of SM RP OA in
30 MO_MSISDN_NPI ISDN-ADDR.NPI 2
MAP-MO-FWSM, see Table 3.16.
SM RP OA in MAP-MO-FWSM, see
31 MO_MSISDN_ADDRESS UTF-STRING 512
Table 3.16.
IMSI received in MAP-MO-FWSM or
IMSI returned by HLR as a result of the
32 MO_IMSI STRING[16] 16
originator validation. The latter takes
precedence if both values are available.
ISDN- Type of number of the SM RP DA field in
33 MO_SC_ADDR_TON 1
ADDR.TON MAP-MO-FWSM, see Table 3.16.
Numbering plan indicator of SM RP DA in
34 MO_SC_ADDR_NPI ISDN-ADDR.NPI 2
MAP-MO-FWSMs, see Table 3.16.
SM RP DA in MAP-MO-FWSM, see
35 MO_SC_ADDR_ADDRESS UTF-STRING 512
Table 3.16.
ISDN- Type of number of SM RP OA in
36 MT_SC_ADDR_TON 1
ADDR.TON MAP-MT-FWSM, see Table 3.16.

Max
length
Numbering plan indicator of SM RP OA in
37 MT_SC_ADDR_NPI ISDN-ADDR.NPI 2
MAP-MT-FWSM, see Table 3.16.
SM RP OA in MAP-MT-FWSM, see
38 MT_SC_ADDR_ADDRESS UTF-STRING 512
Table 3.16.
39 MT_IMSI STRING[1..16] 16 SM RP DA in MAP-MT-FWSM
OCTET- The SM RP UI field in MAP-MO-FWSM
40 MAP_DATA_LOAD 255
STRING[1..255] or MAP-MT-FWSM
41 GSM_TPDU_MTI UINT8 3 GSM TP-MTI
42 GSM_TPDU_MMS BOOLEAN 1 GSM TP-MMS
43 GSM_TPDU_LP BOOLEAN 1 GSM TP-LP
44 GSM_TPDU_RP BOOLEAN 1 GSM TP-RP
45 GSM_TPDU_UDHI BOOLEAN 1 GSM TP-UDHI
46 GSM_TPDU_SRI BOOLEAN 1 GSM TP-SRI
OCTET-STRING
47 GSM_TPDU_OA 12 GSM TP-OA
[2..12]
48 GSM_TPDU_PID UINT8 3 GSM TP-PID
49 GSM_TPDU_DCS UINT8 3 GSM TP-DCS
OCTET-STRING
50 GSM_TPDU_SCTS 7 GSM TP-SCTS
[7]
51 GSM_TPDU_UDL UINT8 3 GSM TP-UDL
OCTET-STRING
52 GSM_TPDU_UD 160 GSM TP-UD
[0..160]
53 GSM_TPDU_FCS UINT8 3 GSM TP-FCS
54 GSM_TPDU_PI UINT8 3 GSM TP-PI
55 GSM_TPDU_RD BOOLEAN 1 GSM TP-RD
56 GSM_TPDU_VPF UINT8 3 GSM TP-VPF
57 GSM_TPDU_SRR BOOLEAN 1 GSM TP-SRR
58 GSM_TPDU_MR UINT8 3 GSM TP-MR
OCTET-STRING
59 GSM_TPDU_DA 12 GSM TP-DA
[2..12]
OCTET-STRING
60 GSM_TPDU_VP 7 GSM TP-VP
[1..7]
61 GSM_TPDU_SRQ BOOLEAN 1 GSM TP-SRQ
OCTET-STRING
62 GSM_TPDU_RA 12 GSM TP-RA
[2..12]
OCTET-STRING
63 GSM_TPDU_DT 7 GSM TP-DT
[7]
64 GSM_TPDU_ST UINT8 3 GSM TP-ST
65 GSM_TPDU_CT UINT8 3 GSM TP-CT
66 GSM_TPDU_MN UINT8 3 GSM TP-MN
67 GSM_TPDU_CDL UINT8 3 GSM TP-CDL
68 GSM_TPDU_CD UINT8 3 GSM TP-CD
OCTET- SM RP UI in an SM response. This field
69 MAP_RESPONSE_DATA_LOAD 255
STRING[1..255] is conditional with gsmRespTpdu.
70 GSM_RESP_TPDU_MTI UINT8 3 GSM_RESP_TPDU_MTI
71 GSM_RESP_TPDU_MMS BOOLEAN 1 GSM_RESP_TPDU_MMS
72 GSM_RESP_TPDU_LP BOOLEAN 1 GSM_RESP_TPDU_LP

Max
length
73 GSM_RESP_TPDU_RP BOOLEAN 1 GSM_RESP_TPDU_RP
74 GSM_RESP_TPDU_UDHI BOOLEAN 1 GSM_RESP_TPDU_UDHI
75 GSM_RESP_TPDU_SRI BOOLEAN 1 GSM_RESP_TPDU_SRI
OCTET-STRING
76 GSM_RESP_TPDU_OA 12 GSM_RESP_TPDU_OA
[2..12]
77 GSM_RESP_TPDU_PID UINT8 3 GSM_RESP_TPDU_PID
78 GSM_RESP_TPDU_DCS UINT8 3 GSM_RESP_TPDU_DCS
OCTET-STRING
79 GSM_RESP_TPDU_SCTS 7 GSM_RESP_TPDU_SCTS
[7]
80 GSM_RESP_TPDU_UDL UINT8 3 GSM_RESP_TPDU_UDL
OCTET-STRING
81 GSM_RESP_TPDU_UD 160 GSM_RESP_TPDU_UD
[0..160]
82 GSM_RESP_TPDU_FCS UINT8 3 GSM_RESP_TPDU_FCS
83 GSM_RESP_TPDU_PI UINT8 3 GSM_RESP_TPDU_PI
84 GSM_RESP_TPDU_RD BOOLEAN 1 GSM_RESP_TPDU_RD
85 GSM_RESP_TPDU_VPF UINT8 3 GSM_RESP_TPDU_VPF
86 GSM_RESP_TPDU_SRR BOOLEAN 1 GSM_RESP_TPDU_SRR
87 GSM_RESP_TPDU_MR UINT8 3 GSM_RESP_TPDU_MR
OCTET-STRING
88 GSM_RESP_TPDU_DA 12 GSM_RESP_TPDU_DA
[2..12]
OCTET-STRING
89 GSM_RESP_TPDU_VP 7 GSM_RESP_TPDU_VP
[1..7]
90 GSM_RESP_TPDU_SRQ BOOLEAN 1 GSM_RESP_TPDU_SRQ
OCTET-STRING
91 GSM_RESP_TPDU_RA 12 GSM_RESP_TPDU_RA
[2..12]
OCTET-STRING
92 GSM_RESP_TPDU_DT 7 GSM_RESP_TPDU_DT
[7]
93 GSM_RESP_TPDU_ST UINT8 3 GSM_RESP_TPDU_ST
94 GSM_RESP_TPDU_CT UINT8 3 GSM_RESP_TPDU_CT
95 GSM_RESP_TPDU_MN UINT8 3 GSM_RESP_TPDU_MN
96 GSM_RESP_TPDU_CDL UINT8 3 GSM_RESP_TPDU_CDL
97 GSM_RESP_TPDU_CD UINT8 3 GSM_RESP_TPDU_CD
More Messages to Send in
98 MAP_MMS BOOLEAN 1
MAP-MO-FWSM
Routing indicator of an SCCP destination
address. In case of a concatenated
99 SCCP_DEST_ADDR_RI SCCP-ADDR.RI 1 message, the value of the last segment
attempted to be delivered is provided,
see Table 3.16.
SSN of an SCCP destination address. In
SCCP- case of a concatenated message, the
100 SCCP_DEST_ADDR_SSN 3
ADDR.SSN value of the last segment attempted to be
delivered is provided, see Table 3.16.
PC of an SCCP destination address. In
case of a concatenated message, the
101 SCCP_DEST_ADDR_PC SCCP-ADDR.PC 10
value of the last segment attempted to be

Max
length
Nature of an address indicator (NAI) of
GT of an SCCP destination address. In
SCCP-
102 SCCP_DEST_ADDR_GT_NAI 1 case of concatenated message, the
ADDR.GT_NAI
value of last segment that was attempted
to be deliver is provided, see Table 3.16.
Numbering plan indicator of GT of an
SCCP destination address. In case of a
SCCP-
103 SCCP_DEST_ADDR_GT_NPI 2 concatenated message, the value of the
ADDR.GT_NPI
last segment attempted to be delivered is
provided, see Table 3.16.
GT of an SCCP destination address. In
104 SCCP_DEST_ADDR_GT_ADDR 20
ADDR.GT_ADDR value of the last segment attempted to be
Translation type of GT of an SCCP
destination address. In case of a
SCCP-
105 SCCP_DEST_ADDR_TT 3 concatenated message, the value of the
ADDR.GT_TT
Routing indicator of an SCCP originating
106 SCCP_ORIG_ADDR_RI SCCP-ADDR.RI 1
address, see Table 3.16.
SCCP- SSN of an SCCP originating address,
107 SCCP_ORIG_ADDR_SSN 3
ADDR.SSN see Table 3.16.
PC of an SCCP originating address, see
108 SCCP_ORIG_ADDR_PC SCCP-ADDR.PC 10
Table 3.16.
Nature of an address indicator of GT of
SCCP-
109 SCCP_ORIG_ADDR_GT_NAI 1 an SCCP originating address, see
ADDR.GT_NAI
Table 3.16.
SCCP-
110 SCCP_ORIG_ADDR_GT_NPI 2 SCCP originating address, see
ADDR.GT_NPI
Table 3.16.
SCCP- GT of an SCCP originating address, see
111 SCCP_ORIG_ADDR_GT_ADDR 20
ADDR.GT_ADDR Table 3.16.
SCCP- Translation type of GT of an SCCP
112 SCCP_ORIG_ADDR_TT 3
ADDR.GT_TT originating address, see Table 3.16.
113 NETWORK_PROFILE_ID UINT8 3 Specific routing profile
ISDN- Type of number of MSISDN-Alert in
114 ALERT_MSISDN_TON 1
ADDR.TON MAP-ALERT-SC, see Table 3.16.
Numbering plan indicator of
115 ALERT_MSISDN_NPI ISDN-ADDR.NPI 2 MSISDN-Alert in MAP-ALERT-SC, see
Table 3.16.
MSISDN-Alert in MAP-ALERT-SC, see
116 ALERT_MSISDN_ADDRESS UTF-STRING 512
Table 3.16.
ISDN- Type of number of an SC address in
117 ALERT_SC_ADDR_TON 1
ADDR.TON MAP-ALERT-SC, see Table 3.16.
Numbering plan indicator of an SC
118 ALERT_SC_ADDR_NPI ISDN-ADDR.NPI 2 address in MAP-ALERT-SC, see
Table 3.16.
SC address in MAP-ALERT-SC, see
119 ALERT_SC_ADDR_ADDRESS UTF-STRING 512
Table 3.16.

Max
length
Error code of a MAP operation described
120 MAP_ERROR_CODE UINT16 5
in Table 3.4.
Additional failure information described in
121 MAP_CAUSE_OF_FAILURE UINT16 5
Table 3.5.
Parameter indicating whether or not a
short message transfer should be
122 MT_PRIORITY_REQUEST UINT8 3 stopped if the originator SC address is
already contained in MWD (GSM
RP-PRI).
Parameter indicating whether TPDU is
123 MT_MSG_TYPE_INDICATOR UINT8 3 SMS Deliver or SMS Status Report
(GSM RP-MTI).
Bit field consisting of 64 bits written in the
124 RBDL_FLAGS_HEX STRING[0..16] 16
hexadecimal string format.
Parameter indicating whether a message
125 TCAP_SEGMENTED BOOLEAN 1
is segmented on TCAP.
It counts the number of requests for a
current incoming (pre-submission) or
126 SM_NUM_OF_ATTEMPTS UINT32 10
outgoing (pre-delivery) trigger for a
message.
Name of a matched keyword list, if the
message text matches any. The length of
127 MATCHED_LIST STRING -
the string depends on configuration
(deprecated).
Recommended-Decision as returned by
an external ADMI application in a
128 REC_DECISION_OUT UINT8 1
notification answer: 0 - Proceed, 1 -
Reject, 2 - Complete, 3 - Drop, 4 - Detect.
Bit field consisting of 64 bits, for detailed
129 INFORMATION_FLAGS UINT64 20
description see Table 3.13.
130 INFORMATION_FLAGS_EXT_1 UINT64 20 description see Table 3.14. This field
extends INFORMATION_FLAGS.
Reason for blocking a message, see
131 MSG_REJECT_REASON UINT64 20
Table 3.15.
Method used for blocking a message: 1 -
132 MSG_REJECT_METHOD UINT8 3
Reject, 2 - Drop, 3 - Discard.
MAP error code received in a response
133 SRISM_HLR_ERROR_CODE_ORIG UINT32 10 to an SRI-SM query about an originating
MSISDN number.
134 SRISM_HLR_ERROR_CODE UINT32 10 to an SRI-SM query about a recipient
MSISDN number.
Originator IMSI as received in
135 MAP_MO_IMSI STRING[16] 16
MAP-MO-FWSM
Routing indicator of an originating HLR
136 SCCP_ORIG_HLR_ADDR_RI SCCP-ADDR.RI 1
SCCP address, see Table 3.16.
SCCP- SSN of an originating HLR SCCP
137 SCCP_ORIG_HLR_ADDR_SSN 3
ADDR.SSN address, see Table 3.16.

Max
length
PC of an originating HLR SCCP address,
138 SCCP_ORIG_HLR_ADDR_PC SCCP-ADDR.PC 10
see Table 3.16.
Nature of an address indicator of GT of
SCCP-
139 SCCP_ORIG_HLR_ADDR_GT_NAI 1 an originating HLR SCCP address, see
ADDR.GT_NAI
Table 3.16.
SCCP-
140 SCCP_ORIG_HLR_ADDR_GT_NPI 2 originating HLR SCCP address, see
ADDR.GT_NPI
Table 3.16.
SCCP- GT of an originating HLR SCCP address,
141 SCCP_ORIG_HLR_ADDR_GT_ADDR 20
ADDR.GT_ADDR see Table 3.16.
SCCP- Translation type of GT of an originating
142 SCCP_ORIG_HLR_ADDR_TT 3
ADDR.GT_TT HLR SCCP address, see Table 3.16.
Type of number of an originating SC
ISDN-
143 A_SC_ADDRESS_TON 1 address as received in an incoming
ADDR.TON
message, see Table 3.16.
Numbering plan indicator of an
144 A_SC_ADDRESS_NPI ISDN-ADDR.NPI 2 originating SC address as received in an
incoming message, see Table 3.16.
Address of an originating SC address as
145 A_SC_ADDRESS_ADDRESS UTF-STRING 512 received in an incoming message, see
Table 3.16.
Routing indicator of an SCCP responding
address. In case of a concatenated
146 SCCP_RESPONDING_ADDR_RI SCCP-ADDR.RI 1 message, the value of the last segment
attempted to be delivered is provided,
see Table 3.16.
SSN of an SCCP responding address. In
147 SCCP_RESPONDING_ADDR_SSN 3
ADDR.SSN value of the last segment attempted to be
PC of an SCCP responding address. In
case of a concatenated message, the
148 SCCP_RESPONDING_ADDR_PC SCCP-ADDR.PC 10
value of the last segment attempted to be
Nature of an address indicator (NAI) of
GT of an SCCP responding address. In
SCCP-
149 SCCP_RESPONDING_ADDR_GT_NAI 1 case of concatenated message, the
ADDR.GT_NAI
value of last segment that was attempted
to be deliver is provided, see Table 3.16.
SCCP responding address. In case of a
SCCP-
150 SCCP_RESPONDING_ADDR_GT_NPI 2 concatenated message, the value of the
ADDR.GT_NPI
GT of an SCCP responding address. In
151 SCCP_RESPONDING_ADDR_GT_ADDR 20
ADDR.GT_ADDR value of the last segment attempted to be

Max
length
Translation type of GT of an SCCP
responding address. In case of a
SCCP-
152 SCCP_RESPONDING_ADDR_TT 3 concatenated message, the value of the
ADDR.GT_TT
Originator Location Area Identification,
153 A_LAI STRING[1..12] 12
see Section 2.7.35.
Inbound/outbound operation indicator,
154 MAP_OPER_ORIGIN UINT8 2
see Section 2.7.37.
HLR modification request in the ATM
155 HLR_MODIF_REQ UINT8 2
operation, see Section 2.7.38.
156 ODB UINT32 9 Operator determined barring data.
List of call barring features, see
157 CALL_BARRING_FEATURES UTF-STRING 512
Section 2.7.33.
Requested subscription information, see
158 REQ_SUBS_INFO STRING[1..8] 8
Section 2.7.39.
159 A_IMEI STRING[1..16] 16 ATI IMEI.
Produces an empty field in the record.
Can be used for omitting some
160 EMPTY_FIELD N/A N/A
information/field from SDR but preserving
the order/position of the rest of attributes.
3.1.3 SM SDR stream
The SM SDR stream is used for logging short messages. A generated SM SDR can contain fields listed in Table 3.3.
Important
The table lists all available attributes in a random order. The first column (#) denotes the order of an attribute in the table.
Whether a particular field appears in a produced SDR and on which position can be configured using the name of the
attribute in the second column.
Table 3.3: Possible parameters of SM SDR stream
Max
length
Possible values: PRE_SUBMIT,
POST_SUBMIT, PRE_DELIVERY,
1 SDR_RECORD_TYPE STRING 13 POST_DELIVERY, SM_NOTIFY,
SESS_REQ, SESS_START,
SESS_CHNG, SESS_TERM, EVENT
2 SDR_FORMAT STRING 2 “SM”
3 SDR_LOG_TIME UINT32 14 (UTC) Jan 1 1970) – the time of record
creation.

Max
length
OCTET-
4 MESSAGE_ID 16 Unique identifier of a message.
STRING[16]
This field carries the source network
5 ORIG_NETWORK_TYPE UINT8 1
type, see Table 3.17.
ISDN- Type of number of a source normalised
6 ORIG_ADDRESS_TON 1
ADDR.TON address, see Table 3.16.
Numbering plan indicator of a source
7 ORIG_ADDRESS_NPI ISDN-ADDR.NPI 2
normalised address, see Table 3.16.
Source normalised address, see
8 ORIG_ADDRESS_ADDRESS UTF-STRING 512
Table 3.16.
IMSI received in MAP-MO-FWSM or
IMSI returned by HLR as a result of an
9 MO_IMSI STRING[1..16] 16
originator validation. The latter takes
precedence if both values are available.
Routing indicator of a source SCCP
10 SCCP_ORIG_ADDR_RI SCCP-ADDR.RI 1
SCCP- SSN of a source SCCP address, see
11 SCCP_ORIG_ADDR_SSN 3
ADDR.SSN Table 3.16.
PC of a source SCCP address, see
12 SCCP_ORIG_ADDR_PC SCCP-ADDR.PC 10
Table 3.16.
SCCP- Nature of an address indicator of GT of a
13 SCCP_ORIG_ADDR_GT_NAI 1
ADDR.GT_NAI source SCCP address, see Table 3.16.
SCCP- Numbering plan indicator of GT of a
14 SCCP_ORIG_ADDR_GT_NPI 2
ADDR.GT_NPI source SCCP address, see Table 3.16.
SCCP- GT of a source SCCP address, see
15 SCCP_ORIG_ADDR_GT_ADDR 20
SCCP- Translation type of GT of a source SCCP
16 SCCP_ORIG_ADDR_TT 3
ADDR.GT_TT address, see Table 3.16.
17 ORIG_COS UINT32 10 Class of Service of the originator.
This field carries identification of a source
18 ORIG_APPL_ID STRING [1..32] 32
application or interface.
Type of number of a destination
ISDN- normalised address; when it is included
19 RECIP_ADDRESS_TON 1
ADDR.TON in a response, it has been changed by a
triggered component. See Table 3.16.
Numbering plan indicator of a destination
20 RECIP_ADDRESS_NPI ISDN-ADDR.NPI 2
normalised address, see Table 3.16.
Destination normalised address, see
21 RECIP_ADDRESS_ADDRESS UTF-STRING 512
Table 3.16.
This field carries identification of a
22 RECIP_APPL_ID STRING [1..32] 32
destination application or interface.
This field carries a recipient IMSI
23 MT_IMSI STRING[1..16] 16
address.
Routing indicator of a destination SCCP
24 SCCP_DEST_ADDR_RI SCCP-ADDR.RI 1
SCCP- SSN of a destination SCCP address, see
25 SCCP_DEST_ADDR_SSN 3
PC of a destination SCCP address, see
26 SCCP_DEST_ADDR_PC SCCP-ADDR.PC 10
Table 3.16.

Max
length
Nature of an address indicator of a
SCCP-
27 SCCP_DEST_ADDR_GT_NAI 1 destination SCCP address, see
ADDR.GT_NAI
Table 3.16.
Numbering plan indicator of GT of a
SCCP-
28 SCCP_DEST_ADDR_GT_NPI 2 destination SCCP address, see
ADDR.GT_NPI
Table 3.16.
SCCP- GT of a destination SCCP address, see
29 SCCP_DEST_ADDR_GT_ADDR 20
SCCP- Translation type of GT of a destination
30 SCCP_DEST_ADDR_TT 3
ADDR.GT_TT SCCP address, see Table 3.16.
31 RECIP_COS UINT32 10 Class of Service of the recipient.
Store and Forward, Transactional or
Single Shot mode; when it is included in
32 MESSAGE_MODE UINT8 2 a response, it has been changed by a
triggered component. For additional
information refer to Table 3.6.
33 MSG_ORIG_SUBM_TIME UINT64 14 (UTC) Jan 1 1970) - the original
submission time.
(UTC) Jan 1 1970) - the expiration time;
34 MSG_EXP_TIME UINT64 14
when it is included in a response, it was
changed by a triggered component.
(UTC) Jan 1 1970) - the preferred
35 MSG_PREF_DELIVERY_TIME UINT64 14 delivery time of a message; when it is
included in a response, it has been
36 MSG_LAST_DELIVERY_TIME UINT64 14 (UTC) Jan 1 1970) - the time of the last
delivery attempt.
Message ID of a related (parent)
OCTET-
37 PARENT_MSG_ID 16 message, e.g. for a notification or an SM
STRING[1..16]
copy.
SM, delivery receipt, intermediate
38 MSG_TYPE UINT8 1 delivery notification described in
Table 3.7.
CONCAT- Number of segments in a concatenated
39 CONCAT_INFO_MAX_SEGMENTS 3
INFO.MAXSEG message, see Table 3.16.
Sequence number of the current
CONCAT-
40 CONCAT_INFO_CURRENT_SEGMENT 3 segment of a concatenated message,
INFO.CURSEG
see Table 3.16.
CONCAT- Concatenated message reference
41 CONCAT_INFO_REFERENCE 5
INFO.REF number, see Table 3.16.
Message encoding, i.e. the encoding of
PAYLOAD-
42 PAYLOAD_INFO_ENCODING 3 content of the MSG_PAYLOAD billing field.
INFO.ENC
See Table 3.8 and Table 3.16.
PAYLOAD-
43 PAYLOAD_INFO_SIZE 5 Size in bytes, see Table 3.16.
INFO.SIZE

Max
length
PAYLOAD-
44 PAYLOAD_INFO_NUM_CHARS 5 Number of characters, see Table 3.16.
INFO.NUMCH
PAYLOAD- National language single shift table, see
45 PAYLOAD_INFO_SINGLE_SHIFT_TAB 3
INFO.SSTAB Table 3.9 and Table 3.16.
PAYLOAD- National language locking shift table, see
46 PAYLOAD_INFO_LOCKING_SHIFT_TAB 3
INFO.LSTAB Table 3.10 and Table 3.16.
Message payload without UDH. The
encoding of the MSG_PAYLOAD billing
field is specified by the
OCTET-
47 MSG_PAYLOAD 4096 PAYLOAD_INFO_ENCODING billing field.
STRING[1..4096]
When the MSG_PAYLOAD billing field is
included in a response, it has been
Message text with removed UDH
OCTET-STRING converted to UTF8; when it is included in
48 SDR_MSG_TEXT_UTF8 4096
[1..4096] a response, it has been changed by a
triggered component.
This field specifies priority of an SM; an
49 MSG_PRIORITY UINT8 3 SM with a higher priority should be
delivered before SMs with lower priorities.
This field specifies subscriptions for a
delivery receipt: Without intermediate
notification: 0 - No delivery receipt, 1 -
Delivery receipt requested, 2 - Delivery
receipt requested in case of failure. 4 -
50 MSG_NOTIF_REQUIRED UINT16 5 Delivery requested in case of success
only. With intermediate notification: 16 -
No delivery receipt, 17 - Delivery receipt
requested, 18 - Delivery receipt
requested in case of failure. 20 - Delivery
receipt requested in case of success.
51 MSG_PROTOCOL_ID UINT8 3 TP-PID – see [3GPP_23.040]
This field specifies the error code carried
52 MSG_ERROR_CODE UINT16 5
with a message, see Table 3.11.
This field contains a value of field
TP-DCS as defined in [3GPP_23.040].
When a message is AO, this field
53 GSM_DATA_CODING_SCHEME UINT8 3
contains a value of field data_coding
as defined in SMPP protocol
specification.
OCTET-
54 GSM_UDH 160 UDH of a message.
STRING[1..160]
Detailed cause of a failure of a related
55 MAP_CAUSE_OF_FAILURE UINT16 5
MAP operation, see Table 3.5.
Bit field consisting of 64 bits written in the
56 RBDL_FLAGS_HEX STRING[0..16] 16
hex string format.
Parameter indicating whether a message
57 TCAP_SEGMENTED BOOLEAN 1
is segmented on TCAP.
ISDN- Type of number of a source untranslated
58 ORIG_UNTRANSL_ADDRESS_TON 1

Max
length
Numbering plan indicator of a source
59 ORIG_UNTRANSL_ADDRESS_NPI ISDN-ADDR.NPI 2
untranslated address, see Table 3.16.
Source untranslated address, see
60 ORIG_UNTRANSL_ADDRESS_ADDRESS UTF-STRING 512
Table 3.16.
ISDN- Type of number of an untranslated
61 RECIP_UNTRANSL_ADDRESS_TON 1
ADDR.TON destination address, see Table 3.16.
Numbering plan indicator of an
62 RECIP_UNTRANSL_ADDRESS_NPI ISDN-ADDR.NPI 2 untranslated destination address, see
Table 3.16.
Untranslated destination address, see
63 RECIP_UNTRANSL_ADDRESS_ADDRESSUTF-STRING 512
Table 3.16.
Type of number of the destination SC
ISDN-
64 MO_SC_ADDR_TON 1 address in case of an MO message, see
ADDR.TON
Table 3.16.
Numbering plan indicator of the
65 MO_SC_ADDR_NPI ISDN-ADDR.NPI 2 destination SC address in case of an MO
Destination SC address in case of an MO
66 MO_SC_ADDR_ADDRESS UTF-STRING 512
Type of number of the destination SC
ISDN-
67 MT_SC_ADDR_TON 1 address in case of an MT message, see
ADDR.TON
Table 3.16.
Numbering plan indicator of the source
68 MT_SC_ADDR_NPI ISDN-ADDR.NPI 2 SC address in case of an MT message,
see Table 3.16.
Source SC address in case of an MT
69 MT_SC_ADDR_ADDRESS UTF-STRING 512
70 MAP_MMS BOOLEAN 1 More Messages to Send flag
GSM TP-LOOP-PREVENTION
71 MSG_LOOP_PREVENTION BOOLEAN 1
parameter
72 MSG_REPLY_PATH BOOLEAN 1 GSM TP-REPLY-PATH parameter
GSM TP-REJECT-DUPLICATES
73 MSG_REJECT_DUPLICATES BOOLEAN 1
parameter
TP-SCTS – see [3GPP_23.040]. The
OCTET- time zone is set based on platform
74 MSG_SC_TIMESTAMP 7
STRING[7] settings. Command “date +%Z” shows a
current time zone setting.
TP-MR – see [3GPP_23.040] or SMPP
75 MSG_MESSAGE_REFERENCE UINT16 5 reference number
(user_message_reference field)
OCTET- Transaction ID used by external billing
76 BILLING_TRANSACTION_ID 160
STRING[1..160] entities
OCTET-
77 SMPP_BILLING_ID 20 SMPP billing ID
STRING[1..20]
Status of a message described in
78 MSG_STATUS UINT8 2
Table 3.12.
Type of number of an SC address of the
ISDN-
79 SRISM_NETW_NODE_ADDR_ORIG_TON 1 originator retrieved by SRI-SM, see
ADDR.TON
Table 3.16.

Max
length
80 SRISM_NETW_NODE_ADDR_ORIG_NPI ISDN-ADDR.NPI 2 address of the originator retrieved by
SRI-SM, see Table 3.16.
SRISM_NETW_NODE_ADDR_ SC address of the originator retrieved by
81 UTF-STRING 512
ORIG_ADDRESS SRI-SM, see Table 3.16.
Type of number of an SGSN address of
ISDN-
82 SRISM_SGSN_NODE_ADDR_ORIG_TON 1 the originator retrieved by SRI-SM, see
ADDR.TON
Table 3.16.
83 SRISM_SGSN_NODE_ADDR_ORIG_NPI ISDN-ADDR.NPI 2 address of the originator retrieved by
SRISM_SGSN_NODE_ADDR_ SGSN address of the originator retrieved
84 UTF-STRING 512
ORIG_ADDRESS by SRI-SM, see Table 3.16.
Type of number of an SC address of the
ISDN-
85 SRISM_NETW_NODE_ADDR_RECIP_TON 1 recipient retrieved by SRI-SM, see
ADDR.TON
Table 3.16.
86 SRISM_NETW_NODE_ADDR_RECIP_NPI ISDN-ADDR.NPI 2 address of the recipient retrieved by
SRISM_NETW_NODE_ADDR_ SC address of the recipient retrieved by
87 UTF-STRING 512
RECIP_ADDRESS SRI-SM, see Table 3.16.
Type of number of an SGSN address of
ISDN-
88 SRISM_SGSN_NODE_ADDR_RECIP_TON 1 the recipient retrieved by SRI-SM, see
ADDR.TON
Table 3.16.
89 SRISM_SGSN_NODE_ADDR_RECIP_NPI ISDN-ADDR.NPI 2 address of the recipient retrieved by
SRISM_SGSN_NODE_ADDR_ SGSN address of the recipient retrieved
90 UTF-STRING 512
RECIP_ADDRESS by SRI-SM, see Table 3.16.
It counts the number of requests for a
current incoming (pre-submission) or
outgoing (pre-delivery) trigger for a
message. Deprecated - the
91 ATTEMPT_COUNTER UINT32 10 SM_NUM_OF_ATTEMPTS field is used
instead. For backward compatibility the
ATTEMPT_COUNTER field should be
replaced by SM_NUM_OF_ATTEMPTS
in the billing stream.)
Name of the matched keyword list, if the
message text matched any. The length of
92 MATCHED_LIST STRING -
the string depends on configuration.
Deprecated.
DEPRECATED. Recommended Decision
as returned by an external application in
93 REC_DECISION_OUT UINT8 1
Notification-Answer: 0 - Proceed, 1 -
Reject, 2 - Complete, 3 - Drop, 4 - Detect.
Error code of a MAP operation described
94 MAP_ERROR_CODE UINT16 5
in Table 3.4.
95 INFORMATION_FLAGS UINT64 20
description see Table 3.13.

Max
length
96 INFORMATION_FLAGS_EXT_1 UINT64 20 description see Table 3.14. This field
extends INFORMATION_FLAGS.
Reason for blocking a message, see
97 MSG_REJECT_REASON UINT64 20
Table 3.15.
Method used for blocking a message: 1 -
98 MSG_REJECT_METHOD UINT8 3
Reject 2 - Drop 3 - Discard.
99 SRISM_HLR_ERROR_CODE_ORIG UINT32 10 to an SRI-SM query about an originating
MSISDN number.
100 SRISM_HLR_ERROR_CODE UINT32 10 to an SRI-SM query about a recipient
MSISDN number.
Type of number of origAddress, this
ISDN-
101 ORIG_OUT_ADDRESS_TON 1 can be changed by third-party
ADDR.TON
applications, see Table 3.16.
Numbering plan indicator of
102 ORIG_OUT_ADDRESS_NPI ISDN-ADDR.NPI 2 origAddress, this can be changed by
third-party applications, see Table 3.16.
origAddress, this can be changed by
103 ORIG_OUT_ADDRESS_ADDRESS UTF-STRING 512
third-party applications, see Table 3.16.
Type of number of recipAddress
ISDN-
104 RECIP_UNCHANGED_ADDRESS_TON 1 before it is changed by third-party
ADDR.TON
Numbering plan indicator of Type of
number of recipAddress before it is
105 RECIP_UNCHANGED_ADDRESS_NPI ISDN-ADDR.NPI 2
changed by third-party applications, see
Table 3.16.
Type of number of recipAddress
106 RECIP_UNCHANGED_ADDRESS_ADDRESS
UTF-STRING 512 before it is changed by third-party
It indicates the destination network type,
107 DEST_NET_TYPE UINT8 1
see Table 3.17.
It specifies the type of operation: 0x01 –
108 OPER_TYPE UINT8 1
MO, 0x02 – MT.
Number of seconds in UTC for a
message when it reached the done state
(State when a message accepted by the
109 SM_DONE_DATE UINT64 20 MCO for further processing is completed
and removed from the system. The
message can be delivered or
undelivered).
110 SM_NUM_OF_ATTEMPTS UINT16 5 Number of delivery attempts
111 SM_MAPPED_NETWORK_ERROR INT32 10 Internal mapped network error
112 SM_SERVICE_TYPE STRING[0..10] 10 SMPP service type
113 SERVICE_TYPE_ID_OUT UINT16 5 Service type ID, e.g. for AO messages.
Originator IMSI as received in
114 MAP_MO_IMSI STRING[1..16] 16
MAP-MO-FWSM.

Max
length
This parameter has value
ORIG_IS_PREPAID if the originator is
prepaid, ORIG_IS_NOT_CHECKED if
115 CHARGING_ORIG_PREPAID STRING 19
the originator was not checked and
ORIG_IS_POSTPAID for postpaid
originators.
RECIP_IS_PREPAID if the recipient is
prepaid, RECIP_IS_NOT_CHECKED if
116 CHARGING_RECIP_PREPAID STRING 20
the recipient was not checked and
RECIP_IS_POSTPAID for postpaid
recipients.
CHARGED_PARTY_ORIG if the charged
party is the originator and
117 CHARGING_CHARGED_PARTY STRING 19
CHARGED_PARTY_RECIP if the
charged party is the recipient of the
message.
This parameter is a sequence of
numbers 1 or 0. The count of numbers
corresponds to the number of charging
requests sent for the whole message
flow. Each number identifies whether an
operation was successful (1) or not (0).
118 CHARGING_OPER_RESULT STRING 4 The first number from left is a result of
the first operation. The following is an
example, where the first operation
(DEBIT) was successful and the second
(CREDIT) not.
<separator>"10"<separator>
It contains a string of operations

performed in the message flow. It does
not contain an exact name of the
operation unless it is specified in a
119 CHARGING_OPER_TYPE STRING 43
prepaid plug-in.
<separator>"Operation1 ←-
Operation2"<separator>
Fingerprint of the message. It can be
120 AFL_KEY STRING[32] 32
used only in Antiflood SDR records.
Source application port of Application
121 UDH_SRC_PORT UINT16 5
Port Addressing (APA) IE of UDH.
Destination application port of (APA) IE of
122 UDH_DST_PORT UINT16 5
UDH.
A mask indicating the set of UDH profiles
123 UDH_PROFILE_MASK UINT32 10
matching a message.
A mask indicating the set of UDH profiles
124 UDH_PROFILE_MASK_SEG UINT32 10
matching a segment of a message.

Max
length
Recommended decision received from
125 ADMI_DECISION UINT8 1 ADMI. 0 = Proceed, 1 = Reject, 2 =
Complete, 3 = Drop, 4 = Detect
Reason for the recommended decision
126 ADMI_DECISION_REASON UINT32 10
from ADMI.
Recommended decision received from
127 CC_DECISION UINT8 1 content control: 0 = Proceed, 1 = Reject,
2 = Complete, 3 = Drop, 4 = Detect
Reason for the recommended decision
128 CC_DECISION_REASON UINT32 10
from content control.
Routing indicator of a source HLR SCCP
129 SCCP_ORIG_HLR_ADDR_RI SCCP-ADDR.RI 1
SCCP- SSN of a source HLR SCCP address,
130 SCCP_ORIG_HLR_ADDR_SSN 3
ADDR.SSN see Table 3.16.
PC of a source HLR SCCP address, see
131 SCCP_ORIG_HLR_ADDR_PC SCCP-ADDR.PC 10
Table 3.16.
Nature of an address indicator of GT of a
SCCP-
132 SCCP_ORIG_HLR_ADDR_GT_NAI 1 source HLR SCCP address, see
ADDR.GT_NAI
Table 3.16.
SCCP-
133 SCCP_ORIG_HLR_ADDR_GT_NPI 2 source HLR SCCP address, see
ADDR.GT_NPI
Table 3.16.
SCCP- GT of a source HLR SCCP address, see
134 SCCP_ORIG_HLR_ADDR_GT_ADDR 20
SCCP- Translation type of GT of a source HLR
135 SCCP_ORIG_HLR_ADDR_TT 3
UTF-
136 IM_EVENT_TYPE 64 SIP method
STRING[1..64]
137 SESSION_TYPE UINT8 1 SIP session type
UTF-
138 MSG_CONTENT_TYPE 64 SIP message content type
STRING[1..64]
139 IMDN_TYPE UINT8 1 IMDN type
UTF-
140 USER_SESSION_ID 255 SIP user session ID
STRING[1..255]
UTF-
141 OUTGOING_SESSION_ID 255 SIP outgoing session ID
STRING[1..255]
142 SESSION_IDENTIFIER UTF-STRING[16] 16 SIP session identifier
143 TRAFFIC_CATEGORY UINT8 1 Traffic category
144 SIP_RESPONSE UINT16 2 SIP response
UTF-
145 USER_STATUS 255 SIP user status
STRING[1..255]
146 SDP_PROTOCOLS UINT8 1 SDP protocols
147 SESSION_CHANGE_TYPE UINT8 3 Type of session change
Type of number of a source SC address
ISDN-
148 A_SC_ADDRESS_TON 1 as received in an incoming message, see
ADDR.TON
Table 3.16.
Numbering plan indicator of a source SC
149 A_SC_ADDRESS_NPI ISDN-ADDR.NPI 2 address as received in an incoming

Max
length
Address of a source SC address as
150 A_SC_ADDRESS_ADDRESS UTF-STRING 512 received in an incoming message, see
Table 3.16.
Domain specific information (message
ID) e.g. for generating correct
151 ORIG_DOMAIN_MSG_ID STRING 65
notifications (IMDN,
SMS-STATUS-REPORT).
152 A_DOMAIN UINT8 1 MVNO id of originating subscriber
153 B_DOMAIN UINT8 1 MVNO id of recipient subscriber
154 S_DOMAIN UINT8 1 Source application MVNO id
155 D_DOMAIN UINT8 1 Destination application MVNO id
64 bit Class of service of originating
156 A_COS UINT64 8
subscriber
64 bit Class of service of recipient
157 B_COS UINT64 8
subscriber
64 bit Class of service of source
158 S_COS UINT64 8
application
64 bit Class of service of destination
159 D_COS UINT64 8
application
Message Template ID(equals to Profile
160 MSG_TEMPLATE_ID UINT16 5
ID of Message Generation AF)
64 bit segment RBDL flags written in the
161 RBDL_FLAGS_SEG_HEX STRING[0..16] 16
hex string format.
Information flags bit field of a segment,
162 INFORMATION_FLAGS_SEG UINT64 8
for detailed description see Table 3.13.
40 Byte customer specific binary data
163 EXT_DATA STRING 40
written in the hex string format.
40 Byte customer specific binary data of
164 EXT_DATA_SEG STRING 40 a segment written in the hex string
format.
Contains sequence of quadruplet which
indicates what profiles were applied for
165 STAT_DATA STRING - the message. Following format is
supported: <feature id>;<profile
id><1,0><1,0>|...
Routing indicator of a responding SCCP
166 SCCP_RESPONDING_ADDR_RI SCCP-ADDR.RI 1
SCCP- SSN of a responding SCCP address, see
167 SCCP_RESPONDING_ADDR_SSN 3
PC of a responding SCCP address, see
168 SCCP_RESPONDING_ADDR_PC SCCP-ADDR.PC 10
Table 3.16.
Nature of an address indicator of GT of a
SCCP-
169 SCCP_RESPONDING_ADDR_GT_NAI 1 responding SCCP address, see
ADDR.GT_NAI
Table 3.16.
SCCP-
170 SCCP_RESPONDING_ADDR_GT_NPI 2 responding SCCP address, see
ADDR.GT_NPI
Table 3.16.
SCCP- GT of a responding SCCP address, see
171 SCCP_RESPONDING_ADDR_GT_ADDR 20

Max
length
SCCP- Translation type of GT of a responding
172 SCCP_RESPONDING_ADDR_TT 3
ISDN- Type of number of source (IP/network/uri)
173 S_ADDR_TON 1
Numbering plan indicator of source
174 S_ADDR_NPI ISDN-ADDR.NPI 2
(IP/network/uri) address, see Table 3.16.
Source (IP/network/uri) address, see
175 S_ADDR_ADDR UTF-STRING 512
Table 3.16.
ISDN- Type of number of destination
176 D_ADDR_TON 1
ADDR.TON (IP/network) address, see Table 3.16.
Numbering plan indicator of destination
177 D_ADDR_NPI ISDN-ADDR.NPI 2
(IP/network) address, see Table 3.16.
Destination (IP/network) address, see
178 D_ADDR_ADDR UTF-STRING 512
Table 3.16.
STRING
179 S_CONS STRING Source (LA) consolidation field.
[1..16]
STRING
180 D_CONS STRING Destination (LA) consolidation field.
[1..16]
A list of RBDL rule names of rules
STRING
181 TRACK_DATA STRING applied to the message. Only rules
[1..4096]
marked for SDR tracking are recorded.
182 TELESERVICE UINT16 5 Teleservice identifier (ANSI MAP).
UTF-
183 A_USER_AGENT 255 Originator user agent header field.
STRING[1.255]
UTF-
184 B_USER_AGENT 255 Recipient user agent header field.
STRING[1.255]
Number uniquely identifying
185 A_LASN UINT32 6
originating/source LA.
Number uniquely identifying
186 B_LASN UINT32 6
recipient/destination LA.
187 ADT_PROFILE UINT16 5 Source Address translation profile ID.
Importance of a message. Messages
with a higher importance are queued for
188 IMPORTANCE UINT8 2
delivery before messages with a lower
importance.
ISDN- Type of number of call-back number, see
189 CBN_TON 1
ADDR.TON Table 3.16.
Numbering plan indicator call-back
190 CBN_NPI ISDN-ADDR.NPI 2
number, see Table 3.16.
Call-back number address digits, see
191 CBN_ADDRESS UTF-STRING 512
Table 3.16.
Mobile identification number related to
192 A_MIN STRING[1..10] 10
the originator.
Mobile identification number related to
193 B_MIN STRING[1..10] 10
the recipient.
Electronic serial number related to the
194 B_ESN UINT32 10
recipient.
195 ODB UINT32 10 Operator determined barring data.

Max
length
List of call barring features, see
196 CALL_BARRING_FEATURES UTF-STRING 512
Section 2.7.33.
197 IR_PROFILE UINT8 3 Intelligent retry profile ID.
Constructed IMSI address (MT
198 F_IMSI STRING[1..16] 16 correlation ID) used for MT-FW-SM
interception.
199 A_IMEI STRING[1..16] 16 Originator IMEI.
200 B_IMEI STRING[1..16] 16 Recipient IMEI.
Originator Location Area Identification,
201 A_LAI STRING[1..12] 12
see Section 2.7.35.
Base cause of an operation failure, see
202 BASE_ERROR UINT64 8
Section 2.7.40.
Produces an empty field in the record.
Can be used for omitting some
203 EMPTY_FIELD N/A N/A
information/field from SDR but preserving
the order/position of the rest of attributes.
3.1.4 Parameter values
Billing records contain some fields of an enumeration type. The following tables list all these parameters and show all available
values of each field.
3.1.4.1 Values of MAP parameters
Table 3.4: MAP_ERROR_CODE
Code Value Description

0x0001 unknownSubscriber SRI-SM
0x0005 unidentifiedSubscriber
0x0006 absentSubscriberSM SRI-SM, MT-FWSM
0x0009 illegalSubscriber MT-FWSM
0x000A bearerServiceNotProvisioned
0x000B teleserviceNotProvisioned SRI-SM
0x000C illegalEquipment MT-FWSM
0x000D callBarred SRI-SM
0x0010 illegalSsOperation
0x0011 ssErrorStatus
0x0012 ssNotAvailable
0x0013 ssSubscriptionViolation
0x0014 ssIncompatibility
0x0015 facilityNotSupported SRI-SM, MT-FWSM, MO-FWSM
0x001B absentSubscriber SRI-SM, MT-FWSM
0x001F subscriberBusyForMT-SMS MT-FWSM
0x0020 sm-DeliveryFailure MT-FWSM, MO-FWSM
0x0022 systemFailure SRI-SM, MT-FWSM, MO-FWSM, ALERT-SC
0x0023 dataMissing SRI-SM, MT-FWSM, ALERT-SC


0x0024 unexpectedDataValue SRI-SM, MT-FWSM, MO-FWSM, ALERT-SC
0x003C atsiNotAllowed
0x003D atmNotAllowed
0x003E informationNotAvailable
0x0401 addressTransFail The SMS Destination Address is invalid.
SMS Destination Address is valid but not
0x0402 addressVacant
currently allocated to an SMS terminal.
Broadcast periodicity failure in MSC. Requested
0x0403 bcsPeriodicityFailMsc broadcast periodicity cannot be handled by
MSC.
A required terminal resource is not available to
0x0404 destResourceShortage process this message. SMS notification is not
pending.
The destination MS-based SME is SMS
0x0405 destBusy
capable, but is currently engaged in a call.
The MS-based SME is no longer at the
0x0406 destNoLongerAtThisAddr temporary SMS routing address. SMS
notification is not pending.
Delivery is not currently possible, but SMS
0x0407 destOutOfService
notification is pending.
The size of a parameter or field is not what is
0x0408 encodingProblem
expected.
The SMSTeleserviceIdentifier is not known, is
0x0409 invalidTeleserviceId not supported or is not authorized by an
addressed functional entity.
An optional parameter that is required for a
0x040A missingExpectedParam
particular function.
A parameter is missing that is mandatory for a
0x040B missingMandatoryParam
particular message.
A network node failed, a link failed or a required
0x040C networkFailure
operation failed.
Network transmission failed due to lack of a
0x040D networkResourceShortage
network resource shortage or link capacity.
The destination SME does not acknowledge
0x040E noAcknowledgement
receipt of the SMS delivery.
The addressed MS-based SME is known, but it
0x040F noPageResponse does not respond to a page. SMS Notification is
not pending.
0x0410 otherGeneralProblems Other general problems.
0x0411 otherNetworkProblem Other network problem.
0x0412 otherRadioInterfaceProb Other radio interface problem.
Other terminal problem. SMS notification is not
0x0413 otherTerminalProblem
pending.
The MS for an MS-based SME is operating in a
0x0414 radioInterfaceIncomp
mode that does not support SMS at this time.
There is no channel available or there is radio
0x0415 radioInterfaceShortage
congestion at this time.
The service is not supported by an addressed
0x0416 serviceNotSupported
functional entity.


The originating MSID is not recognized, the
0x0417 serviceOriginationDenied originating address is not allowed for the
originating MS.
The destination is not authorized to receive this
0x0418 serviceTerminationDenied
service message, the MC refused the message.
An OTASP or OTAPA session does not currently
0x0419 sessionNotActive
exist for the MS.
0x041A smsDelivOnPagingNotSupp SMS delivery on paging channel not supported.
0x041B smsDelivPostponed
The originating supplementary service is not
0x041C supplementServiceSupported
known or supported.
A known parameter has a known, but
0x041D unexpectedParameterValue
unexpected value.
A known parameter has a unknown or
0x041E unrecognizedParameterValue
unsupported value.
0x041F unsuppBsCapability Base Station does not support this service.
The intersystem network interface required for
0x0420 unsuppNetworkInterface the delivery of the received message is not
supported.
The User Data size is too large for access
0x0421 userDataSizeError
technology, transport network, or call mode.
The request cannot be honored, or the MS is
0x0422 smsAccdenDenied
unknown.
The addressed MS is known, but is currently
0x0423 smsAccdenPostponed
unreachable.
0x0424 smsAccdenUnavailable
unavailable.
0x0425 smsAccdenInvalid The SMS TeleserviceID is invalid.
0x0426 ansiTcapUnknownError Unknown TCAP error.
0x0427 ansiTcapRetErrUnrecMin Unrecognized MIN.
0x0428 ansiTcapRetErrUnrecEsn Unrecognized ESN.
0x0429 ansiTcapRetErrIdHlrMism ID/HLR mismatch.
0x042A ansiTcapRetErrOperSeqProblem Operation sequence problem.
0x042B ansiTcapRetErrResShort Resource shortage.
0x042C ansiTcapRetErrOperNotSup Operation not supported.
0x042D ansiTcapRetErrTrunkUnavail Trunk unavailable.
0x042E ansiTcapRetErrParamErr Parameter error.
0x042F ansiTcapRetErrSysFail System failure.
0x0430 ansiTcapRetErrUnrecParamVal Unrecognized parameter value.
0x0431 ansiTcapRetErrFeatInact Feature inactive.
0x0432 ansiTcapRetErrMissParam Missing parameter.
0x0433 ansiTcapRetErrUnrecImsiTmsi Unrecognized IMSI/TMSI.
0x0434 ansiTcapRetErrTmsiVlrMism TMSI/VLR mismatch.
0x0435 ansiTcapRejGenUnrecCompType General problem unrecognized component type.
0x0436 ansiTcapRejGenIncorComp General problem incorrect component portion.
0x0437 ansiTcapRejGenBadStructComp General problem incorrect component portion.
0x0438 ansiTcapRejGenIncorCompCod General problem incorrect component coding.


0x0439 ansiTcapRejInvDupInvId Invoke problem duplicate invocation.
0x043A ansiTcapRejInvUnrecOp Invoke problem unrecognized operation.
0x043B ansiTcapRejInvIncorParam Invoke problem incorrect parameter.
0x043C ansiTcapRejInvUnrecCorId Invoke problem unrecognized correlation id.
Return result problem unrecognized correlation
0x043D ansiTcapRejRrUnrecCorId
id.
0x043E ansiTcapRejRrUnexpRetres Return result problem unexpected return result.
0x043F ansiTcapRejRrIncorParam Return result problem incorrect parameter.
Return error problem unrecognized correlation
0x0440 ansiTcapRejReUnrecCorId
id.
0x0441 ansiTcapRejReUnexpReterr Return error problem unexpected return error.
0x0442 ansiTcapRejReUnrecError Return error problem unrecognized error.
0x0443 ansiTcapRejReUnexpError Return error problem unexpected error.
0x0444 ansiTcapRejReIncorParam Return error problem incorrect parameter.
0x0445 ansiTcapRejTpUnrecPkgType
package type.
0x0446 ansiTcapRejTpIncorTp
transaction portion.
Transaction portion problem badly structured
0x0447 ansiTcapRejTpBadStructTp
0x0448 ansiTcapRejTpUnrecTransid
transaction id.
0x0449 ansiTcapRejTpPermReleasPb
release problem.
0x044A ansiTcapRejTpResourUnavail
unavailable.
0x044B ansiTcapAbort TCAP abort.
All; covers errors and statuses other than
0x1000 ss7Error
MAP-U, i.e. SCCP, TCAP, MAP-P.
SIP error response. Field
0x6000 sipError MAP_CAUSE_OF_FAILURE contains a specific
SIP response code masked with 0x6000.
Table 3.5: MAP_CAUSE_OF_FAILURE
Code Name Description

0x0001 mapError Unknown or unsupported MAP error.
0x0002 mapSuccessfullyDelivered A MAP message was successfully delivered.
0x0003 mapSystemFailure System failure.
0x0004 mapSystemFailurePlmn System failure with network resource PLMN.
0x0005 mapSystemFailureHlr System failure with network resource HLR.
0x0006 mapSystemFailureVlr System failure with network resource VLR.
0x0007 mapSystemFailurePvlr System failure with network resource PVLR.
System failure with network resource controlling
0x0008 mapSystemFailureCmsc
MSC.
0x0009 mapSystemFailureVmsc System failure with network resource VMSC.


0x000A mapSystemFailureEir System failure with network resource EIR.
0x000B mapSystemFailureRss System failure with network resource RSS.
0x000C mapDataMissing Data missing.
0x000D mapUnexpectedDataValue Unexpected data value.
0x000E mapFacilityNotSupported The facility is not supported.
0x000F mapUnknownSubscriber Unknown subscriber.
Unknown subscriber with diagnostic IMSI
0x0010 mapUnknownSubscriberImsiUnknown
unknown.
Unknown subscriber with diagnostic GPRS
0x0011 mapUnknownSubscriberGprsSubUnknown
subscription unknown.
0x0012 mapUnidentifiedSubscriber Unidentified subscriber.
Illegal subscriber; authentication on a mobile
0x0013 mapIllegalSubscriber
station failed.
0x0014 mapIllegalEquipment Illegal equipment; the IMEI check failed.
0x0015 mapTeleserviceNotProvisioned Teleservice is not provisioned.
0x0016 mapAbsentSubscriber Absent subscriber.
0x0017 mapCallBarred Call barred.
0x0018 mapCallBarredServiceActive Call barred with the cause barring service active.
0x0019 mapCallBarredOperBarring Call barred with cause operator barring.
Call barred with an unauthorised message
0x001A mapCallBarredUnauthMsgOrig
originator.
0x001B mapCallBarredUnauthMsgOrigServiceActive
originator and cause barring service active.
0x001C mapCallBarredUnauthMsgOrigOperBarring
originator and cause operator barring.
0x001D mapSubscriberBusy The subscriber is busy for MT-SM.
The subscriber is busy for MT SMS and the
0x001E mapSubscriberBusyGprsSuspend
GPRS connection is suspended.
0x001F mapDeliveryFailure SM delivery failure.
SM delivery failure when memory capacity is
0x0020 mapDeliveryFailureMemCapExceed
exceeded.
SM delivery failure with an equipment protocol
0x0021 mapDeliveryFailureEquipErr
error.
SM delivery failure with equipment not SM
0x0022 mapDeliveryFailureNotSmEquip
equipped.
0x0023 mapDeliveryFailureUnknownSc SM delivery failure with an unknown SC.
0x0024 mapDeliveryFailureScCongest SM delivery failure with SC congestion.
0x0025 mapDeliveryFailureInvalidSmeAddr SM delivery failure with an invalid SME address.
SM delivery failure with subscriber is no service
0x0026 mapDeliveryFailureNoScSubscriber
centre subscriber.
0x0027 mapMsgWaitListFull The message waiting list is full.
0x0028 mapAbsentSubscriberSm Absent subscriber for SM.
Absent subscriber for SM with diagnostic no
0x0029 mapAbsentSubscriberSmNoPageMsc
paging response for MSC.
Absent subscriber for SM with diagnostic IMSI
0x002A mapAbsentSubscriberSmImsiDetach
detached.
Absent subscriber for SM with diagnostic
0x002B mapAbsentSubscriberSmRoamRestrict
roaming restriction.


0x002C mapAbsentSubscriberSmDeregNonGprs
deregistered in HLR for non-GPRS.
Absent subscriber for SM with diagnostic MS
0x002D mapAbsentSubscriberSmPurgedNonGprs
purged for non-GPRS.
0x002E mapAbsentSubscriberSmNoPageSgsn
paging response for SGSN.
Absent subscriber for SM with diagnostic GPRS
0x002F mapAbsentSubscriberSmGprsDetach
detached.
0x0030 mapAbsentSubscriberSmDeregGprs
deregistered in HLR for GPRS.
Absent subscriber for SM with diagnostic MS
0x0031 mapAbsentSubscriberSmPurgedGprs
purged for GPRS.
Absent subscriber for SM with diagnostic an
0x0032 mapAbsentSubscriberSmUnidentMsc
unidentified subscriber via the MSC.
Absent subscriber for SM with diagnostic an
0x0033 mapAbsentSubscriberSmUnidentSgsn
unidentified subscriber via the SGSN.
0x0034 mapAtmNotAllowed Any time modification not allowed.
0x0035 mapUnexpectedSubscriber Unexpected subscriber.
0x0036 mapBearerServiceNotProvisioned Bearer service not provisioned.
0x0037 mapInformationNotAvailable Information not available.
Unknown subscriber with diagnostic “npdb
0x0038 mapUnknownSubscriberNpdbMismatch
mismatch”.
0x0039 mapAbsentSubscriberSmNoRespIpsmgw
response for IPSMGW.
0x003A mapIllegalSsOperation Illegal SS operation.
0x003B mapSsSubscriptionViolation SS subscription violation
0x003C mapSsErrorStatus SS error status
0x003D mapSsIncompatibility SS incompatibility
0x003E mapSsNotAvailable SS not available
0x003F mapAtsiNotAllowed ATSI not allowed
0x0040 mapAbsentSubscriberSmDeregIms
deregistered in HLR for IPSMGW.
0x0401 mapAddressTransFail The SMS Destination Address is invalid.
SMS Destination Address is valid but not
0x0402 mapAddressVacant
currently allocated to an SMS terminal.
Broadcast periodicity failure in MSC. Requested
0x0403 mapBcsPeriodicityFailMsc broadcast periodicity cannot be handled by
MSC.
A required terminal resource is not available to
0x0404 mapDestResourceShortage process this message. SMS notification is not
pending.
The destination MS-based SME is SMS
0x0405 mapDestBusy
capable, but is currently engaged in a call.
The MS-based SME is no longer at the
0x0406 mapDestNoLongerAtThisAddr temporary SMS routing address. SMS
notification is not pending.
0x0407 mapDestOutOfService


The size of a parameter or field is not what is
0x0408 mapEncodingProblem
expected.
The SMSTeleserviceIdentifier is not known, is
0x0409 mapInvalidTeleserviceId not supported or is not authorized by an
addressed functional entity.
An optional parameter that is required for a
0x040A mapMissingExpectedParam
particular function.
A parameter is missing that is mandatory for a
0x040B mapMissingMandatoryParam
particular message.
A network node failed, a link failed or a required
0x040C mapNetworkFailure
operation failed.
Network transmission failed due to lack of a
0x040D mapNetworkResourceShortage
network resource shortage or link capacity.
The destination SME does not acknowledge
0x040E mapNoAcknowledgement
receipt of the SMS delivery.
The addressed MS-based SME is known, but it
0x040F mapNoPageResponse does not respond to a page. SMS Notification is
not pending.
0x0410 mapOtherGeneralProblems Other general problems.
0x0411 mapOtherNetworkProblem Other network problem.
0x0412 mapOtherRadioInterfaceProb Other radio interface problem.
Other terminal problem. SMS notification is not
0x0413 mapOtherTerminalProblem
pending.
The MS for an MS-based SME is operating in a
0x0414 mapRadioInterfaceIncomp
mode that does not support SMS at this time.
There is no channel available or there is radio
0x0415 mapRadioInterfaceShortage
congestion at this time.
The service is not supported by an addressed
0x0416 mapServiceNotSupported
functional entity.
The originating MSID is not recognized, the
0x0417 mapServiceOriginationDenied originating address is not allowed for the
originating MS.
The destination is not authorized to receive this
0x0418 mapServiceTerminationDenied
service message, the MC refused the message.
An OTASP or OTAPA session does not currently
0x0419 mapSessionNotActive
exist for the MS.
0x041A mapSmsDelivOnPagingNotSupp SMS delivery on paging channel not supported.
0x041B mapSmsDelivPostponed
The originating supplementary service is not
0x041C mapSupplementServiceSupported
known or supported.
A known parameter has a known, but
0x041D mapUnexpectedParameterValue
unexpected value.
A known parameter has a unknown or
0x041E mapUnrecognizedParameterValue
unsupported value.
0x041F mapUnsuppBsCapability Base Station does not support this service.
The intersystem network interface required for
0x0420 mapUnsuppNetworkInterface the delivery of the received message is not
supported.


The User Data size is too large for access
0x0421 mapUserDataSizeError
technology, transport network, or call mode.
The request cannot be honored, or the MS is
0x0422 mapSmsAccdenDenied
unknown.
0x0423 mapSmsAccdenPostponed
unreachable.
0x0424 mapSmsAccdenUnavailable
unavailable.
0x0425 mapSmsAccdenInvalid The SMS TeleserviceID is invalid.
0x0426 mapAnsiTcapUnknownError Unknown TCAP error.
0x0427 mapAnsiTcapRetErrUnrecMin Unrecognized MIN.
0x0428 mapAnsiTcapRetErrUnrecEsn Unrecognized ESN.
0x0429 mapAnsiTcapRetErrIdHlrMism ID/HLR mismatch.
0x042A mapAnsiTcapRetErrOperSeqProblem Operation sequence problem.
0x042B mapAnsiTcapRetErrResShort Resource shortage.
0x042C mapAnsiTcapRetErrOperNotSup Operation not supported.
0x042D mapAnsiTcapRetErrTrunkUnavail Trunk unavailable.
0x042E mapAnsiTcapRetErrParamErr Parameter error.
0x042F mapAnsiTcapRetErrSysFail System failure.
0x0430 mapAnsiTcapRetErrUnrecParamVal Unrecognized parameter value.
0x0431 mapAnsiTcapRetErrFeatInact Feature inactive.
0x0432 mapAnsiTcapRetErrMissParam Missing parameter.
0x0433 mapAnsiTcapRetErrUnrecImsiTmsi Unrecognized IMSI/TMSI.
0x0434 mapAnsiTcapRetErrTmsiVlrMism TMSI/VLR mismatch.
0x0435 mapAnsiTcapRejGenUnrecCompType General problem unrecognized component type.
0x0436 mapAnsiTcapRejGenIncorComp General problem incorrect component portion.
0x0437 mapAnsiTcapRejGenBadStructComp General problem incorrect component portion.
0x0438 mapAnsiTcapRejGenIncorCompCod General problem incorrect component coding.
0x0439 mapAnsiTcapRejInvDupInvId Invoke problem duplicate invocation.
0x043A mapAnsiTcapRejInvUnrecOp Invoke problem unrecognized operation.
0x043B mapAnsiTcapRejInvIncorParam Invoke problem incorrect parameter.
0x043C mapAnsiTcapRejInvUnrecCorId Invoke problem unrecognized correlation id.
Return result problem unrecognized correlation
0x043D mapAnsiTcapRejRrUnrecCorId
id.
0x043E mapAnsiTcapRejRrUnexpRetres Return result problem unexpected return result.
0x043F mapAnsiTcapRejRrIncorParam Return result problem incorrect parameter.
Return error problem unrecognized correlation
0x0440 mapAnsiTcapRejReUnrecCorId
id.
0x0441 mapAnsiTcapRejReUnexpReterr Return error problem unexpected return error.
0x0442 mapAnsiTcapRejReUnrecError Return error problem unrecognized error.
0x0443 mapAnsiTcapRejReUnexpError Return error problem unexpected error.
0x0444 mapAnsiTcapRejReIncorParam Return error problem incorrect parameter.
0x0445 mapAnsiTcapRejTpUnrecPkgType
package type.
0x0446 mapAnsiTcapRejTpIncorTp
Transaction portion problem badly structured
0x0447 mapAnsiTcapRejTpBadStructTp


0x0448 mapAnsiTcapRejTpUnrecTransid
transaction id.
0x0449 mapAnsiTcapRejTpPermReleasPb
release problem.
0x044A mapAnsiTcapRejTpResourUnavail
unavailable.
0x044B mapAnsiTcapAbort TCAP abort.
0x1000 unknownSubscriberNotHplmn Subscriber not in Home PLMN.
FDA was not executed due to an exceeded FDA
0x1001 fdaBarredByLicenceLimit
licence limit.
0x1002 callBarredLocalScreening Local screening barred MO submission.
0x1003 callBarredRouting Barred message routing.
0x1100 sccpNoTransAddrNature
0x1101 sccpNoTransSpecAddr
0x1102 sccpSubsystemCongestion
0x1103 sccpSubsystemFailure
0x1104 sccpUnequippedUser
0x1105 sccpMtpFailure
0x1106 sccpNetworkCongestion
0x1107 sccpUnqualified
0x1108 sccpErrMsgTrans
0x1109 sccpErrLocalProcess
0x110A sccpDestNoReassembly
0x110B sccpFailure
0x110C sccpHopCounterViolation
0x110D sccpSegmNotSupport
0x110E sccpSegmFailure
0x110F sccpErr
0x1200 mapPErrNoResponseFromPeer MAP Provider errors.
0x1201 mapPErrServiceCompletionFailure.
0x1202 mapPErrInvalidRespReceived
0x1203 mapPErrServiceNotSupported
0x1204 mapPErrMistypedParameter
0x1205 mapPErrDuplicateInvokeId
0x1206 mapPErrResourceLimitation
0x1207 mapPErrInitiatingRelease
0x1208 mapPErrUnexpectedResponseFromPeer
0x1300 mapPAbrtErr MAP-P-Abort Provider reasons.
0x1301 mapPAbrtMalfunction
0x1302 mapPAbrtDialogReleased
0x1303 mapPAbrtResourceLimit
0x1304 mapPAbrtAbnormalDialog
0x1305 mapPAbrtInvalidPdu
0x1400 mapOpenRefuseOutOfDialogs MAP-Open Refuse reasons.
0x1401 mapOpenRefuseReasonUnknown
0x1402 mapOpenRefuseReasonInvDestRef
0x1403 mapOpenRefuseReasonInvSrcRef


0x1404 mapOpenRefuseReasonAcNotSupp
0x1405 mapOpenRefuseReasonNodeNotReach MAP-Open Refuse reason.
0x1406 mapOpenRefuseReasonPotentialVersionIncomp
0x1500 mapNoticeUnexpectedResult MAP-Notice Problem diagnostic codes.
0x1501 mapNoticeUnexpectedError
0x1502 mapNoticeAbnormalEventReceived
0x1503 mapNoticeMessageCannotBeDelivered
0x1504 mapNoticeResponseRejected
0x1505 mapNoticeAbnormalEventDetected
MAP-U-Abort User Reasons/Diagnostic
0x1600 mapUAbrtErr
Information.
0x1601 mapUAbrtUserSpecificReason
0x1602 mapUAbrtResourceLimitation
0x1603 mapUAbrtResourceUnavailableShortTerm
0x1604 mapUAbrtResourceUnavailableLongTerm
0x1605 mapUAbrtProcCancellationReasonHandover
0x1606 mapUAbrtProcCancellationRadioChannelRelease
0x1607 mapUAbrtProcCancellationNetworkPathRelease
0x1608 mapUAbrtProcCancellationCallRelease
0x1609 mapUAbrtProcCancellationAssociatedProcedureFailure
0x160A mapUAbrtProcCancellationTandemDialogRelease
0x160B mapUAbrtProcCancellationRemoteOperationsFailure
0x6000 - 0x6FFF sipError SIP response codes masked with 0x6000.
3.1.4.2 Values of SM parameters
Table 3.6: MESSAGE_MODE

0x01 SF MO–MT Store and Forward mode
0x03 SINGLE MO–MT Single Shot mode
0x04 FDA FDA mode
0x05 FDA_PROXY_EA FDA Proxy Early Ack mode
0x06 MT_PROXY_EA MT Proxy Early Ack mode
0x07 MT_PROXY MT Proxy mode
0x08 MO_INTERCEPT MO Intercept mode
0x0B MT_INTERCEPT MT Intercept mode

Table 3.7: MSG_TYPE

Short message (SMS-SUBMIT or
0x01 SM
SMS-DELIVER)
0x02 RCPT Delivery receipt (SMS-STATUSREPORT)
0x03 CMD Command (SMS-COMMAND)
0x04 O-COPY Originator copy
0x05 R-COPY Recipient copy
0x06 MM Multimedia Message
Message related to start of a session, e.g. SIP
0x07 SESSION_START
INVITE
0x08 SM-FLASH SM displayed without storing on the device
0x09 CONTROL Control message
Message related to end of a session, e.g. SIP
0x0A SESSION_END
BYE
Table 3.8: PAYLOAD_INFO_ENCODING

Encoding is unknown, e.g. if an SM is
0x00 UNKNOWN
compressed.
0x01 GSM GSM 7 bit default alphabet
0x02 BIN 8 bit data
0x03 UCS2 UCS2
0x04 ASCII Payload converted to ASCII
0x05 LATIN1 Payload converted to ISO-LATIN1
0x13 UTF8 Payload in UTF8
Table 3.9: PAYLOAD_INFO_SINGLE_SHIFT_TAB

0x01 Turkish Turkish language single shift table
0x02 Spanish Spanish language single shift table
0x03 Portuguese Portuguese language single shift table
0x04 Bengali Bengali language single shift table
0x05 Gujarati Gujarati language single shift table
0x06 Hindi Hindi language single shift table
0x07 Kannada Kannada language single shift table
0x08 Malayalam Malayalam language single shift table
0x09 Oriya Oriya language single shift table
0x0A Panjabi Panjabi language single shift table
0x0B Tamil Tamil language single shift table
0x0C Telugu Telugu language single shift table
0x0D Urdu Urdu language single shift table

Table 3.10: PAYLOAD_INFO_LOCKING_SHIFT_TAB

0x01 Turkish Turkish language locking shift table
0x03 Portuguese Portuguese language locking shift table
0x04 Bengali Bengali language locking shift table
0x05 Gujarati Gujarati language locking shift table
0x06 Hindi Hindi language locking shift table
0x07 Kannada Kannada language locking shift table
0x08 Malayalam Malayalam language locking shift table
0x09 Oriya Oriya language locking shift table
0x0A Panjabi Panjabi language locking shift table
0x0B Tamil Tamil language locking shift table
0x0C Telugu Telugu language locking shift table
0x0D Urdu Urdu language locking shift table
Table 3.11: MSG_ERROR_CODE

0x0000 NO_ERROR No error
0x0001 SM_UNKNOWN_SUBSCRIBER SRI–SM
0x0002 SM_ABSENT_SUBSCRIBER_SM SRI–SM, MT–FWSM
0x0003 SM_ILLEGAL_SUBSCRIBER MT–FWSM
0x0004 SM_TELESERVICE_NOT_PROVISIONED SRI–SM
0x0005 SM_ILLEGAL_EQUIPMENT MT–FWSM
0x0006 SM_CALL_BARRED SRI–SM
0x0007 SM_FACILITY_NOT_SUPPORTED SRI–SM, MT–FWSM, MO–FWSM
0x0008 SM_SUBSCRIBER_BUSY_FOR_MT_SMS MT–FWSM
0x0009 SM_SM_DELIVERY_FAILURE MT–FWSM, MO–FWSM
0x000A SM_SYSTEM_FAILURE SRI–SM, MT–FWSM, MO–FWSM, ALERT–SC
0x000B SM_DATA_MISSING SRI–SM, MT–FWSM, ALERT–SC
0x000C SM_UNEXPECTED_DATA_VALUE SRI–SM, MT–FWSM, MO–FWSM, ALERT–SC
0x000D SM_LA_NOT_CONNECTED Internal: a recipient LA is not connected
0x000E SM_INTER_WORKING_ERROR Internal: an interworking error
0x000F SM_DC_SYSTEM_FAILURE Internal: a DC system error
0x0010 SM_BEARER_SERVICE_NOT_PROVISIONED The bearer service is not provisioned.
0x0011 SM_ATM_NOT_ALLOWED ATM is not allowed.
0x0012 SM_INFORMATION_NOT_AVAILABLE The message information is not available.
0x0013 SM_PREPAID_CANNOT_CHARGE The prepaid interface is not available.
0x0014 SM_PREPAID_ORIG_BLOCKED The originator has insufficient funds.
0x0015 SM_PREPAID_RECIP_BLOCKED The recipient has insufficient funds.
Both the originator and recipient have
0x0016 SM_PREPAID_BOTH_BLOCKED
insufficient funds.
0x0017 SM_BARRED_BY_APPLICATION The message is rejected by an application.
The message is rejected due to the keyword
0x0018 SM_BARRED_BY_KEYWORD_FILTERING
filtering.


The message is rejected due to the anti-flooding
0x0019 SM_BARRED_BY_ANTI_FLOODING
check.
0x0020 SM_BILLING_ERROR Billing error
0x0021 SM_DELIVERY_FAILURE_MEM_CAP_EXCEED Delivery failure because of full memory
0x0022 SM_DELIVERY_FAILURE_EQUIP_ERR Delivery failure because of an equipment error
Delivery failure because of an unequipped
0x0023 SM_DELIVERY_FAILURE_NOT_SM_EQUIP
recipient
0x0024 SM_ORIG_ID_INVALID The originator’s ID is invalid.
0x0025 SM_RECIP_ID_INVALID The recipient’s ID is invalid.
0x0026 SM_SYSTEM_BUSY The system is busy.
0x0027 SM_TIMEOUT Timeout
0x0028 SM_SC_ADDRESS_INVALID The SC address is not valid.
0x0029 SM_ORIG_ADDRESS_INVALID The originating address is invalid.
0x0030 SM_RECIP_ADDRESS_INVALID The recipient address is invalid.
0x0031 SM_SERVICE_RESTRICTED The service has been restricted.
0x0032 SM_SERVICE_THROTTLED The service has been throttled.
0x0033 SM_SERVICE_FAILURE The service has failed.
0x1000-0x1063 SM_CUSTOM_<1-100> Custom Error 1-100
Table 3.12: MSG_STATUS

0x00 SUBMITTED The submission process of an SM started.
0x01 REJECTED The SM was rejected.
0x02 ACCEPTED The SM was accepted for delivery.
0x03 BUFFERED The SM was buffered (S&F mode).
0x04 DELIVERED The SM was successfully delivered.
0x05 NOT_DEL_TEMP Unsuccessful delivery attempt, temporary error.
0x06 NOT_DEL_PERM Unsuccessful delivery attempt, permanent error.
0x07 DELETED The SM was deleted (e.g. by SMPP cancel_sm).
0x08 EXPIRED The SM validity period expired.
0x09 HANDED_OVER The SM was successfully handed over.
0x0A NOT_HANDED_OVER The handover was not successful.
3.1.4.3 Values of information flags
Table 3.13: INFORMATION_FLAGS

The message was detected as spoofed due to a GT
0x 0000 0000 0000 0001 infoMOSpoofedGT
mismatch.


The message was detected as spoofed due to an IMSI
0x 0000 0000 0000 0002 infoMOSpoofedIMSI
mismatch.
The message was detected as spoofed because
0x 0000 0000 0000 0004 infoMOSpoofedHLR
MAP-SRI-SM, which verifies the originator, failed.
The message was detected as a fake because MT-FW-SM
0x 0000 0000 0000 0008 infoMTFakeNoSRI
was not preceded by SRI-SM.
0x 0000 0000 0000 0010 Reserved n/a
SRI-SM phishing was detected. MT-FW-SM did not arrive
0x 0000 0000 0000 0020 infoPhishingDetected
after SRI-SM.
0x 0000 0000 0000 0040 infoMTFake Message was detected as a fake (by RBDL).
0x 0000 0000 0000 0080 infoPhishingBlacklisted Indicates an SRI phishing attempt (known phisher).
0x 0000 0000 0000 0100 infoCorruptUDH UDH of the message is malformed.
The message contains an application port which is not
0x 0000 0000 0000 0200 infoUnauthorizedAPA
allowed for a submitter.
0x 0000 0000 0000 0400 infoMNPForeignSubscriber The originating subscriber is foreign (wrong IMSI address).
The message content contains a keyword specified in a
0x 0000 0000 0000 0800 infoKeywordMatched
keyword group.
0x 0000 0000 0000 1000 infoBlackList1 The message is included in blacklist 1.
0x 0000 0000 0000 2000 infoBlackList2 The message is included in blacklist 2.
0x 0000 0000 0000 4000 infoWhiteList1 The message was blacklisted by not matching whitelist 1.
0x 0000 0000 0000 8000 infoWhiteList2 The message was blacklisted by not matching whitelist 2.
The charged subscriber has not sufficient credit to send a
0x 0000 0000 0001 0000 infoNoCredit
message.
0x 0000 0000 0002 0000 infoWrongSCAddress The SC address check failed.
0x 0000 0000 0004 0000 Reserved n/a
0x 0000 0000 0008 0000 infoOwnSubscriber Not used any more.
0x 0000 0000 0010 0000 infoNVLExceeded Network volume limit was exceeded.
TCAP handshake was expected for the message but did
0x 0000 0000 0020 0000 infoTCAPHandshakeNotPresent
not happen.
0x 0000 0000 0040 0000 infoFloodDetected Flooding was detected.
0x 0000 0000 0080 0000 infoOwnSubscriberNotKnown Not used any more.
0x 0000 0000 0100 0000 infoFlashMessage Indicates a flash message (Message Class 0).
Indicates whether submitting messages for foreign
0x 0000 0000 0200 0000 infoOtherOperNotAllowed
recipients is forbidden for the originating LA.
0x 0000 0000 0400 0000 Reserved n/a
FDA (successful or unsuccessful) has been applied to the
0x 0000 0000 0800 0000 infoFDAApplied
message.
0x 0000 0000 1000 0000 infoMoHandoverAck Indicates an MO handover acknowledgement.
Indicates that an SM is a home-routed message (FSG
scenario).
0x 0000 0000 2000 0000 infoHomeRoutedMt - An intercepted MT message is any inbound MT message.
- A network intercepted MT message is any inbound MT
message not home-routed.
Indicates that an MSC/SGSN timestamp adjustment shall
0x 0000 0000 4000 0000 infoTzSkipLocation
be omitted.
Indicates that an MS ISDN/IMSI timestamp adjustment
0x 0000 0000 8000 0000 infoTzSkipRecipient
shall be omitted.
Indicates that adjustment of a TP-SCTS timestamp shall
0x 0000 0001 0000 0000 infoTzSkipScts
be omitted.


Indicates that adjustment of a TP-DC timestamp shall be
0x 0000 0002 0000 0000 infoTzSkipDt
omitted.
0x 0000 0004 0000 0000 infoMoSpoofedTCAP Spoofed (TCAP handshake expected)
0x 0000 0008 0000 0000 infoMoSpoofed Spoofed MO message (unspecified reason)
0x 0000 0010 0000 0000 infoMtFakeTcap Fake MT message (TCAP handshake expected)
0x 0000 0020 0000 0000 infoADTIllegal ADT has marked the MSISDN address as illegal
An external Content Control application indicates that
0x 0000 0040 0000 0000 infoContentIllegal
illegal content has been detected in a message.
A malformed message has been received – covers the
0x 0000 0080 0000 0000 infoMalformed structure of a received packet as well as unexpected
values of its fields, e.g. validity period in past, etc.
0x 0000 0100 0000 0000 infoAddressValidation Indicates that validation of addresses has failed.
Indicates that reassembly was configured to be performed
0x 0000 0200 0000 0000 infoReassemblyNotApplied
with a message but was not applied.
The message was detected as faked either because
0x 0000 0400 0000 0000 infoMtFakeHLR MAP-SRI-SM, which verifies the originator, failed or due to
information from MAP-SRI-SM.
Unauthorized attempt to send a message to SIM Toolkit
0x 0000 0800 0000 0000 infoSTKAttackAttempt
was detected or blocked.
0x 0000 1000 0000 0000 infoCustomRejectReason1
#1.
#2.
#3.
#4.
The MT Correlation failed as SRI cache was not able to
0x 0001 0000 0000 0000 infoMtCorrelIdUnknown
find an SRI record based on MT Correlation ID.
The MT Correlation failed as an SRI cache record was
0x 0002 0000 0000 0000 infoMtCorrelInvalid
invalidated by a previous MT message.
The MT Correlation failed as the MT Correlation ID validity
0x 0004 0000 0000 0000 infoMtCorrelIdTimeout
period in the SRI cache record has expired.
The MT Correlation failed as an MT-SM comes to MCO,
0x 0008 0000 0000 0000 infoMtCorrelNoIntercept but the SRI cache record does not have an interception
request flag.
The MT Correlation failed as the SC address from MT-SM
0x 0010 0000 0000 0000 infoMtCorrelSCAddrNoMatch
does not match SC address in the cache.
0x 0020 0000 0000 0000 infoMTFakeCcGtSc
and SC MAP address mismatch in country code.
0x 0040 0000 0000 0000 infoMTFakeCcGtMsisdn
and MSISDN mismatch in country code.
0x 0080 0000 0000 0000 infoMTFakeCcScMsisdn
The message was detected as faked due to the SC GT
0x 0100 0000 0000 0000 infoMTFakeGT does not match with originator subscriber HLR responding
GT.
0x 0200 0000 0000 0000 infoMTFakeSC address does not match with originator subscriber HLR
responding GT.


The message was detected as spoofed due to the SC
0x 0400 0000 0000 0000 infoMOSpoofedCcScMsisdn
address and originator MSISDN mismatch in country code.
0x 0800 0000 0000 0000 infoDetectedThreat Indicates possible spam or fraudulent message.
Indicates that message contains potentially malicious
0x 1000 0000 0000 0000 infoDetectedMaliciousRef
reference (MSISDN, URL).
0x 2000 0000 0000 0000 infoCLOUActualSriSent SRI request has been initiated by MCO.
Indicates that message text wasn’t able to be converted to
0x 4000 0000 0000 0000 infoTextUnconvertable readable form (UTF-8) and message was processed
transparently.
0x 8000 0000 0000 0000 infoBarringActive Indication of active barring on the service.
any other flag Reserved n/a
3.1.4.4 Values of extended information flags
Table 3.14: INFORMATION_FLAGS_EXT_1

0x 0000 0000 0000 0001 infoAppLaOrig Message originator is an application (SALA, MALA).
0x 0000 0000 0000 0002 infoAppLaRecip Message recipient is an application (SALA, MALA).
0x 0000 0000 0000 0004 infoISR Indicates an ISR message.
ISR message was rejected by the foreign SMSC in the
0x 0000 0000 0000 0008 infoISRRejectedByFSMSC
submission phase.
Message originator identity visibility restricted; the
0x 0000 0000 0000 0010 infoHideCLIR
recipient sees an empty originator address.
0x 0000 0000 0000 0020 Reserved n/a
0x 0000 0000 0000 0040 infoPhishingMonitored SRI phishing monitoring is active.
0x 0000 0000 0000 0080 infoATOActualAtsiSent ATSI request was initiated by MCO.
0x 0000 0000 0000 0100 infoRARRApplied APPLY_RARR action successfully applied.
0x 0000 0000 0000 0200 infoLASNApplied APPLY_LASN action successfully applied.
0x 0000 0000 0000 0400 infoSMSIP SMSIP flag is set in the registration update.
Message was acknoledged during the submission phase
0x 0000 0000 0000 0800 infoImmediateAckApplied
before the Incoming SP.
0x 0000 0000 0000 1000 infoActualHSSReqSent HSS request was initiated by MCO.
Message was delivered via its own queue, not the recipient
0x 0000 0000 0000 2000 infoProxyHighApplied
queue.
0x 0000 0000 0000 4000 infoATOActualAtiSent ATI request was initiated by MCO.
3.1.4.5 Values of reasons for message rejecting

Table 3.15: MSG_REJECT_REASON

0x 0000 0000 0000 0001 MO_SPOOFED_GT The message was blocked due to a GT mismatch.
0x 0000 0000 0000 0002 MO_SPOOFED_IMSI The message was blocked due to an IMSI mismatch.
The message was blocked due to failure to get
0x 0000 0000 0000 0004 MO_SPOOFED_HLR
information from HLR.
The message was blocked due to failure to correlate
0x 0000 0000 0000 0008 MT_FAKE_NO_SRI
with SRI-SM.
0x 0000 0000 0000 0010 reserved n/a
0x 0000 0000 0000 0020 reserved n/a
The message was detected as a fake and blocked (by
0x 0000 0000 0000 0040 MT_FAKE
RBDL logic).
0x 0000 0000 0000 0080 Reserved n/a
0x 0000 0000 0000 0100 CORRUPT_UDH The message was blocked due to a malformed UDH.
The message was blocked because an application
0x 0000 0000 0000 0200 UNAUTH_APA
port in UDH is not authorised for a submitter.
The message was blocked due to a foreign originator
0x 0000 0000 0000 0400 MNP
(wrong IMSI address).
The message was blocked due to a forbidden
0x 0000 0000 0000 0800 KEYWORD_MATCHED
keyword in the message.
The message was blocked due to a match with
0x 0000 0000 0000 1000 BLACKLIST1
blacklist 1.
The message was blocked due to a match with
0x 0000 0000 0000 2000 BLACKLIST2
blacklist 2.
The message was blocked due as it does not match
0x 0000 0000 0000 4000 WHITELIST1
with whitelist 1.
The message was blocked due as it does not match
0x 0000 0000 0000 8000 WHITELIST2
with whitelist 2.
The message was blocked due to a lack of credit of
0x 0000 0000 0001 0000 NO_CREDIT
the charged subscriber.
The message was blocked due to a wrong SC
0x 0000 0000 0002 0000 WRONG_SC_ADDRESS
address.
0x 0000 0000 0004 0000 Reserved n/a
0x 0000 0000 0008 0000 Reserved n/a
The message was blocked due to an exceeded limit
0x 0000 0000 0010 0000 NVL_EXCEEDED
(volume limit).
0x 0000 0000 0020 0000 Reserved n/a
The message was blocked due to an exceeded limit
0x 0000 0000 0040 0000 FLOOD_DETECTED
(antiflood).
0x 0000 0000 0080 0000 Reserved n/a
0x 0000 0000 0100 0000 Reserved n/a
0x 0000 0000 0200 0000 Reserved n/a
0x 0000 0000 0400 0000 Reserved n/a
0x 0000 0000 0800 0000 Reserved n/a
0x 0000 0000 1000 0000 Reserved n/a
0x 0000 0000 2000 0000 Reserved n/a
0x 0000 0000 4000 0000 Reserved n/a
0x 0000 0000 8000 0000 Reserved n/a
0x 0000 0001 0000 0000 Reserved n/a
0x 0000 0002 0000 0000 Reserved n/a


The MO message was blocked due to a missing
0x 0000 0004 0000 0000 MO_SPOOFED_TCAP
TCAP handshake.
0x 0000 0008 0000 0000 MO_SPOOF The MO message was blocked (unspecified reason).
The MT message was blocked due to a missing
0x 0000 0010 0000 0000 MT_FAKE_TCAP
TCAP handshake.
The message was blocked due an illegal MSISDN
0x 0000 0020 0000 0000 ADT_ILLEGAL
address (ADT).
The message was blocked due to the advanced
0x 0000 0040 0000 0000 ADVANCED_CC
content control validation.
The message was blocked due to a malformed
0x 0000 0080 0000 0000 MALFORMED
structure or an unexpected value of a field in PDU.
The message was blocked due to an invalid address
0x 0000 0100 0000 0000 ADDRESS_VALIDATION
(unspecific reason).
0x 0000 0200 0000 0000 Reserved n/a
The message was blocked due to failure to get
0x 0000 0400 0000 0000 MT_FAKE_HLR information from HLR or based on the information
received from HLR.
The message was blocked due to detected
0x 0000 0800 0000 0000 STK_ATTACK_ATTEMPT
unauthorized attempt to message the SIM Toolkit.
0x 0000 1000 0000 0000 CUSTOM_REJECT_REASON_1 The message was blocked due to custom reason #1.
The message was blocked due to SRI cache was not
0x 0001 0000 0000 0000 MT_CORREL_ID_UNKNOWN
able to find SRI record based on MT Correlation ID.
The message was blocked due to SRI cache record
0x 0002 0000 0000 0000 MT_CORREL_INVALID
was invalidated by previous MT message.
The message was blocked due to MT Correlation ID
0x 0004 0000 0000 0000 MT_CORREL_ID_TIMEOUT
validity period in SRI cache record has expired.
The message was blocked due to MT comes to MCO,
0x 0008 0000 0000 0000 MT_CORREL_NO_INTERCEPT but SRI cache record does not have interception
request flag.
The message was blocked due to the SC address
0x 0010 0000 0000 0000 MT_CORREL_SC_ADDR_NO_MATCH
from MT does not match SC address in cache.
The message was blocked due to the source GT and
0x 0020 0000 0000 0000 MT_FAKE_CC_GT_SC
SC MAP address mismatch in country code.
The message was blocked due to the source GT and
0x 0040 0000 0000 0000 MT_FAKE_CC_GT_MSISDN
MSISDN mismatch in country code.
The message was blocked due to the SC MAP
0x 0080 0000 0000 0000 MT_FAKE_CC_SC_MSISDN
The message was blocked due to the SC GT does not
0x 0100 0000 0000 0000 MT_FAKE_GT
match with originator subscriber HLR responding GT.
The message was blocked due to the SC MAP
0x 0200 0000 0000 0000 MT_FAKE_SC address does not match with originator subscriber
HLR responding GT.
The message was blocked due to the SC address
0x 0400 0000 0000 0000 MO_SPOOFED_CC_SC_MSISDN
and originator MSISDN mismatch in country code.
0x 8000 0000 0000 0000 BARRING_ACTIVE The message was blocked due to the active barring.

3.1.4.6 Used structures
Table 3.16: Used structures
Structure Field Type Description

ISDN-ADDR TON UINT8 Type of Number (see [3GPP_23.040])
NPI UINT8 Numbering Plan Indicator (see [3GPP_23.040])
Address STRING Address string
SCCP-ADDR RI UINT8 Routing Indicator (1:route on SSN, 0:route on GT)
SSN UINT8 Subsystem Number
PC UINT32 Point Code
GT_NAI UINT8 Global Title Nature of Address Indicator
GT_NPI UINT8 Global Title Numbering Plan Indicator
GT_Address STRING Global Title Address string
GT_TT UINT8 Global Title Translation Type
CONCAT-INFO MAXSEG UINT8 Number of segments
This field indicates that the message is a reassembled
concatenated message if the field value is 0. In other
CURSEG UINT8
cases, the field value is a sequence number of the current
segment of a concatenated message.
REF UINT16 Reference number
PAYLOAD-INFO ENC UINT8 Message encoding, see Table 3.8.
SIZE UINT16 Message payload size in bytes
NUMCH UINT16 Number of characters of the message
SSTAB UINT8 National language single shift table, see Table 3.9.
LSTAB UINT8 National language locking shift table, see Table 3.10.
3.1.4.7 Network types
Table 3.17: NETWORK_TYPE
Value Meaning
0 UNKNOWN
1 GSM
2 GSM over IP
3 SMPP
4 CDMA
5 IDEN
6 CDMA over IP
7 IMS
8 Generated
9 ADMI
10 RCS_CPM
17 UCP

3.1.5 Message ID mapping
If a message is sent to MCO from an SMPP ESME connected using the SMPP v3.3 protocol, a short 4-byte message ID is
assigned to the message. However, internally, the message has a 16-byte message ID, which is unique over all nodes within
a cluster. This 16-byte message ID is present in billing files and if the 4-byte one is required, it can be computed as the first 8
characters of the 16-byte message ID.
Example:
If the message ID in billing files is EC2A0B90ABCD007000003A3039300000, the actual 4-byte message ID sent to the
ESME is EC2A0B90.
3.2 Infinity SMSC billing files
This section describes legacy Infinity SMSC (ISMSC) billing files. The ISMSC stream type is available as the CSV_ISMSC stream
type.
3.2.1 Stream applicability
This stream is intended for recording in the submission phase and once a message is delivered. Use the CREATE_SDR(CSV_IS
MSC) action in the IN_MSG and FINAL_MSG SDR RBDL stages only.
3.2.2 Optional special attribute fields
These are fields which value is recorded in the <tag>:<value> format. In MCO, the tag is part of the field name, for example,
the 333_ORIG_ESME_PROFILE_NAME field records a source LA as 333:SMPP_TEST.0.
MCO allows a customer to customise tags used per special attribute field, thus when the same field is configured as 222_ORIG
_ESME_PROFILE_NAME , the field is recorded as 222:SMPP_TEST.0. It is also possible to omit the tag at all by configuring a
field with no tag, thus when the same field is configured as ORIG_ESME_PROFILE_NAME , the field is recorded as SMPP_TEST.
0.
3.2.3 Custom/extension attributes
Custom/extension attributes are recorded as optional special attribute fields.
3.2.4 Stream decoding
To decode this SDR stream, use command ismsc_decode:

$ ismsc_decode ISMSC.00.20170308101953Z.csv -l ISN STATE VALIDITY_PERIOD SM_CLASS 333 ←-
_ORIG_ESME_PROFILE_NAME
================== ISMSC.00.20170308101953Z.csv - START - ==================
------------------ Record from line: 2 ------------------
ISN(): B41A8FD6E803E7618D48000000003B56
VALIDITY_PERIOD(): 24300
STATE(): I
SM_CLASS(): M
333_ORIG_ESME_PROFILE_NAME(): 333:SMPP_TEST.0
================== ISMSC.00.20170308101953Z.csv - END - ====================

3.2.5 Supported fields
The full list of available field types and applicable constraints is given in Table 3.18.
Important
The table lists all available attributes in a random order. The second column denotes the unique identification of the
attributes. The field name is used to configure whether a particular field appears in the SDR and in which position.
Table 3.18: ISMSC SDR stream type fields
# Field name Description

1 ISN Message ID - recorded as 32 alphanumeric characters (0-9A-F)
2 TEXT_LEN Size (number bytes) of the message payload
3 TARGET_ID Recipient address
4 ORIGINAL_TARGET Recipient untranslated address
5 SOURCE_ID Originator address
6 SOURCE_MSC_ADDR Source MSC address
7 SEND_MODE Always zero (0)
8 SOURCE_EI_TYPE Type of the source: 9 for SMPP and UCP, otherwise 3
9 SOURCE_EI_CLASS Always one (1)
10 SOURCE_EI_GROUP Always one (1)
Source interface/network type (MAP.1:0, IS41.1:0); when an application
11 SOURCE_EI_ID interface is used, it is either followed by the LA name (e.g. SMPP.TEST:0 or
UCP.TEST:0) or only LA name is recorded (e.g. TEST:0)
12 SOURCE_EI_VERSION Always 1.0
13 TYPE Service type ID - numeric representation of the [SMPP] service_type
INITIAL_DELIVERY_
14 Always zero (0)
ATTEMPTS_COUNT
15 ENTRY_DATE Date and time of a message submission
Date and time a message reached the current state, i.e. submission or final
16 STATE_DATE
date and time
17 GSM_PRIORITY Priority of a message
18 GSM_REPLACE Always -1
19 GSM_PROTOCOL_ID Protocol Identifier, see TP-PID in [3GPP_23.040]
Message content encoding on submission, ???/<enc>, <enc> =
20 LANG
dfl|data|ucs2|ascii|lat1|ia5|gsmext|utf8|???
21 PRIORITY Priority of a message
22 TRACE_LEVEL Always zero (0)
Message content encoding on delivery, ???/<enc>, <enc> =
23 LANG_OUT
24 VALIDITY_PERIOD Message validity in seconds relative to the submission date and time
Message status:
D for DELIVERED
U for REJECTED|NOT_DEL_PERM
25 STATE
E for EXPIRED
C for DELETED
I for SUBMITTED|ACCEPTED|BUFFERED|NOT_DEL_TEMP
26 NOTIF_EXT_ISN Message ID of the original message which status is reported by the receipt


27 NOTIF_EXT_SM_TYPE Always zero (0)
Receipt content encoding, ???/<enc>, <enc> =
28 NOTIF_EXT_LANG
29 NOTIF_EXT_SOURCE Originator of the original message being reported by the receipt
30 NOTIF_EXT_CREATION_DATE Date and time of the receipt creation
31 NOTIF_EXT_ARRIVAL_DATE Date and time of the receipt creation
Date and time a receipt reached the current state, i.e. submission or final
32 NOTIF_EXT_STATE_DATE
date and time
Message status of the original message being reported by the receipt:
D for DELIVERED
U for REJECTED|NOT_DEL_PERM
33 NOTIF_EXT_STATE
E for EXPIRED
C for DELETED
I for SUBMITTED|ACCEPTED|BUFFERED|NOT_DEL_TEMP
Subscription of a message to notifications: 0 for no subscription, 1 for a
34 NOTIF_IND
receipt subscription
Message type/class: M for an MT message, T for an AT message, N for a
35 SM_CLASS
receipt
36 NUM_BYTES_SUCCEEDED Number of payload bytes which reached the target: zero (0) or all
37 NUM_PARTS_SUCCEEDED Number of segments which reached the target: zero (0) or all
38 TOTAL_NUM_PARTS Total number of segments
39 DELIVERY_ATTEMPTS Number of delivery attempts for a message
40 DESTINATION_MSC_ADDR Destination MSC address
41 EI_TYPE Type of the destination: 9 for SMPP and UCP, otherwise 3
42 EI_CLASS Always one (1)
43 EI_GROUP Always one (1)
Destination interface/network type (MAP.1:0, IS41.1:0); when an application
44 EI_ID interface is used, it is either followed by the LA name (e.g. SMPP.TEST:0 or
UCP.TEST:0) or only LA name is recorded (e.g. TEST:0)
45 EI_VERSION Always 1.0
46 NUM_OF_FORWARD_SM Total number of segments
47 VSMSC_ID Always -1
Prepaid state (based on BILLING_DATA flags):
N for Not prepaid
48 PREPAID_STATE T for Prepaid target
S for Prepaid source
B for Both prepaid (source and target)
49 PID Protocol Identifier, see TP-PID in [3GPP_23.040]
50 PRIMARY_TARGET Always empty
51 178_APPLICATION_SRC_PORT Indicates the application’s source port.
52 179_APPLICATION_DEST_PORT Indicates the application’s destination port.
53 181_SAR_MSG_REF_NUM Indicates the SAR concatenated message reference number.
54 182_SAR_TOTAL_SEGMENTS Indicates the total number of segments in the SAR concatenated message.
55 183_SAR_SEGMENT_SEQNUM Indicates the specific segment ID of the SAR concatenated message.
56 250_SOURCE_NETWORK_TYPE Indicates the source network type.
57 256_SERVICE_TYPE Indicates the service type.
Indicates the source consolidation ID parameter. This value is used for a
58 301_SOURCE_CONSOLIDATION
group of ESMEs and defined according to the customer’s needs.


Indicates the target consolidation ID parameter. This value is used for a
59 302_TARGET_CONSOLIDATION
group of ESMEs and defined according to the customer’s needs.
60 333_ORIG_ESME_PROFILE_NAME Indicates the ESME profile name of the sender application.
61 334_DEST_ESME_PROFILE_NAME Indicates the ESME profile name of the destination application.
Indicates the address the Notification should be sent to. SA used in the
62 340_NOTIFICATION_ADDRESS
UCP AO flow.
Any custom attribute specified by rbdl_conf.extdata. <any>
63 <any>_$custom.attribute
determines numeric identification of the field (SA number).
3.3 Telepath fixed-length billing files
MCO supports also fixed-length text field records. This format provides compatibility with Telepath SMSC SDR billing files. All
commonly used Telepath SMSC fields are supported; rarely used or deprecated fields are not supported.
This stream is intended for recording in the submission phase and once a message is delivered. Use the CREATE_SDR(CSV_TP)
action in the IN_MSG and FINAL_MSG SDR RBDL stages only.
3.3.2 Field format
Individual fields can be formatted using the following format description:

TEXT(<width>, <padding>, <fill character>, <default string>)
where
<width> is the width of the field.
<padding> is character L or R for the left or right value position within the field width.
<fill character> is the character for filling the empty space (usually space or zero).
<default string> is the default value if the field value does not exist (usually ’0’ or ’<none>’)..
Do not use comma, colon, semicolon, quotes or parenthesis as <fill character> or in <default string>.
Date and time fields are formatted as follows:
DATE(TELEPATH) - UTC time in the Telepath format.
DATE(TIME_T) - UTC time as a UNIX time stamp.
Any configured stream of records can contain fields listed in Table 3.19.
Important
The table lists all available attributes in a random order. The first column (ID) denotes the unique identification of an
attribute. Whether a particular field appears in a produced SDR and on which position can be configured using the unique
identification (ID).

Table 3.19: Possible parameters of fixed-length billing stream
ID Field name Description Possible values/Size Field type Default format

ASCII characters
TP_1 Structure Code Structure code of the record; fixed value 6 bytes String TEXT(6)
Value = 00099C
ASCII characters
6-7 bytes
Left delimiter 01
TP_2 Calling TON,NPI TON and NPI of the source address String TEXT(7)
MCO Billing Interface Manual

TON 1-2 bytes

NPI 2 bytes
COMMERCIAL-IN-CONFIDENCE
Right delimiter C
ASCII characters
TP_3 Calling Number Number of the calling party String TEXT(20,R,0,’0’)
20 bytes
ASCII characters
6-7 bytes
Left delimiter 01
TP_4 Called TON,NPI TON and NPI of the destination address String TEXT(7)
TON 1-2 bytes
NPI 2 bytes
Right delimiter C
ASCII characters
TP_5 Called Number Full number of the destination address String TEXT(20,R,0,’0’)
20 bytes
Full customer identifier of the source ASCII characters
TP_6 Calling Customer Id String TEXT(20,R)
address 20 bytes
Full customer identifier of the destination ASCII characters
TP_7 Called Customer Id String TEXT(20,R)
address 20 bytes
ASCII characters
TP_8 Calling Service Level Number allocated during provisioning String TEXT(2,R,0,’0’)
2 bytes
ASCII characters
TP_9 Called Service Level Number allocated during provisioning String TEXT(2,R,0,’0’)
2 bytes
Time at which the message was submitted ASCII characters
to MCO; format: YYMMDDhhmmss 16 bytes =
TP_10 Message Submission Time String DATE(TELEPATH)
Time zone information indicating +/-GMT; 12 bytes (time)
format: 0HHC/0HHD (C=+GMT, D= -GMT) 4 bytes (time zone)
Time at which the message was delivered
to MS or time at which the message ASCII characters
reached the state defined in the Cause for 16 bytes =
TP_11 Message Delivery Time String DATE(TELEPATH)
Termination field; format: YYMMDDhhmmss 12 bytes (time)
Time zone information indicating +/-GMT; 4 bytes (time zone)
format: 0HHC/0HHD (C=+GMT, D= -GMT)
Page 110 of 144

ISSUED
R3.0-10.09.B09

ASCII character
4 bytes
Left delimiter: 1.
Right delimiter: C.
Characters 2 and 3
indicate the following:
Reason why the message reached its final

TP_12 Cause for Termination 00: Message delivered String TEXT(4)
state

01: Message expired
02: Message deleted
03: Message
undeliverable
04: Message invalid
05: Message accepted
ASCII characters
TP_13 Call Reference Unique reference of a call String TEXT(12,R,0)
12 bytes
Length of the text part of the message in ASCII characters
TP_14 Message Length String TEXT(4,R,0,’0’)
bytes 4 bytes
ASCII characters
2 bytes
TP_15 Priority Priority level of the message 1C = scheduled or String TEXT(2)
priority messages
0C = otherwise
ASCII characters
2 bytes
It indicates whether the originator requested
TP_16 Deferred 1C = deferred message String TEXT(2)
deferred delivery of the message.
0C = not deferred
message
ASCII characters
2 bytes
It indicates whether the originator requested 1C = receipt is
TP_17 Receipt String TEXT(2)
a receipt for the message. requested
0C = no receipt is
requested
Integer Hexadecimal
TP_18 Protocol ID Protocol ID set by a message indicator TEXT(2,R,0,’0’)
2 bytes number
Page 111 of 144

ISSUED
R3.0-10.09.B09

Number representing an extended short
message class:
1 = not MO message (AO message)
2 = MO message Integer
TP_19 Record Type Integer TEXT(2,R,0,’1’)
3 = copy 2 bytes
4 = receipt

7 = manual ACK

9 = FSG
Number of delivery attempts made before
TP_20 Number of Delivery Attempts 3 bytes String TEXT(3,R,0,’0’)
successful delivery of the message
It indicates the encoding of the message
user data. ASCII characters
TP_21 Message Text Type Integer TEXT(1)
1 = ASCII 1 byte
3 = GSM
Configurable, by default
TP_22 Message Text Message data String TEXT(16,L)
16 bytes
ASCII characters
TP_24 Translated Originator TON TON of the originator of the message Integer TEXT(2)
TON 1-2 bytes
ASCII characters
TP_25 Translated Originator NPI NPI of the originator of the message Integer TEXT(2)
2 bytes
ASCII characters
TP_26 Translated Originator Address Address of the originator of the message String TEXT(20,R,0,’0’)
20 bytes
ID of the user group to which the originator ASCII characters
TP_28 Originator UserGroup ID Integer TEXT(1,R, ,’0’)
belongs 1-3 bytes
ASCII characters
TP_29 Untranslated Originator TON Untranslated originator TON Integer TEXT(2)
1-2 bytes
ASCII characters
TP_30 Untranslated Originator NPI Untranslated originator NPI TEXT(2)
2 bytes
Untranslated Originator ASCII characters
TP_31 Untranslated originator address String TEXT(20,R,0,’0’)
Address 20 bytes
ID of the user group to which the recipient ASCII characters
TP_36 Recipients UserGroup ID Integer TEXT(1,R, ,’0’)
belongs 1-3 bytes
ASCII characters
TP_37 Untranslated Destination NPI Untranslated destination NPI Integer TEXT(2)
2 bytes
ASCII characters
TP_38 Untranslated Destination NPI Untranslated destination NPI Integer TEXT(2)
2 bytes
Untranslated Destination ASCII characters
TP_39 Untranslated destination address String TEXT(20,R,0,’0’)
Page 112 of 144

ISSUED
R3.0-10.09.B09
Address 20 bytes

ID of the virtual SC through which the
TP_40 Billing Format Field Name 1 byte Integer TEXT(1,R, ,’0’)
message was submitted
1 byte
3 = For delivery
TP_41 Message State State of the message 4 = Scheduled Integer TEXT(2)
5 = Done

7 = No state

1 byte
1 = En Route
2 = Delivered
3 = Expired
TP_42 Message Status Status of the message 4 = Deleted Integer TEXT(2)
5 = Undeliverable
6 = Accepted
7 = Invalid
8 = Rejected
0 = NO_RECEIPT
1 = ALL_RECEIPT
2 = NOT_DELIVERED
Type of message status ASCII characters
TP_46 4 = DELIVERY_ACK Integer TEXT(4)
notification requested 1-2 bytes
8 = MANUAL_ACK
16 = INTERMEDIATE_NOT
32 = READ_ACK
Date for attempted delivery of a scheduled
message
ASCII characters
Format: YYMMDDhhmmss
16 bytes =
TP_48 Scheduled Date Time zone information indicating for how String DATE(TELEPATH)
12 bytes (time)
many hours +/-GMT the system was in
4 bytes (time zone)
operation
Format: 0HHC/0HHD (C=+GMT, D= -GMT)
Date at which the message is due to expire; 9-10 bytes
TP_50 Expiry Date Integer DATE(TIME_T)
stored in the UTC format
Address of the virtual SC through which the ASCII characters
TP_57 Source SC Address String TEXT(20,R,0,’<unknown>’)
message was submitted 20 bytes
Integer
TP_63 Mapped Network Error Last recorded SME network error Integer TEXT(1,R, ,’0’)
1-3 bytes
Error code indicating the reason of delivery Integer
TP_64 Local Error Integer TEXT(1,R, ,’0’)
failure 1-3 bytes
Page 113 of 144

ISSUED
R3.0-10.09.B09

Hexadecimal
TP_65 Protocol Identifier Protocol identifier 2 bytes TEXT(2,R,0,’0’)
number
Integer
TP_66 Data Coding Scheme Data coding scheme of the message Integer TEXT(1,R, ,’0’)
1-3 bytes
Integer
TP_67 User Reference Reference supplied by the external system Integer TEXT(1,R, ,’0’)
1-5 bytes

It indicates whether the message is a 2 bytes

receipt (delivery acknowledgement) or a 0C = receipt not set
TP_71 Receipt String TEXT(2)
buffered delivery receipt (intermediate 1C = receipt set
notification). 2C = buffered receipt set
Mobile subscriber identity Number allocated to each mobile handset in ASCII characters
TP_89 String TEXT(20,L, ,’<unknown>’)
address (B-Party IMSI) the GSM network 20 bytes
24 bytes
Global title: TON = 01,
Source MSC address containing TON, NPI NPI = 01, Address = 20
TP_91 Originating MSC Address and 20-character address element in the character digit-string String TEXT(24,R, ,’<unknown>’)
global title or SS7 point code format SS7 point code: TON =
02, NPI = 0C, Address =
20 character string
24 bytes
Global title: TON = 01,
Destination MSC address containing TON, NPI = 01, Address = 20
TP_92 Destination MSC Address NPI and a 20-character address element in character digit-string String TEXT(24,R, ,’<unknown>’)
the global title or SS7 point code format SS7 point code: TON =
02, NPI = 0C, Address =
20 character string
2 bytes
0 = Default billing
1 = Charge originator
2 = Charge recipient
TP_95 Charging Indicator It determines how the message is charged. 4 = SDRs generated but Integer TEXT(2,R,0)
not charged
8 = No SDRs
16 = Charge originator
for reply
Mobile subscriber identity Number allocated to each mobile handset in ASCII characters
TP_100 String TEXT(20,L, ,’<unknown>’)
address (A-Party IMSI) the GSM network 20 bytes
Page 114 of 144

ISSUED
R3.0-10.09.B09

1 byte
It indicates whether the message is prepaid 0 = non-prepaid
TP_107 PPG flag Integer TEXT(1,R, ,’0’)
or non-prepaid. message
1 = prepaid message
1 byte
It indicates whether the message has flag
TP_108 PPG flag of charging 0 = flag not set Integer TEXT(1,R, ,’0’)
PPG Down Policy Applied.

1 = flag set

ASCII characters
TP_114 Name of Transmitter Interface Name of the transmitter interface String TEXT(40,L, ,’<unknown>’)
40 bytes
ASCII characters
TP_115 Name of Receiver Interface Name of the receiver interface String TEXT(40,L, ,’<unknown>’)
40 bytes
ASCII characters
TP_116 SMPP Service Type Service type field of the SMPP protocol String TEXT(10,L, ,’<unknown>’)
5 bytes
Service ID value from octet 1 of the billing Integer
TP_117 Service ID Integer TEXT(2)
identification parameter 2 bytes
ASCII characters
6-7 bytes
Billed party address TON and NPI from
Left delimiter 01
TP_118 Billable Party TON and NPI octets 11 and 12 of the billing identification String TEXT(7)
TON 1-2 bytes
parameter
NPI 2 bytes
Right delimiter C
Billed party address from octets 13 and ASCII characters
TP_119 Billable Party Address String TEXT(20)
further of the billing identification parameter 20 bytes
PSA transaction ID from octets 2-9 of the ASCII characters
TP_120 PSA Transaction ID String TEXT(8)
billing identification parameter 16 bytes
Message reference (identification linking all Integer
TP_121 SAR Message Reference Integer TEXT(2,R, ,’0’)
segments of a segmented message) 2 bytes
Total number of segments of a segmented Integer
TP_122 SAR Number of Segments Integer TEXT(1,R, ,’1’)
message 1 byte
Sequence number of an individual message Integer
TP_123 SAR Sequence Number Integer TEXT(2,R, ,’0’)
segment 1 byte
1 byte
The message was accepted and marked as
TP_128 AntiSpoof Flag 1 = flag set Integer TEXT(1,R, ,’0’)
spoofed.
0 = flag not set
TP_129 CDR_DYNAMIC_ALPHA _TON TON of the dynamic alpha 1 byte Integer TEXT(1,R, ,’0’)
TP_130 CDR_DYNAMIC_ALPHA _NPI NPI of the dynamic alpha 1 byte Integer TEXT(1,R, ,’0’)
Page 115 of 144

ISSUED
R3.0-10.09.B09

CDR_DYNAMIC_ALPHA
TP_131 ADDR of the dynamic alpha Up to 20 bytes String TEXT(20,R, ,’<unknown>’)
_ADDR
TP_132 CDR_OCOS Originator class of service 1-4 bytes Integer TEXT(1,R, ,’0’)
TP_133 CDR_TCOS Recipient class of service 1-4 bytes Integer TEXT(4„R, ,’0’)
CDR_BILLING Hexadecimal
TP_134 SMPP billing ID 2 bytes TEXT(2)
_IDENTIFICATION number

TP_135 CDR_BILLING_TRANS_ID Billing transaction ID String TEXT(32)
TP_140 CDR_MSG_ID Message ID Integer TEXT(20)
Page 116 of 144

ISSUED
R3.0-10.09.B09
3.3.4 SMPP parameter billing_identification
This chapter describes the format of the billing_identification parameter received via the SMPP protocol in a special use
case. This format is applied when the first octet is equal to 0x81. The following table shows how this parameter is decomposed
and how SDR fields are filled in.
Table 3.20: Structure of billing_identification for vendor ID equal to

10000001 (0x81)
Octet Value Meaning SDR field

0: Billing format
1000 0001 Vendor-specific value denoting this format -
tag
0000 0001 MO_COPY_SERVICE
0000 0010 MT_COPY_SERVICE
0000 0011 MT_DIVERT_SERVICE
1: Service ID 117
0000 0100 MT_WHITELIST
0000 0101 MT_BLACKLIST
0000 0110 MT_OOTO_SERVICE
2-9: Transaction
- Transaction identification 120
ID
xxxx xxx0 Subscriber is prepaid
107
10: Prepaid xxxx xxx1 Subscriber is postpaid
status xxxx xx0x Charge was successful
108
xxxx xx1x Charge was unsuccessful
11: TON - Billable party address TON
118
12: NPI - Billable party address NPI
13-33: Address - Billable party address MSISDN - octet string 119
3.4 SMSC V5 ASN.1 billing files
These records are binary encoded according to the ASN.1 Distinguished Encoding Rules (ASN.1-DER). This makes ASN.1
independent of any machine or platform.
Although billing files generated by MCO have the same (abstract) format as SMSC V5 billing files, the set of filled-in fields may
differ since these two products differ in the set of supported features.
Note
Please note that records produced by MCO and by SMSC V5 can also differ on the binary layer since SMSC V5 produces
billing records in ASN.1 Basic Encoding Rules (ASN.1-BER). That shall not be a problem for decoding tools since ASN.1
DER is a subset of the ASN.1 BER format. Option MCO3473_CDR_CODING_INDEF_LENGTH for SMSC V5 billing com-
patibility in sdr_conf.asn1_v5_compatibility table can be used to enable the compatibility with SMSC V5 billing
files. See Section 3.4.4 for details.
This stream is intended for recording in the submission phase and once a message is delivered. Use the CREATE_SDR(ASN_CDR)
action in the IN_MSG and FINAL_MSG SDR RBDL stages only.

MCO can produce two record types of ASN.1 records: CallDetailRecord for messages and NotificationRecord for
message receipts (notifications). To enable a record type, add the corresponding parent field (of the same name as the record type)
to configuration sdr_conf.streams[ASN_CDR].fields, where ASN_CDR should be replaced with the used ASN.1 stream
name. Please also note that feature MCO_SDR_ASN1_V5 should be enabled in license_conf.licenses for ASN.1 records to
be generated.
The content of individual fields is described in Table 3.21. Columns CDR and NR describe whether the field concerned can be
included in CallDetailRecord or NotificationRecord or both.
Important
Table 3.21 lists all available attributes in an alphabetic order with the exception of parent fields which are located in the
first two rows. Please note that unlike CSV streams, empty or zero-filled fields may not be sent even if they are specified
in configuration.
Table 3.21: SDR fields
Field name Description CDR NR

CallDetailRecord Parent field for a call detail record (used for messages). X
NotificationRecord Parent field for a notification record (used for notification). X
Billing identifier in the raw binary format. Not used for MO
billid X X
messages.
billidSMPP Billing identifier in the HEX format. Not used for MO messages. X X
Boolean fields indicating which service is used (different for CDR
boolSer X X
and NR). See Table 3.24 for CDR and Table 3.25 for NR.
callingLineId Originator address for MO messages and LASN for AO messages. X
The same as callingLineId , formatted according to
callingLineIdGSM [3GPP_23.040]. The length octet is represented by the ASN.1 X
length field octet.
cmReferenceNr Reference number of CM. Used only for segmented messages. X
consolidation Customer ID. X
This field indicates that a message is a reassembled concatenated
message if the field value is 0. In other cases, the field value is a
currentSegment X
sequence number of the current segment of a concatenated
message.
deferIndicator Indicates the presence of the message deferred period. X
deferPeriod Message deferred period (hours and minutes). X
deliveryAttempts Number of delivery attempts made. X X
Point code of the destination MSC, the MSC of the previous
destPointCode successful delivery or HLR. This field is absent if the message was X X
routed based on a GT or if the message is not MT.
E.164 address (a called party GT) of the MS serving MSC/SGSN. It
is present for GT-routed messages, e.g. for roaming or foreign
subscribers. The called party GT of the MS serving MSC/SGSN of
dgtiAddress X X
the previous successful delivery or the called party GT of the HLR
interrogation if the HLR did not return an MSC/SGSN address. The
structure is described in Table 3.23.
The same as dgtiAddress, formatted according to
dgtiAddressGSM [3GPP_23.040]. The length octet is represented by the ASN.1 X X
length field octet.


Identifies message importance level. The values are: 1 - High
importance X X
importance; 0 - Normal importance;
Message content size in octets; in case of a concatenated message
lengthOfMessage X X
the total message content size in octets.
logDate Date of record creation in format YYMMDD. X X
logTime Time of record creation in format HHMMSS. X X
messageID Unique message ID in the raw binary format. X X
Reference number (usually a cyclic counter) assigned to the
messageReference X X
message by the originating party.
Message delivery error code (sent only if an error occurs). For
msgError X X
possible values, see Table 3.11.
mtyp 0x11 for a message submission or 0x61 for a message log. X
Recipient of the notification. If the recipient of the notification is an
notifAddress X
LA, it contains its LASN. The structure is described in Table 3.23.
The same as notifAddress, formatted according to
notifAddressGSM [3GPP_23.040]. The length octet is represented by the ASN.1 X
length field octet.
Indicates whether a notification has been generated for this
notifIndicator X
message (ON) or not (OFF).
nser New services flags. See Table 3.26 for the structure. X X
E.164 address (a calling party GT) of the MS serving MSC/SGSN. It
is present for messages routed based on an originating GT, e.g. for
ogtiAddress X
roaming subscribers. Used only for MO messages. The structure is
described in Table 3.23.
The same as ogtiAddress, formatted according to
ogtiAddressGSM [3GPP_23.040]. The length octet is represented by the ASN.1 X
length field octet.
Recipient of the notification (the same as notifAddress of the
orglNotifAddress X
original message). The structure is described in Table 3.23.
The same as orglNotifAddress, formatted according to
orglNotifAddressGSM [3GPP_23.040]. The length octet is represented by the ASN.1 X
length field octet.
E.164 address (a calling party GT) of the MS serving MSC/SGSN
orglOgtiAddress X
from the original message. The structure is described in Table 3.23.
The same as orglOgtiAddress, formatted according to
orglOgtiAddressGSM [3GPP_23.040]. The length octet is represented by the ASN.1 X
length field octet.
origAddress from the original message. The structure is
orglOrigAddress X
The same as orglOrigAddress, formatted according to
orglOrigAddressGSM [3GPP_23.040]. The length octet is represented by the ASN.1 X
length field octet.
Point code of the first MSC in the message routing path
orglOrigPointCode X
(origPointCode) from the original message.
recipAddress from the original message. The structure is described
orglRecipAddress X
in Table 3.23.
The same as orglRecipAddress, formatted according to
orglRecipAddressGSM [3GPP_23.040]. The length octet is represented by the ASN.1 X
length field octet.
orglRecipIntlMobileSubId recipIntlMobileSubId from the original message. X


orglRecipNetworkType recipNetworkType from the original message. X
orglSubmitDate Submit date of the original message in format DDMMYY. X X
orglSubmitTime Submit time of the original message in format HHMMSS. X X
untranslOrigAddress from the original message. The structure is
orglUntranslOrigAddress X
The same as untranslOrigAddress, formatted according to [?].
orglUntranslOrigAddressGSM X
The length octet is represented by the ASN.1 length field octet.
untranslRecipAddress from the original message. The structure is
orglUntranslRecipAddress X
The same as untranslRecipAddress, formatted according to
orglUntranslRecipAddressGSM [3GPP_23.040]. The length octet is represented by the ASN.1 X
length field octet.
origAddress Originator’s number. The structure is described in Table 3.23. X
The same as origAddress, formatted according to
origAddressGSM [3GPP_23.040]. The length octet is represented by the ASN.1 X
length field octet.
Originator’s IMSI - present when received from the network or
origIntlMobileSubId X
obtained via a mobile-originated HLR interrogation.
origLASN Originator’s LASN. X X
origMIN Originator’s MIN. X
Originator’s network type. The only possible values are 1 (GSM)
origNetworkType X
and 3 (CDMA). Otherwise it is not sent.
Point code of the first MSC in the message routing path. Used only
origPointCode X
if the message is MO.
origSCAddress Originator’s service centre address. X
portNumber Port number of an inbound operation. X
ppPser Prepaid services flags. See Table 3.27 for the structure. X X
Indicates whether the priority is set for this message (ON) or not
prioIndicator X
(OFF).
The private data container that is attached to the message
privateContainer X X
(EXT_DATA).
rbdlFlags1 The lowest 32 bits of RBDL flags (1-32). X X
rbdlFlags2 The highest 32 bits of RBDL flags (33-64). X X
recipAddress Recipient’s number. The structure is described in Table 3.23. X
The same as recipAddress, formatted according to
recipAddressGSM [3GPP_23.040]. The length octet is represented by the ASN.1 X
length field octet.
Recipient’s LASN in the address structure format. The structure is
recipAltAddress X X
recipIntlMobileSubId Recipient’s IMSI. X X
recipLASN Recipient’s LASN. X X
recipMIN Recipient’s MIN. X
Recipient’s network type. The only possible values are 1 (GSM) and
recipNetworkType X X
3 (CDMA). Otherwise it is not sent.
segmentsTotal Total number of segments in a CM. X
Service type parameter can be used to indicate the SMS Application
serviceType X X
service associated with the message. Used for SMPP only.
smeReference Reference number assigned to the message by the originating party. X X
smsContentDcs Data coding scheme of the message. X X


smsContents Message text X X
status Message status. For possible values, see Table 3.22. X X
submitDate Date of the message submission in format YYMMDD. X X
submitTime Time of the message submission in format HHMMSS. X X
Date when the message was delivered or deleted in format
terminDate X X
YYMMDD.
Time when the message was delivered or deleted in format
terminTime X X
HHMMSS.
TP-DCS value as provided by the message originator. See
tpDCS X X
[3GPP_23038] for possible values.
Originator’s untranslated number. The structure is described in
untranslOrigAddress X
Table 3.23.
The same as untranslOrigAddress, formatted according to
untranslOrigAddressGSM [3GPP_23.040]. The length octet is represented by the ASN.1 X
length field octet.
Recipient’s untranslated address. The structure is described in
untranslRecipAddress X
Table 3.23.
The same as untranslRecipAddress, formatted according to
untranslRecipAddressGSM [3GPP_23.040]. The length octet is represented by the ASN.1 X
length field octet.
validityPeriod Message validity period (hours and minutes). X X
Table 3.22: Possible values of status field in ASN.1 and their mapping to
MSG_STATUS codes (see Table 3.12).
Code Value MSG_STATUS codes. Description

0x00 DELIVERED 0x04 The SM was successfully delivered.
0x01 EXPIRED 0x08 The SM validity period expired.
0x02 DELETED 0x07 The SM was deleted (e.g. by SMPP cancel_sm).
0x00, 0x02, 0x03,
0x04 SUBMITTED The submission process of an SM started.
0x05
0x07 UNDELIVERABLE 0x06, 0x0A Unsuccessful delivery attempt, permanent error.
0x08 PASSED_ON 0x09 The SM was successfully handed over.
0x09 REJECTED 0x01 The SM was rejected.
Note
The value of the Status field is also influenced by SMSC V5 compatibility option MCO3661_MSG_STATUS_DROP_IS
_DEL.
The values of the callingLineId and callingLineIdGSM fields are also influenced by the SMSC V5 compatibility
option MCO4615_EMPTY_MO_CALLINGLINEID.
Refer to [MCO_OMAN] for detailed information.

Table 3.23: ASN.1 address structure
Field name Description

ton Type of number
npi Numbering plan identification
pid Protocol identifier
msisdn Mobile Subscriber ISDN
msisdnutf8 Mobile Subscriber ISDN in the UTF-8 encoding
Important
The following tables contain SMSC V5.0 flag fields structures, however, most of these flags are not supported by MCO.
Such fields are described as "not supported".
Table 3.24: ASN.1 boolean service (boolser) structure in CallDetail-

Record
Field name Bit number Description

erarr 1 Not supported
transaction-mode 7 Not supported
umf 10 Not supported
fsg 20 Message was received via the FSG.
replace-if-present 24 Not supported
gateway-la 25 Not supported
Table 3.25: ASN.1 boolean services (boolser) structure in Notification-

Record

erarr 1 Not supported
umf 10 Not supported
replace-if-present 24 Not supported
gateway-la 25 Not supported
Table 3.26: ASN.1 new services structure (nser)

mrep 2 Not supported
deleted 3 Not supported
replaced 4 Not supported
lao 5 Originator of the message is a large account


lar 6 Recipient of the message is a large account
fwad 7 Not supported
fwad-cond 8 Not supported
clir 9 Originator address should be invisible at the recipient side
modified 11 Not supported
switched-fwad 13 Not supported
fwad-send 14 Not supported
trace-copy 17 Not supported
udhi 24 User data header is present.
del-by-operator 28 Not supported
Table 3.27: ASN.1 prepaid services (ppPser) structure

orig-pp 0 Originator of an SM is a prepaid user.
recip-pp 1 Recipient of an SM is a prepaid user.
orig-blocked 2 Not supported.
recip-blocked 3 Not supported
prim 4 Service was associated with this SM. (Originator and/or recipient is SMPP.)
charge-recip 5 Recipient is the charged party for Primary Service.
free 6 Service is free.
during-jam 7 Not supported
applied-pmgt 8 Not supported
charge_orig 9 Originator is the charged party for Primary Service.
bulk_match 10 Not supported
during-jam-orig 11 Not supported
during-jam-recip 12 Not supported
3.4.3 ASN.1 tag values
The following table maps ASN.1 fields to corresponding encoded ASN.1 tag values.
Table 3.28: ASN.1 tags CallDetailRecord
Tag value
Field name
(hexadecimal)
CallDetailrecord 30
origAddress A0
origAddress.ton 80
origAddress.npi 81
origAddress.pid 82

Tag value
Field name
(hexadecimal)
origAddress.msisdn 83
origAddress.msisdnutf8 84
origAddressGSM 81
recipAddress A2
recipAddress.ton 80
recipAddress.npi 81
recipAddress.pid 82
recipAddress.msisdn 83
recipAddress.msisdnutf8 84
recipAddressGSM 83
submitDate 84
submitTime 85
Status 86
terminDate 87
terminTime 88
lengthOfMessage 89
prioIndicator 8A
validityPeriod AB
validityPeriod.hours 80
validityPeriod.minutes 81
deferIndicator 8C
deferPeriod AD
deferPeriod.hours 80
deferPeriod.minutes 81
notifIndicator 8E
notifAddress AF
notifAddress.ton 80
notifAddress.npi 81
notifAddress.pid 82
notifAddress.msisdn 83
notifAddressGSM 90
Vsmscid 91
Vsmsctype 92
dgtiAddress B3
dgtiAddress.ton 80
dgtiAddress.npi 81
dgtiAddress.pid 82
dgtiAddress.msisdn 83
dgtiAddressGSM 94
destPointCode 95
ogtiAddress B6
ogtiAddress.ton 80
ogtiAddress.npi 81
ogtiAddress.pid 82
ogtiAddress.msisdn 83

Tag value
Field name
(hexadecimal)
ogtiAddressGSM 97
origPointCode 98
orglSubmitDate 99
orglSubmitTime 9A
transparentPid 9B
mesgReplyPath 9C
recipIntlMobileSubId 9D
callingLineId BE
callingLineId.ton 80
callingLineId.npi 81
callingLineId.pid 82
callingLineId.msisdn 83
callingLineIdGSM 9F1F
Consolidation 9F20
portNumber 9F21
Aser 9F22
Mser 9F23
Nser 9F24
Xser 9F25
origIntlMobileSubId 9F26
Billid 9F27
Lang 9F28
Cbat 9F29
ppPser 9F2A
ppAser 9F2B
ppAserDuringJam 9F2C
ppAserFree 9F2D
ppAserRecip 9F2E
smeReference 9F2F
smsContentDcs 9F30
smsContents 9F31
cmReferenceNr 9F32
currentSegment 9F33
segmentsTotal 9F34
textFormatting 9F35
bytesCompressedData 9F36
predefinedAnimations 9F37
userDefinedAnimations 9F38
predefinedSounds 9F39
userDefinedSounds 9F3A
blackWhitePictures 9F3B
standardWvg 9F3C
characterSizeWvg 9F3D
greyscalePictures 9F3E
colourPictures 9F3F

Tag value
Field name
(hexadecimal)
businessCards 9F40
calendarEntries 9F41
polyphonicMelodies 9F42
bit8PortNumberDest 9F43
bit16PortNumberDest 9F44
lmsgNrSeg 9F45
messageReference 9F46
boolSer 9F47
origLASN 9F48
recipLASN 9F49
origMsgID 9F4A
recipMsgID 9F4B
receiptDate 9F4C
receiptTime 9F4D
Isr 9F4E
recipAltAddress BF4F
recipAltAddress.ton 80
recipAltAddress.npi 81
recipAltAddress.pid 82
recipAltAddress.msisdn 83
generatedSegments 9F50
serviceType 9F51
deliveryAttempts 9F52
untranslOrigAddress BF53
untranslOrigAddress.ton 80
untranslOrigAddress.npi 81
untranslOrigAddress.pid 82
untranslOrigAddress.msisdn 83
untranslOrigAddressGSM 9F54
untranslRecipAddress BF55
untranslRecipAddress.ton 80
untranslRecipAddress.npi 81
untranslRecipAddress.pid 82
untranslRecipAddress.MSISD 83
untranslRecipAddressGSM 9F56
msgError 9F57
TpDCS 9F58
genericUrgencyLevel 9F59
ifaceUrgencyLevel 9F5A
teleserviceID 9F5B
origAddrGroup 9F5C
recipAddrGroup 9F5D
origNetworkType 9F5E
recipNetworkType 9F5F
origServicePrice BF60

Tag value
Field name
(hexadecimal)
origServicePrice.currency 80
origServicePrice.exponent 81
origServicePrice.value 82
recipServicePrice BF61
recipServicePrice.currency 80
recipServicePrice.exponent 81
recipServicePrice.value 82
cser 9F62
origSPBPStatus 9F63
recipSPBPStatus 9F64
billidSMPP 9F65
enumResult 9F66
dser 9F67
importance 9F68
forwAddress BF69
forwAddress.ton 80
forwAddress.npi 81
forwAddress.pid 82
forwAddress.msisdn 83
forwAddress.msisdnutf8 84
forwAddressGSM 9F6A
privateContainer 9F6B
rbdlFlags1 9F6C
rbdlFlags2 9F6D
origSCAddress BF6E
origSCAddress.ton 80
origSCAddress.npi 81
origSCAddress.pid 82
origSCAddress.msisdn 83
origSCAddress.msisdnutf8 84
idMNPdb 9F6F
origMIN 9F70
recipMIN 9F71
logDate 9F72
logTime 9F73
mtyp 9F74
presOrigAddress BF75
presOrigAddress.ton 80
presOrigAddress.npi 81
presOrigAddress.pid 82
presOrigAddress.msisdn 83
presOrigAddress.msisdnutf8 84
presOrigAddressGSM 9F76
presRecipAddress BF77
presRecipAddress.ton 80

Tag value
Field name
(hexadecimal)
presRecipAddress.npi 81
presRecipAddress.pid 82
presRecipAddress.msisdn 83
presRecipAddress.msisdnutf8 84
presRecipAddressGSM 9F78
messageID 9F79
applicationData 9F7A
Table 3.29: ASN.1 tags NotificationRecord
Tag value
Field name
(hexadecimal)
NotificationRecord 61
orglOrigAddress A0
orglOrigAddress.ton 80
orglOrigAddress.npi 81
orglOrigAddress.pid 82
orglOrigAddress.msisdn 83
orglOrigAddressGSM 81
orglRecipAddress A2
orglRecipAddress.ton 80
orglRecipAddress.npi 81
orglRecipAddress.pid 82
orglRecipAddress.msisdn 83
orglRecipAddressGSM 83
orglNotifAddress A4
orglNotifAddress.ton 80
orglNotifAddress.npi 81
orglNotifAddress.pid 82
orglNotifAddress.msisdn 83
orglNotifAddressGSM 85
submitDate 86
submitTime 87
orglSubmitDate 88
orglSubmitTime 89
status 8A
terminDate 8B
terminTime 8C
lengthOfMessage 8D
validityPeriod AE
validityPeriod.hours 80
validityPeriod.minutes 81
vsmscid 8F

Tag value
Field name
(hexadecimal)
vsmsctype 90
consolidation 91
billid 92
smeReference 93
smsContentDcs 94
smsContents 95
messageReference 96
recipLASN 97
origMsgID 98
isr 99
boolSer 9A
recipAltAddress BB
recipAltAddress.ton 80
recipAltAddress.npi 81
recipAltAddress.pid 82
recipAltAddress.msisdn 83
serviceType 9C
dgtiAddress BD
dgtiAddress.ton 80
dgtiAddress.npi 81
dgtiAddress.pid 82
dgtiAddress.msisdn 83
dgtiAddressGSM 9E
destPointCode 9F1F
orglOgtiAddress BF20
orglOgtiAddress.ton 80
orglOgtiAddress.npi 81
orglOgtiAddress.pid 82
orglOgtiAddress.msisdn 83
orglOgtiAddressGSM 9F21
orglOrigPointCode 9F22
deliveryAttempts 9F23
orglUntranslOrigAddress BF24
orglUntranslOrigAddress.ton 80
orglUntranslOrigAddress.npi 81
orglUntranslOrigAddress.pid 82
orglUntranslOrigAddress.msisdn 83
orglUntranslOrigAddressGSM 9F25
orglUntranslRecipAddress BF26
orglUntranslRecipAddress.ton 80
orglUntranslRecipAddress.npi 81
orglUntranslRecipAddress.pid 82
orglUntranslRecipAddress.msisdn 83
orglUntranslRecipAddressGSM 9F27
msgError 9F28

Tag value
Field name
(hexadecimal)
tpDCS 9F29
orglOrigAddrGroup 9F2A
orglRecipAddrGroup 9F2B
recipNetworkType 9F2C
orglRecipNetworkType 9F2D
recipIntlMobileSubId 9F2E
orglRecipIntlMobileSubId 9F2F
origServicePrice BF30
origServicePrice.currency 80
origServicePrice.exponent 81
origServicePrice.value 82
recipServicePrice BF31
recipServicePrice.currency 80
recipServicePrice.exponent 81
recipServicePrice.value 82
ppPser 9F32
ppAser 9F33
ppAserDuringJam 9F34
ppAserFree 9F35
origSPBPStatus 9F36
recipSPBPStatus 9F37
orglNotifDate 9F38
orglNotifTime 9F39
billidSMPP 9F3A
origLASN 9F3B
nser 9F3C
enumResult 9F3D
cser 9F3E
dser 9F3F
importance 9F40
rbdlFlags1 9F41
rbdlFlags2 9F42
orglOrigMIN 9F43
orglRecipMIN 9F44
logDate 9F45
logTime 9F46
ntyp 9F47
presOrigAddress BF48
presOrigAddress.ton 80
presOrigAddress.npi 81
presOrigAddress.pid 82
presOrigAddress.msisdn 83
presOrigAddress.msisdnutf8 84
presOrigAddressGSM 9F49
presRecipAddress BF4A

Tag value
Field name
(hexadecimal)
presRecipAddress.ton 80
presRecipAddress.npi 81
presRecipAddress.pid 82
presRecipAddress.msisdn 83
presRecipAddress.msisdnutf8 84
presRecipAddressGSM 9F4B
privateContainer 9F4C
messageID 9F4D
applicationData 9F4E
3.4.4 Compatibility with SMSC V5 ASN.1 CDRs
Behaviour of the ASN.1 billing can be fine tuned by switches in the sdr_conf.asn1_v5_compatibility cparam table. For
details, refer to section Charging in [MCO_OMAN].

4 SDR decoding
This chapter describes tooling available for SDR streams decoding.
4.1 CSV streams
The sdr_decode.py tool is available for decoding of streams in the CSV format. The csv_decode alias starts the script with
the default configuration specified in the /opt/mco/etc/csv_decode_cfg.py file. It is handful to specify a CSV format
separator and delimiter character used by the system there.
The following is an example of an SDR file containing a single record for an AO-AT message. The first line contains a header with
the name of fields contained in the file. Parentheses suffixed to the field name contain a formatting string if specified; that can help
a decoding tool to understand the data, e.g. whether an address field contains all parts (TON, NPI, address) or only an address
string (see B_ADDR(a) in the example below) etc. The second line contains the actual record data of an individual message.
'RecordNr','LOG_TIME()','SP_ID()','MSG_TYPE()','MSG_ID()','MSG_PARENT_ID()','MSG_MODE()',' ←-
MSG_STATUS()','REJECT_REASON()','REJECT_METHOD()','SM_ERROR()','SUBMIT_TIME()',' ←-
EXPIRY_TIME()','DELIVERY_TIME()','DONE_TIME()','PRIORITY()','NOTIF_REQ()','NR_DEL_ATT() ←-
','NR_DEL_SUB_ATT()','UDH_SRC_PORT()','UDH_DST_PORT()','A_ADDR()','A_UADDR()','A_TADDR() ←-
','B_ADDR(a)','B_UADDR()','B_TADDR()','A_IMSI()','B_IMSI()','MAP_A_IMSI()','MAP_B_IMSI() ←-
','A_AIM_NAME()','B_AIM_NAME()','A_NETWORK_TYPE()','B_NETWORK_TYPE()','S_CGPA()','D_CDPA ←-
()','D_CGPA()','A_HLR_CGPA()','A_HLR_MAP_ERROR()','B_HLR_MAP_ERROR()','A_SC()','B_SC() ←-
','MAP_ERROR()','MAP_CAUSE()','A_MSC()','A_SGSN()','B_MSC()','B_SGSN()','SM_TEXT()',' ←-
SM_TEXT_LENGTH()','SM_CONTENT()','SM_CONTENT_SIZE()','SM_CONTENT_ENCODING()','SM_UDH() ←-
','SM_UDH_SIZE()','SM_UDH_SEG()','SM_UDH_SEG_SIZE()','UDH_MASK()','UDH_MASK_SEG()',' ←-
SM_SEGMENT_MAX()','SM_SEGMENT_CURRENT()','SM_SEGMENT_REF()','A_COS()','B_COS()','S_COS() ←-
','D_COS()','A_DOMAIN()','B_DOMAIN()','S_DOMAIN()','D_DOMAIN()','MSG_FLAGS()',' ←-
DETECT_FLAGS()','DETECT_FLAGS_SEG()','RBDL_FLAGS()','RBDL_FLAGS_SEG()','BILLING_DATA() ←-
','BILLING_DATA_SEG()'
'0','1404371110','5','1','FCCAA75F8002E461907900000200B00D ←-
','','1','4','','','','1404371111','1404457511','1404371110','1404371110','0','00','1','1' ←-
,'','','1.1.6','1.1.6','1.1.6','1.1.666113','1.1.666113','1.1.666113','','','','',' ←-
SMPP_TEST_T','SMPP_TEST_R','3','3','','','','','','','','','','','','','','','Message ←-
2/10','14','4D65737361676520322F31305C0A00','14','5','','','','','0000000000000000', ←-
'0000000000000000','','','','0000000000000000','0000000000000000','0000000000000000' ←-
,'0000000000000000','255','','255','','0000000000000000','0000000000000000', ←-
'0000000000000000','0000000000000000','0000000000000000','0000000000000000','0000000000000000' ←-
The tool decodes the file in the following way:

$ csv_decode CSVSM_rnd-vm-18-68_20140703070346Z.csv
------------------ Record from line: 2 ------------------
RecordNr: 0
LOG_TIME(): 1404371110
SP_ID(): 5
MSG_TYPE(): 1
MSG_ID(): FCCAA75F8002E461907900000200B00D
MSG_PARENT_ID(): N/A
MSG_MODE(): 1
MSG_STATUS(): 4
REJECT_REASON(): N/A

REJECT_METHOD(): N/A
SM_ERROR(): N/A
SUBMIT_TIME(): 1404371111
EXPIRY_TIME(): 1404457511
DELIVERY_TIME(): 1404371110
DONE_TIME(): 1404371110
PRIORITY(): 0
NOTIF_REQ(): 00
NR_DEL_ATT(): 1
NR_DEL_SUB_ATT(): 1
UDH_SRC_PORT(): N/A
UDH_DST_PORT(): N/A
A_ADDR(): 1.1.6
A_UADDR(): 1.1.6
A_TADDR(): 1.1.6
B_ADDR(): 666113
B_UADDR(): 1.1.666113
B_TADDR(): 1.1.666113
A_IMSI(): N/A
B_IMSI(): N/A
MAP_A_IMSI(): N/A
MAP_B_IMSI(): N/A
A_AIM_NAME(): SMPP_TEST_T
B_AIM_NAME(): SMPP_TEST_R
A_NETWORK_TYPE(): 3
B_NETWORK_TYPE(): 3
S_CGPA(): N/A
D_CDPA(): N/A
D_CGPA(): N/A
A_HLR_CGPA(): N/A
A_HLR_MAP_ERROR(): N/A
B_HLR_MAP_ERROR(): N/A
A_SC(): N/A
B_SC(): N/A
MAP_ERROR(): N/A
MAP_CAUSE(): N/A
A_MSC(): N/A
A_SGSN(): N/A
B_MSC(): N/A
B_SGSN(): N/A
SM_TEXT(): Message 2/10\
SM_TEXT_LENGTH(): 14
SM_CONTENT(): 4D65737361676520322F31305C0A00
SM_CONTENT_SIZE(): 14
SM_CONTENT_ENCODING(): 5
SM_UDH(): N/A
SM_UDH_SIZE(): N/A
SM_UDH_SEG(): N/A
SM_UDH_SEG_SIZE(): N/A
UDH_MASK(): 0000000000000000
UDH_MASK_SEG(): 0000000000000000
SM_SEGMENT_MAX(): N/A
SM_SEGMENT_CURRENT(): N/A
SM_SEGMENT_REF(): N/A
A_COS(): 0000000000000000
B_COS(): 0000000000000000
S_COS(): 0000000000000000
D_COS(): 0000000000000000
A_DOMAIN(): 255
B_DOMAIN(): N/A
S_DOMAIN(): 255

D_DOMAIN(): N/A
MSG_FLAGS(): 0000000000000000
DETECT_FLAGS(): 0000000000000000
DETECT_FLAGS_SEG(): 0000000000000000
RBDL_FLAGS(): 0000000000000000
RBDL_FLAGS_SEG(): 0000000000000000
BILLING_DATA(): 0000000000000000
BILLING_DATA_SEG(): 0000000000000000
All options of the tool can be displayed with the following command:
$ csv_decode -h
Usage:
$ csv_decode.py -f[file] <csv_file_name> [-hdr <line_num>] [-s[sep] <separator_char>] [-d[ ←-
el] <delimiter_char>] [-l[ist] <field_name> ..] [-p[res]] [-g[rep] <text>] [-r[ec] < ←-
filter>] -h[elp]
-h - show this help
-f - list of CSV files to be decoded, when omited stdin is read
-hdr - line number where header with field names is located, when not specified the ←-
first line in the file is used
-s - char separating individual fields in a record, when not specified the "," char ←-
is used
-d - char delimiting field values, when not specified the "'" char is used
-l - list of fields to be displayed, when not specified all fields are displayed
-p - outputs non-empty fields only
-g - displays only records which decoded and formatted output contains <text>
-r - displays only records matching with filter specified by <filter>, see examples ←-
below
-c - python config file <csv_decode_cfg.py>
-k - RSA private key in PEM format in file <private_key_file_name>, pass phrase for ←-
key will be prompted
Examples:
$ csv_decode.py -f csvsm.csv
$ tail -f abcd.csv | csv_decode.py
$ csv_decode.py -f csvsm.csv -l A_ADDR B_ADDR
$ csv_decode.py -f csvsm.csv -g infoMoSpoofedGT
$ csv_decode.py -f csvsm.csv -r 'FIELD("SM_ERROR"))=="21"'
$ csv_decode.py -f csvsm.csv -r 'FIELD("A_ADDR")=="1.1.120640980670" and FIELD(" ←-
B_ADDR")=="1.1.6661138"'
There is 'csv_decode' alias which is the same as 'csv_decode.py -c /opt/mco/etc/ ←-

csv_decode_cfg.py -f'
Specify default settings, like delimeter and separator, of csv_decode.py in /opt/mco/etc/ ←-
csv_decode_cfg.py
4.2 ASN.1 streams
The asn1_decode.py tool is available for decoding of streams in the ASN.1 format. The asn1_decode alias can be used
for this tool.
Note
Make sure that you have NGP quaterly patches installed to have this tool working properly.

$ asn1_decode LOGSRV00_CDR_FILE.20170112171618Z.csv.cur
================== LOGSRV00_CDR_FILE.20170112171618Z.csv.cur - START - ==================
------------------ Record from offset: 0 ------------------
CallDetailRecord>
origAddress>
ton : 1 (international)
npi : 1 (telephone)
pid : 0 (plmn)
msisdn : 31654630101
msisdnUTF8 : 31654630101
origAddressGSM : 911356640301F1
recipAddress>
npi : 1 (telephone)
pid : 0 (plmn)
msisdn : 31654630100
msisdnUTF8 : 31654630100
recipAddressGSM : 911356640301F0
submitDate : 2017-01-12
submitTime : 17:17:20
status : 4 (submitted)
lengthOfMessage : 50
prioIndicator : False
validityPeriod>
hours : 24
minutes : 0
deferIndicator : False
deferPeriod>
hours : 0
minutes : 0
notifIndicator : False
notifAddress>
npi : 1 (telephone)
pid : 0 (plmn)
msisdn : 31654630101
msisdnUTF8 : 31654630101
notifAddressGSM : 911356640301F1
dgtiAddress>
npi : 1 (telephone)
pid : 0 (plmn)
msisdn : 31987654321
ogtiAddress>
npi : 1 (telephone)
pid : 0 (plmn)
msisdn : 98111111101
ogtiAddressGSM : 918911111101F1
origPointCode : 301
orglSubmitDate : 2017-01-12
orglSubmitTime : 17:17:20
callingLineId>
npi : 1 (telephone)
pid : 0 (plmn)
msisdn : 31654630101
msisdnUTF8 : 31654630101
callingLineIdGSM : 911356640301F1
smeReference : 0

smsContentDcs : GSM
smsContents : 2017-01-12 17:17:19: Testing message from MO to ←-
MT
messageReference : 66FF71F9EAD8E6618EF000000000A550
boolSer : []
untranslOrigAddress>
npi : 1 (telephone)
pid : 0 (plmn)
msisdn : 31654630101
untranslOrigAddressGSM : 911356640301F1
untranslRecipAddress>
npi : 1 (telephone)
pid : 0 (plmn)
msisdn : 31654630100
untranslRecipAddressGSM : 911356640301F0
tpDCS : 0
origNetworkType : 1 (gsm)
recipNetworkType : 1 (gsm)
rbdlFlags1 : []
rbdlFlags2 : []
logDate : 2017-01-12
logTime : 17:17:20
mtyp : 17 (subs)
messageID : 66FF71F9EAD8E6618EF000000000A550
------------------ Record from offset: 524 ------------------

NotificationRecord>
orglOrigAddress>
npi : 1 (telephone)
pid : 0 (plmn)
msisdn : 31654630101
msisdnUTF8 : 31654630101
orglOrigAddressGSM : 911356640301F1
orglRecipAddress>
npi : 1 (telephone)
pid : 0 (plmn)
msisdn : 31654630100
msisdnUTF8 : 31654630100
orglRecipAddressGSM : 911356640301F0
orglNotifAddress>
npi : 1 (telephone)
pid : 0 (plmn)
msisdn : 31654630101
msisdnUTF8 : 31654630101
orglNotifAddressGSM : 911356640301F1
submitDate : 2017-01-12
submitTime : 17:17:55
orglSubmitDate : 2017-01-12
orglSubmitTime : 17:17:55
status : 0 (delivered)
terminDate : 2017-01-12
terminTime : 17:17:55
lengthOfMessage : 144
validityPeriod>
hours : 24
minutes : 0

smeReference : 0
smsContentDcs : GSM
smsContents : id:3EFE1C0EEBD8E6618EF000000000A550 sub:001 dlvrd ←-
:001 submit date:1701121717 done date:1701121717 stat:DELIVRD err:000 text ←-
:2017-01-12 17:17:54:
messageReference : 3267AB0EEBD8E661A69A000000007F47
boolSer : []
dgtiAddress>
npi : 1 (telephone)
pid : 0 (plmn)
msisdn : 98111111101
deliveryAttempts : 1
orglUntranslOrigAddress>
npi : 1 (telephone)
pid : 0 (plmn)
msisdn : 31654630101
orglUntranslOrigAddressGSM : 911356640301F1
orglUntranslRecipAddress>
npi : 1 (telephone)
pid : 0 (plmn)
msisdn : 31654630100
orglUntranslRecipAddressGSM : 911356640301F0
tpDCS : 0
recipNetworkType : 1 (gsm)
orglRecipNetworkType : 1 (gsm)
recipIntlMobileSubId : 43615460031001F0
rbdlFlags1 : []
rbdlFlags2 : []
logDate : 2017-01-12
logTime : 17:17:55
messageID : 3267AB0EEBD8E661A69A000000007F47
=================== LOGSRV00_CDR_FILE.20170112171618Z.csv.cur - END - ===================
All options of the tool can be displayed with the following command:
$ asn1_decode -h
usage: asn1_decode.py [-h] [-r CONDS] [-l [FIELD [FIELD ...]]] [-g [GREP]]
[-5] [-f [FILENAME [FILENAME ...]]]
[FILENAME [FILENAME ...]]
Decode ASN.1 SDRs.
positional arguments:
FILENAME Name of files to be decoded, "-" or missed for stdin
optional arguments:
-h, --help show this help message and exit
-r CONDS, --rec CONDS
String containing conditions like
FIELD(fieldName)=="value". Supported operations are
"==" (equal), "!=" (not equal), ">", "<", ">=", "<="
(integer comparasion), "=~" (regex matches) and "!~"
(not matches). Multiple conditions can be used with
"and" and "or" logical operators. For example
FIELD(x)=="vx" and FIELD(y)=="vy". Boolean flags can
be used in conditions in the following way:
FIELD(nser.clir)==true

-l [FIELD [FIELD ...]], --list [FIELD [FIELD ...]]
List of fields to be displayed, when not specified all
fields are displayed
-g [GREP], --grep [GREP]
Display only records containing GREP pattern in text
representation of any field. For example, text
representation means that enumerated fields can be
searchedby it's text not only by it's numeric value.
-5, --smscv5 Use with switch for decoding SMSC v.5 ASN.1 billing
files (interprets messageID as text string)
-f [FILENAME [FILENAME ...]], --files [FILENAME [FILENAME ...]]
Name of files to be decoded, "-" or missed for stdin
There is an 'asn1_decode' alias which is the same as 'asn1_decode.py -f'

Acronyms
ADM Acision Dialogue Manager, currently Xtend
ADMI Acision Diameter Messaging Interface

An interface between messaging servers and application servers that provide advanced business logic.
ADT (Flexible) Address Translation
AF Application Function
AO Application-originated
APA Application Port Addressing
ASCII American Standard Code for Information Interchange

This is the most common format for the text of SMs to be sent in. In an ASCII file, each alphabetic, numeric, or special
character is represented with a 7-bit binary number (a string of seven 0s or 1s). 128 possible characters are defined.
ASN.1 Abstract Syntax Notation Nr.1
AT Application-terminated
BER Basic Encoding Rules
CDF Charging Data Function
CDR Call Detail Record

A CDR contains necessary information to bill customers for message transactions. Often also called Service Detail Record
(SDR).
CDMA Code Division Multiple Access
CdPA Called Party Address
CgPA Calling Party Address
CGF Charging Gateway Function
CML Configuration and Management Line

A command line providing configuration and management interface to the product running in a cluster.
CSV Comma-Separated Value

A CSV record is a type of the SDR format.
CTF Charging Trigger Function

D
DCS Data Coding Scheme

DCS is a message field defined in GSM 03.40. It indicates how the message was coded and whether it supports foreign
characters. Examples of types of coding available include ASCII Unicode, EBCDIC etc.
DER Distinguished Encoding Rules
EIR Equipment Identity Register
ESME External Short Message Entity

An entity outside the mobile network that can send messages to, or receive messages from an SMSC.
FDA First Delivery Attempt
GMT Greenwich Mean Time
GPRS General Packed Radio Service
GSM Global System for Mobile communications (formerly Groupe Speciale Mobile)
A set of standards for digital mobile communications developed by European Telecommunications Standards Institute
(ETSI).
GT Global Title
HLR Home Location Register

Repository of GSM customers provisioning data and current location register.
IE Information Element
IMEI International Mobile Equipment Identity
IMSI International Mobile Subscriber Identity

This is the main identity number of a subscriber within the GSM mobile network.
ISO International Standards Organisation

L
LA Large Account
LASN Large Account Short Number
MAP Mobile Application Part
MCO Message Controller
MO Mobile-originated
MO-FW-SM MO-Forward-Short-Message
MAP MO-Forward-Short-Message operation as defined in 3GPP 29.002
MSC Mobile services Switching Centre

This is the interface between the Base Station Subsystem and the fixed network. It performs the necessary functions in
order to handle the calls to and from the mobile stations.
MSISDN Mobile Station International Subscriber Directory Number

The mobile station international ISDN number identifies an MS as an ISDN terminal. It is used to route calls from any
international telecommunications network (PSTN, ISDN, GSM-PLMN) to the MS.
MT Mobile-terminated
MT-FW-SM MT-Forward-Short-Message
MAP MT-Forward-Short-Message operation as defined in 3GPP 29.002
MVNO Mobile Virtual Network Operator
NPI Numbering Plan Indicator
OSI Open Systems Interconnection
PC Point Code
PDU Protocol Data Unit

Information that is delivered as a unit among peer entities of a network and that may contain control information, address
information or data.
PID Protocol Identifier
PLMN Public Land Mobile Network

A PLMN is a network that is established and operated by an administration or by a recognised operating agency for the
specific purpose of providing land mobile telecommunications services to the public.

R
RI Routing Indicator
RBDL Rule Based Decision Logic

The RBDL is a configuration principle that enables an operator to determine numerous aspects of message behaviour in a
flexible way.
SC Service Centre
A synonym for SMSC used in the 3GPP TS 23.040 specification.
SCCP Signalling Connection Control Part

The routing protocol for SS7 networks.
SDR Service Detail Record

Records that allow tracking messages and services applied to them as well as related signalling in a network. Used for
billing and statistics.
SGSN Serving GPRS Support/Service Node
SIP Session Initiation Protocol
SLC Service Logic Component
SM Short Message
SME Short Message Entity

Any source or sink of short messages. The entity is either inside or outside the Public Land Mobile Network (PLMN) and
can send and/or receive short messages, for example, mobile stations, pagers, DTMF telephones.
SMSC Short Message Service Centre

A Mavenir short messaging product. The SMSC system encompasses all of the software and hardware required to send
short messages (SMs) from one Short Message Entity (SME) to another.
SMPP Short Message Peer-to-Peer
SNMP Simple Network Management Protocol

SNMP is an Internet-standard protocol for managing devices on IP networks. Devices that typically support SNMP include
routers, switches, servers, workstations, printers, modem tracks, and more. It is used mostly in network management
systems to monitor network-attached devices for conditions that warrant administrative attention.
SP Service Point
SRI Send-Routing-Info
SSN Sub-system Number

T
TCAP Transaction Capabilities Application Part
TON Type of Number

This makes up part of the MSISDN/MIN.
TP Telepath
TP Transfer Protocol
TPDU Transfer Protocol Data Unit
TT Translation Type
UDH User Data Header

Each SM that is part of a concatenated SM begins with a UDH block that describes information necessary for delivery and
reassembly.
UTC Coordinated Universal Timecode

UTC is the primary time standard by which the world regulates clocks and time.
VLR Visitor Location Register
VMSC Visited MSC

The visited MSC (V-MSC) is the MSC where a customer is currently located. The VLR associated with this MSC has the
subscriber’s data in it.

Bibliography
[3GPP_23.040] 3GPP TS 23.040 V11.4.0 R11: Technical realization of the Short Message Service (SMS)
[MCO_DO] Mavenir Message Controller Documentation Overview
[MCO_GLS_prepaid] Mavenir Message Controller Guidelines: Development of Prepaid Plug-in
[MCO_OMAN] Mavenir Message Controller Operator and Configuration Manual


Message Controller R3.0-10.09.B09: Billing Interface Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Message Controller R3.0-10.09.B09: Billing Interface Manual

Uploaded by

Copyright:

Available Formats

Message Controller R3.0-10.09.

Billing Interface Manual

Document Version: 1.0

1.1 Charging events concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.3 SDR formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.4 SDR stream types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.4.1 Native stream types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.5 SDR stream configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Native SDR streams 6

2.1 Field types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.3 CSV_SM stream type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.4 CSV_MAP stream type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.5 CSV_SIP stream type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.7 Field details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.1 MCO 2.3 CSV billing files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

3.1.2 MAP SDR stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

3.1.3 SM SDR stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

3.1.4 Parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

3.1.4.2 Values of SM parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

3.1.4.3 Values of information flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

3.1.4.4 Values of extended information flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

3.1.4.6 Used structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

3.1.4.7 Network types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

3.1.5 Message ID mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

3.2.1 Stream applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

3.2.2 Optional special attribute fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

3.2.3 Custom/extension attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

3.2.5 Supported fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

3.3 Telepath fixed-length billing files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

3.3.1 Stream applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

3.3.3 Supported fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

3.3.4 SMPP parameter billing_identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

3.4 SMSC V5 ASN.1 billing files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

3.4.2 Supported fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

3.4.3 ASN.1 tag values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

3.4.4 Compatibility with SMSC V5 ASN.1 CDRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

4 SDR decoding 132

4.2 ASN.1 streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

1.1 3GPP charging reference model (TS 32.240) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.2 MCO charging triggers overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2.1 SDR encryption procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.2 SDR decryption procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.1 SDR stream field types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.2 Custom (extdata) field types mapping on SDR stream types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.4 CSV_SM SDR stream type fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.5 CSV_MAP SDR Stream Type Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.6 CSV_SIP SDR stream type fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.8 Normalized TON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.9 Normalized NPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.10 Service points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.12 Message types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.13 Message modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.14 Message statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.16 Reject methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2.18 Network types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.20 MAP errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2.21 MAP causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.22 Message text encodings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

2.24 Requested notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

2.25 Class of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

2.26 Message flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

2.28 Billing data flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

2.29 Signal Operation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43