UM_ADM_V82_35_IUS

March 17, 2018 | Author: Milton Tofetti Moura | Category: Osi Model, Computer Network, Communications Protocols, Telecommunications Standards, Media Technology
Share
Report this link


Comments



Description

sLIOS Lawful Interception Operation System User Manual – Administrator A30828-X9410-B082-35-7619 Version 8.2 Issue 35 Confidential Issued by Program- and Systems Engineering Siemensstrasse 88-92, A-1211 Vienna Copyright © Siemens AG 2007 SIEMENS AKTIENGESELLSCHAFT All Rights Reserved. LIOS V8.2 User Manual – Administrator Issue 35 Copyright 2007 Siemens AG Österreich (Siemens Austria) Reproduction and redistribution only permitted with the written consent of SAGÖ PSE SMC. Issued by the Program and System Engineering division, SMC CI unit Siemensstrasse 92 A-1211 Vienna All hardware and software names used are trade names and/or trade marks belonging to the respective manufacturers. Technical modifications possible. Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written contract. 2/185 A30828-X9410-B082-35-7619 LIOS V8.2 User Manual – Administrator Issue 35 Table of Contents 0 GENERAL INFORMATION....................................................................................7 0.1 References .............................................................................................................................7 0.2 Abbreviations..........................................................................................................................7 0.3 List of Figures .......................................................................................................................10 0.4 List of Tables ........................................................................................................................12 1 INTRODUCTION .................................................................................................14 1.1 Documentation overview ......................................................................................................14 1.2 LIOS manuals.......................................................................................................................14 1.3 Target group and structure of this manual ...........................................................................14 2 SYSTEM DESCRIPTION ....................................................................................15 2.1 The Siemens Lawful Interception solution............................................................................15 2.2 LIOS......................................................................................................................................18 Active monitoring in fixed and mobile (wireless) networks .....................................................................18 2.2.1 LIOS general features...........................................................................................................22 2.2.2 LIOS components .................................................................................................................23 2.2.3 LIOS interfaces .....................................................................................................................24 2.2.4 Data safety............................................................................................................................25 2.2.5 LIOS user roles.....................................................................................................................25 3 WORKING WITH LIOS........................................................................................27 3.1 3.1.1 3.1.1.1 3.1.1.2 3.1.1.3 3.1.1.4 3.1.2 3.1.2.1 3.1.2.2 3.1.3 3.1.3.1 3.1.3.2 3.1.3.3 3.1.4 The LIOS GUI.......................................................................................................................27 The LIOS main page.............................................................................................................27 Header ..................................................................................................................................28 Navigation menu...................................................................................................................29 Application commands bar ...................................................................................................29 Work area (table) ..................................................................................................................29 Wizards, input forms and output forms.................................................................................30 Shifting items between lists ..................................................................................................30 Push buttons.........................................................................................................................31 Working with filter forms .......................................................................................................31 General filtering functions .....................................................................................................31 Filtering by date and time .....................................................................................................32 Filter push buttons ................................................................................................................33 IP address verification ..........................................................................................................33 3.2 3.2.1 3.2.2 User Administration ..............................................................................................................33 User filter...............................................................................................................................35 User data wizard...................................................................................................................36 3.3 3.3.1 3.3.2 User Administration: Groups ................................................................................................38 Group filter ............................................................................................................................40 Group data form....................................................................................................................40 3.4 3.4.1 3.4.2 3.4.3 3.4.4 3.4.5 3.4.5.1 3.4.5.2 Host Administration: NEs......................................................................................................42 Communication Settings.......................................................................................................44 NE activation.........................................................................................................................45 NE filter .................................................................................................................................46 Export....................................................................................................................................46 Setting up NEs......................................................................................................................47 Siemens EWSD and hiQ/E 9200..........................................................................................47 Siemens MSC.......................................................................................................................47 A30828-X9410-B082-35-7619 3/185 LIOS V8.2 User Manual – Administrator Issue 35 3.4.5.3 3.4.5.4 3.4.5.5 3.4.5.6 3.4.5.7 3.4.5.8 3.4.6 3.4.6.1 3.4.6.2 3.4.6.3 3.4.6.4 3.4.6.5 3.4.6.6 3.4.6.7 3.4.6.8 3.4.6.9 3.4.6.10 3.4.6.11 3.4.6.12 3.4.7 3.4.7.1 3.4.7.2 3.4.7.3 3.4.7.4 3.4.7.5 3.4.7.6 3.4.7.7 3.4.7.8 3.4.7.9 3.4.7.10 3.4.7.11 3.4.8 Siemens hiQ 4200 and 8000 ................................................................................................48 Alcatel S12............................................................................................................................48 Huawei C&C08 .....................................................................................................................48 Huawei GSM.........................................................................................................................48 Siemens IN@vantage...........................................................................................................48 Nortel (via LIM) .....................................................................................................................48 NE data wizard .....................................................................................................................48 General .................................................................................................................................49 LI Options .............................................................................................................................50 ETSI Network ID ...................................................................................................................50 LI NE passwords and specific parameters (for EWSD, hiQ/E9200) ....................................52 Parameters for X.25..............................................................................................................54 Parameters for IP (EWSD, hiQ/E9200, MSC SR11/SR12) ..................................................55 Parameters for IP (hiQ4200/8000) .......................................................................................55 Parameters for IP and MCs (Huawei C&C08) ......................................................................56 Parameters for IP (Huawei GSM).........................................................................................58 Parameters for IP (Siemens IN@vantage) ...........................................................................58 Authorization data (Nortel/LIM).............................................................................................60 Applications ..........................................................................................................................60 Application data wizard.........................................................................................................61 General application data.......................................................................................................61 OSI parameter ......................................................................................................................62 Passwords for EWSD and hiQ/E9200 – FT..........................................................................63 Passwords for EWSD and hiQ/E9200 – EFD.......................................................................63 Passwords for Alcatel S12 – MMLCM ..................................................................................64 NE user IDs (MMLCM) .........................................................................................................64 NE user ID wizard.................................................................................................................65 Authorization data.................................................................................................................66 MMLCM authorization data...................................................................................................67 FT authorization....................................................................................................................68 FT Authorization form ...........................................................................................................68 Reset passwords ..................................................................................................................69 3.5 3.5.1 3.5.1.1 3.5.1.2 3.5.1.3 3.5.2 3.5.2.1 3.5.2.2 3.5.2.3 3.5.2.4 3.5.2.5 3.5.2.6 3.5.3 3.5.4 Host Administration: OS Servers..........................................................................................70 Setting up OS servers...........................................................................................................71 KCC LIM ...............................................................................................................................71 Mediation Device (Siemens IP) ............................................................................................71 Utimaco IMS .........................................................................................................................72 OS Server data wizard..........................................................................................................73 Communications parameters for LIM servers.......................................................................73 Parameters for Mediation Device (Siemens IP) ...................................................................74 Transport system and OS server user IDs (IMS) .................................................................75 OS server user IDs ...............................................................................................................75 MMLCM authorization data...................................................................................................77 IMS authorization data..........................................................................................................78 Activate/Deactivate OS servers............................................................................................79 OS server filter......................................................................................................................80 3.6 3.6.1 3.6.2 Host Administration: LIOS Servers.......................................................................................80 LIOS server data wizard .......................................................................................................82 Application data form ............................................................................................................84 3.7 3.7.1 Host Administration: NE Networks .......................................................................................85 NE network data form ...........................................................................................................87 3.8 3.8.1 3.8.2 3.8.2.1 3.8.2.2 3.8.2.2.1 3.8.2.2.2 LEA Administration ...............................................................................................................89 LEA filter ...............................................................................................................................90 LEA data wizard....................................................................................................................91 LEA identification ..................................................................................................................91 Profile types ..........................................................................................................................92 Siemens Fixed (EWSD, hiQ/E 9200) observation parameters.............................................93 Siemens Fixed (hiQ4200/8000) observation parameters.....................................................95 4/185 A30828-X9410-B082-35-7619 LIOS V8.2 User Manual – Administrator Issue 35 3.8.2.2.3 3.8.2.2.4 3.8.2.2.5 3.8.2.2.6 3.8.2.2.7 3.8.2.2.8 3.8.2.2.9 3.8.2.2.10 3.8.2.3 3.8.3 3.8.4 Siemens MSC observation parameters................................................................................96 Huawei GSM observation parameters..................................................................................97 Alcatel S12 observation parameters.....................................................................................98 Huawei Fixed ........................................................................................................................99 Huawei GSM observation parameters................................................................................100 Mediation Device (Siemens IP) observation parameters ...................................................101 Nortel Fixed (LIM) observation parameters ........................................................................102 Utimaco IMS observation parameters ................................................................................102 LEA communication parameters ........................................................................................105 Communication settings .....................................................................................................108 Check LEA modification......................................................................................................109 3.9 3.9.1 LEA Administration: CUGs .................................................................................................110 CUG data form....................................................................................................................111 3.10 3.10.1 3.10.2 3.10.3 3.10.3.1 3.10.3.1.1 3.10.3.1.2 3.10.3.1.3 3.10.3.1.4 3.10.3.1.5 0.1.1.1 About alarms ......................................................................................................................112 LIOS alarm concept ............................................................................................................112 Alarm states........................................................................................................................114 Alarm categories.................................................................................................................114 LI NE alarms .......................................................................................................................114 LI NE alarms from EWSD, hiE/Q9200 and Alcatel S12 .....................................................114 LI NE alarms from LIM........................................................................................................115 LI NE alarms from HiQ4200/8000 ......................................................................................116 LI NE alarms from IN@vantage..........................................................................................116 LI NE alarms from Mediation Device (Siemens IP) ............................................................116 LIOS alarms........................................................................................................................117 3.11 3.11.1 3.11.2 3.11.3 Alarm browser ....................................................................................................................119 Alarm browser: Alarms .......................................................................................................120 Alarm filter...........................................................................................................................123 Alarm browser: Alarm types................................................................................................124 3.12 3.12.1 MML Handling ....................................................................................................................127 MML command states ........................................................................................................127 3.13 3.13.1 3.13.2 MML console ......................................................................................................................127 How to enter an MML command ........................................................................................130 MML commands for LIOS administrators ..........................................................................131 3.14 3.14.1 MML browser ......................................................................................................................133 MML filter ............................................................................................................................133 3.15 3.15.1 3.15.2 3.15.3 EFD Administration.............................................................................................................135 Filter ....................................................................................................................................137 EFD data wizard .................................................................................................................137 Validate ...............................................................................................................................140 4 SPECIAL WORKING PROCEDURES...............................................................141 4.1 Ticket buffer management (only for EWSD and hiQ/E9200) .............................................141 4.2 Setting up closed user groups (CUGs) for LEAs on EWSD and hiQ/E9200 switches.......142 4.3 Configuring LI NE alarm filtering (lios.properties file).........................................................143 4.4 Configuring cyclic DB synchronization ...............................................................................144 4.5 Automatic DN synchronization following a ‘Massive DN modification’ alarm.....................144 4.6 Upgrading the LIOS license................................................................................................144 4.7 Setting up a new EWSD or hiQ/E9200 NE in the LIOS system ........................................145 4.8 Handling an EWSD / hiQ/E9200 upgrade ..........................................................................145 4.9 Setting ETSI properties for NE ID (X.25 and E.164) ..........................................................146 4.10 Configuring maximum number of NE connections for EFD Administration .......................146 A30828-X9410-B082-35-7619 5/185 LIOS V8.2 User Manual – Administrator Issue 35 4.11 Setting active/passive FTP to LEAs and MCs (LIOS.properties file) .................................147 4.12 Switching parallel ticket sending on and off (LIOS.properties file) .....................................147 4.13 Switching support of LI management (HI1) notifications on and off (LIOS.properties file) 147 4.14 4.14.1 4.14.2 4.14.2.1 4.14.2.2 4.14.3 NTP Configuration for LIOS................................................................................................148 Multicast/Broadcast synchronization (automatic) ...............................................................148 Configuration check ............................................................................................................149 NTP server..........................................................................................................................149 NTP client ...........................................................................................................................150 Listing of NTP configuration files for LIOS..........................................................................150 4.15 Turning off the LIOS-proprietary time synchronization.......................................................152 4.16 Changing export format (field delimiter) in the LIOS.properties file ...................................152 4.17 Ticket time stamp conversion according to the time zone of the NE .................................152 5 SYSTEM CONFIGURATION .............................................................................154 5.1 5.1.1 5.1.2 Symmanager ......................................................................................................................154 Overview .............................................................................................................................154 Specifying size and number of internal buffers of the X.25 card ........................................154 5.2 Symmonitor.........................................................................................................................155 5.3 5.3.1 5.3.2 5.3.3 5.3.3.1 5.3.3.2 5.3.3.3 5.3.3.4 5.3.4 5.3.5 FTAM configuration ............................................................................................................155 Administering FTAM file transfer ........................................................................................155 Collecting X.25 configuration data......................................................................................156 Configuring Solstice X.25 software.....................................................................................157 Configuration of the X.25 link .............................................................................................157 Configuration of the LLC2 link ............................................................................................161 Administration of the X.25 routing table..............................................................................165 Activation of the X.25 configuration ....................................................................................167 Configuring the Solstice OSI software................................................................................168 Configuring the Solstice FTAM software ............................................................................175 5.4 5.4.1 5.4.2 5.4.3 5.4.4 5.4.4.1 5.4.5 Installing TopSec System (optional)...................................................................................177 Overview .............................................................................................................................177 Installation of administration software ................................................................................178 Initialization of TopSec Boxes ............................................................................................180 Administration of TopSec Boxes ........................................................................................181 Firmware update.................................................................................................................181 Switch to Plain Data Transfer .............................................................................................182 6 ANNEX 1: EXTERNAL ALARMING – EMAIL AND SMS FORMATS ................184 6.1 Format of the alarm message for email..............................................................................184 6.2 Format of the alarm message for SMS ..............................................................................184 7 ANNEX 2: LIOS – SUPPORTED NETWORK ELEMENTS ...............................185 6/185 A30828-X9410-B082-35-7619 PSE SMC CI Vienna 2005 [3] ETSI ES 201 671 V2.1. Symicron 1999 www.1 (2001-09) ETSI Standard Telecommunications security.02.2 User Manual – Administrator Issue 35 0 General Information 0.02 Dezember 2002 Rohde & Schwarz [7] OTOS / PIMS V1.1 References [1] EWSD/Lawful Interception Lending an ear to fixed network communication A30828-X1130-V310-1-7618 Siemens AG Munich 1999 [2] LIOS System Description P30308-A9792-A082-*-7619 Siemens AG Österreich.symicron. PSE SMC CI Vienna 2003 0.com [6] TopSec Anleitung TopSec Administrator Version 3. Lawful Interception (LI). Handover interface for the lawful interception of telecommunications traffic [4] EWSD/Description of Output Data Lawful Interception Description of Contents of LI Records and of Call Content Connection EWSD Version V17 P30308-A8225-V017-04-7617 Siemens AG Munich 2004 [5] Symdriver-U User Guide Edition 6.LIOS V8.2 Abbreviations AEQ Application Entity Qualifier AFI Address Facility Identification APQ Application Program Qualifier BIANCA BInTec Advanced Network Communication Architecture BRI ISDN Basic Rate Interface CC Call Content CDC Call Data Channel CGI Common Gateway Interface A30828-X9410-B082-35-7619 7/185 .1 Protocol-Independent Messaging System User Manual A30828-X9420-A011-1-7619 Siemens AG Österreich. LIOS V8. 77=frequency: 77. C=long wave signal.5 kHz) DN Directory Number DNS Domain Name System DSP Domain-Specific Part DTE Data Terminal Equipment DTMF Dual Tone Multi Frequency EFD Event-Forwarding Discriminator EMN/OS EWSD Management Network / Operations System ETSI European Telecommunications Standards Institute EWSD Electronic sWitching System – Digital (Elektronisches WählSystem – Digital) FDN Foreign Directory Numbers FT File Transfer FTAM File Transfer Access and Management FTP File Transfer Protocol GPRS General Packet Radio Service GSM Global System for Mobile Communication GTP GPRS Tunnelling Protocol GUI Graphical User Interface HDLC High-level Data Link Control (OSI-Layer 2 Protocol) HICEP Hot InterCeption Event Processor HLR Home Location Register HTML Hypertext Mark-up Language HTMLS HTML Secure HTTPS Hyper Text Transfer Protocol (Secure) IAP Internet Access Provider ICC Interception Communication Center IDI Initial Domain Identifier IIS Internet Information Server 8/185 A30828-X9410-B082-35-7619 .2 User Manual – Administrator Issue 35 CHAP Challenge Handshake Authentication Protocol CLIP Calling Line Identification Presentation CMISE Common Management Information Service Element [X. F=Frankfurt.710] COLP COnnected Line identification Presentation CP Coordination Processor (EWSD) CSV Comma-Separated Values CUG Closed User Group DB DataBase DBMS Database Management System DCE Data Communication Equipment DCF77 long wave time signal (D=Deutschland. LIOS V8.2 User Manual – Administrator Issue 35 IMEI International Mobile Equipment Identity IMS Interception Management System (by Utimaco) IMSI International Mobile Subscriber Identity INB INBand IP Internet Protocol IRI Intercept-Related Information (ETSI) ISDN Integrated Services Digital Network ISO International Systems Organization LAC Local Area Code LAN Local Area Network LC LIOS Client LEA Law Enforcement Agency LEMF Law Enforcement Montitoring Facility LI Lawful Interception LID Lawful Interception Data LIIN LI Identification Number LIM Lawful Interception Manager LIOS Lawful Interception Operation System LS LIOS Server MAC Media Access Control MC Monitoring Center MD Mediation Device MML Man Machine Language MMLCM MML Command Management MSC Mobile Switching Center NE Network Element NSAP Network Service Access Point NT ISDN Network Terminator NTP Network Time Protocol OEM Original Equipment Manufacturer OS Operating System OSI Open Systems Interconnection PBX Private Branch eXchange PC Personal Computer PIMS Protocol-Independent Messaging System POTS Plain Old Telephone System PPP Point to Point Protocol PRI ISDN Primary Rate Interface (S2M) Q3 Interface name as defined in ITU-T Rec. M.3010 A30828-X9410-B082-35-7619 9/185 . ..............................................16 Figure 2-2: LIOS network configuration for monitoring of fixed.......................................................54 Figure 3-23: NE data wizard – transport system / IP.................................40 Figure 3-13: Group data form.............44 Figure 3-16: Host Administration............................................................................................................................2 User Manual – Administrator Issue 35 RAI Remote Administration Interface RAS Remote Access Service RMI Remote Method Invocation (Java) RPPW Replay-Protected PassWord SuB Systemunabhängige Betriebsführung SVC Switched Virtual Connection SWSG SoftWare SafeGuarding TCP Transmission Control Protocol TZ Technologiezentrum URL Uniform Resource Locator WAN Wide Area Network WS WorkStation X...........................................................................................55 Figure 3-24: NE data wizard – transport system / IP (hiQ4200/8000) ....................37 Figure 3-10: User data wizard – external alarming (optional page) .................................................................................................................................................................... NE activation...................................................................50 Figure 3-21: NE data wizard – LI NE passwords and specific parameters (EWSD and hiQ/E9200) ....................................3 List of Figures Figure 2-1: Lawful Interception concept (overview)..........................46 Figure 3-18: NE data wizard – General ......22 Figure 2-7: LIOS components and connections ..42 Figure 3-15: Host Administration....... NE filter ..................32 Figure 3-5: User Administration.............................................................................................25 OSI Recommendation for WAN Networks 0.....................................20 Figure 2-5: Active monitoring in intelligent networks ............................................................................................................................................................................................19 Figure 2-4: Network configuration with LIOS as an umbrella system (example) ......................................25..................45 Figure 3-17: Host Administration........................18 Figure 2-3: LIOS network configuration for Internet and e-mail monitoring (example) ............................................................31 Figure 3-4: Filter form: bottom section................................................ group filter.................39 Figure 3-12: User Administration..................................................................................................................................................52 Figure 3-22: NE data wizard – transport system/X.............................56 Figure 3-26: NE data wizard – Call content routing properties (Huawei C&C08) ...............................................................26 Figure 3-1: LIOS main page – organization ..... general information and group members.................................................21 Figure 2-6: LIOS network configuration for PBX monitoring (example) ....................36 Figure 3-9: User data wizard – operator rights and group memberships............................................................................................55 Figure 3-25: NE data wizard – Communication properties (Huawei C&C08) .................................................................................................25 Figure 2-9: LIOS operation model with operator groups ...........................................28 Figure 3-2: List form example..................49 Figure 3-19: NE data wizard – General ............................35 Figure 3-7: User data wizard – general and security information..................41 Figure 3-14: Host Administration..............................................................................56 10/185 A30828-X9410-B082-35-7619 ...........................................................................................................................................................................23 Figure 2-8: LIOS with external interfaces ............................................................................................................................ NEs .................................................................................................................................................................... mobile and next-generation networks (example)..........................................................................................................................50 Figure 3-20: NE data wizard – General ....................................LIOS V8.........................36 Figure 3-8: User data wizard – user role ...................................................................................................34 Figure 3-6: User Administration – user filter.......................................................38 Figure 3-11: User Administration – Groups....................................................................................................................30 Figure 3-3: Filter form: top section........................ NEs – Communication Settings.... ..................................................................................................................................................78 Figure 3-52: OS server data wizard – IMS authorization data (IMS) .................................................................................................................. 105 Figure 3-82: LEA data wizard – FTAM selectors.......................................................................................................... 107 Figure 3-84: LEA data wizard – transport system (X............................70 Figure 3-45: OS Server data wizard – General .................62 Figure 3-34: Application data wizard – file group password..................................................................................92 Figure 3-67: LEA data wizard – EWSD and hiQ/E9200 observation parameters...................... IRI records per FTAM/IP ...............................................................................Mediation Device (Siemens IP) .......................................................................2 User Manual – Administrator Issue 35 Figure 3-27: NE data wizard – Authorization data (Huawei C&C08) ........................................................................................................................... 103 Figure 3-79: LEA data wizard – IMS...................................................................................................................................................................................64 Figure 3-37: Application data wizard – NE user IDs (MMLCM) .......................................................................................78 Figure 3-53: Activation/Deactivate OS servers ............................................................................................................................................................98 Figure 3-72: LEA data wizard – Huawei Fixed observation parameters ........................73 Figure 3-47: NE data wizard...................................................................................................63 Figure 3-36: Application data wizard – access password (S12) ...................................................................................81 Figure 3-56: LIOS server data wizard – General section ........ IRI records per FTP....................................................................................................................................................................................................................................................................25) ......................58 Figure 3-29: NE data wizard – transport system / Siemens [email protected] Figure 3-41: Application data wizard – FT authorization ....................................................................................79 Figure 3-54: Host Administration..............................................................................65 Figure 3-39: Application data wizard – authorization data .....83 Figure 3-58: LIOS server data wizard – Applications .......................................................63 Figure 3-35: Application data wizard – EFD NE password .................................60 Figure 3-32: Application data wizard – general data .............................................................................. NE Networks.................................83 Figure 3-57: LIOS server data wizard – transport systems ............................................................ 100 Figure 3-75: LEA data wizard – Mediation Device (Siemens IP) observation parameters .96 Figure 3-70: LEA data wizard – Huawei GSM observation parameters.................................93 Figure 3-68: LEA data wizard – hiQ4200/8000 observation parameters .......................................................................................................................................................97 Figure 3-71: LEA data wizard – Alcatel S12 observation parameters................................................................ 106 Figure 3-83: LEA data wizard – transport system (IP) ...................................................................68 Figure 3-42: Application data wizard – FT Authorization form ................87 Figure 3-62: NE network data – ‘Access to NE network’ form ...................................................................... 102 Figure 3-78: LEA data wizard – IMS........................................................................................................88 Figure 3-63: LEA Administration..77 Figure 3-51: OS server data wizard – MMLCM authorization data form (IMS) .59 Figure 3-30: NE data wizard – Authorization Data (Nortel via LIM) ..............................................................................................................................73 Figure 3-46: OS Server data wizard – Communication Parameters (LIM).......... 108 Figure 3-85: Communication Settings form (LEAs)....................................69 Figure 3-44: Host Administration.......................................................................................... LIOS Servers ......................99 Figure 3-73: LEA data wizard – HI2 processing server........ OS Servers .......................................... 101 Figure 3-76: LEA data wizard – Nortel Fixed (LIM) observation parameters .......... NE network.................80 Figure 3-55: Host Administration..86 Figure 3-61: NE network data form...................................99 Figure 3-74: LEA data wizard – Huawei GSM observation parameters................91 Figure 3-66: LEA data wizard – profile types ................. 109 A30828-X9410-B082-35-7619 11/185 ...............84 Figure 3-60: Host Administration...............................................................................................91 Figure 3-65: LEA data wizard – LEA identification ...................................................................................................................... 104 Figure 3-80: LEA data wizard – IMS...........................................................................................................................................LIOS V8.......68 Figure 3-43: Reset passwords – ‘NE passwords’ form ................................................................................................74 Figure 3-48: OS server data wizard – Transport system and OS server user IDs (IMS)..................................57 Figure 3-28: NE data wizard – transport system / IP (Huawei GSM).......................95 Figure 3-69: LEA data wizard – MSC observation parameters..................................................61 Figure 3-33: Application data wizard – OSI........................................................ 102 Figure 3-77: LEA data wizard – Utimaco IMS observation parameters ..........................................................................................................................84 Figure 3-59: Application data form ............89 Figure 3-64: LEA filter......66 Figure 3-40: Application data wizard – MMLCM authorization data.............................................................................................................. 109 Figure 3-86: Check LEA modification ...............25 ........... IRI records per FTAM/X......................................................60 Figure 3-31: NE data wizard – Applications ...................75 Figure 3-49: OS server data wizard – OS server user IDs (IMS)................... OS filter.................................................................................... transport system ......................................76 Figure 3-50: OS server data wizard – MMLCM authorization data (IMS) ............. 105 Figure 3-81: LEA data wizard – transfer protocol.......................................64 Figure 3-38: Application data wizard – NE user ID ................... ................................... 122 Figure 3-92: Alarm filter .................................................... 125 Figure 3-95: Alarm type filter ................... 178 Figure 5-27: Configuration of the TopSec Administration Tool ....................................................................................LIOS V8.... 110 Figure 3-88: LEA Administration: CUG parameters ......................... 135 Figure 3-104: EFD Administration – filter ......................................................................................................................................... 171 Figure 5-18: Stack Manager in Solstice OSI software – Configuration of CONS ........ NE/OS server response.................................................................................... 176 Figure 5-25: ‘Local Initiator Configuration’ of Solstice FTAM software .25 software: LLC2 Link – ‘Closed User Group and Facilities’ window ........... 115 Table 3-3: NE LI alarms from LIM .............................................................................................................................25 software: LLC2 Link – ‘Closed User Group and Facilities’ window ...............................................25 software – ‘Throughput Class and Window Size’ window ..................... 175 Figure 5-24: ‘FTAM Configuration Tool’ of Solstice FTAM software – main window ..................................................................... 181 Figure 5-30: Jobs form of the TopSec Administration ...............................................................................................25 software – ‘Timers and Counters’ window ......................................... 162 Figure 5-8: Solstice X..........25 software – ‘Throughput Class and Window Size’ window ............................. 180 Figure 5-29: Device Table with all configured TopSec Boxes.........................................................................................................................................4 List of Tables Table 3-1: NE Networks sub-application ...............25 software – ‘Addressing Parameters’ window ..................................25 software – Main window ......................................................................................................... 125 Figure 3-96: MML command states............................................................................................................................................................................ 134 Figure 3-103: EFD Administration ...25 Features’ window ..........................................................................................2 User Manual – Administrator Issue 35 Figure 3-87: LEA Administration: CUGs................. 179 Figure 5-28: Default Configuration of the TopSec Boxes..................................................25 software – ‘Closed User Group and Facilities’ window...................................... 160 Figure 5-6: Solstice X............................................................... 172 Figure 5-19: Window ‘Network Layer Addresses’ of Solstice OSI software.......25 software X......................... 174 Figure 5-22: Route Manager window – Host Routes ................................................. 163 Figure 5-9: Solstice X.......................................................25 Link – Link Editor window ............................................................................................................. 169 Figure 5-16: Window ‘Application Selectors’ in Solstice OSI software..................................................... 114 Figure 3-90: Alarm browser........................... 116 12/185 A30828-X9410-B082-35-7619 ........................... 120 Figure 3-91: Alarm details ............25 Features’ window ................... 165 Figure 5-11: X................ ....................... 139 Figure 5-1: X...........................85 Table 3-2: NE LI alarms from EWSD................................................................................................. Alarms.................................... 169 Figure 5-15: Window ‘Device Configuration’ of Solstice OSI software..................................................................................................... 130 Figure 3-100: MML console...................................................................................................... 183 0.................................................................... 170 Figure 5-17: Stack Manager in Solstice OSI software – Configuration of ‘Transport over CONS’ .................................................................................................................................................................................................................... Prompt form ................................................................................................................................25 Routing Table – Definition of host routes ................... 168 Figure 5-14: Window ‘Stack Manager’ of Solstice OSI software.............................. 137 Figure 3-105: EFD data wizard – common EFD data .................................. 174 Figure 5-23: ‘Remote X..... 123 Figure 3-93: Alarm browser: Alarm types ...................................................... 116 Table 3-4: NE LI alarms from hiQ4200/8000.............................. 167 Figure 5-13: ‘OSI Administration Tool’ main window (Solstice OSI software)............................... 127 Figure 3-97: Selection form ..................................................... 159 Figure 5-4: Solstice X... 164 Figure 5-10: Solstice X.................. 133 Figure 3-102: MML filter .......................... 173 Figure 5-21: ‘Remote X..................................25 Administration Tool of the Solstice X...................................................................................................... 159 Figure 5-5: Solstice X........... 131 Figure 3-101: MML browser ............................................................................................................25 Routing Table – Definition of the default route.............................. 111 Figure 3-89: Changes of alarm states ............................................................................ 182 Figure 5-31: Device Configuration of TopSec Box for plain data transfer.. 138 Figure 3-106: EFD data wizard – parameters for EWSD and hiQ/E9200 .................................... 128 Figure 3-99: MML console...................... 176 Figure 5-26: Hardware Configuration overview of LIOS......... hiE/Q9200 and Alcatel S12 ............... 166 Figure 5-12: X................................25 software: LLC2 Link – ‘Link Editor’ window ..................................................... 124 Figure 3-94: Alarm type details Alarm type filter ............ 172 Figure 5-20: Route Manager window – Prefix Routes.................................... 158 Figure 5-3: Solstice X........................................................................................ 157 Figure 5-2: Solstice X................................................................................................................................................................. 161 Figure 5-7: Solstice X............................ 128 Figure 3-98: MML console............................................................ .............................................................................................................................................. 119 Table 5-1: Configuring Solstice X................ 156 Table 5-3: Default parameters for the administration of TopSec Boxes ..........................25 software: X..............................2 User Manual – Administrator Issue 35 Table 3-5: LI NE alarms from IN@vantage ....................................................... 185 A30828-X9410-B082-35-7619 13/185 ........25 Link ......... 179 Table 5-4: Parameters for a new TopSec Box ............................... 182 Table 7-1: LIOS – supported network elements...........................25 software: LLC2 Link ........................................................................................................................... 116 Table 3-6: LI NE alarms from Mediation Device (Siemens IP)........................................................................................................................................................................ 156 Table 5-2: Configuring Solstice X...LIOS V8........ 180 Table 5-5: Parameter table for changing to plain data transfer.............. 116 Table 3-7: LIOS alarms ............................................................. They are the original manuals from these manufactures.2 LIOS manuals The structure of the LIOS manuals reflects the different LIOS user roles (administrator. e. 1. introduction of LIOS user roles and their tasks. Presentation and explanation of the LIOS system. 1.3 Target group and structure of this manual This manual addresses LIOS administrators. error corrections and notes to the user. see [1]. For an introduction to LI.2 User Manual – Administrator Issue 35 1 Introduction Lawful Interception Operation System (LIOS) provides services and applications for the operation of Lawful Interception (LI) on network elements of different vendors (see Annex 2: LIOS – supported network elements). Hardware and standard software manuals. the forms provided for data input. operator. Project-specific configuration documents (‘Handover Document’). LIOS online help. for an introduction to LIOS.LIOS V8. which MML commands are allowed on the MML console.g. LIOS applications and their functions. functional limitations. 1. Description of the individual configuration of LIOS in the user’s project. It is organized as follows: Chapter 1: Introduction Chapter 2: System description Chapter 3: Working with LIOS Chapter 4: Special working procedures Chapter 5: System configuration Chapter 6: Annex 1: external alarming – email and SMS formats Chapter 7: Annex 2: LIOS – supported network elements 14/185 A30828-X9410-B082-35-7619 . supervisor). and data input format. In-detail description of windows. ─ User Manual – Administrator. LIOS Troubleshooting Guide Helps a LIOS administrator to deal with system troubles.1 Documentation overview The LIOS documentation is made up of the following: LIOS manuals. individual fields and parameters. Documentation of the products from other manufacturers used in the LIOS system. ! For a summary of the authorized versions of the hardware and software products used. ─ User Manual – Supervisor. Installation Manual Provides information about the installation of LIOS. and how installation and cabling are implemented. User manuals For each user role there is a separate manual: ─ User Manual – Operator. see [2]. refer to the ‘Handover Document’. Also a wide variety of technical problems have been solved: for example. was awkward and. LIOS and LI adhere to the guidelines on security made by international standardization bodies (e. 2. enterprise networks. Meanwhile efforts have been made by switch manufacturers to integrate the interception function in the hardware and software of the switch – e. For efficient monitoring. there is no way of finding out which subscribers are being monitored. This. It offers high flexibility as regards network organization. The LI feature is integrated in the hardware and software of switches. The Siemens Lawful Interception solution includes the Siemens Monitoring Center. nextgeneration. LIOS as a management system provides functions and a GUI for convenient administration of lawful interception by the personnel in charge. which takes over most of the monitoring work from LEAs. LIOS (see Chapter 2. passive taps and data collectors (combined in groups) are placed at several locations and the required data is extracted by means of IP triggers. ETSI).LIOS V8. now there are no more nailed-up connections or leased lines – the necessary monitoring connections are set up dynamically.2 User Manual – Administrator Issue 35 2 System description Throughout the world. mobile. involving a greater variety of devices.1 The Siemens Lawful Interception solution The Siemens Lawful Interception solution comprises network elements (for fixed. since the build-up of the connection to the law enforcement monitoring facility (LEMF) was often accompanied by cracking noises. The flow of information is automatically routed from monitored communication channels to the law enforcement monitoring facility (LEMF) – without affecting normal network operation. geographical locations. Interception was originally done by tapping telephone lines. however.g. LIOS offers the possibility of moving the administration of Lawful Interception away from switches and setting it up at a central site. legislation and standardization in the field of lawful interception are now compelling network operators to use call-processing equipment. Although expert personnel could well be aware of the possibility of monitoring taking place. Monitoring Internet traffic is different: the Internet is a more complex network. It makes possible a smooth and discreet functioning of lawful interception on switches and in the telecommunications network. At the same time it meets the strictest legal requirements. Internet traffic and e-mail). and switch types. which enables all types of telecommunication to be monitored or recorded as required. A30828-X9410-B082-35-7619 15/185 . LIOS (Lawful Interception Operation System) combined with the LI feature of telecommunications switches is a state-of-the-art solution for efficient and discreet lawful interception. LIOS is connected to switches over the telecommunications or IP network.2) and the Siemens Monitoring Center. it did not always pass unnoticed.g. the Lawful Interception (LI) feature. ─ A subscriber can be monitored by several LEAs simultaneously.IMEI (international mobile equipment identity). Monitoring of all types of subscribers and services available in the network.g. UMTS.PRM (Premium Rate) .UAN (Universal Access Number) .MSISDN (mobile subscriber ISDN number).g. It is thus possible to observe all subscribers from or to whom connections are set up via a monitored NE – i.LNP (Local Number Portability) 16/185 A30828-X9410-B082-35-7619 . LI always supplies the complete content of the communication to and from a monitored subscriber. Call content and IRI records can be transmitted to several LEMFs – with numerous options available. FDNs are telephone numbers – or their first digits – in transit traffic.IMSI (international mobile subscriber identification) or . data. GPRS and VoIP. Internet traffic and e-mail.LIOS V8. A LEMF can be provided with both communication content and IRI records. HI3 signaling method (UUS/sub addressing). ticket output format (ETSI/ASCII/native). So each LEA can have its own settings.NTS (Number Translation Services) .e. ─ Transfer of call content and IRI records to LEMFs. . NE lines are monitored for the FDNs specified. or only with IRI records (for statistical monitoring). SMS.2. subscribers assigned to other NEs or other network providers (e. The following features are supported: . ─ A mobile-network subscriber on MSC can be identified through . e. ─ Active monitoring in intelligent networks.g. POTS.and called-line numbers are transmitted in the signaling. coin-box telephones.2 User Manual – Administrator Issue 35 NE LI admin Telecommunications network IRI records Judge IRI records Communication content LEMF Figure 2-1: Lawful Interception concept (overview) What the Siemens Lawful Interception solution offers ─ Interception of telecommunications in fixed. facsimile. mobile and next-generation networks: voice. see ‘Monitoring of enterprise networks’ in Chapter 2. e. GSM. ─ Monitoring of FDNs (foreign directory numbers). mobile-network subscribers) – provided that calling.FPH (Freephone) .VPN (Virtual Private Network Services) Number Portability Services . ISDN. ─ Monitoring in enterprise networks (private branch exchanges: PBX – Siemens HiPath). 2 User Manual – Administrator Issue 35 .SNP (Service Number Portability) . LI works without being noticed by subscribers and telephone company employees. The only persons aware of it are LIOS personnel and LEA officials.VCC (Virtual Card Calling) .LIOS V8. This is a comprehensive system offered to law enforcement agencies. processing. ─ Clandestine functioning. ─ Siemens Monitoring Center (MC).PCS (Personal Communication Services) . call diversion and malicious-call identification. i. A30828-X9410-B082-35-7619 17/185 .e. it takes over most of the monitoring work from them. e.PPS (Prepaid Services) ─ Monitoring of special features. even NE administrators. evaluating and storing of intercepted information. receiving.g. 2 LIOS While the LI feature covers the overall concept of lawful interception. Alarm messages received from switches are forwarded to the personnel concerned.2 User Manual – Administrator Issue 35 2.LIOS V8. LIOS deals with its administration and the forwarding of intercept-related information. it is routed by the NE directly to the appropriate law enforcement monitoring facility (LEMF). mobile and next-generation networks (example) Roles assumed by LIOS LI administration IRI mediation IRI record routing Alarm handling 18/185 Activation. Active monitoring in fixed and mobile (wireless) networks This covers PSTN (Public Switched Telephone Network). IRI records are received from switches and routed to LEMFs. deactivation and modification of interception measures and management of switch and LEMF interfaces. even of different makes. at the same time. A30828-X9410-B082-35-7619 . This allows LI administration (= observation handling) from one uniform GUI. LIOS embedding in different networks LIOS can access different switch types and versions. Mobile switch IRI records IRI records and alarms LI admin. The intercepted information itself (call content) does not reach LIOS. GSM (Global System for Mobile Communications) and NGN (Next-Generation Network). Mobile network HI2 (IRI records) Fixed network Fixed- NGN switch Target of interception HI3 HI3 Target of interception HI3 (Communication content) network switch Target of interception LEMF Figure 2-2: LIOS network configuration for monitoring of fixed. IRI delivery in the types and formats requested by LEMFs. Next-Generation network LI administration IRI records and alarms LI admin. 19/185 . which are configured on data collectors via a mediation device.2 User Manual – Administrator Issue 35 Monitoring of Internet traffic and e-mail This is done through a passive tapping solution: data collectors (combined in groups) are placed at several locations and the relevant data is extracted by means of IP triggers (filters) and passive taps (see Figure 2-3). A LIOS operator specifies IP triggers. The data is transferred to a mediation device and routed to the LEMF (LIOS is not involved in routing of the intercepted data). Communication content HI2/HI3 Mediation device LEMF Figure 2-3: LIOS network configuration for Internet and e-mail monitoring (example) Roles assumed by LIOS LI administration Alarm handling A30828-X9410-B082-35-7619 Activation. deactivation and modification of interception measures and management of mediation device and LEMF interfaces Alarm messages are collected from MDs and forwarded to the personnel concerned.LIOS V8. Passive tap IP network Data collector LI administration Target of interception LI admin. others via a foreign OS (e. Figure 2-4 shows LIOS accessing different hosts in different ways.g. Some hosts (e. and HI2 Foreign interception operation system LI admin. The advantages of LIOS can be made use of throughout the network. and HI2* HI2 HI2* LI admin.2 User Manual – Administrator Issue 35 LIOS acting as an umbrella system To allow uniform LI administration in heterogeneous networks. deactivation and modification of interception measures IRI records are received from foreign LI management systems and routed to LEMFs.LIOS V8.g. Provision of a uniform GUI to LI personnel A30828-X9410-B082-35-7619 . and HI2 LEMF HI3 HI3 HI3 * mutually exclusive HI2 routes Telecommunications network Figure 2-4: Network configuration with LIOS as an umbrella system (example) Roles assumed by LIOS LI administration IRI mediation Umbrella function 20/185 Activation. LIOS acting as an umbrella system LI admin. Nortel switches via KCC Lawful Interception Manager (LIM)). LIOS – functioning as an umbrella system – can be combined with interception operation systems of other manufacturers (foreign OS). Siemens EWSD) are accessed directly. switching and the services of a communications network are performed separately: by service-neutral switching nodes (Service Switching Points. The IN@vantage platform includes special services for prepaid telephony. IN@vantage) and the LEMF interfaces. deactivation and modification of interception measures and management of switches (Fixed network.LIOS V8. LI administration covers both the IN@vantage switch and the Fixed network/NGN switch. 21/185 . respectively. SSPs) and by a central service control node (Service Control Point. HI2 LEMF LI admin. NGN and IN@vantage) are forwarded to the personnel concerned. IRI records are received from switches and routed to LEMFs. the integration of third-party services and provisioning of virtual private networks. IRI delivery in the types and formats requested by LEMFs. Alarms IRI records and alarms HI3 IN network Target of interception IN@vantage INAP Fixednetwork NGN switch switch Figure 2-5: Active monitoring in intelligent networks Note: INAP (Intelligent Network Application Part) is the Interface between SCP and SSP Roles assumed by LIOS LI administration IRI mediation IRI record routing Alarm handling A30828-X9410-B082-35-7619 Activation. SCP).2 User Manual – Administrator Issue 35 Active monitoring in intelligent networks In an intelligent network (IN). LI admin. NGN. Alarm messages received from switches (Fixed network. ‘ETSI V2.LIOS V8. IRI record conversion is possible. which is a Handover Interface Port 2 (HI2 – for intercept-related information) according to ETSI. e. It meets all requirements laid down in the ETSI Standard ES 201 671 V2. but the communication content itself does not reach LIOS. a record of receipt and delivery is kept in the LIOS database. For the communication with switches. IRI record conversion. LI-BASE and CAP run on the same machine. LIOS can convert IRI records into different formats. if required. It deals with the administration of interception measures and the generation and forwarding of IRI records. Simultaneous handling of different NE types. If a LEMF requests IRI records in a format different from the one provided by a switch – directly or via a foreign OS –. the CAP PC. In case of Siemens hiQ 4200/8000 switches. It includes the delivery and. The communication content lines are managed by LIOS. according to ETSI Standard ES 201 671 V2. LIOS general features LI administration (= observation handling).1. LIOS–LEMF IRI interface.1). IRI record routing. Roles assumed by LIOS LI administration IRI record generation and routing (HI2) Management of HI3 interface 2.2. LIOS receives IRI records from NEs or foreign OSs and routes them to LEMFs. LIOS-HP. also conversion into ASCII format is possible.g.2 User Manual – Administrator Issue 35 Monitoring of enterprise networks (PBX – Siemens HiPath) LIOS is the system-integrated lawful interception solution for Siemens HiPath. HI2 LIOS-HP LI-BASE CAP HI3 LEMF CAP PC CSTA HiPath HI3 HiPath CSTA Figure 2-6: LIOS network configuration for PBX monitoring (example) LIOS-HP communicates with switches and manages LI through LI-BASE and CAP (common administration platform). 22/185 A30828-X9410-B082-35-7619 . it is routed from the HiPath switch directly to the respective law enforcement monitoring facility (LEMF). The LIOS–LEMF IRI interface can be readily adapted to meet national requirements. LIOS invokes the duplication of the content of communication and its routing to LEMFs.1 format’ (i.1 Activation. conversion of IRI records (to meet technical and national requirements). LIOS normally accesses NEs directly. IRI records are transferred to LEMFs through the LIOS–LEMF IRI interface. LIOS can simultaneously handle NEs of different types and versions and belonging to different providers (network operators).1 (2001-09). CSTA is used.e. deactivation and modification of interception measures IRI records are generated based on the interception event information received from switches and sent to LEMFs. for some NE types an umbrella solution with foreign OSs is recommended. through a Q3 interface. Summary suspension of interception measures on NEs or foreign OSs.25 Call content LI admin LIOS server LIOS client Intercepted object NEs Figure 2-7: LIOS components and connections LIOS server The LIOS server maintains the connection with the telecommunications network and houses the LIOS database. LIOS has been supplied with powerful security features. Communication with NEs and foreign OSs from a command console for diagnosis and troubleshooting purposes. If the LI database of an NE or a foreign OS on the one hand and the LIOS database on the other are out of step. EFDs concerning lawful interception can be set up and administered on NEs from LIOS directly. CD. comprehensive logging. If an NE or a foreign OS is overloaded or needs servicing or upgrading. For the communication with NEs. security hardening. LIOS can automatically restore all interception measures (‘resume’). Web applications for all LIOS users (MS Internet Explorer).g. passwords are needed. encryption technology. Automatic handling of expired passwords.2 User Manual – Administrator Issue 35 LIOS converts CALEA-compliant CDC messages to ETSI-compliant IRI records.LIOS V8. Not all NE types and foreign OSs support all features listed here.2 LIOS components LIOS Remote LIOS clients IRI records IP/ISDN/X. Some of these passwords expire after a certain time. 2. e. receives IRI records from A30828-X9410-B082-35-7619 23/185 . IP Sec and security certificates. ‘Wizards’ within applications lead the user through the steps of standard working procedures. Security.25 IRI-records E-mail. Convenient graphical user interface. LI database synchronization. Various filters support information retrieval. LIOS can handle filenaming methods according to ETSI and country-specific requirements. Once the NE or foreign OS is available again. . LIOS server IP or IP/ISDN LEMF LAN PSTN/NGN IRI records IP/ISDN/X. floppy . EFDs (event-forwarding discriminators) are used for the automatic sending of IRI records and alarms from some NE types (Siemens EWSD/hiE9200) to the LIOS server. To prevent misuse. LIOS automatically replaces an expired password with a new one (cyclic password exchange). It communicates with NEs and also foreign OSs (see Figure 2-4). . they can be automatically synchronized. a sophisticated user role model. A comprehensive online help is provided. LIOS can summarily suspend (= temporarily cancel) all interception measures created there.2. IRI records can be delivered by e-mail. CD or floppy. LIOS standard system and LIOS single system In a LIOS standard system. If the connection to a LEMF is broken. On customer request. LIOS servers can be added to cope with the extra load and to keep system performance high. 2. LIOS clients can be set up within the LIOS high-security area (centralized) or they can be set up anywhere remote (decentralized). more observations can be set up and more IRI records must be expected. LIOS can be supplied as a single system (only one LIOS server) – although at the expense of reliability. several external interfaces are provided. the other can take over (hot standby). This means that LIOS users can work hundreds of miles away while security is still maintained (owing to user authentication and HTTPS). Owing to its scalable architecture.LIOS V8. and communicate with the LIOS server from a Web browser through HTTPS.2 User Manual – Administrator Issue 35 NEs and foreign OSs and routes them to LEMFs.2. LIOS clients LIOS users work on LIOS clients. LIOS clients are regular PCs with standard software and a Web browser. The LIOS server is always set up in a high-security area. If a network has a great number of NEs. LIOS users log in on a LIOS client. How far LIOS can be expanded also depends on the number of ports on NEs and the type of connection. LIOS can be configured to fit network size. the data entered by the users is processed by the LIOS server.3 LIOS interfaces For optimum integration of LIOS in a telecommunications network. Depending on the needs of a network provider. servers and connections are duplicated (redundancy concept) – if one fails. Remot LIOS Externa alarmin throug PIMS LIOS Cloc E-mai SMS GU GPS radio DCF7 NTP GU Externa Operato HI EO LE M INI INI INI INI INI INI INI INI Foreign interception operation system NE Mediation 24/185 IN NE A30828-X9410-B082-35-7619 . The LIOS server acts as a Web server for LIOS clients and accommodates all LIOS user software. If a recipient wishes to be alerted by e-mail instead of SMS or vice versa.2. ─ Watchdog feature: prematurely terminated processes are automatically restarted. ─ LIOS is always equipped with a software RAID. a hardware RAID can be provided. 2. the rights related to all three user roles can be given to a privileged person. LIOS servers and connections are duplicated – if one fails.2.2 User Manual – Administrator Issue 35 Figure 2-8: LIOS with external interfaces ─ Interfaces to LIOS clients (see ‘LIOS clients’ in Chapter 2. Time synchronization by means of NTP (Network Time Protocol) or a DCF77 or GPS radio clock.1. All LIOS machines receive the same time. PIMS can be configured to forward alarms of different types to different recipients and to use a specific service (SMS or e-mail) for each recipient. NEs. NEs and foreign OSs can have different times – they are not synchronized. either automatically on a regular basis or triggered by hand (not for all NE types). CD-ROM or floppy disk) is provided.2). Therefore. personnel in charge can be alerted any time and anywhere – by SMS or e-mail. apart from that. or through another connection. The difference of user rights and duties is also reflected in the user documentation – there is a separate manual for each user role. ─ The LIOS database is synchronized with the databases of NEs and foreign OSs. on request. Users will not know the details of the work related to the other user roles. Apart from that. supervisor and administrator – entails its distinct rights and duties.2. they will not be lumbered with information irrelevant to their work. without LIOS being affected. Systems like LIOS often operate in a closed area without anybody near. Through PIMS. Alarms can be classified according to subject and importance. ─ If an NE is unable to send IRI records to LIOS (e. an alternative way of delivering IRI records to the LEMF (e. An external operator can work with a graphical user interface of another manufacturer or with a command-line tool. the other can take over (see ‘LIOS standard system and LIOS single system’ in Chapter 2.5 LIOS user roles A role is assigned to each LIOS user. not all persons working with LIOS have to exactly fit in one of those user roles. through e-mail. Siemens Mediation Devices.10).g.LIOS V8. The communication protocol used is HTTPS. This renders misuse very difficult and guarantees optimum security and secrecy. Each role – operator.4 Data safety ─ In a standard LIOS system. because of a connection break). or the rights of LIOS operators can be divided among several types of LIOS operators.2. For instance. it writes them to an IRI record buffer file.2. this can easily be changed. Remark about LIOS user roles. This makes alarming especially important. ‘LIOS general features’) ─ The external operator interface (EOI) is a command line interface enabling external LI operators to access LIOS and to manage LIOS functions. in practical operation. ─ Alarms issued by NEs (not of all types) and by LIOS provide information about irregularities (see Chapter 3. ─ In case the connection from the LIOS server to a LEMF breaks. (This feature is available for Siemens EWSD/hiE9200. A30828-X9410-B082-35-7619 25/185 . it can be useful for LEA personnel to be informed about LIOS activities. Customers’ requirements differ from country to country. IN@vantage and foreign OSs (see Chapter 2.g.) 2.2) ─ Interfaces to LEMFs. which can be retrieved by LIOS as soon as the connection has been reestablished. ─ External alarming through PIMS (Protocol-Independent Messaging System). LIOS V8.g. the LIOS supervisor can invoke re-sending attempts or. Every action. The scope of work of the individual operator will depend on the rights assigned by the LIOS administrator. A LIOS supervisor’s work is assisted by alarms. He has to react to alarms received from NEs and foreignOSs. LIOS administrator The LIOS administrator manages LIOS users and LIOS operator groups.g. LIOS operators can be organized into operator groups (each operator has to be a member of one or several groups).2. is logged individually. log entries concerning expired observations) after a certain time. observation-related alarms (‘group alarms’) are conveyed to the group. They can communicate with NEs and foreign OSs from a command console for locating the origin of possible system misbehavior and for providing a remedy. The LIOS administrator has several means of trouble-shooting.2 and 2. foreign OSs and LEMFs. e-mail. They are alerted to irregularities by a comprehensive alarming system. LIOS supervisor As a safeguard against misuse. he can initiate IRI record delivery by an alternative way (e. this also includes the setting up of EFDs (event-forwarding discriminators) on NEs of certain types. however. Different rights can be given to different groups.3). For reasons of security. a selection of NEs can be accessed by one group. e. Operator A Operator B Operator C Operator D LIOS user group X NE 1 NE 2 NE 3 LIOS user group Y NE 4 NE 5 Figure 2-9: LIOS operation model with operator groups If a LIOS operator wishes to take over an observation from another group. CDROM or floppy disk).2 User Manual – Administrator Issue 35 LIOS operator LIOS operators are responsible for the handling of interception measures (LI administration) and occasionally also of LEMF data (e. a password is needed. For instance. creating or modifying LEMF objects). If entitled to. they can also temporarily cancel (suspend/resume) all observations set up on an NE (or foreign OS) or remedy LI database discrepancies. If connection problems hinder IRI record transfer to a LEMF. He is responsible for the administration of the entire LIOS system and of the connections to NEs. this includes the apportionment of rights.g. as is shown in the following figure. LIOS operators work under the supervision of a LIOS supervisor. He is responsible for deleting sensitive information (e.2. 26/185 A30828-X9410-B082-35-7619 . another selection by another. foreign OSs and LEMFs. if this also fails. Observations belong to the group. the LIOS supervisor inspects actions of LIOS administrators and operators and surveys all data traffic to and from NEs. LIOS operator tasks can also be performed by external operators (see Chapters 2. communicating with NEs and foreign OSs from a command console.g. logs and powerful tools for their handling. If your password has expired. the prompt window of the MML console). move the mouse pointer to the URL line and type the URL of one of the LIOS servers in your LIOS: https://<LIOS server>/lios For <LIOS server> you can enter the name or the IP address. A30828-X9410-B082-35-7619 27/185 .1 The LIOS main page The LIOS main page is made up of header. select Refresh from the application commands bar or select the Refresh icon ( ). Cancel and Close push buttons).1. Save the URL of the default LIOS server as home page and that of the other as bookmark. you may use the Back command of the Web browser. Notice regarding pop-ups LIOS also uses pop-ups to communicate with the user (e. enter the old password and a new password. Make sure that the Web browser you are using allows pop-ups from the LIOS server. enter your LIOS user ID and password. The LIOS main page is displayed. When prompted.1 The LIOS GUI Notice regarding Web browser handling For opening a new LIOS window. You can access LIOS functions from a Web browser – Internet Explorer (version 5.g. application commands bar and work area. 3. For details consult the Sun Solaris and the Windows XP documentation. 3.2 User Manual – Administrator Issue 35 3 Working with LIOS The LIOS client is a PC with MS Windows operating system. always use the ‘Open new browser’ command (navigation menu). please use the appropriate command provided on the LIOS GUI (Back command in the application commands bar or Previous. For updating the screen content. navigation menu.LIOS V8. If it is necessary to return to a previous LIOS page. ensure that the link is up. and then confirm the new password. Start the Web browser. Do not use commands and shortcuts provided by the Web browser.5 or higher). If the LIOS client is connected to the LIOS server through an ISDN link. Do not use the Back command provided by the Web browser (tool bar or right mouse key). Exception: To navigate through LIOS online help pages. The total of records is calculated and displayed in a separate window. which LIOS application and subapplication is open. The previous set of records is read from the database. (arrow back to first page). click on the Logout command. You can specify the size of a set of records in the Filter form. ‘Maximum number of rows’ pull-down list).1. On the right there are two fields that show the range of records (size of record set) that has been read from the database.3. " (right arrow).LIOS V8.e.2 User Manual – Administrator Issue 35 Header Application Commands bar Navigation menu Work area Figure 3-1: LIOS main page – organization 3. The commands on the right have the following effects: Count. ! (left arrow). in the meantime new records have been written to the database.1. ‘maximum number of rows’). An example should illustrate this.1. You have specified that the 30 newest data records should be read (Filter form. Since the data contained in the database may have changed since the last query. 28/185 A30828-X9410-B082-35-7619 . following the sorting order specified. the set of records read may not be exactly adjacent to the set of records last read. through which the next or previous set respectively is read from the database. which can take some time. these new records are now considered by the system as part of the 30 newest records. Consequently data records that were then among the 30 newest but are no longer so will be displayed again. The next set of records is read from the database.1 Header The header in the top section of the LIOS main page shows you under which LIOS user role and name you are logged in. intending to view the next 30 data records.1. Functioning of Next " and Previous ! Since there may be a great amount of data to be read (loaded) from the database. After some time you press Next. The records of the first page are retrieved from the database. To log out properly. however. i. Next and Previous start a new database query. The header also shows your current position on the LIOS website. you have the option to specify how many data records should be read at a time (see 3. ‘Maximum number of rows’ pull-down list. If. The 30 data records next to the newest 30 data records are read from the database. The word ‘Online’ on the right informs you that the connection to the LIOS server is active. General application commands Refresh. you can even have the same application open several times. you can change the export format (see 4.1. supervisor or administrator) and the scope of the LIOS system you are working with.g. copyright and configuration mode is displayed. Application-specific online help is provided. If after exporting you import the data in a spreadsheet application (e. Help. commas are used as separators (field delimiters). If a parameter of a record has no value. it means that the spreadsheet application expects another separator (field delimiter) than the one provided with the exported data. and general commands like Refresh.4 Work area (table) The work area is normally occupied by a table. they are not part of your LIOS system or you have not been given authorization to work with them. which contains the records that are managed through a particular application.2 Navigation menu The navigation menu on the left lists the LIOS applications and sub-applications available for the user logged in.2 User Manual – Administrator Issue 35 3. If no filter is used all records from database will be exported to a maximum number of records. (Also TXT format with tab stops as separators is supported. A30828-X9410-B082-35-7619 29/185 . To start an application or sub-application.3 Application commands bar The application commands bar contains application-specific commands. all data crammed into one column). MS Excel). application-specific commands will be available. You have to know your password (old password) before you can change it. Change password.16). warning and information messages. So you can work with LIOS from several Web browser instances at the same time. this means. a link to a filter. In this way you can have each LIOS application open multiple times. You can store one of these filter settings for each LIOS application for later use. If you think that LIOS should generally provide a different separator. The data is read from the database and the table is updated. it should automatically be presented as a table.1. Export and Help. A Print form is displayed where you can edit printing options and start the printing operation. The application data will be displayed in the work area. Print. General help is provided. According to the result of filter setting records are exported as a text file in CSV (commaseparated values) format.1. the field remains empty. 3.1. The choice of applications reflects your LIOS user role (operator. If this is not so (e. A form appears where you can change your LIOS user password. For each such application instance a filter can be defined. Open new browser. Type the new password into the ‘New password’ and the ‘Confirm new password’ input fields. A new LIOS main page is opened – in another instance of the Web browser. The maximum number is specified in the LIOS properties file and can be changed by the Administrator. click on the respective menu item. About. The latter are described here.g. It is also used for the display of wizard pages and of error.) Exporting data does not mean removing it from the LIOS database. Empty fields are rendered through two consecutive commas. Print.LIOS V8. 3. If applications described here are not available to you. which are available in every application.1. Remedy: Change the separators in the spreadsheet application (for MS Excel: Data/Text to columns) or in the Windows settings (Windows Control Panel->Regional Options->Numbers->List Separator). Help.1. thus viewing the application data in different ways. Information about LIOS program version. Export. licence. A printer-friendly HTML page reflecting the data currently displayed is generated. For reasons of ergonomics and system performance. To log out properly. 3.1 Shifting items between lists Figure 3-2: List form example To shift items between the lists. If a form serves only to view data. in ascending order. To update the table contents. To view the details of a record.LIOS V8. To perform an action on more than one record. for instance.1. this is indicated by an upward arrow ( ). If you click on the same column heading again. To find out the meaning of an icon. all fields are read-only. It is possible to copy the content of a read-only field to the clipboard (copy/paste). Read-only fields Read-only fields look the same as regular fields. the table contents are not automatically updated.2. Hyperlinks (→) Some output fields are equipped with a hyperlink (→) to detailed information. select the checkboxes on the left and then choose the appropriate command from the application commands bar at the top.2 Wizards.2 User Manual – Administrator Issue 35 Table handling To perform an action on a single record. Quick sorting does not work with all columns. (Do not use the refresh functions provided by the Web browser itself. >> All items are shifted to the right. Leaving the LIOS system.) Quick sorting: If you click on a column heading. an explaination will appear in a text bubble. ‘Generation time’ information: Below every table there is a line telling you when the data was read from the LIOS database and the table was generated (‘Generated on: <date> <time>’) – scroll down if necessary. select the ID (hyperlink) in the first column. If the data kept in the database has changed. the table is sorted by the content of this column. move the cursor to the icon. the Refresh icon ( ) appears at the bottom left. 3. click on an arrow next to a ‘LEA name’ field. select the appropriate icon in the Actions column on the right. click on the Logout command in the header. the table is sorted by the content of the column in descending order (downward arrow ). details of the LEA are displayed. click on the Refresh icon or select Refresh from the application commands bar. input forms and output forms A wizard is a sequence of forms that leads the user through the steps of data input.1. use the arrow push buttons: 30/185 > Selected items are shifted to the right. If you. A30828-X9410-B082-35-7619 . mm. ‘From <date> <time>’ and ‘To <date> <time>’ mark the beginning and the end respectively of the time period when data records were created.2. A30828-X9410-B082-35-7619 31/185 . The data you may have entered in the current page is preserved. the item will be unselected. The next page of a wizard is displayed. You can select more than one item from a list by using the mouse in combination with the Ctrl and Shift keys.e.1 General filtering functions Figure 3-3: Filter form: top section Time frame. The Close button is provided when no input is possible. Shift (!): Selection of a range of items. The OK button appears in some forms. including the present moment. In this section general filtering functions (i. 3. OK. the item will be selected in addition to the items selected already. Your input is discarded and the form is closed Help. The form is closed.2 User Manual – Administrator Issue 35 < Selected items are shifted to the left.g. Close. The two items including the range between them will be highlighted (selected). If you select an item while you are holding down the Ctrl key. see 3. but there is a high input tolerance. The content of the form is updated.LIOS V8. Applicationspecific fields are dealt with together with the respective applications. Input format: generally dd.2 Push buttons Previous. The previous page of a wizard is displayed.3. when data records were created. Your input is accepted and the form is closed. 3. Next.3.1. then hold down the Shift key and select another item.2.3 Working with filter forms LIOS provides various filter forms to support information retrieval. If you click on a selected item while you are holding down the Ctrl key. Finish.1. << All items are shifted to the left.1.yyyy and hh:mm:ss. Cancel. The Finish button appears in a single input form and in the last page of a wizard. Online help is provided 3.1. For details about filtering by date and time. From – To. Your input is accepted and the form is closed. Period of time. Refresh. Select one item. e. make your input first. Ctrl: Selection of more than one item. functions that are common to most LIOS filter forms) are presented and explained. in connection with a View command. ‘this week’. in the To fields: The time is automatically set to 23:59:59. Date has two values (separated by a delimiter). naturally. Date. Records are sorted in ascending (A -> Z) or descending (Z -> A) order. Time has only one value. Input made by the user Completion made automatically Time. however. Time frame in this context always marks a time period that includes the present moment.1. ‘this quarter’ and ‘this year’.yyyy and hh:mm:ss. Possible time frames are ‘today’. ‘this month’. is a considerable input tolerance – e. but no date. 3. If you wish to include all items not older than a certain point of time. the time frames provided go beyond the present moment). but no time in the From fields: The time is automatically set to 00:00:00. Flexible input format Generally speaking.3.LIOS V8. Records are sorted according to the column name you select. Maximum number of rows. There.1. if your input is incomplete. the input format is dd. Ascending/descending. ‘today & yesterday’. If you select a time frame.1. You can however refine the filter settings by editing the values of the From and To fields. Date has only one value. ‘this month & last month’.mm. The current date is automatically inserted. The value is recognized as a day number in a month – the current month and year are automatically inserted. it is automatically completed to agree with your presumable intention.g. The value is recognized as an hour – minutes and 32/185 A30828-X9410-B082-35-7619 . fill in the To fields and leave the From fields empty. ‘this week & last week’.1). Specify how many records will be loaded from the database at a time (see also Functioning of Next " and Previous ! in Section 3. the From and To input fields are automatically adapted (the To input fields remain empty because. The values are recognized as day and month numbers – the current year is automatically inserted.2 Filtering by date and time To filter by date and time you can do the following: ─ Select a time frame or ─ Specify a beginning (From) point and an end (To) point or ─ First select a time frame and then edit beginning or end point. Figure 3-4: Filter form: bottom section Order by. Radio buttons. If you wish to include all items up to a certain point of time. fill in the From fields and leave the To fields empty.2 User Manual – Administrator Issue 35 The main section of a filter form contains application-specific fields. 3.x not allowed " 127.1. A30828-X9410-B082-35-7619 33/185 . supervisor and operator – assign user rights to LIOS operators – assign LIOS operators to operator groups (Groups sub-application) – activate external alarming (PIMS) for individual LIOS users LIOS users have to assume one of the following user roles: – LIOS administrator.3. To activate saved filter settings.x not allowed " 127. . For each LIOS sub-application. Online help is provided. Some IP addresses are used for multicast. Reset. . However.’) for the date and colons (‘:’) for the time. Help.) attached to a network to refer to each other when sending information through a LAN (Local Area Network) or a WAN (Wide Area Network) or the Internet for example. Delimiters: The delimiters (separators) used by LIOS itself are dots (‘. Save. Your input is discarded and the filter form is closed.2 User Manual – Administrator Issue 35 seconds are automatically set to 00. press Load. IPv4 addresses are commonly expressed as a dotted quad: four octets (8 bits) separated by dots.x. – LIOS supervisor. . The values are recognized as hour and minute numbers – seconds are automatically set to 00. : . only within a field the delimiter must be the same.x. These IP addreses can not be used for switch and LEA configuration and will be checked by LIOS: " 224-255. used by network devices (routers. which means that the default settings are applied. Leading zeros are automatically inserted. Filter settings that have been saved are activated. you can save personal filter settings. 3.1. – LIOS operator. IP version 4 (IPv4) is the current standard protocol for the Internet.3 Filter push buttons Finish. Cancel. IP addresses consist of 32 bits (for more details see RFC 791). similar in concept to a telephone number. broadcast or loopback traffic. you can also enter other delimiters (? / .. The filter is reset. LIOS supports IP version 4 and the IP address classes A. but no application is available at present._ \) or leave a space.0. In the ‘Maximum number of rows’ pull-down list you can specify how many records will be loaded from the database at a time.4 IP address verification An IP address (Internet Protocol address) is a unique number. Load. B and C.0..1 allowed 3.LIOS V8. Time has two values (separated by a delimiter). computers. telecom switches.x. Your input is accepted and the form is closed. IP version 6 will also be supported by LIOS. Date and time without leading zeros.2 User Administration The LIOS User Administration enables you to – manage LIOS users – give each LIOS user a particular user role: administrator. time-servers.x. they are unselected.1. Print. For the commands Refresh. A filter form (Figure 3-6) is displayed. the data displayed reflects the default filter settings. Selected users are deleted.1. The user administration for external operators is the same as that for LIOS operators. A record of a deleted user is still kept in the LIOS database. Figure 3-5: User Administration Application commands New user. Delete users. Filter. When you start the User Administration. but deletion is nevertheless possible – observations belong to the LIOS operator group and not to the individual operator. Export and Help see ‘general application commands’ in Section 3. a message is displayed to this effect.4. and define sorting options. All records in the table are selected (checkboxes in the first column) or. you cannot delete your own user record (nor can you change your own LIOS user role). select the Filter command from the application commands bar. Records will only be deleted upon confirmation. Select/unselect all.2) is started. if all have been selected previously. observations and group alarms belong to a LIOS operator group and not to an individual operator.7). where you can enter the data for the new user to be set up. The user data wizard (see 3. A LIOS operator with observation manager rights must be made a member of all operator groups.2. If you wish to see another selection of data.LIOS V8. where you can specify which users should be displayed. LIOS operators can be organized into LIOS operator groups.3. If you are the only LIOS administrator. LIOS makes it possible to integrate external operators. Also the authorization for the communication with NEs and OSs through MML is given to LIOS operator groups (see NE user IDs in Section 3. If a LIOS operator still has observations assigned to him. 34/185 A30828-X9410-B082-35-7619 . A LIOS operator who has invoked ‘suspend NE/OS server’ cannot be deleted before the corresponding ‘resume NE/OS server’ operation has finished. you must select one or more user records. The user name has the string ‘_DEL_’ plus a sequential number appended to it. who can access LIOS through an external operator interface. A filter form appears. Before you can use this command.2 User Manual – Administrator Issue 35 As an optional feature. where you can specify criteria for the data to be displayed. it does not contain all details. Figure 3-6: User Administration – user filter User name.2. The user name cannot be changed – the corresponding field is read-only. Alarming state. All non-deleted LI users are displayed.2. A check mark means that external alarming is active for the particular user. you can define a filter. Table columns User name. For a detailed view. A deleted user’s name is marked by ‘_DEL_’ plus a sequential number appended to it. Activate/deactivate external alarming. A30828-X9410-B082-35-7619 35/185 .1 User filter If you wish to reduce the number of records to be displayed. The user data wizard (see 3. click on the user name (hyperlink) in the first column. Show users: Not deleted. Toggle switch. ‘Wild cards’ (‘*’ and ‘?’) are accepted. The user data wizard is started.2 User Manual – Administrator Issue 35 Table The table provides you with an overview of user information. All deleted LI users are displayed.1. Modify user. The user record is deleted. Actions. It contains the values of the selected user record. where you can modify the user record. functions that are common to most LIOS filter forms) and push buttons see 3. If a field is empty or not selected. To show the Alarming state of an external alarm is an optional feature (depends on the LIOS license). Copy user. Remark. Deleted.1. External alarming is activated or deactivated. Delete user. it has no influence on the filtering process. Name of LIOS user Operator/External operator/Supervisor/Administrator. Only records are displayed whose names match the string entered. For a description of general filtering functions (i. A check mark in the respective column indicates the user role (an external operator is a LIOS operator who works from a system other than LIOS).2) is started.3. These actions affect only the individual record. You can modify these values – at least you have to enter a new user name. ‘Wild cards’ (‘*’ and ‘?’) are accepted.e.LIOS V8. Only records are displayed where a remark added matches the string entered. 3. ASCII characters.2 User data wizard To start the user data wizard. you cannot change your own LIOS user role.2. OPERATOR RIGHTS AND GROUP MEMBERSHIPS This page is provided only for setting up operators. LIOS administrator. Name of the LIOS user (case-sensitive). LIOS operator. External operator. ASCII characters. Confirm password.2 User Manual – Administrator Issue 35 3. Checkboxes: Change on first login. Internal operator. and communicate it to the user. Specify the password the user has to enter. Password never expires. Maximum length: 60 characters.LIOS V8. Supervisor. Maximum length: 25 characters. LIOS supervisor. User role Figure 3-8: User data wizard – user role Select one of the option buttons provided. General and security information Figure 3-7: User data wizard – general and security information User name. The user will have to change the password at the first login. 36/185 A30828-X9410-B082-35-7619 . Remark. Password. Optional parameter. depending on the role the user is to assume. select ‘new user’. Administrator. Retype the password. LIOS operator who works from a system other than LIOS. ‘modify user’ or ‘copy user’. If you are the only LIOS administrator. Groups of which the operator is not a member. The names are shifted to the ‘selected operator groups’ list. How to shift items between the lists with the arrow push buttons and with the Ctrl and Shift keys is explained in Section 3. Observation Manager. Operator group memberships LIOS operators can be organized into operator groups. observations and group alarms belong to an operator group and not to an individual operator. Observation Handling. The observation manager is an optional feature (depends on the LIOS license). Groups of which the operator is a member. LEA Administration. the operator can still handle alarms (Alarm browser). Synchronizing the LIOS database with the LI database of the NE/OS server. Select the appropriate checkboxes (more than one selection is possible). Available operator groups. operators can be authorized to use only a selection of LIOS applications.1. Sending MML commands to NEs and OS servers from the MML console application. To assign an operator to groups. for aligning the LI database of the NE/OS server with the LIOS database. MML Handling. A30828-X9410-B082-35-7619 37/185 . Creation and administration of observations. Administration of LEA data. LIOS operators with Observation Manager rights must be members of all operator groups. The ‘operator group memberships’ form enables you to assign one operator to one or more operator groups.1. If you do not select any checkbox.2 User Manual – Administrator Issue 35 Operator rights Figure 3-9: User data wizard – operator rights and group memberships Other than administrators and supervisors. Selected operator groups. and for suspending and resuming observations and LEAs (OBSGRP) on the NE/OS server.LIOS V8.2. select the groups from the ‘available operator groups’ list on the left and press the ‘>’ button. for an explanation of ‘VIP alarms’. If it is selected and an alarm of a selected alarm type has occurred. then the state is set to ‘inactive’ and an alarm is created (no further alarms for this external-alarming identifier are sent to the PIMS application). Identifier of the corresponding external alarming recipient.2 User Manual – Administrator Issue 35 EXTERNAL ALARMING (optional page) Figure 3-10: User data wizard – external alarming (optional page) Here you can specify which alarm types should be covered by external alarming. the Protocol-Independent Messaging System (PIMS) is used.1. A filter form appears. 3. Note: If the external-alarming identifier is unknown to the PIMS application. When you start the User Administration.2.3 User Administration: Groups LIOS operators can be organized into LIOS operator groups. This means that you should check the external-alarming identifier in the PIMS application and select the ‘active’ checkbox again. How to shift items between the lists with the arrow push buttons and with the Ctrl and Shift keys is explained in Section 3. For external alarming. where you can specify criteria for the data to be displayed. Checkbox. Alarm types that are not covered by external alarming. active. see 3. observations and group alarms belong to a LIOS operator group and not to an individual operator. 38/185 A30828-X9410-B082-35-7619 . select the alarm types from the ‘available alarm types’ list on the left and press the ‘>’ button.LIOS V8. Available alarm types. then an alarm message is send to the PIMS application.11. The PIMS application sends this alarm message to a final destination using the external-alarming identifier. Selected alarm types. To specify which alarm types should be covered by external alarming. select the Filter command from the application commands bar. the data displayed reflects the default filter settings.) External alarming identifier. (See [7]. It also has to be administered with the PIMS application. The names are shifted to the ‘selected alarm types’ list. Alarm types that are covered by external alarming.1. If you wish to see another selection of data. if all have been selected previously.3. where you can enter the data for the new operator group to be set up.2) is opened. you must select one or more group records. Copy group. Table columns Group name. Export and Help see ‘general application commands’ in Section 3.2) is opened. where you can modify the group record. Records will only be deleted upon confirmation. The group data form (see 3.LIOS V8. click on the group name (hyperlink) in the first column. All records in the table are selected (checkboxes in the first column) or. and define sorting options.1. Name of operator group.1. Delete group. Selected operator groups are deleted. you must make them members of the new operator group. The group name cannot be changed – the corresponding field is read-only. A record of a deleted group is still kept in the LIOS database. For the commands Refresh. These actions affect only the individual record. If there are LIOS operators with Observation Manager rights. Print. they are unselected. A LIOS operator who has suspended an NE/OS server and not yet resumed it cannot be deleted. where you can specify which operator groups should be displayed.3. Delete operator groups. The group record is deleted. For a detailed view. Remark Actions. Filter. it does not contain all information. If there are LIOS operators with Observation Manager rights. Table The tables provides you with an overview of group information. A30828-X9410-B082-35-7619 39/185 . If you press the Finish button.3. The group name has the string ‘_DEL_’ plus a sequential number appended to it.2 User Manual – Administrator Issue 35 Figure 3-11: User Administration – Groups Application commands New operator group. a new group record with this data is created. Modify group. A filter form (Figure 3-12) is displayed. you must make them members of the new group. It contains the values of the selected group record. The group data form is opened. You can modify these values – at least you have to enter a new group name. You can only delete a group that contains no operators and has no observations assigned to it. Before you can use this command. Select/unselect all. The group data form (see 3. Remark. 40/185 A30828-X9410-B082-35-7619 . Only records are displayed whose names match the string entered. If a field is empty or not selected. functions that are common to most LIOS filter forms) and push buttons see 3.LIOS V8. group filter Group name. Figure 3-12: User Administration. All deleted operator groups are displayed.2 Group data form To open the group data form. 3.e. it has no influence on the filtering process. Not deleted. For a description of general filtering functions (i. A deleted group is marked by ‘_del’ plus a sequential number appended to its name.3.1. ‘Wild cards’ (‘*’ and ‘?’) are accepted. All non-deleted operator groups are displayed. Deleted. ‘Wild cards’ (‘*’ and ‘?’) are accepted.1.1 Group filter By setting filter criteria you can restrict the data to be displayed.3.2 User Manual – Administrator Issue 35 3.3. select ‘new group’. Only records are displayed where a remark added matches the string entered. Show operator groups. ‘modify group’ or ‘copy group’. Members of the group. LIOS operators with Observation Manager rights must be members of all groups. The names are shifted to the ‘selected users’ list. Remark. Selected users. LIOS users who are not members of the group. Name of the LIOS operator group. general information and group members Group name. Members of operator group To assign users to a group. Maximum length: 60 characters. How to shift items between the lists with the arrow push buttons and with the Ctrl and Shift keys is explained in Section 3. If they are not.1. select the users from the ‘available users’ list on the left and press the ‘>’ button.LIOS V8.2. Maximum length: 25 characters. Available users.2 User Manual – Administrator Issue 35 General information Figure 3-13: Group data form. Optional parameter. A30828-X9410-B082-35-7619 41/185 . they will lose their Observation Manager rights.1. Before you can use this command. For the communication with an NE. LID – for receiving tickets and NE alarms). When you start the Host Administration. open the LIOS Servers sub-application. You can delete an NE only if it has no observations on it (this includes LEA data). As a matter of course. MMLCM – for sending MML commands. NEs can also be organized in NE networks. Selected NE records are deleted.4.2 User Manual – Administrator Issue 35 3. Please note: If you have set up an NE.4 Host Administration: NEs The LIOS Host Administration enables you to administer the communication between LIOS servers and network elements (NEs) and the applications running on LIOS servers and NEs. where you can enter the data for the new NE to be set up. To enter the local communication data. NEs Application commands New NE. you must select one or more NE records. where you can specify criteria for the data to be displayed. Check connection. The NE data wizard (see 3. NEs sub-application. select the Filter command from the application commands bar. NE networks are used for the monitoring of foreign directory numbers (FDN) and of mobile subscribers.g. If you wish to see another selection of data. open the NEs sub-application. to enter the remote communication data. In addition date and time of the connection check is displayed as well. The LIOS Host Administration must be executed in accordance with the administration of NEs! From LIOS’s point of view. 42/185 A30828-X9410-B082-35-7619 . In the column “Connection checked” the result of the connection check is indicated by symbols. A filter form appears. you still have to activate it.LIOS V8. The same applies to application-specific address data for each type of application to be used (e. so that LIOS can access it. Delete NEs. Records will only be deleted upon confirmation. This function invokes to check the connection for all NEs selected in the column “NE name”.6) is started. first of all the data of the LIOS server (local) and the data of the NE (remote) must be specified and written to the LIOS database. Figure 3-14: Host Administration. the data displayed reflects the default filter settings. the remote communication data must also be entered locally on the NE (by the NE administrator). The NE data wizard (see 3. Huawei Fixed.4. Application-specific online help is provided. Records are exported as a text file in CSV (comma-separated values) format. Table The table provides you with an overview of NE information. Modify NE. The data is read from the database and the table is updated.2 User Manual – Administrator Issue 35 Communication settings. The NE name cannot be changed – the corresponding field is read-only. State of the connection check. Provider. Date and time of the connection check is displayed. Connection check to the corresponding NE is not supported. Filter. if all have been selected previously. where you can modify the NE record. For a detailed view. with each line representing one application that has been set up for the communication with the NE (see 3. where you can set the timer and counter values controlling the communication and the CMISE protocol used for the connection to NEs. Activate NEs. it does not contain all details.4). Actions. The settings affect the whole LIOS system – it is not possible to make separate settings for individual NEs. Date and time of the connection check is displayed. they are unselected. Name of network element. <date time>. A filter form (Figure 3-17) is displayed.6) is started. Refresh. a cross ( ) means that it has not. and define sorting options. hiE9200 V3. Copy NE. Connection checked.4. Print. Alcatel S12. A Print form is displayed where you can edit printing options and start the printing operation. A check mark ( ) means that the NE has been activated. The Communication Settings form (see 3. You can modify these values – at least you have to enter a new NE name. … (see Annex 2: LIOS – supported network elements). Active. A30828-X9410-B082-35-7619 43/185 .g.4.1) is displayed. Exporting data does not mean removing it from the LIOS database. Software version of the NE: e. After the check is finished the state of the connection check will be changed. The NE data wizard (see 3.6) is started.4. These actions affect only the individual record. All records in the table are selected (checkboxes in the first column) or. Table columns NE name. where you can specify which NEs should be displayed.4. click on the NE name (hyperlink) in the first column. EWSD V17. Select/unselect all. Connection to the NE is OK. Connection check is in proggess (running).g. The following states are possible (not OK. Help. Check not supported. Connection to the NE is not OK. No Connection check performed yet ? Running since <date time>. Export. Network provider responsible for the NE.LIOS V8. When an NE has been set up. It contains the values of the selected NE record. Version. … (see Annex 2: LIOS – supported network elements). it also has to be activated so that LIOS can communicate with it (see 3. Start date and start time of the connection check is displayed. A printer-friendly HTML page reflecting the data currently displayed is generated. Type of the NE: e. NE type. ! Never.2). OK and Check not supported) <date time>. Siemens fixed EWSD. The NE record is deleted.2 User Manual – Administrator Issue 35 Delete NE. MML session timer (min. Only for EWSD V12 and higher.).8). Range: 10 to 600.LIOS V8. Ticket buffer configuration (only for EWSD and hiQ/E9200) Ticket buffer timer (min. Time (in minutes) to elapse before LIOS checks again if a ticket buffer file has been generated on an NE.4. 44/185 A30828-X9410-B082-35-7619 . Options: 5. 10 and 15 minutes. Reset passwords.). and for hiQ/E9200. Waiting time (in minutes) before an MML command is canceled if there is no response from the NE. Select value from the pull-down list. Figure 3-15: Host Administration. 3. The settings affect the whole LIOS system – it is not possible to make separate settings for individual NEs.4.). NEs – Communication Settings MMLCM timers CMISE response timer (min.1 Communication Settings In the Communication Settings form you can set the timer and counter values controlling the communication and the CMISE protocol used for the connection to NEs. A form is displayed where you can adjust the LI passwords in the LIOS system to the passwords set on the NE (see 3. Waiting time (in minutes) for a CMISE response during an MML session. Options: 5. 10 and 15 minutes MML command timer (min.). Range: 1 to 10. Select value from the pull-down list. Waiting time (in minutes) before an unused MML session is canceled. as a rule). A30828-X9410-B082-35-7619 45/185 . ‘Port count’ and ‘Locked’ refer to NEs. If. click on the hyperlink in the ‘Reason’ column.4. NE activation Before you can activate an NE. observation and LEA data associated with the NE cannot be modified in any way.2 User Manual – Administrator Issue 35 3. the administration of observations will no longer be possible – in the entire LIOS system – unless an adequate license has been obtained. You can deactivate an NE only If it is not a member of an NE network. If an NE is in Locked state. for example. NE activation finally makes LIOS communicate with the NE. a message is displayed to this effect. you go beyond the number of ports covered by the LIOS license (‘licensed ports’). adding or removing applications. the NE is marked as active (‘Active’ column with check mark) and in the ‘State’ column it says ‘Failed’.LIOS V8. ─ ─ Table The column headings ‘Active’. If the number of ports used exceeds the number of ports covered by the license. If there are no active observations associated with it and ─ If it has not been suspended (Locked state). you must create an NE record. ‘NE type’.2 NE activation Figure 3-16: Host Administration. You need not deactivate an NE for modifying it – e. whichever applies. ‘NE name’. After this. To view the reason for the failure. while activating an NE. LIOS will still function for a certain time (20 days.g. Inform the license owner that a new license covering all ports used should be obtained. it means that the NE is active and an attempt to deactivate the NE has failed. If. the column headings ‘State’ and ‘Reason’ refer to the last initiated activation or deactivation job. ‘Wild cards’ (‘*’ and ‘?’) are accepted. NE filter NE name. Only records are displayed whose names match the string entered. If you exceed the number of ports. The NE selected in the table is deactivated. Resuming. you can define a filter.3 NE filter If you wish to reduce the number of records to be displayed. the NE’s response is displayed. how many have already been set up (‘used ports’) and how many can still be set up (‘free ports’). Deactivate.3. DB Synchronization or DB Alignment processing is active or that the NE is in ‘DN modified’ state. Help. You can abort a job if there is no response from the NE. 3. The activation/deactivation job is aborted.LIOS V8. functions that are common to most LIOS filter forms) and push buttons see 3. (Also TXT format with tab stops as separators is supported – to be configured in the LIOS properties. Close. If a field is empty or not selected. Push buttons: Refresh. If NE activation fails. The form is closed. For a description of general filtering functions (i.1. Application-specific online help is provided.4 Export According to the result of filter settings all records read from the LIOS database are exported (saved) in CSV (comma-separated values) format. Activate. 3.4.2 User Manual – Administrator Issue 35 If an NE is in Locked state (cross in the Locked column).1. a report icon appears in the ‘Reason’ column. observation and LEA data associated with the NE cannot be modified in any way. a message is displayed to this effect. The NE selected in the table is activated.4.e. which tells you the reason for the failure. The data is read from the database and the table is updated. and the expiration date is stated. Activation and deactivation jobs can be in the following states: ─ ─ ─ ─ Waiting Processing OK Failed The table at the bottom of the window shows you for each NE type how many ports are covered by the LIOS license (‘licensed ports’). Figure 3-17: Host Administration. If you click on the icon.) 46/185 A30828-X9410-B082-35-7619 . Abort. the current LIOS license will expire after 20 days. it has no influence on the filtering process. ‘Locked’ means that Suspending. 4 applications have been set up for an NE.6 12. hiQ/E9200) – see 3.1 8.4 4. a separate NE or LIOS server record is exported.4.LIOS V8.1 2.4.7. Empty fields are rendered through two consecutive commas.4.2 Siemens MSC 1.6. the export file will contain 4 rows for the NE.7. If. Parameters for IP – see 3.3 10.5 Setting up NEs The sequence of forms provided for setting up NEs varies by NE type.6.4.4.6.7 13. hiQ/E9200.4. The following sections show you the sequence for each NE type and offer you cross-references to the relevant information.4.6.6 6. NE user IDs (MMLCM) – see 3. OSI – see 3. for example.4. the field remains empty.10 16.4.2 3. Passwords for EWSD and hiQ/E9200 – FT – see 3.12 7.7. MSC SR11/SR12) – see 3.4 11.6.7.5.7.4.7.3 4. LI Options – see 3.4. Exporting data does not mean removing it from the LIOS database. FT authorization – see 3. General application data – see 3.25 – see 3. LI NE passwords and specific parameters (for EWSD.25– see 3. 3. General – see 3.7. ETSI Network ID – see 3.1 Siemens EWSD and hiQ/E 9200 1.2 9. FT Authorization form – see 3. NE user ID wizard – see 3.4.6.8 14.4. Parameters for X.4.6.5.5 5.4. MMLCM authorization data – see 3. Passwords for EWSD and hiQ/E9200 – EFD – see 3. Authorization data – see 3.6.7.11 3.2 User Manual – Administrator Issue 35 NE and LIOS server data is exported by application – for each application set up for an NE or a LIOS server. ─ Columns are divided by commas. each line in the export file corresponds to one NE network record. You can reduce the amount of records to be exported by applying additional filter criteria.9 15. Export format: ─ When NE or LIOS server data is exported. 3.7. When NE network data is exported.3 3. General – see 3.7. Parameters for IP (EWSD. ETSI Network ID – see 3.6 A30828-X9410-B082-35-7619 47/185 . In the form displayed.4.4.4. Parameters for X.6.4.6.4.6.4.4.4. specify a directory and a file to which the data should be exported.4.1 2.5 5. each line in the export file corresponds to one application record. ─ If a parameter of a record has no value. Applications – see 3. General – see 3.3 3. Parameters for X.5 4.12 5.4.6.7.4.1 2.8 3.10 3.7.6. Parameters for IP (hiQ4200/8000) – see 3.6.7.3 3.1 6.6.5.4.6 Huawei GSM 1. General – see 3.6.6 NE data wizard To start the NE data wizard.25 – see 3.4.5. General application data – see 3.8 12.9 3.2 9. ETSI Network ID – see 3. NE user IDs (MMLCM) – see 3.1 8.6 10.4 Alcatel S12 1. General application data – see 3.1 2. OSI – see 3.4.6.5.7. ETSI Network ID – see 3.5 Huawei C&C08 1.7 3.4.7 11.4.6.4.11 3.12 7.4.4.2 User Manual – Administrator Issue 35 6.4. Authorization data (Nortel/LIM) – see 3.1 2.6.LIOS V8. General – see 3.4.6. ‘modify NE’ or ‘copy NE’.4.4.3 Siemens hiQ 4200 and 8000 1.4.6.4.5 3.7.4.7.7.4. General – see 3.6.4.5.6. select ‘new NE’.1 2. General – see 3. Passwords for Alcatel S12 – MMLCM – see 3. Parameters for IP (Huawei GSM) – see 3.4.6.7.4.1 2.4.3 3. ETSI Network ID – see 3.9 3.4.6.6. Applications – see 3.6.5.5. 48/185 A30828-X9410-B082-35-7619 .8 Nortel (via LIM) 1.4.7 Siemens IN@vantage 1.1 2. Parameters for IP and MCs (Huawei C&C08)– see 3.4. ETSI Network ID – see 3.4. Parameters for IP (Siemens IN@vantage 3.4. MMLCM authorization data – see 3.4. Authorization data – see 3.3 3.4.4.6.4. NE user ID wizard – see 3. Applications – see 3. General – see 3.4.6.4. permitted characters are uppercase characters. Depending on the NE type selected. Mandatory parameter. Select the NE version from the list provided. MML commands then end with Canceled state although it looks as if the NE’s response (MML command output) text was successfully sent to the MML console. The abbreviation for the provider name has been predefined by the national authorities. The NE name must be identical with the NE name used on the NE (for EWSD and hiQ/E9200: as has been specified by the ENTREXCHID command). and the following special characters: + .LIOS V8. Maximum length: 50 characters. modifying and copying an NE record and setting up applications for an NE. It specifies the name of the NE. select the time zone of the NE. NE version. might be confused with ‘LIOS operator’. All characters accepted. NOTICE REGARDING EWSD AND hiQ/E9200: Lower-case letters as parts of MML commands and parameters are not accepted by EWSD and hiQ/E9200. for easier recognition of the NE record.1 General Figure 3-18: NE data wizard – General Provider. It enables LEAs to identify the LI tickets originating from the network of a particular provider.6. Maximum length: 40 characters. LIOS cannot recognize the end of MML command output data. the term ‘network provider’ is used in a LIOS context. This information is needed only for : A30828-X9410-B082-35-7619 49/185 . the only exceptions are passwords.0 and higher versions let you enter several providers for one NE. separate entries through commas. Optional parameter. Depending on the NE version selected. see Annex 2: LIOS – supported network elements. If LIOS and the NE are located in different time zones. Optional parameter. Mandatory parameter. % # *. Mandatory parameter.4. All characters accepted. If the NE name is not specified on the NE.) NE name. It specifies the abbreviated name of the network provider responsible for the NE. digits. further NE-type-specific parameters may have to be entered. Type of the NE: e. Time zone. file names). Select the NE type from the list provided.2 User Manual – Administrator Issue 35 The NE data wizard is provided for adding. It consists of two or three characters and is used as the first part of the LI ticket names (i. LIOS V6. It can contain 1 to 5 characters (maximum length and allowed characters depend on the NE type). 3. NE type. Software version of the NE. where you can enter a more meaningful NE name. Siemens fixed hiQ4200/8000. Nortel fixed (KCC LIM). Huawei fixed. however. Since this. Remark.e.g. Mandatory parameter. Long NE name. further NE-type-specific parameters may have to be entered. Siemens fixed EWSD. (The term that normally conveys this meaning is ‘network operator’ [ETSI]. Alcatel S12. You can select it only if ‘Location dependent interception’ is selected.2 LI Options Figure 3-19: NE data wizard – General For Siemens MSC. Optional parameter (see above). Optional parameter defining whether the ETSI signaling is configured on the NE. Location based interception. If location dependant interception is activated.2 User Manual – Administrator Issue 35 a) the replay protected password feature: The encryption of the passwords can be used for NE communication (EWSD and hiQ/E9200) – see replay-protected password. then a LEA with ‘Location Area Code’. If not checked.7. 3. the ‘Location Area Code is a mandatory parameter for a LEA connected to this NE. ETSI signaling enabled (Subaddressing). At least the same type or both must be set on NE (for LI option ETSIHI: V2-UUS1 or V2-X). Optional parameter defining whether this feature is configured on the NE (LI option LDEPINT) or not.3 ETSI Network ID Figure 3-20: NE data wizard – General 50/185 A30828-X9410-B082-35-7619 .17. On the LIOS side. it is used on the NE for creating observations. you have to specify the LI Options according to the values used on the NE: CUG indexing activated.2. start the MML console and enter the MML command ‘DISPLIOPT’ or ask the administrator of the NE).8. 3. in addition. (LI option ETSIHI: V2SUBADDR or V2-X). b) the time zone conversion for the time stamp in tickets (EWSD and hiQ/E9200): see Section 4. ‘Forwarded to number country code’ and ‘Call Data Notification’ can not be used (See also chapter 3. it will be possible to define the location where each LEA is allowed to intercept a mobile subscriber (by a set of LACs).4. The corresponding LEA must be compatible with ETSI signaling allowed by NE.6.4. SR11 and SR12 only. Optional parameter defining whether this feature is configured on the NE (LI option LBAINT).3). This feature allows creation of an interception for a range of MSISDN numbers by usage of ‘*’ or some first digits and adding a ‘*’ at the end.LIOS V8. If CUG indexing is activated. Location dependant interception.6.2. If CUG indexing is to be used. Note: If checked. SR11 and SR12 only. the CUG’s index must be administered on the NE and the corresponding flag must be set in the LI options on this NE (to find out. Section 3. ETSI signaling enabled (User to User Info). this flag must be set and. the CUGs must be administered with the same index that has been defined on the NE (managing CUGs belongs to the tasks covered by the LEA Administration).4. (LIOS properties HostAdmin. 46 characters max. IP address. (LIOS properties HostAdmin.. The network ID comprises the operator ID and the NE ID. (The term used for ‘network operator’ in a LIOS context is normally ‘network provider’. 50 characters max. X. Mandatory parameter. Number in international format (= country code + LAC + DN). E.z.164.ETSI_AddHeader = 0). Address. A.ETSI_AddHeader = 1) or Hexadecimal digits.25.properties configuration file: Decimal digits. 0. IP. *. DNS. Select a format (E.ETSI_AddHeader = 1) or Hexadecimal digits. The fields in the NE ID section are optional.164.25.2 User Manual – Administrator Issue 35 The ETSI standard on Lawful Interception also regulates in which format data has to be contained in the IRI records. DTE address in international format. Format. IP or DNS) and enter the NE address accordingly. (LIOS properties HostAdmin. Since data is not received from NEs in ETSI format. For Huawei fixed: Maximal length 5 characters.#*+"!$()<>. Network operator of the NE.). decimal numbers separated by dots (. Accepted input: decimal digits (0-9) and the two special characters #.properties configuration file: Decimal digits.ETSI_AddHeader = 0). X. Input depends on the settings in the lios.ETSI_Hexa = 0 and TicketRouter. Operator ID. NE ID. DNS (domain name system) address. data conversion is necessary. Input depends on the settings in the lios.) Maximal length 5 characters. In this form you can specify how network operator ID and NE ID should be rendered in LI tickets.ETSI_Hexa = 0 and TicketRouter.LIOS V8. 46 characters max.. This is not applicable for Siemens IN@vantage and Nortel fixed. also depends on the NE type. Enter the NE ID as it should be output in ETSI-format tickets._/-?:.Z.9 and %.=&.ETSI_Hexa = 1 and TicketRouter. 25 characters max.. ‘Format’ here only refers to the format of the NE ID (‘Address’) – how the NE communicates with LIOS is irrelevant in this context.ETSI_Hexa = 1 and TicketRouter. 50 characters max. Select a format and enter the NE address according to the format selected. (LIOS properties HostAdmin. A30828-X9410-B082-35-7619 51/185 . Which formats are actually available. Accepted input: a. ‘Format’ here only refers to the format of the NE ID (‘Address’) – how the NE communicates with LIOS is irrelevant in this context. ‘|’. ‘\’. The following characters are allowed: uppercase and lowercase characters. ‘\’. Maximum length and characters allowed depend on NE type and version. ‘|’. ‘[‘ and ‘]’. For EWSD. ‘\’. ‘^’. and special characters except ‘~’. digits. To be able to specify or modify the audit password. For EWSD V12 and higher. For EWSD. For EWSD V13A and higher. Maximum length and characters allowed depend on NE type and version. The LI ID password replaces the hard-coded LI password. DISPLIMEAS). for EWSD V12 it has to be from 1 to 15 characters. LI audit password. and for hiQ/E9200. ‘^’. and for hiQ/E9200. For EWSD. To be able to specify or modify the LI group command password. The following characters are allowed: uppercase and lowercase characters.g. and special characters except ‘~’. The following characters are allowed: uppercase and lowercase characters. hiQ/E9200) Figure 3-21: NE data wizard – LI NE passwords and specific parameters (EWSD and hiQ/E9200) LI NE passwords are needed for the administration of the LI function on EWSD and hiQ/E9200 switches. version V13A and higher.4 LI NE passwords and specific parameters (for EWSD. version V13A and higher.4. For EWSD V12 and higher. For controlling most LI functions on the NE (creating/modifying LEAs and observations) the LI group command password is needed. ‘[‘ and ‘]’. version V13A and higher. the length has to be from 8 to 15 characters.2 User Manual – Administrator Issue 35 3. digits. ‘^’. LI audit password. LI ID password. and for hiQ/E9200. It is needed for invoking LI audit functions (e. you must know the LI ID password. the length has to be from 8 to 15 characters.LIOS V8. and special characters except ‘~’. for EWSD V12 it has to be from 1 to 15 characters. 52/185 A30828-X9410-B082-35-7619 . ‘[‘ and ‘]’. ‘|’. and for hiQ/E9200. It is needed for specifying or modifying the LI group command password and the audit password. LI ID password. and for hiQ/E9200. Maximum length and characters allowed depend on the NE type. and for hiQ/E9200. digits. the length has to be from 8 to 15 characters.6. LI group command password. you must know the LI ID password. The NE identification number should be chosen so that it is unique within the network. Only for EWSD V17 and V18 / hiE9200 V3 and V3. Observation parameters. LEA data wizard.25 should be used. they are stored in a ticket buffer file on the NE. Since ticket buffer files are retrieved from the NE via FT (see 3. NE directory number. and for hiQ/E9200. version V13A and higher. if LI tickets have not been sent to LIOS for more than 24 hours because of a broken connection between the NE and LIOS. Do not confuse the NE identification number with the NE ID as part of the ETSI ticket parameters (see 3. it is sent as a CLIP number to the LEA when the call content is sent. ‘Ticket buffer management activated’ refers to the respective NE and not to LIOS as a whole. Value range: 1 to 65535. The LEA can immediately identify the NE that is connecting to the LEA equipment to send call content. it is contained in the LI tickets of the observation and it can be used by LEAs to identify the NE from which the LI tickets have originated. and for hiQ/E9200. Depending on your selection.7). by hiQ/E9200 and by hiQ4200/8000.4. This number is not administered on the NE but it can be specified in the parameters of an LEA. 1 to 18-digit hexadecimal number. Optional parameter for EWSD switches. CUG indexing is a security feature. The NE identification number is not administered on the NE but it can be specified in the parameters of an observation.4. it is used on the NE for creating observations. Prerequsites for ticket buffer management: On the NE: the ticket buffer file (= ‘ticket file’ in EWSD and hiQ/E9200) flag has to be set in the LI options and a file group has to be created for the ticket buffer file. A to F. version V13A and higher. and for hiQ/E9200. The corresponding LI property must be set on the NE. Observation parameters. CUG indexing activated. the ticket buffer file is retrieved by LIOS. also ‘ETSI V2 signaling’ must be selected. for hiQ/E9200. accepted values: 0 to 9. As soon as the connection is repaired. The corresponding LI property must be set on the NE.LIOS V8. LEA data wizard.2 User Manual – Administrator Issue 35 Realized as Power Node. start the MML console and enter the MML command ‘DISPEXDDAT’ or ask the administrator of the NE. NE identification number.1). The NE directory number should be chosen so that it is unique within the network (it should include the local area code). the CUG’s index must be administered on the NE and the corresponding flag must be set in the LI options on this NE (to find out. For EWSD switches.2. * and #. IP is only supported by EWSD V15 and higher.7). If so. Optional parameter for NEs of EWSD.4.4. in addition. Transport system Specify whether IP or X. ETSI V2 allowed. To find out. protected by a file group password. Ticket buffer management activated. the appropriate input fields are provided. general timers and counters can be set (see 3. Selection of the ETSI_V2 signaling schemes is allowed. Optional parameter for NEs of EWSD version V13A and higher. Section 3. Ticket buffer management means that. If CUG indexing is to be used. TR TKUE 40 active. It specifies a virtual NE directory number.6. Select checkbox if the NE is a Power Node. A30828-X9410-B082-35-7619 53/185 . for hiQ4200/8000 IP is mandatory. and for hiQ/E9200. the CUGs must be administered with the same index that has been defined on the NE (managing CUGs belongs to the tasks covered by the LEA Administration). Only for EWSD V17 and V18 / hiE9200 V3 and V3. For EWSD version V15 and higher. This information is necessary for LIOS to determine the RPPW algorithm (see replay-protected password. If CUG indexing is activated. See also ‘NE identification number’ in LEA Administration. See also ‘CLIP DN’ in LEA Administration. this flag must be set and. version V13A and higher. In the LIOS system: the ticket buffer flag must be set and the FT application data must be administered for this NE. start the MML console and enter the MML command ‘DISPLIOPT’ or ask the administrator of the NE).3). If so.2. If you select this check box. The NE uses the German variant of ETSI_V2. On the LIOS side. the fixed length for the IDI field is 15 and the maximum length for the DSP field is 23. the DTE address is automatically copied into the IDI field of the NSAP address. Window size. DSP. Packet size. Flow control negotiation. 44 for ISDN address format or 48 for local X. only decimal digits are allowed. If AFI is set to 44 (NSAP for ISDN).6.4. If LIOS is operated by an organization other than the telephone company who owns the NE. If selected. Maximum input: 14 digits if AFI is set to 36. Domain-specific part. the fixed length for the IDI field is 14 and the maximum length for the DSP field is 24. Maximum packet size at which flow control negotiation will start. Specifies the X. IDI.25 connection.25 connection is built up. Default value is 7.LIOS V8. ‘Reverse charging’ should normally be set to ‘Off’. Reverse charging. the party who has initiated the connection pays for it. flow control negotiation will be performed before an X. the IDI field is ignored and the maximum length for the DSP field is 38. Default value is 1024.25 Make sure that you enter exactly the same parameters that have been specified on the NE. If AFI is set to 36 (NSAP for X.2 User Manual – Administrator Issue 35 3. NSAP (network service access point) fields AFI. Mandatory parameter. If you press the ‘Tab’ key after entering the DTE address. Mandatory parameter. Data terminal equipment address. An incoming connection is recognized by LIOS through the transport selector and the NSAP address. reverse charging can possibly be set to ‘On’. If AFI is set to 48. As a rule. DTE address.25 address for routing. Mandatory parameter Maximum window size at which flow control negotiation will start. Initial domain identifier. This field specifies who pays for an X. Address facility identification (enter 36 for X. otherwise 15 digits. Mandatory parameters.25).5 Parameters for X. 54/185 A30828-X9410-B082-35-7619 .25 address format.25 Figure 3-22: NE data wizard – transport system/X.25). 6. MSC SR11/SR12) Only for EWSD V15 and higher. If the NE uses only one IP address – for communication and for ticket sending – you can leave this field empty.2 User Manual – Administrator Issue 35 3. IP port for the Web service for the NE–LIOS communication.6. and MSC SR11 and higher.4. IP addresses from which tickets will be sent to LIOS.LIOS V8. A30828-X9410-B082-35-7619 55/185 .6 Parameters for IP (EWSD. Allowed incoming IPs. IP address of the NE. separate IP addresses with a comma. hiQ/E9200. Figure 3-23: NE data wizard – transport system / IP IP address. The NE’s IP address used by LIOS for communicating with the NE.7 Parameters for IP (hiQ4200/8000) Figure 3-24: NE data wizard – transport system / IP (hiQ4200/8000) IP address. 3. hiQ/E9200.4. The port number is automatically set to default. IP port. Maximum length: 25 characters.+ . Enter a user-defined user name._ . A..= .104). a.\. Maximum length: 25 characters.? . This is the IP address of the switch’s LI interface...> ._ .z. This is the IP port of the switch’s LI interface..} .% . ! . e. the following information is necessary: 56/185 A30828-X9410-B082-35-7619 . a.= ..: 155.LIOS V8.& ..] .] .0. The following two parameters are necessary for authentication: User name..} .) ..@ .9. Accepted input: 0. Enter a user-defined password. However./ .z.{ .? .^ .12.* . Password.< .{ .% .^ .6.* . . Call content and LI tickets can be sent to a greater number of LEAs. . IP port..[ ..2 User Manual – Administrator Issue 35 3.. Accepted input: 0.> .\.@ ..4.8 Parameters for IP and MCs (Huawei C&C08) Communication parameters Figure 3-25: NE data wizard – Communication properties (Huawei C&C08) All parameters are mandatory: IP address.+ .# .$ .Z.g. each LEA set up in the LIOS system has be associated with one of these MCs. A..$ ..& ..# . Call content routing properties Figure 3-26: NE data wizard – Call content routing properties (Huawei C&C08) Notifications and alarm messages can be sent by a Huawei C&C08 switch to up to three Huawei monitoring centers (MC)..[ . ! .Z. For setting up an MC./ .(.9. The default port is 6900. Accepted input: IP address format (4 times 0–255 separated by dots.) .(.< . It controls whether to perform the consistency judgment between the number sent back by the LEA and the DN of LEA address. The ‘none’ group is always selected (you cannot unselect it). Alarms can be visible in the Alarm browser application. it needs to know the call source of the corresponding monitoring center and the DN of LEA. The Huawei C&C08 switch sends alarms to the LIOS alarm processing server. Call source code is the number 0–65535. To deny access. A30828-X9410-B082-35-7619 57/185 .2 User Manual – Administrator Issue 35 Huawei MC0. In the combo box you can select which LIOS server will receive alarms for the particular MC from the switch. select the corresponding checkbox in the Access Permitted column next to the Operator Group name. Alarm processing server. unselect the checkbox. The field with the IP address is read-only and is automatically filled with the IP address of the chosen alarm server. the switch will consider the monitoring facility illegal and release the call content connection when it detects an inconsistency.LIOS V8. COLP. MC1 and MC2 Call source. If an NE establishes a call content connection to a LEA. Authorization data Figure 3-27: NE data wizard – Authorization data (Huawei C&C08) To give a LIOS operator group access to the NE. it is needed by the LIOS services. LIOS then forwards alarms to the LEA and stores them also in the LIOS system as A-OIX00100 alarms. If you check this field. <. unselect the checkbox. %. _. %... >. =.. . (. #. +. This IP address is used for communication LIOS–NE. -..LIOS V8. ?. . *. Password. Accepted input: 1–65535 The following three parameters (Huawei NE ID. :. Enter a user-defined password. it is needed by the LIOS services. 3. =. $. . User name and Password) are necessary for authentication: Huawei NE ID.9.2 User Manual – Administrator Issue 35 3.. To deny access..9.. Maximum length: 40 decimal digits. Authorization data To give a LIOS operator group access to the NE... &.z. Accepted input: 0. *.6.6. ).4. &.. <. A. ).Z. ?.10 Parameters for IP (Siemens IN@vantage) 58/185 A30828-X9410-B082-35-7619 . User name. /.9. ".. -. Maximum length: 32 characters. /. This port number is used for the communication LIOS–NE. Maximum length: 32 characters. ". a. Enter a user-defined Huawei NE ID. (.9 Parameters for IP (Huawei GSM) Figure 3-28: NE data wizard – transport system / IP (Huawei GSM) Transport system The following parameters are mandatory: IP address. +.z.Z. :. !. $. a. .. >. Enter a user-defined user name. Accepted input: 0. The ‘none’ group is always selected (you cannot unselect it). _...4. select the corresponding checkbox in the Access permitted column next to the Operator group. !. #. A. Accepted input: 0.. IP port. IP port. 0.9. Accepted input: 30–3600.12. Accepted input: 1–65535. unselect the checkbox. Transaction timer (sec).Z.. /_. IP addresses used for NE–LIOS communication. Accepted input: a. Allowed incomming IPs.. HTTP context string. Server path.: 155. separate IP addresses with a comma. To deny access. In the URL this string appears after the IP address and IP port.0..g. which will be used to create an URL for communication with the Siemens IN@vantage switch.z. select the corresponding checkbox in the Access permitted column next to the Operator group. Maximum length: 256 characters..LIOS V8. A30828-X9410-B082-35-7619 59/185 .2 User Manual – Administrator Issue 35 Figure 3-29: NE data wizard – transport system / Siemens IN@vantage Communication parameters All parameters are mandatory: IP address. Authorization data To give a LIOS operator group access to the NE. IP address used for LIOS–NE communication. Accepted input: IP address format (4 times 0–255 separated by dots. A.. Port number used for LIOS–NE communication. Maximum time – in seconds – that LIOS will wait for the response to a command sent to the switch.104). If the NE uses only one IP address – for LIOS–NE and NE–LIOS communication – you can leave this field empty. e. The selected application record is deleted. To delete an application. press the Modify button. it is needed by the LIOS services. To modify application data. It is needed by the LIOS services. To take away access. The ‘none’ group is always selected (you cannot unselect it).2 User Manual – Administrator Issue 35 The ‘none’ group is always selected (you cannot unselect it).4.11 Authorization data (Nortel/LIM) To give a LIOS operator group access to the NE. select the application and press the Delete button.6. Data that was entered for setting up other applications and that is also needed for the new application is automatically taken over to the new form. 3. where you can enter the data for a new application. Figure 3-30: NE data wizard – Authorization Data (Nortel via LIM) 3.4.12 Applications Figure 3-31: NE data wizard – Applications To set up an application for the communication with the NE.LIOS V8. The Application data wizard is started. to be configured for an NE to enable observation handling and the input of MML commands from the MML console. 60/185 A30828-X9410-B082-35-7619 . LIOS supports the following applications: MMLCM.7) is started. select an application (radio button) and press the New button.4. unselect the checkbox. where you can modify data for the selected application. select the corresponding checkbox in the ‘access permitted’ column next to the operator group name. MML Command Management. The Application data wizard (see 3.6. g. It identifies the port number of the Symicron X. Lawful Interception Data. If LIOS is running in Admin mode. EFD is used only for sending LI NE alarms. e. ‘Primary LIOS server’ indicates the LIOS server that is used for sending MML commands to an NE if the system is working correctly. Regarding FT. Mandatory parameter (only for MMLCM and EFD). LIOS servers can receive LI tickets and LI NE alarms. The secondary LIOS server refers to the pair LIOS server in a redundant system.g. Event-forwarding discriminator. switching to the secondary LIOS server has to be done by hand.4. LID is used only for the sending of LI-NE alarms. Once EFDs have been defined.7. to be configured for an NE to enable the NE to send LI tickets and LI-NE alarms to LIOS. Secondary LIOS server. Primary LIOS server.25 link on the LIOS server that should be used for outgoing connections (default is port 0).1 General application data Figure 3-32: Application data wizard – general data Specify the application name and the primary and secondary LIOS servers for this application. because of a broken connection. to be configured for an NE (EWSD. to be configured for an NE to enable LIOS administrators to manage EFDs on the NE. Application.4. In addition. Mandatory parameter. It identifies the port number of the Symicron X. Only for Siemens EWSD and hiQ/E9200. the secondary LIOS server can take over.LIOS V8. EFDs are used to determine the primary and the secondary LIOS server. Port number for primary LIOS server.7 Application data wizard 3. FT) which you have selected on the previous page. Port number for secondary LIOS server. This happens automatically as far as MMLCM and EFD are concerned. A30828-X9410-B082-35-7619 61/185 . NE connection is broken).2 User Manual – Administrator Issue 35 LID. EFD. and hiQ/E9200) to enable LIOS to retrieve the data stored in LI ticket buffer files from the NE. If LIOS is running in Admin mode. version V13A and higher. EFD. Mandatory parameter (only for MMLCM and EFD).25 link on the LIOS server that should be used for outgoing connections (default is port 0). LID. If the primary LIOS server is not working correctly (e. 3. you can specify a port number of the Symicron X. This field is automatically filled in when the data of the primary LIOS server is entered.25 links on the LIOS server that should be used for outgoing connections. Application type (MMLCM. File Transfer. FT. Ticket buffer files contain LI tickets that could not be sent to LIOS through the LID application. Presentation selector.LIOS V8. Input format for Hexadecimal: 0-9. incl. A-F. Input format for ASCII: all printable characters. The application entity title uniquely identifies an application (MMLCM.7. For the whole application entity title (system title + APQ + AEQ): 10 components max. It identifies the presentation layer (OSI layer 6). LID. Select ASCII mode or Hexadecimal mode. space. Make sure that you enter exactly the same parameters that have been specified on the NE. It identifies the session layer (OSI layer 5). except blanks. ASCII (for FT only): all characters. EFD and LID) or via FTAM for the FT application: Selector editing. maximum length: 8 characters. 4 digits max. 1. Accepted input: Hexadecimal: maximum length: 4 digits. Accepted input: Hexadecimal: maximum length: 4 digits. EFD or FT) within the system.). You can also switch to the other editing mode if the selector fields have already been filled in – the character strings are instantly converted. presentation selector and application entity title. Accepted input: Hexadecimal: maximum length: 4 digits.4. except blanks. The following selector addresses are mandatory OSI layer parameters for the NE communication via Q3 (for MMLCM.2 User Manual – Administrator Issue 35 3. switching between editing modes may not work. containing system title and APQ – application program qualifier. value range: 0 to 9999999. 2. Maximum lengths: 30 digits.). (If non-printing characters are involved. except blanks. Application entity title. for FT application 16 digits. 62/185 A30828-X9410-B082-35-7619 . optional. decimal number. for 2nd component: 0 to 39. Mandatory parameter. for FT application 16 digits. maximum length: 8 characters. maximum length: 16 characters. ASCII (for FT only): all characters. 4 digits max. Session selector. ASCII (for FT only): all characters. Mandatory parameter. 2 components min. for FT application 32 digits. 10 components max. Mandatory parameter for the application layer (OSI layer 7). a-f. Mandatory parameter. It consists of the application process title (mandatory.) Transport selector. It identifies the transport layer (OSI layer 4). For FT application only.) and the AEQ (application entity qualifier. The system title contains an object identifier consisting of decimal numbers separated by dots (. session selector. Value range: for 1st component: 0.2 OSI parameter Figure 3-33: Application data wizard – OSI Enter the OSI parameters for the application with relevance to the NE: transport selector. with the following characters allowed: uppercase and lowercase characters.4.3 Passwords for EWSD and hiQ/E9200 – FT Figure 3-34: Application data wizard – file group password File group password / password confirmation.4 Passwords for EWSD and hiQ/E9200 – EFD Figure 3-35: Application data wizard – EFD NE password EFD NE password / password confirmation. The EFD application sends in a connection request only a password to the specified NE. The NE password has to contain at least one letter. one digit and one special character. a file group must be created for the LI ticket buffer file. _ / . and for hiQ/E9200. and the special characters % .LIOS V8. version V13A and higher. If you are setting up EFD. digits. If selected. the password is encrypted to prevent replay. For ticket buffer management to work.? : . you have to specify an NE user name and a password only for LIOS group ‘none’. and for hiQ/E9200. version V13A and higher.6). one digit and one special character. and for hiQ/E9200. The file group password protects the file group. Maximum length and characters allowed depend on the NE type.4.7. the length has to be from 4 to 8 characters. Only for EWSD V15 and higher.2 User Manual – Administrator Issue 35 3. 3.7. the NE user ID for this password on EWSD and hiQ/E9200 switches is normally ‘MFKONTES’ (8 characters) or ‘MFKON’ (5 characters) depending on the length of NE user names administered on the NE. Maximum length and characters allowed depend on the NE type. For EWSD.4. The file group password must be the same for all ticket buffer file groups administered in the LIOS system. For the encryption. = &. the length has to be from 4 to 14 characters. _ / . A30828-X9410-B082-35-7619 63/185 . specifying the password to protect the EFD application.? : . and the special characters % . The NE password has to contain at least one letter. with the following characters allowed: uppercase and lowercase characters. Only for EWSD and hiQ/E9200. A mandatory parameter. digits. For EWSD. # * + " ! $ ( ) < > . # * + " ! $ ( ) < > . Replay-protected password enabled. ‘Replay-protected password’ only works if the time in the LIOS system and on the NE is precisely the same – this means synchronization through a radio clock or an NTP (Network Time Protocol) server is necessary. time information is used (see ‘time zone’ in Section 3. = &. Mandatory parameter. and the special characters % . provide an NE user ID and an NE password and establish a logical connection between the LIOS operator group name and the NE user ID. A check mark in the Cyclic column means that cyclic password changing is enabled. The ‘NE user IDs’ form contains an entry for each NE user managed to access the NE.4.7.LIOS V8. 64/185 A30828-X9410-B082-35-7619 . Pressing New or Modify opens the ‘NE user ID’ wizard. to allow a LIOS operator group to handle observations on the NE. an X means that it is disabled.6 NE user IDs (MMLCM) Figure 3-37: Application data wizard – NE user IDs (MMLCM) In this step you can administer the NE user authorization (i. _ / . which helps you to manage NE passwords and cyclic password changing.4.2 User Manual – Administrator Issue 35 3. where at least one digit must be present. This field can have up to 8 characters. Access password is used as an additional authorization to access an Alcatel S12 switch through MMLCM. Thus.5 Passwords for Alcatel S12 – MMLCM Figure 3-36: Application data wizard – access password (S12) Access password. # * + " ! $ ( ) < > . = &. NE user ID and password) for the communication with the NE through the MMLCM application.e.7. 3.? : . The allowed characters are: uppercase and lowercase characters. NE user ID and password can be assigned to one or more LIOS operator groups. digits. select this checkbox. an NE user ID and a password are required. Mandatory parameter. above. For EWSD. Replay-protected password enabled. the length has to be from 4 to 24 characters. and MSC. A30828-X9410-B082-35-7619 65/185 . There is no special constraint on the content of the NE password. # * + ‘ " ! $ ( ) < > . = &. # * + ‘ " ! $ ( ) < > . with the following characters allowed: uppercase and lowercase characters. = &. and the special characters % . MSC or S12 switch. digits.? : .2 User Manual – Administrator Issue 35 3. To enable cyclic password change. hiQ/E9200. finally press OK.? : .4. Cyclic password change enabled. for hiQ/E9200. For Alcatel S12. Maximum length and characters allowed depend on the NE type. All NE user IDs managed on an NE must have the same length. edit the password in both fields. finally press OK.LIOS V8. version V13A and higher. with the following characters allowed: uppercase and lowercase characters. The NE password has to contain at least one letter. _ / . ! All NE user IDs must also be configured by the NE administrator on the NE. Maximum length and characters allowed depend on the NE type. the length has to be from 4 to 8 characters. See replay-protected password enabled. for hiQ/E9200. How to modify a password: select the option button in the Order column. and the special characters % . Password / Confirm. the length has to be from 6 to 12 characters. How to add a password: enter a password. Cyclic password changing To log in to an EWSD. It specifies the ID under which the selected LIOS operator group will communicate with the NE. digits. with the following characters allowed: uppercase characters. for MSC and for Alcatel S12.7 NE user ID wizard Figure 3-38: Application data wizard – NE user ID NE user ID. Password for the NE user ID. according to the settings of the NE. then enter the password and the password options. % # *. The password has to be changed after some time. First enter an NE user ID (account). and the special characters + . digits. For EWSD. one digit and one special character. the password is automatically copied to the Password and Confirm fields. repeat it and press the Add button.7. _ / . version V13A and higher. Modify. 66/185 A30828-X9410-B082-35-7619 . When LIOS receives a ‘password expired’ answer when accessing the NE. where you can relate NE user IDs to LIOS operator groups. The selected password will be the valid password. The ‘Show passwords’ button enables you to view the passwords.2 User Manual – Administrator Issue 35 Cyclic password changing lets LIOS do the password changing for you. when it has arrived at the last password in the list. Passwords are displayed in clear text. Pressing Create or Modify opens the ‘MMLCM authorization data’ form. For each NE enter the initial password (to be obtained from the NE administrator) and at least three passwords of your own choice.4. Press this button before you make any modifications and hide passwords after that again. Cancel. OK. A checkmark in the Initial column identifies the password that was first provided by the NE administrator. Your input is accepted and the form is closed. The selected password will be marked ‘initial’. Select the ‘Cyclic password change enabled’ checkbox. Remove. it starts again with the first one (leaving out the initial password).LIOS V8. Push buttons: Add.8 Authorization data Figure 3-39: Application data wizard – authorization data The ‘authorization data’ form serves to relate LIOS operator groups to the NE user IDs you have set up in the ‘NE user ID’ form. The selected password is removed. Show passwords/Hide passwords (toggle button). With the push button functions you can manage passwords. 3. The password entered in the Password field is added to the table.7. As a rule. The password entered in the Password field replaces the selected password. the initial password will be the password originally provided by the NE administrator. Set valid. The initial password will be used for cyclic password changing. Help. A check mark in the Valid column identifies the password that is currently valid on the NE. Online help is provided. Your input is discarded and the form is closed. Set initial. it automatically replaces the password with the next password in the list. The Secondary NE user ID is normally used for the communication with the NE from the secondary LIOS server. LIOS uses the group ‘none’ to get access to the NE. regardless of the group the LIOS operator belongs to. Since LIOS normally uses two LIOS servers.7. NE user ID. which identifies the LIOS operator group. you can define two NE user IDs for each LIOS operator group – this will enable both LIOS servers to send MML commands simultaneously. Each LIOS user can send individual MML commands to the NE. Optional parameter. In this context. A30828-X9410-B082-35-7619 67/185 . regardless of the actual number of LIOS servers in the system. you can leave this field empty.4. ‘Single’ type means that only one NE user ID has been specified for each LIOS operator group. you only need one NE user ID for each LIOS operator group.9 MMLCM authorization data Figure 3-40: Application data wizard – MMLCM authorization data In this form you can establish a logical connection between NE user IDs and LIOS operator groups. Secondary NE user ID. which enhances system speed. The NE user ID is normally used for the communication with the NE from the primary LIOS server. The Secondary NE user ID must be different from the NE user ID.LIOS V8. you can define also a Secondary NE user ID for each LIOS operator group – this will enable both LIOS servers to send MML commands simultaneously. 3. If a LIOS operator group has active observations on an NE. Mandatory parameter. If you are working with a single LIOS system (one LIOS server). If you are working with a single LIOS system. ‘Type’ here refers to the communication with the NE by means of MML.2 User Manual – Administrator Issue 35 Since LIOS normally uses two LIOS servers. which enhances system speed. you cannot remove the connection of the LIOS operator group with the NE user ID. Operator group. It is recommended to use different NE user IDs for different LIOS operator groups. ‘Parallel’ type means that two NE user IDs have been specified for each LIOS operator group. Mandatory parameter. For this purpose the MML console is provided. This means that you have to add an NE user ID and an NE password also for the LIOS group ‘none’. 4.4. the ‘FT authorization’ form (Figure 3-42) is displayed. For EWSD. where you can enter LIOS operator group name.2 User Manual – Administrator Issue 35 3. he will get the message ‘Authorization failure – contact your system administrator’ in the ‘MML output’ form.11 FT Authorization form Figure 3-42: Application data wizard – FT Authorization form Operator group. Thus. NE user ID and NE password. the selected authorization record is deleted. NE user ID. NE user ID and password can be assigned to one or more LIOS operator groups. Specify an NE user ID and a password only for LIOS group ‘none’. set up the group under an NE user ID. which identifies the LIOS operator group. Mandatory parameter.e.7. % # * ! 68/185 All NE user IDs must also be configured by the NE administrator on the NE.LIOS V8. 3. You have to specify an NE user name and a password only for LIOS group ‘none’. to allow a LIOS operator group to access the NE. If you press New or Modify. version V13A and higher. If a LIOS user tries to connect to an NE where authorization data for his group is not administered. with the following characters allowed: uppercase characters. If you press Delete.7. specifying the NE user ID that is used for the selected LIOS operator group for communication with an NE. the length has to be from 4 to 8 characters. NE user ID and password) for FT on the NE.10 FT authorization Figure 3-41: Application data wizard – FT authorization In this step you can administer the NE user authorization (i. Mandatory parameter. Maximum length and characters allowed depend on the NE type. and the special characters + . and for hiQ/E9200. A30828-X9410-B082-35-7619 . digits. LIOS V8.2 User Manual – Administrator Issue 35 Replay-protected password enabled. See 'replay-protected password enabled' in the Passwords section. NE password / Confirm NE password. Mandatory parameter, specifying the password for the NE user ID. Maximum length and characters allowed depend on the NE type. For EWSD, version V13A and higher, and for hiQ/E9200, the length has to be from 4 to 24 characters, with the following characters allowed: uppercase and lowercase characters, digits, and the special characters % . # * + ‘ " ! $ ( ) < > , _ / - ? : ; = &. The NE password has to contain at least one letter, one digit and one special character. 3.4.8 Reset passwords Only for EWSD V12 and higher, and for hiQ/E9200. You should not normally need this command. If the LI database of the NE has got lost (NE in ‘LI DB lost’ state), a LIOS operator with appropriate rights can invoke the ‘DB alignment’ operation, which will automatically reset the LI-specific passwords (LI group command password, ID password and Audit password) on the NE and copy all relevant LI data (observation and LEA data) from the LIOS database to the LI database of the NE. If all has successfully finished, the state of the NE is automatically reset to Ready and the NE’s LI database is again synchronous with the LIOS database. However, if the automatic reset of the LI passwords on the NE has failed or the NE administrator has modified an LI password in the meantime – which he should not do – the ‘DB alignment’ operation does not work. In this case you must be informed by the LIOS operator. Reset passwords enables you to reset the LI passwords administered in the LIOS system to the LI passwords administered on the NE. When you choose Reset passwords, a form is displayed where you can modify the LI passwords. Ask the NE administrator which passwords he has modified. Enter the modified password in the respective input fields and leave the input fields for the other passwords untouched. Figure 3-43: Reset passwords – ‘NE passwords’ form Finally press OK. The passwords will be written to the LIOS database and the NE state will be changed from ‘LI DB lost’ to ‘Suspended’. Inform the LIOS operator that he should now effect ‘Resume’ (instead of ‘DB alignment’); ‘Resume’ will recreate the lost LI database on the NE. Reset passwords is only enabled if the NE is in ‘LI DB lost’ state. A30828-X9410-B082-35-7619 69/185 LIOS V8.2 User Manual – Administrator Issue 35 3.5 Host Administration: OS Servers In a heterogeneous network, LIOS can be set up as an umbrella system to cover also foreign interception operation systems (OS), e.g. LIM (Lawful Interception Manager) by KCC for accessing Nortel fixednetwork switches and Utimaco IMS (Interception Management System) for accessing Siemens GSM, GPRS, HLR and HLRi switches. Host Administration/OS Servers allows you to enter the OS’s communication parameters for the communication between LIOS servers and the OS servers. (To enter LIOS’s communication parameters, open the LIOS Servers sub-application; as a matter of course, the remote communication data must also be entered locally on the OS server by the respective system administrator). For foreign OS Servers must be performed an OS Server administration as well as an NE administration. Figure 3-44: Host Administration, OS Servers Application commands New OS server. The OS Server data wizard (see 3.5.1) is started, where you can enter the data for the OS server to be set up. Delete OS servers. Selected OS server records are deleted. Before you can use this command, you must select one or more OS server records. Records will only be deleted upon confirmation. An OS server record can only be deleted if it has no NEs associated. Check connection. This function invokes to check the connection for all NE’s selected in the column “NE name”. In the column “Connection checked” the result of the connection check is indicated by symbols. In addition date and time of the connection check is displayed as well. Activate/Deactivate OS servers. OS servers of certain types have to be activated so that LIOS can create observations on them (see 3.5.2.3). Filter. A filter form is displayed, where you can specify which OS servers should be displayed, and define sorting options. Select/unselect all. All records in the table are selected (checkboxes in the first column) or, if all have been selected previously, they are unselected. For the commands Refresh, Print, Export and Help see ‘general application commands’ in Section 3.1.1.3. 70/185 A30828-X9410-B082-35-7619 LIOS V8.2 User Manual – Administrator Issue 35 Table The table provides you with an overview of OS information; it does not contain all details. For a detailed view, click on the OS server name (hyperlink) in the first column. Table columns OS server name. Name of the server of the operation system which is to communicate with LIOS. Active. OS server activation information. OS server activated. OS server not activated. OS server need not to be activated. OS server type. Type of operation system. OS server version. Version of operation system. Connection checked. State of the connection check. ! Never. No Connection check performed yet ? Running since <date time>. Connection check is in proggess (running). Start date and start time of the connection check is displayed. After the check is finished the state of the connection check will be changed. The following states are possible (not OK, OK and Check not supported) <date time>. Connection to the NE is not OK. Date and time of the connection check is displayed. <date time>. Connection to the NE is OK. Date and time of the connection check is displayed. Check not supported. Connection check to the corresponding NE is not supported. Actions. These actions affect only the individual record. The scope of actions available depends on the OS server type you are working with. Modify OS server. The OS Server data wizard (see 3.5.1) is started, where you can modify the OS server record. Copy OS server. The OS Server data wizard is started. It contains the values of the selected OS server record. You can modify these values – at least you have to enter a new OS server name. Delete OS server. The OS server record is deleted. Before the record is actually deleted, you will be prompted for confirmation. 3.5.1 Setting up OS servers The sequence of forms provided for setting up OS servers varies by OS server type. The following sections show you the sequence for each type and offer you cross references to the relevant information. 3.5.1.1 KCC LIM 3. General – see 3.5.2 4. Communications parameters for LIM servers – see 3.5.2.1 3.5.1.2 Mediation Device (Siemens IP) 1. General – see 3.5.2 2. Parameters for Mediation Device (Siemens IP) – see 3.5.2.2 A30828-X9410-B082-35-7619 71/185 2 User Manual – Administrator Issue 35 3. MMLCM authorization data – see 3.6 72/185 A30828-X9410-B082-35-7619 .3 3.5.5.5 5.2 2.5.4 4. General – see 3.2.LIOS V8. OS server user IDs – see 3.5.5. Transport system and OS server user IDs (IMS) – see 3.3 Utimaco IMS 1.2.2.1.5. IMS authorization data – see 3.2. Optional parameter.2. Maximum length: 256 characters. Maximum length: 50 characters. Port. OS server version. Name of the server of the operation system which is to communicate with LIOS. Path of the OS Web server where the OS awaits LIOS HTTP requests.. IP address of the OS server. All characters accepted. A30828-X9410-B082-35-7619 73/185 . Remark. * + % #. (Not for all OS types.9. A.LIOS V8. Type of operation system. Server path. 3.1 Communications parameters for LIM servers Figure 3-46: OS Server data wizard – Communication Parameters (LIM) IP address. Provider.5.2 OS Server data wizard The OS Server data wizard is provided for creating and for modifying an OS server record.) Network provider responsible for the OS server.. Figure 3-45: OS Server data wizard – General OS server name. Layout and content of the following form depend on the OS server type selected.2 User Manual – Administrator Issue 35 3. OS server type. Secondary IP address. IP address of secondary OS server..5.Z and . Optional. Accepted input: 0. Maximum length: 5 characters. Version of operation system. IP port number of the OS Web server. 9.. It specifies the ID under which the selected LIOS operator group will communicate with the mediation device (= NE).. Maximum length: 32 characters. Minimum length: 1 character.z. 3. Accepted input: IP address format (4 times 0–255 separated by dots. Accepted input: 0-36000. Once the maximum time has been reached and no response has been received. e. _ -.. IP address of the Mediation Device (MD) . Enter a user-defined password. transport system .used for LIOS–MD communication..2 User Manual – Administrator Issue 35 Accepted input: a. 0.2 Parameters for Mediation Device (Siemens IP) Figure 3-47: NE data wizard..Z..LIOS V8. Minimum length: 1 chaacters. Maximum time – in seconds – that LIOS will wait for a response from the OS server. a.104).? : . # * + " ! $ ( ) < > . _ / .5..e. 74/185 A30828-X9410-B082-35-7619 . Accepted input: 0.Mediation Device (Siemens IP) Transport system All parameters are mandatory: IP address..9 and \ / .. Maximum length: 20 characters. Accepted input: 1–65535 OS server user IDs.: 155. IP port..12. Transaction timer. Password. Port number used for LIOS–MD communication. no response is obtainable).0.2. A.z. the command sent will be treated as ‘undefined’ (i. = &.Z and % . A.g. Port number of the primary OS server to open a RAI connection. select the corresponding checkbox in the ‘Access permitted’ column next to the operator group name. Confirm. A30828-X9410-B082-35-7619 75/185 ..z.4 OS server user IDs To add an OS server user ID. _ / . # * + " ! $ ( ) < > . Backup IP port.9.? : . To delete an OS server user ID. Retype password. unselect the checkbox..2. select an OS server user ID and press Modify: the OS server user ID form is displayed. press New. IP address of the primary OS server (IMS) to open a RAI connection. It is needed by the LIOS services. Port number of the backup IMS server (secondary OS server) to open a RAI connection.2 User Manual – Administrator Issue 35 Maximum length: 20 characters.LIOS V8. A. to modify an OS server user ID.5. Accepted input: 0.2. 3.. To take away access.3 Transport system and OS server user IDs (IMS) Figure 3-48: OS server data wizard – Transport system and OS server user IDs (IMS) Transport system IP address.Z and % . 3. IP port. = &. The ‘none’ group is always selected (you cannot unselect it). press Delete. Access to mediation device To give a LIOS operator group access to the mediation device. IP address of the backup IMS server (secondary OS server) to open a RAI connection..5. a.. Backup IP address. – The password must not contain trivial sequences (e..LIOS V8. % # *. it automatically replaces the password with the next 76/185 A30828-X9410-B082-35-7619 .g. Password for the OS server user ID. the length has to be from 1 to 20 characters. It specifies the ID under which the selected LIOS operator group will communicate with the OS server. and the special characters + . digits. dr5). Cyclic password change enabled. and the special characters % . # * + ‘ " ! $ ( ) < > . For Utimaco IMS only one OS server user ID is allowed. How to add a password: enter a password. For Utimaco IMS. Mandatory parameter. The password has to be changed after some time. The OS server password has to contain at least two letters and two digits. version RAI 2. version RAI 2. an OS server user ID and a password are required.2 User Manual – Administrator Issue 35 Figure 3-49: OS server data wizard – OS server user IDs (IMS) OS server user ID.0. Please note: LIOS does not check whether your input conforms to these two rules. repeat it and press the Add button. Maximum length and characters allowed depend on the OS server type. finally press OK. however. according to the settings of the OS server. _ / . poi. with the following characters allowed: uppercase characters.0. the password is automatically copied to the Password and Confirm fields. select this checkbox. then enter the password and the password options. First enter an OS server user ID (account). Cyclic password changing lets LIOS do the password changing for you. finally press OK. – OS server user name and password must not have any common substring of length greater than 1. with the following characters allowed: uppercase and lowercase characters. When LIOS receives a ‘password expired’ answer when accessing the OS server. edc. For Utimaco IMS. does and it rejects all non-conforming input. To enable cyclic password change. How to modify a password: select the option button in the Order column. Select the ‘Cyclic password change enabled’ checkbox. Cyclic password changing To log in to an OS server. = &. Maximum length and characters allowed depend on the OS server type. Password / Confirm. edit the password in both fields. ATTENTION! The OS server user ID must also be configured by the OS server administrator on the OS server. For each OS server enter the initial password (to be obtained from the OS server administrator) and at least three passwords of your own choice. Utimaco IMS. digits. the length has to be from 8 to 15 characters.? : . which enhances system speed. Your input is accepted and the form is closed. it starts again with the first one (leaving out the initial password).2. Help.LIOS V8.2 User Manual – Administrator Issue 35 password in the list.5. The password entered in the Password field replaces the selected password. OK. Since LIOS normally uses two LIOS servers. Modify. Show passwords/Hide passwords (toggle button). The selected password will be the valid password. Push buttons: Add. Online help is provided – this help screen is displayed. A30828-X9410-B082-35-7619 77/185 . when it has arrived at the last password in the list. The initial password will be used for cyclic password changing. The selected password is removed. where you can relate OS server user IDs to LIOS operator groups. With the push button functions you can manage passwords. the initial password will be the password originally provided by the OS server administrator. Remove. Set valid. you can define two OS server user IDs for each LIOS operator group – this will enable both LIOS servers to send MML commands simultaneously. Pressing Create or Modify displays the MMLCM authorization data form (Figure 3-51). Set initial. The password entered in the Password field is added to the table. A check-mark in the Initial column identifies the password that was first provided by the OS server administrator. A check-mark in the Valid column identifies the password that is currently valid on the OS server. Press this button before you make any modifications and hide passwords after that again. The selected password will be marked ‘initial’. It is recommended to use different OS server user IDs for each LIOS operator group (if the OS server allows more than one OS server user ID). Your input is discarded and the form is closed. Cancel. The ‘Show passwords’ button enables you to view the passwords. 3. As a rule.5 MMLCM authorization data Figure 3-50: OS server data wizard – MMLCM authorization data (IMS) This page serves to relate LIOS operator groups to the OS server user ID you have set up in the ‘OS server user ID’ form. Passwords are displayed in clear text. The OS server user ID is normally used for the communication with the OS server from the primary LIOS server. For this purpose the MML console is provided. Each LIOS user can send individual MML commands to the OS server.6 IMS authorization data Figure 3-52: OS server data wizard – IMS authorization data (IMS) In the Utimaco IMS system all IMS LEA names defined must be assigned to the OS server user ID. regardless of the group the LIOS operator belongs to. which identifies the LIOS operator group. Mandatory parameter. regardless of the actual number of LIOS servers in the system. LIOS uses the group ‘none’ to get access to the OS server.2. This means that you have to add an OS server user ID and an OS server password also for the LIOS group ‘none’. 78/185 A30828-X9410-B082-35-7619 . ‘Parallel’ type means that two OS server user IDs have been specified for each LIOS operator group. In this context. 3. you cannot remove the connection of the LIOS operator group with the OS server user ID. OS server user ID. ‘Single’ type means that only one OS server user ID has been specified for each LIOS operator group. Figure 3-51: OS server data wizard – MMLCM authorization data form (IMS) In this form you can establish a logical connection between OS server user IDs and LIOS operator groups. If you are working with a single LIOS system (one LIOS server). you only need one OS server user ID for each LIOS operator group.2 User Manual – Administrator Issue 35 ‘Type’ here refers to the communication with the OS server by means of MML.LIOS V8.5. LIOS operator group. Mandatory parameter. If a LIOS operator group has active observations on an OS server. Inform the license owner that a new license covering all ports used should be obtained. ‘OS server type’. click on the hyperlink in the ‘Reason’ column. If an OS server is in Locked state (check mark in the Locked column) an observation can not be modified and no observation can be created. double quote (“). the column headings ‘State’ and ‘Reason’ refer to the last initiated activation or deactivation job. You need not deactivate an OS server for modifying it. After this.5. If the number of ports used exceeds the number of ports covered by the license. the administration of observations will no longer be possible – in the entire LIOS system – unless an adequate license has been obtained. as a rule). Table The column headings ‘Active’.3 Activate/Deactivate OS servers Figure 3-53: Activation/Deactivate OS servers Before you can activate an OS server. 3. a message is displayed to this effect. To view the reason for the failure. whichever applies. enter the name in the input field (1–15 characters. the OS server is marked as active (‘Active’ column with check mark) and in the ‘State’ column it says ‘Failed’. how many have already been set up (‘used ports’) and how many can A30828-X9410-B082-35-7619 79/185 . ‘OS server name’. To modify an IMS LEA name.2 User Manual – Administrator Issue 35 To assign a new IMS LEA name.). Activation and deactivation jobs can be in the following states: ─ ─ ─ ─ Waiting Processing OK Failed The table at the bottom of the window shows you for each OS server type how many ports are covered by the LIOS license (‘licensed ports’). you must create an OS server record. If. You can deactivate an OS server only if there are no NEs and no observations associated with it. To delete an IMS LEA name. while activating an OS server. You can delete an IMS LEA name only if there are no observations on the OS server which refer to it. LIOS will still function for a certain time (20 days. tab stop and blank) and press Define: the name is copied to the list below. ‘Port count’ and ‘Locked’ refer to OS servers. for example.LIOS V8. it means that the OS server is active and an attempt to deactivate the OS server has failed. select the record and press Delete. OS server activation finally allows LIOS to create observations on the OS server. select the record (radio button) you wish to modify – the IMS LEA name is automatically copied to the ‘IMS LEA name’ field – enter the new name into the input field and press Modify: the old name is replaced with the name you have just entered. all characters accepted except comma (. you go beyond the number of ports covered by the LIOS license (‘licensed ports’). If. 1. 80/185 A30828-X9410-B082-35-7619 . The OS server selected in the table is deactivated. and the expiration date is stated. If OS server activation fails.5. The activation/deactivation job is aborted. 3. Only records are displayed whose names match the string entered. Figure 3-54: Host Administration.4 OS server filter If you wish to reduce the number of records to be displayed. OS filter OS server name. The data is read from the database and the table is updated. ‘Wild cards’ (‘*’ and ‘?’) are accepted. Push buttons: Refresh. If a field is empty or not selected. Abort. a message is displayed to this effect.e.4. functions that are common to most LIOS filter forms) and push buttons see 3. the OS server’s response is displayed.2 User Manual – Administrator Issue 35 still be set up (‘free ports’).1. it has no influence on the filtering process. The form is closed. 3. If you exceed the number of ports. You can abort a job if there is no response from the OS server. For a description of general filtering functions (i. a hyperlink appears in the ‘Reason’ column. Activate. For more information see Host Administration: NEs. Section 3. If you click on the hyperlink. you can define a filter. Close.LIOS V8. Deactivate. Help. the current LIOS license will expire after 20 days.3. Application-specific online help is provided. The OS server selected in the table is activated. which tells you the reason for the failure.6 Host Administration: LIOS Servers The LIOS Servers sub-application enables you to enter the local parameters for the communication with NEs. 2. The LIOS Server data wizard (see 3. LIOS Servers Application commands New LIOS server.2 User Manual – Administrator Issue 35 Figure 3-55: Host Administration.4.5.LIOS V8.1) is started.6. LID and EFD (for the configuration of remote parameters see 3. A30828-X9410-B082-35-7619 81/185 . where you can enter the data for the applications MMLCM.6NE data wizard and 3. Delete LIOS servers. they are unselected. Specify the local communication parameters for the applications MMLCM.. The LIOS server name cannot be changed – the corresponding field is read-only. Export and Help see ‘general application commands’ in Section 3. Window size. where you can modify the LIOS server record. Actions. You can modify these values – at least you have to enter a new LIOS server name. Reverse charging. ‘modify LIOS server’ or ‘copy LIOS server’. and define sorting options. Default is ‘Off’. LID and EFD (for the configuration of remote parameters use the NE data wizard. Table The table provides you with an overview of LIOS server information. If LIOS is operated by an organization other than the telephone company who owns the NE. Specify each application separately for each LIOS server to be set up.25 connection. Select/unselect all. For the commands Refresh. Before you can use this command.6. Transport system through which the LIOS server can communicate with NEs and OSs. click on the LIOS server name (hyperlink) in the first column. As a rule. IP. where you can specify which LIOS servers should be displayed.LIOS V8. The LIOS server record is deleted.2 User Manual – Administrator Issue 35 OS Server data wizard). Transport systems. Delete LIOS server. it does not contain all details. For a detailed view. the party who has initiated the connection pays for it.6).4.6. The LIOS server data wizard (see 3. The LIOS server data wizard contains three forms for the administration of the local connection data.25 or both. you must select LIOS server records. X. Data that was entered for setting up an application and that is also needed for another application is automatically taken over to the respective forms and need not be entered again. The LIOS server data wizard is started.3. Maximum packet size at which flow control negotiation will start when an X. These actions affect only the individual record. Default value is 1024.25 connection is established. if all have been selected previously. Copy LIOS server. Specify each application separately for each LIOS server that uses the application.1. Default value is 7. Packet size. Records will only be deleted upon confirmation. Maximum window size at which flow control negotiation will start. 3. select ‘new LIOS server’. Table columns LIOS server name. reverse charging can possibly be set to ‘On’. It contains the values of the selected LIOS server record.1) is started. Modify LIOS server. A filter form is displayed. Print. Selected LIOS servers are deleted. All records in the table are selected (checkboxes in the first column) or.1. 82/185 A30828-X9410-B082-35-7619 . The LIOS server data wizard enables you to set LIOS server communication parameters according to the applications used. Section 3. modify or copy a LIOS server record and to set up applications for the LIOS server.1 LIOS server data wizard To start the LIOS server data wizard. Filter. This field specifies who pays for an X. The LIOS server data wizard enables you to add. 25 over ISDN (AFI is 44) and one for local X. For removing an X. X. depending on the transport system available.25 data record press Remove. X.25 (AFI is 36). Select the LIOS server name from the list provided.25 address data for specific connection types. Transport systems In the Transport Systems section you have to specify whether IP or X. For creating or modifying X. you can select both.25 is used for the communication with NEs/OSs.4.6.25 Data form will be displayed. The X.25. If the LIOS server is connected to both systems. A30828-X9410-B082-35-7619 83/185 .2 User Manual – Administrator Issue 35 General data Figure 3-56: LIOS server data wizard – General section LIOS server.25 or both. one for X.25 data press the New or the Modify button. Parameters for X.25 addresses specified: one for X. For details see 3. Figure 3-57: LIOS server data wizard – transport systems Transport systems: Select IP. There can be up to three X.25 data The table contains the X.LIOS V8.25 (AFI is 48). The FT application. LID and EFD. press the Modify button. select the application and press the Delete button. which covers FTAM and FTP. The Application data wizard is started.2 User Manual – Administrator Issue 35 APPLICATIONS Figure 3-58: LIOS server data wizard – Applications To set up an application on the LIOS server for the communication with NEs/OSs. where you can modify data for the selected application.7 (please note that not all pages and fields described there are needed for setting up applications on a LIOS server). where you can enter the data for a new application. LIOS supports the following applications: MMLCM.LIOS V8. select an application (radio button) and press the New button. For details about the applications see 3. need not be managed from the LIOS GUI because it is directly controlled by Solstice. Data that was entered for setting up other applications and that is also needed for the new application is automatically taken over to the new form.6.2 Application data form Figure 3-59: Application data form 84/185 A30828-X9410-B082-35-7619 . The Application data wizard is started. To modify application data.4. The selected application record is deleted. 3. To delete an application. 3.25 link on the LIOS server that should be used for outgoing connections (default is port 0). It identifies the port number of the Symicron X. EFD and LID): Transport selector. 4 digits max. The system title contains an object identifier consisting of decimal numbers separated by dots (. you specify a port number of the Symicron X. value range: 0 to 9999999.5 FN Siemens Mobile (MSC) Version SR9.7 Host Administration: NE Networks The NE Networks sub-application is available in connection with the following NE types: Network element Version Siemens EWSD Version 13 and higher Siemens Surpass hiE9200 Version 1.LIOS V8. Mandatory parameter. session selector. Port number for LIOS server. LID or EFD) within the system. OSI section Enter the OSI parameters for the application with relevance to the NE/OS server: transport selector. Accepted input: Hexadecimal: maximum length: 4 digits.5 Huawei GSM Based on HUAWEI interface specification version 1. Accepted input: Hexadecimal: maximum length: 4 digits. 10 components max. Mandatory parameter. presentation selector and application entity title. 3. Mandatory parameter.). containing system title and APQ – application program qualifier.2 User Manual – Administrator Issue 35 General section Specify the application you wish to set up. Presentation selector.24 Table 3-1: NE Networks sub-application A30828-X9410-B082-35-7619 85/185 . Mandatory parameter for the application layer (OSI layer 7). In addition. 2. SR10. It identifies the presentation layer (OSI layer 6). Application entity title. 4 digits max. Session selector. 1. 2 components min. optional.2 Siemens Surpass hiQ9200 Version 4 and higher Siemens IN@vantage Version 7. It consists of the application process title (mandatory. SR11 and SR12 Siemens IP Mediation Device Version 3. The following selector addresses are mandatory OSI layer parameters for the NE/OS server communication through Q3 (for MMLCM. Make sure that you enter exactly the same parameters that have been specified on the NE/OS server. The application entity title uniquely identifies an application (MMLCM. Value range: for 1st component: 0. Mandatory parameter (only for MMLCM and EFD). Maximum lengths: 30 digits. 3.). Application. For the whole application entity title (system title + APQ + AEQ): 10 components max. It identifies the transport layer (OSI layer 4). LID). Mandatory parameter. for 2nd component: 0 to 39.) and the AEQ (application entity qualifier. It identifies the session layer (OSI layer 5). It identifies the application type (MMLCM. Accepted input: Hexadecimal: maximum length: 4 digits. Select an application from the list provided.25 links on the LIOS server that should be used for outgoing connections. EFD. decimal number. Selected NE networks are deleted. Select/unselect all. NEs (Section 3. It can. LIOS operator groups that have access to the NE network must have been set up as MMLCM users on each NE of the NE network (see 3. you must select one or more NE network records.7.1) is opened. If an NE has been a member of this NE network before and. the data displayed reflects the default filter settings. An NE network can only be deleted if it contains no NEs. If you wish to see another selection of data.4. A filter form appears where you can specify criteria for the data to be displayed. Figure 3-60: Host Administration. 86/185 A30828-X9410-B082-35-7619 . where you can specify which NE networks should be displayed. This can only be done by a LIOS operator who is a member of the LIOS operator group that owns the NE network observations. NE networks are essential for observing mobile-network subscribers. NE network name.4).7). A Siemens EWSD version 13A can only be added to a network if such a network contains no active INobservation. NE Networks Application commands New NE network. Delete NE networks. for some reason. however. where you can specify NE network type. Before you can use this command. they are also needed for the monitoring of foreign directory numbers (FDN) or inside an intelligent network (IN) on fixed-network elements. The NE network data form (see 3. When you start Host Administration. the child observations must be canceled first. where you can enter the data for the new NE network to be set up. For more information see Host Administration. still has child observations pertaining to the NE network. Filter. NE Networks.7. NE networks allow LIOS operators to set up observations on each NE of the entire NE network specified by issuing only a single observation. and define sorting options. A filter form is displayed. All records in the table are selected (checkboxes in the first column) or. The NE network data form (see 3.1) is displayed. contain NEs of different versions.2 User Manual – Administrator Issue 35 From LIOS’s point of view. An NE that is shared by several providers cannot be added to an NE network. they are unselected. An NE network can only contain NEs of the same type.LIOS V8. Please also bear this in mind when you add an NE to an existing NE network. Records will only be deleted upon confirmation. NEs can be organized in NE networks. NE network members and NE network user authorization. if all have been selected previously. select the Filter command from the application commands bar. Export and Help see ‘general application commands’ in Section 3. … Actions. Modify NE network. Table columns NE network name. For a detailed view. Print. Copy NE network. The NE network types listed in the pull-down menu depend on the license. NE network NE network name.7. Delete NE network.LIOS V8. A30828-X9410-B082-35-7619 87/185 . The NE network data form is opened.1. The NE network record is deleted. Figure 3-61: NE network data form. Name of NE network.2 User Manual – Administrator Issue 35 For the commands Refresh. select ‘new NE network’.1. An NE network can only be deleted if it contains no NEs. where you can modify the NE network record. You can modify these values – at least you have to enter a new NE network name. click on the NE network name (hyperlink) in the first column. 3. ‘modify NE network’ or ‘copy NE network’.1 NE network data form To open the NE network data form.1) is opened. The NE network name cannot be changed – the corresponding field is read-only.3. NE network type. It can be e.7. Siemens Mobile (MSC). It contains the values of the selected NE network record. Table The table provides you with an overview of NE network information. it does not contain all details. Siemens Fixed (comprising EWSD and hiQ/E9200). Name of NE network. The NE network data form (see 3.g. These actions affect only the individual record. the NE is a member of the NE network. However. where you can restrict NE network access to only a selection of LIOS operator groups. Siemens Fixed (comprising EWSD and hiQ/E9200). Siemens Mobile (MSC). If the checkbox is selected (check mark). Restrict button. To add or remove an NE. select or unselect the checkbox. NE name. If an NE is removed from the NE network. If an NE is added to an NE network. The NE network types listed in the pull-down menu depend on the license. Table columns Member.LIOS V8. Figure 3-62: NE network data – ‘Access to NE network’ form 88/185 A30828-X9410-B082-35-7619 . NE network access rights cannot be taken from it (observations should be taken over by another LIOS operator group). child observations of observations set up on the NE network are automatically created on the NE. It can be e.2 User Manual – Administrator Issue 35 NE network type. … Select a type from the pull-down list.g. Access to NE network. LIOS operator group who is authorized to access the NE network. child observations of observations set up on the NE network are automatically canceled (‘cleaned’) on the NE. Operator groups. The ‘Access to NE network’ form is displayed. It shows the names of all NEs of the selected NE type which are active and have just one provider assigned. if a LIOS operator group still owns network observations. All LIOS operator groups that have access to the NE are shown here. The address parameters are sent to the NE when an observation is created. LIOS provides the option of automatically routing all those lost tickets to a default LEA. Siemens hiQ4200/8000. Siemens EWSD. An alarm message is generated for each unknown observation when the first LI ticket concerning this observation is received (alarm A-OIF-00009: ‘LI observation unknown’). follow the instructions in the User Manual – Administrator. In the context of LIOS it is always referred to as LEA. A filter form appears. You can view these alarm messages with the Alarm browser.8 LEA Administration The LEA Administration enables you to specify the configuration parameters for the links to the law enforcement agencies (LEA) and to specify parameters concerning the format of the LI data sent to a LEA. the data displayed reflects the default filter settings. where you can specify criteria for the data to be displayed. and Alcatel S12 has ‘virtual subscriber’ (TAX). hiQ4200/8000 has ‘CALEA intercept entry'. Technically speaking. and Alcatel S12 have entirely different viewpoints of LEAs. Section 4. NE and OS terminologies differ: EWSD and hiQ/E9200 have ‘observation group’ (OBSGRP). Nevertheless. It can happen that tickets cannot be assigned to any LEA. MSC and Utimaco IMS have ‘Monitoring Center’ (MONC). As regards the term LEA. Figure 3-63: LEA Administration A30828-X9410-B082-35-7619 89/185 . all LI tickets (LI records) that cannot be assigned to a LEA will remain in the LIOS system. hiQ/E9200 and MSC.2 User Manual – Administrator Issue 35 3.) If no default LEA has been defined.LIOS V8. select the Filter command from the application commands bar. When you start the LEA Administration. If you wish to see another selection of data. Link for call contents Call content data is directly sent via ISDN from the NE to the LEA. LIOS enables you to handle LEAs in much the same manner. as is described in the User Manual – Administrator). (To activate a default LEA. For each LEA (that uses Q3) you can administer two types of links: Link for LI tickets LI tickets are forwarded from LIOS to the LEA through FTP or FTAM (the LIOS-specific FTAM parameters have to be administered on each LIOS server. Print.) 3. Selected LEAs are deleted. You can modify these values – at least you have to enter a new LEA name. The Communication Settings form (Figure 3-85) is displayed. LEA phone number provided in case ticket routing to the LEA is not working. The LEA data wizard (see 3. click on the LEA name (hyperlink) in the first column. The LEA data wizard is started. Communication settings. you must select one or more LEA records.8.4. Phone. These actions affect only the individual record.2) is started. Table The table provides you with an overview of LEA information. The LEA data wizard (see 3. Copy LEA. it has no influence on the filtering process. where you can modify the LEA record. it does not contain all details. where you can set timers and counters for further attempts of LI ticket transfer to LEAs in case of error. The communication settings control the transfer to all LEAs. Select/unselect all. (See 3. It contains the values of the selected LEA record. 6-digit decimal number. Actions. LEA ID on NEs/OSs. The name of a default LEA (see 3.LIOS V8. A LEA record can only be deleted if there are no active and no archived observations associated with it. if all have been selected previously. Number (generated by LIOS) by which a LEA is known to NEs and OSs.3. Export and Help see ‘general application commands’ in Section 3. where you can specify which LEAs should be displayed. Records will only be deleted upon confirmation. Modify LEA. LEA address provided in case ticket routing to the LEA is not working. Filter.8.8. and define sorting options. If a field is empty or not selected.1. A filter form (Figure 3-64) is displayed. LEA name. Delete LEA. For the commands Refresh.8. The result of a LEA modification on NEs and OSs is checked and presented in a report.2) is rendered in bold print. For a detailed view. they are unselected. Table columns LEA name.2) is started.2 User Manual – Administrator Issue 35 Application commands New LEA. Delete LEAs. Before you can use this command. where you can enter the data for the new LEA to be set up. The LEA record is deleted. you can define a filter. 90/185 A30828-X9410-B082-35-7619 .1 LEA filter If you wish to reduce the number of records to be displayed. All records in the table are selected (checkboxes in the first column) or. Observations can only be deleted by the LIOS supervisor.1. The LEA name cannot be changed – the corresponding field is read-only. Check LEA modification. settings for individual LEAs are not possible.8. Address. Z and # $ % + / ? @ _ -. Phone number of the LEA to be entered in case ticket routing to the LEA is not working. LEA name. A. LEA phone number provided in case ticket routing to the LEA is not working. Only records are displayed whose names match the string entered. a. Mandatory parameter. 3. You can also add a remark.2 LEA data wizard The LEA data wizard is provided for creating. the only exceptions are passwords. Accepted input: 0.2 User Manual – Administrator Issue 35 Figure 3-64: LEA filter LEA name.LIOS V8... If a LEA has active observations assigned to it. you cannot modify the LEA name. For a description of general filtering functions (i. functions that are common to most LIOS filter forms) and push buttons see 3. Phone.8.1..1 LEA identification Figure 3-65: LEA data wizard – LEA identification Enter the LEA’s name.2.e. modifying and copying LEA records.1. Name of the LEA. 3.9. ‘Wild cards’ (‘*’ and ‘?’) are accepted. Maximum length: 30 characters. Phone.8. A30828-X9410-B082-35-7619 91/185 . exact postal address and phone number for clear identification of the LEA. NOTICE REGARDING EWSD AND hiQ/E9200: Lower-case letters as parts of MML commands and parameters are not accepted by EWSD and hiQ/E9200..z. Mandatory parameter.3. A. Maximum length: 60 characters. Which profile types are available. all LI tickets that cannot be assigned to a LEA will remain in the LIOS system.z. Mandatory parameter. It depends on the selected profile type whether a parameter form will be displayed or not (press Next/Finish). Accepted input: 0.# * blank (whitespace). a.. Define.LIOS V8. Only for LIOS administrators. Select the appropriate option button and press Remove. If this LEA is to serve as default LEA. Select the appropriate option button (Siemens Fixed (EWSD. 3. depends on the license of the LIOS system you are working with. select the checkbox.2 User Manual – Administrator Issue 35 Maximum length: 24 characters. …) and press Define. you have to define the corresponding profile for the LEA. Accepted input: all characters accepted. If no default LEA has been defined.Z and () /+. Observation parameters are necessary for creating an observation for the LEA. Enter the address of the LEA in case ticket routing to the LEA is not working. one can be specified as a default LEA. An alarm message is generated for each unknown observation when the first LI ticket concerning this observation is received (alarm A-OIF-00009: ‘LI observation unknown’). The name of a default LEA is rendered in bold print.2. Accepted input: all characters accepted.. Alcatel.2 Profile types Figure 3-66: LEA data wizard – profile types In order to enable the LEA to receive tickets from NEs of a particular type. These alarm messages can be viewed with the Alarm browser. Remove. 92/185 A30828-X9410-B082-35-7619 . Of all LEAs set up in the LIOS system. Remark.8. The selected NE type will be removed. Address. Default LEA. hiQ/E9200).. The choice of input fields depends on the type of the NE or OS server that has been selected in the previous form.9.. The default LEA will receive all tickets that cannot be assigned to any LEA (stray tickets). Maximum length: 60 characters. Optional parameter. Version of signaling information in the call content connection: SUBADD-SIGV12 (EWSD V12 and higher. A30828-X9410-B082-35-7619 93/185 . Version of the LI tickets: RECV12 (EWSD V12 and higher.2). DN of ticket connection. where B is interchangeable with * and C is interchangeable with #. and hiE9200 V1 and higher) and RECV17 (EWSD V17/V18 and hiE9200 V3/V3.25 addresses or the IP address specified in the Transfer Protocol and Transport System forms). and hiE9200 V1 and higher). Mandatory parameter.1 Siemens Fixed (EWSD. Number of LAC digits. Overflow DN (call content). Once the LEA has been created. Optional parameter. For details see [4]. this parameter cannot be modified. Version of signaling (call content). Version of LI tickets. Number (generated by LIOS) by which a LEA is known to NEs. Mandatory parameter. This number is sent together with the LI ticket from an NE to LIOS and enables LIOS to identify the LEA that should get the LI ticket (LI tickets are sent from LIOS to the LEA through FTAM or FTP by using the OSI and X. Remark: Since LI tickets are not sent directly from an NE to a LEA. this number is not used for sending LI tickets but it serves as a unique identification for a LEA in the LIOS system. and hiE9200 V1 and higher). SUBADD-SIGV13 (EWSD V13A and higher. Nationally significant directory number (LAC and DN) of the overflow destination for call content data.LIOS V8.2. Nationally significant directory number (LAC and DN) of the LEA.2. REMARK: For referring to ticket (record) layout. where B is interchangeable with * and C is interchangeable with #. Nationally significant directory number (LAC and DN) of the LEA for the transmission of the call content. hiQ9200 V4 and higher. 1 to 24 hexadecimal digits accepted. hiQ9200 V4 and higher.8. Read-only field. hiQ9200 V4 and higher. record version 2 (RECV13). hiQ/E 9200) observation parameters Figure 3-67: LEA data wizard – EWSD and hiQ/E9200 observation parameters LEA identification on NEs.2 User Manual – Administrator Issue 35 3. and hiE9200 V1 and higher). only for charging purposes. Length of LAC. 1 to 24 hexadecimal digits accepted. hiQ9200 V4 and higher. 6-digit decimal number. record version 3 (RECV14) and record version 4 (RECV17). It is recommended to enter here the same number as for the ‘DN of LEA’ field. RECV14 (EWSD V14A and higher. 1 to 24 hexadecimal digits accepted. and hiE9200 V1 and higher). other names are used: record version 1 (corresponds to RECV12). this parameter cannot be modified. RECV13 (EWSD V13A and higher. Once the LEA has been created. DN of LEA (call content). hiQ9200 V4 and higher. 2 User Manual – Administrator Issue 35 SUBADD-ETSIV2 and UUS1-ETSIV2 (the latter two only for EWSD V17/V18 and hiE9200 V3/V3. If Ticket Conversion is not available. NE data wizard) will be transmitted to the LEA. ‘ETSI V2. Transmission (Transmission mode): Choose whether intercept-related information should be sent to the LEA through Q3 as LI tickets or in band (INB). it is referenced by the LI CUG parameters interlock code and the network identification code. If the ‘CUG indexing activated’ flag has been set in the NE data. you must select INB. Single connection (call content). It enables ticket output in the formats ‘Native’ (i. the LI CUG is referenced by an index. If this checkbox is selected. If this checkbox is selected. CUG name.11). 94/185 A30828-X9410-B082-35-7619 . If the network provider has EWSD V15 (hiE9200 V1) or EWSD V16 (hiE9200 V2) switches and the call content is to be transmitted to the LEA in ETSI format. you must select INB.12 with national parameters for Germany. the A-side and B-side call content information will be transmitted separately through two 64-kbit connections. Inband RP 2. if not.1’ (i. Optional parameter. ‘Siemens binary’). Inband reduced protocol 1 (specified for EWSD V.e.1 National A’ (i. and for hiQ/E9200. which is the EWSD and hiQ/E9200 ticket format. LAC) of the NE is to be displayed on the LEA telephone set. as part of the LI ticket. To assign the LEA to an LI CUG. Not all ticket formats may be available in the LIOS system you are working with (license-specific restriction). If INB is used.1 (2005-08)). and hiQ/E9200. ‘single connection’ is not possible. the call content information will be transmitted via a single 64-kbit connection to the LEA as the sum of information of the call contents of user A and user B. If this checkbox is selected. Inband RP 1.) CLIP (calling line identification presentation) DN. in-band IRI transmission is optional. ‘ETSI V2.10) with additional information concerning the call identity used. NE identification number.12. Before you can select INBRP2. This parameter specifies whether a virtual directory number (incl. (If the ‘version of signaling’ is SUBADD-ETSIV2 or UUS1-ETSIV2. INB (in-band IRI transmission). it checks whether the directory number to receive the call content is indeed identical with the number entered under ‘DN of LEA (call content)’. For SUBADD-ETSIV2 and UUS1-ETSIV2 the appropriate LI properties have to be set on the NE.e. version V13A and higher. Before you can select INBRP1. select this checkbox. based on ETSI TS 101 671 V2. For NEs of the type Siemens EWSD.LIOS V8. Q3. for EWSD V11 and lower it is mandatory. For NEs of the type Siemens EWSD. COLP (connected line identification presentation) feature.1). Inband reduced protocol 2 (specified for EWSD V. ‘ETSI V2. HI3 encoding can only be activated in connection with Q3.e. If the DN of the LEA has been rerouted or if a switching error has occurred. Ticket output format. Transport of IRI (intercept-related information) and call content through the same channel. Ticket Conversion is an optional feature. ‘ETSI V2. the NE identification number (see Host Administration. tickets are output as ‘Siemens binary’. For EWSD V12.2). Intercept-related information will be sent to the LEA as LI tickets through a Q3 interface. ETSI V2. If the checkbox is not selected. no LI tickets are generated and there is no link for LI tickets between LIOS and the LEA – the intercept-related information is sent by the NE to the LEA together with the call content over ISDN. ETSI HI3 encoding for EWSD V15&V16. select an LI CUG name from the pulldown list. ‘Siemens ASCII’.e. Explanation: Before the EWSD or hiQ/E9200 switch routes the call content to the LEA. the call content will not be sent. the call content connection will be protected through the COLP feature.12 National D’ (i. version V13A and higher.1 with national parameters for Austria and with file naming method A applied) or ‘Ticket Header V1’. ticket format according to ETSI Standard ES 201 671 V2. Ticket output format. It enables ticket output in the formats ‘ETSI V2. Only relevant for hiQ4200/8000 R11 to support stereo mode call content delivery.LIOS V8. Call data IP port. Mandatory parameter.8.1).12. ticket format according to ETSI Standard ES 201 671 V2.2. You can only enter a DN destination 2 if you have entered a DN destination.e.1’ (i. Number (generated by LIOS) by which a LEA is known to NEs. Choose the LIOS server from the drop-down list. Mandatory parameter.2 User Manual – Administrator Issue 35 3. Also the following 2 parameters are not longer relevant: Call content IP address.properties configuration).12 with national parameters for Germany. ETSI V2. enter the IP address (decimal numbers separated by dots). If LIOS is used as a ticket mediation device (default configuration). based on ETSI TS 101 671 V2. Port for IP address where the intercept-related information (LI tickets) will be sent.1 with national parameters for Austria and with file naming method A applied). IP address where intercept-related information (LI tickets) will be sent. 1 to 30 digits accepted.2 Siemens Fixed (hiQ4200/8000) observation parameters Figure 3-68: LEA data wizard – hiQ4200/8000 observation parameters LEA identification on NEs. Nationally significant directory number (LAC and DN) of the LEA for the transmission of the call content. Call content static DN destination 2. Read-only field. If no drop-down list is available (lios.e.1 National A’ (i.2. If it is not specified with a different DN the transmitting and the receiving call content will be sent via the same DN. and CALEA (depends on license). 1 to 30 digits accepted. Call content static DN destination.12 National D’ (i. Nationally significant directory number (LAC and DN) of the LEA for the transmission of the call content. Call content IP port. this address must correspond to one of the LIOS servers.e. ‘ETSI V2. A30828-X9410-B082-35-7619 95/185 . Call data IP address. ‘ETSI V2. Mandatory parameter. 6-digit decimal number. Therefore it is necessary that the LI option Srx/Main/hiQVariant = 2 (value for ETSI) is set on the switch. Note: the hiQ4200/8000 switch can be operated in ETSI mode or in ANSI mode. ‘ETSI V2. which is at the same time the hiQ 4200 ticket output format. LIOS supports only the ETSI mode.1 (2005-08)). ‘ETSI V2. Call protection ISDN number. Ticket Conversion is an optional feature. If the two numbers do not match. Mandatory parameter. Enhanced signaling to LEA in call content (see also ‘Call identification’ below).9. select an LI CUG name from the pulldown list.2. If Ticket Conversion is not available.12.8. Enhanced signaling.. ticket format according to ETSI Standard ES 201 671 V2. the LI CUG is referenced by an index.1 (2005-08)).e. Ticket output format. DN of LEA (call content).2.9.1) or ‘ETSI V2.2 User Manual – Administrator Issue 35 3.e.LIOS V8. Optional parameter. Call data notification. CUG name. Can not be used together with ‘ETSI signaling’. Number (generated by LIOS) by which a LEA is known to NEs. ETSI V2. Nationally significant directory number (LAC and DN) of the LEA for the transmission of the call content. Only tickets (S-records) are sent to the LEA when the LEA is not allowed to monitor call content forwarded in the GMSC (Gateway MSC). 6-digit decimal number. the stub line connection will be released. Not all ticket formats may be available in the LIOS system you are working with (license-specific restriction). based on ETSI TS 101 671 V2.12 with national parameters for Germany.1’ (i. which is the MSC ticket format.. it is referenced by the LI CUG parameters interlock code and the network identification code.3 Siemens MSC observation parameters Figure 3-69: LEA data wizard – MSC observation parameters LEA identification on NEs. Accepted input: 0. the DN entered in the observation parameters is checked against the DN of the LEA (call content) specified here. To assign the LEA to an LI CUG.12 National D’ (i. if not. Accepted input: 0. Length: 1-16 decimal digits. tickets are output as ‘Native’. It enables ticket output in the formats 'Native' and 'Native for MC' (= Native format including 2 bytes of header information). Before the call content is rerouted. Length: 1-16 decimal digits.This parameter can only be used if ‘Location dependant interception’ is set on the NE. If the ‘CUG indexing activated’ flag has been set in the NE data. 96/185 A30828-X9410-B082-35-7619 . This parameter specifies whether the call content connection should be protected through ‘call protection ISDN number’. Not applicable for SR12. Read-only field. This parameter defines all LACs in which a LEA is allowed to monitor intercepted subscribers. Check if any type of ‘ETSI signaling’ is used (LI option UDI has to be activated on the used NE). DN of LEA (video content). the LI option ETSIHI has to be active on the NE. Number (generated by LIOS) by which a LEA is known to NEs. DTMF (dual tone multi frequency) tones. ETSI handover interface (ETSI V2) will be used for call content and for the IRI records. This feature enables a law enforcement agency (LEA) to receive on the call data channel digits dialed by the monitored subscriber. Unrestricted digital info. Read-only field. DTMF tones allowed in call content transmitted to LEA. Use this parameter only if ‘Location dependant interception’ is activated on the relevant NEs 3. thus enabling the LEA to put call content and tickets together (correlation information). ETSI signaling can not be used. Nationally significant directory number (LAC and DN) of the LEA for the transmission of the video content. This number will be added to the call content and LI tickets. To each intercepted call a unique number (call identification) will be given. If you leave this parameter blank. Unrestricted digital information 64 kbit. Optional parameter. Interception of DTMF in tickets (call data channel – CDC). The transmission of unrestricted 64-kbit digital information in a call to the LEA is supported. Forwarded to number country code. Select this checkbox if the LEA terminal can handle DTMF. ‘Call identification’ is recommended. Optional parameter. choose one of the following options: User to user service information (UUS1-ETSIV2). Maximum of 25 LACs can be entered (one by one with ‘&’ sign or in an interval with ‘&&’ sign or value ‘X’ for all LACs of the related NE. For assigning all country codes value ‘X’ has to be entered for this parameter. Location area Code(s).2 User Manual – Administrator Issue 35 Call identification. ETSI signaling.9. If ‘Enhanced signaling’ is turned on. Nationally significant directory number (LAC and DN) of the LEA for the transmission of the call content. If ETSI signaling is checked. Subaddressing (SUBADRR-ETSIV2). Maximum length: 30 decimal digits.8. These post-cut-through digits are digits dialed or signaled by the intercepted subject after the initial call setup is completed and the call path is cut-through in both directions at the IAP (internet access provider) switch.LIOS V8. A30828-X9410-B082-35-7619 97/185 . For ETSI signaling type. Note: If ETSI is used. Not applicable for SR9. Accepted input: 0.2.. Maximum of 30 country codes can be assigned to one LEA (one by one with ‘&’ sign or in an interval with ‘&&’ sign). Intercepted calls forwarded through GMSC (Gateway MSC) can be monitored only if the LEA has the appropriate country code assigned. ‘Enhanced signaling’ must be active.2.4 Huawei GSM observation parameters Figure 3-70: LEA data wizard – Huawei GSM observation parameters Huawei LEA ID. Mandatory parameter. DN of LEA (call content). such calls will not be monitored. Use this parameter only if on the relevant NEs the feature ‘Location dependant interception’ is activated. LIOS V8.2 User Manual – Administrator Issue 35 Maximum length: 30 decimal digits. Accepted input: 0..9. Ticket output format. ETSI and Native format are supported. ETSI is the standard format. Native is the original ticket format as received from the Huawei GSM switch. The entries in the pull-down menu of the output format depend on the License. Output mode. It is possible to select ‘Combined’ or ‘Split’. Combined means that the call content information will be transmitted to the LEA as the sum of information of the call contents of user A and user B. Split means that the A-side and B-side call content information will be transmitted separately to the LEA. 3.8.2.2.5 Alcatel S12 observation parameters Figure 3-71: LEA data wizard – Alcatel S12 observation parameters LEA identification on NEs. Read-only field. Number (generated by LIOS) by which a LEA is known to NEs. 6-digit decimal number. DN of LEA (call content). Mandatory parameter. Nationally significant directory number (LAC and DN) of the LEA for the transmission of the call content. Maximum of 28 digits between 0 to 9 and A to E. The DN of LEA must be in national format, i.e. with area code but without area code prefixes (such as a leading 0). Ticket output format. Ticket Conversion is an optional feature. It enables ticket output in the formats ‘Alcatel S12 native’, ‘ETSI V2.1’ (i.e. ticket format according to ETSI Standard ES 201 671 V2.1), ‘ETSI V2.1 National D’ (i.e. ‘ETSI V2.1 with national parameters’), or ASCII. Not all ticket formats may be available in the LIOS system you are working with (license-specific restriction). If Ticket Conversion is not available, tickets are output as ‘Alcatel S12 native’, which is the Alcatel S12 ticket format. Note: By default HI1 notifications are created for observation activation, modification and deactivation. These notifications are always created in ETSI V2.1 format independent from the selected Ticket output format. To supress creation of HI1 notifications the following property has to be specified in the lios.properties file: TicketRouter.createHI1 = 0 DN of ticket connection. Mandatory parameter. Nationally significant directory number (LAC and DN) of the LEA. 1 to 28 characters are accepted from the sets 0 – 9 and A – E. Remark: Since LI tickets are not sent directly from an NE to a LEA, this number is not used for sending LI tickets but it is used as a unique identification for a LEA in the LIOS system. This number is sent together with the LI ticket from an NE to LIOS and enables LIOS to identify the LEA that should get the LI ticket (LI tickets are sent from LIOS to the LEA through FTAM or FTP by using the OSI and X.25 addresses specified in the Transfer Protocol and Transport System forms). It is recommended to use the same number as for the ‘DN of LEA’ field. Once the LEA has been created, this parameter cannot be modified. TAXDNS for network elements. TAXDN (also called DN of virtual subscriber) identifies the virtual subscriber, which is the Alcatel S12 term for LEA. This parameter is roughly equivalent to the observation group ID of EWSD, hiQ/E9200 and MSC switches. There are two essential differences: – The observation group ID of a LEA is automatically generated by LIOS and sent to the switches. 98/185 A30828-X9410-B082-35-7619 LIOS V8.2 User Manual – Administrator Issue 35 The observation group ID of a LEA is unique within the system. A LEA is identified through the same observation group ID by all EWSD, hiQ/E9200 and MSC switches . – The TAXDN is kept on the individual S12 switch and has to be entered in the LIOS system.The DN of virtual subscriber is different on every Alcatel S12 switch, although it identifies the same LEA. Enter the DNs of virtual subscribers for all switches that should have a connection with the LEA you are setting up. The field names in this form correspond to the S12 switches that have been created in the Host Administration. A DN must comprise at least 4 digits and as a maximum 16 digits; each digit must be in the range of 0 to 9 and A to E. The DN of virtual subscriber must be in national format, i.e. with area code but without area code prefixes (such as a leading 0). It is used for charging purposes, i.e. to charge the LEA for the call content (CC) links. A DN of virtual subscriber can be modified only if there are no active observations associated with it. 3.8.2.2.6 Huawei Fixed For the delivery of notifications and alarm messages, Huawei C&C08 switches can handle a maximum of three LEAs, referred to as ‘Huawei monitoring centers’. Up to three Huawei monitoring centers (MC0, MC1 and MC2) have been set up on every Huawei C&C08 switch for this purpose (by the LIOS administrator, with the NEs sub-application of the Host Administration). For the delivery of call content and LI tickets, Huawei switches can handle far more LEAs. Each LEA, however, has to be associated with a ‘Huawei monitoring center’, which actually receives notifications and alarms messages. Huawei Fixed observation parameters Figure 3-72: LEA data wizard – Huawei Fixed observation parameters DN of LEA (call content). Mandatory parameter. Nationally significant directory number (LAC and DN) of the LEA for the transmission of the call content. A maximum of 24 characters is accepted. It can contain digits, * and #. Ticket output format. Currently only the ETSI V2.1 (native) format is supported. This is the original ticket format as received from Huawei C&C08 switch. LIOS performs no mediation of IRI record content. Huawei MC ID. Select an ID. The LEA will be associated with the respective Huawei monitoring center – call content and LI tickets will be routed to the LEA, notifications and alarm messages to the Huawei monitoring center. If there is an observation referring to the LEA, the Huawei MC ID cannot be changed; this field is read-only. HI2 processing server Figure 3-73: LEA data wizard – HI2 processing server A Huawei C&C08 switch sends IRI records to the LIOS HI2 processing server. LIOS further forwards the IRI records to the LEA. A30828-X9410-B082-35-7619 99/185 LIOS V8.2 User Manual – Administrator Issue 35 LIOS server. This is the server that receives IRI records from the Huawei switch. Choose one of the LIOS servers from the combo box. HI2 IP address. This field is read-only and is automatically filled with IP address of the chosen HI2 server. Other LEA-specific settings, e.g. COLP, concern the Huawei monitoring center itself. They cannot be made in this form but in the LIOS Host Administration/NEs sub-application (by a LIOS administrator). 3.8.2.2.7 Huawei GSM observation parameters Figure 3-74: LEA data wizard – Huawei GSM observation parameters Huawei LEA ID. Read-only field. Number (generated by LIOS) by which a LEA is known to NEs. DN of LEA (call content). Mandatory parameter. Nationally significant directory number (LAC and DN) of the LEA for the transmission of the call content. Maximum length: 30 decimal digits. Accepted input: 0..9. DN of LEA (video content). Optional parameter. Nationally significant directory number (LAC and DN) of the LEA for the transmission of the video content. Maximum length: 30 decimal digits. Accepted input: 0..9. Ticket output format. ETSI and Native format are supported. ETSI is the standard format. Native is the original ticket format as received from the Huawei GSM switch. The entries in the pull-down menu of the output format depend on the License. Output mode. It is possible to select ‘Combined’ or ‘Split’. Combined means that the call content information will be transmitted to the LEA as the sum of information of the call contents of user A and user B. Split means that the A-side and B-side call content information will be transmitted separately to the LEA. 100/185 A30828-X9410-B082-35-7619 =&.z. Confirm..2.9. One record can be specified for the protocol XML_GE. Select one of the following protocols: • • XML_GE (XML Germany) Siemens_Proprietary A30828-X9410-B082-35-7619 101/185 .. LEA IP address to which the data will be delivered. i. Protocol. Accepted input: IP address format (4 times 0–255 separated by dots. Maximum length: 20 characters..8.2 User Manual – Administrator Issue 35 3.. A._/-?:. IP port. Protocol used for data delivery.. Accepted input: a.#*+"!$()<>. Accepted input: a. Read only. The following parameters are optional: User. Retype the password. Port through which the data will be sent to the LEA. e.Z.9..: 155. Maximum length: 32 characters. %. Enter a user name.e.=&. LEA ID. %. Enter a user-defined password.LIOS V8.... Accepted input: 1–65535.#*+"!$()<>. Name of the LEA.0.Z. Five records can be specified for the protocols ‘Siemens_Proprietary’ and ‘ETSI_IP’._/-?:. The following parameters are mandatory: IP address.g.12.8 Mediation Device (Siemens IP) observation parameters Figure 3-75: LEA data wizard – Mediation Device (Siemens IP) observation parameters This form is provided for specifying the delivery data of the LEA. 0. Password.z. A. IP address.2.. 0. port and protocol to be used.104). 0. A. Accepted input: a.e. which can be used as LEA identification (COLP feature). Press Delete.9 Nortel Fixed (LIM) observation parameters Figure 3-76: LEA data wizard – Nortel Fixed (LIM) observation parameters DN of LEA (call content).1 with national parameters for Austria’). IP port. Add. The selected delivery data record will be deleted (the number on the left will remain visible). The selected delivery data record will be replaced with the data entered in the input fields above.8.. Maximum length: 40 characters. DN of LEA 2 (call content).LIOS V8. must be unique..1 National A’ (i. Select the delivery data record you wish to modify (radio button). Press Add. IP port and select a protocol. Modify. Optional parameter. Accepted input: A-Z and 0-9. Call content destination. 3._-. Select the delivery data record you wish to delete. where B is interchangeable with * and C is interchangeable with #. A valid FTP address for delivering tickets. Enter IP address. where B is interchangeable with * and C is interchangeable with #.=&. 1 to 24 hexadecimal digits accepted. Press Modify. ‘ETSI V2. %..2. Ticket output format. Length: 4-16 characters. Mandatory parameter.8. Enter IP address.2.2 User Manual – Administrator Issue 35 • ETSI_IP Directory. Alternative number.10 Utimaco IMS observation parameters Figure 3-77: LEA data wizard – Utimaco IMS observation parameters 102/185 A30828-X9410-B082-35-7619 . The ticket format provided is ‘ETSI V2. LIM LEA ID. The Protocol can not be modified. Nationally significant directory number (LAC and DN) of the LEA for the transmission of the call content. 1 to 24 hexadecimal digits accepted.z. Mandatory parameter. 3. Delete.Z..9.2.2. The data you have entered is copied into the list below. You can modify the IP address and the IP port. LEA identification in the LIM system..#+!$(). Mandatory parameter with a maximum of 32 characters. ‘FTAM/IP’ and ‘FTP’.LIOS V8. Mandatory parameter. IP address.). If you have entered a DN of LEA for the voice delivery. Additional fields – depending on your choice – will be displayed (see Figure 3-78.25 User ID.). Retype the password. This parameter is needed for an observation to be created in a GPRS network. Optional parameter. Figure 3-79 and Figure 3-80). length: 1 to 19 A30828-X9410-B082-35-7619 103/185 . This parameter is needed for an observation to be created in a GSM network. The options are ‘FTAM/X. all characters accepted except comma (. all characters accepted except comma (.). It identifies the transport layer (OSI layer 4). Nationally significant directory number (LAC and DN) of the LEA for the transmission of the call content. Confirm. IRI records per FTAM/X. FTAM over X.25’. tab stop and blank. It is automatically set to ISDN. You have to enter the same user ID that has been specified on the LEA terminal. Choose a transfer protocol and a transport system from the pull-down list. Accepted input: ASCII: all characters except comma (. The file transfer connection from IMS and the LEA will be opened with this user ID. The file transfer connection to the LEA will be opened with this password. double quote (“). IMS uses its own mediation function – IRI records do not reach LIOS. tab stop and blank. It is automatically set to GTP* (GPRS Tunnelling Protocol) over IP. Transport of data.2 User Manual – Administrator Issue 35 The communication data you enter on this page will be sent to IMS telling it where the intercepted information should be sent. 1 to 25 hexadecimal digits accepted. Transport selector. you can specify a CUG name. For the routing of IRI records (tickets). Transport of voice. Parameter needed for user authentication for the file transfer connection to the LEA. CUG name. IP address of the LEA’s data recording device. Password.25 Figure 3-78: LEA data wizard – IMS. Depending on your choice. double quote (“). Optional parameter. You have to enter the same password that has been specified on the LEA terminal. additional fields will be displayed. DN of LEA. tab stop and blank. Transport of IRI records. select one from the pull-down list. double quote (“). Mandatory parameter with a maximum of 32 characters. Parameter needed for user authentication for the file transfer connection to the LEA. Session selector. Hexadecimal: Hexadecimal digits. Hexadecimal: Hexadecimal digits. FTP 104/185 A30828-X9410-B082-35-7619 . length: 1 to 19 characters. switching between editing modes may not work. tab stop and blank.) Application entity. A-F.). Selector editing. Specifies the X. a-f. tab stop and blank. Mandatory parameter.). double quote (“). The application entity title consists of application title and AEQ. Input format for ASCII: all printable characters except comma (. tab stop and blank. FTAM over IP Figure 3-79: LEA data wizard – IMS. Accepted input: ASCII: all characters except comma (. Mandatory parameter.25 address for routing. length: 1 to 38 digits. double quote (“). (If non-printing characters are involved. You can also switch to the other editing mode if the selector fields have already been filled in – the character strings are instantly converted. Mandatory parameter. Select ASCII mode or Hexadecimal mode. DTE (data terminal equipment) address. The application entity title uniquely identifies an application (here FTAM) within the system (OSI layer 7). Mandatory parameter. length: 1 to 19 characters. Mandatory parameter. IP address.2 User Manual – Administrator Issue 35 characters. IRI records per FTAM/IP The FTAM parameters are described above.LIOS V8. Hexadecimal: Hexadecimal digits.). IP address of the LEA terminal (LEMF) for IRI record reception. Accepted input: ASCII: all characters except comma (. Accepted characters: decimal digits and dots. Presentation selector. maximum length: 24 characters. double quote (“). length: 1 to 38 digits. Maximum input: 25 digits. length: 1 to 38 digits. Input format for Hexadecimal: 0-9. It identifies the presentation layer (OSI layer 6). It identifies the session layer (OSI layer 5). tab stop and blank. Mandatory parameter with a maximum of 32 characters. All characters are accepted except backslash (\). 3.).3 LEA communication parameters The following forms are only visible if a profile has been defined for Siemens Fixed (e. IRI records per FTP User ID. double quote (“). EWSD. The form also contains the OSI parameter input fields for configuring FTAM. You have to enter the same password that has been specified on the LEA terminal. Mandatory parameter with a maximum of 32 characters. A30828-X9410-B082-35-7619 105/185 . You have to enter the same user ID that has been specified on the LEA terminal.LIOS V8. double quote (“). …). Optional parameter. IP address of the LEA terminal (LEMF) for IRI record reception. IP address. tab stop and blank. Siemens Fixed (hiQ4200/8000). hiQ/E9200). For information concerning the parameters to enter contact the administrator of the LEA terminal.2 User Manual – Administrator Issue 35 Figure 3-80: LEA data wizard – IMS. IRI record subdirectory on LEA terminal. Subdirectory on the LEA terminal (LEMF) to which IRI records will be written. Transfer protocol and authentication Figure 3-81: LEA data wizard – transfer protocol The ‘Transfer protocol’ page may not be available in LIOS Admin mode. Parameter needed for user authentication for the file transfer connection to the LEA. Siemens Mobile. all characters accepted except comma (. Retype the password.8. Choose whether FTAM or FTP should be used as file transfer protocol for the transfer of tickets to the LEA. Alcatel Fixed or Nortel Fixed (LIM). Confirm.g.2.). The file transfer connection to the LEA will be opened with this password. Password. Mandatory parameter. all characters accepted except comma (. Parameter needed for user authentication for the file transfer connection to the LEA. The file transfer connection to the LEA will be opened with this user ID. Accepted input: all characters. It identifies the session layer (OSI layer 5). Presentation selector. except blanks. Subdirectory on the LEA terminal to which tickets will be written. the ‘FTAM selectors’ section (see below) is displayed.2 User Manual – Administrator Issue 35 File transfer mode Select either FTAM or FTP as file transfer protocol. length: 1 to 8 characters. Hexadecimal: Hexadecimal digits. Mandatory parameter. Optional parameter. Session selector. except blanks.LIOS V8. Accepted input: ASCII: all characters. session and presentation selectors in accordance with the LEA. The file transfer connection to the LEA will be opened with this user ID. 106/185 A30828-X9410-B082-35-7619 . If you select FTAM. Transport selector. FTAM selectors (only when FTAM is selected as file transfer mode) Figure 3-82: LEA data wizard – FTAM selectors The FTAM selectors are mandatory OSI parameters for the FTAM communication. Password. Maximum length: 20 characters.11. You have to enter the same user ID that has been specified on the LEA terminal. digits. Retype the password.) Ticket subdirectory on LEA terminal. except blanks. except blank. Parameter needed for user authentication for the file transfer connection to the LEA. Confirm password. Authentication User ID. Hexadecimal: Hexadecimal digits. Accepted input characters are capital and small letters. Hexadecimal: Hexadecimal digits. Accepted input: all characters. length: 1 to 8 characters. It identifies the presentation layer (OSI layer 6). which you have to fill in. The file transfer connection to the LEA will be opened with this password Maximum length: 20 characters. Accepted input: ASCII: all characters. (As regards active/passive FTP. underscore and dot. Mandatory parameter. You have to enter the same password that has been specified on the LEA terminal. Mandatory parameter. length: 1 to 16 digits. see 4. Accepted input: ASCII: all characters. length: 1 to 8 characters. length: 1 to 16 digits. It identifies the transport layer (OSI layer 4). minus (-). Parameter needed for user authentication for the file transfer connection to the LEA. Mandatory parameter. length: 1 to 16 digits. Specify the transport. incl. 4 digits max. (If non-printing characters are involved. A-F. APQ (application program qualifier): 4 digits max. Input format for ASCII: all printable characters.25. Value range: for 1st component: 0. Transport system The Transport System form contains details concerning the transport mechanism and the connection to the LEA (OSI layers 1-3). AEQ (application entity qualifier). Select ASCII mode or Hexadecimal mode. The application entity title consists of application title and AEQ. You can also switch to the other editing mode if the selector fields have already been filled in – the character strings are instantly converted. It contains system title and APQ The system title contains an object identifier consisting of decimal numbers separated by dots (. 1. value range: 0 to 9999999. The port number is automatically set to default.2 User Manual – Administrator Issue 35 Selector editing.LIOS V8. switching between editing modes may not work. a-f. Application title (or application process title). Maximum lengths: 68 characters. As regards the transport system.). Mandatory parameter. space. These details have to be provided by the LEA. The appropriate input fields will be displayed. A30828-X9410-B082-35-7619 107/185 . parameters should be linked with &.) FTAM application entity title The application entity title uniquely identifies an application (here FTAM) within the system (OSI layer 7). for 2nd component: 0 to 39. Parameter for IP Figure 3-83: LEA data wizard – transport system (IP) IP address. Optional parameter. IP address of the LEA. 2. Input format for Hexadecimal: 0-9. you can choose between IP and X. 25). NSAP (network service access point) fields AFI. Domain-specific part. has to be specified in accordance with the LEA. connection problem). 108/185 A30828-X9410-B082-35-7619 .LIOS V8. Maximum input: 14 digits if AFI is set to 36. only decimal digits are allowed. LIOS will make further attempts. DSP. Length of time (in hours) during which file transfer attempts will be made. If AFI is set to 36 (NSAP for X. Waiting time (in minutes) before another file transfer will be attempted.25 address for routing. the DTE address is automatically copied into the IDI field of the NSAP address.25 address format.25 Figure 3-84: LEA data wizard – transport system (X.g. If you press the ‘Tab’ key after entering the DTE address. IDI. The communication settings control the transfer to all LEAs. Specifies the X. Mandatory parameter. If AFI is set to 44 (NSAP for ISDN). The window size is always fixed at 7 and the packet size is always fixed at 1024. the fixed length for the IDI field is 14 and the maximum length for the DSP field is 24.25). In the Communication Settings form you can set timers and counters for the transfer of LI tickets in case of error. Address facility identification (enter 36 for X. settings for individual LEAs are not possible. Range: 1 to 100. the IDI field is ignored and the maximum length for the DSP field is 38.3 Communication settings If the sending of LI tickets to LEAs fails (e. Range: 1 to 70. Mandatory parameters.25) DTE (data terminal equipment) address.2 User Manual – Administrator Issue 35 Parameters for X. otherwise 15 digits. Ticket time period (hours). Ticket retry timer (min). 3. Initial domain identifier. 44 for ISDN address format or 48 for local X.8. If AFI is set to 48. the fixed length for the IDI field is 15 and the maximum length for the DSP field is 23. Back. in most cases. Print. that the modification has not taken effect on all NEs/OS servers so that there are different versions of the LEA at the same time.3. After that the LEA will most likely not be in Consistent state. however. LEA modification command state. The repair operation is stopped – no more MML commands regarding the current LEA modification will be sent to the NE/OS server. The LEA modification command is waiting for being processed by the NE/OS server.LIOS V8. The ‘Check LEA modification’ command enables you to perform a check and.4 Check LEA modification A LEA modification affects all NEs/OS servers on which there are observations that regard the LEA (an MML command is sent to all NEs/OS servers involved). The LEA Administration main page is displayed again.2 User Manual – Administrator Issue 35 Figure 3-85: Communication Settings form (LEAs) 3. A30828-X9410-B082-35-7619 109/185 .1. Figure 3-86: Check LEA modification Commands Repair. offers you a repair operation. With ‘Abort’ you can cut off the current LEA modification operation when it has become obvious that it will not solve the problem.8. For the commands Refresh. Export and Help see ‘general application commands’ in Section 3. It can happen. Abort. Table columns NE/OS server name. States: Waiting . Name of NE or OS server on which there are observations assigned to the LEA. A repair operation is started – the LEA modification is repeated on the NEs/OS servers where it has failed.1. State in which the LEA modification command is on the NE/OS server. Up to 15 LI-specific closed user groups (LI CUG) can be set up on EWSD. Select/unselect all.1. if all have been selected previously. Records will only be deleted upon confirmation. The percentage displayed reflects the progress of the operation (successful or unsuccessful). The LEA modification has failed. If the reason is given. . The CUG data form (see 3. . it cannot be deleted. hiQ/E9200 and MSC). Figure 3-87: LEA Administration: CUGs Application commands New CUG. Delete CUGs. Selected CUGs are deleted. All records in the table are selected (checkboxes in the first column) or. they are unselected. a repair is normally possible. If a CUG still has LEAs assigned to it. Setting up LEAs in CUGs protects them from interception and from being intentionally blocked by external calls. A LEA can be a member of only one CUG per profile (EWSD.3. Export and Help see ‘general application commands’ in Section 3. Print. hiQ/E9200 and MSC switches. View reason. Up to 99 closed user groups can be set up on an Alcatel S12 switch.LIOS V8. For Utimaco IMS. where you can enter the data for the new CUG to be set up. For the commands Refresh. 3. Reason why LEA modification on the NE/OS server has failed. Actions. OK Failed . ‘Processing’ refers to the state of a LEA modification on the NE/OS server.2 User Manual – Administrator Issue 35 Checking LEA state checked now. The current LEA state was received from the NE/OS server and will be Processing.1.9 LEA Administration: CUGs The CUGs sub-application of the LEA Administration enables you to administer closed user groups (CUGs) for LEAs.1) is opened. Before you can use this command. 110/185 A30828-X9410-B082-35-7619 . These actions affect only the individual record. LEAs can be set up in CUGs to allow delivery of intercepted voice data. you must select one or more CUG records. The LEA has been successfully modified on the NE/OS server.9. The LEAs contained in the selected LI CUG are displayed. Remark. CUG name.1 CUG data form To open the CUG data form. it does not contain all details.2). a LEA cannot be assigned to an LI CUG because on Alcatel S12 the observation itself is assigned to an LI CUG.2 User Manual – Administrator Issue 35 Table The table provides you with an overview of CUG information. CUG parameters Figure 3-88: LEA Administration: CUG parameters A30828-X9410-B082-35-7619 111/185 . NE type for which the LI CUG can be used.9. To assign a LEA to an LI CUG.1) is opened. With regard to Alcatel S12.8. 3. Display LEAs. The CUG record is deleted. Delete CUG. Actions. These actions affect only the individual record. The CUG data form (see 3. select ‘new CUG’. click on the CUG name (hyperlink) in the first column. The CUG name cannot be changed – the corresponding field is read-only. NE type. Table columns CUG name. Remark entered. It contains the values of the selected CUG record. where you can modify the CUG record. You can modify these values – at least you have to enter a new CUG name. modifying and copying LI CUG records. start the LEA data wizard (see 3.9. ‘modify CUG’ or ‘copy CUG. The CUG data form is provided for creating. Modify CUG.LIOS V8. For a detailed view. The CUG data form is opened. Copy CUG. For Alcatel S12: not used. MSC and Utimaco IMS: Mandatory parameter. 1 to 9999. For Utimaco IMS mandatory. which concern LIOS itself. 3. The CUG parameters vary depending on the NE type. EWSD. EWSD. hiQ/E9200 and MSC: Optional parameter. Remark. Name of LI closed user group.10 About alarms 3. CUG name. CUG NE type. Decimal number. NE-specific parameters. all characters incl. It can also include a comment (annotation) written by a LIOS user. Alcatel S12 and Utimaco IMS: not used.2 User Manual – Administrator Issue 35 The format of the entered data specifies for which NE type the LI CUG can be used. Range: 0 to 65535 (EWSD and hiQ/E9200). CUG interlock code. CUG data network ID. EWSD. CUG index. Alcatel S12: not used. All other alarms refer to operator groups and are therefore called group alarms. Select an NE type for the CUG. 1 to 65535 (Siemens Mobile and Utimaco IMS). LIOS alarms that do not refer to a specific observation or LIOS operator group are so-called global alarms. The alarm code is organized as follows: 112/185 A30828-X9410-B082-35-7619 . MSC and Utimaco IMS: 15 characters max.2). which contains a short text and a description (= long text). which are sent by an NE. range: 1 to 15. Optional parameter. If the LI CUG satisfies validation conditions for all NE types. Alarm format An alarm consists of an alarm code and an alarm text.10. The following conditions apply to the specific NE types: To assign members to a closed user group. and LIOS alarms. Whether an LI CUG index can be used. Closed user group index. hiQ/E9200 and MSC: Mandatory parameter.. They can be also viewed with the Alarm browser. Mandatory parameter. Mandatory parameter. which can be viewed in the Alarm browser. 2 characters max. CUG DNIC. hiQ/E9200.8. decimal numbers. use the Observation form. this entry is without any effect. then it can be used without constraints by all observations. Closed user group data network identification code for the call content connection between the intercepting NE and the LEA’s access.1 LIOS alarm concept Alarm categories The LIOS alarm concept distinguishes between LI NE alarms. depends on the configuration of the NE. hiQ/E9200. CUG ILC. special characters accepted.LIOS V8. EWSD. If no call content connection is established. Alcatel S12: 8 characters max. The LI CUG name must be unique in the LIOS system. Closed user group interlock code for the call content connection between the intercepting NE and the LEA’s access. of the LEA data wizard (see 3.. Maximum length: 50 characters. range: decimal number. The CUG name must be unique in the LIOS system. If some types of LI NE alarms are not to be processed by LIOS. is the individual instance of an alarm. Alarms of these types will not be written to the LIOS database. A30828-X9410-B082-35-7619 113/185 . Attention: this should be done only by authorized personnel. The 1st letter (main group) identifies the originating system: O for operation system (= LIOS) alarm E for NE alarm (E stands for EWSD. hiE/Q9200 and Alcatel S12) H for NE alarm (H stands for hiQ4200/8000) L for NE alarm (L stands for LIM) M for Mediation Device alarms (M stands for MD) S for NE alarm (S stands for IN) The 2nd letter identifies the origin of the alarm: I for Interception The 3rd letter (subgroup) is reserved for future use. Alarm and alarm type In a LIOS context there is a difference between alarm type and alarm. they can be selectively excluded. on the other hand. Alarm number A sequential numbering of alarm types of the same main group (five digits).2 User Manual – Administrator Issue 35 Format: A-BBB-NNNNN Alarm number Subgroup I for interception Main group Alarm origin A for alarm Alarm origin The alarm origin is identified by three letters. An alarm. Chapter 4. what is specified by the alarm code is the alarm type.LIOS V8. it contains generation date and time and a sequential identification number (alarm ID). For details see the LIOS User Manual – Administrator. Strictly speaking. Contact the NE system administrator.3. they refer to a specific observation or LIOS operator group (a LIOS operator can only view group alarms that address his own group). the NE is locked.1 LI NE alarms LI NE alarms are generated by the NEs (not by all NE types) and concern the LI functionality of the NE.10. The error underlying the alarm was corrected. The name of the LIOS user appears in the Responsible field. An alarm has occurred but no LIOS user has dealt with it yet. Figure 3-89: Changes of alarm states Open. i. The alarm is being dealt with by a LIOS user.e.1. User data transmission problems: CUG error. LEA connection failure. To change the alarm record layout.10.10.2 User Manual – Administrator Issue 35 3. The LI NE alarms that are of interest to LIOS are mentioned in the following chapters. Contact the NE system administrator. A30828-X9410-B082-35-7619 . the EWSD LI options have to be modified.e. they may have been precluded on system level from being processed by LIOS (for details see the LIOS User Manual – Administrator. The name of the LIOS user appears in the Responsible field. NOTICE REGARDING EWSD V17 and V18 ALARM RECORD LAYOUT: EWSD V17 and V18provides a new alarm record layout in addition to the old one. 3.2 Alarm states open 1 3 in progress LIOS user* name 2 closed LIOS user* name ) * Can be different users. LEA is busy. the LIOS user has taken over the alarm (1). Exceptions are A-EIM-00002 (‘Massive DN modification’) and A-EID-00008 (‘LI database lost’). 3.LIOS V8. Please launch the Observation Manager and effect DB Alignment. they reach all LIOS operator groups. the LIOS user responsible has closed the alarm (2 and 3). Most LI NE alarms are group alarms.10. Section 4.3 Alarm categories 3. Closed. LIOS can receive and handle alarm records of the new and the old layout. Contact the NE system administrator.6). Contact the NE system administrator. hiE/Q9200 and Alcatel S12 Alarm code A-EIA-00010 A-EID-00008 Short text No answer from LEA LEA busy LEA connection failure LI database lost A-EIG-00005 CUG error A-EIB-00009 A-EIC-00011 114/185 Long text No answer from LEA. i. All LI data is lost.3. which are global alarms. If certain LI NE alarms are not shown in the browser. In progress.1 LI NE alarms from EWSD. Site not found. Intercepted subscriber deleted/removed. To synchronize the NE and the LIOS databases (i. ADD command on switch failed SURV ACT command on switch failed SURV DEACT command on switch failed 115/185 .10. Switch changes state from Suspended or Soft Isolation to Ready. User data transmission problems: COLP error. Contact the NE system administrator. No new call is triggered. New multiple subscriber number (MSN).Site is not of the Type DN ADD command on switch failed SURV ACT command on switch failed SURV DEACT A30828-X9410-B082-35-7619 Long text Unknown NE Unknown DN No answer from LEA LEA is busy LEA connection failure LI database lost CUG error DN modification Lack of resources New location for DN Massive DN modification New MSN creation COLP error DN removed LEA setup failure User-to-User3 overflow NE currently not reachable Line equipment number . Contact the NE system administrator. The observations concerned are still active on the NE. Until the synchronization has finished. the NE is locked for any other operation.Site not found CLLI not found Line equipment number . Switch LI database is not cleared. Table 3-2: NE LI alarms from EWSD.e. CLLI not found Line equipment number .1.Site is not of the Type DN.2 LI NE alarms from LIM Alarm code A-LIM-01000 A-LIM-01001 A-LIM-01101 A-LIM-01102 A-LIM-01103 A-LIM-01104 A-LIM-01105 A-LIM-01106 A-LIM-01107 A-LIM-01108 A-LIM-01109 A-LIM-01110 A-LIM-01111 A-LIM-01112 A-LIM-01113 A-LIM-01114 A-LIM-01201 A-LIM-01202 A-LIM-01203 A-LIM-01204 A-LIM-01205 A-LIM-01206 A-LIM-01207 Short text Unknown NE Unknown DN No answer from LEA LEA is busy LEA connection failure LI database lost CUG error DN modification Lack of resources New location for DN Massive DN modification New MSN creation COLP error DN removed LEA setup failure User-to-User3 overflow NE currently not reachable Line equipment number . For details contact the NE system administrator. Contact the NE system administrator. Switch changes state to Soft isolation. update the subscriber numbers in the LIOS database) start the Observation Manager and effect DN Synchronization. User data transmission problems (lack of resources).LIOS V8. hiE/Q9200 and Alcatel S12 3. The observation is still active.2 User Manual – Administrator Issue 35 Alarm code A-EII-00003 Short text DN modification A-EIK-00007 Lack of resources A-EIL-00001 New location for DN A-EIM-00002 Massive DN modification A-EIM-00004 New MSN creation A-EIO-00006 COLP error A-EIR-00000 DN removed A-EIS-00012 A-EIU-00013 A-EID-00014 LEA setup failure User-to-User3 overflow Soft isolation A-EID-00015 Activate switch Long text Modification of subscriber number. General LEA setup failure.3. Contact the NE system administrator. Intercepted subscriber has new location on the NE. The state of the observation has been set to ABORTED. The state of the observation has been set to ABORTED. User-to-User3 overflow. Contact the NE system administrator. Massive modification of subscriber numbers. but calls in progress are not affected. Site NE reports error Connection to LIOS lost Internal LIM Error LISTObservation command on switch failed Observation is not active Long text DEL command on switch failed Connection to NE failed (Config Error) Too may observations on this NE DN does not match Line equipment number . The Mediation Device has detected an error during execution of a message.10.3.1. The Mediation Device has detected awarning during execution of a message.1. NE reports error Connection to LIOS lost.Site.10.3 LI NE alarms from HiQ4200/8000 Alarm code A-HIQ-00001 Short text Switch can not establish call content link towards LEA Long text It is not possible to set up CC link towards LEA.10.3.5 LI NE alarms from Mediation Device (Siemens IP) The following LI NE alarms for Mediation Device are supported: Alarm code A-MIP-00090 A-MIP-00091 A-MIP-00092 A-MIP-00093 Short text Mediation Device critical error! Mediation Device – error! Mediation Device warning Mediation device LI info Long text The Mediation Device has detected an critical error during execution of a message.3.2 User Manual – Administrator Issue 35 Alarm code A-LIM-01208 A-LIM-01209 A-LIM-01210 A-LIM-01211 A-LIM-01212 A-LIM-01213 A-LIM-01214 A-LIM-01215 A-LIM-01216 Short text command on switch failed DEL command on switch failed Connection to NE failed Too may observations on this NE DN does not match Line equipment number . A failure reason is provided in alarm description Table 3-4: NE LI alarms from hiQ4200/8000 3.4 LI NE alarms from IN@vantage The following IN NE alarms are supported: Alarm code A-SIN-00001 A-SIN-00002 Short text Too many observations Forbidden attempt detected Long text The maximum number of administrated observations has been reached. This can result in inconsistencies in the database. some StatusObervation failed Internal LIM Error LISTObservation command on switch failed Observation is not active anymore Table 3-3: NE LI alarms from LIM 3.LIOS V8. Table 3-5: LI NE alarms from IN@vantage 3. The Mediation Device has sent LI interface relevant information Table 3-6: LI NE alarms from Mediation Device (Siemens IP) 116/185 A30828-X9410-B082-35-7619 . The cache configuration differs from the actual one.1. they reach LIOS operators of all operator groups.1 LIOS alarms LIOS alarms are generated by the LIOS system. The reason could be that the LI observation was not administered through LIOS. Important message sent from ticket routing service. i. File transfer has been started to retrieve the ticket buffer file. Most LIOS alarms are global alarms. if necessary. which is a group alarm. however. update the respective NE communication data or. If a default LEA has been specified. LIOS alarms are the following: Alarm code A-OIF-00001 Short text File transfer connection error A-OIF-00003 Ticket file transfer error A-OIF-00004 MC file sending error A-OIF-00007 LEA data not found A-OIF-00008 Observation has been aborted LI observation unknown A-OIF-00009 A-OIF-00011 A-OIF-00012 A-OIF-00013 Ticket buffer file detected Ticket buffer file transfer OK File transfer error from/to NE A-OIF-00014 Unknown NSAP received A-OIF-00015 Observation group authorization failed Important ticket routing message Received ticket file cannot be saved into LIOS Ticket file cannot be created A-OIF-00016 A-OIF-00017 A-OIF-00018 A-OIF-00019 A-OIF-00020 A-OIF-00021 Problem with processing of the observation Security activation problem. Information: the ticket buffer file was successfully transferred from the NE and will be processed.1.2 User Manual – Administrator Issue 35 0. A remote system tries to connect to a LIOS server through the LID application by sending an NSAP (network service access point).e. contact the NE system administrator. File transfer to LEA has failed. This file cannot be handled as ticket and was moved into the ERROR directory (/opt/li/data/ERROR-files) Ticket file that should be sent to the LEA cannot be created. See Archived Observations for more details. This can happen when the LIOS and the NE databases are not in line or when LIOS has received an LI ticket of an observation which has not been created by LIOS Observation state has been changed to Aborted. has wrong file name or it is not a ticket file. Could not identify NE.25 parameters. LEA data not found in database (LEA data inconsistency): the received LI ticket (LI record) contains a DNREC (DN of the record connection) which cannot be related to any LEA entry in the database. The file transfer from the NE ended with an error. Please check the transfer protocol of the LEA (LEA Administration). Make sure that user ID and password used for file transfer are correct. Enter the correct password. LIOS received data from an unknown NE. There is a problem with the security activation on the switch. If the parameters are correct. For further instructions see also the LIOS Trouble-Shooting Guide. If you need help. Please check the transport system and OSI parameters for the specified LEA (LEA Administration). The ticket file received by LIOS is either corrupted. An LI ticket (LI record) was received which refers to an LI observation which cannot be found in the database. For further analyses see also the LIOS TroubleShooting Guide. If the NSAP is valid. If the parameters are correct. check whether the FT responder on the remote system (NE) is available. the LI ticket is routed to this LEA. The NSAP. A30828-X9410-B082-35-7619 Long text File transfer connection to the LEA failed: received LI tickets (LI records) could not be transferred to the LEA because of a connection error. See the observation details to identify possible problem. Make sure that user ID and password used for file transfer are correct. Ticket mediation failure or insufficient filesystem permissions prevents the file creation.LIOS V8. Please perform the activation manually. Observation group (OBSGRP) password is invalid. Start the observation check or repeat the action if necessary. One of the MML commands required for the observation has failed. owing to errors detected during the running of LIOS itself. Probably some NE has not 117/185 . the OSI parameters and the user authorization parameters of the FT application for the specified NE (Host Administration). check if the responder on the remote system (LEA) is available. add a new NE entry. An exception is A-OIF-00008 (‘Observation error’). Please check the X. An LI ticket buffer file ('ticket file') has been detected on one NE.1. File transfer failed to send file to MC. Please check the transport system parameters of the MC (MC Administration). cannot be identified within LIOS. LIOS alarms have the letter O (standing for ‘operation system’) at the second position of the alarm code. Please check if all NE communication data for the LID application is administered correctly. Observation was inconsistent between NE and LIOS. Distributed write error: write operation to all DBs failed. One or more child observations of a network observation were not successfully created. Please resolve problem. retry suspend. Switch LIOS back to double mode! Consult the LIOS Trouble-Shooting Guide for instructions.25 link on the LIOS servers as described in the LIOS Trouble-Shooting Guide LIOS has switched to single database mode. In-doubt distributed transaction was detected and forced either commit or rollback. Please perform the observation check on all undefined child observations and try again. For instructions see the LIOS Trouble-Shooting Guide. Contact the LIOS administrator. Long lasting lock was detected. X. Please contact the LIOS program vendor to obtain a new LIOS license. Alarm for testing purposes. Creation and modification of observations is not possible because LIOS license entries were modified. Not enough disk space. To find out whether the problem was automatically resolved by LIOS. Your LIOS license has expired. Audit. One or more child observations are in Undefined state. X. Start the Admin Console and set the NE to 'LIDB lost' state. Frozen database session was detected and automatically resolved by LIOS.2 User Manual – Administrator Issue 35 Alarm code Short text A-OIJ-00014 General Job Server failure. General Job Server failure. You have exceeded the scope of the LIOS license. Possible problem with database replication detected. The observation state was not successfully updated owing to a database problem. Otherwise after 20 days creation and modification of observations will no longer be possible.25 link state changed LIOS switched to single database mode Distributed write error A-OIX-00001 A-OIX-00002 A-OIX-00004 A-OIX-00007 A-OIX-00009 A-OIX-00013 A-OIX-00014 A-OIX-00015 A-OIX-00016 A-OIX-00017 A-OIX-00018 A-OIX-00019 A-OIX-00022 A-OIX-00030 Test alarm Not enough disk space Connection request rejected by NE LIOS is running in single database mode Observation inconsistent between NE and LIOS Database replication warning Long lasting database lock detected Frozen database session detected In-doubt distributed transaction detected Reboot of computer LIOS license was modified A-OIX-00031 LIOS license was not found A-OIX-00032 LIOS license exceeded A-OIX-00033 LIOS license expired A-OIX-00043 DB synchronization failed Suspend failed during sending of ENTROBSID command Not enough swap space Unauthorized access Modification of network observation failed Cancellation of network observation failed Creation of network observation failed Takeover of network observation failed Update of the observation failed Modification of an network observation A-OIX-00044 A-OIX-00045 A-OIX-00050 A-OIX-00051 A-OIX-00052 A-OIX-00053 A-OIX-00054 A-OIX-00055 A-OIX-00056 118/185 Long text configured IP address correctly. Please check the X. One or more child observations of a network observation were not successfully taken over. Contact the LIOS administrator to solve the problem. You have 20 days to contact the LIOS program vendor and upgrade the license. The connection request sent to the NE was rejected by the NE because of a wrong parameter concerning the Application layer. One or more child observations of a network observation were not successfully canceled. Please check the observation. see the alarm details. Computer was rebooted. Switch LIOS back to double mode! For instructions see the LIOS Trouble-Shooting Guide. LIOS is running in single database mode. DB synchronization failed. For more in-detail information please refer to the DB synchronization report. You can cancel these child observations explicitly.LIOS V8. Contact your LIOS administrator! An unauthorized access was detected. One or more child observations of a network observation were not successfully modified. A30828-X9410-B082-35-7619 . Otherwise. Not enough swap space. Creation and modification of observations is not possible because LIOS license entries were deleted. Creation and modification of observations is not possible. Please contact the LIOS program vendor and have the license upgraded.25 Link state changed. Consequently the observation data or state kept in LIOS was modified to match the observation on the NE. Please contact the LIOS program vendor to obtain a new LIOS license. Please check the corresponding Application Entity Title of the OSI data (Host Administration). ID and Group passwords might be lost. 10. It is not possible to change modified parameters on the switch. Please modify HI2 processing server of LEAs so that it corresponds to other LIOS server. FTP. The LIOS alarm concept (see 3. CUG The MC cannot be deleted. Account is locked. Please repeat the modification. e. The login to the IMS has failed. FTP. 'It is not possible to change modified parameters on the switch. The login to the IMS has failed.g. It is not possible to receive alarms and notifications on one LIOS server.11 Alarm browser The Alarm browser can be used to view all alarms and to document the processing states of alarms (see 3. Please see alarm description for alarm details. The same subscriber is already intercepted by another LEA. Please repeat the modification. Wrong user or password.g. It is not possible to received tickets on one LIOS server. Change HI1 processing server for NEs (in Huawei Fixed profile). The same subscriber is already intercepted by another LEA. It is not possible to receive tickets on one LIOS server. but the feature has not been enabled. please check the states of the External Alarming processes. CUG The MC cannot be deleted. Please modify HI1 processing server of NEs so that it corresponds to other LIOS server. The corresponding External Alarming Identifier is unknown in the External Alarming application and the state for this External Alarming Identifier is set to inactive.LIOS V8. Huawei CC08 switch has generated an alarm. Table 3-7: LIOS alarms 3. which concern LIOS itself. Wrong user or password. A30828-X9410-B082-35-7619 119/185 . Execution of the command would require a optional freature on the IMS. The connection to the External Alarming application failed.2 User Manual – Administrator Issue 35 Alarm code A-OIX-00057 A-OIX-00060 A-OIX-00061 A-OIX-00071 A-OIX-00100 A-OIX-00101 A-OIX-00102 A-OIX-00103 A-OIX-00104 A-OIX-00200 A-OIX-00201 A-OIX-00202 A-OIX-00203 A-OIX-00204 A-OIX-00205 A-OIX-00207 A-OIX-00200 A-OIX-00201 A-OIX-00202 A-OIX-00203 A-OIX-00204 A-OIX-00205 A-OIX-00207 A-OIN-01001 Short text cannot be performed Observation does not exist on the switch.1) distinguishes between LI NE alarms. MC is still in use. The login to the IMS has failed. and the maximum number of concurrent interceptions has been reached. Execution of the command would require a optional freature on the IMS.10. and the maximum number of concurrent interceptions has been reached. External Alarming Identifier <name> is unknown in External Alarming Transfer error to External Alarming. The maximum number of intercepted targets for this IMS LEA has been reached. Please contact the External Alarming Administrator to check the name. The maximum number can be changed by the IMS administrator or choose a new IMS LEA name.2). The new pasword violates the IMS password rules. The new pasword violates the IMS password rules. MC is still in use. The maximum number of intercepted targets for this IMS LEA has been reached. Account is locked.'. Change call data IP address Alarm from Huawei CC08 switch. Jetty HTTP server could not be started. which are sent by an NE. Modification of parameters of MCCFG entity failed. e. The maximum number can be changed by the IMS administrator or choose a new IMS LEA name. and LIOS alarms. Change HI2 processing server for LEAs (in Huawei Fixed profile). Modification of parameters of MCCFG entity failed. Modification of general parameters failed. but the feature has not been enabled. Multiple interception impossible Too many subscriber for this IMS LEA New password not allowed Login failed User locked Feature not enabled MC in use Multiple interception impossible Too many subscriber for this IMS LEA New password not allowed Login failed User locked Feature not enabled MC in use HTTP Server not started Long text Observation does not exist on the switch. Please modify call data IP address of LEAs so that it corresponds to other LIOS server. The login to the IMS has failed. 1) is set to ‘In progress’ and your user name will appear in the ‘Responsible’ field.11.10. A filter form appears. the data displayed reflects the default filter settings.1 Alarm browser: Alarms When you start the Alarm browser. the Alarm browser is opened. In fact. If you wish to see another selection of data.LIOS V8. Viewing and handling of all global alarms and group alarms (see 3. Figure 3-90: Alarm browser. you are alerted instantly by an exclamation mark ( ) appearing at the bottom left. If high-priority alarms occur. All LIOS users will be reminded as long as high-priority alarms (‘VIP alarms’) are still pending (i. In the Alarm types sub-application (see 3. You can apply this command to alarms that are in Open state ( icon) if you 120/185 A30828-X9410-B082-35-7619 . which refer to operator groups. Alarms Application commands Take over alarms. Alarm browser sub-applications Alarms. If you cannot deal with the alarms immediately and you feel disturbed by the exclamation marks appearing.10. select the Filter command from the application commands bar.11.10. Alarm Reminder. switch the Alarm Reminder off (‘Alarm Reminder on/off’ command). Alarm types. Alarm types (with alarm codes and short text).2 User Manual – Administrator Issue 35 LIOS alarms that do not refer to a specific task or operator group are so-called global alarms.1) kept in the LIOS system. where you can specify criteria for the data to be displayed. see 3. can be configured by a LIOS administrator with the ‘change priority’ command of the Alarm types sub-application. in Open state). are group alarms. the exclamation mark tells you that there are still high-priority alarms pending (i.e. in Open state or in progress). All other alarms. For an explanation of ‘alarm type’.e. Which alarm types should be covered by the Alarm Reminder. The alarm state (see 3.3) a LIOS administrator can determine which alarm types should have a high priority. If you click on an exclamation mark.1. 3. to edit the annotation. For the commands Refresh. Short text. click on the alarm ID. The icon will change to . Alarm code that identifies the alarm type (for an explanation of ‘alarm type’ see 3. A30828-X9410-B082-35-7619 121/185 . LIOS user who has taken over or closed the alarm. To read the annotation. Alarm type. they are unselected. The alarm state is changed to ‘In progress’. not only by the one identified in the ‘Responsible’ field. . These actions affect only the individual record. and define sorting options. Your user name will appear in the ‘Responsible’ field.3. No external-alarming identifier has been defined for this alarm type. the alarm was not handled by PIMS. Error. Alarm Reminder on/off. click on the Annotation ( ) icon in the Actions column. The alarm message was sent to the PIMS application for some. The alarm message could not be sent to the PIMS application. You can change the states of more than one alarm at the same time.2 User Manual – Administrator Issue 35 are about to deal with the underlying problem. where you can specify which alarms should be displayed. The alarm message was sent to the PIMS application for all external-alarming identifiers that are administered for this alarm type. where you can read and edit an annotation made to an alarm or add one yourself. Annotation. The Annotation form is displayed. Annotated. Table columns Alarm ID. Table The table provides you with an overview of alarm information. For a detailed view (Figure 3-91). Filter. Select/unselect all. Time.LIOS V8. but not for all externalalarming identifiers administered. Actions. All records in the table are selected (checkboxes in the first column) or. State. You can apply this command to an alarm that is in Open state ( icon) if you are about to deal with the underlying problem. You can change the state of Close alarms.1).1.1. A filter form (Figure 3-92) is displayed. External alarming state (optional): State of the alarm message with respect to external-alarming. Take over alarm.10.10. Note: The PIMS application has a possibility to log all messages that are sent for an external-alarming identifier. Print. if all have been selected previously. No recipient defined. The annotation is saved in the database. Partly. An annotation to an alarm can be made by any LIOS user. The alarm state is set to Closed. The external-alarming state can be: Sent. it does not contain all details. (For detailed information see 3. Brief alarm information. If the field is empty.2. Export and Help see ‘general application commands’ in Section 3. The Alarm Reminder is switched on or off. A check ( ) in this field means that an annotation has been made to the alarm. Toggle switch command.) Responsible. State of the alarm. The icon will change to more than one alarm at the same time. Date and time when the alarm was generated. You can apply this command to alarms that are in ‘In progress’ state ( icon) and Open state ( icon) where the problems underlying them have been solved. Sequential number that identifies the individual alarm instance. click on the alarm ID (hyperlink) in the first column. 2 User Manual – Administrator Issue 35 Close alarm. Figure 3-91: Alarm details 122/185 A30828-X9410-B082-35-7619 .LIOS V8. The alarm state is changed to Closed. You can apply this command to an alarm that is in ‘In progress’ state ( icon) and Open state ( icon) where the problems underlying them have been solved. 2.e. LEA name. It is possible to filter for global alarms and for group alarms of an operator group. Name of NE or OS server on which the observations were created. Operator group.2 Alarm filter If you wish to reduce the number of records to be displayed.10. LIOS server where the alarm has originated.) Responsible. If a field is empty or not selected. Law enforcement agency. A30828-X9410-B082-35-7619 123/185 .3. Sequential number that uniquely identifies the observation. State of the alarm. Alarm type. you can define a filter. Alarm code that identifies the alarm type (for an explanation of ‘alarm type’ see 3. Figure 3-92: Alarm filter For a description of general filtering functions (i. LIOS operator. • For global alarms select “system” in the Operator group field.1. it has no influence on the filtering process. LIOS user who has taken over or closed the alarm. Source. (For detailed information about alarm states see 3.LIOS V8.11.10.2 User Manual – Administrator Issue 35 3. LIOS operator group to which the observations belong.1). • For group alarms select a specific operator group in the Operator group field (only the alarms of the selected operator group are shown). Observation ID. functions that are common to most LIOS filter forms) and push buttons see 3.1. NE/OS server name. LIOS operator who ‘owns’ the observation.State. Figure 3-93: Alarm browser: Alarm types Application commands Change priority. you. LIOS operators and supervisors will be informed immediately when an alarm of this type occurs and reminded as long as it is pending (i. Table The table provides you with an overview of alarm type information. If you wish to see another selection of data. Filter. they are unselected. the data displayed reflects the default filter settings. For the commands Refresh. select the Filter command from the application commands bar. Export and Help see ‘general application commands’ in Section 3. 124/185 A30828-X9410-B082-35-7619 . in Open state).3 Alarm browser: Alarm types In the Alarm types sub-application. If an alarm type has high priority. in Open state or in progress): an exclamation mark ( ) appears in the user’s browser window. a LIOS administrator can determine which alarm types should have a high priority. Select/unselect all. A filter form (Figure 3-95) is displayed.e.2 User Manual – Administrator Issue 35 3. it does not contain all details. All LIOS users will be reminded as long as high-priority alarms (‘VIP alarms’) are still pending (i.11.1. All records in the table are selected (checkboxes in the first column) or. where you can specify criteria for the data to be displayed. where you can specify which alarm types should be displayed.3. Print. click on the ID (hyperlink) in the first column.e. When you start the Alarm browser (Alarm types).1. For a detailed view (Figure 3-94). Toggle switch command.LIOS V8. A filter form appears. if all have been selected previously. The priority of the alarm type is changed from high to low and vice versa. and define sorting options. LIOS V8.2 User Manual – Administrator Issue 35 Table columns Alarm type. Alarm code that identifies the alarm type (for an explanation of ‘alarm type’ see 3.10.1). Short text. Brief alarm information. High priority. A check mark in this column indicates that the alarm type has high priority: High-priority alarms are covered by the alarm reminder. Actions. These actions affect only the individual record. Change priority. Only for LIOS administrators. Toggle switch command. The priority of the alarm type is changed from high to low and vice versa. By clicking on the Alarm type in the Alarm browser the details of the alarm type are shown. Figure 3-94: Alarm type details Alarm type filter Figure 3-95: Alarm type filter If you wish to reduce the number of records to be displayed, you can define a filter. If a field is empty or not selected, it has no influence on the filtering process. Alarm type. Alarm code that identifies the alarm type (for an explanation of ‘alarm type’ see 3.10.1). Alarm category. See 3.10.3. LIOS alarms. LI alarms generated by LIOS. A30828-X9410-B082-35-7619 125/185 LIOS V8.2 User Manual – Administrator Issue 35 NE alarms. LI alarms generated by NEs. For a description of general filtering functions (i.e. functions that are common to most LIOS filter forms) and push buttons see 3.1.3.1. 126/185 A30828-X9410-B082-35-7619 LIOS V8.2 User Manual – Administrator Issue 35 3.12 MML Handling 3.12.1 MML command states State changes during the sending of MML commands 1 6 queued 2 aborted 5 canceled 4 running 3 7 finished undefined Figure 3-96: MML command states Queued. The MML command is queued in the LIOS system and waits for session establishing (1). Running. The MML command has been sent to the NE and is being processed on the NE (2). Finished (final state). The MML command has been successfully processed on the NE (3). Canceled (final state). The MML command was canceled by the NE because of some errors (e.g. invalid parameters etc.) (4). Aborted (final state). The MML command was aborted by LIOS because of a fatal error (e.g. connection problems) (5 and 6). Undefined. The communication with the NE was interrupted after the command was submitted – LIOS has not received a response from the NE. (7). 3.13 MML console In some situations you may wish to send single commands to an NE or OS; this you can do from the MML console. The commands will normally be MML commands. If, however, the communication with an NE or OS requires a different language (e.g. XML), the MML console provides commands that look like MML but that are subsequently transformed to the language required. In any case, use the MML console and use the commands provided. For information that applies to the LIOS GUI in general, choose Help from the navigation menu on the left. When you have started the MML console, you also have to connect to an NE/OS server. Choose ‘New connection’ from the ‘Quick menu’ – a selection form is displayed where you can select an NE/OS server. After that, all functions of the MML console are available. A30828-X9410-B082-35-7619 127/185 If you are dealing with an old EWSD version. A connection to another NE/OS server is set up in addition to the current connection Clear connection. All connections established will be displayed as different views in the same MML 128/185 A30828-X9410-B082-35-7619 .13. for a list of MML commands for LIOS administrators. see 3. you have to open new connections (Quick menu/New connection). Then select an NE or OS server from the list provided. you have two options: ─ Type an NE or OS server name into the ‘Selected’ field or ─ Define a filter in the ‘Filter’ field (wild-cards: ‘*’ and ‘?’) and press Reload. The MML console remains open. The form is closed and a connection for the MML console is established.13.LIOS V8. For detailed information about MML commands see the documentation of the respective NE/OS server type.2 User Manual – Administrator Issue 35 Selection form Figure 3-97: Selection form To select an NE or OS server. The ‘Allowed commands’ pull-down list contains all MML commands you can use. Finally press Next. If you wish to send MML commands also to other NEs or OSs. The currently active connection is closed. How to enter MML commands is described in Section 3. Figure 3-98: MML console From the ‘Quick menu’ you can choose the following commands: New connection.1. The MML console is closed. some MML commands do not work. Close MML console.2. ) All commands are sent within one NE/OS server session. Name of the NE or OS to which the MML command was sent. a form with the NE’s/OS’s response to the MML command appears (Figure 3-99). If you close and reopen a connection to an NE/OS server. Canceled. Date and time when the command was sent. Unique MML job identification. the table of MML commands is empty again. Sequential number given to the MML command by the coordination processor (CP) of the NE/OS server. A30828-X9410-B082-35-7619 129/185 . Actions. Time. If you click on the job ID of a command. Table columns Job ID. Not relevant.14).2 User Manual – Administrator Issue 35 console window. Not relevant. Running. If you wish to see the NE’s/OS’s response. and Aborted. The table of MML commands in the MML console window shows only the MML commands entered within one MML session. (All MML commands are also written to a log file which can be inspected by the LIOS supervisor. Group to which the operator belongs. CP ID. LIOS user who has issued an MML command via Console. Operator group.) LIOS user. State of MML command. Observation ID. the MML console table and the ‘Command history’ list are empty again.1. MML command. all previously sent MML commands are listed in the MML browser window (see 3. Finished. Table Each command you submit during the current session of the MML console is listed in the table of the MML console. click on the job ID of the respective MML command (Figure 3-99).LIOS V8. (For detailed information see 3. Name of the MML command. To switch between different connections use the ‘Connected to NE/OS server’ pulldown list. The state can be Queued.12. NE/OS server name. However. This means that after closing and reopening the MML console. State. 13. Prompting works only in connection with Siemens Fixed.2 User Manual – Administrator Issue 35 Figure 3-99: MML console.1 How to enter an MML command Type the MML command with the parameters required and a closing semicolon into the MML input line and press the Send button or the Enter key. Siemens hiE and Alcatel S12. If a command requires user interaction or if you have entered a command incomplete. the only exceptions are passwords. Siemens Mobile. 3. 130/185 A30828-X9410-B082-35-7619 . the Prompt form (Figure 3-100) appears.LIOS V8. NE/OS server response A Refresh button is provided so that the output can be dynamically updated while you are waiting for the command to finish. where the NE/OS server response is displayed and where you are informed about which parameter you should submit next. NOTICE REGARDING EWSD AND hiQ/E9200: Lower-case letters as parts of MML commands and parameters are not accepted by EWSD and hiQ/E9200. for example. If prompting does not work. the ‘Command history’ list will provide the 20 last MML commands sent to EWSD switches during the current MML console session. which contains all MML commands with parameters you have entered in the currently active view during the current MML console session. To enter a command you can also choose one from the ‘Allowed commands’ pull-down list. 3. if you do not. hiQ/E9200 and MSC ACTMOBS DISPDN ACTOSITRAC DISPEXDDAT ACTX25TRAC DISPFILE CANCUG DISPJOB CANJOB DISPLIOPT* CANMOBS DISPLNLCKOUT CANSERVCUG DISPLTG CONFX25LINK DISPMOBS CRFGRP DISPMOBSDAT DISPAPPL DISPNUC DISPAUTCL DISPOBSCALL DISPCAC DISPOBSGRP DISPCONN DISPOSIADR DISPCUG DISPPA DISPCXDN DISPPBX DISPCXPBX DISPPBXLN DISPCXPBXLN DISPPORT DISPCXSUB DISPPRO A30828-X9410-B082-35-7619 DISPSLNACC DISPSUB DISPTGRP DISPTIME DISPTRUNK DISPUSERID DISPV5IF DISPX25DTE DISPX25LINK DISPX25ROUTE DMPOSITRAC DMPX25TRAC ENDSESSION ENTRCUG ENTROBSID ENTRSERVCUG MODFGRP MODLIOPT* MODSUB MODUSERID SELMOBS SETFGRPPW STATBA STATDIU STATDLU STATDLUMOD STATDLUPORT STATLTG STATPBXLN STATPORT STATSSP STATSUB STATTRUNK STATX25DAT STOPJOB TESTSUB 131/185 .2 User Manual – Administrator Issue 35 In this way you can also have the NE/OS server guide you through the input procedure: enter the command without parameters and without closing semicolon and press Send. The ‘Command history’ and the ‘Allowed commands’ functions are NE/OS-server-type-specific: i. Siemens EWSD. you are communicating with an EWSD switch (active view). If you press Cancel. Prompting works differently with Alcatel S12 switches: you have to enter a semicolon after the command and after each parameter. Prompt form Enter the parameter prompted and press OK. or from the ‘Command history’ pulldown list.e. the command is canceled by the switch. the MML command will be canceled. Modify the browser settings. the MML commands appropriate for the switch type are provided. the NE/OS server will prompt you to enter the next parameter. Figure 3-100: MML console. This can come in handy if you are entering a complex MML command.LIOS V8.2 MML commands for LIOS administrators As a LIOS administrator you can enter the following MML commands. If. depending on the switch or OS type you are communicating with. the Web browser you are using may not allow pop-ups received from the LIOS server.13. If you enter a semicolon and press OK before you have entered all mandatory parameters. which contains all MML commands a LIOS administrator is permitted to use. which is the format used for the communication with LIM. Siemens IN@vantage TESTSCP Siemens IP mediation device CHANGEPASSWORD QUERYDCGROUPS QUERYDCGROUPPROFILE QUERYLOGFILE Alcatel S12 DISPLAY-ACTIVE-ALARMS DISPLAY-CUG KCC LIM TESTLIM This command is automatically converted by LIOS to XML.2 User Manual – Administrator Issue 35 DISPDBSIZE DISPDLUPORT DISPPSWDAT DISPSERVCUG MODOBSID* MODPSW *Not for EWSD V11. Siemens hiQ4200/8000 GETCALEAINTERCEPT GETVERSION These commands are automatically converted by LIOS to XML. Utimaco IMS MCLIST Huawei Fixed SET GP LST GP MOD HI2CFG LST HI2CFG Huawei GSM STARTLEA CLOSELEA EXITLEA TEST For detailed information about MML commands see the documentation of the respective switch or operation system. which is the format used for the communication with hiQ4200 and hiQ8000 exchanges. 132/185 A30828-X9410-B082-35-7619 .LIOS V8. 3. Table The table contains all MML commands of an Administrator user sent during current and previous sessions via MML console. The following MML commands can be available in the MML browser: " All MML commands of an Administrator user sent during current and previous sessions via MML console. Table columns Job ID. A30828-X9410-B082-35-7619 133/185 . Unique MML Job identification. CP ID. Figure 3-101: MML browser For information that applies to the LIOS GUI in general. Canceled. Print. Not relevant. If a field is empty or not selected. Export and Help see ‘general application commands’ in Section 3.LIOS V8.) LIOS user.1).14.14. Actions. LIOS user who has issued an MML command via console.14 MML browser The MML browser enables you to view MML commands. State. Operator group. State of the MML command. Running. and define sorting options. select Help from the navigation menu on the left.12. MML command. NE name. For the commands Refresh. Application commands Filter. Finished. Not relevant. Time.1. Network element to which the command was sent. Group to which the operator belongs. Observation ID. Sequential number given to the MML command by the coordination processor (CP) of the NE. (For detailed information see 3. Name of the MML command.1 MML filter If you wish to reduce the number of MML jobs displayed. Aborted and Undefined. Date and time when the command was issued.2 User Manual – Administrator Issue 35 3. it has no influence on the filtering process.1. If you click on the job ID of a command. 3. A filter form is displayed (see chapter 3. a form with the NE’s response to the MML command appears. The state can be Queued.1. you can define a filter. where you can specify which MML command records should be displayed. This filed allows filtering of jobs from console. Network element to which the command was sent. State of the MML command. NE/OS server name. functions that are common to most LIOS filter forms) and push buttons see 3.3.1 MML command states) LIOS user. Group to which the operator belongs. LIOS user who has issued an MML command via console. Command.12. Observation ID. 134/185 A30828-X9410-B082-35-7619 .e. State. MML command. MML command type.3. Not relevant. Operator group.LIOS V8.2 User Manual – Administrator Issue 35 Figure 3-102: MML filter For a description of general filtering functions (i. (For detailed information see 3.1. The LIOS EFD Administration renders the management of EFDs convenient and gives you a good overview of EFDs created on the NEs that are connected with the LIOS system. When you start the EFD Administration. To manage the communication with an NE and to set up applications for this purpose. foreign EFDs that have been taken over by the LIOS EFD Administration. EFD types LIOS EFDs.15 EFD Administration Only for Siemens EWSD and hiQ/E9200. ─ NE alarms (LI infos): alarms raised during LI functionality execution. which is prerequisite for the LIOS EFD Administration to work. LI EFDs (Event-Forwarding Discriminators) are mechanisms to be activated on some switch types (EWSD. Whether you can view and handle foreign EFDs.2 User Manual – Administrator Issue 35 3. EFDs that were not created by LIOS and that were not taken over by LIOS. LIOS is interested in two types of events: ─ Tickets (LI records): containing information related to an intercepted subscriber. LIOS EFDs always have lawful interception as their objective. use the LIOS Host Administration. hiQ 9200 and hiE 9200) for forwarding LI tickets and LI-specific alarms to LIOS or other systems. Foreign EFDs that have been created for purposes other than lawful interception can be displayed in the LIOS EFD Administration for informational purposes. the data displayed reflects the default filter settings. EFDs that have been created by the LIOS EFD Administration and are kept in the LIOS database. in this case they can be taken over by the LIOS EFD Administration. If you wish to see another selection of data. select the Filter command from the application commands bar. Figure 3-103: EFD Administration A30828-X9410-B082-35-7619 135/185 . but cannot be manipulated. depends on the functional scope of the LIOS system you are working with (license key). The Host Administration also enables you to set up the EFD application.LIOS V8. Foreign EFDs can have lawful interception as their objective (i. Foreign EFDs.e. An EFD essentially tells the NE what types of events it should forward and to which destination. A filter form appears. forwarding of LI tickets or NE alarms). where you can specify criteria for the data to be displayed. forwarding of LI tickets or NE alarms. Selected EFDs are deleted. If EFDs have got lost in the LIOS DB and are still kept on the NE. ‘Error’. select them and choose Ignore EFDs. EFDs which were created by the LIOS EFD Administration or taken over. If EFDs do not interest you. where you can enter a new EFD to be created. The EFD data wizard (see 3. they are foreign EFDs from the LIOS point of view. You will be asked if you really want to delete EFDs. The newly-created EFDs are automatically marked as LIOS EFDs – they can subsequently be administered through the EFD Administration. If you have used Ignore EFDs erroneously. Delete EFDs. invoke a Validate operation. The table provides you with an overview of EFD information. ‘DB != NE’. EFDs are set to Ignored state. Forwarded events: tickets.e. Table The EFD Administration table provides you with an overview of the EFDs that were created on the NEs set up in the LIOS system. if all have been selected previously. ‘Not in DB’. State.3). Ignore EFDs. Identifier of EFD. Export and Help see ‘general application commands’ in Section 3. Automatically generated by LIOS. i. For a detailed view. The state of an EFD can be ‘OK’. click on the EFD ID (hyperlink). You can also delete an EFD record which exists in the LIOS database but not on the NE (‘Not on NE’ state). NE alarms or both. ‘Not on NE’. Select/unselect all. As EFDs are being set up on the NEs one by one.) Forwarding. You can only delete LIOS EFDs. they become foreign EFDs and can no longer be manipulated with the LIOS EFD Administration. unique on the NE. A filter form (Figure 3-104) is displayed. Table columns EFD ID.1. ‘Ignored’ and ‘Processing’. Foreign EFDs are taken over and are henceforth LIOS EFDs – they can be manipulated with the LIOS EFD Administration as if they had been created by it.1. You are also advised through a summary message whether the creation of EFDs has been successful.e. All records in the table are selected (checkboxes in the first column) or. they are unselected. there state changes to OK or. in case of failure.15.2 User Manual – Administrator Issue 35 Application commands New EFD. Currently valid primary address to which events are sent by the NE. although they may have been created by the LIOS EFD Administration. The EFD can be created on one or more NEs at the same time. Network element where the EFD has been set up. i. Validate NEs. NE name. Fall-back target address for events in case the destination cannot be reached. Filter. Print.2) is started. Backup.LIOS V8. Discriminator ID. Take over EFDs. and define sorting options. it can be more than one address. You can recover them by using Take over.3. you can undo the action with Take over EFDs. It uniquely identifies the EFD within the entire LIOS system. it does not contain all details. where you can specify which EFDs should be displayed. Finally a message confirming the deletion is displayed. To find out what has gone wrong with individual EFDs. For the commands Refresh. If you apply Ignore EFDs on LIOS EFDs. ‘n/a’ indicates that the EFD is not a LIOS EFD. to Undefined. Active destination.15. You can apply Take over only on foreign EFDs that have Lawful Interception (LI) as their objective. (In case of foreign EFDs. 136/185 A30828-X9410-B082-35-7619 . ‘Undefined’. LIOS checks whether the EFD is consistent with the EFD currently active on selected NEs (see 3. LIOS V8. A30828-X9410-B082-35-7619 137/185 . Network element. functions that are common to most LIOS filter forms) and push buttons see 3.15. If a Validate operation has revealed discrepancies between NE and LIOS DB. The EFD is ignored. Checkbox. i.1. A checkmark indicates that the EFD is a LIOS EFD. Otherwise it is a foreign EFD. Ignore. Actions. Synchronize. Modify. State. The EFD record is deleted. ‘Undefined’. only LIOS EFDs are shown. Figure 3-104: EFD Administration – filter NE name.15. Align.3. ‘Not on NE’. If a Validate operation has revealed discrepancies between NE and LIOS DB. By setting filter criteria you can restrict the data to be displayed. You can apply Align only on LIOS EFDs.e. you can apply Synchronize if the NE data is correct and the LIOS data is faulty. For a description of general filtering functions (i.2) is started.e. Delete. The state of an EFD can be ‘OK’. through ‘Take-over’ and ‘Ignore’. ‘Error’. This field can be modified only indirectly.15. you can apply Align if the LIOS DB data is correct and the NE data is faulty. The EFD data is read from the NE and written to the LIOS database (DB). LIOS checks whether the EFD is consistent with the EFD currently active on the NE (see 3. These actions affect only the individual record.2 User Manual – Administrator Issue 35 LIOS EFD. LIOS EFDs only. it has no influence on the filtering process. where you can modify the destination and the backup destination(s) of the EFD You can only modify LIOS EFDs. ‘DB != NE’. ‘Ignored’ and ‘Processing’. EFD data is read from the LIOS database (DB) and written to the NE.2 EFD data wizard The EFD data wizard enables you to manage EFDs on all NEs set up in the LIOS system. it has lawful interception as its objective and has been created or taken over by LIOS. You can apply Synchronize only on LIOS EFDs. If a field is empty or not selected.1 Filter Select the view or views you wish to appear in the main window. 3. ‘Not in DB’. If selected. Take over. 3. Validate. The EFD data wizard (see 3.1. The EFD is taken over.3).15. 1).2. Name of target NE. It identifies the EFD on the individual NE. (Details form only) Creation date.1. ‘Not on NE’.LIOS V8. Remark. it must be unique only on the NE. partially or as a whole. Read-only field. Date and time of creation of the EFD carried out through LIOS (Details form only). Read-only field. If you are creating an EFD. (In the Modify and Details forms this field is read-only. 150 characters max. 138/185 A30828-X9410-B082-35-7619 . The state of an EFD can be ‘OK’. Accepted values: 0 and positive and negative 32-bit integers (value range -2^31-10 to 2^31-1). select one or more NEs from the ‘available NEs’ list (how to shift items between the lists with the arrow push buttons and with the Ctrl and Shift keys is explained in Section 3. Error report. Read-only field. You can add a remark here. Read-only field. ‘Error’. an error report is generated. ‘DB != NE’. ‘Undefined’.2 User Manual – Administrator Issue 35 Common EFD data Figure 3-105: EFD data wizard – common EFD data NE name. If an EFD Administration operation has failed. Date and time of the last validation of the EFD carried out through LIOS. ‘Ignored’ and ‘Processing’. Discriminator ID. ‘Not in DB’. The error report always refers to the last operation.) Last validation. State. 9202. A30828-X9410-B082-35-7619 139/185 ..1.262. Read-only field. Backup destination. Input format: decimal numbers separated by dots (e. (Some foreign EFDs can have more than one backup destination. Read-only field. Destination.1. 0. LIOS server to which events are normally forwarded: application entity title of the LID application set up on the primary LIOS server (see 3.LIOS V8. NE alarms (checkbox). Object IDs generated by the switch for EFDs. Package list. NE alarms (LI infos) are/will be forwarded through the EFD. Name binding.16).2. Read-only field.2). Input format: decimal numbers separated by dots. LIOS server to which events are being sent by the NE: application entity title of the LID application set up on the LIOS server. Object class. LI tickets (LI records) are/will be forwarded through the EFD. If selected. Read-only field.2 User Manual – Administrator Issue 35 EWSD-specific parameters Figure 3-106: EFD data wizard – parameters for EWSD and hiQ/E9200 Active destination. LIOS server (fall-back destination) to which events are forwarded if the primary LIOS server cannot be reached by the switch: application entity title of the LID application set up on the secondary LIOS server.) Tickets (checkbox).g.6. If selected. EFD attribute. EFD attribute. ‘Confirmed mode’ should always be activated. the discrepancies between an NE and LIOS DB can be as follows: 1. As regards a LIOS EFD. Enabled: the discriminator is operational 3. an annotation will be added which states that the EFD was originally kept only on the NE. Locked: processing of the information by the discriminator is prohibited by a managing system. 140/185 A30828-X9410-B082-35-7619 . an annotation will be added which states that EFD data is not identical.2 User Manual – Administrator Issue 35 Confirmed mode. 3. 2. If you wish to validate one or several EFDs. Shutting down: the EFD is not operational owing to a shutdown of the NE.15. The EFD can be in the following operational states: Disabled: the discriminator is not operational. Operational state.LIOS V8. Read-only field. If the Take-over command is available. The EFD is kept on the NE. The EFD is kept on the NE and in the LIOS database. user requests are confirmed by the NE after execution. If activated. The result is compared with the LIOS database. but its values are not identical – the Synchronize and Align buttons are available. the EFD will be entered in the LIOS database and an annotation will be added which states that the EFD was originally kept only on the NE. but not in the LIOS database – the Synchronize button is available. the LIOS database is updated. The EFD is kept in the LIOS database but not on the NE – the Align button is available. the EFD has lawful interception as its objective and can be taken over. The EFD can be in the following administrative states: Unlocked: processing of the information by the discriminator is permitted by a managing system. If you wish to invoke a global validation. Read-only field. If you use Validate on foreign EFDs. At such a global validation. Administrative state. the following actions are taken: All NEs available are asked (polling) whether they have EFDs set up on them. select them.3 Validate LIOS checks whether EFDs kept in the LIOS database are consistent with EFDs currently active on NEs. unselect all EFD records in the table. select the ‘Ticket buffer management activated’ checkbox. Press Next till you arrive at the Applications form. use the Host Administration (‘NE data’ wizard -> FT Application -> General form -> File group password).4. If ticket buffer management has been activated (see 3. 2.g. CR FSINIGRP (creation of file security initiator group. the above procedure does not apply. contact the NE administrator.TYPE=FILEPW. and for hiQ/E9200. To administer the password.e. From the MML console enter the following MML commands CRFGRP:FGRP=LI. Select FT. splits it into single tickets and processes every ticket as usual. and not via MML console. the ‘ticket file’ feature on the NE must have been activated – REC_IN_FILE must have been set in the LI properties of the NE. For each ticket buffer. In the Host Administration/NEs select Modify NE from the Actions column. To retrieve ticket buffer data from the NE.<OBSGRP>. 4.6). The interval of these polling calls can be set in the Host Administration (Communication Settings form – see 3. CR FSFGRP (creation of file security file group and files). fill in the interval of polling calls (in minutes. it retrieves it via FTAM or FTP. PLEASE ENTER AUDIT PASSWORD# enter File-Access Password 3. the FT application has to be configured. To make password administration as simple as possible. Because a maximum of two ticket buffers can be created for every OBSGRP. proceed as follows: 1.<OBSGRP>. To enable an NE to create a ticket buffer file. Enter the file group password. 5. If LIOS detects a ticket buffer file on the NE. a file group with an associated password has to be created on the NE.CYCLIC=NO.4. the following MML commands have to be entered twice (for ticket buffer LI.A002). In the ‘Ticket buffer configuration’ area of the Communication Settings form.A001 and LI. LIOS checks every hour whether a ticket buffer has been created by the NE (i. NetManager. Check if the ‘ticket file’ (= ticket buffer) feature of the NE has been activated. range: 10 to 600). If in doubt. press Modify. These are the Q3 MML commands you have to enter: CR FTINI (creation of file transfer initiator with password type at the authentication function of the NE). Press Next till you arrive at the Passwords form.<OBSGRP>.LIOS V8. For EWSD Power Node and hiQ/E9200 (file transfer via FTP). e. version V13A and higher. Choose NE/Communication settings.ACCESS=DEL&RD&WR&CN&CR. 4.1 Ticket buffer management (only for EWSD and hiQ/E9200) Only for EWSD switches.1).2 User Manual – Administrator Issue 35 4 Special working procedures ! For more detailed information and troubleshooting advice see the LIOS Troubleshooting Guide. a password is required.4.A001. A30828-X9410-B082-35-7619 141/185 . use the Host Administration (see 3.<OBSGRP>.7).A001. whether the connection was interrupted). LIOS allows only one password for all ticket buffers. SETFGRPPW:FGRP=LI. password type). tickets which cannot be sent to LIOS because of connection problems are stored in a ticket buffer (= ‘ticket file’) on the NE. For every OBSGRP. After successful data transfer the ticket buffer file is deleted on the NE. upon request of LIOS. In the ‘New NE data’ or ‘Modify NE data’ form of the Host Administration. For EWSD Classic (file transfer via FTAM). CR FSRULE (definition of a rule stating what the initiator group is allowed to do with the files of the file group). The settings have to be made according to the file access security used in EWSD Innovation – commands must be entered via Q3. To administer FTAM or FTP for an NE. the CUG functionality must be used (otherwise LI MML command ‘CROBSGRP’ will be rejected). Parameters concerning CUG administration: CUGIND (CUG index). generally a LEA can be administered in more than one CUG).e. This information is sent to the NE with a CROBSGRP command.2 User Manual – Administrator Issue 35 4. the same LI CUGs should be registered in the LIOS system (to be done in the LEA Administration. CUG data form). CUGs must be set up on NEs by an ISDN administrator. you can set them up as closed user groups (CUG). it is possible to define up to 15 LI-specific CUGs on an NE. CUGILC (CUG interlock code). • CUG_ADMIN_MAND: If this property is set. • CUG_USAGE_VIA_INDEX: If this property is set.LIOS V8. NE data forms) has to be set or not. Whether this feature can be used depends on the NE configuration.2).8. Assigning LEAs to CUGs (LIOS administration task) Each LEA can be a member of only one CUG (this is a restriction of LIOS. Code) There are three parameters for specifying a CUG for a LEA within the MML commands for creating and modifying observation groups: 142/185 A30828-X9410-B082-35-7619 .2 Setting up closed user groups (CUGs) for LEAs on EWSD and hiQ/E9200 switches To prevent LEAs from being intentionally blocked by external calls and from being objects of observation. and hiQ/E9200. To check the current values use the appropriate MML command. Setting CUGs in the LI options (NE administration task) If the CUG feature is activated (i. Up to 15 CUGs can be predefined on each NE. The value of these parameters can only be modified during installation phase. the CUGs must be set in the LI options (MODLIOPT command). Administration of CUGs for each LEA must be possible by selecting one of the predefined CUGs in the Observation form of the LEA data wizard (LEA Administration – see 3. the CUG functionality must be used with the index method. the flag ‘CUG indexing activated’ (provided in the Host Administration. A CUG for a particular LEA must be set up on the NE on which the ISDN connection of the LEA is administered. Registering LEA CUGs (LIOS administration task) If the use of LI CUGs is allowed on an NE and there are LI CUGs administered on the NE. at least CUG_USAGE_ALLOWED is set in the LI options) and the CUGs are administered on the NE. The following CUG properties can be set in the LI options: • CUG_USAGE_ALLOWED: If this property is set. CUG_ADMIN_MAND and CUG_USAGE_VIA_INDEX. the CUG functionality is allowed. Setting CUG indexing flag for an NE (LIOS administration task) Depending on the value of the LI properties CUG_USAGE_ALLOWED. To set up and administer CUGs proceed as follows: Checking CUG properties in the LI options (NE administration task) In EWSD version V13A and higher. CUGDNIC (CUG data network ident. This configuration is defined on each NE in the properties of the LI options. you have to add its number to the NeLiAlarmSetRestriction property value. set the NeLiAlarmSetRestriction property as follows: 1. is described in the example below. Each LI NE alarm type is further specified by an alarm code (e. If LIOS is to receive LI NE alarms. Therefore LIOS uses an alarm filter and processes only the alarms specified in the filter.properties configuration file. If you wish to add another alarm type number. The LI NE alarm types existing so far have alarm numbers in the range from 0 to 13. 3.g. If there is a CUG assigned to a LEA in the LEA Administration. all NE specific LI alarms are processed. Login to the LIOS server. Change to /opt/li/sw/<LIOS version>/config. a filter for these alarms can be specified in the LIOS system. Therefore a new property has been added to this file. called ‘NeLiAlarmSetRestriction’. Each LI NE alarm type has a special number. but ignores all other alarms (but in any case. 4.properties file. A-EIR-00001). an EFD must exist which forwards the alarms to LIOS. The CUG index is related to the CUG data predefined in the LI options on the NE. CUGILC and CUGDNIC: Specifying the CUG interlock code and the CUG data network identification code by using parameters CUGILC and CUGDNIC (CUGIND is not used). If there is no CUG assigned to a LEA. Modify the line so that it reads as follows: NeLiAlarmSetRestriction = 0&3&8 A30828-X9410-B082-35-7619 143/185 .3 Configuring LI NE alarm filtering (lios.2 User Manual – Administrator Issue 35 CUGIND: Specifying the CUG index by using the CUGIND parameter (CUGILC and CUGDNIC are not used). LI NE alarms not contained in this set of alarms are ignored and therefore the LIOS user is neither notified nor has he the possibility to get any information about these alarm. If the NeLiAlarmSetRestriction property is not set (default). It is not possible to determine only a special set of LI alarms to be forwarded. the CUG parameters are not used in the MML commands for creating and modifying observation groups. If a specific alarm type is to be processed by LIOS. Example: To make LIOS process only the LI NE alarms of types 0 (A-EIR-00000. For a list of all possible LI NE alarm types see 3. this CUG is specified also in the MML commands for creating and modifying observation groups: if the flag ‘CUG indexing activated’ for a specified NE is set. ! If the LEA CUGs set up in the LIOS system do not correspond with the parameters and properties set on the NE. the CUGIND parameter is used. you have to stop and restart the LIOS services. The filter can be specified in the lios. the parameters CUGILC and CUGDNIC are used. 2. The EFD can only contain the information to forward all LI NE alarms or to forward no LI NE alarm. 3 (A-EII-00003. the MML commands for creating and modifying observation groups will be rejected by the NE. if the flag is not set.LIOS V8. DN modification) and 8 (A-EID-00008.10. you have to enter a “&“ character first. For the modifications to take effect. 4. Go to the NeLiAlarmSetRestriction property.properties file) To fulfill (a possible) customer requirement to process only a special set of LI NE alarms (= LI-specific alarms issued by the LI functionality of EWSD and hiQ/E9200) and also of LIM alarms. Open the lios. 5. How to do this. which is located on the LIOS server. the receipt of alarms is confirmed by LIOS through a message sent to the NE). LI database lost). The last part of this alarm code contains the alarm type number (in the example above: 1). the command is rejected. DN removed). If no CUG data is administered in the LI options for this index. the new features are available without LIOS having to be newly set up. edit the ‘lios.6 Upgrading the LIOS license If the network provider (the owner of the LIOS license) wishes to expand the network (e. To configure Automatic DN synchronization. line begins with ‘#’) or the line has been deleted. 144/185 A30828-X9410-B082-35-7619 . If your LIOS system has two LIOS servers. These are the default settings: DBSyncJobComputer.1> Meaning Amount of time in seconds which must pass between the arrival of an alarm and the start of the synchronization. add NEs). 4. Once the license upgrade has been installed. this state synchronization is performed as a routine operation (‘Cyclic DB Synchronization’) every night. The settings controlling this routine can be modified in the LIOS properties. the LIOS license consists of the license key and the license file.e. DBSyncJobComputer. 7. state synchronization covers the states in which observations are on the NE. which reads intercepted DNs from the LI database of the NE and writes them to the LIOS database. 0 Automatic DN synchronization is not used (default). The LI software on the NE automatically changes intercepted DNs accordingly. Speaking in software terms.properties’ configuration file: Parameter AlarmService.TargetSyncDelay <seconds> AlarmService. Save the file and exit. By default. 4. so that the DNs kept in both databases are identical again. modify the ‘NeLiAlarmSetRestriction’ property as follows: NeLiAlarmSetRestriction = If the property is put under comment (i. The NE sends a ‘Massive DN modification’ alarm and the LIOS operator responsible has to effect DN synchronization. restart the LI processes on the two of them.g. covering the NEs where the last state synchronization was performed more than 7 days ago. ! Hour2Execute = 22 Minute2Execute = 00 SyncLength = 5 TimeCriteria = 7 If you modify the settings for cyclic DB synchronization. DBSyncJobComputer./liservices restart All LI processes running on the LIOS server are stopped and restarted. all LI NE alarms are processed. 1 Automatic DN synchronization is used. Indicates whether automatic DN synchronization should run after arrival of an alarm at all. an upgrade of the LIOS license may become necessary. Enter the command: . 4.LIOS V8. For the details of the installation procedure refer to the LIOS Installation Manual. DBSyncJobComputer. Default: 900.4 Configuring cyclic DB synchronization The LIOS operator is supplied with two functions for synchronizing the LIOS database with the NE database: DN synchronization and state synchronization. you have to do so on each LIOS server. LIOS can be configured to automatically start a DN synchronization operation every time it receives a ‘Massive DN modification’ alarm. DN synchronization covers modifications made to intercepted subscribers. To make LIOS process no LI NE alarms.TargetSyncAuto <0.5 Automatic DN synchronization following a ‘Massive DN modification’ alarm A massive DN modification made on an NE is likely to affect observations administered by LIOS.2 User Manual – Administrator Issue 35 6. License key and license file have to be ordered from the manufacturer and installed. Steps to be taken by the LIOS administrator 11.25) and file transfer protocol (FTP or FTAM) should be used and you have to exchange communication parameters (e. 10. If ISDN is used. . Steps to be taken by the EWSD or hiQ/E9200 administrator 8. for some reason. ISDN or IP network. Open the EFD Administration and create an EFD. Open the MML console. Example: MODLIOPT:FBQ3AL=Y. DTE or IP address and system title). (In case of inband create an EFD only for NE alarms. 13.3001. Q3 activated. 14. LIOS has not been adjusted.) 16. connect to the NE and set the LI passwords on the NE: enter the passwords as parameters of the MODOBSID command. In the LIOS Host Administration.6).262.8 Handling an EWSD / hiQ/E9200 upgrade When an EWSD or hiQ/E9200 NE which can be accessed by LIOS is upgraded.10 is the application process title of the LID application on one of the LIOS servers (it does not matter on which one). NEs sub-application.3001. In the LIOS system: The same LIOS operator who has invoked ‘Suspend NE’ now resumes all observations on the NE (Observation Manager/Resume NE). Open the LIOS Host Administration. In the LIOS system: The LIOS administrator changes the EWSD / hiQ/E9200 version (Host Administration – NEs/NE data wizard – see 3.1.7 Setting up a new EWSD or hiQ/E9200 NE in the LIOS system As a preparation you have to discuss with the EWSD or hiQ/E9200 administrator which network (WAN.10. In this case 0. 22. Steps to be taken 17. enter the connection parameters agreed upon with the EWSD or hiQ/E9200 administrator.262. .2 User Manual – Administrator Issue 35 4. Preparation of the communication database on the NE.2. 20.25. We strongly recommend that you should copy the data of an NE already set up (select ‘Copy NE’ ) and modify only the values that are different. 19. the LI database of the NE will be lost.1. On the NE: The NE administrator upgrades the EWSD / hiQ/E9200 software. configure a new WAN partner in the ISDN router (Bintec).g. ISDN). LI options. NEs sub-application.2.) 9. Preparation of the hardware connection from the NE to the X. Preparation of the LI functionality on the NE (LI patches. An ‘LI database lost’ alarm (alarm code A-EID-00008) is generated A30828-X9410-B082-35-7619 145/185 .1.4.LIOS V8. 12. ODAGEN. 18. In the LIOS system: The LIOS administrator also enters the LI NE passwords from the Host Administration. 4.4) and set up a new NE.1. Do NOT deactivate the NE! Do not re-enter EFDs! EFDs of the old EWSD version are automatically regenerated during EWSD / hiQ/E9200 upgrade.FBQ3ALN=0. If the EWSD / hiQ/E9200 NE has been upgraded and. transport system (IP or X. . a LIOS administrator and a LIOS operator (with Observation Manager rights) have to cooperate with the EWSD / hiQ/E9200 administrator. 21. select ‘Activate NEs’. Activate the new NE. LI LTG. NEs sub-application (see 3. In the LIOS system: The LIOS administrator enters the LI NE passwords from the MML console with the MODOBSID command. From the MML console adapt the LI options of the NE with the MODLIOPT command. In the LIOS system: A LIOS operator (with Observation Manager rights) suspends all observations on the NE (Observation Manager/Suspend NE). 15. 763 (i.763 – a header will be added (default). Regulates which characters can be entered in the ETSI form of the NE data wizard to specify NE IDs in the E. Parameter HostAdmin.6).25 or E.763 – a header will be added (default). the NE had version EWSD V12 or higher or hiQ/E9200 – depends also on the LI property settings). a LIOS administrator may wish to enter headers manually. If the owner of the LIOS system you are working with has purchased an ETSI license.ETSI_HexaE164 0 1 TicketRouter. However.164) The ETSI standard on Lawful Interception (ETSI ES 201 671) also regulates in which format data has to be contained in LI tickets.164 address and will leave the 2-byte header according to ETSI to be added by the LIOS system. which necessitates the input of hexadecimal characters. you have to fill in the fields in the ‘NE ID’ section of the ETSI form of the NE data wizard (Host Administration: NEs – see 3.e.25 or E.10 Configuring maximum number of NE connections for EFD Administration For working with the EFD Administration see 3.25 and E. 146/185 A30828-X9410-B082-35-7619 . NE ID strings will be used in LI tickets as they have been entered – no header will be added. 4.763 (i. (2) Ask a LIOS operator with Observation Manager rights to perform Align DB. The LIOS properties in the following control input and conversion of NE IDs for the X. NE IDs will be coded according to Q.ETSI_AddHeaderToE164 0 1 Meaning Regulates which characters can be entered in the ETSI form of the NE data wizard to specify NE IDs in the X. Decimal numbers accepted (default). In the course of EFD Administration operation. NE IDs will be coded according to Q.25 format will be coded according to Q. NE ID strings will be used in LI tickets as they have been entered – no header will be added.25 format.ETSI_HexaX25 0 1 HostAdmin.15.ETSI_AddHeaderToX25 0 1 TicketRouter. Hexadecimal numbers accepted. This is reflected in the default property settings (decimal numbers and automatic addition of header). whether a 2-byte header will be added).25 and the E. He will enter the header in the ‘Address’ field and then the X. if ‘add header’ is ON. whether a 2-byte header will be added).9 Setting ETSI properties for NE ID (X. Decimal Hexadecimal Add header automatically YES NO Do not add header automatically NO YES 4. Decimal numbers accepted (default).4.164 format. LIOS will establish a new connection only when another one has been closed. This means. Proceed as follows: (1) Enter the new NE version (LIOS Host Administration. Hexadecimal numbers accepted. NE data wizard – see 3.164 formats. The property settings for this situation are: ‘hexadecimal characters’ and ‘no automatic addition of header’. The maximum number of simultaneous connections can be configured.2 User Manual – Administrator Issue 35 (only if before upgrading. This will automatically restore LI passwords and observations on the NE. ‘hexadecimal’ should be OFF and vice versa.6). the EFD server establishes connections to several NEs.e.164 format will be coded according to Q. Regulates whether NE IDs entered in the E.164 address.LIOS V8. Once the maximum number is reached. Regulates whether NE IDs entered in the X. Usually the LIOS administrator will enter the X.4. LI management notifications (also called HI1 notifications) notify the LEA about events like observation activation.maxConnections = 8 4. or from hiQ/E9200.properties file) Only for EWSD V13A and higher. If this is not desired.11 Setting active/passive FTP to LEAs and MCs (LIOS.parallelSending = 0 The settings affect ticket sending to all LEAs that are connected with the LIOS system.3). A30828-X9410-B082-35-7619 147/185 . 4.3).12 Switching parallel ticket sending on and off (LIOS.properties’ configuration file is described in Section 4. This means that LEAs receive tickets from two sources. # EFDServer ###################### # the following attribute is used for limitation the number of maximum # connections in RequestManagement # hardcoded default-value is 5 EFDServer. tickets are normally sent to LEAs from both LIOS servers in parallel. for the communication to all LEAs and MCs. Tickets must have originated from EWSD V13A and higher.ConnectModeActive = 1 These settings are generally valid. Nevertheless.e. The following solution has been implemented: ─ The communication to NEs is always done through the active FTP mode. It can also provide information about alarms. and must have the format ‘ETSI V2. edit the ‘lios. and for hiQ/E9200. Parallel ticket sending is ON: TicketRouter.properties’ configuration file (how to access the ‘lios. ‘EFDServer’ property (how to access the ‘lios. but only from one LS at a time. ─ The communication to LEAs and MCs is done by default through the passive FTP mode. HI1 notifications are sent through the HI2 mechanism just like normal tickets. you have to edit the ‘lios. passive FTP (default): FTP. i.13 Switching support of LI management (HI1) notifications on and off (LIOS.properties file) LIOS can use the FTP protocol (parallel to the FTAM protocol) to perform some file transfer operations: ─ to NEs (ticket buffer) ─ to LEAs (ticket transfer) ─ Monitoring Centers (MC events transfer) For FTP to LEAs and MCs it is also possible to use the passive mode. tickets can be sent one time from one LS.ConnectModeActive = 0 active FTP: FTP.properties file) To enhance system performance.1’ (with ‘ETSI National D’ format it does not work because the HI1 data is part of the national parameters). edit the ‘lios.LIOS V8. To switch parallel ticket sending off or on. From the file name the LEA can identify if it is an HI1 or an HI2 notification. deactivation and modification. parallel sending can be switched off. To change it to the active FTP mode.2 User Manual – Administrator Issue 35 To configure the maximum number of simultaneous NE connections.parallelSending = 1 Parallel ticket sending is OFF: TicketRouter. which is also shown in ticket names.properties’ configuration file is described in Section 4. the other time from the other LS. At present LIOS provides only notifications about observation activation and deactivation.properties’ configuration file.properties’ file. only one connection is established. This means that for ticket sending to a LEA. 4. 4. 1 type – one of S (64bit DES). If the NTP server is a stand-alone system.LIOS V8. numeric value. ‘1 M mypass’ ─ Copy/modify file ‘/etc/inet/ntp.1. ‘server 127. HI1 support is ON: TicketRouter. The LIOS-proprietary time synchronization must be turned off (see the Section 4. The NTP server can be a stand-alone system (some computer outside of LIOS) or a LIOS server. A (1-8 characters ASCII). Step-by-step configuration: 23. edit the ‘lios.14. N (64bit NTP number). ─ NTP is used: ─ The NTP server is some computer outside of LIOS.0. e. If NTP is going to be used. M (1-8 characters MD5) password – any password e. ‘broadcast 224. NTP clients are all other LIOS servers existing in the network. These files will be automatically read by Solaris after reboot.conf’ ─ At least one line with the command ‘server <address>’ has to exist to identify the address of the time source e.g.keys’ ─ Insert the authentication key into the file in the format <key> <type> <password> (the key identifies a line in the file and consists of <key> <type> <password>. 4. Generally there are three most common possibilities how to perform time synchronization in LIOS: ─ NTP is not used: Rely on the LIOS-proprietary time synchronization as it was prior to LIOS 7.g. please refer to the next section for information how to configure NTP server and client.127.keys’ has to exist 148/185 A30828-X9410-B082-35-7619 .1 Multicast/Broadcast synchronization (automatic) Multicast/Broadcast synchronization can be used when broadcasting (multicasting) over the network is possible.2 User Manual – Administrator Issue 35 To switch the support of LI management (HI1) notifications off or on.properties’ configuration file is described in Section 4.3).1 key 1 ttl 10’ ─ A line with the command ‘keys /etc/inet/ntp. Both LIOS servers are configured as NTP clients.ETSI_HI1 = 1 HI1 support is OFF: TicketRouter.15) or ─ One of LIOS servers will act as NTP server and other as NTP client. it is needed to know or administer some configuration data for NTP on this machine (this machine must be in time-packets broadcasting mode).g. The LIOS-proprietary time synchronization must be turned off.g. NTP server configuration ─ Create or copy and modify the file ‘/etc/inet/ntp.0’ for local computer clock source (clock can also be on any other server) ─ A line with the command ‘broadcast <address> key <key#> ttl <ttl#> has to exist. It is enough to create some configuration files and place them into the respective directory.1.14 NTP Configuration for LIOS NTP (Network Time Protocol) requires two types of machines to configure: NTP server and NTP client. this key id (and password) is checked by an NTP client when receiving a broadcasted time packet from the server) key – key ID. with proper values set (see above creation of key) address – multicast or broadcast address key# – key ID to sign packets ttl# – number of maximum network hops from NTP server to client e.ETSI_HI1 = 0 4.properties’ configuration file (how to access the ‘lios. hpoll=6.1 NTP server ─ Run ‘ntpq’ utility.00.0.log 2>&1 &’ for logging output into file ‘/tmp/xntpd.a01f1000 Thu. sel_sys.conf’ ─ Line with command ‘multicastclient <address>’ has to exist address – same address as configured on the NTP server in ‘broadcast’ command. leap=00. delay= 0.0.1. srcport=123. event_reach srcadr=LOCAL(0). hmode=3. reftime=c30b0296.2 User Manual – Administrator Issue 35 ─ Restart server. conf. stratum=3. (or simply start /usr/lib/inet/xntpd) remark: start ‘/usr/lib/inet/xntpd –d >/tmp/xntpd.2 Configuration check 4.a01f7000 Thu.00 0. A30828-X9410-B082-35-7619 149/185 . ─ A line with the command ‘trustedKey <key#>’ has to exist key# – key ID which is entered in ‘ntp. rootdispersion=0. Sep 11 2003 16:17:58.00 0.2.00 0.a01f7000 Thu.LIOS V8. Sep 11 2003 16:17:58.conf’ file on the server. NTP client configuration ─ Create or copy and modify the file ‘etc/inet/ntp. ─ A line with the command ‘enable auth bclient’ has to exist. it is also possible not to create a file ntp.00. xmt=c30b0296. ─ Example: ntpq> pstatus 46388 status=9614 reach. (or simply start /usr/lib/inet/xntpd). where only LIOS servers exist and where there is no danger of an attack with false time packets.625. keyid=0. ─ Copy/modify file ‘/etc/inet/ntp.00 0. offset= 0. org=c30b0296. rec=c30b0296.keys’ has to exist. refid=LOCAL(0).625. dstport=123. flash=0x0<OK>. Only the key which is used in the ‘broadcast’ command in the ‘ntp. ppoll=6. remark: start ‘/usr/lib/inet/xntpd –d >/tmp/xntpd. 1 event.keys’ file on client and server.keys’ with exact key line as configured on the NTP server (see above).00. valid=8.00 0.log 2>&1 &’ for logging output into file ‘/tmp/xntpd. ─ The ‘associations’ command displays information about active associations of NTP (If association table is empty or state “condition” is faulty NTP does not work correctly).a01f7000 Thu.00 0. ─ Restart server.06. Sep 11 2003 16:17:58.peer.625. 4.log’ 24.keys (on both – server and client) and not to fill in any information about authorization keys (commands broadcast and trustedKey). Also command ‘broadcastclient’ can be entered instead of ‘multicastclient <address>’. ─ Example: ntpq>associations ind assID status conf reach auth condition last_event cnt =========================================================== 1 46388 9614 yes yes none sys.00.00. reach=377. filtdelay= 0.14.625. rootdelay=0. ─ A line with the command ‘keys /etc/inet/ntp. pmode=4.log’ In a closed network.14. Sep 11 2003 16:17:58. dispersion=10. dstadr=127. precision=-14.00 0.peer reachable 1 2 46389 c000 yes no ─ The ‘pstatus <assID>’ command displays information about associations. is needed. 14. recognized by xntpd 3-5.conf # # An example file that could be copied over to /etc/inet/ntp.73.00.98 6. srcport=123. no events srcadr=gfts7.00 12.conf and # edited. xmt=c30af437.0.624.keys 1 M password >cat ntp_server. filterror= 1.22. filtdelay= 0. sel_sys.25 -1.2 User Manual – Administrator Issue 35 filtoffset= filterror= 4. synchronizes the local clock.014. leap=00.93342000 Thu.73 0. dstadr=224. refid=LOCAL(0). rootdelay=0.conf LIOS broadcast server configuration # # Place to /etc/inet/ntp.11 -1.37 -1.73.3 Listing of NTP configuration files for LIOS >cat ntp.25 -1. auth.01 0.00 12.00 13. reftime=c30b0316.06 0.14. it provides a configuration template for a server that # listens to an external hardware clock.03 0.9ff21000 Thu. # and announces itself on the NTP multicast net.00 11.89 NTP client ─ Run ‘ntpq’ utility ─ The ‘associations’ command displays information about associations of NTP.conf # @(#)ntp_server.1.22 -1. reach=377. offset= -1.2 0. hpoll=6. org=c30b0317. ─ Example: ntpq> assoc ind assID status conf reach auth condition last_event cnt =========================================================== 1 36407 7600 no yes ok sys. rootdispersion=10.10 2.00.peer. hmode=8. ppoll=6.LIOS V8.2.00 10.05 4.93 4. rec=c30b0317.73 0.25 -1.03c41000 Thu.08 3.00 14. dstport=123.94 0. # # # # # # # # # # # This is the external clock device. pmode=5.73 0.10.00 15.624.03 5.73 0.93e: The following devices are XType Device RefID Description ------------------------------------------------------1 local LCL Undisciplined Local Clock 2 trak GPS TRAK 8820 GPS Receiver 3 pst WWV PSTI/Traconex WWV/WWVH Receiver 4 wwvb WWVB Spectracom WWVB Receiver 5 true TRUE TrueTime GPS/GOES Receivers 150/185 A30828-X9410-B082-35-7619 . flash=0x0<OK>.12.73 0.31.73 0.peer ─ The ‘pstatus <assID>’ command displays information about associations.575. Sep 11 2003 15:16:39. delay= 0. Sep 11 2003 16:20:07. keyid=1. Sep 11 2003 16:20:06. ─ Example: ntpq> pstatus 36407 status=7600 reach.99 0. filtoffset= -1.9ff40000 Thu. Sep 11 2003 16:20:07.73 0. dispersion=1.91 0.96 7. valid=8. 16.19 -1.00 5. stratum=4.96 0.1. precision=-14. See the xntpd # Either a peer or server. More servers is optimum.0 # At least one server is required.1. to meet actual settings.XType. documentation.0. Types 15 and 25 will be retained only for a limited time and may be reassigned in future.1 key 1 ttl 100 # Specify keys file for authentication keys /etc/inet/ntp.keys >cat ntp_client.conf LIOS broadcast client configuration # # Place to /etc/inet/ntp.1 A30828-X9410-B082-35-7619 151/185 . Some of the devices benefit from "fudge" factors. # This means that device (hardware clock or any other server) at <address> is source of valid time for this server.127. type 5.1. Replace "XType" with a value from the # table above. Must be same as multicast address on NTP server multicastclient 224. server 127.conf # @(#)ntp_client.LIOS V8.0 prefer # Send time packets automatically # multicast server with key=1 and ttl=100 broadcast 224.0.1.conf # # LIOS NTP multicast client configuration file # # Choose a configuration which matches the NTP server settings # Possible configuration: # multicastclient # broadcastclient # Specify that client listen to broadcasted time packets # # command: multicastclient <address> # set the NTP client to multicast client # the address for multicast client can be modified.2 User Manual – Administrator Issue 35 # # # # # # # # # # # # # # # # # # # # # # # # # # 6 7 8 9 10 11 12 13 15 17 18 19 20 22 23 24 25 26 27 irig chu parse mx4200 as2201 arbiter tpro leitch * datum acts heath nmea atom ptb usno * hpgps arc IRIG CHU ---GPS GPS GPS IRIG ATOM * DATM ACTS WWV GPS PPS TPTB USNO * GPS MSFa IRIG Audio Decoder Scratchbuilt CHU Receiver Generic Reference Clock Driver Magnavox MX4200 GPS Receiver Austron 2201A GPS Receiver Arbiter 1088A/B GPS Receiver KSI/Odetics TPRO/S IRIG Interface Leitch CSD 5300 Master Clock Controller TrueTime GPS/TM-TMD Receiver Datum Precision Time System NIST Automated Computer Time Service Heath WWV/WWVH Receiver Generic NMEA GPS Receiver PPS Clock Discipline PTB Automated Computer Time Service USNO Modem Time Service TrueTime generic receivers Hewlett Packard 58503A GPS Receiver Arcron MSF Receiver * All TrueTime receivers are now supported by one driver.127. Address format: 127. In lios. commas are used as separators (field delimiters). edit the lios. For the modifications to take effect. this means.keys #Selected valid key. ExportFormat = TXT Text format.surround = " Character automatically inserted before and after each field. GFTS1) is the name of the host where the timesync process (trying to set system time according to radio device time) will be started by lirecovery script. For example if LIOS servers are TS1 and TS2 specify value TS3: [TimeSynchronization] TS3 -t /cua31 -s /dev/cua/a 4. the LIOS-proprietary time synchronization mechanism should be turned off. you have to stop and restart the LIOS services (see 4.cfg there is time synchronization section: [TimeSynchronization] GFTS1 -t /cua31 -s /dev/cua/a The first parameter (e. Also TXT format with tab stops as separators is supported. This can be done by setting datagram port for the LIOS-proprietary time server and time client to 0. from which are time-packets accepted by this client trustedkey 1 4.delimiter = .properties file The format for LIOS data export is CSV (comma-separated values) format. This could be a problem if the NEs connected to LIOS are located in 152/185 A30828-X9410-B082-35-7619 .3). The CSV format can be modified in the following ExportFormat properties: ExportFormat.17 Ticket time stamp conversion according to the time zone of the NE The tickets generated by NEs of Type EWSD and hiQ/E9200 contain always GMT time and not the local time where the NE is located. Default is comma (‘.’).properties configuration file.g.properties set: TsyncThread.LIOS V8.15 Turning off the LIOS-proprietary time synchronization Turning off java services If NTP is used. ExportFormat. We do not want this process to be started. Field delimiter (separator).2 User Manual – Administrator Issue 35 # command: broadcastclient # set the NTP client to broadcast client #broadcastclient # Specify that authentication and broadcast listening are enabled enable auth bclient # Specify keys file keys /etc/inet/ntp. 4.extension = csv File name extension automatically added ExportFormat. field delimiters: tab stops ExportFormat = CSV Field delimiters: commas. To change export format and field delimiter.16 Changing export format (field delimiter) in the LIOS. TsyncOff = 1 Turning off native services In lios. Therefore specify as time sync server any host name except LIOS servers. 2 User Manual – Administrator Issue 35 different time zones. example: NE is located in time zone 'Europe/Istanbul': GMT+2 (= +2 hours) LIOS converts the time stamp to GMT+2: 2006/12/18 13:06:28 2.TimeZone = 1 Additionally for each NE concerned the correct time zone has to be set in LIOS Host administration -> NEs -> General by the LIOS Administrator. To avoid this the time stamp can be converted in LIOS to the correct time based on the time zone the NE is located. E. To activate this feature set the following LIOS property: TicketRouter.LIOS V8.: NE provides ticket with GMT time: 2006/12/18 11:06:28 1. example: NE is located in time zone 'Australia/Sydney': GMT+10 + 1 hour DST (= +11 hours) LIOS converts the time stamp to GMT+11: 2006/12/18 22:06:28 A30828-X9410-B082-35-7619 153/185 .g. 25 channel number space (outgoing.1.g.1 Symmanager 5. All tasks described here should not be carried out during normal operation.1.25 packet size) +1. e.: ─ X.1 Overview Symmanager is an administration tool for configuring X.1. e.25 packet size used.g.2 User Manual – Administrator Issue 35 5 System configuration Root permission on the LIOS servers is needed for performing the system configuration tasks described in this chapter.25 packet size used. 154/185 A30828-X9410-B082-35-7619 .LIOS V8. e.25 card The values to be specified for the size (DTSX INTERNAL BUFFER SIZE) and number (MAXIMUM BUFFERS/VC TRIGGER) of internal buffers depend on the X. The following examples show how optimum or necessary values for the two parameters above are defined with respect to the X. log in as root and type symmanager.25 packet size used ─ The value range for this parameter is between 256 and 1024. It may be necessary to adapt the channel number space or size and number of internal buffers (see 5. ─ MAXIMUM BUFFERS/VC TRIGGER = max TPDU/(min. both-way) ─ Repetition counter setting ─ Default packet size and default window size setting Specifying HDLC parameters. 5. It enables you to do the following: Specifying X. X.2).g. ─ The maximum TPDU size accepted by LIOS is 2048. When setting the two parameters.25 cards. ! For more detailed information and troubleshooting advice see the LIOS Troubleshooting Guide. 5. observe the following rules: ─ DTSX INTERNAL BUFFER SIZE = maximum X. For further information see [5].: ─ DTE or DCE functions ─ Maximum HDLC window size ─ Maximum HDLC frame length Specifying the card configuration.25 timer ─ X.25 parameters.: ─ Size of internal buffer (DTSX INTERNAL BUFFER SIZE) ─ Number of internal buffers (MAXIMUM BUFFERS/VC TRIGGER) ─ Switching external clock on and off Usually the default values are sufficient. ─ The value range for this parameter is between 1 and 33. To start Symmanager. incoming.2 Specifying size and number of internal buffers of the X. Therefore additional administration of the X. FTAM to NE is handled either via native X. Symmonitor enables you to localize problems in the transport system (X. Enter symmon.3).25 network or via X. the following prerequisites must be fulfilled: ─ The HSI card must be installed in every LIOS server.25 communication over the Symicron card. MAXIMUM BUFFERS/VC TRIGGER = 3 The maximum TPDU size accepted by LIOS is 2048 and the minimum X. 5.1 Administering FTAM file transfer FTAM must be installed and configured on every LIOS server. MAXIMUM BUFFERS/VC TRIGGER = 17 The formula yields the value 17 if the LIOS TPDU size of 2048 is used. A30828-X9410-B082-35-7619 155/185 .3.25 packet size of 1024 lies within the permissible range of values. With LIOS of version 3 and higher. ─ The driver software for the HSI card must be installed. A self-explaining window is displayed which enables you to trace the X.2 User Manual – Administrator Issue 35 Example 1: Only the X. For details see [5]. 5. Root permission on the LIOS servers is needed for performing the operations described in this section.25 packet size of 128 lies below the permissible range of values. Example 2: Only the X. Before the configuration of the FTAM file transfer can be started.25/ISDN. FTAM to the LEA is handled via native X.25 software is necessary (see 5. With Symmonitor you can view the X. Depending on the hardware configuration of LIOS.25 communication.3.25 via LAN – LLC2) and from there via ISDN to the network element.25 packet size 128 is used: DTSX INTERNAL BUFFER SIZE = 256 Because the maximum X.LIOS V8. the lower limit of the range of values(256) is used. FTAM (File Transfer Access and Management) is used for the following tasks: ─ Transfer of event tickets to the LEA ─ Transfer of event tickets from NE.25 communication on the OSI layers 1 to 3.25 packet size is 1024.25) located between LIOS and the NEs.25. In this case the FTAM data is transferred via LAN to the ISDN router (X. Login as root on the LIOS server which has problems with the X. Proceed as follows: 1.25 packet size 1024 is used: DTSX INTERNAL BUFFER SIZE = 1024 Because the maximum X. 2. the value can be used. Make sure you have selected the correct port to be traced. when delivery of event tickets via Q3 is not possible.2 Symmonitor Root permission on the LIOS servers is needed for performing the operations described in this section. 5.3 FTAM configuration The FTAM configuration does not apply to the LIOS Admin mode. if the network element is connected to LIOS via ISDN. presentation layer and part of the application layer (layers 4 to 7) of the OSI reference model. Table 5-1: Configuring Solstice X.25 software: LLC2 Link 156/185 A30828-X9410-B082-35-7619 . Collecting X.2). if Size Negotiation is enabled.25 configuration data Before starting FTAM file transfer administration.3.4). the necessary X.25 packet size is used if the packet size is not negotiated.3).25 for the data link layer and network layer (layers 2 and 3) of the OSI reference model. 5. Solstice OSI and Solstice FTAM must be installed. The Default Window size must be the same for LIOS and the network provider. The maximum Window size is used for window size negotiation between LIOS and LEA. This option must be activated or deactivated for both partners: LIOS and network elements. The default X. Configuration parameter Explanation local NSAP address local DTE address Logical channel numbers (start/end point) Request Size Negotiation Default and maximum X. 2. The start and end points must be the same for the local LIOS and the network provider. Reading of the ARP cache of the LIOS server by ‘arp –a' MAC address of the TCP/IP port of the LIOS server.LIOS V8.25 software: X. The Solstice X. session layer. Negotiate packet size and window size = yes/no This parameter permits both partners to negotiate an optimum packet size.25 Link listed in Table 5-1 should be collected. Number of layer 3 packets after which an acknowledgment must be sent. ─ Configuring Solstice FTAM software (see 5. if Size Negotiation is enabled.25 software (see 5.25. The Solstice OSI software provides the transport layer. ping to the IP address of the ISDN router 2.25 configuration data for the local X.3. This option must be activated or deactivated for both partners. Configuring FTAM file transfer consists of the following tasks: 1. The Solstice FTAM software provides an FTAM implementation for the application layer (layer 7) of the OSI reference model. Table 5-2: Configuring Solstice X. MAC address of the TCP/IP port of the ISDN Router.3. This address can be determined with the following command: ‘ifconfig hme0’.25 software provides X. This FTAM implementation satisfies the ISO (International Systems Organization) requirements for an FTAM application. ─ Configuring Solstice OSI software (see 5.5).25 Packet size Default and maximum Window size local NSAP address of LIOS as configured in every EWSD database. local DTE address of the HSI card.2 User Manual – Administrator Issue 35 ─ The standard software products HSI software.25 configuration data (see 5. This MAC address can be determined by the following commands: 1. Defines the range of logical channel used in layer 3 of the OSI reference model.2 Collecting X. Negotiate packet size and window size = yes/no This parameter permits both partners to negotiate an optimum packet size and window size.3. Solstice X. The default packet size must be the same for LIOS and the network provider.25 Link For FTAM file transfer to network elements connected via X. Configuring every LIOS server for FTAM transfer: ─ Configuring Solstice X.25/ISDN the necessary configuration data of the local LLC2 Link listed in Table 5-2 should be collected: Configuration parameter Explanation Logical channel numbers (start/end point) Request Size Negotiation MAC address of the ISDN Router MAC address of the LIOS server Defines the range of logical channel used in layer 3 of the OSI reference model. The start and end points must be the same for the local LLC Link and the corresponding port of the ISDN router. The maximum Packet size is used for packed size negotiation between LIOS and LEA.3. 25 Packet Layer For all these layers the proper configuration values are to be administered: A30828-X9410-B082-35-7619 157/185 . log in to the LIOS server under the root user ID.25 link 1.2 User Manual – Administrator Issue 35 5.25 software is divided into two sections.25 software The configuration of the Solstice X. Deletion of all existing default entries: All preinstalled links are not suitable for the required X.3 Configuring Solstice X.1 Configuration of the X. 1. Afterwards no link is displayed in the main window. Generation of a new X.25 software.25 link: To create a new link. 5. It is divided into 3 parts according to the OSI layers defined: Layer 1: Physical Layer Layer 2: HDLC Layer 3: X. For configuring the Solstice X. The ‘Link Editor’ window is displayed.25 configuration program: enter the following command: /opt/SUNWconn/bin/x25tool The ‘X.3.25 Link and of the LLC2 Link.25 Administration Tool of the Solstice X.3.25 Administration Tool’ main window is displayed: Figure 5-1: X.3.25 functionality. press the Add button in the main window and select dte84. Start of the Solstice X.25 software – Main window 2. the administration of the X.LIOS V8. Select all preinstalled links and then delete them by press the Delete button. 25 Link – Link Editor window In the ‘Link Editor’ window enter the following parameters: Link Number <link number> Unique number for identifying the X. select ‘Addressing’. Tx Clock: External. 158/185 A30828-X9410-B082-35-7619 . The ‘Addressing Parameters’ window is displayed.25 software X. Administration of the local NSAP Address: To administer the local NSAP Address.2 User Manual – Administrator Issue 35 Figure 5-2: Solstice X.25 link.LIOS V8. Confirm the settings with Apply and OK.25 link of the network provider.121 Address <DTE address of HSI port> Version 1984 Packet Size Here the collected values for the X. Logical Channel The collected values for SVC-Channel Range are to be entered.25 network via this port. The Clock is usually generated by the connected modem. 2.25 Packet Size (default and maximum) are to be entered.25 card (1-4)> The HSI card connects the LIOS server to the X. These values must Range correspond to the X. Link Type WAN Device HSIP Port Number <number of used port of X. Interface DTE LAP Protocol LAPB Local X. 25 software – ‘Closed User Group and Facilities’ window A30828-X9410-B082-35-7619 159/185 . select the ‘CUG and Facilities’ button. The ‘Closed User Group and Facilities’ window is displayed: Figure 5-4: Solstice X.25 software – ‘Addressing Parameters’ window Enter the following values: Extended Address Extension Confirm the settings with Apply and OK. OSI Local NSAP Address 3. Closed User Group and Size Negotiation: To administer Basic Closed User Group Handling and Size Negotiation.LIOS V8.2 User Manual – Administrator Issue 35 Figure 5-3: Solstice X. select the ‘Timers and Counters’ button.LIOS V8.25 Window Size. It should only be selected. The ‘Throughput Class and Window Size’ window is opened: Figure 5-5: Solstice X. Confirm the settings with Apply and OK. The ‘Timers and Counters’ window is opened. you want to use it for your FTAM connection to the Partner System. Confirm the settings with Apply and OK. Select this box only if CUG is used! CUG Format Basic Size Negotiation Select one of the offered settings.25 Window Size. 160/185 A30828-X9410-B082-35-7619 . Throughput Class and Window Size: To Administer the X. Administration of Timers and Counters: To administer the X. select the Throughput button. no other access. For LIOS select the following settings: Closed User Group CUG.25 software – ‘Throughput Class and Window Size’ window Enter the collected values for X.2 User Manual – Administrator Issue 35 Closed User Group (CUG) is an optional X. Only FTAM to members of the given Closed User Group is possible.25 feature.25 Timers and Counters. depending on the configuration. 6. 4. 25 Communication between LIOS and LEA works well. press the Add button in the main window and select ‘LAN’.25 Link of the network provider shall always be active.25 software – ‘Timers and Counters’ window The Timers and Counters are to be administered in such a way that the X. It is divided into 3 parts according to the OSI layers defined: Layer 1: Physical Layer Layer 2: HDLC Layer 3: X. Normally no changes of the default values are necessary.25 Packet Layer For all these layers. 1.25/ISDN.2 Configuration of the LLC2 link The configuration of the LLC2 Link is only necessary when the network element (e. If the OSI Layer 2 (HDLC) between LIOS and the corresponding X.3.g. EWSD) is connected to LIOS via X.LIOS V8.25 link: For creating a new link.3. The ‘Link Editor’ window is displayed. 5.2 User Manual – Administrator Issue 35 Figure 5-6: Solstice X. the timer ‘Idle Disconnect (LAN or Dialup)’ is to be set to ‘0’. you have to administer the proper configuration values: A30828-X9410-B082-35-7619 161/185 . Generation of a new X. It will be used for the X. Logical Channel Enter the collected values for SVC-Channel Range. Closed User Group and Size Negotiation: Basic Closed User Group Handling and Size Negotiation are to be administered by selecting the ‘CUG and Facilities’ button. Confirm the settings with Apply and OK. Link Type LAN Device HME Port Number 0 Interface DTE LAP Protocol LAPB Local X.2 User Manual – Administrator Issue 35 Figure 5-7: Solstice X. LLC2 and Addressing must not be changed for the requested configuration.25 software: LLC2 Link – ‘Link Editor’ window In the ‘Link Editor’ window.25 Packet Size (default and maximum) here. These values must correspond Range to the LLC2 Link of the ISDN router. 2. The ‘Closed User Group and Facilities’ window will be opened: 162/185 A30828-X9410-B082-35-7619 . enter the following parameters: Link Number <link number> Unambiguous number for identifying the LLC2 link.LIOS V8.25 routing table later in this section.121 Address This entry must not be changed! Otherwise the LLC2 Link will not work! Version 1984 Packet Size Enter the collected values for the X. LIOS V8. 3.2 User Manual – Administrator Issue 35 Figure 5-8: Solstice X. It must not be selected for the LLC2 Link. Link Modes: To administer Link Modes parameters for the LLC2 link. The ‘Link Mode Parameters for link #1’ window is opened: A30828-X9410-B082-35-7619 163/185 .25 software: LLC2 Link – ‘Closed User Group and Facilities’ window Closed User Group (CUG) is an optional X.25 feature. For the LLC2 Link. select the ‘Link Modes’ button. Confirm the settings with Apply and OK. select the following settings: Size Negotiation Select one of the offered settings depending on the configuration. 25 software: LLC2 Link – ‘Closed User Group and Facilities’ window For configuring the LLC2 Link.2 User Manual – Administrator Issue 35 Figure 5-9: Solstice X.121 address in Call Request to LAN Confirm the settings with Apply and OK. select the following parameters: Keep X. YES.25 Window Size. select the Throughput button. 4. The ‘Throughput Class and Window Size’ window is opened: 164/185 A30828-X9410-B082-35-7619 .LIOS V8. Throughput Class and Window Size To administer X. Therefore a routing table is necessary.3 Administration of the X.25 connection has to be established via the X. when the network element is connected to LIOS via X. In this case the X.2 User Manual – Administrator Issue 35 Figure 5-10: Solstice X. Administration of the Default Route After selection of the routing service a window like the following will appear: A30828-X9410-B082-35-7619 165/185 . 5.3.25 routing table This task must only be executed.25 Link or via the LLC2 Link depending on the called DTE address.25 software – ‘Throughput Class and Window Size’ window Enter the collected Values for X. In the main window of ‘x25tool’ choose Services -> Routing to get the routing table.LIOS V8.25 Window Size. 1. Confirm the settings with Apply and OK.25/ISDN.25 software has to decide whether an X.3. That means that every connection to the LEA will be handled via X. LI tickets from the NE will be fetched via the LLC2 link.LIOS V8.25 link.121 default Link Number <Number of the X. Because the default route for FTAM connections is defined via X.25 link.25.25 Routing Table – Definition of the default route. Press the Add button and enter the following parameters: Route Type X.2 User Manual – Administrator Issue 35 Figure 5-11: X. Administration of the host routes to NE When an NE is connected to LIOS via ISDN/X. Confirm the settings with Apply and OK.25 link> Comment: Any comment describing the default entry. The default route should be configured for the X.25 without any further configuration. for every NE one routing table entry has to be configured as follows: 166/185 A30828-X9410-B082-35-7619 . 2. The configuration of a host route must be repeated for every connected NE! 5.25 configuration After configuring the necessary X. Enter the following parameters: Route Type X.25 network software: In the main window. A30828-X9410-B082-35-7619 167/185 . 2.3. Start of X.3. Enabling automatic start of the X.25 links (X. select the Options menu and the Start X.121 host Link Number <Number of the LLC2 link> X.25 and LLC2 if necessary).4 Activation of the X. Because the routing table is read from beginning to end.121 Address DTE address of the NE MAC Address MAC Address of the corresponding ISDN Router Comment: Any comment describing the host route to the given NE.LIOS V8.25 network software: In the main window. activate the configuration: 1. that all host route entries are configured before the default route entry. it is important.25 automatically when booted menu item.2 User Manual – Administrator Issue 35 Figure 5-12: X.25 Routing Table – Definition of host routes Press the Add button followed by the Top button. select the Network menu and the Start X25 menu item. 25 : Creating link 0.LIOS V8. Login to the LIOS server with root user ID.please wait X. Start of the Solstice OSI Configuration program: /opt/SUNWconn/bin/ositool The ‘OSI Administration Tool’ main window is opened: Figure 5-13: ‘OSI Administration Tool’ main window (Solstice OSI software) 2.25 output has been saved in /tmp/x25_output. Now you can stop the X.25 Configuration. This was the last task of the X.25 has found a valid license The network has been brought up..25 Configuration program. Stack configuration: To configure the local OSI stack. Check whether the osinetd process is running. carry out the following steps: 1.2 User Manual – Administrator Issue 35 Messages like the following are written into the output area of the window: <07/15/98 <07/15/98 <07/15/98 <07/15/98 <07/15/98 <07/15/98 <07/15/98 <07/15/98 11:18:21> 11:18:21> 11:18:22> 11:18:22> 11:18:22> 11:18:22> 11:18:22> 11:18:32> Starting the X. The ‘Stack Manager’ window is opened: 168/185 A30828-X9410-B082-35-7619 ..3. --> X. If not. 2. X.25 : link 0 has been started X.d/S90osinetd start The Solstice OSI software you can configure as follows: 1.4 Configuring the Solstice OSI software To configure the Solstice OSI software. 5.25 software . start it: /etc/rc2. select the ‘Stack Manager’ icon. 25 Device. A30828-X9410-B082-35-7619 169/185 . Device configuration: Select Devices from the Configuration pull-down list.LIOS V8.2 User Manual – Administrator Issue 35 Figure 5-14: Window ‘Stack Manager’ of Solstice OSI software 3. The ‘Device Configuration’ window is opened: Figure 5-15: Window ‘Device Configuration’ of Solstice OSI software From the Add pull-down list select X. 2 User Manual – Administrator Issue 35 For the required parameters. enter the following values: Link Number Number of the X. For communication to many FTAM Partner systems these Application Selectors must correspond to the entries for the remote system administered in the partner systems. The ‘Application Selectors’ window is opened. Confirm the entries with Apply and Save and close the ‘Device Configuration’ window.25 link specified in X.25 configuration. From the ‘Network Access’ pull-down list select X. Figure 5-16: Window ‘Application Selectors’ in Solstice OSI software Define the Selectors of the local FTAM Initiator Application here. Configuration of Transport Layer: In the ‘Stack Manager’ window select ‘Transport over CONS’. Connection Pool Maximum Number of simultaneously active connections. You can make entries in character and hexadecimal format. The parameters for ‘Transport over CONS’ are displayed in the ‘Stack Manager’ window: 170/185 A30828-X9410-B082-35-7619 . Application Selector configuration: From the Configuration pull-down list in the Stack Manager select ‘Application Selectors’. SNPA Address local DTE address of HSI port Confirm the settings with Apply and Save and close the ‘Device Configuration’ window.25 and from the Applications pull-down list select FTAM. 4. 5.LIOS V8. The parameters for ‘CONS’ are displayed in the ‘Stack Manager’ window: A30828-X9410-B082-35-7619 171/185 .LIOS V8. select the ‘CONS’ entry. In the ‘Stack Manager’ window.2 User Manual – Administrator Issue 35 Figure 5-17: Stack Manager in Solstice OSI software – Configuration of ‘Transport over CONS’ Perform the following administration tasks: Max PDU Size 4096 Class Options Class 0 Only Confirm the entries with Apply. LIOS V8. For the Type used.25 Packet Size’. enter the complete NSAP address of the LIOS server as it is configured at every NE. Confirm the entries with Apply and close the ‘Stack Manager’ window. The ‘Network Layer Addresses’ window is opened. select CONS: Figure 5-19: Window ‘Network Layer Addresses’ of Solstice OSI software In the NSAP field.2 User Manual – Administrator Issue 35 Figure 5-18: Stack Manager in Solstice OSI software – Configuration of CONS Check/Edit the correct value for ‘Default X. 172/185 A30828-X9410-B082-35-7619 . without separator. select the ‘Network Layer Addresses’ icon from the Main Window of ‘ositool’. Network Layer Addresses: To define the access points to the X. From the ‘NSAP Family’ pull-down list select ‘Free form’. 7.25 Network. Therefore you must configure host routes. you must configured the routing software of the OSI Stack in such a way that the DTE address of a partner system is derived from the NSAP address. E.g. Otherwise the Routing entry for DTE addresses with 14 digits would be used for the DTE addresses with 13 digits. Remove all existing (preconfigured) routes not needed for the applications to be used (e. Figure 5-20: Route Manager window – Prefix Routes Configuration of ‘Prefix Routes’ to LEA From the Category list select Prefix Routes and from Network select CONS. Route Manager: Configure the route manager of the OSI Stack for two kinds of partner systems. select the ‘Route Manager’ icon in the main window of Ositool.LIOS V8. you have to configure the route for a DTE address with only 13 digits (SNPA Offset 3) before the route for a DTE address with 14 digits (SNPA Offset 2). For each routing entry to be configured select ‘Extract Route’. too.g.2 User Manual – Administrator Issue 35 Confirm the entries with Apply and close the ‘Network Layer Addresses’ window. 5. To define the routing entries of the OSI Stack. Configure all routes needed for the applications. Define ‘SNPA Offset’ (leading digits of the NSAP address. LEA and NE. Care is to be taken when you are configuring more routing entries for the same AFI. The routing software walks through the entries from the beginning of the table to the end.’ parameters for each entry: A30828-X9410-B082-35-7619 173/185 . Therefore you must configure prefix routes. For FTAM to NE a routing entry for each NE is necessary. routes with NSAPs beginning with AFI = 52). define the ‘X.. In addition. that are not part of the DTE address) and the ‘SNPA Length’ (length of the DTE address). For FTAM to LEA.25 Service.. Local/Remote Window Size). ! For ‘X. Select ‘Use Closed User Group’ and define the CUG Value if Closed User Group is required for the connections used. Otherwise deriving of the DTE address from the NSAP address will not work.25 Features’ window Select ‘Use Flow Control Parameter Negotiation’ if Flow Control is required for the connections used and select the parameter values to be negotiated (Local/Remote Packed Size. For ‘Addressing Mode’ you must select ‘CONS-84/88’. Figure 5-22: Route Manager window – Host Routes 174/185 A30828-X9410-B082-35-7619 . Configuration of ‘Host Routes’ to NE From the Category list. select Host Routes from and Network select CONS.25 Link Type’ you must select the value ‘1988’ or ‘1984’. For each NE.LIOS V8. configure a host routing entry as is shown in the following figures.2 User Manual – Administrator Issue 35 Figure 5-21: ‘Remote X. Remove all existing (preconfigured) routes not needed for the applications to be used. d/S147osiftrd /etc/rc3.LIOS V8. select ‘Direct Route’ and define ‘NSAP’ (NSAP address) and ‘SNPA’ (DTE address).3. If Closed User Group is required for the connections used.5 Configuring the Solstice FTAM software For configuring the Solstice FTAM software proceed as follows: 1. ! If the entries made are not saved before Ositool is stopped. Disable the automatic start of the FTAM responder by renaming the startup file: mv /etc/rc3. 5. all changes will be lost! Now the local configuration of the OSI Stack is finished. In addition.. A running FTAM Responder can be a security risk! Start the Solstice FTAM Configuration tool ftamtool: /opt/SUNWconn/bin/ftamtool The main window of the ‘FTAM Configuration Tool’ is displayed.25 Features’ window If Flow Control is required for the connections used. select ‘Use Flow Control Parameter Negotiation’ and the parameter values to be negotiated (Local/Remote Packed Size. A30828-X9410-B082-35-7619 175/185 .d/s147osiftrd (replace ‘S’ with ‘s’) The Responder function is not used for LIOS. select ‘Use Closed User Group’ and define the CUG Value.’ parameters for each entry: Figure 5-23: ‘Remote X. 2.2 User Manual – Administrator Issue 35 For each routing entry to be configured. For ‘Addressing Mode’ you must select ‘CONS-84/88’. For ‘X..25 Service.25 Link Type’ you must select the value ‘1988’ or ‘1984’. define the ‘X. Save all administration tasks saved with Save in the main window and stop Ositool. Local/Remote Window Size). Login into the LIOS server with root user ID. LIOS V8. Close the ‘FTAM Configuration Tool’. select the ‘Local Initiator’ icon. 176/185 A30828-X9410-B082-35-7619 . The ‘Local Initiator Configuration’ window is opened: Figure 5-25: ‘Local Initiator Configuration’ of Solstice FTAM software Disable the ‘FTAM-2’. Configuration of local Initiator: In the main window of the ‘FTAM Configuration Tool’. Confirm the entries made with Apply and OK. ‘NBS-9’ and ‘INTAP-1’ document types (these document types are not used for LIOS).2 User Manual – Administrator Issue 35 Figure 5-24: ‘FTAM Configuration Tool’ of Solstice FTAM software – main window 3. The Remote Systems Database is not configured by the ftamtool.LIOS V8. It contains the following products: • TopSec 702(703) ISDN Encryption Box for ISDN BRI Interface • TopSec 730 ISDN Encryption Box for ISDN PRI Interface • TopSec administration software For LIOS one TopSec 730 is installed between BinTec Bianca XL2 and the Network Terminator.4. The TopSec 702 (or TopSec 703) are placed between the Network Terminator and the ISDN Terminaladapter. This is done by the LIOS applications Host Administration and LEA Administration. which allow partner administration from remote hosts (NEs and LEAs). so you need not configure the Local Responder.1 Overview The Siemens TopSec System is used for Encryption of User Data in ISDN B Channel between two Communication Partners. This finishes the configuration of the local FTAM Stack. The following picture gives a short overview about the hardware configuration of the TopSec Boxes in combination wit LIOS: A30828-X9410-B082-35-7619 177/185 .4 Installing TopSec System (optional) 5.2 User Manual – Administrator Issue 35 The Responder function of Solstice FTAM is not used for LIOS. 5. 4. Define the system configuration of the administration program as described in [6]. The following steps have to be executed: 1. Section 5. 3.2 User Manual – Administrator Issue 35 LIO S client LIO S server ( X. With this Key Backup file it is possible to login to the administration software if you have forgotten your administrator password.25) X25/ISD N Router BinTec Bianca XL2 TopSec 730 N etwork term inators ISD N N etw ork N etwork term inator TopSec 703 (702) ISD N Term inaladapter N etwork Elem ents EW SD Figure 5-26: Hardware Configuration overview of LIOS 5. Section 5. 2.2 Installation of administration software The Installation of the administration software has to be done on one of the LIOS Servers. 4.4.LIOS V8. Login to the System as described in [6]. 178/185 A30828-X9410-B082-35-7619 . Section 5.1 and create a Key Backup as described in [6].2 on a floppy disk. Section 2. Initialize the administration software and define an administrator password as described in [6]. Section 5. Install the administration software as described in [6]. 5.LIOS V8. Define the default configuration of the TopSec Boxes as described in [6] Section 5. The following parameters have to be entered (for the other parameters the default values should be used): Parameter Parameter value Speech. going out Always encrypted Plain incoming data Not selected Membership Group 1 Layer Activity Layer 1 and 2 always active Table 5-3: Default parameters for the administration of TopSec Boxes A30828-X9410-B082-35-7619 179/185 .2 User Manual – Administrator Issue 35 Figure 5-27: Configuration of the TopSec Administration Tool 5.1. going out Always encrypted Plain incoming speech Not selected Data. Generate a new entry in the Device table as described in [6].5.3 The following parameters have to be entered in addition to the default configuration: Parameter Parameter value Device ID Any unique number higher than 2 Type of the Box Enter the correct value 730. To add a new TopSec Box to the system you have to do the following: 1.3 Initialization of TopSec Boxes Before any TopSec Box can be used in the administered system it has to be initialized. 702 703 Dial Number Enter the correct dial number necessary for calling the TopSec Box via ISDN (administration) Description Optional: any describing text Table 5-4: Parameters for a new TopSec Box 180/185 A30828-X9410-B082-35-7619 .LIOS V8.2 User Manual – Administrator Issue 35 Figure 5-28: Default Configuration of the TopSec Boxes 5. To connect the LIOS server with the given TopSec Box. The initialization of the TopSec Boxes can only be done via a serial port. Section 5. Initialization via ISDN is not possible.4. the serial cables delivered with the administration software have to be used: • TopSec 730: Connect the serial cable with a free serial port of the LIOS server and the serial port placed on the front side of the TopSec 730 Box • TopSec 702 (703): Connect the serial cable with a free serial port of the LIOS server and the middle S0 Port (RJ45) of the TopSec 702 (703) Box. Connect the new box to the serial port of the LIOS server as described above 2. that resides in the directory specified in the ‘configuration window.2 User Manual – Administrator Issue 35 Figure 5-29: Device Table with all configured TopSec Boxes 3.4. Change to the ‘Jobs’ window and select ‘Firmware Update’. 5. Close the window. 5. 4.) 3.4. Any further configuration task can be done via ISDN if necessary. Select the given TopSec Device in the Devices Table through a double-click on the ‘Device ID’ field 2. for which the firmware has to be updated.4 Administration of TopSec Boxes 5. (These two tasks have to be done for every TopSec Box. Start the Firmware Update by pressing on ‘Start Selected Job’ A30828-X9410-B082-35-7619 181/185 . Enter the name of the new firmware file. Section 5.LIOS V8.1 Firmware update For updating the Firmware of any TopSec Box you have to do the following: 1. Initialize the new box as described in [6].5.5 After this initialization task the TopSec box can be put to its operating destination and plugged into the ISDN connection.4. Select all TopSec Boxes you want to update. 4.5 Switch to Plain Data Transfer For test purposes or if there are problems with the encrypted data transfer on the ISDN connection. Select every TopSec Box you want to modify and change the following two parameters Parameter Parameter Value Data.2 User Manual – Administrator Issue 35 Figure 5-30: Jobs form of the TopSec Administration The update of the firmware takes a few minutes for every TopSec Box. Therefore you have to do the following: 1. it is possible to switch from encrypted to plain data transfer. going out Always clear Plain incoming data Selected Table 5-5: Parameter table for changing to plain data transfer 182/185 A30828-X9410-B082-35-7619 . 5.LIOS V8. Select every TopSec Box. Start the Parameter Update by pressing on ‘Start Selected Job’ To configure the functionality back (from plain to encrypted) you have to execute the same steps with the original parameter values. A30828-X9410-B082-35-7619 183/185 .2 User Manual – Administrator Issue 35 Figure 5-31: Device Configuration of TopSec Box for plain data transfer For proper functioning of the whole LIOS configuration you have to change this behavior for every Box. 4. that has to be updated.LIOS V8. 3. Change to the Jobs form and select ‘Parameter Update’. that is involved. 2. 2 Format of the alarm message for SMS The whole alarm message is sent as a single SMS. LIOS operator to whom the observation belongs. Description of the alarm. This parameter is mandatory. This parameter is mandatory.m hh:mm>). Example: 184/185 A-OIF-00004:5. This parameter is only mandatory for group alarms. This parameter is only mandatory for group alarms. This parameter is only mandatory for group alarms. Example: 5.1 Format of the alarm message for email The personal name in the From part contains the alarm name. Unique observation identifier. Since the length of an SMS is limited to 160 characters. 6. Unique observation identifier. The PIMS application sends the alarm message to the recipients as email or SMS. This parameter is only mandatory for group alarms. it is possible to send alarms as a message via the PIMS application to external targets. This parameter is mandatory. Each line contains a parameter. Possible parameters are: ─ ─ ─ ─ ─ ─ ─ The creation time of the alarm (format: <d. This parameter is mandatory. This parameter is only mandatory for group alarms. NE to which the observation belongs (in case of observation-related alarms). This parameter is mandatory. The body of the email contains the rest of the alarm message. except the first line (contains two parameters). Description of the alarm.2 User Manual – Administrator Issue 35 6 Annex 1: external alarming – email and SMS formats If external alarming has been purchased.5 23:59 Host1 NE:EWSD1 User:op1 Group:opgroup1 OBSid:123 Desc:Error A30828-X9410-B082-35-7619 . LIOS operator to whom the observation belongs. Each line contains a parameter.5 23:59 Host1 NE:EWSD1 User:op1 Group:opgroup1 OBSid:123 Desc:Error 6. This parameter is only mandatory for group alarms.m hh:mm>). The line content is: ─ ─ ─ ─ ─ ─ ─ The alarm name followed by the separator (:) and the creation time of the alarm (format: <d.LIOS V8. This parameter is only mandatory for group alarms. it is possible that the description of the alarm is truncated. This parameter is only mandatory for group alarms. LIOS operator group to which the observation belongs. The hostname of the LIOS server on which the alarm was processed. The next sections describe the look of a message for each medium. NE to which the observation belongs (in case of observation related alarms). LIOS operator group to which the observation belongs. The hostname of the LIOS server on which the alarm was processed. These parameters are mandatory. A30828-X9410-B082-35-7619 185/185 . SR11 and SR12 Siemens IP mediation device Version 3.5 Alcatel S12 MODEL 1400 Huawei C&C08 Version C&C08 Huawei GSM Based on HUAWEI interface specification version 1. SR10. Release 11 Siemens IN@vantage Version 7. Version 3.LIOS V8. Version 3.5 FN Siemens Mobile (MSC) Version SR9. Release 10. Release 11 Siemens Surpass hiQ8000 Release 9. Release 10.0 Table 7-1: LIOS – supported network elements *) Via Lawful Interception Manager (LIM) by KCC.2 Siemens Surpass hiQ9200 Version 4 Siemens Surpass hiQ4200 Release 8.24 Nortel (KCC LIM) * Version OES-D Utimaco IMS RAI 2.2 User Manual – Administrator Issue 35 7 Annex 2: LIOS – supported network elements The following network elements are supported by LIOS: Network element Version Siemens EWSD Versions 11 .Version 18 Siemens Surpass hiE9200 Version 1.
Copyright © 2024 DOKUMEN.SITE Inc.