1. Manuals
  2. Brands
  3. Tekelec Manuals
  4. Server
  5. EAGLE 5
  6. Feature manual

Tekelec EAGLE 5 Feature Manual

Integrated signaling system ecap
Hide thumbs Also See for EAGLE 5:
Table of Contents

Advertisement

Quick Links

Download this manual
®
Tekelec EAGLE
5
Integrated Signaling System
Release 1.0
Feature Manual - ECAP
910-3191-001 Revision D
June 2007

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the EAGLE 5 and is the answer not in the manual?

Questions and answers

Related Manuals for Tekelec EAGLE 5

Summary of Contents for Tekelec EAGLE 5

  • Page 1 ® Tekelec EAGLE Integrated Signaling System Release 1.0 Feature Manual - ECAP 910-3191-001 Revision D June 2007...
  • Page 2 Information in this documentation is subject to change without notice. Unauthorized use or copying of this documentation can result in civil or criminal penalties. Any export of Tekelec products is subject to the export controls of the United States and the other countries where Tekelec has operations.

  • Page 3: Table Of Contents

    Table of Contents Chapter 1. Introduction Overview ....................1-2 Scope and Audience ................. 1-3 Manual Organization ................1-3 Related Documentation................1-3 Documentation Packaging, Delivery, and Updates......1-9 Documentation Admonishments ............1-10 Customer Care Center................1-10 Problem Classification ..............1-11 Response .................... 1-12 Hardware Repair and Return..............
  • Page 4 Table of Contents EAGLE 5 ISS Alarms ................. 4-6 Integrated Accounting Feed Conditions ........4-8 Disaster Recovery ................... 4-12 Log Files ....................4-13 Savelogs ..................... 4-13 Health Check ................... 4-14 Process Check ................... 4-14 Crontab Check .................. 4-14 Disk Space Check ................4-15 Network Check.................
  • Page 5 Figure 2-1. ECAP T1100 Frame ..............2-4 Figure 2-2. Integrated Accounting Feed Architectural Overview ...2-5 Figure 2-3. Interconnectivity Overview ............2-7 Figure 2-4. Aggregator/ECAP/EAGLE 5 ISS Connectivity Diagram ......................2-8 Figure 3-1. Network Configuration ............3-3 Figure 3-2. Integrated Accounting Feed Configuration Menu ....3-15...
  • Page 6 Table 4-1. Critical Platform Alarms ................. 4-5 Table 4-2. Major Platform Alarms ..................4-5 Table 4-3. Minor Platform Alarms ................... 4-6 Table 4-4. EAGLE 5 ISS UAMs ..................4-7 Table 4-5. Integrated Accounting Feed Conditions ............4-9 Table A-1. Data File Tags ....................A-3...
  • Page 7 Introduction Overview ......................1-2 Scope and Audience..................1-3 Manual Organization ..................1-3 Related Documentation ...................1-3 Documentation Packaging, Delivery, and Updates........1-9 Documentation Admonishments ..............1-10 Customer Care Center ...................1-10 Acronyms......................1-12 910-3191-001 Revision D, June 2007...

  • Page 8: Overview

    The ECAP platform is an adjunct system to the Tekelec portfolio of products that work in conjunction with the EAGLE 5 ISS and other system(s) so that the raw MSU data can be converted into accounting records in accordance with Section 7.

  • Page 9: Scope And Audience

    This manual is intended for anyone responsible for installing, maintaining, and using the Integrated Accounting Feed application in the EAGLE 5 ISS. Users of this manual and the others in the EAGLE 5 ISS family of documents must have a working knowledge of telecommunications and network installations.
  • Page 10 EAGLE 5 ISS to implement the SS7-IP Gateway. • The Database Administration Manual – SEAS contains the EAGLE 5 ISS configuration procedures that can be performed from the Signaling Engineering and Administration Center (SEAC) or a Signaling Network Control Center (SNCC).
  • Page 11 Introduction procedure, a flowchart showing the steps required, a list of any EAGLE 5 ISS commands that may be required for the procedure but that are not supported by SEAS, and a reference to optional procedure-related information, which can be found in one of these manuals: —...
  • Page 12 EAGLE 5 ISS. • The FTP-Based Table Retrieve Application (FTRA) User Guide describes how to set up and use a PC to serve as the offline application for the EAGLE 5 ISS FTP Retrieve and Replace feature. • The Hardware Manual - EAGLE 5 ISS provides an overview of each system and its subsystems, details of standard and optional hardware components in each system, and basic site engineering.
  • Page 13 EAGLE 5 ISS documentation set. • The LNP Feature Activation Guide contains procedural information required to configure the EAGLE 5 ISS for the LNP feature and to implement these parts of the LNP feature on the EAGLE 5 ISS: — LNP services —...
  • Page 14 Maintenance Manual and contains the corrective maintenance procedures for critical and major alarms generated on the EAGLE 5 ISS. • The MPS Platform Software and Maintenance Manual - EAGLE 5 ISS with Tekelec 1000 Application Server describes the platform software for the...

  • Page 15: Documentation Packaging, Delivery, And Updates

    • The SEAS Commands Error Messages Manual lists the error messages generated by the EAGLE 5 ISS that are specific to the Signaling Engineering and Administration System (SEAS). It includes the SEAS commands that trigger the error messages, the equivalent system error messages and commands, and the explanatory text.

  • Page 16: Documentation Admonishments

    Customer Care Center The Customer Care Center offers a point of contact through which customers can receive support for problems that may be encountered during the use of Tekelec’s products. The Customer Care Center is staffed with highly trained engineers to provide solutions to your technical questions and issues seven days a week, twenty-four hours a day.

  • Page 17: Problem Classification

    Introduction Problem Classification Once a Customer Service Request (CSR) is issued, the Customer Care Center, along with the customer, determines the classification of the trouble. Problems are reported using problem criteria, as defined in the following sections and “TL-9000 Quality System Metrics (Book Two, Release 3.0)” . Problem –...

  • Page 18: Response

    Any system components being returned for repair or replacement must be processed through the Tekelec Return Material Authorization (RMA) procedures. A hardware repair is defined as an item returned to Tekelec due to a failure, with the returned item being repaired and returned to the customer. It is essential that serial numbers are recorded correctly.
  • Page 19 Introduction IS-41 International Standard 41, same as ANSI-41 ISUP ISDN User Part International Telecommunications Union Mobile Application Part Management Information Base Message Signaling Unit Message Transfer Part Network Management System Network Time Protocol Operation, Administration, and Maintenance Origination Point Code SCCP Signalling Connection Control Part SCMG...
  • Page 20 Introduction 1-14 910-3191-001 Revision D, June 2007...
  • Page 21 Feature Description Introduction...................... 2–2 Hardware Requirements .................2-3 Architectural Overview ...................2-5 Interconnectivity ..................2-6 Integrated Accounting Feed Considerations..........2-9 910-3191-001 Revision D, June 2007...

  • Page 22: Chapter 2. Feature Description

    The Integrated Accounting Feed application performs collection of EAGLE® 5 ISS traffic statistics data. ECAP is one or more T1100-based servers that run in an integrated fashion with EAGLE 5 ISS that receives MSUs from the EAGLE 5 ISS and feeds them to an accounting system.

  • Page 23: Hardware Requirements

    • The maximum number of ECAP Servers is six. • The number of ECAP Servers per frame is two to six. • The EAGLE 5 ISS system used with the ECAP must be equipped with SSEDCM card types running the VXWSLAN application. The VXWSLAN application cards must be provisioned with 100 Mbps links in order to achieve 5000 MSUs/sec.

  • Page 24: Figure 2-1. Ecap T1100 Frame

    Feature Description Figure 2-1. ECAP T1100 Frame BUS A BUS B BUS A 9,10 11,12 BUS A 9,10 11,12 BRK FAIL BUS A BRK FAIL BUS B CRITICAL MAJOR MINOR 910-3191-001 Revision D, June 2007...

  • Page 25: Architectural Overview

    Figure 2-2 provides a high-level architectural view of the Integrated Accounting Feed application as it runs on the ECAP system. The EAGLE 5 ISS (100) connects to the Collector (101) via a direct connected Ethernet cable. The data feed from the EAGLE 5 ISS to the Collector is the STPLAN (104).

  • Page 26: Interconnectivity

    Feature Description Table 2-2 defines the terms used in the above figure. Table 2-2. Integrated Accounting Feed Architecture Terms Term Definition Collector The Collector function runs on the ECAP servers. This function receives the STPLAN MSU feed and parses the MSUs in the feed into categories based on provisioning rules.

  • Page 27: Figure 2-3. Interconnectivity Overview

    See “Architectural Overview” on page 2-5 for a description of the other details in the above figure. A diagram showing a detailed view of the EAGLE 5 ISS/ECAP/Aggregator connectivity is shown in Figure 2-4. This diagram includes the types of connection that flow between each component.

  • Page 28: Figure 2-4. Aggregator/Ecap/Eagle 5 Iss Connectivity Diagram

    Feature Description Figure 2-4. Aggregator/ECAP/EAGLE 5 ISS Connectivity Diagram The connectivity elements are as follows: • EAGLE 5 ISS Connectivity — SLAN to ECAP for Q.752 accounting information — IPSM to NMS for alarms monitoring • ECAP Connectivity — Ethernet to EAGLE SLAN for Q.752 accounting information retrieval.

  • Page 29: Integrated Accounting Feed Considerations

    • The Integrated Accounting Feed application cannot aggregate data to the linkset level. Aggregation of peg counts must be done by the Aggregator. • Because of the nature of the EAGLE 5 ISS and its SLAN subsystem, no other application requiring SLAN copied MSUs may operate simultaneously with the EAGLE 5 ISS that is being used to run the Integrated Accounting Feed application.
  • Page 30 Feature Description 2-10 910-3191-001 Revision D, June 2007...
  • Page 31 ECAP Configuration Introduction...................... 3–2 Configuring the Aggregator ................3–2 Configuring ECAP Network Interfaces ............3-3 Configuring File Transfer ................3-7 Configuring NTP ....................3-9 Configuring NMS ................... 3-11 Configuring the Integrated Accounting Feed Application ......3-15 Configuring SLAN Cards................3-18 Configuring Gateway Screening ..............3-19 910-3191-001 Revision D, June 2007...

  • Page 32: Introduction

    • Configure the NMS on the NMS system (customer specific) and configure the ECAP server to send SNMP traps to the NMS • Configure the Integrated Feed Application • Configure the EAGLE 5 ISS SLAN cards • Configure Gateway Screening on EAGLE 5 ISS Configuring the Aggregator The Aggregator must be configured to receive data files from the ECAP.

  • Page 33: Configuring Ecap Network Interfaces

    The Data Collection Interface is the incoming MSU data network interface. This interface connects an ECAP server to the EAGLE 5 ISS SLAN card via a direct IP connection. Each ECAP server interfaces with one and only one SLAN card.
  • Page 34 ECAP Configuration Procedure 3-1. Configuring Network Interfaces Log in to the ECAP server as the user. platcfg Select Network Configuration from the Platform Configuration Utility Main Menu and press Enter. Select Network Interfaces from the Network Configuration Menu and press Enter.
  • Page 35 ECAP Configuration Select Edit an Interface from the Network Interfaces Menu and press Enter. Select the device that corresponds to the interface you want to configure and press Enter. See Table 3-1 for a list of interfaces and their associated devices. 910-3191-001 Revision D, June 2007...

  • Page 36: Table 3-1. Ecap Network Parameters

    ECAP Configuration Select Edit to configure the interface, using the settings in Table 3-1. Save and Exit the menu . You have now completed this procedure. Table 3-1. ECAP Network Parameters Data Collection File Transfer Maintenance Parameter Interface Interface Interface Device eth93 bond0.200...

  • Page 37: Configuring File Transfer

    ECAP Configuration Configuring File Transfer In addition to the network configuration tasks listed above, the File Transfer Interface must be configured to automatically push data files from the ECAP server to the Aggregator. In normal operating conditions, the ECAP server pushes data files to the Aggregator every 30 minutes.
  • Page 38 ECAP Configuration [aggregator] # chmod 644 .ssh/authorized_keys [aggregator] # exit Test the steps performed above using the command: [ecap1] # ssh ftpuser@aggregator If the steps were performed correctly, you will be logged on to the Aggregator and will not be prompted for a password. The command line prompt will correspond to the display on the Aggregator.

  • Page 39: Configuring Ntp

    ECAP Configuration Configuring NTP Synchronize each ECAP server’s local time with the Aggregator via NTP. This allows the entire ECAP/Aggregator network to have synchronized time. Use the following procedure to configure NTP using platcfg Procedure 3-4. Configuring NTP Log in to the ECAP server as the user.
  • Page 40 ECAP Configuration Select Edit. Edit the IP addresses as desired and click Exit. NOTE: NTP will be functional on the server when only one server is defined; however, providing more than one server will make the protocol more reliable. Save and Exit the menu. You have now completed this procedure.

  • Page 41: Configuring Nms

    ECAP Configuration Configuring NMS ECAP servers generate SNMP traps to capture platform alarms. The MIBs required for platform traps are pre-existing, the snmpAgent used for platform alarms is activated during ECAP installation, and most of the hardware checks that would result in traps are defaulted to enabled. However, the Integrated Accounting Feed application also requires enabling the following: •...
  • Page 42 ECAP Configuration Select Server Configuration from the Platform Configuration Utility Main Menu and press Enter. Select Alarms Configuration from the Server Configuration Menu and press Enter. Select SNMP Configuration from the Alarms Configuration Menu and press Enter. 3-12 910-3191-001 Revision D, June 2007...
  • Page 43 ECAP Configuration Select NMS Configuration from the Server Configuration Menu and press Enter. Select Edit. Select a task from the NMS Server Action menu. You can add, edit, or delete an NMS Server. 910-3191-001 Revision D, June 2007 3-13...
  • Page 44 ECAP Configuration NOTE: The SNMP Community String and Port Number values must match the values configured on the NMS. Save and Exit the menu. You have now completed this procedure. 3-14 910-3191-001 Revision D, June 2007...

  • Page 45: Configuring The Integrated Accounting Feed Application

    Entering this command opens the Integration Accounting Feed Configuration Menu. The Configuration Menu provides options that describe the EAGLE 5 ISS and Aggregator configuration values. A graphical representation of the menu layout is provided in Figure 3-2. Figure 3-2. Integrated Accounting Feed Configuration Menu ECAP Configuration Menu 1.
  • Page 46 Displays a set of options that enable [1..4, E] Configuration the operational parameters associated with the EAGLE 5 ISS MSU feed to be set or changed. STP name Sets the STP name that is used in the The value has a filename of the data file transferred 12-character limit.
  • Page 47 ECAP Configuration Table 3-2. Configuration Menu Options (Continued) Menu Option Description Range of Values Aggregator Sets the path to the directory in No restrictions. Directory for Files which the data files will be stored on the Aggregator File Transfer Sets the number of minutes after the [1...5] Time half hour to send data files to the...

  • Page 48: Configuring Slan Cards

    ECAP Configuration Configuring SLAN Cards The EAGLE 5 ISS SLAN card must be configured to interface with an ECAP server via the Data Collection Interface. Use the commands to establish the links for the SLAN ent-dlk ent-ip-node cards. See Table 3-3 for a list of these commands and their parameters as they apply to the Integrated Application Feed application.

  • Page 49: Configuring Gateway Screening

    Configuring Gateway Screening Gateway Screening measures an MSU attempting to enter the EAGLE 5 ISS against predefined criteria in the EAGLE 5 ISS database to determine whether the MSU should be allowed to enter. Refer to the Database Administration Manual – Gateway Screening for information on configuring Gateway Screening.
  • Page 50 ECAP Configuration 3-20 910-3191-001 Revision D, June 2007...
  • Page 51 Maintenance Alarms ....................... 4–2 Platform Alarms ..................4-2 EAGLE 5 ISS Alarms .................4-6 Integrated Accounting Feed Conditions ..........4-8 Disaster Recovery ..................4–12 Log Files ......................4–13 Savelogs .....................4-13 Health Check ....................4–14 Process Check ...................4-14 Crontab Check ..................4-14 Disk Space Check ..................4-15 Network Check..................4-15...

  • Page 52: Alarms

    NMS. • Connectivity problems between the EAGLE® 5 ISS and ECAP server are raised as UAMs on the EAGLE 5 ISS. • Conditions associated with the Integrated Accounting Feed application may impact operation and may have associated alarms.
  • Page 53 Maintenance Procedure 4-1. Viewing Information on Alarms Log in to the ECAP server as the user. platcfg Select Diagnostics from the Platform Configuration Utility Main Menu and press Enter. Select Online Diagnostics from the Network Diagnostics Menu and press Enter. 910-3191-001 Revision D, June 2007...
  • Page 54 Maintenance Select Verbose from the Online Diagnostics menu and press Enter. An output report, containing debug information for each individual test performed on the server, is displayed. Select Exit to return to the Online Diagnostics menu. You have now completed this procedure. 910-3191-001 Revision D, June 2007...

  • Page 55: Table 4-1. Critical Platform Alarms

    Maintenance Table 4-1. Critical Platform Alarms Alarm Text Range of Values Alarm Data String Value Breaker Panel Feed on or off 1000000000000001 Unavailable Breaker Panel Breaker Failure on or off 1000000000000002 Breaker Panel Monitoring on or off 1000000000000004 Failure Power Feed Unavailable on or off 1000000000000008 Power supply #1 Failure...

  • Page 56: Eagle 5 Iss Alarms

    EAGLE 5 ISS Alarms Connectivity problems that occur on the Data Collection Interface between the EAGLE 5 ISS and ECAP server are raised as UAMs on the EAGLE 5 ISS. See Table 4-4 for a list of these UAMs. Refer to the Maintenance Manual for more information on the EAGLE 5 ISS related alarms.

  • Page 57: Table 4-4. Eagle 5 Iss Uams

    SCCP cards. MSUs have been discarded. Remedy: 1. Use the command rept-stat-slan to verify that the EAGLE 5 ISS SLAN subsystem is IS-NR and is sending MSU packets to ECAP. Refer to the Commands Manual for information on the command.

  • Page 58: Integrated Accounting Feed Conditions

    The conditions listed in Table 4-5 may impact Integrated Accounting Feed operation. If these conditions occur, follow the procedures listed in the Resolution column. If the provided corrective procedures do not work, contact the Tekelec Customer Care Center (see “Customer Care Center” on page 1-10).

  • Page 59: Table 4-5. Integrated Accounting Feed Conditions

    Maintenance Table 4-5. Integrated Accounting Feed Conditions Condition Resolution No data files on the Aggregator The ECAP server is operational and periodically generating data files, but the files are not being transferred to the Aggregator. Remedy: 1. Determine whether the Device Interface Error major platform alarm (see Table 4-2 on page 4-5) has...
  • Page 60 Data file contains no records The data file contains standard data header but no record entries. This occurs when no MSU records are received from EAGLE 5 ISS. There are no SLAN cards in the IS-NR state. Remedy: 1. Use the...
  • Page 61 ECAP do not correspond to EAGLE 5 ISS measurements for the same time period. Remedy: 1. Check EAGLE 5 ISS alarm log for UAM 0152 (see “EAGLE 5 ISS UAMs” on page 4-7). If present, MSUs have been discarded...

  • Page 62: Disaster Recovery

    Therefore, this scenario should also be corrected as soon as possible. In the event of a catastrophic failure where ECAP hardware fails, contact the Tekelec Customer Care Center (see “Customer Care Center” on page 1-10). 4-12 910-3191-001 Revision D, June 2007...

  • Page 63: Log Files

    Maintenance Log Files The Integrated Accounting Feed application generates log files for the following processes (see “Process Check” on page 4-14 for a description of the processes): • MeasServer • TimeServer • FileMover • FileScrubber • Logd • sentryd • surv These logs are written to the directory.

  • Page 64: Health Check

    • MeasServer: Receives and decodes EAGLE 5 ISS SLAN packets, and stores them to a data file • TimeServer: Responds to time queries from the EAGLE 5 ISS SLAN card • Logd: Manages all ECAP logging The following processes run periodically: •...

  • Page 65: Disk Space Check

    The Network Diagnostics commands are used to verify connectivity between the EAGLE 5 ISS SLAN card and the ECAP server and between the ECAP server and the Aggregator. Along with the conditions listed in Table 4-5 on page 4-9, this check should be done in response to the Device Interface Error or Device Interface Warning platform alarms (see Tables 4-2 and 4-3).
  • Page 66 Maintenance Procedure 4-2. Verifying Connectivity between EAGLE 5 ISS SLAN Card and the ECAP Server Log into ECAP as the user. platcfg Select Diagnostics from the Platform Configuration Utility Main Menu and press Enter. Select Network Diagnostics from the Diagnostics Menu and press Enter.
  • Page 67 Verifying ECAP to Aggregator Connectivity Verify connectivity between the ECAP and the Aggregator using the Network Diagnostics tasks described in “Verifying EAGLE 5 ISS to ECAP Connectivity” on page 4-15. In addition to these tasks, you must also perform a secure shell connectivity check.
  • Page 68 Maintenance 4-18 910-3191-001 Revision D, June 2007...
  • Page 69 MSU to XML Field Mapping Introduction......................A-2 Data Files......................A-3 Data File XML DTD ..................A-6 ISUP MSU ......................A-7 ECAP XML Output...................A-8 SCCP MSU ......................A-9 ECAP XML Output.................A-10 MAP MSU.......................A-11 ECAP XML Output.................A-12 910-3191-001 Revision D, June 2007...

  • Page 70: Appendix A. Msu To Xml Field Mapping

    MSU to XML Field Mapping Introduction This appendix provides information on how the MSU parameters that come into the ECAP server relate to the peg count fields in the data file. An overview of the generated data files is provided, along with three samples: an ISUP MSU, an SCCP MSU, and an SCCP MSU with a TCAP layer (MAP MSU).

  • Page 71: Data Files

    MSU to XML Field Mapping Data Files The Integrated Accounting Feed application generates data files periodically. These files are stored in the directory until /usr/TKLC/ecap/xml/pending_ftp they are copied to the Aggregator. Once a file has been copied to the Aggregator, it is moved to the directory where it remains /usr/TKLC/ecap/xml/archive_ftp...
  • Page 72 “undefined” is an invalid protocol and represents an error in decoding. <linkid> [0..65535] EAGLE 5 ISS STP link ID on </linkid> which the MSUs were received (incoming link). This is a decimal value. <si> “isup” or “sccp”...
  • Page 73 MSU to XML Field Mapping Table A-1. Data File Tags (Continued) Range of Values Description <opc> [000..255][000..255] Decimal representation of the </opc> [000..255] (ANSI), or Originating Point Code from [000..007][000..255] the MTP layer [000.007] (ITU-I), or [0..16383] (ITU-N) <dpc> [000..255][000..255] Decimal representation of the </dpc>...

  • Page 74: Data File Xml Dtd

    MSU to XML Field Mapping Table A-1. Data File Tags (Continued) Range of Values Description <msucount> [1..4294967295] Decimal representation of the </msucount> number of MSUs processed with the specified MTP and/or SCCP parameters <octcount> [1..4294967295] Decimal representation of the </octcount> number of octets processed with the specified MTP and/or SCCP parameters.

  • Page 75: Isup Msu

    MSU to XML Field Mapping ISUP MSU The following is an example of ISUP MSU with the ECAP data file. *** Start of MTP Level 3 *** 0000 00000101 05 ----0101 ----.-- Service Indicator ISDN User Part --00---- ----.-- Spare 00------ ----.-- Network Indicator...

  • Page 76: Ecap Xml Output

    MSU to XML Field Mapping 0023 00000000 00 0024 00000000 00 0025 00000000 00 0026 00000000 00 0027 00000000 00 ECAP XML Output <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE ecapreport SYSTEM "ecapreport.dtd"> <ecapreport> <stp>e1021201</stp> <collector>nc1lxvader</collector> <startdate>26092005</startdate> <starttime>102800</starttime> <enddate>26092005</enddate> <endtime>102900</endtime> <record> <signallingstandard>ITU-I</signallingstandard> <linkid>1</linkid> <si>isup</si>...

  • Page 77: Sccp Msu

    MSU to XML Field Mapping SCCP MSU The following is an example of SCCP MSU with the ECAP data file. If an SCCP MSU contains a CgPA or CdPA point code, the point code is copied to the peg count report, but only if the point code differs from the OPC or DPC. *** Start of MTP Level 3 *** 0000 00000011 03 ----0011...

  • Page 78: Ecap Xml Output

    MSU to XML Field Mapping 0039 01111000 78 0040 01010110 56 0041 00110100 34 0042 00010010 12 0043 00001001 09 Data Portion *** Start of TCAP and SCCP Management *** TCAP Layer 0044 00000101 05 .--..-- TCAP Length 0045 01100010 62 .T-..E. Begin Message 0046 00000011 03 .--..-- Message Length Transaction Portion 0047 01001000 48 .--..-.

  • Page 79: Map Msu

    MSU to XML Field Mapping MAP MSU The following is an example of SCCP MSU with a TCAP layer with the ECAP data file. *** Start of MTP Level 3 *** 0000 00000011 03 ----0011 ----.-- Service Indicator SCCP --00---- ----.-- Spare 00------ ----.-- Network Indicator...

  • Page 80: Ecap Xml Output

    MSU to XML Field Mapping 0041 00110100 34 0042 00010010 12 0043 00001001 09 Data Portion *** Start of TCAP and SCCP Management *** TCAP Layer 0044 00100010 22 .--..-- TCAP Length 0045 01100001 61 .T-..E. Unidirectional Message 0046 00100000 20 .--..-- Message Length Optional Dialogue Portion Dialogue Portion 0047 01101011 6b .--..-.
  • Page 81 MSU to XML Field Mapping <mtp> <opc>002-002-001</opc> <dpc>002-002-002</dpc> </mtp> <sccp> <cgpadigits>0987654321098765432190</cgpadigits> <cdpadigits>1234567890123456789010</cdpadigits> <cgpapc>004-002-001</cgpapc> <cdpapc>004-002-002</cdpapc> </sccp> <map> <opcode>5</opcode> </map> <msucount>1</msucount> <octcount>82</octcount> </record> </ecapreport> 910-3191-001 Revision D, June 2007 A-13...
  • Page 82 MSU to XML Field Mapping A-14 910-3191-001 Revision D, June 2007...

  • Page 83: Index

    Customer Service Request 1-10 admonishments, documentation Aggregator Data File XML DTD Aggregator Configuration Data Files Alarms Disaster Recovery 4-12 EAGLE 5 ISS 4-6 Disk Space Check 4-15 Integrated Accounting Feed documentation Platform admonishments Application Considerations Documentation Admonishments Architectural Overview Documentation Packaging, Delivery, and...
  • Page 84 1-12 Hardware Repair and Return Hardware Requirements Platform Alarms 1-12 1-11 hardware return Problem-Major Health 4-14 Problem-Minor 1-11 Health Check Process Check 4-14 Crontab Check 4-14 Disk Space Check 4-15 Report File XML DTD Network Check 4-15 Response 1-11 Process Check 4-14 RSA Public Key Generation...
  • Page 85 Alarms 3-15 admonishments Configuration Menu Documentation Admonishments Integrated Accounting Feed application Documentation Packaging, Delivery, and Introduction Updates ISUP MSU EAGLE 5 ISS Alarms Log Files 4-13 EAGLE 5 ISS Configuration 3-19 Gateway Screening Maintenance 910-3191-001 Revision D, June 2007 Index-3...
  • Page 86 1-10 4-13 Savelogs Documentation Packaging, Delivery, and Updates SCCP MSU Scope and Audience SLAN Card Configuration 3-18 EAGLE 5 SAS Alarms EAGLE 5 SAS Configuration SSCP MSU with TCAP A-11 Gateway Screening 3-19 SLAN Cards 3-18 Eagle Collection Application Processor...
  • Page 87 ECAP Network Interface Configuration Overview Feature File Transfer Interface Configuration Platform Alarms 1-11 Problem-Major Problem-Minor 1-12 4-14 Process Check Gateway Screening Configuration 3-19 Report File XML DTD Hardware Repair and Return 1-12 1-12 Response Hardware Requirements RSA Public Key hardware return 1-12 Generation 4-14...
  • Page 88 Index-6 910-3191-001 Revision D, June 2007...

Table of Contents