2N ATEUS User Manual
  1. Manuals
  2. Brands
  3. 2N Manuals
  4. Control Unit
  5. ATEUS
  6. User manual
2N ATEUS User Manual

2N ATEUS User Manual

Remote control unit
Hide thumbs Also See for ATEUS:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual
ATEUS
- Remote Control Unit
®
RCU
User's Guide
Version: 5.00

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Related Manuals for 2N ATEUS

Summary of Contents for 2N ATEUS

  • Page 1 ATEUS - Remote Control Unit ® User’s Guide Version: 5.00...

  • Page 2: Table Of Contents

    CONTENTS INTRODUCTION......................3 ......................3 ANAGEMENT 1.1.1 Control ....................... 3 1.1.2 Monitoring......................4 ......................4 CCOUNTING 1.2.1 Call Data Record (CDR)..................4 1.2.2 Traces ......................... 4 1.2.3 Logs ........................4 1.2.4 Call statistics ...................... 5 ....................5 XTERNAL OUTING THE RCU SYSTEM ......................7 2.1.1 The basic system....................
  • Page 3 ......................24 EB ACCESS 5.1.1 Welcome Message .................... 24 5.1.2 Authentication ....................25 5.1.3 Web Overview ....................25 5.1.4 Web configuration of the gateway..............28 5.1.5 Incomming Call Simulation................28 SNMP M ....................29 ANAGEMENT 5.2.1 SNMP Queries....................29 5.2.2 SNMP Traps .....................

  • Page 4: Introduction

    1 Introduction Unlike the most of telecommunications devices that come with integrated remote management modules, PRI GSM gateways produced by 2N Telekomunikace a.s, the ATEUS ® STARGATE (Stargate) and ATEUS ® BLUESTAR (Bluestar) come with a Remote Control Unit (RCU), a standalone device offering a wider range of management and accounting capabilities.

  • Page 5: Monitoring

    Fig.1: AT command tunneling over SSH 1.1.2 Monitoring The RCU comes with a number of PRI GSM gateway monitoring methods: • Web interface: over the WWW, clients can monitor their PRI GSM gateways while comfortably sitting in their offices. Occurrences of undesired (erroneous) conditions are promptly indicated by changes of color in the offending modules.

  • Page 6: Call Statistics

    1.2.4 Call statistics The RCU stores call summaries. These can be either overall or based on differed modules and SIM cards. The call statistics are readily available over the web 1.3 External Routing The PRI GSM gateway is equipped with an additional capability to route calls based on an external routing database –...
  • Page 7 Incomming request from the gateway *ring: ch, cref, dial,clip Group number 0 ? Group number 1-9 ? Call is rejected Gateway will route the Call is routed to the group AT^RG = ch, cref, cause call according to its according to number in the internal settings table AT^RG = ch, cref, groups...

  • Page 8: The Rcu System

    2 The RCU System 2.1.1 The basic system The RCU is made up of a powerful industrial PC running the Linux OS. Linux was specifically chosen to make the system relatively secure. On top of the Linux OS are a web server (Apache), a database engine (Postgre) and a set of PRI GSM gateway Management and Accounting applications.

  • Page 9: The Management Databases

    • ISDN Trace Service Engine (ITSE): This engine is responsible for downloading ISDN traces • Status Service Engine (SSE): Responsible for periodically downloading statuses of the PRI GSM gateways. If an undesired status is observed, the corresponding status alarm is generated. •...

  • Page 10: Installation

    3 Installation 3.1 Pre-installation For a comprehensive and painless installation, a pre-installation preparation is mandatory. 3.1.1 Topology The RCU can communicate with PRI GSM gateways in any one of the following modes: • RS-232 serial communication through COM1&COM2. This mode can be used if at least one of the PRI GSM gateways is within the proximity of the RCU.

  • Page 11: Os Installation

    Fig.5: The RCU Topology For each managed PRI GSM gateway, the RCU runs a separate SNMP agent. Each running SNMP agent requires an IP address to communicate with the SNMP management node. Let us assume that our RCU will proxy eight PRI GSM gateways (SG0, SG1, …, SG7), The SNMP agent for SG0 will use Eth0 to communicate with the SNMP management node.

  • Page 12: Configuration

    4 Configuration 4.1 Basic configuration Type sgsetup at the bash prompt to run the management software configuration script bash-2.05a# bash-2.05a# sgsetup The SGSETUP configuration script will guide you through the entire configuration process needed to set up the RCU. The text below will take us through the different options Enter current date [07.08.2003]: Today’s date Enter current time [15:01]:...

  • Page 13: E-Mail Alarms

    4.1.1 E-mail alarms Enable e-mail sending? [YES]: Answer yes (y) to enable e-mail alarms, no (n) disables this option E-mail 'FROM' address [stargate@2n.cz]: This entry acts as the sender (source) of the e-mail E-mail 'TO' address [adminsg@2n.cz]: You must enter the e-mail address of the PRI GSM gateway monitoring crew here.

  • Page 14: Call Data Records (Billing)

    4.1.3 Call Data Records (billing) The RCU collects Call Data Records (CDR) that contains all important information about each call that has passed through PRI GSM gateway. These data could be used for billing purposes. Configuration procedure in sgsetup gives you possibility to enable or disable this collection for each managed gateway.

  • Page 15: The Pri Gsm Gateways

    If however, the RCU will use Ethernet to communicate with PRI GSM Gateway #0 then this is the right place to enter PRI GSM Gateway #0’s IP address. Enter Gateway #0 user name [2n]: Enter Gateway #0 user password [2n]: If Ethernet is enabled as above, it is mandatory to configure username and password.

  • Page 16: Network Address Translation

    (Username and password are case sensitive!) These same parameters must be repeatedly set for all the PRI GSM Gateways managed by the RCU (#1 through #7). See the Example configuration in the next section. 4.1.7 Network Address Translation A classical Network Address Translation (NAT) is applied here to map the SNMP IP addresses configured on Eth0 (Eth0, Eth0:1, …...

  • Page 17: External Routing

    bash-2.05a# bash-2.05a# chcpusn Enter number of database (0 7) Pick a database for this PRI GSM Gateway, it must be free (not previously allocated to another one). Enter 1. string: Enter the first key code for this PRI GSM Gateway Enter 2.

  • Page 18: Web Access Configuration

    critical major minor warning All alarms with an advice of severity level are contained in The Trap Table (Appendix 1). You can choose which alarms should be sent as SMS message and/or e-mail (if enabled in sgsetup!). For this purpose is used file /etc/stargate-traps.conf, where is possible to give severity level to each alarm(trap) and define sending rules for each severity level.

  • Page 19: Testing

    This procedure has to be repeated n times to have all n gateways accessible over the web. 4.3 Testing The first thing to do after configuration is to restart the PRI GSM Gateways services. This forces them to re-read the current configuration files. bash-2.05a# bash-2.05a# service stargate restart To troubleshoot the stargate service use the commands ”service stargate status “...

  • Page 20: Configuration

    SNMP trap IP address (2) [192.168.100.3]: 192.168.30.5 SNMP community [public]: Buster Configuring network interface eth0 ... Configuring network interface eth1 ... Enable e-mail sending ? [YES]: E-mail 'FROM' address [stargate@2n.cz]: remote-tower@control-center.com E-mail 'TO' address [ryba@2n.cz]: watch-tower@control-center.com E-mail subject [Test]: Stargate watch...
  • Page 21 Enable Gateway #0 ? [YES]: Enable Gateway LCR #0 ? [YES]:n Enter Gateway #0 IP address or '-' [192.168.10.3]:192.168.10.2 Enter Gateway #0 user name [2n]: spinner Enter Gateway #0 user password [2n]: secrets Enable Gateway #1 ? [YES]: Enable Gateway LCR #1 ?

  • Page 22: Web Pass

    Enable Gateway #5 ? [YES]: Enable Gateway LCR #5 ? [YES]:n Enter Gateway #5 IP address or '-' [192.168.10.7]:192.168.10.7 Enter Gateway #5 user name [2n]: spinner Enter Gateway #5 user password [2n]: secrets Enable Gateway #6 ? [YES]: Enable Gateway LCR #6 ?

  • Page 23: Starting

    Updating password for user stargateguru 4.4.4 Starting bash-2.05a# bash-2.05a# service stargate restart Shutting down StarGate SNMP daemon: Shutting down StarGate Agent: Shutting down StarGate Trace Logger: Shutting down StarGate Least Cost Routing: [FAILED] Shutting down StarGate Network Server: Starting StarGate SNMP daemon #0 Starting StarGate Network Server #0 Starting StarGate Agent #0 Starting StarGate Trace Logger #0...
  • Page 24 startage 5: OK startage 6: OK startage 7: OK startage 8: DISABLED startage 9: DISABLED...

  • Page 25: Rcu Usage

    5 RCU Usage The RCU can be used in a number of ways as has already been explained in the previous chapters. In the following sections, we will explore methods of retrieving and interpreting the management and accounting data gathered by the RCU. 5.1 Web access To access the managed gateways over the web, open your favorite web browser and for the URL type https://IPaddress.

  • Page 26: Authentication

    5.1.2 Authentication Here, it is enough to type the username and password configured in the RCU with the ‘webpass’ command. Let us visit the ‘Web Overview’ first (Fig.9). Fig.8: Web login dialogue 5.1.3 Web Overview The Web Overview is the main management page as can be seen in the Fig.9. In the center is Fig.9: Web Overview...
  • Page 27 the front view of the PRI GSM gateway. Counting from right, we have the power supply, the CPU card, the AUX card, the PRI card and 16 GSM cards ( In case of Bluestar only 8 of them could be active). When something happens to any of the cards, the card color changes from gray to red.
  • Page 28 Fig.11: PRI GSM gateway statistics Fig.12: CDR and Trace download...

  • Page 29: Web Configuration Of The Gateway

    5.1.4 Web configuration of the gateway This item, which is recommended only for trained technicians, is intended for the configuration of the PRI GSM gateway over the web. If you are not sure of what you are doing please do not use this page. You can configure PRI GSM gateway the same way as it could be done by Stargate(Bluestar, Bluetower) program.

  • Page 30: Snmp Management

    The PRI GSM gateway MIB has to be properly installed in the Network Management Node (NMN). This installation is beyond the scope of this manual (help can be sought from the 2N technical support stuff). When all is installed, SNMP queries can be send from the NMN to the RCU on all the SNMP objects in the PRI GSM gateway MIB.

  • Page 31: Accounting

    source address, which corresponds to the SNMP IP address of the respective PRI GSM gateway (Fig.15) Fig.15: RCU alarms (traps) 5.3 Accounting Besides PRI GSM gateway management, the RCU collects different accounting information. This information can be thereafter retrieved at the discretion of the user in two ways. The first method employs the web interface as has already been mentioned in section 5.1.3.
  • Page 32 Fig.16: RCU accounting data...

  • Page 33: Troubleshooting

    6 Troubleshooting Installing and configuring a system so as to satisfy the expected functionality is only the part of the show. The real challenge is in keeping the system working. The RCU is no exception in this regard, what is worse, there does not exist a question-answer cook book for solving all the possible combinations of error states that may befall the RCU.

  • Page 34: Checking The Databases

    The output of this command can be used against the pre-installation IP map to check whether the gateway ordering and configuration are in agreement. 6.3 Checking the Databases 6.3.1 Gateway Databases The RCU has a total of 21 databases: • Databases stargate0–9 store status information from gateways 0-9. •...
  • Page 35 outgoing calls (ISDN 1 = Locked to GSM) 2 =According to credit Saving call data AT&V, S91 0 = no calls CDRs 1 = successful outgoing 2 = successful incoming 3 = successful incoming + outgoing 4 = not used 5 = all outgoing 6 = all incoming 7 = all incoming + outgoing...

  • Page 36: Stargate (Bluestar) Program Using Rcu As A Tunnel

    NT/M = NT, Master QSIG/M = QSIG, Master QSIG/S = QSIG, Slave PRI2 - TEI Number AT&VI, I01 Not used PRI2 - ISDN layer1 AT&SPR Stargate or Bluestar user manual PRI2 - ISDN layer2 AT&SPR PRI2 - ISDN layer3 AT&SPR PRI2 - Number of AT&XC, AT&XP, current calls...
  • Page 37 Fig. 17: Setting IP address and port Step 2: In the putty menu choose Connection – SSH – Tunnels (Fig. 18). Configure forwarding of a local TCP port (it could be 23 or different) to port 23 (Telnet) of the related PRI GSM gateway.

  • Page 38: Tracing Of The Traffic On Gateways

    Step 5: In the Stargate/Bluestar program, in the list of gateways, add a gateway with IP address 127.0.0.1 and the same port configured as a local port in putty. Step 6: Connect to the new added gateway If You forward more ports in putty, You can connect to a few gateways at the same time using separate Stargate/Bluestar Progam sessions! This way You can use all Stargate/Bluestar Program functions as connected to gateway directly by Telnet.

  • Page 39: Faq

    7 FAQ Q1: All connected gateways do not communicate with the RCU 1-check IP connectivity (ping) 2-make sure that service stargate scripts are running 3-use sgconf to confirm the right configuration and gateway ordering Q2: There is IP connectivity but cannot login to the webview A2: Re-run “webpass”...

  • Page 40: Appendix 1: The Trap Table

    Appendix 1: The Trap Table...
  • Page 41 Base OID: 1.3.6.1.4.1.6530. The Event Log Message in HP OpenView NNM Related Trap ID Source MIB Object Event Form definition Severity trap sgCPUBoard.sgcpuStatus. a value change No response from No response sgcpuSerialPort to NOK serial port from serial port Critical Serial sgCPUBoard.sgcpuStatus.
  • Page 42 sgPRIBoard.sgPRI1Status. a value PRI <port number> sgpri1BusyBChanCurrent increased over Number of busy B PRI - $1 Number <high_up limit> channels increased to of busy B sgPRIBoard.sgPRI2Status. value defined in <Source MIB Object channels sgpri2BusyBChanCurrent sgsetup session Value> increased to $2 Warning a value sgPRIBoard.sgPRI1Status.
  • Page 43 a value SgGSMModuleTab.sgGSM increased over GSM Module <Module ModuleEntry.sgmSIMxASR <Good ASR> Number : Call ( According to ASR value defined in success rate OK: definition chosen in sgsetup <Source MIB Object GSM module $1: sgsetup ) session> Value> ASR OK: $2 Warning...

This manual is also suitable for:

Ateus rcu

Table of Contents