932
Oracle ® Communications EAGLE Database Administration Manual - Global Title Translation Release 45.0 910-6671-001 Revision B February 2014

Oracle Communications EAGLE® Communications EAGLE Database Administration Manual - Global Title Translation Release 45.0 910-6671-001 Revision B February 2014 Oracle ® Communications

  • Upload
    vanhanh

  • View
    252

  • Download
    6

Embed Size (px)

Citation preview

  • Oracle CommunicationsEAGLEDatabase Administration Manual - Global Title Translation

    Release 45.0

    910-6671-001 Revision B

    February 2014

  • Oracle Communications Database Administration Manual - Global Title Translation, Release 45.0Copyright 1993, 2014, Oracle and/or its affiliates. All rights reserved.

    This software and related documentation are provided under a license agreement containing restrictionson use and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverseengineering, disassembly, or decompilation of this software, unless required by law for interoperability, isprohibited.

    The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.

    If this is software or related documentation that is delivered to the U.S. Government or anyone licensing iton behalf of the U.S. Government, the following notice is applicable:

    U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technicaldata delivered to U.S. Government customers are "commercial computer software" or "commercial technicaldata" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictionsand license terms set forth in the applicable Government contract, and, to the extent applicable by the termsof the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer SoftwareLicense (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

    This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applicationsthat may create a risk of personal injury. If you use this software or hardware in dangerous applications,then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures toensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused byuse of this software or hardware in dangerous applications.

    Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarksof their respective owners.

    Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarksare used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of AdvancedMicro Devices. UNIX is a registered trademark of The Open Group.

    This software or hardware and documentation may provide access to or information on content, products,and services from third parties. Oracle Corporation and its affiliates are not responsible for and expresslydisclaim all warranties of any kind with respect to third-party content, products, and services. OracleCorporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to youraccess to or use of third-party content, products, or services.

  • Table of Contents

    Chapter 1: Introduction...............................................................................17Overview...............................................................................................................................................18Scope and Audience............................................................................................................................19Manual Organization...........................................................................................................................19Documentation Admonishments.......................................................................................................19Customer Care Center.........................................................................................................................20Emergency Response...........................................................................................................................22Related Publications............................................................................................................................23Documentation Availability, Packaging, and Updates..................................................................23Locate Product Documentation on the Customer Support Site....................................................24Maintenance and Administration Subsystem..................................................................................24EAGLE 5 ISS Database Partitions......................................................................................................25

    Chapter 2: Global Title Translation (GTT) Overview..........................28Introduction..........................................................................................................................................31Global Title Translation Feature........................................................................................................31Enhanced Global Title Translation Feature......................................................................................34Variable-length Global Title Translation Feature............................................................................38Advanced GT Modification Feature..................................................................................................40Intermediate GTT Load Sharing Feature..........................................................................................42ANSI/ITU SCCP Conversion Feature..............................................................................................42Support of SCCP XUDT Messages....................................................................................................45In-Sequence Delivery of Class 1 UDT Messages.............................................................................46Flexible GTT Load Sharing.................................................................................................................47

    Flexible Intermediate GTT Load Sharing.............................................................................47Flexible Final GTT Load Sharing...........................................................................................51

    Origin-Based SCCP Routing...............................................................................................................55Hex Digit Support for GTT.................................................................................................................61Weighted GTT Load Sharing..............................................................................................................63Transaction-Based GTT Load Sharing..............................................................................................70SCCP Loop Detection..........................................................................................................................75Flexible Linkset Optional Based Routing.........................................................................................76TCAP Opcode Based Routing............................................................................................................92GTT Actions..........................................................................................................................................97

    iii910-6671-001 Revision B, February 2014

  • MTP Routed Global Title Translation.............................................................................................111Unique GTT Selectors........................................................................................................................112XUDT UDT Conversion Feature......................................................................................................115Upgrading from Global Title Translation (GTT) to Enhanced Global Title Translation

    (EGTT)............................................................................................................................................120SCCP Overview..................................................................................................................................122GTT Configuration.............................................................................................................................135EGTT Configuration..........................................................................................................................138Adding a Service Module.................................................................................................................141Removing a Service Module.............................................................................................................151Adding a Mapped SS7 Message Translation Type.......................................................................153Removing a Mapped SS7 Message Translation Type...................................................................155Changing a Mapped SS7 Message Translation Type....................................................................156Adding a Concerned Signaling Point Code...................................................................................157Removing a Concerned Signaling Point Code...............................................................................166Provisioning a Solitary Mated Application....................................................................................170Provisioning a Dominant Mated Application................................................................................189Provisioning a Load Shared Mated Application...........................................................................217Provisioning a Combined Dominant/Load Shared Mated Application...................................244Removing a Mated Application.......................................................................................................269Changing the Attributes of a Mated Application..........................................................................283Changing the Mated Application Type..........................................................................................291Changing the Weight and In-Service Threshold Values of a Mated Application....................298Changing the MRNSET and MRN Point Code Values of MAP Entries....................................308Provisioning MRN Entries................................................................................................................313Removing MRN Entries....................................................................................................................342Changing the Relative Cost Values of MRN Entries.....................................................................352Changing MRN Entries with the ESWT Parameter......................................................................360Changing the Weight and Threshold Values of MRN Entries....................................................369Changing the MAPSET, MAP Point Code, and MAP SSN Values of MRN Entries................384Adding a GT Conversion Table Entry............................................................................................388Removing a GT Conversion Table Entry........................................................................................393Changing a GT Conversion Table Entry.........................................................................................396Changing the ANSI/ITU SCCP Conversion Options...................................................................402Changing SCCP Class 1 Sequencing Option..................................................................................404Changing the SCCP Alarm Thresholds..........................................................................................406Changing the Transaction-Based GTT Load Sharing Options....................................................409Adding a Loopset...............................................................................................................................411Removing a Loopset..........................................................................................................................414Changing the Attributes of a Loopset.............................................................................................418Configuring the ANSI to ITU-N SCCP Conversion Option........................................................426

    iv910-6671-001 Revision B, February 2014

  • Configuring a SCCP Test Message..................................................................................................428Adding Global Title Modification Information.............................................................................435Removing Global Title Modification Information.........................................................................440Changing Global Title Modification Information.........................................................................447Changing the MTP-Routed GTT Options.......................................................................................453

    Chapter 3: Global Title Translation (GTT) Configuration................456Introduction........................................................................................................................................457Adding a Translation Type...............................................................................................................457Removing a Translation Type..........................................................................................................468Adding a Global Title Translation...................................................................................................475Removing a Global Title Translation..............................................................................................501Changing a Global Title Translation...............................................................................................508

    Chapter 4: Enhanced Global Title Translation (EGTT)Configuration..........................................................................................536

    Introduction........................................................................................................................................537Adding a GTT Set...............................................................................................................................538Removing a GTT Set..........................................................................................................................546Changing a GTT Set...........................................................................................................................552Adding a GTT Selector......................................................................................................................558Removing a GTT Selector..................................................................................................................579Changing a GTT Selector..................................................................................................................584Adding Global Title Address Information.....................................................................................595Removing Global Title Address Information................................................................................634Changing Global Title Address Information.................................................................................644Changing the Default GTT Mode Options.....................................................................................685Adding a GTT Action........................................................................................................................689Removing a GTT Action Entry.........................................................................................................704Changing a GTT Action....................................................................................................................708Adding a GTT Action Set..................................................................................................................722Removing a GTT Action Set.............................................................................................................725Changing a GTT Action Set..............................................................................................................728Adding a GTT Action Path Entry....................................................................................................731Removing a GTT Action Path Entry................................................................................................737Changing a GTT Action Path Entry.................................................................................................739Changing the Unique GTT Selector Option...................................................................................744

    v910-6671-001 Revision B, February 2014

  • Appendix A: Controlled Feature Activation Procedures...................746Introduction........................................................................................................................................748Activating the IGTTLS feature.........................................................................................................748Clearing a Temporary FAK Alarm..................................................................................................753Turning Off the IGTTLS Feature .....................................................................................................754Enabling the XGTT Table Expansion Feature................................................................................756Enabling the XMAP Table Expansion Feature...............................................................................761Activating the EPAP Data Split and Dual ExAP Configuration Features.................................766Activating the ANSI/ITU SCCP Conversion Feature..................................................................769Activating the Flexible GTT Load Sharing Feature.......................................................................774Turning Off the Flexible GTT Load Sharing Feature ...................................................................779Activating the Origin-Based SCCP Routing Feature....................................................................780Activating the Hex Digit Support for GTT Feature......................................................................785Activating the Weighted GTT Load Sharing Feature...................................................................789Activating the Transaction-Based GTT Load Sharing Feature....................................................794Activating the SCCP Loop Detection Feature................................................................................799Activating the E5-SM4G/ E5-SM8G-B Throughput Capacity Feature......................................804Activating the Advanced GT Modification Feature......................................................................810Activating the GTT Load Sharing with Alternate Routing Indicator Feature..........................815Turning Off the GTT Load Sharing with Alternate Routing Indicator Feature .......................819Activating the Support for 16 GTT Lengths in VGTT Feature....................................................821Activating the Flexible Linkset Optional Based Routing Feature...............................................825Activating the TCAP Opcode Based Routing Feature..................................................................830Enabling a TOBR Opcode Quantity................................................................................................833Activating the GTT Actions Features..............................................................................................835Activating the XUDT UDT Conversion Feature............................................................................842

    Appendix B: MO SMS B-Party Routing ConfigurationProcedures................................................................................................847

    Introduction........................................................................................................................................848Activating the MO SMS B-Party Routing Feature.........................................................................849Configuring the GSM MO SMS B-Party Routing Options...........................................................854Configuring the IS-41 MO SMS B-Party Routing Options...........................................................856Adding a Service Selector Entry for the MO SMS B-Party Routing Feature.............................858Removing a Service Selector Entry..................................................................................................867Changing the Attributes of a Service Selector Entry for the MO SMS B-Party Routing

    Feature............................................................................................................................................871Turning the MO SMS B-Party Routing Feature Off......................................................................879

    vi910-6671-001 Revision B, February 2014

  • Appendix C: MO SMS Prepaid Intercept on B-Party ConfigurationProcedures................................................................................................882

    Introduction........................................................................................................................................883Activating the Prepaid SMS Intercept Phase 1 Feature................................................................883Configuring the B-Party Check Option for the Prepaid SMS Intercept Phase 1 Feature........888Configuring Point Code Entries for the Prepaid SMS Intercept Phase 1 Feature.....................890Configuring GTA Entries for the Prepaid SMS Intercept Phase 1 Feature................................898Turning Off the Prepaid SMS Intercept Phase 1 Feature ............................................................902

    Glossary.............................................................................................................................905

    vii910-6671-001 Revision B, February 2014

  • List of Figures

    Figure 1: EAGLE 5 ISS Database Partitions (E5-Based Control Cards)....................................................26

    Figure 2: ANSI and ITU MSU Fields affected by the Global Title Translation Feature.........................33

    Figure 3: ANSI and ITU MSU Fields affected by the Enhanced Global Title Translation Feature......36

    Figure 4: Transaction-Based GTT Load Sharing SCCP Options...............................................................72

    Figure 5: Message Routing using Transaction-Based GTT Load Sharing...............................................74

    Figure 6: Message Relay Services and GTT Actions...................................................................................77

    Figure 7: Action When the Subsequent Translation Search Fails..............................................................83

    Figure 8: Action When the Subsequent SELID Search Fails .....................................................................84

    Figure 9: Action When the Same GTT Set Name is Referred to More Than Once.................................85

    Figure 10: Limiting the Number of Database Searches .............................................................................86

    Figure 11: Limiting the Number of GTT Set Searches ...............................................................................88

    Figure 12: Discard GTT Action Entry............................................................................................................97

    Figure 13: UDTS GTT Action Entry...............................................................................................................98

    Figure 14: TCAP Error GTT Action Entry....................................................................................................99

    Figure 15: Duplicate GTT Action Entry......................................................................................................100

    Figure 16: Forward GTT Action Entry........................................................................................................101

    Figure 17: Origin-Based SCCP Routing and XLAT=NONE....................................................................104

    Figure 18: Interaction between the FALLBACK Option and XLAT=NONE........................................104

    Figure 19: GTT Action Path Entry...............................................................................................................106

    Figure 20: GTT Translation and GTT Action Path Table Relationship..................................................107

    Figure 21: Example GTT Action Path Table Entry....................................................................................107

    Figure 22: GTT Translation Lookup - Exact GTT Action Path Match....................................................108

    viii910-6671-001 Revision B, February 2014

  • Figure 23: GTT Translation Lookup - No GTT Action Path Match........................................................109

    Figure 24: GTT Translation Lookup - Exact GTT Action Path Match (with Unspecified GTTSet-Value Combinations).........................................................................................................................110

    Figure 25: Logical View of SCCP Subsystems...........................................................................................123

    Figure 26: SCCP Message Flow through the EAGLE 5 ISS......................................................................124

    Figure 27: Example of Using Translation Type and Global Title Translation Tables..........................125

    Figure 28: Example of Using GTT Selector, GTT Set, and GTA Tables..................................................128

    Figure 29: EGTT Process................................................................................................................................131

    Figure 30: An Example of Double Translation Type Mapping...............................................................134

    ix910-6671-001 Revision B, February 2014

  • List of Tables

    Table 1: Admonishments................................................................................................................................20

    Table 2: Hex Digit Range Example................................................................................................................62

    Table 3: RC Group Weight Example.............................................................................................................65

    Table 4: RC Group In-Service Threshold States ..........................................................................................66

    Table 5: In-Service Threshold Example ........................................................................................................67

    Table 6: Load Shared Group with Weighted GTT Load Sharing Example.............................................68

    Table 7: Combined Dominant/Load Shared Group with Weighted GTT Load Sharing Example.......................................................................................................................................................................69

    Table 8: GTT Set Type and GTT Selector Combinations............................................................................76

    Table 9: Services Supporting Fallback to GTT.............................................................................................78

    Table 10: Exceptions to Fallback to GTT.......................................................................................................79

    Table 11: GTT Hierarchies...............................................................................................................................81

    Table 12: GTT Selector Key.............................................................................................................................89

    Table 13: CdPA GTT Selector Keys................................................................................................................90

    Table 14: CgPA GTT Selector Keys................................................................................................................90

    Table 15: Messages Generated by the EAGLE 5 ISS GTT Selector Keys..................................................91

    Table 16: Search Order for the TCAP Opcode Based Routing Feature Translations with an ANSIOpcode.........................................................................................................................................................94

    Table 17: Valid and Invalid ACN Values ....................................................................................................95

    Table 18: Search Order for the TCAP Opcode Based Routing Feature Translations with an ITUOpcode.........................................................................................................................................................95

    Table 19: GTT Action Events Recorded for Per-TT and System-Wide Measurements Reports ........105

    Table 20: GTT Action Events Recorded for Per-Path Measurements Reports .....................................105

    x910-6671-001 Revision B, February 2014

  • Table 21: GTT Selector Key for GTI=0.........................................................................................................113

    Table 22: Searching Order for CdPA GTI=0 GTT Selectors.....................................................................113

    Table 23: Searching Order for CgPA GTI=0 GTT Selectors.....................................................................114

    Table 24: SCCPMSGCNV Parameter Values ............................................................................................116

    Table 25: Parameter Values after UDT to XUDT or UDTS to XUDTS Conversion..............................116

    Table 26: Parameter Values after XUDT to UDT or XUDTS to UDTS Conversion..............................118

    Table 27: GTT Set and GTT Selector Advanced GTT Feature Default Parameter Values...................121

    Table 28: Use of Aliases in GTT Selector Table..........................................................................................122

    Table 29: MSU Fields Modified by Global Title Translation ...................................................................126

    Table 30: MSU Fields Modified by Enhanced Global Title Translation ................................................129

    Table 31: Service Module and Feature Combinations..............................................................................141

    Table 32: DSM Card Locations.....................................................................................................................143

    Table 33: ELAP-Based and EPAP-Based Features.....................................................................................145

    Table 34: SCCP Throughput Capacity........................................................................................................146

    Table 35: Number Service Module Cards in the System..........................................................................147

    Table 36: Concerned Signaling Point Code Configuration Table...........................................................158

    Table 37: MAP and MRN Point Code Parameter Combinations............................................................171

    Table 38: Maximum Number of True Point Code Entries.......................................................................173

    Table 39: Solitary Mated Application Parameter Combinations.............................................................184

    Table 40: MAP and MRN Point Code Parameter Combinations............................................................191

    Table 41: Maximum Number of True Point Code Entries.......................................................................192

    Table 42: Dominant Mated Application Parameter Combinations for the ENT-MAP Command.....207

    Table 43: Dominant Mated Application Parameter Combinations for the CHG-MAPCommand..................................................................................................................................................212

    Table 44: MAP and MRN Point Code Parameter Combinations............................................................219

    xi910-6671-001 Revision B, February 2014

  • Table 45: Load Shared Mated Application Parameter Combinations for the ENT-MAPCommand..................................................................................................................................................235

    Table 46: Load Shared Mated Application Parameter Combinations for the CHG-MAPCommand..................................................................................................................................................238

    Table 47: MAP and MRN Point Code Parameter Combinations............................................................246

    Table 48: Combined Dominant/Load Shared Mated Application Parameter Combinations forthe ENT-MAP Command........................................................................................................................261

    Table 49: Combined Dominant/Load Shared Mated Application Parameter Combinations forthe CHG-MAP Command.......................................................................................................................264

    Table 50: Subsystem Features.......................................................................................................................271

    Table 51: Mated Application Parameters....................................................................................................284

    Table 52: Mated Application Weight and In-Service Threshold Parameters........................................298

    Table 53: MAP and MRN Point Code Parameter Combinations............................................................309

    Table 54: Parameter Combinations for the ENT-MRN Command.........................................................327

    Table 55: Parameter Combinations for the CHG-MRN Command........................................................333

    Table 56: MRN and MAP Point Code Parameter Combinations............................................................385

    Table 57: GT Conversion Parameter Combinations..................................................................................390

    Table 58: GT Conversion Parameter Combinations..................................................................................400

    Table 59: Changing a Loopset Parameter Combinations.........................................................................424

    Table 60: SCCP Test Message Parameter Combinations..........................................................................428

    Table 61: NAIV/NAI Mapping....................................................................................................................431

    Table 62: NPV/NP Mapping........................................................................................................................431

    Table 63: Add GT Modification Parameter Values...................................................................................439

    Table 64: Change GT Modification Parameter Values..............................................................................451

    Table 65: RTRV-GTTSEL Parameters..........................................................................................................463

    Table 66: RTRV-GTTSEL GTT Set Name Parameters...............................................................................472

    xii910-6671-001 Revision B, February 2014

  • Table 67: SEAS and Global Title Translation Parameter Conversion.....................................................476

    Table 68: Feature Status.................................................................................................................................477

    Table 69: Valid Parameter Combinations for the ent-gtt Routing Parameters......................................479

    Table 70: RTRV-GTTSEL Parameters..........................................................................................................481

    Table 71: Add GTT Parameter Combinations............................................................................................497

    Table 72: SEAS and Global Title Translation Parameter Conversion.....................................................513

    Table 73: Feature Status.................................................................................................................................514

    Table 74: Valid Parameter Combinations for the chg-gtt Routing Parameters.....................................516

    Table 75: RTRV-GTTSEL Parameters..........................................................................................................518

    Table 76: Change GTT Parameter Combinations......................................................................................531

    Table 77: GTT Set Types................................................................................................................................538

    Table 78: GTT Set Parameter Combinations - Only the EGTT feature is on..........................................539

    Table 79: GTT Set Parameter Combinations - The OBSR Feature is Enabled, the FLOBR or theTOBR Features are Enabled or Turned On...........................................................................................539

    Table 80: SETTYPE Feature Requirements.................................................................................................541

    Table 81: RTRV-GTTSEL Parameters..........................................................................................................549

    Table 82: NAIV/NAI Mapping....................................................................................................................558

    Table 83: NPV/NP Mapping........................................................................................................................559

    Table 84: Add GTT Selector Parameter Combinations - EGTT Only.....................................................564

    Table 85: Add GTT Selector Parameter Combinations - Origin-Based SCCP Routing EnabledOnly............................................................................................................................................................565

    Table 86: Add GTT Selector Parameter Combinations - Flexible Linkset Optional Based RoutingEnabled and Turned On Only................................................................................................................568

    Table 87: Add GTT Selector Parameter Combinations - OBSR Enabled and FLOBR Enabled andTurned On.................................................................................................................................................570

    Table 88: Add GTT Selector Parameter Combinations - FLOBR and TOBR Enabled and TurnedOn Only......................................................................................................................................................573

    xiii910-6671-001 Revision B, February 2014

  • Table 89: Add GTT Selector Parameter Combinations - OBSR Enabled, and FLOBR and TOBREnabled and Turned On..........................................................................................................................575

    Table 90: NAIV/NAI Mapping....................................................................................................................579

    Table 91: NPV/NP Mapping........................................................................................................................580

    Table 92: Remove GTT Selector Parameter Combinations - GTI=2 or GTI=4.......................................581

    Table 93: Remove GTT Selector Parameter Combinations - GTI=0........................................................583

    Table 94: NAIV/NAI Mapping....................................................................................................................585

    Table 95: NPV/NP Mapping........................................................................................................................586

    Table 96: Change GTT Selector Parameter Combinations - EGTT Only................................................588

    Table 97: Change GTT Selector Parameter Combinations - Origin-Based SCCP Routing EnabledOnly............................................................................................................................................................590

    Table 98: Change GTT Selector Parameter Combinations - CDGTTSN and CGGTTSN ColumnsShown in the RTRV-GTTSEL Output....................................................................................................592

    Table 99: GTTSN and OPTSN Combinations............................................................................................596

    Table 100: GTA Parameter Combinations - No SETTYPE Column in RTRV-GTTSET Output.........602

    Table 101: GTTSN = CDGTA GTT Set Parameter Combinations...........................................................603

    Table 102: GTTSN = CGGTA GTT Set Parameter Combinations...........................................................605

    Table 103: GTTSN = CGPC GTT Set Parameter Combinations...............................................................607

    Table 104: GTTSN = CGSSN GTT Set Parameter Combinations............................................................608

    Table 105: GTTSN = OPC GTT Set Parameter Combinations.................................................................609

    Table 106: GTTSN = CDSSN GTT Set Parameter Combinations............................................................611

    Table 107: GTTSN = OPCODE GTT Set Parameter Combinations.........................................................612

    Table 108: GTTSN = DPC GTT Set Parameter Combinations.................................................................614

    Table 109: Optional GTA Parameters..........................................................................................................616

    Table 110: Feature Requirements for ENT-GTA Parameters...................................................................619

    Table 111: DLT-GTA Parameter Combinations - EGTT Only.................................................................635

    xiv910-6671-001 Revision B, February 2014

  • Table 112: DLT-GTA Parameter Combinations - GTT Sets CDGTA, CGGTA, CGSSN, CGPC,OPC.............................................................................................................................................................636

    Table 113: DLT-GTA Parameter Combinations - GTT Sets CDSSN, DPC, and OPCODE..................637

    Table 114: GTTSN and OPTSN Combinations..........................................................................................645

    Table 115: GTA Parameter Combinations - No SETTYPE Column in RTRV-GTTSET Output.........653

    Table 116: GTTSN = CDGTA GTT Set Parameter Combinations...........................................................654

    Table 117: GTTSN = CGGTA GTT Set Parameter Combinations...........................................................655

    Table 118: GTTSN = CGPC GTT Set Parameter Combinations...............................................................657

    Table 119: GTTSN = CGSSN GTT Set Parameter Combinations............................................................658

    Table 120: GTTSN = OPC GTT Set Parameter Combinations.................................................................659

    Table 121: GTTSN = CDSSN GTT Set Parameter Combinations............................................................660

    Table 122: GTTSN = OPCODE GTT Set Parameter Combinations.........................................................662

    Table 123: GTTSN = DPC GTT Set Parameter Combinations.................................................................663

    Table 124: Optional GTA Parameters..........................................................................................................664

    Table 125: Feature Requirements for CHG-GTA Parameters..................................................................671

    Table 126: Default GTT Mode Option Parameter Combinations............................................................688

    Table 127: GTT Actions Parameter Combinations....................................................................................699

    Table 128: GTT Actions Features Part Numbers.......................................................................................732

    Table 129: TOBR Opcode Quantity Part Numbers....................................................................................833

    Table 130: GTT Actions Features Part Numbers.......................................................................................836

    Table 131: NAIV/NAI Mapping..................................................................................................................859

    Table 132: NPV/NP Mapping......................................................................................................................860

    Table 133: Parameter Combinations for Adding Service Selectors for the MO SMS B-Party RoutingFeature........................................................................................................................................................865

    Table 134: NAIV/NAI Mapping..................................................................................................................868

    Table 135: NPV/NP Mapping......................................................................................................................868

    xv910-6671-001 Revision B, February 2014

  • Table 136: Parameter Combinations for Removing Service Selectors....................................................869

    Table 137: NAIV/NAI Mapping..................................................................................................................872

    Table 138: NPV/NP Mapping......................................................................................................................872

    Table 139: Parameter Combinations for Changing Service Selectors for the MO SMS B-PartyRouting Feature........................................................................................................................................876

    Table 140: CHG-PPSOPTS Parameter Combinations...............................................................................891

    xvi910-6671-001 Revision B, February 2014

  • Chapter

    1Introduction

    Chapter 1, Introduction, contains an overview ofthe features described in this manual, considerations

    Topics:

    Overview.....18 when upgrading from the Global Title Translation Scope and Audience.....19 (GTT) feature to the Enhanced Global Title

    Translation (EGTT) feature, general information Manual Organization.....19about the database, and the organization of thismanual.

    Documentation Admonishments.....19 Customer Care Center.....20 Emergency Response.....22 Related Publications.....23 Documentation Availability, Packaging, and

    Updates.....23 Locate Product Documentation on the Customer

    Support Site.....24 Maintenance and Administration Subsystem....24 EAGLE 5 ISS Database Partitions.....25

    17910-6671-001 Revision B, February 2014

  • Overview

    The Database Administration Manual Global Title Translation describes the procedures used to configurethe EAGLE 5 ISS and its database to implement these features:

    Global Title Translation Enhanced Global Title Translation Variable-Length Global Title Translation Advanced GT Modification Intermediate GTT Load Sharing ANSI/ITU SCCP Conversion Flexible GTT Load Sharing Origin-Based SCCP Routing Hex Digit Support for GTT Weighted GTT Load Sharing Transaction-Based GTT Load Sharing SCCP Loop Detection MOSMSB-Party Routing MO SMS Prepaid Intercept on B-Party GTT Loadsharing between ITU Network Types GTT Loadsharing with Alternate Routing Indicator Support for 16 GTT Lengths in VGTT Flexible Linkset Optional Based Routing (FLOBR) TCAP Opcode Based Routing (TOBR) GTT Actions XUDT UDT Conversion

    Note: Before enabling any of these features, make sure you have purchased the feature to be turnedon. If you are not sure whether you have purchased the feature to be turned on, contact your TekelecSales Representative or Account Representative.

    Note: Database administration privileges are password restricted. Only those persons with access tothe command class Database Administration can execute the administrative functions. Refer to theCommands Manual for more information on command classes and commands allowed by those classes.

    It is possible for two or more users to make changes to the same database element at any time duringtheir database administration sessions. It is strongly recommended that only one user at a time makeany changes to the database.

    Throughout this manual, these terms are used to refer to either the original card or the EPM-B versionor other replacement version of the card unless one of the card types is specifically required.

    E5-ENET - the original E5-ENET or the E5-ENET-B card E5-ATM - the original E5-ATM or the E5-ATM-B card E5-IPSM - the original E5-IPSM or the E5-ENET-B card that is running the IPSHC GPL E5-SM4G - the original E5-SM4G or the E5-SM8G-B card (not an EPM-B card) MCPM - the original MCPM or the E5-MCPM-B card

    18910-6671-001 Revision B, February 2014

    IntroductionDatabase Administration Manual - Global TitleTranslation

  • Scope and Audience

    This manual is intended for database administration personnel or translations personnel responsiblefor configuring the EAGLE 5 ISS and its database to implement the Global Title Translation featureand the related features shown in the Overview section.

    Manual Organization

    Throughout this document, the terms database and system software are used. Database refers to alldata that can be administered by the user, including shelves, cards, links, routes, global title translationtables, and gateway screening tables. System software refers to data that cannot be administered bythe user, including generic program loads (GPLs).

    This document is organized into the following sections.

    Introduction contains an overview of the features described in this manual, considerations whenupgrading from the Global Title Translation (GTT) feature to the Enhanced Global Title Translation(EGTT) feature, general information about the database, and the organization of this manual.

    Global Title Translation (GTT) Overview describes the Global Title Translation feature and the procedurescommon to both the Global Title Translation (GTT) and Enhanced Global Title Translation (EGTT)features. This chapter also describes the features shown in the Overview section.

    Global Title Translation (GTT) Configuration contains the procedures specific to configure the global titletranslation feature.

    Enhanced Global Title Translation (EGTT) Configuration contains the procedures specific to configurethe enhanced global title translation feature.

    Controlled Feature Activation Procedures describes the procedures necessary to activate and deactivatefeatures (features that require a feature access key to be activated) contained in this manual.

    MO SMS B-Party Routing Configuration Procedures describes the procedures necessary to configure theEAGLE 5 ISS to perform global title translation on the MAP B-Party digits instead of the GTT calledparty address of the message.

    MO SMS Prepaid Intercept on B-Party Configuration Procedures describes the procedures necessary toconfigure the EAGLE 5 ISS to redirect MO SMS messages from a prepaid B-party subscriber to aspecific SMSC.

    Documentation Admonishments

    Admonishments are icons and text throughout this manual that alert the reader to assure personalsafety, to minimize possible service interruptions, and to warn of the potential for equipment damage.

    19910-6671-001 Revision B, February 2014

    IntroductionDatabase Administration Manual - Global TitleTranslation

  • Table 1: Admonishments

    DescriptionIcon

    Danger:

    (This icon and text indicate the possibility ofpersonal injury.)

    Warning:

    (This icon and text indicate the possibility ofequipment damage.)

    Caution:

    (This icon and text indicate the possibility ofservice interruption.)

    Topple:

    (This icon and text indicate the possibility ofpersonal injury and equipment damage.)

    Customer Care Center

    The Tekelec Customer Care Center is your initial point of contact for all product support needs. Arepresentative takes your call or email, creates a Customer Service Request (CSR) and directs yourrequests to the Tekelec Technical Assistance Center (TAC). Each CSR includes an individual trackingnumber. Together with TAC Engineers, the representative will help you resolve your request.

    The Customer Care Center is available 24 hours a day, 7 days a week, 365 days a year, and is linkedto TAC Engineers around the globe.

    Tekelec TAC Engineers are available to provide solutions to your technical questions and issues 7days a week, 24 hours a day. After a CSR is issued, the TAC Engineer determines the classification ofthe trouble. If a critical problem exists, emergency procedures are initiated. If the problem is not critical,normal support procedures apply. A primary Technical Engineer is assigned to work on the CSR andprovide a solution to the problem. The CSR is closed when the problem is resolved.

    Tekelec Technical Assistance Centers are located around the globe in the following locations:

    Tekelec - Global

    Email (All Regions): [email protected]

    USA and Canada

    Phone:

    1-888-367-8552 (toll-free, within continental USA and Canada)

    1-919-460-2150 (outside continental USA and Canada)

    20910-6671-001 Revision B, February 2014

    IntroductionDatabase Administration Manual - Global TitleTranslation

  • TAC Regional Support Office Hours:

    8:00 a.m. through 5:00 p.m. (GMT minus 5 hours), Monday through Friday, excluding holidays

    Caribbean and Latin America (CALA)

    Phone:

    +1-919-460-2150

    TAC Regional Support Office Hours (except Brazil):

    10:00 a.m. through 7:00 p.m. (GMT minus 6 hours), Monday through Friday, excluding holidays

    Argentina

    Phone:

    0-800-555-5246 (toll-free)

    Brazil

    Phone:

    0-800-891-4341 (toll-free)

    TAC Regional Support Office Hours:

    8:00 a.m. through 5:48 p.m. (GMT minus 3 hours), Monday through Friday, excluding holidays

    Chile

    Phone:

    1230-020-555-5468

    Colombia

    Phone:

    01-800-912-0537

    Dominican Republic

    Phone:

    1-888-367-8552

    Mexico

    Phone:

    001-888-367-8552

    Peru

    Phone:

    0800-53-087

    Puerto Rico

    Phone:

    1-888-367-8552

    Venezuela

    21910-6671-001 Revision B, February 2014

    IntroductionDatabase Administration Manual - Global TitleTranslation

  • Phone:

    0800-176-6497

    Europe, Middle East, and Africa

    Regional Office Hours:

    8:30 a.m. through 5:00 p.m. (GMT), Monday through Friday, excluding holidays

    Signaling

    Phone:

    +44 1784 467 804 (within UK)

    Software Solutions

    Phone:

    +33 3 89 33 54 00

    Asia

    India

    Phone:

    +91-124-465-5098 or +1-919-460-2150

    TAC Regional Support Office Hours:

    10:00 a.m. through 7:00 p.m. (GMT plus 5 1/2 hours), Monday through Saturday, excludingholidays

    Singapore

    Phone:

    +65 6796 2288

    TAC Regional Support Office Hours:

    9:00 a.m. through 6:00 p.m. (GMT plus 8 hours), Monday through Friday, excluding holidays

    Emergency Response

    In the event of a critical service situation, emergency response is offered by the Tekelec Customer CareCenter 24 hours a day, 7 days a week. The emergency response provides immediate coverage, automaticescalation, and other features to ensure that the critical situation is resolved as rapidly as possible.

    A critical situation is defined as a problem with the installed equipment that severely affects service,traffic, or maintenance capabilities, and requires immediate corrective action. Critical situations affectservice and/or system operation resulting in one or several of these situations:

    A total system failure that results in loss of all transaction processing capability Significant reduction in system capacity or traffic handling capability

    22910-6671-001 Revision B, February 2014

    IntroductionDatabase Administration Manual - Global TitleTranslation

  • Loss of the systems ability to perform automatic system reconfiguration Inability to restart a processor or the system Corruption of system databases that requires service affecting corrective actions Loss of access for maintenance or recovery operations Loss of the system ability to provide any required critical or major trouble notification

    Any other problem severely affecting service, capacity/traffic, billing, and maintenance capabilitiesmay be defined as critical by prior discussion and agreement with the Tekelec Customer Care Center.

    Related Publications

    For information about additional publications that are related to this document, refer to the RelatedPublications document. The Related Publications document is published as a part of the ReleaseDocumentation and is also published as a separate document on the Tekelec Customer Support Site.

    Documentation Availability, Packaging, and Updates

    Tekelec provides documentation with each system and in accordance with contractual agreements.For General Availability (GA) releases, Tekelec publishes a complete EAGLE 5 ISS documentation set.For Limited Availability (LA) releases, Tekelec may publish a documentation subset tailored to specificfeature content or hardware requirements. Documentation Bulletins announce a new or updatedrelease.

    The Tekelec EAGLE 5 ISS documentation set is released on an optical disc. This format allows for easysearches through all parts of the documentation set.

    The electronic file of each manual is also available from the Tekelec Customer Support site. This siteallows for 24-hour access to the most up-to-date documentation, including the latest versions of FeatureNotices.

    Printed documentation is available for GA releases on request only and with a lead time of six weeks.The printed documentation set includes pocket guides for commands and alarms. Pocket guides mayalso be ordered separately. Exceptions to printed documentation are:

    Hardware or Installation manuals are printed without the linked attachments found in the electronicversion of the manuals.

    The Release Notice is available only on the Customer Support site.

    Note: Customers may print a reasonable number of each manual for their own use.

    Documentation is updated when significant changes are made that affect system operation. Updatesresulting from Severity 1 and 2 Problem Reports (PRs) are made to existing manuals. Other changesare included in the documentation for the next scheduled release. Updates are made by re-issuing anelectronic file to the customer support site. Customers with printed documentation should contacttheir Sales Representative for an addendum. Occasionally, changes are communicated first with aDocumentation Bulletin to provide customers with an advanced notice of the issue until officiallyreleased in the documentation. Documentation Bulletins are posted on the Customer Support site andcan be viewed per product and release.

    23910-6671-001 Revision B, February 2014

    IntroductionDatabase Administration Manual - Global TitleTranslation

    https://secure.tekelec.com/OA_HTML/ibuhpage.jsp

  • Locate Product Documentation on the Customer Support Site

    Access to Tekelec's Customer Support site is restricted to current Tekelec customers only. This sectiondescribes how to log into the Tekelec Customer Support site and locate a document. Viewing thedocument requires Adobe Acrobat Reader, which can be downloaded at www.adobe.com.

    1. Log into the Tekelec Customer Support site.

    Note: If you have not registered for this new site, click the Register Here link. Have your customernumber available. The response time for registration requests is 24 to 48 hours.

    2. Click the Product Support tab.3. Use the Search field to locate a document by its part number, release number, document name, or

    document type. The Search field accepts both full and partial entries.4. Click a subject folder to browse through a list of related files.5. To download a file to your location, right-click the file name and select Save Target As.

    Maintenance and Administration Subsystem

    The Maintenance and Administration Subsystem (MAS) is the central management point for theEAGLE 5. The MAS provides user interface, maintenance communication, peripheral services, alarmprocessing, system disk interface, and measurements. Management and redundancy are provided byuse of two separate subsystem processors.

    The MAS resides on two separate sets of Maintenance and Administration Subsystem Processor(MASP) cards and a Maintenance Disk and Alarm card (collectively referred to as control cards). Thecontrol cards are located in slots 1113 through 1118 of the EAGLE 5 control shelf. The control cardsmust be E5-based cards.

    E5-based Control Cards

    The E5-based set of EAGLE 5 control cards consists of the following cards:

    Two Maintenance and Administration Subsystem Processor cards (E5-MASP) cards. Each dual-slotE5-MASP card is made up of the following two modules:

    Maintenance Communication Application Processor (E5-MCAP) card Terminal Disk Module (E5-TDM) card

    One Maintenance Disk and Alarm card (E5-MDAL card)

    Maintenance Communication Application Processor (E5-MCAP) Card

    The E5-MCAP card contains the Communications Processor and Applications Processor and providesconnections to the IMT bus. The card controls the maintenance and database administration activityand performs both application and communication processing. E5-MCAP cards are located in slots1113 and 1115 of the control shelf.

    Each E5-MCAP card contains two USB ports. One latched USB port is used with removable flashmedia (thumb drives), and one flush-mounted USB port is used with a plug-in flash drive. The

    24910-6671-001 Revision B, February 2014

    IntroductionDatabase Administration Manual - Global TitleTranslation

    https://secure.tekelec.com/OA_HTML/ibuhpage.jsp

  • removable media drive in the latched USB port is used to install and back up customer data. Theflush-mounted USB port is used for upgrade and could be used for disaster recovery.

    Terminal Disk Module (E5-TDM) Card

    The E5-TDM card provides the Terminal Processor for the 16 I/O ports, and interfaces to theMaintenance Disk and Alarm (E5-MDAL) card and fixed disk storage. The E5-TDM card also distributesComposite Clocks and High Speed Master clocks throughout the EAGLE 5, and distributes Shelf IDto the EAGLE 5. Each E5-TDM card contains one fixed SATA drive that is used to store primary andbackup system databases, measurements, and Generic Program Loads (GPLs). E5-TDM cards arelocated in slots 1114 and 1116 of the control shelf.

    Maintenance Disk and Alarm (E5-MDAL) Card

    The E5-MDAL card processes alarm requests and provides fan control. There is only one E5-MDALcard in a control card set. Critical, major, and minor system alarms are provided for up to 6 individualframes. In addition to the 3 system alarms, the E5-MDAL card provides the system audible alarm.The E5-MDAL card provides control of fans on a per-frame basis, and allows for each fan relay to beset individually. The E5-MDAL card is located in slots 1117 and 1118 of the control shelf.

    EAGLE 5 ISS Database Partitions

    The data that the EAGLE 5 uses to perform its functions are stored in two separate areas: the fixeddisk drives, and the removable cartridge. The following sections describe these areas and data that isstored on them. These areas and their partitions are shown in Figure 1: EAGLE 5 ISS Database Partitions(E5-Based Control Cards).

    25910-6671-001 Revision B, February 2014

    IntroductionDatabase Administration Manual - Global TitleTranslation

  • Figure 1: EAGLE 5 ISS Database Partitions (E5-Based Control Cards)

    Fixed Disk Drive

    There are two fixed disk drives on the EAGLE 5. The fixed disk drives contain the master set of dataand programs for the EAGLE 5. The two fixed disk drives are located on the terminal disk modules(E5-TDMs). Both disks have the same files. The data stored on the fixed disks is partially replicatedon the various cards in the EAGLE 5. Changes made during database administration sessions are sentto the appropriate cards.

    The data on the fixed disks can be viewed as four partitions.

    Current partition

    26910-6671-001 Revision B, February 2014

    IntroductionDatabase Administration Manual - Global TitleTranslation

  • Backup partition

    Measurements partition

    Generic program loads (GPLs) partition

    The data which can be administered by users is stored in two partitions on the fixed disk, a currentdatabase partition which has the tables which are changed by on-line administration, and a backupdatabase partition which is a user-controlled copy of the current partition.

    All of the on-line data administration commands affect the data in the current partition. The purposeof the backup partition is to provide the users with a means of rapidly restoring the database to aknown good state if there has been a problem while changing the current partition.

    A full set of GPLs is stored on the fixed disk, in the GPL partition. There is an approved GPL and atrial GPL for each type of GPL in this set and a utility GPL, which has only an approved version.Copies of these GPLs are downloaded to the EAGLE 5 cards. The GPL provides each card with itsfunctionality. For example, the ss7ansi GPL provides MTP functionality for link interface modules(LIMs).

    Measurement tables are organized as a single partition on the fixed disk. These tables are used asholding areas for the measurement counts.

    Removable Media

    The removable media is used with the E5-MCAP card portion of the E5-MASP in card locations 1113and 1115.

    The removable media is used for two purposes.

    To hold an off-line backup copy of the administered data and system GPLs

    To hold a copy of the measurement tables

    Because of the size of the data stored on the fixed disk drives on the E5-TDMs, a single removablemedia cannot store all of the data in the database, GPL and measurements partitions.

    To use a removable media to hold the system data, it must be formatted for system data. To use aremovable media to hold measurements data, it must be formatted for measurements data. The EAGLE5 provides the user the ability to format a removable media for either of these purposes. A removablemedia can be formatted on the EAGLE 5 by using the format-disk command. More informationon the format-disk command can be found in Commands Manual. More information on the removablemedia drives can be found in Hardware.

    Additional and preformatted removable media are available from the Customer Care Center.

    27910-6671-001 Revision B, February 2014

    IntroductionDatabase Administration Manual - Global TitleTranslation

  • Chapter

    2Global Title Translation (GTT) Overview

    Chapter 2, Global Title Translation (GTT) Overview,describes the Global Title Translation feature and

    Topics:

    Introduction.....31 the procedures common to both the Global Title Global Title Translation Feature.....31 Translation (GTT) and Enhanced Global Title

    Translation (EGTT) features. This chapter alsodescribes the features shown in the Overview section.

    Enhanced Global Title Translation Feature.....34 Variable-length Global Title Translation

    Feature.....38 Advanced GT Modification Feature.....40 Intermediate GTT Load Sharing Feature.....42 ANSI/ITU SCCP Conversion Feature.....42 Support of SCCP XUDT Messages.....45 In-Sequence Delivery of Class 1 UDT

    Messages.....46 Flexible GTT Load Sharing.....47 Origin-Based SCCP Routing.....55 Hex Digit Support for GTT.....61 Weighted GTT Load Sharing.....63 Transaction-Based GTT Load Sharing.....70 SCCP Loop Detection.....75 Flexible Linkset Optional Based Routing.....76 TCAP Opcode Based Routing.....92 GTT Actions.....97 MTP Routed Global Title Translation.....111 Unique GTT Selectors.....112 XUDT UDT Conversion Feature.....115 Upgrading from Global Title Translation (GTT) to

    Enhanced Global Title Translation (EGTT).....120 SCCP Overview.....122 GTT Configuration.....135 EGTT Configuration.....138 Adding a Service Module.....141 Removing a Service Module.....151

    28910-6671-001 Revision B, February 2014

  • Adding a Mapped SS7 Message TranslationType.....153

    Removing a Mapped SS7 Message TranslationType.....155

    Changing a Mapped SS7 Message TranslationType.....156

    Adding a Concerned Signaling Point Code.....157 Removing a Concerned Signaling Point Code..166 Provisioning a Solitary Mated Application.....170 Provisioning a Dominant Mated Application..189 Provisioning a Load Shared Mated

    Application.....217 Provisioning a Combined Dominant/Load Shared

    Mated Application.....244 Removing a Mated Application.....269 Changing the Attributes of a Mated

    Application.....283 Changing the Mated Application Type.....291 Changing the Weight and In-Service Threshold

    Values of a Mated Application.....298 Changing the MRNSET and MRN Point Code

    Values of MAP Entries.....308 Provisioning MRN Entries.....313 Removing MRN Entries.....342 Changing the Relative Cost Values of MRN

    Entries.....352 Changing MRN Entries with the ESWT

    Parameter.....360 Changing the Weight and Threshold Values of

    MRN Entries.....369 Changing the MAPSET, MAP Point Code, and

    MAP SSN Values of MRN Entries.....384 Adding a GT Conversion Table Entry.....388 Removing a GT Conversion Table Entry.....393 Changing a GT Conversion Table Entry.....396 Changing the ANSI/ITU SCCP Conversion

    Options.....402 Changing SCCP Class 1 Sequencing Option...404 Changing the SCCP Alarm Thresholds.....406 Changing the Transaction-Based GTT Load

    Sharing Options.....409 Adding a Loopset.....411 Removing a Loopset.....414 Changing the Attributes of a Loopset.....418

    29910-6671-001 Revision B, February 2014

    Global Title Translation (GTT) OverviewDatabase Administration Manual - Global TitleTranslation

  • Configuring the ANSI to ITU-N SCCP ConversionOption.....426

    Configuring a SCCP Test Message.....428 Adding Global Title Modification Information.435 Removing Global Title Modification

    Information.....440 Changing Global Title Modification

    Information.....447 Changing the MTP-Routed GTT Options.....453

    30910-6671-001 Revision B, February 2014

    Global Title Translation (GTT) OverviewDatabase Administration Manual - Global TitleTranslation

  • Introduction

    This chapter describes the Global Title Translation (GTT) and the Enhanced Global Title Translation(EGTT) features and these optional add-on features.

    Variable-length Global Title Translation Advanced GT Modification Intermediate GTT Load Sharing ANSI/ITU SCCP Conversion Flexible GTT Load Sharing Origin-Based SCCP Routing Hex Digit Support for GTT Weighted GTT Load Sharing Transaction-Based GTT Load Sharing SCCP Loop Detection Flexible Linkset Optional Based Routing TCAP Opcode Based Routing GTT Actions XUDT UDT Conversion

    This chapter also contains the procedures that are common to configuring either the Global TitleTranslation (GTT) feature or the Enhanced Global Title Translation (EGTT) feature. To find out aboutthe differences between Global Title Translation feature and the Enhanced Global Title Translationfeature, refer to the Upgrading from Global Title Translation (GTT) to Enhanced Global Title Translation(EGTT) section.

    Global Title Translation Feature

    The Global Title Translation (GTT) feature is designed for the signaling connection control part (SCCP)of the SS7 protocol. The EAGLE 5 ISS uses this feature to determine to which service database to sendthe query message when a Message Signaling Unit (MSU) enters the EAGLE 5 ISS and more informationis needed to route the MSU.

    If an MSU enters the EAGLE 5 ISS and more information is needed to route the MSU, the SCCP of theSS7 protocol sends a query to a service database to obtain the information. The EAGLE 5 ISS uses theGTT feature for the SCCP to determine which service database to send the query messages to. Theseservice databases are also used to verify calling card numbers and credit card numbers. The servicedatabases are identified in the SS7 network by a point code and a subsystem number.

    The GTT feature uses global title address (GTA) information to determine the destination of the MSU.The translation type (TT) indicates which global title translation table is used to determine the routingto a particular service database. Each global title translation table includes the point code (pc) of thenode containing the service database, the subsystem number (ssn) identifying the service database onthat node, and a routing indicator (ri). The routing indicator determines if further global title translationsare required. GTA and TT are contained in the called party address (CDPA) field of the MSU.

    31910-6671-001 Revision B, February 2014

    Global Title Translation (GTT) OverviewDatabase Administration Manual - Global TitleTranslation

  • The global title translation feature changes the destination point code and the origination point codein the routing label. The global title information is not altered. The routing label is changed to indicatethe new destination point code retrieved from the global title translation and the origination pointcode is set to the EAGLE 5 ISSs point code.

    Depending on how the global title translation data is configured, the routing indicator, the subsystemnumber, or the translation type in the called party address may also be changed by the global titletranslation feature. The gray shaded areas in Figure 2: ANSI and ITU MSU Fields affected by the GlobalTitle Translation Feature show the message fields affected by global title translation.

    32910-6671-001 Revision B, February 2014

    Global Title Translation (GTT) OverviewDatabase Administration Manual - Global TitleTranslation

  • Figure 2: ANSI and ITU MSU Fields affected by the Global Title Translation Feature

    The GTT feature allows global title translation on global title addresses of fixed length. There are threeoptional add-on features that enhance the functionality of the global title translation feature:

    33910-6671-001 Revision B, February 2014

    Global Title Translation (GTT) OverviewDatabase Administration Manual - Global TitleTranslation

  • The Variable-length Global Title Translation feature (VGTT) feature allows global title translationon global title addresses of varying length. For more information on this feature, refer to theVariable-length Global Title Translation Feature section.

    The Advanced GT Modification feature allows the EAGLE 5 ISS to modify other fields of an MSUin addition to the translation type when the MSU requires further global title translation and thetranslation type is to be replaced. For more information about this feature, refer to the AdvancedGT Modification Feature section.

    The ANSI/ITU SCCP Conversion Feature converts SCCP messages between the ANSI and ITUformats. For more information about this feature, refer to the ANSI/ITU SCCP ConversionFeaturesection.

    The EAGLE 5 ISS supports:

    269,999, 400,000, or 1,000,000 global title translations. The system default is 269,999 global titletranslations. This quantity can be increased to 400,000 by enabling the feature access key for partnumber 893-0061-01, or to 1,000,000 by enabling the feature access key for part number 893-0061-10.For more information on enabling these feature access keys, refer to the Enabling the XGTT TableExpansion Feature procedure.

    A maximum of 200,000 global title translations assigned to a translation type. 512 translation types, 256 translation types for ANSI MSUs, and 256 translation types for ITU MSUs. 1024, 2000, or 3000 remote point codes (mated applications), with up to 10 subsystems at each point

    code. The system default is 1024 mated applications. This quantity can be increased to 2000 byenabling the feature access key for part number 893-0077-01, or to 3000 by enabling the featureaccess key for part number 893-0077-10. For more information on enabling these feature accesskeys, refer to the Enabling the XMAP Table Expansion Feature procedure.

    The GTT feature requires one of the following cards:

    Database Services Module (DSM) EAGLE 5-Service Module 4GB (E5-SM4G) E5-SM8G-B

    For more information on these cards, refer to the Adding a Service Module procedure or to the HardwareManual - EAGLE 5 ISS.

    Enhanced Global Title Translation Feature

    The Enhanced Global Title Translation (EGTT) feature is designed for the signaling connection controlpart (SCCP) of the SS7 protocol. The EAGLE 5 ISS uses this feature to determine to which servicedatabase to send the query message when a Message Signaling Unit (MSU) enters the EAGLE 5 ISSand more information is needed to route the MSU.

    If an MSU enters the EAGLE 5 ISS and more information is needed to route the MSU, the SCCP of theSS7 protocol sends a query to a service database to obtain the information. The EAGLE 5 ISS uses theEGTT feature for the SCCP to determine which service database to send the query messages to. Theservice databases are identified in the SS7 network by a point code and a subsystem number.

    The EGTT feature uses global title information (GTI) to determine the destination of the MSU. TheEAGLE 5 ISS supports ANSI GTI format 2 and ITU GTI formats 2 and 4. The GTI is contained in thecalled party address (CDPA) field of the MSU. For ITU GTI format 4, the GTI is made up of theNumbering Plan (NP), Nature of Address Indicator (NAI), and Translation Type (TT) selectors.

    34910-6671-001 Revision B, February 2014

    Global Title Translation (GTT) OverviewDatabase Administration Manual - Global TitleTranslation

  • The EGTT feature allows global title translation on global title addresses of fixed length. There arethree optional add-on features that enhance the functionality of the enhanced global title translationfeature:

    The Variable-length Global Title Translation feature (VGTT), allows global title translation onglobal title addresses of varying length. For more information on this feature, refer to theVariable-length Global Title Translation Featuresection.

    The Advanced GT Modification feature allows the EAGLE 5 ISS to modify other fields of an MSUin addition to the translation type when the MSU requires further global title translation and thetranslation type is to be replaced. For more information about this feature, refer to the sectionAdvanced GT Modification Feature.

    The ANSI/ITU SCCP Conversion Feature converts SCCP messages between the ANSI and ITUformats. For more information about this feature, refer to the ANSI/ITU SCCP Conversion Featuresection.

    The EGTT feature requires one of the following cards:

    Database Services Module (DSM) EAGLE 5-Service Module 4GB (E5-SM4G) or E5-SM8G-B

    For more information on these cards, refer to the Adding a Service Module procedure or to the HardwareManual - EAGLE 5 ISS.

    Inclusion of SSN in the CDPA

    When the obtained translation data contains a subsystem, the translated SSN is placed in the SCCPCDPA before the message is sent to the next node. However, when no SSN is present in the CDPA,this insertion applies to ITU messages only. ANSI messages that do not contain an SSN in the CDPAwill be rejected. The gray shaded areas in Figure 3: ANSI and ITU MSU Fields affected by the EnhancedGlobal Title Translation Feature show the message fields affected by enhanced global title translation.

    35910-6671-001 Revision B, February 2014

    Global Title Translation (GTT) OverviewDatabase Administration Manual - Global TitleTranslation

  • Figure 3: ANSI and ITU MSU Fields affected by the Enhanced Global Title Translation Feature

    Inclusion of OPC in the CGPA

    When an ITU unitdata (UDT) message does not have a point code (PC) present in the CGPA, and theCGPA route indicator (RI) is set to Route on SSN, the EGTT feature will insert the OPC from the

    36910-6671-001 Revision B, February 2014

    Global Title Translation (GTT) OverviewDatabase Administration Manual - Global TitleTranslation

  • Message Transfer Part (MTP) routing label into the CGPA before sending the message to the nextnode. The insertion does not apply to ANSI GTT processing.

    Deletion of GT

    The EGTT feature allows a Global Title (GT) in the CDPA to be deleted. For example, when the resultof a GTT performed by the EAGLE 5 ISS is set to Route on SSN, there may be some end nodes thatdo not want to receive the GT information in the CDPA. The enhancement provides an option on aper translation basis (for both ANSI and ITU) to allow the GT to be deleted(ent-gta:gta=000:ri=ssn:ccgt=yes command). The option is not valid when the result of theGT is the EAGLE 5 ISSs point code and local SSN.

    New Commands

    The EGTT feature introduces three new command sets:

    GTTSET commands

    ENT-GTTSET Enter GTT Set CHG-GTTSET Change GTT Set DLT-GTTSET Delete GTT Set RTRV-GTTSET Retrieve GTT Set

    GTTSEL commands

    ENT-GTTSEL Enter GTT Selector CHG-GTTSEL Change GTT Selector DLT-GTTSEL Delete GTT Selector RTRV-GTTSEL Retrieve GTT Selector

    GTA commands

    ENT-GTA Enter Global Title Address CHG-GTA Change Global Title Address DLT-GTA Delete Global Title Address RTRV-GTA Retrieve Global Title Address

    GTT Set Commands

    The GTT Set commands are used to provision new sets of GTTs, linking GTT Selector (-GTTSEL) andGlobal Title Address (-GTA) commands. This set of commands provides greater flexibility whenprovisioning the type of messages that require Global Title Translation. There are no SEAS equivalentsfor these commands.

    GTT Selector Commands

    The GTT Selector commands are used to provision new selectors for global title translation. Togetherwith the GTT Set commands, these commands replace the Translation Type (-TT) commands, providinggreater flexibility when provisioning the type of messages that require Global Title Translation. Thereare no SEAS equivalents for these commands.

    GTA Commands

    GTA commands are used to provision GTTs using the new selectors for GTT.

    37910-6671-001 Revision B, February 2014

    Global Title Translation (GTT) OverviewDatabase Administration Manual - Global TitleTranslation

  • The EAGLE 5 ISS supports the following:

    Maximum of 950 GTT sets. Maximum of 200,000 global title addresses per GTT set. 269,999, 400,000, or 1,000,000 global title addresses. The system default is 269,999 global title

    addresses. This quantity can be increased to 400,000 by enabling the feature access key for partnumber 893-0061-01, or to 1,000,000 by enabling the feature access key for part number 893-0061-10.For more information on enabling these feature access keys, refer to the Enabling the XGTT TableExpansion Feature procedure.

    Maximum of 100,000 GTT selectors. 1024, 2000, or 3000 remote point codes (mated applications), with up to 10 subsystems at each point

    code. The system default is 1024 mated applications. This quantity can be increased to 2000 byenabling the feature access key for part number 893-0077-01, or to 3000 by enabling the featureaccess key for part number 893-0077-10. For more information on enabling these feature accesskeys, refer to the Enabling the XMAP Table Expansion Feature procedure.

    Variable-length Global Title Translation Feature

    A translation type or GTT set can contain global title addresses of varying length. If the Variable-lengthGlobal Title Translation (VGTT) feature is turned on with the chg-feat command, a translation typeor GTT set contain up to 10 different length global title addresses. If the Support for 16 GTT Lengthsin VGTT feature is enabled and turned on with the enable-ctrl-feat and chg-ctrl-featcommands, a translation type or GTT set can contain up to 16 different length global title addresses.The Support for 16 GTT Lengths in VGTT feature cannot be enabled and turned on unless the VGTTfeature is turned on.

    The length of the global title address is only limited by the range of values for the gta and egtaparameters of either the ent-gtt and chg-gtt commands, if only the GTT feature is turned on, orthe ent-gta and chg-gta commands, if the EGTT feature is turned on, and by the global titleaddresses already assigned to the translation type or GTT set. The length of a global title address isfrom 1 to 21 digits, or 1 to 21 hexadecimal digits if the Hex Digit Support for GTT feature is enabled.The ndgt parameter of the ent-tt or ent-gttset command has no effect on the length of the globaltitle address and cannot be used. If the ndgt parameter is specified with the ent-tt or ent-gttsetcommand and the VGTT feature is on or the Support for 16 GTT Lengths in VGTT feature is enabledand turned on, the ent-tt or ent-gttset command is rejected with this message.

    E4011 Cmd Rej: NDGT parameter is invalid for VGTT

    As global title addresses of different lengths are assigned to a specific translation type, these lengthsare displayed in the NDGT field of the rtrv-tt command output, as shown in the following example.

    rlghncxa03w 09-05-25 09:57:31 GMT EAGLE5 41.0.0TYPEA TTN NDGT1 lidb 6, 12, 152 c800 103 d700 6

    ALIAS TYPEA50 365 3

    38910-6671-001 Revision B, February 2014

    Global Title Translation (GTT) OverviewDatabase Administration Manual - Global TitleTranslation

  • TYPEI TTN NDGT105 itudb 8

    ALIAS TYPEI7 105

    TYPEN TTN NDGT120 dbitu 7

    ALIAS TYPEN8 120

    If the global title addresses are assigned to a GTT set, these lengths are displayed in the NDGT field ofthe rtrv-gttset command output, as shown in the following example.

    rlghncxa03w 09-07-07 00:30:31 GMT EAGLE5 41.1.0GTT