1. Manuals
  2. Brands
  3. TELES Manuals
  4. Media Converter
  5. CellX Box series
  6. System manual

TELES CellX Box series System Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
CELLX Box
Systems Manual
Software version 17.1

Advertisement

Table of Contents
loading

Related Manuals for TELES CellX Box series

Summary of Contents for TELES CellX Box series

  • Page 1 CELLX Box Systems Manual Software version 17.1...
  • Page 2 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.

  • Page 3: Table Of Contents

    Table of Contents Table of Contents Preface..........5 Overview.
  • Page 4 Table of Contents 4.6.3 The route.cfg config file ..........33 4.6.3.1 The Restrict variable used in the route.cfg .

  • Page 5: Preface

    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 instruc- tions! In addition to this manual there is a parameter manual summarizing the configuration param- eters used in the config files.
  • Page 6 Organization Organization This guide is organized into the following chapters. “Overview”: describes the general features of the CELLX Box and the Chapter 1 main features for VoIP, telephony, and mobile. “System security and hardware overview”: starts with the safety and Chapter 2 security precautions.

  • Page 7: Overview

    1 Overview...

  • Page 8: Features

    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.

  • Page 9: Implementation Scenarios

    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...

  • Page 10: Cellx Box Last Mile

    Overview 1.2.1 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 avail- able, all you need for immediate communication is an CELLX Box and mobile network cover- age.

  • Page 11: Cellx Box Cost Saving Model

    Overview 1.2.3 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.

  • Page 12: System Security And Hardware Overview

    2 System security and hardware overview...

  • Page 13: Safety And Security Precautions

    System security and hardware overview This chapter starts with the safety and security precautions. Make sure that every- one who works with the CELLX Box is aware of these precautions. The CELLX Box described at the end of this chapter. 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.

  • Page 14: Connecting Cables

    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 ser- vices of a professional antenna installer.

  • Page 15: Upgrades

    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.

  • Page 16: Cdr Files

    System security and hardware overview 2.2.14 CDR files Call Detail Records are intended for analysis of the CELLX Box’s activity only. They are not de- signed to be used for billing purposes, as the times they record are not always exact. 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.

  • Page 17: Physical Description Of The Cellx Box

    System security and hardware overview Default ports used for specific services (continued) Table 2.1 Service Protocol Port SNMP 161 (default, can be set) H.225 registration, admission, 1719 (default, can be set) status H.225 signaling 1720 (default, can be set) GATE Manager 4445 (default, can be set) SIP signaling UDP / TCP...
  • Page 18 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...

  • Page 19: Cellx Box Installation

    3 CELLX Box installation...

  • Page 20: Checklist

    CELLX Box installation This chapter contains information on hardware installation of your CELLX Box. Fol- low the easy instructions to set up your CELLX Box in a matter of minutes. Checklist The following checklist provides step-by-step installation instructions. 1. Check the package contents 2.

  • Page 21: Cabling

    CELLX Box installation Cabling Before you carry out any assembly or servicing tasks, please read the safety instructions given Chapter 2.1 on page 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.

  • Page 22: Power Cabling

    CELLX Box installation 3.3.4 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.

  • Page 23: Configuration

    4 Configuration...

  • Page 24: 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 configu- ration and maintenance tasks are performed with the GATE Manager application.
  • Page 25 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.

  • Page 26: Connecting To The Cellx Box With Gate Manager

    Configuration 5. The IP settings window appears. Select the Ethernet Controller eth1/emac0 and enter the appro- priate network settings and click Finish to continue. To find out your local IP settings with Windows command ipconfig: Open an CLI (Windows-key + r). Type , and press Enter.

  • Page 27: Required Information For Further Scenarios

    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"...
  • Page 28 Configuration After that, the routing between the interfaces must be configured. local network mobile network CELLX 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).

  • Page 29: The Cellx Box Config Files

    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 pos- sible damage out of or in relation with such changes. Therefore please thoroughly check any changes you or a third party made to your configuration.

  • Page 30: The Pabx.cfg Config File

    Configuration 4. Transfer the new configuration file to the CELLX Box and activate the new configura- tion. 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.
  • Page 31 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 ;...

  • Page 32: The Ip.cfg Config File

    192.168.1.90. The default gateway is the CELLX Box on the eth1 interface and the DNS /etc/resolv.conf settings from the file 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...

  • Page 33: The Route.cfg Config File

    [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 re- quests) and TCP traffic on port 4445 (for the GATE Manager) from the same subnet (172.20.0.0/16).

  • Page 34: The Restrict Variable Used In The Route.cfg

    Configuration Restrict MapAll Redirect The routing is done with three variables: , and . The variables will Restrict be evaluated in this order. That means the CELLX Box first analyzes all expressions of a section, then all MapAll expressions and then all Redirect expressions.

  • Page 35: The Mapall Variable Used In The Route.cfg

    Configuration with “CO” is sent to controller by removing the prefix and adding the controller to the number. In addition, individually dialed digits will be converted to block dialing with the syn- |…<<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...

  • Page 36: The Redirect Variable Used In The Route.cfg

    Configuration (20) All mobile calls with the prefix 01555 are transmitted to the mobile controllers . All in- ternational calls are sent to the VoIP provider ( ) with the profile name . All national calls are sent to the controller with the number .

  • Page 37: The Route.cfg For The Last Mile Scenario

    Configuration In the following example all international calls (beginning with ) are sent to VoIP controller PeerA with the provider profile . If the provider is busy, the redirect command activates the second target mapping with the placeholder and the call is automatically sent to another PeerB VoIP provider e.g.
  • Page 38 Configuration route.cfg for the last mile scenario for CELLX Box with FXS ports (continued) Example 4.10 ; SIP profile for IP phone or softphone (8) [Voip:Phone1] VoipDirection=IO VoipPeerAddress= VoipIpMask=0x00000000 VoipSignalling=1 VoipOwnUser=user VoipOwnPwd=pwd VoipAuth=proxy VoipExpires=600 VoipMaxChan=2 VoipCompression=g711a g711u g729a g729b VoipTxM=4 4 2 2 ;...

  • Page 39: Configuration Files For Voip Scenarios

    Configuration 4.6.5 Configuration files for VoIP scenarios These files are designed for the failover and cost saving model scenarios using VoIP connec- ip.cfg tions. Possible changes of the are not shown in this chapter. If you want to use either of these VoIP scenarios with the CELLX Box, rename the config files route.cfg pabx.cfg and and adjust them to suit your needs.
  • Page 40 Configuration The route.cfg shown in Example 4.12 contains far more entries than Example 4.10 on page 37. The content is described below. Example 4.12 voip_route.cfg for routing in failover and other VoIP scenarios [System] ;--------------- (1) Restrict20=@FILE 05 Restrict20=@FILE 06 ;...
  • Page 41 Configuration voip_route.cfg for routing in failover and other VoIP scenarios (continued) Example 4.12 [Voip:sp201] VoipDirection=IO VoipOwnUser=201 VoipOwnPwd=201pass VoipExpires=3600 VoipAuth=www VoipSignalling=1 VoipCompression=g711u g729 VoipTxM=2 VoipSilenceSuppression=no VoipDtmfTransport=3 VoipRFC2833PayloadType=101 [Voip:PeerA] ; (10) VoipDirection=IO VoipPeerAddress=1.2.3.4;; Replace with IP address supplied by your provider VoipIpMask=0xffffffff ;...
  • Page 42 Configuration This mapping receive VoIP calls redirected and send them out to mobile. This is an example of a VoIP profile for local devices. Adjust password, username and the compression codec list to suit your needs. (10) This is an example of an external VoIP profile. Adjust Peer IP, password, username and the compressions list to the values given by the SIP provider.

  • Page 43: Adapting The Config Files

    5 Adapting the config files...

  • Page 44: Editing The Config Files

    Adapting the config files This chapter describes some frequent configuration scenarios. Editing the config files To edit configuration files, connect to the CELLX Box using the GATE Manager, as described Chapter 4.4 Connecting to the CELLX Box with GATE Manager on page Change to Directory view by selecting Directory in the menu in the left pane.

  • Page 45: Setting The Password For The Gate Manager

    Adapting the config files 5.2.1 Setting the password for the GATE Manager The CELLX Box comes with no password set for GATE Manager access. If you do not define a password, access to the system via GATE Manager takes place without one, and FTP access tcs-ag takes place with the default password RemotePassword=<password>...

  • Page 46: Voip Configuration

    Adapting the config files Table 5.1 iptable options used in Example 5.2 Option Description -s <source IP> This policy is only true for packets from the given source IP address. This option is not used in the example but if the source is known use this op- tion for more security.

  • Page 47: Voip Settings For A Public Voip Provider

    Adapting the config files 5.3.1 VoIP settings for a public VoIP provider If a public VoIP provider is used for incoming and outgoing calls the following configuration is needed: a) the CELLX Box must be reachable for incoming SIP and RTP IP traffic. This configuration depends on the network configuration and the VoIP provider.
  • Page 48 Adapting the config files (continued) Table 5.2 Explanation of the SIP profile in Example 5.3 Line in the example Explanation VoipCompression= Defines the values of compression codecs used for the connec- tion. Order the codecs according to your preference. The follow- ing values are defined: g711a, g711u, g729a, g729b, g72616, g72624, g72632, g728, g723, g723L, gsm, ccd, gnx64 VoipSilenceSuppression=No...

  • Page 49: Registrar Profile Defined For The Provider

    Adapting the config files 5.3.1.2 Registrar profile defined for the provider The registrar profile is needed to register your CELLX Box, so that your SIP provider will find you and send calls to your CELLX Box. Example 5.4 shows a registrar profile configured in the route.cfg Example 5.4 A registrar profile Registrar_PeerA...

  • Page 50: Call Routing For Outgoing Calls To The Provider

    Adapting the config files 5.3.1.3 Call routing for outgoing calls to the provider The call routing in the route.cfg tells the CELLX Box which calls are sent to the VoIP provid- MapAll er. The call routing is configured with the parameter (see Table 4.6 on page 35).

  • Page 51: Voip Settings For Local Sip Ua

    Adapting the config files 5.3.2 VoIP settings for local SIP UA The configuration of local SIP user agents (UA, such as softphones or SIP phones) is nearly the same than the configuration for the VoIP provider. If a local SIP device is used for incoming and outgoing calls to the FXS or mobile ports the following configuration is needed: a) The CELLX Box works as registrar for the SIP devices, so a VoIP profile is needed.

  • Page 52: Call Routing For Calls To And From The Local Sip Device

    Adapting the config files 5.3.2.2 Call routing for calls to and from the local SIP device Call routing sends the calls from the ports of the CELLX Box to the local SIP UAs and from the local SIP UAs to the devices on the ports of the CELLX Box. Please see Example 5.7.

  • Page 53: Cost Saving Routing

    Adapting the config files It is also possible to activate a rerouting from one VoIP provider to the next. If the first VoIP provider is not available the calls will be routed to the next VoIP provider. You need two VoIP providers in this case, configured as described in Chapter 5.3.1 on page 47.

  • Page 54: Callback Initiated By Sms

    Adapting the config files Callback initiated by SMS Callback offers the possibility of cost saving and central billing. Figure 5.1 shows how SMS callback can be used. 100 (FXS1) SMS: CAL#100 CELLX 101 (FXS2) mobile 222333444 222444555 102 (FXS3) 103 (FXS4) Figure 5.1 SMS callback example Figure 5.1...

  • Page 55: Mail To Sms

    Adapting the config files route.cfg In the set the entries shown in Example 5.12. Example 5.12 Settings in the route.cfg for SMS callback ; … ; send the incoming SMS to the msg.log file Restrict20=@File 05 ; … ; send SMS with CAL#number to intiate callback to sender and open a leg to number MapAllCB=20 MapAllDLA=$place MapAllplace100=10...
  • Page 56 Adapting the config files The settings in Example 5.13 are explained in Table 5.6. Adjust the IP address of the SmtpS- MailUserOut erver. Set the username and password for the SMTP server if needed ( MailPwdOut ). Set the MailRcpt and the MailFrom variable.

  • Page 57: Maintenance

    6 Maintenance...

  • Page 58: Call Detail Records (Cdr)

    Maintenance This chapter describes the CDR and trace maintenance tasks. Call detail records (CDR) The CELLX Box writes call detail records of all connections to the system memory. The path /boot/cdr.log pabx.cfg to the file ( ) is set in the (see Example 4.2 on page 31).

  • Page 59: Activating Peer Data For Voip Calls

    Maintenance Table 6.1 Entries of the cdr.log file informations separated by commas Column Description Cell ID (if mobile call) RSSI (if mobile call) The service indicator listed in the call log and missed calls list describes the type of connection as a four digit hexadecimal number.

  • Page 60: Cdrs For Callback And Two Stage Calls

    Maintenance The CDR entry in Example 6.2 includes IP addresses for signaling and voice data, audio codec and frame size. Example 6.2 Sample cdr.log file with VoIP information C1,24.11.09-16:52:20,24.11.09- 16:52:22,401419,9777,,172.20.25.103:172.20.25.103,G711a,20,0101,2,10,0,,,11 6.1.2 CDRs for callback and two stage calls In the case of CDR entries for two-stage dialing/callback calls, the beginning and ending times for the first call leg is always used as the call time.

  • Page 61: Missed Calls List

    Maintenance 6.1.4 Missed calls list All incoming calls that are not connected can be recorded in a list to facilitate return calls ( boot/failed.log ). Each line represents an incoming call that was not accepted, with the information separated by commas, as listed in Table 6.4.

  • Page 62: Trace

    10. Select the required file. Open the context menu with a right mouse click, select %Pro- Download From System. Save the file to your PC, The default directory is gramFiles%\teles\GATEManager\Data\<group>\<CELLX Box> CELLX box 17.1/002 Page 62...
  • Page 63 Maintenance 11. Send the trace to customer service. CELLX box 17.1/002 Page 63...
  • Page 64 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...

This manual is also suitable for:

Cellx 3g-4 fxsCellx gsm-4 fxsCellx 3g-4 bri-2Cellx 3g-4Cellx gsm-4 bri-2Cellx gsm-4

Table of Contents