TELES VoIP Box DSL Series, VoIP Box DSL 2, VoIP Box DSL 4, VoIP Box BRI Series, VoIPBox BRI 2 Reference Manual
...
VoIPBox DSL
VoIPBox BRI
Reference Manual
Software version 21.0
VoIPBox DSL / VoIPBox BRI
Reference Manual
TELES AG | HEADQUARTERS
Ernst-Reuter-Platz 8
10587 Berlin
GERMANY
Phone +49 30 399 28-066
Fax +49 30 399 28-051
E-mail sales@teles.com
http www.teles.com
Software version: 21.0 Revised: May 20, 2015 009
© Copyright 2015 TELES AG Informationstechnologien. All rights reserved.
®
TELES
, IntraSTAR®, Intra*®, CELLX®, and iSWITCH® are registered trademarks of TELES AG Informationstechnologien.
All other trademarks used are the property of their respective owners.
The supplied hardware/software systems are protected by copyright and can be used solely by their lawful owners.
All text and figures in this publication have been compiled with great attention to detail. Nonetheless, inaccuracies
and typographical errors cannot be entirely avoided. TELES AG Informationstechnologien provides this document 'as
is' without warranty of any kind, expressed or implied. TELES AG Informationstechnologien reserves the right to make
changes in product design or specifications without notice.
Table of contents
Table of contents
Preface ......................................................................................... 11
About this manual ...................................................................... 13
1 Safety and security precautions...............................................15
1.1 Safety Measures.............................................................................16
1.2 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 .........................................................................18
1.3 Jacks .................................................................................................18
1.4 EMC Protection ...............................................................................19
1.5 System Security ..............................................................................19
1.5.1 Servicing the VoIPBox .................................................................... 20
1.5.2 Protecting the Operating System.................................................20
1.6 CDR Files.......................................................................................... 21
1.7 Network Security............................................................................21
2 Overview ......................................................................................23
2.1 Features........................................................................................... 24
2.2 Implementation scenarios ............................................................26
VoIPBox BRI / VoIPBox DSL – version 21.0.009 Page 3
Table of contents
3 VoIPBox installation ................................................................... 28
3.1 Checklist .......................................................................................... 29
3.2 Package Contents...........................................................................29
3.3 VoIPBox Hardware Description ....................................................30
3.4 Installation Requirements.............................................................31
3.4.1 ISDN Wiring..................................................................................... 31
3.4.2 Ethernet Wiring ..............................................................................32
3.4.3 DSL wiring (optional)......................................................................33
3.5 Preparing for Installation ..............................................................33
3.6 Hardware Connection ...................................................................35
3.7 LED Functionality............................................................................35
3.8 GATE Manager................................................................................36
3.9 Transfer the config file with the GATE Manager to the PC........ 37
3.10 Activate the DSL connection .........................................................38
3.11 Activate PPPoE connection over an Eth interface ......................40
3.11.1 Changing the IP settings................................................................41
3.12 Changing the IP settings................................................................43
3.12.1 Change the IP settings on VoIPBox DSL ......................................43
3.12.2 Change the IP settings on VoIPBox BRI .......................................44
VoIPBox BRI / VoIPBox DSL – version 21.0.009 Page 4
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
4 Configuration files ...................................................................... 52
4.1 Configuration file ip.cfg .................................................................54
4.1.1 System section configuration .......................................................55
4.1.2 Ethernet interface configuration..................................................56
4.1.3 GUI settings..................................................................................... 56
4.1.4 DSL configuration...........................................................................57
4.1.5 Firewall configuration....................................................................57
4.1.6 PPPoE Configuration...................................................................... 58
4.1.7 DHCP and DNSmasq settings .......................................................59
4.2 Configuration File pabx.cfg ...........................................................61
4.2.1 System Settings ..............................................................................61
4.2.1.1 VoIPBox DSL / VoIPBox BRI name................................................61
4.2.1.2 Log Files...........................................................................................61
4.2.1.3 DNS and NTP settings....................................................................63
4.2.1.4 Controller settings..........................................................................66
4.2.1.5 Subscriber settings.........................................................................68
4.2.2 SMTP-Client Configuration............................................................69
4.2.3 Night Configuration .......................................................................71
VoIPBox BRI / VoIPBox DSL – version 21.0.009 Page 5
Table of contents
4.3 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 ................................................................................86
5 Additional VoIP parameters ......................................................88
5.1 Signaling parameters..................................................................... 89
5.2 STUN server parameter.................................................................97
5.3 Set up the VoIPBox DSL / VoIPBox BRI as Registrar...................98
5.4 Routing parameters.....................................................................100
5.5 Quality parameters ......................................................................101
5.6 Call forwarding parameters........................................................106
5.7 Interworking parameter ..............................................................107
5.8 Compression parameters ...........................................................108
5.9 Fax/modem parameters .............................................................109
5.9.1 Fax settings for T.38.....................................................................110
5.10 DTMF parameters ........................................................................111
5.11 Announcements...........................................................................112
VoIPBox BRI / VoIPBox DSL – version 21.0.009 Page 6
Table of contents
6 Signaling and routing features ............................................... 114
6.1 Digit collection (enblock/overlap receiving)..............................115
6.2 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
6.3 CLIP and CLIR................................................................................119
6.3.1 Routing CLIP and CLIR calls.........................................................119
6.3.2 Setting CLIR...................................................................................120
6.3.3 Setting CLIP...................................................................................121
6.4 Conversion of call numbers ........................................................121
6.5 Overwriting OAD ..........................................................................122
6.6 Setting number type in OAD/DAD..............................................123
6.7 Setting the screening indicator...................................................125
6.8 Setting a default OAD ..................................................................127
6.9 Setting sending complete byte in setup....................................128
6.10 OAD screening..............................................................................129
VoIPBox BRI / VoIPBox DSL – version 21.0.009 Page 7
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
7 System maintenance and software update ..........................141
7.1 Configuration errors ....................................................................142
7.2 Status and error messages .........................................................142
7.3 ipupdate - DynDNS client............................................................147
7.4 Trace ..............................................................................................149
7.4.1 ISDN trace output.........................................................................153
7.4.2 Call forwarding to SIP trace output............................................154
7.4.3 VoIP trace output .........................................................................155
7.4.3.1 Interface IP network.....................................................................156
7.4.3.2 RTP/RTCP output ..........................................................................160
7.4.3.3 Internal protocol interface (to ISDN, POTS, mobile) ................165
7.4.3.4 H.245 messages ...........................................................................166
7.4.3.5 RAS (Registration, Admission, Status)........................................171
7.4.3.6 ENUM output ................................................................................175
7.4.4 Remote output .............................................................................176
7.4.5 DTMF tone trace output ..............................................................177
VoIPBox BRI / VoIPBox DSL – version 21.0.009 Page 8
Table of contents
7.5 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
8 Online traffic monitor ..............................................................181
8.1 Calculating and resetting statistic values, resetting counters 182
8.1.1 Calculation and resetting of statistic values .............................182
8.1.2 Additional resetting of counters A-F..........................................184
8.1.3 Resetting statistic counters.........................................................185
8.2 Generating and retrieving CDRs.................................................185
8.2.1 Call log ...........................................................................................187
8.2.2 Missed calls list .............................................................................190
8.3 Sending CDRs via e-mail ..............................................................191
9 Troubleshooting........................................................................ 193
9.1 No connection to the system......................................................194
9.1.1 System does not start correctly..................................................195
9.1.2 Web interface is not accessible ..................................................196
9.1.3 IP address settings .......................................................................198
9.1.4 Firewall issues and NAT / PAT settings ......................................198
9.1.5 ISDN dial-in number missing or wrong .....................................199
9.1.6 ISDN port not loaded correctly / not active ..............................201
VoIPBox BRI / VoIPBox DSL – version 21.0.009 Page 9
Table of contents
9.2 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
9.3 Software update problems .........................................................209
Appendix A: Default config files ...............................................................212
A.1 pabx.cfg.........................................................................................213
A.2 ip.cfg ..............................................................................................216
A.3 route.cfg ........................................................................................218
List of examples ........................................................................220
List of tables ..............................................................................223
List of figures.............................................................................226
VoIPBox BRI / VoIPBox DSL – version 21.0.009 Page 10
Preface
Preface
In this guide
This guide is set up to guide you through the step-by-step installation of your VoIPBox DSL / VoIPBox BRI so that you can
follow it through from the front to the back.
This guide is written for a technician who is familiar with telecom, computer and internet technology.
Make sure you familiarize yourself thoroughly with the safety
and security precautions detailed in 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 – items from the GUI menu.
Code – file names, variables and constants in
configuration files or commands in body text.
"Conventions" on page 11 → – cross-references can be
accessed in the PDF files by a single mouse click.
Configuration data or extracts are written in single-
column tables with a gray background.
# configuration text
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 11
Preface
!
!
!
Safety symbols
The following symbols are used to indicate important information and to describe levels of possible danger.
Note
Useful information with no safety implications.
Attention
Information that must be adhered to as it is necessary to ensure that the system functions correctly and to avoid material damage.
Warning
Danger. Could cause personal injury or damage to the system.
Dangerous voltage
Could cause injury by high voltage and/or damage the system.
Electrostatic discharge
Components at risk of discharge must be grounded before
being touched.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 12
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.
Chapter 3 – VoIPBox installation
contains information on basic installation and configuration
of your VoIPBox. Follow the easy instructions to set up your
VoIPBox in a matter of minutes. Implementation of individual
scenarios require adjustments to the appropriate interfaces.
Tips for basic settings are described here. Links to relevant
chapters are provided for more specific configuration
changes.
Chapter 4 – Configuration files
describes the basic setup and the most commonly used
entries for the configuration files. Configuration of VoIPBoxes
is managed in the following three files: ip.cfg, pabc.cfg, and
route.cfg.
Chapter 5 – Additional VoIP parameters
contains additional configuration entries to fine-tune
communication with the VoIP peer.
Chapter 6 – Signaling and routing features
contains some special configuration examples for different
call routing and configuration cases.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 13
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. It also explains
activation, resetting and analysis of the data.
Chapter 9 – Troubleshooting
discusses problems that you may encounter when operating
your VoIPBox and offers solutions. 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.
Appendix Appendix A – Default config files
contains the config files available on the VoIPBox DSL /
VoIPBox BRI after delivery.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 14
1 Safety and security
precautions
1 Safety and security precautions
!
This chapter contains the safety and security precautions.
In addition this chapter describes important system informations 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.
To avoid personal injury or damage to the system, please
follow all safety instructions before you begin working on
your gateway. VoIPBoxes are CE certified and fulfill all relevant security requirements. The manufacturer assumes no
liability for consequential damages or for damages resulting from unauthorized changes.
1.1 Safety Measures
Danger of electric shock - the power supplies run on 230 V. Do
not open the VoIPBox or its power supply.
Make sure to install the VoIPBox near the power source and
that the power source is easily accessible.
Bear in mind that telephone and WAN lines are also energized
and can cause electric shocks.
Be sure to respect country-specific regulations, standards or
guidelines for accident prevention.
1.2 Power Supply
The included power supply is to be used exclusively for operation of your VoIPBox.
Make sure you read this chapter thoroughly and save the
instructions for future reference. Use only the power supply included in the package contents of your VoIPBox.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 16
1 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
| Weight: 115g
| Tested and certified as per EN60950-1
1.2.2 Symbols
The symbols on the power supply have the following meanings:
---
; 1.25A
Table 1.1 Power Supply Symbols
Symbol Meaning
Certified to conform with European norms.
Protective insulation provided.
For indoor use only.
Not for public disposal. Make sure you dispose of the power supply properly.
Indicates the output polarity of the power supply.
1.2.3 Instructions for Use
Plug the power supply directly into the outlet. The power supply provides safety-low voltage with limited capacity for your
VoIPBox.
Use only the power supply included in the package contents of your VoIPBox.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 17
1 Safety and security precautions
The devices are designed for constant use in dry, indoor locations. However, we recommend that you unplug them if you
do not intend to use them for an extended amount of time.
Make sure the power outlet is easily accessible at all times.
1.2.4 Safety Precautions
Make sure you follow these safety precautions:
| Electrical devices may not be used by individuals who are
not aware of the dangers of electricity and/or the
incorrect use thereof.
| 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.
| Unplug the device if you do not intend to use it for an
extended amount of time.
| Hold the device by its housing when you unplug it. Wall
outlets can become mechanically overloaded; do not
pull on the cord.
| 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).
1.3 Jacks
The jacks on the VoIPBox have fulfilled the requirements of
the SELV safety standard.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 18
1 Safety and security precautions
!
!
1.4 EMC Protection
Use shielded cables.
Do not remove any housing components. They provide EMC
protection.
1.5 System Security
This section describes all points crucial to the VoIPBox’s system security.
The VoIPBox’s location must support normal operation according to EN ETS 300 386. Be sure to select the location with
the following conditions in mind:
Location: Make sure you install the system in a clean, dry,
dust-free location. If possible, use an air-conditioned site.
The site must be free of strong electrical or magnetic
fields, which cause disrupted signals and, in extreme cases, system failure.
Temperature:
The site must maintain a temperature between 0 and
35°C. Be sure to guard against temperature fluctuations.
Resulting condensation can cause short circuiting. The humidity level may not exceed 80%.
To avoid overheating the system, make sure the site provides adequate ventilation.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 19
1 Safety and security precautions
Power:
The site must contain a central emergency switch for the entire power source.
The site’s fuses must be calculated to provide adequate system security. The electrical facilities must comply with applicable regulations.
The operating voltage and frequency may not exceed or fall
below what is stated on the label.
1.5.1 Servicing the VoIPBox
Regular servicing ensures that your VoIPBox runs troublefree. 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.
1.5.2 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
to your configuration!
Download the log files and delete them from the VoIPBox on
a regular basis to ensure VoIPBox’s reliability. All files with the
extension *.log can be deleted. Do not delete or change any
files necessary for system operation. Use the GATE Manager
to check storage space and/or delete files. For more information consult the GATE Manager Reference manual. To save files
before deleting them, use the Receive File option in GATE
Manager.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 20
1 Safety and security precautions
!
1.6 CDR Files
Call Detail Records are intended for analysis of the VoIPBox’s
activity only. They are not designed to be used for billing purposes, as it may occur that the times they record are not exact.
Inaccuracies in the generation of CDRs may occur for active connections if traffic is flowing on the system while
modifications in configuration or routing files are activated.
1.7 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,
to avoid unwanted security breaches and resulting system
malfunctions, you must take the following steps to secure
your VoIPBox if you connect it to the Internet:
| Use the installed firewall.
| Access to the VoIPBox via GATE Manager must be
password protected. Do not use obvious passwords
(anything from sesame to your mother-in-laws maiden
name). Bear in mind: the password that is easiest to
remember is also likely to be easiest to crack.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 21
1 Safety and security precautions
For operation and remote administration of your VoIPBox
open only the following ports only when the indicated services are used:
Table 1.2 Default Ports Used for Specific Services
Service Protocol Port
FTP TCP 21 (default, can be set)
Telnet (for TELES debug access only)
SMTP TCP 25 (default, can be set)
DNS forward UDP 53
HTTP TCP 80 (default, can be set)
NTP UDP 123
H.225 registration, admission, status
H.225 signaling TCP 1720 (default, can be set)
Radius UDP 1812 (default, can be set)
Radius accounting UDP 1813 (default, can be set)
GATE Manager TCP 4445 (default, can be set)
SIP signaling UDP / TCP 5060 (default, can be set)
RTP UDP 29000-29120 (default, can be set)
NMS TCP 4444
TCP 23 (default, can be set)
UDP 1719 (default, can be set)
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 22
2 Overview
2Overview
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 connection of ISDN service equipment with a voice over IP (VoIP)
network. It converts line-based transmission on the ISDN side
to packet-based transmission in the IP network and vice versa. Incoming traffic arrives at one VoIPBox, which routes the
calls accordingly, depending on the call’s destination and attributes. The VoIPBox is available with two, four, or eight BRI
ports.
The VoIPBox BRI Family includes the following variations:
| VoIP Box DSL 2
| VoIP Box DSL 4
| VoIP Box DSL 8
| VoIPBox BRI 2
| VoIPBox BRI 4
| VoIPBox BRI 8
2.1 Features
VoIP
| up to 16 media channels
| H.323 v.4 / SIP v.2 signaling (RFC 3261), operating in
parallel
| Various audio codecs: G.711, G.729
| Fax: T.38 fallback to G.711
| Data: clear channel (RFC 4040)
| ENUM client
| Echo cancellation G.168–2000
| Silence suppression, comfort noise generation, voice
activity detection
| Support for multiple gatekeepers and multiple registrars
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 24
2Overview
| 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
NT
| DSS1 (Q.931, national variants),Q.SIG-BC;
| PP or PMP
DSL
| ADSL2+/VDSL Modem
| PPP or DHCP
| VLAN or virtual path of ATM cell support
TR-069
LCR Engine
| Multiple VoIP-carrier logins
| Multiple ISDN routing methods
| Multilevel alternative routing
| dialed digit manipulation
| time-dependent call routing
| Two-stage dialing
General
| User-friendly GUI with easy and advanced mode
configuration settings
| Ringtone generation
| Configurable ToS/DivServ
| AOC generation
| Integrated DSL router (PPPoE)
| Integrated mail client capable of SMTP authentication
| E-mail messages can trigger calls and play attached
announcements
| Automatic test call
| Redial function
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 25
2Overview
| Autodial function
2.2 Implementation scenarios
These are the most commonly used implementation scenarios.
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 connection to different VoIP destinations. Fax transmission occurs
via T.38 or fallback to G.711a.
Figure 2.1 VoIP gateway
VoIPBox BRI
Internet
ISDN
PBX
DSL/LAN
Local Exchange
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 26
2Overview
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.
PBX
PSTN
VoIPBox BRI
DSL/LAN
Internet
Figure 2.2 Least cost rou ter 2nd generation
VoIP
Carrier
Local Exchange
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 27
3 VoIPBox installation
3 VoIPBox installation
This chapter contains information on basic installation and
configuration of your VoIPBox. Follow the easy instructions
to set up your VoIPBox in a matter of minutes. Implementation of individual scenarios require adjustments to the appropriate interfaces. Tips for basic settings are described
here. Links to relevant chapters are provided for more specific configuration changes.
3.1 Checklist
This checklist provides step-by-step installation instructions.
1. Check the package contents
2. Connect the BRI lines to the PBX and/or the PSTN
3. Transfer the config files with the GATE Manager to the
local computer.
4. Adjust the configuration to your needs with the help of
Quickstart (IP address and BRI / VoIP configuration).
5. Activate the configuration with the GATE Manager.
6. Secure the LAN connection
3.2 Package Contents
Your VoIPBox package contains the following components:
| 1 VoIPBox
| 1 power supply
Check the contents to make sure everything is complete and
undamaged. Immediately report any visible transport damages to customer service. If damage exists, do not attempt operation 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
3 VoIPBox installation
3.3 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 channels. The following pages describe installation of the VoIPBox.
ISDN 2 ISDN 1 ETH2 ETH1 dsl 12 V-
Figure 3.1 VoIPBox BRI with 2 BRI and DSL: front and rear view
ISDN ports Ethernet DSL power
ISDN 8 ISDN 7 ISDN 6 ISDN 4ISDN 5 ISDN 3 ISDN 2 ISDN 1 ETH2 ETH1 12 V-
only available on
VoIPBox BRI 8
Figure 3.2 VoIPBox BRI with 8 BRI and DSL: front and rear view
only available on
VoIPBox BRI 8/4
dsl
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 30
3 VoIPBox installation
!
3.4 Installation Requirements
Before installing your VoIPBox, make sure you have the following 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. Only the ISDN1 port can be configured as a TE port.
Port ISDN1 can be configured as NT to connect a telephone or
PBX.
An attached NTBA or PBX must be connected to the ISDN1
TE outlet if it is to provide the clock for the VoIPBox!
Figure 3.3 → shows the standard pin assignment for TE and
NT modes. You must change the pin assignment if it differs on
the connected equipment.
Figure 3.3 ISDN Wiring Scheme
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 31
3 VoIPBox installation
3.4.2 Ethernet Wiring
To connect the VoIPBox PRI’s Ethernet port ETH1 to an Ethernet switch in your local network.
RJ-45 Ethernet
connector
Front view
5
432
678
Figure 3.4 Ethernet connector PIN assignment
1
Table 3.1 → list the PIN assignement for the Ehternet.
Table 3.1 Pin assignment of the Ethernet connector
PIN Description 10baseT 100baseT 1000baseT
1 Transmit Data+ or BiDirectional TX+ TX+ BI_DA+
2 Transmit Data- or BiDirectional TX- TX- BI_DA-
3 Receive Data+ or BiDirectional RX+ RX+ BI_DB+
4 Not connected or BiDirectional n/c n/c BI_DC+
5 Not connected or BiDirectional n/c n/c BI_DC-
6 Receive Data- or BiDirectional RX- RX- BI_DB-
7 Not connected or BiDirectional n/c n/c BI_DD+
8 Not connected or BiDirectional n/c n/c BI_DD-
Table 3.2 → describes the LEDs on the Ethernet ports.
1
8
Table 3.2 LEDs on the Eth ports
LED Description
Left LED Blinking/on amber operating as a Gigabit connection (1000 Mbps).
Blinking/on green operating as 100-Mbit connection. Blinking –
Right LED On amber operating as a Gigabit connection (1000 Mbps).
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 32
Blinking – activity on this port.
activity on this port.
3 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.
1 - NC
2 - Tip or Ring
3 - Ring or Tip
4 - NC
Figure 3.5 DSL connector PIN assignment
RJ-11 connector
432 1
3.5 Preparing for Installation
There is a difference between VoIPBox DSL and VoIPBox BRI:
a) The VoIP Box DSL comes with an active DHCP server.
b) The VoIP Box BRI has no DHCP server running.
Preparing for installation on VoIPBox DSL
The VoIPBox DSL comes with a fix IP address (192.168.1.2/24)
and an active DHCP server with the address range
192.168.1.50 – 192.168.1.90. The VoIPBox DSL works as a de-
fault gateway in the network. In many cases, no changes need
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 33
3 VoIPBox installation
!
to be made to the IP settings of the VoIPBox DSL. Before
changing the IP configuration, please have the following information available:
| new IP address and netmask in your local network for
the VoIPBox DSL
| new default gateway for VoIPBox DSL
Bear in mind that the preconfigured VoIPBox’s default IP
address is 192.168.1.2. If this IP address is already being
used in your local network, you must change the configuration before you connect it to your local network. This
can be done by connecting the VoIPBox DSL directly to
your computer via Ethernet cable.
Start the computer after connecting to the VoIPBox DSL so
that a DHCP address is assigned to the computer, and follow the working steps described in Chapter 3.14 on
page 49 →.
Preparing for installation on VoIPBox BRI
The VoIPBox BRI comes with a fix IP address (192.168.1.2/24).
Use the Quickstart program to set the IP address and the default 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.
3. Extract the archives and install the Quickstart and the
GATE Manager.
4. Follow the installation instructions.
5. Connect the VoIPBox BRI by Ethernet with a PC. Use
any of the two Ethernet interfaces of the VoIPBox BRI.
6. Start the VoIPBox BRI by connecting the power supply.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 34
3 VoIPBox installation
7. Open Quickstart on the PC. It automatically finds your
VoIPBox BRI. Double click the icon to open the configuration window. Adjust the IP settings and click the finish button. The VoIPBox BRI will be reconfigured with
your new IP address and will then re-start.
3.6 Hardware Connection
Do the following steps:
| Connect your computer to the local network.
| Connect the VoIPBox to the local network
| Connect the VoIPBox to your PBX and/or the PSTN
according to the required port configuration.
| Connect the VoIPBox to the power supply.
3.7 LED Functionality
Each VoIPBox has the following status LEDs:
Table 3.3 VoIPBox LEDs
LED Name Description
Red Power On: Power on.
Green 1 DSL Off: inactive
Green 2 VoIP Off: inactive
Green 3 ISDN Off: inactive
Off: Power off.
On: online
slow blink not synced
fast blink synced but not online
On: registered
blink: register failed
On: idle (MFE)
blink: active call
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 35
3 VoIPBox installation
3.8 GATE Manager
This chapter gives an overview to the GATE Manager. The
GATE Manager will be used to transfer and activate configuration files for the VoIPBox DSL / VoIPBox BRI. In addition the
GATE Manager allows to monitor the VoIPBox DSL /
VoIPBox BRI.
The GATE Manager administration and maintenance software
offers a broad range of functions. The GATE Manager is user
friendly and can be customized to suit your needs.
Figure 3.6 GATE Manager
The following maintenance functions are possible:
| Display system information and network element status.
| Retrieve and display configuration files.
| Restart network elements.
| Use of a trace option for checking functions and fault
diagnosis. Option to use an external tool, e.g. to display
and break down trace data.
| Update the system software (firmware) and
configuration tables.
| Retrieve CDRs (Call Detail Records).
| Display the current connections (status).
| Display statistical information for network elements and
interfaces.
| Display the status of the interfaces.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 36
3 VoIPBox installation
To complete the configuration, retrieve and edit the config
files as described in Chapter 4 on page 52 →. You have to use
GATE Manager version 20.0 or later. For a detailed description
of installation and implementation of the GATE Manager,
please refer to the GATE Manager and Utilities Programs Manual.
3.9 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.
4. Follow the installation instructions.
5. Start the GATE Manager.
6. Add the VoIPBox DSL / VoIPBox BRI as new system to
the default group:
– Select New System form the context menu (right
mouse click to the main system table).
– Insert in the dialog Edit System a System name to
identify the VoIPBox DSL / VoIPBox BRI in the system
table.
– Insert the IP address (default is 192.168.1.2) as Re-
mote number and confirm with OK.
7. Use the green Connect button from the tool bar to
connect to the VoIPBox DSL / VoIPBox BRI. No password is needed. Confirm the dialog with OK.
8. After connect select Directory in the left navigation
bar.
9. The upper left rectangle shows the config files. There
are three config files ip.cfg, pabx.cfg and route.cfg.
10.Select one config-file after another and make a backup
of these file using the context menu Copy On System.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 37
3 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
ip.cfg. Table 3.4 → assist you to place the right configuration
according to the DSL Line settings you receive from your provider.
Table 3.4 DSL settings for line access and login
Method Variant Settings
DSL line access VLAN access Set the VLAN tag as value of the Vlan= parameter
within the [dsl] section.
ATM a cce ss Set the virtual channel identifier (vci) as value
of the Vci= parameter within [dsl] section
Set the virtual path identifier (vpi) as Vpi= pa-
rameter within [dsl] section
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 38
3 VoIPBox installation
Table 3.4 DSL settings for line access and login (continued)
Method Variant Settings
DSL logon
Method
DSL disconnect
time
Logon Data required
No Logon Data/
IP settings
– Most of the internet service provider (ISP) force a
Enter DSL User Name as User= parameter
within [dsl] section
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-
tion (see Example 3.1 on page 39 →).
To obtain IP Settings from a dhcp server config-
ure dslif=dhcp within [dsl] section (see Exam-
ple 3.2 on page 40 →).
If you are required from Provider to configure
static IP address, set it in dslif= within [dsl] section (see Example 3.3 on page 40 →).
disconnect of the DSL line every 24 hours. This can
happen in an inconvenient moment. In order to
preampt this disconnection you can arrange this
action in a certain time by configuring the parameter: DslPPPDisconnectTime
Enter the time in the format hh:mm to the variable:
DslPPPDisconnectTime
For example: DslPPPDisconnectTime=03:15
By default no disconnect time is set.
Example 3.1 Common DSL settings for VLAN/ATM access and PPP login
[dsl]
User="Heinz"
Pwd="123123123"
Vlan=7
Vpi=1
Vci=32
dslif=ppp
[dslppp]
lock
nodeflate
novj
novjccomp
nodetach
usepeerdns
defaultroute
lcp-echo-interval 10
lcp-echo-failure 10
debug
logfile /tmp/pppd.log
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 39
3 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. Ensure that this interface is not used as the
Ethernet interface for Local Area Network communication.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 40
3 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
nodetach
usepeerdns
defaultroute
lcp-echo-interval 10
lcp-echo-failure 10
debug
logfile /tmp/pppd.log
3.11.1 Changing the IP settings
To change the IP settings the following information is needed:
| IP address and netmask for the [eth1]/[eth2] interfaces.
Eth1 is configured to 192.168.1.2/24 after delivery. It is
possible to configure both ports as an Ethernet bridge
[br0].
| If needed, set up a default gateway for the VoIPBox DSL
/ VoIPBox BRI.
Example 3.7 → shows the required sections for the IP config-
uration of the VoIPBox DSL / VoIPBox BRI.
Example 3.5 Main sections of the ip.cfg
[system] # n
Hostname=TAG98313460700000
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 41
3 VoIPBox installation
Example 3.5 Main sections of the ip.cfg (continued)
[eth1] # o
IpAddress=192.168.1.2 netmask 255.255.255.0
[eth2] # p
IpAddress=192.168.178.2 netmask 255.255.255.0
[iptables] # q
# 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
iptables -A block -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A block -m state --state NEW -i ! ppp0 -j ACCEPT
iptables -A block -m limit -j LOG
iptables -A block -j DROP
iptables -A INPUT -j block
iptables -A FORWARD -j block
The hostname n is set here to the serial number
“TAG98313460700000”. The IP address of Eth1 is set to
192.168.1.2/24 o. That is the default. The IP address of Eth2
is 192.168.178.2/24 (p).
The firewall is active. All incoming traffic except traffic on the
GATE Manager port 4445 is blocked. Outgoing traffic is allowed q.
Example 3.8 → shows a part from the ip.cfg with a bridge con-
figuration on Eth1 and Eth2. Both IP interfaces are running in
bridge mode. The IP address is set in the [br0] section in the
same manner as shown before.
Example 3.6 Different IP settings for every interface configured in the ip.cfg
[system]
DefaultGw=192.168.1.1
[br0]
IpAddress=192.168.1.2 netmask 255.255.255.0
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 42
3 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.
3.12.1 Change the IP settings on VoIPBox DSL
The VoIPBox DSL comes with active DHCP server and a fix IP
address (192.168.1.2/24) for both IP ports that works as a
bridge. The VoIPBox DSL works as default gateway in the locale network. The default configuration is shown in Example
3.7 → and compleate in Example A.5 on page 216 →.
As shown in Example 3.7 → the required sections for the IP
configuration of the VoIPBox DSL are the sections [br0] (for
the bridge mode) or [eth1] and [eth2] (for the single Ethernet
interfaces) and for the NAT settings in the first line of the
[iptables] section. For more details please see Chapter 4.1
Configuration file ip.cfg on page 54 →.
Example 3.7 Main sections of the ip.cfg
[br0]
IpAddress=192.168.1.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
iptables -A block -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A block -m state --state NEW -i ! ppp0 -j ACCEPT
iptables -A block -m limit -j LOG
iptables -A block -j DROP
iptables -A INPUT -j block
iptables -A FORWARD -j block
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 43
3 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.
Example 3.8 Different IP settings for every interface configured in the ip.cfg
[system]
DefaultGw=172.20.0.78
[Eth1]
IpAddress=172.20.27.224 netmask 255.255.0.0
[Eth2]
IpAddress=192.168.1.24 netmask 255.255.255.0
Set the NameServer in the pabx.cfg.
3.13 Remote access security
This chapter describes the settings for the remote access and
Web GUI passwords.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 44
3 VoIPBox installation
3.13.1 Graphical User Interface
Remote access is possible via the Web GUI. Even users with little experience can easily configure standard system settings
with this interface. Simply open a browser and enter the system’s IP address in the address bar.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 45
3 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 status and statistics can be retrieved.
The passwords are saved in the ip.cfg in encrypted form:
PwdAdmin=<crypt>
PwdUser=<crypt>
Example 3.9 → shows an ip.cfg entry.
Example 3.9 ip.cfg web GUI section
[httpd]
PwdUser=dc1556f3cebe9e7d5da7e956f1c398c2
PwdAdmin=b4e3d44911fb4ad0d3af9fd2b4db94e4
Md5=yes
CmdExpected=0
UndoLastChanges=1
Never edit these entries. Use the GUI to change the password.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 46
3 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:
System Overview Overview of system information, versions, status and statistics.
Commands Here you can activate a configuration, restart the system, reset to
LAN Settings: Settings for the Ethernet interfaces, default
gateway, DNS, IP routing, and NTP.
WAN Settings: DSL access settings.
Network Services: Shows the active services and allows to
change the password.
Port Settings: Settings for ISDN and VoIP controller.
Expert mode: Schows parts of the configuration files.
the default settings, or restore the last session configuration.
User Data Here you can change the user passwords and the language for the
HTTP interface.
All of the user interface’s pages contain Help buttons and
links to the online help, which provides a detailed description
of all of the individual configuration settings.
3.13.2 Setting a Password for Remote Access
The system comes with no password set for GATE Manager
access. If you do not define a password, access to the system
via GATE Manager takes place without one, and FTP access
takes place with the default password tcs-ag.
The password is set in the pabx.cfg with the parameter
RemotePassword=<password>. The value <password> con-
tains the encrypted text of the password.
Define the encrypted text with the GATE Manager as follows:
1. Open the GATE Manager,
2. Select the menu Edit | Encode Password…
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 47
3 VoIPBox installation
3. Enter the password in clear text in the Encode Password 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 →.
Example 3.10 pabx.cfg with an encoded password
RemotePassword=vDLGTEBIZUNDMR@fNP54B
Transfer the pabx.cfg to the system using the GATE Manager.
After the file has been transferred, reboot the system. The
system can only be accessed with the correct password. Don’t
forget it!
3.13.3 Adjust the firewall settings
In the firewall on the PPP interface is open for incoming TCP
traffic on port 4445 with the following rule
iptables -A INPUT -s 0.0.0.0/0 -p tcp --dport 4445 -i ppp0 -j ACCEPT
Adjust the rule so that the access is possible only from a limited IP range. To do so replace 0.0.0.0/0 e.g. with 192.4.13.0/
24.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 48
3 VoIPBox installation
3.14 Activate the VoIP interface
The VoIP configuration is stored in the file route.cfg. The following 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.
Table 3.6 → shows the configuration for the VoIP interface.
The configuration is divided into three parts:
1. The call routing: The default mapping sends all calls
from the VoIP ports to the BRI ports and all calls from
the BRI ports to the VoIP carrier. This works with the
default settings. This configuration point is divided into
the routing for incoming and for outgoing calls:
– Call routing for calls from the VoIP carrier to the VoIP-
Box DSL / VoIPBox BRI (n). The mapping in the comment before is useful for some PBX. This mapping
(routing) removes the area and/or country code from
the destination address.
– Call routing for calls from the VoIPBox DSL / VoIPBox
BRI to the VoIP carrier. In this example only one VoIP
carrier (PeerA) is used. All calls will be sent to PeerA
(o). The mapping in the comment before is useful for
some VoIP carrier. This mapping adds the area/country code before the called number.
2. The SIP profile: For every SIP carrier one SIP profile is
needed. The SIP profile contains a name (in Table
3.6 → PeerA p), username (VoipUser), password
(VoipPwd), and IP address (VoipPeerAddress,
VoipIpMask) of the remote SIP server. In addition the
SIP profile defines a link to a registrar profile
(VoipRegistrar).
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 49
3 VoIPBox installation
3. The Registrar: In the default configuration contains the
registrar section as a comment, because the registration will be repeated regularly and if the VoIPBox DSL /
VoIPBox BRI is not in use this will create not needed IP
traffic (q). The registrar makes the VoIPBox DSL / VoIPBox BRI for other SIP user visible and reachable.
Remove the comments and fill in the settings
described below:
Table 3.6 VoIP configuration in a route.cfg
[System]
DTMFWaitDial=3
;; ----------------------------------------------------------------------;; incoming calls
;; ----------------------------------------------------------------------;;
Restrict40=Ix
;; to remove country and/or area code from DAD of incoming calls remove '#'
;; from entrys below and adjust country and area codes (in example are
;; 030 - area code of Berlin and 0049 - country code of Germany)
#MapAllIx004930=$Iy
#MapAllIx030=$Iy
; Mapping for incoming calls n
MapAllIx=$Iy
MapAllIy=10s
;; ----------------------------------------------------------------------;; outgoing calls
;; ----------------------------------------------------------------------;;
;; to modify DAD to international format remove '#' from entrys below and
;; adjust country and area codes
#MapAll00=40PeerA:00
#MapAll0=40PeerA:030
#MapAll.=40PeerA:004930?
;; routing for outgoing calls (must be deleted if the routing above activated) o
MapAll.=40PeerA:?
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 50
3 VoIPBox installation
Table 3.6 VoIP configuration in a route.cfg (continued)
;;; SIP profile p
;;; --------------------[Voip:PeerA]
VoipDirection=IO
VoipPeerAddress= ;; ip address:port e.g. 1.2.3.4:5060
VoipIpMask=0xffffffff
Voi pS ign al lin g= 1
Voi pU ser =
Voi pP wd=
;VoipOwnAddress= ; optional
VoipRegistrar=rega
Voi pM axC ha n=6 0
VoipCompression=g711a g711u g729a g729b
#[Registrar:rega] # q
#RegId= ;; ip address:port e.g. 1.2.3.4:5060
#RegOwnId=user@1.2.3.4
#RegUser=
#RegPwd=
#RegSignalling=1
;*END CONFIG*
– RegId contains the IP or hostname of the registrar
followed by a colon on the port number.
– RegOwnId typically contains your host name or tele-
phone number followed by an @ sign and a domain
name or IP address.
– Set user name and password as RegUser and
RegPwd.
For a test call do the following steps:
| If not done, connect the VoIPBox DSL / VoIPBox BRI with
the PBX, IP network/DSL and power supply (see
Chapter 3.6 on page 35 →).
| Check the registration state on VoIP Statistics with the
GATE Manager. If the registration is not successful (not
registered, timeout) check and correct the settings and
activate the new configuration.
| Send a call from a connected telefone to a public
number.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 51
4 Configuration files
4 Configuration files
!
This chapter describes the basic setup and the most commonly used entries for the configuration files. Configuration of VoIPBoxes is managed in the following three files:
ip.cfg, pabc.cfg, and route.cfg.
Table 4.1 Configuration Files
File Function
ip.cfg This file is for the basic configuration of the Ethernet interfaces.
pabx.cfg This file is for system-specific and port-specific settings.
route.cfg This file is for routing and VoIP entries.
Changing configuration data may lead to malfunctions
and/or misrouting, as well as possible consequential damage. 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.
The default configuration with the IP address 192.168.1.2 is
active after delivery. You can configure the system using the
GATE Manager.
Make sure you secure the system with new passwords following configuration and remember to memorize the passwords
(see Chapter 3.13 on page 44 →)!
These configuration files contain all system-specific settings
and are used when the system starts. Comments included in
these files must begin with a semicolon. Comments can also
be placed at the end of the code line. Configuration files must
end with an empty line.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 53
4 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 sections in these files are:
Table 4.2 Required Configuration File Sections
Section File Function
[System] pabx.cfg
[Night<num>]
EXAMPLE: [Night1]
[Night2]
[br0] ip.cfg This section contains the IP configuration
route.cfg
ip.cfg
pabx.cfg
route.cfg
4.1 Configuration file ip.cfg
The basic settings for the two Ethernet interfaces are entered
here. Generally, these settings are entered once and then left
unchanged.
This file contains the following sections, which must appear in
the order given:
Table 4.3 Sections in the ip.cfg File
This section contains the system’s basic
settings.
This section contains time dependent entries that only apply for limited times.
for the Ethernet bridge of both Ethernet interfaces.
Section Function
[System] (required) This section contains entries that define the default gateway
and/or special routing entries.
[br0] (required) The Ethernet controller section define the Ethernet bridge.
[eth1] and [eth2]
(instead of [br0])
[httpd] This section contains the port and access password parame-
[dsl] (optional) These section contains settings for DSL interface.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 54
The Ethernet controller sections – to define every Ethernet interface separately. These sections can be used as an alternative to the bridge section
ters for the graphical user interface.
[br0].
4 Configuration files
Table 4.3 Sections in the ip.cfg File (continued)
Section Function
[dslppp] These section contains settings for the PPP interface used for
the DSL connection.
[iptables] This section contains settings for NAT and the system’s fire-
wall.
[dnsmasq] This section enables the DHCP server the appropriate settings.
4.1.1 System section configuration
The [System] section contains entries that define the default
gateway and/or special routing entries. To define the standard 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
If you must route specific net ranges to gateways other than
what is defined in the default route, make the following entries in the [System] section:
Route= -net <target ip> / <net mask> gw <ip gateway> [dev <device>]
Example 4.2 Routing specific net ranges
[System]
DefaultGw=192.168.1.254
Route= -net 10.0.0.0/12 gw 192.168.1.1 dev br0
If only certain routes apply, leave the line DefaultGw empty.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 55
4 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
Decide whether to use a bridge with both interfaces [br0],
or each interface separately ([eth1] and [eth2]) with different IP settings. It is not possible to mix a bridge and single
interface configuration.
4.1.3 GUI settings
The following parameter is used to change the GUI port in the
section [httpd] (default 80):
GuiPort=<num>
Bear in mind that the passwords for different access levels are
not set here. The encrypted passwords are stored here and
can only be changed via GUI (see Chapter 3.13.1 Graphical
User Interface →).
Example 4.4 GUI configuration
[httpd]
GuiPort=80
PwdUser=dc1556f3cebe9e7d5da7e956f1c398c2
PwdAdmin=b4e3d44911fb4ad0d3af9fd2b4db94e4
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 56
4 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 (Demilitarized zone (computing)) the firewall must be activated in the
ip.cfg (see Chapter 4.1.5 on page 57 →).
The firewall used on VoIPBox DSL / VoIPBox BRI is iptables.
The documentation is freely available on the internet. Only
the table filter is used in the ip.cfg. Outgoing traffic is allowed
unless otherwise specified. Incoming and forwarded traffic is
dropped unless otherwise specified.
The options used in Example 4.5 → are listed in Table 4.4 →.
Table 4.4 iptable options used in Example 4.5 →
Option Description
-P INPUT DROP Policy for the chain (INPUT, OUTPUT, FORWARD) used if no other
filter rule is defined. The action used in this case is DROP. For the
other rules, use the action ACCEPT.
-A INPUT Policy added to the INPUT chain.
-d <destination IP> This policy is only true for packets with the given destination IP address.
-s <source IP> This policy is only true for packets from the given source IP address.
This option is not used in the example but if the source is known
use this option for more security.
-i <interface> This policy is only true for packages used the given IP interface. (lo
– local loop interface, ppp0 – the first IP interface)
-p <protocol> This policy is only true for the given IP protocol (UDP, TCP).
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 57
4 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.
Example 4.5 → shows the firewall rules activated in the ip.cfg.
Example 4.5 Basic firewall settings for ppp0
[iptables]
iptables -P INPUT DROP
iptables -P FORWARD DROP
iptables -P OUTPUT ACCEPT
iptables -A INPUT -d 127.0.0.1 -j ACCEPT
iptables -A INPUT -p icmp --icmp-type echo-request -j ACCEPT
iptables -A INPUT -p icmp --icmp-type echo-reply -j ACCEPT
; iptables -A INPUT -p tcp -i ppp0 --dport ftp -j ACCEPT
; iptables -A INPUT -p tcp -i ppp0 --dport http -j ACCEPT
; iptables -A INPUT -p tcp -i ppp0 --dport smtp -j ACCEPT
iptables -A INPUT -p udp -i ppp0 --dport 53 -j ACCEPT ; DNS forward
iptables -A INPUT -p udp -i ppp0 --dport ntp -j ACCEPT
; iptables -A INPUT -p udp -i ppp0 --dport snmp -j ACCEPT
iptables -A INPUT -p udp -i ppp0 --dport 1719 -j ACCEPT ; H.225 (UDP)
iptables -A INPUT -p tcp -i ppp0 --dport 1720 -j ACCEPT ; H.225 (TCP)
iptables -A INPUT -p tcp -i ppp0 --dport 4445 -j ACCEPT ; GATE Manager
iptables -A INPUT -p udp -i ppp0 --dport 5060 -j ACCEPT ; SIP
iptables -A INPUT -p udp -i ppp0 --dport 29000-29120 -j ACCEPT ; RTP
With these rules, outgoing traffic is allowed, incoming traffic is
only possible in the local interfaces. The following protocols
are allowed for incoming traffic: icmp (ping), DNS forwarding,
NTP, H.225, SIP, and RTP (used for VoIP), and GATE Manager.
4.1.6 PPPoE Configuration
The protocol Point-to-Point over Ethernet is used for DSL
communication. This means the system can connect directly
to the carrier network and terminate VoIP traffic directly.
Changes in this section are not needed. All necessary informa-
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 58
4 Configuration files
tion for setup of the PPPoE connection is defined in the
[dslppp] section. The following example shows a [dslppp]
section.
[dslppp]
lock
nodeflate
novj
novjccomp
nodetach
usepeerdns
defaultroute
lcp-echo-interval 10
lcp-echo-failure 10
debug
logfile /tmp/pppd.log
4.1.7 DHCP and DNSmasq settings
The DHCP (Dynamic Host Configuration Protocol) server provides a mechanism for allocation of an IP address and default
gateway, to client hosts. Dnsmasq is an easy to configure DNS
forwarder. It is designed to provide DNS to a small network.
The section [dnsmasq] contains a list of parameters and settings for the 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
4 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-priv Bogus private reverse lookups. All reverse lookups for pri-
vate IP ranges (i.e. 192.168.x.x, etc) which are not found in
/etc/hosts or the DHCP leases file are answered with "no
such domain" rather than being forwarded upstream.
filterwin2k Later versions of windows make periodic DNS requests
which don't get sensible answers from the public DNS and
can cause problems by triggering dial-on-demand links.
This flag turns on an option to filter such requests. The requests blocked are for records of types SOA and SRV, and
type ANY where the requested name has underscores, to
catch LDAP requests.
user=<username> Specify the userid <username> to which dnsmasq will
change after startup. Dnsmasq must normally be started
as root, but it will drop root privileges after startup by
changing id to another user. Normally this user is "nobody" but that can be over-ridden with this switch.
interface=<if> Defines the network interface the DHCP and DNSmasq
server is bind on.
cache-size=<cache> Set the size of dnsmasq's cache. The default is 150 names.
Setting the cache size to zero disables caching.
domain=<domain> Defines the domain name <domain> used in the network.
dhcp-range=<f>,<l>,<d> The DHCP network range is defined by the first <f> and last
<l> address in the range. Client assignment begins with the
last address. Duration <d> gives the time in hours the assigned address to the DHCP client is valid.
resolve-file=<file> This file contains the name server assigned to the DHCP
clients.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 60
4 Configuration files
4.2 Configuration File pabx.cfg
The pabx.cfg is divided into the [System] section and the optional [Night<num>], [Mail] and [Snmpd] sections.
4.2.1 System Settings
The [System] section is divided into several categories to ensure clarity:
| VoIPBox DSL / VoIPBox BRI name
| Log files
| Global Settings
| Controllers
| Subscribers
4.2.1.1 VoIPBox DSL / VoIPBox BRI name
The variable PabxName defines the name of the VoIPBox DSL
/ VoIPBox BRI in the GATE Manager.
4.2.1.2 Log Files
CDRs, unconnected calls, system events, trace output and statistics can be saved into files. The following entries are necessary to generate log files:
Table 4.6 pabx.cfg: Log File Entries
Entry Description
ActionLog=/boot/protocol.log System events
Log=/boot/cdr.log CDR entries
Failedlog=/boot/failed.log Unconnected calls
TraceLog=/boot/trace.log System trace
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 61
4 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.
A dash (-) appears in place of information that is to be ignored.
Table 4.7 pabx.cfg: Log Parameters
Log=/boot/<file> <saved> <size> <count>
<file> The name of the log file is generated as follows:
[file]yymmdd[0-9|A-Z].log.
<saved> Refers to the frequency with which the file is saved. The following op-
tions are possible:
halfdaily Every day at 11:59 and 23:59
daily Every day at 23:59
weekly Sunday at 23:59
monthly The last day of the month at 23:59
<size> Regardless of the value entered in <day>, the file will be saved when
the <size> has been reached (in kB).
NOTE: We recommend a file size of a multiple of 60kB.
<count> Refers to the number of files that will be saved in the system (between
5 and 35) before the first file is overwritten. This setting is useful not
only for limited file size, but also for files that store events. Normally
size can be limited for these files, e.g. 5 files o f 1MB each. If the fifth
file is full, the first one will automatically be overwritten.
Bear in mind that file size will be unlimited if no parameters are defined.
Please remember to keep track of how much memory is
available on the system using the command df.
In the following entry, the file cdr.log is renamed every day.
Up to 35 CDR files will be saved on the system.
Example 4.7 cdr.log renamed daily
Log=/boot/cdr.log daily - 35
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 62
4 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. Up to five log files will be saved on
the system.
Example 4.9 protocol.log renamed when file size = 1MB
ActionLog=/boot/protocol.log - 1000 5
4.2.1.3 DNS and NTP settings
The following settings for the domain name service (DNS) and
the network time protocol (NTP) are enterted after the log settings. DNS translates domain names to IP addresses. NTP is
used to clock synchronization over the IP network. Table 4.8
→ describes the parameter used for this configuration.
There is no internal time generation for the system when
the power is interrupted. This means the default time is
used when the system is restarted or rebooted!
Therefore it is important to set the system time with an
NTP server.
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 DSL / VoIPBox BRI – version 21.0.009 Page 63
4 Configuration files
Table 4.8 Parameter used for DNS and NTP settings
Parameter Description
NameServer=<dnsserver> Defines the IP address of the used domain name serv-
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. This parameter must
be set if you use for the NTP server a domain name.
NameServerPrio=
[hosts|resolv]
NtpServer=<nserver> Define the IP or name of the VoIPBox’s NTP server
Ntprepeat=<time> Define the time in seconds the NTP query occurs.
Timezone=<tz> Defines the timezone settings (see Table 4.9 on
Allows the default order of the DNS lookup to be
changed.
hosts search for the IP address first in file /etc/hosts.
That is the default.
resolv send a search request to the DNS server first, if
this fail a lookup in the /etc/hosts will follow.
<nserver> queries the standard time.
NOTE: If your system is not attached to an NTP server, you can enter the following configuration to query the time on an attached PBX via a TE port:
SubscriberXX=...TIME
page 64 →).
Table 4.9 Timezone settings for different locations (page 1 of 3)
Ct Tow n Settings
Melbourne,Canberra,Sydney
Perth WST-8
Brisbane EST-10
EST-10EDT-11,M10.5.0/02:00:00,M3.5.0/03:00:00
Adelaide CST-9:30CDT-10:30,M10.5.0/02:00:00,M3.5.0/
Australia
Darwin CST-9:30
Hobart EST-10EDT-11,M10.1.0/02:00:00,M3.5.0/03:00:00
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 64
03:00:00
4 Configuration files
Table 4.9 Timezone settings for different locations (page 2 of 3)
Ct Tow n 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
Kyiv, Ukraine EET-2EEST,M3.5.0/3,M10.5.0/4
Lisbon, Portugal WET-0WEST-1,M3.5.0/01:00:00,M10.5.0/02:00:00
Europe
London, Great Britain GMT+0BST-1,M3.5.0/01:00:00,M10.5.0/02:00:00
Madrid, Spain CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00
Oslo, Norway CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00
Paris, France CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00
Prague, Czech Republic CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00
Roma, Italy CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00
Moscow, Russia MSK-3MSD,M3.5.0/2,M10.5.0/3
St.Petersburg, Russia MST-3MDT,M3.5.0/2,M10.5.0/3
Stockholm, Sweden CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00
Tallinn, Estonia EET-2EEST-3,M3.5.0/03:00:00,M10.5.0/04:00:00
Auckland, Wellington NZST-12NZDT-13,M10.1.0/02:00:00,M3.3.0/
03:00:00
New Zealand
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 65
4 Configuration files
Table 4.9 Timezone settings for different locations (page 3 of 3)
Ct Tow n Settings
Hawaii Time HAW10
Alaska Time AKST9AKDT
Pacific Time PST8PDT
Mountain Time MST7MDT
Mountain Time (Arizona,
no DST)
Central Time CST6CDT
Eastern Time EST5EDT
USA / Canada
Atlantic Time AST4ADT
Atlantic Time (New Brunswick)
Newfoundland Time NST+3:30NDT+2:30,M4.1.0/00:01:00,M10.5.0/
Jakarta WIB-7
Singapore SGT-8
Asia
Ulaanbaatar, Mongolia ULAT-8ULAST,M3.5.0/2,M9.5.0/2
Brazil, São Paulo BRST+3BRDT+2,M10.3.0,M2.3.0
Argentina UTC+3
Central America CST+6
MST7
AST4ADT,M4.1.0/00:01:00,M10.5.0/00:01:00
00:01:00
Central and South America
4.2.1.4 Controller settings
This category defines the parameters that apply to the ports.
The individual ports are defined with the following parameters. Ports set to the same type can have the same address. In
this case they will form a trunk group. If you change this pa-
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 66
4 Configuration files
rameter in the configuration, you must restart the system. Ta-
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> AUTOUP TRAP [SC | AC]
<port> Defines the running (physical) port number.
<address> Defines the configured (virtual) port address. In the default configura-
tion, the BRI TE port is 9, and the BRI NT port is 10. The VoIP port is 40.
<type> Defines the connection type:
TE external (Terminal Endpoint). Only the first controller
NT internal (Network Termination). All NT ports must be
VOIP VoIP module with different codec support.
VOIP SC VoIP software module that supports only G.711.
DTMF virtual controller for activating DTMF tone recognition.
can be set as TE.
configured together to the right of the TE ports.
<mode> Defines the protocol for BRI lines: DSS1
<line_type> Defines Point-to-Multipoint or Point-to-Point mode:
UNIT:<unit> (Optional) Defines the currency for the charges (default EUR). Special
VALUE:
<value>
AUTOUP For TE-ports only: keeps ISDN layer 2 active all the time.
SC Soft codec, only on VoIP ports if the coding is done by software mod-
AC Hardware codec from AudioCodes, only on VoIP ports if the coding is
PMP Point-to-Multipoint
PP Point-to-Point
charge generation is possible for:
Switzerland UNIT:&CH
NOTE: The <line_type> must be configured for these entries to
work.
EXAMPLE:
Controller02=10 NT DSS1 PMP UNIT: VALUE:0.010
Controller03=10 NT DSS1 PMP UNIT: VALUE:0.010
(Optional) For DSS1 NT ports only. Defines the charges that accumulate by unit. Enter the values in the following formats: x.y, x.yy, or x.yyy.
Default is 0.120.
ules. Do not change these settings. The configuration depends on the
VoIPBox DSL / VoIPBox BRI hardware. The following codecs are supported g711a and g711μ.
done by this codec vendor. Do not change these settings. The configuration depends on the VoIPBox DSL / VoIPBox BRI hardware of the 8
BRI box.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 67
4 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
Features for each port can be defined using this entry. Changes become active following a restart Table 4.11 → list some
settings for the subscriber used for the VoIPBox DSL /
VoIPBox BRI.
You must restart the system after making changes to activate the settings.
Table 4.11 pabx.cfg: Subscriber Parameters
Subscriber<port>=<list>
<port> Refers to the running (physical) port number of the controller.
The <list> variable may contain one or more of the following keywords:
TRANSPARENT
ROUTER
ALARM Activates the monitoring mode for the respective port. If a rel-
Only the number is sent as caller ID (without the virtual port
address). Activate configuration suffices to activate changes. If
TRANSPARENT ROUTER is not set, the address of the incoming
port is added to the A party number as a prefix.
evant error occurs at the port, the error is written in the protocol.log file. Depending on the configuration, a remote
connection to the number defined for AlarmCallback is established. Activate configuration suffices to activate changes.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 68
4 Configuration files
!
Table 4.11 pabx.cfg: Subscriber Parameters (continued)
Subscriber<port>=<list>
CHMAX[x] Defines the maximal number of VoIP channels or DTMF chan-
nels. Do not change these settings because the settings depends on the VoIPBox DSL / VoIPBox BRI hardware.
Example 4.11 → shows the configuration for a VoIPBox DSL /
VoIPBox BRI with 8 ISDN ports. On the box with 4 ISDN there is
no AudioCodes controller.
A maximum of two concurrent channels are possible for DTMF
recognition if the callback platform is used.
DTMF[<sec>,/<dir>/
<file>]
Keyword to configure the DTMF controller. For a description of
the format see Chapter 5.11 Announcements on page 112 →.
Example 4.11 → applies for the VoIPBox BRI with 8 ISDN
ports. On the VoIP controller 08 (Lantiq) and 10 (softcodec)
are maximal 4 and on controller 09 (AUdioCodes) maximal 8
VoIP channel.
Example 4.11 VoIPBox DSL / VoIPBox BRI with 8 ISDN ports subscriber settings
Controller08=40 VOIP
Controller09=40 VOIP AC ; only on the box with 8 ISDN
Controller10=40 VOIP SC
Subscriber08=TRANSPARENT ROUTER CHMAX[4] ALARM
Subscriber09=TRANSPARENT ROUTER CHMAX[8] ALARM ; only on the 8 ISDN box
Subscriber10=TRANSPARENT ROUTER CHMAX[4] ALARM
4.2.2 SMTP-Client Configuration
The following entries in the pabx.cfg’s [Mail] section are used
to send e-mail messages from the VoIPBox. The connection to
the SMTP server can be used to send CDR files or alarm messages.
You must restart the system after making changes to activate the settings.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 69
4 Configuration files
The following features are possible:
| Sending CDRs via e-mail
| Sending alarm messages via e-mail
Table 4.12 pabx.cfg Mail parameters used in Example 4.12 →
Mail Parameters
MailAllowedPeers=<ip addr>
Defines IP addresses from which incoming SMTP connections will be accepted. Separate IP addresses with a space. If a dash (-) is entered, the SMTP port (25) will be
blocked for incoming sessions. If this parameter is left empty (default), incoming connections will be accepted from all IP addresses.
MailFrom=<URL>
Enter here the URL that will be sent in the e-mail’s FROM field in the following possible
formats:
MailFrom=domain to send OAD@domain (or user@domain, if no OAD available).
MailFrom=ipaddress to send OAD@ipaddress (or user@ipaddress, if no OAD available).
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> is not added.
MailRcptMax=<count>
Number of "RCPT TO" entries in e-mails that come from the LAN (a message is sent to
the LCR for each "RCPT TO" entry in each incoming e-mail).
MailSendRetries=<count>
Number of times an attempt is made to send an e-mail. Default 10.
SmtpServer=<ip addr>
In <ip addr>, enter the IP address of the destination SMTP server that is to receive the
e-mail messages.
Example 4.12 pabx.cfg Mail Parameters
[Mail]
SmtpServer=172.16.0.10
MailRcpt=teles.de
MailFrom=172.16.0.100
MailRcvMax=300
MailRcptMax=50
MaxMailsToHost=2
MailToHostRetries=10
MailSendRetries=10
MailAllowedPeers=172.16.0.10
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 70
4 Configuration files
Sending Alarm Messages via E-mail
With the appropriate configuration, you can send e-mails containing 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 function.
Example 4.13 Sending Alarm Messages via E-mail
ActionLog=/data/protocol.log daily 1000 5 @<e-mail account>
4.2.3 Night Configuration
The [Night<num>] section is reserved for prospective timecontrolled configuration changes. In the pabx.cfg file, the
Night sections contain all of the system’s Subscriber entries.
Simply copy all Subscriber lines into the Night Section with-
out making any changes.
The sections for the time-dependent configuration changes
and time-controlled routings are defined here.
A maximum of 19 additional daily configuration zones are
possible (Night1 to Night19). The entry NightResetTime reactivates the original configuration contained in the [System]
section.
The entry will have the following syntax:
Table 4.13 pabx.cfg: Night Parameters
Night<num>=<time> <day>
<num> Enter a value between 1 and 19 to define which configuration is to be
loaded.
<time> If there is a time set with the format hh:mm after this entry, this con-
figuration is loaded daily at that time on the defined day.
<day> Use a bitmask to set the weekdays on which the configuration applies
here. The daymask appears in the following order: HoSaFrThWeTu-
MoSu.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 71
4 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 configuration ([System] section) every day at 8:00 p.m:
Example 4.15 Night parameters 2
NightResetTime=20:00 11111111
The configuration section is activated on November 5, December 24, and at noon on Mondays.
Example 4.16 Night parameters 3
Night1=12:00 10000010
Holiday=05.11.
Holiday=24.12.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 72
4 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 bitmask (see Table 4.13 →).
Any defined Night sections must be set in the files pabx.cfg and route.cfg. If there are no changes in these sec-
tions, you must copy them from the [System] section. The
complete Subscriber section must appear in the Night
section of the pabx.cfg. The active route(s) (MapAll, Re-
strict and Redirect entries) must appear in the Night
section of the route.cfg (see Chapter 4.3 Configuration
File route.cfg →).
4.3 Configuration File route.cfg
The system’s routing information is saved in the route.cfg.
The file contains the following sections:
| [System]
| [Night<num>]
| [VoIP=<name>]
| [GateKeeper=<name>]
| [Registrar=<name>]
| [Radius=<name>]
4.3.1 Entries in the Sections [System] and [Night<num>]
The sections [System] and [Night<num>] contain the follow-
ing entries.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 73
4 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. Restrict parameters are always handled be-
fore the MapAll parameters and always require a matching
MapAll parameter.
The left side of the equals sign in the Restrict parameter contains the controller number plus an optional trunk number or
a specific calling number (OAD). The special symbol ? may be
used as a wildcard to represent any character. The right side
contains the prefix that is to be put in front of the DAD and an
optional service indicator.
In the route.cfg, the list of Restrict parameters is searched
from bottom to top for a matching controller plus optional
trunk number / OAD. Because the search is done bottom up,
place the more specific Restrict entries below the more general ones. Once a match has been found, the DAD is prefixed
with the contents of the <pl> variable. Then the call is
mapped.
Table 4.14 route.cfg: Restrict Parameters
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-
<controller> Contains the controller number.
<calling number> Contains the calling number (OAD).
The special symbol ? may be used as a
wildcard to represent any character.
<pl> Stands for a virtual placeholder. The
DAD is prefixed with the contents of
this variable.
its
Optional
59
59
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 74
4 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-
its
<sin> The service indicator variable sin re-
stricts the command to one service.
Without a sin, the Restrict command
is valid for all services.
Possible service indicator values are:
01 Telephony
02 Analog services
03 X.21-services
04 Telefax group 4
05 Videotext (64 kbps)
07 Data transfer 64 kbps
08 X.25-services
09 Teletext 64
10 Mixed mode
15 Used internally for call-
16 Video telephone
D<diverting number>
R<calling number> For calls that are redirected with
For calls that have been diverted by the
network, RestrictD replaces the contents in <diverting number> by the
contents in <pl>. Only in combination
with the service indicator 15.
Redirect3, the original OAD can be
changed again using RestrictR. Only in
combination with service indicator 15.
ing-party manipulation
2
59 for the
diverting
number
59 for the
calling
number
Optional
T<calling number> For calls that are redirected with
Redirect2, the original OAD can be
changed again using RestrictT. Only in
combination with service indicator 15.
All calls coming from BRI controller 9 (PSTN) are sent to BRI
controller 10 (PBX). First, the Restrict command adds the prefix “pl” to the DAD of the received call for all calls coming from
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 75
59 for the
calling
number
4 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. The prefix or
telephone number (DAD) for which the mapping applies is
searched and the call routed according to the matching mapping entry.
Mapping entries begin with the keyword MapAll. They work
as follows: anything on the left of the equals sign is removed
from the prefix / telephone number (DAD) that has come in
and replaced with what is on the right of the equals sign.
If, for example, the incoming DAD is 12345678 with 123456
being the trunk number and 78 the extension,
MapAll123456=9123456 means that 123456 is cut off the
number and 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 DSL / VoIPBox BRI – version 21.0.009 Page 76
4 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-
<direct> Defines the prefix or telephone number
(DAD) for which the entry applies.
<num> Defines the routing for a call in the order
given:
Destination port’s controller number
Op ti on al Vo IP pro f ile na me fo ll ow ed b y
a colon if the call is terminated via VoIP
Optional prefix
Part of the number on the left that is
transmitted
The special symbol ? may be used as a
wildcard to represent any character.
The special symbol . may be used as a wild-
card to represent any digit.
<mode> VOICE Applies for calls with the
service indicator voice (default).
DATA Applies for calls with the
service indicator data.
its
29
59
4 or 5 X
Optional
All international calls (DAD starts with 00) are sent to the VoIP
controller 40 with the profile name DF. 00 is removed from
the DAD, 40DF:00 is added to it. All national calls (DAD starts
with 0) are sent to the controller with the number 9. It is important that the mapping for international calls is placed
above the mapping for national calls. If you change the order
of both mappings, international calls would be sent to controller 9 instead of 40.
Example 4.18 route.cfg Map Parameters
MapAll00=40DF:00
MapAll0=90
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 77
4 Configuration files
4.3.1.3 Redirect
This entry facilitates alternative routing when the first destination cannot be reached or is busy. A placeholder appears to
the right of the equal sign. The routing entry (MapAll) can be
defined for the redirect using the placeholder entered:
Table 4.16 route.cfg: Redirect Parameters
Redirect<type><num>=<redirect> <sin> <time>
Parameter Description No. Digits Optional
<type> Enter 2 or 3 to set the following types:
2 call forwarding no answer
3 call forwarding when busy
<num> Defines the number for which calls will
be redirected. The special symbol ?
may be used as a wildcard to represent
any character.
<redirect> Defines the placeholder used in the
two-target rou ting entry and the number to which calls to <x> will be redirected.
<sin> The service indicator variable sin re-
stricts the command to a service. Without a sin, the Redirect command is
valid for all services.
Possible service indicator values are:
00 All services
01 Telephony
02 Analog services
03 X.21-services
04 Telefax group 4
05 Videotext (64 kbps)
07 Data transfer 64 kbps
08 X.25-services
09 Teletex 64
10 Mixed mode
15 Videotext (new standard )
16 Video telephone
NOTE: Fax forwarding must be set for
analog and telephony services because
incoming fax calls from the analog network may arrive with either telephony
or analog service indicators.
1
59
59
2 (X)
(Only optional if
<time> is
not set. If
<time> is
set and
<sin> is
not needed please
select 00
for sin.)
<time> For type 2 redirect entries, a timer (in
seconds) can be defined after the service indicator entry.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 78
255 X
4 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 command activates the second target mapping with the placeholder A and the call is automatically sent to controller 9.
Example 4.19 Redirect 1
MapAll00=40DF:00
Redirect340DF:=A
MapAllA=9
In the following example, calls to 20 that remain unanswered
for 12 seconds and calls to 21 that remain unanswered for 20
seconds are redirected through the PSTN port.
Example 4.20 Redirect 2
MapAll01555=|2001555<<13
MapAll01556=|2101556<<13
Redirect220=A 01 12
Redirect221=A 01 20
MapAllA=9
Excluding Busy Calls or Specific Cause Values from Redirect
Defines a hexadecimal cause value according to DSS1. When
connections to the destination are rejected because of the
reason defined by the cause value, the VoIPBox sends a busy
signal to the attached PBX. Alternative routing is not carried
out.
To avoid second-choice routings when the called-party number is busy, set the following parameter in the first-choice
port’s 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 because of the reason defined by the cause value, the VoIPBox
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 79
4 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.
In the following example, all outgoing calls over controller 04
are rejected with the cause value 91 when the called party is
busy. Alternative routing is not carried out.
Subscriber04=....BUSY[91]
4.3.2 VoIP Profiles
This section includes all of the most important parameters for
communication with the VoIP peer.
Basic Parameters
Table 4.17 → list some often used parameter. For more infor-
mation please see the Parameter manual.
Table 4.17 route.cfg: VoIP Basic Parameters
VoIP Basic Parameters
[Voip=<name>]
Name of the routing profile. The name must begin with a letter. Choose a short and
meaningful name.
VoipDirection=<mode>
Defines the direction in which VoIP calls can be set up. Possible options: In, Out, IO,
None).
VoipPeerAddress=<ip addr> or <name>
The peer’s IP address or name. Default is 0 (if it is not set, please set the parameter
VoipIpMask to 0x00000000).
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 80
4 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. Default is 0xffffffff (only incoming traffic is accepted
from the defined peer address).
VoipSignalling=<int>
Determines the profile’s signaling protocol for outgoing VoIP calls. In the case of incoming calls, auto recognition ensures that each call from the peer is accepted, regardless of the protocol:
0=H.323 (default), 1=SIP udp, 2=SIP tcp, 3=tls.
NOTE: TLS requires the following additional software: crypto.vnd and the key files
key.pem and cert.pem.
VoipCompression=<list>
The compression to be used, in order of preference. At least one matching codec with
the peer must be defined.
Voice:
g729, g729a, g729b, g729ab
g72616, g72624, g72632, g72640
NOTE: G726 32kBit/s can also be signaled as G.721 by using the entry g721.
g728
g711a, g711u
g723, g723L
NOTE: This has no influence on the compression ratio of incoming RTP packets. Both
sides must be able to receive both ratios.
gsm
The following codecs are also possible: g721 (SIP only)
Fax: t38
Data: trp
gnx64
ccd
Define a special profile for data call origination or destination numbers. Bear in mind
that echo cancellation in this VoIP profile might be switched off (VoipECE=no).
These codecs have a bit rate of 8 kbit/s (compression ratio 1:8). A stands
for annex a and b for Annex b.
These ADPCM codecs have various bit rates: g72616 = 16kBit/s (compression ratio 1:4), g72624 = 24kBit/s, g72632 = 32kBit/s (compression ratio
1:2), and g72640 = 40kBit/s.
The Codec has a bit rate of 16kBit/s (compression ratio 1:4).
These PCM codecs have a bit rate of 64kBit/s. No voice compression occurs. a stands for a-law and u for μ-law.
These codecs work with 30ms data frames. g723.1 uses a bit rate of 6.3
kbit/s, and g723L uses a bit rate of 5.3 kbit/s to send RTP packets.
GSM-FR (full rate) has a bit rate of 13 kbit/s.
T.38 (fax over IP) allows the transfer of fax documents in real time between
2 fax machines over IP. Following fax detection during a call, the voice codec will switch to T.38.
Transparent or clear mode (RFC 4040). Transparent relay of 64 kbit/s data
streams.
Clear-channel signaling (as per RFC3108)
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 DSL / VoIPBox BRI – version 21.0.009 Page 81
4 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.
Voi pT xM= <n um> or <list> fix
The multiplication factor (1-12) for the frame size for transmission of RTP packets (default is 4). 10ms is the default frame size. A list can be defined if different frame sizes
are to be used for different codecs in the VoIP profile. The list must correspond with
the list in the parameter VoipCompression.
Normally the peer’s frame size will be used if it is smal ler than the one defined. If you
enter fix, the configured factor will always be used.
Management Parameters
Table 4.18 route.cfg: VoIP Management Parameters
VoIP Management Parameters
VoipGk=<list>
Name of the assigned gatekeeper profile. You can assign a profile to several gatekeepers to define backup gatekeepers for a VoIP profile. In this case, the next gatekeeper
will be used if the previous one fails.
VoipProxy=<ip addr>
Enter the IP address of the SIP server.
VoipUser=<username>
Define the username for the remote device if authentication is required (SIP only).
VoipPwd=<password>
Define the password for the remote device if authentication is required (SIP only).
VoipRegistrar=<name>
Enter the name of a registrar to be used for the VoIP profile.
VoipRadiusAuthenticate=<name>
Enter the name of the Radius server to activate user authentication.
VoipRadiusAccounting=<name>
Enter the name of the Radius server to activate accounting.
VoipIpLogging=<mode>
Enter Yes to activate recording IP addresses in the CDRs (default is No). The first IP address is the signaling address and the second is the RTP address, followed by the codec and the frame size used.
Example of a CDR entry:
21.08.07-11:01:42,21.08.0711:01:58,40,912345,192.168.0.2:192.168.0.2,G729,10,0101,16,10,0
Example of a failed log entry:
21.08.07-11:11:30,40,91234,192.168.0.2:192.168.0.2,G729,10,0101,ff,2,1
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 82
4 Configuration files
Table 4.18 route.cfg: VoIP Management Parameters (continued)
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 during problem analysis when IP issues occur (default = No).
VoipHold=<mode>
Determines the behavior of the HOLD feature if a PBX sends an Re-INVITE message
for HOLD to the VoIPBox.
transparent: HOLD is sent to PSTN
notify: HOLD is sent as notification to the telephone exchange
ignore: HOLD is not sent to the telephone exchange - the VoIPBox suppresses the
messages to PSTN
VoipSelectProfilesBySignalling=<Yes/No>
When Yes is entered, Voip Si gna lli ng =<i nt > is taken as the criterion for selecting a
voip-profile for an incoming voip call, i.e. the signalling for this voip call must match
the VoipSignalling parameter in this profile. Default No.
4.3.3 Gatekeeper Profiles
Gatekeeper profiles are used to connect the VoIPBox to several systems by using a gatekeeper if the protocol is H.323. It
is possible to configure different gatekeepers for different
destinations and to define backup gatekeepers. These gatekeeper profiles are then assigned to the VoIP profiles:
Table 4.19 route.cfg: Gatekeeper Parameters
Gatekeeper Parameters
[Gatekeeper=<name>]
Name of the gatekeeper profile.
RasPort=<port>
Indicates the port the gatekeeper uses (default 1719) for registration, admission and
status.
OwnRasPort=<port>
Indicates the port the system uses (default 1719) for registration, admission and status.
RasPrefix=<list>
VoIPBox’s defined prefix(es). Use a space to separate entries.
RasId=<name>
The alias used for gatekeeper registration.
GkId=<name>
The gatekeeper’s alias.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 83
4 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>
Max. number of channels used for this gatekeeper. If this parameter is not defined
(default), there will be no limit.
GkUseStun=<mode>
Enter yes (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 Yes to activate this function; default value is No).
GkTerminalTypeWithPrefix=<mode>
Enter No to deactivate sending the Dialed Prefix Information in the Registration Request (default Yes).
GkDynRai=<mode>
When yes is entered, the GK receives an RAI (resource availability indication) when a
status change occurs on the available mobile channels. When no is entered, the RAI is
sent with each ARQ (admission request) and DRQ (disengaged request). Default is no.
GkNoResourceAvailableIndication=<mode>
With this parameter the <system> will not send RAI indications to the Gatekeeper. Default No.
4.3.4 Registrar Profiles
Registrar profiles are used to register the VoIPBox with a SIP
registrar. It is possible to configure different registrars for different destinations and to define backup registrars. These
registrar profiles are then assigned to the VoIP profiles:
Table 4.20 route.cfg: Registrar Parameters
Registrar Parameters
[Registrar=<name>]
The name of the registrar profile.
RegId=<name or ip addr>
Host name or IP address used in the register’s request header. Bear in mind that the
DNS service must be active if you enter the host name.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 84
4 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.
RegSameCallID=<mode>
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 Contact: field.
RegContactParam=<string>
Sets additional header-parameters in the contact field (e.g.the q-value: RegContactParam=q=1.0).
RegUser=<name>
Enter a username for authorization.
RegPwd=<password>
Enter a password for authorization.
RegProxy=<ip addr>
Enter an alternative IP address if you want the request to be sent to an address other
than the one entered in RegId.
RegExpires=<sec>
Enter the number of seconds registration is to be valid. Default 0 means infinite.
RegPing=<sec>
Interval (in seconds) for the registrar ping. The VoIPBox sends an empty UDP packet
to the registrar’s IP address. The packet is essentially an alive packet to avoid possible
firewall problems.
RegSignalling=<int>
Determines the profile’s signaling protocol for registration with the SIP registrar.
1=SIP udp (default)
2=SIP tcp
3=SIP tls
RegUseReceived=<mode>
Enter Yes when an VoIPBox appears behind a NAT and STUN cannot be used. Default
No.
RegSameCallID=<mode>
The same call ID is used for SIP registration Enter No to change the call ID for every
reregistration. (default Yes).
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 85
4 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
[Radius=<name>]
The name of the Radius server profile assigned to one or more VoIP profiles.
Host=<name or ip addr>
Radius server’s host name or IP address. Bear in mind that the DNS service must be
active if you enter the host name.
User=<name>
Enter a username for authorization.
Password=<password>
Enter a password for authorization.
Secret=<secret>
Enter the shared secret.
OwnId=<name or ip addr>
Host name or IP address used in the NAS identifier or NAS IP address (Cisco VSA gateway ID).
ServiceType=<num>
As defined in RFC 2865, Chapter 5.6.
RequestTimeout=<sec>
Number of seconds during which the request is repeated if the Radius server does not
respond.
RequestRetries=<count>
Number of packet retries sent at one time.
StopOnly=<mode>
When Yes is entered, only Accounting Request Messages with the status type stop are
transmitted to the Radius server.
AlwaysConnected=<mode>
Enter No (default) to set the value for the field ConnectedTime to that of the field
DisconnectedTime in accounting-stop messages when the call was not connected.
CallingStationId=<num>
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 DSL / VoIPBox BRI – version 21.0.009 Page 86
4 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)
4 = Gandalf proprietary SingleLink/MultiLink protocol
5 = Xylogics proprietary IPX/SLIP
6 = X.75 Synchronous
NasId=<string>
The string entered is used as network access server identifier attribute in access requests. If no string is entered, the attribute will not be set (default).
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 87
5 Additional VoIP
parameters
5 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 communication with the VoIP peer.
5.1 Signaling parameters
Table 5.1 → list some often used protocol independent VoIP
parameter.
Table 5.1 Customized parameters: protocol-independent VoIP signaling (page 1 of 5)
Protocol-Independent VoIP Signaling Parameters
VoipComprMaster=<mode>
This parameter defines which side the first matching codec comes from:
Yes: Default. Priority is determined by the order of the system’s parameter list.
No: Priority is determined by the peer.
VoipConnectOnCallProc=<mode>
Enter Yes (default No) to change an H.323 Call Proceeding/Call Progress and Alert, or
a SIP 180 or 183, into an H.323 Connect or SIP 200 message. This parameter can be
used if an announcement that plays before the Connect requires a Connect on the
other side to put through the call.
VoipDad=<num>
The digits/numbers defined here will appear in front of the original DAD as described
for the parameter VoipOad below. If the parameter is to be valid in only one direction,
you must also set the parameter VoipDadIn or VoipDadOut.
VoipDadIn=<string>
Specifies that the parameter VoipDad is for incoming calls only. If this parameter is
not set (default), VoipDad will apply for both directions.
VoipDadOut=<string>
Specifies that the parameter VoipDad is for ou tgoing calls only. If this parameter is not
set (default), VoipDad will apply for both directions.
VoipDataBypassPayloadType=<num>
Defines the payload type for the RTP packets when the call is sent as a data call. Default 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 DSL / VoIPBox BRI – version 21.0.009 Page 89
5 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 prepare or even allow a switch to T38. Default no.
VoipG72616PayloadType=<num>
Changes the RTP payload type for G.726 16 b/s. Default is 35. A common alternative
is one of the dynamic payload types from 96 to 127.
VoipG72624PayloadType=<num>
Changes the RTP payload type for G.726 24 b/s. Default is 36. A common alternative
is one of the dynamic payload types from 96 to 127.
VoipG72632PayloadType=<num>
Changes the RTP payload type for G.726 32 b/s. Default is 2. A common alternative is
one of the dynamic payload types from 96 to 127.
VoipG72640PayloadType=<num>
Changes the RTP payload type for G.726 40 b/s. Default is 38. A common alternative
is one of the dynamic payload types from 96 to 127.
VoipHideOadByRemove=<mode>
If Yes is configured and call setup is to VoIP, the OAD will be removed from signaling if
presentation restricted or user-provided, not screened is set in the calling party’s presentation or screening indicator. No (default) means no change will occur.
NOTE: If the SIP protocol is used, Anonymous will always appear as the account in the
From field. Transmission of the OAD can occur in the P-asserted header.
VoipIgnoreDADType=<mode>
Enter yes to change the DAD type to unknown, for example from international. The
type is lost, for example the leading 00 bit is removed. Default no.
VoipLimit=<limit>
Limit with this parameter the total number of units that can be sent through the VoIP
profile where this parameter has been configured. If the limit has been reached, no
further outgoing calls are possible via this profile. The length of a unit in seconds is
defined with VoipUnitPeriod. The counter is reset using the ResetCounter parameter
in the pabx.cfg file.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 90
5 Additional VoIP parameters
Table 5.1 Customized parameters: protocol-independent VoIP signaling (page 3 of 5)
Protocol-Independent VoIP Signaling Parameters
Voi pO ad= <n um> (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. If it is found, the OAD will not be transmitted. If the string does not
match, the remaining OAD will be transmitted.
In the following example, the OAD is not transmitted.
EXAMPLE: VoipOad=-3-\555
In the following example, the remaining OAD 5551212 is transmitted.
EXAMPLE: VoipOad=-3-\444
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\
Enter -\?\y\ to replace any first digits with y. ? is used as a placeholder for one digit. ?
and y can have different lengths.
In the following example, the first three digits are replaced by 00517.
EXAMPLE: VoipOad=-???\00517\
Use a semicolon to concatenate several Vo ipO ad commands. The commands are pro-
cessed from left to right.
In the following example, the first three digits are removed from the beginning of the
OAD. In the remaining OAD, the first three digits are replaced by 444. The OAD
4441212 is transmitted.
EXAMPLE: VoipOad=-3;-???\444\
NOTE: If the parameter is to be valid in only one direction, you must also set the parameter VoipOadIn or VoipOadOut.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 91
5 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.
EXAMPLE: VoipOad=001
To tra nsm it o nly OAD s co nsi sting o f m ore di git s th an thos e de fin ed, e nte r a ! , fo llowed
by the number of digits, at the end of the entry. If the OAD has more digits, it will be
transmitted unchanged. If it has the same number or fewer digits, only the string in
front of the ! will be added in front of the OAD. In the following example, the digits
0015175551212 will appear::
EXAMPLE: VoipOad=001!10
If a minus (-) is entered, the original OAD will not appear. In the following example, no
number will be transmitted.
EXAMPLE: Voi pO ad= -
If integers are entered before the minus sign, only the digits entered in front of the
minus sign will be displayed. In the following example, 789 will appear.
EXAMPLE: VoipOad=789-
If an integer is entered after the minus sign, this number of digits will be removed
from the beginning of the OAD. In the following example, 517 will be removed from
the OAD:
EXAMPLE: Voi pO ad= -3
If -\ is entered followed by the first part of an OAD, that part will be removed. If the
string does not match, the OAD will be transmitted unchanged. In the following example, only 1212 will be transmitted.
EXAMPLE: VoipOad=-\517555
To modify the original OAD, enter random<x>, whereby x represents a number of ran-
dom digits between 1 and 10 that will appear in the OAD. In the following example,
001 plus 2 random digits plus the original OAD will appear.
EXAMPLE: VoipOad=001random2
If --\ is entered followed by a part of an OAD (not necessarily the first part), the OAD
will not be transmitted at all. If the string does not match, the OAD will be transmitted
unchanged. In the following example, the OAD is not transmitted.
EXAMPLE: VoipOad=--\555
VoipOadIn=<string>
Specifies that the parameter VoipOad is for incoming calls only. If this parameter is
not set (default), VoipOad will apply for both directions.
VoipOadOut=<string>
Specifies that the parameter VoipOad is for outgoing calls only. If this parameter is not
set (default), VoipOad will apply for both directions.
VoipProgress=<int>
For H.323: 0=progress indicator is not transmitted. 1 (default)=progress indicator is
transmitted. 2=address complete message is transmitted. 3=call proceeding message
type changed in alerting message type.
For SIP: 0=183 response ignored and not sent. 1=183 response changed to a progress
message with inband-info-available at the ISDN interface (default). 2=183 response
changed to an address complete message at the ISDN interface. 3=183 response
changed to an alerting at the ISDN interface.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 92
5 Additional VoIP parameters
Table 5.1 Customized parameters: protocol-independent VoIP signaling (page 5 of 5)
Protocol-Independent VoIP Signaling Parameters
VoipRingToneFile=</path/file.711>
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.
VoipSignalCLIR=<string>
When the configured string appears at the beginning o f the OAD and the parameter
VoipHideOadByRemove is set, the OAD is removed from signaling, regardless of the
presentation bits in the calling party field. If the parameter VoipHideOadByRemove is
not set (default), the presentation bits are set at presentation restricted (CLIR) if
<string> is -. If the string matches the first digits of the OAD and it comes in with CLIP,
the call will be sent to VoIP using CLIR. If the call comes in with CLIR, the string will be
added to the beginning of the OAD and CLIR will be removed in the signaling.
VoipSingleTcpSession=<mode>
Enter Yes to send all outgoing VoIP connections in a single TCP session. Enter No (default) for an extra TCP session for each VoIP connection.
VoipSuppressInbandInfoAvailableIndicatorInCallProceeding=<mode>
Enter yes to send or receive the Progress Indicator in the Q.931 Call Proceeding message. Default no.
VoipTrpPayloadType=<num>
Defines the payload type for data calls when trp (transparent/clear mode) is used as
codec in VoipCompression=<list>. Default is 56. A common value is 102.
VoipUnitPeriod=<sec>
Set this parameter to a number greater or equal 1 to define how many seconds make
up a unit in the VoipLimit parameter.
Table 5.2 Customized parameters: H.323 signaling
H.323 Signaling Parameters
VoipCanOverlapSend=<mode>
Enter off to deactivate overlap sending during setup (default on).
VoipH245Transport=<int>
This option determines the H.245 offer. 0 (default)=all signaling variants are offered;
1=FastStart only; 2=H.245 tunneling only; 3=extra session.
VoipMapAddressType=<mode>
Fo r ca ll s from VoI P to PST N on ly. Ent er yes to change the 00 at the beginning of a number to international and 0 to national.
VoipMCinRLC= <mode>
Enter Yes to cause the system to send the media channel capability in the reverse logical channel parameters as part of the 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 VoipCompression. Default No.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 93
5 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
No.
VoipService=0x<service indicator>
This parameter sets the ISDN bearer capability. For example, it can be used for calls
coming from VoIP with the bearer capability data. You can define the service indicator
as it is in the 1TR6 code:
101 - ISDN 3,1kHz
102 - analog
103 - ISDN 7kHz
201 - Fax 2
202 - Fax 3
203 - Fax 4
700 - Data
Normally 101 is used. You can send another value to a switch that wants to handle
VoIP calls differently from PSTN calls.
EXAMPLE:
Voi pS erv ic e=0 x1 01
VoipSetupAck=<int>
1=setup acknowledge is transmitted; 0= setup acknowledge is not transmitted; 2 (default) =transmitted with H.323 information.
Table 5.3 Customized parameters: SIP signaling (page 1 of 4)
SIP Signaling Parameters
VoipAckWithSdp=<mode>
Enter yes to send the SDP content in the SIP ack message. Default no.
VoipAllow=<list>
The allow header shows the supported methods and can be set here.
EXAMPLE: VoipAllow=INVITE,BYE
The default setting includes the following:
INVITE,ACK,CANCEL,BYE,UPDATE,REGISTER,PRACK,INFO,NOTIFY,REFER
It may be necessary to remove some of these entries for some peers.
VoipAllowTlsAoc99=<yes/no>
If the AOC99 information (charging information) is sent within a SIP-info-message and
this parameter is set to yes, the AOC information is evaluated. The default value is yes.
VoipAngleBracketIsReserved=<yes/no>
Enter yes to replace < or > in the SIP u ri by their ASCII encoding %3c or %3e. Is needed
when a peer does not accept < or >. Default no.
VoipAnswerUnknownUser=<yes/no>
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 DSL / VoIPBox BRI – version 21.0.009 Page 94
5 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 incoming SIP-Invite.
VoipContactParam=<string>
Sets additional header parameters in the contact field.
VoipDadSource=<int>
SIP only: defines the field from which field the called party number coming from SIP
is to be taken:
0 = URL or URI in the Invite request that contains only digits, otherwise the To: field is
used (default)
1 = To: field
2 = Remote-Party-ID with party = called
4 = URL or URI in the Invite request that can also contain letters
8 = Diversion header (in case a redirect number is to be used as destination number)
VoipDelayDisc=<mode>
Yes delays confirmation transmission during call teardown. That means the release
tone is audible when the peer tears down the call. Default is no.
VoipInfoSamOnly=<mode>
This parameter determines the behavior in the case of overlap sending (VoipOverlap
must also be set). Yes means that the contents of the SubsequentNumber field in info
method will be attached to the URI’s available digits or to the invite message’s To field.
No (default) means that the digit contents of the SubsequentNumber field will be
used.
VoipOadSource=<int>
SIP only: defines the field from which field the calling party number coming from SIP
is to be taken:
0 = From: field (default)
1 = Remote-Party-ID
2 = P-Preferred-Identity
4 = P-Asserted-Identity
8= Display field
NOTE: If 2 or 4 are entered, the number in the field must begin with tel:
Going to SIP, the OAD is written in the following field:
0 = From: field (default)
1 = Remote-Party-ID (if VoipOwnAddress is not set)
For the fields P-Preferred-Identity and P-Asserted-Identity, please check the corresponding parameters. If the number is sent with CLIR to SIP, the From: field contains
anonymous@anonymous.invalid. If the number has to appear in the From: Field, the
decimal value of the parameter must be increased by 8.
VoipOverlap=<mode>
SIP only. Enter yes to activate signaling with overlap sending, as per draft-zhang-sipping-overlap-01.txt. That means digit collection is no longer necessary in the routing
when the digits come from ISDN/POTS with overlap sending. When this parameter is
active, VoipPrack is automatically set to yes. Default is no.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 95
5 Additional VoIP parameters
Table 5.3 Customized parameters: SIP signaling (page 3 of 4)
SIP Signaling Parameters
VoipOwnAddress=<account@domain>
Used for the From field in Sip-Invite and Sip-Response messages. If only the domain
is entered, the origination address (for example from ISDN) followed by an @ sign will
automatically be set at the beginning.
EXAMPLE: VoipOwnAddress=teles.com
VoipOwnDisplay=<string>
The entry is sent as Display Name in the From Field in SIP transmissions. The keyword
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.
<string> The defined string is transmitted
A combination of both is possible.
Examples: 030* or tel:* or sip:user@carrier.de
VoipP-Preferred-Identity=<string>
Sets the P-Preferred-Identity field in the SIP invite message. The following settings are
possible towards SIP:
* The OAD coming from ISDN/POTS is transmitted.
<string> The defined string is transmitted.
A combination of both is possible.
Examples: 030* or tel:* or sip:user@carrier.de
VoipPrack=<mode>
SIP only: Enter yes to activate Provisional Response Messages in the signaling, as per
RFC 3262 "Reliability of Provisional Responses in the Session Initiation Protocol (SIP)".
Default is no.
VoipRejectAnonCause=<cause>
Voip-profile option for SIP only. This variable defines the SIP cause value (e.g. 480) to
reject incoming anonymous sip calls (on this profile). By default not set.
VoipRFC4028=<number>
RFC4028 defines an extension to SIP. This extension allows for a periodic refresh of
SIP sessions through a re-INVITE or UPDATE request. Use this parameter to define in
what way RFC4028 is followed. Enter 0 to not follow RFC4028. Enter 1 to passively follow RFC4028, which means to answer Session-Timer-re-INVITEs or UPDATEs according
to RFC4028. Enter 2 to actively follow RFC4028, meaning that the gateway sends regular Session-Timer UPDATEs. Default is 1.
VoipSdpProxy=<mode>
SIP only. Enter yes to activate proxy mode for SDP signaling for SIP to SIP calls. The
parameters for 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. Default is 0.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 96
5 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 parameter can be used several times.
VoipSipStatusIncompatibleCodec=<reject cause>
An INVITE request is rejected if the codec that is sent with this INVITE does not match
the codecs that have been defined in the VoIP profile. The INVITE is rejected with the
reject cause given in this parameter, as per RFC 3261 (default 415).
VoipSipUserPhone=<mode>
SIP only. Set this parameter to Yes to add ;user=phone in the request header and the
To: line. Default is No.
VoipUseMaxPTime=<mode>
SIP only. Enter yes to set the field mptime (max packet time) with the values set in
VoipTxm (ptime). Default no.
The parameter VoipUseMaxPTime is used when VoipUseMPTime is 0, 1 or 2.
VoipUseMPTime=<int>
This parameter is used to configure packet time signaling in SDP:
0 = set attribute ptime with each individual codec description (default).
1 = set attribute ptime once as the first attribute after the m- line (media type).
2 = set attribute mptime (multiple ptime) once as the first attribute with the list of the
codecs’ corresponding ptimes.
3 = remove attribute ptime or mptime in SDP signaling.
The parameter VoipUseMaxPTime is used when VoipUseMPTime is 0, 1 or 2.
VoipUserAgent=<mode>/<string>
When Yes is set (default), the system type and software version is used in the SIP user
agent header. Enter no to deactivate this setting, or enter a string to change it.
VoipUtuFormat=<int>
Enter 1 to transfer ISDN user to user information to SIP and vice versa in the following
special format: 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 recommendation in http://tools.ietf.org/html/draft-johnston-sipping-cc-uui-09.
5.2 STUN server parameter
Enter here the STUN server’s IP address. A STUN server allows
NAT clients (i.e. computers behind a firewall) to setup phone
calls to a VOIP provider hosted outside of the local network.
When this parameter is active, the gateway looks for a (NAT)
firewall in the network and figures out how to bypass it. All
ports for signaling, RTP and RTCP are checked starting from
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 97
5 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.
This is not a solution for all firewall types.
Table 5.4 STUN server parameters
STUN server parameters
StunServerAddress=<ip address>
Defines the IP address <ip address> of a STUN server.
StunServerPollInterval=<sec>
Defines the Interval <sec> in seconds for the stun request at each port. (default 600).
StunServerPort=<port>
Defines the STUN server port <port> (default 3478).
5.3 Set up the VoIPBox DSL / VoIPBox BRI as Registrar
Enhance the VoIP profile using the parameters listed in Table
5.5 → to allow other SIP user agents to register on the VoIP-
Box DSL / VoIPBox BRI. In this case the VoIPBox DSL / VoIPBox
BRI works as a registrar. This is a server that accepts REGISTER
requests and places the information it receives in those requests into the location service for the domain it handles.
Table 5.5 Customized parameters: location server
Location Server Parameters
VoipAuth=<mode>
Defines the authentication procedure www (default) or proxy.
VoipExpires=<sec>
Defines the maximum number of seconds the agent’s registration applies (default
3600).
VoipOwnPwd=<string>
Defines the password the agent uses to register.
VoipOwnUser=<string>
Defines the username the agent uses to register.
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 98
5 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
VoipIpMask=0x00000000
VoipOwnUser=130
Voi pO wnP wd =te st 130
VoipExpires=300
Voi pA uth =w ww
VoipCompression=g711a g711u g729 g729a g729b g729ab
VoipSilenceSuppression=no
Voi pS ign al lin g= 1
Voi pM axC ha n=8
Voi pT xM= 2
Voi pD tmf Tr ans po rt= 0
VoipRFC2833PayloadType=101
VoipMediaWaitForConnect=Tone
On the remote user agent set up a [Registrar:130] profile as
shown in Example 5.2 →. With that profile the VoIPBox DSL /
VoIPBox BRI b with the IP192.168.1.21, registers on the VoIPBox DSL / VoIPBox BRI a with the IP 192.168.1.12.
Example 5.2 Registrar profile of the SIP user agent 130
[Registrar:130]
RegId=192.168.1.12
RegOwnId=130@192.168.1.21
RegUser=130
RegPwd=test130
RegSignalling=udp
VoIPBox DSL / VoIPBox BRI – version 21.0.009 Page 99
5 Additional VoIP parameters
5.4 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). That means you can use different parameters not only for different IP addresses, but also for different numbers (for example other codec, WaitForConnect, and so on). For example, you can define a number for the head of the
company, so that her MSN always uses G.711.
It is possible to configure a list of numbers for a to tal of up to 80 characters per line.
You must define the entry again if you need more numbers. You can also use a wildcard * at the end of the number to match all calls with OADs or DADs beginning with
the digits entered. Use a comma to separate the numbers.
Example:
VoipDadMask=123, 345*, 567, ....,
VoipDadMask=912, 913*, 914, ....,
Bear in mind that you must enter numbers from specific to global (as for normal routing in the route.cfg). That means you must enter a profile with more specific numbers
above a profile with more global numbers.
VoIPOwnIpAddress=<ip addr> | RH
If the system is behind a NAT firewall that does not translate H.323 or SIP, the private
IP address (not the NAT firewall's public IP address) is transmitted as own IP address
in the H.323 or SIP messages of the gateway. In this case, the public IP address of the
gateway must be defined or retrieved from the SIP request header. The RH option
only works if this parameter is used in a VoIP profile.
VoipUseEnum=<mode>
Enter yes (default no) to activate an ENUM query to the called number before the call
is set up via VoIP or PSTN. Using a standard DNS query, ENUM changes telephone
numbers into Internet addresses. If a number is found, the call is set up via VoIP. If not,
call setup occurs via PSTN or with another VoIP profile.
NOTE: The query must include country and area codes.
VoipUseIpStack=<mode>
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 DSL / VoIPBox BRI – version 21.0.009 Page 100
Loading...