1. Manuals
  2. Brands
  3. TELES Manuals
  4. Telephone
  5. VoIPBox BRI
  6. Reference manual

TELES VoIPBox BRI Reference Manual

Hide thumbs Also See for VoIPBox BRI:
Table of Contents

Advertisement

Quick Links

Download this manual
VoIPBox BRI
Reference manual
Software version 18.0

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for TELES VoIPBox BRI

Summary of Contents for TELES VoIPBox BRI

  • Page 1 VoIPBox BRI Reference manual Software version 18.0...
  • Page 2 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

    EMC Protection................20 System Security ................20 1.5.1 Servicing the VoIPBox ..............21 1.5.2 Protecting the Operating System ..........22 CDR Files..................23 Network Security ................24 Overview ..................27 Features................... 28 Implementation scenarios ............30 TELES Product Version 18.0.002 Page 3...
  • Page 4 Self Provisioning with NMS ............42 3.11 Remote Access and Access Security ..........42 3.11.1 GATE Manager ................43 3.11.2 Graphical User Interface ............... 44 3.11.3 FTP....................46 3.11.4 Setting a Password for Remote Access ........47 TELES Product Version 18.0.002 Page 4...
  • Page 5 System Settings ................70 4.2.1.1 Bypass Relay ................... 71 4.2.1.2 Log Files................... 71 4.2.1.3 Night Configuration ............... 73 4.2.1.4 Controllers ..................75 4.2.1.5 Subscribers ..................77 4.2.1.6 Global Settings................78 4.2.2 SMTP-Client Configuration............82 TELES Product Version 18.0.002 Page 5...
  • Page 6 ISDN dial-up for terminating VoIP calls ........108 Backbone router using a backup gatekeeper......110 Backbone router with direct endpoint signaling (H.323) ..112 IntraSTAR..................114 Backbone router with RADIUS management ......116 VoIP backup and automatic reactivation ........117 TELES Product Version 18.0.002 Page 6...
  • Page 7 RAS (Registration, Admission, Status) ........158 6.7.3.6 ENUM output ................163 6.7.3.7 Examples ..................163 6.7.4 Remote output ................167 6.7.5 SMTP trace output ...............168 6.7.6 Number portability trace output..........172 6.7.7 DTMF tone trace output ..............173 Signaling and routing features ..........175 IntraSTAR..................176 TELES Product Version 18.0.002 Page 7...
  • Page 8 Setting sending complete byte in setup........190 7.11 OAD screening................191 7.12 Miscellaneous routing methods..........193 7.12.1 Routing calls without a destination number......193 7.12.2 Routing calls based on existence of destination number ..194 7.12.3 Changing cause values ..............195 TELES Product Version 18.0.002 Page 8...
  • Page 9 Resetting statistic counters............218 Generating and retrieving CDRs..........218 9.2.1 Call log ...................219 9.2.2 Missed calls list ................222 Sending CDRs via e-mail..............224 Two stage dialing/callback server functionality ....226 10.1 Activating DTMF tone recognition..........228 10.2 Announcements ................228 TELES Product Version 18.0.002 Page 9...
  • Page 10 System does not start correctly..........263 12.1.2 Web interface is not accessible ..........264 12.1.3 IP address settings ...............266 12.1.4 Firewall issues and NAT / PAT settings ........266 12.1.5 ISDN dial-in number missing or wrong ........267 TELES Product Version 18.0.002 Page 10...
  • Page 11 12.2 No calls are possible ..............270 12.2.1 Call does not arrive on the gateway ..........271 12.2.2 Call is rejected or not routed to destination......274 12.2.3 Call is rejected elsewhere............278 12.3 Software update problems ............279 TELES Product Version 18.0.002 Page 11...

  • Page 12: Preface

    Preface In this manual This manual describes the set up of your VoIPBox BRI. It is written for network administrators who use and maintain the gateway. To use this manual you need some experience work- ing with networking devices and be familiar with the concepts and terminology of telecommunication technology.
  • Page 13 Could cause injury by high voltage and/or damage the sys- tem. Electrostatic discharge Components at risk of discharge must be grounded before being touched. Explosion hazard Injury hazard due to explosions endangering the person or the system. VoIPBox BRI Version 18.0.002 Page 13...

  • Page 14: Organization

    Chapter 1 – Safety and security precautions starts with the safety and security precautions. Make sure that everyone who works with the VoIPBox BRI is aware of these precau- tions. The VoIPBox BRI described at the end of this chapter.
  • Page 15 The reasons 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 cannot solve a problem using these instructions, please contact your service partner. VoIPBox BRI Version 18.0.002 Page 15...

  • Page 16: Safety And Security Precautions

    1 Safety and security precautions...

  • Page 17: Safety Measures

    This chapter starts with the safety and security precau- tions. Make sure that everyone who works with the VoIPBox BRI is aware of these precautions. The VoIPBox BRI described at the end of this chapter. Please be sure and take time to read this section to ensure your personal safety and proper operation of your gateway.

  • Page 18: Power Supply

    Tested and certified as per EN60950-1 1.2.2 Symbols The symbols on the power supply have the following mean- ings: Table 1.1 Power Supply Symbols Symbol Meaning Certified to conform with European norms. Protective insulation provided. For indoor use only. VoIPBox BRI Version 18.0.002 Page 18...

  • Page 19: Instructions For Use

    Make sure you use only the correct input voltage. Make sure the installation site is sufficiently ventilated. Use the device only in dry, indoor locations, and protect it from humidity. Do not subject the device to direct sunlight. VoIPBox BRI Version 18.0.002 Page 19...

  • Page 20: Jacks

    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 the public trash).

  • Page 21: Servicing The Voipbox

    Servicing also includes looking after the room in which the system is set up. Ensure that the air-conditioning and its filter system are regularly checked and that the premises are cleaned on a regular basis. VoIPBox BRI Version 18.0.002 Page 21...

  • Page 22: Protecting The Operating System

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

  • Page 23: Cdr Files

    Inaccuracies in the generation of CDRs may occur for ac- tive connections if traffic is flowing on the system while modifications in configuration or routing files are activat- VoIPBox BRI Version 18.0.002 Page 23...

  • Page 24: Network Security

    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 25 Default Ports Used for Specific Services Service Protocol Port For all systems except C X Pro 21 (default, can be set) Telnet (for TELES debug access only) 23 (default, can be set) SMTP DNS forward HTTP 80 (default, can be set) SNTP...
  • Page 26 Port For NMS Telnet MySQL database 3306 NMS protocol 5000 NMS update 5001 NMS task 5002 NMS task 5003 NMS Listen 4444 For C X Pro Call Manager Radius authentication 1812 Radius accounting 1813 VoIPBox BRI Version 18.0.002 Page 26...

  • Page 27: Overview

    2 Overview...

  • Page 28: Features

    This chapter describes the general features of the VoIPBox BRI and the main features for VoIP and telephony. The VoIPBox BRI is a media converter that facilitates the con- nection of ISDN service equipment with a voice over IP (VoIP) network.
  • Page 29 2nd separate 10/100 Base-T Ethernet interface Status indication via LEDs Integrated mail client capable of SMTP authentication E-mail messages can trigger calls and play attached an- nouncements Automatic test call Redial function Autodial function VoIPBox BRI Version 18.0.002 Page 29...

  • Page 30: Implementation Scenarios

    VoIP destinations. Fax transmission occurs via T.38 or fallback to G.711a. Backup routes can be activated in case of VoIP peer failure. After a defined amount of time, the VoIPBox resumes its primary route. Figure 2.1 VoIP gateway VoIPBox BRI Version 18.0.002 Page 30...
  • Page 31 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. Figure 2.2 Least cost router 2nd generation VoIPBox BRI Version 18.0.002 Page 31...

  • Page 32: Voipbox Installation

    3 VoIPBox installation...

  • Page 33: Checklist

    1 RJ-45 LAN cable with gray connectors Check the contents to make sure everything is complete and undamaged. Immediately report any visible transport damag- es to customer service. If damage exists, do not attempt oper- ation without customer-service approval. VoIPBox BRI Version 18.0.002 Page 33...

  • Page 34: Voipbox Hardware Description

    ISDN6 ISDN7 ISDN8 ETH1 ETH2 Figure 3.1 VoIPBox BRI: front and rear view 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 Power VoIPBox BRI Version 18.0.002...

  • Page 35: Isdn Wiring

    3.4.2 Ethernet Wiring To connect the VoIPBox’s Ethernet port to your local network, connect the system to an Ethernet switch or hub in your net- work. Use the three meter cable with gray connectors. VoIPBox BRI Version 18.0.002 Page 35...

  • Page 36: Preparing For Installation

    Connect the VoIPBox with the local network Using the ISDN connection cables included in the pack- age contents, connect the VoIPBox with your PBX and/or the PSTN according to the required port configuration. Connect the VoIPBox with the power supply. VoIPBox BRI Version 18.0.002 Page 36...

  • Page 37: Led Functionality

    Quickstart is an application that helps you to configure the IP settings of your VoIPBox quickly and conveniently without changing any network settings on your computer. You will need Quickstart as of version 15.0. Quickstart can be installed on Windows operating systems. VoIPBox BRI Version 18.0.002 Page 37...

  • Page 38: Installing Quickstart

    Quickstart.exe. The program will automatically search for your VoIPBox in the local network. For Quickstart, the source UDP port is 57445. It might be necessary to change the fire- wall rules on your system. VoIPBox BRI Version 18.0.002 Page 38...
  • Page 39 This column shows the number of VoIP channels per VoIP Module. Type Lists the type of system. An X means the system is a TELES box-based system. CF Mounted This column is not relevant for TELES box-based systems. In the Options menu, you can suppress or activate ICMP ping to test the Internet connection.
  • Page 40 Ethernet interface and the net- mask will be temporary changed. This can be helpful if you want to set up local remote access to the system and use oth- VoIPBox BRI Version 18.0.002 Page 40...

  • Page 41: Startup Via Ftp

    IP address from network range 192.168.1.0 Class C and then access the system via FTP. The default user is teles and the default password is tcs-ag. Download the default configuration files from the /boot direc-...

  • Page 42: Self Provisioning With Nms

    After the system has been configured via Quickstart and all cables are connected, remote administration and mainte- nance can occur with the GATE Manager (Chapter 3.11.1 →), the GUI (Chapter 3.11.2 →), or via FTP (Chapter 3.11.3 →). VoIPBox BRI Version 18.0.002 Page 42...

  • Page 43: Gate Manager

    Display the status of the interfaces. To complete the configuration retrieve and edit the config files as described in Chapter 4 on page 49 →. You have to use GATE Manager version 17.1 or later. For a detailed description VoIPBox BRI Version 18.0.002 Page 43...

  • Page 44: Graphical User Interface

    Simply open a browser and enter the system’s IP address in the address bar. We recommend that you use In- ternet Explorer 6/7 or later. The following administrative levels apply: VoIPBox BRI Version 18.0.002 Page 44...
  • Page 45 The user interface is divided into the following main sections: Table 3.3 GUI: Sections Section Description User Data Here you can change the user passwords and the language for the HTTP interface. System Settings IP Settings:Settings for the Ethernet interfaces and related servic- VoIPBox BRI Version 18.0.002 Page 45...

  • Page 46: Ftp

    Remote access can also occur via FTP. You can use FTP to transfer configuration files. You can also carry out functions and traces with raw commands. Use the username teles and the defined password to connect to the system with FTP.

  • Page 47: Setting A Password For Remote Access

    VoIPBox installation Once you have access to the system, you will be in the folder /home/teles. To upload or download configuration files change to the directory /boot. To download log files, also change to the directory /boot. The following commands can be carried out via FTP access: Table 3.5...
  • Page 48 Transfer the pabx.cfg to the system using the GATE Manager and activate the new configuration. After the file has been transferred reboot the system. The system can than be ac- cessed only with the correct password. Don’t forget to mem- orize it! VoIPBox BRI Version 18.0.002 Page 48...

  • Page 49: Configuration Files

    4 Configuration files...
  • Page 50 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 possible damage out of or in relation to such changes. Please thoroughly check any changes you or a third party have made to your configuration.

  • Page 51: Configuration File Ip.cfg

    The Ethernet Media Access Controller section(s) define the [emac1] (optional) physical Ethernet interface(s). [httpd] This section contains the port and access password parame- ters for the graphical user interface. [nat] (optional) This section includes settings for Network Address Translation. VoIPBox BRI Version 18.0.002 Page 51...

  • Page 52: System Section Configuration

    The [System] section contains entries that define the default gateway and/or special routing entries. To define the stan- dard gateway, use the following entry to set the IP address: DefaultGw=<ip addr> Example 4.1 Default gateway configuration [System] DefaultGw=192.168.1.254 VoIPBox BRI Version 18.0.002 Page 52...

  • Page 53: Ethernet Interface Configuration

    The following entry is used in the [emac1] section if operation of the system is occurs in bridge mode. IpAddress=up 4.1.3 GUI Settings The following parameter is used to change the GUI port in the section [httpd] (default 80): GuiPort=<num> VoIPBox BRI Version 18.0.002 Page 53...

  • Page 54: Bridge Configuration

    Ethernet switch does not have any more ports available for connection of the system. You can simply unplug a cable and plug it into the system’s second Ethernet interface. Example 4.5 Bridge configuration [bridge0] BrConfig=add emac0 add emac1 up VoIPBox BRI Version 18.0.002 Page 54...

  • Page 55: Nat Configuration

    (usually exactly one address), into which the lo- cal IP addresses are to be translated. The IP address is en- tered in decimal notation, followed by a slash (/) and the netmask in bit notation. VoIPBox BRI Version 18.0.002 Page 55...

  • Page 56: Pppoe Configuration

    0/0 port 443 -> 192.168.1.100 port 443 tcp 4.1.6 PPPoE Configuration The protocol Point-to-Point over Ethernet is used for DSL communication with the DSLAM. That means the system can connect directly with the carrier network and terminate VoIP traffic directly. VoIPBox BRI Version 18.0.002 Page 56...
  • Page 57 Route parameter for each range. Bear in mind that configuration of the firewall, the NAT mod- ule and prioritization of the VoIP packets must be considered when routing voice and data through the DSL line. VoIPBox BRI Version 18.0.002 Page 57...

  • Page 58: Firewall Settings

    Example 4.8 Firewall settings: blocking ports [firewall] fw=pass in quick on emac0 proto tcp from 192.168.1.10/32 to any port eq 4445 flags S keepstate keep frags fw=block in log quick on emac0 all VoIPBox BRI Version 18.0.002 Page 58...
  • Page 59 <num> defines the port as number (e.g.: port eq 4445). keep state Ensures that the firewall checks packets from the beginning to the end of a session. This is necessary, as the firewall does not know when a session begins or ends. VoIPBox BRI Version 18.0.002 Page 59...

  • Page 60: Bandwidth Control

    You must set the priority for voice signal- ing and for the voice packets. That means you must prioritize SIP/H.323, RTP and RTCP. You will find the ports used in Table 4.16 →, in the following entries: H225Port VoIPBox BRI Version 18.0.002 Page 60...
  • Page 61 <dest_addr> (can be followed by netmask <mask>) <dest_port> (can be followed by netmask <mask>) <src_addr> <src_port> <protocol tos value> 6 for TCP 17 for UDP VoIPBox BRI Version 18.0.002 Page 61...

  • Page 62: Dhcp Server Settings

    All DHCP queries are accepted and the configured settings are transmitted to the cli- ents. ddns-update-style none; Deactivates dynamic update of the domain name system as per RFC 2136. ; Parameters for the Subnet subnet <network address> netmask <mask for network range> { <list> VoIPBox BRI Version 18.0.002 Page 62...
  • Page 63 ; Global dhcp parameters allow unknown-clients; ddns-update-style none; ; Parameter for the Subnet subnet 192.168.1.0 netmask 255.255.255.0 { range 192.168.1.3 192.168.1.20; option broadcast-address 192.168.1.255; option domain-name "company.de"; option domain-name-servers 192.168.1.2; option routers 192.168.1.2; option subnet-mask 255.255.255.0; VoIPBox BRI Version 18.0.002 Page 63...

  • Page 64: Dnsmasq Settings

    Whenever /etc/resolv.conf is re-read, clear the DNS cache. This is useful when new nameservers may have different data than that held in cache. Example 4.12 DNSmasq settings bogus-priv filterwin2k user=teles cache-size=150 cler-on-reload VoIPBox BRI Version 18.0.002 Page 64...

  • Page 65: Ppp Configuration For Dial-Up Connection

    Defines if the PPP interface is activated automatically after system start. The following values are possible: 0 = No automatic PPP activation (default) 1 = Automatic PPP activation IdleTO=<sec> Enter the number of seconds without traffic before the interface tears down the con- nection. VoIPBox BRI Version 18.0.002 Page 65...
  • Page 66 IP address. Example 4.13 Settings in the Section of the [xppp] ip.cfg [xppp0] Dad=12345 User=user Pwd=pwd Route=0.0.0.0 AuthProto=chap IdleTO=60 MTU=1500 Rfc1662=0 LcpTO=500 StartDelay=10 AutoUp=1 VoIPBox BRI Version 18.0.002 Page 66...

  • Page 67: Vlan Configuration

    IpAddress=192.168.199.1 4.1.13 Examples 4.1.13.1 Default configuration In the following example, the system’s IP address is 192.168.1.1, the netmask is 255.255.255.0, and the standard gateway is 192.168.1.254. Example 4.15 Default configuration [System] DefaultGw=192.168.1.254 [emac0] IpAddress=192.168.1.1/24 VoIPBox BRI Version 18.0.002 Page 67...

  • Page 68: Active Ethernet Bridge

    Integrated DSL-Router Scenario for VoIP In the following example, the system is connected to the local IP network through emac0. The DSL modem is connected to the emac1 interface, which enables the system to connect di- VoIPBox BRI Version 18.0.002 Page 68...
  • Page 69 ; Global dhcp parameters allow unknown-clients; ddns-update-style none; ; Parameter for the Subnet subnet 192.168.1.0 netmask 255.255.255.0 { range 192.168.1.3 192.168.1.20; option broadcast-address 192.168.1.255; option domain-name "company.de"; option domain-name-servers 192.168.1.100; option routers 192.168.1.2; option subnet-mask 255.255.255.0; VoIPBox BRI Version 18.0.002 Page 69...

  • Page 70: Vlan Scenario

    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: Hardware Bypass relay Log files Night configuration VoIPBox BRI Version 18.0.002 Page 70...

  • Page 71: Bypass Relay

    CDRs, unconnected calls, system events, trace output and sta- tistics can be saved into files. The following entries are necessary to generate log files: Table 4.11 : Log File Entries pabx.cfg Entry Description ActionLog=/boot/protocol.log System events Log=/boot/cdr.log CDR entries VoIPBox BRI Version 18.0.002 Page 71...
  • Page 72 Normally size can be limited for these files, e.g. 5 files of 1MB each. If the fifth file is full, the first one will automatically be overwritten. VoIPBox BRI Version 18.0.002 Page 72...

  • Page 73: Night Configuration

    ActionLog=/boot/protocol.log - 1000 5 Please remember to keep track of how much memory is available on the system. 4.2.1.3 Night Configuration The sections for the time-dependent configuration changes and time-controlled routings are defined here. VoIPBox BRI Version 18.0.002 Page 73...
  • Page 74 ([System] section) every day at 8:00 p.m: Example 4.23 Night parameters 2 NightResetTime=20:00 11111111 The configuration section is activated on November 5, Decem- ber 24, and at noon on Mondays. Example 4.24 Night parameters 3 Night1=12:00 10000010 Holiday=05.11. Holiday=24.12. VoIPBox BRI Version 18.0.002 Page 74...

  • Page 75: Controllers

    (Terminal Endpoint). All TE ports must be con- figured together starting with port 1 on the left. internal (Network Termination). All NT ports must be configured together to the right of the TE ports. VOIP VoIP module VoIPBox BRI Version 18.0.002 Page 75...
  • Page 76 For TE-ports only: keeps ISDN layer 2 active all the time. TRAP Sends an SNMP trap if layer 1 changes from active to inactive or from inactive to active. following example applies for the VoIPBox BRI with 4 ISDN ports. Example 4.25 VoIPBox BRI with 4 ISDN ports...

  • Page 77: Subscribers

    DTMF recognition if the callback platform is used. DTMF[<sec>,/ Keyword to configure the DTMF controller. For a description of the for- <dir>/<file>] mat, please see Chapter 10.2 on page 228 →. VoIPBox BRI Version 18.0.002 Page 77...

  • Page 78: Global Settings

    Defines whether CNG (a tone initially sent by a fax device) is transmitted by means of T.38 or RTP: 0 = RTP (default) 1 = T.38 VoipSendUpdate=<mode> Allows ( ) sending of UPDATE messages or not ( is the default value. VoIPBox BRI Version 18.0.002 Page 78...
  • Page 79 NOTE: This is not a solution for all firewall types. StunServerPollInterval=<sec> Interval (in seconds) for the stun request at each port (default 600). Radius=<mode> On (default) activates the Radius service. If you change Off to On, you must restart the system. VoIPBox BRI Version 18.0.002 Page 79...
  • Page 80 Defines the TFTP access port (default 69). Ftpd=<mode> Activates (on) or deactivates (off) FTP access. Default on. Telnetd=<mode> Activates (on) or deactivates (off) TELNET access. Default on. Tftpd=<mode> Activates (on) or deactivates (off) TFTP access. Default off. VoIPBox BRI Version 18.0.002 Page 80...
  • Page 81 If the system is connected via ISDN, a clock may come from the network connected to the corresponding port. Enter TIME in the pabx.cfg’s Subscriber line for the TE port to take the time from the port. VoIPBox BRI Version 18.0.002 Page 81...

  • Page 82: Smtp-Client Configuration

    If 0 is entered, the SMTP port (25) will be blocked for incoming sessions. Default 100. MailPortIn=<num> Enter a TCP port for incoming e-mail (default 25). MailPortOut=<num> Enter a TCP port for outgoing e-mail (default 25). VoIPBox BRI Version 18.0.002 Page 82...
  • Page 83 Configuration files Table 4.17 pabx.cfg Mail Parameters (continued) Mail Parameters MailPropPort=<num> Enter the port number for a TELES proprietary mail protocol. MailPwdIn=<password> Enter a password for incoming e-mail authentication. MailPwdIn=<password> Enter a password for incoming e-mail authentication. MailPwdOut=<password> Enter a password for outgoing e-mail authentication.

  • Page 84: Snmp Settings

    VoIPBox network devic- es and their functions. For a detailed description of SNMP configuration, please refer to Chapter 6.4 SNMP agent →. You must restart the system after making changes to acti- vate the settings. VoIPBox BRI Version 18.0.002 Page 84...

  • Page 85: Time-Controlled Configuration Settings

    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. VoIPBox BRI Version 18.0.002 Page 85...
  • Page 86 Contains the calling number (OAD). The special symbol ? may be used as a wild- card to represent any character. <pl> Stands for a virtual placeholder. The DAD is prefixed with the contents of this variable. VoIPBox BRI Version 18.0.002 Page 86...
  • Page 87 All calls coming from BRI controller 9 (PSTN) are sent to BRI controller 10 (PBX). First, the Restrict command adds the pre- fix “pl” to the DAD of the received call for all calls coming from VoIPBox BRI Version 18.0.002 Page 87...

  • Page 88: Mapall

    9123456 is added to it. The called number is 912345678 with 9 being the port. MapAll123456=9 means that 123456 is cut off and 9 added. The called number is 978 with 9 being the port. VoIPBox BRI Version 18.0.002 Page 88...
  • Page 89 If you change the order of both mappings, international calls would be sent to con- troller 9 instead of 40. Example 4.30 Map Parameters route.cfg MapAll00=40DF:00 MapAll0=90 VoIPBox BRI Version 18.0.002 Page 89...

  • Page 90: Redirect

    <time> For type 2 redirect entries, a timer (in seconds) can be defined after the service indicator entry. VoIPBox BRI Version 18.0.002 Page 90...
  • Page 91 Subscriber line in the pabx.cfg: BUSY[<cause>] This parameter defines a hexadecimal cause value according to DSS1. When connections to the destination are rejected be- cause of the reason defined by the cause value, the VoIPBox VoIPBox BRI Version 18.0.002 Page 91...

  • Page 92: Voip Profiles

    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. Default is 0xffffffff (only incoming traffic is accepted from the defined peer address). VoIPBox BRI Version 18.0.002 Page 92...
  • Page 93 VoIP profile might be switched off ( VoipECE=no VoipMaxChan=<count> Maximum number of channels that can be used with the profile. If this parameter is not defined (default), there will be no limit. VoIPBox BRI Version 18.0.002 Page 93...
  • Page 94 Enter the name of the Radius server to activate accounting. VoipRadiusIMSINegotiation=<mode> If yes is entered, the <system> will negotiate the IMSI to be used in the Radius access request. It will transmit the IMSI in the RADIUS attribute: Filter-Id (11). Default no. VoIPBox BRI Version 18.0.002 Page 94...
  • Page 95 VoipSignalling=<int> profile for an incoming voip call, i.e. the signalling for this voip call must match the VoipSignalling parameter in this profile. Default VoIPBox BRI Version 18.0.002 Page 95...

  • Page 96: Gatekeeper Profiles

    GkUseStun=<mode> Enter (default) to use the STUN values for the GK profile. GkTerminalAliasWithPrefix=<mode> Some gatekeepers may require that prefixes are listed in the Terminal Alias section. Enter to activate this function; default value is VoIPBox BRI Version 18.0.002 Page 96...

  • Page 97: Registrar Profiles

    When Yes is set (default), the same caller ID is always used for SIP registration. Set No to change the caller ID for each SIP registration. RegContact=<name or ip addr> Used in the field. Contact: RegContactParam=<string> Sets additional header-parameters in the contact field (e.g.the q-value: RegContact- Param=q=1.0). VoIPBox BRI Version 18.0.002 Page 97...
  • Page 98 Enter Yes when an VoIPBox appears behind a NAT and STUN cannot be used. Default RegSameCallID=<mode> The same call ID is used for SIP registration Enter No to change the call ID for every reregistration. (default Yes). VoIPBox BRI Version 18.0.002 Page 98...

  • Page 99: Radius Profiles

    This parameter is used to set the calling station ID. The default setting is the OAD, but you can define any calling station ID. To define a partial calling station ID, enter a ? for each digit. For example, CallingStationId=??? will consist of the first three digits of the OAD. VoIPBox BRI Version 18.0.002 Page 99...
  • Page 100 5 = Xylogics proprietary IPX/SLIP 6 = X.75 Synchronous NasId=<string> The string entered is used as network access server identifier attribute in access re- quests. If no string is entered, the attribute will not be set (default). VoIPBox BRI Version 18.0.002 Page 100...

  • Page 101: Routing Examples

    5 Routing examples...

  • Page 102: Voipbox As A Second-Generation Lcr

    01078. All other calls are sent to the PSTN unchanged. All calls from the PSTN or from a VoIP carrier are sent directly to the NT controller, to which the PBX is attached. VoIPBox BRI Version 18.0.002 Page 102...
  • Page 103 [Voip=DF] VoipDirection=IO VoipPeerAddress=domain.com VoipIpMask=0x00000000 VoipSignalling=1 VoipCompression=g729 g711a t38 VoipSilenceSuppression=Yes VoipProxy=192.168.0.150 VoipOwnAddress=user@domain.com VoipUser=user VoipPwd=pwd VoipMaxChan=8 VoipTxM=2 VoipRegistrar=reg [Registrar=reg] RegId=domain.com RegOwnId=user@domain.com RegUser=user RegPwd=pwd RegProxy=192.168.0.150 Bear in mind that emergency calls must be routed to the PSTN. VoIPBox BRI Version 18.0.002 Page 103...

  • Page 104: Voipbox In An H.323 Network

    Since the peers may use various compression algorithms, you can define several if you so choose. The codec with the highest priority is G.729. If the peer does not support it, G.72632, G.711a, G.711u and are also possible. Silence suppression is active. VoIPBox BRI Version 18.0.002 Page 104...
  • Page 105 ;To VoIP MapAll?=40DF:? [Voip=DF] VoipDirection=IO VoipPeerAddress=0.0.0.0 VoipIpMask=0x00000000 VoipSignalling=0 VoipCompression=g729 g72632 g711a g711u t38 VoipSilenceSuppression=Yes VoipMaxChan=8 VoipTxM=4 VoipGk=GK1 [Gatekeeper=GK1] RasPort=1719 OwnRasPort=1719 RasId=VoIPBOX01 RasPrefix=0049 GkId=GK GkAdd=192.168.0.10 GkPwd= GkTtl=300 GkMaxChan=8 Figure 5.2 VoIPBox in an H.323 network VoIPBox BRI Version 18.0.002 Page 105...

  • Page 106: Work@Home Scenario With Signaling Through A Sip Proxy

    ;all other calls from PSTN or VoIP send to ISDN PBX unchanged MapAllpl=10 ; all calls from ISDN PBX to VoIP carrier except remote users DTMFWaitDial=5 MapAll0=|40DF:0<<24 MapAll1=|40DF:1<<24 MapAll2=|40DF:2<<24 MapAll3=|40DF:3<<24 MapAll4=|40DF:4<<24 MapAll5=|40DF:5<<24 MapAll6=|40DF:6<<24 MapAll7=|40DF:7<<24 MapAll8=|40DF:8<<24 MapAll9=|40DF:9<<24 MapAll*=|40DF:*<<24 MapAll#=|40DF:#<<24 VoIPBox BRI Version 18.0.002 Page 106...
  • Page 107 VoipRFC2833PayloadType=101 VoipAutoRtpAddr=Yes VoipT303=5 ;VoIP profile to connect with the SIP network: [Voip=DF] VoipDirection=IO VoipPeerAddress=sip-carrier.com VoipIpMask=0xffffffff VoipUser=user VoipPwd=pwd VoipSignalling=1 VoipCompression=g729 g723 g711a g711u t38 VoipSilenceSuppression=Yes VoipMaxChan=8 VoipTxM=2 VoipDtmfTransport=3 VoipRFC2833PayloadType=101 VoipRegistrar=Reg [Registrar=Reg] RegId=sip-carrier.com RegUser=user RegPwd=pwd RegExpires=3600 VoIPBox BRI Version 18.0.002 Page 107...

  • Page 108: Isdn Dial-Up For Terminating Voip Calls

    This can be used in locations without broadband Internet con- nection and generally have several simultaneous voice calls. Only one ISDN B-channel connection to the Internet is set up, but up to six simultaneous voice calls can be transmitted (de- VoIPBox BRI Version 18.0.002 Page 108...
  • Page 109 29015 keep state keep frags # other will be blocked fw=block in log quick on xppp0 all fw=block out log quick on xppp0 all VoIPBox BRI Version 18.0.002 Page 109...

  • Page 110: Backbone Router Using A Backup Gatekeeper

    VoIP profile is necessary. When a gatekeeper ends registration or does not respond, the next gatekeeper on the list is automatically used. Compression G.729 and T.38 (fax) are used. Silence suppression is active. VoIPBox BRI Version 18.0.002 Page 110...
  • Page 111 MapAlltobri=10 MapAll?=40DF:? [Voip=DF] VoipDirection=IO VoipPeerAddress=0.0.0.0 VoipIpMask=0x00000000 VoipSignalling=0 VoipCompression=g729 t38 VoipSilenceSuppression=Yes VoipMaxChan=8 VoipTxM=4 VoipGk=GK1 GK2 [Gatekeeper=GK1] RasPort=1719 OwnRasPort=1719 RasId=VoIPBOX01 RasPrefix=0049 GkId=GK GkAdd=192.168.0.10 GkPwd= GkTtl=300 GkMaxChan=8 [Gatekeeper=GK2] RasPort=1719 OwnRasPort=1719 RasId=VoIPBOX01 RasPrefix=0049 GkId=backupGK GkAdd=192.168.0.12 GkPwd= GkTtl=300 GkMaxChan=8 VoIPBox BRI Version 18.0.002 Page 111...

  • Page 112: Backbone Router With Direct Endpoint Signaling (H.323)

    The first VoIP peer’s IP address is 172.16.0.30 (VoIP profile iG1). H.323 signaling is used. Only compression G.729 and T.38 (fax) are used. Silence suppression is active. A maximum of 4 VoIP connections can be set up using this profile. VoIPBox BRI Version 18.0.002 Page 112...
  • Page 113 Backbone router with direct endpoint signaling (H.323), configuration in the route.cfg [System] ;To BRI Restrict40=tobri MapAlltobri=10 Restrict10=tovoip MapAlltovoip0=40iG1:0 MapAlltovoip1=40iG1:1 [Voip=iG1] VoipDirection=IO VoipPeerAddress=172.16.0.30 VoipIpMask=0xffffffff VoipSignalling=0 VoipCompression=g729 t38 VoipSilenceSuppression=Yes VoipMaxChan=4 VoipTxM=4 VoipIpLogging=yes [Voip=iG2] VoipDirection=IO VoipPeerAddress=172.16.0.40 VoipIpMask=0xffffffff VoipSignalling=0 VoipCompression=g711a VoipSilenceSuppression=No VoipMaxChan=4 VoipTxM=4 VoipIpLogging=yes VoIPBox BRI Version 18.0.002 Page 113...

  • Page 114: Intrastar

    IP connection and results in fallback to ISDN. An- other quality criterion is packet loss, whereby a fractionlost ratio of 10% in five seconds also results in fallback to ISDN. Bear in mind that silence suppression must be deactivated. VoIPBox BRI Version 18.0.002 Page 114...
  • Page 115 MapOut5=|40DF:0305<<25 MapOut6=|40DF:0306<<25 MapOut7=|40DF:0307<<25 MapOut8=|40DF:0308<<25 MapOut9=|40DF:0309<<25 Redirect340DF:=pl MapAllpl=9 MapIn0=100 MapIn1=101 MapIn2=102 MapIn3=103 MapIn4=104 MapIn5=105 MapIn6=106 MapIn7=107 MapIn8=108 MapIn9=109 [Voip:DF] VoipDirection=IO VoipPeerAddress=company_sub.de VoipIpMask=0xffffffff VoipCompression=g729 t38 VoipSilenceSuppression=No VoipSignalling=1 VoipMaxChan=8 VoipTxM=2 VoipT303=3 VoipIntrastar=Yes VoipBrokenDetectionTimeout=1000 VoipQualityCheck=FractionLost 5 10 10 VoIPBox BRI Version 18.0.002 Page 115...

  • Page 116: Backbone Router With Radius Management

    Backbone router with RADIUS management, configuration in the route.cfg [System] ;BRI Restrict40=tobri MapAlltobri=10 ;To VoIP MapAll?=40DF:? [Voip=DF] VoipDirection=IO VoipPeerAddress=192.168.0.10 VoipIpMask=0xffffffff VoipSignalling=0 VoipCompression=g729 t38 VoipSilenceSuppression=Yes VoipMaxChan=8 VoipTxM=4 VoipRadiusAuthenticate=rad VoipRadiusAccounting=rad [Radius=rad] Host=radiusserver.domain.com User=user Password=pwd Secret=secret OwnId=myself.domain.com ServiceType=1 RequestTimeout=5 VoIPBox BRI Version 18.0.002 Page 116...

  • Page 117: Voip Backup And Automatic Reactivation

    ASR2 value of over 30% for the last 30 calls is sent to IP ad- dress 172.16.0.80. When the ASR2 falls below 30%, profile iG2 is used. After one hour has passed, the connection quality at the original peer is automatically tested. If the connection cor- VoIPBox BRI Version 18.0.002 Page 117...
  • Page 118 VoIP backup and automatic reactivation, configuration in the route.cfg [Voip=iG1] VoipDirection=Out VoipPeerAddress=172.16.0.80 VoipIpMask=0xffffffff VoipSignalling=0 VoipCompression=g729 t38 VoipSilenceSuppression=Yes VoipMaxChan=8 VoipTxM=4 VoipQualityCheck=ASR2 30 30 3600 VoipOverflow=iG2 [Voip=iG2] VoipDirection=Out VoipPeerAddress=172.16.0.90 VoipIpMask=0xffffffff VoipSignalling=0 VoipCompression=g729 t38 VoipSilenceSuppression=Yes VoipMaxChan=8 VoipTxM=4 Figure 5.8 VoIP backup and automatic reactivation VoIPBox BRI Version 18.0.002 Page 118...

  • Page 119: System Maintenance And Software Update

    6 System maintenance and software update...

  • Page 120: Configuration Errors

    If functions were activated by key combinations from terminal devices you can identify these along with the service ID. Example 6.1 Protocol.log file 16.05.06-11:51:31,[990]Start STATUS - TELES.VoIPBOX V11.7a (007f) 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 16.05.06-12:12:06,Remote Control from IP 192.168.1.2 16.05.06-12:12:06,Remote Control: OK...
  • Page 121 System maintenance and soft- ware update Table 6.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- [999] Remote Control: mand.
  • Page 122 Internal error. config: evaluation errcode <num> Port-Specific Entries The <port> has been unblocked. This can occur via re- [<port>]Unblock Port mote access for all controller types or automatically via X Pro for mobile channels. VoIPBox BRI Version 18.0.002 Page 122...
  • Page 123 GatekeeperRequest was not answered. GK <name> !GCF Incoming VoIP call from specified IP address was reject- no profile for ipaddress ed due to no matching VoIP profile. Successful registration at SIP registrar. registrar <name>: registration done VoIPBox BRI Version 18.0.002 Page 123...
  • Page 124 Accounting request to specified Radius server failed timeout acnt <ip addr> due to timeout. Response authenticator from specified Radius server !rsp-auth <ip addr> was invalid (wrong secret/password?). Authentication denied by specified Radius server. !auth <ip addr> <num> VoIPBox BRI Version 18.0.002 Page 124...
  • Page 125 The FIREWALL was not loaded, please check the Configuration for mistakes Error in <dsl_interface> Connection failed. Please, connect a cable in the <ethernet> port Error in <dsl_interface>: Connection Failed. Please, revise your Username/Password configuration Error in <dsl_interface>: Connection Failed. Please, revise the DSL Modem VoIPBox BRI Version 18.0.002 Page 125...

  • Page 126: Software Update

    NOT restart or turn off the system! Make a note of the error message and the update steps that have been taken and contact TELES service. 1. To get the necessary software files for your system, you need to contact your local sales representative.
  • Page 127 These files form a unit and belong to the same software version. To avoid compatibility conflicts, check with TELES service before you update the software. An update of the following optional function modules occurs in the same way.

  • Page 128: Snmp Agent

    Table 6.3 Specific trap Error Code Definition Port registered/up Wrong PIN Unknown error, port restarted Port restart Layer 2 problem Layer 1 problem / port down VoIPBox BRI Version 18.0.002 Page 128...
  • Page 129 Calls rejected due to no user INTEGER 1.3.6.1.4.1.2170.1.2.1.1.11 Calls disconnected INTEGER 1.3.6.1.4.1.2170.1.2.1.1.12 Outgoing calls INTEGER 1.3.6.1.4.1.2170.1.2.1.1.13 Incoming calls INTEGER 1.3.6.1.4.1.2170.1.2.1.1.14 Channels in use more than 90 percent INTEGER 1.3.6.1.4.1.2170.1.2.1.1.15 Accumulated call duration INTEGER 1.3.6.1.4.1.2170.1.2.2.1.1 Number of Ethernet controller INTEGER VoIPBox BRI Version 18.0.002 Page 129...
  • Page 130 Table 6.5 Traps for IP interfaces Port Number Interface Ethernet 1 Ethernet 2 Loopback xppp= (if used) pppoe= (if used) If more than one pppoe<x> profile is configured, the number will also increase. VoIPBox BRI Version 18.0.002 Page 130...

  • Page 131: Dns Forwarder

    With this module, the system can function as a DNS server for the clients in the local network. The system in the local net- work sent the DNS query to the VoIPBox. The following software package must be installed: dnsmasg.tz2. VoIPBox BRI Version 18.0.002 Page 131...

  • Page 132: Ipupdate - Dyndns Client

    IP net- work, even if, for example, it is a common DSL connection with dynamic IP address allocation. Several providers support this service. The following software package must be installed: ipupdate.tz2. VoIPBox BRI Version 18.0.002 Page 132...
  • Page 133 60 seconds. Bear in mind that this setting may cause the provider to block the domain name, since multiple registrations in short intervals are often not allowed. You must clear this with your provider. VoIPBox BRI Version 18.0.002 Page 133...

  • Page 134: Trace

    →). Trace results presented here are for BRI and VoIP interfaces, and for the following services in various levels: Table 6.8 Trace options Option Definition Mail Output for all SMTP packets. NumberPortability Output of all packets for communication with the iMNP. VoIPBox BRI Version 18.0.002 Page 134...
  • Page 135 Offline - trace information is written to a file on the VoIPBox. VoIPBox systems create trace files when the TraceLog=file entry is present in the pabx.cfg. Traces can be activated via re- mote administration (GATE Manager or FTP). VoIPBox BRI Version 18.0.002 Page 135...
  • Page 136 C X Pro, ... ent options can be limited to error messages, debug messag- es, or detailed trace output. The Advanced field is for TELES support usage only. For an explanation of the different trace option please refer to Chapter 6.7 Trace on page 134...
  • Page 137 – DD = day – hh = hour – MM = month – mm = minute – YY = year – ss.ss = hundredths of seconds Traces appear in the following format: [<hh:mm:ss>] <module>[<port>]: <trace> VoIPBox BRI Version 18.0.002 Page 137...

  • Page 138: Isdn Trace Output

    TraceView.exe to translate offline trace out- put. The tool is available for download (see Chapter 3.2 on page 33 →). The GATE Manager’s trace window can also dis- play translated online traces. VoIPBox BRI Version 18.0.002 Page 138...

  • Page 139: Call Forwarding To Sip Trace Output

    The following arguments apply for each module: trclevel=[info; error; debug] Info messages allow the user to observe the progress of the translation process. Detailed information is available at the debug level. Errors (defualt) always appear. VoIPBox BRI Version 18.0.002 Page 139...

  • Page 140: Voip Trace Output

    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. Since they are displayed unabridged, no description is necessary. Information and in- VoIPBox BRI Version 18.0.002 Page 140...

  • Page 141: Interface Ip Network

    IP network and h225accept from <ip address> s <si> for calls coming out of the IP network. Table 6.11 H.323 session Trace Output Description Outgoing VoIP call connect to Incoming VoIP call accept from Peer's IP address <ip address> VoIPBox BRI Version 18.0.002 Page 141...
  • Page 142 The peer's IP address. <ip address> Table 6.13 ETS message types Hex Value Message Type Alerting Call Proceeding Progress Setup Connect Setup Acknowledge Release Complete Facility Notify Information Status VoIPBox BRI Version 18.0.002 Page 142...
  • Page 143 Optional alternative values for IP address port or a new destina- ALT:<ip address>:<port>, tion number for a facility message with the cause call forwarded. <DAD> Table 6.15 Compression codecs used Synonym Codec G.711Alaw64k G.711Ulaw64k G.7231 G.728 VoIPBox BRI Version 18.0.002 Page 143...
  • Page 144 Calls to the IP network 1 Trace Output Description Message type written out; if a decimal number appears here, it will <mt> be translated as per Table 6.13 →. Called party number. <num> Call reference. <cr> VoIPBox BRI Version 18.0.002 Page 144...

  • Page 145: Rtp/Rtcp Output

    1 appears when T.38 (fax) is used, otherwise 0. <fx> The codec used, as per Table 6.15. <comp> Multiplication factor for default frame size (20ms, 30 ms for G.723). <factor> VoIPBox BRI Version 18.0.002 Page 145...
  • Page 146 1 means an RTP-multiplex connection is used (default 0). agg=<bool> The following output shows the channel’s state in the com- pression chip during a startup or change of codec. a[<controller>]: <VoIPcodecChipType>OpenChannelConfiguration ch=<ch> rc=0 a[<controller>]: <VoIPcodecChipType>T38ChannelConfiguration ch=<ch> rc=0 a[<controller>]:<VoIPcodecChipType>ActivateRegularRtpChannelConfiguration ch=<ch> rc=0 VoIPBox BRI Version 18.0.002 Page 146...
  • Page 147 <num> SenderReport packet Packet requested by the driver Delay jitter [msec]. <ji> Round-trip local<->remote, round-trip delay [msec]. <rt> Fraction lost: Fraction of packets lost [8lsb]. <fl> Cumulative lost: number of lost packets [24lsb]. <cl> VoIPBox BRI Version 18.0.002 Page 147...
  • Page 148 Codec change for fax Trace Output Description Fax bypass flag: Voice, data bypass or fax relay Fax bypass Signal detected on decoder output (see Table 6.26) Signal detected on encoder input (see Table 6.26) VoIPBox BRI Version 18.0.002 Page 148...
  • Page 149 V.21 channel 1 (mark tone, 980 Hz) BELL_103_ANSWER_TONE Bell 103 answer tone, 2225 Hz FAX_DCN FAX-DCN (G.3 fax disconnect signal) Fax relay is activated for the corresponding channel: a[<controller>]: Ac49xActivateFaxRelayCommand(1) ch <ch> rc <cr> VoIPBox BRI Version 18.0.002 Page 149...
  • Page 150 CRP (command repeat) DCN (disconnect) Pre-message response Post-message response Post-message command VXX (receive illegal high-speed signal) TCF (training check function Fax image V.8 CI (calling indicator (reserved)) V.8 CM (calling menu) V.8 (joint menu) VoIPBox BRI Version 18.0.002 Page 150...
  • Page 151 The value is in integers and and may not exceed 50 ppm in the following ranges during fax trans- mission (T30TxState): 65535 – 65486 (-50ppm) 0 – 50 (+50ppm) VoIPBox BRI Version 18.0.002 Page 151...

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

    DAD<num> = called party number, OAD<num> = calling party <num> number. Value for OAD field element: <cc> 20 OAD network type provided 40 OAD with sending complete 80 OAD presentation restricted Internal ident for the call leg. <id> VoIPBox BRI Version 18.0.002 Page 152...
  • Page 153 <cr> ch <chan> isdncr <icr> Table 6.31 Received from PSTN 2 Trace Output Description Call reference. <cr> Media channel used for the internal protocol interface (DSS1). <chan> Call reference for the internal protocol interface (DSS1). <icr> VoIPBox BRI Version 18.0.002 Page 153...

  • Page 154: H.245 Messages

    ... OpenLogicalChannel cn=<cn> cpr=<comp> sessid=<sid> ctrl=<ip address>:<rtcp port> ... OpenLogicalChannelAck cn=<cn> sessid=<sid> media=<ip address>:<rtp port> Table 6.34 Logical channel parameters Trace Output Description H.245 channel number per H.225 connection. <cn> Session ID. <sid> VoIPBox BRI Version 18.0.002 Page 154...
  • Page 155 2 (Table 6.39) Command 3 (Table 6.40) Indication Depending on the system control message type, one of the following message IDs appear. Table 6.37 Message IDs for request message Message NonStandard MasterSlaveDetermination TerminalCapabilitySet OpenLogicalChannel CloseLogicalChannel VoIPBox BRI Version 18.0.002 Page 155...
  • Page 156 MultiplexEntrySend RequestMultiplexEntry RequestMode RoundTripDelayRequest MaintenanceLoopRequest CommunicationModeRequest ConferenceRequest MultilinkRequest LogicalChannelRateRequest Table 6.38 Message IDs for response message Message NonStandard MasterSlaveDeterminationAck MasterSlaveDeterminationReject TerminalCapabilitySetAck TerminalCapabilitySetReject OpenLogicalChannelAck OpenLogicalChannelReject CloseLogicalChannelAck RequestChannelCloseAck RequestChannelCloseReject MultiplexEntrySendAck MultiplexEntrySendReject RequestMultiplexEntryAck RequestMultiplexEntryReject RequestModeAck RequestModeReject RoundTripDelayResponse VoIPBox BRI Version 18.0.002 Page 156...
  • Page 157 LogicalChannelRateReject Table 6.39 Message IDs for command message Message NonStandard MaintenanceLoopOffCommand SendTerminalCapabilitySet EncryptionCommand FlowControlCommand EndSessionCommand MiscellaneousCommand CommunicationModeCommand ConferenceCommand h223MultiplexReconfiguration NewATMVCCommand MobileMultilinkReconfigurationCommand Table 6.40 Message IDs for indication message Message NonStandard FunctionNotUnderstood MasterSlaveDeterminationRelease TerminalCapabilitySetRelease OpenLogicalChannelConfirm VoIPBox BRI Version 18.0.002 Page 157...

  • Page 158: 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>). Here is the output syntax for gatekeeper discovery requests: H225 GatekeeperRequest to <ip addr> H225 GatekeeperConfirm <ip addr> VoIPBox BRI Version 18.0.002 Page 158...
  • Page 159 Here is the output syntax for call teardown requests: H225 GkDisengage cr <cr> to <ip addr> H225 DisengageConfirm <ip addr> Here is the output syntax for registration release requests: H225 UnregistrationRequest <ip addr> H225 GkUnregistrationConf to <ip addr> VoIPBox BRI Version 18.0.002 Page 159...
  • Page 160 Table 6.45 Gatekeeper reject reason Reject Reason resourceUnavailable terminalExcluded invalidRevision undefinedReason securityDenial genericDataReason neededFeatureNotSupported Table 6.46 Registration reject reason Reject Reason DiscoveryRequired InvalidRevision InvalidCallSignalAddress InvalidRASAddress DuplicateAlias InvalidTerminalType UndefinedReason TransportNotSupported TransportQOSNotSupported ResourceUnavailable InvalidAlias SecurityDenial RullRegistrationRequired AdditiveRegistrationNotSupported VoIPBox BRI Version 18.0.002 Page 160...
  • Page 161 Table 6.47 Admission reject reason Reject Reason CalledPartyNotRegistered InvalidPermission RequestDenied UndefinedReason CallerNotRegistered RouteCallToGatekeeper InvalidEndpointIdentifier ResourceUnavailable SecurityDenial QosControlNotSupported IncompleteAddress AliasesInconsistent RouteCallToSCN ExceedsCallCapacity CollectDestination CollectPIN GenericDataReason NeededFeatureNotSupported Table 6.48 Unknown Gatekeeper messages Message GatekeeperRequest GatekeeperConfirm GatekeeperReject VoIPBox BRI Version 18.0.002 Page 161...
  • Page 162 Unknown Gatekeeper messages (continued) Message RegistrationRequest RegistrationConfirm RegistrationReject UnregistrationRequest UnregistrationConfirm UnregistrationReject AdmissionRequest AdmissionConfirm AdmissionReject BandwidthRequest BandwidthConfirm BandwidthReject DisengageRequest DisengageConfirm DisengageReject LocationRequest LocationConfirm LocationReject InfoRequest InfoRequestResponse NonStandardMessage UnknownMessageResponse RequestInProgress ResourcesAvailableIndicate ResourcesAvailableConfirm InfoRequestAck InfoRequestNak ServiceControlIndication ServiceControlResponse VoIPBox BRI Version 18.0.002 Page 162...

  • Page 163: Enum Output

    H.323 call with FastStart" on page 164 →) Outgoing H.323 call with FastStart (please see "Outgoing H.323 call with FastStart" on page 165 →) Fax call (please see "Fax call" on page 166 →) VoIPBox BRI Version 18.0.002 Page 163...
  • Page 164 [15:04:18.03] a[04]: ac49x stop ch=0 [15:04:18.06] a[04]: ac49x ch 0 rtcpR 2 ji 221 rt 84 fl 0 in 5012 out 5510 [15:04:18.24] r[02]: 02 81 01 1e [15:04:18.28] r[02]: 00 81 26 1e 08 01 82 5a VoIPBox BRI Version 18.0.002 Page 164...
  • Page 165 [15:25:24.79] a[04]: ac49x stop ch=0 [15:25:24.83] a[04]: ac49x ch 0 rtcpR 2 ji 194 rt 36 fl 0 in 10116 out 8426 [15:25:24.92] r[02]: 02 81 01 26 [15:25:24.92] r[02]: 00 81 30 26 08 01 48 5a VoIPBox BRI Version 18.0.002 Page 165...
  • Page 166 [16:00:43.68] y[04]: h225 decode rc 0, q931 msg 62 (6), len 64 [16:00:43.68] y[04]: h225rcv facility h225cr 7 FS:0(-,0,0) TUNN:1 H245:0(0,0) [16:00:43.68] i[04]: h245rcv(1) cr 7 RequestModeAck [16:00:43.68] i[04]: h245snd(1) cr 7 CloseLogicalChannel cn=1 [16:00:43.68] i[04]: h245snd(1) cr 7 OpenLogicalChannel cn=1 cpr=G sessid=1 ctrl=172.20.0.200:29001 VoIPBox BRI Version 18.0.002 Page 166...

  • Page 167: Remote Output

    [16:01:33.22] r[02]: 00 81 60 36 08 01 01 5a 6.7.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 VoIPBox BRI Version 18.0.002 Page 167...

  • Page 168: Smtp Trace Output

    All other trace output appears in detail mode in ASCII and are also translated. 6.7.5 SMTP trace output This trace option provides output for communication with the mail server that occurs when status information or files are sent. VoIPBox BRI Version 18.0.002 Page 168...
  • Page 169 Content of the message’s body. <content> All other trace output appears in detail mode in ASCII and are also translated. Receiving e-mails and sending them as SMS messages The following output displays communication of an incoming SMTP connection: VoIPBox BRI Version 18.0.002 Page 169...
  • Page 170 The mail module now converts the e-mail message to the in- ternal format and then sent as SMS. Bulk mail (several recipi- ent entries for the same e-mail) appear as individual messages: VoIPBox BRI Version 18.0.002 Page 170...
  • Page 171 SMTP output: transmission error Trace Output Description <num> Current number of retries. The output in the subsequent communication with the mail server are identical to those described above in “Sending files or status information”. VoIPBox BRI Version 18.0.002 Page 171...

  • Page 172: Number Portability Trace Output

    The following output shows that the connection attempt failed: n[99]:np: connect to <ip addr> failed The following output shows a keep alive packet from the iMNP to keep the TCP session open: n[99]:np: recv <> VoIPBox BRI Version 18.0.002 Page 172...

  • Page 173: Dtmf Tone Trace Output

    <message type> <id> <call state> 0 Table 6.62 DTMF output: signaling messages Trace Output Description For setup acknowledge and connect. <message type> Send_d_connect For alert. send_alert_ind For disconnect send_disconnect VoIPBox BRI Version 18.0.002 Page 173...
  • Page 174 DTMF output: media channel designation 2 Trace Output Description Media channel confirmation <msg> Connect confirmation Media channel free confirmation The following output shows the output for negotiated DTMF tones: d[<ctrl>]: dtmf send_info_ind <id> <<dtmf tone>> VoIPBox BRI Version 18.0.002 Page 174...

  • Page 175: Signaling And Routing Features

    7 Signaling and routing features...

  • Page 176: Intrastar

    The type of service appears first on the right side of the equal sign, followed by the ISDN port to which the IntraSTAR setup will be sent. The following type of service values are possible: 0500 (BTX) 0700 (data) VoIPBox BRI Version 18.0.002 Page 176...

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

    (default 5). The call will be forwarded as soon as the specified number of digits has been dialed or a time-out limit has been reached. VoIPBox BRI Version 18.0.002 Page 177...

  • Page 178: Rejecting Data Calls And Specified Numbers

    & followed by the two-digit cause value (see ETS 300 102-1). MapAll<direct>=&<cause> A maximum of 5000 MapAll entries per time zone can be defined. For more than 5000 entries, please use the iMNP. VoIPBox BRI Version 18.0.002 Page 178...

  • Page 179: Whitelist Routing

    PBX at port 10 cannot make any international calls. All national calls are sent to the VoIP profile DF and all lo- cal calls are sent to the PSTN. Example 7.3 Whitelist routing Restrict1012346=int MapAllint00=&91 MapAllint0=40DF:0 MapAllint1=91 MapAllint9=90 VoIPBox BRI Version 18.0.002 Page 179...

  • Page 180: Rejecting Calls With Isdn Bearer Capability Data

    In the following example, two VoIP profiles are configured, so that all calls are routed, regardless of whether they are data calls or voice over IP calls. The first one is for outgoing voice VoIPBox BRI Version 18.0.002 Page 180...

  • Page 181: Clip And Clir

    Line Identification Restriction (CLIR). For example, all CLIP calls can be rejected, so that only calls that do not present the calling number or calls without a calling party number (e.g. an- alog) are transmitted through the VoIPBox. VoIPBox BRI Version 18.0.002 Page 181...

  • Page 182: Setting Clir

    The following example shows an appropriate configuration. With this entry, all calls beginning with 00491555 are sent to the port with the address 22 and the presentation of the num- ber is restricted. Example 7.7 Setting CLIR MapAll00491555=#2200491555 VoIPBox BRI Version 18.0.002 Page 182...

  • Page 183: Setting Clip

    In the following mapping command, the call number 015550123456 is changed to 015559876543 (MapAll...=9..): Example 7.9 Conversion of a call number MapAll015550123456=9015559876543 VoIPBox BRI Version 18.0.002 Page 183...

  • Page 184: Overwriting Oad

    Restrict<port><original OAD>=<OAD to be sent> 15 In the following example, the OAD 456 is displayed to the called person for calls that have been received via port 10. Example 7.11 Overwriting OAD Restrict10=456 15 VoIPBox BRI Version 18.0.002 Page 184...

  • Page 185: Setting Number Type In Oad/Dad

    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. VoIPBox BRI Version 18.0.002 Page 185...
  • Page 186 OAD will be changed from 4930 to 004930 as fol- lows. Example 7.15 Restrict 4 RestrictR4930=004930 15 Enter one of the four specific number types in the DAD as fol- lows: VoIPBox BRI Version 18.0.002 Page 186...

  • Page 187: Setting The Screening Indicator

    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 7.17 Restrict 5 Restrict10=v 15 VoIPBox BRI Version 18.0.002 Page 187...
  • Page 188 BRI controllers to VoIP appears in addition to the international flag from BRI to VoIP. A placeholder routing entry is used (bla or blu), in which the BRI ports are directly assigned to a map- VoIPBox BRI Version 18.0.002 Page 188...

  • Page 189: Setting A Default Oad

    When the destination number begins with 030, the call is sent through controller 10. Example 7.21 Setting default OAD 1 Restrict9=*12345 15 MapAll030=10030 Use the entry Restrict<port><oad>=<num> 15 if digits at the beginning of the OAD are the only ones to be restricted. VoIPBox BRI Version 18.0.002 Page 189...

  • Page 190: Setting Sending Complete Byte In Setup

    In the following example, all calls beginning with 0 are sent with a sending complete to controller 9. Example 7.23 Setting sending complete MapAll0=)90 Removing sending complete The following entry ensures that the Setup never includes a sending complete: MapAll<direct>=(<num> VoIPBox BRI Version 18.0.002 Page 190...

  • Page 191: Oad Screening

    SIP header’s P-Preferred- Identity field. The number received from the PBX is sent in the SIP header’s From field. Syntax Add to your pabx.cfg file the following parameter: CMSN<ctrl>=<default number>[,<number 1>,<number 2>,…, <number n>] VoIPBox BRI Version 18.0.002 Page 191...
  • Page 192 The CMSN parameter screens the calling party number re- ceived on Controller 01 from the PBX. If the received number is between 000 and 299, the SIP header’s P-Preferred-Identi- ty and From field both contain the number 03039928200. If VoIPBox BRI Version 18.0.002 Page 192...

  • Page 193: Miscellaneous Routing Methods

    Routing based on the length of the destination number 7.12.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> VoIPBox BRI Version 18.0.002 Page 193...

  • Page 194: Routing Calls Based On Existence Of Destination Number

    MapAllMMM<digits>=<dest><digits> In the following example, digit collection is activated for all calls that come into port 9. Calls with the destination number 2222 are sent to the VoIP controller with the profile DF and VoIPBox BRI Version 18.0.002 Page 194...

  • Page 195: Changing Cause Values

    (0x80-0x8f) can be mapped to a single cause value by enter- ing TranslateG0Cause=<cause>, whereby <cause> repre- sents a cause value in hexadecimal form between 00 and 7f (or 80 and ff in most significant bit-notation). VoIPBox BRI Version 18.0.002 Page 195...
  • Page 196 Use the following parameter to translate a cause from ISDN to a specific SIP response: SipCause<ISDN cause>=<SIP response> Repeat the entry to initiate an additional translation. VoIPBox BRI Version 18.0.002 Page 196...
  • Page 197 7 bit notation, alternatively 9F in hexadecimal 8 bit nota- tion translates to SIP response 404. Table 7.2 ISDN cause - SIP response and SIP response - ISDN cause (page 1 of 2) ISDN cause SIP response SIP response ISDN cause VoIPBox BRI Version 18.0.002 Page 197...
  • Page 198 ISDN cause - SIP response and SIP response - ISDN cause (page 2 of 2) ISDN cause SIP response SIP response ISDN cause All other cause values are translated to SIP response 500. All other SIP responses are translated to ISDN cause value 16. VoIPBox BRI Version 18.0.002 Page 198...

  • Page 199: 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:...

  • Page 200: Call Forking

    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 VoIPBox BRI Version 18.0.002 Page 200...
  • Page 201 In this example two mappings exist: calls to the destination number 543211234 are mapped to the port 10 and the new destination number 543211234. Calls to the destination num- ber 01721234554 are mapped to the port 20 and the new des- VoIPBox BRI Version 18.0.002 Page 201...
  • Page 202 GlobalIn param- eter. A match is found for calls to 10543211234 and calls to this number are sent to 543211234 and 01721234554 simul- taneously. Example 7.31 Call forking MapAll543211234=10543211234 MapAll01721234554=2001721234554 GlobalIn1=10543211234 GlobalOut1=543211234 01721234554 VoIPBox BRI Version 18.0.002 Page 202...

  • Page 203: Least Cost Routing

    8 Least cost routing...
  • Page 204 This manual contains information only on carrier selection. If you would like to configure any other variation, please contact TELES or refer to the TELES Infrastructure Systems Manual Version 4.5, Chapter 3. Calls are routed transparently for the PBX and its users.

  • Page 205: Carrier Selection

    To block undesired carrier selection prefixes use: MapAll<CarrierSelection>=&91;(Busy signal) Example 8.1 →, calls to international destinations are ter- minated through the VoIP interface. The profile names iG1 and iG2 in the routing entries refer to different VoIP carriers. VoIPBox BRI Version 18.0.002 Page 205...

  • Page 206: Alternative Routing Settings

    (e.g. the VoIP connection has been disrupted). Alternative routing ensures uninterrupted operation of the attached PBX. In such cases, connections are often made via the public network using the Redirect command: MapAll<num>=<port><num> Redirect3<port><num>=<placeholder> VoIPBox BRI Version 18.0.002 Page 206...

  • Page 207: Charge Models

    3.45). The charge impulse generation options can be set for each mapping by adding charge-specific arguments to the MapAll commands as shown below. The use of each variable is explained in Table 8.1 →. VoIPBox BRI Version 18.0.002 Page 207...
  • Page 208 For the internal Layer 3 protocols on C X BRIs, charges can be specified to the third decimal place (thousandth) using the /Value option VoIPBox BRI Version 18.0.002 Page 208...
  • Page 209 If the multiplication factor is set to 255, a “minute price” is used in place of the time variable. These charge models are explained under "Retroactive charge generation after initial toll-free period" page 211 →. VoIPBox BRI Version 18.0.002 Page 209...

  • Page 210: Generating Charges With The Voipbox

    Example 8.5 Generating charges 2 MapAll0172=9123450172 1.65 131/10 ;time=1.65, start=131, wait=10 New charge models can be implemented by taking advantage of the multiplication factor in conjunction with the time and start/wait variables. VoIPBox BRI Version 18.0.002 Page 210...
  • Page 211 1000) of a currency unit (€0.001 or ¹⁄ 10 of a cent) to each charge unit. If thousandths are defined, a maximum value of 65.535 is possible. If tenths are defined, a maximum value of 6553.5 is possible. VoIPBox BRI Version 18.0.002 Page 211...
  • Page 212 MapAll02=90101302 3.00 0/0*10 ; 3 seconds cost €0.01 (€0.20 / minute) MapAll09=90105009 2.00 0/0*3 ; 2 seconds cost €0.003 (€0.09 / minute) The “points” method allows for a more precise calculation of smaller intervals. VoIPBox BRI Version 18.0.002 Page 212...
  • Page 213 Example 8.12 Price per minute 5 ( route.cfg MapAll902=0101302 1.80 0/0*255 ; €0.18 / minute MapAll909=0105009 0.90 0/0*255 ; €0.09 / minute Example 8.13 Price per minute 5 ( pabx.cfg Controller01=10 NT DSS1 UNIT:€ VALUE:0.001 VoIPBox BRI Version 18.0.002 Page 213...

  • Page 214: Online Traffic Monitor

    9 Online traffic monitor...

  • Page 215: Calculating And Resetting Statistic Values And Counters

    15. if the configuration is to apply on the 15th of every month. If the configuration is to apply every day, do not set <day>. With every saving of the log file, the statistic values are reset and calculation starts again from zero. VoIPBox BRI Version 18.0.002 Page 215...
  • Page 216 The following example shows how the statistics appear in the file into which they are copied. Example 9.2 Statistics file 26.10.04-00:00:00,iGATE810000: Calls: 19351 (29716) - Minutes: 46647 - ASR1: 65.12% - ASR(ext): 65.12% - ASR(int): 65.30% - ACD: 144.63s VoIPBox BRI Version 18.0.002 Page 216...

  • Page 217: Additional Resetting Of Counters A-F

    In the following example, the system’s statistic values are saved at noon on the 15th of every month into the file asr.log. Example 9.4 StatisticTimeReset 2 StatisticTimeReset=/data/asr.log 12:00 15. Do not configure both StatisticTimeReset and StatisticTime together. VoIPBox BRI Version 18.0.002 Page 217...

  • Page 218: Resetting Statistic Counters

    Generating and retrieving CDRs Log=/boot/cdr.log failedlog=/boot/failed.log 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. VoIPBox BRI Version 18.0.002 Page 218...

  • Page 219: Call Log

    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. VoIPBox BRI Version 18.0.002 Page 219...
  • Page 220 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. You can ex- pand the subscriber configuration line with the keyword VoIPBox BRI Version 18.0.002 Page 220...
  • Page 221 The following entry shows the route.cfg configuration file changed according to the formula. Example 9.9 Activating peer data for VoIP calls 1 [Voip=Default] VoipDirection=IO VoipPeerAddress=192.168.0.2 VoipIpMask=0xffffffff VoipCompression=g729 g711a t38 VoipMaxChan=30 VoipSilenceSuppression=Yes VoipSignalling=0 VoipTxM=4 VoipIPLogging=Yes VoIPBox BRI Version 18.0.002 Page 221...

  • Page 222: Missed Calls List

    Each line represents an unaccepted incoming call with the fol- lowing information separated by commas: Table 9.3 Failed log entries Column Description Version Start time (format DD.MM.YY-hh.mm.ss) Source. The following format applies: [node number:automatically set in- ternal channel number] VoIPBox BRI Version 18.0.002 Page 222...
  • Page 223 22,15 F1,21.04.10- 09:43:37,[0001:01]101760,[0002:01]0177566,262024550067835,,,,0101,00,4,1,3892 2,19 F1,21.04.10- 12:45:17,[0001:01]101760,[0002:01]0177566,262024550067835,,,,0101,00,26,1,389 22,20 The reason the connection could not be established is speci- fied using DSS1 codes: 91 – (user busy) ff – call not answered (disconnected by calling party) VoIPBox BRI Version 18.0.002 Page 223...

  • Page 224: Sending Cdrs Via E-Mail

    [Mail] sec- tion of the pabx.cfg, as described in Chapter 4.2.2 →. The sender is given as cdr and the system’s name appears in the subject box. The text box contains the CDR information ac- VoIPBox BRI Version 18.0.002 Page 224...
  • Page 225 If you replace the first @ sign with an !, the present cdr.log will be sent whenecver a new one is generated. Example 9.17 Sending CDRs via e-mail 2 Log=/data/cdr.log daily 60 5 !bob@example.com VoIPBox BRI Version 18.0.002 Page 225...

  • Page 226: Two Stage Dialing/Callback Server Functionality

    10 Two stage dialing/ callback server functionality...
  • Page 227 To indicate that the number transmitted using DTMF tones is complete, the caller can press the # key. Otherwise, there is a default timer set to 5 seconds, after which DTMF transmission will automatically end. VoIPBox BRI Version 18.0.002 Page 227...

  • Page 228: Activating Dtmf Tone Recognition

    10.1 Activating DTMF tone recognition The VoIPBox BRI can recognize DTMF tones and use them to initiate calls. In the pabx.cfg, enter a virtual DTMF subscriber, as described in Table 4.15 on page 77. .
  • Page 229 Two stage dialing/callback serv- er functionality the G.711 format is available from TELES free of charge. It is included with the The announcement is defined in the Subscriber line using the following entry in the pabx.cfg file: DTMF[<sec>,/<dir>/<file>] <sec> refers to the maximum number of seconds after which the connection to the DTMF controller is teared down.

  • Page 230: Two Stage Dialing With Dtmf

    PIN before the actual call number: MapAllDLA<pin>=<port> In addition, the mapping to the DTMF port can be extended by the capital letters C to Z to send the digits to different ports: VoIPBox BRI Version 18.0.002 Page 230...
  • Page 231 The user calls a number to trigger callback to his calling num- ber (OAD). After the alert tone, the system or the user hangs up and the user is called back. When he takes the call, he is re- VoIPBox BRI Version 18.0.002 Page 231...
  • Page 232 Calls back the calling party’s number via the defined port. MapAllDTMF=<DTMFport>DTMF Maps to the port that is needed for recognizing DTMF tones. MapAllDLA=<port> Sends all digits that have been entered as DTMF to the speci- fied port. VoIPBox BRI Version 18.0.002 Page 232...
  • Page 233 Not possible for mobile ports. In this scenario, there is no need to adjust the MapAllDTMF=<DTMFport>DTMF command. You need to activate digit collection if the call goes to the mobile network or VoIP (using SIP). VoIPBox BRI Version 18.0.002 Page 233...

  • Page 234: Callback With Dtmf And Preconfigured Callback Number

    The user hangs up and is called back at the de- fined callback number. After the user has accepted the call, he must enter the destination number via DTMF. The connection is set up when he finishes dialing. VoIPBox BRI Version 18.0.002 Page 234...

  • Page 235: Callback To Oad With Predefined Destination Number

    (e.g. operator or corporate central office). Make the following entries in route.cfg: MapAll<number>=CALLB MapAllCB=<port> MapAllDTMF=<port><destination number> Different routings are possible by using the capital letters “C” to “Z”. VoIPBox BRI Version 18.0.002 Page 235...

  • Page 236: Callback With Pin And Preconfigured Callback Number

    He then hangs up. After he takes the callback, he can enter the destination number using DTMF tones. Make the following entries in route.cfg: MapAll<number>=<DTMFport>DTMF MapAllDLA<pin>=CALL<port><callback number> MapAllDTMF=<DTMFport>DTMF MapAllDLA=<port> VoIPBox BRI Version 18.0.002 Page 236...
  • Page 237 Example 10.11 Callback with PIN and preconfigured callback number 2 MAPAll987654=40DTMFC MapAllDLC456=CALL9004930987654 MapAllDTMF=40DTMF MapAllDLA=10 The user must enter a # following the PIN. Otherwise the callback to the predefined number will not take place. VoIPBox BRI Version 18.0.002 Page 237...

  • Page 238: Additional Voip Parameters

    11 Additional VoIP parameters...

  • Page 239: Signaling Parameters

    Defines the payload type for the RTP packets when the call is sent as a data call. De- fault 96. VoIPEarlyT38=<mode> Enter yes to enable T38 before the call has been connected. Enter no to enable T38 after the call has been connected. Default yes. VoIPBox BRI Version 18.0.002 Page 239...
  • Page 240 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. EXAMPLE: VoipOad=001 VoIPBox BRI Version 18.0.002 Page 240...
  • Page 241 Enter -\x\y\ to replace the digits x by the digits y. x must be at the beginning of the OAD. x and y can differ in length. In the following example, the digits 517 are replaced by the digits 00517. EXAMPLE: VoipOad=-517\00517\ VoIPBox BRI Version 18.0.002 Page 241...
  • Page 242 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 243 H.245 negotiation (default No). VoipRejectIncomingNonMatchingFaststart=<mode> Setup will be rejected if the RTP codecs offered for incoming H.323 call setup with Faststart elements do not match those configured in the parameter VoipCompres- sion. Default No. VoIPBox BRI Version 18.0.002 Page 243...
  • Page 244 Enter yes to send a response to a SIP REGISTER request for a user that has not been defined in a VoIP profile in the route.cfg file or to send a response to a SIP SUBSCRIBE request for an unknown event. Default no. VoIPBox BRI Version 18.0.002 Page 244...
  • Page 245 That means digit collection is no longer necessary in the routing when the digets come from ISDN/POTS with overlap sending. When this parameter is active, VoipPrack is automatically set to yes. Default is no. VoIPBox BRI Version 18.0.002 Page 245...
  • Page 246 RTP signaling will be forwarded from one leg to the next and RTP is not handled by the system. Default is no. VoipSessionExpires=<sec> SIP only. Enter the session timer used by the VoipRFC4028 parameter in seconds. De- fault is 0. VoIPBox BRI Version 18.0.002 Page 246...
  • Page 247 A separate contents block is created (using boundaries) or evaluated that contains the ISDN user to user info. Default is 0, which transports the ISDN user to user information in a SIP header field "User-to-User:", according to the recommen- dation in http://tools.ietf.org/html/draft-johnston-sipping-cc-uui-09. VoIPBox BRI Version 18.0.002 Page 247...

  • Page 248: Location Server Parameters

    130 and password test130. Authentication occurs with the procedure www. Example 11.1 Account creation MapAll130=40U1:130 [Voip:U1] VoipDirection=IO VoipIpMask=0x00000000 VoipOwnUser=130 VoipOwnPwd=test130 VoipExpires=300 VoipAuth=www VoipCompression=g711a g711u g729 g729a g729b g729ab VoipSilenceSuppression=no VoipSignalling=1 VoipMaxChan=8 VoipTxM=2 VoipDtmfTransport=0 VoipRFC2833PayloadType=101 VoipMediaWaitForConnect=Tone VoIPBox BRI Version 18.0.002 Page 248...

  • Page 249: Routing Parameters

    Enter Yes to facilitate direct use of an xDSL or dial-up connection if the corresponding profile is defined. Default is No. VoipUseStun=<mode> Enter yes (default yes) to use the STUN values for the VoIP profile. VoIPBox BRI Version 18.0.002 Page 249...

  • Page 250: Quality Parameters

    VoIP profile. For a description of IntraSTAR, see Chapter 7.1 →. For an ex- ample, see Chapter 5.7 →. VoipCallGroup=<name> All outgoing VoIP calls for VoIP profiles with the same VoipCallGroup name are dis- tributed cyclically to these profiles. VoIPBox BRI Version 18.0.002 Page 250...
  • Page 251 32 is 0 dB. VoipIntrastar=<mode> Enter Yes to activate the IntraSTAR feature. When the IP connection results in poor quality, an ISDN call is sent to the peer and the voice data is automatically transmitted via ISDN. VoIPBox BRI Version 18.0.002 Page 251...
  • Page 252 This parameter changes the default interval for PCM codecs (G.711, G.726). That means the VoipTxm factor is muliplied using this interval: 0 = 10ms (default)) 1 = 5 ms 2 = 10 ms 3 = 20 ms VoIPBox BRI Version 18.0.002 Page 252...
  • Page 253 RTP packets. The DSCP is the first six bits in the TOS octet. NOTE: VoipUseIpStack must be 0 (default). VoipSilenceSuppression=<mode> Activates silence suppression (see Table 4.21). VoipSuppressCNG=<mode> Enter On to suppress comfort noise generation. Default is Off. Requires VoipSilence- Suppression=On. VoIPBox BRI Version 18.0.002 Page 253...
  • Page 254 Enter yes (default) to send the RoundTripDelayRequest message every 10 seconds (necessary for long calls with firewalls using TCP aging). VoipVoiceVolume=<num> The volume of VoIP calls coming from the Ethernet. The range is 0-63. The default val- ue of 32 is 0 dB. VoIPBox BRI Version 18.0.002 Page 254...

  • Page 255: 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. VoIPBox BRI Version 18.0.002 Page 255...

  • Page 256: Fax/Modem Parameters

    Additional VoIP parameters This feature is possible with a TELES peer and requires the fol- lowing entries in the VoIP profile: Table 11.8 Customized parameters: VoIP compression VoIP Compression Parameters VoipAggOwnDataPort=<port> VoipAggOwnDataPort=29500 Enter the own port number used for aggregated packets. Default: 29500.
  • Page 257 Enter Yes to switch to T38 although the B party does not signalize T38. (default Yes). VoipT38ErrorCorrectionMode=<int> Sets the error-correction mode: 0 = Redundancy (default) 1 = Forward error correction VoipT38ImageDataRedundancy=<int> Defines the redundancy level for fax content: 0 = Disable (default) 1-3 = Sets level VoIPBox BRI Version 18.0.002 Page 257...

  • Page 258: Dtmf Parameters

    If VoipDtmfTransport=3 is set and the peer does not support DTMF transmission ac- cording to RFC 2833, the following settings apply: 2 = automatic fallback to inband 0 = automatic fallback to signaling messages (default) VoIPBox BRI Version 18.0.002 Page 258...

  • Page 259: Call Forwarding Parameters

    101. 11.8 Call forwarding parameters The following table contains the parameters required for ISDN to SIP. The variable <type> refers to the call-forwarding type, and includes the following options: CFU (unconditional) CFB (busy) VoIPBox BRI Version 18.0.002 Page 259...
  • Page 260 Must include the configured keyword “MSN” which refers to the number to which incoming calls are forwarded (e.g. “CFU to MSN”). RETVAL_<type>StatusNoDiv=<string> LEX display string for status query when call forwarding is inactive. VoIPBox BRI Version 18.0.002 Page 260...

  • Page 261: 12 Troubleshooting

    12 Troubleshooting...

  • Page 262: No Connection To The System

    IP address settings cause that behavior (please refer to Chapter 12.1.3 →). Firewall issues cause that behavior (please refer to Chapter 12.1.4 →). NAT / PAT settings cause the problem (please refer to Chapter 12.1.4 →). VoIPBox BRI Version 18.0.002 Page 262...

  • Page 263: System Does Not Start Correctly

    Check whether you have access to the system using FTP. If you cannot access your VoIPBox, the operating system is no longer accessible. In that case you need to contact your service partner for help. VoIPBox BRI Version 18.0.002 Page 263...

  • Page 264: Web Interface Is Not Accessible

    12.1.2 Web interface is not accessible Your VoIPBox can be accessed through a web interface which requires installation in addition to the mandatory system files. Mismatches between system version and the version of VoIPBox BRI Version 18.0.002 Page 264...
  • Page 265 Chapter 6.3 Software update →. If the problem persists, check if port 80 is blocked by your firewall. For detecting firewall problems, please see Chapter 12.1.4 Firewall issues and NAT / PAT settings →. VoIPBox BRI Version 18.0.002 Page 265...

  • Page 266: Ip Address Settings

    VoIPBox. Network address translation (NAT) or port ad- dress translation (PAT) issues can also cause connection prob- lems. Reasons The configuration of your firewall blocks access to your system. NAT / PAT settings block access to your system. VoIPBox BRI Version 18.0.002 Page 266...

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

    12.1.5 ISDN dial-in number missing or wrong In systems with a BRI / PRI interface, ISDN access can be im- paired due to faulty or missing configurations of dial-in num- bers. VoIPBox BRI Version 18.0.002 Page 267...
  • Page 268 Make sure that your ISDN dial-in number is not used for any other data routings by taking the same steps as above: change the mapping to MapAll?=BBB DATA, trace the routing attempt and adjust the mapping ac- cording to your findings. VoIPBox BRI Version 18.0.002 Page 268...

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

    Example 12.1 PRI controller with CRC4 and DF Controller00=9 TES2M DSS1 CRC4 ;PRI port to DTAG with CRC4 on Controller01=10 NTS2M DSS1 DF ;PRI port to PBX with CRC4 off VoIPBox BRI Version 18.0.002 Page 269...

  • Page 270: No Calls Are Possible

    (please refer Chapter 12.2.2 →). The call arrives on the gateway, is routed to the right des- tination address, but is rejected elsewhere (please refer Chapter 12.2.3 →). VoIPBox BRI Version 18.0.002 Page 270...

  • Page 271: Call Does Not Arrive On The Gateway

    DNS port has been explicitly enabled in the firewall set- tings if all udp ports are blocked. First enable the DNS port, then block all udp ports. Check that the ports have the correct numbers. VoIPBox BRI Version 18.0.002 Page 271...
  • Page 272 (H.323) profiles, which you configure in the route.cfg file. If a VoIP call does not arrive on the gateway, this might be due to incorrect or missing registrar or gatekeeper profiles. To look up the registration state of your gate- VoIPBox BRI Version 18.0.002 Page 272...
  • Page 273 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. Access your system with GATE Manager and go to port status. VoIPBox BRI Version 18.0.002 Page 273...

  • Page 274: Call Is Rejected Or Not Routed To Destination

    Calls from and to VoIP: A technical prefix is causing the problem in the route.cfg’s MapAll parameter. Symptoms The call arrives on the gateway. The gateway refuses to route the call or it routes the call, but not to the right destination address. VoIPBox BRI Version 18.0.002 Page 274...
  • Page 275 VoIP: Missing or incorrect VoIP profiles cause problems with incoming or outgoing VoIP calls. The gateway receives the call but refuses to route it. For an explanation of the configuration of VoIP profiles please read Chapter 4.3.2 VoIP Profiles →. VoIPBox BRI Version 18.0.002 Page 275...
  • Page 276 IP 195.4.13.14. There is only one VoIP profile for incoming VoIP calls in the gateway’s route.cfg file. The VoIP profile’s VoipPeerAddress parameter is 195.4.13.0. parameter contains value VoipIPMask 0xfffffff8 which translates into the subnet mask VoIPBox BRI Version 18.0.002 Page 276...
  • Page 277 VoIP carrier who requires a prefix and is sent else- where, the called number (DAD) arrives on the gateway including the technical prefix. That prefix needs to be re- moved in the MapAll parameter. If a call comes in with- VoIPBox BRI Version 18.0.002 Page 277...

  • Page 278: Call Is Rejected Elsewhere

    Solution Mobile: The CLIR configuration needs to be removed from the routing settings if CLIR is not allowed, or it needs to be activat- ed by the mobile operator where it is allowed. VoIPBox BRI Version 18.0.002 Page 278...

  • Page 279: Software Update Problems

    Solution If you cannot reach the system at all via FTP or GATE Manager, this is because the operating system is no longer accessible. You need to contact your service part- ner for help. VoIPBox BRI Version 18.0.002 Page 279...
  • Page 280 FTP client’s command line inter- preter and selecting restart. This option depends on your FTP client’s functionality. For a description commands, please refer Chapter 3.5 FTP Commands →. – Check whether the software upload was successful. VoIPBox BRI Version 18.0.002 Page 280...

Table of Contents