Teles Informationstechnologien GSM04VOIPUS Mobile Gateway User Manual CELLX Box
Teles AG Informationstechnologien Mobile Gateway CELLX Box
Users manual
| Download: |  |
| Mirror Download [FCC.gov] | |
| Document ID | 2293360 |
| Application ID | jiQrUgEzP9v8xolbWIu1lA== |
| Document Description | Users manual |
| Short Term Confidential | No |
| Permanent Confidential | No |
| Supercede | No |
| Document Type | User Manual |
| Display Format | Adobe Acrobat PDF - pdf |
| Filesize | 79.37kB (992083 bits) |
| Date Submitted | 2014-06-12 00:00:00 |
| Date Available | 2014-12-09 00:00:00 |
| Creation Date | 2014-03-20 14:48:23 |
| Producing Software | Acrobat Distiller 7.0 (Windows) |
| Document Lastmod | 2014-03-20 16:05:25 |
| Document Title | CELLX Box |
| Document Creator | FrameMaker 7.0 |
| Document Author: | frfa |
CELLX Box Systems Manual Software version 17.1 CELLX Box Systems Manual TELES COMMUNICATIONS CORP. 2400 Skyfarm Drive, Hillsborough, CA 94010 United States Phone: +1 646-225 65 98 E-Mail: cellx@teles.com Internet: http://www.teles.com/cellx/index.html Software version: 17.1 Revised: 20 March 2014 © Copyright 2014 TELES AG Informationstechnologien. All rights reserved. CELLX®, TELES®, IntraSTAR®, Intra*®, iGATE®, and iSWITCH® are registered trademarks of TELES AG Informationstechnologien. All other trademarks used are the property of their respective owners. The supplied hardware/software systems are protected by copyright and can be used solely by their lawful owners. All text and figures in this publication have been compiled with great attention to detail. Nonetheless, inaccuracies and typographical errors cannot be entirely avoided. TELES AG Informationstechnologien provides this document 'as is' without warranty of any kind, expressed or implied. TELES AG Informationstechnologien reserves the right to make changes in product design or specifications without notice. CELLX Box 17.1 002 Table of Contents Table of Contents Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.1 1.2 1.2.1 1.2.2 1.2.3 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 Implementation scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 CELLX Box last mile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 CELLX Box failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 CELLX Box cost saving model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 System security and hardware overview . . . . . . . . . . . . . . . . 12 2.1 2.2 2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 2.2.6 2.2.7 2.2.8 2.2.9 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 2.2.15 2.3 Safety and security precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 System security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Connecting Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 Antenna Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 Damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 Repairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 Potentially explosive atmospheres . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 Radio wave exposure information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 Personal medical devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 Environmental considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 Protecting the operating system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 CDR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 Network security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 Physical description of the CELLX Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 CELLX Box installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.1 3.2 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.4 Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Unpacking the shipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 Analog wiring (optional for FXS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 Ethernet wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 Antenna cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 Power cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 LED functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 4.1 4.2 4.3 4.4 4.5 4.6 4.6.1 4.6.2 Configuration tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Skills needed for a configuration setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Assigning an IP address to the CELLX Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Connecting to the CELLX Box with GATE Manager . . . . . . . . . . . . . . . . . . . . . . . . . .26 Required information for further scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 The CELLX Box config files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 The pabx.cfg config file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 The ip.cfg config file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 CELLX box 17.1/002 Page 3 Table of Contents 4.6.3 4.6.3.1 4.6.3.2 4.6.3.3 4.6.4 4.6.5 The route.cfg config file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 The Restrict variable used in the route.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 The MapAll variable used in the route.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 The Redirect variable used in the route.cfg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 The route.cfg for the last mile scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 Configuration files for VoIP scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 Adapting the config files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 5.1 5.2 5.2.1 5.2.2 5.3 5.3.1 5.3.1.1 5.3.1.2 5.3.1.3 5.3.2 5.3.2.1 5.3.2.2 5.4 5.5 5.6 5.7 Editing the config files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 Securing the CELLX Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 Setting the password for the GATE Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 Adjusting the firewall setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 VoIP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 VoIP settings for a public VoIP provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 VoIP profile for the provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 Registrar profile defined for the provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 Call routing for outgoing calls to the provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 VoIP settings for local SIP UA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 VoIP profile for the local SIP UAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 Call routing for calls to and from the local SIP device . . . . . . . . . . . . . . . . . . . . . . . .52 Rerouting or failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Cost saving routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53 Callback initiated by SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 Mail to SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 6.1 6.1.1 6.1.2 6.1.3 6.1.4 6.2 Call detail records (CDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 Activating peer data for VoIP calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 CDRs for callback and two stage calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 Specific cause values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 Missed calls list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 CELLX box 17.1/002 Page 4 Preface Preface In this manual This manual is set up to guide you through the installation of your CELLX Box. It is written for network administrators who use and maintain the gateway. To use this manual you should have some experience working with networking devices and be familiar with the concepts and terminology of telecommunication technology. Make sure you familiarize yourself thoroughly with the safety and security precautions detailed in Chapter 2 System security and hardware overview on page 12 before you begin to install your CELLX Box. TELES is not liable for any damage or injury resulting from a failure to follow these safety and security instructions! In addition to this manual there is a parameter manual summarizing the configuration parameters used in the config files. Conventions This document uses the following typographic conventions: Bold – important information, and items from the GUI and the menu. Code – file names, variables, and constants in config files or commands in body text. "Conventions" on page 5 – cross-references can be accessed in the PDF by a single mouse click. Configuration data or extracts are written in single-column tables with a gray background. Safety Symbols The following symbols are used to indicate important information and to describe levels of possible danger. Note Useful information with no safety implications. Attention Information that must be adhered to as it is necessary to ensure that the system functions correctly and to avoid material damage. Warning Danger. Could cause personal injury or damage to the system. Dangerous voltage Could cause injury by high voltage and/or damage the system. Electrostatic discharge Components at risk of discharge must be grounded before being touched. Explosion hazard Injury hazard due to explosions endangering the person or the system. CELLX box 17.1/002 Page 5 Organization Organization This guide is organized into the following chapters. Chapter 1 “Overview”: describes the general features of the CELLX Box and the main features for VoIP, telephony, and mobile. Chapter 2 “System security and hardware overview”: starts with the safety and security precautions. Make sure that everyone who works with the CELLX Box is aware of these precautions. The CELLX Box described at the end of this chapter. Chapter 3 “CELLX Box installation”: contains information on hardware installation of your CELLX Box. Follow the easy instructions to set up your CELLX Box in a matter of minutes. Chapter 4 “Configuration”: describes how to connect the CELLX Box to the GATE Manager and provides an introduction to the configuration. Before you begin you must be familiar with the hardware, and the CELLX Box must be installed at the location and connected as described in Chapter 3 "CELLX Box installation" on page 19. After installation, the CELLX Box is ready to carry out maintenance tasks using the GATE Manager, and to configure implementation scenarios using VoIP. Chapter 5 “Adapting the config files”: describes some frequent configuration scenarios. Chapter 6 “Maintenance”: describes the CDR and trace maintenance tasks. CELLX box 17.1/002 Page 6 1 Overview 1 Overview This chapter describes the general features of the CELLX Box and the main features for VoIP, telephony, and mobile. The CELLX Box is a media converter that facilitates the connection of voice over IP (VoIP) with mobile networks. The connection to telephone equipment using FXS is optional. It converts line-based transmission on mobile side to packet-based transmission in the IP network and vice versa. Incoming traffic arrives at one CELLX Box, which routes the calls according to their destination and attributes. Table 1.1 list the main variants of the CELLX Box. Table 1.1 Possible product variants of the CELLX Box Product name Description CELLX 3G–4 CELLX Box with four 3G mobile interfaces. CELLX GSM–4 CELLX Box with four GSM mobile interfaces. CELLX 3G–4 FXS CELLX Box with four 3G mobile and four FXS interfaces. CELLX GSM–4 FXS CELLX Box with four GSM mobile and four FXS interfaces. CELLX 3G–4 BRI-2 CELLX Box with four 3G mobile, two BRI interfaces. CELLX GSM–4 BRI-2 CELLX Box with four GSM mobile, two BRI interfaces. The CELLX Box contains two Gigabyte Ethernet interfaces to the IP network. 1.1 Features Mobile 4 GSM or 3G (UMTS) channels Built-in SIM-card server support for unlimited SIMs per channel with vGATE SIM Unit. Individual timers for each SIM /call Possible to configure individual mobile bands Radius accounting request contains SIM’s IMSI to enable SIM-specific billing Support for vGATE sub-limits Number portability Mobile-specific configuration parameters now definable per mobile network (LAIN) vGATE RoutingManager support E-mails to SMS: support for SMS delivery report CELLX box 17.1/002 Page 8 1 Overview VoIP 8 media channels H.323 v.4 / SIP v.2 signaling (RFC 3261), operating in parallel Various audio codecs: G.711, G.723.1, G.726, G.728, G.729, GSM, iLBC Fax: T.38 Data: clear channel RTP multiplexing (reduces bandwidth required for RTP data by up to 60%) ENUM client Echo cancellation G.168–2000 Silence suppression, comfort noise generation, voice activity detection Support for multiple gatekeepers and multiple registrars STUN client Traffic shaping Adjustable time interval for echo detection in VoIP FXS (optional) 4 analog lines (FXS) Fax/modem detection (UDT) Charging impulse (12/16kHz) Integrated line echo cancellation Power feeding for FXO devices Dial-tone and ring-tone generation Calling Line Identification (CLIR) on FXS ports LCR engine Multiple VoIP-provider logins Multiple PSTN routing methods Multilevel alternative routing Dynamic failover to mobile network Dynamic failover to VoIP General 1.2 Ringtone generation Configurable ToS/DivServ AOC generation 2nd separate Gigabit Ethernet interface Status indication via LEDs Integrated mail client capable of SMTP authentication E-mail messages can trigger calls and play attached announcements Automatic test call Redial function Autodial function Implementation scenarios The CELLX Box supports the following implementation scenarios: CELLX Box last mile (see Chapter 1.2.1 on page 10), CELLX Box failover (see Chapter 1.2.2 on page 10), and CELLX Box for cost savings (see Chapter 1.2.3 on page 11) CELLX box 17.1/002 Page 9 1 1.2.1 Overview CELLX Box last mile The CELLX Box provides voice via the mobile network, which offers a reliable alternative to traditional landline connections for voice connections. In rural areas with no landline available, all you need for immediate communication is an CELLX Box and mobile network coverage. The CELLX Box works as a gateway to the mobile interface for voice. local network CELLX Figure 1.1 1.2.2 PSTN mobile network The CELLX Box in a last mile scenario CELLX Box failover The CELLX Box is used if the primary VoIP connection fails, in which case it routes outgoing calls automatically via mobile networks. In this case the CELLX Box works as an mobile gateway that can augment landline connectivity with wireless connectivity to the mobile network. In case of landline connectivity failure, the CELLX Box provides a backup solution to maintain voice communications. The CELLX Box will route all outbound calls to the mobile network. Inbound calls from the mobile network will be routed to the connected telephone equipment. local network PSTN CELLX mobile network VoIP Figure 1.2 The CELLX Box in a failover scenario CELLX box 17.1/002 Page 10 1 1.2.3 Overview CELLX Box cost saving model The CELLX Box also has an effective call routing engine. It turns expensive fixed–to–cellular calls into cheaper cellular–to–cellular calls. Calls from the office to staff cellular phones may even be free of charge. Cellular calls outside the home network are usually subject to high outgoing roaming fees. A CELLX Box callback solution may help to replace those fees with lower incoming roaming fees. This will help to reduce your calling costs significantly. local network CELLX mobile network PSTN VoIP Figure 1.3 The CELLX Box in a cost saving scenario CELLX box 17.1/002 Page 11 2 System security and hardware overview 2 System security and hardware overview This chapter starts with the safety and security precautions. Make sure that everyone who works with the CELLX Box is aware of these precautions. The CELLX Box described at the end of this chapter. 2.1 Safety and security precautions Please be sure and take time to read this section to ensure your personal safety and proper operation of your CELLX Box. To avoid personal injury or damage to the CELLX Box, please follow all safety instructions before you begin working on your CELLX Box. CELLX Boxes are CE certified and fulfill the legally specified safety regulations, including EMC (electromagnetic compatibility) and LVD (low voltage directive) requirements. The manufacturer assumes no liability for consequential damages or for damages resulting from unauthorized changes. The symbols described on Chapter "Safety Symbols" on page 5 are used to indicate important information and to describe levels of possible danger. Before you begin to setup the CELLX Box, please take note of the following advice. Danger of electric shock - do only use the power supply included in delivery. Do not use a broken power supply. The power supply run on 110 V. Bear in mind that telephone and WAN lines are also energized and can cause electric shocks. Wire your system using only the cables included in the package contents. Use only proper Ethernet cables. Do not insert foreign objects into openings in the device. Conductible objects can cause shortcircuiting that results in fire, electric shock, or damage to the device. Never work on the CELLX Box or connect or disconnect cables during a thunderstorm. Do not open the CELLX Box or its power supply. Changes in the device are not permitted. Be sure to respect country-specific regulations, standards or guidelines for accident prevention. Tips for EMC Protection: Use shielded cables. Do not remove any housing components. They provide EMC protection. 2.2 System security This section describes all points crucial to the CELLX Box’s system security. 2.2.1 Transport Disconnect all cables before moving the CELLX Box. As a protection against jolts and impact, this device should be transported in its original packaging only. Condensation can occur if the device is brought from a cold environment into the room where it is to be operated. The device must be absolutely dry prior to being operated. Accordingly, an acclimatization period of at least two hours is required. 2.2.2 Operating conditions The CELLX Box’s location must support normal operation in accordance with EN ETS 300 386. Make sure you install the system in a clean, dry, dust-free location. If possible, use an air-conditioned site. Do not subject the device to direct sunlight. CELLX box 17.1/002 Page 13 2 System security and hardware overview The site must be free of strong electrical or magnetic fields, which cause disrupted signals and, in extreme cases, system failure. The site must maintain a temperature between 32°F and 90°F. Be sure to guard against temperature fluctuations. Resulting condensation can cause a short circuit. The humidity level may not exceed 80%. To avoid overheating the system, make sure the site provides adequate ventilation. Power: The electrical facilities must comply with applicable regulations. The operating voltage and frequency may not exceed or fall below what is stated on the label of the power supply. Antenna: TELES contains no provision or protective device against power surges or lightning strikes. The installation of the antenna must fulfill all necessary safety requirements. Employ the services of a professional antenna installer. Regular servicing ensures that your CELLX Box runs trouble-free. Servicing also includes looking after the room in which the CELLX Box is set up. Ensure that the air-conditioning and its filter system are regularly checked and that the premises are cleaned on a regular basis. Electrical devices may not be used by individuals who are not aware of the dangers of electricity and/or incorrect use thereof. Use shielded cables for EMC protection. Do not remove any housing components. They provide EMC protection. 2.2.3 Connecting Cables Lay all cables in a manner that is not hazardous to pedestrian traffic. The power cord must be unplugged from the AC line socket in order to completely disconnect the equipment (e.g. in emergencies). Cables should not be connected or disconnected during thunderstorms! 2.2.4 Antenna Input The antenna must be protected against destruction due to lightning. The base of the antenna must be grounded. 2.2.5 Damage For safety reasons, if the CELLX Box exhibits visible damage or has been exposed to moisture, then further operation should be discontinued! In this case, please ensure that the CELLX Box is disabled so it cannot be used by anyone else. 2.2.6 Repairs Repairs must be performed only by qualified personnel. Only use replacement parts that comply with device safety standards. Always unplug the AC line connector before opening the device! CELLX box 17.1/002 Page 14 2 2.2.7 System security and hardware overview Upgrades Only install system upgrades that are specifically intended for this device. Installing other upgrades can damage the system or violate safety standards and radio interference regulations. 2.2.8 Cleaning Before cleaning, unplug the AC line connector. Do not use scouring powder or solvents harmful to plastics. Do not allow liquids to penetrate into the interior of the CELLX Box. A dry cloth suffices for cleaning the housing surface. A cloth dipped in water containing a mild detergent and then wrung out well can be used for heavier stains. 2.2.9 Potentially explosive atmospheres Do not use this product in an area where a potentially explosive atmosphere exists. 2.2.10 Radio wave exposure information This product is a low-power radio transmitter and receiver. During operation, it emits low levels of radio frequency energy. Several organizations, e.g. ICNIRP (International Commission on Non-Ionizing Radiation Protection) and IEEE (The Institute of Electrical and Electronics Engineers Inc.) developed safety guidelines about permitted levels of radio wave exposure for the general population, based on thorough scientific studies. To meet the maximum permissible value for radio wave exposure, a distance of 20 centimeters must be kept if running one mobile channel, and an additional 20 centimeters for every further mobile channel. 2.2.11 Personal medical devices Radio waves may affect the operation of cardiac pacemakers and other implanted equipment. To limit the risk, a distance of 20 centimeters must be kept if running one mobile channel, and an additional 20 centimeters for every further mobile channel. If you suspect that interference is taking place, immediately move away from the device. 2.2.12 Environmental considerations Take care to ensure proper disposal of the CELLX Box when it is no longer to be used. 2.2.13 Protecting the operating system Changing configuration data may lead to malfunctions and/or misrouting, as well as possible consequential damage. Make changes at your own risk. TELES is not liable for any damage resulting from, or in relation to, such changes. Please thoroughly check any changes you or a third party have made to your configuration! Make sure the flash disk contains enough storage space. Download log files and delete them from the CELLX Box on a regular basis to ensure your CELLX Box’s reliability. All files with the extension *.log can be deleted. CELLX box 17.1/002 Page 15 2 2.2.14 System security and hardware overview CDR files Call Detail Records are intended for analysis of the CELLX Box’s activity only. They are not designed to be used for billing purposes, as the times they record are not always exact. 2.2.15 Inaccuracies in the generation of CDRs may occur for active connections if traffic is flowing on the system while modifications in configuration or routing files are activated. Network security Every day hackers develop new ways to break into systems through the Internet. While we takes great care to ensure the security of its systems, any system with access through the Internet is only as secure as its user makes it. Therefore, to avoid unwanted security breaches and resulting system malfunctions, you must take the following steps to secure your CELLX Box if you connect it to the Internet: Use an application gateway or a packet firewall. To limit access to the CELLX Box to secure remote devices, delete the default route and add individual secure network segments. Access to the CELLX Box via Telnet, FTP or GATE Manager must be password protected. Do not use obvious passwords (anything from sesame to your mother-in-laws maiden name). Bear in mind: the password that is easiest to remember is also likely to be easiest to crack. The firewall must support the following features: Protection against IP spoofing Logging of all attempts to access the CELLX Box The firewall must be able to check the following information and only allow trusted users to access the CELLX Box: IP source address IP destination address Protocol (whether the packet is TCP, UDP, or ICMP) TCP or UDP source port TCP or UDP destination port ICMP message type For operation and remote administration of your CELLX Box, open the following ports only when the indicated services are used: Table 2.1 Default ports used for specific services Service Protocol Port FTP TCP 21 (default, can be set) Telnet (for debug access only) TCP 23 (default, can be set) SMTP TCP 25 DNS forward UDP 53 HTTP TCP 80 (default, can be set) NTP UDP 123 CELLX box 17.1/002 Page 16 2 Table 2.1 2.3 System security and hardware overview Default ports used for specific services (continued) Service Protocol Port SNMP UDP 161 (default, can be set) H.225 registration, admission, status UDP 1719 (default, can be set) H.225 signaling TCP 1720 (default, can be set) GATE Manager TCP 4445 (default, can be set) SIP signaling UDP / TCP 5060 (default, can be set) RTP UDP 29000-29120 (default, can be set) Physical description of the CELLX Box Figure 2.1 shows front and rear views of the CELLX Box. LED 1 2 3 CELLX 12V= USB Antenna SIM 1 SIM 2 SIM 3 SIM 4 Front view of the CELLX Box FXS1 FXS2 FXS3 FXS4 ETH2 ETH1 Rear view of the CELLX Box Figure 2.1 Front and rear views of the CELLX Box CELLX box 17.1/002 Page 17 2 System security and hardware overview Table 2.2 summarizes the technical data of the CELLX Box. Table 2.2 Technical data of the CELLX Box Feature Description Dimensions and weight Height: 56 mm (2.20 in.) Width: 243 mm (9.57 in.) Depth: 166 mm (6.54 in.) Weight: 0.7 kg (1.54 lbs.) Interfaces 2 Gigabit Ethernet: on rear panel optional 4 FXS or 2 BRI: on rear panel 1 mobile antenna connector: SMA (on front panel) 1 USB – not active / usable (on front panel) 1 power 12 V (on front panel) Jacks The jacks on the CELLX Box have fulfilled the requirements of the following safety standards. ETH jacks: SELV FXS jacks: TNV3 ISDN jacks: SELV LED Please see Table 3.1 on page 22 Power supply Type: DSA-42D-12 1 120350 Input voltage: 100–240 V AC; 50 / 60 Hz; 1,2 A maximum Output voltage: 12V; 3.5 A; 42 W Dimensions: 118 (L) x 48.5 (W) x 35 (H) mm Weight: 230g Jack plug: 5.5 x2.1x12mm Tested and certified as TÜV-GS (EN60950-1), UL/CUL (UL60950-1), T-LICENSE (BS EN60950-1), SAA (AS/NZ60950), CCC (GB4943) EMI standards: FCC (part 15 class B), CE(EN55022), C-TICK, GB9254, GB17625.1 CELLX box 17.1/002 Page 18 3 CELLX Box installation 3 CELLX Box installation This chapter contains information on hardware installation of your CELLX Box. Follow the easy instructions to set up your CELLX Box in a matter of minutes. 3.1 Checklist The following checklist provides step-by-step installation instructions. 1. 2. 3. 4. 5. 6. 7. 3.2 Check the package contents Install the CELLX Box Connect the analog lines (FXS) or ISDN lines to telephone equipment Connect the Ethernet to the LAN Connect the antenna Connect the power supply Check functionality (using the LEDs) Unpacking the shipment Unpack the components and check that the shipment is complete. Make sure nothing is missing. Your CELLX Box package contains the items listed here: 1 CELLX Box 1 power supply 1 RJ-45 LAN cable with gray connectors 1 antenna with magnetic mount Check that there is no equipment damage. Immediately report any visible transport damages to customer service. Do not use the device if it is damaged or if there are signs of malfunction. Instead, send it to customer service or dispose of it properly (not with the public trash). Mounting the CELLX Box If desired, you can mount the CELLX Box on the wall with two screws. Figure 3.1 shows the drilling details. 1¾" max ¼" screw head with max 1/8" dpth Figure 3.1 Holes on the back of the CELLX Box Drilling into electrical wiring can cause drill bit and chuck to become electrically live. Do not touch the chuck or metal housing when drilling into a wall; grasp only the insulated handle(s) provided on the tool. CELLX box 17.1/002 Page 20 3 3.3 CELLX Box installation Cabling Before you carry out any assembly or servicing tasks, please read the safety instructions given in Chapter 2.1 on page 13. Danger of electric shock - the power supply runs on 230 V. Use only the original power supply. Do not use the power supply if it is damaged. Bear in mind that telephone and WAN lines are also energized and can cause electric shocks. Wire your system using only the cables included in the package contents. Use only proper Ethernet cables. Hold the device by its housing when you unplug it. Wall outlets can become mechanically overloaded; do not pull on the cord. Make sure you have the following connections in place: Ethernet connection FXS or ISDN connection to the telephone equipment Power (230 V) If you do not use the supplied cable, make sure you use only a shielded Ethernet cable! 3.3.1 Analog wiring (optional for FXS) You connect analog telephone device on the FXS ports. When the device is properly connected, LED 6 blinks when you pick up the handset. Figure 3.2 shows the standard pin assignment for each FXS analog port. Figure 3.2 3.3.2 Analog wiring scheme Ethernet wiring This step is only needed for the advanced configuration in the failover (see Chapter 1.2.2 on page 10) and cost saving model (see Chapter 1.2.3 on page 11) scenarios, or for maintenance work on the CELLX Box. Use the three-meter cable with gray connectors to connect the CELLX Box’s Ethernet port ETH1 to an Ethernet switch in your network. After successful connection, the LEDs on the Ethernet switch blinks. 3.3.3 Antenna cabling Place the antenna near a window or another place with good reception of the mobile signal. Screw on the antenna to the SMA connector at the front of the CELLX Box. CELLX box 17.1/002 Page 21 3 3.3.4 CELLX Box installation Power cabling Plug the power supply directly into the outlet. Make sure the power outlet is easily accessible at all times. After successful connection, the CELLX Box boots – a running light indicates the initialization process. During the boot procedure, LED1 blinks. If the software is up LED 1 is on. Unplug the device if you do not intend to use it for an extended period of time. 3.4 LED functionality The CELLX Box has the status LEDs described in Table 3.1. Table 3.1 CELLX Box LEDs LED Description 1 – power CELLX Box processor power: Off: power off On: power on Blinking: starting. 2 – 5 mobile state State of the mobile module: On: registered Blinking: SIM not plugged / not registered 6 – FXS State of the FXS interfaces: Off: no activity ON all FXS interfaces are active Blinking: one or more connections are active 7 – USB State of the USB interface is not supported: Always off: After the successful start LED 1 is on – showing that the system of the CELLX Box is started, LED 2–5 are on showing that calls using the mobile modules are possible, LED 6 blinks after a pick up of a connected telephone. CELLX box 17.1/002 Page 22 4 Configuration 4 Configuration This chapter describes how to connect the CELLX Box to the GATE Manager and provides an introduction to the configuration. Before you begin you must be familiar with the hardware, and the CELLX Box must be installed at the location and connected as described in Chapter 3 "CELLX Box installation" on page 19. After installation, the CELLX Box is ready to carry out maintenance tasks using the GATE Manager, and to configure implementation scenarios using VoIP. 4.1 Configuration tools There are two applications available for CELLX Box remote maintenance: Teles Quickstart Teles GATE Manager Quickstart’s purpose is to initially assign an IP address to your CELLX Box. All other configuration and maintenance tasks are performed with the GATE Manager application. Before you can continue, you must download the Quickstart and GATE Manager applications from http://195.4.12.80/agw. Download the version of these two applications that best matches your operating system. These files will be compressed zip files that your operating system already probably already extract. Extract the files, then run the installer found in each. 4.2 Skills needed for a configuration setup Be well versed in telecommunication technology (know the basic concepts of mobile, FXS, VoIP, and IP technology). Know the basics of Windows OS (handle files, install software, download files). Handle a text editor (e.g. notpad++). Be familiar with configuring a device with the help of config files. Before you can start the configuration you have to do the following: 1. Assign IP address, netmask and default gateway to the CELLX Box (see Chapter 4.3 on page 24). 2. Install the GATE Manager and add the CELLX Box to the GATE Manager. 4.3 Assigning an IP address to the CELLX Box Each computer that is to communicate with the CELLX Box requires a network connection. Please have the following information available for connection to your network: IP address in your local network for the CELLX Box to be configured Netmask for the CELLX Box to be configured Default gateway for CELLX Box to be configured Bear in mind that the pre-configured CELLX Box’s default IP address is 192.168.1.2. If this IP address is already being used in your local network, you must run Quickstart without a connection to your local network. This can be done using a back-to-back Ethernet connection from your computer to the CELLX Box. CELLX box 17.1/002 Page 24 4 Configuration Quickstart is a Windows application that helps you to configure the IP settings of your CELLX Box quickly and conveniently without changing any network settings on your computer. 1. Launch Quickstart. 2. If Quickstart detects more than one network interface on your computer, you will be prompted to select the LAN interface from a drop-down menu. Select the interface that is in the same physical network as your CELLX Box. 3. If a Windows Security Alert message appears asking if Quickstart is to be blocked, click Unblock. 4. Quickstart automatically starts scanning your network within the same Ethernet broadcast domain. As soon as your CELLX Box has been detected you can click Stop to stop the scanning. On the Quickstart screen, double click on the CELLX Box Identifier to continue. CELLX box 17.1/002 Page 25 4 Configuration 5. The IP settings window appears. Select the Ethernet Controller eth1/emac0 and enter the appropriate network settings and click Finish to continue. To find out your local IP settings with the Windows command ipconfig: Open an CLI (Windows-key + r). Type cmd, and press Enter. Type ipconfig. For more information see here. If DHCP is used, find out Back Finish Cancel which IP range is free for fixed IP addresses (often the DHCP server is the same as the default gateway). 6. It can take up to five minutes for the CELLX Box to reboot and apply your settings. 4.4 Connecting to the CELLX Box with GATE Manager 1. After you have assigned an IP address to your CELLX Box, assign the CELLX Box to the GATE Manager. 2. Start the GATE Manager application and connect to your CELLX Box. 3. Select the Default group or right-click in the window on the left and select New Group. Enter a group name in the Group field and a Comment in the next field. Confirm with OK. 4. To enter your CELLX Box information, right-click the right pane in the GATE Manager window and select New System from the context menu. Toolbar Connectionbar Main dialog Navigation tree Status bar CELLX box 17.1/002 Page 26 4 Configuration 5. The Edit System dialog box will appear. Enter a meaningful name for your CELLX Box to distinguish it from any others you plan to use. Enter the CELLX Box's IP address. Click OK. 6. Click the green Connect button to connect to your CELLX Box. Now you can run the maintenance tasks described in Chapter 6 "Maintenance" on page 57. Before you go on with editing the config files, read the hints for the needed information in Chapter 4.5. After that familiarize yourself with the config files as described in Chapter 4.6 on page 29. 4.5 Required information for further scenarios Let’s have a look at a typical deployment scenario for the CELLX Box, shown in Figure 4.1. There are four clouds. The CELLX Box is connected to three of them: 1. the local and the telephone network with a PBX and two telephones (local network), 2. the mobile network connected with the public PSTN network, and 3. the VoIP network connected with the public PSTN network. There are three types of hardware interfaces on the CELLX Box: 1. FXS – connects the CELLX Box with the telephones/PBX from telephone network 2. mobile – connects the CELLX Box with the mobile network 3. LAN – connects the CELLX Box with VoIP equipment (local and external VoIP devices). The next task in the configuration is the activation of the interfaces – the configuration is already done for FXS and mobile, but some settings need to be made for VoIP. CELLX box 17.1/002 Page 27 4 Configuration After that, the routing between the interfaces must be configured. local network CELLX mobile network PSTN VoIP Figure 4.1 General scenario for CELLX Box deployment As shown in Figure 4.1 you need to know the following: the local IP network the CELLX Box is integrated into: a fixed IP address, net mask and a default gateway (already done as described in Chapter 4.3 on page 24). the connected telephone equipment (PBX, telephones): which interface is used for which equipment; what are the telephone numbers (internal and external) used for this equipment? the VoIP configuration: You need a contract with a VoIP provider who provides public telephone numbers, a SIP proxy and a registrar. They are needed so that incoming calls from public PSTN network can reach the CELLX Box, and from there your telephone equipment. Your CELLX Box must be accessible for calls from the VoIP provider. For internal VoIP you need your equipment settings. the configuration of your mobile module providing the connection to the mobile network. CELLX box 17.1/002 Page 28 4 Configuration Before you start with the configuration you need the information summarized in Table 4.1. Table 4.1 4.6 information needed to configure a CELLX Box Information Example Description ETH1 IP settings IP address: 172.20.25.87 Net mask: 2550.255.0.0 Default Gw: 172.20.0.78 The IP interface ETH1 is used for configuration and maintenance of the CELLX Box. DHCP is often used in local networks. The CELLX Box works as a gateway and needs a fixed IP configuration. Use an IP address that is outside the DHCP address range. Interface definition for FXS1 – FXS4 (if present) Addr 10 – 13 Telephone numbers used for the FXS interfaces: 100, 101, 102, and 103 This address is needed to send VoIP calls to the FXS ports. The telephone number 100 is assigned to controller 10, 101 to controller 11 and so on. Interface definition for VoIP SIP UDP VoIP profile: VoIP, 172.20.25.11/32; user; passwd Registrar profile: VoIP. 172.20.15.12; user, passwd You need a SIP VoIP profile, and a Registrar profile to get calls over the Ethernet interface. The CELLX Box config files This chapter gives an overview of the config files of the CELLX Box. Configuration of CELLX Boxes is managed in the files listed in Table 4.2: Table 4.2 Configuration files File Function ip.cfg This file is for the basic configuration of the Ethernet interfaces. pabx.cfg This file is for system-specific and port-specific settings. route.cfg This file is for call routing entries. Changing configuration data may lead to malfunctions and/or misrouting, as well as possible consequential damage. All changes are made at your own risk. TELES is not liable for any possible damage out of or in relation with such changes. Therefore please thoroughly check any changes you or a third party made to your configuration. These config files contain all system-specific settings and are used when the system starts. Handle the config files as following: 1. Download the configuration file with the GATE Manager. 2. Save a copy of the configuration file. 3. Edit the configuration file on your local PC with a text editor, e.g. notepad++ (not with a text program like MS Word). CELLX box 17.1/002 Page 29 4 Configuration 4. Transfer the new configuration file to the CELLX Box and activate the new configuration. Changes in the ip.cfg and pabx.cfg require a restart of the CELLX Box. The configuration files are divided into sections. These sections always begin with a line entry in square brackets. The basic required sections are listed in Table 4.3. Table 4.3 Required configuration file sections Section In config file Description [System] pabx.cfg route.cfg ip.cfg Every config file must be started with this section. All previous before will ignored. This section contains the system’s basic settings. [eth1] ip.cfg This section contains the IP configuration for the first Ethernet interface. [iptables] ip.cfg This section contains the firewall settings. [Voip:] route.cfg This section contains the VoIP profile. [Registrar: ] route.cfg This section contains the registrar profile used in the VoIP profile. Comments included in these configuration files must begin with a semicolon. Comments can also be placed at the end of the code line. Configuration files must end with an empty line. Every section contains one or more expressions. In a expression, a keyword or value is assigned to a variable. Then, additional options are possible. An equal sign without spaces is placed between keyword and variable. Example 4.1 The first part of the pabx.cfg [System] PABXName=CELLX-4S_FXS-4 ;(1) As shown in Example 4.1: 4.6.1 the section is [System], the expression is “PABXName=CELLX-4S_FXS-4“, the variable in the expression is PABXName, the value is “CELLX-4S_FXS-4“, the rest “(1)“ of the line after the semicolon is a comment. The pabx.cfg config file The pabx.cfg file contains the definition of the controller which is needed for routing, and the location of the log files needed for maintenance. Only some small changes are needed in this file: change the remote password and if necessary DNS, and NTP adjustments, and SMTP configuration. CELLX box 17.1/002 Page 30 4 Configuration Example 4.2 shows a pabx.cfg file for the last mile scenario. Example 4.2 pabx.cfg for the last mile scenario [System] PABXName=CELLX_GSM-4_FXS-4 ; (1) NameServer=8.8.8.8 ; (2) NtpServer=pool.ntp.org Timezone=CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00 ; Central European Time ActionLog=/boot/protocol.log weekly 1200 3 TraceLog=/boot/trace.log daily 900 7 MsgLog=/boot/msg.log weekly 1200 3 Failedlog=/boot/failed.log daily 1200 7 Log=/boot/cdr.log daily 1200 7 ; (3) StatisticTime=/boot/asr.log 00:00 11111111 Controller00=10 Controller01=11 Controller02=12 Controller03=13 Controller04=20 Controller05=21 Controller06=22 Controller07=23 Controller08=40 Controller09=41 FXS ; (4) FXS FXS FXS GSM ; (5) GSM GSM GSM VOIP ; (6) DTMF Subscriber00=TRANSPARENT Subscriber01=TRANSPARENT Subscriber02=TRANSPARENT Subscriber03=TRANSPARENT Subscriber04=TRANSPARENT Subscriber05=TRANSPARENT Subscriber06=TRANSPARENT Subscriber07=TRANSPARENT Subscriber08=TRANSPARENT Subscriber09=TRANSPARENT #SimCtrlUnitAddress= ;*END CONFIG* ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ANA[0,16,800,250,1500,80,12800,1,1,500,10500,10000,0,1000] NODE[0000] ; (7) ANA[0,16,800,250,1500,80,12800,1,1,500,10500,10000,0,1000] NODE[0001] ANA[0,16,800,250,1500,80,12800,1,1,500,10500,10000,0,1000] NODE[0002] ANA[0,16,800,250,1500,80,12800,1,1,500,10500,10000,0,1000] NODE[0003] GSM[0000,00000,+000000,1,1,1,SIM4,IMSI,BAND(6),TRACE(fecc)] ALARM NODE[0004] GSM[0000,00000,+000000,1,1,1,SIM4,IMSI,BAND(6),TRACE(fecc)] ALARM NODE[0005] GSM[0000,00000,+000000,1,1,1,SIM4,IMSI,BAND(6),TRACE(fecc)] ALARM NODE[0006] GSM[0000,00000,+000000,1,1,1,SIM4,IMSI,BAND(6),TRACE(fecc)] ALARM NODE[0007] ALARM CHMAX[8] NODE[0008] CHMAX[4] DTMF[60] NODE[0009] (1) Definition of the CELLX Box name. This name is displayed in the GATE Manager. (2) DNS and NTP settings of the CELLX Box. Adjust these settings to suit your needs. (3) Path to the call detail records (CDR). (4) Definition of the FXS controller. The controller numbers (10 … 13) are needed for the routing. (5) Definition of the mobile controller. The controller number (20 … 23) are needed for the routing. (6) Definition of the VoIP controller for all VoIP channel. The controller number (40) is needed for the routing. (7) Definition of the settings for FXS controller. More information about the pabx.cfg is contained in the Chapter 5.2 on page 44 ff. about the configuration. CELLX box 17.1/002 Page 31 4 4.6.2 Configuration The ip.cfg config file This file contains the main part of the IP configuration of the CELLX Box. Example 4.3 shows an ip.cfg similar to the factory settings. Only the default gateway and the IP address of the first Ethernet interface is set here. These settings are already done during the installation with the Quickstart tool. The firewall rules are commented out. If the CELLX Box is used behind a firewall in a local network the firewall on the CELLX Box is not needed. Example 4.3 ip.cfg with default gateway and IP address set [System] DefaultGW=192.168.1.1 [eth1] IpAddress=192.168.1.2 netmask 255.255.0.0 [iptables] ; iptables ; iptables ; iptables ; iptables ; iptables ; iptables ; iptables -P -P -P -A -A -A -A INPUT DROP FORWARD DROP OUTPUT ACCEPT INPUT -d 127.0.0.1 -j ACCEPT INPUT -p icmp --icmp-type echo-request -j ACCEPT INPUT -p icmp --icmp-type echo-reply -j ACCEPT INPUT -p tcp -i eth1 --dport 4445 -j ACCEPT Example 4.4 shows the configuration part of the ip.cfg used to configure a default gateway with the IP address 192.168.1.1, and an additional route is set fro the network 10.1.2.0/16 using the gateway 172.20.17.125 over eth2. The IP address of the second IP interface is set to 172.20.27.224 with the netmaks 255.255.0.0. Example 4.4 ip.cfg with the IP configuration of the second IP interface [system] DefaultGW=192.168.1.1 Route=-net 10.1.2.0 netmask 255.255.255.0 gw 172.20.27.125 dev eth2 [eth2] IpAddress=172.20.27.224 netmask 255.255.255.0 The section [dnsmasq] shown in Example 4.5 shows an DHCP setup for eth1. All DHCP requests will be answered and the CELLX Box assign an IP address form the range 192.168.1.10 until 192.168.1.90. The default gateway is the CELLX Box on the eth1 interface and the DNS settings from the file /etc/resolv.conf will be assigned as name server to the hosts. Example 4.5 ip.cdf with DHCP setup [dnsmasq] bogus-priv filterwin2k user=root interface=eth1 domain=teles dhcp-range=192.168,1.10,192.168.1.90,12h cache-size=150 resolv-file=/etc/resolv.conf CELLX box 17.1/002 Page 32 4 Configuration Example 4.6 shows in addition to the examples before the settings for a default gateway on 192.168.1.1, and active NAT masquerading for the internal network 192.168.1.0/24. Example 4.6 Complete ip.cfg with default gateway and NAT [System] DefaultGW=192.168.1.1 [eth1] IpAddress=192.168.1.224 netmask 255.255.0.0 [eth2] IpAddress=172.20.27.224 netmask 255.255.255.0 [iptables] iptables -t iptables -P iptables -P iptables -P iptables -A iptables -A nat -A POSTROUTING -o eth2 -s 192.168.1.0/24 -j MASQUERADE INPUT -j DROP FORWARD -j DROP OUTPUT ACCEPT INPUT -s 172.20/16 -p tcp --dport 4445 -i eth2 -j ACCEPT INPUT -s 172.20/16 -p icmp -i eth2 -j ACCEPT iptables iptables iptables iptables iptables block block block block block -N -A -A -A -A -m -m -m -j state --state ESTABLISHED,RELATED -j ACCEPT state --state NEW -i ! eth2 -j ACCEPT limit -j LOG DROP iptables -A INPUT -j block iptables -A FORWARD -j block [dnsmasq] bogus-priv filterwin2k user=root interface=eth1 domain=teles dhcp-range=192.168.1.50,192.168.1.90,12h cache-size=150 resolv-file=/etc/resolv.conf The firewall blocks all incoming traffic on eth2. The exception on eth2 is icmp (for Ping requests) and TCP traffic on port 4445 (for the GATE Manager) from the same subnet (172.20.0.0/16). For eth1 are no firewall settings defined – all traffic is allowed. 4.6.3 The route.cfg config file The CELLX Box’s routing information is saved in the route.cfg file. Routing describes call processing within the CELLX Box. The routing configuration is the basis for deciding on which interface (FXS, IP, GSM) an incoming call is sent out. The route.cfg contains the sections summarized in Table 4.4. Table 4.4 Sections in the route.cfg file Section Function [System] Contains all routing entries (MapAll, Restrict, Redirect) of the default configuration. [VoIP: ] Contains all settings necessary for communication with the VoIP peer. [Registrar: ] Contains all settings to register with the registrar. CELLX box 17.1/002 Page 33 4 Configuration The routing is done with three variables: Restrict, MapAll, and Redirect. The variables will be evaluated in this order. That means the CELLX Box first analyzes all Restrict expressions of a section, then all MapAll expressions and then all Redirect expressions. The order of the expressions with the same variable (e.g. all MapAll expressions) is important – see the descriptions of the variables. 4.6.3.1 The Restrict variable used in the route.cfg Restrict entries are used to handle calls in a mapping based on the controller / controller group where the calls originate. A Restrict entry can be used, for instance, to route all calls coming from FXS directly to the mobile. If no called party number (DAD) is transmitted, Restrict can also be used to make the call mappable, for instance for calls coming from mo- bile. Table 4.5 route.cfg: Restrict Parameters Restrict = | Parameter Description No. Digits Contains the controller number. Contains the calling number (OAD). The symbol ? may be used as a wildcard to represent any character. 59 together with the controller number Stands for a virtual placeholder. The DAD is prefixed with the contents of this variable. 59 The service indicator variable sin restricts the command to one service. Without a sin, the Restrict command is valid for all services. Possible service indicator values are: 00 all services (default) 01 Telephony 05 sms 06 ussd 15 Used internally for calling party manipulation Optional The Restrict parameter adds a prefix to a DAD before the DAD is mapped. Restrict parameters are always handled before the MapAll parameters. The left side of the equals sign in the Restrict parameter contains the controller number (trunk number, and optional specific calling number (OAD)). The symbol ? may be used as a wildcard to represent any character. The right side contains the prefix or port number that is to be put in front of the DAD and an optional service indicator. In the route.cfg, the list of Restrict parameters is searched from bottom to top for a matching controller plus optional trunk number / OAD. Because the search is done bottom up, place the more specific Restrict entries below the more general ones. Once a match has been found, the DAD is prefixed with the contents of the variable. Then the call is mapped. In Example 4.7 all calls from FXS controller 10 are sent to mobile controller 20. First, the Restrict command adds the prefix “CO” to the DAD of the received call. This Restrict is used for all incoming PSTN calls. Then the call is mapped. In the mapping, everything that is prefixed CELLX box 17.1/002 Page 34 4 Configuration with “CO” is sent to controller 20 by removing the prefix and adding the controller to the number. In addition, individually dialed digits will be converted to block dialing with the syntax |…<<20. The last line from Example 4.7 sends all calls from mobile controller 20 to FXS controller 10. Example 4.7 Restrict Restrict10=CO MapAllCO=|20<<20 Restrict20=10 4.6.3.2 The MapAll variable used in the route.cfg Mapping entries are necessary for routing calls. The prefix or telephone number (DAD) for which the mapping applies is searched and the call routed according to the matching mapping entry. Mapping entries begin with the keyword MapAll. They work as follows: anything on the left of the equals sign is removed from the prefix / telephone number (DAD) that has come in and replaced with what is on the right of the equals sign. If, for example, the incoming DAD is 12345678 with 123456 being the trunk number 10 and 78 the extension, MapAll123456=10123456 means that 123456 is cut off the number and 10123456 is added to it. The called number is 1012345678 with 10 being the port. MapAll123456=10 means that 123456 is cut off and 10 added. The called number is 1078 with 10 being the port. Mappings are searched from top to bottom. Place the more specific entries above the more general ones. Table 4.6 route.cfg: map parameters MapAll = Parameter Description No. Digits Defines the prefix or telephone number for which the entry applies. 29 Defines the routing for a call in the order given: Destination port’s controller number Optional VoIP profile name followed by a colon if the call is terminated via VoIP Optional prefix Part of the number on the left that is transmitted The symbol ? may be used as a wildcard to represent any character. The symbol . may be used as a wildcard to represent any digit. 59 VOICE 4 or 5 DATA CELLX box 17.1/002 Applies for calls with the service indicator voice (default). Applies for calls with the service indicator data. Optional Page 35 4 Configuration All mobile calls with the prefix 01555 are transmitted to the mobile controllers (20). All international calls are sent to the VoIP provider (40) with the profile name DF. All national calls are sent to the controller with the number 9. It is important that the mapping for international calls is placed above the mapping for national calls. If you change the order of both mappings, international calls would be sent to controller 9 instead of 40. Example 4.8 MapAll MapAll01555=|2001555<<14 MapAll00=40DF:00 MapAll0=90 4.6.3.3 The Redirect variable used in the route.cfg This entry facilitates alternative routing when the first destination cannot be reached or is busy. A placeholder appears to the right of the equal sign. The routing entry (MapAll) can be defined for the redirect using the placeholder entered. Table 4.7 route.cfg: redirect parameters Redirect =
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.4 Linearized : No Author : frfa Modify Date : 2014:03:20 16:05:25+01:00 Subject : System manual Create Date : 2014:03:20 14:48:23Z PXC Viewer Info : PDF-XChange Viewer;2.5.212.0;Aug 29 2013;18:42:51;D:20140320160525+01'00' Page Count : 64 XMP Toolkit : XMP Core 4.1.1 Producer : Acrobat Distiller 7.0 (Windows) Creator Tool : FrameMaker 7.0 Format : application/pdf Title : CELLX Box Creator : frfa Description : System manual Copyright : TELES AG Berlin Marked : True Document ID : uuid:a3efe515-e265-4e6c-8b91-3a0a28021c32 Instance ID : uuid:54ba1f4c-4888-4233-9700-5b8427ac5314 Page Mode : UseOutlinesEXIF Metadata provided by EXIF.tools