Om 1 411 2231 814P1.17.15

411-2231-814P1
GSM NSS/UMTS UCC

DMS-MSC/Call Server
OM Reference Manual Vol. 1
GSM17/UMTS03 Standard 17.15 October 2004

test
GSM NSS/UMTS UCC
DMS-MSC/Call Server
Document number: 411-2231-814P1

Product release: GSM17/UMTS03
Document version: Standard 17.15
Date: October 2004
Copyright Country of printing Confidentiality Legal statements Trademarks
Copyright © 1995–2004 Nortel Networks, All Rights Reserved

Originated in the United States of America
NORTEL NETWORKS CONFIDENTIAL
The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees
with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree
of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in
writing by Nortel Networks, the holder is granted no rights to use the information contained herein.
Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as
progress in engineering and manufacturing may warrant.
* Nortel Networks, the Nortel Networks logo, the Globemark HOW the WORLD SHARES IDEAS, and Unified Networks are
trademarks of Nortel Networks. DMS, DMS-HLR, DMS-MSC, MAP, and SuperNode are trademarks of Nortel Networks. GSM is a
trademark of GSM MOU Association.
Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.
ii
Nortel Networks Confidential Copyright © 1995–2004 Nortel Networks
411-2231-814P1 Standard 17.15 October 2004

iii
Publication history
This section contains a high level listing of updates and changes to this
product documentation for this release cycle. If a detailed list of all changes
for the GSM15 release is required, see *Nortel Networks Technical
Publication (NTP) GSM NSS/UMTS UCC DMS-MSC/Call Server Software
Delta (411-2231-199).
Note: While this document is one volume of a three volume set

describing the OM groups that are specific to the DMS-MSC/Call Server
for GSM, the following Publication History is applicable to the three
volume set as a whole.
GSM NSS/UMTS UCC DMS-MSC/Call Server OM Reference Manual Vol. 1 GSM17/UMTS03

iv Publication history
October 2004
NSS17/UMTS03, Standard, 17.15.
September 2004
August 2004
NSS17/UMTS03, Preliminary, 17.14. For review.
April 2004
NSS17/UMTS03, Preliminary, 17.13.
April 2004
NSS17/UMTS03, Draft, 17.12. For review.
March 2004
NSS17/UMTS03, Draft, 17.11. For review.
February 2004
February 2004
November 2003
NSS17/UMTS03, Preliminary Phase 5, 17.08. For review.
October 2003
NSS17/UMTS03, Preliminary Phase 4, 17.07. For review.
September 2003
NSS17/UMTS03, Preliminary Phase 4, 17.06.
September 2003
July 2003
June 2003
April 2003
GSM17/UMTS03, Draft, 17.02. The following release changes have been made
to the document:
• Modified OM groups:
— EXT

Publication history v
February 2003
GSM17/UMTS03, Draft, 17.01. The following release changes have been made
to the document:
• New OM groups added:
— DCAPSFCF
— DCAPSFRF
— DCPSFCFE
— DP3SFCFE
— DCPSFRFE
— CAMMCSI
— DCSIERR
— DP3SFRFE
— BICNANNC
— BICNTONE
• Changed OM groups:
— CAPCALLP
— CAPTRAF
— CAPCTAS
— CAPCCTAS
— GELIDOMG
— CAPOCSI2
— CAPTCSI2
• Obsoleted OM groups that have been replaced:
— CAPSFCF
— CAPSFRF
— CAPSFCFE
— CAPSFRFE
• Deleted OM groups:
— CMLCALLP
— C2CALLP
— CMLCTAS
— GCAP2CS
— GCAP2SI

vi Publication history
— GCAP2ECS
— GCAP2ESI
March 2003
GSM16/UMTS03, Standard, 16.04.
January 2003
GSM16, Preliminary, 16.03. Solution of CRs.
October 2002
GSM16, Preliminary, 16.02. This preliminary release is created for Global
System for Mobile Communications (*GSM) to document Digital Multiplex
Systems-Mobile-services Switching Center (*DMS-MSC) Operational
Measurements (OMs). This manual is split into three volumes.
July 2002
GSM16, draft, 16.01. The following information has been changed:
• various cosmetic improvements
• various error corrections
The following OM groups have been deleted:
• OCMLEDP
• TCMLEDP
The following OM groups have been changed:
• RCH
The following OM groups have been added:
• ASSFTRAF
• CAPSFAF
• CAPAFRF
• CAPSFAFE
• CAPAFRFE
• CMOSCSI
• CMOSCMU
• CMOSCSI2
• CMOSCMU2
• CMOSCSI3
• CMOSCMU3
• CMOSCSI4

Publication history vii
• CMOSCMU4
• CMOSCSI5
• CMOSCMU5
• CAPOCSI
• CAPOCSI2
• CAPTCSI
• CAPTCSI2
• CAPDCSI
• CAPDCSI2
• CAPNCSI
• CAPNCSI2
• CAPOEDP
• CAPTEDP
• CAPERR
• CAPCALLP
• CMLTOCML
• CAPTRAF
• CAPCTAS
• CAPCCTAS
• CAPSFCF
• CAPSFRF
• CAPSFCFE
• CAPSFRFE
• GSMOMTRK
• HCAMLAIH
• HROUTING
• M3UA
• MSCCDSUC
• MSCLORG
• MSCLORMU

viii Publication history
July 2002
GSM15, standard, 15.03. The following information has been changed:
• various cosmetic improvements
• various error corrections
The following OM groups have been deleted:

• MSCPCONF
• MSCTRCMMU
• MSTRCMMU
April 2002
GSM15 15.02 - This preliminary release is created for Global System for
Mobile Communications (*GSM) to document Digital Multiplex Systems-
Mobile-services Switching Center (*DMS-MSC) Operational Measurements
(OMs). This manual is split into three volumes.
July 2001
GSM13 Revision 13.03- This Standard release is created for Global System
for Mobile Communications (*GSM) PCS1900 to document Digital
Multiplex Systems-Mobile-services Switching Center (*DMS-MSC)
Operational Measurements (OMs) for Release GSM13. This manual is split
into three volumes.
The following OM groups were added to this release:

• DSPRMAN
• ECANRMAN
• G7SCCP
• G7SCCPCO
• G7SCCPCX
• GECTOMGG
• GSMPLERRS
• GSMPLUSG
• MSCPCONF
• PRERTEAB
• TRK2

Publication history ix
March 2001
GSM13 Revision 13.02- This Preliminary release is created for Global
System for Mobile Communications (*GSM) PCS1900 to document Digital
Operational Measurements (OMs) for Release GSM13.
The following OM groups were modified to this release:

• XASTAT
September 2000
GSM13 Revision 13.01- This Draft release is created for Global System for
Mobile Communications (*GSM) PCS1900 to document Digital Multiplex
Measurements (OMs) for Release GSM13.
The following OM groups were added to this release:

• GELIDOMG
• GELIDOMU
• GLMSMOMG
• GLMSMOMU
• GMGIFMMU
• GPLOMGR
• GPLOMMU
• GPSLOMGR
• GPSLOMMU
• GSLROMGR
• GSLROMMU
• GSMGSITF
• GSMSCOMG
• GSMSCOMU
• MNPOM
• XASTAT
July 2000
GSM12. Revision 12.02- This Preliminary release is created for Global

x Publication history
April 2000
GSM12. Revision 12.01-This Draft release is created for Global System for
February 2000
GSM11. Revision 11.02– This Preliminary release is created for Global
The following OM groups was added for this release:

• GMCHMMU
• GMCH2MMU
• GMFREMMU
• GMENGTMU
• GMMMGTMU
• GMSMGTMU
• GMSMSMMU
• GMSSMMO
• GMSS2MMU
• GMTRRMMU
• ETMMIMMU
• ETCHIMMU
• ETSMSIMU
• ETSMGIMU
• ETFRIMMU
• ETEQIMMU
• ETMMRMMU
• ETSSIMMU
• ETCHRMMU
• ETSMSRMU
• ETSMGRMU
• ETFRRMMU

Publication history xi
• ETEQRMMU
• ETSIMMU
• ETSIRMMU
• GSBARMMU
• VLR2MMU
• VLR3MMU
• VLR4MMU
• VLR5MMU
• MSCSMSMU
• MSCHO2MU
• EXHOCAMU
• MSCCP3MU
• GMMLTRMU
• GMEANTMU
• GMEAN2MU
• CLINTMMU
• MSCHOMMU
• VLRMMU
• MSCTRMMU
• MSCCRMMU
• GINAPMMU
• GINAP2MMU
• GINAP3MMU
• CPRPL2SZ
• CSRPL1SZ
• CSRPL3SZ
• CSRPL4SZ
• CSRPL5SZ
• FXLGAXBK
• FLRGAXBK
• FMDMAXBK
• FSMLAXBK

xii Publication history
• FHUGAXBK
• CPMMU
• CB2MMU
October 1999
GSM11. Revision 11.01 – This Draft release is created for Global System for
The following OM groups have been modified for this release:

• GINAP2
The following OM groups have been added for this release:

• ACRJ
• GMAPCH2
• ISUPUSAG
• MSCPCONF
• RCH
• UBZOMGRP
February 1999
GSM10. Revision 10.02 – This Preliminary release is created for Global
System for Mobile Communications (GSM)PCS1900 to document Digital
Multiplex Systems-Mobile-services Switching Center (DMS-MSC)

• CIDBOM
• FRDCNTL
• VLR5
The following OM groups have been added for this release:

• C7SERVER
• C7SROUTE
• GMAPTR

Publication history xiii
December 1998
GSM09. Revision 09.03 – This standard release is created for Global System
for Mobile Communications (GSM)PCS1900 to document Digital Multiplex
Systems-Mobile-services Switching Center (DMS-MSC) Operational
The following OM groups have been modified in this release:

• GINAP2
• GMAPCH2
• GMAPMMGT
• GSMECT
The following OM groups have been added to this release:

• ECTFAIL
• ECTINVKS
September 1998
GSM10. Revision 10.01 – This Draft release is created for Global System for
Mobile Communications (GSM)PCS1900 to document Digital Multiplex

• PECTXHST
• TMSIRP
• TMSIRNP
These OM groups have been modified in this release:

• VLR2
• FRDCNTL
August 1998
GSM09. Revision - This Preliminary release is created for Global System for

• CR_COUNT
• CE_COUNT

xiv Publication history
• ETSISIR
• GSMECT
• MSCAOCTC
March 1998
GSM09. Revision - This draft release is created for Global System for Mobile
Communications (GSM)PCS1900 to document Digital Multiplex Systems-
Mobile-services Switching Center (DMS-MSC) Operational Measurements
(OMs) for Release GSM09.

• FRCDNTL
• GECTOMGP
• GSMUSSD
November 1997
GSM08. Revision 08.02 - This standard release is created for Global System
for Mobile Communications (GSM) to document Digital Multiplex Systems-
August 1997
GSM08. Revision 08.01 - This preliminary release is created for Global
System for Mobile Communications (GSM) to document Digital Multiplex
The changes for this release are as follows:

• A Standard Index list is added to this NTP.
• The following OM groups have been modified for this release:
— AOCSS
— C7SCCPCO
— ETSIMMI
— ETSISMGR
— ETSISMSI
— ETSISSR
— EXHOCA
— GINAP2

Publication history xv
— GMAPCH2
— GMAPSMGT
— GMAPSMS
— GMAPSS
— GMEANTM
— GMEANTM2
— GSMLUSAG
— MSCCFSS
— MSCCNAM
— MSCCP
— MSCCP2
— MSCCP3
— MSCCPSRV
— MSCH0
— MSCH02
— MSCLIDBQ
— MSCMPTSS
— MSCSMS
— NPACGGRP
— NPSUM
— OFZ
— PETCUT
— VLR2
— VLR3
• The following OM groups have been added for this release:
— VLR5
May 1997
GSM08. Revision - This draft release is created for Global System for Mobile
Communications (GSM)PCS1900 to document Digital Multiplex Systems-

xvi Publication history

• GINAP2
• MSCCALLR
• MSCCNAM
• MSCEXTSS
• MSCLIDBQ
• NPACGGRP
• NPSUM

• EXT
• IN1SUM
January 1997
GSM07. Revision - This standard release is created for Global System for
October 1996
GSM07. Revision - This preliminary release is created for Global System for

• CUGSS
• EXHOCA
• GACODE
• GCBK
• GINAP
• GMEANTM
• GMEANTM2
• GMMLTRN
• GPRP
• GSRVCBAR
• GTASOM

Publication history xvii
• MSCHO2
• MSCRLT

• EXT
• MSCSMS
• VLR2
June 1996
March 1996
GSM06. Revision - This preliminary release is created for Global System for

• BRSTAT
• CALLINT
• CLLO
• GMAPCH2
• GMAPSS2
• IN1SUMM
• INTSEP
• MSCCP3
• OFFBDIN
• OFZ
• TFACGGRAP
• TRMTFR3
• TFSUM
• VLR2
• VLR3
• VLR4

xviii Publication history

• MSCSMS
• EXT
• MSCCPSRV
• MSCHO
• EXT
• GSMAPSMS
• GMAPSMGT
• MSCHO
• TRK
December 1995

• AOCSS
• CLISS
• ETSICHI
• ETSIEQI
• ETSIEQR
• ETSIFRI
• ETSIFRR
• ETSIMMI
• ETSIMMR
• ETSISMGI
• ETSISMGR
• ETSISMSI
• ETSISMSR
• ETSISSI
• MSCCPSRV
• MSCDRV

Publication history xix
• MSCTRACE
• PETCUT

• GMAPFREC
• GMAPSMGT
• VLR
April 1995

• RMTCU2
• GMAPSS
The following OM group has been added to this release:

• MSCMPTSS (Mobile Switching Services Center Multi-Party
Supplementary Service)
• Global System for Mobile Communications (GSM) 22312231

xx Publication history

xxi
Contents 1
About this document xxiii
Operational measurements system overview 1-1
OM groups: A-D 2-1
OM groups: E 3-1
OM groups: F-GE 4-1
Appendix: DMS-100 base OM groups A-1
List of figures
Figure 61-1 TEXT_FORMAT_CODES for DMS-MSC/Call Server 3-180
Figure 62-1 SCCP Class 2 Message Types 4-42
Figure 62-2 SCCP Class 2 Message Types 4-43
Figure 62-3 SCCP Class 2 Message Type 4-48
Figure 62-4 SCCP Class 2 Message Type 4-48
List of tables
Table 1-1 DMS-MSC/Call Server OM groups 1-4
Table 10-1 SCCP Class 2 Message Types 2-35
Table 10-2 SCCP Class 2 Message Types 2-37
Table 10-3 SCCP Class 2 Message Type 2-41
Table 10-4 SCCP Class 2 Message Type 2-42

xxii Contents

xxiii
About this document 1

This NTP defines specific Operational Measurements (OM) groups and
registers that apply only to the Digital Multiplex Systems Mobile-services
Switching Center/Call Server (DMS-MSC/Call Server) for Global System for
Mobile Communications (GSM).
The OM groups which are common to the *DMS-100 family (also referred to
as “base OM groups”) are discussed in “Appendix: DMS-100 base OM
groups”.
In addition, if an OM group that is associated with a Network Element (NE) is

not found in this NTP, you can find it in the applicable NTP, as follows:
• For Base OMs, refer to the following Base/Telecom and DMS-100 NTPs:
— 411-3001-814, Wireless Networks Base/Telecom Operational
Measurements Reference Manual
— 297-8021-814, North American DMS-100 Operational Measurements
Reference Manual
— 297-2621-814, Digital Switching Systems UCS DMS-250
Operational Measurements Reference Manual
• For Billing OMs produced by the CEM and for additional key
performance indicators (formulas/correlations) produced by the CEM,
refer to the following NTP:
— 411-8111-503, Circuit Core Network OA&M, vol. 1 and vol. 2
Notice of design intent and enhancement 1

The design intent is reflected in the level of detail in the Nortel Networks
Technical Publications (NTP) regarding the following elements:
• Logs
• Parameters
• Data Schema
• Tables
• OMs

xxiv About this document
Starting at GSM13, enhanced attributes were developed to define and

document these GSM elements. However, for those elements introduced prior
to GSM13, the user will find a minimalist level of documentation to represent
these elements. This level of documentation reflects the original design
intent.
Handling merged OM groups 1

For customers who are using the CEM Graphical User Interface (GUI) to
view OM groups, the groups that are visible (MSC or HLR OM groups) can
also be mapped to the corresponding DMS OM groups (including Base/
Telecom groups).

About this document xxv
Table 1-1 presents the DMS OM groups that are merged with MSC or HLR
OM groups and are displayed on the CEM GUI:
Table 1-1- Mapping DMS OM groups that are merged with MSC or HLR OM groups
Groups displayed on CEM DMS OM Groups
C7HSLAL C7HSLAL1,C7HSLAL2
C7LINK C7LINK1,C7LINK2,C7LINK3,C
7LINK4
C7LPP C7LPP2
C7ROUTE C7ROUTE2
CAPDCSI CAPDCSI2
CAPNCSI CAPNCSI2
CAPOCSI CAPOCSI2
CAPTCSI CAPTCSI2
CP CP2
CPMMU CP2MMU
CMOSCMU CMOSCMU2,CMOSCMU3,CM
OSCMU4,CMOSCMU5
CMOSCSI CMOSCSI2,CMOSCSI3,CMOS
CSI4,CMOSCSI5
GHLRADM GHLRADM2,GHLRADM3
GHLRMMGT HCISSOPS,HOPTMMGT,HVLR
SMGT
GINAP GINAP2,GINAP3
GINAPMMU GINAP2MU,GINAP3MU
GLCSOMG GLCSOMG2,GLCSOMG3
GLCSOMU GLCSOMU2,GLCSOMU3
GMAPCH GMAPCH2
GMAPSS GMAPSS2
GMCHMMU GMCH2MMU

xxvi About this document
Table 1-1- Mapping DMS OM groups that are merged with MSC or HLR OM groups
Groups displayed on CEM DMS OM Groups
GMEANTM GMEANTM2
GMEANTMU GMEAN2MU
GMSSMMU GMSS2MMU
HCMLMPT HCMLMPT2
HLRCAMEL HLRCAML2
HO2G2GMU H2G2G2MU
HO2GTO2G HO2GT2G2
MSCCP MSCCP2,MSCCP3
MSCHO MSCHO2
MSCHOMMU MSCHO2MU
OFZ OFZ2
TRK TRNK2,gsmomtrk
TRMTCM TRMTCM2
TRMTCU TRMTCU2,TRMTCU3
TRMTFR TRMTFR2,TRMTFR3
VLR VLR2,VLR4,VLR5
VLRMMU VLR2MMU,VLR3MMU,VLR4M
MU,VLR5MMU,VLR6MMU
Audience for this document 1

This publication is intended for persons involved in the engineering,
administration, operation, or maintenance of the DMS-MSC/Call Server.
Organization of this document 1

This document is Volume 1 of a three volume set describing the OM groups
that are specific to the DMS-MSC/Call Server for GSM. The OM groups are
arranged in alphabetical order across the three volumes.

About this document xxvii
This document describes the OM groups whose names begin with “A”
through those whose names begin with “GE”. The OM groups whose names
fall after “GE” alphabetically, are described in Volumes 2 and 3.
This document is organized as follows:

• Chapter 1, “Operational measurements system overview” provides an
introduction to the DMS-MSC/Call Server’s Operational Measurements
system.
• Chapter 2, “OM groups: A-D” describes, in alphabetical order, the OM
groups whose names begin with “A” through those whose names begin
with “D”.
• Chapter 3, “OM groups: E” describes, in alphabetical order, the OM
groups whose names begin with “E”.
• Chapter 4, “OM groups: F-GE” describes, in alphabetical order, the OM
groups whose names begin with “F” through those whose names begin
with “GE”.
• Appendix , “Appendix: DMS-100 base OM groups” discusses the OM
groups which are common to the DMS-100 family.
Note: In some cases in this three volume set, the OM groups are not
given in strict alphabetical order. This minor deviation from alphabetical
order is done in order to place related OM groups together, as well as to
present OM groups in a logical sequence. For example, the OM group
CP2MMU is described after CPMMU, because CP2MMU is a
continuation of CPMMU.
Software release applicability 1

Nortel Networks (Nortel) software releases for the Wireless product are
developed and identified by the product lines. GSM product lines software is
identified by the letters GSM and a 2-digit number, such as GSM16,
signifying the first release in the SM software stream.
This publication is applicable to the DMS-MSC Family offices that have the
GSM NSS16/UCC03 UCC software release. Unless this publication is
revised, it also applies to offices that have software releases greater than GSM
NSS16/UCC03 UCC.
UCC03/GSM16 Product CM Loads 1

Before GSM05, software loads were package-based loads. GSM05 was the
first DMS-MSC Product CM Load (PCL). A PCL is composed of layers of
software, or Deliverable Release Units (DRUs). The GSM NSS16/UCC03
UCC PCL is composed of BASE16, CSP18, SHR18, SP17, and the GSM
NSS16/UCC03 UCC.

xxviii About this document
For more information about the GSM16/UCC03 PCLs and the functional
groups contained in it, refer to GSM NSS/UMTS UCC DMS-MSC/Call Server
Software Delta (411-2231-199).
Related documents 1
Some publications of the DMS-100 Family contain information that may
relate to the subjects in this publication. For a current listing of DMS-100
NTPs, refer to DMS-10 and DMS-100 Product Documentation Directory
(297-8991-001).
Indication of hypertext links 1

Hypertext links in this document are indicated in blue. If viewing a PDF
version of this document, click on the blue text to jump to the associated
section or page.

1-1
Operational measurements system

overview 1
What are Operational Measurements? 1
The Operational Measurements (OM) system provides the operating
company with switch performance measurements, traffic measurements, and
service data for the Digital Multiplex Systems Mobile-services Switching
Center/Call Server (DMS-MSC/Call Server). System engineers use OM
records to ensure that the DMS-MSC/Call Server operates at its full potential
and optimum efficiency.
Operational Measurements are broken down into specific OM groups and

their associated registers. Each OM group applies to some aspect of call
processing.
OMs provide information regarding the following:

• system performance
• grade of service being offered
• connecting facilities
• performance
• traffic levels of various elements internal to and connected to the system
The OM system records events that occur within the DMS-MSC/Call Server.
Each time a call is initiated, handed off, or terminated, different call
processing events occur. The results of these events eventually are recorded
in registers that are a part of the data store.
The OM system supports two types of counts:

• peg counts, which maintain a count of specified events
• usage counts, which are collected by periodic sampling/scanning and
provide a measure of the cumulative duration during which a specified
condition holds or during which a resource is in a specified state, such as
busy, idle, or unavailable

1-2 Operational measurements system overview
Each peg register can hold a range of values from 0 to 65 535. When the
count in a register exceeds its design limit of 65 535, its extension register
increments by a count of 1 while the basic register clears. Thus, an actual
event count of 65 536 would show a count of 1 in the extension register and 0
in the basic register. When the actual event count reached 131 072 the
extension register would increment again and show a count of 2, and the basic
register would clear again and show a count of 0.
Because extension registers are exactly what their name implies - an

extension to a register - their software and behavior are essentially the same
as the registers that they extend. For this reason, detailed explanations of
individual extension registers are neither necessary nor provided.
OM system background 1
The basic operation of the OM subsystem consists of the pegging and
scanning of operational measurements that occur during what is called the
transfer period. These data are collected into a set of active registers. At the
end of a transfer period, the active data is assigned to a set of holding
registers, and the active registers are cleared.
DMS scheduling activities are established by using a set of DMS

Maintenance and Administrative Position (MAP) Command Interpreter (CI)
commands and by manipulating a series of data tables. The technician can
organize various OM groups into OM accumulation classes and arrange them
so that OM data reports can be sent to designated output devices periodically.
The OM system takes care of OM register transfer, accumulation, and reporting,

as follows:
• OM transfer copies measurement data from active registers to holding
registers.
• OM accumulation adds the data in the holding registers to the
accumulating registers over a specific period of time that is selected by
the switching equipment technician.
• OM reporting presents OM data to the technician, journal file, or printer,
either periodically or on demand.
Because it is likely that another count may occur during the copying process,
OM data cannot be copied directly to an output process. Therefore, once
every 15 or 30 minutes (as defined by the switching equipment technician) a
transfer of all active registers to a corresponding holding register takes place.
Data in the holding register is added to the accumulating register over a
period of time as specified by the technician.
The holding data may be accumulated into a set of accumulating registers that
are set up when the technician defines OM classes using the DMS MAP CI

command OMCLASS. To display instantaneous counts for OMs, the holding

registers (as opposed to accumulating registers) should be directed to the
output device.
The technician can specify whether an OM group’s holding registers are

added to the accumulating registers upon completion of a transfer period. The
technician can also specify the accumulation time for an OM class. Thus,
transfer of holding data depends on how the OM group has been assigned to
an accumulation class and whether the transfer period falls within the
specified accumulation time.
Depending upon datafill in the reporting tables OPRT, OMTAPE, and

OMREPORT, scheduled OM reporting can also take place upon completion
of a transfer period. Datafill for these tables is described in the DMS-100
Family Customer Data Schema.
DMS scheduling activities are established through a set of MAPCI

commands and the manipulation of data tables. The technician can organize
various OM groups into OM accumulation classes and arrange them so that
OM data reports can be sent to designated output devices periodically. For
more detailed information on the current operation of the OM system, refer to
the DMS-100 Family Basic Administration Procedures.
An OM is a measurement tool, not a monitoring tool. The alarm system tables

ALARMTAB and OMTHRESH, also described in the DMS-100 Family
Customer Data Schema, allow monitoring of OM register values against
specific threshold values.
DMS-MSC/Call Server OM groups 1

The DMS-MSC/Call Server OMs measure traffic on the following interfaces:
• C-Interface - the interface between the DMS-MSC/Call Server and the
DMS-HLR
• D-Interface - the interface between the DMS-HLR and the Visitor
Location Register (VLR)
• E-Interface - the interface between DMS-MSC/Call Servers
• F-Interface - the interface to the Equipment Identity Register (EIR)
• G-Interface - the interface between VLRs in separate MSC/Call Servers
• H-Interface - the interface to a Short Message Service Centre (SM-SC)
• Administrative Interface to the DMS-HLR database, for a subscriber’s
data entry or change performed by the administrator
OMs also provide statistics that reflect the performance of DMS-MSC/Call

Server transactions, including the number of transaction requests sent (or

received) by the DMS-MSC/Call Server that are returned (or return) a Result
component. For example, a count is maintained for the number of Update
Location requests that are returned Result components, indicating a
successful Update Location transaction. In addition, statistics are provided
about the state of the system, such as the number of home PLMN subscribers
who are currently registered in a particular VLR database.
The DMS-MSC/Call Server OM groups which are described in this document

are summarized in Table 1-1.
Table 1-1
DMS-MSC/Call Server OM groups
Group name Group name (expanded) Description

(acronym)
ACRJ Anonymous Call Rejection provides an insight of the usage of the

ACRJ feature
ANN Announcements provides information on traffic for recorded

announcement machines
AOCSS GSM MSC Advice of Charge counts AOC attempts
ASUFBUS ASU Fbus messaging data displays number of octets transmitted and
measurements received on each Fbus port.
ASUMEMUT ASU memory utilization displays Data and Program store

information for an ASU.
BILLING Billing collect measurements on impact of

automatic call disconnect events
BRSTAT BRISC Occupancy Status provides statistics on CPU utilization for

SuperNode offices using BRISC
C7GTLNK SCCP global title OMs per link keeps track of global title related OMs on a
per link basis and the number of gtts
performed, the number that failed because
of no translation for address, no translation
for address nature and hop counter
violation.
—sheet 1 of 12—

Table 1-1
DMS-MSC/Call Server OM groups (continued)

(acronym)
C7GWSCCP CCS7 INTL. GW SCCP measures the performance and usage of

the CCS7 SCCP. It was created to
accomodate the 3 new registers associated
with international gateway SCCP. There is
insufficent room in group C7SCCP.
C7LPP stores LPP information related to the

INTER/INTRA-frame traffic and the size of
the messages going through the CCS7
Link. The OM group is created because
there is no existing OM group storing OM
data per frame. This OM group applies to
both LPP, MS and ELPP in STP04.
C7MTP C7 Message Transfer Part provides information on performance and

failures of Message Signal Units (MSUs) at
a Signal Transfer Point (STP).
C7MTPRES MTP Restart Operation counts the number of Partial, Full,

Measurement Adjacent, and Unexpected TRM
procedures occurred in the previous hour.
C7ROUTER CCS7 Router captures operational information about a

CCS7 Router. The Router receives
messages from other CCS7 peripherals
and performs the routing function on these
messages. The OMs will track the number
of messages and bytes processed by the
Router, as well as the number of times and
the amount of time which the Router was
out of service. In future they will also track
the high water marks of messages per
second received in the Router from various
sources, messages discarded due to
congestion, and the number of times and
amount of time when the Router was
congested. These measurements can be
used to determine if the Router is operating
within its capacity and to give an indication
of its workload during the OM period.
CAPCALLP CAMEL Call Processing for O- measures the events related to CAMEL call
CSI, TCSI, and Hotline processing.
—sheet 2 of 12—

Table 1-1

(acronym)
CAPCCTAS Specific CAMEL Call Type measures the call events between CAMEL
Analysis subscriber and UNICOM mobile subscriber.
CAPCTAS CAMEL Call Type Analysis measures call attempt and call answer in
four kinds of Call Type and two kinds of
CAMEL call failure.
CAPTRAF CAMEL Traffic for O-CSI, T-CSI, a usage counter group measuring CAMEL
and Hotline call traffic.
provides two regular time intervals for

usage registers: 100 seconds and 10
seconds.
C2CALLP CAMEL subscriber calls CAMEL provides statistics for calls from one
subscriber Call Processing CAMEL subscriber to another CAMEL
subscriber
C7SROUTE CCS7 Server Routing records the actions of the message router
on the LIU7 peripherals.
CALLINT Call Interception gathers metrics on the resource usage of

call interception
CF6P Six-port conference bridge Note: This section presents a brief

measurements overview of the OM group, CF6P, and a list
of registers. For more detailed information
on OM group, CF6P, refer to NTP 297-
8051-814, DMS-100 Family Advanced
Business Services Operational
Measurements Reference Manual Volume
1 of 5 OM Groups AABS to CNDB.
provides information on the use of a six-

port conference circuit.
CIDBOM Call Interception Database provides service monitoring and keeps

track of the number of Call Monitoring
targets in Call Interception Database
(CIDB) and the number of parallel calls
invoked by a given target
—sheet 3 of 12—

Table 1-1

(acronym)
CLINTMMU Call Interception on the MMU gathers metrics on the resource usage of
call interception (that is, three-port
conference bridges) and error conditions
CLISS Calling Line Identification gathers metrics on CLIP and CLIR

Supplementary Services
CLOSS Calling Line Identification gathers metrics on COLP and COLR

Supplementary Services
CMLCALLP CAMEL Call Processing SSP CAMEL call measurement of call

processing. It covers calls from one
CAMEL subscriber to another CAMEL
subscriber.
CMLCTAS CAMEL Call Type Analysis This group is defined and reserved for
implementation in the future.
This group measures call attempt and call

answer in four kinds of Call Type and two
kinds of CAMEL call failure.
CMLTRAF CAMEL Call Traffic provides usage measurement of traffic for

CAMEL calls
CPADPRBK CPIPP Address Pair Block displays the per-node counts
CPMMU CP MMU provides count of call processing activity

per MMU
CP2MMU CP MMU Group 2 provides further counts of call processing

activity per MMU
CPRPL2SZ Call Recording Stream Primary monitors the use of extension blocks
Recording Unit Pool 2 Size
CRDBOM Call Reference Database provides service monitoring and keeps

track of the number of Call Reference in
Call Reference Database (CRDB) and the
number of Call Elements in Call Element
Database (CEDB)
CSRPL1SZ Call Recording Stream monitors the use of extension blocks

Secondary Recording Unit Pool
1 Size
—sheet 4 of 12—

Table 1-1

(acronym)

3 Size

4 Size

5 Size
CUGSS Closed User Group gathers statistical information

Supplementary Service
DAISGEN provides general information about the

DUTL's operation.
DCAPSFCF Internal IP related CAP measures the successful CAP operations

operations (SCF--SSF) for related to Internal IP for D_CSI, which are
D_CSI involved in relay scenario, interacting
between SCF and SSF.
DCAPSFRF Internal IP related CAP measures the successful CAP operations

operations (SSF--SRF) for related to Internal IP for D_CSI, which are
D_CSI involved in relay scenario, interacting
between SSF and SRF.
DCPSFCFE Internal IP related error in measures the failure related to Internal IP

relaying (SCF--SSF) for D_CSI CAP operations for D_CSI between SCF
and SSF.
DP3SFCFE Internal IP related error in measures the error/failure related to

relaying (SCF--SSF) for Internal IP CAP operations for Proprietary
Proprietary DP3 DP3 between SCF and SSF.
DP3SFRFE Internal IP related error in measures the failure related to Internal IP

relaying (SSF--SRF) for CAP operations for Proprietary DP3
Proprietary DP3 between SSF and Internal IP.
DCPSFRFE Internal IP related error in measure the failure related to Internal IP

relaying (SCF--SRF) for D-CSI CAP operations for D_CSI between SSF
and Internal IP.
—sheet 5 of 12—

Table 1-1

(acronym)
DRM Distributed Record Manager track sthe number of application records,

blocks of records written to disk, and the
number of file rotations.
DSPRMAN Digital Signal Processor used primarily to check capacity.

Resource module Management
ECANRMAN Echo Canceller Resource measures echo canceller resource events

Management and usage statistics on the SPM
EIUETHER Ethernet Interface Unit allows access to traffic information at the

ETHERnet Ethernet protocol level. The information
given by this group of OMs include the total
counts of incoming and outgoing packets
and bytes at the Ethernet interface in a
longword format. The counts are
accumulated over the OM transfer period.
This group of OMs can be used for traffic
measurements of EIU.
EMLPPSS enhanced Multi-Level gathers information on the eMLPP

Precedence and Preemption supplementary service for each call
(eMLPP) Supplementary
Services (EMLPPSS)
ETCHIMMU ETSI Call Handling Dialogue For a dialogue initiator, ETCHIMMU

Initiator on the MMU measures the number of fall backs to and
from the Call Handling related application
context versions.
ETCHRMMU ETSI Call Handling Dialogue For a dialogue responder, ETCHRMMU

Responder on the MMUs measures the number of fall backs to and
from the Call Handling related application
context versions.
ETEQIMMU ETSI Equipment Management For a dialogue initiator, ETEQIMMU

Dialogue Initiator on the MMU measures the number of fall backs to and
from the Equipment Management related
application context versions.
ETEQRMMU ETSI Equipment Management For a dialogue responder, ETEQRMMU

Dialogue Responder on the measures the number of fall backs to and
MMU from the Equipment Management related
—sheet 6 of 12—

Table 1-1

(acronym)
ETFRIMMU ETSI Fault Recovery Dialogue For a dialogue initiator, ETFRIMMU

Initiator on the MMU measures the number of fall backs to and
from the Fault Recovery related application
context versions.
ETFRRMMU ETSI Fault Recovery Dialogue For a dialogue responder, ETFRRMMU

Responder on the MMU measures the number of fall backs to and
from the Fault Recovery related application
context versions.
ETMMIMMU ETSI Mobility Management For a dialogue initiator, ETMMIMMU

from the Mobility Management related
ETMMRMMU ETSI Mobility Management For a dialogue responder, ETMMRMMU

MMU from the Mobility Management related
ETSICHI ETSI Call Handling Dialogue measures fallbacks from Call Handling
Initiator application
ETSICHR ETSI Call Handling Dialogue measures fallbacks from Call Handling
Responder application
ETSIEQI ETSI Equipment Management measures fallbacks from Equipment

Dialogue Initiator Management application
ETSIEQR ETSI Equipment Management measures fallbacks from Equipment

Dialogue Responder Management application
ETSIFRI ETSI Fault Recovery Dialogue measures fallbacks from Fault Recovery
Initiator application
ETSIFRR ETSI Fault Recovery Dialogue measures fallbacks from Fault Recovery
Responder application
ETSIIMMU ETSI Subscriber Info Initiator AC measures subscriber information on MMUs

OMs on MMUs
ETSIMMI ETSI Mobility Management measures fallbacks from Mobility

—sheet 7 of 12—

Table 1-1

(acronym)
ETSIMMR ETSI Mobility Management measures fallbacks from Mobility

ETSIRMMU ETSI Subscriber Information measures the number of fall backs from the
Dialogue Responder on the Subscriber Information related application
MMU context versions and the number of fall
backs to the Subscriber Information related
application context versions on the MMUs
ETSISIR ETSI Subscriber Information measures the number of fall backs from the
Dialogue Responder Subscriber Information related application
context versions and the number of fall
backs to the Subscriber Information related
application context versions
ETSISMGI ETSI Subscriber Management measures fallbacks from Subscriber

ETSISMGR ETSI Subscriber Management measures fallbacks from Subscriber

ETSISMSI ETSI Short Message Service measures fallbacks from Short Message
Dialogue Initiator Services application
ETSISMSR ETSI Short Message Service measures fallbacks from Short Message
Dialogue Responder Services application
ETSISSI ETSI Supplementary Services measures fallbacks from Supplementary

Dialogue Initiator Services application
ETSISSR ETSI Supplementary Services measures fallbacks from Supplementary

Dialogue Responder Services application
ETSMGIMU ETSI Subscriber Management For a dialogue initiator, ETSMGIMU

from the Subscriber Management related
application context versions per MMU.
ETSMGRMU ETSI Subscriber Management The GSM Mobile Application Part

Dialogue Responder on the Subscriber Management group contains
MMU the registers for operations handling
subscriber data such as Insert Subscriber
Data, Delete Subscriber Data, and Send
Parameters per MMU.
—sheet 8 of 12—

Table 1-1

(acronym)
ETSMSIMU ETSI Short Message Service For a dialogue initiator, ETSMSIMU

Dialogue Initiator on the MMU measures the number of fallbacks to and
from the Short Message Services related
ETSMSRMU ETSI Short Message Service For a dialogue responder, ETSMSRMU

MMU from the Short Messages Services related
ETSSIMMU ETSI Supplementary Services For a dialogue initiator, ETSSIMMU

from the Supplementary Services related
application context versions and the
number of fall backs to the Supplementary
Services related application context
versions per MMU.
ETSSRMMU ETSI Supplementary Services For a dialogue responder, ETSSRMMU

MMU from the Supplementary Services related
application context versions and the
number of fall backs to the Supplementary
Services related application context
versions per MMU.
EVGCS Emergency Voice Group Call counts the number of Emergency VGCS
Service calls
EXHOCA MSC External Handover Cause measures activities related to external

handover cause reasons
EXHOCAMU MSC External Handover Cause measures activities related to external

on the MMU handover cause reasons per MMU
EXT Extension Blocks provides information about the usage of

extension blocks
FHUGAXBK Feature Processing Framework provides information about the usage of

Huge Auxiliary Blocks extension blocks
FLRGAXBK Extension Blocks provides information about the usage of

extension blocks
—sheet 9 of 12—

Table 1-1

(acronym)
FMDMAXBK Feature Processing Framework provides information about the usage of

Medium Auxiliary Blocks extension blocks
FPDEVICE File Processor Storage Device counts the number of times that Each File
Activity Counts Processor storage device has entered
various states as well as some usage
indicators specifying device activity. These
registers can indicate the frequency of
some error conditions by recording the
frequency of corresponding state changes.
FPFMSGS FPF Messages OMs provides information about the usage of

extension blocks
FPXLMSGB FPF Extra Large Message provides information about the usage of
Blocks extension blocks
FRDCNTL Fraud Control provides service monitoring related to

supplementary services fraud control
applications
FSMLAXBK Feature Processing Framework monitors the use of extension blocks

Small Auxiliary Blocks
FTROM created as the platform for feature data

block (FDB) high water marks and seizures
as separated by application type.
provides information to assist in switch

resource engineering. It is recommended
that these OMs be used only for that
purpose.
FXLGAXBK Feature Processing Framework monitors the use of extension blocks

Large Auxiliary Blocks
G7SCCP GSM CSS7 Signaling displays the per-node counts for the CM
Connection Control Part and LIU7s involved in the performance of
the CCS7 SCCP
—sheet 10 of 12—

Table 1-1

(acronym)
G7SCCPCO GSM CSS7 SCCP Connection measures the number of messages

Oriented received and sent using the SCCP class 2
connection-oriented group of messages
and displays the per-node counts for the
CM and LIU7s involved
G7SCCPX GSM CSS7 SCCP Extended provides information on the performance

Services and use of extended unitdata and extended
unitdata service (XUDT/XUDTS) messages
GACODE GSM Account Code measures the number of account code

calls
GCAP2CS GSM CAMEL Application Part monitors the amount of successful CAMEL
Phase 2 Application Part (CAP) operations involved
in a relay scenario between the Service
Control Function (SCF) and the Service
Switching Function (SSF)
GCAP2ECS GSM CAMEL Application Part monitors the amount of failed CAP
Phase 2 Error in Replaying operations (error or reject messages)
(SCF -- SSF) between the SCF and SSF, when the SSF
relays the message between the SCF and
SRF
GCAP2ESI GSM CAMEL Application Part monitors error and reject messages
Phase 2 Error in Replaying between the SSP and the IP
(SSF -- SRF)
GCAP2SI GSM CAMEL Application Part monitors the amount of successful CAP
Phase 2 (SSF -- SRF) operations, which are involved in a relay
scenario, interacting between SSF and
SRF
GCBK GSM Code Blocking measures the number of calls blocked and
passed by specific Network Management
control of type CBk
GCISBXBK GSM CI Sub Extension Block displays the per-node counts
GELIDOMG GSM Emergency Services keeps track of the call scenarios that are
Location Information Delivery used for the location services E911
OM Group functionality

Table 1-1

(acronym)
GELIDOMU GSM Emergency Location keeps track of the call scenarios per MMU
Identification per MMU that are used for the location services E911
functionality
GSMOMTRK GSM OM Trunk measures the incoming and outgoing traffic

for two-way European Telecommunications
Standards Institute (ETSI) ISDN User Part
(ISUP) and ETSI Primary rate interface
(PRI) trunks.
Existing operational measurement groups that apply to DMS-MSC/Call

Server
Existing OMs are those Operational Measurements that are not unique to the
DMS-MSC/Call Server but rather are common to the *DMS-100 family. For
a discussion of these OMs, refer to “Appendix: DMS-100 base OM groups”.
Correlated operational measurement groups that apply to DMS-MSC/Call

Server
Correlated OMs are those Operational Measurements that do not exist on the
switch and are fully defined in the UMTS OMC-S Element Manager OA&M
Guide for the UMTS Family.


OM groups: A-D 2-1
OM groups: A-D 2
This chapter describes, in no particular order, the OM groups of the
DMS-MSC/Call Server for GSM, whose names begin with “A” through “D”.

2-2 OM groups: A-D
ACRJ
Anonymous Call Rejection OM Group 2
The ACRJ provides insight to the ACRJ feature. The ACRJ register is pegged
when the ACRJ feature is applied to route anonymous calls to treatment. The
ACRJ then releases the call.
Registers
The following ACRJ registers may be displayed:
ACRJINVK
Release history
ACRJ was made available in GSM11.
Group structure
ACRJ provides one tuple per MSC/Call Server.
Key field: None
Info field: None
Associated OM groups
None
Associated products
None
Register ACRJINVK 2
Anonymous call rejection
The ACRNJINVK register is pegged when the ACRJ feature is applied. The
ACRJ routes originating anonymous calls to treatment and then releases the
call.
Register type
Peg
Associated register
No registers are associated with this register.
Validation formula
m = Number of times the ACRJINVK register is pegged.
m = Number of times ACRJ service is applied.

OM groups: A-D 2-3
Associated logs
No logs are associated with this register.
Log number:
None
Extension register
There is no extension register.

2-4 OM groups: A-D
ANN
Announcements OM Group 2
The Announcements (ANN) OM group provides information on traffic for
recorded announcement machines.
Registers
The following ANN registers may be displayed at the MAP as follows:
ANNATT ANNOVFL ANNTRU ANNSBU
ANNMBU ANNFTRU
Release history
ANN was made available in B20. It was modified in BCS21 and BCS33.
Group structure
Key field: COMMON_LANGUAGE_NAME CLLI is the common-language
location identifier for the announcement.
Number of tuples: One per announcement trunk.
Datafill
Three tables must be entered with data: ANNS and ANNMEMS:
• Table ANNS contains the data for each announcement assigned in the
switch.
• The subscriber defines other CLLI.
• Table ANNMEMS assigns tracks to announcements.
The OM group OFZ provides information on office traffic by the intended
call destination.
The OM group OTS provides information on office traffic by the accurate call
destination.
Associated products
None
Register ANNATT 2
Announcement attempts
This register counts calls that route to an announcement.

OM groups: A-D 2-5
Register type
Peg
Associated register
Register OFZ_INANN counts calls that originate on a trunk and the system
first routes to an announcement.
Register OFZ_ORIGANN counts calls that originate on a line and the system
first routes to an announcement.
Registers OFZ_INANN and OFZ_ORIGANN do not count calls that the

system routes to an announcement after the system first routes the calls
somewhere else.
The relationship between these registers are:
Σ (ANN_ANNATT) OFZ_INANN + OFZ_ORIGANN
ANN
Register OTS_ORGTRMT counts calls that originate on a line and the system
connects to a tone or an announcement.
Register OTS_INCTRMT counts calls that originate on a trunk and the

system connects to a tone or an announcement.
Register TONES_TONEATT counts attempts to connect to a tone generator.
The relationship between these registers are:
Σ (ANN_ANNATT) + Σ (TONES_TONEATT)
TONES TONES
OTS_ORGTRMT + OTS_INCTRMT
Extension register
None
Associated logs
The line maintenance subsystem generates LINE 138 if the system routes a
call to a treatment after the call is call processing busy.
The trunk maintenance subsystem generates TRK 138 if the system routes a
call routes to a treatment after the call is call processing busy.

2-6 OM groups: A-D
Validation formula
None
Register ANNMBU 2
Announcement manual busy usage
Register ANNMBU records when an announcement is manual busy. Each
announcement consists of a minimum of one track. The following busy states
are measured:
• track manual busy
• track network management (NWM) busy
The system assigns each track one trunk circuit or channel. The system
associates one announcement and one ANN tuple to each track. Table
ANNMEMS defines the connections between tracks and announcements.
Register ANNMBU is a usage register. The scan rate is 100s. The number of
scans for each collection interval (15 min. or 30 min.) divides usage counts.
The number of scans for each collection interval does not divide not the
number of scans in 60 min.
Register type
Usage
Register history
ANNMBU was introduced in BCS20. It was modified in BCS21.
Associated registers
Register ANNTRU records if an announcement is traffic busy.
Register ANNSBU records if an announcement is system busy.
The relationship between these registers, for each tuple, is as follows:
TOTAL BUSY USE = ANNTRU + ANNSBU + ANNMBU
Extension register
None
Associated logs
None
Validation formula
None

OM groups: A-D 2-7
Register ANNOVFL 2
Announcement overflow
Register ANNOVFL counts calls that the system routes to a recorded
announcement, but that fail to connect to the announcement for two reasons.
The maximum number of calls are connected to the announcement or the
announcement is maintenance-busy. Register ANNOVFL does not count the
number of calls that overflow because of network blockage.
Register type
Peg
Register history
Register ANNOVFL was introduced in BCS20.
None
Extension register
None
Associated logs
None
Validation formula
None
Register ANNSBU 2
Announcement system-busy use
Register ANNSBU is a usage register. The scan rate is 100s. The register
records when an announcement is system busy. Each announcement uses one
or more tracks. Table ANNMEMS defines the connections between tracks
and announcements. The busy states that ANNSBU measures are as follows:
• track system busy

• track peripheral module busy
• queued to be manual busy
The number of scans for each collection interval (15 min. or 30 min.) divides
usage counts. The number of scans for each collection interval does not
divide not the number of scans in 60 min.
Register type
Usage

2-8 OM groups: A-D
Register history
Register ANNSBU was introduced in BCS20 and modified in BCS33.
Register ANNTRU records if an announcement is traffic busy.
Register ANNMBU records if an announcement is manual busy.
The relationship between these registers, for each tuple, is as follows:
TOTAL BUSY USAGE = ANNTRU + ANNSBU + ANNMBU
Extension register
None
Associated logs
The system generates TRK106 if a test on trunk equipment fails.
Validation formula
None
Register ANNTRU 2
Announcement traffic use
Register ANNTRU records when an announcement is traffic busy. The scan
rate is 100s. The number of scans for each collection interval (15 min. or 30
min.) divides usage counts. The number of scans for each collection interval
does not divide not the number of scans in 60 min.
Register type
Usage
Register history
Register ANNTRU was introduced in BCS20 and modified in BCS21 and
BCS33.
Register ANNMBU records if an announcement is manual busy.
Register ANNSBU records if an announcement is system busy.
The relationship between these registers, in each tuple, is as follows:

• TOTAL BUSY USE = ANNTRU + ANNSBU + ANNMBU
Extension register
None

OM groups: A-D 2-9
AOCSS
GSM MSC Advice of Charge 2
Registers
The following AOCSS registers can be displayed:
AOCIATT AOCIATT2 AOCCATT AOCCATT2
AOCISUC AOCISUC2 AOCCSUC AOCCSUC2
Registers with names ending with the number 2 are extension registers and
are not documented in this publication. For information on these registers, see
the appropriate primary register.
Release history
AOCSS was created in GSM05.
Group structure
Key field: None
Info field: None
Number of tuples: One per DMS-MSC/Call Server.
None
Associated products
None
Validation Formula
The number of attempts of an operation (given by the appropriate ATT
registers) is always greater than or equal to the number of successful
responses (given by the corresponding SUC registers).
[ACOCIATT + (AOCIATT2 x 65535)] > [AOCISUC + (AOCISUC2 x

65535)]
[AOCCATT + (AOCCATT2 x 65535] > [AOCCSUC + (AOCCSUC2 x

65535)]

2-10 OM groups: A-D
Register AOCIATT 2
Advice of Charge Information Attempts
This register is pegged when an AOCI attempt occurs. An AOC attempt can
occur because the subscriber is provisioned for AoCI.
Associated register
Register AOCIATT2 is pegged each time AOCIATT rolls-over.
Associated logs
None
EXT register
AOCIATT2
Validation formula
The number of AOCI attempts (given by AOCIATT register) is always
greater than or equal to the number of successful AOCI transactions (given by
AOCISUC).

65535)]
Register AOCCATT 2
Advice of Charge Charging Attempts
This register is pegged when an AOCC attempt occurs. An AOCC attempt
can occur because the subscriber is provisioned for AOCC SS.
Associated register
Register AOCCATT2 is pegged each time AOCCATT rolls-over.
Associated logs
None
EXT register
AOCCATT2
Validation formula
The number of AOCC attempts (given by AOCCATT register) is always
greater than or equal to the number of successful AOCC transactions (given
by AOCCSUC).
[AOCCATT + (AOCCATT2 x 65535] > [AOCCSUC + (AOCCSUC2 x

65535)]

OM groups: A-D 2-11
Register AOCISUC 2
Advice of Charge Information Successful Transaction
This register is pegged when an Advice of Charge Information (AOCI) call is
successful. A successful AOCI call occurs when the MS sends a “Facility”
message with a Return Result response to the MSC/Call Server. This scenario
occurs for both MO and MT calls.
Associated register
Register AOCISUC2 is pegged each time AOCISUC “rolls-over”.
Associated logs
None
EXT register
AOCISUC2
Validation formula
The number of AOCI attempts (given by AOCIATT register) is always
greater than or equal to the number of successful AOCI transactions (given by
AOCISUC).

65535)]
Register AOCCSUC 2
Advice of Charge Charging Successful Transaction
This register is pegged when an Advice of Charge Charging (AOCC) call is
successful. A successful AOCC call occurs when the MS sends a “Facility”
message with a Return Result response to the MSC/Call Server. This scenario
occurs for both MO and MT calls.
Associated register
Register AOCCSUC2 is pegged each time AOCCSUC2 rolls-over.
Associated logs
None
EXT register
AOCCATT2
Validation formula
The number of AOCC attempts (given by AOCCATT register) is always
greater than or equal to the number of successful AOCC transactions (given
by AOCCSUC).

2-12 OM groups: A-D

65535)]

OM groups: A-D 2-13
ASSFTRAF
CAMEL call traffic for ASSF 2
This OM group, CAMEL call traffic for ASSF, (ASSFTRAF), is used to
provide ASSP traffic statistics of CAMEL call processing.
This OM group is a 2-dimensional group which is keyed by protocol (Phase 2

and Phase 3) and the registers themselves. For implementation of pegging
Phase 3 registers will not be included in this feature.
Registers
ASSFTRAF registers can be displayed at the DMS Maintenance and
Administrative Position (MAP) as follows:
ASFATT ASFATT2 ASFSEZ ASFSEZ2
ASFANS ASFANS2 ASFSEZU ASFSEZU2
ASFANSU ASFANSU2
Note: Registers with names ending with the number 2 are extension
registers and are not documented in this publication. For information on
these registers, see the appropriate primary register.
Release history
ASSFTRAF was made available in GSM16.
Group structure
Number of Tuples: 2
Key field: None
Info field: None
None
Validation Formula
None
Associated products
None

2-14 OM groups: A-D
Register ASFATT 2
CAMEL call attempt on ASSF mode
Register Describe what the OM register measures. Describe what the OM
register is used for. If OTHER, clearly state what the unit of measure is. If a
USAGE register, provide the scan rate (10/100 sec).
ASFATTL pegs the number of times sending of Call Notification Records

failed.
Release history
ASFATT was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register ASFSEZ 2
CAMEL call seize on ASSF mode
ASFSEZ pegs the number of times sending of Call Notification Records

failed.
Release history
ASFSEZ was made available in GSM16.
None
Associated logs
None
Extension register
None

OM groups: A-D 2-15
Validation formula
None
Register ASFANS 2
CAMEL call answer on ASSF mode
ASFANS pegs the number of times sending of Call Notification Records

failed.
Release history
ASFANS was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register ASFSEZU 2
CAMEL call seize usage on ASSF mode
ASFSEZU pegs the number of times sending of Call Notification Records

failed.
Release history
ASFSEZU was made available in GSM16.
None
Associated logs
None

2-16 OM groups: A-D
Extension register
None
Validation formula
None
Register ASFANSU 2
CAMEL call answer usage on ASSF mode
ASFANSU pegs the number of times sending of Call Notification Records

failed.
Release history
ASFANSU was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None

OM groups: A-D 2-17
ASUFBUS
ASU Fbus messaging data measurements 2
OM group, ASUFBUS, displays number of octets transmitted and received
on each Fbus port.
Registers
The following ASUFBUS registers can be displayed:
FB0TXPK2 FB0TXPKT FB0RXPK2 FB0RXPKT
FB1TXPK2 FB1TXPKT FB1RXPK2 FB1RXPKT
FB0TXER2 FB0TXERR FB0RXER2 FB0RXERR
FB1TXER2 FB1TXERR FB1RXER2 FB1RXERR
FB0TXOC2 FB0TXOCT FB0RXOC2 FB0RXOCT
FB1TXOC2 FB1TXOCT FB1RXOC2 FB1RXOCT
Release history
ASUFBUS was created in CSP03.
Group structure
Key field: None
Info field: pm_type: Please refer to Section “ Associated products” on page

18.
pm_number: {integer}
Number of tuples: One tuple for each ASU
Datafill
LIUINV table defines the tuples of this OM.

2-18 OM groups: A-D
None
Validation formula
None
Associated products
Application Specific Unit (ASU) nodes that will inherit this OM are:
• LIU7: Link Interface Unit
• EIU: Ethernet Interface
• XLIU: X.25 Link Interface Unit
• APU: Application Processing Unit
• VPU: Voice Processing Unit
Register FB0TXPKT 2
Fbus 0 Transmit Packets
Register FB0TXPKT, within an audit period, accumulates the number of
packets transmitted successfully from an ASU on Fbus 0.
Release history
FB0TXPKT was created in CSP03.
Register type
Peg
Associated register
FB0TXPK2: The higher word.
Validation formula
Total Value = FB0TXPK2* 65536 + FB0TXPKT
Associated logs
Log number: None
EXT register
FB0TXPK2
Register FB0RXPKT 2
Fbus 0 Receive Packets
Register FB0RXPKT, within an audit period, accumulates the number of
packets received successfully by an ASU from Fbus 0.

OM groups: A-D 2-19
Release history
FB0RXPKT was created in CSP03.
Register type
Peg
Associated register
FB0RXPK2: The higher word.
Validation formula
Total Value = FB0RXPK2* 65536 + FB0RXPKT
Associated logs
Log number: None
EXT register
FB0RXPK2
Register FB0TXERR 2
Fbus 0 Transmit Errors
Register FB0TXERR, within an audit period, accumulates the number of
packets that could not be sent out from an ASU on Fbus 0 due to an error.
Release history
FB0TXERR was created in CSP03.
Register type
Peg
Associated register
FB0TXER2: The higher word.
Validation formula
Total Value = FB0TXER2* 65536 + FB0TXERR
Associated logs
Log number: None
EXT register
FB0TXER2

2-20 OM groups: A-D
Register FB0RXERR 2
Fbus 0 Receive Errors
Register FB0RXERR, within an audit period, accumulates the number of
packets that were not received successfully by an ASU on Fbus 0 due to an
error.
Release history
FB0RXERR was created in CSP03.
Register type
Peg
Associated register
FB0RXER2: The higher word.
Validation formula
Total Value = FB0RXER2* 65536 + FB0RXERR
Associated logs
Log number: None
EXT register
FB0RXER2
Register FB1TXPKT 2
Fbus1 Transmit Packet
Register FB1TXPKT, within an audit period, accumulates the number of
packets transmitted successfully from an ASU on Fbus 1.
Release history
FB1TXPKT was created in CSP03.
Register type
Peg
Associated register
FB1TXPK2: The higher word.
Validation formula
Total Value = FB1TXPK2* 65536 + FB1TXPKT
Associated logs
Log number: None

OM groups: A-D 2-21
EXT register
FB1TXPK2
Register FB1RXPKT 2
Fbus1 Receive Packets
Register FB1RXPKT, within an audit period, accumulates the number of
packets received successfully by an ASU from Fbus 1.
Release history
FB1RXPKT was created in CSP03.
Register type
Peg
Associated register
FB1RXPK2: The higher word.
Validation formula
Total Value = FB1RXPK2* 65536 + FB1RXPKT
Associated logs
Log number: None
EXT register
FB1RXPK2
Register FB1TXERR 2
Fbus1 Transmit Errors
Register FB1TXERR, within an audit period, accumulates the number of
packets that could not be sent out from an ASU on Fbus 1 due to an error.
Release history
FB1TXERR was created in CSP03.
Register type
Peg
Associated register
FB1TXER2: The higher word.
Validation formula
Total Value = FB1TXER2* 65536 + FB1TXERR

2-22 OM groups: A-D
Associated logs
Log number: None
EXT register
FB1TXER2
Register FB1RXERR 2
Fbus1 Receive Errors
Register FB1RXERR, within an audit period, accumulates the number of
packets that were not received successfully by an ASU on Fbus 1 due to an
error.
Release history
FB1RXERR was created in CSP03.
Register type
Peg
Associated register
FB1RXER2: The higher word.
Validation formula
Total Value = FB1RXER2* 65536 + FB1RXERR
Associated logs
Log number: None
EXT register
FB1RXER2
Register FB0TXOCT 2
Fbus 0 Transmit Octets
Register FB0TXOCT, within an audit period, accumulates the number of
octets (bytes) transmitted from an ASU on Fbus 0.
Release history
FB0TXOCT was created in CSP03.
Register type
Other
Associated register
FB0TXOC2: The higher word.

OM groups: A-D 2-23
Validation formula
Total Value = FB0TXOC2 * 65536 + FB0TXOCT
Associated logs
Log number: None
EXT register
FB0TXOC2
Register FB0RXOCT 2
Fbus 0 Receive Octets
Register FB0RXOCT, within an audit period, accumulates the number of
octets (bytes) received by an ASU on Fbus 0.
Release history
FB0RXOCT was created in CSP03.
Register type
Other
Associated register
FB0RXOC2: The higher word.
Validation formula
Total Value = FB0RXOC2 * 65536 + FB0RXOCT
Associated logs
Log number: None
EXT register
FB0RXOC2
Register FB1TXOCT 2
Fbus1 Transmit Octets
Register FB1TXOCT, within an audit period, accumulates the number of
octets (bytes) transmitted from an ASU on Fbus 1.
Release history
FB1TXOCT was created in CSP03.
Register type
Other

2-24 OM groups: A-D
Associated register
FB1TXOC2: The higher word.
Validation formula
Total Value = FB1TXOC2 * 65536 + FB1TXOCT
Associated logs
Log number: None
EXT register
FB1TXOC2
Register FB1RXOCT 2
Fbus1 Receive Octets
Register FB1RXOCT, within an audit period, accumulates the number of
octets (bytes) received by an ASU on Fbus 1.
Release history
FB1RXOCT was created in CSP03.
Register type
Other
Associated register
FB1RXOC2: The higher word.
Validation formula
Total Value = FB1RXOC2* 65536 + FB1RXOCT
Associated logs
Log number: None
EXT register
FB1RXOC2

OM groups: A-D 2-25
ASUMEMUT
ASU memory utilization 2
OM group, ASUMEMUT, displays Data and Program store information for
an ASU.
Registers
The following ASUMEMUT registers can be displayed:
ASUDSTOT ASUDSAVL ASUPSTOT ASUPSAVL
Release history
ASUMEMUT was created in CSP03.
Group structure
Key field: None
Info field: pm_type: Please refer to Section “ Associated products” on page

25.
pm_number: {integer}
Number of tuples: One tuple for each ASU
Datafill
LIUINV table defines the tuples of this OM.
None
Validation formula
None
Associated products
Application Specific Unit (ASU) nodes that will inherit this OM are:
• LIU7: Link Interface Unit
• EIU: Ethernet Interface
• XLIU: X.25 Link Interface Unit
• APU: Application Processing Unit
• VPU: Voice Processing Unit

2-26 OM groups: A-D
Register ASUDSTOT 2
Total Data Store (DS) memory
Register ASUDSTOT holds total DS memory information in Kbytes.
Release history
ASUDSTOT was created in CSP03.
Register type
Other
Associated register
None
Validation formula
None
Associated logs
Log number: None
EXT register
None
Register ASUDSAVL 2
Free Data Store (DS) memory
Register ASUDSAVL holds available DS memory information in Kbytes.
Release history
ASUDSAVL was created in CSP03.
Register type
Other
Associated register
None
Validation formula
None
Associated logs
Log number: None
EXT register
None

OM groups: A-D 2-27
Register ASUPSTOT 2
Total Program Store (PS) memory
Register ASUPSTOT holds total PS memory information in Kbytes.
Release history
ASUPSTOT was created in CSP03.
Register type
Other
Associated register
None
Validation formula
None
Associated logs
Log number: None
EXT register
None
Register ASUPSAVL 2
Free Program Store (PS) memory
Register ASUPSAVL holds available PS memory information in Kbytes.
Release history
ASUPSAVL was created in CSP03.
Register type
Other
Associated register
None
Validation formula
None
Associated logs
Log number: None
EXT register
None

2-28 OM groups: A-D
BICNANNC
BICN Announcements 2
The BICNANNC (BICN Announcements) OM Group is structured
identically to the base UMTS/GSM Announcements OM Group, but is for
BICN announcements that are provided in the MGWs as opposed to the
MTMs or DTMs. This group has one register which measures: announcement
attempts.
Registers
The BICNANNC registers may be displayed:
BICNANAT
Release history
BICNANNC was created in GSM17.
Group structure
Number of tuples: 0-255
Key field: COMMON_LANGUAGE_NAME (ANNS CLLI)
Info field: None
ANN
Associated products
MGW
Validation formula
None
Datafill
Table ANNS.

OM groups: A-D 2-29
OMSHOW example
Figure 2-1
OMSHOW example - BICNANNC OM group
Register BICNANAT 2
BICN announcement attempts
Register BICNANAT exists in the BICNANNC OM Group and pegs the
number of BICN announcement attempts.
Register history
BICNANAT was created in GSM17.
Register type
Peg
Associated register
None

2-30 OM groups: A-D
Validation formula
None
Associated logs
None
EXT register
None

OM groups: A-D 2-31
BICNTONE
BICN Tones 2
The BICNTONE (BICN Tones) OM Group is structured identically to the
base UMTS/GSM Tones OM Group, but is for BICN tones that are provided
in the MGWs as opposed to the MTMs or DTMs. This group has one register
which measures: tone attempts.
Registers
The BICNTONE registers may be displayed:
BICNTNAT
Release history
BICNTONE was created in GSM17.
Group structure
Number of tuples: 0-255
Key field: COMMON_LANGUAGE_NAME (TONES CLLI)
Info field: None
TONES
Associated products
MGW
Validation formula
None
Datafill
Table TONES.

2-32 OM groups: A-D
OMSHOW example
Figure 2-2
OMSHOW example - BICNTONE OM group
Register BICNTNAT 2
BICN tone attempts
Register BICNTNAT exists in the BICNTONE OM Group and pegs the
number of BICN tone attempts.
Register history
BICNTNAT was created in GSM17.
Register type
Peg
Associated register
None
Validation formula
None
Associated logs
None
EXT register
None

OM groups: A-D 2-33
BILLING
Billing 2
Collect measurements on impact of automatic call disconnect events.
Registers
The following BILLING registers may be displayed:
PBRGEN LONGCALL
Release history
BILLING was modified in GSM09.
Group structure
1 tuple per DMS-MSC/Call Server.
Key field: None
Info field: None
None
Associated products
GSM Partial Billing
Register PBRGEN 2
PBRGEN is pegged first time a partial billing record is generated. The
register is implemented as a precautionary measure to account for the
possibility that the operating company personnel may configure the switch in
such a way that numerous partial billing records are generated per call. As a
result, the performance of the switch may be adversely affected and this peg
may be used as an indicator to the operating company personnel.
Associated register
None
Validation formula
None
Associated logs
GMSC 618

2-34 OM groups: A-D
EXT register
None
Register LONGCALL 2
LONGCALL is pegged first time a call disconnection service event is
involved. The register is implemented as a precautionary measure to count the
number of disconnections for calls. As a result, if the counts approach levels
high enough to be detrimental to customer satisfaction, this peg may be used
as an indicator to the craftsperson that the call duration specified may need to
be extended.
Associated register
None
Validation formula
None
Associated logs
GMSC 618
EXT register
None

OM groups: A-D 2-35

2-36 OM groups: A-D
BRSTAT
BRISC Occupancy Status 2
The BRISC Occupancy Status (BRSTAT) OM Group provides statistics on
CPU utilization for SuperNode offices using the reduced instruction set
computer (BRISC). CPU utilization is the ratio of realtime spent on CPU
function to the time expected for that function. The usage registers are
updated every minute to reflect this ratio.
The software operating system (SOS) scheduler uses scheduler classes to

allocate CPU time among concurrent processes. A scheduler class is a group
of processes that perform similar or related functions.
Registers
The following BRSTAT registers may be displayed:
BRSCAP BRSCMPLX *BRSSCHED *BRSFORE
*BRSMAINT *BRSDNC *BRSOM *BRSGTERM
*BRSBKG *BRSIDLE *BRSAUXCP *BRSNETM
*BRSSNIP
Note: The registers prefixed with an asterisk (*) are DMS-100 specific
registers. This section documents only the registers associated with the
GSM SuperNode switches. For information on the DMS-100 registers,
refer to DMS-100 Family Operational Measurements 297-1001-814.
Release history
BRSTAT was modified in GSM06.
Group structure
BRSTAT provides one tuple per office.
Key field: None
Info field: None
None
Associated products
This group is related only to the BRISC SuperNode core only.

OM groups: A-D 2-37
Register BRSCAP 2
BRISC Call Capacity
Register BRSCAP is a usage register that indicates the percentage of call
processing capacity used within the engineering recommendation for which
grade of service specifications are guaranteed to be met. This meaning is the
same as in previous releases. Only the algorithm to determine the value is
different.
This register is updated every minute to reflect the average call processing
usage observed since the last OM transfer.
Associated register
None
Validation formula
None
Associated logs
None
EXT register
None
Register BRSCMPLX 2
BRISC Call Complexity Ratio
Register BRSCMPLX represents the engineering number of call attempts at
capacity. This register is updated every minute to reflect the observed
ENGBHCA of the last minute. The holding BRSCMPLX register represents
the ENGBHCA over the last OM period.
Associated register
None
Validation formula
None
Associated logs
None
EXT register
None

2-38 OM groups: A-D
C7GTLNK
SCCP global title OMs per link 2
OM group, C7GTLNK, is used to keep track of global title related OMs on a
per link basis. Currently all GTT OMs are uploaded from the link and
combined into a single register in the CM. This means that GTT OMs could
only be studied on a per office basis. This feature changes this so that when
the OMs are uploaded, they are placed in a register for their respective link.
These OMs are used to keep track of the number of gtts performed, the
number that failed because of no translation for address, no translation for
address nature and hop counter violation.
It is important to note that these OMs are for OMs uploaded from the link.
This means that if a translation is performed in the CM, register C7MSGGT
of the C7SCCP OMGROUP is still pegged. These OMs have not changed.
The addition is when the GTT OM is uploaded from the link.
Registers
C7GTLNK registers can be displayed at the DMS Maintenance and
Administrative Position (MAP) as follows: :
C7GTT C7GTT2 C7RFNTN C7RFNTA
C7HOPERR C795GTT C795NGTT
Release history
C7GTLNK was made available in STP041.
Group structure
Key field: C7_LINKSET_NUMBER { 0 TO max_c7_linksets + 1 }
Info field: C7LINK_OMINFO {0 to 15}
Number of tuples: max_c7_links + 1 (currently 254 + 1)
Datafill
Because these OMs are related to the links, they are therefore related to the
datafill in table c7link. There will be one set of registers for each link in table
c7link.
OM group C7GTLNK is related to the C7SCCP group. While they both
reside in the CM. C7SCCP stores the OMs (including GTT OMs) pegged in

OM groups: A-D 2-39
the CM and LIU7 while C7GTLNK stores GTT OMs pegged on the link and
then uploaded to the CM.
Validation formula
None
Associated products
CCS7, LIU7, STP004.1
Register C7GTT 2
number of translations performed
Register C7GTT measures the number of global title translations performed
per link.
Release history
C7GTT was made available in STP041.
Register type
Peg
Associated register
None
Validation formula
None
Associated logs
Log number: None
EXT register
C7GTT2
Register C7RFNTN 2
Routing failures for no translation for address nature
Register C7RFNTN counts, per link, the number of GTTs that resulted in
error due to no translation for the address nature.
Release history
C7RFNTN was made available in STP041.
Register type
Peg
Associated register
None

2-40 OM groups: A-D
Validation formula
None
Associated logs
Log number: CCS241
This log is generated when there is a routing error for no translation for the
address nature.
EXT register
None
Register C7RFNTA 2
Routing failures for no translation for address
Register C7RFNTA counts, per link, the number of GTTs that resulted in error
due to translation for the address.
Release history
C7RFNTA was made available in STP041.
Register type
Peg
Associated register
None
Validation formula
None
Associated logs
Log number: CCS241
This log is generated when there is an error cause by no translation for the
address.
EXT register
None
Register C7HOPERR 2
Hop counter violations
Register C7HOPERR counts, per link, the number of messages that had an
SCCP hop counter violation in them.
Release history
C7HOPERR was made available in STP041.

OM groups: A-D 2-41
Register type
Peg
Associated register
None
Validation formula
None
Associated logs
Log number: CCS241
This log generated to report a hop counter violation.
EXT register
None
Register C795GTT 2
Above 95th percentile with GTT
Register C795GTT is the number of 95th percentile tests failed for MSUs
requiring global title translation (GTT). Pegged per link.
Register C795GTT counts the number of MSUs sampled, with processing

handling delays above the 95th-percentile requirement for MSUs with GTT.
The processing handling delay is the interval starting when the STP receives
the last bit of a message from the incoming signalling link and ending when
the message has been placed in the output signalling link control buffer.
Release history
C795GTT was made available in STP041.
Register type
Peg
Associated register
None
Validation formula
None
Associated logs
Log number: None

2-42 OM groups: A-D
EXT register
None
Register C795NGTT 2
Above 95th percentile without GTT
Register C795NGTT is the number of 95th percentile tests failed for MSUs
not requiring global title translation (GTT). Pegged per link.
Register C795GTT counts the number of MSUs sampled, with processing

handling delays above the 95th-percentile requirement for MSUs without
GTT.
Release history
C795NGTT was made available in STP041.
Register type
Peg
Associated register
None
Validation formula
None
Associated logs
Log number: None
EXT register
None

OM groups: A-D 2-43
C7GWSCCP
CCS7 INTL. GW SCCP 2
OM group, C7GWSCCP, measures the performance and usage of the CCS7
SCCP. It was created to accomodate the 3 new registers associated with
international gateway SCCP. There is insufficent room in group C7SCCP.
Registers
C7GWSCCP registers can be displayed at the DMS Maintenance and
C7THROWN C7MSGCC C7MSGCC2
Release history
C7GWSCCP was made available in BSC34.
Group structure
Key field: None
Info field: None
Number of tuples: 1
Datafill
None
Group C7GWSCCP is associated with group C7SCCP. It contains registers
which are used by international gateway SCCP and which cannot be
accomodated in group C7SCCP.
Register C7THROWN 2
Number of incoming SCCP messages discarded due to MSB7 overload.
Release history
C7THROWN was made available in BSC34.
Register type
Peg
C7MSGHDL (in group C7SCCP) Total number of messages processed.
C7MSGCC Number of SCCP messages processed in the CC

2-44 OM groups: A-D
Validation formula
C7MSGHDL = C7THROWN + C7MSGCC
(handled = discarded + processed)
Associated register
None
Register C7MSGCC 2
Register C7MSGCC counts the number of messages processed by the CC.
Release history
C7MSGCC was made available in BSC34.
Register type
Peg
C7MSGHDL (in group C7SCCP) Total number of SCCP messages
processed.
C7THROWN Number of SCCP messages discarded due to overload in the

MSB7.
Validation formula
C7MSGHDL = C7THROWN + C7MSGCC
(handled = discarded + processed)
Associated logs
None
Extension register
C7MSGCC2

OM groups: A-D 2-45
C7LINK
Note 1: The OM group, C7LINK, has been removed and has been
replaced by the following OM groups: C7LINK1, C7LINK2, C7LINK3,
and C7LINK4.
Note 2: For information regarding OM groups, C7LINK1, C7LINK2,

C7LINK3, and C7LINK4, refer to the NTP 411-3001-814 Volume 1,
Wireless Networks Base/Telecom Operational Measurements Reference
Manual Volume 1 of 3 OM groups ACCSBNS - EXT.

2-46 OM groups: A-D
C7LPP
This OM group is used to store LPP information related to the
INTER/INTRA-frame traffic and the size of the messages going through the
CCS7 Link. The OM group is created because there is no existing OM group
storing OM data per frame. This OM group applies to both LPP, MS and
ELPP in STP04.
Registers
C7LPP registers can be displayed at the DMS Maintenance and
VALIDFL NILREG1 NILREG2 NILREG3
IEH5SRX IEH5STX IAH5SRX IAH5STX
IEH1TRX IEH1TTX IEA1TRX IEA1TTX
IAH1TRX IAH1TTX IAA1TRX IAA1TTX
C7L27RX C7L27TX C7L43RX C7L43TX
C7L74RX C7L74TX C7L75RX C7L75TX
C7H1CRX C7H1CTX C7H2CRX C7H2CTX
C7H3CRX C7H3CTX C7H4CRX C7H4CTX
C7L22TX
Group structure
Key field: Controller (MS or LIM)
Info field: card number for MS and lim number for LIM
Number of tuples: 21
Datafill
Tables C7LINK and LIUINV.
C7LPP2. Some of the LPP OM registers originally in C7LPP are moved to
C7LPP2 due to the number of registers limit (max. 28). The OM registers in
C7LPP2 are mainly user Part OMs.
Validation formula
All OMs in C7LPP are expressed in percentage and should never be > 100.

OM groups: A-D 2-47
Also the sum of the following OM registers should also be = 100.
C7L27RX + C7L43RX + C7L74RX + C7L75RX = 100 or 0
C7H1CRX + C7H2CRX + C7H3CRX + C7H4CRX = 100 or 0
IEA1TRX + IAA1TRX = 100
The same formulae above apply for the OM registers in the TX direction also.
Associated products
all LIU7s/HLIUs
Register VALID_FL 2
Validity of the OM data in table C7LPP
The register is only used to indicate whether other registers in group C7LPP
are valid.
Register type
indicate if all the other OM data are valid in table C7LPP.
Associated register
All other registers in C7LPP. (e.g. IEH5SRX, IEH5STX,
IEH1TRX,IEH1TTX, IEA1TRX, IEA1TTX, IAH5SRX, IAH5STX,
IAH1TRX,IAH1TTX, IAA1TRX, IAA1TTX, C7L27RX, C7L27TX,
C7L43RX,C7L43TX, C7L74RX, C7L74TX, C7H1CRX, C7H1CTX,
C7H2CRX,C7H2CTX, C7H3CRX, C7H3CTX).
Validation formula
Either 0 (Invalid) or 1 (Valid)
Associated logs
Log number: None
EXT register
None
Register VALIDFL2 2
Validity of the OM data in table C7LPP2
The register is only used to indicate whether other registers in group C7LPP2
are valid.
Register type
indicate if all the other OM data are valid in table C7LPP2.

2-48 OM groups: A-D
Associated register
All other registers in C7LPP2. (e.g. LPPSCRX, LPPSCRX2,
LPPSCTX,LPPUPRX, LPPUPRX2, LPPUPTX, LPPUPTX2, LPPSCTX2,
LPMTPRX,LPMTPRX2, LPMTPTX, LPMTPTX2).
Validation formula
Either 0 (Invalid) or 1 (Valid)
Associated logs
Log number: None
EXT register
None
Register IEH5SRX 2
Incoming INTER-frame Traffic Highest % (5 sec per 24 hr)
The register is expressed in unit of percentage of the total traffic going
through the frame. They represent the Highest 5-second INTER-frame traffic
in the incoming (RX) and outgoing directions (TX) per 24 hour.
Register type
High Water Mark for 5 second incoming Inter-frame traffic
Associated register
VALID_FL -is used to indicate whether the register above is valid or not.
Validation formula
Range : 0 - 100
Associated logs
Log number: None
EXT register
None
Register IEH5STX 2
Outgoing INTER-frame Traffic Highest % (5 sec per 24 hr)
through the frame. They represent the Highest 5-second INTER-frame traffic
Register type
High Water Mark for 5 second incoming Inter-frame traffic

OM groups: A-D 2-49
Associated register
Validation formula
Range : 0 - 100
Associated logs
Log number: None
EXT register
None
Register IEH1TRX 2
Incoming INTER-frame Highest % (1 transfer period per 24 hr)
through the frame. They represent the Highest INTER-frame traffic in the
incoming (RX) and outgoing directions (TX) in one transfer period per 24
hour.
Register type
High Water Mark
Associated register
Validation formula
Range: 0 - 100
Associated logs
Log number: None
EXT register
None
Register IEH1TTX 2
Outgoing INTER -frame Traffic Highest % (1 transfer period per 24 hr)
through the frame. They represent the Highest INTER-frame traffic in the
hour.
Register type
High Water Mark

2-50 OM groups: A-D
Associated register
Validation formula
Range: 0 - 100
Associated logs
Log number: None
EXT register
None
Register IEA1TRX 2
Incoming INTER-frame Traffic Accumulated % (1 transfer period per 24
hr)
through the frame. They represent the INTER-frame traffic in the incoming
(RX) and outgoing directions (TX) in one transfer period.
Register type
Accumlated data for 1 transfer period
Associated register
Validation formula
Range: 0 - 100
Associated logs
Log number: None
EXT register
None
Register IEA1TTX 2
Outgoing INTER-frame Traffic Accumlated % (1 transfer period per 24 hr)
through the frame. They represent the INTER-frame traffic in the incoming
Register type
Accumlated data for 1 transfer period

OM groups: A-D 2-51
Associated register
Validation formula
Range: 0 - 100
Associated logs
Log number: None
EXT register
None
Register IAH5SRX 2
Incoming INTRA-frame Traffic Highest % (5 sec per 24 hr)
through the frame. They represent the Highest 5-second INTRA-frame traffic
Register type
High Water Mark
Associated register
Validation formula
Range : 0 - 100
Associated logs
Log number: None
EXT register
None
Register IAH5STX 2
Outgoing INTRA-frame Traffic Highest % (5 sec per 24 hr)
through the frame. They represent the Highest 5-second INTRA-frame traffic
Register type
High Water Mark
Associated register

2-52 OM groups: A-D
Validation formula
Range : 0 - 100
Associated logs
Log number: None
EXT register
None
Register IAH1TRX 2
Incoming INTRA-frame Highest % (1 transfer period per 24 hr)
through the frame. They represent the Highest INTRA-frame traffic in the
hour.
Register type
High Water Mark
Associated register
Validation formula
Range: 0 - 100
Associated logs
Log number: None
EXT register
None
Register IAH1TTX 2
Outgoing INTRA-frame Highest % (1 transfer period per 24 hr)
through the frame. They represent the Highest INTRA-frame traffic in the
hour.
Register type
High Water Mark
Associated register

OM groups: A-D 2-53
Validation formula
Range: 0 - 100
Associated logs
Log number: None
EXT register
None
Register IAA1TRX 2
Incoming INTRA-frame Traffic Accumulated % (1 transfer period per 24
hr)
through the frame. They represent the INTRA-frame traffic in the incoming
Register type
Accumlated INTRA-frame data for 1 transfer period
Associated register
Validation formula
Range: 0 - 100
Associated logs
Log number: None
EXT register
None
Register IAA1TTX 2
Outgoing INTRA-frame Traffic Accumlated % (1 transfer period per 24 hr)
through the frame. They represent the INTRA-frame traffic in the incoming
Register type
Accumlated INTRA-frame data for 1 transfer period
Associated register

2-54 OM groups: A-D
Validation formula
Range: 0 - 100
Associated logs
Log number: None
EXT register
None
Register C7L27RX 2
% of incoming MSU length =< 27 bytes (LIU7)
The register is expressed in unit of percentage of the total LIU7 traffic going
through the frame. They represent traffic with message length <= 27 bytes
going through LIU7 in the incoming (RX) and outgoing directions (TX) for
one transfer period.
Register type
Accumulate data for 1 transfer period
Associated register
Validation formula
Range: 0 - 100
C7L27RX + C7L43RX + C7L74RX + C7L75RX= 100 or 0
C7L27TX + C7L43TX + C7L74TX + C7L75TX = 100 or 0
If the frame has no LIU7, the sum will always be added up to 0. Otherwise,
the sum should be equal to 100.
Associated logs
Log number: None
EXT register
None
Register C7L27TX 2
% of outgoing MSU length =< 27 bytes (LIU7)
through the frame. They represent traffic with message length <= 27 bytes
going through LIU7 in the incoming (RX) and outgoing directions (TX) for
one transfer period.

OM groups: A-D 2-55
Register type
Associated register
Validation formula
Range: 0 - 100
C7L27RX + C7L43RX + C7L74RX + C7L75RX= 100 or 0
Associated logs
Log number: None
EXT register
None
Register C7L43RX 2
of incoming MSU length 20 -> 43 bytes (LIU7)
through the frame. They represent LIU7 traffic with message length (>= 28
and <= 43 bytes) in the incoming (RX) and outgoing directions (TX) for one
transfer period.
Register type
Associated register
VALID_FL - is used to indicate whether the register above is valid or not.
Validation formula
Range: 0 - 100

2-56 OM groups: A-D
Associated logs
Log number: None
EXT register
None
Register C7L43TX 2
% of outgoing MSU length 20 -> 43 bytes (LIU7)
transfer period.
Register type
Associated register
VALID_FL - is used to indicate whether the register above is valid or not.
Validation formula
Range: 0 - 100
Associated logs
Log number: None
EXT register
None
Register C7L74RX 2
% of incoming MSU length 35 -> 74 bytes (LIU7)
transfer period.
Register type

OM groups: A-D 2-57
Associated register
Validation formula
Range: 0 - 100
Associated logs
Log number: None
EXT register
None
Register C7L74TX 2
% of outgoing MSU length 35 -> 74 bytes (LIU7)
transfer period.
Register type
Associated register
Validation formula
Range: 0 - 100
Associated logs
Log number: None

2-58 OM groups: A-D
EXT register
None
Register C7L75RX 2
% of incoming MSU length > 74 bytes (LIU7)
bytes) in the incoming (RX) and outgoing directions (TX) for one transfer
period.
Register type
Associated register
Validation formula
Range: 0 - 100
Associated logs
Log number: None
EXT register
None
Register C7L75TX 2
% of outgoing MSU length > 74 bytes (LIU7)
bytes) in the incoming (RX) and outgoing directions (TX) for one transfer
period.
Register type
Associated register

OM groups: A-D 2-59
Validation formula
Range: 0 - 100
Associated logs
Log number: None
EXT register
None
Register C7H1CRX 2
% of incoming MSU length =< 1 ATM cell (HLIU)
The register is expressed in unit of percentage of the total HLIU traffic going
through the frame. They represent HLIU traffic with message length (<= 1
cell [36 bytes]) in the incoming (RX) and outgoing directions (TX) for one
transfer period.
Register type
Associated register
Validation formula
Range: 0 - 100
C7H1CTX + C7H2CTX + C7H3CTX + C7H4CRX= 100 or 0
Associated logs
Log number: None
EXT register
None

2-60 OM groups: A-D
Register C7H1CTX 2
% of outgoing MSU length =< 1 ATM cell (HLIU)
through the frame. They represent HLIU traffic with message length (<= 1
cell [36 bytes]) in the incoming (RX) and outgoing directions (TX) for one
transfer period.
Register type
Associated register
Validation formula
Range: 0 - 100
C7H1CTX + C7H2CTX + C7H3CTX + C7H4CRX= 100 or 0
Associated logs
Log number: None
EXT register
None
Register C7H2CRX 2
% of incoming MSU length 1 -> 2 ATM cells (HLIU)
through the frame. They represent HLIU traffic with message length (> 1 cell
[53 bytes] and <= 2 cell [106 bytes]) in the incoming (RX) and outgoing
directions (TX) for one transfer period.
Register type
Associated register
Validation formula
Range: 0 - 100

OM groups: A-D 2-61
C7H1CTX + C7H2CTX + C7H3CTX + C7H4CTX= 100 or 0
Associated logs
Log number: None
EXT register
None
Register C7H2CTX 2
% of outgoing MSU length 1 -> 2 ATM cells (HLIU)
through the frame. They represent HLIU traffic with message length (> 1 cell
[53 bytes] and <= 2 cell [106 bytes]) in the incoming (RX) and outgoing
directions (TX) for one transfer period.
Register type
Associated register
Validation formula
Range: 0 - 100
C7H1CTX + C7H2CTX + C7H3CTX + C7H4CTX= 100 or 0
Associated logs
Log number: None
EXT register
None

2-62 OM groups: A-D
Register C7H3CRX 2
% of incoming MSU length 2 -> 3 ATM cells (HLIU)
through the frame. They represent HLIU traffic with message length (> 2
cells [106 bytes] and <= 3 cells [159 bytes]) in the incoming (RX) and
outgoing directions (TX) for one transfer period.
Register type
Associated register
Validation formula
Range: 0 - 100
C7H1CTX + C7H2CTX + C7H3CTX + C7H4CTX = 100 or 0
Associated logs
Log number: None
EXT register
None
Register C7H3CTX 2
% of outgoing MSU length 2 -> 3 ATM cells (HLIU)
cells [106 bytes] and <= 3 cells [159 bytes]) in the incoming (RX) and
outgoing directions (TX) for one transfer period.
Register type
Associated register
Validation formula
Range: 0 - 100

OM groups: A-D 2-63
Associated logs
Log number: None
EXT register
None
Register C7H4CRX 2
% of incoming MSU length > 3 ATM cells (HLIU)
cells [159 bytes]) in the incoming (RX) and outgoing directions (TX) for one
transfer period.
Register type
Associated register
Validation formula
Range: 0 - 100
Associated logs
Log number: None
EXT register
None

2-64 OM groups: A-D
Register C7H4CTX 2
% of outgoing MSU length > 3 ATM cells (HLIU)
cells [159 bytes]) in the incoming (RX) and outgoing directions (TX) for one
transfer period.
Register type
Associated register
Validation formula
Range: 0 - 100
Associated logs
Log number: None
EXT register
None
Register C7L22TX 2
% of incoming MSU length 0 -> 22 bytes (LIU7)
through the frame. They represent LIU7 traffic with message length (>= 0 and
<= 22 bytes) in the incoming (RX) and outgoing directions (TX) for one
transfer period.
Release history
C7L22TX was made available in BCS35.
Register type
Associated register

OM groups: A-D 2-65
Validation formula
Range: 0 - 100
Associated logs
Log number: None
EXT register
None

2-66 OM groups: A-D
C7MTP
C7 Message Transfer Part 2
OM group, C7MTP, provides information on performance and failures of
Message Signal Units (MSUs) at a Signal Transfer Point (STP).
Registers
C7MTP registers can be displayed at the DMS Maintenance and
C7MSIDPC C7MSISIO C7XSDYWT C7XSDYNT
C7PHDYWT C7PHDYNT C7GTT95 C7NGTT95
C7SMPWT1 C7SMPWT2 C7SMPNT1 C7SMPNT2
Release history
C7MTP was made available in BCS32.
Group structure
Key field: None
Info field: None
Number of tuples: 1 for each STP.
Validatin formula
None
C7LINK1 provides information about the failure and recoveries of a CCS7
link.
C7LINK2 provides information on calls and congestion for a CCS7 link.
C7LINK3 monitors traffic and performanced of a Message signal Unit

(MSU) for a CCS7 link.
C7SCCP provides information on the performance and use of the CCS7

signalling connection control port (SCCP).

OM groups: A-D 2-67
Associated products
None
Register C7XSDYWT 2
Average Cross-STP delay for MSUs requiring Global Title Translation
This register reports the average Cross-STP delay for MSUs that require GTT.
Cross-STP delay is defined in Bellcore Technical Reference (TR-000082) as
follows:
• Cross-STP Delay - The interval beginning when the STP receives the last
bit of a message from the incoming signalling link and ending when the
STP transmits the last bit of the message on the outgoing signaling link.
• The MSU sampling rate for this register is once every ten seconds.
• Average Cross-STP delay is reported in milliseconds.
Release history
C7XSDYWT was made available in BCS32.
Register type
High Water: Performance Register. (Reports MSU delay through an STP
office.)
Associated register
None
Validation formula
None
Associated logs
None
EXT register
None
Register C7XSDYNT 2
Average Cross-STP delay for MSUs not requiring Global Title Translation
This register reports the average Cross-STP delay for MSUs that do NOT
require GTT. Cross-STP delay is defined in Bellcore Bellcore Technical
Reference (TR-000082) as follows:
• Cross-STP Delay - The interval beginning when the STP receives the last
bit of a message from the incoming signalling link and ending when the
STP transmits the last bit of the message on the outgoing signaling link.
• Average Cross-STP delay is reported in milliseconds.

2-68 OM groups: A-D
Release history
C7XSDYNT was made available in BCS32.
Register type
office.)
Associated register
None
Validation formula
None
Associated logs
None
EXT register
None
Register C7PHDYWT 2
Average Processor Handling delay for MSUs requiring Global Title
Translation
This register reports the average Processing Handling delay for MSUs that
require GTT. The Processing handling delay is defined in Bellcore Technical
Reference (TR-000082) as follows:
• Processing Handling Delay - The interval beginning when the STP
receives the last bit of a message from the incoming signalling link and
ending when the message has been placed in the output signaling link
control buffer.
• Average Processing Handling delay is reported in milliseconds.
Release history
C7PHDYWT was made available in BCS32.
Register type
office.)
Associated register
None

OM groups: A-D 2-69
Validation formula
None
Associated logs
None
EXT register
None
C7PHDYNT 2
Average Processor Handling delay for MSUs requiring Global Title
translation
This register reports the average Processing Handling delay for MSUs that do
NOT require GTT. The Processing handling delay is defined in Bellcore
Technical Reference (TR-000082) as follows:
• Processing Handling Delay - The interval beginning when the STP
receives the last bit of a message from the incoming signalling link and
ending when the message has been placed in the output signaling link
control buffer.
• Average Processing Handling delay is reported in milliseconds.
Release history
C7PHDYNT was made available in BCS32.
Register type
office.)
Associated register
None
Validation formula
None
Associated logs
None
EXT register
None

2-70 OM groups: A-D
Register C7GTT95 2
Number of 95th percentile tests failed for MSUs requiring GTT
This register reports the number of Processing Handling delays above the
95th percentile requirement for MSUs requiring GTT. This requirement, as
specified in Bellcore Technical Reference (TR-000082), states that the
Processor Handling time for MSUs requiring GTT should not exceed 200
millseconds.
Release history
C7GTT95 was made available in BCS32.
Register type
Peg
Associated register
None
Validation formula
None
Associated logs
None
EXT register
None
Register C7NGTT95 2
Number of 95th percentile tests failed for MSUs not requiring GTT
This register reports the number of Processing Handling delays above the
95th percentile requirement for MSUs not requiring GTT. This requirement,
as specified in Bellcore Technical Reference (TR-000082), states that the
Processor Handling time for MSUs not requiring GTT should not exceed 80
millseconds.
Release history
C7NGTT95 was made available in BCS32.
Register type
Peg
Associated register
None
Validation formula
None

OM groups: A-D 2-71
Associated logs
None
EXT register
None
Register C7SMPWT1 2
Number of MSUs sampled for Cross-STP and Processor Handling delay
measurements that required GTT
This register reports the number of MSUs requiring GTT that were sampled
for average Cross STP and Processor Handling delay measurements.
(Reported in registers C7XSDYWT and C7PHDYWT). An extension register
is provided to support larger STP systems.
Release history
C7SMPWT1 was made available in BCS32.
Register type
Peg
C7XSDYWT and C7PHDYWT
Validation formula
None
Associated logs
None
EXT register
C7SMPWT2
Register C7SMPNT1 2
Number of MSUs sampled for Cross-STP and Processor Handling delay
measurements that did not require GTT
This register reports the number of MSUs not requiring GTT that were
sampled for average Cross STP and Processor Handling delay measurements.
(Reported in registers C7XSDYNT and C7PHDYNT). An extension register
is provided to support larger STP systems.
Release history
C7SMPNT1 was made available in BCS32.

2-72 OM groups: A-D
Register type
Peg
C7XSDYNT and C7PHDYNT
Validation formula
None
Associated logs
None
EXT register
C7SMPNT2

OM groups: A-D 2-73
C7MTPRES
MTP Restart Operation Measurement
OM group, C7MTPRES, counts the number of Partial, Full, Adjacent, and
Unexpected TRM procedures occurred in the previous hour.
Registers
C7MTPRES registers can be displayed at the DMS Maintenance and
RESPARCT RESFULCT RESADJCT RESUNXCT
Release history
C7MTPRES was made available in STP03/CSP05.
Group structure
Key field: None
Info field: None
Number of tuples: 1
Validatin formula
None
There are not other OM groups related to this group.
Associated products
This OM provides measurement for the CM.
Register RESPARCT 2
Partial restart count
Register RESPARCT counts the number of Partial register procedure that
occurred in the previous hour.
Release history
RESPARCT was made available in STP03/CSP05.
Register type
Peg

2-74 OM groups: A-D
Associated register
None
Validation formula
None
Associated logs
Log number: 145
Logs 145 are issued whenever the Partial restart procedure is initiated. There
should be a correlation between the number of logs issued for Partial restart
and this register.
EXT register
None
Register RESFULCT 2
Full restart count
Register RESFULCT counts the number of Full restart that occurred in the
previous hour.
Release history
RESFULCT was made available in STP03/CSP05.
Register type
Peg
Associated register
None
Validation formula
None
Associated logs
Log number: 145
Logs 145 are issued whenever the Full restart procedure is initiated. There
should be a correlation between the number of logs issued for Full restart and
this register.
EXT register
None

OM groups: A-D 2-75
Register RESADJCT 2
Adjacent restart count
Register RESADJCT counts the number of Adjacent restart that occurred in
the previous hour.
Release history
RESADJCT was made available in STP03/CSP05.
Register type
Peg
Associated register
None
Validation formula
None
Associated logs
Log number: 145
Logs 145 are issued whenever the Adjacent restart procedure is initiated.
There should be a correlation between the number of logs issued for Adjacent
restart and this register.
EXT register
None
Register RESUNXCT 2
Unexpected TRM count
Register RESUNXCT counts the number of Unexpected TRM that occurred
in the previous hour.
Release history
RESUNXCT was made available in STP03/CSP05.
Register type
Peg
Associated register
None
Validation formula
None

2-76 OM groups: A-D
Associated logs
Log number: 145
Logs 145 are issued whenever the Unexpected TRM procedure is initiated.
There should be a correlation between the number of logs issued for
Unexpected TRM and this register.
EXT register
None

OM groups: A-D 2-77
C7ROUTER
CCS7 Router 2
OM group, C7ROUTER, captures operational information about a CCS7
Router. The Router receives messages from other CCS7 peripherals and
performs the routing function on these messages. The OMs will track the
number of messages and bytes processed by the Router, as well as the number
of times and the amount of time which the Router was out of service. In future
they will also track the high water marks of messages per second received in
the Router from various sources, messages discarded due to congestion, and
the number of times and amount of time when the Router was congested.
These measurements can be used to determine if the Router is operating
within its capacity and to give an indication of its workload during the OM
period.
Registers
C7ROUTER registers can be displayed at the DMS Maintenance and
C7RTMSR C7RTMSR2 C7RTBTR C7RTBTR2
C7INTOVL C7BUFOFL C7ILLPHW C7MTSHW
C7STHW C7TOTHW C7RTCNG C7RTCNGU
C7RTOOS C7RTOOSU
Release history
C7ROUTER was made available in BCS36.
Group structure
Key field: This field contains the Router number
Info field: This field has a two part structure consisting of the PM type and
PM number of the Router. (Currently only LIU7 is supported as the PM type)
Number of tuples: The number of tuples is 32.
Datafill
There is a one-to-one correspondance between routers data-filled in Table
C7ROUTER and visible tuples in the OM group.

2-78 OM groups: A-D
Validatin formula
None
None
Associated products
This OM group is associated with a CCS7 Router. The only peripheral
currently supported as a Router is the LIU7.
Register C7RTMSR 2
CCS7 Router MSUs received for routing (normal)
This register is pegged once for each MSU processed by the CCS7 Router by
invoking the routing functionality. Any MSUs received by the Router and
discarded due to Overload situations will not be counted in this OM.
Release history
C7RTMSR was made available in BCS36.
Register type
Peg
Associated register
Register C7RTBTR also measures messages to be routed, but it records the
number of BYTES received as opposed to the number of units.
Validation formula
None
Associated logs
Log number: None
EXT register
C7RTMSR2
Register C7RTBTR 2
CCS7 Router bytes received for routing (normal)
This register is pegged for each MSU processed by the CCS7 Router by
invoking the routing functionality. However this register accumulates the
number of BYTES received. The bytes of any MSUs received by the Router
and discarded due to Overload situations will not be counted in this OM.
Release history
C7RTMSR was made available in BCS36.

OM groups: A-D 2-79
Register type
Peg
Associated register
Register C7RTMSR also measures messages to be routed, but it records the
number of MSU UNITS received as opposed to the number of bytes.
Validation formula
None
Associated logs
Log number: None
EXT register
C7RTBTR2
Register C7INTOVL 2
Number of MSUs discarded due to interrupt overload
This register is pegged once whenever an MSU destined for the CCS7 Router
is discarded due to the detection of interrupt overload. The discarding of
MSUs is a protection measure to help the Router cope with congestion. This
OM is not currently activated.
Release history
C7INTOVL was made available in BCS36.
Register type
Peg
Associated register
None
Validation formula
None
Associated logs
Log number: None
EXT register
None
Register C7BUFOFL 2
Number of MSUs discarded due to buffer overflow
This register is pegged once whenever an MSU is discarded due to buffer
overflow within the CCS7 Router. This OM is not currently activated.

2-80 OM groups: A-D
Release history
C7BUFOFL was made available in BCS36.
Register type
Peg
Associated register
None
Validation formula
None
Associated logs
Log number: None
EXT register
None
Register C7ILLPHW 2
ILLP high water mark for messges/sec received
This register records the most ILLP messages received within a one second
interval during the OM period. This OM is not currently activated.
Release history
C7ILLPHW was made available in BCS36.
Register type
High Water
Associated register
None
Validation formula
None
Associated logs
Log number: None
EXT register
None

OM groups: A-D 2-81
Register C7MTSHW 2
MTS high water mark for messges/sec received
This register records the most MTS messages received within a one second
Release history
C7MTSHW was made available in BCS36.
Register type
High Water
Associated register
None
Validation formula
None
Associated logs
Log number: None
EXT register
None
Register C7STHW 2
ST high water mark for messges/sec received
This register records the most ST messages received within a one second
Release history
C7STHW was made available in BCS36.
Register type
High Water
Associated register
None
Validation formula
None
Associated logs
Log number: None

2-82 OM groups: A-D
EXT register
None
Register C7TOTHW 2
Total high water mark for messges/sec received
This register records the most messages received (from all three possible
sources) within a one second interval during the OM period. This OM is not
currently activated.
Release history
C7TOTHW was made available in BCS36.
Register type
High Water
Associated register
None
Validation formula
None
Associated logs
Log number: None
EXT register
None
Register C7RTCNG 2
Number of times the CCS7 Router was congested
This register is pegged once for each time that the Router reports that it is
experiencing congestion. This OM is not currently activated.
Release history
C7RTCNG was made available in BCS36.
Register type
Peg
Associated register
Register C7RTCNGU records the AMOUNT of time (in seconds) during
which the Router was experiencing congestion.
Validation formula
None

OM groups: A-D 2-83
Associated logs
Log number: None
EXT register
None
Register C7RTCNGU 2
Amount of time that the Router was congested
This register records the amount of time (in seconds based upon a 10 second
scan) during which the Router was experiencing congestion. This OM is not
currently activated.
Release history
C7RTCNGU was made available in BCS36.
Register type
Usage
Associated register
Register C7RTCNG records the NUMBER of times that the Router
experienced congestion.
Validation formula
None
Associated logs
Log number: None
EXT register
None
Register C7RTOOS 2
Number of times the CCS7 Router was OOS
This register is pegged once for each time that the Router enters an
Unavailable state(i.e. when the corresponding PM is out of service) from an
Available state (when the corresponding PM is In Service or In Service -
Trouble.
Release history
C7RTOOS was made available in BCS36.
Register type
Peg

2-84 OM groups: A-D
Associated register
The register C7RTOOSU records the AMOUNT of time (in seconds) that the
Router was in an Unavailable state.
Validation formula
None
Associated logs
Log number: None
EXT register
None
Register C7RTOOSU 2
Amount of time that the Router was OOS
This register records the amount of time (in seconds based upon a 10 second
scan) that the Router was in an Unavailable state.
Release history
C7RTOOSU was made available in BCS36.
Register type
Usage
Associated register
Register C7RTOOS records the NUMBER of times that the Router entered an
Unavailable state.
Validation formula
None
Associated logs
Log number: None
EXT register
None

OM groups: A-D 2-85
C7SROUTE
CCS7 Server Routing 2
The C7SROUTE OM group records the actions of the message router on the
LIU7 peripherals. For each node that can route messages to the CCS7 Server
is measures:
• OFFBOARD - requests routed off-board
• FALLBACK - requests routed to the fall-back path
• DISCARD - requests that are discarded because they could not be routed
Registers
C7SROUTE registers may be displayed at the DMS-MAP as follows:
OFFBOARD OFFBRD2 FALLBACK FALLBCK2
DISCARD DISCARD2
Release history
C7SROUTE was created in GSM10.
Group structure
Key field: Linkset Number
Matches linksets datafilled in Table C7LKSET.
Info field: Routing Info
Number of tuples: One per linkset datafilled.
The C7SERVER (CCS7 Server)OM group is associated with this group since
it collects information on messages received by each CCS7 Server.
Datafill
Each linkset is datafilled in Table C7LKSET.

2-86 OM groups: A-D
Validation formula
The number of messages routed to the CCS7 Servers should equal the number
of messages received.
Messages Routed Off-board = ∑ OFFBOARD in C7SROUTE
Alll LIU7s & CM
Messages Received By The CCS7 Servers = ∑ C7SVMSR in C7SERVER

All SVR7s
Messages Routed Off-board = Messages Received By The CCS7 Servers
Note: The pegging of LIU7 and SVR7 events are done remotely and only
uploaded to the CM periodically, therefore the C7SROUTE &
C7SERVER Active registers related to the LIU7s & SVR7s will not
necessarily be up to date. Also if a LIU7 or SVR7 goes out of service
before the upload occurs then the record of events may be lost.
Associated products
None
Register OFFBOARD 2
Routed off-board
The number of UDT / UDTS requests that are routed to an off-board CCS7
Server.
Release history
OFFBOARD was created in GSM10.
Register type
Peg
Associated register
None
Validation formula
Refer to “Validation formula” on page 2-86.
Associated logs
None
EXT register
OFFBORD2

OM groups: A-D 2-87
Register FALLBACK 2
Routed to fall-back path
The number of UDT / UDTS requests that are routed on the fall-back path.
Release history
FALLBACK was created in GSM10.
Register type
Peg
Associated register
None
Validation formula
None
Associated logs
None
EXT register
FALLBCK2
Register DISCARD 2
Discarded
The number of UDT / UDTS requests that could not be routed off-board or on
the fall-back path and therefore had to be discarded.
Register type
Peg
Associated register
None
Validation formula
None
Associated logs
None
EXT register
DISCARD2

2-88 OM groups: A-D
CALLINT
Call Interception 2
The CALLINT OM group gathers measurements on the resource usage of
call interception (that is, three-port conference bridges) and error conditions.
Registers
CALLINT registers may be displayed at the DMS-MAP as follows:
CICONF3U CNRFAIL CIMONERR
Release history
CALLINT was created in GSM06.
Group structure
CALLINT provides one tuple per DMS-MSC/Call Server.
Key field: None
Info field: None
None
Associated products
None
Register CICONF3U 2
Call Interception Three-Port Conference Bridge Usage
CICONF3U pegs the number of times the Call Interception uses a three-port
conference bridge.
Release history
CICONF3U was created in GSM06.
None
Associated logs
None

OM groups: A-D 2-89
Extension register
None
Validation formula
None
Register CNRFAIL 2
Call Notification Record Failure
CNRFAIL pegs the number of times sending of Call Notification Records

failed.
Release history
CNRFAIL was created in GSM06.
None
Associated logs
None
Extension register
None
Validation formula
None
Register CIMONERR 2
Call Interception Monitoring Call Error
CIMONERR pegs the number of error conditions occurring in the Monitoring

Call. The Monitoring Call is not necessarily taken down when CIMONERR
increments.
Release history
CIMONERR was created in GSM06.
None

2-90 OM groups: A-D
Associated logs
None
Extension register
None
Validation formula
None

OM groups: A-D 2-91
CAMMCSI
CAMel MCSI 2
Th CAMel MCSI OM group keeps track of the M-CSI-related activity for
each CAMEL Phase. This is a two dimensional OM group with one
dimension for the OM registers and the other dimension for the CAMEL
Phase applicable.
Registers
CAMMCSI registers may be displayed at the DMS-MAP as follows:
MMLUDV MMLUDV2 MMLUSV MMLUSV2
MMEXDE MMEXDE2 MMIMDE MMIMDE2
MMATMS MMATMS2 MMENRESP MMENRSP2
MMENDAMS MMENDMS2 MMENUXDV MMENUXD2
MMENUNSB MMENUNS2 MMENEVNS MMENENS2
MMENTOUT MMENTOT2 MMENFAIL MMENFL2
MMENSCAB MMSCAB2 MMENEXCP MMENEXC2
MMENSSFL MMENSSF2
Release history
CAMMCSI was created in UMTS03/GSM17.
Group structure
Number of tuples: Equal to the number of CAMEL Phases supported over
CAMEL Ph 3.
Key field: None
Info field: Indicates the phase of CAMEL
None
Associated products
CMS-MSC

2-92 OM groups: A-D
Register MMLUDV 2
MM Location Update event on Different Vlr
Register MMLUDV counts the number of times the Note MM Event message
was successfully built and dispatched to the gsmSCF for the MM event
‘Location Update to a different VLR Service Area’.
Release history
MMLUDV was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Validation formula
None
Extension register
MMLUDV2
MMU register
None
MMU EXT register

None
Register MMLUSV 2
MM Location Update event on Same VlrUMTS03
Register MMLUSV counts the number of times the Note MM Event message
‘Location Update to the same VLR Service Area’.
Release history
MMLUSV was created in UMTS03/GSM17.
Register type
Peg
None

OM groups: A-D 2-93
Associated logs
None
Validation formula
None
Extension register
MMLUSV2
MMU register
None
MMU EXT register

None
Register MMEXDE 2
MM EXplicit DEtach
Register MMEXDE counts the number of times the Note MM Event message
‘Explicit Detach of MS’.
Release history
MMEXDE was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Validation formula
None
Extension register
MMEXDE2
MMU register
None
MMU EXT register

None

2-94 OM groups: A-D
Register MMIMDE 2
MM Implicit DEtach
Register MMIMDE counts the number of times the Note MM Event message
‘Implicit Detach of MS’.
Release history
MMIMDE was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Validation formula
None
Extension register
MMIMDE2
MMU register
None
MMU EXT register

None
Register MMATMS 2
MM ATtach of MS
Register MMATMS counts the number of times the Note MM Event message
‘Attach of MS’.
Release history
MMATMS was created in UMTS03/GSM17.
Register type
Peg
None

OM groups: A-D 2-95
Associated logs
None
Validation formula
None
Extension register
MMATMS2
MMU register
None
MMU EXT register

None
Register MMENRESP 2
MM EveNt RESPonse received
Register MMENRESP counts the number of times the Note MM Event
Result was received from the gsmSCF.
Release history
MMENRESP was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Validation formula
None
Extension register
MMENRSP2
MMU register
None
MMU EXT register

None

2-96 OM groups: A-D
Register MMENTOUT 2
MM EveNt TimeOUT
Register MMENTOUT counts the number of times the T_MCSI (table
GSMTIMRS) timer got expired while waiting for a reply from gsmSCF after
sending the Note MM Event message.
Release history
MMENTOUT was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Validation formula
None
Extension register
MMENTOT2
MMU register
None
MMU EXT register

None
Register MMENFAIL 2
MM EveNt FAILure
Register MMENFAIL counts the number of times failure occurred at the VLR
while trying to send the Note MM Event message to the gsmSCF.
Release history
MMENFAIL was created in UMTS03/GSM17.
Register type
Peg
None

OM groups: A-D 2-97
Associated logs
None
Validation formula
None
Extension register
MMENFL2
MMU register
None
MMU EXT register

None
Register MMENSCAB 2
MM event Service Control point ABort
Register MMENSCAB counts the number of times the transaction which was
initiated by the VLR was aborted by gsmSCF.
Release history
MMENSCAB was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Validation formula
None
Extension register
MMSCAB2
MMU register
None
MMU EXT register

None

2-98 OM groups: A-D
Register MMENEXCP 2
MM EveNt EXception
Register MMENEXCP counts the number of times:
• spurious/extra parameters are received during decoding of the response
message from the gsmSCF
• ERROR with an unsupported error cause is received from the gsmSCF
• the gsmSCF responds with an incorrect application context
Release history
MMENEXCP was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Validation formula
None
Extension register
MMENEXC2
MMU register
None
MMU EXT register

None
Register MMENSSFL 2
MM EveNt SubSystem FaiLure
Register MMENSSFL counts the number of times the Note MM Event
message was not sent to the gsmSCF due to MAP subsystem failure.
Release history
MMENSSFL was created in UMTS03/GSM17.
Register type
Peg

OM groups: A-D 2-99
None
Associated logs
None
Validation formula
None
Extension register
MMENSSFL2
MMU register
None
MMU EXT register

None
Register MMENDAMS 2
MM EveNt error code DAta MiSsing
Register MMENDAMS counts the number of times an Error was recieved
with error code ‘Data Missing’.
Release history
MMENDAMS was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Validation formula
None
Extension register
MMENDMS2
MMU register
None

2-100 OM groups: A-D
MMU EXT register

None
Register MMENUXDV 2
MM EveNt UneXpected Data Value
Register MMENUXDV counts the number of times an Error was recieved
with error code ‘Unexpected Data Value’.
Release history
MMENUXDV was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Validation formula
None
Extension register
MMENUXD2
MMU register
None
MMU EXT register

None
Register MMENUNSB 2
MM EveNt UnkNown SuBsriber
Register MMENUNSB counts the number of times an Error was recieved
with error code ‘Unknown Subscriber’.
Release history
MMENUNSB was created in UMTS03/GSM17.
Register type
Peg

OM groups: A-D 2-101
None
Associated logs
None
Validation formula
None
Extension register
MMENUNS2
MMU register
None
MMU EXT register

None
Register MMENEVNS 2
MM EveNt EVent Not Supported
Register MMENEVNS counts the number of times an Error was recieved
with error code ‘MM Event Not Supported’.
Release history
MMENEVNS was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Validation formula
None
Extension register
MMENENS2
MMU register
None

MMU EXT register

None

CAPCCTAS
Specific CAMEL Call Type Analysis 2
This OM group is created to measure the call events between CAMEL
subscriber and UNICOM mobile subscriber.
The pegging implementation is not included in this feature.
Registers
CAPCCTAS registers may be displayed at the DMS-MAP as follows:
CATTCU CATTCU2 CATTUC CATTUC2
CANSCU CANSCU2 CANSUC CANSUC2
Release history
CAPCCTAS was created in GSM06 and was modified in UMTS03/GSM17.
Group structure
Note: Info field “CAP_PHASE” displays the supported CAMEL phases
(Phase2 and Phase3).
Number of tuples: 2 (PHASE2 & PHASE3)
Key field: Nil
Info field: CAP_PHASE
None
Associated products
CMS-MSC
Register CATTCU 2
CMCC CAMEL subscriber calls Unicom mobile subscriber, call attempts
This register is increased by 1, when the calling party is CAMEL subscriber
and the called party is Unicom. mobile subscriber (by discriminating the
number).
It is a global register and only has the definition in this feature.
Release history
CATTCU was created in GSM06 and was modified in UMTS03/GSM17.

Register type
Usage
None
Associated logs
None
Extension register
CATTCU2
Validation formula
None
Register CATTUC 2
Unicom mobile subscriber calls CAMEL subscriber, call attempts
This register is increased by 1, when the called party is CAMEL subscriber
and the calling party is Unicom mobile subscriber (by discriminating the
number).
Release history
CATTUC was created in GSM06 and was modified in UMTS03/GSM17.
Register type
Usage
None
Associated logs
None
Extension register
CATTUC2
Validation formula
None

Register CANSCU 2
CAMEL subscriber calls Unicom mobile subscriber, call answer
This register is increased by 1, when the calling party is CAMEL subscriber,
the called party is Unicom. mobile subscriber (by discriminating the number)
and the call is answered.
Release history
CANSCU was created in GSM06 and was modified in UMTS03/GSM17.
Register type
Usage
None
Associated logs
None
Extension register
CANSCU2
Validation formula
None
Register CANSUC 2
Unicom mobile subscriber calls CAMEL subscriber, call answer
This register is increased by 1, when the called party is CAMEL subscriber,
the calling party is Unicom mobile subscriber (by discriminating the number)
and the call is answered.
Release history
CANSUC was created in GSM06 and was modified in UMTS03/GSM17.
Register type
Usage
None
Associated logs
None

Extension register
CANSUC2
Validation formula
None


CAPOCSI
CAMEL Originating CSI 2
This OM group is created for O-CSI to measure:
• InitDPs for DP2 trigger
• InitDPs for DP2 triggered for ROAMERs
• InitDPs for DP2 triggered on Call forward
• CAMEL messages
Registers
CAPOCSI registers may be displayed at the DMS-MAP as follows:
ODP2 ODP22 ODP2R ODP2R2
ODP2CF ODP2CF2 ODP2RCF ODP2RCF2
OCONNECT OCONNEC2 OCONT OCONT2
OCONTARG OCONTAR2 OETC OETC2
OCTR OCTR2 OACH OACH2
OACR OACR2 ODFC ODFC2
OFCI OFCI2 OSCI OSCI2
ORRB ORRB2 OERB OERB2
Release history
CAPOCSI was created in GSM06.
Group structure
Number of tuples: 3 (Number of CAMEL Phases supported by O-CSI)
Key field: Nil
Info field: OCSI_PHASE
None
Associated products
CMS-MSC

Register ODP2 2
CAMEL DP2 (Collected Info DP) triggers
This register is increased by 1, when CAMEL Initial DP operations is build
and sent by the dP2 in the IN originating call model to the SCF.
Release history
ODP2 was created in GSM06.
None
Associated logs
None
Extension register
ODP22
Validation formula
None
Register ODP2R 2
CAMEL DP2 triggers for Roamers
This register is increased by 1 when CAMEL InitialDP operation for a
Roamer subscriber is build and sent by the SSF at DP2 in the IN originating
call model to the SCP.
Release history
ODP2R was created in GSM06.
None
Associated logs
None
Extension register
ODP2R2
Validation formula
None

Register ODP2CF 2
CAMEL DP2 CF Triggers
This register is increased by 1 when DP2 is detected on call forwarded call in
the O-BCSM and the InitDP is build and sent by SSF.
Release history
ODP2CF was created in GSM06.
None
Associated logs
None
Extension register
ODP2CF2
Validation formula
None
Register ODP2RCF 2
CAMEL DP2 CF triggers for Roamers
This register is increased by 1 when DP2 is detected on a call forwarded call
for a Roamer subscriber in the O-BSCM and the SSF is invoked.
Release history
ODP2RCF was created in GSM06.
None
Associated logs
None
Extension register
ODP2RC2
Validation formula
None
Register OCONNECT 2
CAMEL Connect
This register is increased by 1 when CAMEL Connect operation is received
from the SCF and processed successfully by the SSF.

Release history
OCONNECT was created in GSM06.
None
Associated logs
None
Extension register
OCONNEC2
Validation formula
None
Register OCONT 2
CAMEL Continue
This register is increased by 1 when CAMEL Continue operation is received
Release history
OCONT was created in GSM06.
None
Associated logs
None
Extension register
OCONT2
Validation formula
None
Register OCONTARG 2
CAMEL continue with Argument
This register is increased by 1 when CAMEL Continue with Argument
operations is received from the SCF and processed successfully by the SSF.
Release history
OCONTARG was created in GSM06.

None
Associated logs
None
Extension register
OCONTAR2
Validation formula
None
Register OETC 2
CAMEL Establish Temporary Connection
This register is increased by 1 if CAMEL EstablishTemporaryConnection
operation is received by the SSF.
Release history
OETC was created in GSM06.
None
Associated logs
None
Extension register
OETC2
Validation formula
None
Register OCTR 2
CAMEL Connect to Resource
This register is increased by 1 when the ConnectToResource message
received by SSF.
Release history
OCTR was created in GSM06.
None

Associated logs
None
Extension register
OCTR2
Validation formula
None
Register OACH 2
CAMEL Apply Charging
This register is increased by 1 if an Apply Charging operation is received by
the SSF.
Release history
OACH was created in GSM06.
None
Associated logs
None
Extension register
OACH2
Validation formula
None
Register OACR 2
CAMEL Apply Charging Report
This register is increased by 1 if an Apply Charging Report is sent by the SSF.
Release history
OACR was created in GSM06.
None
Associated logs
None
Extension register
OACR2

Validation formula
None
Register ODFC 2
CAMEL Disconnect Forward Connection
This register is increased by 1 when a CAMEL Disconnect Forward
Connection operation is received by SSF.
Release history
ODFC was created in GSM06.
None
Associated logs
None
Extension register
ODFC2
Validation formula
None
Register OFCI 2
CAMEL Furnish Charging-Information
This register is increased b 1 when a CAMEL FurnishChargingInformation
operation is received from the SCF and processed successfully by the SSF.
Release history
OFCI was created in GSM06.
None
Associated logs
None
Extension register
OCFI2
Validation formula
None

Register OSCI 2
CAMEL Send Charging-Information
This register is increased by 1 when a CAMEL Send Charge Info operation is
received by SSF.
Release history
OSCI was created in GSM06.
None
Associated logs
None
Extension register
OSCI2
Validation formula
None
Register ORRB 2
CAMEL Request Report BSCM Event
This register is increased by 1 when the SCP return a RRBE to the SSF to arm
one or more EDPs.
Release history
ORRB was created in GSM06.
None
Associated logs
None
Extension register
ORRB2
Validation formula
None
Register OERB 2
CAMEL Event Report BCSM
This register is increased by 1 when SSF notifies the SCP of armed EDP by
sending an EventReport BCSM operation.

Release history
OERB was created in GSM06.
None
Associated logs
None
Extension register
OERB2
Validation formula
None


CAPOCSI2
CAMEL Originating CSI - 2 2
The OM group, CAMEL Originating CSI - 2 (CAPOCSI2), is an extension
OM group for CAPOCSI. This OM group measures CAMEL operations for
O-CSI. New register OEENDS (extn. register OEENDS2) is added to OM
group CAPOCSI2 to measure the number of Empty End (for O-CSI)
operations sent to SCP.
Registers
CAPOCSI2 registers may be displayed at the DMS-MAP as follows:
OCIRQ OCIRQ2 OCIR OCIR2
ORSTTMR ORSTTMR2 OPA OPA2
OSRR OSRR2 OPCUI OPCUI2
OPCUIACK OPCUIAC2 ORELCALL ORELCAL2
OCANCEL OCANCEL2 OAT OAT2
OATACK OATACK2 OEENDR OEENDR2
OEENDS OEENDS2
Release history
CAPOCSI2 was created in GSM06 and modified in UMTS03/GSM17.
Group structure
Note: Info field "OCSI_PHASE" displays the supported CAMEL phases
(Phase1, Phase2 and Phase3) by O-CSI.
Key field: Nil
Info field: OCSI_PHASE
None
Associated products
DMS-MSC

Register OCIRQ 2
CAMEL Call Information Request
This register is increased by 1 if a CAMEL Call Information is received by
the SSF.
Release history
OCIRQ was created in GSM06.
None
Associated logs
None
Extension register
OCIRQ2
Validation formula
None
Register OCIR 2
CAMEL Call Information report
This register is increased by 1 when a CAMEL Call Information Report is
sent by SSF.
Release history
OCIR was created in GSM06.
None
Associated logs
None
Extension register
OCIR2
Validation formula
None
Register ORSTTMR 2
CAMEL Reset timer
This register is increased by 1 when the SSF receives a ResetTimer operation
from the SCF.

Release history
ORSTTMR was created in GSM06.
None
Associated logs
None
Extension register
ORSTTMR2
Validation formula
None
Register OPA 2
CAMEL Play Announcement
This register is increased by 1 when the Play Announcement message
received by SSF from SCF.
Release history
OPA was created in GSM06.
None
Associated logs
None
Extension register
OPA2
Validation formula
None
Register OSRR 2
CAMEL Specialized Resource Report
This register is increased by 1 when the Specialized Resource Report
operation is successfully sent from SSF to the SCF.
Release history
OSRR was created in GSM06.

None
Associated logs
None
Extension register
OSRR2
Validation formula
None
Register OPCUI 2
CAMEL Prompt And Collect User Information
This register is increased by 1 when the PCUI
(PromptAndCollectUserInformation) message received by SSF from SCF.
Release history
OPCUI was created in GSM06.
None
Associated logs
None
Extension register
OPCUI2
Validation formula
None
Register OPCUIACK 2
CAMEL Prompt and Collect User Information ACK
This register is increased by 1 when the PCUI_ACK message received by
SSF from SRF.
Release history
OPCUIACK was created in GSM06.
None

Associated logs
None
Extension register
OPCUIAC2
Validation formula
None
Register ORELCALL 2
CAMEL Release Call
This register is increased by 1 when CAMEL ReleaseCall operation is
received from the SCF and processed successfully by the SSF.
Release history
ORELCALL was created in GSM06.
None
Associated logs
None
Extension register
ORELCAL2
Validation formula
None
Register OCANCEL 2
CAMEL CAP Cancel
This register is increased by 1 when CANCEL operation is received by SSF.
Release history
OCANCEL was created in GSM06.
None
Associated logs
None
Extension register
OCANCEL2

Validation formula
None
Register OAT 2
CAMEL Activity Test
This register is increased by 1 if an CAMEL ActifityTest operation in
received by the SSF.
Release history
OAT was created in GSM06.
None
Associated logs
None
Extension register
OAT2
Validation formula
None
Register OATACK 2
CAMEL Activity Test ACK
This register is increased by 1 when a Activity Test ACK is sent from SSF to
SCF.
Release history
OATACK was created in GSM06.
None
Associated logs
None
Extension register
OATACK2
Validation formula
None

Register OEENDR 2
CAMEL Empty End Received
This register is increased by 1 when an Empty End message is received from
SCF by SSF.
Release history
OEENDR was created in GSM06.
None
Associated logs
None
Extension register
OEENDR2
Validation formula
None
Register OEENDS 2
CAMEL Empty End Sent for CAMEL O-CSI
Register OEENDS is increased by 1, when an Empty End message is sent
from SSF to SCF to end the transaction for CAMEL O-CSI.
Release history
OEENDS was created in UMTS03/NSS17.
Register type
Peg
None
Associated logs
None
Extension register
OEENDS2
Validation formula
None

CAPSFAF
CAMEL Operations (SCF-ASSF) 2
This OM group, (CAMEL Operations (SCF-ASSF) (CAPSFAF), is used to
monitor the amount of successful CAP operations, which are involved in
relay scenario, interacting between the SCF and Assisting SSF.
In the ASSF mode the only valid operation coming in end package from the
SCP is RLC. Other operations rather than RLC coming in from the SCF will
be treated as unsupported operations and registers in this group will be treated
as unsupported operations and registers in this group will not be pegged.

and Phase 3) and the registers themselves. For implementation of pegging
Registers
CAPSFAF registers can be displayed at the DMS Maintenance and
SCFCTR SCFCTR2 ASFARI ASFARI2
SCFPA SCFPA2 ASFSRR ASFSRR2
SCFPCUI SCFPCUI2 ASFPCUIA ASFPCUA2
SCFRLC SCFRLC2 SCFRST SCFRST2
SCFCAN SCFCAN2 SCFAT SCFAT2
SCFDFC SCFDFC2
Release history
CAPSFAF was made available in GSM16.
Group structure
Number of Tuples: 2
Key field: None
Info field: None

None
Validation Formula
None
Associated products
None
Register SCFCTR 2
CAMEL ConnectTo Resource (SCF--ASSF)

failed.
Release history
SCFCTR was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register ASFARI 2
CAMEL AssistRequestinstructions (ASSF->SCF)

failed.
Release history
ASFARI was made available in GSM16.

None
Associated logs
None
Extension register
None
Validation formula
None
Register SCFPA 2
CAMEL PlayAnnouncement (SCF->ASSF)

failed.
Release history
SCFPA was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register ASFSRR 2
CAMEL SpecializedResourceReport (ASSF->SCF)

failed.

Release history
ASFSRR was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register SCFPCUI 2
CAMEL PromptAndCollectUserinformatio (SCF->ASSF)

failed.
Release history
SCFPCUI was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register ASFPCUIA 2
CAMEL PromptAndCollectUserinformationAck (ASSF->SCF)


failed.
Release history
ASFPCUIA was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register SCFRLC 2
CAMEL ReleaseCall (SCF->ASSF)

failed.
Release history
SCFRLC was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None

Register SCFRST 2
CAMEL ResetTimerl (SCF->ASSF)

failed.
Release history
SCFRST was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register SCFCAN 2
CAMEL Cancel (SCF->ASSF)

failed.
Release history
SCFCAN was made available in GSM16.
None
Associated logs
None
Extension register
None

Validation formula
None
Register SCFAT 2
CAMEL Activity Test (SCF->ASSF)

failed.
Release history
SCFAT was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register SCFDFC 2
CAMEL DisconnectForwardConnection (SCF->ASSF)

failed.
Release history
SCFDFC was made available in GSM16.
None
Associated logs
None

Extension register
None
Validation formula
None

CAPAFRF
CAMEL Operations (ASSF-SRF) 2
This OM group, CAMEL Operations (ASSF-SRF)(CAPAFRF), is used to
monitor the amount of successful CAP operations which are involved in relay
scenarios, interacting between the ASSF and internal SRF.

and Phase 3) and the registers themselves. The implementation of pegging
Phase 3 resisters is not included in this feature.
Registers
CAPAFRF registers can be displayed at the DMS Maintenance and
ASFPA ASFPA2 SRFSRR SRFSRR2
ASFPCUI ASFPCUI2 SRFPCUIA SRFPCUA2
ASFCAN ASFCAN2
Release history
CAPAFRF was made available in GSM16.
Group structure
Number of Tuples: 2
Key field: None
Info field: None
None
Register ASFPA 2
CAMEL PlayAnnouncement (ASSF->SRF)


failed.
Release history
ASFPA was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register SRFSRR 2
CAMEL SpecializedResourceReport (SRF->ASSF)

failed.
Release history
SRFSRR was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None

Register ASFPCUI 2
CAMEL PromptAndCollectUserInformation (ASSF->SRF)

failed.
Release history
ASFPCUI was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register SRFPCUIA 2
CAMEL PromptAndCollectUserInformationAck (SRF->ASSF)

failed.
Release history
SRFPCUIA was made available in GSM16.
None
Associated logs
None
Extension register
None

Validation formula
None
Register ASFCAN 2
CAMEL Cancel (SRF->ASSF)

failed.
Release history
ASFCAN was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None

CAPSFAFE
CAMEL error/reject in replaying (SCF-ASSF) 2
This OM group, CAMEL error/reject in replaying SCF-ASSF) (CAPSFAFE),
is used to monitor the amount of failed CAP operations between SCF and
ASSF.
This OM group is a 2-dimensional group which is denied by protocol (Phase

2 and Phase 3) and the registers themselves. The implementation of pegging
Registers
CAPSFAFE registers can be displayed at the DMS Maintenance and
AERRCTR AREJCTR SERRARI SREJARI
AERRPA AREJPA SREJSRR AERRPCUI
AREJPCUI SREJPCUA AERRRST AREJRST
AERRCAN AREJCAN AERRDFC AREJDFC
AREJRLC AREJAT CPFCAS
Release history
CAPSFAFE was made available in GSM16.
Group structure
Number of Tuples: 2
Key field: None
Info field: None
None
Validation formula
None

Associated products
None
Register AERRCTR 2
CAMEL ConnectTo Resource (SCF->ASSF)

failed.
Release history
AERRCTR was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register AREJCTR 2

failed.
Release history
AREJCTR was made available in GSM16.
None
Associated logs
None

Extension register
None
Validation formula
None
Register SERRARI 2

failed.
Release history
SERRARI was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register SREJARI 2

failed.
Release history
SREJARI was made available in GSM16.
None

Associated logs
None
Extension register
None
Validation formula
None
Register AERRPA 2

failed.
Release history
AERRPA was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register AREJPA 2

failed.
Release history
AREJPA was made available in GSM16.

None
Associated logs
None
Extension register
None
Validation formula
None
Register SREJSRR 2

failed.
Release history
SREJSRR was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register AERRPCUI 2

failed.

Release history
AERRPCUI was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register AREJPCUI 2

failed.
Release history
AREJPCUI was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register SREJPCUA 2


failed.
Release history
SREJPCUA was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register AERRRST 2

failed.
Release history
AERRRST was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None

Register AREJRST 2

failed.
Release history
AREJRST was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register AERRCAN 2

failed.
Release history
AERRCAN was made available in GSM16.
None
Associated logs
None
Extension register
None

Validation formula
None
Register AREJCAN 2

failed.
Release history
AREJCAN was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register AERRDFC 2

failed.
Release history
AERRDFC was made available in GSM16.
None
Associated logs
None

Extension register
None
Validation formula
None
Register AREJDFC 2

failed.
Release history
AREJDFC was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register AREJAT 2

failed.
Release history
AREJAT was made available in GSM16.
None

Associated logs
None
Extension register
None
Validation formula
None
Register AREJRLC 2

failed.
Release history
AREJRLC was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register CPFCAS 2

failed.
Release history
CPFCAS was made available in GSM16.

None
Associated logs
None
Extension register
None
Validation formula
None

CAPAFRFE
CAMEL error/reject in replaying (ASSF-SRF) 2
This OM group, CAMEL error/reject in replaying ASSF-SRF) (CAPAFRFE),
is used to monitor the amount of failed CAP operations between ASSF and
SRF involved in the relay function.
This OM group is a 2-dimensional group which is denied by protocol (Phase

2 and Phase 3) and the registers themselves. The implementation of pegging
Registers
CAPAFRFE registers can be displayed at the DMS Maintenance and
RERRPA RREJPA AREJSRR RERRPCUI
RREJPCUI AREJPCUA RERRCAN RREJCAN
CPFASI
Release history
CAPAFRFE was made available in GSM16.
Group structure
Number of Tuples: 2
Key field: None
Info field: None
None
Validation Formula
None
Associated products
None

Register RREJPA 2
CAMEL REJECT for PlayAnnouncement (SRF--ASSF)
This register is pegged when SRF send REJECT to ASSF for PA.
Release history
RREJPA was made available in GSM16.
Register type
Peg
Associated register
None
Validation formula
None
Associated logs
Log number: None
EXT register
None
Register AREJPCUA 2
This register is pegged when ASSF REJECT to SRF for PCUI_ACK.
Release history
AREJPCUA was made available in GSM16.
Register type
Peg
Associated register
None
Validation formula
None
Associated logs
Log number: None
EXT register
None

Register RERRPA 2

failed.
Release history
RERRPA was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register RREJAA 2

failed.
Release history
RREJAA was made available in GSM16.
None
Associated logs
None
Extension register
None

Validation formula
None
Register AREJSRR 2

failed.
Release history
AREJSRR was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register RERRPCUI 2

failed.
Release history
RERRPCUI was made available in GSM16.
None
Associated logs
None

Extension register
None
Validation formula
None
Register RREJPCUI 2

failed.
Release history
RREJPCUI was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register AREJCUA 2

failed.
Release history
AREJCUA was made available in GSM16.
None

Associated logs
None
Extension register
None
Validation formula
None
Register RERRCAN 2

failed.
Release history
RERRCAN was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None
Register RREJCAN 2

failed.
Release history
RREJCAN was made available in GSM16.

None
Associated logs
None
Extension register
None
Validation formula
None
Register CPFASI 2

failed.
Release history
CPFASI was made available in GSM16.
None
Associated logs
None
Extension register
None
Validation formula
None

CAPDCSI
CAMEL Dialed Service CSI 2
This OM group is used to count the triggers and operations for D-CSI.
They are:
• InitDPs for DP3 triggered on Call forward
• CAMEL messages
Registers
CAPDCSI registers may be displayed at the DMS-MAP as follows:
DDP3 DDP32 DDP3R DDP3R2
DDP3CF DDP3CF2 DDP3RCF DDP3RCF2
DCONNECT DCONNEC2 DCONT DCONT2
DCONTARG DCONTAR2 DETC DETC2
DCTR DCTR2 DDFC DDFC2
DFCI DFCI2 DSCI DSCI2
DRSTTMR DRSTTMR2 DPA DPA2
DSRR DSRR2
Release history
CAPDCSI was created in GSM16.
Group structure
Number of tuples: 1(Number of CAMEL Phases supported by O-CSI)
Key field: None
Info field: DCSI_PHASE
None

Associated products
DMS-MSC
Register DDP3 2
CAMEL DP3 Triggers
This register is increased by 1 when CAMEL InitialDP operation is built and
sent by the SSF at DP3 in the IN originating call model to the SCP.
Release history DDP3

was made available in GSM16.
None
Associated logs
None
Extension register
DDP32
Validation formula
None
Register DDP3R 2
CAMEL DP3 Triggers for Roamers
Roamer subscriber is built and sent by the SSF at DP3 in the IN originating
Release history
DDP3R was made available in GSM16.
None
Associated logs
None
Extension register
DDP3R2
Validation formula
None

Register DDP3CF 2
This register is increased by 1 when DP3 is detected on call forwarded call in
the O-BCSM and the InitDP is built and sent by SSF.
Release history
DDP3CF was made available in GSM16.
None
Associated logs
None
Extension register
DDP3CF2
Validation formula
None
Register DDP3RCF 2
This register is increased by 1 when DP3 is detected for a Roamer subscriber
in the O-BCSM and the SSF is invoked.
Release history
DDP3RCF was made available in GSM16.
None
Associated logs
None
Extension register
DDP3RCF2
Validation formula
None
Register DCONNECT 2
CAMEL Connect

Release history
DCONNECT was made available in GSM16.
None
Associated logs
None
Extension register
DCONNEC2
Validation formula
None
Register DCONT 2
CAMEL Continue
Release history
DCONT was made available in GSM16.
None
Associated logs
None
Extension register
DCONT2
Validation formula
None
Register DCONTARG 2
CAMEL Continue with Argument
Release history
DCONTARG was made available in GSM16.

None
Associated logs
None
Extension register
DCONTAR2
Validation formula
None
Register DETC 2
Release history
DETC was made available in GSM16.
None
Associated logs
None
Extension register
DETC2
Validation formula
None
Register DCTR 2
This register is increased by 1 when the ConnedtToResource message
received.
Release history
DCTR was made available in GSM16.
None

Associated logs
None
Extension register
DCTR2
Validation formula
None
Register DDFC 2
This register is increased by 1 if an CAMEL DisconnectForwardConnection
Release history
DDFC was made available in GSM16.
None
Associated logs
None
Extension register
DDFC2
Validation formula
None
Register DFCI 2
This register counts the number of times that an CAMEL
FurnishChargingInformation operation is received from the SCF and
processed successfully by the SSF.
Release history
DFCI was made available in GSM16.
None
Associated logs
None

Extension register
DFCI2
Validation formula
None
Register DSCI 2
This register is increased by 1 when a CAMEL Send Charge info operation is
received by SSF.
Release history
DSCI was made available in GSM16.
None
Associated logs
None
Extension register
DSCI2
Validation formula
None
Register DRSTTMR 2
CAMEL Reset Timer
from the SCF.
Release history
DRSTTMR was made available in GSM16.
None
Associated logs
None
Extension register
DRSTTMR2

Validation formula
None
Register DPA 2
This register is increased by 1 when the PlayAnnouncement message
Release history
DPA was made available in GSM16.
None
Associated logs
None
Extension register
DPA2
Validation formula
None
Register DSRR 2
This register is increased by 1 when the SpecializedResourceReport operation
is successfully sent from SSF to the SCF.
Release history
DSRR was made available in GSM16.
None
Associated logs
None
Extension register
DSRR2
Validation formula
None


CAPDCSI2
CAMEL Dialed Service CSI 2
This OM group is the extension group for CAPDCSI.
Registers
CAPDCSI2 registers may be displayed at the DMS-MAP as follows:
DPCUI DPCUI2 DPCUIACK DPCUIAC2
DRELCALL DRELCAL2 DCANCEL DCANCEL2
DAT DAT2 DATACK DATACK2
DEENDS DEENDS2 DEENDR DEENDR2
Release history
CAPDCSI2 was created in GSM16.
Group structure
Number of tuples: 1
Key field: None
None
Associated products
DMS-MSC
Register DPCUI 2
CAMELPrompt And Collect User Information
Release history
DPCUI was made available in GSM16.
None

Associated logs
None
Extension register
CPDUI2
Validation formula
None
Register DPCUIACK 2
CAMEL Prompt And Collect User Information ACK
SSF from SRF.
Release history
DPCUIACK was made available in GSM16.
None
Associated logs
None
Extension register
DPCUIAC2
Validation formula
None
Register DRELCALL 2
CAMEL Release Call
Release history
DRELCALL was made available in GSM16.
None
Associated logs
None

Extension register
CRELCAL2
Validation formula
None
Register DCANCEL 2
CAMEL CAP Cancel
Release history
DCANCEL was made available in GSM16.
None
Associated logs
None
Extension register
DCANCEL2
Validation formula
None
Register DAT 2
CAMEL Activity Test
This register is increased by 1 if an CAMEL ActivityTest operation is
Release history
DAT was made available in GSM16.
None
Associated logs
None
Extension register
DAT2
Validation formula
None

Register DATACK 2
This register is increased by 1 when a Activity test ack is sent from SSF to
SCF.
Release history
DATACK was made available in GSM16.
None
Associated logs
None
Extension register
DATACK2
Validation formula
None
Register DEENDS 2
CAMEL Empty End Sent
This register is increased by 1 when an Empty End message is sent from SSF
to SCF.
Release history
DEENDS was made available in GSM16.
None
Associated logs
None
Extension register
DEENDS2
Validation formula
None
Register DEENDR 2
SCF by SSF.

Release history
DEENDR was made available in GSM16.
None
Associated logs
None
Extension register
DEENDR2
Validation formula
None

CAPNCSI
CAMEL Network Service CSI 2
This OM group is used for N-CSI to measure the number of
• InitDPs for DP3 triggered on call forward
• CAMEL messages
Registers
CAPNCSI registers may be displayed at the DMS-MAP as follows:
NDP3 NDP32 NDP3R NDP3R2
NDP3CF NDP3CF2 NDP3RCF NDP3RCF2
NCONNECT NCONNEC2 NCONT NCONT2
NCONTARG NCONTAR2 NETC NETC2
NCTR NCTR2 NACH NACH2
NACR NACR2 NDFC NDFC2
NRRB NRRB2 NERB NERB2
NFCI NFCI2 NSCI NSCI2
Release history
CAPNCSI was created in GSM16.
Group structure
Number of tuples: 1(number of CAMEL phases supported by O-CSI)
Key field: None
None
Associated products
DMS-MSC

Register NDP3 2
CAMEL DP3 Triggers
Release history
NDP3 was made available in GSM16.
None
Associated logs
None
Extension register
NDP32
Validation formula
None
Register NDP3R 2
Roamer subscriber is built and sent by the SSF at DP3 in the IN originating
Release history
NDP3R was made available in GSM16.
None
Associated logs
None
Extension register
NDP3R2
Validation formula
None

Register NDP3CF 2
This register is increased by 1 when DP3 is detected on a call forwarded call
in the O-BCSM and the SSF in invoked.
Release history
NDP3CF was made available in GSM16.
None
Associated logs
None
Extension register
NDP3CF2
Validation formula
None
Register NDP3RCF 2
CAMEL DP3 CF triggers for Roamers
This register is increased by 1 when CF DP2 detection point is triggered for
Roamer subscriber in the Virtual O-GCSM and the SSF is invoked due to N-
CSI.
Release history
NDP3RCF was made available in GSM16.
None
Associated logs
None
Extension register
NDP3RCF2
Validation formula
None

Register NCONNECT 2
CAMEL Connect
Release history
NCONNECT was made available in GSM16.
None
Associated logs
None
Extension register
NCONNEC2
Validation formula
None
Register NCONT 2
CAMEL Continue
This register is increased by 1 when Camel continue operation is received
Release history
NCONT was made available in GSM16.
None
Associated logs
None
Extension register
NCONT2
Validation formula
None
Register NCONTARG 2
CAMEL Continue with Argument

Release history
NCONTARG was made available in GSM16.
None
Associated logs
None
Extension register
NCONTAR2
Validation formula
None
Register NETC 2
Release history
NETC was made available in GSM16.
None
Associated logs
None
Extension register
NETC2
Validation formula
None
Register NCTR 2
received.
Release history
NCTR was made available in GSM16.

None
Associated logs
None
Extension register
NCTR2
Validation formula
None
Register NACH 2
This register is increased by 1 if an ApplyCharging operation is received by
the SSF.
Release history
NACH was made available in GSM16.
None
Associated logs
None
Extension register
NACH2
Validation formula
None
Register NACR 2
This register is increased by 1 if an ApplyCharging operation is sent by the
SSF.
Release history
NACR was made available in GSM16.
None

Associated logs
None
Extension register
NACR2
Validation formula
None
Register NDFC 2
operations is received by the SSF.
Release history
NDFC was made available in GSM16.
None
Associated logs
None
Extension register
NDFC2
Validation formula
None
Register NRRB 2
CAMEL Request Report BCSM Event
one or more EDPs.
Release history
NRRB was made available in GSM16.
None
Associated logs
None

Extension register
NRRB2
Validation formula
None
Register NERB 2
This register is increased by 1 when BCSM reaches the event armed as an
EDP and the SSF notified the SCP by sending an EventReportBCSM
operation.
Release history
NERB was made available in GSM16.
None
Associated logs
None
Extension register
NERB2
Validation formula
None
Register NFCI 2
Furnish Charging-Information
This register counts the number of times that an Camel
Release history
NFCI was made available in GSM16.
None
Associated logs
None
Extension register
NFCI2

Validation formula
None
Register NSCI 2
This register is increased by 1 when a CAMEL Send Charge Info operation is
received by SSF.
Release history
NSCI was made available in GSM16.
None
Associated logs
None
Extension register
NSCI2
Validation formula
None

CAPNCSI2
CAMEL Network Service CSI-2 2
This is the extension OM group for CAPNCSI.
Registers
CAPNCSI2 registers may be displayed at the DMS-MAP as follows:
NCIRQ NCIRQ2 NCIR NCIR2
NRSTTMR NRSTTMR2 NPA NPA2
NSRR NSRR2 NPCUI NPCUI2
NPCUIACK NPCUIAC2 NRELCALL NRELCAL2
NCANCEL NCANCEL2 NAT NAT2
NATACK NATACK2 NEENDS NEENDS2
NEENDR NEENDR2
Release history
CAPNCSI2 was created in GSM16.
Group structure
Number of tuples: 1
Key field: None
Info field: NCSI_PHASE
None
Associated products
DMS-MSC
Register NCIRQ 2
This register is increased by 1 if an CAMEL Call Information Request is

Release history
NCIRQ was made available in GSM16.
None
Associated logs
None
Extension register
NCIRQ2
Validation formula
None
Register NCIR 2
CAMEL Call Information Report
This register is increased by 1 when a CAMEL Call Information Report is
sent by SSF.
Release history
NCIR was made available in GSM16.
None
Associated logs
None
Extension register
NCIR2
Validation formula
None
Register NRSTTMR 2
CAMEL Reset Timer
from the SCF.
Release history
NRSTTMR was made available in GSM16.

None
Associated logs
None
Extension register
NRSTTMR2
Validation formula
None
Register NPA 2
Release history
NPA was made available in GSM16.
None
Associated logs
None
Extension register
NPA2
Validation formula
None
Register NSRR 2
this register is increased by 1 when the SpecializedResourceReport operation
Release history
NSRR was made available in GSM16.
None

Associated logs
None
Extension register
NSRR2
Validation formula
None
Register NPCUI 2
CAMEL Prompt And Collect User Information
(PromptAndCollectUserInfomration) message received by SSF from SCF.
Release history
NPCUI was made available in GSM16.
None
Associated logs
None
Extension register
NPCUI2
Validation formula
None
Register NPCUIACK 2
CAMEL Prompt And Collect User Information ACK
SSF from SRF.
Release history
NPCUIACK was made available in GSM16.
None
Associated logs
None

Extension register
NPCUIAC2
Validation formula
None
Register NRELCALL 2
CAMEL Release Call
Release history
NRELCALL was made available in GSM16.
None
Associated logs
None
Extension register
NRELCAL2
Validation formula
None
Register NCANCEL 2
CAMEL CAP Cancel
Release history
NCANCEL was made available in GSM16.
None
Associated logs
None
Extension register
NCANCEL2
Validation formula
None

Register NAT 2
CAMEL Activity Test
This register is increased by 1 if an CAMEL ActifityTest operation is
Release history
NAT was made available in GSM16.
None
Associated logs
None
Extension register
NAT2
Validation formula
None
Register NATACK 2
This register is increased by 1 when a Activity test ACK is sent from SSF to
SCF.
Release history
NATACK was made available in GSM16.
None
Associated logs
None
Extension register
NATACK2
Validation formula
None
Register NEENDS 2
CAMEL Empty End Sent
This register is increased by 1 when a Empty End message is sent from SSF
to SCF.

Release history
NEENDS was made available in GSM16.
None
Associated logs
None
Extension register
NEENDS2
Validation formula
None
Register NEENDR 2
This register is increased by 1 when an EMpty End message is received from
SCF by SSF.
Release history
NEENDR was made available in GSM16.
None
Associated logs
None
Extension register
NEENDR2
Validation formula
None


CAPOEDP
CAMEL O-BCS Events 2
This OM group measures the number of EDPs armed and reported on the
Originating-Basic Call State Model (O-BCSM).
Registers
CAPOEDP registers may be displayed at the DMS-MAP as follows:
OEDP4A OEDP4A2 OEDP4R OEDP4R2
Release history
CAPOEDP was created in GSM16.
Group structure
Number of tuples: 3
Key field: None
Info field: CAMEL_PHASE
None
Associated products
DMS-MSC
Register OEDP4A 2
CAMEL EDP4 Armed
This register is increased by 1 when EDP4 is armed.
Release history
EDP4 was made available in GSM16.

None
Associated logs
None
Extension register
EDPRA2
Validation formula
None
Register OEDP4R 2
CAMEL EDP4 Reported
This register is increased by 1 when EDP4 is reported.
Release history
OEDP4R was made available in GSM16.
None
Associated logs
None
Extension register
OEDP4R2
Validation formula
None
Register OEDP5A 2
CAMEL EDP5 Armed
Release history
OEDP5A was made available in GSM16.
None
Associated logs
None

Extension register
OEDP5A2
Validation formula
None
Register OEDP5R 2
CAMEL EDP5 Reported
Release history
None
Associated logs
None
Extension register
OEDP5R2
Validation formula
None
Register OEDP6A 2
CAMEL EDP6 Armed
Release history
None
Associated logs
None
Extension register
OEDP6A2
Validation formula
None

Register OEDP6R 2
CAMEL EDP6 Reported
Release history
None
Associated logs
None
Extension register
OEDP6R2
Validation formula
None
Register OEDP7A 2
CAMEL EDP7 Armed
Release history
OEDP7A2 was made available in GSM16.
None
Associated logs
None
Extension register
OEDP7A2
Validation formula
None
Register OEDP7R 2
CAMEL EDP7 Reported
Release history

None
Associated logs
None
Extension register
OEDP7R2
Validation formula
None
Register OEDP9A 2
CAMEL EDP9 Armed
Release history
None
Associated logs
None
Extension register
OEDP9A2
Validation formula
None
Register OEDP9R 2
CAMEL EDP9 Reported
Release history
None
Associated logs
None

Extension register
OEDP9R2
Validation formula
None
Register OEDP10A 2
CAMEL EDP10 Armed
Release history
None
Associated logs
None
Extension register
OEDP10A2
Validation formula
None
Register OEDP10R 2
CAMEL EDP10 Reported
Release history
OEDP10R2 was made available in GSM16.
None
Associated logs
None
Extension register
OEDP10R2
Validation formula
None


CAPTEDP
CAMEL T-BCS Events 2
This OM group measures the number of EDPs armed and reported on the
Terminating-Basic Call State Model (T-BCSM).
Registers
CAPTEDP registers may be displayed at the DMS-MAP as follows:
TEDP13A TEDP13A2 TEDP13R TEDP13R2
Release history
CAPTEDP was created in GSM16.
Group structure
Number of tuples: 3
Key field: None
Info field: CAMEL_PHASE
None
Associated products
DMS-MSC
Register TEDP13A 2
CAMEL EDP13 Armed
Release history
TEDP13A was made available in GSM16.
None

Associated logs
None
Extension register
TEDP13A2
Validation formula
None
Register TEDP13R 2
The register is increased by 1 when EDP13 is reported.
Release history
TEDP13R was made available in GSM16.
None
Associated logs
None
Extension register
TEDP13R2
Validation formula
None
Register TEDP14A 2
CAMEL EDP14 (T_No_Answer) Armed
Release history
None
Associated logs
None
Extension register
TEDP14A2

Validation formula
None
Register TEDP14R 2
CAMEL EDP14 (T_No_Answer) Reported
Release history
None
Associated logs
None
Extension register
TEDP14R2
Validation formula
None
Register TEDP15A 2
CAMEL EDP15 Armed
Release history
None
Associated logs
None
Extension register
TEDP15A2
Validation formula
None
Register TEDP15R 2

Release history
None
Associated logs
None
Extension register
TEDP15R2
Validation formula
None
Register TEDP17A 2
CAMEL EDP17 Armed
This register is pegged when EDP17 is armed.
Release history
None
Associated logs
None
Extension register
TEDP17A2
Validation formula
None
Register TEDP17R 2
Release history
None

Associated logs
None
Extension register
TEDP17R2
Validation formula
None
Register TEDP18A 2
CAMEL EDP18 Armed
Release history
None
Associated logs
None
Extension register
TEDP17A2
Validation formula
None
Register TEDP18R 2
Release history
None
Associated logs
None
Extension register
TEDP18R2

Validation formula
None

CAPERR
This OM group is obsoleted and been replaced by other OM groups.
The new groups contain registers for appropriate pegging of Internal IP

scenarios for:
• Originating CAMEL Subscription Information(O-CSI)
• Terminating CAMEL Subscription Information(T-CSI)
• Network Dialled Service CAMEL Subscription Information(N-CSI)
• Dialled Services CAMEL Subscription Information(D-CSI)
• Hotline specific, and Proprietary DP3
In addition, the new OM Groups are CSI Type specific and two-dimensional
based on CAMEL Phases and their registers.

CAPCALLP
CAMEL Call Processing for O-CSI, TCSI, and Hotline 2
This OM group measures the events related to CAMEL call processing.
Registers
CAPCALLP registers may be displayed at the DMS-MAP as follows:
OBCALATT OBCALAT2 TBCALATT TBCALAT2
OBCALSZ OBCALSZ2 TBCALSZ TBCALSZ2
OBCALCON OBCALCO2 TBCALCON TBCALCO2
OBCLABB OBCLABB2 TBCLABB TBCLABB2
OBCLABA OBCLABA2 TBCLABA TBCLABA2
HOTLATT HOTLATT2 HOTLSEZ HOTLSEZ2
HOTLANS HOTLANS2
Release history
CAPCALLP was created in GSM16 and modified for UMTS03/GSM17.
Group structure
Note: Info field “CSI_PHASE” displays the supported CAMEL phases
Key field: Nil
Info field: CSI_PHASE
None
Associated products
DMS-MSC
Register OBCALATT 2
CAMEL Call Attempts on SSF O-BCSM
This register is increased by 1, when the CAMEL DP2 triggers on O-BCSM.

Release history
OBCALATT was made available in GSM16 and modified in UMTS03/
GSM17.
Register type
Peg
None
Associated logs
None
Extension register
OBCALAT2
Validation formula
None
Register TBCALATT 2
CAMEL Call Attempts on SSF T-BCSM
This register is increased by 1 when the CAMEL DP2 triggers T-BCSM.
Release history
TBCALATT was made available in GSM16 and modified in UMTS03/
GSM17.
Register type
Peg
None
Associated logs
None
Extension register
TBCALAT2
Validation formula
None

Register OBCALSZ 2
CAMEL Call Attempts on SSF O-BCSM
and the call on O-BCSM initiates seizure of outgoing route.
Release history
OBCALSZ2 was made available in GSM16 and modified in UMTS03/
GSM17.
Register type
Peg
None
Associated logs
None
Extension register
OBCALSZ2
Validation formula
None
Register TBCALSZ 2
CAMEL CALL Seizure on SSF T-BCSM
and the CAMEL call on SSF T-BCSM initiates seizure of outgoing route.
Release history
TBCALSZ2 was made available in GSM16 and modified in UMTS03/
GSM17.
Register type
Peg
None
Associated logs
None
Extension register
TBCALSZ2

Validation formula
None
Register OBCALCON 2
CAMEL Call Connections on SSF O-BCSM
and the call is connected, that is, message indicating alerting is received.
Release history
OBCALCON was made available in GSM16 and modified in UMTS03/
GSM17.
Register type
Peg
None
Associated logs
None
Extension register
OBCALCO2
Validation formula
None
Register TBCALCON 2
CAMEL Call Connections on SSF T-BCSM
and the call is connected, that is, message indicating alerting is received.
Register type
Peg
Release history
TBCALCON was made available in GSM16 and modified in UMTS03/
GSM17.
None
Associated logs
None

Extension register
TBCALCO2
Validation formula
None
Register OBCLABB 2
GSM CAll Adandon Abandon before Alerting on SSF O-BCSM
This register is increased by 1 when the calling party is CAMEL subscriber
and calling party abandon the call before alerting.
Release history
OBCLABB was made available in GSM16 and modified in UMTS03/
GSM17.
Register type
Peg
None
Associated logs
None
Extension register
OBCLABB2
Validation formula
None
Register TBCLABB 2
GSM Call Abandon before Alerting on SSF T-BCSM
and calling party abandon the call before alerting.
Release history
TBCLABB was made available in GSM16 and modified in UMTS03/
GSM17.
Register type
Peg
None

Associated logs
None
Extension register
TBCLABB2
Validation formula
None
Register OBCLABA 2
Caller Abandon after Alerting on SSF O-BCSM but before answer
and calling party abandon the call after alerting but before answer.
Release history
OBCLABA was made available in GSM16 and modified in UMTS03/
GSM17.
Register type
Peg
None
Associated logs
None
Extension register
OBCLABA2
Validation formula
None
Register TBCLABA 2
Caller Abandon after Alerting on SSF T-BCSM but before Answer
and calling party abandon the call after alerting but before answer.
Release history
TBCLABA was made available in GSM16 and modified in UMTS03/
GSM17.
Register type
Peg

None
Associated logs
None
Extension register
TBCLABA2
Validation formula
None
Register HOTLATT 2
Hotline Call Attempt
This register is increased by 1 w hen the called party is HOTLINE and the
CAMEL service is triggered.
Release history
HOTLATT was made available in GSM16 and modified in UMTS03/
GSM17.
Register type
Peg
None
Associated logs
None
Extension register
HOTLATT2
Validation formula
None
Register HOTLSEZ 2
Hotline Call Seizure
This register is increased by 1 when the called party is HOTLINE and the call
seizes an outgoing trunk.
Release history
HOTLSEZ was made available in GSM16 and modified in UMTS03/
GSM17.

Register type
Peg
None
Associated logs
None
Extension register
HOTLSEZ2
Validation formula
None
Register HOTLANS 2
Hotline Call Answer
This register is increased by 1 when the called party is HOTLINE and the call
is answered.
Release history
HOTLANS was made available in GSM16 and modified in UMTS03/
GSM17.
Register type
Peg
None
Associated logs
None
Extension register
HOTLANS2
Validation formula
None

CAPSFCF
Internal IP related CAP operations (SCF--SSF) 2

scenarios for:

CAPSFCFE
Internal IP related error in relaying (SCF--SSF) 2

scenarios for:


CAPSFRF
Internal IP related CAP operations (SSF--SRF) 2

scenarios for:


CAPSFRFE
Internal IP related error in relaying (SSF--SRF) 2

scenarios for:


CAPTCSI
CAMEL Terminating CSI 2
This OM group is used to count the triggers and operations for T-CSI.
They are:
• CAMEL messages
Registers
CAPTCSI registers may be displayed at the DMS-MAP as follows:
TDP12 TDP122 TCONNECT TCONNEC2
TCONT TCONT2 TCONTARG TCONTAR2
TETC TETC2 TCTR TCTR2
TACH TACH2 TACR TACR2
TDFC TDFC2 TRRB TRRB2
TERB TERB2 TFCI TFCI2
TCIRQ TCIRQ2 TCIR TCIR2
TRSTTMR TRSTTMR2
Release history
CAPTCSI was created in GSM16.
Group structure
Key field: None
Info field: TCSI_PHASE
None
Associated products
DMS-MSC

Register TDP12 2
CAMEL DP12 Triggers
Release history
TCP12 was made available in GSM16.
None
Associated logs
None
Extension register
TDP122
Validation formula
None
Register TCONNECT 2
CAMELConnect
Release history
TCONNECT was made available in GSM16.
None
Associated logs
None
Extension register
TCONNEC2
Validation formula
None
Register TCONT 2
CAMEL Continue

Release history
TCONT was made available in GSM16.
None
Associated logs
None
Extension register
TCONT2
Validation formula
None
Register TCONTARG 2
CAMELContinue with Argument
Release history
TCONTARG was made available in GSM16.
None
Associated logs
None
Extension register
TCONTAR2
Validation formula
None
Register TETC 2
Release history
TETC was made available in GSM16.

None
Associated logs
None
Extension register
TETC2
Validation formula
None
Register TCTR 2
received.
Release history
TCTR was made available in GSM16.
None
Associated logs
None
Extension register
TCTR2
Validation formula
None
Register TACH 2
This register is increased by 1 if an ApplyCharging operations is received by
the SSF.
Release history
TACH was made available in GSM16.
None

Associated logs
None
Extension register
TACH2
Validation formula
None
Register TACR 2
This register is increased by 1 if an ApplyCharging operation is sent by the
SSF.
Release history
TACR was made available in GSM16.
None
Associated logs
None
Extension register
TACR2
Validation formula
None
Register TDFC 2
Release history
TDFC was made available in GSM16.
None
Associated logs
None

Extension register
TDFC2
Validation formula
None
Register TRRB 2
CAMEL Request Report BCSM Event
one or more EDPs.
Release history
TRRB was made available in GSM16.
None
Associated logs
None
Extension register
TRRB2
Validation formula
None
Register TERB 2
his register is increased by 1 when BCSM reaches the event armed as an EDP
and the SSF notifies the SCP by sending an EventReportBCSM operation.
Release history
TERB was made available in GSM16.
None
Associated logs
None
Extension register
TERB2

Validation formula
None
Register TFCI 2
This register counts the number of times that a CAMEL
Release history
TFCI was made available in GSM16.
None
Associated logs
None
Extension register
TFCI2
Validation formula2
None
Register TCIRQ 2
This register is increased by 1 if an CAMEL Call Information operations is
Release history
TCIRQ was made available in GSM16.
None
Associated logs
None
Extension register
TCIRQ
Validation formula
None

Register TCIR 2
CAMEL Call Information Report
This register is increased by 1 when a CAMEL call information report is sent
by SSF.
Release history
TCIR was made available in GSM16.
None
Associated logs
None
Extension register
TCIR2
Validation formula
None
Register TRSTTMR 2
CAMEL Reset Timer
from the SCF.
Release history
TRSTTMR was made available in GSM16.
None
Associated logs
None
Extension register
TRSTTMR2
Validation formula
None

CAPTCSI2
CAMEL Terminating CSI-2 2
This OM group is the extension for CAPTCSI. This OM group measures
CAMEL operations for T-CSI. New register TEENDS (extn. register
TEENDS2) is added to OM group CAPTCSI2 to measure the number of
Empty End operations sent to SCP for T-CSI.
Registers
CAPTCSI2 registers may be displayed at the DMS-MAP as follows:
TPA TPA2 TSRR TSRR2
TPCUI TPCUI2 TPCUIACK TPCUIAC2
TRELCALL TRELCAL2 TCANCEL TCANCEL2
TAT TAT2 TATACK TATACK2
TEENDR TEENDR2 TEENDS TEENDS2
Release history
CAPTCSI2 was created in GSM16, and modified in UMTS03/NSS17.
Group structure
Note: Info field "TCSI_PHASE" displays the supported CAMEL phases
(Phase1, Phase2 and Phase3) by T-CSI.
Number of tuples: 3 (Number of CAMEL Phases supported by T-CSI)
Key field: Nil
Info field: TCSI_PHASE
None
Associated products
DMS-MSC
Register TPA 2

Release history
TPA was made available in GSM16.
None
Associated logs
None
Extension register
TPA2
Validation formula
None
Register TSRR 2
This register is increased by 1 when the SpecializedResourceReport operation
Release history
TSRR was made available in GSM16.
None
Associated logs
None
Extension register
TSRR2
Validation formula
None
Register TPCUI 2
CAMEL Prompt and Collect User Information
Release history
TPCUI was made available in GSM16.

None
Associated logs
None
Extension register
TPCUI2
Validation formula
None
Register TPCUIACK 2
CAMEL Prompt And collect User Information Ack
SSF from SRF.
Release history
TPCUIACK was made available in GSM16.
None
Associated logs
None
Extension register
TPCUIAC2
Validation formula
None
Register TRELCALL 2
CAMEL Release Call
Release history
TRELCALL was made available in GSM16.
None

Associated logs
None
Extension register
TRELCAL2
Validation formula
None
Register TCANCEL 2
CAMEL CAP Cancel
This register is increased by 1 when CANCEL operations is received by SSF.
Release history
TCANCEL was made available in GSM16.
None
Associated logs
None
Extension register
TCANCEL2
Validation formula
None
Register TAT 2
CAMEL Activity Test
This register is increased by 1 if an CAMEL ActivityTest operation is
Release history
TAT was made available in GSM16.
None
Associated logs
None
Extension register
TAT2

Validation formula
None
Register TATACK 2
This register is increased by 1 when a Activity test ACK is sent from SSF to
SCF.
Release history
TATACK was made available in GSM16.
None
Associated logs
None
Extension register
TATACK2
Validation formula
None
Register TEENDR 2
SCF by SSF.
Release history
TEENDR was made available in GSM16.
None
Associated logs
None
Extension register
TEENDR2
Validation formula
None

Register TEENDS 2
CAMEL Empty End Sent for CAMEL T-CSI
Register TEENDS is increased by 1, when an Empty End message is sent
from SSF to SCF to end the transaction for CAMEL T-CSI.
Release history
TEENDS was made available in GSM16 and modified in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
TEENDS2
Validation formula
None


CIDBOM
Call Interception Database 2
The CIDBOM provides service monitoring and records the number of Call
Monitoring targets in Call Interception Database (CIDB) and the number of
parallel calls invoked by a given target. This is called Call Interception Call
Forward Database (CICFDB) or Call Interception Parallel Call Database
(CI_PAR_DB).
Note: This OM is only meant to be used for System engineering

purposes. The system operator is not expected to do anything with these
values.
Registers
The following CIDBOM registers may be displayed:
CI_COUNT CI_PAR_C
Release history
CIDBOM was made available in GSM10.
Group structure
CIDBOM provides two tuple per MSC/Call Server.
Key field: None
Info field: None
None
Associated products
None
Register CI_COUNT 2
Call Interception OM
An entry is made in the database and the CI_COUNT is increased by one
when a monitored call is up. The CIDB adds a new tuple for a new target
IMSI or IMEI. The entry in the CIDB database is removed and the tuple is
decreased by one when the call is taken down.
Register type
Peg

Associated register
Validation formula
Not applicable.
Associated logs
Log number
None
Extension register
Register CI_PAR_C 2
CI Parallel calls OM
When a user makes a monitored call and has multiple call forwarding calls
up, CI_PAR_C is increased by one for each instance of call-forwarding.
For example, if a user makes one monitored call and had two call forwarded
calls then the CI_COUNT will be one and the CI_PAR_C will be three.
(1+2=3).
When a user makes a monitored call and has multiple active call forwarding,
the CI_PAR_C decrements by 1 for each instance of a call-forwarding call
taken down by the user.
Consider the example above example again. If one of the instances of a call-
forwarding is taken down by the user the CI_COUNT will still be one and the
CI_PAR_C will be two. (1+1=2).
Register type
Peg
Associated register
Validation formula
Not applicable
Associated logs

Log number
None
Extension register


CLINTMMU
Call Interception on the MMU 2
The CLINTMMU OM group gathers metrics on the resource usage of call
interception (that is, three-port conference bridges) and error conditions.
Registers
CLINTMMU registers may be displayed at the DMS-MAP as follows:
• CICNF3MU
• CRFAILMU
• CMONERMU
Release history
CLINTMMU was created in GSM11.
Group structure
Number of tuples: one per Server
Key field: This field contains the CCS7 Servers id.
Info field: This field contains the CCS7 Server number.
CALLINT
Associated products
MMU
Validation formula
The sum of peg counts in the register for all available MMUs is always
smaller or equal to the number of peg counts in the existing register of the
corresponding OM group.
Register CICNF3MU 2
Call Interception Three-Port Conference Bridge Usage per MMU
CICNF3MU pegs the number of times the Call Interception uses a three-port
conference bridge.

Release history
CICNF3MU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register CRFAILMU 2
Call Notification Record Failure per MMU
CRFAILMU pegs the number of times sending of Call Notification Records

failed.
Release history
CRFAILMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register CMONERMU 2
Call Interception Monitoring Call Error per MMU

CMONERMU pegs the number of error conditions occurring in the

Monitoring Call. The Monitoring Call is not necessarily taken down when
CMONERMU is incremental.
Release history
CMONERMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None

CLISS
Calling Line Identification Supplementary Services 2
The CLISS OM group gathers measurements on the calling line identification
supplementary services CLIP and CLIR.
Registers
The following CLISS registers may be displayed:
CLIPOVER CLIRDOVR
Release history
CLISS was made available in GSM05.
Group structure
Number of tuples: One tuple per MSC/Call Server.
Key field: None
Info field: None
None
Associated products
None
Register CLIPOVER 2
Calling Line Identification Presentation Overridden
Register CLIPOVER is a peg register that pegs the number of times the called
subscriber overrides the calling subscriber’s CLI restrictions.
Associated register
None
Validation formula
None
Associated logs
None
Log number
None

EXT register
None
Register CLIRDOVR 2
Calling Line Identification Restriction Default Overridden
Register CLIRDOVR is a peg register that pegs the number of times a
subscriber provisioned with temporary CLIR overrides the default CLIR
mode when setting up a call.
Associated register
None
Validation formula
None
Associated logs
None
Log number
None
EXT register
None

CLOSS
Calling Line Identification Supplementary Services 2
The CLOSS (Calling Line Identification Supplementary Services) group
gathers metrics on the calling line identification supplementary services
Connected Line Identification Presentation (COLP) and Connected Line
Identification Restriction (COLR).
Registers
CLOSS registers may be displayed at the DMS MAP as follows:
COLPINVO COLRINVO COLPFAIL
Release history
CLOSS was created in GSM06.
Group structure
CLOSS provides one tuple for each MSC/Call Server.
Key field: None
Info field: None
None
Validation formula
None
Associated products
None
Register COLPINVO 2
Connected Line Identification Presentation Invoked
COLPINVO pegs the number of times COLP is invoked.
Release history
COLPINVO was created in GSM06.
Register type
PEG
None

Extension register
None
Register COLRINVO 2
Connected Line Identification Restriction Invoked
COLRINVO pegs the number of times COLR is invoked.
Release history
COLRINVO was created in GSM06.
Register type
PEG
None
Extension register
None
Register COLPFAIL 2
Connected Line Identification Presentation Fail
COLPINVO pegs the number of times COLP is invoked but is refused due to
COLR. The Connected Party Number (COPN) is not sent to the originating
mobile in this case.
Release history
COLPFAIL was created in GSM06.
Register type
PEG
None
Extension register
None

CAPCTAS
CAMEL Call Type Analysis 2
This group measures call attempt and call answer in four kinds of Call Type
and two kinds of CAMEL call failure.
The 4 kinds of call types are:

• CAMEL subscriber calls PSTN user
• CAMEL subscriber calls ordinary mobile subscriber
• PSTN user calls CAMEL subscriber
• Ordinary mobile subscriber calls CAMEL subscriber
The two CAMEL call failures are:

• CAMEL calls filtered due to overload
• Call failure for the system (SSF and SCF) issue
Registers
CAPCTAS registers can be displayed at the DMS Maintenance and
CFLTCAL CFLTCA2 CATTCL CATTCL2
CATTCM CATTCM2 CATTLC CATTLC2
CATTMC CATTMC2 CANSCL CANSCL2
CANSCM CANSCM2 CANSLC CANSLC2
CANSMC CANSMC2 CFALSYS CFALSY2
Release history
CMLCTAS was made available in GSMC13. This group was renamed to
CAPCTAS in GSM16. This OM was modified in UMTS03/GSM17.
Group structure
Note: Info field “CAP_PHASE” displays the supported CAMEL phases
(Phase 2 and Phase 3).

Key field: Nil
Info field: CAP_PHASE
None
Associated products
DMS-MSC
Register CFLTCAL 2
CAMEL call filtered
Register CFLTCAL is is increased by 1, when a CAMEL call arrived at SSF
but was filtered due to SSF overload.
Release history
C2FLTCAL was made available in GSMC13. This register was renamed in
GSM16. This OM was modified in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
CFLTCA2
Validation formula
None
Register CATTCL 2
CAMEL subscriber calls PSTN user (Land), call attempts
This register is increased by 1, when CAMEL subscriber calls PSTN user and
the call is going to be routed to PSTN user.

Release history
C2ATTCL was made available in GSMC13. This register was renamed in
Register type
Peg
None
Associated logs
None
Extension register
CATTCL2
Validation formula
None
Register CATTCM 2
CAMEL call subscriber calls ordinary mobile subscriber, call attempts
This register is increased by 1, when CAMEL subscriber calls ordinary
mobile subscriber and the HLR return to GMSC MSRN for the called mobile.
Release history
C2ATTCM was made available in GSMC13. This register was renamed in
Register type
Peg
None
Associated logs
None
Extension register
CATTCM2
Validation formula
None

Register CATTLC 2
PSTN user (Land) calls CAMEL subscriber, call attempts
and the call is coming in GMSC from PSTN network (trunk).
Release history
C2ATTLC was made available in GSMC13. This register was renamed in
Register type
Peg
None
Associated logs
None
Extension register
CATTLC2
Validation formula
None
Register CATTMC 2
Ordinary mobile subscriber calls CAMEL subscriber, call attempts
and the call is coming in GMSC from A-interface.
Release history
C2ATTMC was made available in GSMC13. This register was renamed in
Register type
Peg
None
Associated logs
None

Extension register
CATTMC2
Validation formula
None
Register CANSCL 2
CAMEL subscriber calls PSTN user (Land), call answer
This register is increased by 1, when CAMEL subscriber calls PSTN user and
the call is answered.
Release history
C2ANSCL was made available in GSMC13 This register was renamed in
Register type
Peg
None
Associated logs
None
Extension register
CANSCL2
Validation formula
None
Register CANSCM 2
CAMEL subscriber calls ordinary mobile subscriber, call answer
This register is increased by 1, when CAMEL subscriber calls ordinary
mobile subscriber and the call is answered.
Release history
C2ANSCM was made available in GSMC13. This register was renamed in
Register type
Peg

None
Associated logs
None
Extension register
CANSCM2
Validation formula
None
Register CANSLC 2
PSTN user (Land) calls CAMEL subscriber, call answer
the call is coming in GMSC from PSTN network (trunk) and the call is
answered.
Release history
C2ANSLC was made available in GSMC13. This register was renamed in
Register type
Peg
None
Associated logs
None
Extension register
CANSLC2
Validation formula
None
Register CANSMC 2
Ordinary mobile subscriber calls CAMEL subscriber, call answer
the call is coming in GMSC from A-interface and the call is answered.

Release history
C2ANSMC was made available in GSMC13. This register was renamed in
Register type
Peg
None
Associated logs
None
Extension register
CANSMC2
Validation formula
None
Register CFALSYS 2
CAMEL call failure for the system issue
The register is increased by 1, when the call failed due to system issue. The
system issue here means issue of SSF plus SCF, such as SSF CAMEL
operating timeout, or SSF CAMEL operation being discarded by SCF.
Release history
C2FALSYS was created in GSMC13. This register was renamed in
GSM16.This OM was modified in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
CFALSYS2
Validation formula
None

CMLTOCML
CAMEL Subscriber call to CAMEL Subscriber Call Processing 2
This OM group measures the events related to CAMEL subscriber to
CAMEL subscriber call.
Registers
CMLTOCML registers can be displayed at the DMS Maintenance and
CTOCATT CTOCATT2 CTOCSEZ CTOCSEZ2
CTOCCON CTOCCON2 CTOCANS CTOCANS2
CTOCNAN CTOCNAN2 CTOCBSY CTOCBSY2
CTOCABDB CTOCABB2 CTOCABA CTOCABA2
CTOCANSU CTOCANU2 CTOCSEZU CTOCSEU2
CTOCCONU CTOCCOU2
Release history
CMLTOCML was made available in GSM16.
Group structure
Number of tuples: one
Key field: None
Info field: None
None
Associated products
DMS-MSC

Register CTOCATT 2
CAMEL Subscriber Calls CAMEL Subscriber, Call Attempts
This register is increased by 1 when the calling party is CAMEL subscriber
and SRI returns T-CSI, i.e. the called party is CAMEL subscriber.
Release history
CTOCATT was made available in GSM16.
None
Associated logs
None
Extension register
CTOCATT2
Validation formula
None
Register CTOCSEZ 2
CAMEL Subscriber Calls CAMEL Subscriber, Call Initiates Seizure of
Route
This register is increased by 1 when the call is from CAMEL subscriber to
CAMEL subscriber and the call seizes an outgoing trunk.
Release history
CTOSCEZ was made available in GSM16.
None
Associated logs
None
Extension register
CTOCSEZ2
Validation formula
None

Register CTOCCON 2
CAMEL Subscriber Calls CAMEL Subscriber, Call Connected
CAMEL subscriber and the call is connected.
Release history
CTOCCON was made available in GSM16.
None
Associated logs
None
Extension register
CTOCCON2
Validation formula
None
Register CTOCANS 2
CAMEL Subscriber Calls CAMEL Subscriber, Call Answered
CAMEL subscriber and the call is answered.
Release history
CTOCANS was made available in GSM16.
None
Associated logs
None
Extension register
CTOCANS2
Validation formula
None
Register CTOCNAN 2
CAMEL Subscriber Calls CAMEL Subscriber, Call No Answer
CAMEL subscriber and the call is taken down due to no answer.

Release history
CTOCNAN was made available in GSM16.
None
Associated logs
None
Extension register
CTOCNAN2
Validation formula
None
Register CTOCBSY 2
CAMEL Subscriber Calls CAMEL Subscriber, Called Party Busy
Release history
CTOCBSY was made available in GSM16.
None
Associated logs
None
Extension register
CTOCBSY2
Validation formula
None
Register CTOCABDB 2
CAMEL Subscriber Calls CAMEL Subscriber, Caller Abandon Before Call
Alerting
CAMEL subscriber and the calling party abandon the call before alerting.
Release history
CTOCABDB was made available in GSM16.

None
Associated logs
None
Extension register
CTOCABB2
Validation formula
None
Register CTOCABA 2
CAMEL Subscriber Calls CAMEL Subscriber, Caller Abandon After Call
Alerting But Before Answered
CAMEL subscriber and the calling party abandon the call after alerting and
before answer.
Release history
CTOCABA was made available in GSM16.
None
Associated logs
None
Extension register
CTOCABA2
Validation formula
None
Register CTOCANSU 2
CAMEL Subscriber Calls CAMEL Subscriber, Call Usage After Call
Answered
This register is a usage counter. It measures total occupancy from call
answered to call released. It scans every 100 seconds. At every scan the
increment of the register is the number of calls, which satisfy when the call is
from CAMEL subscriber to CAMEL subscriber and the call is answered by
not released yet.

Release history
CTOCANSU was made available in GSM16.
None
Associated logs
None
Extension register
CTOCANU2
Validation formula
None
Register CTOCSEZU 2
CAMEL Subscriber Calls CAMEL Subscriber, Call Usage After Seizure Of
Outgoing Route
This register is a usage counter. It scans every 100 seconds. At every scan the
increment of the register is the number of calls which satisfy when the call is
from CAMEL subscriber to CAMEL subscriber and the call initiates seizure
of route and not released yet.
Release history
CTOCSEZU was made available in GSM16.
None
Associated logs
None
Extension register
CTOCSEU2
Validation formula
None
Register CTOCCONU 2
CAMEL Subscriber Calls CAMEL Subscriber, Call Usage After Connected
This register is a usage counter. It scans every 100 seconds. At every scan the
increment of the register is the number of calls which satisfy when the call if
from CAMEL subscriber to CAMEL subscriber and the call is connected and
the call is not released yet.

Release history
CTOCCONU was made available in GSM16.
None
Associated logs
None
Extension register
CTOCCOU2
Validation formula
None


CAPTRAF
CAMEL Traffic for O-CSI, T-CSI, and Hotline 2
The CAMEL Traffic for O-CSI, T-CSI, and Hotline (CAPTRAF) group is an
usage counter group measuring CAMEL call traffic.
The OM system provides two regular time intervals for usage registers: 100
seconds and 10 seconds. If scanned or sampled too frequently, they would
cause great degradation on real time of call processing. However, the data
precision increases. The choice of fast scan time or slow scan time is a trade-
off between real time and data precision. To void obvious real time
degradation, these usage registers are sampled every 100 seconds.
In TABLE OFCOPT, there is an office parameter, OMINERLANGS, which

controls the unit of output usage registers. When OMINERLANGS is set to
Y, the unit of OM data is converted to Deci-Erlang at the time when the data
in the active register is transferred to the holding register; otherwise, it is
CCS. The conversion to Deci-Erlang provides more accuracy than the Erlang
measurement.
Note: The raw content obtained from accumulating usage register may
not always be what the operator desires. It is the sum of the Deci-Erlang
every transfer time period, instead the Discerning over the whole
repeating time. The following example uses OC2ANSU to explain it.
Assume: an operator wants to see one day’s originating CAMEL call traffic
value from the OC2ANSU accumulating register.
1. Active register -> Holding register
Active register has the total time of active calls, in CCS. Its content is
transferred to the holding register every constant period of time, which is
called transferring time period. Suppose that there are n scans during the
transferring time period.
Right before the transferring, a division is made to convert data in active

register from CCS to Deci-Erlang. And the value after conversion is stored in
holding register.
2. Holding register -> Accumulating register
Nothing except accumulation would be done when transferring data from

holding register to accumulating register at every transfer moment. So after a
relatively long period of reporting time, say a day, the value in the accumulating
register is:
• After Accumulating register

• The call traffic over the reporting period is the average value.
It is used to obtain the average traffic in Deci-Erlangs, during the reporting

period the value held must be divided by the number of transfer. This is done
by the administration during downstream processing, where the number of
transfers can be determined by dividing the reporting period by the transfer
period (OMXFR).
Registers
CAPTRAF registers can be displayed at the DMS Maintenance and
OCANSU OCANSU2 TCANSU TCANSU2
OCSEZU OCSEZU2 TCSEZU TCSEZU2
OCCONU OCCONU2 TCCONU TCCONU2
HOTLSZU HOTLSZU2 HOTLANU HOTLANU2
Release history
CMLTRAF was made available in GSMC13. This OM group was renamed to
CAPTRAF in GSM16. This OM group was modified in UMTS03/GSM17.
Group structure
Number of Tuples: 2 (PHASE2 & PHASE3)
Key field: Nil
None
Associated products
DMS-MSC

Register OCANSU 2
CAMEL Answered Call Usage On SSF O-CSM
Register OCANSU is a usage register that measures total occupancy from call
answer to call release. A state variable is updated at real-time, indicating number
of active calls, which satisfies the following requirements:
• the calling party is a CAMEL subscriber
• the call is answered and not released yet
The register scans every 100 seconds. And at every scan the register accrues
with the value of the state variable at that moment.
Release history
OCANSU was made available in GSMC13. This register was renamed to
OCANSU in GSM16. This OM register was modified in UMTS03/GSM17.
Register type
Usage
None
Associated logs
None
Extension register
OCANSU2
Validation formula
None
Register TCANSU 2
CAMEL Answered Call Usage On SSF T-CSM
Register TCANSU is an usage counter. It measures total occupancy from call
• the called party is a CAMEL subscriber
Release history
TC2ANSU was made available in GSMC13. This register was renamed in
GSM16. This OM register was modified in UMTS03/GSM17.

Register type
Usage
None
Associated logs
None
Extension register
TCANSU2
Validation formula
None
Register OCSEZU 2
CAMEL call usage after seizure of outgoing route on SSF O-BCSM
Register OCSEZU is an usage counter. It measures total occupancy from call
Release history
OC2SEZU was made available in GSMC13. This register was renamed in
Register type
Usage
None
Associated logs
None
Extension register
OCSEZU2
Validation formula
None

Register TCSEZU 2
CAMEL call usage after seizure of outgoing route on SSF T-BCSM
Register TCSEZU is an usage counter. It measures total occupancy from call
Release history
TC2SEZU was made available in GSMC13. This register was renamed in
Register type
Usage
None
Associated logs
None
Extension register
TCSEZU2
Validation formula
None
Register OCCONU 2
CAMEL call usage after Connected on SSF O-BCSM
Register OCCONU is an usage counter. It measures total occupancy from call
Release history
OC2CNTU was made available in GSMC13. This register was renamed in

Register type
Usage
None
Associated logs
None
Extension register
OCCONU2
Validation formula
None
Register TCCONU 2
CAMEL usage after Connected on SSF T-BCSM
Register TCCONU is an usage counter. It measures total occupancy from call
Release history
TC2CNTU was made available in GSMC13. This register was renamed in
Register type
Usage
None
Associated logs
None
Extension register
TCCONU2
Validation formula
None

Register HOTLSZU 2
Hotline Call Seizure Usage
Register HOTLSZU is an usage counter. It measures total occupancy from call
• the called party is a HOTLINE subscriber
• the call seized is an out-going trunk
Release history
HLSEZU was made available in GSMC13. This register was renamed in
Register type
Usage
None
Associated logs
None
Extension register
HOTLSZU2
Validation formula
None
Register HOTLANU 2
Hotline Call Answer Usage
Register HOTLANU is an usage counter. It measures total occupancy from call
• the called party is a HOTLINE subscriber

Release history
HLANSU was made available in GSMC13. This register was renamed in
Register type
Usage
None
Associated logs
None
Extension register
HOTLANU2
Validation formula
None

CF3P
Three-port conference curcuits 2
The Three-port conference circuits (CF3P) Lines that use the Three–way
Calling (3WC) feature request three-port conference circuits. Calls that go to
service analysis positions after the activation of the position request three–
port conference circuits. Trunk test positions request three-port conference
circuits when a request to monitor talking is issued.
The registers in CF3P provide information on the use of a three-port

conference circuit. The information includes the number of times the system
seized a circuit. The information also incudes the number of times that a
circuit was not available. The information also includes the queue overflows
and abandons.
Multiple usage registers monitor conference circuits in different busy states.
Registers
CF3P registers may be displayed at the Maintenance and Administration
Position (MAP) as follows:
CNFSZRS CNFOVFL CNFQOCC CNFQOVFL
CNFQABAN CNFTRU CNFSBU CNFMBU
Release history
CF3P was made available before BCS20.
Group structure
CF3P provides provides one tuple for each office.
Key field: COMMON_LANGUAGE_NAME. This field contains the

external identifier CF3P.
Info field: CONF_MEM_NUMBER This field indicates the number of

software-equipped conference circuits in the office.
None
Validation formula
None
Associated products
None

Register CNFMBU 2
CF3P manual busy usage
Register CNFMBU is a usage register. Every 10 s CNFMBU scans the
conference circuits. CNFMBU records the number of conference circuits that
are in any of the following states during the last OM transfer period:
• manual busy
• seized
• network management procedures
Maintenance personnel can seize a circuit for diagnostic tests while working
from the trunk test position at the MAP terminal. Personnel also can be
working by the automatic trunk test (ATT) system can seize a circuit for
diagnostic tests. A system audit on the conference ports can also seize a
circuit for diagnostic tests.
The system updates the active register every 10 s with the number of CF3Ps
that are in any of the previously listed states. For example, if one conference
port is manual busy, the active register increases by 1 every 10s. The register
will continue to increase for as long as the port is in this state. The register
also increases if the system seizes one of the ports for a system audit. The
system copies the accumulated count to the holding register (CNFMBU)
every 30 min (and erases the previous value). If no ports are in these busy
states, CNFMBU will show a value that is not zero. Values that are not zero
will only appear if the system counted a port during the last OM transfer
period (30 min).
Release history
CNFMBU was made available before BCS20.
None
Associated logs
None
Register CNFOVFL 2
CF3P overflows
Register CNFOVFL increases when the system can not satisfy a request for a
three-port conference circuit immediately because conference circuits are
busy.
Three way callig attempts fail and the system routes the calls to treatment.
Service analysis and trunk test position requests attempt to queue.

Release history
CNFOVFL was made available before BCS20.
Register CNFOVFL equals the number of calls that attempt to enter the
conference circuit work queue.
Number of calls that enter the queue = CNFOVFL – CNQOVFL.
Associated logs
The all trunks busy (ATB) subsystem generates ATB100 for each blocked
attempt to seize a trunk to a exact numbering plan area (NPA) or central
office. The system advanced the call to another route.
Register CNFQABAN 2
Register CF3P queue abandons
Register CNFQABAN counts circuit requests abandoned while the requests
wait in the conference circuit queue.
The system uses this register in non-TOPS environments.
Release history
Register CNFQABAN was made available before BCS20.
None
Associated logs
The line maintenance subsystem generates the following logs when the
system encounters problems during call processing: LINE104, LINE105,
LINE109, and LINE204.
Register CNFQOCC 2
CF3P queue occupancy
Register CNFQOCC is a usage register. Every 10 s the system scans
conference circuits, and CNFQOCC records. The system scans if requests for
a conference circuit are waiting in the queue. The queue consists of waiting
service analysis and trunk test position requests only.
Release history
Register CNFQOOC was made available before BCS20.

None
Associated logs
None
Register CNFQOCCT 2
CF3P queue occupancy TOPS environment
Register CNFQOCCT is a usage register. Every 10 s the system scans the
conference circuits, and CNFQOCCT records. The system scans if requests
for a conference circuit are waiting in the queue. The queue consists of
waiting service analysis and trunk test position only.
Release history
Register CNFQOCCT was made available before BCS20.
None
Associated logs
None
Register CNFQOVFL 2
CF3P queue overflows
Register CNFQOVFL counts attempts to enter the wait queue when the queue
is full. Only requests from trunk test or service analysis positions increase this
register. Other requests do not attempt to wait.
Release history
Regsiter CNFQOVFL was made available before BCS20.
None
Associated logs
The line maintenance subsytem generates LINE 138 when the system routes a
call to a treatment after being call processing busy.
The trunk maintenance subsystem generates LINE 138 when the system
routes a call to a treatment after being call processing busy.

The line maintenance subsystem generates LINE120 when the DMS switch
fails to set up a requested three-way call. Failure occurs because a hardware
or software resource is not available.
Register CNFSBU 2
CF3P system busy usage
Register CNFSBU is a usage register. Every 10 s the system scans conference
circuits. CNFSBU records if the conference circuits are remote busy,
peripheral module busy, system busy, carrier failed, or unloaded. A
conference request that originated in the system can place the conference
circuits in these states.
Release history
Register CNFSBU was made available before BCS20.
None
Associated logs
The trunk maintenance subsystem generates TRK106 when a diagnostics test
on trunk equipment fails.
Register CNFSZRS 2
CF3P seizures
Register CNFSZRS increases when the system assigns a circuit in response to
a request. The system assigns the circuit before an attempt to set up network
paths to the three ports.
Release history
Register CNFSZRS was made available before BCS20.
None
Associated logs
None
Register CNFTRU 2
CF3P traffic busy usage
Register CNFTRU is a usage register. Every 10 s the system scans the
conference circuits, and CNFTRU records if the circuits are call processing
busy, unloaded, or locked out.
Release history
Register CNFTRU was made available before BCS20.

None
Associated logs
None

CF6P
Six-port conference bridge measurements 2
Note: This section presents a brief overview of the OM group, CF6P, and
a list of registers. For more detailed information on OM group, CF6P,
refer to NTP 2972621-814P1, Digital Switching Systems UCS DMS-250
Operational Measurements Reference Manual (Volume 1 of 2).
The OM group, CF6P, provides information on the use of a six-port

conference circuit and Voice Group Call Service.
Registers increase when:

• the system seizes a circuit
• the system makes a circuit not available
• a queue overflows
• the system abandons a queue
The following GSM/UMTS services request six-port conference circuits:

• 6-port Multi-Party service.
• Voice Group Call service.
Registers
CF6P registers may be displayed at the Maintenance and Administration
CF6SZRS CF6OVFL CF6QOCC CF6QOVFL
CF6QABAN CF6TRU CF6SBU CF6MBU
Release history
The OM group CF6P was introduced before BCS20.
APC005
Functionality is added to support Meridian Digital Centrex (MDC) features,
like 6WC, on Global Peripheral Platform (GPP) lines for:
• ANSI ISDN telephone user part (ATUP)
• ANSI ISDN user part (ANSI ISUP)
• Australian ISUP (AISUP) trunk signaling

BCS33
The system can convert registers CF6TRU, CF6SBU, and CF6MBU from
hundred call seconds (CCS) to deci-erlangs before the register appears. Use
the OMSHOW command on the active class to display the register.
Group structure
The OM group CF6P provides one register for each office.
Key field: COMMON_LANGUAGE_NAME
Info field: CONF6_OM_INFO
None

CMOSCSI
CAMEL Mobile Originated Short Messaging Service 2
CAMEL Subscription Information OM Group 2
The CMOSCSI group keeps track of the scenarios that are used for the
CAMEL short messaging services functionality.
Registers
CMOSCSI registers may be displayed at the Maintenance and Administration
CERROR CERROR2 CIDEDFLR CIDEDFL2
CIDEDSUB CIDEDSU2 CINVOKE CINVOKE2
COSMFLR COSMFLR2 COSMSUB COSMSUB2
CRELEAS CRELEAS2 CSSFAIL CSSFAIL2
CSSINVK CSSINVK2
Release history
CMOSCSI was created in GSM16.
Group structure
CMOSCSI provides one tuple per MSC/Call Server.
Key field: None
Info field: None
CMOSCMU
Validation formula
None
Associated products
CAMEL PHASE 3 SHORT MESSAGING SERVICE
Register CERROR 2
CAMEL SMS-CSI Int_Error operation received
This register counts the number of times that the CAMEL SMS-CSI Int_Error
operation is received.

Release history
CERROR was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CERROR2
Validation formula
None
Register CIDEDFLR 2
CAMEL SMS-CSI Implicitly disarm DP_O_SMS_Submitted
This register counts the number of times the EDP armed for Failure is
disarmed implicitly.
Release history
CIDEDFLR was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CIDEDFL2
Validation formula
None

Register CIDEDSUB 2
CAMEL SMS-CSI Implicitly disarm DP_O_SMS_Failure
This register counts the number of times the EDP armed for Submitted is
disarmed implicitly.
Release history
CIDEDSUB was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CIDEDSU2
Validation formula
None
Register CINVOKE 2
CAMEL SMS-CSI Int_Invoke_SMS_SSF sent (SMS -> SSF)
This register counts the number of times the SSF is invoked and the necessary
resources are allocated and when Int_Invoke_SMS_SSF is sent. SMS
provides all info needed by the SSF for opening a dialogue with the SCP.
Release history
CINVOKE was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CINVOKE2

Validation formula
None
Register COSMFLR 2
CAMEL SMS-CSI Originating Short Message Failure
This register counts the number of times it is indicated that there is a failure in
a Short Message (SM) submission attempt.
Release history
COSMFLR was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
COSMFLR2
Validation formula
None
Register COSMSUB 2
CAMEL SMS-CSI Originating Short Message Submitted per MMU
This register counts the number of times it is indicated that there is a
successful Short Message (SM) submission attempt.
Release history
COSMSUB was made available in GSM16.
Register type
Peg
None
Associated logs
None

Extension register
COSMSUB2
Validation formula
None
Register CRELEAS 2
CAMEL SMS-CSI Int_Release_SMS
This register counts the number of times the short message transaction is
denied or barred due to the application of the DSH or an SCP Release
instruction.
Release history
CRELEAS was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CRELEAS2
Validation formula
None
Register CSSABRT 2
CAMEL SMS-CSI SMS_Aborted
This register counts the number of times a SMS-Aborted message is received.
Release history
CSSABRT was made available in GSM16.
None
Associated logs
None

Extension register
CSSABRT2
Validation formula
None
Register CSSFAIL 2
CAMEL SMS-CSI Int_SMS_Failure sent (SMS-> SSF)
This register counts the number of times the mobile connection has been lost/
released while the smsSSF is non-idle.
Release history
CSSFAIL was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CSSFAIL2
Validation formula
None
Register CSSINVK 2
CAMEL SMS-CSI Int_SMS_SSF_Invoked (SMS -> SSF)
This register counts the number of times the smsSSF is successfully invoked
prior to starting a dialog with the SCP.
Release history
CSSINVK was made available in GSM16.
Register type
Peg
None

Associated logs
None
Extension register
CSSINVK2
Validation formula
None


CMOSCMU
CAMEL Subscription Information OM Group on MMUs
The CMOSCMU group keeps track of the scenarios that are used for the
CAMEL short messaging services on a per MMU basis. This is a two
dimensional OM group with the first dimension for the OM registers and the
second dimension for the MMU servers that are in service. The registers of
this OM group have a one to one correspondence with the registers of the
CMOSCSI OM group.
Registers
CMOSCMU registers may be displayed at the Maintenance and
Administration Position (MAP) as follows:
CERRORMU CERRORM2 CIDEDFMU CIDEDFM2
CIDEDSMU CIDEDSM2 CINVOKMU CINVOKM2
COSMFLMU COSMFLM2 COSMSUMU COSMSUM2
CRELESMU CRELESM2 CSFAILMU CSFAILM2
CSSINVMU CSSINVM2
Release history
CMOSCMU was created in GSM16.
Group structure
CMOSCMU provided tuples equal to the number of MMUs in service.
Key field: None
Info field: None
CMOSCCI
Validation formula
None
Associated products
None

Register CERRORMU 2
CAMEL SMS-CSI Int_Error operation received per MMU
This register counts the number of times that the CAMEL SMS-CSI Int_Error
operation is received. This is the MMU register that corresponds to the CM
register, CERROR.
Release history
CERRORMU was made available in GSM16.
None
Associated logs
None
Extension register
CERRORM2
Validation formula
None
Register CIDEDFMU 2
CAMEL SMS-CSI Implicitly disarm DP_O_SMS_Submitted per MMU
This register counts the number of times the EDP armed for Failure is
disarmed implicitly. This is the MMU register that corresponds to the CM
register, CIDEDF.
Release history
CIDEDFMU was made available in GSM16.
None
Associated logs
None
Extension register
CIDEDFM2
Validation formula
None

Register CIDEDSMU 2
CAMEL SMS-CSI Implicitly disarm DP_O_SMS_Failure per MMU
This register counts the number of times the EDP armed for Submitted is
disarmed implicitly. This is the MMU register that corresponds to the CM
register, CIDEDS.
Release history
CIDEDSMU was made available in GSM16.
None
Associated logs
None
Extension register
CIDEDSM2
Validation formula
None
Register CINVOKMU 2
CAMEL SMS-CSI Int_Onvoke_SMS_SSF sent (SMS -> SSF) per MMU
This register counts the number of times the SSF is invoked and the necessary
resources are allocated and when Int_Invoke_SMS_SSF is sent. SMS
provides all info needed by the SSF for opening a dialogue with the SCP. This
is the MMU register that corresponds to the CM register, CINVOK.
Release history
CINVOKMU was made available in GSM16.
None
Associated logs
None
Extension register
CINVOKM2
Validation formula
None

Register COSMFLMU 2
CAMEL SMS-CSI Originating Short Message Failure per MMU
This register counts the number of times it is indicated that there is a failure in
a Short Message (SM) submission attempt. This is the MMU register that
corresponds to the CM register, COSMFL.
Release history
COSMFLMU was made available in GSM16.
None
Associated logs
None
Extension register
COSMFLM2
Validation formula
None
Register COSMSUMU 2
CAMEL SMS-CSI Originating Short Message Submitted per MMU
This register counts the number of times it is indicated that there is a
successful Short Message (SM) submission attempt. This is the MMU
register that corresponds to the CM register, COSMSU.
Release history
COSMSUMU was made available in GSM16.
None
Associated logs
None
Extension register
COSMSUM2
Validation formula
None

Register CRELESMU 2
CAMEL SMS-CSI Int_Release_SMS per MMU
This register counts the number of times the short message transaction is
denied or barred due to the application of the DSH or an SCP Release
instruction. This is the MMU register that corresponds to the CM register,
CRELEAS.
Release history
CRELESMU was made available in GSM16.
None
Associated logs
None
Extension register
CRELESM2
Validation formula
None
Register CSFAILMU 2
CAMEL SMS-CSI Int_SMS_Failure sent (SMS-> SSF) per MMU
This register counts the number of times the mobile connection has been lost/
released while the smsSSF is non-idle. This is the MMU register that
corresponds to the CM register, CSSFAIL.
Release history
CSFAILMU was made available in GSM16.
None
Associated logs
None
Extension register
CSFAILM2
Validation formula
None

Register CSSINVMU 2
CAMEL SMS-CSI Int_SMS_SF_Invoked (SMS-> SSF) per MMU
This register counts the number of times the smsSSF is successfully invoked
prior to starting a dialog with the SCP. This is the MMU register that
corresponds to the CM register, CSSINVK.
Release history
CSSINVMU was made available in GSM16.
None
Associated logs
None
Extension register
CSSINVM2
Validation formula
None

CMOSCSI2
CAMEL Subscription Information OM Group - 2
The CMOSCSI2 OM group keeps track of the scenarios that are used for the
Registers
CMOSCSI2 registers may be displayed at the Maintenance and
CABORT CABORT2 CCONERR CCONERR2
CCONREQ CCONREQ2 CCONCOT CCONCOT2
CCONWOP CCONWOP2 CCOTERR CCOTERR2
CCOTREQ CCOTREQ2 CDSHAPP CDSHAPP2
CERSMNF CERSMNF2 CERSMNS CERSMNS2
CERSMRF CERSMRF2 CERSMRS CERSMRS2
CFCIERR CFCIERR2 CFCIREQ CFCIREQ2
CINITDP CINITDP2 CMISPRM CMISPRM2
Release history
CMOSCSI2 was created in GSM16.
Group structure
Number of tuples: 1
Key field: None
Info field: None
capscmu2
Validation formula Associated products

CAMEL Phase 3 Short Messaging Service

Register CABORT 2
CAMEL SMS-CSI ABORT
This register counts the number of times that the Abort operation has been
received, which indicates an exception has occurred on the SSP that required
the smsSSF to be taken down and prematurely end the dialogue with the SCF.
Release history
CABORT was made available in GSM16.
None
Associated logs
None
Extension register
CABORT2
Validation formula
None
Register CCONERR 2
CAMEL SMS-CSI CAP Connect_SMS Error
This register counts the number of times that an error is encountered and a
CAP connect-SMS operation is not requested from the SCF to continue
processing the Short Message (SM) request with modified parameters.
Release history
CCONERR was made available in GSM16.
None
Associated logs
None
Extension register
CCONERR2
Validation formula
None

Register CCONREQ 2
CAMEL SMS-CSI CAP Connect_SMS
This register counts the number of times that a CAP Connect_SMS
operations is requested from the SCF to continue processing the Short
Message (SM) request with modified parameters.
Release history
was made available in GSM16.
None
Associated logs
None
Extension register
CCONREQ2
Validation formula
None
Register CCONCOT 2
CAMEL SMS-CSI CAP Consumed Continue Message
This register counts the number of times that a CAMEL SMS-CSI CAP
Continue message is consumed.
Release history
CCONCOT was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CCONCOT2
Validation formula
None

Register CCONWOP 2
CAMEL SMS-CSI Connect without Parameters
Connect without Parameters operation is received.
Release history
CCONWOP was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CCONWOP2
Validation formula
None
Register CCOTERR 2
CAMEL SMS-CSI CAP Continue_SMS Error
CAP Continue_SMS operation is not requested from the SCF to continue
processing the SM request with the existing parameters.
Release history
CCOTERR was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CCOTERR2

Validation formula
None
Register CCOTREQ 2
CAMEL SMS-CSU Cap Continue_SMS
This register counts the number of times that a CAP Continue_SMS
operations is requested from the SCF to continue processing the SM request
with the existing parameters.
Release history
CCOTREQ was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CCOTREQ2
Validation formula
None
Register CDSHAPP 2
CAMEL SMS-CSI DSH Applied
This register counts the number of times that CAMEL SMS-CSI DSH is
applied.
Release history
CDSHAPP was made available in GSM16.
Register type
Peg
None
Associated logs
None

Extension register
CDSHAPP2
Validation formula
None
Register CERSMNF 2
CAMEL SMS-CSI ERSMS EDP-N Failure
This register counts the number of times that ERSMS is sent to the SCP when
an O-SMS_Failure event is detected for an armed EDP-N.
Release history
CERSMNF was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CERSMNF2
Validation formula
None
Register CERSMNS 2
CAMEL SMS-CSI ERSMS EDP-N Submitted
an O-SMS_Submitted event is detected for an armed EDP-N.
Release history
CERSMNS was made available in GSM16.
Register type
Peg
None

Associated logs
None
Extension register
CERSMNS2
Validation formula
None
Register CERSMRF 2
CAMELSMS-CSI ERSMS EDP-R Failure
an O_SMS_Failure event is detected for an armed EDP-R.
Release history
CERSMRF was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CERSMRF2
Validation formula
None
Register CERSMRS 2
CAMEL SMS-CSI ERSMS EDP-R Submitted
an O-SMS_Submitted event is detected for an armed EDP-R.
Release history
CERSMRS was made available in GSM16.
Register type
Peg

None
Associated logs
None
Extension register
CERSMRS2
Validation formula
None
Register CFCIERR 2
CAMEL SMS-CSI CAP Furnish_Charging_Information_SMS_Error
CAP Furnish_Charging_Information_SMS operation is not requested from
the SCF to record CAMEL SMS billing information.
Release history
CFCIERR was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CFCIERR2
Validation formula
None
Register CFCIREQ 2
CAMEL SMS-CSI Int_Error operation received
This register counts the number of times that a CAP
Furnish_Charging_Information_SMS operation is requested from the SCF to
record CAMEL SMS billing information.
Release history
CFCIREQ was made available in GSM16.

Register type
Peg
None-+
Associated logs
None
Extension register
CFCIREQ2
Validation formula
None
Register CINITDP 2
CAMEL SMS-CSI Initial_DP_SMS (SSF-> SCP)
This register counts the number of times that a CAP Initial_DP_SMS
operation is sent from the SSF to the SCP to start a dialogue with the SCF.
Release history
CINITDP was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CINITDP2
Validation formula
None
Register CMISPRM 2
CAMEL SMS-CSI Missing Parameter (SSF-> SCP)
This register counts the number of times that there is an error in the received
operation argument. The responding entity cannot start to process the
requested operation because the argument is incorrect: an expected optional
parameter, which is essential for the application is not included in the
operation argument.

Release history
CMISPRM was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CMISPRM2
Validation formula
None

CMOSCMU2
CAMEL Subscription Information OM Group 2 on MMUs
The CMOSCMU2 group keeps track of the scenarios that are used for the
CAMEL short messaging services on a per MMU basis. This is a two
CMOSCSI2 OM group.
Registers
CMOSCMU2 registers may be displayed at the Maintenance and
CABORTMU CABORTM2 CCONERMU CCONERM2
CCONREMU CCONREM2 CCONCTMU CCONCTM2
CCONWPMU CCONWPM2 CCOTERMU CCOTERM2
CCOTREMU CCOTREM2 CDSHAPMU CDSHAPM2
CERSNFMU CERSNFM2 CERSNSMU CERSNSM2
CERSRFMU CERSRFM2 CERSRSMU CERSRSM2
CFCIERMU CFCIERM2 CFCIRQMU CFCIRQM2
CINTDPMU CINTDPM2 CMISPRMU CMISPAM2
Release history
CMOSCMU2 was created in GSM16.
Group structure
The number of tuples is equal to the number of MMUs in service
Key field: None
Info field: None
CMOSCSI2

Validation formula
Associated products
None
Register CABORTMU 2
CAMEL SMS-CSI ABORT
This register counts the number of times that the Abort operation has been
received, which indicates an exception has occurred on the SSP that required
the smsSSF to be taken down and prematurely end the dialogue with the SCF.
This is the MMU register that corresponds to the CM register, CABORT.
Release history
CABORTMU was made available in GSM16.
None
Associated logs
None
Extension register
CABORTM2
Validation formula
None
Register CCONERMU 2
CAMEL SMS-CSI CAP Connect_SMS_Error per MMU
CAP connect-SMS operation is not requested from the SCF to continue
processing the Short Message (SM) request with modified parameters. This is
the MMU register that corresponds to the CM register, CCONERR.
Release history
CCONERMU was made available in GSM16.
None
Associated logs
None

Extension register
CCONERM2
Validation formula
None
Register CCONREMU 2
CAMEL SMS-CSI CAP Connect_SMS per MMU
This register counts the number of times that a CAP Connect_SMS
operations is requested from the SCF to continue processing the Short
Message (SM) request with modified parameters. This is the MMU register
that corresponds to the CM register, CCONREQ.
Release history
CCONREMU was made available in GSM16.
None
Associated logs
None
Extension register
CCONREM2
Validation formula
None
Register CCONCTMU 2
CAMEL SMS-CSI CAP Consumed Continue Message per MMU
Continue message is consumed. This is the MMU register that corresponds to
the CM register, CCONCOT.
Release history
CCONCTMU was made available in GSM16.
None
Associated logs
None
Extension register
CCONCTM2

Validation formula
None
Register CCONWPMU 2
CAMEL SMS-CSI CAP Connect without Parameters per MMU
Connect without Parameters operation is received. This is the MMU register
that corresponds to the CM register, CCONWOP.
Release history
CCONWPMU was made available in GSM16.
None
Associated logs
None
Extension register
CCONWPM2
Validation formula
None
Register CCOTERMU 2
CAMEL SMS-CSI CAP Continue_SMS per MMU
CAP Continue_SMS operation is not requested from the SCF to continue
processing the SM request with the existing parameters. This is the MMU
register that corresponds to the CM register, CCOTERR.
Release history
CCOTERMU was made available in GSM16.
None
Associated logs
None
Extension register
CCOTERM2
Validation formula
None

Register CCOTREMU 2
CAMEL SMS-CSI CAP Continue_SMS per MMU
This register counts the number of times that a CAP Continue_SMS
operations is requested from the SCF to continue processing the SM request
with the existing parameters. This is the MMU register that corresponds to the
CM register, CCOTREQ.
Release history
CCOTREMU was made available in GSM16.
None
Associated logs
None
Extension register
CCOTREM2
Validation formula
None
Register CDSHAPMU 2
CAMEL SMS-CSI DSH Applied per MMU
This register counts the number of times that CAMEL SMS-CSI DSH is
applied. This is the MMU register that corresponds to the CM register,
CDSHAPP.
Release history
CDSHAPMU was made available in GSM16.
None
Associated logs
None
Extension register
CDSHAPM2
Validation formula
None

Register CERSNFMU 2
CAMEL SMS-CSI ERSMS EDP-N Failure per MMU
an O-SMS_Failure event is detected for an armed EDP-N. This is the MMU
register that corresponds to the CM register, CERSMNF.
Release history
CERSNFMU was made available in GSM16.
None
Associated logs
None
Extension register
CERSNFM2
Validation formula
None
Register CERSNSMU 2
CAMEL SMS-CSI ERSMS EDP-N Submitted per MMU
an O-SMS_Submitted event is detected for an armed EDP-N. This is the
MMU register that corresponds to the CM register, CERSMNS.
Release history
CERSNSMU was made available in GSM16.
None
Associated logs
None
Extension register
CERSNSM2
Validation formula
None

Register CERSRFMU 2
CAMEL SMS-CSI ERSMS EDP-R Failure per MMU
an O_SMS_Failure event is detected for an armed EDP-R. This is the MMU
register that corresponds to the CM register, CERSMRF.
Release history
CERSRFMU was made available in GSM16.
None
Associated logs
None
Extension register
CERSRFM2
Validation formula
None
Register CERSRSMU 2
CAMEL SMS-CSI ERSMS EDP-R Submitted per MMU
an O-SMS_Submitted event is detected for an armed EDP-R. This is the
MMU register that corresponds to the CM register, CERSMRS.
Release history
CERSRSMU was made available in GSM16.
None
Associated logs
None
Extension register
CERSRSM2
Validation formula
None

Register CFCIERMU 2
CAMEL SMS-CSI CAP Furnish_Charging_Information_SMS Error per
MMU
CAP Furnish_Charging_Information_SMS operation is not requested from
the SCF to record CAMEL SMS billing information. This is the MMU
register that corresponds to the CM register, CFCIERR.
Release history
CFCIERMU was made available in GSM16.
None
Associated logs
None
Extension register
CFCIERM2
Validation formula
None
Register CFCIRQMU 2
CAMEL SMS-CSI CAP Furnish_Charging_Information_SMS per MMU
Furnish_Charging_Information_SMS operation is requested from the SCF to
record CAMEL SMS billing information. This is the MMU register that
corresponds to the CM register, CFCIREQ.
Release history
CFCIRQMU was made available in GSM16.
None
Associated logs
None
Extension register
CFCIRQM2
Validation formula
None

Register CINTDPMU 2
CAMEL SMS-CSI Initial_DP_SMS (SSF-> SCP)
This register counts the number of times that a CAP Initial_DP_SMS
operation is sent from the SSF to the SCP to start a dialogue with the SCF.
This is the MMU register that corresponds to the CM register, CINITDP.
Release history
CINTDPMU was made available in GSM16.
None
Associated logs
None
Extension register
CINTDPM2
Validation formula
None
Register CMISPRMU 2
CAMEL SMS-CSI Missing Parameter (SCP -> SSF)
This register counts the number of times that there is an error in the received
operation argument. The responding entity cannot start to process the
requested operation because the argument is incorrect: an expected optional
parameter, which is essential for the application is not included in the
operation argument. This is the MMU register that corresponds to the CM
register, CMISPRM.
Release history
CMISPRMU was made available in GSM16.
None
Associated logs
None
Extension register
CMISAM2
Validation formula
None


CMOSCSI3
This OM group keeps track of the scenarios that are used for the CAMEL
short messaging services functionality.
Registers
CAEDPNF CAEDPNF2 CAEDPNS CAEDPNS2
CAEDPRF CAEDPRF2 CAEDPRS CAEDPRS2
CAPPEND CAPPEND2 CARMTDP CARMTDP2
CCOLINF CCOLINF2 CDEDPFL CDEDPFL2
CDEDPSU CDEDPSU2 CFCIAPD CFCIAPD2
CFCIOVR CFCIOVR2 CFCISUC CFCISUC2
CRRSMER CRRSMER2 CTIMREX CTIMREX2
Release history
Group structure
Number of tuples: 1
Key field: None
Info field: None
CMOSCMU3
Validation formula
None
Associated products

Register CAEDPNF 2
CAMEL SMS-CSI Arm EDP-N Failure
This register counts the number of times that an Event Detection Point -
Notify (EDP-N) for Failure is armed.
Release history
CAEDPNF was made available in GSM16.
None
Associated logs
None
Extension register
CAEDPNF2
Validation formula
None
Register CAEDPNS 2
CAMEL SMS-CSI Arm EDP-N Submitted
This register counts the number of times that an Event Detection Point-Notify
(EDP-N) for Submitted is armed.
Release history
CAEDPNS was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CAEDPNS2
Validation formula
None

Register CAEDPRF 2
CAMEL SMS-CSI Arm EDP-R Failure
This register counts the number of times that an Event Detection Point-Report
(EDP-R) for Failure is armed.
Release history
CAEDPRF was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CAEDPRF2
Validation formula
None
Register CAEDPRS 2
CAMEL SMS-CSI Arm EDP-R Submitted
(EDP-R) for Submitted is armed.
Release history
CAEDPRS was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CAEDPRS2

Validation formula
None
Register CAPPEND 2
CAMEL SMS-CSI Application_End Received
This register counts the number of times the Application_End operations has
been received.
Release history
CAPPEND was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CAPPEND2
Validation formula
None
Register CARMTDP 2
CAMEL SMS-CSI Arm Detection Point
This register counts the number of times the detection point
SMS_Collected_Info is armed as a trigger detection point (TDP).
Release history
CARMTDP was made available in GSM16.
Register type
Peg
None
Associated logs
None

Extension register
CARMTDP2
Validation formula
None
Register CCOLINF 2
CAMEL SMS-CSI Initiate dialogue with SCF and trigger
DP_SMS_Collected_info
This register counts the number of times the SMS_Collected_Info detection
point has been triggered.
Release history
CCOLINF was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CCOLINF2
Validation formula
None
Register CDEDPFL 2
CAMEL SMS-CSI Disarm EDP Failure
This register counts the number of times that an Event Detection Point-
Request (EDP-R) for Failure is disarmed.
Release history
CDEDPFL was made available in GSM16.
Register type
Peg
None

Associated logs
None
Extension register
CDEDPFL2
Validation formula
None
Register CDEDPSU 2
CAMEL SMS-CSI Disarm EDP Submitted
Request (EDP-R) for Submitted is disarmed.
Release history
CDEDPSU was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CDEDPSU2
Validation formula
None
Register CFCIAPD 2
CAMEL SMS-CSI Append FCI Data
This register counts the number of times Furnish Charging Information (FCI)
data is appended to existing logical SMS records.
Release history
CFCIAPD was made available in GSM16.
Register type
Peg

None
Associated logs
None
Extension register
CFCIAPD2
Validation formula
None
Register CFCIOVR 2
CAMEL SMS-CSIOverwrite CAMEL Logical SMS Record with FCI
overwrites all non-completed CAMEL logical SMS record data.
Release history
CFCIOVR was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CFCIOVR2
Validation formula
None
Register CFCISUC 2
CAMEL SMS-CSI Write CAMEL Logical SMS Record with Furnish
Charging information (FCI)
Furnish Charging Information (FCI) message is successful.
Release history
CFCISUC was made available in GSM16.

Register type
Peg
None
Associated logs
None
Extension register
CFCISUC2
Validation formula
None
Register CRRSMER 2
CAMEL SMS-CSI RRSM Error
This register counts the number of times an RRSMSE
(Request_Report_SMS_Event) Error is encountered. The SCF is notified and
the Tssf Timer is reset. There is no event detection point armed when a
RRSMSE error is encountered.
Release history
CRRSMER was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CRRSMER2
Validation formula
None
Register CTIMREX 2
CAMEL SMS-CSI Timer Expired
This register counts the number of times that the Abort operations has been
received, which indicates the Tssf timer has expired or other exception has

occurred on the SSF that required the SSF to be taken down and end the
dialogue with the SCF.
Release history
CTIMREX was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CTIMREX2
Validation formula
None


CMOSCMU3
The CMOSCMU3 OM group keeps track of the scenarios that are used for
the CAMEL short messaging services on a per MMU basis. This is a two
CMOSCSI3 OM group.
Registers
CAEDNFMU CAEDNFM2 CAEDNSMU CAEDNSM2
CAEDRFMU CAEDRFM2 CAEDRSMU CAEDRSM2
CAPPENMU CAPPENM2 CARMDPMU CARMDPM2
CCOLINMU CCOLINM2 CDEDPFMU CDEDPFM2
CDEDPSMU CDEDPSM2 CFCIAPMU CFCIAPM2
CFCIOVMU CFCIOVM2 CFCISUMU CFCISUM2
CRRSERMU CRRSERM2 CTIMRXMU CTIMRXM2
Release history
Group structure
Number of tuples: One tuple per MSC/Call Server.
Key field: None
Info field: None
CMOSCSI3
Validation formula

Associated products
None
Register CDEDPFMU 2
CAMEL SMS-CSI Disarm EDP Failure per MMU
Register CAEDNFMU 2
CAMEL SMS-CSI Arm EDP-N Failure per MMU
Notify (EDP-N) for Failure is armed. This is the MMU register that
corresponds to the CM register, CAEDPNF.
Release history
CAEDNFMU was made available in GSM16.
None
Associated logs
None
Extension register
CAEDNFM2
Validation formula
None
Register CAEDNSMU 2
CAMEL SMS-CSI EDP-N Submitted per MMU
This register counts the number of times that an Event Detection Point-Notify
(EDP-N) for Submitted is armed. This is the MMU register that corresponds
to the CM register, CAEDPNS.
Release history
CAEDNSMU was made available in GSM16.
None
Associated logs
None
Extension register
CAEDNSM2

Validation formula
None
Register CAEDRFMU 2
CAMEL SMS-CSI EDP-R Failure per MMU
(EDP-R) for Failure is armed. This is the MMU register that corresponds to
the CM register, CAEDPRF.
Release history
CAEDRFMU was made available in GSM16.
None
Associated logs
None
Extension register
CAEDRFM2
Validation formula
None
Register CAEDRSMU 2
CAMEL SMS-CSI Arm EDP-R Submitted per MMU
(EDP-R) for Submitted is armed. This is the MMU register that corresponds
to the CM register, CAEDPRS.
Release history
CAEDRSMU was made available in GSM16.
None
Associated logs
None
Extension register
CAEDRSM2
Validation formula
None

Register CAPPENMU 2
CAMEL SMS-CSI Application_End Received per MMU
This register counts the number of times the Application_End operations has
been received. This is the MMU register that corresponds to the CM register,
CAPPEND.
Release history
CAPPENMU was made available in GSM16.
None
Associated logs
None
Extension register
CAPPENM2
Validation formula
None
Register CARMDPMU 2
CAMEL SMS-CSI Arm Detection Point per MMU
This register counts the number of times the detection point
SMS_Collected_Info is armed as a trigger detection point (TDP). This is the
MMU register that corresponds to the CM register, CARMTDP.
Release history
CARMDPM was made available in GSM16.
None
Associated logs
None
Extension register
CARMDPM2
Validation formula
None

Register CCOLINMU 2
CAMEL SMS-CSI Initiate dialogue with SCF and trigger
DP_SMS_Collected_Info per MMU
This register counts the number of times the SMS_Collected_Info detection
point has been triggered. This is the MMU register that corresponds to the
CM register, CCOLINF.
Release history
CCOLINMU was made available in GSM16.
None
Associated logs
None
Extension register
CCOLINM2
Validation formula
None
Register CDEDPSMU 2
CAMEL SMS-CSI Disarm EDP Failure per MMU
This register counts the number of times that an Event Detection Point-
Request (EDP-R) for Failure is disarmed. This is the MMU register that
corresponds to the CM register, .
Release history
CDEDPSMU was made available in GSM16.
None
Associated logs
None
Extension register
CDEDPSM2
Validation formula
None

Register CFCIAPMU 2
CAMEL SMS-CSI Append FCI data
data is appended to existing logical SMS records. This is the MMU register
that corresponds to the CM register, CFCIAPD.
Release history
CFCIAPMU was made available in GSM16.
None
Associated logs
None
Extension register
CFCIAPM2
Validation formula
None
Register CFCIOVMU 2
CAMEL SMS-CSI Overwrite CAMEL Logical SMS Record with FCI per
MMU
overwrites all non-completed CAMEL logical SMS record data. This is the
MMU register that corresponds to the CM register, CFCIOVR.
Release history
CFCIOVMU was made available in GSM16.
None
Associated logs
None
Extension register
CFCIOVM2
Validation formula
None

Register CFCISUMU 2
CAMEL SMS-CSI Write CAMEL Logical SMS Record with Furnish
Charging Information (FCI) per MMU extension
Furnish Charging Information (FCI) message is successful. This is the MMU
register that corresponds to the CM register, CFCISUC.
Release history
CFCISUMU was made available in GSM16.
None
Associated logs
None
Extension register
CFCISUM2
Validation formula
None
Register CRRSERMU 2
CAMEL SMS-CSI RRSM Error per MMU
This register counts the number of times an RRSMSE
(Request_Report_SMS_Event) Error is encountered. The SCF is notified and
the Tssf Timer is reset. There is no event detection point armed when a
RRSMSE error is encountered. This is the MMU register that corresponds to
the CM register, CRRSMER.
Release history
CRRSERMU was made available in GSM16.
None
Associated logs
None
Extension register
CRRSERM2
Validation formula
None

Register CTIMRXMU 2
CAMEL SMS-CSI Timer Expired per MMU
This register counts the number of times that the Abort operations has been
received, which indicates the Tssf timer has expired or other exception has
occurred on the SSF that required the SSF to be taken down and end the
dialogue with the SCF. This is the MMU register that corresponds to the CM
register, CTIMREX.
Release history
CTIMRXMU was made available in GSM16.
None
Associated logs
None
Extension register
CTIMRXM2
Validation formula
None

CMOSCSI4
The CMOSCSI4 OM group keeps track of the scenarios that are used for the
Registers
CMISREC CMISREC2 COUTPRM COUTPRM2
CRELSER CRELSER2 CRELREQ CRELREQ2
CREPERR CREPERR2 CREQREP CREQREP2
CRESERR CRESERR2 CRESTMR CRESTMR2
CSYSFAI CSYSFAI2 CTSKREF CTSKREF2
CUNXCOMP CUNXCOP2 CUNXDAT CUNXDAT2
CUNXPRM CUNXPRM2
Release history
Group structure
Number of tuples: One
Key field: None
Info field: None
CAPSCMU4
Validation formula
None
Associated products
CAMEL PHASE 3 SHORT MESSAGING SERVICE

Register CMISREC 2
CAMEL SMS-CSI Missing Customer Record (SCP -> SSF)
This register counts the number of times a CAP operation is sent and an error
is sent by the SCF to the SSF, if the SLP could not be found in the SCF
because the required customer record does not exist.
Release history
CMISREC was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CMISREC2
Validation formula
None
Register COUTPRM 2
CAMEL SMS-CSI Parameter Out of Range (SCP -> SSF)
This register counts the number of instances when the responding entity
cannot start the processing of the requested operation because an error in a
parameter of the operation argument is detected; a parameter value is out of
range.
Release history
COUTPRM was made available in GSM16.
None
Associated logs
None
Extension register
COUTPRM2
Validation formula
None

Register CRELSER 2
CAMEL SMS-CSI CAP Release_SMS Error
This register counts the number of times an error is encountered while
processing RELEASE_SMS Error operation from the SCP.
Release history
CRELSER was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CRELSER2
Validation formula
None
Register CRELREQ 2
CAMEL SMS-CSI CAP Release_SMS
This register counts the number of times that a CAP Release_SMS operation
is requested from the SCF to bar the Short Message (SM) request.
Release history
CRELREQ was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CRELREQ2

Validation formula
None
Register CREPERR 2
CAMEL SMS-CSI CAP Request_Report_SMS_Event Error
CAP Request_Report_SMS_Event operations is not sent from the SCF to arm
one or more event detection points.
Release history
CREPERR was made available in GSM16.
None
Associated logs
None
Extension register
CREPERR2
Validation formula
None
Register CREQREP 2
CAMEL SMS-CSI CAP Request_Report_SMS_Event
Request_Report_SMS_Event operation is sent from the SCF to arm one or
more event detection points.
Release history
CREQREP was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CREQREP2

Validation formula
None
Register CRESERR 2
CAMEL SMS-CSI CAP Reset_Timer_SMS operation Error
This register counts the number of times that an error occurs while processing
a CAP Reset_Timer_SMS operation.
Release history
CRESERR was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CRESERR2
Validation formula
None
Register CRESTMR 2
CAMEL SMS-CSI CAP Reset_Timer SMS operation
This register counts the number of times that a CAP Reset_Timer_SMS
operation is received to alter the Tssf timer value and restart the timer.
Release history
CRESTMR was made available in GSM16.
Register type
Peg
None
Associated logs
None

Extension register
CRESTMR2
Validation formula
None
Register CSYSFAI 2
CAMEL SMS-CSI System Failure (SCP-> SSF)
This register counts the number of instances when an error is returned by a PE
if it was not able to fulfill a specific task as requested by an operation, and
recovery is not expected to be completed within the current call instance.
Release history
CSYSFAI was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CSYSFAI2
Validation formula
None
Register CUNXCOMP 2
CAMEL SMS-CSI Unexpected Component Sequence (SCP->SSF)
This register counts the number of instances when the smsSSF cannot process
the operation in the current state of the smsSSF fsm.
Release history
CUNXCOMP was made available in GSM16.
Register type
Peg
None

Associated logs
None
Extension register
CUNXCOMP2
Validation formula
None
Register CUNXDAT 2
CAMEL SMS-CSI Unexpected Data Value (SCP->SSF)
cannot complete the processing of the requested operation because a
parameter has not unexpected that value.
Release history
CUNXDAT was made available in GSM16.
None
Associated logs
None
Extension register
CUNXDAT2
Validation formula
None
Register CUNXPRM 2
CAMEL SMS-CSI Unexpected Parameter (SCP -> SSF)
This register counts the number of instances when a valid but unexpected
parameter was present in the operation argument. The presence of this
parameter is not consistent with the presence of the other parameters. The
responding entity cannot start to process the operation.
Release history
CUNXPRM was made available in GSM16.
Register type
Peg
None

Associated logs
None
Extension register
CUNXPRM2
Validation formula
None
Register CTSKREF 2
CAMEL SMS-CSI Task Refused (SCP->SSF)
if it was not able to fulfill a specific task as requested by an operations, and
recovery is expected to be completed within the current call instance.
Release history
CTSKREF was made available in GSM16.
None
Associated logs
None
Extension register
CTSKREF2
Validation formula
None


CMOSCMU4
The CMOSCMU4 OM group keeps track of the scenarios that are used for
the CAMEL short messaging services on a per MMU basis. This is a two
CMOSCSI4 OM group.
Registers
CMISREMU CMISREM2 COUTPRMU COUTPMM2
CREPERMU CREPERM2 CREQREMU CREQREM2
CRELERMU CRELERM2 CRELREMU CRELREM2
CRESERMU CRESERM2 CRESTRMU CRESTRM2
CSYSFAMU CSYSFAM2 CTSKREMU CTSKREM2
CUNXCOMU CUNXCOM2 CUNXDAMU CUNXDAM2
CUNXPAMU CUNXPAM2
Release history
Group structure
Number of tuples: Equal to the number of MMUs in service
Key field: None
Info field: None
CMOSCSI4
Validation formula

Associated products
None
Register CRELREMU 2
CAMEL SMS-CSI CAP Release_SMS per MMU
Register CRELERMU 2
CAMEL SMS-CSI CAP Release_SMS Error per MMU
Register CMISREMU 2
CAMEL SMS-CSI Missing Customer Record (SCP-> SSF) per MMU
This register counts the number of times a CAP operation is sent and an error
is sent by the SCF to the SSF, if the SLP could not be found in the SCF
because the required customer record does not exist. This is the MMU
register that corresponds to the CM register, CMISREC.
Release history
CMISREMU was made available in GSM16.
None
Associated logs
None
Extension register
CMISREM2
Validation formula
None
Register COUTPRMU 2
CAMEL SMS-CSI Parameter Out of Range (SCP ->SSF) per MMU
cannot start the processing of the requested operation because an error in a
parameter of the operation argument is detected; a parameter value is out of
range. This is the MMU register that corresponds to the CM register,
COUTPRM.
Release history
COUTPRMU was made available in GSM16.
None

Associated logs
None
Extension register
COUTPMM2
Validation formula
None
Register CREPERMU 2
CAMEL SMS-CSI CAP Request_Report_SMS_Event Error per MMU
CAP Request_Report_SMS_Event operations is not sent from the SCF to arm
one or more event detection points. This is the MMU register that
corresponds to the CM register, CREPERR.
Release history
CREPERMU was made available in GSM16.
None
Associated logs
None
Extension register
CREPERM2
Validation formula
None
Register CREQREMU 2
CAMEL SMS-CSI CAP Request_Report_SMS_Event per MMU
Request_Report_SMS_Event operation is sent from the SCF to arm one or
more event detection points. This is the MMU register that corresponds to the
CM register, CREQREP.
Release history
CREQREMU was made available in GSM16.
None

Associated logs
None
Extension register
CREQREM2
Validation formula
None
Register CRESERMU 2
CAMEL SMS-CSI CAP Reset_Timer_SMS operation Error per MMU
This register counts the number of times that an error occurs while processing
a CAP Reset_Timer_SMS operation. This is the MMU register that
corresponds to the CM register, CRESERR.
Release history
CRESERMU was made available in GSM16.
None
Associated logs
None
Extension register
CRESERM2
Validation formula
None
Register CRESTRMU 2
CAMEL SMS-CSI CAP Reset_Timer SMS operation
This register counts the number of times that a CAP Reset_Timer_SMS
operation is received to alter the Tssf timer value and restart the timer. This is
the MMU register that corresponds to the CM register, CRESTMR.
Release history
CRESTRMU was made available in GSM16.
None
Associated logs
None

Extension register
CRESTRM2
Validation formula
None
Register CSYSFAMU 2
CAMEL SMS-CSI System Failure (SCP-> SSF)
if it was not able to fulfill a specific task as requested by an operation, and
recovery is not expected to be completed within the current call instance. This
is the MMU register that corresponds to the CM register, CSYSFAI.
Release history
CSYSFAMU was made available in GSM16.
None
Associated logs
None
Extension register
CSYSFAM2
Validation formula
None
Register CTSKREMU 2
CAMEL SMS-CSI Task Refused (SCP->SSF)
if it was not able to fulfill a specific task as requested by an operations, and
recovery is expected to be completed within the current call instance. This is
the MMU register that corresponds to the CM register, CTSKREF.
Release history
CTSKREMU was made available in GSM16.
None
Associated logs
None

Extension register
CTSKREM2
Validation formula
None
Register CUNXCOMU 2
CAMEL SMS-CSI Unexpected Component Sequence (SCP->SSF)
This register counts the number of instances when the smsSSF cannot process
the operation in the current state of the smsSSF fsm. This is the MMU register
that corresponds to the CM register, CUNXCOMP.
Release history
CUNXCOMU was made available in GSM16.
None
Associated logs
None
Extension register
CUNXCOM2
Validation formula
None
Register CUNXDAMU 2
CAMEL SMS-CSI Unexpected Data Value (SCP->SSF)
cannot complete the processing of the requested operation because a
parameter has not unexpected that value. This is the MMU register that
corresponds to the CM register, CUNXDAT.
Release history
CUNXDAMU was made available in GSM16.
None
Associated logs
None
Extension register
CUNXDAM2

Validation formula
None
Register CUNXPAMU 2
CAMEL SMS-CSI Unexpected Parameter (SCP -> SSF)
This register counts the number of instances when a valid but unexpected
parameter was present in the operation argument. The presence of this
parameter is not consistent with the presence of the other parameters. The
responding entity cannot start to process the operation. This is the MMU
register that corresponds to the CM register, CUNXPRM.
Release history
CUNXPAMU was made available in GSM16.
None
Associated logs
None
Extension register
CUNXPAM2
Validation formula
None

CMOSCSI5
CAMEL Subscription Information OM Group-5
short messaging services functionality.
Registers
CCONRJ CCONRJ2 CCOTRJ CCOTRJ2
CFCIRJ CFCIRJ2 CMISTYP CMISTYP2
CREQRJ CREQRJ2 CRELRJ CRELRJ2
CRESRJ CRESRJ2 CSABOR CSABOR2
CSERRO CSERRO2 CSREJT CSREJT2
CUNROP CUNROP2 CUNXLNK CUNXLIN2
CNOTRID CNOTRID2 CWROPAK CWROPAK2
Release history
Group structure
Number of tuples: 1
Key field: None
Info field: None
CAPSCMU5
Validation formula
None
Associated products

Register CNOTRID 2
CAMEL SMS-CSI No Transaction ID
This register counts the number of times that there is no resource for the
transaction ID and the SSF tries to get the transaction ID.
Release history
CNOTRID was made available in GSM16.
None
Associated logs
None
Extension register
CNOTRID2
Validation formula
None
Register CWROPAK 2
CAMEL SMS-CSI Wrong Packaging
This register counts the number of times that there is a wrong packaging
(generic for all operations). For example, if resetTimerSMS is received in an
END package, this OM will be pegged since resetTimerSMS cannot come in
an END package.
Release history
CWROPAK was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CWROPAK2
Validation formula
None

Register CCONRJ 2
CAMEL SMS-CSI CAP connect_SMS Reject
This register counts the number of times that a CAMEL SMS-CST CAP
Connect message is rejected.
Release history
CCONRJ was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CCONRJ2
Validation formula
None
Register CCOTRJ 2
CAMEL SMS-CSI CAP Continue_SMS Reject
Continue message is rejected.
Release history
CCOTRJ was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CCONRJ2

Validation formula
None
Register CFCIRJ 2
CAMEL SMS-CSI CAP Furnish_Charging_Information_SMS Reject
Furnish_Charging_Information message is rejected.
Release history
CFCIRJ was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CFCIRJ2
Validation formula
None
Register CMISTYP 2
CAMEL SMS-CSI Mistyped Parameter
This register counts the number of times that a problem code for mistyped
parameter Reject is received.
Release history
CMISTYP was made available in GSM16.
Register type
Peg
None
Associated logs
None

Extension register
CMISTYP2
Validation formula
None
Register CREQRJ 2
CAMEL SMS-CSI CAP Request_Report_SMS_Event Reject
Request_Report_SMS_Event message is rejected.
Release history
CREQRJ was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CREQRJ2
Validation formula
None
Register CRELRJ 2
CAMEL SMS-CSI CAP Release_SMS Reject
Release_SMS message is rejected.
Release history
CRELRJ was made available in GSM16.
Register type
Peg
None

Associated logs
None
Extension register
CRELRJ2
Validation formula
None
Register CRESRJ 2
CAMEL SMS-CSI CAP Reset_Timer_SMS Reject
Reset_Timer_SMS message is rejected.
Release history
CRESRJ was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CRESRJ2
Validation formula
None
Register CSABOR 2
CAMEL SMS-CSI SCP returns an ABORT
This register counts the number of times the SCP returns an ABORT.
Release history
CSABOR was made available in GSM16.
Register type
Peg
None

Associated logs
None
Extension register
CSABOR2
Validation formula
None
Register CSERRO 2
CAMEL SMS-CSI SCP Returns an ERROR
This register counts the number of times the SCP returns an ERROR.
Release history
CSERRO was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CSERRO2
Validation formula
None
Register CSREJT 2
CAMEL SMS-CSI SCP Returns a Reject
This register counts the number of times the SCP returns a Reject.
Release history
CSREJT was made available in GSM16.
Register type
Peg
None

Associated logs
None
Extension register
CSREJ2
Validation formula
None
Register CUNROP 2
CAMEL SMS-CSI Unrecognized Operation
This register counts the number of times an unrecognized operation is
received from the SCP and a Reject is sent with problem code ‘unrecognized
operation.’
Release history
CUNROP was made available in GSM16.
Register type
Peg
None
Associated logs
None
Extension register
CUNROP2
Validation formula
None
Register CUNXLNK 2
CAMEL SMS-CSI Unexpected Linked Operation
This register counts the number of times a Reject with unexpected linked
operation problem code is sent to the SCP.
Release history
CUNXLNK was made available in GSM16.
Register type
Peg

None
Associated logs
None
Extension register
CUNXLIN2
Validation formula
None


CMOSCMU5
short messaging services on a per MMU basis. This is a two dimensional OM
group with the first dimension for the OM registers and the second dimension
for the MMU servers that are in service. The registers of this OM group have
a one to one correspondence with the registers of the CMOSCSI5 OM group.
Registers
CCONRJMU CCONRJM2 CCOTRJMU CCOTRJM2
CFCIRJMU CFCIRJM2 CMISTYMU CMISTYM2
CREQRJMU CREQRJM2 CRELRJMU CRELRJM2
CRESRJMU CRESRJM2 CSABORMU CSABORM2
CSERROMU CSERROM2 CSREJTMU CSREJTM2
CUNROPMU CUNROPM2 CUNXLIMU CUNXLIM2
CNOTRIMU CNOTRIM2 CWROPAMU CWROPAM2
Release history
Group structure
Number of tuples: Equal to the number of MMUs in service.
Key field: None
Info field: None
None
Validation formula

Associated products
None
Register CNOTRIMU 2
CAMEL SMS-CSI No Transaction ID per MMU
Register CCONRJMU 2
CAMEL SMS-CSI CAP Connect_SMS Reject per MMU
This register counts the number of times that a CAMEL SMS-CST CAP
Connect message is rejected. This is the MMU register that corresponds to the
CM register, CCONRJ.
Release history
CCONRJMU was made available in GSM16.
None
Associated logs
None
Extension register
CCONRJM2
Validation formula
None
Register CCOTRJMU 2
CAMEL SMS-CSI CAP Continue_SMS Reject per MMU
Continue message is rejected. This is the MMU register that corresponds to
the CM register, CCOTRJ.
Release history
CCOTRJMU was made available in GSM16.
None
Associated logs
None
Extension register
CCOTRJM2

Validation formula
None
Register CFCIRJMU 2
CAMEL SMS-CSI CAP Furnish_Charging_Information_SMS Reject per
MMU
Furnish_Charging_Information message is rejected. This is the MMU register
that corresponds to the CM register, CFCIRJ.
Release history
CFCIRJMU was made available in GSM16.
None
Associated logs
None
Extension register
CFCIRJM2
Validation formula
None
Register CMISTYMU 2
CAMEL SMS-CSI Mistyped Parameter per MMU
This register counts the number of times that a problem code for mistyped
parameter Reject is received. This is the MMU register that corresponds to
the CM register, CMISTYP.
Release history
CMISTYMU was made available in GSM16.
None
Associated logs
None
Extension register
CMISTYM2

Validation formula
None
Register CREQRJMU 2
CAMEL SMS-CSI CAP Request_Report_SMS_Event Reject per MMU
Request_Report_SMS_Event message is rejected. This is the MMU register
that corresponds to the CM register, CREQRJ.
Release history
CREQRJMU was made available in GSM16.
None
Associated logs
None
Extension register
CREQRJM2
Validation formula
None
Register CRELRJMU 2
CAMEL SMS-CSI CAP Release_SMS Reject per MMU
Release_SMS message is rejected. This is the MMU register that corresponds
to the CM register, CRELRJ.
Release history
CRELRJM2 was made available in GSM16.
None
Associated logs
None
Extension register
CRELRJM2
Validation formula
None

Register CRESRJMU 2
CAMEL SMS-CSI CAP Reset_Timer_SMS Reject per MMU
Reset_Timer_SMS message is rejected. This is the MMU register that
corresponds to the CM register, CRESRJ.
Release history
CRESRJMU was made available in GSM16.
None
Associated logs
None
Extension register
CRESRJM2
Validation formula
None
Register CSABORMU 2
CAMEL SMS-CSI SCP Returns an ABORT per MMU
This register counts the number of times the SCP returns an ABORT. This is
the MMU register that corresponds to the CM register, CSABOR.
Release history
CSABORMU was made available in GSM16.
None
Associated logs
None
Extension register
CSABORM2
Validation formula
None

Register CSERROMU 2
CAMEL SMS-CSI SCP Returns an ERROR per MMU
This register counts the number of times the SCP returns an ERROR. This is
the MMU register that corresponds to the CM register, CSERRO.
Release history
CSERROMU was made available in GSM16.
None
Associated logs
None
Extension register
CSERROM2
Validation formula
None
Register CSREJTMU 2
CAMEL SMS-CSI SCP Returns a Reject per MMU
This register counts the number of times the SCP returns a Reject. This is the
MMU register that corresponds to the CM register, CSREJT.
Release history
CSREJTMU was made available in GSM16.
None
Associated logs
None
Extension register
CSREJTM2
Register CUNROPMU 2
CAMEL SMS-CSI Unrecognized Operation per MMU
This register counts the number of times an unrecognized operation is
received from the SCP and a Reject is sent with problem code ‘unrecognized
operation.’ This is the MMU register that corresponds to the CM register,
CUNROP.

Release history
CUNROPMU was made available in GSM16.
None
Associated logs
None
Extension register
CUNROPM2
Validation formula
None
Validation formula
None
Register CUNXLIMU 2
CAMEL SMS-CSI Unexpected Linked Operations per MMU
This register counts the number of times a Reject with unexpected linked
operation problem code is sent to the SCP. This is the MMU register that
corresponds to the CM register, CUNXLNK.
Release history
CUNXLIMU was made available in GSM16.
None
Associated logs
None
Extension register
CUNXLIM2
Validation formula
None
Register CWROPAMU 2
CAMEL SMS-CSI Wrong Packaging per MMU
This register counts the number of times that there is a wrong packaging
(generic for all operations). For example, if resetTimerSMS is received in an
END package, this OM will be pegged since resetTimerSMS cannot come in

an END package. This is the MMU register that corresponds to the CM

register, CWROPAK.
Release history
CWROPAK was made available in GSM16.
None
Associated logs
None
Extension register
CWROPAK2
Validation formula
None

CPADPRBK
CPIPP Address Pair Block OMs 2
The CPIPP Address Pair Block OMs group created to display the per-node
counts.
Registers
The following CPADPRBK registers may be displayed at the DMS MAP:
CPAXSZMU CPAXOVMU CPAXHIMU CPAXSZU2

CPAXHIU2
Release history
CPADPRBK was created in GSM13.
Group structure
Number of tuples: One per Server
Key field: This field contains the CCS7 Servers id
EXT
Validation formula
The original validation formula on the per register counts stands.
Validation formula for the new OM groups on the per MMU basis is:
• The sum of peg counts in the register for all available MMUs is always
smaller than or equal to the number of peg counts in the existing register
of the corresponding OM group.
Associated products
MMU
Register CPAXSZMU 2
CPIPP Address Pair Block OMs
Register CPAXSZMU counts the number of requests for a particular type of
extension block per MMU.
Release history
CPAXSZMU was created in GSM13.

EXTSIEZ
Extension register
CPAXSZU2
Validation formula
None
Register CPAXOVMU 2
Register CPAXOVMU counts when a particular type of extension block is
not available per MMU.
Release history
CPAXOVMU was created in GSM13.
EXTOVFL
Extension register
None
Validation formula
None
Register CPAXHIMU 2
Register CPAXHIMU counts the maximum number of extension blocks of
each time which are in simultaneous use during an OM transfer per MMU.
Release history
CPAXHIMU was created in GSM13.
EXTHI
Extension register
CPAXHIU2
Validation formula
None


CPMMU
CP MMU 2
The Call Processing per MMU OM group displays the per-node counts on
each MMU.
Registers
CPMMU registers may be displayed at the DMS MAP as follows:
CCBSZMMU CCBSZMU2 CCBOVLMU CLPSZMMU
CLPSZMU2 CPTRAPMU CPSUICMU ORGDENMU
WATDENMU CPLSZMMU CPLSZMU2 COOVFLMU
CPOVFLMU CPLOSZMU OUTBSZMU OBOVFLMU
MULTSZMU MTOVFLMU WAKESZMU WEOVFLMU
CINITCMU WINITCMU ITDENYMU INLBSZMU
INLBSZU2 IBOVFLMU CBOOVFMU
Release history
CPMMU was created in GSM11.
Group structure
Key field: This field contains the CCS7 Server id.
Number of Tuples: One per Server.
CP
Associated products
MMU

Validation formula
Register CCBSZMMU 2
Call condense block seizure per MMU
Register CCBSZMMU is a peg register that increments the count when a
CCB is allocated to a original message.
Release history
CCBSZMMU was created in GSM11.
None
Associated logs
None
Extension register
CCBSZMU2
Validation formula
None
Register CCBOVLMU 2
Call condense Block Overflow per MMU
Register CCBOVLMU is a peg register that counts Original messages that are
lost because no idle CCBs are available at that time per MMU.
Release history
CCBOVLMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None

Register CLPSZMMU 2
Call Process seizure per MMU
Register CLPSZMMU is a peg register that counts the number of times a call
process is activated during a call.
Release history
CLPSZMMU was created in GSM11.
None
Associated logs
None
Extension register
CLPSZMU2
Validation formula
None
Register CPTRAPMU 2
Call Process Trap per MMU
Register CPTRAPMU is a peg register that counts the calls that fail during a
callp due to illegal software conditions.
Release history
CPTRAPMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register ORGDENMU 2
Origination denial per MMU
Register ORGDENMU is a peg register that counts originations that are
ignored by the CC because they were not serviced within 3 s of interval.

Release history
ORGDENMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register WATDENMU 2
Wait denial per MMU
Register WATDENMU is a peg register that counts the calls that are lost due
to unavailable processes.
Release history
WATDENMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register CPLSZMMU 2
Call Processing letters seizure existing call per MMU
Register CPLSZMMU is a peg register that counts seizures of CP letters that
carry messages to calls already in the system.
Release history
CPLSZMMU was created in GSM11.

None
Associated logs
None
Extension register
CPLSZMU2
Validation formula
None
Register COOVFLMU 2
Call Processing letter overflow originating calls per MMU
Register COOVFLMU is a peg register that counts the originating messages
that could not be passed to callp using a CP letter.
Release history
COOVFLMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register CPOVFLMU 2
Call Processing letters overflow existing calls per MMU
Register CPOVFLMU is a peg register that counts attempts to send a progress
message to an existing call that fail because no CP letters are available.
Release history
CPOVFLMU was created in GSM11.
None

Associated logs
None
Extension register
None
Validation formula
None
Register CPLOSZMU 2
Call Processing letters seizures originating calls per MMU
Register CPLOSZMU is a peg register that counts origination Messages that
are successfully attached to a CCB.
Release history
CPLOSZMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register OUTBSZMU 2
Outgoing buffer seizure per MMU
Register OUTBSZMU is peg register that counts messages going to
peripheral modules that are placed in the outgoing buffers.
Release history
OUTBSZMU was created in GSM11.
Associated register
None
Associated logs
None

Extension register
None
Validation formula
None
Register OBOVFLMU 2
Outgoing buffer overflow per MMU
Register OBOVFLMU is peg register that counts outgoing messages that are
lost due to absence of an idle outgoing buffer.
Release history
OBOVFLMU was created in GSM11.
Associated register
None
Associated logs
None
Extension register
None
Validation formula
None
Register MULTSZMU 2
Multiblock seizure per MMU
Register MULTSZMU is peg register that counts seizures of a multiblock.
Release history
MULTSZMU was created in GSM11.
Associated register
None
Associated logs
None
Extension register
None
Validation formula
None

Register MTOVFLMU 2
Multiblock overflow per MMU
Register MTOVFLMU is peg register that counts attempts at 3-way calling
that fail when an idle multi block is not available.
Release history
MTOVFLMU was created in GSM11.
Associated register
None
Associated logs
None
Extension register
None
Validation formula
None
Register WAKESZMU 2
CPWAKEUP block seizure per MMU
Register WAKESZMU is peg register that counts CPWAKEUP block seizure.
Release history
WAKESZMU was created in GSM11.
Associated register
None
Associated logs
None
Extension register
None
Validation formula
None
Register WEOVFLMU 2
CPWAKEUP Block overflow per MMU
Register WEOVFLMU is peg register that counts unsuccessful CPWAKEUP
block seizures.

Release history
WEOVFLMU was created in GSM11.
Associated register
None
Associated logs
None
Extension register
None
Validation formula
None
Register CINITCMU 2
Call condense Cold restart per MMU
Register CINITCMU is peg register that counts the number of CCBs that
were in use at the time of a cold restart.
Release history
CINITCMU was created in GSM11.
Associated register
None
Associated logs
None
Extension register
None
Validation formula
None
Register WINITCMU 2
Calls lost warm restart per MMU
Register WINITCMU is peg register that counts the calls in progress that
were lost in a warm restart.
Release history
WINITCMU was created in GSM11.

Associated register
None
Associated logs
None
Extension register
None
Validation formula
None
Register ITDENYMU 2
Call originations denied per MMU
Register ITDENYMU is a peg register that counts line and trunk call
originations that are lost during cold and warm restarts.
Release history
ITDENYMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register INLBSZMU 2
Incoming long buffer seizures per MMU
Register INLBSZMU is a peg register that counts successful requests for a
long buffer for an incoming long message.
Release history
INLBSZMU was created in GSM11.
None

Associated logs
None
Extension register
INLBSZU2
Validation formula
None
Register IBOVFLMU 2
Incoming long buffers overflow per MMU
Register IBOVFLMU is a peg register that counts requests for a long buffer
for an incoming long message that are unsuccessful.
Release history
IBOVFLMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register CBOOVFMU 2
Long Origination denial per MMU
Register CBOOVFMU is a peg register that counts long origination that were
denied to reserve long buffers for long progress messages.
Release history
CBOOVFMU was created in GSM11.
None
Associated logs
None

Extension register
None
Validation formula
None
Register CBOOVFMU 2
Call Processing letter overflow originating calls per MMU
Register CBOOVFMU counts the originating messages that couldn't be
passed to CallP using a CP letter, on an MMU basis.
Register Type
Peg
Extension Register
None
Associated CM Register
OM Group CP:CPLOOVFL
Register CPSUICMU 2
Call Process Suicide per MMU
Register CPSUICMU counts the calls that failure during CallP, on an MMU
basis.
Register Type
Peg
Extension Register
None
OM Group CP:CPSUIC
Register CPSUICMU 2
Call Process Suicide per MMU
Counts the calls that failure during CallP, on an MMU basis.
Register type
Peg
OM Group CP:CPSUIC

Extension Register
None


CP2MMU
CP2 MMU 2
The Call Processing per MMU OM group is a continuation of the CPMMU
OM group and displays the per-node counts on each MMU.
Registers
CP2MMU registers may be displayed at the DMS MAP as follows:
ECCBSZMU ECBOVLMU ECBTRUMU CPWRKUMU
INFDENMU CPLHIMMU CCBHIMMU CLPHIMMU
OUTBHIMU MULTHIMU WAKEHIMU OVRLDMMU
INLBHIMU
Release history
CP2MMU was created in GSM11.
Group structure
CP2
Associated products
MMU
Validation formula

Register ECCBSZMU 2
Extended Call Control Block seizures
Register ECCBSZMU is a peg register that counts ECCBs that are seized.
Release history
ECCBSZMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register ECBOVLMU 2
Extended Call Control Block unsuccessful attempts per MMU
Register ECBOVLMU is a peg register that counts requests to an ECCB that
fails due to insufficient provisioning of resources.
Release history
ECBOVLMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register ECBTRUMU 2
Extended Call Control Block usage per MMU
Register ECBTRUMU is a peg register that records the ECCB Block in use.

Release history
EXBTRUMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register CPWRKUMU 2
Call processing usage per MMU
Register CPWRKUMU is a peg register that counts the amount of time the
CC is undergoing heavy Call.
Release history
CPWRKUMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register INFDENMU 2
Ineffective deny per MMU
Register INFDENMU is a peg register that counts originations/abandon pairs
that are ignored by the CC because they were not serviced.
Release history
INFDENMU was created in GSM11.

None
Associated logs
None
Extension register
None
Validation formula
None
Register CPLHIMMU 2
Call processing letters high watermark per MMU
Register CPLHIMMU is a peg register that reflects the maximum number of
CP Letters in simultaneous use during the preceding OM transfer.
Release history
CPLHIMMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register CCBHIMMU 2
Call condense high watermark per MMU
Register CCBHIMMU is a peg register that reflects the maximum number of
CCBs in simultaneous use during the preceding OM transfer.
Release history
CCBHIMMU was created in GSM11.
None

Associated logs
None
Extension register
None
Validation formula
None
Register CLPHIMMU 2
Call Processes high watermark per MMU
Register CLPHIMMU is a peg register that reflects the maximum number of
call processes in simultaneous use during the preceding OM transfer.
Release history
CLPHIMMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register OUTBHIMU 2
Outgoing buffer high watermark per MMU
Register OUTBHIMU is a peg register that reflects the maximum number of
outgoing buffers in simultaneous use during the preceding OM transfer
period.
Release history
OUTBHIMU was created in GSM11.
None
Associated logs
None

Extension register
None
Validation formula
None
Register MULTHIMU 2
Multiblock high watermark per MMU
MULTHIMU is a peg register that reflects the maximum number of outgoing
multi blocks in simultaneous use during the preceding OM transfer period.
Release history
MULTHIMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register WAKEHIMU 2
Wake up block high watermark per MMU
Register WAKEHIMU is peg register that reflects the maximum number of
wake up blocks in simultaneous use during the preceding OM transfer.
Release history
WAKEHIMU was created in GSM11.
Associated register
None
Associated logs
None
Extension register
None

Validation formula
None
Register OVRLDMMU 2
Central control overload per MMU
Register OVRLDMMU is peg register that counts minutes during which CC
overload controls are in effect over the last OM transfer period.
Release history
OVRLDMMU was created in GSM11.
Associated register
None
Associated logs
None
Extension register
None
Validation formula
None
Register INLBHIMU 2
Long buffer high watermark per MMU
Register INLBHIMU is peg register that reflects the maximum number of
long buffers in simultaneous use during the preceding OM transfer period.
Release history
INLBHIMU was created in GSM11.
Associated register
None
Associated logs
None
Extension register
None
Validation formula
None

CPRPL2SZ
Call recording stream primary recording unit pool 2 size OMs 2
The Call Recording Stream Primary Recording Unit Pool 2 Size
(CPRPL2SZ) OM group monitors the use of extension blocks. Extension
blocks are auxiliary software resources that are allocated to calls for purposes
such as special billing records, data extensions for operator services, and
custom calling features. The primary purpose of an extension block is to
provide additional storage for data associated with a call.
Registers
CPRPL2SZ registers may be displayed at the DMS MAP as follows:
• EXT2SZMU
• EXT2SZU2
• EXT2OVMU
• EXT2HIMU
• EXT2HIU2
Release history
CPRPL2SZ was created in GSM11.
Group structure
EXT
Associated products
MMU
Validation formula

Register EXT2SZMU 2
Counts the number of requests for a particular type of extension block per
MMU.
Register EXT2SZMU is a peg register that counts the number of requests for
a particular type of extension block per MMU.
Release history
EXT2SZMU was created in GSM11.
None
Associated logs
None
Extension register
EXT2SZU2
Validation formula
None
Register EXT2OVMU 2
Counts when a particular type of extension block is not available per MMU.
Register EXT2OVMU is a peg register that counts when a particular type of

extension block is not available per MMU.
Release history
EXT2OVMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register EXT2HIMU 2
Counts the maximum number of extension blocks per MMU.

Register EXT2HIMU is a peg register that counts the maximum number of

extension blocks of each time which are in simultaneous use during an OM
transfer per MMU.
Release history
EXT2HIMU was created in GSM11.
None
Associated logs
None
Extension register
EXT2HIU2
Validation formula
None


CRDBOM
Call Reference Database 2
The CRDBOM provides service monitoring and records the number of Call
Reference in Call Reference Database (CRDB) and the number of Call
Element in Call Element Database (CEDB).
Registers
CRDBOM registers may be displayed at the Maintenance and Administration
CR_COUNT CE_COUNT
Release history
CRDBOM was created in GSM09.
Group structure
Key field: None
Info field: None
Number of tuples: 2
None
Validation formula
None
Associated products
None
Register CE_COUNT 2
CALL Element_ Count
CE_COUNT is increased by 1, when CEDB adds a Call Element tuple.
Decrement by 1, if removes a Call Element tuple out of the CEDB.
Release history
CE_COUNT was created in GSM09.
Register type
Peg

None
Extension register
None
Register CR_COUNT 2
CALL Reference_Count
CR_COUNT is increased by 1, when CRDB adds a Call Reference.
Decrement by 1, if remove a Call Reference tuple out of the CRDB.
Release history
CR_COUNT was created in GSM09.
Register type
Peg
None
Extension register
None

CSRPL1SZ
Call recording stream secondary recording unit pool 1 size OMs 2
The Call Recording Stream Secondary Recording Unit Pool 1 Size
(CSRPL1SZ) OM group monitors the use of extension blocks. Extension
Registers
CSRPL1SZ registers may be displayed at the DMS MAP as follows:
EXT1SZMU EXT1SZU2 EXT1OVMU EXT1HIMU

EXT1HIU2
Release history
CSRPL1SZ was created in GSM11.
Group structure
EXT
Associated products
MMU
Validation formula
Register EXT1SZMU 2
MMU

Release history
None
Associated logs
None
Extension register
EXT1SZU2
Validation formula
None
Register EXT1OVMU 2

Release history
None
Associated logs
None
Extension register
None
Validation formula
None
Register EXT1HIMU 2

transfer per MMU.

Release history
None
Associated logs
None
Extension register
EXT1HIU2
Validation formula
None

CSRPL3SZ
The Call Recording Stream Secondary Recording Unit Pool 3 Size
(CSRPL3SZ) OM group monitors the use of extension blocks. Extension
Registers
• EXT3SZMU
• EXT3SZU2
• EXT3OVMU
• EXT3HIMU
• EXT3HIU2
Release history
CPRPL3SZ was created in GSM11.
Group structure
EXT
Associated products
MMU
Validation formula

Register EXT3SZMU 2
MMU.
Release history
None
Associated logs
None
Extension register
EXT3SZU2
Validation formula
None
Register EXT3OVMU 2

Release history
None
Associated logs
None
Extension register
None
Validation formula
None
Register EXT3HIMU 2


transfer per MMU.
Release history
None
Associated logs
None
Extension register
EXT3HIU2
Validation formula
None

CSRPL4SZ
The Call recording stream Secondary recording unit Pool 4 size (CSRPL4SZ)
OM group monitors the use of extension blocks. Extension blocks are
auxiliary software resources that are allocated to calls for purposes such as
special billing records, data extensions for operator services, and custom
calling features. The primary purpose of an extension block is to provide
additional storage for data associated with a call.
Registers
• EXT4SZMU
• EXT4SZU2
• EXT4OVMU
• EXT4HIMU
• EXT4HIU2
Release history
Group structure
EXT
Associated products
MMU
Validation formula

Register EXT4SZMU 2
MMU.
Release history
None
Associated logs
None
Extension register
EXT4SZU2
Validation formula
None
Register EXT4OVMU 2

Release history
None
Associated logs
None
Extension register
None
Validation formula
None
Register EXT4HIMU 2


transfer per MMU.
Release history
None
Associated logs
None
Extension register
EXT4HIU2
Validation formula
None

CSRPL5SZ
The Call recording stream Secondary recording unit Pool 5 size (CSRPL5SZ)
OM group monitors the use of extension blocks. Extension blocks are
auxiliary software resources that are allocated to calls for purposes such as
special billing records, data extensions for operator services, and custom
calling features. The primary purpose of an extension block is to provide
additional storage for data associated with a call.
Registers
• EXT5SZMU
• EXT5SZU2
• EXT5OVMU
• EXT5HIMU
• EXT5HIU2
Release history
Group structure
EXT
Associated products
MMU
Validation formula

Register EXT5SZMU 2
MMU.
Release history
None
Associated logs
None
Extension register
EXT5SZU2
Validation formula
None
Register EXT5OVMU 2

Release history
None
Associated logs
None
Extension register
None
Validation formula
None
Register EXT5HIMU 2


transfer per MMU.
Release history
None
Associated logs
None
Extension register
EXT5HIU2
Validation formula
None

CUGSS
Closed User Group Supplementary Service 2
The CUGSS (Closed User Group Supplementary Service) group gathers
statistical information on the Closed User Group (CUG) supplementary
service.
Registers
CUGSS registers may be displayed at the DMS-MAP as follows:
CUGATT CUGSUC
Release history
CUGSS was created in GSM07.
Group structure
CUGSS provides one tuple for each MSC/Call Server.
Key field: None
Info field: None
None
Validation formula
None
Associated products
None
Register CUGATT 2
CUG Attempts
CUGATT pegs all explicit and implicit CUG call attempts invoked from
mobile subscribers subscribed to CUG service. Explicit CUG attempt means,
the mobile subscriber provides any combination of CUG Index, Suppress
Preferential CUG and Suppress Outgoing Access in the call establish request
message (SETUP message). Implicit CUG attempt means, the mobile
subscriber does not provide any explicit CUG data in the call establish
request message (SETUP message).
Release history
CUGATT was created in GSM07.

Register type
Peg
None
Extension register
None
Register CUGSUC 2
CUG Successful
CUGSUC pegs all successful CUG origination call attempts from mobiles. A
CUG call attempt is successful if the CUG authorization check passes for the
mobile call origination.
Note: Authorization checks for CUG call termination (either on mobiles

or ISDN nodes) does neither concern not influence this OM group.
Release history
CUGSUC was created in GSM07.
Register type
Peg
None
Extension register
None

DAISGEN
This OM group, DAISGEN, provides general information about the DUTL's
operation.
Registers
DAISGEN registers may be displayed at the DMS-MAP as follows:
DAISSYEV DAISCOEV DAISREEV DAISRLEV

DAISNFEV DAISABEV DAISPRER DAISSYER
Release history
DAISGEN was created in BSC27.
Group structure
Key field: None
Info field: None
Number of tuples: None
Register DAISSYEV 2
The number of System Events that transpire within DAIS.
Release history
Register type
Peg
Register DAISCOEV 2
The number of Connect Events that occur within DAIS.
Release history
Register type
Peg
Register DAISREEV 2
The number of Refuse Events that happen within DAIS.
Release history

Register type
Peg
Register DAISRLEV 2
The number of Release Events located within DAIS.
Release history
Register type
Peg
Register DAISNFEV 2
The number of Not Finish Events that are found within DAIS.
Release history
Register type
Peg
Register DAISABEV 2
The number of Abort Events that are indigenous to DAIS.
Release history
Register type
Peg

DCAPSFCF
Internal IP related CAP operations (SCF--SSF) for D_CSI 2
This OM group is created to measure the successful CAP operations related
to Internal IP for D_CSI, which are involved in relay scenario, interacting
between SCF and SSF.
Registers
DCAPSFCF registers may be displayed at the DMS-MAP as follows:
DCCTR DCCTR2 DCPACS DCPACS2

DCSRRSC DCSRRSC2 DCPCUICS DCPCUIC2
DCPUIASC DCPUIAS2 DCCANCS DCCANCS2
Note: The registers in OM group, DCAPSFCF, are to be pegged in case

of DCSI triggering only.
Release history
DCAPSFCF was created in UMTS03/NSS17.
Group structure
Note: Info field “DCSI_PHASE” displays the supported CAMEL phases
(Phase3) by D-CSI.
Key field: Nil
Number of tuples: 1 (PHASE3)
Datafill
None
None
Validation formula
None
Associated products
DMS-MSC

Register DCCTR 2
D_CSI - CAMEL ConnectToResource
Register DCCTR is increased by 1, when the ConnectToResource message
received.
Release history
DCCTR was created in UMTS03/NSS17.
Register type
Peg
None
Associated logs
None
Extension register
DCCTR2
Register DCPACS 2
D_CSI - CAMEL PlayAnnouncement (SCF--SSF)
Register DCPACS is increased by 1, when the PlayAnnouncement message
Release history
DCPACS was created in UMTS03/NSS17.
Register type
Peg
None
Associated logs
None
Extension register
DCPACS2
Register DCSRRSC 2
D_CSI - CAMEL SpecializedResourceReport (SSF--SCF)
Register DCSRRSC is increased by 1, when the SpecializedResourceReport
operation is successfully sent from SSF to the SCF.

Release history
DCSRRSC was created in UMTS03/NSS17.
Register type
Peg
None
Associated logs
None
Extension register
DCSRRSC2
Register DCPCUICS 2
D_CSI - CAMEL PromptAndCollectUserInformation (SCF--SSF)
Register DCPCUICS is increased by 1, when the PCUI
Release history
DCPCUICS was created in UMTS03/NSS17.
Register type
Peg
None
Associated logs
None
Extension register
DCPCUIC2
Register DCPUIASC 2
D_CSI - CAMEL PromptAndCollectUserInformation Ack (SSF--SCF)
Register DCPUIASC is increased by 1, when the PCUI_ACK operation is
successfully sent from SSF to SCF.
Release history
DCPUIASC was created in UMTS03/NSS17.

Register type
Peg
None
Associated logs
None
Extension register
DCPUIAS2
Register DCCANCS 2
D_CSI - CAMEL Cancel (SCF--SSF)
Register DCCANCS is increased by 1, when the Cancel message received by
SSF from SCF.
Release history
DCCANCS was created in UMTS03/NSS17.
Register type
Peg
None
Associated logs
None
Extension register
DCCANCS2

DCAPSFRF
Internal IP related CAP operations (SSF--SRF) for D_CSI 2
This OM group is created to measure the successful CAP operations related
to Internal IP for D_CSI, which are involved in relay scenario, interacting
between SSF and SRF.
Registers
DCAPSFRF registers may be displayed at the DMS-MAP as follows:
DCPASI DCPASI2 DCSRRIS DCSRRIS2

DCPCUISI DCPCUIS2 DCPUIAIS DCPUIAI2
DCCANSI DCCANSI2
Note: The registers in OM group, DCAPSFRF, are to be pegged in case

of DCSI triggering only.
Release history
DCAPSFRF was created in UMTS03/NSS17.
Group structure
(Phase3) by D-CSI.
Key field: Nil
Datafill
None
None
Validation formula
None
Associated products
DMS-MSC

Register DCPASI 2
D_CSI - CAMEL PlayAnnouncement (SSF--SRF)
Register DCPASI is increased by 1, when a PlayAnnouncement operation is
successfully sent from the SSF to SRF (internal IP).
Release history
DCPASI was created in UMTS03/NSS17.
Register type
Peg
None
Associated logs
None
Extension register
DCPASI2
Register DCSRRIS 2
D_CSI - CAMEL SpecializedResourceReport. (SRF--SSF)
Register DCSRRIS is increased by 1, when the SpecializedResourceReport
message received by SSF from SRF (internal IP).
Release history
DCSRRIS was created in UMTS03/NSS17.
Register type
Peg
None
Associated logs
None
Extension register
DCSRRIS2

Register DCPCUISI 2
D_CSI - CAMEL PromptAndCollectUserInformation (SSF--SRF)
Register DCPCUISI is increased by 1, when the
PromptAndCollectUserInformation operation is successfully sent from the
SSF to SRF (internal IP).
Release history
DCPCUISI was created in UMTS03/NSS17.
Register type
Peg
None
Associated logs
None
Extension register
DCPCUIS2
Register DCPUIAIS 2
D_CSI - CAMEL PromptAndCollectUserInformation Ack (SRF--SSF)
Register DCPUIAIS is increased by 1, when the PCUI_ACK message
received by SSF from SRF (internal IP).
Release history
DCPUIAIS was created in UMTS03/NSS17.
Register type
Peg
None
Associated logs
None
Extension register
DCPUIAI2

Register DCCANSI 2
D_CSI - CAMEL Cancel (SSF--SRF)
Register DCCANSI is increased by 1, when CANCEL operation is
successfully sent from SSF to SRF.
Release history
DCCANSI was created in UMTS03/NSS17.
Register type
Peg
None
Associated logs
None
Extension register
DCCANSI2

DCPSFCFE
Internal IP related error in relaying (SCF--SSF) for D_CSI 2
This OM group measures the failure related to Internal IP CAP operations for
D_CSI between SCF and SSF.
Registers
DCPSFCFE registers may be displayed at the DMS-MAP as follows:
DECTR DECTR2 DJCTR DJCTR2

DEPAC DEPAC2 DJPAC DJPAC2
DJSRRS DJSRRS2 DEPCUIC DEPCUIC2
DJPCUIC DJPCUIC2 DJPUIAS DJPUIAS2
DECANC DECANC2 DJCANC DJCANC2
DCPFCI DCPFCI2
Note: The registers in this DCPSFCFE group are to be pegged in case of

D_CSI triggering only.
Release history
DCPSFCFE was created in UMTS03/GSM17.
Group structure
(Phase3) by D-CSI.
Key field: Nil
Datafill
None
None
Validation formula
None
Associated products
DMS-MSC

Register DECTR 2
D_CSI - CAMEL return ERROR for ConnectToResource (SCF--SSF)
Register DECTR is increased by 1, when SSF fails to handle the CTR
operation and return ERROR for it.
Register type
Peg
Release history
DECTR was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
DECTR2
Register DJCTR 2
D_CSI - CAMEL REJECT for ConnectToResource (SCF--SSF)
Register DJCTR is increased by 1, when CAP message of the received CTR
is not correct and SSF REJECT for it.
Register type
Peg
Release history
DJCTR was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None

Extension register
DJCTR2
Register DEPAC 2
D_CSI - CAMEL return or relay ERROR for PlayAnnouncement (SCF--
SSF)
Register DEPAC is increased by 1, when SSF return ERROR to SCF, or SSF
relay PA ERROR from SRF to SCF.
Register type
Peg
Release history
DEPAC was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
DEPAC2
Register DJPAC 2
D_CSI - CAMEL REJECT or relay REJECT for PlayAnnouncement (SCF--
SSF)
Register DJPAC is increased by 1, when the received PA is not correct and
SSF send REJECT to SCF, or SSF relay REJECT to SCF for PA.
Register type
Peg
Release history
DJPAC was created in UMTS03/GSM17.
Register type
Peg
None

Associated logs
None
Extension register
DJPAC2
Register DJSRRS 2
D_CSI - CAMEL REJECT for Specialized Resource Report (SCF--SSF)
Register DJSRRS is increased by 1, when SCF REJECT to SSF for SRR.
Register type
Peg
Release history
DJSRRS was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
DJSRRS2
Register DEPCUIC 2
D_CSI - CAMEL return or relay ERROR for
PromptAndCollectUserInformation (SCF--SSF)
Register DEPCUIC is increased by 1, when SSF return ERROR for PCUI to
SCF, or SSF relay ERROR for PCUI from SRF to SCF.
Register type
Peg
Release history
DEPCUIC was created in UMTS03/GSM17.
Register type
Peg

None
Associated logs
None
Extension register
DEPCUIC2
Register DJPCUIC 2
D_CSI - CAMEL REJECT or relay REJECT for
Register DJPCUIC is increased by 1, when the received PCUI is not correct
and SSF REJECT, or SSF relay PCUI REJECT from SRF to SCF.
Register type
Peg
Release history
DJPCUIC was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
DJPCUIC2
Register DJPUIAS 2
D_CSI - CAMEL REJECT for PromptAndCollectUserInformation Ack
(SCF--SSF)
Register DJPUIAS is increased by 1, when SSF return ERROR for
CANCEL(Invoke ID) to SCF, or SSF relay return-ERROR to SCF.
Register type
Peg
Release history
DJPUIAS was created in UMTS03/GSM17.

Register type
Peg
None
Associated logs
None
Extension register
DJPCUIC2
Register DECANC 2
D_CSI - CAMEL return or relay ERROR for Cancel (SCF--SSF)
Register DECANC is increased by 1, when SCP REJECT to SSF for
PCUI_ACK.
Register type
Peg
Release history
DECANC was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
DECANC2
Register DJCANC 2
D_CSI - CAMEL REJECT or relay REJECT for Cancel (SCF--SSF)
Register DJCANC is increased by 1, when the received CANCEL is not
correct and SSF REJECT, or SSF relay CANCEL REJECT from SRF to SCF.
Register type
Peg

Release history
DJCANC was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
DJCANC2
Register DCPFCI 2
D_CSI - CAMEL failed to relay operations from SCP to IP
Register DCPFCI is increased by 1, when SSF fails to process CTR, PA,
PCUI or CANCEL received from SCF for internal processing issue. In this
case SSF does not return ERROR or REJECT to SCF.
Register type
Peg
Release history
DCPFCI was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
DCPFCI2

DCPSFRFE
Internal IP related error in relaying (SCF--SRF) for D-CSI 2
This OM group is created to measure the failure related to Internal IP CAP
operations for D_CSI between SSF and Internal IP.
Registers
DCPSFRFE registers may be displayed at the DMS-MAP as follows:
DEPAS DEPAS2 DJPAS DJPAS2

DJSRRI DJSRRI2 DEPCUIS DEPCUIS2
DJPCUIS DJPCUIS2 DJPUIAI DJPUIAI2
DECANS DECANS2 DJCANS DJCANS2
DCPFIC DCPFIC2
Note: The registers in this DCPSFRFE group are to be pegged in case of

D_CSI triggering only.
Release history
DCPSFRFE was created in UMTS03/GSM17.
Group structure
(Phase3) by D-CSI.
Key field: Nil
Datafill
None
None
Validation formula
None
Associated products
DMS-MSC

Register DEPAS 2
D_CSI - CAMEL return ERROR for PlayAnnouncement. (SSF--SRF)
Register DEPAS is increased by 1, when SRF return ERROR for
PlayAnnouncement operation.
Register type
Peg
Release history
DEPAS was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
DEPAS2
Register DJPAS 2
D_CSI - CAMEL REJECT for PlayAnnouncement. (SSF--SRF)
Register DJPAS is increased by 1, when SRF send REJECT to SSF for PA.
Register type
Peg
Release history
DJPAS was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
DJPAS2

Register DJSRRI 2
D_CSI - CAMEL REJECT for Specialized Resource Report. (SSF--SRF)
Register DJSRRI is increased by 1, when SSF send REJECT to SRF for SRR.
Register type
Peg
Release history
DJSRRI was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
DJSRRI2
Register DEPCUIS 2
D_CSI - CAMEL return ERROR for PromptAndCollectUserInformation.
(SSF--SRF)
Register DEPCUIS is increased by 1, when SRF return ERROR to SSF for
PCUI.
Register type
Peg
Release history
DEPCUIS created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None

Extension register
DEPCUIS2
Register DJPCUIS 2
D_CSI - CAMEL REJECT for PromptAndCollectUserInformation. (SSF--
SRF)
Register DJPCUIS is increased by 1, when SRF REJECT to SSF for PCUI.
Register type
Peg
Release history
DJPCUIS created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
DJPCUIS2
Register DJPUIAI 2
D_CSI - CAMEL REJECT for PromptAndCollectUserInformation Ack.
(SSF--SRF)
Register DJPUIAI is increased by 1, when SSF REJECT to SRF for
PCUI_ACK.
Register type
Peg
Release history
DJPUIAI created in UMTS03/GSM17.
Register type
Peg
None

Associated logs
None
Extension register
DJPUIAI2
Register DECANS 2
D_CSI - CAMEL return ERROR (CancelFailed) for Cancel. (SSF--SRF)
Register DECANS is increased by 1, when SRF return ERROR to SSF for
CANCEL.
Register type
Peg
Release history
DECANS created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
DECANS2
Register DJCANS 2
D_CSI - CAMEL REJECT for Cancel. (SSF--SRF)
Register DJCANS is increased by 1, when SRF REJECT to SCF for
CANCEL.
Register type
Peg
Release history
DJCANS created in UMTS03/GSM17.
Register type
Peg

None
Associated logs
None
Extension register
DJCANS2
Register DCPFIC 2
D_CSI - CAMEL failed to relay operations from IP to SCP
Register DCPFIC is increased by 1, when SRR, PCUI_ACK, ERROR and
REJECT relay failure due to SSF internal call processing failure. In this case,
SSF does not return ERROR or REJECT to SRF.
Register type
Peg
Release history
DCPFIC created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
DCPFIC2

DCSIERR
Errors for CAMEL Dialed Service CSI 2
The DCSIERR (Errors for CAMEL Dialed Service CSI) group is created to
measure the number of the errors related to CAMEL messages/operations for
D-CSI.
Registers
DCSIERR registers may be displayed at the DMS-MAP as follows:
DMISCSTR DSCMISPR DSCTSKRE DSCUXCOS

DSCUXDAV DSCUXPAR DSCPRMOR DSCSYSFL
DLSSOTSV DEXPTSSF DCPFLBFQ DTIOFLBF
DSSFINID DETCFAIL DCIRQOPE DCNCLFAI
DINPCRES DREQINFE DUNAVLRE DUNKLEGI
DEXPTARI DUNSPTDO DCSMISPR DCSTSKRE
DCSUXCOS DCSUXDAV DCSUXPAR DCSPRMOR
DCSSYSFL DUSTCAPK
Release history
DCSIERR was created in UMTS03/GSM17.
Group structure
(Phase3) by D-CSI.
Key field: Nil
Number of tuples: 1 (Number of CAMEL Phases supported by D-CSI)
Datafill
None
None
Validation formula
None
Associated products
DMS-MSC

Register DMISCSTR 2
DCSI - Missing Customer Record
Register DMISCSTR is increased by 1, when a CAMEL operation is sent
(SSF -- SCF) and error is returned to the SSF, with the error code
"MissingCustomerRecord"
Example:
The CAMEL operation is sent to the SCF, which does not have the service
for the given subscriber. The SCF responds with a “ missing customer
record “ error message to the SSF.
Release history
DMISCSTR was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None
Register DSCMISPR 2
DCSI - Missing Parameter (SSF--SCF)
Register DSCMISPR is increased by 1, when a CAMEL operation is sent
"MissingParameter".
Release history
DSCMISPR was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None

Extension register
None
Register DSCTSKRE 2
DCSI - Task Refused (SSF--SCF)
Register DSCTSKRE is increased by 1, when a CAMEL operation is sent
"TaskRefused".
Release history
DSCTSKRE was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None
Register DSCUXCOS 2
DCSI - Unexpected component Sequence (SSF--SCF)
Register DSCUXCOS is increased by 1, when a CAMEL operation is sent
"UnexpectedComponentSequence".
Release history
DSCUXCOS was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None

Register DSCUXDAV 2
DCSI - Unexpected Data Value (SSF--SCF)
Register DSCUXDAV is increased by 1, when a CAMEL operation is sent
"UnexpectedDataValue".
Release history
DSCUXDAV was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None
Register DSCUXPAR 2
DCSI - Unexpected Parameter (SSF--SCF)
Register DSCUXPAR is increased by 1, when a CAMEL operation is sent
"UnexpectedParameter".
Release history
DSCUXPAR was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None

Register DSCPRMOR 2
DCSI - Parameter OUT of range (SSF--SCF)
Register DSCPRMOR is increased by 1, when CAMEL operation is sent
"ParameterOutOfRange".
Release history
DSCPRMOR was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None
Register DSCSYSFL 2
DCSI - System Failure (SSF--SCF)
Register DSCSYSFL is increased by 1, when CAMEL operation is sent
“SystemFailure”.
Release history
DSCSYSFL was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None

Register DLSSOTSV 2
DCSI - Local Subsystem Out of Service
Register DLSSOTSV is increased by 1, when the SSF interface detects that
the local CCS7 subsystem, ‘GSMCAP’, is out of service, while attempting to
encode and send CAMEL operation to the SCF.
Example:
While CAP subsystem is out of service on the MSC , a CAMEL call is
invoked by a subscriber.
Release history
DLSSOTSV was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None
Register DEXPTSSF 2
DCSI - Expiration of TSSF timer
Register DEXPTSSF is increased by 1, when the SSF Application timer Tssf
expires.
Example:
InitialDP is sent to SCF and there is no response from SCF till the expiry
of the Tssf timer. The TSSF timer value is determined by the GINSSF
field in Table GSMTIMRS.
Release history
DEXPTSSF was created in UMTS03/GSM17.
Register type
Peg
None

Associated logs
None
Extension register
None
Register DCPFLBFQ 2
DCSI - Call Processing failure before CAMEL query
Register DCPFLBFQ is increased by 1, when the CAMEL calls fails before
sending a CAMEL query message to the CCS7 transport link to be routed to
the SCP.
Example:
SSF is unable to determine the routing address from the translations for a
CAMEL call. The default call handling is applied for the call after
pegging this OM.
Release history
DCPFLBFQ was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None
Register DTIOFLBF 2
DCSI - Transaction ID overflow before 1st CAMEL query
Register DTIOFLBF is increased by 1, when CAMEL call failures because
no transaction ID is available in the SSF before sending the first GSM CAP
query.
Example:
The transaction ids are allocated to the CAMEL calls from a pool of ids. If
at any point , if this poll is exhausted then any attempt for a new CAMEL
call initiation will fail and this OM will be pegged.

Release history
DTIOFLBF was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None
Register DSSFINID 2
DCSI - SSF Initiation Denied
Register DSSFINID is increased by 1, when SSF initiation is denied.
Note: Only the definition of this register is available for future usage and
this remains unpegged showing zero value in this release.
Release history
DSSFINID was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None
Register DETCFAIL 2
DCSI - ETC failed
Register DETCFAIL is increased by 1, when Establish Temporary
Connection to IP failed and detected by SSF.

Example:
If the establish temporary connection to the IP is failed due to reasons like
network busy, local busy, local noanswer, remote release, authorization
denied etc.
Release history
DETCFAIL was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None
Register DCIRQOPE 2
DCSI - CIRQ error
Register DCIRQOPE is increased by 1, when CIRQ is received from SCF by
SSF and the SSF fails to process the CIRQ operation due to any error.
Example:
InitialDP is sent to SCF. SCF responds with CIRQ. If the CIRQ operation
has any error like missing mandatory parameters, illegal values in existing
parameters, CIRQ message not expected or not in sequence etc. then this
OM is pegged.
Release history
DCIRQOPE was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None

Extension register
None
Register DCNCLFAI 2
DCSI - Cancel Failed
Register DCNCLFAI is increased by 1, when the SSF fails to process the
CANCEL operation received from the SCF.
Example:
InitialDP is sent to SCF. SCF sends a CIRQ and then a CANCEL
operation with invokeId parameter set to 1. The SSF responds with a
“Cancel Failed” error.
Release history
DCNCLFAI was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None
Register DINPCRES 2
DCSI - Improper Caller Response
Register DINPCRES measures the Error messages with “Improper Caller
Response”.
Release history
DINPCRES was created in UMTS03/GSM17.
Register type
Peg
None

Associated logs
None
Extension register
None
Register DREQINFE 2
DCSI - Requested Information Error
Register DREQINFE is measures the Error messages with “Requested
Information Error “.
Release history
DREQINFE was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None
Register DUNAVLRE 2
DCSI - Unavailable Resource
Register DUNAVLRE is measures the errors where “Call processing
resources cannot be allocated”.
Release history
DUNAVLRE was created in UMTS03/GSM17.
Register type
Peg
None

Associated logs
None
Extension register
None
Register DUNKLEGI 2
DCSI - Unknown Leg ID
Register DUNKLEGI is increased by 1, when error message is sent by SSF
with “Unknown legID”.
Example:
InitialDP is sent to SCF and SCF responds with CIRQ having sending-
side legid=3. Then SSF responds with “Unknown Legid” error message
back to SCF.
Release history
DUNKLEGI was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None
Register DEXPTARI 2
DCSI - Expiry of TARI Timer
Register DEXPTARI is increased by 1, when connection establishment
between SSF and internal IP/SRF expired.
Example:
InitialDP is sent to SCF and it responds with CTR. SSF sends connect to
IP. IP does not respond with ARI and SSF times out waiting for ARI from
IP.
Release history
DEXPTARI was created in UMTS03/GSM17.

Register type
Peg
None
Associated logs
None
Extension register
None
Register DUNSPTDO 2
DCSI - Unsupported Operation
Register DUNSPTDO is increased by 1, when an operation is received
(SCF -- SSF) and the operation code is currently unsupported/unrecognized
by the SSF. The SSF will then encode and return a "reject" with an
appropriate problem code.
Example:
InitialDP for CAMEL Phase1 is sent to SCF. SCF responds with ETC.
ETC is not supported in Phase1. SSF rejects the ETC as “Unrecognized
Operation” and the OM register is pegged.
For CAMEL Phase 3 InitialDP, if the response from the SCF is a CALL
GAP message, this OM register is pegged when the SSF rejects with an
“Unrecognized Operation”.
Release history
DUNSPTDO was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None

Register DCSMISPR 2
DCSI - Missing Parameter (SCF--SSFSCF--SSF)
Register DCSMISPR is increased by 1, when a CAMEL operation is received
(SCF -- SSF) and the SSF encounters a problem processing the operation
which is characterized by the CAMEL error code "MissingParameter".
Example:
InitialDP is sent to SCF and the SCF sends SCI (Send Charge Info)
without mandatory parameter(s) like AOC Initial. SSF responds with a
“Missing Parameter” error.
Release history
DCSMISPR was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None
Register DCSTSKRE 2
DCSI - Task Refused (SCF--SSF)
Register DCSTSKRE is increased by 1, when a CAMEL operation is
received (SCF-- SSF) and the SSF encounters a problem processing the
operation which is characterized by the CAMEL error code "TaskRefused".
Example:
InitialDP is sent to SCF and a CIRQ is received by SSF while another
CIRQ is pending for the same leg. Then SSF will respond with “Task
Refused” error for the second CIRQ while a CIRP is sent for the first
CIRQ.
Release history
DCSTSKRE was created in UMTS03/GSM17.
Register type
Peg

None
Associated logs
None
Extension register
None
Register DCSUXCOS 2
DCSI - Unexpected component Sequence (SCF--SSF)
Register DCSUXCOS is increased by 1, when a CAMEL operation is
operation which is characterized by the CAMEL error code
"UnexpectedComponentSequence".
Example:
InitialDP is sent to SCF and PA/AC is received in a multi- component
message by SSF. PA is processed normally. As SSF can process only
PA/PCUI/Cancel after PA, it will respond with “Unexpected Component
Sequence” error.
Release history
DCSUXCOS was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None
Register DCSUXDAV 2
DCSI - Unexpected Data Value (SCF--SSF)
Register DCSUXDAV is increased by 1, when a CAMEL operation is
"UnexpectedDataValue".

Example:
InitialDP is sent to SCP and an AC with maximum call duration set to 0 is
received. Then SSF responds with “Unexpected Data Value” error.
Release history
DCSUXDAV was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None
Register DCSUXPAR 2
DCSI - Unexpected Parameter (SCF--SSF)
Register DCSUXPAR is increased by 1, when a CAMEL operation is
"UnexpectedParameter".
Example:
InitialDP is sent to SCP and SSF received CIRQ message with
Requested_info_type_parm other than 1,2 or 30 then SSF responds with
“UnexpectedParameter” error.
Release history
DCSUXPAR was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None

Extension register
None
Register DCSPRMOR 2
DCSI - Parameter OUT of range (SCF--SSF)
Register DCSPRMOR is increased by 1, when a CAMEL operation is
received by SSF (SCF--SSF), and the SSF encounters a problem processing
the operation which is characterized by the CAMEL error code
"ParameterOutOfRange".
Example:
InitialDP is sent to SCF and SCI with Tsw timer value greater than 86400
is received by SSP. The SSF then responds with “Parameter out of range”
error.
Release history
DCSPRMOR was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None
Register DCSSYSFL 2
DCSI - System Failure (SCF--SSF)
Register DCSSYSFL is increased by 1, when a CAMEL operation is received
by SSF (SCF--SSF), and the SSF encounters a problem processing the
operation which is characterized by the CAMEL error code “SystemFailure”.
Example:
InitialDP is sent to the SCF and the SCF responds with a CTR. This CTR
has to be sent to the IP, but the parameter “IP_ADDRESS” in Table
OFCVAR is not datafilled. The SSF responds with a “System Failure”
error.
Release history
DCSSYSFL was created in UMTS03/GSM17.

Register type
Peg
None
Associated logs
None
Extension register
None
Register DUSTCAPK 2
DCSI - Unsupported TCAP package type
Register DUSTCAPK is increased by 1, when an operation is received
(SCF -- SSF) within a TCAP package type that is currently unsupported for
that operation.
Release history
DUSTCAPK was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
None

DP3SFCFE
Internal IP related error in relaying (SCF--SSF) for Proprietary DP3 2
The DP3SFCFE group measures the error/failure related to Internal IP CAP
operations for Proprietary DP3 between SCF and SSF.
Registers
DP3SFCFE registers may be displayed at the DMS-MAP as follows:
PECTR PECTR2 PJCTR PJCTR2

PEPAC PEPAC2 PJPAC PJPAC2
PJSRRS PJSRRS2 PEPCUIC PEPCUIC2
PJPCUIC PJPCUIC2 PJPUIAS PJPUIAS2
PECANC PECANC2 PJCANC PJCANC2
PCPFCI PCPFCI2
Note: The registers in this DP3SFCFE group are to be pegged in case of

Proprietary DP3 triggering only.
Release history
DP3SFCFE was created in UMTS03/GSM17.
Group structure
(Phase2) by Proprietary DP3.
Key field: Nil
Datafill
None
None
Validation formula
None
Associated products
DMS-MSC

Register PECTR 2
Proprietary DP3 - CAMEL return ERROR for ConnectToResource (SCF--
SSF)
Register PECTR is increased by 1, when SSF fails to handle the CTR
operation and return ERROR for it.
Release history
PECTR was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PECTR2
Register PJCTR 2
Proprietary DP3 - CAMEL REJECT for ConnectToResource (SCF--SSF)
Register PJCTR is increased by 1, when CAP message of the received CTR is
not correct and SSF REJECT for it.
Release history
PJCTR was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PJCTR2

Register PEPAC 2
Proprietary DP3 - CAMEL return or relay ERROR for PlayAnnouncement
(SCF--SSF)
Register PEPAC is increased by 1, when SSF return ERROR to SCF, or SSF
relay PA ERROR from SRF to SCF.
Release history
PEPAC was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PEPAC2
Register PJPAC 2
Proprietary DP3 - CAMEL REJECT or relay REJECT for
PlayAnnouncement (SCF--SSF)
Register PJPAC is increased by 1, when the received PA is not correct and
SSF send REJECT to SCF, or SSF relay REJECT to SCF for PA.
Release history
PJPAC was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PJPAC2

Register PJSRRS 2
Proprietary DP3 - CAMEL REJECT for Specialized Resource Report
(SCF--SSF)
Register PJSRRS is increased by 1, when SCF REJECT to SSF for SRR.
Release history
PJSRRS was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PJSRRS2
Register PEPCUIC 2
Proprietary DP3 - CAMEL return or relay ERROR for
Register PEPCUIC is increased by 1, when SSF return ERROR for PCUI to
SCF, or SSF relay ERROR for PCUI from SRF to SCF.
Release history
PEPCUIC was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PEPCUIC2

Register PJPCUIC 2
Proprietary DP3 - CAMEL REJECT or relay REJECT for
Register PJPCUIC is increased by 1, when the received PCUI is not correct
and SSF REJECT, or SSF relay PCUI REJECT from SRF to SCF.
Release history
PJPCUIC was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PJPCUIC2
Register PJPUIAS 2
Proprietary DP3 - CAMEL REJECT for PromptAndCollectUserInformation
Ack (SCF--SSF)
Register PJPUIAS is increased by 1, when SCP REJECT to SSF for
PCUI_ACK.
Release history
PJPUIAS was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PJPUIAS2

Register PECANC 2
Proprietary DP3 - CAMEL return or relay ERROR for Cancel (SCF--SSF)
Register PECANC is increased by 1, when SSF return ERROR for
CANCEL(Invoke ID) to SCF, or SSF relay return-ERROR to SCF.
Release history
PECANC was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PECANC2
Register PJCANC 2
Proprietary DP3 - CAMEL REJECT or relay REJECT for Cancel. (SCF--
SSF)
Register PJCANC is increased by 1, when the received CANCEL is not
correct and SSF REJECT, or SSF relay CANCEL REJECT from SRF to SCF.
Release history
PJCANC was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PJCANC2

Register PCPFCI 2
Proprietary DP3 - CAMEL failed to relay operations from SCP to IP
Register PCPFCI is increased by 1, when SSF fails to process CTR, PA,
PCUI or CANCEL received from SCF for internal processing issue. In this
case SSF does not return ERROR or REJECT to SCF.
Release history
PCPFCI was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PCPFCI2

DP3SFRFE
Internal IP related error in relaying (SSF--SRF) for Proprietary DP3 2
The DP3SFRFE OM group measures the failure related to Internal IP CAP
operations for Proprietary DP3 between SSF and Internal IP.
Registers
DP3SFRFE registers may be displayed at the DMS-MAP as follows:
PEPAS PEPAS2 PJPAS PJPAS2

PJSRRI PJSRRI2 PEPCUIS PEPCUIS2
PJPCUIS PJPCUIS2 PJPUIAI PJPUIAI2
PECANS PECANS2 PJCANS PJCANS2
PCPFIC PCPFIC2
Note: The registers in this DP3SFRFE group are to be pegged in case of

Proprietary triggering only.
Release history
DP3SFRFE was created in UMTS03/GSM17.
Group structure
(Phase3) by Proprietary DP3.
Key field: Nil
Datafill
None
None
Validation formula
None
Associated products
DMS-MSC

Register PEPAS 2
Proprietary DP3 - CAMEL return ERROR for PlayAnnouncement
(SSF--SRF)
Register PEPAS is increased by 1, when SRF return ERROR for
PlayAnnouncement operation.
Release history
PEPAS was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
REPAS2
Register PJPAS 2
Proprietary DP3 - CAMEL REJECT for PlayAnnouncement
(SSF--SRF)
Register PJPAS is increased by 1, when SRF send REJECT to SSF for PA.
Release history
PJPAS was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PJPAS2

Register PJSRRI 2
Proprietary DP3 - CAMEL REJECT for Specialized Resource Report
(SSF--SRF)
Register PJSRRI is increased by 1, when SSF send REJECT to SRF for SRR.
Release history
PJSRRI was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PJSRRI2
Register PEPCUIS 2
Proprietary DP3 - CAMEL return ERROR for
PromptAndCollectUserInformation (SSF--SRF)
Register PEPCUIS is increased by 1, when SRF return ERROR to SSF for
PCUI.
Release history
PEPCUIS was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PEPCUIS2

Register PJPCUIS 2
(SSF--SRF)
Register PJPCUIS is increased by 1, when SRF REJECT to SSF for PCUI.
Release history
PJPCUIS was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PJPCUIS2
Register PJPUIAI 2
Ack (SSF--SRF)
Register PJPUIAI is increased by 1, when SSF REJECT to SRF for
PCUI_ACK.
Release history
PJPUIAI was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PJPUIAI2

Register PECANS 2
Proprietary DP3 - CAMEL return ERROR (CancelFailed) for Cancel
(SSF--SRF)
Register PECANS is increased by 1, when SRF return ERROR to SSF for
CANCEL.
Release history
PECANS was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PECANS2
Register PJCANS 2
Proprietary DP3 - CAMEL REJECT for Cancel (SSF--SRF)
Register PJCANS is increased by 1, when SRF REJECT to SCF for
CANCEL.
Release history
PJCANS was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PJCANS2

Register PCPFIC 2
Proprietary DP3 - CAMEL failed to relay operations from IP to SCP
Register PCPFIC is increased by 1, when SRR, PCUI_ACK, ERROR and
REJECT relay failure due to SSF internal call processing failure. In this case,
SSF does not return ERROR or REJECT to SRF.
Release history
PCPFIC was created in UMTS03/GSM17.
Register type
Peg
None
Associated logs
None
Extension register
PCPFIC2

DRM
Distributed Record Manager 2
The OM, DRM, track sthe number of application records, blocks of records
written to disk, and the number of file rotations.
Registers
DRM registers may be displayed at the DMS-MAP as follows:
RECORDS RECORDS2 BLOCKS ROTATES
Release history
DRM was created in BCS34.
Group structure
Key field: APPLNAME
Info field: None
Number of tuples: 32
Datafill
Corresponds to applications in table DRMAPPL.
None
Validation formula
Can be verified through observation and interrogation of the files created via
DRM. This would require an understanding of the application which uses
DRM.
Associated products
BillingServer
Register RECORDS 2
Register RECORDS is a count of the number of individual DRM application
records written into a block. A block will contain one or more records
grouped together to be written to disk. As an application request DRM to
write a block to disk it will also pass DRM a count of the application records
in that block. The number of records is not used by DRM except to add to the
RECORDS register.

Release history
RECORDS was created in BCS34.
Register type
Peg
RECORDS is loosely associated with BLOCKS in that it will increase by n as
BLOCKS increases (i.e. each time a BLOCK is incremented the count of
application records within the block will also be added too)
Validation formula
The relationship is completely dictated by the DRM application. If the
application chooses to place 10 records in a block and then gives that block to
DRM to write to disk then RECORDS will increase by 10 and BLOCKS by 1.
Associated logs
LOG NUMBER: None.
Extension register
RECORDS2
Register BLOCKS 2
Register BLOCKS is a count of the number of blocks DRM was given to
write to disk. The block size is completely dictated by the DRM application.
A block is a collection of one or more application records.
Release history
BLOCKS was created in BCS34.
Register type
Peg
BLOCKS is loosely associated with RECORDS in that it will increase by n as
RECORDS increases.
Validation formula
The relationship is completely dictated by the DRM application. If the
application chooses to place 10 records in a block and then gives that block to
DRM to write to disk then RECORDS will increase by 10 and BLOCKS by 1.
Associated logs
LOG NUMBER: None.

Extension register
None
Register ROTATES 2
Register ROTATES is a count of the number of new files opened.
Release history
ROTATES was created in BCS34.
Register type
Peg
None
Validation formula
None
Associated logs
LOG NUMBER: None
Extension register
None

DSPRMAN
Digital Signal Processor Resource module Management 2
The DSPRMAN (Digital Signal Processor Resource module Management)
group is used primarily to check capacity. Most of the measures relate to the
usage of the resources on a SPM node and to measure trouble due to the
number of lost resources.
DSPRMAN contains 21 peg registers that measure COntinuity Test (COT),

DTMF and Tone Synthesis (TONSYN) resource events and usage statistics
on the SPM peripheral in the SPM OC-3 IEC Trunking application. These
resources only exist on DSP RMs on an SPM node. These registers’ reports
include:
• available resource low-water-mark threshold violations

• resources lost
• resources denied
• resources utilized
• the highest number of resources allocated
Resources can be lost if an attempt was made to spare a failed RM and there
was no spare RM. Non-restorable resources (COT, DTMF, TONESYN) are
always lost when an uncontrolled sparing action occurs. For controlled
sparing actions, in-use non-restorable resources are deloaded (gracefully
relinquished by Call Processing).
If the collection period is 30 minutes, there will be a collection of the data

every 15 minutes, and the data from each 15 minute transfer must be
combined to make a composite set of measurements for the one 30 minute
collection.
When collecting OMs from peripherals, the OM Base Software on the CM

gets the data for the active registers one minute before the end of the
collection period. Under control of the OM Base software, at the end of the
collection period, all of the active registers become the holding registers and
the active registers are cleared.
Therefore, when using the CMCI command OMSHOW to see OM data, the
active registers will usually be seen to be all zeroes, except for this last minute
of the collection period. Therefore, users of OMSHOW will usually want to
look at the data in the holding registers. The real-time data for the active
registers can be viewed directly on the SPM peripherals. Use the CM tool
remlogin to remotely login to the SPM of interest, at the SPM, change to the
directory omutils and use the ci command print to see the active data.

DSPRMAN Logic Flow

When an resource is requested from SPM Resource Management, to be attached
to a trunk/call, the following high-level steps which result in OMs are followed:
• If a resource is available in the pool,
— Resource Management increments an internal usage count pertaining
to the resource type. If the total allocated is greater than the current
value of the high-water-mark, then the high-water-mark register is set
to the new maximum value.
• If a resource is not available for use in the pool,
— Resource Management increments the DENY register pertaining to
the resource type.
• If a resource has been allocated/given to a user (CallP), and if the number
of free resources in the pool is at or below the low-water-mark threshold
on the pool,
— RMAN increments the LOW register count pertaining to the resource
type requested. (An alarm may also be generated.)
• If Resource Management must take a resource away from a user (CallP)
due to a RM sparing action,
— RMan increments the LOST register pertaining to the resource type.
All non-restorable resources are always lost in uncontrolled sparing
actions.
— ECANs are restorable resources, so they are not lost in the event of
sparing an RM. When a controlled sparing action occurs, resources
are gracefully deloaded by CallP and are therefore usually not lost.
• Should CallP not relinquish a non-restorable resource, in order to
complete the sparing action,
— Resource Management takes the non-restorable resource away from
CallP.
— This results in RMAN incrementing the LOST register for each
resource type for each lost non-restorable resource.
On the local SPM’s active CEM, at the end of a 100 second scan period,
Resource Management calculates the percentage utilization of the resources
in each of the resource pools and re-computes the average for all previous
scan periods since the beginning of the current collection period and this
value is written to the OM register for percentage utilization of the resource
type.
At the end of a transfer/collection period, all registers are zeroed.

Registers
DSPRMAN registers may be displayed at the DMS-MAP as follows:
COTLOW COTLOST COTDENY COTUTIL

COTHI COTFAIL DTMFLOW DTMFLOST
DTMFDENY DTMFUTIL DTMFHI MFLOW
MFLOST MFDENY MFUTIL MFHI
TONELOW TONELOST TONEDENY TONEUTIL
TONEHI
Release history
DSPRMAN was created in GSM07.
Group structure
DSPRMAN provides one tuple for each MSC/Call Server.
Key field: nil_type_id
Info field: sots_NODE_INFO
Datafill
At least one DSP RM must be provisioned in the SPM table MNCKTPAK
and resource pools must be selected for one or more of the types supported on
a DSP RM.
Group ECANRMAN contains OMs for other resource types existing on SPM
nodes. It also contains OMs for resources managed by SPM Resource
Management.
Validation formula
None
Associated products
SPM OC-3 IEC Trunking.
Register COTLOW 2
COT Low-Water Mark threshold violations on the node-level COT pool
COTLOW is a count of the number of low-water-mark threshold violations
on the SPM node-level pool of COT resources since the last collection period.
The threshold being crossed once is an indication of potential resource
exhaustion on the node. When the low-water-mark threshold is crossed more
than once in a collection period, this indicates the (CallP) user was operating
around the threshold for a while. This means resources were freed, the total

number free became more than the threshold, but then some more allocations
took place and the threshold was crossed again.
Operating at the threshold for a long period of time is a strong indication that
the (Telco) user is in danger of running out of those types of resources on the
node. The corrective action is to provision another RM or another SPM to
support the call rate and call mix.
Release history
COTLOW was created in GSM07.
Register type
Peg
COTUTIL - the percentage of COTs at the node-level is to be considered high
at the time the low-water-mark threshold is crossed. One can compute it using
the threshold value and the queue size obtained from the SPM node level
MAP.
Extension register
None
Associated logs
SPM350
Register COTLOST 2
Number of COT resources taken away from or lost by Resource
Management Users (CallP)
COT pegs the number of COT resources which were taken away from users
(CallP) of SPM Resource Management due to sparing actions.
Release history
COTLOST was created in GSM07.
Register type
Peg
None
Extension register
None

Associated logs
None
Register COTDENY 2
COT requests denied
COTDENY pegs the count of COT resources denied to users.
Release history
COTDENY was created in GSM07.
Register type
Peg
COTUTIL. One would expect the percentage utilization (COTUTIL) to be
100%, provided the user is trying to get a resource when the pool of resources
is available to the user.
Extension register
None
Associated logs
None
Register COTUTIL 2
COT resource percent utilization
The percentage of the total number of COT resources in the node-level pool
which are allocated to users (CallP) of Resource Management and it is the
average percentage utilization for all scan periods (100 second) during a
collection/transfer period. It does not indicate the total number in-use at the
end of a scan or transfer period.
Release history
COTUTIL was created in GSM07.
Register type
Peg
None
Extension register
None

Associated logs
None
Register COTHI 2
COT High-Water Mark for COT allocations from the COT pool
COTHI pegs the highest number of COT resources that was allocated at any
instant from the node-level pool during a collection/transfer period. Its value
starts off at zero at the beginning of each collection/transfer period for the
node. An update occurs when there is a new high-water-mark in the collection
period and this occurs when the total number of resources allocated from the
COT pool exceeds the previous high-water-mark for the pool.
Release history
COTHI was created in GSM07.
Register type
Peg
None
Extension register
None
Associated logs
None
Register COTFAIL 2
Continuity Test Failed for the CCS7 trunk
COTFAIL pegs the number of CCS7 Continuity Test Failures for Trunks on
the SPM node. These events are reported by the DSP Application running on
the RM and they are pegged on the Active CEM of each SPM peripheral.
Release history
COTFAIL was created in GSM07.
Register type
Peg
None
Validation formula
None. The count must be less than or equal to the number of COT tests
performed on the SPM during the OM Collection period.

Extension register
None
Associated logs
None
Register DTMFLOW 2
DTMF Low-Water Mark threshold violations on the node-level DTMF pool
DTMFLOW is a count of the number of low-water-mark threshold violations
on the SPM node-level pool of DTMF resources since the last collection
period. The threshold being crossed once is an indication of potential resource
Release history
DTMFLOW was created in GSM07.
Register type
Peg
DTMFUTIL - the percentage of DTMFs at the node-level is to be considered
high at the time the low-water-mark threshold is crossed. One can compute it
using the threshold value and the queue size obtained from the SPM node
level MAP.
Extension register
None
Associated logs
SPM350
Register DTMFLOST 2
Number of DTMF resources taken away from or lost by Resource
DTMFLOST pegs the number of DTMF resources which were taken away
from users (CallP) of SPM Resource Management due to sparing actions.

Release history
DTMFLOST was created in GSM07.
Register type
Peg
None
Extension register
None
Associated logs
None
Register DTMFDENY 2
DTMF resources denied
DTMFDENY pegs the count of DTMF resources denied to users.
Release history
DTMFDENY was created in GSM07.
Register type
Peg
DTMFUTIL. One would expect the percentage utilization (DTMFUTIL) to
be 100%, provided the user is trying to get a resource when the pool of
resources is available to the user.
Extension register
None
Associated logs
None
Register DTMFUTIL 2
Percent Utilization of DTMF resources
The percentage of the total number of DTMF resources in the node-level pool

Release history
DTMFUTIL was created in GSM07.
Register type
Peg
None
Extension register
None
Associated logs
None
Register DTMFHI 2
DTMF High-Water Mark for Allocations from the DTMF pool
DTMFHI pegs the highest number of DTMF resources that was allocated at
any instant from the node-level pool during a collection/transfer period. Its
value starts off at zero at the beginning of each collection/transfer period for
the node. An update occurs when there is a new high-water-mark in the
collection period and this occurs when the total number of resources allocated
from the DTMF pool exceeds the previous high-water-mark for the pool.
Release history
DTMFHI was created in GSM07.
Register type
Peg
None
Extension register
None
Associated logs
None
Register TONELOW 2
ToneSyn Low-Water Mark threshold violations on the node-level
ToneSyn pool
TONELOW is a count of the number of low-water-mark threshold violations
on the SPM node-level pool of ToneSyn resources since the last collection


Release history
TONELOW was created in GSM07.
Register type
Peg
TONEUTIL - the percentage of ToneSyns at the node-level is to be
considered high at the time the low-water-mark threshold is crossed. One can
compute it using the threshold value and the queue size obtained from the
SPM node level MAP.
Extension register
None
Associated logs
None
Register TONELOST 2
ToneSyn resources taken away from or lost by Resource Management
Users (CallP)
TONELOST pegs the number of ToneSyn resources which were taken away
Release history
TONELOST was created in GSM07.
Register type
Peg
None

Extension register
None
Associated logs
None
Register TONEDENY 2
ToneSyn resources denied
TONEDENY pegs the count of ToneSyn resources denied to users.
Release history
TONEDENY was created in GSM07.
Register type
Peg
TONEUTIL. One would expect the percentage utilization (TONEUTIL) to be
Extension register
None
Associated logs
None
Register TONEUTIL 2
Percent Utilization of ToneSyn resources
The percentage of the total number of ToneSyn resources in the node-level
pool which are allocated to users (CallP) of Resource Management and it is
the average percentage utilization for all scan periods (100 second) during a
Release history
TONEUTIL was created in GSM07.
Register type
Peg
None

Extension register
None
Associated logs
SPM350
Register TONEHI 2
High-Water Mark for ToneSyn resource allocations from the ToneSyn
pool
TONEHI pegs the highest number of ToneSyn resources that was allocated at
from the ToneSyn pool exceeds the previous high-water-mark for the pool.
Release history
TONEHI was created in GSM07.
Register type
Peg
None
Extension register
None
Associated logs
None
Register MFLOW 2
MF Low-Water Mark threshold violations on the node-level MF pool
MFLOW is a count of the number of low-water-mark threshold violations on
the SPM node-level pool of MF resources since the last collection period. The
threshold being crossed once is an indication of potential resource exhaustion
on the node. When the low-water-mark threshold is crossed more than once in
a collection period, this indicates the (CallP) user was operating around the
threshold for a while. This means resources were freed, the total number free
became more than the threshold, but then some more allocations took place
and the threshold was crossed again.


Release history
MFLOW was created in GSM07.
Register type
Peg
MFUTIL - the percentage of ToneSyns at the node-level is to be considered
level MAP.
Extension register
None
Associated logs
None
Register MFLOST 2
Number of MF resources taken away from or lost by Resource
MFLOST pegs the number of MF resources which were taken away from
users (CallP) of SPM Resource Management due to sparing actions.
Release history
MFLOST was created in GSM07.
Register type
Peg
None
Extension register
None
Associated logs
None

Register MFDENY 2
MF resources denied (CallP failed to Allocate for
a call)
MFDENY pegs the count of MF resources denied to users.
Release history
MFDENY was created in GSM07.
Register type
Peg
MFUTIL. One would expect the percentage utilization (MFUTIL) to be
Extension register
None
Associated logs
None
Register MFUTIL 2
Average Percent Utilization of MF resources
The percentage of the total number of MF resources in the node-level pool
Release history
MFUTIL was created in GSM07.
Register type
Peg
None
Extension register
None
Associated logs
SPM350

Register MFHI 2
High-Water Mark for MF resource allocations from the MF pool
MFHI pegs the highest number of MF resources that was allocated at any
instant from the node-level pool during a collection/transfer period. Its value
starts off at zero at the beginning of each collection/transfer period for the
node. An update occurs when there is a new high-water-mark in the collection
period and this occurs when the total number of resources allocated from the
MF pool exceeds the previous high-water-mark for the pool.
Release history
MFHI was created in GSM07.
Register type
Peg
None
Extension register
None
Associated logs
SPM350


DUTLGEN
The OM group, DUTLGEN, provides general information about the DUTL's
operation.
Registers
DUTLGEN registers may be displayed at the DMS-MAP as follows:
DUTLSYEV DUTLCOEV DUTLREEV DUTLDIEV

DUTLPRER DUTLSYER
Release history
DUTLGEN was created in BSC27.
Group structure
Key field: None
Info field: None
Register DUTLSYEV 2
The number of System Events that transpire within DUT.
Release history
DUTLSYEV was created in BSC27.
Register type
Peg
Register DUTLCOEV 2
The number of Connect Events that occur within DUTL.
Release history
DUTLCOEV was created in BSC27.
Register type
Peg
Register DUTLREEV 2
The number of Refuse Events that happen within DUTL.
Release history
DUTLREEV was created in BSC27.

Register type
Peg
Register DUTLDIEV 2
The number of Disconnect Events that appear within DUTL.
Release history
DUTLDIEV was created in BSC27.
Register type
Peg
Register DUTLPRER 2
The number of Protocol Errors that are found within DUTL.
Release history
DUTLPRER was created in BSC27.
Register type
Peg
Register DUTLSYER 2
The number of System Errors that take place within DUTL.
Release history
DUTLSYER was created in BSC27.
Register type
Peg


3-1
OM groups: E 3
DMS-MSC/Call Server for GSM, whose names begin with “E”.

3-2 OM groups: E
ECANRMAN
Echo Canceller Resource Management 3
The ECANRMAN (Echo Canceller Resource Management) group contains
measures for echo canceller resource events and usage statistics on the SPM.
This group contains six registers that count the following events:
• available resource low-water-mark threshold violations
• resources lost
• resources denied
• SOS events
• resources utilized
• the highest number of resources allocated
The OMs are cleared at the beginning of every collection period. Therefore,
they represent what has taken place during the last collection period. If the
collection period is 30 minutes, there will be a collection of the data every 15
minutes, and the data from each 15 minute transfer must be combined to
make a composite set of measurements for the one 30 minute collection.
When collecting OMs from peripherals, the OM Base Software on the CM

gets the data for the active registers one minute before the end of the
collection period. Under control of the OMBase software, at the end of the
collection period, all of the active registers become the holding registers and
the active registers are cleared.
Therefore, when using the CMCI command OMSHOW to see OM data, the
active registers will usually be seen to be all zeroes, except for this last minute
of the collection period. Therefore, users of OMSHOW will usually want to
look at the data in the holding registers. The real-time data for the active
registers can be viewed directly on the SPM peripherals. Use the CM tool
remlogin to remotely login to the SPM of interest, at the SPM, change to the
directory omutils and use the ci command print to see the active data.
ECANRMAN Logic Flow 3

When an ECAN resource is requested from SPM Resource Management, to be
attached to a trunk:
• If one is available in the ECAN pool, then RMan increments an internal
usage counter for the total number of resources allocated from the pool.
• If the usage counter is greater than the current value of the high-
watermark (maximum number of resources allocated at any one instance
during the last scan period) then RMan updates the high-water-mark
register (field) for the scan period.

OM groups: E 3-3
• If one is not available for use in the ECAN pool, then RMan increments
the ECANDENY register.
• If an ECAN resource has been allocated/given to a user (CallP) and if the
number of free resources in the pool is at or below the low-water-mark
threshold on the ECAN pool, then RMan increments the ECANLOW
register (field). An alarm should also be generated.
If an ECAN resource agent gets a message from the resource it represents

which indicates that it has failed to converge (cancel the echo) (either due to
the limits of its parameters (as set in table SPMECAN) or due to an algorithm
failure), then RMan increments the ECANFAIL register.
If Resource Management must take an ECAN resource away from a user

(CallP) due to a RM sparing action, it increments the ECANLOST register.
Note: All non-restorable resources are always lost in sparing actions.

ECAN is a restorable resource, so it is not lost in the event of sparing an
RM. When a controlled sparing action occurs, resources are gracefully
released by CallP and they are therefore not lost. In the event of an RM
failure (critical fault) and there is no spare RM, then all resources on the
failed RM are lost.
Registers
ECANRMAN registers may be displayed at the DMS-MAP as follows:
ECANLOW ECANLOST ECANDENY ECANFAIL

ECANUTIL ECANHI ATMPTSOV ATMPTS
USGSECS
Note: Fields (registers) ATMPTSOV, ATMPTS, and USGSECS are

displayed as part of the OMGROUP but are not used in GSM.
Release history
ECANRMAN was created in GSM07.
Group structure
ECANRMAN provides one tuple for each MSC/Call Server.
Key field: nil_type_id
Info field: sots_NODE_INFO
Datafill
For NORTEL Echo Cancellers, a VSP RM must be datafilled in SPM Table
MNCKTPAK.

3-4 OM groups: E
ECANRMAN contains OMs for resources managed by SPM Resource
Management.
Validation formula
There is no mathematical relationship between the groups.
For the ECAN set of resources, or the set of resources of any type, at any
given instant, there is a mathematical relationship between the number of
resources free and in-use. (But these numbers are not output as OMs. They
are visible by a MAP interface.) If the low-water-mark threshold is set to 60%
of the total number of resources in the pool, when the threshold is reached,
the number of resources in-use must be equal to 60% and the number free
must be 40% of the total number in the pool.
Associated products
SPM OC-3 IEC Trunking
Register ECANLOW 3
ECAN Low-Water mark threshold violations on the node-level ECAN pool
ECANLOW is a count of the number of low-water-mark threshold violations
on the SPM node-level pool of ECAN resources since the last collection
Release history
ECANLOW was created in GSM07.
Register type
Peg
ECANUTIL - the percentage of ECANs at the node-level is to be considered
level MAP.

OM groups: E 3-5
Extension register
None
Associated logs
SPM350
Register ECANLOST 3
ECAN resources lost or taken away from Callp
ECANLOST pegs the number of ECAN resources which were taken away
Release history
ECANLOST was created in GSM07.
Register type
Peg
None
Extension register
None
Associated logs
None
Register ECANDENY 3
ECAN requests denied
ECANDENY pegs the count of ECAN resources denied to users.
Release history
ECANDENY was created in GSM07.
Register type
Peg
ECANUTIL. One would expect the percentage utilization (ECANUTIL) to
be 100%, provided the user is trying to get a resource when the pool of
resources is available to the user.
Extension register
None

3-6 OM groups: E
Associated logs
None
Register ECANFAIL 3
ECAN failures to converge (SOS) events
ECANFAIL pegs when an ECAN resource sends an SOS message to its
resource agent. This message is sent when a sustained degradation in
performance is detected by the ECAN resource.
Release history
ECANFAIL was created in GSM07.
Register type
Peg
None
Extension register
None
Associated logs
None
Register ECANUTIL 3
ECAN Percentage Utilization
The percentage of the total number of ECAN resources in the node-level pool
Release history
ECANUTIL was created in GSM07.
Register type
Peg
None
Extension register
None

OM groups: E 3-7
Associated logs
None
Register ECANHI 3
ECAN High-Water Mark for Usage
ECANHI pegs the highest number of ECAN resources that was allocated at
from the ECAN pool exceeds the previous high-water-mark for the pool.
Release history
ECANHI was created in GSM07.
Register type
Peg
None
Extension register
None
Associated logs
None

3-8 OM groups: E
EIUETHER
Ethernet Interface Unit ETHERnet 3
The OM group, EIUETHER, allows access to traffic information at the
Ethernet protocol level. The information given by this group of OMs include
the total counts of incoming and outgoing packets and bytes at the Ethernet
interface in a longword format. The counts are accumulated over the OM
transfer period. This group of OMs can be used for traffic measurements of
EIU.
Registers
EIUETHER registers may be displayed at the DMS-MAP as follows:
EIURXBYT EIURXPKT EIURXBCA EIURXDIS

EIURXERR EIURXUPP EIURXBY2 EIURXPK2
EIURXBC2 EIURXDI2 EIURXER2 EIURXUP2
EIUTXBYT EIUTXPKT EIUTXBCA EIUTXDIS
EIUTXERR EIUTXBY2 EIUTXPK2 EIUTXBC2
EIUTXDI2 EIUTXER2
Release history
EIUETHER was created in BSC31.
Group structure
Key field: None
Info field: EIU nnn , where nnn is between 0 and 750
Number of tuples: one per EIU
Datafill
For each EIU datafilled in the LIUINV table, there will be one tuple of OMs
of this group.
None
Validation formula
None
Associated products
None

OM groups: E 3-9
Register EIURXBYT 3
EIU Ethernet Receive BYTes
This is the number of bytes received on the ethernet interface, including
frame check sequence bytes. This register along with others in this group are
used for EIU traffic and performance measurements.
Release history
EIURXBYT was created in BSC31.
Register type
Peg
None
Validation formula
None
Extension register
EIURXBY2
Register EIURXPKT 3
EIU Ethernet Receive PacKeTs
This is the number of unicast packets delivered to a higher-layer protocols
such as IP or ARP on an EIU. This register along with others in this group are
Release history
EIURXPKT was created in BSC31.
Register type
Peg
None
Validation formula
None
Associated logs
None
Extension register
EIURXPK2

3-10 OM groups: E
Register EIURXBCA 3
EIU Ethernet Receive BroadCAsts
This is the number of broadcast packets delivered to a higher-layer protocols
such as IP or ARP. This register along with others in this group are used for
EIU traffic and performance measurements.
Release history
EIURXBCA was created in BSC31.
Register type
Peg
None
Validation formula
None
Associated logs
None
Extension register
EIURXBC2
Register EIURXDIS 3
EIU Ethernet Receive DIScards
This is the minimum number of received packets which were chosen to be
discarded even though no errors in the packet itself are detected. Possible
reason for discarding a packet is due to resource limitations in the EIU (no
free buffers to hold a received packet). This register along with others in this
group are used for EIU traffic and performance measurements.
Release history
EIURXDIS was created in BSC31.
Register type
Peg
None
Validation formula
None

OM groups: E 3-11
Associated logs
None
Extension register
EIURXDI2
Register EIURXERR 3
EIU Ethernet Receive ERRer
This is the number of received packets that contained errors. This register
along with others in this group are used for EIU traffic and performance
measurements.
Release history
EIURXERR was created in BSC31.
Register type
Peg
None
Validation formula
None
Associated logs
None
Extension register
EIURXER2
Register EIURXUPP 3
EIU Ethernet Receive Unknown Protocol Packets
This is the number of packets discarded because of an unknown or
unsupported protocol. This register along with others in this group are used
for EIU traffic and performance measurements.
Release history
EIURXUPP was created in BSC31.
Register type
Peg
None

3-12 OM groups: E
Validation formula
None
Associated logs
None
Extension register
EIURXUP2
Register EIUTXBYT 3
EIU Ethernet Transmit BYTes
This is the number of bytes transmitted out of the Ethernet interface,
including frame check sequence bytes. This register along with others in this
group are used for EIU traffic and performance measurements.
Release history
EIUTXBYT was created in BSC31.
Register type
Peg
None
Validation formula
None
Associated logs
None
Extension register
EIUTXBY2
Register EIUTXPKT 3
EIU Ethernet Transmit PacKeTs
This is the number of packets that higher-layer protocols requested to be
transmitted to a unicast Ethernet address. This register along with others in
this group are used for EIU traffic and performance measurements.
Release history
EIUTXPKT was created in BSC31.
Register type
Peg

OM groups: E 3-13
None
Validation formula
None
Associated logs
None
Extension register
EIUTXPK2
Register EIUTXBCA 3
EIU Ethernet Transmit BroadCAsts
This is the number of packets that higher-layer protocols requested to be
transmitted to a broadcast Ethernet address. This register along with others in
this group are used for EIU traffic and performance measurements.
Release history
EIUTXBCA was created in BSC31.
Register type
Peg
None
Validation formula
None
Associated logs
None
Extension register
EIUTXBC2
Register EIUTXDIS 3
EIU Ethernet Transmit BYTes
This is the number of outbound packets which were chosen to be discarded
even though no errors are detected to prevent their being transmitted. Possible
reason for discarding a packet is due to resource limitations in the EIU (no
free buffers to hold a packet). This register along with others in this group are

3-14 OM groups: E
Release history
EIUTXDIS was created in BSC31.
Register type
Peg
None
Validation formula
None
Associated logs
None
Extension register
EIUTXDI2
Register EIUTXERR 3
EIU Ethernet Transmit Error
This is the number of outbound packets that could not be transmitted because
of errors. This register along with others in this group are used for EIU traffic
and performance measurements.
Release history
EIUTXERR was created in BSC31.
Register type
Peg
None
Validation formula
None
Associated logs
None
Extension register
EIUTXER2

OM groups: E 3-15

3-16 OM groups: E
EMLPPSS
Enhanced Multi-Level Precedence and Preemption Supplementary
Services 3
OM group enhanced Multi-Level Precedence and Preemption (eMLPP)
Supplementary Services (EMLPPSS) gathers information on the eMLPP
supplementary service for each call. Currently there are seven precedence
levels defined and each call may belong to any one of the precedence levels.
The OM for the calling subscriber is pegged only if the calling subscriber has
an eMLPP subscription. The OM for the calling subscriber will be pegged
with the precedence level {4, 3, 2, 1, 0, B, A} found in the CM Service
Request message.
If there is no precedence found in the CM Service Request message, the OM

is not pegged for the originator.
Since the precedence level for the called party is the precedence of the calling
subscriber, it is always pegged for the called party.
This OM group provides information specific to GSM-Railways

functionality.
Registers
The following EMLPPSS registers may be displayed:
• PRECDNC4
• PRECDNC3
• PRECDNC2
• PRECDNC1
• PRECDNC0
• PRECDNCB
• PRECDNCA
Release history
EMLPPSS was created in GSMR01.
Group structure
EMLPPSS provides seven tuples per DMS-MSC/Call Server.

OM groups: E 3-17
Key field: None
Info field: None
None
Associated products
None
Validation Formula
None
Register PRECDNC0 3
Precedence Level 0
Register PRECDNC0 is a peg register that counts the number of calls
belonging to this particular precedence level.
Release history
Register PRECDNC0 was created in GSMR01.
Associated register
None
Validation formula
None
Associated logs
None
EXT register
None
Register PRECDNC1 3
Precedence Level 1
Release history
Associated register
None

3-18 OM groups: E
Validation formula
None
Associated logs
None
EXT register
None
Register PRECDNC2 3
Precedence Level 2
Release history
Associated register
None
Validation formula
None
Associated logs
None
EXT register
None
Register PRECDNC3 3
Precedence Level 3
Release history
Associated register
None
Validation formula
None

OM groups: E 3-19
Associated logs
None
EXT register
None
Register PRECDNC4 3
Precedence Level 4
Release history
Associated register
None
Validation formula
None
Associated logs
None
EXT register
None
Register PRECDNCA 3
Precedence Level A
Register PRECDNCA is a peg register that counts the number of calls
Release history
Register PRECDNCA was created in GSMR01.
Associated register
None
Validation formula
None
Associated logs
None

3-20 OM groups: E
EXT register
None
Register PRECDNCB 3
Precedence Level B
Register PRECDNCB is a peg register that counts the number of calls
Release history
Register PRECDNCB was created in GSMR01.
Associated register
None
Validation formula
None
Associated logs
None
EXT register
None

OM groups: E 3-21
ETCHIMMU
ETSI Call Handling Dialogue Initiator on the MMU 3
For a dialogue initiator, ETCHIMMU measures the number of fall backs to
and from the Call Handling related application context versions. The fields
represent the various application contexts, and the tuples represent the
Registers
The following ETCHIMMU registers may be displayed:
ERNERQMU ERNERMU2 ERNEFBMU ERNEFMU2
ELIRRQMU ELIRFBMU EHOCRQMU EHOCFBMU
ECCTRQMU ECCTFBMU
Release history
ETCHIMMU was created in GSM11.
Group structure
Number of tuples: One per Server.
ETSICHI
Associated products
MMU
Validation Formula

3-22 OM groups: E
Register ECCTFBMU 3
This register reflects the summarized OM data of version1, version2 and
version2+.
Release history
ECCTFBMU was made available in GSM11.
Register type
Peg
Extension register
ETICCTFB
Registr ECCTRQMU 3
This register reflects the summarized OM data of version1, version2 and
version2+.
Release history
ECCTRQMU was made available in GSM11.
Register type
Peg
Extension register
ETICCTRQ
Register EHOCFBMU 3
Number of Fallbacks to HandoverControl(11) Context per MMU
Register EHOCFBMU is a peg register that records the number of fallbacks
to the various HandoverControl(11) context versions performed by the
DMS-MSC/Call Server. Tuples of this register represent versions. By

examining the tuples in this register and the tuples in EHOCRQMU, which
records the number of fall backs from the HandoverControl(11) context
versions, the operator gets an indication of the HandoverControl(11) context
versions provisioned in the network.
Release history
Register EHOCFBMU was created in GSM11.
Associated register
EHOCRQMU
GMPHOREQ and GMPHORES from group GMAPCH.

OM groups: E 3-23
Validation formula
On the DMS-MSC/Call Server, the number of pegs to registers GMPHOREQ
from group GMAPCH is greater or equal to the sum of the number of pegs to
registers GMPHORES from group GMAPCH and EHOCFBMU.
On the DMS-MSC/Call Server, the number of pegs to register EHOCFBMU

is less than or equal to the number of pegs to register EHOCRQMU.
Associated logs
None
EXT register
None
Register EHOCRQMU 3
Number of Fallbacks from Handover Control(11) Context per MMU.
Register EHOCRQMU is a peg register that records the number of fall backs
from the various HandoverControl(11) context versions performed by the
examining the tuples in this register and the tuples in EHOCFBMU, which
records the number of fall backs to the HandoverControl(11) context
Release history
Register EHOCRQMU was created in GSM11.
Associated register
EHOCFBMU
Validation formula
registers GMPHORES from group GMAPCH and EHOCRQMU.
On the DMS-MSC/Call Server, the number of pegs to register EHOCRQMU

is greater than or equal to the number of pegs to register EHOCFBMU.
Associated logs
None

3-24 OM groups: E
EXT register
None
Register ELIRFBMU 3
Number of fallbacks to LocationInfo Retrievals(5) context per MMU.
Register ETILIRPFB is a peg register that records the number of fallbacks to

the various LocationInfoRetrieval(5) context versions performed by the?.

examining the tuples in this register and the tuples in ELIRRQMU, which
records the number of fall backs from the LocationInfoRetrieval(5) context
versions, the operator gets an indication of the LocationInfoRetrieval(5)
context versions provisioned in the network.
Release history
Register ETILIRPFB was created in GSM11.
Associated register
ELIRRQMU
GMSRIREQ and GMSRIRES from group GMAPCH.
Validation formula
On the DMS-MSC/Call Server, the number of pegs to registers GMSRIREQ
from group GMAPCH is greater than or equal to the sum of the number of
pegs to registers GMSRIRES from group GMAPCH and ELIRFBMU.
On the DMS-MSC/Call Server, the number of pegs to register ELIRFBMU is

less than or equal to the number of pegs to register ELIRRQMU.
Associated logs
None
EXT register
None
Register ELIRRQMU 3
Number of Fallbacks from LocationInfoRetrieval(5) Context per MMU.
Register ELIRRQMU is a peg register that records the number of fall backs
from the various LocationInfoRetrieval(5) context versions performed by the
examining the tuples in this register and the tuples in ELIRFBMU, which
record the number of fall backs to the LocationInfoRetrieval(5) context

OM groups: E 3-25

Release history
Register ELIRRQMU was created in GSM11.
Associated register
ELIRFBMU
Validation formula
pegs to registers GMSRIRES from group GMAPCH and ELIRRQMU.
On the DMS-MSC/Call Server, the number of pegs to register ELIRRQMU is

greater than or equal to the number of pegs to register ELIRFBMU.
Associated logs
None
EXT register
None
Register ERNEFBMU 3
Number of Fallbacks to RoamingNumberEnquiry(3) Context per MMU.
ERNEFBMU records the number of fallbacks to the various

RoamingNumberEnquiry(3) context versions performed by the DMS-HLR.
Tuples of this register represent versions. By examining the tuples in this
register and the tuples in ERNERQMU, which records the number of fall
backs from the RoamingNumberEnquiry(3) context versions, the operator
gets an indication of the RoamingNumberEnquiry(3) context versions
provisioned in the network.
Release history
Register ERNEFBMU was created in GSM11.
Associated register
ERNERQMU
Validation formula
On the DMS-HLR, the number of pegs to register ETILUPFB is less than or
equal to the number of pegs to register ETILUPRQ.

3-26 OM groups: E
Associated logs
None
EXT register
ERNEFMU2
Register ERNERQMU 3
Number of Fallbacks from RoamingNumberEnquiry(3) Context per MMU.
Register ERNERQMU is a peg register that records the number of fall backs
from the various RoamingNumberEnquiry(3) context versions performed by
the DMS-HLR. Tuples of this register represent versions. By examining the
tuples in this register and the tuples in ERNEFBMU, which record the
number of fall backs to the RoamingNumberEnquiry(3) context versions, the
operator gets an indication of the RoamingNumberEnquiry(3) context
Release history
Register ERNERQMU was created in GSM11.
Associated register
ERNEFBMU
Validation formula
On the DMS-HLR, the number of pegs to register ERNERQMU is greater
than or equal to the number of pegs to register ERNEFBMU.
Associated logs
None
EXT register
ERNERMU2

OM groups: E 3-27
ETCHRMMU
ETSI Call Handling Dialogue Responder on the MMUs 3
For a dialogue responder, ETCHRMMU measures the number of fall backs to
and from the Call Handling related application context versions. The fields
Registers
The following ETCHRMMU registers may be displayed:
ERNERQMU ERNEFBMU ELIRRQMU ELIRRMU2
ELIRFBMU ELIRFMU2 EHOCRQMU EHOCFBMU
Release history
ETCHRMMU was created in GSM11.
Group structure
ETSICHR
Associated products
MMU
Validation Formula
Register ERNERQMU 3
Number of fall backs from the various RoamingNumberEnquiry(3) context
versions per MMU.

3-28 OM groups: E
Register ERNERQMU is a peg register that records the number of fall backs
from the various RoamingNumberEnquiry(3) context versions recommended
by the DMS-MSC/Call Server. Tuples of this register represent versions. By
examining the tuples in this register and the tuples in ETRFNEFB, which
records the number of fall backs to the RoamingNumberEnquiry(3) context
versions, the operator gets an indication of the RoamingNumberEnquiry(3)
Release history
Register ERNERQMU was created in GSM11.
Associated register
ERNEFBMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ERNERQMU
is greater than or equal to the number of pegs to register ERNEFBMU.
Associated logs
None
EXT register
None
Register ERNEFBMU 3
Number of fallbacks to the various RoamingNumberEnquiry(3) context
versions per MMU.
Register ERNEFBMU is a peg register that records the number of fallbacks to

the various RoamingNumberEnquiry(3) context versions recommended by
the DMS-MSC/Call Server. Tuples of this register represent versions. By
examining the tuples in this register and the tuples in ERNERQMU, which
records the number of fall backs from the RoamingNumberEnquiry(3)
context versions, the operator gets an indication of the
RoamingNumberEnquiry(3) context versions provisioned in the network.
Release history
Register ERNEFBMU was created in GSM11.
Associated register
ERNERQMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ERNEFBMU
is less than or equal to the number of pegs to register ERNERQMU.

OM groups: E 3-29
Associated logs
None
EXT register
None
Register ELIRRQMU 3
Number of fall backs from the various LocationInfoRetrieval(5) context
versions per MMU.
Register ELIRRQMU is a peg register that records the number of fall backs
from the various LocationInfoRetrieval(5) context versions recommended by
tuples in this register and the tuples in ELIRFBMU, which records the
number of fall backs to the LocationInfoRetrieval(5) context versions, the
operator gets an indication of the LocationInfoRetrieval(5) context versions
Release history
Register ELIRRQMU was created in GSM11.
Associated register
ELIRFBMU
Validation formula
On the DMS-HLR, the number of pegs to register ELIRRQMU is greater than
or equal to the number of pegs to register ELIRFBMU.
Associated logs
None
EXT register
ELIRRMU2
Register ELIRFBMU 3
Number of fallbacks to the various LocationInfoRetrieval(5) context versions
per MMU.
Register ELIRFBMU is a peg register that records the number of fallbacks to

the various LocationInfoRetrieval(5) context versions recommended by the
DMS-HLR. Tuples of this register represent versions. By examining the
tuples in this register and the tuples in ELIRRQMU, which records the
number of fall backs from the LocationInfoRetrieval(5) context versions, the
operator gets an indication of the LocationInfoRetrieval(5) context versions

3-30 OM groups: E
Release history
Register ELIRFBMU was created in GSM11.
Associated register
ELIRRQMU
Validation formula
On the DMS-HLR, the number of pegs to register ELIRFBMU is less than or
equal to the number of pegs to register ELIRRQMU.
Associated logs
None
EXT register
ELIRFMU2
Register EHOCRQMU
Number of fall backs from the various HandoverControl(11) context versions
per MMU.
Register EHOCRQMU is a peg register that records the number of fall backs
from the various HandoverControl(11) context versions recommended by the
examining the tuples in this register and the tuples in EHOCFBMU, which
Release history
Register EHOCRQMU was created in GSM11.
Associated register
EHOCFBMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register EHOCRQMU
is greater than or equal to the number of pegs to register EHOCFBMU.
Associated logs
None
EXT register
None

OM groups: E 3-31
Register EHOCFBMU 3
Number of fallbacks to the various HandoverControl(11) context versions per
MMU.
Register EHOCFBMU is a peg register that records the number of fallbacks

to the various HandoverControl(11) context versions recommended by the
examining the tuples in this register and the tuples in EHOCRQMU, which
record the number of fall backs from the HandoverControl(11) context
Release history
Register EHOCFBMU was created in GSM11.
Associated register
EHOCRQMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register EHOCFBMU
is less than or equal to the number of pegs to register EHOCRQMU.
Associated logs
None
EXT register
None

3-32 OM groups: E
ETEQIMMU
ETSI Equipment Management Dialogue Initiator on the MMU 3
For a dialogue initiator, ETEQIMMU measures the number of fall backs to
and from the Equipment Management related application context versions.
The fields represent the various application contexts, and the tuples represent
the application context versions.
Registers
The following ETEQIMMU registers may be displayed:
EEMNRQMU EEMNFBMU
Release history
ETEQIMMU was created in GSM11.
Group structure
ETSIEQI
Associated products
MMU
Validation Formula
Register EEMNFBMU 3
Number of Fallbacks to EquipmentMngt(13) Context per MMU.
Register EEMNFBMU is a peg register that records the number of fallbacks

to the various EquipmentMngt(13) context versions performed by the?.

OM groups: E 3-33

examining the tuples in this register and the tuples in EEMNRQMU, which
record the number of fall backs from the EquipmentMngt(13) context
versions, the operator gets an indication of the EquipmentMngt(13) context
Associated register
EEMNRQMU
GMCIMREQ and GMCIMRES from group GMAPEMGT.
Validation formula
On the DMS-MSC/Call Server, the number of pegs to registers GMCIMREQ
from group GMAPEMGT is greater than or equal to the sum of the number of
pegs to registers GMCIMRES from group GMAPEMGT and EEMNFBMU.
On the DMS-MSC/Call Server, the number of pegs to register EEMNFBMU

is less than or equal to the number of pegs to register EEMNRQMU.
Associated logs
None
EXT register
None
Register EEMNRQMU 3
Number of Fallbacks from EquipmentMngt(13) Context per MMU.
Register EEMNRQMU is a peg register that records the number of fall backs
from the various EquipmentMngt(13) context versions performed by the
examining the tuples in this register and the tuples in EEMNFBMU, which
record the number of fall backs to the EquipmentMngt(13) context versions,
the operator gets an indication of the EquipmentMngt(13) context versions
Associated register
EEMNFBMU
Validation formula
from group GMAPEMGT is greater or equal to the sum of the number of
pegs to registers GMCIMRES from group GMAPEMGT and EEMNRQMU.

3-34 OM groups: E
On the DMS-MSC/Call Server, the number of pegs to register EEMNRQMU

is greater than or equal to the number of pegs to register EEMNFBMU.
Associated logs
None
EXT register
None

OM groups: E 3-35
ETEQRMMU
ETSI Equipment Management Dialogue Responder on the MMU 3
For a dialogue responder, ETEQRMMU measures the number of fall backs to
Registers
The following ETEQRMMU registers may be displayed:
EEMNRQMU EEMNRMU2 EEMNFBMU EEMNFMU2
Release history
ETEQRMMU was created in GSM11.
Group structure
ETSIEQR
Associated products
MMU
Validation Formula
Register EEMNRQMU 3
Number of fall backs from the various recommended EquipmentMngt(13)
context versions per MMU.

3-36 OM groups: E
Register EEMNRQMU is a peg register that records the number of fall backs
from the various recommended EquipmentMngt(13) context versions. Tuples
of this register represent versions.
EIR functionality is not supported.
Release history
Register EEMNRQMU was created in GSM11.
Associated register
EEMNFBMU
Validation formula
The number of pegs to register EEMNRQMU is greater than or equal to the
number of pegs to register EEMNFBMU.
Associated logs
None
EXT register
EEMNRMU2
Register EEMNFBMU 3
Number of fall backs to EquipmentMngt(13) context versions recommended
per MMU.
Register EEMNFBMU is a peg register that records the number of fall backs
to EquipmentMngt(13) context versions recommended.
By examining this register and EEMNRQMU, which records the number of

fall backs from the EquipmentMngt(13) context, the operator gets an
indication of the EquipmentMngt(13) context versions provisioned in the
network.
Release history
Register EEMNFBMU was created in GSM11.
Associated register
EEMNRQMU
Validation formula
The number of pegs to register EEMNFBMU is less than or equal to the
number of pegs to register EEMNRQMU.

OM groups: E 3-37
Associated logs
None
EXT register
EEMNFMU2

3-38 OM groups: E
ETFRIMMU
ETSI Fault Recovery Dialogue Initiator on the MMU 3
For a dialogue initiator, ETFRIMMU measures the number of fall backs to
and from the Fault Recovery related application context versions. The fields
Registers
ETFRIMMU registers may be displayed at the DMS MAP as follows:
EISTRQMU EISTRMU2 EISTFBMU EISTFMU2
Release history
ETFRIMMU was created in GSM11.
Group structure
ETSIFRI
Associated products
MMU
Validation Formula
Register EISTFBMU 3
Number of Fallbacks to Reset(10) Context per MMU.
Register EISTFBMU is a peg register that records the number of fallbacks to

the various Reset(10) context versions performed by the DMS-HLR. Tuples
of this register represent versions. By examining the tuples in this register and

OM groups: E 3-39
the tuples in EISTRQMU, which record the number of fall backs from the
Reset(10) context versions, the operator gets an indication of the Reset(10)
Release history
Register EISTFBMU was created in GSM11.
Associated register
EISTRQMU
Validation formula
On the DMS-HLR, the number of the number of pegs to register EISTFBMU
is less than or equal to the number of pegs to register EISTRQMU.
Associated logs
None
EXT register
EISTFMU2
Register EISTRQMU 3
Number of Fallbacks from Reset(10) Context per MMU.
Register EISTRQMU is a peg register that records the number of fall backs
from the various Reset(10) context versions performed by the DMS-HLR.
register and the tuples in EISTFBMU, which records the number of fall backs
to the Reset(10) context versions, the operator gets an indication of the
Reset(10) context versions provisioned in the network.
Release history
Register EISTRQMU was created in GSM11.
Associated register
EISTFBMU
Validation formula
On the DMS-HLR, the number of pegs to register EISTRQMU is greater than
or equal to the number of pegs to register EISTFBMU.
Associated logs
None
EXT register
EISTRMU2

3-40 OM groups: E

OM groups: E 3-41
ETFRRMMU
ETSI Fault Recovery Dialogue Responder on the MMU 3
For a dialogue responder, ETFRRMMU measures the number of fall backs to
and from the Fault Recovery related application context versions. The fields
Registers
The following ETFRRMMU registers may be displayed:
ERSTRQMU ERSTFBMU
Release history
ETFRRMMU was created in GSM11.
Group structure
ETSIFRR
Associated products
MMU
Validation Formula
Register ERSTRQMU 3
Number of fall backs from the various Reset(10) context per MMU.
Register ERSTRQMU is a peg register that records the number of fall backs
from the various Reset(10) context versions recommended by the DMS-
MSC/Call Server. Tuples of this register represent versions. By examining

3-42 OM groups: E
the tuples in this register and the tuples in ERSTFBMU, which records the
number of fall backs to the Reset(10) context versions, the operator gets an
indication of the Reset(10) context versions provisioned in the network.
Release history
Register ERSTRQMU was created in GSM11.
Associated register
ERSTFBMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ERSTRQMU
is greater than or equal to the number of pegs to register ERSTFBMU.
Associated logs
None
EXT register
None
Register ERSTFBMU 3
Number of fallbacks to the various Reset(10) context per MMU.
Register ERSTFBMU is a peg register that records the number of fallbacks to

the various Reset(10) context versions recommended by the DMS-MSC/Call
Server. Tuples of this register represent versions. By examining the tuples in
this register and the tuples in ERSTRQMU, which records the number of fall
backs from the Reset(10) context versions, the operator gets an indication of
the Reset(10) context versions provisioned in the network.
Release history
Register ERSTFBMU was created in GSM11.
Associated register
ERSTRQMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ERSTFBMU is
less than or equal to the number of pegs to register ERSTRQMU.
Associated logs
None
EXT register
None

OM groups: E 3-43

3-44 OM groups: E
ETMMIMMU
ETSI Mobility Management Dialogue Initiator on the MMU 3
For a dialogue initiator, ETMMIMMU measures the number of fall backs to
and from the Mobility Management related application context versions. The
fields represent the various application contexts, and the tuples represent the
Registers
The following ETMMIMMU registers may be displayed:
ETUPRQMU ETUPFBMU ETCLRQMU ETCLRMU2
ETCLFBMU ETCLFMU2
Release history
ETMMIMMU was created with GSM11.
Group structure
ETSIMMI
Associated products
MMU
Validation Formula
Register ETCLFBMU 3
Number of Fallbacks to LocationCancel(2) Context per MMU.

OM groups: E 3-45
Register ETCLFBMU is a peg register that records the number of fallbacks to

the various LocationCancellation(2) context versions performed by the?.

tuples in this register and the tuples in ETCLRQMU, which records the
number of fall backs from the LocationCancellation(2) context versions, the
operator gets an indication of the LocationCancellatio(2) context versions
Release history
Register ETCLFBMU was created in GSM11.
Associated register
ETCLRQMU
Validation formula
On the DMS-HLR, the number of the number of pegs to register
ETCLFBMU is less than or equal to the number of pegs to register
ETCLRQMU.
Associated logs
None
EXT register
ETCLFMU2
Register ETCLRQMU 3
Number of Fallbacks from the LocationCancel(2) Context per MMU.
Register ETCLRQMU is a peg register that records the number of fall backs
from the various LocationCancellation(2) context versions performed by the
tuples in this register and the tuples in ETCLFBMU, which records the
number of fall backs to the LocationCancellation(2) context versions, the
operator gets an indication of the LocationCancellation(1) context versions
Release history
Register ETCLRQMU was created in GSM11.
Associated register
ETCLFBMU

3-46 OM groups: E
Validation formula
On the DMS-HLR, the number of pegs to register ETCLRQMU is greater
than or equal to the number of pegs to register ETCLFBMU.
Associated logs
None
EXT register
ETCLRMU2
Register ETUPRQMU 3
Number of Fallbacks from NetworkLocUp(1) Context per MMU.
Register ETUPRQMU is a peg register that records the number of fall backs
from the various NetworkLocUp(1) context versions performed by the

examining the tuples in this register and the tuples in ETUPFBMU, which
records the number of fall backs to the NetworkLocUp(1) context versions,
the operator gets an indication of the NetworkLocUp(1) context versions
Release history
Register ETUPRQMU was created in GSM11.
Associated register
ETUPFBMU
GMULREQ and GMULRES from group GMAPMMGT.
RDREQ and GMRDRES from group GMAPFREC.
Validation formula
On the DMS-MSC/Call Server, the number of pegs to registers GMULREQ
from group GMAPMMGT and RDREQ from group GMAPFREC is greater
or equal to the sum of the number of pegs to registers GMULRES from group
GMAPMMGT, RDRES from group GMAPFREC, and ETUPRQMU.
On the DMS-MSC/Call Server, the number of pegs to register ETUPRQMU

is greater than or equal to the number of pegs to register ETUPFBMU.
Associated logs
None

OM groups: E 3-47
EXT register
None
Register ETUPFBMU 3
Number of Fallbacks to the NetworkLocUp(1) Context per MMU.
Register ETUPFBMU is a peg register that records the number of fallbacks to

the various NetworkLocUp(1) context versions performed by the DMS-MSC/
Call Server. Tuples of this register represent versions. By examining the
tuples in this register and the tuples in ETUPRQMU, which records the
number of fall backs from the NetworkLocUp(1) context versions, the
operator gets an indication of the NetworkLocUp(1) context versions
Release history
Register ETUPFBMU was created in GSM 11.
Associated register
ETUPRQMU
RDREQ and RDRES from group GMAPFREC.
Validation formula
GMAPMMGT, RDRES from group GMAPFREC, and ETUPFBMU.
On the DMS-MSC/Call Server, the number of pegs to register ETUPFBMU

is less than or equal to the number of pegs to register ETUPRQMU.
Associated logs
None
EXT register
None

3-48 OM groups: E
ETMMRMMU
ETSI Mobility Management Dialogue Responder on the MMU 3
For a dialogue responder, ETMMRMMU measures the number of fall backs
to and from the Mobility Management related application context versions.
Registers
The following ETMMRMMU registers may be displayed:
ELUPRQMU ELUPRMU2 ELUPFBMU ELUPFMU2
ELCLRQMU ELCLFBMU
Release history
ETMMRMMU was created in GSM11.
Group structure
ETSIMMR
Associated products
MMU
Validation Formula
Register ELCLFBMU 3
Number of Fallbacks to the LocationCancellation(2) Context per MMU.

OM groups: E 3-49
Register ELCLFBMU is a peg register that records the number of fallbacks to

the various LocationCancellation(2) context versions recommended by the
examining the tuples in this register and the tuples in ELCLRQMU, which
records the number of fall backs from the LocationCancellation(2) context
versions, the operator gets an indication of the LocationCancellation(2)
Release history
Register ELCLFBMU was created in GSM11.
Associated register
ELCLRQMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ELCLFBMU
is less than or equal to the number of pegs to register ELCLRQMU.
Associated logs
None
EXT register
None
Register ELCLRQMU 3
Number of Fallbacks from the LocationCancellation(2) Context per MMU.
Register ELCLRQMU is a peg register that records the number of fall backs
from the various LocationCancellation(2) context versions recommended by
examining the tuples in this register and the tuples in ELCLFBMU, which
record the number of fall backs to the LocationCancellation(2) context
Release history
Register ELCLRQMU was created in GSM11.
Associated register
ELCLFBMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ELCLRQMU
is greater than or equal to the number of pegs to register ELCLFBMU.

3-50 OM groups: E
Associated logs
None
EXT register
None
Register ELUPFBMU 3
Number of Fallbacks to the NetworkLocUp(1) Context per MMU.
Register ELUPFBMU is a peg register that records the number of fallbacks to

the various NetworkLocUp(1) context versions recommended by the DMS-
HLR. Tuples of this register represent versions. By examining the tuples in
this register and the tuples in ELUPRQMU, which records the number of fall
backs from the NetworkLocUp(1) context versions, the operator gets an
indication of the NetworkLocUp(1) context versions provisioned in the
network.
Release history
Register ELUPFBMU was created in GSM11.
Associated register
ELUPRQMU
Validation formula
On the DMS-HLR, the number of pegs to register ELUPFBMU is less than or
equal to the number of pegs to register ELUPRQMU.
Associated logs
None
EXT register
ELUPFMU2
Register ELUPRQMU 3
Number of Fallbacks from the NetworkLocUp(1) Context per MMU.
Register ELUPRQMU is a peg register that records the number of fall backs
from the various NetworkLocUp(1) context versions recommended by the
tuples in this register and the tuples in ELUPFBMU, which record the number
of fall backs to the NetworkLocUp(1) context versions, the operator gets an
network.

OM groups: E 3-51
Release history
Register ELUPRQMU was created in GSM11.
Associated register
ELUPFBMU
Validation formula
On the DMS-HLR, the number of pegs to register ELUPRQMU is greater
than or equal to the number of pegs to register ELUPFBMU.
Associated logs
None
EXT register
ELUPRMU2

3-52 OM groups: E
ETSICHI
ETSI Call Handling Dialogue Initiator 3
For a dialogue initiator, ETSICHI measures the number of fall backs to and
from the Call Handling related application context versions. The fields
Registers
The following ETSICHI registers may be displayed:
ETIRNERQ ETIRNER2 ETIRNEFB ETIRNEF2
ETILIRRQ ETILIRFB ETIHOCRQ ETIHOCFB
ETICCTRQ ETICCTFB
Release history
ETSICHI was created in GSM05.
Group structure
ETSICHI provides three tuples per DMS-MSC/Call Server.
Key field: GSM_MAP_AC_VERSION
VERSION1, VERSION2, VERSION2+
Info field: None
GMAPCH
Associated products
None
Validation Formula
Under operating conditions in which no application context version fall backs
occur, no registers are pegged.
The number of requests of an operation (given by the appropriate RQ and

RQ2 registers) is greater than or equal to the sum of the number of responses

OM groups: E 3-53
(given by the corresponding RES and RS2 registers) and number of dialogue
requests for the application context (given by the appropriate RQ and R2
fields and tuples).
The sum of the number of dialogue requests from a particular application

context (given by the appropriate RQ and R2 fields and tuples) is greater than
or equal to the sum of the number of dialogue fall backs to its alternative
application context (given by the appropriate FB and F2 fields and tuples).
Register ETICCTRQ 3
Number of Fallbacks from CallControlTransfer Context
Register ETICCTRQ is a peg register that records the number of fall backs
from the various CallControlTransfer context versions performed by the
examining the tuples in this register and the tuples in ETICCTFB, which
records the number of fall backs to the CallControlTransfer context versions,
the operator gets an indication of the CallControlTransfer context versions
Associated register
ETICCTFB
RCHREQ and RCHRES from group GMAPCH2
Validation formula
On the DMS-MSC/Call Server, the number of pegs to registers RCHREQ
from group GMAPCH2 is greater or equal to the sum of the number of pegs
to registers RCHRES from group GMAPCH2 and ETICCTRQ.
On the DMS-MSC/Call Server, the number of pegs to register ETICCTRQ is

greater than or equal to the number of pegs to register ETICCTFB.
Associated logs
None
EXT register
None
Register ETICCTFB 3
Register ETICCTFB is a peg register that records the number of fallbacks to
the various callControlTransfer context versions performed by the
examining the tuples in this register and the tuples in ETICCTRQ, which
records the number of fall backs from the callControlTransfer context

3-54 OM groups: E
versions, the operator gets an indication of the callControlTransfer context

Associated register
ETICCTRQ
RCHREQ and RCHRES from group GMAPCH2
Validation formula
On the DMS-MSC/Call Server, the number of pegs to registers RCHREQ
from group GMAPCH2 is greater than or equal to the sum of the number of
pegs to registers RCHRES from group GMAPCH2 and ETICCTFB.
On the DMS-MSC/Call Server, the number of pegs to register ETICCTFB is

less than or equal to the number of pegs to register ETICCTRQ.
Associated logs
None
EXT register
None
Register ETIHOCFB 3
Number of Fallbacks to HandoverControl(11) Context.
Register ETIHOCFB is a peg register that records the number of fallbacks to

the various HandoverControl(11) context versions performed by the?.

examining the tuples in this register and the tuples in ETIHOCRQ, which
records the number of fall backs from the HandoverControl(11) context
Associated register
ETIHOCRQ
Validation formula
registers GMPHORES from group GMAPCH and ETIHOCFB.
On the DMS-MSC/Call Server, the number of pegs to register ETIHOCFB is

less than or equal to the number of pegs to register ETIHOCRQ.

OM groups: E 3-55
Associated logs
None
EXT register
None
Register ETIHOCRQ 3
Number of Fallbacks from Handover Control(11) Context.
Register ETIHOCRQ is a peg register that records the number of fall backs
from the various HandoverControl(11) context versions performed by the
examining the tuples in this register and the tuples in ETIHOCFB, which
Associated register
ETIHOCFB
Validation formula
registers GMPHORES from group GMAPCH and ETIHOCRQ.
On the DMS-MSC/Call Server, the number of pegs to register ETIHOCRQ is

greater than or equal to the number of pegs to register ETIHOCFB.
Associated logs
None
EXT register
None
Register ETILIRFB 3
Register description
Register ETILIRPFB is a peg register that records the number of fallbacks to
the various LocationInfoRetrieval(5) context versions performed by the?.

examining the tuples in this register and the tuples in ETILIRRQ, which
records the number of fall backs from the LocationInfoRetrieval(5) context

3-56 OM groups: E

Associated register
ETILIRRQ
GMSRIREQ and GMSRIRES from group GMAPCH
Validation formula
pegs to registers GMSRIRES from group GMAPCH and ETILIRFB.
On the DMS-MSC/Call Server, the number of pegs to register ETILIRFB is

less than or equal to the number of pegs to register ETILIRRQ.
Associated logs
None
EXT register
None
Register ETILIRRQ 3
Number of Fallbacks from LocationInfoRetrieval(5) Context.
Register ETILIRRQ is a peg register that records the number of fall backs
from the various LocationInfoRetrieval(5) context versions performed by the
examining the tuples in this register and the tuples in ETILIRFB, which
record the number of fall backs to the LocationInfoRetrieval(5) context
Associated register
ETILIRFB
Validation formula
pegs to registers GMSRIRES from group GMAPCH and ETILIRRQ.
On the DMS-MSC/Call Server, the number of pegs to register ETILIRRQ is

greater than or equal to the number of pegs to register ETILIRFB.

OM groups: E 3-57
Associated logs
None
EXT register
None
Register ETIRNEFB 3
Number of Fallbacks to RoamingNumberEnquiry(3) Context.
ETIRNEFB records the number of fallbacks to the various

RoamingNumberEnquiry(3) context versions performed by the DMS-HLR.
register and the tuples in ETIRNERQ, which records the number of fall backs
from the RoamingNumberEnquiry(3) context versions, the operator gets an
indication of the RoamingNumberEnquiry(3) context versions provisioned in
the network.
Associated register
ETIRNERQ
Validation formula
On the DMS-HLR, the number of pegs to register ETILUPFB is less than or
equal to the number of pegs to register ETILUPRQ.
Associated logs
None
EXT register
ETIRNEF2
Register ETIRNERQ 3
Number of Fallbacks from RoamingNumberEnquiry(3) Context.
Register ETIRNERQ is a peg register that records the number of fall backs
from the various RoamingNumberEnquiry(3) context versions performed by
tuples in this register and the tuples in ETIRNEFB, which record the number
of fall backs to the RoamingNumberEnquiry(3) context versions, the operator
gets an indication of the RoamingNumberEnquiry(3) context versions
Associated register
ETIRNEFB

3-58 OM groups: E
Validation formula
On the DMS-HLR, the number of pegs to register ETIRNERQ is greater than
or equal to the number of pegs to register ETIRNEFB.
Associated logs
None
EXT register
ETIRNER2

OM groups: E 3-59
ETSICHR
ETSI Call Handling Dialogue Responder 3
For a dialogue responder, ETSICHR measures the number of fall backs to and
from the Call Handling related application context versions. The fields
Registers
The following ETSICHR registers may be displayed:
ETRRNERQ ETRRNEFB ETRLIRRQ ETRLIRR2
ETRLIRFB ETRLIRF2 ETRHOCRQ ETRHOCFB
Release history
ETSICHR was created in GSM05.
Group structure
ETSICHR provides three tuples per DMS-MSC/Call Server.
Key field: GSM_MAP_AC_VERSION,
Info field: None
None
Associated products
None
Validation Formula
The sum of the number of dialogue requests for a particular application

or equal to the sum of the number of dialogue fall backs recommended its

3-60 OM groups: E
alternative application context (given by the appropriate FB and F2 fields and

tuples).
Register ETRRNERQ 3
Number of fall backs from the various RoamingNumberEnquiry(3) context
versions.
Register ETRRNERQ is a peg register that records the number of fall backs
from the various RoamingNumberEnquiry(3) context versions recommended
by the DMS-MSC/Call Server. Tuples of this register represent versions. By
examining the tuples in this register and the tuples in ETRFNEFB, which
records the number of fall backs to the RoamingNumberEnquiry(3) context
versions, the operator gets an indication of the RoamingNumberEnquiry(3)
Associated register
ETRRNEFB
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRRNERQ is
greater than or equal to the number of pegs to register ETRRNEFB.
Associated logs
None
EXT register
None
Register ETRRNEFB 3
Number of fallbacks to the various RoamingNumberEnquiry(3) context
versions.
Register ETRRNEFB is a peg register that records the number of fallbacks to

the various RoamingNumberEnquiry(3) context versions recommended by
examining the tuples in this register and the tuples in ETRRNERQ, which
records the number of fall backs from the RoamingNumberEnquiry(3)
context versions, the operator gets an indication of the
RoamingNumberEnquiry(3) context versions provisioned in the network.
Associated register
ETRRNERQ

OM groups: E 3-61
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRRNEFB is
less than or equal to the number of pegs to register ETRRNERQ.
Associated logs
None
EXT register
None
Register ETRLIRRQ 3
Number of fall backs from the various LocationInfoRetrieval(5) context
versions.
Register ETRLIRRQ is a peg register that records the number of fall backs
from the various LocationInfoRetrieval(5) context versions recommended by
tuples in this register and the tuples in ETRLIRFB, which records the number
of fall backs to the LocationInfoRetrieval(5) context versions, the operator
gets an indication of the LocationInfoRetrieval(5) context versions
Associated register
ETRLIRFB
Validation formula
On the DMS-HLR, the number of pegs to register ETRLIRRQ is greater than
or equal to the number of pegs to register ETRLIRFB.
Associated logs
None
EXT register
ETRLIRR2
Register ETRLIRFB 3
Number of fallbacks to the various LocationInfoRetrieval(5) context
versions.
Register ETRLIRFB is a peg register that records the number of fallbacks to

the various LocationInfoRetrieval(5) context versions recommended by the
tuples in this register and the tuples in ETRLIRRQ, which records the number
of fall backs from the LocationInfoRetrieval(5) context versions, the operator

3-62 OM groups: E
gets an indication of the LocationInfoRetrieval(5) context versions

Associated register
ETRLIRRQ
Validation formula
On the DMS-HLR, the number of pegs to register ETRLIRFB is less than or
equal to the number of pegs to register ETRLIRRQ.
Associated logs
None
EXT register
ETRLIRF2
Register ETRHOCRQ
Number of fall backs from the various HandoverControl(11) context versions
Register ETRHOCRQ is a peg register that records the number of fall backs
from the various HandoverControl(11) context versions recommended by the
examining the tuples in this register and the tuples in ETRHOCFB, which
Associated register
ETRHOCFB
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRHOCRQ
is greater than or equal to the number of pegs to register ETRHOCFB.
Associated logs
None
EXT register
None
Register ETRHOCFB 3
Number of fallbacks to the various HandoverControl(11) context versions.
Register ETRHOCFB is a peg register that records the number of fallbacks to

the various HandoverControl(11) context versions recommended by the

OM groups: E 3-63

examining the tuples in this register and the tuples in ETRHOCRQ, which
record the number of fall backs from the HandoverControl(11) context
Associated register
ETRHOCRQ
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRHOCFB is
less than or equal to the number of pegs to register ETRHOCRQ.
Associated logs
None
EXT register
None

3-64 OM groups: E

OM groups: E 3-65
ETSIEQI
ETSI Equipment Management Dialogue Initiator 3
For a dialogue initiator, ETSIEQI measures the number of fall backs to and
from the Equipment Management related application context versions. The
Registers
The following ETSIEQI registers may be displayed:
ETIEMNRQ ETIEMNFB
Release history
ETSIEQI was created in GSM05.
Group structure
ETSIEQI provides three tuples per DMS-MSC/Call Server.
Info field: None
Application context negotiation is considered a failure. Therefore, RES and
RS2 MAP registers (provided by GSM MAP Robustness) associated with the
given application context are not pegged. However, the number of pegs for
the RQ and R2 fields and tuples of the appropriate application context do
account for part of the discrepancy between the REQ and RES registers.
Associated products
None
Validation Formula

3-66 OM groups: E

fields and tuples).

Register ETIEMNFB 3
Number of Fallbacks to EquipmentMngt(13) Context.
Register ETIEMNFB is a peg register that records the number of fallbacks to

the various EquipmentMngt(13) context versions performed by the DMS-
the tuples in this register and the tuples in ETIEMNRQ, which record the
number of fall backs from the EquipmentMngt(13) context versions, the
operator gets an indication of the EquipmentMngt(13) context versions
Associated register
ETIEMNRQ
Validation formula
from group GMAPEMGT is greater than or equal to the sum of the number of
pegs to registers GMCIMRES from group GMAPEMGT and ETIEMNFB.
On the DMS-MSC/Call Server, the number of pegs to register ETIEMNFB is

less than or equal to the number of pegs to register ETIEMNRQ.
Associated logs
None
EXT register
None
Register ETIEMNRQ 3
Number of Fallbacks from EquipmentMngt(13) Context.
Register ETIEMNRQ is a peg register that records the number of fall backs
from the various EquipmentMngt(13) context versions performed by the

OM groups: E 3-67

examining the tuples in this register and the tuples in ETIEMNFB, which
record the number of fall backs to the EquipmentMngt(13) context versions,
the operator gets an indication of the EquipmentMngt(13) context versions
Associated register
ETIEMNFB
Validation formula
from group GMAPEMGT is greater or equal to the sum of the number of
pegs to registers GMCIMRES from group GMAPEMGT and ETIEMNRQ.
On the DMS-MSC/Call Server, the number of pegs to register ETIEMNRQ is

greater than or equal to the number of pegs to register ETIEMNFB.
Associated logs
None
EXT register
None

3-68 OM groups: E
ETSIEQR
ETSI Equipment Management Dialogue Responder 3
For a dialogue responder, ETSIEQR measures the number of fall backs to
Registers
The following ETSIEQR registers may be displayed:
ETREMNRQ ETREMNR2 ETREMNFB ETREMNF2
Release history
ETSIEQR was created in GSM05.
Group structure
ETSIEQR provides three tuples per DMS-MSC/Call Server.
Info field: None
None
Associated products
None
Validation Formula

tuples).

OM groups: E 3-69
Register ETREMNRQ 3
Register ETREMNRQ is a peg register that records the number of fall backs
from the various recommended EquipmentMngt(13) context versions. Tuples
of this register represent versions.
Associated register
ETREMNFB
Validation formula
The number of pegs to register ETREMNRQ is greater than or equal to the
number of pegs to register ETREMNFB.
Associated logs
None
EXT register
ETREMNR2
Register ETREMNFB 3
Register ETREMNFB is a peg register that records the number of fall backs
to EquipmentMngt(13) context versions recommended.
By examining this register and ETREMNRQ, which records the number of

fall backs from the EquipmentMngt(13) context, the operator gets an
indication of the EquipmentMngt(13) context versions provisioned in the
network.
Associated register
ETREMNRQ
Validation formula
The number of pegs to register ETREMNFB is less than or equal to the
number of pegs to register ETREMNRQ.
Associated logs
None
EXT register
ETREMNF2

3-70 OM groups: E

OM groups: E 3-71
ETSIFRI
ETSI Fault Recovery Dialogue Initiator 3
For a dialogue initiator, ETSIFRI measures the number of fall backs to and
from the Fault Recovery related application context versions. The fields
Registers
ETSIFRI registers may be displayed at the DMS MAP as follows:
ETIRSTRQ ETIRSTR2 ETIRSTFB ETIRSTF2
Release history
ETSIFRI was created in GSM05.
Group structure
ETSIFRI provides three tuples per DMS-MSC/Call Server.
Info field: None
GMAPFREC

Associated products
None
Validation Formula

3-72 OM groups: E

(given by the corresponding RES and RS2 registers.) and number of dialogue
fields and tuples).

Register ETIRSTFB 3
Number of Fallbacks to Reset(10) Context.
Register ETIRSTFB is a peg register that records the number of fallbacks to

the various Reset(10) context versions performed by the DMS-HLR. Tuples
of this register represent versions. By examining the tuples in this register and
the tuples in ETIRSTRQ, which record the number of fall backs from the
Reset(10) context versions, the operator gets an indication of the Reset(10)
Associated register
ETIRSTRQ
Validation formula
On the DMS-HLR, the number of the number of pegs to register ETIRSTFB
is less than or equal to the number of pegs to register ETIRSTRQ.
Associated logs
None
EXT register
ETIRSTF2
Register ETIRSTRQ 3
Number of Fallbacks from Reset(10) Context.
Register ETIRSTRQ is a peg register that records the number of fall backs
from the various Reset(10) context versions performed by the DMS-HLR.
register and the tuples in ETIRSTFB, which records the number of fall backs
to the Reset(10) context versions, the operator gets an indication of the
Reset(10) context versions provisioned in the network.

OM groups: E 3-73
Associated register
ETIRSTFB
Validation formula
On the DMS-HLR, the number of pegs to register ETIRSTRQ is greater than
or equal to the number of pegs to register ETIRSTFB.
Associated logs
None
EXT register
ETIRSTR2

3-74 OM groups: E
ETSIFRR
ETSI Fault Recovery Dialogue Responder 3
For a dialogue responder, ETSIFRR measures the number of fall backs to and
from the Fault Recovery related application context versions. The fields
Registers
The following ETSIFRR registers may be displayed:
ETRRSTRQ ETRRSTFB
Release history
ETSIFRR was created in GSM05.
Group structure
ETSIFRR provides one tuple per DMS-MSC/Call Server.
Info field: None
None
Associated products
None
Validation Formula

tuples).

OM groups: E 3-75
Register ETRRSTRQ 3
Register ETRRSTRQ is a peg register that records the number of fall backs
from the various Reset(10) context versions recommended by the DMS-
the tuples in this register and the tuples in ETRRSTFB, which records the
number of fall backs to the Reset(10) context versions, the operator gets an
indication of the Reset(10) context versions provisioned in the network.
Associated register
ETRRSTFB
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRRSTRQ is
greater than or equal to the number of pegs to register ETRRSTFB.
Associated logs
None
EXT register
None
Register ETRRSTFB 3
Register ETRRSTFB is a peg register that records the number of fallbacks to
the various Reset(10) context versions recommended by the DMS-MSC/Call
Server. Tuples of this register represent versions. By examining the tuples in
this register and the tuples in ETRRSTRQ, which records the number of fall
backs from the Reset(10) context versions, the operator gets an indication of
the Reset(10) context versions provisioned in the network.
Associated register
ETRRSTRQ
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRRSTFB is
less than or equal to the number of pegs to register ETRRSTRQ.
Associated logs
None
EXT register
None

3-76 OM groups: E

OM groups: E 3-77
ETSIIMMU
ETSI Subscriber Info Initiator AC OMs on MMUs 3
Each MMU is datafilled in Table C7SERVER as an MMU application server.
MMUs are applications of the C7SERVER.
Registers
The following ETSISII register may be displayed:
EISERQMU EISERMU2 EISEFBMU EISEFMU2
Release history
ETSIIMMU was created in GSM11.
Group structure
ETSISII
Associated products
MMU
Validation Formula
• The sum of peg counts in the register for all available MMUs is always

3-78 OM groups: E
Register EISERQMU 3
Number of fall backs from Subscriber info enquiry(28) context versions
per MMU
Register EISERQMU is a peg register that records the number of fall backs
from the Subscriber info enquiry(28) context per MMU.
Release history
Register EISERQMU was created in GSM11.
Associated register
EISEFBMU
Validation formula
None
Associated logs
None
Extension register
EISERMU2
Register EISEFBMU 3
Number of fall backs from Subscriber info enquiry(28) context versions
recommended per MMU
Register EISEFBMU is a peg register that records the number of fall backs
from the Subscriber info enquiry(28) context per MMU.
Release history
Register EISEFBMU was created in GSM11.
Associated register
EISERQMU
Validation formula
None
Associated logs
None
Extension registers
EISEFMU2

OM groups: E 3-79
ETSIMMI
ETSI Mobility Management Dialogue Initiator 3
For a dialogue initiator, ETSIMMI measures the number of fall backs to and
from the Mobility Management related application context versions. The
Registers
The following ETSIMMI registers may be displayed:
ETILUPRQ ETILUPFB ETILCLRQ ETILCLR2
ETILCLFB ETILCLF2
Release history
ETSIMMI was created with GSM05.
Group structure
ETSIMMI provides three tuples per DMS-MSC/Call Server.
Key field: GSM_MAP_AC_VERSION.
Info field: None
GMAPMMGT

Associated products
None

3-80 OM groups: E
Validation Formula

RQ2 registers.) is greater than or equal to the sum of the number of responses
fields and tuples).

Register ETILCLFB 3
Number of Fallbacks to LocationCancel(2) Context.
Register ETILCLFB is a peg register that records the number of fallbacks to

the various LocationCancellation(2) context versions performed by the?.

tuples in this register and the tuples in ETILCLRQ, which records the number
of fall backs from the LocationCancellation(2) context versions, the operator
gets an indication of the LocationCancellatio(2) context versions provisioned
in the network.
Associated register
ETILCLRQ
Validation formula
On the DMS-HLR, the number of the number of pegs to register ETILCLFB
is less than or equal to the number of pegs to register ETILCLRQ.
Associated logs
None
EXT register
ETILCLF2
Register ETILCLRQ 3
Number of Fallbacks from the LocationCancel(2) Context.
Register ETILCLRQ is a peg register that records the number of fall backs
from the various LocationCancellation(2) context versions performed by the

OM groups: E 3-81

tuples in this register and the tuples in ETILCLFB, which records the number
of fall backs to the LocationCancellation(2) context versions, the operator
gets an indication of the LocationCancellation(1) context versions
Associated register
ETILCLFB
Validation formula
On the DMS-HLR, the number of pegs to register ETILCLRQ is greater than
or equal to the number of pegs to register ETILCLFB.
Associated logs
None
EXT register
ETILCLR2
Register ETILUPRQ 3
Number of Fallbacks from NetworkLocUp(1) Context.
Register ETILUPRQ is a peg register that records the number of fall backs
from the various NetworkLocUp(1) context versions performed by the DMS-
the tuples in this register and the tuples in ETILUPFB, which records the
number of fall backs to the NetworkLocUp(1) context versions, the operator
gets an indication of the NetworkLocUp(1) context versions provisioned in
the network.
Associated register
ETILUPFB
RDREQ and GMRDRES from group GMAPFREC.
Validation formula
GMAPMMGT, RDRES from group GMAPFREC, and ETILUPRQ.
On the DMS-MSC/Call Server, the number of pegs to register ETILUPRQ is

greater than or equal to the number of pegs to register ETILUPFB.

3-82 OM groups: E
Associated logs
None
EXT register
None
Register ETILUPFB 3
Number of Fallbacks to the NetworkLocUp(1) Context.
Register ETILUPFB is a peg register that records the number of fallbacks to

the various NetworkLocUp(1) context versions performed by the DMS-MSC/
tuples in this register and the tuples in ETILUPRQ, which records the number
of fall backs from the NetworkLocUp(1) context versions, the operator gets
an indication of the NetworkLocUp(1) context versions provisioned in the
network.
Associated register
ETILUPRQ
RDREQ and RDRES from group GMAPFREC.
Validation formula
GMAPMMGT, RDRES from group GMAPFREC, and ETILUPFB.
On the DMS-MSC/Call Server, the number of pegs to register ETILUPFB is

less than or equal to the number of pegs to register ETILUPRQ.
Associated logs
None
EXT register
None

OM groups: E 3-83
ETSIMMR
ETSI Mobility Management Dialogue Responder 3
For a dialogue responder, ETSIMMR measures the number of fall backs to
and from the Mobility Management related application context versions. The
Registers
The following ETSIMMR registers may be displayed:
ETRLUPRQ ETRLUPR2 ETRLUPFB ETRLUPF2
ETRLCLRQ ETRLCLFB
Release history
ETSIMMR was created in GSM05.
Group structure
ETSIMMR provides three tuples per DMS-MSC/Call Server.
Info field: None
None
Associated products
None
Validation Formula


3-84 OM groups: E

tuples).
Register ETRLCLFB 3
Number of Fallbacks from the LocationCancellation(2) Context.
Register ETRLCLFB is a peg register that records the number of fallbacks to

the various LocationCancellation(2) context versions recommended by the
examining the tuples in this register and the tuples in ETRLCLRQ, which
records the number of fall backs from the LocationCancellation(2) context
Associated register
ETRLCLRQ
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRLCLFB is
less than or equal to the number of pegs to register ETRLCLRQ.
Associated logs
None
EXT register
None
Register ETRLCLRQ 3
Number of Fallbacks from the LocationCancellation(2) Context.
Register ETRLCLRQ is a peg register that records the number of fall backs
from the various LocationCancellation(2) context versions recommended by
examining the tuples in this register and the tuples in ETRLCLFB, which
record the number of fall backs to the LocationCancellation(2) context
Associated register
ETRLCLFB
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRLCLRQ is
greater than or equal to the number of pegs to register ETRLCLFB.

OM groups: E 3-85
Associated logs
None
EXT register
None
Register ETRLUPFB 3
Number of Fallbacks to the NetworkLocUp(1) Context.
Register ETRLUPFB is a peg register that records the number of fallbacks to

the various NetworkLocUp(1) context versions recommended by the DMS-
this register and the tuples in ETRLUPRQ, which records the number of fall
backs from the NetworkLocUp(1) context versions, the operator gets an
network.
Associated register
ETRLUPRQ
Validation formula
On the DMS-HLR, the number of pegs to register ETRLUPFB is less than or
equal to the number of pegs to register ETRLUPRQ.
Associated logs
None
EXT register
ETRLUPF2
Register ETRLUPRQ 3
Number of Fallbacks from the NetworkLocUp(1) Context.
Register ETRLUPRQ is a peg register that records the number of fall backs
from the various NetworkLocUp(1) context versions recommended by the
tuples in this register and the tuples in ETRLUPFB, which record the number
of fall backs to the NetworkLocUp(1) context versions, the operator gets an
network.
Associated register
ETRLUPFB

3-86 OM groups: E
Validation formula
On the DMS-HLR, the number of pegs to register ETRLUPRQ is greater than
or equal to the number of pegs to register ETRLUPFB.
Associated logs
None
EXT register
ETRLUPR2

OM groups: E 3-87
ETSIRMMU
ETSI Subscriber Information Dialogue Responder on the MMU 3
For a dialogue responder, ETSIRMMU measures the number of fall backs
from the Subscriber Information related application context versions and the
number of fall backs to the Subscriber Information related application context
versions. The fields represent the various application contexts, and the tuples
represent the application context versions.
The fall back to either version 2 or version 1 should not occur. However, for
the completeness and since it is a new supported Application Context, this
ETSIRMMU OM group has to be implemented.
Registers
The following ETSIRMMU registers may be displayed:
ESIERQMU ESIERMU2 ESIEFBMU ESIEFMU2
Release history
ETSIRMMU was created in GSM11.
Group structure
ETSIRMMU provides four tuples per DMS-MSC/Call Server.
Info field: None
ETSISIR
Associated products
MMU
Validation Formula
Register ESIERQMU 3
Number of Fallbacks from InfoRetrieval (14) context per MMU.

3-88 OM groups: E
Register ESIERQMU records the number of fall backs from the various
SubscriberInfoEnquiry(28) context versions recommended by the DMS-
the tuples in this register and the tuples in ESIEFBMU, which record the
number of fall backs to the SubscriberInfoEnquiry(28) context versions, the
operator gets an indication of the SubscriberInfoEnquiry(28) context versions
Release history
Register ESIERQMU was created in GSM11.
Associated register
ESIEFBMU
Validation formula
Provide a mathematical formula which describes the relationship of this
register to the associated registers listed above or other registers in the same
group.
On the DMS-MSC/Call Server, the number of pegs to register ESIERQMU is

greater than or equal to the number of pegs to register ESIEFBMU.
Associated logs
None
Extension register
If there is an extension register, list it here.
ESIERMU2
Register ESIEFBMU 3
Number of Fallbacks to the InfoRetrieval(14) Context per MMU.
Register ESIEFBMU records the number of fallbacks to the various

the tuples in this register and the tuples in ESIERQMU, which records the
number of fall backs from the SubscriberInfoEnquiry(28) context versions,
the operator gets an indication of the SubscriberInfoEnquiry(28) context
Release history
Register ESIEFBMU was created in GSM11.
Associated register
ESIERQMU

OM groups: E 3-89
Validation formula
group.
On the DMS-MSC/Call Server, the number of pegs to register ESIEFBMU is

less than or equal to the number of pegs to register ESIERQMU.
Associated logs
None
Extension register
ESIEFMU2

3-90 OM groups: E
ETSISIR
ETSI Subscriber Information Dialogue Responder 3
For a dialogue responder, ETSISIR measures the number of fall backs from
the Subscriber Information related application context versions and the
number of fall backs to the Subscriber Information related application context
versions. The fields represent the various application contexts, and the tuples
represent the application context versions.
The fall back to either version 2 or version 1 should not occur. However, for
the completeness and since it is a new supported Application Context, this
ETSISIR OM group has to be implemented.
Registers
The following ETSISIR registers may be displayed:
ETRSIERQ ETRSIER2 ETRSIEFB ETRSIEF2
Release history
ETSISIR was created in GSM09.
Group structure
ETSISIR provides four tuples per DMS-MSC/Call Server.
Info field: None
None
Associated products
None
Validation Formula

context (given by the appropriate RQ fields and tuples) is greater than or
equal to the sum of the number of dialogue fall backs recommended its

OM groups: E 3-91
alternative application context (given by the appropriate FB fields and

tuples).
Register ETRSIERQ 3
Number of Fallbacks from Subscriber Info Enquiry(28)context.
ETRSIERQ records the number of fall backs from the various

the tuples in this register and the tuples in ETRSIEFB, which record the
number of fall backs to the SubscriberInfoEnquiry(28) context versions, the
operator gets an indication of the SubscriberInfoEnquiry(28) context versions
Associated register
ETRSIEFB
Validation formula
group.
On the DMS-MSC/Call Server, the number of pegs to register ETRSIERQ is

greater than or equal to the number of pegs to register ETRSIEFB.
Associated logs
None
Extension register
If there is an extension register, list it here.
ETRSIER2
Register ETRSIEFB 3
Number of Fallbacks from InfoRetrieval(14) Context.
Describe what the OM register measures. Describe what the OM register is

used for. If OTHER, clearly state what the unit of measure is. If a USAGE
register, provide the scan rate (10/100 sec).

ETRSIEFB records the number of fallbacks to the various


3-92 OM groups: E

the tuples in this register and the tuples in ETRSIERQ, which records the
number of fall backs from the SubscriberInfoEnquiry(28) context versions,
the operator gets an indication of the SubscriberInfoEnquiry(28) context
Associated register
ETRSIERQ
Validation formula
group.
On the DMS-MSC/Call Server, the number of pegs to register ETRSIEFB is

less than or equal to the number of pegs to register ETRSIERQ.
Associated logs
None
Extension register
ETRSIEF2

OM groups: E 3-93
ETSISMGI
ETSI Subscriber Management Dialogue Initiator 3
For a dialogue initiator, ETSISMGI measures the number of fall backs to and
from the Subscriber Management related application context versions. The
Registers
The following ETSISMGI registers may be displayed:
ETIIRTRQ ETIIRTR2 ETIIRTFB ETIIRTF2
ETIIVRRQ ETIIVRFB ETISMDRQ ETISDMR2
ETISDMFB ETISDMF2 ETITRCRQ ETITRCR2
ETITRCFB ETITRCF2 ETIPRGRQ ETIPRGFB
Release history
ETSISMGI was created in GSM05.
Group structure
ETSISMGT provides three tuples per DMS-MSC/Call Server.
Info field: None
GMAPSMGT


3-94 OM groups: E
Associated products
None
Validation Formula

fields and tuples).

Register ETIIRTFB 3
Number of Fallbacks to InfoRetrieval(14) Context.
Register ETIITRFB is a peg register that records the number of fall backs to
the various InfoRetrieval(14) context versions performed by the DMS-MSC/
Call Server. Note that InfoRetrieval(14) version1(1) is the fall back for
InterVlrInfoRetrieval(15) version2(2).
By examining tuples in this register, the version2 tuple in ETIIVRRQ, and

tuples in ETIITRRQ, the operator gets an indication of the InfoRetrieval(14)
Associated register
ETIIRTRQ, ETIIVRRQ, ETIIVRR2
SAIREQ and SAIRES in group GMAPSMGT
Validation formula
On the DMS-MSC/Call Server, the number of pegs to SAIREQ from group
GMAPSMGT is greater or equal to the sum of the number of pegs to SAIRES
from group GMAPSMGT and ETIIRTFB.
On the DMS-MSC/Call Server, there is no definite relationship between the

number of pegs to register ETIIRTRQ and the number of pegs to register
ETIIRTFB because Inter-Vlr Information Retrieval context may fall back to
Information Retrieval context.

OM groups: E 3-95
Associated logs
None
EXT register
ETIIRTF2
Register ETIIRTRQ 3
Number of Fallbacks from InfoRetrieval(14) Context.
Register ETIIRTRQ is a peg register that records the number of fall backs
from the various InfoRetrieval(14) context versions performed by the DMS-
the tuples in this register and the tuples in ETIIRTFB, which records the
number of fall backs to the InfoRetrieval(14) context versions, the operator
gets an indication of the InfoRetrieval(14) context versions provisioned in the
network.
Associated register
ETIIRTFB
SAIREQ and SAIRES in group GMAPSMGT
Validation formula
On the DMS-MSC/Call Server, the number of pegs to SAIREQ in group
GMAPSMGT is greater than or equal to the sum of the number of pegs to
SAIRES from group GMAPSMGT and ETIIRTRQ.

ETIIRTFB because Inter-VLR Information Retrieval context may fall back to
Associated logs
None
EXT register
ETIIRTR2
Register ETIIVRFB 3
Number of Fallbacks to InterVlrInfoRetrieval(15) Context.
Register ETIIVRFB is a peg register that records the number of fall backs to
the various InterVlrInfoRetrieval(15) context versions performed by the
examining the tuples in this register and the tuples in ETIIVRRQ, which

3-96 OM groups: E
records the number of fall backs from the InterVlrInfoRetrieval(15) context

versions, the operator gets an indication of the InterVlrInfoRetrieval(15)
Associated register
None
Validation formula
The Inter-Vlr Information Retrieval context is not supported for GSM05;
therefore the validation formula is not applicable.
If this context were supported, then the number of pegs to the Send
Identification request register in group GMAPSMGT would be greater than
or equal to the sum of the number of pegs to the Send Identification result
register in group GMAPSMGT and ETIIVRFB.
If this context were supported, then the number of pegs to ETIIVRFB will be
less than or equal to the number of pegs to ETIIVRRQ.
Associated logs
None
EXT register
None
Register ETIIVRRQ 3
Number of Fallbacks from InterVlrInfoRetrieval(15) Context.
Register ETIIVRRQ is a peg register that records the number of fall backs
from the various InterVlrInfoRetrieval(15) context versions performed by the
DMS-MSC/Call Server. Note that the fall back for InterVlrInfoRetrieval(15)
version2(2) is InfoRetrieval(14) version1(1).
By examining tuples in this register, tuples in ETIIVRFB, and the version1

tuple in ETIIRTFB, the operator gets an indication of the
InterVlrInfoRetrieval(15) and InfoRetrieval(14) context versions provisioned
in the network.
Associated register
ETIIVRFB, ETIIRTFB
Validation formula
therefore, the validation formula is not applicable.

OM groups: E 3-97
register in group GMAPSMGT and ETIIVRRQ.
If this context were supported, then the number of pegs to ETIIVRRQ would
be greater than or equal to the number of pegs to ETIIVRFB.
Associated logs
None
EXT register
None
Register ETIPRGFB 3
Number of Fallbacks to MsPurging(27) Context.
Register ETIPRGFB is a peg register that records the number of fallbacks to

the various MsPurging(27) context versions performed by the DMS-MSC/
tuples in this register and the tuples in ETIPRGRQ, which records the number
of fall backs from the MsPurging(27) context versions, the operator gets an
indication of the MsPurging(27) context versions provisioned in the network.
Associated register
None
Validation formula
The MsPurging context is not supported for GSM05; therefore, the validation
formula is not applicable.
If this context were supported, then the number of pegs to the PurgeMS
request register in group GMAPSMGT will be greater than or equal to the
sum of the number of pegs to the Send Identification result register in group
GMAPSMGT and ETIPRGFB.
If this context were supported, then the number of pegs to ETIPRGFB would
be less than or equal to the number of pegs to ETIPRGRQ.
Associated logs
None
EXT register
None

3-98 OM groups: E
Register ETIPRGRQ 3
Number of Fallbacks from MsPurging(27) Context.
Register ETIPRGRQ is a peg register that records the number of fall backs
from the various MsPurging(27) context versions performed by the DMS-
the tuples in this register and the tuples in ETIPRGFB, which record the
number of fall backs to the MsPurging(27) context versions, the operator gets
an indication of the MsPurging(27) context versions provisioned in the
network.
Associated register
ETIPRGFB
Validation formula
request register in group GMAPSMGT would be greater than or equal to the
sum of the number of pegs to the PurgeMS result register in group
GMAPSMGT and ETIPRGRQ.
If this context were supported, then the number of pegs to ETIPRGRQ would
be greater than or equal to the number of pegs to ETIPRGFB.
Associated logs
None
EXT register
None
Register ETISDMFB 3
Number of Fallbacks to SubscriberDataMngt(16) Context.
Register ETISDMFB is a peg register that records the number of fallbacks to

the various Subscriber DataMngt(16) context versions performed by the
tuples in this register and the tuples in ETISMDRQ, which records the
number of fall backs from the SubscriberDataMngt(16) context versions, the
operator gets an indication of the SubscriberDataMngt(16) context versions
Associated register
ETISMDRQ

OM groups: E 3-99
Validation formula
On the DMS-HLR, the number of pegs to register ETISDMFB is less than or
equal to the number of pegs to register ETISMDRQ.
Associated logs
None
EXT register
ETISDMF2
Register ETISMDRQ 3
Number of Fallbacks from SubscriberDataMngt(16) Context.
Register ETISMDRQ is a peg register that records the number of fall backs
from the various SubscriberDataMngt(16) context versions performed by the
tuples in this register and the tuples in ETISDMFB, which records the number
of fall backs to the SubscriberDataMngt(16) context versions, the operator
gets an indication of the SubscriberDataMngt(16) context versions
Associated register
ETISDMFB
Validation formula
On the DMS-HLR, the number of pegs to register ETISMDRQ is greater than
or equal to the number of pegs to register ETISDMFB.
Associated logs
None
EXT register
ETISDMR2
Register ETITRCFB 3
Number of Fallbacks to Tracing(17) Context.
Register ETITRCFB is a peg register that records the number of fallbacks to

the various Tracing(17) context versions performed by the DMS-HLR.
register and the tuples in ETITRCRQ, which records the number of fall backs
from the Tracing(17) context versions, the operator gets an indication of the
Tracing(17) context versions provisioned in the network.

3-100 OM groups: E
Associated register
ETITRCRQ
Validation formula
On the DMS-HLR, the number of the number of pegs to register ETITRCFB
is less than or equal to the number of pegs to register ETITRCRQ.
Associated logs
None
EXT register
ETITRCF2
Register ETITRCRQ 3
Number of Fallbacks from Tracing(17) Context.
Register ETITRCRQ is a peg register that records the number of fall backs
from the various Tracing(17) context versions performed by the DMS-HLR.
register and the tuples in ETITRCFB, which record the number of fall backs
to the Tracing(17) context versions, the operator gets an indication of the
Associated register
ETITRCFB
Validation formula
On the DMS-HLR, the number of pegs to register ETITRCRQ is greater than
or equal to the number of pegs to register ETITRCFB.
Associated logs
None
EXT register
ETITRCR2

OM groups: E 3-101
ETSISMGR
ETSI Subscriber Management Dialogue Responder 3
The GSM Mobile Application Part Subscriber Management group contains
the registers for operations handling subscriber data such as Insert Subscriber
Data, Delete Subscriber Data, and Send Parameters.
Registers
The following ETSISMGR registers may be displayed:
ETRIRTRQ ETRIRTR2 ETRIRTFB ETRIRTF2
ETRIVRRQ ETRIVRFB ETRSDMRQ ETRSDMFB
ETRTRCRQ ETRTRCFB ETRPRGRQ ETRPRGR2
ETRPRGFB ETRPRGF2
Release history
ETSISMGR was created in GSM05.
Group structure
ETSISMGR provides three tuples per DMS-MSC/Call Server.
Info field: None
None
Associated products
None
Validation Formula

3-102 OM groups: E

or equal to the sum of the number of dialogue fall backs recommended to its
tuples).
Register ETRIRTRQ 3
Register ETRIRTRQ is a peg register that records the number of fall backs
from the various InfoRetrieval(14) context versions recommended by the
tuples in this register and the tuples in ETRIRTFB, which records the number
of fall backs to the InfoRetrieval(14) context versions, the operator gets an
indication of the InfoRetrieval(14) context versions provisioned in the
network.
Associated register
ETRIRTFB
Validation formula
InfoRetrieval and InterVlrInfoRetrieval both fall back to InfoRetrieval.
Therefore, no definite relationship can be drawn between ETRIRTRQ and
ETRIRTFB in an MSC/Call Server INode configuration.
Otherwise on the DMS-HLR, the number of pegs to register ETRIRTRQ is

greater than or equal to the number of pegs to register ETRIRTFB.
Associated logs
None
EXT register
ETRIRTR2
Register ETRIRTFB 3
Register ETRITRFB is a peg register that records the number of fall backs to
the various InfoRetrieval(14) context versions recommended by the DMS-
HLR. Note that InfoRetrieval(14) version1(1) is the fall back for


OM groups: E 3-103
Associated register
ETRIRTRQ and ETRIVRRQ
Validation formula
Therefore, no definite relationship can be drawn between ETRIRTFB,
ETRIRTRQ, and ETRIVRFB in an MSC/Call Server INode configuration.
Otherwise on the DMS-HLR, the number of pegs to register ETRIRTFB is

less than or equal to the number of pegs to register ETRIRTRQ. On the DMS-
MSC/Call Server, the number of pegs to register ETRIRTFB is less than or
equal to the number of pegs to register ETRIVRRQ.
Associated logs
None
EXT register
ETRIRTF2
Register ETRIVRRQ 3
Register ETRIVRRQ is a peg register that records the number of fall backs
from the various InterVlrInfoRetrieval(15) context versions recommended by
the DMS-MSC/Call Server. Note that the fall back for
InterVlrInfoRetrieval(15) version2(2) is InfoRetrieval(14) version1(1).
By examining tuples in this register, tuples in ETRIVRFB, and the version1

tuple in ETRIRTFB, the operator gets an indication of the
in the network.
Associated register
ETRIVRFB and ETRIRTFB
Validation formula
Therefore, no definite relationship can be drawn between ETRIVRRQ and
ETRIRTFB in an MSC/Call Server INode configuration.
Otherwise on the DMS-MSC/Call Server, the number of pegs to register

ETRIVRRQ is greater than or equal to the number of pegs to register
ETRIVRFB and ETRIRTFB.
Associated logs
None

3-104 OM groups: E
EXT register
None
Register ETRIVRFB 3
Register ETRIVRFB is a peg register that records the number of fall backs to
the various InterVlrInfoRetrieval(15) context versions recommended by the
Associated register
None
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRIVRFB is
less than or equal to the number of pegs to register ETRIVRRQ.
Associated logs
None
EXT register
None
Register ETRSDMRQ 3
Register ETRSDMRQ is a peg register that records the number of fall backs
from the various SubscriberDataMngt(16) context versions recommended by
examining the tuples in this register and the tuples in ETRSDMFB, which
record the number of fall backs to the SubscriberDataMngt(16) context
versions, the operator gets an indication of the SubscriberDataMngt(16)
Associated register
ETRSDMFB
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRSDMRQ
is greater than or equal to the number of pegs to ETRSDMFB.
Associated logs
None

OM groups: E 3-105
EXT register
None
Register ETRSDMFB 3
Register ETRSDMFB is a peg register that records the number of fallbacks to
the various SubscriberDataMngt(16) context versions recommended by the
examining the tuples in this register and the tuples in ETRSDMRQ, which
records the number of fall backs from the SubscriberDataMngt(16) context
Associated register
ETRSDMRQ
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRSDMFB is
less than or equal to the number of pegs to register ETRSDMRQ.
Associated logs
None
EXT register
None
Register ETRTRCRQ 3
Register ETRTRCRQ is a peg register that records the number of fall backs
from the various Tracing(17) context versions recommended by the DMS-
the tuples in this register and the tuples in ETRTRCFB, which record the
number of fall backs to the Tracing(17) context versions, the operator gets an
indication of the Tracing(17) context versions provisioned in the network.
Associated register
ETRTRCFB
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRTRCRQ is
greater than or equal to the number of pegs to register ETRTRCFB.
Associated logs
None

3-106 OM groups: E
EXT register
None
Register ETRTRCFB 3
Register ETRTRCFB is a peg register that records the number of fallbacks to
the various Tracing(17) context versions recommended by the DMS-MSC/
tuples in this register and the tuples in ETRTRCRQ, which records the
number of fall backs from the Tracing(17) context versions, the operator gets
an indication of the Tracing(17) context versions provisioned in the network.
Associated register
ETRTRCRQ
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRTRCFB is
less than or equal to the number of pegs to register ETRTRCRQ.
Associated logs
None
EXT register
None
Register ETRPRGRQ 3
Register ETRPRGRQ is a peg register that records the number of fall backs
from the various MsPurging(27) context versions recommended by the DMS-
this register and the tuples in ETRPRGFB, which record the number of fall
backs to the MsPurging(27) context versions, the operator gets an indication
of the MsPurging(27) context versions provisioned in the network.
Associated register
ETRPRGFB
Validation formula
On the DMS-HLR, the number of pegs to register ETRPRGRQ is greater than
or equal to the number of pegs to register ETRPRGFB.
Associated logs
None

OM groups: E 3-107
EXT register
ETRPRGR2
Register ETRPRGFB 3
Register ETRPRGFB is a peg register that records the number of fallbacks to
the various MsPurging(27) context versions recommended by the DMS-HLR.
register and the tuples in ETRPRGRQ, which records the number of fall
backs from the MsPurging(27) context versions, the operator gets an
Associated register
ETRPRGRQ
Validation formula
On the DMS-HLR, the number of pegs to register ETRPRGFB is less than or
equal to the number of pegs to register ETRPRGRQ.
Associated logs
None
EXT register
ETRPRGF2

3-108 OM groups: E
ETSISMSI
ETSI Short Message Service Dialogue Initiator 3
For a dialogue initiator, ETSISMSI measures the number of fall to and backs
from the Short Message Services related application context versions. The
application context versions
Registers
The following ETSISMSI registers may be displayed:
ETISMORQ ETISMOFB ETISMARQ ETISMAR2
ETISMAFB ETISMAF2 ETIMWDRQ ETIMWDFB
ETISMTRQ ETISMTFB
Release history
ETSISMSI was created in GSM05.
Group structure
ETSISMSI provides three tuple per DMS-MSC/Call Server.
Info field: none
GMAPSMS

Associated products
None

OM groups: E 3-109
Validation Formula

(given by the corresponding RES and RS2 registers provided by AD4634)
and number of dialogue requests for the application context (given by the
appropriate RQ and R2 fields and tuples).

Register ETIMWDFB 3
Number of Fallbacks to the MwdMngt(24) Context.
Register ETIMWDFB is a peg register that records the number of fallbacks to

the various MwdMngt(24) context versions performed by the DMS-MSC/
tuples in this register and the tuples in ETIMWDRQ, which records the
number of fall backs from the MwdMngt(24) context versions, the operator
gets an indication of the MwdMngt(24) context versions provisioned in the
network.
ETIMWDRQ
GMNMPREQ from group GMAPSMS.
Validation formula
On the DMS-MSC/Call Server, the number of pegs to registers GMNMPREQ
from group GMAPSMS is greater or equal to the number of pegs to register
ETIMWDFB.
On the DMS-MSC/Call Server, the number of pegs to register ETIMWDFB

is less than or equal to the number of pegs to register ETIMWDRQ.
Associated logs
None
EXT register
None

3-110 OM groups: E
Register ETIMWDRQ 3
Number of Fallbacks from the MwdMngt(24) Context.
Register ETIMWDRQ is a peg register that records the number of fall backs
from the various MwdMngt(24) context versions performed by the DMS-
the tuples in this register and the tuples in ETIMWDFB, which record the
number of fall backs to the MwdMngt(24) context versions, the operator gets
an indication of the MwdMngt(24) context versions provisioned in the
network.
ETIMWDFB
Validation formula
ETIMWDRQ.
On the DMS-MSC/Call Server, the number of pegs to register ETIMWDRQ

is greater than or equal to the number of pegs to register ETIMWDFB.
Associated logs
None
EXT register
None
Register ETISMAFB 3
Number of Fallbacks to the ShortMsgAlert(23) Context.
Register ETISMAFB is a peg register that records the number of fallbacks to

the various ShortMsgAlert(23) context versions performed by the DMS-
this register and the tuples in ETISMARQ, which records the number of fall
backs from the ShortMsgAlert(23) context versions, the operator gets an
indication of the ShortMsgAlert(23) context versions provisioned in the
network.
Associated register
ETISMARQ

OM groups: E 3-111
Validation formula
On the DMS-HLR, the number of pegs to register ETISMAFB is less than or
equal to the number of pegs to register ETISMARQ.
Associated logs
None
EXT register
ETISMAF2
Register ETISMARQ 3
Number of Fallbacks from the ShortMsgAlert(23) Context.
Register ETISMARQ is a peg register that records the number of fall backs
from the various ShortMsgAlert(23) context versions performed by the DMS-
this register and the tuples in ETISMAFB, which record the number of fall
backs to the ShortMsgAlert(23) context versions, the operator gets an
network.
Associated register
ETISMAFB
Validation formula
On the DMS-HLR, the number of pegs to register ETISMARQ is greater than
or equal to the number of pegs to register ETISMAFB.
Associated logs
None
EXT register
ETISMAR2
Register ETISMOFB 3
Number of Fallbacks to the ShortMsgAlert(23) Context.
ETISMOFB records the number of fall backs to ShortMsgRelay(21)

version1(1) and ShortMsgMO-Relay(21) context versions experienced by the
DMS-MSC/Call Server. The fallbacks to each version of ShortMsgMO-
Relay(21) context and ShortMsgRelay(21) version1(1) are recorded on a per
tuple basis. By examining this register and ETISMORQ, which records the
number of fall backs from the ShortMsgMO-Relay(21) context, the operator
gets an indication of the ShortMsgMO-Relay(21) and ShortMsgRelay(21)

3-112 OM groups: E
Associated register
ETISMORQ
GMFSMREQ and GMFSMRES from group GMAPSMS.
Validation formula
On the DMS-MSC/Call Server, the number of pegs to registers GMFSMREQ
from group GMAPSMS is greater or equal to the sum of the number of pegs
to registers GMFSMRES from group GMAPSMS and ETISMOFB.
On the DMS-MSC/Call Server, the number of pegs to register ETISMOFB is

less than or equal to the number of pegs to register ETISMORQ.
Associated logs
None
EXT register
None
Register ETISMORQ 3
Number of Fallbacks from ShortMsgMO-Relay(21) and ShortMsgRelay(21)
Contexts.
Register ETISMORQ is a peg register that records the number of fall backs
from the various ShortMsgMO-Relay(21) context versions performed by the
examining the tuples in this register and the tuples in ETSIMOFB, which
records the number of fall backs to the ShortMsgMO-Relay(21) context
versions and to ShortMsgRelay(21) version1(1), the operator gets an
indication of the ShortMsgRelay(21) and ShortMsgRelay(21) context
ETISMOFB
GMFSMREQ and GMFSMRES from Group GMAPSMS.
Validation formula
On the DMS-MSC/Call Server, the number of pegs to GMFSMREQ from
group GMAPSMS is greater than or equal to the sum of the number of pegs to
GMFSMRES from group GMAPSMS and ETISMORQ.
On the DMS-MSC/Call Server, the number of pegs to register ETISMORQ is

greater than or equal to the number of pegs to register ETISMOFB.

OM groups: E 3-113
Associated logs
None
EXT register
None

3-114 OM groups: E
ETSISMSR
ETSI Short Message Service Dialogue Responder 3
For a dialogue responder, ETSISMSR measures the number of fall backs to
and from the Short Messages Services related application context versions.
Registers
The following ETSISMSR registers may be displayed:
ETRSGWRQ ETRSGWR2 ETRSGWFB ETRSGWF2
ETRSMORQ ETRSMOFB ETRSMARQ ETRMWDRQ
ETRMWDR2 ETRMWDFB ETRMWDF2 ETRSMTRQ
ETRSMTFB
Release history
ETSISMSR was created in GSM05.
Group structure
ETSISMSR provides three tuples per DMS-MSC/Call Server.
Info field: None
None
Associated products
None
Validation Formula
occur, no registers are pegged. The sum of the number of dialogue requests
for a particular application context (given by the appropriate RQ and R2

OM groups: E 3-115
fields and tuples) is greater than or equal to the sum of the number of dialogue
fall backs recommended its alternative application context (given by the
appropriate FB and F2 fields and tuples).
Register ETRSGWRQ 3
ETSI Dialogue Responder ShortMsgGateway
Register ETRSGWRQ is a peg register that records the number of fall backs
from the various ShortMsgGateway(20) context versions recommended by
tuples in this register and the tuples in ETRSGWFB, which records the
number of fall backs to the ShortMsgGateway(20) context versions, the
operator gets an indication of the ShortMsgGateway(20) context versions
Associated register
ETRSGWFB
Validation formula
On the DMS-HLR, the number of pegs to register ETRSGWRQ is greater
than or equal to the number of pegs to register ETRSGWFB.
Associated logs
None
EXT register
ETRSGWR2
Register ETRSGWFB 3
ETSI Dialogue Responder ShortMsgGateway-Fallbacks
Register ETRSGWFB is a peg register that records the number of fallbacks to
the various ShortMsgGateway(20) context versions recommended by the
tuples in this register and the tuples in ETRSGWRQ, which records the
number of fall backs from the ShortMsgGateway(20) context versions, the
Associated register
ETRSGWRQ
Validation formula
On the DMS-HLR, the number of pegs to register ETRSGWFB is less than or
equal to the number of pegs to register ETRSGWRQ.

3-116 OM groups: E
Associated logs
None
EXT register
ETRSGWF2
Register ETRSMORQ 3
ETSI Dialogue Responder ShortMsgMo-Relay Request
Register ETRSMORQ is a peg register that records the number of fall backs
from the various ShortMsgMO-Relay(21) context versions recommended by
the DMS-MSC/Call Server. Tuples of this register represent versions.
The DMS-MSC/Call Server does not support SMS IWMSC functionality.
Associated register
ETRSMOFB
Validation formula
The number of pegs to register ETRSMORQ is greater than or equal to the
number of pegs to register ETRSMOFB.
Associated logs
None
EXT register
None
Register ETRSMOFB 3
ETSI Dialogue Responder ShortMsgMo-Fallback
Register ETRSMOFB is a peg register that records the number of fall backs
to ShortMsgRelay(21) version1(1) and ShortMsgMO-Relay(21) context
versions recommended by the DMS-MSC/Call Server. The fallbacks to
ShortMsgRelay(21) version1(1) and each version of ShortMsgMO-Relay(21)
context are recorded on a per tuple basis.
By examining this register and ETRSMTRQ, which records the number of

fall backs from the ShortMsgMT-Relay(25) context, the operator gets an
indication of the ShortMsgMT-Relay(25) and ShortMsgRelay(21) context
Associated register
ETRSMTRQ

OM groups: E 3-117
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRSMOFB is
less than or equal to the number of pegs to register ETRSMTRQ.
Associated logs
None
EXT register
None
Register ETRSMARQ 3
ETSI Dialogue Responder ShortMsgAlert Request
Register ETRSMARQ is a peg register that records the number of fall backs
from the various ShortMsgAlert(23) context versions recommended by the
DMS-MSC/Call Server. Tuples of this register represent versions.
Associated register
None
Validation formula
None
Associated logs
None
EXT register
None
Register ETRMWDRQ 3
ETSI Dialogue Responder ShortMsgMwdMngt Request
Register ETRMWDRQ is a peg register that records the number of fall backs
from the various MwdMngt(24) context versions recommended by the DMS-
this register and the tuples in ETRMWDFB, which record the number of fall
backs to the MwdMngt(24) context versions, the operator gets an indication
of the MwdMngt(24) context versions provisioned in the network.
Associated register
ETRMWDFB
Validation formula
On the DMS-HLR, the number of pegs to register ETRMWDRQ is greater
than or equal to the number of pegs to register ETRMWDFB.

3-118 OM groups: E
Associated logs
None
EXT register
ETRMWDR2
Register ETRMWDFB 3
ETSI Dialogue Responder ShortMsgMwdMngt-Fallback
Register ETRMWDFB is a peg register that records the number of fallbacks
to the various MwdMngt(24) context versions recommended by the DMS-
this register and the tuples in ETRMWDRQ, which records the number of fall
backs from the MwdMngt(24) context versions, the operator gets an
indication of the MwdMngt(24) context versions provisioned in the network.
Associated register
ETRMWDRQ
Validation formula
On the DMS-HLR, the number of pegs to register ETRMWDFB is less than
or equal to the number of pegs to ETRMWDRQ.
Associated logs
None
EXT register
ETRMWDF2
Register ETRSMTRQ 3
ETSI Dialogue Responder ShortMsgMt Request
Register ETRSMTRQ is a peg register that records the number of fall backs
from the various ShortMsgMT-Relay(25) context versions recommended by
the DMS-MSC/Call Server. Note that the fall back for ShortMsgMT-
Relay(25) version2(2) is ShortMsgRelay(21) version1(1).
By examining tuples in this register, tuples in ETRSMTFB, and the version1

tuple in ETRSMRFB, the operator gets an indication of the Short Message
Mobile Termination context versions provisioned in the network.
Associated register
ETRSMTFB and ETRSMOFB

OM groups: E 3-119
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRSMTRQ
is greater than or equal to the number of pegs to register ETRSMTFB and the
version1 tuple of ETRSMOFB.
Associated logs
None
EXT register
None
Register ETRSMTFB 3
ETSI Dialogue Responder ShortMsgMt-Fallback
Register ETRSMTFB is a peg register that records the number of fall backs to
the various ShortMsgMT-Relay(25) context versions recommended by the
examining the tuples in this register and the tuples in ETRSMTRQ, which
records the number of fall backs from the ShortMsgMT-Relay(25) context
versions, the operator gets an indication of the ShortMsgMT-Relay(25)
Associated register
ETRSMTRQ
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRSMTFB is
less than or equal to the number of pegs to register ETRSMTRQ.
Associated logs
None

3-120 OM groups: E
ETSISSI
ETSI Supplementary Services Dialogue Initiator 3
For a dialogue initiator, ETSISSI measures the number of fall backs to and
from the Supplementary Services related application context versions and the
number of fall backs to the Supplementary Services related application
context versions. The fields represent the various application contexts, and
the tuples represent the application context versions.
Registers
The following ETSISSI registers may be displayed:
ETINSSRQ ETINSSFB ETINUSRQ ETINUSR2
ETINUSFB ETINUSF2 ETIMUSRQ ETIMUSFB
Release history
ETSISSI was created with GSM05.
Group structure
ETSISSI provides three tuples per DMS-MSC/Call Server.
Info field: None
GMAPSS

Associated products
None

OM groups: E 3-121
Validation Formula

fields and tuples).

Register ETIMUSFB 3
Number of Fallbacks from NetworkUnstructuredSs(19) Context.
Register ETIMUSFB is a peg register that records the number of fallbacks to

the various mobile initiated NetworkUnstructuredSS(19) context versions
performed by the DMS-MSC/Call Server. Tuples of this register represent
versions. By examining the tuples in this register and the tuples in
ETIMUSRQ, which records the number of fall backs from the mobile
initiated NetworkUnstructuredSS(19) context versions, the operator gets an
indication of the mobile initiated NetworkUnstructuredSs(19) context
Associated register
ETIMUSRQ
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETIMUSFB is
less than or equal to the number of pegs to register ETIMUSRQ.
Associated logs
None
EXT register
None
Register ETIMUSRQ 3
Register ETIMUSRQ is a peg register that records the number of fall backs
from the various mobile initiated NetworkUnstructuredSs(19) context

3-122 OM groups: E
versions performed by the DMS-MSC/Call Server. Note that the fall back for
mobile initiated NetworkUnstructuredSs(19) version2(2) is
NetworkFunctionalSs(18) version1(1).
By examining tuples in this register, tuples in ETIMUSFB, and the version1

tuple in ETINSSFB, the operator gets an indication of the unstructured SS
Associated register
ETIMUSFB and ETINSSFB
Validation formula
Not applicable on the DMS-MSC/Call Server because Mobile Initiated
UnstructuredSS has no Phase1 implementation.
If higher versions of Network Initiated UnstructuredSS are supported, then

the number of pegs to register ETIMUSRQ will be greater or equal to the
number of pegs to register ETIMUSFB and the version1 tuple of ETINSSFB.
Associated logs
None
EXT register
None
Register ETINSSFB 3
Number of Fallbacks to NetworkFunctionalSs(18) Context.
Register ETINSSFB is a peg register that records the number of fall backs to
the various NetworkFunctionalSs(18) context versions performed by the
DMS-MSC/Call Server. Note that NetworkFunctionalSs(18) version1(1) is
the fall back for network initiated NetworkUnstructuredSs(19) version2(2).
By examining tuples in this register, the version2 tuple in ETINUSRQ, and

tuples in ETINSSRQ, the operator gets an indication of the structured SS
Associated register
ETINSSRQ, ETINUSRQ, ETIMUSRQ
GMRSSREQ, GMRSSRES, GMESSREQ, GMESSRES, GMISSREQ,

GMISSRES, GMRPWREQ, GMRPWRES, GMASSREQ, GMASSRES,
GMDSSREQ, and GMDSSRES from group GMAPSS.

OM groups: E 3-123
Validation formula
On the DMS-MSC/Call Server, the number of pegs to REQ registers from
group GMAPSS is greater or equal to the sum of the number of pegs to the
RES registers from group GMAPSS and ETINSSFB.

number of pegs to register ETINSSRQ and the number of pegs to register
ETINSSFB because UnstructuredSS context may fall back to
NetworkFunctionalSS context.
Associated logs
None
EXT register
None
Register ETINSSRQ 3
Number of FallBacks from NetworkFunctionalSs(18) Context.
Register ETINSSRQ is a peg register that records the number of fall backs
from the various NetworkFunctionalSs(18) context versions performed by the
examining the tuples in this register and the tuples in ETINSSFB, which
records the number of fall backs to the NetworkFunctionalSs(18) context
versions, the operator gets an indication of the NetworkFunctionalSs(18)
ETINSSFB

Validation formula
On the DMS-MSC/Call Server, the number of pegs to the REQ registers from
group GMAPSS is greater than or equal to the sum of the number of pegs to
the RES registers from group GMAPMMGT and ETINSSRQ.

number of pegs to register ETINSSRQ and the number of pegs to register
ETINSSFB because UnstructuredSS context may fall back to
Associated logs
None

3-124 OM groups: E
EXT register
None
Register ETINUSFB 3
Register ETINUSFB is a peg register that records the number of fallbacks to

the various network initiated NetworkUnstructuredSS(19) context versions
performed by the DMS-HLR. Tuples of this register represent versions. By
examining the tuples in this register and the tuples in ETINUSRQ, which
records the number of fall backs from the network initiated
NetworkUnstructuredSS(19) context versions, the operator gets an indication
of the network initiated NetworkUnstructuredSs(19) context versions
Associated register
ETINUSRQ
Validation formula
On the DMS-HLR, the number of pegs to register ETINUSFB is less than or
equal to the number of pegs to register ETINUSRQ.
Associated logs
None
EXT register
ETINUSF2
Register ETINUSRQ 3
Register ETINUSRQ is a peg register that records the number of fall backs
from the various network initiated NetworkUnstructuredSs(19) context
versions performed by the DMS-HLR. Note that the fall back for network
initiated NetworkUnstructuredSs(19) version2(2) is
By examining tuples in this register, tuples in ETINUSFB, and the version1

tuple in ETINSSFB, the operator gets an indication of the unstructured SS
Associated register
ETINUSFB

OM groups: E 3-125
Validation formula
Not applicable on the DMS-HLR because Network Initiated UnstructuredSS
has no PhaseI implementation.

the number of pegs to register ETINUSRQ will be greater or equal to the
number of pegs to register ETINUSFB.
Associated logs
None
EXT register
ETINUSR2

3-126 OM groups: E
ETSISSR
ETSI Supplementary Services Dialogue Responder 3
For a dialogue responder, ETSISSR measures the number of fall backs to and
from the Supplementary Services related application context versions and the
number of fall backs to the Supplementary Services related application
context versions. The fields represent the various application contexts, and
the tuples represent the application context versions.
Registers
The following ETSISSR registers may be displayed:
ETRNSSRQ ETRNSSR2 ETRNSSFB ETRNSSF2
ETRNUSRQ ETRNUSFB ETRMUSRQ ETRMUSR2
ETRMUSFB ETRMUSF2
Release history
ETSISSR was created in GSM02.
Group structure
ETSISSR provides three tuple per DMS-MSC/Call Server.
Info field: None
None
Associated products
None
Validation Formula

OM groups: E 3-127

or equal to the sum of the number of dialogue fall backs recommended to its
tuples).
Register ETRNSSRQ 3
Number of Fallbacks from NetworkFunctionalSs(18) Context.
Register ETRNSSRQ is a peg register that records the number of fall backs
from the various NetworkFunctionalSs(18) context versions recommended by
tuples in this register and the tuples in ETRNSSFB, which records the number
of fall backs to the NetworkFunctionalSs(18) context versions, the operator
gets an indication of the NetworkFunctionalSs(18) context versions
Associated register
ETRNSSFB
Validation formula
On the DMS-HLR, the number of pegs to register ETRNSSRQ is greater or
equal to the number of pegs to register ETRNSSFB.
Associated logs
None
EXT register
ETRNSSR2
Register ETRNSSFB 3
Number of Fallbacks to NetworkFunctionalSs(18) Context.
Register ETRNSSFB is a peg register that records the number of fall backs to
the various NetworkFunctionalSs(18) context versions recommended by the
DMS-HLR. Note that NetworkFunctionalSs(18) version1(1) is the fall back
for network initiated NetworkUnstructuredSs(19) version2(2).
By examining tuples in this register, the version2 tuple in ETRNUSRQ, and

tuples in ETRNSSRQ, the operator gets an indication of the structured SS
Associated register
ETRNSSRQ

3-128 OM groups: E
Validation formula
On the DMS-HLR, the number of pegs to register ETRNSSFB is less than or
equal to the number of pegs to register ETRNSSRQ.
Associated logs
None
EXT register
ETRNSSF2
Register ETRNUSRQ 3
Number of Fallbacks to NetworkUnstructuredSs(19) Context.
Register ETRNUSRQ is a peg register that records the number of fall backs
versions recommended by the DMS-MSC/Call Server. Note that the fall back
for network initiated NetworkUnstructuredSs(19) version2(2) is
By examining tuples in this register, tuples in ETRNUSFB, and the version1

tuple in ETRNSSFB, the operator gets an indication of the unstructured SS
Associated register
ETRNUSFB
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRNUSRQ is
greater than or equal to the number of pegs to register ETRNUSFB.
Associated logs
None
EXT register
None
Register ETRNUSFB 3
Register ETRNUSFB is a peg register that records the number of fallbacks to

recommended by the DMS-MSC/Call Server. Tuples of this register represent
ETINUSRQ, which records the number of fall backs from the network

OM groups: E 3-129
indication of the network initiated NetworkUnstructuredSs(19) context

Associated register
ETRNUSRQ
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRNUSFB is
less than or equal to the number of pegs to register ETRNUSRQ.
Associated logs
None
EXT register
None
Register ETRMUSRQ 3
Register ETRMUSRQ is a peg register that records the number of fall backs
versions performed by the DMS-HLR. Note that the fall back for mobile
By examining tuples in this register, tuples in ETRMUSFB, and the version1

tuple in ETRNSSFB, the operator gets an indication of the unstructured SS
Associated register
ETRMUSFB and ETRNSSFB
Validation formula
On the DMS-HLR, the number of pegs to register ETRMUSRQ is greater
than or equal to the number of pegs to registers ETRMUSFB and the version1
tuple of ETRNSSFB.
Associated logs
None
EXT register
ETRMUSR2

3-130 OM groups: E
Register ETRMUSFB 3
Register type
Peg
Register ETRMUSFB is a peg register that records the number of fallbacks to
the various mobile initiated NetworkUnstructuredSS(19) context versions
examining the tuples in this register and the tuples in ETRMUSRQ, which
record the number of fall backs from the mobile initiated
of the mobile initiated NetworkUnstructuredSs(19) context versions
Associated register
None
Validation formula
On the DMS-HLR, the number of pegs to register ETRMUSFB is less than or
equal to the number of pegs to register ETRMUSRQ.
Associated logs
None
EXT register
ETRMUSF2

OM groups: E 3-131
ETSMGIMU
ETSI Subscriber Management Dialogue Initiator on the MMU 3
For a dialogue initiator, ETSMGIMU measures the number of fall backs to
and from the Subscriber Management related application context versions.
Registers
The following ETSMGIMU registers may be displayed:
EIRTRQMU EIRTRMU2 EIRTFBMU EIRTFMU2
EIVRRQMU EIVRFBMU ESMDRQMU ESDMRMU2
ESDMFMMU ESDMFMU2 ETRCRQMU ETRCRMU2
ETRCFBMU ETRCFMU2 EPRGRQMU EPRGFBMU
Release history
ETSMGIMU was created in GSM11.
Group structure
ETSMGIMU
Associated products
MMU
Validation Formula
corresponding MMU.

3-132 OM groups: E
Register EIRTFBMU 3
Number of Fallbacks to InfoRetrieval(14) Context per MMU.
Register ETIITRFB is a peg register that records the number of fall backs to
the various InfoRetrieval(14) context versions performed by the DMS-MSC/
Call Server. Note that InfoRetrieval(14) version1(1) is the fall back for
By examining tuples in this register, the version2 tuple in EIVRRQMU, and

Release history
Register ETIITRFB was created in GSM11.
Associated register
ETIIRTRQ, EIVRRQMU, ETIIVRR2
SAIREQ and SAIRES in group GMAPSMGT.
Validation formula
On the DMS-MSC/Call Server, the number of pegs to SAIREQ from group
GMAPSMGT is greater or equal to the sum of the number of pegs to SAIRES
from group GMAPSMGT and EIRTFBMU.

EIRTFBMU because Inter-Vlr Information Retrieval context may fall back to
Associated logs
None
EXT register
EIRTFMU2
Register ETIIRTRQ 3
Number of Fallbacks from InfoRetrieval(14) Context per MMU.
Register ETIIRTRQ is a peg register that records the number of fall backs
from the various InfoRetrieval(14) context versions performed by the DMS-
the tuples in this register and the tuples in EIRTFBMU, which records the

OM groups: E 3-133

network.
Release history
Register ETIIRTRQ was created in GSM11.
Associated register
EIRTFBMU
SAIREQ and SAIRES in group GMAPSMGT.
Validation formula
On the DMS-MSC/Call Server, the number of pegs to SAIREQ in group
GMAPSMGT is greater than or equal to the sum of the number of pegs to
SAIRES from group GMAPSMGT and ETIIRTRQ.

EIRTFBMU because Inter-VLR Information Retrieval context may fall back
to Information Retrieval context.
Associated logs
None
EXT register
EIRTRMU2
Register EIVRFBMU 3
Number of Fallbacks to InterVlrInfoRetrieval(15) Context per MMU.
Register EIVRFBMU is a peg register that records the number of fall backs to
the various InterVlrInfoRetrieval(15) context versions performed by the
examining the tuples in this register and the tuples in EIVRRQMU, which
Release history
Register EIVRFBMU was created in GSM11.
Associated register
None

3-134 OM groups: E
Validation formula
therefore the validation formula is not applicable.
register in group GMAPSMGT and EIVRFBMU.
If this context were supported, then the number of pegs to EIVRFBMU will
be less than or equal to the number of pegs to EIVRRQMU.
Associated logs
None
EXT register
None
Register EIVRRQMU 3
Number of Fallbacks from InterVlrInfoRetrieval(15) Context per MMU.
Register EIVRRQMU is a peg register that records the number of fall backs
from the various InterVlrInfoRetrieval(15) context versions performed by the
DMS-MSC/Call Server. Note that the fall back for InterVlrInfoRetrieval(15)
version2(2) is InfoRetrieval(14) version1(1).
By examining tuples in this register, tuples in EIVRFBMU, and the version1

tuple in EIRTFBMU, the operator gets an indication of the
in the network.
Release history
Register EIVRRQMU was created in GSM11.
Associated register
EIVRFBMU, EIRTFBMU
Validation formula
therefore, the validation formula is not applicable.
register in group GMAPSMGT and EIVRRQMU.

OM groups: E 3-135
If this context were supported, then the number of pegs to EIVRRQMU

would be greater than or equal to the number of pegs to EIVRFBMU.
Associated logs
None
EXT register
None
Register EPRGFBMU 3
Number of Fallbacks to MsPurging(27) Context per MMU.
Register EPRGFBMU is a peg register that records the number of fallbacks to

the various MsPurging(27) context versions performed by the DMS-MSC/
tuples in this register and the tuples in EPRGRQMU, which records the
number of fall backs from the MsPurging(27) context versions, the operator
gets an indication of the MsPurging(27) context versions provisioned in the
network.
Release history
Register EPRGFBMU was created in GSM11.
Associated register
None
Validation formula
request register in group GMAPSMGT will be greater than or equal to the
sum of the number of pegs to the Send Identification result register in group
GMAPSMGT and EPRGFBMU.
If this context were supported, then the number of pegs to EPRGFBMU

would be less than or equal to the number of pegs to EPRGRQMU.
Associated logs
None
EXT register
None

3-136 OM groups: E
Register EPRGRQMU 3
Number of Fallbacks from MsPurging(27) Context per MMU.
Register EPRGRQMU is a peg register that records the number of fall backs
from the various MsPurging(27) context versions performed by the DMS-
the tuples in this register and the tuples in EPRGFBMU, which record the
number of fall backs to the MsPurging(27) context versions, the operator gets
an indication of the MsPurging(27) context versions provisioned in the
network.
Release history
Register EPRGRQMU was created in GSM11.
Associated register
EPRGFBMU
Validation formula
request register in group GMAPSMGT would be greater than or equal to the
sum of the number of pegs to the PurgeMS result register in group
GMAPSMGT and EPRGRQMU.
If this context were supported, then the number of pegs to EPRGRQMU

would be greater than or equal to the number of pegs to EPRGFBMU.
Associated logs
None
EXT register
None
Register ESDMFMMU 3
Number of Fallbacks to SubscriberDataMngt(16) Context per MMU.
Register ESDMFMMU is a peg register that records the number of fallbacks

to the various Subscriber DataMngt(16) context versions performed by the
tuples in this register and the tuples in ESMDRQMU, which records the
number of fall backs from the SubscriberDataMngt(16) context versions, the

OM groups: E 3-137
Release history
Register ESDMFMMU was created in GSM11.
Associated register
ESMDRQMU
Validation formula
On the DMS-HLR, the number of pegs to register ESDMFMMU is less than
or equal to the number of pegs to register ESMDRQMU.
Associated logs
None
EXT register
ESDMFMU2
Register ESMDRQMU 3
Number of Fallbacks from SubscriberDataMngt(16) Context per MMU.
Register ESMDRQMU is a peg register that records the number of fall backs
from the various SubscriberDataMngt(16) context versions performed by the
tuples in this register and the tuples in ESDMFMMU, which records the
number of fall backs to the SubscriberDataMngt(16) context versions, the
Release history
Register ESMDRQMU was created in GSM11.
Associated register
ESDMFMMU
Validation formula
On the DMS-HLR, the number of pegs to register ESMDRQMU is greater
than or equal to the number of pegs to register ESDMFMMU.
Associated logs
None
EXT register
ESDMRMU2
Register ETRCFBMU 3
Number of Fallbacks to Tracing(17) Context per MMU.

3-138 OM groups: E
Register ETRCFBMU is a peg register that records the number of fallbacks to

the various Tracing(17) context versions performed by the DMS-HLR.
register and the tuples in ETRCRQMU, which records the number of fall
backs from the Tracing(17) context versions, the operator gets an indication
of the Tracing(17) context versions provisioned in the network.
Release history
Register ETRCFBMU was created in GSM11.
Associated register
ETRCRQMU
Validation formula
On the DMS-HLR, the number of the number of pegs to register
ETRCFBMU is less than or equal to the number of pegs to register
ETRCRQMU.
Associated logs
None
EXT register
ETRCFMU2
Register ETRCRQMU 3
Number of Fallbacks from Tracing(17) Context per MMU.
Register ETRCRQMU is a peg register that records the number of fall backs
from the various Tracing(17) context versions performed by the DMS-HLR.
register and the tuples in ETRCFBMU, which record the number of fall backs
to the Tracing(17) context versions, the operator gets an indication of the
Release history
Register ETRCRQMU was created in GSM11.
Associated register
ETRCFBMU
Validation formula
On the DMS-HLR, the number of pegs to register ETRCRQMU is greater
than or equal to the number of pegs to register ETRCFBMU.

OM groups: E 3-139
Associated logs
None
EXT register
ETRCRMU2

3-140 OM groups: E
ETSMGRMU
ETSI Subscriber Management Dialogue Responder on the MMU 3
The GSM Mobile Application Part Subscriber Management group contains
the registers for operations handling subscriber data such as Insert Subscriber
Data, Delete Subscriber Data, and Send Parameters.
Registers
The following ETSMGRMU registers may be displayed:
EIRTRQMU EIRTRMU2 EIRTFBMU EIRTFMU2
EIVRRQMU EIVRFBMU ESDMRQMU ESDMFBMU
ETRCRQMU ETRCFBMU EPRGRQMU EPRGR2MU
EPRGFBMU EPRGFMU2
Release history
ETSMGRMU was created in GSM11.
Group structure
ETSISMGR
Associated products
MMU
Validation Formula
Register EIRTRQMU 3
Number of fall backs from the various InfoRetrieval(14) context per MMU.

OM groups: E 3-141
Register EIRTRQMU is a peg register that records the number of fall backs
from the various InfoRetrieval(14) context versions recommended by the
tuples in this register and the tuples in EIRTFBMU, which records the
network.
Release history
Register EIRTRQMU was created in GSM11.
Associated register
EIRTFBMU
Validation formula
Therefore, no definite relationship can be drawn between EIRTRQMU and
EIRTFBMU in an MSC/Call Server INode configuration.
Otherwise on the DMS-HLR, the number of pegs to register EIRTRQMU is

greater than or equal to the number of pegs to register EIRTFBMU.
Associated logs
None
EXT register
EIRTRMU2
Register EIRTFBMU 3
Number of fall backs to the various InfoRetrieval(14) context per MMU.
Register ETRITRFB is a peg register that records the number of fall backs to
the various InfoRetrieval(14) context versions recommended by the DMS-
HLR. Note that InfoRetrieval(14) version1(1) is the fall back for

Release history
Register ETRITRFB was created in GSM11.
Associated register
EIRTRQMU and EIVRRQMU

3-142 OM groups: E
Validation formula
Therefore, no definite relationship can be drawn between EIRTFBMU,
EIRTRQMU, and EIVRFBMU in an MSC/Call Server INode configuration.
Otherwise on the DMS-HLR, the number of pegs to register EIRTFBMU is

less than or equal to the number of pegs to register EIRTRQMU. On the
DMS-MSC/Call Server, the number of pegs to register EIRTFBMU is less

than or equal to the number of pegs to register EIVRRQMU.
Associated logs
None
EXT register
EIRTFMU2
Register EIVRRQMU 3
Number of fall backs from the various InterVlrInfoRetrieval(15) context per
MMU.
Register EIVRRQMU is a peg register that records the number of fall backs
from the various InterVlrInfoRetrieval(15) context versions recommended by
the DMS-MSC/Call Server. Note that the fall back for
InterVlrInfoRetrieval(15) version2(2) is InfoRetrieval(14) version1(1).
By examining tuples in this register, tuples in EIVRFBMU, and the version1

tuple in EIRTFBMU, the operator gets an indication of the
in the network.
Release history
Register EIVRRQMU was created in GSM11.
Associated register
EIVRFBMU and EIRTFBMU
Validation formula
Therefore, no definite relationship can be drawn between EIVRRQMU and
EIRTFBMU in an MSC/Call Server INode configuration.
Otherwise on the DMS-MSC/Call Server, the number of pegs to register

EIVRRQMU is greater than or equal to the number of pegs to register
EIVRFBMU and EIRTFBMU.

OM groups: E 3-143
Associated logs
None
EXT register
None
Register EIVRFBMU 3
Number of fall backs to the various InterVlrInfoRetrieval(15) context per
MMU.
Register EIVRFBMU is a peg register that records the number of fall backs to
the various InterVlrInfoRetrieval(15) context versions recommended by the
Release history
Register EIVRFBMU was created in GSM11.
Associated register
None
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register EIVRFBMU is
less than or equal to the number of pegs to register EIVRRQMU.
Associated logs
None
EXT register
None
Register ESDMRQMU 3
Number of fall backs from the various SubscriberDataMngt(16) context per
MMU.
Register ESDMRQMU is a peg register that records the number of fall backs
from the various SubscriberDataMngt(16) context versions recommended by
examining the tuples in this register and the tuples in ESDMFBMU, which
record the number of fall backs to the SubscriberDataMngt(16) context

3-144 OM groups: E
Release history
Register ESDMRQMU was created in GSM11.
Associated register
ESDMFBMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ESDMRQMU
is greater than or equal to the number of pegs to ESDMFBMU.
Associated logs
None
EXT register
None
Register ESDMFBMU 3
Number of fallbacks to the various SubscriberDataMngt(16) context per
MMU.
Register ESDMFBMU is a peg register that records the number of fallbacks

to the various SubscriberDataMngt(16) context versions recommended by the
examining the tuples in this register and the tuples in ESDNRQMU, which
records the number of fall backs from the SubscriberDataMngt(16) context
Release history
Register ESDMFBMU was created in GSM11.
Associated register
ESDNRQMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ESDMFBMU
is less than or equal to the number of pegs to register ESDNRQMU.
Associated logs
None
EXT register
None

OM groups: E 3-145
Register ETRCRQMU 3
Number of fall backs from the various Tracing(17) context per MMU.
Register ETRCRQMU is a peg register that records the number of fall backs
from the various Tracing(17) context versions recommended by the DMS-
the tuples in this register and the tuples in ETRCFBMU, which record the
number of fall backs to the Tracing(17) context versions, the operator gets an
indication of the Tracing(17) context versions provisioned in the network.
Release history
Register ETRCRQMU was created in GSM11.
Associated register
ETRCFBMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRCRQMU
is greater than or equal to the number of pegs to register ETRCFBMU.
Associated logs
None
EXT register
None
Register ETRCFBMU 3
Number of fallbacks to the various Tracing(17) context per MMU.
Register ETRCFBMU is a peg register that records the number of fallbacks to

the various Tracing(17) context versions recommended by the DMS-MSC/
tuples in this register and the tuples in ETRCRQMU, which records the
number of fall backs from the Tracing(17) context versions, the operator gets
an indication of the Tracing(17) context versions provisioned in the network.
Release history
Register ETRCFBMU was created in GSM11.
Associated register
ETRCRQMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ETRCFBMU
is less than or equal to the number of pegs to register ETRCRQMU.

3-146 OM groups: E
Associated logs
None
EXT register
None
Register EPRGRQMU 3
Number of fall backs from the various MsPurging(27) context per MMU.
Register EPRGRQMU is a peg register that records the number of fall backs
from the various MsPurging(27) context versions recommended by the DMS-
this register and the tuples in EPRGFBMU, which record the number of fall
backs to the MsPurging(27) context versions, the operator gets an indication
of the MsPurging(27) context versions provisioned in the network.
Release history
Register EPRGRQMU was created in GSM11.
Associated register
EPRGFBMU
Validation formula
On the DMS-HLR, the number of pegs to register EPRGRQMU is greater
than or equal to the number of pegs to register EPRGFBMU.
Associated logs
None
EXT register
EPRGR2MU
Register EPRGFBMU 3
Number of fallbacks to the various MsPurging(27) context per MMU.
Register EPRGFBMU is a peg register that records the number of fallbacks to

the various MsPurging(27) context versions recommended by the DMS-HLR.
register and the tuples in EPRGRQMU, which records the number of fall
backs from the MsPurging(27) context versions, the operator gets an
Release history
Register EPRGFBMU was created in GSM11.

OM groups: E 3-147
Associated register
EPRGRQMU
Validation formula
On the DMS-HLR, the number of pegs to register EPRGFBMU is less than or
equal to the number of pegs to register EPRGRQMU.
Associated logs
None
EXT register
EPRGFMU2

3-148 OM groups: E
ETSMSIMU
ETSI Short Message Service Dialogue Initiator on the MMU 3
For a dialogue initiator, ETSMSIMU measures the number of fallbacks to and
from the Short Message Services related application context versions. The
Registers
The following ETSMSIMU registers may be displayed:
ESMORQMU ESMOFBMU ESMARQMU ESMARMU2
ESMAFBMU ESMAF2MU EMWDRQMU EMWDFBMU
ESMTRQMU ESMTFBMU
Release history
ETSMSIMU was created in GSM11.
Group structure
ETSISMSI
Associated products
MMU
Validation Formula

OM groups: E 3-149
Register EMWDFBMU 3
Number of Fallbacks to the MwdMngt(24) Context per MMU.
Register EMWDFBMU is a peg register that records the number of fallbacks

to the various MwdMngt(24) context versions performed by the DMS-MSC/
tuples in this register and the tuples in EMWDRQMU, which records the
number of fall backs from the MwdMngt(24) context versions, the operator
gets an indication of the MwdMngt(24) context versions provisioned in the
network.
Release history
Register EMWDFBMU was created in GSM11.
EMWDRQMU
Validation formula
EMWDFBMU.
On the DMS-MSC/Call Server, the number of pegs to register EMWDFBMU

is less than or equal to the number of pegs to register EMWDRQMU.
Associated logs
None
EXT register
None
Register EMWDRQMU 3
Number of Fallbacks from the MwdMngt(24) Context per MMU.
Register EMWDRQMU is a peg register that records the number of fall backs
from the various MwdMngt(24) context versions performed by the DMS-
the tuples in this register and the tuples in EMWDFBMUEMWDFBMU,
which record the number of fall backs to the MwdMngt(24) context versions,
the operator gets an indication of the MwdMngt(24) context versions

3-150 OM groups: E
Release history
Register EMWDRQMU was created in GSM11.
EMWDFBMU
Validation formula
EMWDRQMU.
On the DMS-MSC/Call Server, the number of pegs to register EMWDRQMU

is greater than or equal to the number of pegs to register EMWDFBMU.
Associated logs
None
EXT register
None
Register ESMAFBMU 3
Number of Fallbacks to the ShortMsgAlert(23) Context per MMU.
Register ESMAFBMU is a peg register that records the number of fallbacks

to the various ShortMsgAlert(23) context versions performed by the DMS-
this register and the tuples in ESMARQMU, which records the number of fall
backs from the ShortMsgAlert(23) context versions, the operator gets an
network.
Release history
Register ESMAFBMU was created in GSM11.
Associated register
ESMARQMU
Validation formula
On the DMS-HLR, the number of pegs to register ESMAFBMU is less than
or equal to the number of pegs to register ESMARQMU.
Associated logs
None

OM groups: E 3-151
EXT register
ESMAF2MU
Register ESMARQMU 3
Number of Fallbacks from the ShortMsgAlert(23) Context per MMU.
Register ESMARQMU is a peg register that records the number of fall backs
from the various ShortMsgAlert(23) context versions performed by the DMS-
this register and the tuples in ESMAFBMU, which record the number of fall
backs to the ShortMsgAlert(23) context versions, the operator gets an
network.
Release history
Register ESMARQMU was created in GSM11.
Associated register
ESMAFBMU
Validation formula
On the DMS-HLR, the number of pegs to register ESMARQMU is greater
than or equal to the number of pegs to register ESMAFBMU.
Associated logs
None
EXT register
ESMARMU2
Register ESMOFBMU 3
Number of Fallbacks to the ShortMsgRelay(21) and ShortMsgRelay (21)
Context per MMU.
ESMOFBMU records the number of fall backs to ShortMsgRelay(21)

version1(1) and ShortMsgMO-Relay(21) context versions experienced by the
DMS-MSC/Call Server. The fallbacks to each version of ShortMsgMO-
Relay(21) context and ShortMsgRelay(21) version1(1) are recorded on a per
tuple basis. By examining this register and ESMORQMU, which records the
number of fall backs from the ShortMsgMO-Relay(21) context, the operator
gets an indication of the ShortMsgMO-Relay(21) and ShortMsgRelay(21)
Release history
Register ESMOFBMU was created in GSM11.

3-152 OM groups: E
Associated register
ESMORQMU
GMFSMREQ and GMFSMRES from group GMAPSMS.
Validation formula
On the DMS-MSC/Call Server, the number of pegs to registers GMFSMREQ
from group GMAPSMS is greater or equal to the sum of the number of pegs
to registers GMFSMRES from group GMAPSMS and ESMOFBMU.
On the DMS-MSC/Call Server, the number of pegs to register ESMOFBMU

is less than or equal to the number of pegs to register ESMORQMU.
Associated logs
None
EXT register
None
Register ESMORQMU 3
Number of Fallbacks from ShortMsgMO-Relay(21) and ShortMsgRelay(21)
Contexts per MMU.
Register ESMORQMU is a peg register that records the number of fall backs
from the various ShortMsgMO-Relay(21) context versions performed by the
examining the tuples in this register and the tuples in ETSIMOFB, which
records the number of fall backs to the ShortMsgMO-Relay(21) context
versions and to ShortMsgRelay(21) version1(1), the operator gets an
indication of the ShortMsgRelay(21) and ShortMsgRelay(21) context
Release history
Register ESMORQMU was created in GSM11.
ESMOFBMU
GMFSMREQ and GMFSMRES from Group GMAPSMS.
Validation formula
On the DMS-MSC/Call Server, the number of pegs to GMFSMREQ from
group GMAPSMS is greater than or equal to the sum of the number of pegs to
GMFSMRES from group GMAPSMS and ESMORQMU.

OM groups: E 3-153
On the DMS-MSC/Call Server, the number of pegs to register ESMORQMU

is greater than or equal to the number of pegs to register ESMOFBMU.
Associated logs
None
EXT register
None

3-154 OM groups: E
ETSMSRMU
ETSI Short Message Service Dialogue Responder on the MMU 3
For a dialogue responder, ETSMSRMU measures the number of fall backs to
and from the Short Messages Services related application context versions
per MMU. The fields represent the various application contexts, and the
tuples represent the application context versions.
Registers
The following ETSMSRMU registers may be displayed:
ESGWRQMU ESGWRMU2 ESGWFBMU ESGWFMU2
ESMORQMU ESMOFBMU ESMARQMU EMWDRQMU
EMWDRMU2 EMWDFBMU EMWDFMU2 ESMTRQMU
ESMTFBMU
Release history
ETSMSRMU was created in GSM11.
Group structure
ETSISMSR
Associated products
MMU
Validation Formula

OM groups: E 3-155
Register ESGWRQMU 3
ETSI Dialogue Responder ShortMsgGateway (20) contact versions per
MMU.
Register ESGWRQMU is a peg register that records the number of fall backs
from the various ShortMsgGateway(20) context versions recommended by
tuples in this register and the tuples in ESGWFBMU, which records the
number of fall backs to the ShortMsgGateway(20) context versions, the
Release history
Register ESGWRQMU was created in GSM11.
Associated register
ESGWFBMU
Validation formula
On the DMS-HLR, the number of pegs to register ESGWRQMU is greater
than or equal to the number of pegs to register ESGWFBMU.
Associated logs
None
EXT register
ESGWRMU2
Register ESGWFBMU 3
ETSI Dialogue Responder ShortMsgGateway(20) contact versions -Fallbacks
per MMU.
Register ESGWFBMU is a peg register that records the number of fallbacks

to the various ShortMsgGateway(20) context versions recommended by the
tuples in this register and the tuples in ESGWRQMU, which records the
number of fall backs from the ShortMsgGateway(20) context versions, the
Release history
Register ESGWFBMU was created in GSM11.
Associated register
ESGWRQMU

3-156 OM groups: E
Validation formula
On the DMS-HLR, the number of pegs to register ESGWFBMU is less than
or equal to the number of pegs to register ESGWRQMU.
Associated logs
None
EXT register
ESGWFMU2
Register ESMORQMU 3
ETSI Dialogue Responder ShortMsgMo-Relay(21) Request per MMU.
Register ESMORQMU is a peg register that records the number of fall backs
from the various ShortMsgMO-Relay(21) context versions recommended by
the DMS-MSC/Call Server. Tuples of this register represent versions.
Release history
Register ESMORQMU was created in GSM11.
Associated register
ESMOFBMU
Validation formula
The number of pegs to register ESMORQMU is greater than or equal to the
number of pegs to register ESMOFBMU.
Associated logs
None
EXT register
None
Register ESMOFBMU 3
ETSI Dialogue Responder ShortMsgMoRelay(21)-Fallback per MMU.
Register ESMOFBMU is a peg register that records the number of fall backs
to ShortMsgRelay(21) version1(1) and ShortMsgMO-Relay(21) context
versions recommended by the DMS-MSC/Call Server. The fallbacks to
ShortMsgRelay(21) version1(1) and each version of ShortMsgMO-Relay(21)
context are recorded on a per tuple basis.

OM groups: E 3-157
By examining this register and ESMTRQMU, which records the number of

fall backs from the ShortMsgMT-Relay(25) context, the operator gets an
indication of the ShortMsgMT-Relay(25) and ShortMsgRelay(21) context
Release history
Register ESMOFBMU was created in GSM11.
Associated register
ESMTRQMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ESMOFBMU
is less than or equal to the number of pegs to register ESMTRQMU.
Associated logs
None
EXT register
None
Register ESMARQMU 3
ETSI Dialogue Responder ShortMsgAlert Request per MMU.
Register ESMARQMU is a peg register that records the number of fall backs
from the various ShortMsgAlert(23) context versions recommended by the
DMS-MSC/Call Server. Tuples of this register represent versions.
Release history
Register ESMARQMU was created in GSM11.
Associated register
None
Validation formula
None
Associated logs
None
EXT register
None

3-158 OM groups: E
Register EMWDRQMU 3
ETSI Dialogue Responder ShortMsgMwdMngt Request per MMU.
Register EMWDRQMU is a peg register that records the number of fall backs
from the various MwdMngt(24) context versions recommended by the DMS-
this register and the tuples in EMWDFBMU, which record the number of fall
backs to the MwdMngt(24) context versions, the operator gets an indication
of the MwdMngt(24) context versions provisioned in the network.
Release history
Register EMWDRQMU was created in GSM11.
Associated register
EMWDFBMU
Validation formula
On the DMS-HLR, the number of pegs to register EMWDRQMU is greater
than or equal to the number of pegs to register EMWDFBMU.
Associated logs
None
EXT register
EMWDRMU2
Register EMWDFBMU 3
ETSI Dialogue Responder ShortMsgMwdMngt-Fallback per MMU.
Register EMWDFBMU is a peg register that records the number of fallbacks

to the various MwdMngt(24) context versions recommended by the DMS-
this register and the tuples in EMWDRQMU, which records the number of
fall backs from the MwdMngt(24) context versions, the operator gets an
indication of the MwdMngt(24) context versions provisioned in the network.
Release history
Register EMWDFBMU was created in GSM11.
Associated register
EMWDRQMU
Validation formula
On the DMS-HLR, the number of pegs to register EMWDFBMU is less than
or equal to the number of pegs to EMWDRQMU.

OM groups: E 3-159
Associated logs
None
EXT register
EMWDFMU2
Register ESMTRQMU 3
ETSI Dialogue Responder ShortMsgMt Request per MMU.
Register ESMTRQMU is a peg register that records the number of fall backs
from the various ShortMsgMT-Relay(25) context versions recommended by
the DMS-MSC/Call Server. Note that the fall back for ShortMsgMT-
Relay(25) version2(2) is ShortMsgRelay(21) version1(1).
By examining tuples in this register, tuples in ESMTFBMU, and the version1

tuple in ETRSMRFB, the operator gets an indication of the Short Message
Mobile Termination context versions provisioned in the network.
Release history
Register ESMTRQMU was created in GSM11.
Associated register
ESMTFBMU and ESMOFBMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ESMTRQMU
is greater than or equal to the number of pegs to register ESMTFBMU and the
version1 tuple of ESMOFBMU.
Associated logs
None
EXT register
None
Register ESMTFBMU 3
ETSI Dialogue Responder ShortMsgMt-Fallback per MMU.
Register ESMTFBMU is a peg register that records the number of fall backs
to the various ShortMsgMT-Relay(25) context versions recommended by the
examining the tuples in this register and the tuples in ESMTRQMU, which
records the number of fall backs from the ShortMsgMT-Relay(25) context
versions, the operator gets an indication of the ShortMsgMT-Relay(25)

3-160 OM groups: E
Release history
Register ESMTFBMU was created in GSM11.
Associated register
ESMTRQMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ESMTFBMU
is less than or equal to the number of pegs to register ESMTRQMU.
Associated logs
None

OM groups: E 3-161
ETSSIMMU
ETSI Supplementary Services Dialogue Initiator on the MMU 3
For a dialogue initiator, ETSSIMMU measures the number of fall backs to
and from the Supplementary Services related application context versions and
the number of fall backs to the Supplementary Services related application
context versions per MMU. The fields represent the various application
contexts, and the tuples represent the application context versions.
Registers
The following ETSSIMMU registers may be displayed:
ENSSRQMU ENSSFBMU ENUSRQMU ENUSRMU2
ENUSFBMU ENUSFMU2 EMUSRQMU EMUSFBMU
Release history
ETSSIMMU was created with GSM11.
Group structure
ETSISSI
Associated products
MMU
Validation Formula
Register EMUSFBMUU 3
Number of Fallbacks to the NetworkUnstructuredSs(19) Context per MMU.

3-162 OM groups: E
Register EMUSFBMUU is a peg register that records the number of fallbacks

to the various mobile initiated NetworkUnstructuredSS(19) context versions
performed by the DMS-MSC/Call Server. Tuples of this register represent
EMUSRQMU, which records the number of fall backs from the mobile
indication of the mobile initiated NetworkUnstructuredSs(19) context
Release history
Register EMUSFBMUU was created in GSM11.
Associated register
EMUSRQMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register EMUSFBMU
is less than or equal to the number of pegs to register EMUSRQMU.
Associated logs
None
EXT register
None
Register EMUSRQMU 3
Number of Fallbacks from NetworkUnstructuredSs(19) Context per MMU.
Register EMUSRQMU is a peg register that records the number of fall backs
versions performed by the DMS-MSC/Call Server. Note that the fall back for
mobile initiated NetworkUnstructuredSs(19) version2(2) is
By examining tuples in this register, tuples in EMUSFBMU, and the version1

tuple in ENSSFBMU, the operator gets an indication of the unstructured SS
Release history
Register EMUSRQMU was created in GSM11.
Associated register
EMUSFBMU and ENSSFBMU

OM groups: E 3-163
Validation formula
Not applicable on the DMS-MSC/Call Server because Mobile Initiated
UnstructuredSS has no Phase1 implementation.

the number of pegs to register EMUSRQMU will be greater or equal to the
number of pegs to register EMUSFBMU and the version1 tuple of
ENSSFBMU.
Associated logs
None
EXT register
None
Register ENSSFBMU 3
Number of Fallbacks to NetworkFunctionalSs(18) Context per MMU.
Register ENSSFBMU is a peg register that records the number of fall backs
to the various NetworkFunctionalSs(18) context versions performed by the
DMS-MSC/Call Server. Note that NetworkFunctionalSs(18) version1(1) is
the fall back for network initiated NetworkUnstructuredSs(19) version2(2).
By examining tuples in this register, the version2 tuple in ENUSRQMU, and

tuples in ENSSRQMU, the operator gets an indication of the structured SS
Release history
Register ENSSFBMU was created in GSM11.
Associated register
ENSSRQMU, ENUSRQMU, EMUSRQMU

Validation formula
On the DMS-MSC/Call Server, the number of pegs to REQ registers from
group GMAPSS is greater or equal to the sum of the number of pegs to the
RES registers from group GMAPSS and ENSSFBMU.

number of pegs to register ENSSRQMU and the number of pegs to register
ENSSFBMU because UnstructuredSS context may fall back to

3-164 OM groups: E
Associated logs
None
EXT register
None
Register ENSSRQMU 3
Number of FallBacks from NetworkFunctionalSs(18) Context per MMU.
Register ENSSRQMU is a peg register that records the number of fall backs
from the various NetworkFunctionalSs(18) context versions performed by the
examining the tuples in this register and the tuples in ENSSFBMU, which
records the number of fall backs to the NetworkFunctionalSs(18) context
versions, the operator gets an indication of the NetworkFunctionalSs(18)
Release history
Register ENSSRQMU was created in GSM11.
ENSSFBMU

Validation formula
On the DMS-MSC/Call Server, the number of pegs to the REQ registers from
group GMAPSS is greater than or equal to the sum of the number of pegs to
the RES registers from group GMAPMMGT and ENSSRQMU.

number of pegs to register ENSSRQMU and the number of pegs to register
ENSSFBMU because UnstructuredSS context may fall back to
Associated logs
None
EXT register
None
Register ENUSFBMU 3

OM groups: E 3-165
Register ENUSFBMU is a peg register that records the number of fallbacks to

examining the tuples in this register and the tuples in ENUSRQMU, which
records the number of fall backs from the network initiated
of the network initiated NetworkUnstructuredSs(19) context versions
Release history
Register ENUSFBMU was created in GSM11.
Associated register
ENUSRQMU
Validation formula
On the DMS-HLR, the number of pegs to register ENUSFBMU is less than or
equal to the number of pegs to register ENUSRQMU.
Associated logs
None
EXT register
ENUSFMU2
Register ENUSRQMU 3
Register ENUSRQMU is a peg register that records the number of fall backs
versions performed by the DMS-HLR. Note that the fall back for network
By examining tuples in this register, tuples in ENUSFBMU, and the version1

Release history
Register ENUSRQMU was created in GSM11.
Associated register
ENUSFBMU

3-166 OM groups: E
Validation formula
Not applicable on the DMS-HLR because Network Initiated UnstructuredSS
has no PhaseI implementation.

the number of pegs to register ENUSRQMU will be greater or equal to the
number of pegs to register ENUSFBMU.
Associated logs
None
EXT register
ENUSRMU2

OM groups: E 3-167
ETSSRMMU
ETSI Supplementary Services Dialogue Responder on the MMU 3
For a dialogue responder, ETSSRMMU measures the number of fall backs to
and from the Supplementary Services related application context versions and
the number of fall backs to the Supplementary Services related application
context versions per MMU. The fields represent the various application
contexts, and the tuples represent the application context versions.
Registers
The following ETSSRMMU registers may be displayed:
ENSSRQMU ENSSRMU2 ENSSFBMU ENSSFMU2
ENUSRQMU ENUSFBMU EMUSRQMU EMUSRMU2
EMUSFBMU EMUSFMU2
Release history
ETSSRMMU was created in GSM11.
Group structure
ETSISSR
Associated products
MMU
Validation Formula

3-168 OM groups: E
Register ENSSRQMU 3
Number of Fallbacks from NetworkFunctionalSs(18) Context per MMU.
Register ENSSRQMU is a peg register that records the number of fall backs
from the various NetworkFunctionalSs(18) context versions recommended by
tuples in this register and the tuples in ENSSFBMU, which records the
number of fall backs to the NetworkFunctionalSs(18) context versions, the
operator gets an indication of the NetworkFunctionalSs(18) context versions
Release history
Register ENSSRQMU was created in GSM11.
Associated register
ENSSFBMU
Validation formula
On the DMS-HLR, the number of pegs to register ENSSRQMU is greater or
equal to the number of pegs to register ENSSFBMU.
Associated logs
None
EXT register
ENSSRMU2
Register ENSSFBMU 3
Number of Fallbacks to NetworkFunctionalSs(18) Context per MMU.
Register ENSSFBMU is a peg register that records the number of fall backs
to the various NetworkFunctionalSs(18) context versions recommended by
the DMS-HLR. Note that NetworkFunctionalSs(18) version1(1) is the fall
back for network initiated NetworkUnstructuredSs(19) version2(2).
By examining tuples in this register, the version2 tuple in ENUSRQMU, and

tuples in ENSSRQMU, the operator gets an indication of the structured SS
Release history
Register ENSSFBMU was created in GSM11.
Associated register
ENSSRQMU

OM groups: E 3-169
Validation formula
On the DMS-HLR, the number of pegs to register ENSSFBMU is less than or
equal to the number of pegs to register ENSSRQMU.
Associated logs
None
EXT register
ENSSFMU2
Register ENUSRQMU 3
Number of Fallbacks to NetworkUnstructuredSs(19) Context per MMU.
Register ENUSRQMU is a peg register that records the number of fall backs
versions recommended by the DMS-MSC/Call Server. Note that the fall back
for network initiated NetworkUnstructuredSs(19) version2(2) is
By examining tuples in this register, tuples in ENUSFBMU, and the version1

Release history
Register ENUSRQMU was created in GSM11.
Associated register
ENUSFBMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ENUSRQMU
is greater than or equal to the number of pegs to register ENUSFBMU.
Associated logs
None
EXT register
ENUSRMU2
Register ENUSFBMU 3
Register ENUSFBMU is a peg register that records the number of fallbacks to

recommended by the DMS-MSC/Call Server. Tuples of this register represent

3-170 OM groups: E

ETINUSRQ, which records the number of fall backs from the network
indication of the network initiated NetworkUnstructuredSs(19) context
Release history
Register ENUSFBMU was created in GSM11.
Associated register
ENUSRQMU
Validation formula
On the DMS-MSC/Call Server, the number of pegs to register ENUSFBMU
is less than or equal to the number of pegs to register ENUSRQMU.
Associated logs
None
EXT register
ENUSFMU2
Register EMUSRQMU 3
Register EMUSRQMU is a peg register that records the number of fall backs
versions performed by the DMS-HLR. Note that the fall back for mobile
By examining tuples in this register, tuples in EMUSFBMU, and the version1

Release history
Register EMUSRQMU was created in GSM11.
Associated register
EMUSFBMU and ENSSFBMU
Validation formula
On the DMS-HLR, the number of pegs to register EMUSRQMU is greater
than or equal to the number of pegs to registers EMUSFBMU and the
version1 tuple of ENSSFBMU.

OM groups: E 3-171
Associated logs
None
EXT register
EMUSRMU2
Register EMUSFBMU 3
Number of fallbacks to the various mobile initiated
NetworkUnstructuredSS(19) context per MMU.
Register EMUSFBMU is a peg register that records the number of fallbacks

to the various mobile initiated NetworkUnstructuredSS(19) context versions
examining the tuples in this register and the tuples in EMUSRQMU, which
record the number of fall backs from the mobile initiated
of the mobile initiated NetworkUnstructuredSs(19) context versions
Release history
Register EMUSFBMU was created in GSM11.
Register type
Peg
Associated register
None
Validation formula
On the DMS-HLR, the number of pegs to register EMUSFBMU is less than
or equal to the number of pegs to register EMUSRQMU.
Associated logs
None
EXT register
EMUSFMU2

3-172 OM groups: E
EVGCS
Emergency Voice Group Call Service 3
The Emergency Voice Group Call Service (EVGCS) contains registers that
count the number of Emergency VGCS calls.
This OM group provides information specific to GSM-Railways

functionality.
Registers
EVGCS registers may be displayed at the DMS MAP as follows:
EVGCSSS EVGCSSS2 EVGCSDI EVGCSDI2
Release history
EVGCS was made available in GSMR02.
Group structure
Number of Tuples: 1
Key field: None
Info field: None
None
Associated products
None
Validation formula
None
Register EVGCSSS 3
Emergency VGCS Service Subscribers
Register EVGCSSS is a peg register that counts the Emergency VGCS calls
originated by a service subscriber.

OM groups: E 3-173
Release history
EVGCSSS was made available in GSMR02.
None
Associated logs
None
Extension register
EVGCSSS2
Validation formula
None
Register EVGCSDI 3
Emergency VGCS Dispatcher
Register EVGCSDI is a peg register that counts the Emergency VGCS calls
originated by a dispatcher.
Release history
EVGCSDI was made available in GSMR02.
None
Associated logs
None
Extension register
EVGCSDI2
Validation formula
None

3-174 OM groups: E
EXHOCA
MSC External Handover Cause 3
The MSC External Handover Cause group contains registers that measure
activities related to external handover cause reasons.
In GSM15, support for Adaptive Multi-Rate (AMR) over A-interface is

added. The OM pegs Handover by its A-interface cause value. AMR
introduces a few handover types which are mapped to three (3) A-interface
causes: uplink quality, downlink quality, and traffic.
Registers
EXHOCA registers may be displayed at the DMS MAP as follows:
HRCA02 HRCA022 HRCA03 HRCA032
HRCA08 HRCA082 HRCA0C HRCA0C2
HRCA0D HRCA0D2 HRCA31 HRCA312
HRCA32 HRCA322 HRCAXX HRCAXX2
Release history
EXHOCA was created in GSM07 and modified in GSM15.
Group structure
Number of Tuples: Same as the number of the trunk group.
Key field: CLLI
Info field: TRKDIR, NCCT, NWNCCT, and CICPOOL
This group is associated with MSCHO. The GHOREQD register in the OM
group MSCHO is pegged when the Handover Required message is first
received by the MSC/Call Server. The registers in EXHOCA are pegged after
the handover type has been determined.

OM groups: E 3-175
Associated products
DMS-MSC/Call Server
Validation formula
The sum of counts in all of the registers in the OM group EXHOCA should be
less than or equal to the count that indicates the total number of Handover
Required messages received from the BSS.
[(65535 * HRCA022)+HRCA02] + [(65535 * HRCA032)+HRCA03]
+[(65535 * HRCA042)+HRCA04] + [(65535 * HRCA052)+HRCA05]
+[(65535 * HRCA062)+HRCA06] + [(65535 * HRCA072)+HRCA07]
+[(65535 * HRCA082)+HRCA08] + [(65535 * HRCA0c2)+HRCA0c]
+[(65535 * HRCA0d2)+HRCA0d] + [(65535 * HRCA312)+HRCA31]
+[(65535 * HRCA322)+HRCA32] + [(65535 * HRCAxx2)+HRCAxx]
<= GHOREQD
Register HRCA02 3
External Handover Cause 02
Register HRCA02 is a peg register that records the number of attempted
MSC/Call Server controlled handovers due to cause of Uplink quality (02).
Release history
HRCA02 was created in GSM07.
None
Associated logs
None
Extension register
HRCA022
Validation formula
None

3-176 OM groups: E
Register HRCA03 3
MSC/Call Server controlled handovers due to the cause of Uplink strength
(03).
Release history
None
Associated logs
None
Extension register
HRCA032
Validation formula
None
Register HRCA04 3
MSC/Call Server controlled handovers due to cause of Downlink quality
(04).
Release history
None
Associated logs
None
Extension register
HRCA042
Validation formula
None

OM groups: E 3-177
Register HRCA05 3
MSC/Call Server controlled handovers due to the cause of Downlink strength
(05).
Release history
None
Associated logs
None
Extension register
HRCA052
Validation formula
None
Register HRCA06 3
MSC/Call Server controlled handovers due to cause of Distance (06).
Release history
None
Associated logs
None
Extension register
HRCA062
Validation formula
None

3-178 OM groups: E
Register HRCA07 3
MSC/Call Server controlled handovers due to the cause of O and M
intervention (07).
Release history
None
Associated logs
None
Extension register
HRCA072
Validation formula
None
Register HRCA08 3
MSC/Call Server controlled handovers due to cause of Response to MSC/
Call Server invocation (08).
Release history
None
Associated logs
None
Extension register
HRCA082
Validation formula
None

OM groups: E 3-179
Register HRCA0C 3
External Handover Cause 0C
Register HRCA0C is a peg register that records the number of attempted
MSC/Call Server controlled handovers due to the cause of Better Cell (0C).
Release history
HRCA0C was created in GSM07.
None
Associated logs
None
Extension register
HRCA0C2
Validation formula
None
Register HRCA0D 3
External Handover Cause 0D
Register HRCA0D is a peg register that records the number of attempted
MSC/Call Server controlled handovers due to cause of Directed Retry (0D).
Release history
HRCA0D was created in GSM07.
None
Associated logs
None
Extension register
HRCAOD2
Validation formula
None
Register HRCAXX 3
External Handover with any other Cause
Register HRCAXX is a peg register that records the number of attempted
MSC/Call Server controlled handovers due to any other cause.

3-180 OM groups: E
Release history
HRCAXX was created in GSM07.
None
Associated logs
None
Extension register
HRCAXX2
Validation formula
None
Register HRCA31 3
This register is used to records the number of attempted MSC/Call Server
controlled intra-MSC handovers with cause of ‘Circuit pool mismatch’
(0x31).
Release history
None
Associated logs
None
Extension register
HRCA312
Validation formula
None
Register HRCA32 3

controlled intra-MSC handovers with cause of ‘Switch circuit pool’ (0x32).

OM groups: E 3-181
Release history
None
Associated logs
None
Extension register
HRCA322
Validation formula
None

3-182 OM groups: E
EXHOCAMU
MSC External Handover Cause on the MMU 3
The MSC External Handover Cause group contains registers that measure
activities related to external handover cause reasons in the MMU.
Registers
EXHOCAMU registers may be displayed at the DMS MAP as follows:
HRCA02MU HRCA02U2 HRCA03MU HRCA03U2
HRCA08MU HRCA08U2 HRCA0CMU HRCA0CU2
HRCA0DMU HRCA0DU2 HRCA31MU HRCA31U2
HRCA32MU HRCA32U2 HRCAXXMU HRCAXXU2
Release history
EXHOCAMU was created in GSM11.
Group structure
EXHOCA
Associated products
MMU, DMS-MSC/Call Server
Validation formula

OM groups: E 3-183
Register HRCA02MU 3
External Handover Cause 02 per MMU
Register HRCA02MU is a peg register that records the number of attempted
MSC/Call Server controlled handovers due to cause of Uplink quality (02).
Release history
HRCA02MU was created in GSM11.
None
Associated logs
None
Extension register
HRCAO2U2
Validation formula
None
Register HRCA03MU 3
MSC/Call Server controlled handovers due to the cause of Uplink strength
(03).
Release history
None
Associated logs
None
Extension register
HRCAO3U2
Validation formula
None

3-184 OM groups: E
Register HRCA04MU 3
MSC/Call Server controlled handovers due to cause of Downlink quality
(04).
Release history
None
Associated logs
None
Extension register
HRCAO4U2
Validation formula
None
Register HRCA05MU 3
MSC/Call Server controlled handovers due to the cause of Downlink strength
(05).
Release history
None
Associated logs
None
Extension register
HRCAO5U2
Validation formula
None

OM groups: E 3-185
Register HRCA06MU 3
MSC/Call Server controlled handovers due to cause of Distance (06).
Release history
None
Associated logs
None
Extension register
HRCAO6U2
Validation formula
None
Register HRCA07MU 3
MSC/Call Server controlled handovers due to the cause of O and M
intervention (07).
Release history
None
Associated logs
None
Extension register
HRCAO7U2
Validation formula
None

3-186 OM groups: E
Register HRCA08MU 3
MSC/Call Server controlled handovers due to cause of Response to MSC/
Call Server invocation (08).
Release history
None
Associated logs
None
Extension register
HRCAO8U2
Validation formula
None
Register HRCA0CMU 3
External Handover Cause 0C per MMU
Register HRCA0CMU is a peg register that records the number of attempted
MSC/Call Server controlled handovers due to the cause of Better Cell (0C).
Release history
HRCA0CMU was created in GSM11.
None
Associated logs
None
Extension register
HRCAOCU2
Validation formula
None

OM groups: E 3-187
Register HRCA0DMU 3
External Handover Cause 0D per MMU
Register HRCA0DMU is a peg register that records the number of attempted
MSC/Call Server controlled handovers due to cause of Directed Retry (0D).
Release history
HRCA0DMU was created in GSM11.
None
Associated logs
None
Extension register
HRCAOD2
Validation formula
None
Register HRCAXXMU 3
External Handover with any other Cause per MMU
Register HRCAXXMU is a peg register that records the number of attempted
MSC/Call Server controlled handovers due to any other cause.
Release history
HRCAXXMU was created in GSM11.
None
Associated logs
None
Extension register
HRCAXXU2
Validation formula
None

3-188 OM groups: E
Register HRCA31MU 3
controlled intra-MSC handovers with cause of ‘Circuit pool mismatch’
(0x31).
Release history
None
Associated logs
None
Extension register
HRCA31U2
Validation formula
None
Register HRCA32MU 3

controlled intra-MSC handovers with cause of ‘Switch circuit pool’ (0x32).
Release history
None
Associated logs
None
Extension register
HRCA32MU
Validation formula
None

OM groups: E 3-189
EXT
Extension Blocks 3
The OM group, Extension blocks (EXT), keeps track of extension block
usage. For R4 BICN, two new extension blocks are defined. Their
EXT_FORMAT_CODE are H248_TRANSACTION_EXT and
H248_LARGE_TRANSACTION_EXT. These extension blocks store
incoming H.248 requests with multiple actions and outgoing H.248 replies
when ALF is ON.
Registers
EXT registers may be displayed at the DMS MAP as follows:
EXTSEIZ EXTOVFL EXTHI EXTSEIZ2
EXTHI2
Release history
EXT was made available in BCS35+. Modified in GSM06 and GSM17.
Group structure
Key Field: EXT_FORMAT_CODE
This feature introduces 2 new values for EXT_FORMAT_CODE -

H248_TRANSACTION_EXT and H248_LARGE_TRANSACTION_EXT.
A key field/EXT block has been added:

228 GSM_WB_SCCP_EXT_BLOCKS
Info Field: EXTINFO
Number of Tuples: One tuple per EXT_FORMAT_CODE
The data collected in EXT indicates the types of extension blocks that are
used most often and indicates extension blocks that are under provisioned or
over provisioned.
The following table lists EXT_FORMAT_CODEs and associated AUD logs

for the OM group EXT applicable to DMS-MSC/Call Server.

3-190 OM groups: E
Figure 3-1
TEXT_FORMAT_CODES for DMS-MSC/Call Server
Index EXT_FROMAT_CODE AUD log associated

with
EXT_FORMAT_CODE
116 GSM_MAP_MSC_EXT_BLK AUD584
117 GSM_MAP_VLR_EXT_BLK AUD585
119 TC_AP_COMPONENT_EXT_BLK AUD587
122 GSM_MESSAGE_BLOCKS AUD590
127 GSM_MAP_SCCP_Extension_Blo AUD595

cks
128 Handover_Parm_Extension_Block AUD596

s
129 PCS_1900_EXTENSION_BLOCK AUD597

S
140 GSM_MAP_IN1TF_EXT_BLK AUD606
146 MONFTR_EXT_BLOCK AUD614
150 GSM_MONCALL_EXT_BLOCK AUD618
155 GSM_INAP_EXT_BLK N/A
None
Associated products
DMS-MSC/Call Server, GSM IN (Integrated MSC/SSP)

OM groups: E 3-191
Validation formula
The number of GSM_MAP_IN1TF_EXT_BLKs is based upon the number of
Transaction IDs datafilled in table TCAPTRID for the IN1TF AE TCAP
Application (that is, entry SPARE1_TC_AP) multiplied by 2.
Register EXTHI 3
Extension Blocks High
Register EXTHI exists in the EXT OM Group and records the maximum
number of extension block in use during an OM transfer period.
Release history
EXTHI was made available in BCS35+, and modified in GSM17.
Register type
High Water Mark
None
Associated logs
None
Extension register
EXTHI2
Validation formula
None
Register EXTHI2 3
Extension register for extension block high
Register EXTHI2 exists in the EXT group and is an extension register for OM
register EXTHI.
Release history
EXTHI2 was made available in GSM17. .
Register type
High Water Mark
None
Associated logs
None

3-192 OM groups: E
Extension register
None
Validation formula
None
Register EXTOVFL 3
Extension Blocks Overflow
Register EXTOVFL exists in the EXT OM Group and is pegged when an
extension block cannot be seized.
Release history
EXTOVFL was made available in BCS35+, and modified in GSM17.
None
Associated logs
None
Extension register
None
Validation formula
None
Register EXTSEIZ 3
Extension Blocks Seized
Register EXTSEIZ exists in the EXT OM Group and is pegged every time an
extension block is seized.
Release history
EXTSEIZ was made available in BCS35+, and modified in GSM17.
None
Associated logs
None
Extension register
EXTSEIZ2

OM groups: E 3-193
Validation formula
None
Register EXTSEIZ2 3
Extesnion register for extension block seizure
Register EXTSEIZ2 exists in the EXT OM and is an extension register for the
EXTSEIZ register.
Release history
EXTSEIZ2 was made available in GSM17.
None
Associated logs
None
Extension register
None
Validation formula
None

3-194 OM groups: E

4-1
OM groups: F-GE 4
DMS-MSC/Call Server for GSM, whose names begin with “F” through those
whose names begin with “GE”.

4-2 OM groups: F-GE
FHUGAXBK
Feature Processing Framework Huge Auxiliary Blocks 4
The FPF Huge Auxiliary Blocks (FHUGAXBK) OM group monitors the use
of extension blocks. Extension blocks are auxiliary software resources that
are allocated to calls for purposes such as special billing records, data
extensions for operator services, and custom calling features. The primary
purpose of an extension block is to provide additional storage for data
associated with a call.
Registers
FHUGAXBK registers may be displayed at the DMS MAP as follows:
FHEXSZMU FHEXOVMU FHEXHIMU FHEXSZU2
FHEXHIU2
Release history
FHUGAXBK was created in GSM11.
Group structure
EXT
Associated products
MMU
Validation formula

OM groups: F-GE 4-3
Register FHEXSZMU 4
MMU.
Register FHEXSZMU is a peg register that counts the number of requests for
Release history
FHEXSZMU was created in GSM11.
None
Associated logs
None
Extension register
FHEXSZU2
Validation formula
None
Register FHEXOVMU 4
Register FHEXOVMU is a peg register that counts when a particular type of
Release history
FHEXOVMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register FHEXHIMU 4

4-4 OM groups: F-GE
Register FHEXHIMU is a peg register that counts the maximum number of

transfer per MMU.
Release history
FHEXHIMU was created in GSM11.
None
Associated logs
None
Extension register
FHEXHIU2
Validation formula
None

OM groups: F-GE 4-5
FLRGAXBK
Extension Blocks 4
The FLRGAXBK OM group monitors the use of extension blocks. Extension
Registers
FLRGAXBK registers may be displayed at the DMS MAP as follows:
FLEXSZMU FLEXOVMU FLEXHIMU FLEXSZU2
FLEXHIU2
Release history
FLRGAXBK was created in GSM11.
Group structure
EXT
Associated products
MMU
Validation formula
Register FLEXSZMU 4
Register FLEXSZMU is a peg register that counts the number of requests for

4-6 OM groups: F-GE
Release history
FLEXSZMU was created in GSM11.
None
Associated logs
None
Extension register
FLEXSZU2
Validation formula
None
Register FLEXOVMU 4
Register FLEXOVMU is a peg register that counts when a particular type of
Release history
FLEXOVMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register FLEXHIMU 4
Register FLEXHIMU is a peg register that counts the maximum number of

transfer per MMU.
Release history
FLEXHIMU was created in GSM11.

OM groups: F-GE 4-7
None
Associated logs
None
Extension register
FLEXHIU2
Validation formula
None

4-8 OM groups: F-GE
FMDMAXBK
Feature Processing Framework Medium Auxiliary Blocks 4
The FPF Medium Auxiliary Blocks (FMDMAXBK) OM group monitors the
use of extension blocks. Extension blocks are auxiliary software resources
that are allocated to calls for purposes such as special billing records, data
Registers
FMDMAXBK registers may be displayed at the DMS MAP as follows:
FMEXSZMU FMEXOVMU FMEXHIMU FMEXSZU2
FMEXHIU2
Release history
FMDMAXBK was created in GSM11.
Group structure
EXT
Associated products
MMU
Validation formula

OM groups: F-GE 4-9
Register FMEXSZMU 4
Register FMEXSZMU is a peg register that counts the number of requests for
Release history
FMEXSZMU was created in GSM11.
None
Associated logs
None
Extension register
FMEXSZU2
Validation formula
None
Register FMEXOVMU 4
Register FMEXOVMU is a peg register that counts when a particular type of
Release history
FMEXOVMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register FMEXHIMU 4
Register FMEXHIMU is a peg register that counts the maximum number of

transfer per MMU.

4-10 OM groups: F-GE
Release history
FMEXHIMU was created in GSM11.
None
Associated logs
None
Extension register
FMEXHIU2
Validation formula
None

OM groups: F-GE 4-11
FPDEVICE
File Processor Storage Device Activity Counts 4
This group counts the number of times that Each File Processor storage
device has entered various states as well as some usage indicators specifying
device activity. These registers can indicate the frequency of some error
conditions by recording the frequency of corresponding state changes.
Registers
The following FPDEVICE registers may be displayed at the DMS MAP:
FPDIP0EU FPDIP1EU FPDEVMB FPDEVMBU

FPDEVRB FPDEVRBU FPDEVNA FPDEVNAU
FPDEVIT FPDEVITU FPDEVSB FPDEVSBU
FPDEVRQ FPDEVNU FPDEVBWR FPDEVBRD
FPDEVUNR FPDEVREC FPDEVASN
Note: OM registers designated by ’*’ (asterisk) are not to be pegged in

BCS33.
Release history
FPDEVICE was created in BCS33.
Group structure
Number of tuples: 12 per FP, to a maximum of 100 FPs
Key field: FP0,FP1,FP2...FP99
Info field: SCSI 0,1 DEVICE 0-5
None
Validation formula
None
Associated products
None
Register FPDEVNU 4
File Processor Storage Device number of usage intervals in the last
transfer period
FPDEVNU is pegged every 10 seconds, when the usage scan process checks
the usage conditions for the FPDEVICE group of OM registers. This number

may differ from the expected number that would be calculated by dividing the
transfer period by 10 seconds. This difference is due to the time required to
transfer the OMs from the FP node to the CM.
Release history
FPDEVNU was created in BCS33.
Register type
Peg
None
Validation formalu
None
Associated logs
None
Extension register
None
Register FPDIP0EU 4
File Processor Device Interface Paddleboard for controller 0, enabled
usage
FPDIP0EU is pegged every 10 seconds, provided that the specified SCSI
device interface paddleboard (SDIP) on controller 0 is enabled. The purpose
of this value to track usage of the SDIPs in the File Processor system.
Release history
FPDIP0EU was created in BCS33.
Register type
Usage
FPDEVNU - The number of 10 second usage intervals checked in the last
transfer period.
The number of usage intervals or scan periods is necessary since it may differ
from the transfer period/10 seconds. This is due to the skew between the
nodes and OM transfer time.

Validation formalu
FPDEVNU * 10 seconds = Total time used to monitor usage in the last
transfer period.
FPDIP0EU * 10 seconds = Total time the SDIP was enabled in the last
transfer period.
FPDIP0EU / FPDEVNU = Ratio of time enabled to total time monitored in

the last transfer period
Associated logs
None
Extension register
None
Register FPDIP1EU 4
File Processor Device Interface Paddleboard for controller 1, enabled
usage
FPDIP1EU is pegged every 10 seconds, provided that the specified SCSI
device interface paddleboard (SDIP) on controller 1 is enabled. The purpose
of this value to track usage of the SDIPs in the File Processor system.
Release history
FPDIP1EU was created in BCS33.
Register type
Usage
transfer period.
Validation formula
transfer period.
FPDIP1EU * 10 seconds = Total time the SDIP was enabled in the last
transfer period.

FPDIP1EU / FPDEVNU = Ratio of time enabled to total time monitored in

Associated logs
None
Extension register
None
Register FPDEVMB 4
File Processor Storage Device Manual Busy state count
FPDEVMB is pegged every time the specified storage device enters the
manual busy state (MBSY). Since this state must be initiated from the
maintenance and administration position (MAP), it is simply an indication of
the number of times the device was taken out of service.
Release history
FPDEVMB was created in BCS33.
Register type
Peg
None
Validation formula
None
Associated logs
LOG NUMBER: FP 503
Extension register
None
Register FPDEVMBU 4
File Processor Storage Device Manual Busy state usage
FPDEVMBU is pegged every 10 seconds, provided that the specified storage
device is in the manual busy state (MBSY). Since this state must be initiated
from the maintenance and administration position (MAP), it is simply an
indication of the amount of time that the device was taken out of service.
Release history
FPDEVMBU was created in BCS33.

Register type
Usage
Associated register
transfer period.
Validation formula
transfer period.
FPDEVMBU * 10 seconds = Total time the Storage Device was MBSY in the
last transfer period.
FPDEVMBU / FPDEVNU = Ratio of time MBSY to total time as monitored

in the last transfer period.
Associated logs
None
Extension register
None
Register FPDEVRB 4
File Processor Storage Device Resource Busy state count
FPDEVRB is pegged every time the specified storage device enters the
resource busy state (RBSY). This state is an indication that the specified
device is capable of providing its intended service, however, a resource it
requires is out of service. For example, the node on which the device resides
is out of service, thus the device cannot provide complete service. While the
device is resource busy-only maintenance actions may be executed. If a
device is resource busy due to the node being manb, as opposed to sysb, no
system actions, such as audits, will be performed on the device during this
time. This is because a craftsperson requested the node be excluded from any
system actions when he manually busied the node. This count ,therefore,
indicates the number of times that the device was unable to provide normal
service due to a resource being out of service.
Release history
FPDEVRB was created in BCS33.

Register type
Peg
None
Validation formula
None
Associated logs
Log Number: FP 503
Extension register
None
Register FPDEVRBU 4
File Processor Storage Device Resource Busy state usage
FPDEVRBU is pegged every 10 seconds, provided that the specified storage
device is in the resource busy state (RBSY). It is, therefore, indication of the
amount of time that the device was taken out of service due to a resource
problem.
Release history
FPDEVRBU was created in BCS33.
Register type
Usage
transfer period.
Validation formula
transfer period.
FPDEVRBU * 10 seconds = Total time the Storage Device was RBSY in the
FPDEVRBU / FPDEVNU = Ratio of time RBSY to total time as monitored

in the last transfer period

Associated logs
None
Extension register
None
Register FPDEVNA 4
File Processor Storage Device Not Available state count
FPDEVNA is pegged every time the specified storage device enters the not
available state (NA). Since this state is an indication that the specified device,
while capable of providing its intended service, is isolated due to the link to
the device being out of service. That is, no communication, nor maintenance,
at the device level is possible while in the not available state. This count
provides the number of times that this communication has been lost.
Release history
FPDEVNA was created in BCS33.
Register type
Peg
None
Validation formula
None
Associated logs
Log Number: FP 503
Extension register
None
Register FPDEVNAU 4
File Processor Storage Device Not Available state usage
FPDEVNAU is pegged every 10 seconds, provided that the specified storage
device is in the not available state (NA). It is, therefore, an indication of the
amount of time that the device was taken out of service due to a problem with
the link to the device.
Release history
FPDEVNAU was created in BCS33.
Register type
Usage

transfer period.
Validation formula
transfer period.
FPDEVNAU * 10 seconds = Total time the Storage Device was NA in the last
transfer period.
FPDEVNAU / FPDEVNU = Ratio of time NA to total time as monitored in

Associated logs
None
Extension register
None
Register FPDEVIT 4
File Processor Storage Device In Service trouble state count
FPDEVIT is pegged every time the specified storage device enters the in
service trouble state (ISTB). This state is an indication that a particular device
is experiencing a non-critical fault. That is, applications may still use the
device, but it is limited. For instance, perhaps the minimum threshold of bad
blocks has been detected, however I/O is available because there are a
number of good blocks left for write operations; once the maximum threshold
of bad blocks is encountered, the device will become sysb. This count
provides the number of times that this non-critical state was entered.
Release history
FPDEVIT was created in BCS33.
Register type
Peg
Validation formula
None

Associated logs
Log Number: FP 503
Extension register
None
Register FPDEVITU 4
File Processor Storage Device In Service Trouble state usage
FPDEVITU is pegged every 10 seconds, provided that the specified storage
device is in the in service trouble state (ISTB). It is, therefore, an indication of
the amount of time that the device was in this none critical trouble state.
Release history
FPDEVITU was created in BCS33.
Register type
Usage
transfer period.
Validation formula
transfer period.
FPDEVITU * 10 seconds = Total time the Storage Device was ISTB in the
FPDEVITU / FPDEVNU = Ratio of time ISTB to total time as monitored in

the last transfer period.
Associated logs
None
Extension register
None

Register FPDEVSB 4
File Processor Storage Device System Busy state count
FPDEVSB is pegged every time the specified storage device enters the
system busy state (SYSB). This state is an indication that a particular device
has experienced a critical hardware fault, thus it is unavailable to users. While
in this state, system maintenance periodically attempts to return the faulty
device to service. A manual attempt to recover from the fault can also be
made by invoking the RTS command from the MAP. This count provides the
number of times that this critical state was entered.
Release history
FPDEVSB was created in BCS33.
Register type
Peg
None
Validation formula
None
Associated logs
Leg Number: FP 503
Extension register
None
Register FPDEVSBU 4
File Processor Storage Device System Busy state usage
FPDEVSBU is pegged every 10 seconds, provided that the specified storage
device is in the in system busy state (SYSB). It is, therefore, an indication of
the amount of time that the device was in this critical trouble state.
Release history
FPDEVSBU was created in BCS33.
Register type
Usage
transfer period.

Validation formula
transfer period.
FPDEVSBU * 10 seconds = Total time the Storage Device was SYS B in the
FPDEVSBU / FPDEVNU = Ratio of time SYSB to total time as monitored in

Associated logs
None
Extension register
None
Register FPDEVBW 4
File Processor Storage Device Blocks Written count
Note: Register FPDEVBW is not pegged in BCS33.
Register FPDEVBW is pegged with a count equal to the number of blocks

written to the specified storage device. This count can be used to determine
the block write traffic by taking into account the time interval over which the
count was accumulated.
Release history
FPDEVBW was created in BCS33.
Register type
Peg
transfer period.

Validation formula
transfer period.
FPDEVBW / FPDEVNU = Average number of blocks written per second, in

Associated logs
None
Extension register
None
Register FPDEVBR 4
File Processor Storage Device Blocks Read count
Note: Register FPDEVBW is not pegged in BCS33.
FPDEVBR is pegged with a count equal to the number of blocks read from
the specified storage device. This count can be used to determine the block
read traffic by taking into account the time interval over which the count was
accumulated.
Release history
FPDEVBR was created in BCS33.
Register type
Peg
transfer period.
Validation formula
transfer period.
FPDEVBR / FPDEVNU = Average number of blocks read per second, in the

Associated logs
None

Extension register
None
Register FPDEVRQ 4
File Processor Storage Device requests count
FPDEVRQ is pegged with a count equal to the number of requests made to
the specified storage device. This count can be used to determine the request
traffic by taking into account the time interval over which the count was
accumulated.
Release history
FPDEVRQ was created in BCS33.
Register type
Peg
transfer period.
Validation formula
transfer period.
FPDEVRQ / FPDEVNU = Average number of device requests per second, in

Associated logs
None
Extension register
None

FPFMSGS
FPF Messages OMs 4
The FPF Messages OMs group is created to display the per-node counts of
extension blocks. Extension blocks are auxiliary software resources that are
allocated to calls for purposes such as special billing records, data extensions
for operator services, and custom calling features. The primary purpose of an
extension block is to provide additional storage for data associated with a call.
Registers
The following FPFMSGS registers may be displayed at the DMS MAP:
FPFMSZMU FPFMOVMU FPFMHIMU FPFMSZU2

FPFMHIU2
Release history
FPFMSGS was created in GSM13.
Group structure
EXT
Validation formula
Associated products
MMU
Register FPFMSZMU 4
FPF Messages OMs
Register FPFMSZMU counts the number of requests for a particular type of

Release history
FPFMSZMU was created in GSM13.
EXTSIEZ
Extension register
FPFMSZU2
Validation formula
None
Register FPFMOVMU 4
FPF Messages OMs
Register FPFMOVMU counts when a particular type of extension block is
Release history
FPFMOVMU was created in GSM13.
EXTOVFL
Extension register
None
Validation formula
None
Register FPFMHIMU 4
FPF Messages OMs
Register FPFMHIMU counts the maximum number of extension blocks of
Release history
FPFMHIMU was created in GSM13.
EXTHI
Extension register
FPFMHIU2

Validation formula
None


FPXLMSGB
FPF Extra Large Message Blocks OMs 4
The FPF XL Message Blocks OMs group is created to display the per-node
counts for extension blocks. Extension blocks are auxiliary software
resources that are allocated to calls for purposes such as special billing
records, data extensions for operator services, and custom calling features.
The primary purpose of an extension block is to provide additional storage for
data associated with a call.
Registers
The following FPXLMSGB registers may be displayed at the DMS MAP:
FPXLSZMU FPXLOVMU FPXLHIMU FPXLSZU2

FPXLHIU2
Release history
FPXLMSGB was created in GSM13.
Group structure
EXT
Validation formula
Associated products
MMU

Register FPXLSZMU 4
FPF XL Message Blocks OMs
Register FPXLSZMU counts the number of requests for a particular type of
Release history
FPXLSZMU was created in GSM13.
EXTSIEZ
Extension register
FPXLSZU2
Validation formula
None
Register FPXLOVMU 4
Register FPXLOVMU counts when a particular type of extension block is not
available per MMU.
Release history
FPXLOVMU was created in GSM13.
EXTOVFL
Extension register
None
Validation formula
None
Register FPXLHIMU 4
Register FPXLHIMU counts the maximum number of extension blocks of
Release history
FPXLHIMU was created in GSM13.
EXTHI

Extension register
FPXLHIU2
Validation formula
None

FRDCNTL
Fraud Control 4
The OM group FRDCNTL provides service monitoring related to
supplementary services fraud control applications.
Registers
FRDCNTL registers may be displayed at the DMS MAP as follows:
CFEXHST GSSEXHST ECTEXHST
Release history
FRDCNTL was created in GSM09.
Group structure
Number of Tuples: 1
Key field: None
Info field: None
None
Validation Formula
None
Associated Products
None
Register GSSEXHST 4
GSSDB exhaustion
GSSEXHST is increased by 1, when an attempt is made to add a subscriber

entry beyond the allowed limit (1024).
Release history
GSSEXHST was made available in GSM09.
Register type
Peg

None
Associated logs
None
Extension register
GSSEXHST2
Validation formula
None
Register CFEXHST 4
Call forward exhaustion
CFEXHST is increased by 1, when an attempt to invoke CFU or CFNRC-
HLR while this activity is monitoring 600 subscribers already.
Release history
CFEXHST was made available in GSM09.
Register type
Peg
None
Associated logs
None
Extension register
CFEXHST2
Validation formula
If the number of subscribers that are controlled by this activity at any instance
exceeds 600, then CFEXHST register is pegged.
Register ECTEXHST 4
ECT exhaustion
ECTEXHST is increased by one, when an attempt to invoke ECT, while the
control is being applied to 600 subscribers involved in active ECT calls.
Release history
ECTEXHST was made available in GSM10.

Register type
Peg
None
Associated logs
None
Extension register
None
Validation formula
If the number of subscribers that are controlled by this activity at any instance
exceeds 600, then ECTEXHST register is pegged.

FSMLAXBK
Feature Processing Framework Small Auxiliary Blocks 4
The FPF Small Auxiliary Blocks (FSMLAXBK) OM group monitors the use
of extension blocks. Extension blocks are auxiliary software resources that
are allocated to calls for purposes such as special billing records, data
Registers
FSMLAXBK registers may be displayed at the DMS MAP as follows:
FSEXSZMU FSEXOVMU FSEXHIMU FSEXSZU2
FSEXHIU2
Release history
FSMLAXBK was created in GSM11.
Group structure
EXT
Associated products
MMU
Validation formula

Register FSEXSZMU 4
Register FSEXSZMU is a peg register that counts the number of requests for
Release history
FSEXSZMU was created in GSM11.
None
Associated logs
None
Extension register
FSEXSZU2
Validation formula
None
Register FSEXOVMU 4
Register FSEXOVMU is a peg register that counts when a particular type of
Release history
FSEXOVMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register FSEXHIMU 4
Register FSEXHIMU is a peg register that counts the maximum number of

transfer per MMU.

Release history
FSEXHIMU was created in GSM11.
None
Associated logs
None
Extension register
FSEXHIU2
Validation formula
None

FTROM
FTROM group is created as the platform for feature data block (FDB) high
water marks and seizures as separated by application type.
This OM group provides information to assist in switch resource engineering.

It is recommended that these OMs be used only for that purpose.
Registers
FTROM registers may be displayed at the DMS MAP as follows:
FTRHI FTRSEIZ FTRSEIZ2
Release history
FTROM was created in NA009.
Group structure
Key field: FTR_NAME describes FDB type. There are currently 511 defined
FDB application types that will be supported.
Info field: The info field contains the size of the FDB.
Possible sizes are SMALL, MEDIUM, LARGE, and X_LARGE, and
CRITICAL. The size information allows one to relate the FDB type to the
FDB size as stored in the EXT OM group under the corresponding tuples,
SMALL_FEATURE_DATA, MEDIUM_FEATURE_DATA,
LARGE_FEATURE_DATA, X_LARGE_FEATURE_DATA,
CRITICAL_FEATURE_DATA.
Number of Tuples: 511
EXT. EXT monitors the use of extension blocks.
Associated products
None
Validation formula
None
Register FTRHI 4
Maximum number of FDBs in simultaneous use
Register FTRHI controls the maximum number of simultaneously allocated
feature data blocks (FDBs) of a specific type during an OM transfer period.

At the beginning of each transfer period FTRHI is set to the number of FDBs
currently in use. Upon each FDB allocation, if the number of currently used
FDBs exceeds the value of FTRHI, FTRHI register is incremented. At any
time, for any given FDB type, an active FTRHI register reflects the maximum
number of simultaneously allocated FDBs from the beginning of the transfer
period to date. The holding register reflects the maximum number of
simultaneously allocated FDBs during the previous transfer period.
Release history
FTRHI was created in NA009.
Register type
High Water Mark
EXTHI
Associated logs
None
Validation formula
None
Extension register
None
Register FTRSEIZ 4
Number of successful FDB allocations
Register FTRSEIZ controls the number of successfully allocated feature data
blocks (HDBs) of a specific type.
It monitors the number of FDBs that are succesully allocated during the
transfer period. At the beginning of each transfer period, FTRSEIZ and
FTRSEIZ2 (extension) active registers are initialized to zero.The active
register is incremented when a request for a particular type of FDB is
successful.
Release history
FTRSEIZ was created in NA009.
Register type
Peg
EXTSEIZ, EXTSEIZ2

Associated logs
None
Validation formula
Total of all tuples with info field SMALL =
EXT::SEIZ for tuple SMALL_FEATURE_DATA
Total of all tuples with info field MEDIUM =

EXT::SEIZ for tuple MEDIUM_FEATURE_DATA
Total of all tuples with info field LARGE =

EXT::SEIZ for tuple LARGE_FEATURE_DATA
Total of all tuples with infor field X_LARGE =

EXT::SEIZ for tuple X_LARGE_FEATURE_DATA
Total of all tuples with info field CRITICAL =

EXT::SEIZ for tuple CRITICAL_FEATURE_DATA
Extension register
FTRSEIZ2


FXLGAXBK
Feature Processing Framework Extra large auxiliary block 4
The FPF Extra Large Auxiliary Block (FXLGAXBK) OM group monitors the
use of extension blocks. Extension blocks are auxiliary software resources
that are allocated to calls for purposes such as special billing records, data
Registers
FXLGAXBK registers may be displayed at the DMS MAP as follows:
FXEXSZMU FXEXOVMU FXEXHIMU FXEXSZU2
FXEXHIU2
Release history
FXLGAXBK was created in GSM11.
Group structure
EXT
Associated products
MMU
Validation formula

Register FXEXSZMU 4
Register FXEXSZMU is a peg register that counts the number of requests for
Release history
FXEXSZMU was created in GSM11.
None
Associated logs
None
Extension register
FXEXSZU2
Validation formula
None
Register FXEXOVMU 4
Register FXEXOVMU is a peg register that counts when a particular type of
Release history
FXEXOVMU was created in GSM11.
None
Associated logs
None
Extension register
None
Validation formula
None
Register FXEXHIMU 4
Register FXEXHIMU is a peg register that counts the maximum number of

transfer per MMU.

Release history
FXEXHIMU was created in GSM11.
None
Associated logs
None
Extension register
FXEXHIU2
Validation formula
None

G7SCCP
GSM CSS7 Signaling Connection Control Part 4
The GSM CCS7 Signaling Connection Control Part group displays the per-
node counts for the CM and LIU7s involved in the performance of the CCS7
signaling connection control part (SCCP). The register counts the number of
messages handled by the SCCP routing control (SCRC), messages that are
formatted into UDT user data, messages that arrive at the SCRC already
formatted, global title translations (GTT), messages that successfully reach
their destinations, and messages that fail to reach their destination.
The new GSM OM groups reside on the CM only. The OM data count from
the existing registers of the old OM groups pegged on the LIU7s are
transferred to the CM. On the CM, this data is pegged into the new registers
of the corresponding new OM groups.
This allows the user the flexibility to view the summary OMs during normal
operation and the detailed OMs on a per LIU7 basis when trying to identify
problem area during system recovery procedure.
Registers
G7SCCP registers can be displayed at the DMS Maintenance and
G7RTFALL G7RTFNTN G7RTFNTA G7RTFNWF
G7RTFNWC G7RTFSSF G7RTFSSC G7RTFUEQ
G7UDTTX G7UDTTX2 G7UDTRX G7UDTRX2
G7UDTSTX G7UDTSRX G7MSGHDL G7MSGHD2
G7MSGGT G7MSGGT2 G7CLS0TX G7CLS0T2
G7CLS0RX G7CLS0R2 G7CLS1TX G7CLS1T2
G7CLS1RX G7CLS1R2 G7SYNERR G7RTBKSS
G7LOCSS G7LOCSS2
Release history
G7SCCP was made available in GSM13 feature patch WSD02.

Group structure
Key field: None
Info field: This field contains the LIU7 number
Number of tuples: 1 per LIU7
Validation formula
Validation of this OM is performed with a count of Table GHLRSSOP. This
count can be a total count or a count on a per Supplementary Service basis.
The existing validation formula for C7SCCP on the peg register counts also
apply for G7SCCP.
Validation formula for the new OM groups on the per LIU7 basis is:
The sum of peg counts in the register for all available LIU7s is always smaller
or equal to the number of peg counts in the existing register of the
Associated OMs
C7SCCP
Register G7CLS0RX 4
GSM CCS7 connectionless class 0 received
Counts unitdata (UDT) and extended unitdata (XUDT) connectionless class 0
SCCP messages that are received by SCCP routing control (SCRC) from the
CCS7 network through the message transfer part (MTP).
Release history
G7CLS0RX was made available in GSM15.
Register Type
Peg
Associated Register
C7CLS0RX from C7SCCP OM group.
Validation Formula
Please refer to the original OM group “G7SCCP” on page 4-44.
Associated Logs
Log Number: Please refer to the original OM group “G7SCCP” on page 4-44.

EXT Register
G7CLS0R2
Register G7RTFALL 4
GSM CCS7 Route Failure All
Register G7RTFALL is a peg register that counts the number of Signaling
Connection Control Part (SCCP) routing control (SCRC) that cannot be
routed. This includes messages from the link through the message transfer
part (MTP) and from local subsystems through SCCP connectionless control
(SCLC). This register also includes messages that cannot be routed because
of incorrect encoding or unrecognized fields.
Release history
G7RTFALL was made available in GSM13 feature patch WSD02.
Register type
Peg
C7RTFALL from C7SCCP OM group.
Associated logs
None
Extension register
None
Validation formula
None
Register G7RTFNTN 4
GSM CCS7 Route Failure no translation of such nature
Register G7RTFNTN is a peg register that counts messages that SCCP
routing control receives. The system cannot route these messages because the
field value, No Translation for an Address of Such Nature, appear in the
CDPA of the message.
Release history
G7RTFNTN was made available in GSM13 feature patch WSD02.
Register type
Peg
C7RTFNTN from C7SCCP OM group.

Associated logs
None
Extension register
None
Validation formula
None
Register G7RTFNTA 4
GSM CCS7 Route Failure no translation for such address
Register G7RTFALL is a peg register that counts messages that SCCP routing
control receives. The system cannot route these messages because the field
value, No Translation for such address, appear in the CDPA of the message.
Release history
G7RTFNTA was made available in GSM13 feature patch WSD02.
Register type
Peg
C7RTFNTA from C7SCCP OM group.
Associated logs
None
Extension register
None
Validation formula
None
Register G7RTFNWF 4
GSM CCS7 Route Failure network failure
Register G7RTFNWF is a peg register that counts messages that SCCP
routing control receives. The system cannot route these messages because of
network failure.
Release history
G7RTFNWF was made available in GSM13 feature patch WSD02.
Register type
Peg

C7RTFNWF from C7SCCP OM group.
Associated logs
None
Extension register
None
Validation formula
None
Register G7RTFNWC 4
GSM CCS7 Route Failure network congestion
Register G7RTFNWC is a peg register that counts messages that SCCP
routing control receives. The system cannot route these messages because of
network congestion.
Release history
G7RTFNWC was made available in GSM13 feature patch WSD02.
Register type
Peg
C7RTFNWC from C7SCCP OM group.
Associated logs
None
Extension register
None
Validation formula
None
Register G7RTFSSC 4
GSM CCS7 Route Failure subsystem congestion
Register G7RTFSSC is a peg register that counts messages that SCCP routing
control receives. The system cannot route these messages because of
subsystem congestion.
Release history
G7RTFSSC was made available in GSM13 feature patch WSD02.

Register type
Peg
C7RTFSSC from C7SCCP OM group.
Associated logs
None
Extension register
None
Validation formula
None
Register G7RTFSSF 4
GSM CCS7 Route Failure subsystem failure
Register G7RTFSSF is a peg register that counts messages that SCCP routing
control receives. The system cannot route these messages because of
subsystem failure.
Release history
G7RTFSSF was made available in GSM13 feature patch WSD02.
Register type
Peg
C7RTFSSF from C7SCCP OM group.
Associated logs
None
Extension register
None
Validation formula
None
Register G7RTFUEQ 4
GSM CCS7 Route Failure user unequipped
Register G7RTFUEQ is a peg register that counts messages that SCCP
routing control receives. The system cannot route these messages because the
destination local subsystem is unknown.

Release history
G7RTFUEQ was made available in GSM13 feature patch WSD02.
Register type
Peg
C7RTFUEQ from C7SCCP OM group.
Associated logs
None
Extension register
None
Validation formula
None
Register G7UDTTX 4
GSM CCS7 UDT transmitted
Register G7UDTTX is a peg register that counts unidata (UDT)
connectionless SCCP messages that are transmitted. The system routes these
messages to the network through the message transfer part (MTP).
Release history
G7UDTTX was made available in GSM13 feature patch WSD02.
Register type
Peg
C7UDTTX from C7SCCP OM group.
Associated logs
None
Extension register
G7UDTTX2
Validation formula
None

Register G7UDTRX 4
GSM CCS7 UDT received
Register G7UDTRX is a peg register that counts unidata (UDT)
connectionless SCCP messages that are received. The system receives these
messages to the network through the message transfer part (MTP).
Release history
G7UDTRX was made available in GSM13 feature patch WSD02.
Register type
Peg
C7UDTRX from C7SCCP OM group.
Associated logs
None
Extension register
G7UDTRX2
Validation formula
None
Register G7UDTSTX 4
GSM CCS7 UDT send
Register G7UDTSRX is a peg register that counts unidata (UDT) service
connectionless SCCP messages. The SCRC receives these messages from the
CCS7 network through the message transfer part (MTP). UDTS messages
consist of a message that failed. This message has the return option and a
routing failure reason.
Release history
G7UDTSTX was made available in GSM13 feature patch WSD02.
Register type
Peg
C7UDTSTX from C7SCCP OM group.
Associated logs
None

Extension register
None
Validation formula
None
Register G7UDTSRX 4
GSM CCS7 UDT received
Register G7UDTSRX is a peg register that counts unidata (UDT) service
connectionless SCCP messages. The SCRC receives these messages from the
CCS7 network through the message transfer part (MTP). UDTS messages
consist of a message that failed. This message has the return option and a
routing failure reason.
Release history
G7UDTSRX was made available in GSM13 feature patch WSD02.
Register type
Peg
C7UDTSRX from C7SCCP OM group.
Associated logs
None
Extension register
none
Validation formula
None
Register G7MSGHDL 4
GSM CCS7 messages handled
Register G7MSGHDL is a peg register that counts messages handled by the
SCRC. Messages sent from local users through SCCP connectionless control
(SCLC) are included, as are messages sent from the CCS7 network through
the MTP.
Release history
G7MSGHDL was made available in GSM13 feature patch WSD02.
Register type
Peg

C7MSGHDL from C7SCCP OM group.
Associated logs
None
Extension register
G7MSGHD2
Validation formula
None
Register G7MSGGT 4
GSM CCS7 Global Title Translations
Register G7MSGHDL is a peg register that counts messages received by the
SCRC that require global title translation (GTT).
Release history
G7MSGHDL was made available in GSM13 feature patch WSD02.
Register type
Peg
C7MSGGT from C7SCCP OM group.
Associated logs
None
Extension register
G7MSGHD2
Validation formula
None
Register G7CLS0TX 4
GSM CCS7 connectionless class 0 transmitted
SCCP messages that are routed to the CCS7 network through the message
transfer part (MTP).
Release history
G7CLS0TX was made available in GSM13 feature patch WSD02.

Register type
Peg
C7CLS0TX from C7SCCP OM group.
Associated logs
None
Extension register
G7CLS0TX2
Validation formula
None
Register G7CLS1TX 4
GSM CCS7 connectionless class 1 transmitted
SCCP messages that are routed to the CCS7 network through the message
Release history
Register type
Peg
C7CLS1TX from C7SCCP OM group.
Associated logs
None
Extension register
G7CLS1TX2
Validation formula
None
Register G7CLS1RX 4
GSM CCS7 connectionless class 1 received

Release history
G7CLS1RX was made available in GSM13 feature patch WSD02.
Register type
Peg
C7CLS1RX from C7SCCP OM group.
Associated logs
None
Extension register
G7CLS1RX2
Validation formula
None
Register G7SYNERR 4
GSM CCS7 syntax errors
Counts messages received by SCCP routing control (SCRC) that cannot be
routed because of syntax errors in the called party address (CDPA).
Release history
G7SYNERR was made available in GSM13 feature patch WSD02.
Register type
Peg
C7SYNERR from C7SCCP OM group.
Associated logs
None
Extension register
None
Validation formula
None

Register G7RTBKSS 4
GSM CCS7 routed to backup subsystem
Counts the messages that are routed to a backup subsystem when the primary
subsystem is not available.
Release history
G7RTBKSS was made available in GSM13 feature patch WSD02.
Register type
Peg
C7RTBKSS from C7SCCP OM group.
Associated logs
None
Extension register
none
Validation formula
None
Register G7LOCSS 4
GSM CCS7 local subsystem
Counts the messages intended for a local subsystem that are received by
SCCP routing control (SCRC) from the CCS7 network through the message
Release history
G7LOCSS was made available in GSM13 feature patch WSD02.
Register type
Peg
C7LOCSS from C7SCCP OM group.
Associated logs
None
Extension register
G7LOCSS2

Validation formula
None


G7SCCPCO
GSM CSS7 Signaling Connection Control Part Connection Oriented4
The GSM CSS7 Signaling Connection Control Part (SCCP) Connection
Oriented (G7SCCPCO) OM group measures the number of messages
received and sent using the SCCP class 2 connection oriented group of
messages and displays the per-node counts for the CM and LIU7s involved.
This group is divided into two sets. The first set counts the total number of
Class 2 messages sent and received. Each register in this set has an extension
register. The second set counts the number of SCCP Class 2, Data Form One
(DT1), messages sent and received.
After subtracting DT1 messages from total messages, the remainder provides
a value that represents the overhead in establishing virtual connections using
SCCP Class 2 messaging. A relatively high overhead may mean
inefficiencies either in design or in the setting of timers, or in the ability of
one end or the other to react according to the specification. Overhead should
be 10-25% of the total DT1 messages.
Class 2 messages are currently received and accepted only by a Link Interface
Unit (LIU7).
The new GSM OM groups reside on the CM only. The OM data count from
the existing registers of the old OM groups that are pegged on the LIU7s are
transferred to the CM. On the CM this data is pegged into the new registers of
the corresponding new OM groups.
G7SCCPCO is not pegged on the CM, however OMSHOW will display tuple
0 (NIL_PMTYPE 0) for consistency. Counts for this tuple will always be
zero.
This allows the user the flexibility to view the summary OMs during normal
problem area(s) during system recovery procedure.
Registers
G7SCCPCO registers can be displayed at the DMS Maintenance and
G7CLS2TX G7CLS2T2 G7CLS2RX G7CLS2R2
G7DT1TX G7DT1T2 G7DT1RX G7DT1R2
G7ITTX G7ITRX G7CRTX G7CRT2
G7CRRX G7CRR2 G7CCTX G7CCT2

G7CCRX G7CCR2 G7RLSDTX G7RLSDT2
G7RLSDRX G7RLSDR2 G7RLCTX G7RLCT2
G7RLCRX G7RLCR2 G7CREFRX G7CREFTX
G7COFAIL G7COMREJ
Release history
G7SCCPCO was made available in GSM13 feature patch WSD02.
Group structure
Key field: None
Info field: This field contains the LIU7 number.
Tuples: 1 tuple per LIU7.
C7SCCPCO
Associated products
LIU7
Validation formula
The existing validation formula for C7SCCPCO on the peg register counts
also applies for G7SCCPCO.
Register G7CCRX 4
GSM CCS7 Connection Confirmations Received
Register G7CCRX is a peg register that counts the number of Signaling
Connection Control Part (SCCP) Class 2 connection confirmation messages
received.
Release history
G7CCRX was made available in GSM13 feature patch WSD02.

C7CCRX from C7SCCPCO OM group.
Associated logs
None
Extension register
G7CCR2
Validation formula
None
Register G7CCTX 4
GSM CCS7 Connection Confirmations Transmitted
Register G7CCTX is a peg register that counts the number of Signaling
Connection Control Part (SCCP) Class 2 connection confirmation messages
sent.
Release history
G7CCTX was made available in GSM13 feature patch WSD02.
C7CCTX from C7SCCPCO OM group.
Associated logs
None
Extension register
G7CCT2
Validation formula
None
Register G7CLS2RX 4
GSM CCS7 Class 2 Received
Register G7CLS2RX is a peg register that counts the valid SCCP Class 2
messages, excluding DT1, that are received from the far-end office across the
CCS7 link. Data is collected from each LIU7 that supports SCCP Class 2
messages. The G7CLS2RX register and its extension register are pegged on
receipt of the following SCCP Class 2 message types:

Table 4-1
SCCP Class 2 Message Types
Type Description Class Code (Hexadecimal)
CR connection request 2/3 01H
CC connection confirm 2/3 02H
CREF connection refuse NA 03H
RLSD released NA 04H
RLC release complete NA 05H
ERR protocol data unit NA 0FH

error
IT inactivity test all 0H
Release history
G7CLS2RX was made available in GSM13 feature patch WSD02.
C7CLS2RX from C7SCCPCO OM group.
Associated logs
None
Extension register
G7CLS2R2
Validation formula
None
Extension register
G7CLS2RX2

Register G7CLS2TX 4
GSM CCS7 Class 2 Transmitted
Register G7CLS2TX is a peg register that counts the valid and invalid SCCP
Class 2 messages, excluding DT1, that are transmitted from the near-end
office across the CSS7 link. Data is collected from each LIU7 that supports
SCCP Class 2 messages. Sending the following SCCP Class 2 message types
increments this register and its extension register:
Table 4-2
SCCP Class 2 Message Types
CR connection request 2/3 01H
CC connection confirm 2/3 02H
CREF connection refuse NA 03H
RLSD released NA 04H
RLC release complete NA 05H
ERR protocol data unit NA 0FH

error
IIT inactivity test all 0H
Release history
C7CLS2TX
Associated logs
None
Extension register
G7CLS2TX2

Validation formula
None
Register G7COFAIL 4
GSM CCS7 Connections Failed
Register G7COFAIL is a peg register that counts the connections that are
released for any reason other than a Released (RLSD) request from the far-
end office.
If one of the following three events occur, the G7COFAIL register pegs and
the connection is released:
• an Inactivity Test (IT) message is received with an incorrect class

• an Error (ERR) message is received
• a Connection Confirm (CC) message is received that is corrupt or
incorrectly formatted
Release history
G7COFAIL was made available in GSM13 feature patch WSD02.
C7COFAIL from C7SCCPCO OM group.
Associated logs
None
Extension register
None
Validation formula
None
Register G7COMREJ 4
GSM CCS7 Connection Oriented Message Request Rejected
Register G7COMREJ is a peg register that counts the number of times the
DMS-MSC/Call Server rejects a SCCP Class 2 message request for
connection made by the far-end office because it contains a message type that
is not supported.
Whenever the far-end office requests a connection to be established and the

DMS-MSC/Call Server refuses the request, the DMS-MSC/Call Server sends
back a Connection Refused (CREF) message. This action pegs the
G7COMREJ register. The DMS-MSC/Call Server refusal implies a lack of
resources available to set up the connection.

Only 2048 connections can be established on any LIU7 processor on which a

subsystem using SCCP Class 2 messaging is located. Any attempt to set up
more than this number of connections results in transmission of a CREF
message to the far-end office.
Release history
G7COMREJ was made available in GSM13 feature patch WSD02.
C7COMREJ from C7SCCPCO OM group.
Associated logs
None
Extension register
None
Validation formula
None
Register G7CREFRX 4
GSM CCS7 Connections Refused (Class 2 messages) Received
Register G7CREFRX is a peg register that counts the SCCP Class 2
Connections Refused (CREF) messages that are rejected by the SCCP. Any
refusal is normally associated with an immediate lack of available resources.
Unusually high counts of this register indicate that insufficient resources are
allocated to the connection control portion of the SCCP.
Release history
G7CREFRX was made available in GSM13 feature patch WSD02.
C7CREFRX from C7SCCPCO OM group.
Associated logs
None
Extension register
None
Validation formula
None

Register G7CREFTX 4
GSM CCS7 Connections Refused (Class 2 messages) Transmitted
Register G7CREFTX is a peg register that counts the SCCP Class 2 CREF
messages that are rejected by the SCCP. Refusals are normally associated
with an immediate lack of available resources. This event occurs, for
example, when the local subsystem is not in service or if the maximum
number of connections (2048) are already established.
Unusually high counts of this register indicate that insufficient resources are
allocated to the connection control portion of the SCCP.
Release history
G7CREFTX was made available in GSM13 feature patch WSD02.
C7CREFTX from C7SCCPCO OM group.
Associated logs
None
Extension register
None
Validation formula
None
Register G7CRRX 4
GSM CCS7 Connection Requests Received
Register G7CRRX is a peg register that counts the SCCP Class 2 connection
request messages received.
Release history
G7CRRX was made available in GSM13 feature patch WSD02.
C7CRRX from C7SCCPCO OM group.
Associated logs
None
Extension register
G7CRR2
Validation formula
None

Register G7CRTX 4
GSM CCS7 Connection Requests Transmitted
Register G7CRTX is a peg register that counts the SCCP Class 2 connection
request messages sent.
Release history
G7CRTX was created in GSM13 feature patch WSD02.
C7CRTX from C7SCCPCO OM group.
Associated logs
None
Extension register
G7CRT2
Validation formula
None
Register G7DT1RX 4
GSM CCS7 Data Form One (DT1) Received
Register G7DT1RX is a peg register that counts the valid SCCP Class 2 DT1
messages that are received from the far-end office and accepted by the near-
end office. DT1 messages arriving from unknown connections are not
counted. Data is collected from each LIU7that supports SCCP Class 2
messages. This register and its extension register are incremented on the
receipt of the following SCCP Class 2 message type:
Table 4-3
SCCP Class 2 Message Type
DT1 Data Form 12 06H
Release history
G7DT1RX was made available in GSM13 feature patch WSD02.
G7CLS2TX
G7CLS2T2

Associated logs
None
Extension register
G7DT1R2
Validation formula
None
Register G7DT1TX 4
GSM CCS7 Data Form One (DT1) Messages Transmitted
Register G7DT1TX is a peg register that counts the valid SCCP Class 2 DT1
messages transmitted from the DMS-MSC/Call Server. Data is collected from
each LIU7 that supports SCCP Class 2 messages. This register and its
extension register are incremented when the following SCCP Class 2
message type is sent:
Table 4-4
SCCP Class 2 Message Type
DT1 Data Form 12 06H
Release history
G7DT1TX was made available in GSM13 feature patch WSD02.
C7DT1TX from C7SCCPCO OM group.
Associated logs
None
Extension register
G7DT1T2
Validation formula
None
Register G7ITRX 4
GSM CCS7 Inactivity Test Messages Received
Register G7ITRX is a peg register that measures the number of Inactivity Test
(IT) messages received because of a time-out of the inactivity send timer. The

inactivity send timer records the interval between consecutive messages sent
on an active connection. The current value of this timer is three minutes. One
count on this register means that the DMS-MSC/Call Server has informed the
far-end office by way of an IT message that it is still interested in this
connection. On receipt of this message, the far-end office resets its inactivity
receive timer.
Release history
G7ITRX was made available in GSM13 feature patch WSD02.
C7ITRX from C7SCCPCO OM group.
Associated logs
None
Extension register
None
Validation formula
None
Register G7ITTX 4
GSM CCS7 Inactivity Test Messages Transmitted
Register G7ITTX is a peg register that counts the IT messages transmitted
from the near-end office because of a time-out of the inactivity send timer.
The inactivity send timer records the interval between consecutive messages
sent on an active connection. The current value of this timer is three minutes
or refer to Table SCCPTMR. One count on this register means that the DMS-
MSC/Call Server has informed the far-end office by way of an IT message
that it is still interested in this connection. On receipt of this message, the far-
end office resets its inactivity receive timer.
Release history
G7ITTX was made available in GSM13 feature patch WSD02.
C7ITTX from C7SCCPCO OM group.
Associated logs
None
Extension register
None

Validation formula
None
Register G7RLCRX 4
GSM CCS7 Connection Released Complete (Class 2 messages) Received
Register G7RLCRX is a peg register that counts the SCCP Class 2 connection
Released Complete (RLC) messages received.
The number of RLC messages received should be the same as the number of
Released (RLSD) messages transmitted. If the count on G7RLSDTX is
greater than the count on G7RLCRX, then the release timer (timer
TCONNREL in table SCCPTMR) is set for too short a time. That is, if the
RLC message sent does not arrive in time, the DMS-MSC/Call Server must
send another RLSD message. The default value for this timer is 10 seconds.
Ideally, the number of RLSD messages sent equals the number of RLC
messages received.
Release history
G7RLCRX was made available in GSM13 feature patch WSD02.
G7CLS2RX
G7CLS2R2
Associated logs
None
Extension register
G7RLCR2
Validation formula
None
Register G7RLCTX 4
GSM CCS7 Connection Released Complete (Class 2 messages)
Transmitted
Register G7RLCTX is a peg register that counts the SCCP Class 2 connection
RLC messages sent.
The number of RLC messages sent should be the same as the number of
RLSD messages received. If the number of RLC messages transmitted
(counted by G7RLCTX) is greater than the number of RLSD messages
received (counted by G7RLSDRX), the far-end timer is set too short for the

DMS-MSC/Call Server. In other words, if the far-end timing interval expires

before it receives the anticipated RLC message, the DMS-MSC/Call Server
must send another RLSD message.
Ideally, the number of RLSD messages received equals the number of RLC
messages sent.
Release history
G7RLCTX was made available in GSM13 feature patch WSD02.
G7CLS2TX
G7CLS2T2
Associated logs
None
Extension register
None
Validation formula
None
Register G7RLSDTX 4
GSM CCS7 Connection Released (Class 2 messages) Transmitted
Register G7RLSDTX is a peg register that counts the SCCP Class 2 released
(RLSD) messages sent.
RLSD messages are transmitted from an LIU7. The pegs are zero if there are
no LIU7s in service or if no LIU7 contains a valid load containing SCCP
class 2 software.
Release history
G7RLSDTX was made available in GSM06.
C7RLSDTX from C7SCCPCO OM group.
Associated logs
None
Extension register
G7RLSDT2

Validation formula
None
Register G7RLSDRX 4
GSM CCS7 Connection Released (Class 2 messages) Received
Register G7RLSDRX is a peg register that counts the number of SCCP Class
2 Connection Released (RLSD) messages received. This message indicates
the far end wants to release the established connection.
The number of Released Complete (RLC) messages transmitted should be the

same as the number of RLSD messages received. If the number of RLC
messages transmitted (counted by G7RLCTX) is greater than the number of
RLSD messages received (counted by G7RLSDRX), the far-end timer is set
too short for the DMS-MSC/Call Server. In other words, if the far-end timing
interval expires before it receives the anticipated RLC message, the DMS-
MSC/Call Server must send another RLSD message.
Ideally, the number of RLSD messages received is equal to the number of

RLC messages sent.
Release history
G7RLSDRX was made available in GSM13 feature patch WSD02.
C7RLSDRX from C7SCCPCO OM group.
Associated logs
None
Extension register
G7RLSDR2
Validation formula
None
Register G7RLCTX 4
GSM CCS7 Connection Release Complete (Class 2 messages)
Transmitted
Register G7RLCTX is a peg register that counts the number of SCCP Class 2
Connection Release Complete (RLC) messages transmitted. The switch sends
this message in response to an RLSD message if a valid connection was
present or not.
The number of Released Complete (RLC) messages transmitted should be the

same as the number of RLSD messages received. If the number of RLC

messages transmitted is greater than the number of RLSD messages received

(counted by G7RLSDRX), the far-end timer is set too short for the DMS-
MSC/Call Server. In other words, if the far-end timing interval expires before
it receives the anticipated RLC message, the DMS-MSC/Call Server must
send another RLSD message.
Ideally, the number of RLSD messages received is equal to the number of

RLC messages sent.
Release history
G7RLCTX was made available in GSM13 feature patch WSD02.
C7RLCTX from C7SCCPCO OM group.
Associated logs
None
Extension register
G7RLCT2
Validation formula
None
Register G7RLCRX 4
GSM CCS7 Connection Released (Class 2 messages) Received
Register G7RLCRX is a peg register that counts the number of SCCP Class 2
Connection Released Complete (RLC) messages received. The far-end sends
this message in response to a RLSD message from the local end.
Release history
G7RLCRX was made available in GSM13 feature patch WSD02.
C7RLCRX from C7SCCPCO OM group.
Associated logs
None
Extension registers
G7RLCR2
G7RLCT2

Validation formula
None

G7SCCPX
GSM CSS7 Signaling Connection Control Part Extended Services 4
The GSM CSS7 Signaling Connection Control Part Extended Services
(G7SCCPX) OM group provides information on the performance and use of
extended unitdata and extended unitdata service (XUDT/XUDTS) messages.
The registers count the number of messages that are formatted into extended
XUDT and XUDTS messages, messages that encounter reassembly errors,
and messages that encounter hop counter violations.
G7SCCPX is cloned off the C7SCCPX OM group, the only difference is that
it reports OM on a per LIU7 basis. The GSM OM group resides on the CM
only and displays the per-node counts for the CM and LIU7s involved. The
OM data count from the existing registers of the old OM groups that are
pegged on the LIU7s are transferred to the CM. On the CM this data is
pegged into the new registers of the corresponding new OM groups.
This allows the user flexibility to view the summary OMs during normal
problem area during system recovery procedure.
Registers
G7SCCPX registers are displayed at the Maintenance and Administration
G7XUDTRX G7XUDTRX2 G7XUDTSR G7XUDTTX

G7XUDTT2 G7XUDTST G7XTIMER G7XSGTOS
G7XRSERR G7XHCERR
Release history
G7SCCPX was created in GSM13 feature patch WSD02.
Group structure
Key field: None
Info field: This field contains the LIU7 number
Number of tuples: 1 per LIU7.
Validation formula
Validation of this OM is performed with a count of Table GHLRSSOP. This
count can be a total count or a count on a per Supplementary Service basis.

Associated OMs
C7SCCPX.
Register G7XUDTRX 4
GSM CCS7 XUDT received
Register G7XUDTRX counts extended unitdata (XUDT) connectionless
Register type
Peg
Release history
G7XUDTRX was created in GSM13 patch release WSD02.
C7XUDTRX from C7SCCPCO OM group.
Associated logs
None
Extension register
G7XUDTR2
Validation formula
None
Register G7XUDTSR 4
GSM CCS7 XUDTS received
Counts extended unitdata service (XUDTS) connectionless SCCP messages
that are received by SCCP routing control (SCRC) from the CCS7 network
through the message transfer part (MTP).
Register type
Peg
Release history
G7XUDTSR was created in GSM13 patch release WSD02.
C7XUDTSR from C7SCCPCO OM group.

Associated logs
None
Extension register
None
Validation formula
None
Register G7XUDTTX 4
GSM CCS7 XUDTS transmitted
Register G7XUDTTX counts extended unidata (XUDT) connectionless
SCCP messages that are routed into the network through the message transfer
part (MTP).
Register type
Peg
Release history
G7XUDTTX was created in GSM13 patch release WSD02.
C7XUDTSR from C7SCCPCO OM group.
Associated logs
None
Extension register
G7XUDTT2
Validation formula
None
Register G7XUDTST 4
GSM CCS7 XUDTS transmitted
Register G7XUDTST counts extended unitdata service (XUDTS)
connectionless SCCP messages that are routed into the network through the
message transfer part (MTP).
Register type
Peg
Release history
G7XUDTST was created in GSM13 patch release WSD02.

Associated Registers
C7XUDTST from C7SCCPX OM group.
Associated logs
None
Extension register
None
Validation formula
None
Register G7XTIMER 4
GSM CCS7 reassembly error, timer expired
Register G7XTIMER counts extended unitdata (XUDT) connectionless
SCCP messages that cannot be reassembled because the reassembly timer has
expired.
Register type
Peg
Release history
G7XTIMER was created in GSM13 patch release WSD02.
C7XTIMER from C7SCCPX OM group.
Associated logs
None
Extension register
None
Validation formula
None
Register G7XSGTOS 4
GSM CCS7 reassembly error, XUDT message received out of sequence.
Register CFBPR contains the Counts extended unitdata (XUDT)
connectionless SCCP messages that cannot be reassembled because of a
segment received out of sequence.
Register type
Peg

Release history
CFBPR was created in GSM13 patch release WSD02.
C7SGTOS from C7SCCPX OM group.
Associated logs
None
Extension register
None
Validation formula
None
Register G7XRSERR 4
GSM CCS7 reassembly error, no reassembly space
Register G7XRSERR counts extended unitdata (XUDT/XUDTS)
connectionless SCCP messages that cannot be reassembled because of a lack
of resources.
Register type
Peg
Release history
G7XRSERR was created in GSM13 patch release WSD02.
C7XRSERR from C7SCCPX OM group.
Associated logs
None
Extension register
None
Validation formula
None
Register G7XHCERR 4
GSM CCS7 hop counter validation
Register G7XHCERR counts extended unitdata and extended data service
(XUDT/XUDTS) connectionless SCCP messages that are discarded due to a
hop counter violation.

Register type
Peg
Release history
G7XHCERR was created in GSM13 patch release WSD02.
C7SGTOS from C7SCCPX OM group.
Associated logs
None
Extension register
None
Validation formula
None

GACODE
GSM Account Code 4
The GSM Account Code group measures the number of account code calls.
Registers
GACODE registers may be displayed at the DMS MAP as follows:
GACREQV GACREQNV GACVOL GACFLEN
GACFNAC
Release history
GACODE was created in GSM07.
Group structure
Number of Tuples: 1
Key field: None
Info field: None
None
Associated products
GSM
Register GACREQV 4
GSM Account Code Required/Verified
Register GACREQV is a peg register that counts the mobile originated calls
that require an account code and whose subscribed account length is greater
than zero. The dialed account code length should be verified by the DMS-
MSC/Call Server.
Release history
GACREQV was created in GSM07.
None
Associated logs
None

Extension register
None
Validation formula
None
Register GACREQNV 4
GSM Account Code Required/not Verified
Register GACREQNV is a peg register that counts the mobile originated calls
that require an account code and whose subscribed account code length is
greater than zero. The dialed account code length should not be verified by
the DMS-MSC/Call Server.
Release history
GACREQNV was created in GSM07.
None
Associated logs
None
Extension register
None
Validation formula
None
Register GACVOL 4
GSM Account Code Voluntary Entered
Register GACVOL is a peg register that counts the mobile originated calls
that use the account code voluntary feature. This register is pegged when a
subscriber enters the account code dialing pattern and the subscriber has the
account code voluntary feature.
Release history
GACVOL was created in GSM07.
None
Associated logs
None

Extension register
None
Validation formula
None
Register GACFLEN 4
GSM Account Code Failed Due to Incorrect Length
Register GACFLEN is a peg register that counts the calls that failed when a
subscriber feature enters the incorrect account code length.
Release history
GACFLEN was created in GSM07.
None
Associated logs
None
Extension register
None
Validation formula
None
Register GACFNAC 4
GSM Account Code Failed Due to Absence of Account Code
Register GACFNAC is a peg register that counts the calls that failed when a
subscriber is using the account code required feature and the account code is
missing.
Release history
GACFNAC was created in GSM07.
None
Associated logs
None
Extension register
None

Validation formula
None


GCBK
GSM Code Blocking 4
The GSM Code Blocking OM group measures the number of calls blocked
and passed by specific Network Management Code controls of type CBk.
This encompasses both percentage blocking based controls and gap based
controls. This group shows how effectively the code controls are restricting
traffic to particular destination codes.
Registers
The following GCBK registers may be displayed at the DMS MAP:
GCBKBLK GCBKPASS
Release history
GCBK was created in GSM07.
Group structure
Number of tuples: One tuple per trunk group
Key field: None
Info field: GCBK_OMINFO is made up of three parts: GCBKKEY,

GCBK_TYPE, and GCBK_GAP_OR_PCT_LEVEL.
None
Validation formula
(GCBKBLKs + GCBKPASS) = the total number of calls made to destination
codes within the range specified for the control.
Associated products
DMS-MSC/Call Server
Register GCBKBLK 4
GSM Code Blocking Count
Register GCBKBLK is a peg register that measures the number of calls to the
given range of blocked destination codes.
Release history
GCBKBLK was created in GSM07.

GCBKPASS
Extension register
None
Associated logs
NWM600 - is generated when a percentage based CBK control is applied or
removed.
NWM604 - is generated when a gap based CBK control is applied or

removed.
Validation formula
For each code blocking control, the total number of calls to the given range of
destination codes for control (GCBKBLKs) is equal to GCBKPASS.
Register GCBKPASS 4
GSM Code Blocking Passed
Register GCBKPASS is a peg register that measures the number of calls to
the given range of destination codes which have passed the blocking control.
Release history
GCBKPASS was created in GSM07.
GCBKBLKs
Extension register
None
Associated logs
NWM600 - is generated when a percentage based CBK control is applied or
removed.
NWM604 - is generated when a gap based CBK control is applied or

removed.
Validation formula
For each code blocking control, the total number of calls to the given range of
destination codes for control (GCBKBLKs) is equal to GCBKPASS.

GCISBXBK
GSM CI Sub Extension Block OMs 4
The GSM CI Sub Extension Block OMs group created to display the per-node
counts.
Registers
The following GCISBXBK registers may be displayed at the DMS MAP:
GCEXSZMU GCEXOVMU GCEXHIMU GCEXSZU2

GCEXHIU2
Release history
GCISBXBK was created in GSM13.
Group structure
EXT
Validation formula
Associated products
MMU
Register GCEXSZMU 4
GSM CI Sub Extension Block OMs
Register GCEXSZMU counts the number of requests for a particular type of
Release history
GCEXSZMU was created in GSM13.

EXTSIEZ
Extension register
GCEXSZU2
Validation formula
None
Register GCEXOVMU 4
Register GCEXOVMU counts when a particular type of extension block is
Release history
GCEXOVMU was created in GSM13.
EXTOVFL
Extension register
None
Validation formula
None
Register GCEXHIMU 4
Register GCEXHIMU counts the maximum number of extension blocks of
Release history
GCEXHIMU was created in GSM13.
EXTHI
Extension register
GCEXHIU2
Validation formula
None

GELIDOMG
GSM Emergency Services Location Information Delivery OM Group 4
The OM Group keeps track of the call scenarios that are used for the location
services E911 functionality.
Registers
The following GELIDOMG registers may be displayed at the DMS MAP:
LCSINVK LCSINV2 CASPUSH CASPUS2

NCASPULL NCASPUL2 TOCASPUS TOCASPU2
ESRKOVFL ESRKOFL2 ESRKAUDT ESRKAUD2
Release history
GELIDOMG was created in GSM13 and modified for UMTS03/GSM17.
Group structure
Number of tuples: one
Key field: none
Info field: none
GELIDOMU
Associated products
None
Associated logs
None
Validation formula
Let X be the number of times the LCSINVK register is pegged
Let Y be the number of times the CASPUSH register is pegged.
Let Z be the number of times the NCASPULL register is pegged.
Let W be the number of times the TOCASPUS register is pegged.

The following are the formulae that apply to these registers:
• X=Y+Z
• X/2=Y
• X/2=Z
• Y<=X
• Z<=X
• W<=Y
• W<=Z
Register LCSINVK 4
Location Services functionality invoked
Register LCSINVK is pegged whenever LCS is invoked.
Register type
Peg
Extension register
LCSINV2
Validation formula
See the validation formulae given for the OM group.
Register CASPUSH 4
CAS PUSH scenario
Register CASPUSH is pegged whenever the scenario is identified to be CAS
PUSH.
Register type
Peg
Extension register
CASPUS2
Validation formula
Register NCASPULL 4
NCAS PULL scenario
Register NCASPULL is pegged every time an NCAS PULL is used.

Register type
Peg
Extension register
NCASPUL2
Validation formula
Register TOCASPUS 4
Timed Out CAS PUSH
Register TOCASPUS is pegged whenever a timed out CAS PUSH is
followed by a successful NCAS PULL.
Register type
Peg
Extension register
TOCASPU2
Validation formula
Register ESRKOVFL 4
ESRK tokens exhausted
Register ESRKOVFL counts the number of emergency calls that falls back to
phase 1 because all the ESRK tokens for that particular LCSIDX are in use.
Release history
Register ESRKOVFL was created in UMTS03/GSM17.
Register type
Peg
Associated register
None
Validation formula
None
Associated Logs
Log Number: GMSC 609

Extension register
ESRKOFL2
Register ESRKAUDT 4
ESRK Audit
Register ESRKAUDT counts the number of tokens that has remained in the
inuse state for a long time and is freed by the audit.
Release history
Register ESRKAUDT was created in UMTS03/GSM17.
Register type
Peg
Associated register
None
Validation formula
None
Associated Logs
None
Extension register
ESRKAUD2


GELIDOMU
GSM Emergency Location Identification OMs on MMUs 4
The OM group keeps count of the call scenarios that are used for the location
services on a per MMU basis. This is a two dimensional OM group with the
first dimension for the OM registers and the second dimension for the MMU
servers that are in service. The registers of this OM group have a one-to-one
correspondence with the registers of the GELIDOMG OM group.
Registers
The following GELIDOMU registers may be displayed at the DMS MAP:
LCSINMU LCSINM2 CASPUMU CASPUM2

NCASPUMU NCASPUM2 TOCASPMU TOCASPM2
Release history
GELIDOMU was created in GSM13.
Group structure
Number of tuples: equal to the number of MMU servers that are in service.
Key field: None
Info field: None
GELIDOMG
Associated products
None
Associated logs
None
Validation formula
For a given register, the sum of peg counts in the register for all available
MMUs is always smaller than or equal to the number of peg counts in the
corresponding register of the associated OM group.

Register LCSINMU 4
Location Services functionality invoked per MMU
Register LCSINMU is pegged whenever LCS is invoked in the MMU.
Register type
Peg
Extension register
LCSINM2
Validation formula
Register CASPUMU 4
CAS PUSH scenario per MMU
Register CASPUMU is pegged whenever the scenario in the MMU is
identified to be CAS PUSH.
Register type
Peg
Extension register
CASPUM2
Validation formula
Register NCASPUMU 4
NCAS PULL scenario per MMU
Register NCASPUMU is pegged every time an NCAS PULL is used in the
MMU.
Register type
Peg
Extension register
NCASPUM2
Validation formula

Register TOCASPMU 4
Timed Out CAS PUSH per MMU
Register TOCASPMU is pegged whenever a timed out CAS PUSH is
followed by a successful NCAS PULL in the MMU.
Register type
Peg
Extension register
TOCASPM2
Validation formula


-1
Appendix: DMS-100 base OM groups

While this publication describes OM groups that are specific to the
DMS-MSC/Call Server, another set of OM groups exists which are common
to the DMS-100 family. These “base OM groups” are not described in this
publication.
The base OM groups are listed in Table 0-1. The scope of the table is all of
the base OM groups, not just those in a certain alphabetical range.
For the most current information on the base OM groups, refer to DMS-100
Family Operational Measurements.
Table 0-1
Base OM groups for DMS-MSC/Call Server
Group Description
AMA Automatic Message Accounting (collects data on billable call).
ANN Recorded announcements.
C7LINK1 Performance and usage of a CCS7 link, link failures.
C7LINK2 Performance and usage of a CCS7 link, congestion, and traffic measurements.
C7LINK3 Monitors traffic and performance of a message signaling unit for CCS7.
C7LKSET Monitors traffic and performance of a link set.
C7MTP CCS7 Message Transfer Part (MTP) counts message signaling units that are
discarded by a CCS7 MTP of a Signal Transfer Point (STP).
C7ROUTE CCS7 Message Transfer Part counts message signaling units that are discarded
by a CCS7 route.
C7RTESET CCS7 Message Transfer Part counts message signaling units that are discarded
by a CCS7 routeset.
—sheet 1 of 4—

-2 Appendix: DMS-100 base OM groups
Nortel Networks Confidential
Table 0-1
Base OM groups for DMS-MSC/Call Server (continued)
Group Description
C7SCCP CCS7 Message Transfer Part counts message signaling units that are discarded
by a CCS7 SCCP layer.
CBK Code block group limits percentage of traffic into congested area.
CM Computing module of the E-Core switch.
CP Call processing software house.
CP2 Extension of CP.
CPU CPU maintenance summary.
CPUSTAT CP status OM data.
CSL Console device maintenance summary.
DDU Disk drive unit file and maintenance work.
ENETMAT Defined for the ENET matrix cards.
ENETOCC CPU occupancies of processes in each ENET.
ENETPLNK ENET P-side link.
ENETSYS ENET system cards.
EXT Extension block OM. Fundamental record data in addition to standard registers.
IOC I/O controller maintenance summary.
IOSYS I/O systems.
ISUPCGRP ISUP circuit group availability.
ISUPCKTA ISUP circuit group availability.
ISUPCONN ISUP end-to-end connection performance.
ISUPERRS Performance of ISUP node with respect to immunity to resets and abnormal
conditions.
ISUPUSAG ISUP utilization in terms of measured message volume.
LIUFBUS Gathered at the frame bus interface of an EIU.
LOGS Log messages.
—sheet 2 of 4—

Appendix: DMS-100 base OM groups -3
Table 0-1
Group Description
MACHCONG Machine congestion.
MS Message switch summary.
MSCHAIN Message switch chain.
MSCHNLK Message switch channelized link.
MSFBUS Message switch frame bus OM group.
MSFBUSTP Message switch frame bus taps OM group.
MTU Magnetic tape unit maintenance summary.
OFZ Office traffic summary indicates the traffic offered to the office as a whole.
OFZ2 Extension of OFZ.
OTS Office traffic summary. The measurements for OTS are based on the actual
disposition of call. Calls originating within or incoming into the DMS and the types
of agents that these calls terminate to (actual call disposition) are recorded.
PCMCARR CCITT DS30 carrier maintenance summary.
PM Peripheral module maintenance summary.
PM1 Single unit peripheral module maintenance summary.
PM2 Double unit peripheral module maintenance summary.
PMOVLD Peripheral module overload controls.
PMTYP Peripheral module maintenance summary subtotal.
SLM System load module for the E-Core switch.
SOTS Supplementary office traffic summary. The Group contains information on an

office basis of the No Circuit Class (NCCLS) category together with outgoing and
terminating network performance.
STORE Provides information about data and program store.
SVCT Service circuits.
SYSPERF Measurements in SYSPERF can be used to evaluate the performance of

components of the switch.
—sheet 3 of 4—

-4 Appendix: DMS-100 base OM groups
Table 0-1
Group Description
TCAPERRS TCAP error count.
TCAPUSAG TCAP usage measurement.
TCN7ERRS TCAP error counts for CCITT. The corresponding feature implements the hooks
necessary for an Austrian version of TCAP.
TCN7USAG TCAP usage measurements for CCITT. The corresponding feature implements
the hooks necessary for an Austrian version of TCAP.
TM Trunk module maintenance measurement.
TONES Tones group pegs events like number of calls routed to a given tone.
TRK Trunk group.
TRMTER Treatment equipment related.
TRMTFR Treatment feature related.
TRMTFR2 Extension of TRMTFR.
TRMTPR Treatment protocol-related measures the number of times a treatment is called

due to protocol violations.
TRMTRS Treatment resource shortage.
TROUBLEQ System referred line diagnostic queue.
TS Time switch group.
UTR Universal tone receiver, international/domestic.
—sheet 4 of 4—

test
Family Product Manual Contacts Copyright Confidentiality Legal
GSM NSS/UMTS UCC

DMS-MSC/Call Server
To order documentation from Nortel Networks Global Wireless Knowledge Services, call
(1) (877) 662-5669
To report a problem in this document, call

(1) (877) 662-5669
or send e-mail from the Nortel Networks Customer Training & Documentation World Wide Web site at
http://www.nortelnetworks.com/td
Copyright © 1995–2004 Nortel Networks, All Rights Reserved
NORTEL NETWORKS CONFIDENTIAL

The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its
employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the
same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly
authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.
Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as
progress in engineering and manufacturing may warrant.
* Nortel Networks, the Nortel Networks logo, the Globemark HOW the WORLD SHARES IDEAS, and Unified Networks are
trademarks of Nortel Networks. DMS, DMS-HLR, DMS-MSC, MAP, and SuperNode are trademarks of Nortel Networks. GSM is a
trademark of GSM MOU Association.
Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.
Document number: 411-2231-814P1
Product release: GSM17/UMTS03
Document version: Standard 17.15
Date: October 2004
Originated in the United States of America

Om 1 411 2231 814P1.17.15

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

Om 1 411 2231 814P1.17.15

Uploaded by

Copyright:

Available Formats

411-2231-814P1

GSM NSS/UMTS UCC

GSM17/UMTS03 Standard 17.15 October 2004

Document number: 411-2231-814P1

Copyright Country of printing Confidentiality Legal statements Trademarks

Copyright © 1995–2004 Nortel Networks, All Rights Reserved

NORTEL NETWORKS CONFIDENTIAL

411-2231-814P1 Standard 17.15 October 2004

Note: While this document is one volume of a three volume set

GSM NSS/UMTS UCC DMS-MSC/Call Server OM Reference Manual Vol. 1 GSM17/UMTS03

411-2231-814P1 Standard 17.15 October 2004

GSM NSS/UMTS UCC DMS-MSC/Call Server OM Reference Manual Vol. 1 GSM17/UMTS03

411-2231-814P1 Standard 17.15 October 2004

GSM NSS/UMTS UCC DMS-MSC/Call Server OM Reference Manual Vol. 1 GSM17/UMTS03

The following OM groups have been deleted:

The following OM groups were added to this release:

411-2231-814P1 Standard 17.15 October 2004

The following OM groups were modified to this release:

The following OM groups were added to this release:

GSM NSS/UMTS UCC DMS-MSC/Call Server OM Reference Manual Vol. 1 GSM17/UMTS03

The following OM groups was added for this release:

411-2231-814P1 Standard 17.15 October 2004

GSM NSS/UMTS UCC DMS-MSC/Call Server OM Reference Manual Vol. 1 GSM17/UMTS03

The following OM groups have been modified for this release:

The following OM groups have been added for this release:

The following OM groups have been modified for this release:

The following OM groups have been added for this release:

411-2231-814P1 Standard 17.15 October 2004

The following OM groups have been modified in this release:

The following OM groups have been added to this release:

The following OM groups have been added to this release:

These OM groups have been modified in this release:

The following OM groups have been added to this release:

GSM NSS/UMTS UCC DMS-MSC/Call Server OM Reference Manual Vol. 1 GSM17/UMTS03

The following OM groups have been added to this release:

The changes for this release are as follows:

411-2231-814P1 Standard 17.15 October 2004

GSM NSS/UMTS UCC DMS-MSC/Call Server OM Reference Manual Vol. 1 GSM17/UMTS03

The following OM groups have been added to this release:

The following OM groups have been modified for this release:

The following OM groups have been added to this release:

411-2231-814P1 Standard 17.15 October 2004

The following OM groups have been modified for this release:

The following OM groups have been added to this release:

GSM NSS/UMTS UCC DMS-MSC/Call Server OM Reference Manual Vol. 1 GSM17/UMTS03

The following OM groups have been modified for this release:

The following OM groups have been added to this release:

411-2231-814P1 Standard 17.15 October 2004

The following OM groups have been modified for this release:

The following OM groups have been modified for this release:

The following OM group has been added to this release:

GSM NSS/UMTS UCC DMS-MSC/Call Server OM Reference Manual Vol. 1 GSM17/UMTS03

411-2231-814P1 Standard 17.15 October 2004

Operational measurements system overview 1-1

OM groups: A-D 2-1

OM groups: F-GE 4-1

Appendix: DMS-100 base OM groups A-1

GSM NSS/UMTS UCC DMS-MSC/Call Server OM Reference Manual Vol. 1 GSM17/UMTS03

411-2231-814P1 Standard 17.15 October 2004

About this document 1

In addition, if an OM group that is associated with a Network Element (NE) is

Notice of design intent and enhancement 1

GSM NSS/UMTS UCC DMS-MSC/Call Server OM Reference Manual Vol. 1 GSM17/UMTS03