TELES_VoIPBOX_GSM_15.0

8/11/2019 TELES_VoIPBOX_GSM_15.0

1/231

Software version 15.0u

VoIPBOX GSM Family


2/231

T A B L E O F C O N T E N T S

2

Chapter 1 About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

1.1 organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.2 conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.3 Safety Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2 Safety and Security Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

2.1 Safety Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.2 FCC / Industry Canada Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.3 Power Supply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.3.1 Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.3.2 Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.3.3 Instructions for Use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.3.4 Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4 Jacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.5 Tips for EMC Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.6 System Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.6.1 Protecting the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.7 CDR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.8 Network Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 3 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

3.1 Whats New in Version 15.0u . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.2 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.3 Implementation Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 4 VoIPBOX Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

4.1 Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.2 Package Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.3 VoIPBOX Hardware Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4.4 Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.4.1 Analog Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.4.2 Ethernet Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

4.5 Preparing for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.6 Hardware Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

4.7 LED Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4.8 Startup with Quickstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4.8.1 Installing Quickstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4.8.2 Configuration with Quickstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4.8.3 Startup via GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

4.9 Startup via FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

4.10 Self Provisioning with NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4.11 Remote Access and Access Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

ta e o contents


3/231


3

4.11.1 GATE Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4.11.2 Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4.11.3 FTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4.11.4 Setting a Password for Remote Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Chapter 5 Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

5.1 Configuration File ip.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

5.1.1 System Section Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.1.2 Ethernet Interface Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.1.3 GUI Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.1.4 Bridge Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

5.1.5 NAT Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

5.1.6 PPPoE Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

5.1.7 Firewall Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

5.1.8 Bandwidth Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

5.1.9 DHCP Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.1.10 PPP Configuration for Dial-Up Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

5.1.11 VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

5.1.12 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Active Ethernet Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Integrated DSL-Router Scenario for VoIP Traffic with an Active DHCP Server and Firewall. . . . . . . . 53

VLAN Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

5.2 Configuration File pabx.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

5.2.1 System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Bypass Relay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Night Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Global Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

5.2.2 SMTP-Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

5.2.3 Number Portability Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

5.2.4 SNMP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

5.2.5 Time-Controlled Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

5.3 Configuration File route.cfg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

5.3.1 Entries in the Sections [System] and [Night] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Restrict. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Redirect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

5.3.2 VoIP Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

5.3.3 Gatekeeper Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84


4/231


4

5.3.4 Registrar Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

5.3.5 Radius Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Chapter 6 Routing Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

6.1 Mobile Gateway in a Corporate Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

6.2 VoIPBOX Integration in a Carrier Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

6.3 VoIPBOX as the Only Interface to the Outside World . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

6.4 VoIPBOX as a Second-Generation LCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Chapter 7 System Maintenance and Software Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

7.1 Configuration Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

7.2 Status and Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

7.3 Software Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

7.4 Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

7.4.1 ISDN Trace Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

7.4.2 Call Forwarding to SIP Trace Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

7.4.3 POTS Trace Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Trace Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

sst Trace Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

app Trace Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

mid Trace Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

ton Trace Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

7.4.4 Mobile Trace Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1067.4.5 VoIP Trace Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Interface IP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

RTP/RTCP Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Internal Protocol Interface (to ISDN, POTS, Mobile) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

H.245 Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

RAS (Registration, Admission, Status) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

ENUM Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

7.4.6 Remote Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

7.4.7 SMTP Trace Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1377.4.8 Number Portability Trace Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

7.4.9 DTMF Tone Trace Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Chapter 8 Signaling and Routing Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144

8.1 IntraSTAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

8.2 Digit Collection (Enblock/Overlap Receiving). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

8.3 Rejecting Data Calls and Specified Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

8.3.1 Blacklist Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

8.3.2 Whitelist Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145


5/231


5

8.3.3 Rejecting Calls with ISDN Bearer Capability Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

8.3.4 Specific Routing of Data Calls via VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

8.4 CLIP and CLIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

8.4.1 Routing CLIP and CLIR Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1478.4.2 Routing Calls without CLIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

8.4.3 Setting CLIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

8.4.4 Setting CLIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

8.5 Conversion of Call Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

8.6 Setting Number Type in OAD/DAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

8.7 Setting the Screening Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

8.8 Setting a Default OAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

8.9 Setting Sending Complete Byte in Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

8.10 Excluding Prefixes from vGATE Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

8.10.1 Exclusion from SIM Daily Call Attempts Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1528.10.2 Exclusion from SIM Minutes Counter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

8.11 Miscellaneous Routing Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

8.11.1 Routing Calls without a Destination Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

8.11.2 Routing Calls Based on Existence of Destination Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

8.11.3 Changing Cause Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

8.12 Caller ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

8.13 Call-Forwarding Translation: ISDN to SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Chapter 9 Mobile Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157

9.1 Connection to a vGATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

9.2 Module Distribution of Various Mobile Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

9.3 Network-Specific Mobile Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

9.3.1 Using a Fixed Mobile Port Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

9.3.2 Using the LAIN as the Mobile Port Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

9.3.3 Fixed LAIN for a Mobile Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

9.4 Incoming Voice Calls from Mobile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

9.5 Blocking Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

9.6 Setting Limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

9.6.1 Count Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

9.7 defining Time Limits for Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

9.8 Pause between Two Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

9.9 Time-Controlled SIM Logoff. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

9.10 Mobile-User PBX Callback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

9.11 Optional Mobile Quality Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

9.12 Deactivating Mobile ReRouting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

9.13 Setting Autodial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

9.14 Disconnecting Calls After Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

9.15 Checking Ports/Mobile Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170


6/231


6

9.16 Recharging Prepaid SIMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

9.16.1 Recharge Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Checking the Active SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Addressing SIMs Using Port- and Controller-Specific Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Blocking the Port Containing the Recharging SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

9.16.2 Recharging Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Direct Recharging via Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Indirect Recharging via GATE Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

9.16.3 Prepaid Account Status Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Direct Account-Status Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Indirect Account-Status Query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Saving /Forwarding the Account Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

9.17 Defining Special Characters for Voice Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Chapter 10 Least Cost Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180

10.1 Carrier Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

10.1.1 Routing Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

10.2 Alternative Routing Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

10.3 Charge Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

10.4 Generating Charges with the VoIPBOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Chapter 11 Online Traffic Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186

11.1 ASR Calculation and Resetting Statistic Values and Counters . . . . . . . . . . . . . . . . . . . . . . . . . . 18611.1.1 Saving and Sending Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

11.1.2 Saving Statistics and Resetting Statistic Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

11.1.3 Resetting Statistic Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

11.2 Generating and Retrieving CDRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

11.2.1 Call Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

11.2.2 Missed Calls List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

11.3 Generating Online CDRs via E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Chapter 12 DLA/Callback Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195

12.1 Call Connector and Callback Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19512.1.1 Special Announcement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

12.1.2 DLA with DTMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

12.1.3 DLA with Fixed Destination Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

12.1.4 Callback with DTMF and OAD as Callback Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

12.1.5 Callback with DTMF and PreConfigured Callback Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

12.1.6 Callback to OAD and Fixed Second Leg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

12.1.7 Callback with B-Leg First . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

12.1.8 DLA with DTMF and PIN for Second Leg and Callback for First Leg . . . . . . . . . . . . . . . . . . . . . . . 200

12.1.9 Using a PIN in Front of the Call Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200


7/231


7

Chapter 13 SMS Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201

13.1 Sending SMS via E-mail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

13.2 Receiving SMS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

13.2.1 SMS to E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

13.2.2 SMS to SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

13.2.3 SMS to File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

13.3 Setting Up Connections via E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

13.4 Sending Announcements via E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

13.5 Displaying Incoming Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

13.6 Sending Automatic SMS for Unconnected Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Chapter 14 Additional VoIP Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206

14.1 Signaling Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20614.2 Location Server Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

14.3 Routing Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

14.4 Quality Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

14.5 Compression Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

14.6 Fax/Modem Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

14.7 DTMF Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

14.8 Call Forwarding Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Chapter 15 Optional Function Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227

15.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22715.2 Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

15.3 SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

15.4 DNS Forwarder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

15.5 ipupdate - DynDNS Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229


8/231

A B O U T T H I S M A N U A L

8

VoIPBOX GSM 15.0u. Revised: 2010.

1 A B O U T T H I S M A N U A L

This manual is set up to guide you through the step-by-step installation of your VoIPBOX so that you can follow it

through from the front to the back. Quick-installation instructions appear in Chapter 4.8, Startup withTELES.Quickstart . Make sure you familiarize yourself thoroughly with the safety and security precautions de-tailed in Chapter 2 before you begin to install your VoIPBOX TELES is not liable for any damage or injury result-ing from a failure to follow these safety and security instructions!

1 . 1 O R G A N I Z A T I O N

This manual is organized into the following chapters.

Chapter 1, About this Manual introduces the VoIPBOX Systems Manual and how it is set up.

Chapter 2, Safety and Security Precautions contains information about security issues relevant

to connection with the IP network.

Chapter 3, Overview briefly describes the VoIPBOX and its implementation scenarios.

Chapter 4, VoIPBOX Installation contains information on how to connect and configure thesystem so that it is ready for operation.

Chapter 5, Configuration Files describes the VoIPBOXs individual configuration files andparameters.

Chapter 6, Routing Examples contains useful examples and descriptions of scenario-basedconfigurations in the r out e. cf g.

Chapter 7, System Maintenance and Software Update describes system messages that aresaved in the protocol file, as well as trace options.

Chapter 8, Signaling and Routing Features describes configuration settings in ther out e. cf gused for adjusting signaling and customizing the configuration for specific scenarios.

Chapter 9, Mobile Configuration Options describes mobile configuration entries.

Chapter 10, Least Cost Routing describes configuration options for various routing processes.

Chapter 11, Online Traffic Monitor contains the configuration for monitoring the systemsstatistics and CDRs.

Chapter 12, DLA/Callback Services contains money-saving features that expand the functionalityof your VoIPBOX to include callback capability and DTMF services.

Chapter 13, SMS Gateway contains a description of options for sending and receiving SMS

messages through the VoIPBOX. Chapter 14, Additional VoIP Parameters contains additional configuration entries to fine-tune

communication with the VoIP peer.

Chapter 15, Optional Function Modules contains information on expansion modules.

1 . 2 C O N V E N T I O N S

This document uses the following typographic conventions:

Bold items from the GUI menu.

Halfbold items from the GUI and the menu.
http://../Old_Templates/Box-Based/Box_Installation.pdfhttp://../Old_Templates/Box-Based/Box_Installation.pdfhttp://../Old_Templates/Box-Based/Box_Installation.pdfhttp://../Old_Templates/Box-Based/Box_Safety.pdfhttp://../Old_Templates/Box-Based/Box_Safety.pdfhttp://../Old_Templates/Box-Based/Box_Safety.pdfhttp://../Old_Templates/Box-Based/Box_Installation.pdfhttp://../Old_Templates/Box-Based/Box_Installation.pdf


9/231

A B O U T T H I S M A N U A L

9


Code file names, variables and constants in configuration files or commands in body text.

"conventions" on page 8 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.

1 . 3 S A F E T Y S Y M B O L S

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 func-tions 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 dischargeComponents at risk of discharge must be grounded before being touched.

ii

!!

!!


10/231

S A F E T Y A N D S E C U R I T Y P R E C A U T I O N S

C H A P T E R 2

10


2 S A F E T Y A N D S E C U R I T Y P R E C A U T I O N S

Please be sure and take time to read this section to ensure your personal safety and proper operation of your

VoIPBOX.

To avoid personal injury or damage to the system, please follow all safety instructions before you begin workingon your VoIPBOX.

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.

2 . 1 S A F E T Y M E A S U R E S

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.

If you do not use the Ethernet cable included in the package contents, make sure you use a shielded Ethernet cable.

2 . 2 F C C / I N D U S T R Y C A N A D A N O T I C E

In accordance with the manufacturers specifications, the VoIPBOX comes installed with modular transmittersQ24CL001 (FCC ID: O9EQ24CL001)and Q24PL001 (FCC ID: O9EQ24PL001).

The antenna gain, including cable loss, must not exceed 3 dBi at 1900 MHz / 1.4 dBi at 850 MHz for mobile op-erating configurations and 7 dBi at 1900 MHz / 1.4 dBi at 850 MHz for fixed mounted operations, as defined in2.1091 and 1.1307 of the rules for satisfying RF exposure compliance.

The antenna(s) used for this transmitter must be installed to provide a separation distance of at least 20 cm fromall persons and must not be collocated or operating in conjunction with any other antenna or transmitter.

The VoIPBOX has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a res-idential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installedand used in accordance with the instructions, may cause harmful interference to radio communications. However,there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harm-

ful interference to radio or television reception, which can be determined by turning the equipment off and on, theuser is encouraged to try to correct the interference by one or more of the following measures:

Reorient or relocate the receiving antenna.

Increase the separation between the equipment and receiver.

Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

Consult the dealer or an experienced radio/TV technician for help.


11/231


C H A P T E R 2

11


2 . 3 P O W E R S U P P L Y

The included power supply is to be used exclusively for operation of your VoIPBOX.

2 . 3 . 1 T E C H N I C A L D A T A

The following list includes technical information on the power supply:

Type: GSP-1216TLS/1 for VoIPBOX

Input voltage: 230V~ +/-15% 50-60Hz; 0.40A

Output voltage: 12V ---; 1.6A

Weight: 96g

Tested and certified as per EN60950-1

2 . 3 . 2 S Y M B O L S

The symbols on the power supply have the following meanings:

Make sure you read this chapter thoroughly and save the instructions for future ref-erence. Use only the power supply GSP-1216TLS/1 included in the package contentsof your VoIPBOX.

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

ii

o - + + - o


12/231


C H A P T E R 2

12


2 . 3 . 3 I N S T R U C T I O N S F O R U S E

Plug the power supply directly into the outlet. The power supply provides safety-low voltage with limited capacityfor your VoIPBOX.

The devices are designed for constant use in dry, indoor locations. However, we recommend that you unplug themif you do not intend to use them for an extended amount of time. Make sure the power outlet is easily accessibleat all time.

2 . 3 . 4 S A F E T Y P R E C A U T I O N S

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/orincorrect 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; donot pull on the cord.

The room temperature may not exceed 35C.

Do not use the device if it is damaged or if there are signs of misfunction. In this case, send it to TELESService or dispose of it properly (not with the public trash).

2 . 4 J A C K S

The jacks on the VoIPBOX have fulfilled the requirements of the following safety standards.

ETH jacks: SELV FXS jacks: TNV3

FXO Jacks: TNV3

BRI Jacks: SELV

Use only the power supply GSP-1216TLS/1 included in the package contents of yourVoIPBOX.

ii


13/231


C H A P T E R 2

13


2 . 5 T I P S F O R E M C P R O T E C T I O N

2 . 6 S Y S T E M S E C U R I T Y

This section describes all points crucial to the VoIPBOXs system security.

The VoIPBOXs location must support normal operation according to EN ETS 300 386. Be sure to select the location

with the following conditions in mind:

Servicing the VoIPBOX

Regular servicing ensures that your VoIPBOX runs trouble-free. Servicing also includes looking after the room inwhich the system is set up. Ensure that the air-conditioning and its filter system are regularly checked and that thepremises are cleaned on a regular basis.

Use shielded cables.Do not remove any housing components. They provide EMC protection.

Location: Make sure you install the system in a clean, dry, dust-free location. If pos-sible, use an air-conditioned site. The site must be free of strong electrical or mag-netic fields, which cause disrupted signals and, in extreme cases, system failure.

Temperature: The site must maintain a temperature between 0 and 35C. Be sure toguard against temperature fluctuations. Resulting condensation can cause short cir-cuiting. The humidity level may not exceed 80%.To avoid overheating the system, make sure the site provides adequate ventilation.

Power: The site must contain a central emergency switch for the entire power source.The sites fuses must be calculated to provide adequate system security. The electri-cal facilities must comply with applicable regulations.The operating voltage and frequency may not exceed or fall below what is stated onthe label.Antenna: VoIPBOX contains no provision or protective device against power surgesor lightning strikes.The installation of the antenna must fulfill all necessary safety requirements. Employ

the services of a professional antenna installer.

!!

!!


14/231


C H A P T E R 2

14


2 . 6 . 1 P R O T E C T I N G T H E O P E R A T I N G S Y S T E M

Changing configuration data and/or SIM card positions may lead to malfunctions and/or misrouting, as well as pos-

sible consequential damage. Make changes at your own risk. TELES is not liable for any possible damage resultingfrom or in relation to such changes. Please thoroughly check any changes you or a third party have made to yourconfiguration!

Make sure your hard disk or flash disk contains enough storage space. Downloading the log files and deleting themfrom the VoIPBOX on a regular basis will ensure your VoIPBOXs reliability.

Be careful when deleting files that you do not delete any files necessary for system operation.

2 . 7 C D R F I L E S

Call Detail Records are intended for analysis of the VoIPBOXs activity only. They are not designed to be used for

billing purposes, as it may occur that the times they record are not exact.

2 . 8 N E T W O R K S E C U R I T Y

Every day hackers develop new ways to break into systems through the Internet. While TELES takes great care toensure the security of its systems, any system with access through the Internet is only as secure as its user makesit. Therefore, to avoid unwanted security breaches and resulting system malfunctions, you must take the followingsteps to secure your VoIPBOX if you connect it to the Internet:

Use an application gateway or a packet firewall.

To limit access to the VoIPBOX to secure remote devices, delete the default route and add individual secure

network segments. Access to the VoIPBOX via Telnet, FTP or GATE Manager must be password protected. Do not use obvious

passwords (anything from sesameto your mother-in-laws maiden name). Bear in mind: the passwordthat is easiest to remember is also likely to be easiest to crack.

The firewall must support the following features:

Protection against IP spoofing

Logging of all attempts to access the VoIPBOX

vGATE Control Unit:Do not use Ctrl/Alt/Del (Task Manager) to shut down vGATEDesktop or vGATECtrl. Donot perform queries on the database. This can result in damages to the database. Do

not use any MySQL tools, such as MySQL-Front to make changes in or perform testson the database.

Inaccuracies in the generation of CDRs may occur for active connections if traffic isflowing on the system while modifications in configuration or routing files are acti-

vated.

!!

ii


15/231


C H A P T E R 2

15


The firewall must be able to check the following information and only allow trusted users to access the VoIPBOX:

IP source address

IP destination address

Protocol (whether the packet is TCP, UDP, or ICMP)

TCP or UDP source port

TCP or UDP destination port

ICMP message type

For operation and remote administration of your VoIPBOX BRI open only the following ports only when the indi-cated services are used:

Table 2.2 Default Ports Used for Specific Services

Service Protocol PortFor all systems except vGATE

FTP TCP 21 (default, can be set)

Telnet (for TELES debug accessonly)

TCP 23 (default, can be set)

SMTP TCP 25

DNS forward UDP 53

HTTP TCP 80 (default, can be set)

SNTP UDP 123

SNMP UDP 161 (default, can be set)

H.225 registration, admission, sta-tus

UDP 1719 (default, can be set)

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)

vGATE Control Unit TCP 57343

vGATE tunneling TCP 4446

For vGATE Control Unit and iMNP

FTP TCP 21


16/231


C H A P T E R 2

16


Telnet TCP 23

MySQL database TCP 3306

iGATE or VoIPBOX to vGATE TCP 57342

vGATE tunneling to iGATE or

VoIPBOX

TCP 4446

iGATE or VoIPBOXto iMNP TCP 9003

Remote vGATEDesktop TCP 57344

Remote vGATEDesktop (read only) TCP 57345For vGATE Sim Unit

vGATE Control Unit plus iGATE orVoIPBOX

TCP 51500

For NMS

FTP TCP 21

Telnet TCP 23

MySQL database TCP 3306

NMS protocol TCP 5000

NMS update TCP 5001

NMS task TCP 5002

NMS task TCP 5003

NMS Listen TCP 4444

For vGATE Call Manager

Radius authentication UDP 1812

Radius accounting UDP 1813

Table 2.2 Default Ports Used for Specific Services (continued)

Service Protocol Port


17/231

O V E R V I E W

C H A P T E R 3

17


3 O V E R V I E W

The VoIPBOX GSM Family provides a combined mobile and VoIP gateway solution for carrier networks and for

corporate customers wanting to connect their PBX to mobile and VoIP services. This full-featured gateway can beadded to analog and IP environments in a cost-effective and convenient manner. The VoIPBOX GSM Family con-verts fixed-to-mobile into mobile-to-mobile calls, terminating calls to mobile networks at lower rates than possiblevia fixed-net interconnection.

The VoIPBOX GSM Family includes the following variations:

VoIPBOX GSM 2

VoIPBOX GSM 4

VoIPBOX GSM 2 FXS

VoIPBOX GSM 4 FXS

VoIPBOX GSM 2 BRI

VoIPBOX GSM 4 BRI

VoIPBOX GSM 2 LCR

VoIPBOX GSM 4 LCR

3 . 1 W H A T S N E W I N V E R S I O N 1 5 . 0 U

VoIPBOX GSM now available with 2 or 4 GSM engines

VoIPBOX GSM now available with BRI or FXO/FXS extension

Calling Line Identification Presentation (CLIP) detection on FXO ports

Calling Line Identification Restriction (CLIR) on FXS ports

Software checks for hardware extension

Redial function now possible

Autodial function now possible

Log-file field names have been changed (V1 now C1 for CDR and F1 for failed)


18/231

O V E R V I E W

C H A P T E R 3

18


3 . 2 F E A T U R E S

Mobile

2 or 4 GSM channels

Built-in SIM-card server support for unlimited SIMs per channel with vGATE Sim Unit

Individual timers for each SIM /call

Possible to configure individual mobile bands

Radius accounting request contains SIMs IMSI to enable SIM-specific billing

Support for vGATE sub-limits

Number portability

GSM-specific configuration parameters now definable per mobile network (LAIN)

vGATE RoutingManager support

Emails to SMS: support for SMS delivery report

VoIP

8 or 16 media channels

H.323 v.4 / SIP v.2 signaling (RFC 3261), operating in parallel

Various audio codecs: G.711, G.723.1, G.726, G.728, G.729, GSM, iLBC, Fax T.38, Data: clear channel

RTP multiplexing (reduces bandwidth required for RTP data by up to 60%)

ENUM client

Echo cancellation G.1682000

Silence suppression, comfort noise generation, voice activity detection Support for multiple gatekeepers and multiple registrars

STUN client

Traffic shaping

Configurable time interval for echo detection in VoIP

ISDN

2 BRI ports, TE or NT

DSS1 (Q.931),Q.SIG-BC; PP or PMP

Analog

4 analog lines (FXS)

Fax/modem detection (UDT)

Charging impulse (12/16kHz)

Integrated line echo cancellation


19/231

O V E R V I E W

C H A P T E R 3

19


FXS

Power feeding for FXO devices

Dial-tone and ring-tone generation

CLIP transmission

FXO

CLIP detection

Dial-tone and ring-tone generation

LCR Engine

Multiple VoIP-carrier logins

Multiple PSTN routing methods

Multilevel alternative routing

Dynamic fallback to PSTN

Dynamic fallback to VoIP

Lifeline functionality on power loss or system failure

General

User-friendly GUI with easy and advanced mode configuration settings

Ringtone generation

Configurable ToS/DivServ

AOC generation Integrated DSL router (PPPoE)

2nd separate 10/100 Base-T Ethernet interface

Status indication via LEDs

Integrated mail client capable of SMTP authentication

Email messages can trigger calls and play attached announcements

Automatic test call

3 . 3 I M P L E M E N T A T I O N S C E N A R I O S

These are the most commonly used implementation scenarios:


20/231

O V E R V I E W

C H A P T E R 3

20


VoIP GatewayThe VoIPBOXes sophisticated routing algo-rithms allow VoIP communication via SIP serv-

er and/or gatekeeper (H.323), as well as multi-destination operation without a SIP Server orgatekeeper. Various voice codecs ensure uni-versal connection to different VoIP destina-tions. Fax transmission occurs via T.38 orfallback to G.711a. Backup routes can be ac-tivated in case of VoIP peer failure. After a de-fined amount of time, the VoIPBOX resumes itsprimary route.

Least Cost Router 2nd GenerationThe VoIPBOXs sophisticated routing algo-rithms serve as an LCR between your PBX andthe PSTN or VoIP carrier. Internet connectioncan occur via integrated DSL router. The sys-tem reverts to ISDN if there is an IP connectionfailure.

Mobile NTThe VoIPBOXes are connected to the custom-ers PBX with up to four lines, and to the mo-bile carriers network via GSM. The mobilegateway can multiplex the available mobilechannels, as well as directly connect subscrib-ers.

LAN VoIP

Carrier

4 x BRI

Ethernet

LAN VoIP

Carrier

2 lines

Ethernet

2 lines

PSTN

4 lines

4 lines


21/231

O V E R V I E W

C H A P T E R 3

21


Corporate ScenarioThe VoIPBOX only receives mobile calls fromthe customers PBX. Calls are terminated di-

rectly in the mobile network. The sophisticatedrouting algorithms allow you to route calls tospecific carriers if SIM cards from various carri-ers are used.

Mobile Gateway with VoIPThe VoIPBOXes are set up in small or medium-sized enterprises. The mobile gateway canmultiplex the available mobile channels for anattached PBX and/or a Soft PBX. It can alsoconnect subscribers directly. The sophisticatedrouting algorithms allow additional VoIP com-munication via SIP and/or H.323. Various voicecodecs ensure universal connection to differentVoIP destinations. Fax transmission occurs viaT.38. The VoIPBOX recognizes calls to the mo-

bile network and sends them through the mo-bile gateway to the mobile network. All othercalls are terminated via the VoIP carrier.

Carrier ScenarioOne or more mobile gateways are connectedto the carrier network via VoIP.The carrier net-work routes mobile connections to the individ-ual mobile gateways, which then terminate themobile calls.

4 lines

PSTN

IP

Network

PSTN


22/231

O V E R V I E W

C H A P T E R 3

22


Connection to a centralized SIM server(vGATE):The mobile gateways are integratedin the vGATE through the IP network. All SIM

cards in the vGATE network are installed inand maintained from a central server, so that itis no longer necessary to install SIM cards intoeach VoIPBOX. The vGATEDesktop makes itpossible to assign SIMs virtually to randomports and various times without physically re-moving the SIMs from the vGATE Sim Unit.

IP

Network


23/231

V O I P B O X I N S T A L L A T I O N

C H A P T E R 4

23


4 V O I PBO X I N S T A L L A T I O N

This section contains information on basic installation and configuration of your VoIPBOX. Follow the easy instruc-

tions to set up your VoIPBOX in a matter of minutes.

Implementation of individual scenarios require adjustments to the appropriate interfaces. Tips for basic settings aredescribed here. Links to relevant chapters are provided for more specific configuration changes.

4 . 1 C H E C K L I S T

The following checklist provides step-by-step installation instructions.

1. Check the package contents2. Install the device3. Connect the BRI or analog lines to the PBX and/or the PSTN4. Check functionality (using the LEDs)5. Using Quickstart, set the configuration (IP address and BRI / VoIP configuration)6. Secure the LAN connection7. Secure connection with the configuration program

4 . 2 P A C K A G E C O N T E N T S

Your VoIPBOX package contains the following components. Check the contents to make sure everything is com-plete and undamaged. Immediately report any visible transport damages to customer service. If damage exists, donot attempt operation without customer-service approval:

1 VoIPBOX

1 power supply

1 RJ-45 LAN cable with gray connectors

1 antenna with magnetic mount


24/231


C H A P T E R 4

24


4 . 3 V O I P B O X H A R D W A R E D E S C R I P T I O N

Figure 4.1 shows the front and rear view of all VoIPBOX variations. The VoIPBOX handles traffic on up to 8

Figure 4.1 VoIPBOX: Front and Rear View

VoIPBOX GSM

VoIPBOX GSM FXO

VoIPBOX GSM LCR

VoIPBOX GSM FXS

VoIPBOX GSM BRI
http://-/?-http://-/?-http://-/?-


25/231


C H A P T E R 4

25


media channels. The following pages describe installation of the VoIPBOX.

4 . 4 I N S T A L L A T I O N R E Q U I R E M E N T S

Before installing your VoIPBOX, make sure you have the following connections in place:

Ethernet connection

ISDN BRI or Analog connection to PBX and/or to the PSTN

Power

4 . 4 . 1 A N A L O G W I R I N G

The TE ports connect to the PSTN and the NT or FXS ports connect to the PBX. You can connect the VoIPBOX to

additional outlets for any additional interfaces.

Figure 4.2shows the standard pin assignment for each FXS analog port.

Figure 4.3shows the standard pin assignment for TE and NT modes. You must change the pin assignment if itdiffers on the connected equipment

If you do not use the included cable, make sure you use only a shielded Ethernet ca-ble!

An attached NTBA or PBX must be connected to the ISDN1 TE outlet if it is to providethe clock for the VoIPBOX!

ii

ii

1

2

3

4

5

6

TipRing

Figure 4.2 Analog Wiring Scheme

7

8

3

4

5

6

Network

Interface

1

2

7

8

3

4

5

RX+

6TX-

Terminal

Interface

1

2

TX+

TE NT

Abbreviations: TX - Transmit / RX - Receive

RX-

TX-

RX+RX-

TX+

Figure 4.3 ISDN Wiring Scheme
http://-/?-http://-/?-http://-/?-http://-/?-


26/231


C H A P T E R 4

26


4 . 4 . 2 E T H E R N E T W I R I N G

To connect the VoIPBOXs Ethernet port to your local network, connect the system to an Ethernet switch or hub in

your network. Use the three meter cable with gray connectors.If you want to connect the VoIPBOX directly to your computer and a connection cannot be established after youplug the cable in, use a cable with the following pin assignment:

4 . 5 P R E P A R I N G F O R I N S T A L L A T I O N

Each computer that is to communicate with the VoIPBOX requires a network connection. Please have the followinginformation for connection to your network available:

IP address in your local network for the VoIPBOX to be configured

Netmask for the VoIPBOX to be configured

Default gateway for VoIPBOX to be configured

DNS server address

NTP server address

4 . 6 H A R D W A R E C O N N E C T I O N

Connect your computer with the local network

Connect the VoIPBOX with the local network

Connect the VoIPBOX with your PBX according to the port configuration.

Connect the VoIPBOX with the power supply.

Bear in mind that the preconfigured VoIPBOXs default IP address is 192.168.1.2. Ifthis IP address is already being used in your local network, you must run Quickstartwithout a connection to your local network. This can occur using a back-to-backEthernet connection from your computer to the VoIPBOX.If the desired IP address for the VoIPBOX is not in your network, you must assign yourcomputer a temporary IP address from this IP-address range.

1

2

7

8

3

4

5

6

7

8

3

4

5

6

1

2

RX+

RX-

TX+TX- TX-

TX+

RX+

RX-

Connector 1 Connector 2

Abbreviations: TX - Transmit / RX - Receive

Figure 4.4 Ethernet Wiring Scheme

ii


27/231


C H A P T E R 4

27


4 . 7 L E D F U N C T I O N A L I T Y

Each VoIPBOX has the following status LEDs:

Table 4.1 VoIPBOX LEDs

LED Description

Green 1-4 Off:

Telephone on the hook.

On:

Telephone off the hook.

Blinking:

Call active.

Green 5 On:

At least one SIM is active.

Blinking:

Mobile call.

Green 6 On:

All four SIMs are active.

Green 7-8 Off:

Link is down.

On:Link is active, no traffic.

Blinking:

Link is active with traffic.

Green 9 Off:

No VoIP call/no error

On:

VoIP call active

Blinking:

VoIP registration error

Red Off:

Power off.

On:

Power on.


28/231


C H A P T E R 4

28


4 . 8 S T A R T U P W I T H Q U I C K S T A R T

Quickstart is an application that helps you to configure the IP settings of your VoIPBOX quickly and conveniently

without changing any network settings on your computer. You will need Quickstart as of version 15.0.Quickstart can be installed on any of the following operating systems:

Windows 2000

Windows XP

Windows Vista

If you are using any of these operating systems, please follow the instructions in this chapter. If you are using anon-Windows operating system (e.g. Linux) follow the instructions in Chapter 4.9 .


29/231


C H A P T E R 4

29


4 . 8 . 1 I N S T A L L I N G Q U I C K S T A R T

Make sure the GATE Manager is not run-

ning on your computer. To install Quick-start on your computer, insert the CD andselect Quickstart from the menu.

When asked if you want to install compo-nents on your machine, click Install.

Click Nextin the introduction window tobegin installation of the Quickstart.

Once installation begins, click Nextto in-stall Quickstart in the predefined folder.To install it in another location, click

Browse and select a folder from thebrowser that appears. Then click Next.

Click Close to exit when installation iscomplete.

Figure 4.5 Quickstart Installation


30/231


C H A P T E R 4

30


4 . 8 . 2 C O N F I G U R A T I O N W I T H Q U I C K S T A R T

Figure 4.6 Quickstart

Now you can use Quickstart to set up your VoIPBOX. Open Quickstart.exe. The program will automatically searchfor your VoIPBOX in the local network. For Quickstart, the source UDP port is 57445. It might be necessary tochange the firewall rules on your system.

Click the Searchbutton to restart the search. When the program has found your VoIPBOX, it will appear in themain window. As soon as it appears, you can end the search by clicking Stop. The window on the right providesa running tally of the systems status.

The systems icon will appear in gray if it is unconfigured. Once it has been configured, it will appear in green. Theserial number appears as the systems name.

To change the appearance of the window, select Large Icons, Small Iconsor Detailsfrom the Viewmenu. In

the following description, we will use the Details View, which contains the following columns:

In the Optionsmenu, you can suppress or activate ICMP ping to test the Internet connection.

Table 4.2 Quickstart Details View Columns

Heading Definition

Identifier This column lists the systems serial number.

IP Address This column lists the systems IP address.

Configured An X means the system contains the configuration files.

# of VoIP Ctrls This column lists the number of VoIP Modules installed in the system. It will always be 1.VoIP Channels This column shows the number of VoIP channels per VoIP Module.

Type Lists the type of system.

Box An X means the system is a TELES box-based system.

CF Mounted This column is not relevant for TELES box-based systems.


31/231


C H A P T E R 4

31


To perform the initial configuration of the system, double-click the icon or right-click and select Configure. The IPSettingsdialog will appear. If you are using a DHCP serv-

er, activate the checkbox DHCP. This will deactivate thenext four lines. Your DHCP server will automatically provideall of the other necessary information. If you do not have aDHCP server, leave the DHCPcheckbox empty. The defaultIP address appears in the IP Addressbox. Enter a new IPaddress. If the address you enter already exists in the net-work, you will be notified to choose another address at theend of the configuration process. Enter the systems net-mask in the Maskdialog box. Enter the IP address for theDefault Gateway and the Time Server in the corre-sponding dialog boxes. Select the Time Zonefor the loca-

tion of the system. Click Finish.

Now the IP settings are configured; all other processes run automatically. First the systems IP address will bechanged and then the system will start with the new IP address.

If you right-click the systems icon in the main window and choose Temporarily Configure IP Address, only theIP address for the systems first Ethernet interface and the netmask will be temporary changed. This can be helpfulif you want to set up local remote access to the system and use other IP settings on the remote device than thesystems IP configuration in the network. Bear in mind that the functions on the systems first Ethernet interfacework with the new settings.

Now you can complete the systems configuration using the GUI (cf. Chapter 4.8.3 on page 32 ).

There is no internal time generation for the system when the power is interrupted.That means the default time is used when the system is restarted or rebooted! There-fore it is important to set the system time with an NTP server.

Figure 4.7Quickstart Configuration: IP Settings

ii


32/231


C H A P T E R 4

32


4 . 8 . 3 S T A R T U P V I A G U I

Figure 4.8 GUI

System configuration can occur via the GUI. We recommend you use Internet Explorer 6/7. Simply open a browser,enter the systems IP address in the address bar, and click Loginin the navigation menu on the left. Enter theusername teles-carrierand the password tcs-carrierto access the system.

Using the navigation menu on the left, click Faststartto configure the system. Follow the steps as they appear.

4 . 9 S T A R T U P V I A F T P

If you are using a computer that does not use a Windows operating system, you can preconfigure the system viaFTP. The systems default IP address is 192.168.1.2. To configure the system using FTP, you must assign your com-puter an IP address from network range 192.168.1.0 Class C and then access the system via FTP.

The default user is telesand the default password is tcs-ag. To configure the system, use the default config-uration file example on the CD for your device in the Configfilesdirectory and the following subdirectories:

ip.cfg

This subdirectory contains the file (ip.cfg) responsible for configuration of the Ethernet interface. pabx.cfg

This subdirectory contains the file (pabx.cfg) responsible for the port configuration.

route.cfg

This subdirectory contains the file (route.cfg) responsible for the routing configuration.

To edit the default configuration, follow the directions in Chapter 5.2.1.4 . Upload the configuration files intothe /bootdirectory.


33/231


C H A P T E R 4

33


4 . 1 0 S E L F P R O V I S I O N I N G W I T H N M S

With a management connection to the NMS (Network Management System), the VoIPBOX can retrieve its config-

uration files from the configured NMS. That means that custom configuration of the device occurs automaticallywhen the device is started. The following setting must be made in the [System]section of the pabx.cfg:

AlarmCallback=

RemoteCallback=

As soon as the device is started, it connects automatically with the NMS, which uses the devices TAG number tosend a prepared configuration. For further information on configuration of the NMS, please refer to the NMS Sys-tems Manual.

4 . 1 1 R E M O T E A C C E S S A N D A C C E S S S E C U R I T Y

After the system has been configured and all cables are connected, remote administration and maintenance canoccur with the GATE Manager (Chapter 4.11.1), the GUI (Chapter 4.11.2), or via FTP (Chapter 4.11.3 ).

4 . 1 1 . 1 G AT E M A N A GE R

Figure 4.9 GATE Manager

The GATE Manager administration and maintenance software offers a broad range of functions. TheGATE Manager is user friendly and can be customized to suit your needs.


34/231


C H A P T E R 4

34


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

Use the CD enclosed in your package contents to install the GATE Manager. You have to use GATE Manager ver-

sion 15.0 or later. For a detailed description of installation and implementation of the GATE Manager, please referto the GATE Manager and Utilities Programs Manual.

GATE Manager remote access can occur via IP. GATE Manager access via IP uses port 4444 as origination TCP portand port 4445 as destination port. The following default value (4445) is configured in the pabx.cfgfile for the

systems port:

In the default configuration, ISDN access is disabled. To configure the system so that certain data calls are receivedas remote administration calls, make the following changes in the pabx.cfg:

RemoteCode=BBB

MapAll=BBB DATA

Make the following entries in the route.cfgif the system is to handle all data calls as remote-administrationcalls:

MoipPort=4445

MapAll0=BBB DATAMapAll1=BBB DATAMapAll2=BBB DATAMapAll3=BBB DATAMapAll4=BBB DATAMapAll5=BBB DATA

MapAll6=BBB DATAMapAll7=BBB DATAMapAll8=BBB DATAMapAll9=BBB DATA


35/231


C H A P T E R 4

35


4 . 1 1 . 2 G R A P H I C A L U S E R I N T E R F A C E

Figure 4.10 GUI

Remote access can occur via the GUI. Even users with little experience can easily configure standard system settingswith this interface. Simply open a browser and enter the systems IP address in the address bar. We recommendthat you use Internet Explorer 6/7.

The following administrative levels apply:

Carrier Mode (Full Access)

User: teles-carrier

Password: tcs-carrier

All configuration pages can be accessed in this mode.

Administrator Mode

User: teles-admin

Password:tcs-admin

This access level is for the user networks administrator. All IP and routing entries, with the exception of VoIP carrierentries, can be set here.

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.


36/231


C H A P T E R 4

36


Of course, these configuration levels correspond with the most important scenarios. The passwords are saved inthe ip.cfgin encrypted form:

PwdCarrier=

PwdAdmin=

PwdUser=

Example:

The user interface is divided into the following main sections:

All of the user interfaces pages contain Helpbuttons and links to the online help, which provides a detailed de-scription of all of the individual configuration settings.

[httpd]PwdUser=k24X0sdc.uMcMPwdAdmin=k2UMj19qtovzIPwdCarrier=k2jryo6Xd5vN6

Never copy these entries from one system to another, as the encryption is unique foreach system.

Table 4.3 GUI: Sections

Section Description

User Data Here you can change the user passwords and the language for the HTTP in-terface.

System Settings IP Settings: Settings for the Ethernet interfaces and related services.

Port Settings: Settings for the VoIPBOXes ports.

VoIP Settings: VoIP settings for the SIP or H.323 carrier.

Telephony Routing:Routings for telephone numbers.

System Overview Overview of system information and drivers.

Telephony Routing VoIP settings for the SIP or H.323 carrier and routings for telephone num-bers.

Commands Here you can activate a configuration or restart the system.

ii


37/231


C H A P T E R 4

37


4 . 1 1 . 3 F T P

Remote access can also occur via FTP. You can use FTP to transfer configuration files. You can also carry out func-

tions and traces with raw commands. Use the username telesand the defined password to connect to the sys-tem with FTP.

The following entries ensure the security of your FTP access:

Once you have access to the system, you will be in the folder /home/teles. To upload or download configura-tion files change to the directory /boot. To download log files, also change to the directory /boot.

The following commands can be carried out via FTP access:

4 . 1 1 . 4 S E T T I N G A P A S S W O R D F O R R E M O T E A C C E S S

The following entry ensures the security of your remote access. Use the mkpwd.exetool to generate the pass-word. You will find it on the enclosed CD in the directory pwd.

Table 4.4 FTP Security Entries

FTP Security

FtpdPort=

Defines the FTP access port (default 21).

RemotePassword=Defines the password for FTP and GATE Manager access. Please refer to Chapter 4.11.4 for instructionson how to enter an encrypted password in the pabx.cfg. If you do not define a password, access to thesystem via GATE Manager occurs without a password, and FTP access occurs with the default passwordtcs-ag.

Table 4.5 FTP Commands

Command Function

SITE xgboot Boots the entire system.

SITE xgact Activates the configuration.

SITE xgact 1-19 Activates the Nightsection corresponding with the number 1-19.

SITE xgtrace 0 Deactivates trace.

SITE xgtrace 1 Activates layer 2 trace.SITE xgtrace 2 Activates layer 3 trace.


38/231


C H A P T E R 4

38


Start the program in a command window with the entry mkpwd . The output shows the encryptedpassword. Enter the encrypted password in the configuration file pabx.cfgs parameter line as follows:

When the file has been transferred to the system and the configuration has been activated, access to the systemcan occur only with the password. Dont forget to memorize the password!

If you do not define a password, access to the system via GATE Manager occurs without a password, and FTP ac-cess occurs with the default password tcs-ag.

RemotePassword=


39/231

C O N F I G U R A T I O N F I L E S

C H A P T E R 5

39


5 C O N F I G U R A T I O N F I L E S

This chapter describes the basic setup and the most commonly used entries for the configuration files. Configura-

tion of VoIPBOXes is managed in the following three files:

The system comes without the files. The default configuration with the IP address 192.168.1.2 is active when thefiles are not on the system. You can configure the system using Quickstart, GATE Manager or via FTP (userteles,

password tcs-ag). If you use the GUI to make configuration changes, the files will be adjusted automatically.

Make sure you secure the system with new passwords following configuration and remember to memorize thepasswords!

These configuration files contain all system-specific settings and are used when the system starts. Comments in-cluded in these files must begin with a semicolon. They do not need to be at the beginning of a line. Configurationfiles must end with an empty line.

The configuration files follow these conventions: Individual files are divided into sections. These sections alwaysbegin with a line entry in square brackets. The basic required sections are in these files:

Table 5.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 entries.

Changing configuration data may lead to malfunctions and/or misrouting, as well aspossible consequential damage. All changes are made at own risk. TELES is not liablefor any possible damage out of or in relation to such changes. Please thoroughlycheck any changes you or a third party have made to your configuration.

Table 5.2 Required Configuration File Sections

Section File Function

[System] pabx.cfg

route.cfg

ip.cfg

This section contains the systems basic settings.

[Night]

EXAMPLE:

[Night1]

[Night2]

pabx.cfg

route.cfgThis section contains time dependent entries that only apply forlimited times.

ii


40/231


C H A P T E R 5

40


5 . 1 C O N F I G U R A T I O N F I L E I P . C F G

The basic settings for the two Ethernet interfaces are entered here. One interface usually suffices. The second in-terface can be used for special requirements, e.g. as a hub port, DSL router or vLAN interface. Generally, thesesettings are entered once and then left unchanged.

This file contains the following sections, which must appear in the order given:

[emac0] ip.cfg This section contains the IP configuration for the first Ethernet in-terface.

Table 5.3 Sections in the ip.cfg File

Section Function

[System](required) This section contains entries that define the default gateway and/or specialrouting entries.

[emac0] (required)[emac1] (optional)

The Ethernet Media Access Controller section(s) define the physical Ethernetinterface(s).

[httpd] This section contains the port and access password parameters for the

graphical user interface.[nat](optional) This section includes settings for Network Address Translation.

[br i dge0] (optional) These section(s) contain settings for the second Ethernet controller in bridgemode.

[pppoe] (optional) These sections contain settings for direct connection between the systemand the DSLAM when the PPPoE protocol is used. can be 0or 1.

[firewall](optional) This section contains settings for activating the systems firewall.

[altqd](optional) This section enables prioritization of VoIP packets in the VoIPBOX through

an IP network using bandwidth control.[dhcpd](optional) This sections contains a list of parameters and settings for the DHCP server

in the system. It is divided into global settings for the server and parametersfor the DHCP subnet.

[vl an] (optional) These section(s) contain settings for the virtual networks. can be any-thing from 0to 9.

Table 5.2 Required Configuration File Sections (continued)

Section File Function


41/231


C H A P T E R 5

41


5 . 1 . 1 S Y S T E M S E C T I O N C O N F I G U R A T I O N

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=

Example:

If you must route specific net ranges to gateways other than what is defined in the default route, make the follow-ing entries in the [System] section:

Route= -netmask

Example:

If only certain routes apply, leave the line DefaultGwempty.

5 . 1 . 2 E T H E R N E T I N T E R F A C E C O N F I G U R A T I O N

The following settings are possible for the sections [emac0]and [emac1]:

IpAddress=/The IP address is entered in decimal notation, followed by a slash (/) and the netmask in bit notation.

Example:

The following entry is used to allocate an IP address via DHCP:

IpAddress=dhcp

The following entry is used in the [emac1]section if operation of the system is occurs in bridge mode.

IpAddress=up

5 . 1 . 3 G U I S E T T I N G S

The following parameter is used to change the GUI port in the section [httpd] (default 80):

GuiPort=

Bear in mind that the passwords for different access levels are not set here. The encrypted passwords are storedhere and can only be changed via GUI (cf. Chapter 4.11.2 on page 35).

[System]DefaultGw=192.168.1.254

[System]DefaultGw=192.168.1.254Route=10.0.0.0 -netmask 255.0.0.0 192.168.1.1

IpAddress=192.168.1.2/24


42/231


C H A P T E R 5

42


Example:

5 . 1 . 4 B R I D G E C O N F I G U R A T I O N

A bridge can connect two networks with each other. A bridge works like a hub, forwarding traffic from one inter-face to another. Multicast and broadcast packets are always forwarded to all interfaces that are part of the bridge.This can occur on the Ethernet or VLAN level:

BrConfig=add add up

Activating another Ethernet interface in this way is useful, for example, when the Ethernet switch does not haveany more ports available for connection of the system. You can simply unplug a cable and plug it into the systemssecond Ethernet interface.

Example:

5 . 1 . 5 N A T C O N F I G U R A T I O N

The NAT (Network Address Translation) module translates IP addresses from the local network to an IP address or

range on a public interface. All rules are defined in the [nat]section:

[httpd]GuiPort=80

PwdUser=k24X0sdc.uMcMPwdAdmin=k2UMj19qtovzIPwdCarrier=k2jryo6Xd5vN6

[bridge0]BrConfig=add emac0 add emac1 up

Table 5.4 NAT Configuration

map= ->

This parameter maps the IP address in the local network to the IP address in the public network.

Defines the translated interface or protocol:

emac1 The systems second Ethernet interface

pppoe0 Protocol used for DSL connectionsxppp Protocol used for dial-up connections

The IP address is entered in decimal notation, followed by a slash (/) and the netmaskin bit notation. The entire local network range is configured.

Defines the public network range, with network address and mask (usually exactly oneaddress), into which the local IP addresses are to be translated. The IP address is enteredin decimal notation, followed by a slash (/) and the netmask in bit notation.


43/231

C O N F I G U R A T I O N

Documents

TELES_VoIPBOX_GSM_15.0