1. Manuals
  2. Brands
  3. TELES Manuals
  4. Media Converter
  5. VoIP Box DSL Series
  6. Reference manual

TELES VoIP Box DSL Series Reference Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

VoIPBox DSL
VoIPBox BRI
Reference Manual
Software version 21.0

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the VoIP Box DSL Series and is the answer not in the manual?

Questions and answers

Related Manuals for TELES VoIP Box DSL Series

Summary of Contents for TELES VoIP Box DSL Series

  • Page 1 VoIPBox DSL VoIPBox BRI Reference Manual Software version 21.0...
  • 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 ..................11 About this manual ..............13 Safety and security precautions ..........15 Safety Measures ................16 Power Supply .................. 16 1.2.1 Technical Data ................17 1.2.2 Symbols ................... 17 1.2.3 Instructions for Use ............... 17 1.2.4 Safety Precautions .................
  • Page 4 Table of contents VoIPBox installation ..............28 Checklist ..................29 Package Contents................29 VoIPBox Hardware Description ............ 30 Installation Requirements............. 31 3.4.1 ISDN Wiring ..................31 3.4.2 Ethernet Wiring ................32 3.4.3 DSL wiring (optional)..............33 Preparing for Installation .............. 33 Hardware Connection ..............
  • Page 5 Table of contents 3.13 Remote access security ..............44 3.13.1 Graphical User Interface ............... 45 3.13.2 Setting a Password for Remote Access ........47 3.13.3 Adjust the firewall settings............48 3.14 Activate the VoIP interface ............49 Configuration files ..............52 Configuration file ip.cfg ..............
  • Page 6 Table of contents Configuration File route.cfg ............73 4.3.1 Entries in the Sections [System] and [Night<num>] ....73 4.3.1.1 Restrict..................... 74 4.3.1.2 MapAll....................76 4.3.1.3 Redirect ................... 78 4.3.2 VoIP Profiles ..................80 4.3.3 Gatekeeper Profiles ............... 83 4.3.4 Registrar Profiles ................84 4.3.5 Radius Profiles ................
  • Page 7 Table of contents Signaling and routing features ..........114 Digit collection (enblock/overlap receiving) ......115 Rejecting data calls and specified numbers......116 6.2.1 Blacklist routing................116 6.2.2 Whitelist routing ................117 6.2.3 Rejecting calls with ISDN bearer capability data ......118 6.2.4 Specific routing of data calls via VoIP ........118 CLIP and CLIR................119 6.3.1 Routing CLIP and CLIR calls............119...
  • Page 8 Table of contents 6.11 Miscellaneous routing methods..........131 6.11.1 Routing calls without a destination number......132 6.11.2 Routing calls based on existence of destination number ..132 6.11.3 Changing cause values ..............134 6.12 Call forwarding translation: ISDN to SIP........137 6.13 Call forking ..................139 System maintenance and software update ......141 Configuration errors ..............142 Status and error messages ............142...
  • Page 9 Table of contents Software Update ................178 7.5.1 Update the TELES software............178 7.5.2 Restore the original TELES configuration ........179 7.5.3 The automatic start check............180 Online traffic monitor ..............181 Calculating and resetting statistic values, resetting counters 182 8.1.1 Calculation and resetting of statistic values ......182 8.1.2...
  • Page 10 Table of contents No calls are possible ..............202 9.2.1 Call does not arrive on the gateway ..........202 9.2.2 Call is rejected or not routed to the right destination .....206 Software update problems ............209 Appendix A: Default config files ...............212 pabx.cfg ..................213 ip.cfg ....................216 route.cfg ..................218 List of examples ................220...

  • Page 11: Preface

    Chapter 1 Safety and se- curity precautions → before you begin to install your gateway. TELES is not liable for any damage or injury resulting from a failure to follow these safety and security instructions! Conventions This document uses the following typographic conventions: Bold –...
  • Page 12 Preface Safety symbols The following symbols are used to indicate important infor- mation 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 en- sure that the system functions correctly and to avoid mate- rial damage.

  • Page 13: About This Manual

    About this manual About this manual Chapter 1 – Safety and security precautions contains the safety and security precautions. In addition this chapter describes important system informations to protect the VoIPBox DSL / VoIPBox BRI. Chapter 2 – Overview gives you an overview of the VoIPBox DSL / VoIPBox BRI box. Lists all types of box, the features offered and describes two implementation scenarios.
  • Page 14 About this manual Chapter 7 – System maintenance and software update describes system messages that are saved in the protocol file, as well as trace options. Chapter 8 – Online traffic monitor describes the contents of traffic monitoring, i.e. call statistics, system statistics, and call detail records.

  • Page 15: Safety And Security Precautions

    1 Safety and security precautions...

  • Page 16: Safety Measures

    Safety and security precautions This chapter contains the safety and security precautions. In addition this chapter describes important system infor- mations to protect the VoIPBox DSL / VoIPBox BRI. Please be sure and take time to read this section to ensure your personal safety and proper operation of your gateway.

  • Page 17: Technical Data

    Safety and security precautions 1.2.1 Technical Data The following list includes technical information on the power supply: Type: DSA-15P-12 EU 120150 for VoIPBox Input voltage: 110-230V~ +/-15% 50-60Hz; 0.5A Output voltage: 12V ---; 1.25A Weight: 115g Tested and certified as per EN60950-1 1.2.2 Symbols The symbols on the power supply have the following mean-...

  • Page 18: Safety Precautions

    The room temperature may not exceed 35°C. Do not use the device if it is damaged or if there are signs of misfunction. In this case, send it to TELES Service or dispose of it properly (not with household waste).

  • Page 19: Emc Protection

    Safety and security precautions EMC Protection Use shielded cables. Do not remove any housing components. They provide EMC protection. System Security This section describes all points crucial to the VoIPBox’s sys- tem security. The VoIPBox’s location must support normal operation ac- cording to EN ETS 300 386.

  • Page 20: Servicing The Voipbox

    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 possible damage resulting from or in relation to such changes. Please thoroughly check any changes you or a third party have made...

  • Page 21: Cdr Files

    Network Security Every day, hackers develop new ways to break into systems through the Internet. While TELES 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,...

  • Page 22: Default Ports Used For Specific Services

    Table 1.2 Default Ports Used for Specific Services Service Protocol Port 21 (default, can be set) Telnet (for TELES debug ac- 23 (default, can be set) cess only) SMTP 25 (default, can be set) DNS forward HTTP 80 (default, can be set) H.225 registration, admis-...

  • Page 23: Overview

    2 Overview...

  • Page 24: Features

    Overview This chapter gives you an overview of the VoIPBox DSL / VoIPBox BRI box. Lists all types of box, the features offered and describes two implementation scenarios. The VoIPBox BRI is a media converter that facilitates the con- nection of ISDN service equipment with a voice over IP (VoIP) network.
  • Page 25 Overview Traffic shaping Configurable time interval for echo detection in VoIP ISDN 2, 4, or 8 BRI NT ports. Port 1 can be configured as TE or DSS1 (Q.931, national variants),Q.SIG-BC; PP or PMP ADSL2+/VDSL Modem PPP or DHCP VLAN or virtual path of ATM cell support TR-069 LCR Engine Multiple VoIP-carrier logins...

  • Page 26: Implementation Scenarios

    Overview Autodial function Implementation scenarios These are the most commonly used implementation scenari- VoIP gateway The VoIPBox’s sophisticated routing algorithms allow VoIP communication via SIP server and/or gatekeeper (H.323), as well as multi-destination operation without a SIP Server or gatekeeper. Various voice codecs ensure universal connec- tion to different VoIP destinations.

  • Page 27: Least Cost Router 2Nd Generation

    Overview Least cost router 2nd generation The VoIPBox’s sophisticated routing algorithms serve as an LCR between your PBX and the PSTN or VoIP carrier. Internet connection can occur via integrated DSL router. The system reverts to ISDN if there is an IP connection failure. P B X PSTN V o I...

  • Page 28: Voipbox Installation

    3 VoIPBox installation...

  • Page 29: Checklist

    Immediately report any visible transport damag- es to customer service. If damage exists, do not attempt oper- ation without customer-service approval. Software and manual are available for download at: http://as-support.teles.de. VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 29...

  • Page 30: Voipbox Hardware Description

    VoIPBox installation VoIPBox Hardware Description Figure 3.1 → shows the front and rear view of all VoIPBox vari- ations. The VoIPBox handles traffic of up to 8/16 media chan- nels. The following pages describe installation of the VoIPBox. ISDN 2 ISDN 1 ETH2 ETH1...

  • Page 31: Installation Requirements

    VoIPBox installation Installation Requirements Before installing your VoIPBox, make sure you have the fol- lowing connections in place: ISDN BRI connection to PBX and/or to the PSTN Ethernet for configuration and VoIP DSL (optional) Power 3.4.1 ISDN Wiring Connect the TE port connect to the PSTN and the NT ports to the PBX.

  • Page 32: Ethernet Wiring

    VoIPBox installation 3.4.2 Ethernet Wiring To connect the VoIPBox PRI’s Ethernet port ETH1 to an Ether- net switch in your local network. RJ-45 Ethernet connector Front view 4 3 2 1 Figure 3.4 Ethernet connector PIN assignment Table 3.1 → list the PIN assignement for the Ehternet.

  • Page 33: Dsl Wiring (Optional)

    VoIPBox installation 3.4.3 DSL wiring (optional) To connect the VoIPBox DSL / VoIPBox BRI’s DSL use a cable with the following PIN assignment. RJ-11 connector 1 - NC 2 - Tip or Ring 3 - Ring or Tip 4 - NC 4 3 2 1 Figure 3.5 DSL connector PIN assignment...

  • Page 34: Gate Manager

    Use the Quickstart program to set the IP address and the de- fault gateway to the VoIPBox DSL. Do the following steps: 1. Open the TELES support page in a Web browser at http:/ /195.4.12.8/agw/ 2. Download the GATE Manager software, the Quickstart and the manual.

  • Page 35: Hardware Connection

    VoIPBox installation 7. Open Quickstart on the PC. It automatically finds your VoIPBox BRI. Double click the icon to open the configu- ration window. Adjust the IP settings and click the fin- ish button. The VoIPBox BRI will be reconfigured with your new IP address and will then re-start.

  • Page 36: Gate Manager

    VoIPBox installation GATE Manager This chapter gives an overview to the GATE Manager. The GATE Manager will be used to transfer and activate configura- tion files for the VoIPBox DSL / VoIPBox BRI. In addition the GATE Manager allows to monitor the VoIPBox DSL / VoIPBox BRI.

  • Page 37: Transfer The Config File With The Gate Manager To The Pc

    GATE Manager and Utilities Programs Man- ual. Transfer the config file with the GATE Manager to the PC 1. Open the TELES support page in a Web browser at http://195.4.12.8/agw/. 2. Download the GATE Manager. 3. Extract the archive and install the GATE Manager.

  • Page 38: Activate The Dsl Connection

    VoIPBox installation 11.Select the context menu Edit to change the selected config file. After editing the file, upload it to the VoIPBox DSL / VoIPBox BRI. 3.10 Activate the DSL connection The DSL configuration is stored in the [dsl] section of the Table 3.4 →...

  • Page 39: Common Dsl Settings For Vlan/Atm Access And Ppp Login

    VoIPBox installation Table 3.4 DSL settings for line access and login (continued) Method Variant Settings DSL logon Logon Data re- Enter DSL User Name as User= parameter within [dsl] section Method quired Enter DSL Password as Pwd= parameter within [dsl] section Choose ppp Method by setting dslif=ppp with- in [dsl] section Enter ppp settings by inducting a [dslppp] sec-...

  • Page 40: Activate Pppoe Connection Over An Eth Interface

    VoIPBox installation Example 3.2 DSL access with dynamic IP address [dsl] Vlan=7 Vpi=1 Vci=32 dslif=dhcp Example 3.3 DSL access with fixed IP address [dsl] Vlan=7 Vpi=1 Vci=32 dslif= 10.1.3.100 netmask 255.255.255.0 3.11 Activate PPPoE connection over an Eth interface Configure the PPPoE settings within the [dsl] section. Set the dsleth= parameter to the IP interface that initiates the PPPoE interconnection.

  • Page 41: Changing The Ip Settings

    VoIPBox installation Set the DSL interface to PPP dslif=ppp within [dsl] section and use the mandatory [dslppp] section for PPPoE (see Example 3.4 on page 41 →). Example 3.4 PPPoE configuration on ETH2 [dsl] User="Heinz" Pwd="123123123" dslif=ppp dsleth=eth2 [dslppp] lock nodeflate novj novjccomp...

  • Page 42: Different Ip Settings For Every Interface Configured In The Ip.cfg

    VoIPBox installation Example 3.5 Main sections of the ip.cfg (continued) [eth1] IpAddress=192.168.1.2 netmask 255.255.255.0 [eth2] IpAddress=192.168.178.2 netmask 255.255.255.0 [iptables] # iptables -t nat -A POSTROUTING -o ppp0 -s 192.168.1.2 netmask 255.255.255.0 -j MASQUERADE iptables -P INPUT DROP iptables -P FORWARD DROP iptables -P OUTPUT ACCEPT iptables -A INPUT -s 0.0.0.0/0 -p tcp --dport 4445 -i ppp0 -j ACCEPT iptables -N block...

  • Page 43: Changing The Ip Settings

    VoIPBox installation 3.12 Changing the IP settings In many cases no changes on the IP settings of the VoIPBox DSL / VoIPBox BRI are needed. Because the IP configuration of the VoIPBox BRI is different to the IP configuration of the VoIPBox DSL the settings are described in different chapter.

  • Page 44: Change The Ip Settings On Voipbox Bri

    VoIPBox installation 3.12.2 Change the IP settings on VoIPBox BRI The VoIPBox BRI will be used as an network element with a fix IP address in the IP network. Here is the setup of the default gateway important. Example 3.8 → shows a part from the ip.cfg with a default gateway and different settings for every IP interface.

  • Page 45: Graphical User Interface

    VoIPBox installation 3.13.1 Graphical User Interface Remote access is possible via the Web GUI. Even users with lit- tle experience can easily configure standard system settings with this interface. Simply open a browser and enter the sys- tem’s IP address in the address bar. VoIPBox DSL / VoIPBox BRI –...

  • Page 46: Ip.cfg Web Gui Section

    VoIPBox installation The following administrative levels apply: Administrator Mode (Full Access) User: teles-admin Password: tcs-admin This access level is for the user network’s administrator. All configuration pages can be accessed in this mode. Read-Only Mode User: teles-user Password: tcs-user No configuration changes can be made at this level. Only sta- tus and statistics can be retrieved.

  • Page 47: Setting A Password For Remote Access

    VoIPBox installation Enter the IP address of the VoIPBox DSL / VoIPBox BRI in the Web browser to start the GUI. The user interface is divided into the following main sections: Table 3.5 GUI: Sections Section Description System Settings Different settings for the VoIPBox DSL / VoIPBox BRI: LAN Settings: Settings for the Ethernet interfaces, default gateway, DNS, IP routing, and NTP.

  • Page 48: Adjust The Firewall Settings

    VoIPBox installation 3. Enter the password in clear text in the Encode Pass- word box and click OK. 4. In the screenshot above, the clear text password is Weihnachtsmann@Bln108. The encoded password is vDLGTEBIZUNDMR@fNP54B. 5. Enter the encoded password as shown in Example 3.10 →.

  • Page 49: Activate The Voip Interface

    VoIPBox installation 3.14 Activate the VoIP interface The VoIP configuration is stored in the file route.cfg. The fol- lowing settings are needed from the VoIP provider: The IP address of the SIP server. User name and password for the SIP account. For incoming calls is a registrar setup needed.

  • Page 50: Voip Configuration In A Route.cfg

    VoIPBox installation 3. The Registrar: In the default configuration contains the registrar section as a comment, because the registra- tion will be repeated regularly and if the VoIPBox DSL / VoIPBox BRI is not in use this will create not needed IP traffic ( ).
  • Page 51 VoIPBox installation Table 3.6 VoIP configuration in a route.cfg (continued) ;;; SIP profile ;;; --------------------- [Voip:PeerA] VoipDirection=IO VoipPeerAddress= ;; ip address:port e.g. 1.2.3.4:5060 VoipIpMask=0xffffffff VoipSignalling=1 VoipUser= VoipPwd= ;VoipOwnAddress= ; optional VoipRegistrar=rega VoipMaxChan=60 VoipCompression=g711a g711u g729a g729b #[Registrar:rega] # #RegId= ;; ip address:port e.g. 1.2.3.4:5060 #RegOwnId=user@1.2.3.4 #RegUser= #RegPwd=...

  • Page 52: Configuration Files

    4 Configuration files...

  • Page 53: Configuration Files

    Changing configuration data may lead to malfunctions and/or misrouting, as well as possible consequential dam- age. All changes are made at own risk. TELES is not liable for any damage caused by or in relation to such changes. Please thoroughly check any changes you or a third party have made to your configuration.

  • Page 54: Configuration File Ip.cfg

    Configuration files The configuration files follow these conventions: Individual files are divided into sections. These sections always begin with a line entry in square brackets. The basic required sec- tions in these files are: Table 4.2 Required Configuration File Sections Section File Function...

  • Page 55: System Section Configuration

    Configuration files Table 4.3 Sections in the ip.cfg File (continued) Section Function These section contains settings for the PPP interface used for [dslppp] the DSL connection. This section contains settings for NAT and the system’s fire- [iptables] wall. This section enables the DHCP server the appropriate settings. [dnsmasq] 4.1.1 System section configuration...

  • Page 56: Ethernet Interface Configuration

    Configuration files 4.1.2 Ethernet interface configuration The following settings are possible for the sections [br0] or [eth1] and [eth2]: IpAddress=<ip addr> netmask <netmask> The IP address is entered in decimal notation, followed by the keyword netmaks and the netmask in decimal notation. Example 4.3 IP address configuration IpAddress=192.168.1.2 netmask 255.255.255.0...

  • Page 57: Dsl Configuration

    Configuration files 4.1.4 DSL configuration The DSL configuration is described in Chapter 3.10 on page 38 →. 4.1.5 Firewall configuration If the VoIPBox DSL / VoIPBox BRI is running in a DMZ (Demili- tarized zone (computing)) the firewall must be activated in the (see Chapter 4.1.5 on page 57 ip.cfg →).

  • Page 58: Pppoe Configuration

    Configuration files Table 4.4 iptable options used in Example 4.5 → (continued) Option Description --dport <portnum> This policy is only true for the given protocol number. Sometimes the definition in /etc/protocols will be used instead. This option can only be used together with the -p option. -j ACCEPT Defines the action that is carried out if the packet matches the rule.

  • Page 59: Dhcp And Dnsmasq Settings

    DHCP server in the system. Example 4.6 → shows a [dnsmasq] section. Example 4.6 A [dnsmasq] section with DHCP and DNSmasq parameter [densmasq] bogus-priv filterwin2k user=root interface=br0 domain=teles dhcp-range=192.168.1.50,192.168.1.90,12h cache-size=150 resolv-file=/etc/resolv.conf VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 59...

  • Page 60: Parameter Of The [Dnsmasq] Section

    Configuration files DHCP should only be used on the VoIPBox DSL. The content of this section is described in Table 4.5 →. Table 4.5 Parameter of the [dnsmasq] section Parameter Description Bogus private reverse lookups. All reverse lookups for pri- bogus-priv vate IP ranges (i.e.

  • Page 61: Configuration File Pabx.cfg

    Configuration files Configuration File pabx.cfg The pabx.cfg is divided into the [System] section and the op- tional [Night<num>], [Mail] and [Snmpd] sections. 4.2.1 System Settings The [System] section is divided into several categories to en- sure clarity: VoIPBox DSL / VoIPBox BRI name Log files Global Settings Controllers...

  • Page 62: Cdr.log Renamed Daily

    Configuration files You can define how the log files are to be divided. There are two possibilities for saving entries into a new file: In increments of time (twice-daily, daily, weekly, monthly) Depending on the size of the file You can also define a maximum number of up to 7 files to be generated.

  • Page 63: Dns And Ntp Settings

    Configuration files In the following entry, the file failed.log is renamed once a week. Up to 10 failed files will be saved on the system. Example 4.8 failed.log renamed once a week failedlog=/boot/failed.log weekly - 10 In the following entry, the file protocol.log is renamed when the file has reached 1MB.

  • Page 64: Parameter Used For Dns And Ntp Settings

    Configuration files Table 4.8 Parameter used for DNS and NTP settings Parameter Description Defines the IP address of the used domain name serv- NameServer=<dnsserver> er. Enter your network or ISP’s DNS server. If you don’t know it, you can also enter another DNS server. If you have more than one address, enter this parameter up to three times on different lines.
  • Page 65 Configuration files Table 4.9 Timezone settings for different locations (page 2 of 3) Town Settings Amsterdam, Netherlands CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00 Athens, Greece EET-2EEST-3,M3.5.0/03:00:00,M10.5.0/04:00:00 Barcelona, Spain CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00 Berlin, Germany CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00 Brussels, Belgium CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00 Budapest, Hungary CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00 Copenhagen, Denmark CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00 Dublin, Ireland GMT+0IST-1,M3.5.0/01:00:00,M10.5.0/02:00:00 Geneva, Switzerland CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00 Helsinki, Finland EET-2EEST-3,M3.5.0/03:00:00,M10.5.0/04:00:00...

  • Page 66: Controller Settings

    Configuration files Table 4.9 Timezone settings for different locations (page 3 of 3) Town Settings Hawaii Time HAW10 Alaska Time AKST9AKDT Pacific Time PST8PDT Mountain Time MST7MDT Mountain Time (Arizona, MST7 no DST) Central Time CST6CDT Eastern Time EST5EDT Atlantic Time AST4ADT Atlantic Time (New Brun- AST4ADT,M4.1.0/00:01:00,M10.5.0/00:01:00...

  • Page 67: Pabx.cfg: Controller Parameters

    Configuration files rameter in the configuration, you must restart the system. ble 4.10 → list some settings for the controller parameter that may be used on the VoIPBox DSL / VoIPBox BRI. Table 4.10 pabx.cfg: Controller Parameters Controller<port>=<address> <type> <mode> <line_type> FCT UNIT:<unit> VALUE:<value>...

  • Page 68: Subscriber Settings

    Configuration files The following example applies for the VoIPBox BRI with 4 ISDN ports. Example 4.10 VoIPBox BRI with 4 ISDN ports Controller00=9 TE DSS1 PMP Controller01=10 NT DSS1 PMP Controller02=10 NT DSS1 PMP Controller03=10 NT DSS1 PMP Controller04=40 VOIP Controller05=40 VOIP SC 4.2.1.5 Subscriber settings...

  • Page 69: Smtp-Client Configuration

    Configuration files Table 4.11 pabx.cfg: Subscriber Parameters (continued) Subscriber<port>=<list> Defines the maximal number of VoIP channels or DTMF chan- CHMAX[x] nels. Do not change these settings because the settings de- pends on the VoIPBox DSL / VoIPBox BRI hardware. Example 4.11 → shows the configuration for a VoIPBox DSL / VoIPBox BRI with 8 ISDN ports.

  • Page 70: Pabx.cfg Mail Parameters

    MailFrom=ipaddress to send OAD@ipaddress (or user@ipaddress, if no OAD avail- able). MailFrom=123@ to send 123@<IP address of gateway>. MailFrom=123@teles.de to send 123@teles.de. MailFrom=123@ipaddress to send 123@ipaddress. MailRcpt=<domain> In <domain>, enter the destination domain, the destination address and an @ sign. If the destination address is already complete (with an @ sign), <domain>...

  • Page 71: Night Configuration

    Configuration files Sending Alarm Messages via E-mail With the appropriate configuration, you can send e-mails con- taining alarm messages that are written into the log file. The sender is given as alarm and the system’s name appears in the subject box. The text box contains the alarm message. The following entry in the configuration file activates this func- tion.

  • Page 72: Night Parameters 1

    Configuration files The configuration section is activated Fridays, Wednesdays and Mondays at noon unless the day in question is a holiday: Example 4.14 Night parameters 1 Night2=12:00 00101010 The configuration section switches back to the default config- uration ([System] section) every day at 8:00 p.m: Example 4.15 Night parameters 2 NightResetTime=20:00 11111111...

  • Page 73: Configuration File Route.cfg

    Configuration files Holidays Up to 50 different dates can be set for night sections used by holiday. The variable dd.mm sets the day and month in which the night section is activated when the 8th bit is set in the bit- mask (see Table 4.13 →).

  • Page 74: Restrict

    Configuration files 4.3.1.1 Restrict 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 PSTN directly to the PBX. The Restrict parameter adds a prefix to a DAD before the DAD is mapped.
  • Page 75 Configuration files Table 4.14 route.cfg: Restrict Parameters (continued) Restrict<controller><calling number>=<pl> <sin> | RestrictD<diverting number>=<pl> 15 RestrictR<calling number>=<pl> 15 RestrictT<calling number>=<pl> 15 Parameter Description No. Dig- Optional <sin> The service indicator variable sin re- stricts the command to one service. Without a sin, the Restrict command is valid for all services.

  • Page 76: Mapall

    Configuration files PSTN. Then the call is mapped. In the mapping, everything that is prefixed with “pl” is sent to controller 10 by removing the prefix and adding the controller to the number. Example 4.17 route.cfg Restrict Parameters Restrict9=pl MapAllpl=10 4.3.1.2 MapAll Mapping entries are necessary for routing calls.

  • Page 77: Route.cfg Map Parameters

    Configuration files Mappings are searched from top to bottom. Place the more specific entries above the more general ones. Table 4.15 route.cfg: Map Parameters MapAll<direct>=<num> <mode> Parameter Description No. Dig- Optional Defines the prefix or telephone number <direct> (DAD) for which the entry applies. Defines the routing for a call in the order <num>...

  • Page 78: Redirect

    Configuration files 4.3.1.3 Redirect This entry facilitates alternative routing when the first desti- nation 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.16 route.cfg: Redirect Parameters Redirect<type><num>=<redirect>...

  • Page 79: Redirect 2

    Configuration files In the following example all international calls (beginning with 00) are sent to VoIP controller 40 with the carrier profile DF. If the carrier cannot be reached or is busy, the redirect com- mand activates the second target mapping with the place- holder A and the call is automatically sent to controller 9.

  • Page 80: Voip Profiles

    Configuration files sends a busy signal to the attached PBX. Alternative routing is not carried out. You can also define a range of consecutive cause values: BUSY[<cause>,<cause>] An exclamation point (!) in front of a cause value means all cause values except the one listed. For example, BUSY[!95], means all cause values except 95 will be rejected with a busy signal.
  • Page 81 Configuration files Table 4.17 route.cfg: VoIP Basic Parameters (continued) VoIP Basic Parameters VoipIpMask=<ip mask> The subnetmask is used to determine the size of the IP address range for incoming traffic. The syntax is 0x followed by the mask in hexadecimal notation. Example of a Class C mask entry: 0xffffff00.
  • Page 82 Configuration files Table 4.17 route.cfg: VoIP Basic Parameters (continued) VoIP Basic Parameters VoipSilenceSuppression=<mode> Yes activates silence suppression, CNG (comfort noise generation) and VAD (voice ac- tivity detection). No (default) deactivates silence suppression. NOTE: In SIP signaling, silence suppression is negotiated as per RFC3555. VoipTxM=<num>...

  • Page 83: Gatekeeper Profiles

    Configuration files Table 4.18 : VoIP Management Parameters (continued) route.cfg VoIP Management Parameters VoipStatLogging=<mode> When Yes is entered, statistic values (e.g. fraction lost, round trip time, etc.) for the VoIP profile are saved into the protocol.log file every ten minutes. This is helpful dur- ing problem analysis when IP issues occur (default = No).

  • Page 84: Registrar Profiles

    Configuration files Table 4.19 route.cfg: Gatekeeper Parameters (continued) Gatekeeper Parameters GkPwd=<name> Password to log onto the gatekeeper. If you do not use authentication, leave this entry blank. GkAdd=<ip addr> The gatekeeper’s IP address. GkTtl=<sec> Gatekeeper time to live (default 0 means infinite). GkMaxChan=<count>...
  • Page 85 Configuration files Table 4.20 route.cfg: Registrar Parameters (continued) Registrar Parameters RegOwnId=<name@ip addr/domain> Typically a host name or telephone number followed by an @ sign and a domain name or IP address. The entry used in the From: field. The default setting is RegUser@RegId.

  • Page 86: Radius Profiles

    Configuration files 4.3.5 Radius Profiles Radius profiles are used to connect the VoIPBox to a Radius server. You can use a Radius server for different destinations and for access and/or accounting. These Radius profiles are then assigned to the VoIP profiles: Table 4.21 route.cfg: Radius Parameters Radius Parameters...

  • Page 87: Route.cfg: Radius Parameters

    Configuration files Table 4.21 route.cfg: Radius Parameters (continued) Radius Parameters CallType=<int> Enter one of the following to define the call type: 3 = VoIP and telephony 2 = VoIP only 1 = Telephony only FramedProtocol=<int> Enter one of the following to define the framed protocol (see RFC 2865, Chapter 5.7): 1 = PPP 2 = SLIP 3 = AppleTalk Remote Access Protocol (ARAP)

  • Page 88: Additional Voip Parameters

    5 Additional VoIP parameters...

  • Page 89: Signaling Parameters

    Additional VoIP parameters This chapter contains additional configuration entries to fine-tune communication with the VoIP peer. You can enter the following additional parameters in the route.cfg to adjust the configuration for improved commu- nication with the VoIP peer. Signaling parameters Table 5.1 →...
  • Page 90 Additional VoIP parameters Table 5.1 Customized parameters: protocol-independent VoIP signaling (page 2 of 5) Protocol-Independent VoIP Signaling Parameters VoipEarlyVP=<mode> Activates the VoIP coder chip caused by an incoming SIP 180 or 183 without sdp. Fax tones coming from ISDN are already recognized before the connect and can thus pre- pare or even allow a switch to T38.
  • Page 91 Additional VoIP parameters Table 5.1 Customized parameters: protocol-independent VoIP signaling (page 3 of 5) Protocol-Independent VoIP Signaling Parameters VoipOad=<num> (continued) If -<num>-\ is entered followed by a part of an OAD (not necessarily the first part), the entered number of digits is cut from the OAD and the remaining OAD is searched for the entered part.
  • Page 92 Additional VoIP parameters Table 5.1 Customized parameters: protocol-independent VoIP signaling (page 4 of 5) Protocol-Independent VoIP Signaling Parameters VoipOad=<num> In the following examples, the OAD is 5175551212. The digits/numbers defined here will be transmitted in front of the original OAD. In the following example, 001 will appear in front of the number 5175551212.

  • Page 93: Customized Parameters: H.323 Signaling

    Enter a G.711 file and its path which is to be played as a ring tone to the caller for calls coming from VoIP. The ring tone is repeated until connect or disconnect of the call. A converter tool to convert wave files to the G.711 format is available from TELES free of charge.

  • Page 94: Customized Parameters: Sip Signaling

    Additional VoIP parameters Table 5.2 Customized parameters: H.323 signaling (continued) H.323 Signaling Parameters VoipRestrictTCS=<mode> If Yes is entered, the response in the H.323 tunneling terminal capability set contains only the codecs offered by the peer and not those configured in the system. Default VoipService=0x<service indicator>...
  • Page 95 Additional VoIP parameters Table 5.3 Customized parameters: SIP signaling (page 2 of 4) SIP Signaling Parameters VoipContact=<account@domain> | <ip address> | RH Used for the Contact field in Sip-Invite and Sip-Response messages. Can be entered in the parameter or, with the RH keyword, taken from the request header of the incom- ing SIP-Invite.
  • Page 96 MSN causes the calling telephone’s MSN to be transmitted as Display Name. The key- word DSP causes the ISDN display information element to be transmitted as Display Name. Default: no setting. Example: From: "John" <sip:493011111@teles.de> VoipP-Asserted-Identity=<string> Sets the P-Asserted-Identity field in the SIP invite message. The following settings are possible toward SIP: * The OAD coming from ISDN is transmitted.

  • Page 97: Stun Server Parameter

    Additional VoIP parameters Table 5.3 Customized parameters: SIP signaling (page 4 of 4) SIP Signaling Parameters VoipSipLine=<string> SIP only. Use this parameter to include a freely defined line in a SIP INVITE. This pa- rameter can be used several times. VoipSipStatusIncompatibleCodec=<reject cause>...

  • Page 98: Set Up The Voipbox Dsl / Voipbox Bri As Registrar

    Additional VoIP parameters 29000 for RTP and 29001 for RTCP for a defined range of ports. Set this range with VoipGlobalMaxChan. If, for instance, VoipGlobalMaxChan=30 is set, the RTP ports that are checked are 29000, 29002, 29004,…, 29058. Accordingly, the RTCP ports that are checked are 29001, 29003, 29005, …, 29059.

  • Page 99: Voip Profile With Location Server Settings For Sip User Agent 130

    Additional VoIP parameters Example 5.1 → creates an account for a user agent with the username 130 and password test130. Authentication occurs with the procedure www. The own IP is 192.168.1.12. Example 5.1 VoIP profile with location server settings for SIP user agent 130 MapAll130=40U1:130 [Voip:U1] VoipDirection=IO...

  • Page 100: Routing Parameters

    Additional VoIP parameters Routing parameters Table 5.6 Customized parameters: VoIP routing VoIP Basic Parameters VoipEnumDomain=<string> Use this parameter to modify the domain name for the enum query (default is e164.arpa). VoipOadMask=<num> VoipDadMask=<num> It is also possible to define the profile by destination or origination number (and not only by the IP address).

  • Page 101: Quality Parameters

    Additional VoIP parameters Quality parameters Table 5.7 Customized parameters: VoIP quality (page 1 of 5) VoIP Quality Parameters SigTos=<num> Enter a value between 0 and 255 (default is 0) to set the TOS (type of service) field in the SIP/SIPS packet IP header. Possible values are described in Table 5.8 →.
  • Page 102 Additional VoIP parameters Table 5.7 Customized parameters: VoIP quality (page 2 of 5) VoIP Quality Parameters VoipMaximumBandwidth=<number> Defines an upper limit for available bandwidth for the VoIP profiles to be configured if traffic shaping is active for the corresponding VoIP profile. Enter the upper limit for available bandwidth for the VoIP profiles to be configured (see the parameter VoipBandwidthRestriction) if traffic shaping is active for the cor- responding VoIP profile.
  • Page 103 Additional VoIP parameters Table 5.7 Customized parameters: VoIP quality (page 3 of 5) VoIP Quality Parameters VoipEcl=<ms> This parameter defines the required tail length for echo cancellation. The following values in ms are possible: 64 (default) VoipInputGain=<num> The volume of VoIP calls coming from ISDN, POTS or mobile. The range is 0-63. The default value of 32 is 0 dB.
  • Page 104 Additional VoIP parameters Table 5.7 Customized parameters: VoIP quality (page 4 of 5) VoIP Quality Parameters VoipPCMPacketInterval=<int> This parameter changes the default interval for PCM codecs (G.711, G.726). That means the VoipTxm factor is muliplied using this interval: For 16-channel chips: 0 = 20ms (default) 1 = 5 ms 2 = 10 ms...
  • Page 105 Additional VoIP parameters Table 5.7 Customized parameters: VoIP quality (page 5 of 5) VoIP Quality Parameters VoipT301=<sec> An outgoing VoIP calls will be canceled in the state of Alerting (for H323) or Ringing (for SIP) if the number of seconds entered has passed and there is no response from the IP or VoIP carrier.

  • Page 106: Call Forwarding Parameters

    Additional VoIP parameters The following specifications for Quality of Service correspond with RFC791 and RFC1349. Table 5.8 Quality of service values Distribu- Precedence tion Description Precedence TOS: 0=normal delay, 1=low delay TOS: 0=normal throughput, 1=high throughput TOS: 0=normal reliability, 1=high reliability TOS: 0=normal service, 1=minimize monetary cost MBZ: must be 0 (currently not used) Precedence...

  • Page 107: Interworking Parameter

    Additional VoIP parameters CFNR (not reachable) Table 5.9 Customized parameters: VoIP call forwarding VoIP Call-Forwarding Parameters CMD_<type>Activate=<string> Activates call forwarding (CFU, CFB, CFNR). Must include the keyword MSN, which re- fers to the number to which incoming calls shall be forwarded (e.g. “*41*MSN#”). CMD_<type>Deactivate=<string>...

  • Page 108: Compression Parameters

    The relationship between header and payload benefits the payload when several calls occur simultaneously. This com- pression does not result in any loss in voice quality. This feature is possible with a TELES peer and requires the fol- lowing entries in the VoIP profile: Table 5.10...

  • Page 109: Fax/Modem Parameters

    Additional VoIP parameters Fax/modem parameters Table 5.11 → list some parameter for VoIP fax. Table 5.11 Customized parameters: VoIP fax VoIP Fax/Modem Parameters VoipAPartyCanSwitchToT38=<mode> Enter Yes (default) to activate fax detection in both directions. When No is set, fax de- tection and translation to T.38 are carried out only when the call comes from VoIP.

  • Page 110: Fax Settings For T.38

    Additional VoIP parameters Table 5.11 Customized parameters: VoIP fax (continued) VoIP Fax/Modem Parameters VoipT38Version=<int> 0 = T38 version 0 (default) 1 = T38 version 1 2 = T38 version 2002 ASN1 syntax TPKT enabled 3 = T38 version V34 V33 support 2002 ASN1 syntax TPKT enabled. Is needed to send v34 faxes via T38.

  • Page 111: Dtmf Parameters

    Additional VoIP parameters 5.10 DTMF parameters Table 5.12 Customized parameters: VoIP DTMF VoIP DTMF Parameters VoipComprDtmfInband=<list> This parameter always forced DTMF-tone inband transmission for the configured voice codes, regardless of what is configured for: VoipDtmfTransport=. The same co- decs can be configured as for VoipCompression=<list> VoipDtmfFallback=<int>...

  • Page 112: Announcements

    The announcement’s file for- mat must be G.711. A converter tool to convert wave files to the G.711 format is available from TELES free of charge. It is included with the The announcement is defined in the Sub- scriber line using the following entry in the pabx.cfg file:...

  • Page 113: Announcements (Pabx.cfg)

    Additional VoIP parameters To stop the announcement after the entry of the first digit, a [ needs to be added behind DTMF to the respective MapAll pa- rameter: MapAll<number>=<DTMFport>DTMF[ In this example, a maximum of 5 channels can recognize DTMF tones and change them into dialing data. The default announcement is named DTMF1.711 and must be available in the boot directory.

  • Page 114: Signaling And Routing Features

    6 Signaling and routing features...

  • Page 115: Digit Collection (Enblock/Overlap Receiving)

    Signaling and routing features This chapter contains some special configuration examples for different call routing and configuration cases. Digit collection (enblock/overlap re- ceiving) This function makes it possible to collect up to 58 digits and transmit calls when a specific number of digits has been di- aled.

  • Page 116: Rejecting Data Calls And Specified Numbers

    Signaling and routing features The following example shows a call with the prefix 01555. The | (pipe) signifies that the following digits will be collected be- fore they are transmitted. The 14 at the end is the sum of the port digits and the digits of the called party number (e.g.

  • Page 117: Whitelist Routing

    Signaling and routing features In the following example, all calls to the number 004915551234 and all service calls with the prefix 0180 are re- jected with a busy signal. All other calls are sent to the VoIP profile DF. Example 6.2 Blacklist routing MapAll015551234=&91 MapAll004915551234=&91...

  • Page 118: Rejecting Calls With Isdn Bearer Capability Data

    Signaling and routing features 6.2.3 Rejecting calls with ISDN bearer capability data ISDN data calls can be handled differently from voice calls de- pending on the configuration of the call types DATA or VOICE. This setting is especially interesting for VoIP or mobile calls: MapAll<direct>=&<cause>...

  • Page 119: Clip And Clir

    Signaling and routing features calls and all calls from VoIP to ISDN. The second profile is ex- clusively for outgoing data calls, so that signaling consists solely of clear mode in SDP. Example 6.5 Routing data calls via VoIP MapAll0=40DATA:0 DATA MapAll9=40DATA:9 DATA MapAll0=|40DF:0<<24 MapAll9=|40DF:9<<24...

  • Page 120: Setting Clir

    Signaling and routing features Use the following configuration to define the various routing methods. Example 6.6 Routing CLIP and CLIR calls InsertCLIR=On Restrict9=OK 01 Restrict|9=OK 01 Restrict90=FAIL 01 MapInOK00491555=2200491555 MapInFAIL=&aa InsertCLIR=On activates this mode. 01 is the service indicator for telephony (analog and ISDN) and is used to differentiate these calls from remote administration calls.

  • Page 121: Setting Clip

    Signaling and routing features 6.3.3 Setting CLIP Setting an exclamation point (!) in front of a call number makes it possible to force the presentation of the origination number of calls regardless of how the call comes into the sys- tem.

  • Page 122: Overwriting Oad

    Signaling and routing features This example presents an alternative, in which the routing file is searched through again after conversion of the call number to determine the route for the prefix 01555. Please bear in mind that you can configure a maximum of 5000 mapping en- tries.

  • Page 123: Setting Number Type In Oad/Dad

    Signaling and routing features Setting number type in OAD/DAD In some cases it may be necessary to set a specific number type for the OAD or DAD. There are different methods for the various interfaces. The following number types can be set: Table 6.1 Number types Type...

  • Page 124: Restrict 2

    Signaling and routing features You can set a u (unknown type of number) in the Restrict entry to change transmission of the national/international bit to 0 or 00 at the beginning of the OAD. As in a mapping entry, the national/international bit will always appear left of the equal sign as 0 or 00.

  • Page 125: Setting The Screening Indicator

    Signaling and routing features If the call is not connected and a Redirect3 is configured for the call, the OAD will be changed from 4930 to 004930 as fol- lows. Example 6.15 Restrict 4 RestrictR4930=004930 15 Enter one of the four specific number types in the DAD as fol- lows: MapAll<num>=<port><type><num>...

  • Page 126: Restrict 5

    Signaling and routing features User provided verified and passed: v In the following Restrict example, the calling party number sent is specified as user provided verified and passed: Example 6.17 Restrict 5 Restrict10=v 15 Network provided: p In the following Restrict example, the calling party number sent is specified as network provided.

  • Page 127: Setting A Default Oad

    Signaling and routing features or blu), in which the BRI ports are directly assigned to a map- ping. Traffic at BRI port 9 is sent directly to VoIP port 40 with the VoIP profile iG1. Traffic from BRI port 10 is sent to VoIP port 40 with the profile iG2.

  • Page 128: Setting Sending Complete Byte In Setup

    Signaling and routing features In the following example, the digits 004930 are replaced with 030 followed by the remaining digits. The destination number begins with 030 and is sent through port 10. Example 6.22 Setting default OAD 2 Restrict9004930=030 15 MapAll030=10030 Setting sending complete byte in set- In some cases the ISDN or H323 peer system may require this...

  • Page 129: Oad Screening

    Signaling and routing features The ( causes removal of sending complete in the ISDN Setup or in the H323 Setup. In the following example, all calls beginning with 0 are sent without a sending complete to VoIP controller 40. The VoIP profile is DF.
  • Page 130 If the calls received from ISDN are forwarded to SIP, the pa- rameter VoipP-Preferred-Identity needs to be configured in the used VoIP profile in route.cfg: VoipP-Preferred-Identity=<sip:*@c5.teles.de> If the calling party number received from the PBX matches the range configured with the CMSN parameter, both, P-Pre- ferred-Identity and From field contain the same calling party number.

  • Page 131: Miscellaneous Routing Methods

    VoipDirection=IO VoipPeerAddress=195.4.12.50 VoipSignalling=1 VoipCompression=g711a g711u g729 VoipTxM=2 VoipOadOut=03039928 VoipOwnAddress=<@c5.teles.de> VoipP-Preferred-Identity=<sip:*@c5.teles.de> 6.11 Miscellaneous routing methods In the following scenarios it may occur that some call num- bers must be routed with differing lengths or that some call numbers may require additional number conversion:...

  • Page 132: Routing Calls Without A Destination Number

    Signaling and routing features 6.11.1 Routing calls without a destination number Enter the following configuration in the route.cfg if the VoIPBox must route calls that come in without a destination number: Restrict<port>=<pl> MapAll<pl><num>=<port><num> MapAll<pl>=<port> Incoming calls from the configured port will be assigned a placeholder and then all calls beginning with the placeholder will be routed to the placeholder’s placeholder’s mapping.

  • Page 133: Routing Based On Dad

    Signaling and routing features placeholder. The $ in the mapping entry, followed by the de- fined placeholder (MMM), causes a second search of the routing file when the number is complete: DTMFWaitDial=<sec> Restrict<port>=<pl> MapAll<pl>=|$MMM<<98 The second routing-file search is based on the routing entry with the leading placeholder (MMM): MapAllMMM<digits>=<dest><digits>...

  • Page 134: Changing Cause Values

    Signaling and routing features 6.11.3 Changing cause values It is possible to group cause values together into a single de- fined cause value so that rejected calls can be handled in a specified manner by the PBX sending the call to the VoIPBox. The following cause value groups can be defined in the pabx.cfg.

  • Page 135: Isdn Cause - Sip Response And Sip Response - Isdn Cause

    Signaling and routing features Translating individual cause values The following parameter allows you to translate any cause values to any other one: Translate<cause>=<cause>. The val- ues entered must be in hexadecimal notation between 00 and 7f (or 80 and ff in most significant bit-notation). Translating SIP causes to ISDN and vice versa You can define a specific translation from SIP responses (4xx - 6xx) to ISDN cause values and vice versa.
  • Page 136 Signaling and routing features Table 6.2 ISDN cause - SIP response and SIP response - ISDN cause (page 2 of 3) ISDN cause SIP response SIP response ISDN cause VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 136...

  • Page 137: Call Forwarding Translation: Isdn To Sip

    [ISDNFCGW] Type=<signaling GW> The current solution for call-forwarding translation is for the TELES.iLEX signaling gateway. Other solutions may be imple- mented according to individual requirements. To use call-for- warding translation with the TELES.iLEX, the parameter Type must be configured as follows: Type=TELES_LEX VoIPBox DSL / VoIPBox BRI –...

  • Page 138: Call Forwarding

    Signaling and routing features Depending on the signaling gateway, other optional parame- ters may be included in this section. For a description of these parameters, please refer to the parameters listed in Chapter 5.6 Call forwarding parameters on page 106 →.

  • Page 139: Call Forking

    Signaling and routing features 6.13 Call forking The call forking functionality is mostly used to send inbound calls to your PBX extension and mobile phone simultaneous- ly. Calls can be answered from either the extension or the mo- bile phone. To activate this feature, you need to add two parameters to the route.cfg GlobalIn and GlobalOut...

  • Page 140: Call Forking

    Signaling and routing features Assign the numbers which you want to call simultaneously to the GlobalOut<int> parameter. The integer value is used to map GlobalIn to GlobalOut. You can define up to 32 different GlobalOut configurations: GlobalOut<int>=<destinationNumber1> <destinationNumber2> where int >= 1 Be aware that for both destination numbers the MapAll pa- rameter needs to be set.

  • Page 141: System Maintenance And Software Update

    7 System maintenance and software update...

  • Page 142: Configuration Errors

    If functions were activated by key combinations from terminal devices you can identify these along with the service ID. Example 7.1 Protocol.log file 06.05.14-16:37:26,[990]Start STATUS - TELES VoIPBox DSL 2 V20.0.2.0 (004e) 06.05.14-16:37:26,Remote Control from IP 172.20.27.141 (172.20.27.141) 06.05.14-16:37:26,Remote Control: OK 16.05.06-12:10:57,[01A]ERR: Layer1 16.05.06-12:10:58,[000]ERR: OK 16.05.06-12:10:58,[010]ERR: OK...

  • Page 143: Session

    System maintenance and soft- ware update Table 7.1 Event log messages Message Definition Status Program TELES system software and status program have [990] Start STATUS been started. System Start System restarted by timer. [999] System-Boot System restarted by remote administration com-...

  • Page 144: Event Log Messages

    System maintenance and soft- ware update Table 7.1 Event log messages (continued) Message Definition A Layer 1 or Layer 2 error occurred on <num>. [<port><i>] ERR: Prob- lem at Port <num> <i> indicates error type: Layer 1 error Layer 2 error Layer 1&2 operational.
  • Page 145 System maintenance and soft- ware update Table 7.2 Protocol.log status and error messages (page 2 of 4) Message Definition The <port> has been blocked. This can occur via re- [<port>]Restart Port mote access for all controller types. Ethernet Interface The Ethernet controller’s status is checked every [99d]ERR: eth1<num><state>...
  • Page 146 System maintenance and soft- ware update Table 7.2 Protocol.log status and error messages (page 3 of 4) Message Definition Nonce missing in response from registrar (possible registrar <name>: gives no nonce error in registrar configuration). Registration with specified registrar is not allowed. registrar <name>: registration forbidden Specified registrar does not respond.

  • Page 147: Ipupdate - Dyndns Client

    System maintenance and soft- ware update Table 7.2 Protocol.log status and error messages (page 4 of 4) Message Definition Error in ip.cfg line <line>: parameter "<parameter_name>" does not belong to any Sec- tion There is an error in the NAT Configuration The NAT was not loaded, please check the Configuration for mistakes There is an error in the DHCPD Configuration The DHCP SERVER was not loaded, please check the Configuration for mistakes...

  • Page 148: Pabx.cfg: Dyndns

    System maintenance and soft- ware update Make the following entries in the system’s pabx.cfg, in the [DynDNS] section: Table 7.3 pabx.cfg: DynDNS DynDNS Parameters service=<type> Specifies which provider is used. The following providers are supported: http://www.dhs.org dyndns http://www.dyndns.org dyndns-static dyns http://www.dyns.cx ezip http://www.ez-ip.net...

  • Page 149: Trace

    System maintenance and soft- ware update In the following example, the DynDNS service is used and the domain name is host.domain.de; the username is user and the password is pwd. The VoIPBox works as DSL router and the dynamically allocated IP address of the PPPoE interface is used.
  • Page 150 System maintenance and soft- ware update Table 7.4 Trace options Option Definition DTMF Output for DTMF tone recognition. Remote Output for GATE Manager and NMS communication. Figure 7.1 GATE Manager: Online Trace activation window VoIPBoxes offer two different types of trace: Online - trace information is immediately displayed in the GATE Manager’s trace window.

  • Page 151: Online Trace Activation Window

    Contains a list of port-independent trace options. The different op- tions can be limited to error messages, debug messages, or de- tailed trace output. The Advanced field is for TELES support usage only. For an explanation of the different trace option please refer to Chapter 7.4 Trace on page 149...
  • Page 152 System maintenance and soft- ware update Table 7.5 Online trace activation window (continued) Field Description Level Select which special type of information you want to trace for the different timeslots. Additional The following additional entries are possible. The number behind the colon refers to the trace level.

  • Page 153: Isdn Trace Output

    System maintenance and soft- ware update Traces appear in the following format: [<hh:mm:ss>] <module>[<port>]: <trace> <module> – s = send for PRI/BRI ports – r = receive for PRI/BRI ports – x = send to VoIP destinations – y = receive from VoIP destinations –...

  • Page 154: Call Forwarding To Sip Trace Output

    System maintenance and soft- ware update The following example shows an raw DSS1 trace: Example 7.3 ISDN trace output 17.05.06-09:54:40,Start 11.7a (L3) [09:55:14.58] r[00]: 00 01 02 02 08 02 00 02 05 04 03 80 90 a3 18 03 a1 83 81 6c 02 81 31 70 06 81 31 32 33 34 35 7d 02 91 81 [09:55:14.58] s[00]: 02 01 02 04 08 02 80 02 0d 18 03 a9 83 81 [09:55:14.58] s[01]: 00 01 a8 9a 08 02 00 46 05 04 03 80 90 a3 18 03 a1 83 89 6c 02 81 31 70 06 81 31 32 33...

  • Page 155: Voip Trace Output

    System maintenance and soft- ware update The arguments define which traces are to appear and are sep- arated by a comma. The following arguments apply for each module: trclevel=[info; error; debug] Info messages allow the user to observe the progress of the translation process.

  • Page 156: Interface Ip Network

    System maintenance and soft- ware update Particularly in the case of VoIP connections (protocols H.323 and SIP), the trace output is quite extensive and abbreviations make it difficult to keep track of the results. The following list contains a description of H.323 output. Output for the signaling protocol SIP is transmitted in ASCII and translated for better legibility.

  • Page 157: Ets Message Types

    System maintenance and soft- ware update The output syntax is h225connect to <ip address> cr <cr> s <si> for calls going into the IP network and h225accept from <ip address> s <si> for calls coming out of the IP network Table 7.7 H.323 session Trace Output...

  • Page 158: Incoming Voip Calls

    System maintenance and soft- ware update Table 7.9 ETS message types Hex Value Message Type Facility Notify Information Status The following lines show the packet contents in detail. h225 decode rc 0, q931 msg 0x<mt> = 0, len <length> h225<type> <mt> voipcfg addr <ip address> rc 0 compr <codec> h225<type>...

  • Page 159: Compression Codecs Used

    System maintenance and soft- ware update Table 7.11 Compression codecs used Synonym Codec G.711Alaw64k G.711Ulaw64k G.7231 G.728 G.729 gsmFullRate T.38fax G.729A G.72616 G.72624 G.72632 G.729B G.729AB G.729E G.723L Transparent G.721 iLBC20 iLBC30 When the call is sent in the direction of the IP network, the trace will include only the most important information: h225<type>...

  • Page 160: Rtp/Rtcp Output

    System maintenance and soft- ware update Or: h225<type> callproc typ <mt> cr <cr> Table 7.13 Calls to the IP network 2 Trace Output Description The ETS message type in hexadecimal. <mt> Call reference. <cr> 7.4.3.2 RTP/RTCP output The RTP/RTCP output displays whether the signaling informa- tion corresponds with the contents of the compression chips.

  • Page 161: Rtp Stop Message

    System maintenance and soft- ware update The RTP stop message has the following syntax: rtp stop cr <cr>1 ch <ch> Table 7.15 RTP stop message Trace Output Description Call reference. <cr> The internal media channel used. <ch> VP module This module's output shows the controller packets for the voice connections.

  • Page 162: Rtp Packet Statistics

    System maintenance and soft- ware update a[<controller>]: <VoIPcodecChipType> ch <ch> establish Sent and received bytes appear with the following output re- sults: a[<controller>]: <VoIPcodecChipType> ch <ch>: in <byte> out <byte> Table 7.17 RTP packet statistics Trace Output Description The internal media channel used. <ch>...

  • Page 163: Jitter Buffer Status

    System maintenance and soft- ware update Table 7.19 Jitter buffer status Trace Output Description SteadyStateDelay in milliseconds NumberOfVoiceUnderrun NumberOfVoiceOverrun NumberOfVoiceDecoderBfi (bfi = bad frame interpolation) NumberOfVoicePacketsDropped NumberOfVoiceNetPacketsLost NumberOfIbsOverrun (ibs = in band signaling) NumberOfCasOverrun An RTP connection has ended when the following trace out- put appears: a[<controller>]: <VoIPcodecChipType>...
  • Page 164 System maintenance and soft- ware update Table 7.22 fax or data signal event (continued) Value Definition Description ANS_TONE_2100_FAX_CED_OR_ FAX-CED or modem-ANS (answer tone, MODEM 2100 Hz) ANS_TONE_WITH_REVERSALS ANS (answer tone with reversals) ANS_TONE_AM ANSam (AM answer tone) ANS_TONE_AM_REVERSALS ANSam (AM answer tone with rever- sals) FAX_V21_PREAMBLE_FLAGS FAX-V.21 preamble flags...

  • Page 165: Internal Protocol Interface (To Isdn, Pots, Mobile)

    System maintenance and soft- ware update Table 7.23 DTMF tone recognition Trace Output Description Media channel <ch> Recognized DTMF tone in the stream or as per RFC2833 <dtmf> Direction <dir> Coming from BRI/analog Coming from VoIP Tone has ended <mode> Tone has been recognized Signal level in -dBm <lev>...

  • Page 166: H.245 Messages

    System maintenance and soft- ware update Output also appears when a call comes from the internal pro- tocol interface and is assigned to a VoIP profile. The charac- ters appear in front of the colon in the routing entry. pstnrcv get_voipcfg <voip profile> compr <list> Table 7.25 Received from PSTN 1 Trace Output...

  • Page 167: Codec Used

    System maintenance and soft- ware update plained later appear. The most important message types that contain further information elements are as follows..TerminalCapabilitySet peer=<comp> cfg=<comp> ... TerminalCapabilitySet <comp> Table 7.28 Codec used Trace Output Description List of compression codecs offered (see Table 7.11), the list of the <comp>...

  • Page 168: Multimedia System Control Message Types

    System maintenance and soft- ware update Table 7.31 Multimedia system control message types Message 0 (Table 7.32) Request 1 (Table 7.33) Response 2 (Table 7.34) Command 3 (Table 7.35) Indication Depending on the system control message type, one of the following message IDs appear.

  • Page 169: Message Ids For Command Message

    System maintenance and soft- ware update Table 7.33 Message IDs for response message (continued) Message TerminalCapabilitySetAck TerminalCapabilitySetReject OpenLogicalChannelAck OpenLogicalChannelReject CloseLogicalChannelAck RequestChannelCloseAck RequestChannelCloseReject MultiplexEntrySendAck MultiplexEntrySendReject RequestMultiplexEntryAck RequestMultiplexEntryReject RequestModeAck RequestModeReject RoundTripDelayResponse MaintenanceLoopAck MaintenanceLoopReject CommunicationModeResponse ConferenceResponse MultilinkResponse LogicalChannelRateAcknowledge LogicalChannelRateReject Table 7.34 Message IDs for command message Message NonStandard MaintenanceLoopOffCommand...

  • Page 170: Message Ids For Indication Message

    System maintenance and soft- ware update Table 7.34 Message IDs for command message (continued) Message MiscellaneousCommand CommunicationModeCommand ConferenceCommand h223MultiplexReconfiguration NewATMVCCommand MobileMultilinkReconfigurationCommand Table 7.35 Message IDs for indication message Message NonStandard FunctionNotUnderstood MasterSlaveDeterminationRelease TerminalCapabilitySetRelease OpenLogicalChannelConfirm RequestChannelCloseRelease MultiplexEntrySendRelease RequestMultiplexEntryRelease RequestModeRelease MiscellaneousIndication JitterIndication h223SkewIndication NewATMVCIndication UserInput...

  • Page 171: Ras (Registration, Admission, Status)

    System maintenance and soft- ware update Table 7.35 Message IDs for indication message (continued) Message FlowControlIndication MobileMultilinkReconfigurationIndication 7.4.3.5 RAS (Registration, Admission, Status) As a general rule, the most important terminal and gatekeep- er messages appear written out with the gatekeeper's IP ad- dress (<ip addr>).

  • Page 172: Gatekeeper Reject Reason

    System maintenance and soft- ware update Here is the output syntax for call admission requests: H225 GkAdmission cr <cr> to <ip addr> H225 AdmissionConfirm <ip addr> cr <cr> H225 AdmissionReject <ip addr> reason <reason> Table 7.38 Gatekeeper 2 Trace Output Description Admission reject reason, see Table 7.42.

  • Page 173: Registration Reject Reason

    System maintenance and soft- ware update Table 7.41 Registration reject reason Reject Reason DiscoveryRequired InvalidRevision InvalidCallSignalAddress InvalidRASAddress DuplicateAlias InvalidTerminalType UndefinedReason TransportNotSupported TransportQOSNotSupported ResourceUnavailable InvalidAlias SecurityDenial RullRegistrationRequired AdditiveRegistrationNotSupported InvalidTerminalAliases GenericDataReason NeededFeatureNotSupported Table 7.42 Admission reject reason Reject Reason CalledPartyNotRegistered InvalidPermission RequestDenied UndefinedReason CallerNotRegistered RouteCallToGatekeeper...

  • Page 174: Unknown Gatekeeper Messages

    System maintenance and soft- ware update Table 7.42 Admission reject reason (continued) Reject Reason IncompleteAddress AliasesInconsistent RouteCallToSCN ExceedsCallCapacity CollectDestination CollectPIN GenericDataReason NeededFeatureNotSupported Table 7.43 Unknown Gatekeeper messages Message GatekeeperRequest GatekeeperConfirm GatekeeperReject RegistrationRequest RegistrationConfirm RegistrationReject UnregistrationRequest UnregistrationConfirm UnregistrationReject AdmissionRequest AdmissionConfirm AdmissionReject BandwidthRequest BandwidthConfirm BandwidthReject...

  • Page 175: Enum Output

    System maintenance and soft- ware update Table 7.43 Unknown Gatekeeper messages (continued) Message LocationConfirm LocationReject InfoRequest InfoRequestResponse NonStandardMessage UnknownMessageResponse RequestInProgress ResourcesAvailableIndicate ResourcesAvailableConfirm InfoRequestAck InfoRequestNak ServiceControlIndication ServiceControlResponse 7.4.3.6 ENUM output This output is assigned to group and occurs with Layer2 and Layer3 traces.

  • Page 176: Remote Output

    System maintenance and soft- ware update 7.4.4 Remote output This trace option provides output for communication with the GATE Manager or NMS. To activate this option, activate the section Remote in the GATE Manager. You can choose the depth of the trace output: Error is limited to error messages; Debug provides information;...

  • Page 177: Dtmf Tone Trace Output

    System maintenance and soft- ware update 7.4.5 DTMF tone trace output Output about the setup of connections with the DTMF module and DTMF tone recognition are debugged. The output differ- entiates between the groups err and inf. Output is defined with a d, and the port number is that of the virtual DTMF con- troller.

  • Page 178: Software Update

    Media channel free confirmation The following output shows the output for negotiated DTMF tones: d[<ctrl>]: dtmf send_info_ind <id> <<dtmf tone>> Software Update 7.5.1 Update the TELES software The following files are needed: xbri.tz1 start totalimage_bri.img The following files are optional: ipupdate.tz2 –...

  • Page 179: Restore The Original Teles Configuration

    7. Connect the VoIPBox DSL / VoIPBox BRI with Ethernet and wait until the startup is completed. 8. The original TELES configuration is now available. Until the next restart of the VoIPBox DSL / VoIPBox BRI the old configuration remains available in the following files: –...

  • Page 180: The Automatic Start Check

    System maintenance and soft- ware update 7.5.3 The automatic start check Since version V21.0.4.0 the /boot/startcheck file is available to prevent a boot loop of the VoIPBox DSL / VoIPBox BRI. This file contains a number. The default is 5. This number can be change.

  • Page 181: Online Traffic Monitor

    8 Online traffic monitor...

  • Page 182: Calculating And Resetting Statistic Values, Resetting Counters

    Online traffic monitor This chapter describes the contents of traffic monitoring, i.e. call statistics, system statistics, and call detail records. It also explains activation, resetting and analysis of the data. The Online Traffic Monitor allows you to collect and monitor statistics and call detail records (CDRs).

  • Page 183: Saving And Sending Statistics 1

    Wednesday into the file asr.log and sent to an e- mail account. Example 8.1 Saving and sending statistics 1 StatisticTime=/data/asr.log 00:00 00001000 @info@teles.de The following list shows the statistic values that are calculated for the entire system at the defined time and date and copied into the specified file:...

  • Page 184: Additional Resetting Of Counters A-F

    Online traffic monitor The following example shows how the statistics appear in the file into which they are copied. Example 8.2 Statistics file 26.10.04-00:00:00,Voip810000: Calls: 19351 (29716) - Minutes: 46647 - ASR1: 65.12% - ASR(ext): 65.12% - ASR(int): 65.30% - ACD: 144.63s 8.1.2 Additional resetting of counters A-F IF you use StatisticTimeReset instead of StatisticTime, the...

  • Page 185: Resetting Statistic Counters

    Online traffic monitor configure both StatisticTimeReset StatisticTime together. 8.1.3 Resetting statistic counters The following setting in the pabx.cfg resets the statistic counters and unblocks the controller group. The following syntax must be used: ResetCounter=<port> <time> <day | mask> Up to five entries for as many groups and/or times are possi- ble.
  • Page 186 Online traffic monitor With recording of files, system maintenance increases. You have to be sure to download or delete files and ensure that there is enough disk space left on the hard drive. The service indicator listed in the call log and missed calls list describes the type of connection as a four digit hexadecimal number.

  • Page 187: Call Log

    Online traffic monitor 8.2.1 Call log The following entry in the pabx.cfg configuration file activates the capability to generate CDRs in the VoIPBox: Log=/boot/cdr.log The cdr.log file is stored in the data directory. New entries are always added to the end of the file. The file is open only during editing.

  • Page 188: Sample Log File

    Online traffic monitor Sample log file The example below shows a sample log file. Example 8.6 Sample log file C1,25.11.09-10:16:20,25.11.09-10:16:27,9,111,,,,,0102,7,1f,0,,3663,10,,, C1,25.11.09-10:35:16,25.11.09-10:35:26,9,111,,,,,0102,10,1f,0,3,38922,14,,, C1,25.11.09-10:38:30,25.11.09-10:38:41,9,111,,,,,0102,11,90,0,3,38922,14,,, Differentiating between ports in the same trunk group To differentiate between ports with the same number in the CDRs, a specific node number must be defined.

  • Page 189: Activating Peer Data For Voip Calls 1

    Online traffic monitor Activating peer data for VoIP calls To generate a VoIP-call CDR entry that includes IP addresses for the remote device’s signaling and voice data, audio codec and frame size, the entry VoipIpLogging=Yes must be includ- ed in the VoIP profile. The following entry shows the route.cfg configuration file changed according to the formula.

  • Page 190: Missed Calls List

    Online traffic monitor CDRs for callback and two-stage calls In the case of CDR entries for DLA/Callback calls, the begin- ning and ending times for the first call leg is always used as the call time. The call time in seconds appears first for the first leg, followed by a slash and the connection time for the sec- ond leg.

  • Page 191: Sending Cdrs Via E-Mail

    Online traffic monitor Table 8.3 Failed log entries (continued) Column Description Call duration (if the call does not result in an Alerting, the entry will be -1) Number of call attempts The example below shows a sample failed log file. Example 8.12 Failed log file 1 F1,06.05.14-13:13:20,10493039928163502,5,,,,,0101,03,-1,0,,...

  • Page 192: Sending Cdrs Via E-Mail 2

    Online traffic monitor If you replace the first @ sign with an !, the present cdr.log will be sent whenecver a new one is generated. Example 8.14 Sending CDRs via e-mail 2 Log=/data/cdr.log daily 60 5 !bob@example.com VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 192...

  • Page 193: Troubleshooting

    9 Troubleshooting...

  • Page 194: No Connection To The System

    Troubleshooting This chapter discusses problems that you may encounter when operating your VoIPBox and offers solutions. The rea- sons are listed that may cause the different problems. Every reason is described in detail, the symptoms are identified and suggestions are made for solving the issue. If you can- not solve a problem using these instructions, please con- tact your service partner.

  • Page 195: System Does Not Start Correctly

    Troubleshooting ISDN access The dial-in number is missing or wrong (please refer to Chapter 9.1.5 →). The ISDN port is not loaded correctly / not active (please refer to Chapter 9.1.6 →). 9.1.1 System does not start correctly The system is not accessible at all or it restarts approximately every two minutes.

  • Page 196: Web Interface Is Not Accessible

    Troubleshooting If the system can be accessed but restarts approximately every two minutes, try to solve the problem by taking the following actions: – Connect to your VoIPBox via FTP. – Change to the boot directory. – Delete or rename the *.tz1 file. This stops the recur- ring reboot of the system and gives you time to search for the problem.
  • Page 197 Troubleshooting the web interface, missing web interface files or no permis- sion for port 80 are most likely the reason why access to a sys- tem through the web interface fails. Reasons The system is not accessible through the web interface because the required files were not installed.

  • Page 198: Ip Address Settings

    Troubleshooting 9.1.3 IP address settings Faulty IP address settings or a disabled ICMP can impede con- nections to your system. Reasons A syntax error in the IP address settings occurred in the ip.cfg file. The netmask was not set correctly in the ip.cfg file. The Internet Control Message Protocol (ICMP) is disabled in your network.

  • Page 199: Isdn Dial-In Number Missing Or Wrong

    Troubleshooting Symptoms The gateway cannot be accessed from remote. There is ethernet activity on the gateway. Ping works if you connect directly to the gateway. The gateway can be accessed via GATE Manager if you connect directly to the gateway. Solution Make sure there is ethernet activity by checking the ethernet...
  • Page 200 Troubleshooting Reasons The configuration of the RemoteCode parameter in the pabx.cfg is missing or does not match the corresponding dial-in number mapping in the route.cfg. There is no route configured for the ISDN dial-in number in the route.cfg. The ISDN dial-in number was configured in the route.cfg using the wrong number format (i.e.

  • Page 201: Isdn Port Not Loaded Correctly / Not Active

    Troubleshooting 9.1.6 ISDN port not loaded correctly / not active Other issues that can inhibit ISDN remote access relate to the ISDN interface. Reasons PRI only: The CRC4 mode does not match the peer’s CRC4 mode. The ISDN cable pin assignment is wrong. The TE or NT port configurations in the pabx.cfg file are missing or wrong.

  • Page 202: No Calls Are Possible

    Troubleshooting If layer 1 is still inactive, make sure that there is no problem with the wiring. Check the ISDN cable pin assignment. You can do so by looking at the cable colors or by using a cable tester. Please refer to Chapter 3.4.1 on page 31 →...

  • Page 203: Udp 5060 (Sip) For Ip 195.4.12.0/24 Range Enabled, All Other Udp Ports Blocked

    Troubleshooting Reasons VoIP: The firewall configuration in the ip.cfg blocks VoIP traffic. VoIP: The global VoIP settings cause problems. VoIP: Authentication failed. ISDN: The ISDN port is not active. Symptoms The incoming call does not arrive on the gateway. Solution VoIP: If a VoIP call does not arrive on the gateway, check your firewall settings in the ip.cfg file.

  • Page 204: Global Voip Settings In The Pabx.cfg

    Troubleshooting VoIP: Problems with incoming calls often originate in the glo- bal VoIP settings in the pabx.cfg file. Global VoIP settings ap- ply to the whole system, not just to any particular VoIP profile. Check that the SIP port has been set correctly and matches the sender’s destination port.

  • Page 205: Gatekeeper Profile

    GkAdd=192.168.0.10 GkPwd= GkTtl=300 GkMaxChan=30 GkDynMaxChan=Yes Example 9.5 Registrar profile [Registrar=reg] RegId=office.teles.de RegUser=4930399280 RegPwd=123456789 RegProxy=<ip adr.> RegPing=20 RegExpires=3600 ISDN: If an incoming ISDN call does not arrive on the gateway, check the port status (using GATE Manager) and the configu- ration of the ISDN ports in the pabx.cfg.

  • Page 206: Call Is Rejected Or Not Routed To The Right Destination

    Troubleshooting If you see in the GATE Manager that layer 1 is active but layer 2 does not show the entry “MFE” (Multiframe established), check the port configuration in the pabx.cfg file. Refer to Chapter 9.1.6 ISDN port not loaded correctly / not active → for details.
  • Page 207 Troubleshooting since mappings are searched from top to bottom and the first match is taken. Also ensure that no routes are missing. If you encounter problems routing VoIP calls, ascertain that the VoIP profiles are included in the mappings, since VoIP calls are distinguished by different profiles, not by different trunk groups.

  • Page 208: Calls From 195.4.13.14 Rejected

    Troubleshooting which you expect VoIP calls. Verify that the codecs which have been entered in the VoipCompression parameter match the peer’s codec. To look up the codec offered by the peer, you need to run a layer 2 / layer 3 trace. In the case of an outgoing call, set VoipDirection=Out or VoipDirection=IO.

  • Page 209: Software Update Problems

    Troubleshooting To allow for calls coming from 195.4.13.14 the VoipIpMask parameter needs to be changed, as shown in the following example. The IP addresses 195.4.13.0 to 195.4.13.15 can now send VoIP traffic. Example 9.7 Calls from 195.4.13.14 accepted [Voip:GW2] VoipDirection=In VoipPeerAddress=195.4.13.0 VoipIpMask=0xfffffff0 VoipCompression=g711u g711a...
  • Page 210 Troubleshooting Reasons The file transmission was interrupted. The system memory is full. The wrong file(s) has / have been transferred. Operating system and system files are not from the same version package, such as 16.1. The files have been loaded into the wrong directory (only when using FTP for transfer).
  • Page 211 Troubleshooting If you have access to the system, the operating system starts but the *.tz1 file is defective. Try to solve the problem by taking the following actions: – Connect with your VoIPBox via FTP. – Change to the boot directory. –...

  • Page 212: Appendix A Default Config Files

    Appendix A Default config files...

  • Page 213: Pabx.cfg

    Appendix A Default config files This chapter contains the config files available on the VoIPBox DSL / VoIPBox BRI after delivery. pabx.cfg The pabx.cfg contains the settings of the BRI ports and other system specific configurations. Example A.1 → shows the de- fault settings of the pabx.cfg.

  • Page 214: Pabx.cfg Of A Voipbox Bri 2

    Appendix A Default config files Example A.2 → shows the pabx.cfg of a VoIPBox BRI 2. This configuration is similar to the configuration of the VoIPBox DSL shown in Example A.1 →. Example A.2 pabx.cfg of a VoIPBox BRI 2 [System] PabxName=VoIPBOX_BRI_2 TraceLog=/boot/trace.log daily 1200 3...

  • Page 215: Pabx.cfg Of A Voipbox Bri 8

    Appendix A Default config files Example A.4 → shows the pabx.cfg of a VoIPBox BRI 8. This configuration is similar to the configuration of the VoIPBox BRI 2 but the number of ISDN controller is now 8, and an ad- ditional VoIP controller 09 with an AudioCodes codec.

  • Page 216: Ip.cfg

    Appendix A Default config files ip.cfg The ip.cfg contains the settings of the Ethernet interfaces. ample A.5 → shows the default settings of the ip.cfg of the VoIPBox DSL. Example A.5 Default ip.cfg of the VoIPBox DSL [system] Hostname=TAG99014188200316 [br0] IpAddress=192.168.1.2 netmask 255.255.255.0 #[Eth1] #IpAddress=192.168.1.2 netmask 255.255.255.0...
  • Page 217 Default ip.cfg of the VoIPBox DSL (continued) [dnsmasq] bogus-priv filterwin2k user=root interface=br0 domain=teles dhcp-range=192.168.1.50,192.168.1.90,12h cache-size=150 resolv-file=/etc/resolv.conf The [system] section contains the hostname of the VoIPBox DSL / VoIPBox BRI. The [br0] section hold the IP set- tings of the bridge 0 which contains both IP interfaces. The [dsl] section contains user name and password for DSL ac- cess.

  • Page 218: Route.cfg

    Appendix A Default config files Example A.6 → contains the default ip.cfg of the VoIPBox BRI. This configuration assigns an IP address to the bridge inter- face of both IP interfaces. Example A.6 ip.cfg od the VoIPBox BRI [system] Hostname=TAG99014188200316 ;;...
  • Page 219 Appendix A Default config files Example A.7 Default route.cfg (continued) ;;; SIP profile ;;; --------------------- [Voip:PeerA] VoipDirection=IO VoipPeerAddress= ;; ip address:port e.g. 1.2.3.4:5060 VoipIpMask=0xffffffff VoipSignalling=1 VoipUser= VoipPwd= ;VoipOwnAddress= ; optional VoipRegistrar=rega VoipMaxChan=4 VoipCompression=g711a g711u g729a g729b [Registrar:rega] RegId= ;; ip address:port e.g. 1.2.3.4:5060 RegOwnId=user@1.2.3.4 RegUser= RegPwd=...

  • Page 220: List Of Examples

    List of examples List of examples Common DSL settings for VLAN/ATM access and PPP login........39 DSL access with dynamic IP address................. 40 DSL access with fixed IP address ................40 PPPoE configuration on ETH2 ..................41 Main sections of the ip.cfg..................41 Different IP settings for every interface configured in the ip.cfg......
  • Page 221 List of examples 6.11 Overwriting OAD......................122 6.12 Restrict 1 ........................123 6.13 Restrict 2 ........................124 6.14 Restrict 3 ........................124 6.15 Restrict 4 ........................125 6.16 MapAll ......................... 125 6.17 Restrict 5 ........................126 6.18 Restrict 6 ........................126 6.19 Restrict 7 ........................
  • Page 222 List of examples Default pabx.cfg......................213 pabx.cfg of a VoIPBox BRI 2..................214 pabx.cfg of a VoIPBox BRI 4..................214 pabx.cfg of a VoIPBox BRI 8..................215 Default ip.cfg of the VoIPBox DSL................216 ip.cfg od the VoIPBox BRI ..................218 Default route.cfg......................

  • Page 223: List Of Tables

    Li st of tabl es List of tables Power Supply Symbols....................17 Default Ports Used for Specific Services ..............22 Pin assignment of the Ethernet connector..............32 LEDs on the Eth ports....................32 VoIPBox LEDs .........................35 DSL settings for line access and login .................38 GUI: Sections ........................47 VoIP configuration in a route.cfg .................50 Configuration Files......................53...
  • Page 224 Li st of tabl es pabx.cfg: DynDNS......................148 Trace options........................149 Online trace activation window .................151 H.323 output ........................156 H.323 session .......................157 H.225 signaling......................157 ETS message types ......................157 7.10 Incoming VoIP calls......................158 7.11 Compression codecs used..................159 7.12 Calls to the IP network 1 ....................159 7.13 Calls to the IP network 2 ....................160 7.14...
  • Page 225 Li st of tabl es 1TR6 service indicators ....................186 Call log entries......................187 Failed log entries......................190 VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 225...

  • Page 226: List Of Figures

    Li st of fi gures List of figures VoIP gateway ........................26 Least cost router 2nd generation ................27 VoIPBox BRI with 2 BRI and DSL: front and rear view..........30 VoIPBox BRI with 8 BRI and DSL: front and rear view..........30 ISDN Wiring Scheme......................31 Ethernet connector PIN assignment ................32 DSL connector PIN assignment..................33 GATE Manager .......................36...

This manual is also suitable for:

Voip box dsl 2Voip box dsl 4Voip box bri seriesVoipbox bri 2Voipbox bri 4Voipbox bri 8 ... Show all

Table of Contents